HP Virtual Connect 1Gb Ethernet Cookbook

Transcription

1 Technical white paper HP Virtual Connect 1Gb Ethernet Cookbook (Version 3.30 through 3.60 Firmware Enhancements) Purpose 3 Documentation feedback 3 Introduction to Virtual Connect 1Gb Ethernet Networking 4 New Features: 4 vnets, Tunnels and Shared Uplink Sets 12 Determining Network Traffic Patterns (North/South and East/West) and Virtual Connect network design (Active/Active vs. Active/Standby) 13 Single Domain/Enclosure Scenarios 14 Overview 14 Requirements 14 Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 15 Overview 15 Requirements 15 Installation and configuration 17 Summary 23 Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 26 Overview 26 Requirements 26 Installation and configuration 28 Summary 34 Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling VMware ESX 37 Overview 37 Requirements 37 Configuring Uplinks to a vnet (LACP) 37 Installation and configuration 39 Summary 43 Results 43 1

2 Scenario 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 47 Overview 47 Requirements 47 Configuring Uplinks to a SUS (LACP) 47 Installation and configuration 49 Summary 55 Results 55 Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 57 Overview 57 Requirements 57 Configuring Uplinks to a vnet (LACP) 57 Installation and configuration 59 Summary 66 Results 66 Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 71 Overview 71 Requirements 71 Configuring Uplinks to a vnet (LACP) 71 Installation and configuration 73 Summary 79 Results 79 Appendix A: Scenario-based Cisco command line reference 83 Appendix B: Scenario-based ProCurve command line reference 88 Appendix C: Acronyms and abbreviations 92 Appendix D: Useful VC CLI Command sets 93

3 Purpose The purpose of this Virtual Connect Cookbook is to provide users of Virtual Connect with a better understanding of the concepts and steps required when integrating HP BladeSystem and Virtual Connect components into an existing network. This document will focus specifically on the Virtual Connect 1Gb Ethernet modules as installed in the c7000 BladeSystem enclosure. There is an additional paper, Virtual Connect Flex-10/FlexFabric Cookbook which focuses specifically on Flex-10 and FlexFabric (10 GB) networking scenarios. 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 1Gb Network solutions. Although these scenarios are shown individually, some scenarios could be combined to create a more complex and versatile Virtual Connect environment, such as the combined use of Shared Uplink Sets (SUS) and vnet Tunnels. Existing users of Virtual Connect will quickly realize that as of VC firmware release 3.30 that the selection between Mapped and Tunneled modes are no longer of concern. The capabilities provided in those previously individual modes are now available in the default installation of VC firmware 3.30 and beyond. These capabilities and changes will be discussed in further detail later in this paper. The scenarios as written are meant to be self-contained configurations and do not build on earlier scenarios, with this you may find some repetition or duplication of configuration across scenarios. This paper is not meant to be a complete or detailed guide to Virtual Connect solutions, but is intended to provide the reader with some valid examples of how Virtual Connect 1Gb networking solutions could be deployed within their environments. Many additional configurations or scenarios could also be implemented. Please refer to the following section for additional reference material on Virtual Connect. This paper also focuses on the feature enhancements and updates that have been provided in the 3.30, 3.51 and 3.60 firmware releases. As Virtual Connect firmware release 3.6x will be the final firmware release to be supported on Virtual Connect 1Gb modules, this will be the final release of this paper. Future Virtual Connect enhancement and implementation scenarios will be provided in the Virtual Connect Flex-10/FlexFabric Cookbook which focuses on 10Gb Virtual Connect and FCoE solutions and scenarios. Documentation feedback HP welcomes your feedback. To make comments and suggestions about product documentation, send a message to [email protected]. Include the document title and manufacturing part number. All submissions become the property of HP. Purpose 3

4 Introduction to Virtual Connect 1Gb Ethernet Networking 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). Once the LAN and SAN connections are physically made to the pool of servers, the server administrator uses Virtual Connect management tools (Virtual Connect Manager or Virtual Connect Enterprise Manager) to create an Interconnect module connection profile for each server. It is important to note that Virtual Connect firmware release 3.6x will be the final release set to be supported on Virtual Connect 1Gb Ethernet modules. This document will discuss features relevant to the Virtual Connect 1/10 and Virtual Connect 1/10-F modules. It is also equally important to note that the original Virtual Connect 1/10 Ethernet module had gone end of sales life (EOL) in early 2012 and that the Virtual Connect 1/10-F module will go EOL later in New Features: Virtual Connect Firmware 3.30 includes the following new features: Command Line Interface Telemetry Provides improved reporting and metrics from the VC domain and individual VC-Enet modules. New metrics include CPU load, memory utilization, discover information, port statistics, L2 MAC address table, IGMP groups, link aggregation information, VC networks information, interfaces information, throughput information, and module hostname control. Network Access Groups for profile Allows a VC network administrator to define specific subsets of domain networks. Network subsets are then associated with each profile, which limits the network connections to those subsets. Simultaneous tunneled and mapped VLAN connections In earlier versions, these modes were mutually exclusive within a VC domain Increased mapped VLAN capacity The number of VLANs supported in a shared uplink set is increased from 128 to The number of connections on a server downlink has been increased from 28 to 162. Additional CLI and GUI commands have been added to support management of multiple networks with a single command. Note: this enhancement (Increased mapped VLAN capacity) only applies to 10Gb VC Domains only. Enhanced port status Provides additional status and information on link status Simplified iscsi boot setup Automatically retrieves parameters from HP 4000 SAN solutions and attaches them to server profiles. This feature significantly reduces required manual entries. GUI Profile Wizard support (Ethernet, iscsi, FC, FCoE) New CLI commands New CLI commands to support save and restore configurations, copy profiles, and the show config command that generates a CLI script that can be used to restore the current VC domain configuration Native IE8 browser support Running in IE7 emulation is no longer required Loop avoidance Specific detection of Cisco PVST BPDUs emerging from servers are added, and when found, result in disabling of the server-facing physical port generating them and an administrative alert being sent. IGMPv3 snooping support (no support for Source-specific multicast) TACACS+/RADIUS role based security User authentication, Command Authorization, and Command logging Updated SNMP MIBs Severity level added to all traps (alerts) to improve notification Support for user-defined login screen notice (typically a security message) Support Log File Compression has been added, which provides the ability to capture more support information Notification of unsupported cables The HP VC FlexFabric 10Gb/24-Port module does not support DAC cables longer than 5m for uplink ports X1 X4. Starting with this release, a port status of "unsupported"

5 is displayed if an unsupported DAC cable is attached to any of the uplink ports X1 X4. This limitation is documented in the QuickSpecs and the HP Virtual Connect for c-class BladeSystem Setup and Installation Guide. Improved integration with HP System Insight Manager. The HP VC 8Gb 20-Port FC Module firmware is now correctly returning several important elements of the HP MIBs as part of the System Insight Manager discovery. Virtual Connect Firmware 3.51 includes the following new features: Enhanced support for network loop protection Support for Internet Explorer 9.x Support for Mozilla Firefox 6.x and 7.x Virtual Connect Firmware 3.60 includes the following new features: Support for new hardware: HP ProLiant BL420c Gen8 Server Blade HP ProLiant BL465c Gen8 Server Blade Included in HP SPP, the baseline for most ProLiant environments Support for Mozilla Firefox 9.x and ESR 10xAdd VC 3.60 features Please refer to the VC 3.60 Release notes for further information 3.60 Release Notes /3.60 CLI User Guide /3.60 User Guide Additional Virtual Connect Reference Material Link to HP Virtual Connect technology site, provides a great deal of reference information on Virtual connect, Flex-10 and FlexFabric. Link to Overview of HP Virtual Connect technology Link to HP Virtual Connect for c-class BladeSystem Setup and Installation Guide Link to HP Flex-10 technology with FlexFabric components Link to HP BladeSystem Network Reference Architecture - FlexFabric and VMware vsphere 5 Link to Virtual Connect User, Setup and CLI Guides ng=en&cc=us&docindexid=64180&taskid=101&prodtypeid= &prodseriesid= Introduction to Virtual Connect 1Gb Ethernet Networking 5

6 Virtual Connect Flex-10/FlexFabric Cookbook Virtual Connect can be used to support both Ethernet and FCoE connections. The Virtual Connect Flex- 10/FlexFabric Cookbook is provided with basic Virtual Connect configurations for both 10Gb and 10Gb with FCoE solutions, whereas the Virtual Connect 1Gb Ethernet Cookbook (this paper) provides 1Gb scenarios only. If you are new to Virtual Connect and will be utilizing Flex-10 or FlexFabric it is highly recommended that you also review that document. This document replaces the original Virtual Connect FlexFabric Cookbook, with both FlexFabric (FCoE) and Flex-10 scenarios. Virtual FlexFabric/Flex-10 Cookbook Virtual Connect Fibre Channel Cookbook Virtual Connect can be used to support both Ethernet and Fibre Channel connections; however, this guide is focused completely on the Ethernet configuration. For Fibre Channel connectivity, please refer to the Virtual Connect Fibre Channel Cookbook Virtual Connect iscsi Cookbook Virtual Connect can be used to support iscsi accelerated connections, including iscsi boot, however, this guide is focused completely on the Ethernet and iscsi configuration. For iscsi connectivity, please refer to the Virtual Connect iscsi Cookbook Virtual Connect 1/10-F module Uplink Port Mappings It is important to note how the external uplink ports on the Flex-10 module are configured. The graphic below outlines the type and speed each port can be configured as. Ports X1 and X2; Are XFP 10Gb Optical ports Ports S1 and S2; Are 1Gb SFP ports and can be used for 1Gb Optical or RJ45 copper, these ports will NOT operate at 100Mb Ports 1 4 1Gb RJ45 ports, will operate at 100Mb The CX-4 connection is shared with port X1, only one of these connections, either the CX-4 or XFP X1, can be used at a time. Figure 1 - Virtual Connect 1/10-F Module port configuration speeds and types.

7 Tunneled VLAN and Mapped VLANS Readers that are familiar with earlier releases of Virtual Connect firmware features will realize that VC 3.30 firmware removed the need to configure VC in Mapped vs. Tunneled mode. As of VC 3.30 firmware release, VC now provides the ability to simultaneously take advantage of the features and capabilities that were provided in either mapped or tunneled modes, there is no need to choose the domain s mode of operation. The key feature gained here is the ability to now use Mapped VLANs (multiple networks) and Tunneled networks within the same profile. Virtual Connect VLAN Support Shared Uplink Set Shared Uplink Sets provide administrators with the ability to distribute VLANs into discrete and defined Ethernet Networks (vnet.) These vnets can then be mapped logically to a Server Profile Network Connection allowing only the required VLANs to be associated with the specific server NIC port. This also allows the flexibility to have various (multiple) network connections for different physical Operating System instances (i.e. VMware ESX host and physical Windows host.) When installing Virtual Connect, the default domain configuration is Legacy VLAN Capacity mode, however, Multiple Networks and the Tunnel mode can still be used simultaneously. After Expanded VLAN Capacity mode is configured, you must delete the VC domain to return to Legacy VLAN Capacity mode. Note: Expanded VLAN Capacity mode is not supported on the following 1Gb based VC Ethernet modules, such as: HP 1/10Gb VC-Enet Module HP 1/10Gb-F VC-Enet Module Legacy VLAN Capacity Legacy VLAN capacity mode allows up to 320 VLANs per domain and 128 VLANs per Shared Uplink Set. In addition, up to 28 VLANs are allowed per server NIC port. Care must be taken not to exceed the limit per physical server port, an error message will be display if this value is exceeded. The following Shared Uplink Set rules apply to legacy capacity mode: 320 VLANs per Virtual Connect Ethernet domain, 128 VLANs per Shared Uplink Set (single uplink port). 28 VLANs per server NIC port The above configuration rules apply only to a Shared Uplink set. If support for additional VLANs is required, a VLAN Tunnel can be configured to support a large number of VLANs. Please see the Virtual Connect Release Notes for future details. Expanded VLAN Capacity New in VC 3.30 Note: Expanded VLAN Capacity mode is not supported on the following 1Gb based VC Ethernet modules, such as: HP 1/10Gb VC-Enet Module HP 1/10Gb-F VC-Enet Module This mode allows up to 1000 VLANs per domain when implementing a Share Uplink Set (SUS). In addition, up to 162 VLANs are allowed per physical server port, with no restriction on how those VLANs are distributed among the server connections mapped to the same physical server port. Care must be taken not to exceed the limit per physical server port. The following Shared Uplink Set rules apply: 1000 VLANs per Virtual Connect Ethernet domain, 162 VLANs per Ethernet server port. The above configuration rules apply only to a Shared Uplink set. If support for a larger numbers of VLANs is required, a VLAN Tunnel can be configured to support a large number of VLANs. Please see the Virtual Connect 3.30 Release Notes for future details. When installing Virtual Connect, the default configuration is Legacy VLAN Capacity, however, Multiple Networks and the Tunnel mode can now be used simultaneously. After Expanded VLAN Capacity mode is configured, you must delete the VC domain to return to Legacy VLAN Capacity mode. Introduction to Virtual Connect 1Gb Ethernet Networking 7

8 If the above noted 1Gb VC modules are inserted into an enclosure that is in Expanded VLAN Capacity mode, they are marked as incompatible. If these modules are installed in an enclosure, converting to Expanded VLAN Capacity mode will not be permitted. Figure 2 - Configuring Expanded VLAN Capacity support. MAC Cache Failover When a VC-Enet uplink 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. Enabling Fast MAC Cache Failover causes Virtual Connect to transmit Ethernet packets on newlyactive 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 (5 seconds recommended) and completes in about 1 minute. When implementing Virtual Connect in an Active/Standby configuration, where some of the links connected to a VC Network (whether a SUS or vnet) are in standby, MAC Cache Fail-over would be employed to notify the switch as a link transitions from Standby to Active within Virtual Connect. Note: Be sure to set switches to allow MAC addresses to move from one port to another without waiting for an expiration period or causing a lock out. Network Access Groups (NAG) Before VC 3.30, any server profile could be assigned any set of networks. If policy dictated that some networks should not be accessed by a system that accessed other networks (for example, the Intranet and the Extranet or DMZ networks) there was no way to enforce that policy automatically. With VC 3.30 and later, network access groups are defined by the network administrator and associated with a set of networks that can be shared by a single server. Each server profile is associated with one network access group. A network cannot be assigned to the server profile unless the profile is a member of the network access group associated with that network. A network access group can contain multiple networks. Up to 128 network access groups are supported in the domain. Ethernet networks and server profiles that are not assigned to a specific network access group are added to the domain Default network access group automatically. The Default network access group is predefined by VCM and cannot be removed or renamed. If you are updating to VC 3.30, all current networks are added to the Default network access group and all server profiles are set to use the Default network access group. Network communication within the network access group behaves similarly to earlier versions of VC firmware, because all profiles can reach all networks.

9 If you create a new network access group, NetGroup1, and move existing networks from the Default network access group to NetGroup1, then a profile that uses NetGroup1 cannot use networks included in the Default network access group. Similarly, if you create a new network and assign it to NetGroup1 but not to the Default network access group, then a profile that uses the Default network access group cannot use the new network. Therefore, an administrator cannot inadvertently, or intentionally, place a server on networks that reside in different Network Access Groups. Private Networks The Private Networks option provides extra networking security. When checked, the network is configured so that all server ports connected to it cannot communicate with each other within the Virtual Connect domain. All packets from servers are sent through the VC domain and out the uplink ports only. Servers on the network can only communicate with each other through an external Layer 3 router that redirects the traffic back to the VC Domain. IGMP Snooping The IGMP Snooping feature enables VC-Enet modules to monitor (snoop) the IGMP IP multicast membership activities and configure hardware Layer 2 switching behavior of multicast traffic to optimize network resource usage. IGMP v1, v2, and v3 snooping are supported. The IGMP Snooping idle timeout interval is set to 260 seconds by default. This value is the "Group Membership Interval" value as specified by IGMP v2 specification (RFC2236). For optimum network resource usage, set the interval to match the configuration on the customer network's multicast router settings. Network loop protection To avoid network loops, Virtual Connect first verifies that only one active uplink exists per network from the Virtual Connect domain to the external Ethernet switching environment. Second, Virtual Connect makes sure that no network loops are created by the stacking links between Virtual Connect modules. One active link A VC uplink set can include multiple uplink ports. To prevent a loop with broadcast traffic coming in one uplink and going out another, only one uplink or uplink LAG is active at a time. The uplink or Link Aggregation Group (LAG) with the greatest bandwidth should be selected as the active uplink. If the active uplink loses the link, then the next best uplink is made active. No loops through stacking links If multiple VC-Enet modules are used, they are interconnected using stacking links, which might appear as an opportunity for loops within the VC environment. For each individual network in the Virtual Connect environment, VC blocks certain stacking links to ensure that each network has a loop-free topology. 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, which provides the ability to manage, control or prevent a loop at the FlexNIC. 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. 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: Introduction to Virtual Connect 1Gb Ethernet Networking 9

10 PVST+ BPDUs 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. Figure 3 Mac Cache Fail-over, IGMP Snooping and Network Loop Protection are all configurable under the Ethernet Settings, Advanced settings, Other tab.

11 Bulk VLAN Creation In addition to providing support for a greater number of VLANs, VC now provides the ability to create several VLANs, within a Shared Uplink Set (SUS), in a single operation. Using the Bulk VLAN creation feature in the GUI or the add network-range command in the CLI many VLANs can be added to a SUS in a single operation. In addition, copying an existing SUS is also now possible. When creating an Active/Active SUS configuration, you can create the first SUS, and then copy it. Figure 4 - Example of adding multiple VLANs to a SUS through the GUI. Here is an example of creating a shared Uplink Set using the CLI command add network-range to create the more than 50 VLANs shown above. add uplinkset VLAN-Trunk-1 add uplinkport enc0:1:x5 Uplinkset=VLAN-Trunk-1 speed=auto add uplinkport enc0:1:x6 Uplinkset=VLAN-Trunk-1 speed=auto add network-range -quiet Uplinkset=VLAN-Trunk-1 NamePrefix=VLAN- NameSuffix=-1 VLANIds= , State=enabled PrefSpeedType=auto SmartLink=enabled Note: VC Domains with 1Gb modules, and VC releases prior to 3.30 support(ed) only 320 VLANs per domain, and 128 VLANs per Shared Uplink Set, in addition, to create each VLAN with SmartLink enabled required two lines of script per VLAN. In the example above, over 50 VLANs are created in a single statement, with Smart Link enabled. Copying a Shared Uplink Sets Virtual Connect provides the ability to copy a Shared Uplink Set. This can be very handy when defining an Active/Active Shared Uplink Set design. You simply create the first SUS, and then copy it. For example, after creating Shared Uplink Set VLAN-Trunk-1 you can copy it to VLAN-Trunk-2. You will then need to add uplinks to the new SUS and ensure all networks have SmartLink enabled. This can be accomplished as follows; copy uplinkset VLAN-Trunk-1 VLAN-Trunk-2 from VlanStr=1 tovlanstr=2 replace=last add uplinkport enc0:2:x5 Uplinkset=VLAN-Trunk-2 speed=auto add uplinkport enc0:2:x6 Uplinkset=VLAN-Trunk-2 speed=auto set network-range -quiet Uplinkset=VLAN-Trunk-1 VLANIds= , SmartLink=enabled Introduction to Virtual Connect 1Gb Ethernet Networking 11

12 vnets, Tunnels and Shared Uplink Sets vnet There are two types of vnets. The first is a simple vnet that will pass only untagged frames. The second is a vnet tunnel which will pass tagged frames for one or many VLANs. The vnet is a simple network connection between one or many server NICs to one or many uplink ports. A vnet could be used to connect a single VLAN, no tagging, to one or many server NICs, if this network is part of a VLAN, by configuring the upstream switch port as an access or untagged port, by extension, any server connected to this vnet would reside in that VLAN, but would not need to be configured to interpret the VLAN tags. Benefits of a vnet vnet Tunnel A vnet can be setup to provide connectivity without the need to configure VLANs within VC. A tunneled vnet will pass VLAN tagged frames, without the need to interpret or forward those frames based on the VLAN tag. Within a tunneled vnet the VLAN tag is completely ignored by Virtual Connect and the frame is forwarded to the appropriate connection (server NIC[s] or uplinks) depending on frame direction flow. In this case, the end server would need to be configured to interpret the VLAN tags. This could be a server with a local operating system, in which the network stack would need to be configured to understand which VLAN the server was in, or a virtualization host with a vswitch supporting multiple VLANs. The tunneled vnet can support up to 4096 VLANs. Benefits of a vnet Tunnel A vnet tunnel can present one or many VLANs to a server NIC. When additional VLANs are added to the upstream switch port, they are made available to all server NICs connected to the VLAN Tunnel, with no changes required within Virtual Connect. All presented VLANs are passed through the tunnel, unchanged. A vnet Tunnel can pass an unlimited number of VLANs (4096) and is not constrained by the VLAN limits of the Shared Uplink Set. Shared Uplink Set (SUS) The SUS provides the ability to support VLAN tagging and forward frames based on the VLAN tags of those frames. The SUS connects one or many server NICs to one or many uplink ports. A SUS would be configured for the specific VLANs it will support. If support for additional VLANs is required, those VLANs need to be configured within the SUS. When connecting a server NIC to a network within a SUS, there are two choices provided. The key difference between these two options is the state in which the frame is passed to the server NIC. When configuring a server NIC for network connection; 1. Selecting a single network which would be mapped to a specific VLAN. 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. 2. Selecting multiple networks which would provide connectivity to one or more VLANs. The Map VLAN Tags feature provides the ability to use a Shared Uplink Set to present multiple networks to a single NIC. If you select Multiple Networks when assigning a Network to a server NIC, you will have the ability to configure multiple Networks (VLANS) on that server NIC. At this point VC tags ALL the packets presented to the NIC unless the Native check box is selected for one of the networks, in which case packets from this network (VLAN) will be untagged, and any untagged packets leaving the server will be placed on this Network (VLAN).

13 With Mapped VLAN Tags, you can create a Shared Uplink Set that contains ALL the VLANs you want to present to your servers, then present only ONE network (the one associated with the VLAN we want the server NIC in) to the Windows, LINUX or the ESX Console NIC, then select Multiple Networks for the NIC connected to the ESX vswitch and select ALL the networks that we want presented to the ESX host vswitch. The vswitch will then break out the VLANs into port groups and present them to the guests. Using Mapped VLAN Tags minimizes the number of uplinks required. Benefits of a SUS A Shared Uplink Set can be configure to support both tagged and un-tagged network traffic to a server NIC, which simplifies the overall configuration and minimizes the number of uplink cables required to support the network connections. Determining Network Traffic Patterns (North/South and East/West) and Virtual Connect network design (Active/Active vs. Active/Standby) When choosing which Virtual Connect network design to use, consider the type of network traffic this enclosure will need to support. For example, will there be much server to server traffic needed within the enclosure, or is the traffic flow mainly in/out bound of the enclosure. Network traffic patterns, North/South vs. East/West, should be considered when designing a Virtual Connect solution as network connectivity can be implemented in a way to maximize the connected bandwidth and/or minimize the need for server to server traffic to leave the enclosure when communicating on the same VLAN within the enclosure. For example; if the solution being implemented will have a high level of in/out or North/South traffic flow, an Active/Active network design would likely be the better solution. However, if a greater level of network traffic is between systems within the same enclosure/vlan, such as a multi-tiered application, then a better design may be Active/Standby, as this would minimize or eliminate any server to server communications from leaving the enclosure. The single SUS is a popular configuration when supporting primarily East/West traffic patterns. No matter which NIC a server is active on, if talking to another server within the enclosure on the same VLAN, the traffic will remain within the VC/enclosure. Introduction to Virtual Connect 1Gb Ethernet Networking 13

14 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. Where possible, examples for Windows and/or VMware will also be provided. Requirements This chapter will utilize a single HP BladeSystem c7000 enclosure with TWO Virtual Connect Ethernet modules and a half height BladeSystem Server. The server will connect to the Virtual Connect models with two 1Gb NICs. NIC 1 will connect to the VC module in Bay 1 and NIC 2 will connect to the VC module in Bay 2. A pair of managed network switches should also be provided, the switches should also be trunked together. It is assumed that a Virtual Connect Domain has been created either through the GUI or a CLI script and no VC Networks, uplink sets or Server Profiles have been created. Figure 5 - c7000 Enclosure with Sixteen (16) Half Height Gen 8 BladeSystem servers, two Virtual Connect 1/01-F Ethernet modules in rear bays 1 & 2, and two Virtual Connect 4Gb FC modules in rear Bays 3 & 4.

15 Scenario 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. No special upstream switch configuration is required as the switch is in the factory default configuration, typically configured as Access ports. When configuring Virtual Connect, we can provide several ways to implement network fail-over or redundancy. One option would be to connect TWO uplinks to a single vnet; those two uplinks would connect from different Virtual Connect modules within the enclosure and could then connect to the same upstream switch or two different upstream switches, depending on your redundancy needs. An alternative would be to configure TWO separate vnets, each with a single uplink configured and connection to two switches. Each option has its advantages and disadvantages. We will review the first option in this scenario. In addition, several vnets can be configured to support the required networks to the servers within the BladeSystem enclosure. These networks could be used to separate the various network traffic, such as iscsi, backup, VMotion from production network traffic. The single vnet is a popular configuration when supporting primarily East/West traffic patterns. No matter which NIC a server is active on, if talking to another server within the enclosure on the same vnet, the traffic will remain within VC/the enclosure. Requirements In order to implement this scenario, an HP BladeSystem c7000 enclosure with one or more server blades and TWO Virtual Connect 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 and Spanning Tree (STP) is not required. Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 15

16 Figure 6 - 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. Figure 7 - 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. A single vnet is configured and connected to both switches. Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 16

17 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: The switch ports are configured as ACCESS ports, either presenting the Default VLAN or a specific VLAN and will forward (only) untagged frames. As an alternative, if the switch ports were configured as TRUNK ports and forwarding multiple VLANS, Virtual Connect would forward those tagged frames to the host NICs configured for this network. The connected host would then need to be configured to interpret those VLAN tags. Note: for a vnet to forward TAGGED frames, vnet Tunneling must be enabled. vnet Tunneling will be discussed in a later Scenario. This scenario assumes the switch port is configured as an Access port and the frames are presented to Virtual Connect as untagged. Configuring the VC module VC CLI commands Physically connect Port 1 of Network switch 1 to Port 1 on the VC module in Bay 1. 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. In addition to the GUI, many of the configuration settings within VC can also be accomplished via a CLI command set. In order to connect to VC via a CLI, open an SSH connection to the IP address of the active VCM. Once logged in, VC provides a CLI with help menus. Throughout this scenario the CLI commands to configure VC for each setting will also be provided. 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. 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. 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 Ether the Network Name of vnet-prod Note; Do NOT select any of the options (ie; Smart Link, Private Networks etc.) Select Add Port, then add the following ports; Enclosure 1, Bay 1, Port 1 Enclosure 1, Bay 2, Port 1 Leave Connection Mode as Auto Select Apply Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 17

18 Note: By connecting TWO Uplinks from this vnet we have provided a redundant path to the network. As each uplink originates from a different VC module, one uplink will be Active and the second will be in Standby. This configuration provides the ability to lose an uplink cable, network switch or depending on how the NICs are configured at the server (teamed or un-teamed), even a VC module. Note: In this configuration Smartlink should NOT be enabled. Smartlink is used to turn off downlink ports within Virtual Connect, if ALL available uplinks to a vnet or SUS are down. We will use Smartlink in a later scenario. Defining a new vnet via CLI The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create the vnet "vnet-prod" and configure uplinks as discussed above add Network vnet-prod add uplinkport enc0:1:1 Network=vNet-PROD speed=auto add uplinkport enc0:2:1 Network=vNet-PROD speed=auto set network vnet-prod SmartLink=Disabled Figure 8 - 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, which also provides a hyperlink to additional information about the connect switch. 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 Create a server profile called App-1 In the Network Port 1 drop down box, select vnet-prod In the Network Port 2 drop down box, select vnet-prod In the Assign the Profile to a Server Bay, select Bay 1 and apply Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 18

19 Defining a Server Profile with NIC Connections, 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 to server bay 1 add profile App-1 -nodefaultenetconn add enet-connection App-1 pxe=enabled add enet-connection App-1 pxe=disabled set enet-connection App-1 1 Network=vNet-PROD set enet-connection App-1 2 Network=vNet-PROD assign profile App-1 enc0:1 Figure 9 - Define Server Profile (App- 1). Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 19

20 Figure 10 - Server Profile View Bay 1. Optionally Configuring Additional Uplinks to a vnet (LACP) If additional uplink bandwidth or redundancy is required, uplinks can be added it 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) which 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. When some of the uplinks configured within a vnet connect a VC module to different upstream switches, or from multiple VC modules to a single or multiple switches, some links will be active and the remaining will be Standby, potentially providing additional bandwidth, using Link Aggregation Protocol (LACP ad), as well as increase availability. Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 20

21 Figure 11- Shows two Ethernet uplinks from Port 1 and 2 on Module 1 to Port 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. Figure 12 - Logical View; Shows two Ethernet uplinks from Ports 1& 2 of each VC module to the network switch. A single vnet is configured and connected to both switches. Switch configuration (LACP) 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: Note: when adding the additional uplinks, the switch ports connected to Virtual Connect will need to be configured for LACP and in the same Link Aggregation Group. Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 21

22 Adding uplinks to an existing vnet via GUI Edit the vnet named vnet-prod In the left pane of the Virtual Connect Manager screen, click on the Network vnet-prod Select Add Port, then add the following ports; Enclosure 1, Bay 1, Port 2 Enclosure 1, Bay 2, Port 2 Leave Connection Mode as Auto Select Apply Note: By connecting FOUR Uplinks from this vnet we have provided additional bandwidth and a redundant path to the network as two uplinks will be active and two will be in standby. 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" and configure uplinks as discussed above add uplinkport enc0:1:2 Network=vNet-PROD speed=auto add uplinkport enc0:2:2 Network=vNet-PROD speed=auto set network vnet-prod SmartLink=Disabled Figure 13 - 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. Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 22

23 Figure 14 - 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 trouble establishing an active/active connection, confirm the LAG ID. Figure 15 - Link aggregation confirmed - Bay 2. Summary We created a couple different Virtual Connect Network solutions; based 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. When VC profile App-1 is applied to the server in bay1 and is powered up, it has one NIC through each virtual connect module connected to vnet-prod, which connects to the network infrastructure through a pair of 1Gb uplinks. These NICs could now be configured as individual NICs (Figure 16) with their own IP address or as a pair of TEAMED NICs (Figure 17). Either NIC could be active. As a result, this server could access the network through either NIC or either uplink cable, depending on which is active at the time. When additional bandwidth was required, additional uplinks were added to the existing vnet, this process had no effect on the server profile. As additional servers are added to the enclosure, simply create additional profiles, or copy existing profiles, configure the NICs for vnet-prod and apply them to the appropriate server bays. Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 23

24 Results The following graphics provides examples of a Windows 2008R22 Server with TWO NICs connected to the network. Initially, each NIC has its own TCP/ /IP address, either or both NICs could be actively working on the network. Additional examples are shown when using NIC teaming. Figure 16 - Both NICs for Profile App-1are connected to the network through vnet-prod. The following graphics provide an example of a Windows 2008R2 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. If a VC module where to fail, then NIC teaming would fail-over to the standby NIC. Figure 17 - Both NICs, using the HP Network Configuration Utility. Scenario 1 Simple vnet with Active/ /Standby Uplinks and Optional Link Aggregationn 802.3ad (LACP) - Windows 24

25 Figure 18 - Both NICs for Profile App-1are teamed and connected to the network through vnet- PROD. Scenario 1 Simple vnet with Active/Standby Uplinks and Optional Link Aggregation 802.3ad (LACP) - Windows 25

26 Scenario 2 Multiple Simple Networks with Active\Active Uplinks 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. No special upstream switch configuration is required as the switch is in the factory default configuration. As discussed in scenario 1, when configuring Virtual Connect, we can provide several ways to implement network fail-over or redundancy. In this scenario we will configure TWO separate vnets, each with a single uplink configured from each VC module. We will later connect additional uplinks, to provide additional bandwidth. In addition, several vnets can be configured to support the required networks to the servers within the BladeSystem enclosure. These networks could be used to separate the various network traffic, such as iscsi, backup, VMotion from production network traffic. The dual vnet is a popular configuration when supporting primarily North/South traffic patterns, as this configuration maximizes the use of all external connections. Requirements In order to implement this scenario, an HP BladeSystem c7000 enclosure with one or more server blades and TWO Virtual Connect 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. Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 26

27 Figure 19 - 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. Figure 20 - 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. Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 27

28 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: The switch ports are configured as ACCESS ports, either presenting the Default VLAN or a specific VLAN and will forward (only) untagged frames. As an alternative, if the switch ports were configured as TRUNK ports and forwarding multiple VLANS, Virtual Connect would forward those tagged frames to the host NICs configured for this network. The connected host would then need to be configured to interpret those VLAN tags. Note: for a vnet to forward TAGGED frames, vnet Tunneling must be enabled. vnet Tunneling will be discussed in a later Scenario. This scenario assumes the switch port is configured as an Access port and the frames are presented to Virtual Connect as untagged. Configuring the VC module VC CLI commands Physically connect Port 1 of Network switch 1 to Port 1 on the VC module in Bay 1. 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. In addition to the GUI many of the configuration settings within VC can be also be accomplished via a CLI command set. In order to connect to VC via a CLI, open an SSH connection to the IP address of the active VCM. Once logged in, VC provides a CLI with help menus. Throughout this scenario the CLI commands to configure VC for each setting will also be provided. Defining a new vnet via GUI Create a vnet and name it vnet-prod-1 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 Ether the Network Name of vnet-prod-1 Note; Do NOT select any of the options (ie; Smart Link, Private Networks etc.) Select Add Port, then add the following ports; Enclosure 1, Bay 1, Port 1 Leave Connection Mode as Auto Select Apply Create a vnet and name it vnet-prod-2 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 Ether the Network Name of vnet-prod-2 Note; Do NOT select any of the options (ie; Smart Link, Private Networks etc.) Select Add Port, then add the following ports; Enclosure 1, Bay 2, Port 1 Leave Connection Mode as Auto Select Apply Note: By connecting ONE Uplink from each vnet we have provided a redundant path to the network. As each uplink originates from a different VC module and provided connectivity for its own vnet. All uplinks will be Active. This configuration provides the ability to lose an uplink cable, network switch Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 28

29 or depending on how the NICs are configured at the server (teamed or un-teamed), even a VC module. Note: In this configuration Smartlink should be enabled. Smartlink is used to turn off downlink ports within Virtual Connect, if ALL available uplinks to a vnet or SUS are down, thus initiating a teaming fail-over. Defining a new vnet via CLI The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect. # Create the vnet "vnet-prod-1" and configure uplinks as discussed above add Network vnet-prod-1 add uplinkport enc0:1:1 Network=vNet-PROD-1 speed=auto set network vnet-prod-1 SmartLink=Enabled # Create the vnet "vnet-prod-2" and configure uplinks as discussed above add Network vnet-prod-2 add uplinkport enc0:2:1 Network=vNet-PROD-2 speed=auto set network vnet-prod-2 SmartLink=Enabled Figure 21 - 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. 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. Create a server profile called App-1 In the Network Port 1 drop down box, select vnet-prod-1 In the Network Port 2 drop down box, select vnet-prod-2 In the Assign the Profile to a Server Bay, select Bay 1 and apply Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 29

30 Defining a Server Profile with NIC Connections, 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 to server bay 1 add profile App-1 -nodefaultenetconn add enet-connection App-1 pxe=enabled add enet-connection App-1 pxe=disabled set enet-connection App-1 1 Network=vNet-PROD-1 set enet-connection App-1 2 Network=vNet-PROD-2 assign profile App-1 enc0:1 Figure 22 - Define Server Profile (App- 1). Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 30

31 Figure 23 - Server Profile View Bay 1. Optionally Configuring Additional Uplinks to a vnet (LACP) If additional uplink bandwidth or redundancy is required, uplinks can be added it 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) which 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. When some of the uplinks configured within a vnet connect a VC module to different upstream switches, or from multiple VC modules to a single or multiple switches, some links will be active and the remaining will be Standby, potentially providing additional bandwidth, using Link Aggregation Protocol (LACP ad), as well as increase availability. Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 31

32 Figure 24 - Shows two Ethernet uplinks from Port 1 and 2 on Module 1 to Port 1 and 2 on the first network switch and two uplinks from ports 1 and 2 on Module 2 too Ports 1 and 2 on the second network switch. Figure 25 - Logical View; Shows two Ethernet uplinks from Ports 1& 2 of each VC module to the network switch. Switch configuration (LACP) 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: Note: when adding the additional uplinks, the switch ports connected to Virtual Connect will need to be configured for LACP and in the same Link Aggregation Group. Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 32

33 Adding uplinks to an existing vnet via GUI Edit the vnet named vnet-prod-1 In the left pane of the Virtual Connect Manager screen, click on the Network vnet-prod-1 Select Add Port, then add the following ports; Enclosure 1, Bay 1, Port 2 Leave Connection Mode as Auto Enable Smart Link Select Apply Edit the vnet named vnet-prod-2 In the left pane of the Virtual Connect Manager screen, click on the Network vnet-prod-2 Select Add Port, then add the following ports; Enclosure 1, Bay 2, Port 2 Leave Connection Mode as Auto Enable Smart Link Select Apply Note: By connecting FOUR Uplinks from this vnet we have provided additional bandwidth and a redundant path to the network as two uplinks will be active and two will be in standby. 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" and configure uplinks as discussed above add uplinkport enc0:1:2 Network=vNet-PROD-1 speed=auto set network vnet-prod-1 SmartLink=Enabled # Edit the vnet "vnet-prod-2" and configure uplinks as discussed above add uplinkport enc0:2:2 Network=vNet-PROD-2 speed=auto set network vnet-prod-2 SmartLink=Enabled Figure 26 - Adding uplinks to an existing vnet (vnet-prod-1). Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 33

34 Note: The Port Status and Connected to information. If the connected switch supports LLDP, the connected to information should be displayed as below. Figure 27 - 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 trouble establishing an active/active connection, confirm the LAG ID and verify switch configuration for the ports connecting to each VC module. Summary We created a couple different Virtual Connect Network solutions; based initially for availability with a higher degree of north/south traffic, both uplinks were active. We later added two additional links; this increased the network bandwidth to the Virtual Connect network, while still maintaining availability. When VC profile App-1 is applied to the server in bay1 and is powered up, it has one NIC through each virtual connect module, NIC 1 is connected to vnet-prod-1, which connects to the network infrastructure through a pair of 1Gb uplinks. NIC 2 is connected to vnet-prod-2, which connects to the alternate switch through two 1Gb uplinks. These NICs could now be configured as individual NICs (Figure 28) with their own IP address or as a pair of TEAMED NICs (Figure 29-30). Either NIC could be active. As a result, this server could access the network through either NIC or either uplink cable, depending on which is active at the time. When additional bandwidth was required, additional uplinks were added to the existing vnets, this process had no effect on the server profile. As additional servers are added to the enclosure, simply create additional profiles, or copy existing profiles, configure the NICs for vnet-prod-1 and vnet-prod-2 and apply them to the appropriate server bays. Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 34

35 Results The following graphics provides examples of a Windows 2008R22 Server with TWO NICs connected to the network. Initially, each NIC has its own TCP/ /IP address, either or both NICs could be actively working on the network. Additional examples are shown when using NIC teaming. Figure 28 - Both NICs for Profile App-1are connected to the network through vnet-prod 1 and vnetprod-2 networks. The following graphics provide an example of a Windows 2008R2 Server with TWO NICs teamed and connected to the network. One NIC will be active, the other in standby, in the event of an Uplink or switch failure, VC would fail-over the uplinks and the server would not be affected by the failure, however, if the VC module with the active uplinks were to fail, the teaming software will fail the NIC over to the alternate path, as required. Figure 29 - Both NICs, using the HP Network Configuration Utility. Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 35

36 Figure 30 - Both NICs for Profile App-1are teamed and connected to the network through vnet- PROD-1 and vnet-prod-2. Scenario 2 Multiple Simple Networks with Active\Active Uplinks Link Aggregation 802.3ad (LACP) - Windows 36

37 Scenario 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 Tunnel. The vnet Tunnel will accept and forward tagged frames between servers and uplinks. With a vnet Tunnel Virtual Connect does not make forwarding decisions based on the VLAN Tag, instead all server NICs connected to the vnet Tunnel will receive ALL frames, much like a VLAN Trunked switch port. In this scenario, the upstream network switch is configured to pass multiple VLANs to two ports on each VC module. The upstream switch ports will be configured as trunk ports for several VLANs, (VLAN 1, and ). Note: VLAN 101 will be configured as untagged as this VLAN will be used for console and management access. The dual vnet is a popular configuration when supporting primarily North/South traffic patterns, as this configuration maximizes the use of all external connections. Requirements In order to implement this scenario, an HP BladeSystem c7000 enclosure with one of more server blades and TWO Virtual Connect 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. Configuring Uplinks to a vnet (LACP) When all uplinks configured within a vnet connect a VC module to an upstream switch, ALL links could 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). When some of the uplinks configured within a vnet connect a VC module to different upstream switches, some links will be active and the remaining will be Standby, providing additional bandwidth and/or availability, using Link Aggregation Protocol (LACP ad). Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling VMware ESX 37

38 Figure 31 - 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. Figure 32 - Logical View; Shows two Ethernet uplinks from Portss 1&2 of each VC module to the network switches. Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP)) with VLAN Tunneling VMware ESX 38

39 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: The upstream switch ports are configured as TRUNK ports, presenting VLANs 1, and Note: VLAN 101 is set to default (untagged). The upstream switch ports are configured within the same Link Aggregation Group. When adding the additional uplinks to the vnet, the switch ports connected to Virtual Connect will need to be configured for LACP and configured for the same Link Aggregation Group. Configuring the VC module Physically connect Ports 1 and 2 of the first network switch to Ports 1 and 2 on the VC module in Bay 1. Physically connect Ports 1 and 2 of the second network switch to Ports 1 and 2 of the VC module in Bay 2, if you have only one network switch, connect the second VC module cables to alternates port on the same switch. This will NOT create a network loop and does not require Spanning Tree to be configured. VC CLI commands Many of the configuration settings within VC can be also be accomplished via a CLI command set. In order to connect to VC via a CLI, open an SSH connection to the IP address of the active VCM. Once logged in, VC provides a CLI with help menus. Through this scenario the CLI commands to configure VC for each setting will also be provided. Defining a new vnet via GUI Create a vnet and name it vnet-prod-1 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 Ether the Network Name of vnet-prod-1 Note; Do NOT select any of the options (ie; Smart Link, Private Networks etc.) Select Add Port, then add the following ports; Enclosure 1, Bay 1, Port 1 Enclosure 1, Bay 1, Port 2 Enable Smart Link Enable VLAN Tunneling Leave Connection Mode as Auto Select Apply Create a vnet and name it vnet-prod-2 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 Ether the Network Name of vnet-prod-2 Select Add Port, then add the following ports; Enclosure 1, Bay 2, Port 1 Enclosure 1, Bay 2, Port 2 Enable Smart Link Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling VMware ESX 39

40 Enable VLAN Tunneling Leave Connection Mode as Auto Select Apply Note: By connecting ONE Uplink from each vnet we have provided a redundant path to the network. As each uplink originates from a different VC module and provided connectivity for its own vnet. All uplinks will be Active. This configuration provides the ability to lose an uplink cable, network switch or depending on how the NICs are configured at the server (teamed or un-teamed), even a VC module. Note: In this configuration Smartlink should be enabled. Smartlink is used to turn off downlink ports within Virtual Connect, if ALL available uplinks to a vnet or SUS are down, thus initiating a teaming failover. Defining a new vnet via CLI The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create the vnet "vnet-prod-1" and configure uplinks as discussed above add Network vnet-prod-1 add uplinkport enc0:1:1 Network=vNet-PROD-1 speed=auto add uplinkport enc0:1:2 Network=vNet-PROD-1 speed=auto set network vnet-prod-1 SmartLink=Enabled VLanTunnel=Enabled # Create the vnet "vnet-prod-2" and configure uplinks as discussed above add Network vnet-prod-2 add uplinkport enc0:2:1 Network=vNet-PROD-2 speed=auto add uplinkport enc0:2:2 Network=vNet-PROD-2 speed=auto set network vnet-prod-2 SmartLink=Enabled VLanTunnel=Enabled Figure 33 - Define Ethernet Network (vnet-prod-1). NOTE: Enable VLAN Tunneling is check, as well as Smart Link. Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling VMware ESX 40

41 Figure 34 - 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. 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 Create a server profile called ESX-1 In the Network Port 1 drop down box, select vnet-prod-1 In the Network Port 2 drop down box, select vnet-prod-2 In the Assign the Profile to a Server Bays, select Bay 1 and apply Defining a Server Profile with NIC Connections, 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 ESX-1 add profile ESX-1 nodefaultenetconn add enet-connection ESX-1 pxe=enabled add enet-connection ESX-1 pxe=disabled set enet-connection ESX-1 1 Network=vNet-PROD-1 set enet-connection ESX-1 2 Network=vNet-PROD-2 assign profile ESX-1 enc0:1 Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling VMware ESX 41

42 Figure 35 - Define a Server Profile (ESX-1). Figure 36 ESX-1 Profile Bay View. Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling VMware ESX 42

43 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 and vnet-prod-2 respectively, which connects to the network infrastructure through uplinks. These NICs could be configured within the OS as individual NICs with their own IP address or as a pair of TEAMED NICs or connected to the same vswitch. Either NIC could be active. As a result, this server could access the network through either NIC or either set of uplink cables, depending on which NIC is active at the time. When additional bandwidth is required, additional uplinks could be added to each vnet. If additional VLANs need to be supported by these vnets, simply configure the upstream switch ports for the new VLANs, then configure the ESX vswitch with additional port groups to support these VLANs, no additional Virtual Connect configuration is required. As additional servers are added to the enclosure, simply create additional profiles, configure the NICs for vnet-prod-1 and vnet-prod-2 and apply them to the appropriate server bays. Results The following graphic provides an example of an ESX server with TWO NICs connected to the same vswitch, the console is configured for VLAN 101, which was the Default (untagged) VLAN. Additional port groups were configured to support each additional VLAN. VMotion has been configured on VLAN 110 and is tagged. Figure 37 - As VLAN-101 was set as Untagged at the switch port, you need to ensure that the Hypervisor in NOT configured for VLAN tagging. However, if you want to put this server onto a VLAN that is tagged, this setting will need to be configured for that VLAN. Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling VMware ESX 43

44 Figure 38 - Both NICs for Profile ESX-1are connected to the network through vnet=prod-1 and vnet-prod-2, VLANs are configured as Port Groups within the virtual switch. Note: As VLAN 101 is set as untagged at the upstream switch port, the management network port group should be defined as untagged. This will allow the server to be deployed, without having the set a VLAN ID for the management network. Figure 39 - 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. Note: As this Scenario is based on an Active/Active configuration, and Smart Link is enabled, ensure that the vswitch Network Failover Detection is set to Link Status only. If an uplink or external switch fails, smart link will turn the server connection off, causing the vswitch to fail over to the alternate NIC. Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling VMware ESX 44

45 Figure 40 You may want to specify a specific NIC for VMotion traffic. This will ensure that all VMotion traffic between servers within the enclosure will remain on the same VC module, reducing the likelihood of multiple hops between servers. By setting the second adapter to standby, VMotion traffic will remain on vmnic0 (VC module Bay 1) and will only use vmnic1 if a failure were to occur. Note: As this Scenario is based on an Active/Active configuration, to ensure that ALL VMotion traffic between servers within the enclosure is contained, on each server edit the VMotion vswitch properties and move one of the Adapters to Standby. This will ensure that ALL VMotion traffic will occur on the same Virtual Connect module. Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling VMware ESX 45

46 When configuring the virtual guest, edit the Network Adapter configuration and select which VLAN this guest will connect to. Figure 41 Set the Guest VM to the appropriate VLAN. Figure 42 - Windows VM Guest configured in VLAN 102. Scenario 3 Multiple Simple Networks Providing Redundancy and Link Aggregation 802.3ad (LACP) with VLAN Tunneling VMware ESX 46

47 Scenario 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. The single SUS is a popular configuration when supporting primarily East/West traffic patterns. No matter which NIC a server is active on, if talking to another server within the enclosure on the same vnet, the traffic will remain within VC/the enclosure. Requirements In order to implement this scenario, an HP BladeSystem c7000 enclosure with one of more server blades and TWO Virtual Connect 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. Configuring Uplinks to a SUS (LACP) When all uplinks configured within a SUS connect a VC module to an upstream switch, ALL links could 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). Two identical SUS would be utilized to create and Active/Active design. When some of the uplinks configured within a SUS connect a VC module to different upstream switches, some links will be active and the remaining will be Standby, providing additional bandwidth and/or availability, using Link Aggregation Protocol (LACP ad). A single SUS would be used to create an Active/Standby design. Scenario 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 47

48 Figure 43 - Shows two Ethernet uplinks from Port 1 and 2 on Module 1 to Portt 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. Figure 44 - 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- by the server will be untagged, as only a single network is mapped to each NIC. Trunk. Both NICs for blade App-1 are connected VLAN-101, all frames are received Scenario 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 48

49 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: The upstream switch ports are configured as TRUNK ports, presenting VLANs 1, and Note: VLAN 101 is set to default (untagged). The upstream switch ports are configured within the same Link Aggregation Group. When adding the additional uplinks to the vnet, the switch ports connected to Virtual Connect will need to be configured for LACP and configured for the same Link Aggregation Group. Configuring the VC module Physically connect Ports 1 and 2 of the first network switch to Ports 1 and 2 on the VC module in Bay 1. Physically connect Ports 1 and 2 of the second network switch to Ports 1 and 2 of the VC module in Bay 2, if you have only one network switch, connect the second VC module cables to alternates port on the same switch. This will NOT create a network loop and does not require Spanning Tree to be configured. VC CLI commands Many of the configuration settings within VC can also be accomplished via a CLI command set. In order to connect to VC via a CLI, open an SSH connection to the IP address of the active VCM. Once logged in, VC provides a CLI with help menus. Through this scenario the CLI commands to configure VC for each setting will also be provided. 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. 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. Configuring Fast MAC Cache Failover via CLI (Ethernet settings) The following command can be copied and pasted into an SSH based CLI session with Virtual Connect # Set Advanced Ethernet Settings to Enable Fast MAC cache fail-over set mac-cache Enabled=True Refresh=5 Scenario 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 49

50 Figure 45 - Ethernet Settings - Ensure Fast MAC Cache is enabled. Defining a new Shared Uplink Set via GUI Create a SUS and name it VLAN-Trunk, assign 4 uplinks from two modules and add VLANs 1, , On the Virtual Connect Manager screen, click Define, Shared Uplink Set to create a SUS Ether the Network Name of VLAN-Trunk 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 Enclosure 1, Bay 2, Port 2 Add Networks as follows; VLAN-101, as native VLAN VLAN-1, and VLAN Leave Connection Mode as Auto Note: By creating a SUS we have provided the ability to present one or many VLANs to a server NIC. As two uplinks are configured from each VC module within the SAME SUS we have provided an active/standby configuration with Link Aggregation (802.3ad, LACP). This configuration provides additional bandwidth and the ability to lose an uplink cable, network switch or depending on how the NICs are configured at the server (teamed or un-teamed), even a VC module. However, only one uplink pair will be active at a time. Note: Smart Link In this configuration Smartlink should NOT be enabled. Smartlink is used to turn off downlink ports within Virtual Connect network, if ALL available uplinks to that network are down. Scenario 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 50

51 Defining a new Shared Uplink Set via CLI #Create Shared Uplink Set "VLAN-Trunk" and configure uplinks 1 and 2 from each VC-F module add uplinkset VLAN-Trunk add uplinkport enc0:1:1 Uplinkset=VLAN-Trunk speed=auto add uplinkport enc0:1:2 Uplinkset=VLAN-Trunk speed=auto add uplinkport enc0:2:1 Uplinkset=VLAN-Trunk speed=auto add uplinkport enc0:2:2 Uplinkset=VLAN-Trunk speed=auto # Create Networks VLAN-1, and for Shared Uplink Set "VLAN-TRUNK" add network VLAN-101 uplinkset=vlan-trunk VLanID=101 NativeVLAN=Enabled Set Network VLAN-101 SmartLink=disabled add network-range -quiet UplinkSet=VLAN-Trunk NamePrefix=VLAN- NameSuffix= VLANIds=1, , State=enabled PrefSpeedType=auto SmartLink=disabled Figure 46 - Define Shared Uplink Set VLAN-Trunk and VLANs. Scenario 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 51

52 Figure 47 - VLAN-Trunk Link aggregation confirmed Bay 1. Note: All connections within an 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 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 52

53 Figure 48 - VLAN-Trunk Link aggregation confirmed Bay 2. Note: All connections within an 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. 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 Create a server profile called App-1 In the Network Port 1 drop down box, select VLAN-101 In the Network Port 2 drop down box, select VLAN-101 In the Assign the Profile to a Server Bays, select Bay 2 and apply Defining a Server Profile with NICs Connections to a single VLAN, 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 App-1 -nodefaultenetconn add enet-connection App-1 pxe=enabled add enet-connection App-1 pxe=disabled set enet-connection App-1 1 Network=VLAN-102 set enet-connection App-1 2 Network=VLAN-102 assign profile App-1 enc0:2 Note: The following graphics provide examples of a how a Windows or Linux server might be configured for a specific VLAN. In this case both NICs are configured for network VLAN-101. Any frames received by Virtual Connect for this server will have their VLAN tags intact, Virtual Connect will remove the tags and present the frames to the server NICs, and therefore, the VC port is acting as an ACCESS port. Scenario 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 53

54 Figure 49 - Define a Server Profile App-1, connected to VLAN-102. Figure 50 - View Bay - Note VLAN-102. Scenario 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 54

55 Summary Results We created a Virtual Connect Shared Uplink Set (SUS), to supportt several VLANs (1, , ). The SUS was created with both Active and standbyy uplinks, to provide both additional bandwidth and availability, LACP was used to provide additional bandwidth. When VC profile App-1 is applied to the server in bay2 and is powered up, it has two NICs connected to VLAN-102, which connects to the network infrastructure through two (active) 1Gb uplinks. These NICs are configured in VLAN 102, however, Virtual Connect is removing the VLAN tags and presenting the frames as untagged, so the operating system does not need to understand which VLAN it is on. These NICs could now be configured as individual NICs with theirr own IP address or as a pair of TEAMED NICs. Either NIC could be active. As a result, this serverr could access the network through either NIC or either uplink cable, depending on which NICC and Uplink iss active at the time. As additional servers are added to the enclosure, simply create additional profiles or copy the APP-1 profile, configure it for the appropriate network and applyy them to the appropriate server bays. The following graphic provides an example of a Windows 2008 R2 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 51 - Both NICs for Profile App-1are connected to the network through VLAN-102. Scenario 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 55

56 The following graphics provide an example of a Windows 2008R2 Server with TWO NICs teamed and connected to the network. One NIC will be active, the other in standby, in the event of an Uplink or switch failure, VC would fail-over the uplinks and the server would not be affected by the failure, however, if the VC module with the active uplinks were to fail, the teaming software will fail the NIC over to the alternate path, as required. Figure 52 - Team both NICs, using the HP Network Configurationn Utility. Figure 53 - Both NICs for Profile App-1are teamed and connected to the network through VLAN Scenario 4 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) Windows 56

57 Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX Overview This configuration uses single 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. The single SUS is a popular configuration when supporting primarily East/West traffic patterns. No matter which NIC a server is active on, if talking to another server within the enclosure on the same VLAN, the traffic will remain within the VC/enclosure. Requirements In order to implement this scenario, an HP BladeSystem c7000 enclosure with one of more server blades and TWO Virtual Connect 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. Configuring Uplinks to a vnet (LACP) When all uplinks configured within a SUS connect a VC module to an upstream switch, ALL links could 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). When some of the uplinks configured within a SUS connect a VC module to different upstream switches, some links will be active and the remaining will be Standby, providing additional bandwidth and/or availability, using Link Aggregation Protocol (LACP ad). This scenario will have both Active and Standby links. Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 57

58 Figure 54 - Shows two Ethernet uplinks from Port 1 and 2 on Module 1 to Portt 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. Figure 55 - 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 VLANare received by the Trunk. Both NICs for blade ESX-1 are connected to Several VLANs, all frames server will be tagged, except VLAN-101. Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 58

59 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: The upstream switch ports are configured as TRUNK ports, presenting VLANs 1, and Note: VLAN 101 is set to default (untagged). The upstream switch ports are configured within the same Link Aggregation Group. When adding the additional uplinks to the vnet, the switch ports connected to Virtual Connect will need to be configured for LACP and configured for the same Link Aggregation Group. Configuring the VC module Physically connect Ports 1 and 2 of the first network switch to Ports 1 and 2 on the VC module in Bay 1. Physically connect Ports 1 and 2 of the second network switch to Ports 1 and 2 of the VC module in Bay 2, if you have only one network switch, connect the second VC module cables to alternates port on the same switch. This will NOT create a network loop and does not require Spanning Tree to be configured. VC CLI commands Many of the configuration settings within VC can also be accomplished via a CLI command set. In order to connect to VC via a CLI, open an SSH connection to the IP address of the active VCM. Once logged in, VC provides a CLI with help menus. Through this scenario the CLI commands to configure VC for each setting will also be provided. 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. 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. Configuring Fast MAC Cache Failover via CLI (Ethernet settings) The following command can be copied and pasted into an SSH based CLI session with Virtual Connect # Set Advanced Ethernet Settings to Enable Fast MAC cache fail-over set mac-cache Enabled=True Refresh=5 Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 59

60 Figure 56 - Ethernet Settings - Ensure Fast MAC Cache is enabled. Defining a new Shared Uplink Set via GUI Create a SUS and name it VLAN-Trunk, assign 4 uplinks from two modules and add VLANs 1, , On the Virtual Connect Manager screen, click Define, Shared Uplink Set to create a SUS Ether the Network Name of VLAN-Trunk 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 Enclosure 1, Bay 2, Port 2 Add Networks as follows; VLAN-101, as native VLAN VLAN-1, and VLAN Leave Connection Mode as Auto Note: By creating a SUS we have provided the ability to present one or many VLANs to a server NIC. As two uplinks are configured from each VC module within the SAME SUS we have provided an active/standby configuration with Link Aggregation (802.3ad, LACP). This configuration provides additional bandwidth and the ability to lose an uplink cable, network switch or Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 60

61 depending on how the NICs are configured at the server (teamed or unteamed), even a VC module. However, only one uplink pair will be active at a time. Note: Smart Link In this configuration Smartlink should NOT be enabled. Smartlink is used to turn off downlink ports within Virtual Connect network, if ALL available uplinks to that network are down. Defining a new Shared Uplink Set via CLI #Create Shared Uplink Set "VLAN-Trunk" and configure uplinks 1 and 2 from each VC-F module add uplinkset VLAN-Trunk add uplinkport enc0:1:1 Uplinkset=VLAN-Trunk speed=auto add uplinkport enc0:1:2 Uplinkset=VLAN-Trunk speed=auto add uplinkport enc0:2:1 Uplinkset=VLAN-Trunk speed=auto add uplinkport enc0:2:2 Uplinkset=VLAN-Trunk speed=auto # Create Networks VLAN-1, and for Shared Uplink Set "VLAN-TRUNK" add network VLAN-101 uplinkset=vlan-trunk VLanID=101 NativeVLAN=Enabled Set Network VLAN-101 SmartLink=disabled add network-range -quiet UplinkSet=VLAN-Trunk NamePrefix=VLAN- NameSuffix= VLANIds=1, , State=enabled PrefSpeedType=auto SmartLink=disabled Figure 57 - Define Shared Uplink Set VLAN-Trunk and VLANs. Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 61

62 Figure 58 - VLAN-Trunk Link aggregation confirmed Bay 1. Note: All connections within an 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 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 62

63 Figure 59 - VLAN-Trunk Link aggregation confirmed Bay 2. Note: All connections within an 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. Defining a Server Profile with NICs Connections to multiple VLANs, 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 Create a server profile called ESX-1 In the Network Port 1 drop down box, select Multiple Networks Select VLANs, 101 through 105 and 2101,2110,2120 Check Untagged for VLAN-101 In the Network Port 2 drop down box, select Multiple Networks Select VLANs, 101 through 105 and 2101,2110,2120 Check Untagged for VLAN-101 In the Assign the Profile to a Server Bays, select Bay 1 and apply Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 63

64 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 ESX-1 add profile ESX-1 -nodefaultfcconn -nodefaultfcoeconn add server-port-map-range ESX-1:1 UplinkSet=VLAN-Trunk VLanIds= ,2101,2110,2120 set server-port-map ESX-1:1 VLAN-101 UnTagged=true set enet-connection ESX-1 1 pxe=enabled add server-port-map-range ESX-1:2 UplinkSet=VLAN-Trunk VLanIds= ,2101,2110,2120 set server-port-map ESX-1:2 VLAN-101 UnTagged=true set enet-connection ESX-1 2 pxe=disabled assign profile ESX-1 enc0:1 Note: The graphic below is an example of a how an ESX server would be configured to support connections to several VLANs. In this case both NICs are configured for Multiple Networks. Any frames received by Virtual Connect for this server will have their VLAN tags intact, Virtual Connect will forward ALL frames tagged, except for VLAN 101, which we have defined as untagged. Click on the Edit link to the right of the Multiple Networks dropdown to edit or define which VLANs this NIC will connect to. Figure 60 - Define a Server Profile ESX-1, connected to Multiple VLANs. Note: That when Multiple Networks is selected, the VLAN tags are left unaffected, even if only one VLAN is subsequently selected. Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 64

65 Figure 61 - Select the VLANs to be configured for this NIC, also note only ONE VLAN can be defined as Untagged. Figure 62 - View Bay - Note Multiple VLAN Connections. Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 65

66 Summary We created a Virtual Connect Shared Uplink Set (SUS), to support several VLANs (1, , ). The SUS was created with both Active and Standby uplinks, to provide both additional bandwidth and availability. In addition, the single SUS was used to promote better East/West traffic patterns between servers within the same VLAN. When VC profile ESX-1 is applied to the server in bay1 and is powered up, it has two NICs connected to Multiple VLANs, which connects to the network infrastructure through a two (active) 1Gb uplinks. These NICs are configured for VLANs , 2101,2110,2120, all VLAN tags are passed to the server, with the exception of VLAN 101, which we configured as Untagged. Both NICs are connected to the SAME vswitch. Port Groups are defined for each VLAN. As additional servers are added to the enclosure, simply create additional profiles or copy the ESX-1 profile, configure it for the appropriate network(s) and apply them to the appropriate server bays. 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 and VLANs 2101, 2110, VLAN 101 is not tagged. Port Groups are added to support each VLAN. Figure 63 - As VLAN-101 was set as Untagged within the Server Profile, you need to ensure that the Hypervisor in NOT configured for VLAN tagging. However, if you want to put this server onto a VLAN that is tagged, this setting will need to be configured with that VLAN tag. Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 66

67 Figure 64 - Both NICs for Profile ESX-1are connected to the network through the SUS VLAN- Trunk, VLANs are configured as Port Groups within the virtual switch. Note: As VLAN 101 is set as untagged at the Server profile, the management network port group should be defined as untagged. This will allow the server to be deployed, without having to set the a VLAN ID for the management network. Figure 65 - Both NICs for Profile ESX-1 are connected to the network through Multiple Networks; VLANs are configured as Port Groups within the virtual switch. Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 67

68 Figure 66 - Configuring the ESX vswitch for Multiple Networks / VLANs. If additional VLANs need to be supported, simply configure the upstream switch ports for those VLANs, add them to the SUS and configure the vswitch as below to support those additional VLANs. Note: Ensure that the vswitch Network Failover Detection is set to Link Status only. If a VC module were to fail, this will ensure that vswitch fails over to the alternate NIC. Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 68

69 Figure 67 To speed VMotion events and to ensure that ALL VMotion traffic between servers within the enclosure is contained on the same VC module, on each server edit the VMotion vswitch properties and move one of the Adapters to Standby. Note: By ensuring that ALL servers within an enclosure use the SAME NIC, which in turn would be connected to the SAME I/O Bay, we can ensure that ALL VMotion traffic will occur on the same Virtual Connect module. Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 69

70 When configuring the virtual guest, edit the Network Adapter configuration and select which VLAN this guest will connect to. Figure 68 Set the Guest VM to the appropriate VLAN. Figure 69 - Windows VM Guest configured in VLAN 102. Scenario 5 VLAN Tagging (802.1Q) with a Shared Uplink Set (SUS) with Link Aggregation using LACP (802.3ad) VMware ESX 70

71 Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX Overview In this scenario, the upstream network switch connects multiple VLANs to two ports on each VC module. This scenario configuration uses TWO Virtual Connect Shared Uplink Sets (SUS). The SUS provides the ability to present a single or multiple VLANs to a server NIC. Utilizing TWO identical SUS provides the ability to redundantly connect all VLANs to the server NICs as required and leverage all connected uplinks. The dual SUS is a popular configuration when supporting primarily North/South traffic patterns, as this configuration maximizes the use of all external connections. Requirements In order to implement this scenario, an HP BladeSystem c7000 enclosure with one of more server blades and TWO Virtual Connect 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. Configuring Uplinks to a vnet (LACP) When all uplinks configured within a vnet connect a VC module to an upstream switch, ALL links could 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). When some of the uplinks configured within a vnet connect a VC module to different upstream switches, some links will be active and the remaining will be Standby, providing additional bandwidth and/or availability, using Link Aggregation Protocol (LACP ad). This scenario will have ALL uplinks Active. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 71

72 Figure 70 - Shows two Ethernet uplinks from Port 1 and 2 on Module 1 to Portt 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. Figure 71 - Logical View; Shows two Ethernet uplinks from each VC module to the network switches. The Uplinks from each Module are associated with thee Shared Uplink Sets VLAN- VLANs, all Trunk-1 and VLAN-Trunk-2. Both NICs for blade ESX-1 are connected to Several frames are received by the server will be tagged, except VLAN-101. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Linkk Aggregation using LACP (802.3ad) VMware ESX 72

73 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: The upstream switch ports are configured as TRUNK ports, presenting VLANs 1, and Note: VLAN 101 is set to default (untagged). The upstream switch ports are configured within the same Link Aggregation Group. When adding the additional uplinks to the vnet, the switch ports connected to Virtual Connect will need to be configured for LACP and configured for the same Link Aggregation Group. Configuring the VC module Physically connect Ports 1 and 2 of the first network switch to Ports 1 and 2 on the VC module in Bay 1. Physically connect Ports 1 and 2 of the second network switch to Ports 1 and 2 of the VC module in Bay 2, if you have only one network switch, connect the second VC module cables to alternates port on the same switch. This will NOT create a network loop and does not require Spanning Tree to be configured. VC CLI commands Many of the configuration settings within VC can also be accomplished via a CLI command set. In order to connect to VC via a CLI, open an SSH connection to the IP address of the active VCM. Once logged in, VC provides a CLI with help menus. Through this scenario the CLI commands to configure VC for each setting will also be provided. Defining a new Shared Uplink Sets via GUI Create a SUS and name it VLAN-Trunk-1, assign 2 uplinks from the Bay 1 module and add VLANs 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 Add Networks as follows; VLAN-101, as native VLAN VLAN-1, and VLAN Enable Smartlink for ALL networks Leave Connection Mode as Auto Note: By creating a SUS we have provided the ability to present one or many VLANs to a server NIC. As two uplinks are configured from the module Link Aggregation (802.3ad, LACP) will be used to ensure both links are active. This configuration provides additional bandwidth and the ability to lose an uplink cable. Note: Smart Link In this configuration Smartlink should be enabled. Smartlink is used to turn off downlink ports within Virtual Connect network, if ALL available uplinks to that network are down. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 73

74 Defining a new Shared Uplink Set via CLI #Create Shared Uplink Set "VLAN-Trunk-1" and configure uplinks 1 and 2 from the VC-F module in Bay 1 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-1-1, VLAN and for Shared Uplink Set "VLAN- TRUNK-1" add network VLAN uplinkset=vlan-trunk-1 VLanID=101 NativeVLAN=Enabled Set Network VLAN SmartLink=Enabled add network-range -quiet UplinkSet=VLAN-Trunk-1 NamePrefix=VLAN- NameSuffix=-1 VLANIds=1, , State=enabled PrefSpeedType=auto SmartLink=Enabled Copy a new Shared Uplink Set via CLI copy uplinkset VLAN-Trunk-1 VLAN-Trunk-2 fromvlanstr=1 tovlanstr=2 replace=last add uplinkport enc0:2:1 Uplinkset=VLAN-Trunk-2 speed=auto add uplinkport enc0:2:2 Uplinkset=VLAN-Trunk-2 speed=auto set network-range -quiet UplinkSet=VLAN-Trunk-2 VLANIds=1, , SmartLink=enabled Set Network VLAN SmartLink=Enabled Figure 72 - Define Shared Uplink Set VLAN-Trunk and VLANs. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 74

75 Figure 73 - VLAN-Trunk Link aggregation confirmed Bay 1. Note: All connections within an 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. If the LAG ID is not the same, you likely have a LACP configuration issue with the upstream switch. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 75

76 Figure 74 - VLAN-Trunk-2 Link aggregation confirmed Bay 2. Note: All connections within an 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. If the LAG ID is not the same, you likely have a LACP configuration issue with the upstream switch. Defining a Server Profile with NICs Connections to multiple VLANs, 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 Create a server profile called ESX-1 In the Network Port 1 drop down box, select Multiple Networks Select VLANs from VLAN-Trunk-1, 101 through 105 and 2101,2110,2120 Check Untagged for VLAN-101 In the Network Port 2 drop down box, select Multiple Networks Select VLANs from VLAN-Trunk-2, 101 through 105 and 2101,2110,2120 Check Untagged for VLAN-101 In the Assign the Profile to a Server Bays, select Bay 1 and apply Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 76

77 Defining a Server Profile with NICs Connections to a 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 ESX-1 add profile ESX-1 -nodefaultfcconn -nodefaultfcoeconn add server-port-map-range ESX-1:1 UplinkSet=VLAN-Trunk-1 VLanIds= ,2101,2110,2120 set server-port-map ESX-1:1 VLAN UnTagged=true set enet-connection ESX-1 1 pxe=enabled add server-port-map-range ESX-1:2 UplinkSet=VLAN-Trunk-2 VLanIds= ,2101,2110,2120 set server-port-map ESX-1:2 VLAN UnTagged=true set enet-connection ESX-1 2 pxe=disabled assign profile ESX-1 enc0:1 Note: The graphic below is an example of a how an ESX server might be configured to support connection to several VLANs. In this case both NICs are configured for network Multiple Networks. Any frames received by Virtual Connect for this server will have their VLAN tags intact, Virtual Connect will forward ALL frames tagged, except for VLAN 101, which we have defined as untagged. Click on the Edit link to the right of the Multiple Networks dropdown to edit or define which VLANs this NIC will connect to. Figure 75 - Define a Server Profile ESX-1, connected to Multiple VLANs. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 77

78 Figure 76 - Select the VLANs to be configured for this NIC, also note only ONE VLAN can be defined as Untagged. Figure 77 - View Bay - Note Multiple VLAN Connections. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 78

79 Summary We created two independent but identical Shared Uplink Sets (SUS), to support several VLANs (1, , ). Each SUS was created with Active uplinks, to provide both additional bandwidth and availability. When VC profile ESX-1 is applied to the server in bay1 and is powered up, it has two NICs each connected to Multiple VLANs, which connects to the network infrastructure through two (active) 1Gb uplinks. These NICs are configured for VLANs , 2101,2110,2120, all VLAN tagged are passed to the server, with the exception of VLAN 101, which we configured as Untagged. Both NICs are connected to the SAME vswitch. Port Groups are defined for each VLAN. As additional servers are added to the enclosure, simply create additional profiles or copy the ESX-1 profile, configure it for the appropriate network and apply them to the appropriate server bays. 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 and VLANs 2101, 2110, VLAN 101 is not tagged. Port Groups are added to support each VLAN. Figure 78 - As VLAN-101 was set as Untagged within the Server Profile, you need to ensure that the Hypervisor in NOT configured for VLAN tagging. However, if you want to put this server onto a VLAN that is tagged, this setting will need to be configured with that VLAN tag. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 79

80 Figure 79 - Both NICs for Profile ESX-1 are connected to the network through Multiple Networks; VLANs are configured as Port Groups within the virtual switch. Note: As VLAN 101 is set as untagged at the Server profile, the management network port group should be defined as untagged. This will allow the server to be deployed, without having to set a VLAN ID for the management network. Figure 80 - Configuring the ESX vswitch for Multiple Networks / VLANs. Note: As this Scenario is based on an Active/Active configuration, and Smart Link is enabled, ensure that the vswitch Network Failover Detection is set to Link Status only. If an uplink or external switch fails, smart link will turn the server connection off, causing the vswitch to fail over to the alternate NIC. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 80

81 Figure 81 - 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. Note: As this Scenario is based on an Active/Active configuration, to ensure that ALL VMotion traffic between servers within the enclosure is contained, on each server edit the VMotion vswitch properties and move one of the Adapters to Standby. This will ensure that ALL VMotion traffic will occur on the same Virtual Connect module. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 81

82 When configuring the virtual guest, edit the Network Adapter configuration and select which VLAN this guest will connect to. Figure 82 Set the Guest VM to the appropriate VLAN. Figure 83 - Windows VM Guest configured in VLAN 102. Scenario 6 VLAN Tagging (802.1Q) with Multiple Shared Uplink Sets (SUS) and Link Aggregation using LACP (802.3ad) VMware ESX 82

83 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 & 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. NOTE: If two switches are being used, issue the same commands on the second switch. Table 1a Scenario 1 and 2 (Part 1) - Cisco IOS command line configuration. Command Shortcut Description >enable >en Privilege mode #configure terminal #config t Configure via terminal #interface gigabitethernet0/1 #int gi1/0/1 Focus on Port 1 #switchport mode access #switchport access vlan 1 #spanning-tree portfast trunk #sw mo ac #sw ac vl 1 #sp portf tr Set port 1 for Single VLAN mode Allow Port 1 access to VLAN 1 Enable portfast on Port 1 #exit #exit Remove focus from Port 1 #exit #exit Remove focus from Port 1 #show vlan brief #sh vl br Display all VLANs #show interface gigabitethernet0/1 status #copy running-config startup-config (For permanent changes only) #sh int gi0/1 status #cop ru st Display the status of Port 1 Save the running configuration to NVRAM. Otherwise, the changes will be lost on the next reboot. Appendix A: Scenario-based Cisco command line reference 83

84 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 two switches are being used, issue the same commands on the second switch. Table 1b Scenario 1 and 2 (Part 2) - Cisco IOS command line configuration. Command Shortcut Description >enable >en Privilege mode #configure terminal #config t Configure via terminal #interface gigabitethernet0/1 #int gi1/0/1 Focus on Port 1 #switchport mode access #switchport access vlan 1 #sw mo ac #sw ac vl 1 Set Port 1 for Single VLAN mode Allow Port 1 access to VLAN 1 #channel-protocol lacp #channel-p l Configure Port 1 for 802.3ad LACP #channel-group 10 mode active #spanning-tree portfast trunk #channel-g 10 mo ac #sp portf tr Enable channel group 10 Enable portfast on Port 1 #exit #ex Remove focus from Port 1 #interface gigabitethernet0/2 #switchport mode access #int gi0/2 Focus on Port 2 #sw mo ac Set port 2 for Single VLAN mode #channel-protocol lacp #channel-p l Configure Port 2 for 802.3ad LACP #channel-group 10 mode active #switchport access vlan 1 #spanning-tree portfast trunk #channel-g 10 mo ac #sw ac vl 1 #sp portf tr Enable channel group 10 Allow Port 2 access to VLAN 1 Enable portfast on Port 2 #exit #exit Remove focus from Port 2 #exit #exit Exit config mode #show lacp 10 internal #sh la 10 i Show the LACP group 10 configuration Appendix A: Scenario-based Cisco command line reference 84

85 Table 1b Scenario 1 and 2 (Part 2) - Cisco IOS command line configuration. Command Shortcut Description #show etherchannel summary #show interface portchannel10 trunk #sh eth sum #sh int port-channel 10 tr Show the etherchannel configuration Show the Port channel 10 trunk configuration #show vlan brief #sh vl br Display all VLANs #show interface gigabitethernet0/2 status #copy running-config startup-config (For permanent changes only) #sh int gi1/0/2 status #cop ru st Display the status of Port 2 Save the running configuration to NVRAM. Otherwise, the changes will be lost on the next reboot. Appendix A: Scenario-based Cisco command line reference 85

86 Scenario 3-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 two switches are being used, issue the same commands on the second switch. Table 2 Scenario 3 6 Cisco IOS command line configuration (802.1Q, 802.3ad). Command Shortcut Description >enable >en Privilege mode #configure terminal #config t Configure via terminal #interface gigabitethernet0/1 #int gi0/1 Focus on Port 1 #switchport trunk allowed vlan , #switchport mode trunk #switchport trunk native vlan 101 #sw tr ac vl , #sw mo tr #sw tr na vlan 101 Configure port 1 for VLANs 101 through 105, Enable trunking on Port 1 Set VLAN 101 as native #channel-protocol lacp #channel-p l Configure port 20 for 802.3ad LACP #channel-group 10 mode active #spanning-tree portfast trunk #channel-g 10 mo ac #sp portf tr Enable channel group 10 Enable portfast on Port 1 #exit #ex Remove focus from Port 1 #interface gigabitethernet0/2 #int gi0/2 Focus on Port 2 #switchport trunk allowed vlan , #switchport mode trunk #switchport trunk native vlan 101 #sw tr ac vl , #sw mo tr #sw tr na vlan 101 Configure port 2 for VLANs 101 through 105, Enable trunking on Port 2 Set VLAN 101 as native #channel-protocol lacp #channel-p l Configure Port 21 for 802.3ad LACP #channel-group 10 mode active #spanning-tree portfast trunk #channel-g 10 mo ac #sp portf tr Enable channel group 10 Enable portfast on Port 2 Appendix A: Scenario-based Cisco command line reference 86

87 Table 2 Scenario 3 6 Cisco IOS command line configuration (802.1Q, 802.3ad). Command Shortcut Description #exit #ex Remove focus from Port 2 #show lacp 10 internal #sh la 10 i Show the LACP group 10 configuration #show etherchannel summary #show interface portchannel10 trunk #copy running-config startup-config (For permanent changes only) #sh eth sum #sh int port-channel 10 tr #cop ru st Show the etherchannel configuration Show the port channel 10 trunk configuration Save the running configuration to NVRAM. Otherwise, the changes will be lost on the next reboot. Appendix A: Scenario-based Cisco command line reference 87

88 Appendix B: Scenario-based ProCurve command line reference Scenario 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 two switches are being used, issue the same commands on the second switch. Table 3a Scenario 1 & 2 (Part 1) - ProCurve command line configuration (simple network). Command Shortcut Description >enable >en Privilege mode #configure terminal #conf Configure in global mode #span #span Enables spanning-tree (MSTP mode by default) #vlan 1 untagged [Ethernet] 1 #spanning-tree 1 admin-edge-port #vlan 1 untag 1 Allow VLAN 1 on Port 1, and set Port 1 to untagged mode #span 1 admin-edge Set Port 1 to be an edge port (non bridging port). Note: port is set by default in autoedge mode which automatically sets port to Edge if no BPDU are received after 3 sec. #show interface brief 1 #sh int br 1 Display the status of Port 1 #show vlan ports 1 detail # show vlan ports 1 detail Displays the VLAN detail for Port 1 #show vlan 1 #sh vlan 1 Display VLAN 1 port information #write memory (For permanent changes only) #write mem Save the running configuration to NVRAM. Otherwise, the changes will be lost on the next reboot. Appendix B: Scenario-based ProCurve command line reference 88

89 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 two switches are being used, issue the same commands on the second switch. Table 3b Scenario 1 &2 2 (Part 2) - ProCurve command line configuration (simple network, 1 untagged VLAN ). Command Shortcut Description >enable >en Privilege mode #configure terminal #conf Configure in global mode #span #span Enables spanning-tree (MSTP mode by default) #trunk 1-2 trk1 lacp #trunk 1-2 trk1 lacp Configure LACP porttrunk 1 to include Ports 1 & 2 #vlan 1 untagged [Ethernet] trk1 #spanning-tree ethernet trk1 adminedge-port #show vlan ports trk1 detail #vlan 1 untag trk1 Allow VLAN 1 on Port 1 & 2, and set to untagged mode #span e trk1 adminedge # show vlan ports trk1 detail Set Port 1 to be an edge port (non bridging port). Note: port is set by default in autoedge mode which automatically sets port to Edge if no BPDU are received after 3 sec. Displays the VLAN detail for Trunk1 #show vlan 1 #sh vlan 1 Display VLAN 1 port information #write memory (For permanent changes only) #write mem Save the running configuration to NVRAM. Otherwise, the changes will be lost on the next reboot. Appendix B: Scenario-based ProCurve command line reference 89

90 Scenario 3-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 two switches are being used, issue the same commands on the second switch. Table 4 Scenario ProCurve command line configuration (Tagged VLANs). Command Shortcut Description >enable >en Privilege mode #configure terminal #conf Configure in global mode #span #span Enables spanning-tree (MSTP mode by default) #trunk 1-2 trk1 lacp #trunk 1-2 trk1 lacp Configure LACP porttrunk 1 to include Ports 1 & 2 #vlan 101 untagged trk1 #vlan 101 untag trk1 Allow VLAN 101 on Ports 1 and 2 and configure Ports 1 and 2 for untagged VLAN mode #vlan 102 tagged trk1 #vlan 102 tag trk1 Allow VLAN 1021 on Ports 1 and 2 and configure Ports 1 and 2 for untagged VLAN mode #vlan 103 tagged trk1 #vlan 103 tag trk1 Allow VLAN 103 on Ports 1 and 2 and configure Ports 1 and 2 for untagged VLAN mode #vlan 104 tagged trk1 #vlan 104 tag trk1 Allow VLAN 104 on Ports 1 and 2 and configure Ports 1 and 2 for untagged VLAN mode #vlan 105 tagged trk1 #vlan 105 tag trk1 Allow VLAN 104 on Ports 1 and 2 and configure Ports 1 and 2 for untagged VLAN mode Appendix B: Scenario-based ProCurve command line reference 90

91 Table 4 Scenario ProCurve command line configuration (Tagged VLANs). Command Shortcut Description #spanning-tree ethernet trk1 adminedge-port #span e trk1 adminedge Set Port 1 to be an edge port (non bridging port). Note: port is set by default in autoedge mode which automatically sets port to Edge if no BPDU are received after 3 sec. #show vlan 101 #sh vlan 101 Display VLAN 101 #show vlan 102 #sh vlan 102 Display VLAN 102 #show vlan 103 #sh vlan 103 Display VLAN 103 #show vlan 104 #sh vlan 104 Display VLAN 104 #show vlan 105 #sh vlan 105 Display VLAN 105 #show vlan ports trk1 detail #show interface brief1-2 # show vlan ports trk1 detail #sh int br1-2 Displays the VLAN detail for Trunk 1 Show Port 1-2 status #write memory (For permanent changes only) #write mem Save the running configuration to NVRAM. Otherwise, the changes will be lost on the next reboot. Note: as ProCurve does not provide the ability to create a bulk set of VLANs, each VLAN must be created individually. Therefore; create and configure the addition VLANs as required. Appendix B: Scenario-based ProCurve command line reference 91

92 Appendix C: Acronyms and abbreviations Term Auto Port Speed** CLP String Definition 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 off. Read by the server hardware upon power in. Custom Port Speed** DCC** EtherChannel* Flex NIC** Flex-10 Nic Port** IEEE802.1Q IEEE802.3ad LACP LOM Maximum Link Connection Speed** Multiple Networks Link Speed Settings** MZ1 or MEZZ1; LOM Network Teaming Software pnic** Port Aggregation Port Aggregation Protocol (PAgP)* Port Bonding Preferred Link Connection Speed** Share Uplink Set (SUS) Smart Link Trunking (Cisco) Trunking (Industry) Trunking (Industry) VLAN VLAN Tagging vnic Manually set Flex NIC speed (up to Maximum value defined) Dynamic Control Channel. Future method for VC to change Flex-10 NIC port settings on the fly (without powering off) A Cisco proprietary technology that combines multiple NIC or switch ports for greater bandwidth, load balancing, and redundancy. The technology allows for bi-directional aggregated network traffic flow. One of four virtual NIC partitions available per Flex-10 Nic port. Each capable of being tuned from 100Mb to 10Gb A physical 10Gb port that is capable of being partitioned into 4 Flex NICs An industry standard protocol that enables multiple virtual networks to run on a single link/port in a secure fashion through the use of VLAN tagging. An industry standard protocol that allows multiple links/ports to run in parallel, providing a virtual single link/port. The protocol provides greater bandwidth, load balancing, and redundancy. Link Aggregation Control Protocol (see IEEE802.3ad) LAN-on-Motherboard. Embedded network adapter on the system board Maximum Flex NIC speed value assigned to vnet by the network administrator. Can NOT be manually overridden on the server profile. Global Preferred and Maximum Flex NIC speed values that override defined vnet values when multiple vnets are assigned to the same Flex NIC Mezzanine Slot 1; LAN on Motherbard/systemboard NIC A software that runs on a host, allowing multiple network interface ports to be combined to act as a single virtual port. The software provides greater bandwidth, load balancing, and redundancy. Physical NIC port. A Flex NIC is seen by VMware as a pnic Combining ports to provide one or more of the following benefits: greater bandwidth, load balancing, and redundancy. A Cisco proprietary protocol aids in the automatic creation of Fast EtherChannel links. PAgP packets are sent between Fast EtherChannel-capable ports to negotiate the forming of a channel. A term typically used in the Unix/Linux world that is synonymous to NIC teaming in the Windows world. Preferred Flex NIC speed value assigned to a vnet by the network administrator. A set of Ethernet uplinks that are used together to provide improved throughput and availability to a group of associated Virtual Connect networks. Each associated Virtual Connect network is mapped to a specific VLAN on the external connection and appropriate VLAN tags are removed or added as Ethernet packets enter or leave the Virtual Connect domain. 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 Q VLAN tagging Combining ports to provide one or more of the following benefits: greater bandwidth, load balancing, and redundancy. Combining ports to provide one or more of the following benefits: greater bandwidth, load balancing, and redundancy. A virtual network within a physical network. Tagging/marking an Ethernet frame with an identity number representing a virtual network. Virtual NIC port. A software-based NIC used by Virtualization Managers vnet Virtual Connect Network used to connect server NICs to the external Network *The feature is not supported by Virtual Connect. **This feature was added for Virtual Connect Flex-10. Appendix C: Acronyms and abbreviations 92

93 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. VC Domain Configuration #Enclosure Setup #Import Enclosure and Set Domain Name #Ensure password matches the OA password import enclosure username=administrator password=administrator set domain name=vc_domain_1 #Importing additional or multiple Enclosures to an existing VC Domain # Importing an Enclosure into an existing VC Domain (Note: As of this writing (VC firmware 2.30) the following commands must be executed individually and cannot be part of a larger script). #The IP address, login and password information used in this command are from the OA of the enclosure being imported. Import enclosure UserName=Administrator Password=password Import enclosure UserName=Administrator Password=password Import enclosure UserName=Administrator Password=password #Configure MAC and WWN to VC Defined and select pool #1 set domain mactype=vc-defined macpool=1 set domain wwntype=vc-defined wwnpool=1 set serverid type=vc-defined poolid=1 #Change Administrator set user Administrator password=administrator # Set Advanced Ethernet Settings to "Map VLAN Tags" and set "Force server connections" to disabled set enet-vlan vlantagcontrol=map sharedservervlanid=false # Set Advanced Ethernet Settings to "Tunnel VLAN Tags" set enet-vlan vlantagcontrol=tunnel # Set Advanced Ethernet Settings to a Preferred speed of 500Mb and a Max Speed of 2500Mb 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 #Create Shared Uplink Set "Prod-Net" and configure multiple uplinks on VC Module 1, Ports 1, 2 and 3 add uplinkset Prod-Net add uplinkport enc0:1:1 Uplinkset=Prod-Net speed=auto add uplinkport enc0:1:2 Uplinkset=Prod-Net speed=auto add uplinkport enc0:1:3 Uplinkset=Prod-Net speed=auto Appendix D: Useful VC CLI Command sets 93

94 # Create Networks PROD-A through PROD-D, supporting VLANs 101 through 104 on Shared Uplink Set "Prod- Net" add network VLAN_10 uplinkset=prod-net VLanID=10 add network VLAN_20 uplinkset=prod-net VLanID=20 # (optionally) Set network VLAN_20 as a Private Network set network VLAN20 Private=Enabled Creating vnets #Create vnet "Prod-Net" and configure uplinks add Network Prod-Net add uplinkport enc0:1:3 Network=Prod-Net speed=auto #Optionally enable the vnet as a Private Network set network Prod-Net Private=Enabled 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 # configured on a specific Shared Uplink Set to be presented to a server NIC, ensure that # the Force VLAN mappings as Shared Uplink Set check box is enabled. # Shared Uplink Set, use the following commands to do so # This will set the Force same VLAN mappings as Shared Uplink Sets check box to enabled # Result is that only VLANs from this shared uplink will be available to this NIC add server-port-map App-1:1 VLAN_10 Uplinkset=Prod-Net add server-port-map App-1:1 VLAN_20 Uplinkset=Prod-Net # Create Server Profile App-1 Both NICs are configured on network VLAN_20 add profile App-1 -nodefaultenetconn add enet-connection App-1 pxe=enabled add enet-connection App-1 pxe=disabled set enet-connection App-1 1 Network=VLAN_20 set enet-connection App-1 2 Network=VLAN_20 assign profile App-1 enc0:2 # Create Server Profile ESX-1 Both NICs are configured on Both networks VLAN_10 and VLAN_20 add profile ESX-1 -nodefaultenetconn add enet-connection ESX-1 pxe=enabled add enet-connection ESX-1 pxe=disabled add server-port-map ESX-1:1 VLAN_10 VLanId=10 add server-port-map ESX-1:1 VLAN_20 VLanId=20 add server-port-map ESX-1:2 VLAN_10 VLanId=10 add server-port-map ESX-1:2 VLAN_20 VLanId=20 assign profile ESX-1 enc0:1 Appendix D: Useful VC CLI Command sets 94

95 # 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 SpeedType=Custom Speed=500 add enet-connection Server-1 pxe=disabled Network=Console SpeedType=Custom Speed=500 add enet-connection Server-1 pxe=disabled Network=VMotion SpeedType=Custom Speed=2500 add enet-connection Server-1 pxe=disabled Network=VMotion SpeedType=Custom Speed=2500 add enet-connection Server-1 pxe=disabled Network=Prod SpeedType=Custom Speed=2000 add enet-connection Server-1 pxe=disabled Network=Prod SpeedType=Custom Speed=2000 add enet-connection Server-1 pxe=disabled add server-port-map Server-1:7 Prod VLanId=104 add server-port-map Server-1:7 Prod VLanId=105 add enet-connection Server-1 pxe=disabled add server-port-map Server-1:8 Prod VLanId=104 add server-port-map Server-1:8 Prod VLanId=105 Assign profile Server-1 enc0:1 # Add TWO fc connections to Profile ESX-1 with a specific WWN add fc-connection ESX-1 Fabric=SAN_3 AddressType=User-Defined PortWWN=50:06:0B:00:00:C2:ff:00 NodeWWN=50:06:0B:00:00:c2:ff:01 add fc-connection ESX-1 Fabric=SAN_4 AddressType=User-Defined PortWWN=50:06:0B:00:00:C2:ff:02 NodeWWN=50:06:0B:00:00:C2:ff:03 # Add TWO NIC connections to Profile ESX-1 with a specific MAC and iscsi MAC address add enet-connection ESX-1 AddressType=User-Defined EthernetMac= AA-AA IScsiMac= BB-BB pxe=enabled add enet-connection ESX-1 AddressType=User-Defined EthernetMac= AA-CC IScsiMac= BB-CC pxe=disabled Appendix D: Useful VC CLI Command sets 95

96 For more information To read more about Virtual Connect, go to: hp.com/go/virtualconnect Get connected hp.com/go/getconnected Copyright 2012 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. Part number , Fourth edition December2012 Appendix D: Useful VC CLI Command sets 96