HP Virtual Connect Enterprise Manager Software - Manual (Page 133)

VCM shows an incorrect address for VCEM
When you log into the VCM while under VCEM control, the following message is displayed:
VC Domain locked by Virtual Connect Enterprise Manager [x.x.x.x]
The x.x.x.x in the message is an incorrect IP address for VCEM.
NOTE: The incorrect IP address does not have any impact on VCEM management of VCM.
Leaving the incorrect IP address in place does not break any VCEM operations. The IP address is
only displayed to inform you that VCM is managed by VCEM from that IP address.
To correct the IP address in VCM, complete the following steps:
1. Verify that the Windows host where VCEM is installed has its network adapters bound in the
correct order. The network adaptor handling communications with VCM should be first in the
list. If not, re-order the network adaptors so the network adaptor handling communications
with VCM is the first one in the list.
2. Open a Windows command prompt on the VCEM host and run the following command: >
Vcem –uvcm
This command will get the IP address from the system and update all of the VC
Domains that VCEM is managing with the correct IP address.
Communicating with the enclosure OA
Although VCEM may report the VC Domain status as Managed by VCEM (green status) on the VC
Domains tab, the VC Domain might be indicating a different overall status which is not displayed
in the VCEM GUI. If the VC Domain has lost communication with the enclosure OA, VCM reports
this problem by modifying the VC Domain status. However, the VCEM GUI does not directly report
it and the only indicator for the communication issue will be one of the following error messages
displayed when VCEM is trying to communicate with VCM.
•
Error message A
The operation cannot be performed because the VC Manager has lost communication with the enclosure's
[enclosure name] Onboard Administrator (OA). This communication issue could be intermittent. Go to VC
Manager to check the status of all the enclosures associated with that VC Domain. See the Virtual Connect
user guide for more information if there is a lost communication.
•
Error message B
The operation cannot be performed because the VC Manager has lost communication with the enclosure Onboard
Administrator (OA). This communication issue could be intermittent. Go to the VC Manager to check the
status of all the enclosures associated to that VC Domain. If there is a lost communication, go to Virtual
Connect user guide to get information on how to resolve this issue.
Once VCEM returns one of the error messages above, you must go to the VCM GUI and check
the VC Domain overall status to see if it is still reporting the communication problem with the
enclosure OA and then see the HP Virtual Connect Manager User Guide to resolve the situation.
MAC, WWN, and Serial Number management
You must verify that VC Domains within a network have unique MAC addresses, WWN addresses,
and serial numbers. Adding a VC Domain to a VC Domain Group or creating a VC Domain Group
does not verify that the profiles in a VC Domain use MAC or WWN addresses allocated in the
VCEM external address pool. You can overwrite the external addresses to become in use status.
To prevent external addresses from use in VCEM, add the addresses to the exclusion addresses
pool. If you plan to add the VC Domain back to VCEM, then you must also remove these addresses
from the exclusion addresses pool.
Duplicate MAC and WWN address assignments
Using VCEM 6.2 or 6.2.1 may result in duplicate MAC and WWN address assignments. This will
occur if a VC profile edit fails when removing iSCSI or FCoE connections via the VCEM Graphical
User Interface (GUI). The VCEM 6.2.2 or later upgrade contains a critical fix and is strongly
recommended to prevent this issue.
VCM shows an incorrect address for VCEM 133