By Csoto-Oracle on May 15, 2015
VNICs in states other than "UP" can cause network outages. In a virtual rack, excessive number of unused vNICs can cause performance issues.
Sometimes the steps to delete these stale VNICs can be confusing to some guys, so I am posting here simple steps to achieve it.
The syntax of the deletevnic command is:
# deletevnic connector vnic_id
Ok, but how can I know the connector and vnic_id of each stale VNIC?
Well, they are listed in Exachk.
But also, you can check what VNICs are stale by running the following command:
# showvnics|grep -i WAIT-IOA
And then you will see the vnic_id in the first column and the conector in the last column.
The output would be something like:
74 WAIT-IOA N 27ABA3F429048 rackcn02 192.168.8.2 0000 00:14:4F:FB:70:D7 13 0x8007 0A-ETH-2
30 WAIT-IOA N 5E6C3186A4361 rackcn04 192.168.8.4 0000 00:14:4F:FA:50:D4 13 0x8007 0A-ETH-3
51 WAIT-IOA N BDC7F7A61E5E0 rackcn01 192.168.8.1 0000 00:14:4F:FA:91:3F 13 0x8007 0A-ETH-3
16 WAIT-IOA N A584D5DA41538 rackcn01 192.168.8.1 0000 00:14:4F:F8:8D:84 13 0x8007 0A-ETH-4
But, as several times the VNICs are associated to compute nodes, some people may think that deleting the VNIC would affect the networking performance of the compute node.
The answer for that perfectly valid concern is that, as the vnic_id is unique, then you can safely use the deletevnic command for each one of the stale VNICs.