7510 MGW Software Upgrade Customer Manual

All rights reserved.
Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent.
Next Generation Network Product Group Gateway Project: A7510 R3.0
___________________
7510 MGW Software Upgrade Customer Manual
02 01 ED
2009-12-04 2008-11-19 Date
Document revised Initial version Change Note Appraisal Authority
Rainer Bussmann Jens Guballa Author
Document based on Template 3FZ-01762-0001-PTZZA ED NGN 02 Draft 3FZ-08118-AAAA-TNZZA
ALL INFORMATION CONTAINED IN THIS DOCUMENT REMAINS THE SOLE AND EXCLUSIVE PROPERTY OF ALCATEL-LUCENT AND SHALL NOT BE DISCLOSED BY THE RECIPIENT TO THIRD PERSONS WITHOUT THE PRIOR WRITTEN CONSENT OF ALCATEL-LUCENT.
Alcatel-Lucent NGN
TABLE OF CONTENTS
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel-Lucent.
1 2 3 4
5 6
History .......................................................................................3 Referenced Documents....................................................................4 List of Abbreviations.......................................................................5 Scope.........................................................................................6 4.1 Product group and release applicability..........................................6 4.2 Abstract................................................................................6 Syntax Markers..............................................................................7 Hitless Software Upgrade .................................................................8 6.1 Patch Upgrade from R3.0 Bxx to R3.0 Byy .......................................8 6.2 Hitless Upgrade from R3.0 Bxx to R3.0 Byy ......................................8 6.2.1 Restrictions .......................................................................8 6.2.2 Preparation .......................................................................9 6.2.3 Starting the Upgrade ............................................................9 Non-hitless Software Upgrade.......................................................... 14 7.1 Preparation.......................................................................... 14 7.2 Starting the Upgrade .............................................................. 14 Graceful Software Upgrade............................................................. 17 8.1 SW-Upgrade Strategy .............................................................. 17 8.2 Precondition ........................................................................ 17 8.2.1 Login to the 7510 MG ......................................................... 17 8.2.2 Download of new SW-build (optional) ...................................... 18
8.2.2.1 8.2.2.2 Download PAK-file .................................................................................. 18 Check integrity of the new SW-build ......................................................... 18
8.2.3 Check state of all modules ................................................... 18 8.2.4 Verify that there is only one login session................................. 19 8.2.5 Backup the configuration file................................................ 19 8.2.6 Increase verbosity ............................................................. 20 8.3 SW-Upgrade Procedure ............................................................ 21 8.3.1 Start the drain down procedure .......................................... 21 8.3.2 Release remaining active call contexts .................................... 22 8.3.3 Activate the SW-Upgrade command ........................................ 22 8.3.4 Check new software configuration.......................................... 23 Appendix-A: FPGA/Boot/PROM check ................................................... 24 Appendix-B: TI-MCM Firmware Boot and FPGA upgrade .............................. 27
2/28
ALL INFORMATION CONTAINED IN THIS DOCUMENT REMAINS THE SOLE AND EXCLUSIVE PROPERTY OF ALCATEL-LUCENT AND SHALL NOT BE DISCLOSED BY THE RECIPIENT TO THIRD PERSONS WITHOUT THE PRIOR WRITTEN CONSENT OF ALCATEL -LUCENT
3FZ-08118-AAAA-TNZZA
Alcatel-Lucent NGN
1 History
Date 2008-11-24 2009-09-01 2009-12-02
Version Ed01P01 Ed01P02 Ed02P01
Author Jens Guballa Rainer Bussmann Rainer Bussmann
Change Description initial version link to [1] updated/corrected -document reworked, non-hitless and hitless SWUP added. -title changed
3/28
Alcatel-Lucent NGN
2 Referenced Documents
[1]. [2]. [3]. [4]. [5]. [6]. [7]. [8]. [9].
Alcatel-Lucent 7510 Media Gateway Release Note Rel 3.0 803-03757-BN01-DFZZA Media Gateway Safety Guidelines and Agency Approvals 3FZ 08013 AAAA PCZZA Media Gateway Installation and Configuration Guide 3FZ 08012 AAAP PCZZA Media Gateway Reference Guide: Gateway Specific Cmds 3FZ 08016 AAAP PCZZA Media Gateway Reference Guide: IP Specific Commands 3FZ 08017 AAAP PCZZA Media Gateway Reference Guide: Signaling Commands 3FZ 08055 AAAP PCZZA Media Gateway Reference Guide: TDM Specific Commands 3FZ 08075 AAAP PCZZA Media Gateway Alarm Manager User Guide 3FZ 08099 AAAP PCZZA Media Gateway Element Manager User Guide 3FZ 08057 AAAP PCZZA
4/28
Alcatel-Lucent NGN
3 List of Abbreviations
BGW CAS CLI CMC DCME FTP MG MGAM MGC MGEM SCM SGW SPC SSH SSR SW SWUP TFTP TGW UI VMG
Border Gateway Channel Associated Signaling Command Line Interface Convergent Network Management Center Digital Circuit Multiplication Equipment File Transfer Protocol Media Gateway Media Gateway Alarm Manager Media Gateway Controller Media Gateway Element Manager System Control Module Signaling Gateway Semi-Permanent Connection Secure Shell SWUP Safe Resources Software Software Upgrade Trivial File Transfer Protocol Trunk Gateway User Interface Virtual Media Gateway
5/28
Alcatel-Lucent NGN
4 Scope
4.1 Product group and release applicability

Product: A7510 Release: 3.0
4.2 Abstract
This document describes the procedure necessary to upgrade the 7510 MG with a new SWbuild. Three kinds of software upgrade are described, the hitless, non-hitless and graceful software upgrade.
6/28
Alcatel-Lucent NGN
5 Syntax Markers
In this document the following different font attributes and markers are used: Marker Bold fixed font Meaning Command line input to be provided by the operator Indicates the reply from the system Refers to a 7510 MG file name The operator must supply input for the argument contained in the angle brackets Example view chassis
Normal fixed font Italic fixed font Angle brackets <>
IP Gateway Cache Entries: 0 config.txt
check pak <filename>
7/28
Alcatel-Lucent NGN
6 Hitless Software Upgrade

If the customer wants to upgrade inside R3.0, which means to upgrade from a build Bxx of R3.0 to a build Byy from R3.0, follow this chapter. Example: Upgrade from R3.0 B01 to R3.0 B03. According to the Release notes of the R3.0 Byy build there can be a Patch- or a Hitless Upgrade possible. Please follow the corresponding subchapter. An operator forced downgrade from R3.0 Byy to R3.0 Bxx backwards can also be done in the same way as the upgrade. If you are connected to the 7510 via telnet session, please use command define ui syslog enable to get all output of the gateway to your session. For further investigations create and save a log-file before starting the upgrade
6.1 Patch Upgrade from R3.0 Bxx to R3.0 Byy

A patch upgrade is a hitless upgrade, which can only be supported for a dedicated software version with stable contexts and interfaces (from SW point-of-view). Which R3.0 software supports this kind of upgrade is mentioned in the official [1]Release Notes. Please continue with chapter 6.2 after you verified that a patch upgrade is possible.
Note: only point 20) in chapter 6.2.3 distinguishes a patch upgrade from a hitless upgrade
6.2 Hitless Upgrade from R3.0 Bxx to R3.0 Byy 6.2.1 Restrictions
Signaling Gateways are not supported by hitless SW upgrade. Gateways with CAS/DCME links are not supported by hitless SW upgrade. E1/T1 CIM cards are not supported by hitless SW upgrade. These cards need to be removed from chassis prior to upgrade. If the 7510 MGW is configured as a Border Gateway and all PIM cards are in one N+1 redundancy group and the IP traffic is categorized in amber side and green side traffic, then N must be greater or equal than 3. It must be guaranteed that after N+1 to 1+1 redundancy group conversion at least one PIM 1+1 redundancy group for amber and one group for green side exist.
8/28
Alcatel-Lucent NGN
6.2.2 Preparation
1) Logout all other users using the following commands view ui remove telnet connection x (with x is the connection id) 2) If not covered by a network management system as, e.g., the Alcatel-Lucent 1300 CMC, prepare an FTP client with IP connection to the OAM-port of the 7510 on an external host. 3) If not covered by a network management system as, e.g., the Alcatel-Lucent 1300 CMC, get R3.0 Software as described in the [1] Release Notes. 4) Check TI-MCM Boot and FPGA Version, see Appendix-B. 5) Check, if for each PIM/CIM/MCM N+1 redundancy group, SWUP Safe Resources (SSR) are defined, i.e., for each N+1 redundancy group 1+1 redundancy groups (with active cards) are defined, which take effect during SWUP. The calls on the active cards will not be lost. NOTE: This should have been done already during creation of redundancy groups. If this was not done yet use command: define redundancy ssr role <group_name> <chassis> <slot> {enable|disable}
6.2.3 Starting the Upgrade

1) Check Variant and ICS of all boards and compare with released ICS from official Release Notes (Example: Variant=CAAA, ICS=02) For any differences or problems contact Alcatel-Lucent Support!
9/28
Alcatel-Lucent NGN 2) Make sure one of the below settings being on: - diag view soft-: MGW Ignore dual pim, mcm, gigabite evts - view mg config: Alarm Throttling State (on, on), MCM failure (i.e. even of MCM getting down) is ignored (on, off), MCM failure (i.e. even of MCM getting down) is ignored (off, on), Send ServiceChanges for individual calls which is present on this MCM board, one by one. (off, off) , Disabling MG and forced to clear all active calls. i.e. get unregistered to MGC. All these combinations are needed in some situation. But the (off, off) MUST NOT be allowed in case of SWUP. Recommended settings in SWUP are: - diag view soft-: MGW Ignore dual pim, mcm, gigabite evts - view mg config: Alarm Throttling State
off on
3) Check via UI command the FPGA versions of all boards while still running the old software. Compare with released FPGA versions in the official [1] Release Notes of the new to be installed software. For details see Appendix-A. view prom full all For any differences or problems contact Alcatel-Lucent Support! Upgrading with wrong FPGA, Variant or ICS can lead to damaged boards and system outages. 4) Check Alarms status of the 7510 with command view alarm active Gateway should be alarm free or only known problems/alarms should be reported 5) Check for the availability of the new software package on the flash card. In case it is not present transfer the new software file <Lmmddyy.pak> with an external FTP client or a management system, e.g. CMC, to the active SCM of the 7510 MG. When doing so it has to be ensured that the binary transfer mode is used. 6) Check the integrity of the software file with command check pak <Lmmddyy.pak>
10/28
Alcatel-Lucent NGN
7) Copy the new software to the standby SCM with commands
(assumed: standby SCM in slot 11) rconsole 1 11 tftp get 200.1.1.42:<Lmmddyy.pak> check pak <Lmmddyy.pak> exit (assumed: standby SCM in slot 10) rconsole 1 10 tftp get 200.1.1.43:<Lmmddyy.pak> check pak <Lmmddyy.pak> exit 8) If there are any files listed with extension .BC, rename these files Example: rename scm.bc scmbc.Bxx 9) Create a backup of your current running config file copy config.txt config.Bxx 10) The Load of the 7510 should not exceed the allowed values to guarantee a hitless upgrade. (see [1] Release Notes). Check the Megaco Traffic Load Status of the 7510 on the MGC for the actually CAPS rate. Verify also on the 7510 using the MGEM. Check in the field MGW Load the actual CPU value and then press the 24h button to get the history. Both should not have exceeded the value of CPU 15% for the last hour. This value is correlated to a traffic mix with 30CAPS and 0.9 Erlang.
CPU24h view: check for the last hour
Current CPU load.
11/28
Alcatel-Lucent NGN
11) Prevent the syslog function from writing to a local file (e.g., aatlog.txt) with command: define syslog save mode none 12) Disable the CLI and SNMP logging functions with commands define cli log status disable define snmp log status disable 13) Enable task-switch during write prom/fpga to flash with command diag define upgrade system prom-fpga delay enable This will increase the upgrade time but prevents calls from failing during prom/fpga upgrade. NOTE: this command was only introduced in later R3.0 SW packages and may not be available in each gateway with R3.0 software. 14) Disable the H.248 overload control package and the capability change indication with commands define profile h248 capability default sc-capch disable define profile h248 package <profile-tag> overload-ctrl disable 15) Set the context non-emergency rejection thresholds with commands define profile h248 cor-thresh default start 90 define profile h248 cor-thresh default all 95 16) Assure overload calculation is done only on active cards with command diag define overload h248 calculation input active-cards 17) Arrange from N+1 to 1+1 for xIM and MCM define redundancy n-to-1 <minutes> From now on, no more calls will be established on standby-candidate slots. After the time defined in minutes these modules will be rebooted as standby modules, still existing calls will be released. 18) Execute following commands diag define upgrade system tftp-check disable diag define upgrade system check-pak disable diag define upgrade system ignore-file boot disable diag define h248 swup bulk-sync block-time 180 NOTE: The bulk synchronization block time should be chosen depending on the average call holding time. The value should be in the range from 180 to 300 seconds.
12/28
Alcatel-Lucent NGN 19) Save the configuration to make sure, the system is configured as 1+1 after reboot. When changing the configuration from N+1 to 1+1, the new configuration is not saved automatically (configuration is NEVER automatically saved in the 7510) save 20) Upgrade the system with command upgrade system hitless <Lmmddyy.pak> in case of a patch upgrade as described in chapter 6.1: upgrade system patch <Lmmddyy.pak> 21) Verify loaded software and prom version with command view version all Compare against the example from the Release Notes. Normally the produced SWPROM has the same Bxx name as the SW-PROM version. 22) Check software upgrade logging for reported problems on active and standby SCM with command cat swuplog.txt 23) Re-arrange from 1+1 to N+1 for xIM and MCM define redundancy 1-to-n 24) Save the configuration, to make the N+1 configuration reboot-save save 25) Check Alarms status of the 7510 with command view alarm active and compare with the Alarm status before the SW upgrade 26) If MGEM is used as an application of a management platform like, e.g., CMC, upgrade MGEM if applicable. In case MGEM and/or MGAM are used as standalone applications, the upgrade procedures are described in Media Gateway Element Manager User Guide (Chapter 2), Media Gateway Alarm Manager User Guide (Chapter 2)
13/28
Alcatel-Lucent NGN
7 Non-hitless Software Upgrade

A non-hitless software upgrade is applicable in case the actual configuration is not supported by hitless software upgrade. See the restrictions for hitless software upgrade in section 6.2.1. If there should be calls on the gateway during non-hitless software upgrade process, these calls will be lost.
7.1 Preparation
The steps in this section can be seen as optional steps. They depend on the network environment in which you are running the 7510 MG. The preparation steps might be covered already by a network management system as, e.g., the Alcatel-Lucent 1300 CMC. 1) Prepare an FTP client with IP connection to the OAM-port of the 7510 on an external host. 2) Get R3.0 Software as described in the [1] Release Notes
7.2 Starting the Upgrade

1) Check Variant and ICS of all boards and compare with released ICS from official Release Notes (Example: Variant=CAAA, ICS=02) For any differences or problems contact Alcatel-Lucent Support! 2) Check via UI command the FPGA versions of all boards while still running the old software. Compare with released FPGA versions in the official [1] Release Notes of the new to be installed software. For details see Appendix-A. view prom full all For any differences or problems contact Alcatel-Lucent Support! Upgrading with wrong FPGA, Variant or ICS can lead to damaged boards and system outages. 3) Check Alarms status of the 7510 with command view alarm active Gateway should be alarm free or only known problems/alarms should be reported
14/28
Alcatel-Lucent NGN 4) Check for the availability of a backup of current running config file. In case no backup exists, it is recommended to create one. copy config.txt config.Bxx
5) If there are any files listed with extension .BC, rename these files Example: ls *.bc rename scm.bc scmbc.Bxx 6) Check for the availability of the new software package on the flash card. In case it is not present transfer the new software file <Lmmddyy.pak> with an external FTP client or a management system, e.g. CMC, to the active SCM of the 7510 MG. When doing so it has to be ensured that the binary transfer mode is used. 7) Check the integrity of the software file with command check pak <Lmmddyy.pak> 8) Copy the new software and the config backup to the standby SCM with commands (assumed: standby SCM in slot 11) rconsole 1 11 tftp get 200.1.1.42:<Lmmddyy.pak> tftp get 200.1.1.42:config.Bxx check pak <Lmmddyy.pak> exit (assumed: standby SCM in slot 10) rconsole 1 10 tftp get 200.1.1.43:<Lmmddyy.pak> tftp get 200.1.1.43:config.Bxx check pak <Lmmddyy.pak> exit 9) Disable checks, diag define diag define diag define not needed, with following commands: upgrade system ignore-state enable upgrade system tftp-pak disable upgrade system check-pak disable
10) Upgrade the system with command (may take some minutes) upgrade system non-hitless <Lmmddyy.pak> 11) Verify loaded software and prom version with commands view chassis view vmg status view uptime all cat pf1:vinfo.txt view version all view prom full all Compare against the example from the Release Notes. Normally the produced SWPROM has the same Bxx name as the SW-PROM version.
15/28
Alcatel-Lucent NGN 12) Check software upgrade logging for reported problems on active and standby SCM with command cat swuplog.txt
13) Check Alarms status of the 7510 with command view alarm active and compare with the Alarm status before the SW upgrade. 14) Remember to keep alarms on the 7510 on a minimum and disable all unused card slots and rear I/O boards (MIM). Example: disable module gw.1.3.card & disable module gw.1.3.mim 15) If MGEM is used as an application of a management platform like, e.g., CMC, upgrade MGEM if applicable. In case MGEM and/or MGAM are used as standalone applications, the upgrade procedures are described in Media Gateway Element Manager User Guide (Chapter 2), Media Gateway Alarm Manager User Guide (Chapter 2)
16/28
Alcatel-Lucent NGN
8 Graceful Software Upgrade

8.1 SW-Upgrade Strategy

This section describes the general strategy that applies for a graceful SW-upgrade. It only covers the SW-upgrade within a major 7510 MG SW-release like Release 3.0. The procedure can be performed without the need for any onsite interventions, i.e. remote access to the 7510 MG is sufficient. The upgrade is performed by using the so called drain down procedure. Here a single chassis wide command is used which will drain traffic away from every VMG (virtual TGW or BGW instance) on the 7510 MG, i.e. existing calls will be maintained, but new calls will be rejected. The MGC will then redirect new calls to other Gateways. The execution of this command will result in a H.248 ServiceChange command being sent to the MGC for each and every active virtual TGW/BGW entity within the 7510 MG chassis. The operator may wait for the calls to be finished or he may issue a command to force the teardown of those calls. Hereafter the command for the SW-upgrade can be issued. There is no additional interaction needed to disable the drain-down procedure after the upgrade is finished. Dependent on the hardware configuration of the chassis, e.g. how many boards are equipped, the loading of the 7510 MG may last around 10 minutes. During this outage time the signaling gateway functionality as well as all provisioned semi-permanent connections will be down. It is assumed that the network configuration will provide a redundancy concept for the SGWs as well as for the SPCs, thus the impact on the network should be minimized. After the loading is finished, the 7510 MG will return to a full service state, including all the SGWs and all the SPCs that have been provisioned.
8.2 Precondition
This chapter describes the preconditions that must be fulfilled before the graceful SWupgrade can be executed. If any of these conditions is not fulfilled the SW-upgrade shall not be performed.
8.2.1 Login to the 7510 MG

The operator performing the SW-upgrade must be logged in to the command line interface of the 7510 MG where the SW-upgrade shall be performed. For this purpose a telnet or SSH session is sufficient. The user performing the upgrade procedure must have the system privileges System, Update, View and Code. A precondition for the further proceeding is that no VMG scope is set. If in doubt, the following command shall be used: define vmg scope none
17/28
Alcatel-Lucent NGN
8.2.2 Download of new SW-build (optional)

If the new software build has not been transferred yet to the gateway, it has to be done now.
8.2.2.1 Download PAK-file The new SW-build (PAK-file) must have been downloaded onto the flash disk of the active SCM. There are several options for that: On the 7510 MG get the PAK-file from an external TFTP server: tftp get <IP-address> <PAK-file> Transfer the file with an external FTP client to the 7510 MG. When doing so it has to be ensured that the binary transfer mode is used.
Note: The network management system might provide a convenient way for the last option. 8.2.2.2 Check integrity of the new SW-build After the file has been downloaded successfully, the integrity of the PAK-file shall be checked: check pak <PAK-File> scanning archive <PAK-file> for corruption ... computed checksum matches stored checksum (0x2faa0cc4 == 0x2faa0cc4) If the command reports a corruption of the PAK-file, then the SW-upgrade procedure shall not be continued. This case may happen if either the file was already corrupted prior to the file transfer to the 7510 MG, or if file transfer itself did not succeed. In any case, this problem needs to be solved by, e.g., repeating the file transfer.
8.2.3 Check state of all modules

All modules must be in the UP state before the SW-upgrade procedure can start. If one or more modules are not in the UP state, the SW-upgrade procedure shall not be started. Maintenance actions must be taken to bring all equipped system modules, which are enabled, in UP state. The state of all modules can be displayed with the following command:
18/28
Alcatel-Lucent NGN view chassis

--------------------------------------------------------------------------Ch Sl VB-Type VB-State VB-Admin VB-Function LBI VM-State VM-Admin --------------------------------------------------------------------------1 1 ENABLED VMCDA ENABLED 1 2 ENABLED VMCDA DISABLED 1 3 VBMCM3E UP ENABLED ACTIVE-MCM mcm1 VMCDA ENABLED 1 4 ENABLED DISABLED 1 5 ENABLED DISABLED 1 6 DISABLED DISABLED 1 7 DISABLED VM1GEM DISABLED 1 8 DISABLED VM1GEM DISABLED 1 9 VBSFM UP ENABLED ACTIVE-SFM sfm VMCDA ENABLED 1 10 VBSCM2 UP ENABLED ACTIVE-SCM * scm VMSCM ENABLED 1 11 VBSCM2 UP ENABLED STANDBY-SCM VMSCM ENABLED 1 12 VBSFM UP ENABLED STANDBY-SFM VMCDA ENABLED 1 13 DISABLED DISABLED 1 14 DISABLED DISABLED 1 15 ENABLED VMPIM DISABLED 1 16 ENABLED VMPIM ENABLED 1 17 VBPIxGES UP ENABLED ACTIVE-PIM pim1 VMPIM ENABLED 1 18 VBPIxGES UP ENABLED ACTIVE-PIM pim2 VMPIM ENABLED 1 19 VBPIxGES UP ENABLED ACTIVE-PIM pim3 VMPIM ENABLED 1 20 VBPIxGES UP ENABLED ACTIVE-PIM pim4 VMPIM ENABLED ---------------------------------------------------------------------------
8.2.4 Verify that there is only one login session

It has to be ensured that for the further proceeding no other users are connected to the 7510 MG, thus the following commands must be issued: view ui UI Sessions: # Type 0 SERIAL 1 RCON SERV 2 RCON SERV 3 RCON SERV 4 TELNET 5 TELNET 6 TELNET 7 TELNET 8 SSH 9 SSH 10 SSH 11 SSH
Active No No No No Yes Yes No No No No No No
Source N/A N/A N/A N/A 149.204.181.66:48393 172.24.224.32:1722 N/A N/A N/A N/A N/A N/A
User
user1 user2
clear ui <session nbr> For the example above it is assumed that the user user1 is used to perform the SWupgrade procedure, i.e., the session number 5 for the user user2 must be terminated.
8.2.5 Backup the configuration file

Create a copy of the configuration file config.txt. First, the current configuration must be saved to the flash disk:
19/28
Alcatel-Lucent NGN save Next, active and standby configuration for the SCM must be determined. This information can be retrieved from the system prompt. If the system prompt looks like VS-ET:ACT-SCM:1.10(r0)>=9:diag:main:vMGx# then the active SCM is located at slot 10. This means that the standby SCM is located in slot 11. In case the active SCM is located in slot 11, the prompt looks like VS-ET:ACT-SCM:1.11(r0)>=9:diag:main:vMGx# and the standby SCM is located in slot 10. Now a local backup copy of config.txt file shall be created: Copy the file on the active SCM: copy config.txt config.sav Copy the file on the standby SCM. For the commands given below it is assumed that the standby SCM is located in slot 11. rcon 1 11 copy config.txt config.sav exit Note: The backup file config.sav might already exist. In this case either another file name has to be chosen for the new backup file, or the existing backup file must be removed using the following command: remove config.sav
8.2.6 Increase verbosity

It is strongly recommended that from now on the save command is not executed anymore as it is intended that the following changes to the system are not reboot save. The operator is advised to enable the system logging. This step can be skipped if the system logging is already enabled. To check the systems logging configuration the following command must be issued: view syslog config System Log Settings ------------------Display Log Mode ..................... Enabled 20/28
Alcatel-Lucent NGN Priority ................. notice Save Log Mode ..................... Priority ................. File Name ................ Remote Host IP Address ... Remote Facility Name ..... None notice aatlog.txt 0.0.0.0 local0
Save UI command ..................... Disable If the system logging is not yet enabled the following commands must be issued: define ui syslog enable define syslog display priority warn define syslog save mode local With the commands specified above the system logs will be displayed on the console, and additionally they are stored in the file AATLOG.TXT.
8.3 SW-Upgrade Procedure

Before the SW-upgrade procedure is executed, it has to be ensured that the preconditions of chapter 8.2 are fulfilled. In case any of the conditions described there are not fulfilled the SW-upgrade procedure shall not be executed. To execute the SW-upgrade procedure the following actions need to be taken step by step:
8.3.1 Start the drain down procedure

As described in chapter 6 the drain down procedure must be started with the following command: define system traffic-drain start 0 never This command results in sending a H.248 ServiceChange command to the MGC for each active VMG instance within the 7510 MG chassis. The ServiceChange commands will instruct the MGC not to create new call contexts, but existing call contexts are not affected, i.e., stable calls will not be released, neither by the MGC nor by the 7510 MG. The MGC will then redirect new calls to other gateways. The drain down procedure can be cancelled by issuing the following command: define system traffic-drain cancel For each instance of VMG in the 7510 MG this command causes a H.248 ServiceChange command to be sent to the MGC to allow new context creation requests. At any time of the drain down procedure the operator can display the number of contexts that are still active in the 7510 MG by issuing the following command: view system traffic-drain statistics
Traffic-drain status is: Stopped
21/28
Alcatel-Lucent NGN
Traffic-drain duration Proceed level is Delay time is Query interval is Register interval is : : : : : None None None 60 sec 1 sec
Emergency calls : 0 Non-emergency calls : 0 Index VMG ID EmergencyCall 1 vmg1 0 2 vmg2 0 3 vmg3 0
Non-emergencyCall 0 0 0
TrafficDrain Status Stopped Stopped Stopped
8.3.2 Release remaining active call contexts

With the information provided by the previous command the operator can decide when to continue with the procedure by releasing the existing call contexts. In case there are contexts still active and the operator decides to continue with the SW-upgrade procedure, then the existing call contexts will be aborted immediately. At any time the command described above can be used to get more information about the number of active contexts. To force the teardown of the active contexts the following command has to be issued: define system traffic-drain state disable-all This will clear all active contexts in the 7510 MG regardless of whether they are emergency contexts or not, and for each VMG instance the association to the MGC will be closed. Each VMG will be disabled. If for any reason the SW-upgrade procedure shall be aborted in this state, then the following command can be used to establish the association between each instance of a VMG and its corresponding MGC: define system traffic-drain state enable-all
8.3.3 Activate the SW-Upgrade command

To initiate the SW-upgrade in the system the following command must be issued: upgrade system non-hitless <PAK-file> This command starts the automatic upgrade process by exploding the new PAK-file and extracting the new runtime and boot PROM software. The PAK-file will be automatically copied to the flash disk of the standby SCM. The upgrade process takes a few minutes. No input shall be provided while the upgrade is proceeding.
22/28
Alcatel-Lucent NGN If an error is encountered during the execution of the command the automatic upgrade procedure halts and a fallback to the previous software version is triggered autonomously. In this case the following actions should be taken: Check the syslog messages for any information about error conditions (file AATLOG.TXT) Check the software upgrade log-file named SWUPLOG.TXT. If further assistance is required, the Customer Support must be contacted. After the command is successful finished, the 7510 MG is in a full functional state. The 7510 MG autonomously starts the setup of the associations between each instance of VMG and the related MGC, and new call context attempts from the MGC are accepted. Also, each created SGW as well as each provisioned SPC will be in service again.
8.3.4 Check new software configuration

1) Verify loaded software and prom version with commands view version all view prom full all Compare against the example from the Release Notes. Normally the produced SWPROM has the same Bxx name as the SW-PROM version. 2) Check software upgrade logging for reported problems on active and standby SCM with command cat swuplog.txt
23/28
Alcatel-Lucent NGN
Appendix-A:
FPGA/Boot/PROM check
Check FPGA versions of all boards via command and compare with released FPGA versions from official Release Notes. NOTES: there are total three type of images in flash in each boards: Boot: refer the different BootROM, there three type of BOOT exist o SCMBoot, BootROM used for SCM1 boards o SCM2Boot, BootROM used for SCM2 boards o PIM2Boot, BootROM used for PIM2 boards o RM7-Boot, used for other boards, including CIM, SFM, MCM, PIM1 PROM: it is same for all the boards. FPGA: other image except the aboves are called FPGA, including CMM, CMT, SBI, TDM, PAC, ASR, DSP firmware, NPU image etc.
the following command view prom full all shows all the FPGA/Boot/PROM on all slots. A7510:rem-cons:ACT-CIM:1.1(r0)>=3:sduc:main# view prom full all Entities in the CURRENT directory of the bootflash! Module (1, 1) LBI : cim Version of FPGA-CMT SW..... v3_rev6 Version of FPGA-SBIB SW.... v1_rev4 Version of SW-PROM......... A7510_R30 prom 08Jan08 11:54:56 Entities in the PREVIOUS directory of the bootflash! Module (1, 1) LBI : cim Version of FPGA-CMT SW..... v3_rev6 Version of FPGA-SBIB SW.... v1_rev4 Version of SW-PROM......... A7510_R30 prom 07Jan08 12:23:29 Entities in the ORIGIN directory of the bootflash! Module (1, 1) LBI : cim Version of FW-Boot SW...... v2_rev8 Version of FPGA-CMT SW..... v1_rev5 Version of FPGA-SBIB SW.... v1_rev4 ... /* following are the output for other slots */
The following command diag view packages shows the Boot/PROM/FPGA section rules: A7510:rem-cons:ACT-CIM:1.1(r0)>=3:sduc:main# diag view packages Package Firmware selected : ORIGIN Package Selected : CURRENT Package Launched : CURRENT Package CURRENT on directory : DIR1 Package PREVIOUS on directory : DIR2 Directory DIR1 is OK 24/28
Alcatel-Lucent NGN Directory DIR2 is OK
The following are the rule how system use select different images in current, previous and original directory.
Boot Selection
Boot selection is controlled by following: Package Firmware selected : ORIGIN

The rule of FW_BOOT choice is: 1. If the firmware selector points to CURRENT DIR { If there is FW_BOOTin CURRENT DIR The FW_BOOTin CURRENT DIR is loaded. Else If there is FW_BOOTin PREVIOUS DIR The FW_BOOTin PREVIOUS DIR is loaded. Else The FW_BOOTin ORIGIN DIR is loaded. } 2. If the firmware selector points to PREVIOUS DIR { If there is FW_BOOTin PREVIOUS DIR The FW_BOOTin PREVIOUS DIR is loaded. Else The FW_BOOTin ORIGIN DIR is loaded. } 3. If the firmware selector points to ORIGIN DIR { The FW_BOOTin ORIGIN DIR is loaded. } If want to change the selector, then can use the following command: diag define firmware package current/previous
PROM/FPGA use the same control flag: Package Selected : CURRENT */ Package Launched : CURRENT
PROM/FPGA Selection
/* define where to load PROM/FPGA /* show where is loading actual */
The rule of PROM/FPGA choice is: 1. If the package selector points to CURRENT DIR { If there is PROM/FPGA in CURRENT DIR The PROM/FPGA in CURRENT DIR is loaded.
25/28
Alcatel-Lucent NGN
Else If there is PROM/FPGA in PREVIOUS DIR The PROM/FPGA in PREVIOUS DIR is loaded. Else The PROM/FPGA in ORIGIN DIR is loaded. } 2. If the package selector points to PREVIOUS DIR { If there is PROM/FPGA in PREVIOUS DIR The PROM/FPGA in PREVIOUS DIR is loaded. Else The PROM/FPGA in ORIGIN DIR is loaded. } 3. If the package selector points to ORIGIN DIR { The PROM/FPGA in ORIGIN DIR is loaded. } If want to change the selector, then can use the following command: diag define package current/previous Normally the Package Selected and Package Launched should be same.
For the above example, the actual running image version should be: FW-Boot SW...... v2_rev8 FPGA-CMT SW..... v3_rev6 FPGA-SBIB SW.... v1_rev4 SW-PROM......... A7510_ R30 prom 07Jan08 12:23:29 Verifying rules: Rule-1: If there is in CURRENT or PREVIOUS directory an entity FW_FAULT present it has to be removed. Because of the big size of FW_FAULT there may be space problems when trying to write another entity into this directory. Remove FW_FAULT with following command:
diag remove prom entity (dir1/dir2) fw_fault Rule-2: FW-Boot involve two parts, the first part is hard coded, always taken from DIR0
(Origin), while the second part is taken from the Package Firmware selected
Rule-3: FPGA-xxxx can be taken from DIR0, DIR1 or DIR2; SW-PROM is always taken from
DIR1 or DIR2.To chose DIR1 or DIR2 is controlled by Package Selected
26/28
Alcatel-Lucent NGN
Appendix-B:
TI-MCM Firmware Boot and FPGA upgrade
Before the upgrade the boot, use the method included in Appendix-A to verify the Boot/FPGA versions The correct boot version should be: Version of FW-Boot SW...... A7510_R3.0 RM7-Boot v3_rev1 or Version of FW-Boot SW...... v3_rev1 The correct FPGA CMT version should be: Version of FPGA-CMT SW..... A7510_R3.0 fmcm2cmt v1_rev3 or Version of FPGA-CMT SW..... v1_rev3
The Boot/FPGA version in original directory is not correct In this case, should do Boot upgrade has to be done. This is only allowed for an Alcatel-Lucent technical specialist, because incorrect upgrades can damage the hardware and may require replacement of the board. VBMCMxE with inconsistent Boot and FPGA come to idle state but will not get available MCP resources.
1) Following procedure has to be executed on active SCM in slot 10: define nvram pf <runing.pak> <newpak.pak>
<running.pak> is the package which system currently running package, you can use view nvram to get <newpak.pak> is the package you want to upgrade.
2) Following procedure has to be executed on all MCM boards: rcon 1 x with x = slot of MCM upgrade image current fw_boot 200.1.1.42:pf2:RM7-Boot.img upgrade image current fpga_cmt 200.1.1.42:pf2:fmcm2cmt.img upgrade image previous fw_boot 200.1.1.42:pf2:RM7-Boot.img upgrade image previous fpga_cmt 200.1.1.42:pf2:fmcm2cmt.img upgrade prom previous 200.1.1.42:pf2:prom.img upgrade prom current 200.1.1.42:pf2:prom.img diag define firmware package current diag define package current
exit
In case of Boot/FPGA version upgrade, above UI command also upgrade the PROM to make sure the actual SW-PROM is as well in the CURRENT directory. Avoid package and firmware selectors pointing to different directories.
3) Following procedure has to be executed on active SCM in slot 10: (Run this command on active SCM) reset module 1 x with x = slot of MCM 27/28
Alcatel-Lucent NGN
Need to wait until the reset MCM is in standby status, then reset the next MCM module. Repeat the reset command for all MCM modules.
28/28

7510 MGW Software Upgrade Customer Manual

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

7510 MGW Software Upgrade Customer Manual

Diunggah oleh

Hak Cipta:

Format Tersedia

All rights reserved.

Next Generation Network Product Group Gateway Project: A7510 R3.0

7510 MGW Software Upgrade Customer Manual

2009-12-04 2008-11-19 Date

Document revised Initial version Change Note Appraisal Authority

Rainer Bussmann Jens Guballa Author

Document based on Template 3FZ-01762-0001-PTZZA ED NGN 02 Draft 3FZ-08118-AAAA-TNZZA

Date 2008-11-24 2009-09-01 2009-12-02

Version Ed01P01 Ed01P02 Ed02P01

Author Jens Guballa Rainer Bussmann Rainer Bussmann

[1]. [2]. [3]. [4]. [5]. [6]. [7]. [8]. [9].

4.1 Product group and release applicability

Normal fixed font Italic fixed font Angle brackets <>

IP Gateway Cache Entries: 0 config.txt

check pak <filename>

6 Hitless Software Upgrade

6.1 Patch Upgrade from R3.0 Bxx to R3.0 Byy

6.2.3 Starting the Upgrade

CPU24h view: check for the last hour

Current CPU load.

7 Non-hitless Software Upgrade

7.2 Starting the Upgrade

8 Graceful Software Upgrade

8.1 SW-Upgrade Strategy

8.2.1 Login to the 7510 MG

8.2.2 Download of new SW-build (optional)

8.2.3 Check state of all modules

Alcatel-Lucent NGN view chassis

8.2.4 Verify that there is only one login session

Active No No No No Yes Yes No No No No No No

8.2.5 Backup the configuration file

8.2.6 Increase verbosity

8.3 SW-Upgrade Procedure

8.3.1 Start the drain down procedure

TrafficDrain Status Stopped Stopped Stopped

8.3.2 Release remaining active call contexts

8.3.3 Activate the SW-Upgrade command

8.3.4 Check new software configuration

Alcatel-Lucent NGN Directory DIR2 is OK

Boot selection is controlled by following: Package Firmware selected : ORIGIN

TI-MCM Firmware Boot and FPGA upgrade

Anda mungkin juga menyukai