Cisco BPX 8650, Installation And Configuration Manual

Page: 561 / 606

A-5
Cisco BPX 8600 Series Installation and Configuration
Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005
Appendix A Upgrade Information
Upgrade Protection from Release 9.3 to a Later Release
The Upgrade Protection feature introduced in 9.3 protects you against the effects of failing to turn off
statistics. In 9.3, statistics collection is automatically turned off by the system when you enter the loadrev
1 phase. You are now prevented from running loadrev/runrev during the time that statistics collection is
enabled. When you execute loadrev, the switch gives this message “Warning: Statistics collection will be
automatically disabled.”
In addition to statistics collected by Cisco WAN Manager, the local statistics collection state machines
are also disabled at this time.
Upgrade Protection applies only to a “graceful upgrade,” that is, an upgrade to a standby controller card.
There is no change to the “nongraceful upgrade” procedure.
This feature is operational only when upgrading from Release 9.3 to a later release. Upgrade from
Release 9.2 to 9.3 does not use this 9.3 feature. Upgrade Protection is used in intraversion upgrades, such
as an upgrade between 9.3.1 and 9.3.2
If you attempt to load an older release than the one currently running, you are warned that downgrades
are not supported. You may override this warning and continue at your own risk. This feature is meant
to warn you early in case an invalid release is inadvertently loaded.
If you need to see certain statistics at this phase of the upgrade, you are allowed to restart state machines
one at a time. However, it is your responsibility to disable all these machines before entering the runrev
phase.
Procedure
Before a software upgrade, investigate the following issues:
•
Recent software errors. Any nodes that continually log errors or have logged recent errors should be
reported to Cisco TAC.
•
Card errors. Cards that are logging self or background test failures or have a history of hardware
errors should be investigated by Cisco TAC.
• Nodes with less than 40% CPU idle time (20% in the case of PCCs). Such nodes are not usually
found within BPX/IGX/IPX networks. These nodes should be examined closely. If the idle time is
consistently low, you should contact the Cisco TAC.
•
Load model failures. These failures should be reported to the Cisco TAC. Software Release 8.4 and
higher use trunk-based loading and can show load model failures shortly after network topology
changes.
• Any trunks that are logging errors should either be fixed or configured not to pass management
traffic for the duration of the upgrade.
•
All alarms should be accounted for. The real purpose of this check is to ensure that there are no
alarms, such as bus failures, which requires special intervention before the upgrade.
The process of upgrading a network from one release of switch software to another involves the
following phases:
Step 1
Load the new software image into the switches of the network by using loadrev 1
Step 2
Upgrade the new image in standby controller cards (assuming graceful software upgrade) by using
upgrade . If you need to see certain statistics at this phase of the upgrade, you are allowed to restart state
machines one at a time. However, it is your responsibility to disable all these machines before entering
the runrev phase.