Command line interface overview, Logging on to the hp virtual connect manager gui – HP Virtual Connect 8Gb 24-port Fibre Channel Module for c-Class BladeSystem User Manual
Page 13
HP Virtual Connect Manager 13
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.
Command Line Interface overview
The VCM Command Line Interface can be used as an alternative method for administering the VCM. Using
the CLI can be useful in the following scenarios:
•
You can develop tools that utilize VCM functions for data collection and for executing provisioning and
configuration tasks.
•
When no browser is available or you prefer to use a command line interface, you can access
management data and perform configuration tasks.
•
You can batch commands using script files. These script files can be run manually or scheduled to run
automatically.
For more information, see the HP Virtual Connect Manager Command Line Interface for c-Class BladeSystem
User Guide on the Installing tab of the HP BladeSystem Technical Resources website
Logging on to the HP Virtual Connect Manager GUI
Log on using the user name (Administrator) and password.
You can optionally specify the authentication method or VCM role at logon.
To specify the authentication method (local, ldap, radius, tacacs), enter the authentication method followed
by a colon before the user name. For example, ldap:user1.
To specify the VCM role (domain, network, server, storage), enter the role followed by a colon before the
user name. For example, network:user1.
For more information on authentication methods and VCM roles, see "Virtual Connect users and roles (on
)."