vCenter guidelines and restrictions
Follow these guidelines and restrictions when configuring vCenter:
- Special characters in the port group names are replaced with the URL-encoded values.
- Standard port groups with the same name that reside in different ESX/ESXi hosts must have identical VLAN settings across all hosts.
- For all vCenter port groups, Network OS automatically creates a port profile with the following format: auto-vcenter_name-datacenter_ID-port-group-name. User editing of these auto port groups is not supported.
- Network OS supports vCenter discovery that is based on events.
- Network OS supports LLDP and QoS (IEEE 8021.p) for distributed virtual switches (dvSwitches).
- Using port-profile names fewer than 63 characters has been shown to conserve CPU resources.
- CDP/LLDP-receiving interface ports must not have any conflicting configurations on the interface that prevent them from being in a port-profiled mode.
- An interface is prevented from becoming a port-profile-port only when conflicting switchport, QoS, and security configurations reside on the interface. An FCoE configuration on the interface does not prevent a port-profile-port configuration.
- Before configuring a vCenter in the fabric, remove all the manually created port profiles that have vCenter inventory MAC associations.
- Up to four vCenter configurations are supported per fabric, with support for multiple data centers.
- Duplicate vCenter asset values are not supported, such as duplicate MAC addresses and duplicate Host names.
NOTERefer to the Release Notes for the number of port groups supported per platform, as well as other related information.