Support for Fabric Guard


Currently, Netvisor One detects a Layer 2 loop using by STP, LLDP, or loop detect code. However if there is a third party device connect to a Pluribus Networks switch which consumes LLDP such as a hypervisor vSwitch, and the port is configured as an edge port, Netvisor One cannot detect loops on the network.


If a port is configured as fabric-guard port, Netvisor One triggers sending global discovery multicast packets on this port after the port is physically up and in an adjacency wait state. If a port with fabric-guard configuration receives a global discovery packet, Netvisor One disables the port in the same way LLDP disables the port when receiving messages from the same switch.


In order to re-enable the port once the loop is fixed, you must manually enable the port using the command, port-config-modify port port-number enable.


To enable fabric guard, use the following syntax:


CLI (network-admin@Leaf1) > port-config-modify port port-number fabric-guard

 


To disable fabric guard, use the following syntax:


CLI (network-admin@Leaf1) > port-config-modify port port-number no-fabric-guard