Installing Release 6.4
SmartEdge OS for SmartEdge Routers , Release 6.4.1

Contents

1Introduction

2

Supported Hardware
2.1Supported Devices
2.2Identifying Hardware

3

Booting the Device for the First Time

4

Upgrading to Release 6.4
4.1Before You Begin
4.2Upgrade the Boot ROM Image
4.3Upgrade the Minikernel Image
4.4Additional Minikernel Upgrade Steps
4.5Download the 6.4 Release Image
4.6Upgrade to the 6.4 Release Image
4.7Upgrade the Line Card FPGAs
4.8Recover a Standby Controller Card
4.9Verify System Chassis State
4.10Verify System Routing

5

Verifying System Operation After an Upgrade
5.1Before You Begin
5.2Check the Versions of Software and Hardware
5.3Check the Results of POD Tests
5.4Run ODD Tests on Each Line Card
5.5Run ODD Tests on the Standby Controller Card
5.6Bring Line Cards into Service
5.7Assign IP Addresses to Management Ports
5.8Check System Status
5.9Switch to the Standby Controller Card and Continue Testing
Copyright

© Ericsson AB 2010. 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.

1   Introduction

This document describes the SmartEdge router and Release 6.4 of the SmartEdge OS.

Note:  
If the SmartEdge router stops forwarding packets or routing protocol peers stop exchanging messages, check the process status using the show process crash-info and show chassis commands in any mode. If any process has a respawn count greater than 1, that process has been restarted. Send core dumps to your local technical support representative, along with the system version, configuration, any console logs of the activity during a crash, and all stored log messages.

For current security notifications, visit the Ericsson E-business portal at https://ebusiness.ericsson.net/.

2   Supported Hardware

This section describes supported hardware for the SmartEdge OS, Release 6.4.

2.1   Supported Devices

This release is compatible with common equipment available for the SmartEdge router . You can run Release 6.4 on the following devices:

Release 6.4 supports the Cross-Connect Route Processor (XCRP) Version 4 (XCRP4) Controller card.

For more information about hardware and common equipment, see the CD-ROM that accompanies the SmartEdge router or the support web site for the hardware guide for your specific platform:

For information about new hardware introduced in Release 6.4, see the Technical Product Description.

2.2   Identifying Hardware

You can identify particular hardware by entering the show hardware command (in any mode).

Table 1 lists the two-character product codes (the first two characters in the serial number) that identify the SmartEdge chassis types.

Table 1    Chassis Types

Chassis

Product Code

Description

SmartEdge 100 AC

B8

SmartEdge 100 chassis that supports AC power.

SmartEdge 100 DC

B9

SmartEdge 100 chassis that supports DC power.

SmartEdge 400 AC

44

SmartEdge 400 chassis that supports AC power source with an AC power tray.

SmartEdge 400 DC

0A

SmartEdge 400 chassis that supports DC power.

SmartEdge 800e

9C

SmartEdge 800 chassis; not certified as NEBS compliant.

SmartEdge 800 NEBS

8Y

NEBS-compliant SmartEdge 800e chassis.

SmartEdge 800s

B2

SmartEdge 800 NEBS chassis with BNC connectors removed.

SmartEdge 1200n

D9

NEBS-compliant SmartEdge 1200 chassis.

SmartEdge 1200H

H1

High-power NEBS-compliant SmartEdge 1200 chassis.

3   Booting the Device for the First Time

To boot a SmartEdge router for the first time:

  1. Connect a console to the named port on the device:
    • SmartEdge 100 router—“CRAFT” on the front panel of the chassis.
    • SmartEdge 400 router—“CRAFT” on the controller card. This is slot 6 for the active controller card or slot 5 for the standby controller card.
    • SmartEdge 600 router—“CRAFT 2” on the controller card. This is slot 7 for the active controller card or slot 8 for the standby controller card.
    • SmartEdge 800 router—“CRAFT” on the controller card. This is slot 7 for the active controller card or slot 8 for the standby controller card.
    • SmartEdge 1200 router—“CRAFT” on the controller card. This is slot 7 for the active controller card or slot 8 for the standby controller card.
    • SmartEdge 1200H router—“CRAFT” on the controller card. This is slot 7 for the active controller card or slot 8 for the standby controller card.
  2. Power on the device:
    • SmartEdge 100 router—Toggle the switch to “on,” which is marked “1” on the rear panel.
    • SmartEdge 400 router—Insert the fuses in the external fuse panel or, if the router is powered by AC power, connect each AC power cord to a separate building outlet for a circuit rated at 15A with a 15A circuit breaker. The PWR A and optionally PWR B LEDs on the front of the chassis should light to signify adequate power.
    • SmartEdge 600 router—Insert the fuses in the external fuse panel. The PWR A and optionally PWR B LEDs on the front of the chassis should light to signify adequate power.
    • SmartEdge 800 router—Insert the fuses in the external fuse panel. The PWR A and optionally PWR B LEDs on the front of the chassis should light to signify adequate power.
    • SmartEdge 1200 router—Insert the fuses in the external fuse panel. The PWR A1 and PWR A2 LEDs on the front of the chassis should light to signify adequate power.
    • SmartEdge 1200H router—Insert the fuses in the external fuse panel. The PWR A1 and PWR A2 LEDs on the front of the chassis should light to signify adequate power.

    If you need more information about powering on your system or about inserting fuses, see the hardware guide for your device.

  3. Check the console output:
    1. If you see an ok prompt, the auto-boot? variable is set to false. You must change its value; proceed to Step 4.
    2. If a message appears indicating that the system will auto-boot in five seconds, the auto-boot? variable is already set to true. No changes are necessary; proceed to Step 5.
  4. Set the auto-boot? variable to true at the prompt by issuing the following command:

    setenv auto-boot? true

  5. To reset the hardware, enter the following:

    reset-all

  6. Wait for the system to reload.

4   Upgrading to Release 6.4

To upgrade your system to Release 6.4, perform the following steps:

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

4.1   Before You Begin


 Stop! 
The Advanced Services Engine (ASE) card must be running the correct version of the boot ROM and so must the SmartEdge OS system. To avoid a serious equipment outage in the field, if you are running SmartEdge OS Release 6.4.1.2 or later on either the ASE or the SmartEdge OS system, DO NOT DOWNGRADE to 6.4.1.1 or earlier. If you must downgrade, contact your support representative for an equipment-safe procedure. Downgrading from these releases can cause permanent damage to the ASE.

Before upgrading to Release 6.4, ensure your system is ready to upgrade:

4.2   Upgrade the Boot ROM Image


 Caution! 
You must upgrade the boot ROM version to the version listed as required for your release in the Technical Product Description. If you do not, serious errors may result and the system may be unable to boot.

If you attempt to upgrade to Release 6.4 without upgrading the boot ROM version, you see the following error:

-----------------------------------------------------------
Auto-boot in 0 seconds - press se* to abort, ENTER to boot:
no such file core1
Error: Alternate CPU load action 'load flash core1' failed
error: abort
-----------------------------------------------------------

If you see this error or your system does not boot, contact your support representative for instructions on how to resolve the problem.

To upgrade the boot ROM image:

  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 OFW-XC4-2.0.2.45.fallback.md5 file from a server in the lab domain:

[local]Redback#upgrade bootrom ftp://user-id:pwd@lab/dir/OFW-XC4-2.0.2.45.fallback.md5 

Double slashes (//directory) indicate an absolute pathname to a directory on the remote server; a single slash (/directory) indicates a relative pathname.

  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.
    Note:  
    If the system does not reboot, the auto-boot? variable in the new version of the boot ROM image might be set to false.

  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

ARP                          SUCCESS
CSM                          SUCCESS
DHCP                         SUCCESS
ISM                          SUCCESS
RDB                          SUCCESS
SM AAA DSLline               SUCCESS
SM AAA Session               SUCCESS
SM AAA Strings               SUCCESS
SM ISM2                      SUCCESS
SM LDP ADJ                   SUCCESS
SM LDP CTX                   SUCCESS
SM LDP PEER                  SUCCESS
SM LM                        SUCCESS
SM RCM                       SUCCESS
SM RIB                       SUCCESS
SM STATD                     SUCCESS

4.3   Upgrade the Minikernel Image


 Caution! 
You must upgrade the minikernel version to the version listed as required for your release in the Technical Product Description. If you do not, serious errors may result. Depending on your system, you may also have to perform the additional steps in " Additional Minikernel Upgrade Steps."

There is currently no procedure for upgrading the minikernel image that does not involve reloading the entire system and bringing down subscribers. Therefore, if the target code image requires an update to one of these components, ISSU cannot be used.

If your system is not currently running the minikernel version required for your release, perform the following steps:

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

    upgrade minikernel {ftp: | scp: | /md} url. When using this syntax, note the following:

    • Double slashes (//directory) indicate an absolute path name to a directory on the remote server; a single slash (/directory) indicates a relative pathname.
    • When referring to a file on a remote server, the syntax for the url argument is:

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

    • When referring to a file on the /md directory, the syntax for the url argument is:

      filename.ext

    The following example uses FTP to download the minikernel file MINIKERN_RBN64-xc4.p11.v7 from a server in the lab domain in the test_sw directory. In the example, the FTP username and password are my_userid and my_password, respectively.

[local]Redback#upgrade minikernel 
ftp://my_userid:my_password@lab//test_sw/MINIKERN_RBN64-xc4.p11.v7
  1. Type y and press Enter when the system prompts you to reload.

    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.

  2. When the reload is complete, verify that the system is using the new minikernel image by issuing the show version command in any mode.
  3. If your system has dual controller cards, wait a few minutes until the system has had a chance to synchronize its controller card, and then verify the redundancy state. Enter 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  

ARP                          SUCCESS
CSM                          SUCCESS
DHCP                         SUCCESS
ISM                          SUCCESS
RDB                          SUCCESS
SM AAA DSLline               SUCCESS
SM AAA Session               SUCCESS
SM AAA Strings               SUCCESS
SM ISM2                      SUCCESS
SM LDP ADJ                   SUCCESS
SM LDP CTX                   SUCCESS
SM LDP PEER                  SUCCESS
SM LM                        SUCCESS
SM RCM                       SUCCESS
SM RIB                       SUCCESS
SM STATD                     SUCCESS

4.4   Additional Minikernel Upgrade Steps

If either of the following conditions are met, you must perform the additional steps in this section after upgrading the minikernel version:

To continue upgrading the 6.4 minikernel image:

  1. Ensure that you have backed up your configuration settings with one of the following methods:
    • Save the current configuration to /flash or to a remote location (by FTP or SCP) with the save configuration /flash/filename command or the save configuration ftp://username[:password]@ip-address//path/filename command.
    • Back up the configuration during the upgrade. When the system prompts you to save the current configuration, enter y and specify the location and filename for the file. If you do not specify the location and filename, the SmartEdge OS saves the configuration to /flash/redback.cfg.

    Verify that the configuration was saved before proceeding with the upgrade.

  2. Access the boot ROM interface (that is, navigate to the ok prompt):
    1. From the console port, enter the reload command (in exec mode):

      [local]Redback#reload

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

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

      If you typed se* within five seconds, the boot ROM ok prompt appears. The system sets the autoboot time limit to five seconds; however, during some operations, such as a release upgrade, the system sets the time limit to one second to speed the process, then returns it to five seconds when the system has rebooted. (If you missed the time limit, the reload continues.)

  3. Invoke the minikernel image by entering the following boot ROM command:

    ok installsys

    Note:  
    If the system returns an error or does not return a prompt after you enter the installsys command, the required minikernel image is not yet installed. In this case, go back and install the minikernel image.

  4. Enter the data when the system prompts you for the local IP address of the server, network mask, and gateway IP address for a server on which the software release is located.
  5. If you plan to install the minikernel by using the external Flash memory, leave the prompts for the network configuration blank and press the Enter key.
  6. At the prompts for the network configuration:
    • Enter y at the prompt to format the internal Flash memory.
    • Enter n at the prompt to format the external Flash memory.
    • Enter y at the prompt to install the new release.
  7. When the system prompts you for the remote server data, enter the IP address of the server, username, password, and URL of the release package.

    or

    Enter the URL to the operating system image if you are installing from the external Flash memory.

  8. Reload the system with the downloaded image:
    1. Enter the y at the prompt to reboot the system.
    2. If a standby controller card is present, the system synchronizes it to the updated active controller card.

4.5   Download the 6.4 Release Image

To download Release 6.4 of the SmartEdge OS image to the alternate partition on your system, perform the following steps:

  1. Enter the release download command in exec mode:

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

    Note:  
    The release download command works in the local context..

    • If you enter the hostname argument instead of 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 pathname.

    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 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 SmartEdge OS image; enter the show release command in any mode.

4.6   Upgrade to the 6.4 Release Image

Before upgrading the release image, back up your system and verify that the information has been successfully saved. Several steps in the upgrade procedure reboot the device, which could delete the running configuration if it is not successfully saved.


 Caution! 
Before beginning the release upgrade process, ensure that you have performed any additional steps outlined in the upgrade alerts listed in the Technical Product Description for your release.

 Stop! 
If you are upgrading an FPGA image version for PPA3 cards, ensure that you have performed the special manual procedure in "FPGA Upgrade Required for PPA3 Cards" in the Technical Product Description for your release. If a downgrade is needed after performing the special manual procedure, see "Downgrade an FPGA Upgrade for PPA3 Cards" in the Technical Product Description for your release.

After downloading the 6.4 release image, continue with the following steps to upgrade your system to the 6.4 SmartEdge OS image. This procedure activates the alternate partition to which the 6.4 software has been downloaded:

  1. Enter the release upgrade command in exec mode to activate the new software image.
[local]Redback#release upgrade
  1. The system warns you that it will reboot and that the release will become active immediately. Verify that the SmartEdge OS version in the prompt message is 6.4.
  2. When the system prompts you to continue, type y and press Enter. The system begins the upgrade.
  3. When the upgrade is complete and running the new SmartEdge OS, verify that the system is using the 6.4 SmartEdge OS image; enter the show version command in any mode.
    Note:  
    If the system fails to restart using the 6.4 SmartEdge OS image, and your system has dual controller cards, the system reboots and reloads the old SmartEdge OS. If your system does not have dual controller cards, you can restore the old SmartEdge OS by switching partitions from the console boot ROM interface.

  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  

ARP                          SUCCESS
CSM                          SUCCESS
DHCP                         SUCCESS
ISM                          SUCCESS
RDB                          SUCCESS
SM AAA DSLline               SUCCESS
SM AAA Session               SUCCESS
SM AAA Strings               SUCCESS
SM ISM2                      SUCCESS
SM LDP ADJ                   SUCCESS
SM LDP CTX                   SUCCESS
SM LDP PEER                  SUCCESS
SM LM                        SUCCESS
SM RCM                       SUCCESS
SM RIB                       SUCCESS
SM STATD                     SUCCESS

Do not upgrade the line card FPGAs until the active and standby controller cards are synchronized.

4.7   Upgrade the Line Card FPGAs


 Stop! 
Before beginning the line card FPGA upgrade process for PP3 cards, ensure that you have performed the special manual procedure in "FPGA Upgrade Required for PPA3 Cards" in the Technical Product Description for your release. If a downgrade is needed after performing the special manual procedure, see "Downgrade an FPGA Upgrade for PPA3 Cards" in the Technical Product Description for your release.

Each line card has one or more FPGAs, each of which has a required (supported) version for a given release of the SmartEdge OS. Whenever the SmartEdge OS detects an FPGA mismatch, it logs a message similar to the following:

%LOG-6-TDM_CONS: [resMgrLo] *NOTICE* Card in slot 2 has HubFpga rev mismatch

Depending on the line card type, the card may or may not initialize when an FPGA mismatch occurs.

To upgrade the FPGA on a line card:

  1. Confirm that you have the time required to perform the upgrade.

    Traffic on a card is interrupted for approximately five minutes for each FPGA upgrade.

  2. Stop traffic to the card you want to upgrade by administratively shutting it down with the shutdown command, if it is not already done.

     Caution! 
    There must be no live traffic running on a card while its FPGA is being upgraded.
  3. Enter the following command in exec mode:

    reload fpga slot

    Note:  
    If you are upgrading an ATM OC MIC on a SmartEdge 100 router, see additional syntax specifications for the reload fpga command. If you are upgrading another type of line card on the SmartEdge 100 router, use the reload fpga mic slot command.

  4. After the upgrade is complete, bring the card back into service using the no shutdown command.
  5. Verify that the FPGA version is correct by issuing the following command:

    show hardware card slot detail

    Ensure that the value of nameFpga rev (the version on the card) in the command output matches the value of the nameFpga file rev (the version in the SmartEdge OS).

[local]Redback>show hardware card 1 detail
 
Slot                : 1                 Type                : ge4-20-port
Serial No           : F101G4710G0VDU    Hardware Rev        : 01
EEPROM id/ver       : 0x5a/4            Mfg Date            : 30-NOV-2010
HubFpga rev         : 0xf               HubFpga file rev    : 0xf
SpiFpga rev         : 0x0               SpiFpga file rev    : N/A
IPPA memory         : 2048 MB           EPPA memory         : 2048 MB
Voltage 1.200V      : 1.196 (-0%)       Voltage 1.200V      : 1.196 (-0%)
Voltage 1.200V      : 1.201 (+0%)       Voltage 1.250V      : 1.245 (-0%)
Temperature         : NORMAL (52 C)
Card Status         : HW initialized    POD Status          : Success
ODD Status          : Not Available
Fail LED            : Off               Active LED          : On
Standby LED         : Invalid
Chass Entitlement   : All (0x0)
Ports Entitled      : All
Active Alarms       : NONE

4.8   Recover a Standby Controller Card

In rare occurrences, during a release upgrade, the standby XCRP card may not come up. This issue does not impact service. To recover the standby XCRP card, manually reseat the card in its slot.

Use the show chassis and show redundancy commands to verify the state of the primary and standby XCRP cards. For the expected output, see Section 4.9 and Section 5.8, respectively.

Alternatively, use a console connection to the XCRP cards to monitor the state.

4.9   Verify System Chassis State

Enter the show chassis command (in any mode) to verify that the installed cards have been initialized and are operating. The following example shows the output from the show chassis command for a SmartEdge 1200 router :

[local] Redback>show chassis 
Current platform is SE1200 NEBS
 (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 Upgrade Required
    N-SONET EU Enabled        O-Card Admin State ODD    P-Coprocessor Ready
    P1-ASP1 Ready             P2-ASP2 Ready             R-Traffic Card Ready
    S-SPPA Ready              U-Card PPAs/ASP UP        W-Warm Reboot
    X-XCRP mismatch)
Slot: Configured-type           Slot: Installed-type          Initialized Flags
-------------------------------------------------------------------------------
  1 : 10ge-4-port                 1 : 10ge-4-port               Yes IEUDR
  2 : 10ge-4-port                 2 : 10ge-4-port               Yes IEUR
  3 : 10ge-4-port                 3 : 10ge-4-port               Yes IEUR
  4 : ge-10-port                  4 : none                      No
  5 : 10ge-4-port                 5 : none                      No
  6 : ge-10-port                  6 : none                      No
  7 : xcrp4-base                  7 : xcrp4-base                Yes A
  8 : xcrp4-base                  8 : xcrp4-base                Yes B
  9 : none                        9 : none                      No
 10 : none                       10 : none                      No
 11 : none                       11 : ge4-20-port               No
 12 : none                       12 : none                      No
 13 : none                       13 : none                      No
 14 : none                       14 : none                      No

The following example shows a controller card that did not come up. To resolve this issue, see Section 4.8

[local] Redback>show chassis
Current platform is SE1200 NEBS
 (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 Upgrade Required
         N-SONET EU Enabled      O-Card Admin State ODD  P-Coprocessor Ready
         P1-ASP1 Ready           P2-ASP2 Ready           R-Traffic Card Ready
         S-SPPA Ready            U-Card PPAs/ASP UP      W-Warm Reboot
         X-XCRP mismatch)
Slot: Configured-type Slot: Installed-type Initialized Flags
-------------------------------------------------------------------------------
1 : fege-60-2-port               1 : fege-60-2-port      Yes IEUDR
2 : fege-60-2-port               2 : fege-60-2-port      Yes IEUR
3 : ge4-20-port                  3 : ge4-20-port         Yes IEURH
4 : ge4-20-port                  4 : ge4-20-port         Yes IEURH
5 : none                         5 : none No 
6 : none                         6 : none No 
7 : xcrp4-base                   7 : xcrp4-base          Yes A
8 : xcrp4-base                   8 : unknown             No B
9 : none                         9 : none No 
10 : none                       10 : none No 
11 : none                       11 : none No 
12 : ge4-20-port                12 : ge4-20-port         Yes IEURH
13 : none                       13 : none No 
14 : none                       14 : none No 

4.10   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.

5   Verifying System Operation After an Upgrade

This section describes the steps to take to verify that a newly installed SmartEdge router is operating properly.

5.1   Before You Begin

The procedure for testing and verifying the installation of your SmartEdge software begins after you have powered on your device and accessed the SmartEdge OS CLI through its console port. The hardware guide for your device contains descriptions of how to power on the device and connect to its console ports.

Although this procedure covers all SmartEdge systems, it does not provide the details of each possible installation configuration. You need the following information before proceeding:

5.2   Check the Versions of Software and Hardware

To check the versions of software and hardware:

  1. Enter the show version command (in any mode) to confirm that the expected SmartEdge OS, boot ROM, and minikernel versions are installed.
  2. Enter the show hardware command (in any mode) to verify that the hardware versions are as expected. Check the temperature and voltage readings.
  3. Enter the card command (in global configuration mode) to enable the line cards on the SmartEdge router ; for example:
[local]Redback#configure 
[local]Redback(config)#card ether-12-port 5 
  1. Enter the show chassis command (in any mode) to display installed and configured card types and slot locations and verify that all installed cards are successfully initialized; for example:
[local]Redback>show chassis 

Current platform is SE800e
(Flags: A-Active Crossconnect    B-StandBy Crossconnect  C-SARC Ready
...

5.3   Check the Results of POD Tests

Enter the show diag pod command with the detail keyword (in any mode) to display the results of the power-on diagnostics (POD) tests. All POD results should indicate the PASS condition.

[local]Redback>show diag pod detail 

5.4   Run ODD Tests on Each Line Card

To run ODD tests for each line card:

  1. Enter the card command (in configuration mode) to enter card configuration mode.
  2. Enter the shutdown command to shut down the line card.
  3. Enter the on-demand-diagnostic command to enable the ODD.
  4. Enter the diag on-demand command to start the ODD session on the card. Run the ODD at level 3. For example:
[local]Redback(config)#card ether-12-port 5 
[local]Redback(config-card)#shutdown   
[local]Redback(config-card)#on-demand-diagnostic   
[local]Redback(config-card)#end     

Nov 4 14:06:38: Marking PTD channel DEAD for slot 5   
... 

[local]Redback#diag on-demand card 5 level 3    

Marking PTD channel DEAD for slot 5   
... 
  1. Enter the show diag on-demand command with the detail keyword to show the results of the ODD. The Test Summary field shows In Progress if the test has not been completed.
[local]Redback#show diag on-demand card 5 detail

Slot Number             : 5
Card Type               : ether-12-port
Detected Card Type      : ether-12-port   
Serial Number           : 7UAA8070200197  
Detected Serial Number  : 7UAA8070200197  
Controller Serial Number: 6Y515070603805  
Test Level              : 3  
Loop Count              : 4  
Start Time              : 14:09:09  11/04/2005  
Completion Time         : N/A  
Test Summary            : In Progress    

  1. Repeat this procedure for each line card.

5.5   Run ODD Tests on the Standby Controller Card

To run ODD tests on the standby controller card:

  1. Enter the diag on-demand standby level 2 command to run these tests at level 2.
    Note:  
    For XCRP4 and SmartEdge 100 router controller cards, you can run tests at levels 1, 2, 3, and 4.

  2. Run the ODD test for the standby controller card at level 2. (The SmartEdge 100 router does not support standby controller cards.)
[local]Redback# diag on-demand standby level 2 
  1. Enter the show diag on-demand standby command to show the results of the ODD. Use the detail keyword to see the details rather than the summary.

5.6   Bring Line Cards into Service

To bring line cards into service:

  1. Enter the no on-demand-diagnostic command followed by the no shutdown command, for example:
[local]Redback#configure 
[local]Redback(config)#card ether-12-port 5 
[local]Redback(config-card)#no on-demand-diagnostic
[local]Redback(config-card)#no shutdown   
[local]Redback(config-card)#end  
  1. Connect a fiber or wire loopback (Rx to Tx) on each port of the line cards. Verify that the Link LED indicators on the line cards show that all connected ports have successfully established link-level connectivity. The line card LEDs are described in detail in the hardware guides for your device.
  2. Enter the show port detail command (in any mode) to verify that the line operational and administrative state are both "up" and no alarms currently exist.

5.7   Assign IP Addresses to Management Ports

Assign an IP address to the Ethernet management port on the active controller card and another IP address to the management port on the standby controller card. (The SmartEdge 100 router does not have a standby controller card.) Verify that you can use a Telnet session to connect to the management ports.

The following example shows how to assign an IP address to the management port of the active controller card in slot 7 of a SmartEdge 800 router :

[local]Redback#configure 
!Create the interface in the local context and assign an IP address 
[local]Redback(config)#context local 
[local]Redback(config-ctx)#interface mgmt 
[local]Redback(config-if)#ip address 192.168.110.1 255.255.255.0 
[local]Redback(config-if)#exit 
!Configure the management port 
[local]Redback(config)#port ethernet 7/1 
[local]Redback(config-port)#bind interface mgmt local 
[local]Redback(config-port)#no shutdown 
[local]Redback(config-port)#end 

5.8   Check System Status

To check system status:

  1. For systems with two controller cards, issue the show redundancy command to verify that the active and standby controller cards are ready and synchronized.
[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    

ARP                          SUCCESS
CSM                          SUCCESS
DHCP                         SUCCESS
ISM                          SUCCESS
RDB                          SUCCESS
SM AAA DSLline               SUCCESS
SM AAA Session               SUCCESS
SM AAA Strings               SUCCESS
SM ISM2                      SUCCESS
SM LDP ADJ                   SUCCESS
SM LDP CTX                   SUCCESS
SM LDP PEER                  SUCCESS
SM LM                        SUCCESS
SM RCM                       SUCCESS
SM RIB                       SUCCESS
SM STATD                     SUCCESS
 

The following example shows a controller card that did not come up. To resolve this issue, see Section 4.8

[local]Redback>show redundancy
---------------------------------
This XCRP is active
---------------------------------
STANDBY XCRP READY? : NO
VxWorks in sync? : NO
Database in sync? : NO
Software Release in sync? : NO
Firmware in sync? : NO
Mate-to-Mate link up? : NO
  1. Issue the show disk command in exec mode to display the status of the internal memory card (NetBSD compact Flash) and external memory card (mass storage device) in the controller card to which you are connected.

    If you are displaying the status of an external mass storage device, this command should display the device as mounted on the /md directory.

  2. Issue the show memory command (in any mode) to display statistics about the available and allocated memory in the system memory partition of the main memory on the controller card to which you are connected. Verify that the memory approximately matches the expected used and free numbers of bytes.
  3. Issue the show system alarm all command (in any mode) to display system-, card-, port-, channel-, and subchannel-level alarms. Although some alarm conditions might be present because the traffic ports are not physically connected, you should see no unexpected alarms.
  4. Issue the show log command (in any mode) so that you can check all the alarms reported since starting this installation procedure. Enter the show log command with the active tdm-console keywords (in any mode) to display system alarm events reported to the console.
  5. Issue the show hardware detail command. Compare the output of the command with what you expect for this SmartEdge router equipped with the same options.
[local]Redback#show hardware detail 
Fan Tray Status            Present
Fan(s) Status              Normal
Power Supply A Status      Normal
Power Supply B Status      Normal
Active Alarms              NONE
...

5.9   Switch to the Standby Controller Card and Continue Testing

For routers with two controller cards, switch to the standby controller card. To test a controller card, it must be in the active state:

  1. Issue the reload switch-over command to force the standby controller card to assume control of the system.
  2. Issue the show redundancy command to verify that the active and standby controller cards are ready and synchronized after the switchover.
[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    

ARP                          SUCCESS
CSM                          SUCCESS
DHCP                         SUCCESS
ISM                          SUCCESS
RDB                          SUCCESS
SM AAA DSLline               SUCCESS
SM AAA Session               SUCCESS
SM AAA Strings               SUCCESS
SM ISM2                      SUCCESS
SM LDP ADJ                   SUCCESS
SM LDP CTX                   SUCCESS
SM LDP PEER                  SUCCESS
SM LM                        SUCCESS
SM RCM                       SUCCESS
SM RIB                       SUCCESS
SM STATD                     SUCCESS
  1. Repeat the following procedures: