shut/no shut on vethernet interfaces?

[Dragomir]

can i do a shut and no shut on vethernet interfaces in ucs? I need to torubleshoot an issue why a vm is failing to pxe boot or cannot communicate to the pe/tftp server on one blade while its working on another in the same chassis

[balaji.bandi]

We need more information, is this UCS connected to FI ? then you shoult be able touse UCS Manager shutdown and no shut the port.

[Kirk J]

If it's UCSM integrated, you can disable/re-enable the vnic in the equipment view (there is also a 'reset' that would accomplish the same).  Are you trying force pinning for that host out one specific side of the FIs?  You could also adjust the vswitch/dVS teaming, and disable the vmnic out the side in question at the vmware level.

If all else fails, take a capture at vmware level to see what is/isn't responding:

pktcap-uw --uplink vmnicX

https://kb.vmware.com/s/article/2051814

Also, confirm the vmnic for that physical host MAC address matches the vnic mac address in service profile, to confirm the vlans you think are programmed for the vnic/veth are really the interface you think it is at the vmware vmnic level assignment level.

It would also be helpful to understand the L2 connectivity between guestVM and the PXE/tftp server...  Perhaps your vnic/VMnic disabling can force connectivity such that both guestVM/and ESXi host,,, and the PXE server are pinned to the same FI (this assumes your PXE server is hosted in same UCSM), as this would avoid northbound switching.

Kirk...