Brocade Virtual ADX Installation and Deployment Guide (Supporting ADX v03.1.00) - Manual (Page 52)

The virtual interfaces of VMs correspond to ovs-ports and are named vif1.1, vif1.2, vif2.1 etc. For
example, were a virtual interface is named "vif1.2" the number "1" identifies the VM and remains the
same for all virtual interfaces belonging to a particular VM, while the number "2" identifies the interface
index within the VM.
Mapping a XenCenter Network to an ovs-bridge
Use the following OVS commands to identify the ovs-bridge corresponding to a network on the
XenCenter GUI:
1. The following command takes the Network name specified in the XenCenter GUI as input and lists
the network uuid.
[root@xenserver ~]# xe network-list name-label=<network-name>
2. Input the network uuid into the following command to list the ovs-bridge corresponding to the
XenCenter GUI Network.
[root@xenserver ~]# ovs-vsctl -- --columns=name find interface external_ids:xs-
network-uuid=<network uuid>
Mapping XenCenter VM Virtual Interfaces to ovs-ports
Use the following OVS commands to identify the ovs-ports corresponding to the Brocade Virtual ADX
VM’s virtual interfaces created on the XenCenter GUI.
1. The following command takes the VM name specified on the XenCenter GUI as input and lists the
VM’s uuid.
[root@xenserver ~]# xe vm-list name-label=sivadx-centos-xvda | grep uuid
2. Input the VM uuid into the following command to list the ovs-ports corresponding to Brocade Virtual
ADX Virtual Interfaces configured on the XenCenter GUI
[root@xenserver ~]# ovs-vsctl -- --columns=name find interface external_ids:xs-vm-
uuid=<VM uuid>
Configuring VLANs
Once you have identified the ovs-bridge and ovs-port mappings, you can configure VLANs on ovs-
ports corresponding to the Brocade Virtual ADX data ports. OVS supports the following VLAN modes
on ovs-ports:
• trunk - a trunk port carries packets on one or more specified VLANs. A packet that ingresses on a
trunk port is in the VLAN specified in its 802.1Q header or VLAN 0 if the packet has no 802.1Q
header. A packet that egresses through a trunk port will have an 802.1Q header if it has a non-zero
VLAN ID. Any packet that ingresses on a trunk port tagged with a VLAN that the port does not trunk
is dropped.
• access - an access port carries packets on exactly one specified VLAN. Packets egressing on an
access port do not have an 802.1Q header. Any packet with an 802.1Q header and a non-zero
VLAN ID that ingresses on an access port is dropped, regardless of whether the VLAN ID in the
header is the access port’s VLAN ID.
• native-tagged - a native-tagged port resembles a trunk port, with the exception that a packet without
an 802.1Q header that ingresses on a native-tagged port is in the ‘‘native VLAN’’ (specified in the
tag field).
• native-untagged - a native-untagged port resembles a native-tagged port, with the exception that a
packet that egresses on a native-untagged port in the native VLAN will not have an 802.1Q header.
Mapping a XenCenter Network to an ovs-bridge
52 Brocade Virtual ADX Installation and Deployment Guide
53-1003241-01