traceroute was removed from the boxmgmt internal commands several years ago due to security reasons.
I would recommend that you leverage the network connectivity tests, ping, telnet, arp, arping and most importantly netstat to troubleshoot this one.
I've seen many instances where static routes were in affect, causing very similar outcome to what you're seeing. You might want to exclude other issues such as: VLAN membership, closed firewall ports, etc.
Idan
3 Apprentice
•
675 Posts
0
December 14th, 2015 11:00
Hi there,
traceroute was removed from the boxmgmt internal commands several years ago due to security reasons.
I would recommend that you leverage the network connectivity tests, ping, telnet, arp, arping and most importantly netstat to troubleshoot this one.
I've seen many instances where static routes were in affect, causing very similar outcome to what you're seeing. You might want to exclude other issues such as: VLAN membership, closed firewall ports, etc.
Regards,
Idan Kentor
RecoverPoint Corporate Systems Engineering
Email: idan.kentor@emc.com
Twitter: @IdanKentor