Monitoring Bond Interfaces in DPDK Enabled Devices
Starting with Contrail Networking Release 1910, you can use the Contrail Command user interface (UI) to monitor the status of primary and secondary devices that are members of a bond interface. This feature is available for device systems configured with Data Plane Development Kit (DPDK). In releases prior to release 1910, you could only see a bond interface in the Contrail Command UI. In release 1910, you can view the details and receive notifications about the status of the primary as well as secondary devices in the bond interface.
To monitor the members in a bond interface, perform the following steps:
- Click Infrastructure>Cluster.
The Overview page is displayed.
- Click Cluster Nodes. The Cluster AIO Nodes page is displayed.
Click Compute Nodes tab. A list of nodes is displayed.
- Click any node to view the Node Details. The Summary tab is displayed.
- Click Interfaces tab. A list of interfaces
deployed in the node is displayed.
Click on a bond interface to view and monitor the bond interface. See Figure 1.
Figure 1: Members of the Bond Interface - Click Alarms tab. A list of alarms is displayed.
This tab overrides the old alarms and shows you the latest alarm generated when the primary or secondary device in the bond interface goes DOWN. This indicates that the member has become inactive. See Figure 2.
Figure 2: Alarms Generated by Bond Interface Members Note In a multi-node setup, when the primary interface goes down in a DPDK enabled device, the Contrail Command UI cannot display the status as the connection between the controller and the primary interface is inactive. The Contrail Command UI obtains the previous status from the cache and displays it.
You can also use vif—list command on the CLI to view the details of the bond interface members.
Executing the vif—list command gives you the following output when all interface members are UP:
vif0/0 PMD: 0 (Speed 1000, Duplex 1) Type:Physical HWaddr:9e:b1:2a:68:e8:58 IPaddr:0.0.0.0 Vrf:0 Mcast Vrf:65535 Flags:XTcL3L2VpDpdk QOS:0 Ref:19 RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Fabric Interface: eth_bond_bond0 Status: UP Driver: net_bonding Slave Interface(1): 0000:04:00.0 Status: UP Driver: net_ixgbe Slave Interface(2): 0000:04:00.1 Status: UP Driver: net_ixgbe RX packets:0 bytes:0 errors:0 TX packets:5 bytes:430 errors:0 Drops:0 TX port packets:5 errors:0 TX device packets:5 bytes:450 errors:0
Executing the vif—list command gives you the following output when all interface members are DOWN:
vif0/0 PMD: 0 (Speed 1000, Duplex 1) Type:Physical HWaddr:9e:b1:2a:68:e8:58 IPaddr:0.0.0.0 Vrf:0 Mcast Vrf:65535 Flags:XTcL3L2VpDpdk QOS:0 Ref:19 RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Fabric Interface: eth_bond_bond0 Status: DOWN Driver: net_bonding Slave Interface(1): 0000:04:00.0 Status: DOWN Driver: net_ixgbe Slave Interface(2): 0000:04:00.1 Status: DOWN Driver: net_ixgbe RX packets:0 bytes:0 errors:0 TX packets:5 bytes:430 errors:0 Drops:0 TX port packets:5 errors:0 TX device packets:5 bytes:450 errors:0
Executing the vif—list command gives you the following output when bond interface is not configured and there are no secondary devices:
vif0/0 PMD: 0 (Speed 1000, Duplex 1) Type:Physical HWaddr:9e:b1:2a:68:e8:58 IPaddr:0.0.0.0 Vrf:0 Mcast Vrf:65535 Flags:XTcL3L2VpDpdk QOS:0 Ref:19 RX queue errors to lcore 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 Fabric Interface: 0000:04:00.0 Status: DOWN Driver: net_ixgbe RX packets:0 bytes:0 errors:0 TX packets:5 bytes:430 errors:0 Drops:0 TX port packets:5 errors:0 TX device packets:5 bytes:450 errors:0