Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

NEW    

Field Notice Customer Satisfaction Survey

 

Your feedback is very important to us.  Please take a minute to complete the brief Satisfaction Survey for this Field Notice

 

Cisco BTS 10200 Softswitch

Field Notice: FN - 62264 - BTS 10200 Softswitch Firmware Upgrade to 5.19.3 for Sun 1280 Platforms


Revised December 13, 2005

December 01, 2005

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

Product

Comments

BTS Other - 3.5

BTS 10200 Call Agent and EMS's utilizing N1280's and V1280's

BTS Other - 4.x

BTS 10200 Call Agent and EMS's utilizing N1280's and V1280's

Problem Description

Sporadic reboot failures on N1280 and V1280 hardware.

Background

During Cisco lab testing, it was observed sporadic reboot failures were occurring on the 1280's.

Problem Symptoms

System hangs on reboot.

Workaround/Solution

The workaround would be to power cycle the 1280's.

  1. Power off the system by unplugging power cords.

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

  3. At lom> prompt, enter poweron.

Solution:

The patch is available via SunSolve as patch ID 114526-04. The following link will take you to the server where you can obtain the patch.

http://sunsolve.sun.com/pub-cgi/show.pl?target=about_sunsolve

Once at the server, to the right side of the web page you will find the link to "Patches and Updates". Once you get to the patches and update web page, insert or copy and paste the patch ID 114526-04 in the window titled: "PatchFinder" and click on "Find Patch" button. This will take you to the download page for the patch with the supporting material.

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.19.3, it is recommended to upgrade to the (5.19.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 114526-04.zip onto ftp server.

    • The patch can be downloaded from Sunsolve (http://sunsolve.sun.com )

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

    • Unzip the patch.

Example:

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

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

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

    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.19.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@// scapp rtos

      Example:

      lom>flashupdate -f ftp://root:opticall@10.89.224.9//tmp/114526-04 scapp rtos

  6. Verify System Boards

    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

  7. Upgrade 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/114526-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. Shut down all BTS platforms.

  9. prica19# platform stop all

  10. Shut down Solaris Operating System.

  11. prica19# shutdown -i0 -g0 -y

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

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

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

    Example:

    lom>poweron

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

  16. Wait 15 minutes for the system to stabilize.

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

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.