Along with the changes mentioned in my last post related to how ESXi responds to a ping, there are also some changes to the ping command.
There are two new options:
-I <interface> outgoing interface - for IPv6 scope or IPv4
(IPv4 advanced option; bypasses routing lookup)
-N <next_hop> set IP_NEXTHOP - requires -I option
(IPv4 advanced option; bypasses routing lookup)
The -I option has been around for a while, but it never did what people thought it did. It had no effect for IPv4. Now it does effect IPv4 so that you can select the outgoing interface for a ping, rather than relying out the routing table. This give you the ability to test whether the second interface of a multipathing group has connectivity.
The second option, -N, I have not played around with yet, but it appears to allow you to specify the next hop, effectively temporarily adding in a router for your destination. I will update this article when I've had a chance to play around with it, or if anyone else has had a chance to experiment with that option, let me know what the results were in the comments.
No comments:
Post a Comment