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 server profiles 198
If the selected network is part of a shared uplink set, it has an associated external VLAN mapping. This
external VLAN is used to pre-populate the server-assigned VLAN entry to maintain consistency throughout the
VC domain. However, multiple networks on different shared uplink sets can have the same external VLAN
mapping. If those networks are selected for the same server port, you must edit the server VLAN to ensure all
VLANs are unique for each server port.
Server VLAN mappings are not linked to the uplink VLAN mappings. If a pre-populated server VLAN
mapping is accepted, and later the uplink VLAN mapping is changed, the changes are not propagated to the
server side.
VLAN ID mapping guidelines
• For each server port, all VLAN mappings must be unique. When the 'Force same VLAN mappings as
Shared Uplink Sets' option is selected, this setting is handled automatically because all networks within
a shared uplink set must have unique VLAN IDs. If the 'Force same VLAN mappings as Shared Uplink
Sets' option is not selected, then each network can only be mapped once (including untagged).
• Different server VLANs can be mapped to the same network between two different server ports. For
example, in server port 1, server VLAN 100 maps to the Purple network. In port 2, server VLAN 200
also maps to the Purple network. The result is that these different server VLANs can communicate with
each other directly, and a broadcast frame on VLAN 100 from server port 1 is sent into the VC Domain
and comes out to VLAN 200 on server port 2. This behavior extends to any number of different server
VLANs mapped to the same vNet in any given VC Domain.
• The same server VLAN can be mapped to two different networks. This action has a similar but opposite
effect to the above scenario. For example, server VLAN 300 is mapped to the Green network on server
port 1, but mapped to the Red network on server port 2. This mapping means that server VLAN 300 is
split into separate broadcast domains for different server ports.
• A network can only be mapped to a physical port once. Any additional mappings created by the server
profile result in an error.