Perfect Example for me was I was running into an issue where I could not ping a public TLOC address from vmanage, or either of the vsmarts, yet that address replied from anywhere else AND when I changed the tloc address on the vEdge to something else in the same network range, it replied to pings!
This meant we KNEW the issue was on the vsmart. But it was very hard to get the vSmart to show me its next-hop, so eventually i found that if you login to the vshell you can actually run the ip route show command....
vmanage-0# vshell
vmanage-0:~$ /sbin/ip route show| grep blackhole
blackhole 71.22.44.5
Obviously I have changed IP addresses to protect the innocent, but in this example the IP I could not reach was 71.22.44.5, I had run into this bug:
No comments:
Post a Comment