• Firmware Update
• Add/remove/reset server blades or Onboard Administrator (OA) modules
• Retrieve any VC Ethernet module status and state information (e.g. stacking links, port statistics, etc.)
• Add/edit/copy/delete/assign Server Profile
• Add/edit/delete VC Network
• Configure Port Mirroring
• Restore Domain Configuration
• Change SNMP Settings
• Change Advanced Ethernet Settings

1. Directory Server Settings – If a DNS name is configured for the Directory Server Address then it will no longer be resolved. The IP address will need to be configured as the Directory Server Address.
2. SNMP Trap Destination – If a DNS name is configured for the SNMP Trap Destination then it will no longer be resolved. The IP address will need to be configured as the SNMP Trap Destination.
3. From the VCM CLI – Any URL targets provided to save backup configuration or support dump will need to use IP address and not DNS name.

1. Log into the Onboard Administrator and select Enclosure Settings > Enclosure Bay IP Addressing.
2. Select the “Interconnect Bays” tab and remove DNS server IP address entries from the bays that include VC Ethernet Modules and click Apply.
3. Within 5 minutes, the DNS settings for the modules should update and normal module communication will be restored.
4. It is important that no VC domain changes are made until the following step is fully completed.
5. From the VCM GUI, select “Tools” => “Reset Virtual Connect Manager.” This will force resynchronization of the modules if not synchronized in Step 3 above.IMPORTANT : If the NO_COMM condition was present or detected during one of the VCM administrative update tasks (listed in the DESCRIPTION section above), VCM may automatically resynchronize the modules, which would create a temporary VC domain-wide network outage during VC module initialization in either Step 3 or Step 5 above (but not both). Outage time will vary depending on the size of the VC domain.

1. If relying on Dynamic DNS updates for iLO, the OA firmware version must be updated to at least OA FW 3.11 before proceeding with the next step, otherwise iLO will only be reachable by IP address and there may be other ramifications to iLO LDAP Authentication.
2. In the OA, in Enclosure Bay IP Addressing, Select the “Interconnect Bays” tab and remove the DNS server IP address entries from the “Shared Interconnect Settings.” Click Apply.
3. In the OA, in Enclosure Bay IP Addressing, Select the “Device Bays” tab and remove DNS server IP address entries from the “Shared Interconnect Settings” and click Apply.
4. Within 5 minutes, the DNS settings for the modules should update and normal module communication will be restored.
5. It is important that no VC domain changes are made until the following step is fully completed.
6. From the VCM GUI, select “Tools” => “Reset Virtual Connect Manager.” This will force resynchronization of the modules if not synchronized in Step 3 above.IMPORTANT : If the NO_COMM condition was present or detected during one of the VCM administrative update tasks (listed in the DESCRIPTION section above), VCM may automatically resynchronize the modules, which would create a temporary VC domain-wide network outage during VC module initialization in either Step 4 or Step 6 above (but not both). Outage time will vary depending on the size of the VC domain.

1. On the External DHCP Scope, create an exclusion range of IP addresses (preferably only the VC Ethernet module addresses). This exclusion range needs to be configured within EBIPA on the OA.
2. In the OA, in Enclosure Bay IP Addressing, select the “Interconnect Bays” tab and configure the IP Addresses that were excluded in Step 1 above for bays that contain VC Ethernet modules. Do not configure DNS Server entries. Click Apply.
3. It is important that no VC domain changes are made until the following steps are fully completed.
4. Reboot the standby and primary VC modules to force them to use the new EBIPA lease. In a redundant design, the modules should be rebooted serially to mitigate downtime.

IMPORTANT : If the NO_COMM condition was present or detected during one of the VCM administrative update tasks (listed in the DESCRIPTION section above), VCM may automatically resynchronize the modules, which would create a temporary VC domain-wide network outage during VC module initialization. Outage time will vary depending on the size of the VC domain.