Download AMF 110 Specifications

ISSU Introduction
Use the issu boot command to complete the automatic phase of the ISSU operation.
Example
To upgrade a system with a release file in the Flash, SBx81CFC960-5.4.5-1.2.rel, use the
command:
awplus# issu boot SBx81CFC960-5.4.5-1.2
Initiating the ISSU Manual Phase
In order to complete the ISSU process all the LIFs must be rebooted. You use the reboot
card command to successively reboot each line card in your switch.
Example
To reboot the line card in slot 1 of chassis 2, use the command:
awplus> enable
awplus# reboot card 2.1
reboot card 2.1 system? (y/n):
y
If the specified card does not exist in the chassis, the command is rejected.
Errors and Recovery
If an error occurs during the ISSU process (such as a CFC failing to rejoin the chassis, or the
Active CFC leaving the stack) the ISSU process will halt, and one of two conditions can
result:
■
If the ISSU process fails before the new active master CFC is running the new release,
then the boot system configuration is reset, and the old release reverts to being the
primary release. In effect, the stack returns to its pre ISSU condition.
■
If the new Active CFC is running the new release, the new release becomes the
primary release
Either situation requires manual intervention by rebooting all stack members that are not
running the same release as the stack Active CFC.
If the ISSU process aborts, the reason can be viewed by displaying the show issu
command. You can use this show output and the logs produced to help determine the
cause of the failure. The most common failure is likely to be due to the node rejoin time
expiring. This could be because the configuration takes too long to replay, and the CFC
cannot rejoin the stack before the rejoin timer expires. If this happens a solution might be
to increase the value of the node rejoin timer.
Example
To display the ISSU state, use the command:
awplus# show issu
88
New and Enhanced Features in AlliedWare Plus 5.4.4 Major and Minor Versions