User guide

HP Virtual Connect for Cisco Network Administrators (version 4.x)
Document Number: C01386629 Date: January 2014
page 19
Virtual Connect Manager
The purpose of the Virtual Connect Manager (VCM) is to function as the single point
of administration for the Virtual Connect Domain. This means that all aspects of configuring,
managing, and monitoring the Virtual Connect Domain and all VC Ethernet and Fiber Channel
modules is provided by VCM.
VCM runs embedded on either the HP 10/10D or the HP Flex Fabric Ethernet modules when
installed in interconnect any side by side interconnect bay. VCM utilizes its own CPU, memory,
and flash resources onboard the VC Ethernet modules.
VCM runs in High Availability mode when Virtual Connect Ethernet modules are installed in
both side by side interconnect bay. By default, the Virtual Connect Ethernet module in odd
interconnect bay will be the active VCM and the Virtual Connect Ethernet module in even
interconnect bay will be the standby VCM. The Virtual Connect Domain configuration is check
pointed from the active VCM to the standby whenever configuration changes are made. In this way, if
the Virtual Connect Ethernet module functioning as the active VCM fails, the standby Ethernet
module can assume the role of active VCM without loss of Virtual Connect Domain configuration
settings.
Note:
Even though VCM is only active on a single Virtual Connect Ethernet module at one time, this has
nothing to do with the Ethernet connectivity functionality provided by the Virtual Connect Ethernet
modules. All Virtual Connect modules in the domain are functionally active at all times and every
port on every Virtual Connect module can be configured to actively carry network traffic at the
same time.
Virtual Connect Manager User Interfaces
Virtual Connect Manager (VCM) provides three user interfaces for managing and monitoring the
Virtual Connect Domain – Web, SSH CLI, and SNMP.
The Web and SSH CLI interfaces provide nearly an identical set of features used to manage the
Virtual Connect Domain. For more information on the specifics of these interfaces, please consult the
Virtual Connect Users Guide: (www.hp.com/go/bladesystem/documentation).
VC’s SNMP implementation allows the administrator to monitor the Virtual Connect domain and
associated modules. The SNMP configuration is controlled by the Virtual Connect Manager and
applies to all modules in the VC domain. The SNMP agent software module residing on a primary
module provides access to managed information using SNMP protocol. The managed information is
presented as a hierarchical database called a MIB. Each element of the managed information is
identified by a unique identifier called Object ID. Basic SNMP support is provided for VC-Enet
modules.
VC MIB Support