Guest

Cisco BTS 10200 Softswitch

Field Notice: FN - 62709 - Sun1280 114527-04 (5.20.3) Firmware Patch for Daylight Saving Time (DST) Change for the BTS10200


March 16, 2007

February 19, 2007

NOTICE:

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Products Affected

Comments

BTS Other - 4.X

Sun 1280 only

Problem Description

Recommended Sun firmware to comply with the upcoming U.S. 2007 DST changes.

Background

New U.S. Daylight Saving Time rules go into effect in March 2007.

For systems that have not been updated with the new U.S. DST policy changes, timestamps will exhibit a one hour time clock offset lasting three weeks beginning at 2:00 A.M. on the second Sunday in March of 2007. They will also exhibit a one hour time clock offset lasting one week beginning at 2:00 A.M. on the first Sunday in November.

The primary fix for this issue is described in FN 62688. In addition, Sun recommends that the firmware on the 1280s be upgraded so that the System Controller firmware has the necessary updates.

For further details and to obtain a copy of the patch, you can visit the Patches & Updates from the Sun Update Connection.

Problem Symptoms

This is a recommendation by Sun but the overall effects to the BTS Customers operational status should be minimal if customers adhere to BTS application field notice FN 62688.

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.20.3, it is recommended to upgrade to the (5.20.3) latest SUN firmware. The patch and further details are located on the Patches & Updates page.

Upgrade Prerequisites

The following requirements 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 114527-04.zip onto ftp server.

    • The patch can be downloaded from Sunsolve

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

    • Unzip the patch.

      Example:

      [hostname]#cd /tmp 
      [hostname]#unzip 114527-04.zip
      

For each box this will require the following steps to be executed:

  1. Obtain management IP address, Netmask, hostname, DNS domain ,DNS server before going for next steps

  2. Run an Ethernet cable to connect the network that the FTP server resides on to the Solaris System Controler (SSC). This is the port labeled "SSC#".

    Note: Put the port in the management vlan for your BTS such that it would have access to a TFTP server via this vlan.

Verify Firmware

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

  1. Connect to the console.

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

  3. lom>showsc
    
  4. Example:

  5. #################################

  6. lom>showsc
    
  7. SC: SSC1

  8. System Controller

  9. Clock failover disabled.

  10. SC date: Tue Jun 14 12:15:33 PDT 2005

  11. SC uptime: 321 days 1 hour 26 minutes 11 seconds

  12. ScApp version: 5.17.0

  13. RTOS version: 38

  14. Solaris Host Status: Active - Solaris #################################

  15. If the ScApp version is not 5.20.3 and the RTOS version is not 45, then continue 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. Connect to console.

  2. Connect ethernet cable to the LOM/SC port.

  3. Set up IPaddress for LOM/SC port.

  4. lom>setupnetwork
    
  5. Example:

  6. ##################################

  7. lom>setupnetwork
    
  8. Network Configuration

  9. ---------------------

  10. Is the system controller on a network? [yes]: yes
    
  11. Use DHCP or static network settings? [DHCP]: static
    
  12. Hostname [c02u2cl212]:

  13. IP Address [10.2.2.122]: 10.89.183.14
    
  14. Netmask [255.255.0.0]: 255.255.255.0
    
  15. Gateway [10.2.2.254]: 10.89.183.254
    
  16. DNS Domain []:

  17. Primary DNS Server []:

  18. Secondary DNS Server []:

  19. Connection type (telnet, none) [none]:

  20. Rebooting the SC is required for changes in the above network settings to take effect. ##################################

  21. Reset SC controller.

  22. 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.20.3:

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

  2. Verify all BTS platforms are up as STANDBY. Issue the nodestat command to verify all applications are in standby state.

  3. Connect to console

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

  5. Upgrade firmware on SC:

    Caution: When performing this step, do not:

    • Power down any part of the system.

    • Reset any part of the system.

    • lom>flashupdate -f ftp://user:password@// all rtos
      

    Example:

    lom>flashupdate -f ftp://root:opticall@10.89.224.9//tmp/114527-04 all rtos
    
  6. Verify System Boards

  7. lom>showboards -p version
    

    Example:

     
    lom>showboards -p version 
    
    

    Component

    Compatible

    Version

    SSC1

    Reference

    5.19.3 Build_01

    /N0/IB6

    Yes

    5.19.3 Build_01

    /N0/SB0

    Yes

    5.19.3 Build_01

    /N0/SB2

    Yes

    5.19.3 Build_01

  8. Upgrade firmware on all system boards.

  9. lom> flashupdate -f ftp://:@// all rtos
    

    Example:

    lom>flashupdate -f ftp://root:opticall@10.89.224.9//tmp/114527-04 all rtos
    

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

  10. Shut down all BTS platforms.

  11. prica19# platform stop all
    
  12. Shut down Solaris Operating System.

  13. prica19# shutdown -i0 -g0 -y
    
  14. Power 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.

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

  16. At the lom> prompt, issue the poweron command.

    Example:

    lom>poweron
    
  17. Verify all platforms are up as STANDBY. Once the system has booted up, log in as root and issue the nodestat command to verify the applications have come back to standby state.

  18. Wait 15 minutes for the system to stabilize.

  19. Switchover all platforms and repeat the same procedure for the 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
    
  20. After following the steps mentioned above if you see any fault reasons then do the following exercises to get all the relevant information about the system being upgraded

    showboards -v 
    showcomponent -v 
    showfault 
    showlogs -v 
    showerrorbuffer 
    showsc -v
    

If showboards -v command returns any of the Slot containing CPU board as component with Status Degraded, execute the following

lom>showchs -b 

Component

Status

/N0/RP0

Suspect

/N0/SB0/P2/B1/D1/L0

Faulty

/N0/SB2

Suspect

Note: If the above output comes, then call SUN support .

If showcomponent -v returns untest for any component, there is no concern.

Revision History

Revision

Date

Comment

1.1

16-MAR-2007

Updated Title, Background and Workaround/Solution sections with new patch version 114527-04.

1.0

19-FEB-2007

Initial Public Release

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.