Software Owner manual

• To remove the account and release the VC Domain from VCEM control, from the VCM
command prompt, enter
remove external-manager Username=xyz
mactype=<Factory-Default/User-Defined> MacStart=<> MacEnd=<>
wwnType=<Factory-Default/User-Defined> WwnStart=<> WwnEnd=<>
serverIdType=<Factory-Default/User-Defined> serverIdStart=<>
serverIdEnd=<>
NOTE: The “-quiet” option is used to suppress user confirmation prompts. This option is useful
for scripting operations. This option is available or later for the disable account, remove the
account, and release ranges commands.
For more information, see the HP Virtual Connect Manager Command Line Interface User Guide.
VC Domain displays Configuration Mismatch status
If the VCEM data does not match the data from the VC Domain, then the Configuration Mismatch
icon appears. This might happen when either the user suspends the external manager lock and
then modifies the VC Domain, or adds or removes VC Modules from rear-enclosure interconnect
bays.
To correct this issue, see “Resynchronizing a VC Domain with Configuration Mismatch” (page 73).
VC Domain displays Connectivity failure status
The Connectivity failure icon might appear if any of the following occur:
• Connection timeout, network problems, Virtual Connect Ethernet Modules physically not
available, or enclosure problem
• VCM failover
• VC Domain firmware update
• Virtual Connect Ethernet Module IP address change.
To correct this issue, perform any of the following:
• Ethernet VC modules are not physically available or there is a connection timeout or a network
problems between VCEM and VC Ethernet modules.
To correct this issue, verify the Ethernet VC Modules are still available and that there are no
network-related issues with the VCM. From the command line at the VCEM server, ping the
VC Domain IP.
For information on enclosure problems, see “Enclosure has a hardware failure and must be
replaced” (page 174).
• In a redundant environment, the failover between active and standby VC module is taking
place.
To correct this issue:
1. Verify that the failover between the active and standby VC module is taking place.
2. Wait a few minutes until the failover completes, and then try again.
3. Log into VCM (https://<VCDomain_IP>). A status of Active Virtual Connect Manager not
at this IP address might appear.
4. You must also rediscover the Onboard Administrator related to this VC Domain again by
selecting Systems Insight Manager menu Options→Identify System or Options→Discovery.
• Verify firmware update is in progress and wait a few minutes until the update is completed.
Log into the VCM (https://<VCDomain_IP>), and verify the VC Domain firmware status, click
Domain Settings→Firmware Management.
168 Troubleshooting VCEM