INSTRUCTIONS     1/190 47-CRA 119 1170/1-V1 Uen F    

Installing Release 6.3.1.1

© Copyright Ericsson AB 2010. All rights reserved.

Disclaimer

No part of this document may be reproduced in any form without the written permission of the copyright owner. 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 L M Ericsson.

Contents


1

Installing Release 6.3.1.1
1.1Supported Hardware
1.2Booting the Device for the First Time
1.3Upgrading to Release 6.3.1.1
1.4Verifying System Operation After an Upgrade



1   Installing Release 6.3.1.1

This document describes the SmartEdge router and Release 6.3.1.1 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 your core dumps to 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/.

1.1   Supported Hardware

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

1.1.1   Supported Devices

You can run Release 6.3.1.1 on the following devices:

This release is compatible with common equipment available for the SmartEdge 100, SmartEdge 400, SmartEdge 600, SmartEdge 800, SmartEdge 1200, and SmartEdge 1200H routers. Release 6.3.1.1 supports all versions of SmartEdge controller cards, including the new Cross-Connect Route Processor (XCRP) Version 4 (XCRP4) Controller card.

For more information about the hardware and common equipment, see the CD-ROM that accompanies the SmartEdge router or the support web site for the hardware guides for your particular platform. For information about the new hardware introduced in Release 6.3.1.1, see Technical Product Description.

1.1.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 800 and SmartEdge 1200 chassis types.

Table 1    SmartEdge 800 and SmartEdge 1200 Chassis Types

Chassis

Product Code

Description

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 1200s

D7

Standard SmartEdge 1200 chassis; not certified as NEBS compliant.

SmartEdge 1200n

D9

NEBS-compliant SmartEdge 1200 chassis.

SmartEdge 1200H

H1

High-power NEBS-compliant SmartEdge 1200 chassis.

1.1.3   Required FPGA Versions for Traffic Cards

Note:  
The versions in this table are subject to change and may increase over time as new versions are released.

Table 2 lists the field-programmable gate array (FPGA) version required for each traffic card. The Lim or Hub FPGA is present on all traffic cards; the Hub FPGA is present only on traffic cards that use PPA2. The Flip or Spi FPGA is present only on Ethernet cards; the Spi FPGA is present only on Ethernet traffic cards that use PPA2.

Table 2    Required FPGA Version for Each Traffic Card and MIC

Traffic Card

Tioga or Hub FPGA

Lim or Spi FPGA

Flip or Sonata FPGA

2-port 1000Base-TX Gigabit Ethernet MIC

2-port SFP-Based Gigabit Ethernet MIC

12-port 10/100 TX MIC

12-port 100 FX SFP-based MIC

2-port ATM OC-3c/STM-1c IR MIC

0x27

1-port OC-48c/STM-16c XR

0x7

0x5

1-port OC-48c/STM-16c LR1

0x7

0x5

1-port OC-48c/STM-16c LR2

0x7

0x5

1-port OC-48c/STM-16c SR

0x7

0x5

4-port OC-12c/STM-4c IR

0x7

0x4

8-port OC-3c/STM-1c IR

0x3

0x4

1-port channelized OC-12 to DS-3 IR

0x7

0x3

1-port channelized OC-12 to DS-1 IR

0x7

0x3

3-port channelized STM-1 to E1/DS-0 IR

0x7

0xE

12-port 10/100 Ethernet

0x7

0x5

0x9

4-port Gigabit Ethernet

0x7

0x5

0xC

4-port Gigabit Ethernet, Advanced

0x7

0x5

0xC

12-port channelized DS-3

0x7

0xA

12-port clear-channel DS-3

0x7

0xA

3-port channelized DS-3

0x7

0xA

6-port clear-channel E3

0x7

0x1

24-port channelized E1

0x7

0xC

12-port ATM DS-3

0x7

0x3

1-port ATM OC-12c/STM-4c IR

0x7

0x9

1-port ATM OC-12c/STM-4c IR, Enhanced

0x7

0x3

2-port ATM OC-3c/STM-1c IR

0x7

0x9

4-port ATM OC-3c/STM-1c IR

0x7

0x6

8-port ATM OC-3c/STM-1c

0x03

0x04

1-port POS OC-192c/STM-64c

0x42

0x17

4-port POS OC-48c/STM-16c

0x03

0x05

4-port POS OC-12c/STM-4c

0x03

0x05

8-port POS OC-3c/STM1-c

0x03

0x05

4-port Gigabit Ethernet 3

0x9

0xA

5-port Gigabit Ethernet

0x53

0x13

10-port Gigabit Ethernet 1020 (less than Rev 60)

0x43

0x6

10-port Gigabit Ethernet 1020 (greater than or equal to Rev 60)

0x60

0xC

20-port Gigabit Ethernet 1020

0x43

0x6

60-port Fast Ethernet plus 2-port Gigabit Ethernet

0xd

0xd1

20-port Gigabit Ethernet

0x09

1-port 10 Gigabit Ethernet

0x41

0x17

4-port 10 Gigabit Ethernet

0x0A

0x26

SmartEdge Storage Engine (SSE)

0x1e

-

-

Advanced Storage Engine (ASE)

0x44

5.7

-

Note:  
To determine which FPGA version is required, enter the show hardware card <slot no.> detail command.

Note:  
If you use a Lim or Spi 10-port Gigabit Ethernet 1020 card (greater than or equal to Rev 60), you must upgrade to 0x13. Failing to do so may result in intermittent card failures after reloads.

1.2   Booting the Device for the First Time

To boot an SmartEdge router for the first time:

  1. Connect a console to the named port on the router
    • SmartEdge 100 router—“CRAFT” on the front panel of the chassis.
    • SmartEdge 400 router—“CRAFT 2” on the active XCRP3 controller card or “CRAFT” on the active XCRP4 controller card in slot 6.
    • SmartEdge 600 router—“CRAFT 2” on the active XCRP4 controller card in slot 7.
    • SmartEdge 800 router—“CRAFT 2” on the active XCRP3 controller card or “CRAFT” on the active XCRP4 controller card in slot 7.
    • SmartEdge 1200 router—“CRAFT” on the active controller card in slot 7.
    • SmartEdge 1200H router—“CRAFT” on the active controller card in slot 7.
  2. Power on the SmartEdge router.
    • 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. For more information, see the SmartEdge 400 Router Hardware Guide.
    • 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. For more information, see the SmartEdge 600 Router Hardware Guide.
    • 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. For more information, see the SmartEdge 800 Router Hardware Guide.
    • 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. For more information, see the SmartEdge 1200 Router Hardware Guide.
    • 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. For more information, see the SmartEdge 1200H Router Hardware Guide.
  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 5 seconds, the auto-boot? variable is already set to true. No changes are necessary.
  4. Set the auto-boot? variable to true at the prompt; enter:

    setenv auto-boot? true

  5. To reset the hardware, enter:

    reset-all

  6. Wait for the system to reload.

1.3   Upgrading to Release 6.3.1.1

To upgrade the SmartEdge OS to Release 6.3.1.1, perform the following procedures.

  1. Before You Begin: Release 6.3.1.1 Upgrade Alerts
  2. Check the Required Software Components
  3. Upgrade the Boot ROM Image
  4. Upgrade the Minikernel Image
  5. Upgrade the Minikernel Image (Optional Additional Steps for Release 6.3.1.1)
  6. Download the 6.3.1.1 Release Image
  7. Upgrade to the 6.3.1.1 Release Image
  8. Upgrade the Traffic Card FPGAs
  9. Verify System Chassis State
  10. Verify System Routing

1.3.1   Before You Begin: Release 6.3.1.1 Upgrade Alerts

Note the following situations that require additional steps or may affect your system before you upgrade to Release 6.3.1.1:

In addition, before you upgrade, check for any relevant security notifications on the Ericsson E-business portal at https://ebusiness.ericsson.net.

1.3.1.1   Update Bridge Profile Configuration

In this release, a port or circuit can be associated with either a bridge profile or a link group, but not both. If you have one or more ports or circuits associated with both a bridge profile and a link group, change the configuration so that the bridge profile is configured for the link group—not the port or circuit—before you upgrade to Release 6.3.1.1.

1.3.1.2   Preserve Link Group Configuration

In newer releases (after 6.1.4.1), a port or circuit can be associated to a bridge profile or to a link group, but not both. To preserve this behavior after the upgrade:

  1. Use the show configuration command to display the link-group configuration.
  2. Copy the configuration to a text file.
  3. If you have bridge profiles configured directly under any of the physical ports belonging to a link group, remove them.
  4. Upgrade the SmartEdge router to Release 6.3.1.1.
  5. Use the text file you created with link group configuration information to reconfigure the bridge profiles under the dot1q pvc mode under the link group. This must be done manually.
  6. Reapply the bridge profiles to the ATM PVCs under the link group.
  7. Verify that the link group configuration is correct.

1.3.1.3   Remove IS-IS Graceful Restart

In Release 6.1.4.3, the command [no] graceful-restart replaced the [no] restart graceful-time command.

The implementation of IS-IS graceful restart in Release 6.1.4.3 and subsequent releases does not interoperate with the previous implementations of the feature. As a result, for IS-IS graceful restart, systems running earlier releases of the SmartEdge OS will not interoperate with those running Release 6.1.4.3 and later.

Before you upgrade to Release 6.3.1.1 (if you are not on release 6.1.4.3 or later), first disable IS-IS graceful restart by using the no restart graceful-time command (pre-Release 6.1.4.3 version of the command). When the upgrade to Release 6.3.1.1 is completed on all adjacent IS-IS routers, use the graceful-restart command (Release 6.1.4.3 and later version of the command) to re-enable the feature.

If you need to downgrade from Release 6.3.1.1 to a release earlier than 6.1.4.3, first disable IS-IS graceful restart on all adjacent IS-IS routers by using the no graceful-restart command. After downgrading a router, use the no restart graceful-time command to disable the feature on that router until all other IS-IS routers have been downgraded. When the downgrade is completed on all IS-IS routers, use the restart graceful-time command to re-enable the feature for each router. Remember that all SmartEdge IS-IS systems in your network must be running the same version of graceful restart; different versions do not interoperate.

1.3.1.4   Required Upgrade to New Boot ROM Version for XCRP4

If you use an XCRP4 controller card, you must upgrade to boot ROM version 2.0.2.45 before upgrading to Release 6.3.1.1. See Upgrade the Boot ROM Image. If you do not upgrade the boot ROM version, the system is unable to boot.

If you attempt to upgrade to Release 6.3.1.1 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, contact your support representative.

If you upgrade to Release 6.3.1.1 without upgrading the boot ROM version, and your system does not boot, contact your support representative for instructions to resolve this problem.

1.3.1.5   Required Upgrade to Minikernel Version for XCRP4

If you use an XCRP4 controller card, you must upgrade to minikernel version 11.7 before upgrading to Release 6.3.1.1. See Upgrade the Minikernel Image.

1.3.1.6   Additional Steps to Upgrade the Minikernel for Some XRCP4 Systems

If your system uses an XCRP4 Controller card, and you meet any of the following conditions, you must download the new boot ROM and minikernel versions by performing the procedure outlined in the “Upgrade to a New Boot ROM Image” and “Upgrade to a New Minikernel Image” sections in the Upgrading the Boot ROM or Minikernel document. You must also perform the additional steps in the Upgrade the Minikernel Image (Optional Additional Steps for Release 6.3.1.1) section after you upgrade the minikernel version to 11.7.

1.3.2   Check the Required Software Components


 Caution! 
If you use an XCRP4, you must upgrade the boot ROM and minikernel versions to the versions in Table 3. If you do not, serious errors may result.

To upgrade to Release 6.3.1.1, the router must be running the boot ROM and minikernel versions listed in Table 3. You can verify that the router is running the correct software components by entering the show version command. (The version of the boot ROM image is shown in the line that begins System Bootstrap version.)

Table 3    Software Components Required for Release 6.3.1.1

Component

Version

Filename

XCRP boot ROM

1.0b1272

of1272.bin

XCRP minikernel

23

netbsd.min.v23.bz2.bin

XCRP3 boot ROM

1.0b1272

of1272.bin

XCRP3 minikernel

23

netbsd.min.v23.bz2.bin

XCRP4 boot ROM

2.0.2.45

OFW-XC4-2.0.2.45.fallback.md5

XCRP4 minikernel

11.7

MINIKERN_RBN64-xc4.p11.v7

ASE boot ROM

2.0.2.45

OFW-ASE-2.0.2.45.fallback.md5

ASE minikernel

13.5

MINIKERN_ASE64-ase.p13.v5

SmartEdge 100 controller boot ROM

2.0.1.4

OFW-se100-2.0.1.4.primary.bin

SmartEdge 100 controller minikernel

2.7

se100-minikernel.p2.v7.bin

Note:  
When upgrading the minikernel on a system running release 6.1.1.5 and boot ROM version 2.0.2.45, an extra reboot is required for all components to be fully operational.

1.3.3   Upgrade the Boot ROM Image

To determine the boot ROM and minikernel version you have, see the Before You Begin: Release 6.3.1.1 Upgrade Alerts section.

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 of1272.bin file from a server in the lab domain:

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

Double slashes (//directory) indicate an absolute pathname to a directory on the remote server; a single slash (/directory) indicates a relative pathname 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.
    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

1.3.4   Upgrade the Minikernel Image

Table 3 lists the required minikernel version and filename. If a minikernel upgrade is necessary:

  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 filename.ext file from a server in the lab domain and dir directory:

[local]Redback#upgrade minikernel 
ftp://userid:pwd@lab//dir/filename.ext

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

  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; enter 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

1.3.5   Upgrade the Minikernel Image (Optional Additional Steps for Release 6.3.1.1)

Note:  
Perform this procedure only if your system uses an XCRP4 and you meet the following criteria:
  • You used minikernel 11.5 to reformat the internal flash memory.
  • The internal flash memory card has less than 900 MB of total space. Use the show disk command to determine the space on the internal flash memory card (in 512-byte increments).

To continue upgrading the 6.3.1.1 minikernel image:

  1. Back up all data on the internal flash memory card. Ensure that you have backed up your configuration settings.
  2. 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 autoboot time limit to 5 seconds; however, during some operations, such as a release upgrade, the system sets the time limit to 1 second to speed the process, then returns it to 5 seconds when the system reboots. (If you missed the time limit, the reload continues.)

  1. 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 minikernel image is not installed on the system boot ROM. In this case, you must install the minikernel image in the boot ROM; perform the procedure described in the Upgrade the Minikernel Image section.

  2. 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.
  3. 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.
  4. 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.
  5. When the system prompts you for the remote server data, enter the IP address of the server, username and 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.

  6. Reload the system with the downloaded image:
    1. If you use an XCRP3 controller card: enter the reboot command to reboot the system.

      or

      If you use an XCRP4 controller card: enter 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.

1.3.6   Download the 6.3.1.1 Release Image


 Caution! 
Before beginning the release download process, ensure that you have performed any additional steps outlined in the Before You Begin: Release 6.3.1.1 Upgrade Alerts section. If you do not perform the steps outlined in that section, you may lose your configuration be unable to boot your router.
Note:  
If you completed the steps outlined in the Upgrade the Minikernel Image (Optional Additional Steps for Release 6.3.1.1) section, you downloaded the new release using the minikernel and do not need to perform this procedure.

To download Release 6.3.1.1 of the SmartEdge OS image to the alternate partition on your system:

  1. Enter the release download command in exec mode:

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

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

1.3.7   Upgrade to the 6.3.1.1 Release Image


 Caution! 
Before beginning the release upgrade process, ensure that you have performed any additional steps outlined in the Before You Begin: Release 6.3.1.1 Upgrade Alerts section. If you do not perform the steps outlined in that section, you may lose your configuration or be unable to boot your router.
Note:  
If you completed the steps outlined in the Upgrade the Minikernel Image (Optional Additional Steps for Release 6.3.1.1)section, you downloaded the new release using the minikernel and do not need to perform this procedure.

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

  1. Enter the release upgrade command in exec mode to activate the 6.3.1.1 software image.
[local]Redback#release upgrade
  1. When you are prompted to reboot, verify that the SmartEdge OS version in the prompt message is 6.3.1.1. Type y 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 filename for the configuration, the system saves the current configuration in the redback.cfg file.
  3. When the upgrade is complete and running the new SmartEdge OS, verify that the system is using the 6.3.1.1 SmartEdge OS image; enter the show version command in any mode.
    Note:  
    If the system fails to restart using the 6.3.1.1 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 traffic card FPGAs or the minikernel image until the active and standby controller cards are synchronized.

1.3.8   Upgrade the Traffic Card FPGAs

You might need to upgrade the traffic card FPGAs after you install the 6.3.1.1 software release image. Each traffic card has one or more FPGAs. Each FPGA has a supported version; for supported FPGA versions, see Table 2.

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

Note:  
Upgrading a traffic card FPGA interrupts traffic forwarding on the affected card for approximately 5 minutes.

To upgrade traffic card FPGAs after you install the 6.3.1.1 software release image:

  1. Determine whether any traffic cards on your system require a mandatory FPGA upgrade by entering 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

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

  3. For each traffic card, enter the following command in exec mode:

    show hardware card slot detail

    The 6.3.1.1 software release image may also include optional, but recommended, FPGA upgrades for one or more traffic cards.

  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.
    Note:  
    If the system detects a mismatch during a reboot, a message similar to the following appears:

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


    The show log active tdm-console command output also shows the logged message.

  5. After all upgrades are complete, verify that the FPGA versions are correct by entering the following command for each traffic card:

    show hardware card slot detail

1.3.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 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.3.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.

1.4   Verifying System Operation After an Upgrade

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

1.4.1   Before You Begin

The procedure for testing and verifying the installation of your SmartEdge software begins after you have powered on your SmartEdge router and accessed the SmartEdge OS CLI through its console port (also called the CRAFT 2 port). The SmartEdge router hardware guides contain descriptions of how to power on your SmartEdge router 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:

1.4.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 version is installed. In addition, check bootstrap (also called the boot ROM) and minikernel versions.
  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 traffic 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
...

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

1.4.4   Run ODD Tests on Each Traffic Card

To run ODD tests for each traffic card:

  1. Enter the card command (in configuration mode) to enter card configuration mode.
  2. Enter the shutdown command to shut down the traffic 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 traffic card.

1.4.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 XCRP3 controller cards and earlier, you can run tests at levels 1 and 2. For XCRP4 and SmartEdge 100 router controller cards, you can run tests at levels 1, 2, 3, and 4.

  2. Run the ODD 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.

1.4.6   Bring Traffic Cards into Service

To bring traffic 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 traffic cards. Verify that the Link LED indicators on the traffic cards show that all connected ports have successfully established link-level connectivity.

    The traffic card LEDs are described in detail in SmartEdge 100 Hardware Guide, SmartEdge 400 Hardware Guide, SmartEdge 600 Hardware Guide, SmartEdge 800 Hardware Guide, SmartEdge 1200 Hardware Guide, and SmartEdge 1200H Hardware Guide.

  2. Enter the show port detail command (in any mode) to verify that the line state and admin state are up and no alarms are present.

1.4.7   Assign IP Addresses to Management Ports

Assign an IP address to the management port (Ethernet) 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 

1.4.8   Check System Status

To check system status:

  1. For systems with two controller cards, enter 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
 
  1. Enter the show disk command in exec mode to display the status of the internal (NetBSD compact-flash) and external (mass-storage device) memory cards 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. Enter 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. Enter 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 due to the fact that the traffic ports are not physically connected, no unexpected alarms should be present.
  4. Enter 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. Enter 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
...

1.4.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. Enter the reload switch-over command to force the standby controller card to assume control of the system.
  2. Enter 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: