Configuring Layer 4 Ports for Fabric Communication


Netvisor ONE receives fabric communication messages by using system vFlow entries to match traffic flows based on the IP packet protocol, TCP or UDP, and Layer 4 destination port.


Any existing TCP or UDP traffic across the network using the same Layer 4 destination port may match the vFlows and may potentially cause conflicts.


Table 1: Default Port Values for Netvisor ONE


Message Type

Layer 4 Port

fabric

23399

notify

23398

proxy

23397

fabric-keepalive

23394

filesystem-replication

23392

cluster-traffic-forwarding

23391

vport-statistics

23390

l2-encap

23389

igmp-encap

23388

icmpv6-encap

23387

arp-encap

23386

cluster-analytics

23385



To avoid conflicts with generic TCP or UDP traffic, configure an alternate Layer 4 port range for special messages using the command:


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


You can specify the value for the starting point of the range:


range-start 1024..65435 port range start


To display the current starting point and range values, use the following command:


CLI (network-admin@switch) > fabric-comm-ports-show


switch:                                pnswitch2

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 configure each node in the fabric individually.


This change temporarily interrupts fabric communication until you have completed the configuration of each node with the same port range.


There is no loss of switched traffic if the interruption is brief.


Because application of this command prevents communication with other nodes, you must log into each node directly and separately apply the fabric-comm-ports-modify command.