Configuring Ports for Fabric Communication


Netvisor One vFlows used to match fabric traffic do so based on the packet protocol, TCP or UDP, plus the Layer 4 destination port. That means any existing TCP or UDP traffic that happens to use the same Layer 4 destination port matches the vFlows.


You can now configure a port range for TCP or UDP traffic in order to avoid traffic conflicts with existing TCP or UDP traffic.


A new command allows this functionality:


CLI (network-admin@Spine1) > fabric-comm-ports-modify


range-start

Specify a port range from 1024 to 65435.



CLI (network-admin@Spine1) > fabric-comm-port-show


switch:                          techpub-accton-2

range-start:                     23300

fabric-port:                     23399

notify-port:                     23398

proxy-port:                      23397

fabric-keepalive-port:           23394

filesystem-replication-port:     23392

cluster-traffic-forwarding-port: 23391

vport-statistics-port:           23390

l2-encap-port:                   23389

igmp-encap-port:                 23388

icmpv6-encap-port:               23387

arp-encap-port:                  23386

cluster-analytics-port:          23385

 


When you modify the port range, you must do so on each node in the fabric which temporarily interrupts fabric communication until you configure each node with the same port range. There is no forwarded traffic loss if the interruption is brief. Since application of this command prevents communication with other nodes, you must log in to each node directly and separately to apply the command.