Specifications

HP Virtual Connect for Cisco Network Administrators (version 1.2x) page 11
identified by a unique identifier called Object ID. Basic SNMP support is provided for VC-Enet
modules.
The VC-Enet modules support the applicable groups of the following SNMP MIBs:
• Compaq Host MIB
• Compaq System Info MIB
• RFC 3418 SNMPv2-MIB
• RFC 2863 IF-MIB
• RFC 4188 BRIDGE-MIB
The VC-Enet modules support the following SNMP traps:
• cpqHoSWRunningStatusChangeTrap from CPQ-HOST MIB
• coldStart trapfrom SNMPv2-MIB
Virtual Connect Port Descriptions
The three types of ports are VC downlinks, VC uplinks, and internal cross-connects:
• VC Downlinks
o Non-visible ports that are directly connected to server NIC ports through the
enclosure midplane.
o Only role is to provide connectivity to directly connected blade server NICs
• VC Uplinks
o Visible ports on the VC-Enet module faceplate that provide external connectivity for
the VC domain.
o Roles include stacking link, network analyzer port (see Port Monitoring), normal mode
(providing external connectivity for one or more vNets or Shared Uplink Sets)
• Internal cross-connects
o A non-visible port that interconnects two horizontally adjacent VC-Enet modules
o Only role is to function as a stacking link
Overview of Virtual Connect Ethernet Connectivity
While Virtual Connect provides many features, its primary purpose is to provide internal and external
network connectivity for blade servers in a c-Class enclosure. For Ethernet, Virtual Connect
accomplishes this purpose by bridging together, at layer 2, VC downlink ports (server NICs) with
other VC downlink ports and with VC uplink ports connected to an external switched network.
Virtual Connect provides the administrator with control over which uplinks and which downlinks are
assigned to the same layer 2 network through the use of Virtual Connect Networks (vNets or Shared
Uplink Sets).
A VC Administrator defines vNets and, optionally, assigns VC uplinks to the vNets to provide external
network connectivity. Once the vNets are defined, they are available for the Server Administrator to
assign to server NIC ports. When a Server Admin moves a server profile from one server bay to
another, the vNet assignments and, if used, managed MAC addresses (see section entitled “VC
Managed MAC Addresses) are moved with the profile. This allows the server administrator to easily
move the “Ethernet connectivity profile” for a server from one bay to another without requiring the
assistance of the Network Administrator.
A vNet can be used to bridge together multiple VC downlinks for an internal-to-the-enclosure-only
network or a vNet can be used to bridge together one or more VC downlinks with one or more VC
uplinks to provide external network connectivity for the blade servers in the enclosure. A vNet
cannot be used to bridge together multiple VC uplinks to provide connectivity between two