HP Insight Management-Software - Manual (Page 120)

Resolving removal of the last VC Domain from a VC Domain Group
If existing unassigned profiles targeted to be deleted from a VC Domain Group reaches 1600
addresses (MAC or WWN) and the last VC Domain has lost connection with VCEM, the last
domain will not be deleted. Select one of the following options to resolve this situation:
•
Re-establish the VC Domain connection and try to remove the last VC Domain from VC Domain
Group again.
•
Delete the remaining unassigned server profiles from the VC Domain Group and then remove
the last VC Domain from the VC Domain Group.
VC Domain Groups and VC Domain Management
•
At times the network port speed configured as 10 Gb on a VC Domain that supports 10 Gb
incorrectly displays as Auto on a VC Domain that does not support 10 Gb.
This situation occurs when the Virtual Connect Manager user interface on the VC Domain
without the SFP-SR connector displays the network speed as Auto.
The Auto value appears only on the Virtual Connect Manager user interface. When VCEM
attempts to capture the network configuration from Virtual Connect Manager, the information
returned is 10Gb and not Auto.
To resolve this issue:
1.
Access the Virtual Connect Manager user interface on the VC Domain that does not have
the SFP-SR connector.
2. Edit the network with the incorrectly labeled Auto port speed to use another port speed
value (for example, 1 Gb).
3. Save the edits.
4. Edit the network again, and set the port speed to Auto.
•
If, after performing data migration, you are running Virtual Connect Manager and try to access
a VCEM-managed VC Domain, the following error message appears:
VC Domain locked by Virtual Connect Enterprise Manager
address>.
To resolve this issue:
1.
Go to the CMS and invoke the MS-DOS command box.
2. Change the directory to the \.
3. Run either of the following CLI commands:
◦ >vcem -updatevcmdesc
◦ >vcem -uvcm
To validate that the problem has been corrected, browse to the Virtual Connect Managers
that showed the incorrect message to ensure that the correct message is displayed.
•
Using VCEM 1.40 or 6.0 to disable SNMP on Virtual Connect Manager 2.30 can result in
improper propagation of SNMP enablement to the VC Domain Group. This issue occurs if
you use either VCEM 1.40 or 6.0 to disable SNMP for VC Ethernet or Fibre Channel modules
and the following conditions exist:
◦ The VC Domain Group contains a combination of VC firmware version 2.30 and earlier
firmware such as 2.10 or 2.0x.
◦ You select a VC Domain running VC firmware 2.30, put it into VC Domain Maintenance,
and use the Virtual Connect Manager user interface to disable SNMP.
While a permanent fix will be provided in a future VC firmware release, you can resolve this
issue by performing these steps:
120 Troubleshooting VCEM