HP Insight Management-Software User Manual
Page 106
•
Verify firmware update is in progress and wait a few minutes until the update is completed.
Log into the Virtual Connect Manager (https://
firmware status, click Domain Settings
→Firmware Management.
•
Run an Systems Insight Manager discovery to identify the new VC Domain IP address and
perform the operation again.
If you perform an operation that changes the VC Domain status to Connectivity failure, VCEM
will check the connectivity using the information from Systems Insight Manager nodes after
the operation completes.
•
Remove the VC Domain from the VC Domain Group, and run the Systems Insight Manager
discovery task to identify the new VC Domain IP address.
Break the external manager lock, and then release these MAC and WWN address ranges
as follows:
1.
Telnet in to the Virtual Connect Manager using an SSH connection such as SSH
Administrator@xxx.xxx.xxx.xxx, where xxx.xxx.xxx.xxx is the VC Domain IP address.
2.
To determine the user name of the external manager account, from the Virtual Connect
Manager command prompt, enter show external-manager. For this example, assume
the user name returned was xyz.
3.
To disable the account, from the Virtual Connect Manager command prompt, enter set
external-manager Username=xyz Enabled=false
.
If the VC Domain firmware is 2.1x or later, perform the following:
•
To remove the account and release the VC Domain from VCEM control, from the Virtual
Connect Manager command prompt, enter:
remove external-manager Username=xyz
mactype=
wwnType=
serverIdType=
serverIdEnd=<>
NOTE:
The option “-quiet” is available to suppress user confirmation prompts. This
option is useful for scripting operations. This option is available for VC firmware 2.1x or
later for the disable account, remove the account, and release ranges commands.
Cannot resynchronize VC Domain that is in Configuration Mismatch state
Attempting to resynchronize a VC Domain that is in Configuration Mismatch results in a failed job,
and the following message appears:
Unable to import the MAC, WWN or VSN addresses. Possible reasons include
1) Address is being used in VCEM.
2) Address conflicts with an existing Exclusion Range.
3) Address does not fall within the defined VCEM Global Range.
To identify why the issue occurred, consider that both VC and VCEM use two MAC addresses for
each Ethernet network connection and two WWN addresses for each Fibre Channel connection.
However, only one of these addresses appears in the user interface. When checking if a server
profile is using an address, you must consider both the displayed address and the hidden address.
When considering the hidden addresses, add 1 to the addresses that are being displayed. For
example, if a profile is using two Ethernet connections with MAC addresses 00-21-5A-9B-00-00
and 00-21-5A-9B-00-02 then the hidden addresses will be 00-21-5A-9B-00-01 and
00-21-5A-9B-00-03. In this example, the profile will be using four MAC addresses from
00-21-5A-9B-00-00 to 00-21-5A-9B-00-03.
106 Troubleshooting VCEM