HP Virtual Connect 4Gb Fibre Channel Module for c-Class BladeSystem - Manual (Page 14)

HP Virtual Connect Manager 14
Pop-up windows must be enabled for certain features to function correctly. Check the browser settings
to make sure pop-up blockers are not enabled before running the application.
• Cookies
Cookies must be enabled for certain features to function correctly. Check your browser settings to make
sure cookies are enabled before running the application.
Accessing HP Virtual Connect Manager
Access to VCM occurs over the same Ethernet connection used to access the enclosure Onboard
Administrator and server blade iLO connections.
Access VCM in one of the following ways:
• If the management network uses dynamic DNS, locate the Default Network Settings label on the
primary VC-Enet module, and then type the DNS name into the address field of the web browser.
If the management network does not use dynamic DNS, use the Onboard Administrator to access VCM.
• Log on to the enclosure Onboard Administrator. From the rack overview screen, select the Virtual
Connect Manager link from the left navigation tree.
• Log on to the enclosure Onboard Administrator. To display the Interconnect Bays summary screen,
select Interconnect Bays in the left navigation tree of the Onboard Administrator user interface. Select
the Management URL link for the primary VC-Enet module.
VCM typically operates on the primary VC-Enet module unless that module becomes unavailable,
causing a failover to the backup VC-Enet module. If you cannot connect to the primary VC-Enet module,
try connecting to the management URL for the backup VC-Enet module.
• Access the VCM CLI remotely through an SSH session by connecting to the VC-Enet module
management IP address.
In a multi-enclosure VC domain, VCM runs on the primary module in the primary enclosure. If both the
primary and backup modules in the primary enclosure fail, are powered off, or are removed, VCM is not
accessible.