Guest

Cisco BTS 10200 Softswitch

Field Notice: FN - 62118 - BTS10200 on Sun 1280 Requires Firmware Upgrade for Clock Slip


June 21, 2005


Products Affected

  • BTS-1280-4-AC=

  • BTS-1280-4-DC=

  • BTS-1280PROC-4=

Problem Description

The BTS 10200 1280's may be susceptible to clocking drift or jumping after a run time of 528 days resulting in a possible dual outage to resolve the issue.

Background

On very rare occasions, the Time of Day (TOD) on Sun Fire 3800/4800/4810/6800, V1280 and Netra 1280 domains may be susceptible to a clock drift or jump. This issue may occur after 528 days of SC continuous uptime, where the TOD within a domain in the system may become random and unstable. The intervals reported have varied, but the behavior is generally that the TOD jumps backwards approximately one hour.

For further details, you can reference the notice located in Sunsolve.

Problem Symptoms

System TOD clocking drifting or jumping in time. For example, hour increments.

Workaround/Solution

BTS 10200 Customers using 1280's in their solution must verify the firmware by executing the following command at the console level:

  1. #. [enter]

  2. LOM>showsc

    The command will display the "SC uptime:" and current "ScApp version:" firmware.

  3. If the firmware version is earlier than 5.18.3, it is recommended to upgrade to the (5.18.3) latest SUN firmware. The patch and further details are located on the Patches & Updates page.

Upgrading Prerequisites

The following requirement must be met before starting this procedure.

  1. A temporary ip address, netmask, and default gateway.

  2. An Ethernet cable.

  3. Console access.

  4. An FTP server

  5. Download and unzip the Solaris patch 114525-04.zip onto ftp server.

    • The patch can be download from Sunsolve

    • Transfer the patch to /tmp directory of an ftp server.

    • Unzip the patch.

      Example: [hostname]#cd /tmp

      [hostname]#unzip 114525-04.zip

Verifying Firmware

Perform the following steps to verify the firmware of the System Controller board (SC).

  1. Connecting to the console

  2. Entering to lom> prompt by typing #. (# sign and a dot )

  3. lom>showsc

    Example:

    ################################# 
    lom>showsc 
    SC: SSC1 
    System Controller 
    Clock failover disabled. 
    SC date: Tue Jun 14 12:15:33 PDT 2005 
    SC uptime: 321 days 1 hour 26 minutes 11 seconds 
    ScApp version: 5.17.0 
    RTOS version: 38 
    Solaris Host Status: Active - Solaris 
    ################################# 
    
  4. If the ScApp version is not 5.18.3 and RTOS version is not 41, then continuing on with this procedure. Otherwise stop.

Setting up network for SC

In order to upgrade the firmware, it is required that the 10/100 ethernet for LOM/System Controller (the RJ-45 connector next to serial port B) must be configured with a valid ip address for upgrading.

  1. Connecting to console.

  2. Connecting Ethernet cable to LOM/SC port.

  3. Setting up ip address for LOM/SC port.

  4. lom>setupnetwork

    Example:

    ################################## 
    lom>setupnetwork 
    Network Configuration 
    --------------------- 
    Is the system controller on a network? [yes]: yes 
    Use DHCP or static network settings? [DHCP]: static 
    Hostname [c02u2cl212]: 
    IP Address [10.2.2.122]: 10.89.183.14 
    Netmask [255.255.0.0]: 255.255.255.0 
    Gateway [10.2.2.254]: 10.89.183.254 
    DNS Domain []: 
    Primary DNS Server []: 
    Secondary DNS Server []: 
    Connection type (telnet, none) [none]: 
    Rebooting the SC is required for changes in the above network settings to take effect. 
    ##################################
    
  5. Reset SC controller.

    lom>resetsc
    

Performing Firmware Upgrade

Note: The procedure will require the BTS component being updated to be taken out of service during the procedure. This will not impact traffic for Customers operating on redundant systems

The following steps will upgrade the System Controller board firmware to 5.18.3.

  1. Using terminal, log in as root on STANDBY side.

  2. Verifying all BTS platforms are up as STANDBY.

    Use the nodestat command to verify all applications are in standby state.

  3. Connecting to console

  4. Entering lom> prompt.

    From the console connection, type #. (# sign and a dot) to get to the lom> prompt

  5. Upgrading firmware on SC

    caution Caution: When performing this step, do not:

    • Power down any part of the system.

    • Reset any part of the system.

      lom>flashupdate -f ftp://:@// scapp rtos

      Example:

      lom>flashupdate -f ftp://root:opticall@10.89.224.9//tmp/114525-04 scapp rtos 
      
  6. Verifying System Boards

    lom>showboards -p version
    

    Example:

    lom>showboards -p version
    

    Component Compatible Version

    --------- ---------- ------- 
    SSC1 Reference 5.17.0 
    /N0/IB6 Yes 5.17.0 
    /N0/SB0 Yes 5.17.0 
    /N0/SB2 Yes 5.17.0 
    /N0/SB4 Yes 5.17.0 
    
    
  7. Upgrading firmware on all system boards.

    lom> flashupdate -f ftp://:@// sb0 sb2 sb4 ib6
    

    Example:

    lom>flashupdate -f ftp://root:opticall@10.89.224.9//tmp/114525-04 sb0 sb2 sb4 ib6 
    

    Note: In this example, there are three System boards. If your system only has one System board, then sb2 and sb4 can be omitted.

  8. Shutting down all BTS platforms.

    prica19# platform stop all 
    
  9. Shutting down Solaris Operating System.

    prica19# shutdown -i0 -g0 -y 
    
  10. Powering off the system by unplugging power cords.

    Remove power from the system.

    Note: This is an important step. The system must be power cycled as part of the firmware upgrade.

  11. Wait about 30 seconds, then plug the power cords back.

  12. At lom> prompt, enter poweron.

    Example:

     lom>poweron 
    
  13. Verifying all platforms are up as STANDBY.

    Once the system has booted up, log in as root and use the nodestat command to verify the applications have come back to standby state.

  14. Wait for 15 minutes for system stabilize.

  15. Switchover all platforms and repeat the same procedure for other side.

    Use the appropriate CLI commands to switchover the applications.

    For call agent:

    CLI> control call-agent id=CAxxx 
    CLI> control feature-server id=FSPTCxxx 
    CLI> control feature-server id=FSAINxxx 
    

    For EMS:

    CLI> control bdms id=BDMSxx 
    CLI> control element-manager id=EMxx 
    

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.