Specifications

Powering On and Initializing XSR Software
3-2 Software Configuration
• ETH 10/100 LEDs turn ON and OFF a few times during initialization as the XSR proceeds
from bootrom to power up diagnostics to software image, then they remain ON or OFF
depending on the LAN type.
• ETHERNET Activity LEDs blink when frames pass on the LAN.
• Console Activity LED is OFF until the CLI comes up. Then it blinks ON/OFF during
console keyboard input or output.
• NIM LEDs are OFF until the CLI comes up. Then they are turned ON if a supported card is
present (T1/E1 or Serial), and the card passes the power-up diagnostics test.
3. XSR software initializes in two phases. A cold start (including power cycling) is marked by
diagnostic and router software phases. A warm start skips the powerup diagnostics and boots
to router software. First-time startup is a cold start with the following sequence of events:
• Basic hardware initialization of the processor, memory, and other components occurs.
• Bootrom Monitor mode is accessible now and can be entered by pressing a special key
combination within a 5-second interval. For more information, refer to “Bootrom Monitor
Mode Commands” on page 3-36.
• Power-up diagnostics test the following hardware blocks:
- RAM size is detected
- On-board Flash size is detected
- FastEthernet is checked
- Ethernet on motherboard is checked
- NIM cards 1 and 2 is checked
- Real-Time Clock are checked
- Front panel LEDs are set to reflect current status
• Diagnostics test results are saved for later use by system software.
• The software image in Flash memory is verified by checksum.
- If no valid image exists in
flash: or cflash:, Bootrom Monitor mode is acquired.
- If the default file (xsr1800.fls) is not found as specified in Bootrom mode, an FTP/TFTP
server as defined in network parameters of Bootrom mode is queried.
- If the image is not found remotely, initialization is suspended in Bootrom mode.
• A valid image in Flash memory, if present, is decompressed.
• The decompressed software image is loaded into RAM.
• Execution is passed to the software image.
• The operating system is started.
• The Flash startup configuration files (startup-config, private-config) become the running
configuration.
• All software modules are initialized. If an error occurs when processing startup-config, the
CLI will continue processing the file until the end. If the file contains more than one error,
Note: Optionally, you can create a boot-config file to identify the name of a firmware file from which
the XSR boots. Refer to the boot system command in the XSR CLI Reference Guide for more
information.