cancel
Showing results for 
Search instead for 
Did you mean: 

Veritas appliances are unable to ping any client in a certain subnet

DoubleP
Level 6
   VIP   

A certain linux policy has been failing consistently for the last couple months. Working with our internal linux admin team, we've discovered that when acting as media servers, the appliances (3.0) are unable to ping anything in a certain subnet. The appliances are 5330s and 5240s. The jobs fail with a 58: 

Error bpbrm (pid=1009) cannot connect to client.company.com

Before anyone asks; yes, the appliances do show up in the client's server and media server lists. 

1 ACCEPTED SOLUTION

Accepted Solutions

Krutons
Level 6
   VIP   

Have you looked at the route tables on the client and appliances since these specific clients are in a different subnet?

View solution in original post

2 REPLIES 2

Krutons
Level 6
   VIP   

Have you looked at the route tables on the client and appliances since these specific clients are in a different subnet?

View solution in original post

sdo
Level 6
Partner    VIP    Certified

ping and ICMP traffic have absolutely nothing at all to do with status 58.  Maybe your networking team, or OS management teams, have blocked ICMP traffic across switches and firewalls and routers and within the OS themselves.

Anyway, status 58 can be caused by many things (but not lack of ping), such as:  no route to client, client down, client powered-off, client lost networking, ports not open across firewall, client not installed, client stopped, client un-installed... anyway, status 58 effectively means that the server was unable, for whatever reason, to reach the client - nothing at all to do with ping.