HP Virtual Connect for c-Class BladeSystem Version 4.01 User Guide
Table Of Contents
- HP Virtual Connect for c-Class BladeSystem Version 4.01 User Guide
 - Abstract
 - Notice
 - Contents
 - Introduction
 - HP Virtual Connect Manager
 - Virtual Connect domains
- Understanding Virtual Connect domains
 - Managing domains
 - Managing SNMP
 - Viewing the system log
 - Managing SSL configuration
 
 - HP BladeSystem c-Class enclosures
 - Virtual Connect users and roles
- Understanding VC administrative roles
 - Managing users
- Local Users screen
 - Configuring LDAP, RADIUS, and TACACS+
- Minimum requirements
 - LDAP Server Settings (LDAP Server) screen
 - LDAP Server Settings (LDAP Groups) screen
 - LDAP Server Settings (LDAP Certificate) screen
 - RADIUS Settings (RADIUS Server) screen
 - RADIUS Settings (RADIUS Groups) screen
 - TACACS+ Settings screen
 - Role Management (Role Authentication Order) screen
 - Role Management (Role Operations) screen
 
 
 
 - Virtual Connect networks
- Understanding networks and shared uplink sets
 - Managing networks
- Network Access Groups screen
 - Define Network Access Group screen
 - Ethernet Settings (Port Monitoring) screen
 - Ethernet Settings (Advanced Settings) screen
 - Quality of Service
 - IGMP Settings (IGMP Configuration) screen
 - IGMP Settings (Multicast Filter Set) screen
 - Define Ethernet Network screen
 - Ethernet Networks (External Connections) screen
 - Ethernet Networks (Server Connections) screen
 
 - Managing shared uplink sets
 
 - Virtual Connect fabrics
 - Virtual Connect server profiles
- Understanding server profiles
 - Managing MAC, WWN, and server virtual ID settings
 - Managing server profiles
- Define Server Profile screen
- Creating FCoE HBA connections for a BL890c i4
 - Limited Ethernet connections when using HP Virtual Connect Flex-10/10D modules
 - Creating iSCSI connections
 - Flex-10 iSCSI connections
 - Define Server Profile screen (multiple enclosures)
 - Multiple network connections for a server port
 - Defining server VLAN mappings
 - Fibre Channel boot parameters
 
 - Server Profiles screen
 - Edit Server Profile screen
 - Assigning a server profile with FCoE connections to an HP ProLiant BL680c G7 Server Blade
 - Unassigning a server profile with FCoE connections to an HP ProLiant BL680c G7 Server Blade and deleting the SAN fabric
 - General requirements for adding FC or FCoE connections
 
 - Define Server Profile screen
 - Virtual Connect and Insight Control Server Deployment
 
 - Virtual Connect modules
- Firmware updates
 - Stacking Links screen
 - Throughput Statistics screen
 - Enclosure Information screen
 - Enclosure Status screen
 - Interconnect Bays Status and Summary screen
- Causes for INCOMPATIBLE status
 - Ethernet Bay Summary (General Information) screen
 - Ethernet Bay Summary (Uplink Port Information) screen
 - Ethernet Bay Summary (Server Port Information) screen
 - Ethernet Bay Summary (MAC Address Table) screen
 - Ethernet Bay Summary (IGMP Multicast Groups) screen
 - Ethernet Bay Summary (Name Server) screen
 - Ethernet Port Detailed Statistics screen
 - FC Port Detailed Statistics screen
 - FC Bay Summary screen
 - Interconnect Bay Overall Status icon definitions
 - Interconnect Bay OA Reported Status icon definitions
 - Interconnect Bay VC Status icon definitions
 - Interconnect Bay OA Communication Status icon definitions
 
 - Server Bays Summary screen
 - Server Bay Status screen
 - Port status conditions
 - Interconnect module removal and replacement
- Virtual Connect modules
 - Upgrading to an HP Virtual Connect 8Gb 24-Port FC Module
 - Upgrading to an HP Virtual Connect 8Gb 20-Port FC Module
 - Upgrading or removing an HP Virtual Connect Flex-10, HP Virtual Connect FlexFabric, or HP Virtual Connect Flex-10/10D module
 - Upgrading to an HP Virtual Connect FlexFabric module from a VC-FC module
 - Onboard Administrator modules
 
 
 - Maintenance and troubleshooting
 - Appendix: Using Virtual Connect with nPartitions
 - Support and other resources
 - Acronyms and abbreviations
 - Documentation feedback
 - Index
 
Virtual Connect networks  99 
Enhanced network loop protection detects loops on downlink ports, which can be a Flex-10 logical port or 
physical port. The feature applies to Flex-10 logical function if the Flex-10 port is operating under the control 
of DCC protocol. If DCC is not available, the feature applies to a physical downlink port. 
Enhanced network loop protection uses two methods to detect loops: 
•  It periodically injects a special probe frame into the VC domain and monitors downlink ports for the 
looped back probe frame. If this special probe frame is detected on downlink ports, the port is 
considered to cause the loop condition. 
For tunneled networks, the probe frame transmission is extended over a longer period of time 
proportional to the number of tunneled networks. The probe frames are sent on a subset of tunnels every 
second until all tunnels are serviced.  
•  It monitors and intercepts common loop detection frames used in other switches. In network 
environments where the upstream switches send loop detection frames, the VC Enet modules must 
ensure that any downlink loops do not cause these frames to be sent back to the uplink ports. Even 
though VC probe frames ensure loops are detected, there is a small time window depending on the 
probe frame transmission interval in which the loop detection frames from the external switch might loop 
through down link ports and reach uplink ports. By intercepting the external loop detection frames on 
downlinks, the possibility of triggering loop protection on the upstream switch is eliminated. When 
network loop protection is enabled, VC-Enet modules intercept the following types of loop detection 
frames: 
o  PVST+ BPDUs 
o  Procurve Loop Protect frames 
When the network loop protection feature is enabled, any probe frame or other supported loop detection 
frame received on a downlink port is considered to be causing the network loop, and the port is disabled 
immediately until an administrative action is taken. The administrative action involves resolving the loop 
condition and clearing the loop protection error condition. The "loop detected" status on a port can be 
cleared by one of the following administrative actions: 
•  Restart loop detection by issuing "reset" loop protection from the CLI or GUI 
•  Unassign all networks from the port in "loop detected" state 
The SNMP agent supports trap generation when a loop condition is detected or cleared. 
Virtual Connect provides the ability to enable or disable network loop protection. The feature is enabled by 
default and applies to all VC-Enet modules in the domain. Network loops are detected and server ports can 
be disabled even prior to any enclosure being imported. 
A loop-protect reset command resets and restarts loop detection for all server ports in a “loop-detected” error 
condition. 
Pause flood protection 
Ethernet switch interfaces use pause frame based flow control mechanisms to control data flow. When a 
pause frame is received on a flow control enabled interface, the transmit operation is stopped for the pause 
duration specified in the pause frame. All other frames destined for this interface are queued up. If another 
pause frame is received before the previous pause timer expires, the pause timer is refreshed to the new 
pause duration value. If a steady stream of pause frames is received for extended periods of time, the transmit 
queue for that interface continues to grow until all queuing resources are exhausted. This condition severely 
impacts the switch operation on other interfaces. In addition, all protocol operations on the switch are 
impacted because of the inability to transmit protocol frames. Both port pause and priority-based pause 
frames can cause the same resource exhaustion condition. 










