Cisco introduced Consistent Device Naming in Cisco UCS Manager Release 2.2(4).
In the past I could saw that VMware vNIC placement order not adhered to Cisco UCS configuration. But his issue will not be seen in the latest ESXi updates – ESXi 6.5 U2 and ESXi 6.7 U1.
When there is no mechanism for the Operating System to label Ethernet interfaces in a consistent manner. It becomes difficult to manage network connections with server configuration changes.
Allows Ethernet interfaces to be named in a consistent manner. This makes Ethernet interface names more persistent when adapter or other configuration changes are made.
To configure CDN for a vNIC, do the following:
- Enable consistent device naming in the BIOS policy.
- Associate the BIOS policy with a service profile.
- Configure consistent naming for a vNIC.
- Guidelines and Limitations for Consistent Device Naming
- Configuring Consistent Device Naming in a BIOS Policy
- Configuring a CDN Name for a vNIC
This makes Ethernet interface names more uniform, easy to identify, and persistent when adapter or other configuration changes are made.
set consistent-device-name-control cdn-name
Whether consistent device naming is enabled or not. This can be one of the following:
- enabled—Consistent device naming is enabled for the BIOS policy. This enables Ethernet interfaces to be named consistently.
- disabled—Consistent device naming is disabled for the BIOS policy.
- platform-default—The BIOS uses the value for this attribute contained in the BIOS defaults for the server type and vendor.