There are no commands specifically for DAUR; after AAUR is enabled or disabled, DAUR is
enabled or disabled.
After you enable AAUR on a stack, and you add another unit with a different software image,
the new unit fails to join the stack and enters in stand-alone mode. The new unit sends an
AAUR request to its UP-stream port neighbor. If it does not receive an answer, it sends the
request on its DOWN-stream port. The switch reboots after the image is properly
transferred.
Important:
If the unit is powered off while the diagnostic image is being programmed to the flash, the
diagnostic image is corrupted. The only way to recover is to download the diagnostic image
using the console serial port. At boot time, press “Shift + 3” to accede to the downloading
menu.
If you add a unit that has its base switch set to off to a unit that has the base switch set, the
non-base unit retrieves the image from the other unit.
The AAUR enabled/disabled state is ignored for the unit that is added to the stack under the
following conditions:
• If a unit with AAUR disabled is added to a stack that has AAUR enabled, then the image
transfer process starts.
• If a unit with AAUR enabled is added to a stack that has AAUR disabled, then there is no
image transfer.
After the diagnostic image version is updated, an AAUR check is performed. If the added unit
has the same agent image as the stack, the unit reboots. Otherwise, an AAUR is performed.
In the case where a unit with Release 5.0 or Release 5.1 software is added to a stack having
an agent image that exceeds 6M, the agent transfer is stopped.
You may encounter the following situations:
• A stack is running the Release 5.2 non_ssh software and 5.2 diagnostic image:
- If the agent image on the added unit is Release 5.0 or 5.1 and the diagnostic version
is also Release 5.0 or 5.1, then, because the Release 5.2 image size is less than
6M, AAUR starts the agent image transfer and then the unit reboots. After the reboot,
the unit has the new Release 5.2 image that supports DAUR and the 5.2 diagnostic
image is transferred. The unit reboots again and joins the stack.
- If the agent image on the added unit is Release 5.2_ssh software with the Release
5.2.0.1 diagnostic image, then, because both images support DAUR, the new added
unit does not join the stack . A diagnostic update is performed and, because the
agent images are different, an agent update is also performed, after which the switch
reboots. The switch joins the stack after reboot.
• A stack with Release 5.3 or newer and Release 5.3 diagnostic image:
- If the agent image on the added unit is Release 5.1 or 5.0 and the Release 5.1 or
5.0 diagnostic, then, because the 5.3 image size is greater than 6M, the AAUR
Diagnostic Auto Unit Replacement (DAUR)
Troubleshooting Avaya ERS 4000 Series April 2014 43
To Next Page
Loading...
