Understanding Avaya / Nortel AUR, AAUR, DAUR and LAUR features when replacing a failed unit in a stack

So lets describe what each of these acronyms stand for and then explain what they do when you replace a failed stack unit.

**NOTE** Depending on your switch model and software version not all of these features are available.  Please read the documentation for an understand of what features are supported on your platform.

AUR

 Auto Unit Replacement (or automatic unit replacement).

Function:  This feature is responsible for replacing the failed unit's configuration onto the replacement device.  The replacement device will automatically reset after AUR has copied the configuration.

AAUR

 Agent Auto Unit Replacement.

Function:  This feature is responsible for replacing the failed unit's image(software) onto the replacement device.  The replacement device will automatically reset after AAUR has copied the image (software).

DAUR

 Diagnostics Auto Unit Replacement.

Function:  This feature is responsible for replacing the failed unit's firmware(diagnostics) onto the replacement device.  The replacement device will automatically reset after DAUR has copied the  firmware(diagnostics).

LAUR

 Licensing Auto Unit Replacement.

Function:  This feature is not like the others, it actually builds a virtual license, based on the loaded license file and the MAC address of the stack.  The stack continues to use the virtual license file even if the base unit fails and is replaced.  "This means that you do not need to regenerate a new license file when you replace a failed base unit in a stack.




Actual Operation of these features

So lets walk through the replacement process.  Say we have a stack of 4x ERS4524GT switches and unit #4 fails.  Luckily we work in the perfect workplace and we have a spare ERS4524GT switch on the shelf, but we are unsure of what state the config is in or what software is actually running on the switch.  Not to worry we can replace the failed unit with no issues as its the same hardware type as the switch that failed.

Now the following steps would be.

1. Remove old switch from the stack.
2. Insert new switch into stack, connecting stacking cables, its best to leave the front ports unpactched at this stage and  do not power up the replacement unit.
3. Check the base switch on the replacement unit is off (we are replacing unit#4 remember)
4. Power on the replacement unit.
5. Device will boot up, DAUR on the stack will detect if the firmware(diagnostics) is the same in the replacement unit as is what is running on the stack.  If an upgrade is required DAUR will download the firmware(diagnostics) to the replacement unit and reboot that unit only.  If DAUR has determined no upgrade is required then nothing more will be performed by this feature.
6. Once DAUR has upgraded or determined no firmware(diagnostics) upgrade is required, AAUR will detect if the image(software) is the same in the replacement unit as is what is running on the stack.  If an upgrade is required AAUR will download the image(software) to the replacement unit and reboot that unit only.  If AAUR has determined no upgrade is required then nothing more will be performed by this feature.
7.  Once AAUR has upgraded or determined no image(software)upgrade is required, AUR will download the replacement configuration of the failed unit to the replacement unit and reboot that unit only.
8. Once the unit has has rebooted for the final time (which could have been 3x times!!) you can now connect all the front ports
9. Confirm stack operation with "show stack-info" and "show stack health" commands

 Hopefully if you are new to Avaya / Nortel stackable switches this guide has helped you somewhat.  


Please leave a comment if you have any questions or if you have found this guide to be useful.  I will attempt to get back to you in a timely manner.

Avaya ERS5000 6.2.7 software released 16JUL13

A new version of software for the Avaya ERS5000 (5500 and 5600) family has been released.

Please download the software from here or using the links below

File:

ers5000v6.2.7.0.zip , 6.2.x Enterprise Device Manager COM Plug-in for ERS5000 R6.2.7

File:

ers5xxx_627_webpost.sha512.sig , 6.2.x ERS 5000 Series SHA512 Checksum File Digital Signature

File:

ers5xxx_627_webpost.sha512 , 6.2.x ERS 5000 Series SHA512 Checksum File

File:

ers5xxx_627_webpost.md5.sig , 6.2.x ERS 5000 Series MD5 Checksum File Digital Signature

File:

ers5xxx_627_webpost.md5 , 6.2.x ERS 5000 Series MD5 Checksum File

File:

5xxx_627019s.img , 6.2.x ERS 5000 Series Secure Runtime Image Software

File:

5xxx_627018.img , 6.2.x ERS 5000 Series Standard Runtime Image Software

File:

5xxx_60018_diags.bin , 6.2.x ERS 5000 Series Diagnostic Image

Problems Resolved in This Release

SNMP Query kills the Management access of the switch (wi01079031)

ERS 5530 Port state is down, the port could not be recovered until a reboot of the switch (wi01066585)

L2 traffic not working correctly on ports 29-30 of a 5632 (wi00856971)

Bootp failure for MAC Imaging Server (wi01081777)

EDMGraphical statistics of Minimum/sec values were negative for a port (wi01047631)

Full Mesh SMLT connectivity issues whenthe portswere manually bounced (wi01077465)

"show autotopology nmm-table" was not recognizing ERS4850 (wi01083032)
IST-Cluster-Member unreachable inmanagementVLAN only, after Peer-Mac is cleared(wi01082418)

ERS 5632FD 6.2.5.0 Telnet session to the SMLT interface IP on an ERS 5632 switch/stack from within ERS 8600 abruptly drops (wi01087145)

SNMP walk on ERS5000 produced inconsistent results for the MIB object ipAddressifIndex (wi01082905)

Data Access Exception tIdt occurred on non-base unit (wi01112122)

Ghost APIPA IP address appeared when scanning via SNMP tools with IP routing enabled globally (wi01074372)

VLAN configuration was corrupted on one of NBU when VLANs are created/deleted multiple times and ARP traffic is running in background (wi01112129)

On ERS55xx when the UPS was switched from AC to battery, all PoE ports went down (wi01112133)

When IGMP Query is received on a VLAN with snooping disabled, the query is not flooded not getting flooded to all ports of the VLAN (wi01097626)

Avaya ERS5510-48T boot sequence after power on (software version 6.2.6.035)

The following output has been captured off the serial console port of an Avaya ERS5510-48T during its boot sequence after power on.

Device is running software version 6.2.6.035

Serial settings are: 9600 baud, 8 data bits, no parity and 1 stop bit (9600/8-N-1)

Booting...

Testing Memory...............................

Starting..

Ethernet Routing Switch 5510-48T

Hardware Rev :    4

CPU CLOCK :266000000
Resets: 19.
Initializing Flash..
Reading MAC Address..
MAC Address: MA-CA-DD-RE-SS-00
Initializing Switch CBs
PCI unit 0: Dev 0x5670, Rev 0x02, Chip BCM5670_A1, Driver BCM5670_A0
PCI unit 1: Dev 0x5690, Rev 0x03, Chip BCM5690_A2, Driver BCM5690_A0
PCI unit 2: Dev 0x5690, Rev 0x03, Chip BCM5690_A2, Driver BCM5690_A0
PCI unit 3: Dev 0x5690, Rev 0x03, Chip BCM5690_A2, Driver BCM5690_A0
PCI unit 4: Dev 0x5690, Rev 0x03, Chip BCM5690_A2, Driver BCM5690_A0
Attaching SOC unit 0... PCI device BCM5670_A1 attached as unit 0.
Attaching SOC unit 1... PCI device BCM5690_A2 attached as unit 1.
Attaching SOC unit 2... PCI device BCM5690_A2 attached as unit 2.
Attaching SOC unit 3... PCI device BCM5690_A2 attached as unit 3.
Attaching SOC unit 4... PCI device BCM5690_A2 attached as unit 4.

Diagnostic Version 6.0.0.15 Nov 14 2011, 10:09:06



Test 102  ROM  Config                - PASSED
Test 104  FANs                       - PASSED
Test 207  XGS SWITCH Registers       - PASSED
Test 208  FABRIC Registers           - PASSED
Test 211  PHYs Register              - PASSED
Test 212  Internal Loopback          - PASSED
 Press Esc to Enter Diag
Run Agent 1 Ver:6.2.6.035
Decompressing the image  done.
Target Name: tgt
User: target
usrNetDevNameGet: no network device
done
Code Segment 0x100000 -- 0x10a0fff protection=2

Initializing ......
Broadcom Command Monitor: Copyright (c) 1998-2008 Broadcom Corporation

Completing initialization...


         ###   ###            ###   ###   ###            ###   ###
        #####   ###          ###   #####   ###          ###   #####
       ### ###   ###        ###   ### ###   ###        ###   ### ###
      ###   ###   ###      ###   ###   ###   ###      ###   ###   ###
     ###     ###   ###    ###   ###     ###   ###    ###   ###     ###
    ###       ###   ###  ###   ###       ###   ###  ###   ###       ###
   ##########  ###   ######   ##########  ###   ######   ##########  ###
  ############  ###   ####   ############  ###   ####   ############  ###
 ###             ###   ##   ###             ###  ###   ###             ###
                                                ###
                                               ###


Enter Ctrl-Y to begin.

  ***************************************************************
  *** Ethernet Routing Switch 5510-48T                        ***
  *** Avaya                                                   ***
  *** Copyright (c) 1996-2010,  All Rights Reserved           ***
  *** BOSS 6.0 SSH                                            ***
  *** HW:06       FW:6.0.0.15  SW:v6.2.6.035                  ***
  ***************************************************************

Avaya ERS5510-24T boot sequence after power on (software version 6.2.6.035)

The following output has been captured off the serial console port of an Avaya ERS5510-24T during its boot sequence after power on.

Device is running software version 6.2.6.035

Serial settings are: 9600 baud, 8 data bits, no parity and 1 stop bit (9600/8-N-1)

Booting...

Testing Memory...............................

Starting..

Ethernet Routing Switch 5510-24T

Hardware Rev :    4

CPU CLOCK :266000000
Resets: 7.
Initializing Flash..
Reading MAC Address..
MAC Address: MA-CA-DD-RE-SS-00
Initializing Switch CBs
PCI unit 0: Dev 0x5670, Rev 0x02, Chip BCM5670_A1, Driver BCM5670_A0
PCI unit 1: Dev 0x5690, Rev 0x03, Chip BCM5690_A2, Driver BCM5690_A0
PCI unit 2: Dev 0x5690, Rev 0x03, Chip BCM5690_A2, Driver BCM5690_A0
Attaching SOC unit 0... PCI device BCM5670_A1 attached as unit 0.
Attaching SOC unit 1... PCI device BCM5690_A2 attached as unit 1.
Attaching SOC unit 2... PCI device BCM5690_A2 attached as unit 2.

Diagnostic Version 6.0.0.15 Nov 14 2011, 10:09:06



Test 102  ROM  Config                - PASSED
Test 104  FANs                       - PASSED
Test 207  XGS SWITCH Registers       - PASSED
Test 208  FABRIC Registers           - PASSED
Test 211  PHYs Register              - PASSED
Test 212  Internal Loopback          - PASSED
 Press Esc to Enter Diag
Run Agent 1 Ver:6.2.6.035
Decompressing the image  done.
Target Name: tgt
User: target
usrNetDevNameGet: no network device
done
Code Segment 0x100000 -- 0x10a0fff protection=2

Initializing ......
Broadcom Command Monitor: Copyright (c) 1998-2008 Broadcom Corporation

Completing initialization...


         ###   ###            ###   ###   ###            ###   ###
        #####   ###          ###   #####   ###          ###   #####
       ### ###   ###        ###   ### ###   ###        ###   ### ###
      ###   ###   ###      ###   ###   ###   ###      ###   ###   ###
     ###     ###   ###    ###   ###     ###   ###    ###   ###     ###
    ###       ###   ###  ###   ###       ###   ###  ###   ###       ###
   ##########  ###   ######   ##########  ###   ######   ##########  ###
  ############  ###   ####   ############  ###   ####   ############  ###
 ###             ###   ##   ###             ###  ###   ###             ###
                                                ###
                                               ###


Enter Ctrl-Y to begin.

  ***************************************************************
  *** Ethernet Routing Switch 5510-24T                        ***
  *** Avaya                                                   ***
  *** Copyright (c) 1996-2010,  All Rights Reserved           ***
  *** BOSS 6.0 SSH                                            ***
  *** HW:34       FW:6.0.0.15  SW:v6.2.6.035                  ***
  ***************************************************************