Fabric Over Management Interface
You can now configure fabric communication run over either the management interface or the in-band interface. Since fabric communication over the in-band interface can be disrupted due to STP, ports flapping, and other factors, fabric communication over management provides a more consistent configuration.
If you create a fabric with the management interface, any nodes joining the fabric inherit this setting. All nodes in a single fabric all run on the same network type. You cannot run a mixed configuration of management and in-band interfaces. Fabrics advertised on an incompatible network are not available for when you issue the fabric-join command. This keeps a switch from joining an incompatible fabric.
If the fabric is configured on the management interface, all fabric-communication is on the management network, except for the following:
- Cluster synchronization-related traffic such as VLAG synchronizations and forwarded STP packets.
- Cluster keep-alive packets on the fabric
- Fabric keep-alive packets and global-discovery packets because both run on management and in-band interfaces.
Two new states are added to the state field of fabric-node-show:
CLI (network-admin@switch) > fabric-node-show ?
[state offline|online|in-band-only-online|mgmt-only-online| fabric-joined|eula-required|setup-required|fabric-required| fresh-install]
Since there are now two networks for Netvisor One to monitor for connectivity, online means both management and in-band are reachable; in-band-only-online means the switch is only reachable through the in-band network; mgmt-only-online means it is only reachable through the management network; and offline means the switch is not reachable on either network.
Monitoring and reporting are reported on both the management and in-band network connectivity.