Cisco Cisco Packet Data Gateway (PDG) インストールガイド
System Power-up
▀ System Boot Process
▄ ASR 5500 Installation Guide
106
System Boot Process
The boot process is initiated after power is applied to the chassis.
Step 1
When power is first applied to the chassis, the MIO/UMIOs in slots 5 and 6 and all fan trays are the first to receive
power.
power.
Once the software is running, power is then quickly applied to the remaining cards in the system.
Important:
The fans in the fan trays initially rotate at medium speed until the first MIO completes its boot up. If
no MIO/UMIO boots successfully within a few minutes, the fan speed increases to 100%.
Step 2
During the startup process, each card performs a series of Power-On Self Tests (POSTs) to ensure that the hardware is
operational. These tests also verify that the card meets all license requirements to operate on this chassis.
operational. These tests also verify that the card meets all license requirements to operate on this chassis.
Step 3
If the MIO/UMIO in slot 5 successfully executes all POSTs, it becomes the active chassis management MIO/UMIO for
the system. The MIO/UMIO in slot 6 becomes the standby.
the system. The MIO/UMIO in slot 6 becomes the standby.
Important:
If the MIO/UMIO in slot 5 fails to boot, the MIO/UMIO in slot 6 automatically becomes the active
chassis management MIO.
Step 4
The active MIO/UMIO begins loading the operating system software image that is designated in the boot stack. The
boot stack entries are contained in the boot.sys file that resides on the MIO/UMIO's flash device.
boot stack entries are contained in the boot.sys file that resides on the MIO/UMIO's flash device.
The standby MIO/UMIO observes the active card's startup. If the file on the active card is loading normally, the standby
MIO/UMIO boots from the active card's image. If the active MIO/UMIO experiences a problem during this phase, the
standby card loads its software image, that is designated by its own boot stack entry in its boot.sys file, and takes control
of the system as the active card.
MIO/UMIO boots from the active card's image. If the active MIO/UMIO experiences a problem during this phase, the
standby card loads its software image, that is designated by its own boot stack entry in its boot.sys file, and takes control
of the system as the active card.
Step 5
After the software image is loaded into MIO RAM, the active card determines if other cards are installed in the chassis
by applying power to the other slots and signaling them. If the chassis slot contains a card, power is left on to that slot.
All empty slots are powered off.
by applying power to the other slots and signaling them. If the chassis slot contains a card, power is left on to that slot.
All empty slots are powered off.
Important:
If no MIO/UMIOs are installed in slots 5 and 6 or if they both fail to boot, other cards in the system
will not boot.
Step 6
When power is applied to the other installed cards, they each perform their own series of POSTs.
Important:
After successful completion of the POSTs, each of the data processing cards enter standby mode.
Installed DPC/UDPCs or DPC2/UDPC2s remain in standby mode until they are made active via configuration.
Step 7
After entering the standby mode, each of the DPC/UDPC or DPC2/UDPC2 control processors communicate with the
active chassis management MIO to receive the appropriate code.
active chassis management MIO to receive the appropriate code.
Step 8
Upon successful loading of the software image, the system loads a configuration file designated in the boot stack
(boot.sys file). If this is the first time the system is powered on and there is no configuration file, the active MIO/UMIO
invokes the system's Quick Setup Wizard. Use the Quick Setup Wizard to configure basic system parameters that enable
the system to communicate across the management network.
(boot.sys file). If this is the first time the system is powered on and there is no configuration file, the active MIO/UMIO
invokes the system's Quick Setup Wizard. Use the Quick Setup Wizard to configure basic system parameters that enable
the system to communicate across the management network.