2101-lynch-hp networking and virtual connect flex fabric best practices student lab guide_final (2)

HP Discover 2011 Hands-On Lab

Best Practices for HP Virtual Connect FlexFabric and HP

Networking A-Series

Table of contents

Section 1 – HP A5800 IRF and Networking Config ........................................................................................................................ 4

Objectives .................................................................................................................................................................................................. 4

Task 1: Name the system and enable Telnet access ................................................................................................................ 4

Task 2: Configure Switch 1 to be IRF Master .............................................................................................................................. 4

Task 3: Configure Switch 2 to be IRF Slave .................................................................................................................................. 5

Task 4: Activate IRF-Ports on switch 2 and verify IRF functionality ................................................................................... 6

Task 5: Complete configuration of the IRF system ................................................................................................................... 6

Section 2 Create Virtual Connect Domain ....................................................................................................................................... 12

Objectives ................................................................................................................................................................................................ 12

Task 1: Create Virtual Connect Domain....................................................................................................................................... 12

Task 2: Create Active/Active Shared Uplink Sets ..................................................................................................................... 15

Task 4: Create Server Profile ............................................................................................................................................................. 16

Section 3 Failure Scenarios .................................................................................................................................................................... 18

Objectives ................................................................................................................................................................................................ 18

Task 1: Verify NCU Team and Start Streaming Sample Video ........................................................................................... 18

Task 2: Shutdown IRF Member Ports ........................................................................................................................................... 19

Task 3: Shutdown All IRF Port Members ..................................................................................................................................... 20

Appendix A – Student POD Information .......................................................................................................................................... 22

For more information about HP Certifications .............................................................................................................................. 26

Figure 1-1c: Lab Topology, Cabling, Names

Split LACP

A5

82

0 IR

F

Student Switch

IRF Member 1

Switch-X

Flex-Fabric

Bay-1

(FF-A)

Student Switch

IRF Member 2

Switch-X

Flex-Fabric

Bay-2

(FF-B)

Core Switch

IRF Member 1

Core Switch

IRF Member 2

c7

00

0 E

nclo

su

re

OA

A5

82

0 IR

F

Workstation

OA, Workstation, & Video Network

Port 1/0/1 = FF-A, BAG 2

Port 1/0/2 = FF-B, BAG 3

Port enc0:1:X3 = IRF-1, LACP


Port 2/0/1 = FF-A, BAG 2

Port 2/0/2 = FF-B, BAG 3



Multi-Active Detect

Logical Reference

1/0/28 & 2/0/28

IRF-Port-1: 1/0/22, 2/0/23

IRF-Port-2: 1/0/23, 2/0/22

Port 1/0/24, BAG 1 Port 2/0/24, BAG 1

OA IP = 10.1.100.X0

X = POD ID

Figure 1-1 provides a reference for what you will be building in this lab activity. Note that you will

be replacing any reference to X with your POD-ID. For example the name of the IRF system for

POD-1 will be “Switch-1”.

Ports 1/0/24 on both switches are connected to the core, which are disabled. During the lab, your

ports will be enabled once you have completed the IRF portion of the lab.

Each POD will have a workstation connected to a back-end network to be used for IP connectivity to

the Onboard Administrator on the c7000 enclosure as well as direct console access to the switches.

Appendix A contains the list of all relevant IP Addresses per Student POD.

Figure 1-2: Lab IP and VLAN Configuration

Split LACP

A5

82

0 IR

F

Student Switch

IRF Member 1

Switch-X

Flex-Fabric

Bay-1

Student Switch

IRF Member 2

Switch-X

Flex-Fabric

Bay-2

Core Switch

IRF Member 1

Core Switch

IRF Member 2

c7

00

0 E

nclo

su

re

ILO

A5

82

0 IR

FOSPF Backbone

VLAN: 5 Tagged

IP Address: 172.16.5.X0

Local VLANs

VLAN: X0

A5800 IRF IP: 192.168.X0.1

VLAN: X1

A5800 IRF IP: 192.168.X1.1

VLAN: X2

A5800 IRF IP: 192.168.X2.1

VLAN: X3

Server Profile

Connection 1: VLANX0-A

Connection 2: VLANX0-B

Server IP: 192.168.X0.50

Gateway: 192.168.X0.1

Local VLANs

OSPF Backbone

Server VLAN

Core IP Config

172.16.5.254

Figure 1-2 provides a reference for the IP and VLAN configuration for this lab. Again you will be

replacing any reference to X with your POD-ID. For example the server IP address for POD-1 will be

19.168.10.50 with a default gateway of 192.168.10.1. You can also use the table below as a

reference for VLAN and IP configuration.

Switch Name VLAN ID IP Address

Switch-X 5 172.16.5.X0

Switch-X X0 192.168.X0.1

Switch-X X1 192.168.X1.1

Switch-X X2 192.168.X2.1

Switch-X X3 MAD/BFD

Section 1 – HP A5800 IRF and Networking Config

Objectives

After completing this section you will be able to:

• Perform basic switch configuration

• Configure and verify operation of a two switch IRF system

Task 1: Name the system and enable Telnet access

1. Establish a console connection with first Switch and assign it the switch name: Switch-<POD-

ID>.

Example (POD-5): Switch-5

<Switch>system-view

[Switch]sysname Switch-<POD-ID>

[Switch-5]

2. Setup a local user account to be used for telnet access. The username will be “admin” with a

plain-text password of “hpdiscover”. You’ll also need to permit this user access to the Telnet

interface.

[Switch-5]local-user admin

[Switch-5-luser-admin]service-type telnet

[Switch-5-luser-admin]password simple password

[Switch-5-luser-admin]authorization-attribute level 3

[Switch-5-luser-admin]quit

3. Now that a local-user exists the remote console ports need to be set to use local

authentication.

[Switch-5]user-interface vty 0 4

[Switch-5-ui-vty0-4]authentication-mode scheme

4. Finally the Telnet server needs to be enabled. Note that on the A5800 this is done by default

but on some products like the A-Series MSR routers it is disabled by default.

[Switch-5]telnet server enable

[Switch-5]save

Task 2: Configure Switch 1 to be IRF Master

5. Configure the IRF priority and the IRF Ports.

[Switch-5]irf member 1 priority 32

[Switch-5]int ten 1/0/22

[Switch-5-int-ten1/0/22]shutdown



[Switch-5]irf-port 1/1

[Switch-5-irf-port1/1]port group int ten 1/0/22

[Switch-5-irf-port1/1]port group int ten 1/0/23


[Switch-5-int-ten1/0/22]undo shutdown



[Switch-5]quit

[Switch-5]irf-port-configuration active

<Switch-5>display irf

<Switch-5>display irf configuration

<Switch-5>display irf topology

<Switch-5>save

Task 3: Configure Switch 2 to be IRF Slave

1. Establish a console connection with the second switch.

2. Change the device id to 2 (unit number)

<Switch>system-view

Display the current IRF information for Switch 2.

<Switch>display irf

<Switch>display irf configuration

<Switch>display irf topology

What is the member ID, role and priority in the default state?

[Switch]irf member 1 renumber 2

[Switch]quit


Confirm that new member ID will be 2

<Switch>reboot

3. Configure the IRF Ports on Switch 2

<Switch>display irf config

Confirm that A2 has the new member id

<Switch>system-view

[Switch]int ten 2/0/22

[Switch-int-ten2/0/22]shutdown

[Switch-int-ten2/0/22]int ten 2/0/23

[Switch-int-ten2/0/23]shutdown

[Switch]irf-port 2/2

[Switch-irf-port2/2]port group int ten 2/0/23

[Switch-irf-port2/2]port group int ten 2/0/22

Why are the IRF port assignments the reverse of Switch 1?

[Switch]int ten 2/0/22

[Switch-int-ten2/0/22]undo shutdown

[Switch-int-ten2/0/22]int ten 2/0/23

[Switch-int-ten2/0/23]undo shutdown

[Switch-int-ten2/0/23]quit

[Switch]save

[Switch]irf-port-configuration active

At this point member 2 will reboot and accept its role as a member of the IRF.

Task 4: Verify IRF functionality

1. Verify IRF performance on Switch 1

<Switch>display irf



Status: IRF should be up and running, messages will display to Switch 1 as Switch 2 reboots

reporting the change in IRF topology and status

2. On the management connection for Switch 2 verify IRF performance

<Switch>display irf



Task 5: Complete configuration of the IRF system

At this point physical Switches 1 and 2 are acting as a single virtual switch. The configuration of

both switches can be performed from one or both console connections.

How are the ports on the 2nd switches identified?

1. Establish a console connection to either switch in the IRF system.

2. Configure VLAN interfaces and OSPF.

In the examples below certain values will require your POD-ID to complete. For VLANs you will see

the example reference VLAN X0 where the “X” represents your POD-ID. If you have POD-ID 7 the

value in your config would then be VLAN 70.

This same approach is taken for IP addresses. In the examples below IP addresses will be referenced

similarly. The third octet will be represented as 172.16.5.X0 where your POD-ID will again be “X”.

So for this example a POD-ID of 10 would result in 172.16.5.100 for this value.

<Switch_A1>system-view

[Switch]vlan 5

[Switch-vlan5]vlan X0

[Switch-vlanX0]vlan X1

[Switch-vlanX1]vlan X2

[Switch-vlanX2]int vlan 5

[Switch-int-vlan5]ip address 172.16.5.X0 24

Try issuing the command “display this” after setting the IP address of a VLAN interface. What

information does this command provide?

[Switch-int-vlan5]int vlan X0

[Switch-int-vlanX0]ip address 192.168.X0.1 24

[Switch-int-vlanX0]int vlan X1


[Switch-int-vlanX1]int vlan X2


[Switch-int-vlanX2]quit

[Switch]ospf 1

[Switch-ospf1]area 0

[Switch-ospf1-area0]network 192.168.0.0 0.0.255.255

[Switch-ospf1-area0]network 172.16.0.0 0.0.255.255

[Switch-ospf1-area0]quit

[Switch-ospf1]quit

To check your work use the “display ip interface brief” command to list all configured IP interfaces

on this system.

3. Configure Bridge Aggregation Groups (BAGs) 1, 2, and 3

[Switch]int bridge-aggregation 1

[Switch-int-bragg1]link-aggregation mode dynamic

[Switch-int-bragg1]description “BAG to Core”

[Switch-int-bragg1]quit

[Switch]int te1/0/24

[Switch-int-ten1/0/24]port link-aggregation group 1

[Switch-int-ten1/0/24]int te2/0/24

Which physical switch does port 2/0/24 belong to?

Note that this port can now be configured from Member Switch 1.




[Switch-int-bragg1]port link-type trunk

[Switch-int-bragg1]port trunk permit vlan 5

Use the “display this” command to see the link-type and previously configured features for this BAG.

Move on to BAGs 2 & 3. This is a useful command for checking your work as you move through a

task.




[Switch-int-bragg2]description “BAG to enc0:1:X3 enc0:1:X4”


[Switch]int te1/0/1







[Switch-int-bragg2]port trunk permit vlan X0 to X2


Setting the aggregation group’s link-type to trunk tells the switch to apply an 802.1q tag for each

packet that egresses this interface. The “vlan X to X” argument allows for a range of VLAN-IDs to be

permitted on this trunked interface. Note that the default VLAN is VLAN-1 and will also be

designated as the PVID (untagged VLAN) for these trunked ports.



[Switch-int-bragg3]description “BAG to enc0:2:X3 enc0:2:X4”


[Switch]int te1/0/2







[Switch-int-bragg2]port trunk permit vlan X0 to X2


You can use the “display interface” and “display current-configuration interface” commands to check

the VLAN memberships configured for a port. Use “display interface bridge-aggregation 3” to check

the VLAN membership for BAG 3.

4. Establishing MAD/BFD between IRF members

The lab diagram references a physical connection for MAD traffic which is a common approach to

enabling MAD/BFD. For the purposes of this lab we’re going to place the MAD/BFD traffic onto

VLAN X3 rather than running a dedicated cable. VLAN X3 has already been created so the next step

is to configure the MAD/BFD interface and establish the MAD connection.

[Switch]vlan X3

[Switch-vlanX3]port gi1/0/28

[Switch-vlanX3]port gi2/0/28

[Switch] interface vlan X3

[Switch-int-vlanX1]mad bfd enable

[Switch-int-vlanX1]mad ip address 10.255.255.1 24 member 1

[Switch-int-vlanX1]mad ip address 10.255.255.2 24 member 2

[Switch-int-vlanX1]quit

[Switch]mad exclude interface gi1/0/28

[Switch]mad exclude interface gi2/0/28

[Switch]quit

Now use the “display mad” and “display mad verbose” commands to view the status of MAD.

This feature allows multiple members of an IRF system to detect a state where both believe that they

are master. Using BFD allows the members to establish a UDP session and use that connection to

monitor health. In the event that multi-masters are detected the lower priority members will shut

down all interfaces to prevent network issues that would occur in this state.

You should get a report like this:

Current MAD status: Detect

Excluded ports(configurable):

Excluded ports(cannot be configured):

Ten-GigabitEthernet1/0/22




MAD LACP disabled.

MAD BFD enabled interface:

Vlan-interface4094

mad ip address 10.255.255.1 255.255.255.0 member 1

mad ip address 10.255.255.2 255.255.255.0 member 2

5. Enabling Spanning Tree Protocol (STP) and Connect to Core

You now have most of the fundamental networking in place at the A5800 level of this lab. The next

step is to connect to the core and verify IP connectivity, OSPF, and LACP. This portion of the lab will

mostly consist of verifying the operation of configuration made to this point.

1. Enable STP globally (make sure that you are at the base system level and not at the interface

level of the config)

[Switch]stp enable

[Switch]save

2. Enable “stp edged-port enable” on the ports connecting to Virtual Connect

[Switch]int ten1/0/1

[Switch]stp edged-port enable







[Switch]save

The command stp edged-port enable is exactly the same as the Cisco spanning-tree

portfast command.

Your uplinks to the core have been disabled. When you are ready to proceed have the instructor

enable the core links to BAG-3.

You should see notifications on the console that the interfaces are up and updates from OSPF, STP,

and LACP. Use the following commands to verify operation. You’ll step your way from verifying

basic connectivity

display current-configuration (CTRL-G)

display stp

display interface [brief]

display ip route (CTRL-L)

display ospf [brief | peer | routing]

display lldp neighbor [brief, list]

display port trunk

display link-aggregation [summary | verbose]

display vlan [all | VLAN-ID]

ping

3. Verify physical connectivity to the core. You can use LLDP and display interface commands.

4. Once physical connectivity has been verified you need to check the operation of LACP.

What is the status of the three BAGs created so far (note that 1&2 have not been configured on the

server side yet)

What are the 5 flags listed for each of the BAGs what’s different between BAG1 and BAGs 2&3?

5. Check STP operation and see what links are blocking and forwarding.

6. See if OSPF has formed and adjacency with the core.

How many OSFP neighbors do you see?

What routes have been learned via OSFP?

Ping the core router 172.16.5.254 (if another POD is to this same point in the lab you should be able

to ping their IRF system IP interfaces as well).

This concludes this section of the lab.

Section 2 Create Virtual Connect Domain

Objectives

After completing this lab you will be able to:

Create a Virtual Connect Domain

Create Ethernet Networks

Create Bridge Aggregates to Virtual Connect uplink ports

Credentials

Onboard Administrator admin hpdiscover

Windows Host Administrator hpdiscover

Task 1: Create Virtual Connect Domain

1. Log into OA via SSH with putty

a. Examine your POD table in Appexdix A.

1. Execute “connect interconnect 1”

2. Provide the Administrator credentials

3. Import local enclosure by using “import enclosure” command

->import enclosure Username=admin Password=hpdiscover

Importing enclosure, please wait...

SUCCESS: Enclosure imported

**************************************************************

IMPORT ENCLOSURE SUMMARY

**************************************************************

Enclosure Name : POD-Enclosure

Rack Name : Discover-Rack1

IP Address : 10

Status : OK

**************************************************************

2 VC-ENET Modules and 0 VC-FC Modules:

**************************************************************

=======================================================

Bay Product Name Power UID

=======================================================

1 HP VC FlexFabric 10Gb/24-Port Module On Off

2 HP VC FlexFabric 10Gb/24-Port Module On Off

**************************************************************

1 Physical Servers:

**************************************************************

======================================

Bay Product Name Status UID

======================================

1 ProLiant BL460c G7 Off Off

2 ProLiant BL460c G7 Off Off

**************************************************************

16 Device Bays:

**************************************************************

=================================

Bay Device Status

=================================

1 ProLiant BL460c G7 OK

2 ProLiant BL460c G7 OK

3 <Empty> OK

4 <Empty> OK

5 <Empty> OK

6 <Empty> OK

7 <Empty> OK

8 <Empty> OK

9 <Empty> OK

10 <Empty> OK

11 <Empty> OK

12 <Empty> OK

13 <Empty> OK

14 <Empty> OK

15 <Empty> OK

16 <Empty> OK

**************************************************************

Stacking Links:

**************************************************************

Connection Status : OK

Redundancy Status : OK

===========================================

Link Speed Connected From Connected To

===========================================

1 10Gb enc0:1:X7 enc0:2:X7

2 10Gb enc0:1:X8 enc0:2:X8

4. Execute “show interconnect *”. Verify the output. Examine Firmware version, Product Type, and

Status.

->show interconnect *

ID : enc0:1

Enclosure : STC01-C7K01

Bay : 1

Type : VC-ENET+FC

Product Name : HP VC FlexFabric 10Gb/24-Port Module

Role : Primary

Status : OK

Comm Status : OK

OA Status : OK

Power State : On

MAC Address : 00:24:81:f7:17:85

Node WWN : 10:00:00:11:0a:02:0a:0e

Firmware Version : 3.18 2011-04-01T22:57:39Z

Manufacturer : HP

Part Number : 571956-B21

Spare Part Number : 572213-001

Rack Name : DC-row6-rack14

Serial Number : TW203800F8

UID : Off

--------------------------------------------------------

ID : enc0:2

Enclosure : STC01-C7K01

Bay : 2

Type : VC-ENET+FC

Product Name : HP VC FlexFabric 10Gb/24-Port Module

Role : Standby

Status : OK

Comm Status : OK

OA Status : OK

Power State : On

MAC Address : 00:24:81:f7:17:8b

Node WWN : 10:00:00:11:0a:02:0a:0f

Firmware Version : 3.18 2011-04-01T22:57:39Z

Manufacturer : HP

Part Number : 571956-B21

Spare Part Number : 572213-001

Rack Name : DC-row6-rack14

Serial Number : TW203800F9

UID : Off

5. Define Virtual Connect Managed MAC and WWN Addres pools

set domain MacType=VC-Defined MacPool=[Team_ID]

set domain WwnType=VC-Defined WwnPool=[Team_ID]

Task 2: Create Active/Active Shared Uplink Sets

NOTE: Names within VC CLI are cAsE SeNsItIvE

1. Create UplinkSet_SideA

-> add uplinkset UplinkSet_SideA

-> add uplinkport enc0:1:X3 UplinkSet=UplinkSet_SideA

-> add uplinkport enc0:1:X4 UplinkSet=UplinkSet_SideA

2. Create Ethernet Networks, assigned to UplinkSet_SideA

-> add network vlan_N0A uplinkset=UplinkSet_SideA VLANID=N0




3. Verify both uplink ports are Linked/Active by using the “show uplinkport”

->show uplinkport enc0:1:X3

ID : enc0:1:X3

Enclosure : POD-Enclosure

Status : Linked (Active) (10Gb)

Type : SFP-DAC

Speed : Auto

Used By : UplinkSet_SideA

Connected From : -- --

Connected To : 3c:e5:a6:35:a3:e4 (Ten-GigabitEthernet1/0/1)


ID : enc0:1:X4



Type : SFP-DAC

Speed : Auto

Used By : UplinkSet_SideA



4. Create UplinkSet_SideB

-> add uplinkset UplinkSet_SideB

-> add uplinkport enc0:2:X3 UplinkSet=UplinkSet_SideB

-> add uplinkport enc0:2:X4 UplinkSet=UplinkSet_SideB

5. Create Ethernet Networks, assigned to UplinkSet_SideB

-> add network vlan_N0B uplinkset=UplinkSet_SideB VLANID=N0




6. Verify both uplink ports are Linked/Active by using the “show uplinkport” ->show uplinkport enc0:2:X3

ID : enc0:2:X3



Type : SFP-DAC

Speed : Auto

Used By : UplinkSet_SideB




ID : enc0:2:X4



Type : SFP-DAC

Speed : Auto

Used By : UplinkSet_SideB



7. Telnet to IRF Management IP

8. Verify Bridge Aggregate Status

[Switch-1]display link-aggregation verbose

Note that BAGs 2&3 should look like 1 now. The flags for a functioning LACP link are ACDEF.

Task 4: Create Server Profile

1. Create a server profile for Bay 1

->add profile Bay1 -NoDefaultEnetConn -NoDefaultFcConn -

NoDefaultFcoeConn

SUCCESS: Profile added : Bay1

2. Add vlan_N0A

->add enet-connection Bay1 Network=vlan_N0A

SUCCESS: Connection added to server profile : Bay1

3. Add vlan_N0B

->add enet-connection Bay1 Network=vlan_N0B

SUCCESS: Connection added to server profile : Bay1

4. Assign profile to Bay 1

->assign profile Bay1 enc0:1

SUCCESS: Profile 'Bay1' assigned to device bay enc0:1

->show profile Bay1

Name : Bay1

Device Bay : enc0:1

Server : ProLiant BL460c G7

Status : OK

Serial Number : MXQ01505B1

UUID : 507778MXQ01505B1

Ethernet Network Connections

==============================================================

Port Network Name Status PXE MAC Address Allocated

Speed

==============================================================

1 vlan_N0A OK UseBIOS 00-17-A4-77-24-00 10Gb

2 vlan_N0B OK UseBIOS 00-17-A4-77-24-02 10Gb

Section 3 Failure Scenarios

Objectives

After completing this lab you will be able to:

Examine Virtual Connect Uplink and LAG status

Examine A5820 Port and Bridge-Aggregate Status

Understand failover capabilities of Comware and Virtual Connect

Task 1: Verify NCU Team and Start Streaming Sample Video

1. Log into your Windows server in Bay 1 with the iLO3 Integrated Remote Console

a. Open a Web Browser to your iLO https://10.1.100.N3

b. Login with admin/hpdiscover

2. Verify Local Area Connection and Local Area Connection 2 is both in an NFT team.

a. Open the NCU

b. Verify that the HP Network Team #1 Team has both Local Area Connection and

Local Area Connection #2 as members.

https://10.1.100.n3/

3. Verify the Windows Media Streaming Service is started

4. On your desktop, open the HOL2101-PODid file begin streaming your video. This should

open Windows Media Player.

Task 2: Shutdown IRF Member Ports

1. Log into your IRF switch cluster via the console port

2. Shutdown irf-port-1/1 [member port ten1/0/22]



What happened to the video stream?

3. View the IRF Topology

<Switch>display irf



Is the IRF Cluster still up? How many IRF Port Members are Active?

4. Undo Shutdown irf-port-1/1 [member port ten1/0/22]



5. Shutdown irf-port-2/1 [member port ten2/0/23]

[Switch-5]int ten2/0/23


What happened to the video stream?

6. View the IRF Topology

<Switch>display irf



Is the IRF Cluster still up? How many IRF Port Members are Active?

7. Undo Shutdown irf-port-2/1 [member port ten2/0/23]



Task 3: Shutdown Bridge-Agg2 and Bridge-Agg3

1. Shutdown Bridge-Aggregate 2

[Switch]int bridge2

[Switch-int-bragg2]shutdown

2. Display the Bridge-Aggregate status. Examine the status of Bridge-Aggregate 2.

Examine the state of NIC1 within NCU.

[Switch]display link-agg verbose

What happened to Bridge-Aggregate 2?

3. Re-enable Bridge-Aggregate 2. Wait until the NIC within the OS is Linked before

continuing to Step 4.

[Switch]int bridge2

[Switch-int-bragg2]undo shutdown

4. Shutdown Bridge-Aggregate 3

[Switch]int bridge3

[Switch-int-bragg3]shutdown

Notice what happens to the second NIC and the video stream.

5. Re-enable Bridge-Aggregate 3

[Switch]int bridge3

[Switch-int-bragg3]undo shutdown

Task 4: Shutdown All IRF Port Members

1. Shutdown irf-port-1/1 and irf-port 1/2





What happened to Switch 2?

Appendix A – Student POD Information

POD-1

Onboard Administrator 10.1.100.10 admin/hpdiscover

FlexFabric Bay 1 10.1.100.11 Administrator/DGDNF0FP

FlexFabric Bay 2 10.1.100.12 Administrator/W5PFZ4Z5

iLO Bay 1 10.1.100.13 admin/hpdiscover


Windows Server 192.168.10.50 VID 10

OSPF Interface 172.16.5.10 VID 5

POD-2


FlexFabric Bay 1 10.1.100.21 Administrator/ZHDK02C3

FlexFabric Bay 2 10.1.100.22 Administrator/FGY74GPS





POD-3


FlexFabric Bay 1 10.1.100.31 Administrator/BWZ6H8JP

FlexFabric Bay 2 10.1.100.32 Administrator/BNQBZZSG





POD-4


FlexFabric Bay 1 10.1.100.41 Administrator/WNBR8TH9

FlexFabric Bay 2 10.1.100.42 Administrator/WWKMT38H





POD-5


FlexFabric Bay 1 10.1.100.51 Administrator/BDFFFQ08

FlexFabric Bay 2 10.1.100.52 Administrator/DY0YQPYT





POD-6


FlexFabric Bay 1 10.1.100.61 Administrator/WP5NWKGS

FlexFabric Bay 2 10.1.100.62 Administrator/WXDJFV7Z





POD-7


FlexFabric Bay 1 10.1.100.71 Administrator/M4SYH68Q

FlexFabric Bay 2 10.1.100.72 Administrator/3T3Q2BT6





POD-8


FlexFabric Bay 1 10.1.100.81 Administrator/KJCHMFCQ

FlexFabric Bay 2 10.1.100.82 Administrator/0QM96397





POD-9


FlexFabric Bay 1 10.1.100.91 Administrator/62S442VH

FlexFabric Bay 2 10.1.100.92 Administrator/6J7C0HB4





POD-10


FlexFabric Bay 1 10.1.100.101 Administrator/3BMH5W9K

FlexFabric Bay 2 10.1.100.102 Administrator/ Z46Q8BD7





POD-11


FlexFabric Bay 1 10.1.100.111 Administrator/K09HNYQR

FlexFabric Bay 2 10.1.100.112 Administrator/BNQBZZSG





POD-12


FlexFabric Bay 1 10.1.100.121 Administrator/4DG5Y2Q6

FlexFabric Bay 2 10.1.100.122 Administrator/MC2T2G0W





For more information about HP Certifications

Much of the content presented today at this lab is part of the broader HP Certification curriculum.

Visit http://www.hp.com/certification/ to find out more about the industry’s most complete IT certified

professional program.

ExpertONE: Converged Infrastructure

http://www.hp.com/certification/newops-CI.html

ExpertONE: Networking

http://www.hp.com/certification/expert_one-networking.html

Share with colleagues

© Copyright 20XX 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.

Trademark acknowledgments, if needed.

4AA2-xxxxENW, Created Month 20XX

http://www.hp.com/certification/

http://www.hp.com/certification/newops-CI.html

http://www.hp.com/certification/expert_one-networking.html

http://www.hp.com/go/getconnected








2101-lynch-hp networking and virtual connect flex fabric best practices student lab guide_final (2)

Documents

irf system

irf portion

irf master

irf slave

irf functionality

irf port members

switchx port

hp a5800 irf