API Guide

OS10(config-if-eth1/1/1)# no switchport access vlan
4. Assign the interface to the controller.
OS10(config-if-eth1/1/1)# nve-controller
To view the controller information and the ports the controller manages, use the show nve controller command.
OS10# show nve controller
Management IP : 10.16.140.29/16
Gateway IP : 55.55.5.5
Max Backoff : 1000
Configured Controller : 10.16.140.172:6640 ssl (connected)
Controller Cluster
IP Port Protocol Connected State Max-Backoff
10.16.140.173 6640 ssl true ACTIVE 1000
10.16.140.171 6640 ssl false BACKOFF 1000
10.16.140.172 6640 ssl true ACTIVE 1000
NVE Controller Ports
ethernet1/1/1:1
ethernet1/1/15
Service Nodes
In an NSX-provisioned VXLAN environment, service nodes replicate L2 broadcast, unknown-unicast, and multicast (BUM) traffic
that enter an OS10 VTEP to all other VTEPs. For the service node replication of BUM traffic to work, you need IP connectivity
between the service nodes and the VTEP, so that the BUM traffic from a VTEP reaches the other remote VTEPs via a VXLAN
overlay through the service nodes. The NSX controller manages a cluster of service nodes and sends the IP addresses of the
nodes to the VTEP through OVSDB protocol. The service node cluster provides redundancy, and also facilitates load balancing
of BUM traffic across service nodes.
The following shows BUM traffic replication in the controller-provisioned VXLAN environment:
Since VTEP relies on service nodes to replicate BUM traffic, we need a mechanism to monitor the connectivity between the
VTEP and the service nodes. BFD can be used to monitor the connectivity between the VTEP and service nodes, and detects
failures. The NSX controller provides parameters, such as the minimum TX and RX interval, and the multiplier, to initiate the BFD
VXLAN
991