Nortel GGSN - HW Installation and Maintenance Guide - 411-5221-923

411-5221-923
Nortel GGSN
Hardware Installation and Maintenance
Guide
GGSN 6.0 Standard 06.09 August 2008
Nortel GGSN
Hardware Installation and Maintenance Guide
Document number: 411-5221-923

Product release: GGSN 6.0
Document version: Standard 06.09
Date: August 2008
Copyright Country of printing Confidentiality Legal statements Trademarks
Copyright © 2004–2008 Nortel Networks, All Rights Reserved

Originated in the United States of America/Canada
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing
NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR
IMPLIED. The information and/or products described in this document are subject to change without notice.
Nortel, Nortel Networks, the Nortel logo and the Globemark are trademarks of Nortel Networks.
All other trademarks are the property of their respective owners.

ii Copyright © 2004–2008 Nortel Networks
411-5221-923 Standard 06.09 August 2008

iii
Copyright © 2004–2008 Nortel Networks
Publication history
August 2008
GGSN6.0, Standard 06.09 release
Q01874195-01
Addeded “Appendix D: GGSN billing status verification CLI command

output on GGSN’s with SSC3 cards” on page D-1.
Added references to the new Appendix D, throughout the document.
August 2008
GGSN6.0, Standard 06.08 release
Added the following steps:
• Step 12 in “Single CMC card configuration” on page 4-35

• Step 24 and 25 in “Multiple CMC card configuration” on page 4-40
• Step 27 in “Single CMC2 card configuration” on page 4-51
• Step 34 in “Multiple CMC2 card configuration” on page 4-57
• Step 10 and 11 in “Aborting CMC2 to CMC3 Upgrade” on page 4-
67
• Step 27 and 29 in “Single CM3 card configuration” on page 4-72
• Step 35 and 37 in “Multiple CMC3 card configuration” on page 4-78
June 2008
GGSN6.0, Preliminary 06.07
Modified some references to GGSN5.0.1 and GGSN4.1.1.
GGSN6.0, Preliminary 06.06
Nortel GGSN Hardware Installation and Maintenance Guide GGSN 6.0

iv Publication history Copyright © 2004–2008 Nortel Networks
Modified/Deleted references to GGSN5.0 under the following sections:
• “Subscriber Service Card (SSC3)” on page 1-7

• “Single CMC card configuration” on page 4-35
• “Single CMC2 card configuration” on page 4-51
• “Multiple CMC2 card configuration” on page 4-57
• “Single CM3 card configuration” on page 4-72
• “Multiple CMC3 card configuration” on page 4-78
• “Prerequisites for SSC-2 to SSC-3 upgrade” on page 4-91
• “SSC types” on page B-13
• “Update SSC3 XFPGA firmware” on page C-27
GGSN 6.0, Preliminary 06.05.
Added step 14 in “SSM bootrom upgrade” on page C-19, and added

the procedure “Update SSC3 XFPGA firmware” on page C-27.
Modified steps 16, 23 and 24 of Multiple CMC card configuration

procedure. Modified step 34 of Multiple CMC3 card configuration
procedure.
May 2008
Modified Figure i, "PC05 Documentation Roadmap" on page vii
May 2008
GGSN 6.0, Preliminary 06.02. This is the preliminary release of this
document.
February 2008
Draft 06.01 release for GPRS9 and UMTS6 (GGSN 6.0). This is the
initial release of this document for GGSN 6.0.
411-5221-923 Standard 06.09 August 2008

Publication history v
May 2006
Preliminary 05.08, GGSN 5.0. Corrected for SME comments and
change requests.
April 2006
change requests.

design document changes.
March 2006
January 2006
December 2005
Preliminary 05.03, GGSN 5.0. Corrected for SME comments about
bootrom versions.
Preliminary 05.02, GGSN 5.0.
October 2005
Draft 05.01 release for GPRS 7 and UMTS5 (GGSN 5.0). This is the
initial release of this document for GGSN 5.0.
July 2005
Standard 03.10 release for GPRS 6.1 and UMTS 4.1 (GGSN 4.1).
Preliminary 03.08 release for GPRS 6.1 and UMTS 4.1 (GGSN 4.1).
June 2005

vi Publication history Copyright © 2004–2008 Nortel Networks
May 2005
March 2005
February 2005
Draft 03.01 release for GPRS 6.1 and UMTS 4.1 (GGSN 4.1).
December 2004
August 2004
July 2004
Draft 02.01 release for GPRS 6.0 and UMTS 4.0 (GGSN 4.0).
April 2004
January 2004
Preliminary 01.01release for GPRS 5.0 and UMTS 3.0 (GGSN 3.2).
411-5221-923 Standard 06.09 August 2008

Publication history i
Contents 1
About this document v
Before you begin v
Text conventions vi
How to get help vi
Related documents 1-vii
Roadmap to Packet Core 05 documentation vii
Specifications vii
Passport documentation ix
Nortel Wireless Network Management x
Preside Multiservice Data Manager (MDM) documentation xi
Related training xi
Indication of hypertext links xi
Nortel branding xi
Nortel GGSN hardware overview 1-1

Introduction 1-1
Chassis cards 1-3
Switch Fabric Card (SFC1/SFC2) 1-3
SFC1 card 1-3
Control Management Card (CMC2/CMC3) 1-4
Subscriber Service Card (SSC2) 1-7
Subscriber Service Card (SSC3) 1-7
Line cards 1-8
Types of line cards 1-8
Optical fiber capabilities 1-8
Fan tray and filter 1-8
Optional AC Power Shelf 1-9
Power modules 1-9
Chassis physical installation 2-1

Safety 2-1
Site requirements 2-1
Location 2-2
Power requirements 2-2
Tools required for installation 2-2
AC plug types 2-3
Rack requirements for the GGSN 2-4
Unpacking the system 2-5
Confirming the shipment 2-5
Installing the SSG chassis in the rack 2-6
Installing in a standard 19-inch rack 2-6
Installing the cable management bezel 2-7
Installing in a 23-inch rack 2-8
Installing the AC Power Shelf (optional) 2-9
Installing the empty AC Power Shelf 2-9
Installing power modules 2-13

ii Publication history Copyright © 2004–2008 Nortel Networks
Installing DC power (No AC Power Shelf) 2-14

Attaching a ground 2-15
Connecting –48 VDC sources 2-16
Using wire and lugs 2-17
Installing cards in the chassis 2-17
General card installation instructions 2-19
Installing an SFC 2-21
Installing a CMC 2-21
Installing an SSC2/SSC3 2-22
Installing Line Cards 2-22
Connecting external cabling 2-24
Cable routing 2-25
Connecting to the CMC CONSOLE port for Quickstart 2-25
Connecting to the ENET MGMT port for a LAN connection 2-25
Connecting cables to ALC ports 2-27
Connecting optical cables 2-27
Connecting coaxial cables 2-28
Connecting the alarm cable to the chassis 2-28
Initial startup and configuration 3-1

Before beginning 3-1
Launching the terminal program 3-1
Applying power to the chassis 3-2
Verifying connectivity to the terminal 3-2
Confirming initial hardware operation 3-2
Chassis LEDs 3-2
Card Status and Active LED 3-3
Performing the quickstart 3-4
Quickstart log 3-8
Using the CLI 3-8
Configuring the Nortel GGSN 3-9
Line Card Configuration 3-9
Logging out 3-9
Troubleshooting the installation 3-9
General Indications 3-10
Using chassis alarm and status indicators 3-10
Using card Status and Active indicators 3-11
Maintenance, repair, and upgrade 4-1

Monitoring system activity 4-1
Front-panel indicators 4-1
Software indications 4-2
Using chassis alarms 4-2
Performing periodic maintenance 4-2
Replacing a fan filter 4-2
Hard drive maintenance 4-4
Updating the software 4-9
Checking software version number 4-10
Obtaining a software patch 4-10
Powering down the chassis 4-11
411-5221-923 Standard 06.09 August 2008

Publication history iii
Logging out 4-11

Shutting off power 4-11
Making field repairs 4-12
Replacing a card 4-12
Abort CMC2 to CMC3 Upgrade 4-67
Replacing a fan tray 4-101
Returning components to Nortel Networks 4-103
Appendix A: Nortel GGSN specifications A-1

Physical specifications A-1
Chassis size and weight A-1
Power requirements A-1
Temperature requirements A-1
Facility requirements A-2
Chassis location A-2
Space around chassis A-2
Compliance A-2
Safety A-2
EMC A-2
Certifications A-3
Appendix B: Hardware reference B-1

Chassis B-1
Chassis alarm connector pinout B-3
Chassis rear view B-3
Switch Fabric Card (SFC) B-6
Control and Management Card (CMC) B-7
CMC types B-8
CMC CONSOLE connector pinout B-12
Subscriber Service Card (SSC) B-12
Line cards B-16
OC3 ATM Line Card (OC3 ALC) B-16
Fast Ethernet Line Card (FELC) B-18
Gigabit Ethernet Line Card (GELC) B-21
AC Power Shelf B-24
Appendix C: Product maintenance procedures C-1

Manual GGSN shutdown, resync, or CMC switchover C-1
Move G-CDR files from standby CMC C-4
CMC Upgrade/Downgrade Preparation C-6
Boot CMC card from network C-12
Boot a CMC card using tftp C-12
CMC bootrom upgrade C-14
SSM bootrom upgrade C-19
Update SSC3 XFPGA firmware C-27
CMC2 Server Port Migration C-33
Types of Migration C-33
Migration of CMC2 Server Ports to FELC C-34
Migration of CMC2 Server Ports to GELC C-38
Migration of CMC2 Server Ports to ALC C-42

iv Publication history Copyright © 2004–2008 Nortel Networks
Migration of auxiliary management CMC2 server port C-47
Appendix D: GGSN billing status verification CLI command output

on GGSN’s with SSC3 cards D-1
Impact D-1
Details D-2
List of terms E-1
411-5221-923 Standard 06.09 August 2008

v
About this document 2

The Nortel Gateway GPRS Support Node (GGSN) provides
interworking with external packet-switches networks and is connected
with SGSNs via an IP-based packet domain PLMN backbone network.
GGSN features include VPNs, policy routing, firewalls, traffic shaping,
and content redirection.
The GGSN system consists of:

• Nortel GGSN, a rack-mounted chassis with a series of cards
mounted inside, and including a scalable multi threaded operating
system
• Service Creation System (SCS), a powerful graphical software
application.
Before you begin 2

This guide provides the necessary information to properly install and
commission the Nortel GGSN, and to maintain and repair the system
hardware.
• What’s covered in this manual:

This manual provides instructions for installing the Nortel GGSN
chassis and cards, installing the optional AC Power Shelf,
connecting cables, checking for basic operation, and performing
hardware monitoring, updates, and repairs.
• When to use this manual:

Use the information in this manual for initial installation and startup
of the Nortel GGSN, and for ongoing hardware operation,
maintenance, and repair.
• Who should use this manual:

This manual is intended for installation personnel and hardware
maintenance personnel.

vi About this document Copyright © 2004–2008 Nortel Networks
Text conventions 2
This guide uses the following text conventions:
angle brackets (< >) Indicate that you choose the text to enter based
on the description inside the brackets. Do not type
the brackets when entering the command.
Example: If the command syntax is
ping <ip_address>, you enter
ping 192.32.10.12
bold Courier text Indicates command names and options and text
that you need to enter.
Example: Use the dinfo command.
Example: Enter show ip {alerts|routes}.
italic text Indicates new terms, book titles, and variables in
command syntax descriptions. Where a variable is
two or more words, the words are connected by
an underscore.
Example: If the command syntax is
show at <valid_route>, valid_route is one
variable and you substitute one value for it.
plain Courier Indicates command syntax and system output, for
text example, prompts and system messages.
Example: Set Trap Monitor Filters
How to get help 2

If you purchased a service contract for your Nortel* product from a
distributor or authorized reseller, contact the technical support staff for
that distributor or reseller for assistance.
If you purchased a Nortel service program, contact Nortel Technical

Solutions Centers.
411-5221-923 Standard 06.09 August 2008

About this document vii
Related documents 2
Roadmap to Packet Core 05 documentation
Figure i shows the NTPs in the documentation suite for PC05.
Figure i
PC05 Documentation Roadmap
Fault and
Planning and Installation and Operations and Performance
Concepts Upgrading
Engineering Commissioning Administration Management
GGSN06 GGSN and SCS SGSN/GPRS SGSN Provisioning SGSN SGSN

Documentation New in this Release Upgrade Procedures Accounting Monitoring Guide
Roadmap 411-5221-200 411-5221-307 411-5221-904 411-5221-312 411-5221-050
411-5221-004
SGSN SGSN/UMTS GGSN Hardware SGSN SGSN
About the What's New Upgrade Administration Components
Installation and
UMTS Network 411-5221-202 411-5221-308 411-5221-313 411-5221-060
Maintenance Guide
411-8111-502
411-5221-923
Packet Core SCS and GGSN GGSN Command
SGSN
Terminology Conformance Guide Upgrades Line Interface (CLI)
GGSN Provisioning Administration
411-8111-804 411-5221-201 411-5221-309 Guide
Procedures 411-5221-313
411-5221-922
SGSN 411-5221-927
SGSN AN GGSN SGSN
Call Detail Records
Overview Upgrade User’s Guide Alarms
411-5221-204
411-5221-311 411-5221-310 411-5221-926 411-5221-500
SGSN
Core Network
GGSN Billing Samples GGSN Provisioning Troubleshooting
User’s Guide 411-5221-205 Procedures Guide
411-5221-926 411-5221-927
GGSN 411-5221-501
Billing Samples
GGSN RADIUS GGSN Corbashell GGSN Alarms
411-5221-206
Interface Guide CLI Guide Reference Manual
411-5221-928 411-5221-929 411-5221-921
SGSN Planning
& Engineering
411-5221-314 SIG GGSN
SIG Monitoring Guide
User Guide
User Guide 411-5221-924
411-5221-975
411-5221-975 GGSN
User’s Guide GGSN
411-5221-926 User’s Guide
411-5221-926
SIG
User Guide GGSN Corbashell
411-5221-975 CLI Guide
411-5221-929
GGSN Corbashell
CLI Guide SIG
411-5221-929 User Guide
411-5221-975
Specifications
For more information about the GPRS interfaces and protocols referred
to in this document, refer to the following specifications:
• GSM 04.64 (V8.7.0), “Digital cellular telecommunications system
(Phase 2+); General Packet Radio Service (GPRS); Mobile Station

viii About this document Copyright © 2004–2008 Nortel Networks
– Serving GPRS Support Node (MS - SGSN) Logical Link Control

(LLC) layer specification”
(Phase 2+); General Packet Radio Service (GPRS); Mobile Station
(MS) – Serving GPRS Support Node (SGSN); Subnetwork
Dependent Convergence Protocol (SNDCP)”
• GSM TS 08.14 (V8.0.0), “Digital cellular telecommunications
system (Phase 2+); General Packet Radio Service (GPRS); Base
Station System (BSS) - Serving GPRS Support Node (SGSN)
interface; Gb interface Layer 1”
• GSM 08.16, Digital cellular telecommunications system (Phase
2+); General Packet Radio Service (GPRS); Base Station System
(BSS) - Serving GPRS Support Node (SGSN); Network Service
(Phase 2+); General Packet Radio Service (GPRS); Base Station
System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS
Protocol (BSSGP)”
• 3GPP TS 03.33 (V8.1.0), “Lawful Interception; Stage 2 (Release
99)”
• 3GPP TS 09.60 (V7.6.0), “Digital cellular telecommunications
system (Phase 2+); General Packet Radio Service (GPRS); Base
Station System (BSS) - Serving GPRS Support Node (SGSN);
GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface”
• 3G TS 23.060, (V4.9.0), “GPRS Service Description. Stage 2”
• 3GPP TS 23.078, (V4.11.1), “Camel Service Description; Stage 2”
• 3GPP TS 23.040 (V4.8.0), “Technical realization of the Short
Message Service (SMS); Point-to Point (PP)”
• 3GPP TS 24.008 (V4.14.0), “Mobile radio interface layer 3
specification; Core Network Protocols – Stage 3”
• 3GPP TS 24.011 (V4.1.1), “Point-to-Point Short Message Service
(SMS) support on mobile radio interface”
• 3GPP TS 29.002 (V4.15.0), “SGSN Mobile Application Part (MAP)
Specification”
• 3GPP TS 29.016 (V4.1.0), “SGSN –Visitors Location Register
(VLR) Gs interface network service specification”
• 3GPP TS 29.018 (V4.5.0), “General Packet Radio Service (GPRS);
Serving GPRS Support Node (SGSN) –Visitors Location Register
(VLR); Gs interface layer 3 specification”
411-5221-923 Standard 06.09 August 2008

About this document ix
• 3GPP TS 29.060 (V4.11.0), “General Packet Radio Service

(GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp
Interface”
• 3GPP TS 29.078 (V4.8.0), “Camel Phase 3, Camel Application
Part (CAP) Specification”
• 3GPP TS 32.015 (V3.6.0), “GSM call and event data for the packet
switched domain”
• 3GPP TS 33.106 (V4.0.0), “Lawful Interception Requirements”
• 3GPP TS 33.107 (V4.3.0), “Technical Specification Group Services
and Systems Aspects; 3G Security; Lawful Interception
Architecture and Functions”
Passport documentation
Refer to the following NTPs in the Passport suite for additional
information relative to the Passport platform:
• Passport 15000, 20000 Hardware Description (241-1501-200)
• Passport 15000, 20000 Site Requirements and Preparation Guide
(241-1501-205)
• Passport 15000, 20000 Hardware Installation, Maintenance and
Upgrade (241-1501-240)
• Passport 7400, 15000, 20000 Documentation Guide (241-5701-
001)
• Passport 7400, 15000, 20000 List of Terms (241-5701-005)
• Passport 7400, 15000, 20000 Overview (241-5701-030)
• Passport 7400, 15000, 20000 Management System User Interface
Guide (241-5701-045)
• Passport 7400, 15000, 20000 Commands (241-5701-050)
• Passport 7400, 15000, 20000 Command Summary Card (241-
5701-053)
• Passport 7400, 15000, 20000 Components (241-5701-060)
• Passport 7400, 15000, 20000 Software Installation Guide (241-
5701-270)
• Passport 6400, 7400, 15000, 20000 Alarms (241-5701-500)
• Passport 7400, 15000, 20000 Trace Guide (241-5701-510)
• Passport 7400, 15000, 20000 Troubleshooting Guide (241-5701-
520)
• Passport 7400, 15000, 20000 Configuration Guide (241-5701-600)
• Passport 7400, 15000, 20000 User Access Guide (241-5701-605)

x About this document Copyright © 2004–2008 Nortel Networks
• Passport 7400, 15000, 20000 Data Collection Guide (241-5701-

611)
• Passport 7400, 15000, 20000 FP Configuration Reference (241-
5701-615)
• Passport 7400, 15000, 20000 Accounting Fundamentals (241-
5701-650)
• Passport 7400, 15000, 20000 ATM Overview (241-5701-700)
• Passport 7400, 15000, 20000 ATM Routing and Signaling
Fundamentals (241-5701-702)
• Passport 7400, 15000, 20000 ATM Traffic Management
Fundamentals (241-5701-705)
• Passport 7400, 15000, 20000 ATM Traffic Shaping and Policing
(241-5701-706)
• Passport 7400, 15000, 20000 ATM Queuing and Scheduling (241-
5701-707)
• Passport 7400, 15000, 20000 ATM Configuration Guide (241-
5701-710)
• Passport 7400, 15000, 20000 ATM Monitoring and Troubleshooting
Guide (241-5701-715)
• Passport 7400, 15000, 20000 Understanding IP (241-5701-805)
• Passport 7400, 15000, 20000 Configuring IP (241-5701-810)
• Passport 7400, 15000, 20000 Frame Relay Fundamentals (241-
5701-901)
• Passport 7400, 15000, 20000 Configuring Frame Relay (241-5701-
902)
• Passport 7400, 15000, 20000 Frame Relay to ATM Interworking
Guide (241-5701-920)
• Passport 7400 Hardware Description (241-7401-200)
• Passport 7400 Hardware Installation, Maintenance and Upgrade
(241-7401-240)
Nortel Wireless Network Management

Refer to Nortel Wireless Network Management System
Documentation Guide (411-5221-003) for a complete list of NTPs in
the Wireless Network Management documentation suite.
411-5221-923 Standard 06.09 August 2008

About this document xi
Preside Multiservice Data Manager (MDM) documentation

Refer to the following NTPs in the Preside MDM suite for additional
information about Passport OA&M:
• Preside MDM Fault Management User Guide (241-6001-011)
• Preside MDM Configuration Management for Passport User Guide
(241-6001-023)
• Preside MDM Administrator Guide (241-6001-303)
• Preside MDM Management Data Provider User Guide (241-6001-
309)
• Preside MDM Workstation Utilities User Guide (241-6001-804)
• Preside MDM MDP Data Formats Reference Guide (241-6001-
806)
Related training 2
For questions regarding training courses for the SGSN, please contact
your local Nortel representative for the latest course identification,
availability, and training center location.
Indication of hypertext links 2

Hypertext links in this document are indicated in blue. If viewing a PDF
version of this document, click on the blue text to jump to the
associated section or page.
Nortel branding 2
Nortel is changing the branding of some of its product lines. Part of this
effort includes changing the names of the products. New product names
have been created using the following format:
Nortel <function> <model>
where:
– <function> describes what function the product performs.
– <model> is a model series number.
For example, the Baystack 450 product has been renamed as the
Nortel Ethernet Switch 450. Some of the new product names are
quite lengthy. To make our documents easier to read, the product
names are shortened after their first occurrence. For example, the
Nortel Ethernet Switch 450 product name is referred to as the
Ethernet Switch 450 for second and subsequent occurrences.
To alleviate any confusion the rebranding might cause, Table i and

Table ii are job aids to assist the end user in reconciling inconsistent

xii About this document Copyright © 2004–2008 Nortel Networks
product terminology across multiple documents. During the transition,

both the existing product names and the new product names may
appear in the documentation and software.
Table i details the original product names and their corresponding new
and abbreviated product names. Table ii details the new product
names to the original names.
Table i
Original product names mapped to new names
Original Name(s) New Name Short Name Function
Alteon Application Nortel Applications Switch Applications

Switch xxxx xxxx Switch xxxx
Alteon Web Switch 184 Nortel Web Switch 184 Web

Switch 184
BayStack 450 Nortel Ethernet Switch 450 Ethernet

Switch 450
BPS2000 2-port SFP Nortel Ethernet Switch 2-port

GBIC MDA SFP GBIC MDA
CCN CS Nortel GSM/UMTS MSC MSC Mobile Switching

(DMS MSC) Center
CCN HLR Nortel GSM/UMTS HLR 100 HLR 100 Home Location
(DMS HLR) Register
Combined MSC and Nortel GSM/UMTS Combined Combined

HLR MSC/HLR MSC/HLR
(DMS Trinode)
Contivity xxxx Secure IP Nortel VPN Router xxxx VPN Router

Services Gateway xxxx
DMS Gateway Mobile Nortel GSM/UMTS MSC MSC Server Mobile Switching
Switching Center Server Center
(GMSC)
GPP Nortel GSM/UMTS IWF IWF Interworking Function
HSS Nortel GSM/UMTS HSS HSS Home Subscriber

Server
—sheet 1 of 3—
411-5221-923 Standard 06.09 August 2008

About this document xiii
Table i
Original product names mapped to new names (continued)
iBTS Nortel BTS xxxx BTS xxxx Base Transceiver

Station
IMS Solution Nortel IMS IMS IP Multimedia

Subsystem
NIMS-PrOptima™ for NIMS-PrOptima™ for Network Information

Preside for Wireless W-NMSa Management System
Internet & Wireless Network
Management System
Nortel Networks Secure Nortel VPN Router xxxx VPN Router

Router xxxx xxxx
Offline Configuration for Wireless Provisioning System WPS for Wireless Provisioning
Access Networks for Access b Access System
(OCAN)
Passport 7400 (7K) Nortel Multiservice Switch Multiservice

7400 Switch 7400

15000 Switch 15000

20000 Switch 20000
Preside for Wireless Nortel Wireless Network W-NMS Network Management

Internet (PWI) Management System System for Wireless
Networks
RNC Nortel UMTS RNC xxxx RNC xxxx
Shasta 5000 BSN Nortel IP Services Edge IP Services

Router 5500 Edge Router
5500
Univity GGSN Nortel GGSN GGSN Gateway GPRS

(Shasta GGSN) Support Node
Univity HLR c Nortel GSM/UMTS HLR 200 HLR 200 Home Location
Register
Univity MLC Nortel MLC MLC Mobile Location

(MLC) Center
—sheet 2 of 3—

xiv About this document Copyright © 2004–2008 Nortel Networks
Table i
Original product names mapped to new names (continued)
Univity SGSN Nortel SGSN SGSN Serving GPRS

(SGSN, (Nortel SGSN/GPRS (SGSN/GPRS, Support Node
GPRS SGSN, Nortel SGSN/UMTS SGSN/UMTS
UMTS SGSN, -use where required to -use where
USGSN or U-SGSN) differentiate technology.) required to
differentiate
technology.)
Univity Signaling Nortel GSM/UMTS SIG SIG Signaling Interworking

Gateway (SIG d, Gateway
SS7-IP Gateway)
UMGW (MGW, Nortel GSM/UMTS MGW MGW Media Gateway

Passport Voice
Gateway (PVG))
Wireless Gateway (WG) See the following:

NOTE: Configuration NOT - Nortel SGSN
supported in PC04 and - Nortel GSM/UMTS MGW
beyond, is supported in OAM.
—sheet 3 of 3—
a. NIMS PrOptima™ is a sub-component of W-NMS
b. WPS for Access is a sub-component of W-NMS
c. May have also been referred to as Everest HLR
d. May have also been referred to as HP SIG
Table ii
New product names mapped to original name(s)
New Name Short Name Original Name(s)
Nortel Ethernet Switch 2-port SFP BPS2000 2-port SFP GBIC

GBIC MDA MDA
Nortel Applications Switch xxxx Applications Switch xxxx Alteon Application Switch
xxxx
Nortel BTS xxxx BTS xxxx iBTS
Nortel Ethernet Switch 450 Ethernet Switch 450 BayStack 450
Nortel GGSN GGSN Univity GGSN, Shasta

GGSN
—sheet 1 of 3—
411-5221-923 Standard 06.09 August 2008

About this document xv
Table ii
New product names mapped to original name(s) (continued)
Nortel GSM/UMTS Combined Combined MSC/HLR Combined MSC and HLR,

MSC/HLR DMS Trinode
Nortel GSM/UMTS HLR 100 HLR 100 CCN HLR, DMS HLR
Nortel GSM/UMTS HLR 200 HLR 200 Univity HLR a
Nortel GSM/UMTS HSS HSS HSS
Nortel GSM/UMTS IWF IWF GPP
Nortel GSM/UMTS MGW MGW UMGW (function of a

Wireless Gateway), Passport
Voice Gateway (PVG)
Nortel GSM/UMTS MSC MSC CCN CS,

DMS MSC
Nortel GSM/UMTS MSC Server MSC Server DMS Gateway Mobile

Switching Center (GMSC)
Nortel GSM/UMTS SIG SIG Univity Signaling Gateway,

SIG b,
SS7-IP Gateway
Nortel IMS IMS IMS Solution
Nortel IP Services Edge Router IP Services Edge Router 5500 Shasta 5000 BSN
5500
NIMS-PrOptima™ for W-NMS c NIMS-PrOptima™ for

Preside for Wireless
Internet
Nortel MLC MLC Univity MLC, MLC
Nortel Multiservice Switch 7400 Multiservice Switch 7400 Passport 7400 (7K)
Nortel VPN Router xxxx VPN Router xxxx Contivity xxxx Secure IP
Services Gateway,
Nortel Networks Secure
Router xxxx
—sheet 2 of 3—

xvi About this document Copyright © 2004–2008 Nortel Networks
Table ii
New product names mapped to original name(s) (continued)
Nortel SGSN: SGSN Univity SGSN,

- Nortel SGSN/GPRS SGSN/GPRS GPRS SGSN,
- Nortel SGSN/UMTS SGSN/UMTS) UMTS SGSN,
U-SGSN, or USGSN
function of a Wireless
Gateway
Nortel UMTS RNC xxxx RNC xxxx RNC
Nortel Web Switch 184 Web Switch 184 Alteon Web Switch 184
Nortel Wireless Network W-NMS Preside for Wireless

Management System Internet (PWI)
Wireless Provisioning System for WPS for Access Offline Configuration for
Access d Access Networks (OCAN)
—sheet 3 of 3—
a. May also have been referred to as Everest HLR
b. May also have been referred to as HP SIG
c. NIMS PrOptima™ is a sub-component of W-NMS
d. WPS for Access is a sub-component of W-NMS
411-5221-923 Standard 06.09 August 2008

1-1
Nortel GGSN hardware overview 1

Introduction 1
The Shasta 5000 Broadband Service Node is a modular service
creation system. The number and type of actual components that
make up a system depend on the configuration at a particular site. The
chassis supports various combinations of services by accommodating
different combinations of cards.
The SSG (Figure 1-1) of Nortel GGSN consists of the following

components:
• Chassis, with fan tray and card cage
• Cards—Each chassis has slots for up to 14 cards, as follows
— Switch Fabric Card (SFC1/SFC2): one required, plus one
additional card for redundancy—slots allowed: 7, 8
— Control and Management Card (CMC3): one required, plus one
additional card for redundancy—slots allowed: 13, 14
— Subscriber Service Card (SSC2/SSC3): Maximum of six cards
per chassis—slots allowed: 1–6, 9–13
— Line cards, such as the OC3 ATM Line Card: typically one to six
cards per chassis—slots allowed: 1–6, 9–13
• AC Power Shelf (if a source of –48 VDC power is not available),
containing four power modules.

1-2 Nortel GGSN hardware overview Copyright © 2004–2008 Nortel Networks
Figure 1-1
Major components of the SSG
CMC
CMC
SSC Reset
SSC Reset Disk
ALC Disk
ALC
SFC Activity
SFC Activity Signal
ALC Signal Sync
ALC Sync
RDI
SSC Activity
RDI
SSC Activity Signal

SSC Signal Sync
SSC
Chassis with Cards
RDI
Sync t1
RDI MM Por
MM Por
t1
Activity Eject
Activity Signal Eject

PCMCIA
Signal Sync
t1 RDI PCMCIA P
MM Por Sync O
RDI P E
t1 SSM1 us R
MM Por Activity Stat E
O N T
SSM1 us R E 1
Activity Signal Stat Activity
N T T
E 1 Speed
Signal Sync
Activity T Link P
RDI Speed
Sync t2 SSM2 us Link O
RDI MM Por Stat P E R
t2 SSM2 us O N T
MM Por Activity Stat Activity E R E
N 2
T T
Activity Signal Activity E 2 Speed
Sync SSM3 us T Link
Signal Stat Speed M
t2 RDI SSM3 us Link G
MM Por Sync E
SSM1 us RDI Stat Activity M N M
Stat t2 E G 1
SSM1 us MM Por Activity Activity N M
E
Stat Activity T
SSM1 us Activity Signal SSM4 us E 1 Speed
Stat T
Stat Activity Signal Sync SSM4 us Speed
Link
SSM1 us SSM2 us
P
Stat Activity
RDI Stat Activity Link M O
Stat Sync t3 P O
SSM2 us R
Activity
RDI MM Por Activity M O D T
Stat Activity t3 O R E
SSM2 us MM Por Activity D M
Stat Activity T
SSM2 us Activity Signal SSM1 E
C P
SSM3 us M O
Stat Activity SSM1 O
Stat
Signal Sync C P R
SSM3 us O N
Activity Activity Port 3
RDI O T
Stat Sync R T
SSM3 us MM
RDI SSM2 N R
Stat Activity t3 T T
SSM3 us MM Por Activity SSM2 O
SSM4 us R L
Stat Activity Stat Activity Signal O
SSM4 us SSM3 L
Activity Stat Activity Signal Sync
SSM4 us RDI SSM3
Stat Activity Sync t4 Status
SSM4 us RDI MM Por
Stat Activity t4 SSM4 Status Active
SSM1 MM Por
Activity SSM4 Status Active
SSM1 Status Active
SSM1 Status
SSM2 t4 Active
SSM1 MM Por
SSM2 Port 4 Status Active
MM
SSM2 Status Active
SSM3
SSM2 Status Active
SSM3
Status Active
SSM3
SSM4 Status Active 14
SSM3
SSM4
Status
SSM4
Status
Active
Status
Active
Active
10
11
12
Fan Tray
9
BSN
Active
A 5000
8
SHAST
7
Strap
6 s
Ground
Cut-off
Fan Filter
Fan Statu
5 s
Alarm
4 Contact
Alarm
3
2 Status
Alarm
1
Critical
Major
Minor
AC Power Shelf
OK
PWR
FAULT
OK
PWR Temp
FAULT 1 LIM
OK
PWR Temp
FAULT 1 LIM
OK
PWR Temp
FAULT 1 LIM
Temp
1 LIM
CB2
AC
R
POWE 2
1
CB1
10182FA
The chassis consists of a card cage, with 14 slots for cards; a fan tray
for cooling; power entry and distribution; and the backplane. The
chassis mounts in a standard 19-inch rack; with rack extenders it
mounts in a 23-inch rack. The chassis requires a source of –48 VDC
power.
Front-panel LEDs provide chassis alarm status and fan status. A front-
panel alarm cutoff switch shuts off the alarm output, a feature that is
411-5221-923 Standard 06.09 August 2008

useful for controlling alarm flooding. A wrist strap jack is provided for
use with a wrist strap to prevent electrostatic discharge when installing
or servicing cards.
The rear of the chassis contains two sets of connectors for –48 VDC
power, and a power on-off circuit breaker. The dual connections allow
connection to redundant –48 VDC sources.
CAUTION
Although the chassis has redundant DC power
connections, they connect to a common power bus. A
failure of one DC link will not be reported as an alarm.
Chassis cards 1
Cards are inserted and removed from the front of the chassis. Each
card has a unique “physical address” determined by the slot number.
Color coding on the cards and on the chassis front indicates which
cards can be installed in which chassis slots.
All cards are designed to allow hot-swapping—card removal and

insertion with power on—so that system operation is not interrupted
except for activity associated with the removed card.
The front of each chassis card has a pair of general LEDs that indicate
status and activity. Some individual cards have additional indicators for
specific operational parameters.
Switch Fabric Card (SFC1/SFC2) 1

The Switch Fabric Card is always installed in slot 7 or slot 8 of the
chassis. One SFC card is required for operation, and a second SFC
card may be added for redundancy. The SFC card is based on a
switching matrix, providing connectivity between GGSN subscribers
and IP networks. An alphanumeric display provides information about
card configuration and status. LEDs show card status and activity.
SFC1 card
The SFC1 includes a daughter module mounted on standoffs—
hexagonally shaped, mechanical connectors that separate the
daughter module from the line card. The following type of daughter
module is supported by Nortel GGSN.
Full load: 10 Gb/s system (7.5 Gb/s daughter module) supports

chassis fully populated with 14 cards.

SFC2 card
The SFC2 card comes in a 10 Gbps version only. In addition to the
functionality provided by the SFC1 card, the SFC2 provides support
for native ATM traffic shaping to trunk Virtual Circuits (VCs).
CAUTION
The GGSN architecture does not support the direct replacement
of an active SFC1 with an SFC2 in the same slot. You must
follow the migration procedure. See “Migrating SFC1 to SFC2”
on page 4-13.
Control Management Card (CMC2/CMC3) 1

The Control and Management Card must be installed in slot 14 or slot
13. One CMC card is required for operation, and a second CMC card
may be added as a standby CMC for redundancy. The CMC controls
Nortel GGSN resources and routing.
If the primary CMC card fails, the GGSN will restart, and the original
standby CMC will become the new primary CMC. If the original
primary CMC card recovers (as in case when it is not a hardware
failure), then it is put into standby mode. There is a temporary platform
outage while the GGSN restarts. If the GGSN is configured with only
one CMC card and this CMC has a hardware failure, the GGSN will
continue to apply services to any existing customer already
connected, but will be unable to establish new subscriber connections.
Eventually the SSMs will time-out and the GGSN will stop.
The Control and Management Cards are responsible for running

system level processes such as basic system operation and
management, assignment of subscribers to SSMs, IKE and routing
algorithms including OSPF, RIP, and BGP. Routing decisions result in
the formation of routing tables which in turn are then used to populate
the FIB Manager tables. The FIB manager is responsible for
distributing reachability information to FIB tables on each of the SSMs.
There are two types of CMC cards available. Each is composed of
dual processors, memory and Layer 2 cache.
The CMC card contains connectors for the default management

Ethernet port. Typically, the management ethernet port should be used
for network management access (such as access the various SCS
servers, log servers, Radius servers, and so on) It also contains a
console serial port, and a serial modem port. A PCMCIA slot is
provided for Software Updates (CMC2 Only). An alphanumeric display
411-5221-923 Standard 06.09 August 2008

provides information about card configuration and status, while LEDs

show card status and activity.
Three generations of the Control and Management Card exist:
• CMC second generation, CMC2 - available with 512 MB or 1 GB of

memory
• CMC third generation, CMC3 - available with 4 GB of memory
CMC3 is the third generation Control and Management Card for the
GGSN. While CMC3 fulfills the same role as the two previous CMC
cards, CMC3 has significantly more processing power and increases
the maximum allowable on-board memory to 4 GB. Also, a network
security processor has been added to CMC3 to improve the public key
encryption operations over the earlier CMC cards. Other
improvements in CMC3 include a 40 GB higher-performance hard
drive, the removal of the compact flash and PCMCIA socket, the
removal of the Ethernet server ports, and ISN changes to improve
performance. Software release GGSNS4.1 or later must be installed
on the GGSN for CMC3 operation.
Table 1-1 gives a comparison between CMC2 and CMC3 features.

Table 1-1
Comparison between CMC2 and CMC3
Feature CMC1/CMC2 CMC3

On-board interconnection Fixed Point-to-point Packet switch architecture
topology
Number of processor two MPC755 @ 233 MHz Four (two per BCM1250)
cores @ 750 MHz to 1 GHz
Memory bandwidth 4.2 Gbps (1x64bits @ 34 Gbps - 51 Gbps (2 x
66 Mhz) 64bits @ 266400 Mhz)
Total memory capacity 1 GB Fixed 4 GB DIMM
per card
L2 Cache size per 512 kB 512 kB per BCM1250
processor
Maximum bandwidth 100 Mbps 600 Mbps
processor-fabric port
Number of priority 2 4
queues per processor
Hot standby GE link over No Yes
backplane
IKE bulk encryption No Yes
hardware accelerator
Inline packet No Yes
classification
PCMCIA (PC Card) port Yes No
Compact Flash Yes - SanDisk No
Server Ports Yes - 2 ports No
Management Ethernet Yes - 1 port Yes - 1port
Modem Port Yes - 1 port Yes - 1 port
Console Port Yes - 1 port Yes - 1 port
Access to the CMC is permitted or denied using passwords with

optional SSL/ IPSec encryption. The module supports a text-based
command line interface (CLI) for configuration and subscriber policy
management, although the SCS will be the primary means of device
configuration in a production environment. Configuration download is
via file transfer protocol, trivial file transfer protocol (TFTP), or
bootstrap protocol (BOOTP); and the system maintains security,
system and command logs.
411-5221-923 Standard 06.09 August 2008

A hard disk mounted on the CMC contains system configuration files.

Image software is stored on resident Flash (CMC2 only).
CAUTION
Pressing the reset button on the CMC card will cause a reboot of
the shelf. This also applies to the redundant CMC.
Subscriber Service Card (SSC2) 1

The Subscriber Service Card (SSC) can be installed in any free slot
(except slot 7, 8, or 14). The Subscriber Service Card is responsible
for subscriber connections and the applications of IP services to each.
Regardless of the placement of the SSC in the chassis, the throughput
of the card will be limited by the OC12 interface to the backplane. The
SSC card processes individual packets and performs subscriber
services.
Each SSC has an Ethernet Packet InterFace (EPIF) module

responsible for the translation of ATM cell data to Ethernet frames. The
SSC interface is composed of four OC3 links which using the EPIF
map to four MII Ethernet interfaces respectively. Each runs at OC3
data rate equivalent speeds (135 Mbps). Each of the Ethernet
interfaces is used to connect to a single Subscriber Service Module
(SSM). A fully populated SSC houses four SSMs. Each SSM has its
own set of status and activity LED indicators. Each SSM connects to
the SSC via an Ethernet/MII controller and is responsible for
controlling the four Subscriber Service Processors, the HiFn chip for
encryption and header authentication and the SSM memory.
A GGSN chassis can accommodate up to six active subscriber service

cards. All SSC cards are actively load balanced. The SSC cards can
be placed in slots 1-6 and 9-13, although it is recommended that SSC2
cards not be placed in slots 5, 6, 9, or 10 since these slots have high
bandwidth interfaces of which this version of SSC card cannot take
advantage.
Subscriber Service Card (SSC3) 1

The third generation Subscriber Services Card (SSC3) is the evolution
of SSC1 and SSC2. SSC3 provides the same functionality as SSC2,
but improves on performance and scalability. Newer technology
increases the general performance of the current code base when
ported to SSC3. The faster processors, the expanded memory, and
the faster encryption chip provide the performance enhancements of
SSC3. SCC3 includes connections which can be used for an optional
IPSec engine daughter card (Security and Encryption Card or SEC),

supporting full line rate encryption/decryption. The GGSN5.0.1

software or later must be installed on the GGSN for SSC3 operation.
SSC3 is not compatible with SFC1 and should only be utilized with a
CMC3 card.
Line cards 1
Line cards contain ports connected to subscriber service groups, and
provide the interface with ISPs and with subscribers. Line cards can
be installed in any proper slots (except slot 7, 8, or 14). Based on the
capacity requirements, the SSG configuration can be scalable for the
Nortel GGSN. 1 to 4 line cards can be configured in the SSG.
Types of line cards

Nortel GGSN supports several types of line cards, including:
• OC3 ALC (asynchronous transfer mode line card)
• Fast Ethernet Line Card
• Gigabit Ethernet Line Card
Recommendations for unused line cards
It is highly recommended that the line card should be removed from
the GGSN chassis and replaced with a filler plate if all ports on the line
card are not being used or configured. Otherwise, the dynamic PDP
session information will be downloaded to the unused line card and
the CPU overload situation may be triggered in some cases.
Optical fiber capabilities

Line cards for multimode or single-mode optical fiber are available
from Nortel Networks..
WARNING
Invisible laser radiation can be emitted from fiber optic
connectors. Avoid direct exposure to the laser beam.
Fan tray and filter 1

A fan tray mounted at the bottom of the chassis cools the card
cage.The tray is removable and hot-swappable. A replaceable filter
directly below the fan tray protects the card cage from dust.
411-5221-923 Standard 06.09 August 2008

Optional AC Power Shelf 1
The chassis requires a source of –48 VDC power. If this power is not
available at the site, the optional AC Power Shelf can convert 110 or 220
VAC into the necessary –48 VDC.
Power modules
The AC Power Shelf contains four power modules. Each power
module is an independent “hot-swappable” unit. Each module supplies
the necessary voltages for powering the chassis.
In a fully-loaded chassis, even if one power module fails, the others

supply sufficient power for the chassis. The failed power module can
be removed and replaced without interrupting system operation.

411-5221-923 Standard 06.09 August 2008

2-1
Chassis physical installation 2

This chapter explains how to install about the Nortel GGSN hardware
components.
• “Safety” on page 2-1
• “Site requirements” on page 2-1
• “Tools required for installation” on page 2-2
• “Cable types needed for installation” on page 2-3
• “AC plug types” on page 2-3
• “Rack requirements for the GGSN” on page 2-4
• “Unpacking the system” on page 2-5
• “Confirming the shipment” on page 2-5
• “Installing the SSG chassis in the rack” on page 2-6
• “Installing the AC Power Shelf (optional)” on page 2-9
• “Installing DC power (No AC Power Shelf)” on page 2-14
• “Installing cards in the chassis” on page 2-17
• “Connecting external cabling” on page 2-24
Safety 2
DANGER
The chassis uses –48 VDC electrical power. If present, the AC
Power Shelf uses 110 VAC power. These voltages can be fatal.
Take all normal precautions to prevent harm to personnel or
damage to equipment.
Site requirements 2
Confirm the site requirements detailed in this section.

2-2 Chassis physical installation Copyright © 2004–2008 Nortel Networks
Location
CAUTION
The chassis should be installed only in a restricted access area
(dedicated equipment room, equipment closet, or the like) in
accordance with articles 110-16, 110-17, and 110-18 of the
National Electrical Code, ANSI/NFPA 70 or the local authority
having jurisdiction.
Ensure that there is sufficient space around the installation so that no

passersby will contact any of the connectors or controls.
Ensure that the chassis air vents are not blocked.
Power requirements
The SSG chassis requires a source of either:
• –48 VDC
or
• 110 VAC or 220 VAC, 50-60 Hz (with optional AC Power Shelf)
The chassis typically requires 1,500 watts of power. In the future, it
may consume as much as 1,850 watts.
Tools required for installation 2

To install the SSG, the following tools are required:
• Slot-tip screwdriver, medium
• Phillips head screwdriver, medium
• ESD (antistatic) wrist strap (included in shipment)
411-5221-923 Standard 06.09 August 2008

Cable types needed for installation

Table 2-1 details the cable types needed for installation of the GGSN.
Table 2-1
Cable types used in SSG installation
Cable Type Connector Type Provided Purpose

Serial UTP Twisted Pair Yes (in the Connect a terminal with a
Management RJ-45-to-DB-25 system CMC card on the SSG for
Cable connector accessory using SCS, the iSOS CLI
RJ-45-to-RJ-45 kit) and other management.
connectors
AC Power Shelf Panduit “thimble” Yes (if AC Connects power supplies
Cable connector Power with power shelf, using volt
Shelf is return, volts direct current,
ordered) and grounding connections.
AC Power Cable 14 AMP connector Yes (if Connects chassis to AC
(Cord) ordered) power source.
DC Power Cable 14 AMP connector No Connects chassis to DC
power source.
Chassis Front DB-25 to DB-25 No Indicates through a terminal
Panel Alarm connectors session if a power supply
Cable error has occurred.
Coaxial Cable BNC connector No. Connects router or switch
using coaxial cable to a BNC
port on the ALC card on the
SSG.
Optical Cable SC “square” No Connects router or switch
connector using optical cable to an SC
optical port on the ALC card
on the SSG.
AC plug types 2
A 20amp cord is required with AC power. When AC power is ordered
with the equipment, two 110V cords (of the appropriate country type)
are sent with 20amp plugs on the ends. The standard North American
20amp power cord comes with plug ends NEMA 5-20P and IEC-320-
C19 as shown in Figure 2-1.

Figure 2-1
North American Power Cord
NEMA 5-20P IEC-320-C19
Other available AC plug types are shown in Figure 2-2.
Figure 2-2
AC plug types
Rack requirements for the GGSN 2

Note the following rack requirements for mounting the SSG and the
optional AC Power Shelf:
• Rack size
— 19-inch width (if installing the chassis in a 23-inch rack, use
optional 23-inch bracket adapters.)
— 18-inch minimum depth
— Standard height
• Rack spacing
— SSG Chassis: 11 U (rack units) high, where 2 U = 3.5 in.
— AC Power Shelf: 3 U high
• Mounting—The SSG chassis is mounted with eight standard rack
screws.
411-5221-923 Standard 06.09 August 2008

• Location
— The SSG can be placed anywhere in the rack
— The rack location should not be available to public access.
— If the optional AC Power Shelf is used, it must be mounted
directly below the SSG chassis
DANGER:
Do not locate the chassis where personnel can touch the DC
power source or cabling. Contact with this electrical source can
be fatal.
Unpacking the system 2

Carefully unpack the system. Remove all packing material from the
chassis and cards. Save all packing material.
WARNING
Two people are needed to unpack the chassis. Four people are
needed to move the chassis if it is loaded with cards.
Confirming the shipment 2

After unpacking, confirm that the shipment contains the following parts
and accessories:
• Shipping container 1:
— Chassis (includes fan tray, backplane, rack mounts, air filter).
— Card blanks for covering blank slots
• Shipping container 2: Accessory kit (SAC), including:
— ESD wrist strap
— Nortel GGSN Hardware Installation and Maintenance Guide
— Product Release Notes
— Serial management cable
— Cable management bezel
— Terminal block cover
— AC Power Shelf status cable (optional; if required by customer)
— Two AC power cables (optional; if required by customer)
• Shipping container 3 (and optionally, 3b, 3c, 3d):
— Cards (Number and type of cards depends on the customer’s order)

• Shipping container 4 (optional; if ordered):

— AC Power Shelf (if required by customer), with DC supply harness
• Shipping container 5 (optional; if AC Power Shelf ordered):
— 4 Power supply modules
The following items can be ordered separately:

• Optional chassis front-panel alarm cable
• Optional 23-inch bracket adapters
• Optional SSG emergency recovery PCMCIA card
Installing the SSG chassis in the rack 2

The chassis is designed to fit in a standard 19-inch rack. With the
addition of optional bracket adapters, it can also fit into a 23-inch rack.
ATTENTION
At least two people are needed to install an empty chassis,
containing no cards or fan tray. If the chassis contains cards
and fan tray, at least four people are needed to install the
chassis.
Installing in a standard 19-inch rack 2

Procedure 2-1
Installing the chassis in a standard 19-inch rack (Figure 2-3)
Step Action
1 Using two people for an empty chassis, or four people for a full one, lift
the chassis and slide it into the rack from front to back.
2 Align the mounting holes on the chassis with holes in the rack, and attach
the chassis using eight screws.
3 Tighten the screws hand-tight to begin, then use the appropriate

screwdriver to tighten them securely, proceeding clockwise from screw to
screw.
-END-
411-5221-923 Standard 06.09 August 2008

Figure 2-3
Installing the chassis in the rack
14
13
12
11
10
9
BSN
A 5000
8
SHAST
7
Strap
6 s
Ground
Cut-off Fan Statu
5 s
Alarm
4 Contact
Alarm
3
2 Status
Alarm
1
Critical
Major
Minor
10183FA
Installing the cable management bezel 2

The cable management bezel is shipped uninstalled. It is installed
above the card bay, across the top front of the chassis.
Procedure 2-2
Installing the card management bezel (Figure 2-4)
Step Action
1 Use a screwdriver to remove the three screws at the top of the chassis.
2 Snap the cable management bezel into place.
3 Secure the bezel with the three screws.

Procedure 2-2
Installing the card management bezel (Figure 2-4)
Step Action
-END-
Figure 2-4
Installing the cable management bezel
14
13
12
11
10
9
BSN
A 5000
8
SHAST
7
Strap
6 s
Ground
Cut-off Fan Statu
5 s
Alarm
4 Contact
Alarm
3
2 Status
Alarm
1
Critical
Major
Minor
10184FA
Installing in a 23-inch rack 2

If installing the chassis in a 23-inch rack, use the optional 23-inch bracket
adapters available from Nortel Networks.
• If using an AC Power Shelf, go to “Installing the AC Power Shelf
(optional)” on page 2-9 now.
411-5221-923 Standard 06.09 August 2008

• If using DC power, go to “Installing DC power (No AC Power Shelf)”

on page 2-14 now.
Installing the AC Power Shelf (optional) 2

Note that the AC Power Shelf can only be installed in a 19-inch rack. If
the installation has an optional AC Power Shelf, install it now, before
installing cards in the chassis. If there is no AC Power Shelf required,
skip to “Installing cards in the chassis” on page 2-17.
The AC Power Shelf supplies power to the chassis at locations where

–48 VDC is not available. This unit converts 110 volts AC or 220 volts
AC into the required –48 VDC potential needed for powering the
chassis. Note that the AC Power Shelf has two power switches, each
controlling the power of each of the two pairs of power supplies. Also,
the AC Power Shelf has two power connectors that enable two power
cords to connect to 110 or 220 volts AC power source.
Installing the empty AC Power Shelf 2

The AC Power Shelf is best installed empty. Install the power modules
after mounting the shelf in the rack and attaching cables to the
chassis.
WARNING
Before installation, ensure the AC Power Shelf is not connected
to an AC power source.
Procedure 2-3
Installing the AC Power Shelf (Figure 2-5)
Step Action
1 Remove any power modules from the AC Power Shelf.
2 Ensure the two power switches on the front of the AC Power Shelf are off.
3 Lift the AC Power Shelf and slide it into the rack from front to back. Place
the AC Power Shelf immediately below the SSG chassis.
Attention: Be sure to install the AC power shelf directly below the
chassis.
4 Use a Phillips screwdriver to secure the AC Power Shelf to the rack with
four screws.
5 At the rear of the AC Power Shelf, clip the cable ties to free the set of
black, green, and red cables.

Procedure 2-3
Installing the AC Power Shelf (Figure 2-5)
Step Action
6 Use a Phillips screwdriver to attach the set of AC Power Shelf cables to

the “A” set of terminals at the rear of the SSG chassis.
7 Install the clear terminal block cover over the terminals, and use a
screwdriver to secure it with two screws.
8 Connect the status cable from the chassis connector to the DB-25
connector labeled J109 on the AC Power Shelf (Figure 2-6).
9 Connect both power cords from the AC Power Shelf to a source of 110 or
220 VAC power.
-END-
411-5221-923 Standard 06.09 August 2008

Figure 2-5
Installing the AC Power Shelf in the rack
CMC
CMC
SSC Reset
SSC Reset Disk
ALC Disk
ALC
SFC Activity
SFC Activity Signal
ALC Signal Sync
ALC Sync
RDI
SSC Activity
RDI
SSC Activity Signal

SSC Signal Sync
SSC
Chassis
RDI
Sync t1
RDI MM Por
MM Por
t1
Activity Eject

PCMCIA
Signal Sync
t1 RDI PCMCIA P
MM Por Sync O
RDI P E
t1 SSM1 us R
O N T
SSM1 us R E 1
N T T
E 1 Speed
Signal Sync
Activity T Link P
RDI Speed
t2 SSM2 us O N T
N 2
T T
Sync SSM3 us T Link
Signal Stat Speed M
MM Por Sync E
Stat t2 E G 1
E
Stat Activity T
Stat T
Link
SSM1 us SSM2 us
P
Stat Activity
Stat Sync t3 P O
SSM2 us R
Activity
Stat Activity T
C P
SSM3 us M O
Stat
Signal Sync C P R
SSM3 us O N
Activity Activity t3 RDI O T
Stat
MM Por Sync R T
SSM3 us RDI SSM2 N R
SSM4 us R L
SSM4 us SSM3 L
SSM4 us RDI SSM3
SSM4 us RDI MM Por
SSM1 MM Por
SSM1 Status Active
SSM1 Status
SSM2 t4 Active
SSM1 MM Por
SSM2 t4 Status Active
MM Por
SSM2 Status Active
SSM3
SSM2 Status Active
SSM3
Status Active
SSM3
SSM3
Status Active 10
9
BSN
Active
A 5000
8
SHAST
7
Strap
6 s
Ground
Cut-off Fan Statu
5 s
Alarm
4 Contact
Alarm
3
2 Status
Alarm
1
Critical
Major
Minor
AC Power Shelf
CB2
AC
R
POWE 2
1
CB1
10185FA

Figure 2-6
Connecting cables to the AC Power Shelf
Warning!
INPUT
A -38V to -60V B
38.5A
Terminal
-48VDC GND -48 V -48VDC GND -48 V
RTN 1850W RTN
AC Power Shelf Block

Status
OFF ON
Cover
Status
ON
50
Cable
Black
AC Power
Red Cords
Green/
Yellow
10186EA
WARNING
Be sure to install the clear terminal block cover. The terminal
block cover protects against accidental contact with the –48
VDC terminals.
411-5221-923 Standard 06.09 August 2008

Installing power modules 2

The AC Power Shelf accommodates four power modules.
Procedure 2-4
Installing the power modules in the AC Power Shelf (Figure 2-7)
Step Action
1 Pick up a power module with both hands and position it in front of the AC
Power Shelf, with the connector facing the rear and the fan facing the
front.
2 Slide the power module into the AC Power Shelf, ensuring that the guides
on the power module align with those in the shelf.
3 Repeat steps 1 and 2 for remaining power modules.
4 Connect the 20 AMP connector AC power cord from the power supply to
the power shelf.
5 Turn both switches on the AC Power Shelf front panel to on. Ensure the
AC POWER lights come on. Ensure the PWR OK lights are on green on
all power modules.
6 Turn the power circuit breaker at the rear of the SSG chassis to on.
Ensure the chassis fan tray status LEDs are on and green.
7 Connect the 20 AMP connector AC power cord from the power supply to
the power shelf.
-END-

Figure 2-7
Installing power modules
CMC
CMC
SSC Reset
SSC Reset Disk
ALC Disk
ALC
SFC Activity
SFC Activity Signal
ALC Signal Sync
ALC Sync
RDI
SSC Activity
RDI
SSC Activity Signal

SSC Signal Sync
SSC
Chassis
RDI
Sync t1
RDI MM Por
MM Por
t1
Activity Eject

PCMCIA
Signal Sync
t1 RDI PCMCIA P
MM Por Sync O
RDI P E
Port 1 SSM1 us R
MM Activity Stat E
O N T
SSM1 us R E 1
N T T
E 1 Speed
Signal Sync
Activity T Link P
RDI Speed
t2 SSM2 us O N T
N 2
T T
Sync SSM3 us T Link
Signal Stat Speed M
MM Por Sync E
Stat t2 E G 1
E
Stat Activity T
Stat T
Link
SSM1 us SSM2 us
P
Stat Activity
Stat Sync t3 P O
SSM2 us R
Activity
Stat Activity T
C P
SSM3 us M O
Stat
Signal Sync C P R
SSM3 us O N
Stat
MM Por Sync R T
SSM4 us R L
SSM4 us SSM3 L
SSM4 us RDI SSM3
SSM4 us RDI MM Por
SSM1 MM Por
SSM1 Status Active
SSM1 Status
SSM2 Port 4 Active
SSM1 MM
MM Por
SSM2 Status Active
SSM3
SSM2 Status Active
SSM3
Status Active
SSM3
SSM3
Status Active 10
9
BSN
Active
A 5000
8
SHAST
7
Strap
6 s
Ground
Cut-off Fan Statu
5 Alarm
tacts
4 Alarm
Con
3
2 Status
Alarm
1
Critical
Major
Minor
AC Power
OK
PWR
FAULT
Shelf
Temp
1 LIM
OK
PWR
FAULT
OK
PWR Temp
FAULT 1 LIM OK
PWR
Temp FAULT
1 LIM
CB2 Temp
1 LIM
AC
R
POWE 2
1
CB1
10187FA
Installing DC power (No AC Power Shelf) 2

If the optional AC Power Shelf has not been installed (or if –48 VDC
sources are not already connected), attach –48 VDC sources to the
chassis now, according to the procedure in “Connecting –48 VDC
sources” on page 2-16.”
411-5221-923 Standard 06.09 August 2008

If the AC Power Shelf has been installed, go to “Installing cards in the

chassis” on page 2-17 now.
CAUTION
The chassis can be powered by dual (or redundant) power
feeds. Ensure that the circuit breaker at the rear of the chassis is
set to Off before installation or while servicing the unit.
Attaching a ground 2
If a ground cable is not attached to the chassis, attach a ground cable
now, as shown in Figure 2-8. Use a double lug so the ground cable is
connected to both grounding studs at the rear of the chassis.

Connecting –48 VDC sources 2

Procedure 2-5
Connecting the –48 VDC source to the chassis (Figure 2-8)
Step Action
1 Ensure the power circuit breaker on the rear of the chassis is set to off.
2 Connect a source of –48 VDC to the “A” set of terminals on the terminal
block. The black Panduit cable connects to the –48 VDC slot, and the red
cable connects to the –48 RTN slot.
WARNING
Be sure the source of –48 VDC is off before connecting it to the
chassis.
Step Action
3 To ensure redundancy, connect a separate source of –48 VDC to the “B”

set of terminals. The black Panduit cable connects to the –48 VDC slot,
and the red cable connects to the –48 RTN slot.
Figure 2-8
Connecting the –48 VDC sources
INPUT
A -38V to -60V B
-48 V 38.5A -48 V
-48VDC GND 1850W -48VDC GND
RTN RTN
Terminal
AC Power Shelf Block
Status
Cover
OFF ON
ON
50
Ground
Connection
10188EA
411-5221-923 Standard 06.09 August 2008

ATTENTION
Only one set of cables is required to power the chassis. The other set is
used as a backup.
CAUTION
Although the power connection is redundant, it uses a common
power bus and has a seamless switchover. A failure of one DC
link will not raise an alarm.
Step Action
4 Install the clear terminal block cover over the terminals, and use a
screwdriver to secure it with two screws.
-END-
Using wire and lugs
WARNING
For safety, be sure to install the clear terminal block cover. The
terminal block cover protects against accidental contact with
the –48 VDC terminals.
Use 8-gauge copper wire (or higher capacity) for making the –48 VDC
connection and ground connection.
Use the following lugs for DC connections:
• Panduit LCA8-10-L or equivalent

Use the following lugs for ground:
• Panduit LCD8-10A-L
Installing cards in the chassis 2
If cards are not already installed in the chassis, install them according
to the rules listed in “General card installation instructions” on page 2-
19. Note that some cards can be installed only in specific slots.

To prevent ESD failures during card installation, a wrist strap must be

used.
Procedure 2-6
Connecting the wrist strap
Step Action
1 Plug one end of the wrist strap into the connector on the front of the
chassis (Figure 2-9).
2 Secure the other end around your wrist.
-END-
411-5221-923 Standard 06.09 August 2008

Figure 2-9
Typical SSG card installation, front view
SSC SSC SSC SSC ALC ALC SFC SFC ALC ALC SSC SSC CMC CMC
OC3 ATM OC3 ATM OC3 ATM OC3 ATM
Activity Activity Activity Activity Reset Reset

Signal Signal Signal Signal Disk Disk
RDI Sync RDI Sync RDI Sync RDI Sync
MM Port 1 MM Port 1 MM Port 1 MM Port 1
Activity Activity Activity Activity

Signal Signal Signal Signal
Eject Eject
SSM1 SSM1 SSM1 SSM1 SSM1 SSM1 PCMCIA PCMCIA

Status Status Status Status Status Status
MM Port 2 MM Port 2 MM Port 2 MM Port 2 P P
Activity Activity Activity Activity Activity Activity E O E O
N R N R
E T E T
SSM2 SSM2 SSM2 SSM2 Activity Activity Activity Activity SSM2 SSM2 T T
1 1
Status Status Status Status Signal Signal Signal Signal Status Status
Link Speed Link Speed
Activity Activity Activity Activity RDI Sync RDI Sync RDI Sync RDI Sync Activity Activity
P P
E O E O
N R N R
SSM3 SSM3 SSM3 SSM3 SSM3 SSM3 E E
T T
Status Status Status Status Status Status T 2 T 2
Activity Activity Activity Activity Activity Activity Link Speed Link Speed
E M E M
SSM4 SSM4 SSM4 SSM4 MM Port 3 MM Port 3 MM Port 3 MM Port 3 SSM4 SSM4 N G N G
Status Status Status Status Status Status E M E M
T 1 T 1
Activity Activity Activity Activity Activity Activity Activity Activity Activity Activity
M M
RDI Sync RDI Sync RDI Sync RDI Sync O P O P
SSM1 SSM1 SSM1 SSM1 SSM1 SSM1 D O D O
E R E R
M T M T
C C
SSM2 SSM2 SSM2 SSM2 SSM2 SSM2 O P O P
N O N O
T R T R
MM Port 4 MM Port 4 MM Port 4 MM Port 4 R T R T
SSM3 SSM3 SSM3 SSM3 SSM3 SSM3 O O
L L
SSM4 SSM4 SSM4 SSM4 SSM4 SSM4
Status Status Status Status Status Status Status Status Status Status Status Status Status Status
Active Active Active Active Active Active Active Active Active Active Active Active Active Active
ESD
Wrist Strap
Connection
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Console Port
Alarm Cut-off
Ground Strap
Alarm Status Fan Status
Minor Major Critical

SHASTA 5000 BSN
10189EA
General card installation instructions 2

The type and number of cards installed in a SSG chassis will vary
depending on the application. However, each chassis must have at
least one Switch Fabric Card (SFC1/SFC2) installed in either slot 7 or
slot 8 and one Control and Management card (CMC2/CMC3) installed
in either slot 13 or 14.
All cards are “hot-swappable”—that is, they can be installed or

removed while power is supplied to the chassis.

Keep these hints in mind when installing cards:

• Note the color coding on the card and on the chassis front panel
(Figure 2-10). Front-panel colors correspond to the types of cards
that can be installed in each slot.
Figure 2-10
Match color coding on the chassis with colors on the cards
Green Red Yellow Red Green Blue
1 2 3 4 5 6 7 8 9 10 11 12 13 14
10196EA
• Install the Switch Fabric Cards (SFC1/SFC2) only in slots 7 and 8

(seen from the front of the chassis, and counting from left to right).
If upgrading to an SFC2 from an SFC1, follow the procedure in
“Migrating SFC1 to SFC2” on page 4-13.
• Install the Control and Management Cards (CMC2/CMC3) only in
slots 13 and 14.
• If a single CMC card is used, install it in slot 14. Install any other
type of card (except an SFC) in slot 13.
• Install line cards in slots 1–6 and slots 9–12. Slot 13 may be used if
no CMC installed in it.
• Add card blanks to cover any empty slots. Each card blank is held
in position by its screws.
CAUTION
The chassis and cards are designed to permit insertion or
removal of the cards from the chassis with power applied.
However, service personnel are cautioned to remove from their
hands any metallic objects (such as rings or watches) before
changing cards. Damage to the product may result from the
shorting of circuit card traces or leads by a metal object.
411-5221-923 Standard 06.09 August 2008

Procedure 2-7
Installing a card in the card cage
Step Action
1 Before attempting to install a card, ensure that no packing material,

cabling, or hardware obstructs the connector or the slot.
2 Working from the front of the chassis, slide a card into the slot, first
catching it along the runners on the side and then guiding it through the
slot. The card's chassis connectors face to the rear, the card's indicator
panel (the side with LEDs) faces the front of the chassis.
3 Press the card firmly until the connector seats, and the card ejectors can
be engaged.
4 Close the card ejectors to lock the card into place.
5 Tighten the top and bottom screws with a flat-tip screwdriver.
-END-
Installing an SFC 2
Install a Switch Fabric Card (SFC) in slot 7. Optionally, install another
SFC in slot 8.
Slots 7 and 8 may contain only Switch Fabric Cards. No other card
may be installed in these slots. Each chassis must have at least one
SFC.
The GGSN architecture does not support the direct replacement of an

active SFC1 card with an SFC2 card in the same slot. See “Migrating
SFC1 to SFC2” on page 4-13 for the upgrade procedure.
Installing a CMC 2
Install a Control and Management Card (CMC2/CMC3) in slot 14.
Optionally, install another CMC card in slot 13. A second CMC card is
redundant in the event of a failure of the active CMC. The GGSN
architecture supports only identical versions (CMC2/CMC2 or CMC3/
CMC3) of Control and Management Cards in the same chassis. For a
CMC card upgrade procedure, refer to the GGSN Upgrade Guide.
Slots 13 and 14 usually contain only Control and Management Cards.

If only one CMC is used, install it in slot 14. Each chassis must have at
least one CMC.

Make a secondary CMC redundant

Upon installing a second CMC, the GGSN does not automatically copy
the images from the primary. Complete the following procedure to
provision a redundant CMC.
Procedure 2-8
Provisioning a redundant CMC
Step Action
1 Issue the following command from the CLI to copy an image from the
existing CMC to the newly installed (Standby) card:
copy image from = /disk/image/<image_name> to = standby-cmc
2 Repeat until all required images are copied to the Standby CMC.
3 Resync the GGSN. For more information on resyncing the GGSN, see
the Nortel GGSN Provisioning Procedures (411-5221-927).
-END-
CAUTION
If all required image files are not copied to a newly installed
CMC, an outage may occur if that standby CMC becomes
active. An image file is considered necessary if it appears in the
CMC bootorder.
Installing an SSC2/SSC3 2
Install Subscriber Service Cards (SSC2/SSC3) as required in slots 1–6
and slots 9–12. A typical chassis contains from two to six SSC2s or
SSC3s. No more than six SSC cards can be installed in a chassis. If
the chassis contains only one CMC in slot 14, slot 13 can be used for
an SSC(SSC2 or SSC3).
The GGSN architecture does not support the direct replacement of an

active SSC card with a newer version card in the same slot (SSC2 to
SSC3). Follow the upgrade procedure in chapter 4 for SSC Card
Upgrade. As of software release 5.0, a combination of SSC2 and
SSC3 cards are supported in the same chassis.
Installing Line Cards 2

Install Line Cards as required in slots 1-6 and 9-12. Slot 13 may also
be used for a Line Card if there is not a redundant CMC in the slot.
411-5221-923 Standard 06.09 August 2008

Line card slots are color coded to differentiate between high-speed

slots and low-speed slots. High speed slots (5, 6, 9, and 10) are
capable of 1.2 Gbps, and are coded red. Low speed slots (1, 2, 3, 4,
11, and 12) are capable of 622 Mbps, and are coded green. High
speed line cards must be installed in the red slots (5, 6, 9, and 10) to
be fully functional.
ATTENTION
For high speed slots to be active, a fully loaded (10 Gbps)
Switch Fabric Card (SFC) must be installed in the chassis.
Table 2-2 shows the operational status of each card in the high speed
and low speed slots.
Table 2-2
Operational status of Line Cards in high speed vs. low speed slots
Card High Speed - 1.2 Gbps Low Speed - 622 Mbps

Red Slots 5, 6, 9, 10 Green Slots 1-4, 11, 12
OC3 ALC Fully Operational Fully Operational
FELC Fully Operational Only Ports 1-4 active
GELC Fully Operational Not Operational
Install card blanks in any empty slots. Card blanks are included in the
GGSN shipment.
ATTENTION
Card blanks are required to achieve rated EMI levels and
cooling.

Connecting external cabling 2

Communication with the controller may be by means of any of these
types of connections:
• Direct connection through the serial CONSOLE port on the CMC.
This is necessary for startup of the chassis (Quickstart). The serial
management cable can be used to connect to the CONSOLE port.
• Ethernet LAN connection through an Ethernet management (ENET
MGMT) port on the CMC, using the UTP twisted-pair Serial
Management Cable that is included in your GGSN shipment. This
is normally required for configuration and operation using the SCS.
It is not needed for Quickstart.
Attention: The CAT-5 cable used for 1000 base (Gige over Ethernet copper) requires
a cross-over of all 4 pairs. The user can set autosense / force speed to 1 Gbs on the
CMC3 port using this cable. The Ethernet port on CMC3 is capable of doing Gige and
auto-negotiate (autosense). The user should use the following pin-out for the Gige
connection:
– 1-3
– 2-6
– 3-1
– 4-7
– 5-8
– 6-2
– 7-4
– 8-5
Connections to the Internet and intranets are usually by means of

optical or coaxial cables to ports on the ATM line card. These
connections are required for the GGSN to provide services to
subscribers. They are not required for Quickstart.
WARNING
This Class 1 Laser/LED product contains a laser light source
that can injure eyes. Never look into an optical fiber or connector
port. Always assume that the fiber optic cable or connector is
connected to a laser light source.
Other cable connections to the chassis may include:

• Optional chassis front-panel alarm cable to provide alarm signals
to a terminal or indicator.
411-5221-923 Standard 06.09 August 2008

• Optional direct connection through a modem connected to the AUX

port on the CMC, using a standard RJ-45 UTP Serial Management
Cable.
Cable routing 2
Cables may be routed upward from the chassis and cards, then
through the cable management bezel.
Connecting to the CMC CONSOLE port for Quickstart 2

The CONSOLE port on the Control and Management card provides an
interface to a terminal for initial startup (Figure 2-11).
Attention: This connection is required for quickstart.
Procedure 2-9
Connecting to the CMC CONSOLE port
Step Action
1 Locate the serial management cable. It has an RJ-45 connector on one

end and a DB-25 serial connector on the other.
2 Plug the RJ-45 connector on the serial cable into the CMC CONSOLE
port.
3 Plug the DB-25 serial connector into a PC or workstation serial port.
-END-
Connecting to the ENET MGMT port for a LAN connection 2

The Ethernet LAN connection is made through an Ethernet
management (ENET MGMT) port on the Control/Management Card.
This connection is normally required for configuration and operation
using the SCS. It is not required for quickstart.

Figure 2-11
Connecting cables to the chassis and cards (typical)
Optical Cable
To Network
To Console
OC3 ATM OC3 ATM OC3 ATM OC3 ATM
Activity
Signal
Activity
Signal
Activity
Signal
Activity
Signal
Reset
Disk
Reset
Disk
Serial
RDI Sync RDI Sync RDI Sync RDI Sync Management
Cable
MM Port 1 MM Port 1 MM Port 1 MM Port 1
Activity Activity Activity Activity

Eject Eject
SSM1 SSM1 SSM1 SSM1 SSM1 SSM1 PCMCIA PCMCIA

Status Status Status Status Status Status
MM Port 2 MM Port 2 MM Port 2 MM Port 2 P P
Activity Activity Activity Activity Activity Activity E O E O
N R N R
E T E T
SSM2 SSM2 SSM2 SSM2 Activity Activity Activity Activity SSM2 SSM2 T T
1 1
Status Status Status Status Signal Signal Signal Signal Status Status
Activity Activity Activity Activity RDI Sync RDI Sync RDI Sync RDI Sync Activity Activity
P P
E O E O
N R N R
SSM3 SSM3 SSM3 SSM3 SSM3 SSM3 E E
T T
Status Status Status Status Status Status T 2 T 2
Activity Activity Activity Activity Activity Activity Link Speed Link Speed
E M E M
SSM4 SSM4 SSM4 SSM4 MM Port 3 MM Port 3 MM Port 3 MM Port 3 SSM4 SSM4 N G N G
Status Status Status Status Status Status E M E M
T 1 T 1
Activity Activity Activity Activity Activity Activity Activity Activity Activity Activity
M M
RDI Sync RDI Sync RDI Sync RDI Sync O P O P
SSM1 SSM1 SSM1 SSM1 SSM1 SSM1 D O D O
E R E R
M T M T
C C
SSM2 SSM2 SSM2 SSM2 SSM2 SSM2 O P O P
N O N O
T R T R
MM Port 4 MM Port 4 MM Port 4 MM Port 4 R T R T
SSM3 SSM3 SSM3 SSM3 SSM3 SSM3 O O
L L
SSM4 SSM4 SSM4 SSM4 SSM4 SSM4
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Console Port
Alarm Cut-off
Ground Strap

SHASTA 5000 BSN
To Alarms Alarm Cable

10197EA
Procedure 2-10
Connecting to an Ethernet management port (Figure 2-11)
Step Action
1 Attach one end of an Ethernet UTP twisted pair cable to the CMC,
fastening the RJ-45 clip to the ENET MGMT port on the card.
2 Attach the other end of the cable to the LAN.
-END-
411-5221-923 Standard 06.09 August 2008

Connecting cables to ALC ports 2

Cables from the ALC ports provide connections to ISP backbones and
subscriber access networks. These connections are normally required
in order for the SSG to provide services to subscribers. They are not
required for quickstart.
Connecting optical cables
Procedure 2-11
Connecting optical cables with SC connectors
Step Action
1 For optical ports, insert a standard optical SC “square” type cable

connector in one of the ALC ports. Be sure to use a multimode optical
cable for a multimode ALC and a single-mode optical cable for a single-
mode ALC.
2 Connect the SC connector on one end of the SC optical cable to the SC

cable connector on the ALC port.
3 Connect the SC connector on the other end of the SC optical cable to the
SC connector on the backbone switch or router connected to the ISP
backbone or subscriber access network.
4 Repeat for additional ports.
-END-

Connecting coaxial cables

Procedure 2-12
Connecting coaxial cables with SC connectors
Step Action
1 For coaxial ports, insert a standard BNC cable connector in one of the
ALC ports.
2 Connect the BNC connector on one end of the coaxial cable to the BNC
cable connector on the ALC port.
3 Connect the BNC connector on the other end of the coaxial cable to the
BNC cable connector on the backbone switch or router connected to the
ISP backbone or subscriber access network.
4 Repeat for additional ports.
-END-
Connecting the alarm cable to the chassis 2

The optional alarm cable (Figure 2-11) connects the chassis front-
panel alarm output to a terminal or other alarm indicator.
Procedure 2-13
Connecting the optional alarm cable
Step Action
1 Connect one end of the alarm cable to the Alarm Contacts connector at
the front of the chassis.
2 Connect the other end to a terminal or other alarm indicator.
-END-
411-5221-923 Standard 06.09 August 2008

3-1
Initial startup and configuration 3

This chapter explains how to start up and configure the Nortel GGSN.
• “Before beginning” on page 3-1
• “Launching the terminal program” on page 3-1
• “Applying power to the chassis” on page 3-2
• “Confirming initial hardware operation” on page 3-2
• “Performing the quickstart” on page 3-4
• “Quickstart log” on page 3-8
• “Configuring the Nortel GGSN” on page 3-9
• “Line Card Configuration” on page 3-9
• “Troubleshooting the installation” on page 3-9
Before beginning 3
Before starting up the GGSN for the first time, be sure that all cabling is
connected as shown in the previous chapter. In addition, ensure that
the following information is available:
• Management Ethernet IP address
• Default router address
• Service Creation System IP addresses
• Auxiliary management interfaces
Launching the terminal program 3

At the PC or workstation, launch the terminal program, and set it for:
• 9600 baud
• 8 bits
• 1 stop bit
• No parity
• Software flow control

3-2 Initial startup and configuration Copyright © 2004–2008 Nortel Networks
• VT-100 emulation
Applying power to the chassis 3

To perform an initial startup and operational check, apply power to the
chassis, and confirm that the necessary operating lights are lit.
To apply power to the chassis:

• If using the optional AC Power Shelf, ensure the front-panel
switches are set to on.
• At the rear of the chassis, set the chassis power on-off circuit
breaker to on.
Verifying connectivity to the terminal

Procedure 3-1
Verifying connectivity to the terminal
Step Action
1 At startup, observe messages from the GGSN scroll across the terminal
screen.
2 At the terminal, press the Return or Enter key a few times and see that
the cursor moves down a line on the screen for each Return or Enter.
-END-
Confirming initial hardware operation 3

Examine the LEDs on the chassis and on each card. Normal and
abnormal operation are discussed in this section.
Chassis LEDs
After 30 seconds, chassis front-panel LEDs should be as follows:
• Minor Alarm Status LED off
• Major Alarm Status LED off
• Critical Alarm Status LED off
• Fan Status LED green
If these LEDs are not as shown here, see “Troubleshooting the

installation” on page 3-9.
411-5221-923 Standard 06.09 August 2008

Card Status and Active LED

Each card has status and activity LEDs and alphanumeric display
panels at the lower front of the card. Individual cards may also have
their own sets of indicators.
All card Status and Active LEDs should be as follows:

• Status LED:
— Yellow during power-up
— Green to indicate normal operation
• Active LED:
— On yellow during power-up
— Green to indicate normal operation

Performing the quickstart 3

The GGSN launches the quickstart program automatically. After a
series of auto-boot messages, the terminal displays an initial
configuration dialog box.
Procedure 3-2
Performing the quickstart
Step Action
1 Follow the GGSN prompts and fill in the information on the terminal
monitor.
The Quickstart begins by showing how to navigate the Quickstart dialog
box, then asks for a password. Enter a password and verify it with re-
entry. The password is not echoed on the screen.
Initial System Configuration...

'.' = clear field;
'-' = go to previous field;
^D = quit
<CR> = keep previous value
For administrative password/security key, '.'

and <CR> are not allowed.
Password:
Please enter the value again for confirmation.
Password:
The password is used to validate the administrative user “admin.”

• Use a period to clear any field and start over. Note that clearing is not
allowed for the password or security key.
• Use the hyphen to go to the previous field.
• Use the Control-D combination to quit the Quickstart dialog.
2 The dialog asks for the IP address and prefix length of the GGSN, its
netmask, and the default next-hop router. Enter the management
Ethernet IP address and the default router address.
411-5221-923 Standard 06.09 August 2008

Procedure 3-2
Step Action
3 Also enter the IP address for the standby CMC if one is present. If a
standby CMC is not present, or networking will not be used on the
standby CMC, then this field can be left blank. If the address is included, it
must be different from the management Ethernet IP address. For
example:
Management Ethernet IP Address (address/mask-

len):10.0.0.58/24
Standby CMC Management Ethernet IP Address

(address/mask-len): 10.0.0.59/24
Default route via interface: 10.0.1.253
Default router address: mgmt-eth0
4 The dialog asks for IP addresses and interfaces to use to reach the SCS.
Enter Service Creation System (SCS) reachability information. For
example:
1st SCS IP Address: 10.0.0.5
1st SCS Interface (for static route; use

'dynamic' if running routing): mgmt-eth0
2nd SCS IP Address:.
2nd SCS Interface (for static route; use

'dynamic' if running routing):.
3rd SCS IP Address:.
3rd SCS Interface (for static route; use

'dynamic' if running routing):.
Note the use of the period (.) to clear unused fields.

If the SCS is not directly reachable by way of the management Ethernet,
enter the interface by which the SCS can be reached.

Procedure 3-2
Step Action
5 The system prompts for information about desired auxiliary management

interfaces and about local and remote IP address information. Enter
information about any desired auxiliary management interfaces. The
GGSN will use this to create IP interfaces on the specified virtual circuit.
Only RFC 1483 routed LLC and VCMUX interfaces are supported.
The interface information is specified as physical slot + physical port +
virtual path + virtual circuit to use for the interface, along with the
desired IP encapsulation. For example:
1st Auxiliary ATM Management Interface
(slot/port/vpi/vci/{vcmux,llcsnap,llcbridge}: .
1st Auxiliary ATM Management interface IP address
(address/mask-len): .
1st Auxiliary ATM Management interface remote
IP address: .
2nd Auxiliary ATM Management Interface
(slot/port/vpi/vci/{vcmux,llcsnap,llcbridge,ether}:.
2nd Auxiliary ATM Management interface IP address
(address/mask-len):.
2nd Auxiliary ATM Management interface remote
IP address:.
3rd Auxiliary ATM Management Interface
(slot/port/vpi/vci/{vcmux,llcsnap,llcbridge,ether}:.
3rd Auxiliary ATM Management interface IP address
(address/mask-len):.
3rd Auxiliary ATM Management interface remote
IP address:.
1st auxiliary Ethernet management interface (slot/

port): 2/1
411-5221-923 Standard 06.09 August 2008

Procedure 3-2
Step Action
1st auxiliary Ethernet management interface IP address

(address/
mask-len): 10.0.0.23/24
2nd auxiliary Ethernet management interface (slot/port):.
2nd auxiliary Ethernet management interface IP address

(address/
mask-len):.
3rd auxiliary Ethernet management interface (slot/port):.
3rd auxiliary Ethernet management interface IP address

(address/
mask-len):.
Note the use of the period (.) to clear unused fields.

Also note that for Ethernet, VPI and VCI should be specified as “0”; slot
and port are still required. For RFC 1483 bridged LLC, the VPI and VCI
are specified as they would be for either VCMUX or RFC 1483 routed
LLC.
6 This completes the Quickstart. The GGSN command line interface (CLI)
prompt appears, showing the name and user level. For example:
bsn(SSU)#
-END-
User levels are as follows:

• U: User—has read-only access to the GGSN
• SU: Super-user—has read and write access to the GGSN
• SSU: Super-super-user—has read and write access to the GGSN,
and can also save configurations

Quickstart log 3
For future reference, enter Quickstart information here:
Management Ethernet IP address
Standby CMC Management Ethernet

IP Address
Default Router Address
Service Creation System IP

addresses
Auxiliary Management Interfaces
Using the CLI 3

The command line interface (CLI) is the GGSN software that is seen
on the terminal after the quickstart.
Use the CLI only for troubleshooting and monitoring system activity.
CAUTION
The CLI is intended to be a way to troubleshoot system level
problems with the Nortel GGSN. Configuration using CLI is not
recommended. It can put the SCS out of synchronization with
the GGSN.
For further information about the CLI, see the Nortel GGSN Command
Line Interface Guide (411-5221-922).
411-5221-923 Standard 06.09 August 2008

Configuring the Nortel GGSN 3

Use only the Service Creation System (SCS) to configure the Nortel
GGSN. The SCS is a powerful graphical management and
provisioning tool that allows quick and efficient configuration of all
parameters. For information about configuring the SSG device, the
ISP environment, or the subscriber environment, see the Nortel GGSN
Provisionaing Procedures (411-5221-927).
Attention: The SCS is the software tool for all subscriber service
and policy configuration.
Line Card Configuration 3

For all trunk interfaces configured, the associated ports on the line
cards with the interfaces must be enabled. Enabling the ports will
ensure that any IP packet data sent to one of these interfaces will be
processed properly and any necessary outgoing communication
connections can be performed. If a port is not enabled then this may
impact the ability of the Nortel GGSN to communicate with other
external devices in the IP network.
Logging out 3
To log out from a terminal connected to the console port:
Use the exit command, with no arguments. For example:

exit
This command exits the SSG software and returns control to the login
prompt.
After 15 minutes with no activity, the system automatically logs out a

user. Any new user sees the login screen.
Troubleshooting the installation 3

If after installation the chassis does not operate properly, use the
tables in this section to help isolate and correct the problem.
The front of each chassis card has a pair of general LEDs that indicate
status and activity. Some individual cards have additional indicators for
specific operational parameters. In addition, the chassis has its own
set of indicators.

General Indications
To use general indications for troubleshooting see Table 3-1.
Table 3-1
Using general indications for troubleshooting
Indicator Possible cause Recommended action

No activity at chassis; no fans • No power applied to • Ensure –48 VDC is applied to
or indicator LEDs chassis terminals at rear of chassis.
• Chassis on-off circuit • Ensure on-off circuit breaker
breaker set to off at rear of chassis is set to on.
• If using AC Power Shelf, • Check cabling between
power switches on shelf chassis and AC Power Shelf.
off or cabling not correct
• Ensure AC Power Shelf front-
panel switches are on.
No indication at terminal • Terminal not connected to • Ensure serial cable is
console CMC CONSOLE port on securely connected to CMC
chassis CONSOLE port and to
terminal.
• Incorrect terminal
parameters • Ensure terminal is set for
9600 baud, 8 bits, 1 stop bit,
no parity. Ensure software
flow control, VT-100
emulation.
CAUTION
Although the chassis has redundant DC power connections,
they connect to a common power bus. A failure of one DC link
will not be reported as an alarm.
Using chassis alarm and status indicators

The Alarm Status LEDs on the chassis front panel are off to indicate
normal operation. Chassis alarms only indicate a fan failure. Single fan
failure yields a major alarm, multiple fan failure yields a critical alarm.
No other events trigger these alarms.
Attention: Chassis alarms are only generated by fan failure.

Circuit pack alarms are displayed by the LEDs on the individual
card.
To clear a fan failure alarm, replace the fan tray. See “Replacing a fan
tray” on page 4-101.
411-5221-923 Standard 06.09 August 2008

Fan status indicators

The Fan Status LEDs on the chassis front panel indicate operation or
failure of the fan tray (Table 3-2).
Table 3-2
Analyzing fan status indicators
Indication Possible cause Recommended action

Fan Status LED green. Normal operation. None.
Fan Status LED red. Malfunction of fan tray. Replace fan tray.
Using card Status and Active indicators

Table 3-3 shows how to use Status and Active indications for
troubleshooting.
Table 3-3
Using a card's Status and Active indicators for troubleshooting
Indication Possible cause Recommended action

No indicator LEDs illuminated Possible power failure on Replace the failed card. Do not
on card. card (for example, blown fuse attempt to replace the fuse or any
or other component failure). other component on the card.
Status LED green. Normal operation.
Status LED red. Card is faulty. Replace card with known good
card.
Status LED yellow. Card is not configured by Configure card using SCS.
software.
Active LED green. Normal operation: card is None.
online and active.
Active LED yellow. Slot is configured correctly, Card is in standby mode (CMC
but card is disabled by and SFC only).
software.

411-5221-923 Standard 06.09 August 2008

4-1
Maintenance, repair, and upgrade 4

This chapter explains how to monitor, maintain, and repair the
Nortel GGSN.
The following topics are explained in this chapter:
• “Monitoring system activity” on page 4-1

• “Performing periodic maintenance” on page 4-2
• “Hard drive maintenance” on page 4-4
• “Updating the software” on page 4-9
• “Powering down the chassis” on page 4-11
• “Making field repairs” on page 4-12
• “Returning components to Nortel Networks” on page 4-103
Monitoring system activity 3
Monitor system activity using the hardware and software
indications.
Front-panel indicators
Each card has status and activity LEDs and alphanumeric display
panels at the lower front of the card. Individual cards may also
have their own sets of indicators.
General card Status and Active LEDs

• Status LED: If the Status LED on the card is green, then the
card is electrically good. Red indicates an electrical
malfunction in the card.
• Active LED: Green indicates the card is enabled. Yellow
indicates the slot has the correct configuration, but the card is
disabled. Red indicates a problem or malfunction.
See “Appendix B: Hardware reference” on page B-1 for specific
LEDs for individual cards.
General card alpha displays

Alpha displays are another way to monitor card status. Refer to
Appendix B for the meaning of alpha displays for each card.
Nortel Networks GGSN Hardware Installation and Maintenance Guide

4-2 Maintenance, repair, and upgrade Copyright © 2004–2008 Nortel Networks
Software indications
• Change to the log file directory and use the show command to
monitor selected activity or to get statistics. For example:
cd /disk/log
show log mylogfile
The show command can display a variety of information. See the Nortel
GGSN CLI Commands manual (the CLI manual) for more information.
Using chassis alarms

Monitor the alarm LEDs on the front of the chassis to get an indication
of the operational status of the fans. See “Troubleshooting the
installation” on page 3-9 for a discussion these alarms.
Caution:
Chassis alarms only indicate fan failure. No other alarm is
displayed on the front of the chassis.
Performing periodic maintenance 3

The only periodic maintenance required by the chassis is replacement
of the fan filters.
Replacing a fan filter

Inspect the fan filter every 3 to 6 months under normal operating
conditions, and replace as necessary.
Procedure 3-3
Replacing a filter
Step Action
1 Use a Phillips screwdriver to unscrew the three thumbscrews holding the

fan tray door (Figure 4-1).
2 Swing the fan tray door forward and down to expose the air filter.
411-5221-923 Standard 06.09 August 2008

Figure 4-1
Opening the fan tray door
CMC
CMC
SSC Reset
SSC Reset Disk
ALC Disk
ALC
SFC Activity
SFC Activity Signal
ALC Signal Sync
ALC Sync
RDI
SSC Activity
RDI
SSC Activity Signal

SSC Signal Sync
SSC RDI
Sync
RDI
MM Por
t1
MM Por
t1
Activity Eject

PCMCIA
Signal Sync
t1 RDI PCMCIA P
MM Por Sync O
RDI P E
t1 SSM1 us R
O N T
SSM1 us R E 1
N T T
E 1 Speed
Signal Sync
Activity T Link P
RDI Speed
t2 SSM2 us O N T
N 2
T T
Sync SSM3 us T Link
Signal Stat Speed M
MM Por Sync E
Stat t2 E G 1
E
Stat Activity T
Stat T
Link
SSM1 us SSM2 us
P
Stat Activity
Stat Sync t3 P O
SSM2 us R
Activity
Stat Activity T
C P
SSM3 us M O
Stat
Signal Sync C P R
SSM3 us O N
Stat
MM Por Sync R T
SSM4 us R L
SSM4 us SSM3 L
SSM4 us RDI SSM3
SSM4 us RDI MM Por
SSM1 MM Por
SSM1 Status Active
SSM1 Status
SSM2 t4 Active
SSM1 MM Por
MM Por
SSM2 Status Active
SSM3
SSM2 Status Active
SSM3
Thumbscrew
Status Active
SSM3
SSM3
Status Active 10
Active 9
8
7
6
5
4
BSN
3 5000
STA
SHA
Fan tray
2
1
Door
10198FA
Warning:
Coming into physical contact with rotating fan blades can cause
serious injury.
Step Action
3 Slide the new filter into the chassis.
4 Shut the fan tray door and secure it with the thumbscrews.
-END-

Figure 4-2
Replacing the fan filter
CMC
CMC
SSC Reset
SSC Reset Disk
ALC Disk
ALC
SFC Activity
SFC Activity Signal
ALC Signal Sync
ALC Sync
RDI
SSC Activity
RDI
SSC Activity Signal

SSC Signal Sync
SSC RDI
Sync
RDI
MM Por
t1
MM Por
t1
Activity Eject

PCMCIA
Signal Sync
RDI PCMCIA P
MM Port 1 Sync O
RDI P E
t1 SSM1 us R
O N T
SSM1 us R E 1
N T T
E 1 Speed
Signal Sync
Activity T Link P
RDI Speed
t2 SSM2 us O N T
N 2
T T
Sync SSM3 us T Link
Signal Stat Speed M
MM Por Sync E
Stat t2 E G 1
E
Stat Activity T
Stat T
Link
SSM1 us SSM2 us
P
Stat Activity
Stat Sync t3 P O
SSM2 us R
Activity
Stat Activity T
C P
SSM3 us M O
Stat
Signal Sync C P R
SSM3 us O N
Stat
MM Por Sync R T
SSM4 us R L
SSM4 us SSM3 L
SSM4 us RDI SSM3
SSM4 us RDI MM Por
SSM1 MM Por
SSM1 Status Active
SSM1 Status
SSM2 t4 Active
SSM1 MM Por
MM Por
SSM2 Status Active
SSM3
SSM2 Status Active
SSM3
Status Active
SSM3
SSM3
Status Active 10
Active 9
8
7
6
Filter
5
4
3
2
1
10199FA
Hard drive maintenance 4

This procedure should be used to maintain the hard drive on a Nortel
GGSN. Disk cleanup is necessary to prevent the GGSN from
generating a high disk usage alarm, which is an indication that a disk
cleanup activity is past due for sustained system health. This
procedure is used to clean up files, scripts, downloaded information,
and system generated files that are no longer required. This activity
should be performed in a maintenance window.
411-5221-923 Standard 06.09 August 2008

The hard drive maintenance procedure should be performed if current

disk capacity level is over 60%. Use CLI command “show storage” to
check the disk occupancy level periodically.
Procedure 4-4
GGSN hard drive maintenance procedure
Step Action
1 Clean up the boot directory: The first directory is “/disk/image”. This

directory contains all the boot paths. Enter the commands show version
and show bootorder to determine the boot paths in current use. Any
path starting with “/flash” is the flash drive not the hard drive. Do not
remove files from the flash drive. Directories not listed from the show
bootorder or show version can be removed. To remove an image, use
the remove image <path> command. This will remove the image from
both the active and standby CMC.
ssg-76(SSU)# show version

Shasta 5000: IP Services Operating System
iSOS (tm), Version ggsns3.1.2Oct24-3
Built on Fri Oct 24 17:30:39 CDT 2003
Copyright (c) 1998-2001 Shasta Networks, Inc.
Copyright (c) 1999-2001 Nortel Networks Corporation.
All rights reserved.
System booted from ata:/disk/image/nero/ggsn312.3/cmc
System restarted by SCS resync
Booted using configuration: primary
ssg-76(SSU)# show bootorder
flags (f) : 0x0
boot file1 (f1) : /disk/image/nero/ggsn312.3/cmc
boot file2 (f2) : /disk/image/STAUTLER/PACKET/cmc
boot file3 (f3) : /disk/image/GGSN2081/cmc
boot file4 (f4) : /flash/image/isn/cmc //not hard
drive but flash drive
boot server address (h):
configuration (s) :
diag mode (dm) : 0x0
core dump mode (cm) : 0x1
ether mode (pm) : 0x111511
ssg-76(SSU)# remove image /disk/image/G207-02
ssg-76(SSU)# cd G207-02
Unable to change directory to G207-02: confmgr: No
Such Database

Step Action
2 Clean up the accounting directories:

The second directory is “/disk/acct”. This directory contains paths which
can hold RADIUS and GTP Accounting records. Accounting files need to
be cleaned from the active CMC and the standby CMC regularly.
Accounting files are written to disk when the Nortel GGSN determinesthat
it can not communicate with one or more of these server types, whether
the cause is actualserver outage or networking issues.The directory for
RADIUS Accounting files is “/disk/acct/radius”. In order to send the files
from the active CMC to a RADIUS accounting server on the network, use
the radacct disksend <gi isp> <profile name> command. If the files
simply need to be removed from the directory, use the remove file
command. Since the “remove file”command can not remove large
numbers of files at one time, it will be necessary to remove blocks of files
at one time. This can be accomplished by using the “*” delimiter after a
text string. Hence, remove file /disk/acct/radius/305* will remove all
files starting with the name “305”. Removing single file names can be
done by using the same command followed by the filename, such as
remove file 2491043A.02U. It is recommended to remove in blocks of no
more than 100 files at one time. Delete only closed or inactive files. A file
name ending in “W”,such as 2491042A.02W indicates an active file being
written. A file such as “2491043A.02U” indicates a closed file. It will also
be necessary to log into the standby CMC and check for RADIUS
Accounting files.
If RADIUS Accounting files are found on the standby and not needed, use
the remove file command explained above to remove the files.If the files
need to be stored to a RADIUS server, the files will need to be transferred
to the active CMC first. Use the command copy file standby
cmc:<<path>/filename>> <<path>/filename>> on the active CMC to
copy the files from the standby. After all files have been copied to the
active, use the remove file command explained above to remove the files
from the standby CMC. To transfer the files on the active CMC to the
RADIUS server, simply use the radacct disksend <gi isp>
<profilename> command.Example to copy a RADIUS Accounting file
from the standby CMC:
ssg76(SSU)# copy file standby-cmc:/disk/acct/radius/

903AAAAA.12U
/disk/acct/radius/903AAAAA.12U
Copying standby-cmc:/disk/acct/radius/903AAAAA.12U
Copying file /disk/acct/radius/903AAAAA.12U from
standby CMC to
/disk/acct/radius/903AAAAA.12U. Please wait...
Success
ssg76(SSU)#
411-5221-923 Standard 06.09 August 2008

Step Action
The “/disk/acct/gtp/cdrs” contains GTP accounting files. If the files are not
needed, they can be removed. Simply use the remove file command as
explained above.
Just like RADIUS Accounting files, if the filename ends with a “W”, the file
is active. Never remove an active file from the active CMC. If the files are
needed, the following procedure can be used to transfer the files to the
CGF.
a. Enter show gtpbill <ga-isp>. Verify the ISP state is “TO_CGF”, and
the active CGF field will indicate which CGF is receiving the G-
CDR’s. Do not continue if the “ISP state” is not “TO_CGF”.
# show gtpbill ssg-76-isp-ga

GTP Accounting Object Spy
=========================
RAM Buffer: State: True - On
Max Size: 500 ext blocks
Currently: 4 ext blocks in buffer
OK to send CDRs from disk: False
Ext Blks on Reg Unproc Lst: 0
Ext Blks on Hot Unproc Lst: 0
Ext Blk Proc Bunch Size: 0
TOS: 0x00
ISP: Name: ssg-76-isp-ga

ISP ID: 9
IP Addr: 99.104.76.166
Object State: TO_CGF
RAM CDR Max File size: 1048576 bytes
RAM CDR File Timeout: 1800 seconds
Next Pkt Seq Num: 38885
Next Charge ID Num: 3125008
Next Local Rec Seq Num: 1621559
Stored Pkt Seq Num 38782
CDR Encoding Scheme: ASN.1 BER
CDR Record Encoding Version: V3.2
CBB Mgmt Ext Version: 3
Bulk Update In Prog: No
Closed Unsent CDR files: 1251036A.05U
POS_DUP_PKTs in Q: 0
Mtc Msg Q: 0 Messages
CGF ID: 0
CGF State: IDLE
CGF IP Addr: 99.104.76.30
CGF UDP Port: 3386
Pkt Ack Timeout: 5 seconds
Max Number Rexmits: 1
Periodic Echo Timeout: 60 seconds

Step Action
GTP Hdr Ver In Use: VER2_6B

Open Pkt Linked: No
Fallback Occured: No
Rel Pos Dup Tmr: Null
Num Pkts Wait Ack Q: 0
CGF ID: 1
CGF State: CGF_NOT_PROVISIONED
CGF IP Addr: 0.0.0.0
CGF UDP Port: 0
Pkt Ack Timeout: 0 seconds
Max Number Rexmits: 0
Periodic Echo Timeout: 0 seconds
GTP Hdr Ver In Use: VER2_6B
Open Pkt Linked: No
Fallback Occured: No
Rel Pos Dup Tmr: Null
Num Pkts Wait Ack Q: 0
Audit status: Enabled
FTP status: Disabled
Number of CDRs audited in current audit file 0
Number of times the Write-to-Disk is enabled :1
Total Time spent in Write-to-Disk mode : 7769
secs
b. Enter gtpbill disksend allow to start the transfer.

c. After each file is successfully transferred, the file is automatically
removed.
d. After all files are transferred, enter gtpbill disksend off. Log into the
standby CMC and see if there are any GTP Accounting files. If not
needed, remove the files from the standby CMC using the remove
file command. If there are files on the standby CMC that are needed,
use the command copy file standbycmc:<<path>/filename>>
<<path>/file name> on the active CMC to copy the files from the
standby CMC. Follow the same procedure outlined above to send the
files to the CGF
3 Clean up the configuration directory:

The next directory is “/disk/config”. This holds the primary and quickstart
configuration files. This directory should be left alone unless you have
been adding your own backups.
411-5221-923 Standard 06.09 August 2008

Step Action
4 Clean up the core directories:

The next set of directories (i.e. “/disk/core”, “/disk/core1”, and “/disk/
core2”) contain core dump files. The core files within these directories can
be removed after the next level of support has indicated successful
retrieval of files required for investigation into a system event. These files
need to be removed from the active and standby CMC. These files
consume large amounts of disk space. A successful CMC core dump will
consume 1 gigabyte of space while an SSP core dump will consume a
few hundred megabytes.
5 Examine the log directory:

The next directory is “/disk/log”. This is controlled through the SCS from
the device Configuration Screen. The command logs are defaulted to 1
megabyte files and two history files. The event logs are defaulted to 2
megabyte files and 4 history files. The Nortel GGSN automatically rotates
and deletes log files, so they are in line with the provisioned attributes
from the SCS. There is no manual intervention needed in this directory.
-END-
Updating the software 4

Nortel Networks periodically makes available new versions of the
GGSN software. For more information on obtaining and installing
software updates, refer to the Nortel SCS & GGSN Upgrade Manual
(411-5221-309).

Checking software version number

Procedure 4-5
Checking the current GGSN software version
Step Action
1 From the CLI prompt, type:

show version
2 Read the current software version number and information. For example:
Shasta 5000: IP Services Operating System

iSOS (tm), Version GGSNS5.0-ggsns5.0a-10
Built on Fri Oct 15 10:43:39 CDT 2004 by loadbuild
Copyright (c) 1998-2000 Shasta Networks, Inc.
Copyright (c) 2000-2004 Nortel Networks Corporation.
All rights reserved.
Patch Status: No cards have been patched.
System booted from ata:/disk/image/ggsns5.0/cmc

System restarted by CLI reload
Booted using configuration: primary
Slot Port(s) Card Version Status Software Version

---- --------- ----- -------------- ---------------------
-----------------
1 1,2,4 /SSC Ok built on Oct 15 2004,
10:56:51,GGSNS5.0-ggsns5.0a-10
2 1,2,3,4 /SSC Ok built on Oct 15 2004,
10:56:51,GGSNS5.0-ggsns5.0a-10
10:56:51,GGSNS5.0-ggsns5.0a-10
10:56:51,GGSNS5.0-ggsns5.0a-10
10:56:51,GGSNS5.0-ggsns5.0a-10
10:56:51,GGSNS5.0-ggsns5.0a-10
-END-
Obtaining a software patch

To obtain a software patch:
If you do not already have an account set up on the Nortel Networks

support page, send e-mail to Nortel Networks support.
411-5221-923 Standard 06.09 August 2008

An account will be set up that will allow you access to the software
patches.
Powering down the chassis 4

Logging out
After 15 minutes with no activity, the system automatically logs out a
user. Any new user sees the login screen.
Use this procedure to log out.
To log out from a terminal connected to the console port, use the exit
command with no argument:
exit
This exits the Shasta BSN software and returns control to the login
prompt.
Shutting off power

If the SSG chassis must be powered down, use the following
procedure.
Procedure 4-6
Powering down the chassis
Step Action
1 Perform the procedure to handle the traffic and billing information before
the shutdown. “Manual GGSN shutdown, resync, or CMC switchover” on
page C-1 in “Appendix C: Product maintenance procedures” on page C-1.
2 Use the shutdown command to halt the SSG system:

shutdown
3 Set the circuit breaker at the rear of the chassis to off.
4 If using an AC Power Shelf, set the two switches at the front of the shelf to
off. (Off is shown as “0” on the switches.)
-END-
Warning:
The chassis can be powered by dual (or redundant) power feeds.
Ensure that the circuit breaker at the rear of the chassis is set to off
before installation or while servicing the unit.

Making field repairs 4

Field repair consists entirely of replacement of defective items. No
components of the SSG are user-serviceable. Components that can
be replaced are as follows:
• Cards
• Fan tray
• Fan filter
Caution:
Always perform any field maintenance activity during the
maintenance window.
Replacing a card
All cards are “hot-swappable,” allowing replacement even while power
is applied to the SSG chassis and the chassis is operational. The
following procedure describes the recommended steps to physically
replace a card. The steps for the different GGSN configurations of
different hardware cards are described in separate sections.
Prerequisites before performing any card maintenance

• Enable “Device State Notification” on the SCS client: click “View”,
then check and select 'Device State Notification”.
By enabling 'Device State Notification' users gets an update on the
SCS client promptly when there are card changes.
• Open ‘Monitor Chassis’ window: right-click on the device that you

are going to perform the card maintenance -> Monitor -> click
“Chassis”.
411-5221-923 Standard 06.09 August 2008

Attention: Although all cards are electronically hot-swappable, be aware

of the effect the replaced card may have on the system. For example,
when replacing a CMC card, ensure that the CMC to be replaced is in
Standby mode. If it is the Active CMC, perform a switch cmc and wait until
the system completes the switchover before replacing the card. After
replacing the CMC, verify that the iSOS version of the replaced card
matches the Active CMC iSOS version.
For SFC, SSC, or CMC card upgrades, refer to the Card Replacement
procedure in this chapter.
Procedure 4-7
General card replacing procedure
Step Action
1 Remove any attached cables from the front of the card.
2 Use a flat-tip screwdriver to loosen the screws at the top and bottom front
of the card.
3 Pull the ejector levers forward to release the card.
4 Pull the card straight out of the slot.
5 Insert the new card into the slot and slide it in until the ejector levers
engage.
6 Use a flat-tip screwdriver to tighten the screws on the front of the card
7 Attach any necessary cables to the new card
-END-
Warning:
This Class 1 Laser/LED product contains a laser light source that
can injure eyes. Never look into an optical fiber or connector port.
Always assume that the fiber optic cable or connector is connected
to a laser light source.
Migrating SFC1 to SFC2

When upgrading a GGSN chassis configured with SFC1 cards to
SFC2 cards, the following procedure must be followed in order to keep
the SCS Server in sync with the GGSN.
• “SFC1 to SFC2 Card Upgrade” on page 4-15

Use this process only if your GGSN software release is GGSNS4.0 or

above. Lower releases of software do not support the SFC2 card.
Caution:
The GGSN architecture does not support the direct replacement of
the only SFC1 card, with an SFC2 card. The SFC2 card needs to
be inserted in an empty redundant slot (i.e. slot 7 or 8).
If the GGSN platform is powered off and then restarted with a different,
active SFC card in slot 7, the SCS will not recognize the change and
slot 7 cannot be manually reconfigured. The Active SFC and CMC
cards for a BSN cannot be set “Administratively Disabled” from the
SCS, and their Administrative Status box is grayed out in the
Configuration - General window. When another SFC becomes active
in slot 8, the old SFC in slot 7 can be deleted from the SCS server
database.
Upgrade Considerations
After the upgrade, ATM Connections will now use L2 Traffic Profiles in
the SFC2 environment. Existing connections are not modified as part
of the SFC1 to SFC2 upgrade, but are changed when later viewed and
saved with the SCS GUI. There is a CORBA utility called,
SCSConvertConn, which can be run against the SCS databases to
convert connections to use ATM L2 Traffic Profiles. Without changing
the connection to use traffic profiles, previously configured ATM Traffic
Parameters can not be viewed or modified. Running SCSConvertConn
utility is an optional alternative. See “Executing the SCSConvertConn
Utility” on page 4-23.
411-5221-923 Standard 06.09 August 2008

SFC1 to SFC2 Card Upgrade

After GGSN software is loaded and the standby CMC card is in a
redundant state, the SFC1 cards can be upgraded to SFC-2 cards if
needed.
Procedure 4-8
Upgrading card from SFC1 to SFC2
Step Action
1 Set the GGSN to deny new incoming traffic:

a. Log in Gn ISP through SCS Client.
b. Select Access Properties -> Tunnels -> GTP.
c. Select the GTP tunnel and click “Edit”.
d. Select the device and click “Edit”.
e. Check and select the “Redirection Response Cause”. The
recommended setting is “No Resource Available (199)”. This cause
value is used to reject any new incoming Create PDP Context
Request message from SGSN.
f. Select Device under GTP Tunnel and select “Disallow PDP Context
Creation” on GTP tunnel device.

Procedure 4-8
Step Action
2 All active PDP contexts should be closed before upgrade. Operator can
either wait until all PDP contexts are closed then upgrade the SFC1 card
or use the procedure listed below to close all active PDP contexts.
a. Manually take down existing PDP contexts
— Log in Gn ISP through SCS Client.
— Select Access Properties -> Tunnels -> GTP
— Select the GTP tunnel and click “Edit”.
— Select the device and click “Edit”.
— Click “Initiate” for “Terminate Existing PDP Contexts” to take
down all existing PDP Context on GGSN.
b. Manually flush all billing records to ensure all billing information is
preserved before upgrade.
— Login to GGSN.
— Enter the following CLI commands:
gtpbill flush billing <Ga ISP Name>
show gtpbill <Ga ISP Name>
— Check the result of “show gtpbill” for ExtBlksonRegUnprocLst and

NumPktsWaitAckQ under the active CGF server, should be zero
before proceeding to next step. Wait and repeat “show gtpbill”
command if necessary.
Refer to “Appendix D: GGSN billing status verification CLI
command output on GGSN’s with SSC3 cards” on page D-1
for billing status verification for GGSN’s with SSC3 cards.
— Use the following command to disable gtpbill audit:

gtpbill audit isp=<Ga ISP Name> disable
c. If Radius Accounting records are being used for accounting

purposes, and if it is desired to send all the Radius Accounting
records stored on the disk to the RADIUS server before upgrading the
SFC1 card, issue the following CLI command:
radacct disksend <Gi_ISP_Name> <Radius_Profile_Name>
start
411-5221-923 Standard 06.09 August 2008

Procedure 4-8
Step Action
3 Make sure the following images are stored in the booting directory (e.g. “/
disk/image/ggsns5.0”) using “dir” CLI command:
208127 04-Mar-2004 21:51:26 rw STAT2_02.BIN

104066 04-Mar-2004 21:51:26 rw STAT_02.BIN
65235 04-Mar-2004 21:51:26 rw STATTOP.HEX
130465 04-Mar-2004 21:51:28 rw STATTOP2.HEX
1311800 04-Mar-2004 21:51:10 rw CHROME.BIN
4 Use “show card” to display the SFC1 card information

shasta-130(SHASTA)# show card
SSM/CT3/COC3 CPU states: A - auto-reset; N - need catchup;
C - catching up; D - in delete
U - up; X - failed; '-' - disabled; * - not
present
v - uncommunicative; d - dumping core; L -
loading
T - temporarily down; ~ - spared
ALC port states: U - up; D - down (alarm)
ELC/GELC port states: U /- up; D - down (link fail)
CT3/COC3 port states: + - up; '-' - down (alarm)
Slot Configured/Found Enabled Info
---- ----------------------- -------- -----
1 SSC /SSC Enabled U U U U
5 ALC /ALC Enabled U D D D [ICP Rev.
1.6]
6 ELC /ELC Enabled U U U D D D D D
7 SFC /SFC Enabled 10G Active [FPGA
Rev. 2.0]
8 SFC /SFC Enabled 10G Standby [FPGA
Rev. 2.0]
9 ALC /ALC Enabled D D D D [ICP Rev.
1.6]
1.6]
12 SSC /SSC Enabled U U - U
13 CMC3 /CMC3 Enabled Standby
(Redundant)
14 CMC3 /CMC3 Enabled Active
Make sure two SFC cards are recognized by “show card” CLI command
as “10G Active [FPGA Rev. 2.0]” and “10G Standby [FPGA Rev. 2.0]”.

Procedure 4-8
Step Action
5 Using the SCS GUI, set “Administration Status” to “Down” on Device

Window to disable the standby SFC1 card.
6 Basically pull out the standby SFC1 card on the GGSN chassis. The
following event log is shown:
29-Jan-2004 09:34:28 14/1/1:cardmgr,0: 2, 1, MAJOR, Card

of type SFC removed from slot 8
7 Delete “standby SFC” card on the Device Window to remove the standby
SFC1 card via SCS GUI.
8 Physically insert the SFC-2 card into the standby (empty) SFC1 card slot
on the GGSN chassis. The SFC-2 card is automatically detected by SSG
software and the SFC-2 card’s load image is downloaded. After
downloading is complete, the SFC-2 card LED shows “STBY”. On the
SCS GUI, the SFC-2 “redundancy state” is “Standby”, “Administration
status” and “Operation status” is “Up”. The following logs are shown when
inserting an SFC-2 card:
411-5221-923 Standard 06.09 August 2008

Procedure 4-8
Step Action
9 Using the SCS GUI, set “Administration Status” to “Down” on Device

Window to disable the standby SFC1 card.
27-Jan-2004 15:47:13 14/1/1:cardmgr,0: 1, 1, INFO, Card of

type SFC2 inserted in slot 8
27-Jan-2004 15:47:13 14/1/1:cardmgr,0: 13, 1, MINOR, Found
card of type SFC2 in slot 8, but slot is not configured.
27-Jan-2004 15:47:22 14/1/1:cardmgr,0: 33, 1, INFO, Card in
slot 8 has been enabled.
27-Jan-2004 15:47:23 14/1/1:cardmgr,0: 34, 1, INFO, Card in
slot 8 is up.
Enter the “show card” CLI command, the following is shown:

U - up; X - failed; '-' - disabled; *
- not present
v - uncommunicative; d - dumping core;
L - loading

---- ----------------------- -------- -----
5 ALC /ALC Enabled U D D D [ICP
Rev. 1.6]
7 SFC /SFC Enabled 10G Active
[FPGA Rev. 2.0]
8 SFC2 /SFC2 Enabled 10G Standby [FPGA
Rev. 2.0/29.0]
9 ALC /ALC Enabled D D D D [ICP
Rev. 1.6]
10 ALC /ALC Enabled D D D D

Procedure 4-8
Step Action
[ICP Rev. 1.6]

(Redundant)
10 Perform “switch sfc” CLI command and answer “Y” on prompt. The
following logs is shown:
09-Jan-2004 08:51:38 14/1/1:cli,3: admin@/pty/

tel01.S: [Success]
: switch sfc
09-Jan-2004 08:51:38 14/1/1:cmcmgr,0: 13, 1,
CRITICAL, SFC Switch from slot 7 started.
09-Jan-2004 08:51:38 14/1/1:cardmgr,0: 35, 1, INFO,
Card switchover from slot 7 issued by user via CLI
command.
09-Jan-2004 08:51:42 14/1/1:cardmgr,0: 32, 1, INFO,
Card in slot 7 has been disabled.
09-Jan-2004 08:51:53 14/1/1:cardmgr,0: 30, 1,
CRITICAL, Card switch to active complete for slot 8.
Please note that the ALC, FELC and GELC line cards cannot be reset or
reboot during 20 seconds “switch sfc” operation. After “switch sfc”
operation, previous active SFC card’s “redundancy state” is “Standby
Disabled”, “Administration status” as “Up” and “Operation status” is
“Down”. The “show card” CLI command will display the following:

U - up; X - failed; '-' - disabled;
* - not present
L - loading
411-5221-923 Standard 06.09 August 2008

Procedure 4-8
Step Action
---- ----------------------- -------- -----

1.6]
7 SFC /SFC Disabled 10G [FPGA Rev. 2.0]
8 SFC2 /SFC2 Enabled 10G Active [FPGA Rev.

2.0/29.0]
1.6]
1.6]
(Redundant)
11 Set “Administration Status” to “Down” on Device Window via SCS GUI to

disable the standby SFC1 card.
12 Physically pull out the standby SFC1 card. The following log is shown.
13 Physically insert SFC-2 card into the standby (empty) SFC1 card on
GGSN chassis. The SFC-2 card is automatically detected by SSG
software and the SFC-2 card’s load image is downloaded. After
downloading is complete, the SFC-2 card LED shows “STBY”. The SFC-2
“redundancy state” is “Standby”, “Administration status” and “Operation
status” are “Up”.
14 Perform “switch sfc” CLI command to put the previous standby SFC-2
card back to active. There is a 60 minutes timer set for the back-to-back
SFC card switchover operation. This implies that for the second SFC-2
card switchover, it needs to wait for 60 minutes before running the “switch
sfc” CLI command again.

Procedure 4-8
Step Action
15 Make sure two SFC-2 cards are recognized by SSG using “show card”
CLI command as shown below:
7 SFC2 /SFC2 Enabled 10G Active [FPGA

Rev. 2.0/29.0]

Rev. 2.0/29.0]
16 Make sure the SFC-2 card information is sync up with SSG “show card”
CLI commands on the Device window of SCS GUI.
17 Set the GGSN to allow new incoming traffic

a. Login Gn ISP through SCS Client.
d. Select Device under GTP Tunnel, click “Edit” and un-select “Disallow
PDP Context Creation” on GTP tunnel device.
-END-
SCSConvertConn - GGSN SFC2 ATM Conversion Utility

SCSConvertConn tool is a GGSN Utility used to convert ATM
connections to use L2 Traffic Profiles after a successful upgrade of
SFC1 to SFC2. This utility acts on all ATM connections in the SCS
database for the specified BSN once it has been upgraded. Existing
ATM connections created while an SFC1 was active in the BSN use
ATM Traffic Parameters in the connection record. Once the SSG has
been upgraded to SFC2, ATM connections now use L2 Traffic Profiles
to take advantage of the new SFC2 features like Traffic Shaping on
trunk interfaces.
Caution:
Once ATM Connections have been converted to use L2 Traffic
Profiles, if the SFC2 is later downgraded to an SFC1, any ATM
connection configured to use SFC2 traffic shaping features will
become unconfigured and not come up.
411-5221-923 Standard 06.09 August 2008

Executing the SCSConvertConn Utility

The SCSConvertConn utility is provided with the UNIX SCS Server
4.0.0 or above and can be found in a new utility directory:
<SCSInstallRoot>/bin/util/SCSConvertConn
To execute the utility the user must be logged is as root or as the SCS
Administrative user. The utility will not execute if provisioning is
blocked by some other process that is already in progress: System
backup/restore, Device move or Connection move. This tool should be
used during maintenance period to ensure no other configuration is
occurring, and a successful DB backup should have been performed.
Once the tool has started the operation, the data can only be restored
with a DB restore.
During execution the utility will validate that the region and device
exist, and that an SFC2 is active in the BSN. If the connection is not an
ATM connection or is an MLPPP connection, it will not convert it.
Otherwise the utility will first check to see if the connection is
converted, and if not, try to find an existing profile to match the
configured traffic parameters settings. If one does not exist, the utility
will create a new traffic profile containing the configured traffic
parameters, and name the file in the format traffic-<isp name>-<port
type>-<list of configured parameters>.
The utility takes the following arguments:
$SCSConvertConn <spm.ior> <username> <password> <region> <device>
spm.ior - .ior file provided in <SCSInstallRoot/proc>

username - must be device_owner
password - password for device_owner user
region - name of region in which device is located
device - device for which the connections are to be converted

Sample Execution:
scs1# ./SCSConvertConn ../../proc/spm.ior device_owner do bsn_region1

bsn3
*********************************************************
* This tool should be used during maintenance period to *
* ensure no configuration happen: *
* 1.An successful DB backup should have been performed. *
* 2.Once the tool has started the operation, the data *
* can only be restored with a DB restore *
*********************************************************
Do you want to continue? [y/n]
y
Connection conversion started
22 connections (ATM) converted
Connection conversion stopped
scs1#
Execution of the utility takes time depending upon the number of

connections to be converted and the speed and availability of the
system the SCS Server is running on. The utility can take
approximately 5 minutes per 1000 connections to convert.
During execution the utility creates a log file in the util directory
detailing all actions taken. The log file has the name format of:
<SCSInstallRoot/bin/util/
ConvertConn_<region>_<device>_<date>_<time>.log
Example log entries:
03-Sep-2003 12:01:28 347 connection conversion started 03-Sep-2003 12:01:28 347

Connection “bsn3-10-1-smb-7(slot:10,port:1)” is not an ATM conn. Do not convert
03-Sep-2003 12:01:28 348 “bsn3-12-1-2(slot:12,port:1)” already converted 03-
Sep-2003 12:01:30 872 Convert connection “bsn3-12-1-2-32-vprn-
sub3(slot:12,port:1)” successfully 03-Sep-2003 12:01:36 172 Convert connection
“bsn3-atm2-trunk(slot:6,port:1)” successfully 03-Sep-2003 12:01:36 715 Convert
connection “bsn3-atm2-trunk2(slot:6,port:1)” successfully 03-Sep-2003 12:01:36
812 Connection “bsn3-corp-lan(slot:14,port:4)” is not an ATM conn. Do not
convert 03-Sep-2003 12:01:36 848 connection conversion stopped
Downgrading SFC2 to SFC1 Card

Downgrade from SFC2 to SFC1 is discouraged. The Switch SFC
functionality is not supported when switching from SFC2 to SFC1, so
repowering the SSG is necessary. Connections configured on SFC2
which utilize features not present in SFC1 may cause session errors if
411-5221-923 Standard 06.09 August 2008

the SSG is later downgraded back to SFC. For example, shaped trunk
connections are not supported on SFC1.
Caution:
Downgrading from SFC2 to SFC1 is discouraged. Once ATM
connections have been modified under an SFC2 environment, their
old traffic shaping configurations are lost if going back to SFC1.
If a downgrade is required the following process must be followed.

Procedure 4-9
Pre-check for the Downgrade to SFC1 card
Step Action
1 Make sure SCS is loaded with GGSNS4.0 or above release.
2 Make sure SSG is loaded with GGSNS4.0 or above load. If SSG is

equipped with two CMCs, make sure that both CMC cards are loaded
with the same GGSN load.
3 On SSG, make sure two SFC cards are recognized by SSG (via the
“show card” CLI command) as:
7 SFC2 /SFC2 Enabled 10G Active [FPGA Rev.

2.0/29.0]
8 SFC2 /SFC2 Enabled 10G Standby [FPGA Rev.
2.0/29.0]
-END-

Procedure 4-10
Downgrading to SFC1 Card
Step Action
1 Get SFC cards information.

Use “show card” to display the SFC cards information. For example:
shasta-49(SSU)# show card
U - up; X - failed; '-' - disabled; * -
not present
v - uncommunicative; d - dumping core; L
- loading

---- ----------------------- -------- -----
1.6]
Rev. 2.0/29.0]
Rev. 2.0/29.0]
9 GELC /GELC Enabled U [FPGA Rev. 0.5]
[GBIC Multi]
10 ELC /ELC Enabled U U U U U U U U
13 CMC3 /CMC3 Enabled
Standby(Redundant)
Active
411-5221-923 Standard 06.09 August 2008

Procedure 4-10
Step Action
2 If there is no ATM trunk and no access connection on GGSN or there is

no ALC card, skip this step and move onto next step.
Restore the default traffic shaping profile for each ATM trunk and access
connection on ALC cards via SCS GUI
The default traffic profile is in “traffic-<isp>-<port-type>-UBR-PCR-0-
MCR-0” format. The default traffic profile for each ATM trunk or access
connection can be achieved via the Traffic Parameters tab within the
Connection Configuration window derived from the SCS Client
Configuration - Connection window. This operation needs to performed
for each ATM trunk and access connection on a per ISP basis.
Please note that if any of the ATM trunk or access connections is
associated with non-default traffic profiles, after the SFC-2 to SFC1 card
hardware downgrade operation, the ATM connection status will be shown
as “UnCfg” - Configuration Error to reflect the mismatched traffic shaping
capability supported by the SFC1 card.
3 Use SCS GUI to set “Administration Status” to “Down” on Device Window

to disable the standby SFC-2 card.
4 On SSG, pull out the standby SFC-2 card from the chassis.
The following event log will be shown on the console:
02-Apr-2004 21:19:37 14/1/1:cardmgr,0: 2, 1, MAJOR, Card of

type SFC2 removed from slot 8
5 Delete the entry of “standby SFC-2” card on Device Window via SCS
GUI. The following log is shown on the console:
02-Apr-2004 21:31:51 14/1/1:cardmgr,0: 2, 1, MAJOR, Card of

type Empty removed from slot 8
02-Apr-2004 21:31:51 14/1/1:cardmgr,0: 13, 1, MINOR, Found
card of type Empty in slot 8, but slot is not configured.

Procedure 4-10
Step Action
6 On SSG chassis, insert an SFC1 card into the standby (empty) SFC card
slot on the chassis. The SFC1 will initialize to the OFF state. The
following logs are shown on the console when the SFC1 card is inserted
into the standby (empty) SFC card slot:
02-Apr-2004 15:47:13 14/1/1:cardmgr,0: 32, 1, INFO, Card

in slot
8 has been disabled.
On SSG, the “show card” cli will prompt as -

- not present
v - uncommunicative; d - dumping core; L - loading

---- ----------------------- -------- -----
1.6]
Rev. 2.0/29.0]
8 Empty /SFC Disabled 10G [FPGA Rev.
15.0]
Rev. 1.6]
Rev. 1.6]
(Redundant)
411-5221-923 Standard 06.09 August 2008

Procedure 4-10
Step Action
7 Power off the SSG, remove the remaining SFC-2 card, and power up the
SSG.
On SSG, the “show card” cli after SSG booting up will be prompted as -

* - not present
L - loading

---- ----------------------- -------- -----
5 ALC /ALC Enabled U D D D [ICP
Rev. 1.6]
6 ELC /ELC Enabled U U U D D D
D D
7 SFC2 /Empty Enabled
Rev. 2.0]
Rev. 1.6]
Rev. 1.6]
Standby (Redundant)
8 Use SCS GUI to delete the “SFC-2” card on Device Window to remove
the SFC-2 card from the SCS database.
(On SCS, it takes less than a minute to detect the new Active SFC1 card
and update the SCS database.)

Procedure 4-10
Step Action
9 If the ATM trunk or access connection status is shown as healthy “Up”

condition, skip this step and move onto next step.
On SSG, the “show conn” cli will be prompted as -
shasta-130(SHASTA)# show conn

Connection Type L2 Type Slot/Port/VPI/VCI
Status Node
---------- ---- ------- ----------------
- ------ ----
ssg-130-isp-gn-atm-5-1-conn trunk ATM-VC 5/1/0/437
Up (all)
shasta-130-5-1-4 access ATM-VC 5/2/0/992
Up 12/3/3
If there is any ATM trunk or access connection is shown as -

shasta-130(SHASTA)# show conn
Connection Type L2 Type Slot/Port/VPI/VCI
Status Node
---------- ---- ------- ----------------
- ------ ----
ssg-130-isp-gn-atm-5-2-conn trunk unknown 5/2/0/0
UnCfg
ssg-130-isp-gn-atm-5-1-conn trunk unknown 5/1/0/0
UnCfg
That means the ATM connection is associated with the mismatched traffic
shaping capability supported by the SFC card.
10 Use SCS GUI to select UBR (PCR: 0, MCR:0) for each ATM trunk and
access connection via the Traffic Parameters tab within the Connection
Configuration window derived from the SCS Client Configuration -
Connection window.
11 If a standby SFC1 card is required, on SSG, insert SFC card into standby
(empty) SFC card slot. Perform “switch sfc” CLI command if plan to put
the previous SFC1 card back to Active.
411-5221-923 Standard 06.09 August 2008

Procedure 4-10
Step Action
12 On SSG, make sure two SFC1 cards are recognized by GGSN (via the
“show card” CLI command) as:
7 SFC /SFC Enabled 10G Standby [FPGA

Rev. 2.0]
Rev. 2.0]
13 Through the SCS GUI, make sure the SFC card information is sync-up
with the “show card” CLI command display via clicking the SCS Client
Configuring-Device window on slot 7 and 8.
-END-
Replacing an SFC or SFC2 Card

The SFC redundancy is supported as per Shasta 5000 BSN
functionality. When the active SFC card is pulled out without issuing a
CLI command ‘switch sfc’, the fabric will lose its clocking possibly
causing CMC card reboot. Before pulling out the SFC card, a ‘switch
sfc’ CLI command needs to be executed so that the redundant SFC
becomes active and responsible for the switch clock. In the event of an
active SFC failure, the standby SFC becomes the active SFC
automatically and takes over the clock.

Single SFC card configuration

In this situation, an empty SFC slot should be available on the SSG
chassis.
Procedure 4-11
Step Action

b. Select Access Properties -> Tunnels -> GTP
2 Flush Billing information using the CLI command ‘gtpbill flush billing
<ispname>’. The progress of the billing flush can be monitored via the
command ‘show gtpbill <ispname>’. There is a line in the display “Bulk
Update in Progress”. When this line is set to “No”, accounting information
has been flushed from the SSPs to the CMC.
Refer to “Appendix D: GGSN billing status verification CLI command
output on GGSN’s with SSC3 cards” on page D-1 for billing status
verification for GGSN’s with SSC3 cards.
3 Insert the replacement SFC card into the vacant slot.
4 Wait till it boots up to the standby state, as seen on the card status display
5 If it is desired to set the new switch to active, log in to the switch and
execute a ‘switch sfc’ command at the prompt.
6 The new SFC card will take some time to become active. In order to
determine when this happens, the operator can arrange for data to be
sent through GGSN at a low traffic rate and observe the data traffic
successfully being sent. Once the new SFC card has become active and
the old card is in a standby state.
7 The old SFC card can now be physically removed.
411-5221-923 Standard 06.09 August 2008

Procedure 4-11
Step Action
8 Delete the removed card from the SCS GUI:

a. Log in to the Device Owner or any ISP through SCS Client.
b. Select the device via Devices -> Regions -> Your Region - > Your
Device.
c. Select the GGSN and click “Edit”.
d. On the Device tab, click on the card to be replaced and click “Delete”.
9 Set the GGSN to allow new incoming traffic:

e. Select Device under GTP Tunnel and deselect “Disallow PDP
Context Creation” on GTP tunnel device.
-END-
Multiple SFC card configuration

In this situation, the SFC card to be replaced should always be in the
standby mode. If not, a ‘switch sfc’ should be issued to set it to standby
mode.
Procedure 4-12
Step Action


Procedure 4-12
Step Action
2 Flush Billing information using the CLI command ‘gtpbill flush billing
<ispname>’. The progress of the billing flush can be monitored via the
command ‘show gtpbill <ispname>’. There is a line in the display “Bulk
Update in Progress”. When this line is set to “No”, accounting information
has been flushed from the SSPs to the CMC.
3 If the SFC card to be replaced is in active mode, log in to the switch and
execute a ‘switch sfc’ CLI command at the prompt.
4 Use SCS GUI to set “Administration Status” to “Down” on Device Window

to disable the standby SFC card and then physically remove the SFC
card from the chassis.
5 Delete the removed SFC card from the SCS GUI:

Device.
d. On the Device tab, click on the Card to be replaced and click “Delete”.
6 Physically insert the new SFC card.
7 The new SFC card will boot up into standby mode.
8 If it is desired to set the new card to active mode, once again execute a
‘switch sfc’ to switch the new SFC card from standby to active mode.

a. Login Gn ISP through SCS Client.
10 The new SFC card will take some time to become active. In order to
determine whether this happens, the operator can arrange for data to be
sent through GGSN at a low traffic rate and observe for the data traffic
being successfully sent.
-END-
411-5221-923 Standard 06.09 August 2008

Replacing a CMC Card

In case there are other GGSNs in the network with the same APN
configuration as the affected GGSN, it is recommended that the
affected GGSN be removed from the DNS Server database for the
duration of card replacement in order to minimize any network impact.
Prerequisites for Replacing CMC card

• Ensure console access for all CMC card(s).
• Ensure the isn image is in the last bootorder sequence:
— Issue the ‘show bootorder’ CLI command to check if the
location of boot file4 (f4) is the isn image directory (i.e. for
CMC2 it is “/flash/image/isn/cmc” and for CMC3 it is “/disk/
image/isn/cmc3”).
— Use the ‘set bootorder’ CLI command to add/change boot
file4 (f4) to isn image directory if boot file4 (f4) does not have
the isn image directory set.
— Issue the CLI command “show bootorder” to verify the
bootorder setting change.
Single CMC card configuration
In this situation, all functionality related to the CMC card must be
systematically disabled before card replacement.
Procedure 4-13
Step Action


Procedure 4-13
Step Action
2 All active PDP contexts should be closed before card replacement.

Operator can either wait until all PDP contexts are closed then replace the
CMC card or use the procedure listed below to close all active PDP
contexts.
a. Manually take down existing PDP contexts:
— Select Access Properties -> Tunnels -> GTP.
— Click “OK” to Terminate All Existing PDP Contexts.
— Click “OK” at the bottom of the “GTP Tunnel Configuration” menu.
b. Manually flush all GTP accounting information from the GGSN to the
CGF server after all PDP contexts are closed. Monitor the value of
the variable “SM.NbrActPdpCtxt” which indicates the number of
active PDP Contexts. A CGF must have been properly configured.
— Allow transferring billing records from disk to the CGF. Use the
CLI command ‘gtpbill disksend allow’.
— Transfer billing records to the appropriate CGF. Use the CLI
command ‘gtpbill sendto cgf <ispname> <cgf_id>”
— Perform a flush of all the currently active PDP sessions. Use the
CLI command ‘gtpbill flush billing <ispname>’.
— The progress of the billing record transfer can be monitored via
the CLI command ‘show gtpbill <ispname>’. A listing of Closed
Unsent CDR files represents the records which still have not
been sent to the CGF. The CGF state should be “RUNNING”.
When all the records have been transferred, this listing will be
empty.
c. If RADIUS Accounting is activated, then send all the RADIUS
Accounting records stored on the disk to the RADIUS server before
card replacement otherwise they can be left and deleted during a
reboot/resync. Repeat the following CLI command for all RADIUS
Profile and Gi ISP on the GGSN - ‘radacct disksend <Gi_ISP_Name>
<Radius_Profile_Name> start’. Only perform this step for RADIUS
Profile configured with RADIUS Accounting enabled.
411-5221-923 Standard 06.09 August 2008

Procedure 4-13
Step Action
3 Unapply the patching profile currently applied to the GGSN. Refer to

“Appendix B: GGSN Patch Application” in the GGSN Provisioning
Procedures (411-5221-927).
4 Disconnect all cables from the CMC card and remove the CMC card.
5 Physically add the new CMC card in the same slot and reconnect cables.
6 Connect to new CMC card via console cable.
7 If the CMC card doesn’t boot up completely, refer to the following:

a. If the CMC card is a CMC2 card, it can be booted up form the flash
memory,
b. If the CMC card is a CMC3 card, it can be booted up from the
network. See “Boot CMC card from network” on page C-12.
8 Configure the quickstart configuration for admin password and IP

connectivity.
9 Log into the new CMC card remotely using the admin password.
10 When a fresh CMC card boots up, the software may not be the GGSN
software (i.e. it may be the GGSN Base software). In this case, FTP
GGSN software to the directory /disk/image from a remote server.
11 If the firmware on the new CMC card is not an updated one, bootrom
upgrade is required. See “CMC bootrom upgrade” on page C-14.

Procedure 4-13
Step Action
12 Verify the time and timezone configured on the GGSN. Use the CLI
commands 'show time' and 'show timezone'.
If the time or timezone are not configured correctly, set the time and/ or
timezone from the SCS client.
a. Log in to the SCS Client with Device Owner privileges.
b. In the SCS Client, click on Devices in icon panel, select the region,
right-click on the Device, click Configure then Device.
c. In the Configuration-Device window, under Time and Timezone
Settings, set the Date and/ or Time and/ or Primary Time Zone.
If a Network Time Protocol (SNTP) server is available, the server can be

configured under SNTP Client Configuration.
If a SNTP server is configured under SNTP Client Configuration, and the
GGSN CLI command 'show time' or 'show timezone' return incorrect date
and/ or time and/ or timezone, perform the following steps to correct the
mismatch.
i. Manually set the time on the GGSN using the command:
set time YYYY/MM/DD
ii. From the SCS client, navigate to SNTP Client Configuration,
uncheck the option Enable SNTP Client.
iii. Verify the Time Zone settings under Time and Time Zone
Settings. If set incorrectly, modify the settings.
iv. Click OK to close the Configure-Device window.
v. Navigate to SNTP Client Configuration under Configure-Device,
check option Enable SNTP Client.
vi. Click OK.
vii. Verify the time and timezone settings on the GGSN using the CLI
13 Apply the patching profile that was applied to the device before the CMC
replacement. Refer to “Appendix B: GGSN patch Application” in the
GGSN Provisioning Procedures (411-5221-927).
411-5221-923 Standard 06.09 August 2008

Procedure 4-13
Step Action
14 Change bootorder to the select GGSN software on the new CMC card.
Attention: Resync the GGSN to boot up the GGSN software.
– Perform the command “set quickstart” making sure that it has

the correct configuration. You can select the default settings
by just pressing “enter” after each entry.
– Resync the GGSN as per patch instructions. After the GGSN
comes back insync, use the command “show quickstart” to
verify that quickstart configuration is correct.
– Additionally run the command “show config qs1 db=ispmdb”
to ensure that auxiliary and management ports are still
contained in the ispmdb.

-END-

Procedure 4-14
Multiple CMC card configuration
Step Action
1 Perform the steps 1 - 15 of the manual GGSN shutdown procedure. See

“Manual GGSN shutdown, resync, or CMC switchover” on page C-1. This
does the following:
• Deny any new PDP sessions.
• Close all active PDP sessions.
• Save the remaining GTP billing records to the local disk.
• Send all RADIUS accounting information to RADIUS server.
Attention: Also before replacing the card unapply all the patches and
patch profiles as the procedure to bring up the new card will take longer if
the patches are still applied.
2 Use ‘show card’ CLI command to determine if CMC card to be replaced is

in the standby state. For example:
shasta-19(SSU)# show card.

13 CMC /CMC Enabled Standby (Redundant)
14 CMC /CMC Enabled Active
3 If the CMC card to be replaced is in the active state, switch the CMC card
over using ‘switch cmc’ and make active CMC card the standby CMC
card.
4 Perform the procedure to move the GTP billing disk files from the standby
CMC card if necessary. See “Move G-CDR files from standby CMC” on
page C-4.
5 The standby CMC card should be disabled via the SCS GUI:
Device.
d. On the Device tab, click on the Card to be replaced and click “Edit”.
e. Set the Admin Status to Down.
f. Click OK.
6 Issue the ‘show bootorder’ CLI command on the active CMC card and
save it so the new card can match it in later step.
411-5221-923 Standard 06.09 August 2008

Procedure 4-14
Step Action
7 Issue the ‘show quickstart’ CLI command on the active CMC and
save the output display. This information is necessary if the replacement
CMC card does not boot.
8 Disconnect all cables from the standby CMC card. Physically remove the
standby CMC card.
Attention: Do not insert the CMC card until the CMC card is deleted from
the SCS GUI.
9 In the SCS Client Configuration -Device window, delete the standby

CMC.
a. Select the correct row in the card list and click DELETE.
b. Click OK in the delete confirmation box.

Procedure 4-14
Step Action
10 Insert a new CMC card in the same slot as the old standby CMC card.
Reconnect any console and Ethernet cables to the new standby CMC. If
this is a CMC2 card then enable the card from the SCS:
a. Enable the new CMC card via SCS GUI.
— Log in to the Device Owner or any ISP through SCS Client.
— Select the device via Devices -> Regions -> Your Region - > Your
Device.
— Select the GGSN and click “Edit”.
— On the Device tab, click on the Card to be replaced and click
“Edit”.
— Set the Admin Status to Up.
— Click OK.
b. If the new standby CMC card can not find a load to boot or it is stuck
in a boot loop, perform the following:
— During the boot sequence the card will indicate, "Press Space
Bar, then Q, to stop auto-boot...", hit the space bar and q.
— Enter the command "setbp"
— Alter the first boot file to the isn image directory .
The isn image directory for CMC2 is located at "/flash/image/isn/
cmc".
The isn image directory for CMC3 is located at “/disk/image/isn/
cmc3”.
— Everything else leave alone.
— At the end enter "yes" to save the modification.
— Enter "reset" to reboot the card
— If it is still stuck in a boot loop and a known directory path
contains image files this process can be repeated, using this path
as boot file 1. Be sure the path ends with "/cmc".
— If the card is still stuck in a boot loop, it can be booted up from the
network. See “Boot CMC card from network” on page C-12.
— If the card is still stuck in a boot loop this CMC can not be used.
There is no image to bring the card up on, so a new card will
need to be used.
c. If the "[BSN Boot]" prompt is seen, perform the same instructions as
for a boot loop, except do not hit the space bar followed by entering
"Q". Contact next level of support if card is stuck in this state.
411-5221-923 Standard 06.09 August 2008

Procedure 4-14
Step Action
d. If there is a BSN login prompt and after entering the username/

password you can not log in, try and enter "Ctrl-X". This will take the
card to the "[BSN Boot]" prompt. Follow the same instructions as
stated in the first bullet list under option b.
e. If the new CMC can not be brought up contact next level of support.
f. After the standby CMC card successfully comes up log into it from the
console.
g. Enter "show bootorder" and "show version", verify this is the same as
the active CMC.
h. From the active CMC enter "show card" and see if the standby CMC
is redundant.
i. If the standby CMC is marked redundant go to 21, to verify CMC's are
up.
11 Unseat the active CMC card to make the new CMC active.
12 If the CMC card still doesn’t boot up completely, refer to the following:
a. If the CMC card is a CMC2, it can be booted up from the flash
memory or from the network.
b. If the CMC card is a CMC3, it can be booted up from the network.
See “Boot CMC card from network” on page C-12.
13 On the console for the new CMC card, issue the ‘show version’ CLI
command after the CMC boots up. Save this information. The disk
directory that it booted from can be used as a “backup load”.
14 Configure quickstart configuration with IP connectivity information.

set quickstart
15 Log into the new CMC card remotely using the admin password.

Procedure 4-14
Step Action
16 When a fresh CMC card boots up, the software may be the Shasta Base
software. In this case, perform the following:
a. Enter the correct bootorder as the prior standby CMC card had:
For CMC2:
shasta-19(SSU)# set bootorder
flags (f) : 0x80
/* hit Enter */
boot file1 (f1) : /disk/image/ggsns501/cmc /* type /
disk/image/ggsns60/cmc where /disk/image/ggsns60/cmc is the new
bootfile */
boot file2 (f2) : /disk/image/ggsns411/cmc /* type /
disk/image/ggsns501/cmc */
boot file3 (f3) : /disk/image/ggsns4.0/cmc /* type
/disk/image/ggsns411/cmc */
boot file4 (f4) : /flash/image/isn/cmc
/* hit Enter */
boot server address (h) : /
* hit Enter */
configuration (s) :
/* hit Enter */
diag mode (dm) : 0x0 /
* hit Enter */
core dump mode (cm) : 0x0 /*
hit Enter */
For CMC3:
shasta-19(SSU)# set bootorder
flags (f) : 0x80
/* hit Enter */
boot file1 (f1) : /disk/image/ggsns501/cmc3 /* type /
disk/image/ggsns60/cmc3 where/disk/image/ggsns60/cmc is the new
bootfile */
boot file2 (f2) : /disk/image/ggsns411/cmc3 /* type /
disk/image/ggsns501/cmc3 */
boot file3 (f3) : /disk/image/ggsns4.0/cmc3 /* type /
disk/image/ggsns411/cmc3 */
boot file4 (f4) : /disk/image/isn/cmc3
/* hit Enter */
boot server address (h) : /
* hit Enter */
configuration (s) :
/* hit Enter */
diag mode (dm) : 0x0 /
* hit Enter */
core dump mode (cm) : 0x0 /*
hit Enter */
411-5221-923 Standard 06.09 August 2008

Procedure 4-14
Step Action
b. Create directories if necessary and FTP the image files stored in .

Make sure the directory path in the bootorder aligns with the directory
paths where the images are stored in. Also all paths need to end with
“/cmc”:
(on GGSN CLI)

ggsn-065(SSU)# mkdir /disk/image/ggsns5.0
(on the server or PC)
/home/temp 129 ftp 1.2.3.4 /* the GGSN ip address */
Connected to 1.2.3.4.
220 ggsn FTP server ready
Name (1.2.3.4:temp): abcd
331 Password required
Password:
230 User logged in
ftp> cd /disk/image/ggsns5.0
250 Changed directory to "/disk/image/ggsns5.0"
ftp> bin
200 Type set to I, binary mode
ftp> prompt off
Interactive mode off.
ftp> mput *.*
200 Port set okay
150 Opening BINARY mode data connection
226 Transfer complete
local: aps_0_5.bin remote: aps_0_5.bin
127954 bytes sent in 0.021 seconds (6060.49 Kbytes/s)
...
c. For CMC2 verify the location of boot file4 (f4) is “/flash/

image/isn/cmc” and
For CMC3 verify the location of boot file4 (f4) is “/disk/

image/isn/cmc3”
See “Prerequisites for Replacing CMC card” on page 4-35 for details.
17 Show the bootorder of the new CMC card. If it does not match the
standby card, set the bootorder to match the other CMC card.
show bootorder

Procedure 4-14
Step Action
18 If the firmware on the new CMC card is differnt from the one on the
existing CMC card:
a. Verify the bootrom version for the existing CMC card:
show card slot=<existing CMC Slot> mode=detail
b. If the bootrom version on the new CMC card is lower than the one on
the existing CMC card, bootrom upgrade on the new CMC card is
required. See “CMC bootrom upgrade” on page C-14.
Example: If the bootrom version on the new CMC2 card is 6.3(1) and
the existing CMC2 card is 8.0(1), bootrom upgrade to 8.0(1) on the
new CMC2 card is required.
new CMC3 card is required.
c. If the bootrom version on the new CMC card is higher than the one on
the existing CMC card, bootrom upgrade on the existing CMC card is
required. See “CMC bootrom upgrade” on page C-14.
existing CMC2 card is required.
existing CMC3 card is required.
19 Reinsert and reconnect cables to the previous active CMC card if it was
removed.
20 Resync the GGSN to boot up the GGSN load, it should now be

redundant.
21 To check that the other CMC card can come up, issue the ‘switch cmc’
CLI command.
22 It is desirable to let the CMC that contains the remaining GTP billing files
be the active. Issue the ‘switch cmc’ CLI command. After this CMC is
back in operation, the GTP billing files can be transferred to the CGF with
the ‘gtpbill disksend allow’ CLI command.
23 Verify bootorder entry.

show bootorder
411-5221-923 Standard 06.09 August 2008

Procedure 4-14
Step Action
If the bootorder is not appropriate considering the suggested entries for

CMC2 and CMC3, modify it with the following command:
set bootorder
FOR CMC2:
boot file1 (f1) :/disk/image/<current_image>/cmc

boot file3 (f3) :/disk/image/<previous_image>/cmc
boot file4 (f4) :/flash/image/isn/cmc
FOR CMC3 remove all /flash entries in the bootorder:
boot file1 (f1) :/disk/image/<image>/cmc3

boot file3 (f3) :/disk/image/<previous_supported_load>/cmc3
boot file4 (f4) :/disk/image/<default_BSN_load>/cmc3
CMC3 is only supported in PC04 loads.

Attention:
Bootorder is different for CMC2 and CMC3 cards. For CMC2 cards, the
load must be in the /disk with the isn load in the /flash directory. CMC3 has
no /flash entry.
Attention: On the active CMC card verify that all the image files exist
including the “MANIFEST”.

Procedure 4-14
Step Action
If an SNTP server is configured under SNTP Client Configuration, and the
mismatch.
set time YYYY/MM/DD
vi. Click OK.
411-5221-923 Standard 06.09 August 2008

Procedure 4-14
Step Action
25
a. Log in to the GGSN. Issue the command 'show version'. Make a note
of the GGSN software version running.
b. Next, issue the command 'show card'.
If the GGSN has a standby CMC (CMC2/ CMC3) verify the standby CMC
card is in 'Redundant' state. If the standby CMC card is not in Redundant
state, please contact Nortel support.
c. Use the command 'show quickstart' to determine the standby CMC
card management IP address.
d. If the standby CMC card is redundant, telnet to the standby CMC card
and issue the command 'show version'. Make sure the standby CMC
card is running the same version as the active CMC.
e. If the standby CMC is not running the same GGSN software load as
the active CMC, please contact Nortel support.
replacement. Refer to “Appendix B: GGSN Patch Application” in the

correct configuration. You can select the default settings by
just pressing “enter” after each entry.
– In addition, run the command “show config qs1 db=ispmdb”

-END-
Upgrade CMC2 to CMC3

This procedure must only be done during a Maintenance window.
Traffic will be halted during the upgrade. A GGSN that contains both a

CMC3 and CMC2 is not supported outside of this short upgrade

window.
All functionality related to the GGSN will be systematically disabled

before card replacement. Traffic must be redirected from the affected
GGSN for the duration of the CMC2 to CMC3 Upgrade in order to
minimize any network impact.
SCS configuration activity should cease during the short upgrade

window except for the configuration steps required by the CMC2 to
CMC3 Upgrade procedure. All patch profiles on the GGSN will be
unapplied in the following procedures prior to the CMC card gets
upgraded.
Prerequisites for Upgrade CMC2 to CMC3

• The GGSN must be running at least GGSN4.1.1 release software.
— Using the ‘show bootorder ’ CLI command, check that the first
bootorder entry is pointing to the GGSN4.1.1 (or higher) load on
the CMC2’s disk.
— In the Configuration-Device GUI display, check that the iSOS
Version is GGSN4.1.1 (or higher).
• Since the CMC3 does not have server ports, the server port
migration Procedure must already be completed. See “CMC2
Server Port Migration” on page C-33.
• The CMC3 does not have flash or PCMCIA file systems. The USB
ports are not supported. The first and second bootorder entries for
the CMC2 should not be for /flash or /pcmcia during the CMC3
upgrade. After the CMC3 upgrade is successful, all /flash and /
pcmcia bootorder entries will be removed.
• The GGSN is operating normally with no alarm conditions.
• The accounting servers (e.g. CGF, RADIUS, etc.) must be up.
• If a large number of billing, auditing, and/or accounting records are
present on the active and standby disks, this will extend the time
required to perform the upgrade. To minimize the time required
during the upgrade in this case, the “CMC Upgrade/Downgrade
Preparation” procedure can be executed in a separate
maintenance window prior to the CMC2 to CMC3 upgrade
procedure.
411-5221-923 Standard 06.09 August 2008

Procedure 4-15
Single CMC2 card configuration
Step Action
1 This procedure requires that the CMC2 be in slot 14 and slot 13 be

unused. If slot 13 is used, this card must be temporarily removed from slot
13 during the CMC3 Upgrade. After the upgrade is completed, this card
can return to slot 13.
2 Issue the ‘show bootorder’ CLI command and record the bootorder
information for the active CMC2 card.
3 Issue the ‘show quickstart’ CLI command on the active CMC2 and save
the output display.


Procedure 4-15
Step Action

CMC2 card or use the procedure listed below to close all active PDP
contexts.
empty.
411-5221-923 Standard 06.09 August 2008

Procedure 4-15
Step Action
6 Unapply the GGSNS6.0 patching profile to the device. Refer to “Appendix

B: GGSN Patch Application” in the GGSN Provisioning Procedures (411-
5221-927).
7 Insert the CMC3 into slot 13.
8 Wait for the SCS Client to show the CMC3.

b. In the Diagnostics and Maintenance window, click GET CARDS.
c. In the SCS Client Configuration - Device window, wait for the CMC3
to appear in slot 13.
9 Proceed to the next step if the CMC3 has booted up and its Operational
Status is “Up”. If the CMC3 card cannot be booted up, the CMC3 can be
booted from the network. See “Boot CMC card from network” on page C-
12.
10 If the firmware on the new CMC3 card is not an updated one, a bootrom
11 Wait for the CMC3 to become redundant.

a. Double click on the card/slot in the Configuration-Device window and
check the General Redundancy State to see the status.
b. Do not continue to the next step until the CMC3 is redundant.

Procedure 4-15
Step Action
12 Log into the console port on the active CMC2 and perform the following
steps:
Attention: On the active CMC card verify that all the image files
exist including the “MANIFEST”. If the file does not exist call
support for help.
a. Copy image from the active CMC2 to the redundant CMC3.
copy image /disk/image/<image> standby-cmc
Attention: If the “copy image” command fails reboot the active

CMC2 card.
b. Do not continue unless the copy status is “Success”.

c. Perform a switchover between the CMC2 and the CMC3.
switch cmc
d. If the switchover was successful, the newly-installed CMC3 is the
active CMC.
13 Disconnect cables from the CMC2 and connect them to the CMC3.
14 From the SCS Client, verify that the GGSN is In Sync.
15 Check that the CMC2 is now in the Standby state.

a. In the Diagnostics and Maintenance window, click GET CARDS.
b. Double click on the card/slot in the Configuration-Device window and
16 Disable the standby CMC2 card via the SCS GUI:

a. In the SCS Client Configuration-Device window, open the Edit Card
dialog by double-clicking the correct row in the card list
b. Set Admin Status to DOWN.
c. Click OK.
17 Remove the CMC2 from slot 14.
18 In the SCS Client Configuration-Device window, delete the standby

CMC2.
b. Click OK.
411-5221-923 Standard 06.09 August 2008

Procedure 4-15
Step Action
19 Power down the GGSN chassis.
20 Move the CMC3 from slot 13 to slot 14.
21 Power up the GGSN chassis.
22 The GGSN will be Out-of-sync. A Card Mismatch window will appear.

Click OK. There also will be a session error: Out Of Sync Session Error
Sequence Mismatch.
23 In the SCS Client Configuration-Device window, delete the mismatched

CMC3 in slot 13.
b. Click OK.
24 Resync the GGSN.
25 Remove /flash and /pcmcia bootorder entries since the CMC3 cannot be
booted using /flash or /pcmcia.
26 Resync the GGSN to boot up the GGSN software.

Procedure 4-15
Step Action
mismatch.
set time YYYY/MM/DD
vi. Click OK.

-END-
411-5221-923 Standard 06.09 August 2008

Procedure 4-16
Multiple CMC2 card configuration
Step Action
1 Issue the ‘show card’ CLI command to determine which card is Active
and which card is Standby.
3 Issue the ‘show quickstart’ CLI command on the active CMC and save
the output display. This information is necessary if the replacement CMC
card does not boot.
4 If the CMC card to be replaced is in standby state, and no billing or

auditing records are present on the standby CMC, proceed to step 8.
Check if the Accounting files are present or not on the standby in the
directory /disk/ACCT/GTP. See “Move G-CDR files from standby CMC”
on page C-4
5 If the CMC card to be replaced is standby and billing or auditing records

are present on the standby CMC, switch the CMC card using ‘switch
cmc’ and make the active CMC card the standby CMC card.
Attention: The Card to be replaced should now be the active

CMC.
6 Perform the steps 3 - steps 12 of the ““CMC Upgrade/Downgrade

Preparation” on page C-6” procedure as found in “Appendix C: Product
maintenance procedures” on page C-1”. This procedure sends all billing,
accounting, and/or auditing records from both the active and standby
CMCs to their appropriate collection servers in order to ensure that no
such information is lost during the upgrade.
7 Switch the CMC card using “switch cmc” and make the active CMC card
the standby CMC card.
Attention: The card to be replaced should now be the Standby

CMC.
8 Unapply the GGSN patching profile to the device. Refer to “Appendix B:

GGSN patch application” in GGSN Provisioning Procedures (411-5221-
927).

Procedure 4-16
Step Action

b. In the SCS Client, click on Devices in icon panel, select the
region,right-click on the Device, click Configure then Device.
c. In the Configuration-Device window, open the Edit Card dialog by
double-clicking the correct row in the card list.
d. Set Admin Status to DOWN.
e. Click OK.
10 Remove all cables from the faceplate connections of the standby CMC2
card. Physically remove the standby CMC2 card.
Attention: Do not insert the CMC3 card until it is deleted from the
SCS GUI.

CMC2.
12 Insert a CMC3 card into the same slot from which the CMC2 card was
removed.
Status is “Up”. If the CMC3 cannot be booted up, abort this procedure by
proceeding to the Abort CMC2 to CMC3 procedure. See “Abort CMC2 to
CMC3 Upgrade” on page 4-67.
14 On the console for the new CMC3 card, issue the ‘show version’ CLI
command. Save this information. The disk directory that it booted from
can be used as a backup load for this card.
15 Wait for the SCS Client to show the new CMC3 card. In a busy SCS
system, this could take several minutes. This process can be encouraged
by clicking “GET CARDS” in the Diagnostics and Maintenance window.
411-5221-923 Standard 06.09 August 2008

Procedure 4-16
Step Action
16 Wait for the CMC3 card to go into “Standby” state. A short delay may
occur as configuration data is copied to the newly-installed CMC3 card.
• Double click on the card/slot on the Configuration->Device page and
check the Redundancy State to see the status. The Redundancy
State status should be “Standby”. Confirm with OK.
• Do not continue to the next step until the CMC3 is in the Standby
state. If the CMC3’s does not go into the Standby state, proceed to
the Abort CMC2 to CMC3 procedure. See “Abort CMC2 to CMC3
Upgrade” on page 4-67.

Procedure 4-16
Step Action
18 Logon using the console port on the active CMC2 and perform the
following step:
a. On the active CMC2 load verify that all the image files exist including
the “MANIFEST”
Attention: If any of the files are missing please contact product

support.
b. Copy load from the active CMC2 to the standby CMC3 to ensure the
load is the same and in the same directory on both cards. The “/
disk/image/<image>” parameter below must be the same as the
first bootorder entry.

CMC2 card.
Create the directories if they do not exist by using a telnet session to the
standby-cmc.
An INFO message appears on the console/event logs saying that CMC3
configurations are not the same.
c. Do not continue unless the copy status is “Success”. If the copy
status is not “Success”, proceed to the Abort CMC2 to CMC3
procedure. See “Abort CMC2 to CMC3 Upgrade” on page 4-67.
List the files on the standby-cmc image directory and verify that all the
files listed are copied in the standby-cmc image directory.
d. If you are using GTP accounting, copy the CHGSEQNO file in the
cdrs subdirectory to the standby CMC by issuing the following
command:
copy file /disk/acct/gtp/cdrs/CHGSEQNO standby-cmc
Create the below directories if they do not exist by using a telnet session
to the standby-cmc:
telnet <standby-cmc>
mkdir /disk/acct
mkdir /disk/acct/gtp
mkdir /disk/acct/gtp/cdrs
411-5221-923 Standard 06.09 August 2008

Procedure 4-16
Step Action
19 From the active CMC2 console, perform a switchover between the CMC2
and the CMC3 cards.
switch cmc
If the switchover was successful, the newly-installed CMC3 card is the
active CMC card.
Attention: It is possible that the GGSN may go out-of-sync.
20 From the SCS Client, verify that the GGSN is insync. If the GGSN is not
insync, due to a session error “Session Sequence number mismatch”,
resync the GGSN from the SCS Client GUI. Wait for the GGSN to come
back insync.
21 In the SCS Client Configuration-Device window, disable the standby

CMC2.
a. In the SCS Client, click on Devices in icon panel, select the
region,right-click on the Device, click Configure then Device.
b. In the Configuration-Device window, open the Edit Card dialog by
double-clicking the correct row in the card list.
c. Set Admin Status to DOWN.
d. Click OK.
card. Remove the standby CMC2 card from the chassis slot. The CMC3
card should not be inserted in the empty slot until it is deleted from the
SCS GUI or until a later step.

CMC2 card.
• Select the correct row in the card list and click DELETE.
• Click OK in the delete confirmation dialog box.
24 Insert the second CMC3 card into the chassis slot from which the standby
CMC2 was removed.
25 Reconnect any console and Ethernet cables to the CMC3 card faceplate.
Status is “Up”. If the CMC3 card cannot be booted up, abort this
procedure by proceeding to the Abort CMC2 to CMC3 procedure. See
“Abort CMC2 to CMC3 Upgrade” on page 4-67.
command. Save this information. The disk directory that it booted from
can be used as a “backup load” for this card.

Procedure 4-16
Step Action
State status should be “Standby”.
• Do not continue to the next step until the CMC3 card is in the Standby
state. If the CMC3 card does not go into the Standby state, proceed
to the Abort CMC2 to CMC3 procedure. See “Abort CMC2 to CMC3
Upgrade” on page 4-67.
30 Logon using the console port on the active CMC3 card and perform the
following step:
a. On the active CMC card verify that all the image files exist including
the “MANIFEST”. If the file does not exist call support for help.
b. Copy load from the active CMC3 card to the standby CMC3 card to
ensure the load is the same and in the same directory on both cards.
The “/disk/image/<image>” parameter below must be the same
as the first bootorder entry.
Create the directories if they do not exist by using a telnet session to the
standby-cmc.
An INFO message appears on the console/event logs saying that CMC3
configurations are not the same.
procedure. See “Abort CMC2 to CMC3 Upgrade” on page 4-67.
command:
to the standby-cmc:
mkdir /disk/acct
31 Issue the command “reboot standby-cmc” to bring the card on the GGSN
5.0 load.
411-5221-923 Standard 06.09 August 2008

Procedure 4-16
Step Action

show bootorder
set bootorder

34

Procedure 4-16
Step Action
35 After the GGSN comes back insync, apply the GGSN patching profile to
the device. Refer to “Appendix B: GGSN patch application” in GGSN
Provisioning Procedures (411-5221-927).
– Additionally run the command “show config qs1 db=ispmdb”
36 The active slot for the CMC has been changed as a result of the upgrade
procedure. An optional “switch cmc” can be issued to return the active
CMC card to the same slot as at the beginning of the procedure.
411-5221-923 Standard 06.09 August 2008

Procedure 4-16
Step Action
mismatch.
set time YYYY/MM/DD
vi. Click OK.

39 Perform test calls to check that the newly-active CMC3 card is

operational. If the active CMC3 card is not operational, abort this
“Abort CMC2 to CMC3 Upgrade” on page 4-67.

Procedure 4-16
Step Action
40 If the CMC3 upgrade is successful, remove all bootorder entries of /flash

and /pcmcia. The CMC3 only supports booting off the disk and the
network.
-END-
411-5221-923 Standard 06.09 August 2008

Abort CMC2 to CMC3 Upgrade

Procedure 4-17
Aborting CMC2 to CMC3 Upgrade
Step Action
1 Disable the standby CMC3 card via the SCS GUI.

CMC3 card.
4 Reinsert the CMC2 card into the same slot from which the standby CMC3
card was removed.
5 Reconnect any console and Ethernet cables.
6 The CMC2 card should come up as the standby.
7 If there is no more CMC3 card in the chassis, this procedure has been
completed. Otherwise, from the still active CMC3 console, perform a
switchover (switch cmc) between the CMC2 card and the CMC3 card.
The CMC3 card should become the standby.
8 Repeat steps 1- 6 in order to return the other CMC2 card to the chassis.
9 From the active CMC2 card, re-add the previously recorded bootorder
entries for /flash and /pcmcia. These bootorder entries were removed
during the upgrade.

Procedure 4-17
Step Action
mismatch.
set time YYYY/MM/DD
vi. Click OK.
411-5221-923 Standard 06.09 August 2008

Procedure 4-17
Step Action
11
-END-
Post CMC3 Upgrade procedure

This procedure creates a backup software load on the active and
standby CMC3 card.
Procedure 4-18
Step Action
1 Logon using the console port on the active CMC3 card.
2 Create a backup load directory.

cd /disk/image
mkdir backup
3 Copy the software load to the backup directory.
Attention: On the active CMC card verify that all the image files
exist including the “MANIFEST”. If the file does not exist call
support for help.
copy image /disk/image/<image> /disk/image/backup
4 Copy the backup load to the standby CMC3 card.

copy image /disk/image/backup/<image> standby-cmc

Procedure 4-18
Step Action
5 Change the bootorder to include the backup image “/disk/image/backup/

<image>/cmc3” as the last boot file.
set bootorder
-END-
Downgrade CMC3 to CMC2

If it becomes necessary to return to the CMC2 card after the CMC3
card has been installed, this procedure should be performed. Also,
CMC3 card is supported with GGSNS4.1.1 load, this procedure
doesn’t need to be done prior to the software rollback to GGSNS4.1.1.
This procedure must only be done during a Maintenance window.

Traffic must be halted during the downgrade. A GGSN that contains
both a CMC3 and CMC2 is not supported outside of this short upgrade
window.
All functionality related to the GGSN will be systematically disabled

before card replacement. Traffic must be redirected from the affected
GGSN for the duration of the CMC3 to CMC2 downgrade in order to
minimize any network impact.
SCS configuration activity should cease during the short downgrade

window except for the configuration steps required by the CMC3 to
CMC2 Downgrade procedure.
Prerequisites for Downgrade CMC3 to CMC2

• The GGSN must be running at least GGSN4.1.1 release software.
— Using the ‘show bootorder’ CLI command, check that the first
bootorder entry is pointing to the GGSN4.1.1 (or higher) load on
the CMC3’s disk.
— In the Configuration-Device GUI display, check that the iSOS
Version is GGSN4.1.1 (or higher).
• The GGSN is operating normally with no alarm conditions.
• The accounting servers (e.g. CGF, RADIUS, etc.) must be up.
• If a large number of billing, auditing, and/or accounting records are
present on the active and standby disks, this will extend the time
required to perform the downgrade. To minimize the time required
during the downgrade in this case, the “CMC Upgrade/Downgrade
Preparation” procedure can be executed in a separate
411-5221-923 Standard 06.09 August 2008

maintenance window prior to the CMC2 to CMC3 downgrade

procedure.

Procedure 4-19
Single CM3 card configuration
Step Action
1 This procedure requires that the CMC3 be in slot 14 and slot 13 be

unused. If slot 13 is used, this card must be temporarily removed from slot
13 during the CMC3 Downgrade. After the downgrade is completed, this
card can return to slot 13.
the output display.

411-5221-923 Standard 06.09 August 2008

Procedure 4-19
Step Action

CMC2 card or use the procedure listed below to close all active PDP
contexts.
empty.

Procedure 4-19
Step Action
6 Unapply the GGSNS6.0 patching profile to the device. Refer to “Appendix

B: GGSN Patch Application” in the GGSN Provisioning Procedures (411-
5221-927).
7 Insert the CMC2 into slot 13.
8 Wait for the SCS Client to show the CMC2

b. In the Diagnostics and Maintenance window, click GET CARDS.
c. In the SCS Client Configuration - Device window, wait for the CMC2
to appear in slot 13.
Status is “Up”. If the CMC2 card cannot be booted up, the CMC2 can be
booted from its flash memory or from the network. See “Boot CMC card
from network”.
10 If the firmware on the new CMC2 card is not an updated one, a bootrom
11 Wait for the CMC2 to become redundant.

a. Double click on the card/slot in the Configuration-Device window and
b. Do not continue to the next step until the CMC2 is redundant.
12 Log into the console port on the active CMC3 and perform the following
steps:
b. Copy image from the active CMC3 to the redundant CMC2.

CMC3 card.
c. Do not continue unless the copy status is “Success”.

d. Perform a switchover between the CMC3 and the CMC2
switch cmc
e. If the switchover was successful, the newly-installed CMC2 is the

active CMC.
13 Disconnect cables from the CMC3 and connect them to the CMC2.
411-5221-923 Standard 06.09 August 2008

Procedure 4-19
Step Action
14 From the SCS Client, verify that the GGSN is In Sync.
15 Check that the CMC3 is now in the Standby state.

a. In the Diagnostics and Maintenance window, click GET CARDS.
b. Double click on the card/slot in the Configuration-Device window and

a. In the SCS Client Configuration-Device window, open the Edit Card
dialog by double-clicking the correct row in the card list
c. Click OK.
17 Remove the CMC3 from slot 14.

CMC3.
b. Click OK.
19 Power down the GGSN chassis.
20 Move the CMC2 from slot 13 to slot 14.
21 Power up the GGSN chassis.
22 The GGSN will be Out-of-sync. A Card Mismatch window will appear.

Click OK. There also will be a session error: Out Of Sync Session Error
Sequence Mismatch.
23 In the SCS Client Configuration-Device window, delete the mismatched

CMC2 in slot 13.
b. Click OK.
24 Resync the GGSN.
25 Add the /flash and /pcmcia bootorder entries to the CMC2.
26 Resync the GGSN to boot up the GGSN software.

Procedure 4-19
Step Action
27
28 Apply the GGSNS5.0 patching profile to the device. Refer to “Appendix B:

GGSN Patch Application” in the GGSN Provisioning Procedures (411-
5221-927).
– In additional run the command “show config qs1 db=ispmdb”
411-5221-923 Standard 06.09 August 2008

Procedure 4-19
Step Action
mismatch.
set time YYYY/MM/DD
vi. Click OK.

-END-

Procedure 4-20
Step Action
1 Issue the ‘show card’ CLI command to determine which card is Active
and which card is Standby.
the output display. This information is necessary if the replacement CMC2
card does not boot.
4 If the CMC card to be replaced is in standby state, and no billing or

auditing records are present on the standby CMC, proceed to step 8.
Check if the Accounting files are present or not on the standby in the
directory /disk/ACCT/GTP. See “Move G-CDR files from standby CMC”
on page C-4
5 If the CMC card to be replaced is standby and billing or auditing records

are present on the standby CMC, switch the CMC card using “switch
cmc” and make the active CMC card the standby CMC card.
Attention: The card to be replaced should now be the active CMC.
6 Perform the steps 3 - steps 12 of the “CMC Upgrade/Downgrade

Preparation” on page C-6 procedure as found in “Appendix C: Product
maintenance procedures” on page C-1”. This procedure sends all billing,
accounting, and/or auditing records from both the active and standby
CMCs to their appropriate collection servers in order to ensure that no
such information is lost during the downgrade.
7 Switch the CMC card using “switch cmc” and make the active CMC card
the standby CMC card.
Attention: The card to be replaced should now be the standby

CMC.
8 Unapply the GGSNS patching profile to the device. Refer to Appendix B:

GGSN Patch Application in GGSN Provisioning Procedures (411-5221-
927).
411-5221-923 Standard 06.09 August 2008

Procedure 4-20
Step Action

b. Click on “Devices”.
c. Right click on the GGSN device and select “Configure” and then
select “Device...”
d. In the cards window select the standby CMC3 and click on “Edit...”
e. Set Admin Status to DOWN.
f. Click OK.
Attention: Do not insert the CMC2 card until the CMC3 card is
deleted from the SCS GUI.

CMC3.
12 Insert a CMC2 card into the same slot from which the CMC3 card was
removed.
13 Reconnect any console and Ethernet cables to the CMC2.
Status is “Up”. If the CMC2 cannot be booted up, it can be booted from
the network See “Boot CMC card from network” on page C-12 or from
flash memory.
command. Save this information.
16 If the bootcode on the CMC2’s bootrom is out of date, an upgrade of the

bootrom is required. See “CMC bootrom upgrade” on page C-14.

Procedure 4-20
Step Action
State status should be “Standby”. Confirm with OK.
• Do not continue to the next step until the CMC2 is in the Standby
state. If the CMC2 does not go into the Standby state, proceed to the
Abort CMC3 to CMC2 procedure. See “Abort CMC3 to CMC2
Downgrade” on page 4-87
19 Logon using the console port on the active CMC3 and perform the
following step:
b. Copy load from the active CMC3 to the standby CMC2 to ensure the
load is the same and in the same directory on both cards. The “/
disk/image/<image>” parameter below must be the same as the
first bootorder entry.

CMC3 card.

procedure. See “Abort CMC3 to CMC2 Downgrade” on page 4-87.
command:
to the standby-cmc:
mkdir /disk/acct
411-5221-923 Standard 06.09 August 2008

Procedure 4-20
Step Action
20 From the active CMC3 console, perform a switchover between the CMC3
and the CMC2 cards.
switch cmc
If the switchover was successful, the newly-installed CMC2 card is the
active CMC card.
When the switch cmc command is issued on the shasta, if the standby
CMC is redundant, “The CMC switch will cause the CMC boards in the
BSN to become temporarily non-redundant” warning is seen on the active
console.
21 If only one management Ethernet cable and/or console is available for the
GGSN, disconnect it/them from the standby CMC3 card and connect it/
them to the faceplate of the active CMC2 card.
22 From the SCS Client, verify that the GGSN is In Sync. If the GGSN and
SCS are no longer in sync, resync the Device.
23 In the SCS Client Configuration-Device window, disable the standby

CMC3.
a. Open the Edit Card dialog by double clicking the correct row in the
card list.
c. Click OK.
card. Remove the standby CMC3 card from the chassis slot.

CMC3 card.
• Select the correct row in the card list and click DELETE.
• Click OK in the delete confirmation dialog box.
26 Insert the second CMC2 card into the chassis slot from which the standby
CMC3 was removed.
27 Reconnect any console and Ethernet cables to the CMC2 card faceplate.
Status is “Up”. If the CMC2 cannot be booted up, it can be booted from
the network See “Boot CMC card from network” on page C-12 or from
flash memory.
command. Save this information.

Procedure 4-20
Step Action
30 If the bootcode on the CMC2 card bootrom is out of date, an upgrade of

the bootrom is required. See “CMC bootrom upgrade” on page C-14.
State status should be “Standby”.
• Do not continue to the next step until the CMC2 card is in the Standby
state. If the CMC2 card does not go into the Standby state, proceed
to the Abort CMC3 to CMC2 procedure. See “Abort CMC3 to CMC2
Downgrade” on page 4-87.
411-5221-923 Standard 06.09 August 2008

Procedure 4-20
Step Action
33 Logon using the console port on the active CMC2 card and perform the
following step:
b. Copy load from the active CMC2 card to the standby CMC2 card to
ensure the load is the same and in the same directory on both cards.
The “/disk/image/<image>” parameter below must be the same
as the first bootorder entry:

procedure. see abort CMC3 to CMC2 downgrade.
command:
to the standby-cmc:
mkdir /disk/acct
e. From the still active CMC2 console, perform a switchover between

the active CMC2 card and the standby CMC2 cards.
switch cmc
f. If the switchover was successful, the newly-installed CMC2 is the
active CMC card.

Procedure 4-20
Step Action

show bootorder
set bootorder
FOR CMC2:

boot file2 (f2) :/disk/image/<previous_image>/cmc
boot file3 (f3) :
boot file4 (f4) :/flash/image/isn/cmc


Attention: Bootorder is different for CMC2 and
CMC3 cards. For CMC2 cards, the load must be in
the /disk with the isn load in the /flash entry. CMC3
has no /flashentry.
On the active CMC card verify that all the Image files exist including the
“MANIFEST”. If the file does not exist call support for help.
411-5221-923 Standard 06.09 August 2008

Procedure 4-20
Step Action
35
36 Apply the GGSN patching profile to the device. Refer to Appendix B:

GGSN Patch Application in GGSN Provisioning Procedures (411-5221-
927).
– In addition run the command “show config qs1 db=ispmdb” to
ensure that auxiliary and management ports are still
The active slot for the CMC has been changed as a result of the
downgrade procedure. An optional “switch cmc” can be issued to return
the active CMC card to the same slot as at the beginning of the
procedure.

Procedure 4-20
Step Action
mismatch.
set time YYYY/MM/DD
vi. Click OK.

39 Perform test calls to check that the newly-active CMC2 card is

operational. If the active CMC2 card is not operational, abort this
“Abort CMC3 to CMC2 Downgrade” on page 4-87.
411-5221-923 Standard 06.09 August 2008

Procedure 4-20
Step Action
40 If the downgrade to CMC2 is successful, add the bootorder entries of /

flash and /pcmcia.
-END-
Abort CMC3 to CMC2 Downgrade

Contact Nortel Networks personnel about re-installing the CMC2 in the GGSN.
Replacing an SSC-2/SSC-3 Card

Single SSC card configuration
This section describes the card replacement procedure for the single
SSC card configuration in the Nortel GGSN chassis. It is
recommended that the new card is inserted into a vacant SSC slot
different from the slot of the old card. This approach will provide a
suitable destination for sessions on the replaced card to migrate.
Procedure 4-21
Step Action
1 Log into the Nortel GGSN console.
2 Flush Billing information to the CMC using the CLI command ‘gtpbill
flush billing <accounting_ispname>’. The progress of the
billing flush can be monitored via the command ‘show gtpbill
<ispname>’. There is a line in the display “Bulk Update in Progress”.
When this line is set to “No”, accounting information has been flushed
from the SSPs to the CMC.
3 Physically insert the new card into a different slot from the old card.
4 Once the new card has booted up to status “UP” as described by the card
LED display, verify that it has the same bootrom as the old card. If a
bootrom upgrade is needed, perform the bootrom upgrade. For detailed
procedure, See “SSM bootrom upgrade” on page C-19.

Procedure 4-21
Step Action
5 Via SCS GUI, verify that the new card has been detected by the Nortel
GGSN.
a. Log in Device Owner or any ISP through SCS Client.
Device.
c. Select the device and click “Edit”.
d. On the Device tab, look for an SSC card present in the slot it is added
to.
e. Click on the SSC card and click “Edit”.
f. If the card or its SSMs are disabled, enable them.
g. Click OK.
6 Disable the old SSC.

Device.
d. On the Device tab, click on the card to be replaced and click “Edit”.
e. Individually disable all the SSMs and finally disable the card itself.
f. Click OK. At this point, any services type PDP sessions present on
the old SSC card should start moving from the old card to the new
card if the old card is operational.
7 Physically remove the old card.
8 Remove old card via SCS.

Device.
d. On the Device tab, click on the removed card and click “Delete”.
e. Click OK.
9 Log out of the GGSN console.
-END-
411-5221-923 Standard 06.09 August 2008

Multiple SSC card configuration

This section describes the card replacement procedure for the multiple
SSC card configuration in the SSG chassis. Disabling an SSC card
should cause existing PDP sessions on the old card to move to other
SSC cards, if they can handle extra PDP sessions. In case other SSC
cards cannot handle the extra burden, the displaced PDP sessions will
be dropped. Since all cards are hot-swappable, there is no need to
deny traffic before card replacement, if there are sufficient cards on the
SSG.
Procedure 4-22
Step Action
1 Log into the Nortel GGSN console
2 Identify the slots which the SSC cards occupy:

show card
3 For each SSC card listed perform a ‘show card slot=xx detail’. The
parameter ‘xx’ is the slot number of the SSC. This will display the
Bootrom version for each SSM on the line “ROM version:”. Record the
bootrom version for the SSMs of each SSC card.
4 Flush Billing information using the CLI command ‘gtpbill flush

billing <ispname>’ with Ga or Gn ISP. The progress of the billing
flush can be monitored via the command ‘show gtpbill
5 Disable the old SSC.

Device.
e. Individually disable all the SSMs and finally disable the card itself.
f. Click OK.
6 Physically remove the old card.

Procedure 4-22
Step Action

a. Log in to Device Owner or any ISP through SCS Client.
Device.
e. Click OK.
8 Physically insert the new card into the same slot of the old card.
LED display, verify if the firmware on the new SSC card is differnt from
the one on other SSC cards:
a. Verify the bootrom version for the new SSC card:
show card slot=<new SSC Slot> mode=detail
b. If the bootrom version on the new SSC card is equal to the one on
other SSC cards (obtained from step 3), go to step 10.
c. If the bootrom version on the new SSC card is lower than the one on
other SSC cards, bootrom upgrade on the new SSC card is required.
For details procedure, See “SSM bootrom upgrade” on page C-19.
Example: If the bootrom version on the new SSC2 card is 6.0(1) and
the existing SSC2 card is 6.1(2), bootrom upgrade to 6.1(2) on the
new SSC2 card is required.
the existing SSC3 card is 1.5(1), bootrom upgrade to 1.5(1) on the
new SSC3 card is required.
d. If the bootrom version on the new SSC card is higher than the one on
other SSC cards, bootrom upgrade on other SSC cards is required.
For details procedure, See “SSM bootrom upgrade” on page C-19.
the existing SSC2 card is 6.1(2), bootrom upgrade to 6.2(1) on other
SSC2 cards is required.
the existing SSC3 card is 1.5(1), bootrom upgrade to 1.6(1) on other
SSC3 cards is required.
411-5221-923 Standard 06.09 August 2008

Procedure 4-22
Step Action
10 Via SCS GUI, verify that the new card is detected from the Nortel GGSN.
Device.
e. If the card or its SSMs are disabled, enable them.
f. Click OK.
11 Log out of the Nortel GGSN console.
-END-
SSC-2 to SSC-3 Upgrade

This section describes the card upgrade procedure for SSC-2 to SSC-
3 configuration in the Nortel GGSN chassis. SSC-2 and SSC-3 cannot
coexist in the same chassis except during this upgrade procedure.
When upgrading, all SSC-2 cards must be removed and only SSC-3
cards may be inserted. Disabling an SSC-2 card should cause existing
PDP sessions on the removed SSC-2 card to move to SSC-2 cards, if
they can handle extra PDP sessions. In case the SSC-2 cards cannot
handle the extra burden, the displaced PDP sessions will be dropped.
Since all cards are hot-swappable, there is no need to deny traffic
before card replacement, if there are sufficient cards on the Nortel
GGSN. SSC-2 to SSC-3 upgrade process is not service impacting.
Prerequisites for SSC-2 to SSC-3 upgrade

• The GGSN must be running GGSN5.0.1 software or later and be
upgraded to CMC3.
• SSC-3 is not compatible with SFC1. Make sure there are no
SFC1s in the shelf before starting the SSC-2 to SSC-3 hardware
upgrade procedure.
Procedure 4-23
Upgrading from SSC-2 to SSC-3
Step Action
1 Log into the GGSN console

Procedure 4-23
Step Action

3 If there are fewer than 6 SSC-2 cards in the GGSN, fill the empty slots
with SSC-3 cards by following steps 4 through 6.
4 Physically insert the new SSC3 card into an empty slot.
LED display, verify the new SSC3 SSM bootrom version. If a bootrom
upgrade is needed, perform the bootrom upgrade. See “SSM bootrom
upgrade” on page C-19 for procedure details.
6 Via SCS GUI, verify that the new card has been detected by the Nortel
GGSN.
Device.
d. On the Device tab, look for an SSC-3 card present in the slot it is
added to.
e. Click on the SSC-3 card and click “Edit”.
f. If the card or its SSMs are disabled, enable them.
g. Click OK.
7 Go to step 16.
8 If there are 6 SSC-2 cards in the GGSN, follow step 8 through step 14
until all SSC-3 cards have been inserted.
Attention: Activate SSC-3 migration mode by entering the CLI command ‘set
ssc3 migration active’. With SSC-3 migration mode active, aggregation sessions
will be allowed to move more than once and will not be lost during card
replacement. The migration mode will be set to inactive by the GGSN software
during SSM redundancy processing. If an SSM/SSC fail after the ‘set ssc3
migration active’ CLI command was issued but before the SSC was disabled, the
CLI command should be issued again before the card is disabled.
411-5221-923 Standard 06.09 August 2008

Procedure 4-23
Step Action
9 Disable one SSC-2 card.

a. Activate SSC-3 migration mode:
set ssc3 migration active
b. Verify SSC-3 migration state is active:
show ssc3 migration state
c. Log in Device Owner or any ISP through SCS Client.
d. Select the device via Devices -> Regions -> Your Region - > Your
Device.
e. Select the device and click “Edit”.
f. On the Device tab, click on the card to be replaced and click “Edit”.
g. Disable the first SSM
h. Verify SSC-3 migration state is inactive:
i. Repeat steps a to h until all SSMs are disabled.
j. Finally disable the SSC-2 card
k. Follow step c through e and disable the SSC-2 card.
l. Click OK.
10 Physically remove the old SSC-2 card.

Device.
e. Click OK.
12 Physically insert the new SSC-3 card into the same slot of the old card.
13 Once the new SSC-3 card has booted up to status “UP” as described by
the card LED display, follow procedure “SSM bootrom upgrade” on page
C-19 and verify that the new SSC-3 card has the correct bootrom.

Procedure 4-23
Step Action
14 Via SCS GUI, verify that the new card is detected from the Nortel GGSN.
Device.
c. Select the device and click “Edit”. If the card is not automatically
detected by SCS, perform steps d through f:
d. Right click on Your Device.
e. Select “Diagnostics & Maintenance”.
f. Click on “Get Cards” in the upper right hand corner.
15 Remove the SSC-2 cards and replace them with SSC-3 cards by
following step 1 through step 14 for each SSC-2 cards.
16 Verify that migration mode is no longer active by entering the CLI

command ‘show ssc3 migration status’. If the response to this
command indicates that the migration mode is active, deactivate SSC-3
migration mode by entering the CLI command ‘set ssc3 migration
inactive’.
-END-
SSC-3 to SSC-2 Downgrade

This section describes the card downgrade procedure for SSC-3 to
SSC-2 configuration in the SSG chassis. SSC-2 and SSC-3 cannot
coexist in the same chassis except during an upgrade or downgrade
procedure. When downgrading, all SSC-3 cards must be removed and
only SSC-2 cards may be inserted. Disabling an SSC-3 card will cause
existing PDP sessions on the disabled SSC-3 card to move to other
cards, if they can handle additional PDP sessions. In case the SSC-2
cards cannot handle the extra burden, the displaced PDP sessions will
411-5221-923 Standard 06.09 August 2008

be dropped. SSC-3 to SSC-2 rollback process is service impacting

due to GGSN resync is required.
Procedure 4-24
Downgrading from SSC-3 to SSC-2
Step Action

2 Log into the SSG console

4 If six SSC-3 cards are present, go to step 15.
5 If fewer than six SSC-3 cards are present on the GGSN, the SSC-2 cards
should be placed in empty slots first. Repeat step 6 through step 8 below
until all empty slots are filled, (or all SSC-2 cards have been inserted).
6 Physically insert the new SSC-2 card into a different slot from the old
SSC-3 card.
the card LED display, verify the new SSC-2 SSM bootrom version. If a
bootrom upgrade is needed, perform the bootrom upgrade. See “SSM
bootrom upgrade” on page C-19 for details.

Procedure 4-24
Step Action
8 Via SCS GUI, verify that the new SSC-2 card has been detected by the
Nortel GGSN.
Device.
d. On the Device tab, look for an SSC-2 card present in the slot it is
added to.
e. Click on the SSC-2 card and click “Edit”.
f. If the SSC-2 card or its SSMs are disabled, enable them.
g. Click OK.
9 The SSC-3 cards should be removed by following step 10 through step

13 until all SSC-3 cards are removed.
Attention: Activate SSC-3 migration mode by entering the CLI

command ‘set ssc3 migration active’. With SSC-3 migration mode
active, aggregation sessions will be allowed to move more than
once and will not be lost during card replacement. The migration
mode will be set to inactive by the GGSN software during SSM
redundancy processing. If an SSM/SSC fails after the ‘set ssc3
migration active’ CLI command was issued but before the SSC
was disabled, the CLI command should be issued again before the
SSC-3 card is disabled.
411-5221-923 Standard 06.09 August 2008

Procedure 4-24
Step Action

a. Activate SSC-3 migration mode:
b. Verify SSC-3 migration state is active:
c. Log in Device Owner or any ISP through SCS Client.
d. Select the device via Devices -> Regions -> Your Region - > Your
Device.
e. Select the device and click “Edit”.
f. On the Device tab, click on the SSC-3 card to be replaced and click
“Edit”.
g. Disable the first SSM
h. Verify SSC-3 migration state is inactive:
i. Repeat a to h until all SSMs are disabled.
j. Finally disable the SSC-3 card
k. Follow step c through e and disable the SSC-3 card.
l. Click OK.
12 Remove old SSC-3 card via SCS.

Device.
d. On the Device tab, click on the removed SSC-3 card and click
“Delete”.
e. Click OK.
13 Go to step 25..
14 Remove the SSC-3 cards and replace them with SSC-2 cards by
following steps 15 through 21 for each SSC-3 card.

Procedure 4-24
Step Action
15 Activate SSC-3 migration mode by entering the CLI command ‘set ssc3
migration active’. With SSC-3 migration mode active, aggregation
sessions will be allowed to move more than once and will not be lost
during card replacement. The migration mode will be set to inactive by the
GGSN software during SSM redundancy processing. If an SSM/SSC fail
after the ‘set ssc3 migration active’ CLI command was issued
but before the SSC was disabled, the CLI command should be issued
again before the SSC-3 card is disabled.

Device.
d. On the Device tab, click on the SSC-3 card to be replaced and click
“Edit”.
e. Individually disable the SSMs and enter the CLI ‘set ssc3
migration active’ until all the SSMs are disabled. This step is
repeated 4 times for each SSM.
f. Finally disable the SSC-3 card itself and enter the CLI ‘set ssc3
migration active’.
g. Click OK.
18 Remove old SSC-3 card via SCS.

Device.
d. On the Device tab, click on the removed SSC-3 card and click
“Delete”.
e. Click OK.
19 Physically insert the replacement SSC-2 card into the same slot as the
old SSC-3 card.
the card LED display, verify that it has the correct bootrom. If a bootrom
upgrade is desired, perform the bootrom upgrade. For detailed
procedure, See “SSM bootrom upgrade” on page C-19.
411-5221-923 Standard 06.09 August 2008

Procedure 4-24
Step Action
21 Via SCS GUI, verify that the new SSC-2 card is detected from the Nortel
GGSN.
Device.
c. Select the device and click “Edit”. If the card is not automatically
detected by SCS, perform steps d through f:
d. Right click on Your Device.
e. Select “Diagnostics & Maintenance”.
f. Click on “Get Cards” in the upper right hand corner.
g. On the Device tab, click on the replacement card and click “Edit”.
h. If the SSC-2 card or its SSMs are disabled, enable them.
i. Click OK.
22 Repeat step 18 through step 21 until all new SSC-2 cards have been
inserted.
23 Resync the GGSN. For detailed procedure, See “Manual GGSN

shutdown, resync, or CMC switchover” on page C-1.

25 Verify that migration mode is no longer active by entering the CLI

command ‘show ssc3 migration status’. If the response to this
command indicates that the migration mode is active, deactivate SSC-3
migration mode by entering the CLI command ‘set ssc3 migration
inactive’.
-END-

Replacing a FELC, GELC or ALC

For line card replacement, the line card may take up to 5 minutes
before it can handle data traffic after card replacement.
Procedure 4-25
Single line card configuration
Step Action

2 Disable the old card.

Device.
e. Disable the card itself.
f. Click OK.
3 Replace the card in the same slot. It will boot up.
4 Enable the old card:

Device.
e. Enable the card itself.
f. Click OK.
411-5221-923 Standard 06.09 August 2008

Procedure 4-25
Single line card configuration
Step Action

-END-
Multiple line card configuration

The procedure is the same as for the single line card except that if the
operator is sure that the line card to be replaced is not handling any
data traffic or the data traffic is shared with other line cards, there is no
need to disable and consequently enable the card for the duration of
the procedure. It is important that the new line card is replaced in the
same slot as the old line card.
Replacing a fan tray

If one or more fans in the fan tray stops functioning, replace the fan
tray using the following procedure.
Procedure 4-26
Replacing a fan tray
Step Action
1 Verify that a new fan tray is on hand before replacing the existing fan tray.
2 If present, remove the alarm cable from the front connector of the fan tray.
3 Use a Phillips screwdriver to unscrew three thumbscrews at the fan tray

door.
4 Open the fan tray door by pulling it down and forward.
5 Use the finger slots on the ends of the fan tray to slide the fan tray forward
to remove it from the chassis (Figure 4-3), and wait until the fans have
stopped spinning.

Caution:
Never operate the chassis for more than five minutes with the fan tray
removed. An extended period without the cooling provided by the fan tray
may result in an automatic system shutdown.
Figure 4-3
Fan tray location
CMC
CMC
SSC Reset
SSC Reset Disk
ALC Disk
ALC
SFC Activity
SFC Activity Signal
ALC Signal Sync
ALC Sync
RDI
SSC Activity
RDI
SSC Activity Signal

SSC Signal Sync
SSC RDI
Sync
RDI
MM Por
t1
MM Por
t1
Activity Eject

PCMCIA
Signal Sync
t1 RDI PCMCIA P
MM Por Sync O
RDI P E
t1 SSM1 us R
O N T
SSM1 us R E 1
N T T
E 1 Speed
Signal Sync
Activity T Link P
RDI Speed
t2 SSM2 us O N T
N 2
T T
Sync SSM3 us T Link
Signal Stat Speed M
MM Por Sync E
Stat t2 E G 1
E
Stat Activity T
Stat T
Stat Activity Signal Sync SSM4 us ed Link
SSM1 us SSM2 us
Spe P
Stat Activity
Stat Sync P O
SSM2 us RDI MM Port 3 Activity M D
R
Activity Stat Activity O
O T
t3 R E
Stat Activity T
C P
SSM3 us M O
Stat
Signal Sync C P R
SSM3 us O N
Stat
MM Por Sync R T
SSM4 us R L
SSM4 us SSM3 L
SSM4 us RDI SSM3
SSM4 us RDI MM Por
Stat Activity Port 4 SSM4 Status Active
SSM1 MM
SSM1 Status Active
SSM1 Status
SSM2 t4 Active
SSM1 MM Por
MM Por
SSM2 Status Active
SSM3
SSM2 Status Active
SSM3
Status Active
SSM3
SSM4 Status Active
SSM3
SSM4 Status Active
Fan Tray
SSM4 Status Active
SSM4 Status Active
Status Active
Active
14
13
12
11
10
9
8
7
6
5
4
3
2
1
Insert a Finger Here

and Pull Forward
10200FA
411-5221-923 Standard 06.09 August 2008

Step Action
6 Insert the new fan tray into the chassis, with the fan tray connector to the
rear.
7 Push the fan tray in until the rear connector seats and the fan tray is flush
with the front of the chassis.
8 Close the fan tray door.
9 Tighten the three thumbscrews.
10 Reattach any alarm cables.
11 Verify that the Fan Status LED is green.
-END-
Returning components to Nortel Networks 4

Procedure 4-27
Returning components to Nortel Networks
Step Action
1 Obtain RMA number and approval to return component from the Nortel
Networks Technical Assistance Center (TAC)
2 Pack and ship in original container to Nortel Networks. Current shipping

address can be found at:
www.nortel.com
-END-

411-5221-923 Standard 06.09 August 2008

A-1
Appendix A: Nortel GGSN

specifications A
This appendix lists the specifications for the SSG of Nortel GGSN.
• “Physical specifications” on page A-1
• “Facility requirements” on page A-2
• “Compliance” on page A-2
Physical specifications
Chassis size and weight
The SSG chassis has the following size and weight:
• Size: 19in. W x 18in. D x 19 1/4in. H
• Weight (empty): 39 lbs (empty, with fan tray) (18 kg)
• Weight (fully loaded with cards): 135 lbs (61 kg)
Power requirements
The Nortel GGSN products have the following power requirements:
• SSG chassis: –38 to –60 VDC @ 48 amperes (approximately
1,850 watts)
• AC Power Shelf: 90-260 VAC, 50-60 Hz, 20 amperes maximum
per system
Temperature requirements
The SSG chassis requires the following environmental parameters:
• Operating temperature: 23° to 131° F (-5° to 55° C)
• Humidity: 10% to 90%, noncondensing

A-2 Appendix A: Nortel GGSN specifications Copyright © 2004–2008 Nortel Networks
Facility requirements
Chassis location
Warning:
The chassis should be installed only in a restricted access area
(dedicated equipment room, equipment closet, or the like) in
accordance with articles 110-16, 110-17, and 110-18 of the
National Electrical Code, ANSI/NFPA 70, or the local authority
having jurisdiction.
Space around chassis

There must be sufficient space around the installation so that no
passersby will contact any of the chassis connectors or controls.
Ensure the chassis air vents are not blocked.
Compliance
The Nortel GGSN is a Class A system and is in full compliance with
the following Safety and EMC standards.
Safety
The Shasta BSN chassis complies with:
• UL 1950, 3rd Edition, Rev. 6/98, Information Technology
Equipment
• CSA C22.2 No. 950-95, 3rd Edition, Rev. 6/98, Information
Technology Equipment
• EN 60950: 1992, A1, A2: 1993, A3: 1995, A4: 1997, A11: 1998
• EN 60825-1: 1994, thru. A11
• EN 60825-2: 1994
• IEC60950: 1992, A1, A2: 1993, A3: 1995, A4: 1996, and per CB
Bulletin 92AI (Feb. 1998)
• CB Certification
EMC
• EN50082-1 (1997)
• EN55022 Class A (1995)
• EN 300 386 V1.3.1 (2001-09) - GGSN to DC power source must be
less than 3m
• VCCI Class A (May 1999),
411-5221-923 Standard 06.09 August 2008

Appendix A: Nortel GGSN specifications A-3
• FCC Part 15 Subpart B Class A

• CISPR 22/85 Class A
• ICES-003 Class A (ANSI C63.4 1992) and AS/NZS 3548 Class A
(1995)
• CNS13438 Class A
Certifications
• NEBS Compliance level III in accordance with Telcordia SR-3580
• CE Declaration (Europe)
• NOM Certification (Mexico)
• IRAM Certification (Argentina)
• ANATEL Certification (Brazil)
• MIC Certification, Type Approval (S. Korea)
• Taiwan Approval, for applicable product

A-4 Appendix A: Nortel GGSN specifications Copyright © 2004–2008 Nortel Networks
411-5221-923 Standard 06.09 August 2008

B-1
Appendix B: Hardware reference B

This appendix contains detailed information about the SSG of Nortel
GGSN hardware components.
• “Chassis” on page B-1
• “Switch Fabric Card (SFC)” on page B-6
• “Control and Management Card (CMC)” on page B-7
• “Subscriber Service Card (SSC)” on page B-12
• “Line cards” on page B-16
• “AC Power Shelf” on page B-24
Chassis
Figure B-1 shows a front view of the chassis.

B-2 Appendix B: Hardware reference Copyright © 2004–2008 Nortel Networks
Figure B-1
SSG chassis, front view
1 2 3 4 5 6 7 8 9 10 11 12 13 14
Alarm Contacts Alarm Cut-off

ESD wrist

strap
connection
Shasta 5000 BSN
chasful1.vsd
Table B-1 shows the front panel controls, connectors, and indicators
for the chassis.
Table B-1
Chassis front controls, connectors, and indicators
Control, connector, or indicator Function

Major Major alarm
Minor Minor alarm
Critical Critical alarm
Alarm Contacts Connector for alarm contact pinouts
Alarm cut-off Push to shut off alarms
Fan status Green: Normal operation
Red: Fan tray fault
411-5221-923 Standard 06.09 August 2008

Caution:
Chassis alarms only indicate fan failure. No other alarm is
displayed on the front of the chassis.
Chassis alarm connector pinout

Table B-2 shows the pins and connections to the chassis front panel
Alarm connector.
Table B-2
Alarm contact connector pinout
Pin group Common Normally open Normally closed

Critical audible 2 1 14
alarm
Major audible 16 3 15
alarm
Minor audible 5 4 17
alarm
Connect only safety extra-low voltage (SELV) circuits to alarm 1 and

alarm 2 connectors. Maximum rating for the alarm circuits is 2
amperes, 50 volt-amps.
Chassis rear view

Figure B-2 shows a rear view of the chassis.

Figure B-2
SSG chassis, rear view
A B
AC Power Shelf –48 –48 –48 –48
GND GND
Status VDC RTN VDC RTN
O OFF I ON
Ground studs
Power on-off
chasback.vsd
circuit breaker
Table B-3 below shows the functions of the chassis rear panel controls
and connectors, while Table B-4 gives the connections to the AC
Power Shelf Status connector.
Table B-3
Chassis rear controls and connectors
Control or connector Function

A, B –48 VDC input to chassis
Power on-off circuit breaker Main chassis power switch; applies power
to chassis
Connector for optional AC Power Connector for cable to optional AC Power
Shelf status Shelf
411-5221-923 Standard 06.09 August 2008

Table B-4
AC Power Shelf Status connector pinout
Pin Signal name Remarks

1 NC No connection.
2 RESET_RTN RESET_RTN pin of all rectifiers connected together.
3 RESET RESET pin of all rectifiers connected together.
4 INHIBIT INHIBIT pin of all rectifiers connected together.
5 INHIBIT_RTN INHIBIT pin of all rectifiers connected together.
6 MARGIN+ MARGIN+ pin of all rectifiers connected together.
7 MARGIN– MARGIN– pin of all rectifiers connected together.
8 HOST_RETURN Reference pin.
9 FAULT FAULT+ (FAULT) pin of all rectifiers connected together.
10 OVERTEMP_WARNING OVERTEMP_WARNING (OTW) pin of all rectifiers
connected together.
11 POWER_FAIL_WARNING POWER_FAIL_WARNING (PFW) pin of all rectifiers
connected together.
12 MISSING_MODULE MISSING_MODULE+ (MM) signal of connected to MM– to
the adjacent one to form a daisy chain. MM+ of the first
one brought out to this pin. The other end connected to
HOST_RETURN.
14 BAT_FAULT/ Indicates that battery reserve energy is not available.
BAT_NOT_AVAILABLE Indicates that the battery string external to the BIU has a
fault and should be serviced as soon as possible.
15 BIU_FAULT/BBU_FAULT Indicates that the BIU has a fault and should be replaced
as soon as possible. Indicates that the BBU has a fault and
should be replaced as soon as possible.
16 BIU_OVERTEMPERATUR Overtemperature.
E
17 BAT_ON_CHARGE1 This signal is de-asserted (negated) when the BBU1 is
providing power to the distribution bus.
18 BAT_ON_CHARGE2 This signal is de-asserted (negated) when the BBU2 is
providing power to the distribution bus.
20 BAT_STATUS1 If the battery is being charged, then this signal indicates
whether the battery has reached the nominal float voltage.
If the battery is being discharged, this signal indicates
whether or not the battery is approaching the low-voltage
disconnect threshold.

Table B-4
AC Power Shelf Status connector pinout (continued)
Pin Signal name Remarks

21 BAT_STATUS2 Same as above for BBU2.
22 BAT_PRESENT1 A strap to alarm return that allows the system to detect an
installed unit
23 BAT_PRESENT2 Same as above for BBU2
24 BAT_DISCONNECT Battery disconnect.
25 BAT_DISCONNECT_RTN Battery disconnect return.
Switch Fabric Card (SFC)

The Switch Fabric Card is always installed in slot 7 or slot 8 of the
chassis. One SFC is required for operation, and a second SFC may be
added for redundancy. The SFC is based on a switching matrix,
providing connectivity between GGSN subscribers and IP networks.
An alphanumeric display provides information about card configuration

and status. LEDs show card status and activity.
The SFC1 or SFC2 includes a daughter module. The type of daughter

module determines allowable system load:
Full load: 10 Gbps system (7.5 Gbps daughter module). Supports

chassis fully populated with 14 cards.
The SFC2 card only comes with a fully loaded 10 Gb/s system,
supporting a full chassis.
Figure B-3 shows an illustration of the Switch Fabric Card, along with
its controls, contacts, and indicators.
411-5221-923 Standard 06.09 August 2008

Figure B-3
Switch Fabric Card (SFC1, SFC2
Control, connector, or
SFC indicator Function
Alpha display ACT: Card is active.

STBY: Card is in standby.
Status Card status LED.
Green: Card is healthy; normal operation.
Red: Card is faulty.
Yellow: Card is not configured by software.
Active Card active LED.
Green: Card is online and active.
Yellow: Card is in standby mode.
Status
Active
10202EA
Control and Management Card (CMC)

The Control and Management Card must be installed in slot 14 or slot
13. One CMC is required for operation, and a second CMC may be
added as a standby CMC for redundancy. If only a single CMC is

provisioned, it is installed in slot 14 and any other type of card (except

an SFC card) may be installed in slot 13.
Attention: To make a CMC card redundant, follow the procedure “Make

a secondary CMC redundant”
The Control and Management Cards are responsible for running

system level processes such as basic system operation and
management, assignment of subscribers to SSMs, IKE and routing
algorithms including OSPF, RIP, IS-IS and BGP. Routing decisions
result in the formation of routing tables which in turn are then used to
populate the FIB Manager tables. The FIB manager is responsible for
distributing reachability information to FIB tables on each of the SSMs.
There are three types of CMC available for the GGSN. Each is
composed of dual processors, memory and Layer 2 cache.
The CMC contains connections for the default management Ethernet

port. Typically, the management Ethernet port should be used only for
network management access (such as access to the various SCS
servers, log servers, Radius servers). The CMC also contains a
console serial port, and a serial modem port. An alphanumeric display
provides information about card configuration and status, while LEDs
show card status and activity. A hard disk mounted on the CMC
contains system configuration files. Image software is stored on
resident Flash (CMC2 Only).
Figure B-4 and Figure B-5 show the CMC3 and CMC2 faceplates,
respectively.
Caution:
Pressing the reset button on the CMC will cause a reboot of the
shelf. This also applies to the redundant CMC.
CMC types
Two generation of the Control and Management Card exist:
• CMC second generation, CMC2 or CMC+ - available with 512 MB
or 1 GB of memory
• CMC third generation, CMC3 - available with 4 GB of memory
The part number for the CMC is on a sticker at the top component side
of the card. Different CMCs, as identified by the part number, have
different memory options. Software release GGSNS4.1.1 or later must
be installed on the GGSN for CMC3 operation.
411-5221-923 Standard 06.09 August 2008

Attention: In a system with redundant CMC cards, both CMC cards

must be of the same version.
Figure B-4
Control/Management Card 3(CMC3)
CMC3
USB Ports
ENET Management Port
Serial Modem Port
Serial Console Port

Figure B-5
Control/Management Card (CMC2)
CMC
Reset
Disk
PCMCIA Port
Eject
PCMCIA
P
E O
N R
E T
T 1
Link Speed Server Ports
P
E O
N R
E T
T 2
Link Speed
E M
N G
E M Management Port
T 1
Link Speed
M
O P
O
D
E R Serial Modem Port
M T
C
O P
N O
T R Serial Console Port
R T
O
L
Status
Active
10203EA
411-5221-923 Standard 06.09 August 2008

Table B-5 below shows the controls, connectors, and indicators on the
CMC.
Table B-5
CMC controls, connectors, and indicators
Control, Function
connector, or
indicator
Reset Resets (reboots) entire system. This applies to the redundant
CMC also.
Eject Ejects card from PCMCIA slot (CMC2 only)
PCMCIA Off: PCMCIA card is not installed in slot.
Green: Normal operation. PCMCIA card is installed and
functional.
(CMC2 Only)
ENET PORT1 Ethernet port 1. Server port. (CMC2 Only)
Link Off: Indicates that the port is not connected.
Green: Indicates normal operation of the port.
Speed Off: Port is connected at 10 Mbps.
Green: Port is connected at 100 Mbps.
ENET PORT2 Ethernet port 2. Server port. (CMC2 Only)
Green: Port is connected at 100 Mbps.
ENET MGMT Ethernet management port. Dedicated for management
purposes.
Green: Port is connected at 100 Mbps
MODEM Performs same functions as CONSOLE PORT, but allows
PORT connection to an external modem.
CONSOLE Controls SSG via serial connection to terminal.
PORT
Alpha display ACT: Card is active.
STBY: Card is in standby.
—sheet 1 of 2—

Table B-5
CMC controls, connectors, and indicators (continued)
Control, Function
connector, or
indicator
Green: Card is healthy; normal operation.
Yellow: Card is in standby mode.
—sheet 2 of 2—
CMC CONSOLE connector pinout

Table B-6 below shows the pins and signals on the CMC’s CONSOLE
connector.
Table B-6
Control/Management Card CONSOLE connector pinout
RJ-45 Pin Function DB-25 Pin Function

1 CTS 4 RTS
2 DSR 20 DTR
3 RXD 2 TX
4 GND 7 GND
5 GND – N/C
6 TXD 3 RXD
7 DTR 6 DSR
8 RTS 5 CTS
Subscriber Service Card (SSC)

The Subscriber Service Card (Figure B-6) is responsible for subscriber
connections and the applications of IP services to each. Regardless of
the placement of the SSC in the chassis, the throughput of the card
will be limited by the OC12 interface to the backplane. The SSC card
processes individual packets and performs subscriber services. It
contains up to four subscriber service modules (SSMs), each with its
own set of status and activity LED indicators.
A GGSN chassis can accommodate up to six active subscriber service

cards. All SSCs are actively load balanced. The SSCs can be placed
411-5221-923 Standard 06.09 August 2008

in slots 1-6 and 9-13, although it is recommended that they not be

placed in slots 5-6, 9-10 since these slots have high bandwidth
interfaces of which the SSCs cannot take advantage. If the chassis
contains only one CMC in slot 14, then slot 13 can be used for an
SSC. A typical chassis contains 2-6 SSCs. The maximum number of
SSCs in a chassis must not exceed 6.
Attention: If you are removing an active SSC, use the SCS to disable
each SSM individually before removing the card from the chassis
SSC types
Subscriber Service Cards are available in two versions:
SSC2 supports 2 GB of memory, divided into 512 MB for each

SSM. In addition, SSC2 improves on the core processing speed of
266 MHz by increasing it to 333.3 MHz.
SSC3 supports 4 GB of memory, and the addition of an optional

IPSec engine daughter card (Security and Encryption Card or
SEC) with full line rate encryption/decryption. The status and
activity of this SEC daughter card is indicated by the SSO Status
and Active LEDs on the SSC3 faceplate.
As of software release GGSN5.0.1, a mix of SSC2 and SSC3

cards is supported in the same chassis only during card upgrade.
Software release GGSN5.0.1 or later must installed on the GGSN
for SSC3 operation.

Figure B-6
Subscriber Service Card 3(SSC3)
Control, connector,
SSC or indicator Function
SSM Status Green: SSM is healthy.

Indicates normal operation.
Red: SSM is faulty.
Yellow: SSM is not
configured by software.
SSM Activity Green: SSM is online and
active.
Yellow: SSM is in standby
mode.
Alpha display DNLD: Card is
downloading microcode
from CMC.
SSM1
XFR: Card is transferring
Status image from CMC.
Subscriber Service Module
Activity
(SSM) 1 Status
UP: Card is up and normal.
SSM2
RST: Card is being reset by
Status CMC.
SSM2 Status
Activity BOOT: Card is not
SSM3
functioning normally.
Status
Activity
SSM3 Status Status Card status LED.
Green: Card is healthy;
SSM4 normal operation.
Status
SSM4 Status Red: Card is faulty.
Activity
Yellow: Card is not
configured by software.
SSM1
Green: Card is online and
SSM2
active.
Yellow: Card is in standby
SSM3 mode.
SSM4
Status
Active
10206EA
411-5221-923 Standard 06.09 August 2008

Figure B-7
Subscriber Service Card (SSC1, SSC2)
SSC
SSM1
Status
Activity
Subscriber Service Module
(SSM) 1 Status
SSM2
Status
Activity
SSM2 Status
SSM3
Status
Activity
SSM3 Status
SSM4
Status
Activity
SSM4 Status
SSM1
SSM2
SSM3
SSM4
Status
Active
10206EA

Line cards
Line cards include ATM line cards (ALCs) and other line cards. Line
cards are available for multimode and single-mode optical fiber, and for
BNC coaxial connections. The types of line cards are as follows:
• OC3 ATM Line Card (OC3 ALC)—available with single-mode or
multimode OC3 optical fiber connection.
• Fast Ethernet Line Card (FELC)—has eight ports of Ethernet
connectivity; each port operates on either 10BASE-T or 100BASE-
T.
• Gigabit Ethernet Line Card (GELC)—provides a single full-
duplex gigabit Ethernet port within the SSG. This card is available
with single-mode or multimode optical fiber connection.
OC3 ATM Line Card (OC3 ALC)

Shown in Figure B-8 the OC3 ALC (Asynchronous Transfer Mode Line
Card) contains ports connected to subscriber service groups, and
provides the actual interface with ISPs and with subscribers.
The OC3 ALC can be installed in any free slot (except slot 7, 8, or 14).
This line card contains a single intelligent card parser (ICP) module:
The ICP is not field-replaceable.
The OC3 ALC is a class 1 laser product.
CLASS 1 LASER PRODUCT
WARNING:
Invisible laser radiation can be emitted from fiber optic
connectors. Avoid direct exposure to the laser beam.
411-5221-923 Standard 06.09 August 2008

Figure B-8
OC3 ATM Line Card (OC3 ALC)
Control, Connector,
ALC
OC3 ATM
or Indicator Function
Activity
Activity Green: Indicates normal operation of the
Signal port.
RDI Sync Flashing Green: Indicates active traffic on
the port.
Red: Card is not configured by software.
Port with OC3
Optical Connector Signal Off: Indicates healthy signal.
MM Port 1 Amber: Indicates Loss of Signal (LOS).
Activity RDI Off: Normal operation. No remote defects
Signal on the port.
RDI Sync Yellow: Indicates a remote defect.
Sync Off: Indicates port is in sync. Normal
Port with OC3 operation.
Optical Connector Yellow: Indicates Loss of Sync. Could
MM Port 2 indicate loss of frame or path.
Activity Port 1 (2, 3, 4) OC3 connector for optical fiber to this port.
Signal
RDI Sync Alpha display UP: Card is active.
OFF: Card is disabled.
Port with OC3 Status Card status LED.
Optical Connector Green: Card is healthy; normal operation.
MM Port 3 Red: Card is faulty.
Activity
Signal Active Card active LED.
RDI Sync Green: Card is online and active.
Port with OC3

Optical Connector
MM Port 4
Status
Active
10207EA

The following tables (Table B-7 and Table B-8) show the specifications
for the OC3 multimode and OC3 single-mode optical power,
respectively.
Table B-7
OC3 multimode optical specifications
Parameter Symbol Min. Typ. Max. Unit

Output (Transmit) Optical Power Po –20 –14
62.5/125υm fiber
Input (Receive) Optical Power PIN Min. (W) –30 dBm avg.
Minimum
Input (Receive) Optical Power PIN Max. –14 dBm avg.
Maximum
Center Wavelength λc 1270 1310 1380 nm
Spectral Width - FWHM Dl 137 nm
- nm RMS 58 nm RMS
Table B-8
OC3 single-mode optical specifications

Output (Transmit) Optical Power Po –15 –8 dBm
10/125υm fiber
Input (Receive) Optical Power PIN Min. (W) –30 dBm avg.
Minimum
Input (Receive) Optical Power PIN Max. –8 dBm avg.
Maximum

Spectral Width - FWHM Dl 7.7 nm
- nm RMS
Fast Ethernet Line Card (FELC)

The Fast Ethernet Line Card contains ports connected to subscriber
service groups, and provides the actual interface with ISPs and with
subscribers. Figure B-9 shows the front panel of the card.
411-5221-923 Standard 06.09 August 2008

The FELC provides eight ports of Ethernet connectivity. Each port

operates at either 10BASE-T or 100BASE-T. Each port is autosensing
to the line rate and connects to the user network via an RJ45 and UTP
cable. The FELC translates the incoming Ethernet frames into ATM
cells, via a layer 2/layer 3 lookup, and steers those frames to the
appropriate SSM. In the outgoing direction, ATM cells are converted
into Ethernet frames with the appropriate MAC header.
The FELC can be installed in any free slot (except slot 7, 8, or 14).
If the FELC is installed in a low speed (622 Mbps) slot, only the first
four ports are activated. For functionality on all eight ports, installation
in a high speed slot (5, 6, 9, or 10) is required.

Figure B-9
Fast Ethernet Line Card (FELC)
Control, connector,
FELC or indicator Function
Link
Speed
Active
Link On: Indicates this port has detected the
Port 1 presence of an active 10 Mb/s or 100 Mb/s
Port 2 link.
Port 3
Port 4
Off: Indicates no link detected.
Port 5
Port 6
Speed On: Link is operating at 100 Mb/s.
Port 7 Off: If active, link is operating at 10 Mb/s.
Port 8
P
Active Blinking on: Indicates this FELC port is
O
R
receiving or transmitting Ethernet frames.
T
1
Off: Indicates no frames are being
received or transmitted by this port.
P
O
R
T
Port 1 (2, 3, 4, 5, RJ-45 connector to this Ethernet port.
2 6, 7, 8)
P
O
R
Alpha display HERE: CMC has detected this card.
T
3
UP: Card is active.
FAIL: Card is disabled.
P
O
R
T
4 10BASE-T or Green: Card is healthy; normal operation.
P 100BASE-T Red: Card is faulty.
O
R Yellow: Card is not configured by software.
T
5
P
O Green: Card is online and active.
R
T
6
P
O
R
T
7
P
O
R
T
8
Status
Active
10212EA
411-5221-923 Standard 06.09 August 2008

Gigabit Ethernet Line Card (GELC)

The Gigabit Ethernet Line Card (GELC) provides a single full-duplex
gigabit Ethernet port within the SSG. Figure B-10 shows the front
panel of the card.
This card is primarily a trunk-side interface and as such, a layer 3+

address resolution facility is provided for the steering of packets to the
correct SSM (Subscriber Service Module) for service-level processing.
Gigabit Interface Converter (GBIC) modules allow for various media
types (e.g. short haul or long haul) to be supported with the same PCB
assembly.
As of software release GGSN4.1.1, the GE card can support up to

256k unique IP addresses.
The GELC must be installed in any free 1.2 Gb slot (5, 6, 9, or 10).
The GELC contains a single search daughter card (SDC) module. This
module is not field-replaceable.

Figure B-10
Gigabit Ethernet Line Card (GELC)
Control, Connector,
GELC or Indicator Function
Link Off: Indicates that the link state is

down.
Green: Indicates that the link state
has successfully negotiated and is
up.
Sync Green: Indicates port is in sync.
Normal operation.
Off: Indicates Loss of Sync. Could
Link indicate loss of frame or path.
Sync
RX TX RX Illuminated to indicate frame
reception.
TX Illuminated to indicate frame
transmission.
Port) Gigabit Ethernet connector for
optical fiber to this port
Alpha display UP: Card is active.
OFF: Card is disabled.
Port with SC Status Card status LED.
Optical Connector Green: Card is healthy; normal
SM Port 2 operation.
Yellow: Card is not configured by
software.
Status
Active
10213EA
411-5221-923 Standard 06.09 August 2008

The following tables (Table B-9 and Table B-10) shows the
specifications for the Gigabit Ethernet Modules.
Table B-9
1000Base-SX port specifications

Output (Transmit) Optical Power Po –9.5 –4 dBm avg.
50/62.5 υm fiber
Input (Receive) Optical Sensitivity PIN Min. (W) –17 dBm avg.
Minimum
Input (Receive) Optical Power Maximum PIN Max. –4 dBm avg.
Distance 50um Fiber 2-220 m
62.5um 2-500 m
Fiber
Table B-10
1000Base-LX port specifications

50/62.5 υm Multi-mode fiber

9 υm Single-mode fiber
Input (Receive) Optical Sensitivity PIN Min. (W) –20 dBm avg.
Minimum
Input (Receive) Optical Power Maximum PIN Max. –3 dBm avg.
Distance 50um Fiber 2-550 m
62.5um 2-550 m
Fiber
2-10 Km
9um Fiber

AC Power Shelf
The AC Power Shelf converts AC line current to a –48 VDC source for
powering the chassis. The AC Power Shelf contains four power
modules. Each power module is an independent “hot-swappable” unit.
Each module supplies the necessary voltages for powering the
chassis.
In a fully-loaded chassis, even if one power module fails, the others

supply sufficient power for the chassis. You can remove and replace
failed power module without interrupting system operation.
Figure B-11 shows a front view of the AC Power Shelf and its
indicators. Figure B-12 shows the rear view.
Figure B-11
AC Power Shelf and indicator front view detail
PWR OK PWR OK PWR OK PWR OK

FAULT FAULT FAULT FAULT
CB2
TEMP TEMP TEMP TEMP

AC
POWER 1LIM 1LIM 1LIM 1LIM
1 2
CB1
PWR OK
FAULT
CB2
TEMP
AC
POWER 1LIM
1 2
CB1
10214EA
411-5221-923 Standard 06.09 August 2008

Table B-11 explains the indicators and switches on each power

module, while Table B-12 explains the controls, connectors, and
indicators on the AC Power Shelf front panel.
Table B-11
Power module indicators and switches

PWR OK Power OK (green): The unit is powered up
and operating normally.
FAULT Off: Indicates normal operation.
Fault (yellow): The unit has detected an
internal fault.
TEMP Off: Indicates normal operation.
Overtemperature (yellow): The unit has
shut down due to overtemperature
condition.
I LIM Off: Indicates normal operation.
Current Limit (yellow): The unit is
overloaded and operating in current limit.
Table B-12
AC Power Shelf front controls, connectors, and indicators

Switch Module - AC Power 1,2 Green: Switch is turned on and normal.
Figure B-12
AC Power Shelf rear view detail
AC Power
Cords
10215EA

411-5221-923 Standard 06.09 August 2008

C-1
Appendix C: Product maintenance

procedures C
This appendix contains procedures that need to be executed during the
product maintenance of Nortel GGSN:
• “Manual GGSN shutdown, resync, or CMC switchover” on page C-
1
• “Move G-CDR files from standby CMC” on page C-4
• “CMC Upgrade/Downgrade Preparation” on page C-6
• “Boot CMC card from network” on page C-12
• “CMC bootrom upgrade” on page C-14
• “SSM bootrom upgrade” on page C-19
• “Update SSC3 XFPGA firmware” on page C-27
• “CMC2 Server Port Migration” on page C-33
Manual GGSN shutdown, resync, or CMC switchover

In order to reduce to a minimum the number and amount of
unprocessed billing information lost when a scheduled GGSN
shutdown, resync, or CMC card switchover is performed, certain steps
must be performed on the GGSN using the CLI commands described
below. It is recommended that a manual GGSN shutdown, resync, or
CMC card switchover is performed during low traffic volume (Off Peak
Hours).
The length of time needed to perform these steps depends upon the
traffic volume and number of active subscribers on the Nortel GGSN.

C-2 Appendix C: Product maintenance procedures Copyright © 2004–2008 Nortel Networks
Procedure C-1
Manual GGSN shutdown or CMC switchover
Step Action

d. Select or Add the device and click “Edit”.
2 Close all existing active PDP sessions. On the SCS GUI, on the GTP
tunnel tab, click the initiate button next to “Terminate Existing PDP
Contexts” on the GTP Tunnel Device Configuration window. Wait until the
GGSN has confirmed that all sessions have been closed. Monitor the
value of the variable “SM.NbrActPdpCtxt” which indicates the number of
active PDP Contexts.
<># show stats hist sm <Gn ispname>
3 If you are using GTP Accounting proceed to step 4, if not, proceed to step
14.
4 Stop transferring any G-CDRs from disk to the CGF.

<># gtpbill disksend off
5 Perform a flush of all the currently active PDP sessions.

<># gtpbill flush billing <ispname>
6 Check the result of ‘show gtpbill <ispname>’. The previous operation is

not complete until the following parameters have a value of zero: “Ext
Blks on Reg Unproc Lst”, “Ext Blks on Hot Unproc Lst”, “POS_DUP_PKTs
in Q” and “Num Pkts Wait Act Q” for each utilized CGF.
a. Wait and repeat the ‘show gtpbill <ispname>’ command if
necessary.
b. After a period of time, if all of the above parameters have a value of
zero, proceed to step 12. Otherwise, proceed to the next step.
411-5221-923 Standard 06.09 August 2008

Procedure C-1
Manual GGSN shutdown or CMC switchover (continued)
Step Action
7 Offline all CGFs that are provisioned for each ISP using GTP Billing by
repeating the command if necessary. Offlining the CGFs will cause the
remaining billing records to be written to the local disk.
<># gtpbill cgf offline <ispname> <cgf 0_or_1>
8 Turn off the RAM Ext Buffer by setting the size to zero (0).
<># gtpbill modrambuff 0
9 Allow the unprocessed Extension Block lists to be processed. Use 'show

gtpbill <ispname>', on the output displayed there is a “RAM Buffer”
section and a line called “Currently”. This line shows the number of blocks
currently in the buffer waiting to be processed.
10 Ensure that the all provisioned CGFs, have entered the OFFLINE state
(Use 'show gtpbill <ispname>') for each GTP ISP using GTP Billing.
11 As soon as step 8 and step 9 have been performed, flush the contents of
the CDR RAM file buffer to disk. This is done by changing the CDR file
size limit. On the SCS GUI, for the ISP using GTP billing:
a. Find the selected CGF Profile. Then, on the CGF Profile General
page, record the configured value for the CDR file size limit. This will
be used to restore the original configuration after making a small
change.
b. Change the value of the CDR file size limit by two bytes and apply the
change (i.e. click OK). This will cause the CDR RAM file buffer to be
flushed to the local disk.
c. Check the result of ‘show gtpbill <ispname>’. The previous
operation is not complete until the following parameters have a value
of zero: “Ext Blks on Reg Unproc Lst”, “Ext Blks on Hot Unproc Lst”,
“POS_DUP_PKTs in Q” and “Num Pkts Wait Act Q” for each utilized
CGF.
d. Wait and repeat the ‘show gtpbill <ispname>’ command if
necessary. This takes time since it is writing the CDR to the local disk.
e. Change the CDR file size limit back to its original configuration.
12 If auditing is currently enabled, it will need to be shut down in order to

flush the remaining audit entries to a file.
<># gtpbill audit <ispname> disable
13 If there is currently a FTP audit transfer session in progress the session

will be lost when the Nortel GGSN is rebooted or shut down. The file
being transferred will remain on the Nortel GGSN.
14 If you are using RADIUS Accounting proceed to step 15, if not, proceed to
step 16.

Procedure C-1
Manual GGSN shutdown or CMC switchover (continued)
Step Action
15 Send all RADIUS Accounting records stored on disk to the RADIUS

server. Use the following CLI command on RADIUS profiles that have
accounting enabled. The command should only be executed on one
RADIUS accounting profile at a time and should not be repeated until the
previous profile’s transfer is complete.
<># radacct disksend <Connection ispid> <Radius Profile name>
start
To check the status of the RADIUS accounting transfer for a RADIUS

profile:
<># radacct disksend <Connection ispid> <Radius Profile name>
After the RADIUS accounting transfer for a RADIUS profile is complete,

the following status is displayed:
Last status:< All records have been sent>
16 Shutdown the GGSN or switchover the CMC card.
17 After CMC switchover or reboot, go back and uncheck the “Disallow PDP
Context Creation” checkbox on the GTP Tunnel Device Configuration
window.
-END-
Move G-CDR files from standby CMC

In the event of a CMC card switchover, it may be necessary to
manually transfer any unprocessed G-CDR files from the standby
CMC card to the active CMC card. This is accomplished by the
following procedure.
411-5221-923 Standard 06.09 August 2008

Procedure C-2
Moving G-CDR files from standby CMC
Step Action
1 On the standby CMC card, perform the following CLI command:

cd /disk/acct/gtp/cdrs
dir
Note any files ending in the letter 'U'. For example,
ssg(standby-cmc)(SSU)# dir
size date time name
---------- ------ ----- --------
512 12-Apr-2003 04:02:20 <DIR>
512 12-Apr-2003 04:02:20 <DIR>
0 02-Jul-2003 10:03:20 CHGSEQNO
1023970 22-May-2003 05:39:12 2250539A.05U
1023970 22-May-2003 05:44:18 2250544A.05U
1023970 22-May-2003 05:51:28 2250551A.05U
2 On the active CMC card, for each of the files ending in the letter “U” in
step 1, perform the following CLI command:
copy file standby-cmc:/disk/acct/gtp/cdrs/<filename> /disk/
acct/gtp/cdrs/<filename>
For example,
ssg (SSU)# copy file standby-cmc:/disk/acct/gtp/cdrs/
2250539A.05U /disk/acct/gtp/cdrs/2250539A.05U
Attention: Note any files that were not successfully copied from the
standby CMC card.
On the standby CMC, perform the following CLI commands:

cd /disk/acct/gtp/cdrs
dir
For each file that was successfully copied to the active CMC in step
above, remove it from the standby CMC:
remove file /disk/acct/gtp/cdrs/<file_name>

Procedure C-2
Moving G-CDR files from standby CMC (continued)
Step Action
3 On the standby CMC card, perform the following CLI command:

cd /disk/acct/gtp/audit
dir
Note any files ending in the letter 'F'. For example,
shasta-57(SSU)# dir
size date time attr name
---------- ------ ----- ----- ---
512 24-Aug-2004 18:01:12 rw . <DIR>
512 22-Jun-2070 12:24:16 rw .. <DIR>
2636 13-Aug-2004 16:14:50 rw 1381514A.03F
1023998 13-Aug-2004 16:52:32 rw 1381624A.03F
1024015 13-Aug-2004 16:54:06 rw 1381652A.03F
1024015 13-Aug-2004 16:55:40 rw 1381654A.03F
4 On the active CMC card, for each of the files ending in the letter “F” in
step 1, perform the following CLI command:
copy file standby-cmc:/disk/acct/gtp/audit/<filename> /disk/
acct/gtp/audit/<filename>
For example,
ssg (SSU)# copy file standby-cmc:/disk/acct/gtp/audit/
1381514A.03F /disk/acct/gtp/audit/1381514A.03F
Note any files that were not successfully copied from the standby CMC
card.
On the standby CMC, perform the following CLI commands:
cd /disk/acct/gtp/audit
dir
For each file that was successfully copied to the active CMC in step
above, remove it from the standby CMC:
remove file /disk/acct/gtp/audit/<file_name>
-END-
CMC Upgrade/Downgrade Preparation

In preparation for a CMC upgrade or downgrade procedure, all billing,
accounting, and/or auditing records should be sent from both the
active and standby CMCs to their appropriate collection servers in
411-5221-923 Standard 06.09 August 2008

order to ensure that no such information is lost. Note that these

procedures must only be performed during a Maintenance Window.
Procedure C-3
CMC upgrade/downgrade preparation
Step Action
1 On the active CMC, issue the following commands to enable log

monitoring and disable the telnet idle time-out.
monitor log
set terminal port=telnet idle=0

3 All active PDP contexts should be closed before card replacement. The
operator can either wait until all PDP contexts are closed or use the
following procedure to manually close all active PDP contexts:
• Log in Gn ISP through SCS Client.
• Select Access Properties -> Tunnels -> GTP.
• Select the GTP tunnel and click “Edit”.
• Select the device and click “Edit”.
• Click “Initiate” for “Terminate Existing PDP Contexts” to take down all
existing PDP Context on GGSN.
• Monitor the value of the variable “SM.NbrActPdpCtxt” which indicates
the number of active PDP contexts by using the following command:
show stats hist sm <Gn ispname>
When this value is zero, all PDP contexts are closed.
Attention: Do not continue until all PDP contexts are closed.
4 If you are using GTP accounting, proceed to step 5, if not, proceed to step
11.

Procedure C-3
CMC upgrade/downgrade preparation (continued)
Step Action
5 If you are using a CGF server, proceed to step 6, if not, proceed to step 7.
6 Ensure all GTP accounting information on the active CMC is transferred

to the CGF server.
a. Allow transferring billing records from disk to the CGF. Use the CLI
command
gtpbill disksend allow
b. Turn off the RAM ext buffer by setting the size to zero (0).
gtpbill modrambuff 0
c. Ensure the RAM buffer is flushed to disk.
gtpbill modramdisk <ispname> 102400
d. Monitor the progress of the billing record transfer by using the ‘show
gtpbill <ispname>’ command. The operation is not complete until
the following parameters have a value of zero for each utilized CGF
and the listing of Closed Unsent CDR files is empty.
— Currently (ext blocks in buffer)
— Ext Blks on Reg Unproc Lst
— Ext Blks on Hot Unproc Lst
— Num CDRs in RAM file
— POS_DUP_PKTS in Q
— Num Pkts Wait Ack Q
Attention: Do not continue until all billing records have been transferred.
e. Copy the CHGSEQNO file in the cdrs subdirectory to the standby

CMC by issuing the following command:
7 If you are using “FTP pull” accounting, proceed to step 8 if not, proceed to
step 9.
8 Transfer any GTP accounting files from the GGSN to the downstream
FTP server.
9 If you are using gtpbill auditing, proceed to step 10, if not, proceed to step
11.
411-5221-923 Standard 06.09 August 2008

Procedure C-3
Step Action
10 Ensure all gtpbill audit information on the active CMC is transferred.

a. Start the FTP audit transfer by issuing the following command:
gtpbill ftp start isp=<ispname>
A log will be generated indicating the FTP audit transfer has started.
b. The progress of the audit file transfer can be monitored by listing the
files in the /disk/acct/gtp/audit directory:
dir /disk/acct/gtp/audit
The operation is not complete until the above directory is empty. A log will
be generated indicating completion of the audit file transfer.
Attention: Do not continue until all audit files have been transferred.
11 If you are using RADIUS accounting, proceed to step 12, if not, proceed
to step 13.

radacct disksend <Connection ispid> <Radius Profile name>
start
profile:
Last status:<All records have been sent>
Attention: Do not continue until all RADIUS accounting records have

been transferred.
13 Perform a switchover between the active CMC and the standby CMC.
switch cmc
If the switchover was successful, the previous standby CMC is now the
active CMC.

Procedure C-3
Step Action
14 On the newly active CMC, issue the following commands to enable log
monitoring and disable the telnet idle time-out.
monitor log
set terminal port=telnet idle=0
15 If you are using GTP accounting, proceed to step 16, if not, proceed to
step 22.
16 If you are using a CGF server, proceed to step 17, if not, proceed to step
18.
17 Ensure all GTP accounting information on the newly active CMC (i.e. the
old standby CMC) is transferred to the CGF server.
a. Allow transferring billing records from disk to the CGF. Use the CLI
command
gtpbill disksend allow
b. Ensure the RAM file is flushed to disk.
gtpbill modramdisk <ispname> 102400
c. Turn off the RAM ext buffer by setting the size to zero (0).
gtpbill modrambuff 0
d. Monitor the progress of the billing record transfer by using the ‘show
gtpbill <ispname>’ command. The operation is not complete until the
following parameters have a value of zero for each utilized CGF and
the listing of Closed Unsent CDR files is empty.
— Currently (ext blocks in buffer)
— Ext Blks on Reg Unproc Lst
— Ext Blks on Hot Unproc Lst
— POS_DUP_PKTS in Q
— Num Pkts Wait Ack Q
Attention: Do not continue until all billing records have been transferred.
18 If you are using “FTP pull” accounting, proceed to step 19, if not, proceed
to step 20.
19 Transfer any GTP accounting files from the GGSN to the downstream
FTP server.
20 If you are using gtpbill auditing, proceed to step 21, if not, proceed to step
22.
411-5221-923 Standard 06.09 August 2008

Procedure C-3
Step Action
21 Ensure all gtpbill audit information on the newly active CMC (i.e. the old
standby CMC) is transferred.
a. Start the FTP audit transfer by issuing the following command:
gtpbill ftp start isp=<ispname>
A log will be generated indicating the FTP audit transfer has started.
b. The progress of the audit file transfer can be monitored by listing the
files in the /disk/acct/gtp/audit directory:
dir /disk/acct/gtp/audit
The operation is not complete until this directory is empty. A log will be
generated indicating completion of the audit file transfer.
Attention: Do not continue until all audit files have been transferred.
22 If you are using RADIUS accounting, proceed to step 23, if not, then you
are finished with this procedure.

start
profile:
Last status:<All records have been sent>
Attention: This procedure is not complete until all RADIUS accounting

records have been transferred.
24 Unapply the GGSN6.0 patching profile to the device. Refer to the

“Clearing a patch profile” section in “Appendix B: GGSN patch
application” in Nortel GGSN Provisioning Procedures (411-5221-927).
25 Return to the procedure that referred you here or “Downgrade CMC3 to

CMC2” on page 4-70.
-END-

Boot CMC card from network

If a CMC card does not bootup when inserted in the chassis, a
bootable load may not be setup on disk properly. If the bootorder is not
set properly, on bootup from the console the user may hit ‘<space>q’
when prompted in order to change the bootorder using the ‘setbp’
command. ‘lg’ causes the card to boot using the new boot information.
If the load on disk has been corrupted, the card may have to be booted
from the network. The CMC can be booted from a network using tftp or
ftp server.
Boot a CMC card using tftp

The following is a procedure to boot a CMC card using tftp:
Procedure C-4
Boot a CMC card
Step Action
1 Setup a TFTPBOOT server. Create a dir on the TFTPBOOT server

named /tftpboot/dir1/dir2 where the uncompressed load files will reside.
Note: dir1 and dir2 can be any name the user wishes.
2 Make sure the CMC card to be reloaded is not the Standby CMC. A
Standby CMC card cannot be booted from the network. Login to the
console of the CMC card.
3 If possible, login with Super Super User privileges and issue the ‘reboot’
command. Otherwise, do a hardware reset of the CMC card.
4 When prompted at the console, hit ‘<space>q’ within the three second
window in order to change the boot information.
411-5221-923 Standard 06.09 August 2008

Procedure C-4
Boot a CMC card
Step Action
5 Enter the command ‘setbp’.

a. Set the “flags” parameter to 0x80.
b. If the CMC card is a CMC2 card, Enter the “boot file1” parameter: “/
dir1/dir2/cmc”. dir1 and dir2 are the same names used in step 1).
c. If the CMC card is a CMC3 card, Enter the “boot file1” parameter: “/
dir1/dir2/cmc3”. dir1 and dir2 are the same names used in step 1).
d. Enter a text name for the “boot server name”.
e. Enter a text name for the “BSN name”.
f. Enter the management IP address and netmask length for the “BSN
address” in the format <ip addr>/<netmask length in bits>.
g. Enter the “boot server address”. This is the IP address of the
TFTPBOOT server.
h. Enter the Default Router IP address.
i. Use the default parameter values for all other parameters.
6 After finishing entering parameter values, issue the ‘lg’ command to

cause the CMC card to do a tftpboot.
7 After the CMC card is booted, ftp the load to the local disk and set the
bootorder entries appropriately.
8 Issue the ‘set quickstart’ command and configure the SCS server
address.
9 Reboot the CMC card to ensure that it boots from disk properly.
-END-

CMC bootrom upgrade

Procedure C-5
CMC bootrom upgrade
Step Action
1 Get CMC slot information. Use the following command to get CMC slot
information:
show card
For example:

U - up; X - failed; '-' - disabled; * - not present
---- ----------------------- -------- -----
5 ALC /ALC Enabled U D D D [ICP Rev. 1.6]
7 SFC /SFC Enabled 10G Active [FPGA Rev. 2.0]
8 SFC /SFC Enabled 10G Standby [FPGA Rev. 2.0]
9 GELC /GELC Enabled U [FPGA Rev. 0.5] [GBIC Multi]
13 CMC /CMC Enabled Standby (Redundant)
411-5221-923 Standard 06.09 August 2008

Procedure C-5
CMC bootrom upgrade
Step Action
2 Verify the bootrom version for each CMC card. Use the following
command to check the bootrom version on CMC:
show mfg slot=<slot #> mode=detail
For example:
shasta-19(SSU)# show mfg slot=13 mode=detail

Slot Type Serial Number Version Date
---- ---- ------------- ------- ----
13 CMC 26A000797 7.9 0105
Boot ROM Revision: 8.0(1)
Verify if “Boot ROM Revision” is the supported bootrom version for current
release. For GGSN5.0, the CMC2 should use Boot ROM Revision 8.0(1)
or later and the CMC3 should use 2.2(1) or later. If bootrom firmware
version is correct, the bootrom firmware does not require an update. Both
CMC cards should have the same version of bootrom.
3 Obtain the required CMC bootrom files from a remote server and place
them in the directory /disk/bootrom on the GGSN. If the directory “/disk/
bootrom” doesn't exist, create it by typing the command “mkdir /disk/
bootrom”. Obtain the required CMC bootrom files from a remote server
and place them in the directory /disk/bootrom on the GGSN.
CMC bootrom files may also be downloaded from www.nortel.com -->
“Products & Services” --> “Products” --> “Family” --> “SHASTA” --> “See
the products in this family” --> “Downloads”. Find the required CMC
bootrom files, download them in the directory /disk/bootrom on the
GGSN.

Procedure C-5
CMC bootrom upgrade
Step Action
4 Each CMC has a primary and secondary bootrom bank. This provides
bootrom redundancy. The primary bootrom is “bootrom=0”. The
secondary bootrom is “bootrom=1”. The CMC cards ship from the factory
with a valid bootrom in the primary bank. All subsequent updates by
default go to the secondary bank. During the boot process, the processor
always begins executing from the primary bank but immediately checks to
see if the secondary bank is valid. If so, the bootrom image in the
secondary bank is executed. If the image in the bootrom secondary bank
is not valid, the image in the bootrom primary bank is loaded and
executed. The user can tell if the primary or secondary bootrom bank
image has been used by:
a. Logging into the console and rebooting the CMC.
b. One of the following messages is displayed soon after the reboot:
— CMC Booting from: Primary ROM
— CMC Booting from: Secondary ROM
411-5221-923 Standard 06.09 August 2008

Procedure C-5
CMC bootrom upgrade
Step Action
5 For each CMC, update the bootrom. Both CMC card should be updated to
the same version of bootrom. Otherwise, there will be a problem on the
CMC switch-over. If the user updates the primary bootrom with a file
which is corrupt, the CMC will become unbootable. If this happens,
contact Nortel Networks personnel.
a. For each CMC2 card which has bootrom revision 5.0.2 or earlier:
For this bootrom revision, the “bootrom=” parameter must be used to:
— Update the Secondary bootrom.
— Test that Secondary bootrom has been updated correctly.
Update Primary bootrom using same file as was successfully used in
updating the Secondary bootrom.
update bootrom cmc slot=<slot #> bootrom=1 file=/disk/image/

bootrom5.0/cr_8_0_1.bin
Verify that the secondary bootrom has been updated correctly by doing a
resync on the GGSN. From the console of each CMC, check that the
following message is displayed soon after the reboot:
CMC Booting from: Secondary ROM
If instead the CMC booted from the Primary ROM, the bootrom image
used in the previous step may be corrupt. If this happened, re-transfer the
bootrom files from the server and repeat the previous step. If the CMC
booted using the Secondary ROM, then update the Primary ROM:
update bootrom cmc slot=<slot #> bootrom=0 file=/disk/image/

b. For CMC2 bootrom revision 6.0.1 or later:
It is recommended that the “bootrom=” parameter not be used when
updating the CMC2’s bootrom from revision 6.0.1 or later unless
instructed to do so by Nortel Networks personnel. By default, the
secondary bootrom (i.e. bootrom=1) is updated.
update bootrom cmc slot=<slot #> file=/disk/image/

It is recommended that the “bootrom=” parameter not be used when

updating the CMC3’s bootrom unless instructed to do so by Nortel
Networks personnel. By default, the secondary bootrom (i.e.
bootrom=1) is updated.
update bootrom cmc3 slot=<slot #> file=/disk/image/

bootrom5.0/c3_2_2_1.bin

Procedure C-5
CMC bootrom upgrade
Step Action
6 Resync the GGSN so the bootrom change takes effect. A resync is

required before loading the GGSN software load. From the console of
each CMC, check that the following message is displayed soon after the
reboot:
CMC Booting from: Secondary ROM
If instead the CMC booted from the primary ROM, the bootrom image
used in the previous step may be corrupt. If this happened, re-transfer the
bootrom files from the server and return to the previous step.
7 Verify the CMC bootrom upgraded successfully. Use the following

command to check the bootrom version on each CMC:
show mfg slot=<slot #> mode=detail
Each CMC2 “Boot ROM Revision” should be equal to 8.0(1) or later. Each
CMC3 “Boot ROM Revision” should be equal to 2.2(1) or later. Both CMC
cards should have the same version of CMC bootrom.
-END-
411-5221-923 Standard 06.09 August 2008

SSM bootrom upgrade

The SSM bootrom upgrade process is service impacting due to SSC
card needs to reboot for the new version of bootrom running.
Procedure C-6
SSM bootrom upgrade
Step Action
1 Identify the slots which the SSC cards occupy. Verify all SSMs are up in
the GGSN. Enter the command ‘show card’ to accomplish this. Each port
for the SSC card will show as ‘U’ for up and the card will be marked as
enabled.
# show card
SSM/CT3 CPU states: A - auto-reset; N - need catchup;
present
loading
ELC/GELC port states: U - up; D - down (link fail)
CT3 port states: + - up; '-' - down (alarm)

---- ----------------- ------- -----
5 ALC /ALC Enabled U U D D [ICP
Rev. 1.6]
6 ALC /ALC Enabled U U D D [ICP
Rev. 1.6]
Rev. 2.0]
10 ELC /ELC Enabled U U U U D D D D

Procedure C-6
SSM bootrom upgrade
Step Action
2 For SSMs that are not up and are known to have hardware issues other
than bootrom, please disable the SSMs prior to upgrade and send the
card back for repair and return. Otherwise, try and bring up the SSM via
the SCS GUI. If any SSM or SSC cannot be brought up, use the RMA
process for repair and return. The process will ask for the exact failure
message and the serial number of the SSC. The serial number can be
found using the ‘show mfg slot=x’ command. The parameter ‘x’ is the
slot where the SSC resides. Afterwards, delete the card from the SCS
and remove the card from the GGSN hostname. If there is a spare SSC,
replace the bad SSC with a spare SSC with the same encryption level.
# show mfg slot=1

Slot Type Serial Number Version Date
---- ---- ------------- ------- ----
1 SSC SCI02002J 3.0 0117
411-5221-923 Standard 06.09 August 2008

Procedure C-6
SSM bootrom upgrade
Step Action
3 For each SSC card listed from the ‘show card’ command in step 1
perform a ‘show card slot=xx detail’. The parameter ‘xx’ is the slot
number of the SSC. This will display the Bootrom version for each SSM
on the line “ROM version:”. If the version is already at the updated version
there is no reason to upgrade that SSM.
Each SSC2 “ROM version” should be equal to 6.0(1) or later. Each SSC3
“ROM version” should be equal to 1.5(1) or later. All SSC cards should
have the same version of bootrom
# show card slot=1 detail

SSM/CT3 CPU states: A - auto-reset; N - need catchup;
present
loading
ELC/GELC port states: U - up; D - down (link fail)
CT3 port states: + - up; '-' - down (alarm)

---- ----------------- ------- -----
SSC state: running
EPIF state: running
SSM 1 state: running
CPU: IBM PPC740/750 (0x88302) Bus Speed: 83MHz
Memory: 512M Encrypt: No Limit
ROM version: 6.0(1)
Enet chip: Shasta DV (0x547ffff), rev: 0x2000303
ROM version: 6.0(1)
ROM version: 6.0(1)
ROM version: 6.0(1)

Procedure C-6
SSM bootrom upgrade
Step Action
4 Before the bootrom is updated, the PDP session creation must be

disabled for the duration of the upgrade (if it has not been done yet) as
follows:
a. Login to the Gn ISP through SCS Client.
Request from SGSN.
5 From the ‘show card’ command in step 1 start at the first SSC card and
issue the command ‘update bootrom’, for each SSM in the SSC card
that needs to be updated. In the command ‘update bootrom ssm slot =
xx module = yy file=/disk/<directory path>/<bootrom binary>’, the
parameters ‘xx’ is the slot number of the SSC card, ‘yy’ is the module
number (1 to 4), ‘directory path’ parameter is the directory where the
bootrom file exists, ‘bootrom binary’ is the bootrom file. All SSMs on all
SSCs should be updated to the same version of bootrom.
# update bootrom ssm slot=1 module=1 file=/disk/bootrom/

SR6_0_1.BIN
Confirm [y/n]: y
This Firmware will make boot non-redundant
Confirm [y/n]: y
Flashing SSM with version 6.0(1), built Wed Jul 24 09:40:48
2004
Updating SSM slot 1 module 1 boot ROM. Please wait...
SSM slot 1 module 1 boot ROM successfully upgraded
6 To upgrade an SSC3 bootrom, the entire card is upgraded by one

command rather than a command for each SSM. The command is:
update bootrom ssc3 slot=<slot> file=</disk/image/yourImage/

s3_1_5_1.bin>
411-5221-923 Standard 06.09 August 2008

Procedure C-6
SSM bootrom upgrade
Step Action
7 If an SSM fails to upgrade, disable, remove and delete the SSC from the
SCS GUI, and have the SSC card sent back for repair and return as
indicated in step 2. If there is a spare SSC card present with the same
encryption level of the bad SSC, replace the bad SSC card and re-
execute starting at step 2.
8 After all SSMs for the SSC have been upgraded, it will be necessary to
reset the SSC card for the new firmware to take effect. In order to disable
the card, the following steps must be performed.
a. Login Device Owner or any ISP through SCS Client.
b. Select the device via Devices -> Regions -> (Your Region) - > Your
Device.
e. Disable the SSC card.
f. Click OK.
9 After disabling the card, verify that the card is disabled via the CLI by
entering the ‘show card slot=<xx>’ command where the parameter ‘xx’
is the SSC card to view the status. The card will be marked Disabled, and
an ‘*’ will appear for each SSM.
# show card slot=1

- not present
L - loading

---- ----------------------- -------- -----
1 SSC /SSC Disabled * * * *

Procedure C-6
SSM bootrom upgrade
Step Action
10 After the SSC card has been disabled, as seen by the appearance of
console logs for each SSM on the SSC thus:
21-Nov-2003 19:52:36 13/1/1:sspmgr,0: 13, 1, INFO, SSM 2 in

slot 1 removal processing done
The card can now be enabled. After enabling the card, verify that the card
has been enabled via the CLI, enter the ‘show card’ command as
indicated above. The card will appear as enabled, and all SSMs will show
‘U’. Wait for all SSMs to return to service before proceeding the next step
(this may take a few minutes). The steps to enable a card via the SCS
GUI are listed below:
a. Login any ISP or Device_Owner through SCS Client.
b. Select the device via Devices -> Regions -> (Your Region) - > Your
Device.
d. On the Device tab, click on the Card to be replaced and click “Edit”.
e. Enable the Card.
f. Click OK.
# show card slot=1
* - not present
v - uncommunicative; d - dumping
core; L - loading

---- ----------------------- -------- -----
1 SSC /SSC Enabled L L L L
# show card slot=1

* - not present
v - uncommunicative; d - dumping
core; L - loading
411-5221-923 Standard 06.09 August 2008

Procedure C-6
SSM bootrom upgrade
Step Action


---- ----------------------- -------- -----
11 If SSC fails to reset, disable and delete the SSC from the SCS, and have
the SSC card sent back for repair and return as indicated in step 2. There
is no rollback procedure for bootrom update failures at this time.

Procedure C-6
SSM bootrom upgrade
Step Action
12 Enter the command ‘show card slot=<xx> detail’ to display the new
bootrom for each SSC individually.
shasta-124(SSU)# show card slot=1 mode=detail

- not present
L - loading

---- ----------------------- -------- -----
SSC state: running
EPIF state: running
ROM version: 6.1(2)

ROM version: 6.1(2)

ROM version: 6.1(2)
ROM version: 6.1(2)
Enet chip: Shasta DV (0x547ffff), rev:
0x2000303
13 Repeat steps step 5 through step 12 for each SSC that requires firmware
upgrade.
411-5221-923 Standard 06.09 August 2008

Procedure C-6
SSM bootrom upgrade
Step Action
14 For SSC3 cards only: An XFPGA firmware version update may be

required. After bootrom version upgrade has been performed on all SSC3
cards, please proceed to upgrade the SSC3 XFPGA firmware version.
See “Update SSC3 XFPGA firmware” on page C-27. This step is not
applicable for GGSN’s with SSC2 cards.
15 Enable PDP session creation on the GGSN

a. Login to the Gn ISP through SCS Client.
e. Select Device under GTP Tunnel and deselect “Disallow PDP Context
-END-
Update SSC3 XFPGA firmware

If the GGSN has SSC3 cards, a SSC3 XFPGA firmware update may
be required.
Attention: Make sure SSC3 firmware version verification and upgrade has been completed on
all SSC3 cards. See “SSM bootrom upgrade” on page C-19 for details.
Procedure C-7
Step Action
1 Telnet/ ssh to the GGSN with a username with SSU (Super Super User)
privilege.

Procedure C-7
Step Action
2 Make a note of the number of SSC3 cards on the GGSN and the slot
number:
ggsn(SSU)# show card
Here is an example. SSC3 cards are placed in slot 1, 3 and 11:

Thu 25-Jan-2007 07:02:07 CST
U - up; X - failed; '-' - disabled; * - not present
M - failover move in progress;
T - temporarily down
~ - spared overflow pool; ^ - spared failover pool

---- ---------------- ------- -----
1 SSC3 /SSC3 Enabled U U U U
5 ALC /ALC Enabled U U U U [ICP Rev. 1.7]
7 SFC2 /SFC2 Enabled 10G Active [FPGA Rev. 2.0/30.5]
8 SFC2 /SFC2 Enabled 10G Standby [FPGA Rev. 2.0/30.5]
9 GELC /GELC Enabled U [FPGA Rev. 0.5] [GBICMulti]
10 ELC /ELC Enabled U U D U U U D U
14 CMC3 /CMC3 Enabled Standby (Redundant)
3 Make a note of the current SSC3 XFPGA firmware version using the
following command
ggsn(SSU)# show card slot=<SSC3 slot> mode=detail
The version will appear as:

GGI GMII Bridge A version: <version number>
GGI GMII Bridge B version: <version number>
4 The supported SSC3 XFPGA firmware version for GGSN 5.0.x is ‘12’.
• If the user was directed to this procedure from a SSC3 bootrom
upgrade, please proceed to “Enable PDP session creation on the
GGSN” , step 15.
• If the SSC3 XFPGA firmware version returned in the previous step
does not match ‘12,’ please proceed to the next step to update the
SSC3 XFPGA firmware version.
411-5221-923 Standard 06.09 August 2008

Procedure C-7
Step Action
5 Login to the console port of the GGSN.
6 Open two telnet/ ssh terminals to the GGSN. On one, execute the
following command:
ggsn(SSU)# monitor log
Monitor the GGSN ‘monitor log’ terminal’ during the SSC3 XFPGA
upgrade.
7 Login to the SCS client as device_owner user. Double click the GGSN.
From the ‘Device’ tab, select the SSC3 card from the ‘Cards’ table and
click ‘Edit’. In the ‘General’ tab, bring the ‘Administrative Status’ to ‘Down’.
Monitor the GGSN console/ “monitor log” window. Logs similar to the
following will be displayed.
25-Jan-2007 07:37:29 13/1/1:sspmgr,0: 13, 1, INFO, SSM

1 in slot 1 removal processing done
8 On the other telnet/ ssh terminal, perform ‘show card’ and verify the
SSM’s are indicated by “*”.

---- ---------------- ------- -----
1 SSC3 /SSC3 Disabled * * * *

Procedure C-7
Step Action
9 Update SSC3 XFPGA firmware
ggsn(SSU)# update xfpga type=ssc3 slot= <SSC3 slot>

file=<directory path for SSC3_0C.XSV>
Here is an example capture:

shasta-44(SSU)# update xfpga type=ssc3 slot= 1 file= /
disk/image/xfpga/SSC3_0C.XSV
Confirm [y/n]: y
Here are the logs from the GGSN console:

Card type = 16
18-Jan-2007 06:10:09 13/1/1:cli,2: admin@/pty/tel00.S:
[Success]: update xfpga type=ssc3 slot= 2 file= /disk/
image/xfpga/SSC3_0C.XSV
file length = 1213928
SUCCESS - Completed XSVF execution.
FPGA chain updated with file /disk/image/xfpga/
SSC3_0C.XSV!
Here are the logs from “monitor log”

[Attempting]: update xfpga type=ssc3 slot= 1 file= /
disk/image/xfpga/SSC3_0C.XSV
[Success]: update xfpga type=ssc3 slot= 1 file= /disk/
image/xfpga/SSC3_0C.XSV
411-5221-923 Standard 06.09 August 2008

Procedure C-7
Step Action
10 From the SCS client - device_owner user, double click the GGSN. From
the ‘Device’ tab, select the SSC3 card that was disabled from the ‘Cards’
table and click ‘Edit’. In the ‘General’ tab, bring the ‘Administrative Status’
to ‘Up’.
Here the GGSN logs from “monitor log”

25-Jan-2007 10:04:47 13/1/1:cardmgr,0: 33, 1, INFO,
Card in slot 1 has been enabled.
[Success]: enable card slot= 1
…
25-Jan-2007 10:04:57 13/1/1:cardmgr,0: 34, 1, INFO,
Card in slot 1 is up.
…
Attention: If patches are applied to the GGSN and include SSP patches,
these patches will be reapplied when the SSC3 SSM’s comes up.
…
25-Jan-2007 10:05:17 13/1/1:sspmgr,0: 3, 1, CLEAR, SSM
1 in slot 1 is up
2 in slot 1 is up
3 in slot 1 is up
4 in slot 1 is up
25-Jan-2007 10:06:02 1/1/2:com,0: 2, 1, INFO,
Overload: Resource cpu has been enabled.
25-Jan-2007 10:06:02 1/1/2:com,0: 2, 1, INFO,
Overload: Resource interrupt has been enabled.
…
11 Verify all the SSM’s are up.

---- ---------------- ------- -----

Procedure C-7
Step Action
12 Verify the version displayed in “show card slot=<SSC3 slot>

mode=detail”. Parameters “GGI GMII Bridge A version” and “GGI GMII
Bridge B version” must indicate “12.”

ggsn(SSU)# show card mode=detail
---- ---------------- ------- -----
SSC3 state: running

SEC state: running
XPIF state: running
CPU: BCM1250 (0x125011ff) Bus Speed: 357MHz
ROM version: 1.5(1)
DIAG ROM version: 3.13
GGI GMII Bridge A version: 12
GGI GMII Bridge B version: 12
SEC GMII Bridge version: 7

ROM version: 1.5(1)

ROM version: 1.5(1)

ROM version: 1.5(1)
411-5221-923 Standard 06.09 August 2008

Procedure C-7
Step Action
13 When the SSC3 XFPGA firmware upgrade has completed and all the
SSC3 SSM’s are up, then proceed to upgrading the next SSC3 card.
Repeat step 7 through step 12 (above) to update the XFPGA firmware on
all SSC3 cards on the GGSN.
14 After SSC3 XFPGA firmware update, please proceed to “Enable PDP

session creation on the GGSN” , step 15 to enable traffic.
-END-
CMC2 Server Port Migration

The CMC2 Server Ports are the ENET 1 and ENET 2 ports on the
CMC2 faceplate. After the GGSN has been upgraded to at least
GGSN4.1.1 and prior to deploying the CMC3 cards, the CMC2 Server
Port connections and trunks must be migrated to line card ports since
the CMC3 card does not contain any Server Ports. The Server Port
Migration may be done while the GGSN is in-service during a low-
traffic maintenance window. This procedure must be completed and
test-soaked prior to deploying the CMC3 cards.
During an in-service Server Port Migration, the communication to the

servers with which the CMC2 Server Ports communicate may be
temporarily halted. If communication with a CGF accounting server is
temporarily halted and GTP CDR accounting records need to be sent
to the CGF, the GGSN will save the GTP CDR accounting records to
the CMC2 disk. Once communication to the CGF resumes, the user
can issue a command to send GTP CDR accounting records on the
CMC2 disk to the CGF.
The ISP IP address which the Server Ports use must not be changed
during the in-service Server Port Migration.
Types of Migration
The Server Port Migration to FELC ports is preferred since the Server
ports on the CMC2 are equivalent to Fast Ethernet ports on a FELC. If
the Server Port Migration to FELC ports is not possible, then migration
to GELC and ALC ports is allowed. The following procedures are
defined:
• Migration of CMC2 Server Ports to FELC - for customers who have
spare FELC ports and use CMC2 Server ports. This procedure
requires at least two FELC cards in the GGSN.

• Migration of CMC2 Server Ports to GELC - for customers that use

GELC and CMC2 Server ports but do not have spare FELC ports.
This procedure requires at least two GELC cards in the GGSN.
• Migration of CMC2 Server Ports to ALC - for customers that use
ALC and CMC2 Server ports but do not have spare FELC ports.
This procedure requires at least two ALC cards in the GGSN.
• Migration of Auxiliary Management CMC2 Server Port - for
customers who use an auxiliary management Server port.
Migration of CMC2 Server Ports to FELC
Procedure C-8
Migration of CM2 server ports to FELC
Step Action
1 Determine the IP address and root password of the servers that

communicate with the CMC2 Server ports. Login to these servers to verify
the correctness of the server IP address and root password. This
information will be needed in a later step.
2 Select spare FELC ports to be used as Server ports.

a. Two FELC cards should be selected that have spare ports in order to
achieve card redundancy. If only one Server port is to be migrated
from each of the two CMC2 cards, only one spare port is needed on
each of the two FELC cards. If two Server ports are to be migrated
from each of the two CMC2 cards, two spare ports are needed on
each of the two FELC cards.
b. If not enough spare FELC ports are available or if the customer
prefers, two new FELC cards should be used if two spare line card
slots are available. The total number of line cards in the GGSN should
not exceed four.
c. For identification purposes in this procedure, name one of the FELC
cards “FELC #1” and the other “FELC #2”.
411-5221-923 Standard 06.09 August 2008

Procedure C-8
Migration of CM2 server ports to FELC (continued)
Step Action
3 Make note of the Connection ID and Trunk Interface Name that

corresponds to each CMC2 Server Port.
a. Using the SCS client, login with device owner privileges to the ISP
which uses the CMC2 Server Ports.
b. On the GGSN Configuration - Connections displays for CMC/13 and
CMC/14, make note of the Connection ID’s for Enet 1 and Enet 2 for
both CMC2’s.
c. On the GGSN Configuration - Trunk Interfaces displays for CMC/13
and CMC/14, make note of the Trunk Interface Names for Enet 1 and
Enet 2 for both CMC2’s.
4 Map the Server port Connection ID’s to FELC ports.

a. For each Server port Connection ID recorded for CMC/13 in the
previous step select a spare port to move to in “FELC#1”. Make note
of these choices.
b. For each Server port Connection ID recorded for CMC/14 in the
previous step select a spare port to move to in “FELC#2”. Make note
of these choices.
5 Check that communication to each server is up.

a. If CGF’s are used, their state can be displayed with the ‘show gtpbill
<ispname>’ command. If the “CGF State” is IDLE or RUNNING, the
CGF is operational and has IP connectivity to the GGSN.
b. Do not proceed to next step until all servers associated with the
CMC2 Server Ports are up.
6 Add cabling to the selected ports on “FELC#1” and “FELC#2” if it is not

already present.
7 If Connections and Trunk Interfaces for the selected ports on “FELC#1”

and “FELC#2” were previously configured on another ISP but are
currently unused, record any configuration information used by these
Connections and Trunk Interfaces that may need to be saved. Next,
delete these same Connections and Trunk Interfaces.

Procedure C-8
Step Action
8 Add new Connections and Trunk Interfaces to the previously selected

ports on “FELC#1” and “FELC#2.
a. In order for the outgoing traffic to be balanced across all the
Connection ID’s, the “Weight values” in the Connection Configuration
displays should remain at their default value of “1”.
b. If a routing protocol such as OSPF is used, configure the routing
protocol to be used by the newly configured Trunk Interfaces by going
to the Routing display.
Attention: For OSPF routing configuration and verification procedure

please refer to “Nortel GGSN Provisioning Procedures (411-5221-927)”
and for OSPF CLI please refer “Nortel GGSN Command Line Interface
Guide (411-5221-922)”.
9 Verify that the new Trunk Interfaces are up.

a. Issue the ‘show interface isp =<ispname>’ CLI command. Where
<ispname> is the isp which the Server Ports use. Verify that each
new interface is Up.
10 If a routing protocol such as OSPF is used, issue the ‘ping isp

=<ispname> <server ip addr> ifname=<ifname>’ CLI command for
each new interface. If pinging fails, take action to correct the IP
connectivity problem.

Guide (411-5221-922)”.
11 Check if the provisioned Routing and Profile(s) configuration need to be

changed. For example, check if any static routes to the CMC2 Server
Ports need to be removed or changed.
411-5221-923 Standard 06.09 August 2008

Procedure C-8
Step Action
12 If static routes are required in the external router network between the
GGSN and the servers, add the static routes to external routers. The
communication to the servers may go down while the static routes in the
external network are being modified.
a. Use the ‘show isp <ispname>’ CLI command to find the IP address
of the ISP which the Server Ports use.
b. Add static routes to the external routers so packets sent to the ISP IP
address will be sent to the selected ports on “FELC#1” or “FELC#2”.
c. Issue the ‘ping isp =<ispname> <server ip addr>
ifname=<ifname>’ CLI command for each new interface. If pinging
fails, take action to correct the IP connectivity problem.
d. From each server, verify that the ISP IP address which the Server
Ports use can be pinged. If pinging fails, take action to correct the IP
13 Unplug the Ethernet cables from CMC/13’s and CMC/14’s Server ports.
14 After waiting several minutes, verify communication to the servers is up. If

a routing protocol is used, it may take several minutes for the packets to
be re-routed from the CMC2 Server Ports to the new Line Card ports.
a. Use the ‘show isp’ CLI command to verify that the ISP which the
Server Ports use is up.
b. From each server, verify that each new trunk interface IP address can
be pinged.
c. From each server, verify that the ISP IP address which the Server
Ports use can be pinged.
d. If CGF’s are used, their state can be displayed with the ‘show gtpbill
e. If any step above fails, take action to correct the IP connectivity
problem. If the problem cannot be corrected, re-plug the CMC2
Server Port cables and return to the previous GGSN and external
router configurations.
15 If communication to all servers is verified to be up, delete the old CMC2

Sever Port Connections and Trunk Interfaces.
16 Validate the correct operation. Perform test calls which require

communication with all of the servers using the newly configured FELC
ports. Verify the correct operation.

Procedure C-8
Step Action
17 Validate the FELC card redundancy.

a. Unplug each Server port Ethernet cable on “FELC #1”.
b. Perform test calls which require communication with all of the
servers. Verify the correct operation.
c. Replug each Server port Ethernet cable on “FELC #1”. Unplug each
Server port Ethernet cable on “FELC #2”.
d. Perform test calls which require communication with all of the
e. After finished testing, replug each Server port Ethernet cable on
“FELC #2”.
f. If this step fails, determine the problem and take corrective action.
18 If using a CGF, issue the ‘gtpbill disksend allow’ CLI command, to send
any GTP CDR billing records on the CMC2 disk to the CGF.
19 The Server Port Migration to FELC procedure has been completed.
-END-
Migration of CMC2 Server Ports to GELC

If a certain ISP is used on the CMC2 Server Ports, this same ISP can
continue to be used after the CMC2 Server Ports have been migrated
to GELC ports. For example, in Figure C-1, two Ga ISP trunks are
used and an external router filters (firewalls) the Gn ISP trunk and Ga
ISP trunk traffic. The Ga and Gn trunks defined on the GGSN each
have their own MAC/IP addresses. The router should filter the traffic
based on the source MAC/IP address.
411-5221-923 Standard 06.09 August 2008

Figure C-1
Traffic Security using Ga and Gn trunks and external router
GELC #1 wireless
Gn ISP trunk core
Ga ISP trunk network
Router
GELC #2
Gn ISP trunk
CGF
Ga ISP trunk
Procedure C-9
Server port migration to GELC
Step Action
1 Configure an external router to firewall the traffic between the two ISP
trunks. For example, in Figure 1 the Gn ISP trunk traffic is not allowed to
enter the CGF. Also, the Ga ISP trunk traffic is not allowed to enter the
wireless core network. The external router’s routing table should allow the
Ga ISP trunks to communicate with the Servers, which in this example, is
the CGF.

3 The CMC2 Server Port traffic needs to be moved to two GELC cards. Two
GELC cards are needed in order to achieve card redundancy. Select the
two GELC cards. For identification purposes in this procedure, name one
of the GELC cards “GELC #1” and the other “GELC #2”.

both CMC2’s.

Procedure C-9
Server port migration to GELC (continued)
Step Action

If CGF’s are used, their state can be displayed with the ‘show gtpbill
<ispname>’ command. If the “CGF State” is IDLE or RUNNING, the CGF
is operational and has IP connectivity to the GGSN.
Do not proceed to next step until all servers associated with the CMC2
Server Ports are up.
6 Add cabling to “GELC#1” and “GELC#2” if it is not already present.
7 Add new Connections and Trunk Interfaces to cards “GELC#1” and

“GELC#2.

and for OSPF CLI please refer to “Nortel GGSN Command Line Interface
Guide (411-5221-922)”.

a. Issue the CLI command.
show interface isp =<ispname>
Where <ispname> is the isp which the Server Ports use.
Verify that each new interface is Up.
9 If a routing protocol such as OSPF is used, issue the CLI command for
each new interface.
ping isp =<ispname> <server ip addr> ifname=<ifname>
If pinging fails, take action to correct the IP connectivity problem.

Guide (411-5221-922)”.
411-5221-923 Standard 06.09 August 2008

Procedure C-9
Step Action

address which the Server Ports use will be sent to “GELC#1” or
“GELC#2”.
c. Issue the ‘ping isp =<ispname> <server ip addr>
ifname=<ifname>’ CLI command for each new interface. If pinging
fails, take action to correct the IP connectivity problem.

be pinged.


Procedure C-9
Step Action

communication with all of the servers using the newly configured GELC
cards. Verify the correct operation.
16 Validate the GELC card redundancy.

a. Unplug cable on “GELC #1”.
c. Replug cable on “GELC #1”. Unplug cable on “GELC #2”.
e. After finished testing, replug cable on “GELC #2”.
18 The Server Port Migration to GELC procedure has been completed.
-END-
Migration of CMC2 Server Ports to ALC

If a certain ISP is used on the CMC2 Server ports, this same ISP can
continue to be used after the Server Ports have been migrated to ALC
ports. For example, in Figure C-2, two Ga ISP trunks are used and an
ATM switch/router filters (firewalls) the Gn ISP trunk and Ga ISP trunk
traffic. If spare ALC ports are available, these should be used for the
Ga traffic. Otherwise, Ga and Gn trunk traffic can be combined on a
single ALC port with the use of separate virtual circuits. The Ga and
Gn trunks defined on the GGSN each have their own VPI/VCI/IP
addresses. The ATM switch/router should filter the traffic based on the
VPI/VCI and/or source IP address.
411-5221-923 Standard 06.09 August 2008

Figure C-2
Traffic Security using Ga and Gn ISP trunks and external ATM Switch/Route
r
ALC #1 ATM Switch/Router

Gn ISP trunk wireless
Ga ISP trunk core
network
ALC #2
Gn ISP trunk ethernet CGF
Ga ISP trunk
Procedure C-10
Server port migration to ALC
Step Action
1 Configure an external ATM switch/router to filter (firewall) the trunk traffic

between the two ISP trunks. For example, in Figure 2 the Gn ISP trunk
traffic is not allowed to enter the CGF. Also, the Ga ISP trunk traffic is not
allowed to enter the wireless core network. The external router’s routing
table should allow the Ga ISP trunks to communicate with the Servers,
which in this example, is the CGF.

3 The CMC2 Server Port traffic needs to be moved to two ALC cards. Two
ALC cards are needed in order to achieve card redundancy. Select the
two ALC cards. For identification purposes in this procedure, name one of
the ALC cards “ALC #1” and the other “ALC #2”.

both CMC2’s.

Procedure C-10
Server port migration to ALC (continued)
Step Action
5 Map the Server port Connection ID’s to ALC ports.

a. If spare ALC ports are available, these should be used for the Server
Port traffic. Otherwise, separate ISP trunk traffic can be combined on
a single ALC port with the use of separate virtual circuits.
b. For each Server port Connection ID recorded for CMC/13 in the
previous step select a spare port to move to in “ALC#1”. Make note of
these choices.
c. For each Server port Connection ID recorded for CMC/14 in the
previous step select a spare port to move to in “ALC#2”. Make note of
these choices.

a. If CGF’s are used, their state can be displayed with the ‘show gtpbill
b. Do not proceed to next step until all servers associated with the
CMC2 Server Ports are up.
7 Add cabling to the selected ports on “ALC#1” and “ALC#2” if it is not

already present.
8 If Connections and Trunk Interfaces for the selected ports on “ALC#1”

and “ALC#2” were previously configured on another ISP but are currently
unused, record any configuration information used by these Connections
and Trunk Interfaces that may need to be saved. Next, delete these same
Connections and Trunk Interfaces.
9 Add new Connections and Trunk Interfaces to the previously selected

ports on “ALC#1” and “ALC#2.

Guide (411-5221-922)”.
411-5221-923 Standard 06.09 August 2008

Procedure C-10
Step Action

a. Issue the CLI command.
show interface isp =<ispname>
Where <ispname> is the isp which the Server Ports use.
Verify that each new interface is Up.
11 If a routing protocol such as OSPF is used, issue the CLI command for
each new interface.

Guide (411-5221-922)”.

address will be sent to the selected virtual circuits on “ALC#1” or
“ALC#2”.
c. Issue the CLI command for each new interface.


Procedure C-10
Step Action

be pinged.


communication with all of the servers using the newly configured ALC
ports. Verify the correct operation.
18 Validate the ALC card redundancy.

a. Unplug each Server port cable on “ALC #1”.
c. Replug each Server port cable on “ALC #1”. Unplug each Server port
cable on “ALC #2”.
e. After finished testing, replug each Server port cable on “ALC #2”.
20 The Server Port Migration to ALC procedure has been completed.
-END-
411-5221-923 Standard 06.09 August 2008

Migration of auxiliary management CMC2 server port

If a customer is using an auxiliary management CMC2 Server port, it
must be migrated to a FELC, GELC or ALC port. It is preferred that a
FELC port be used if a spare FELC port is available.
Procedure C-11
Migration of auxiliary management CMC2 server port
Step Action
1 Telnet into the CMC2 management port.
2 Issue the following CLI command: ‘show quickstart’. Save the

information that is displayed.
3 Select up to three FELC, GELC or ALC ports to be used as auxiliary

management ports.
4 Configure an external router to provide traffic separation (firewalling)

between these ports and the SCS Server and the other traffic.
5 Pull the CMC’s auxiliary management CMC2 Server port cables. Add
cable(s) to the selected FELC, GELC or ALC port(s) if necessary.
6 Verify that the Operation Status of each selected port is “Up”.
7 Issue the CLI command: ‘set quickstart’.

a. If migrating to ALC, enter the configuration information requested for
the “auxiliary management ATM interface”.
b. If migrating to FELC or GELC, enter the configuration information
requested for the “auxiliary management Ethernet interface”.
8 The newly created interface(s) can be seen with:

show interface
To check the routing table for this isp

show route isp=default

Procedure C-11
Migration of auxiliary management CMC2 server port (continued)
Step Action
9 OSPF can be configured for the new auxiliary management port(s) only
by issuing CLI commands. If OSPF is needed, the OSPF area and
interface must be added for the auxiliary management. Here is an
example:
> add ospf area isp=default area=2.2.0.4 type=normal
report_isp_ipaddr=yes
> add ospf interface isp=default area=2.2.0.4
interface=mgmt-eth1 dr_priority=1 auth=none cost=1
type=bcast
> start ospf default
In order for the above commands to be accepted, the Default ISP IP

address must be configured. To configure the Default ISP IP address,
login to the SCS as the device_owner, go to Device, go to Routing. Enter
the Default ISP IP address.
To check the OSPF configuration:
show isp isp=default
10 From a server, verify that the new auxiliary management port can be
pinged. If pinging fails, determine the IP connectivity problem and take
corrective action. If the problem cannot be resolved, abort this procedure
by issuing ‘set quickstart’ and setting the parameters back to the original
values recorded and reconnecting the cabling.
11 Verify operation of auxiliary management port.

a. Telnet into the new auxiliary management port.
b. Verify that the GGSN login prompt appears. If the GGSN login prompt
does not appear, abort this procedure by issuing ‘set quickstart’ and
setting the parameters back to the original values recorded and
reconnecting the cabling.
c. Login to the GGSN.
12 The Migration of Auxiliary Management CMC2 Server Port Procedure is

complete.

Guide (411-5221-922)”.
-END-
411-5221-923 Standard 06.09 August 2008

D-1
Appendix D: GGSN billing status

verification CLI command output on
GGSN’s with SSC3 cards D
This section explains a GGSN billing status verification CLI command
output on GGSN's with SSC3 cards.
During GGSN card maintenance or software upgrade, the GGSN CLI

command 'gtpbill flush billing isp=<Ga ISP>' is issued to flush GGSN
billing records to disk.
The status can be verified using the GGSN CLI command:
show gtpbill isp=<Ga ISP> mode=detail
On GGSN's with SSC3 cards, the output of
show gtpbill isp=<Ga ISP>
may appear stuck with the values below:

<command>
"Bulk Update In Prog: Yes"
"Outstanding SSP Reps: 32 "
<command>
The above example is for a 4 SSC card line up
(4 SSC x 4 SSM x 4 SSP = 64 SSP processors).
Impact
For GGSN's with SSC3 cards, users will not know when the GTP
billing information has been flushed.

D-2 Appendix D: GGSN billing status verification CLI command output on GGSN’s with SSC3 cards
Details
SSC3 cards have 2 SSP's per SSM, while SSC2 cards have 4 SSP's
per SSM. The software is calculating the Outstanding SSP Reps with
SSC2 cards at 64. So the command will never be complete with SSC3
cards, as there are only 32 SSP's. When the Outstanding SSP Reps is
at 32, the command is essentially finished and customer may continue
at that point.
411-5221-923 Standard 06.09 August 2008

E-1
List of terms E
Access link
Type of connection that always belongs to a subscriber.
AC Power Shelf
Optional power supply for the chassis. The AC Power Shelf is required only
when a source of –48 VDC is not available.
ALC
ATM line card, installed in the chassis. The ALC can be a dedicated card or
a multiplexed card, depending upon whether it contains an ICP module:
Dedicated card—No ICP module. Card is used for access connections, to

and from subscribers only.
Multiplexed card—With ICP module. Card is used for trunk connections to

Internet service providers.
BSN
Broadband Service Node.
Chassis
Nortel GGSN chassis. The chassis contains a fan tray for cooling and a card
cage for all cards.
CLI
The command line interface (CLI) is the GGSN software that is seen on the
terminal after the quickstart. Use the CLI only for troubleshooting and
monitoring system activity.
CMC
Control/Management Card, installed in the chassis. One CMC is required in
each chassis, and one additional CMC may optionally be added for
redundancy. The CMC must be installed in slot 13 or slot 14. If there is only
one CMC, it must be installed in slot 14.

E-2 List of terms Copyright © 2004–2008 Nortel Networks
Fan tray
Removable tray of fans used for cooling the Nortel GGSN chassis.
FELC
Fast Ethernet Line Card. Provides eight ports of Ethernet connectivity. Each
port operates on either 10BASE-T or 100BASE-T. Each port is autosensing
to the line rate and connects to the user network via an RJ-45 and UTP
cable. The FELC translates the incoming Ethernet frames into ATM cells, via
a layer 2/layer 3 lookup, and steers those frames to the appropriate SSM. In
the outgoing direction, ATM cells are converted into Ethernet frames with
the appropriate MAC header.
Filter
Removable filter mounted directly above the fan tray in the Nortel GGSN
chassis. The filter cleans air sent to cool the chassis cards.
ICP
Intelligent Card Parser, a module mounted on many ATM line cards (ALCs).
ISP
Internet service provider.
Line card
Line cards include ATM line cards and other types. There are typically one
to six line cards per chassis. Line cards may be installed in slots 1–6, slots
9–12, and in slot 13 (if not used for a second CMC).
Power modules
Replaceable power supplies used in the optional AC Power Shelf. The AC
Power Shelf can hold up to four power modules. Each power module is an
independent “hot-swappable” unit.
Quickstart
Internal GGSN software for initial startup and entering the IP address of the
chassis.
SFC
Switch Fabric Card, installed in the chassis. The SFC is based on an ATM
switching matrix, providing connectivity between GGSN subscribers and IP
networks. One SFC is required in each chassis, plus one additional card for
redundancy. The SFC must be installed in slot 7 or slot 8.
SFC Daughter Module

Part of the Switch Fabric Card (SFC) that determines allowable system
load. SFC daughter module is as follow:
411-5221-923 Standard 06.09 August 2008

List of terms E-3
7.5 Gb/s daughter module
SCS
Service Creation System, a powerful graphical management and
provisioning tool that allows the device owner and/or Internet service
provider (ISP) clients to quickly and efficiently configure device and
subscriber parameters.
SSC
Subscriber Service Card, installed in the chassis. There are typically two to
six SSCs per chassis. SSCs may be installed in slots 1–6, slots 9–12, and
slot 13 (if not used for a second CMC).The SSC is equipped with one to four
subscriber service modules (SSMs).
SSM
Subscriber service module, a module on the Subscriber Service Card
(SSC). The SSC has space for four SSMs.
Trunk port
Port to an ISP. This type of port supports routing.
U2-ICP
U2 intelligent card parser, a daughter module. Used in some ATM line cards.
VPN
Virtual private network.

E-4 List of terms Copyright © 2004–2008 Nortel Networks
411-5221-923 Standard 06.09 August 2008

test
Family Product Manual Contacts Copyright Confidentiality Legal
Nortel GGSN
Hardware Installation and Maintenance Guide
Document number: 411-5221-923
Product release: GGSN 6.0

Document version: Standard 06.09
Date: August 2008
Originated in the United States of America/Canada
To order documentation from Nortel Networks Global Wireless Knowledge Services, call
(1) (877) 662-5669
To report a problem in this document, call

(1) (877) 662-5669
or send e-mail from the Nortel Networks Customer Training & Documentation World Wide Web site at
http://www.nortel.com/documentfeedback
Copyright © 2004–2008 Nortel Networks, All Rights Reserved
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing
NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS
OR IMPLIED. The information and/or products described in this document are subject to change without notice.
Nortel, Nortel Networks, the Nortel logo and the Globemark are trademarks of Nortel Networks.
All other trademarks are the property of their respective owners.

Nortel GGSN - HW Installation and Maintenance Guide - 411-5221-923

Загружено:

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

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

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

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

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

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

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

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

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

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

Nortel GGSN - HW Installation and Maintenance Guide - 411-5221-923

Загружено:

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

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

411-5221-923

Document number: 411-5221-923

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright © 2004–2008 Nortel Networks, All Rights Reserved

All other trademarks are the property of their respective owners.

411-5221-923 Standard 06.09 August 2008

Addeded “Appendix D: GGSN billing status verification CLI command

Added references to the new Appendix D, throughout the document.

Added the following steps:

• Step 12 in “Single CMC card configuration” on page 4-35

Modified some references to GGSN5.0.1 and GGSN4.1.1.

GGSN6.0, Preliminary 06.06

Nortel GGSN Hardware Installation and Maintenance Guide GGSN 6.0

Modified/Deleted references to GGSN5.0 under the following sections:

• “Subscriber Service Card (SSC3)” on page 1-7

GGSN 6.0, Preliminary 06.05.

Added step 14 in “SSM bootrom upgrade” on page C-19, and added

GGSN 6.0, Preliminary 06.04.

Modified steps 16, 23 and 24 of Multiple CMC card configuration

Modified Figure i, "PC05 Documentation Roadmap" on page vii

411-5221-923 Standard 06.09 August 2008

Preliminary 05.06, GGSN 5.0. Corrected for SME comments and

Preliminary 05.02, GGSN 5.0.

Nortel GGSN Hardware Installation and Maintenance Guide GGSN 6.0

411-5221-923 Standard 06.09 August 2008

Nortel GGSN hardware overview 1-1

Chassis physical installation 2-1

Nortel GGSN Hardware Installation and Maintenance Guide GGSN 6.0

Installing DC power (No AC Power Shelf) 2-14

Initial startup and configuration 3-1

Maintenance, repair, and upgrade 4-1

411-5221-923 Standard 06.09 August 2008

Logging out 4-11

Appendix A: Nortel GGSN specifications A-1

Appendix B: Hardware reference B-1

Appendix C: Product maintenance procedures C-1

Nortel GGSN Hardware Installation and Maintenance Guide GGSN 6.0

Migration of auxiliary management CMC2 server port C-47

Appendix D: GGSN billing status verification CLI command output

List of terms E-1

411-5221-923 Standard 06.09 August 2008

About this document 2

The GGSN system consists of:

Before you begin 2

• What’s covered in this manual:

• When to use this manual:

• Who should use this manual:

Nortel GGSN Hardware Installation and Maintenance Guide GGSN 6.0

This guide uses the following text conventions:

How to get help 2

If you purchased a Nortel service program, contact Nortel Technical

411-5221-923 Standard 06.09 August 2008

GGSN06 GGSN and SCS SGSN/GPRS SGSN Provisioning SGSN SGSN

Nortel GGSN Hardware Installation and Maintenance Guide GGSN 6.0

– Serving GPRS Support Node (MS - SGSN) Logical Link Control

411-5221-923 Standard 06.09 August 2008

• 3GPP TS 29.060 (V4.11.0), “General Packet Radio Service

Nortel GGSN Hardware Installation and Maintenance Guide GGSN 6.0

• Passport 7400, 15000, 20000 Data Collection Guide (241-5701-

Nortel Wireless Network Management

411-5221-923 Standard 06.09 August 2008

Preside Multiservice Data Manager (MDM) documentation

Indication of hypertext links 2

To alleviate any confusion the rebranding might cause, Table i and