If I execute “link state down” for particular interface (on one side of the link), why is neighboring port (on the other switch) still showing up?
Is this in a virtual switch such as one found in NV Air or on a VX virtual machine?
If so, the reason is that there is not a physical wire connecting the two VMs and instead a virtual link which does not represent line protocol at L1/L2 in the same way as a physical link.
OK, so it is a feature then :( Thanks for swift response!
Do you know if we can expect improvements of current behavior? I’m asking because when I’m using virtualized environment provided by other networking vendor, it works as expected (i.e. as I’m using physical devices). I’m hoping it is already on the road map and Nvidia Engineering team has a date when it will be implemented.
Based on my experience, to get the clear answer on it, you should get your regional sales representative or Solution Architect engineer.
To be specific for the context of this question – are we talking about using VX in your own hypervisor or are we talking about NVIDIA Air?
(The answer to how we implement a solution for this differs depending on where we’re talking about the fix)
I did mention Nvidia Air in the title; now when you mentioned differences between NV Air and VX I would suggest to cover both, if possible.