Cisco PRP-1= Spezifikationen Seite 34

  • Herunterladen
  • Zu meinen Handbüchern hinzufügen
  • Drucken
  • Seite
    / 88
  • Inhaltsverzeichnis
  • LESEZEICHEN
  • Bewertet. / 5. Basierend auf Kundenbewertungen
Seitenansicht 33
34
OL-17436-01
Upgrading to the PRP
Upgrading the RP ROM Monitor Using Cisco IOS Release 12.0(24)S or Later, page 34
Upgrading the RP ROM Monitor Prior to Cisco IOS Release 12.0(24)S, page 35
Note The PRP-2 does not require an RP ROM monitor upgrade before Cisco IOS Software Release 12.0(30)S.
If you attempt this upgrade on a PRP-2 using a prior software release, you will receive the following
error message:
Error: Unknown Flash Device type!
GRP ROM monitor upgrade won't continue
Upgrading the RP ROM Monitor Using Cisco IOS Release 12.0(24)S or Later
New functionality was introduced in Cisco IOS Software Release 12.0(24)S that enables the secondary
RP to have its ROM monitor image upgraded while in standby mode, and does not require a reboot of
the router. In order for this to work, the router must already be running Cisco IOS Software Release
12.0(24)S or later.
In the following procedure, RP1 is initially the active RP and RP2 is the standby RP.
Step 1 After you enter the configuration to load the new Cisco IOS software image, reload the standby PRP
(RP2) using the hw-module standby reload command.
Step 2 Once the standby RP (RP2) is available again, use the upgrade rom-monitor slot sec-rp-slot command.
If the routine finds that an upgrade is necessary, the new code will begin to be loaded. When this
command is completed, reload the RP2 using the hw-module standby reload command.
Step 3 Switch over from the active PRP (RP1) to the standby PRP (RP2) using the redundancy
force-switchover command. Once RP2 becomes active, the line cards will be reloaded.
Step 4 Let the router return to full operation with Interior Gateway Protocol (IGP) and Exterior Gateway
Protocol (EGP) peers established (this may take a considerable amount of time, depending on the size
and complexity of the router configuration).
Step 5 Check the line card CPU utilization using the execute-on all show proc cpu | inc CPU command. If the
CPU utilization has stabilized at the normal running level, proceed with the next step; otherwise, wait
another five minutes and check again.
Step 6 Upgrade the Mbus-agent-rom using the upgrade mbus-agent-rom all command. Normal forwarding
operation of the line cards will not be affected during the upgrade. The line cards do not need to be
reloaded. If any error messages are displayed (see following example), repeat this step before contacting
Cisco TAC.
MBus agent ROM upgrade failed on slot 7 (rc=5)
MBus agent ROM upgrade failed on slot 8 (rc=6)
Step 7 Use the show version command. If there is an error message at the bottom of the output indicating that
a Fabric-downloader code upgrade is required, use the upgrade fabric-downloader all command.
Normal forwarding operation of the line cards will not be affected during the upgrade. The line cards do
not need to be reloaded. If any error messages are displayed (see following example), repeat this step
before contacting Cisco TAC.
Fabric-downloader upgrade failed on slot 7 (rc=5)
Fabric-downloader upgrade failed on slot 8 (rc=6)
Seitenansicht 33
1 2 ... 29 30 31 32 33 34 35 36 37 38 39 ... 87 88

Kommentare zu diesen Handbüchern

Keine Kommentare