Implementing Multi-Chassis Link Aggregation Groups (MC-LAG)

Transcription

1 Implementing Multi-Chassis Link Aggregation Groups (MC-LAG) HPE Synergy Virtual Connect SE 40Gb F8 Module and Arista 7050 Series Switches Technical white paper

2 Technical white paper Contents Introduction... 3 Design Scenario... 3 Arista MLAG Overview... 4 Solution Components... 4 Hardware and Software... 4 Configuration and Verification... 6 Arista DCS-7050SX Switch Configuration... 6 MLAG Data Plane and VARP Configuration... 9 HPE OneView Configuration ESXi/VM Network Configuration Simple Network Connectivity Test Conclusion Appendix A - Bill of Materials Appendix B - Switch Configuration Appendix C: Configure resources in HPE OneView Appendix D: HPE OneView Basic Concepts Resources and additional links... 34

3 Technical white paper Page 3 Introduction Multi-Chassis Link Aggregation (MC-LAG) technologies are commonly used in the IT industry in order to implement highly resilient and highbandwidth networks. This document provides technical details for IT administrators implementing MC-LAG designs when using HPE Synergy Virtual Connect (VC) modules in conjunction with Arista switches. It is assumed that the reader has familiarity with basic networking configurations as well as an understanding of HPE OneView. If more details on either topic are needed, the reader should refer to resources listed at the end of this document. Design Scenario MC-LAG is a type of link aggregation group (LAG) with constituent ports that terminate on separate chassis (chassis in this context refers to a physical switch) peers. The primary purpose of MC-LAG is to provide redundancy in the event one of the peers fail, but MC-LAG also offers better bandwidth utilization and support for active/active topologies. Its implementation varies by vendor which means that the protocol existing between the peers is often proprietary. The MC-LAG peers use an interchassis control protocol to communicate control information and coordinate with each other to ensure that data traffic is forwarded. Note Networking vendors frequently use different nomenclature when referring to MC-LAG. For example, Arista switches use the term MLAG, while HPE FlexFabric switches use the term Intelligent Resilient Framework or IRF, and Cisco switches often use virtual port channels or vpc. In this paper, MC-LAG is used generically to refer to the concept of aggregating ports across physically separate switches. Like Arista switches, the HPE Synergy Virtual Connect Interconnect Modules use the term MLAG in this paper. Figure 1 Figure 1 provides a high-level, logical depiction of the network design used in this document. In Figure 1 above, the switch peers (labeled as Device 1 and Device 2) participate in their own MC-LAG. The MC-LAG supported on these top-of-rack (ToR) switches allows for downstream connections to terminate on separate VC modules. This provides redundancy in the unlikely event that any of the solution components fail. Since one MC-LAG is configured to include all the links shown on the ToR side of Figure 1, this essentially creates a single logical ToR switch.

4 Technical white paper Page 4 Figure 1 shows two ports from each of the VC modules (labeled as VC1 and VC2) have been designated for use in their own MLAG (note that HPE typically uses the term MLAG for Synergy VC modules). All four of these VC uplink ports are aggregated Ethernet connections and participate in an MLAG;. The Synergy VC s implementation of MLAG allows the modules to easily interoperate with any third-party ToR or End of Row (EoR) switch. In this design all four uplinks are active and are able to forward traffic. Figure 2 Figure 2 depicts an alternate topology that includes only one ToR switch. HPE Synergy VC modules will also support this topology and successfully create an MLAG connection to the single ToR switch, but it is not recommended for production environments as Device 1 represents a single point of failure. Arista MLAG Overview In order to implement MLAG on Arista switches, users must configure the MLAG control plane and the MLAG data plane. The control plane configuration involves creating an MLAG domain and establishing a switch peer link. Data plane configuration requires adding data ports to a port channel, and adding VLANs to that port channel. When implementing MLAG, it may be desirable to configure the ToR switches as the default gateway for certain VLANs (as opposed to placing the default gateway on the core switches). When placing gateways on ToR switches using MLAG, it is recommended that users implement some form of first-hop routing redundancy. For most cases when using MLAG, Arista recommends using virtual IP (VIP) and virtual ARP (VARP) as opposed to virtual routing redundancy protocol (VRRP). VIP/VARP allows Arista switches to provide full active/active paths for the data traffic. In this paper, each VLAN s default gateway is configured on the Arista 7050 s and VIP/VARP is used for routing redundancy. For more detailed information on VARP with Arista, please refer to Active-active router redundancy using VARP Guide. Solution Components Hardware and Software Two Arista 7050 series switches are used as the ToR devices. A three frame HPE Synergy solution is used to house the two master VC modules. The following table provides details of the key network hardware components and O/S s used in this paper:

5 Technical white paper Page 5 COMPONENT QUANTITY FIRMWARE AND SOFTWARE VERSION Synergy Composer (Management Appliance) HPE OneView ToR Switch Arista - DCS-7050SX-64 2 EOS Synergy Fabric Modules Master - HPE Synergy Virtual Connect SE 40Gb F Satellite - HPE Synergy 20Gb Interconnect Link Module Compute Node Network Adapter HPE Synergy 3820C 10/20Gb Converged Network Adapter Operating Systems VM Host 1 vsphere 6.0U2 VM 1 Windows 2012R2 Cables 10 Gb 8 Note: 4 x cables for ToR Switches & VCs, 2 x cables MLAG peer link between Arista Switches, and 2 x cables are used between VCs stacking links. Table 1

6 Technical white paper Page 6 Configuration and Verification This section details the steps necessary to configure MLAG on two Arista 7050 switches and Synergy VC modules. An overview of vsphere host networking is also covered, along with a verification test of connectivity between a VM and external networks. Arista DCS-7050SX Switch Configuration 1. Connect two Arista switches together using port 17 and 18 (these are not special ports) on each switch as peer-links to form a MLAG control plane. These ports will be configured as the MLAG control-plane and as MLAG peer inks in a following section of this paper. 2. Connect two switches ports 23 and port 24 (again, not special ports) to two different VC modules. These ports will be configured as data paths also in a following section of this paper. Physical Connections - Arista Switches MLAG Control Plane Configuration The control plane configuration involves creating a MLAG domain and establishing switch peer links. Switch 1 configuration: 1. Login directly to a console session on the first Arista switch 2. Configure ports 17 & 18 to be a port channel for the peer link Switch 1 port-channel-peerlinks 3. Configure a dedicated VLAN to be used for MLAG peer communication Switch 1 - Dedicated VLAN for MLAG Peer communication 4. Configure the switch virtual interface (SVI) for peer-to-peer communication Switch 1 Configure SVI interface for MLAG communication

7 Technical white paper Page 7 5. Configure VLANs and peer IP address to be used by MLAG service and create MLAG domain ID Switch 1 Configure VLANs and peer IP Switch 2 configuration: 1. Login directly to a console session on the second Arista switch 2. Configure ports 17 & 18 to be a port channel for the peer link Switch 2 port-channel-peerlinks 3. Configure a dedicated VLAN to be used for MLAG peer communication Switch 2 - Dedicated VLAN for MLAG Peer communication 4. Configure the switch virtual interface (SVI) for peer-to-peer communication Switch 2 Configure SVI interface for MLAG communication 5. Configure VLANs and peer IP address to be used by MLAG service and create MLAG domain ID Switch 2 Configure VLANs and peer IP Arista Switch MLAG control plane verification 1. Login directly to a console session on the first Arista switch 2. Run the show mlag command

8 Technical white paper Page 8 3. Run the show mlag config-sanity command Show resulting MLAG on switch 1 Show resulting MLAG configuration consistency between switches 4. Repeat these steps on the second switch Show resulting MLAG on switch 2 Show resulting MLAG configuration consistency between switches

9 Technical white paper Page 9 For more information about Arista MLAG, please refer to the Arista MLAG Configuration Guide MLAG Data Plane and VARP Configuration Switch 1 configuration: 1. Configure ports 23 & 24 to be a port channel for the data plane (from Arista 7050s to Synergy VCs) 2. Define Data VLANs Configuring port channel for data plane Setup VLAN deffinitions Note Omit the next three steps if placing default gateways on the core switches. 3. Configure VLAN interface and Virtual-Router address. Configure VLAN interface 4. Repeat Steps 2 & 3 for the remaining data VLANs (for this paper: 151, ) 5. Configure the global common virtual MAC address. Switch 2 configuration: Configure virtual MAC address 1. Configure ports 23 & 24 to be a port channel for the data plane (from Arista 7050s to Synergy VCs) Configuring port channel for data plane

10 Technical white paper Page Define Data VLANs Setup VLAN deffinitions Note Omit the next three steps if placing default gateways on the core switches. 3. Configure VLAN interface and Virtual-Router address Configure VLAN interface 4. Repeat Steps 1 & 2 for the remaining data VLANs (for this paper: 151, ) 5. Configure the global common virtual MAC address. Configure virtual MAC address VIP/VARP verification 1. Display the virtual router s IP address assignments by typing the show ip virtual-router command at the switch console. Display IP addresses assigned to the virtual router

11 Technical white paper Page 11 HPE OneView Configuration In order to achieve the architected redundancy from each server to the MLAG enabled upstream network switches, two connections should be configured: one is from the server s NIC 1 to Ethernet fabric A and the other is from the server s NIC 2 to Ethernet fabric B. The following steps are necessary to create and configure these connections: 1. Create Networks and Network Sets 2. Create a Logical Interconnect Uplink Set 3. Create Server Profile Network Connections Note: An overview of OneView terms and concepts is included in Appendix D Create Networks and Network Sets To create networks and Network-sets, from the HPE OneView Dashboard, select OneView>NETWORKING >>Networks / Network Sets. Network ToR-VM-App with VLAN 154 is created as shown in the following figure. Create Network

12 Technical white paper Page Repeat these steps to create other desired networks. Click Create + to stay in the create network wizard. The required multiple networks have been created Use of network sets allows for multiple networks to be treated as a single construct and therefore makes it easier to assign multiple networks to any given server. 2. An example of creating a network set. Create the required group or set of multiple networks

13 Technical white paper Page An example of a network set configured as DCA-ToR-NetSet that contains five networks with corresponding VLAN values. A network set Logical Interconnect Groups, Enclosure Groups, and Logical Enclosures in Synergy The terms Logical Interconnect Group (LIG), Logical Enclosures (LE), and Enclosure Groups (EG) are important concepts in a Synergy solution and are briefly discussed here. Refer to Appendix D for more details on these terms The template of configuration parameters represented by an individual LIG is combined with other LIGs that represent additional interconnect options like SAS interconnects, SAN interconnects, etc. These multiple LIGs are placed within another template construct known as an EG. These combined templates are then applied to physical enclosures (frames) and interconnect hardware. This action causes the hardware to be actually configured (or Composed ) with the parameters in the EG. At that point it is ready for an administrator to start creating server profiles used for system deployment. The following steps in this paper assume that LIGs, LEs and EGs have already been created, as they might be in an existing Synergy installation. Users that are performing initial deployments of Synergy, or if LIGs, LEs, and EGs have not been created should refer to Appendix C for the steps and sequence to create these objects. Create a Logical Interconnect Group Uplink-Set This section demonstrates editing an existing LIG named DCA-SolCenter-LIG. The process of configuring an Uplink-set involves three steps found under the Logical Interconnect Group section in OneView. 1. The first section is general information. Enter a name for the uplink set then select type, in this case Ethernet will be selected, finally a LACP timer option is set. 2. In the second section, the configuration of the Networks occurs. Select our previously defined networks that will be used in this uplink set connection. 3. The last section defines the actual Uplink ports used to connect to the ToR external switches. This section details how the assignment of the uplink ports for this shared uplink set (SUS) will occur 4. Complete the wizard by clicking Create or Create+. Synergy Master Virtual Connect Modules Cluster Links Connections

14 Technical white paper Page 14 Note: When using HPE s VC SE 40Gb F8 for Synergy interconnects, the support for MC-LAG (MLAG) requires cluster links between master interconnect modules. The Synergy Virtual Connect interconnects use ports seven (7) and eight (8) to connect these required cluster link cables. 5. To edit an existing Logical Interconnect Group and add/change/delete networks and SUS from the uplinks, use the HPE OneView Dashboard. Click on OneView>NETWORKING >>Logical Interconnect Group (LIG) / Logical Interconnects (LI) and then click Edit. Move to the Logical Interconnect Group section. 6. Hover over to the right of Redundancy setting and click on the edit hyperlink. Editing a Logical Interconnect Group 7. Once in the Logical Interconnect edit mode and then in the Logical Interconnect Group section, click Add uplink set. 8. Define the correct network type, networks, and uplinks ports as shown in the figure below.

15 Technical white paper Page 15 Create an Uplink Set After uplink-set for the connections between Synergy Master VCs and Arista switches fully configured in the logical Interconnect Group (LIG), and Logical Interconnect (LI) is synchronize from group (LIG).

16 Technical white paper Page Verification of Uplinks and LLDP neighbors from the Arista switches. (After Logical Interconnect instantiated and synced, Ports are up) Show neighbors command from Switch 1 Show neighbors command from Switch Verification of Uplinks of the four links bundled together from both of the switches. Show interface status Show trunk status from Switch 1 Show trunk status from Switch 2 All four 10 Gb links are active and bundle as 40 Gb logical link from both switches. Links are aggregated as port-channel 700 (MLAG 700) as show above This 40 Gb logical link is layer 2 trunk link and pass all the desired VLANs. OneView configured uplink set DCA-ToR for these connections below. The details of connected upstream device name, port information can be seen in the Uplink Ports section in OneView as shown below. 1. Return to OneView and select the HPE OneView Dashboard 2. Click on OneView>INTERCONNECTS >> and highlight one of the VC interconnects. 3. In the Interconnects view, use the pulldown and select Uplink Ports to get the statistics view.

17 Technical white paper Page 17 Show virtual connect connection information

18 Technical white paper Page 18 Show virtual connect connection information Logical diagram of MC-LAG configuration Create Server Profile Network Connections As describthaed in the above network and network-set sections, Downlink connections are configured as part of a server s profile or within templates. With multiple NICs defined in a node, each server profile should be configured to support dual connections from NIC#1 to an A side fabric and from NIC#2 to a B side fabric of the Synergy Virtual Connect. In this way full redundancy and the benefits from MC-LAG are achieved.

19 Technical white paper Page To add a network connection as part of a server profile or server profile template, either use the creation wizard or edit an existing server profile. 2. From the HPE OneView Dashboard, select OneView>SERVERS>>Server Profiles / Server Profile Templates, then in the connection section, click add. Creating the requisite server profile settings

20 Technical white paper Page The following is an example of configuring Ethernet downlink connection A for a VMware vsphere host server profile. Note that the network set DCA-ToR-NetSet, which was created earlier, is used in this step. Using this network set easily allows multiple VLANs/networks to be assigned. Repeat this step for connection B. The Add Connection wizard

21 Technical white paper Page The following graphic displays both configured Ethernet downlink connections A and B. Configured network connections 5. Downlinks, which are the connections from VCs to network of the compute nodes can be seen from downlink ports of the Interconnects under NETWORKING > Interconnects >> Click name of interconnects and then Downlink Ports: Downlink ports detail view

22 Technical white paper Page 22 ESXi/VM Network Configuration For testing purposes, VMware vsphere 6.0 update 2 was selected. An ESXi host was deployed as the virtualized infrastructure platform Hypervisor in the solution. The ESXi host was added to vcenter and configured with a distributed virtual switch (DVS) containing dual uplinks as shown below. DVS configuration details One test VM was created and assigned an IP address of Additionally the network connection was assigned to a port group called VM-App and is setup to use VLAN 154. DVS configuration details Note The MLAG configuration that has been detailed in previous sections of this paper provides redundancy for network links between the VC modules and the ToR switch. For the network links between the VC modules and server NICs, some of form of NIC teaming is required for redundancy. VMware s ESXi vswitch natively provides this functionality. For other OS s, users should ensure some form of host NIC teaming is implemented.

23 Technical white paper Page 23 The following logical diagram illustrates how the VM s data traffic will traverse the VCs, up to the top of rack switches, and out to the Internet in this case. The server has dual links (A/B) each reaching the VCs. The two VCs are implemented with MLAG functionality. One logical connection has been created between the VCs and the Arista peer switches. Logical configuration of test environment Simple Network Connectivity Test A VM (Window 2012R with MAC address of ) connected to port-group VM-App was used to verify basic network connectivity. 1. Start the VM network information and internet access test, by logging in to the operating system of the VM 2. From a command prompt, type ipconfig /all

24 Technical white paper Page Ping an external web site VM NIC network configuration with ipconfig VM Internet end to end Testing: (Ping test) 4. Back on the Arista switches, ARP table Information can be shown by using the show ip arp command. The VM s MAC address can be seen in the ARP table where MAC learned from as shown below. (VM MAC address is learned from switch 2 for this case) VM on VLAN 154 not learned VM MAC learned from Switch 2 Both the host mgmt NIC on VLAN 150 and the VM on VLAN 154 are learned from logical link Port-Channel700. Test VM successfully accesses data center core network and Internet resources. Conclusion By utilizing MC-LAG, customers can achieve a robust, redundant network environment that can survive multiple points (N+2) of failure within the environment and still keep data traffic moving form system to system. Utilizing Arista Switch MLAG (or MC-LAG) as implemented in the HPE Synergy solution in conjunction with Arista switches, this design goal can be achieved.

25 Technical white paper Page 25 Appendix A - Bill of Materials Note Part numbers used are based on the part numbers that were used for testing and subject to change. The bill of materials does not include complete support options or other rack and power requirements. If you have questions regarding ordering, please consult with your HPE Reseller or HPE Sales Representative for more details. hpe.com/us/en/services/consulting.html Table A-1. Bill of Materials Qty Part Number Description Arista Switches 2 JH581A Arista - DCS-7050SX-64 - switch - 64 ports - managed - rack-mountable Synergy Network Component B21 HPE Synergy 20Gb Interconnect Link Mod B23 HPE VC SE 40Gb F8 Module B21 HPE Synergy 3820C 10/20Gb CNA (one per compute node) B21 HPE BLc QSFP+ to SFP+ Adapter B21 HPE BLc 40G QSFP+ QSFP+ 3m DAC Cable

26 Technical white paper Page 26 Appendix B - Switch Configuration DCA-AR7050SX-01#show run Command: show running-config device: DCA-AR7050SX-01 (DCS-7050SX-64, EOS F) boot system flash:/eos f.swi transceiver qsfp default-mode 4x10G ip virtual-router mac-address mlag-peer hostname DCA-AR7050SX-01 ntp server spanning-tree mode mstp no spanning-tree vlan 4094 service unsupported-transceiver hpedcalab c4a6b356 aaa root secret 5 $1$1.SoCUkg$1y2E8bQMlITTt1jeODXEs/ username admin privilege 15 role network-admin secret 5 $1$QbZBtbiM$yISOJJRxr2qYk1i229np/. username dca-admin privilege 15 secret 5 $1$qwFN..c3$M8093lONojPzT1vsdgalE0 clock timezone US/Central vlan 3 vlan 150 name vsphere-mgmt vlan 151 name vsphere-vmotion vlan 153 name VM-Web vlan 154 name VM-App vlan 155 name VM-DB vlan 4094 trunk group MLAG-Peer interface Port-Channel100 switchport trunk allowed vlan 3 switchport mode trunk mlag 100 interface Port-Channel700 switchport trunk allowed vlan

27 Technical white paper Page 27 switchport mode trunk mlag 700 interface Port-Channel1000 switchport trunk allowed vlan 4094 switchport mode trunk switchport trunk group MLAG-Peer interface Ethernet1 shutdown switchport mode trunk channel-group 100 mode active interface Ethernet2 switchport mode trunk channel-group 100 mode active interface Ethernet3-16 interface Ethernet17 channel-group 1000 mode active interface Ethernet18 channel-group 1000 mode active interface Ethernet19-22 interface Ethernet23 channel-group 700 mode active interface Ethernet24 channel-group 700 mode active interface Ethernet49/1-4 interface Ethernet50/1-4 interface Ethernet51/1-4 interface Ethernet52/1-4 interface Management1 ip address /22 interface Vlan3 description Connection to ToR Switches of Synergy - OSPF SVI (Move from NX6K-01/02) ip address /29 ip ospf mtu-ignore ip ospf area interface Vlan150 description vsphere-mgmt ip address /24 ip virtual-router address interface Vlan151 description VM-vMotion ip address /24 ip virtual-router address

28 Technical white paper Page 28 interface Vlan153 description VM-Web ip address /24 ip virtual-router address interface Vlan154 description VM-App ip address /24 ip virtual-router address interface Vlan155 description VM-DB ip address /24 ip virtual-router address interface Vlan4094 no autostate ip address /30 ip virtual-router mac-address 00:1c:73:00:00:99 ip route / ip routing mlag configuration domain-id DCA-Arista-1 local-interface Vlan4094 peer-address peer-link Port-Channel1000 reload-delay 500 router ospf 1 network /24 area network /24 area network /24 area network /24 area network /24 area max-lsa management api http-commands no shutdown End DCA-AR7050SX-02#show run Command: show running-config device: DCA-AR7050SX-02 (DCS-7050SX-64, EOS F) boot system flash:/eos f.swi transceiver qsfp default-mode 4x10G ip virtual-router mac-address mlag-peer hostname DCA-AR7050SX-02

29 Technical white paper Page 29 ntp server spanning-tree mode mstp no spanning-tree vlan 4094 service unsupported-transceiver hpedcalab c4a6b356 enable secret 5 $1$B8nMySQ8$pFtZCenUfNPAxMfYCYkvd. no aaa root username admin privilege 15 role network-admin secret 5 $1$X2O9mSvc$noTw51a.lB4q5ufS9hral/ username dca-admin privilege 15 secret 5 $1$yAAKysBl$rRvruB2wajSpBSUUknWqH. clock timezone US/Central vlan 3 vlan 150 name vsphere-mgmt vlan 151 name vsphere-vmotion vlan 153 name VM-Web vlan 154 name VM-App vlan 155 name VM-DB trunk group MLAG-Peer interface Port-Channel100 switchport trunk allowed vlan 3 switchport mode trunk mlag 100 interface Port-Channel700 switchport trunk allowed vlan switchport mode trunk mlag 700 interface Port-Channel1000 switchport trunk allowed vlan 4094 switchport mode trunk switchport trunk group MLAG-Peer interface Ethernet1 shutdown channel-group 100 mode active interface Ethernet2 channel-group 100 mode active

30 Technical white paper Page 30 interface Ethernet3-8 interface Ethernet9 switchport trunk allowed vlan 40 switchport mode trunk interface Ethernet10 interface Ethernet11-16 interface Ethernet17 channel-group 1000 mode active interface Ethernet18 channel-group 1000 mode active interface Ethernet19-22 interface Ethernet23 channel-group 700 mode active interface Ethernet24 channel-group 700 mode active interface Ethernet25-48 interface Ethernet49/1-4 interface Ethernet50/1-4 interface Ethernet51/1-4 interface Ethernet52/1-4 interface Management1 ip address /22 interface Vlan3 description Connection to ToR Switches of Synergy - OSPF SVI ip address /29 ip ospf cost 120 ip ospf mtu-ignore ip ospf area interface Vlan150 description vsphere-mgmt ip address /24 ip virtual-router address interface Vlan151 description VM-vMotion ip address /24 ip virtual-router address interface Vlan153 description VM-Web

31 Technical white paper Page 31 ip address /24 ip virtual-router address interface Vlan154 description VM-App ip address /24 ip virtual-router address interface Vlan155 description VM-DB ip address /24 ip virtual-router address interface Vlan4094 ip address /30 ip virtual-router mac-address 00:1c:73:00:00:99 ip route / ip routing mlag configuration domain-id DCA-Arista-1 local-interface Vlan4094 peer-address peer-link Port-Channel1000 reload-delay 500 router ospf 1 network /24 area network /24 area network /24 area network /24 area network /24 area max-lsa management api http-commands no shutdown end #End of Configurations

32 Technical white paper Page 32 Appendix C: Configure resources in HPE OneView 1. Add users to the appliance. a. Create user accounts with specific privileges and local or directory-based authentication b. Add a fully authorized local user (Infrastructure administrator) c. Add a local user with specialized access d. Add a fully authorized user with authentication by membership in an organizational directory e. Add a user with role-based access and authentication by membership in an organizational directory f. Create user accounts assigned with predefined or specialized privileges with local or directory-based authentication. g. See the Users and Groups online help for more information 2. Add firmware bundle to the appliance firmware repository. a. Add the latest firmware bundle to the appliance. See the Firmware Bundles online help for more information. 3. Create networks. a. Create Ethernet networks for data b. Create Fibre Channel over Ethernet networks for storage. See the Networks online help for more information. 4. Create network sets. a. Create network sets to group Ethernet networks together to simplify management. See the Network Sets online help for more information. 5. Create one or more logical interconnect groups. a. Create one or more logical interconnect groups to define the connections between your networks and interconnect uplink ports. See the Logical Interconnect Groups online help for more information. 6. Create an enclosure group. a. Create an enclosure group to define and maintain consistent configurations and to be able to detect and manage devices such as interconnects and server hardware in your frames. See the Enclosure Groups online help for more information. 7. Create a logical enclosure. a. Create a logical enclosure to define asset of enclosures to which to apply an enclosure group. See the Logical Enclosures online help for more information. 8. Optional: Add storage systems and storage pools. a. Add storage systems to the appliance b. Add storage pools to the appliance. See the Storage Systems online help and the Storage Pools online help for more information. 9. Optional: Create volumes. a. Create volumes in the storage pools. b. You can also create volumes by creating volume templates. c. You can add existing volumes from storage systems to the appliance. See the Volumes online help and the Volume Templates online help for more information. 10. Optional: Add a SAN manager to the appliance to manage SAN storage. a. Add a SAN manager to access the SANs it manages. See the SAN Managers online help for more information. 11. Optional: Associate SANs with networks. a. Associate SANs with networks in HPE OneView. See the SAN Managers online help for more information. 12. Create server profiles and apply them to server hardware. a. Create and apply server profiles to define common configurations for your server hardware. See the Server Profiles online help for more information. 13. Optional: Attach a SAN volume to a server profile. a. Attach a SAN volume to a sever profile. See the Server Profiles online help for more information. 14. Save the appliance configuration to a backup file. a. Save the initial appliance configuration settings and database to a backup file in the event that you need to restore the appliance to its current configuration in the future. See the Settings online help for more information about creating and saving appliance backup files.

33 Technical white paper Page 33 Appendix D: HPE OneView Basic Concepts HPE OneView is an integrated, converged management platform, which runs on the Synergy Composer Appliances. It provides software-defined resources, such as configuration templates for the ecosystem as well as individual system templates and server profiles. This enables the operations users to capture the best practices across a variety of disciplines, including networking, storage, hardware configuration, operating system build, and configuration. It manages compute, network, and storage resources within HPE Synergy Composable Infrastructure as well as connections to a host of external resources HPE Virtual Connect was introduced to simplify server connection management, provide cable reduction, and bring down the siloes between server, storage, and network teams. It enables users to rapidly change and deploy server connectivity within these connected environments. Terms and Definitions: Synergy Frame Fabric Fabrics define connectivity for the servers in HPE OneView logical interconnect group to the data center infrastructure. Uplink ports that are part of the fabric present themselves to the data center switches. Synergy frame and OneView management support up to three distinct fabrics. Module or Interconnect Module (ICM) and bays refers to the I/O module installed into interconnect Module Bays in the back of the Synergy frame. There are six bays and bays 1-3 are path A while bays 4 6 are path B of each fabric. Master vs. Satellite Module The master module contains intelligent networking capabilities that extends connectivity to multiple frames through Satellite Interconnect Modules. This can eliminate the top of rack switch need and substantially reduce cost. The reduction in components also simplifies fabric management at scale while consuming fewer ports at the data center aggregation layer. Networks A network represents a Fibre Channel, Ethernet, or Fibre Channel over Ethernet (FCoE) network in the data center. A network resource defined under NETWORKING in OneView and can be associated with connections as part of server profile or server profile template, or as part of uplink set in defining logical interconnect group / logical interconnect. Multiple networks and Network set A network set is a logical object that groups multiple tagged Ethernet networks and VLANs and identified by a single name. Network sets are used to simplify configuring network connectivity in server profile. It allows a quick deployment of network environment changes to multiple server profiles. Logical interconnect Group (LIG), Logical interconnect (LI), and Interconnect - The logical interconnect group is a template. It defines the physical and logical configuration of the interconnects that are configured together to form a logical interconnect. A logical interconnect is a single entity for multiple physical interconnects. The interconnect is a physical representation of a interconnect module and its connections. The configurations between logical interconnect group and logical interconnect must be matched. Enclosure Groups (EG) and Logical Enclosures (LE) - An enclosure group is a logical resource that defines a set of enclosures (or frames) that use the same configuration for network connectivity. An enclosure group is populated with LIGs, which ensures that every enclosure in the enclosure group is configured identically with regard to uplinks and data center networks. A logical enclosure maps EG s to physical enclosures (or frames) and is the means for the LIG and EG settings to be applied to the environment. Uplink-Set or Shared Uplink Set (SUS) Part of logical interconnect group / logical interconnect. Uplink sets define the uplink connectivity for selected networks. Network types in an uplink set can either be an Ethernet or Fibre Channel (FC), but not both. Server Profile Template, Server Profile, and Server Server profile is the logical configuration of server that cover all aspects of a server including firmware versioning, BIOS settings, options, connectivity (network and storage), boot configuration, and serial number. Server profile template is a template that simplifies management of server profiles when any changes is needed. Network Connections part of server profile configuration to define downstream networks and network connections.

34 Technical white paper Page 34 Resources and additional links HPE Servers hpe.com/servers HPE Networking hpe.com/networking HPE Synergy Frame QuickSpecs HPE Synergy Configuration and Compatibility Guide (includes details on the Master / Satellite architecture) Arista MLAG Configuration Guide Arista active-active router redundancy using VARP Guide To help us improve our documents, please provide feedback at hpe.com/contact/feedback.

35 Technical White Paper Page 35 Sign up for updates Rate this document Copyright 2015 Hewlett Packard Enterprise Development LP. The information contained herein is subject to change without notice. The only warranties for HPE 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. HPE shall not be liable for technical or editorial errors or omissions contained herein. Add trademark acknowledgments as needed. For trademark policy, see 4AA4-xxxxENW, Month 20XX, Rev. #