HP 5900AF-48XG-4QSFP+ Switch – Copy from USB

Copying files from a USB flash drive Every 5900 switch provides a USB port for you to copy files from a USB flash drive.

To copy a file from a USB flash drive to the Flash memory of the master switch:

1. Reinitialize USB drive :

<HP>cd slot1#flash:/
<HP>%Jan 1 00:27:54:421 2011 HP FS/4/FS_REMOVED: usba: removed from slot 1
%Jan 1 00:27:54:858 2011 HP FS/5/FS_INSERTED: usba: inserted into slot 1

<HP>dir usba0:/
Directory of usba0:
0 -rw- 80509952 Dec 16 2015 10:55:20 5900_5920-CMW710-R2422P01.ipe
1 -rw- 7309312 Jan 01 2011 00:15:46 5900_5920-cmw710-boot-r2311p05.bin
2 -rw- 12679168 Dec 16 2015 10:59:34 5900_5920-cmw710-packet-capture-r2422p01.bin
3 -rw- 54262784 Jan 01 2011 00:13:18 5900_5920-cmw710-system-r2311p05.bin
4 drw- – Aug 03 2016 08:48:02 System Volume Information

2. Checks :
<HP>display boot-loader
Software images on slot 1:
Current software images:
flash:/5900_5920-cmw710-boot-r2311p05.bin
flash:/5900_5920-cmw710-system-r2311p05.bin
Main startup software images:
flash:/5900_5920-cmw710-boot-r2311p05.bin
flash:/5900_5920-cmw710-system-r2311p05.bin
Backup startup software images:
None

3. Copy USB to FLASH :
<HP>Copy usba0:/5900_5920-cmw710-packet-capture-r2422p01.bin to flash:/5900_5920-cmw710-packet-capture-r2422p01.bin
<HP>Copy usba0:/5900_5920-CMW710-R2422P01.ipe to flash:/5900_5920-CMW710-R2422P01.ipe

4. Backup Existing startup Image :
<HP>boot-loader file boot flash:/5900_5920-cmw710-boot-r2311p05.bin system flash:/5900_5920-cmw710-system-r2311p05.bin slot 1 backup

This command will set the backup startup software images. Continue? [Y/N]:y
The images that have passed all examinations will be used as the backup startup software images at the next reboot on slot 1.

5. Setup Main startup Image :
<HP>boot-loader file flash:/5900_5920-CMW710-R2422P01.ipe slot 1 main
Verifying image file………Done.
Images in IPE:
5900_5920-cmw710-boot-r2422p01.bin
5900_5920-cmw710-system-r2422p01.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to target slot.
Decompressing file 5900_5920-cmw710-boot-r2422p01.bin to flash:/5900_5920-cmw710-boot-r2422p01.b in……………………Done.
Decompressing file 5900_5920-cmw710-system-r2422p01.bin to flash:/5900_5920-cmw710-system-r2422p01.bin……………………………………………………………………………………………………………………………Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 1.

6. Checks :
<HP>display boot-loader
Software images on slot 1:
Current software images:
flash:/5900_5920-cmw710-boot-r2311p05.bin
flash:/5900_5920-cmw710-system-r2311p05.bin
Main startup software images:
flash:/5900_5920-cmw710-boot-r2422p01.bin
flash:/5900_5920-cmw710-system-r2422p01.bin
Backup startup software images:
None

7. Finally :
<HP>reboot
Start to check configuration with next startup configuration file, please wait.……..DONE!
Current configuration may be lost after the reboot, save current configuration? [Y/N]:y

Saved the current configuration to mainboard device successfully.
This command will reboot the device. Continue? [Y/N]:y
Now rebooting, please wait…

8. When Switch is rebooted, Confirm Boot Loader is running the new image & old image is backed up :
<HP>display boot-loader
Software images on slot 1:
Current software images:
flash:/5900_5920-cmw710-boot-r2422p01.bin
flash:/5900_5920-cmw710-system-r2422p01.bin
Main startup software images:
flash:/5900_5920-cmw710-boot-r2422p01.bin
flash:/5900_5920-cmw710-system-r2422p01.bin
Backup startup software images:
flash:/5900_5920-cmw710-boot-r2311p05.bin
flash:/5900_5920-cmw710-system-r2311p05.bin

Summary Commands :

<HP>cd slot1#flash:/
<HP>dir usba0:/
<HP>display boot-loader
<HP>Copy usba0:/5900_5920-cmw710-packet-capture-r2422p01.bin to flash:/5900_5920-cmw710-packet-capture-r2422p01.bin
<HP>Copy usba0:/5900_5920-CMW710-R2422P01.ipe to flash:/5900_5920-CMW710-R2422P01.ipe
<HP>boot-loader file boot flash:/5900_5920-cmw710-boot-r2311p05.bin system flash:/5900_5920-cmw710-system-r2311p05.bin slot 1 backup
<HP>boot-loader file flash:/5900_5920-CMW710-R2422P01.ipe slot 1 main
<HP>display boot-loader
<HP>reboot

HP 5900 JC772A “Airflow direction is not preferred” Setting

HI, I’m seeing the below errors on a IRF stack of 5900AF switches

The switch is rack ports front power supply rear.

The DC advise that the power supplys suck are in (wrong direction) but the fans blow out the back.

[Master01]dis log | inc Oct
%Oct 20 03:40:37:565 2014 Master01 SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.3.10-User=admin; Command is display ntp-service status
%Oct 20 03:40:55:142 2014 Master01 DEV/1/FAN_DIRECTION_NOT_PREFERRED: -Slot=2; Fan 1 airflow direction is not preferred on slot 2, please check it.
%Oct 20 03:40:55:144 2014 Master01 DEV/1/FAN_DIRECTION_NOT_PREFERRED: -Slot=2; Fan 2 airflow direction is not preferred on slot 2, please check it.
%Oct 20 03:40:58:357 2014 Master01 SHELL/6/SHELL_CMD: -Line=vty0-IPAddr=192.168.3.10-User=admin; Command is dis log
%Oct 20 03:41:16:853 2014 Master01 DEV/1/FAN_DIRECTION_NOT_PREFERRED: Fan 1 airflow direction is not preferred on slot 1, please check it.
%Oct 20 03:41:16:853 2014 Master01 DEV/1/FAN_DIRECTION_NOT_PREFERRED: Fan 2 airflow direction is not preferred on slot 1, please check it.

[Master01]dis device manuinfo
 Slot 1
DEVICE_NAME          : 5900AF-48XG-4QSFP+ JC772A
DEVICE_SERIAL_NUMBER : XXXXXXXXX
MAC_ADDRESS          : 4431-922B-88B3
MANUFACTURING_DATE   : 2013-11-20
VENDOR_NAME          : HP
Fan 1
DEVICE_NAME          : HP A58x0AF frt(ports)-bck(pwr) Fan Tray JC683A
DEVICE_SERIAL_NUMBER : CN47FDF1WG
MANUFACTURING_DATE   : 2014-07-19
VENDOR_NAME          : HP
Fan 2
DEVICE_NAME          : HP A58x0AF frt(ports)-bck(pwr) Fan Tray JC683A
DEVICE_SERIAL_NUMBER : CN47FDF1T6
MANUFACTURING_DATE   : 2014-07-19
VENDOR_NAME          : HP

[Master01]dis environment
 Slot 1
System temperature information (degree centigrade):
-------------------------------------------------------------------------------
Sensor    Temperature  LowerLimit  WarningLimit  AlarmLimit ShutdownLimit
hotspot 1      40           0            50          55           NA
hotspot 2      38           0            58          63           NA
 Slot 2
System temperature information (degree centigrade):
-------------------------------------------------------------------------------
Sensor    Temperature  LowerLimit  WarningLimit  AlarmLimit ShutdownLimit
hotspot 1      41           0            50          55           NA
hotspot 2      40           0            58          63           NA



[Master01]dis fan
 Slot 1
      FAN    1
      State    : FanDirectionFault
      Wind Direction    :Port-to-Power
      Prefer Wind Direction    :Power-to-Port
      FAN    2
      State    : FanDirectionFault
      Wind Direction    :Port-to-Power
      Prefer Wind Direction    :Power-to-Port
 Slot 2
      FAN    1
      State    : FanDirectionFault
      Wind Direction    :Port-to-Power
      Prefer Wind Direction    :Power-to-Port
      FAN    2
      State    : FanDirectionFault
      Wind Direction    :Port-to-Power
      Prefer Wind Direction    :Power-to-Port


The Fix :

Turned out to just be a preferred setting.

[Master01]fan prefer-direction slot 1 port-to-power
[Master01]fan prefer-direction slot 2 port-to-power

[Master01]dis log | inc recovered
%Oct 20 06:00:45:653 2014 Master01 DEV/5/FAN_RECOVERED: Fan 1 recovered.
%Oct 20 06:00:45:655 2014 Master01 DEV/5/FAN_RECOVERED: Fan 2 recovered.
%Oct 20 06:01:00:791 2014 Master01 DEV/5/FAN_RECOVERED: -Slot=2; Fan 1 recovered.
%Oct 20 06:01:00:793 2014 Master01 DEV/5/FAN_RECOVERED: -Slot=2; Fan 2 recovered.

[Master01]dis fan
 Slot 1
      FAN    1
      State    : Normal
      Wind Direction    :Port-to-Power
      Prefer Wind Direction    :Port-to-Power
      FAN    2
      State    : Normal
      Wind Direction    :Port-to-Power
      Prefer Wind Direction    :Port-to-Power
 Slot 2
      FAN    1
      State    : Normal
      Wind Direction    :Port-to-Power
      Prefer Wind Direction    :Port-to-Power
      FAN    2
      State    : Normal
      Wind Direction    :Port-to-Power
      Prefer Wind Direction    :Port-to-Power

HPE 5900AF Switch Series – How to Upgrade the Software in an IRF Configuration

Environment : HP 5900AF switches configured in an IRF configuration.

This article discusses how to upgrade from Version 7.1.035, Release 2209 to Version 7.1.045,
Release 2307. TFTP is used to transfer the binary file to the switch.

In the following example, the 5900AF switches are configured for IRF. The steps for upgrading the
firmware for both switches follow:

***** Copy file from TFTP server to switch *****
tftp 172.16.20.220 get 5900_5920-CMW710-R2307.ipe

***** Configure the boot loader to use new file *****
boot-loader file flash:/5900_5920-CMW710-R2307.ipe slot 1 main

***** Verify boot loader configuration *****
display boot-loader

***** Save configuration *****
save force

***** Reboot *****
reboot

—– Both boxes reboot ——-
***** Verify the new version after reboot *****
display version

***** General verification after reboot *****
display device
display irf
display irf topology

Upgrading HP Procurve firmware via USB flash drive

The ProCurve 5400zl series have a USB port on them that you can use to transfer files, in addition to TFTP and SCP/SFTP. Since I had a few of these to upgrade and they were in a lab environment (e.g. not connected to any “real” networks), I didn’t want to bother with setting up a TFTP server. The upgrade process is pretty straightforward and is similar to doing an upgrade via TFTP.

HP software (“firmware”) updates do not require that you have a valid login or service contract, unlike Cisco. I grabbed the latest version (at the time of writing), which is K.13.45 (be sure to read the Release Notes that accompany each release as well, prior to performing an upgrade). Save the .downloaded file to your USB flash drive and plug the flash drive into the switch.

To check what version of the software is currently running, issue the “show version” command:

SW1# show version
Image stamp:    /sw/code/build/btm(t3a)
                Aug  4 2008 15:08:24
                K.13.25
                93
Boot Image:     Primary

We can see that we’re running version K.13.25 and that we booted from the primary flash. We can see the current contents of flash, as well as our USB drive:

SW1# show flash
Image           Size(Bytes)   Date   Version
-----           ----------  -------- -------
Primary Image   : 7442476   08/04/08 K.13.25
Secondary Image : 6782942   12/07/07 K.12.57
Boot Rom Version: K.12.12
Default Boot    : Primary

SW1# dir

Listing Directory /ufa0:
-rwxrwxAwx  1 0       0          7442476 Nov  3  2008 K_13_25.SWI
-rwxrwxAwx  1 0       0          7494786 Oct 30  2008 K_13_45.SWI
SW1#

Because I’ve been running K.13.25 and it’s been stable, I’m going to copy it to secondary flash and then overwrite the primary with the new software. We’ll then reboot the switch with the new software (keeping the previous version in secondary as a “backup” in case anything goes wrong).

SW1# copy flash flash secondary

This command isn’t real intuitive (and it takes a while as well), but here we’re basically copying from flash, to flash, with the secondary as our destination. In this case, the contents of the primary flash will be copied to the secondary. “copy flash flash primary” would copy the contents of the secondary into the primary. Let’s verify what we have now:

SW1# show flash
Image           Size(Bytes)   Date   Version
-----           ----------  -------- -------
Primary Image   : 7442476   08/04/08 K.13.25
Secondary Image : 7442476   08/04/08 K.13.25
Boot Rom Version: K.12.12
Default Boot    : Primary

We can see that the contents of the primary have now been copied to the secondary as well. Let’s copy the K_13_45.SWI image from the USB drive to primary flash:

SW1# copy usb flash K_13_45.SWI primary
The Primary OS Image will be deleted, continue [y/n]?  y

After a moment, we’ll see this message:

Validating and Writing System Software to the Filesystem ...

When the copy has completed, we need to reload the switch with the new software:

SW1# boot system flash primary
System will be rebooted from primary image. Do you want to continue [y/n]?  y

The switch will take a minute to reboot (I won’t bother pasting the complete bootup process) and then we can, again, use “show version” to verify that we’re now running the latest software:

SW1# show version
Image stamp:    /sw/code/build/btm(t3a)
                Oct 17 2008 20:03:02
                K.13.45
                706
Boot Image:     Primary

See, wasn’t that easy!? We’ve successfully upgraded the firmware, and we’ve also kept a backup copy of the previous software in case things go badly. If that happens, just issue the “boot system flash secondary” command to reload the switch with the previous software.

This “upgrade via USB” method can come in handy at times, e.g. when the switch is in a lab and you don’t have a server handy to load the files from. For the switches in my production network, I would use SFTP to ugprade them instead of having to visit each switch individually to plug in and remove the USB drive. Yes, you can SFTP to the switch and upload a new version of firmware. It rocks. =)

Firmware Upgrade in HP 5900 Switch Series

1. To see your flash drive storage in switch from user view:

2. Enable the ftp server and upload the downloaded file to the FTP server of the switch:

login to ftp server and upload the downloaded zip extracted  fw file:

5900_5920-CMW710-R2208P01.ipe

This ipe file contains the system and boot image of the new version. You can also upgrade from the .bin file. Check that your file is uploaded :

2. To see the current version of FW image is installed:

3. Set the current image as backup system for backup boot option:

You need to know how many slot you have. For my case, i have only slot number 1. If you have multiple slot then you need to repeat the step for that specific slot given by slot number. Use “display version” to get the slot number.

4. Set the downloaded image .ipe file as the main startup image:

5. Now check that your main software package should now point to the new version and backup should point to the old one:

6. In order to install the main image to the current one, we need to reboot the system:

The command will ask you to save the current config, so save it please if you want to keep the current info.

7. The reboot will take some time to come up the OS. To make sure your upgrade is successful, run the command from user view:

Also check the version of the software:

HP 5900AF IRF INITIAL SETUP & CONFIGURATION

<HP>sys
[HP]sysname Master01

Next we configure VLAN interface 1 for management access and configure SSH. This must also be completed in ‘system-view’ as with most configuration changes.

[Master01] interface vlan-interface 1
[Master01-Vlan-interface1] ip address 192.168.17.20 255.255.255.0
[Master01-Vlan-interface1] quit
[Master01] ssh server enable
[Master01] public-key local create rsa (After issuing this command you may enter modulus value or leave the default)
[Master01] user-interface vty 0 15
[Master01-ui-vty0-15] authentication-mode scheme
[Master01-ui-vty0-15] protocol inbound ssh
[Master01-ui-vty0-15] quit
[Master01] local-user administrator (create user account ‘administrator’)
[Master01-luser-administrator] password simple admin (assign password ‘admin’)
[Master01-luser-administrator] service-type ssh
[Master01-luser-administrator] authorization-attribute user-role network-admin (assign Network Admin privileges)
[Master01-luser-administrator] quit
[Master01] snmp comm read public
[Master01] snmp comm write private
[Master01] snmp sys-info version all
[Master01] ip route 0.0.0.0 0.0.0.0 192.168.17.254 (default gateway)
[Master01] quit
<Master01> save

Now that the basic switch configuration is complete we can start on setting up IRF for the two switches. The last 4 Ports must be used to form an IRF and assigned to the IRF group. Ten-gigabit ports 45-48 on both switches for the IRF group.

[Master01] irf member 1 priority 10
[Master01] int ten1/0/45
[Master01-Ten-GigabitEthernet1/0/45] shut
[Master01-Ten-GigabitEthernet1/0/45] int ten1/0/46
[Master01-Ten-GigabitEthernet1/0/46] shut
[Master01-Ten-GigabitEthernet1/0/46] int ten1/0/47
[Master01-Ten-GigabitEthernet1/0/47] shut
[Master01-Ten-GigabitEthernet1/0/47] int ten1/0/48
[Master01-Ten-GigabitEthernet1/0/48] shut
[Master01-Ten-GigabitEthernet1/0/48] quit
[Master01] irf-port 1/2
[Master01-irf-port1/2] port group interface ten1/0/45
[Master01-irf-port1/2] port group interface ten1/0/46
[Master01-irf-port1/2] port group interface ten1/0/47
[Master01-irf-port1/2] port group interface ten1/0/48

After adding the interfaces to the IRF port group, we must do the same on the second switch along with changing the member number.

Second switch only :

<HP>sys
[HP] irf member 1 renumber 2
[HP] quit
<HP> save
<HP> reboot

after rebooting…

[HP] int ten2/0/45
[HP-Ten-GigabitEthernet2/0/45] shut
[HP-Ten-GigabitEthernet2/0/45] int ten2/0/46
[HP-Ten-GigabitEthernet2/0/46] shut
[HP-Ten-GigabitEthernet2/0/46] int ten2/0/47
[HP-Ten-GigabitEthernet2/0/47] shut
[HP-Ten-GigabitEthernet2/0/48] int ten2/0/48
[HP-Ten-GigabitEthernet2/0/48] shut
[HP-Ten-GigabitEthernet2/0/48] quit
[HP] irf-port 2/1
[HP-irf-port2/1] port group interface ten2/0/45
[HP-irf-port2/1] port group interface ten2/0/46
[HP-irf-port2/1] port group interface ten2/0/47
[HP-irf-port2/1] port group interface ten2/0/48

now bring the interfaces back up and activate IRF… Leave int 2/0/45/46 shutdown as we are not using these interfaces for the IRF even thou they are assigned to the group.

[HP-irf-port2/1] quit
[HP] int ten2/0/47
[HP-Ten-GigabitEthernet2/0/47] undo shut
[HP-Ten-GigabitEthernet2/0/47] int ten2/0/48
[HP-Ten-GigabitEthernet2/0/48] undo shut
[HP-Ten-GigabitEthernet2/0/48] quit
[HP] irf-port-configuration active

Now we return to the primary switch and complete setup…

[Master01] int ten1/0/45
[Master01-Ten-GigabitEthernet1/0/47] undo shut
[Master01-Ten-GigabitEthernet1/0/47] int ten1/0/48
[Master01-Ten-GigabitEthernet1/0/48] undo shut
[Master01-Ten-GigabitEthernet1/0/48] quit
[Master01] irf-port-configuration active

Following this, the secondary switch will reboot and activate the IRF configuration. The configuration should be saved ([Master01] save) as long as there are no issues. We can now check the status of both IRF member switches.

irf console

Summary Configuration :

HP 5900 Initial Setup :

system-view
sysname W4ETSETRANSSW01-2
vlan 11
description MGMT
quit
ssh server enable
public-key local create rsa
Y
user-interface vty 0 15
authentication-mode scheme
protocol inbound ssh
quit
local-user admin
password simple h0gw4rt
service-type ssh
authorization-attribute user-role network-admin
quit
save

IRF Initial Setup : Add Interface to IRF – 4 last Interface must be part of the IRF Group

‘
SWITCH 1 :

irf member 1 priority 10
int ten1/0/45
shut
int ten1/0/46
shut
int ten1/0/47
shut
int ten1/0/48
shut
quit

irf-port 1/2
port group interface ten1/0/45
port group interface ten1/0/46
port group interface ten1/0/47
port group interface ten1/0/48

SWITCH 2 :

After adding the interfaces to the IRF port group, we must do the same on the
second switch along with changing the member number.

‘
Renumbering Ports :

sys
irf member 1 renumber 2
Y
quit
save
Y

Y

reboot
Y

‘
IRF Initial Setup : Add Interface to IRF

system-view
int ten2/0/45
shut
int ten2/0/46
shut
int ten2/0/47
shut
int ten2/0/48
shut
quit

irf-port 2/1
port group interface ten2/0/45
port group interface ten2/0/46
port group interface ten2/0/47
port group interface ten2/0/48

‘
now bring the interfaces back up and activate IRF…

error : (undo shutdown) Bind all interfaces in the same group to IRF/PEX ports or cancel the bindings on all of them.

This is why we have added all 4 interfaces to IRF group as above and only using 2/0/47/48 ports and have left 2/0/45/46 shutdown. The port 2/0/45/46 will remain redundant and will be unusable as access port as these ports are part of the IRF group.

quit
int ten2/0/47
undo shut
int ten2/0/48
undo shut
quit
irf-port-configuration active

‘
SWITCH 1 :

sys
int ten1/0/47
undo shut
int ten1/0/48
undo shut
quit
irf-port-configuration active

H3C 5800 IRF Configuration

Intelligent Resilient Framework (IRF) is a software virtualization technology developed by H3C. IRF combines multiple physical devices into a logical device. IRF 2.0 is a common virtualization technology that combines multiple devices into a virtual device.  It allows one to aggregate 2 or more switches into a single switching and routing system also known as a “virtual switch”. IRF is available on many of the HPN A-Series switches.

• Load balancing, aggregation and redundancy at all levels and of all functions: Link, L2 and L3 Forwarding, Management and Security.
• Simplified LAN design: by aggregating switches at the core and distribution layer, the combination of MSTP and VRRP, with all the complexity it implies in design, implementation and maintenance, is no longer required to achieve load balancing and resiliency.

Switch A

system-view
irf member 1 pri 32

No reboot required

Switch B

Switch A – Create IRF Port 2 on Switch A

interface ten-gigabitethernet 1/0/xx
shutdown
interface ten-gigabitethernet 1/0/xx
shutdown
irf-port 1/2
port group interface ten-gigabitethernet 1/0/xx
port group interface ten-gigabitethernet 1/0/xx
quit
interface ten-gigabitethernet 1/0/xx
undo shutdown
interface ten-gigabitethernet 1/0/xx
undo shutdown
save 

interface ten-gigabitethernet 2/0/xx
shutdown
interface ten-gigabitethernet 2/0/xx
shutdown
irf-port 2/1
port group interface ten-gigabitethernet 2/0/xx
port group interface ten-gigabitethernet 2/0/xx
quit
interface ten-gigabitethernet 2/0/xx
undo shutdown
interface ten-gigabitethernet 2/0/xx
undo shutdown
irf-port-configuration active
save

ACTIVATE IRF CONFIGURATION

Switch A
quit
irf-port-configuration active

HP Link Aggregation

Link aggregation is known as Trunking, Bridge Aggregation and Port Channel Configuration. All 3 mean the same thing, use a group of ports to provide load balancing, link resilience and maximize bandwidth.

We will go through configuring each series of switch, then setup to use the LACP protocol and the finally allow VLANs over the links.

‘
Interface Bridge Port-Channel :

interface Bridge-Aggregation 11
description LACP to W4ETSEACCSW02
port link-type trunk
port trunk permit vlan all
link-aggregation mode dynamic
stp loop-protection
mad enable
!

Interface Port-Channel Bind to Bridge :

interface Ten-GigabitEthernet1/0/46
port link-mode bridge
description Uplink to ** UKBILLMCFW3**
port link-type trunk
port trunk permit vlan all
port link-aggregation group 11
!
interface Ten-GigabitEthernet2/0/46
port link-mode bridge
description Uplink to ** UKBILLMCFW4**
port link-type trunk
port trunk permit vlan all
port link-aggregation group 11

‘
To show our link aggregation information :

display link-aggregation summary
Verifying Spanning-Tree :

displ stp brief

Creating an HP IRF (Intelligent Resilient Framework) Networking stack between 2 switches

Intelligent Resilient Framework (IRF) is a software virtualization technology developed by H3C. IRF combines multiple physical devices into a logical device. IRF 2.0 is a common virtualization technology that combines multiple devices into a virtual device.  It allows one to aggregate 2 or more switches into a single switching and routing system also known as a “virtual switch”. IRF is available on many of the HPN A-Series switches.

• Load balancing, aggregation and redundancy at all levels and of all functions: Link, L2 and L3 Forwarding, Management and Security.
• Simplified LAN design: by aggregating switches at the core and distribution layer, the combination of MSTP and VRRP, with all the complexity it implies in design, implementation and maintenance, is no longer required to achieve load balancing and resiliency.

A short checklist for creating a IRF stack on 2 HP switches. I executed this on 2 HP A3600 EI switches:

1. Login onto the switch using the console port
2. sys (Enter system view)
3. show version (Ensure that both switches are running the same software version)
4. reset saved-configuration (Reset the config)
5. irf member 1 renumber 1 (Assign an IRF member number to the first switch)
6. irf member 1 renumber 2 (Assign an IRF member number to the second switch)
7. quit (Quit to user view)
8. save (Save the config)
9. reboot (Reboot the switches)
10. irf mac-address persistent always (Enable MAC address persistance)
11. irf member 1 priority 32 (Set the highest prio on the first member/switch)
12. irf member 2 priority 30 (Set the second highest prio on the second member/switch)
13. int GigabitEthernet 1/0/51
14. shut
15. int GigabitEthernet 1/0/52
16. shut
17. int GigabitEhternet 2/0/51
18. shut
19. int GigabitEthernet 2/0/52
20. shut (shutdown all interfaces you want to use for IRF on both switches)
21. irf port 1/1 (Create IRF port 1/1 on the first member)
22. port group interface GigabitEthernet 1/0/51 (add the switch port to the IRF port)
23. quit
24. irf port 1/2 (Create IRF port 1/2 on the first member)
25. port group interface GigabitEthernet 1/0/52 (add the switch port to the IRF port)
26. quit
27. irf port 2/1 (Create IRF port 2/1 on the second member)
28. port group interface GigabitEthernet 2/0/51 (add the switch port to the IRF port)
29. quit
30. irf port 2/2 (Create IRF port 2/2 on the second member)
31. port group interface GigabitEthernet 2/0/52 (add the switch port to the IRF port)
32. quit
33. save (Save config)
34. interface GigabitEthernet 1/0/51
35. undo shut
36. interface GigabitEthernet 1/0/52
37. undo shut
38. interface GigabitEthernet 2/0/51
39. undo shut
40. interface GigabitEthernet 2/0/52
41. undo shut (enable all interfaces you want to use for IRF on both switches)
42. irf-port-configuration active (Activate the IRF config on BOTH switches)
43. Now connect your fiber CROSSWISE, so 1/0/51 to 2/0/52 and 1/0/52 to 2/0/51
44. ATTENTION: The second IRF member will reboot! Wait for it to get back up. You will see the switches negotiate for about 30 seconds before the IRF becomes active.
45. If all works well;
46. quit
47. save
48. reboot
49. disp irf (Display the IRF setup)
50. disp irf topology (Display the IRF Topology)
51. Both irf port should be up. If one is DOWN or DIS(abled), something went wrong.
52. Check the IRF prio of the second member. It should be 30.

Summary Configuration :

irf domain 60
irf mac-address persistent timer
irf auto-update enable
undo irf link-delay
!
irf member 1 renumber 1
irf member 1 renumber 2
quit
save
reboot
!
irf mac-address persistent always
irf member 1 priority 32
irf member 2 priority 30
!
interface Ten-GigabitEthernet1/0/47
description IRF Link to ** (2/0/47) **
shut
!
interface Ten-GigabitEthernet1/0/48
description IRF Link to ** (2/0/48) **
shut
!

interface Ten-GigabitEthernet2/0/47
description IRF Link to ** (1/0/47) **
shut
!
interface Ten-GigabitEthernet2/0/48
description IRF Link to ** (1/0/48) **
shut
!
irf-port 1/2
port group interface Ten-GigabitEthernet1/0/47 mode enhanced
port group interface Ten-GigabitEthernet1/0/48 mode enhanced
quit
!
irf-port 2/1
port group interface Ten-GigabitEthernet2/0/47 mode enhanced
port group interface Ten-GigabitEthernet2/0/48 mode enhanced
quit
!
save
!
interface Ten-GigabitEthernet1/0/47
undo shut
!
interface Ten-GigabitEthernet1/0/48
undo shut
!
interface Ten-GigabitEthernet2/0/47
undo shut
!
interface Ten-GigabitEthernet2/0/48
undo shut
!
irf-port-configuration active
quit
save
reboot

Troubleshooting :

disp irf (Display the IRF setup)
disp irf topology (Display the IRF Topology)

Both irf port should be up. If one is DOWN or DIS(abled), something went wrong.
Check the IRF priority of the second member. It should be 30.