Deployment Guide
• The interface must be in Switchport Trunk mode.
• The interface must not be a member of any VLAN
• The interface must not be a member of a port-channel
When the above conditions are not met when assigning the interfaces to be managed by the controller, the system returns error
messages.
When the interface is assigned, you cannot:
• remove the interface from Switchport Trunk mode
• add the interface as a member of any VLAN
• remove the interface from the controller configuration if the interface has active port-scoped VLAN (Port,VLAN) pairs configured by
the controller
To assign an interface to be managed by the OVSDB controller:
1. Configure an interface from CONFIGURATION mode.
OS10(config)# interface ethernet 1/1/1
2. Configure L2 trunking in INTERFACE mode.
OS10(config-if-eth1/1/1)# switchport mode trunk
3. Configure the access VLAN assigned to a L2 trunk port in the INTERFACE mode.
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:
Controller-provisioned VXLAN
49