Page 1 HP Virtual Connect Ethernet Cookbook: Single and Multi Enclosure Domain (Stacked) Scenarios Part number 603028-003 Third edition August 2010...
Page 2: Intended Audience
© Copyright 2009,2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
Page 3: Table Of Contents
Contents Purpose .............................. 6 Introduction to Virtual Connect ....................... 7 Tunneled VLAN and Mapped VLANS ..................... 9 Chapter 1: Single Domain/Enclosure Scenarios ..................12 Overview ..............................12 Requirements ............................12 Scenario 1:1 – Simple vNet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows ............................
Page 4 Configuring Uplinks to a vNet (LACP) ..................... 62 Installation and configuration ........................64 Summary............................. 70 Results ..............................71 Scenario 1:6 – VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) – VMware ESX ........................73 Overview ..............................
Page 5 Summary............................165 Result ..............................166 Chapter 3: Multi-Enclosure (Stacking) Scenarios ................... 170 Overview ............................... 170 Requirements ............................. 170 Scenario 3:1 – Multi-Enclosure stacking, with Multiple Simple vNets, Redundant Uplinks and LACP (2 Enclosures) ..............................171 Overview ............................... 171 Requirements ............................. 171 Installation and configuration ........................
Page 6: Purpose
Purpose The purpose of this Virtual Connect Cookbook is to provide new users to Virtual Connect with a better understanding of the concepts and steps required when integrating HP BladeSystem and Virtual Connect components into an existing network. The scenarios in this Cookbook vary from simplistic to more complex while covering a range of typical building blocks to use when designing Virtual Connect solutions.
Page 7: Introduction To Virtual Connect
Introduction to Virtual Connect Virtual Connect is an industry standard-based implementation of server-edge virtualization. It puts an abstraction layer between the servers and the external networks so the LAN and SAN see a pool of servers rather than individual servers (Figure 1).
Page 8 The following Shared Uplink Set rules apply per domain: • 320 Unique VLANs per Virtual Connect Ethernet module • 128 Unique VLANs per Shared Uplink Set • 28 Unique Server Mapped VLANs per Server Profile Network Connection Please see the Virtual Connect 2.30 Release Notes for future details on these and other new features. Introduction to Virtual Connect 8...
Page 9: Tunneled Vlan And Mapped Vlans
Tunneled VLAN and Mapped VLANS Virtual Connect provides two Ethernet networks connection methods. Both of these connection types are discussed within the following scenarios. vNet A vNet is a term used to describe a network within Virtual Connect. A vNet could represent a dedicated network within Virtual Connect, in which case it would operate in one of two modes, the first is a simple vNet that will pass untagged frames.
Page 10 If a single network is selected, the frames will be presented to the server NIC WITHOUT a VLAN tag. In this case the host operating system does not need to understand which VLAN it resides in. When the server transmits frames back to VC, those frames will not be tagged, however; Virtual Connect will add the VLAN tag and forward the frame onto the correct VLAN.
Page 11 If Virtual Connect is set to Map VLAN Tags Mode, you can do the following; • Create a Shared Uplink Set – (the behavior of a SUS changes and now provides the ability to connect multiple networks to a NIC) which can support several VLANs up to the publish limits. •...
Page 12: Chapter 1: Single Domain/Enclosure Scenarios
Chapter 1: Single Domain/Enclosure Scenarios Overview This chapter will provide several simple configuration scenarios of Virtual Connect, using a Single HP BladeSystem c7000 enclosure with two Virtual Connect Ethernet modules installed in Bays 1 and 2. Each scenario will provide an overview of the configuration, show how to complete that configuration and include both GUI and CLI (scripted) methods.
Page 13: Scenario 1:1 - Simple Vnet With Active/Standby Uplinks And Optional Link Aggregation 802.3Ad (Lacp) - Windows
Scenario 1:1 – Simple vNet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows Overview This simple configuration uses the Virtual Connect vNet. The vNet is the simplest way to connect Virtual Connect to a network and server. In this scenario, the upstream network switch connects a network to a single port on each VC module.
Page 14 Figure 1-2 Physical View; Shows a single Ethernet uplink from Port 1 on Module 1 to Port 1 on the first network switch and a single uplink from Port 1 on Module 2 to Port 1 on the second network switch. Item Description Switch Cross Connect...
Page 15: Installation And Configuration
Figure 1-3 Logical View; Shows a single Ethernet uplink from Port 1 on Module 1 on the first network switch and a single uplink from Port 1 on Module 2 to Port 1 on the second network switch. Installation and configuration Switch configuration Appendices A and B provide a summary of the commands required to configure the switch in either a Cisco IOS or a ProCurve network infrastructure.
Page 16 • Physically connect Port 1 of the second Network switch to Port 1 of the VC module in Bay 2, if you have only one network switch, connect VC port 1 (Bay 2) to an alternate port on the same switch. This will NOT create a network loop and does not require Spanning Tree to be configured.
Page 17 Defining a new vNet via GUI Create a vNet and name it “vNet-PROD” • Login to Virtual Connect, if a Domain has not been created, create it now, but cancel out of the network and profile wizards. • On the Virtual Connect Manager screen, click Define, Ethernet Network to create a vNet •...
Page 18 Figure 1-5 Define Ethernet Network (vNet-PROD). Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below Defining a Server Profile with NIC Connections, via GUI Each server NIC will connect to a specific network. On the Virtual Connect Manager screen, click Define, Server Profile to create a Server Profile •...
Page 19 Figure 1-7 Server Profile View Bay 1. Scenario 1:1 – Simple vNet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 19...
Page 20: Optionally Configuring Additional Uplinks To A Vnet (Lacp)
Optionally Configuring Additional Uplinks to a vNet (LACP) If additional uplink bandwidth or redundancy is required, additional uplinks can be configured for an existing vNet. There are two options available when configuring additional uplinks, when all uplinks configured within a vNet connect a single VC module to a single upstream switch, ALL links will be active, providing additional bandwidth, using Link Aggregation Protocol (LACP 802.3ad), this requires the upstream switch to be configured, on these ports, for link aggregation control protocol (LACP) and be configured in the same link aggregation group.
Page 21: Switch Configuration
Figure 1-9 Logical View; Shows two Ethernet uplinks from Ports 1& 2 of each VC module to the network switch. Switch configuration Appendices A and B provide a summary of the commands required to configure the switch in either a Cisco IOS or a ProCurve network infrastructure.
Page 22 Figure 1-10 Adding uplinks to an existing vNet (vNet-PROD). Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below Figure 1-11 Link aggregation confirmed – Bay 1. Note: All connections within an active/active LACP group will have the same LAG ID.
Page 23: Summary
Figure 1-12 Link aggregation confirmed - Bay 2. Summary We created a couple different Virtual Connect Network solutions; base initially for availability, one link was active while the second was in standby mode. We later added two additional links; this increased the network bandwidth to the Virtual Connect network, while still maintaining availability.
Page 24 Figure 1-13 Both NICs for Profile App-1are connected to the network through vNet-PROD. The following graphics provide an example of a Windows 2003 server with TWO NICs teamed and connected to the network. One NIC will be active while the other is in standby. In the event of an Uplink or switch failure, VC will fail-over to the standby uplinks.
Page 25 Figure 1-15 Both NICs for Profile App-1are teamed and connected to the network through vNet-PROD. Scenario 1:1 – Simple vNet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 25...
Page 26: Scenario 1:2 - Multiple Simple Networks With Active\Active Uplinks And Optional Link Aggregation 802.3Ad (Lacp) - Windows
Scenario 1:2 – Multiple Simple Networks with Active\Active Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows Overview This simple configuration uses the Virtual Connect vNet. The vNet is the simplest way to connect Virtual Connect to a network and server. In this scenario, the upstream network switch connects a network to a single port on each VC module.
Page 27 Figure 1-16 Physical View; Shows a single Ethernet uplink from Port 1 on Module 1 to Port 1 on the first network switch and a single uplink from Port 1 on Module 2 to Port 1 on the second network switch. Item Description Switch Cross Connect...
Page 28: Installation And Configuration
Figure 1-17 Logical View; Shows a single Ethernet uplink from Port 1 on Module 1 to Port 1 on the first network switch and a single uplink from Port 1 on Module 2 to Port 1 on the second network switch. The Uplink from Module 1 is associated with vNet-PROD-1 and the Uplink from Module 2 is associated with vNet-PROD-2.
Page 29 • Connect Port 1 of the second Network switch to Port 1 of the VC module in Bay 2, if you have only one network switch, connect the second VC module, port 1 to an alternate port on the same switch. This will NOT create a network loop and does not require Spanning Tree to be configured.
Page 30 Defining two new vNet via GUI Create a vNet and name it “vNet-PROD-1” • On the Virtual Connect Manager screen, click Define, Ethernet Network to create a vNet • Ether the Network Name of “vNet-PROD-1” Optionally select Smart Link, but, do NOT select any of the other options (ie; Private Networks etc.) •...
Page 31 Figure 1-19 Define Ethernet Network (vNet-PROD-1). Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below. Figure 1-20 Define Ethernet Network (vNet-PROD-2). Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below Scenario 1:2 –...
Page 32: Optionally Configuring Additional Uplinks To A Vnet (Lacp)
Optionally Configuring Additional Uplinks to a vNet (LACP) If additional uplink bandwidth or redundancy is required, additional uplinks can be configured for an existing vNet. There are two options available when configuring additional uplinks, when all uplinks configured within a vNet connect a single VC module to a single upstream switch, ALL links will be active, providing additional bandwidth, using Link Aggregation Protocol (LACP 802.3ad), this requires the upstream switch to be configured, on these ports, for link aggregation control protocol (LACP) and be configured in the same link aggregation group.
Page 33 Figure 1-22 Logical View; Shows two Ethernet uplinks from Ports 1&2 of each VC module to the network switch. Switch configuration Appendices A and B provide a summary of the commands required to configure the switch in either a Cisco IOS or a ProCurve network infrastructure. The configuration information provided in the appendices assumes the following information: •...
Page 34 Note: By connecting two Uplinks from each vNet we have provided additional bandwidth and redundant paths to the network. Adding uplinks to an existing vNet via CLI The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Edit the vNet "vNet-PROD-1"...
Page 35 Figure 1-24 Adding uplinks to an existing vNet (vNet-PROD-2). Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below Figure 1-25 Link aggregation confirmed – Bay 1. Note: All connections within an active/active LACP group will have the same LAG ID.
Page 36 Figure 1-26 Link aggregation confirmed - Bay 2. Defining a Server Profile with NIC Connections, via GUI Each server NIC will connect to a specific network. On the Virtual Connect Manager screen, click Define, Server Profile to create a Server Profile •...
Page 37 Figure 1-27 Define Server Profile (App-1). Figure 1-28 View Bay 1. Scenario 1:2 – Multiple Simple Networks with Active\Active Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows...
Page 38: Summary
Summary We created a couple different Virtual Connect Network solutions; base initially for bandwidth, which also provided additional availability. Two VC networks were created, both with a single active uplink. We later added two additional links; this increased the network bandwidth to the Virtual Connect networks, while still maintaining availability.
Page 39 The following graphics provide an example of a Windows 2003 server with TWO NICs teamed and connected to the network. One NIC will be active, the other NIC will be in standby, in the event of an Uplink, switch or VC module failure; the teaming software will fail the NIC over to the alternate path, as required.
Page 40: Scenario 1:3 - Multiple Simple Networks Providing Redundancy And Link Aggregation 802.3Ad (Lacp) With Vlan Tunneling - Vmware Esx
Scenario 1:3 – Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling – VMware ESX Overview This configuration uses the Virtual Connect vNet. The vNet is the simplest way to connect Virtual Connect to a network and server. In this scenario, the upstream network switch is configured to pass multiple VLANs to two ports on each VC module.
Page 41 Figure 1-32 Physical View; Shows two Ethernet uplinks from Ports 1 & 2 on Module 1 to Ports 1 & 2 on the first network switch and two uplinks from Ports 1 and 2 on Module 2 to Ports 1 & 2 on the second network switch. Item Description Switch Cross Connect...
Page 42: Installation And Configuration
Figure 1-33 Logical View; Shows two Ethernet uplinks from Ports 1&2 of each VC module to the network switch. Installation and configuration Switch configuration Appendices A and B provide a summary of the commands required to configure the switch in either a Cisco IOS or a ProCurve network infrastructure.
Page 43 Configuring Fast MAC Cache Failover • When an uplink on a VC Ethernet Module that was previously in standby mode becomes active, it can take several minutes for external Ethernet switches to recognize that the c-Class server blades can now be reached on this newly active connection. •...
Page 44 Defining two new vNets via GUI Create a vNet and name it “vNet-PROD-1” • On the Virtual Connect Manager screen, click Define, Ethernet Network to create a vNet • Ether the Network Name of “vNet-PROD-1” Select Enable VLAN Tunneling Optionally select Smart Link, but, do NOT select Private Networks •...
Page 45 Figure 1-35 Adding uplinks to an existing vNet (vNet-PROD-1). Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below Scenario 1:3 – Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling – VMware ESX 45...
Page 46 Figure 1-36 Adding uplinks to an existing vNet (vNet-PROD-2). Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below Figure 1-37 Link aggregation confirmed – Bay 1. Note: All connections within an active/active LACP group will have the same LAG ID.
Page 47 Figure 1-38 Link aggregation confirmed - Bay 2. Defining a Server Profile with NIC Connections, via GUI Each server NIC will connect to a specific network. On the Virtual Connect Manager screen, click Define, Server Profile to create a Server Profile •...
Page 48 Figure 1-39 Define a Server Profile (ESX-1). Figure 1-40 View Bay 1. Scenario 1:3 – Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling – VMware ESX 48...
Page 49: Summary
Summary We created two VC networks, both with TWO active uplinks. Both VC Networks will pass several VLANs as configured/defined by the connected switch, without modification or interpreting the VLAN tags. When VC profile ESX-1 is applied to the server in bay1 and is powered up, it has two NICs, these NICs are connected to “vNet-PROD-1”...
Page 50 Figu re 1-42 Configuring the ESX vSwitch for Multiple Networks / VLANs. If additional VLANs need to be supported, simply configure the upstream switch ports for those VLANs, then configure the vSwitch as below to support those additional VLANs. When configuring the virtual guest, edit the Network Adapter configuration and select which VLAN this guest will connect to.
Page 51 Figure 1-43 The guest Virtualization Manager’s network adapter is then configured for the appropriate VLAN. Scenario 1:3 – Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling – VMware ESX 51...
Page 52: Scenario 1:4 - Vlan Tagging (802.1Q) With A Shared Uplink Set (Sus) With Link Aggregation Using Lacp (802.3Ad) - Windows
Scenario 1:4 – VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) – Windows Overview This configuration uses the Virtual Connect Shared Uplink Set (SUS). The SUS provides the ability to present a single or multiple VLANs to a server NIC. In this scenario, the upstream network switch connects multiple VLANs to two ports on each VC module.
Page 53 Figure 1-44 Physical View; Shows two Ethernet uplinks from Ports 1 and 2 on Module 1 to Ports 1 and 2 on the first network switch and two uplinks from Ports 1 and 2 on Module 2 to Ports 1 and 2 on the second network switch. Item Description Switch Cross Connect...
Page 54: Installation And Configuration
Figure 1-45 Logical View; Shows two Ethernet uplinks from each VC module to the network switches. The Uplinks from both Modules are associated with the Shared Uplink Set “VLAN-Trunk-1. Both NICs for blade App-1 are connected to PROD-A, all frames are received untagged. Installation and configuration Switch configuration Appendices A and B provide a summary of the commands required to configure the switch in either a...
Page 55 Configuring Fast MAC Cache Failover • When an uplink on a VC Ethernet Module that was previously in standby mode becomes active, it can take several minutes for external Ethernet switches to recognize that the c-Class server blades can now be reached on this newly active connection. •...
Page 56 Enclosure 1, Bay 1, Port 1 Enclosure 1, Bay 1, Port 2 Enclosure 1, Bay 2, Port 1 Enclosure 1, Bay 2, Port 2 • Add Networks as follows; PROD-A = VLAN ID=101 PROD-B = VLAN ID=102 PROD-B = VLAN ID=103 PROD-B = VLAN ID=104 •...
Page 57 Figure 1-47 Define Shared Uplink Set (VLAN-Trunk-1). Figure 1-48 Link aggregation confirmed – Bay 1. Note: All connections within an active/active LACP group will have the same LAG ID. To view this, go to the Interconnect bay and view Uplink Port Information. If you are having troubles establishing an active/active connection, confirm the LAG ID Scenario 1:4 –...
Page 58 Figure 1-49 Link aggregation confirmed - Bay 2. Defining a Server Profile with NICs Connections to a single VLAN, via GUI Each server NIC will connect to a network. On the Virtual Connect Manager screen, click Define, Server Profile to create a Server Profile •...
Page 59 Figure 1-50 Define a Server Profile (App-1). Figure 1-51 View Bay 1. Scenario 1:4 – VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) – Windows 59...
Page 60: Summary
Summary We created a Virtual Connect Shared Uplink Set (SUS), to support 4 VLANs (101-104). The SUS was created with both Active and standby uplinks, to provide both additional bandwidth and availability. When VC profile App-1 is applied to the server in bay1 and is powered up, it has two NICs connected to “PROD-A”, which connects to the network infrastructure through a two (active) 1Gb uplinks.
Page 61 Figure 1-54 Both NICs for Profile App-1are teamed and connected to the network through PROD-A Scenario 1:4 – VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) – Windows 61...
Page 62: Scenario 1:5 - Vlan Tagging (802.1Q) With A Shared Uplink Set (Sus) With Link Aggregation Using Lacp (802.3Ad) - Vmware Esx
Scenario 1:5 – VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) – VMware ESX Overview This configuration uses the Virtual Connect Shared Uplink Set (SUS). The SUS provides the ability to present a single or multiple VLANs to a server NIC. In this scenario, the upstream network switch connects multiple VLANs to two ports on each VC module.
Page 63 Figure 1-55 Physical View; Shows two Ethernet uplinks from Ports 1 and 2 on Module 1 to Ports 1 and 2 on the first network switch and two uplinks from Ports 1 and 2 on Module 2 to Ports 1 and 2 on the second network switch. Item Description Switch Cross Connect...
Page 64: Installation And Configuration
Figure 1-56 Server Profile ESX-1 configured with Multiple Networks on NICs 1&2 with PROD-A configured as the Default VLAN (untagged). All additional networks will be presented with tags. Installation and configuration Switch configuration Appendices A and B provide a summary of the commands required to configure the switch in either a Cisco IOS or a ProCurve network infrastructure.
Page 65 Configuring the VC Module for Map VLAN Tags via GUI (Ethernet settings) Enable Tunnel VLAN Tags within Virtual Connect • On the Virtual Connect Manager screen, Left pane, click Ethernet Settings, Advanced Settings • Select Map VLAN Tags • Select Fast MAC Cache Fail-over with a refresh of 5 •...
Page 66 Defining a new Shared Uplink Set via GUI Create a SUS and name it “VLAN-Trunk-1” • On the Virtual Connect Manager screen, click Define, Shared Uplink Set to create a SUS • Ether the Network Name of “VLAN-Trunk-1” • Select Add Port, then add the following ports; Enclosure 1, Bay 1, Port 1 Enclosure 1, Bay 1, Port 2 Enclosure 1, Bay 2, Port 1...
Page 67 Figure 1-58 Define Shared Uplink Set (VLAN-Trunk-1). Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below Figure 1-59 Link aggregation confirmed – Bay 1. Note: All connections within an active/active LACP group will have the same LAG ID. To view this, go to the Interconnect bay and view Uplink Port Information.
Page 68 Figure 1-60 Link aggregation confirmed - Bay 2. Defining a Server Profile with NICs Connections to Multiple VLANs, via GUI Each server NIC will connect to a specific network. On the Virtual Connect Manager screen, click Define, Server Profile to create a Server Profile •...
Page 69 Defining a Server Profile with NICs Connections to Multiple VLANs, via CLI The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create and Assign Server Profile App-1 add profile ESX-1 –nodefaultenetconn -nodefaultfcconn add enet-connection ESX-1 pxe=Enabled add enet-connection ESX-1 pxe=Disabled add server-port-map ESX-1:1 PROD-A VLanId=101 Untagged=True...
Page 70: Summary
Figure 1-62 Configuring NIC Port 1 with Multiple Networks, note PROD-A is not tagged, Note; that both NICs are configured with the same settings below. Note: the above graphic is an example of a how an ESX hypervisor might be configured for multiple VLANs.
Page 71: Results
Results The following graphic provides an example of an ESX Server with TWO NICs connected to the network. Both NICs are configured to support VLANs 101-104. VLAN 101 is the default VLAN and is not tagged. Port Groups are added to support each VLAN. Figure 1-63 Both NICs for Profile ESX-1 are connected to the network through Multiple Networks;...
Page 72 When configuring the virtual guest, edit the Network Adapter configuration and select which VLAN this guest will connect to. Figure 1-65 Edit the configuration of the Guest network adapter and configure it for the appropriate VLAN. Scenario 1:5 – VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) – VMware ESX 72...
Page 73: Scenario 1:6 - Vlan Tagging (802.1Q) With Multiple Shared Uplink Sets (Sus) And Link Aggregation Using Lacp (802.3Ad) - Vmware Esx
Scenario 1:6 – VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) – VMware Overview This configuration uses the Virtual Connect Shared Uplink Set (SUS). The SUS provides the ability to present a single or multiple VLANs to a server NIC. In this scenario, the upstream network switches present several VLANs to two ports on each VC module.
Page 74 Figure 1-66 Physical View; Shows two Ethernet uplinks from Ports 1 and 2 on Module 1 to Ports 1 and 2 on the first network switch and two uplinks from Ports 1 and 2 on Module 2 to Ports 1 and 2 on the second network switch. Item Description Switch Cross Connect...
Page 75: Installation And Configuration
Figure 1-67 Server Profile ESX-1 configured with Multiple Networks on NICs 1&2 with PROD-A-1 and PROD-A-2 configured as the Default VLAN (untagged) at the server profile. All additional networks will be presented with tags. Installation and configuration Switch configuration Appendices A and B provide a summary of the commands required to configure the switch in either a Cisco IOS or a ProCurve network infrastructure.
Page 76 Configuring Fast MAC Cache Failover • When an uplink on a VC Ethernet Module that was previously in standby mode becomes active, it can take several minutes for external Ethernet switches to recognize that the c-Class server blades can now be reached on this newly active connection. •...
Page 77 Defining a new Shared Uplink Sets via the GUI Create a SUS and name it “VLAN-Trunk-1” • On the Virtual Connect Manager screen, click Define, Shared Uplink Set to create a SUS • Ether the Network Name of “VLAN-Trunk-1” • Select Add Port, then add the following ports;...
Page 78 Defining a new Shared Uplink Set via the CLI #Create Shared Uplink Set "VLAN-Trunk-1" and configure an uplink on VC Module 1, Ports 1 and 2 add uplinkset VLAN-Trunk-1 add uplinkport enc0:1:1 Uplinkset=VLAN-Trunk-1 speed=auto add uplinkport enc0:1:2 Uplinkset=VLAN-Trunk-1 speed=auto # Create Networks VLAN_101 and VLAN_104 for Shared Uplink Set "VLAN-TRUNK-1" add network PROD-A-1 uplinkset=VLAN-Trunk-1 VLanID=101 Set Network PROD-A-1 SmartLink=Enabled add network PROD-B-1 uplinkset=VLAN-Trunk-1 VLanID=102...
Page 79 Figure 1-69 Define Shared Uplink Set (VLAN-Trunk-1). Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below Note: Smart Link is enabled, if ALL uplinks to this SUS fail, then server downlinks will be turned off, initiating a NIC teaming fail-over.
Page 80 Figure 1-70 Define Shared Uplink Set (VLAN-Trunk-2). Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below. Note: Smart Link is enabled, if ALL uplinks to this SUS fail, then server downlinks will be turned off, initiating a NIC teaming fail-over.
Page 81 Figure 1-71 Link aggregation confirmed – Bay 1. Note: All connections within an active/active LACP group will have the same LAG ID. To view this, go to the Interconnect bay and view Uplink Port Information. If you are having troubles establishing an active/active connection, confirm the LAG ID Figure 1-72 Link aggregation confirmed - Bay 2.
Page 82 Defining a Server Profile with NICs Connections to Multiple VLANs, via GUI Each server NIC will connect to a specific network. On the Virtual Connect Manager screen, click Define, Server Profile to create a Server Profile • Create a server profile called “ESX-1” •...
Page 83 Figure 1-73 Server Profile (ESX-1) with Multiple Networks configured. Figure 1-74 Configuring NIC Port 1 with Multiple Networks, PROD-A-1 is not tagged, Note; that both NICs are configured with the same settings below, except NIC 2 is connected to PROD-x-2. Scenario 1:6 –...
Page 84: Summary
Figure 1-75 Configuring NIC Port 2 with Multiple Networks, PROD-A-2 is not tagged, Note; that both NICs are configured with the same settings below, except NIC 2 is connected to PROD-x-2. Note: the above graphic is an example of a how an ESX hypervisor might be configured for multiple VLANs.
Page 85: Results
Results The following graphic provides an example of an ESX Server with TWO NICs connected to the network. Both NICs are configured to support VLANs 101-104. VLAN 101 is the default VLAN and is not tagged. Port Groups are added to support each VLAN. Figure 1-76 Both NICs for Profile ESX-1are connected to the network through Multiple Networks, VLANs are configured as Port Groups within the virtual switch.
Page 86 Figure 1-77 Configuring the ESX vSwitch for Multiple Networks / VLANs. When configuring the virtual guest, edit the Network Adapter configuration and select which VLAN this guest will connect to. Scenario 1:6 – VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) – VMware ESX 86...
Page 87 Figure 1-78 Edit the configuration of the Guest network adapter and configure it for the appropriate VLAN. Scenario 1:6 – VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) – VMware ESX 87...
Page 88: Scenario 1:7 - Private Networks (Simple Vnet)
Scenario 1:7 – Private Networks (Simple vNet) Overview This scenario uses the private Networks feature to restrict communications between hosts within a Virtual Connect Network. In this scenario, a single uplink port from the VC module will be used to carry a single or multiple VLANs to a simple vNet.
Page 89 Figure 1-79 Physical View; Shows a single Ethernet uplink from Port 1 on Module 1 to Port 1 on the first network switch and a single uplink from Port 1 on Module 2 to Port 1 on the second network switch. Item Description Switch Cross Connect...
Page 90: Installation And Configuration
Figure 1-80 Private VLANs - Simple Network Connection showing a single Ethernet uplink to a single VC-Enet port (Port 1). VC-Enet Port 1 is configured as part of the VC Network Prod-Net. As the Private Network feature is enabled on Prod-Net, servers that are connected to Prod-Net will not be able to talk directly to each other within VC, an external router would be required.
Page 91 Configuring Fast MAC Cache Failover • When an uplink on a VC Ethernet Module that was previously in standby mode becomes active, it can take several minutes for external Ethernet switches to recognize that the c-Class server blades can now be reached on this newly active connection. •...
Page 92 Defining a new vNet via GUI Create a vNet and name it “vNet-PROD” • On the Virtual Connect Manager screen, click Define, Ethernet Network to create a vNet • Ether the Network Name of “vNet-PROD” Select Private Networks • Select Add Port, then add the following ports; Enclosure 1, Bay 1, Port 1 Enclosure 1, Bay 2, Port 1 •...
Page 93 Figure 1-82 Define a new vNet (vNet-Prod) and enable Private Networks. Defining a Server Profile Four server profiles will be required; both Network ports will be connected to vNet-PROD On the Virtual Connect Manager screen, click Define, Server Profile to create a Server Profile •...
Page 94 On the Virtual Connect Manager screen, click Define, Server Profile to create a Server Profile • Create a server profile called “Web-4” • In the Network Port 1 drop down box, select “vNet-PROD” • In the Network Port 2 drop down box, select “vNet-PROD” •...
Page 95: Summary
Figure 1-84 View Server Bay 1. Summary All server blades are assigned a Server Profile which is configured with a single NIC on vNet PROD_NET. When the blades are powered up and their profiles are applied, the blades in bays 1 through 4 will have both NICs connected to the vNet-PROD network.
Page 96 Figure 1-85 Both NICs for Profile Web-1are connected to the network through vNet-PROD. Scenario 1:7 – Private Networks (Simple vNet) 96...
Page 97 The following graphics provides an example of a Windows 2003 server with TWO NICs teamed and connected to the network. One NIC will be active, in the event of an Uplink, switch or VC module failure; the teaming software will fail the NIC over to the alternate path, if required. Figure 1-86 Team both NICs, using the HP Network Configuration Utility.
Page 98: Chapter 2: Flex-10 Scenario
Chapter 2: Flex- 1 0 Scenario Overview This chapter will provide configuration scenarios of Virtual Connect Flex-10, using a single HP BladeSystem c7000 enclosure with two Virtual Connect Flex-10 Ethernet modules installed in Bays 1 and 2. If additional Network ports are required, over what TWO Flex-10 NICs will provide, additional network ports can be added along with additional VC or VC Flex-10 modules, switches or Pass-Thru modules.
Page 99 Item Description Half Height BladeSystem Server VC Ethernet Modules Chapter 2: Flex-10 Scenario 99...
Page 100: Windows 2003/2008
Scenario 2:1 - Flex- 1 0 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - Windows 2003/2008 Overview This scenario discusses the Flex-10 features provided in Virtual Connect. For an overview of Flex-10, please refer to the following technology brief. HP Flex-10 technology brief: http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01608922/c01608922.pdf Virtual Connect Flex-10 provides the ability to either present the 10Gb server NICs as single 10Gb NICs, or divide each NIC into as many as 4 “physical function”...
Page 101 Figure 2-2 Physical View; Shows one 10Gb Ethernet uplink from Ports 1 on Module 1 to Port 1 on the first network switch and one 10Gb uplink from Port 1 on Module 2 to Port 1 on the second network switch. Item Description Switch Cross Connect...
Page 102: Installation And Configuration
Figure 2-3 Server blade profile with TWO Flex-10 NICs configured. Each NIC is connected to a vNet (Prod-101-1 and Prod-101-2), which are part of the Shared Uplink Sets, VLAN-Trunk-1 and VLAN-Trunk-2 respectively. The VLAN- Trunks are connected, at 10Gb, to a network switch, through Port X1 on VC module 1 and Port X1 on VC module 2. Installation and configuration Switch configuration Appendices A and B provide a summary of the commands required to configure the switch in either a...
Page 103 • Enabling Fast MAC Cache Failover forces Virtual Connect to transmit Ethernet packets on newly active links, which enables the external Ethernet switches to identify the new connection (and update their MAC caches appropriately). This transmission sequence repeats a few times at the MAC refresh interval (five seconds is the recommended interval) and completes in about one minute.
Page 104 Figure 2-4 Ethernet Settings. Defining a new Shared Uplink Set (VLAN-Trunk-1) Connect Port X1 of VC module 1 to Port 1 on switch 1 Create a SUS named “VLAN-Trunk-1” and connect it to Flex-10 Port X1 on Module 1 • On the Virtual Connect Home page, select Define, Shared Uplink Set •...
Page 105 Defining a new Shared Uplink Set via CLI The following script can be used to create the first Shared Uplink Set (VLAN-Trunk-1) The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create Shared Uplink Set "VLAN-Trunk-1" and configure uplinks add uplinkset VLAN-Trunk-1 add uplinkport enc0:1:X1 Uplinkset=VLAN-Trunk-1 speed=auto # Create Networks Prod-A-1 through Prod-D-1 for Shared Uplink Set "VLAN-Trunk-1"...
Page 106 Figure 2-5 Define a Shared Uplink Set (VLAN-Trunk-1) and add VLANs. Note: The “Connected to” field in the graphic above displays the MAC address and port number of the switch this uplink is connected to. This information is provided through LLDP discover and is not available in all switch products.
Page 107 Figure 2-7 Associated Networks. Summary Note: In this scenario we have created two independent Share Uplink Sets (SUS), each originating from the opposite VC-Modules, by doing so we provide the ability to create separate and redundant connections out of VC. When we create the server profiles, you will see how the NICs will connect to VLANs accessed through the opposite VC module, which provides the ability to create an Active / Active uplink scenario.
Page 108 • In the Assign Profile to Server Bay box, locate the Select Location drop down and select Bay 1, they apply Note: you should now have a server profile assigned to Bay 1, with 2 Server NIC connections. NICs 1&2 should be connected to networks PROD-A-1 and PROD-A-2. Defining a Server Profile via CLI The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create Server Profile Server-1...
Page 109: Summary
LOM:1-a can be assigned to Prod-101-1, no other NIC on LOM:1 can be assigned to Prod-101-1) This is discussed in further details in the Flex-10 technology brief mentioned earlier in this scenario. As additional NICs are added to a server profile that is assigned to a server with a 10Gb Flex-NIC, the assignment will alternate between LOM:1 and LOM:2.
Page 110 Figure 2-11 Windows 2003 Network Connections (2 Connections Active). The NICs that are not configured within VC will appear with a red x as not connected. You can go into Network Connections for the Windows 2003 server and Disable any NICs that are not currently in use. Windows assigns the NICs as NIC 1-8, whereas four of the NICs will reside on LOM:1 and four on LOM:2.
Page 111 Figure 2-13 Windows 2003 Network Connections (2 Connections). Note: In windows 2003 the NIC speeds may not be shown accurately when speeds are configured in 100MB increments above 1Gb. IE: if a NIC is configured for 2.5Gb within Flex-10, it will be displayed in Windows 2003 as a 2Gb NIC.
Page 112 Figure 2-14 Windows 2003 Device Manager shows all 8 NICs. Note: This is the case no matter how many NICs are actually configured and in use. Windows 2008 Networking Configuration Example The following graphics show a Windows 2008 server with TWO Flex-10 NICs configured as single NICs, at FULL 10Gb speed.
Page 113 The NICs that are not configured within VC will appear with a red x as not connected. You can go into Network Connections for the Windows 2008 server and Disable any NICs that are not currently in use. Windows assigns the NICs as NIC 1-8, whereas four of the NICs will reside on LOM:1 and four on LOM:2.
Page 114: Nic Teaming
NIC Teaming If higher availability is desired, NIC teaming in Flex-10 works the same way as in standard network configurations. Simply, open the NIC teaming Utility and configure the available NICs for teaming. In this example, we have only TWO NICs available, so selecting NICs for teaming will be quite simple. However, if multiple NICs are available, ensure that the correct pair of NICs is teamed.
Page 115 Figure 2-19 View – Network Connections – NIC Team #1. Figure 2-20 View – Network Connections – NIC Team #1 – Windows. Scenario 2:1 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - Windows 2003/2008 115...
Page 116: Adding Additional Nics To An Existing Server Profile
Adding additional NICs to an existing server Profile What has been shown and discussed to this point is standard Virtual Connect functionality. We will now go into more of the specific Flex-10 features by providing additional NICs to the Windows server, without adding additional server hardware.
Page 117 Editing a Server Profile We will edit server profile Server-1 and add TWO additional NICs to the server. Each server NIC will connect to a specific network. • On the main VC menu, select Server Profile Server-1 • Under Ethernet Network Connections, click the Add Network Connection button twice •...
Page 118 Figure 2-22 Setting the Network connection Port Speed. Figure 2-23 Server NIC speed and LOM Mappings. Scenario 2:1 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - Windows 2003/2008 118...
Page 119: Summary
Summary Initially the Virtual Connect server profile was created with only TWO 10Gb NICs configured and applied to Enclosure Bay 1. Without installing any additional hardware, the profile was later edited and two additional NICs were added, the initial NICs had their speed set down to 2.5Gb each and the newly added NICs were set with a link speed of 7.5Gb.
Page 120 Figure 2-25 Windows 2003 Network Connections NIC Speed. Note: Even though the Profile is set to 2.5Gb and 7.5Gb respectively, Windows 2003 does not display values correctly. Windows 2008 displays the correct values. Scenario 2:1 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - Windows 2003/2008 120...
Page 121 Figure 2-26 Windows 2008 Network Connections (4 Active Connections). Figure 2-27 Windows 2008 Network Connections NIC Speed. Note: Windows 2008 displays the correct link speed values Scenario 2:1 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - Windows 2003/2008 121...
Page 122: Scenario 2:2 - Flex-10 - Vlan Tagging (802.1Q) With Multiple Shared Uplink Sets (Sus) And Mapped Vlans - Windows 2008 Hyper-V
Scenario 2:2 - Flex- 1 0 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - Windows 2008 Hyper-V Overview This scenario discusses the Flex-10 features provided in Virtual Connect. For an overview of Flex-10, please refer to the following technology brief. HP Flex-10 technology brief; http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01608922/c01608922.pdf Virtual Connect Flex-10 provides the ability to either present the 10Gb server NICs as single 10Gb NICs, or divide each NIC into as many as 4 “physical function”...
Page 123: Requirements
Requirements In order to implement this scenario, an HP BladeSystem c7000 enclosure with one of more Blade G6 servers with 10Gb NICs and TWO Virtual Connect Flex-10 Ethernet modules, installed in Bays 1 & 2 are required. In addition, we will require ONE or TWO external Network switches. As Virtual Connect does not appear to the network as a switch and is transparent to the network, any standard managed switch will work with Virtual Connect.
Page 124: Installation And Configuration
Figure 2-29 Server Blade profile with TWO Flex-10 NICs configured. Each NIC is connected to a vNet (PROD-A- 1 and PROD-A-2), the additional NICs are connected to other networks, which are also part of the Shared Uplink Sets, VLAN-Trunk-1 and VLAN-Trunk-2 respectively. The VLAN-Trunks are connected, at 10Gb, to a network switch, through Port X1 on VC module 1 and Port X1 on VC module 2, creating an Active/Active uplink.
Page 125 Configuring Fast MAC Cache Failover • When an uplink on a VC Ethernet Module that was previously in standby mode becomes active, it can take several minutes for external Ethernet switches to recognize that the c-Class server blades can now be reached on this newly active connection. •...
Page 126 Figure 2-30 Ethernet Settings. Defining a new Shared Uplink Set (VLAN-Trunk-1) Connect Port X1 of VC module 1 to Port 1 on switch 1 Create a SUS named “VLAN-Trunk-1” and connect it to Flex-10 Port X1 on Module 1 • On the Virtual Connect Home page, select Define, Shared Uplink Set •...
Page 127 PROD-E-2 = VLAN ID=105 • Enable Smartlink on ALL Networks • Click Apply Defining a new Shared Uplink Set via CLI The following script can be used to create the first Shared Uplink Set (VLAN-Trunk-1) The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create Shared Uplink Set "VLAN-Trunk-1"...
Page 128 for Ports X7 & X8, which are the internal cross connect ports, the cross connects will disconnect, if an SFP+ module is plugged in Ports X7 or X8. Figure 2-31 Define a Shared Uplink Set (VLAN-Trunk-1) and add VLANs. Note: The “Connected to” field in the graphic above displays the MAC address and port number of the switch this uplink is connected to.
Page 129 Figure 2-32 Active / Active SUS. Summary Note: In this scenario we have created two independent Share Uplink Sets (SUS), each originating from the opposite VC-Modules, by doing so we provide the ability to create separate and redundant connections out of VC. When we create the server profiles, you will see how the NICs will connect to VLANs accessed through the opposite VC module, which provides the ability to create an Active / Active uplink scenario.
Page 130 Defining a Server Profile via CLI The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create Server Profile Server-1 add profile Server-1 –nodefaultenetconn add enet-connection Server-1 pxe=Enabled Network=PROD-A-1 SpeedType=Custom Speed=2500 add enet-connection Server-1 pxe=Disabled Network=PROD-A-2 SpeedType=Custom Speed=2500 add enet-connection Server-1 pxe=Disabled add server-port-map Server-1:3 PROD-C-1 VLanId=102 add server-port-map Server-1:3 PROD-C-1 VLanId=103...
Page 131 Server NIC Speed and LOM Mappings We will now focus more of the specific Flex-10 features. Note the “Allocated Bandwidth” and the LOM “Mapping” settings in the following graphic. Flex-10 based NICs have the ability of being configured as a Single 10Gb NIC or divided into as many as FOUR (4) physical NICs.
Page 132 Figure 2-35 Adjusting the NIC speed. Figure 2-36 Configuring Multiple Networks. Scenario 2:2 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - Windows 2008 Hyper-V 132...
Page 133: Summary
Summary This profile will present NIC 1 to network “PROD-A-1” & NIC 2 to network PROD-A-2 which are mapped to VLAN 101 (management network); frames for VLAN 101 will be passed to NICs 1&2 untagged. NICs 3&4 are connected to “Multiple Networks” (Production VLANs), PROD-B-1 – PROD-E-1 and PROD-B-2 – PROD-E-2, which are mapped to VLANs 102 –...
Page 134 Figure 2-37 Windows 2008 Network Connections (4 Active Connections). Figure 2-38 Windows 2008R2 Network Connections NIC Speed. Note: Windows 2008R2 displays the correct link speed values Scenario 2:2 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - Windows 2008 Hyper-V 134...
Page 135 Figure 2-39 Windows 2008 Network Connections (4 Active Connections – Renamed). Ensure that the Hyper-V role has been installed and configured, then install the latest version of the HP ProLiant Network Teaming Software and run the utility. Notice the NIC Names that were set earlier. You can also highlight each NIC and select properties to verify the MAC address of the NIC before creating the team.
Page 136 Figure 2-41 HP ProLiant Network Configuration Utility with both teams created. Creating the VLANs within NIC Teaming Highlight the Production NIC team and click the VLAN (802.1Q) button on the right and create a VLAN for each VLAN that this NIC team will support. Figure 2-42 HP ProLiant Network Configuration Utility VLAN configurations for Production Team.
Page 137 Creating the Hyper-V Virtual Network Run the Hyper-V Manager, open the Virtual Network Manager and create a new External Virtual Network for each VLAN that was created within the NIC team, enable the VLAN ID check box and enter the VLAN ID for this VLAN.
Page 138 Assigning a Virtualization Manager to a Network/VLAN Run the Hyper-V Manager and select HP Insight Virtualization Manager software that requires a network connection to be made. Select Setting for that Virtualization Manager, click the Network Adapter, under the Network drop down box, select the appropriate VLAN (VLAN 102), enable virtual LAN identification and enter the appropriate VLAN ID for this system and apply the settings.
Page 139 Verify that the Guest is connected to the correct VLAN Open a console to the Virtualization Manager and verify that it is in the correct VLAN. Figure 2-45 Verify guest VM received an IP address for the correct VLAN. Scenario 2:2 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - Windows 2008 Hyper-V 139...
Page 140: Overview
Scenario 2:3 - Flex- 1 0 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - ESX 4 Overview This scenario discusses the Flex-10 features provided in Virtual Connect. For an overview of Flex-10, please refer to the following technology brief. HP Flex-10 technology brief; http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01608922/c01608922.pdf Virtual Connect Flex-10 provides the ability to either present the 10Gb server NICs as single 10Gb NICs, or divide each NIC into as many as 4 “physical function”...
Page 141: Requirements
Requirements In order to implement this scenario, an HP BladeSystem c7000 enclosure with one of more Blade G6 servers with 10Gb NICs and TWO Virtual Connect Flex-10 Ethernet modules, installed in Bays 1& 2 are required. In addition, we will require ONE or TWO external Network switches. As Virtual Connect does not appear to the network as a switch and is transparent to the network, any standard managed switch will work with Virtual Connect.
Page 142: Installation And Configuration
Figure 2-47 Server Blade profile with TWO Flex-10 NICs configured. Each NIC is connected to a vNet (PROD-A- 1 and PROD-A-2), the additional NICs are connected to other networks, which are also part of the Shared Uplink Sets, VLAN-Trunk-1 and VLAN-Trunk-2 respectively. The VLAN-Trunks are connected, at 10Gb, to a network switch, through Port X1 on VC module 1 and Port X1 on VC module 2, creating an Active/Active uplink.
Page 143 their MAC caches appropriately). This transmission sequence repeats a few times at the MAC refresh interval (five seconds is the recommended interval) and completes in about one minute. Configuring the VC Module for Map VLAN Tags via GUI (Ethernet settings) Note: Flex-10 has also provided additional controls when configuring VC for mapped VLAN tags (Multiple Networks over a single link) support.
Page 144 Defining a new Shared Uplink Set (VLAN-Trunk-1) Connect Port X1 of VC module 1 to Port 1 on switch 1 Create a SUS named “VLAN-Trunk-1” and connect it to Flex-10 Port X1 on Module 1 • On the Virtual Connect Home page, select Define, Shared Uplink Set •...
Page 145 Defining a new Shared Uplink Set via CLI The following script can be used to create the first Shared Uplink Set (VLAN-Trunk-1) The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create Shared Uplink Set "VLAN-Trunk-1" and configure uplinks add uplinkset VLAN-Trunk-1 add uplinkport enc0:1:X1 Uplinkset=VLAN-Trunk-1 speed=auto # Create Networks Prod-A-1 through Prod-D-1 for Shared Uplink Set "VLAN-Trunk-1"...
Page 146 Note: The “Connected to” field in the graphic above displays the MAC address and port number of the switch this uplink is connected to. This information is provided through LLDP discover and is not available in all switch products. This information can be very helpful when determining which switches and ports VC is connected to.
Page 147 Figure 2-50 Active / Active SUS. Summary Note: In this scenario we have created two independent Share Uplink Sets (SUS), each originating from the opposite VC-Modules, by doing so we provide the ability to create separate and redundant connections out of VC. When we create the server profiles, you will see how the NICs will connect to VLANs accessed through the opposite VC module, which provides the ability to create an Active / Active uplink scenario.
Page 148 Defining a Server Profile via CLI The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create Server Profile Server-1 add profile Server-1 –nodefaultenetconn add enet-connection Server-1 pxe=Enabled Network=PROD-A-1 SpeedType=Custom Speed=500 add enet-connection Server-1 pxe=Disabled Network=PROD-A-2 SpeedType=Custom Speed=500 add enet-connection Server-1 pxe=Disabled Network=PROD-B-1 SpeedType=Custom Speed=2500 add enet-connection Server-1 pxe=Disabled Network=PROD-B-2 SpeedType=Custom...
Page 149 Server NIC Speed and LOM Mappings We will now focus more of the specific Flex-10 features. Note the “Allocated Bandwidth” and the LOM “Mapping” settings in the following graphic. Flex-10 based NICs have the ability of being configured as a Single 10Gb NIC or divided into as many as FOUR (4) physical NICs.
Page 150 Figure 2-54 Adjusting the NIC speed. Figure 2-55 Configuring Multiple Networks. Scenario 2:3 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - ESX 4 150...
Page 151: Summary
Summary This profile will present NIC 1 to network “PROD-A-1” & NIC 2 to network PROD-A-2 which are mapped to VLAN 101; frames for VLAN 101 will be passed to NICs 1&2 untagged. NICs 3&4 are connected to PROD-B-1 & PROD-B-2, which are mapped to VLAN 102; frames for VLAN 102 will be passed to NICs 3&4 untagged.
Page 152 ESX 4 Networking Configuration Example The following graphics show an ESX 4 server with two Flex-10 NICs configured as six NICs. Figure 2-57 vSwitch Configuration the ESX Host with 6 NICs. Scenario 2:3 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - ESX 4 152...
Page 153 VMWARE ESX Host Networking configuration Example When configuring the ESX virtual switch, add virtual networks for each VLAN this ESX host will support. Figure 2-58 Configuring the ESX vSwitch for Multiple Networks / VLANs. Note: That vSwitch2 has two NICs configured to redundantly, support VLANs 103, 104 and 105. Note: If implementing ESX 3.5 on Flex-10, first review VMWARE KB 1007982 and ensure Network Failure Detection is set to Beacon Probing.
Page 154 Figure 2-59 Selection of the Virtual Network (VLAN) as required. Scenario 2:3 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Mapped VLANs - ESX 4 154...
Page 155: Overview
Scenario 2:4 - Flex- 1 0 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Tunneled VLANs - ESX 4 Overview This scenario discusses the Flex-10 features provided in Virtual Connect. For an overview of Flex-10, please refer to the following technology brief. HP Flex-10 technology brief; http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01608922/c01608922.pdf Virtual Connect Flex-10 provides the ability to either present the 10Gb server NICs as single 10Gb NICs, or divide each NIC into as many as 4 “physical function”...
Page 156: Requirements
Requirements In order to implement this scenario, an HP BladeSystem c7000 enclosure with one of more Blade G6 servers with 10Gb NICs and TWO Virtual Connect Flex-10 Ethernet modules, installed in Bays 1& 2 are required. In addition, we will require ONE or TWO external Network switches. As Virtual Connect does not appear to the network as a switch and is transparent to the network, any standard managed switch will work with Virtual Connect.
Page 157: Installation And Configuration
Figure 2-61 Server Blade profile with TWO Flex-10 NICs configured. Each FlexNIC will connect to a different network. Both Shared Uplinks Sets and vNets are used. VLAN-Trunk-1 and VLAN-Trunk-2 respectively connect to Port X1 on Bays 1&2, were VLAN-Many-1 and VLAN-Many- 2 are connected to Port X2 on Bays 1&2 of the Flex-10 modules.
Page 158 Configuring Fast MAC Cache Failover • When an uplink on a VC Ethernet Module that was previously in standby mode becomes active, it can take several minutes for external Ethernet switches to recognize that the c-Class server blades can now be reached on this newly active connection. •...
Page 159 Figure 2-62 Ethernet Settings. Defining a new Shared Uplink Set (VLAN-Trunk-1) Connect Port X1 of VC module 1 to Port 1 on switch 1 Create a SUS named “VLAN-Trunk-1” and connect it to Flex-10 port X1 on Module 1 • On the Virtual Connect Home page, select Define, Shared Uplink Set •...
Page 160 • Add Networks as follows; PROD-A-2 = VLAN ID=101 PROD-B-2 = VLAN ID=102 PROD-C-2 = VLAN ID=103 • Enable SmartLink on ALL Networks • Click Apply Defining two new vNets via GUI Create a vNet and name it “VLAN-Many-1” • On the Virtual Connect Manager screen, click Define, Ethernet Network to create a vNet •...
Page 161 Defining a new Shared Uplink Set via CLI The following script can be used to create the first Shared Uplink Set (VLAN-Trunk-1) The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create Shared Uplink Set "VLAN-Trunk-1" and configure uplinks add uplinkset VLAN-Trunk-1 add uplinkport enc0:1:X1 Uplinkset=VLAN-Trunk-1 speed=auto # Create Networks Prod-A-1 through Prod-D-1 for Shared Uplink Set "VLAN-Trunk-1"...
Page 162 Figure 2-63 Define a Shared Uplink Set (VLAN-Trunk-1) and add VLANs. Note: The “Connected to” field in the graphic above displays the MAC address and port number of the switch this uplink is connected to. This information is provided through LLDP discover and is not available in all switch products.
Page 163 Summary Note: In this scenario we have created two independent Share Uplink Sets (SUS), each originating from the opposite VC-Modules, by doing so we provide the ability to create separate and redundant connections out of VC. When we create the server profiles, you will see how the NICs will connect to VLANs accessed through the opposite VC module, which provides the ability to create an Active / Active uplink scenario.
Page 164 Defining a Server Profile We will create a server profile with two server NICs. Each server NIC will connect to a specific network. • On the main menu, select Define, then Server Profile • Create a server profile called “Server-1” •...
Page 165: Summary
Figure 2-67 Define a Server Profile with 8 NICs. Summary This profile is configured as follows; • NICs 1&2 are connected to “PROD-A-1” & “PROD-A-2” (Console Network), which are mapped to VLAN 101 • NICs 3&4 are connected to “PROD-B-1” & “PROD-B-2” (VMotion Network), which are mapped to VLAN 102 •...
Page 166: Result
Result VMware ESX Configuration Example The following graphics show an ESX server with two Flex-10 NICs configured as 8 NICs. NICs speeds are also configured accordingly and connected to vSwitches, with port groups to present the VLANs accordingly. When configuring the vSwitches for ESX, you will notice that 8 NICs actually already exist, as per the Virtual Connect server Profile.
Page 167 ESX 4 Networking Configuration Example The following graphics show an ESX 4 server with two Flex-10 NICs configured as six NICs. Figure 2-69 vSwitch Configuration the ESX Host with 8 NICs. Scenario 2:4 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Tunneled VLANs - ESX 4 167...
Page 168 VMWARE ESX Host Networking configuration Example When configuring the ESX virtual switch, add virtual networks for each VLAN this ESX host will support. Figure 2-70 Configuring the ESX vSwitch for Multiple Networks / VLANs. Note: That vSwitch 3 has two NICs configured to, redundantly, support VLANs 103, 104 and 105. Note: If implementing ESX 3.5 on Flex-10, first review VMWARE KB 1007982 and ensure Network Failure Detection is set to Beacon Probing.
Page 169 Figure 2-71 Selection of the Virtual Network (VLAN) as required. Scenario 2:4 - Flex-10 - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Tunneled VLANs - ESX 4 169...
Page 170: Chapter 3: Multi-Enclosure (Stacking) Scenarios
Chapter 3: Multi-Enclosure (Stacking) Scenarios Overview This chapter will provide sample configuration scenarios of Virtual Connect and/or Virtual Connect with Flex-10, using multiple (Stacked) HP BladeSystem c7000 enclosures, which is referred to a Multi-enclosure stacking (ME), each with two Virtual Connect Ethernet modules installed in Bays 1 and 2. Each scenario will provide an overview of the configuration, show how to complete that configuration and include both GUI and CLI (scripted) methods.
Page 171: Overview
Scenario 3:1 – Multi-Enclosure stacking, with Multiple Simple vNets, Redundant Uplinks and LACP (2 Enclosures) Overview This simple configuration uses the Virtual Connect vNet using uplinks from TWO different enclosures within the stacked Virtual Connect domain, which is referred to a Multi-enclosure stacking (ME). The vNet is the simplest way to connect Virtual Connect to a network and server.
Page 172 Figure 3-1 Physical View; Shows TWO Ethernet uplinks from Ports 1 and 2 on Module 1 in Enclosure 1 to Ports 1 and 2 on the first network switch and TWO uplinks from Ports 1 and 2 on Module 2 in Enclosure 2 to Ports 1 and 2 on the second network switch.
Page 173: Installation And Configuration
Installation and configuration Switch configuration Appendices A and B provide a summary of the commands required to configure the switch in either a Cisco IOS or a ProCurve network infrastructure. The configuration information provided in the appendices assumes the following information: •...
Page 174 set enet-vlan vlantagcontrol=Tunnel set mac-cache Enabled=True Refresh=5 Figure 3-3 Ethernet Settings. Importing the Second Enclosure via GUI In order to stack Virtual Connect we need to first implement Virtual Connect, configure a Virtual Connect Domain within a HP BladeSystem c7000 enclosure, cable the enclosure together and then “import” the additional enclosures into the existing VC Domain.
Page 175 Importing the Second Enclosure via CLI The following command can be copied and pasted into an SSH based CLI session with Virtual Connect # Importing an Enclosure into an existing VC Domain Import enclosure 10.0.0.50 UserName=Administrator Password=password Note: Type “YES” when prompted Note: the IP Address (User name and password) is for the OA of the enclosure being imported.
Page 176 Figure 3-6 The figure below shows importing the enclosure. Figure 3-7 The enclosure is imported. Scenario 3:1 – Multi-Enclosure stacking, with Multiple Simple vNets, Redundant Uplinks and LACP (2 Enclosures) 176...
Page 177 Figure 3-8 VC Domain Stacking Links. Defining a new vNet via GUI Create a vNet and name it “vNet-PROD-1” • Login to Virtual Connect • On the Virtual Connect Manager screen, click Define, Ethernet Network to create a vNet • Enter the Network Name of “vNet-PROD-1”...
Page 178 Note: By connecting TWO Uplinks from each vNet we are leveraging LACP to provide additional bandwidth. By creating TWO separate vNets, we are also providing the ability to have ALL uplinks active and then provide fail-over through the server’s NICs with NIC teaming or two NICs connected to a vSwitch if a hypervisor is used.
Page 179 Figure 3-10 Define Ethernet Network (vNet-PROD-2). Note: The uplinks are connected to different enclosures, (enc0 and enc1). Defining a Server Profile with NIC Connections, via GUI Each server NIC will connect to a specific network. On the Virtual Connect Manager screen, click Define, Server Profile to create a Server Profile •...
Page 180: Summary
Figure 3-11 Define a Server Profile (App-1) and Assigns it to a Bay in either enclosure. Summary We created a Virtual Connect Domain within a BladeSystem c7000 enclosure, using 10Gb Ethernet cables, we then connected the VC modules from a second enclosure to this enclosure. We then extended the Virtual Connect domain (stacked) to include the second enclosure.
Page 181: Results
Results The following graphic provides an example of a Windows 2003 server with TWO NICs connected to the network, each NIC has its own TCP/IP address, either or both NICs could be actively working on the network. Figure 3-12 Both NICs for Profile App-1are connected to the network through vNet-PROD. The following graphics provide an example of a Windows 2003 server with TWO NICs teamed and connected to the network.
Page 182 Figure 3-13 Team both NICs, using the HP Network Configuration Utility. Figure 3-14 Both NICs for Profile App-1are teamed and connected to the network through vNet-PROD. Scenario 3:1 – Multi-Enclosure stacking, with Multiple Simple vNets, Redundant Uplinks and LACP (2 Enclosures) 182...
Page 183: Scenario 3:2 - Flex-10 With Multi-Enclosure Stacking - Vlan Tagging (802.1Q) With Multiple Shared Uplink Sets (Sus) - Vmware Esx - (4 Enclosures)
Scenario 3:2 - Flex- 1 0 with Multi-Enclosure stacking - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) - VMware ESX - (4 Enclosures) Overview This scenario discusses the Flex-10 features provided in Virtual Connect. For an overview of Flex-10, please refer to the following technology brief.
Page 184: Requirements
Table 3-1 Flex-10 NIC – Optimization for a VMWARE ESX implementation Console VMotion Production Console VMotion Production NIC #1 NIC #2 NIC #3 NIC #4 NIC #5 NIC #6 Traditional technology Virtual Connect Flex- 500Mb 2.5Gb 500Mb 2.5Gb Requirements In order to implement this scenario, four HP BladeSystem c7000 enclosure with one of more Blade G6 servers with 10Gb NICs and TWO Virtual Connect Flex-10 Ethernet modules, installed in Bays 1&...
Page 185 Item Description 10 Gb Uplink Switch Cross Connect Enclosure 1 Enclosure 2 Enclosure 3 Enclosure 4 External 10Gb Stacking link 10 Gb Uplink Internal Dual 10Gb Stacking links Figure 3-16 Server Blade profile with TWO Flex-10 NICs configured. Each NIC is connected to a Shared Uplink Set (VLAN-Trunk-1 and VLAN-Trunk-2), the additional NICs are connected to other networks, which are also part of the Shared Uplink Sets.
Page 186: Installation And Configuration
Installation and configuration Switch configuration Appendices A and B provide a summary of the commands required to configure the switch in either a Cisco IOS or a ProCurve network infrastructure. The configuration information provided in the appendices assumes the following information: •...
Page 187 set enet-vlan PrefSpeedType=Custom PrefSpeed=500 MaxSpeedType=Custom MaxSpeed=2500 Figure 3-17 Ethernet Settings. Importing the Second (and additional) Enclosure(s) via GUI In order to stack Virtual Connect we need to first implement Virtual Connect, configure a Virtual Connect Domain within a HP BladeSystem c7000 enclosure, cable the enclosure together and then “import” the additional enclosures into the existing VC Domain.
Page 188 Note: when importing additional enclosures through the CLI, each of the import Enclosure statements below must be executed individually and cannot be part of a larger script. When run, each command will ask for a “yes” to confirm the enclosure importation, once the enclosure has been found. Import enclosure 10.0.0.60 UserName=Administrator Password=password Import enclosure 10.0.0.30 UserName=Administrator Password=password Import enclosure 10.0.0.40 UserName=Administrator Password=password...
Page 189 Figure 3-20 Importing the enclosure. Figure 3-21 Importing additional enclosures. Scenario 3:2 - Flex-10 with Multi-Enclosure stacking - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) - VMware ESX - (4 Enclosures) 189...
Page 190 Figure 3-22 VC Domain Stacking Links. Defining a new Shared Uplink Set (VLAN-Trunk-1) Connect Port X2 of VC module 1, enclosure 1 to Port 1 on switch 1 Create a SUS named “VLAN-Trunk-1” and connect it to Flex-10 Port X2 on Module 1, enclosure 1 •...
Page 191 Defining a new Shared Uplink Set (VLAN-Trunk-2) Connect Port X2 of VC module 2m enclosure 4 to Port 1 on switch 2 Create a SUS named “VLAN-Trunk-2” and connect it to Flex-10 Port X2 on Module 2, enclosure 4 • On the Virtual Connect Home page, select Define, Shared Uplink Set •...
Page 192 # Create Shared Uplink Set "VLAN-Trunk-2" and configure uplinks add uplinkset VLAN-Trunk-2 add uplinkport enc3:2:X2 Uplinkset=VLAN-Trunk-2 speed=auto # Create Networks Prod-A-2 through Prod-D-2 for Shared Uplink Set "VLAN-Trunk-2" add network PROD-A-2 uplinkset=VLAN-Trunk-2 VLanID=101 set network SmartLink=Enabled PROD-A-2 add network PROD-B-2 uplinkset=VLAN-Trunk-2 VLanID=102 set network SmartLink=Enabled PROD-B-2...
Page 193 Figure 3-23 Define a Shared Uplink Set (VLAN-Trunk-1) and add VLANs. Note: The “Connected to” field in the graphic above displays the MAC address and port number of the switch this uplink is connected to. This information is provided through LLDP discover and is not available in all switch products.
Page 194 Figure 3-24 Active / Active SUS. Note: In this scenario we have created two independent Share Uplink Sets (SUS), each originating from the opposite VC-Modules, by doing so we provide the ability to create separate and redundant connections out of VC. When we create the server profiles, you will see how the NICs will connect to VLANs accessed through the opposite VC module, which provides the ability to create an Active / Active uplink scenario.
Page 195 Defining a Server Profile via CLI The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create Server Profile Server-1 add profile Server-1 –nodefaultenetconn add enet-connection Server-1 pxe=Enabled Network=PROD-A-1 SpeedType=Custom Speed=500 add enet-connection Server-1 pxe=Disabled Network=PROD-A-2 SpeedType=Custom Speed=500 add enet-connection Server-1 pxe=Disabled Network=PROD-B-1 SpeedType=Custom Speed=2500 add enet-connection Server-1 pxe=Disabled Network=PROD-B-2 SpeedType=Custom...
Page 196 Alternatively, the profile could be assigned to any server bay within the enclosure stack. # Create Server Profile Server-1 to the 4 enclosure, bay 11 Figure 3-27 Assign the server Profile to Enclosure 3, slot 11. Scenario 3:2 - Flex-10 with Multi-Enclosure stacking - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) - VMware ESX - (4 Enclosures) 196...
Page 197 Server NIC Speed and LOM Mappings We will now focus more of the specific Flex-10 features. Note the “Allocated Bandwidth” and the LOM “Mapping” settings in the following graphic. Flex-10 based NICs have the ability of being configured as a Single 10Gb NIC or divided into as many as FOUR (4) physical NICs.
Page 198 Figure 3-29 Adjusting the NIC speed. Figure 3-30 Configuring Multiple Networks. Scenario 3:2 - Flex-10 with Multi-Enclosure stacking - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) - VMware ESX - (4 Enclosures) 198...
Page 199: Summary
Summary This profile will present NIC 1 to network “PROD-A-1” & NIC 2 to network PROD-A-2 which are mapped to VLAN 101; frames for VLAN 101 will be passed to NICs 1&2 untagged. NICs 3&4 are connected to PROD-B-1 & PROD-B-2, which are mapped to VLAN 102; frames for VLAN 102 will be passed to NICs 3&4 untagged.
Page 200 ESX 4 Networking Configuration Example The following graphics show an ESX 4 server with two Flex-10 NICs configured as six NICs. Figure 3-32 vSwitch Configuration the ESX Host with 6 NICs. Scenario 3:2 - Flex-10 with Multi-Enclosure stacking - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) - VMware ESX - (4 Enclosures) 200...
Page 201 VMWARE ESX Host Networking configuration Example When configuring the ESX virtual switch, add virtual networks for each VLAN this ESX host will support. Figure 3-33 Configuring the ESX vSwitch for Multiple Networks / VLANs. Note: That vSwitch 3 has two NICs configured to, redundantly, support VLANs 103, 104 and 105. Note: If implementing ESX 3.5 on Flex-10, first review VMWARE KB 1007982 and ensure Network Failure Detection is set to Beacon Probing.
Page 202 Figure 3-34 Selection of the Virtual Network (VLAN) as required. Scenario 3:2 - Flex-10 with Multi-Enclosure stacking - VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) - VMware ESX - (4 Enclosures) 202...
Page 203: Appendix A: Scenario-Based Cisco Command Line Reference
Appendix A: Scenario-based Cisco command line reference All of the following commands in this appendix assume an unaltered factory default configuration before execution of the switch commands. Scenario 1-1 & 1-2 – Cisco IOS command line configuration (Simple vNet with Active/Standby Uplinks) Connect to the Cisco switch servicing the VC-Enet uplink ports and enter the following IOS commands.
Page 204 Simple vNet with Active/Standby Uplinks and Link Aggregation 802.3ad (LACP) - Windows Connect to the Cisco switch servicing the VC-Enet uplink ports and enter the following IOS commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 1b Scenario 1 (Part 2) - Cisco IOS command line configuration Command...
Page 205 Table 1b Scenario 1 (Part 2) - Cisco IOS command line configuration Command Shortcut Description #copy running-config startup-config #cop ru st Save the running configuration to NVRAM. Otherwise, the changes (For permanent changes only) will be lost on the next reboot. Appendix A: Scenario-based Cisco command line reference 205...
Page 206 Scenario 1-3 – Cisco IOS command line configuration (Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP)) Connect to the Cisco switch servicing the VC-Enet uplink ports and enter the following IOS commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 4 Scenario 1-3 - Cisco IOS command line configuration (802.1Q, 802.3ad) Command...
Page 207 Scenario 1-4 through 1-6 – Cisco IOS command line configuration (Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP)) Connect to the Cisco switch servicing the VC-Enet uplink ports and enter the following IOS commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 4 Scenario 1-4 –...
Page 208 Scenario 1-7 – Cisco IOS command line configuration (Private Networks (Simple vNet)) Connect to the Cisco switch servicing the VC-Enet uplink ports and enter the following IOS commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 7 Scenario 7 - Cisco IOS command line configuration Command...
Page 209 Scenario 2-1– Cisco IOS command line configuration (VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS)) Connect to the Cisco switch servicing the VC-Enet uplink ports and enter the following IOS commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 4 Scenario 1-4 –...
Page 210 Scenario 2-2 & 2-3 – Cisco IOS command line configuration (VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS)) Connect to the Cisco switch servicing the VC-Enet uplink ports and enter the following IOS commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 4 Scenario 1-4 –...
Page 211 Scenario 2-4 – Cisco IOS command line configuration (VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and vNets) Connect to the Cisco switch servicing the VC-Enet uplink ports and enter the following IOS commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 9 Scenario 2-3 &...
Page 212 Scenario 3-1– Cisco IOS command line configuration (Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP)) Connect to the Cisco switch servicing the VC-Enet uplink ports and enter the following IOS commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 10 Scenario 3-1 - Cisco IOS command line configuration Command...
Page 213 Scenario 3-2 – Cisco IOS command line configuration (VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS)) Connect to the Cisco switch servicing the VC-Enet uplink ports and enter the following IOS commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 10 Scenario 3-2 Cisco IOS command line configuration (802.1Q) Command...
Page 214: Appendix B: Scenario-Based Procurve Command Line Reference
Appendix B: Scenario-based ProCurve command line reference Scenario 1-1 & 1-2 – ProCurve command line configuration (Simple vNet with Active/Standby Uplinks) Connect to the ProCurve switch servicing the VC-Enet uplink ports and enter the following commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 1a Scenario 1-1 and 1-2 (Part 1) - ProCurve command line configuration (simple network) Command...
Page 215 Simple vNet with Active/Standby Uplinks and Link Aggregation 802.3ad (LACP) Connect to the ProCurve switch servicing the VC-Enet uplink ports and enter the following commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 1b Scenario 1-1 and 1-2 (Part 2) - ProCurve command line configuration (simple network) Command...
Page 216 Scenario 1-3 – ProCurve command line configuration (Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP)) Connect to the ProCurve switch servicing the VC-Enet uplink ports and enter the following commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 3 Scenario 1-3 - ProCurve command line configuration (untagged VLANs) Command...
Page 217 Scenario 1-4 through 1-6 – ProCurve command line configuration (Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP)) Connect to the ProCurve switch servicing the VC-Enet uplink ports and enter the following commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 3 Scenario 1-3 - ProCurve command line configuration (untagged VLANs) Command...
Page 218 Scenario 1-7 – ProCurve command line configuration (Simple vNet with Active/Standby Uplinks) Connect to the ProCurve switch servicing the VC-Enet uplink ports and enter the following commands.. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 5 Scenario 1-7 - ProCurve command line configuration (simple network) Command...
Page 219 Scenario 2-1– ProCurve command line configuration (VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS)) Connect to the ProCurve switch servicing the VC-Enet uplink ports and enter the following commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 6 Scenarios 2-1 - ProCurve command line configuration (802.1Q) Command...
Page 220 Scenario 2-2 & 2-3 – ProCurve command line configuration (VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS)) Connect to the ProCurve switch servicing the VC-Enet uplink ports and enter the following commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 7 Scenarios 2-2 through 2-3 - ProCurve command line configuration (802.1Q) Command...
Page 221 Scenario 2-4 – ProCurve command line configuration (VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and vNets) Connect to the ProCurve switch servicing the VC-Enet uplink ports and enter the following commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 8 Scenario 2-4 ProCurve command line configuration (802.1Q) Command...
Page 222 Scenario 3-1– ProCurve command line configuration (Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP)) Connect to the ProCurve switch servicing the VC-Enet uplink ports and enter the following commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 9 Scenario 3-1 - ProCurve command line configuration (untagged VLANs) Command...
Page 223 Scenario 3-2 – ProCurve command line configuration (VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS)) Connect to the ProCurve switch servicing the VC-Enet uplink ports and enter the following commands. NOTE: If t w o s w it ch es a r e b ein g u s ed , is s u e t h e s a m e com m a n d s on t h e s econ d s w it ch . Table 9 Scenarios 3-2 - ProCurve command line configuration (802.1Q) Command...
Page 224: Appendix C: Acronyms And Abbreviations
Appendix C: Acronyms and abbreviations Term Definition Auto Port Speed** Let VC automatically determine best Flex NIC speed Flex-10 NIC settings written to the server hardware by VC/OA when the server is power oof. CLP String Read by the server hardware upon power in. Custom Port Speed** Manually set Flex NIC speed (up to Maximum value defined) Dynamic Control Channel.
Page 225 Smart Link A feature that, when enabled, configures a Virtual Connect network so that if all external uplinks lose link to external switches, Virtual Connect will drop the Ethernet link on all local server blade Ethernet ports connected to that network. Trunking (Cisco) 802.1Q VLAN tagging Trunking (Industry)
Page 226: Appendix D: Useful Vc Cli Command Sets
Appendix D: Useful VC CLI Command sets The following are a collection of useful VC CLI commands. These CLI commands and many more are documented in detail in Virtual Connect Manager Command Line Interface Version 1.31 (or later) User Guide. The following CLI commands can be copied and pasted into an SSH session with the VCM and will apply immediately upon paste.
Page 227 set enet-vlan PrefSpeedType=Custom PrefSpeed=500 MaxSpeedType=Custom MaxSpeed=2500 #Add additional User to VCM, creates User jimbo add user jimbo password=password privileges=domain,network,server,storage Creating Shared Uplink Sets #Create Shared Uplink Set "Prod-Net" and configure a single uplink on VC module 1, port 2 add uplinkset Prod-Net add uplinkport enc0:1:2 Uplinkset=Prod-Net speed=auto #Add an additional uplink on port 3 to Prod-Net add uplinkport enc0:1:3 Uplinkset=Prod-Net speed=auto...
Page 228 Server Profiles #Create Server Profile App-1, apply this profile to Server Slot 1 and configure NIC 1 to Multiple Networks VLAN_10 and VLAN_20 add profile App-1 -nodefaultenetconn add enet-connection App-1 pxe=Enabled add enet-connection App-1 pxe=Disabled add server-port-map App-1:1 VLAN_10 VLanId=10 add server-port-map App-1:1 VLAN_20 VLanId=20 assign profile App-1 enc0:1 # As an alternative when connection to Multiple Networks, if you want ALL networks...
Page 229 # Create Server Profile Server-1 with Flex-10 NICs configured for specific speeds add profile Server-1 -nodefaultenetconn add enet-connection Server-1 pxe=Enabled Network=Console-101-1 SpeedType=Custom Speed=500 add enet-connection Server-1 pxe=Disabled Network=Console-101-2 SpeedType=Custom Speed=500 add enet-connection Server-1 pxe=Disabled Network=VMotion-102-1 SpeedType=Custom Speed=2500 add enet-connection Server-1 pxe=Disabled Network=VMotion-102-2 SpeedType=Custom Speed=2500 add enet-connection Server-1 pxe=Disabled Network=Prod-103-1 SpeedType=Custom Speed=2000 add enet-connection Server-1 pxe=Disabled Network=Prod-103-2 SpeedType=Custom Speed=2000...

This manual is also suitable for:

Virtual connect

HP Integrity BL890c - i2 Server Manual

Chapter 1: Single Domain/Enclosure Scenarios

Chapter 2: Flex-10 Scenario

Chapter 3: Multi-Enclosure (Stacking) Scenarios

Appendix A: Scenario-Based Cisco Command Line Reference

Appendix B: Scenario-Based Procurve Command Line Reference

Appendix C: Acronyms and Abbreviations

Appendix D: Useful VC CLI Command Sets

Quick Links

Related Manuals for HP Integrity BL890c - i2 Server

Summary of Contents for HP Integrity BL890c - i2 Server

This manual is also suitable for:

Table of Contents