Upgrading the Boot ROM or Minikernel

Contents

1Upgrading the Boot ROM or Minikernel
1.1Before You Begin
1.2Boot ROM Commands
1.3About the Standard Reboot Upgrade Procedure
1.4Upgrade Software Procedure
1.5Modular Upgrade (Patch) Instructions

2

Format Internal Devices, Install a New System Image, or Both

3

Enable Automatic Reload
3.1Connect a Console to the Console Port on Each Controller Card
3.2Set the auto-boot? Variable on the Active Controller Card
3.3Set the auto-boot? Variable on the Standby Controller Card
3.4Upgrade Operations

4

Reloading the System Manually
Copyright

© Ericsson AB 2009–2011. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
SmartEdge is a registered trademark of Telefonaktiebolaget LM Ericsson.
NetOp is a trademark of Telefonaktiebolaget LM Ericsson.

1   Upgrading the Boot ROM or Minikernel

Most of the tasks associated with configuring and maintaining the SmartEdge router involve using commands supported by the operating system. However, some tasks require that you use the boot ROM (also referred to as the boot loader) software installed on the controller cards in the SmartEdge router .

Note:  
In the following descriptions, the term controller card applies to the Cross-Connect Route Processor (XCRP4) Controller card, including the controller carrier card, unless otherwise noted.

The term controller carrier card refers to the controller functions on the carrier card within the SmartEdge™ 100 chassis; these functions are compatible with the XCRP4 Controller card. The term I/O carrier card refers to the traffic card functions on the carrier card; these functions are compatible with the similar functions that are implemented on the traffic card that are supported on all other SmartEdge routers.


Note:  
The messages in this document are displayed when you use a SmartEdge router with a controller and the minikernel version current at the time of publication. If you use a different controller or a different minikernel version, the messages you view may be different than the messages in this document.

1.1   Before You Begin

The boot ROM image contains system firmware that provides access to low-level functions used to manipulate system devices, view and modify boot parameter values, and control boot procedures. The SmartEdge router implements SmartFirmware, an ANSI C implementation of OpenFirmware (IEEE 1275-1994, Standard for Boot Firmware Initialization Configuration Firmware: Core Requirements and Practices) plus errata, recommend practices, and accepted proposals to configure system boot parameters and to boot the operating system software.

It is assumed that there is a Trivial File Transfer Protocol (TFTP) server that has the needed software image files on it, and that the server is configured and reachable by the SmartEdge router.

Note:  
For the IP address of the TFTP server and for the exact file names, contact your technical support representative.

Software image file names have the following formats:

The installation document provides the software image file names for the operating system releases that they cover. This document is available at https://ebusiness.ericsson.net.

1.2   Boot ROM Commands

Table 1 describes the boot ROM commands supported on the SmartEdge router.

Table 1    Boot ROM Commands

Syntax

Description

Argument Values

boot net filename


or


boot hd:a /flash/filename

Boots from a TFTP server or from /flash.

Name of the file to be booted.

bootsys

Loads and runs the software image.

None.

cd path

Changes the currently open device to the one specified by the path argument. The device also parses any optional arguments to configure the device.

path—Actual or relative device path. Entering .. specifies the parent of the current device.

dev path

Changes the currently open device to the one specified by the path argument. The device also parses any optional arguments to configure the device.

path—Actual or relative device path. Entering... specifies the parent of the current device.

devalias [name string]

Displays all device aliases, if no arguments specified; otherwise, creates a device alias called name with the value string.

name—Optional. Name of the device alias.


string—Optional. String to which the alias refers.

installsys

Invokes the BSD minikernel.

None.

load net filename


or


load hd:a /flash/filename

Loads an image from a TFTP server or from /flash.

Name of the file to be downloaded.

printenv [parameter]

Displays all parameter variables, their current values, and their default values if no argument is specified; otherwise, displays the specified parameter variable.

See Table 2.

probe-all

Probes the system for all devices and builds the device tree.

None.

reset

Resets the hardware and boots the system.

None.

set-default var

Sets the value of a parameter to the default value.

See Table 2.

set-defaults

Sets all parameter values back to their default values.

None.

setenv parameter value

Sets the value of a parameter to a specified value. All characters entered up to the end of the line (including spaces), are stored in NVRAM.

See Table 2.

show-devs

Displays all the devices in the device tree.

None.

sysinfo

Displays system information including router, chassis, memory, and environmental information.

None.

update-bootrom

Updates and runs the currently loaded boot ROM image.

None.

Table 2 lists the parameters used with these boot ROM commands: printenv, setenv, and set-default.

Table 2    Parameters Used with printenv, set-default, and setenv Boot ROM Commands

Syntax

Description

Values

auto-boot?

If true, runs the word in boot-command after the standard bootup process; otherwise, runs the Forth interpreter on the console and displays an ok prompt.

true or false; the default value is true.

auto-boot-timeout

Maximum amount of time, in milliseconds, that the autoboot process waits for a key press before times out. (This is not a standard OpenFirmware parameter.)

Integer; the default value is 5000.

boot-command

Command to boot the system if the auto-boot? value is true.

String; the default value is bootsys.

boot-device

Device to use to load the boot ROM image when the boot command is issued. The string is usually an alias to the actual device.

String; the default value is flash.

boot-file-ppc0

NetBSD file to load from the boot device when the boot command is issued.

String; the default value is /p01/netbsd.

boot-file-ppc1

vxWorks file to load from the boot device when the boot command is issued.

String; the default value is /p01/vxWorks.gz.

diag-device

Device to use to load the diagnostic image if the diag-switch? value is true when boot is issued.

String; the default value is net.

diag-file

Diagnostic file to load if the diag-switch? value is true when boot is issued.

String; the default value is diag.

diag-switch?

If true, turns on extended tests and displays more verbose output.

true or false; the default value is false.

fcode-debug

Ericsson internal use only; do not modify.

true or false; the default value is false.

gateway-ip-addr

IP address of the gateway router to the IP network on which the TFTP server is located.

String.

ignore-cfgfile

If true, the bootup configuration file is bypassed the first time the system is reloaded, after which the parameter is set to false. This parameter allows you to bypass the loading of a possibly corrupt configuration file. It is set from the ok prompt.

true or false; the default value is false.

input-device

Device path to use for the console input. The keyboard value is usually an alias to the actual input device determined in some machine-dependent manner.

String; the default value is keyboard.

inverse-video

If true, displays text on the console as black-on-white; otherwise, displays text on the console as white-on-black. (This is not a standard OpenFirmware parameter).

true or false; the default value is true.

ip-addr

IP address and network mask of the Ethernet management port on the active controller card in the SmartEdge router; format is A.B.C.D:E.F.G.H.

String.

little-endian

Ericsson internal use only; do not modify.

true or false; the default value is false.

load-base

Ericsson internal use only; do not modify.

0x05600000.

mac_addr

MAC address of the active controller card.

String.

nvramrc

Seven device aliases; Ericsson internal use only; do not modify.

String.

oem-banner

String to display when the banner command is issued, if the oem-banner? value is set to true.

String.

oem-banner?

If true, display the contents of the oem-banner value when the banner command is issued.

true or false; the default value is false.

oem-logo

Bitmap to display if the oem-logo? value is true. The contents can be machine-dependent.

Bitmap: 64 x 64 x 1 (512 bytes).

oem-logo?

If true, displays the bitmap in the oem-logo value in front of the banner when the banner command is issued; otherwise, a default logo (or no logo) displays.

true or false; the default value is false.

output-device

Name of the device to use for console. This is usually an alias to the actual device.

String; the default value is screen.

real-base

Ericsson internal use only; do not modify.

0x00000000.

real-mode?

Ericsson internal use only; do not modify.

true.

real-size

Ericsson internal use only; do not modify.

0x00080000.

screen-#columns

Number of columns desired for console output. If 0 is specified, the largest allowable number is used, depending on the font used.

Integer; the default value is 80.

screen-#rows

Number of rows desired for console output. If 0 is specified, the largest allowable number is used, depending on the font used.

Integer; the default value is 24.

secondary-diag?

If true, run secondary diagnostics at bootup. (This is not a standard OpenFirmware parameter.)

true or false; the default value is true.

server-ip-addr

IP address of the TFTP server.

String.

update-ofw?

Ericsson internal use only; do not modify.

false.

use-nvramc?

Ericsson internal use only; do not modify.

true.

user-auth

If true, prompts users for password authentication. If false, authentication is bypassed. Set this flag to false if password is forgotten or lost. If set to false, it is set to true the next time the device is rebooted.

true or false; the default value is true.

virt-base

Ericsson internal use only; do not modify.

Integer; the default value is -1.

virt-size

Ericsson internal use only; do not modify.

Integer; the default value is -1.

vx-config-flags

Ericsson internal use only; do not modify.

0x0.

vx-other

Ericsson internal use only; do not modify.

0x7a.

vx-target-name

Ericsson internal use only; do not modify.

String.

vx-host-name

Ericsson internal use only; do not modify.

String.

Note:  
Diagnostic syntax, diag-device, diag-file, and diag-switch?, have no effect on the power-on diagnostics (POD) nor are they affected by the POD.

1.3   About the Standard Reboot Upgrade Procedure

The standard reboot upgrade process replaces all components of the operating system. It terminates existing subscriber sessions. All traffic forwarding is interrupted for a minimum of several minutes.

1.4   Upgrade Software Procedure

This section includes instructions on upgrading the operating system image installed on your SmartEdge router to a newer release. It does not include patch upgrades. Patch upgrades and instructions on installing a system patch on your operating system are described in the Modular Upgrade (Patch) Instructions section.

To upgrade the operating system to a new release, perform in sequence the following procedures:

  1. Before You Begin
  2. Upgrade the Boot ROM Image
  3. Download the New Operating System Release Image
  4. Upgrade to the New Operating System Release Image
  5. Upgrade the Minikernel Image
  6. Upgrade the Traffic Card FPGAs
  7. Verify System Chassis State
  8. Verify System Routing

In addition to the operating system image stored on the local file system, each controller card contains a boot ROM image (also referred to as the boot loader image) and a minikernel image in its EEPROM.

Table 3 shows the commands that apply to standard reboot upgrades. For full descriptions of the commands, see the Command List.

Table 3    Standard Reboot Upgrade Tasks

Task

Root Command

Install an alternate release on the system.

release download

Manually erase an alternate system image.

release erase

Upgrade the system to use its alternate release.

release upgrade

Display release and installation information for the software images currently installed on the system.

show release

Display the current version of the software running on the system.

show version

Upgrade the boot ROM image in the EEPROM on the active controller card in a working system and reload it.

upgrade bootrom

Upgrade the minikernel image in the EEPROM on the active controller card in a working system and reload it.

upgrade minikernel

1.4.1   Before You Begin

To upgrade your system to a new release of the operating system, you need to determine the file name and version of the new software release image. You also need to know whether the new software release requires an upgrade to the boot ROM image or the minikernel image. For a table of the file names and versions required for the release, see the release notes for the release to which you are upgrading

  1. Determine the boot ROM, minikernel, and operating system versions that your system is currently running.

    In the following example of the show version command, the operating system version is SEOS-6.5.0.0.24-Release, the boot ROM version is Mips,rev2.0.2.44, and the minikernel version is 11.7.

[local]Redback>show version

Redback Networks SmartEdge OS Version SEOS-6.5.0.0.24-Release
Built by sysbuild@SWB-node01 Fri Oct 22 23:00:06 PDT 2010
Copyright (C) 1998-2010, Redback Networks Inc. All rights reserved.
System Bootstrap version is Mips,rev2.0.2.44
Installed minikernel version is 11.7
Router Up Time -   27 days, 20 hours 35 minutes 35 secs

If the boot ROM and minikernel versions do not match the versions required in the release notes, upgrade one or both of them as required. Upgrade the boot ROM image before you install the new software release image and the minikernel image after you install the software release image.

  1. As part of the upgrade, check the release notes to determine whether you also need to upgrade any traffic card field-programmable gate arrays (FPGAs).
  2. The SmartEdge router ships with the current operating system release installed in the active partition, either p01 or p02. Use the show release command to show which partition is active and which is the alternate, and shows the version of the operating system installed in each. The operating system in the active partition automatically loads when you power on the system.
  3. Enter the show ip route summary all-context command to display summary information for all IP routes in all contexts before upgrading. Routing configuration including static routes should be preserved during upgrades.

    The following example illustrates the show ip route summary all-context command

[local]Redback>show ip route summary all 

Total unicast routes summary in all contexts: 
Route Source            Tot-Routes     Act-Routes  Max Ever Reached

Connected                       21             21                21
IP Host                         13             13                13
Subscriber Address               5              5                 5
Subscriber Static                2              2                 2
Static                           3              3                 3
Ospf-InterArea                 125            125               126
Ospf-IntraArea                  37             33                37
Ospf-Ext-Type 2                  5              5                 6
IBGP                            91             45               279
Ldp                             30             30                30

1.4.2   Upgrade the Boot ROM Image

To determine the boot ROM and minikernel version you have, see the Before You Begin section.

To upgrade the boot ROM image, perform the following steps:

  1. Enter the following command in exec mode to upgrade to the new version of the boot ROM image:

    upgrade bootrom {ftp: | scp: | /md} url

    The following example uses FTP to download the of1267.bin file from a server in the lab domain.

[local]Redback#upgrade bootrom ftp://user-id:pwd@lab/dir/of1267.bin 

Double slashes (//directory) indicate an absolute path name to a directory on the remote server; a single slash (/directory) indicates a relative path name under the username account home directory

  1. Type y and press Enter when the system prompts you to continue with the following message:
This operation will cause the box to reload, do you want to continue?
  1. When the system prompts you to save the current configuration, type y to save the current configuration, or n to not save it, and press Enter.
  2. After the file transfer completes, the system should automatically reboot and reload. The reload process takes several minutes.
  3. When the reload is complete, verify that the system is using the new boot ROM image; enter the show version command in any mode.
  4. If your system has dual controller cards, wait a few minutes until the system has had a chance to synchronize its controller cards and then verify the redundancy state. The following example illustrates the show redundancy command:
[local]Redback>show redundancy 

---------------------------------
This XCRP is active
---------------------------------
STANDBY XCRP READY?: YES
VxWorks in sync?          : YES
Database in sync?         : YES
Software Release in sync? : YES
Firmware in sync?         : YES
Mate-to-Mate link up?     : YES

1.4.3   Download the New Operating System Release Image

To download the new release of the operating system image to the alternate partition on your system:

  1. Enter the release download command in exec mode. This command can take up to 20 minutes to complete, during which the CLI prompt becomes unavailable.

    Enter the release download command:

    release download {ftp: | scp:}//username[:passwd]@{ip-addr | hostname} //directory/filename.ext

    If you enter the hostname argument rather than the ip-addr argument, the SmartEdge router must be configured for Domain Name System (DNS) services.

    Double slashes (//directory) indicate an absolute path name to a directory on the remote server; a single slash (/directory) indicates a relative path name under the username account home directory.

    The following example illustrates the release download command:

[local]Redback#release download ftp://guest@10.1.1.1//images/
RELnew/SEOS-rel-new.tar.gz
  1. When prompted, enter y for yes to erase the existing alternate image, if any. Wait until the download finishes.
  2. When the download is complete, verify that the alternate partition has loaded the new operating system image; enter the show release command in any mode.

1.4.4   Upgrade to the New Operating System Release Image

Continue with the following steps to activate the new operating system release image that you downloaded in the preceding section:

  1. Enter the release upgrade command in exec mode to activate the new software image.

    The SmartEdge router reboots. Any active subscriber sessions are interrupted.

[local]Redback#release upgrade
  1. When you are prompted to reboot, verify that the operating system version in the prompt message is one you wish to run. Type y for yes to continue.
  2. When the system prompts you to save the current configuration, type y to save the current configuration, or n to not save it, and press Enter. If you enter y, but do not specify a file name for the configuration, the system saves the current configuration in the redback.cfg file.
  3. When the upgrade is complete and running the new operating system, verify that the system is using the new image; enter the show version command in any mode.
  4. If your system has dual controller cards, wait a few minutes until the system has had a chance to synchronize its controller cards and then verify the redundancy state. The following example illustrates the show redundancy command:
[local]Redback>show redundancy 
--------------------------------
This XCRP is active
---------------------------------
STANDBY XCRP READY?: YES
VxWorks in sync?: YES
Database in sync?: YES
Software Release in sync?: YES
Firmware in sync?: YES
Mate-to-Mate link up?: YES
  1. Do not upgrade the traffic card FPGAs or the minikernel image until the active and standby controller cards are synchronized.

1.4.5   Upgrade the Minikernel Image

If your system is running a boot ROM image that is earlier than the version listed in the release notes, you must upgrade the boot ROM image before you install the new software release. To determine the boot ROM and minikernel version you have, see the Before You Begin section.

If your system is running a minikernel image that is earlier than the version listed in the release notes, you must upgrade the minikernel image after you install the new software release and upgrade the traffic card FPGAs:

  1. Enter the following command in exec mode to upgrade to the new version of the minikernel image:

    upgrade minikernel {ftp: | scp: | /md} url

    The following example uses FTP to download the netbsd.v22.bin file from a server in the lab domain:

[local]Redback#upgrade minikernel ftp://userid:pwd@lab/netbsd.v22.bin

Double slashes (//directory) indicate an absolute path name to a directory on the remote server; a single slash (/directory) indicates a relative path name under the username account home directory:

  1. Type y and press Enter when the system prompts you to continue with the following message:
This operation will cause the box to reload, do you want to continue? 

The reload process takes several minutes. If your system has a standby controller card, the minikernel image on the standby controller card is synchronized automatically with the active controller card.

  1. When the reload is complete, verify that the system is using the new minikernel image; enter the show version command in any mode.
  2. If your system has dual controller cards, wait a few minutes until the system has had a chance to synchronize its controller cards and then verify the redundancy state. The following example illustrates the show redundancy command:
[local]Redback>show redundancy
--------------------------------
This XCRP is active
---------------------------------
STANDBY XCRP READY?: YES
VxWorks in sync?: YES
Database in sync?: YES
Software Release in sync?: YES
Firmware in sync?: YES
Mate-to-Mate link up?: YES

1.4.6   Upgrade the Traffic Card FPGAs

You might need to upgrade the traffic card FPGAs after you install the new software release image. Each traffic card has one or more FPGAs. Each FPGA has a supported version; for a table of supported FPGA versions, see the release notes for the release to which you are upgrading.

Mismatches between the supported and actual FPGA versions might occur after a software upgrade:

To upgrade traffic card FPGAs after you install a new software release image:

  1. Determine whether any traffic cards on your system require a mandatory FPGA upgrade; enter the following command in any mode:

    show chassis

    The command output displays an “M” flag for any traffic card that requires an FPGA upgrade. (This flag appears only for mandatory FPGA upgrades; it does not appear for optional FPGA upgrades.) If an “M” flag is shown for any traffic card, that traffic card will not be initialized.

  2. For each traffic card with an “M” flag or if you choose to upgrade a traffic card that has an out-of-date FPGA image, enter the following command in exec mode:

    reload fpga slot

  3. The new software release image may also include optional but recommended FPGA upgrades for one or more traffic cards. For each traffic card, enter the following command in exec mode:

    show hardware card slot detail

  4. Examine the command output. If the value of the nameFpga file rev is greater than the value of the nameFpga rev, a newer FPGA image is available for the traffic card.
%LOG-6-TDM_CONS: [resMgrLo] *NOTICE* Card in slot 2 has HubFpga rev mismatch
  1. After all upgrades are complete, verify that the FPGA versions are correct; enter the following command for each traffic card:

    show hardware card slotdetail

1.4.7   Verify System Chassis State

Enter the show chassis command to verify that the installed cards have been initialized and are operating. The following example illustrates the show chassis command (in any mode) for an SmartEdge 800 router.

[local] Redback>show chassis 
Current platform is SE800
(Flags: A-Active Crossconnect    B-StandBy Crossconnect  C-SARC Ready
        D-Default Traffic Card   E-EPPA Ready            G-Upgrading FPGA
        H-Card Admin State SHUT  I-IPPA Ready            M-FPGA Mismatch
        N-SONET EU Enabled       O-Card Admin State ODD  R-Traffic Card Ready
        S-SPPA Ready             U-Card PPAs UP          W-Warm Reboot
        X-XCRP mismatch)
Slot: Configured-type           Slot: Installed-type    Initialized Flags
-----------------------------------------------------------------------
  1 : ge-10-port                  1 : ge-10-port                Yes IEUR
  2 : none                        2 : none                      No  
  3 : none                        3 : none                      No  
  4 : none                        4 : none                      No  
  5 : ge-10-port                  5 : ge-10-port                Yes IEUDR
  6 : none                        6 : none                      No  
  7 : xcrp                        7 : xcrp                      Yes A
  8 : xcrp                        8 : xcrp                      Yes B
  9 : ge-10-port                  9 : ge-10-port                Yes IEUR
 10 : none                       10 : none                      No  
 11 : none                       11 : none                      No  
 12 : none                       12 : none                      No  
 13 : none                       13 : none                      No
 14 : ge-10-port                 14 : ge-10-port                Yes IEUR

1.4.8   Verify System Routing

Enter the show ip route summary all-context command (in any mode) to display summary information for all IP routes in all contexts and verify routing operations after the upgrade.

1.5   Modular Upgrade (Patch) Instructions

This section describes how to install a system patch to your operating system. The modular patch upgrade replaces only individual operating system components that need to be upgraded, so is only suitable for deploying minor software changes. The patch preserves existing subscriber sessions and interrupts traffic forwarding only if the software of one or more line cards is updated, and then for typically less than one minute on each affected interface.

Table 3, shows the commands that apply modular patch upgrades. For a full description the command, see the Command List.

Table 4    Modular Upgrade (Patch) Tasks

Task

Root Command

Install an modular system patch on the system.

release download modular

Display release and installation information for the software images currently installed on the system.

show release

Display the current version of the software running on the system.

show version

Upgrade the boot ROM image in the EEPROM on the active controller card in a working system and reload it.

upgrade bootrom

Upgrade the minikernel image in the EEPROM on the active controller card in a working system and reload it.

upgrade minikernel

To install a modular patch to your operating system:

  1. Enter the release download command with the modular keyword in exec mode to download the modular patch to the active partition.
  2. After the modular patch is installed, enter the release upgrade command with the modular keyword (in exec mode).

2   Format Internal Devices, Install a New System Image, or Both

This section describes how to perform the following tasks:

Table 5 lists the information required to reformat internal devices and also to install a new system image.

Table 5    Optional and Required Data

Prompt

Description

Example Data

IP address

IP address of the Ethernet management port on the controller card to which you will connect.

155.53.53.254

netmask

Network mask for the IP address of the Ethernet management port on the controller card to which you will connect.

255.255.252.0

gateway IP address

IP address of the gateway router to the IP network of the TFTP server. This address is not used if the TFTP server is on the same subnet as the SmartEdge router.

155.53.39.254

IP address of server

IP address of the TFTP server on which the system image file is located.

155.53.32.126

username and password

Account name and password to access the system image.

test

path to release

URL for the system image to be downloaded.

/images/REL_5_0_3/SEOS-5.0.3.tar.gz

install directory (p01/p02)

Partition in which to install the system image, usually p01.

p01

Perform the following steps to format internal devices, install a new system image, or both:

  1. Access the boot ROM interface (that is, get to the ok prompt)
    • Enter the reload command (in CLI exec mode) from the console port:
[local]Redback#reload 
Auto-boot in 5 seconds - press se* to abort, ENTER to boot:

If you typed se* within 5 seconds, the boot ROM ok prompt appears. The system sets the auto-boot time limit to 5 seconds; however, during some operations, such as a release upgrade, the system sets the time limit to one second to speed up the process, then returns it to 5 seconds when the system reboots. (If you missed the time limit, the reload continues; start again with step a.)

  1. Display and verify boot parameters; enter the following boot ROM command:

    ok printenv

    This command prints all boot parameters.

  2. Verify that the parameters listed in Table 6 are set to the required values.
Table 6    Boot Parameter Values

Parameter

Value

boot-device

flash

boot-command

bootsys

  1. If these values are not correctly set, enter the following boot ROM command to set the required values:

    ok setenv parameter value

  2. Reformat the devices and download a new software image:
    1. Invoke the minikernel image; enter the following boot ROM command:

      ok installsys

    2. Enter the data as requested by the system when it prompts you for the following information: local IP address, the network mask, and the gateway IP address for a server on which the software release is located.
    3. Enter y at the prompt to format a device; otherwise, enter n.
    4. Enter y at the prompt to install a new release; otherwise, enter n.
    5. If you entered y in the previous step, enter the data as requested by the system when it prompts you for the remote server data: IP address of the server, the username and password, and the URL of the release package.

    After the download is complete, the minikernel image exits and the prompt changes to #.

  3. Reload the system with the downloaded image:
    1. Enter the following boot ROM command:

      #reboot

    2. If a standby controller card is present, the system synchronizes it to the updated active controller card:

      syncing disks... done

      rebooting

      Program terminated!

      [0]Booting(2)....

      Enabling L1/L2 Caches.....

The following example displays output and responses for Step 5; responses are shown in bold:

Starting System Install Script...

Enter IP address : 10.12.209.197
Enter netmask : 255.255.248.0

Enter gateway IP address : 10.12.208.1
Configuring ethernet interface...
add net default:gateway 10.12.208.1

Checking for presence of first compact flash disk...compact flash disk 
detected
Checking for presence of second compact flash disk...compact flash disk 
detected

Two compact flash disks detected on XCRPSMRP....

Checking for presence of hard disk...hard disk detected
Would you like to erase the vxWorks compact flash disk(Y/N) : y

formatting compact flash disk...done
Would you like to erase the BSD compact flash disk(Y/N) : y
formatting compact flash disk...10+0 records in
10+0 records out
655360 bytes transferred in 1 secs (655360 bytes/sec)
/dev/rwd1a: 377856 sectors in 1476 cylinders of 8 tracks, 32 sectors
184.5MB in 93 cyl groups (16 c/g, 2.00MB/g, 512 i/g)
super-block backups (for fsck -b #) at:
32, 4160, 8288, 12416, 16544, 20672, 24800, 28928,
32800, 36928, 41056, 45184, 49312, 53440, 57568, 61696,
65568, 69696, 73824, 77952, 82080, 86208, 90336, 94464,
98336, 102464, 106592, 110720, 114848, 118976, 123104, 127232,
131104, 135232, 139360, 143488, 147616, 151744, 155872, 160000,
163872, 168000, 172128, 176256, 180384, 184512, 188640, 192768,
196640, 200768, 204896, 209024, 213152, 217280, 221408, 225536,
229408, 233536, 237664, 241792, 245920, 250048, 254176, 258304,
262176, 266304, 270432, 274560, 278688, 282816, 286944, 291072,
294944, 299072, 303200, 307328, 311456, 315584, 319712, 323840,
327712, 331840, 335968, 340096, 344224, 348352, 352480, 356608,
360480, 364608, 368736, 372864, 376992,
done
Would you like to erase the hard disk(Y/N) : y

Would you like to download a new release(Y/N) : y
Enter IP address of server : 10.12.215.10
Enter username : test
Enter password :
Enter path to release :/images/REL_5_0_3/SEOS-5.0.3.tar.gz
Enter install directory (p01/p02) : p01
ftping release...

ftp://test:test@10.12.215.10//images/REL_5_0_3/SEOS-5.0.3.tar.gz
(13890K)
- [########################] 13890K | 117.69K/s
14223725 bytes transferred in 118.03 sec (117.69k/sec)

copying releases to appropriate compact flash disk....
.
.
.
done

Exiting System Install Script...
#

3   Enable Automatic Reload

The operating system supports up to two controller cards per router: one active and one on standby. The operating system ensures that the standby controller card is synchronized with the active controller card so that, if the active controller card fails, the standby can become active immediately. To synchronize the two controller cards, the operating system occasionally reloads the standby controller card automatically. This requires that the auto-boot? variable be set to true.

For more information about the auto-boot? variable, see the Upgrading the Boot ROM or Minikernel section.

To verify the setting of the auto-boot? variable on both controller cards, perform the following tasks:

3.1   Connect a Console to the Console Port on Each Controller Card

The console port is labeled “Craft 2” on the front panel of the controller card. (Two cables are shipped with the system for connecting consoles to the console ports.)

3.2   Set the auto-boot? Variable on the Active Controller Card

After you are connected to the SmartEdge router through the console that is connected to the active controller card, perform the following steps

  1. Enter the reload command in exec mode.
  2. Determine the state of the boot ROM variable, auto-boot?:
    • If you see the following message on the console connected to the active controller card, the auto-boot? variable has already been set to true:
Auto-boot in 5 seconds - press se* to abort, ENTER to boot:

Enter se* to cancel the reload process and access the boot loader interface. Proceed to the Set the auto-boot? Variable on the Standby Controller Card section.

  1. Set the auto-boot? variable to true; enter the following command:
ok setenv auto-boot? true auto-boot? = true 
  1. Because you have modified the boot loader, enter the following command:
ok reset

The reset command resets the hardware and initiates a system reload.

  1. Proceed to the Set the auto-boot? Variable on the Standby Controller Card section.

3.3   Set the auto-boot? Variable on the Standby Controller Card

After you are connected to the SmartEdge router through the console that is connected to the standby controller card, perform the following steps:

  1. Determine the state of the auto-boot? variable
    • If you see the standby# prompt on the console, the auto-boot? variable is set to true. No further action is needed.
    • If you see the ok prompt on the console connected to the standby controller card, the auto-boot? variable is set to false.
  2. Set the auto-boot? variable to true; enter the following command:
ok setenv auto-boot? true  auto-boot? = true 
  1. Because you have modified the boot loader, enter the following command:
ok reset

If the active controller card fails, the system will continue to operate with the standby controller card.

3.4   Upgrade Operations

Upgrade operations using the non-standard reboot procedure are described in the following sections.

Note:  
Before attempting this procedure, consult your technical support representative.

3.4.1   Upgrade to a New Boot ROM Image

The boot ROM image is stored in the EEPROM on a controller card.

Table 7 lists the data needed to download the new boot ROM file; arguments described are configured through the setenv boot ROM command.

Table 7    Data Required to Download the Boot ROM File

Argument

Description

Example

ip-addr

IP address and network mask of the Ethernet management port on the controller card to which you will be connected; format is A.B.C.D:E.F.G.H.

155.53.53.254:255.255.252.0

gateway-ip-addr

IP address of the gateway router to the IP network on which the server is located. This address is not used if the server is on the same subnet as the SmartEdge router.

155.53.55.254

server-ip-addr

IP address of the server.

10.21.6.200

To upgrade to a new boot ROM image in the EEPROM, perform the following steps:

  1. Access the boot ROM interface (that is, get to the ok prompt).
    1. Enter the reload command (in CLI exec mode) from the console port:

      [local]Redback#reload

    2. Watch the reload progress messages carefully. When the following message appears, immediately type se*:

      Auto-boot in 5 seconds - press se* to abort, ENTER to boot:

      The system sets the auto-boot time limit to 5 seconds; however, during some operations, such as a release upgrade, the system sets the time-limit to one second to speed up the process, then returns it to 5 seconds when the system reboots. (If you missed the time limit, the reload continues; start again with step a.)

  1. Verify that the arguments listed in Table 7 are set to the required values; enter the following boot ROM commands:

    ok printenv ip-addr

    ok printenv gateway-ip-addr

    ok printenv server-ip-addr

  2. If the values for the arguments listed in Table 7 are not correct, enter the following commands with the correct values:

    ok setenv ip-addr ip-addr

    ok setenv gateway-ip-addr gateway-ip-addr

    ok setenv server-ip-addr server-ip-addr

  3. Enter one of the following commands to download the new boot ROM image file:

    ok load net filename

    or

    ok load hd:a /flash/filename

    where the filename argument is the filename of the boot ROM image file provided by your local technical representative, for example, bootrom-new.bin.

  4. Enter the following command to update the EEPROM:

    ok update-bootrom

3.4.2   Upgrade to a New Minikernel Image

Table 8 lists the data needed to download the new minikernel image; arguments described are configured through the setenv boot ROM command.

Table 8    Data Required to Download the Minikernel Image

Argument

Description

Example

ip-addr

IP address and network mask of the Ethernet management port on the controller card to which you will be connected; format is A.B.C.D:E.F.G.H.

155.53.53.254:255.255.252.0

gateway-ip-addr

IP address of the gateway router to the IP network on which the server is located. This address is not used if the server is on the same subnet as the SmartEdge router.

155.53.55.254

server-ip-addr

IP address of the server.

10.21.6.200

To upgrade to a new minikernel image, perform the following steps:

  1. Access the boot ROM interface (that is, get to the ok prompt):
  1. Enter the reload command (in CLI exec mode) from the console port:

    [local]Redback#reload

  2. Watch the reload progress messages carefully. When the following message appears, immediately type se*:

    Auto-boot in 5 seconds - press se* to abort, ENTER to boot:

    The system sets the auto-boot time limit to 5 seconds; however, during some operations, such as a release upgrade, the system sets the time-limit to one second to speed up the process, then returns it to 5 seconds when the system reboots. (If you missed the time limit, the reload continues; start again with step a.)

  1. Verify that the arguments listed in Table 8 are set to the required values; enter the following boot ROM commands:

    ok printenv ip-addr

    ok printenv gateway-ip-addr

    ok printenv server-ip-addr

  2. If the values for the arguments listed in Table 8 are not correct, enter the following commands with the correct values:

    ok setenv ip-addrip-addr

    ok setenv gateway-ip-addr gateway-ip-addr

    ok setenv server-ip-addr server-ip-addr

  3. Download the new minikernel image; enter one of the following boot ROM commands:

    okload net filename

    or

    ok load hd:a /flash/filename

    where the filename argument is the filename of the minikernel image provided by your local technical representative; for example, netbsd.min.v20.bz2.

  4. Install the new minikernel image; enter the following boot ROM command:

    ok write-kernel

4   Reloading the System Manually

If you need to restart the operating system, you can do so without having to power down the system. To restart the operating system manually, reload the main memory of the active controller card. You can also reload the standby controller card and you can switch over to the standby controller card.

To restart the operating system, perform one of the tasks described in Table 9; enter all commands in exec mode.

Table 9    Manual Reload Tasks

Task

Root Command

Reload the system software on the active controller card first, and then reload the standby controller card.

reload

Reload the system software on the standby controller card only.

reload standby

Reload the system software on the active controller card and, if the standby controller card is ready, cause the standby card to become the active controller card.

reload switch-over