31NUP0031 7470 Rel 5

31NUP0031
Version 2.0 (Issued) 14 July 2004
Alcatel 7470 Multi-Service Platform Release 5.0 Upgrade Procedure
Network Upgrade Procedure

Authored by 3LS TEC, IPD Services and Support
ABSTRACT: This document introduces the new hardware and software features delivered in Release 5.0 of the 7470 Multi-Service Platform, and provides detailed information about the various upgrade procedures that may be performed when upgrading an Alcatel 7470 Multi-Service Platform from Release 4.2 or 4.3 to Release 5.0.
Issued
Alcatel 7470 Multi-Service Platform Release 5.0 Network Upgrade Procedure Version 2.0 (Issued)
31NUP0031 7/19/2004
Table Of Contents
1. INTRODUCTION............................................................................................................................................. 1 1.1. OVERVIEW.................................................................................................................................................. 1 1.1.1. Upgrade the Control Complex.............................................................................................................. 1 1.1.2. Upgrade the Fabric Cards.................................................................................................................... 3 1.1.3 Upgrade the Service Cards ................................................................................................................... 4 1.1.4. Upgrade the IP Service Cards (ISC)..................................................................................................... 5 1.1.5. Upgrade the Line Cards........................................................................................................................ 6 1.1.6. Fabric Size Upgrade to 32k Cells ......................................................................................................... 8 1.1.7. Optional Control Mode Conversion...................................................................................................... 9 1.2. NEW HARDWARE INTRODUCED IN REL 5.0............................................................................................... 10 1.2.1 The 4-port OC3/STM1 Cell Relay Card.............................................................................................. 10 1.2.2 The 8-port DS3 Cell Relay Card......................................................................................................... 11 1.3 NEW FEATURES INTRODUCED IN REL 5.0 ................................................................................................. 11 1.3.1 CPSS Scalability ................................................................................................................................. 11 1.3.2 Improved Auto-Reconcile.................................................................................................................... 11 1.3.3 ILMI 4.0 Support................................................................................................................................. 12 1.3.4 Integrated CallP/PNNI/Data Spooling ............................................................................................... 12 1.3.5 Configurable Individual Alarm Severity ............................................................................................. 12 1.3.6 Increased Scalability of Address Translation ..................................................................................... 12 1.3.7 Connection Enhancements.................................................................................................................. 13 1.3.8 Switched Services VBNs...................................................................................................................... 13 1.3.9 PNNI Diagnostic Improvements ......................................................................................................... 13 1.3.10 Default Fabric Type Change From 2k to 32k ................................................................................ 13 1.3.11 NMS Support for Static Routing Tables ......................................................................................... 14 1.3.12 4.5k connection support for DS3-2/E3-2 CR with eTM.................................................................. 14 1.3.13 RTD Measurement on Cell Relay Cards ........................................................................................ 14 1.3.14 RTD Measurement on Frame Relay Cards .................................................................................... 14 1.3.15 Dynamic Channel Selection over ISLs ........................................................................................... 14 1.3.16 Multi-Port Ethernet VLAN Support................................................................................................ 14 1.3.17 Multi-Port Ethernet VC-VC Forwarding Support.......................................................................... 15 1.3.18 In-band IP Support for Spooling .................................................................................................... 15 1.3.19 Inband IP Using SPVCs ................................................................................................................. 15 1.4. SYSTEM REQUIREMENTS OF RELEASE 5.0 FEATURES ............................................................................... 15 1.5. NETWORK MANAGEMENT (5620) SUPPORT.............................................................................................. 17 1.6. IMPORTANT POINTS VITAL TO THE REL 5.0 UPGRADE.............................................................................. 17 2. 3. UPGRADE OVERVIEW ............................................................................................................................... 19 CONTROL COMPLEX UPGRADE............................................................................................................. 20 3.1. UPGRADE THE CONTROL COMPLEX (SIMPLEX) ........................................................................................ 20 3.1.1. Download the Application S/W Generic ............................................................................................. 20 3.1.2. Record the System Parameters and Backup the Database.................................................................. 20 3.1.3. Set the Next Bank and Reset the Card (with an Optional ePM Upgrade)........................................... 21 3.1.4. Re-Configure the Control Complex .................................................................................................... 21 3.1.5 Restore the System Database .............................................................................................................. 21 3.2. UPGRADE CONTROL COMPLEX (REDUNDANT) ......................................................................................... 21 3.2.1. Download the Application Software ................................................................................................... 21 3.2.2. Record the System Parameters and Backup the Database.................................................................. 21 3.2.3. Confirm Demerits on the Control Complex ........................................................................................ 22
3LS TEC IPD Services & Support
Issued
iii
31NUP0031 7/19/2004
3.2.4. 3.2.5. 3.2.6. 3.2.7. 3.2.8. 3.2.9. 4.
Set the Next Bank and Reset the Inactive Control Card (with an Optional ePM Upgrade) ............... 22 Verify Demerits ................................................................................................................................... 22 Release Control to the Newly Upgraded Control Card ...................................................................... 22 Set the Next Bank and Reset the Newly Inactive Control Card (with an optional ePM Upgrade) ..... 23 Verify Demerits ................................................................................................................................... 23 Release Control to the Former Active and Newly Upgraded Inactive Control Card ......................... 24
FABRIC UPGRADE....................................................................................................................................... 25 4.1. FABRIC UPGRADE FOR A STANDALONE SWITCH WITH SIMPLEX FABRIC .................................................. 26 4.1.1. Download the Application S/W Generic ............................................................................................. 26 4.1.2. Set the Next Bank and Reset the SHUB............................................................................................... 26 4.2. FABRIC UPGRADE FOR A STANDALONE SWITCH WITH REDUNDANT FABRIC ............................................ 27 4.2.1. Download the Application S/W Generic ............................................................................................. 27 4.2.2. Set the Next Bank and Reset the Inactive Y SHUB.............................................................................. 27 4.2.3. Perform a Fabric Activity Switch to Y ................................................................................................ 28 4.2.4. Set the Next Bank and Reset the Inactive X SHUB ............................................................................. 28 4.2.5. Perform a Fabric Activity Switch back to X........................................................................................ 29 4.3 FABRIC UPGRADE FOR A MULTI-SHELF SWITCH WITH SIMPLEX FABRIC .................................................. 29 4.3.1. Download the Application S/W Generic ............................................................................................. 29 4.3.2. Set the Next Bank and Reset the Fabric Cards ................................................................................... 29 4.3.3. Confirm Proper S/W and Fabric Health ............................................................................................. 30 4.4. FABRIC UPGRADE FOR A MULTI-SHELF SWITCH WITH REDUNDANT FABRIC ........................................... 31 4.4.1. Download the Application S/W Generic ............................................................................................. 31 4.4.2. Set the Next Bank and Reset the Inactive Y Fabric ............................................................................. 31 4.4.3. Confirm Proper S/W and Fabric Health ............................................................................................. 32 4.4.4. Perform a Fabric Activity Switch to Y ................................................................................................ 33 4.4.5. Set the Next Bank and Reset the Inactive X Fabric............................................................................. 33 4.4.6. Confirm Proper S/W and Fabric Health ............................................................................................. 34 4.4.7. Perform a Fabric Activity Switch back to X........................................................................................ 34
5.
THE SERVICE CARD UPGRADE .............................................................................................................. 35 5.1. UPGRADE THE CALL PROCESSING CARDS (SIMPLEX) ............................................................................... 35 5.1.1. Download the Application S/W Generic ............................................................................................. 35 5.1.2. Confirm the Status of the Card ........................................................................................................... 36 5.1.3. Set the Next Bank and Reset the Card (with an optional ePM Upgrade) ........................................... 36 5.1.4. Confirm the Status of the Card ........................................................................................................... 36 5.2. UPGRADE THE CALL PROCESSING CARDS (1+1 HOT REDUNDANCY) ...................................................... 36 5.2.1. Download the Application S/W Generic ............................................................................................. 37 5.2.2. Confirm the Status of the Cards.......................................................................................................... 37 5.2.3. Set the Next Bank and Reset the Inactive Card (with an optional ePM Upgrade).............................. 37 5.2.4. Re-Confirm the Status of the Cards .................................................................................................... 37 5.2.5. Set the Next Bank and Reset the Active Card (with an optional ePM Upgrade)................................. 38 5.2.6. Final Confirmation of the Status of the Cards .................................................................................... 38 5.3. UPGRADE THE DATA SPOOLING CARD (SIMPLEX).................................................................................... 38 5.3.1. Download the Application S/W Generic ............................................................................................. 38 5.3.2. Confirm the Status of the Card, the Data Collector Links, and the Spooled Records in the Current Interval 39 5.3.3. Set the Next Bank and Reset the Card (with an optional ePM Upgrade) ........................................... 39 5.3.4. Re-Confirm the Status of the Card, the Data Collector Links, and the Spooled Records in the Current Interval 39 5.4. UPGRADE THE DATA SPOOLING CARD (REDUNDANT).............................................................................. 40 5.4.1. Download the Application S/W Generic ............................................................................................. 40
Issued
iv
31NUP0031 7/19/2004
5.4.2. Confirm the Status of the Cards, the Data Collector Links, and the Spooled Records in the Current Interval 40 5.4.3. Set the Next Bank and Reset the Inactive Card (with an optional ePM Upgrade).............................. 40 5.4.4. Re-Confirm the Status of the Card, the Data Collector Links, and the Spooled Records in the Current Interval 41 5.4.5. Set the Next Bank and Reset the Active Card (with an optional ePM Upgrade)................................. 41 5.3.6. Final Confirmation of the Status of the Card, and the Data Collector Links ..................................... 41 5.5. UPGRADE THE PNNI CARD (SIMPLEX) ..................................................................................................... 42 5.5.1. Download the Application S/W Generic ............................................................................................. 42 5.5.2. Confirm the Status of the Card ........................................................................................................... 42 5.5.3. Set the Next Bank and Reset the Card (with an optional ePM Upgrade) ........................................... 42 5.5.4. Confirm the Status of the Card ........................................................................................................... 42 5.6. UPGRADE THE PNNI CARD (1+1 WARM REDUNDANT) ............................................................................ 43 5.6.1. Download the Application S/W Generic ............................................................................................. 43 5.6.2. Confirm the Status of the Cards.......................................................................................................... 43 5.6.3. Set the Next Bank and Reset the Inactive Card (with an optional ePM Upgrade).............................. 43 5.6.4. Re-Confirm the Status of the Cards .................................................................................................... 43 5.6.5. Set the Next Bank and Reset the Active Card (with an optional ePM Upgrade)................................. 44 5.6.6. Final Confirmation the Status of the Cards ........................................................................................ 44 6. THE IP SERVICES CARD (ISC) UPGRADE ............................................................................................. 45 6.1. UPGRADE THE ISC (SIMPLEX) .................................................................................................................. 45 6.1.1. Download the Application S/W Generic ............................................................................................. 45 6.1.2. Backup the Current Config File on the ISC ........................................................................................ 45 6.1.3. Confirm the Status of the Card ........................................................................................................... 45 6.1.4. Set the Next Bank and Reset the ISC................................................................................................... 46 6.1.5. Re-Confirm the Status of the ISC ........................................................................................................ 46 6.2. UPGRADE THE ISC (REDUNDANT)............................................................................................................ 46 6.2.1. Download the Application S/W Generic ............................................................................................. 46 6.2.2. Backup the Current Config File on the ISC ........................................................................................ 46 6.2.3. Confirm the Status of the Cards.......................................................................................................... 46 6.2.4. Set the Next Bank and Reset the Inactive ISC ..................................................................................... 47 6.2.5. Re-Confirm the Status of the Cards .................................................................................................... 47 6.2.6. Set the Next Bank and Reset the Active ISC ........................................................................................ 47 6.2.7. Final Confirmation of the Status of the Cards .................................................................................... 47 7. THE LINE CARD UPGRADE PROCEDURE ............................................................................................ 48 7.1. GENERAL LINE CARD UPGRADE............................................................................................................... 48 7.1.1. Download the Application S/W Generic ............................................................................................. 48 7.1.2. Confirm the Status of the Card ........................................................................................................... 48 7.1.3. Set the Next Bank and Reset the Line card ......................................................................................... 48 7.1.4. Re-Confirm the Status of the Card ...................................................................................................... 49 7.2. LINE CARD VERSION -2 UPGRADE ........................................................................................................ 49 7.2.1. Replace the Existing Line Card with the New -2 Version of the Card............................................ 49 7.2.2. Re-Confirm the Status of the Card and Configure Version -2 of the Card..................................... 49 7.3 APS LINE CARD UPGRADE ....................................................................................................................... 50 8. 9. UPGRADING TO 32K FABRIC ................................................................................................................... 51 CONTROL MODE CONVERSION ............................................................................................................. 52 9.1. CONVERTING FROM NON-INTEGRATED CONTROL MODE TO INTEGRATED CONTROL MODE ................... 52 9.1.1 Download the Application S/W to the Inactive Banks......................................................................... 52 9.1.2. Set the Control Mode to Integrated..................................................................................................... 52
Issued
31NUP0031 7/19/2004
9.1.3.
Integrated Control Mode Conversion Implications ............................................................................ 53
APPENDIX A: DOWNLOADING THE APPLICATION S/W GENERICS...................................................... 54 A.1. RELEASE 5.0 APPLICATION SOFTWARE & BOOTPROM FIRMWARE GENERICS .......................................... 54 A.2. APPLICATION S/W GENERIC DOWNLOAD PROCEDURE............................................................................. 55 A.2.1. Specify the IP or CPSS Address .......................................................................................................... 55 A.2.2. Specify the User Name ........................................................................................................................ 55 A.2.3. Specify the Users Password............................................................................................................... 55 A.2.4. Specify Path to the Location of the Application S/W Generic............................................................. 55 A.2.5. Specify the Name of the Application S/W Generic .............................................................................. 56 A.2.6. Download the Application S/W Generic to the Inactive S/W Bank ..................................................... 56 APPENDIX B: RECORD CONFIGURATION PARAMETERS AND BACKUP THE SWITCHS DATABASE .............................................................................................................................................................. 58 B.1. RECORD THE CONFIGURATION PARAMETERS OF THE SWITCH .................................................................. 58 B.2. BACKUP/RESTORE THE SWITCHS DATABASE .......................................................................................... 58 B.2.1. Specify the IP or CPSS Address .......................................................................................................... 58 B.2.2. Specify the User Name ........................................................................................................................ 59 B.2.3. Specify the Users Password............................................................................................................... 59 B.2.4. Specify Path to the Location ............................................................................................................... 59 B.2.5. Specify the File Name ......................................................................................................................... 59 B.2.6. To Backup the Switchs Database....................................................................................................... 59 B.2.7. To Restore the Switchs Database ...................................................................................................... 60 B.3. SET THE NEXT BANK AND RESET THE CARD ............................................................................................ 60 B.3.1. Set the Next Bank on the Card ............................................................................................................ 60 B.3.2. Replace the PM with the ePM (Optional) ........................................................................................... 61 B.3.3. Reset the Card to Make the Next Bank Current.............................................................................. 61 B.3.4. Confirm the Application Software was Downloaded Correctly. ......................................................... 61 B.4 RE-CONFIGURE THE SWITCHS SYSTEM PARAMETERS (SIMPLEX ONLY) ................................................. 62 B.4.1 Re-configure the IP/CPSS Parameters ............................................................................................... 62 B.4.2. Reset the Control Card ....................................................................................................................... 62 B.4.3. Re-Configure the Fabric Type ............................................................................................................ 62 B.4.4. Re-Configure the Switchs Peripheral Shelves ................................................................................... 63 B.4.5. Re-Configure all UCS Slots and Connect CPSS ................................................................................. 64 APPENDIX C: NODAL DOWNGRADE PROCEDURE..................................................................................... 65 C.1 INTERFACE CARD DOWNGRADE PROCEDURE ................................................................................................... 65 C.2 FABRIC CARD DOWNGRADE PROCEDURE......................................................................................................... 66 C.2.1 Multi-Shelf Redundant Fabric Downgrade Procedure............................................................................ 66 C.2.2 Standalone Redundant Fabric Downgrade Procedure............................................................................ 68 C.3 CONTROL CARD DOWNGRADE PROCEDURE (WITH BACKUP CONTROL CARD) ................................................. 69 C.3.1 CONTROL CARD DOWNGRADE PROCEDURE WITH NO BACKUP CONTROL CARD ............................................ 70 APPENDIX D: REFERENCES............................................................................................................................... 72
Issued
vi
31NUP0031 7/19/2004
1. Introduction
1.1. Overview
This document describes how to upgrade an Alcatel 7470 Multi-Service Platform to Release 5.0, from a software base of either Release 4.2 or Release 4.3. If the base release is earlier than Release 4.2, please refer to the document 31NUP0022 which details the Release 4.2 upgrade procedure, or 31NUP0026 which details the Release 4.3 upgrade procedure. Once the 7470 switch has been upgraded to either Rel 4.2 or Rel 4.3, then this document can be used to upgrade the switch to Rel 5.0. An upgrade of a Rel 4.2 or Rel 4.3 7470 system consists of the following six mandatory components and one optional upgrade component.
1.1.1.
Upgrade the Control Complex
Description The control complex contains the database of the switch. The database stores the configuration and all of the programmed connections of the system. It is the most important and complex part of the upgrade procedure. Upgrade Implications and Service Impact The control complex upgrade usually involves redundant (active and inactive) Control cards that work together, to ensure there are minimal service impacts when upgraded as a pair. The Control cards always reside in slots 1 and 2 of Peripheral Shelf 1. A simplex control complex upgrade will incur a service outage and will require a database restoration. If the Control Mode of the switch changes from Non-integrated to Integrated (or the opposite), then there will be a service outage caused by the deestablishing and re-establishing of all PVC and SPVC connections. All existing SVC connections are removed and will need to be re-established. Minimum Hardware Required As a pre-requisite, Rel 5.0 requires the Control cards to be of the Enhanced Processing Engine Card (EPEC) variety, also known as Control-2 Cards. This is also a pre-requisite for Rel 4.2 and Rel 4.3 so there will be no need for Control card hardware replacement.
Issued
31NUP0031 7/19/2004
Error Detection and Correction (EDC) Consideration Required Error detection and correction (EDC) functionality is being introduced into release 4.3, 5.0 and future 7470 releases. This new functionality will detect and correct database corruption on the Control Card. EDC is scheduled to be available in the 7470 release 4.3HLS6V2 and 5.0 HLS4V2. Individuals should check product release notices to determine if EDC needs to be considered during upgrade planning. The following describes any issues relating to upgrading where EDC is involved: Upgrade from Non-EDC load to EDC load No issue Upgrading from EDC load to Non-EDC load There will be no upgrade path from a node running a software load with EDC functionality to a 5.0 load that does not support EDC. Upgrading from EDC load to EDC load EDC is being turned on slowly where the first releases containing EDC will have correction disabled by default. It is important to note, when upgrading from a load that has EDC with correction disabled to a load that has correction enabled by default, that correction will not automatically be enabled after the upgrade.
New in Release 5.0
With the introduction of Rel 4.2, there were no additional hardware components made available for the Control-2 cards. With the introduction of Rel 4.3 came an optional Control-2 card processing module upgrade, consisting of a new module called the Enhanced Processor Module (ePM), which replaces the old Processing Module (PM). Additionally, a new 256MB PCMCIA flash disk card was introduced in Rel 4.3. It is mandatory that the new flash disk be simultaneously installed with the new ePM module, as in future releases that allow increased numbers of connections on the switch and require increased database storage capacity, the new flash card will be required. If the 7470 system is to be used in integrated control mode in Rel 5.0, the new ePM module and flash card is MANDATORY.
Issued
31NUP0031 7/19/2004
If the 7470 system is to be used in non-integrated control mode, the new ePM module and flash disk are OPTIONAL, but strongly recommended for performance reasons. The product part number of the ePM and PCMCIA flash disk upgrade package is 908477-02. With the introduction of Rel 5.0, also comes the ability to have a Control-2 card operating in an Integrated control mode (CallP/PNNI) to assume the additional responsibilities of the Data Spooling Service card. This transition involves the installation of a secondary 6MB PCMCIA card on the Control-2 card. If the intent is to migrate from an integrated control mode PM-based Control card (Rel 4.2 or Rel 4.3) to an integrated control mode ePM-based Control card with 256MB flash disk and data spooling capability (Rel 5.0), the product part number of this complete upgrade package is 90-8977-01. If the intent is to merely add data spooling capability to an integrated control mode ePMbased Control card with 256MB flash disk (Rel 5.0), the data spooling upgrade package is 90-8977-02. If a non-integrated to integrated control mode conversion is desired in Rel 5.0, a password must be entered to allow this conversion to take place. The product part number of the non-integrated to integrated control mode conversion package is 90-9160-21. The above information will be incorporated into the various Control card upgrade scenarios, contained in later sections of this document.
1.1.2.
Upgrade the Fabric Cards
Description The fabric complex represents the freeway of the switch and is a means of sending (switching) ATM cells quickly and efficiently from one endpoint to another. Upgrade Implications and Service Impact Each 7470 system typically has redundant X and Y fabric complexes. On a peripheral shelf (PU), the X or Y fabrics is represented by DHUB, SHUB, and LSHUB cards and on a switching shelf (SU) the X and Y fabrics are represented by DSC and DRX cards. With fabric redundancy, the fabric complex can be upgraded without any service impacts. Without fabric redundancy, there will be a service impact to all connections crossing a fabric card until such time as the card finishes resetting and returns to service.
Issued
31NUP0031 7/19/2004
Minimum Hardware Required With the introduction of Rel 5.0, several types of fabric cards have been discontinued (Diablo-based HUB and DSC cards). The Rel 5.0 7470 system will now only support Eagle-based HUB cards and NSX-based DSC cards. All other types of fabric cards can no longer be present in the system. The reason for the discontinuance of the above fabric cards is that Rel 5.0 of the 7470 system will only operate with a fabric size of 32k cells. It is NOT possible to perform a 32k-cell size fabric conversion in Rel 5.0. All Rel 4.2 and Rel 4.3 systems with older hardware and/or a fabric size of 32k cells MUST have their older hardware replaced and be converted to 32k cell mode, BEFORE attempting to upgrade those systems to Rel 5.0. New In Rel 5.0 There is nothing new to Rel 5.0 in terms of the fabric complex.
1.1.3
Upgrade the Service Cards
Description The Service Complex comprises cards that provide specialized services such as Switched Services (Call Processing), Call Routing (PNNI), and Statistic Collection (Data Spooling). Upgrade Implications and Service Impact All Service cards can be configured for either Simplex or 1+1 APS modes of operation. When upgrading using 1+1 APS there should be no service impact, other than the clearing of frame relay SVCs and N-ISDN SVCs when upgrading the Call Processing cards. When in simplex mode there WILL be service impacts when the card is reset. When upgrading simplex Call Processing (CallP) cards, all SPVCs and SVCs will be cleared and only the SPVCs will be re-established once the card re-initializes. When upgrading simplex PNNI cards, there will be an inability to route new switched calls until the card re-initializes. Furthermore, SPVCs and SVCs may also be torn down depending on network conditions, of which only the SPVCs will be re-established when the card re-initializes.
Issued
31NUP0031 7/19/2004
When upgrading Simplex Data Spooling cards, all existing spooled data will be lost and no new data will be spooled until the card re-initializes. Minimum Hardware Required Similar to the Control cards, all Service cards will be EPEC Cards (i.e. Service-2) as this was a pre-requisite for both Rel 4.2 and Rel 4.3. This means that no Service card replacement will be required. All existing Service cards in the system will be immediately upgrade-able to Release 5.0, through the appropriate software migration path contained in this document. New in Rel 5.0 With the introduction of Rel 4.2, there were no additional hardware components made available for the Service-2 cards. With the introduction of Rel 4.3, came an optional Service-2 card processing module upgrade, consisting of a new module called the Enhanced Processor Module (ePM), which replaces the old Processing Module (PM). To convert CallP, PNNI, or Data Spooling service cards from PM-based to ePM based, a conversion kit is required which has the product part number 90-8477-01.
1.1.4.
Upgrade the IP Service Cards (ISC)
Description At the time of writing this document there was no specific Rel 5.0 application software for the 7470 ISC, so there are no actual software upgrade scenarios to consider. However, there are new hardware considerations, which must be addressed in this section. The ISC was unavailable in R4.1 so no upgrade considerations from R4.1 will be presented here. The ISC was introduced in Rel 4.2 and provides IP Routing functionality to the 7470 system. It represents the Routing Engine and it has no physical interfaces. It uses its own database known as the Current configuration file. It has another configuration file called the Alternate that can be converted into the Current.
Issued
31NUP0031 7/19/2004
Upgrade Implications and Service Impact The ISC can be configured for 1+1 APS, which will offer a certain amount of protection, but all protocols supported by the card will temporarily go down when an activity switch occurs. For this reason, even when upgrading the ISC using a redundant configuration, there will be a slight service impact. When upgrading a simplex ISC card the logical routers will be down until the ISC has re-initialized and returned to a normal state of operation. Minimum Hardware Required The initial ISC for the 7470 system was introduced in Rel 4.2 with a single ePM and a product part number of 90-6184-12. In Rel 4.2 HLS#5, a new ISC was introduced that was equipped with dual ePM modules and had a product part number of 90-6184-13. If upgrading a single ePM ISC from Rel 4.2 to Rel 5.0, and the performance benefit of having dual ePMs on the ISC is required, then the card will have to be upgraded to 906184-13. An ISC Upgrade Kit (90-8477-01) is available to upgrade the ISC card from a 90-618412 to a 90-6184-13. If upgrading a dual ePM ISC to Rel 5.0, then no additional hardware is required. New in Rel 5.0 There is nothing new to the ISC as of Rel 5.0.
1.1.5.
Upgrade the Line Cards
Description Line cards represent the gateways to and from the switch and contain the endpoints of most cross-connections in the database of the control complex. The 7470 system has evolved into a true multi-services edge platform as it provides an interface for many different types of services and traffic types including Cell Relay, Frame Relay, Circuit Emulation, xDSL, Switched Services, and IP Routing. Upgrade Implications and Service Impact Line cards are usually configured in simplex mode and have no protection available to them.
Issued
31NUP0031 7/19/2004
When line cards are reset in simplex mode, all traffic that traverses the line card will stop until the card re-initializes and re-downloads its cross-connections from the control card. Some line cards can be configured for 1+1 APS and can be upgraded without any service impact. Other line cards can be configured for 1:N APS and can be upgraded with a minimal impact to existing service. Minimum Hardware Required Rel 5.0 will only support the -2 line card hardware variants, with the exception of the OC12-1/STM4-1, OC3-1/STM1-1, DS3-1/E3-1, and the T1-1/E1-1 cell relay line cards. Any older line cards must be removed from the system, or upgraded to -2 hardware variant cards, PRIOR to any upgrade to Rel 5.0. It is important to ensure that all existing line cards are at the minimum hardware revision during the planning phase of an upgrade. The following comments are other specific requirements to note. All OC12-1/STM4-1 cards require a Boot PROM upgrade to support the 1+1 APS feature introduced in Release 3.1. There exists an OC12-1/STM4-1 upgrade kit that includes the proper Boot PROM and a faceplate sticker displaying the 90-level part number. The 90level part number for this kit is 90-4556-11. Furthermore, all high-speed peripheral shelves require a Revision 5.4 (or greater) FIC upgrade to support 1+1 APS. The FIC revision is obtained from the 87-level part number of the FIC, using the last two digits: 87-0922-01-54 {indicates a revision 5.4 FIC}. This information can be obtained using three separate methods: 1. Through a Level 6 NMTI session, once the Control card is operating with Release 4.2 or higher application software, execute the commands MAINT > OBJECT > SLOT > SLOT_ID on the FIC slot to obtain the cards 87-level part number. Remove the inactive FIC from the shelf and view the non-chip side of the board. The 87-level part number will be printed on a sticker. It will be necessary to perform a fabric activity switch to view the second FIC.
2.
Issued
31NUP0031 7/19/2004
3.
Through a Level 0, 5, or 6 NMTI session, once the Control card is operating with Rel 4.2 or higher application software, execute the commands MAINT > SYSTEM > MORE > INVENTORY > (HSPS#) where (HSPS#) indicates the shelf number of the high-speed peripheral shelf.
Some T1/E1 Channelized Frame Relay cards may require a Boot Prom upgrade, if the cards were shipped before April 1st, 1999. A problem existed in the T1/E1 CFR card Boot Proms causing a small percentage of CFR cards to fail initialization. This issue is captured in TA#535 and the probability of this problem occurring is increased with heat and load size. Thus, as a card is upgraded, it becomes more susceptible to the problem. It is recommended to deliver new Boot Proms for both T1 and E1 CFR cards to sites where these card types will be upgraded. This is a precautionary measure, as the number of CFR cards exhibiting the problem has been very small. The Boot Prom versions, which correct the CFR initialization problem, are: E1 CFR (75 and 120 Ohm) T1 CFR => A22C02-H1-03 => A22702-H1-03
New in Rel 5.0 There are two new line cards being introduced in Rel 5.0. These cards are the 4-port OC3/STM1 cell relay card, and the 8-port DS3 cell relay card.
1.1.6.
Fabric Size Upgrade to 32k Cells
Description Note: The fabric MUST be upgraded to a size of 32k cells BEFORE any upgrade to Rel 5.0 is performed.
A 7470 system operating with a 32k-cell fabric is able to harness the advanced traffic and buffer management features available. This includes Internal Flow Control (IFC), extended Service Category Queues, advanced Service Arbitration schemes, per-VC Accounting, ABR Flow Control, and others. These features can be used to optimize the efficiency of the switch.
Issued
31NUP0031 7/19/2004
Upgrade Implications and Service Impact When the fabric size conversion to 32k cells is performed, every connection in the 7470 switch database will be modified. These modified connections must be re-downloaded to their respective line cards, which results in a slight interruption of traffic flow for each connection. Due to the fact that every connection in the 7470 system database must be redownloaded, the total data outage time is dependent on the total number of connections contained in the database. The data outage time for each connection will not be constant across all connections due to the manner in which the modified connection redownloading process is performed. This service outage will tear down and re-establish all PVC and SPVC connections while all existing SVC connections will be lost. Minimum Hardware Required Eagle-based DHUBs (90-5891-x1), Eagle-based SHUBs (90-6085-x1), Eagle-based LSHUBs (90-3162-x2) and NSX-based DSCs (90-3598-x3) are required. New in Rel 5.0 In Rel 5.0, there can only be a fabric type of 32k-cells. Due to this restriction, as mentioned above, the fabric MUST be converted to a 32k-cell fabric size before any upgrade to Rel 5.0 can proceed. The procedure for upgrading a Rel 4.2 system to a 32k-cell fabric size is outlined in 31NUP0022. The procedure for upgrading a Rel 4.3 system to a 32k-cell fabric size is outlined in 31NUP0026.
1.1.7.
Optional Control Mode Conversion
Description There are two types of control mode: non-integrated and integrated. Non-integrated control mode requires that the control cards operate with application software of the designation: A21215-x0-xx. Non-integrated control mode requires the switch to be equipped with its own Call Processing and PNNI services cards. Integrated control mode requires that the control cards operate with application software of the designation: A21515-x0-xx.
Issued
31NUP0031 7/19/2004
Integrated control mode uses the resources on the control card to perform Call Processing and PNNI Routing activities, thus removing the need to have separate Call Processing and PNNI cards in the system. Upgrade Implications and Service Impact The 7470 system cannot be directly converted from a non-integrated mode of control to an integrated mode of control, during an upgrade. The system must first be upgraded to Rel 5.0 and then converted to the desired control mode. There is a special procedure for the control mode conversion, detailed later in this document. Minimum Hardware Required If converting to a non-integrated control mode then Call Processing and PNNI cards must be added to the system, as the control card will no longer have the ability to perform their duties. If converting to integrated control mode then the existing Call Processing and PNNI cards can and should be removed from the switch. New in Rel 5.0 In Rel 5.0, it is not possible to convert from an integrated control mode to a nonintegrated control mode. Additionally, in order to convert from a non-integrated control mode to an integrated control mode, a control mode conversion kit must be purchased. The product part number of the non-integrated to integrated control mode conversion package is 90-9160-21.
1.2. New Hardware Introduced in Rel 5.0

This section describes the new hardware that is introduced in Rel 5.0 of the 7470 system.
1.2.1
The 4-port OC3/STM1 Cell Relay Card
The 4-port OC3/STM1 cell relay card is required for the DSLAM aggregation market to provide aggregation for underutilized DSLAM channels to POP.
Issued
10
31NUP0031 7/19/2004
1.2.2
The 8-port DS3 Cell Relay Card
The 8-port DS3 cell relay card is required for the DSLAM aggregation market to provide aggregation for underutilized DSLAM channels to POP. Approximately 85% of the DSLAMs output can be DS3.
1.3 New Features Introduced in Rel 5.0

This section describes the new features that are introduced in Rel 5.0 of the 7470 switch.
1.3.1
CPSS Scalability
With the introduction of Rel 5.0, comes the ability to have larger networks. The newly increased maximums are as follows: A maximum number of 250 routers (including gateways) per domain. A maximum number of 15 router links per node per domain A maximum number of 10 gateway nodes per domain A maximum number of 128 NM domain nodes per domain A maximum number of 244 stub nodes per domain A maximum number of 60 stub links per router per domain A maximum number of 250 router nodes plus stub nodes per domain
This feature is intended to grow the number of supported nodes such as to allow for increased growth.
1.3.2
Improved Auto-Reconcile
This 5620 to 7470 recovery mechanism has been re-designed to auto-reconcile the databases. Manual reconciles will occur only in the following cases: When the 7470 is first discovered by the 5620 NMS When a customer requests a full reconcile (using the 5620 or NMTI) Under certain scenarios if the operator uses NMTI rather than the 5620 for making substantial configuration changes
Issued
11
31NUP0031 7/19/2004
In all other cases, the communication recovery mechanism shall use the event monitoring mechanism for synchronizing the 5620 and 7470 databases after the communication failure
1.3.3
ILMI 4.0 Support
The ILMI protocol supports the bi-directional exchange of ATM interface parameters between two Interface Management Entities (IMEs) connected over a cell relay interface. ILMI 4.0 is supported on the following 7470 cell relay cards: OC12-2 and STM4-2 cell relay cards OC3-2M and STM1-2M cell relay cards OC3-2 and STM1-2 cell relay cards DS3-2 and E3-2 cell relay cards T1-2 and E1-2 cell relay cards
1.3.4
Integrated CallP/PNNI/Data Spooling
This feature implements the data spooling capabilities that currently exist on the data spooling card onto the integrated control card. Prior to this feature, the integrated control card did not have data spooling capability.
1.3.5
Configurable Individual Alarm Severity
With the implementation of this feature the node shall provide the ability to change the priority of an alarm. Alarms that have had their priorities modified by the operator can be subsequently modified (hence, the node shall always remember what the default priorities are).
1.3.6
Increased Scalability of Address Translation
This feature allows the 5620, using the 7470 Address Translation feature, to scale the total number of tables and entries supported in the network to greater than the maximum supported on a node. Without this feature, the 5620 cannot configure more Address Translation entries in the entire network than that which is supported on a single node.
Issued
12
31NUP0031 7/19/2004
1.3.7
Connection Enhancements
This feature will allow up to 64000 nodal connections even if some of the connections are made over the same ISL.
1.3.8
Switched Services VBNs
With the introduction of Switched Services VBNs, a network provider can allocate backbone bandwidth to switched calls from a single set of customers and only calls originating from those customers can utilize that bandwidth.
1.3.9
PNNI Diagnostic Improvements
This feature is broken up into three sub-features. All are designed to enhance the diagnostic capabilities of the switch when trying to debug PNNI networks and related problems. The three sub-features are: (1) PNNI Packet Trace this provides the customer the ability to trace the PNNI protocol packets entering or exiting the switch on specific PVC or SVCC based RCCs. This provides similar functionality to a packet sniffer. (2) Routing Table Enhancements this provides the customer more detailed behavioral information about the path selection algorithms used to route calls using PNNI. Customers can specify different call characteristics when entering the routing table, to simulate a real call entering the switch. The resulting routing table displays the actual path chosen by PNNI when those call characteristics are applied during path selection. (3) Signalling Packet Trace this provides the customer the ability to trace the signalling link messages entering or exiting the switch on a specific signalling link.
1.3.10 Default Fabric Type Change From 2k to 32k

The 7470 2k/12k HUB cards (Diablo-based HUBS) will not be supported for use in a Rel 5.0 system. Upgrades from 2k/12k to 32k fabric will not be supported in a Rel 5.0 system. The default fabric type will be changed to 32k.
Issued
13
31NUP0031 7/19/2004
1.3.11 NMS Support for Static Routing Tables

Configuration of static PNNI routing tables is currently supported on the 7470 only via NMTI. The objective of this feature is to provide a node interface to support static routing table management via the 5620 and to re-size the maximum number of routing tables and routes supported by the node.
1.3.12 4.5k connection support for DS3-2/E3-2 CR with eTM

Currently the 3-port DS3-2 and E3-2 cell relay cards can support a maximum of 2k connections per port with a limit of 6k connections per card. With this feature, the card will be able to support a maximum of 4.5k connections per port, with a 13.5k connection limit per card.
1.3.13 RTD Measurement on Cell Relay Cards

The -2 cell relay cards (excluding the OC12-2/STM4-2 cell relay cards) provide the ability to measure the round trip delay experienced by an OAM loopback cell, net of the cell processing time in the returning node.
1.3.14 RTD Measurement on Frame Relay Cards

The 16-port T1/E1 frame relay cards provide the ability to measure the round trip delay experienced by an OAM loopback cell, net of the cell processing time in the returning node.
1.3.15 Dynamic Channel Selection over ISLs

This feature eliminates the requirement for all BTV channels to be broadcast to all ISLs. Rather, a channel will only be distributed to an ISL if a viewer exists for that ISL. As a result, the ISL bandwidth usage will become more demand-oriented.
1.3.16 Multi-Port Ethernet VLAN Support

This feature introduces Bridged Virtual Local Area Network (VLAN) features to the 7470 Multi-port Ethernet Adaptation card. Ethernet endpoints will be converted as follows during the Rel 5.0 upgrade: VCI5 = 1 VPI5 = VCI4
indicates Release 5
Issued
14
31NUP0031 7/19/2004
Release 4 endpoint representation is still supported in Release 5.0, but user-priority mapping will not be available when the Release 4 representation is used.
1.3.17 Multi-Port Ethernet VC-VC Forwarding Support

This feature introduces VC-VC forwarding features to the 7470 Multi-port Ethernet Adaptation card.
1.3.18 In-band IP Support for Spooling

With this feature, the Data Spooling card shall support being a part of the In-band IP DCN.
1.3.19 Inband IP Using SPVCs

With this feature, the In-band IP solution shall support SPVCs.
1.4. System Requirements of Release 5.0 Features

The table below outlines the minimum system hardware requirements for all new functionality made available in Rel 5.0 of the 7470 system. If an R appears in the table then that particular piece of hardware is required to use that feature.
indicates Release 4
Issued
15
31NUP0031 7/19/2004
New Feature
Service CTL Integ. Card-2 CTL Card-2 Card-2
32k Fabric
SRAM Card
Data Spooling Card
DS32/E3-2
eTM
-2 CR Line Cards
ENET
16 Port F/R
CPSS Scalability Enhanced AutoReconcile ILMI 4.0 Support Integrated CallP/PNNI/Data Spooling Configurable Individual Alarm Severity Enhanced Address Translation Scalability Connection Enhancements Switched Services VBNs PNNI Diagnostic Improvements Default Fabric Type Change From 2k to 32k NMS Support For Static Routing Tables 4.5k Connection Support For DS32/E3-2 With eTM RTD Measurement On Cell Relay Cards RTD Measurement On Frame Relay Cards Dynamic Channel Selection Over ISLs
R R
R R
R R
R R
Issued
16
31NUP0031 7/19/2004
Multi-Port Ethernet VLAN Support Multi-Port Ethernet VC-VC Forwarding Support In-band IP Support For Data Spooling Cards In-band IP Using SPVCs
1.5. Network Management (5620) Support

Release 5.0 (SGA115-Fx-xx, SGA115-Hx-xx) of the Alcatel 5620 Network Manager will provide support for Release 5.0 of the Alcatel 7470 Multi-Service Platform. It is imperative that the 5620 Network Manager be upgraded to Release 5.0 prior to attempting an upgrade of a 7470 Multi-Service Platform. To safeguard against network management difficulties, during a 7470 system upgrade, the following steps should be executed before the 7470 switch upgrade commences: Perform a 5620 Network Manager database backup, Disable network-wide BWA Re-Routing, Disable network-wide Bumping. In some cases disabling the Reconcile Servers can provide more control of the Reconcile process and could assist in a smooth upgrade.
At the end of the 7470 system upgrade(s), re-enable anything that was manually disabled during execution of the previous steps. It is recommended that the complete set of steps required to ensure that the 5620 behaves smoothly is incorporated into the Method of Procedure (MOP) used for the actual upgrade. These steps should be staged before the actual upgrade takes place.
1.6. Important Points Vital to the Rel 5.0 Upgrade

This section lists important items of information that will be of interest when planning the upgrade.
Issued
17
31NUP0031 7/19/2004
Ensure that the upgrade is 100% complete before any configuration changes are made to the switch. Configuring anything on the 7470 system that is outside of the upgrade Procedure in the middle of an upgrade is not supported and is highly discouraged. It is imperative that an audit of the customers network be performed to ensure that all cards in the network are at the minimum hardware Revision. This should be performed during the planning phase of the upgrade so that ample time is available to replace obsolete hardware. The Release 5.0 7470 system database is not backward compatible with Release 4.2 and 4.3 7470 system databases. After an upgrade of a 7470 system to Release 5.0, it will be impossible to downgrade the system database to an earlier software release while maintaining the database. This does not mean that the original Rel 4.2 or Rel 4.3 database cannot be restored using a special procedure, but rather that a systemmanaged database conversion to an earlier software release cannot be performed. Refer to 31NUP0022 section 14 for an important discussion on Network Upgrade Strategies. This discussion talks about methods that can be used to minimize traffic hits in networks that carry switched services. It is important that the Method of Procedure (MOP) that is used to upgrade the customers network include a Back-out procedure. The Back-out procedure details the steps required to abort an upgrade if critical problems have occurred that have no acceptable workaround. The basic Back-out procedure is really the reverse of the Upgrade procedure. The node is reverted back to the previous release at the point of the upgrade severe problems were observed. First, the Line cards are brought back to the previous release, then the Service cards are brought back to the previous release, then the Fabric is brought back to the previous release, and finally the Control cards are brought back to the previous release. When bringing the Control cards back to the previous release a database restoration will be required if the entire complex has been upgraded. Aborting and backing out of an upgrade is a drastic measure used only when no other alternatives are available.
Issued
18
31NUP0031 7/19/2004
2. Upgrade Overview
This section outlines the general procedure involved when upgrading a 7470 system to Rel 5.0 from a base software release of either Release 4.2 or Release 4.3. The table below lists an ordered set of upgrade tasks (and the associated section) required to be executed when upgrading the 7470 system.
Step
Description
Section Reference
1. 2. 3. 4. 5. 6.
The Control Complex Upgrade The Fabric Upgrade The Service Card Upgrade The ISC Card Upgrade General UCS Card Upgrade 32k Cell Size Fabric Conversion
Must have been done in Rel 4.2/Rel 4.3, PRIOR to the Rel 5.0 upgrade.
Section 3.0 Section 4.0 Section 5.0 Section 6.0 Section 7.0 Section 8.0
7.
The Control Complex Mode Conversion (Optional)
Section 9.0
Issued
19
31NUP0031 7/19/2004
3. Control Complex Upgrade

The Control Complex Upgrade Procedure will vary depending on whether the switch is equipped with a single Control card (Simplex configuration) or two Redundant Control cards. If the switch is only equipped with a Simplex configuration then there will be a significant service interruption throughout the entire switch and a database restoration will need to take place. To upgrade a Simplex Control Complex the procedure in section 3.1 should be followed. If the switch is equipped with a Redundant Control Complex there will be minimal/no service impact and the procedure in section 3.2 should be followed. Please note that before any upgrade to Rel 5.0 is attempted, the system must be operating in a 32k-cell fabric mode. Without the system operating in a 32k-cell fabric mode, the upgrade cannot proceed. New in Rel 4.3 was the ePM and the new 256M PCMCIA flash disk. These two pieces of hardware will be packaged together in an ePM Upgrade Kit (90-8477-02). If the switch is to be upgraded to Rel 5.0 with the new ePM and flash disk then the procedure changes slightly in that each Control card will need to be physically removed and the new hardware attached. These procedures are included below.
3.1. Upgrade the Control Complex (Simplex)

Since a Simplex Control Complex is being upgraded the Control Card in slot 1-1 is the only card we are upgrading in this section.
3.1.1.
Download the Application S/W Generic
The Application S/W Generic must be downloaded to the non-current software bank. Refer to section A.1 to determine the proper software Generic required and then proceed to execute the steps in section A.2 to initiate the download.
3.1.2.
Record the System Parameters and Backup the Database
Since the database on a Simplex Control Complex will be lost during an upgrade it is imperative that the nodal database is backed up before the upgrade. It is also important to record all of the switchs configuration and system parameters. Refer to section B.1 for a list of the system parameters that should be recorded. Refer to section B.2 for the procedure required to backup the systems database.
Issued
20
31NUP0031 7/19/2004
3.1.3.
Set the Next Bank and Reset the Card (with an Optional ePM Upgrade)
Once the proper software has been downloaded to the inactive bank, the Control card can be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the Control card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
3.1.4.
Re-Configure the Control Complex
After the Simplex Control card has been upgraded it will initialize with an empty database. To prepare the switch for the database restoration process many system parameters should be manually re-configured. Follow the procedure detailed in section B.4 to re-configure the required system parameters.
3.1.5
Restore the System Database
The system database must now be restored from the backup file, in order to return the system to its normal state. Follow the procedure outlined in section B.2 to restore the systems database.
3.2. Upgrade Control Complex (Redundant)

Since a Redundant Control Complex is being upgraded the Control Cards in slots 1-1 and 1-2 are the only cards being upgraded in this section.
3.2.1.
Download the Application Software
The application software must be downloaded to the non-current software bank of both Control cards in slots 1-1 and 1-2. Refer to section A.1 to determine the proper software generic required and then proceed to execute the steps in section A.2 to initiate the download. Remember that the new Rel 5.0 software will need to be downloaded to both Control cards.
3.2.2.
Record the System Parameters and Backup the Database
Upgrading a Redundant Control Complex should not require a database restoration but it is a good practice to backup the database anyway and to record the system configuration parameters. Refer to section B.1 for a list of the system parameters that should be recorded. Refer to section B.2 for the procedure required to backup the switchs database.
Issued
21
31NUP0031 7/19/2004
3.2.3.
Confirm Demerits on the Control Complex
Before upgrading the Control Complex it is important to ensure that there are no demerits on the Control Complex. To view control complex demerits issue the following NMTI command: MAINT SYSTEM CONTROL. If there are Control demerits please resolve the issue before continuing or consult your Alcatel support representative.
3.2.4.
Set the Next Bank and Reset the Inactive Control Card (with an Optional ePM Upgrade)
Once it has been confirmed that there are no Control Complex demerits the Inactive Control card can be upgraded. Refer to section B.3 for the procedure required to reset and next-bank the Inactive Control card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
3.2.5.
Verify Demerits
Now that the Inactive Control card has been upgraded it is prudent to confirm that the newly upgraded Control card is ready to assume control of the switch before a Release Control is performed. To view Control demerits issue the following NMTI command: MAINT SYSTEM CONTROL. After the Inactive Control card is reset the demerits will initially start at 5500 meaning that the Active and Inactive Control cards are out of synch. The number of demerits will then decrease until it reached 1000. When demerits are at 1000 it means that the Inactive Control card is reconciling its database with the Active Control card. When the reconcile process is finished the demerits will go down to 0. The reconcile process can take from 5 to 15 minutes to complete as it is dependent on the size of the database. If there are still Control demerits after 15 minutes or so there may be a problem with the Control Complex. Please resolve the issue before continuing and/or consult your Alcatel support representative.
3.2.6.
Release Control to the Newly Upgraded Control Card
This step involves switching control of the switch to the newly upgraded Control card. Since the upgrade of the Inactive Control card proceeded smoothly with no demerits, this procedure can move forward. Issue the following NMTI command: MAINT SYSTEM CONTROL RELEASE_CTL PROCEED.
Issued
22
31NUP0031 7/19/2004
This will cause the previous Active Control card to be reset. If the control mode is Integrated, then all frame relay SVCs and N-ISDN SVCs will be cleared. These SVCs will need to be re-established. NOTE: It is important to note that the previous Active Control card has not had its next bank set yet. This is for security reasons to ensure that a database that is intact from the previous release exists on the card. If the next bank was set, the database would have been converted and the previous Active Control card (current Inactive) would reconcile its database from the new Active Control card. If the upgrade had to be aborted for any reason the only manner to regain the previous database would be through a database restoration. The previous Active Control card will go out of synch with the current Active Control card and they will no longer be able to communicate. This is due to the fact that the previous Active Control card is running a software release lower than the current Active is running. NOTE: The rule that governs the relationship between Redundant Control cards is that an Inactive CTL card can synch-up and reconcile from an Active CTL card that is running a lower software release. However, an Inactive CTL card cannot synch-up and reconcile from an Active CTL that is running a higher software release. Confirm that the previous Active Control card has initialized properly by issuing the following NMTI command: MAINT OBJECT SLOT ICTL .
3.2.7.
Set the Next Bank and Reset the Newly Inactive Control Card (with an optional ePM Upgrade)
Refer to section B.3 for the procedure required to reset and next-bank the Inactive Control card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
3.2.8.
Verify Demerits
Now that the new Inactive Control card has been upgraded it is prudent to confirm that the newly upgraded Control card is ready to re-assume control of the switch before a Release Control is performed. To view Control demerits issue the following NMTI command: MAINT SYSTEM CONTROL.
Issued
23
31NUP0031 7/19/2004
After the Inactive Control card is reset the demerits will initially start at 5500 meaning that the Active and Inactive Control cards are out of synch. The number of demerits will then decrease until it reached 1000. When demerits are at 1000 it means that the Inactive Control card is reconciling its database with the Active Control card. When the reconcile process is finished the demerits will go down to 0. The reconcile process can take from 5 to 15 minutes to complete as it is dependent on the size of the database. If there are still Control demerits after 15 minutes or so there may be a problem with the Control Complex. Please resolve the issue before continuing and/or consult your Alcatel support representative.
3.2.9.
Release Control to the Former Active and Newly Upgraded Inactive Control Card
It is usually preferable to switch back to the Control card that was active before the upgrade started. This step accomplishes this by switching control of the switch to the former Active Control card (newly upgraded Inactive Control card). This procedure can move forward by issuing the following NMTI command: MAINT SYSTEM CONTROL RELEASE_CTL PROCEED. This will cause the current Active Control card to be reset and the Current Active to assume control. If the control mode is Integrated, then all frame relay SVCs and NISDN SVCs will be cleared and will need to be re-established. Confirm that the new Inactive Control card initializes successfully by issuing the NMTI command: MAINT OBJECT SLOT ICTL. Finally check the Control demerits for a last time by issuing the following NMTI command: MAINT SYSTEM CONTROL. If there are still Control demerits after 15 minutes or so there may be a problem with the Control Complex. Please resolve the issue before continuing and/or consult your Alcatel support representative.
Issued
24
31NUP0031 7/19/2004
4. Fabric Upgrade
This section will describe the procedure required to upgrade a 7470s Fabric. In order to upgrade to Rel 5.0, the customer requires 32k Fabric and needs to physically replace old Diablo-based Fabric cards and upgrade to 32k Fabric before any further work takes place. The procedure for upgrading a Rel 4.2 system to a 32k-cell fabric size is outlined in 31NUP0022. The procedure for upgrading a Rel 4.3 system to a 32k-cell fabric size is outlined in 31NUP0026. The Fabric can be configured in various ways. The Fabric could be from a Standalone switch in where only the SHUBs on a single Peripheral Shelf need to be upgraded and there is no Switching Shelf. Alternatively, the Fabric could be from a Multi-Shelf switch in which we need to upgrade the Switching Shelf that houses the DSCs and the DHUBs (or LSHUBs) on each Peripheral Shelf. Finally, within each type of switch the Fabric could be either Simplex or Redundant. A Simplex Fabric has only an X Fabric and a Redundant Fabric has an X Fabric and a completely redundant Y Fabric as well. The table below indicates the relevant sections to refer to based on the type of the switch and its hardware requirements.
Section
Switch Type
Simplex or Redundant Fabric Simplex Fabric Redundant Fabric Simplex Fabric Redundant Fabric
Hardware Replacement No No No No
4.1 4.2 4.3 4.4
Standalone Standalone Multi-Shelf Multi-Shelf
For Fabric Redundant switches, it is generally recommended that the customer use their X Fabric as their active Fabric. There are no technical requirements for this recommendation but it is recommended for consistent utilization and deployment of the 7470 system. This section is written assuming that the X Fabric is the active Fabric although there may be exceptions that need to be dealt with on a case by case basis.
Issued
25
31NUP0031 7/19/2004
4.1. Fabric Upgrade for a Standalone Switch with Simplex Fabric

Note: The fabric MUST have been upgraded to a size of 32k cells BEFORE any upgrade to Rel 5.0 is performed. When upgrading a Standalone switch with Simplex Fabric there will be a service impact for the duration of the Fabric outage. The duration of time should last for the time required for the SHUB to initialize with its new S/W load. The following steps are required to upgrade the Fabric on this type of switch.
4.1.1.
The proper S/W Generic will need to be downloaded to the non-current S/W bank of the SHUB. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
4.1.2.
Set the Next Bank and Reset the SHUB
(1) Confirm that the proper S/W Generic has been downloaded to the non-current bank of the cards by issuing the following NMTI command: MAINT OBJECT SLOT <1-HX> . (2) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. Since there is no Y Fabric the NMTI screen should indicate N/A and the X Fabric should indicate Ok (Active). (3) Set the next bank on the SHUB by issuing the following NMTI command: MAINT OBJECT SLOT <1-HX> NEXT_BANK PROCEED. (4) Reset the card issuing the following NMTI command: MAINT OBJECT SLOT <1-HX> RESET_CARD. (5) Confirm that the card initialized successfully with the new S/W load by issuing the following NMTI command: MAINT OBJECT SLOT <1-HX> . The new S/W load should be visible with a status of Current.
Issued
26
31NUP0031 7/19/2004
(6) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. Since there is no Y Fabric the NMTI screen should indicate N/A and the X Fabric should indicate Ok (Active).
4.2. Fabric Upgrade for a Standalone Switch with Redundant Fabric

When upgrading a Standalone switch with Redundant Fabric there will not be a service impact. First the Inactive Y SHUB is upgraded to the new release. A Fabric Activity switch is then performed so that the X Fabric can be upgraded. Finally, a Fabric Activity Switch switches activity back the X Fabric. The following are the detailed steps required to upgrade the Fabric on this type of switch.
4.2.1.
The proper S/W Generic will need to be downloaded to the non-current S/W bank of both the X and the Y SHUB. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
4.2.2.
Set the Next Bank and Reset the Inactive Y SHUB
(1) Confirm that the proper S/W Generic has been downloaded to the non-current bank of the card by issuing the following NMTI command: MAINT OBJECT SLOT <1-HY> . (2) First, verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. The X Fabric should indicate Ok (Active) and the Y Fabric should indicate Ok.
(3) Set the next bank on the SHUB by issuing the following NMTI command: MAINT OBJECT SLOT <1-HY> NEXT_BANK PROCEED. (4) Reset the card by issuing the following NMTI command: MAINT OBJECT SLOT <1-HY> RESET_CARD.
Issued
27
31NUP0031 7/19/2004
(5) Confirm that the card initialized successfully with the new S/W load by issuing the following NMTI command: MAINT OBJECT SLOT <1-HY> . The new S/W load should be visible with a status of Current. (6) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. The X Fabric should indicate Ok (Active) and the Y Fabric should indicate Ok.
4.2.3.
Perform a Fabric Activity Switch to Y
Perform a Fabric Activity Switch to force the Y Fabric to assume control of the switch while the X Fabric is upgraded. Issue the following NMTI command: MAINT SYSTEM FABRIC FORCE_SWITCH PROCEED. The Y Fabric should now show a status of Active, and the activity LEDs of the Y Fabric cards should now be on (green).
4.2.4.
Set the Next Bank and Reset the Inactive X SHUB
(1) Confirm that the proper S/W Generic has been downloaded to the non-current bank of the card by issuing the following NMTI command: MAINT OBJECT SLOT <1-HX> . (2) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. The X Fabric should indicate Ok and the Y Fabric should indicate Ok Active. (3) Set the next bank on the SHUB by issuing the following NMTI command: MAINT OBJECT SLOT <1-HX> NEXT_BANK PROCEED. (4) Reset the card issuing the following NMTI command: MAINT OBJECT SLOT <1-HX> RESET_CARD. (5) Confirm that the card initialized successfully with the new S/W load by issuing the following NMTI command:
Issued
28
31NUP0031 7/19/2004
MAINT OBJECT SLOT <1-HX> . The new S/W load should be visible with a status of Current. (6) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. The X Fabric should indicate Ok and the Y Fabric should indicate Ok Active.
4.2.5.
Perform a Fabric Activity Switch back to X
(1) Perform a Fabric Activity Switch back to X so the Fabric upgrade ends in the same state it began in. Issue the following NMTI command: MAINT SYSTEM FABRIC FORCE_SWITCH PROCEED. (2) Verify that there are no Fabric problems and the X Fabric has properly assumed control of the switch by issuing the following NMTI command: MAINT SYSTEM FABRIC. The X Fabric should indicate Ok Active and the Y Fabric should indicate Ok.
4.3 Fabric Upgrade for a Multi-Shelf Switch with Simplex Fabric

When upgrading a Multi-Shelf switch with Simplex Fabric there will be a service impact for the duration of the Fabric outage. The duration of time should last for the time required for the X HUBs and X DSCs to initialize with its new S/W load. The following steps are required to upgrade the Fabric on this type of switch.
4.3.1.
The proper S/W Generic will need to be downloaded to the non-current S/W bank of the X HUBs and X DSCs. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download for each card.
4.3.2.
Set the Next Bank and Reset the Fabric Cards
(1) Confirm that the proper S/W Generic has been downloaded to the non-current bank of the cards by issuing the following NMTI command: MAINT OBJECT SLOT <slot_id> ,
Issued
29
31NUP0031 7/19/2004
Where <slot_id> represents the slot number of the Fabric cards. (2) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. Since there is no Y Fabric the NMTI screen should indicate N/A and the X Fabric should indicate Ok (Active). (3) Set the next bank and reset all of the Fabric cards by starting with the highest numbered shelf and working down to the lowest numbered shelf. Perform this operation on Fabric pairs (i.e. 7-HX, X-S7) together before proceeding to the next lowest shelf. Issue the following NMTI commands in the following sequence: MAINT OBJECT SLOT X-S8 NEXT_BANK PROCEED, MAINT OBJECT SLOT X-S8 RESET_CARD PROCEED, MAINT OBJECT SLOT P8-HX NEXT_BANK PROCEED, MAINT OBJECT SLOT P8-HX RESET_CARD PROCEED,
MAINT OBJECT SLOT X-S1 NEXT_BANK PROCEED, MAINT OBJECT SLOT X-S1 RESET_CARD PROCEED, MAINT OBJECT SLOT P1-HX NEXT_BANK PROCEED, MAINT OBJECT SLOT P1-HX RESET_CARD PROCEED.
NOTE: For high-speed shelves, the only cards to be upgraded at this time should be the DSC cards. The high-speed line card(s) should not be upgraded until the line card upgrade section.
4.3.3.
Confirm Proper S/W and Fabric Health
(1) Confirm that all of the cards initialized successfully with the proper new Rel 5.0 S/W load by issuing the following NMTI command:
Issued
30
31NUP0031 7/19/2004
MAINT OBJECT SLOT <slot_id> , Where <slot_id> represents the slot number of the cards that make up the Fabric. The new S/W load should be visible with a status of Current. (2) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. Since there is no Y Fabric the NMTI screen should indicate N/A and the X Fabric should indicate Ok (Active).
4.4. Fabric Upgrade for a Multi-Shelf Switch with Redundant Fabric

When upgrading a Multi-Shelf switch with Redundant Fabric there will not be a service impact. First, the Inactive Y Fabric is upgraded to the new release. A Fabric Activity switch is then performed so that the X Fabric can be upgraded. Finally, a Fabric Activity Switch switches activity back the X Fabric. The following are the detailed steps required to upgrade the Fabric on this type of switch.
4.4.1.
The proper S/W Generic will need to be downloaded to the non-current S/W bank of both the X and Y Fabric cards. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
4.4.2.
Set the Next Bank and Reset the Inactive Y Fabric
(1) Confirm that the proper S/W Generics have been downloaded to the non-current bank of the cards by issuing the following NMTI command: MAINT OBJECT SLOT <slot_id> , Where <slot_id> represents the slot number of the cards that make up the Y Fabric. (2) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. The X Fabric should indicate Ok (Active) and the Y Fabric should indicate Ok.
Issued
31
31NUP0031 7/19/2004
(3) Set the next bank and reset all of the Y Fabric cards by starting with the highest numbered shelf and working down to the lowest numbered shelf. Perform this operation on Fabric pairs (i.e. 7-HX, X-S7) together before proceeding to the next lowest shelf. Issue the following NMTI commands in the following sequence: MAINT OBJECT SLOT Y-S8 NEXT_BANK PROCEED, MAINT OBJECT SLOT Y-S8 RESET_CARD PROCEED, MAINT OBJECT SLOT P8-HY NEXT_BANK PROCEED, MAINT OBJECT SLOT P8-HY RESET_CARD PROCEED,
MAINT OBJECT SLOT Y-S1 NEXT_BANK PROCEED, MAINT OBJECT SLOT Y-S1 RESET_CARD PROCEED, MAINT OBJECT SLOT P1-HY NEXT_BANK PROCEED, MAINT OBJECT SLOT P1-HY RESET_CARD PROCEED. NOTE: For high-speed shelves, the only cards to be upgraded at this time should be the DSC cards. The high-speed line card(s) should not be upgraded until the line card upgrade section.
4.4.3.
(1) Confirm that all of the Y Fabric cards initialized successfully with the proper new Rel 5.0 S/W load by issuing the following NMTI command: MAINT OBJECT SLOT <slot_id> , Where <slot_id> represents the slot number of the cards that make up the Fabric. The new S/W load should be visible with a status of Current. (2) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC.
Issued
32
31NUP0031 7/19/2004
The X Fabric should indicate Ok
Active and the Y Fabric should indicate Ok.
4.4.4.
Perform a Fabric Activity Switch to Y
Perform a Fabric Activity Switch to force the Y Fabric to assume control of the switch so that the X Fabric can be upgraded. Issue the following NMTI command: MAINT SYSTEM FABRIC FORCE_SWITCH PROCEED. The Y Fabric should now show a status of Active, and the activity LEDs of the Y Fabric cards should now be on (green).
4.4.5.
Set the Next Bank and Reset the Inactive X Fabric
(1) Confirm that the proper S/W Generics have been downloaded to the non-current bank of the cards by issuing the following NMTI command: MAINT OBJECT SLOT <slot_id> , Where <slot_id> represents the slot number of the cards that make up the X Fabric. (2) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. The X Fabric should indicate Ok and the Y Fabric should indicate Ok (Active). (3) Set the next bank and reset all of the X Fabric cards by starting with the highest numbered shelf and working down to the lowest numbered shelf. Perform this operation on Fabric pairs (i.e. 7-HX, X-S7) together before proceeding to the next lowest shelf. Issue the following NMTI commands in the following sequence: MAINT OBJECT SLOT X-S8 NEXT_BANK PROCEED, MAINT OBJECT SLOT X-S8 RESET_CARD PROCEED, MAINT OBJECT SLOT P8-HX NEXT_BANK PROCEED, MAINT OBJECT SLOT P8-HX RESET_CARD PROCEED,
Issued
33
31NUP0031 7/19/2004
MAINT OBJECT SLOT X-S1 NEXT_BANK PROCEED, MAINT OBJECT SLOT X-S1 RESET_CARD PROCEED, MAINT OBJECT SLOT P1-HX NEXT_BANK PROCEED, MAINT OBJECT SLOT P1-HX RESET_CARD PROCEED. NOTE: For high-speed shelves, the only cards to be upgraded at this time should be the DSC cards. The high-speed line card(s) should not be upgraded until the line card upgrade section.
4.4.6.
(1) Confirm that all of the X Fabric cards initialized successfully with the proper new Rel 5.0 S/W load by issuing the following NMTI command: MAINT OBJECT SLOT <slot_id> , Where <slot_id> represents the slot number of the cards that make up the Fabric. The new S/W load should be visible with a status of Current. (2) Verify that there are no Fabric problems by issuing the following NMTI command: MAINT SYSTEM FABRIC. The Y Fabric should indicate Ok Active and the X Fabric should indicate Ok.
4.4.7.
Perform a Fabric Activity Switch back to X
(1) Perform a Fabric Activity Switch back to X so the Fabric upgrade ends in the same state it began in. Issue the following NMTI command: MAINT SYSTEM FABRIC FORCE_SWITCH PROCEED. (2) Verify that there are no Fabric problems and the X Fabric has properly assumed control of the switch by issuing the following NMTI command: MAINT SYSTEM FABRIC. The X Fabric should indicate Ok Active and the Y Fabric should indicate Ok.
Issued
34
31NUP0031 7/19/2004
5. The Service Card Upgrade

The Service cards are the Call Processing cards, the PNNI cards, and the Data Spooling cards. The Call Processing cards control and manage all Switched Calls (SPVCs and SVCs) that they are assigned to on the switch. The PNNI card is responsible for creating and updating Routing Tables that the Switched Calls dynamically use. The Data Spooling card is used to collect and propagate useful statistics on Switched Calls. Each type of Service card can be configured for either Simplex or 1+1 APS Protection. Depending on the configuration the Upgrade Procedure will vary. New to Rel 4.3 is the ePM which will be packaged in a Service card ePM Upgrade Kit (90-8477-01). If the switch is to be upgraded to Rel 5.0 with the new ePM then the procedure changes slightly in that each Service card will need to be physically removed and the new hardware attached. NOTE: It is a pre-requisite to have EPEC cards for all of the Service cards. Since we are upgrading from Rel 4.2 or Rel 4.3 the Service cards must already be EPEC cards. NOTE: If upgrading to Integrated Control Mode on the switch it is not necessary to upgrade the Service cards as their functionality will be part of the Control load.
5.1. Upgrade the Call Processing Cards (Simplex)

Depending on the configuration of the switch there could be more than a single Call Processing card controlling the Switched Calls. Each independent Call Processing card on a specific switch is associated with a single Call Control Group identified with a unique number. Each Peripheral Shelf can be assigned a different Call Control Group number. This is a method to partition the switch among different Call Processing cards. Ensure that all Call Processing cards on a switch are upgraded. Upgrading a Simplex Call Processing card involves setting the next bank and resetting the card. Until the card re-initializes, all existing SPVCs and SVCs will be torn down and no new Switched Calls will be permitted across the Call Control Group that this Call Processing card controls. When the card comes back up all existing SPVCs will be reestablished and all previously existing SVC will be lost.
5.1.1.
The Application S/W Generic must be downloaded to the non-current S/W bank of the Call Processing card. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
Issued
35
31NUP0031 7/19/2004
5.1.2.
Confirm the Status of the Card
Confirm that the Call Processing card is in good working order before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Call Processing card. The card should have a status of Ok.
5.1.3.
Set the Next Bank and Reset the Card (with an optional ePM Upgrade)
The Call processing card should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the Inactive Call Processing card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
5.1.4.
Confirm that the Call Processing card is in good working order before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Call Processing card. The card should have a status of Ok.
5.2. Upgrade the Call Processing Cards (1+1 HOT Redundancy)

Depending on the configuration of the switch there could be more than one Call Processing redundant pairs controlling the Switched Calls. Each independent Call Processing pairs on a specific switch is associated with a single Call Control Group identified with a unique number. Each Peripheral Shelf can be assigned a different Call Control Group number. This is a method to partition the switch among different Call Processing cards. Ensure that all Call Processing card pairs on a switch are upgraded. Upgrading Redundant Call Processing cards involves setting the next bank and resetting the Inactive card first. Once the Inactive card initializes properly, the Active card is upgraded causing an Activity switch to the Inactive. With this type of redundancy all Switched Calls should not be impacted.
3LS TEC IPD Services & Support 36
Issued
31NUP0031 7/19/2004
5.2.1.
The Application S/W Generic must be downloaded to the non-current S/W bank of both Call Processing cards. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
5.2.2.
Confirm the Status of the Cards
Confirm that the Call Processing cards are in good working order and that 1+1 APS is properly configured on the APS pair before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Call Processing cards. Both cards should have a status of Ok. The card in the odd slot should have an Activity Status of Active and its Redundancy should indicate 1+1 Hot, Enabled And Available (Synchronized). The card in the even slot should have an activity status of Inactive and its Redundancy should indicate 1+1 Hot, Enabled And Available (Synchronized).
5.2.3.
Set the Next Bank and Reset the Inactive Card (with an optional ePM Upgrade)
The Inactive Call processing card should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the Inactive Call Processing card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
5.2.4.
Re-Confirm the Status of the Cards
Confirm that the Call Processing cards are in good working order and that 1+1 APS is properly configured on the APS pair before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Call Processing cards. Both cards should have a status of Ok. The card in the odd slot should have an Activity Status of Active and its Redundancy should indicate 1+1 Hot, Enabled And Available (Synchronized). The card in the even slot should have an activity status of Inactive and its Redundancy should indicate 1+1 Hot, Enabled And Available (Synchronized).
Issued
37
31NUP0031 7/19/2004
5.2.5.
Set the Next Bank and Reset the Active Card (with an optional ePM Upgrade)
By resetting the Active Call Processing card the Inactive card will immediately assume control of the assigned Call Control Group. The Active Call processing card should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the Active Call Processing card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
5.2.6.
Final Confirmation of the Status of the Cards
Confirm that the Call Processing cards are in good working order and that 1+1 APS is properly configured on the APS pair before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Call Processing cards. Both cards should have a status of Ok. The card in the odd slot should have an Activity Status of Active and its Redundancy should indicate 1+1 Hot, Enabled And Available (Synchronized). The card in the even slot should have an activity status of Inactive and its Redundancy should indicate 1+1 Hot, Enabled And Available (Synchronized). To take the APS pair back to its initial state, the Active card in the even slot can be reset which will allow the card in the odd slot to assume control. The status of the cards should then be re-confirmed.
5.3. Upgrade the Data Spooling Card (Simplex)

The Data Spooling cards collect statistics on the activity of all Switched Calls on the switch. It collects (Spools) a pool of statistics at regular intervals and then ftps these statistics to a machine called the Data Collector. For a Simplex upgrade the Data Spooling card will need to be next banked and then reset. All Spooled records will be lost as soon as the card is reset so it is important to ensure that the records in the current interval are successfully spooled before resetting the card.
5.3.1.
The Application S/W Generic must be downloaded to the non-current S/W bank of the Data Spooling card. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
Issued
38
31NUP0031 7/19/2004
5.3.2.
Confirm the Status of the Card, the Data Collector Links, and the Spooled Records in the Current Interval
(1) Confirm that the Data Spooling card is in good working order before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Call Processing card. The card should have a status of Ok. (2) Confirm that the Data Collector Link is up and that all of the records in the current interval have been Spooled and ftped to the Data Collector. Issue the following NMTI command: MAINT OBJECT RESOURCE DATA_SPOOLING.
5.3.3.
The Data Spooling card should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the Data Spooling card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
5.3.4.
Re-Confirm the Status of the Card, the Data Collector Links, and the Spooled Records in the Current Interval
(1) Confirm that the Data Spooling card is in good working order before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Data Spooling card. The card should have a status of Ok. (2) Confirm that the Data Collector Link is up. Issue the following NMTI command: MAINT OBJECT RESOURCE DATA_SPOOLING.
Issued
39
31NUP0031 7/19/2004
5.4. Upgrade the Data Spooling Card (Redundant)

The Data Spooling cards collect statistics on the activity of all Switched Calls on the switch. It collects (Spools) a pool of Stats at regular intervals and then ftps these Stats to a machine called the Data Collector. For a Redundant upgrade the Inactive Data Spooling card will need to be next banked and then reset. After the Inactive card initializes with the new load and the Data Collector Links are re-established the Active card will be next banked and reset causing the Inactive card to assume control of the Data Spooling. For a Redundant upgrade there should be no impact to the Spooling of records.
5.4.1.
The Application S/W Generic must be downloaded to the non-current S/W bank of both Data Spooling cards. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
5.4.2.
Confirm the Status of the Cards, the Data Collector Links, and the Spooled Records in the Current Interval
(1) Confirm that the Data Spooling cards are in good working order before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Data Spooling card. The card should have a status of Ok. (2) Confirm that the Data Collector Links are up and that all of the records in the current interval have been Spooled and ftped to the Data Collector. Issue the following NMTI command: MAINT OBJECT RESOURCE DATA_SPOOLING.
5.4.3.
The Inactive Data Spooling card should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the Inactive Data Spooling card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
Issued
40
31NUP0031 7/19/2004
5.4.4.
Re-Confirm the Status of the Card, the Data Collector Links, and the Spooled Records in the Current Interval
(1) Confirm that the Data Spooling card is in good working order before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Data Spooling card. The card should have a status of Ok. (2) Confirm that the Data Collector Link is up and that all of the records in the current interval have been Spooled and ftped to the Data Collector. Issue the following NMTI command: MAINT OBJECT RESOURCE DATA_SPOOLING.
5.4.5.
The Active Data Spooling card should now be next-banked and reset. This will cause the Inactive card to assume control of the Spooling of records. Refer to section B.3 for the procedure required to reset and next-bank the Active Data Spooling card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
5.3.6.
Final Confirmation of the Status of the Card, and the Data Collector Links
(1) Confirm that the Data Spooling cards are in good working order before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Data Spooling cards. The card should have a status of Ok. (2) Confirm that the Data Collector Links are up and that all of the records in the current interval have been Spooled and ftped to the Data Collector. Issue the following NMTI command: MAINT OBJECT RESOURCE DATA_SPOOLING.
Issued
41
31NUP0031 7/19/2004
5.5. Upgrade the PNNI Card (Simplex)

Upgrading a Simplex PNNI card involves setting the next bank and resetting the card. For the duration of the outage there will be an inability to route new switched calls until the card comes back up. Furthermore, SPVCs and SVCs may also be torn down depending on network conditions.
5.5.1.
The Application S/W Generic must be downloaded to the non-current S/W bank of Simplex the PNNI card. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
5.5.2.
Confirm that the PNNI card is in good working order before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the PNNI card. The card should have a status of Ok. The Activity Status should be Active and 1+1 Warm Redundancy should be Disabled.
5.5.3.
The PNNI card should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
5.5.4.
Confirm that the PNNI card is in good working order before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the PNNI card. The card should have a status of Ok. The Activity Status should be Active and 1+1 Warm Redundancy should be Disabled.
Issued
42
31NUP0031 7/19/2004
5.6. Upgrade the PNNI Card (1+1 Warm Redundant)

Upgrading Redundant PNNI cards involves setting the next bank and resetting the Inactive card first. Once the Inactive card initializes properly, the Active card is upgraded causing an Activity switch to the Inactive. With this type of redundancy there will be no service impact.
5.6.1.
The Application S/W Generic must be downloaded to the non-current S/W bank of both PNNI cards. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
5.6.2.
Confirm that the PNNI cards are in good working order and that 1+1 WARM Redundancy is properly configured on the APS pair before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the PNNI cards. Both cards should have a status of Ok. The card in the odd slot should have an Activity Status of Active and its 1+1 Warm Redundancy status should indicate Enabled And Available. The card in the even slot should have an activity status of Inactive and its 1+1 Warm Redundancy status should indicate Enabled And Available.
5.6.3.
The Inactive PNNI card should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the Inactive PNNI card. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
5.6.4.
Confirm that the PNNI cards are in good working order and that 1+1 WARM Redundancy is properly configured on the APS pair before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>,
Issued
43
31NUP0031 7/19/2004
Where <slot_id> is the slot number of the PNNI cards. Both cards should have a status of Ok. The card in the odd slot should have an Activity Status of Active and its 1+1 Warm Redundancy status should indicate Enabled And Available. The card in the even slot should have an activity status of Inactive and its 1+1 Warm Redundancy status should indicate Enabled And Available.
5.6.5.
By resetting the Active PNNI card the Inactive card will immediately assume control. The Active PNNI card should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the Active PNNI. If an ePM upgrade is required then there will be a special procedure in section B.3 to handle this.
5.6.6.
Final Confirmation the Status of the Cards
Confirm that the PNNI cards are in good working order and that 1+1 WARM Redundancy is properly configured on the APS pair before starting the upgrade by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the PNNI cards. Both cards should have a status of Ok. The card in the odd slot should have an Activity Status of Active and its 1+1 Warm Redundancy status should indicate Enabled And Available. The card in the even slot should have an activity status of Inactive and its 1+1 Warm Redundancy status should indicate Enabled And Available. To take the APS pair back to its initial state, the Active card in the even slot can be reset which will allow the card in the odd slot to assume control. The status of the cards should then be re-confirmed.
Issued
44
31NUP0031 7/19/2004
6. The IP Services Card (ISC) Upgrade

The ISC is a new card initially introduced in Rel 4.2. It provides IP Routing capability. At the time of writing this version of the document there was only a Rel 4.2 load for this card, therefore there are no current Rel 5.0 upgrade implications for the card. There is a plan in place to extend the functionality of the ISC to include features such as OSPF and MPLS and these may be introduced in a Hardened Load Set within Rel 5.0. At that time this section will be relevant. The ISC should be treated differently from all of the other components of a 7470 switch upgrade thus it has its own section in the NUP. The ISC stores information on the configuration of all of its Routers, Service Interfaces, and Virtual Connections in its Current Config File. The cross-connections on the ISC are stored in the Control cards database. The ISC also contains a file called the Alternate Config File that can be used as a vehicle to update the current configuration of the switch.
6.1. Upgrade the ISC (Simplex)

A Simplex ISC Upgrade will involve setting the Next Bank and Resetting the ISC. There will be a service impact while the ISC initializes with the new Rel 5.0 load. The ISC will retain its existing Config file when it initializes with the new Rel 5.0 load and will not require a Config file restoration.
6.1.1.
The Application S/W Generic must be downloaded to the non-current S/W bank of the ISC. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
6.1.2.
Backup the Current Config File on the ISC
It is a good practice to backup the Current Config file and the Alternate Config file before upgrading the ISC. This can be accomplished by bringing up a Command Line Interface (CLI) session on the switch and issuing the following command: copy current-config ftp //aaa.bbb.ccc.ddd/path/filename, Where aaa.bbb.ccc.ddd is the IP address of the Gateway to the Active NMS, path is the location on the NMS, and filename is the name of the file.
6.1.3.
Confirm that the ISC is in good working order by issuing the following NMTI command:
Issued
45
31NUP0031 7/19/2004
CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the ISC. The ISC should have a status of Ok.
6.1.4.
Set the Next Bank and Reset the ISC
The ISC should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the ISC.
6.1.5.
Re-Confirm the Status of the ISC
Confirm that the ISC is in good working order by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the ISC. The ISC should have a status of Ok.
6.2. Upgrade the ISC (Redundant)

A Redundant ISC upgrade involves upgrading the Inactive ISC first. The Active ISC should then be upgraded forcing the Inactive to assume control.
6.2.1.
The Application S/W Generic must be downloaded to the non-current S/W bank of both ISCs. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
6.2.2.
Backup the Current Config File on the ISC
It is a good practice to backup the Current Config file before upgrading the ISC. This can be accomplished by bringing up a Command Line Interface (CLI) session on the switch and issuing the following command: copy current-config ftp //aaa.bbb.ccc.ddd/path/filename, Where aaa.bbb.ccc.ddd is the IP address of the Gateway to the Active NMS, path is the location on the NMS, and filename is the name of the file.
6.2.3.
Confirm that both ISCs are in good working order by issuing the following NMTI command:
Issued
46
31NUP0031 7/19/2004
CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the ISC. The ISC should have a status of Ok.
6.2.4.
Set the Next Bank and Reset the Inactive ISC
The Inactive ISC should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the ISC.
6.2.5.
Confirm that the ISC is in good working order by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the ISCs. The ISCs should have a status of Ok.
6.2.6.
Set the Next Bank and Reset the Active ISC
The Inactive ISC should now be next-banked and reset. Resetting the Active ISC will revert control to the Inactive ISC. Refer to section B.3 for the procedure required to reset and next-bank the ISC.
6.2.7.
Final Confirmation of the Status of the Cards
Confirm that the ISC is in good working order by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the ISCs. The ISCs should have a status of Ok.
Issued
47
31NUP0031 7/19/2004
7. The Line Card Upgrade Procedure

The final mandatory component of upgrading the 7470 switch is upgrading the Universal Card Slot (UCS) Line cards. The Line cards represent the entry and exit points to the switch and the 7470 switch supports a large variety of Line cards. Refer to table A-1 for a list of all supported Line cards. The general upgrade procedure is quite simple as it involves setting the next bank and resetting the Line card. Traffic that would normally flow through that card will stop until the card initializes into its new load and downloads its cross-connections from the Control card. This case is detailed in section 7.1. If the Line card needs to be replaced with a -2 version of the card then execute the procedure in section 7.2. There are other special cases of a Line card upgrade that are a little more involved such as upgrading using 1+1 APS or 1:N APS. With these upgrades there should be no service impact. These cases are detailed in section 7.3.
7.1. General Line Card Upgrade

During the resetting of the card, traffic that would normally flow through the card will stop until the card initializes into its new load and downloads its cross-connections from the Control card.
7.1.1.
The Application S/W Generic must be downloaded to the non-current S/W bank of the Line card. Refer to section A.1 to determine the proper S/W Generic required and then proceed to execute the steps in section A.2 to initiate the download.
7.1.2.
Confirm that the Line card is in good working order by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Line card. Both cards should have a status of Ok.
7.1.3.
Set the Next Bank and Reset the Line card
The Line card should now be next-banked and reset. Refer to section B.3 for the procedure required to reset and next-bank the Line card.
Issued
48
31NUP0031 7/19/2004
7.1.4.
Re-Confirm the Status of the Card
Confirm that the Line card is in good working order by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Line card. The card should have a status of Ok.
7.2. Line Card Version -2 Upgrade

During the time required to replace the Line card with the new -2 card, traffic that would normally flow through the card will stop until the new card initializes into its new load and downloads its cross-connections from the Control card.
7.2.1.
Replace the Existing Line Card with the New -2 Version of the Card
(1) Remove the existing Line card and immediately replace it with the new -2 version of the card. (2) Wait until the new Line card initializes and confirm that the proper S/W load is running on the card by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Line card. The Line card should have a status of Ok.
7.2.2.
Re-Confirm the Status of the Card and Configure Version -2 of the Card
(1) Confirm that the Line card is in good working order by issuing the following NMTI command: CONFIG OBJECT SLOT <slot_id>, Where <slot_id> is the slot number of the Line card. The card should have a status of Ok. (2) Notice that the version of the card will should indicate version-2 under installed and version-1 under configured. Configure the card for version-2 by issuing the following NMTI command:
Issued
49
31NUP0031 7/19/2004
CONFIG OBJECT SLOT <slot_id> OPTION CARD_VERSION <version-2>, Where <slot_id> represents the slot number of the card.
7.3 APS Line Card Upgrade

There are two cases that represent Line card APS upgrades in which there should be no impact to existing service. The first case represents 1+1 APS upgrades and the second represents 1:N APS upgrades. For the upgrade procedure for both cases refer to 31NUP0022 section 11, procedure#3, and section 12, procedure#4, respectively. These comprehensive procedures also describe how to configure an existing Simplex Line card configuration for 1+1 or 1:N APS.
Issued
50
31NUP0031 7/19/2004
8. Upgrading to 32k Fabric

A 7470 switch running 32k Fabric is able to harness the advanced Traffic and Buffer management features available. This includes Internal Flow Control (IFC), extended Service Category Queues, advanced Service Arbitration schemes, per-VC Accounting, ABR Flow Control, and others. These features can be used to optimize the efficiency of the switch. Upgrading to 32k Fabric will cause every connection in the 7470 switch database to be modified. These modified connections must be re-downloaded to their respective Line cards, which results in a slight interruption of traffic flow for each connection. Due to the fact that every connection in the 7470 system database must be re-downloaded, the total data outage time is dependent on the total number of connections contained in the database. The data outage time for each connection will not be constant across all connections due to the manner in which the modified connection re-downloading process is performed. This service outage will tear down and re-establish all PVC and SPVC connections while all existing SVC connections will be lost. In Rel 5.0, the fabric size can only be of the 32k-cell type. Therefore, any conversion process required will take place in either Rel 4.2 using 31NUP0022, or in Rel 4.3 using 31NUP0026. This document will not outline the 32k-cell size conversion process, as it has no relevance in Rel 5.0.
Issued
51
31NUP0031 7/19/2004
9. Control Mode Conversion

There are two options for Control Mode on the Control Complex: Non-integrated and Integrated. Non-integrated Control mode requires that the Control cards have S/W of the designation: A21215-x0-xx. Non-integrated Control mode requires the switch to be equipped with its own Call Processing and PNNI cards. Integrated Control mode requires that the Control cards have S/W of the designation: A21515-x0-xx. Integrated Control mode uses the resources on the Control card to perform Call Processing and PNNI Routing activities thus removing the need to have a separate Call Processing card and PNNI card on the switch. The Call Processing performance with the Integrated Control mode is not as fast as having a separate Call Processing and PNNI card. The 7470 switch cannot be directly upgraded from a Non-integrated mode of control to an Integrated mode of control. The system must first be upgraded to a Release 5.0 Non-integrated control mode and then converted to an Integrated control mode, once the system-wide upgrade has been completed. There is a special procedure for doing this later in this NUP. If converting to Integrated Control mode then the existing Call Processing and PNNI cards should be removed from the switch after the conversion.
9.1. Converting From Non-integrated Control Mode to Integrated Control Mode

9.1.1 Download the Application S/W to the Inactive Banks
Download the Integrated Application S/W (A21514-Hx-xx) to the inactive banks of the Control card(s) by following the procedure detailed in section A.2. Confirm that the S/W was successfully downloaded by issuing the following MNTI command:
MAINT OBJECT SLOT <slot_id>,
Where <slot_id> is the slot number of the Control card(s).
9.1.2.
Set the Control Mode to Integrated
Once the Integrated S/W was successfully downloaded to the inactive banks of the Control card(s) the Control Mode can be set to Integrated by issuing the following NMTI command:
CONFIG SYSTEM MORE CONTROL_MODE <INTEGRATED> PROCEED
Issued
52
31NUP0031 7/19/2004
9.1.3.
Integrated Control Mode Conversion Implications
The following points summarize the implications of the Integrated Control Mode Conversion. When converting from a Non-integrated control mode to an Integrated control mode in Rel 5.0, the control cards MUST be equipped with an ePM module and a 256MB flash disk. A Non-integrated to Integrated control mode conversion kit is required to perform the conversion. This conversion kit has a product part number of 909160-21. The Next Bank of each Control card is set to the Integrated Control application automatically. The Control card that was active at the time of the Control Mode change, reboots as the active Control card. The PNNI and Call Processing applications execute on the control card and any previously configured PNNI links, signalling links and SPVCs are brought back into service after suffering a service outage. All previously configured SVCs are released. All shelves previously assigned to a Call Processing Group are automatically moved to Call Processing Group 1, and a nodal alarm is raised to indicate this. An Application Mismatch alarm is raised for any currently installed service cards running either the PNNI or Call Processing applications, since these are not supported by the Integrated application. Each such card will reset once. These cards should be removed from the node after verifying that service with integrated mode is functioning. SVC billing is still performed using the Spooling card, provided one is installed and programmed. There is no service impact to PVCs. All signalling links configured on the Control application, that are in excess of the number supported by the Integrated application, are automatically removed from the 7470 database and an alarm is raised for each signalling link discarded. A database reconcile from the 5620 is performed automatically.
Issued
53
31NUP0031 7/19/2004
Appendix A: Downloading the Application S/W Generics

This section outlines the procedure for downloading Application Software (S/W) to the cards of the 7470 switch.
A.1. Release 5.0 application software & BootPROM firmware generics

Not all cards in a Rel 5.0 7470 MSP system will be upgraded to Rel 5.0 application software versions (generics). Please refer to the latest version of the Release Notice 31RN0042, for the actual application software versions to use, as well as the BootPROM firmware versions needed to support that software. Note: It is important to note that the proper BootPROM firmware load must be installed on the card before the application software can be installed. This is an upgrade task that must be considered before the day/night of the upgrade. Note: It is incumbent upon a qualified Alcatel Support representative to review the appropriate Release Notices to understand all implications associated with the release that will be used. Actual application software generics will change from load-set to load-set as the software release matures, hence the need to use the latest release notice (31RN0042).
Issued
54
31NUP0031 7/19/2004
A.2. Application S/W Generic Download Procedure

A.2.1. Specify the IP or CPSS Address
If the node has a direct IP network connection, and configured IP information, then perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK SOURCE IP_ADDR <IP_address>, where <IP_address> has the form: aaa.bbb.ccc.ddd. If the node does not have a direct IP network connection, then the software download must be performed via CPSS and the following NMTI operation should be performed: MAINT FILE_TRANSFER NETWORK SOURCE CPSS_ADDR DOMAIN <domain> NODE <node_number>, where <domain> and <node_number> specify the CPSS address of the NMS workstation. (typically domain = 33,000 and node_number = 1023).
A.2.2. Specify the User Name

Perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK USER_INFO USER_ID <user_name>, where <user_name> is the name of your NMS UNIX account.
A.2.3. Specify the Users Password

Perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK USER_INFO PASSWORD <password> , where <password> is the password of your NMS UNIX account (Note: the password will not be displayed).
A.2.4. Specify Path to the Location of the Application S/W Generic

Perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK FILE_INFO PATH <path>,
Issued
55
31NUP0031 7/19/2004
where <path> identifies the directory location for database storage. Ensure that the directory path has the proper access permissions for the UNIX account.
A.2.5. Specify the Name of the Application S/W Generic

Perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK FILE_INFO FILE <file_name>, where <file_name> identifies the name of the application software file. Refer to Table A-1 for the appropriate S/W Generic.
A.2.6. Download the Application S/W Generic to the Inactive S/W Bank
Determine which of the two S/W banks is the current and which one is not being used by performing the following NMTI operation: MAINT OBJECT SLOT <slot_number>. The Bank that has current next to it is currently being used and the bank that has ok next to it is not being used. These banks can be specified by BANK_1 and BANK_2. The non-current S/W bank is the one the S/W should be downloaded to. To download Application S/W perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK UPGRADE <slot_id>, where <slot_id> identifies the card slot. Start to download by performing the following NMTI operation: BANK_1 PROCEED (or BANK_2 PROCEED). NOTE: If the current S/W bank is selected, the following message will be displayed: Downloading to the current bank is not permitted. If this happens simply select the non-current bank to continue with the upgrade. NOTE: When the card is operating in BOOT mode software, it is possible to download Application S/W to either S/W Banks. By looking at the NMTI screen verify that the following messages are displayed:
Issued
56
31NUP0031 7/19/2004
Proceeding with upgrade, Initializing, x blocks transferred, Load received. The time for the Application S/W to download will vary for each card but may take from 2 to 5 minutes using IP, provided the 36170 node and the NMS workstation are on the same LAN. Once the Application S/W download has completed enter through NMTI: PROCEED.
Issued
57
31NUP0031 7/19/2004
Appendix B: Record Configuration Parameters and Backup the Switchs Database

This procedure is a necessary step for a Simplex Control Complex upgrade as the database is lost when the card is reset into the new load. This procedure is also required as a precautionary measure for a Redundant Control Complex upgrade. Should the upgrade fail, the back-up database will be used to restore the system.
B.1. Record the Configuration Parameters of the Switch

Since some of the HOUSE Menu configuration of the switch is not included in a backedup database this information will need to be manually recorded. Record all nodal configuration parameters including: the CPSS Node Number, the CPSS Domain Number, the CPSS Node Type, the CPSS Connection Details, the Default Router, the Sub-Net Mask, the IP Address, the Serial Port configuration, and the System Fabric configuration.
B.2. Backup/Restore the Switchs Database

The procedures used to backup and restore a backed-up database are very similar and they differ only at the final step. For this reason follow the procedure in this section for both backing-up a database and restoring a database. If a database backup is required execute steps B.2.1, B.2.2, B.2.3, B.2.4, B.2.5, and B.2.6. If a database restoration is required execute steps B.2.1, B.2.2, B.2.3, B.2.4, B.2.5, and B.2.7.
B.2.1. Specify the IP or CPSS Address

If the node has a direct IP network connection, and configured IP information, then perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK SOURCE IP_ADDR <IP_address>, where <IP_address> has the form: aaa.bbb.ccc.ddd. If the node does not have a direct IP network connection, then the database back-up must be performed via CPSS and the following NMTI operation should be performed: MAINT FILE_TRANSFER NETWORK SOURCE CPSS_ADDR DOMAIN <domain> NODE <node_number>, where <domain> and <node_number> specify the CPSS address of the NMS workstation. (typically domain = 33,000 and node_number = 1023).
Issued
58
31NUP0031 7/19/2004
B.2.2. Specify the User Name

Perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK USER_INFO USER_ID <user_name>, where <user_name> is the name of your NMS UNIX account.
B.2.3. Specify the Users Password

Perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK USER_INFO PASSWORD <password> , where <password> is the password of your NMS UNIX account (Note: the password will not be displayed).
B.2.4. Specify Path to the Location

Perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK FILE_INFO PATH <path>, where <path> identifies the directory location for database storage. Ensure that the directory path has the proper access permissions for the UNIX account.
B.2.5. Specify the File Name

Perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK FILE_INFO FILE <file_name>, where <file_name> will be the name used for the backup file.
B.2.6. To Backup the Switchs Database

Perform the following NMTI operation: MAINT FILE_TRANSFER NETWORK DATABASE BACK_UP PROCEED.
Issued
59
31NUP0031 7/19/2004
This process takes about 1-2 minutes and once the backup is complete the message Database Backup Completed will be displayed. If the process fails, verify all information entered above and retry the backup. If the process continues to fail, please contact your Alcatel representative.
B.2.7. To Restore the Switchs Database

Perform the following NMTI command: MAINT FILE_TRANSFER NETWORK DATABASE RESTORE PROCEED. Verify that the following messages are displayed: Initializing...Please Wait, Proceeding with restore, x bytes are transferred, Copying the database. Please wait, Database Restore completed, Control card is going to be reset now.
B.3. Set the Next Bank and Reset the Card

B.3.1. Set the Next Bank on the Card
Confirm that the proper S/W Generic is loaded on the inactive S/W bank by performing the following NMTI command: MAINT OBJECT SLOT <slot_id> . To set the Next Bank perform the following NMTI operation: MAINT OBJECT SLOT <slot_id> NEXT_BANK PROCEED, where <slot_id> identifies the card slot.
Issued
60
31NUP0031 7/19/2004
B.3.2. Replace the PM with the ePM (Optional)

If the card is to be upgraded with the new ePM then the card must be removed from the shelf and the PM must be swapped with the ePM. Refer to the appropriate Upgrade Kit as outlined in the Table B-1. Upgrade Kit Part Number Control Card (Both Nonintegrated and Integrated) Service Card (Call Processing, PNNI, and Data Spooling) 90-8477-02 90-8477-01
Table B-1 Upgrade Kit Part Numbers Once the PM is swapped with the ePM insert the card back into the shelf and it should initialize with the new S/W load. If this step is executed then step B.3.3 is not required. NOTE: If the card that is being upgraded with an ePM is a Control card then the new 256M SanDisk is required to replace the old SanDisk. This will be clear in the Upgrade Kit.
B.3.3. Reset the Card to Make the Next Bank Current

As stated above, if the card was previously removed for installation of the ePM, this step is not required. To reset the card with the new Application S/W perform the following NMTI operation: MAINT OBJECT SLOT <slot_id> RESET_CARD PROCEED, where <slot_id> identifies the card slot. The card will initialize with the new Release 5.0 application software load.
B.3.4. Confirm the Application Software was Downloaded Correctly.

Perform the following NMTI operation to ensure that the Application S/W has been properly downloaded and the card initialized successfully with it. MAINT OBJECT SLOT <slot_id> , where <slot_id> identifies the card slot.
Issued
61
31NUP0031 7/19/2004
B.4 Re-Configure the Switchs System Parameters (Simplex Only)

After a Simplex Control card is next-banked to a new S/W release, the switch will initialize with an empty database and the only method of accessing the switch is through the serial port. The Control Complex must be re-configured in order to restore the switchs system database and return the system to a normal state.
B.4.1
Re-configure the IP/CPSS Parameters
Access the node through a serial port and reconfigure the CPSS/IP parameters by performing the following NMTI operations: HOUSE MORE CPSS DOMAIN_NUMBER <cpss_domain_number> PROCEED, HOUSE MORE CPSS NODE_NUMBER <cpss_node_number> PROCEED, HOUSE MORE IP_ADDRESSES CTLIP <ip_node_address) PROCEED, HOUSE MORE IP_ADDRESSES DEF_ROUTER <ip_router_address> PROCEED, HOUSE MORE IP_ADDRESS SUBNET_MASK <ip_subnet_mask> PROCEED. NOTE: DO NOT restore the CPSS connection to the 5620 network manager at this time. If restoration of CPSS is performed with the system UCS slots unconfigured, all 5620managed links and paths terminating on those slots will be erased!!!
B.4.2. Reset the Control Card

Reset the Control card allowing the above changes to take effect by issuing the following NMTI command: HOUSE MORE CPSS PROG_TO_CURR PROCEED. If IP connectivity is not restored at this point, re-verify the IP parameters.
B.4.3. Re-Configure the Fabric Type

Re-Configure the system Fabric by issuing the following NMTI commands. For Standalone Simplex Fabric:
3LS TEC IPD Services & Support 62
Issued
31NUP0031 7/19/2004
CONFIG SYSTEM FABRIC EQUIPMENT STANDLONE SIMPLEX PROCEED. For Standalone Redundant Fabric: CONFIG SYSTEM FABRIC EQUIPMENT STANDALONE REDUNDANT PROCEED. For Switching Fabrics (with Switching Shelves): CONFIG SYSTEM FABRIC EQUIPMENT NUM_DSC <num_dsc_cards> PROCEED.
B.4.4. Re-Configure the Switchs Peripheral Shelves

Re-Configure the switchs Peripheral Shelves by issuing the following NMTI commands. For Dual Peripheral Shelves: No configuration required. For Low Speed (LS) Peripheral Shelves: CONFIG OBJECT SHELF P# TYPE SINGLE PROCEED, CONFIG OBJECT SHELF P# ISL_PORT HX-1 ATTACH #A PROCEED. For High Speed Peripheral Shelves: CONFIG OBJECT SHELF P# TYPE HIGH_SPEED PROCEED, CONFIG OBJECT SHELF P# ISL_PORT FX#-1 ATTACH #A PROCEED, CONFIG OBJECT SHELF P# ISL_PORT FX#-2 ATTACH #A PROCEED. For 350 Enhanced Broadband Access Shelves: CONFIG OBJECT SHELF P# TYPE HIGH_DENSITY PROCEED, CONFIG OBJECT SHELF P# ISL_PORT HX-1 ATTACH #A PROCEED,
Issued
63
31NUP0031 7/19/2004
CONFIG OBJECT SHELF P# ISL_PORT HX-2 ATTACH #A PROCEED.
B.4.5. Re-Configure all UCS Slots and Connect CPSS

Re-Configure all UCS slots by issuing the following NMTI command: CONFIG OBJECT SLOT CONFIG_ALL PROCEED. Verify that all slots have been properly configured for each shelf in the system by issuing the following NMTI command for each shelf: CONFIG SHOW_SLOTS P# . Confirm that all shelves and slots have been configured as they were in the earlier application S/W load and then re-connect the original CPSS connections by issuing the following NMTI command: CONFIG OBJECT RESOURCE CPPS # TO HOST <nms_ip_address> . NOTE: If restoration of CPSS is performed, with the system UCS slots unconfigured, all 5620-managed links and paths terminating on those slots, will be erased.
Issued
64
31NUP0031 7/19/2004
Appendix C: Nodal Downgrade Procedure

Every effort must be made to continue with a 5.0 upgrade; this downgrade procedure should not be attempted unless deemed absolutely necessary. Should it be necessary at any time during the upgrade to Release 5.0 to abort the upgrade, and return the system to its initial state, the cards are to be downgraded in the following order: 1. Downgrade all Interface cards. 2. Downgrade all Fabric cards. 3. Downgrade the Control cards.
C.1 Interface Card Downgrade Procedure

Line cards should be downgraded starting with the lowest numbered peripheral shelf first. Downgrade the line cards by selecting the memory bank with the original application load and resetting.
1. Set the next active bank by entering: MAINT OBJECT SLOT <slot_id> NEXT_BANK PROCEED where slot_id identifies the card slot. 2. Reset the card by entering:
MAINT OBJECT SLOT <slot_id> RESET_CARD PROCEED
where slot_id identifies the card slot.
Issued
65
31NUP0031 7/19/2004
3. Verify that no unusual alarms have been raised for the newly downgraded interface cards (NMTI): ALARMS > OUTSTANDING > ALL_ALARMS
4. Execute Steps (1) to (3) for each interface card downgrade. Note: The Interface card downgrade is now complete.
C.2 Fabric Card Downgrade Procedure

C.2.1 Multi-Shelf Redundant Fabric Downgrade Procedure
Fabric cards should be downgraded in pairs starting with the highest numbered shelf first. DSC cards should be downgraded first followed by DHUB or LSHUB cards. Downgrade the fabric cards by selecting the memory bank with the original application load and resetting. For example, downgrade the fabric cards to the old application software, in the following order: MAINT OBJECT SLOT *-S# NEXT_BANK PROCEED MAINT OBJECT SLOT *-S# RESET_CARD PROCEED MAINT OBJECT SLOT P#-H* NEXT_BANK PROCEED MAINT OBJECT SLOT P#-H* RESET_CARD PROCEED
MAINT OBJECT SLOT *-S1 NEXT_BANK PROCEED MAINT OBJECT SLOT *-S1 RESET_CARD PROCEED MAINT OBJECT SLOT P1-H* NEXT_BANK PROCEED MAINT OBJECT SLOT P1-H* RESET_CARD PROCEED
1. Verify that the fabric is error free by entering: MAINT SYSTEM FABRIC
Issued
66
31NUP0031 7/19/2004
2. Set the next active bank on the inactive DSC card by entering: MAINT OBJECT SLOT <slot_id> NEXT_BANK PROCEED
where slot_id identifies the inactive DSC card slot. 3. Reset the inactive DSC card to make the Next_Bank current. MAINT OBJECT SLOT <slot_id> RESET_CARD PROCEED where slot_id identifies the inactive DSC card slot. 4. Set the next active bank on the inactive HUB card by entering:
MAINT OBJECT SLOT <slot_id> NEXT_BANK PROCEED where slot_id identifies the inactive HUB card slot. 5. Reset inactive HUB card to make the Next_Bank current. MAINT OBJECT SLOT <slot_id> RESET_CARD PROCEED where slot_id identifies the inactive HUB card slot. 6. When all the inactive fabric pairs have been downgraded, verify that the fabric is error free: MAINT SYSTEM FABRIC
Issued
67
31NUP0031 7/19/2004
7. Check the alarm queue to make sure there are no alarms being reported from the active or inactive switching fabric. ALARMS OUTSTANDING ALL_ALARMS
8. Perform a fabric activity switch by entering: MAINT SYSTEM FABRIC FORCE_SWITCH PROCEED 9. Repeat steps 1-7 for the newly inactive fabric. 10. For the last time, verify that the fabric is error free by entering: MAINT SYSTEM FABRIC
Note: The multi-shelf redundant fabric downgrade is now complete.
C.2.2 Standalone Redundant Fabric Downgrade Procedure

1. Verify there are no Fabric demerits: MAINT SYSTEM FABRIC
2. Set the in-active HUB cards in-active software bank status to Next:
Issued
68
31NUP0031 7/19/2004
MAINT OBJECT SLOT P1-H* NEXT_BANK PROCEED
3. Downgrade the in-active HUB card to the old application software: MAINT OBJECT SLOT P1-H* RESET_CARD PROCEED 4. Verify there are no Fabric demerits: MAINT SYSTEM FABRIC 5. Release Fabric activity to the newly-downgraded HUB card:
MAINT SYSTEM FABRIC FORCE_SWITCH PROCEED 6. Repeat Steps 1 5 for the newly-inactive HUB card.
Note: The standalone redundant fabric downgrade is now complete.
C.3 Control Card Downgrade Procedure (with backup control card)

We recommend that a spare control card should be available before the upgrade. The spare CTL card should be pre-downloaded with the original software generic.
1. Remove both active and inactive control cards in slots P1-1 & P1-2 respectively. 2. Insert the spare control card into P1-1 which was made as a backup control card. 3. Once the control card comes up as active, insert one of the upgraded control cards into slot P1-2, wait until it comes up as inactive, and do a next bank of this card. 4. Pull out the inactive card, replace the ePM (Enhanced Processor Module) and PCMCIA flash disk with the old PM module and flash disk.
Issued
69
31NUP0031 7/19/2004
5. Plug the card into P1-2, wait until it comes up as inactive. 6. If the inactive control card contains the same release as the active control card, then go to step 7. Otherwise, download the original software generic into the inactive control card, do a next bank, reset the inactive control card, and wait until it comes up as inactive. 7. Force the 5620 to reconcile with the downgraded 7470 (if this does not happen automatically). This can be done by selecting the 7470 node on the 5620 map, and perform a Database Get from ObjectAll 8. Select the 7470 node from the 5620 map, and perform a List Paths, searching for paths which are Interrupted Via NMTI (IVN) 9. Clean up any paths that are shown to be Interrupted Via NMTI (IVN). a. This can be done by downloading the paths to the node and then uploading them. b. If step a fails, the paths can be disconnected and reconnected. c. If steps a & b fail, the paths have to be deleted and re-made by checking the path connections manually. Note: The control complex downgrade is now complete.
C.3.1 Control Card Downgrade Procedure with no backup control card

If both Active and Inactive control cards have Rel 5.0 in their current banks, and the original software in their in-active software banks, then you need to do the downgrade as follows: 1. Force the in-active control card into boot mode (main object slot ctl forceboot) 2. Wait until it comes up in boot mode, select next bank, pull it out. 3. Replace the ePM and PCMCIA flash disk with old PM module and flash disk. 4. Pull out the active control card, and plug the formally in-active control card with old PM and PCMCIA flash disk into slot P1-1. 5. Wait until it comes up with two LEDs (Status and active) flash red, use a Dummy Terminal to configure the nodes CTL IP, Default Router, CPSS address, then reset it. 6. Wait until it comes up, then restore the nodes original database.
Issued
70
31NUP0031 7/19/2004
7. Wait until it comes up, then plug the second control into slot P1-2, which will come up as inactive, do next bank, pull out the inactive control. 8. Replace the ePM and PCMCIA flash disk with old PM module and flash disk. 9. Plug it into slot P1-2, and wait until it comes up as the inactve control. 10. Force the 5620 to reconcile with the downgraded 7470 (if this does not happen automatically). This can be done by selecting the 7470 node on the 5620 map, and perform a Database Get from ObjectAll 11. Select the 7470 node from the 5620 map, and perform a List Paths, searching for paths which are Interrupted Via NMTI (IVN) 12. Clean up any paths that are shown to be Interrupted Via NMTI (IVN). a. This can be done by downloading the paths to the node and then uploading them. b. If step a fails, the paths can be disconnected and reconnected. c. If steps a & b fail, the paths have to be deleted and re-made by checking the path connections manually. Note: The control complex downgrade is now complete.
Issued
71
31NUP0031 7/19/2004
Appendix D: References
7470 MSP Rel 5.0 Release Notice Latest version of 31RN0042, downloadable from Technical Support web site below.
Technical support http://www.alcatel.com/support/ Technical Support Engineers are available to assist you 24 hours a day, 7 days a week. For the list of regional contact telephone and fax numbers, visit: http://www alcatel.com/support/ and click on the Global Support link.
Customer documentation http://www.alcatel.com/osds Product manuals and documentation updates are available through the Alcatel Support Documentation and Software Download service at Alcatel.com. If you are a new user and require access to this service, please contact your Alcatel sales representative.
Issued
72
31NUP0031 7/19/2004
Document History
Version 1.0 (Draft) 1.1 (Draft) Date 12/19/2001 01/24/2002 Author M. Horwood M. Horwood Creation Corrected various errors Removed irrelevant sections 1.2 (Draft) 1.3 (Issued) 01/24/2002 02/06/2002 M. Horwood M. Horwood Corrected various errors Corrected various errors Issued document 1.4 (Issued) 09/16/2002 M. Horwood Corrected various errors Added downgrade procedure 1.5 (Issued) 1.6 (Issued) 09/25/2002 10/18/2002 S Wall M. Horwood Added EDC Consideration Requirements Corrected errors in previous document version, header, and date information Updated part number information Updated boot prom information 1.7 (Issued) 10/22/2002 D. M. Wong Updated boot prom information on DS3 UFR, E3UFR, T1CFR and HSSI FR Corrected various errors Added SVC clearing information Removed software generic table & minor editing corrections. Reason
1.8 (Issued) 1.9 (Issued) 2.0
11/04/2002 01/08/2004 14 July 2004
M. Horwood M. Horwood W H Yim
Issued
73
Alcatel and logo are registered trademarks of Alcatel Networks Corporation. Information subject to change without notice. Copyright 2000-2004, Alcatel Networks Corporation. All rights reserved.
Corporate Headquarters 54 rue La Boetie 75008 Paris France Tel +33 1 4076 1010 Fax +33 1 4076-1400
Europe, Middle East and Africa Alcatel Telecom Limited Coldra Woods, Chepstow Road Newport Gwent NP18 2YB United Kingdom Tel. +44 (0) 1633 413600 Technical Assistance Centre: Tel +44 1633 413666 Fax +44 1633 413522
North America Alcatel Networks Corporation 600 March Road P.O. Box 13600 Kanata Ontario K2K 2E6 Canada Tel +1 613 591 3600 Fax +1 613 591 3680 Technical Assistance Centre: Tel +1 613 784-6100 Tel 1 888 252-2832 Fax +1 613 784-8900 Fax +1 613 784-8902 Fax +1 613 784-8905
Asia Pacific Alcatel Shanghai Bell AND/IPD TAC Yingdong Building No.58 New Jinqiao Road 201206 Pudong Shanghai P.R.China Technical Assistance Centre http://bndtac.alcatelsbell.com.cn/contact/

31NUP0031 7470 Rel 5

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

31NUP0031 7470 Rel 5

Загружено:

Авторское право:

Доступные форматы

31NUP0031

Version 2.0 (Issued) 14 July 2004

Alcatel 7470 Multi-Service Platform Release 5.0 Upgrade Procedure

Network Upgrade Procedure

3LS TEC IPD Services & Support

3.2.4. 3.2.5. 3.2.6. 3.2.7. 3.2.8. 3.2.9. 4.

3LS TEC IPD Services & Support

3LS TEC IPD Services & Support

Integrated Control Mode Conversion Implications ............................................................................ 53

3LS TEC IPD Services & Support

Upgrade the Control Complex

3LS TEC IPD Services & Support

New in Release 5.0

Upgrade the Fabric Cards

3LS TEC IPD Services & Support

Upgrade the Service Cards

Upgrade the IP Service Cards (ISC)

3LS TEC IPD Services & Support

Upgrade the Line Cards

3LS TEC IPD Services & Support

3LS TEC IPD Services & Support

Fabric Size Upgrade to 32k Cells

3LS TEC IPD Services & Support

Optional Control Mode Conversion

3LS TEC IPD Services & Support

1.2. New Hardware Introduced in Rel 5.0

The 4-port OC3/STM1 Cell Relay Card

3LS TEC IPD Services & Support

The 8-port DS3 Cell Relay Card

1.3 New Features Introduced in Rel 5.0

3LS TEC IPD Services & Support

ILMI 4.0 Support

Integrated CallP/PNNI/Data Spooling

Configurable Individual Alarm Severity

Increased Scalability of Address Translation

3LS TEC IPD Services & Support

Switched Services VBNs

PNNI Diagnostic Improvements

1.3.10 Default Fabric Type Change From 2k to 32k

3LS TEC IPD Services & Support

1.3.11 NMS Support for Static Routing Tables

1.3.12 4.5k connection support for DS3-2/E3-2 CR with eTM

1.3.13 RTD Measurement on Cell Relay Cards

1.3.14 RTD Measurement on Frame Relay Cards

1.3.15 Dynamic Channel Selection over ISLs

1.3.16 Multi-Port Ethernet VLAN Support

3LS TEC IPD Services & Support

1.3.17 Multi-Port Ethernet VC-VC Forwarding Support

1.3.18 In-band IP Support for Spooling

1.3.19 Inband IP Using SPVCs

1.4. System Requirements of Release 5.0 Features

3LS TEC IPD Services & Support

Service CTL Integ. Card-2 CTL Card-2 Card-2

Data Spooling Card

3LS TEC IPD Services & Support

1.5. Network Management (5620) Support

1.6. Important Points Vital to the Rel 5.0 Upgrade

3LS TEC IPD Services & Support

3LS TEC IPD Services & Support

The Control Complex Mode Conversion (Optional)

3LS TEC IPD Services & Support

3. Control Complex Upgrade