411-5221-309 v6 30

411-5221-309
GPRS/UMTS
Nortel GGSN and SCS

Upgrade Manual
GGSN6.0 Standard 06.30 March 10, 2010
test
GPRS/UMTS
Nortel GGSN and SCS

Upgrade Manual
Document number: 411-5221-309 Product release: GGSN6.0 Document version: Standard 06.20 Date: April 16, 2009
Copyright1 Country of printing2 Confidentiality3 Legal statements4 Trademarks5
1Copyright 20002006 Nortel Networks, All Rights Reserved 2Sourced in the United States of America 3NORTEL CONFIDENTIAL
The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose it only to its employees with a need to know, and shall protect it, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein. 4Information is subject to change without notice. Nortel Networks reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. This equipment has been tested and found to comply with FFC regulations. This equipment generates, uses and can radiate radio frequency energy. If not installed and used in accordance with the instruction manual, this equipment may cause harmful interference to radio communications. This equipment is designed to provide reasonable protection against harmful interference when installed and operated correctly. Operation of this equipment in a residential area can cause harmful interference, in which case the user will be required to correct the interference at their own expense.
Nortel Networks Confidential
411-5221-309
Standard
06.30 March 10, 2010
Publication history
March 10, 2010 Draft 06.30; Add steps to migrate from SCS 5.0.2 to SCS 6.0.1 at section Migrating SCS to a new physical server with Same or Different IP address on page 169.
April 16, 2009 Draft 06.20; Information related to CR Q02013599/ Case 090403-12755 updated. GGSN upgrade checklist updated with steps to verify GGSN disk space usage and if necessary, delete specified files. SectionVerify sufficient GGSN/SCS space on page 105 In case of GGSN rollback, verify GGSN patches are applied after resync. Section GGSN Rollback procedure on page 547
April 9, 2009
Draft 06.18; The SCS now supports the Sun Netra T5220 Server. The T5220 only supports Solaris 10, and is shipped with Solaris 10 already installed. Only the GGSN5.0.1 and GGSN6.0 releases are supported on the T5220. There is no DAT drive shipped with the T5220. If transitioning an existing SCS server to the new T5220 hardware, the high level process is to install Solaris 10 on the new T5220 server, perform a new install of the GGSN SCS 6.0.1 application software, copy over the data, and bring into service. If performing a new SCS deployment, new install procedure is also provided.
GPRS/UMTS
Upgrade Manual GGSN6.0
Publication history
The following sections have been updated for SCS server migration to Solaris 10 operating system. - SCS Support on Sun Netra T5220 on page 16 - SCS Migration or New Installation on Sun Netra T5220 on page 22 - SCS server preparation: Migration of the current SCS to new hardware or New Install of SCS on new hardware on page 142 - Migrating SCS to a new physical server with Same or Different IP address on page 169 - Appendix S: Solaris 10 Installation on page 745 - Appendix T: Perform SCS 6.0.1 new installation on page 764 - Appendix U: SCS 6.0.1 Database Migration Example on page 777 June 10, 2008 Draft 06.12; CR Q01886391 related to corrections noted during VO SCS and GGSN 6.0 upgrade. Changes have been updated to Checklist, SCS upgrade, GGSN upgrade chapters.
June 2, 2008 Draft 06.11; Corrections were noted during VO SCS and GGSN 6.0 upgrade. Changes have been updated to GGSN Software Upgrade chapter. May 13, 2008 Draft 06.10. <<add new content, CR info>> May 11, 2008 Draft 06.09. Fast feature patch migration steps added to Upgrade readiness checkpoint #1 (14 days prior) on page 86 March 18, 2008 Draft 06.06; draft. Following CRs have been updated. Q01841280, Q01845615, Q01772242-01. March 11, 2008 Draft 06.05; draft. Following CRs have been updated. Q01796777-01 - SCS client hangs in Windows 2003 during the
411-5221-309
Standard
06.30 March 10, 2010
Publication history
Uninstallation process. Refer to SCS client rollback on XP (version 2002 or later), Window 2003 and Vista on page 358 1. Q01688364-01 - Procedure to install SCS client on Windows 2003 Refer to SCS Client Installation for XP (version 2002 or later) and Vista on page 356 and SCS client rollback on XP (version 2002 or later), Window 2003 and Vista on page 358 2. Q01787789 - Upgrade NTP updates required - During Solaris 9 patch cluster installation, in case /opt is not mounted on server reboot. Section Install Recommended Patches for Solaris 9 and Solaris 10 on page 452 has been updated with steps to mount /opt in case the partition is not mounted. - In case /etc/passwd was edited with an incorrect path for csh, future login to the server as root user will fail. Section Resolve SCS server login issue in case of incorrect shell path on page 227 can be followed to correct the issue. - SSL precheck: Following sections updated: Determine if SSL is enabled on the SCS server on page 62, Optional -Install SSL Package on page 297 - SSL installation for SCS client on Unix: Following sections updated: Enabling SSL on the SCS Client on page 358 3. Q01505119-03 - Invalid IP address for SNTP Client Configuration The following pre-upgrade and post-upgrade checks have been added. - SCS pre-upgrade: Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration on page 99, - SCS post-upgrade:Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration on page 339, - GGSN post-upgrade: Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration on page 543 - GGSN rollback: Software rollback procedure on page 5-547 Step 4. on page 548 updated. March 10, 2008 Draft 06.04; draft. Follow CRs have been updated. Q01787702 - Note related to single SSC3 card configuration has been added under SSC3 XFPGA firmware update section. Refer to Step 11 on page 529 and Step 15 on page 531 Q01803186-01 - Option to perform automatic SCS and iPlanet backup. Refer to SCS Periodic Backup setup option on page 225. SCS post upgrade checklist has been updated - Configure SCS 6.0 periodic backup on page 329
GPRS/UMTS
Publication history
January 24, 2008 Draft 06.03; draft. Fast feature patch migration details added. Please refer to Upgrade readiness checkpoint #1 14 days prior to upgrade on page 35 January 24, 2008 Draft 06.02; draft. Updates to feature migration added. Pre-checks for feature patches: Upgrade readiness checkpoint #1 14 days prior to upgrade on page 35 Post SCS 6.0 upgrade checklist: Upgrade readiness checkpoint #5 every day after the upgrade for 7 days on page 304 Post GGSN 6.0 upgrade checklist: GGSN Post-Upgrade Procedure on page 541 New section updated: Add or Verify SOC key on page 223, Verify patch status information on page 224.
November 2, 2007 Draft 06.01; draft. Updates with review comments. CR Q01666808 updated. Please refer to the CR notes for details. September 30, 2007 Draft 06.00; draft. June 20, 2007 Standard 04.31; standard release. The following updates have been added. Q01505096 - Procedure to modify host name, domain name and IP address after SCS installation New section Appendix O: Procedure to modify SCS server IP, host name or domain name on page 689 has been added to assist users to modify the SCS server systems settings. New section Appendix P: Perform a SCS 6.0 new install on page 704.
411-5221-309
Standard
06.30 March 10, 2010
Publication history
The following sections have been added related to the migration procedure. - Modifying LDAP backup in case of server domain name change on page 211 - Resetting LDAP/ iPlanet Root DN name and password on page 212 - Modify SCS server IP address or hostname on page 218 - Modify SCS server domain name on page 220 June 01, 2007 Standard 04.30; standard release. The following updates have been added. 1. CR Q01651001 - Wrong billing records - Precheck Checkpoint 1 item 21, page 103 added to verify if patch G411_01339974AACT_GTPACCT has been applied and activated. - Postcheck Checkpoint 5 item 30, page 341 added to make changes to Max SGSN Change Partial Billing option on the APN Groups if patch G411_01339974AACT_GTPACCT was activated in GGSN 4.1.1. These checkpoints are applicable to GGSN 4.1.1 to GGSN 5.0.x upgrade only. 2. CR Q01657607 - No allocated metadb space on mounted partition Section Appendix L: Procedure to mirror a server in case metadb partition is not assigned on page 676 has been added. This procedure can be used to mirror a non-mirrored SCS server. This procedure requires free (unmounted) disks to be available on the server. 3. A new section Appendix M: Updating server eeprom on page 685 has been added to assist users to set the server boot parameters in eeprom. Setting eeprom can be performed in multi-user mode. This eliminates going into the server ok prompt to make changes to the boot options. 4. A new section Appendix N: Using format utility to modify the partition flag on page 687 has been added to assist users to verify or modify the disk partition flags. 5. Discrepancies with disk space requirements for Solaris 9 Live upgrade and SCS 5.0.x upgrade have been corrected. Sections updated are: - Checkpoint 0 item 6, page 52SCS server hardware analysis on page 52 - Checkpoint 0 item 15, page 78 Familiarize with the process of creating a Solaris 9 Boot Environment (BE) on page 78 - Solaris 9 Boot Environment Creation on page 414 - Appendix K: Disk Analysis For Non-Mirrored Servers on page 666
GPRS/UMTS
10
Publication history
May 10, 2007 Draft 04.30.1; draft release. The following CRs have been fixed. Q01640370 - Procedure for updating the host name is case there is a mismatch between the current host name and LDAP (or iPlanet) host name has been updated for clarity. Please refer to section SCS server hostname modification if necessary on page 123. Section Enabling SSL on the SCS Client on page 358 has been updated for clarity.
April 26, 2007 Standard 04.29; standard release. The following CRs have been updated. Q01640370 - When there is a mismatch between the SCS server host name and the LDAP (or iPlanet) server instance, the host name of the SCS must be modified to match the LDAP (or iPlanet instance). Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32 has been updated to verify if a hostname mismatch exists. A new checkpoint has been added to modify the host name back if necessary. Please refer to Upgrade readiness checkpoint #6 after it is determined the SCS server will not be rolled back to Solaris 8 on page 308. Q01541686 - Patch application procedure clarification. GGSN Pre-Upgrade Procedure on page 495, Step 15 updated for clarity. GGSN Rollback procedure on page 547, Step 3. and Step 4. updated for clarity.
April 10, 2007 Standard 04.26; standard release with updates for Q01612698. April 2, 2007 Standard 04.25; standard release with updates for Q01483435, Q01589308, procedure to update Solaris 9 patch cluster during Solaris 9 Live Upgrade. March 23, 2007 Standard 04.24; standard release with updates for CR Q01418229, Q01525483, Q01495083, Q01492800, Q01488754, Q01584012, Q01471531, Q01532148.
411-5221-309
Standard
06.30 March 10, 2010
Publication history
11
February 9, 2007 Standard 04.22; standard release with updates for CR Q01565474. January 15, 2007 Standard 04.21; standard release with update for CR Q01525483, Q01526502. November 29, 2006 Standard 04.20; standard release with updates for CR Q01408496, Q01492800, Q01413902, Q01481387, Q01477539. October 10, 2006 Standard 04.19; standard release with updates for CR Q01471255. September 12, 2006 Standard 04.18; standard release with updates for GGSNS5.0.1 upgrade. June 9, 2006 Standard 04.17; standard release for minor changes. June, 2006 Standard 04.16; updated for Standard. May 12, 2006 Preliminary 04.15; updated based on email from Technology. May 1, 2006 Preliminary 04.14; updated based on CR Q01292767. April 26, 2006 Preliminary 04.14; updated with current source from Product Test. April 20, 2006 Preliminary 04.12; corrected issues: Upgrade resync does not work without "set bootorder and reference to a patch G401_01257941A_ISPMGR should be G401_01257941B_G50UPGRADE. April 7, 2006 Preliminary 04.11; first preliminary release of this document. Document reworked based on new source from Design.
GPRS/UMTS
12
Publication history
April 6, 2006 Draft 04.10; Preliminary. Document reworked based on new source from Design. January 24, 2006 Draft 04.08; Preliminary. Changes as per CR Q01295397. January 10, 2006 Draft 04.07; Preliminary. Changes as per CR Q01257941. Provided spelling corrections. January 9, 2006 Draft 04.06; Preliminary. Changes as per CR Q01277141. January 4, 2006 Draft 04.05; Preliminary. Changes as per CRs Q01278442 and Q01280549. December 2005 Draft 04.04; Preliminary. Changes as per CRs Q01274833-01, Q01271324, Q01277307, Q01279904, Q01278442. Draft 04.03; Preliminary. Changes as per CR Q01274833. Draft 04.02; new issue for GGSN 5.0. Changes as per CR Q01269450. October 2005 Draft 04.01; new issue for GGSN 5.0 August 15, 2005 Preliminary 03.05; Pre-upgrade procedure, Step 4 replaced. Optional PostUpgrade Procedures, Steps 4 and 5 and information about G401_01175688_PATCHER added. Items added to GGSN/SCS pre upgrade checkpoint 3. August 5, 2005 Preliminary 03.04; Updated software references to GGSN4.0 to 4.0.1 and GGSNS4.1 to 4.1.1. August 5, 2005 Preliminary 03.03a; Appendix O and Patch removal procedure backouts too.
411-5221-309
Standard
06.30 March 10, 2010
Publication history
13
August 4, 2005 Preliminary 03.02; Pre-upgrade procedure, Step4 update backout. August 3, 2005 Preliminary 03.01; updates for GGSN 4.1.1 including Pre-upgrade procedure, Patch removal and Appendix O-Manual upgrade snapshot. July 22, 2005 Standard 02.23; updates for CR Q1172693. July 20, 2005 Standard 02.22; updates to Backup and restore procedures for SCS appendix. July 20, 2005 Standard 02.21; first standard release of this document for GGSNS4.1. July 19, 2005 Preliminary 02.20; addressed more comments germane to CR Q01172974. July 19, 2005 Preliminary 02.19; addressed CR Q01172974 (added information from PB33: Auxiliary Ethernet Management Port and/or Default ISP if, after a switch sfc, switch cmc, resync, GGSN Upgrade, GGSN Rollback command execution, the qs1 ispdb.cfg becomes corrupted and auxiliary Ethernet management port and/or default ISP do not recover correctly). July 15, 2005 Preliminary 02.18; addressed CR Q01172707. July 14, 2005 Preliminary 02.17; added information from PB 29 (boot loop scenario possibility when rolling back to GGSN3.2.1and recovery procedure). July 14, 2005 Preliminary 02.16; corrections based on feedback in CR Q01124838 (LDAP console start-up in post upgrade checkpoint #1). July 13, 2005 Preliminary 02.15; corrections based on feedback in CR Q01170926. July 5, 2005 Preliminary 02.14; corrections based on feedback in CR Q01166514.
GPRS/UMTS Upgrade Manual GGSN6.0
14
Publication history
June 28, 2005 Preliminary 02.13; minor corrections to patching profile procedures for CR Q01147717. June 16, 2005 Preliminary 02.12; clarified supported bootrom versions for CMC2 (6.3(1) or later) and SSM (6.1(2) or later) in section GGSN Pre-Upgrade Procedure. Also further clarified patching profile procedures for CR Q01147717. June 3, 2005 Preliminary 02.11; addressed CR Q01147717 (multiple issues largely to do with patching profiles). June 2, 2005 Preliminary 02.10; addressed CR Q01145152 (multiple issues). May 18, 2005 Preliminary 02.09; addressed CR Q01124838 (multiple minor issues). Also includes information concerning unsupported accounting elements in GGSNS4.0.1 and beyond, and how to delete if provisioned prior to upgrade. May 12, 2005
check device /disk
Preliminary 02.08; addresses CR Q01135106 (action to take in the event of CLI command errors).
Update with version 4.21: Information for Q01135106 has been removed from the NTP. May 11, 2005 Preliminary 02.07; addresses CR Q01123438 (upgrade timings). May 10, 2005 Preliminary 02.06; addresses CR Q01133327. April 22, 2005 Preliminary 02.05; reflects implementation of software solution for URL wildcard matching, removed the precheck associated with it. April 18, 2005 Preliminary 02.04; added note to rollback procedure explaining what to do if a session error indicated that a version mismatch occurred per CR Q01118752.
411-5221-309
Standard
06.30 March 10, 2010
Publication history
15
April 14, 2005 Preliminary 02.03; changed the command pkgrm NNbrscs.pds to "pkgrm NNBRSCS" for CR Q01113784. March 23, 2005 Preliminary 02.02; first preliminary release of this document for GGSNS4.1. March 17, 2005 Draft 02.01b; addressed CR Q01078852; other changes based on internal review comments. February 1, 2005 Draft 02.01a; new issue for GGSNS4.1. December 15, 2004 Preliminary 01.11. Addresses CRs Q01022218, Q01042647, Q01020435. Added Appendix A: GGSNS3.2.X to GGSNS4.0 patch application. December 3, 2004 Preliminary 01.10. Addresses CRs Q01029449, Q01037743, and Q01004689. November 23, 2004 Preliminary 01.09. Merged the day 3 and day 1 checklist with day 2 check list. Also addressed CRs Q01000036, Q01029334, Q01029502, Q00999960, Q01029449, and Q01029334. November 15, 2004 Preliminary 01.08. Added 3.1.3 patching procedures and addressed many comments from internal review. November 6, 2004 Preliminary 01.07. Addressed CRs CR Q01021311 for SCS, Q01021298, redirect traffic before the resync and start it after the resync. October 29, 2004 Preliminary 01.06. Addressed CRs Q01004697, Q01004697, Q00993122, Q01004697, and updates resulting from lab trials. October 26, 2004 Preliminary 01.05. Addressed CRs Q00993122 and Q01004689.
GPRS/UMTS
16
Publication history
October 22, 2004 Preliminary 01.04. Addressed CRs Q00991056, Q00991081, Q01004263, Q01001579, Q01000036, Q00999960, Q00999934, Q00990980. September 20, 2004 Preliminary 01.03. Made corrections to software optionality control and checklists. September 13, 2004 Preliminary 01.02. Replaced the updated Pre-upgrade checklist and SCS and GPRS upgrade chapters. September 9, 2004 Preliminary 01.01. First preliminary release for PC04. Addressed CRs Q00968835, Q00972814, and Q00972791; added note to Full system backup and restore system requirements section stating requirement that all components of SCS Server, (LDAP, domain server, region server) be installed on the same physical server. August 18, 2004 Draft 01.00E. Replaced the updated SCS and GPRS upgrade chapter. August 11, 2004 Draft 01.00D. Replaced the updated Pre-upgrade checklist and SCS and GPRS upgrade chapters. July 29, 2004 Draft 01.00C. Added Pre-upgrade checklist chapter. Also addressed CRs CRQ00937607, Q00938598, Q00943472. July 16, 2004 Draft 01.00B. Updated to address Q00865564-01, and other issues discovered in internal review. June 2004 Draft 01.00A; manual given its own NTP number (411-5221-309), and rev number reflects this (restarting it at 01.00A). Upgrade chapter updated by Design Group. May 2004 Draft 07.00A; new issue for GPRS 6.0 / UMTS 4.0. Manual split into multiple (5) volumes, each reflecting upgrade procedures and considerations for an individual node. This is volume 4 (GPRS /UMTS SCS and GGSN).
411-5221-309 Standard 06.30 March 10, 2010
Publication history
About this document

Purpose 11 Audience for this document 11 Documentation roadmap 11 Related documents 13 Special text conventions in this document SCS Text Convention 14
11
14
GGSN 6.0 Upgrade Overview and New Install Overview

General Upgrade Information 15 SCS Support on Sun Netra T5220 16 Packet Core Upgrade Order 16 Upgrade order rationale 16 Upgrade order and dependencies 16 Hardware Requirements for SCS 19 SCS Upgrade Overview 20 SCS Rolling Upgrade: 21 GGSN Upgrade Overview 21 SCS Migration or New Installation on Sun Netra T5220 22 Backward Compatibility 22 SCS and GGSN Load Lineup 23 Software delivery methods 23 Acquiring GPRS Packet Core software for the CS-LAN 24 SCS Software Delivery 24 Preparing the SCS software file for an upgrade with ESD 25 GGSN Software Delivery 27 Preparing the GGSN software file for an upgrade with ESD 29
15
GGSN/SCS pre upgrade checklists

Pre-upgrade checklists 31 Upgrade readiness checkpoint #0 28 days prior to upgrade 32 Upgrade readiness checkpoint #1 14 days prior to upgrade 35 Upgrade readiness checkpoint #27 days prior to upgrade 41 Upgrade readiness checkpoint #32 days prior to upgrade 44 Upgrade readiness checkpoint #4night before the upgrade 46 Checklist work instructions and details 48
31
SCS Upgrade Overview

SCS and GGSN Load Lineup 135 SCS Text Convention 135 SCS Installation Directories 136 Symbolic Link 137 Overall upgrade strategy for SCS 138 SCS upgrade / Rollback options 139 Overall Rollback Strategy 140 Supported SCS upgrade scenarios 140 SCS server upgrade at a high level 140
135
SCS server preparation: Migration of the current SCS to new

Publication history
hardware or New Install of SCS on new hardware

Before installation 142 Network requirements for LDAP/SCS: 142 Hardware Requirements for SCS 143 System settings needed 143 Disk partition sizing 144 Overview of SCS New Install and Migration procedure
142
144
SCS Upgrade Prechecks

Prechecks prior to starting SCS upgrade 146
146 161
SCS Upgrade on the Same Physical Server

Upgrade SCS from 4.1.2 to SCS 6.0 161 Overview 161 Upgrade SCS from 5.0.2 to 6.0 166
Migrating SCS to a new physical server with Same or Different IP address 169 Database backup and restore procedures for migrating to a new physical server 181
Database backup procedure for SCS migrating to a new physical server 181 Backup Solid Database 182 Backup LDAP database 184 Database restore procedure for SCS migrating to a new physical server 189 LDAP (or iPlanet) database modifications on the new SCS server 191 Database Restore on the new SCS server 194
Basic SCS system administration

Basic SCS Server Maintenance 199 Basic system settings required on the SCS: 199 Determine SCS and LDAP/ iPlanet installation directories 200 Start SCS server. Enable SCSWatch and LDAPWatch 200 Stop SCS server. Disable LDAPWatch 202 Enable LDAPWatch 203 Disable LDAPWatch 204 Disable SCS provisioning 204 Enable SCS provisioning 204 Check SCS provisioning status 204 Start the LDAP / iPlanet server. Enable LDAPWatch 204 Disable LDAPWatch. Stop the LDAP / iPlanet 205 Verify and Stopping SCS server and LDAP server processes 207 Verify LDAP/ iPlanet server and admin process status 208 To login to iPlanet admin console and verify iPlanet server performance parameter: 208 Rebooting the SCS server 209 Rebooting the SCS server to single user mode 209 Modifying LDAP backup in case of server domain name change 210 Resetting LDAP/ iPlanet Root DN name and password 211 411-5221-309 Standard
199
06.30 March 10, 2010
Publication history
To verify and if needed, reset Root DN and its password 212 SOC key update procedure 214 SOC key delete procedure 216 Understanding Sun hard disk naming convention 217 Modify SCS server IP address or hostname 217 Modify SCS server domain name 219 Verify the SCS server umask settings 220 Fixing Solaris error - getexecname() failed 221 Fixing - unable to eject CDROM from drive 222 Add or Verify SOC key 222 Verify patch status information 223 SCS Periodic Backup setup option 224 Resolve SCS server login issue in case of incorrect shell path 226 Swap memory space allocation 227 SCS and iPlanet auto startup scripts 229 SCS data collection during SCS server migration 230
Database backup and restore procedures

SCS backup/ restore options 232 Option 1: SCS backup/ restore using tar 232 Stop SCS and LDAP server processes before starting the backup Perform a tar backup 233 Restart LDAP (or iPlanet) and SCS processes 236 Restore Procedure for the tar backup 237 Restore SCS 4.1.2, SCS 5.0.2 and SCS 6.0 238 Option 2: SCS backup using SCSAdmin 241 FTP the backup to a remote server 243 Option 3: Perform Tape Backup Restore Procedure 244 232
232
SCS Software Upgrade

Upgrade SCS 4.1.2 to SCS 6.0 245 SCS 4.1.2 to SCS 6.0 upgrade details 246 Disable SCS 4.1.2 provisioning 251 Perform a SOLID database backup 252 Executing rollingSCS.sh procedure 252 Verify SOLID database integrity 256 Execute SCS Upgrade script - setup.sh 257 Verify SCS Upgrade logs 266 Change the pmuser password 267 Execute ns_server_secure.sh script 268 Login to iPlanet administration console 269 Enable SCS and iPlanet auto startup scripts: 270 Optional - Install SSL Package 271 Upgrade GGSN SCS from 5.0.2 to 6.0 273 SCS 5.0.2 to 6.0 upgrade details 274 Disable SCS 5.0.2 provisioning 279 Perform a SOLID database backup 279 Executing rollingSCS.sh procedure 280 Verify SOLID database integrity 283 Execute SCS 6.0 Upgrade script - setup.sh 285
245
GPRS/UMTS
Upgrade Manual
GGSN6.0
Publication history
Verify SCS upgrade logs 290 Change the pmuser password 292 Stop SCS 5.0.2 processes and start SCS 6.0 server processes Enable SCS and iPlanet auto startup scripts: 296 Optional -Install SSL Package 296
292
Modify partition level file permissions SCS Post-upgrade / Rollback checklists
299 303
Post Upgrade checkpoint #5 303 Upgrade readiness checkpoint #6after it is determined the SCS server will not be rolled back to Solaris 8 307 Checklist work instructions and details 308 Checklist work instructions and details 342
Procedure for Changing the SCS server IP address

Changing SCS configuration 346
346 347
OS Hardening of GGSN SCS Server

Packaging 347 Pre-work 347 Upgrading OS hardening software on the SCS server 348 Installing OS hardening software on SCS server 348 OS hardening procedures 352
OS unhardening procedure on Solaris 8 SCS Client upgrade procedures
353 354
SCS client installation 354 SCS Client Installation for Windows 2000 and XP (older that version 2002) 354 SCS Client Installation for Windows 2003 server 354 SCS Client Installation for XP (version 2002 or later) and Vista 355 SCS Solaris Client Installation 355 SCS client rollback 356 356 SCS client rollback on Windows 2000 and XP (older that version 2002) 356 SCS client rollback on XP (version 2002 or later), Window 2003 and Vista 357 SCS client rollback on Solaris 357 Enabling SSL on the SCS Client 357 Enabling SSL on SCS Windows Client Machine 357 Enabling SSL on the SCS Unix Client Machine 358
OS hardening of SCS client machines

Client hardening 361
361 362 372
Rollback SCS 6.0 to SCS 4.1.2 after Solaris 9 Upgrade SCS 6.0 to SCS 5.0.2 Rollback procedure
411-5221-309
Standard
06.30 March 10, 2010
Publication history
Clean up procedure in case of upgrade failure for SCS 4.1.2 to 6.0 upgrade 378 Clean up procedure in case of upgrade failure for SCS 5.0.2 to SCS 6.0 381 Backup and Restore Procedures for SCS with a Tape Drive
Local backup 384 Backing up essential data to tape 384 Backing up dynamic data to tape 384 Backing up the full system 384 Local Restore 384 Restoring essential data 384 Restoring dynamic data 385 Restoring the full system 385 Centralized backup 385 Installing the VERITAS client software 386 Performing a backup 387 Configuring a backup policy 387 Centralized restore 389 Performing centralized restore 389
383
Full System backup and restore

Full system backup and restore system requirements 393 Full system backup and restore resource needs 393 Impact of full system backup and restore 393 Installing the backup and restore software package 394 Installation of backup and restore software package 395 Removal of backup and restore software package 398 Performing a full system backup 398 Perform SCS and LDAP/ iPlanet backup 398 Stopping the SCS applications 399 Full server backup procedure 401 Restart the SCS applications 405 Performing a full system restore 406 Log on in single user mode with the Solaris system CD ROM Restore the SCS 408 Start the SCS applications 411
392
407
Solaris 9 Boot Environment Creation

Creating a Boot Environment (BE) For Solaris 9 413 Understanding Sun hard disk naming convention 413 Identify the Partitions for Solaris 9 Boot environment 413
413
Deleting the Boot Environment
443
Delete Solaris 8 Boot Environment and Reuse Solaris 8 partitions on Solaris 9 444
Publication history
Copy the upgraded SCS 6.0 from Solaris 8 to Solaris 9

Perform BE copy 446 Verify successful completion of SCSBECopy.sh 448
446
Install Recommended Patches for Solaris 9 and Solaris 10
451
Upgrade GGSNS4.1.1 to GGSNS6.0 on Two servers with same IP address 454 Upgrade GGSNS5.0.1 to GGSNS6.0 on Two servers with same IP address 469 Steps to recover from Solid database corruption issue
Problem Description 481 Steps to resolve solid database corruption 481 Steps if solid database integrity check passes 483 Steps if solid database integrity check fails 483
481
GGSN Software Upgrade GGSN Pre-Upgrade Procedure

GGSN Pre-Upgrade Procedure duration Steps before GGSN upgrade 495 495
493 495
GGSN Upgrade Procedure

GGSN upgrade options 521 GSGN Upgrade Steps 521 Reject GGSN incoming traffic 522 Update CMC bootrom firmware 524 Upgrade to GGSN 6.0 software 533
521
GGSN Post-Upgrade Procedure

GGSN Post-Upgrade Procedure duration Steps after GGSN upgrade 541 541
541
Optional Post-Upgrade Procedures

New feature provisioning/activation 545 GGSN Hardware Upgrade 545 GGSN 4.1.1/GGSN 5.0.1 Patch Removal Health Check Monitoring 545 545
545
GGSN Rollback procedure

Software rollback procedure 547
547 554
554
GGSN Upgrade Follow-up

System Monitoring checkpoint GGSN upgrade follow-up 411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential Checklist work instructions and details 555
Publication history
GGSN miscellaneous Operations

Change the GGSNs SCS IP address Resync with iSOS Ver. 572 571
571
Appendix A: GGSN SOC

Software Optionality Control (SOC) SOC Feature Activation 577 577
577
Appendix B: Recovery Procedure

Fault recovery 28 583 Backup the qs1 ispdb.cfg file 583 Recovery of management ports with backup-up ispdb.cfg file 584 Recovery of management ports without a backup-up ispdb.cfg file 584
581
Appendix C: Unmirroring the File Systems
586
Appendix D: Creating a Partition on a New Disk for Disk Mirroring 600 Appendix E: Creating Mirrors 609
Appendix F: Performing Backup and Restore of Mounted Noncritical File Systems for Mirrored Servers 627 Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name 633 Appendix H: Example capture of iPlanet server uninstallation 656 Appendix I: Disk Check for SCS for non-mirrored servers Appendix J: Disk Check for SCS for mirrored server Appendix K: Disk Analysis For Non-Mirrored Servers
Disk Space Analysis 666 Identifying Unmounted Partitions required for Solaris 9 Boot Environment (BE) Creation 668 Steps to identify unmounted disk on the SCS server 668 Disk Partitioning of an Unmounted Disk 670
661 664 666
Appendix L: Procedure to mirror a server in case metadb partition is not assigned 676
Pre-requisites 676 Procedure Overview 676 Detailed Procedure 677
GPRS/UMTS
Upgrade Manual
GGSN6.0
Publication history
Appendix M: Updating server eeprom

Detailed Steps 685
685
Appendix N: Using format utility to modify the partition flag 687 Appendix O: Procedure to modify SCS server IP, host name or domain name 689
Terminologies 689 Pre-requisites 689 Overview of the procedure Detailed Procedure 692 691
Appendix P: Perform a SCS 6.0 new install

Install Procedure 704
704 714
Appendix Q: Fast Feature Migration Script examples

G501_FF01435785ACT_INF - L2TP Cabcharge 714 Manual SCS Pre-upgrade steps 714 Manual SCS post upgrade script execution 715 SCS post upgrade script execution 715 G501_FF01567650ACT_IPCMC - TCP MSS Clamping 717 Manual SCS Pre-upgrade steps 717 SCS post upgrade script execution 718 G501_01407739ACT_INF and G501_01595094AACT_AAA 719 Manual SCS post upgrade script execution 719 SCS post upgrade script execution 719 SGSN Change Partial Billing - G411_01339974AACT_GTPACCT 721 Manual SCS post upgrade script execution 721 SCS post upgrade script execution 722 Consecutive Parking Meter feature 723 SCS post upgrade script execution 723
Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs

.inputparms_upgrade.scs 735
727 745 764
Appendix S: Solaris 10 Installation

Solaris 10 New Installation Example 746
Appendix T: Perform SCS 6.0.1 new installation

Initial Server Configuration Install Procedure 765 764
Appendix U: SCS 6.0.1 Database Migration Example

SCS and iPlanet backup example for move to a new SCS server SCS and iPlanet restore example 779 777
777
411-5221-309
Standard
06.30 March 10, 2010
Publication history
Appendix V: Log captures for SCS Full Server Backup and Restore 783
Full Server Backup 783 Full Server Restore for Mirrored Servers on Solaris 8 Full Server Restore for non-mirrored servers 833 797
List of figures
Figure 1-1 Figure 2 Figure 1 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 GPRS/UMTS Packet Core Network documentation roadmap 12 Software order and ESD delivery overview 24 ISP Firewall rule related to RADIUS 103 SCS Upgrade Strategy for upgrade from SCS 4.1.2 to SCS 6.0 138 SCS Upgrade Strategy for upgrade from SCS 5.0.2 to SCS 6.0 138 Resetting LDAP/ iPlanet Root DN and password 213 Setting server IP address to new server 346 GGSN Upgrade Strategy 493 Resync with iSOS functionality 573 Device Maintenance window 574 Resync confirmation window 575 Modify SCS server IP in SCS Server Properties 701
List of tables
Table 1 Table 2 Table 3 Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Third party software upgrades 21 Backward compatibility information 22 SCS and GGSN Load Lineup 23 Upgrade readiness checkpoint #0 28 days prior to upgrade 32 Upgrade readiness checkpoint #1 14 days prior to upgrade 35 Upgrade readiness checkpoint #2 7 days prior to upgrade 41 Upgrade readiness checkpoint #3 2 days prior to upgrade 44 Upgrade readiness checkpoint #4 night before the upgrade 46 Disk Mirroring Mapping for Critical File Systems 70 Disk Mirroring Mapping for Non-critical File Systems 70 Example Disk Mirroring Mapping for Critical File Systems 71 Example Disk Mirroring Mapping for Non-critical File Systems 71 metadb partition table 73 Example metadb partition table 73 Recommended SCS server software disk space 144 Partition table for T5220 144 Upgrade SCS 4.1.2 to SCS 6.0 on same server 162 Rollback SCS 6.0 to SCS 4.1.2 on same server 165 Upgrade SCS 5.0.2 to SCS 6.0 on same server 166 GGSNS6.0 to GGSNS5.0.1 on Same Server Roll-back 168 Migrating SCS server to new server, same IP address upgrade procedures (includes T5220 migration) 171 Migrating SCS server to new server, same IP address or different IP, roll-back procedures 179 Upgrade readiness checkpoint #5 every day after the upgrade for 7 days 303 Upgrade readiness checkpoint #6 after it is determined the SCS server will not be rolled back to Solaris 8 307 GPRS/UMTS Upgrade Manual GGSN6.0
10
Publication history Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 Table 34 Table 35 Table 36 Table 37 Table 38 Table 39
Nortel Networks Confidential Supported hardware for full system backup and restore 393 Basic SCS server backup steps and timings 398 Basic SCS server restore steps and timings 406 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures 455 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures 470 GGSN pre-upgrade procedure timing 495 GGSN upgrade procedure 521 GGSN post-upgrade procedure timing 541 System Monitoring checkpoint 554 Example disk mirror map for critical file system 586 Example disk mirror map for non-critical file system 586 Partition Information for Non-Mirrored Servers 667 Example of Partition Information for Non-Mirrored Servers 667 Disk Partitions assigned for the non-mirrored server 679 SCS 6.0 .inputparms_install.scs File 727 SCS 6.0 .inputparms_upgrade.scs 737 Partition table for the Sun T5220 745 Partition table for the Sun T5220 758
411-5221-309
Standard
06.30 March 10, 2010
11
About this document

Purpose
The intent of this document is to provide a set of step-by-step upgrade procedures for the GPRS/UMTS SCS and GGSN. Both hardware and software upgrade procedures are described.
1
1
This document provides a detailed description of the various SCS and GGSN software and hardware upgrade procedures for GGSNS6.0.
Audience for this document

This document is intended for personals involved specifically in the maintenance and upgrade of GPRS/UMTS systems and networks. It is assumed that the reader has practical experience with GPRS/UMTS networks and standards, competency in the terminology and concepts, and competent, hands-on experience in UNIX operating system, and the configuration of GPRS/UMTS node equipment.
Documentation roadmap
Figure 1-1 lists all GPRS/UMTS Packet Core Network user documentation arranged by category (Concepts, Planning and Engineering and so on). When searching for specific kind of information, use this figure to identify the document you need.
GPRS/UMTS
Upgrade Manual
GGSN6.0
12
About this document
Figure 1-1 GPRS/UMTS Packet Core Network documentation roadmap

Concepts Planning and Engineering Upgrading Installation and Commisioning Operations and Administration Fault and Performance Management
Packet Core Documentation 411-5221-004 About the UMTS Network 411-8111-502 Terminology 411-8111-804 GGSN RADIUS Interface Guide 411-5221-928 SGSN/UMTS User Guide 411-8111-903 GGSN User Guide 411-5221-926 SGSN/GPRS User Guide 411-5221-955 SIG User Guide 411-5221-975
GGSN, SCS Delta 411-5221-200 SGSN, SIG Delta 411-5221-202 Packet Core Conformance Guide 411-5221-201 SGSN Call Detail Records 411-5221-204 SGSN Billing Samples 411-5221-205 GGSN Billing Samples 411-5221-206 SGSN/UMTS User Guide 411-5221-903 GGSN User Guide 411-5221-926 SGSN/GPRS User Guide 411-5221-955 SIG User Guide 411-5221-975 Corbashell CLI Guide 411-5221-929
Packet Core Upgrade Strategy 411-5221-303 SIG Upgrade 411-5221-306 SGSN/GPRS Upgrade 411-5221-307 SGSN/UMTS Upgrade 411-5221-308 SCS & GGSN Upgrade 411-5221-309
SGSN Provisioning Procedures 411-5221-904 GGSN Provisioning Procedures 411-5221-927 GGSN H/W Install & Maintenance 411-5221-923
SGSN/UMTS Customer User Guide Documentation 411-8111-903 411-5221-003 GGSN User Guide 411-5221-926 SGSN/GPRS User Guide 411-5221-955 SIG User Guide 411-5221-975 GGSN CLI Guide 411-5221-922 GGSN Provisioning Procedures 411-5221-927 Corbashell CLI Guide 411-5221-929
GGSN Monitoring Guide 411-5221-924 SGSN/GPRS Monitoring Guide 411-5221-050 SGSN/UMTS Monitoring Guide 411-8111-050 SGSN Components 411-5221-060 SGSN Alarms 411-5221-500 GGSN Alarms 411-5221-921 Core Network Troubleshooting Guide 411-5221-501 SGSN/UMTS User Guide 411-8111-903 GGSN User Guide 411-5221-926 Corbashell CLI Guide 411-5221-929 SGSN/GPRS User Guide 411-5221-955 SIG User Guide 411-5221-975
411-5221-309
Standard
06.30 March 10, 2010
About this document
13
Related documents
Nortel, GGSN and SCS Delta Document; 411-5221-200 GGSN Release Notes for the current and upgradable GGSN software version Specifications for UMTS/GPRS Packet Core Conformance Guide; 411-5221-201 Nortel Call Detail Record Manual; 411-5221-204 Nortel GGSN Billing Samples; 411-5221-206 Please review latest versions of Nortel GGSN bulletins
Please refer to the Day Light Savings time bulletins if your region (United States or Western Australia) recognized an adjustment in the official time change date to March 2007 - 2006007540 and 2007007769. Sun recommended Solaris patches for Live Upgrade - Sun information document number 72099 from SunSolve web site http://sunsolve.sun.com Nortel, SGSN/GPRS Upgrade Manual; 411-5221-307 Nortel, SGSN/UMTS Upgrade Manual; 411-5221-308 Nortel, SS7/IP Gateway (SIG) Upgrade Manual; 411-5221-306 Nortel, Online Documentation - Preside MDM Engineering Guide, 2416001-100 Nortel, GPRS 6.0 UMTS 4.1.1 GGSN CLI Guide; 411-5221-922 Nortel, GPRS 6.0 UMTS 4.1.1 GGSN User Guide; 411-5221-926 Nortel, GPRS 6.0 UMTS 4.1.1 GGSN Provisioning Procedures; 411-5221-927 Nortel GGSN Corbashell CLI Guide, 411-5221-929 Nortel, GGSN Hardware Installation and Maintenance Guide, 411-5221923 Nortel, Passport 15000 Site Requirements and Preparation Guide, 2411501-205 Nortel, Passport 15000 Hardware Installation Guide, 241-1501-210 Nortel, Passport 7400 Hardware Installation Guide, 241-7401-210 Nortel, Passport 7400, 15000 Software Installation Guide, 241-5701-270 Patch Application Document (PAD) 85-8990 UMTS 3.0.1 Patch Baseline Upgrade. The PAD can be accessed by going to: http://gis.us.nortel.com/portal/home.shtml or http://www.nortel.com/index.html
14
About this document
Special text conventions in this document

The names of published documents are displayed in Italics (as displayed here). In this guide, CLI commands to be entered are shown in Courier bold font. CLI output is shown in Courier plain. CLI variables are shown <in_italics_and_enclosed_in_angle_brackets>. Hypertext links or URLs within this document are displayed as blue text.
SCS Text Convention The SCS upgrade procedures in this document show example command input and output. It may not match your installation exactly. When a command or a parameter must be entered by the user, the command or parameter is shown in bold text. For example, to change directory to the location of the scs.config file, use: # cd /etc/shasta The # character is used as the default Unix command prompt. When an installation-specific parameter is required, the parameter is enclosed in angled brackets. Use the value appropriate to your installation without the angled brackets. An example of entering a parameter is: IP Address of host: <host IP address> where the host IP address is 10.1.23.3 would be entered: IP Address of host: 10.1.23.3
411-5221-309
Standard
06.30 March 10, 2010
15

General Upgrade Information
This document provides the upgrade paths for the GGSN and SCS components for the following software releases: GGSNS4.1.1 to GGSNS6.0 GGSNS5.0.1 to GGSNS6.0
2
2
Please refer to table SCS and GGSN Load Lineup on page 23 on actual load names in different releases. Note: Throughout this document, there are references to GGSNSX.X.X (example: GGSNS6.0). GGSNSX.X.X refers to both GGSN and SCS (GGSN 6.0 with SCS 6.0). The GGSN 6.0 SCS can manage GGSN 6.0, 5.0.1, 5.0 and 4.1.1. The SCS server is upgraded first, then the GGSNs are upgraded. GGSN SCS 6.0 supports Rolling Upgrade where the SCS upgrade is performed while the current SCS software is in service. During certain SCS upgrade activities, GGSNs cannot be configured or monitored through the SCS. However, GGSN traffic is unaffected. Each GGSN will go out of service while its software and configuration data is upgraded. To minimize service impact, the GGSNs can be upgraded one at a time. The rest of the chapters in this document contain the following information: SCS and GGSN pre-upgrade checklist. SCS Server and SCS Client upgrade procedures. SCS Server and SCS Client rollback procedures. GGSN bootrom and software upgrade procedures. GGSN rollback procedures.
GPRS/UMTS
16
SCS Backup/ Restore options Solaris operating system hardening
SCS Support on Sun Netra T5220
The SCS now supports the Sun Netra T5220 Server. The T5220 only supports Solaris 10, and is shipped with Solaris 10 already installed. There is no DAT drive shipped with the T5220. If transitioning an existing SCS server to the new T5220 hardware the high level process is to install Solaris 10 operating system on the new T5220, perform a new install of SCS 6.0.1 application software, copy over the data, and bring into service. This document also provides details of Solaris 10 new installation, SCS 6.0.1 new installation on Solaris 10 and backup migration procedure to the new server.
Packet Core Upgrade Order
Upgrade order rationale During the network upgrade process, while some network components are being upgraded to Packet Core 6.0, there will be other nodes that have already been upgraded to Packet Core 6.0, and some nodes still running on Packet Core 5.x or 4.x software version and are yet to be upgraded. This results in a situation where network nodes running different software versions have to interact to provide service. Keeping this in mind, a network order of upgrades is recommended in this section. All network components should be upgraded in this recommended order to ensure conformance to Backwards Compatibility limitations, to minimize the risk of service downtime, and to ensure optimal service availability. Upgrade order and dependencies The diagram below highlights the high-level network order of upgrade. The following discussion outlines some general considerations as well as specific comments about the upgrade of different network components.
411-5221-309
Standard
06.30 March 10, 2010
17
Step 0:
Functional Packet Core 4.X/ 5.X network
Step 1:
OAM Upgrade Step 1.1: Main/Perf. server - W-NMS 5.0.1.3 Step 1.2: Server of Client Step 1.3: Policy Services Step 1.4: CGF
Step 2:
Packet Core Upgrade Step 2.1: SCS Step 2.2: GGSN Step 2.3: SIG Step 2.4: SGSN/UMTS
Step 3:
Functional Packet Core 6.0 network
General notes about upgrade The comments below are applicable to upgrade of each network component Pre-upgrade checks - Ensure that all prerequisite hardware changes, if any, and software loads have been obtained prior to starting the upgrade. Ensure that appropriate backups and data reformatting are completed in advance to reduce the risk of starting an upgrade and then aborting. A detailed pre-upgrade checklist can be found in GGSN/SCS pre upgrade checklists on page 31.
GPRS/UMTS
18
Post-upgrade checks - At every step during network upgrade, a suite of critical calls test cases should be executed to verify network sanity. A suite of regression, sanity and backwards compatibility test cases should also be executed. This will help identify issues as soon as they occur and will help in making decisions to rollback the network components to a steady sane state instead of proceeding on with the upgrades. A detailed post-upgrade checklist can be found in the corresponding SCS and GGSN upgrade chapters. Inter-vendor compatibility - The order of upgrades discussed in this section is the recommended order for Nortel networks elements. If there are any non-Nortel NEs used in the customer network, consult with the appropriate vendors for compatibility summary before performing any upgrades.
Discussion of order of upgrades Step 0 - Functional Packet Core 5.X, 4.X network Execute all pre-checks. Execute network sanity verification test cases. At this point, an upgrade plan should be in place that has identified the nodes that will be upgraded and those that will not. This also impacts the customers management and backend systems including billing systems, which may be impacted by new billing and OAM formats. All documents and templates necessary for the upgrade must be available at this point. Step 1 - OAM Upgrade The OAM components monitor all the other nodes in the network. Therefore these network components must be upgraded first. It is assumed that any upgrades to the network IP/ATMs will happen at this point. The OAM network components should be upgraded in this order Step 1.1 - Main Server and Performance Server Main Server and Performance Server should be upgraded at the same time, during the same maintenance window. Step 1.2 - Server of Client (SOC) The use of SOC in a OAM network is optional. However, if a SOC is being used in the customer OAM network, the server should be upgraded at this point. Step 1.3 - Policy Services (including DNS, DHCP, and RADIUS) Step 1.4 - CGF (Billing Server) Nortels CGF solution is capable of supporting multiple Call Data Record (CDR) formats simultaneously. Under normal conditions the CGF should
411-5221-309 Standard 06.30 March 10, 2010
19
be upgraded with the OAM network. Note that the SGSNs and the GGSNs all send CDR information to the CGF. The SGSN and GGSN have configuration flags that control which billing format is sent to the CGF. After upgrading the SGSN these flags can be changed on all relevant nodes. It should also be confirmed that the customers back end systems are prepared for the new billing formats. After upgrading the CGF, confirm that the CGF operates properly and processes billing records of different formats. Step 1.5 - LIG
Step 2 - Packet Core upgrade Packet Core network components must be upgraded in this order Step 2.1 - SCS The SCS must be upgraded before the GGSN. The SCS is not forwardcompatible with GGSN, therefore SCS must be upgraded first, followed by GGSN. Step 2.2 - GGSN The GGSN upgrade is out of service so to avoid an outage to the endusers, the GGSN to be upgraded must be flagged as unavailable and traffic must be routed to another GGSN during the upgrade. Step 2.3 - SIG Step 2.4 - SGSN After upgrading the SGSN, new message formats and billing versions can be enabled on the CGF, HLR, GGSN, and SGSN. Step 3 - Functional Packet Core 6.0 network Execute all post-checks. Execute network sanity verification test cases. At this point, all network components should be on Packet Core 6.0 release software. Verify end to end functionality on the new software release.
Hardware Requirements for SCS

The following is the nominal SCS requirements. The SCS runs on a Sun Microsystems server. Suns offerings are continuously changing, and Nortel is continually evaluating these offerings. Contact your Nortel Account team to determine the optimal recommended and supported solution for your network.
GPRS/UMTS
20
The supported hardware and minimum recommended hardware configuration is: SunFire V890, SunFire V880, SunFire V250, Netra 240 Note: Sun E250 and E450 hardware platforms are not supported for GGSNS6.0. 4 gigabytes memory
Optional: 20GB 4-mm DDS-4 internal/ external tape drive

There are five scenarios for SCS upgrade: SCS Upgrade on the same physical server without Solaris server disk mirroring SCS Upgrade on the same physical server with Solaris server disk mirroring Migrate GGSNS6.0 to a new physical server with a different IP address Migrate GGSNS6.0 to a new physical server with the same IP address SCS Upgrade on two physical servers with same the IP address
Similar pre-upgrade checklists are applied to the above scenarios. The supported operating system for GGSNS6.0 SCS is Solaris 9. GGSNS4.1.1 to GGSNS6.0 SCS upgrade includes a Solaris 9 upgrade. GGSNS5.0.1 to GGSNS6.0 upgrade may not require Solaris 9 upgrade as the SCS server should already be running Solaris 9. Solaris upgrade for non-mirrored servers requires at least one free, unassigned disk partition for every critical file system (/, /var, /usr, /opt) of at least 4 GB plus the space currently occupied by the current mounted file system. In case a free and unassigned disk partition is not available, Nortel recommends using a separate disk for this purpose. Solaris upgrade for mirrored servers require unmirroring the disk partitions. The recovered partition from unmirroring the server on Solaris 8 is used as partitions for Solaris 9. The server will be remirrored after the SCS and GGSN upgrade and post-check steps are completed. All the required third party software needs to be upgraded to align with Solaris 9. SCS software upgrade takes care of upgrading the third party software. Table 1 lists all the third party software that will be upgraded.
411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential Table 1 Third party software upgrades Third Party Software (current version) AdventNet SNMP 2.0 Visibroker 4.0 JRE 1.2.2 Directory Server for SCS 4.1.2: LDAP 4.16 Directory Server for SCS 5.0: iPlanet 5.1 Certicom SSL 1.1.19
21
Third Party Software (new version) AdventNet SNMP 4.0 Visibroker 6.0 JRE 1.4.2 Directory Server: iPlanet 5.1
Certicom SSL 3.1.19
SCS Rolling Upgrade: In GGSN 6.0 SCS, the user can use the functionality of SCS Rolling upgrade. Rolling upgrade reduces the loss of service time by setting up rolling directories where the upgrade is performed while the actual servers are running. Rolling upgrade reduces the loss of service time by obviating the need to stop the servers during upgrade. It creates a duplicate directory of the existing SCS and LDAP servers. So once the rolling setup is performed, an upgrade of these duplicate SCS server and directory server will ensure that there is no service loss. During the SCS server upgrade, users must execute the rollingSCS.sh and then setup.sh scripts. The setup.sh script will display the parameters that will be set for SCS 6.0 and obtain confirmation from the user. Once the confirmation is given, the SCS upgrade will continue without any further interaction from the user.
GGSN Upgrade Overview
The GGSN 6.0 software upgrade is performed after the SCS server has been upgraded to SCS 6.0. The GGSN 6.0 is backward compatible with Packet Core 5.X and 4.X Nortel SGSN for the GTP messaging interface. The GGSN 6.0 supports GTP version 0 with 3GPP R98 compatibility and GTP version 1 with 3GPP Rel-4, Rel-5 and Rel-6 compatibility. If a CMC2 to CMC3 or SFC1 to SFC2 hardware upgrade is also required during the GGSN 6.0 upgrade, the GGSN 6.0 software upgrade is required to be completed before the hardware upgrade can occur. Please refer to Nortel GGSN Hardware Installation and Maintenance Guide, 411-5221-923 for more information about the optional CMC2 to CMC3 and/or SFC-1 to SFC-2 hardware upgrade. After the GGSN upgrade, new features on the GGSN can be provisioned via SCS GUI configuration or activated via Software Optionality Control (SOC). It is recommended that new features should not be configured or activated on
GPRS/UMTS
22
SCS before SCS and at least one GGSN using those features are both upgraded.
SCS Migration or New Installation on Sun Netra T5220

SCS supports 2 options.
Server migration: An existing SCS running SCS 4.1.2 or SCS 5.0.2 can be migrated to the Sun Netra T5220 platform. Detailed instructions are provided in section on page 168. New SCS installation: SCS can directly be installed on the Sun Netra T5220. In both cases, the following steps must be completed in the same order. Perform Solaris 10 new installation and update the system with the latest Solaris recommended patches. Please refer to Appendix S: Solaris 10 Installation on page 745 Install SCS 6.0.1 on the Solaris 10 server. Please refer to Appendix T: Perform SCS 6.0.1 new installation on page 764 In case of SCS migration, the backup from the old server is restored on the new SCS server. GGSNs are then migrated to the new SCS server.
Backward Compatibility
Table 2 describes the backward compatibility information for the SCS and GGSN. The GGSN 6.0 upgrade is N-2 compatible.
Table 2 Backward compatibility information GGSN Version SCS Version GGSNS4.1.1 GGSNS5.0.1 GGSNS6.0 GGSNS4.1.1 Compatibility Yes Yes Yes GGSN 5.0.1 Compatibility No Yes Yes GGSN 6.0 Compatibility No No Yes
411-5221-309
Standard
06.30 March 10, 2010
23
SCS and GGSN Load Lineup

Table 3 SCS and GGSN Load Lineup Release GGSNS4.1.1 GGSNS5.0.1 GGSNS6.0 GGSNS6.0 SCS GGSNS4.1.2_SCS5.0(1) GGSNS5.0.2_SCS5.0(14) GGSNS6.0_SCS6.0(47) GGSNS6.0.1_SCS6.0(1) GGSN ggsns4.1.1-iSOS-build-9 ggsns5.0.1-iSOS-build-17 ggsns6.0i-isos-build-61 ggsns6.0i-isos-build-61
Software delivery methods
Customers receive the GPRS Packet Core software either through electronic software delivery (ESD) or manufactured on physical media, such as a compact disk (CD). The physical media is delivered by courier to the customer site. The Galaxy ESD tool accommodates global software delivery using business-to-business processes and automated electronic distribution of Nortel products to customer locations. The following figure shows a highlevel example of how the software is released to the customer site through ESD.
GPRS/UMTS
24
Figure 2 Software order and ESD delivery overview
Acquiring GPRS Packet Core software for the CS-LAN
Software for the GPRS Packet Core is stored in the Nortel Networks Software Vault. The Software Vault is a repository for maintaining and distributing controlled copies of software loads to Nortel customers. The Software Vault provides the following benefits: version control access control query and persistency capabilities using a distributed multi-client, multi-server architecture transaction control
SCS Software Delivery
The SCS related software is delivered via Electronic Software Delivery (ESD) or a SCS software package CD. The folders on the SCS CD correspond to the target operating systems and contain the software delivered for that target operating system: Solaris: contains the SCS Server and other software to run on Solaris (version 9). NNXMLGGSN.pds.gz cmxml_toms_patch.tar NNoshscs.pds.Z - (Operating system Hardening) NNBRSCS.pds - (Full Server Backup and Restore) directory-5[1].1sp3-us.sparc-sun-solaris2.8.tar (iPlanet 5.1) policy_size_check.tar (Policy Size Check) scs_corba_server.tar.Z (SCS CORBA server) Note: SCS 6.0 Corba Server tar file is packaged in a separate CD.
411-5221-309
Standard
06.30 March 10, 2010
25
scsclient.tar.Z (SCS client for Solaris) scsserver.tar.Z (SCS servers: domain, region, pull, log, etc.) Solaris 9 software CDs. Windows: contains the SCS Client to run on Windows. InstallSCS.exe Note: The SCS requires the latest Solaris 9 patches need to be installed. The latest Solaris patches file, 9_recommended.zip can be downloaded from http:/ /sunsolve.sun.com. Details are given in Install Recommended Patches for Solaris 9 and Solaris 10 on page 452 SCS SSL CD Apart from the standard SCS software delivery, if the customer needs to install and activate SSL, customer needs to order an SSL CD from Nortel Networks. The SSL CD contains the following package: sslpkg.tar.Z (installs SSL package on the SCS Server and SCS Unix Client) sslpkg.zip (installs SSL package on the SCS Windows client machine) SCS Corba Server CD For SCS 6.0 (GGSNS6.0), SCS Corba Server installation file is packaged in a separate CD. scs_corba_server.tar.Z (SCS CORBA server)
Preparing the SCS software file for an upgrade with ESD
Before starting an upgrade on the SCS, perform the following software preparative measures: Move the software [load] file(s) to the appropriate directory on the SCS. If retrieving the software from ESD, the software load file is located in the ESD drop box.
For GGSN 6.0: GGSN0061.tar SCS GSSL0060.tar SSL Package GCOR0060.tar - SCS Corba Server application
GPRS/UMTS
26
Note: The following procedure shows how to prepare the SCS software for an upgrade. Use the first procedure when retrieving the SCS software from an ESD delivery.
Procedure 1 Preparing the SCS software for an upgrade Step 1 2 3 Action At the workstation, login as root onto the SCS Server. #cd /opt/shasta Create SCS 6.0 installation directory: #mkdir scs6.0 #cd /opt/shasta/scs6.0 Use file transfer protocol (FTP) to transfer the software load file as a binary file to the SCS 6.0 directory of the SCS (above step). #ftp <ESD IP address> #cd /loads/gsmvo_data (find the software location from your Electronic Delivery Confirmation email) #bin
For GGSN SCS 6.0: #get GGSN0061.tar #get GSSL0060.tar (only get this file if you have SSL package)
For GGSN SCS 6.0: If SCS CORBA server has been requested, then get the CORBA server tar file. # get GCOR0060.tar #quit 5 Verify the files are on the SCS in /opt/shasta/scs6.0. Compare the bytes size on the two files from the ESD server and on the SCS server and verify that they match. #ls -l 6 This procedure is complete.
411-5221-309
Standard
06.30 March 10, 2010
27
GGSN Software Delivery
The GGSN software is delivered via Electronic Software Delivery (ESD) or a GGSN software package CD. In the GGSN CD, the following files are included: Image MANIFEST SSC3_0C.XSV APS_0_5.BIN APSD_BT.BIN APSDIAG.BIN C3_2_2_1.BIN C3D_1_20.ROM CHROME.BIN CMC.P0 CMC.P1 CMC2_ROM.ID CMC3.P0 CMC3_ROM.ID CR_8_0_1.BIN GSE_0_5.BIN ICP2_0_7.BIN ICP_1_7.BIN LOGIN MOTD O3A_0_1.BIN O3D_1_05.ROM S3_1_5_1.BIN S3D_3_13.ROM SR6_1_2.BIN SSC2_ROM.ID SSC3_ROM.ID SSP.P0 SSP.P1 SSP.P2
28
SSP.P3 SSP3.P0 STAT2_02.BIN STAT_02.BIN STATTOP.HEX STATTOP2.HEX TZ.CFG TZU.CFG <<Firmware>> - contains the CMC and SSC bootrom files cr_8_0_1.bin c3_2_2_1.bin sr_6_1_2.bin s3_1_5_1.bin SSC3_0C.XSV
411-5221-309
Standard
06.30 March 10, 2010
29
Preparing the GGSN software file for an upgrade with ESD

Before starting an upgrade on the GGSN, perform the following software preparative measures:
Move the software [load] file(s) to the appropriate directory on the SCS If retrieving the software from ESD, the software load file is located in the ESD drop box. GGSN0060.tar < For GGSN 6.0 The following procedure shows how to prepare the GGSN software for an upgrade. Use this procedure when retrieving the GGSN software from an ESD delivery.
Procedure 2 Preparing the GGSN software for an upgrade Step 1 2 3 Action At the workstation, login as root onto the SCS Server. #cd /opt <-note, the ggsn load can be stored in any partition that has sufficient disk space Make Directory on the SCS Server for the GGSN software For GGSNS6.0: #mkdir GGSN6.0 #cd GGSN6.0 4 From the SCS Server, FTP to the ESD drop box (find the software location from your Electronic Delivery Confirmation email) SCS Server Command Line> ftp <ESD IP address> ftp> cd /loads/gsmvo_data ftp> bin ftp> prompt ftp> hash GGSNS6.0: ftp> mget GGSN0060.tar
#quit 5 On the SCS Server verify the file is in /opt/GGSN6.0. Compare the bytes size on the two files from the ESD server and on the SCS server and verify that they match. #ls -l
sheet 1 of 2
GPRS/UMTS
30
Procedure 2 Preparing the GGSN software for an upgrade Step 6 Action On the SCS Server, Untar the GGSN software in /opt/GGSN6.0 #tar -xvf GGSN0060.tar Verify the untar files with the GGSN Software Delivery files. Contact your next level of support if any files are missing. 7 Create a directory on the GGSN for FTPing the GGSN software. Login to the GGSN # cd /disk/image # mkdir GGSN6.0 8 From the SCS Server, FTP the GGSN software to the GGSN. # cd /tmp/GGSN6.0 Load Server Command Line> ftp <GGSN Management IP Address> Ftp> cd /disk/image/GGSN6.0 ftp> bin ftp> prompt ftp> hash ftp> mput * # quit 9 Verify software files on the GGSN by logging into the GGSN. Telnet or SSH to GGSN management IP address #cd /disk/image/GGSN6.0 #dir 10 This procedure is complete.
sheet 2 of 2
411-5221-309
Standard
06.30 March 10, 2010
31

Pre-upgrade checklists
3
3
The following four checkpoints (summarized in Table 1 through Table 5) must be completed in their entirety prior to the upgrade. The first checkpoint starts 4 weeks prior to upgrade. All data captured from the process must be retained for two weeks after the upgrade has been completed. If two servers with same IP are upgraded to SCS 6.0, all checkpoints must be performed on both primary server and the standby server. If a new SCS installation is performed on the Sun Netra T5220 server, skip this section. Refer to SCS Migration or New Installation on Sun Netra T5220 on page 22 for details.
GPRS/UMTS
32
Upgrade readiness checkpoint #0 28 days prior to upgrade

Table 1 Upgrade readiness checkpoint #0 28 days prior to upgrade Item 1 Description Verify that the version of this manual is the most recent and is shared by the entire team. Verify if there are any upgrade related CABs/Bulletins needed to read before upgrade. 1. IP addresses obtained for: GGSN --Active CMC IP address: _________________ --Standby CMC IP address: _________________ --user ID: _________________ (for GGSN the password for super user is required) SCS --IP address: _________________ --user ID: _________________ (for SCS Server, the password for root is required) 2. Identify the SCS home directory and LDAP home directory 3. Obtain the GGSN active and standby CMC console access/ IP address 4. Obtain the SCS server console access/ IP address 5. Login to the console ports and verify connectivity is possible 6. Obtain the SCS client ISP user ID and password for all ISPs configured on the SCS client. 4 Capture GGSN software version. Verify GGSN CMC and SSC bootrom versions
sheet 1 of 3
Work Instruction Checkpoint 0 item 1, page 48 Checkpoint 0 item 2, page 48 Checkpoint 0 item 3, page 48
Checkpoint 0 item 4, page 49
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Table 1 Upgrade readiness checkpoint #0 28 days prior to upgrade Item 5 Description Collect GGSN primary and qs1 config, bootorder, quickstart
33
Work Instruction Checkpoint 0 item 5, page 52 Checkpoint 0 item 6, page 52
Login to the SCS server as root user and determine: a. Solaris operating system release running
b. Hardware type Note: Sun E250 and E450 hardware platforms are not supported for GGSNS6.0.
c. Number of disks
d. Disk space availablility
SCS server hostname verification.
Checkpoint 0 item 7, page 57 Checkpoint 0 item 8, page 58 Checkpoint 0 item 9, page 61
SCS server domain name verification.
Determine if OS Hardening is enabled on the SCS server. Note: If the SCS server is running Solaris 8 operating system and the server is OS hardened, OS unhardening must be performed prior to starting the Solaris 9 boot environment creation. Refer to the work instructions for more details. Note: If the SCS server is already running Solaris 9 and SCS 5.0.2, OS unhardening is not required. Skip this checkpoint.
sheet 2 of 3
GPRS/UMTS
34
Table 1 Upgrade readiness checkpoint #0 28 days prior to upgrade Item 10 Description Determine if SSL is enabled on the SCS server. Note: This checkpoint is applicable only for SCS servers running SCS 5.0.2. Skip this checkpoint if the SCS server is running SCS 4.1.2. 11 Verify if all the recommended Solaris patches for Solaris Live Upgrade are applied. Note: This checkpoint is valid for SCS servers running SCS 4.1.2 on Solaris 8 operating system. If the SCS server is already running Solaris 9 and SCS 5.0.2. Skip this checkpoint. 12 Clean up of unwanted files to free disk space Checkpoint 0 item 12, page 64 Checkpoint 0 item 13, page 64 Checkpoint 0 item 14, page 64 Work Instruction Checkpoint 0 item 10, page 62 Checkpoint 0 item 11, page 63
13
SOC key data collection
14
Check the mirrors and record the mirror status. Note: This checkpoint is valid for SCS servers running SCS 4.1.2 on Solaris 8 operating system. If the SCS server is already running Solaris 9 and SCS 5.0.2. Skip this checkpoint.
15
Familiarize with partition and disk space requirements for creating a Solaris 9 Boot Environment (BE). Note: This checkpoint is valid for SCS servers running SCS 4.1.2 on Solaris 8 operating system. If the SCS server is already running Solaris 9 and SCS 5.0.2. Skip this checkpoint.
sheet 3 of 3
411-5221-309
Standard
06.30 March 10, 2010
35
Upgrade readiness checkpoint #1 14 days prior to upgrade All items in Table 2 must be confirmed within 14 days of the upgrade. All interaction with the GGSN/SCS must be logged to a console file, and retained as part of procedural records. If two servers with same IP are upgraded to SCS 6.0, the checkpoint must be performed on both primary server and standby server.
Table 2 Upgrade readiness checkpoint #1 14 days prior to upgrade Item 1 2 3 4 5 6 7 8 Description Verify that the GGSN/SCS at site is running the required software. Start capturing trending data (i.e, Performance statistics) Project Manager to review the procedure with the customer to convey the overall upgrade and pre-check procedures. Verify the SCS installation profile. If the SCS is being migrated to a new physical Server, with different IP, please verify the Patch servers. Set the limits for rlim_fd_max and rlim_fd_cur Kernel parameters Make a note of Allow tunnel terminatoin check box provisioning on all the trunk interfaces for each Gi ISP. Trim Domain behavior clarification for GGSN 4.1.1 and GGSN 6.0 Note: This checkpoint is valid only for GGSNs running 4.1.1. Skip this checkpoint if the GGSN is running 5.0.1. 9 Check RADIUS Server mis-configuration.
sheet 1 of 6
Work Instruction Checkpoint 1 item 1, page 86 Checkpoint 1 item 2, page 87 NA Checkpoint 1 item 4, page 87 Checkpoint 1 item 5, page 89 Checkpoint 1 item 6, page 90 Checkpoint 1 item 7, page 91 Checkpoint 1 item 8, page 91
GPRS/UMTS
36
Table 2 Upgrade readiness checkpoint #1 14 days prior to upgrade (continued) Item 10 Description Patch Verification for G501_FF01435785ACT_INF: Cabcharge L2TP Authentication Feature Note: This check point is valid only for GGSNs on 5.0.1. Skip this checkpoint if the GGSNs are on 4.1.1. Follow the work instructions if patch G501_FF01435785ACT_INF has been activated. Skip this checkpoint if the patch has not been activated. Note: Mark a check in the last column if this checkpoint was executed. 11 Patch Verification for G501_01450778ACT_IFMGR: Increase the MTU Size of Gn IP Interface on GELC feature. Note: This check point is valid only for GGSNs on 5.0.1. Skip this checkpoint if the GGSNs are on 4.1.1. Patch description: If on or more GELC card is present on the GGSN (5.0.1) and G501_01450778ACT_IFMGR patch is activated, the default MTU settings on the Gn interface configured on the GELC card/ port is set to1536. Skip this checkpoint if a GELC card does not exist on the GGSN. Login to the GGSN and issue the command show card command to verify. Follow the work instructions if a GELC card is present on the GGSN and patch G501_01450778ACT_IFMGR has been activated. Mark a check in the last column if this checkpoint was executed. 12 Patch Verification for G501_FF01567650ACT_IPCMC: TCP MSS Clamping feature Note: this check point is valid only for GGSNs on 5.0.1. Skip this checkpoint if the GGSNs are on 4.1.1. Follow the work instructions if patch G501_FF01567650ACT_IPCMC has been activated. This feature also requires patches G501_FF01567650_IPSSP and G501_FF01727897_GTP. Note: Mark a check in the last column if this checkpoint was executed.
sheet 2 of 6
Work Instruction Checkpoint 1 item 10, page 93
411-5221-309
Standard
06.30 March 10, 2010
37
Table 2 Upgrade readiness checkpoint #1 14 days prior to upgrade (continued) Item 13 Description Patch Verification for G501_FF01385577ACT_ERCMC: DCCv2 Envelope Reporting Feature Note: this check point is valid only for GGSNs on 5.0.1. Skip this checkpoint if the GGSNs are on 4.1.1. Note: This feature requires a SOC key. Follow the work instructions if the SOC key DIAMETER ENVELOPE REPORTING has been activated. Skip this section if the SOC key has not been activated. This feature also requires patch G501_FF01385577ACT_ERCMC to be activated and patch G501_FF01385577_ERSSP to be applied. Note: Mark a check in the last column if this checkpoint was executed. 14 Patch Verification for G501_FF01368038ACT_INF: DCCv2 Customization Essentials Feature Note: This check point is valid only for GGSNs on 5.0.1. Skip this checkpoint if the GGSNs are on 4.1.1. Note: This feature requires a SOC key. Follow the work instructions if the SOC key DIAMETER CC RT CHARG and DIAMETER CC ESSENTIALS have been activated. Skip this section if the SOC key has not been activated. This feature requires patch G501_FF01368038ACT_INF. Note: Mark a check in the last column if this checkpoint was executed.
sheet 3 of 6
GPRS/UMTS
38
Table 2 Upgrade readiness checkpoint #1 14 days prior to upgrade (continued) Item 15 Description Patch Verification for G501_FF01385579ACT_DCCCMC, G501_FF01385579ACT_DCCSSP: Parking Meter Charging Enhancement Feature Note: This check point is valid only for GGSNs on 5.0.1. Skip this checkpoint if the GGSNs are on 4.1.1. Note: This feature requires a SOC key. Follow the work instructions if the SOC key TIME EVENT BILLING has been activated. This feature also requires patches G501_FF01385579ACT_DCCCMC and G501_FF01385579ACT_DCCSSP to be activated. Note: Mark a check in the last column if this checkpoint was executed. 16 Patch Verification for G501_FF01510131ACT_CPM: Consecutive Parking Meter Feature Note: This check point is valid only for GGSNs on 5.0.1. Skip this checkpoint if the GGSNs are on 4.1.1. Note: This feature requires a SOC key. Follow the work instructions if the SOC key TIME EVENT BILLING has been activated. This feature also requires patch G501_FF01510131ACT_CPM to be activated. Note: Mark a check in the last column if this checkpoint was executed.
sheet 4 of 6
411-5221-309
Standard
06.30 March 10, 2010
39
Table 2 Upgrade readiness checkpoint #1 14 days prior to upgrade (continued) Item 17 Description Patch Verification for G501_FF01369144ACT_PPDCMC: Dual Coupon Feature Note: This check point is valid only for GGSNs on 5.0.1. Skip this checkpoint if the GGSNs are on 4.1.1. Note: This feature requires a SOC key. Follow the work instructions if the SOC key Diameter CC has been activated. This feature also requires patches G501_FF01369144_PPDSSP and G501_FF01369144ACT_PPDCMC to be activated. Note: Mark a check in the last column if this checkpoint was executed. 18 Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration Note: This check point is valid only for GGSNs on 5.0.1. Skip this checkpoint if the GGSNs are on 4.1.1. Note: Mark a check in the last column if this checkpoint was executed. 19 Patch Verification for G501_01407739ACT_INF and G501_01595094AACT_AAA Note: This check point is valid only for GGSNs on 5.0.1. Skip this checkpoint if the GGSNs are on 4.1.1. Note: Mark a check in the last column if this checkpoint was executed. 20 RADIUS Security Service Policy (firewall) verification on all connection ISP. Note: This check point is related to RADIUS messaging for VPN call models. Note: This checkpoint is applicable to GGSNs currently on GGSN 4.1.1 only.
sheet 5 of 6
GPRS/UMTS
40
Table 2 Upgrade readiness checkpoint #1 14 days prior to upgrade (continued) Item 21 Description Patch Verification for G411_01339974AACT_GTPACCT - SGSN Change Partial Billing verification. Note: This checkpoint is applicable to GGSNs currently on GGSN 4.1.1 only.
sheet 6 of 6
411-5221-309
Standard
06.30 March 10, 2010
41
Upgrade readiness checkpoint #27 days prior to upgrade All items in Table 3 must be confirmed within seven days of the upgrade. All interaction with the GGSN/SCS must be logged to a console file, and retained as part of procedural records. If two servers with same IP are upgraded to SCS 6.0, the checkpoint must be performed on both primary server and standby server.
Table 3 Upgrade readiness checkpoint #2 7 days prior to upgrade Item 1 2 3 Description Verify that the version of this manual is the most recent and is shared by the entire team. Verify the CABs / Bulletins, and verify if there are any upgrade related CABs / Bulletins Post-upgrade critical call testing plan in place. Contact Name ___________________ Contact Phone: __________________ 4 Customers CGF/Billing contact information captured Contact Name ___________________ Contact Phone: __________________ 5 Plan for remote access to GGSN/SCS for the night of the upgrade is in place. Also confirm with the customer that user names and passwords have debug permissions Obtain customer and Nortel contact(s) for Go/No-Go decision for the upgrade. Nortel Contact Name ____________ Nortel Contact Phone: __________________ Customer Contact Name ____________ Customer Contact Phone: ____________
sheet 1 of 3
Checkpoint 2 item 5, page 104 Checkpoint 2 item 6, page 105
GPRS/UMTS
42
Table 3 Upgrade readiness checkpoint #2 7 days prior to upgrade (continued) Item 7 Description Confirm that the Nortel internal support organizations notified of upgrade via email from the COL/PM: * * * * 8 9 10 GTAC WNE GPS TAS Checkpoint 2 item 8, page 105 Checkpoint 2 item 9, page 107 Checkpoint 2 item 10, page 108 Checkpoint 2 item 11, page 108 Checkpoint 2 item 12, page 108 Checkpoint 2 item 13, page 108 14 Work Instruction Checkpoint 2 item 7, page 105 X
Verify the GGSN and SCS server have adequate disk space for the new software (new load and patches). Confirm with the COL/PM that trending data is continuing to be captured daily. Ensure provisioning lock down is put in place for GGSN/SCS and obtain confirmation from the Customer Take a full system backup of SCS Server. The SCS will be unavailable to manage GGSN while the backup is under way. The total SL duration is about 1 to 2 hours. The actual duration depends on size of disks of SCS Server. Ensure that a plan is in place for the customer to obtain the billing files before and after the upgrade Verify with the customer that the upgraded software loads for GGSN/SCS are identified and available on site, as well as the patches. The GGSN and SCS software is provided on a CD. Please refer to the SSG software delivery and Contents of the SCS software sections of this document. Also verify with customer that Solaris 8 CDs and Solaris 9 CDs are obtained.
11
12
13
14
Identify and Obtain Software Optionality Control (SOC) Keys: Identify if any SOC keys are required for the new features after Upgrade. Software Optionality Control (SOC) is to enable Customer specific features with the SOC Keys. SOC keys have to be configured after the upgrade in order to have the customer specific features work. SOC keys will be provided by Nortel. Please identify, if there are any customer specific feature which require keys. Customer should contact their Nortel Networks Accounting representative to obtain the Keys.
sheet 2 of 3
15
411-5221-309
Standard
06.30 March 10, 2010
43
Table 3 Upgrade readiness checkpoint #2 7 days prior to upgrade (continued) Item 15 Description Verify the SNMP port and Trap daemon port for the SCS Work Instruction Checkpoint 2 item 15, page 108 Checkpoint 2 item 16, page 111 Checkpoint 2 item 17, page 116 Checkpoint 2 item 18, page 117 X 16
16
Verify and set the size limit and Look through limit for the LDAP. This will decide how many entries from the LDAP are retrieved during any search or other operations. These limits should be set to -1. By setting to -1, all the entries in the LDAP will be retrieved. Verify DNS configuration on the SCS server.
17
18
Delete any duplicate entries for LDAPServerName and LDAPPath if it exists: Verify if there are any duplicate entries for parameters LDAPServerName and LDAPPath in SCS system files - <SCS_ROOT>/ bin/.scs.config and /etc/shasta/scs.config. If duplicate entries are present, then delete the line with the duplicate entry. Download Solaris 9 Recommended patch cluster.
19
Checkpoint 2 item 19, page 118 Checkpoint 2 item 20, page 119
20
If upgrading from GGSN4.1 or 4.1.1 to GGSN 6.0, use the policy_size_check.sh tool to ensure that policy sizes are within SCS limits. Reduce the size of any that will exceed 256 Kbytes after the upgrade. This checkpoint is valid for upgrade of SCS 4.1.1 to SCS 6.0. Skip this checkpoint if upgrading SCS 5.0.2 to SCS 6.0.
sheet 3 of 3
GPRS/UMTS
44
Upgrade readiness checkpoint #32 days prior to upgrade All items in Table 4 must be confirmed within two days of the upgrade. All interaction with the GGSN/SCS must be logged to a console file, and retained as part of procedural records. If two servers with same IP are upgraded to SCS 6.0, the checkpoint must be performed on both primary server and standby server.
Table 4 Upgrade readiness checkpoint #3 2 days prior to upgrade Item 1 2 Description Verify that the version of this manual is the most recent and is shared by the entire team. Verify the CABs / Bulletins, and verify if there are any upgrade related CABs / Bulletins. In addition to the released patches, it is also required to enquire with the GNTS if there are any patches in the pipe line. CIQ has been formally reviewed for correctness (by at least two WNE resources and a Database Engineering resource) and provided to all Nortel internal support organizations notified of upgrade via email: * * * * 4 GTAC WNE GPS TAS Checkpoint 3 item 4, page 122 Checkpoint 3 item 5, page 122 Checkpoint 3 item 6, page 122 Checkpoint 3 item 7, page 122 Checkpoint 3 item 8, page 122 Checkpoint 3 item 9, page 122 Work Instruction Checkpoint 3 item 1, page 122 Checkpoint 3 item 2, page 122 Checkpoint 3 item 3, page 122 X
Check the SCS and GGSN CDs and make sure all the load files are available on the CDs. Make sure all patches are available on the GGSN/ SCS. Verify the latest Go/No-Go decision with customer and Nortel contact(s) as identified in Table 3 checkpoint #2. Plan in place for the customer to obtain the billing files before and after the upgrade Ensure plan in place for critical call testing on night of upgrade. Trending data is continuing to be captured daily. Check patch list for changes (have any gone to Ri.e. released status); also check for EMG (emergency) patches.
sheet 1 of 2
5 6 7 8 9
411-5221-309
Standard
06.30 March 10, 2010
45
Table 4 Upgrade readiness checkpoint #3 2 days prior to upgrade (continued) Item 10 Description Plans in place to monitor system after the upgrade (Post Upgrade Checkpoints, which are documented in this document. See SCS Postupgrade / Rollback checklists on page 304). Verify if a hostname mismatch exists between the LDAP (or iPlanet) server instance and the SCS server. If a hostname mismatch exists then modify the server hostname to match the LDAP (or iPlanet) instance hostname. Modification of server hostname requires a server reboot. Please plan on executing the procedure in a maintenance window. Work Instruction Checkpoint 3 item 10, page 123 Checkpoint 3 item 11, page 123 X
11
sheet 2 of 2
GPRS/UMTS
46
Upgrade readiness checkpoint #4night before the upgrade All items in Table 5 must be confirmed on the night before the upgrade. All interaction with the GGSN/SCS must be logged to a console file, and retained as part of procedural records. If two servers with same IP are upgraded to SCS 6.0, the checkpoint must be performed on both primary server and standby server
Table 5 Upgrade readiness checkpoint #4 night before the upgrade Item 12 13 14 Description Verify that the version of this manual is the most recent and is shared by the entire team. Critical call test plan executed successfully prior to the upgrade, Confirm the proper support teams are in place and an escalation process has been defined (i.e.: ERC#, support contact information, etc.). Also verify remote connectivity to the GGSN/SCS is still available. All consoles and/or telnet sessions need to be captured during the upgrade. Confirm with the customer that billing records are being obtained before the upgrade. Display a history of what has been occurring on the GGSN node. Display the current configuration loaded on the GGSN. Check and remove the obsolete SCS processes and LDAP processes auto startup files. Check and remove the mirrors of the critical file systems.
sheet 1 of 2
Work Instruction Checkpoint 4 item 1, page 128 Checkpoint 4 item 2, page 128 Checkpoint 4 item 3, page 128 Checkpoint 4 item 4, page 128 Checkpoint 4 item 5, page 128 Checkpoint 4 item 6, page 128 Checkpoint 4 item 7, page 129 Checkpoint 4 item 8, page 129 Checkpoint 4 item 9, page 131
15 16 17 18 19 20
411-5221-309
Standard
06.30 March 10, 2010
47
Table 5 Upgrade readiness checkpoint #4 night before the upgrade (continued) Item 21 Description Note: This checkpoint is valid only for SCS 4.1.2 to SCS 6.0 upgrade. Please skip this checkpoint if you are upgrading from SCS 5.0.2 to SCS 6.0. Also, this item only applies to SCS upgrade on the same physical server. Create Solaris 9 Boot Environment: This checkpoint item includes the following steps: 1. Stop the SCS Server and LDAP server. The SL duration is about 2 minutes. 2. Solaris 8 OS unhardening. The SL duration is about 5 minutes. 3. Start up the LDAP server and SCS server if auto-startup is not set. The SL duration is about 2 minutes. 4. Remove LDAP and SCS watches. 5. Create the Solaris 9 Boot Environment. This step will last about 3 hours and a half. The timing depends on the SCS server hardware. Please refer to detailed steps from the link under Work Instruction column.
sheet 2 of 2
GPRS/UMTS
48
Checklist work instructions and details

Upgrade readiness checkpoint #0 (28 days prior)
Checkpoint 0 item 1Verify correct version of the Upgrade Manual
Make sure to pull the most recent version of this manual from for PC06:
https://app49.nortelnetworks.com/cgi-bin/HelmExpress/coll
Click Wireless & Mobility. Under General Packet Radio Service, click GGSN 6.0 Standard
Return to Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32
Checkpoint 0 item 2Verify CABs and Bulletins
Verify to see all the released bulletins for the present version of the GGSN and SCS. The CABs and Bulletins can be accessed on the Nortel Networks web site, by the Customer. The customers would have registered for and activated their accounts to access the CABs/Bulletins. Use the user information and log into the Nortel Networks web site for CABs/Bulletins. Return to Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32
Checkpoint 0 item 3IP Addresses
Obtain the IP addresses for the SCS server and GGSN active and standby CMC. Important Note: a. Obtain the GGSN active and standby CMC console IP address b. Obtain the SCS server console IP address. c. Login to the console ports and verify connectivity is possible. Determine the current SCS and LDAP (or iPlanet) installation directories. The installation directories of SCS server and LDAP (or iPlanet) can be identified in file /etc/shasta/scs.config. SCS is installed in the directory path indicated in SCSHead and LDAP (or iPlanet) is installed in the directory path indicated in LDAPPath.
411-5221-309
Standard
06.30 March 10, 2010
49
d. Obtain the SCS client ISP user ID and password for all ISPs configured on the SCS client. The ISPs configured can be identified from the GGSN. Log in to the GGSN and issue the command show isp. Return to Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32
Checkpoint 0 item 4Capture GGSN software version. Verify GGSN CMC and SSC bootrom versions
Telnet to the GGSN management IP Issue the following commands
Capture GGSN software version:

show version
Note: GGSN must be running GGSN 5.0.1 or GGSN 4.1.1 CMC2 and CMC3 bootrom: The supported CMC bootrom firmware versions for GGSN 6.0 are: CMC2 bootrom version 8.0(1) - cr_8_0_1.bin CMC3 bootrom version 2.2(1) - c3_2_2_1.bin If the GGSN is not currently using the bootrom firmware version listed above, a CMC bootrom upgrade is necessary. The bootrom upgrade will be performed on the same day of the GGSN upgrade. Make a note of the active and standby CMC slot number from show card and CMC bootrom installed using show card slot=<CMC 2 or 3 slot> mode=detail. Here is an example capture for CMC2:
ggsn(SSU)# show card Slot Configured/Found Enabled Info ------------------------------------1 SSC /SSC Enabled U U U U 2 SSC /SSC Enabled U U U U 3 SSC /SSC Enabled U U U U 4 SSC /SSC Enabled U U U U 5 ALC /ALC Enabled U U D U [ICP Rev. 1.6] 6 ELC /ELC Enabled U U U U U U D U 7 SFC /SFC Enabled 10G Standby [FPGA Rev. 2.0]
GPRS/UMTS
50

8 10 11 12 13 14 SFC ELC SSC SSC CMC CMC /SFC /ELC /SSC /SSC /CMC /CMC Enabled

10G Active [FPGA Rev. 2.0] Enabled U D U U U U U U Enabled U U U U Enabled U U - U Enabled (Redundant) Enabled Active
Verify Active CMC:

ggsn(SSU)# show card slot= 14 mode= detail Fri 23-Mar-2007 15:22:19 CDT SSM/CT3/COC3 CPU states: A - auto-reset; N - need catchup; C - catching up; D - in delete U - up; X - failed; '-' - disabled; * not present M - failover move in progress; v - uncommunicative; d - dumping core; L - loading T - temporarily down ~ - spared overflow pool; ^ - spared failover pool 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 ---14 Configured/Found Enabled Info ---------------------------------CMC /CMC Enabled Active Memory: 1024M Processor 0 Type: Motorola PPC740/750 (0x80301) Processor 1 Type: Motorola PPC740/750 (0x80301) ROM Version: 8.0(1)
Verify Standby CMC:

ggsn(SSU)# show card slot= 13 mode= detail Fri 23-Mar-2007 15:20:42 CDT SSM/CT3/COC3 CPU states: A - auto-reset; N - need catchup; C - catching up; D - in delete U - up; X - failed; '-' - disabled; * not present M - failover move in progress; v - uncommunicative; d - dumping core; L - loading T - temporarily down ~ - spared overflow pool; ^ - spared failover pool 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 ---13 Configured/Found Enabled Info ---------------------------------CMC /CMC Enabled Standby (Redundant) Memory: 1024M Processor 0 Type: Motorola PPC740/750 (0x80301) Processor 1 Type: Motorola PPC740/750 (0x80301) ROM Version: 8.0(1)
411-5221-309
Standard
06.30 March 10, 2010
51
SSC2 and SSC3 bootrom: The supported SSC2 and SSC3 bootrom firmware versions for GGSN 6.0 are: SSC2 bootrom version 6.1.2 - SR6_1_2.BIN SSC3 bootrom version 1.5.1 - S3_1_5_1.BIN If the GGSN is running GGSN 5.0.1 software and has SSC3 cards, an XFPGA firmware upgrade may be necessary. The supported firmware version is 12. SSC3 XFPGA firmware version - 12 - SSC3_0C.XSV
If the SSC cards are not currently running the supported bootrom firmware, a SSC firmware upgrade is required. The firmware files are packaged with the GGSN load. Make a note of the SSC2 or SSC3 bootrom version installed on the GGSN. If the GGSN has SSC3 cards, make a note of the XFPGA firmware version as well. Use command show card to view the SSC card lineup. Use show card slot=<SSC 2 or 3 slot number> mode=detail to view/ capture the SSC bootrom version. If SSC3 cards are installed, make a note of the XFPGA firmware version.
Here is an example capture for SSC2:

ggsn(SSU)# show card slot= 1 mode= detail Slot Configured/Found Enabled Info ------------------------------------1 SSC /SSC Enabled U U U U 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.1(2) <- SSC2 bootrom version Enet chip: Shasta DV (0x547ffff), rev: 0x2000303 Is in the data mesh Has missed 0 polls
Here is an example capture for SSC3, make a note of both the bootrom version and XFPGA firmware version:
ssg-21(SSU)# show card slot= 1 mode= detail Fri 23-Mar-2007 19:36:47 GMT+1 SSM/CT3/COC3 CPU states: A - auto-reset; N - need catchup; C - catching up; D - in delete U - up; X - failed; '-' - disabled; * not present M - failover move in progress;
GPRS/UMTS
52

- loading

v - uncommunicative; d - dumping core; L T - temporarily down ~ - spared overflow pool; ^ - spared
failover ALC port ELC/GELC CT3/COC3 Slot ---1
pool states: U - up; D - down (alarm) port states: U /- up; D - down (link fail) port states: + - up; '-' - down (alarm)
Configured/Found Enabled Info ---------------------------------SSC3 /SSC3 Enabled U U U U SSC3 state: running SEC state: running XPIF state: running SSM 1 state: running CPU: BCM1250 (0x125011ff) Bus Speed: 357MHz Memory: 1024M Encrypt: No Limit ROM version: 1.5(1) <-SSC3 bootrom version DIAG ROM version: 3.13 GGI GMII Bridge A version: 9 <- XFPGA version GGI GMII Bridge B version: 9 <- XFPGA version SEC GMII Bridge version: 7 Enet chip: BCM 1250 (0x1250), rev: 0x0
Checkpoint 0 item 5Collect GGSN primary and qs1 config, bootorder, quickstart
Telnet to the GGSN. Set the telnet terminal paging to 0 lines. This allows user to capture long output from a show command.
ggsn(SSU)# set terminal telnet lines=0
Capture the following data.

ggsn(SSU)# ggsn(SSU)# ggsn(SSU)# ggsn(SSU)# show show show show quickstart bootorder config primary config qs1
Checkpoint 0 item 6SCS server hardware analysis
a. Solaris operating system release running and Solaris patches applied.

# showrev
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential # showrev -p
53
If the Release indicates 5.8, current Solaris operating system running is Solaris 8 and upgrade to Solaris 9 is required. If the Release indicates 5.9, current Solaris operating system running is Solaris 9 and upgrade of operating system is not necessary. b. Hardware type prtconf -pv: provides details platform type, platform configuration, memory size (RAM installed), system peripherals, server boot environment variables
# prtconf -pv
Note: Sun E250 and E450 hardware platforms are not supported for GGSNS6.0. If the SCS server is running on a E250 or E450, a new platform complying withHardware Requirements for SCS on page 143 must be identified prior to starting the upgrade. For details on the server migration, please follow SCS server preparation: Migration of the current SCS to new hardware or New Install of SCS on new hardware on page 142. prtdiag -v: provides system configuration details as well as system level diagnostics. Note, this command is not available on servers running Solaris 8 operating system.
# prtdiag -v
c. Number of disks
# /usr/sbin/format < /dev/null
d. Disk space availablility. SCS upgrade has two disk space requirements depending on the Solaris operating system. There is one swap space requirement: 1. Does the server have enough disk space to perform an SCS 6.0 upgrade. 2. Does the server have free unmounted disks (or disk partitions) required to perform Solaris 9 upgrade.
GPRS/UMTS
54
3. Does the server have enough swap space for running SCS server processes. Note: If the SCS server is running SCS 4.1.2 on Solaris 8, requirement 1 and 2 must be satisfied. Note: If the SCS server is running SCS 5.0.2 on Solaris 9, requirement 1 must be satisfied. First, run the following command to capture a summary of partitions and disk space available/ used.
# df -k
The output displays the following fields as follows: file system name total space allocated in the file system (in Kbytes) amount of space allocated to existing files total amount of space available for the creation of new files percentage of space that is currently allocated the mount point
Check the partition /, <SCS_ROOT> partition, /usr and /var. These are the critical file systems partitions. Note, some servers can have more or less mounted partitions. If the more than 99% of the disk space is occupied in these partitions, the SCS server processes will automatically shut down. If the partitions are more than 75% full, customer should clean up and make sure enough disk space is available. Note: <SCS_ROOT> partition - partition where SCS server is installed To find out <SCS_ROOT>, execute the following command as root user on the SCS server.
# cat /etc/shasta/scs.config | grep SCSHead | cut -f 2- -d=
The disk space requirements for SCS 6.0 upgrade can be categorized into two: Disk space required for SCS 6.0 upgrade
411-5221-309
Standard
06.30 March 10, 2010
55
Disk space required for Solaris 9 upgrade (this requirement can be skipped if the server is running SCS 5.0.2 on Solaris 9) Swap space requirement Lets look into these requirement in detail: i. Disk space required for SCS 6.0 upgrade During SCS rolling upgrade, the upgrade process makes a copy of the current SCS directory to the new SCS 6.0 directory and a new instance for LDAP is created in the current LDAP directory. This means the at lest twice the amount of disk space currently used by SCS and LDAP plus 3 GB free space is required to perform SCS 6.0 upgrade. To make SCS server backups simple, SCS 6.0 is recommended to be installed in the same partition as the current SCS and LDAP installation. The additional 3 GB is a conservative estimate and is assigned for SCS 6.0 upgrade and room for database and log directory usage increase over a period of time. Here are some steps to determine the disk usage by the current SCS and LDAP (or iPlanet) installation. Find the installation directory for SCS
# cat /etc/shasta/scs.config | grep SCSHead | \ cut -f 2- -d= /opt/shasta/scs <- for example
Determine the disk space used by SCS, here is an example:

# cd /opt/shasta/scs # du -k .
The space returned here is in KB. Find the installation LDAP
# cat /etc/shasta/scs.config | grep LDAPPath | \ cut -f 2- -d= /opt/shasta/ldap <- for example
Determine the disk space used by LDAP, here is an example:

# cd /opt/shasta/ldap # du -k .
The space returned here is in KB.
GPRS/UMTS
56
Here is the minimum space recommended for swap and /opt partition.
Deployment Number of BSNs Swap Space Minimum Required 1408 MB 704 MB 352 MB Recommended Minimum /opt 3-5 GB 3-5 GB 3-5 GB
Large Medium Small
15-20 Devices or multiple Regions 7-10 Devices with Maximum of 1 Region 1 or 2 Devices with limited subscribers
Note: If /, /var or /opt partitions have more than 99% of the disk space occupied, the SCS processes will automatically shut down. If the disks are more than 75% full, customer should clean up and make sure enough disk space is available.
ii. Disk space required for Solaris 9 upgrade Solaris 9 Live Upgrade commands make a copy of the existing mounted partitions into the unmounted partitions. Then the unmounted partitions are upgraded to Solaris 9. Setting the size limit on the unmounted disk partition depends on the amount of disk space currently used by the server. An equal amount of disk space used by the current partition plus at least 3 to 5 GB per mounted disk partition will be needed to perform Solaris 9 live upgrade. For mirrored server: The SCS server is first unmirrored prior to starting the Solaris 9 upgrade. After unmirroring, for each mounted partition, the unmirrored, unmounted partition will be used as the boot environment partition assigned for Solaris 9. If the server was mirrored correctly, the mounted partition and the recovered partition on unmirroring are of equal size (matching geometrically). Each mounted partition must have at least 3 to 5 GB free space for Solaris 9 upgrade. For more details, please refer to Checkpoint 0 item 14, page 64 Check the mirrors and record the mirror status. For non-mirrored server: An equal amount of disk space used by the current partition plus at least 3 to 5 GB per mounted disk
411-5221-309
Standard
06.30 March 10, 2010
57
partition will be needed to perform Solaris 9 live upgrade. Please refer to Appendix K: Disk Analysis For Non-Mirrored Servers on page 666 for more details.
iii. Swap space requirement The required swap space for a large scale SCS Deployment is about 1408M which is 1441792 Kb. The swap l command reports total and free space for each of the swap partitions that have been configured for the system. Notice that this number does not reflect the total amount of virtual memory in the system since physical memory is not counted in the output. Use of the swap s command reports the total amount of virtual memory. Use swap s to determine the swap space available. Here are examples of the swap commands.
Example: # swap -l
swapfile /dev/dsk/c0t0d0s1 dev 32,1 swaplo blocks free 16 3073872 3066512
# swap -s
total: 366832k bytes allocated + 282256k reserved = 649088k used, 1683528k available
If the swap space available on the server does not match the recommended swap space, please follow Swap memory space allocation on page 228 to add additional swap space. Return to Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32
Checkpoint 0 item 7SCS server hostname verification
Verify the SCS server has the hostname configured to match the currently operational LDAP (or iPlanet) instance. a. Make a note of the hostname configured on the server. Capture the output of the following commands:
GPRS/UMTS
58
GGSN/SCS pre upgrade checklists # uname -a | awk '{print $2}' # hostname
Make sure the output from the above commands match. b. Make a note of the LDAP (or iPlanet) server instance name. Capture the output of the following command:
# cat /etc/shasta/scs.config | grep LDAPServerName | cut -f 2- -d-
Make sure the hostname output from the above steps b. and a. match. If the hostname from step b. does not match step a., the hostname of the SCS server must be modified to match the hostname set for the LDAP (or iPlanet) instance (step b). The hostname modification will be made in Upgrade readiness checkpoint #3 2 days prior to upgrade on page 44. When the hostname of the SCS server is modified, a server reboot is necessary. Please plan this during a maintanence window.
Return to Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32 or If the above section was executed during checkpoint #3, please return to Checkpoint 3 item 11, page 123
Checkpoint 0 item 8SCS server domain name verification
Verify the SCS server host has domainname configured and matches with the LDAP (or iPlanet) instance. Example captures are provided for reference. c. Make a note of domain entry set in /etc/resolv.conf. Make sure a domain name is set:
# cat /etc/resolv.conf domain us.nortel.com
d. Make a note of /etc/hosts

# cat /etc/hosts # # Internet host table # 411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential 127.0.0.1 192.168.35.1
GGSN/SCS pre upgrade checklists localhost zrc2s135.us.nortel.com
59
loghost
Note: If domain name is not listed for the SCS host name, it need not be modified e. Make a note of /etc/defaultdomain
# cat /etc/defaultdomain
Note: If domain name is not listed in /etc/defaultdomain, it need not be added. f. Make a note of <LDAPRoot> from /etc/shasta/scs.config
# cat /etc/shasta/scs.config | grep LDAPRoot LDAPRoot="uid=admin,ou=People,o=us.nortel.com"
Make a note of the string after o=. Here is it set to us.nortel.com. This is the administrative domain name. This must match the domain name set in /etc/resolv.conf g. Make a note of <LDAPRoot> from <SCS_ROOT>/bin/.scs.config To find <SCS_ROOT>, make a note of SCSHead from /etc/shasta/scs.config. Note, SCSHead is same as <SCS_ROOT>
# cat /etc/shasta/scs.config | grep SCSHead SCSHead=/opt/shasta/scs
Change directory to the path returned by the above command. From the above example:
# cd /opt/shasta/scs
Change to bin directory

# cd bin
Make a note of <LDAPRoot> from .scs.config file.

# cat /opt/shasta/scs/bin/.scs.config | grep LDAPRoot LDAPRoot="uid=admin,ou=People,o=us.nortel.com"
Make a note of the string after o=. Here is it set to us.nortel.com. This is the administrative domain name. This must match the domain name set in /etc/resolv.conf h. Launch LDAP (or iPlanet) console and determine the domain name. This requires the user to telnet to the SCS server from X Windows or through a monitor directly connected to the SCS server.
GPRS/UMTS
60
Determine LDAP (or iPlanet) installation directory:

# cat /etc/shasta/scs.config | grep LDAPPath
Here is an example for SCS 4.1.2
# cat /etc/shasta/scs.config | grep LDAPPath LDAPPath=/opt/shasta/ldap
Here is an example for SCS 5.0.2
# cat /etc/shasta/scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet
Change directory to the path returned by LDAPPath

# cd <LDAPPath>
Here is an example: For SCS 4.1.2:
# cd /opt/shasta/ldap
For SCS 5.0.2:
# cd /opt/shasta/iplanet
Determine the LDAP (or iPlanet) admin server port:

# cat admin-serv/config/adm.conf | grep port
Here is an example for SCS 4.1.2:
# cat admin-serv/config/adm.conf | grep port port: 23611
Here is an example for SCS 5.0.2:
# cat admin-serv/config/adm.conf | grep port port: 33611
If you are using telnet to connect to the SCS server, then export Unix DISPLAY environment variable. If SCS server is connected to a monitor directly, then DISPLAY environment variable need not be exported. In C shell, execute the following commands, replace IP_ADDRESS with the host IP you are connecting to the SCS.
# setenv DISPLAY IP_ADDRESS:0.0
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential # <LDAPPath>/startconsole &
61
Username: admin (unless modified by user) Password: admin Administration URL: http://scshost.domain:ldap_admin_port Where ldap_admin_port is the port returned in the above step. Under Servers and Applications tab, make a note of the Administrative Domain. The domain is the first node in the tree structure. On the right panel, make a note of the Domain Name. Make sure the above steps a. through f. have the same domain name set. Return to Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32
Checkpoint 0 item 9Determine if OS Hardening is enabled on the SCS server
Note: This checkpoint is valid for SCS servers running Solaris 8. If the SCS server is currently on Solaris 9, skip this checkpoint. 1. Login to the SCS server as root user. Verify if /SECURITY directory exists.
# ls /SECURITY
Note: If the above ls command fails with the error No such file or directory, the server is not OS hardened. Skip this step and return to Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32 Note: If ls returns a directory listing similar the example below, proceed with this checkpoint.
# ls SECURITY Current_Release NNoshscs osh4 supplement
2. Change directory to the directory path listed below and perform a file listing using ls command:
# cd /SECURITY/NNoshscs/bin
3. Usels command to show the directory listing:

62
# ls Solaris_OsHarden
Solaris_OsUnHarden
showstatus
4. Execute the script showstatus to verify if the SCS server is OS hardened.

# ./showstatus The system is not hardened. The system is installed with the following package(s): Package "NNoshscs.SCS_V05_00.E03", patch level "none".
Note: The actual version may vary according to your release. If the SCS server is OS hardened, the server unhardening is performed prior to Solaris 9 Live Upgrade. Please refer to Checkpoint 4 item 10, page 131 Return to Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32
Checkpoint 0 item 10Determine if SSL is enabled on the SCS server
Note: This checkpoint is applicable for SCS 5.0.2. The checkpoint can be skipped if the SCS server is running SCS 4.1.2. As root user, verify if SSL is enabled on the SCS server.
Change to the bin directory in the directory path returned by the above command and execute SCSAdmin status. Here is an example:
# cd /opt/shasta/server # cd bin # ./SCSAdmin status
If SSL is enabled on the SCS server, SCSAdmin status will indicate:

SSL is enabled on present servers
If SSL is enabled on the SCS server, then after the SCS server software upgrade, SSL software also must be upgrade. Make a note of this information as it will be needed during SCS 6.0 server upgrade.
411-5221-309
Standard
06.30 March 10, 2010
63
Checkpoint 0 item 11Verify if all the recommended Solaris patches for Solaris Live Upgrade are applied
Note: This checkpoint is valid for SCS servers running SCS 4.1.2 on Solaris 8 operating system. If the SCS server is already running Solaris 9 and SCS 5.0.2. Skip this checkpoint. It is recommended to install the latest Solaris 8 patch cluster on the SCS server prior to starting the Solaris 9 Live Upgrade. If the latest Solaris 8 patch cluster is not installed, at least the latest limited set of recommended patches for Solaris 9 Live Upgrade is required. Live Upgrade may fail to work properly if at least the limited set of recommended patches are not installed on the system. For the recommended patch details, please visit: http://sunsolve.sun.com - Search for the "live upgrade minimum patch requirements" Note: From the Solaris live upgrade minimum patch requirement list, the following patches will fail to install. Users need not take any actions. 111879-01 - Problem with older prodreg and Live Upgrade (this patch is not required as prodreg utility is not used to update the liveupgrade package) 121430-16 - Required for Solaris 10 live upgrade (not required for Solaris 9 upgrade) 112279-03 - pkgrm failed during upgrade from S8 to S9 with DSR 114251-01 - pkgrm failed if upgrade from S8U7 to upper release with DSR.
GPRS/UMTS
64
Checkpoint 0 item 12Clean up of unwanted files to free disk space
Login to the server as root user. Check the disk space available on the server using df -k. If certain partitions have high usage (capacity column in df k), user must try to clean up any unwanted files or directories stored on the server. Note: Please dont delete files from /usr or /var. Unwanted log files could be deleted from /var. Please be cautious when cleaning up /opt/shasta directory and / directory. Return to Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32
Checkpoint 0 item 13SOC key data collection
Log in to the GGSN as admin user. Issue the command:

show soc
Record the output
Checkpoint 0 item 14Check the mirrors and record the mirror status
Note: This checkpoint is valid for SCS servers running SCS 4.1.2 on Solaris 8 operating system. If the SCS server is already running Solaris 9 and SCS 5.0.2. Skip this checkpoint. The file systems of SCS Server might have mirrors.
Gather mirroring information:
Execute the following commands to check if the SCS server has mirrored drives:
# which metastat # /usr/sbin/metastat
411-5221-309
Standard
06.30 March 10, 2010
65
If there is no output or metastat command returns metastat: <server_name>: there are no existing databases on the console, it implies that the file systems is not mirrored. If metastat returns output, record the output of the commands mentioned in procedure below. This information is needed for recreating the mirrors on Solaris 9 after completion of the upgrade procedures. If metastat does not return output, then verify the partitioning required for non-mirrored servers. Please go to sectionAppendix K: Disk Analysis For Non-Mirrored Servers on page 666. The following partitions are termed Critical File systems / - Root partition /usr - Location for system executables /var - Location for logs /opt - Location of applications including SCS and LDAP/ iPlanet server Other partitions not listed above are termed Non-Critical File systems. Example of this type of partition is /export/home and swap. Note: The server you are working on may have additional partitions. Record the partition information for all critical and non-critical file systems that are mounted on the server.
Step 1: Determine the critical file systems and the associated metadevice name. Perform 'df -k' to find out all the mounted file systems and record the output. Also, perform cat /etc/vfstab to record the swap partition as the metadevice name for swap is not displayed with df -k. Example:
urc2y3pa# df -k Filesystem /dev/md/dsk/d0 /proc fd mnttab /dev/md/dsk/d5 swap swap /dev/md/dsk/d8 /dev/md/dsk/d7 kbytes used avail capacity 10086988 429705 9556414 5% 0 0 0 0% 0 0 0 0% 0 0 0 0% 20174761 5447 19967567 1% 17404448 16 17404432 1% 17404536 104 17404432 1% 70577241 1876603 67994866 3% 20174761 9 19973005 1% Mounted on / /proc /dev/fd /etc/mnttab /var /var/run /tmp /opt /export/home
GPRS/UMTS
66
The df -k example shows: A) Metadevice Critical File System: d0 ------- / d5 ------- /var d6 ------- /usr d8 ------- /opt
B) Metadevice Non-critical File Systems: d7 ------- /export/home
Run: cat /etc/vfstab. Find out the metadevice name for swap. Here is an example.
# cat /etc/vfstab
#device #to mount fd /proc /dev/md/dsk/d1 /dev/md/dsk/d0 /dev/md/dsk/d5 /dev/md/dsk/d7 /dev/md/dsk/d8 device to fsck /dev/fd fd /proc proc /dev/md/rdsk/d0 /dev/md/rdsk/d5 /dev/md/rdsk/d7 mount FS point type no no swap / ufs /var ufs /export/home ufs fsck pass no 1 1 ufs 1 mount mount at boot options no no 1 yes
yes -
/dev/md/rdsk/d8 /opt
C) Metadevice Non-critical File System - Swap partition: d1 -------swap Note: The server you are working on may have additional partitions. So record all the mounted partitions (Step 3 below).
Step 2: Record 'metastat' for critical and non-critical file systems. '/usr/sbin/metastat <metadevice_name>'
411-5221-309 Standard 06.30 March 10, 2010
67
Example: urc2y3pa# metastat d0 d0: Mirror Submirror 0: d10 State: Okay Submirror 1: d20 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 20484288 blocks <--Verify Block Size d10: Submirror of d0 State: Okay Size: 20484288 blocks <--Verify Block Size Stripe 0: Device Start Block Dbase State c1t0d0s0 0 No Okay
Hot Spare
d20: Submirror of d0 State: Okay Size: 20484288 blocks <--Verify Block Size Stripe 0: Device Start Block Dbase State c1t2d0s0 0 No Okay
Hot Spare
Repeat Step 2 for all the other critical file systems and non-critical files systems. Important Note: Verify the block size of the submirrors in each mirror. If the block size of the sub-mirrors is not the same, follow section Appendix D: Creating a Partition on a New Disk for Disk Mirroring on page 600 Here is an example capture of a mirrored server.
urc2y3pa# metastat d0: Mirror Submirror 0: d10 State: Okay Submirror 1: d20 State: Okay Pass: 1
GPRS/UMTS
68

Read option: roundrobin (default) Write option: parallel (default) Size: 20484288 blocks d10: Submirror of d0 State: Okay Size: 20484288 blocks Stripe 0: Device c1t0d0s0 d20: Submirror of d0 State: Okay Size: 20484288 blocks Stripe 0: Device c1t2d0s0
Start Block 0
Dbase State No Okay
Hot Spare
Start Block 0
Dbase State No Okay
Hot Spare
d1: Mirror Submirror 0: d11 State: Okay Submirror 1: d21 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 16780224 blocks d11: Submirror of d1 State: Okay Size: 16780224 blocks Stripe 0: Device c1t0d0s1 d21: Submirror of d1 State: Okay Size: 16780224 blocks Stripe 0: Device c1t2d0s1
Start Block 0
Dbase State No Okay
Hot Spare
Start Block 0
Dbase State No Okay
Hot Spare
d5: Mirror Submirror 0: d15 State: Okay Submirror 1: d25 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 40968576 blocks d15: Submirror of d5 State: Okay Size: 40968576 blocks Stripe 0: Device c1t0d0s5 d25: Submirror of d5 State: Okay Size: 40968576 blocks Stripe 0:
Start Block 0
Dbase State No Okay
Hot Spare
411-5221-309
Standard
06.30 March 10, 2010

Device c1t2d0s5 Start Block 0

Dbase State No Okay
69
Hot Spare
Start Block 0
Dbase State No Okay
Hot Spare
Start Block 0
Dbase State No Okay
Hot Spare
Start Block 0
Dbase State No Okay
Hot Spare
Start Block 0
Dbase State No Okay
Hot Spare
Step 3: Fill out the following table: For each critical and non-critical file system mounted on the server, fill out the following: a. Respective metadevice name
GPRS/UMTS
70
b. Column First sub-mirror/ disk partition-- Partition for Solaris 8 with the first submirror returned from the metastat command output. c. Column Second submirror/ disk partition -- Partition for Solaris 9 with the second submirror.
Table 6 Disk Mirroring Mapping for Critical File Systems Critical file system Metadevice name of the mirror First sub-mirror / disk partition -- Partition for Solaris 8 Second sub-mirror / disk partition -- Partition for Solaris 9
Table 7 Disk Mirroring Mapping for Non-critical File Systems Non-critical file system Metadevice name of the mirror First sub-mirror / disk partition Second sub-mirror / disk partition
411-5221-309
Standard
06.30 March 10, 2010
71
Here is an example Disk Mirror Mapping Table. Output from metastat and /etc/vfstab are used to fill out this table
Table 8 Example Disk Mirroring Mapping for Critical File Systems Critical file system Metadevice name of the mirror First sub-mirror / disk partition -- Partition for Solaris 8 d10/ c1t0d0s0 d15/ c1t0d0s5 d18/ c1t1d0s7 Second sub-mirror / disk partition -- Partition for Solaris 9 d20/ c1t2d0s0 d25/ c1t2d0s5 d28/ c1t3d0s7
/ /var /opt
d0 d5 d8
Table 9 Example Disk Mirroring Mapping for Non-critical File Systems Non-critical file system /export/home swap Metadevice name of the mirror d7 d1 First sub-mirror / disk partition d17/ c1t0d0s7 d11/ c1t0d0s1 Second sub-mirror / disk partition d27/ c1t2d0s7 d21/ c1t2d0s1
Note: Create the above tables for Critical File System, Non-Critical File System and metadb (from Step 4 below) output in a MS Word document or an MS Excel spreadsheet before proceeding to the next step.
GPRS/UMTS
72
Step 4: Record 'metadb' and /etc/lvm/md.tab. These partitions must not be used for Solaris 9 BE creation. Recording these are important as these partitions will again be used to re-create the mirrors on Solaris 9. Note: File /etc/lvm/md.tab may or may not be set correctly on the server you are working on. Usually, the operator performing the mirroring for the first time needs to manually set this file. Solaris OS by default adds this file with all lines commented out with #. This means, file /etc/lvm/md.tab has not been set and needs to be set at this point.
# metadb flags a m a a a a a a a a a a a first blk 16 1050 2084 16 1050 2084 16 1050 2084 16 1050 2084 block count 1034 1034 1034 1034 1034 1034 1034 1034 1034 1034 1034 1034
p p p p p p p p p p p p
luo luo luo luo luo luo luo luo luo luo luo luo
/dev/dsk/c1t0d0s3 /dev/dsk/c1t0d0s3 /dev/dsk/c1t0d0s3 /dev/dsk/c1t1d0s3 /dev/dsk/c1t1d0s3 /dev/dsk/c1t1d0s3 /dev/dsk/c1t3d0s3 /dev/dsk/c1t3d0s3 /dev/dsk/c1t3d0s3 /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3
# cat /etc/lvm/md.tab mddb01 c1t0d0s3 c1t1d0s3 c1t2d0s3 c1t3d0s3 d8 -m d18 d18 1 1 c1t1d0s7 d28 1 1 c1t3d0s7 d7 -m d17 d17 1 1 c1t0d0s7 d27 1 1 c1t2d0s7 d5 -m d15 d15 1 1 c1t0d0s5 d25 1 1 c1t2d0s5 d1 -m d11 d11 1 1 c1t0d0s1 d21 1 1 c1t2d0s1 d0 -m d10 d10 1 1 c1t0d0s0 d20 1 1 c1t2d0s0
You can notice from metadb command output that there are 3 entries for a single metadb partition. Also, the first line of file md.tab will list out the unique metadb partitions.
flags a m p a p a p luo luo luo first blk 16 1050 2084 block count 1034 1034 1034 /dev/dsk/c1t0d0s3 /dev/dsk/c1t0d0s3 /dev/dsk/c1t0d0s3
If you notice 3 entries for the metadb partition, then the metadb partition was assigned using the command:
411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential # metadb -a -f -c 3 /dev/dsk/c1t0d0s3
73
If you notice 2 entries, then metadb partition was assigned using:

# metadb -a -f -c 2 /dev/dsk/c1t0d0s3
Record the above output in the following table.
Table 10 metadb partition table metadb Partition Number of repetitions while executing metadb command
Table 11 Example metadb partition table metadb Partition

c1t0d0s3 c1t1d0s3 c1t2d0s3 c1t3d0s3
Number of repetitions while executing metadb command 3 3 3 3
Important Note: If /etc/lvm/md.tab file has all lines commented out, please perform the following: a. Find the unique metadb partitions configured on the server
# metadb
a m a a flags p luo p luo p luo first blk 16 8208 16400 block count 8192 /dev/dsk/c1t0d0s3 8192 /dev/dsk/c1t0d0s3 8192 /dev/dsk/c1t0d0s3
GPRS/UMTS
74

a a a a a a a a a p p p p p p p p p luo luo luo luo luo luo luo luo luo 16 8208 16400 16 8208 16400 16 8208 16400 8192 8192 8192 8192 8192 8192 8192 8192 8192

/dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3 /dev/dsk/c1t1d0s3 /dev/dsk/c1t1d0s3 /dev/dsk/c1t1d0s3 /dev/dsk/c1t3d0s3 /dev/dsk/c1t3d0s3 /dev/dsk/c1t3d0s3
Here c1t0d0s3, c1t1d0s3, c1t2d0s3, c1t3d0s3 are the unique metadb partitions. b. Determine the mirroring configuration using metastat -p.
# metastat -p d0 -m d10 1 d20 1 d1 -m d11 1 d21 1 d5 -m d15 1 d25 1 d7 -m d17 1 d27 1 d8 -m d18 1 d28 1 d10 d20 1 1 c1t0d0s0 1 c1t2d0s0 d11 d21 1 1 c1t0d0s1 1 c1t2d0s1 d15 d25 1 1 c1t0d0s5 1 c1t2d0s5 d17 d27 1 1 c1t0d0s7 1 c1t2d0s7 d18 d28 1 1 c1t1d0s7 1 c1t3d0s7
c. Update the file /etc/lvm/md.tab file with the values obtained from metadb and metastat -p (above) using the following steps. Copy /etc/lvm/md.tab to a backup file
# cp /etc/lvm/md.tab /etc/lvm/md.tab.original
Clear out /etc/lvm/md.tab

# cat /dev/null > /etc/lvm/md.tab
Add a line starting with mddb01 followed by the unique partitions obtained from metadb
Example: mddb01 c1t0d0s3 c1t2d0s3 c1t1d0s3 c1t3d0s3
Update /etc/md.tab with metastat -p. Note: Use >> after metastat -p
# metastat -p >> /etc/lvm/md.tab 411-5221-309 Standard 06.30 March 10, 2010
75
The modified /etc/lvm/md.tab is:

Step 5: Record 'cat /etc/vfstab' Step 6: Record 'format' Here is an example:

urc2y3pa# format < /dev/null Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010183a01,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010186a81,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b0b1,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0 6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0 10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 Specify disk (enter its number):
Step 7: Record boot path for current Solaris 8 and new Solaris 9
GPRS/UMTS
76
Important Step to determine server boot path for Solaris 8 and Solaris 9:
Make a note of the server boot path for the current Solaris 8 and new Solaris 9. This is needed to make changes to Solaris boot environment before Solaris 9 BE is activated or when the server is rolled back to Solaris 8 after activating Solaris 9. Here is a brief explanation and the steps: Use ls -al command on the partition that is being assigned for / file system for the current Solaris 8 and the new Solaris 9. These path are needed as the server will look for the kernel executable in / during server reboot when activating Solaris 9 or during rollback for Solaris 8. Determine the server root device for Solaris 8: Run df -k and find out the currently mounted / partition. In the below example, /dev/dsk/c1t0d0s0 is set for /.
# df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t0d0s0 61522236 14749551 46157463 25% /
Run ls -al for the physical partition assigned for the current Solaris 8 / partition.
# ls -al /dev/dsk/c1t0d0s0 lrwxrwxrwx 1 root root 70 May 4 11:46 /dev/ dsk/c1t0d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@2/ fp@0,0/ssd@w500000e010188041,0:a
Record the string that follows the /devices directory. Please note down this information. Also update the spreadsheet that has Disk Mirroring Mapping for Critical File Systems on page 70 In the above example, this string is:
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0:a
Edit the string to change the major name (ssd, in this case) to disk, resulting in:
/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w500000e010188041,0:a
Make a note of this string, this is called solaris8_root for reference. This will be needed if you want to rollback from Solaris 9 to Solaris 8. solaris8_root - /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w500000e010188041,0:a
411-5221-309
Standard
06.30 March 10, 2010
77
Determine the server root device for Solaris 9: Run ls -al for the physical partition assigned for / for Solaris 9. From the below example, /dev/dsk/c1t2d0s0 is set for /.
# ls -al /dev/dsk/c1t2d0s0 lrwxrwxrwx 1 root root 70 Aug 23 15:31 /dev/ dsk/c1t2d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@2/ fp@0,0/ssd@w21000004cf786ffa,0:a
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf786ffa,0:a
/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf786ffa,0:a
Make a note of this string, this is called solaris9_root for reference. This will be needed during reboot of the server after mirroring all the partitions.
solaris9_root - /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w21000004cf786ffa,0:a
Record solaris8_root and solaris9_root in the spreadsheet that containsDisk Mirroring Mapping for Critical File Systems on page 70 This concludes the data collection for Solaris 8 mirrored servers. Return to Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32
GPRS/UMTS
78
Note: Read through the section Appendix C: Unmirroring the File

Systems on page 586 before proceeding to the next section. Solaris 9 Live Upgrade process that creates the Solaris 9 boot environment requires the disks on the server to be unmirrored. The following section assumes that the Solaris server the user is working on has been unmirrored.
Checkpoint 0 item 15 Familiarize with the process of creating a Solaris 9
Boot Environment (BE) Read through this section to learn the steps that are executed to create a new Solaris 9 Boot Environment. If there is not a free partition that meets the requirements as specified in the above section, an additional disk that is pre-formatted and partitioned is required to serve this purpose. Please refer to Identifying Unmounted Partitions required for Solaris 9 Boot Environment (BE) Creation on page 668 Note: If there is no free partition and no additional disk/no spare disk slot, the upgrade can not proceed.
Boot Environment (BE) For Solaris 9
This section details the steps to analyze the Solaris 8 system for identifying the partitions for creating Solaris 9 Boot Environment. The Solaris 9 boot environment creation has the following steps. See Solaris 9 Boot Environment Creation on page 414 for details. Identify the Partitions for Solaris 9 Boot environment. Check required packages for Solaris Live Upgrade. Verify and update the version of Live Upgrade. Create the Solaris 9 BE and mount the critical file systems that are mounted in the current boot environment. Upgrade the Solaris 9 BE from the Solaris CDs. Check the status of the Solaris 9 BE. Check and remove the file /var/sadm/system/data/packages_to_be_added if it exists. Activate Solaris 9 Boot environment.
411-5221-309
Standard
06.30 March 10, 2010
79
Understanding Sun hard disk naming convention
Perform df -k or /etc/vfstab on your server. You will notice the physical partition name on a unmirrored server to cvtwdxsz. On a mirrored server, you can find this info by running /usr/sbin/metastat c - Disk Controller / v - Controller number t - Physical Bus Target / w - Target number d - Drive / x - Drive number s - Disk slice / z - Slice number With format, explained below, we can identify the total number of hard disks available on the server. With df -k and /etc/vfstab explained below, make a note of the disks currently used by the system.
Identify the Partitions for Solaris 9 Boot environment
1. Check the disk partitions and disk space used for the current Solaris 8 partition using df -k and /etc/vfstab. Also, make a note of the swap partition from /etc/vfstab since df -k will not show the drive name for swap. Note 1: Refer to the table Disk Mirroring Mapping to find out the available partitions. The recovered partitions (un-mounted) after unmirroring the server will be used for Solaris 9 BE creation. Note 2: Usually Solaris 9 boot environment is created only for critical file systems. This way the server has the necessary system file to boot of Solaris 9. Boot environment for non-critical file systems can also be created if needed by the user. Note 3: It is a must that the size of each unassigned and unmounted partitions should be at least larger than the used size of its corresponding critical file system plus 3 GB.
# df -k Filesystem /dev/dsk/c1t0d0s0 /proc fd mnttab /dev/dsk/c1t0d0s5 swap swap /dev/dsk/c1t1d0s7 /dev/dsk/c1t0d0s7
kbytes used avail capacity 10086988 428609 9557510 5% 0 0 0 0% 0 0 0 0% 0 0 0 0% 20174761 5452 19967562 1% 18497672 16 18497656 1% 18497936 280 18497656 1% 70577241 1279298 68592171 2% 20174761 9 19973005 1%
Mounted on / /proc /dev/fd /etc/mnttab /var /var/run /tmp /opt /export/home
GPRS/UMTS
80
2. Make a note of the swap partition as well as other mounted partitions.

# cat /etc/vfstab #device device mount FS fsck mount mount #to mount to fsck point type pass at boot options # #/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes fd /dev/fd fd no /proc /proc proc no /dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no /dev/dsk/c1t0d0s1 swap no /dev/dsk/c1t0d0s5 /dev/rdsk/c1t0d0s5 /var ufs 1 no /dev/dsk/c1t0d0s7 /dev/rdsk/c1t0d0s7 /export/home ufs 2 yes /dev/dsk/c1t1d0s7 /dev/rdsk/c1t1d0s7 /opt ufs 2 yes swap /tmp tmpfs yes -
3. From df -k and /etc/vfstab identify the disk partitions for all critical file systems (/, /var, /usr, /opt) that are mounted. Make a note of the mounted critical file system partitions. From the above example capture: / - /dev/dsk/c1t0d0s0 swap - /dev/dsk/c1t0d0s1 /var - /dev/dsk/c1t0d0s5 /opt - /dev/dsk/c1t1d0s7 4. Calculate the combined disk space used for all the critical file systems. The critical file systems are - /, /var, /usr, /opt. This usually depends on the server installation. 5. Identify the unassigned and unmounted partitions that will be used for Solaris 9 Live upgrade using format. The recovered partitions (unmounted) after un-mirroring the server will be used for Solaris 9 BE creation. Please follow table Disk Mirroring Mapping for partition details.
# format < /dev/null

Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010183a01,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010186a81,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b0b1,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
411-5221-309
Standard
06.30 March 10, 2010
81
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0 6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0 10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 11. c1t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf786ffa,0
Note: Please make sure that each partition has a flag "wm" (except swap partition) before using it. The swap partition's flag should be "wu". Flag wm means read/write mountable Flag wu means read/write unmountable Here are steps to verify and correct partition flag:
zrc2s0pw# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf27c6c6,0 1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfa3b945,0 Specify disk (enter its number): 1 selecting c1t1d0 [disk formatted] Warning: Current Disk has mounted partitions. FORMAT MENU: disk type - select a disk - select (define) a disk type
partition - select (define) a partition table
GPRS/UMTS
82
GGSN/SCS pre upgrade checklists current format repair label analyze defect backup verify save inquiry volname !<cmd> quit format> verify Primary label contents: Volume name = < > - describe the current disk - format and analyze the disk - repair a defective sector - write label to the disk - surface analysis - defect list management - search for backup labels - read and display labels - save new disk/partition definitions - show vendor, product and revision - set 8-character volume name - execute <cmd>, then return
ascii name = <SUN36G cyl 24620 alt 2 hd 27 sec 107> pcyl ncyl acyl nhead nsect Part 0 1 2 3 411-5221-309 Standard = 24622 = 24620 = 2
= 27 = 107 Tag root swap Flag wm Cylinders 0 - 24615 Size 33.91GB 5.64MB 33.92GB 0 Blocks (24616/0/0) 71115624 (4/0/0) 11556
wu 24616 - 24619 wu wu 0 - 24619 0
backup -
(24620/0/0) 71127180 0
(0/0/0)
06.30 March 10, 2010
Nortel Networks Confidential 4 5 6 var usr wu wm wm 0 0 0 0 0 0 0 0
GGSN/SCS pre upgrade checklists (0/0/0) (0/0/0) (0/0/0) (0/0/0) 0 0 0 0
83
7 unassigned wm
To set these flags, please perform the following steps: #fomat >Specify disk (enter its number): <-----specify disk by entering number for choice > partition (or you can just enter 'p') > (enter number for partition) > Enter partition id tag[swap]: <----choose to change or keep remaining tag name > Enter partition permission flags[wu]: wm <---------change the flag to 'wm' here > Enter new starting cyl[24616]: (Hit Enter to select the default value) > Enter partition size[11556b, 4c, 5.64mb, 0.01gb]: (Hit Enter to select the default value) > partition> label <----type label at this prompt to save changes > Ready to label disk, continue? yes <-----type 'yes' here Exit format by entering q
If you want to use a new disk for the Solaris 9 BE, then follow section Appendix D: Creating a Partition on a New Disk for Disk Mirroring on page 600
Solaris 9 BE - Creating Solaris 9 BE with lucreate
Details of this section can be found in section Solaris 9 Boot Environment Creation 26, page 414. Please read this sections to get an idea of the Live
GPRS/UMTS
84
Upgrade software installation. This package contains the necessary executables needed for creating Solaris 9 BE. After installing the Live Upgrade software, the next step is to run the lucreate command. This will create the Solaris 9 BE partitions that will be upgraded on running luupgrade. Check the Disk Mirroring Mapping for Critical File Systems on page 5-70 and Disk Mirroring Mapping for Non-critical File Systems on page 5-70. The partitions that were entered in column Second submirror/ disk partition -Partition for Solaris 9 will be used in as the partitions in lucreate Here is an example: Disk Mirror Mapping Table
Critical file system Metadevice name of the mirror First sub-mirror / disk partition -- Partition for Solaris 8 d10/ c1t0d0s0 d15/ c1t0d0s5 d18/ c1t1d0s7 Second submirror / disk partition -- Partition for Solaris 9 d20/ c1t2d0s0 d25/ c1t2d0s5 d28/ c1t3d0s7
/ /var /opt
d0 d5 d8
lucreate syntax to use when creating Solaris 9 BE:
# lucreate -c solaris8 -m critical_fs_/:/dev/dsk/<partition>:ufs -m critical_fs_/var:/dev/dsk/<partition>:ufs -m critical_fs_/usr:/dev/dsk/ <partition>:ufs -m critical_fs_/opt:/dev/dsk/<partition>:ufs -n solaris9 Note: The critical file systems depends on the server installation. lucrate example:
# lucreate -c solaris8 -m /:/dev/dsk/c1t2d0s0:ufs -m /var:/ dev/dsk/c1t2d0s5:ufs -m /opt:/dev/dsk/c1t3d0s7:ufs -n solaris9
<END of Creating Solaris 9 BE with lucreate procedure>

411-5221-309 Standard 06.30 March 10, 2010
85
GPRS/UMTS
86
These sub-sections are referenced in Table 2 through Table 5 . They provide details for item checklists that require it. Upgrade readiness checkpoint #1 (14 days prior) 1
Checkpoint 1 item 1Verify GGSN/SCS software load
Verify the GGSN is running the required software Log on to the GGSN as admin.
#show version
The above command will display the version the GGSN is running at present The version should be either GGSNS 4.0.1, 4.1, 4.1.1 or 5.0. Here is an example that has a ggsns4.1.1 load.
# show version Shasta 5000: IP Services Operating System iSOS (tm), Version ggsns4.1.1-isos-build-9 Built on Fri Jul 15 17:49:59 CDT 2005 by shtbld Copyright (c) 1998-2000 Shasta Networks, Inc. Copyright (c) 2000-2004 Nortel Networks Corporation. All rights reserved. Patch Status: One or more cards have been patched. System booted from ata:/disk/image/G411_9/cmc System restarted by SCS resync Booted using configuration: primary Slot Port(s) Card Version Status ---- --------- ----- ------------------2 1,2,4 /SSC Ok 18:22:26,ggsns4.1.1-isos-build-9 3 2,3,4 /SSC Ok 18:22:26,ggsns4.1.1-isos-build-9 Software Version -------------------------------built on Jul 15 2005, built on Jul 15 2005,
Verify SCS is running the required software. Log on to the SCS Server as root
# cat /etc/shasta/scs.config | grep SCSHead # cd <path returned by the above command> # cd bin # cat version
This file will show, the present software of the SCS. Please refer to Table 3, SCS and GGSN Load Lineup, on page 23.
411-5221-309
Standard
06.30 March 10, 2010
87
Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35

Checkpoint 1 item 2Data to be pulled daily
The following data is to be pulled daily: PDP activation success rate counters PDP activation failure rate counters PDP deactivation success rate counters PDP deactivation failure rate counters Activation Success Activation Failure Alarms Log files Any other performance statistics the customer is interested in.
Please refer to - Check the stability and performance of Gn interface on page 558, for details on the commands required to get these counter values. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 3no special instruction
Checkpoint 1 item 4Verify the SCS installation profile
SCS has multiple server processes which should be installed on the same physical server, and LDAP should also be installed on the same physical server as SCS. Verify if all the SCS servers and LDAP are installed on the same physical server or not. If all the SCS Servers and LDAP are not installed on the same physical server, please contact Nortel Support team. To verify whether all the SCS Servers and LDAP are installed on the same physical server, please do the following: 1. Log on to SCS Server as root 2. Capture the SCS server system file /etc/shasta/scs.config.
GPRS/UMTS
88
GGSN/SCS pre upgrade checklists # cat /etc/shasta/scs.config
3. Determine the location of SCS server installation and capture the system file .scs.config.
# cat /etc/shasta/scs.config |grep SCSHead
# cd <path returned for SCSHead> # cd bin # cat .scs.config
Here is an example:
# cat .scs.config # # This file was generated during SCS installation. # Please do not modify manually. # SCSHead=/opt/shasta InstallDomainServer=yes InstallRegionServer=yes InstallMonitorServer=yes InstallPullServer=yes InstallLogServer=yes DomainServerIp=localhost RegionId=1 LDAPUsername="uid=admin,ou=Administrators,ou=TopologyManage ment,o=NetscapeRoot" LDAPPassword=admin LDAPRoot="uid=admin,ou=People,o=us.nortel.com" PullListenPort=4321 LogLogPort=4322 LogAccountPort=4323 RegionRootDir=/opt/shasta DBAdminPassword=admin MaximumHeapSize=512 SCSBackup=/opt/shasta/backup DBBackupTimeWait=150 DOMAIN_IP=localhost IIOP=0 LDAPPath=/opt/shasta/ldap/netscape/server4 LDAPServerName=slapd-server602 LDAPServerIp=localhost LDAPServerPort=389 LogUser=pmuser
411-5221-309
Standard
06.30 March 10, 2010
89
4. Observe the details that are high lighted in the above snap shot. InstallRegionServer, InstallDomainServer, InstallMonitorServer, InstallPullServer, InstallLogServer should have yes as value, which means all these servers are installed on this server. Also, check LDAPServerIp which should be localhost, which means LDAP is also installed on the same physical server. If the SCS physical server does not have all these servers and LDAP installed, please contact Nortel support team. 5. Verify /tftpboot and /tftpboot/patches exists on the SCS server.
# ls /tftpboot patches # ls /tftpboot/patches
If the GGSN has been software patched earlier, the patch zip files will be listed. If there is an error like:
/tftpboot: No such file or directory or /tftpboot/patches: No such file or directory
Create /tftpboot/patches manually using:

# mkdir -p /tftpboot/patches
Checkpoint 1 item 5Check if there are multiple patch servers on the SCS Server
This step is only required, if you are migrating the SCS Server to a new Physical server with a different IP. If you are upgrading the SCS Server on the same physical server or migrating to a new physical server with same IP as the old SCS Server, this step can be skipped. Logon to the SCS Client as device_owner Click on File and then SCS Configuration...
GPRS/UMTS
90
Click on Server Properties Tab. The following window will open.
Check if there are multiple Patch Servers on your SCS Server as shown in the above picture. If there is only one patch server, unlike in the above example, this step can be skipped. If there are multiple Patch servers running on your SCS Server, please contact Nortel Support Team. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 6Set the rlim_fd_max and rlim_fd_cur Kernel parameters
rlim_fd_max (Maximum File descriptors allowed) and rlim_fd_cur (Current File descriptors limit) are Solaris system parameters and can be found in file /etc/system. Verify if /etc/system has rlim_fd_max and rlim_fd_cur set to 4096.
# cd /etc # cat system | grep "rlim_fd_max" # cat system | grep "rlim_fd_cur"
If the system parameters are already set, the above commands will return an output similar to the output shown below:
# cat system | grep "rlim_fd_max" set rlim_fd_max=4096 # cat system | grep "rlim_fd_cur" set rlim_fd_cur=4096
411-5221-309
Standard
06.30 March 10, 2010
91
If the above commands do not return the parameter values (4096) or do not return any output, then the parameters must be added to /etc/system file. Use vi editor to add the following 2 lines at the end of the file. Note, if the value does not match 4096, modify the parameters to 4096.
set rlim_fd_max=4096 set rlim_fd_cur=4096
Note: If the kernel parameters have been updated, a server reboot is required. Please follow sectionRebooting the SCS server on page 210 If the customer has any concerns about changing these two kernel parameters, please contact Nortel Support team. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 7-Make a note of Allow tunnel terminatoin check box provisioning on all the trunk interfaces for each Gi ISP a. Determine all the Gi ISPs configured. To determine the Gi ISPs, login to the GGSN and issue the command show apn. Each APN is associated with an ISP. From the ISP column, make a note of the Gi ISP names.
b. Login to each Gi ISP from the SCS Client c. Navigate to the Trunk interface configuration for each GGSN that will be upgraded (Right click on each GGSN-> Configure-> Trunk Interface) d. Select each trunk interface and click the Edit button e. Make a note of the Allow tunnel termination check box option (checked or un-checked). These values may be needed during GGSN upgrade or rollback. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 8Trim Domain behavior clarification for GGSN 4.1.1 and GGSN 6.0
In GGSN 4.1.1, when MSISDN under APN anonymous RADIUS authentication is selected (under Access tab) and Trim Domain option on the RADIUS Profile is not selected, the username sent in the RADIUS Access
92
Request is the MSISDN number only (domain name is not appended with the username). With the above configuration, RADIUS server needs to be provisioned with the MSISDN username without the domain name. In GGSN 6.0, when MSISDN under APN anonymous RADIUS authentication is selected (under Access tab) and Trim Domain option on the RADIUS Profile is not selected, the username sent in the RADIUS Access Request is the MSISDN appended with the domain name. With this configuration, the RADIUS server needs to be provisioned with the MSISDN username appended with the domain name; for example: 41794938028@subdomain.com Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 9Check RADIUS Server mis-configuration
The objective of this checkpoint is to verify the RADIUS Server Secret set on the RADIUS Servers configuration on the RADIUS Profile are same for all the RADIUS servers with the same IP. If multiple RADIUS Profile contains RADIUS Servers with the same IP Address but different secrets, after the upgrade, the association between the RADIUS Profiles and the Access Groups will be cleared. To keep the Access Groups from being cleared after the upgrade, a change must be made so that RADIUS servers with same IP address have the same server secret. Note: The RADIUS server administrator may need to be contacted to verify the RADIUS server secret. 1. Log into SCS client using a user that has ISP User privilege. 2. On the left side of the SCS window, click on the Access Properties icon. 3. Under Access Properties, click on Access Groups. 4. Open the Access Groups one by one. 5. In the Access Group Configuration window, select Group Settings tab. Make a note of the RADIUS Profile associated to the Access Group. If there are multiple Access Groups, make a note of the associated RADIUS Profiles. 6. From Access Properties, click on RADIUS Profile. Select the RADIUS Profile and click Edit Click on RADIUS Servers tab Select the RADIUS servers in the list one by one and make a note of the IP address
411-5221-309 Standard 06.30 March 10, 2010
93
7. If there are multiple RADIUS Profiles with same RADIUS Server IP, then contact the RADIUS server administrator to get the server secret. Re-enter the RADIUS server secret for these RADIUS servers in the RADIUS Profile. 8. Repeat the above steps if you have multiple ISPs. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 10Patch Verification for G501_FF01435785ACT_INF: Cabcharge L2TP Authentication feature
This checkpoint is applicable to GGSNs currently on GGSN 5.0.1 only. Patch description: Patch G501_FF01435785ACT_INF alters the GGSN Anonymous RADIUS Authentication behavior. If the patch G501_FF01435785ACT_INF has been actived, the GGSN appends the APN name as the domain name to the anonymous username authentication options. This is applied to both the MSISDN and customer-defined anonymous username. The following rules also apply: For APNs provisioned with anonymous authentication, the anonymous username configured from the SCS client is always used, overriding any user name supplied by the mobile in the PCO IE of Create PDP Context request. When the User name/ Password option is selected under Anonymous Radius Authentication and the User name contains the following reserved strings: "MSISDN" - the actual MSISDN supplied by the mobile and the configured password will be used as the username/ password. "IMSI" - the actual IMSI supplied by the mobile and the configured password will be used as the username/ password. When L2TP is used, the appended anonymous authentication user name is also communicated to the LNS during L2TP tunnel negotiation. Note: When the above condition is true, then a SCS post upgrade check must be executed after SCS 6.0 upgrade (and prior to GGSN 6.0 upgrade). Please refer to Patch Verification for G501_FF01435785ACT_INF: Cabcharge L2TP Authentication feature for more details. In addition, a GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0.
GPRS/UMTS
94
Please refer to Patch Verification for G501_FF01435785ACT_INF: Cabcharge L2TP Authentication Feature on page 542. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 11Patch Verification for G501_01450778ACT_IFMGR: Increase the MTU Size of Gn IP Interface on GELC feature
This checkpoint is applicable to GGSNs currently on GGSN 5.0.1 only. Patch description: If one or more GELC card(s) are present on the GGSN and G501_01450778ACT_IFMGR patch is activated, the default MTU settings on the Gn interface configured on the GELC card/ port is set to1536. a. Verify if one or more GELC card(s) exists on the GGSN. Login to the GGSN and issue the command:
show card
Note: If the GGSN has one or more GELC cards, proceed to the next step. If the GGSN does not have a GELC card, skip this check point and proceed to the next checkpoint. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35 b. Verify if patch G501_01450778ACT_IFMGR has been actived. For details on patch verification, please refer to Verify patch status information on page 224. c. Login to the SCS client as the Gn ISP user. d. From Device Manager, double click on the GGSN, then click on the Trunk Interfaces tab. A list of turnk interfaces configured on the Gn ISP are displayed. e. Select the GELC card on the left pane, this will list the trunk interfaces configured on the GELC card/ port. f. Make a note of the trunk interfaces configured configured on a GELC card/ porton for the Gn ISP. g. Repeat the above steps for all the GGSNs managed by the SCS server. h. Mark a check in the last column in the checkpoint table after these steps are executed.
411-5221-309
Standard
06.30 March 10, 2010
95
Note: After SCS 6.0 upgrade and prior to the GGSN 6.0 upgrade, a SCS post upgrade check needs to be executed to modify the trunk interface MTU to match 1536. For details, please refer to Checkpoint 5 item 21, page 333. Note: A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_01450778ACT_IFMGR: Increase the MTU Size of Gn IP Interface on GELC feature. on page 543. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 12Patch Verification for G501_FF01567650ACT_IPCMC: TCP MSS Clamping feature
This checkpoint is applicable to GGSNs currently on GGSN 5.0.1 only. Patch Description: This feature provides the ability to configure the GGSN to modify or add the TCP MSS option for uplink and downlink packets to prevent IP fragmentation between the SGSN and GGSN for TCP based mobile subscriber packets (e.g. packets that are part of a http flow). Note: After SCS 6.0 upgrade and prior to the GGSN 6.0 upgrade, a SCS post upgrade check needs to be executed. Here the APNs configured on the GGSNs must be updated with the MSS value. Please refer to Patch Verification for G501_FF01567650ACT_IPCMC: TCP MSS Clamping feature on page 334 Note: A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_FF01567650ACT_IPCMC: TCP MSS Clamping feature on page 543. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 13Patch Verification for G501_FF01385577ACT_ERCMC: DCCv2 Envelope Reporting Feature
This checkpoint is applicable to GGSNs currently on GGSN 5.0.1 only. SOC and Patch verification instructions:
GPRS/UMTS
96
a. Verify if SOC key DIAMETER ENVELOPE REPORTING has been enabled on the SCS. For detailed steps, please refer to Add or Verify SOC key on page 223. If the SOC key has been activated, proceed to the next step. If the SOC key has not been activated, skip this checkpoint item and proceed to the next item.
b.
If the SOC key has been enabled, verify if patch G501_FF01385577ACT_ERCMC has been activated. For detailed steps, please refer to Verify patch status information on page 224.
c. If the patch has been activated, mark a check in the last column in the checkpoint table after these steps are executed. Review the note given below. If the patch has not been activated, skip this checkpoint item and proceed to the next item.
Note: If patch G501_FF01385577ACT_ERCMC has been activated: A SCS 6.0 post upgrade check must be executed to verify the SOC key has been migrated. Please refer to Patch Verification for G501_FF01385577ACT_ERCMC: DCCv2 Envelope Reporting Feature on page 336. A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_FF01385577ACT_ERCMC: DCCv2 Envelope Reporting Feature on page 543.
Checkpoint 1 item 14Patch Verification for G501_FF01368038ACT_INF: DCCv2 Customization Essentials Feature
This checkpoint is applicable to GGSNs currently on GGSN 5.0.1 only. SOC and Patch verification instructions: a. Verify if SOC keys DIAMETER CC RT CHARG and DIAMETER CC ESSENTIALS have been enabled on the SCS. For detailed steps, please refer to Add or Verify SOC key on page 223.
411-5221-309
Standard
06.30 March 10, 2010
97
If the SOC keys have been activated, proceed to the next step. If the SOC key has not been activated, skip this checkpoint item and proceed to the next item.
b.
If the SOC keys have been enabled, verify if patch G501_FF01368038ACT_INFC has been activated. For detailed steps, please refer to Verify patch status information on page 224.
c. If the patch has been activated, mark a check in the last column in the checkpoint table after these steps are executed. Review the note given below. If the patch has not been activated, skip this checkpoint item and proceed to the next item.
Note: If patch G501_FF01368038ACT_INF has been activated: A SCS 6.0 post upgrade check must be executed to verify the SOC key has been migrated. Please refer to Checkpoint 5 item 24, page 336. A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_FF01368038ACT_INF: DCCv2 Customization Essentials Feature on page 543.
Checkpoint 1 item 15Patch Verification for G501_FF01385579ACT_DCCCMC, G501_FF01385579ACT_DCCSSP: Parking Meter Charging Enhancement feature
This checkpoint is applicable to GGSNs currently on GGSN 5.0.1 only. SOC and Patch verification instructions: a. Verify if SOC keys TIME EVENT BILLING has been enabled on the SCS. For detailed steps, please refer to Add or Verify SOC key on page 223. b. If the SOC keys have been enabled, verify if patches G501_FF01385579ACT_DCCCMC and G501_FF01385579ACT_DCCSSP have been activated. For detailed steps, please refer to Verify patch status information on page 224.
c. Mark a check in the last column in the checkpoint table after these steps are executed.
98
Note: If patches G501_FF01385579ACT_DCCCMC and G501_FF01385579ACT_DCCSSP have been activated: A SCS 6.0 post upgrade check must be executed to verify the SOC key has been migrated. Please refer to Checkpoint 5 item 25, page 336. A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_FF01385579ACT_DCCCMC, G501_FF01385579ACT_DCCSSP: Parking Meter Charging Enhancement Feature on page 543.
Checkpoint 1 item 16Patch Verification for G501_FF01510131ACT_CPM: Consecutive Parking Meter feature
This checkpoint is applicable to GGSNs currently on GGSN 5.0.1 only. SOC and Patch verification instructions: a. Verify if SOC key TIME EVENT BILLING has been enabled on the SCS. For detailed steps, please refer to Add or Verify SOC key on page 223. b. If the SOC keys have been enabled, verify if patches G501_FF01385579ACT_DCCCMC and G501_FF01385579ACT_DCCSSP have been activated. For detailed steps, please refer to Verify patch status information on page 224.
c. Mark a check in the last column in the checkpoint table after these steps are executed. Note: If patches G501_FF01385579ACT_DCCCMC and G501_FF01385579ACT_DCCSSP have been activated: A new SOC key CTP TIME EVENT BILLING must be requested from Nortel. A SCS 6.0 post upgrade check must be executed to verify the SOC key has been migrated. Please refer to Checkpoint 5 item 25, page 336. A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0.
411-5221-309
Standard
06.30 March 10, 2010
99
Please refer to Patch Verification for G501_FF01510131ACT_CPM: Consecutive Parking Meter Feature on page 543. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 17Patch Verification for G501_FF01369144ACT_PPDCMC: Dual Coupon feature
This checkpoint is applicable to GGSNs currently on GGSN 5.0.1 only. SOC and Patch verification instructions: a. Verify if SOC keys Diameter CC SOC has been enabled on the SCS. For detailed steps, please refer to Add or Verify SOC key on page 223. b. If the SOC keys have been enabled, verify if patch G501_FF01369144ACT_PPDCMC has been activated. For detailed steps, please refer to Verify patch status information on page 224.
c. Mark a check in the last column in the checkpoint table after these steps are executed. Note: If patch G501_FF01369144ACT_PPDCMC has been activated: A SCS 6.0 post upgrade check must be executed to verify the SOC key has been migrated. Please refer to Checkpoint 5 item 27, page 338. A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_FF01369144ACT_PPDCMC: Dual Coupon Feature on page 543.
d. Repeat the above steps for all other GGSNs. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 18Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration
This checkpoint is applicable to GGSNs currently on GGSN 5.0.1 only.
GPRS/UMTS
100
a. Verify if patch G501_01505119ACT_SNTP has been activated. For detailed steps, please refer to Verify patch status information on page 224. b. If the patch G501_01505119ACT_SNTP has not been activated, skip this checkpoint and proceed to the next checkpoint. If the patch G501_01505119ACT_SNTP has been activated, verify if the Server IP Address under SNTP Client Configuration has an IP x.y.z.0: Login to the SCS client as device_owner user. From Device Manager, double click on the GGSN. On the Device tab, check the Server IP Address under SNTP Client Configuration. If the last octet of the IP address is 0 (similar to x.y.z.0): Mark a check in the last column in the checkpoint table after these steps are executed. A SCS 6.0 post upgrade check must be executed. Please refer to Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration on page 339. A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration on page 543.
c. Repeat the above steps for all other GGSNs. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 19Patch Verification for G501_01407739ACT_INF and G501_01595094AACT_AAA
This checkpoint is applicable to GGSNs currently on GGSN 5.0.1 only. Patch Description: Patches G501_01407739ACT_INF and G501_01595094AACT_AAA alters the default behavior of the Anonymous RADIUS authentication functionality on the GGSN. Note, this checkpoint is valid for APNs with Anonymous RADIUS Authentication enabled and one of the below conditions (Case 2 or Case 3) are true.
411-5221-309
Standard
06.30 March 10, 2010
GGSN/SCS pre upgrade checklists 101
a. Case 1: If the patch G501_01407739ACT_INF is deactivated in GGSN 5.0.1, there is not change in the default behavior (RFC compliant behavior). b. Case 2: Patch G501_01407739ACT_INF is active in GGSN 5.0.1. The note section below will be applicable if this patch has been activated. If the GGSN does not receive the password attribute in the PCO option of the GTP Create Request message, GGSN will send a padded and encrypted blank character as password to the RADIUS server in the RADIUS Access Request message. c. Case 3: Patches G501_01407739ACT_INF and G501_01595094AACT_AAA are active in GGSN 5.0.1. The note section below will be applicable if these patches have been activated. If the GGSN does not receive the password attribute in the PCO option of the GTP Create Request message, GGSN will send the password attribute and no password value to the RADIUS server in the RADIUS Access Request message. Note: After SCS 6.0 upgrade and prior to the GGSN 6.0 upgrade, a SCS post upgrade check needs to be executed. Here the APNs configured on the GGSNs will be updated. Please refer to Patch Verification for G501_01407739ACT_INF and G501_01595094AACT_AAA on page 339 A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_01407739ACT_INF and G501_01595094AACT_AAA. on page 544.
Checkpoint 1 item 20RADIUS Security Service Policy (firewall) verification on all connection ISP
a. Login to the GGSN and run the command show isp. Make a note of the ISP names. Note, some ISPs could have multiple GGSNs configured. b. Login to the SCS client as a connection ISP (ISPs except Gn, Ga and LI ISP). c. Click on Service Policies on the left pane. This will bring up Service Policy Manager. d. Double click on ISP Node Services folder in the left pane.
GPRS/UMTS
102
e. Expand the Service Policies list by clicking on the magnifying glass icon next to the Service Policies folder. This will list the Security service policy. Check if there are any security server policy listed in the right pane. f. If there are no security policies, login from the SCS client as the next connection ISP. Repeat the above steps. g. If there is a h. Click on Service Profile. Make a note if i. From Device Manager-> Click the region name under Regions-> Right click on the GGSN-> Configure-> Node services... j. Verify if either a Management Policy or ISP Node Policy has been applied. k. If the ISP does not have the Management Policy or ISP Node Policy configured, proceed to the next connection ISP. l. If the GGSN has a Management Policy or ISP Node Policy, select the on the Policy and click Edit. i. An ISP Firewall policy may be configured with a rule to allow packets from the ISP (_IspAddr) to a RADIUS server and reject any other packets. The rule may have the service set as RADIUS (udp) or could be set as (Any). ii. If a rule exists with the Service set as RADIUS, the Source as (_IspAddr), Destination as (Any or a network object), Action set as (Accept), a new rule must be added below this rule. To add a new rule below, right click on the rule and select Add Rule After. Use the rule (Src: _IspAddr, Dest: Any/ network object rule, Service: Any or RADIUS, Action: Accept) as reference to add the new rule. In the new rule, the source and destination of the reference rule is reversed. Here is a snapshot, rule 2 (highlighted in green). Note, the new rule must be added before the rule (Any/ Any/ Any/ Drop)
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Figure 1 ISP Firewall rule related to RADIUS
m. Repeat the above steps for other connection ISPs.
A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to RADIUS Security Service Policy (firewall) verification on all connection ISP. on page 544. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
Checkpoint 1 item 21Patch Verification for G411_01339974AACT_GTPACCT - SGSN Change Partial Billing verification
This checkpoint is applicable to GGSNs currently on GGSN 4.1.1 only. 1. Login to the SCS client using Device Owner privilege and select the Patch icon on the left image panel. 2. Select the Device tab and click on the Region name. Make a note of the active patch profile applied to the GGSN. 3. Select the Profile tab, click on the active patch profile and click Edit. 4. Click the drop down box next to Patchable Load. Select GGSNS4.1.1. 5. Verify if patch G411_01339974AACT_GTPACCT has been added to the patch profile and is activated. 6. If the above patch has been applied and activated, a post SCS upgrade check procedure needs to be executed in order to maintain the same behavior in GGSN 6.0 as GGSN 4.1.1. The details are provided in section SCS Post-upgrade/ Rollback Checkpoint 5 item 30, page 341. Return to Table 2, Upgrade readiness checkpoint #1 14 days prior to upgrade, on page 35
104
Upgrade readiness checkpoint #2 (7 days prior) 2

Make sure to pull the most recent version of this manual from:
http://app49.nortelnetworks.com/cgi-bin/HelmExpress/coll
Click Wireless & Mobility. Under General Packet Radio Service, click GGSN 6.0 Standard Return to Table 3, Upgrade readiness checkpoint #2 7 days prior to upgrade, on page 41
Checkpoint 2 item 2Verify list of CABs / Bulletins
Verify to see all the released bulletins for the present version of the GGSN and SCS. The CABs and Bulletins can be accessed on the Nortel Networks web site, by the Customer. The customers would have registered for and activated their accounts to access the CABs / Bulletins. Use the user information and log into the Nortel Networks web site for CABs / Bulletins. Return to Table 3, Upgrade readiness checkpoint #2 7 days prior to upgrade, on page 41
Checkpoint 2 item 3Critical test plan
Ensure critical call test plan is representative of customers network; and that the customer has identified a critical call test plan. Return to Table 3, Upgrade readiness checkpoint #2 7 days prior to upgrade, on page 41
Checkpoint 2 item 4no special instructions
Checkpoint 2 item 5Remote access
Identify with the customer that there is remote access capability into the customers GGSN, and login credentials have debug permissions.
411-5221-309
Standard
06.30 March 10, 2010
Checkpoint 2 item 8Verify sufficient GGSN/SCS space
Before downloading the new load to the GGSN/SCS, verify there is enough space on the GGSN/SCS for the software. If disk space must be cleared, contact the customer to free up disk space. The following are examples/ recommendations: 1. From the SCS Server: go to the SCS_ROOT directory and type: df -k. Verify that the system disk space for the SCS_ROOT is at least 4GB for large deployment, 3GB for medium and small deployments. Please refer to SCS Server preparation section of this document. 2. For a GGSN: i. Log in to the GGSN active and standby CMC, and enter the following command:
show storage
ii. Carefully analyze the output for Device Name: /disk iii. Check the current disk space usage: Current disk capcity level. Verify the current disk capacity is NORMAL level. iv. If the Current disk capcity level is close to, or above 65%, disk space clean up is required. Here are some pointers for disk space clean up. v. GGSN Core files: Verify if there are GGSN core files in the following directories:
dir /disk/core dir /disk/core1
GPRS/UMTS
106
dir /disk/core2
vi. If there are core files listed in the GGSN core directories, FTP all the core files to a remote server and notify Nortel support. vii. After FTP completes, delete all the core files using the following commands:
cd /disk/core remove file * cd /disk/core1 remove file * cd /disk/core2 remove file *
viii.Execute the command show storage to verify if the Current disk capcity level has improved (Current disk capcity level is 65% or below). If sufficient disk space has been cleared, proceed to Checkpoint 2 item 9 "Verify trending data will be collected", on page 3-107. If sufficient disk space has not been cleared, proceed to the steps detailed below: ix. GGSN GTP Accounting files: If a CGF server configured in a CGF/ GTP Profile under a Gn/ Ga ISP is unreachable, GGSN stores GTP accounting files in /disk/acct/gtp/cdrs. The GTP accounting files have a .XXU file extenstion (where XX are numbers). x. To verify GGSN GTP accounting files exists on disk, determine the Ga ISP name, then issue the command show gtpbill isp=<Ga ISP> command. From the command output, look for the Object State and Closed Unsent CDR files.
show isp show gtpbill isp=<Ga ISP>
Here is an example:
ggsn-158(SSU)# show gtpbill isp= ga-158 ... ISP: Name: ga-158 ISP ID: 5 IP Addr: 47.104.152.10
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Object State: ... Closed Unsent CDR files: ...
GGSN/SCS pre upgrade checklists 107 TO_CGF 413AAACR.13U 413AAACQ.13U
Note: If the Object State is set to TO_CGF, this means, the CGF server is online and connected correctly to the GGSN. If the Object State is set to DISK_ALL_EMERGENCY, the provisioned CGF server is offline. The user must debug any connectivity issues from the GGSN Ga ISP to the CGF serve as well as verify the CGF process status on the CGF server. Note: Make sure the Object State is back to TO_CGF prior to proceeding. xi. Verify Automated G-CDR Transfer option is enabled on the CGF Profile. Here are the steps. From the SCS client, log in to the Ga ISP. Navigate to Access Properties-> GTP Profile, select the GTP Profile configured and click Edit. Make a note of the CGF Profile name (CGF). Next, click the CGF Profile icon under the Access Properties. Select the CGF Profile retrieved from the GTP Profile, then click Edit. Click the Servers tab. Verify the Automated G-CDR Transfer option is enabled. If the option is not enabled, click on the check box to enable the option. Note, user has an option to select when the G-CDR files on GGSN disk are sent to the CGF server. When the Automated G-CDR option is enabled, if there are any G-CDR accounting files on the GGSN disk, and the CGF server is online, the G-CDR files are automatically sent to the CGF server. xii. Normally, G-CDR file transfer completion depends on the number of G-CDR files on the GGSN disk as well as stability of the CGF server connection to the GGSN Ga ISP. Execute show storage command to verify the current disk capacity is NORMAL level or the disk usage is equal to or less than 65%.
Current disk capcity level: NORMAL
Checkpoint 2 item 9Verify trending data will be collected
Verify with the COL/PM that trending data will continue to be gathered (i.e. Performance).
108

Checkpoint 2 item 11Full system backup of SCS Server Please refer to Full System backup and restore on page 393 for Full system backup. Return to Table 3, Upgrade readiness checkpoint #2 7 days prior to upgrade, on page 41
Checkpoint 2 item 13Verify the software loads for the Upgrade
The software that should be used for the upgrade for both GGSN and SCS is provided in a CD. The contents of the CD are detailed in this document. Please check the CD against the software listed. See GGSN Software Delivery on page 27 and SCS Software Delivery on page 24. Return to Table 3, Upgrade readiness checkpoint #2 7 days prior to upgrade, on page 41
Checkpoint 2 item 15Verify the SCS SNMP and Trap Daemon Ports
If the Solaris SNMP manager and a SCS SNMP Proxy server are both attempting to use the same TCP port, the SNMP process does not start and frequent error messages will appear at the console port. The same errors will be seen with Trap Daemon process too. Make sure that the SCS is not using standard Solaris Port numbers used for SNMP and Trap daemon which 161, and 162. Follow the step below to check the ports being used by the SCS.
411-5221-309
Standard
06.30 March 10, 2010
This step is executed on the SCS Client. Log on to the SCS client as device_owner. 1. On the main menu bar of the SCS client, open the File menu and select SCS Configuration. 2. Check the default ports for SNMP proxy, and trap daemon as shown in the figure. If the port numbers are not 161, and 162 as shown in the picture below, skip this step. If the port numbers are 161, and 162, proceed to the next step.
3. If the port numbers 161 and 162 were still configured, these will have to be changed. Nortel recommends to change them to port numbers 5001, and 5002. If customer has other preferences, any other free port can also be picked. Before changing the ports, verify that the ports are indeed free.
GPRS/UMTS
110
Do this by running the following commands on the SCS server command line. Log on to the SCS Server as root. /usr/bin/netstat -a|grep "*.5001" If this port is in use you will see output resembling the following: *.5001 Idle
If the port is free you will see no output, indicating the port is free. Repeat this process for the 5002 port. /usr/bin/netstat -a|grep "*.5002" If this port is in use you will see output resembling the following: *.5002 Idle
If the port is free you will see no output, indicating that the port is free. Assuming both ports are free, proceed with the next step. If either port is occupied contact Nortel next level of support, before proceeding with the procedure 4. On the SCS Client, Enter the value 5001 for the SNMP proxy port and 5002 for the SNMP trap daemon port as shown in the following figure
411-5221-309
Standard
06.30 March 10, 2010
111
Click on OK to close the dialog box and save the changes. Note: A corresponding change must be made to any customer network management system or third party system using SNMP to access the Shasta MIB information via the SCS Server processes. Return to Table 3, Upgrade readiness checkpoint #2 7 days prior to upgrade, on page 41
Checkpoint 2 item 16Verify the size limit and look through limit for LDAP
There are 2 options to verify the LDAP/ iPlanet size limit. One is the command line option and the other is the LDAP/ iPlanet console GUI option. If you are connected to the SCS server using a directly connected monitor, GUI option may be easier. Option 1: Command line option Determine the LDAP/ iPlanet installation directory and verify the sizelimit and lookthroughlimit.
112
# cat /etc/shasta/scs.config | grep LDAPPath # cd <Path returned for LDAPPath> # cat /etc/shasta/scs.config | grep LDAPServerName # cd <Path returned for LDAPServerName> # cd config # grep "\-1" *
An output similar to the following lines must be displayed. This indicates, file dse.ldif has the sizelimit and lookthroughlimit set to -1.
dse.ldif:nsslapd-sizelimit: -1 dse.ldif:nsslapd-lookthroughlimit: -1
Here is an example:
# pwd /opt/shasta/iplanet/slapd-wars-sc98/config # grep "\-1" * dse.ldif:nsslapd-sizelimit: -1 dse.ldif:nsslapd-lookthroughlimit: -1
Option 2: LDAP/ iPlanet console GUI option Determine the LDAP/ iPlanet installation directory and verify the sizelimit and lookthroughlimit.
# cat /etc/shasta/scs.config | grep LDAPPath # cd <Path returned for LDAPPath>
If you are connected to the SCS server from a directly connected monitor, skip the setenv DISPLAY command. If you are using xterm (Exceed, cygwin) to remotely connect to the SCS server using xterm:
# setenv DISPLAY <your computer IP address>:0.0
For example:
# setenv DISPLAY 47.102.75.171:0.0
./startconsole& Log in as admin/admin Double click on your server name on the left panel Double click on Server Group
411-5221-309
Standard
06.30 March 10, 2010
Double Click on the directory server. The following window will open
Click on the Configuration Tab. The following window will appear
Click on the Performance Tab. Set the Size Limit to -1 as shown in the following window and Click on Save.
114
Double Click on the Database Icon on the left Panel, and click on the Performance Tab. The following window will appear
411-5221-309
Standard
06.30 March 10, 2010
Change the Look Through Limit to -1 and Click on Save as shown in the following figure.
GPRS/UMTS
116
After saving the limits, exit the console. Click on the console in the menu and click on exit. Return to Table 3, Upgrade readiness checkpoint #2 7 days prior to upgrade, on page 41
Checkpoint 2 item 17Verify DNS configuration on SCS server
Verify that DNS is properly configured on the SCS server before the SCS is upgraded. The steps are: 1. Check whether the file /etc/hosts has an entry similar to: <your-SCS-IP-address> <your-SCS-Hostname> <yourSCSHostname>.<your-domain> loghost Add this information as necessary. 2. Check whether the file /etc/resolv.conf has entries similar to:
411-5221-309
Standard
06.30 March 10, 2010
domain <your-domain-from-hosts-file> (more domains if necessary) search <your-domain-from-hosts-file> one or more entries of your DNS server(s) nameserver <your-DNS-server-IP-address> Add this information as necessary. 3. Check whether the file /etc/nsswitch.conf has entries similar to: hosts: files dns Add this information as necessary. Return to Table 3, Upgrade readiness checkpoint #2 7 days prior to upgrade, on page 41
Checkpoint 2 item 18Delete any duplicate entries for LDAPServerName and LDAPPath if it exists
In the SCS system files - <SCS_ROOT>/bin/.scs.config and /etc/shasta/scs.config, determine there are no duplicate entries for the LDAPPath and LDAPServerName. Here is an example where there are duplicate entries:
# cat /etc/shasta/scs.config | grep SCSHead # cd <path returned by above cat command>/bin
Search for LDAPServerName duplicate entry in <SCS_ROOT>/bin/ .scs.config:

# cat .scs.config | grep LDAPServerName LDAPServerName=slapd-urc2y1th1 LDAPServerName=slapd-urc2y1th1
Search for LDAPPath duplicate entry in <SCS_ROOT>/bin/.scs.config:

# cat .scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet LDAPPath=/opt/shasta/iplanet
# cd /etc/shasta
Search for LDAPServerName duplicate entry in /etc/shasta/scs.config:

# cat .scs.config | grep LDAPServerName GPRS/UMTS Upgrade Manual GGSN6.0
118
GGSN/SCS pre upgrade checklists LDAPServerName=slapd-urc2y1th1 LDAPServerName=slapd-urc2y1th1
Search for LDAPPath duplicate entry in /etc/shasta/scs.config:

If there are any duplicate entries for LDAPPath or LDAPServerName in either: <SCS_ROOT>/bin/.scs.config or /etc/shasta/scs.config use vi editor and delete the line with the duplicate entry. There must be only 1 line for LDAPServerName and LDAPPath. Here is an example after the duplicate entries have been deleted.
# cd <SCS_ROOT>/bin # cat .scs.config | grep LDAPServerName LDAPServerName=slapd-urc2y1th1 # cat .scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet
# cd /etc/shasta/ # cat scs.config | grep LDAPServerName LDAPServerName=slapd-urc2y1th1 # cat scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet
Checkpoint 2 item 19Download Solaris 9 Recommended patch cluster
Download Solaris 9 recommended patch cluster from http://sunsolve.sun.com-> Support-> Patches and Updates-> Recommended Patch Clusters-> Solaris 9 The patch cluster is of zip format (9_Recommended.zip).
411-5221-309
Standard
06.30 March 10, 2010
Note: There could be multiple Solaris 9 options available at the download site, choose the one that indicates Solaris 9 (and a file size in MB) Login to the SCS server as root user. Determine a partition that has sufficient space. File 9_Recommended.zip sizes varies between 200 MB to 250 MB. On extracting the zip file, the extracted patch cluster will occupy around 550MB to 650 MB disk space. User df -k to determine the amount of disk usage and space available.
# df -k
In this example, the patch cluster 9_Recommended.zip is FTP'ed to / export/home

# cd /export/home
FTP 9_Recommended.zip to /export/home Extract the zip file

# unzip 9_Recommended.zip
This takes approximately 10-20 minutes depending on the server hardware.
Checkpoint 2 item 20Check policy sizes with the policy_size_check.sh tool
This checkpoint is valid for upgrade of SCS 4.1.1 to SCS 6.0. Skip this checkpoint if upgrading SCS 5.0.2 to SCS 6.0. Currently, the SCS limits a Content Based Billing policys size. If a policys size reaches 256Kbytes, it will not be sent to the GGSN. The policy_size_check.sh tool calculates the potential CBB policy size, showing its current size and the size it will become in its 5.0 format as a result of SCS upgrade. (Details about how to install and run the tool are shown as follow.) First, copy the policy_size_check tool software (policy_size_check.tar) on the CD to the working directory, for example, to the /tmp directory. And then install the policy_size_check.sh tool. See below for example input/output capture of tool installation. In this case the policy_size_check.tar has been copied from the CD to the /tmp directory. Insert the SCS 6.0 CD and find the CD mount point:
GPRS/UMTS
120
a. Create a directory in /tmp on the SCS server

# cd /tmp # mkdir policy_test
b. Use df -k to find the CD mount point. Example:

# df -k /vol/dev/dsk/c0t2d0/ggsn0060 407692 407692 0 100%
/cdrom/ggsn0060
c. Copy file policy_size_check.tar to /tmp/policy_test.

# cp /cdrom/ggsn0060/Solaris/policy_size_check.tar /tmp/policy_test
# cd /tmp/policy_test # ls -l total 28304 -rw-r--r-1 root policy_size_check.tar
other
14476288 Aug
9 16:30
d. Untar policy_size_check.tar
# x x x x x x x tar xvf policy_size_check.tar Readme, 352 bytes, 1 tape blocks SampleRun, 2522 bytes, 5 tape blocks lib, 0 bytes, 0 tape blocks lib/shastaChecker.jar, 14414301 bytes, 28153 tape blocks lib/SolidDriverChecker.zip, 50084 bytes, 98 tape blocks lib/xmlparserv2.jar, 660890 bytes, 1291 tape blocks policy_size_check.sh, 1526 bytes, 3 tape blocks
# ls -al total 29680 drwxr-xr-x 3 root drwxrwxrwt 8 root -r-xr-xr-x 1 2505 -r-xr-xr-x 1 2505 SampleRun drwxr-xr-x 2 2505 -r-xr-xr-x 1 2505 policy_size_check.sh -rw-r--r-1 root policy_size_check.tar
other sys 500 500 500 500 other
461 Nov 27 12:12 . 9478 Nov 27 12:13 .. 352 Sep 15 15:09 Readme 2522 Sep 15 15:09 342 Sep 15 15:09 lib 1526 Sep 15 15:09 15134720 Nov 27 12:02
e. Determine SCS installation directory and script policy_size_check.sh will require the SCS installation directory as an argument.
# cat /etc/shasta/scs.config | grep SCSHead
411-5221-309
Standard
06.30 March 10, 2010
The path returned in SCSHead is the SCS installation directory. Make a note this path. Here is an example:
# cat /etc/shasta/scs.config | grep SCSHead SCSHead=/opt/shasta/scs
e. Execute the policy_size_check.sh tool. This script needs to be provided with the current installation directory of the SCS server as the input parameter. The usage of the script is:
./policy_size_check.sh <Path_returned_for_SCSHead>
See example below. Make a note of any policy that will exceed the 256Kbyte limitation, and attempt to minimize its size before the upgrade For example, delete unused or unnecessary policy rules, URLs, etc.; see Nortel GGSN Provisioning Procedures for information on defining policies. Then re-run the tool to ensure that the resulting policy size will be within supported limits. Note that in this example, there is one policy (i.e. cisp_policy_wap) that will exceed the database limitations after upgrade, and will need to be modified before proceeding with the SCS upgrade.
# ./policy_size_check.sh /opt/shasta parameters to the database: jdbc:solid://localhost:1313/admin/ admin Here are the policy sizes: Policy Name ISP Type Current Size 5.0 Size --------------------------------------------------------------------------------------cbb_policy_wap cisp_wap CBB 71347 74987 pirr_test cisp_wap CBB 29301 30657 cisp_policy_wap isp-1 CBB 255098 267507 These following policies will exceed the database limitations after upgrade to 5.0: Name ISP -----------------------------cisp_policy_wap isp-1
GPRS/UMTS
122
Upgrade readiness checkpoint #3 (2 days prior) 3

Click Wireless & Mobility. Under General Packet Radio Service, click GGSN 5.0 Standard Return to Table 4, Upgrade readiness checkpoint #3 2 days prior to upgrade, on page 44
Checkpoint 3 item 2Verify CABs / Bulletins
Verify to see all the released bulletins for the present version of the GGSN and SCS. The CABs and Bulletins can be accessed on the Nortel Networks web site, by the Customer. The customers would have registered for and activated their accounts to access the CABs / Bulletins. Use the user information and log into the Nortel Networks web site for CABs / Bulletins. Return to Table 4, Upgrade readiness checkpoint #3 2 days prior to upgrade, on page 44
Checkpoint 3 item 3no special instructions Checkpoint 3 item 4no special instructions Checkpoint 3 item 5no special instructions Checkpoint 3 item 6no special instructions Checkpoint 3 item 7no special instructions Checkpoint 3 item 8no special instructions
Checkpoint 3 item 9Patch inclusion / exclusion review of Non-R status patches
The Upgrade team must conduct a patch inclusion / exclusion review of all non-R status patches for GGSNS4.1.1 (if the current GGSN(s) are on GGSN4.1.1 or GGSNS5.0.1 (if the current GGSN(s) are on GGSN5.0.1); this review must include Nortel GPS. Explicit risk / benefit of each non-R status must be ascertained.
411-5221-309
Standard
06.30 March 10, 2010
Checkpoint 3 item 11SCS server hostname modification if necessary
Please refer to Checkpoint 0 item 7, page 57 for verification steps to determine if there is a hostname mismatch between the LDAP (or iPlanet) instance and the SCS server hostname. Note: Please make a note of the SCS server hostname (from the uname a command). It is manditory that the SCS server hostname must match the LDAP (or iPlanet) instance during SCS upgrade. After SCS server upgrade, it is recommended that the SCS hostname and LDAP (or iPlanet) instance name match. If it is necessary to change the hostname back, please refer to Upgrade readiness checkpoint #6 after it is determined the SCS server will not be rolled back to Solaris 8 on page 308 Note: When the hostname of the SCS server is modified, a server reboot is necessary. Please plan this during a maintanence window. If there is a hostname mismatch, please execute the following steps to modify the SCS server hostname to match the LDAP (or iPlanet) server instance. A. The following Solaris system files must be modified in order to change the server hostname.
File File File File File File File 1: 2: 3: 4: 5: 6: 7: /etc/hosts /etc/nodename /etc/inet/hosts /etc/inet/ipnodes /etc/net/ticlts/hosts /etc/net/ticots/hosts /etc/net/ticotsord/hosts
The hostname must match the LDAPServerName returned from the following command. This command will return the LDAP (or iPlanet) server instance name.
GPRS/UMTS
124
Use vi editor to modify the current hostname to the hostname matching the LDAP (or iPlanet) server instance name.
File 1: /etc/hosts
File /etc/hosts is a symbolic link to /etc/inet/hosts. Make sure /etc/hosts is a symbolic link using:
# ls -la /etc/hosts lrwxrwxrwx 1 root hosts -> ./inet/hosts root 12 Mar 29 23:19 /etc/
If file /etc/hosts is not a symbolic link similar to the output captured below,
# ls -al hosts -r--r--r-1 root sys 74 Mar 29 15:17 hosts
then both /etc/hosts and /etc/inet/hosts files have to be modified. For file /etc/hosts, two scenarios are presented. a. File /etc/hosts does not have the hostname returned for LDAPServerName. b. File /etc/hosts has the hostname returned for LDAPServerName but is not set as the primary hostname. Note: In both cases, file /etc/hosts must have an alias loghost. a. If the hostname returned for LDAPServerName is not provisioned in /etc/ hosts, then modify /etc/hosts file: i. Add an entry for the hostname returned for LDAPServerName. ii. The IP address for this hostname must match the SCS server IP address. iii. Add the alias loghost to this hostname. Example 1: Here, the hostname matching LDAPServerName (zngds0nn) is not present in /etc/hosts. The primary hostname is set to zrc2s0u9. The primary hostname has the alias loghost. The LDAP server instance name is:
# cat /etc/shasta/scs.config | grep LDAPServerName | cut -f 2- -dzngds0nn 411-5221-309 Standard 06.30 March 10, 2010
# cat /etc/hosts # # Internet host table # 127.0.0.1 localhost #current hostname 192.168.6.15 zrc2s0u9 10.128.16.38 10.128.25.62 10.128.26.71 gre vlan ipsec
loghost zrc2s0u9.us.nortel.com
Here is the file /etc/hosts after modification:

# cat /etc/hosts # # Internet host table # 127.0.0.1 localhost #LDAP server instance 192.168.162.35 zngds0nn #current hostname 192.168.6.15 zrc2s0u9 10.128.16.38 10.128.25.62 10.128.26.71 gre vlan ipsec
zngds0nn.us.nortel.com
loghost
zrc2s0u9.us.nortel.com
b. If the hostname returned for LDAPServerName is provisioned in /etc/hosts but does not have the alias loghost: i. Update /etc/hosts file to add the alias loghost ii. Remove the alias loghost from the current hostname. Example 2: Here, the hostname matching LDAPServerName is present in /etc/hosts but it does not have the alias loghost. The current hostname is zrc2s0u9 has the alias loghost. LDAP server instance is installed with hostname zngds0nn.
# cat /etc/hosts # # Internet host table # 127.0.0.1 localhost #current hostname GPRS/UMTS Upgrade Manual GGSN6.0
126
GGSN/SCS pre upgrade checklists 192.168.6.15 zrc2s0u9
Nortel Networks Confidential loghost zrc2s0u9.us.nortel.com
#LDAP server instance 192.168.162.35 zngds0nn 10.128.16.38 gre 10.128.25.62 vlan 10.128.26.71 ipsec
The LDAP server instance name is:

# cat /etc/shasta/scs.config | grep LDAPServerName | cut -f 2- -dzngds0nn

# cat /etc/hosts # # Internet host table # 127.0.0.1 localhost #current hostname 192.168.6.15 zrc2s0u9 #LDAP server instance 192.168.162.35 zngds0nn 10.128.16.38 gre 10.128.25.62 vlan 10.128.26.71 ipsec
loghost
B. All occurrences of the current hostname must be modified with the LDAP (or iPlanet) server instance in the following system files:
File 2: /etc/nodename File 3: /etc/inet/hosts <- If /etc/hosts is a symbolic link and has already been modified, skip this file.
File File File File
4: 5: 6: 7:
/etc/inet/ipnodes /etc/net/ticlts/hosts /etc/net/ticots/hosts /etc/net/ticotsord/hosts
C. Make a directory in /var/crash to match the LDAP instance hostname.
411-5221-309
Standard
06.30 March 10, 2010
# mkdir -p /var/crash/<LDAP instance hostname>
Here is an example capture, the hostname is taken from the above example:
# mkdir -p /var/crash/zngds0nn
D. A reboot of the server is required. Perform a reboot of the server by following section Rebooting the SCS server on page 210
E. After server reboot, verify the SCS server host name has been modified. Execute the following commands to verify the hostname.
# uname -a | awk '{print $2}' # hostname
<End of hostname modification procedure> Return to Table 4, Upgrade readiness checkpoint #3 2 days prior to upgrade, on page 44
GPRS/UMTS
128
Upgrade readiness checkpoint #4 (night before the upgrade) 4

Click Wireless & Mobility. Under General Packet Radio Service, click GGSN 5.0 Standard
Return to Table 5, Upgrade readiness checkpoint #4 night before the upgrade, on page 46
Checkpoint 4 item 2Verify critical call test plan executed successfully
Verify with the customer that the critical call test plan was successfully executed with no issues prior to the upgrade. Return to Table 5, Upgrade readiness checkpoint #4 night before the upgrade, on page 46
Checkpoint 4 item 3Confirm support and connectivity available
Confirm that your next level of support is in place, and that remote connectivity to the GGSN, and SCS is still available and functional. Return to Table 5, Upgrade readiness checkpoint #4 night before the upgrade, on page 46
Checkpoint 4 item 4no special instructions Checkpoint 4 item 5no special instructions
Checkpoint 4 item 6Display event log
Log into the GGSN CLI. For details refer to Nortel GGSN Provisioning Procedures, 411-5221-927. The show log event command displays a
411-5221-309 Standard 06.30 March 10, 2010
history of what has been occurring on the node since the last reboot. The event logs are not always abnormal. When a node is rebooted or resync, the current event log is moved to the name EVENT.0 (stored in the logs directory) and a new event log is started. The GGSN will store up to 4 old logs (EVENT.0, EVENT.1, EVENT.2 and EVENT.3). Once this threshold is hit, EVENT.2 is moved to EVENT.3 and the old EVENT.3 is removed from the file system. When viewing the log, look for events that are labeled CRITICAL and WARNING. Some of the WARNING events are for information purpose that you can ignore. Be sure to read and understand the error message as best as possible. Once you understand the log message, perform further troubleshooting by using other show commands. Always be prepared to make logs available to Nortel support when a problem or other issue occurs.
# show log event Mon 16-Oct-2000 15:45:59 14/1/1:User Manager 0 1 1 INFO admin logged in on /pty/tel00.S (from 99.82.25.108) Mon 16-Oct-2000 15:19:19 14/1/1:User Manager 0 2 1 INFO admin logged out from /pty/tel00.S Mon 16-Oct-2000 15:01:22 14/1/1:User Manager 0 1 1 INFO admin logged in on /pty/tel00.S (from 99.82.24.202)
Checkpoint 4 item 7Display primary configuration
The show config primary command displays the current configuration loaded on the GGSN. If there is a configuration error that you cannot resolve, use show config primary to capture the configuration information and provide it to the Nortel support team. Return to Table 5, Upgrade readiness checkpoint #4 night before the upgrade, on page 46
Checkpoint 4 item 8 Check and remove the obsolete SCS processes and LDAP processes auto startup files
The SCS Server might have obsolete auto startup files. We dont need those files any more. Those files may cause the GGSN 6.0 SCS process startup failure after Solaris OS reboot. 1. Check the obsolete SCS auto startup files. If the any of the following files exists, remove it.
# ls -la /etc/init.d/scsServer GPRS/UMTS Upgrade Manual GGSN6.0
130
GGSN/SCS pre upgrade checklists # rm -f /etc/init.d/scsServer
# ls -la /etc/rc2.d/S91scsServer # rm -f /etc/rc2.d/S91scsServer
# ls -la /etc/rc0.d/K91scsServer # rm -f /etc/rc0.d/K91scsServer
# ls -la /etc/rc1.d/K91scsServer # rm -f /etc/rc1.d/K91scsServer
# ls -la /etc/rcS.d/K91scsServer # rm -f /etc/rcS.d/K91scsServer
2. Check the obsolete LDAP auto startup files. If the any of the following files exists, remove it.
# ls -la /etc/init.d/ldapServer # rm -f /etc/init.d/ldapServer
# ls -la /etc/rc2.d/S90ldapServer # rm -f /etc/rc2.d/S90ldapServer
# ls -la /etc/rc0.d/K90ldapServer # rm -f /etc/rc0.d/K90ldapServer
# ls -la /etc/rc1.d/K90ldapServer # rm -f /etc/rc1.d/K90ldapServer
# ls -la /etc/rcS.d/K90ldapServer # rm -f /etc/rcS.d/K90ldapServer
411-5221-309
Standard
06.30 March 10, 2010
Checkpoint 4 item 9 Check and remove the mirrors of the critical file
systems
The file systems of SCS Server might have mirrors. The mirrors of the critical file system(/, /opt, /usr and /var) must be removed before upgrading Solaris 8 to Solaris 9. After upgrade, we could create mirrors for them again. Check the mirrors by the following command. # metastat Please save the output for re-mirroring after the upgrade. If there is no output or metastat: not found on the console, it implies that the file systems have no mirrors, otherwise, see Appendix C: Unmirroring the File Systems on page 586 for the un-mirroring instruction. Return to Table 5, Upgrade readiness checkpoint #4 night before the upgrade, on page 46
Checkpoint 4 item 10Solaris 9 Boot Environment creation.
The Solaris 9 Boot Environment creation needs to be taken at the night before the upgrade. The duration of the Solaris 9 BE creation takes about 3 and a half hours depending on the server hardware. Please perform the following steps to take the Solaris 9 BE creation. Note: Below steps 1 through 3 can be skipped if the SCS server is OS unhardened. Please refer to section Determine if OS Hardening is enabled on the SCS server on page 61 1. Stop the SCS Server and LDAP server. Since the Solaris 8 OS unhardening of next step will go to single user mode, we need to stop the LDAP server and SCS Server before we unharden the OS. Stop the SCS Server by the commands:
# cd SCS_ROOT/bin # ./SCSAdmin stop
Stop the LDAP Server by the commands:
GPRS/UMTS
132
GGSN/SCS pre upgrade checklists # SCS_ROOT/bin/LDAPWatch-disable # LDAP_ROOT/stop-admin # LDAP_ROOT/slapd-<hostname>/stop-slapd
2. Solaris 8 OS unhardening. On the current running SCS Server, Solaris 8 OS is hardened. We need to unharden the Solaris 8 OS system before creating the new Solaris 9 BE. The OS unhardening action should be taken at Solaris OS single user mode. When the unhardening is done, the system needs to reboot. In the duration of the Solaris 8 OS unhardening, the SCS server is not in service. See OS unhardening procedure on Solaris 8 on page 354 for the instruction. 3. Start up the LDAP server and SCS server if auto-startup is not set This step is needed only if the SCS server cannot startup automatically upon the OS booting up. If the SCS server process has been set to autostartup, ignore this step. Check SCS Server status by the command.
# cd SCS_ROOT/bin # ./SCSAdmin status
If SCS Server is not started, start up the LDAP server and then the SCS server by the commands. # cd LDAP_ROOT # ./start-admin # cd LDAP_ROOT/slapd-<hostname> # ./start-slapd
# cd SCS_ROOT/bin # ./SCSAdmin start
4. Remove LDAP and SCS watches. Rolling Upgrade strategy is an optional choice. It is to meet the customers requirement to reduce the SCS server downtime to minimum during upgrade. For Rolling Upgrade, SCS Server is still alive for monitoring during SCS 5.0 software upgrade. If the decision is to use Rolling Upgrade, remove all the LDAP Watches and SCS Watches from crontab. If the decision is to do just a silent upgrade without rolling SCS directory and LDAP instance, only remove all the LDAP watches from the crontab.
411-5221-309
Standard
06.30 March 10, 2010
SeeRemove All the LDAP Watches and SCS Watches from the crontab on page 207 5. Create the Solaris 9 Boot Environment. This step will create the Solaris 9 BE on current system. See Solaris 9 Boot Environment Creation on page 414 for instruction. Return to Table 5, Upgrade readiness checkpoint #4 night before the upgrade, on page 46
GPRS/UMTS
134
411-5221-309
Standard
06.30 March 10, 2010
135

This section contains details on the server requirements for the SCS server upgrade and details the upgrade and rollback strategy as well. Please read through this section and make sure all requirements are satisfied. The following upgrade and rollback procedures are covered: SCS 4.1.2 to SCS 6.0 upgrade SCS 5.0.2 to SCS 6.0 upgrade Support for Sun Netra T5220: SCS 6.0 to SCS 6.0.1 upgrade and migration to Solaris 10 SCS rollback from current SCS release to previous release Migration of SCS to a new host with same IP address Migration of SCS to a new host with different IP address Upgrade SCS 4.1.2 to 6.0 on two servers with same IP address
Upgrade SCS 5.0.2 to SCS 6.0 on two servers with same IP address SCS new installation procedure details: Support for Sun Netra T5220: Green field deployment of SCS 6.0.1 on Solaris 10.
SCS and GGSN Load Lineup

Please refer to SCS and GGSN Load Lineup on page 23
4 4
SCS Text Convention
The SCS upgrade procedures in this document show example command input and output. It may not match your installation exactly. When a command or a parameter must be entered by the user, the command or parameter is shown in bold text. For example, to change directory to the location of the scs.config file, use: # cd /etc/shasta The # character is used as the default Unix command prompt. When an installation-specific parameter is required, the parameter is enclosed in angled brackets. Use the value appropriate to your installation without the angled brackets.
GPRS/UMTS
136
An example of entering a parameter is: IP Address of host: <host IP address> where the host IP address is 10.1.23.3 would be entered: IP Address of host: 10.1.23.3
SCS Installation Directories

To remove dependencies of this document on root directory structures, the following nomenclature is used:
1. <SCS_ROOT> indicates the directory which contains the SCS installation prior to SCS 6.0 - SCS 4.1.2 or SCS 5.0.2, for example:
Current SCS 4.1.2 installation = <SCS_ROOT> = /opt/shasta/scs
or
Current SCS 5.0.2 installation = <SCS_ROOT> = /opt/shasta/scs502
2. <SCS6.0_ROOT> indicates the directory which contains the SCS 6.0 installation, for example:
<SCS6.0_ROOT> = /opt/shasta/scs6.0 or <SCS6.0_ROOT> = /opt/shasta/scs6.0.1 <-For SCS 6.0.1
3. <LDAP_ROOT> will indicate the directory specified at Netscape Directory server installation for SCS 4.1.2, for example:
<LDAP_ROOT> = /opt/shasta/ldap
4. <IPLANET_ROOT> will indicate the directory where the iPlanet 5.1 is installed on the SCS 5.0.2, for example:
<IPLANET_ROOT> = /opt/shasta/iplanet
The installation directories are determined by the following step:
411-5221-309
Standard
06.30 March 10, 2010
137
For SCS 4.1.2-> 6.0 Upgrade: The absolute path of the SCS and LDAP 4.16 on the current SCS 4.1.2 can be found in the file: /etc/shasta/scs.config as the value of:
SCSHead=<absolute path of SCS 4.1.2 installation> LDAPPath=<absolute path of LDAP installation>
For SCS 5.0.2-> 6.0 Upgrade: The absolute path of the SCS and iPlanet5.1 on the current SCS 5.0.2 can be found in the file: /etc/shasta/scs.config as the value of:
SCSHead=<absolute path of SCS 5.0.2 installation> LDAPPath=<absolute path of iPlanet installation>
Symbolic Link For compatibility with other Nortel products, an additional soft link, /shasta, must be created to the SCS parent directory. Verify if a soft link already exists for /opt/shasta.
# ls /shasta ldap scs
If you get an error while executing ls, then create the soft link as in the following example:
# ls /shasta /shasta: No such file or directory
Create a soft link using:

# ln -s /opt/shasta /shasta
At this point, <SCS_ROOT>, /shasta/scs and /opt/shasta/scs (or /opt/shasta/scs502) should all be interchangeable for the purposes of this document. So, where ever SCS is installed, /shasta/scs is a valid path to the scs installation. The requirement is that /shasta/scs be a valid path to the SCS install directory. Note: Many of the scripts which output information display the absolute paths. So the user should remember that an absolute path and a link to that path are interchangeable.
GPRS/UMTS
138
Overall upgrade strategy for SCS

This section describes how to proceed with the SCS upgrade. This procedures outline SCS 4.1.2 upgrade to SCS 6.0 and SCS 5.0.2 to SCS 6.0 upgrade. Rollback procedures are also outlined.
Figure 3 SCS Upgrade Strategy for upgrade from SCS 4.1.2 to SCS 6.0
Backup SCS 4.1.2 and LDAP 4.16
Create/Upgrade Solaris 9 BE
Upgrade SCS/LDAP servers
Activate Solaris 9 BE and reboot
Figure 4 SCS Upgrade Strategy for upgrade from SCS 5.0.2 to SCS 6.0
Backup SCS 5.0.2 and iPlanet 5.1
Rolling upgrade of SCS server Stop SCS 5.0.2 Start SCS 6.0
411-5221-309
Standard
06.30 March 10, 2010
139
Before the SCS upgrade is done, the upgrade Pre-checks have to be executed 28/14/7/2/1 days prior to the upgrade, and on the night of the upgrade. Refer to: Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32 Upgrade readiness checkpoint #1 14 days prior to upgrade on page 35 Upgrade readiness checkpoint #27 days prior to upgrade on page 41 Upgrade readiness checkpoint #32 days prior to upgrade on page 44 Upgrade readiness checkpoint #4night before the upgrade on page 46 - for all the checks needed to be done, and detailed steps for each check. SCS upgrade / Rollback options The SCS upgrade options provided in this document consider the scenarios which are listed below. For each of the SCS upgrade scenarios, rollback procedures are also documented in different tables. The rollback tables are documented after the upgrade tables. SCS upgrade steps table This section describes the various parameters used in the upgrade steps table. Please go through the description to understand the SCS upgrade tables. Each SCS scenario has the following four sections. Overview Pre-conditions Table of upgrade procedures Table of roll-back procedures
The procedure tables (for upgrade and rollback) list the steps in order. Each step has: Step - the number of the step Duration, Tot- the total duration of the step in Hours and Minutes Duration, SL - Supervision Loss, or the duration that the SCS will be unable to manage the GGSN network. Duration, DT - Downtime, or the duration that an affected SCS or GGSN is out of service. Procedure - the section number and title of the procedure. Refer to each section individually for the detailed procedures.
140
Note: Procedure references in this section are actually hypertext links. If viewing this manual in PDF on your computer, clicking on a blue procedure reference will take you directly to that section (note that the cursor changes to a hand with a pointing index finger ( ) when positioned over a hyperlink). Then, when you are done, clicking on the black navigation arrow in the Acrobat toolbar ( ) takes you back to where you were before you began. To assist managing maintenance window durations, suitable stopping points are noted between appropriate steps. In all cases, the user performing the SCS upgrade must have root privilege to perform the upgrade. OS Hardening is an optional final step in all scenarios and is described in OS Hardening of GGSN SCS Server on page 348.
Overall Rollback Strategy

The overall steps in the Rollback the SCS are: 1. Rollback SCS Clients. Refer to SCS client rollback on page 357. 2. Rollback SCS Server. Refer to Rollback SCS 6.0 to SCS 4.1.2 after Solaris 9 Upgrade on page 363.
Supported SCS upgrade scenarios

The SCS server upgrade is supported for three scenarios. The following are the three scenarios: SCS Upgrade on the Same Physical Server on page 161. Migrating SCS to a new physical server with Same or Different IP address on page 169
SCS server upgrade at a high level 1. Identify the SCS upgrade scenario and get an overview of the upgrade and rollback steps provided in this document. 2. Upgrade the SCS Server: Each upgrade scenario has a table that details the upgrade steps. Follow the table of upgrade steps to complete the upgrade. Click on the links above to proceed to the table of steps for your SCS upgrade scenario.
411-5221-309
Standard
06.30 March 10, 2010
141
3. Upgrade the SCS Client(s): Client upgrade is also done as part the SCS upgrade steps. Though SCS supports upgrade to the same physical server or migration to a different physical server, most times SCS upgrade will be on to the same physical server.
GPRS/UMTS
142
SCS server preparation: Migration of the current SCS to new hardware or New Install of SCS on new
SCS server preparation: Migration of the current SCS to new hardware or New Install of SCS on new hardware 5
For a new server installation that is serving as the target of migration from a different server, it is recommended that the directory structures are identical to the original installation. Before installation The following information needs to be determined and set before installing iPlanet and SCS. Do not change these parameters which will effect the functioning of the SCS Server. Root user id uses csh shell Machine IP Address Host name Domain name Disk partitioned space
Network requirements for LDAP/SCS: DNS name server: It is recommended to enable DNS on the SCS server network. The configuration and operation of the LDAP process uses the DNS name server to resolve the hostname. The 3rd party LDAP software provider documentation highly recommends it and the GGSN/SCS documentation is written with configuration and examples based on the presence of the DNS nameserver for the LDAP Server process. The server domain name is set in the files /etc/hosts and /etc/resolv.conf Here is an example:
# cat /etc/hosts 127.0.0.1 localhost 47.104.70.61 zrc2s0px zrc2s0px.us.nortel.com loghost
# cat /etc/resolv.conf domain us.nortel.com nameserver 47.103.121.21 nameserver 47.103.120.20 nameserver 47.103.128.21
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialSCS server preparation: Migration of the current SCS to new hardware or New Install
Hardware Requirements for SCS The following is the nominal SCS requirements. The SCS runs on a Sun Microsystems server. Suns offerings are continuously changing, and Nortel is continually evaluating these offerings. Contact your Nortel Account team to determine the optimal recommended and supported solution for your network. The supported hardware and minimum recommended hardware configuration is: SunFire V890, SunFire V880, SunFire V250, Netra 240, Sun Enterprise T5220 Note: Sun E250 and E450 hardware platforms are not supported for GGSNS6.0. Note: Sun Netra T5220 is shipped with Solaris 10. The T5220 is only supported on Solaris 10 (Full server tape backup is not supported). Around 4 to 8 gigabytes memory Optional: 20GB 4-mm DDS-4 internal/ external tape drive
System settings needed File /etc/passwd contains the root user shell set as csh: root:x:0:1:Super-User:/:/usr/bin/csh File /etc/nsswitch.conf contains: hosts: file dns example: hosts:file dns File /etc/resolv.conf contains: domain <domain name> example: domain my.company.com File /etc/hosts contains: <machines static ip address> <hostname> <fqdn> loghost example: 99.100.100.100 scshost scshost.my.company.com loghost
GPRS/UMTS
144
SCS server preparation: Migration of the current SCS to new hardware or New Install of SCS on new
Disk partition sizing Table 12 lists the minimum recommended disk space for the SCS server software.
Table 12 Recommended SCS server software disk space Deployment Number of GGSNs Swap Space Minimum Required 4 - 8 GB 4 - 8 GB 1 - 2 GB Recommended Minimum /opt 8 GB 8 GB 8 GB
Large Medium Small
15-20 Devices or multiple Regions 7-10 Devices with Maximum of 1 Region 1 or 2 Devices with limited subscribers
Table 13 Partition table for T5220 Slice 0 1 2 3 4 5 6 7 /opt 50 GB /var 500 MB 22 GB Partition Name / swap Size 45 GB 16 GB
For detailed instructions for migrating the SCS to a new hardware platform, please refer to Migrating SCS to a new physical server with Same or Different IP address on page 169
Overview of SCS New Install and Migration procedure

1. Install Solaris 9/ 10. SCS is supported on Solaris 10 currently on Sun T5220.
Is the new hardware is Sun T5220, install Solaris 10 operating system. Refer to Appendix S: Solaris 10 Installation on page 745 for details.
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialSCS server preparation: Migration of the current SCS to new hardware or New Install
If the new hardware is not Sun T5220 and is one of the supported hardware listed in Hardware Requirements for SCS on page 143, install Solaris 9 operating system. 2. Install Solaris recommended patches. Refer to Install Recommended Patches for Solaris 9 and Solaris 10 on page 452 3. Install SCS 6.0 or 6.0.1. If the new hardware is Sun T5220, perform a new installation of SCS 6.0.1. For details, please refer to Appendix T: Perform SCS 6.0.1 new installation on page 764 If the new hardware is not Sun T5220, perform a new installation of SCS 6.0. For details, please refer to Appendix P: Perform a SCS 6.0 new install on page 704 4. In case of migration, restore database and migrate the GGSN(s). For details, please refer to Appendix U: SCS 6.0.1 Database Migration Example on page 777 5. For new installations, provision the GGSN following the Provisioning Procedure NTP - 411-5221-92.
GPRS/UMTS
146

Before starting the SCS upgrade prechecks, determine:
Pre-requisite: Ensure the Critical call test plan executed successfully prior to the upgrade, see Checkpoint 4 item 2, page 128.
- <SCS_ROOT> where the current SCS 4.1.2 or SCS 5.0.2 server is installed - <LDAP_ROOT> where LDAP 4.16 for SCS 4.1.2 is installed - <IPLANET_ROOT> where iPlanet 5.1 for SCS 5.0.2 is installed.
Prechecks prior to starting SCS upgrade

The SCS and LDAP/ iPlanet installation paths are required while executing the SCS upgrade procedure.
1. Determine <SCS_ROOT> where current SCS 4.1.2 or 5.0.2 are installed and running.
# cd /etc/shasta # cat scs.config | grep SCSHead
If you are currently running SCS 4.1.2:

Example: # cat scs.config | grep SCSHead SCSHead=/opt/shasta/scs
Make a note of the current SCS 4.1.2 root directory:

<SCS_ROOT>
If you are currently running SCS 5.0.2:

Example: # cat scs.config | grep SCSHead SCSHead=/opt/shasta/scs502
Make a note of the SCS 5.0.2 root directory:

<SCS_ROOT>
411-5221-309
Standard
06.30 March 10, 2010
147
2. Verify the status of the SCS processes. All SCS server processes must be running prior to starting the upgrade. Execute the following from the SCS server bin directory under <SCS_ROOT>.
# cd <SCS_ROOT>/bin
Here is an example where the server is running SCS 5.0.2:

# cd /opt/shasta/scs502/bin # ./SCSAdmin status Running Solid Database Server since Aug_14 (pid=3644) Running SCS Daemon since Aug_14 (pid=3739) Running SCS Domain Server since Aug_14 (pid=3761) Running SNMP Proxy since Aug_14 (pid=3885) Running SCS Region Server since Aug_14 (pid=3915) Running SCS Monitor Server since Aug_14 (pid=3974) Running SCS Trap Daemon since Aug_14 (pid=3999) Running SCS Pull Server since Aug_14 (pid=4034) Running SCS Log Server since Aug_14 (pid=4054) Running SCS CORBA Server since Aug_14 (pid=3891) SCS Provisioning is enabled SSL is not enabled on present servers All SCS server processes are running. Version SCS GGSNS5.0.2_SCS5.0(14)
Note: If the server is not installed with SCS Corba Server, the Corba Server process will not be displayed in SCSAdmin status If any of the SCS server processes are not running, restart the SCS server processes:
# cd <SCS_ROOT>/bin #./SCSAdmin restart #./SCSAdmin status
Execute SCSAdmin status mentioned above to verify all the processes are running. If any of the processes does not start, contact your next level of support before proceeding.
GPRS/UMTS
148
3. Confirm SCS processes are running from the <SCS_ROOT>. Steps to determine if SCS processes are running from installation directory of SCS are given below for both SCS 4.1.2 and SCS 5.0.2. Below example show a capture from a SCS 4.1.2 installation. Here the root directory is /opt/shasta/scs (ignore /bin directory from ps aef command output.).
# ps -aef | grep SCS root 23673 1 0 21:51:19 pts/1 0:00 /bin/sh -f shasta/scs/bin/SCSRegionServer root 23646 1 0 21:51:10 pts/1 0:00 /bin/sh shasta/scs/bin/SCSCorbaServer root 23574 1 0 21:50:45 pts/1 0:00 /bin/sh shasta/scs/bin/SCSDaemon root 23774 1 0 21:51:59 pts/1 0:00 /bin/sh shasta/scs/bin/SCSLogServer root 23701 1 0 21:51:30 pts/1 0:00 /bin/sh shasta/scs/bin/SCSMonitorServer root 23755 1 0 21:51:51 pts/1 0:00 /bin/sh shasta/scs/bin/SCSPullServer root 23729 1 0 21:51:41 pts/1 0:00 /bin/sh shasta/scs/bin/SCSTrapDaemon root 23589 1 0 21:50:52 pts/1 0:00 /bin/sh shasta/scs/bin/SCSDomainServer
/opt/ -f /opt/ -f /opt/ -f /opt/ -f /opt/ -f /opt/ -f /opt/ -f /opt/
Here is an example from a SCS 5.0.2 installation. Here the root directory is /opt/shasta/scs502.
# ps -aef | grep SCS root 3761 1 0 Aug 14 ? shasta/scs502/bin/SCSDomainServer root 3999 1 0 Aug 14 ? shasta/scs502/bin/SCSTrapDaemon root 3739 1 0 Aug 14 ? shasta/scs502/bin/SCSDaemon root 3974 1 0 Aug 14 ? shasta/scs502/bin/SCSMonitorServer root 3891 1 0 Aug 14 ? shasta/scs502/bin/SCSCorbaServer root 3915 1 0 Aug 14 ? shasta/scs502/bin/SCSRegionServer root 4054 1 0 Aug 14 ? shasta/scs502/bin/SCSLogServer root 4034 1 0 Aug 14 ? shasta/scs502/bin/SCSPullServer 0:00 /bin/sh -f /opt/ 0:00 /bin/sh -f /opt/ 0:00 /bin/sh -f /opt/ 0:00 /bin/sh -f /opt/ 0:00 /bin/sh -f /opt/ 0:00 /bin/sh -f /opt/ 0:00 /bin/sh -f /opt/ 0:00 /bin/sh -f /opt/
4. Determine LDAP or iPlanet installation directory: If upgrading from SCS 4.1.2, determine the LDAP 4.16 installation directory <LDAP_ROOT>. If upgrading from SCS 5.0.2, determine the iPlanet installation directory <IPLANET_ROOT>.
411-5221-309
Standard
06.30 March 10, 2010
149
a.For SCS 4.1.2-> 6.0 upgrade: Change directory to SCS root directory/bin directory and determine the value set for parameter LDAPPath
# cd <SCS_ROOT>/bin # cat .scs.config | grep LDAPPath Example: # cd /opt/shasta/scs/bin # cat .scs.config | grep LDAPPath LDAPPath=/opt/shasta/ldap
From the above example: <LDAP_ROOT> = LDAPPath = /opt/shasta/ldap For SCS 4.1.2-> 6.0 upgrade, record the LDAP root directory: <LDAP_ROOT> or b.For SCS 5.0.2-> 6.0 upgrade: Determine iPlanet installation directory <IPLANET_ROOT>
# cd <SCS_ROOT>/bin # cat .scs.config | grep LDAPPath Example: # cd /opt/shasta/scs5.0/bin # cat .scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet
From the above example: <IPLANET_ROOT> = LDAPPath = /opt/shasta/iplanet For SCS 5.0.2-> 6.0 upgrade, record the iPlanet root directory: <IPLANET_ROOT> 5. Determine LDAP_SERVER_PORT: Change directory to SCS root directory/bin directory and determine the value set for parameter LDAPServerPort. For SCS 4.1.2-> 6.0:
# cd <SCS_ROOT>/bin # cat .scs.config | grep LDAPServerPort GPRS/UMTS Upgrade Manual GGSN6.0
150
Example: # cd /opt/shasta/scs/bin # cat .scs.config | grep LDAPServerPort LDAPServerPort=389
From the example:

LDAP_SERVER_PORT = 389
Make a note of LDAP_SERVER_PORT as the next step involves verification of SCS and LDAP server process status. For SCS 4.1.2-> 6.0: <LDAP_SERVER_PORT> For SCS 5.0.2-> 6.0:
# cd <SCS_ROOT>/bin # cat .scs.config | grep LDAPServerPort Example: # cd /opt/shasta/scs502/bin # cat .scs.config | grep LDAPServerPort LDAPServerPort=390 From the example: LDAP_SERVER_PORT = 390
Make a note of LDAP_SERVER_PORT as the next step involves verification of SCS and LDAP server process status. For SCS 5.0.2-> 6.0: <LDAP_SERVER_PORT>
6. Determine LDAP (or iPlanet) LDAPPassword:

# cd /etc/shasta # cat scs.config | grep LDAPPassword Example: # cd /etc/shasta # cat scs.config | grep LDAPPassword LDAPPassword=admin
411-5221-309
Standard
06.30 March 10, 2010
151
Make a note of LDAP_PASSWORD: <LDAP_PASSWORD>
7. In the SCS system files - <SCS_ROOT>/bin/.scs.config and /etc/shasta/scs.config, determine there are no duplicate entries for the LDAPPath and LDAPServerName. Here is an example where there are duplicate entries:
# cat /etc/shasta/scs.config | grep SCSHead # cd <path returned by above cat command>/bin
Search for LDAPServerName duplicate entry in <SCS_ROOT>/bin/ .scs.config:

# cat .scs.config | grep LDAPServerName LDAPServerName=slapd-urc2y1th1 LDAPServerName=slapd-urc2y1th1
Search for LDAPPath duplicate entry in <SCS_ROOT>/bin/.scs.config:

# cd /etc/shasta
Search for LDAPServerName duplicate entry in /etc/shasta/scs.config:

# cat scs.config | grep LDAPServerName LDAPServerName=slapd-urc2y1th1 LDAPServerName=slapd-urc2y1th1
Search for LDAPPath duplicate entry in /etc/shasta/scs.config:

# cat scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet LDAPPath=/opt/shasta/iplanet
If there are any duplicate entries for LDAPPath or LDAPServerName in either: <SCS_ROOT>/bin/.scs.config or /etc/shasta/scs.config
GPRS/UMTS
152
use vi editor and delete the line with the duplicate entry. There must be only 1 line for LDAPServerName and LDAPPath. Here is an example after the duplicate entries have been deleted.
# cd <SCS_ROOT>/bin # cat .scs.config | grep LDAPServerName LDAPServerName=slapd-urc2y1th1 # cat .scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet
# cd /etc/shasta/ # cat scs.config | grep LDAPServerName LDAPServerName=slapd-urc2y1th1 # cat scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet
8. Make sure setup.sh, rollingSCS.sh files and install directory does not exist in the current SCS server installation directory. Please refer Determine <SCS_ROOT> where current SCS 4.1.2 or 5.0.2 are installed and running. on page 146 to identify the current SCS installation directory. Determine the current SCS installation directory.
Change directory to the current SCS installation directory

# cd <path returned by above cat command>
Verify if files setup.sh, rollingSCS.sh and directory install exists or not. If the file and directory exists, then remove them. Here is an example capture:
Example:
Here is a scenario where setup.sh file and install directory exists:

# ls setup.sh setup.sh # ls rollingSCS.sh rollingSCS.sh
411-5221-309
Standard
06.30 March 10, 2010
153
# ls install bin etc tmp
export
lib
log
mibs
opt
proc
Remove files setup.sh, rollingSCS.sh and directory install
# rm setup.sh # rm rollingSCS.sh # rm -rf install
Note: Deleting a directory on Solaris require -rf option in rm command.
9. From the SCS Server, input the following command to verify the LDAP/ iPlanet directory server instance and admin servers processes are running. If the process is not running, try restarting the processes. a. Check LDAP server process is running.
# ps -aef | grep -v grep | grep slapd Example: # ps -aef | grep -v grep | grep slapd nobody 990 1 0 Aug 11 ? 0:31 ./nsslapd -f /opt/shasta/ldap/slapd-zrc2s186/config/slapd.conf -i /opt/shasta/
If the above ps -aef command does not return a result, start the LDAP/ iPlanet directory server processes: Determine the LDAP/ iPlanet installation directory:
# cat /etc/shasta/scs.config | grep LDAPPath # cd <Path returned by LDAPPath> # cat /etc/shasta/scs.config | grep LDAPServerName # cd <Path returned by LDAPServerName> # ./start-slapd
b. Next step is to verify the LDAP/ iPlanet server socket is open in LISTEN state.
GPRS/UMTS
154
# cat /etc/shasta/scs.config | grep LDAPServerPort # netstat -na | grep <port returned for LDAPServerPort> Example: # netstat -na | grep 389 | grep LISTEN *.389 *.* 0 LISTEN 0 0 24576
c. Check LDAP/ iPlanet admin process is running

# ps -aef| grep -v grep | grep admin
Example for LDAP: # ps -aef | grep -v grep | grep admin root 528 1 0 Aug 11 ? d /opt/shasta/ldap/admin-serv/config Example for iPlanet: # ps -aef | grep -v grep | grep admin root 3628 3200 0 Aug 14 ? opt/shasta/iplanet/admin-serv/config root 3185 1 0 Aug 14 ? opt/shasta/iplanet/admin-serv/config root 3200 3185 0 Aug 14 ? opt/shasta/iplanet/admin-serv/config 0:07 ns-httpd -d / 0:00 ./uxwdog -d / 0:01 ns-httpd -d / 0:00 ./ns-admin -
If the above ps -aef command does not return a result, start the LDAP/ iPlanet admin server processes using:
# cat /etc/shasta/scs.config | grep LDAPPath # pwd <Path returned by LDAPPath> #./start-admin
Verify if the admin server process started, otherwise contact Nortel support.
# ps -aef | grep -v grep | grep admin
10. Verify if SSL is enabled on the SCS server.

# cat /etc/shasta/scs.config | grep SCSHead # cd <Path to SCSHead>
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential # cd bin
155
Run SCSAdmin status and verify is SSL enabled.

# ./SCSAdmin status <- Verify if SSL is enabled. Look for: SSL is <not> enabled on present servers
If SSL is not enabled, please skip this step and proceed to the next step to Step 11 on page 156. If SSL is enabled on the SCS server, then make a backup copy of the SSL certificates files:
trusted.txt sslrsa.crt
Here is an example:
# cd <SCS_ROOT>/etc # cp trusted.txt trusted.txt.BACKUP # cp sslrsa.crt sslrsa.crt.BACKUP
The backup copies of the SSL certificates can be restored after SCS upgrade. To copy the backup files to a /etc/shasta directory:
# cp *.BACKUP /etc/shasta
Make a backup copy of the SSL certificates on the SCS client. SCS client for Windows and Solaris are outlined below. SCS client for Windows: Login to the SCS client host, then change directory to the SCS client location. If you have a Desktop icon on the PC, then Right mouse click on the SCS client icon-> Properties--> Look for the path listed in Start In. Ignore the bin directory. Change directory to the path listed in the above statement and then change directory to etc directory. Copy files:
trusted.txt to trusted.txt.BACKUP sslrsa.crt to sslrsa.crt.BACKUP
GPRS/UMTS
156
Copy trusted.txt.BACKUP and sslrsa.crt.BACKUP to another location, example: C:\mysslcertificates\ SCS client for Solaris:
Log in to the SCS client on the Solaris server, then change directory to the location where SCS client is installed. If you do not know the SCS client installation location, use the following Unix find command to find the location:
# find / -name SCSClient
Here is an example:
# find / -name SCSClient /opt/scs-client/bin/SCSClient
Note: If the SCS client installation directory is named SCSClient, then you will see two entries from the find command, one for the directory and one for file SCSClient in the bin directory. Change directory to the SCS client installation directory (ignore the bin directory). Change directory to etc directory. Make a backup copy of files:
# cp trusted.txt trusted.txt.BACKUP # cp sslrsa.crt sslrsa.crt.BACKUP
Create a SSL backup directory and copy the backup files to this directory. You can also FTP these files to a different server and FTP the files back after SCS server/ client upgrade. To copy the backup files to a new directory. Note: If the SCS server and client are on the same server, then you can skip this step, otherwise copy the backup files to /etc/shasta
# cp *.BACKUP /etc/shasta The backup files can be moved back after the SCS client upgrade.
11. Run System diagnosis tools: System diagnostic tools provide an overall view of the health of the SCSs platform. This information should be captured in a file so that it can be compared to results after an upgrade to ensure there are no significant differences.
411-5221-309
Standard
06.30 March 10, 2010
157
d. System Command prstat

<Syntax>: prstat -c -a <interval> <counter> Where: -c - Print new reports below previous reports instead of overprinting them. -a - Report information about processes and users. In this mode prstat displays separate reports about processes and users at the same time. <interval> - This will re-display the details every <interval> seconds. <counter> - Number of times the details will be displayed
The prstat command displays Process ID, user name, size, state and time taken by this process. The prstat command also displays the percentage of the CPU time used and the process name. State in the display shown below, can be cpu1 or cpu2 or sleep, Idle etc. The example shown below, will display the CPU usage details for the top 15 processes and users, every 10 seconds, and the command prompt will come back after displaying the details 5 times.
Example:
# prstat -c -a 10 5
PID USERNAME SIZE RSS 12596 root 191M 13313 root 1552K 12352 root 324M 536 root 3608K 12622 root 185M 12491 root 127M 12421 root 326M 12456 root 197M 12262 root 63M 378 root 1664K in.comsat/1 178 root 2008K 12390 root 188M 17394 root 336K 691 root 1240K SolarisNativeTo/1 160 daemon 2544K NPROC USERNAME SIZE 58 root 1803M 1 nobody 23M 1 daemon 2544K STATE PRI NICE 39M sleep 0 1192K cpu2 58 43M sleep 0 2896K sleep 58 29M sleep 0 36M sleep 0 46M sleep 50 48M sleep 30 24M sleep 0 856K sleep 58 1264K 38M 232K 856K sleep sleep sleep sleep 50 18 42 1 50 TIME CPU PROCESS/NLWP 0 0:00.00 0.1% java/23 0 0:00.00 0.1% prstat/1 0 0:00.00 0.1% java/53 0 0:00.00 0.0% nscd/11 0 0:00.00 0.0% java/19 0 0:00.00 0.0% java/25 0 0:00.00 0.0% java/59 0 0:00.00 0.0% java/59 0 0:00.00 0.0% java/29 0 0:00.16 0.0% 0 0 0 0 0:08.05 0:00.00 0:00.00 0:00.00 0.0% cron/1 0.0% java/23 0.0% sh/1 0.0%
1760K sleep RSS MEMORY 452M 23% 6712K 0.3% 1760K 0.1%
0 0:00.00 0.0% statd/3 TIME CPU 0:10.44 0.3% 0:00.00 0.0% 0:00.00 0.0%
Total: 60 processes, 508 lwps, load averages: 0.17, 0.58, 0.89
GPRS/UMTS
158
Note: The SCS processes PIDs can be seen when the SCSAdmin status command is executed from <SCS_ROOT>/bin. Please verify, if any of the SCS processes are taking very high CPU times. If more details are required for any process shown in the display, use the following command.
# ps -ef | grep <PID> where <PID> is the process ID to search.
The command can be re-executed if need be. If one or more processes are continually consuming all the CPU, the system may have a problem. See the document Nortel Networks Shasta 5000 Broadband Service Node Troubleshooting Guide, for further instructions.
e.
System Command df -k Ensure there is enough free space on the current SCS server host machine to install the new SCS software. Please refer to Step 0 item 6 on page 52 for details on disk space availability.
f. System Command swap Please refer to Step 0 item 6 on page 52 for details on swap space availability.
12. Verify the SCS Client is functional prior to upgrading: Log in on the SCS server as device_owner Open the menu item Help, Help and ensure the help files are installed. View devices in the region Check all active devices in each region are in sync. This is shown with a green icon followed by the GGSNs node name followed by (In Sync) as in the following illustration
Note which devices are not in sync (e.g., disconnected, or administratively down)
411-5221-309
Standard
06.30 March 10, 2010
159
To verify basic ability to make configuration changes in the SCS databases, open the Users manager, and create/delete a dummy user on ISP device_owner. Creating a user does not send information to the GGSN. Verify that the user created, modified, and deleted. Here are the steps to add a dummy user from the SCS client. Login to the SCS client as device_owner user. Click Users icon in the left pane to access User Manager. Click Add, this will bring up User Configuration window. Enter a username dummy and set the password. Click User View Profile, select device_owner. From the All ISPs list, click device_owner and click the button displaying the right arrow. This will add device_owner to the Selected ISPs list. Click device_owner from the Selected ISPs list, then click Default ISP. Click OK to save the configuration. Lauch another SCS client session and login as the user created in the above steps. Verify the login is successful. From the device_owner SCS client session, click User icon in the left pane. From User Manager, select the dummy user. Click Delete.
The customer may wish to determine another configuration parameter to change on the device and view changes on the GGSN using its CLI (e.g. increasing a particular timeout value by a second). However the particular parameter must be considered carefully to avoid impacting network operation. Note: Refer to GGSN Provisioning Procedures (NTP 411-5221-927) for more details on GGSN provisioning. 13. If a GGSN is In Sync for 7 days (no re-syncs or micro syncs) and no configuration changes are made for 7 days, a time threshold is reached. When the SCS Region server session is re-established to that GGSN, a session error is raised and the GGSN is marked Out of Sync. Hence, before the upgrade follow this procedure to avoid this. Log into the SCS Client GUI On the Device Manager panel, right click on the device and select Configure and then Device
160
On the Device tab, if the Up Since time is greater than 7 days, then perform some minor configuration change. For instance add a security service policy with the default rule set and then delete it. For details on adding a security policy, please refer to - Verify the GGSN Configuration on page 316. Note: The Up Since time indicates the time when the GGSN was last rebooted. This is not an indication of the last configuration change made to the GGSN. Performing this manual configuration step above guarantees the configuration time stamp is not past the threshold (7 days) by resetting it. If the Up Since time is less than 7 days, a configuration change is not required. The configuration can still be added as a precheck. From GGSN 5.0.2 and above, the GGSN command show log event will display SCS provisioning. Users can run the command to check for provisioning changes. From the output, search for the string Config Change. Here is an example:
Fri 02-Nov-2007 13:10:29 13/1/1:DBG Manager 0 1 1 INFO DBGMSG_I: spm_process_work_request: Config Change. Calling [modify_device]. seq=[1536] object_type=[0] operation=[1]
The GGSN Session Log can also be used to verify for any configuration changes. To access the GGSN Session Log, from the SCS client-> Device Manager, right click on the GGSN and select Diagnostics & Maintenance. The SCS Server upgrade can now be performed without effecting the GGSN state. Return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
411-5221-309
Standard
06.30 March 10, 2010
SCS Upgrade on the Same Physical Server 161

This section provides an overview of the SCS upgrade procedure on the same server for: and For SCS 5.0.2 - refer to section Upgrade SCS from 5.0.2 to 6.0 on page 166 For SCS 4.1.2 - refer to section U pgrade SCS from 4.1.2 to SCS 6.0 on page 161
Upgrade SCS from 4.1.2 to SCS 6.0

This section provides an overview of the SCS upgrade procedure from SCS 4.1.2 to SCS 6.0 on the same server. If you are upgrading from GGSN SCS 5.0.2 to 6.0, please go to the next section Upgrade SCS from 5.0.2 to 6.0 on page 166
Overview SCS 4.1.2 to SCS 6.0 upgrade involves Solaris OS upgrade from Solaris 8 to Solaris 9 and LDAP server upgrade from 4.16 to iPlanet 5.1. Solaris will be upgraded using the Solaris live upgrade feature. iPlanet upgrade will be done as part of the SCS upgrade. All the other third party software upgrade is transparent to the user. The required steps are documented in the table Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162 below. From GGSNS 5.0, SCS introduced a new upgrade strategy called Rolling Upgrade to reduce the loss of service time for the SCS servers. Rolling upgrade creates a duplicate directory of the existing SCS 4.1.2 server and a duplicate LDAP 4.16 server instance. Then SCS 6.0 software upgrade is performed on the duplicate SCS server directory/LDAP instance, while the original SCS/LDAP servers are still in service. Pre-requisite: Upgrade readiness checkpoint #0 to checkpoint #4 must be completed before starting the SCS upgrade procedures. Please refer to GGSN/SCS pre upgrade checklists on page 31. Note: It is recommended that the new features should not be configured via SCS GUI prior to at least one GGSN using those features is upgraded.
GPRS/UMTS
162
Pre-conditions
Obtain the following software and patches required for the SCS upgrade Obtain SCS 6.0 CD or from Electronic Software Delivery. Solaris 8 Disk 1 and Disk 2 Solaris 9 Disk 1 and Disk 2 Make sure that the SCS Server is running Solaris 8 and latest Solaris 8 recommended patches are installed. The latest patch cluster can be obtained from Sun website at http://sunsolve.sun.com. See Install Recommended Patches for Solaris 9 and Solaris 10 on page 452. This example gives details on the procedure to update Solaris 9 patch cluster. Users can follow the same procedure for Solaris 8 patch application also. Backup Media: DDS-4 Tapes for Full system backup and restore. You may require multiple tapes depending on the size of the server partitions and disk space used Log onto the SCS Client as device owner, and click on Devices and then region to make sure all the GGSNs are in sync. Make sure all the GGSNs are Insync before starting the upgrade procedure.
Table 14 Upgrade SCS 4.1.2 to SCS 6.0 on same server Step Duration Tot 1 2 0:15 0:05 SL 0:35 DT SCS Upgrade Prechecks on page 146 During the SCS 6.0 software upgrade: 1. Do not make any configuration change to avoid config mismatch between pre-upgrade and post-upgrade. Disable SCS provisioning. See Disable SCS provisioning on page 205. 2. Do not do the Sync States and Query States operation in Patch Manager dialog to avoid Sequence Number mismatch between SCS and GGSN after upgrade is done. 3 0:10 0:10 Perform a tar backup of LDAP and SCS Directories and config files before executing the upgrade. See Option 1: SCS backup/ restore using tar on page 233
sheet 1 of 3
Procedure
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Table 14 Upgrade SCS 4.1.2 to SCS 6.0 on same server Step Duration Tot 4 0:12 SL DT SCS 6.0 Software upgrade. Procedure
See Upgrade SCS 4.1.2 to SCS 6.0 on page 246. 5 0:05 Copy the upgraded SCS 6.0 from Solaris 8 BE to Solaris 9 BE. See Copy the upgraded SCS 6.0 from Solaris 8 to Solaris 9 on page 447. 6 0:02 0:02 Stop the original SCS Server, LDAP directory server and LDAP admin server processes. See Verify and Stopping SCS server and LDAP server processes on page 208. Activate the new Solaris 9 boot environment. Refer to Important Step to determine server boot path for Solaris 8 and Solaris 9: on page 432 Enable LDAPWatch. See LDAPWatch-enable command in section Enable LDAPWatch on page 204 See SCS Client upgrade procedures on page 355 Note: If SCS Server is SSL enabled, the SCS Client machine should also be SSL enabled for the client to function normally. If you have enabled SSL on the SCS Server in the previous step, refer to Enabling SSL on the SCS Client on page 358 for more details on how to enable SSL on client machine. SSL enabling will be done after the SCS Client installation. 10 0:01 Post upgrade critical check: verify that all the GGSNs are in sync and there are no sequence number mismatch session errors. Log on SCS Client with the user device_owner, go to Device Manager and verify that all the GGSNs are in sync. Open Diagnostics & Maintenance Dialog, then select Session Errors tab and verify that there are no sequence number mismatch session errors. 11 0:20 See SCS Post-upgrade / Rollback checklists on page 304 The post upgrade checks have to be executed every day for 7 days after the upgrade, to make sure the SCS server is functioning properly after the upgrade. 12 0:10 0:10 Take a tar backup of the Databases as soon as the upgrade to GGSN 6.0 is completed. See Option 1: SCS backup/ restore using tar on page 233.
sheet 2 of 3
7 8 9
0:01 0:02 0:06
0:01 -
GPRS/UMTS
164
Table 14 Upgrade SCS 4.1.2 to SCS 6.0 on same server Step Duration Tot 13 0:03 SL 0:03 DT Stop SCS server and LDAP server to prepare installing recommended patches for Solaris 9. See Verify and Stopping SCS server and LDAP server processes on page 208. 14 0:10 0:10 Optional: Apply OS hardening for Solaris 9, please see OS Hardening of GGSN SCS Server on page 348 The OS hardening makes the system secure from unauthorized access and modification. 15 16 0:10 0:30 0:10 Verify partition level file permissions following Modify partition level file permissions on page 300 Delete the Solaris 8 BE and mount the Solaris 8 partitions to Solaris 9 for reuse. This is an optional operation. Perform this step unless there isnt enough disk space on Solaris 9. Warning: If the Solaris 8 boot environment is deleted, we cannot rollback to Solaris 8 any more. This step must be performed after at least 24 hours from the moment that upgrade is completed. Nortel strongly recommends to perform this step after one week, but within 30 days. For mirrored servers, you can delete the Solaris 8 BE and reuse it for Solaris 9 disk mirroring. See Delete Solaris 8 Boot Environment and Reuse Solaris 8 partitions on Solaris 9 on page 445.
sheet 3 of 3
Procedure
Times indicated in the table are estimates only. After the SCS Server and Client have upgraded, proceed to the pre checks for GGSN upgrade, GGSN Software Upgrade on page 493
411-5221-309
Standard
06.30 March 10, 2010
Table of roll-back procedures from GGSN SCS 6.0 to SCS 4.1.2 The rollback procedure explains the steps to rollback SCS 6.0 to SCS 4.1.2 after the server has been rebooted with Solaris 9 boot environment. The explanation also includes procedure to rollback from Solaris 9 to Solaris 8. Note: The rollback procedure assumes that the Solaris 8 boot environment has not been deleted after activating to Solaris 9 boot environment. Note: If the GGSN software was upgraded to GGSN 6.0, it must be rolled back first before rolling back the SCS. See the GGSN roll back procedures in GGSN Rollback procedure on page 547. This must be performed prior to the SCS roll back.
Table 15 Rollback SCS 6.0 to SCS 4.1.2 on same server Step Duration Tot 1 2 3 0:10 0:25 0:15
per GGSN
Description DT 0:10 0:25 0:15

per GGSN
SL 0:10 -
Rollback GGSN to 4.1.1 software load. Please refer toGGSN Rollback procedure on page 547. Follow procedure Rollback SCS 6.0 to SCS 4.1.2 after Solaris 9 Upgrade on page 363. Using SCS 4.1.2 client software, (if the client is not available), please install the client using SCS Client upgrade procedures on page 355 For each GGSN, before resynching the GGSN, stop the traffic on the GGSN to be resynched. See Reject GGSN incoming traffic on page 522 For each GGSN, See Resync with iSOS Ver. on page 572 for rebooting the GGSN to 4.1.1 software load. After the resync, allow the traffic to start again. See Step 23 inUpgrade to GGSN 6.0 software on page 533.
0:30
See SCS Post-upgrade / Rollback checklists on page 304 The post upgrade / rollback checks have to be executed every day for 7 days after the rollback, to make sure the SCS server is functioning properly after the rollback.
GPRS/UMTS
166
Upgrade SCS from 5.0.2 to 6.0

Table 16 Upgrade SCS 5.0.2 to SCS 6.0 on same server Step Duration Tot 1 2 0:15 0:05 SL DT SCS Upgrade Prechecks on page 146 During the SCS 6.0 software upgrade: 1. Do not make any configuration change to avoid config mismatch between pre-upgrade and post-upgrade. Disable SCS provisioning. See Disable SCS provisioning on page 205. 2. Do not do the Sync States and Query States operation in Patch Manager dialog to avoid Sequence Number mismatch between SCS and GGSN after upgrade is done. 3 0:10 Perform a tar backup of LDAP and SCS Directories and config files before executing the upgrade. See Option 1: SCS backup/ restore using tar on page 233. 4 0:12 Perform SCS 6.0 Software upgrade. See Upgrade GGSN SCS from 5.0.2 to 6.0 on page 274. 5 0:06 See SCS Client upgrade procedures on page 355 Note: If SCS Server is SSL enabled, the SCS Client machine should also be SSL enabled for the client to function normally. If you have enabled SSL on the SCS Server in the previous step, refer to Enabling SSL on the SCS Client on page 358 for more details on how to enable SSL on client machine. SSL enabling will be done after the SCS Client installation. 6 0:01 Post upgrade critical check: verify that all the GGSNs are in sync and there are no sequence number mismatch session errors. Log on SCS Client with the user device_owner, go to Device Manager and verify that all the GGSNs are in sync. Open Diagnostics & Maintenance Dialog, then select Session Errors tab and verify that there are no sequence number mismatch session errors. 7 0:20 See SCS Post-upgrade / Rollback checklists on page 304 The post upgrade checks have to be executed every day for 7 days after the upgrade, to make sure the SCS server is functioning properly after the upgrade. Procedure
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Table 16 Upgrade SCS 5.0.2 to SCS 6.0 on same server (continued) Step Duration Tot 8 9 0:10 0:03 SL 0:10 0:03 DT Procedure
Take a tar backup of the databases as soon as the upgrade to SCS 6.0 is completed. See Option 1: SCS backup/ restore using tar on page 233. Optional: Stop SCS server and LDAP server to prepare installing recommended patches for Solaris 9. See Stop SCS server. Disable LDAPWatch on page 203 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206 To apply Solaris 9 recommended patches, refer to Install Recommended Patches for Solaris 9 and Solaris 10 on page 452
10
0:10
0:10
Optional: Apply OS hardening for Solaris 9, if not install before, otherwise ignore this step. Please see OS Hardening of GGSN SCS Server on page 348 The OS hardening makes the system secure from unauthorized access and modification.
GPRS/UMTS
168
Table of roll-back procedures for GGSN SCS 6.0 to SCS 5.0.2 The following section explains how to rollback the SCS 6.0 to SCS 5.0.2. GGSN will be rolled back to 5.0.1 prior to rolling back SCS.
Table 17 GGSNS6.0 to GGSNS5.0.1 on Same Server Roll-back Step Duration Tot SL 0:10 DT 0:10 0:25 Rollback GGSN to 5.0.1 software load. Please refer toGGSN Rollback procedure on page 547. See SCS 6.0 to SCS 5.0.2 Rollback procedure on page 373 See SCS Post-upgrade / Rollback checklists on page 304 The post upgrade / rollback checks have to be executed every day for 7 days after the rollback, to make sure the SCS server is functioning properly after the rollback. Description
1. 0:10 2. 0:25 3. 0:30
411-5221-309
Standard
06.30 March 10, 2010
Migrating SCS to a new physical server with Same or Different IP address
169
Migrating SCS to a new physical server with Same or Different IP address 8

This section can be followed in case of SCS server migration from a old Sun hardware to a new Sun hardware. During a SCS server upgrade, an option to upgrade the Sun hardware platform is also available. To upgrade to GGSNS6.0 and migrate of a new hardware platform with the same or different IP address as the current SCS server, the customer must decide on the SCS server software load to upgrade to. This will determine the Solaris operating system to be installed on the new server platform. Customers who are moving to a new SCS hardware begin by installing Sun Solaris 9 or Solaris 10 on their new hardware. SCS 6.0 requires Solaris 9 OS and SCS 6.0.1 requires Solaris 10 OS. Sun Netra T5220 is supported only on Solaris 10 operating system. In case the customer is migrating to Sun Netra T5220, SCS 6.0.1 is the supported SCS version. Here are the possibilities. Upgrading from SCS 4.1.2 or SCS 5.0.2 and migrating to new Sun hardware platform. Migrating SCS 6.0 to new Sun hardware running on Solaris 9 Migrating SCS 6.0 to new Sun hardware running on Solaris 10. This requires a SCS 6.0.1 installation on the new server and a database restore. Here is an overview of the steps to upgrade and migrate the SCS server to a new hardware platform. On the new server: A reinstallation of the Solaris 9 or Solaris 10 operating system may be required to meet the recommended system configuration. For details, please refer to SCS server preparation: Migration of the current SCS to new hardware or New Install of SCS on new hardware on page 142 On the new server: Depending on the selected operating system, Solaris 9 or Solaris 10 recommended patches must be applied on the new server.
GPRS/UMTS
170
Upgrade from SCS 4.1.2 or SCS 5.0.2 to SCS 6.0 on Solaris 9 is supported. Direct upgrade from SCS 4.1.2 or SCS 5.0.2 to SCS 6.0.1 on Solaris 10 is not supported. On the current server, SCS 4.1.2 or SCS 5.0.2 must first be upgraded to SCS 6.0. In case Solaris 10 supported is required, then SCS 6.0 must be migrated to SCS 6.0.1 on the new hardware platform. On the old server: A SCS solid and ldap/ iplanet database backup is performed. On the new server: Depending on the choice of SCS software to be upgraded, SCS 6.0 or SCS 6.0.1 is installed on the new server. On the new server: The Solid and iPlanet database from the old server is restored on the new SCS server. If the new server IP address if different: If there are customer specific features that are activated with SOC, the existing SOC keys have to be reapplied from Nortel. GGSNs are then migrated to the new SCS server. Important Note: It is recommended that the new features should not be configured via SCS GUI prior to at least one GGSN using those features is upgraded.
Pre-conditions
GGSNS6.0 (SCS 6.0) or GGSNS6.0 (SCS 6.0.1) SCS Software CD Optional - GGSNS6.0 (for SCS 6.0 or 6.0.1) SCS CORBA Server Application CD Optional - GGSNS6.0 (for SCS 6.0 or 6.0.1) SCS SSL Software CD Backup Media (Tapes for backup) Note: Sun Netra T5220 is not shipped with a tape drive. A full server tape backup is not supported on the T5220.
Make sure all the GGSNs are in Sync before the Upgrade or Migration. Log onto the SCS Client as device owner, and click on Devices and then region to make sure all the GGSNs are in sync.
Important Note for SCS migration to Sun T5220 platform: Table 18 Migrating SCS server to new server, same IP address upgrade procedures (includes T5220 migration) on page 172 details the migration procedure for both SCS 4.1.2 to SCS 6.0 or SCS 6.0.1 as well as SCS 6.0 to SCS 6.0.1.
411-5221-309
Standard
06.30 March 10, 2010
171
To upgrade from SCS 5.0.2 to 6.0.1 on the new T5220 platform, table 16 Upgrade SCS from 5.0.2 to 6.0 on page 166 should be executed first to upgrade SCS 5.0.2 to 6.0 on the old server. Then the SCS 6.0 can be upgraded to SCS 6.0.1 on the new server steps of table 18 Migrating SCS server to new server, same IP address upgrade procedures (includes T5220 migration) on page 172.
GPRS/UMTS
172
Table 18 Migrating SCS server to new server, same IP address upgrade procedures (includes T5220 migration) Step Duration Tot 1 SL DT For SCS 4.1.2 upgrade and migration only. Skip this step if current release is already SCS 6.0. Backup the whole SCS, LDAP Directories and Configuration files before the Upgrade. This step is needed if the upgrade fails and need to Rollback. See SCS backup/ restore options on page 233 2 For SCS 4.1.2 upgrade and migration only. Skip this step if current release is already SCS 6.0. See SCS Software Upgrade on page 246 3 0:10 This step is applicable to SCS 4.1.2 upgrade and migration. This step is applicable to SCS 6.0 migration. On the Old Server, take a backup of Solid and LDAP (or iPlanet) databases: If upgrading from SCS 4.1.2, the current SCS 4.1.2 server processes must be stopped, SCS 6.0 processes must be started. See Database backup and restore procedures for migrating to a new physical server on page 182 If upgrading from SCS 4.1.2 - After the backup is complete, SCS 6.0 processes must be stopped, SCS 4.1.2 server processes must be started. This backup is needed to be restored on the new SCS Server. Transfer these backup files, to another intermediate server using ftp, till the new server is ready. Description
sheet 1 of 8 4 Applicable to both SCS 4.1.2 and SCS 6.0 migration: Perform data collection from the current server. The parameters collected in this step will be used during the new installation of SCS on the new server. Please refer to SCS data collection during SCS server migration on page 231
411-5221-309
Standard
06.30 March 10, 2010
173
Table 18 Migrating SCS server to new server, same IP address upgrade procedures (continued)(includes T5220 Step Duration Tot 5 SL DT Applicable to both SCS 4.1.2 and SCS 6.0 migration: Check the /opt/patches and /tftpboot/patches directories on the old server, and if there are any GGSN patches present in these directories, transfer those files to an intermediate server (using ftp, and binary transfer), and verify the files have identical permission. 6 Applicable to both SCS 4.1.2 and SCS 6.0 migration: If the old and new SCS servers have the same IP, the ethernet cable from the new server must be disconnected prior to starting the Solaris operating system installation. If the old and new SCS servers have different IP address, it is recommended to connect the new SCS server to the network and assign a valid IP address prior to the Solaris operating system installation. 7 Applicable to both SCS 4.1.2 and SCS 6.0 migration: On the new server: Reinstallation of Solaris 9 or Solaris 10 on the new server. The disk partitioning on new server may not match the Nortel GGSN SCS recommended disk partitioning. A Solaris operating system reinstallation will be required to update the new server with the Nortel GGSN SCS recommended disk partition. If the SCS is upgraded/ migrated to SCS 6.0 - Perfom a new installation of Solaris 9, refer to Nortel Installation Method 0000003-24-8096. Please contact Nortel support to request the Installation Method document. If the new server is Sun Netra T5220, (SCS is upgraded/ migrated to SCS 6.0.1), Perform a new installation of Solaris 10, refer toAppendix S: Solaris 10 Installation on page 745 8 Applicable to both SCS 4.1.2 and SCS 6.0 migration: Install recommended patches for Solaris 9 or Solaris 10 (depending on the Solaris OS installed). Refer to Install Recommended Patches for Solaris 9 and Solaris 10 on page 452 sheet 2 of 8 Description
GPRS/UMTS
174
Table 18 Migrating SCS server to new server, same IP address upgrade procedures (continued)(includes T5220 Step Duration Tot 9 SL DT Applicable to both SCS 4.1.2 and SCS 6.0 migration: If the new server has the same IP as the old server, unplug the ethernet cable on the old server to allow IP access to the new server. 10 0:03 Applicable to both SCS 4.1.2 and SCS 6.0 migration: After Solaris OS installation, SCS 6.0 (for Solaris 9) or SCS 6.0.1 (for Solaris 10) software, SCS and iPlanet database files, SCS configuration files and GGSN patches must be FTPed to the new server. Transfer the files in BINARY mode. FTP the following files to the new server.. SCS load files: - scsserver.tar.Z - Optional: scs_corba_server.tar.Z - Optional: sslpkg.zip From the old SCS server: - /opt/patches tar file - /tftpboot/patches tar file - SCS Solid and iPlanet backup files - /etc/shasta/scs.config - copy this file to a temporary directory for reference 11 Applicable to both SCS 4.1.2 and SCS 6.0 migration: If the new server IP is same as the old server, unplug the ethernet cable from the new server reconnect the old server back to the network. sheet 3 of 8 Description
411-5221-309
Standard
06.30 March 10, 2010
175
Table 18 Migrating SCS server to new server, same IP address upgrade procedures (continued)(includes T5220 Step Duration Tot 12 0:60 SL 0:60 DT Applicable to both SCS 4.1.2 and SCS 6.0 migration: On the New Server: Perform a new install the iPlanet and SCS. Install SCS 6.0 - Refer to Appendix P: Perform a SCS 6.0 new install on page 704 or Install SCS 6.0.1 - Refer to Appendix T: Perform SCS 6.0.1 new installation on page 764 Nortel IMs have details on new installation of SCS/ GGSN. Contact Nortel Support Team if you need the instructions for SCS installation. When performing a new install of SCS and iPlanet, please follow instructions below when setting the SCS <Region ID>, <LDAPServerPort> and <LDAPRoot> <Region ID> and <LDAPServerPort> settings should be the same on the old server and the new server. LDAP root point (<LDAPRoot>) on the new SCS server must be different than the old server. This root point will used only during installation and reverted back to the original LDAPRoot after the database restore. For example: Old server LDAPRoot: uid=admin,ou=people,o=us.nortel.com New server LDAPRoot: uid=ldap,ou=people,o=us.nortel.com Description
13
0:20
0:20
Applicable to both SCS 4.1.2 and SCS 6.0 migration: On the New Server: Restore the Solid and LDAP (or iPlanet) following instructions fromDatabase restore procedure for SCS migrating to a new physical server on page 190 Here is an example capture of database migration to SCS 6.0.1 - Appendix U: SCS 6.0.1 Database Migration Example on page 777 sheet 4 of 8
GPRS/UMTS
176
Table 18 Migrating SCS server to new server, same IP address upgrade procedures (continued)(includes T5220 Step Duration Tot 14 SL DT Applicable to both SCS 4.1.2 and SCS 6.0 migration: Update LDAPRoot in <SCS_ROOT>/bin/.scs.config and /etc/shasta/ scs.config The LDAPRoot uid must be updated to match the old server LDAPRoot uid. 15 Applicable to both SCS 4.1.2 and SCS 6.0 migration: Restart SCS and iPlanet processes. See Start SCS server. Enable SCSWatch and LDAPWatch on page 201. Check SCS processes and resync all the Devices. <SCS_ROOT>/bin/SCSAdmin status 16 Applicable to both SCS 4.1.2 and SCS 6.0 migration: If the new server IP is different from the old server - On the New Server: See Changing SCS configuration on page 347 17 Applicable to both SCS 4.1.2 and SCS 6.0 migration: If the new server IP is different from the old server If there are no customer specific feature that are activated with SOC, please skip this step. If there are customer specific features, since the SCS Server IP address have been changed, the existing SOC keys have to be reapplied from Nortel and reactivated. For configuring the SOC keys and activating features, see SOC key update procedure. 18 Optional: Install the SSL package on SCS 5.0.x Server. See Optional - Installation of the SSL Package. This step is only required, if the customer wants to install and enable SSL on the SCS server. sheet 5 of 8 Description
411-5221-309
Standard
06.30 March 10, 2010
177
Table 18 Migrating SCS server to new server, same IP address upgrade procedures (continued)(includes T5220 Step Duration Tot 19 0:05 SL 0:05 DT Install the SCS Client for the New Server: See SCS client installation on page 355 See SCS Client upgrade procedures on page 355 Note: If SCS Server is SSL enabled, the SCS Client machine should also be SSL enabled for the client to function normally. If you have enabled SSL on the SCS Server in the previous step, refer to Enabling SSL on the SCS Client on page 384 for more details on how to enable SSL on client machine. SSL enabling will be done after the SCS Client installation. 20 Enable iPlanet Directory Server security. See Step 22 on page 269. 21 Change the pmuser password. This step is optional. See Change the pmuser password on page 268 22 Setup a periodic SCS backup scheme. Please refer to SCS Periodic Backup setup option on page 225 Description
GGSN MIGRATION PROCEDURE: The new server is ready for operation. Please schedule a maintenance window to move the GGSNs to the new server. 23 If the new server IP is same as the old server, disconnect the old SCS server from the network. Connect the new SCS server to the network. If the new server IP is differnet from the old server, it is recommended to have the old server connected to the network. sheet 6 of 8
GPRS/UMTS
178
Table 18 Migrating SCS server to new server, same IP address upgrade procedures (continued)(includes T5220 Step Duration Tot 24 SL DT If the SCS region has multiple GGSNs, migrate the GGSNs one at a time to the new SCS server. Perform a resync and verify the GGSN comes insync on the new SCS server. Verify the first migrated GGSN can process mobile activations without issues prior to moving the other GGSNs. Log on to the SCS Client on the old SCS Server, right click on the device to be moved, click on configuration, click on Management, and change the GGSN Administrative Status to down. On the New Server: For Each GGSN: Before resyncing the GGSN, stop the traffic on the GGSN to be resynched. See Reject GGSN incoming traffic on page 522 Log in to the GGSN as admin user. In case the old and new SCS server IP addersses are different: Update the new SCS server IP address in the GGSN quickstart configuration. See Change the GGSNs SCS IP address on page 571 The GGSN to be migrated to the new SCS server must be rebooted manually from the GGSN CLI. This is applicable to both cases where the old and new SCS server have same or different IP addresses. Reboot the GGSN by issuing the command: reboot Description
25
Log in as device_owner user to the SCS client and connect to the new SCS server IP address. Resync the first GGSN. Verify the GGSN is insync and there are no sequence number mismatch session errors. Log on SCS Client with the user device_owner, go to Device Manager and verify that all the GGSNs are in sync. Open Diagnostics & Maintenance Dialog, then select Session Errors tab and verify that there are no sequence number mismatch session errors. Verify GGSN is able to process incoming mobile activations. sheet 7 of 8
411-5221-309
Standard
06.30 March 10, 2010
179
Table 18 Migrating SCS server to new server, same IP address upgrade procedures (continued)(includes T5220 Step Duration Tot 26 27 28 SL DT If there are other GGSNs configured on the old SCS server, migrate the GGSNs one at a time. Take a backup of the Databases as soon as the upgrade to GGSN 5.0/ 5.0.1 is over. See Database backup procedure for SCS on page 242. Optional: Apply OS hardening for Solaris 9 or Solaris 10, please see OS Hardening of GGSN SCS Server on page 348 The OS hardening makes the system secure from unauthorized access and modification. 29 If a GGSN upgrade is performed: Refer toUpgrade to GGSN 6.0 software on page 533 Description
sheet 8 of 8
An example capture is presented inAppendix U: SCS 6.0.1 Database Migration Example on page 777
Table of roll-back procedures after migrating to new SCS server with same or different IP address
The rollback procedures provide instructions to revert to the prior version of the SCS Software on the original server. Note: If the GGSN software was upgraded to GGSN 5.0/ 5.0.1, it must be rolled back first before rolling back the SCS. See the GGSN roll back procedures in GGSN Rollback procedure on page 547. This must be performed prior to the SCS roll back.
GPRS/UMTS
180
Table 19 Migrating SCS server to new server, same IP address or different IP, roll-back procedures Step Duration Tot 1. SL DT Perform a patch audit on the GGSN. Determine the GGSN patch level from the SCS client (device_owner) user. Patches on the old SCS server may need to be updated to match the patch level indicated from SCS Client - Patch Manager. 2. For Each GGSN: Before resyncing the GGSN, stop the traffic on the GGSN(s) to be moved to the old SCS server. Refer toReject GGSN incoming traffic on page 522 Disable traffic on one GGSN only. After making sure the GGSN comes back insync from the old SCS server, the other GGSN(s) can be moved to the old SCS server. 3. 0:05 0:05 On new server: Refer toStop SCS server. Disable LDAPWatch on page 203 Close all your existing SCS Clients If the new server has same IP address as the old server: - On the new server - Disconnect the ethernet cable - On the old server - Reconnect the ethernet cable Description
If the new server does not have the same IP as the old server: - On the new server: The ethernet cable from the new server need not be disconnected - On the old server: Make sure the ethernet cable is connected. Verify pinging the GGSN management IP address.
FTP the required GGSN patches to the old SCS server. 4

sheet 1 of 2
0:05
0:05
On old server: Start SCS server proceses. Refer to Start SCS server. Enable SCSWatch and LDAPWatch on page 201
411-5221-309
Standard
06.30 March 10, 2010
181
Table 19 Migrating SCS server to new server, same IP address or different IP, roll-back procedures (continued) Step Duration Tot 5 0:15
per GGSN
Description DT 0:15
per GGSN
SL
If the SCS region has multiple GGSNs, migrate the GGSNs one at a time to the old SCS server. Perform a resync and verify the GGSN comes insync on the old SCS server. Verify the first migrated GGSN can process mobile activations without issues prior to moving the other GGSNs. Log in to the GGSN as admin user. Update the new SCS server IP address in the GGSN quickstart configuration. Please refer toChange the GGSNs SCS IP address on page 571 Reboot the GGSN after the SCS server IP has been modified. Issue the command: reboot
Resync the GGSN. Refer toResync with iSOS Ver. on page 572 After the resync, allow the traffic to start again. Please refer to steps Upgrade to GGSN 6.0 software on page 533
0:30
See SCS Post-upgrade / Rollback checklists on page 304 The post upgrade / roll back checks have to be executed every day for 7 days after the rollback, to make sure the SCS server is functioning properly after the rollback.
0:15
per GGSN
0:15
per GGSN
If the SCS server region has multiple GGSNs, move the other GGSNs to the old SCS server.
sheet 2 of 2
GPRS/UMTS
182
Database backup and restore procedures for migrating to a new physical server
Nortel Networks
Database backup and restore procedures for migrating to a new physical server 9
Note: This procedure requires a fresh installation of SCS on the new server. During the LDAP or iPlanet and SCS installation, make sure LDAPRoot point on the new server is different from the old server.
Database backup procedure for SCS migrating to a new physical server

Create a temporary backup directory to store the SCS and LDAP database backups. This directory can then be tared up and FTPed to the new server. Make sure you have sufficient space to store the backup.You can use df -k to check the current disk usage and space available.
Example: # df -k
The example assumes the server has enough disk space in /opt.
# cd /opt # mkdir backup_to_move
SCS processes must be running in order to perform a solidDB backup. Verify SCS processes are running before proceeding to the SCS server solidDB backup.
# cd /etc/shasta # more scs.config | grep SCSHead Example: SCSHead=/opt/shasta/scs <SCS_ROOT> = SCSHead = /opt/shasta/scs # cd <SCS_ROOT>/bin Example: # cd /opt/shasta/scs/bin # ./SCSAdmin status
Running Running Running Running Running Solid Database Server since Feb_14 (pid=7287) SCS Daemon since Feb_14 (pid=7305) SCS Domain Server since Feb_14 (pid=7320) SNMP Proxy since Feb_14 (pid=7503) SCS Region Server since Feb_14 (pid=7524)
Running SCS Monitor Server since Feb_14 (pid=7546) Running SCS Trap Daemon since Feb_14 (pid=7571)
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialDatabase backup and restore procedures for migrating to a new physical server
Running SCS Pull Server since Feb_14 (pid=7637) Running SCS Log Server since Feb_14 (pid=7673) Running SCS CORBA Server since Feb_14 (pid=7509) SSL is not enabled on present servers All SCS server processes are running. Version SCS GGSNS<version>_SCS<version>(xx)
183
Note: If customer is not using Corba server, you will not see the Corba Server running.
Backup Solid Database SCS backup script SCSAdmin backup solidDB <backup directory> backs up the following files to <SCS_ROOT>/opt/solidSolaris/database/<backup directory> directory. database file - solid.db configuration file - solid.ini log files - solXXXXX.log
Make sure <backup directory> is unique and does not exists in <SCS_ROOT>/opt/solidSolaris/database directory. On an SCS server, the backup can be executed with the following command (log in as root): To backup Solid database:
# cd <SCS_ROOT>/bin # ./SCSAdmin backup solidDB backup_directory
The backup utility will create the backup_directory directory, or if it exists will query the user for overwrite confirmation. Tar up and compress the solidDB backup directory and move it to the temporary backup directory created in the beginning of the procedure. Here is an example backup using SCSAdmin backup solidDB <backup directory>. solidDB backup directory is tarred, compressed and moved to temporary backup directory /opt/backup_to_move. 1. Perform Backup
# ./SCSAdmin backup solidDB backup<SCS_version> Here, replace <SCS_version> with the SCS server you are working on.
Here is an example to backup SCS 5.0.2:

# ./SCSAdmin backup solidDB backup<SCS_version>
GPRS/UMTS
184
Nortel Networks
Example: # ./SCSAdmin backup solidDB solid502 binDir is /opt/shasta/scs502/bin head is /opt/shasta/scs502 configFile is /opt/shasta/scs502/bin/.scs.config backup_dir is /opt/shasta/scs502/opt/solidSolaris/database/ solid502 Solid Remote Control v.04.00.0025 (C) Copyright Solid Information Technology Ltd 1993-2003 Exit by giving command: exit Backup started. .......
2. Verify backup directory. Here is an example.

# cd ../opt/solidSolaris/database # ls backup412
backup
default
solid
# ls backup412 sol00027.log sol00028.log solmsg.out
solid.db
solid.ini
3. Tar, compress and move backup to temporary backup directory

# tar cvf backup412.tar backup412 # compress backup412.tar # ls backup412 backup412.tar.Z backup default solid File backup412.tar.Z is the compressed solidDB backup. # mv backup412.tar.Z /opt/backup_to_move
411-5221-309
Standard
06.30 March 10, 2010
185
Backup LDAP database On an SCS server, to back up the LDAP database, you should perform an online backup using the ldapsearch command line script. It is required that LDAP is running to execute the ldapsearch. The output of the ldapsearch command will be directed to a file, which will be used for restoring the LDAP database when required. Make a note of the LDAP server installation directory
#cat /etc/shasta/scs.config | grep LDAPPath Example: LDAPPath=/opt/shasta/ldap <LDAP_ROOT> = LDAPPath = /opt/shasta/ldap
Check LDAP server process is running:

# ps -aef | grep -v grep | grep slapd nobody 611 1 0 20:04:04 ? 0:01 ./ns-slapd -f / opt/shasta/ldap/slapd-urc2y3pa/config/slapd.conf -i /opt/ shasta/
Check LDAP admin process is running:

# ps -aef| grep -v grep | grep admin root 310 1 0 Jan 20 ? opt/shasta/ldap/admin-serv/config 0:03 ./ns-admin -d /
If the above ps -aef command does not return a result, then start the LDAP directory server and admin server processes. To start LDAP directory server process:
# cd <LDAP_ROOT> # slapd-<hostname>/start-slapd
To start LDAP admin server process:

# ./start-admin
Run the above ps -aef command and verify the processes are running. Make a note of the LDAPServerPort and LDAPRoot before proceeding to the ldapsearch procedure. Pay close attention to LDAPRoot root point in the current server installation. This information is needed during the SCS new server installation. a. To find out LDAPServerPort:
#cat /etc/shasta/scs.config | grep LDAPServerPort GPRS/UMTS Upgrade Manual GGSN6.0
186
Database backup and restore procedures for migrating to a new physical server Example: LDAPServerPort=389
Nortel Networks
b. To find out LDAPRoot:

# cat /etc/shasta/scs.config | grep LDAPRoot Example: LDAPRoot="uid=ushasta,ou=people,o=us.nortel.com"
Note: Make a note of the LDAPRoot point as it will be required during the LDAP restore procedure on the new server. LDAPServerPort and LDAPRoot will be used as arguments to the ldapsearch script. Reset LDAP root DN name and password: This step is required if the LDAP Root DN or password were modified. If the LDAP is installed using the Nortel provided ns_server_setup.sh script, the password will be password. And if the password is not known, you can change the password in from the LDAP console. If you are not sure if LDAP Root DN or password was changed, modify it to: According to the SCS release, modify the Root DN/ password to the following: For SCS 4.1.2/ LDAP 4.1.6: Root DN: cn=Directory Manager Password: password For SCS 5.0.2 and SCS 6.0/ iPlanet 5.1: Root DN: cn=Directory Manager Password: dmanager The cn name is displayed as Root DN. The password is encrypted. To obtain the cn name, use the following procedure.
1.
Change directory to <LDAP_ROOT>

#cd <LDAP_ROOT> # cd /opt/shasta/ldap
411-5221-309
Standard
06.30 March 10, 2010
187
2. Set unix DISPLAY environment variable: setenv DISPLAY IP:0:0 3. Launch the LDAP GUI console.
#./startconsole &
4. The LDAP GUI will open. Enter the LDAP Password. 5. Double click on Your server listing (For example, zrcjs0e.us.nortel.com) 6. Double click on Server Group, and then double click on Directory Server. This will open the Directory Server window. 7. Click on the Configuration tab, next to Tasks. 8. Click on Manager Tab, in the configuration window. The following window will appear.
9. Click Save and exit LDAP console.
GPRS/UMTS
188
Nortel Networks
Perform LDAP backup using ldapsearch: 1. At the command prompt, change to the LDAP directory.
# cd <LDAP_ROOT>/shared/bin
Run the ldapsearch command line script as follows:

# ./ldapsearch -p <LDAP Server Port #> -T -b <LDAP Root Point> objectclass=* > <filename>
The ldap database is now backed up in <filename> file. Example for the command:
#./ldapsearch -p 389 -T -b uid=ushasta,ou=People,o=us.nortel.com objectclass=* > ldapdata
The Unix > operator directs ldapsearch results to backup file ldapdata. The backup file ldapdata will be created in the <LDAP_ROOT>/shared/bin. Verify file ldapdata is created and copy the backup file to the temporary backup directory created in the beginning of the procedure.
Example: # pwd /opt/shasta/ldap/shared/bin # cp ldapdata /opt/backup_to_move
Verify the temporary backup directory and make sure the backup files have been copied correctly.
# cd /opt/backup_to_move # ls
Note: The backup files generated from these procedures should be stored on an alternate server to protect against hardware failure. FTP the backed up files to the new server:
# cd /opt/backup_to_move # ftp <New Server IP> ftp> cd /opt ftp> mkdir backup_to_restore
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialDatabase backup and restore procedures for migrating to a new physical server ftp> bin ftp> hash ftp> mput *
End of Backup Procedure
189
GPRS/UMTS
190
Nortel Networks
Database restore procedure for SCS migrating to a new physical server 9

Perform SCS fresh install (see Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name on page 633 for a screen capture of the process). After LDAP and SCS servers have been installed, proceed to the restore procedure. Procedure: Uncompress and untar the solidDB backup from the old server and copy LDAP and solidDB backups to the SCS and LDAP server directories.
Example:
1. This step assumes /opt/backup_to_restore has the backup from the old server.
# cd /opt/backup_to_restore # ls ldapdata backup412.tar.Z
2. Uncompress and untar solidDB backup:

# uncompress backup412.tar.Z # tar xvf backup412.tar # ls backup412 sol00027.log sol00028.log solmsg.out
solid.db
solid.ini
3. Verify SCS installation directory:

# cat /etc/shasta/scs.config | grep SCSHead Example: SCSHead=/opt/shasta/scs <SCS_ROOT> = SCSHead = /opt/shasta/scs
4. Verify LDAP installation directory:

# cat /etc/shasta/scs.config | grep LDAPPath Example: LDAPPath=/opt/shasta/ldap <LDAP_ROOT> = LDAPPath = /opt/shasta/ldap
5. Create backup directory in <SCS_ROOT>/opt/solidSolaris/database:
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialDatabase backup and restore procedures for migrating to a new physical server # cd <SCS_ROOT>/opt/solidSolaris/database # mkdir backup Example: # cd /opt/shasta/scs/opt/solidSolaris/database # mkdir backup # cd backup
191
6. Copy solidDB backup files to new server <SCS_ROOT>/opt/solidSolaris/ database/backup.

# cp /opt/backup_to_restore/backup412/* .
7. Copy ldapdata to <LDAP_ROOT>/shared/bin Example:

# cd /backup_to_restore # cp ldapdata /opt/shasta/ldap/shared/bin
As part of migration of SCS Server to a new physical server, restore the LDAP database first, then restore the SCS solid database.
GPRS/UMTS
192
Nortel Networks
LDAP (or iPlanet) database modifications on the new SCS server WARNING: Restoring a database overwrites your existing database files. The process for restoring a previously generated backup consists of copying the database and associated index files from the backup location to the database directory. The database can be restored from the command line by using the ldapmodify command line script. For restoring the LDAP database using the ldapmodify, the following are required. The backed up file for the LDAP data, The Root DN name which is Directory Manager by default, and its password.
The steps involved in the LDAP restore are: 1. If the new SCS server domain name (Fully Qualified Domain Name) is different from the old SCS server, edit the LDAP backup file. For example, on your old SCS server, the FQDN used is us.nortel.com and on the new SCS Server, the FQDN used is us.nt.nortel.com. If the FQDN name is the same between the old and new SCS Server, then skip this step. All the instances of FQDN in the LDAP backup file should be changed to the new FQDN. For section Edit the LDAP backup file below for details. 2. Identify the LDAP Root DN Name and Password. For more details, see Modify LDAP root DN name and password if you have not used ns_server_setup.sh script to install the LDAP server. If you have used ns_server_setup.sh to install LDAP, skip this step. on page 194 3. Restore the LDAP data using the ldapmodify. For details, see Restore the LDAP database using ldapmodify on page 196
Edit the LDAP backup file Note: If the FQDN is the same for old and new SCS Servers, skip this step. Use a text editor, e.g. vi, to replace all the occurrences of FQDN with the new FQDN in the backed up file. Make sure there is no old FQDN name in the file. Note: The first dn which contains SCS LDAPRoot may be encrypted, so you may not see FQDN in it. Also replace this dn in the file with a line like this:
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialDatabase backup and restore procedures for migrating to a new physical server dn: uid=<ldapRootUid>,ou=People,o=<domain name>
193
Example
dn: uid=scs502,ou=People,o=ca.nt.com
Here is snap shot of the original LDAP data backup file

version: 1 dn:: dWlkPWJodDEsb3U9UGVvcGxlLG89dG1hLmNvbS52biA= uid: scs502 givenName: scs502 objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson sn: Shasta cn: UShasta Shasta dn: dc=ISPs,uid=scs502,ou=People,o=us.nortel.com dc: ISPs objectClass: top objectClass: domain
Here is snap shot of the modified LDAP data backup

version: 1 dn: uid=scs502,ou=People,o=ca.nt.com uid: scs502 givenName: scs502 objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson sn: Shasta cn: UShasta Shasta dn: dc=ISPs,uid=scs502,ou=People,o=ca.nt.com dc: ISPs objectClass: top objectClass: domain
From this example:

+ ldapRootUid is scs502 + The old domain name is us.nortel.com
GPRS/UMTS
194
Nortel Networks
+ The new domain name is ca.nt.com
Modify LDAP root DN name and password on the new SCS server Modify LDAP root DN name and password if you have not used ns_server_setup.sh script to install the LDAP server. If you have used ns_server_setup.sh to install LDAP, skip this step. According to the SCS release, modify the Root DN/ password to the following: For SCS 4.1.2/ LDAP 4.1.6: Root DN: cn=Directory Manager Password: password For SCS 5.0.2 and SCS 6.0/ iPlanet 5.1: Root DN: cn=Directory Manager Password: dmanager To obtain the cn name, use the following procedure. 1. Change directory to <LDAP_ROOT> (or <IPLANET_ROOT>
#cd <LDAP_ROOT>
2. Set unix DISPLAY environment variable: setenv DISPLAY IP:0:0 3. Launch LDAP (or iPlanet console)
#./startconsole&
4. The LDAP GUI will open. Enter the LDAP Password. 5. Double click on the server listing (For example, zrcjs0e.us.nortel.com) 6. Double click on Server Group, and then double click on Directory Server. This will open the Directory Server window. 7. Click on the Configuration tab, next to Tasks.
411-5221-309
Standard
06.30 March 10, 2010
195
8. Click on Manager Tab, in the configuration window. The following window will appear.
The cn name is displayed as Root DN. The password is encrypted. If the LDAP is installed using the Nortel provided ns_server_setup.sh script, the password will be password. And if the password is not known, you can change the password in this window and click on Save. (DO NOT CLOSE THE GUI)
Database Restore on the new SCS server 1. On the new server, verify SCS processes are running. If the SCS server processes are not running, start the processes. Next, make a note of the LDAPRoot. You need to change the LDAPRoot point to match the old server.
# cd /etc/shasta # cat scs.config | grep SCSHead Example: SCSHead = /opt/shasta/scs <SCS_ROOT> = SCSHead = /opt/shasta/scs
GPRS/UMTS
196
Database backup and restore procedures for migrating to a new physical server # cat scs.config | grep LDAPRoot LDAPRoot ="uid=admin,ou=people,o=us.nortel.com"
Nortel Networks
# cd <SCS_ROOT>/bin # ./SCSAdmin status Example: # cd /opt/shasta/scs/bin # ./SCSAdmin status
If SCS processes are not running, start the processes. # ./SCSAdmin start # ./SCSAdmin status
Restore the LDAP database using ldapmodify To restore LDAP data from the command line: 1. Change directory to <LDAP_ROOT>/shared/bin (or <IPLANET_ROOT>/shared/bin)
#cd <LDAP_ROOT>/shared/bin
2. Run the ldapmodify. The default LDAP Root DN password for SCS 4.1.2 is password The default iPlanet Root DN password for SCS 5.0.2 and SCS 6.0 is dmanager Pass the appropriate password to the following ldapmodify command. In the example below, the Root DN password is set to password.
# ./ldapmodify -p <LDAP Server Port #> -D Root DN -w <Root DN Password> -c -a -f <LDAP data file name> Example: #./ldapmodify -p 389 -D cn=Directory Manager -w password -c -a -f ldapdata
411-5221-309
Standard
06.30 March 10, 2010
197
Restore Solid database WARNING: Restoring a database overwrites your existing database files. Restoring a Solid database can be done manually or by using the SCSAdmin command. The following are the steps to restore the database manually using the SCSAdmin command: 1. Use the SCSAdmin command to restore the Solid database. Note: The files required for the restore are listed in the database backup procedure. They are solid.db, solXXXX.log, and solid.ini files.
# cd <SCS_ROOT>/bin # ./SCSAdmin restore solidDB
By default, the restore command will restore files from the <SCS_ROOT>/opt/solidSolaris/database/backup directory. Here is a snap shot for the execution of the above command
# ./SCSAdmin restore solidDB This will overwrite database(s). Are you sure? (Y)es or (N)o: y Delete the old database... Restore the database from /opt/scs32/opt/solidSolaris/ database/backup ... Done.
LDAPRoot modification in .scs.config 1. Modify LDAPRoot in <SCS_ROOT>/bin/scs.config to match the old server. If the LDAPRoot point on the old and new servers are the same, modifying .scs.config is not necessary. Before proceeding, find out the LDAPRoot of the old server. You can follow the procedure below to find out the LDAPRoot on the old and new server.
# cd <SCS_ROOT>/bin # cat .scs.config | grep LDAPRoot
2. Modify <LDAPRoot> point so that the root point on the old and new server are same:
198
Nortel Networks
On the new server, edit <SCS_ROOT>/bin/.scs.config and modify LDAPRoot parameter to match the old server.
# cd <SCS_ROOT>/bin
Edit file .scs.config with vi editor. Go to the line LDAPRoot and modify the root point to match the old server LDAPRoot.
# vi .scs.config
Restart LDAP and SCS server processes 1. Enable LDAP Watch

# cd <SCS_ROOT>/bin # ./LDAPWatch-enable
2. Restart LDAP server process

# cd <LDAP_ROOT>/slapd-<hostname> # ./stop-slapd # ./start-slapd
3. Restart LDAP admin

# cd <LDAP_ROOT> # ./restart-admin
4. Restart SCS Processes

# cd <SCS_ROOT>/bin # ./SCSAdmin restart
Note: Restarting the SCS server may be fail with the following error message:
Starting Solid Database Server:[1] + Exit 100 /opt/nortel/ SCS50/opt/solidSolaris/bin/solid -f -c ... .Solid database has the following error: Code: 10016 (DBE_ERR_LOGFILE_CORRUPT)
411-5221-309
Standard
06.30 March 10, 2010
199
If the problem occurs: 1. Deletes all log files of SCS SOLID database directory in <SCS_ROOT>/ opt/solidSolaris/database/default. Here <SCS_ROOT> indicates the current SCS server root directory 2. Restarts SCS
# cd <SCS_ROOT>/bin # ./SCSAdmin restart
These log files is not useful for the new SCS server any more, so deleting does not cause any damages.
End of Backup Procedure
GPRS/UMTS
200

Basic SCS Server Maintenance
10
10
Perform regular SCS server backup and store the backup on a different server. The are multiple options to backup the SCS server. See Database backup and restore procedures on page 233 for details. Periodically check the SCS server disk usage. If any of the critical file system (/, /usr, /var, /opt) disk space reaches 99%, SCS server processes automatically shutdown. See System Command df -k on page 158 for details. If SSL is enabled on the SCS server, then have a backup copy of the SSL certificates handy. This will be useful during a database restore. To find out if SSL is enabled on the SCS server, run <SCS_ROOT>/bin/ SCSAdmin status. Here <SCS_ROOT> is the current SCS installation directory. Please refer to NTP Nortel GGSN Provisioning Procedures: 411-5221-927 for details on how to generate SSL certificates for SCS server and client.
Basic system settings required on the SCS:

Make sure you are in C - shell.
#echo $SHELL
10
This will show the present shell. If the default shell for root is not set as csh, then modify /etc/passwd and put in /usr/bin/csh instead of the preconfigured shell. Find the path where csh is located.
# which csh /usr/bin/csh Use vi editor to modify the shell entry for root user. # more /etc/passwd root:x:0:1:Super-User:/:/usr/bin/csh
After modifying /etc/passwd, login to the server as root from another telnet window. This way, if there was some error modifying /etc/passwd, and you are unable to log back in to the server, you are still logged into the server in the original window that was used to modify the file. Make sure to correct any errors in /etc/passwd in case of a login failure. Other system settings needed are: File /etc/nsswitch.conf contains: hosts: file dns
411-5221-309 Standard 06.30 March 10, 2010
201
Example: hosts:file dns File /etc/resolv.conf contains: domain <domain name> Example: domain my.company.com File /etc/hosts contains: <machines static ip address> <hostname> <fqdn> loghost Example: 99.100.100.100 scshost scshost.my.company.com loghost
Determine SCS and LDAP/ iPlanet installation directories

1. To determine the SCS installation directory, also referred as <SCS_ROOT>:
10
The path returned by SCSHead is the current SCS installation directory. Here is an example:
# cat /etc/shasta/scs.config | grep SCSHead SCSHead=/opt/shasta/scs6.0
2. To determine LDAP/ iPlanet installation directory, also referred as <LDAP_ROOT> or <IPLANET_ROOT>. The path returned by LDAPPath is the current LDAP/ iPlanet installation directory. Here is an example:
Determine the LDAP/ iPlanet instance name referred as <LDAPServerName>.

# cat /etc/shasta/scs.config | grep LDAPServerName LDAPServerName=slapd-urc2y1th
Note: The LDAP/ iPlanet start/ stop scripts are located in <LDAPPath>/<LDAPServerName>.
Start SCS server. Enable SCSWatch and LDAPWatch

Use this command to start the SCS server applications.
GPRS/UMTS
10
202
To determine <SCS_ROOT>: 3. Login to the SCS server as root user. 4. Determine the SCS home directory
The path returned in the above step is <SCS_ROOT>. 5. Start SCS server processes
# cd <SCS_ROOT>/bin # ./SCSAdmin start
/opt/shasta/scs502/bin/SCSWatch-disable: SCSWatch is already disabled /opt/shasta/scs502/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled /opt/shasta/scs502/bin/SCSDiskUsageMonitor-disable: SCSDiskUsageMonitor is alrea dy disabled /opt/shasta/scs502/bin/SCSCleanXmlExportFiles-disable: SCSCleanXmlExportFiles is already disabled [1] 6685 Starting Solid Database Server:.Started [2] 6703 Starting SCS Daemon:.Started [3] 6715 Starting SCS Domain server:.......Started [4] 6747 Starting SNMP Proxy:Started [5] 6753 Starting SCS CORBA Server:........Started [6] 6777 Starting SCS Region server:.....Started [7] 6802 Starting SCS Monitor server:.....Started [8] 6844 Starting SCS Trap daemon:.....Started [9] 6870 Starting SCS Pull Server:...Started [10] 6889 Starting SCS Log Server:..Started ------------------------------------------Nortel Service Creation System Server Version SCS GGSNS5.0.2_SCS5.0(14) ------------------------------------------Adding SCSCleanLogcsv first time Added SCSCleanLogcsv to crontab Adding SCSWatch to Crontab for first time. Added SCSWatch to crontab Adding SCSDiskUsageMonitor first time Added SCSDiskUsageMonitor to crontab Adding SCSCleanXmlExportFiles first time Added SCSCleanXmlExportFiles to crontab
411-5221-309
Standard
06.30 March 10, 2010
203
6. Enable SCSWatch. This script checks the status of the SCS server processes. If any of the processes are down, then SCSWatch will restart the process.
#<SCS_ROOT>/bin/SCSWatch-enable
7. Enable LDAPWatch. This script checks the status of the LDAP or iPlanet server processes. If the process is down, then LDAPWatch will restart the process.
#<SCS_ROOT>/bin/LDAPWatch-enable
Stop SCS server. Disable LDAPWatch

Use this command to stop the SCS server applications.
10
<SCS_ROOT> is the installation directory of the particular SCS you want to start. To determine <SCS_ROOT>: 1. Login to the SCS server as root user. 2. Determine the current SCS home directory
# cd <SCS_ROOT>/bin # ./SCSAdmin stop
/opt/shasta/scs502/bin/SCSWatch-disable: SCSWatch is already disabled /opt/shasta/scs502/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled Removed SCSDiskUsageMonitor from crontab Removed SCSCleanXmlExportFiles from crontab [1] 6370 Stopping SCS CORBA Server:.[1] + Done /opt/shasta/scs502/opt/jre/bin/ java -cp ....Stopped [1] 6384 Stopping SCS Log Server:.[1] + Done /opt/shasta/scs502/opt/jre/ bin/java -cp ....Stopped [1] 6398 Stopping SCS Pull Server:.[1] + Done /opt/shasta/scs502/opt/jre/ bin/java -cp ....Stopped [1] 6412 Stopping SCS Trap Daemon:.[1] + Done /opt/shasta/scs502/opt/jre/ bin/java -cp .....Stopped [1] 6432 Stopping SCS Monitor Server:.[1] + Done /opt/shasta/scs502/opt/jre/ bin/java -cp ...Stopped [1] 6440 Stopping SCS Region Server:.[1] + Done /opt/shasta/scs502/opt/jre/ bin/java -cp ...Stopped Stopping SNMP Proxy:.Stopped
GPRS/UMTS
204

[1] 6462 Stopping bin/java [1] 6470 Stopping bin/java Stopping SCS Domain Server:.[1] -cp ...Stopped + Done

/opt/shasta/scs502/opt/jre/ /opt/shasta/scs502/opt/jre/
SCS Daemon:.[1] + Done -cp ....Stopped Solid Database Server:.Stopped
Note: If the SCS Server is SSL Enabled, and if you see a warning message Warning: subject (somename, EMAIL=somename@nortel.com) does not match server name (SSL Plus Sample RSA Server Certificate) while stopping the SCS Processes, please ignore the message. 4. Disable LDAPWatch. This script checks the status of the LDAP or iPlanet server processes. If the process is down, then LDAPWatch will restart the process.
#<SCS_ROOT>/bin/LDAPWatch-disable
Enable LDAPWatch
10
Use the following command to enable LDAPWatch. This script checks the status of the LDAP or iPlanet server processes. If the process is down, then LDAPWatch will restart the process. 1. Login to the SCS server as root user. 2. Determine the SCS home directory
# cd <SCS_ROOT>/bin
4. Enable LDAPWatch.
If you performing the above step during an upgrade, return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
411-5221-309
Standard
06.30 March 10, 2010
205
Disable LDAPWatch
10
Use the following command to disable LDAPWatch. This script checks the status of the LDAP or iPlanet server processes. If the process is down, then LDAPWatch will restart the process. 1. Login to the SCS server as root user. 2. Determine the SCS home directory
# cd <SCS_ROOT>/bin
4. Disable LDAPWatch.
#<SCS_ROOT>/bin/LDAPWatch-disable
Disable SCS provisioning

Use this command to disable SCS Provisioning.
# <SCS_ROOT>/bin/SCSAdmin disableProvisioning
10
If you performing the above step during an upgrade, return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
Enable SCS provisioning

Use this command to enable SCS Provisioning.
# <SCS_ROOT>/bin/SCSAdmin enableProvisioning
10
Check SCS provisioning status

Use this command to verify SCS Provisioning status.
# <SCS_ROOT>/bin/SCSAdmin status
10
Start the LDAP / iPlanet server. Enable LDAPWatch
10
Use these commands to start the directory server process. For Netscape Directory Server 4.16 and iPlanet Directory Server 5.1, the commands are the same. Determine the LDAP or iPlanet installation directory 1. Determine the current iPlanet home directory
206
# cat /etc/shasta/scs.config | grep LDAPPath | cut -f 2- -d=
2. Change directory to path indicated in the above step. 3. Determine the directory server name
# cat /etc/shasta/scs.config | grep LDAPServerName | cut -f 2- -d=
4. Change directory to directory server name returned in the above step.

# ./start-slapd # cd .. # ./start-admin
The following is the output for the start-admin command for LDAP 4.16. If you see a warning about the super-user, please ignore that.
# start-admin Info: Cache expiration set to 600 seconds Netscape-Administrator/4.2 B2001.300.0126 startup: listening to http://zrc2s0mc, port 23611 as root warning: daemon is running as super-user)
The following is the output for the start-admin command for iPlanet 5.1.
# ./start-admin iPlanet-WebServer-Enterprise/6.0SP2 B01/06/2003 22:24 Info: Cache expiration set to 600 seconds warning: daemon is running as super-user [LS ls1] http://urc2y3pa.us.nortel.com, port 33611 ready to accept requests startup: server started successfully
5. Determine the current SCS home directory

The path returned in the above step is <SCS_ROOT>. 6. Enable LDAPWatch

Disable LDAPWatch. Stop the LDAP / iPlanet
10
Use these commands to disable LDAPWatch and stop the LDAP or iPlanet server processes. 7. Login to the SCS server as root user. 8. Determine the current SCS home directory
411-5221-309
Standard
06.30 March 10, 2010
207
cat /etc/shasta/scs.config | grep SCSHead | cut -f 2- -d=
The path returned in the above step is <SCS_ROOT>. 9. Disable LDAPWatch

# <SCS_ROOT>/bin/LDAPWatch-disable
10. Determine the current LDAP or iPlanet home directory

cat /etc/shasta/scs.config | grep LDAPPath | cut -f 2- -d=
cat /etc/shasta/scs.config | grep LDAPServerName | cut -f 2- -d=
13. Change directory to directory server name returned in the above step. 14. Stop LDAP or iPlanet server process
# ./stop-slapd
15. Stop LDAP or iPlanet admin server process

# cd .. # ./stop-admin
Remove All the LDAP Watches and SCS Watches from the crontab Use Crontab -l command to list out the crontab entries. Use these commands to stop the SCS Watches.
# <SCS_ROOT>/bin/LDAPWatch-disable # <SCS_ROOT>/bin/SCSWatch-disable # <SCS_ROOT>/bin/SCSDiskUsageMonitor-disable # <SCS_ROOT>/bin/SCSCleanXmlExportFiles-disable # <SCS_ROOT>/bin/SCSLogcsv-disable Examples:
# crontab -l #ident "@(#)root 1.19 98/07/06 SMI" /* SVr4.0 1.1.3.1 */ # # The root crontab should be used to perform accounting data collection. # # The rtc command is run to adjust the real time clock if and when # daylight savings time changes. # 10 3 * * 0,4 /etc/cron.d/logchecker 10 3 * * 0 /usr/lib/newsyslog 15 3 * * 0 /usr/lib/fs/nfs/nfsfind 1 2 * * * [ -x /usr/sbin/rtc ] && /usr/sbin/rtc -c > /dev/null 2>&1 30 3 * * * [ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/ gsscred_clean
GPRS/UMTS
208
59 11 * * * ksh -e '/opt/shasta/scs/bin/SCSCleanLogcsv.ksh 4' * * * * * /opt/shasta/scs/bin/SCSWatch 59 * * * * /opt/shasta/scs/bin/SCSDiskUsageMonitor 59 23 * * * /opt/shasta/scs/bin/SCSCleanXmlExportFiles * * * * * /opt/shasta/scs/bin/LDAPWatch # /opt/shasta/scs/bin/LDAPWatch-disable # /opt/shasta/scs/bin/SCSWatch-disable /opt/shasta/scs/bin/SCSWatch-disable: SCSWatch is being updated and disabled in Cron Removed SCSWatch from crontab # /opt/shasta/scs/bin/SCSDiskUsageMonitor-disable Removed SCSDiskUsageMonitor from crontab # /opt/shasta/scs/bin/SCSCleanXmlExportFiles-disable Removed SCSCleanXmlExportFiles from crontab # /opt/shasta/scs/bin/SCSCleanLogcsv-disable Removed SCSCleanLogcsv from crontab # crontab -l #ident "@(#)root 1.19 98/07/06 SMI" /* SVr4.0 1.1.3.1 */ # # The root crontab should be used to perform accounting data collection. # # The rtc command is run to adjust the real time clock if and when # daylight savings time changes. # 10 3 * * 0,4 /etc/cron.d/logchecker 10 3 * * 0 /usr/lib/newsyslog 15 3 * * 0 /usr/lib/fs/nfs/nfsfind 1 2 * * * [ -x /usr/sbin/rtc ] && /usr/sbin/rtc -c > /dev/null 2>&1 30 3 * * * [ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/ gsscred_clean
Verify and Stopping SCS server and LDAP server processes

1. Verify status of SCS server processes
# cd <SCS_ROOT>/bin #./SCSAdmin status
10
2. To stop SCS Processes:

#./SCSAdmin stop
3. Disable LDAPWatch
# ./LDAPWatch-disable
4. Check LDAP server processes is running

5. Check LDAP admin process is running

# ps -aef| grep -v grep | grep admin
411-5221-309
Standard
06.30 March 10, 2010
209
root 310 1 0 Jan 20 ? opt/shasta/ldap/admin-serv/config
0:03 ./ns-admin -d /
If the above ps -aef command returns a result, then stop the LDAP directory server and admin server processes. a. To stop LDAP directory server process:
# cd <LDAP_ROOT>/slapd-<hostname> #./stop-slapd
b. To stop LDAP admin server process:

# cd ../ #./stop-admin # cd /
If you performing the above steps during an upgrade, return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
Verify LDAP/ iPlanet server and admin process status

Check LDAP server processes is running
10
Check LDAP admin process is running
# ps -aef| grep -v grep | grep admin root 310 1 0 Jan 20 ? 0:03 ./ns-admin -d /opt/ shasta/ldap/admin-serv/config
To login to iPlanet admin console and verify iPlanet server performance parameter: 10
iPlanet admin server port is assigned 33611. To login to the iPlanet console, use: # cd <IPLANET_ROOT>
GPRS/UMTS
210
Note: If you are using xterm session and telnet to connect to the SCS server from another host (or PC), then export environment variable DISPLAY on the xterm console before launching iPlanet console: Example: # setenv DISPLAY hostIP:0.0 # ./startconsole & Username: admin (unless modified by user) Password: admin Administration URL: http://scshost.domain: 33611
Rebooting the SCS server
10
Note: If a monitor is not directly connected to the SCS server, you can login to the serial console to the SCS server. a. Login to the SCS server as root (if you are already logged in as root from a previous procedure, skip this step. b. Stop SCS processes first and then LDAP (or iPlanet) processes following Verify and Stopping SCS server and LDAP server processes on page 208 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206 c. Execute the following command to sync up the Solaris server hard disks.
# sync; sync; sync; sync
d. Type init 6 to reboot the server.

# init 6
Rebooting the SCS server to single user mode
10
Note: If a monitor is not directly connected to the SCS server, login to the serial console to the SCS server. IP connectivity (example: telnet access) will be disabled with the server is rebooted into single user mode. i. Login to the SCS server as root (if you are already logged in as root from a previous procedure, skip this step. ii. Stop SCS processes first and then LDAP (or iPlanet) processes following Verify and Stopping SCS server and LDAP server processes on page 208 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206
411-5221-309
Standard
06.30 March 10, 2010
211
iii. Execute the following command to sync up the Solaris server hard disks.
# sync; sync; sync; sync
iv. Type init 0

# init 0 INIT: New run level: 0
v. At the ok prompt, type boot -rs

{6} ok boot -rs Boot device: /pci@8,700000/scsi@1/disk@6,0:f File and args: -rs ... ... INIT: SINGLE USER MODE #
Modifying LDAP backup in case of server domain name change
10
Modifying the LDAP/ iPlanet backup file is needed in case the server domain name (Fully Qualified Domain Name - FQDN) is to be modified. This modified backup file can then be restored. Use a text editor, e.g. vi, to replace all the occurrences of FQDN with the new FQDN in the LDAP/ iPlanet backup file. Note: The first dn which contains SCS LDAPRoot may be encrypted, so you may not see FQDN in it. Also replace this dn in the file with a line like this: dn: uid=<ldapRootUid>,ou=People,o=<domain name> e.g. uid=scs502,ou=People,o=ca.nt.com Here is snap shot of the LDAP data backed up file. In this example:
ldapRootUid is scs502 The old domain name is us.nortel.com The new domain name is ca.nt.com
Original data from LDAP/ iPlanet backup:

version: 1 dn:: dWlkPWJodDEsb3U9UGVvcGxlLG89dG1hLmNvbS52biA= uid: scs502 givenName: scs502 objectClass: top
GPRS/UMTS
212
Basic SCS system administration objectClass: person objectClass: organizationalPerson objectClass: inetorgperson sn: Shasta cn: UShasta Shasta
dn: dc=ISPs,uid=scs502,ou=People,o=us.nortel.com dc: ISPs objectClass: top objectClass: domain
Updated data from LDAP/ iPlanet backup:

version: 1 dn: uid=scs502,ou=People,o=ca.nt.com uid: scs502 givenName: scs502 objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson sn: Shasta cn: UShasta Shasta dn: dc=ISPs,uid=scs502,ou=People,o=ca.nt.com dc: ISPs objectClass: top objectClass: domain
Resetting LDAP/ iPlanet Root DN name and password

For restoring LDAP/ iPlanet database in case of a SC Sserver move or IP address/ domainname/ hostname change, the LDAP Root DN must be:
cn=Directory Manager.
10
If LDAP Root DN was modified, reset it to cn=Directory Manager. The restoration also requires its password provided. If the you dont remember its password, it can reset as well. If the iPlanet is installed automatically during SCS 5.0.x new installation or upgrade, the default password will be 'dmanager'. In SCS 4.1.2, the default password is 'password'.
411-5221-309
Standard
06.30 March 10, 2010
213
To verify and if needed, reset Root DN and its password Change directory to <LDAP_ROOT>
#cd <LDAP_ROOT>
Set unix DISPLAY environment variable: setenv DISPLAY IP:0.0

#./startconsole &
This will launch the LDAP/ iPlanet GUI. Enter the LDAP password (default is admin). Double click on the server listing (For example, zrcjs0e.us.nortel.com) Double click on Server Group, and then double click on Directory Server. This will open the Directory Server window. Click on the Configuration tab, next to Tasks. Click on Manager Tab, in the configuration window. The following window will appear.
GPRS/UMTS
214
Figure 5 Resetting LDAP/ iPlanet Root DN and password
If the Directory Manager DN does not match cn=Directory Manager, reset the value Reset Directory Manager DN to cn=Directory Manager To reset the Directory Manager password: For SCS 5.0.2, type - dmanager For SCS 4.1.2, type - password
Click Save and exit LDAP console. Note: Users must make a note of the Directory Manager password in case it is modified to a non-default value.
411-5221-309
Standard
06.30 March 10, 2010
215
SOC key update procedure

This procedure is used:
10
After migrating SCS system to a new Physical Server with different IP address or Changing the current server IP address to a new IP address
SCSSocUtil is located in <SCS6.0_ROOT/bin>
1. Make a note of the SOC feature name and the license key. The SOC license key can be retrieved from the SCS client also. a. Login to SCS client as 'device_owner' user b. From File-> SCS Configuration, click on SOC Activation tab c. Select the SOC feature and click 'Edit' d. Select the entire SOC License Key and copy using Window copy sequence 'Ctrl-C' e. Save the SOC feature name and license key as it will be required during the SOC update procedure explained in this procedure. 2. Have the new SOC license key handy as it will ne needed during the update procedure. 3. Login as 'root' to the SCS server 4. Make a note of SCS installation directory by executing the following command:
cat /etc/shasta/scs.config | grep SCSHead
The above command will return an output similar to:

SCSHead=/opt/shasta/scs6.0
5. Change directory to <SCSHead>/bin 6. Verify SCS Processes are running.

# cd <SCS_ROOT>/bin # ./SCSAdmin status
GPRS/UMTS
216
If SCS processes are not running, start the processes

7. Make sure you can execute the following command

./SCSSocUtil -h <-This will return usage syntax for SCSSocUtil Logged in as User root SCS SOC Util application starts... Usage: SCSSocUtil serverIP:port dbUserName password update oldSOCKey newSOCKey Usage: SCSSocUtil serverIP:port dbUserName password delete SOCKey
Where: serverIP: SCS server IP address The SCS server IP address also can be obtained from: File-> SCS Configuration...-> Server Properties tab port: 1313 dbUserName: admin password: admin Use 'update' option oldSOCKey: Current SOC license key listed on SCS client newSOCKey: New SOC license key obtained from Nortel Note: Have the old SOC and new SOC license keys handy before executing SCSSocUtil.
8. Execute SCSSocUtil with update option to update the SOC license key. Here is an example:
411-5221-309
Standard
06.30 March 10, 2010
217
./SCSSocUtil 192.168.35.1:1313 admin admin update ooooooooooooooooooooooooooooooooo nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
Where strings: ooo... indicate oldSOCKey nnn... indicate newSOCKey Note: If SCS is enabled with multiple SOC features, then execute SCSSocUtil one by one to update all the SOC license keys. 9. If you have a SCS client window already open, exit the session. 10. Login to SCS client as 'device_owner' user. 11. Verify SOC license key has been updated. From File-> SCS Configuration, click on SOC Activation tab Select the SOC feature and click 'Edit' Verify the new SOC license key. Click 'OK'
If the SCS client has not refreshed the SOC key, select the SOC feature, click 'Edit' and then click 'OK'. This will refresh the entry on the SCS client. 12. Restart SCS Processes and resync GGSN.
# ./SCSAdmin restart
SOC key delete procedure
10
Delete SOC key option will delete the key entry from the database. Use this option only when the SOC feature will no longer be used. To Delete the SOC key using the SCSSocUtil script.
SCSSocUtil <serverIP:port> <dbUserName> <password> delete <SOCKey> Example: # cd <SCS_ROOT>/bin # ./SCSSocUtil 199.30.28.146:1313 admin admin delete d4b10260fe9a850d5627c475fd0c9ba0 SCS SOC Util application starts... SOC license key for feature Diameter is deleted.
GPRS/UMTS
218
Understanding Sun hard disk naming convention
10
Perform df -k or /etc/vfstab on your server. You will notice the physical partition name on a unmirrored server to cvtwdxsz. On a mirrored server, you can find this info by running /usr/sbin/metastat c - Disk Controller / v - Controller number t - Physical Bus Target / w - Target number d - Drive / x - Drive number s - Disk slice / z - Slice number With format, df -k and /etc/vfstab, we can identify the total number of hard disks available on the server and disk partitions mounted. Partitions assigned for swap can be identified from /etc/vfstab.
Modify SCS server IP address or hostname

1. Make a note of the current IP address and hostname configured on the server using ifconfig -a and uname -a. 2. Make a backup copy of /etc/hosts file.
# cp /etc/hosts /etc/hosts.old
10
3. Using vi editor, edit /etc/hosts, modify the old IP address with the new IP address. If a hostname change is required, then modify all occurrences of the old hostname associated with the old IP address with the new hostname (associated with the new IP address). 4. Make a backup copy of /etc/netmasks file.
# cp /etc/netmasks /etc/netmasks.old
5. Modify /etc/netmasks if there is a change in the subnet mask for the new IP address. 6. Modify /etc/defaultrouter if there is a change in the default router IP address for the new IP address. 7. If a hostname change is required, make a backup copy of /etc/nodename.
# cp /etc/nodename /etc/nodename.old
8. Edit /etc/nodename file. Modify the old hostname with the new hostname.
411-5221-309
Standard
06.30 March 10, 2010
219
9. If a hostname change is required, modify all occurrences of the old hostname with the new hostname in the host file in the following directories:
# /etc/net/ticlts # /etc/net/ticots # /etc/net/ticotsord
Note: There are usually 2 occurrences of the hostname in the hosts file 10. Using ifconfig -a command, find out the interface name associated with the old IP address. If a hostname and IP address change is required for the system, then verify if a file /etc/hostname.<ifname> exits for the old IP address. If the file exists, then edit file /etc/hostname.<ifname> to modify the old hostname with the new hostname. 11. Here is an example where both the IP address and hostname are modified: Old IP: 47.104.6.101 - hostname: urc2y3pa New IP: 47.104.5.30 - hostname: urc2y1th Subnet mask did not require modification (so /etc/netmasks file was not modified). Default router did not require modification (so, /etc/defaultrouter was not modified) Verify the interface name using ifconfig -a and the hostname using uname -a.
# ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 47.104.6.101 netmask fffffc00 broadcast 47.104.7.255 ether 0:3:ba:b:49:49
# uname -a SunOS urc2y3pa 5.9 Generic_118558-33 sun4u sparc SUNW,SunFire-880
Edit /etc/hosts to modify 47.104.6.101 with 47.104.5.30, modify the hostname from urc2y3pa to urc2y1th Old /etc/hosts file:
# cat /etc/hosts
127.0.0.1 47.104.6.101 localhost urc2y3pa urc2y3pa.us.nortel.com loghost
GPRS/UMTS
220
Updated /etc/hosts file:

# cat /etc/hosts
127.0.0.1 47.104.5.30 localhost urc2y1th urc2y1th.us.nortel.com loghost
Since a hostname change was required, /etc/nodename is modified. Old /etc/nodename file:
# more /etc/nodename urc2y3pa
Updated /etc/nodename file:

# more /etc/nodename urc2y1th
Since a hostname change was required, modify all occurrences of the old hostname with the new hostname in the following files:
# /etc/net/ticlts/hosts # /etc/net/ticots/hosts # /etc/net/ticotsord/hosts
Since a hostname change is required, verify if /etc/hostname.<ifname> file exist. Edit /etc/hostname.<ifname> file with the new hostname. If the file does not exist, then create /etc/hostname.<ifname> and add the new hostname.
# ls /etc/host* /etc/hostname.eri0 /etc/hosts
# cat /etc/hostname.eri0 urc2y3pa
Modified /etc/hostname.<ifname>
# cat /etc/hostname.eri0 urc2y1th
Modify SCS server domain name

1. Edit /etc/resolv.conf, modify the domain name set after the key word domain. Old domain name - ca.nortel.com New domain name - us.nortel.com
10
411-5221-309
Standard
06.30 March 10, 2010
221
Old /etc/resolv.conf file:

# cat /etc/resolv.conf domain ca.nortel.com nameserver 192.168.128.21 search internal.nortel.com
Modified /etc/resolv.conf:
# cat /etc/resolv.conf domain us.nortel.com nameserver 192.168.128.21 search internal.nortel.com
Verify the SCS server umask settings

In some cases, the default directory and file permission modes on the SCS server may be set incorrectly. This is usually observed after upgrading the SCS server from Solaris 8 to Solaris 9. This procedure outlines the verification steps as well as steps to update the permissions if necessary. 1. Log in to the SCS server as root user.
10
2. Issue the command umask. The return value must match 022. Here is an example. Note: The leading 0 in the return value is not printed by umask.
# umask 22
3. In the above example, umask returns 022. If the return value does not match 022, permission settings must be modified. Here is an example where the umask return value is 027. The command umask 022 is issued to modify the permissions to 022.
# umask 27 <- umask set incorrectly # umask 022 <- modify umask to 022 # umask 22 <- verify the permissions is modified to 022
GPRS/UMTS
222
4. Verify the file permissions in /opt/patches and /tftpboot/patches. The files must have permissions matching 644 (-rw-r--r--). Verify /opt/patches
# cd /opt/patches # ls -al
Here is an example of a patch:

-rw-r--r-1 207074 800 G60_01911088_ISPMGR.zip 10566 Sep 2 14:24
Verify /tftpboot/patches
# cd /tftpboot/patches # ls -al
Here is an example of a patch:

-rw-r--r-1 root other G60_01911088_ISPMGR_cmc.p1.gz 2097 Sep 2 15:13
Note: If any of the files have different file permissions in /opt/patches or in /tftpboot/patches, use the chmod command to modify the file permissions to match 644.
# cd /opt/patches # chmod 644 * # cd /tftpboot/patches # chmod 644 *
Fixing Solaris error - getexecname() failed
10
During SCS server reboot or when executing commands - ps or swap or any SCSAdmin commands, the error - getexecname() failed could be returned. To fix the error, verify and execute the following steps. 1. Make sure /etc/vfstab has partition listing for the file systems fd and /proc, i.e, partitions fd and /proc must not have a # in the beginning of the line. 2. If fd and /proc partitions are commented out, edit /etc/vfstab and uncomment them, i.e. remove # if its added to the beginning of the entry for fd and /proc.
411-5221-309 Standard 06.30 March 10, 2010
223
3. Make sure the directory /proc exists.

ls /proc
4. If /proc directory exists, skip this step. If /proc does not exist, create a /proc directory and mount the proc file system.
mkdir /proc
Mount the proc file system to /proc.

mount -F proc /proc
5. Reboot the SCS server.

sync; sync; sync; sync init 6
Fixing - unable to eject CDROM from drive
10
In some cases, issuing the command eject cdrom may not eject the CDROM from the drive. In this case, Solaris Volume Manager process will need to be restarted. 1. Log in to the server as root user. 2. Change directory to /etc/init.d
cd /etc/init.d
3. Restart Solaris Volume Manager

# ./volmgt stop # ./volmgt start volume management starting.
Add or Verify SOC key

Here are the steps to verify if a SOC key has been enabled. 4. Log in to the SCS client as device_owner user. 5. From the File menu, click SCS Configuration. 6. Click the SOC Activation tab. 7. To add a new SOC key: Click on Add, then paste the SOC key provided for the feature.
10
GPRS/UMTS
224
Click OK to save the SOC key. Select the SOC key and click Edit. Modify the Activation Status to Enabled. 8. To verify is a SOC key has been activated: The SOC Activation tab provides the list of SOC keys that are currently enabled on the SCS server. 9. To enable a SOC key that was previously disabled: From the SOC Activation tab, select the SOC key with Disabled status. Click Edit. Modify the Activation Status to enabled. Click OK to activate the SOC key.
Verify patch status information

Here are the steps to verify if a patch has been applied or activated. 1. Log in to the SCS client as device_owner user. 2. Click on the Patch icon on the left pane. This will open the Patch Manager panel.
10
3. Click on the Device tab. Select the Region from the left pane. This will list the GGSNs configured in the SCS region. 4. Make a note of the Patch Profile applied to the GGSN. The patch profile applied to the GGSN is called the active patch profile. 5. Click the Profile tab. This lists the patch profiles configured. 6. Select the active patch profile obtained from the previous steps and click Edit. 7. From the Patchable Load: drop down option, select the appropriate load running on the GGSN (example: GGSN 4.1.1 or GGSN 5.0.1). 8. On SCS 5.0.2, the Patch Profile Configuration window has 2 panes, Patch Packages and Patch Rules. An option to search for a specific patch is also available. Paste the name of the patch required to be verified in the Search text field. If the patch profile has the patch added as a patch rule, then the patch rules pane will list the patch. Select the patch and click Edit. If the patch name contains the string ACT, it represents an activatable patch. This lets the user select the patch Directive as Activate and Deactivate.
411-5221-309
Standard
06.30 March 10, 2010
225
For non-activatable patches (GEN patches), the option to modify the patch directive is disabled. Users can verify is the patch exists as a patch rule in the patch profile.
For an ACT patch, verify if the directive is Activate. 9. On SCS 4.1.2, users must manually search the list of patch rules and verify is a patch has been applied or activated.
SCS Periodic Backup setup option
10
SCS 6.0 provides an option to setup the SCS server to perform periodic backup. The periodic backup setup script SCSPeriodicBackup is located in <SCS_ROOT>/bin. Here are the usage information. Determine SCS 6.0 installation directory using:
Change directory to SCS 6.0 installation directory.

cd <SCSHead> cd bin
Example:
cd /opt/shasta/scs6.0 cd bin
Execute the SCS periodic backup setup script:

# ./SCSPeriodicBackup
This script provides the following options: 1) Backup info - Provides information if periodic backup has been enabled or not 2) Monthly backup - Configure for monthly backup 3) Weekly backup - Configure for monthly backup 4) Daily backup - Configure for monthly backup 5) Disable - Disable the configured periodic backup 6) Exit - Exit script
GPRS/UMTS
226
Here is an example to setup periodic weekly backup.

# ./SCSPeriodicBackup *********** SCS PERIODIC BACKUP *************************** * This script is used to periodically backup SCS system. * * + SCS backup should be set at the free slot time. * * + The backup files is saved into indicated folder. * * + In case monthly backup, note that February only has 28 or 29 days.* 1) Backup info 2) Monthly backup 3) Weekly backup 4) Daily backup 5) Disable 6) Exit Please specify your choice [1-6]: 3 ******************** WEEKLY SCS BACKUP ******************** 1) Sunday 2) Monday 3) Tuesday 4) Wednesday 5) Thursday 6) Friday 7) Saturday Please specify week day [1-7]: 1 Please specify <hour number [0-23]> <minute number [0-59]>: 0 0 Please specify backup folder [/opt/shasta/scs6.0/backup]: <-Hit enter to select the default option WARNING: SCS system was weekly backed up on Sunday at 00:00:00 CST. Do you want to replace it with the new setting (y/n)? [n]: y <-Script will prompt if a similar backup was configured earlier SCS system is now weekly backed up on Sunday at 00:00:00 CST.
Execute the script again with option 1 to verify the settings:

# ./SCSPeriodicBackup *********** SCS PERIODIC BACKUP *************************** * This script is used to periodically backup SCS system. * 411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential * * * * * or
227
+ SCS backup should be set at the free slot time. + The backup files is saved into indicated folder. + In case monthly backup, note that February only has 28 29 days.*
1) Backup info 2) Monthly backup 3) Weekly backup 4) Daily backup 5) Disable 6) Exit Please specify your choice [1-6]: 1 SCS system is currently weekly backed up on Sunday at 00:00:00 CST. Backup folder is /opt/shasta/scs6.0/backup.
SCS server crontab will be updated with the entry:

# crontab -l 0 0 * * 0 /opt/shasta/scs6.0/bin/SCSCronBackup #SCS system is now weekly backed up on Sunday at 00:00:00 CST
Resolve SCS server login issue in case of incorrect shell path
10
When editing /etc/passwd, incorrectly setting the csh shell path for root user will result in subsequent login failure for root user. The following steps can be executed to correct the csh shell path. Pre-requisites: Solaris 9 Disk 1 (of 2) Mount point of / partition (disk partition for /) Serial console access to the SCS server or directly connected monitor Knowledge of editing files using vi editor
Steps: 1. Insert the Solaris 9 Disk 1 into the SCS server CDROM. 2. Connect to the SCS server through the serial console or from a directly connected monitor. 3. Access to the Solaris ok prompt:
GPRS/UMTS
228
If a Sun keyboard is available and connected to the server, press the key sequence Stop A If a serial console session is available, then press the key sequence Ctrl] (Ctrl key and ] key), then type the following: send break 4. At the ok prompt, type:
{2} ok boot cdrom -s
5. After the server reboots from the CDROM, at the command prompt, create a directory a. Use pwd to find the exact path.
mkdir a pwd /tmp/root
6. Export the following environment variables in ksh shell.

# ksh # export TERM=vt100
7. Mount the / partition on /tmp/root/a. Here is an example.

# mount -o rw /dev/dsk/c1t1d0s0 /tmp/root/a
8. Change directory to /tmp/root/a/etc and edit the file passwd using vi editor. Modify the entry for root user, set the correct path for csh /usr/bin/csh. Save the changes.
# cd /tmp/root/a/etc # vi passwd
9. After the file modification, verify the content using cat vfstab. Here is an example.
# cat /etc/passwd root:x:0:1:Super-User:/:/usr/bin/csh
10. Change directory to /, then reboot the server.

# cd / # reboot
11. After the server reboots, verify logging into the server as root user.
Swap memory space allocation

1. Log into your SCS workstation as a root level user.
10
2. Determine which partition has available space for creating the additional swap space.
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Example:

# df -k Filesystem /dev/dsk/c1t0d0s1 /proc fd mnttab /dev/dsk/c1t0d0s3 swap /dev/dsk/c1t0d0s2 swap /dev/dsk/c1t1d0s0 home
229
kbytes used avail capacity Mounted on 8065025 6721990 1262385 85% / 0 0 0 0% /proc 0 0 0 0% /dev/fd 0 0 0 0% /etc/mnttab 4032504 57044 3935135 2% /var 5541664 8 5541656 1% /var/run 18145961 12883309 5081193 72% /opt 5546208 4552 5541656 1% /tmp 35003383 29628972 5024378 70% /export/
3. Open a console window. 4. Change to the directory that contains extra disk space. For example, /export/home has space to swap.
# cd /export/home
5. Create a new file using the mkfile command. Note this is an example only. Syntax: mkfile <file size> <filename> # mkfile 705248k swap_more It may take a good deal of time for the system to create this file. 6. Add this file to the swap space, using the swap command. Syntax: swap -a <absolute path to swap file> # swap -a /export/home/swap_more 7. Edit the /etc/vfstab file so that the server allocates this file as swap space after a server reboot. Add a line to the file using vi or text editor to allocate the file you just created as swap space. Example entry:
/export/home/swap_more - - swap - no -
8. Reboot the workstation and log back in as root user. 9. Verify the swap space was added correctly by using the swap -l command. # swap -l
swapfile dev swaplo blocks free
GPRS/UMTS
230

/dev/dsk/c0t0d0s1 32,1 /export/home/swap_more - 16

16 21015362101536 1410480 1410480
SCS and iPlanet auto startup scripts

SCS and iPlanet processes can be automatically started during a server reboot. Here are the steps to enable the auto startup scripts. 1. Determine SCS 6.0 installation directory using:
10
2. Change directory to SCS 6.0 installation directory.

cd <SCSHead> cd bin
Example:
cd /opt/shasta/scs6.0 cd bin
3. Script SCSAutoStart can be used to enable or disable the auto startup scripts. Here is the usage:
# ./SCSAutoStart Usage: SCSAutoStart <enable/disable>
4. To enable SCS and iPlanet auto startup scripts, execute:

# ./SCSAutoStart enable
Example:
# ./SCSAutoStart enable SCS auto startup is enable
In case the auto startup scripts need to be disabled, execute:

# ./SCSAutoStart disable
Example:
# ./SCSAutoStart disable SCS auto startup is disable
411-5221-309
Standard
06.30 March 10, 2010
231
SCS data collection during SCS server migration

The following SCS parameters must be collected from the old server.
10
These parameters will need to be reused during the new installation of SCS software on the new server. One exception is the LDAP Root point. The uid in LDAPRoot must not match between the old and new SCS server. After a database restore on the new SCS server, the LDAPRoot uid is reverted back to match the old SCS server. Here are the SCS parameters. 5. Determine <SCS_ROOT>
# cd /etc/shasta # more scs.config | grep SCSHead
Example:
SCSHead=/opt/shasta/scs <SCS_ROOT> = SCSHead = /opt/shasta/scs
6. Determine <LDAP_ROOT>
# more scs.config | grep LDAPPath
Example:
LDAPPath=/opt/shasta/ldap <LDAP_ROOT> = LDAPPath = /opt/shasta/ldap
7. Determine SCS Region ID

# more .scs.config | grep RegionId
Example:
# more .scs.config | grep RegionId RegionId=1
8. Determine LDAP/ iPlanet server port

# more scs.config | grep LDAPServerPort
Example:
232
Basic SCS system administration # more scs.config | grep LDAPServerPort LDAPServerPort=389
9. Determine the LDAP Root point.

# cat .scs.config | grep LDAPRoot LDAPRoot="uid=admin,ou=People,o=us.nortel.com"
Example:
# cat .scs.config | grep LDAPRoot LDAPRoot="uid=admin,ou=People,o=us.nortel.com"
Note: The uid in LDAPRoot must not match between the old and new SCS server. After a database restore on the new SCS server, the LDAPRoot uid is reverted back to match the old SCS server.
411-5221-309
Standard
06.30 March 10, 2010
Database backup and restore procedures 233

Note: The backup and restore (database and Full system) is only supported for SCS Servers with LDAP, Domain, and Region running on the same physical machine. WARNING: After a database restore, a restart of the SCS server processes and a GGSN resync is required. Plan to resync the GGSN during the next maintenance window.
SCS backup/ restore options

There are 3 options of performing a SCS backup and restore. Option 1: SCS backup/ restore using tar. Please refer to Option 1: SCS backup/ restore using tar on page 233
11
Option 2: SCS backup/ restore using SCSAdmin. Please refer to Option 2: SCS backup using SCSAdmin on page 242 Option 3: For performing Tape backup, please refer to Backup and Restore Procedures for SCS with a Tape Drive on page 384
Option 1: SCS backup/ restore using tar

The tar backup option can be used to backup the entire SCS and LDAP/ iPlanet installation directories as well as the patch directories. It is recomended to FTP the backup to a different server.
11
A restore of the tar backup will overwrite the directories of the same name. After the restore, restart of the SCS server processes is required as well as a GGSN resync. Note: The size of the tar file can be large. (The size varies with the configuration that is present) Before taking the backup, make sure there is enough space in the disk partition where the backup is being taken. Also, it is advisable to compress thebackup.
Stop SCS and LDAP server processes before starting the backup
1. Determine the SCS installation directory, disable LDAPWatch:
# cat /etc/shasta/scs.config | grep SCSHead # cd <Path returned for SCSHead>
11
GPRS/UMTS
234
Database backup and restore procedures # cd bin #./LDAPWatch-disable
2. Check SCS version

# cat version
3. Stop SCS server processes:

#./SCSAdmin stop #./SCSAdmin status //verify all the processes are stopped
4. Stop LDAP/ iPlanet directory server process. a. Determine the LDAP/ iPlanet installation directory.
# cat /etc/shasta/scs.config | grep LDAPPath # cd <Path returned for LDAPPath> # cat /etc/shasta/scs.config | grep LDAPServerName # cd <Path returned for LDAPServerName>
b. Stop LDAP/ iPlanet directory server instance:

#./stop-slapd
c. Stop LDAP/ iPlanet admin server process

# cd ../ # ./stop-admin
d. Verify the LDAP/ iPlanet instance and admin process are stopped.
# ps -aef | grep -v grep | grep slapd # ps -aef | grep -v grep | grep admin
Perform a tar backup
11
1. Verify there is sufficient disk space on the SCS server. Issue the command df -k. This command will return the disk space available in kilo bytes.
# df -k For servers on Solaris 9, df -kh option can be used. This will display the file size in easy readable form. 411-5221-309 Standard 06.30 March 10, 2010
The example below shows 16 GB disk space available and around 4.7 GB disk space already utilized. It is a safe estimate to have around 4 GB free space for storing the backup. This is not a hard limit either as it depends on the amount of files present in SCS installation and LDAP or iPlanet installation directories. If you do not have enough disk space on a particular partition, choose another one. df -k will give you the details of the current file systems mounted and space available.
# df -k /opt
Filesystem /dev/dsk/c0t0d0s3 kbytes used avail capacity 21182089 4679735 16290534 23% Mounted on /opt
2. Determine the SCS installation directory.

3. Determine the LDAP/ iPlanet installation directories.

4. Create a backup directory in a partition that has sufficient disk space. Here is an example.
# mkdir /opt/tarbackup
5. Change directory to the newly created backup directory.

# cd /opt/tarbackup
6. Perform a backup. Here, the SCS and LDAP/ iPlanet installation directories are backed up first, next the GGSN patch repositories directories are backed up separately. To perform a backup for SCS 6.0:
# tar cpf backup_SCS<servername>_SCS<version>_<data>.tar <Directory Path returned for SCSHead> <Directory Path returned for LDAPPath> /etc/shasta/scs.config
where <servername> is the SCS server name. This can be useful to identify the backup, <version> is the SCS version, for example 6.0. Here is an example:
# tar cpf backup_SCS619_6.0_06092008.tar /opt/shasta/scs6.0 /opt/shasta/iplanet
GPRS/UMTS
236
Note: While executing the tar command, please remove the tags < > before the directory path. Note: While writing the tar file, if there are any links etc, these files will not be added to the tar file. There might some warning messages like, the xx file is not dumped. Ignore these messages. To perform the backup for SCS 4.1.2 or 5.0.2:
# tar cpf backup_SCS<servername>_SCS<version>_<data>.tar <Directory Path returned for SCSHead> <Directory Path returned for LDAPPath> /etc/shasta/scs.config /etc/init.d/ SCSInit /etc/init.d/LDAPInit
where <servername> is the SCS server name. This can be useful to identify the backup, <version> is the SCS version, for example one of 4.12 or 5.0.2. 7. Perform a backup of the GGSN patch repositories directories.
# tar cpf patches_<version>_<date>.tar /opt/patches / tftpboot/patches
where <version> is the GGSN version. Here is an example.

# tar cpf patches_6.0_06092008.tar /opt/patches /tftpboot/ patches
8. Make sure the files are present in the directory and contains all the required files.
# tar -tvf <SCS_backup_file>.tar # tar -tvf <patches>.tar
This will display all the files that the tar file contained. Here is an example:
# tar -tvf backup_SCS619_6.0_06092008.tar # tar -tvf patches_6.0_06092008.tar
9. Compress the SCS tar backup to save disk space.

# compress <SCS_backup_file>.tar
On compressing the tar backup, the tar backup file is appended with a .Z extension. Here is an example.
411-5221-309
Standard
06.30 March 10, 2010
# compress SCS619_6.0_06092008.tar # ls SCS619_6.0_06092008.tar* SCS619_6.0_06092008.tar.Z
Restart LDAP (or iPlanet) and SCS processes

10. Start LDAP/ iPlanet directory server and admin processes a. Determine the LDAP/ iPlanet installation directory
# cat /etc/shasta/scs.config | grep LDAPPath # cd <Path returned for LDAPPath> # cat /etc/shasta/scs.config | grep LDAPServerName # cd <Path returned for LDAPServerName> # ./start-slapd
11
b. Start LDAP admin server process

# cd ../ #./start-admin

# cat /etc/shasta/scs.config | grep SCSHead # cd <Path returned for SCSHead> # cd bin
12. Enable LDAPWatch:

#./LDAPWatch-enable
13. Start SCS server processes:

#./SCSAdmin start #./SCSAdmin status //verify all the processes are running
If you are referring to the above tar backup option during an upgrade, return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162 or
238
Upgrade SCS 5.0.2 to SCS 6.0 on same server on page 166
Restore Procedure for the tar backup

Use the procedure in this section if you would like to restore a copy of the backed-up tar files.
11
Make sure the tar file backed up in the previous section is present in the /opt/ tarbackup directory. This operation performs a rollback to the original SCS Server. WARNING: A GGSN resync is required after the restore procedure. Please plan the resync in a maintenance window. 1. Determine the correct backup tar file to be restored from the backup directory. Here is an example:
# cd /opt/tarbackup # ls SCS619_6.0_06092008.tar* SCS619_6.0_06092008.tar.Z
2. Determine the SCS installation directory, disable LDAPWatch:

# cat /etc/shasta/scs.config | grep SCSHead # cd <Path returned for SCSHead> # cd bin # ./LDAPWatch-disable
3. Check SCS version.

# cat version
4. Stop SCS server processes:

#./SCSAdmin stop #./SCSAdmin status //verify all the processes are stopped
5. Stop LDAP/ iPlanet directory server process. a. Determine the LDAP/ iPlanet installation directory.
# cat /etc/shasta/scs.config | grep LDAPPath # cd <Path returned for LDAPPath>
411-5221-309
Standard
06.30 March 10, 2010
# cat /etc/shasta/scs.config | grep LDAPServerName # cd <Path returned for LDAPServerName>
b. Stop LDAP/ iPlanet directory server instance:

#./stop-slapd
c. Stop LDAP/ iPlanet admin server process

# cd ../ # ./stop-admin
d. Verify the LDAP/ iPlanet instance and admin process are stopped.
# ps -aef | grep -v grep | grep slapd # ps -aef | grep -v grep | grep admin
Restore SCS 4.1.2, SCS 5.0.2 and SCS 6.0

Note: Before deleting the directories, make sure you have the right backup files to restore.
11
Note: Log in to the SCS client as device_owner user and make a note of the GGSN status (insync, out-of-sync, insync with session errors). This status can be compared on completion of the resync procedure after the restore. 1. If the server has sufficient disk space, move the current SCS and LDAP/ iPlanet installation directories to temp directories. If sufficient disk space is not available, delete the SCS and LDAP/ iPlanet installation directories. Here is an example if sufficient disk space is available.
# df -k /opt
Filesystem /dev/dsk/c0t0d0s7 kbytes used avail capacity Mounted on 53534079 14984736 38014003 29% /opt
# cat /etc/shasta/scs.config | grep SCSHead SCSHead=/opt/shasta/scs6.0 # cat /etc/shasta/scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet # cd /opt/shasta
GPRS/UMTS
240
Database backup and restore procedures # mv scs6.0 scs6.0_temp # mv iplanet iplanet_temp
Here is an example where sufficient disk space is not available which requires deleting the current SCS and LDAP/ iPlanet installation directories.
# cat /etc/shasta/scs.config | grep SCSHead SCSHead=/opt/shasta/scs6.0 # cat /etc/shasta/scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet # rm -rf <Path returned for SCSHead> # rm -rf <Path returned for LDAPServerName>
Note: Make sure the backup file created in the previous section is not deleted with this command. 2. Change directories
# cd /opt/tarbackup
3. Uncompress the backup.

# uncompress <SCS_backup_file>.tar.Z
4. Restore the backup.

# tar xpf <SCS_backup_file>.tar
5. Optional: In case, the GGSN patch repository directory needs to be restored: tar the current GGSN patch repository directories to the backup directory. Here is an example.
# cd /opt/tarbackup # tar cpf patches_6.0_06092008-1.tar /opt/patches / tftpboot/patches # tar -tvf patches_6.0_06092008-1.tar
Untar the previously backed up GGSN patch directories.

# tar -tvf <patches>.tar
6. Start LDAP/ iPlanet directory server and admin processes
411-5221-309
Standard
06.30 March 10, 2010
a. Determine the LDAP/ iPlanet installation directory

# cat /etc/shasta/scs.config | grep LDAPPath # cd <Path returned for LDAPPath> # cat /etc/shasta/scs.config | grep LDAPServerName # cd <Path returned for LDAPServerName> # ./start-slapd
b. Start LDAP admin server process

# cd ../ #./start-admin

# cat /etc/shasta/scs.config | grep SCSHead # cd <Path returned for SCSHead> # cd bin
8. Enable LDAPWatch:
#./LDAPWatch-enable
9. Start SCS server processes:

#./SCSAdmin start #./SCSAdmin status //verify all the processes are running
10. Please plan a maintenance window. Perform a GGSN resync. Verify the GGSN is insync after the reboot. If the GGSN does not come insync, please contact Nortel support. 11. Log in to the SCS client as device_owner user. Add a dummy RADIUS Profile from Access Properties Manager. Add a dummy server IP and save the changes. Log in to the GGSN and issue the command:
ggsn # show radius profile isp= default
12. Verify the RADIUS Profile has been added to the GGSN. 13. From the SCS client, delete the RADIUS Profile. Verify the profile has been deleted from the GGSN.
GPRS/UMTS
242
Option 2: SCS backup using SCSAdmin Recommended GGSN pre-backup modification Check the GGSNs in the SCS Client GUI BEFORE an upgrade or backup of the SCS software or any restart of the SCS processes on the SCS server. 1. Log into the SCS Client GUI. 2. On the Device manager panel, right click on the device and select 'configure', then 'device'. 3. On the 'Device' tabbed panel, if the Up Since time is greater than 7 days, then perform some minor configuration change (for instance, add a service policy and then delete it). Note: The Up Since time indicates the time when the GGSN was last rebooted. This is not an indication of the last configuration change made to the GGSN. There is no visible indication of when the last configuration change was made. Performing this step guarantees the configuration time stamp is not past the threshold by resetting it. 4. Now the SCS server processes can be stopped/started/restarted without affecting the GGSN state. Database backup procedure for SCS On an SCS server running the GGSNS4.0.1/GGSNS4.1.x/ GGSNS5.0/ GGSNS5.0.1 version of SCS software, the backup of both Solid and LDAP databases can be executed with the following command (log in as root): Note: Using the system backup option creates a backup file for LDAP in a format that is not exportable to another server. So this option cannot be used to migrate the LDAP database to a new server. For this, use the steps in Backup LDAP database on page 185.
# cd <SCS_ROOT>/bin # ./SCSAdmin backup system
Starting DomainAndRegion Backups Waiting for servers to finish ....server areaId 0 displayBackupStatus -status: SUCCESS displayBACKUP Status of server: 0 status: SUCCESS Server[0] BACKUP succeeded BACKUP of system SUCCESSFUL backupPath : /opt/shasta/scs/backup timeStamp : 20030328043940 Enable new Clients to login Enabled Clients to provision No match It is a good back up file.
Note: The optional <time> parameter causes the backup to wait for the number of seconds before beginning the backup. The default is 120 seconds. A warning is generated to any connected SCS Clients. All SCS Client provisioning changes are blocked once the backup begins.
411-5221-309 Standard 06.30 March 10, 2010
By default, the backup files are placed in the <SCS_ROOT>/backup directory. This is the default directory designated during the upgrade/install to the SCS software. The actual directory of the backup directory is found in file /etc/ shasta/scs.config as the value of SCSBackup:
SCSBackup=<absoltue path of backup directory>
The backup will create a new directory in the backup directory with the current time stamp as the directory name. In the time stamp directory will be two directories, one for Solid and one for LDAP. In the Solid directory is a tarred and zipped file of the Solid backup files. In the LDAP directory is a tarred and zipped file of the LDAP backup file: Note: For GGSN 6.0, the directory name is appended with the version name too. For example, instead of just the time stamp, the directory name will be GGSN 5.0_20050206050435
# pwd /export/home/shasta/scs/backup/20030506050435 # ls DomainRegionSolidDB # ls -al * DomainRegionSolidDB: total 1092 drwxr-xr-x 2 root drwxr-xr-x 5 root -rw-r--r-1 root DomainBackup.tar.Z
LDAPDB
other other other
512 May 512 May 547976 May
7 16:22 . 6 17:06 .. 6 17:06
The above file will contain both the Domain and Region Server database backup.
LDAPDB: total 1000 drwxr-xr-x 2 root drwxr-xr-x 5 root -rw-rw-rw1 root .slapd.name -rw-rw-rw1 root .slapd.path -rw-rw-rw1 root LdapBackup.tar.Z
other other other other other
512 May 512 May 15 May 45 May 495815 May
6 17:06 . 6 17:06 .. 6 17:04 6 17:04 6 17:04
Note: The backup files generated from these procedures should be stored on an alternate server in case the active server crashes.
GPRS/UMTS
244
After completion of the Database backup procedure, please return to the referring section instead of continuing on to the Database restore procedure (unless a database restore is needed). FTP the backup to a remote server 1. Determine the location of the SCS system backup directory.
# cat /etc/shasta/scs.config | grep SCSBackup
Here is an example.
# cat /etc/shasta/scs.config | grep SCSBackup SCSBackup=/opt/shasta/scs502/backup
2. Change directory to <SCSBackup>. Determine the latest backup directory.

# cd <SCSBackup> # ls -lrt <SCSBackup>
3. tar the backup directory.

# tar cvf <filename.tar> <backup directory name>
4. Here is an example.
tar cvf GGSNS5.0.2_SCS5.0_14_20081114142339.tar GGSNS5.0.2_SCS5.0_14_20081114142339
5. FTP the backup tar file to a remote server.
After completion of the Database backup procedure, please return to the referring section instead of continuing on to the Database restore procedure (unless a database restore is needed).
Database restore procedure On an SCS server running the GGSNS4.0 or later version of SCS software, the restore of both Solid and LDAP databases can be executed with the following command (log in as root):
# cd <SCS_ROOT>/bin # ./SCSAdmin restore system <time>
Note: The restore procedure automatically closes the SCS Client.
411-5221-309
Standard
06.30 March 10, 2010
The <time> parameter causes the restore to wait for the number of seconds before beginning the restore. A warning is generated to any connected SCS Clients. All SCS Client provisioning changes are blocked once the restore begins.
The backup files are read from the backup directory. The location of the backup directory is found in file /etc/shasta/scs.config as the value of SCSBackup:
SCSBackup=<absoltue path of backup directory>
The restore will prompt the user to select the version of the backup files to be restored by listing the time stamp directories from the backup directory. Note: For GGSN 6.0, the directory name is appended with the version name too. For example, instead of just the time stamp, the directory name will be GGSN 5.0_20050206050435. The list here will show the version also for 5.0 backup only.
# ./SCSAdmin restore system 100 List available backup(s): 1. /opt/shasta/scs/backup/20030314020520 2. /opt/shasta/scs/backup/20030314021144 3. /opt/shasta/scs/backup/20030314022416 4. /opt/shasta/scs/backup/20030314031608 5. /opt/shasta/scs/backup/20030314104327 Please choose a backup from the above list: [1..5] (Enter Q(q) to exit)
Select the desired backup version and the restore process will restore both the LDAP and Solid databases. The default time for the wait before the restore starts is 120 seconds. After the restore is done, the SCS Processes have to be restarted
After restarting the SCS Processes, all the Devices have to be resynched.
Option 3: Perform Tape Backup Restore Procedure For performing Tape backup, please refer to Backup and Restore Procedures for SCS with a Tape Drive on page 384
GPRS/UMTS
246

This section details the following SCS server upgrade paths: SCS 4.1.2 to SCS 6.0 - Upgrade SCS 4.1.2 to SCS 6.0 on page 246
12
SCS 5.0.2 to SCS 6.0 - Upgrade GGSN SCS from 5.0.2 to 6.0 on page 274
Upgrade SCS 4.1.2 to SCS 6.0
12
The following steps provide the user with a high level overview of the SCS 6.0 software upgrade. The detailed steps are explained in SCS 4.1.2 to SCS 6.0 upgrade details on page 247 Step 1: Make sure SCS 4.1.2 and LDAP 4.16 server processes are running Step 2: Create a new directory for SCS 6.0 server installation. This is <SCS6.0_ROOT> Example: <SCS6.0_ROOT> = /opt/shasta/scs6.0 Step 3: Copy SCS 6.0 server software scsserver.tar.Z file and iPlanet directory server tar file from the SCS installation CD or ESD to <SCS6.0_ROOT> Step 4: Uncompress and untar scsserver.tar.Z file in <SCS6.0_ROOT> Step 5: Disable SCS 4.1.2 provisioning Step 6: Perform a SOLID database backup Step 7: Execute upgrade script - rollingSCS.sh Step 8: Verify SOLID database integrity Step 9: Execute upgrade script - setup.sh Step 10: Verify SCS and iPlanet upgrade logs
411-5221-309
Standard
06.30 March 10, 2010
247
Convention: <SCS_ROOT> = GGSN SCS 4.1.2 installation directory <SCS6.0_ROOT> = GGSN SCS 6.0 installation directory
Example:
<SCS6.0_ROOT> = /opt/shasta/scs6.0 <LDAP_ROOT> = LDAP 4.16 installation directory

Example:
<LDAP_ROOT> = /opt/shasta/ldap <IPLANET_ROOT> = iPlanet 5.1 installation directory

Example:
<IPLANET_ROOT> = /opt/shasta/iplanet Make a note of the above directory structures as they will be required during the upgrade process.
SCS 4.1.2 to SCS 6.0 upgrade details 1. Login as root onto the SCS Server 2. Make sure you are in C - shell.
#echo $SHELL
This will show the present shell. If the default shell for root is not set as csh, then modify /etc/passwd and put in /usr/bin/csh instead of the set shell. Example: If the default shell is set to sh, /etc/passwd will look like:
# more /etc/passwd root:x:0:1:Super-User:/:/usr/bin/sh
Find the location of csh:

# which csh /usr/bin/csh GPRS/UMTS Upgrade Manual GGSN6.0
248
Modify /etc/passwd to:

# more /etc/passwd root:x:0:1:Super-User:/:/usr/bin/csh
After modifying /etc/passwd, login to the server as root from another telnet window. This way, if there was some error modifying /etc/passwd, and you are unable to log back in to the server, you are still logged into the server in the original window that was used to modify the file. Make sure to correct any errors in /etc/passwd in case of a login failure. Other system settings needed are: File /etc/nsswitch.conf contains: hosts: file dns Example: hosts:file dns File /etc/resolv.conf contains: domain <domain name> Example: domain my.company.com File /etc/hosts contains: <machines static ip address> <hostname> <fqdn> loghost Example: 99.100.100.100 scshost scshost.my.company.com loghost To view the system domain name: # domainname <-this shows domainname To view the system host name: # hostname <- this show host name 3. Verify LDAP 4.16 directory server and admin servers are running. If the process is not running, start the processes.
Example:
Determine <LDAP_ROOT>
# cd /etc/shasta # more scs.config | grep LDAPPath Example: LDAPPath=/opt/shasta/ldap <LDAP_ROOT> = LDAPPath = /opt/shasta/ldap
411-5221-309
Standard
06.30 March 10, 2010
249
Check LDAP server processes is running

# ps -aef | grep slapd | grep -v grep nobody 611 1 0 20:04:04 ? 0:01 ./ns-slapd -f / opt/shasta/ldap/slapd-urc2y3pa/config/slapd.conf -i /opt/ shasta/
Check LDAP admin process is running

# ps -aef | grep admin | grep -v grep root 310 1 0 Jan 20 ? 0:03 ./ns-admin -d / opt/shasta/ldap/admin-serv/config
If the above ps -aef command does not return a result, start the LDAP directory server and admin server processes. To start LDAP directory server process:
# cd <LDAP_ROOT> Example: # cd /opt/shasta/ldap # slapd-<hostname>/start-slapd (here <hostname> represents the server hostname you are working on)
To start LDAP admin server process:

#./start-admin
Execute the above ps -aef command and verify LDAP directory server and admin server processes are running. If the processes dont start, contact your next level of support before proceeding. 4. Verify the status of all the SCS 4.1.2 processes. Execute the following from the <SCS_ROOT>/bin directory. If any of the processes are not running, try restarting the processes. In the snapshot shown below, the current SCS version is 4.1.1 and all processes are running.
# cd /etc/shasta # more scs.config | grep SCSHead Example: SCSHead=/opt/shasta/scs <SCS_ROOT> = SCSHead = /opt/shasta/scs
GPRS/UMTS
250
SCS Software Upgrade # cd <SCS_ROOT>/bin Example: # cd /opt/shasta/scs/bin # ./SCSAdmin status
Running Solid Database Server since Feb_14 (pid=7287) Running SCS Daemon since Feb_14 (pid=7305) Running SCS Domain Server since Feb_14 (pid=7320) Running SNMP Proxy since Feb_14 (pid=7503) Running SCS Region Server since Feb_14 (pid=7524) Running SCS Monitor Server since Feb_14 (pid=7546) Running SCS Trap Daemon since Feb_14 (pid=7571) Running SCS Pull Server since Feb_14 (pid=7637) Running SCS Log Server since Feb_14 (pid=7673) Running SCS CORBA Server since Feb_14 (pid=7509) SSL is not enabled on present servers All SCS server processes are running. Version SCS GGSNS<version>_SCS<version>(xx)
Note: If customer is not using Corba, you will not see the Corba Server running. If any process is not running, restart the SCS server processes. To restart SCS server processes:
# cd <SCS_ROOT>/bin #./SCSAdmin restart
If any of the processes are not running, contact your next level of support before proceeding. 5. Create a directory for GGSN SCS 6.0 software. This is represented as <SCS6.0_ROOT>. Example, create a directory scs6.0
Example:
# cd /opt/shasta # mkdir scs6.0 # cd scs6.0
Next, retrieve the SCS 6.0 software from the CD or ESD. The following steps explain the steps copy the software from a CD.
411-5221-309
Standard
06.30 March 10, 2010
251
6. Insert the SCS 6.0 software CD. Verify CDROM mount point on the server using df -k. Copy the SCS Server software (scsserver.tar.Z) on the CD to the <SCS6.0_ROOT> directory.
# df -k #cp /cdrom/ggsn0060/Solaris/scsserver.tar.Z <SCS6.0_ROOT>
Example:
# df -k /vol/dev/dsk/c0t2d0/ggsn0060 407692 407692 0 100%
/cdrom/ggsn0060
# cp /cdrom/ggsn0060/Solaris/scsserver.tar.Z /opt/shasta/scs6.0
7. Copy the iPlanet Directory Server 5.1 software (directory-5[1].1sp3us.sparc-sun-solaris2.8.tar) on the CD to the <SCS6.0_ROOT> directory.
Example:
# cp /cdrom/ggsn0060/Solaris/directory-5*.tar /opt/shasta/scs6.0
8. Uncompress the SCS Server software, in the <SCS6.0_ROOT> directory # uncompress scsserver.tar.Z 9. Untar the SCS server software into the <SCS6.0_ROOT> directory.
# tar -xvf scsserver.tar
10. Copy the SCS Corba server software (scs_corba_server.tar.Z) on the CD or ESD to the <SCS6.0_ROOT> directory. Note, SCS Corba server software can be copied from the SCS Corba server application CD or ESD (GCOR0060). Note: This step is only required if the customer is using Corba Server. Uncompress the SCS Corba file, but DO NOT UNTAR THE CORBA TAR FILE.
# cp /cdrom/cdrom0/Solaris/scs_corba_server.tar.Z <SCS6.0_ROOT> # uncompress scs_corba_server.tar.Z
Note: 1GB of free space in the root directory is recommended. 11. Verify server port 33611 is not in use by the server prior to the upgrade.
# netstat -na | grep -v grep | grep 33611
GPRS/UMTS
252
If netstat returns a port, then make sure all other iPlanet admin processes are stopped. Proceed to the next section Disable SCS 4.1.2 provisioning on page 252.
Disable SCS 4.1.2 provisioning Note: This step is mandatory. If this step is skipped, GGSNs will go Out of Sync after the SCS 6.0 upgrade. 12. Disable SCS 4.1.2 provisioning. a. Determine <SCS_ROOT>
# cat /etc/shasta/scs.config | grep SCSHead Example: # cat /etc/shasta/scs.config | grep SCSHead <SCS_ROOT> = SCSHead=/opt/shasta/scs
b. Disable SCS provisioning

# cd <SCS_ROOT>/bin # ./SCSAdmin disableProvisioning
Example: # cd /opt/shasta/scs/bin # ./SCSAdmin disableProvisioning
From this point the GGSNs are not under management control but the GGSN can still handle traffic.
Proceed to Perform a SOLID database backup on page 253.
411-5221-309
Standard
06.30 March 10, 2010
253
Perform a SOLID database backup 13. Make a backup copy of SCS 4.1.2 SOLID database.
# ./SCSAdmin backup solidDB
This will backup SCS SOLID database to <SCS_ROOT>/opt/solidSolaris/database/backup
Proceed to Executing rollingSCS.sh procedure on page 253.
Executing rollingSCS.sh procedure 14. Run the rollingSCS.sh and follow the prompts to setup your rolling SCS directory and duplicate LDAP directory server instance.
# cd <SCS6.0_ROOT> #./rollingSCS.sh
Here is a sample of the rollingSCS.sh script execution for SCS 4.1.2 to SCS 6.0.
# cd /opt/shasta/scs6.0
zrc2s0u8# ./rollingSCS.sh This script lets you upgrade without impacting the current SCS servers ================================================================= The following parameters are automatically detected ================================================================= Directory where current SCS servers are running : /opt/shasta/server SCS will be upgraded in the following directory /opt/shasta/scs6.0 :
The root directory for current Netscape Directory Server : /opt/shasta/ldap Machine name zrc2s0u8 Domain name us.nortel.com IP address 47.104.6.14 : : :
GPRS/UMTS
254

New instance name zrc2s0u81 New instance port 390 New LDAP Root DN Password dmanager

: : :
The following Netscape Directory Servers are currently installed on your machine: (1) /opt/shasta/ldap/slapd-zrc2s0u8 The Netscape Directory Server directory to be exported : 1 Root point to be exported : o=us.nortel.com ================================================================= Do you want to change the parameters suggested above (Y/N)? [N]: <- Type Y to proceed Now we will export data from the root point o=us.nortel.com at server /opt/shasta/ldap/slapd-zrc2s0u8 then update and import them to the server /opt/shasta/ldap/slapdzrc2s0u81 Do you want to continue (Y/N)? [Y]: <- Type Y to proceed Setting up the directory for the upgraded SCS Servers... slapd-zrc2s0u8 ======================================================= Rolling upgrade for Netscape Directory Server begins! ======================================================= Creating new instance... Creating new instance completed Exporting the data, please wait...... Exporting data completed. /opt/shasta/ldap/slapd-zrc2s0u81 is being shutdown... Netscape Directory Server is shutdown. Reset the look through limit and size limit of the new instance server.... Schema update, please wait... Creating indexes for Netscape Directory Server Creating index shastaId OK Creating index shastaType OK Creating index shastaContainerId OK
411-5221-309
Standard
06.30 March 10, 2010

Creating index shastaContainerType OK Creating index ntlTemplateType OK Creating index ntlIpdemuxTmplRefPI OK Creating index ntlShastaSGroupRefPI OK Creating index ntlShastaConnectionRefPI OK Creating index ntlShastaDeviceRefPI OK Creating index ntlShastaCardRefPI OK Creating index ntlShastaPortRefPI OK Creating index ntlIpdemuxRefPI OK
255
Creating index ntlBgpIncomingRoutePolicyRefPI OK Creating index ntlBgpOutgoingRoutePolicyRefPI OK Creating index ntlTunnelSetRefPI OK Creating index ntlVPNRefPI OK Creating index ntlBridgeGroupRefPI OK Creating index userid OK /opt/shasta/ldap/slapd-zrc2s0u81 is being shutdown for importing data... Server is still running, please wait..... /opt/shasta/ldap/slapd-zrc2s0u81 is shutdown Importing the data, please wait..... Importing data completed. /opt/shasta/ldap/slapd-zrc2s0u81 is starting... /opt/shasta/ldap/slapd-zrc2s0u81 is restarted. We will now backup your primary directory server, please wait... Back up completed We will now backup your new directory server, please wait... Back up the new server completed The rolling upgrade of your LDAP directory server is completed.
GPRS/UMTS
256
You can find the primary server backup at /opt/shasta/ldap/slapdzrc2s0u8/bak/afterRollingUpgrade/ You can find the new server backup at /opt/shasta/ldap/slapdzrc2s0u81/bak/afterRollingUpgrade/ Please see the file /opt/shasta/scs6.0/rollingUpgradeLdap.log for installation details 390 The .inputparms_rolling.scs has been updated
End of ./rollingSCS.sh for SCS 6.0 Upgrade capture
Note: The script rollingSCS.sh validates the SCS server configuration and populates the file .inputparms_rolling.scs. The parameters set in this file will be used by the upgrade script setup.sh for performing the upgrade.
Proceed to Verify SOLID database integrity on page 257
411-5221-309
Standard
06.30 March 10, 2010
257
Verify SOLID database integrity 15. Execute the SOLID database integrity check and make sure there are no errors. i. Make sure the current working directory is <SCS6.0_ROOT>
# pwd
ii. Execute SOLID database integrity check

# <SCS6.0_ROOT>/opt/solidSolaris/bin/solid -x testindex -c <SCS6.0_ROOT>/opt/solidSolaris/database/default
Here is an example command:

# /opt/shasta/scs6.0/opt/solidSolaris/bin/solid -x testindex -c /opt/shasta/scs6.0/opt/solidSolaris/database/default
Here is an example capture:

Testing the database index. Warning! Starting roll-forward recovery, please wait ... Warning! Recovery of 1 transactions successfully completed -------------------Mon Nov 12 02:48:51 2007 Bonsai tree: Key id = 1091 Clustering key Bonsai tree is ok. Storage tree: Key id = 191 Clustering key Key id = 193 Key id = 291 Clustering key ... ... Storage tree is ok. Database index has been tested successfully. Database index is ok.
Important Note: If there are no errors, then proceed to the next section Execute SCS Upgrade script - setup.sh on page 258 If the above command returns an error, then SCS 4.1.2 SOLID database backup must be manually copied into <SCS6.0_ROOT>/opt/solidSolaris/database/default.
GPRS/UMTS
258
iii. Copy 4.1.2 SOLID database files into <SCS6.0_ROOT>/opt/solidSolaris/database/default

# cp <SCS_ROOT>/opt/solidSolaris/database/backup/* <SCS6.0_ROOT>/opt/solidSolaris/database/default
Example:
# cp /opt/shasta/scs/opt/solidSolaris/database/backup/* /opt/shasta/scs6.0/opt/solidSolaris/database/default
iv. Execute SOLID database integrity check again

# <SCS6.0_ROOT>/opt/solidSolaris/bin/solid -x testindex -c <SCS6.0_ROOT>/opt/solidSolaris/database/default
Here is an example:
# /opt/shasta/scs6.0/opt/solidSolaris/bin/solid -x testindex -c / opt/shasta/scs6.0/opt/solidSolaris/database/default
If there were any errors in the first integrity check, it should not be seen in the second integrity check.
Proceed to Execute SCS Upgrade script - setup.sh on page 258
Execute SCS Upgrade script - setup.sh 16. Upgrade the SCS Server by running setup.sh upgrade script. Change to the directory where the SCS 6.0 server software file was un-tarred. Run the setup.sh script to upgrade the SCS server software. iPlanet schema files will be updated by the setup.sh script. Check for the message LDAP schema files updated successfully during the execution of the script. If the automatic update is not successful, the script will prompt the user that the schema file update failed.
# cd <SCS6.0_ROOT>/bin # ./setup.sh
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Example: # cd /opt/shasta/scs6.0 #./setup.sh
259
Note: When prompted to choose an option pick (U) Upgrade the current SCS Server, and choose the type of upgrade (r - rolling upgrade). The script reads the file .inputparms_rolling.scs, validates the input parameters and displays the parameters to the user. The user must then check the parameters once again, and continue the upgrade by answering y when prompted. In most cases the displayed parameters can be accepted. In case any of the parameters needs to be modified, answer n. Then use vi editor to modify the file .inputparms_rolling.scs from the path displayed in the confirmation message. Save the changes and rerun setup.sh.
Example: Please check the input parameters and confirm If the input is not right, quit by answering n Change the /opt/shasta/scs6.0/.inputparms_rolling.scs and restart the script if you answer n
Here is a sample upgrade capture for SCS 4.1.2 to SCS 6.0 upgrade.
# ./setup.sh 5.9 is a supported Solaris version Logged in as User root Silent procedure is selected /opt/shasta/scs6.0/install/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled This program will install Nortel Service Creation System. Version SCS GGSNS6.0_SCS6.0(47) ***************************************************************** * SCS 6.0 requires IPlanet LDAP 5.1. If you are not running IPlanet * * LDAP 5.1, please upgrade the LDAP server before starting the SCS * * Installation. Please refer to the SCS installation document and * * SCS Release Notes for details on upgrading the Directory Server. * * * * SCS and LDAP require Solaris Recommended Patches. * * Make sure that the latest patches have been installed * * If you are not sure, please abort the setup and check Patch level * * Restart the setup.sh script after checking the patch level * ***************************************************************** You have the following options: (C) Create a new SCS Server installation (U) Upgrade the current SCS Server
GPRS/UMTS
260

(A) Abort this installation
Please enter (C)reate, (U)pgrade or (A)bort? [A]: u <- Enter U to upgrade (N) Normal Upgrade the current SCS Server (R) Rolling Upgrade the current SCS Server Please enter (N)ormal or (R)olling? [N]: r <- Enter r to select Rolling Upgrade Found the parameters File, /opt/shasta/scs6.0/ .inputparms_rolling.scs oldVersion=GGSNS4.1.2_SCS5.0(1) action=upgrade The following SCS server(s) are currently installed on this machine: Version SCS GGSNS4.1.2_SCS5.0(1) SCS Domain Server (LDAP Server IP = localhost) SCS Region Server (Region ID = 1) SCS Monitor Server SCS Pull Server (Listening Port = 4321) SCS Log Server (Logging Port = 4322, Accounting Port = 4323) SCS CORBA Server in the same directory as you specified. Reading input Parameters from /opt/shasta/scs6.0/ .inputparms_rolling.scs, Please wait Reading the input parameters and Validating... This is a valid LDAP Path The ldap server is slapd-zrc2s0u81 /opt/shasta/ldap/slapd-zrc2s0u81/config Ldap port is validated Value from the config File is - 390 Checking if the LDAP Schema files are present LDAP Schema Files are present in /opt/shasta/scs6.0 ================================================================= The Following Parameters are read from the /opt/shasta/scs6.0/ .inputparms_rolling.scs ================================================================= SCS will be upgraded in the following directory : /opt/shasta/ scs6.0 SCS processes will run after the reboot : y SCS Backup Directory is : /opt/shasta/ scs6.0/backup LDAP is installed on this server : y LDAP Port on this Server is : 390 LDAP Path is : /opt/shasta/ldap LDAP Server is : slapd-zrc2s0u81 LDAP IP Address is : localhost LDAP Data Migration is : y LDAP Migration Path is : /opt/shasta/ iplanet LDAP Migration Port is : 396 Is CSV User set on this Server : y Name of the user to collect the CSV Files : pmuser Days CSV Files will be preserved : 4 Install Corba Server on this Server : n Please check the input parameters and confirm If the input is not right, quit by answering n
411-5221-309
Standard
06.30 March 10, 2010
261
Change the /opt/shasta/scs6.0/.inputparms_rolling.scs and restart the script if you answer n Do you want to continue (Y/N)? [N]: y <- Enter Y to proceed with the upgrade User accepted the parameters, continuing with upgrade SCS will be installed in /opt/shasta/scs6.0. Checking the available space ... Required space 205132 Kbytes. Available space 43072471 Kbytes. Found enough space to install SCS. Backup the current SCS database to /opt/shasta/scs6.0/opt/solidSolaris/database/ backup.GGSNS4.1.2_SCS5.0(1) ...... Using /opt/shasta/ldap as LDAP path Using slapd-zrc2s0u81 as LDAP server **************************************************** * The 5.0 LDAP schema has been changed. * * This Upgrade script will update the schema files * **************************************************** Upgrading the database ... Upgrading your SOLID server to latest version of SOLID FlowEngine 4.0 ... Verifying the current database files ..... [1] 12193 Starting Solid Database Server:.Started Currently running SCS version GGSNS4.1.2_SCS5.0(1). Upgrading domain database schema... Detected Last Upgrade Number: 48 Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying Applying upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade upgrade # # # # # # # # # # # # # # # # # # # # # # # # 500... 501... 502... 503... 504... 505... 506... 507... 508... 511... 512... 513... 514... 515... 516... 517... 518... 519... 520... 521... 522... 523... 524... 525...
GPRS/UMTS
262

Applying upgrade # 526... Applying upgrade # 527... Applying upgrade # 528... Applying upgrade # 529... Applying upgrade # 530... Applying upgrade # 531... Applying upgrade # 532... Applying upgrade # 533... Applying upgrade # 534... Applying upgrade # 535... Applying upgrade # 536... Applying upgrade # 537... Applying upgrade # 538... Applying upgrade # 539... Applying upgrade # 540... Applying upgrade # 541... Applying upgrade # 542... Applying upgrade # 543... Applying upgrade # 544... Applying upgrade # 545... Applying upgrade # 546... Applying upgrade # 547... Applying upgrade # 601... Applying upgrade # 602... Applying upgrade # 603... Applying upgrade # 604... Applying upgrade # 605... Applying upgrade # 606... Applying upgrade # 607... Applying upgrade # 700... Applying upgrade # 701... Applying upgrade # 702... Applying upgrade # 703... Applying upgrade # 704... Applying upgrade # 705... Applying upgrade # 706... Applying upgrade # 707... Applying upgrade # 708... Applying upgrade # 709... Applying upgrade # 710... Applying upgrade # 711... Applying upgrade # 712... Setting Last Upgrade Number to 712 ... Upgrading region database schema... Detected Last Upgrade Number:
35 Applying upgrade # 500... Applying upgrade # 501... Applying upgrade # 502... Applying upgrade # 503... Applying upgrade # 601... Applying upgrade # 602... Applying upgrade # 603... Applying upgrade # 700... Applying upgrade # 701... Applying upgrade # 702... Applying upgrade # 703... Applying upgrade # 704... Applying upgrade # 705... Setting Last Upgrade Number to 705 ... Calling the upgrade_drop_add_procedure script Apply upgrade_drop_add_procedure-do.sql ... Apply upgrade_drop_add_procedure-reg.sql ... Stopping Solid Database Server:.Stopped
411-5221-309
Standard
06.30 March 10, 2010

Copying the required files ...
263
LDAP Installation..... /opt/shasta/iplanet ============================== iPlanet Directory Server 5.x installation begins! ============================== zrc2s0u8 us.nortel.com Unpacking ... Start installation, please wait... Installing Netscape core components Installing Server Core Components Installing iPlanet Directory Suite Installing Administration Services Installing nsPerl Installing PerLDAP Extracting Netscape core components ... Extracting Server Core Components ... Extracting Core Java classes ... Extracting Java Runtime Environment ... Extracting iPlanet Directory Server ... Extracting iPlanet Directory Server Console ... Extracting iPlanet Administration Server ... Extracting Administration Server Console ... Extracting nsPerl 5.005_03 ... Extracting PerLDAP 1.4.1 ... [slapd-zrc2s0u8]: starting up server ... [slapd-zrc2s0u8]: [11/May/2008:12:01:28 -0500] - iPlanetDirectory/5.1 Service Pack 3 B2003.324.1439 starting up [slapd-zrc2s0u8]: [11/May/2008:12:01:29 -0500] - slapd started. Listening on all interfaces port 396 for LDAP requests Your new directory server has been started. Created new Directory Server Start Slapd Starting Slapd server configuration. Success Slapd Added Directory Server information to Configuration Server. Configuring Administration Server... Your parameters are now entered into the Administration Server database, and the Administration Server will be started. Changing ownership to admin user root... Setting up Administration Server Instance... Configuring Administration Tasks in Directory Server... Configuring Global Parameters in Directory Server... iPlanet-WebServer-Enterprise/6.0SP2 B01/06/2003 22:24 warning: daemon is running as super-user [LS ls1] http://zrc2s0u8.us.nortel.com, port 33611 ready to accept requests startup: server started successfully Installation is complete. See /opt/shasta/iplanet/setup/setup.log for possible errors. Schema update, please wait... Complete schema update Data Migration y Deleting Root Point and Suffix to allow Migration from existing database.....
GPRS/UMTS
264

Deleting Root Point and Suffix done Migrating data, please wait...
******* Migration from 4.16 Netscape Directory Server to 5.1 iPlanet Directory Server ********* Shutdown the legacy Directory Server instance: /opt/shasta/ldap/ slapd-zrc2s0u81 Shutting down server slapd-zrc2s0u81 . . . . . . Netscape Communications Corporation Netscape-Directory/4.16 B01.300.2102 Sun | Netscape Alliance iPlanet-Directory/5.1 Service Pack 3 B2003.324.1439 Version of the old directory server: 4.16 Connected to 5.1 LDAP server Backup /opt/shasta/iplanet/slapd-zrc2s0u8/config on /opt/shasta/ iplanet/slapd-zrc2s0u8/config_backup ... /opt/shasta/iplanet/slapd-zrc2s0u8/config has been backup in /opt/ shasta/iplanet/slapd-zrc2s0u8/config_backup Parse the configuration file: /opt/shasta/ldap/slapd-zrc2s0u81/ config/slapd.conf... Migrate key/cert databases... Update general server parameters... Update successfully nsslapd-reservedescriptors Update successfully passwordHistory Update successfully nsslapd-sizelimit Update successfully nsslapd-errorlog-maxlogsperdir Update successfully nsslapd-enquote-sup-oc Update successfully passwordStorageScheme Update successfully nsslapd-rootpwstoragescheme Update global LDBM parameters... Update successfully nsslapd-mode Update successfully nsslapd-lookthroughlimit Update specific backend parameters... Shutting down server slapd-zrc2s0u8 . . . . . . data processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Processing... Done.
411-5221-309
Standard
06.30 March 10, 2010
265
[11/May/2008:12:04:26 -0500] - import MigratedDB_0: Index buffering enabled with bucket size 9 [11/May/2008:12:04:26 -0500] - import MigratedDB_0: Beginning import job... [11/May/2008:12:04:26 -0500] - import MigratedDB_0: Processing file "/opt/shasta/ldap/slapd-zrc2s0u81/config//ldif/ MigratedDB_0.ldif" [11/May/2008:12:04:28 -0500] - import MigratedDB_0: Finished scanning file "/opt/shasta/ldap/slapd-zrc2s0u81/config//ldif/ MigratedDB_0.ldif" (1806 entries) [11/May/2008:12:04:29 -0500] - import MigratedDB_0: Workers finished; cleaning up... [11/May/2008:12:04:33 -0500] - import MigratedDB_0: Workers cleaned up. [11/May/2008:12:04:33 -0500] - import MigratedDB_0: Cleaning up producer thread... [11/May/2008:12:04:33 -0500] - import MigratedDB_0: Indexing complete. Post-processing... [11/May/2008:12:04:34 -0500] - import MigratedDB_0: Flushing caches... [11/May/2008:12:04:34 -0500] - import MigratedDB_0: Closing files... [11/May/2008:12:04:35 -0500] - import MigratedDB_0: Import complete. Processed 1806 entries in 9 seconds. (200.67 entries/ sec) [11/May/2008:12:04:35 -0500] - import MigratedDB_1: Index buffering enabled with bucket size 9 [11/May/2008:12:04:35 -0500] - import MigratedDB_1: Beginning import job... [11/May/2008:12:04:36 -0500] - import MigratedDB_1: Processing file "/opt/shasta/ldap/slapd-zrc2s0u81/config//ldif/ MigratedDB_1.ldif" [11/May/2008:12:04:36 -0500] - import MigratedDB_1: Finished scanning file "/opt/shasta/ldap/slapd-zrc2s0u81/config//ldif/ MigratedDB_1.ldif" (2 entries) [11/May/2008:12:04:36 -0500] - import MigratedDB_1: Workers finished; cleaning up... [11/May/2008:12:04:41 -0500] - import MigratedDB_1: Workers cleaned up. [11/May/2008:12:04:41 -0500] - import MigratedDB_1: Cleaning up producer thread... [11/May/2008:12:04:41 -0500] - import MigratedDB_1: Indexing complete. Post-processing... [11/May/2008:12:04:41 -0500] - import MigratedDB_1: Flushing caches... [11/May/2008:12:04:41 -0500] - import MigratedDB_1: Closing files... [11/May/2008:12:04:41 -0500] - import MigratedDB_1: Import complete. Processed 2 entries in 6 seconds. (0.33 entries/sec) ****** -> -> End of migration ******
Migration started at Sun May 11 17:01:54 2008 Migration ended at Sun May 11 17:04:44 2008
*********************************************** -> The migration report file is available at: /opt/shasta/ iplanet/slapd-zrc2s0u8/logs/Migration_11052008_120151.log
Updating the config file with the new LDAP information *.5001 Idle Selecting next available port...
GPRS/UMTS
266
SNMP Proxy using port 5002, SNMP Trap using port 5003. LDAP schema files updated successfully Now stopping and restarting LDAP server slapd-zrc2s0u8 ... To generate CSV formatted accounting data, a user id must be designated as the owner of the generated files. It is recommended that the user id not be the root user. The ownership of any existing CSV formatted accounting data file will also be changed to this user id. The user id, pmuser, already exists and will be used by the SCS Log Server process for CSV generated files. Updating For Rolling Upgrade... SSL is being disabled The installation logs are saved in /opt/shasta/scs6.0/lib/install/ *.log. UPGRADE IS COMPLETED SUCCESSFULLY The following SCS server(s) are currently installed on this machine: Version SCS GGSNS6.0_SCS6.0(47) SCS SCS SCS SCS SCS SCS You can Server. Domain Server (LDAP Server IP = localhost) Region Server (Region ID = 1) Monitor Server Pull Server (Listening Port = 4321) Log Server (Logging Port = 4322, Accounting Port = 4323) CORBA Server use '/opt/shasta/scs6.0/bin/SCSAdmin start' to run SCS
End of ./setup.sh capture for SCS 4.1.2 to SCS 6.0 upgrade
Proceed to Verify SCS Upgrade logs on page 267
411-5221-309
Standard
06.30 March 10, 2010
267
Verify SCS Upgrade logs 17. The SCS upgrade log files are located in the <SCS6.0_ROOT>/lib/install. Run the following commands.
# cd <SCS6.0_ROOT>/lib/install # grep -i error *.log | grep -i solid
The above grep command should NOT return any thing if there are no solid upgrade errors. If the grep command returns any error lines, please contact Nortel support. 18. Make sure there are no iPlanet installations errors. To check iPlanet installation logs, check file rollingUpgradeLdap.log in <SCS6.0_ROOT>.
Example: # cat /opt/shasta/scs6.0/rollingUpgradeLdap.log Look for line:
Success Slapd Added Directory Server information to Configuration Server. and ***** Rolling upgrade for LDAP succeeded at <date> *****
19. Make sure there are no iPlanet installations errors.

# cd /opt/shasta/iplanet/setup # more setup.log [06/02/06:17:19:55] - [Setup] [06/02/06:17:19:55] - [Setup] installation... [06/02/06:17:19:55] - [Setup] [06/02/06:17:19:55] - [Setup] core components [06/02/06:17:19:55] - [Setup] Components [06/02/06:17:19:55] - [Setup] Directory Suite [06/02/06:17:19:55] - [Setup] Administration Services [06/02/06:17:19:55] - [Admin] pre-configuration. [06/02/06:17:19:55] - [Setup] [06/02/06:17:19:55] - [Setup]
Info Start... Info Start silent Info PreInstall phrase... Start Installing Netscape Start Installing Server Core Start Installing iPlanet Start Installing Success Administration Server Start Installing nsPerl Start Installing PerLDAP
GPRS/UMTS
268
SCS Software Upgrade [06/02/06:17:19:55] - [Setup] binaries... [06/02/06:17:19:55] - [Setup] components ... [06/02/06:17:20:41] - [Setup] [06/02/06:17:20:41] - [Setup] core components. [06/02/06:17:20:41] - [Setup] Core Components. [06/02/06:17:20:52] - [Setup] Directory Suite. [06/02/06:17:20:55] - [Setup] Administration Services. [06/02/06:17:20:55] - [Setup] [06/02/06:17:20:55] - [Setup] [06/02/06:17:20:56] - [Setup]
Nortel Networks Confidential Info Unzip component Info Extracting Netscape core Info PostInstall phrase... Success Installing Netscape Success Installing Server Success Installing iPlanet Success Installing Success Installing nsPerl. Success Installing PerLDAP. Info DONE
Note: If there are any errors in the setup.log file, iPlanet installation may not be complete and result in critical processes not starting. Please follow Clean up Procedure in case of Upgrade failure. 20. Make sure critical iPlanet files are installed correctly.
# # # # # # # cd ls ls cd ls ls ls /opt/shasta/iplanet start-admin stop-admin slapd* start-slapd stop-slapd restart-slapd
Proceed to Change the pmuser password on page 268 Change the pmuser password 21. Change the pmuser password. This step is optional Note: If unix user to collect the Performance data is configured for the first time during the upgrade to 5.0, set the password for this user. Default name to this user is pmuser. Check if the user already exists before the upgrade, this can be done by the command "cat /etc/passwd". If the user exists, do not change the password unless the customer asks for the password to be changed.
# passwd pmuser
Enter the password twice and the password will be set. Proceed to Execute ns_server_secure.sh script on page 269
411-5221-309
Standard
06.30 March 10, 2010
269
Execute ns_server_secure.sh script 22. Run the ns_server_secure.sh script to enable iPlanet directory server security. Before you run the script, you need to set the unix PATH environment variable.
Example:
Make sure you are in CSH.

# echo $SHELL
If you are not in CSH, type csh at the server prompt and hit enter.
Set the PATH environment variable # set path=(/opt/shasta/iplanet/shared/bin $path) <----manually set path before running script # cd /opt/shasta/scs6.0
Execute ns_server_secure.sh
# ./ns_server_secure.sh Here is an example capture: # ./ns_server_secure.sh **** NOTE **** Please run this script on the machine where Netscape Directory Server is installed. There is no need to restart the Netscape Directory Server after running this script. Do you have SCS installed on this machine [Y/N]: Y <---answered Y Please specify the directory where SCS is installed. [/opt/shasta/scs6.0]: <---accepted default Please specify the root directory where the Netscape Directory Server is installed. [/space/netscape/server4]: /opt/shasta/iplanet <----notice difference here Please provide the LDAP Server IP address [localhost]: <---accepted default Please provide the LDAP Server Port Number [390]: <---accepted default Please provide the LDAP Root point for SCS [uid=admin,ou=People,o=us.nortel.com]: <---accepted default Please provide the Directory Manager password for Netscape Directory Server [password]: dmanager <----notice difference here **** CASE 1 **** Disable anonymous access to LDAP Directory GPRS/UMTS Upgrade Manual GGSN6.0
270
Deleting Self entry modification ACL in o=us.nortel.com: Already deleted. Modification complete Deleting Anonymous access ACL in o=us.nortel.com: Already deleted. Modification complete **** CASE 2 **** Enable search on LDAP Configuration to authorized users only Deleting anonymous access to LDAP configuration information : Already deleted. Modification complete Enable admin only access to LDAP configuration information : modifying entry cn=SNMP,cn=config Modification complete **** CASE 3 **** Enable search on LDAP Monitoring to authorized users only Deleting anonymous access to LDAP monitoring information : Already deleted. Modification complete Enable admin only access to LDAP monitoring information : modifying entry cn=monitor Modification complete **** CASE 4 **** Enable subtree search on LDAP NULL DN to authorized users only No changes need to be done as Netscape Directory Server does not allow this. No modifications need to be done **** CASE 5 **** Enable search on LDAP schema to authorized users only Enable admin only access to LDAP schema information : Already deleted. Modification complete Completed adding access control to Netscape Directory Server.
Proceed to Login to iPlanet administration console on page 270
Login to iPlanet administration console 23. iPlanet admin server port is assigned 33611. To login to the iPlanet console, use:
# cd <IPLANET_ROOT>
Note: Export environment variable DISPLAY before launching iPlanet console.
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Example:
271
In C shell:
# setenv DISPLAY <YOUR_PC_IP>:0.0 # ./startconsole & Username: admin (unless modified by user) Password: admin Administration URL: http://scshost.domain:33611
24. Verify iPlanet directory server performance parameter Size Limit is set to -1 After the Console window comes up, in the left-hand frame there is a tree showing the directory structure. Click on the "magnifying glass" icon next to the (Fully Qualified Domain Name) to expand the tree to display the Server Group folder icon.
25. Click on the "magnifying glass" icon next to the Server group folder icon to expand the tree to display the Directory Server icon. 26. Double click on the Directory Server icon to bring up the Directory Server screen 27. Click on the Configuration tab of the Directory Server screen to bring up the Configuration window. 28. Click on the Performance tab of the Configuration window and set the Size Limits field to -1. Click Save. If the value is already set to -1, then exit out of the window and close the directory server console. Proceed to Enable SCS and iPlanet auto startup scripts: on page 271
Enable SCS and iPlanet auto startup scripts: Enable SCS and iPlanet auto startup scripts. This way, SCS and iPlanet processes are started automatically on a server reboot. Please follow instructions in SCS and iPlanet auto startup scripts on page 230
GPRS/UMTS
272
After enabling the SCS/ iPlanet startup scripts, proceed to: Optional - Install SSL Package on page 272 or Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
Optional - Install SSL Package 29. Optional - Installation of the SSL Package. This step is only required, if the customer wants to install and enable SSL on the SCS server. Note: If SSL is enabled on the SCS Server, the SCS Client machine should also be SSL enabled. If client is not SSL enabled, the SCS Client will not come up. a. Login as root on to the SCS server. Make sure the login shell is csh. Please refer to Basic system settings required on the SCS: on page 200 to verify if the current login shell is csh
# cd <SCS6.0_ROOT>
b. Insert the SSL CD. Then find out the CD mount point using df -k. Note, the SCS SSL software can also be retrieved from ESD.
# df -k Here is an example: # df -k ... <-Other mounted partitions /vol/dev/dsk/c0t6d0/ggsn0060 330000 330000 0
100%
/ cdrom/gssl0060
c. Copy the sslpkg.tar.Z from the SCS SSL CD to the present directory, uncompress and then untar the SSL package file.
# cp /cdrom/gssl0060/SSL/sslpkg.tar.Z <SCS6.0_ROOT> # uncompress sslpkg.tar.Z # tar -xvf sslpkg.tar
d. Change the execution permission of setup.sh.

# chmod 755 setup.sh
e. Execute the setup.sh

# ./setup.sh 411-5221-309 Standard 06.30 March 10, 2010
273
Here is an example:
# ./setup.sh This program will install SCS SSL version SCS GGSNS6.0_SCS6.0(42) Please specify the directory for SCS installation [/opt/ shasta/scs6.0]: <-hit enter to select default Matching SCS version found - SCS SSL will be installed in /opt/shasta/scs6.0. Copying the required files...... SCS SSL is now installed. Refer to SCS documentation for instructions on enabling SSL.
The above step will install the SSL package. f. Refer to Nortel GGSN Provisioning Procedures NTP 411-5221-927 (v09.18 or greater), section Enabling SSL to generate SSL certificates and install them on the SCS client. g. Enable the SSL
# cd <SCS6.0_ROOT>/bin # ./SCSAdmin SSLEnable on
h. Restart the SCS Processes to enable the SSL

i. Verify SCS processes are running and SSL is enabled

# ./SCSAdmin status
Return to: Table 14 Upgrade SCS 4.1.2 to SCS 6.0 on same serveron page 162 OR Table 8 Migrating SCS to a new physical server with Same or Different IP addresson page 169
and proceed to the next step
GPRS/UMTS
274
Upgrade GGSN SCS from 5.0.2 to 6.0
12
The following steps provide the user with a high level overview of the GGSN SCS 6.0 software upgrade. The detailed steps are explained in SCS 5.0.2 to 6.0 upgrade details on page 275 Step 1: Make sure GGSN SCS 5.0.2 and iPlanet 5.1 server processes are running Step 2: Create a new directory for GGSN SCS 6.0 server installation. This is <SCS60_ROOT >
Example:
<SCS60_ROOT> : /opt/shasta/scs6.0
Step 3: Copy SCS 6.0 server software scsserver.tar.Z file from the SCS installation CD to <SCS6.0_ROOT>. The software can also be retrieved from ESD. Step 4: Uncompress and untar scsserver.tar.Z file in <SCS6.0_ROOT> Step 5: Disable SCS 5.0.2 provisioning Step 6: Perform a SOLID database backup Step 7: Execute upgrade script - rollingSCS.sh Step 8: Verify SOLID database integrity Step 9: Execute upgrade script - setup.sh Step 10: Verify SCS and iPlanet upgrade logs
Convention: <SCS502_ROOT> = SCS 5.0.2 installation directory

Example: /opt/shasta/scs502
<SCS6.0_ROOT> = SCS 6.0 installation directory

Example: /opt/shasta/scs6.0
<IPLANET_ROOT> = iPlanet 5.1 installation directory. This directory is common for both SCS 5.0.2 and SCS 6.0 installations
Example: /opt/shasta/iplanet 411-5221-309 Standard 06.30 March 10, 2010
275
Make a note of the above directory structures as they will be required during the upgrade process.
SCS 5.0.2 to 6.0 upgrade details 1. Login as root onto the SCS Server 2. Make sure you are in C - shell.
#echo $SHELL
This will show the present shell. If the default shell for root is not set as csh, then modify /etc/passwd and put in /usr/bin/csh instead of the preconfigured shell. Find the path where csh is located.
# which csh /usr/bin/csh
Use vi editor to modify the shell entry for root user.

After modifying /etc/passwd, login to the server as root from another telnet window. This way, if there was some error modifying /etc/passwd, and you are unable to log back in to the server, you are still logged into the server in the original window that was used to modify the file. Make sure to correct any errors in /etc/passwd in case of a login failure. Other system settings needed are: File /etc/nsswitch.conf contains: hosts: file dns Example: hosts:file dns File /etc/resolv.conf contains: domain <domain name> Example: domain my.company.com File /etc/hosts contains: <machines static ip address> <hostname> <fqdn> loghost
276
Example: 99.100.100.100 scshost scshost.my.company.com loghost 3. Verify iPlanet 5.1 directory server and admin servers are running. If the process is not running, start the processes. Determine <IPLANET_ROOT> and iPlanet instance:
# cd /etc/shasta
a. Determine <IPLANET_ROOT>
# more scs.config | grep LDAPPath Example: LDAPPath=/opt/shasta/iplanet <IPLANET_ROOT> = LDAPPath = /opt/shasta/iplanet
b. Determine <iPLANET instance>

# more scs.config | grep LDAPServerName Example: LDAPServerName=slapd-zrc2s186 <iPlanet instance> = LDAPServerName = slapd-zrc2s186
c. Check LDAP server processes is running from <IPLANET_ROOT>/ <iPlanet instance>, check the correct iPlanet instance is running (instance matching LDAPServerName):
# ps -aef | grep -v grep | grep slapd nobody 14025 1 0 Aug 25 ? 0:06 ./ns-slapd D /opt/shasta/iplanet/slapd-zrc2s186 -i /opt/shasta/ iplanet/slapd-z
Check LDAP admin process is running:

# ps -aef | grep -v grep | grep admin root 13552 13550 0 Aug 25 ? opt/shasta/iplanet/admin-serv/config
0:00 ns-httpd -d /
If the above ps -aef command does not return a result, start the iPlanet directory server and admin server processes. To start iPlanet directory server process:
# cd <IPLANET_ROOT>/<iPlanet instance> 411-5221-309 Standard 06.30 March 10, 2010
277
Example: # cd /opt/shasta/iplanet/slapd-zrc2s186 # ./start-slapd
To start iPlanet admin server process:

#./start-admin
Verify iPlanet admin server port 33611 is LISTENing:

# netstat -na | grep -v grep | grep 33611 Example: # netstat -na | grep -v grep | grep 33611 *.33611 *.* 0 0 LISTEN
0 24576
Execute the above ps -aef command and verify iPlanet directory server and admin server processes are running. If the processes dont start, contact your next level of support before proceeding. 4. Verify the status of all the SCS 5.0.2 processes. Execute the following from the <SCS502_ROOT>/bin directory. If any of the processes are not running, try restarting the processes.
# cd /etc/shasta # more scs.config | grep SCSHead Example: SCSHead = /opt/shasta/scs502 <SCS502_ROOT> = SCSHead = /opt/shasta/scs502 # cd <SCS502_ROOT>/bin # ./SCSAdmin status
Example: # cd /opt/shasta/scs502/bin # ./SCSAdmin status

Running Solid Database Server since 12:11:12 (pid=27047) Running SCS Daemon since 12:11:13 (pid=27065) Running SCS Domain Server since 12:11:20 (pid=27081) Running SNMP Proxy since 12:11:32 (pid=27113) Running SCS Region Server since 12:11:46 (pid=27145) Running SCS Monitor Server since 12:11:56 (pid=27171) Running SCS Trap Daemon since 12:12:06 (pid=27222) Running SCS Pull Server since 12:12:16 (pid=27249) Running SCS Log Server since 12:12:25 (pid=27269) Running SCS CORBA Server since 12:11:37 (pid=27119) SSL is not enabled on present servers All SCS server processes are running. Version SCS GGSNS5.0.2_SCS5.0(14)
GPRS/UMTS
278
Note: If customer is not using Corba, you will not see the Corba Server running. If any process is not running, restart the SCS server processes. To restart SCS server processes:
# cd <SCS502_ROOT>/bin #./SCSAdmin restart
If any of the processes are not running, contact your next level of support before proceeding. 5. Create a directory for GGSN SCS 6.0 software. This is represented as <SCS6.0_ROOT>.
Example: # cd /opt/shasta # mkdir scs6.0 # cd scs6.0
6. Insert the GGSN SCS 6.0 software CD. Verify CDROM mount point on the server using df -k. Copy the SCS Server software (scsserver.tar.Z) on the CD to the <SCS6.0_ROOT> directory. Note, the SCS server software can also be retrieved from ESD.
# df -k <-Find CD mount point
#cp /cdrom/ggsn0061/Solaris/scsserver.tar.Z <SCS6.0_ROOT> Example: # df -k /vol/dev/dsk/c0t2d0/ggsn0061 407692 407692 0 100% /cdrom/ggsn0061 # cp /cdrom/ggsn0060/Solaris/scsserver.tar.Z /opt/shasta/ scs6.0
7. Uncompress the SCS Server software, in the <SCS6.0_ROOT> directory

# uncompress scsserver.tar.Z
8. Untar the SCS server software into the <SCS6.0_ROOT> directory.
411-5221-309
Standard
06.30 March 10, 2010
279
# tar -xvf scsserver.tar
9. Copy the SCS Corba server software (scs_corba_server.tar.Z) on the CD (or ESD) to the <SCS6.0_ROOT> directory. Note, SCS Corba server software can be copied from the SCS Corba server application CD or ESD (GCOR0060).
#cp /cdrom/cdrom0/Solaris/scs_corba_server.tar.Z <SCS6.0_ROOT> Example: # cp /cdrom/cdrom0/Solaris/scs_corba_server.tar.Z /opt/shasta/scs6.0
10. Uncompress scs_corba_server.tar.Z

#uncompress scs_corba_server.tar.Z
Note: 1GB of free space in the root directory is recommended. Use df -k to verify the disk space availability. Note: This step is only required of the customer is using Corba. Uncompress the SCS Corba file, but DO NOT UNTAR THE CORBA FILE.
Proceed to Disable SCS 5.0.2 provisioning on page 280.
GPRS/UMTS
280
Disable SCS 5.0.2 provisioning Note: This step is mandatory. If this step is skipped, GGSNs will go Out of Sync after the SCS 6.0 upgrade. Note: Also, login to the SCS client and make sure the GGSN is insync. If the GGSN has a status other than Insync, please contact Nortel support. 11. Disable SCS 5.0.2 provisioning. a. Determine <SCS502_ROOT>:
# cat /etc/shasta/scs.config | grep SCSHead Example: # cat /etc/shasta/scs.config | grep SCSHead <SCS_ROOT> = SCSHead=/opt/shasta/scs
b. Disable SCS provisioning:

# cd <SCS502_ROOT>/bin # ./SCSAdmin disableProvisioning
Example: # cd /opt/shasta/scs/bin # ./SCSAdmin disableProvisioning
From this point the GGSNs are not under management control but the GGSN can still handle traffic
Proceed to Perform a SOLID database backup on page 280.
Perform a SOLID database backup 12. Make a backup copy of SCS 5.0.2 SOLID database.
# ./SCSAdmin backup solidDB
This will backup SCS SOLID database to <SCS502_ROOT>/opt/solidSolaris/database/backup Here is an example:

# ./SCSAdmin backup solidDB binDir is /opt/shasta/scs502/bin head is /opt/shasta/scs502
411-5221-309
Standard
06.30 March 10, 2010
281
configFile is /opt/shasta/scs502/bin/.scs.config backup_dir is /opt/shasta/scs502/opt/solidSolaris/database/ backup This will overwrite the directory /opt/shasta/scs502/opt/ solidSolaris/database/backup. Are you sure? (Y)es or (N)o: y Solid Remote Control v.04.00.0025 (C) Copyright Solid Information Technology Ltd 1993-2003 Exit by giving command: exit Backup started. ....
Proceed to Executing rollingSCS.sh procedure on page 281.
Executing rollingSCS.sh procedure 13. Run the rollingSCS.sh and follow the prompts to setup your rolling SCS directory and duplicate LDAP directory server instance.
# cd /opt/shasta/scs6.0 #./rollingSCS.sh
Here is a sample of rollingSCS.sh script execution.

# ./rollingSCS.sh This script lets you upgrade without impacting the current SCS servers ================================================================= ================ The following parameters are automatically detected ================================================================= ================ Directory where current SCS servers are running : /opt/shasta/scs502 SCS will be upgraded in the following directory : /opt/shasta/scs6.0 The root directory for current Netscape Directory Server : /opt/shasta/iplanet Machine name : ur2y3pa Domain name : us.nortel.com IP address : 47.104.6.101 New instance name : ur2y3pa1 New instance port : 390 New LDAP Root DN Password : dmanager
GPRS/UMTS
282
The following Netscape Directory Servers are currently installed on your machine: (1) /opt/shasta/iplanet/slapd-ur2y3pa The Netscape Directory Server directory to be exported : 1 Root point to be exported : o=us.nortel.com ================================================================= Do you want to change the parameters suggested above (Y/N)? [N]: <- Hit enter to select N, if user selects Y, the script will prompt to user input Now we will export data from the root point o=us.nortel.com at server /opt/shasta/iplanet/slapd-ur2y3pa then update and import them to the server /opt/shasta/iplanet/ slapd-ur2y3pa1 Do you want to continue (Y/N)? [Y]: Setting up the directory for the upgraded SCS Servers... slapd-ur2y3pa ======================================================= Rolling upgrade for Netscape Directory Server begins! ======================================================= Creating new instance... Creating new instance completed Exporting the data, please wait...... Exporting data completed. 3544 3487 Adding entries for creating organization index 3487 3544 /opt/shasta/iplanet/slapd-ur2y3pa1 is being shutdown... Netscape Directory Server is shutdown. Reset the look through limit and size limit of the new instance server.... Schema update, please wait... Creating indexes for Netscape Directory Server Creating index shastaId [06/Dec/2008:18:44:12 +0000] - userRoot: Indexing attribute: shastaId [06/Dec/2008:18:44:12 +0000] - userRoot: Finished indexing. Creating index shastaType [06/Dec/2008:18:44:13 +0000] - userRoot: Indexing attribute: shastaType [06/Dec/2008:18:44:13 +0000] - userRoot: Finished indexing.
411-5221-309
Standard
06.30 March 10, 2010
283
Creating index shastaContainerId [06/Dec/2008:18:44:13 +0000] - userRoot: Indexing attribute: shastaContainerId [06/Dec/2008:18:44:13 +0000] - userRoot: Finished indexing. Creating index shastaContainerType [06/Dec/2008:18:44:14 +0000] - userRoot: Indexing attribute: shastaContainerType [06/Dec/2008:18:44:14 +0000] - userRoot: Finished indexing. Creating index ntlTemplateType [06/Dec/2008:18:44:15 +0000] - userRoot: Indexing attribute: ntlTemplateType [06/Dec/2008:18:44:15 +0000] - userRoot: Finished indexing. Creating index ntlIpdemuxTmplRefPI [06/Dec/2008:18:44:16 +0000] - userRoot: Indexing attribute: ntlIpdemuxTmplRefPI [06/Dec/2008:18:44:16 +0000] - userRoot: Finished indexing. Creating index ntlShastaSGroupRefPI [06/Dec/2008:18:44:16 +0000] - userRoot: Indexing attribute: ntlShastaSGroupRefPI [06/Dec/2008:18:44:16 +0000] - userRoot: Finished indexing. Creating index ntlShastaConnectionRefPI [06/Dec/2008:18:44:17 +0000] - userRoot: Indexing attribute: ntlShastaConnectionRefPI [06/Dec/2008:18:44:17 +0000] - userRoot: Finished indexing. Creating index ntlShastaDeviceRefPI [06/Dec/2008:18:44:18 +0000] - userRoot: Indexing attribute: ntlShastaDeviceRefPI [06/Dec/2008:18:44:18 +0000] - userRoot: Finished indexing. Creating index ntlShastaCardRefPI [06/Dec/2008:18:44:18 +0000] - userRoot: Indexing attribute: ntlShastaCardRefPI [06/Dec/2008:18:44:18 +0000] - userRoot: Finished indexing. Creating index ntlShastaPortRefPI [06/Dec/2008:18:44:19 +0000] - userRoot: Indexing attribute: ntlShastaPortRefPI [06/Dec/2008:18:44:19 +0000] - userRoot: Finished indexing. Creating index ntlIpdemuxRefPI [06/Dec/2008:18:44:20 +0000] - userRoot: Indexing attribute: ntlIpdemuxRefPI [06/Dec/2008:18:44:20 +0000] - userRoot: Finished indexing. Creating index ntlBgpIncomingRoutePolicyRefPI [06/Dec/2008:18:44:21 +0000] - userRoot: Indexing attribute: ntlBgpIncomingRoutePolicyRefPI [06/Dec/2008:18:44:21 +0000] - userRoot: Finished indexing. Creating index ntlBgpOutgoingRoutePolicyRefPI [06/Dec/2008:18:44:21 +0000] - userRoot: Indexing attribute: ntlBgpOutgoingRoutePolicyRefPI [06/Dec/2008:18:44:21 +0000] - userRoot: Finished indexing. Creating index ntlTunnelSetRefPI [06/Dec/2008:18:44:22 +0000] - userRoot: Indexing attribute: ntlTunnelSetRefPI [06/Dec/2008:18:44:22 +0000] - userRoot: Finished indexing. Creating index ntlVPNRefPI [06/Dec/2008:18:44:23 +0000] - userRoot: Indexing attribute: ntlVPNRefPI
GPRS/UMTS
284
[06/Dec/2008:18:44:23 +0000] - userRoot: Finished indexing. Creating index ntlBridgeGroupRefPI [06/Dec/2008:18:44:23 +0000] - userRoot: Indexing attribute: ntlBridgeGroupRefPI [06/Dec/2008:18:44:24 +0000] - userRoot: Finished indexing. Creating index userid [06/Dec/2008:18:44:24 +0000] - userRoot: Indexing attribute: userid [06/Dec/2008:18:44:24 +0000] - userRoot: Finished indexing. /opt/shasta/iplanet/slapd-ur2y3pa1 is being shutdown for importing data... /opt/shasta/iplanet/slapd-ur2y3pa1 is shutdown Importing the data, please wait..... Importing data completed. /opt/shasta/iplanet/slapd-ur2y3pa1 is starting... /opt/shasta/iplanet/slapd-ur2y3pa1 is restarted. We will now backup your primary directory server, please wait... Back up completed We will now backup your new directory server, please wait... Back up the new server completed The rolling upgrade of your LDAP directory server is completed. You can find the primary server backup at /opt/shasta/iplanet/ slapd-ur2y3pa/bak/afterRollingUpgrade/ You can find the new server backup at /opt/shasta/iplanet/slapdur2y3pa1/bak/afterRollingUpgrade/ Please see the file /opt/shasta/scs6.0/rollingUpgradeLdap.log for installation details 390 The .inputparms_rolling.scs has been updated
End of Executing rollingSCS.sh procedure
Note: The script rollingSCS.sh validates the SCS server configuration and populates the file .inputparms_rolling.scs. The parameters set in this file will be used by the upgrade script setup.sh for performing the upgrade. Proceed to Verify SOLID database integrity on page 284
Verify SOLID database integrity 14. Execute the SOLID database integrity check and make sure there are no errors.
411-5221-309 Standard 06.30 March 10, 2010
285
i. Make sure the current working directory is <SCS6.0_ROOT>

# pwd
ii. Execute SOLID database integrity check

<SCS6.0_ROOT>/opt/solidSolaris/bin/solid -x testindex -c <SCS6.0_ROOT>/opt/solidSolaris/database/default

Testing the database index. Warning! Starting roll-forward recovery, please wait ... Warning! Recovery of 1 transactions successfully completed -------------------Mon Nov 12 02:48:51 2007 Bonsai tree: Key id = 1091 Clustering key Bonsai tree is ok. Storage tree: Key id = 191 Clustering key Key id = 193 Key id = 291 Clustering key ... ... Storage tree is ok. Database index has been tested succesfully. Database index is ok.
Important Note: If there are no errors, then proceed to the next section Execute SCS 6.0 Upgrade script - setup.sh on page 286 If the above command returns an error, then SCS 5.0.2 SOLID database backup must be manually copied into <SCS6.0_ROOT>/opt/solidSolaris/database/default. iii. Copy 5.0.2 SOLID database files into <SCS6.0_ROOT>/opt/solidSolaris/database/default
# cp <SCS502_ROOT>/opt/solidSolaris/database/backup/* <SCS6.0_ROOT>/opt/solidSolaris/database/default
Here is an example:
# cp /opt/shasta/scs502/opt/solidSolaris/database/backup/* /opt/shasta/scs6.0/opt/solidSolaris/database/default
GPRS/UMTS
286
iv. Execute SOLID database integrity check again

# <SCS6.0_ROOT>/opt/solidSolaris/bin/solid -x testindex -c <SCS502_ROOT>/opt/solidSolaris/database/default
Here is an example:
If there were any errors in the first integrity check, it should not be seen in the second integrity check. Proceed to Execute SCS 6.0 Upgrade script - setup.sh on page 286
Execute SCS 6.0 Upgrade script - setup.sh 15. Upgrade the SCS Server by running setup.sh upgrade script. Change to the directory where the GGSN SCS 6.0 server software file was un-tarred. Run the setup.sh script to upgrade the SCS server software. iPlanet schema files will be updated by the setup.sh script. Check for the message LDAP schema files updated successfully during the execution of the script. If the automatic update is not successful, the script will prompt the user that the schema file update failed.
# pwd <- verify current working directory /opt/shasta/scs6.0 #./setup.sh
Example: #./setup.sh
Note: When prompted to choose an option pick (U) Upgrade the current SCS Server, and choose the type of upgrade (r - rolling upgrade). The script reads the file .inputparms_rolling.scs, validates the input parameters and displays the parameters to the user. The user must then check the parameters once again, and continue the upgrade by answering y when prompted. In most cases the displayed parameters can be accepted. In case any of the parameters needs to be modified, answer n. Then use vi editor to modify the file .inputparms_rolling.scs from the
411-5221-309
Standard
06.30 March 10, 2010
287
path displayed in the confirmation message. Save the changes and rerun setup.sh. Note: Default settings to install SCS CORBA server in the file .inputparms_rolling.scs is set to n. If SCS CORBA server is installed together with the SCS server, use vi editor to modify InstallCorbaServer to y. Here is an example capture for setup.sh script execution
# ./setup.sh 5.9 is a supported Solaris version Logged in as User root Silent procedure is selected /opt/shasta/scs6.0/install/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled This program will install Nortel Service Creation System. Version SCS GGSNS6.0_SCS6.0(47) ***************************************************************** **** * SCS 6.0 requires IPlanet LDAP 5.1. If you are not running IPlanet * * LDAP 5.1, please upgrade the LDAP server before starting the SCS * * Installation. Please refer to the SCS installation document and * * SCS Release Notes for details on upgrading the Directory Server. * * * * SCS and LDAP require Solaris Recommended Patches. * * Make sure that the latest patches have been installed * * If you are not sure, please abort the setup and check Patch level * * Restart the setup.sh script after checking the patch level * ***************************************************************** **** You have the following options: (C) Create a new SCS Server installation (U) Upgrade the current SCS Server (A) Abort this installation Please enter (C)reate, (U)pgrade or (A)bort? [A]: u <-Type U to select Upgrade (N) Normal Upgrade the current SCS Server (R) Rolling Upgrade the current SCS Server Please enter (N)ormal or (R)olling? [N]: r <- Type r to select rolling upgrade Found the parameters File, /opt/shasta/scs6.0/ .inputparms_rolling.scs oldVersion=GGSNS5.0.2_SCS5.0(14) action=upgrade
GPRS/UMTS
288
The following SCS server(s) are currently installed on this machine: Version SCS GGSNS5.0.2_SCS5.0(14) SCS Domain Server (LDAP Server IP = localhost) SCS Region Server (Region ID = 1) SCS Monitor Server SCS Pull Server (Listening Port = 4321) SCS Log Server (Logging Port = 4322, Accounting Port = 4323) SCS CORBA Server in the same directory as you specified. Reading input Parameters from /opt/shasta/scs6.0/ .inputparms_rolling.scs, Please wait Reading the input parameters and Validating... This is a valid LDAP Path The ldap server is slapd-ur2y3pa1 /opt/shasta/iplanet/slapd-ur2y3pa1/config Ldap port is validated Value from the config File is - 390 Checking if the LDAP Schema files are present LDAP Schema Files are present in /opt/shasta/scs6.0 ================================================================= The Following Parameters are read from the /opt/shasta/scs6.0/ .inputparms_rolling.scs ================================================================= SCS will be upgraded in the following directory : /opt/shasta/ scs6.0 SCS processes will run after the reboot : y SCS Backup Directory is : /opt/shasta/ scs6.0/backup LDAP is installed on this server : y LDAP Port on this Server is : 390 LDAP Path is : /opt/shasta/ iplanet LDAP Server is : slapd-ur2y3pa1 LDAP IP Address is : localhost LDAP Data Migration is : n Is CSV User set on this Server : y Name of the user to collect the CSV Files : pmuser Days CSV Files will be preserved : 4 Install Corba Server on this Server : y Corba Installation directory : /opt/shasta/ scs6.0 Corba file location and name : /opt/shasta/ scs6.0/scs_corba_server.tar Corba Server IP Address : localhost Corba Server ORB IP : default Corba Port : 0 Please check the input parameters and confirm If the input is not right, quit by answering n Change the /opt/shasta/scs6.0/.inputparms_rolling.scs and restart the script if you answer n Do you want to continue (Y/N)? [N]: y <- Type y to proceed. Note, if n is selected, the script will exit. User can modify .inputparms_rolling.scs if required and rerun setup.sh
411-5221-309
Standard
06.30 March 10, 2010
289
User accepted the parameters, continuing with upgrade SCS will be installed in /opt/shasta/scs6.0. Checking the available space ... Required space 127092 Kbytes. Available space 16976450 Kbytes. Found enough space to install SCS. Backup the current SCS database to /opt/shasta/scs6.0/opt/solidSolaris/database/ backup.GGSNS5.0.2_SCS5.0(14) ...... Using /opt/shasta/iplanet as LDAP path Using slapd-ur2y3pa1 as LDAP server **************************************************** * The 5.0 LDAP schema has been changed. * * This Upgrade script will update the schema files * **************************************************** Upgrading the database ... Upgrading your SOLID server to latest version of SOLID FlowEngine 4.0 ... Verifying the current database files ..... [1] 11456 Starting Solid Database Server:.Started Currently running SCS version GGSNS5.0.2_SCS5.0(14). Upgrading domain database schema... Detected Last Upgrade Number: 607 Applying upgrade # 700... Applying upgrade # 701... Applying upgrade # 702... Applying upgrade # 703... Applying upgrade # 704... Applying upgrade # 705... Applying upgrade # 706... Applying upgrade # 707... Applying upgrade # 708... Applying upgrade # 709... Applying upgrade # 710... Applying upgrade # 711... Applying upgrade # 712... Setting Last Upgrade Number to 712 ... Upgrading region database schema... Detected Last Upgrade Number: 603 Applying upgrade # 700... Applying upgrade # 701... Applying upgrade # 702... Applying upgrade # 703... Applying upgrade # 704... Applying upgrade # 705... Setting Last Upgrade Number to 705 ... Calling the upgrade_drop_add_procedure script Apply upgrade_drop_add_procedure-do.sql ... Apply upgrade_drop_add_procedure-reg.sql ... Stopping Solid Database Server:.Stopped
GPRS/UMTS
290
Copying the required files ... *.5001 Selecting next available port... *.5002 *.5002 Selecting next available port...
Idle
Idle Idle
SNMP Proxy using port 5003, SNMP Trap using port 5004. LDAP schema files updated successfully Now stopping and restarting LDAP server slapd-ur2y3pa1 ... To generate CSV formatted accounting data, a user id must be designated as the owner of the generated files. It is recommended that the user id not be the root user. The ownership of any existing CSV formatted accounting data file will also be changed to this user id. The user id, pmuser, already exists and will be used by the SCS Log Server process for CSV generated files. Extracting Corba files, please wait... This program will install SCS Corba Server version SCS GGSNS6.0_SCS6.0(47) SCS Corba Server will be installed in /opt/shasta/scs6.0. Found Domain server installed. New SCS Corba server version matches installed SCS version. Continuing... SCS Corba Server will be installed in /opt/shasta/scs6.0. Checking the available space... Required space 61440 Kbytes. Available space 16885851 Kbytes. Found enough space to install SCS Corba Server. Copying the required files...... SCS Corba Server is now installed. You can use /opt/shasta/scs6.0/bin/SCSCorbaServer to run SCS Corba Server. Updating For Rolling Upgrade... SSL is being disabled The installation logs are saved in /opt/shasta/scs6.0/lib/install/ *.log. UPGRADE IS COMPLETED SUCCESSFULLY The following SCS server(s) are currently installed on this machine: Version SCS GGSNS6.0_SCS6.0(47)
411-5221-309
Standard
06.30 March 10, 2010

SCS SCS SCS SCS SCS SCS You can Server.
291
Domain Server (LDAP Server IP = localhost) Region Server (Region ID = 1) Monitor Server Pull Server (Listening Port = 4321) Log Server (Logging Port = 4322, Accounting Port = 4323) CORBA Server use '/opt/shasta/scs6.0/bin/SCSAdmin start' to run SCS
This completes the example ./setup.sh output. Proceed to Verify SCS upgrade logs on page 291
Verify SCS upgrade logs 16. The SCS upgrade log files are located in the <SCS6.0_ROOT>/lib/install. Run the following commands.
# cd <SCS6.0_ROOT>/lib/install # grep -i error *.log | grep -i solid
The above grep command should NOT return any error lines if there are no solid upgrade errors. If the grep command returns any error lines, please contact Nortel support. 17. Make sure there are no iPlanet installations errors. To check iPlanet installation logs, check file rollingUpgradeLdap.log in <SCS6.0_ROOT>.
Example: # cat /opt/shasta/scs6.0/rollingUpgradeLdap.log | grep "Success Slapd" Look for line:
Success Slapd Added Directory Server information to Configuration Server. AND # cat /opt/shasta/scs6.0/rollingUpgradeLdap.log | grep "LDAP succeeded"
Look for line:

***** Rolling upgrade for LDAP succeeded at <date> *****
18. Verify iPlanet process for SCS 6.0 is running.

# cat /etc/shasta/scs.config | grep LDAPPath # cat /etc/shasta/scs.config | grep LDAPServerName
GPRS/UMTS
292
iPlanet instance ns-slapd process must be running from <LDAPPath>/ <LDAPServerName>.

Example: # cat /etc/shasta/scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet # cat /etc/shasta/scs.config | grep LDAPServerName LDAPServerName=slapd-ur2y3pa1 # ps -aef |grep slapd nobody 2028 1 0 18:13:08 ? 0:03 ./ns-slapd D /opt/shasta/iplanet/slapd-ur2y3pa -i /opt/shasta/iplanet/ slapd-ur nobody 17926 1 0 18:57:30 ? 0:00 ./ns-slapd D /opt/shasta/iplanet/slapd-ur2y3pa1 -i /opt/shasta/ iplanet/slapd-u
19. Make sure critical iPlanet files are installed correctly and the following files exits.
# cat /etc/shasta/scs.config | grep LDAPPath # cat /etc/shasta/scs.config | grep LDAPServerName # cd <path returned by grep LDAPPath> # cd <path returned by grep LDAPServerName> # ls start-slapd # ls stop-slapd # ls restart-slapd Example: # cat /etc/shasta/scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet # cat /etc/shasta/scs.config | grep LDAPServerName LDAPServerName=slapd-ur2y3pa1
# cd /opt/shasta/iplanet # cd slapd-ur2y3pa1 # ls start-slapd start-slapd # ls stop-slapd
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential stop-slapd # ls restart-slapd restart-slapd
293
Proceed to Change the pmuser password on page 293.
Change the pmuser password 20. Change the pmuser password Note: If unix user to collect the Performance data is configured for the first time during the upgrade to 6.0, set the password for this user. Default name to this user is pmuser. Check if the user already exists before the upgrade, this can be done by the command "cat /etc/passwd". If the user exists, do not change the password unless the customer asks for the password to be changed.
# passwd pmuser
Enter the password twice and the password will be set. Proceed to Stop SCS 5.0.2 processes and start SCS 6.0 server processes on page 293
Stop SCS 5.0.2 processes and start SCS 6.0 server processes 21. Determine the SCS 5.0.2 server installation directory and stop SCS 5.0.2 processes. Determine SCS 5.0.2 installation directory:
# cat /etc/shasta/scs.config.bak | grep SCSHead | cut -f 2-d=
Here is an example:
# cat /etc/shasta/scs.config.bak | grep SCSHead | cut -f 2-d= /opt/shasta/scs502
Change directory to the path returned from the above command:
GPRS/UMTS
294
SCS Software Upgrade # cd <SCS502_ROOT> # cd bin
Here is an example:
# cd /opt/shasta/scs502 # cd bin
Stop the SCS server processes.

#./SCSAdmin stop
22. Disable LDAPWatch from SCS 5.0.2. The script is located in <SCS502_ROOT>/bin
# ./LDAPWatch-disable
23. Stop iPlanet process associated with SCS 5.0.2 Determine the current iPlanet home directory
# cat /etc/shasta/scs.config.bak | grep LDAPPath | cut -f 2- -d=
Here is an example:
# cat /etc/shasta/scs.config.bak | grep LDAPPath | cut -f 2- -d= /opt/shasta/iplanet
Change directory to path indicated in the above step. Here is an example:

Determine the directory server name

# cat /etc/shasta/scs.config.bak | grep LDAPServerName | cut -f 2- -d=
Here is an example:
# cat /etc/shasta/scs.config.bak | grep LDAPServerName | cut -f 2- -d= slapd-ur2y3pa
Change directory to directory server name returned in the above step. Here is an example:
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential # cd slapd-ur2y3pa
295
Stop iPlanet directory instance for SCS 5.0.2.

# ./stop-slapd
24. Verify iPlanet directory instance associated with SCS 6.0 is running. The iPlanet directory instance can be determined from:
Here is an example:
# cat /etc/shasta/scs.config | grep LDAPServerName | cut -f 2- -d= slapd-ur2y3pa1
Pass the output of the above command as the grep option to the following ps command. A ns-slapd process must be running with the directory instance.
# ps -aef | grep <LDAPServerName>
Here is an example:
# ps -aef |grep slapd-ur2y3pa1 nobody 17926 1 0 18:57:30 ? 0:00 ./ns-slapd D /opt/shasta/iplanet/slapd-ur2y3pa1 -i /opt/shasta/ iplanet/slapd-u
25. Start SCS 6.0 processes. Determine SCS 6.0 installation directory:
Here is an example:
# cat /etc/shasta/scs.config | grep SCSHead | cut -f 2- -d= /opt/shasta/scs6.0
Change directory to the path returned from the above command:

# cd <SCS6.0_ROOT> # cd bin
Here is an example:
296
SCS Software Upgrade # cd /opt/shasta/scs6.0 # cd bin
Start the SCS server processes.

#./SCSAdmin start
Here is an example:
# ./SCSAdmin start
/opt/shasta/scs6.0/bin/SCSWatch-disable: SCSWatch is already disabled /opt/shasta/scs6.0/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled /opt/shasta/scs6.0/bin/SCSDiskUsageMonitor-disable: SCSDiskUsageMonitor is already disabled /opt/shasta/scs6.0/bin/SCSCleanXmlExportFiles-disable: SCSCleanXmlExportFiles is already disabled [1] 20564 Starting Solid Database Server:.Started [2] 20582 Starting SCS Daemon:.Started [3] 20595 Starting SCS Domain server:........Started [4] 20630 Starting SNMP Proxy:.Started [5] 20640 Starting SCS CORBA Server:.........Started [6] 20666 Starting SCS Region server:......Started [7] 20712 Starting SCS Monitor server:......Started [8] 20741 Starting SCS Trap daemon:......Started [9] 20771 Starting SCS Pull Server:...Started [10] 20791 Starting SCS Log Server:..Started ------------------------------------------Nortel Service Creation System Server Version SCS GGSNS6.0_SCS6.0(47) ------------------------------------------Adding SCSCleanLogcsv first time Added SCSCleanLogcsv to crontab Adding SCSWatch to Crontab for first time. Added SCSWatch to crontab Adding SCSDiskUsageMonitor first time Added SCSDiskUsageMonitor to crontab Adding SCSCleanXmlExportFiles first time Added SCSCleanXmlExportFiles to crontab
End of SCS 5.0.2-> 6.0 Upgrade Procedure Proceed to Enable SCS and iPlanet auto startup scripts: on page 297
411-5221-309
Standard
06.30 March 10, 2010
297
Enable SCS and iPlanet auto startup scripts: 26. Enable SCS and iPlanet auto startup scripts. This way, SCS and iPlanet processes are started automatically on a server reboot. Please follow instructions in SCS and iPlanet auto startup scripts on page 230.
After enabling SCS/ iPlanet startup scripts, return to: If applicable, Optional -Install SSL Package on page 297 or Proceed to Table 16 Upgrade SCS 5.0.2 to SCS 6.0 on same serveron page 166
Optional -Install SSL Package 27. Optional - Installation of the SSL Package. This step is required if: SSL was enabled on SCS 5.0.2 and customer has purchased SCS 6.0 SSL software. Verify if the following checkpoint was valid for the serverDetermine if SSL is enabled on the SCS server on page 62 The customer wants to install and enable the SSL. Note: If SSL is enabled on the SCS Server, the SCS Client machine should also be SSL enabled. If client is not SSL Enabled, the SCS Client will not come up. a. Login as root on to the SCS server. Make sure the login shell is csh. Please refer to Basic system settings required on the SCS: on page 200 to verify if the current login shell is csh
# cd <SCS6.0_ROOT>
b. Insert the SSL CD. Then find out the CD mount point using df -k
# df -k Here is an example: # df -k ... <-Other mounted partitions /vol/dev/dsk/c0t6d0/gssl0060 330000 330000 cdrom/gssl0060
100%
GPRS/UMTS
298
c. Copy the sslpkg.tar.Z from the SCS SSL CD to the present directory, uncompress and then untar the SSL package file.
# cp /cdrom/gssl0060/SSL/sslpkg.tar.Z <SCS6.0_ROOT> # uncompress sslpkg.tar.Z # tar -xvf sslpkg.tar
d. Change the execution permission of setup.sh.

e. Execute the setup.sh

# ./setup.sh
Here is an example:
# ./setup.sh This program will install SCS SSL version SCS GGSNS6.0_SCS6.0(42) Please specify the directory for SCS installation [/opt/ shasta/scs6.0]: <-hit enter to select default Matching SCS version found - SCS SSL will be installed in /opt/shasta/scs6.0. Copying the required files...... SCS SSL is now installed. Refer to SCS documentation for instructions on enabling SSL.
The above step will install the SSL package. f. If SSL was already enabled on the SCS server prior to the upgrade, you can retrieve the backup copies of the SSL certificates into the new SCS server installation directory/etc. Verify SCS Upgrade Prechecks on page 146 and see if SSL was enabled prior to the SCS upgrade. If SSL was not enabled prior to the SCS upgrade, then please refer to NTP Nortel GGSN Provisioning Procedures : 411-5221-927 for steps to create SSL certificates and install on the SCS server. If SSL was enabled prior to the upgrade, then copy sslrsa.crt.BACKUP and trusted.txt.BACKUP to the newly upgraded SCS installation directory/etc.
If previous SCS version is SCS 5.0.2 # cp <SCS502_ROOT>/etc/trusted.txt <SCS6.0_ROOT>/etc # cp <SCS502_ROOT>/etc/sslrsa.crt <SCS6.0_ROOT>/etc
g. Enable the SSL

# cd <SCS6.0_ROOT>/bin
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential # ./SCSAdmin SSLEnable on
299
h. Restart the SCS Processes to enable the SSL

i. Verify SCS processes are running and SSL is enabled

# ./SCSAdmin status
Proceed to Table 16 Upgrade SCS 5.0.2 to SCS 6.0 on same serveron page 166
GPRS/UMTS
300
Modify partition level file permissions
13
In some cases, the partition level file permissions: read, write, execute file permissions are not set for non-root users. This results in unix command execution failure for non-root users. This procedure is required when /opt is a unique partition. Perform df -k and verify if /opt is a mounted partition. Example:
# df -k
Filesystem /dev/dsk/c1t0d0s0 /proc fd mnttab swap swap /dev/dsk/c1t1d0s0 kbytes used avail capacity Mounted on 61522236 26682002 34225012 44% / 0 0 0 0% /proc 0 0 0 0% /dev/fd 0 0 0 0% /etc/mnttab 14639928 16 14639912 1% /var/run 14675816 35904 14639912 1% /tmp 70592505 3549768 66336812 6% /opt
Here is an example of the errors in case the partition level file permissions are not set correctly for non-root users. Executing pwd will result in error.
cd /opt pwd pwd: cannot determine current directory!
Non-root users will not be able to execute corbashell.sh

cd /opt/shasta/scs/corba/examples/java ./corbashell.sh /opt/shasta/scs/proc/spm.ior Segmentation Fault - core dumped
Here are the steps to resolve the directory level file permissions: 1. Login to the SCS server as root user. 2. Determine the current SCS home directory
3. Change directory to path indicated in the above step. 4. Stop SCS server processes
bin/SCSAdmin stop
411-5221-309
Standard
06.30 March 10, 2010
301
5. Disable LDAPWatch
bin/LDAPWatch-disable
6. Determine the current iPlanet home directory

9. Change directory to directory server name returned in the above step. 10. Stop iPlanet process.
./stop-slapd
11. Change directory one level up

cd ../
12. Stop iPlanet process and admin process

./stop-admin
13. Try unmounting /opt (Location where SCS is installed)

umount /opt umount: /opt busy
14. If umount fails indicating busy, run the following commands:

cd / fuser /opt /opt: umount -f /opt
15. Make a note of directory permissions for /opt

ls -al /opt
Here is an example:
ls -al /opt total 4 drwx-----2 root drwxr-xr-x 26 root
other root
512 Nov 16 18:00 . 512 Nov 22 10:21 ..
GPRS/UMTS
302
16. Modify directory permissions

chmod 755 /opt pwd /
17. Mount /opt (mount point where SCS is installed)

mount /opt
18. Determine the current iPlanet home directory

21. Change directory to directory server name returned in the above step. 22. Start iPlanet process and admin process Here is an example:
cd /opt/shasta/ipl* cd slapd* ./start-slapd cd ../ ./start-admin
23. Determine the current SCS home directory

24. Change directory to path indicated in the above step. 25. Start SCS server processes
bin/SCSAdmin start
26. Enable LDAPWatch

bin/LDAPWatch-enable
27. Login to the SCS server as non-root user. Change directory to /opt and execute basic unix commands
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential cd /opt pwd df -k /opt
303
28. Execute corbashell.sh as non-root user.
Return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
GPRS/UMTS
304
SCS Post-upgrade / Rollback checklists
14
The purpose of this section is to monitor the health of the SCS Server after the upgrade, evaluate the SCS server, and make sure the SCS upgrade is successful. These check points should be evaluated every day after the upgrade for 7 days. The SCS server is functioning normally, if all the check points can be verified successfully. Please contact Nortel support team, in case any of the check points fail. The following checkpoint items summarized in Table 20 must be completed in their entirety after the upgrade is over. Also, all data captured from the process must be retained for one week after the upgrade has been completed. Before proceeding with the check point verification, make sure there are no GGSNs that are out of sync before the upgrade. If there are any GGSNs that are out of sync before the upgrade, those GGSNs will remain as out of sync after the upgrade. The purpose of these checks are to make sure that the health and status of the SCS Server and GGSNs will be the same before and after the upgrade. The check point items are executed on SCS Server, SCS Client, and GGSN. Root user access is required for executing the items on the SCS Server. On the SCS Client it is required to log in as device_owner used id and also as any of the ISPs for some items. Userid admin should be used for the GGSN.
Post Upgrade checkpoint #5 All items in Table 20 must be confirmed within 7 days after the upgrade. All interaction with the GGSN/SCS must be logged to a console file, and retained as part of procedural records.
Table 20 Upgrade readiness checkpoint #5 every day after the upgrade for 7 days Item 1 Description Check if the LDAP is running or not, and check if LDAP console can be started.
sheet 1 of 4
411-5221-309
Standard
06.30 March 10, 2010
SCS Post-upgrade / Rollback checklists 305
Table 20 Upgrade readiness checkpoint #5 every day after the upgrade (continued) for 7 days (continued) Item 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 Description Check if the SCS Processes are running or not. Log on to the SCS Client, and check if the help files are available. Verify Basic Configuration. Reset SNMP Trap Port on SCS client. Note: This step needs to be executed only once. Verify if SCS only configuration can be done. Verify if GGSN configuration changes can be made. Trim Domain behavior clarification for GGSN 4.1.1 and GGSN 6.0. Note: This step needs to be executed only once. Verify Accounting data is collected and viewable. Verify Monitoring. Verify Alarms. Verify the Disk space. Verify the swap space. Note: This step needs to be executed only once. Verify tftp is running. Note: This step needs to be executed only once. Verify if the CSV purging mechanism is working fine. Check /var/mail for any errors with monitoring cron jobs. Execute command prstat. Configure SCS 6.0 periodic backup. Note: This step needs to be executed only once.
sheet 2 of 4
Work Instruction Checkpoint 5 item 2, page 312 Checkpoint 5 item 3, page 313 Checkpoint 5 item 4, page 313 Checkpoint 5 item 5, page 315 Checkpoint 5 item 6, page 316 Checkpoint 5 item 7, page 318 Checkpoint 5 item 8, page 318 Checkpoint 5 item 9, page 323 Checkpoint 5 item 10, page 323 Checkpoint 5 item 11, page 324 Checkpoint 5 item 12, page 325 Checkpoint 5 item 13, page 325 Checkpoint 5 item 14, page 326 Checkpoint 5 item 15, page 327 Checkpoint 5 item 16, page 329 Checkpoint 5 item 17, page 329
GPRS/UMTS
306
Table 20 Upgrade readiness checkpoint #5 every day after the upgrade (continued) for 7 days (continued) Item 18 19 20 Description Check if there are multiple Patch Servers running on the SCS Server. Perform patch Sync States Note: This step needs to be executed only once. Patch Verification for G501_FF01435785ACT_INF: Cabcharge L2TP Authentication Feature. Note: This checklist needs to be executed only once. 21 Patch Verification for G501_01450778ACT_IFMGR: Increase the MTU Size of Gn IP Interface on GELC feature Note: This checklist needs to be executed only once. 22 Patch Verification for G501_FF01567650ACT_IPCMC: TCP MSS Clamping feature Note: This checklist needs to be executed only once. 23 Patch Verification for G501_FF01385577ACT_ERCMC: DCCv2 Envelope Reporting Feature Note: This checklist needs to be executed only once. 24 Patch Verification for G501_FF01368038ACT_INF: DCCv2 Customization Essentials Feature Note: This checklist needs to be executed only once. 25 Patch Verification for G501_FF01385579ACT_DCCCMC, G501_FF01385579ACT_DCCSSP: Parking Meter Charging Enhancement Feature Note: This checklist needs to be executed only once. 26 Patch Verification for G501_FF01510131ACT_CPM: Consecutive Parking Meter Feature Note: This checklist needs to be executed only once. 27 Patch Verification for G501_FF01369144ACT_PPDCMC: Dual Coupon Feature Note: This checklist needs to be executed only once.
sheet 3 of 4
411-5221-309
Standard
06.30 March 10, 2010
Table 20 Upgrade readiness checkpoint #5 every day after the upgrade (continued) for 7 days (continued) Item 28 Description Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration Note: This checklist needs to be executed only once. 29 Patch Verification for G501_01407739ACT_INF and G501_01595094AACT_AAA Note: This checklist needs to be executed only once. 30 Patch Verification for G411_01339974AACT_GTPACCT - SGSN Change Partial Billing verification. Note: This checkpoint is valid only for GGSNs upgraded from GGSN 4.1.1 to GGSN 6.0 only. Note: This checklist needs to be executed only once.
sheet 4 of 4
GPRS/UMTS
308
Upgrade readiness checkpoint #6after it is determined the SCS server will not be rolled back to Solaris 8 The checkpoint items mentioned in Table 21 needs to be performed after sanity execution and it is determined that the SCS server will not be rolled back to Solaris 8 or the previous version of SCS server.
Table 21 Upgrade readiness checkpoint #6 after it is determined the SCS server will not be rolled back to Solaris 8 Item 1 2 Description Recreate disk mirrors. Note, this procedure is application only if the SCS server was disk mirrored prior to the SCS server upgrade. Only if applicable, modify the SCS server hostname if it was modified while executing Upgrade readiness checkpoint #3 2 days prior to upgrade on page 44 Work Instruction Checkpoint 6 item 1, page 343 Checkpoint 6 item 2, page 343 X
411-5221-309
Standard
06.30 March 10, 2010
Checklist work instructions and details These sub-sections are referenced in Table 20 . They provide details for item checklists that require it. Post Upgrade checkpoint #5 (everyday for 7 days after the upgrade) 5
Checkpoint 5 item 1 Check if LDAP is running or not and check if LDAP console can be started.
This item is executed on the SCS Server with root access From the SCS Server, input the following command to verify the SCS directory server is running and directory server console can be started. If the process is not running or the console cannot be started, contact your next level of support before proceeding. a. Verify iPlanet directory instance associated with SCS 6.0 is running. The iPlanet directory instance can be determined from:
Here is an example:
# cat /etc/shasta/scs.config | grep LDAPServerName | cut -f 2- -d= slapd-ur2y3pa
Pass the output of the above command as the grep option to the following ps command. A ns-slapd process must be running with the directory instance.
# ps -aef | grep <LDAPServerName>
Here is an example:
# ps -aef |grep slapd-ur2y3pa nobody 29087 1 0 14:18:25 ? 0:03 ./ns-slapd -D /opt/shasta/iplanet/slapd-ur2y3pa -i /opt/shasta/ iplanet/slapd-ur
If the above ps command does not return a result, then start iPlanet directory server instance. Determine the current iPlanet home directory
GPRS/UMTS
310
Here is an example:
# cat /etc/shasta/scs.config | grep LDAPPath | cut -f 2- -d= /opt/shasta/iplanet
Change directory to path indicated in the above step. Here is an example:

Determine the directory server name

Here is an example:
# cat /etc/shasta/scs.config | grep LDAPServerName | cut -f 2- -d= slapd-ur2y3pa
Change directory to directory server name returned in the above step. Here is an example:
# cd slapd-ur2y3pa
Start the iPlanet directory instance for SCS 6.0.

# ./start-slapd
b. Verify iPlanet admin server process is running. Process ns-httpd must be running.
# ps -aef | grep admin | grep -v grep root 28873 28741 0 14:17:49 ? opt/shasta/iplanet/admin-serv/config root 28875 28873 0 14:17:50 ? opt/shasta/iplanet/admin-serv/config root 28741 1 0 14:17:39 ? opt/shasta/iplanet/admin-serv/config
0:00 ns-httpd -d / 0:01 ns-httpd -d / 0:00 ./uxwdog -d /
If the iPlanet admin process is not running, start the admin process. First, determine the iPlanet installation directory using:
Here is an example:
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential /opt/shasta/iplanet
311
Change directory to the path returned by the above command. Here is an example:
# cd /opt/shasta/iplanet #./start-admin
c. Login to iPlanet administration console. This requires either an xterm (to the server) or a directly connected monitor to the server. iPlanet admin server port is assigned 33611. To login to the iPlanet console from xterm: Determine the iPlanet installation directory.
Change directory to the path returned by the above command. Here is an example:
Note: Export environment variable DISPLAY before launching iPlanet console

Example:
In C shell:
# setenv DISPLAY <YOUR_PC_IP>:0.0 # ./startconsole & Username: admin (unless modified by user) Password: admin Administration URL: http://scshost.domain:33611
Note: Make sure that the slapd process and ns-httpd are running, and directory server console can be started. Note: If you are upgrading to SCS 6.0, you will see two directory server instances on the iPlanet console. Return to Upgrade readiness checkpoint #5 every day after the upgrade for 7 days on page 304
GPRS/UMTS
312
Checkpoint 5 item 2- Check if SCS is running
This item is executed on the SCS Server with root access Verify the status of all the SCS process. Execute the following from the SCS server /bin directory. If any of the processes are not running, contact your next level of support before proceeding. Check the SCS 6.0 installation location:
Example: # cat /etc/shasta/scs.config | grep SCSHead SCSHead=/opt/shasta/scs6.0 <SCS6.0_ROOT> = /opt/shasta/scs6.0
Make a note of SCSHead. To verify SCS server process status:

# cd <SCS6.0_ROOT>/bin # ./SCSAdmin status
Here is an example:
# cd /opt/shasta/scs6.0/bin # ./SCSAdmin status Running Solid Database Server since Mar_24 (pid=14935) Running SCS Daemon since Mar_24 (pid=14953) Running SCS Domain Server since Mar_24 (pid=14965) Running SNMP Proxy since Mar_24 (pid=15056) Running SCS Region Server since Mar_24 (pid=15086) Running SCS Monitor Server since Mar_24 (pid=15112) Running SCS Trap Daemon since Mar_24 (pid=15138) Running SCS Pull Server since Mar_24 (pid=15191) Running SCS Log Server since Mar_24 (pid=15211) Running SCS CORBA Server since Mar_24 (pid=15062) SCS Provisioning is enabled SSL is not enabled on present servers All SCS server processes are running. Version SCS GGSNS6.0_SCS6.0(43)
If any of the SCS processes are not running, the output of the above command will identify the processes that are not running with a comment ! Not Running. Please contact next level support. Return to Upgrade readiness checkpoint #5 every day after the upgrade for 7 days on page 304
411-5221-309
Standard
06.30 March 10, 2010
Checkpoint 5 item 3- Verify SCS Client is functional
This item is executed on the SCS Client. Log in on the SCS Client GUI, connected to the SCS Server as device_owner userid Open the menu item Help, About SCS... and ensure the version is as expected. Open the menu item Help, HelpTopics... and ensure the help files are installed.
Return to Upgrade readiness checkpoint #5 every day after the upgrade for 7 days on page 304
Checkpoint 5 item 4Verify the basic configuration. Reset SNMP Trap Port on SCS client
This item is executed on the SCS client, after the Item 3. Ensure all configured regions are visible Double click on each region and verify: All configured devices are in each region Make sure all active devices in each region are in sync. This is shown with a green icon followed by the GGSNs node name followed by (In Sync) as in the following illustration
If there are any session errors for any device, and these session errors are not existing before the upgrade, Please contact the Nortel next level of support. Note which devices are not in sync (e.g., disconnected, or administratively down) and compare to the SCS pre-check conditions or since the last check point verification.
Reset SNMP Trap Port on SCS client: Below are the steps to verify and set SCS Trap Daemon Port and SNMP Proxy Port on the SCS client.
GPRS/UMTS
314
Login to the SCS server as root user. Change directory to SCS 6.0 server log directory:
# cd /opt/shasta/scs5.0/log/servers # more SCSTrapDaemon.log | grep "Trap port" Here is an example capture: # more SCSTrapDaemon.log | grep "Trap port" 18-May-2006 21:40:48 395 INFO Trap port: 5002
Make a note of the Trap port. In the above example, Trap port is set to port number 5002.
# pwd # /opt/shasta/scs5.0/log/servers # more snmpproxy.log | grep Proxy Here is an example capture: # more snmpproxy.log | grep Proxy [Thu May 18 21:39:16 2006] SNMP Proxy started, port : 5003
Next, verify SNMP Proxy port on the SCS server. From the SCS server log directory:
Make a note of the SNMP Proxy port. In the above example, SNMP Proxy port is 5003. Launch SCS 5.0 client and login as device_owner ISP. From the File menu, modify SCS Trap Daemon Port and SNMP Proxy Port if the values set are different from that on the SCS server (above steps). File-> SCS Configuration...-> SNMP Properties SCS Trap Daemon Port-> Set it to port number returned from the Trap port output on the SCS server. SNMP Proxy Port-> Set it to port number returned from the SNMP Proxy port output on the SCS server. Click OK to commit the changes. Login as 'admin' user on all the GGSN's in the SCS region and perform:
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential show spmaddr
Verify SNMP Trap port matches the SCS Trap Daemon Port that was set on the SCS client.
Here is an example capture on the GGSN.

ssg-27(SSU)# show spmaddr SCS Region Servers: Order Address Route via interface port ------------------------------1 47.104.70.77 mgmt-eth0
SNMP Trap ----------5002
Checkpoint 5 item 5- Verify the SCS configuration
This item is executed on the SCS Client, after the Item 4 Click on the ISP icon, and create a dummy ISP. Note: Do not assign the ISP to any Device. If it is assigned to any device, and if the ISP is deleted, the device will need a resync. Creating an ISP checks the communication between SCS and LDAP. If the ISP can be created then the communication between LDAP and SCS is fine. To create the ISP, click on Add button and type in the name and click ok.Verify that the user and ISP can be created, modified, and deleted. Open the Users manager, and create/delete a dummy user. Creating a user does not send information to the GGSN.Click on Add and to add the user. Make sure to delete the user and ISP created to check. Refer to GGSN Procedure Reference Manual (NTP 411-5221-927) for details to add/ modify/delete users.
GPRS/UMTS
316
Checkpoint 5 item 6- Verify the GGSN Configuration
This check point is executed on both SCS Client and GGSN. Note: This item should be repeated at least on one GGSN per each load the SCS is managing. For example, if the SCS is managing a 4.0.1, and 4.1 GGSN, the item has to be repeated for one GGSN on each of these loads. On the SCS Client: Verify ability to make GGSN configuration changes (Refer to GGSN Procedure Reference Manual NTP 411-5221-927 for more details) Log out (as device owner) Log in as an ISP Owner Create a service policy: Double click on Service Policies
Click on the Security icon under Service Policy
Click Add... to add a new policy Provide a policy name (e.g test) and click OK
411-5221-309
Standard
06.30 March 10, 2010
Accept the default policy by clicking OK. Here is an example of a default security policy rule.
Save the policy as a shared security policy by clicking OK
Note: Do not assign this Service Policy to a Subscriber Template as this will cause traffic disruption. Log on to the GGSN CLI Once the policy is created on the SCS, it can be seen on the ISPs GGSNs with the show policy command. On the GGSN enter the command show policy. As an example, where the ISP name is ssg20-isp-gi:
shasta-20(SSU)# show policy
Policy -----ssg-20-isp-gi.test.sec PolicyID -------2 Status ------On disk
The policy can be deleted from the SCS Client by selecting its row and selecting Delete
GPRS/UMTS
318
Verify the policy is no longer listed via the show policy command on the affected GGSN.
Checkpoint 5 item 7- Trim Domain behavior clarification for GGSN 4.1.1 and GGSN 6.0
In GGSN 4.0.1/ GGSN 4.1.x, when MSISDN under APN anonymous RADIUS authentication is selected (under Access tab) and Trim Domain option on the RADIUS Profile is not selected, the username sent in the RADIUS Access Request is the MSISDN number only (domain name is not appended with the username). With the above configuration, RADIUS server needs to be provisioned with the MSISDN username without the domain name. In GGSN 6.0, when MSISDN under APN anonymous RADIUS authentication is selected (under Access tab) and Trim Domain option on the RADIUS Profile is not selected, the username sent in the RADIUS Access Request is the MSISDN appended with the domain name. With this configuration, the RADIUS server needs to be provisioned with the MSISDN username appended with the domain name; for example: 41794938028@subdomain.com
Checkpoint 5 item 8- Verify Accounting data
This item is executed on the SCS Server and SCS Client On the SCS Server: Verify Accounting data (performance statistics) is collected and viewable. Make sure you have the entry for LogUser in the /etc/ shasta/scs.config file. The value for the label LogUser will be pmuser by default, unless any other name is given during the upgrade. There will not be any entry to this label in the /etc/shasta/scs.config file, if it is answered N to the question Do you want to designate a user id for the CSV formatted data.? during the upgrade.
411-5221-309
Standard
06.30 March 10, 2010
On the SCS Client: Create an accounting profile, or use an existing accounting profile Note: It is expected that a pre-existing accounting profile will be used, but the steps to create a basic accounting profile are provided for completeness. For more information on accounting profiles and accounting elements, see the Nortel GGSN User Guide, 411-5221-926. If the Accounting profile already exists skip creating the new accounting profile, and proceed to checking the LOGS on Open the device manager and double-click on the appropriate device. on page 321. Follow the procedure from the step Open device Manager... if the existing profile can be used. To create an accounting profile, select the access properties
Select Accounting Profiles from the list of access properties Select Add... and create a profile named test, for instance
Select ISP and OK This opens the Accounting Profile dialog Select ISP IP Stats and Edit
GPRS/UMTS
320
Select New and create an accounting element named test_isp, Select ISP IP Stats for the Type from the drop down
list and box as shown in the above figure, and select OK Select the new element and OK
Click on the created Profile, test_isp as shown in the above figure and Click on OK.
411-5221-309
Standard
06.30 March 10, 2010
This should create a row in the accounting profile with the test_isp accounting element
Open the device manager and double-click on the appropriate device. Switch to the Access Properties tab
On the ISP Accounting Profile, select the newly created test accounting profile. Select OK to apply to the device Allow accounting data to accumulate for several intervals (each interval is 15 min) Open the Logs manager by double clicking on the Logs icon
Select the region and device appropriate for the ISP Select the Accounting tab on the Log Manager
GPRS/UMTS
322
Select an accounting element (e.g. ISP), and verify accounting data is visible
Go back to the SCS Server Verify the *.csv files are present in the <SCS_ROOT>/log/preside/ regionX/deviceY directory. Where X is the region # in which the device is configured and Y is the device #.
411-5221-309
Standard
06.30 March 10, 2010
Checkpoint 5 item 9- Verify Monitoring
This item is executed on the SCS Client Select the GGSN of interest in the Device Manager Right click, and select Monitor->Chassis The graphical representation of the GGSN should be shown with all hardware displayed with appropriate status LEDs Select the HistStats tab on the Monitoring Window Select a stat to poll (e.g. Mem) Select an interval to poll, and select Start A tabular representation should show successive polls from the GGSN.
Checkpoint 5 item 10- Verify Alarms
This item is executed on the SCS Client Select the Alarms icon
Navigate to the GGSN of interest in the alarm manager Select the GGSN View the Current Alarms The Current Alarms should have a list of various alarms for the GGSN, as alarms are created as part of the GGSN restart process. Note: It is possible to create new alarms by disabling ports, or removing cards. However, these tests can interfere with traffic. When the
GPRS/UMTS
324
disturbance is introduced to the GGSN, the alarm should be displayed on the Current Alarm list. Return to Upgrade readiness checkpoint #5 every day after the upgrade for 7 days on page 304
Checkpoint 5 item 11- Check the Disk space
This item is executed on the SCS Server. # df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 721230 574802 88730 87% / /dev/dsk/c0t0d0s3 962134 824324 80082 92% /usr /proc 0 0 0 0% /proc fd 0 0 0 0% /dev/fd mnttab 0 0 0 0% /etc/mnttab swap 1916712 16 1916696 1% /var/run /dev/dsk/c0t0d0s6 3971950 3209683 722548 82% /opt /dev/dsk/c0t0d0s5 480815 122193 310541 29% /software /dev/dsk/c0t0d0s4 480815 1742 430992 1% /tmp The output displays the following fields as follows -file system name -total space allocated in file system (in Kbytes) -amount of space allocated to existing files -total amount of space available for the creation of new files -percentage of space that is currently allocated -the mount point SCS automatically shuts down if the disk usage is more than 99% for the /, <SCS_ROOT> and /var, partitions. (<SCS_ROOT> is the root directory for the SCS for example, /opt/shasta) If the disk space is above 90%, please follow the customer specific Disk Management procedures to clean up the disks.
411-5221-309
Standard
06.30 March 10, 2010
Checkpoint 5 item 12- Verify the Swap space
This item is executed on the SCS Server. The "swap -s" command reports total and free space for each of the swap partitions that have been configured on SCS server. # swap -s total: 488488k bytes allocated + 982328k reserved = 1470816k used, 1853920k available The above command shows the swap space. The swap space is the last number is kb, which is 1853920 in the above snapshot. Make sure that the swap partition has more than 1408M bytes of memory space for large deployments, which is 1441792kb.
Checkpoint 5 item 13- Verify tftp is running
This item is executed on the SCS Server. Verify that the tftp process is running in idle state on the SCS server:
# netstat -a | grep tftp
Here is an example:
# netstat -a | grep tftp *.tftp Idle *.tftp Idle
or Executing <SCS_ROOT>/lib/install/enable_tftp which would indicate that tftp is already enabled.

# cat /etc/shasta/scs.config | grep SCSHead # cd <Path returned for SCSHead>
GPRS/UMTS
326
SCS Post-upgrade / Rollback checklists # lib/install/enable_tftp
If tftp is not running, run the following command to enable tftp service.
# cat /etc/shasta/scs.config | grep SCSHead # cd <Path returned for SCSHead> # lib/install/enable_tftp
If tftp service is unable to start, please contact nortel next level of support.
Return to:Upgrade readiness checkpoint #5 every day after the upgrade for 7 days on page 304
Checkpoint 5 item 14- Purging of CSV files
This item is executed on the SCS Server. SCS Server schedules a cron job, to purge the CSV files. If customer does not have PWI/W-NMS to collect the CSV files, or any other 3rd party tool to collect performance statistics, make sure the CSV files are not getting accumulated. SCS schedules a cron job to clear all the CSV files which are older than x days, and x is configured during the upgrade/install. The default is 4 days. All the CSV files which are older than this x days should be removed by the cronjob. The SCSCronCleanLogcsv.txt file in the <SCS6.0_ROOT>/bin will show the value for the x and how the cronjob is scheduled. Here is an example of the above file 59 11 * * * ksh -e '/opt/scs/bin/SCSCleanLogcsv.ksh 4' Where the last digit in the above file is the value of x. Verify the crontab entry set in the SCS server using:
crontab -l
411-5221-309
Standard
06.30 March 10, 2010
Check the <SCS_ROOT>/log/preside/* directories and make sure that the CSV files are correctly purged. Every time the cronjob removes any files, it will write a log and the log file will be located under <SCS_ROOT>/log/ preside. A Sample log file will be cleanlogcsv.out.2004Oct131159. Please check this file and make sure the cronjob will only delete the CSV files that are older than x days. Return to Upgrade readiness checkpoint #5 every day after the upgrade for 7 days on page 304
Checkpoint 5 item 15- Check for errors in the /var/mail for cron command failure mails.
This item is executed on the SCS Server. SCS schedules cron jobs: To monitor the SCS processes, LDAP processes, Disk usage monitoring, and for the CSV purging. For example, SCSWatch cron job will restart the SCS processes if they are not running, and the LDAPWatch will restart the LDAP processes if LDAP is not running, All these cron jobs are scheduled for the root user. If there is any error in executing these cron jobs, an email will be sent to the user root, on the Solaris server. In order to make sure there are no errors, please check the /var/mail for mails to root. The command mailx can be used to navigate through the emails for root user.
# cd /var/mail # mailx
Each message is assigned a mail id. Here are some navigation commands: mailx - to open the command line email program To go to the last email - Type $ and hit enter To go to the next email - Type n and hit enter To exit mailx - Type exit
GPRS/UMTS
328
Enter the command mailx.

# mailx
Go the last email. Type $ and hit enter. Here, make a note of the Massage number. From the last message number, subtract 10. Type the number (last message number - 10) and hit enter. Identify the emails, that were sent after the upgrade or since the last check point verification. Check these emails for any error messages or check if the SCS processes or the LDAP processes are started by the SCSWatch or LDAPWatch cron jobs. If LDAP or SCS is being restarted by the cron job, please contact the Nortel Support team. If the LDAP and SCS were restarted after the SCS rebooted, and you are able to use the SCS GUI without problems, messages of this type can be ignored; otherwise, contact the Nortel Support team. Type exit to exit out of mailx program.
Here is an example SCSWatch email to the root user

From root Mon Oct 4 06:23:04 2004 Date: Mon, 4 Oct 2004 06:23:03 -0500 (CDT) From: Super-User <root> To: root Subject: Output from "cron" command Your "cron" job on server602 /opt/shasta/bin/LDAPWatch
produced the following output:

LDAP Admin Server is off, restarting it now. Warning! task_eval_init(): unable to set User/Group baseDN Netscape-Administrator/4.2 B2001.300.0126 startup: listening to http://server602, port 30270 as root warning: daemon is running as super-user LDAP Server (slapd-server602) is off, restarting it now.
411-5221-309
Standard
06.30 March 10, 2010
Checkpoint 5 item 16- Execute the command prstat
For details on the prstat command, see System Command prstat on page 157 Return to Upgrade readiness checkpoint #5 every day after the upgrade for 7 days on page 304
Checkpoint 5 item 17- Configure SCS 6.0 periodic backup
The server can be configured to perform a automated periodic backup at regular intervals. Please refer to SCS Periodic Backup setup option on page 225 for details. This is an optional step.
Checkpoint 5 item 18: Check if there multiple Patch Servers running on the SCS Server
Note: This step needs to be executed once. The step need not be executed for seven days following the upgrade. Logon to the SCS Client as device_owner Click on File and then SCS Configuration... Click on Server Properties Tab. The following window will open.
Check if there are multiple Patch Servers on your SCS Server as shown in the above picture. If there is only one patch server, unlike in the above example, this step can be skipped. If there are multiple patch servers, remove the in correct one. Patch Server IP address should be same as the physical IP address of your
GPRS/UMTS
330
SCS Server. In the above example, the Patch server in the row 6 is incorrect. Delete this Patch server. Click on the Patch server to be removed and click on delete button as shown in the following picture.
Click on Yes to delete the patch server. The SCS GUI only allows to delete the Patch server, if there are multiple patch servers. There must always be one Patch server. Also, if the Patch server IP address is to be edited for some reason, the change is only allowed when there is only one Patch server. Before editing the details for the Patch server, remove the multiple Patch servers, if existing.
Checkpoint 5 item 19Perform patch Sync States
Perform a patch Sync States to avoid any synchronization mismatch in patch information between the SCS server and GGSN.
411-5221-309
Standard
06.30 March 10, 2010
a. Log in to the GGSN with a user with SSU privilege. b. Issue the command monitor log. Event logs related to patching will be printed on the terminal. c. Log in to the SCS client as device_owner user. d. Click the Patch icon in the left pane. This will open Patch Manager. e. Click on the Device tab. f. On the left pane, click on the region name under Region. g. Double click on the GGSN. This will open Patch Device Information window. h. Click Sync States button. This check will push the patching information on the SCS server to the GGSN. When the patch information on the SCS server and GGSN are in synchronization, no new patches will be applied or unapplied here. i. Wait till the logs on the GGSN telnet terminal stops, then proceed to the next step. j. Repeat steps Step g through Step i for the other GGSNs in the region. Return to Upgrade readiness checkpoint #5 every day after the upgrade for 7 days on page 304
Checkpoint 5 item 20Patch Verification for G501_FF01435785ACT_INF: Cabcharge L2TP Authentication feature
User must execute this checkpoint if the patch G501_FF01435785ACT_INF was activated and Anonymous RADIUS Authentication is selected on the connection ISP(s) APNs. SCS script SCSUpgradeL2TPCabcharge.sh packaged with the SCS server can be used to automate APN configuration modification so that the feature is migrated to SCS 6.0. The script updates the APNs on selected ISPs with the following settings: On the APN, under Anonymous RADIUS Authentication i. If MSISDN or User Name was selected from SCS 5.0.1, the follow options are selected after script execution: - Add APN as domain
GPRS/UMTS
332
- Override Mobile supplied username ii. If Username was set with string MSISDN from SCS 5.0.1, then the radio button option MSISDN is selected after script execution. iii. If Username was set with string IMSI, then the radio button option IMSI is selected after script execution. Execute the script: SCSUpgradeL2TPCabcharge.sh to update the APNs. - Change directory to <SCS6.0_ROOT>/bin
# cd /opt/shasta/scs6.0/bin # ./SCSUpgradeL2TPCabcharge.sh
Here is a snapshot of the user prompts:

# ./SCSUpgradeL2TPCabcharge.sh ************ SCS UPGRADE L2TP CABCHARGE ********* ...info about the script ************************************************* Do you want to continue? (Y)es or (N)o: y <-Enter y if patch G501_FF01435785ACT_INF was activated in GGSN 5.0.1 The upgrade L2TP Cabcharge is starting... G501_FF01435785ACT_INF patch rule checking...
ISP_ID --3 4 5 6
ISP_NAME -----isp-ga isp-internet isp-blackberry isp-data
Enter ISP IDs to upgrade [all]:all <-hit enter to select all to update all ISPs, or enter ISP ID to select specific ISP
The upgrade will continue with below information: Selected ISP IDs: 3 4 5
411-5221-309
Standard
06.30 March 10, 2010
6 Do you want to continue? (Y)es or (N)o: y <- enter y to proceed 17-Apr-2008 13:48:01 794 INFO table.client.disconnectAll: 127.0.0.1:1099/1 Upgrade L2TP Cabcharge has completed successfully The upgrade proccess log file path: /opt/shasta/scs6.0/log/ servers/SCSUpgrageAPN/UpgradeL2TPCabcharge041708_134643.log
- Details of the APNs being modified can be found the log file indicated at the end of the script execution. - Detail script output can be found in G501_FF01435785ACT_INF L2TP Cabcharge on page 714 If the SCS 6.0 migration has been performed, a GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_FF01435785ACT_INF: Cabcharge L2TP Authentication Feature on page 542.
Checkpoint 5 item 21Patch Verification for G501_01450778ACT_IFMGR: Increase the MTU Size of Gn IP interface on GELC feature
Patch description: If on or more GELC card is present on the GGSN and G501_01450778ACT_IFMGR patch is activated, the default MTU settings on the Gn interface configured on the GELC card/ port is set to1536. Execute the following steps if Checkpoint 1 item 11, page 94 was executed. a. Login to the SCS client as the Gn ISP user. b. From Device Manager, double click on the GGSN, then click on the Trunk Interfaces tab. A list of trunk interfaces configured on the Gn ISP are displayed. c. Select the GELC card on the left pane, this will list the trunk interfaces configured on the GELC card/ port. d. Select the trunk interface on the right pane, then click Edit. e. Modify the MTU settings to 1536. Click OK to save the changes.
GPRS/UMTS
334
f. Repeat the above steps to modify the MTU on all the GELC cards/ ports on the GGSN on the Gn ISP. Also, repeat the same steps for all the GGSNs managed by the SCS server. Note: A GGSN post upgrade check must be executed to verify there are no connectivity issues following the GGSN 6.0 upgrade. Please refer to GGSN Post-Upgrade Procedure Patch Verification for G501_01450778ACT_IFMGR: Increase the MTU Size of Gn IP Interface on GELC feature. on page 543.
Checkpoint 5 item 22Patch Verification for G501_FF01567650ACT_IPCMC: TCP MSS Clamping feature
Patch Description: This feature provides the ability to configure the GGSN to modify or add the TCP MSS option for uplink and downlink packets to prevent IP fragmentation between the SGSN and GGSN for TCP based subscriber packets (e.g. packets that are part of an http flow). If the patch G501_FF01567650ACT_IPCMC was activated on GGSN 5.0.1 and the TCP MSS value was set on the GGSN, the script SCSUpgradeTCPMSSClamping.sh (packaged with the SCS server) can be executed to update the APNs on selected ISPs with the TCP MSS value for SCS 6.0. Note: The GGSN command show tcp mss can be used to retrieve the configured TCP MSS from the GGSN. - Execute the script: SCSUpgradeTCPMSSClamping.sh Change directory to <SCS6.0_ROOT>/bin
# cd /opt/shasta/scs6.0/bin # ./SCSUpgradeTCPMSSClamping.sh

# ./SCSUpgradeTCPMSSClamping.sh ************ UPGRADE TCP MSS CLAMPING FEATURE ************ ......info about the script *********************************************************** Do you want to continue? (Y)es or (N)o: y <- enter y to continue
411-5221-309
Standard
06.30 March 10, 2010
The upgrade TCP MSS Clamping is starting... G501_FF01567650ACT_IPCMC patch rule checking...
ISP_ID --3 4 5 6
ISP_NAME -----isp-ga isp-internet isp-blackberry isp-data
Enter ISP IDs to upgrade [all]:all <-hit enter to select all to update all ISPs, or enter ISP ID to select specific ISP
Please input the TCP Maximum Segment Size [1424]:1460 <- enter TCP MSS value
The upgrade will continue with below information: Selected ISP IDs: 3 4 5 6 TCP Maximum Segment Size is set to: 1460 Do you want to continue? (Y)es or (N)o: y <-type y to proceed with the update Connect to server..... ... ... 17-Apr-2008 16:36:10 154 INFO table.client.disconnectAll: 127.0.0.1:1099/1 Upgrade TCP MSS Clamping has completed successfully The upgrade proccess log file path: /opt/shasta/scs6.0/log/ servers/UpgrageAPNlog/UpgradeTCPClamping-041708_163343.log
- Details of the APNs being modified can be found the the log file indicated at the end of the script execution. - Detail script output can be found in G501_FF01567650ACT_IPCMC TCP MSS Clamping on page 717 Note: A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_FF01567650ACT_IPCMC: TCP MSS Clamping feature on page 543.
GPRS/UMTS
336
Checkpoint 5 item 23Patch Verification for G501_FF01385577ACT_ERCMC: DCCv2 Envelope Reporting Feature
Execute the following steps if Checkpoint 1 item 13, page 95 was executed. Instructions: a. Login to the SCS client and device_owner user. b. Click on the File menu and select SCS Configuration. c. Click on the SOC Activation tab. d. Verify the SOC key DIAMETER ENVELOPE REPORTING has enabled status. Note: A GGSN 6.0 post upgrade checkpoint must be executed to verify the functionality after GGSN 6.0 upgrade. Please refer to Patch Verification for G501_FF01385577ACT_ERCMC: DCCv2 Envelope Reporting Feature on page 543
Checkpoint 5 item 24Patch Verification for G501_FF01368038ACT_INF: DCCv2 Customization Essentials feature
Execute the following steps if Checkpoint 1 item 14, page 96 was executed. Instructions: a. Login to the SCS client and device_owner user. b. Click on the File menu and select SCS Configuration. c. Click on the SOC Activation tab. d. Verify the SOC keys DIAMETER CC RT CHARG and DIAMETER CC ESSENTIALS have enabled status. Note: A GGSN 6.0 post upgrade checkpoint must be executed to verify the functionality after GGSN 6.0 upgrade. Please refer to Patch Verification for G501_FF01368038ACT_INF: DCCv2 Customization Essentials Feature on page 543
Checkpoint 5 item 25Patch Verification for G501_FF01385579ACT_DCCCMC, G501_FF01385579ACT_DCCSSP: Parking Meter Charging Enhancement feature
Execute the following steps if Checkpoint 1 item 15, page 97 was executed.
411-5221-309 Standard 06.30 March 10, 2010
Instructions: a. Login to the SCS client and device_owner user. b. Click on the File menu and select SCS Configuration. c. Click on the SOC Activation tab. d. Verify the SOC key TIME EVENT BILLING has enabled status. A GGSN 6.0 post upgrade checkpoint must be executed to verify the functionality after GGSN 6.0 upgrade. Please refer to Patch Verification for G501_FF01385579ACT_DCCCMC, G501_FF01385579ACT_DCCSSP: Parking Meter Charging Enhancement Feature on page 543
Checkpoint 5 item 26Patch Verification for G501_FF01510131ACT_CPM: Consecutive Parking Meter feature
Execute the following steps if Checkpoint 1 item 16, page 98 was executed. Instructions: a. Login to the SCS client and device_owner user. b. Click on the File menu and select SCS Configuration. c. Click on the SOC Activation tab. d. Verify the SOC key TIME EVENT BILLING has enabled status. e. Add new SOC key CTP TIME EVENT BILLING. Set the Activation Status to Enabled. Note: The two SOC keys enable some common functionality but there is also distinct functionality associated with each. It is possible and valid to enable neither, one, or both SOCs. Note: Following the upgrade, the same set of SOCs should remain enabled as before. Note: The script upgradeCBBPolicyByAddingContentTypeProfile.sh must be executed to automatically create and associate a Content Type Profile to an existing CBB policy if that CBB policy has a Coupon Profile associated with it. Note: The script automatically restarts the SCS server. Here are some rules:
GPRS/UMTS
338
Content Type profile name is generated base on the Coupon Profile name. Update attributes of existing Content Type Ids and Coupon Ids which are used by CBB policy based on one to one mapping between them. Base Time Interval value of Content Type Id will be copied from one of Coupon Id. If Base Time Interval value of Coupon Id is empty, default value will be used for one of Content Type Id. New fields Time Quota Type and Envelope Reporting are set with default values. - Add Content type Id to Content Type Profile. Add Content Type Profile to CBB policy. After upgrading to SCS 6.0 and after activating CTP TIME EVENT BILLING SOC (optional), customers are able to execute this script to automatically configure Content Type profiles for the existing CBB policies After running the script restart server is recommended.
Note: Prior to starting the migration, the script performs a SCS backup is to ensure the original database can be restored in case the migration failed. f. The script upgradeCBBPolicyByAddingContentTypeProfile.sh is located under $SCS_HOME/bin directory.
# cd <SCS6.0_ROOT>/bin # ./upgradeCBBPolicyByAddingContentTypeProfile.sh
- Detail script output can be found in Consecutive Parking Meter feature on page 723 Note: A GGSN 6.0 post upgrade checkpoint must be executed to verify the functionality after GGSN 6.0 upgrade. Please refer to Patch Verification for G501_FF01510131ACT_CPM: Consecutive Parking Meter Feature on page 543
Checkpoint 5 item 27Patch Verification for G501_FF01369144ACT_PPDCMC: Dual Coupon feature
Execute the following steps if Checkpoint 1 item 17, page 99 was executed. Instructions: a. Login to the SCS client and device_owner user.
411-5221-309 Standard 06.30 March 10, 2010
b. Click on the File menu and select SCS Configuration. c. Click on the SOC Activation tab. d. Verify the SOC key Diameter CC SOC has enabled status. A GGSN 6.0 post upgrade checkpoint must be executed to verify the functionality after GGSN 6.0 upgrade. Please refer to Patch Verification for G501_FF01369144ACT_PPDCMC: Dual Coupon Feature on page 543.
Checkpoint 5 item 28Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration
Execute the following steps if Checkpoint 1 item 18, page 99 was executed patch G501_01505119ACT_SNTP was activated and SNTP server IP address configured as x.y.z.0, then execute the following steps. Instructions: a. Login to the SCS client as device_owner user. b. From Device Manager, double click on the GGSN. c. On the Device tab, check the Server IP Address under SNTP Client Configuration. IP address must be of the format x.y.z.255. d. Repeat the above steps for all GGSN that had Checkpoint 1 item 18, page 99 executed. A GGSN 6.0 post upgrade checkpoint must be executed to verify the functionality after GGSN 6.0 upgrade. Please refer to Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration on page 543.
Checkpoint 5 item 29Patch Verification for G501_01407739ACT_INF and G501_01595094AACT_AAA
Execute the following steps if Checkpoint 1 item 19, page 100 was executed. Script SCSUpgradeRadiusAuthentication.sh is packaged with the SCS server and can be executed to automate the following provisioning changes on the APN. Here are the options the script enables depending on the activation of the patches.
GPRS/UMTS
340
a. If the patch G501_01407739ACT_INF is deactivated in GGSN 5.0.1, no change on the APN is required. The default value currently is "RFC compliant default behavior". b. If the patch G501_01407739ACT_INF is active in 5.0.1, the option "Send a padded and encrypted blank character as password to RADIUS" will be selected for all the APN's under each ISP. c. If both patches G501_01407739ACT_INF and G501_01595094AACT_AAA are active in 5.0.1, "Send only password attribute and no password value" will be selected for all the APN's under each ISP. Execute the script: SCSUpgradeRadiusAuthentication.sh to update the APNs. - Change directory to <SCS6.0_ROOT>/bin
# cd /opt/shasta/scs6.0/bin # ./SCSUpgradeRadiusAuthentication.sh

# ./SCSUpgradeRadiusAuthentication.sh ********** UPGRADE RADIUS AUTHENTICATION ********** ...info about the script *************************************************** Do you want to continue? (Y)es or (N)o: y <- enter y to continue The upgrade Radius Authentication is starting... G501_01407739ACT_INF patch rule checking... G501_01595094AACT_AAA patch rule checking... List of isps have both G501_01407739ACT_INF and G501_01595094AACT_AAA patches are activated The Radius Authentication Type on APN(s) of these isps will be upgrade to'Send only password attribute and no password value' ISP_ID ISP_NAME -------3 isp-ga 4 isp-internet 5 isp-blackberry 6 isp-data Enter ISP ID to upgrade [all]:all <-hit enter to select all to update all ISPs, or enter ISP ID to select specific ISP
The upgrade will continue with below information: Selected ISP IDs: 411-5221-309 Standard 06.30 March 10, 2010
3 4 5 6 Do you want to continue? (Y)es or (N)o: y <-type y to proceed with the update Connect to server.....
- Details of the APNs being modified can be found the log file indicated at the end of the script execution. - Detail script output can be found in G501_01407739ACT_INF and G501_01595094AACT_AAA on page 719 A GGSN 6.0 post upgrade check must be executed to verify the fast feature patch functionality has been migrated to GGSN 6.0. Please refer to Patch Verification for G501_01407739ACT_INF and G501_01595094AACT_AAA. on page 544.
Checkpoint 5 item 30Patch Verification for G411_01339974AACT_GTPACCT - SGSN Change Partial Billing verification
This checkpoint is applicable to GGSNs upgraded from GGSN 4.1.1 to GGSN 6.0 only. Execute the following steps if Checkpoint 1 item 21, page 103 was executed. Script SCSUpgradeSGSNChangePartialBilling.sh is packaged with the SCS server and can be executed to update all APN(s) on selected ISP(s) to disable 'MAX SGSN Change Partial. Note: GGSN 4.1.1 patch G411_01339974AACT_GTPACCT must be activated on the GGSN for script to update the APNs. Execute the script: SCSUpgradeSGSNChangePartialBilling.sh to update the APNs. - Change directory to <SCS6.0_ROOT>/bin
# cd /opt/shasta/scs6.0/bin # ./SCSUpgradeSGSNChangePartialBilling.sh

342
# ./SCSUpgradeSGSNChangePartialBilling.sh SCS Upgrade SGSN Change Partial Billing ******** UPGRADE SGSN CHANGE PARTIAL BILLING ************** ....info about the script *********************************************************** Do you want to continue? (Y)es or (N)o: y <- enter y to continue The upgrade SGSN Change Partial Billing is starting... G411_01339974AACT_GTPACCT patch rule checking...
ISP_ID --290 291 292 361 390 419 433 444
ISP_NAME -----gn-139 gi-139 ga-139 gre-139 l2tp-139 li_default_isp vlan-139 vprn
Enter ISP ID to upgrade [all]:361 <-hit enter to select all to update all ISPs, or enter ISP ID to select specific ISP The upgrade will continue with below information: Selected ISP IDs: 361 Do you want to continue? (Y)es or (N)o: y <-type y to proceed with the update Connect to server..... ... ... 23-Apr-2008 16:40:05 066 INFO table.client.disconnectAll: 127.0.0.1:1099/1 Upgrade SGSN Change Partial Billing has completed successfully The upgrade proccess log file path: /opt/shasta/scs6.0/log/ servers/SCSUpgrageAPN/SCSUpgradeSGSNChangePartialBilling042308_163846.log
- Details of the APNs being modified can be found the log file indicated at the end of the script execution. - Detail script output can be found in SGSN Change Partial Billing G411_01339974AACT_GTPACCT on page 721
411-5221-309 Standard 06.30 March 10, 2010
Checklist work instructions and details These sub-sections are referenced in Table 21. They provide details for item checklists that require it. This checkpoint must be executed after sanity is executed and only after it is determined that the SCS server will not be rolled back to Solaris 8 or the previous version of SCS server. Post Upgrade checkpoint #6 6
Checkpoint 6 item 1Recreate disk mirrors
Note: This checkpoint is applicable to SCS server with mirrored disks prior to the SCS server upgrade. This check point is executed if the user wants to recreate disk mirrors for the file system which are un-mirrored prior to the SCS upgrade. Once the mirrors are created, the server cannot be rolled back to Solaris 8 unless a full server restore is performed from a tape backup. If the user is completely satisfied with the upgrade and would not be going back to Solaris 8, proceed to creating mirrors on Solaris 9. Use the metastat command to display the current status of the mirrors. # metastat If there is no output or metastat: not found on the console, it implies that the file systems have no mirrors. You could create mirrors, see Appendix E: Creating Mirrors on page 609.
Return to Upgrade readiness checkpoint #6 after it is determined the SCS server will not be rolled back to Solaris 8 on page 308
Checkpoint 6 item 2Only if applicable, modify SCS server hostname
Note: This checkpoint is applicable only if the SCS server hostname was modified prior to the SCS server upgrade. It is recommended that the SCS hostname and iPlanet instance name match. If it is necessary to change the hostname, the following procedure can be executed to modify the hostname.
GPRS/UMTS
344
Please refer to upgrade logs captured during Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32. This will be useful to determine the hostnames. Make a note of the hostname configured on the server. Capture the output of the following commands:
Make sure the output from the above commands match. Make a note of the iPlanet server instance name. Capture the output of the following command:
Use vi editor to change the current hostname.
File 1: /etc/hosts
In the file /etc/hosts, add a hostname alias loghost to the new hostname. Here is an example capture. The old hostname for the server is zrc2s0u9. iPlanet server instance is installed with hostname zngds0nn with loghost alias.
# cat /etc/hosts # # Internet host table # 127.0.0.1 localhost #old hostname 192.168.6.15 zrc2s0u9 #iPlanet server 192.168.162.35 10.128.16.38 10.128.25.62 10.128.26.71 instance zngds0nn gre vlan ipsec
loghost
411-5221-309
Standard
06.30 March 10, 2010

# cat /etc/hosts # # Internet host table # 127.0.0.1 localhost #current hostname 192.168.6.15 zrc2s0u9 zrc2s0u9.us.nortel.com #iPlanet server 192.168.162.35 10.128.16.38 10.128.25.62 10.128.26.71 instance zngds0nn gre vlan ipsec
loghost
ii. All occurrences of the current hostname must be modified with the new hostname in the following system files:
File File File File File File 2: 3: 4: 5: 6: 7: /etc/nodename /etc/inet/hosts /etc/inet/ipnodes /etc/net/ticlts/hosts /etc/net/ticots/hosts /etc/net/ticotsord/hosts
iii. Make a directory in /var/crash to match the new hostname (if it does not exist).
# mkdir -p /var/crash/<new hostname>
Here is an example capture, the hostname is taken from the above example:
# mkdir -p /var/crash/zrc2s0u9
iv. A reboot of the server is required. Perform a reboot of the server by following section Rebooting the SCS server on page 210
v. After server reboot, verify the SCS server host name has been modified. Execute the following commands to verify the hostname.
GPRS/UMTS
346
<End of hostname modification procedure>
Return to Upgrade readiness checkpoint #6 after it is determined the SCS server will not be rolled back to Solaris 8 on page 308
411-5221-309
Standard
06.30 March 10, 2010
Procedure for Changing the SCS server IP address
347
Procedure for Changing the SCS server IP address 15

If the SCS application is migrated to a new server, and the IP address of the new server is different than the old server, then some of the SCS configuration data must be changed. The management IP address stored on the GGSN must also be changed. Changing SCS configuration 1. It is necessary to reprovision the destinations for the various SCS Log and Pull servers to the new SCS server. This is done in the SCS Client under File->SCS Configuration..., Server Properties tab as in Figure 6.
Figure 6 Setting server IP address to new server
2. Edit each entry and change the IP address to the new value 3. Restart the SCS Processes # cd <SCS_ROOT> # ./SCSAdmin restart
GPRS/UMTS
348
16
OS Hardening for the Solaris 9 SCS Server makes changes to the Solaris Operating Environment to secure the system against unauthorized access and modification. This is an optional step. As part of this access control to the SCS Server: 1. Remote login of root user is disabled. A user account needs to be created for SCS server administration. Remote administrations will login as this user and su to root. 2. All well-known system accounts and in-bound FTP access are disabled. A user will be created for Preside to login for retrieving logs via FTP. OS hardening requires completion of recommended patches for Solaris 9. For OS Hardening information refer to Preside fore Wireless Internet, Operating System Security Enhancements User Guide, 411-5221-521. Prior to GGSNS3.1.X, TFTP was disabled by OS Hardening. The GGSN software patching mechanism added in GGSNS3.1 requires TFTP for proper operation. Therefore TFTP is enabled when the SCS software is installed. If the use of TFTP contradicts an operators security policies, it may be disabled by running the script # <SCS_ROOT>/lib/install/disable_tftp However, this will cause malfunction of the patching facility and may lead to support issues. If patching is subsequently required, TFTP can be re-enabled by running the script: # <SCS_ROOT>/lib/install/enable_tftp Packaging Packaging of the OS hardening script is delivered on the GGSN 6.0 SCS CD. Pre-work Certain steps are required to prepare the server for the execution of the Nortelsupplied, OS Hardening scripts. The scripts will remove remote access to the server with root privilege. You can create a non-root userid on the SCS server through normal administrative means. Check with your Solaris system administrator for the process to create a userid on the SCS server. Example Solaris commands which can be used to create a new userid on a server are:
# useradd -d /user/pmuser pmuser # passwd pmuser
411-5221-309
Standard
06.30 March 10, 2010
349
New password: Re-enter new password: passwd (SYSTEM): passwd successfully changed for pmuser
This creates a new userid of pmuser with a home directory of /user/ pmuser. These commands are not the only method through which the nonroot userid may be created; check with your Solaris system administrator for the correct method. Once the OS Hardening script has been executed, use the non-root userid to remotely connect to the server. Create a new Unix group nortel and create a new user nortel. If the group and user already exists, the following commands will not modify the current group and user.
# groupadd nortel # useradd -g nortel nortel If the group and user already exists, then the above commands will exit without making any changes. Here is ann example: # groupadd nortel UX: groupadd: ERROR: nortel is already in use. another. # useradd -g nortel nortel UX: useradd: ERROR: nortel is already in use. another.
Choose
Choose
Upgrading OS hardening software on the SCS server Upgrading OS Hardening on the SCS server requires following the steps: See Installing OS hardening software on SCS server on page 349 to install new package. See OS hardening procedures on page 353 to activate the new package.
Installing OS hardening software on SCS server After the installation of the SCS Server on Solaris 9, the following steps detail the OS hardening process. 1. The OS Harden package is on the SCS installation CD and is named NNoshscs.pds.Z 2. Insert the SCS installation CD and find out the CD mount point. Then copy NNoshscs.pds.Z from installation CD.
# df -k Here is an example: # df -k ... <- other mount points
GPRS/UMTS
350
OS Hardening of GGSN SCS Server /vol/dev/dsk/c0t6d0/gssl0060 1264 ggsn0060 # cd /cdrom/ggsn0060/Solaris # cp NNoshscs.pds.Z / # cd /
1264
100%
/cdrom/
3. Uncompress the NNoshscs.pds.Z file by running the command:

# uncompress NNoshscs.pds.Z
4. Install the OS Hardening software by running the command

# pkgadd -d NNoshscs.pds
The following interactions are required after command execution The following packages are available: (This is an example capture, the Solaris version will vary depending on the current Solaris version running the server)
1 NNoshscs Nortel Networks Solaris 9 OS Hardening scripts for SCS Server (sparc) SCS_V05_00.E03 Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: all
#The selected base directory </SECURITY> must exist before installation is attempted. Do you want this directory created now [y,n,?,q] y This package contains scripts which will be executed with super-user permission during the process of installing this package.Do you want to continue with the installation of <NNoshscs> [y,n,?] y Verify that all of the scripts (Solaris_OsHarden, Solaris_OsUnHarden, and showstatus) are present under / SECURITY/NNoshscs/bin. # cd /SECURITY/NNoshscs/bin # ls Solaris_OsHarden Solaris_OsUnHarden # pwd /SECURITY/NNoshscs/bin Run the showstatus script
showstatus
411-5221-309
Standard
06.30 March 10, 2010
351
THE VERSION MUST BE UPDATED # ./showstatus The system is not hardened. The system is installed with the following package(s): Package "NNoshscs.SCS_V05_00.E03", patch level "none".
Note: The actual version may vary according to your release.

Here is an example capture: # pkgadd -d NNoshscs.pds The following packages are available: 1 NNoshscs Nortel Networks Solaris 9 OS Hardening scripts for SCS Server (sparc) SCS_V05_00.E03 Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: all Processing package instance <NNoshscs> from </NNoshscs.pds> Nortel Networks Solaris 9 OS Hardening scripts for SCS Server (sparc) SCS_V05_00.E03 Nortel Networks ## Executing checkinstall script. The selected base directory </SECURITY> must exist before installation is attempted. Do you want this directory created now [y,n,?,q] y Using </SECURITY> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts which will be executed with superuser permission during the process of installing this package. Do you want to continue with the installation of <NNoshscs> [y,n,?] y Installing Nortel Networks Solaris 9 OS Hardening scripts for SCS Server as <NNoshscs> ## Executing preinstall script. ## Installing part 1 of 1. /SECURITY/NNoshscs/bin/Solaris_OsHarden /SECURITY/NNoshscs/bin/Solaris_OsUnHarden /SECURITY/NNoshscs/bin/showstatus /SECURITY/NNoshscs/cfg/scs/account_removal_list /SECURITY/NNoshscs/cfg/scs/cron_disable_list
GPRS/UMTS
352
/SECURITY/NNoshscs/cfg/scs/ftp_disable_list /SECURITY/NNoshscs/cfg/scs/ftpaccess_list /SECURITY/NNoshscs/cfg/scs/inetd_disable_list /SECURITY/NNoshscs/cfg/scs/ipv6_disable_list /SECURITY/NNoshscs/cfg/scs/kernel_modification_list /SECURITY/NNoshscs/cfg/scs/netrc_lock_list /SECURITY/NNoshscs/cfg/scs/new_default_ftpd /SECURITY/NNoshscs/cfg/scs/new_default_inetd /SECURITY/NNoshscs/cfg/scs/new_default_telnetd /SECURITY/NNoshscs/cfg/scs/new_inetinit /SECURITY/NNoshscs/cfg/scs/new_inetsvc /SECURITY/NNoshscs/cfg/scs/new_issue /SECURITY/NNoshscs/cfg/scs/new_login /SECURITY/NNoshscs/cfg/scs/new_nddconfig /SECURITY/NNoshscs/cfg/scs/new_newsyslog /SECURITY/NNoshscs/cfg/scs/new_nscd.conf /SECURITY/NNoshscs/cfg/scs/new_passwd /SECURITY/NNoshscs/cfg/scs/new_syslog.conf /SECURITY/NNoshscs/cfg/scs/nfs_disable_list /SECURITY/NNoshscs/cfg/scs/rauth_disable_list /SECURITY/NNoshscs/cfg/scs/service_removal_list /SECURITY/NNoshscs/lib/OsHardenAccount /SECURITY/NNoshscs/lib/OsHardenBSM /SECURITY/NNoshscs/lib/OsHardenBanner /SECURITY/NNoshscs/lib/OsHardenCheck /SECURITY/NNoshscs/lib/OsHardenCron /SECURITY/NNoshscs/lib/OsHardenEnv.ksh /SECURITY/NNoshscs/lib/OsHardenFTP /SECURITY/NNoshscs/lib/OsHardenFinish /SECURITY/NNoshscs/lib/OsHardenInetd /SECURITY/NNoshscs/lib/OsHardenInetsvc /SECURITY/NNoshscs/lib/OsHardenInit /SECURITY/NNoshscs/lib/OsHardenKernel /SECURITY/NNoshscs/lib/OsHardenLogin /SECURITY/NNoshscs/lib/OsHardenNFS /SECURITY/NNoshscs/lib/OsHardenNetrc /SECURITY/NNoshscs/lib/OsHardenNetwork /SECURITY/NNoshscs/lib/OsHardenNscd /SECURITY/NNoshscs/lib/OsHardenPam /SECURITY/NNoshscs/lib/OsHardenPasswd /SECURITY/NNoshscs/lib/OsHardenRun /SECURITY/NNoshscs/lib/OsHardenSyslog /SECURITY/NNoshscs/lib/OsHardenTCP /SECURITY/NNoshscs/lib/OsHardenUtil /SECURITY/NNoshscs/lib/Package_Version /SECURITY/NNoshscs/supplement/disable_X11 /SECURITY/NNoshscs/supplement/disable_rdisc /SECURITY/NNoshscs/supplement/enable_X11 /SECURITY/NNoshscs/supplement/enable_rdisc [ verifying class <none> ] ## Executing postinstall script. Successfully installed package NNoshscs, version SCS_V05_00.E03. Installation of <NNoshscs> was successful. <end of example capture>
411-5221-309
Standard
06.30 March 10, 2010
353
OS hardening procedures Note: OS hardening must be performed at the system console. 1. Login to the SCS server as root user and reboot the server to single user mode
# sync; sync; sync # init 0 INIT: New run level: 0 {6} ok boot -rs Boot device: /pci@8,700000/scsi@1/disk@6,0:f args: -rs ... ... INIT: SINGLE USER MODE #
File and
2. Change to the /SECURITY/NNoshscs/bin directory and run the OS hardening script named Solaris_OsHarden
# cd /SECURITY/NNoshscs/bin # ./Solaris_OsHarden -p NNoshscs
3. Upon completion of hardening script accept system reboot. Reboot the server:
# init 6
4. Verify the OS hardening by changing to the /SECURITY/NNoshscs/bin directory and running the showstatus script:
# ./showstatus The system is hardened with the following configuration: Version "NNoshscs.SCS_V05_00.E03", patch level "none". (XX and YY will be your version number) The system is installed with the following packege(s): Package "NNoshscs.SCS_V05_00.E03", patch level "none".
Note: The actual version may vary according to your release.
GPRS/UMTS
354
OS unhardening procedure on Solaris 8
OS unhardening procedure on Solaris 8
17
The Solaris 8 OS must be unhardened before the Solaris 9 BE creation. The following steps detail the OS unhardening process. 1. Login to the SCS server as root user and reboot the server to single user mode
# sync; sync; sync # init 0 INIT: New run level: 0 At the ok prompt, type boot -rs {6} ok boot -rs Boot device: /pci@8,700000/scsi@1/disk@6,0:f args: -rs ... ... INIT: SINGLE USER MODE #
File and
2. Change to the /SECURITY/NNoshscs/bin directory (cd /SECURITY/ NNoshscs/bin) and run the OS Unhardening script named Solaris_OsUnHarden:
# ./Solaris_OsUnHarden -p NNoshscs
3. Upon completion of unhardening script accept system reboot.

# reboot
4. Verify the OS unhardening by changing to the /SECURITY/NNoshscs/bin (cd /SECURITY/NNoshscs/bin) directory and running the showstatus script: # ./showstatus
The system is not hardened. The system is installed with version "SCS_V05_00.E03", patch level "none".
5. Remove the OS Hardening software by running the command

# pkgrm NNoshscs
411-5221-309
Standard
06.30 March 10, 2010
SCS Client upgrade procedures 355
SCS Client upgrade procedures

SCS client installation
18
18
To facilitate roll back, it is recommended that you install the new version of the SCS GUI client in a different installation directory. You can keep multiple versions of the SCS GUI client on your machine. Should you need to roll back you can exit the newer client, and launch the old client (once the SCS server is rolled back). When you are satisfied with the new SCS Server installation, delete the older SCS GUI clients to preserve disk space. SCS Windows/Solaris Clients are only supported for JRE/JDK Version 1.4.2. If the machine is not running the JRE 1.4.2, please download the JRE 1.4.2 from Sun website, http://java.sun.com Install the new SCS client software on the SCS client host machine, using the following instructions. SCS Client Installation for Windows 2000 and XP (older that version 2002) 1. On the Windows machine, where the SCS client is to be installed, copy the InstallSCS.exe file from the SCS CD or ESD. Double click on the file, and follow the instructions to complete the installation. When prompted to specify the directory for the Windows client, select the directory different from the GGSNS4.1.1 and GGSNS5.0.1 SCS Client installation. Return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
SCS Client Installation for Windows 2003 server Windows 2003 server has a feature - Data Execution Prevention (DEP) enabled by default that prevents installing the SCS client. Users must disable DEP for the SCS client installation file - InstallSCS.exe prior to performing the installation. The following steps can be followed for SCS client installation on Windows 2003 server. 1. On the Windows 2003 sever, copy the InstallSCS.exe file from the SCS 6.0 CD or ESD. 2. Disable DEP: From Control Panel-> System--> Advanced--> Performance--> Settings. Select Turn on DEP for all programs and
GPRS/UMTS
356
services except those I select -> Add--> Select InstallSCS.exe. Click Apply 3. Set XP compatibility for InstallSCS.exe: Right click InstallSCS.exe-> Properties-> Compatibility. Check Run this program in compatibility mode for: Select Windows XP 4. Install SCS client: Double click on InstallSCS.exe, follow the instructions on the screen. When prompted to specify the directory for the Windows client, select the directory different from the GGSNS4.1.1 and GGSNS5.0.1 SCS Client installation. Return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
SCS Client Installation for XP (version 2002 or later) and Vista 1. On the Windows host, copy the InstallSCS.exe file from the SCS 6.0 CD or ESD. 2. Set Windows 2000 compatibility for InstallSCS.exe: Right click InstallSCS.exe-> Properties-> Compatibility. Check Run this program in compatibility mode for: Select Windows 2000 3. Install SCS client: Double click on InstallSCS.exe, follow the instructions on the screen. When prompted to specify the directory for the Windows client, select the directory different from the GGSNS4.1.1 and GGSNS5.0.1 SCS Client installation. Return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
SCS Solaris Client Installation 1. Log in to the Solaris server as root. 2. Create a new directory for installing SCS client for SCS 6.0. Here is an example.
# cd /opt/shasta # mkdir scsclient6.0 # cd scsclient6.0
3. Insert the SCS software CD (or from ESD). Find out the CD mount point using df -k
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential # df -k Here is an example: # df -k ... <-Other mounted partitions /vol/dev/dsk/c0t6d0/ggsn0061 330000 330000 ggsn0061
100%
/cdrom/
4. Copy the scsclient.tar.Z file from the Software CD to the present directory
# cp /cdrom/ggsn061/Solaris/scsclient.tar.Z \ /opt/shasta/scsclient6.0
5. uncompress scsclient.tar.Z 6. tar -xvf scsclient.tar 7. This will create the file setup.sh script, in the present directory. Execute the script
# ./setup.sh
8. The script will prompt for the installation directory for the SCS Client. Please accept the default which will be the present working directory. This will install the Solaris client. 9. Change to bin directory.
# cd bin
10. If the user is logged in remotely to the server, please set the DISPLAY environment variable.
# csh # setenv DISPLAY <yourIPAddress>:0.0
11. ./SCSClient & (This command will start the Solaris Client) Return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
SCS client rollback

SCS client rollback on Windows 2000 and XP (older that version 2002) 1. Uninstall the installation of the GGSN 6.0 SCS Client from Control Panel-> Add/ Remove Programs.
GPRS/UMTS
18
358
2. Install the GGSNS4.1.1 or GGSNS5.0.1 SCS Client if it is not installed.
SCS client rollback on XP (version 2002 or later), Window 2003 and Vista 1. Determine the installation directory of the SCS 6.0 client. One way is to right click on the SCS client icon (either from Desktop if SCS Client icon exists or Start-> Programs-> Shasta SCS Client GGSNS6.0-> SCS Client), click Properties. From the Shortcut tab, make a note to the directory listed in the text box Start in. 2. Change directory to the path noted from the above step. Go one level up to the SCS client installation directory (one level above bin directory). 3. Change directory to UninstallerData 4. Right click on the file - Uninstall SCS.exe, select Properties->Compatibility. Check Run this program in compatibility mode for: Select Windows 2000 5. Double click on Uninstall SCS.exe, follow the instructions on the screen.
SCS client rollback on Solaris 1. Close any open SCS client sessions 2. Remove the SCS client installation directory using:
# rm -rf <scs_client_installation_directory>
Enabling SSL on the SCS Client
18
If SSL is enabled on the SCS server, the user must enable SSL on the client machine. Refer to the section below for steps to enable SSL after the SCS client installation.The SSL packages for SCS Clients are packaged on the SCS SSL CD or ESD. Enabling SSL on SCS Windows Client Machine 1. Copy the sslpkg.zip file from the SSL CD to the <SCS_CLIENT_HOME> (where <SCS_CLIENT_HOME> is SCS Client install directory) on the windows PC. 2. Unzip the sslpkg.zip file, using the WinZip utility. Extract the files the SCS Client directory 3. Edit the file <SCS_CLIENT_HOME>\bin\guiclient.bat to enable SSL. Look for the string that contains the following text com.shasta.spm.gui.Login
411-5221-309 Standard 06.30 March 10, 2010
Before this string, add the following string to the file <space>-DSPM_ENABLE_SSL=true<space> Example: <space>-DSPM_ENABLE_SSL=true com.shasta.spm.gui.Login here, <space> is one space. 4. Save the file 5. Please refer to section If SSL is enabled on the SCS server, then make a backup copy of the SSL certificates files: on page 155 and Make a backup copy of the SSL certificates on the SCS client. SCS client for Windows and Solaris are outlined below. on page 155 If SSL was not enabled prior to SCS server/ client upgrade, please refer to NTP Nortel GGSN Provisioning Procedures : 411-5221-927 for steps to create SSL certificates and install on the SCS client. If SSL was enabled prior to the SCS client/ server upgrade, move the backup copies of the SSL certificates to the current SCS client installation directory\etc. Copy C:\mysslcertificates\sslrsa.crt.BACKUP to <SCS_CLIENT_HOME>\etc Copy C:\mysslcertificates\trusted.txt.BACKUP to <SCS_CLIENT_HOME>\etc
Rename sslrsa.crt.BACKUP file to sslrsa.crt Rename trusted.txt.BACKUP to trusted.txt
Enabling SSL on the SCS Unix Client Machine 1. Insert the SCS SSL CD into the SCS server CDROM/ DVDROM. Find out the CD mount point.
# df -k Here is an example: # df -k ... <-Other mounted partitions /vol/dev/dsk/c0t6d0/gssl0060 330000 330000 gssl0060
100%
/cdrom/
GPRS/UMTS
360
2. Copy the sslpkg.tar.Z file from the SSL CD to the <SCS_CLIENT_ROOT> (where <SCS_CLIENT_ROOT> is SCS Client install directory) on the unix machine.
# cp /cdrom/gssl0060/Solaris/sslpkg.tar.Z opt/scsclient
3. Uncompress the sslpkg.tar.Z and untar it

# uncompress sslpkg.tar.Z # tar -xvf sslpkg.tar
4. Modify file permissions for file setup.sh

5. Execute setup.sh. Here is an example.

# ./setup.sh This program will install SCS SSL version SCS GGSNS6.0_SCS6.0(42) Please specify the directory for SCS installation [/opt/ shasta/scs6.0]: Matching SCS version found - SCS SSL will be installed in / opt/shasta/scs6.0. Copying the required files...... SCS SSL is now installed. Refer to SCS documentation for instructions on enabling SSL.
6. Edit the file <SCS_CLIENT_HOME>/bin/SCSClient to enable SSL, using vi editor. Look for the line that contains the following text com.shasta.spm.gui.Login Before this line, add the following line to the file <space>-DSPM_ENABLE_SSL=true<space> Where space is one space 7. Save the file 8. Please refer to section If SSL is enabled on the SCS server, then make a backup copy of the SSL certificates files: on page 155 and Make a
411-5221-309
Standard
06.30 March 10, 2010
backup copy of the SSL certificates on the SCS client. SCS client for Windows and Solaris are outlined below. on page 155 If SSL was not enabled prior to SCS server/ client upgrade, please refer to NTP Nortel GGSN Provisioning Procedures : 411-5221-927 for steps to create SSL certificates and install on the SCS client. If SSL was enabled prior to the SCS client/ server upgrade, move the backup copies of the SSL certificates to the current SCS client installation directory\etc.
# # # # # cd cp cd mv mv <SCS_CLIENT_ROOT> /etc/shasta/*.BACKUP etc etc sslrsa.crt.BACKUP sslrsa.crt trusted.txt.BACKUP trusted.txt
GPRS/UMTS
362
19
Client hardening Customers may choose to follow manufacturer recommendations or local administrative practices to secure their client machines. For Windows NT and Window 98
http://www.microsoft.com/technet/security/topics/ networksecurity/threatmi.mspx#EJD
For Windows 2000 http://www.microsoft.com/downloads/details.aspx?familyid=15E83186A2C8-4C8F-A9D0-A0201F639A56&displaylang=en
Solaris See OS Hardening of GGSN SCS Server on page 348.
411-5221-309
Standard
06.30 March 10, 2010
Rollback SCS 6.0 to SCS 4.1.2 after Solaris 9 Upgrade
363
Rollback SCS 6.0 to SCS 4.1.2 after Solaris 9 Upgrade 20

This procedure explains the steps required to rollback SCS 5.0.1 or SCS 5.0.2 on Solaris 9 to SCS4.x on Solaris 8. Note: Reference to SCS 5.0 in this section refers to SCS 5.0.1 or SCS 5.0.2 Pre-requisite: This procedure can be run only if Solaris 8 BE (Boot Environment) is available. If Solaris 8 BE has been deleted, you will need to recover the system using the Tape backup performed on Solaris 8 with SCS4.x running. Procedure: Starting point: Server is running SCS 5.0.1 or SCS 5.0.2 on Solaris 9. Run the command uname to find out if the server is running on Solaris 9. # uname -rm 5.9 sun4u Please take a note of SCS 5.0 and iPlanet installation directory before proceeding. To find the current SCS and iPlanet installation directories: SCS root directory:
Example:
SCSHead=/opt/shasta/scs5.0 <SCS6.0_ROOT> = SCSHead = /opt/shasta/scs5.0
LDAP root directory:

GPRS/UMTS
364
Example :
LDAPPath=/opt/shasta/ldap <IPLANET_ROOT> = LDAPPath = /opt/shasta/iplanet
1. Close all instances of SCS client connected to the SCS server. 2. Disable LDAPWatch and SCSWatch
<SCS6.0_ROOT>/bin/LDAPWatch-disable <SCS6.0_ROOT>/bin/SCSWatch-disable
Example:
# cd /opt/shasta/scs6.0 # ./LDAPWatch-disable # ./SCSWatch-disable
3. Stop SCS 6.0 and LDAP iplanet processes

<SCS6.0_ROOT>/bin/SCSAdmin stop
Example:
# pwd /opt/shasta/scs6.0/bin # ./SCSAdmin stop
Verify SCS 6.0 processes are stopped

<SCS6.0_ROOT>/bin/SCSAdmin status
Example:
# ./SCSAdmin status
4. Stop LDAP iplanet processes

<IPLANET_ROOT>/slapd-<hostname>/stop-slapd <IPLANET_ROOT>/stop-admin
Example:
411-5221-309
Standard
06.30 March 10, 2010
365
# slapd*/stop-slapd # ./stop-admin
Verify LDAP iplanet processes are stopped

# ps aef | grep v grep | grep slapd
(the above command must not return a result)

# ps aef | grep v grep | grep admin
(the above command must not return a result) If the above ps command returns a result, stop the processes. 5. Uninstall iPlanet directory server and remove iplanet installation directory.
# cd <IPLANET_ROOT> # ./uninstall
Example:
# cd /opt/shasta/iplanet # ./uninstall
(hit enter to select default) When prompted for: Would you like to continue with local uninstallation? [No]: Yes Answer Yes 6. After the uninstall procedure completes, remove iplanet installation directory
# cd /opt/shasta # \rm -rf iplanet
See Appendix H: Example capture of iPlanet server uninstallation on page 656 for an example of the uninstallation procedure.
GPRS/UMTS
366
7. Delete <shasta> directory in /opt. This will delete both SCS 6.0 and iPlanet directories Example:
# cd /opt # \rm -R shasta
8. Check the Solaris 8 BE name

# /usr/sbin/lustatus
Example:
# /usr/sbin/lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- -------- ------ --------- --------------solaris8 yes no no yes solaris9 yes yes yes no -
9. Active Solaris 8 BE
# /usr/sbin/luactivate solaris8
Example:
# /usr/sbin/luactivate solaris8 *********************************************************** *** The target boot environment has been activated. It will be used when you reboot. NOTE: You MUST NOT USE the reboot, halt, or uadmin commands. You MUST USE either the init or the shutdown command when you reboot. If you do not use either init or shutdown, the system will not boot using the target BE. *********************************************************** *** In case of a failure while booting to the target BE, the following process needs to be followed to fallback to the currently working boot environment: 1. Enter the PROM monitor (ok prompt). 2. Change the boot device back to the original boot environment by typing:
411-5221-309
Standard
06.30 March 10, 2010
367
setenv boot-device disk6:a 3. Boot to the original boot environment by typing: boot *********************************************************** *** Activation of boot environment <solaris8> successful.
10. Reboot so that the newly activated BE takes effect.

# init 0
At the ok prompt, use the Solaris OpenBoot PROM nvalias command to define the solaris8_root and solaris9_root device alias. From the solaris8_root and solaris9_root captured in Important Step to determine server boot path for Solaris 8 and Solaris 9: on page 432:
{2} ok nvalias solaris8_root /pci@8,600000/SUNW,qlc@2/ fp@0,0/disk@w500000e010188041,0:a {2} ok nvalias solaris9_root /pci@8,600000/SUNW,qlc@2/ fp@0,0/disk@w21000004cf786ffa,0:a
Redefine the boot-device alias to reference solaris8_root and solaris9_root. At the ok prompt:
{2} ok setenv boot-device solaris8_root solaris9_root boot-device = solaris8_root solaris9_root {2} ok nvstore {2} ok setenv use-nvramrc? true use-nvramrc? = true
Execute printenv and verify that the boot-device variable is set to current_root and backup_root (under Value column). Verify variable usenvramrc is set to true. Reboot the server
{2} ok boot solaris8_root
Note: In case the server is unable to reboot indicating a disk check is needed, please perform the following steps to fix the disk errors.
368
If the SCS server had mirrored disks please have the follow tables handy Disk Mirroring Mapping for Critical File Systems on page 70 and Disk Mirroring Mapping for Non-critical File Systems on page 70 If the SCS server had non-mirrored disks please have the follow table handyPartition Information for Non-Mirrored Servers on page 667 Perform disk check procedure detailed in section Appendix I: Disk Check for SCS for non-mirrored servers on page 661
11. As soon as the server comes up, check if SCS 4.x and LDAP 4.16 processes are running. If the processes are running stop the processes.
12. Disable LDAPWatch and SCSWatch in SCS 5.0.x

Example:
# cd /opt/shasta/scs6.0/bin # ./LDAPWatch-disable # ./SCSWatch-disable
13. Verify LDAPWatch and SCSWatch have been disabled in the system crontab file. An entry for SCSWatch and LDAPWatch must not be listed in the server crontab.
# crontab l
14. Stop SCS 6.0 and iPlanet processes if already started

<SCS6.0_ROOT>/bin/SCSAdmin status <-Check if SCS processes are running <SCS6.0_ROOT>/bin/SCSAdmin stop <-Stop SCS 6.0 process
Example:
# pwd
411-5221-309
Standard
06.30 March 10, 2010
369
/opt/shasta/scs5.0/bin
Stop SCS 6.0 processes

# ./SCSAdmin stop # ./SCSAdmin status
Verify is iPlanet processes are running

# ps aef | grep v grep | grep slapd <-Check iplanet process # ps aef | grep v grep | grep admin <-Check iplanet admin process
Example:
# ps aef | grep v grep | grep slapd nobody 14986 1 0 Feb 15 ? 0:08 ./ns-slapd -D / opt/shasta/iplanet/slapd-urc2y3pa -i /opt/shasta/iplanet/ slapd-u
# ps aef | grep v grep | grep admin root 562 449 0 Feb 07 0:01 ns-httpd -d /opt/shasta/ iplanet/admin-serv config root 442 1 0 Feb 07 0:00 ./uxwdog -d /opt/shasta/ iplanet/admin-serv/config root 449 442 0 Feb 07 0:00 ns-httpd -d /opt/ shasta/iplanet/admin-serv/config
Stop iPlanet server and admin server process

<IPLANET_ROOT>/slapd-<hostname>/stop-slapd <-Stop iplanet server <IPLANET_ROOT>/stop-admin <-Stop iplanet admin server
Example:
# cd /opt/shasta/iplanet # slapd*/stop-slapd # ./stop-admin
15. Uninstall iPlanet server (/opt/shasta/iplanet) and remove iplanet installation directory
370
Rollback SCS 6.0 to SCS 4.1.2 after Solaris 9 Upgrade # cd <IPLANET_ROOT> # ./uninstall
(hit enter to select default) When prompted for: Would you like to continue with local uninstallation? [No]: Yes Answer = Yes 16. Remove iplanet installation directory.
See Appendix H: Example capture of iPlanet server uninstallation on page 656 for an example capture of the uninstallation procedure. 17. Delete <SCS6.0_ROOT> in /opt. This will delete both SCS 6.0 and iPlanet directories Example:
# cd /opt/shasta # \rm -R scs5.0
18. Start LDAP 4.16 server and admin processes.

# cd <LDAP_ROOT> # cd slapd-<hostname>
(modify <hostname> to match your server)

# ./start-slapd # cd ../ # ./start-admin
19. Clean up any additional LDAP 4.16 instances created because of a previous upgrade. Example:
411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential # pwd /opt/shasta/ldap # ls | grep slapd slapd-urc2y3pa slapd-urc2y3pa1
371
If the above ls command returns 2 entries, clean up is required. If the SCS server was upgraded to SCS 5.0.2, then the second LDAP server instance is automatically deleted. If the SCS server was upgraded to SCS 5.0.1, then the second LDAP server instance (slapd-<hostname>1) needs to be deleted. Note: It is possible that the SCS server hostname already has a 1 at the end of the name, so the second LDAP instance name will be slapd-<hostname1>1 Stop the second ldap instances: Example:
# pwd /opt/shasta/ldap # cd slapd-<hostname>1 # ./stop-slapd # cd ../
Remove additional ldap instance Carefully note down the ldap instance that has a 1 appended at the end. If your server hostname already has a 1 (example: scsserver1), then the redundant ldap instance usually is scsserver11. Example:
# ls | grep slapd slapd-urc2y3pa <-original ldap server instance) slapd-urc2y3pa1 <-ldap server instance added by a prior upgrade)
# rm -rf slapd-urc2y3pa1 <-remove redundant ldap instance
20. Start SCS4.x server processes
GPRS/UMTS
372
Rollback SCS 6.0 to SCS 4.1.2 after Solaris 9 Upgrade # cd <SCS_ROOT>/bin # ./SCSAdmin start # ./SCSAdmin status
Example:
# cd /opt/shasta/scs/bin # ./SCSAdmin start
21. Verify all SCS server processes are running.

# ./SCSAdmin status
22. Enable SCSWatch and LDAPWatch.

# pwd /opt/shasta/scs/bin # ./SCSWatch-enable # ./LDAPWatch-enable
23. Revert /etc/shasta/scs.config file to reflect the SCS 4.1.2 Change directory to /etc/shasta
# cd /etc/shasta
Copy the current scs.config file to scs.config.<SCS_version>. Here is an example for SCS 5.0.2.
# cp scs.config scs.config.502
Copy scs.config.bak to scs.config

# cp scs.config.bak scs.config
24. Login to the SCS client 4.1.2. The GGSNs in the region will be out of sync in case SCS 6.0 post upgrade scripts were executed or any provisioning changes were made from the SCS. Resync of the GGSN is required in case the GGSN show out of sync.
End of rollback of SCS 6.0 on Solaris 9 to SCS4.x on Solaris 8
411-5221-309
Standard
06.30 March 10, 2010
SCS 6.0 to SCS 5.0.2 Rollback procedure 373

1. Verify SCS 6.0 process status
Example: # cd /opt/shasta/scs6.0/bin # ./SCSAdmin status Running Solid Database Server since Mar_24 (pid=14935) Running SCS Daemon since Mar_24 (pid=14953) Running SCS Domain Server since Mar_24 (pid=14965) Running SNMP Proxy since Mar_24 (pid=15056) Running SCS Region Server since Mar_24 (pid=15086) Running SCS Monitor Server since Mar_24 (pid=15112) Running SCS Trap Daemon since Mar_24 (pid=15138) Running SCS Pull Server since Mar_24 (pid=15191) Running SCS Log Server since Mar_24 (pid=15211) Running SCS CORBA Server since Mar_24 (pid=15062) SCS Provisioning is enabled SSL is not enabled on present servers All SCS server processes are running. Version SCS GGSNS6.0_SCS6.0(43)
2. Close all instances of SCS client connected to the SCS server. 3. Stop SCS 6.0 processes
# ./SCSAdmin stop
4. Disable SCSWatch and LDAPWatch process.

# ./SCSWatch-disable # ./LDAPWatch-disable
5. Stop iPlanet instance for SCS 6.0. Determine <IPLANET_ROOT>

Here is an example:
GPRS/UMTS
374
SCS 6.0 to SCS 5.0.2 Rollback procedure
Determine iPlanet instance for SCS 6.0.

# cat /etc/shasta/scs.config | grep LDAPServerName
Here is an example:
# cat /etc/shasta/scs.config | grep LDAPServerName LDAPServerName=slapd-zrc2s0ns1
Change directory to the directory returned from the above command. From the above example:
# cd slapd-zrc2s0ns1
Stop iPlanet directory server instance.

# ./stop-slapd
6. Start iPlanet instance for SCS 5.0.2. Determine the iPlanet instance for SCS 5.0.2. Note, the file /etc/shasta/scs.config.bak has information about SCS 5.0.2 installation.
# cat /etc/shasta/scs.config.bak | grep LDAPServerName
Here is an example:
# cat /etc/shasta/scs.config.bak | grep LDAPServerName LDAPServerName=slapd-zrc2s0ns
Change directory to the directory path returned by the above command. From the above example.
# cd slapd-zrc2s0ns
Start iPlanet instance for SCS 5.0.2.

# ./start-slapd
Note, if the iPlanet directory process is already running, the server will return a message indicating the process is running. Here is an example:
There is an ns-slapd process already running: 14148
7. Verify iPlanet instance for SCS 5.0.2 is running is the assigned port
411-5221-309
Standard
06.30 March 10, 2010
# cd <SCS502_ROOT> # cat .scs.config | grep LDAPServerPort Example: # cat .scs.config | grep LDAPServerPort LDAPServerPort=390 Check port 390 is listening: # netstat -na | grep LdapServerPort (number) Example: # netstat -na | grep 390 *.390 *.* 0 LISTEN
0 24576
Note: There can be multiple processes listed with the netstat command output If netstat command does not return any output, please contact next line of support.
8. Verify iPlanet admin server process is running

# ps -aef | grep -v grep | grep admin
Here is an example:
# ps -aef | grep admin | grep -v grep root 3628 3200 0 Aug 14 ? opt/shasta/iplanet/admin-serv/config root 3185 1 0 Aug 14 ? opt/shasta/iplanet/admin-serv/config root 3200 3185 0 Aug 14 ? opt/shasta/iplanet/admin-serv/config 0:06 ns-httpd -d / 0:00 ./uxwdog -d / 0:01 ns-httpd -d /
If the above ps command does not return results indicating ns-httpd process is running, then start the iPlanet admin process. Here are the steps to start the iPlanet admin process. Determine <IPLANET_ROOT>
Here is an example:
GPRS/UMTS
376
SCS 6.0 to SCS 5.0.2 Rollback procedure
# cd /opt/shasta/iplanet # ./start-admin
9. Start SCS 5.0.2 processes. Determine <SCS502_ROOT>.

# cat /etc/shasta/scs.config.bak | grep SCSHead
Here is an example:
# cat /etc/shasta/scs.config | grep SCSHead SCSHead=/opt/shasta/scs502
Change directory to the directory path returned by the above command. From the above example.
# cd /opt/shasta/scs502 # cd bin #./SCSAdmin start
10. Verify SCS 5.0.2 processes are running

#./SCSAdmin status
11. Revert /etc/shasta/scs.config.bak file to /etc/shasta/scs.config to reflect the SCS 5.0.2. Note, if this step is not performed, subsequent upgrade from SCS 5.0.2 to SCS 6.0 will have issues. Change directory to /etc/shasta
# cd /etc/shasta
Copy SCS 6.0 scs.config file to scs.config.6.0

# cp scs.config scs.config.502
Copy scs.config.bak to scs.config

# cp scs.config.bak scs.config
12. Login to the SCS client 5.0.2. The GGSNs in the region will be out of sync in case SCS 6.0 post upgrade scripts were executed or any provisioning changes were made from the SCS. Resync of the GGSN is required in case the GGSN show out of sync.
411-5221-309 Standard 06.30 March 10, 2010
13. <<IN CASE OF CLEAN UP IPLANET INSTANCE MUST BE IDENTIFIED, DELETED, SCS ROOT DELETED>>
urc2y1th# pwd /opt/shasta/scs6.0/bin urc2y1th# del crontab for LDAPWatch urc2y1th# ./SCSAdmin stop urc2y1th# urc2y1th# cat .scs.config # # This file was generated during SCS installation. # Please do not modify manually. # InstallDomainServer=yes InstallRegionServer=yes InstallMonitorServer=yes InstallPullServer=yes InstallLogServer=yes DomainServerIp=localhost RegionId=99 LDAPUsername="uid=admin,ou=Administrators,ou=TopologyManage ment,o=NetscapeRoot" LDAPPassword=admin LDAPRoot="uid=UShasta,ou=People,o=us.nortel.com" PullListenPort=4321 LogLogPort=4322 LogAccountPort=4323 DBAdminPassword=admin MaximumHeapSize=512 DBBackupTimeWait=300 DOMAIN_IP=localhost IIOP=0 RegionRootDir=/opt/shasta/scs6.0 SCSHead=/opt/shasta/scs6.0 LDAPPath=/opt/shasta/iplanet LDAPServerName=slapd-urc2y1th1 LDAPServerIp=localhost LDAPServerPort=390 SCSBackup=/opt/shasta/scs6.0/backup LogUser=pmuser urc2y1th# urc2y1th# urc2y1th# cd LDAPPath/ LDAPPath/: No such file or directory urc2y1th# cd LDAPServerName LDAPServerName: No such file or directory urc2y1th# stop process stop: Arguments should be jobs or process id's urc2y1th# cd .. urc2y1th# rm -rf LDAPServerName urc2y1th# urc2y1th# ls LDAPServerName LDAPServerName: No such file or directory urc2y1th# cd /opt/shasta/iplanet urc2y1th# cd slapd-urc2y1th1 GPRS/UMTS Upgrade Manual GGSN6.0
378
SCS 6.0 to SCS 5.0.2 Rollback procedure urc2y1th# urc2y1th# urc2y1th# urc2y1th# urc2y1th# urc2y1th#
./stop-slapd cd ../ rm -rf slapd-urc2y1th1 cd ../ rm -rf scs6.0
411-5221-309
Standard
06.30 March 10, 2010
Clean up procedure in case of upgrade failure for SCS 4.1.2 to 6.0 upgrade 379
Clean up procedure in case of upgrade failure for SCS 4.1.2 to 6.0 upgrade
Pre-requisite:
22
a. This procedure can be run only to clean up SCS 6.0 installation incase SCS 6.0 or iPlanet processes don't start after SCS 6.0 upgrade. b. The server has not been activated to Solaris 9. Starting point: Server is running SCS 6.0 on Solaris 8. Run the command uname to find out if the server is running on Solaris 8. # uname -rm 5.8 sun4u Please take a note of SCS 6.0 and iPlanet installation directory before proceeding. To find the current SCS and iPlanet installation directories:
# cat /etc/shasta/scs.config | grep SCSHead Example:
SCSHead=/opt/shasta/scs <SCS6.0_ROOT> = SCSHead = /opt/shasta/scs5.0
# cat /etc/shasta/scs.config | grep LDAPPath Example:

1. 1. Disable LDAPWatch and SCSWatch

Example:
# cd /opt/shasta/scs6.0/bin
GPRS/UMTS
380
Clean up procedure in case of upgrade failure for SCS 4.1.2 to 6.0 upgrade # ./LDAPWatch-disable # ./SCSWatch-disable
2. Stop SCS 6.0

<SCS6.0_ROOT>/bin/SCSAdmin stop
Example:
# pwd /opt/shasta/scs6.0/bin # ./SCSAdmin stop
3. Verify SCS 6.0 processes are stopped

<SCS6.0_ROOT>/bin/SCSAdmin status
Example:
# ./SCSAdmin status
4. . Stop LDAP iplanet processes

<IPLANET_ROOT>/slapd-<hostname>/stop-slapd <IPLANET_ROOT>/stop-admin
Example:
# cd /opt/shasta/iplanet # slapd*/stop-slapd # ./stop-admin
5. . Verify LDAP iplanet processes are stopped

# ps aef | grep v grep | grep slapd <-the above command must not return a result # ps aef | grep v grep | grep admin <-the above command must not return a result)
If the above ps command returns a result, stop the processes. 6. . Uninstall iPlanet directory server and remove iplanet installation directory.
411-5221-309 Standard 06.30 March 10, 2010
Clean up procedure in case of upgrade failure for SCS 4.1.2 to 6.0 upgrade 381
# cd <IPLANET_ROOT> # ./uninstall
Example:
# cd /opt/shasta/iplanet # ./uninstall
(hit enter to select default) When prompted for: Would you like to continue with local uninstallation? [No]: Yes Answer Yes See Appendix H: Example capture of iPlanet server uninstallation on page 656 for an example of the uninstallation procedure. 7. After the uninstall procedure completes, remove iplanet installation directory
8. Move SCS 6.0 installation directory in /opt. Example:

# cd /opt/shasta # mv scs6.0 scs6.0_temp
9. After a successful SCS 6.0 upgrade is complete, delete the directory scs6.0_temp.
<<End of Procedure>>
GPRS/UMTS
382
Clean up procedure in case of upgrade failure for SCS 5.0.2 to SCS 6.0
1. Verify if iPlanet instance has been created
# cd <IPLANET_ROOT> # ls
23
The following section explains the steps to execute to clean up incomplete SCS server upgrade directories.
Note 1: Please note that there are 2 iPlanet instances in <IPLANET_ROOT>, slapd-<hostname> and slapd-<hostname>1. slapd<hostname>1 is created during SCS 5.0.2 upgrade. Note 2: Replace <hostname>1 with your server hostname appended with 1.
Here is an example: # cd /opt/shasta/iplanet # ls admin-serv httpacl admin adminacl include startconsole admserv install alias java bin lib dist manual
plugins restart-admin
start-
setup stop-admin shared uninstall slapd-urc2y1th userdb slapd-urc2y1th1
2. If slapd-<hostname>1 directory exists, then change directory to slapd<hostname>1. If the directory does not exist, then skip this step and do to the step to delete <SCS502_ROOT> directory below. If slapd<hostname>1 exists, then change directory to slapd-<hostname>1, execute stop-slapd, then delete the directory <IPLANET_ROOT>/slapd<hostname>1. Note: MAKE SURE YOU DELETE ONLY SLAPD-<hostname>1. DO NOT DELETE SLAPD-<hostname>.
# # # # cd slapd-<hostname>1 ./stop-slapd cd ../ rm -rf slapd-<hostname>1
Here is an example: 411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential # # # #
383
cd slapd-urc2y1th1 ./stop-slapd cd ../ rm -rf slapd-urc2y1th1
3. Change directory to /opt/shasta (or where <SCS6.0_ROOT> was created). Remove directory <SCS6.0_ROOT>.
Here is an example: # cd /opt/shasta # rm -rf scs6.0
4. Proceed to Upgrade GGSN SCS from 5.0.2 to 6.0 on page 274
GPRS/UMTS
384
Backup and Restore Procedures for SCS with a Tape Drive
Backup and Restore Procedures for SCS with a Tape Drive 24

There are three types of backups for the data on the SCS server: essential: backs up the GGSN provisioning data, historical alarms, SCS configuration and system management data dynamic: backs up the logs and performance counters full system: backs up the operating system, the SCS application software, dynamic data as defined previously, and essential data as defined previously
The procedures in this section explain how to perform local or centralized backup and restore for essential data and dynamic data. Full system backup and restore is performed locally only. There are also procedures for backing up and restoring the Lightweight Directory Access Protocol (LDAP) and SOLID databases on the SCS server. In the procedures in this section the following variables are used: 1. <SCS_ROOT> indicates the directory which contains the SCS installation. For example, <SCS_ROOT> = /opt/shasta/scs 2. <LDAP_ROOT> indicates the directory specified at Netscape Directory server installation. For example, <LDAP_ROOT> = /opt/shasta/ldap The absolute path of the LDAP software on an existing system is stored in the file: /etc/shasta/scs.config with the following value: LDAPPath=<absolute path of LDAP installation> Note: The Restore procedure should be only performed on a system that has the exact hardware configuration as the system that the backup data was taken from. For example: The types and number of cards configured on the devices that the server connect to should be the same before the backup and after the restore.
411-5221-309
Standard
06.30 March 10, 2010
385
Local backup
This section contains procedures for performing local backup of essential data, dynamic data, and full system data. Note: Each time local backup is done, the tape is re-wound and ejected automatically. Backing up essential data to tape 1. Log into the SCS server to be backed up using the root user Id. 2. In a command line window enter:
24
<SCS_ROOT>/bin/SCSAdmin tape{=/dev/rmt/<number>} backup system <delay>

where{=dev/rmt/<number>} specifies the tape drive destination, <number> is the tape drive number. This parameter is optional; if you omit it, it defaults to =/dev/rmt/0 where<delay> is the time in seconds to wait before starting the backup
Backing up dynamic data to tape 1. Log into the SCS server to be backed up using the root user Id. 2. In a command line window enter: <SCS_ROOT>/bin/SCSAdmin tape{=/dev/rmt/<number>} archive log
where{=dev/rmt/<number>} specifies the tape drive destination, <number> is the tape drive number. This parameter is optional; if you omit it, it defaults to =/dev/rmt/0
Backing up the full system See Performing a full system backup on page 399.
Local Restore
24
The procedures in this section contain procedures for performing local restore of essential data, dynamic data, and full system data. Note: Each time local restore is done, the tape is re-wound and ejected automatically.
Restoring essential data 1. Log into the SCS server to be restored using the root user Id. 2. In a command line window enter:
GPRS/UMTS
386
<SCS_ROOT>/bin/SCSAdmin tape{=/dev/rmt/<number>} restore system <delay>

where{=dev/rmt/<number>} specifies the tape drive destination, <number> is the tape drive number. This parameter is optional; if you omit it, it defaults to =/dev/rmt/0 where<delay> is the time in seconds to wait before starting the backup
Restoring dynamic data 1. Log into the SCS server to be backed up using the root user Id. 2. In a command line window enter: <SCS_ROOT>/bin/SCSAdmin tape{=/dev/rmt/<number>} retrieve log
where{=dev/rmt/<number>} specifies the tape drive destination, <number> is the tape drive number. This parameter is optional; if you omit it, it defaults to =/dev/rmt/0
Note: Data is restored to a date coded directory when the backup was taken, not the original log directory. This way the retrieved data will not override the current log data in the log directory. The file format is "log_YYYY_MM_DD", where YYYY is the year, MM is the month, and DD is the day the backup was taken. For example, if the backup was taken at Feb 11, 2005, when you retrieve the data from the tape, the data will be put in log_2005_02_11 directory. Restoring the full system See Performing a full system restore on page 407.
Centralized backup
24
VERITAS NetBackup* is a third party tool used for centralized backup. The data can be backed up locally on each server or from (and/or to) a central location using VERITAS NetBackup*. For more information about VERITAS NetBackup, refer to the following VERITAS documents, which are available on http://www.sun.com: VERITAS NetBackup 5.0 System Administrator's Guide Volume I for UNIX VERITAS NetBackup 5.0 System Administrator's Guide Volume II for UNIX VERITAS NetBackup 5.1 Installation Guide for UNIX VERITAS NetBackup 5.0 User's Guide for UNIX
Before performing the procedures in this section you must:
411-5221-309
Standard
06.30 March 10, 2010
387
install the VERITAS NetBackup server software on the SCS server as described in VERITAS NetBackup 5.1 Installation Guide for UNIX install the VERITAS NetBackup client software on each SCS server as described in Installing the VERITAS client software on page 387 /etc/hosts file needs to be updated on each of the SCS servers and the VERITAS NetBackup server On the SCS server, update /etc/hosts with: <Veritas server IP> <hostname> On the Veritas server, update /etc/hosts with: <SCS server IP> <hostname>
Installing the VERITAS client software This procedure installs the VERITAS client software on the SCS server(s). This procedure must be performed after you install the VERITAS NetBackup server software and before you attempt the first backup of the SCS server. The client in the steps below refer to the SCS server. 1. Log in as root into the VERITAS NetBackup server. 2. Move software from the VERITAS NetBackup server to temporary space in the /tmp directory on the client by executing the install_client_files script from the NetBackup server. To execute this script, you must have a login ID and password that you can use to access the clients through ftp. 3. Type the following command: /usr/openv/netbackup/bin/install_client_files ftp <client> <user> where: <client> is the hostname of the SCS server <user> is the user Id required by ftp on the SCS server. If OS Hardening is installed on the SCS server, you must use a user Id other than root. The install_client_files script prompts you for a password for each of the SCS servers. 4. Log into the SCS server that you installed the backup and restore scripts on, using the root user Id. 5. Type the following command: sh /tmp/bp/bin/client_config
388
The client_config script installs the binaries and updates the /etc/services and inetd.conf files on the SCS server. 6. Edit the file /usr/openv/netbackup/bp.conf. Look for the following lines. If these lines do not exist in the file, add the appropriate information: SERVER = <NetBackup server host name> CLIENT_NAME = <SCS server host name> 7. Save and close the bp.conf file. 8. Perform step 4. and step 7 for each SCS server that you installed the backup and restore scripts on. Performing a backup Before performing a backup you must define a backup policy in NetBackup. A backup policy defines the server to back up, the files and directories to be backed up, the type of backup, where to store the backed up files, and the frequency of the backup. For more information about backup policies and how to schedule automated backups, refer to the VERITAS NetBackup documentation. You must be familiar with and know how to perform the following tasks using VERITAS NetBackup: create and configure a policy back up the data on a server restore the data to a server monitor NetBackup activity
Configuring a backup policy 1. Log into the Netbackup server or client using the root user Id. 2. In a command line window, type: /usr/openv/netbackup/bin/jnbSA & 3. Enter the Host name, User, and Password of the server that has the VERITAS NetBackup installed. 4. Click on Login. 5. Click on the Create a Backup Policy icon.
The Backup Policy Configuration Wizard window opens.
6. Click on Next.
411-5221-309 Standard 06.30 March 10, 2010
389
7. In the Policy name field, type <hostname>_NNunix where <hostname> is the SCS server host name associated with the Ethernet port in the B&R subnet. Select Standard for the Policy type from the drop-down list. 8. Click on Next. 9. In the Client List window, click on Add. 10. In the Add Client window, in the Client name field, type the IP address or host name of the SCS server to be backed up. For the Hardware and operating system field, select Solaris, Solaris8/Solaris9 from the dropdown list. 11. Click on OK.
The SCS server appears in the Client list.
12. Click on Next. 13. In the Files window, click on Insert. 14. In the list under Pathname or Directive, type: <SCS_ROOT>/backup 15. In the Files window, click on Add. 16. In the list under Pathname or Directive, type: <SCS_ROOT>/log 17. Click on Next. 18. In the Backup Type window, select the Full Backup box. 19. Click on Next. 20. In the Rotation window, specify how often to run full backups and how long to retain the data for them. 21. Click on Next. 22. In the Start window, specify the time window during which backups are allowed to start. 23. Click on Next. 24. Click on Finish. In the pop-up window asking if you want to create another policy, click No. The backup policy appears in the list on the right side of the Backup Policy Management window. 25. Log on to the SCS Server as root cd into /usr/openv/netbackup/bin, create soft link as follows:
390
ln -s <SCS_ROOT>/bin/centralEssenVeritasPre.sh bpstart_notify.<policy_name> ln -s <SCS_ROOT>/bin/centralEssenVeritasPost.sh bpend_notify.<policy_name> policy_name is the one you put in step 7 above. 26. Click on the left side of the main screen to display the list of defined policies. 27. On the right side of the Backup Policy Management window, doubleclick on the backup policy you just created. 28. In the Change Policy window, in the Policy storage unit field, select the tape device to be used for backing up the server. Ensure that the Allow multiple data streams field is not selected. Ensure that the Compression field is not selected. 29. Click on OK. 30. In the middle panel of the Backup Policy Management window, click on Schedules under the new backup policy. 31. On the right side of the Backup Policy Management window, doubleclick on the schedule Name Full in the schedule list. 32. In the Change Schedule window, click on the Start Window tab. 33. In the Start Window tab, specify the Start time and Duration fields. 34. Click on OK.
Centralized restore
VERITAS NetBackup is a third party tool used for centralized restore. For detailed information on how to perform a restore using VERITAS NetBackup, see the VERITAS NetBackup documentation. Performing centralized restore 1. Log into the Netbackup server or client using the root user Id. 2. In a command line window, type: /usr/openv/netbackup/bin/jnbSA & 3. Enter the Host name, User, and Password of the server that has the VERITAS NetBackup installed. 4. Click on Login. 5. Click on Backup, Archive, and Restore on the left side of the window.
24
411-5221-309
Standard
06.30 March 10, 2010
391
6. Ensure that the NetBackup server field shows the host name of the NetBackup server. 7. Ensure that the Source client field is the host name or IP address of the SCS server whose data you want to restore. a. Click on the hand icon in the upper right corner of the window. The Specify NetBackup Machines window opens. b. In the Source client / Policy type tab, enter the host name or IP address in the New client name: field. c. Click the Add button. The new name or address is added to the Client list portion of the window. d. Click to select the new name or address from the list, and click on the Make Current button. e. Click the OK button in the bottom left corner of the window. The name or address appears in the Source client: field in the main window. 8. Ensure that the Destination client field is the host name or IP address of the SCS server to which you want data restored. a. Click on the hand icon in the upper right corner of the window. The Specify NetBackup Machines window opens. b. In the Destination client tab, enter the host name or IP address in the New client name: field. c. Click the Add button. The new name or address is added to the Client list portion of the window. d. Click to select the new name or address from the list, and click on the Make Current button. e. Click the OK button in the bottom left corner of the window. The name or address appears in the Destination client: field in the main window. 9. In the Restore Type field, select Normal Backups from the drop-down list. 10. Under Browse directory, type: / 11. Press the Enter key. 12. Select the directory(s) or folder(s) that you want to restore. 13. Click on Restore.
GPRS/UMTS
392
14. In the Restore Files window, if you are restoring essential data, specify a destination directory of <SCS_ROOT>/backup. If you are restoring dynamic data, leave the destination directory empty. 15. Click on Start Restore. 16. Look at the status of the restore job using the Activity Monitor. The restore is successful if it has a status of 0 when it is finished. 17. If you are restoring dynamic data, you have completed this procedure. If you are restoring essential data, go to step18. 18. Log into the SCS server that you are restoring using the root user Id. 19. In a command line window enter: <SCS_ROOT>/bin/SCSAdmin restore system <delay>
where<delay> is the time in seconds to wait before starting the restore
411-5221-309
Standard
06.30 March 10, 2010
393
25
A full system backup should be performed whenever changes to the SCS operating system or application are made. However, more frequent backups of the configuration data stored in the SCS databases should be performed as described in Database backup procedure for SCS on page 242. Note: For mirrored servers, full system backup and restore backups critical file systems such as /, /usr, /var and /opt. Verify /etc/vfstab for the mounted file systems. If there are other mounted file systems such as / export/home, please follow Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems for Mirrored Servers on page 627. Full system backup and restore provides the ability to back up all OS, applications, and data on to tape. The tapes can be used to restore the same server to the configuration at the time the backup was performed. Nortel provides instructions for an SCS running on an certain platforms with a specific configuration described in Full system backup and restore system requirements on page 394. If a procedure is required, there is a large amount of information in the public domain. For instance, see Sun Microsystems BigAdmin System Administration Portal at: http://www.sun.com/bigadmin/scripts/indexBackup.html The following sections describe: Full system backup and restore system requirements Impact of a full system backup and restore Installing the backup and restore package Performing a full system backup Performing a full system restore
GPRS/UMTS
394
Full system backup and restore system requirements

Table 22 shows the hardware that is supported for full system backup and restore.
Table 22 Supported hardware for full system backup and restore SCS Version GGSNS4.1.1 GGSN 5.0/ 5.0.1 GGSN 6.0 Server Type E250, SF V880, SF V250, E 450 E250, SF V880, SF V250, E 450, SF V890, Netra 240 SF V880, SF V250, SF V890, Netra 240
25
Note: Full server tape backup is not supported on Sun T5220. For this feature, it is required that all components of SCS Server (LDAP, domain server, region server etc) are installed on the same physical server. Full system backup and restore resource needs Resources needed to complete Full System Backup/Restore procedure One technician, familiar with the UNIX system and OAM commands File systems are saved on DAT therefore a DAT drive (DDS4) is required on the machine to backup. To perform the full restore, the CD-ROM of the Solaris system (version 2.8/2.9): For Solaris 8: this is the CD-ROM labeled "Solaris 8 software | 1 of 2". For Solaris 9: this is the CD-ROM labeled "Solaris 9 software | 1 of 2" 20-40 Gbyte DDS4 DAT For non-mirrored servers, all partitions are backed up to 1 DDS4 tape. For mirrored servers: Critical partitions (/, /usr, /var and /opt) are backed up to 1 DDS4 tape.
Each non-critical partition must be backed up to separate DDS4 tapes. For example, non-critical partition /export/home must be backed up to 1 DDS4 tape.
Impact of full system backup and restore The impact of performing a full system backup is as follows: The SCS will be unavailable to manage GGSN while the backup is under way. Configuration of the GGSN is not possible while the SCS is unavailable.
411-5221-309
Standard
06.30 March 10, 2010
395
Fault and performance monitoring of the GGSN from the SCS is not possible while the SCS is unavailable. However, other monitoring systems (such as Preside for Wireless Internet) can continue to provide fault surveillance of GGSNs. There is no impact to traffic There is no need to resync the GGSN upon completing the backup.
The impact of performing a full system restore are: All information on the SCS is replaced with the backup Any provisioning since the last Solid and LDAP database backup is lost Any historical information since the last full system backup is lost After the SCS is restored, a resync of each GGSN is required
Nortel recommends that you frequently back-up and store off-line, the Solid and LDAP database information. The most recent copy should be restored in addition to the full system restore to minimize loss of configuration information.
Installing the backup and restore software package
25
The Nortel Backup and Restore software NNBRSCS.pds is included on the SCS 6.0 CD. Note: Use this package to perform a full server backup and restore on SCS 6.0, SCS 5.0.2 and SCS 4.1.2. Pre-work The backup and restore package requires the presence of a a userid nortel which is a member of the user group nortel on the SCS prior to installing the NNBRSCS.pds package. The nortel userid and user group must be created through normal administrative means. Check with your Solaris system administrator for the process to create a new user group and userid on the SCS server. Example Solaris commands which can be used to create a new user group and userid on a server are: groupadd, useradd, and passwd. 1. Determine if unix group nortel and user nortel have already been added. Verify that an entry for nortel exists in /etc/group and /etc/passwd
# more /etc/group | grep nortel # more /etc/passwd | grep nortel
2. If the above commands do not return a value - nortel, then add group nortel and user nortel.
396
Full System backup and restore # groupadd nortel # useradd -g nortel nortel
3. Verify if NNbrscs package is installed on the server.

# pkginfo -l NNbrscs
If pkginfo returns a result, remove the package using:

# pkgrm NNbrscs
4. Verify if NNBRSCS package is already installed on the server.

# pkginfo -l NNBRSCS | grep "VERSION*" VERSION: V05_00.E03
a. If the above command does not return a result, then install the NNBRSCS.pds package from the SCS 6.0 CD following the procedure Installation of backup and restore software package. b. If pkginfo -l NNBRSCS returns a result and the VERSION does not match V05_00.E03, then remove the installed package using:
# pkgrm NNBRSCS
After removing NNBRSCS, install NNBRSCS package from SCS 6.0 CD following the procedure Installation of backup and restore software package. c. If pkginfo -l NNBRSCS returns a result and VERSION matches V05_00.E03, then proceed to the Backup Procedure - Performing a full system backup.
Installation of backup and restore software package
25
1. The SCS Server backup/restore software is on the GGSNS6.0 SCS CD and is named NNBRSCS.pds for PC06. Insert SCS 6.0 CD and verify the mount point
# df -k Filesystem kbytes used Mounted on /vol/dev/dsk/c0t2d0/ggsn0061 407692 407692 ggsn0061 # cd /cdrom/ggsn061/Solaris # cp NNBRSCS.pds /tmp avail capacity
100%
/cdrom/
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential # cd /tmp
397
2. The software can be installed by executing the following command

# pkgadd -d NNBRSCS.pds When prompted for:
Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: all (Answer all) Do you want this directory created now [y,n,?,q] y (Answer y) Do you want to install these conflicting files [y,n,?,q] y (Answer y) Do you want to continue with the installation of <NNBRSCS> [y,n,?] y (Answer y) Here is an example installation capture:
# pkgadd -d NNBRSCS.pds The following packages are available: 1 NNBRSCS Backup and Restore tools for SCS (sparc) V05_00.E03 Select package(s) you wish to process (or 'all' to process all packages). (default: all) [?,??,q]: all Processing package instance <NNBRSCS> from </BR/NNBRSCS.pds> Backup and Restore tools for SCS (sparc) V05_00.E03 /*********************************************************************** *** *** *** Copyright Notice *** *** @ 2002 Nortel Networks *** *** *** *** This software embodies materials and concepts which are *** *** confidential to Nortel Networks and is made available solely *** *** pursuant to the terms of a written licence agreement with *** *** Nortel Networks or its licenced distributor. *** *** *** *** Copyright @ 1996, 1997 Original Reusable Objects, Inc. *** *** *** *** Restricted Rights legend: *** *** ------------------------- *** *** Under FAR 27.405(b)(2) and DFAR 227.7202-3: Use, modification, *** *** reproduction, release, performance, display, or disclosure by ***
GPRS/UMTS
398
*** the U.S. Government is subject to restrictions set forth in *** *** subdivision (c)(1) of FAR 52.227-19. *** *** *** ***********************************************************************/ ## Executing checkinstall script. Using </opt/nortel> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. The following files are already installed on the system and are being used by another package: * /opt/nortel <attribute change only> * - conflict with a file which does not belong to any package. Do you want to install these conflicting files [y,n,?,q] y ## Checking for setuid/setgid programs. This package contains scripts which will be executed with super-user permission during the process of installing this package. Do you want to continue with the installation of <NNBRSCS> [y,n,?] y Installing Backup and Restore tools for SCS as <NNBRSCS> ## Installing part 1 of 1. /usr/local/nortel/tools/bin/ds_backup.ksh /usr/local/nortel/tools/bin/ds_exportEnv.awk /usr/local/nortel/tools/bin/ds_restore.sh /usr/local/nortel/tools/bin/ds_scsbackup.ksh /usr/local/nortel/tools/bin/ds_scsrestore.sh /usr/local/nortel/tools/cfg/ds_BR.env /usr/local/nortel/tools/etc/init.d/mirror /usr/local/nortel/tools/etc/init.d/nxt-step /usr/local/nortel/tools/lib/ds_brLib.lib /usr/local/nortel/tools/lib/ds_cmnLib.lib /usr/local/nortel/tools/lib/ds_logMgt.lib /usr/local/nortel/tools/lib/ds_system.lib [ verifying class <none> ] ## Executing postinstall script. Installation of <NNBRSCS> was successful.
411-5221-309
Standard
06.30 March 10, 2010
399
Removal of backup and restore software package

These scripts can be removed by executing the following command
# pkgrm NNbrscs.pds
25
Performing a full system backup
25
Table 23 describes the basic steps in backing up the SCS Server with approximate timings. This procedure only applies for the configuration described above. For more details on configuration, Full system backup and restore system requirements on page 394. Note: If the configuration does not match the described configuration, full system backup is a local customer responsibility.
Table 23 Basic SCS server backup steps and timings Step 1. 2. 3. 4. 5. 6. Backup SCS and LDAP/ iPlanet using SCSAdmin backup system Stop the SCS applications Check and modify the /etc/lvm/md.tab if needed (This step is only applied to mirrored Solaris server). Depending on the type of server installation, execute Disk Check for SCS for mirrored server or Disk Check for SCS for non-mirrored server Log on in single user mode Backup the SCS Server (Ignore any Warning messages that appear during the backup. Also, the time taken would vary based on the size of the system. The time might vary form 1 hour to multiple hours.) Restart the SCS applications For mirrored servers only: Backup any mounted non-critical filesystems. Restart the SCS applications Time (minutes) 10 10 10 20 10 30~180
7. 8. 9.
10 30~120 5
Perform SCS and LDAP/ iPlanet backup Perform a SCS and LDAP/ iPlanet backup using Option 2: SCS backup using SCSAdmin on page 242.
GPRS/UMTS
400
Stopping the SCS applications

1. If not already done, log in to the SCS Server with the root login and password.
25
2. Determine the SCS installation directory, disable LDAPWatch, stop SCS server processes:
# cat /etc/shasta/scs.config | grep SCSHead # cd <Path returned for SCSHead> # cd bin # ./LDAPWatch-disable # ./SCSAdmin stop # ./SCSAdmin status
3. Determine the LDAP/ iPlanet installation directory.

# cat /etc/shasta/scs.config | grep LDAPPath # cd <Path returned for LDAPPath> # cat /etc/shasta/scs.config | grep LDAPServerName # cd <Path returned for LDAPServerName> Stop LDAP/ iPlanet directory server instance: #./stop-slapd
4. Stop LDAP/ iPlanet admin server process

# cd ../ #./stop-admin
5. Verify if the server is mirrored or non-mirrored. Issue the following command. If the command returns a result, then the server is mirrored. If the command returns Command not found, then the server is nonmirrored.
# /usr/sbin/metastat
Note: Skip the next step if the SCS is non-mirrored. Proceed to Full server backup procedure on page 402. 6. If the SCS server is mirrored, check and modify the /etc/lvm/md.tab.
411-5221-309
Standard
06.30 March 10, 2010
401
To find out if your server is mirrored, run df -k. If mount points (/, /var, /opt, etc) have Filesystem as /dev/md/dsk/d<num>, then the server is mirrored. a. Find the unique metadb partitions configured on the server
# metadb
a m a a a a a a a a a a a flags p luo p luo p luo p luo p luo p luo p luo p luo p luo p luo p luo p luo first blk 16 8208 16400 16 8208 16400 16 8208 16400 16 8208 16400 block count 8192 /dev/dsk/c1t0d0s3 8192 /dev/dsk/c1t0d0s3 8192 /dev/dsk/c1t0d0s3 8192 /dev/dsk/c1t8d0s3 8192 /dev/dsk/c1t8d0s3 8192 /dev/dsk/c1t8d0s3 8192 /dev/dsk/c1t1d0s3 8192 /dev/dsk/c1t1d0s3 8192 /dev/dsk/c1t1d0s3 8192 /dev/dsk/c1t9d0s3 8192 /dev/dsk/c1t9d0s3 8192 /dev/dsk/c1t9d0s3
Here c1t0d0s3, c1t8d0s3, c1t1d0s3, c1t9d0s3 are the unique metadb partitions. b. Determine the mirroring configuration using metastat -p.
# metastat -p d0 -m d10 1 d20 1 d1 -m d11 1 d21 1 d5 -m d15 1 d25 1 d7 -m d17 1 d27 1 d8 -m d18 1 d28 1 d10 d20 1 1 c1t0d0s0 1 c1t8d0s0 d11 d21 1 1 c1t0d0s1 1 c1t8d0s1 d15 d25 1 1 c1t0d0s5 1 c1t8d0s5 d17 d27 1 1 c1t0d0s7 1 c1t8d0s7 d18 d28 1 1 c1t1d0s0 1 c1t9d0s0
c. Update the file /etc/lvm/md.tab file with the values obtained from metadb and metastat -p (above) using the following steps. Clear out /etc/lvm/md.tab
# cat /dev/null > /etc/lvm/md.tab
Add a line starting with mddb01 followed by the unique partitions obtained from metadb
GPRS/UMTS
402
Full System backup and restore Example:
mddb01 c1t0d0s3 c1t8d0s3 c1t1d0s3 c1t9d0s3
Update /etc/md.tab with metastat -p. Note: Use >> after metastat -p
# metastat -p >> /etc/lvm/md.tab
The modified /etc/lvm/md.tab is:

Full server backup procedure
25
Before proceeding to the backup procedure, verify the disks are free of errors or corruption by following Appendix I: Disk Check for SCS for nonmirrored servers on page 661 or Appendix J: Disk Check for SCS for mirrored server on page 664 depending on the server installation. Log in to single user mode 1. Change the run level to 0 (Go to Open Boot PROM prompt):
# sync;sync;sync # init 0
2. On the Open Boot PROM (OBP) prompt, boot the machine in single user mode: {0} ok boot -rs 3. Wait for the single user login prompt and then give the root password to enter in system maintenance mode. After the boot you will see:
411-5221-309
Standard
06.30 March 10, 2010
403
Type control-d to proceed with normal startup, (or give the root password for system maintenance)
Enter the root password. Backup the SCS server 1. Move to the following directory:
# cd /usr/local/nortel/tools/bin
2. Put a tape in the tape drive and launch the following command:
# ./ds_backup.ksh
(For SCS 3.2.1 only) Then put a tape in the tape drive for each request of the script. Dont forget to label each tape with the name of the host, the date and the name of current set of tapes (SYSTEM, APPLICATION, and DATA) and then to enable the data protector (open the erasure prevention slide of the tape). You will need at least two tapes. If the size of data exceeds the size of the tape, the following message is displayed:
DUMP : End-of-tape detected DUMP : Change Volumes : Mount volume'#2' on 'hostname:/dev/ rmt/0cn' DUMP : NEEDS ATTENTION : Is the new volume (#2) mounted on 'hostname:/dev/rmt/0cn' and ready to go : ("yes" or "no")
You must: Eject the previous tape Put a non-protected tape in the tape driver Answer yes and then press the [ENTER] key. The backup of the data continues. If you put in a protected tape, the script displays the following message:
DUMP: NEEDS ATTENTION: Cannot open `hostname:/dev/rmt/0cn'. Do you want to retry the open? ("yes" or "no")
You must: Eject the protected tape Put a non-protected tape in the tape driver Answer yes and then press the [ENTER] key. The backup of the data continues. When it is finished you will see:
GPRS/UMTS
404
Building data tape, please wait......... =========================================== ejecting data tape. Please wait........................ Please write protect data tape Please ENTER to continue ===============END OF BACKUP PROCEDURE=======
For GGSNS4.0.1/GGSNS4.1.x/GGSNS5.0 and GGSNS6.0, this is simpler since one tape is needed.
During the backup, monitor the console logs. Look for logs similar to the following. This indicates all the critical file systems - /, /var and /opt and backed up.
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential ... drwxr-xr-x 8 nortel nortel -rw-r--r-- 1 root other
405
512 Mar 29 01:00 tools 709 Mar 29 01:00 vfstab
c1t0d0s0;d0;/;system c1t0d0s5;d5;/var;system c1t1d0s0;d8;/opt;application ... b. Verify / is backed up: Wed Mar 29 01:01:06 CST 2006 : Dump of /dev/md/rdsk/d0... DUMP: Writing 32 Kilobyte records DUMP: Date of this level 0 dump: Wed Mar 29 01:01:07 2006 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d0 (urc2y3pa:/) to /dev/rmt/0cn. DUMP: DUMP IS DONE DUMP: Level 0 dump on Wed Mar 29 01:01:07 2006 Wed Mar 29 01:07:31 CST 2006 : Dump of / (c1t0d0s0 - d0 - system).Done
c. Verify /var is backed up: Wed Mar 29 01:07:31 CST 2006 : Dump of /var (c1t0d0s5 - d5 - system)... Wed Mar 29 01:07:32 CST 2006 : Dump of /dev/md/rdsk/d5... DUMP: Writing 32 Kilobyte records DUMP: DUMP IS DONE DUMP: Level 0 dump on Wed Mar 29 01:07:33 2006 Wed Mar 29 01:08:51 CST 2006 : Dump of /var (c1t0d0s5 - d5 - system).Done
d. Verify /opt is backed up

Wed Mar 29 01:08:51 CST 2006 : /opt not mounted. Processing sanity check... Wed Mar 29 01:08:52 CST 2006 : Sanity check of /opt OK. Wed Mar 29 01:08:52 CST 2006 : Dump of /opt (c1t1d0s0 - d8 - application)... Wed Mar 29 01:08:52 CST 2006 : Dump of /dev/md/rdsk/d8... ... Wed Mar 29 01:28:08 CST 2006 : Dump of /opt (c1t1d0s0 - d8 - application).Done Wed Mar 29 01:28:08 CST 2006 : Dumping to "SYSAPPDATA" tape...Done
GPRS/UMTS
406
Non-mirriored server: This completes the backup procedure for nonmirrored servers. Please refer to Restart the SCS applications on page 406 to reboot the server and start the SCS server processes. Mirrored server: For mirrored servers, only critical filesystem partitions are backed up by the backup script. To backup the mounted non-critical filesystem partitions, please refer to Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems for Mirrored Servers on page 627 After backing up the non-critical filesystems, please refer to Restart the SCS applications on page 406 to reboot the server and start the SCS server processes.
Restart the SCS applications
25
Once the backup is complete, you need to go to the next run level. Normally the SCS is configured to start its processes after system restart. If not, you can start them manually. 1. Reboot the server to multiuser mode # sync;sync;sync
# init 6
2. After the server reboots, verify if the LDAP (or iPlanet) process and SCS server processes are running.
# ps -aef | grep SCS # ps -aef | grep slapd # ps -aef | grep admin
3. If the processes are not running, start the processes. Determine the LDAP/ iPlanet installation directory.
4. Start LDAP/ iPlanet directory server instance:

#./start-slapd
5. Start LDAP/ iPlanet admin server process

411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential # cd ../ #./start-admin
407
# cat /etc/shasta/scs.config | grep SCSHead # cd <Path returned for SCSHead> # cd bin # ./LDAPWatch-enable # ./SCSAdmin start # ./SCSAdmin status
If the SCS server process do not start, indicating an solid error similar to Solid Database Engine process has encountered an internal error and is unable to start, please refer to section Steps to recover from Solid database corruption issue on page 482 to fix the issue. Please refer to Full Server Backup on page 783 for example capture of a Full server backup for a mirrored server on Solaris 8. At the end of this capture, a capture of a Full server backup for a non-mirrored server is included.
Performing a full system restore
25
Table 24 describes the basic steps in restoring up the SCS Server and list their approximate timings. This applies for the configuration described in section Full system backup and restore system requirements on page 394. If the configuration does not match the described configuration, full system restore is a local customer responsibility. Full system restore should only be carried out as a last option.
Table 24 Basic SCS server restore steps and timings Step 1. Log on in single user mode with the Solaris system CD-ROM Time (minutes) 10
GPRS/UMTS
408
Table 24 Basic SCS server restore steps and timings (continued) 2. Restore the SCS Server (The time taken for Restore will be approximately equal to backup time.) 70~200 for small system ~180 to more than 360 (a large system) 3. For Mirrored servers only: only critical file systems (/, swap, /var and /usr) are restored during the full server restore. The non-critical file systems need to be restored manually. Follow the procedure in Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems for Mirrored Servers on page 627. Depending on the type of server installation, execute the procedure in either Appendix J: Disk Check for SCS for mirrored server on page 664 or Appendix I: Disk Check for SCS for non-mirrored servers on page 661. Start SCS processes Resync GGSN(s) 30
4.
20
5. 6.
10 10
Prior to restoring the server you must have the tape cartridges from the desired full-system backup. You must also have a Solaris system CD ROM #2. Note: For mirrored servers, only critical file systems (/, swap, /var and / usr) are backed up. The non-critical file systems need to be restored manually. Following procedure Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems for Mirrored Servers
Log on in single user mode with the Solaris system CD ROM

1. If not already done, log in to the SCS Server with root login and password on the system supervision console.
25
2. If restoring to GGSNS4.0.1/GGSNS4.1.x, please insert the Solaris 8 Operating System 1 of 2 CD into CD-ROM. If restoring to GGSNS5.0/ GGSNS6.0, please insert the Solaris 9 Operating System 1 of 2 CD into CD-ROM. a. Verify the title information in the contents of the Copyright file indicates" Operating System 1 of 2". 3. Change the run level to 0 (Go under Open Boot PROM): Under root login:
#sync;sync;sync;sync .# init 0
411-5221-309
Standard
06.30 March 10, 2010
409
4. Under the OBP prompt:

{0} ok boot cdrom rs
Restore the SCS

1. Check that all backup tapes are protected against accidental erasure. If not, set the data protector on (open the erasure prevention slide).
25
2. Put the first backup tape (labeled SYSTEM) in the tape drive and check if the following command produces a similar output:
# mt status (verify tape is recognized by the server) Example: # mt status HP DDS-4 DAT (Sun) tape drive: sense key(0x6)= Unit Attention file no= 0 block no= 0 # cd / # tar xv
residual= 0
retries= 0
The following is displayed:

x /tmp/backup/SYSTEM x /tmp/backup/
3. Move to the following directory:

# cd /tmp/backup/tools/bin
4. Launch the following command:

# ./ds_restore.sh
This script checks that: The server was booted with the Solaris system cdrom The server is in single user mode. The inserted cartridge is the SYSTEM cartridge (for PC03 only) The hostid of the server matches the hostid stored in the backup tape Then the script restores the content of the tape labeled SYSTEM, and ejects the tape You are not required to change any tape during the restore process unless the backup is stored in multiple tapes.
GPRS/UMTS
410
5. After the ds_restore.sh script progresses through the restore of the system, the script will reboot the server or you will be prompted to enter system single user mode. If you are prompted to login to single usermode, type in the root password.
INIT: SINGLE USER MODE Type control-d to proceed with normal startup, (or give root password for system maintenance): Enter root password here single-user privilege assigned to /dev/console. Entering System Maintenance Mode At the prompt, type init 6 to reboot the server: # init 6
Note: On performing init 6 if the server does not reboot and takes you to single user mode again like the example capture below, then type reboot at the single user mode prompt:
INFO |PRELIMINARY TASKS INFO | ================= WARN |/usr/local/nortel/tools/bin/ds_restore.sh: test: unknown operator S INFO |TTY = /dev/console INFO | INFO | Checking run level (must be in single user mode) ... INIT: Cannot create /var/adm/utmpx INIT: failed write of utmpx entry:" " INIT: failed write of utmpx entry:" " INIT: SINGLE USER MODE Type control-d to proceed with normal startup, (or give root password for system maintenance): Enter root password at the prompt single-user privilege assigned to /dev/console. Entering System Maintenance Mode
Enter root password when prompted to enter system single user mode. At the prompt, type reboot to reboot the server. # reboot For non-mirrored servers, the server restore procedure is complete. After the reboot, the server boots up from the hard disk. Verify SCS and LDAP (or iPlanet) processes start, otherwise start the LDAP (or iPlanet) and SCS processes manually.
411-5221-309
Standard
06.30 March 10, 2010
411
For non-mirrored servers, the server restore procedure is complete. After the reboot, the server boots up from the hard disk. Verify SCS and LDAP (or iPlanet) processes start, otherwise start the LDAP (or iPlanet) and SCS processes manually. After the full server restore, verify server disks are ok. Please refer to Appendix I: Disk Check for SCS for non-mirrored servers on page 661. For mirrored servers, after the first reboot, the ds_restore.sh script starts setting up the mirrors on the server. You will need to perform two additional server reboot to complete the system restore. The ds_restore.sh script will prompt you to reboot the server when each stage completes. Please proceed to the next step. 6. When prompted to reboot the server, reboot the SCS server # init 6 Note: If the server comes back to single user mode without a full reboot, then at the single user mode prompt, type reboot. After the server comes up, mirrors are attached and the data resync process starts. This takes > 1 hour depending on the size of the partitions and amount of data. 7. After the resync of the mirrors are completes, you will be prompted to reboot the server. Type init 6 to reboot the restored SCS server. # init 6 Note: If the server comes back to single user mode without a full reboot, then at the single user mode prompt, type reboot. This complete the restore procedure for mirrored servers. 8. After the full server restore, verify server disks are ok. Depending on the server installation, run through procedure Disk Check for SCS for mirrored server or Disk Check for SCS for non-mirrored server. 9. After the server reboots, verify all the partitions are mounted.
# df -k
10. If the server is mirrored, verify disk mirroring status is ok using:

# df -k # metastat
GPRS/UMTS
412
11. For mirrored servers, only critical file systems (/, swap, /var and /usr) are backed up. The non-critical file systems need to be restored manually. Following procedure Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems for Mirrored Servers on page 627 12. Eject the Solaris CDROM. After the reboot, login as root and enter the command:
# eject cdrom
For GGSNS6.0, this is simplified since only one tape is needed. At this point you may want to restore a more recent SCS database. Refer to Database restore procedure on page 244 for instructions.
Start the SCS applications
25
If the SCS was configured to automatically restart its processes, then the SCS will start once the reboot completes. Additional instructions are provided if the SCS must be started manually. Note: A GGSN resync is required after the restore. Please plan to resync the GGSN in a maintenance window. 1. After the server reboots, verify if the LDAP (or iPlanet) process and SCS server processes are running.
# ps -aef | grep SCS # ps -aef | grep slapd # ps -aef | grep admin
2. If the processes are not running, start the processes. Determine the LDAP/ iPlanet installation directory.
3. Start LDAP/ iPlanet directory server instance:

#./start-slapd
4. Start LDAP/ iPlanet admin server process

# cd ../
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential #./start-admin
413
# cat /etc/shasta/scs.config | grep SCSHead # cd <Path returned for SCSHead> # cd bin # ./LDAPWatch-enable # ./SCSAdmin start # ./SCSAdmin status
IMPORTANT NOTE: When the SCS starts, all GGSN will be out of sync. Before provisioning can be accomplished, you must resync each GGSN. As the GGSN may still be handling traffic, follow steps in section Traffic Migration prior to performing a resync on each GGSN to minimize service impact. Here is an example capture of a full server restore for mirrored server. After this capture, a full server restore for non-mirrored server is included.
For detailed logs, please refer to: Full Server Backup on page 783 Full Server Restore for Mirrored Servers on Solaris 8 on page 797 Full Server Restore for non-mirrored servers on page 833
GPRS/UMTS
414

Note: Make sure /etc/shasta directory exists and scs.config is present.
26
This section provides details of how to create the Solaris 9 boot environment, upgrade the boot environment to Solaris9 and how to activate it upon reboot.
Creating a Boot Environment (BE) For Solaris 9

The Solaris 9 boot environment creation has the following steps. Identify the Partitions for Solaris 9 Boot environment. Check required packages for Solaris Live Upgrade. Verify and update the version of Live Upgrade. Create the Solaris 9 BE and mount the critical file systems that are mounted in the current boot environment. Upgrade the Solaris 9 BE from the Solaris CDs. Check the status of the Solaris 9 BE.
26
Check and remove the file /var/sadm/system/data/packages_to_be_added if it exists.
Understanding Sun hard disk naming convention Perform df -k or /etc/vfstab on your server. You will notice the Filesystem name is similar to cvtwdxsz. c - Disk Controller / v - Controller number t - Physical Bus Target / w - Target number d - Drive / x - Drive number s - Disk slice / z - Slice number With format, explained below, we can identify the total number of hard disks available on the server. With df -k and /etc/vfstab explained below, make a note of the disks currently used by the system. Identify the Partitions for Solaris 9 Boot environment 1. Check the disk partitions and disk space used for the current Solaris 8 partition using df -k and /etc/vfstab.
411-5221-309
Standard
06.30 March 10, 2010
415
Also, make a note of the swap partition from /etc/vfstab since df -k will not show the drive name for swap. Note: For mirrored servers, refer to the tables Disk Mirroring Mapping for Critical File Systems on page 70 and Disk Mirroring Mapping for Non-critical File Systems on page 70 to find out the available partitions. The recovered partitions (un-mounted) after un-mirroring the server will be used for Solaris 9 BE creation.
# df -k
Filesystem /dev/dsk/c1t0d0s0 /proc fd mnttab /dev/dsk/c1t0d0s5 swap swap /dev/dsk/c1t1d0s7 /dev/dsk/c1t0d0s7 home kbytes used avail capacity Mounted on 10086988 428609 9557510 5% / 0 0 0 0% /proc 0 0 0 0% /dev/fd 0 0 0 0% /etc/mnttab 20174761 5452 19967562 1% /var 18497672 16 18497656 1% /var/run 18497936 280 18497656 1% /tmp 70577241 1279298 68592171 2% /opt 20174761 9 19973005 1% /export/
2. Make a note of the swap partition as well as other mounted partitions.

# cat /etc/vfstab
#device device mount FS fsck mount mount #to mount to fsck point type pass at boot options # #/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes fd /dev/fd fd no /proc /proc proc no /dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no /dev/dsk/c1t0d0s1 swap no /dev/dsk/c1t0d0s5 /dev/rdsk/c1t0d0s5 /var ufs 1 no /dev/dsk/c1t0d0s7 /dev/rdsk/c1t0d0s7 /export/home ufs 2 yes /dev/dsk/c1t1d0s7 /dev/rdsk/c1t1d0s7 /opt ufs 2 yes swap /tmp tmpfs yes -
3. From df -k and /etc/vfstab identify the disk partitions for all critical file systems (/, /var, /usr, /opt) that are mounted. Make a note of the mounted partitions. From the above example capture: / - /dev/dsk/c1t0d0s0 swap - /dev/dsk/c1t0d0s1 /var - /dev/dsk/c1t0d0s5 /opt - /dev/dsk/c1t1d0s7
GPRS/UMTS
416
4. Calculate the combined disk space used for all the critical file systems. The critical file systems are - /, /var, /usr, /opt. This usually depends on the server installation. 5. Identify the unassigned and unmounted partitions that will be used for Solaris 9 Live upgrade using format. Note 1: Please dont use other format options , some format options may damage your file system and the damage cannot fall back. Note 2: For mirrored servers, the recovered partitions (un-mounted) after un-mirroring the server will be used for Solaris 9 BE creation. Please follow tables refer to the tables Disk Mirroring Mapping for Critical File Systems on page 70 and Disk Mirroring Mapping for Non-critical File Systems on page 70 to for partition table details. Note 3: For mirrored servers, please refer Solaris 9 BE - Creating Solaris 9 BE with lucreate on page 83 for details on the partitions to use for creating Solaris 9 Boot Environment. Proceed with the following steps to execute format
Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010183a01,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010186a81,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b0b1,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0 6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0 10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 11. c1t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf786ffa,0
6. From Step 1 (df -k and /etc/vfstab) and Step 3 (format), find out the unused disks available in the server. From the above example capture:
411-5221-309
Standard
06.30 March 10, 2010
417
df -k and /etc/vfstab indicated c1t0dxsz and c1t1dxsz are used by the server. Any of the other drives can be used for creating the Solaris 9 boot environment. 7. If there are sufficient unassigned and unmounted partitions, it is recommended that a separate partition should be mounted for each of the critical file systems(/, /var, /usr and/opt) for Solaris 9 BE. It is a must that the size of each unassigned and unmounted partitions should be at least larger than the used size of its corresponding critical file system plus 3 GB. Note: If there arent enough unassigned and unmounted partitions to mount all the critical file systems separately, it is recommended that at least a separate partition should be mounted for /opt. In this case, the Solaris 9 BE root partition should be at least larger than the total used size of the critical file systems except /opt plus 3 to 5 GB. 8. If there is only one unassigned and unmounted partition and the partition is larger than the total size of the used critical file systems(/, /var, /usr and /opt) plus 3 GB, the partition can be used to hold the Solaris 9 BE. Note: If the required free partition as described above is not found, an additional disk that is pre-formatted and partitioned needs to be added for this purpose. If there is no free partition and no additional disk/no spare disk slot, the upgrade can not proceed. 9. Determine the drives that are unmounted. You may need to re-partition the drives to create the Solaris 9 boot environment. Use the format command to reformat the drive. Here is an example to partition a 72 GB drive. Here disk controller 1, target 4 is selected. The following are the partition and disk space allocation. slice 0 - 10gb slice 1 - 8gb slice 5 - 20gb slice 7 - 20gb
# format
Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a7ebe,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
GPRS/UMTS
418
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a8d24,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a851d,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a904e,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a9aae,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a93e0,0 Specify disk (enter its number): 4 selecting c1t4d0 [disk formatted] FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return quit
format> p
PARTITION MENU: 0 1 2 3 4 5 6 7 select modify name print label !<cmd> quit change `0' partition change `1' partition change `2' partition change `3' partition change `4' partition change `5' partition change `6' partition change `7' partition select a predefined table modify a predefined partition table name the current table display the current table write partition map and label to the disk execute <cmd>, then return
partition> p (to display the current partition table)

Current partition table (original): Total disk cylinders available: 14087 + 2 (reserved cylinders) Part Tag Flag 0 root wm 1 swap wu 2 backup wu 3 unassigned wu 4 unassigned wu 5 unassigned wu 6 usr wm 7 unassigned wu Cylinders 0 25 26 51 0 - 14086 0 0 0 52 - 14086 0 Size 129.19MB 129.19MB 68.35GB 0 0 0 68.10GB 0 Blocks (26/0/0) 264576 (26/0/0) 264576 (14087/0/0) 143349312 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (14035/0/0) 142820160 (0/0/0) 0
partition> m
Select partitioning base:
411-5221-309
Standard
06.30 March 10, 2010
419
0. Current partition table (original) 1. All Free Hog Choose base (enter number) [0]? 1 Part Tag Flag Cylinders Size Blocks 0 root wm 0 0 (0/0/0) 0 1 swap wu 0 0 (0/0/0) 0 2 backup wu 0 - 14086 68.35GB (14087/0/0) 143349312 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 0 0 (0/0/0) 0 6 usr wm 0 0 (0/0/0) 0 7 unassigned wm 0 0 (0/0/0) 0 Do you wish to continue creating a new partition table based on above table[yes]? (hit enter) Free Hog partition[6]? (hit enter) Enter size of partition '0' [0b, 0c, 0.00mb, 0.00gb]: Enter size of partition '1' [0b, 0c, 0.00mb, 0.00gb]: Enter size of partition '3' [0b, 0c, 0.00mb, 0.00gb]: Enter size of partition '4' [0b, 0c, 0.00mb, 0.00gb]: Enter size of partition '5' [0b, 0c, 0.00mb, 0.00gb]: Enter size of partition '7' [0b, 0c, 0.00mb, 0.00gb]:
20gb 8gb (hit enter) (hit enter) 20gb 20gb
Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 4121 20.00GB (4122/0/0) 41945472 1 swap wu 4122 - 5770 8.00GB (1649/0/0) 16780224 2 backup wu 0 - 14086 68.35GB (14087/0/0) 143349312 3 unassigned wm 0 0 (0/0/0) 0 4 unassigned wm 0 0 (0/0/0) 0 5 unassigned wm 5771 - 9892 20.00GB (4122/0/0) 41945472 6 usr wm 9893 - 9964 357.75MB (72/0/0) 732672 7 unassigned wm 9965 - 14086 20.00GB (4122/0/0) 41945472 Okay to make this the current partition table[yes]? yes Enter table name (remember quotes): "c1t4d0" Ready to label disk, continue? yes
partition> p
Current partition table (c1t4d0): Total disk cylinders available: 14087 + 2 (reserved cylinders) Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 4121 20.00GB (4122/0/0) 41945472 1 swap wu 4122 - 5770 8.00GB (1649/0/0) 16780224 2 backup wu 0 - 14086 68.35GB (14087/0/0) 143349312 3 unassigned wu 0 0 (0/0/0) 0 4 unassigned wu 0 0 (0/0/0) 0 5 unassigned wu 5771 - 9892 20.00GB (4122/0/0) 41945472 6 usr wm 9893 - 9964 357.75MB (72/0/0) 732672 7 unassigned wu 9965 - 14086 20.00GB (4122/0/0) 41945472
partition> q
FORMAT MENU: disk type partition current format repair label analyze defect backup verify save inquiry select a disk select (define) a disk type select (define) a partition table describe the current disk format and analyze the disk repair a defective sector write label to the disk surface analysis defect list management search for backup labels read and display labels save new disk/partition definitions show vendor, product and revision
GPRS/UMTS
420

volname !<cmd> quit

- set 8-character volume name - execute <cmd>, then return
format> q
End of format procedure Note: Please make sure that each partition has a flag "wm" (except swap partition) before using it. The swap partition's flag should be "wu". Flag wm means read/write mountable Flag wu means read/write unmountable Here are steps to verify and correct partition flag:
zrc2s0pw# format Searching for disks...done
AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf27c6c6,0 1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfa3b945,0 Specify disk (enter its number): 1 selecting c1t1d0 [disk formatted] Warning: Current Disk has mounted partitions.
FORMAT MENU: disk type - select a disk - select (define) a disk type
partition - select (define) a partition table current - describe the current disk format repair label - format and analyze the disk - repair a defective sector - write label to the disk
411-5221-309
Standard
06.30 March 10, 2010

analyze defect backup verify save - surface analysis - defect list management - search for backup labels - read and display labels - save new disk/partition definitions
421
inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> quit format> verify - execute <cmd>, then return
Primary label contents:
Volume name = <
>
ascii name = <SUN36G cyl 24620 alt 2 hd 27 sec 107> pcyl ncyl acyl nhead nsect Part 0 1 2 3 4 5 6 = 24622 = 24620 = 2 = 27 = 107 Tag root swap backup var usr Flag wm Cylinders 0 - 24615 Size Blocks
33.91GB (24616/0/0) 71115624 5.64MB (4/0/0) 11556
wu 24616 - 24619 wu wu wu wm wm 0 0 - 24619 0 0 0 0 0
33.92GB (24620/0/0) 71127180 0 0 0 0 (0/0/0) (0/0/0) (0/0/0) (0/0/0) (0/0/0) 0 0 0 0 0
7 unassigned wm
To set these flags, please perform the following steps:
> fomat
GPRS/UMTS
422
> Specify disk (enter its number): <-----specify disk by entering number for choice > partition (or you can just enter 'p') > (enter number for partition) > Enter partition id tag[swap]: <----choose to change or keep remaining tag name > Enter partition permission flags[wu]: wm <---------change the flag to 'wm' here > Enter new starting cyl[24616]: (Hit Enter to select the default value) > Enter partition size[11556b, 4c, 5.64mb, 0.01gb]: (Hit Enter to select the default value) > partition> label <----type label at this prompt to save changes > Ready to label disk, continue? yes <-----type 'yes' here Exit format by entering q
10. After identifying all the disk (slices) partitions to be used for all the critical file systems needed for solaris 9 live upgrade, run the command newfs to reformat the partitions example: If the identified partition for / used for solaris 9 live upgrade is c0t1d0s0, then run the following command:
# newfs /dev/rdsk/c0t1d0s0
Type y at the prompt. Repeat the same steps to reformat the partitions for other identified critical file systems.
Check required packages for Solaris Live Upgrade
11. Check your current operating environment for the following packages: SUNWadmap, SUNWadmc, SUNWlibC, SUNWbzip. Those packages are required for Solaris Live Upgrade. If those packages are missing, use the pkgadd command to add them. You need to obtain the Solaris 8 CD 1 to get those packages. Use the pkginfo command to check if the required packages are installed.
# pkginfo system # pkginfo system # pkginfo system # pkginfo system SUNWadmap SUNWadmap SUNWadmc SUNWadmc SUNWlibC SUNWlibC SUNWbzip SUNWbzip System administration applications System administration core libraries Sun Workshop Compilers Bundled libC The bzip compression utility
411-5221-309
Standard
06.30 March 10, 2010
423
If any of the above packages is missing, insert the Solaris 8 CD 1 and use the pkgadd command to add it. Check df -k to find the mount point for the CD ROM.
# # # # # cd /cdrom/cdrom0/s0/Solaris_8/Product pkgadd -d . SUNWadmap pkgadd -d . SUNWadmc pkgadd -d . SUNWlibC pkgadd -d . SUNWbzip
Verify and update the version of Live Upgrade
12. Once the partitions, that are unmounted and unassigned with sufficient sizes as detailed in the above steps, identified to hold both the root partition for Solaris 9 and the critical file systems, then verify that if there is existing live upgrade version running on your machine.
# pkginfo SUNWluu # pkginfo SUNWlur
If the above pkginfo returns an error that SUNWluu and SUNWlur are not installed, follow Step 13 to install the Live Upgrade Software package. Instructions are given below. If there is a Live Upgrade software already installed, you need to uninstall the Live Upgrade software by using the following commands and then go to follow Step 13 to install the Live Upgrade Software package. Instructions are given below.
# pkgrm SUNWlur # pkgrm SUNWluu
If the above pkgrm command fails, execute the below class to uninstall old live upgrade package
# cd /var/sadm/prod/ # java -cp . uninstall_Live_Upgrade_2_0_0502
13. Install the Live Upgrade software that come with Solaris 9 CD 2. The live upgrade binary can be found at /<CDMOUNT>/Solaris_9/Tools/ Installers, where <CDMOUNT> can be determined by running df -k and check for column Mounted on for the CD ROM mount point. Run the liveupgrade20 command.
# cd /CDMOUNT/Solaris_9/Tools/Installers # ./liveupgrade20
Please accept all the default options for the installation.
GPRS/UMTS
424

# ./liveupgrade20
Solaris Web Start will assist you in installing software for Live Upgrade 2.0 05/02. <Press ENTER to continue> Sun Microsystems, Inc. Binary Code License Agreement Live Upgrade READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED SUPPLEMENTAL LICENSE ... <--[21%]--[ENTER To Continue]--[n To Finish]--> ... Enter 'y' to accept the license agreement. Enter 'n' to decline the license agreement and exit the install.y
IMPORTANT NOTICE Patches Needed to Run Solaris Live Upgrade Correct operation of Solaris Live Upgrade requires that a limited set of patch revisions be installed for a given OS version. Before installing or running Live Upgrade, you are required to install a limited set of patch revisions. Make sure you have the most recently updated patch list by consulting sunsolve.sun.com. Search for the info doc 72099 on the SunSolve(tm) web site. Live Upgrade may fail to work properly if the latest limited set of patch revisions are not installed on this system. <Press ENTER to continue> Please select the type of install to perform from the following choices: Typical - Software will be installed with the most common options. Recommended for most users. Custom - You may choose the options you want to install. 411-5221-309 Standard 06.30 March 10, 2010
425
Recommended for advanced users. 1. Typical 2. Custom What would you like to do [1]? 1 Checking disk space. The following items will be installed: Product: Live Upgrade 2.0 05/02 Location: / Size: 2.15 MB ------------------------------Live Upgrade 2.0 05/02 (usr) 991.22 KB Live Upgrade 2.0 05/02 (root) 1.18 MB
Ready to Install 1. Install Now 2. Start Over 3. Exit Installation What would you like to do [1]? 1 Installing Live Upgrade 2.0 05/02 |-1%--------------25%-----------------50%----------------75%--------------100%|
Installation details: Product Live Upgrade 2.0 05/02 Done Result Installed More Info Available
1. 2.
Enter the number corresponding to the desired selection for more information, or enter 2 to continue [2]: 2
Create the Solaris 9 BE
14. The file /var/sadm/system/data/packages_to_be_added may cause the luupgrade or luactivate command fail to run. Check if that file exists. If that file exists, remove it. Otherwise go to next step.
# cd /var/sadm/system/data # ls
GPRS/UMTS
426
If the file packages_to_be_added exists, remove it and then execute ls command again to confirm that file has been removed.
# rm -f packages_to_be_added # ls
Note: The follow steps details the Solaris 9 live upgrade. Please do not make any changes to Unix system configuration after commands lucreate and luupgrade have completed. Example of Unix system configurations are: Adding a new Unix user Adding a new Unix user group Modifying password for Unix users Modifying /etc/host, /etc/resolv.conf
15. Once live upgrade is installed, then create the Solaris 9 boot partition using the lucreate command. The following are three examples: Example 1:
# lucreate -c solaris8 -m /:/dev/dsk/c0t2d0s4:ufs -m /usr:/ dev/dsk/c0t2d0s5:ufs -m /var:/dev/dsk/c0t2d0s6:ufs -m / opt:/dev/dsk/c0t2d0s7:ufs -n solaris9
In the above example, for the new boot environment of Solaris 9, / (root) is mounted on disk c0t2d0 slice 4, /usr is mounted on disk c0t2d0 slice 5, /var is mounted on disk c0t2d0 slice 6 and /opt is mounted on disk c0t2d0 slice 7. Example 2:
# /usr/sbin/lucreate -c solaris8 -m /:/dev/dsk/c0t2d0s7:ufs -m /opt:/dev/dsk/c0t2d0s5:ufs -n solaris9
In the above example, for the new boot environment of Solaris 9, / (root) is mounted on disk c0t2d0 slice 7 and /opt is mounted on disk c0t2d0 slice 5. Example 3:
# /usr/sbin/lucreate -c solaris8 -m /:/dev/dsk/c0t2d0s7:ufs -n solaris9
411-5221-309
Standard
06.30 March 10, 2010
427
In the above example, for the new boot environment of Solaris 9, all the critical file systems are mounted on disk c0t2d0 slice 7. Note: If the lucreate command is not found, please run /usr/sbin/lucreate command.
Upgrade the Solaris 9 BE
16. Once the Solaris 9 boot partition has been created and optionally one or more file systems mounted separately in the new boot environment, the Solaris 9 BE needs to be upgraded with software from the Solaris CDs. 17. Insert the Solaris 9 Software 1 of 2 CD.
# eject cdrom
18. Verify the mount point for the cdrom by using the following command.
# df -k
In the following df -k capture, Solaris 9 Disk 1 is mounted on /cdrom/sol_9_905_sparc/s0

# df -k Filesystem Mounted on
kbytes
used
avail capacity
/dev/dsk/c1t0d0s0 8072333 353257 7638353 5% / /dev/dsk/c1t0d0s6 10086988 778549 9207570 8% /usr /proc 0 0 0 0% /proc fd 0 0 0 0% /dev/fd mnttab 0 0 0 0% /etc/mnttab /dev/dsk/c1t0d0s1 8072333 130548 7861062 2% /var swap 19048176 16 19048160 1% /var/run swap 19048296 136 19048160 1% /tmp /dev/dsk/c1t0d0s5 10086988 3138860 6847259 32% /opt /dev/dsk/c1t1d0s7 70592505 9 69886571 1% /export/ home0 /dev/dsk/c1t0d0s7 20174761 713114 19259900 4% /export/ home /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s5 31 2 26 8% /cdrom/ sol_9_905_sparc/s5 /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s4 31 2 26 8% /cdrom/ sol_9_905_sparc/s4 /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s3 31 2 26 8% /cdrom/ sol_9_905_sparc/s3 /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s2 31 2 26 8% /cdrom/ sol_9_905_sparc/s2 /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s1 276303 259052 0 100% /cdrom/ sol_9_905_sparc/s1 /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s0
GPRS/UMTS
428

312294 sol_9_905_sparc/s0 312294

0 100% /cdrom/
Type the following command to start the upgrade from CD 1.

# /usr/sbin/luupgrade -u -n solaris9 -s /cdrom/sol_9_905_sparc/s0
Where solaris9 is the name given for the BE in the lucreate command, /cdrom/sol_9_905_sparc/s0 is where the cdrom is mounted. Note, the mount point for the cdrom could be different on your server. Two packages (SUNWcsr and SUNWcsu) partially fail to install due to the user accout uucp was removed by Solaris 8 OS hardening. You can also refer to the log file(/var/sadm/system/logs/upgrade_log) for more detail. Accordingly the following warning message is displayed on the terminal console. The partial installation failure of the two packages wont impact Solaris 9 system. Please ignore this warning.
WARNING: <2> packages failed to install properly on boot environment <solaris9>.
19. Once the upgrade from Solaris 9 Disk 1 is complete, eject the Solaris 9 Disk 1.
# eject cdrom
20. Verify the mount point for the cdrom by using df -k command. In the next example, the mount point if /cdrom/sol_9_905_sparc_2
# df -k
21. Rrun the following command for upgrade from Solaris 9 Disk 2.
# /usr/sbin/luupgrade -i -n solaris9 -s /cdrom/sol_9_905_sparc_2 -O '-nodisplay -noconsole'
Where solaris9 is the name of the BE created when using the lucreate command.
Check the status of the Solaris 9 BE
22. Once the upgrade is done the status of the boot partition can be checked by running the following command.
Boot Environment Is Active Active Can Copy
411-5221-309
Standard
06.30 March 10, 2010
429
Name Complete Now On Reboot Delete Status -------------------------- -------- ------ --------- ------ --------solaris8 yes yes yes no solaris9 yes no no yes -
GPRS/UMTS
430
Apply Solaris 9 recommended patches to the Solaris 9 BE
23. Solaris 9 recommended patches can be applied to the Solaris 9 boot environment by specifying the -t flag to the luupgrade command. The -O switch to "luupgrade -t" specifies additional options to pass to the Solaris patch application program. The "patch_order" file located within 9_Recommended is passed as an option.
# luupgrade -t -n "<Solaris 9 BE> \ -s <directory path for 9_Recommended> -O \ "-M directory path for 9_Recommended patch_order"
Make sure Solaris 9 Recommended patch cluster has been FTPed to the server - Please follow Checkpoint 2 item 19, page 118 to FTP and extract the patch cluster. In the following example, /export/home/9_Recommended directory contains recommended patch cluster.
# cd /export/home # ls 9_Recommended
9_Recommended.zip
Patch the Solaris 9 boot environment

# luupgrade -t -n "solaris9" -s /export/home/9_Recommended -O "-M /export/home/9_Recommended patch_order" Validating the contents of the media </export/home/ 9_Recommended>. The media contains 150 software patches that can be added. All 150 patches will be added because you did not specify any specific patches to add. Mounting the BE <solaris9>. Adding patches to the BE <solaris9>. Checking installed patches... Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch number 116340-05 has been successfully installed. See /a/var/sadm/patch/116340-05/log for details Patch packages installed: SUNWgzip SUNWsfinf
...
411-5221-309
Standard
06.30 March 10, 2010
431
... ...
Patchadd is terminating. Unmounting the BE <solaris9>. The patch add to the BE <solaris9> failed (with result code <2>).
Note: The luupgrade -t command may return an error when the command completes execution. The following Solaris patch application exit codes can be ignored. 2 - Attempt to apply a patch that's already been applied 8 - Attempting to patch a package that is not installed
After Solaris 9 recommended patch cluster has been applied to the Solaris 9 boot environment, the next step is to check and remove the file packages_to_be_added if it exists from the Solaris 9 boot environment. 24. The file /var/sadm/system/data/packages_to_be_added which locates on Solaris 9 BE may cause the luactivate solaris9 command fail to run. Mount Solaris 9 BE and check if that file exists. If that file exists, remove it. Otherwise, unmount Solaris 9 BE and then skip this step.
# /usr/sbin/lumount solaris9 /.alt.solaris9
The above commands output is the mount point of Solaris 9 BE file system. Generally the mount point is /.alt.solaris9.
# cd /.alt.solaris9/var/sadm/system/data # ls
If the file packages_to_be_added exists, remove it and then execute ls command again to confirm that file has been removed.
# rm -rf packages_to_be_added # ls
Unmount Solaris 9 BE.

# cd /
GPRS/UMTS
432
Solaris 9 Boot Environment Creation # /usr/sbin/luumount solaris9
The Solaris 9 boot environment creation is completed. Proceed to the next section below to set the server boot path. Important Step to determine server boot path for Solaris 8 and Solaris 9: Make a note of the server boot path for the current Solaris 8 and new Solaris 9. This is needed to make changes to Solaris boot environment before Solaris 9 BE is activated or when the server is rolled back to Solaris 8 after activating Solaris 9. Here is a brief explanation and the steps: Use ls -al command on the partition that is being assigned for / file system for the current Solaris 8 and the new Solaris 9. These path are needed as the server will look for the kernel executable in / during server reboot when activating Solaris 9 or during rollback for Solaris 8. Determine the server root device for Solaris 8: Run df -k and find out the currently mounted / partition. In the below example, /dev/dsk/c1t0d0s0 is set for /.
# df -k Filesystem kbytes used avail capacity Mounted on /dev/dsk/c1t0d0s0 61522236 14749551 46157463 25% /
Run ls -al for the physical partition assigned for the current Solaris 8 / partition.
Record the string that follows the /devices directory (do not include / device). Please note down this information. Also update the spreadsheet that has Disk Mirroring Mapping for Critical File Systems on page 70 In the above example, this string is:
411-5221-309
Standard
06.30 March 10, 2010
433
Make a note of this string, this is called solaris8_root for reference. This will be needed if you want to rollback from Solaris 9 to Solaris 8. solaris8_root - /pci@8,600000/SUNW,qlc@2/fp@0,0/
disk@w500000e010188041,0:a
Determine the server root device for Solaris 9: Verify the / partition assisgned for Solaris 9 during lucreate. Please refer to Create the Solaris 9 BE on page 425 Run ls -al for the physical partition assigned for / for Solaris 9. From the below example, /dev/dsk/c0t2d0s0 is set for /.
Make a note of this string, this is called solaris9_root for reference. This will be needed during reboot of the server after mirroring all the partitions.
solaris9_root - /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w21000004cf786ffa,0:a
GPRS/UMTS
434
If you are using mirrored server setup, record solaris8_root and solaris9_root in the spreadsheet that containsDisk Mirroring Mapping for Critical File Systems on page 70 If you are using a non-mirrored server, check tables recorded in Appendix K: Disk Analysis For Non-Mirrored Servers on page 666
Next step: Please stop here and continue with your readiness checkpoints. Return to checkpoint:
Upgrade readiness checkpoint #4 night before the upgrade on page 46
OR
If you are visiting this section from an SCS Upgrade table, proceed to the step below - Activating the Boot Environment.
411-5221-309
Standard
06.30 March 10, 2010
435
Activating the Boot Environment
Once the BE is created and upgraded, it can be made active upon reboot.
# /usr/sbin/luactivate solaris9
Reboot so that the newly activated BE takes effect.

# init 0
At the ok prompt, use the Solaris OpenBoot PROM nvalias command to define the solaris9_root and solaris8_root device alias. From the solaris9_root and solaris8_root captured in the above:
{2} ok nvalias solaris9_root /pci@8,600000/SUNW,qlc@2/ fp@0,0/disk@w21000004cf786ffa,0:a {2} ok nvalias solaris8_root /pci@8,600000/SUNW,qlc@2/ fp@0,0/disk@w500000e010188041,0:a
Redefine the boot-device alias to reference solaris9_root and solaris8_root. At the ok prompt:
{2} ok setenv boot-device solaris9_root solaris8_root boot-device = current_root backup_root {2} ok nvstore {2} ok setenv use-nvramrc? true use-nvramrc? = true
Execute printenv and verify that the boot-device variable is set to current_root and backup_root (under Value column). Verify variable usenvramrc is set to true. Reboot the server
If you performing the above steps during an upgrade, return to:
GPRS/UMTS
436
Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
Note: In case the server is unable to reboot indicating a disk check is needed, please perform the following steps to fix the disk errors. If the SCS server had mirrored disks please have the follow tables handy Disk Mirroring Mapping for Critical File Systems on page 70 and Disk Mirroring Mapping for Non-critical File Systems on page 70 If the SCS server had non-mirrored disks please have the follow table handyPartition Information for Non-Mirrored Servers on page 667 Perform disk check procedure detailed in section Appendix I: Disk Check for SCS for non-mirrored servers on page 661
Sample execution of lucreate, luupgrade and luupgrade -t
Here a mirrored server has been un-mirrored and the recovered partitions have been used as partitions to create the Solaris 9 boot environment.
# cd /var/sadm/system/data urc2y3pa# ls locales_installed packages_to_be_added
vfstab.unselected
# rm -rf packages_to_be_added
# cd
<<<<lucreate command execution:>>>>

# /usr/sbin/lucreate -c solaris8 -m /:/dev/dsk/c1t2d0s0:ufs -m /var:/ dev/dsk/c1t2d0s5:ufs -m /opt:/dev/dsk/c1t3d0s7:ufs -n solaris9 Discovering physical storage devices Discovering logical storage devices Cross referencing storage devices with boot environment configurations Determining types of file systems supported Validating file system requests Preparing logical storage devices Preparing physical storage devices Configuring physical storage devices Configuring logical storage devices Analyzing system configuration. No name for current boot environment. Current boot environment is named <solaris8>.
411-5221-309
Standard
06.30 March 10, 2010
437
Creating initial configuration for primary boot environment <solaris8>. The device </dev/dsk/c1t0d0s0> is not a root device for any boot environment. PBE configuration successful: PBE name <solaris8> PBE Boot Device </ dev/dsk/c1t0d0s0>. Comparing source boot environment <solaris8> file systems with the file system(s) you specified for the new boot environment. Determining which file systems should be in the new boot environment. Updating boot environment description database on all BEs. Searching /dev for possible boot environment filesystem devices Updating system configuration files. The device </dev/dsk/c1t2d0s0> is not a root device for any boot environment. Creating configuration for boot environment <solaris9>. Creating boot environment <solaris9>. Creating file systems on boot environment <solaris9>. Creating <ufs> file system for </> on </dev/dsk/c1t2d0s0>. Creating <ufs> file system for </opt> on </dev/dsk/c1t3d0s7>. Creating <ufs> file system for </var> on </dev/dsk/c1t2d0s5>. Mounting file systems for boot environment <solaris9>. Calculating required sizes of file systems for boot environment <solaris9>. Populating file systems on boot environment <solaris9>. Checking selection integrity. Integrity check OK. Populating contents of mount point </>. Populating contents of mount point </opt>. Populating contents of mount point </var>. Copying. Creating shared file system mount points. Creating compare databases for boot environment <solaris9>. Creating compare database for file system </var>. Creating compare database for file system </opt>. Creating compare database for file system </>. Updating compare databases on boot environment <solaris9>. Making boot environment <solaris9> bootable. Population of boot environment <solaris9> successful. Creation of boot environment <solaris9> successful.
<<<<luupgrade command execution with Solaris 9 Disk 2>>>>

# df -k Filesystem kbytes used avail capacity /dev/dsk/c1t0d0s0 10086988 450429 9535690 5% /proc 0 0 0 0% fd 0 0 0 0% mnttab 0 0 0 0% /dev/dsk/c1t0d0s5 20174761 6494 19966520 1% swap 17326584 16 17326568 1% swap 17326792 224 17326568 1% /dev/dsk/c1t1d0s7 70577241 2178283 67693186 4% /dev/dsk/c1t0d0s7 20174761 428251 19544763 3% /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s5 31 2 26 8% sol_9_905_sparc/s5 /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s4 31 2 26 8% sol_9_905_sparc/s4 /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s3
Mounted on / /proc /dev/fd /etc/mnttab /var /var/run /tmp /opt /export/home /cdrom/ /cdrom/
GPRS/UMTS
438

31 2 sol_9_905_sparc/s3 /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s2 31 2 sol_9_905_sparc/s2 /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s1 276303 259052 sol_9_905_sparc/s1 /vol/dev/dsk/c0t6d0/sol_9_905_sparc/s0 312294 312294 sol_9_905_sparc/s0 26 26 0 0

8% 8% 100% 100% /cdrom/ /cdrom/ /cdrom/ /cdrom/
# /usr/sbin/lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- -------- ------ --------- ------ --------solaris8 yes yes yes no solaris9 yes no no yes -
# /usr/sbin/luupgrade -u -n solaris9 -s /cdrom/sol_9_905_sparc/s0 Validating the contents of the media </cdrom/sol_9_905_sparc/s0>. The media is a standard Solaris media. The media contains an operating system upgrade image. The media contains <Solaris> version <9>. Constructing upgrade profile to use. Locating the operating system upgrade program. Checking for existence of previously scheduled Live Upgrade requests. Creating upgrade profile for BE <solaris9>. Determining packages to install or upgrade for BE <solaris9>. Performing the operating system upgrade of the BE <solaris9>. CAUTION: Interrupting this process may leave the boot environment unstable or unbootable. Upgrading Solaris: 78% completed // this indicate the status CAUTION: Interrupting this process may leave the boot environment unstable or unbootable. Upgrading Solaris: 100% completed Installation of the packages from this the media is complete. Adding operating system patches to the BE <solaris9>. The operating system patch installation is complete. INFORMATION: </var/sadm/system/logs/upgrade_log> contains a log of the upgrade operation. INFORMATION: </var/sadm/system/data/upgrade_cleanup> contains a log of cleanup operations required. WARNING: <140> packages must be installed on boot environment <solaris9>. INFORMATION: </var/sadm/system/data/packages_to_be_added> on boot environment <solaris9> contains a list of packages that must be installed on the boot environment for the upgrade to be complete. The packages in this list were not present on the media that was used to upgrade this boot environment. INFORMATION: If the boot environment was upgraded using one media of a multiple media distribution, for example the Solaris CD media, you must
411-5221-309
Standard
06.30 March 10, 2010
439
continue the upgrade process with the next media. Complete the upgrade by using the luupgrade <-i> option to install the next media of the distribution. Failure to complete the upgrade process with all media of the software distribution makes the boot environment unstable. INFORMATION: Review the files listed above on boot environment <solaris9>. Before you activate the boot environment, determine if any additional system maintenance is required or if additional media of the software distribution must be installed. The Solaris upgrade of the boot environment <solaris9> is partially complete. LUUPGRADE 2 urc2y3pa# eject cdrom
Insert Solaris 9 CD 2 urc2y3pa# df -k Filesystem kbytes used /dev/dsk/c1t0d0s0 10086988 450424 /proc 0 0 fd 0 0 mnttab 0 0 /dev/dsk/c1t0d0s5 20174761 6562 swap 17283664 16 swap 17284192 544 /dev/dsk/c1t1d0s7 70577241 2178829 /dev/dsk/c1t0d0s7 20174761 428251 /vol/dev/dsk/c0t6d0/sol_9_905_sparc_2 579808 579808 sol_9_905_sparc_2 avail capacity 9535695 5% 0 0% 0 0% 0 0% 19966452 1% 17283648 1% 17283648 1% 67692640 4% 19544763 3% 0 100% Mounted on / /proc /dev/fd /etc/mnttab /var /var/run /tmp /opt /export/home /cdrom/
<<<<luupgrade command execution with Solaris 9 Disk 2>>>>

urc2y3pa# /usr/sbin/luupgrade -i -n solaris9 -s /cdrom/ sol_9_905_sparc_2 -O '-nodisplay -noconsole' Validating the contents of the media </cdrom/sol_9_905_sparc_2>. The media is a standard Solaris media. The media contains a standard Solaris installer. The media contains <Solaris_2_of_2> version <9>. Mounting BE <solaris9>. Running installer on BE <solaris9>. Sun Microsystems, Inc. Binary Code License Agreement Live Upgrade READ THE TERMS OF THIS AGREEMENT AND ANY PROVIDED SUPPLEMENTAL LICENSE TERMS (COLLECTIVELY "AGREEMENT") CAREFULLY BEFORE OPENING THE SOFTWARE MEDIA PACKAGE. BY OPENING THE SOFTWARE MEDIA PACKAGE, YOU AGREE TO THE TERMS OF THIS AGREEMENT. IF YOU ARE ACCESSING THE SOFTWARE ELECTRONICALLY, INDICATE YOUR ACCEPTANCE OF THESE TERMS BY SELECTING THE "ACCEPT" BUTTON AT THE END OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL THESE TERMS, PROMPTLY RETURN THE UNUSED SOFTWARE TO YOUR PLACE OF PURCHASE FOR A REFUND OR, IF THE SOFTWARE IS ACCESSED ELECTRONICALLY, SELECT THE "DECLINE" BUTTON AT THE END OF THIS AGREEMENT.
GPRS/UMTS
440
1. LICENSE TO USE. Sun grants you a non-exclusive and non-transferable license for the internal use only of the accompanying software and documentation and any error corrections provided by Sun (collectively "Software"), by the number of users and the class of computer hardware for which the corresponding fee has been paid. 2. RESTRICTIONS Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Except as specifically authorized in any Supplemental License Terms, you may not make copies of Software, other than a single copy of Software for archival purposes. Unless enforcement is prohibited by applicable law, you may not modify, decompile, reverse engineer Software. Software is not designed or licensed for use in on-line control of aircraft, air traffic, aircraft navigation or aircraft communications; or in the design, construction, operation or maintenance of any nuclear facility. You warrant that you will not use Software for these purposes. You may not publish or provide the results of any benchmark or comparison tests run on Software to any third party without the prior written consent of Sun. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement. 3. LIMITED WARRANTY. Sun warrants to you that for a period of ninety (90) days from the date of purchase, as evidenced by a copy of the receipt, the media on which Software is furnished (if any) will be free of defects in materials and workmanship under normal use. Except for the foregoing, Software is provided "AS IS". Your exclusive remedy and Sun's entire liability under this limited warranty will be at Sun's option to replace Software media or refund the fee paid for Software. 4. DISCLAIMER OF WARRANTY. UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. 5. LIMITATION OF LIABILITY. TO THE EXTENT NOT PROHIBITED BY LAW, IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF OR RELATED TO THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. In no event will Sun's liability to you, whether in contract, tort (including negligence), or otherwise, exceed the amount paid by you for Software under this Agreement. The foregoing limitations will apply even if the above stated warranty fails of its essential purpose. 6. Termination. This Agreement is effective till terminated. You may terminate this Agreement at any time by destroying all copies of Software. This Agreement will terminate immediately without notice from Sun if you fail to comply with any provision of this Agreement. Upon Termination, you must destroy all copies of Software. 7. Export Regulations. All Software and technical data delivered under this Agreement are subject to US export control laws and may be subject to export or import regulations in other countries. You agree to comply strictly with all such laws and regulations and acknowledge that you have the responsibility to obtain such licenses to export, re-export, or import as may be required after delivery to you.
411-5221-309
Standard
06.30 March 10, 2010
441
8. U.S. Government Restricted Rights. Use, duplication, or disclosure by the U.S. Government is subject to restrictions set forth in this Agreement and as provided in DFARS 227.7202-1 (a) and 227.7202-3(a) (1995), DFARS 252.227-7013 (c)(1)(ii)(Oct 1988), FAR 12.212 (a) (1995), FAR 52.227-19 (June 1987), or FAR 52.227-14(ALT III) (June 1987), as applicable. 9. Governing Law. Any action related to this Agreement will be governed by California law and controlling U.S. federal law. No choice of law rules of any jurisdiction will apply. 10. Severability. If any provision of this Agreement is held to be unenforceable, This Agreement will remain in effect with the provision omitted, unless omission would frustrate the intent of the parties, in which case this Agreement will immediately terminate. 11. Integration. This Agreement is the entire agreement between you and Sun relating to its subject matter. It supersedes all prior or contemporaneous oral or written communications, proposals, representations and warranties and prevails over any conflicting or additional terms of any quote, order, acknowledgment, or other communication between the parties relating to its subject matter during the term of this Agreement. No modification of this Agreement will be binding, unless in writing and signed by an authorized representative of each party. For inquiries please contact: Sun Microsystems, Inc. 901 San Antonio Road, Palo Alto, California 94303 INFORMATION: </var/sadm/system/logs/upgrade_log> contains a log of the upgrade operation. INFORMATION: </var/sadm/system/data/upgrade_cleanup> contains a log of cleanup operations required. WARNING: <42> packages must be installed on boot environment <solaris9>. INFORMATION: </var/sadm/system/data/packages_to_be_added> on boot environment <solaris9> contains a list of packages that must be installed on the boot environment for the upgrade to be complete. The packages in this list were not present on the media that was used to upgrade this boot environment. INFORMATION: If the boot environment was upgraded using one media of a multiple media distribution, for example the Solaris CD media, you must continue the upgrade process with the next media. Complete the upgrade by using the luupgrade <-i> option to install the next media of the distribution. Failure to complete the upgrade process with all media of the software distribution makes the boot environment unstable. INFORMATION: Review the files listed above on boot environment <solaris9>. Before you activate the boot environment, determine if any additional system maintenance is required or if additional media of the software distribution must be installed. Unmounting BE <solaris9>. The installer run on boot environment <solaris9> is complete.
urc2y3pa# lustatus
GPRS/UMTS
442
Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- -------- ------ --------- ------ --------solaris8 yes yes yes no solaris9 yes no no yes -
<<<<luupgrade -t command execution to update Solaris 9 patches>>>>

# luupgrade -t -n "solaris9" -s /export/home/9_Recommended -O "-M / export/home/9_Recommended patch_order" Validating the contents of the media </export/home/9_Recommended>. The media contains 150 software patches that can be added. All 150 patches will be added because you did not specify any specific patches to add. Mounting the BE <solaris9>. Adding patches to the BE <solaris9>. Checking installed patches... Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch number 116340-05 has been successfully installed. See /a/var/sadm/patch/116340-05/log for details Patch packages installed: SUNWgzip SUNWsfinf Checking installed patches... Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch number 121992-01 has been successfully installed. See /a/var/sadm/patch/121992-01/log for details Patch packages installed: SUNWcsu Checking installed patches... Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch number 117067-04 has been successfully installed. See /a/var/sadm/patch/117067-04/log for details Patch packages installed: SUNWesu Checking installed patches... Verifying sufficient filesystem capacity (dry run method)... Installing patch packages... Patch number 112964-15 has been successfully installed. See /a/var/sadm/patch/112964-15/log for details Patch packages installed: SUNWcsu Checking installed patches... Executing prepatch script... Modifying pkginfo files... Modifying backout packages... Verifying sufficient filesystem capacity (dry run method)...
411-5221-309
Standard
06.30 March 10, 2010

Installing patch packages... .... ....
443
Patchadd is terminating. Unmounting the BE <solaris9>. The patch add to the BE <solaris9> failed (with result code <2>).
Note: The following Solaris patch application exit codes can be ignored. 2 - Attempt to apply a patch that's already been applied 8 - Attempting to patch a package that is not installed
<<<<Solaris 9 boot environment verification>>>>

# lumount solaris9 /.alt.solaris9 # cd /.alt.solaris9 # cd var/sadm/system/data/ # ls locales_installed packages_to_be_added upgrade_cleanup
upgrade_cleanup_2006_02_18 vfstab.unselected
# rm -rf packages_to_be_added # cd / # luumount solaris9
<<End of Solaris 9 boot environment example captures>
GPRS/UMTS
444

Delete the Solaris 9 Boot EnvironmentI
27
Incase any errors are detected during the boot environment creation or upgrade process, please contact your Nortel Support person. If it is determined that the boot partition needs to be deleted then use the following command.
# ludelete solaris9
The partitions used for the boot partition and the critical file system need to be mounted locally on separate directories and data removed from them to free up space. Please contact your Nortel support for performing these operations. These operations need to be performed before creating the boot environment for Solaris 9 again.
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialDelete Solaris 8 Boot Environment and Reuse Solaris 8 partitions on Solaris 9
445
Delete Solaris 8 Boot Environment and Reuse Solaris 8 partitions on Solaris 9
28
After GGSN 6.0 is upgraded successfully, if SCS server need more disk space and the user want to free up the partitions which belong to the Solaris 8 and reuse those partitions on Solaris 9, please do the following steps: 1. Delete the Solaris 8 Boot Environment 2. Free up the Solaris 8 partitions and mount them on Solaris 9
Warning: These are optional operations. If the Solaris 8 boot environment is deleted, we cannot rollback to Solaris 8 any more.
Delete the Solaris 8 Boot Environment If user want to free up the partitions of Solaris 8 and reuse them on Solaris 9, the Solaris 8 boot environment should be deleted first. Use the following command to delete the Solaris 8 BE.
# ludelete solaris8
Here solaris8 is the boot environment name of the Solaris 8 OS system. Free up the Solaris 8 partitions and mount them on Solaris 9 The partitions of Solaris 8 used for the boot partition(/) and the critical file system (including /var, /user, /opt) can be freed up and reused. Usually the partitions which are non-critical file system (like /export) are shared between Solaris 8 and Solaris 9, so we dont need to consider those partitions here. Here is an example: /dev/dsk/c0t0d0s0 is the partition for root path(/) of Solaris 8 and /var/temp is a mount point on Solaris 9. The partition /dev/dsk/ c0t0d0s0 will be mounted to /var/temp on Solaris 9. Please take the actions on Solaris 9 as the following steps: 1. On Solaris 9, create a temporary mount point to mount the partition previously belong to Solaris 8.
#mkdir /var/temp
GPRS/UMTS
446
Delete Solaris 8 Boot Environment and Reuse Solaris 8 partitions on Solaris 9Nortel Networks Confidential
2. Mount the Solaris 8 partition and free up the disk space

# mount /dev/dsk/c0t2d0s0 /var/temp # cd /var/temp # ls (Confirm that you are going to delete the files under the current path later) # rm -rf * # cd /
3. Repeat the above two steps to free up other Solaris 8 critical file system partitions and mount them on Solaris 9 if needed. Please make sure the mount point should be different for different partitions when typing the mkdir command. Return to: Upgrade SCS 4.1.2 to SCS 6.0 on same server on page 162
411-5221-309
Standard
06.30 March 10, 2010
447
Copy the upgraded SCS 6.0 from Solaris 8 to Solaris 9 29

The SCS software has been upgraded on Solaris 8. The upgraded SCS 6.0 software need to be synchronized from Solaris 8 boot environment (BE) to Solaris 9 BE before the server can be activated and rebooted to Solaris 9. Note: Stop SCS 4.1.2 and LDAP 4.16 processes as well as iPlanet 5.1 directory server and admin processes. Note: Make sure /etc/shasta directory is present and scs.config is present before starting this procedure. Note: From SCS upgrade pre-checks detailed in section Prechecks prior to starting SCS upgrade on page 146, have the current SCS 4.1.2 and LDAP installation directory path handy as they will be used in the following section.
Perform BE copy
1. Stop SCS 4.1.2 process.
# cd <SCS_ROOT>/bin # ./SCSAdmin stop Example: # cd /opt/shasta/scs/bin #./SCSAdmin stop
29
2. Disable LDAPWatch and SCSWatch.

# pwd /opt/shasta/scs/bin # ./LDAPWatch-disable # ./SCSWatch-disable
3. Stop LDAP 4.16 directory server and admin process.

# cd <LDAP_ROOT> # slapd-<hostname>/stop-slapd
Example: # cd /opt/shasta/ldap # slapd-urc2y3pa/stop-slapd
GPRS/UMTS
448
Note: <<CHECK>> slapd-<hostname>1 directory that was created when running rollingSCS.sh will be removed after the SCS 6.0 upgrade procedure by the SCS upgrade script - setup.sh.
# ./stop-admin
4. Stop iPlanet directory server and admin process.

# cd <IPLANET_ROOT> # slapd-<hostname>/stop-slapd # ./stop-admin Example: # cd /opt/shasta/iplanet # slapd-urc2y3pa/stop-slapd # ./stop-admin
5. Use the following command to do the synchronization process. Execute the lustatus command to obtain the Solaris 9 BE name.
# /usr/sbin/lustatus # <SCS6.0_ROOT>/bin/SCSBECopy.sh
SCSBECopy.sh will prompt the user for two input paramaters

Enter Solaris 9 BE name when prompted for Solaris 9 BE. <Hit enter if the default Solaris 9 BE matches lustatus output> Please use the default option for the solaris 9 BE mount point (hit enter for the second prompt). Examples: # lustatus Boot Environment Is Active Active Can Copy Name Complete Now On Reboot Delete Status -------------------------- -------- ------ --------- -----solaris8 yes no no yes solaris9 yes yes yes no # cd <SCS6.0_ROOT>/bin # ./SCSBECopy.sh Need to mount Solaris 9 file system, please specify the solaris 9 BE name. [solaris9]: <-Hit enter if the above lustatus command returns a matching name Please specify the solaris 9 BE mount point. [/opt/ solaris9BE]: <-Hit enter to select the default option
411-5221-309
Standard
06.30 March 10, 2010
449
Solaris 9 BE is mounted. Stop LDAP 5.1 Watch ... /opt/shasta/scs6.0/bin/LDAPWatch-disable: LDAPWatch is already disabled iPlanet Admin Server is running, Stopping it ... Copying LDAP 5.1 files ... Copying SCS files ... Copying /etc/shasta/scs.config ... Solaris 9 BE is unmounted. Done successfully!
<<RECAPTURE>> Verify successful completion of SCSBECopy.sh 6. Verify <SCS6.0_ROOT> and <IPLANET_ROOT> are copied to Solaris 9 BE.
Example:
<SCS6.0_ROOT> = /opt/shasta/scs6.0
Here are the steps with example captures: a. Determine the Solaris 9 BE name from lustatus and mount Solaris 9 BE
b. Mount Solaris 9 BE
# /usr/sbin/lumount solaris9 /.alt.solaris9
c. Verify shasta directory is present on Solaris 9 BE /opt.

# cd /.alt.solaris9/opt # ls shasta
Next step is to compare the content of the iplanet and scs6.0 directories in the Solaris 9 BE directories with the upgraded /opt/shasta/iplanet and /opt/shasta/scs6.0 on Solaris 8 BE. d. Verify SCS6.0 in Solaris 9 BE.
# cd /.alt.solaris9/opt/shasta/scs6.0 # ls | wc -l
19 (this indicates there are 19 files/directories)
GPRS/UMTS
450
e. Verify SCS6.0 in Solaris 8 BE.

# ls /opt/shasta/scs6.0 | wc l
Values of above step d and e must be the same f. Verify IPLANET in Solaris 9 BE
# cd /.alt.solaris9/opt/shasta/iplanet # ls | wc l 22 (this indicates there are 22 files/directories)
g. Verify IPLANET in Solaris 8

# ls /opt/shasta/iplanet | wc -l
Values of above step f and g must be the same Note: Executing SCSBECopy.sh script copies .tmp files to Solaris 9 BE /opt/shasta/iplanet. These files can be ignored. The file count may not match with Solaris 8 BE. Note: Skip the next step of disabling Solaris 9 snmpdx process if it was already performed from a previous upgrade. 7. Locate all Solaris snmpdx files these will conflict with the SCS snmp server and must be removed before activating Solaris 9. a. Use unix find command to locate files matching name snmpdx
# find /.alt.solaris9/etc name *snmpdx print
Here is an example:
# find /.alt.solaris9/etc -name '*snmpdx' -print / .alt.solaris9/etc/init.d/init.snmpdx /.alt.solaris9/etc/rc0.d/K07snmpdx /.alt.solaris9/etc/rc1.d/K07snmpdx /.alt.solaris9/etc/rc2.d/K07snmpdx /.alt.solaris9/etc/rc3.d/S76snmpdx /.alt.solaris9/etc/rcS.d/K07snmpdx
b. Create a backup directory for the Solaris 9 snmpdx startup and shutdown scripts to a backup:
# mkdir -p /.alt.solaris9/opt/snmpdxbackup
411-5221-309
Standard
06.30 March 10, 2010
451
c. Move all K07snmpdx, S76snmpdx, and init.snmpdx files to the snmpdxbackup directory:
# find /.alt.solaris9/etc -name '*snmpdx' -exec mv {} / .alt.solaris9/opt/snmpdxbackup \;
d. Verify that K07snmpdx , S76snmpdx , and init.snmpdx are present in the snmpdxbackup directory:
# ls /.alt.solaris9/opt/snmpdxbackup
Here is an example:
# ls /.alt.solaris8/opt/snmpdxbackup K07snmpdx S76snmpdx init.snmpdx
e. Verify that no snmpdx startup or shutdown files remain in the / .alt.solaris9/etc directory, nor in any of the subdirectories of / .alt.solaris9/etc
# find /.alt.solaris9/etc name *snmpdx print #
Note: This command above will not return any output if step 7c. was successful. If files are still present, cd to each folder listed in the output of the find command, and issue the mv command to move each file listed to the /.alt.solaris9/opt/snmpdxbackup directory, or repeat step 7c. above. 8. Unmount Solaris 9 BE
# cd / # luumount solaris9
GPRS/UMTS
452
30
The recommended patches for Solaris 9 are critical, and they must be used for SCS server upgrade. Note: Installing recommended patches must be performed at the system console. 1. Depending on the current Solaris operating system, download the recommended patches for Solaris 9 or Solaris 10 from http://sunsolve.sun.com-> Support-> Patches and Updates-> Recommended Patch Clusters-> Solaris 9 (or Solaris 10), and save the patches into directory /opt/shasta/temp on SCS server. The file is of zip format (9_Recommended.zip or 10_Recommended). Note: There could be multiple Solaris 9 and Solaris 10 options available at the download site, choose the one that indicates Solaris 9 (file size) or Solaris 10 (file size) Here is an example capture to installation Solaris 9 recommended patch cluster. 2. Login to the SCS server as root user. 3. Go to the directory that stores the patches.
# cd /opt/shasta/temp
4. Extract the patches files.

# unzip 9_Recommended.zip
Note: This takes approximately 3-5 minutes. 5. Stop SCS server processes. a. Determine <SCS_ROOT>
Example:
# cat /etc/shasta/scs.config | grep SCSHead <SCS_ROOT> = SCSHead=/opt/shasta/scs6.0
b. Stop SCS server processes and disable LDAPWatch
411-5221-309
Standard
06.30 March 10, 2010
453
# <SCS_ROOT>/bin/SCSAdmin stop # ./LDAPWatch-disable
6. Stop iPlanet server processes.Make a note of the LDAP server installation directory a. Determine iPlanet installation directory:
#cat /etc/shasta/scs.config | grep LDAPPath
Example:
b. Stop iPlanet directory server process:

# cd <IPLANET_ROOT> # slapd-<hostname>/stop-slapd
c. Stop iPlanet admin server process:

# ./start-admin
7. Execute the following command:

# sync;sync;sync;sync
8. Reboot the server in single user mode to install the patch cluster.
# init 0 {ok} boot -s
At the ok prompt, boot the server in single user mode. 9. At the command prompt, execute the command df -k. If /opt is a separate partition, then /opt needs to manually mounted. Here are the steps to mount /opt. a. View file /etc/vfstab using the cat command
# cat /etc/vfstab
b. Make a note of the device to mount (first column) for /opt. c. Mount the physical partition on /opt
# mount /dev/dsk/<partition> /opt
Here is an example:
GPRS/UMTS
454
Install Recommended Patches for Solaris 9 and Solaris 10 # mount /dev/dsk/c1t4d0s7 /opt
10. Change directory to /opt. Run the installation script to install the patches:
# cd /opt/shasta/temp/9_Recommended # ./install_cluster
Note: This will take a significant amount of time, approximately sixty minutes on a Sun Fire V890. 11. Enter y to confirm patch installation. PATCH INSTALLATION LASTS MORE THAN 30 MINUTES. Note: Ignore installation failure return code 2, 8 and 35: Return codes: 2 - Attempt to apply a patch that has already been applied 8 - Attempt to patch a package that is not installed. 35 - Later revision already installed. 12. Remove the recommended patches for Solaris 9 from the SCS server.
# cd /opt/shasta/temp # rm 9_Recommended.zip # rm -r 9_Recommended
13. Reboot the SCS server back to multi-user mode

# init 6
14. Verify SCS and iPlanet server processes are running.
411-5221-309
Standard
06.30 March 10, 2010
Upgrade GGSNS4.1.1 to GGSNS6.0 on Two servers with same IP address
455
Upgrade GGSNS4.1.1 to GGSNS6.0 on Two servers with same IP address 31

In this document, the two SCS servers are referred as below. Server A - Primary Server Server B - Secondary/Backup server Note: The objective of this procedure is to upgrade both Server A and Server B from GGSNS4.1.1 SCS to GGSN 6.0 or GGSNS5.0.1 to GGSNS6.0 and keep data synchronized between the two servers. Before starting this procedure, it is recommended that any activity between Server A and Server B (e.g., resiliency) be stopped. They can be restarted once the procedure is completed. This procedure assumes that the variables <SCS_ROOT> and <LDAP_ROOT> are set in the users environment file.
Pre-conditions
Server A is on service and Server B is standby. Two servers consistent with SCS requirements, hardware requirements, pre-installed with Solaris 8, and latest Solaris 8 Patches. The latest patch cluster can be obtained from Sun website at http://sunsolve.sun.com-> Support-> Patches and Updates-> Recommended Patch Clusters-> Select Solaris 8. Note: If the current SCS is SCS 5.0.2, the server should be running Solaris 9. Upgrade of Solaris 9 is not required.
The disk partitions and spaces are available on both Server A and Server B. GGSN 6.0 SCS Software CD Backup Media (Tapes for backup) Make sure all the GGSNs are in Sync before the Upgrade on Server A. Log onto the SCS Client as device owner, and click on Devices and then region to make sure all the GGSNs are in sync.
GPRS/UMTS
456
Table 25 describes the procedure to upgrade SCS from 4.1.x or 4.0.1 to 5.0 on two servers with same IP address.
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures Step Duration Tot 1 0:02 SL DT Objective: Verify SCS and LDAP installations on Server B before migration. On the Server B, verify if GGSNS4.1.x/GGSNS4.0.1/GGSNS5.0.1 and LDAP 4.16 (or iPlanet 5.1) are already installed. If they are not installed install the LDAP 4.16 and GGSNS4.1.x/GGSNS4.0.1 or GGSN 5.0.1 and iPlanet 5.1, please refer to Documentation to install or contact Nortel Support Team. The LDAP root point, LDAP Port and Region ID should be the same between Server A and Server B. SCS #cd <SCS_ROOT>/bin # cat version LDAP #cd LDAP_ROOTIPLANET_ROOT #cat LICENSE.txt 2 0:03 0:03 Objective: Stop SCS servers on Server A to ensure no configuration changes happen. Close all your existing SCS Clients Stop the SCS servers on Server A. #cd <SCS_ROOT>/bin #./SCSAdmin stop sheet 1 of 13 Description
411-5221-309
Standard
06.30 March 10, 2010
457
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 3 0:10 SL 0:10 DT Objective: Backup Solid and LDAP on Server A and to transfer backups from Server A to Server B to be used for database restore on Server B. For GGSNS4.1.x/GGSNS4.0.1 go to See This procedure requires a fresh installation of SCS on the new server. During the LDAP or iPlanet and SCS installation, make sure LDAPRoot point on the new server is different from the old server. on page 182 This backup is not a system backup, it is a backup of the individual Solid and LDAP databases as detailed in the above procedure. This backup is needed to be restored on the Server B. Transfer these backup files, to another intermediate server using ftp, till the server B is ready. This backup is needed to be restored on the Server B. Transfer all the database backup files for LDAP, SCS and all the files in /opt/patches and / tftpboot/patches from the server A, (using ftp, and binary transfer) to another intermediate server using ftp, till the server B is ready. 4 0:02 0:02 Objective: Switch Connectivity to Server B. Switch connectivity to Server B so that Server B is visible on the network. sheet 2 of 13 Description
GPRS/UMTS
458
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 5 0:20 SL 0:20 DT Objective: Restore databases on Server B from database backups transferred from Server A. Once the server B is functioning, transfer all the required files from the intermediate server to it. Transfer all the database backup files for LDAP, SCS and all the files in /opt/patches and /tftpboot/patches from the server A, now residing on an intermediate server (using ftp, and binary transfer) to the server B. Copy all the files into corresponding directories. Like all the files in /opt/patches on the server A to the /opt/patches on the server B so on. Also verify the files have identical permission and directories have 755 permission. On server B, restore the Solid and LDAP For GGSNS4.1.x/GGSNS4.0.1 go to Database restore procedure for SCS migrating to a new physical server on page 190. If the restore fails, stop the procedure, switch connectivity back to Server A, bring back the SCS servers on Server A by issuing the command "./SCSAdmin start" from <SCS_ROOT>/bin directory on server A. 6 0:05 0:05 Objective: Start servers after database restore on Server B. Start SCS servers on Server B. #cd <SCS_ROOT>/bin #./SCSAdmin start 7 0:06 Objective: Verify after database restore on Server B, that all devices are in sync. If the SCS client is not already installed, install the SCS Client for Server B: See "SCS client installation" on page 142. Open the client and verify if all ggsns are in sync. If any of ggsns are not in-sync, call Nortel Support team. sheet 3 of 13 Description
411-5221-309
Standard
06.30 March 10, 2010
459
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 8 0:10 SL 0:10 DT Objective: Stop SCS servers on Server B to ensure no configuration changes happen. Close all your existing SCS Clients. Stop the SCS servers on Server B. #cd <SCS_ROOT>/bin #./SCSAdmin stop 9 0:10 0:10 Objective: Backup Solid and LDAP on Server B and to transfer backups from Server B to Server A to be used for database restore on Server A. For GGSNS4.1.x/GGSNS4.0.1 go to See "Database backup procedure for SCS migrating to a new physical server" on page 81. This backup is not a system backup, it is a backup of the individual Solid and LDAP databases as detailed in the above procedure. This backup is needed to be restored on the Server A. Transfer these backup files, to another intermediate server using ftp, till the server A is ready. Transfer all the database backup files for LDAP, SCS and all the files in / opt/patches and /tftpboot/patches from the server B, (using ftp, and binary transfer) to another intermediate server using ftp, till the server A is ready. 10 0:02 0:02 Objective: Switch Connectivity to Server A. Switch connectivity to Server A so that Server A is visible on the network. sheet 4 of 13 Description
GPRS/UMTS
460
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 11 0:20 SL 0:20 DT Objective: Restore databases on Server A from database backups transferred from Server B. On Server A, restore the Solid and LDAP. Ensure the scs server processes are not restarted after the database restore. Once the server A is functioning, transfer all the required files from the intermediate server to it. Transfer all the database backup files for LDAP, SCS and all the files in /opt/patches and /tftpboot/patches from the server B, now residing on an intermediate server (using ftp, and binary transfer) to the server A. Copy all the files into corresponding directories. Like all the files in /opt/patches on the server B to the /opt/patches on the server A so on. Also verify the files have identical permission and directories have 755 permission. For GGSNS4.1.x/GGSNS4.0.1 go to Database restore procedure for SCS migrating to a new physical server on page 190. If the restore fails, stop the procedure, switch connectivity back to Server B, bring back the SCS servers on Server B by issuing the command "./SCSAdmin start" from <SCS_ROOT>/bin directory on server B. 12 0:05 0:05 Objective: Start servers after database restore on Server A. Start SCS servers on Server A. #cd <SCS_ROOT>/bin #./SCSAdmin start 13 14 0:15 0:03 0:03 SCS Upgrade Prechecks on page 146 Stop SCS server and LDAP server to prepare OS unhardening on Solaris 8. See Stop SCS server. Disable LDAPWatch on page 203 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206 15 0:05 0:05 Solaris 8 OS unhardening if Server A is hardened. SeeOS unhardening procedure on Solaris 8 on page 354 sheet 5 of 13 Description
411-5221-309
Standard
06.30 March 10, 2010
461
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 16 0:02 SL 0:02 DT Start up the LDAP server and SCS server if auto-startup is not set. See Start the LDAP / iPlanet server. Enable LDAPWatch on page 205. See Start SCS server. Enable SCSWatch and LDAPWatch on page 201. 17 0:02 Remove all the LDAP watches from the crontab on Server A. See Remove All the LDAP Watches and SCS Watches from the crontab on page 207. 18 3:30 Solaris 9 boot environment Creation and Upgrade on Server A. Refer to Solaris 9 Boot Environment Creation on page 414. 19 0:10 0:10 Stop the SCS server on Server A. See Stop SCS server. Disable LDAPWatch on page 203. Close all your existing SCS Clients. 20 0:10 0:10 Objective: Backup files on Server A. Backup the whole SCS, LDAP Directories and configuration files before the Upgrade on Server A. See Option 1: SCS backup/ restore using tar on page 233 21 0:10 0:10 Objective: Upgrade SCS servers on Server A to GGSN 5.0. See SCS Software Upgrade on page 246. 22 0:05 0:05 Copy the upgraded SCS 5.0 from Solaris 8 BE to Solaris 9 BE on Server A. See Copy the upgraded SCS 6.0 from Solaris 8 to Solaris 9 on page 447. 23 24 25 0:01 0:01 0:05 0:01 0:01 0:05 Stop the original LDAP 4.16 Admin Server and Directory Server. See Disable LDAPWatch. Stop the LDAP / iPlanet on page 206. Activate the new Solaris 9 boot environment on Server A. Refer to Activating the Boot Environment on page 435 Reboot server A using the command init 6. After Solaris 9 is booted, SCS Server 5.0 will start up automatically. sheet 6 of 13 Description
GPRS/UMTS
462
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 26 0:02 SL DT Enable LDAPWatch on Server A if it is not. See LDAPWatch-enable command in section Start the LDAP / iPlanet server. Enable LDAPWatch on page 205 Change the pmuser password. This step is optional. See Change the pmuser password on page 268 28 0:01 Enable iPlanet Directory Server security. See Step 22 on page 269 29 0:10 Install the SSL package on SCS 5.0 Server. This step is optional. See Optional - Installation of the SSL Package. This step is only required, if the customer wants to install and enable SSL on the SCS server. on page 272 30 0:10 Objective: SCS Client upgrade to 5.0. See SCS Client upgrade procedures on page 355 If SCS Server is SSL enabled, the SCS Client machine should also be SSL enabled for the client to function normally. If you have enabled SSL on the SCS Server in the previous step, refer to Enabling SSL on the SCS Client on page 358 for more details on how to enable SSL on client machine. 31 0:01 Post upgrade critical check: verify that all the GGSNs are in sync and there are no sequence number mismatch session errors. Log on SCS Client with the user device_owner, go to Device Manager and verify that all the GGSNs are in sync. Open Diagnostics & Maintenance Dialog, then select Session Errors tab and verify that there are no sequence number mismatch session errors. 32 0:20 See SCS Post-upgrade / Rollback checklists on page 304 The post upgrade checks have to be executed every day for 7 days after the upgrade, to make sure the SCS server is functioning properly after the upgrade. 33 0:10 0:10 Take a backup of the Databases as soon as the Server A upgrade to GGSN 5.0 is over. See Database backup procedure for SCS on page 242. sheet 7 of 13 Description
27
0:01
411-5221-309
Standard
06.30 March 10, 2010
463
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 34 0:03 SL 0:03 DT Stop SCS server and LDAP server on Server A to prepare installing recommended patches for Solaris 9. See Stop SCS server. Disable LDAPWatch on page 203 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206 35 36 0:02 0:10 0:02 0:10 Reboot the system by entering reboot -- -s to boot the system in single user mode on Server A. Apply OS hardening for Solaris 9 on Server A, please see OS Hardening of GGSN SCS Server on page 348 The OS hardening makes the system secure from unauthorized access and modification. 37 0:30 Delete the Solaris 8 BE and mount the Solaris 8 partitions to Solaris 9 for reuse on Server A. This is an optional operation. Take this step unless there isnt enough disk space on Solaris 9. Description
Warning: On the new server, if the Solaris 8 boot environment is deleted, we cannot rollback to Solaris 8 any more. This step must be performed after 24 hours counting from the moment that upgrade is done. Nortel strongly recommends this step be performed after one week, but within 30 days.
See Delete Solaris 8 Boot Environment and Reuse Solaris 8 partitions on Solaris 9 on page 445. 38 0:03 Note: The steps from here and below need to be performed during a maintenance window to be determined by the customer. Objective: Upgrade SCS servers on Server B to GGSN 5.0. Stop SCS server and LDAP server on Server B if they are running. See Stop SCS server. Disable LDAPWatch on page 203 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206. sheet 8 of 13
GPRS/UMTS
464
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 39 0:05 SL DT Solaris 8 OS unhardening if Server B is hardened. SeeOS unhardening procedure on Solaris 8 on page 354 40 0:02 Remove all the LDAP watches from the crontab on Server B. See Remove All the LDAP Watches and SCS Watches from the crontab on page 207. 41 3:30 Solaris 9 boot environment Creation and Upgrade on Server B. Refer to Solaris 9 Boot Environment Creation on page 414. 42 0:10 Backup the whole SCS, LDAP Directories and configuration files before the Upgrade on Server B. This step is needed if fails to upgrade and need to Rollback. See SCS backup/ restore options on page 233. 43 0:10 Objective: SCS Software Upgrade. See SCS Software Upgrade on page 246. 44 0:05 Copy the upgraded SCS 5.0 from Solaris 8 BE to Solaris 9 BE on Server B. See Copy the upgraded SCS 6.0 from Solaris 8 to Solaris 9 on page 447. 45 46 47 48 0:01 0:01 0:05 0:02 Stop the original LDAP 4.16 Admin Server and Directory Server. See Disable LDAPWatch. Stop the LDAP / iPlanet on page 206. Activate the new Solaris 9 boot environment on Server B. Refer to Activating the Boot Environment on page 435 Reboot server B using the command init 6. After Solaris 9 is booted, SCS Server 5.0 will start up automatically. Enable LDAPWatch on Server A if it is not. See LDAPWatch-enable command in section Start the LDAP / iPlanet server. Enable LDAPWatch on page 205 Change the pmuser password. This step is optional. See Change the pmuser password on page 268 sheet 9 of 13 Description
49
0:01
411-5221-309
Standard
06.30 March 10, 2010
465
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 50 0:01 SL DT Enable iPlanet Directory Server security. See See Step 22 on page 269. 51 0:10 Install the SSL package on SCS 5.0 Server. This step is optional. See Optional - Installation of the SSL Package. This step is only required, if the customer wants to install and enable SSL on the SCS server. on page 272 52 0:03 Stop SCS server and LDAP server on Server B to prepare installing recommended patches for Solaris 9. See Stop SCS server. Disable LDAPWatch on page 203 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206 53 54 0:02 0:10 Reboot the system by entering init S to boot the system in single user mode on Server B. Apply OS hardening for Solaris 9 on Server B, please see OS Hardening of GGSN SCS Server on page 348 The OS hardening makes the system secure from unauthorized access and modification. 55 56 0:10 0:03 0:10 Verify partition level file permissions following Modify partition level file permissions on page 300 Objective: Stop Server B. Close all your existing SCS Clients. Stop the SCS servers on Server B. #cd <SCS_ROOT>/bin #./SCSAdmin stop sheet 10 of 13 Description
GPRS/UMTS
466
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 57 0:10 SL DT Objective: Backup Solid and LDAP on Server A and to transfer backups from Server A to Server B to be used for database restore on Server B. For GGSN 5.0 go to See This procedure requires a fresh installation of SCS on the new server. During the LDAP or iPlanet and SCS installation, make sure LDAPRoot point on the new server is different from the old server. on page 182 This backup is not a system backup, it is a backup of the individual Solid and LDAP databases as detailed in the above procedure. This backup is needed to be restored on the Server B. Transfer these backup files, to another intermediate server using ftp, till the server B is ready. Transfer all the database backup files for LDAP, SCS and all the files in / opt/patches and /tftpboot/patches from the server A, (using ftp, and binary transfer) to another intermediate server using ftp, till the server B is ready. 58 0:10 0:10 Objective: Stop Server A and switch connectivity to Server B. Close all your existing SCS Clients. Stop the SCS servers on Server A. #cd <SCS_ROOT>/bin #./SCSAdmin stop Switch connectivity to Server B so that Server B is visible on the network. sheet 11 of 13 Description
411-5221-309
Standard
06.30 March 10, 2010
467
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 59 0:20 SL 0:20 DT Objective: Restore databases on Server B from database backups transferred from Server A. On server B, restore the Solid and LDAP For GGSN 5.0 go to Database restore procedure for SCS migrating to a new physical server on page 190. Once the server B is functioning, transfer all the required files from the intermediate server to it. Transfer all the database backup files for LDAP, SCS and all the files in /opt/patches and /tftpboot/patches from the server A, now residing on an intermediate server (using ftp, and binary transfer) to the server B. Copy all the files into corresponding directories. Like all the files in /opt/patches on the server A to the /opt/patches on the server B so on. Also verify the files have identical permission and directories have 755 permission. If the restore fails, stop the procedure, switch connectivity back to Server A, bring back the SCS servers on Server A by issuing the command "./SCSAdmin start" from <SCS_ROOT>/bin directory on server A. 60 0:05 0:05 Objective: Start servers after database restore on Server B. Start SCS servers on Server B. #cd <SCS_ROOT>/bin #./SCSAdmin start 61 0:10 Objective: Verify after database restore on Server B, that all devices are in sync. If the SCS client is not already installed, install the SCS Client for Server B: See SCS Client upgrade procedures on page 355 Open the client and verify if all ggsns are in sync. If any of ggsns are not in-sync, call Nortel Support team. sheet 12 of 13 Description
GPRS/UMTS
468
Table 25 GGSNS4.1.1to GGSN 6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 62 0:05 SL 0:05 DT Objective: Stop SCS servers on Server B to ensure no configuration changes happen. Close all your existing SCS Clients. Stop the SCS servers on Server B. #cd <SCS_ROOT>/bin #./SCSAdmin stop 63 0:02 0:02 Objective: Switch Connectivity to Server A. Switch connectivity to Server A so that Server A is visible on the network. 64 0:05 0:05 Objective: Start SCS servers on Server A Start SCS servers on Server A. #cd <SCS_ROOT>/bin #./SCSAdmin start 65 66 0:10 0:30 0:10 Verify partition level file permissions following Modify partition level file permissions on page 300 Delete the Solaris 8 BE and mount the Solaris 8 partitions to Solaris 9 for reuse on Server B. This is an optional operation. Take this step unless there isnt enough disk space on Solaris 9. Description
Warning: On the new server, if the Solaris 8 boot environment is deleted, we cannot rollback to Solaris 8 any more. This step must be performed after 24 hours counting from the moment that upgrade is done. Nortel strongly recommends this step be performed after one week, but in 30 days.
See Delete Solaris 8 Boot Environment and Reuse Solaris 8 partitions on Solaris 9 on page 445. sheet 13 of 13
411-5221-309
Standard
06.30 March 10, 2010
469
GPRS/UMTS
470
Upgrade GGSNS5.0.1 to GGSNS6.0 on Two servers with same IP address 32

The objective of this procedure is to upgrade both Server A and Server B from GGSNS5.0 SCS to GGSNS 5.0.1 (SCS 5.0.1 to SCS 5.0.2) and keep data synchronized between the two servers. In this document, the two SCS servers are referred as below. Server A - Primary Server Server B - Secondary/Backup server Before starting this procedure, it is recommended that any activity between Server A and Server B (e.g., resiliency) be stopped. They can be restarted once the procedure is completed. This procedure assumes that the variables <SCS6.0_ROOT> and <IPLANET_ROOT> are set in the users environment file.
Pre-conditions
Server A is on service and Server B is standby. Two servers consistent with SCS requirements, hardware requirements, pre-installed with Solaris 9, and latest Solaris 9 Patches. The latest patch cluster can be obtained from Sun website at http://sunsolve.sun.com-> Support-> Patches and Updates-> Recommended Patch Clusters-> Select Solaris 9. The disk partitions and spaces are available on both Server A and Server B. GGSNS6.0.1 SCS (SCS 6.0) Software CD Backup Media (Tapes for backup) Make sure all the GGSNs are in Sync before the Upgrade on Server A. Log onto the SCS Client as device owner, and click on Devices and then region to make sure all the GGSNs are in sync.
411-5221-309
Standard
06.30 March 10, 2010
471
Table 26 describes the procedure to upgrade SCS from 5.0.2 to 6.0 on two servers with same IP address.
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures Step Duration Tot 0:02 SL DT Objective: Verify SCS and iPlanet installations on Server B before migration. On the Server B, verify if GGSNS5.0 and iPlanet 5.1 are already installed. If they are not installed install the GGSN 5.0 and iPlanet 5.1. Please refer to IM documentation to install or contact Nortel Support Team. The iPlanet root point, LDAP Port and Region ID should be the same between Server A and Server B. SCS #cd <SCS6.0_ROOT>/bin # cat version LDAP #cd <IPLANET_ROOT> #cat LICENSE.txt 0:03 0:03 Objective: Stop SCS servers on Server A to ensure no configuration changes happen. Close all your existing SCS Clients Stop the SCS servers on Server A. #cd <SCS6.0_ROOT>/bin #./SCSAdmin stop sheet 1 of 11 Description
GPRS/UMTS
472
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 0:10 SL 0:10 DT Objective: Backup Solid and LDAP on Server A and to transfer backups from Server A to Server B to be used for database restore on Server B. See Database backup and restore procedures for migrating to a new physical server on page 182 This backup is not a system backup, it is a backup of the individual Solid and iPlanet databases as detailed in the above procedure. This backup is needed to be restored on the Server B. Transfer these backup files, to another intermediate server using ftp, till the server B is ready. This backup is needed to be restored on the Server B. Transfer all the database backup files for iPlanet, SCS and all the files in /opt/patches and / tftpboot/patches from the server A, (using ftp, and binary transfer) to another intermediate server using ftp, till the server B is ready. 0:02 0:02 Objective: Switch Connectivity to Server B. Switch connectivity to Server B so that Server B is visible on the network. 0:20 0:20 Objective: Restore databases on Server B from database backups transferred from Server A. Once the server B is functioning, transfer all the required files from the intermediate server to it. Transfer all the database backup files for LDAP, SCS and all the files in /opt/patches and /tftpboot/patches from the server A, now residing on an intermediate server (using ftp, and binary transfer) to the server B. Copy all the files into corresponding directories. Like all the files in /opt/patches on the server A to the /opt/patches on the server B so on. Also verify the files have identical permission and directories have 755 permission. On server B, restore the Solid and IPLANET. Go to Database restore procedure for SCS migrating to a new physical server on page 190. If the restore fails, stop the procedure, switch connectivity back to Server A, bring back the SCS servers on Server A by issuing the command "./SCSAdmin start" from <SCS6.0_ROOT>/bin directory on server A. sheet 2 of 11 Description
411-5221-309
Standard
06.30 March 10, 2010
473
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 0:05 SL 0:05 DT Objective: Start servers after database restore on Server B. Start SCS servers on Server B. #cd <SCS6.0_ROOT>/bin #./SCSAdmin start 0:06 Objective: Verify after database restore on Server B, that all devices are in sync. If the SCS client is not already installed, install the SCS Client for Server B: See "SCS client installation" on page 142. Open the client and verify if all ggsns are in sync. If any of ggsns are not in-sync, call Nortel Support team. 0:10 0:10 Objective: Stop SCS servers on Server B to ensure no configuration changes happen. Close all your existing SCS Clients. Stop the SCS servers on Server B. #cd <SCS6.0_ROOT>/bin #./SCSAdmin stop sheet 3 of 11 Description
GPRS/UMTS
474
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 0:10 SL 0:10 DT Objective: Backup Solid and LDAP on Server B and to transfer backups from Server B to Server A to be used for database restore on Server A. See "Database backup procedure for SCS migrating to a new physical server" on page 81. This backup is not a system backup, it is a backup of the individual Solid and iPlanet databases as detailed in the above procedure. This backup is needed to be restored on the Server A. Transfer these backup files, to another intermediate server using ftp, till the server A is ready. Transfer all the database backup files for iPlanet, SCS and all the files in / opt/patches and /tftpboot/patches from the server B, (using ftp, and binary transfer) to another intermediate server using ftp, till the server A is ready. 0:02 0:02 Objective: Switch Connectivity to Server A. Switch connectivity to Server A so that Server A is visible on the network. 0:20 0:20 Objective: Restore databases on Server A from database backups transferred from Server B. On Server A, restore the Solid and LDAP. Ensure the scs server processes are not restarted after the database restore. Once the server A is functioning, transfer all the required files from the intermediate server to it. Transfer all the database backup files for LDAP, SCS and all the files in /opt/patches and /tftpboot/patches from the server B, now residing on an intermediate server (using ftp, and binary transfer) to the server A. Copy all the files into corresponding directories. Like all the files in /opt/patches on the server B to the /opt/patches on the server A so on. Also verify the files have identical permission and directories have 755 permission. Go to Database restore procedure for SCS migrating to a new physical server on page 190. If the restore fails, stop the procedure, switch connectivity back to Server B, bring back the SCS servers on Server B by issuing the command "./SCSAdmin start" from <SCS6.0_ROOT>/bin directory on server B. sheet 4 of 11 Description
411-5221-309
Standard
06.30 March 10, 2010
475
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 0:05 SL 0:05 DT Objective: Start servers after database restore on Server A. Start SCS servers on Server A. #cd <SCS6.0_ROOT>/bin #./SCSAdmin start 0:15 0:03 0:03 SCS Upgrade Prechecks on page 146 Stop SCS server and LDAP server to prepare OS unhardening on Solaris 8. See Stop SCS server. Disable LDAPWatch on page 203 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206 0:05 0:05 Solaris 8 OS unhardening if Server A is hardened. SeeOS unhardening procedure on Solaris 8 on page 354 0:10 0:02 0:10 0:02 Verify partition level file permissions following Modify partition level file permissions on page 300 Start up the LDAP server and SCS server if auto-startup is not set. See Start the LDAP / iPlanet server. Enable LDAPWatch on page 205. See Start SCS server. Enable SCSWatch and LDAPWatch on page 201. 0:02 Remove all the LDAP watches from the crontab on Server A. See Remove All the LDAP Watches and SCS Watches from the crontab on page 207. 0:10 0:10 Objective:Backup files on Server A. Backup the whole SCS, LDAP Directories and configuration files before the Upgrade on Server A. See SCS backup/ restore options on page 233 0:10 0:10 Objective: Upgrade SCS servers on Server A to GGSN 5.0.2. See Upgrade SCS from 5.0.2 to 6.0 on page 166. sheet 5 of 11 Description
GPRS/UMTS
476
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 0:02 SL DT Enable LDAPWatch on Server A if it is not. See LDAPWatch-enable command in section Start the LDAP / iPlanet server. Enable LDAPWatch on page 205 Change the pmuser password. This step is optional. See Change the pmuser password on page 268 0:10 Install the SSL package on SCS 5.0 Server. This step is optional. See Optional - Installation of the SSL Package. This step is required if: on page 297 0:10 Objective: SCS Client upgrade to 5.0.2. See SCS Client upgrade procedures on page 355 If SCS Server is SSL enabled, the SCS Client machine should also be SSL enabled for the client to function normally. If you have enabled SSL on the SCS Server in the previous step, refer to Enabling SSL on the SCS Client on page 358 for more details on how to enable SSL on client machine. 0:01 Post upgrade critical check: verify that all the GGSNs are in sync and there are no sequence number mismatch session errors. Log on SCS Client with the user device_owner, go to Device Manager and verify that all the GGSNs are in sync. Open Diagnostics & Maintenance Dialog, then select Session Errors tab and verify that there are no sequence number mismatch session errors. 0:20 See SCS Post-upgrade / Rollback checklists on page 304 The post upgrade checks have to be executed every day for 7 days after the upgrade, to make sure the SCS server is functioning properly after the upgrade. 0:10 0:03 0:10 0:03 Take a backup of the Databases as soon as the Server A upgrade to GGSN 5.0 is over. See Database backup procedure for SCS on page 242. Stop SCS server and LDAP server on Server A to prepare installing recommended patches for Solaris 9. See Stop SCS server. Disable LDAPWatch on page 203 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206 sheet 6 of 11 Description
0:01
411-5221-309
Standard
06.30 March 10, 2010
477
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 1:20 0:02 0:10 SL 1:20 0:02 0:10 DT Install recommended patches for Solaris 9 on Server A, please see Install Recommended Patches for Solaris 9 and Solaris 10 on page 452 Reboot the system by entering reboot -- -s to boot the system in single user mode on Server A. Apply OS hardening for Solaris 9 on Server A, please see OS Hardening of GGSN SCS Server on page 348 The OS hardening makes the system secure from unauthorized access and modification. 0:10 0:03 0:10 Verify partition level file permissions following Modify partition level file permissions on page 300 Note: The steps from here and below need to be performed during a maintenance window to be determined by the customer. Objective: Upgrade SCS servers on Server B to SCS 5.0.2. Stop SCS server and iPlanet server on Server B if they are running. See Stop SCS server. Disable LDAPWatch on page 203 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206. 0:05 Solaris 8 OS unhardening if Server B is hardened. SeeOS unhardening procedure on Solaris 8 on page 354 0:02 Remove all the LDAP watches from the crontab on Server B. See Remove All the LDAP Watches and SCS Watches from the crontab on page 207. 0:10 Backup the whole SCS, LDAP Directories and configuration files before the Upgrade on Server B. This step is needed if fails to upgrade and need to Rollback. See SCS backup/ restore options on page 233. 0:10 Objective: SCS Software Upgrade. See Upgrade GGSN SCS from 5.0.2 to 6.0 on page 274. sheet 7 of 11 Description
GPRS/UMTS
478
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 0:02 SL DT Enable LDAPWatch on Server A if it is not. See LDAPWatch-enable command in section Start the LDAP / iPlanet server. Enable LDAPWatch on page 205 Change the pmuser password. This step is optional. See Change the pmuser password on page 268 0:10 Install the SSL package on SCS 5.0 Server. This step is optional. See Optional - Installation of the SSL Package. This step is required if: on page 297 0:03 Stop SCS server and LDAP server on Server B to prepare installing recommended patches for Solaris 9. See Stop SCS server. Disable LDAPWatch on page 203 and Disable LDAPWatch. Stop the LDAP / iPlanet on page 206 1:20 0:02 0:10 Install recommended patches for Solaris 9 on Server B, please see Install Recommended Patches for Solaris 9 and Solaris 10 on page 452 Reboot the system by entering reboot -- -s to boot the system in single user mode on Server B. Apply OS hardening for Solaris 9 on Server B, please see OS Hardening of GGSN SCS Server on page 348 The OS hardening makes the system secure from unauthorized access and modification. 0:10 0:03 0:10 Verify partition level file permissions following Modify partition level file permissions on page 300 Objective: Stop Server B. Close all your existing SCS Clients. Stop the SCS servers on Server B. #cd <SCS6.0_ROOT>/bin #./SCSAdmin stop sheet 8 of 11 Description
0:01
411-5221-309
Standard
06.30 March 10, 2010
479
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 0:10 SL DT Objective: Backup Solid and LDAP on Server A and to transfer backups from Server A to Server B to be used for database restore on Server B. For GGSN 5.0 go to See This procedure requires a fresh installation of SCS on the new server. During the LDAP or iPlanet and SCS installation, make sure LDAPRoot point on the new server is different from the old server. on page 182 This backup is not a system backup, it is a backup of the individual Solid and LDAP databases as detailed in the above procedure. This backup is needed to be restored on the Server B. Transfer these backup files, to another intermediate server using ftp, till the server B is ready. Transfer all the database backup files for LDAP, SCS and all the files in / opt/patches and /tftpboot/patches from the server A, (using ftp, and binary transfer) to another intermediate server using ftp, till the server B is ready. 0:10 0:10 Objective: Stop Server A and switch connectivity to Server B. Close all your existing SCS Clients. Stop the SCS servers on Server A. #cd <SCS_ROOT>/bin #./SCSAdmin stop Switch connectivity to Server B so that Server B is visible on the network. sheet 9 of 11 Description
GPRS/UMTS
480
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 67 0:20 SL 0:20 DT Objective: Restore databases on Server B from database backups transferred from Server A. On server B, restore the Solid and LDAP For GGSN 5.0 go to Database restore procedure for SCS migrating to a new physical server on page 190. Once the server B is functioning, transfer all the required files from the intermediate server to it. Transfer all the database backup files for LDAP, SCS and all the files in /opt/patches and /tftpboot/patches from the server A, now residing on an intermediate server (using ftp, and binary transfer) to the server B. Copy all the files into corresponding directories. Like all the files in /opt/patches on the server A to the /opt/patches on the server B so on. Also verify the files have identical permission and directories have 755 permission. If the restore fails, stop the procedure, switch connectivity back to Server A, bring back the SCS servers on Server A by issuing the command "./SCSAdmin start" from <SCS_ROOT>/bin directory on server A. 68 0:05 0:05 Objective: Start servers after database restore on Server B. Start SCS servers on Server B. #cd <SCS_ROOT>/bin #./SCSAdmin start 69 0:10 Objective: Verify after database restore on Server B, that all devices are in sync. If the SCS client is not already installed, install the SCS Client for Server B: See SCS Client upgrade procedures on page 355 Open the client and verify if all ggsns are in sync. If any of ggsns are not in-sync, call Nortel Support team. sheet 10 of 11 Description
411-5221-309
Standard
06.30 March 10, 2010
481
Table 26 GGSNS5.0.1 to GGSNS6.0 on two servers, same IP address upgrade procedures (continued) Step Duration Tot 70 0:05 SL 0:05 DT Objective: Stop SCS servers on Server B to ensure no configuration changes happen. Close all your existing SCS Clients. Stop the SCS servers on Server B. #cd <SCS_ROOT>/bin #./SCSAdmin stop 71 0:02 0:02 Objective: Switch Connectivity to Server A. Switch connectivity to Server A so that Server A is visible on the network. 72 0:05 0:05 Objective: Start SCS servers on Server A Start SCS servers on Server A. #cd SCS_ROOTLDAP_ROOT/bin #./SCSAdmin start sheet 11 of 11 Description
GPRS/UMTS
482
Steps to recover from Solid database corruption issue

Problem Description
33
33
SCS solid database corruption issue could occur when the SCS solid database process is not stopped cleanly prior to a server reboot. When this corruption occurs SCS server is not operational and SCS Processes cannot be started. An error will be returned when trying to start the SCS server:
# ./SCSAdmin start /opt/shasta/scs/bin/SCSWatch-disable: SCSWatch is already disabled /opt/shasta/scs/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled /opt/shasta/scs/bin/SCSDiskUsageMonitor-disable: SCSDiskUsageMonitor is already disabled /opt/shasta/scs/bin/SCSCleanXmlExportFiles-disable: SCSCleanXmlExportFiles is already disabled [1] 660 Starting Solid Database Server:.[1] + Exit 100 / opt/shasta/scs/opt/solidSolaris/bin/solid -f -c ... .Solid database has the following error: Solid Database Engine process has encountered an internal error and is unable to start
To fix the corruption issue, a solid database integrity check is performed. If the integrity check is ok, then a new installation of SCS is not required. If the integrity check fails, a new installation of SCS is required followed by a database restore. In this case, LDAP/ iPlanet installation is not required.
Steps to resolve solid database corruption
33
1. Refer to Determine SCS and LDAP/ iPlanet installation directories on page 201 to determine the location of SCS installation directory. 2. Stop all SCS server processes.
# cd <SCSHead>/bin/SCSAdmin stop
3. Verify the solid database integrity check.

# <SCSHead>/opt/solidSolaris/bin/solid -x testindex -c <SCSHead>/opt/solidSolaris/database/default
411-5221-309
Standard
06.30 March 10, 2010
483
Here are two example captures, example one - integrity check passes, example two - integrity check fails. a. Integrity check passes:
# /opt/shasta/scs6.0/opt/solidSolaris/bin/solid -x testindex -c ../database/default Testing the database index. -------------------Fri Nov 14 13:42:46 2008 Bonsai tree: Key id = 1091 Clustering key Bonsai tree is ok. Storage tree: Key id = 191 Clustering key ... ... Storage tree is ok. Database index has been tested succesfully. Database index is ok.
b. Integrity check fails:

# /opt/shasta/scs6.0/opt/solidSolaris/bin/solid -x testindex -c /opt/shasta/scs6.0/opt/solidSolaris/database/ default Testing the database index. Warning! Starting roll-forward recovery, please wait ... Solid Database Engine process has encountered an internal error and is unable to continue normally. Please report the following information to Solid Information Technology. Status: 1757@tab0blobg2.c Code: 1 Date: 08.03 19:51:46 Product: Solid FlowEngine Version: 04.00.0048 Operating system: Solaris 8 SPARC MT
4. If the integrity check passes, then proceed to execute Steps if solid database integrity check passes on page 484. OR 5. If the integrity check fails, then Steps if solid database integrity check fails on page 484.
484
Steps if solid database integrity check passes If the database integrity check passes, there is no corruption to the solid database. Execute the following steps to fix the corruption issue. 1. Change directory to <SCSHead>/opt/solidSolaris/database/default Here is an example.
cd /opt/shasta/scs6.0/opt/solidSolaris/database/default
2. Edit the file solid.ini using vi editor. Comment out the following line and save the changes:
FileNameTemplate=log/sol#####.log
Here is an example after modification.

[Logging] #FileNameTemplate=log/sol#####.log
3. Start all SCS server processes.

# cd <SCSHead>/bin/SCSAdmin start
Steps if solid database integrity check fails Overview of the steps i. Add a new LDAP root point (not matching current LDAP root point). The current LDAP root point can be identified from <SCS_ROOT>/bin/.scs.config ii. Stop all SCS server processes. iii. Rename the current SCS home directory. iv. Create SCS home directory to match the previous SCS home directory v. Copy scsserver.tar, scs_corba_server.tar, directory-5[1].1sp3us.sparc-sun-solaris2.8.tar to scs6.0 vi. Perform a new install of SCS, pass in the new LDAP root point vii. Restore old solidDB viii.Modify <SCS_ROOT>/bin/scs.config, modify LDAPRoot to match old LDAP root point ix. Start SCS server processes.
411-5221-309
Standard
06.30 March 10, 2010
485
Steps to fix solid database corruption 1. Change directory to <SCS_ROOT>/bin

2. Make a note of following parameters from file .scs.config. This is needed while performing a new install of SCS server
# # # # # # # cat cat cat cat cat cat cat .scs.config .scs.config .scs.config .scs.config .scs.config .scs.config .scs.config | | | | | | | grep grep grep grep grep grep grep RegionId LDAPPath LDAPRoot LDAPServerPort LDAPServerName LDAPUsername LDAPPassword
3. Next step is to launch the iPlanet console. If the SCS server has a directly connected monitor, please login from the monitor. If a monitor is not available or the SCS server only has remote access, the user needs to telnet to the SCS server using X Windows - xterm to be able to launch the iPlanet console. To launch iPlanet console using xterm, export the DISPLAY environment variable
# setenv DISPLAY <IP_Address_of_PC_connecting_to_SCS:0.0>
Here is an example
# setenv DISPLAY 192.168.35.1:0.0
4. Make sure that the iPlanet server is running:

# cd <IPLANET_HOME>
where <IPLANET_HOME> is the directory path matching <LDAPPath> obtained earlier 5. Verify iPlanet server process are running
# ps -aef | grep -v grep | grep slapd
Example:
# ps -aef | grep -v grep | grep slapd nobody 439 1 0 14:22:26 ? 0:02 ./ns-slapd D /opt/shasta/iplanet/slapd-zrc2s1861 -i /opt/shasta/ iplanet/slapd-
If the above ps command returns no result, then start the iPlanet server process
GPRS/UMTS
486
Steps to recover from Solid database corruption issue # <LDAP_SERVER_PATH>start-slapd
where LDAP_SERVER_PATH is the directory name returned for <LDAPPath> earlier.
6. Verify iPlanet admin server process is running

# ps -aef | grep admin | grep -v grep
If the above ps command returns no result, then start the iPlanet server process
./start-admin
7. Launch the iPlanet server console and login to the iPlanet console.
# cd iplanet # ./staconsole &
Note: The default username is admin, password is admin, URL is <http:/ /scshost.domain:33611> 8. Create a LDAP root point. The new LDAP root point must be different than the previous LDAP root point (refer above - cat /bin/.scs.config) 9. Double click domain name 10. Double click <scshostname>.<domain.name> 11. Double click directory server. There should be directory server and administrator server below server group. Double click directory server. 12. Click on the directory tab 13. Expand <domain.name> 14. Click on People, Object-> New-> User Here is an example First name: ldap, last name: user, user id: ldap, password ldap Leave the rest of the fields as default. Important Note: The User ID is the uid in <LDAPRoot> and must be different from the current LDAP root point where the solid database issue has occurred. Refer to <SCS_ROOT>/bin/.scs.config
# cat .scs.config | grep LDAPRoot
411-5221-309
Standard
06.30 March 10, 2010
487
15. Click OK to go back to the main screen with Servers and Applications. Minimize the iPlanet console window. 16. Perform new install of SCS server
# cd /opt/shasta/scs6.0/bin # ./SCSAdmin stop # cd /opt/shasta/
17. Move the current <SCS_ROOT> to <SCS_ROOT_ORG>

# mv scs6.0 scs6.0_org
18. Create a directory for <SCS_ROOT> with the same name as the directory moved in previous step. 19. Copy scsserver.tar, scs_corba_server.tar and directory-5[1].1sp3-us.sparcsun-solaris2.8.tar to <SCS_ROOT>
# mkdir scs6.0 # cp scs6.0_org/scs*.tar scs6.0 # cp scs6.0_org/dir* scs6.0
20. Change directory to <SCS_ROOT>

# cd scs6.0
21. Extract scsserver.tar

# tar xvf scsserver.tar
Note: Have the parameters captured in step 2 handy as they need to be entered during the new install of SCS server. 22. Perform new install of SCS server using script setup.sh. Pass the -m option to the script. Here is an example capture.
# ./setup.sh -m
5.9 is a supported Solaris version Logged in as User root Manual procedure is selected /opt/shasta/scs6.0/install/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled This program will install Nortel Service Creation System. Version SCS GGSNS6.0_SCS6.0(47) ***************************************************************** * SCS 6.0 requires IPlanet LDAP 5.1. If you are not running IPlanet * * LDAP 5.1, please upgrade the LDAP server before starting the SCS *
GPRS/UMTS
488
* Installation. Please refer to the SCS installation document and * * SCS Release Notes for details on upgrading the Directory Server. * * * * SCS and LDAP require Solaris Recommended Patches. * * Make sure that the latest patches have been installed * * If you are not sure, please abort the setup and check Patch level * * Restart the setup.sh script after checking the patch level * ***************************************************************** You have the following options: (C) Create a new SCS Server installation (U) Upgrade the current SCS Server (A) Abort this installation Please enter (C)reate, (U)pgrade or (A)bort? [A]: c Please specify the directory for the new SCS installation [/opt/ shasta/scs6.0]: SCS will be installed in /opt/shasta/scs6.0. Checking the available space ... Required space 106636 Kbytes. Available space 9709564 Kbytes. Found enough space to install SCS. Copying the required files ... Here are the possible server installation components for this machine: (1) (2) (3) (4) SCS Domain Server (with SNMP Proxy) SCS Region Server (with Monitor Server and SCS Trap Daemon) SCS Pull Server SCS Log Server
Please select the server(s) to install (separated by spaces) [1 2 3 4]: You have selected the following server(s) to install: (1) (2) (3) (4) SCS Domain Server (with SNMP Proxy) SCS Region Server (with Monitor Server and SCS Trap Daemon) SCS Pull Server SCS Log Server
Here are the possible deployment profile options: (1) Large Scale Deployment, requires 1792M of virtual memory (for region with 15-20 devices, or multiple region servers) (2) Medium Scale Deployment, requires 896M of virtual memory (for single region server with 7-10 devices) (3) Small Scale Deployment, requires 448M of virtual memory (1 or 2 devices with limited number of subscribers) This machine currently has 13751M of virtual memory available. Please select deployment profile [1]: <-Hit enter to select default
411-5221-309
Standard
06.30 March 10, 2010
489
Please provide this Region ID [1]: <-This value must match the old SCS region ID. Please refer to earlier step Please provide the listening port for Pull Server [4321]: <-Hit enter to select default Please provide the logging port for Log Server [4322]: <-Hit enter to select default Please provide the accounting port for Log Server [4323]: <-Hit enter to select default We need to install Solid database server on this host. Please provide password for the SCS database users [admin]: Please provide path for the SCS backup [/opt/shasta/scs6.0/ backup]: checking if snmp default port 5001 has been used, please wait ... snmp prxy will use port 5001. checking if TrapDaemon default port 5002 has been used, please wait ... TrapDaemon will use port 5002. Is LDAP server installed and running on this host (y/n)? [n]: y Please provide the LDAP path : /opt/shasta/iplanet <-Enter the iPlanet installation directory. This is <LDAPPath> captured in step 2. We need to collect the LDAP information for the Domain/Pull/Log Server. /opt/shasta/iplanet is LDAP path slapd-ur2y3pa is LDAP server Please provide the LDAP Server IP address [localhost]: Please provide the LDAP Server port [389]: <-Enter <LDAP_PORT>. This is <LDAPServerPort> captured in step 2. Ldap port is validated Value from the config File is - ldapPort: 389 Please provide the LDAP username [uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot ]: <-This must match the old LDAPUsername captured in step 2. Please provide the LDAP password: <-This must match the old LDAPPassword captured in step 2. Please provide the LDAP root: uid=ldap35,ou=People,o=us.nortel.com <-Enter the LDAP root, modify the uid to match the UID created from the iPlanet console. Note, UID entered must not match the old LDAPRoot UID. Values for ou=People and o=domain.com must match old <LDAPRoot>. Valid Root point - dn: uid=ldap35,ou=People, o=us.nortel.com uid: ldap35 givenName: ldap35 cn: ldap35 user Validated Root Point
GPRS/UMTS
490
Do you want to run SCS server processes at boot time? (Y)es or (N)o? [N]: Y Installing the Solid Database Server ... [1] 29739 Start the solid server ... Solid Server is running ... Creating database tables for the SCS Domain Server ... 23-Mar-2009 19:54:02 198 INFO ldap.connection.info: localhost,389,uid=admin,ou=Administrators,ou=TopologyManagement,o =NetscapeRoot,uid=ldap35,ou=People,o=us.nortel.com 23-Mar-2009 19:54:02 393 INFO sni.7: Created a new LDAP connection... 1 Adding Patch Server information in SCS Domain Server database ... Enabling tftp - tftp already enabled, no changes made Creating database tables for the SCS Region Server ... Adding Pull Server information in SCS Domain Server database ... Adding Log Server information in SCS Domain Server database ... We have created the required SCS database tables. Now we will shutdown the Solid database server. Stopping Solid Database Server:.Stopped [1] + Done /opt/shasta/scs6.0/opt/solidSolaris/ bin/solid -f -c ... LDAP schema files updated successfully Now stopping and restarting LDAP server slapd-ur2y3pa ... To generate CSV formatted accounting data, a user id must be designated as the owner of the generated files. It is recommended that the user id not be the root user. The ownership of any existing CSV formatted accounting data file will also be changed to this user id. Do you want to designate a user id for the CSV formated data.? (Y)es or (N)o? [Y]: Please enter a user id. [pmuser]: The user id, pmuser, already exists and will be used by the SCS Log Server process for CSV generated files. Please enter the number of days the individual CSV files should be preserved before the SCSCleanLogcsv.ksh script removes them. [4]: Do you want to install the SCS GGSNS6.0_SCS6.0(47) SCS Corba Server? (Y)es or (N)o? [Y]: n <- enter y if SCS Corba Server is installed The installation logs are saved in /opt/shasta/scs6.0/lib/install/ *.log. INSTALLATION IS COMPLETED SUCCESSFULLY The following SCS server(s) are currently installed on this machine: Version SCS GGSNS6.0_SCS6.0(47) SCS SCS SCS SCS SCS You can Server. Domain Server (LDAP Server IP = localhost) Region Server (Region ID = 1) Monitor Server Pull Server (Listening Port = 4321) Log Server (Logging Port = 4322, Accounting Port = 4323) use '/opt/shasta/scs6.0/bin/SCSAdmin start' to run SCS
411-5221-309
Standard
06.30 March 10, 2010
491
23. Start SCS server processes

# cd bin
24. Verify SCS server processes can be started

# ./SCSAdmin start
25. Perform a backup of solid database to a new directory <newsoliddb> on the new server
# ./SCSAdmin backup solidDB newsoliddb binDir is /opt/shasta/scs6.0/bin head is /opt/shasta/scs6.0 configFile is /opt/shasta/scs6.0/bin/.scs.config backup_dir is /opt/shasta/scs6.0/opt/solidSolaris/database/ newsoliddb Solid Remote Control v.04.00.0025 (C) Copyright Solid Information Technology Ltd 1993-2003 Exit by giving command: exit Backup started.
26. Create a solid database backup directory on the new server

# mkdir -p <SCS_ROOT>/opt/solidSolaris/database/backup
Here is an example:
# mkdir -p /opt/shasta/scs6.0/opt/solidSolaris/database/ backup
27. Copy the solid database files from the old SCS server to the new SCS server
# cd <SCS_ROOT_ORG>/opt/solidSolaris/database/default # cp solid.db solid.ini <SCS_ROOT>/opt/solidSolaris/ database/backup
Here is an example:
# cd /opt/shasta/scs6.0_org/opt/solidSolaris/database/ default # cp solid.db solid.ini /opt/shasta/scs6.0/opt/ solidSolaris/database/backup
28. Restore solidDB on the new SCS server

Here is an example:
# cd /opt/shasta/scs6.0/bin GPRS/UMTS Upgrade Manual GGSN6.0
492
# ./SCSAdmin restore solidDB
29. Using vi editor, edit file <SCS_ROOT>/bin/.scs.config. Modify the uid in <LDAPRoot> to match the old SCS server. Please verify step 2 for the original <LDAPRoot> In the above example:
Old LDAPRoot - uid=admin,ou=People,o=us.nortel.com New LDAPRoot - uid=ldap,ou=People,o=us.nortel.com Modify New LDAPRoot to uid=admin,ou=People,o=us.nortel.com
30. Make sure iPlanet server processes are running

# ps -aef | grep slapd # ps -aef | grep admin
31. Start SCS server processes

# pwd <SCS_ROOT>/bin
Example:
# cd /opt/shasta/scs6.0/bin # ./SCSAdmin start
411-5221-309
Standard
06.30 March 10, 2010
493
GGSN Software Upgrade

Figure 7 GGSN Upgrade Strategy GGSN Pre-upgrade Check
34
The flow of GGSN software upgrade strategy is described in Figure 7. The upgrade stages listed in the flow should be performed in the sequence order.
GGSN Post-upgrade Check
GGSN Post-Upgrade Procedures
For each GGSN upgrade stage, there is a procedure or procedures associated to it: 1. GGSN pre-upgrade system check, See GGSN Pre-Upgrade Procedure on page 495. 2. GGSN software upgrade, See GGSN Upgrade Procedure on page 521. 3. GGSN post-upgrade system check, See GGSN Post-Upgrade Procedure on page 541. 4. GGSN optional post-upgrade configuration, See Optional Post-Upgrade Procedures on page 545.
GPRS/UMTS
Upgrade Manual
GGSN6.0
494
5. GGSN software rollback after software upgrade if it is necessary, See GGSN Rollback procedure on page 547. GGSN system monitoring after software upgrade, See GGSN Upgrade Follow-up on page 554
411-5221-309
Standard
06.30 March 10, 2010
GGSN Pre-Upgrade Procedure
495

GGSN Pre-Upgrade Procedure duration
Table 27 GGSN pre-upgrade procedure timing Step Duration (Hours:Mins) Upgrade Total 1 2 0:20 Current Step 0:20 Down Time 0:00 GGSN pre-upgrade procedure Make a note of GGSN combo patch profile name Description
35
35
Note: Prior to starting the GGSN pre-upgrade or upgrade procedures, it is recommended to connect to the GGSN active and standby CMC console ports.
Steps before GGSN upgrade
35
1. Upgrade the SCS server and the SCS clients to SCS 6.0 before proceeding to the GGSN upgrade. See SCS and GGSN Load Lineup on page 23 for SCS and GGSN load line up. 2. Log into the GGSN CLI via a telnet or ssh session. 3. If GGSN console port access is available, connect to the CMC console port. 4. The following system checks must be performed prior to the upgrade activity to establish a baseline. The results may be used for comparison with results captured after the upgrade is complete. This will serve to establish confidence in the overall health of the system. Log the resulting output to file. For more details on the CLI commands refer to the Nortel GGSN CLI Guide, 411-5221-926. You will be directed to perform these steps both before and after the GGSN upgrade. a. show bootorder Use this command to verify and record the current boot order. This will be required if a rollback is necessary:
# show bootorder
GPRS/UMTS
Upgrade Manual
GGSN6.0
496
b. show socket Enter the command show socket and ensure the pull server, log server and log accounting server are established. Verify the ports 4321, 4322 and 4323 are established; if not contact your next level of support.
# show socket 7fbcdfd4 TCP 47.104.70.80.4322 7fbcdc64 TCP 47.104.70.80.4323 7fbdef34 TCP 47.104.70.80.4321 0 0 0 0 47.104.5.50.49154 ESTABLISHED 0 47.104.5.50.49155 ESTABLISHED 0 47.104.5.50.49235 ESTABLISHED
c. show card Enter the command show card. Verify all SSC cards with ports are showing as U (UP), - (disabled), or * (not present); if not, contact your next level of support before proceeding. Record the status of each. If there is a standby CMC card, verify the standby CMC displays the info status as Redundant. If the standby CMC is not redundant, call the next line of Nortel support and do not continue. A standby CMC is a preferred configuration, but is not required.
# 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 ---1 2 3 4 5 6 7 8 Configured/Found Enabled Info ----------------- ------- ----SSC /SSC Enabled U U U U SSC /SSC Enabled U U U U SSC /SSC Enabled U U U U SSC /SSC Enabled U U U U ALC /ALC Enabled U U U U [ICP Rev. 1.6] GELC /GELC Enabled D [FPGA Rev. 0.5] [GBIC Multi] SFC2 /SFC2 Enabled 10G Active [FPGA Rev. 2.0/30.5] SFC2 /SFC2 Enabled 10G Standby [FPGA Rev. 2.0/30.5]
411-5221-309
Standard
06.30 March 10, 2010

9 10 11 12 13 14 GELC /GELC [GBIC Multi] ELC /ELC SSC /SSC SSC /SSC CMC /CMC CMC /CMC

Enabled
497
D [FPGA Rev. 0.5]
Enabled U U U D D D D D Enabled U U U U Enabled U U U U Enabled Standby (Redundant) Enabled Active
d. Determine the Gn, Ga and Gi ISPs Use the show isp CLI command and record the ISPs configured.
show isp
To identify the Gn ISP: issue the command show tunnel. Make a note of the ISP associated with tunnel Type as gtp. This ISP is the Gn ISP. Here is an example where ISP gn-158 is configured with a tunnel of Type gtp:
ggsn-158(SSU)# show tunnel Mon 02-Jun-2008 03:02:07 CDT Tunnel ISP -------l2tp-contivity gi-158 l2tptunnelto169 gi-158 gtptunnel gn-158
Type ---l2tp lac l2tp lac gtp
Status -----UP IDLE n/a
To identify the Ga ISP: Issue the command show cgf isp= <isp_name> For the <isp_name>, enter each ISP name from the show isp command one at a time. For the ISP that is configured with a CGF profile, an output is returned with the CGF Profile name and at least one Server (CGF server IP) configured. Make a note of the ISP name This is the Ga ISP. Other ISPs will not return an output.
ggsn-158(SSU)# show cgf isp= ga-158 Mon 02-Jun-2008 02:50:42 CDT ISP CGF Profile ... ... Server 1 UDP Port 1 ... ... Server 2 UDP Port 2 = = ga-158 cgf
= =
47.104.6.17 3386
= =
47.104.6.16 3386
GPRS/UMTS
Upgrade Manual
GGSN6.0
498
To identify the Gi ISP: Issue the command show apn. The ISPs configured with one or more APNs are the Gi (Connection) ISP.
e. show stats hist sm <Gn-ISP> Use show stats hist sm <gn-isp> CLI command to determine extent of current traffic on the GGSN. For further information on what each value represents refer to Nortel GGSN User Guide, 411-5221926. Here is an example:
# show stats hist sm isp=ssg-21-isp-gn
f. show gtpbill <Ga-ISP> Enter show gtpbill <ga-isp> to view the current state of the billing system. Take note of the items in bold. Also execute this command multiple times and verify the RAM Buffer Currently field increments. If current customer network contains two CGFs, verify the state of both CGFs is IDLE. Also verify the object state is set to TO_CGF. If not contact your next level of support.
# 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
411-5221-309
Standard
06.30 March 10, 2010

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 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
499
g. show stats hist apn <ISP name> <APN name> Using the Gi ISP name, verify attaches and detaches are successful for each APN using the following commands. See items in bold below and refer to Nortel GGSN User Guide, 411-5221-926 for the detailed information of the historical statistics: Note: Results are meaningful only for an in-service GGSN.
# show apn all
Note the apn name and the ISP.
GPRS/UMTS
Upgrade Manual
GGSN6.0
500
# show stats hist apn <Gi ISP> <apn name>
Here is an example:
# show stats hist apn ssg-54-isp-gi ssg54auth
APN HISTORICAL STATS for ISP <ssg-49-isp-gi> & APN <apnnoauth-local-radius> 0 SM.NbrActPdpCtxt.Apn.Bgrd.Low 0 SM.NbrActPdpCtxt.Apn.Intact.Low 0 SM.NbrActPdpCtxt.Apn.Strm.Low 0 SM.NbrActPdpCtxt.Apn.Conv.Low 5178 SM.NbrActPdpCtxt.Apn.Bgrd.Medium 0 SM.NbrActPdpCtxt.Apn.Intact.Medium 0 SM.NbrActPdpCtxt.Apn.Strm.Medium 0 SM.NbrActPdpCtxt.Apn.Conv.Medium 0 SM.NbrActPdpCtxt.Apn.Bgrd.High 0 SM.NbrActPdpCtxt.Apn.Intact.High 0 SM.NbrActPdpCtxt.Apn.Strm.High 0 SM.NbrActPdpCtxt.Apn.Conv.High 37032 SM.AttActPdpCtxt.Apn 16901 SM.SuccActPdpCtxt.Apn 37032 SM.AttDynActPdpCtxt.Apn 16901 SM.SuccDynActPdpCtxt.Apn 37032 SM.AttActPdpCtxtAutReq.Apn 6978 SM.FailActPdpCtxtAutReq.Apn 5 SM.AttDeactPdpCtxtMsAndSgsn.Apn 5 SM.SuccDeactPdpCtxtMsAndSgsn.Apn 11718 SM.AttDeactPdpCtxtGgsn.Apn 11718 SM.SuccDeactPdpCtxtGgsn.Apn 5516 SM.MaxNbrActPdpCtxt.Apn 0 SM.AttUpdPdpCtxtMsAndSgsn.Apn 0 SM.SuccUpdPdpCtxtMsAndSgsn.Apn 0 SM.AttUpdPdpCtxtGgsn.Apn 0 SM.SuccUpdPdpCtxtGgsn.Apn 0 SM.FailActPdpCtxtApnDown.Apn 0 SM.NbrDynActPdpCtxt.Apn 0 SM.NbrStaticActPdpCtxt.Apn 0 SM.AttDeactPdpCtxtGgsn.Manual.Apn 0 SM.SuccDeactPdpCtxtGgsn.Manual.Apn
411-5221-309
Standard
06.30 March 10, 2010

0 0 0 0 0 0 0

SM.AttDeactPdpCtxtGgsn.ITO.Apn SM.SuccDeactPdpCtxtGgsn.ITO.Apn SM.AttDeactPdpCtxtGgsn.MaxDur.Apn SM.SuccDeactPdpCtxtGgsn.MaxDur.Apn SM.AttDeactPdpCtxtGgsn.SgsnRstrt.Apn SM.SuccDeactPdpCtxtGgsn.SgsnRstrt.Apn SM.PdpCtxtAclRej.Apn
501
0 SM.NbrActCtxtPrepaid.Apn 0 0 0 0 0 SM.SuccActBamCtxt.Apn SM.SuccActIpsecCtxt.Apn SM.SuccActGreCtxt.Apn SM.SuccActL2tpCtxt.Apn SM.SuccActL2ipCtxt.Apn
0 SM.AttActSecPdpCtxt.Apn 0 SM.SuccActSecPdpCtxt.Apn 0 SM.FailActSecPdpCtxt.NoDataPlaneRsrc.Apn 0 SM.IMSIRuleMatchSucc.Apn 0 SM.IMSIRuleMatchFail.Apn 0 SM.IMSITotRuleComaprisons.Apn 0 SM.SuccActMplsCtxt.Apn 0 SM.SuccActCbbCtxt.Apn 0 SM.NbrActCbbCtxt.Apn 0 SM.MaxNbrActCbbCtxt.Apn
h. show storage Issue the command show storage on both the active and standby CMC cards to verify the amount of disk space available on the GGSN. The paramaters highlighted in bold in the example below indicate the free disk space and disk capacity threshold levels. It is recommended that the current disk capacity threshold be NORMAL or the capacity of disk is less than or equal to 65%. If the command show storage reveals that there is insufficient space to proceed with the upgrade, follow the steps outlined in Section Checkpoint 2 item 8, "Verify sufficient GGSN/SCS space," on page 105 to perform disk cleanup. In case it is determined old accounting files are not needed, refer to GGSN hard drive maintenance procedure in the Nortel GGSN Hardware Installation and Maintenance Guide, 411-5221-923 to delete old accounting files.
502
Here is an example:
ggsn-158(SSU)# show storage Mon 02-Jun-2008 03:32:36 CDT *********************************** * Device Name: /disk *********************************** Volume information -----------------volume descriptor ptr (pVolDesc): cache block I/O descriptor ptr (cbio): auto disk check on mount: max # of simultaneously open files: file descriptors in use: # of different files in use: # of descriptors for deleted files: # of obsolete descriptors:
0x7f2ee140 0x7f2ea1c0 NOT ENABLED 62 30 30 0 0 )
current volume configuration: - volume label: NO LABEL ; (in boot sector: - volume Id: 0x4d590000 - total number of sectors: 78,140,160 - bytes per sector: 512 - # of sectors per cluster: 64 - # of reserved sectors: 32 - FAT entry size: FAT32 - # of sectors per FAT copy: 9,539 - # of FAT table copies: 2 - # of hidden sectors: 0 - first cluster is in sector # 19,110 - Update last access date for open-read-close = FALSE - names style: 8.3 STD DOS - root dir start cluster: 2 FAT handler information: ------------------------ allocation group size: - free space on volume:
123 clusters 37,292,769,282 bytes
Volume space allocation information ----------------------------------- Total space: 40,007,761,926 bytes - Used space: 2,714,992,640 bytes - Free space: 37,292,769,282 bytes Current disk capcity level: NORMAL, 6% used Provisioned disk capacity WARNING threshold: 88% Provisioned disk capacity CRITICAL threshold: 94%
i. show task Use this command to display the tasks running on the primary CMC, their priority and the status of task. The status of PEND (pending), DELAY, or READY are all normal states for a task. SUSPEND is undesirable. For example: show task or show task <task name>
411-5221-309 Standard
06.30 March 10, 2010
503
ggsn-158(SSU)# show task Mon 02-Jun-2008 03:42:37 CDT

NAME ENTRY TID PRI STATUS PC SP ERRNO DELAY ---------- ------------ -------- --- ---------- -------- -------- ------- ----dogmgr dog_catcher 7f6fbd0 0 DELAY 5162c34 7f6df20 0 28 tExcMon excMonTask 7f6c8c0 0 PEND+T 510e0d0 7f67ec8 3d0004 87
Tasks are also run on SSPs. To find out more about a task on a particular SSP, use the command specifying a SSP node. The SSC slot and module can be determined using the show card command.
show task node=p(SSC slot)/(SSM #)/(SSP #)
For example:
show task node=p1/1/1
Use show task to determine if a task has been suspended on the GGSN.
Please contact Nortel support if the status of any task indicates SUSPEND. The show task command can also be used to find the tasks that using high CPU. Issue the command show log event. Scroll through the logs and verify there are no RPC timeouts in the logs.
Also, if the GGSN event log registers an RPC timeout, use show task with the task name of the task in the to node portion of the event to
determine if the task is in suspended mode. j. show cpu This command displays CPU usage information. The command displays a list of different tasks in the system, with the percentages of time each is using the CPU. For example:
ggsn-158(SSU)# show cpu NAME ENTRY TID PRI total % (ticks) delta % (ticks) -------- -------- ----- --- --------------- --------------dogmgr dog_catche effae78 0 0% ( 68) 0% ( 0) ... snmpmgr snmpd_main 263a0410 160 0% ( 0) 0% ( 0) KERNEL 0% ( 659) 0% ( 659) INTERRUPT 0% ( 18) 0% ( 18) IDLE 85% ( 138877) 85% ( 138877) --------------------------------------------------------------
GPRS/UMTS
Upgrade Manual
GGSN6.0
504

TOTAL/DELTA Ticks 37 tasks were created. 32 tasks were deleted.

161631 161631
Use this command if the GGSN exhibits sluggish performance. (During provisioning or high traffic times, high utilization may occur and should not be of concern, unless there are noticeable performance issues.) k. show memusage Use this command to show the memory usage in the system. Execute this command when performance appears to be degrading. This CLI command must be executed multiple times to capture the data and do the comparison.
ggsn-158(SSU)# show memusage Memory Statistics Summary -------------------------------------------Module Instance# allocs mem size # fails cur max cur max ipcmgr 0 62 70 8928 11076 0 parser 0 27242 28558 988533 2911543 0 taskmgr 0 65 68 20540 21488 0 ... cliedit 0 62 62 878 878 0 ------------------------------------------------------------Total 79441 81891 54986387 56565966 0
VXWORKS SYSTEM HEAP SUMMARY: status bytes blocks avg block max block %util ------ ---------- -------- ---------- ---------- ----current free 528094024 31 17035291 607118896 84.1% alloc 99996408 6189 16157 - 15.9% ----- ---------- -------- ---------- ---------- ----total 628090432 6220 cumulative alloc 115160032 9122 12624 -
If the number of failures increment on one of the modules, this could indicate a memory leak. In this case, contact GGSN support. l. show version Executing this command displays the current version of iSOS that is booted on the GGSN, the location of the image and how the node was
411-5221-309 Standard 06.30 March 10, 2010
505
last booted. Make a note of this as it will be used in case of GGSN software rollback. Here is an example of show version. System booted from ata indicate the location of the GGSN image. Make a note of it. For example:
ggsn-158(SSU)# show version Mon 02-Jun-2008 03:48:32 CDT Shasta 5000: IP Services Operating System iSOS (tm), Version ggsns5.0.1-isos-build-17 Built on Fri Sep 15 14:10:48 CDT 2006 by shtbld Copyright (c) 1998-2000 Shasta Networks, Inc. Copyright (c) 2000-2004 Nortel Networks Corporation. All rights reserved. Patch Status: One or more cards have been patched. System booted from ata:/disk/image/CD501/cmc3 System restarted by SCS resync Booted using configuration: primary Slot Port(s) Card Version Status Software Version ---- --------- ----- -------------- ------------------------------------1 1,2,3,4 /SSC Ok built on Sep 15 2006, 14:31:21,ggsns5.0.1-isos-build-17 2 1,2,3,4 /SSC Ok built on Sep 15 2006, 14:31:21,ggsns5.0.1-isos-build-17 3 1,2,3,4 /SSC Ok built on Sep 15 2006, 14:31:21,ggsns5.0.1-isos-build-17 4 1,2,3,4 /SSC Ok built on Sep 15 2006, 14:31:21,ggsns5.0.1-isos-build-17 11 1,2,3,4 /SSC Ok built on Sep 15 2006, 14:31:21,ggsns5.0.1-isos-build-17 12 1,2,3,4 /SSC Ok built on Sep 15 2006, 14:31:21,ggsns5.0.1-isos-build-17
m. Bootorder configuration parameter: Make sure configuration parameter in show bootorder is left blank or set to primary. To verify the settings, issue show bootorder. If the field configuration (s) indicate any other value than empty field or primary, then issue set bootorder in the GGSN CLI. Hit enter to accept default for other bootorder parameters. Reset the configuration field by typing a dot . (without the single quotes) to clear the value. Issue show bootorder and verify the configuration field. n. Login GGSN to verify CMC Redundancy state. If two CMC cards are present they should be in redundant state with the same software version running. On the active CMC, use show redundancy status. For example:
506
shasta-158(SSU)# show redundancy status Standby CMC Redundant -----------------------------Configs in sync iSOS releases identical
o. Check the current status of patch application on the GGSN. Refer to the GGSN patching health check procedure in Nortel GGSN Provisioning Procedures - 411-5221-927. Patching Instructions: 5. Verify if there are any new EMG patches released for the current GGSN release. Refer to the latest Release Notes for GGSN 4.1.1 (for GGSN 4.1.1 release) or GGSN 5.0.1 (for GGSN 5.0.1 release) for the list of released patches. If there are any new EMG patches that have not been applied, consult the customer for applying the new EMG patches. There are multiple options to retrieve the applied patch list from the GGSN.
show patchmgr history show patchmgr history APPLIED show patchmgr history ACTIVATED show patchmgr history DEACTIVATED show patchmgr patchdir <- note this command is applicable only for GGSNs running GGSN 5.0.1.
6. Refer to the latest Release Notes for GGSN 6.0 for the list of released patches. 7. Download the GGSN 6.0 released patches from www.nortel.com 8. FTP the patches/ patch package(s) matching the GGSN 6.0 load to /opt/patches on the SCS server. 9. Accept the patches/ patch package(s) to the SCS. a. Login SCS GUI using Device Owner privilege and select the Patch icon on the left image panel. b. Select the Patch tab and click on the Add button to view a list of patches/ patch package(s) that have been FTPed to the SCS server and not been accepted. To accept individual patches: Each patch has to be added or accepted individually. From the Accept Patch File window, click on the patch to be added from the Patches List. Click OK.
411-5221-309 Standard 06.30 March 10, 2010
507
Patches can also be added in bulk by holding the Shift key and selecting multiple patches. Set the patch Persistency to Persistent. For more detail, refer to section GGSN patch application from the GGSN Provisioning Procedures - 4115221-927. To accept patches as patch packages: From the Accept Patch File window, check the patch package(s) to be added from the Patch Packages pane, set the patch Persistency to Persistent. Click OK. For more details, please refer section Procedure to update Patch Package from the GGSN Provisioning Procedures - 411-5221-927
10. A new combo patch profile should be created and applied to the GGSN prior to upgrade. The combo patch profile includes current release patches and GGSN 6.0 patches. Add all the GGSN 6.0 patches/ patch package(s) to the combo patch profile. The current release patches should be removed from the combo patch profile only after GGSN software upgrade, soak has been completed and determined that the GGSN will not be rolled back to the current GGSN software version. a. From the Patch Manager, clone the current active patch profile. i. Go to Profile tab and click the Add button. Enter a valid name for the combo patch profile name. ii. Use the Select bottom and pick current active patch profile to be cloned. iii. Once new profile is created, a Patch Profile Configuration window will appear. From the Patchable Load pull-down menu, select GGSN 6.0. iv. Once the release load is selected, click the Add button to add GGSN 6.0 patches/ patch package(s). The Add patch rule window will appear. Select the GGSN 6.0 patches/ patch package(s) and click OK. Select proper Scope and Directive for the patch rule. Set the Directive to Deactivate when adding the patch rule. The default settings for the Scope is to apply patch to all cards. If Default is selected, the patch will be applied to appropriate cards automatically. Note: Please consult with the customer prior to activating the Activatable (ACT) patches. Note: Multiple patches can be selected to add multiple patche rules in a single step instead of adding patch rules one at a time. For more details on adding patch rules for individual patches or patch packages, please refer to section
GPRS/UMTS
Upgrade Manual
GGSN6.0
508
GGSN patch application-> Patching functions-> Profile tab from the GGSN Provisioning Procedures - 411-5221-927 v. Repeat previous step for each patch until all GGSN 6.0 patches are added. Note: For more details on GGSN patching instructions, please refer to Nortel GGSN Provisioning Procedures, 411-5221-927. b. Log in to GGSN using telnet or ssh. At the GGSN prompt, type monitor log. You can also login to the GGSN console. c. Launch another SCS client session, login as device owner. Click on Alarm icon in the left panel. This will launch the Alarm Manager panel On the Current Alarm tab, click on the GGSN you are working on. This will display all the alarms generated by the GGSN in the right panel Scroll down the alarm list all the way to the bottom
d. Go to the other SCS client session where patching operation was started. From the Patch Manager screen, choose the Device tab and select the device which is going to be upgraded. Click the Edit button and the Patch Device Configuration window will appear. Click the Select button to select the newly added combo patch profile. Click on the OK button to link the device to the selected profile. The new combo patch profile has overridden the original active patch profile. Important Note: Please note to watch the monitor log events from the telnet or ssh terminal or console till patching is completed before proceeding to the next step. Important Note: Also, go to the Device icon and select the device to be upgraded. Select the Diagnostics & Maintenance and check the session log under Session Log tab to see if the patch profile has been successfully modified. Make sure all GGSN 6.0 patches are downloaded before moving to next step. Important Note: Monitor Alarm Manager with patching during patch application. On Alarm Manager on the SCS client, a patch alarm is generated when a patching operation fails on the GGSN. The alarm is generated whenever a condition is detected that indicates that the GGSN is out of sync with the SCS for patch data. The alarm is generated based on the slot/port/processor that the failure occurred. Only one alarm will be generated for a slot/port/processor, i.e. multiple patching operation failures exist, only one alarm is generated for the slot/port/processor. If the conditions that caused the alarm are resolved, the patch alarm is
411-5221-309
Standard
06.30 March 10, 2010
509
cleared. Please refer to Alarm Guide, NTP 411-5221-921 for more details. Here is an example Patching Alarm where patching operation fails.
Description: Patch data is out of sync Severity: Major Clearable: Yes Alarm type: Patch Probable cause: A patch did not apply to the specified target. Remedial action: Look at the event logs to determine the patch that had the failure.
e. Important Note - Make a note of the combo patch profile name. Do not delete the combo patch profile till it is determined that the GGSN software will not be rolled back to the current load. 11. Transfer the GGSN 6.0 software to the GGSN. The new GGSN software should be available on a FTP server or GGSN CD. The FTP server can be any storage location for the GGSN image files. If the GGSN software is retrieved using ESD (Electronic Software Delivery), please refer to GGSN Software Delivery on page 27 for steps to download the GGSN image to the GGSN. For more details, please refer to section Preparing the GGSN software for an upgrade on page 29 ALERT: Rebooting GGSN 6.0 from /flash is not support for CMC2 cards. a. With an FTP server i. Use the following command to copy image from FTP server to GGSN for both active and standby CMC. You will be prompted for username and password. Be sure to name the directory on the FTP server that is the same as it should be named on the CMC disks. The entire image folder will be transferred, including the folder name.
copy image from=ftp:/<FTP Server IP Address>/ <Full Directory Path to Image Files>/GGSN6.0 to=/disk/image
b. Using FTP to transfer the image on GGSN: i. Use the following commands to create GGSN 6.0 directory (GGSN6.0) in /disk/image.
cd /disk/image
GPRS/UMTS
Upgrade Manual
GGSN6.0
510
GGSN Pre-Upgrade Procedure mkdir GGSN6.0
ii. Open FTP session to GGSN from load server where the image files are located:
Load ftp> ftp> ftp> ftp> Server Command Line> ftp <GGSN IP Address>
cd /disk/image/GGSN6.0 bin prompt mput <image files>
iii. Login to GGSN and copy the image to Standby-CMC:

copy image from=/disk/image/GGSN6.0 to=standby-cmc
Note: The GGSN load can also be loaded from a TFTP server. Please refer to NTP Hardware Installation and Maintenance Guide: 411-5221-923 - section: Boot a CMC card using TFTP for details. 12. If GGSN is not currently using the supported bootrom firmware, transferring firmware files to the GGSN is required. The supported CMC2 bootrom firmware is 8.0(1) or later and the supported CMC3 bootrom firmware is version 2.2(1) or later. All CMCs must have the same version of bootrom. Otherwise, there will be a problem for CMC switch-over. a. Get CMC slot information. Use show card command to get CMC slot information. Here is an example of a GGSN with CMC2 cards:
shasta-19(SSU)# 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 ---1 2 3 4 5 6 7 8 9 10 11 Configured/Found ----------------------SSC /SSC SSC /SSC SSC /SSC SSC /SSC ALC /ALC ELC /ELC SFC /SFC SFC /SFC GELC /GELC ELC /ELC SSC /SSC Enabled -------Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Info ----U U U U U U U U U U U U U U U U U D D D [ICP Rev. 1.6] U U U D D D D D 10G Active [FPGA Rev. 2.0] 10G Standby [FPGA Rev. 2.0] U [FPGA Rev. 0.5] [GBIC Multi] U U U U U U U U U U U U
411-5221-309
Standard
06.30 March 10, 2010

12 13 14 SSC CMC CMC /SSC /CMC /CMC

Enabled Enabled Enabled U U U U Standby (Redundant) Active
511
Here is an example of a GGSN with CMC3 cards.

ssg-141(SSU)# show card
Fri 28-Mar-2008 11:21:49 CDT SSM/CT3/COC3 CPU states: A - auto-reset; N - need catchup; C - catching up; D - in delete U - up; X - failed; '-' - disabled; * - not present M - failover move in progress; v - uncommunicative; d - dumping core; L - loading T - temporarily down ~ - spared overflow pool; ^ - spared failover pool 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 ---3 4 6 8 9 10 12 13 14 Configured/Found ----------------------SSC3 /SSC3 SSC3 /SSC3 GELC /GELC SFC2 /SFC2 GELC /GELC ELC /ELC SSC /SSC CMC3 /CMC3 CMC3 /CMC3 Enabled -------Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Info ----U U U U U U U D [FPGA Rev. 0.5] [GBIC Multi] 10G Active [FPGA Rev. 2.0/30.5] D [FPGA Rev. 0.5] [GBIC Multi] U D U U U U D U U U U U Active Standby (Redundant)
b. Verify the bootrom version for Active CMC card. Use the following command to check the bootrom version on CMC: show card slot=<Active CMC Slot> mode=detail. Here is an example of a GGSN with CMC2 cards:
shasta-19(SSU)# show card slot=14 mode=detail Slot Configured/Found Enabled Info ------------------------------------14 CMC /CMC Enabled Active Memory: 1024M Processor 0 Type: Motorola PPC740/750 (0x80301) Processor 1 Type: Motorola PPC740/750 (0x80301) ROM Version: 8.0(1) Management Ethernet Port (5) is Up: : :
Here is an example of a GGSN with CMC3 cards:

ssg-141(SSU)# show card slot= 13 mode= detail Slot Configured/Found Enabled Info ------------------------------------13 CMC3 /CMC3 Enabled Active Memory: 2048M Processor 0 Type: BCM1250 (0x125011ff) Processor 1 Type: BCM1250 (0x125011ff)
GPRS/UMTS
Upgrade Manual
GGSN6.0
512
Nortel Networks Confidential ROM Version: 2.2(1); DIAG version:
1.20(1) GMII Bridge Version: 9 : :
Verify if ROM Version is equal to 8.0(1) or later for the active CMC2 card or 2.2(1) or later for the active CMC3 card. If the current bootrom firmware version is the supported bootrom version for GGSN 6.0, the bootrom firmware does not require to transfer. In this case, proceed to Step 13. c. Verify the bootrom version for standby CMC card. Use the following command to check the bootrom version on CMC: show card slot=<Standby-CMC Slot> mode=detail. For example:
ssg-149(SSU)# show card slot = 13 mode = detail
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 ------------------------------------13 CMC /CMC Enabled Standby (Redundant) Memory: 1024M Processor 0 Type: Motorola PPC740/750 (0x80301) Processor 1 Type: Motorola PPC740/750 (0x80301) ROM Version: 8.0(1) : :
Verify if ROM Version is equal to 8.0(1) or later for the standby CMC2 card or 2.2(1) or later for the standby CMC3 card. If the current bootrom firmware version is the supported bootrom version for GGSN 6.0, bootrom firmware upgrade is not required, then proceed to Step 13. Otherwise, proceed to the following step to upgrade the GGSN bootrom software. The new GGSN firmware should be available on FTP server or GGSN CD. The FTP server can be any storage location for the GGSN Bootrom
411-5221-309
Standard
06.30 March 10, 2010
513
files. For CMC2 card, use the following steps to transfer firmware to GGSN: a. With an FTP server i. Use the following commands to download Bootrom files from the FTP server for both active and standby CMC if CMC is in redundant mode.
copy file ftp:/<FTP server IP Address>/<Full Directory Path to BootRom Files>/cr_8_0_1.bin /disk/image/bootrom6.0
b. Using FTP to put the firmware on GGSN i. Use the following commands to create bootrom directory from /disk/image.
cd /disk/image mkdir bootrom6.0
ii. Open FTP session to GGSN from load server where the bootrom files are located:
Load ftp> ftp> ftp> Server Command Line> ftp <GGSN IP Address>
cd /disk/image/bootrom6.0 bin put cr_8_0_1.bin
iii. Copy bootrom files to Standby-CMC

copy file from=/disk/image/bootrom6.0/cr_8_0_1.bin to=standby-cmc
For CMC3 card, use the following steps to transfer firmware to GGSN: a. With an FTP server i. Use the following commands to download Bootrom files from the FTP server for both active and standby CMC3 if CMC3 is in redundant mode.
copy file ftp:/<FTP server IP Address>/<Full Directory Path to BootRom Files>/c3_2_2_1.bin /disk/image/bootrom6.0
b. Using FTP to put the firmware on GGSN i. Use the following commands to create bootrom directory from / disk/image.
GPRS/UMTS
Upgrade Manual
GGSN6.0
514
ii. Open FTP session to GGSN from load server where the bootrom files are located:
Load ftp> ftp> ftp> Server Command Line> ftp <GGSN IP Address>
cd /disk/image/bootrom6.0 bin put c3_2_2_1.bin
iii. Copy bootrom files to Standby-CMC

copy file from=/disk/image/bootrom6.0/c3_2_2_1.bin to=standby-cmc
13. Verify if ROM Revision on all SSMs in all SSCs are equal to 6.1(2) for SSC2 cards and 1.5.1 for SSC3. These are the supported bootrom version for GGSN 6.0. If bootrom firmware version is correct, the bootrom firmware file transfer and upgrade is not required. The supported SSC2 and SSC3 bootrom files are: SSC2 bootrom version 6.1(2) - sr6_1_2.bin SSC3 bootrom version 1.5(1) - s3_1_5_1.bin The latest GGSN firmware should be available GGSN 6.0 CD or ESD in the Firmware directory. If the GGSN is running GGSN 5.0.1 software and has SSC3, XFPGA firmware upgrade may be necessary. The supported SSC3 XFPGA firmware version is: 12 SSC3 XFPGA firmware file: SSC3_0C.XSV
a. Identify the slots which the SSC cards (SSC2 or SSC3) occupy. Verify all SSMs are up in the GGSN. Use the following command to get SSC slot information: show card b. For each SSC card listed from the show card command perform a show card slot=<SSC Slot> mode=detail. This will display the Bootrom version for each SSM on the line ROM version:. Here is an example of show card for SSC2.
shasta-19(SSU)# show card slot=1 mode=detail 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
411-5221-309
Standard
06.30 March 10, 2010
515
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 ---1 Configured/Found Enabled Info ---------------------------------SSC /SSC Enabled U U U U SSC state: running EPIF state: running SSM 1 state: running CPU: Motorola PPC745/755 (0x83202) Bus Speed: 83MHz Memory: 512M Encrypt: No Limit ROM version: 6.0(1) <- bootrom version Enet chip: Shasta DV (0x547ffff), rev: 0x2000303 Is in the data mesh Has missed 0 polls Has missed 0 hellos : : SSM 2 state: running CPU: Motorola PPC745/755 (0x83202) Bus Speed: 83MHz Memory: 512M Encrypt: No Limit ROM version: 6.0(1) Enet chip: Shasta DV (0x547ffff), rev: 0x2000303 Is in the data mesh Has missed 0 polls Has missed 0 hellos : : SSM 3 state: running CPU: Motorola PPC745/755 (0x83202) Bus Speed: 83MHz Memory: 512M Encrypt: No Limit ROM version: 6.0(1) Enet chip: Shasta DV (0x547ffff), rev: 0x2000303 Is in the data mesh Has missed 0 polls Has missed 0 hellos : : SSM 4 state: running CPU: Motorola PPC745/755 (0x83202) Bus Speed: 83MHz Memory: 512M Encrypt: No Limit ROM version: 6.0(1) Enet chip: Shasta DV (0x547ffff), rev: 0x2000303 Is in the data mesh Has missed 0 polls Has missed 0 hellos
GPRS/UMTS
Upgrade Manual
GGSN6.0
516
Here is a snapshot of show card for SSC3:

# show card slot= 2 mode= detail SSM/CT3/COC3 CPU states: A - auto-reset; N - need catchup; C - catching up; D - in delete U - up; X - failed; '-' - disabled; * - not present M - failover move in progress; v - uncommunicative; d - dumping core; L - loading T - temporarily down ~ - spared overflow pool; ^ - spared failover pool 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 ---2
Configured/Found Enabled Info ---------------------------------SSC3 /SSC3 Enabled U U U U SSC3 state: running SEC state: running XPIF state: running SSM 1 state: running CPU: BCM1250 (0x125011ff) Bus Speed: 357MHz Memory: 1024M Encrypt: No Limit ROM version: 1.5(1) <- bootrom version DIAG ROM version: 3.13 GGI GMII Bridge A version: 12 <-XFPGA version GGI GMII Bridge B version: 12 <-XFPGA version SEC GMII Bridge version: 7 ... SSM 2 state: running CPU: BCM1250 (0x125011ff) Bus Speed: 357MHz Memory: 1024M Encrypt: No Limit 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 ... SSM 3 state: running CPU: BCM1250 (0x125011ff) Bus Speed: 357MHz Memory: 1024M Encrypt: No Limit
411-5221-309
Standard
06.30 March 10, 2010

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 ... SSM 4 state: running CPU: BCM1250 (0x125011ff) Bus Speed: 357MHz Memory: 1024M Encrypt: No Limit 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
517
c. If a firmare upgrade is required, transfer the firmware files to the GGSN. There are 2 options given below: GGSN copy file option: If the standby CMC card is in redundant status, the following copy file command option can be used to transfer the firmware file to both the active and standby CMC cards with the execution of the copy file command.
For SSC2: copy file ftp:/<FTP Server IP Address>/<Full Directory Path to BootRom Files>/sr6_1_2.bin /disk/ image/bootrom6.0 For SSC3: copy file ftp:/<FTP Server IP Address>/<Full Directory Path to BootRom Files>/s3_1_5_1.bin /disk/ image/bootrom6.0
Using FTP to transfer the firmware to the GGSN: With this option, the firmware files must be ftped to the active and standby CMC cards individually. Use the following commands to create bootrom directory from / disk/image.
Open FTP session to GGSN from load server where the bootrom files are located:
Load Server Command Line> ftp <GGSN IP Address> ftp> cd /disk/image/bootrom6.0 ftp> bin
GPRS/UMTS
Upgrade Manual
GGSN6.0
518

For SSC2 bootrom: ftp> put sr6_1_2.bin For SSC3 bootrom: ftp> put s3_1_5_1.bin
For SSC3 XFPGA firmware ftp> put SSC3_0C.XSV
Copy bootrom files to Standby-CMC
For SSC2: copy file from=/disk/image/bootrom6.0/sr6_1_2.bin to=standby-cmc
For SSC3: copy file from=/disk/image/bootrom6.0/s3_1_5_1.bin to=standby-cmc For SSC3 XFPGA firmware copy file from=/disk/image/bootrom6.0/SSC3_0C.XSV to=standby-cmc
14. Use "show healthcheck" CLI command to determine whether the Health Check Monitor is enabled or not so that the same setting can be provisioned in post-upgrade procedure. If the functionality is enabled (i.e. "Monitoring status" is "ACTIVE"), make a note for the Nodal Success Rate Threshold Value and the Network Success Rate Threshold Value. Refer to the Nortel GGSN 6.0 User Guide NTP 411-5221-926 (search for Health Check Monitor (HCM)) for more details.
ggsn-158(SSU)# show healthcheck Mon 02-Jun-2008 04:00:44 CDT <HEALTH CHECK MONITOR> Monitoring status: Profile Name: hcm End of Last Monitoring Interval: 2008 Current Network Success Rate: Network Success Rate Threshold Value: Current Nodal Success Rate: Nodal Success Rate Threshold Value: ACTIVE Mon Jun 2 4:0:0
IDLE 90% IDLE 95%
411-5221-309
Standard
06.30 March 10, 2010
519
Attempted Activations: Attempted Activations Threshold:
IDLE 0
15. If upgrading from GGSN 4.1.1 to GGSN 6.0 ensure that the patch G411_01303739EMG_ISPMGR is marked as persistent and a rule for the patch has been added to the combo patch profile and the patch is activated. 16. User is ready to proceed to GGSN Upgrade Procedure on page 521.
GPRS/UMTS
Upgrade Manual
GGSN6.0
520
411-5221-309
Standard
06.30 March 10, 2010
521

GGSN upgrade options
GGSN 6.0 software upgrade has the following options: Upgrade from GGSN 4.1.1 to GGSN 6.0 Upgrade from GGSN 5.0.1 to GGSN 6.0
36
36
The GGSN software upgrade options listed above are detailed in this chapter and have similar upgrade procedure. In case, GGSN card upgrades are performed during the GGSN 6.0 upgrade: CMC2 server port migration and CMC2 to CMC3 card upgrade can be performed after the software upgrade to GGSN 6.0 release. If a SFC1 to SFC2 card upgrade is planned, and if the GGSN is currently operating on CMC2 cards, perform the CMC2 to CMC3 card upgrade prior to starting the SFC1 to SFC2 card upgrade.
GSGN Upgrade Steps

Table 28 GGSN upgrade procedure Step Duration (Hours:Mins) Upgrade Total 1 2 3 0:02 0:04 0:08 Current Step 0:02 0:02 0:04
(between 0:02 and 0:04)
36
Description
Down Time 0.02 0.02 0:04 Prepare GGSN for upgrade by rejecting all incoming traffic, See Reject GGSN incoming traffic on page 522. Update CMC bootrom firmware if required, See Update CMC bootrom firmware on page 524. Update SSC bootrom firmware if required, See Update SSC bootrom firmware on page 526.
0:10
0:02
0:02
If the GGSN has SSC3 cards, Update SSC3 XFPGA firmware if required, See Update SSC3 XFPGA firmware on page 528 Upgrade GGSN software to GGSN 6.0 and resync the GGSN, See Upgrade to GGSN 6.0 software on page 533. Note: The GGSN upgrade time is around 10 minutes if CMC and SSC firmware upgrade is not required.
0:20
0.10
(between 0:04 and 0:10)
0.10
GPRS/UMTS
Upgrade Manual
GGSN6.0
522
Reject GGSN incoming traffic 1. Set the GGSN to deny new incoming traffic. This should be done before actual upgrade is performed. In order to minimize the impact to subscribers who are trying to activate PDP sessions, the following steps should be implemented to reject new traffic on the GGSN that is being upgraded. Note: If a secondary GGSN is available, traffic can be redirected to it. a. Login Gn ISP through SCS Client. b. Select Access Properties -> Tunnels -> GTP c. Select the GTP tunnel and click Edit. d. Select the device under "Device Specific Settings" and click Edit to modify the device specific setting. e. Check the box for "Disallow PDP Context Creation" on GTP Tunnel Device Configuration window. f. Select "No Resources Available" for "Redirect Response Cause" on the same window, GTP Tunnel Device Configuration window. g. Click "OK" at the bottom of the "GTP Tunnel Device Configuration" menu h. Click "OK" at the bottom of the "GTP Tunnel Configuration" menu. 2. Login to the GGSN and run the CLI command show stats hist sm <gn_isp> to determine the number of active PDP sessions in Gn ISP:
# show stats hist sm <Gn ISP name>
3. All active PDP contexts should be closed before upgrade. Since new contexts are not allowed on the GGSN, operator can either wait till all PDP contexts are closed or use the techniques listed below to close all active PDP contexts before upgrade. a. Manually take down existing PDP contexts. i. Login Gn ISP through SCS Client. ii. Select Access Properties -> Tunnels -> GTP iii. Select the GTP tunnel and click Edit to modify the GTP tunnel setting. iv. Select the device and click Edit to modify device specific setting. v. Click Initiate for Terminate Existing PDP Contexts to take down all existing PDP Context on GGSN. vi. Click OK. vii. Click OK to exit GTP Tunnel Configuration window.
411-5221-309 Standard 06.30 March 10, 2010
523
b. Make ensure all billing information is preserved before upgrade. i. Login to GGSN ii. Enter the following CLI commands:
# show gtpbill <Gn ISP Name> # show gtpbill <Ga ISP Name>
iii. Check the results of show gtpbill <Gn ISP Name> and show gtpbill <Ga ISP Name> for the counters Currently: ext blocks in buffer, "Ext Blks on Reg Unproc Lst", Ext Blks on Hot Unproc Lst and "Num Pkts Wait Ack Q. Proceed to the next step if all parameters display a value of zero. iv. Use the following CLI command to disable gtpbill audit:
# gtpbill audit <Ga ISP Name> disable
v. Use the following CLI command to verify the gtpbill audit has been disabled:
# show gtpbill <Ga ISP Name>
vi. Issue the following commands to flush the billing and audit records to the disk.
gtpbill flush billing isp= <ga_isp> force gtpbill flush audit isp= <ga_isp>
Perform next step only if RADIUS Accounting is enabled and RADIUS Profile is configured. Any remaining RADIUS Accounting files on disk will be deleted upon reboot/resync. 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 GGSN, issue the following CLI commands: Find out the Connection ISP name.
# show isp
Find out the RADIUS Profile name. Also make a note of the accounting port number for each profile.
# show radius <Connection ISP name>
The below CLI commands needs to be executed once for each RADIUS Profile.
GPRS/UMTS
Upgrade Manual
GGSN6.0
524
radacct manager flushdiskbuff profile= <profilename> isp= <ispname> acct_port=<accounting_port> radacct manager disksend profile=<profilename> isp=<ispname> vpn=<vpnname> acct_port=<acctport> action= start
Note: Refer to the show radius <isp> command to get information for <acct_port> for each RADIUS Profile. RADIUS accounting records may also be left on disk and implicitly deleted during a reboot/resync. For example, RADIUS accounting records are only being used for identity propagation. Check with your system administrator on how to proceed. Update CMC bootrom firmware The supported bootrom firmware for GGSN 6.0 are: CMC2 bootrom version 8.0(1) - cr_8_0_1.bin CMC3 bootrom version 2.2(1) - c3_2_2_1.bin If the GGSN is not currently using the bootrom firmware listed above, new bootrom files should already be transferred to the GGSN in step 12. of GGSN Pre-Upgrade procedure. In this case, bootrom firmware update is required. If the GGSN is using correct bootrom, skip the rest of this section and proceed to Upgrade to GGSN 6.0 software on page 533. The following sections provide the procedures for updating bootrom firmware. Change CMC bootrom firmware 1. Make sure all the CMC cards are in service and if both CMC cards are inserted on the GGSN, make sure the Standby CMC card is in Redundant mode. 2. Get CMC slot information. Use the following command to get CMC slot information: show card. For example:
shasta-20(SSU)# 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 M - failover move in progress; v - uncommunicative; d - dumping core; L - loading T - temporarily down ~ - spared overflow pool; ^ - spared failover pool 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)
411-5221-309
Standard
06.30 March 10, 2010
525
Slot Configured/Found Enabled Info ------------------------------------1 SSC /SSC Enabled U U U U 2 SSC /SSC Enabled U U U U 3 SSC /SSC Enabled U U U U 4 SSC /SSC Enabled U U U U 5 ALC /ALC Enabled U U U U [ICP Rev. 1.7] 6 ELC /ELC Enabled U U U D D D D D 7 SFC /SFC Enabled 10G Active [FPGA Rev. 3.0] 8 SFC /SFC Enabled 10G Standby [FPGA Rev. 3.0] 9 GELC /GELC Enabled U [FPGA Rev. 0.5] [GBIC Multi] 10 ELC /ELC Enabled U U U U U U U U 11 SSC /SSC Enabled U U U U 12 SSC /SSC Enabled U U U U 13 CMC3 /CMC3 Enabled Standby (Redundant) 14 CMC3 /CMC3 Enabled Active
3. If a CMC firmware upgrade is require, update bootrom firmware for Active CMC card. Use the following command to update the bootrom version on CMC2 card: a. From CMC2 Bootrom revision 5.0.2 or earlier
update bootrom cmc file= /disk/image/bootrom6.0/cr_8_0_1.bin
confirm (y) yes Non Redundant (y) yes
Repeat the update command listed above one more time to update secondary bootrom on Active CMC2. b. Update the CMC bootrom version: From CMC2 Bootrom revision 6.0.1 or later: Update the primary bootrom:
update bootrom cmc bootrom=0 file=/disk/image/bootrom6.0/ cr_8_0_1.bin confirm (y) yes
Warning: Firmware updates to bank 0 are not redundant. Do you wish to continue? Confirm [y/n]: y
Update the secondary bootrom:
update bootrom cmc bootrom=1 file=/disk/image/bootrom6.0/ cr_8_0_1.bin confirm (y) yes
For CMC3 card, use the following CLI command:
GPRS/UMTS
Upgrade Manual
GGSN6.0
526
update bootrom cmc3 slot=<slot #> file=/disk/image/ bootrom6.0/c3_2_2_1.bin
4. Update bootrom firmware for Standby CMC card. Use the following applicable command to update the bootrom. For CMC2 Bootrom revision 5.0.2 and 6.0.1 or later
update bootrom cmc slot=<Standby CMC Slot> bootrom=0 file=/ disk/image/bootrom6.0/cr8_0_1.bin confirm (y) yes
Warning: Firmware updates to bank 0 are not redundant. Do you wish to continue? Non Redundant (y) yes
update bootrom cmc slot=<Standby CMC Slot> bootrom=1 file=/ disk/image/bootrom6.0/cr8_0_1.bin confirm (y) yes
For CMC3 card, use the following CLI command:

update bootrom cmc3 slot=<standby CMC slot #> file=/disk/ image/bootrom6.0/c3_2_2_1.bin
Update SSC bootrom firmware 5. If a SSC bootrom upgrade is required, update firmware for SSM. For SSC2: Use the following command to update the bootrom version on SSC2 SSM:
update bootrom ssm all file= /disk/image/bootrom6.0/sr6_1_2.bin
Here is an example to upgrade SSM bootrom from 5.0(2) to 6.1(2):

shasta-19 (SSU)# update bootrom ssm all file=
/disk/image/bootrom6.0/sr6_1_2.bin
Confirm [y/n]: y This Firmware will make boot non-redundant Confirm [y/n]: y Flashing SSMs with version 6.1(2), 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 Updating SSM slot 1 module 2 boot ROM. Please wait...
For SSC3: Use the following command to update the bootrom version on SSC3 SSM:
411-5221-309 Standard
06.30 March 10, 2010

update bootrom ssc3 slot= 2 file= /disk/image/bootrom6.0/S3_1_5_1.BIN
527
Here is an example:
ssg-141(SSU)# update bootrom ssc3 slot= 2 file= /disk/image/bootrom6.0/S3_1_5_1.BIN Confirm [y/n]: y erasing CRM flash from 00000000 to 001FFFFF Erase command sequence done Flash erase succeeded from 00000000 to 001FFFFF Writing file /disk/image/g501cd/S3_1_5_1.BIN to CRM flash address 0 flash write complete: 576896 bytes at address 00000000
GPRS/UMTS
Upgrade Manual
GGSN6.0
528
Update SSC3 XFPGA firmware If the GGSN has SSC3 cards, SSC3 XFPGA firmware update may be required. 6. Telnet/ ssh to the GGSN with a username with SSU (Super Super User privilege) 7. 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

shasta-44(SSU)# show card Thu 25-Jan-2007 07:02:07 CST SSM/CT3/COC3 CPU states: A - auto-reset; N - need catchup; C - catching up; D - in delete U - up; X - failed; '-' - disabled; * not present M - failover move in progress; v - uncommunicative; d - dumping core; L - loading T - temporarily down ~ - spared overflow pool; ^ - spared failover pool 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 ---- ---------------------- -------1 SSC3 /SSC3 Enabled 3 SSC3 /SSC3 Enabled 5 ALC /ALC Enabled 6 ELC /ELC Enabled 7 SFC2 /SFC2 Enabled 30.5] 8 SFC2 /SFC2 Enabled 30.5] 9 GELC /GELC Disabled Multi] 10 ELC /ELC Enabled 11 SSC3 /SSC3 Enabled 13 CMC3 /CMC3 Enabled 14 CMC3 /CMC3 Enabled
Info ----U U U U U U U U U U U U [ICP Rev. 1.7] U U U U U U U U 10G Active [FPGA Rev. 2.0/ 10G Standby [FPGA Rev. 2.0/ D [FPGA Rev. 0.5] [GBIC U U D U U U D U U U U U Active Standby (Redundant)
8. Make a note of the current SSC3 XFPGA version using the following command
ggsn(SSU)# show card slot=<SSC3 slot> mode=detail
The version will appear as:
411-5221-309
Standard
06.30 March 10, 2010
529
GGI GMII Bridge A version: <version number> GGI GMII Bridge B version: <version number>
9. Login to the console port of the GGSN. 10. 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: 11. 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. Note: If the GGSN has only 1 SSC3 card, users will not be able to disable the SSC3 card from the SCS client. In this case, login to the GGSN as admin user. Then issue the command disable card slot=<SSC3 slot>. Note: If the GGSN has only 1 SSC3 card, disabling the SSC3 card will cause service interruption till the SSC3 card is enabled back. The SSC3 card will be enabled after the XFPGA firmware upgrade. 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: slot 1 removal processing done 25-Jan-2007 07:37:29 13/1/1:sspmgr,0: slot 1 removal processing done 25-Jan-2007 07:37:29 13/1/1:sspmgr,0: slot 1 removal processing done 25-Jan-2007 07:37:29 13/1/1:sspmgr,0: slot 1 removal processing done 13, 1, INFO, SSM 1 in 13, 1, INFO, SSM 2 in 13, 1, INFO, SSM 3 in 13, 1, INFO, SSM 4 in
12. On the other telnet/ ssh terminal, perform show card and verify the SSMs are indicated by *.
Slot ---1 Configured/Found ----------------------SSC3 /SSC3 Enabled -------Disabled Info ----* * * *
13. Update SSC3 XFPGA firmware
GPRS/UMTS
Upgrade Manual
GGSN6.0
530
ggsn(SSU)# update xfpga type= ssc3 slot= <SSC3 slot> file= <directory path for SSC3_0C.XSV>

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

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

09-Jun-2008 23:18:40 13/1/1:cli,2: admin@/pty/tel00.S: [Attempting]: update xfpga type= ssc3 slot= 1 file= /disk/ SSC3_0C.XSV 09-Jun-2008 23:18:43 13/1/1:cli,2: admin@/pty/tel00.S: [Success]: update xfpga type= ssc3 slot= 1 file= /disk/ SSC3_0C.XSV
14. 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. Note: If the GGSN has only 1 SSC3 card and disable card slot=<SSC3 slot> command was used to disable the SSC3 card, then login to the GGSN as admin user and execute the command enable card slot=<SSC3 slot> to enable the SSC3 card. Here the GGSN logs from monitor log
09-Jun-2008 23:18:50 13/1/1:cardmgr,0: 33, 1, INFO, Card in slot 1 has been enabled. 09-Jun-2008 23:18:50 13/1/1:cli,2: admin@/pty/tel00.S: [Success]: enable card slot= 1 09-Jun-2008 23:18:50 13/1/1:cardmgr,0: 34, 1, INFO, Card in slot 1 is up.
411-5221-309
Standard
06.30 March 10, 2010
531
Note: If patches are applied to the GGSN and include SSP patches, these patches will be reapplied with the SSC3 card comes up
09-Jun-2008 23:19:10 13/1/1:sspmgr,0: 3, 1, CLEAR, SSM 1 slot 1 is up 09-Jun-2008 23:19:10 13/1/1:sspmgr,0: 3, 1, CLEAR, SSM 2 slot 1 is up 09-Jun-2008 23:19:10 13/1/1:sspmgr,0: 3, 1, CLEAR, SSM 3 slot 1 is up 09-Jun-2008 23:19:10 13/1/1:sspmgr,0: 3, 1, CLEAR, SSM 4 slot 1 is up 09-Jun-2008 23:19:10 1/1/2:com,0: 2, 1, INFO, Overload: Resource cpu has been enabled. 09-Jun-2008 23:19:10 1/1/2:com,0: 2, 1, INFO, Overload: Resource interrupt has been enabled. in in in in
15. Verify all the SSMs are up.

ggsn(SSU)# show card

Slot ---1 Configured/Found ----------------------SSC3 /SSC3 Enabled -------Enabled Info ----U U U U
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 be 12
Slot ---1 Configured/Found ----------------------SSC3 /SSC3 Enabled -------Enabled Info ----U U U U
SSC3 state: running SEC state: running XPIF state: running SSM 1 state: running CPU: BCM1250 (0x125011ff) Bus Speed: 357MHz Memory: 1024M Encrypt: No Limit 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 SSM 2 state: running CPU: BCM1250 (0x125011ff) Bus Speed: 357MHz
GPRS/UMTS
Upgrade Manual
GGSN6.0
532
Nortel Networks Confidential Memory: 1024M Encrypt: No Limit 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
SSM 3 state: running CPU: BCM1250 (0x125011ff) Bus Speed: 357MHz Memory: 1024M Encrypt: No Limit 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 SSM 4 state: running CPU: BCM1250 (0x125011ff) Bus Speed: 357MHz Memory: 1024M Encrypt: No Limit 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
16. Repeat steps Step 11 through Step 15 (above) to update the XFPGA firmware on the other SSC3 cards. Perform SSC3 XFPGA firmware upgrade 1 SSC3 card at a time. When the SSC3 firmware upgrade completes and all the SSMs are up, then proceed to upgrading the second SSC3.
411-5221-309
Standard
06.30 March 10, 2010
533
Upgrade to GGSN 6.0 software This section explains to procedure to upgrade GGSN 4.1.1 or GGSN 5.0.1 to GGSN 6.0. 1. Issue the CLI command show bootorder to record the original setup prior to any changes. 2. Before performing the set bootorder command, check to ensure that the load exists in /disk/image directory. 3. Make a note of the current GGSN boot directory. This entry can be found from show bootorder command on the GGSN. Note down the path listed in boot file1 (f1). Use this path as the second boot file option when executing set bootorder (next step) Here is an example with GGSN on 4.1.1. Here the current ggsn boot directory is /disk/image/G411_9/cmc.
ssg-18(SSU)# show bootorder flags (f) : 0x80 boot file1 (f1) : /disk/image/G411_9/cmc boot file2 (f2) : /disk/image/G401_4/cmc boot file3 (f3) : /disk/image/isn/cmc boot file4 (f4) : /flash/image/isn/cmc boot server address (h): 47.104.4.133 configuration (s) : diag mode (dm) : 0x0 core dump mode (cm) : 0x1 ether mode (pm) : 0x311311
Here is an example with GGSN on 5.0.1.

ggsn-158(SSU)# show bootorder Mon 02-Jun-2008 05:22:25 CDT flags (f) : 0x80 boot file1 (f1) : /disk/image/CD501/cmc3 boot file2 (f2) : /disk/image/G401_4/cmc boot file3 (f3) : /disk/image/isn/cmc3 boot file4 (f4) : /flash/image/isn/cmc boot server address (h): configuration (s) : diag mode (dm) : 0x0 core dump mode (cm) : 0x1 ether mode (pm) : 0x411011
4. Make sure the location of boot file3 (f3) and boot file4 (f4) are set to the following
CMC2 (f3): /disk/image/isn/cmc CMC3 (f3): /disk/image/isn/cmc3
GPRS/UMTS
Upgrade Manual
GGSN6.0
534
CMC2 (f4): /flash/image/isn/cmc CMC3 (f4): /flash/image/isn/cmc3
Note: Prior to setting boot file4 (f4) below issue command dir /flash/ image/isn to confirm that the isn image is present on the flash. If the isn image is not present do not set boot file4 (f4). Same applies to boot file3 (f3). Use the next step to set GGSN software to GGSN 6.0. 5. Use set bootorder command to change the bootorder to select GGSN 6.0 software image: a. For GGSN with CMC2, change bootorder on GGSN to select GGSN 6.0 software. Step to set bootorder for CMC3 is captured after the below example. Here is an example of the set bootorder command on CMC2:
ssg-18(SSU)# set bootorder '.' = clear field; flags (f) '-' = go to previous field; ^D = quit
: 0x80 <-If current value not set to 0x80, enter 0x80
boot file1 (f1) : /disk/image/G411_9/cmc <- At the prompt, type the location where GGSN 6.0 load has been FTPed. Example:/disk/image/GGSN6.0/cmc. Remember to add a CMC at the end of the boot directory boot file2 (f2) : /disk/image/G401_4/cmc <- Type current GGSN boot directory boot file3 (f3) : /disk/image/G401_4/cmc <- Type /disk/image/isn/cmc boot file4 (f4) : <- Type /flash/image/isn/cmc boot server address (h): <- if you have a TFTP server with a valid GGSN image, set the server IP here configuration (s) : <- Make sure this field is left blank or indicates primary. If this field is set to any other value, will cause resync failure diag mode (dm) : 0x0 <-If set to 0x1, set to 0x0
411-5221-309
Standard
06.30 March 10, 2010
535
core dump mode (cm) : 0x1 <- To enable core dump flag, set to 0x1. Otherwise, set it to 0x0
Note: GGSN provisioning procedures, 411-9221-927 has the recommended configuration in the set bootorder CLI b. For GGSN with CMC3 card, change bootorder on GGSN to select GGSN 6.0 software. Use set bootorder command to change the bootorder to select GGSN 6.0 software image. Here is an example set bootorder on CMC3
ssg-141(SSU)# set bootorder '-' = go to previous field; ^D = quit
'.' = clear field; flags (f)
boot file1 (f1) : /disk/image/G411_0/cmc3 <-At the prompt, type the location where GGSN 6.0 load has been FTPed. Example:/disk/image/GGSN6.0/cmc. Remember to add a CMC3 at the end of the boot directory boot file2 (f2) : /disk/image/WK636_14/cmc3 <-Type current GGSN boot directory boot file3 (f3) : /disk/image/G411_9/cmc3 <-Hit enter to select default boot file4 (f4) : /disk/image/isn/cmc3 <-Make sure to set it to /disk/image/isn/cmc3 boot server address (h): 47.104.6.14 <-if you have a TFTP server with a valid GGSN image, set the server IP here configuration (s) : <- Make sure this field is left blank or indicates primary. If this field is set to any other value, will cause resync failure diag mode (dm) : 0x0 <-If set to 0x1, set to 0x0 core dump mode (cm) : 0x1 GPRS/UMTS Upgrade Manual GGSN6.0
536
Nortel Networks Confidential <-To enable core dump flag, set to 0x1. Otherwise, set it to 0x0
Note: Depending on current active GGSN load, the boot file3(f3) for CMC2 card or boot file2(f2) for CMC3 card can be set to the current GGSN version running on the GGSN. 6. Issue the CLI command show bootorder to verify the bootorder setting change. Login to the standby-cmc and issue the command show bootorder and make sure the bootorder matches the active cmc card. If show bootorder is not matching, please contact Nortel support. 7. Verify the image files exists in the boot file1 directory path. Issue the command dir <boot directory> and verify the image files exists. Note, do not include the cmc or cmc3 from the boot file1 path. Here is an example:
dir /disk/image/GGSN6.0
If the image file are not listed, re-FTP the image files to /disk/image/GGSN6.0 directory. 8. Note: This step is applicable to GGSN 4.1.1 to 6.0 upgrade only: Determine all the Gi ISPs configured. Login to each Gi ISP from the SCS Client. View the Gi interface to see if the allow tunnel termination box is checked. If not, check it. Here are the steps. Log in to the GGSN and issue the command show apn Make note of the ISP names associated with the APNs. Log in the SCS client as the ISP. Double click the GGSN, click Trunk Interfaces. Double click on each trunk interface and check Allow Tunnel Termination. Repeat the above steps for all ISPs. 9. Log in the GGSN console if available. 10. Log in to SCS through SCS Client as device owner user. 11. To complete the upgrade procedure, right click on the GGSN device involved in the upgrade and select Diagnostics & Maintenance. Select the Device Maintenance tab. Click the Resync with iSOS Ver button and select GGSNS6.0. Click OK.
411-5221-309
Standard
06.30 March 10, 2010
537
12. This displays a confirm window. Read the content in window and click YES. Note: Make sure to continuously monitor the device resync status. During the resync process, in the case a pop-up information window appears questioning whether or not to continue the resync, click "YES". Clicking "NO", or failing to respond to this pop-up inquiry, may cause the GGSN to prematurely terminate the boot process and go out of sync with the SCS. 13. If GGSN console access is available, monitor the console. If there are any errors displayed, contact Nortel support for any clarifications. 14. Wait for the GGSN to come back In Service (InSync). Recovery time depends on the amount of installed hardware and network provisioning. 15. Verify the software is upgrade successfully by checking the GGSN on SCS Client goes InSync with the new software loadname listed besides the GGSN device. 16. If the redundant CMC is not synced, force the new software load to the standby card by typing the following CLI command:
copy image /disk/image/GGSN6.0 standby-cmc
17. Verify the standby CMC resyncs in a redundant state with the new software. Use the following command to show if the CMC cards are in redundant mode: show redundancy status. For example:
ssg-141(SSU)# show redundancy status Redundancy Profile Name : default SSM Redundancy for Aggr Status: Disabled CMC Redundancy Status: Cold Standby CMC Redundant --------------------------------------------Configs in sync iSOS releases different Card types identical Task privilege : 0
18. Use the following command to show the new version of the GGSN software: show version.
ssg-141(SSU)# show version Fri 02-May-2008 20:22:41 Shasta 5000: IP Services Operating System iSOS (tm), Version ggsns6.0i-isos-build-61 Built on Thu Apr 17 11:07:49 CDT 2008 by shtbld 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/G60-61/cmc3
GPRS/UMTS
Upgrade Manual
GGSN6.0
538

System restarted by CLI reload Booted using configuration: primary
Slot Port(s) Card Version Status Software Version ---- --------- ----- -------------- ------------------------------------2 1,2,3,4 /SSC3 Ok built on Apr 17 2008, 11:33:38,ggsns6.0i-isos-build-61 4 1,2,3 /SSC3 Ok built on Apr 17 2008, 11:33:38,ggsns6.0i-isos-build-61 12 1,2,3,4 /SSC Ok built on Apr 17 2008, 11:28:42,ggsns6.0i-isos-build-61
19. Identify the slots which the CMC cards occupy. Use the following command to get CMC slot information: show card. 20. If a CMC bootrom upgrade was performed, verify the CMC bootrom upgraded successfully. Use the following command to check the bootrom version on CMC(s):
show card slot=<Active CMC Slot> mode=detail show card slot=<Standby CMC Slot> mode=detail
Verify if Boot ROM Revision is equal to 8.0(1) or later for CMC2 cards, 2.2(1) or later for CMC3 cards. All CMCs must have the same version of bootrom. 21. Verify the bootrom is updated properly. Use the following command to check the bootrom version on SSMs:
show card slot=<SSC Slot> mode=detail
22. If a SSC bootrom upgrade was performed, verify if ROM Revision on all SSMs are equal to 6.1(2) for SSC2 SSM and 1.5.1 for SSC3 SSM. All SSMs on all SSCs must have the same version of bootrom. 23. Set the GGSN to allow new incoming traffic a. Login Gn ISP through SCS Client. b. Select Access Properties -> Tunnels -> GTP. c. Select the GTP tunnel and click Edit. d. Select Device under GTP Tunnel, click Edit and un-select Disallow PDP Context Creation on GTP tunnel device. e. Login to the GGSN to verify the GTP tunnel setting change. Make sure the Disallow PDP Context Creation is set to FALSE.
Find out the Gn ISP name. # show isp Find out the GTP tunnel name. # show tunnel
411-5221-309
Standard
06.30 March 10, 2010
539
# show tunnel <GTP tunnel name> <Gn ISP name>
GPRS/UMTS
Upgrade Manual
GGSN6.0
540
411-5221-309
Standard
06.30 March 10, 2010
541

GGSN Post-Upgrade Procedure duration
Table 29 GGSN post-upgrade procedure timing Step Duration (Hours:Mins) Upgrade Total 1 0:10 Current Step 0:10 Down Time 0:00 GGSN post-upgrade procedure Description
37
37
Steps after GGSN upgrade
37
1. The system checks must be performed after the upgrade to verify overall system integrity. The baseline output captured prior to the upgrade can be used for comparison in case any anomalies are detected. Refer to the commands specified in Step 4. in GGSN Pre-Upgrade Procedure on page 495 for GGSN post-upgrade checks. 2. Ensure that all the Image files exist in the boot directory including the MANIFEST file. Note: If they do not all exist, contact product support. 3. Ensure that all GGSN 6.0 patches are applied on the GGSN by using the following command:
show patchmgr history
Make sure all the GGSN 6.0 patches are applied Make sure none of the GGSN 4.0.1 or GGSN 4.1.1 or GGSN 4.1 patches are applied using the same CLI command. If you are upgrading from GGSN 5.0 to 5.0.1, make sure noe of the GGSN 5.0 patches are applied
4. Launch another SCS client session, login as device owner. Click on Alarm icon in the left panel. This will launch the Alarm Manager panel On the Current Alarm tab, click on the GGSN you are working on. This will display all the alarms generated by the GGSN in the right panel Scroll down the alarm list all the way to the bottom Verify there are no patch related alarms. Please refer to Alarm Guide, NTP 411-5221-921 for alarm details.
542
5. Perform critical call testing to make sure all calls go through as expected. 6. Please contact the customer for billing verification. It is recommended to verify the billing records during the critical call testing. Refer to Nortel GGSN 6.0 Billing Samples NTP 411-5221-206 for latest information. 7. For GGSN 4.1.1 to GGSN 6.0 upgrade only: If Secure PAP/CHAP L2TP negotiation feature is enabled before upgrade, then it needs to be enabled after upgrade. Perform the following steps via SCS: Login SCS with Gn ISP privilege Under Access Properties for Tunnels GTP, goes to Device Specific Settings under the General tab of the GTP Tunnel Configuration Dialog Check L2TP Secure PAP box to turn on this functionality Use show tunnel mode=verbose CLI to verify that the functionality is enabled (i.e. "L2TP secure PAP" is "YES") 8. If CMC bootrom was upgraded prior to GGSN upgrade, verify CMC2 (or CMC3) bootrom is updates. Use the following command to check the bootrom on the CMC: For CMC2: Verify the CMC2 bootrom is 8.0(1) Note: Use GGSN command show card to determine the active and standby CMC 2 slot number
show card show card slot=<active CMC2 slot number> mode=detail show card slot=<standby CMC2 slot number> mode=detail
For CMC3: Verify the CMC3 bootrom is 2.2(1)

show card show card slot=<active CMC3 slot number> mode=detail show card slot=<standby CMC3 slot number> mode=detail
9. Verify the SSM bootrom is updated properly. Use the following command to check the bootrom version on SSMs:
show card slot=<SSC Slot> mode=detail
Verify if ROM Revision on all SSMs are equal to 6.0(1) or later for SSC2 SSM and 1.5.1 for SSC3 SSM. All SSMs on all SSCs must have the same version of bootrom. 10. Patch Verification for G501_FF01435785ACT_INF: Cabcharge L2TP Authentication Feature
411-5221-309
Standard
06.30 March 10, 2010
543
If Checkpoint 1 item 10, page 93 was executed, execute a set of test cases to verify the functionality works after GGSN 6.0 upgrade. 11. Patch Verification for G501_01450778ACT_IFMGR: Increase the MTU Size of Gn IP Interface on GELC feature. If Checkpoint 1 item 11, page 94 Log in to the GGSN and issue the command:
show isp show interface isp=<Gn ISP> <- Repeat the above command for all interfaces
12. Patch Verification for G501_FF01567650ACT_IPCMC: TCP MSS Clamping feature If Checkpoint 1 item 12, page 95 was executed, execute a set of test cases to verify the functionality works after GGSN 6.0 upgrade. 13. Patch Verification for G501_FF01385577ACT_ERCMC: DCCv2 Envelope Reporting Feature If Checkpoint 1 item 13, page 95 was executed, execute a set of test cases to verify the functionality works after GGSN 6.0 upgrade. 14. Patch Verification for G501_FF01368038ACT_INF: DCCv2 Customization Essentials Feature If Checkpoint 1 item 14, page 96 was executed, execute a set of test cases to verify the functionality works after GGSN 6.0 upgrade. 15. Patch Verification for G501_FF01385579ACT_DCCCMC, G501_FF01385579ACT_DCCSSP: Parking Meter Charging Enhancement Feature If Checkpoint 1 item 15, page 97 was executed, execute a set of test cases to verify the functionality works after GGSN 6.0 upgrade. 16. Patch Verification for G501_FF01510131ACT_CPM: Consecutive Parking Meter Feature If Checkpoint 1 item 16, page 98 was executed, execute a set of test cases to verify the functionality works after GGSN 6.0 upgrade. 17. Patch Verification for G501_FF01369144ACT_PPDCMC: Dual Coupon Feature If Checkpoint 1 item 17, page 99 was executed, execute a set of test cases to verify the functionality works after GGSN 6.0 upgrade. 18. Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration If Checkpoint 1 item 18, page 99 was executed: Login to the GGSN as admin user. Execute the command show ntp
544
Verify the ntp server IP address is set to x.y.z.255
19. Patch Verification for G501_01407739ACT_INF and G501_01595094AACT_AAA. If Checkpoint 1 item 19, page 100 was executed, execute a set of test cases to verify the functionality works after GGSN 6.0 upgrade. 20. RADIUS Security Service Policy (firewall) verification on all connection ISP. If Checkpoint 1 item 20, page 101 was executed, execute a set of test cases related to RADIUS messaging within a VPN to verify the functionality works after GGSN 6.0 upgrade.
411-5221-309
Standard
06.30 March 10, 2010
545
38
New feature provisioning/activation Refer to Nortel GGSN Provisioning Procedures, 411-5221-927 for provisioning new features introduced in the GGSN 6.0 release. See Appendix A: GGSN SOC on page 577 for the new feature activation via SOC control. GGSN Hardware Upgrade Optionally, SSC2 to SSC3, CMC2 to CMC3 and/or SFC-1 to SFC-2 hardware upgrade can now proceed after software upgrade. Refer to Nortel GGSN Hardware Installation and Maintenance Guide, 411-5221-923 for more information about the SSC2 to SSC3, CMC2 to CMC3 and SFC-1 to SFC-2 hardware upgrade. GGSN 4.1.1/GGSN 5.0.1 Patch Removal After GGSN software upgrade and not going to roll back to the previous release, the GGSNS4.1.1 and GGSNS5.0.1 patches can be removed from the active combo patch profile. 1. Login SCS GUI using Device Owner privilege and select the Patch icon on the left image panel. 2. From the Patch Manager screen, select current active patch profile under Profile tab and click the Edit button. 3. Select GGSN 4.1.1 as the patchable load and find the patch to be removed. Click the Delete button to remove the patch rule. Select Yes to continue. Repeat the step by selecting GGSN 5.0.1 as the patchable load. After the deletion, the active patch profile will only consist of GGSN 6.0 patches 4. Click on OK button to exit the patch profile configuration. 5. Go to Device icon and select the device being upgraded. Select the Diagnostics & Maintenance and check the session log under Session Log tab to see if the patch rule has been successfully deleted.
Health Check Monitoring After GGSN software upgrade, verify the Health Check Monitor parameters to the same as set prior to the upgrade. Refer to Step 14 of Steps before GGSN upgrade to determine the output captured prior to the GGSN upgrade. a. Login to the GGSN and issue the command show healthcheck. Verify the parameters set prior to the upgrade match.
show healthcheck
GPRS/UMTS
Upgrade Manual
GGSN6.0
546
b. If the parameters do not match, proceed to the next step to add a new HCM Profile. i. Login SCS GUI using Device Owner privilege, click on the Access Properties icon in the left pane. Select the HCM profiles icon on the middle pane. ii. From the HCM Profiles screen, click the "Add" button, input HCM profile name, (e.g. hcmpro60), set the Monitoring status (HCM Enabled Checkbox), Network Success Rate Threshold Value and the Nodal Success Rate Threshold Value as per the settings in GGSN 4.1.1 or GGSN 5.0.1 and then click "OK" button. iii. Double click relevant device icon in "Device Manager" screen. iv. In "<Device Name> Configuration" dialog, choose "Access Properties" Tab, then click "Select" button right of "HCM Profile" field. v. Choose HCM profile name(e.g. hcmpro50) in the list, then click "OK" button.
411-5221-309
Standard
06.30 March 10, 2010
547

Software rollback procedure
39
If it becomes necessary to roll the GGSN on 6.0 with SSC3 cards back to the GGSN 4.1.1, make sure the SSC3 cards are replaced with SSC2 cards, prior to the rollback to GGSN 4.1.1. Please refer to Hardware Installation and Maintenance Guide NTP 411-5221-923 for the procedure to downgrade SSC3 to SSC2. Note: This procedure assumes that a combo patch profile is active on the GGSN. The combo patch profile will have patches for the current GGSN load as well as the previous GGSN load from which the GGSN was upgraded from. Note: It is recommended the user have the GGSN Release Notes handy for the software version GGSN will be downgraded to. 1. Go to Device Manager on SCS GUI, under the Configuration Management tag, to make sure the Enable SSH Server box is unselected. This is to prevent sshd CLI commands from being executed and causing warning message during system resync. 2. Set the GGSN to deny new incoming traffic. This should be done before actual upgrade is performed. In order to minimize the impact to subscribers who are trying to activate PDP sessions, the following steps should be implemented to redirect traffic away from the GGSN that is being upgraded. a. Login Gn ISP through SCS Client. b. Select Access Properties -> Tunnels -> GTP c. Select the GTP tunnel and click Edit. d. Select the device under "Device Specific Settings" and click Edit to modify the device specific setting. e. Check the box for "Disallow PDP Context Creation" on GTP Tunnel Device Configuration window. f. Select "No Resources Available" for "Redirect Response Cause" on the same window, GTP Tunnel Device Configuration window. g. Click "OK" at the bottom of the "GTP Tunnel Device Configuration" menu h. Click "OK" at the bottom of the "GTP Tunnel Configuration" menu.
GPRS/UMTS
Upgrade Manual
GGSN6.0
548
3. Verify the GGSN has the combo patch profile applied. Login to SCS client as device_owner user From Patch Manager, click Device tab Make a note of the patch profile applied to the GGSN Click on Profile tab Select the patch profile and click Edit Click on Patchable Load drop down list and select the GGSN load the GGSN will be downgraded to. The GGSN Release Notes may come in handy if the user is unaware of the patches available for the GGSN load. Verify the GGSN patches rules for the appropriate software version are added in the patch profile.
4. Patch Instructions: For GGSN downgrade to GGSN 4.1.1: Ensure the patch G411_01303739EMG_ISPMGR has been added as a patch rule in the combo patch profile. For GGSN downgraded to GGSN 5.0.1: If Checkpoint 1 item 18, page 99 Patch Verification for G501_01505119ACT_SNTP: SNTP Client Configuration on page 99 was execute, then: Login to the SCS client as device_owner user. From Device Manager, double click on the GGSN. On the Device tab, modify the Server IP Address under SNTP Client Configuration so that the last octet of the IP address is 0 (similar to x.y.z.0):
5. Determine all the Gi ISPs configured. Login to each Gi ISP from the SCS Client. Uncheck the allow tunnel termination box on the Gi interface if it was unchecked before the upgrade. 6. Use set bootorder command to change the bootorder to select the previous software image. Make sure the location of boot file3 (f3) and boot file4 (f4) are set to the following:
CMC2 (f3): /disk/image/isn/cmc CMC3 (f3): /disk/image/isn/cmc3 CMC2 (f4): /flash/image/isn/cmc CMC3 (f4): /flash/image/isn/cmc3
411-5221-309
Standard
06.30 March 10, 2010
549
Note: Prior to setting boot file4 (f4) below issue command dir /flash/image/isn to confirm that the isn image is present on the flash. If the isn image is not present do not set boot file4 (f4). Same applies to boot file3 (f3). 7. Use the next step to set GGSN software to GGSN 6.0. For GGSN with CMC2, change bootorder on GGSN to select the version of GGSN software you want to rollback. Step to set bootorder for CMC3 is captured after the below example. Here is an example of the set bootorder command on CMC2:
ssg-18(SSU)# set bootorder '.' = clear field; flags (f) '-' = go to previous field; ^D = quit
boot file1 (f1) : /disk/image/G411_9/cmc <- At the prompt, type the location where GGSN load for the previous version to rollback In this example, the ggsn is rolled back to GGSN 4.1.1: /disk/image/GGSN411/cmc. Remember to add a CMC at the end of the boot directory boot file2 (f2) : /disk/image/GGSN60/cmc <- Type the current GGSN boot directory (GGSN 6.0) boot file3 (f3) : /flash/image/GGSN501/cmc <- Type /disk/image/isn/cmc boot file4 (f4) : <- Type /flash/image/isn/cmc boot server address (h): <- if you have a TFTP server with a valid GGSN image, set the server IP here configuration (s) : <- Make sure this field is left blank or indicates primary. If this field is set to any other value, will cause resync failure diag mode (dm) : 0x0 <-If set to 0x1, set to 0x0
core dump mode (cm) : 0x1 <- To enable core dump flag, set to 0x1. Otherwise, set it to 0x0
GPRS/UMTS
Upgrade Manual
GGSN6.0
550
Note: GGSN provisioning procedures, 411-9221-927 has the recommended configuration in the set bootorder CLI For GGSN with CMC3 card, change bootorder on GGSN to select the software image you want to rollback.
Use set bootorder command to change the bootorder. Here is an example set bootorder on CMC3
ssg-141(SSU)# set bootorder '-' = go to previous field; ^D = quit
'.' = clear field; flags (f)
boot file1 (f1) : /disk/image/G411_0/cmc3 <- At the prompt, type the location where GGSN load for the previous version to rollback In this example, GGSN is rolled back to GGSN 4.1.1: /disk/image/GGSN411/cmc3. Remember to add a CMC3 at the end of the boot directory boot file2 (f2) : /disk/image/WK636_14/cmc3 <-Type current GGSN boot directory boot file3 (f3) : /disk/image/G411_9/cmc3 <-Hit enter to select default boot file4 (f4) : /disk/image/isn/cmc3 <-Make sure to set it to /disk/image/isn/cmc3 boot server address (h): 47.104.6.14 <-if you have a TFTP server with a valid GGSN image, set the server IP here configuration (s) : <- Make sure this field is left blank or indicates primary. If this field is set to any other value, will cause resync failure diag mode (dm) : 0x0 <-If set to 0x1, set to 0x0 core dump mode (cm) : 0x1 <-To enable core dump flag, set to 0x1. Otherwise, set it to 0x0
411-5221-309
Standard
06.30 March 10, 2010
551
8. Resync the GGSN to complete the rollback from SCS 6.0 client. Click on the Devices level Right mouse click on the GGSN Device and click on Diagnostics and Maintenance Click on Resync with iSOS Ver button. This will bring the drop down list box, select the previous release to roll back. This will open a confirm window, please read the content of the window and click on Yes to rollback and resync the GGSN.
Note: There may be some CLI warning messages displayed on the console due to new CLI commands added in GGSN 6.0 and cannot be recognized in GGSN 4.1.1 or GGSN 5.0.1. Those CLI warning messages can be ignored and have no service impact. 9. Patch related instructions: i. Execute the following command to verify GGSN patches are applied.
show patchmgr history APPLIED
ii. The above command must list applied patches. If the command returns a list of applied patches, proceed to Step vii iii. If patches are not listed, execute the following steps. Telnet to the GGSN and issue the command:
monitor log
iv. Log in to the SCS client as device_owner user. Navigate to Patch Manager-> Device tab. v. Verify the GGSN has the combo patch profile associated with it. If a patch profile is not associated, the appropriate combo patch profile created prior to the GGSN upgrade must be associated. To associate the combo patch profile to the GGSN, click on the GGSN, then click Edit. Select the appropriate patch profile to be associated to the rolled back GGSN, click OK. Monitor the GGSN telnet terminal. The terminal logs will indicate patches are getting applied to the GGSN. Here is an example:
13-Apr-2009 15:22:16 13/1/2:patchmgr,0: 5, 1, INFO, Applied patchid G501_01939135_GTP.
GPRS/UMTS
Upgrade Manual
GGSN6.0
552
vi. If a patch profile is associated with the GGSN, and GGSN command show patchmgr history APPLIED did not return the list of applied patches: Then double click the GGSN. This will open the Patch Device Information window. Click the Sync States button. If there was a synchronization issue between the GGSN and SCS, patches will get applied. Monitor the GGSN telnet terminal. The terminal logs will indicate patches are getting applied to the GGSN. Here is an example:
13-Apr-2009 15:22:16 13/1/2:patchmgr,0: 5, 1, INFO, Applied patchid G501_01978420_SVC.
Note: If the patches are already applied, the GGSN event logs will return the following message (users can ignore this message):
09-Apr-2009 14:28:27 13/1/1:patchmgr,0: 11, 1, INFO, Attempted to apply patch G501_01320881ACT_CTP, but it was already applied.
vii. For GGSN downgrade from GGSN 6.0 to GGSN 4.1.1: Login to the SCS client as device_owner, click on Patch Manager, Patch tab Select and double click the patch G411_01303739EMG_ISPMGR to review patch application instructions in the .pd file. Follow the patch application instructions for GGSN 4.1.1 patch G411_01303739EMG_ISPMGR. The patch application instructions are detailed under Field Application Instructions in the patch .pd file that is packaged with this patch.
viii.For GGSN downgraded from GGSN 6.0 to GGSN 5.0.1: Make sure patch G501_01223788ACT_P2ROUTING has been added to the active patch profile and activated. 10. Perform this step if it was not performed as part of the previous step. Run the CLI command set quickstart taking all the current values by pressing Enter after each prompt. 11. Occasionally after Rollback to GGSN 4.1.1, a problem may manifest where the GGSN auxiliary Ethernet Management Port does not recover correctly. See Appendix B: Recovery Procedure on page 581 check for this condition and, if it exists, how to recover from it. Return to this procedure after recovery. 12. Set the GGSN to allow new incoming traffic if it was denied earlier.
411-5221-309 Standard 06.30 March 10, 2010
553
a. Login Gn ISP through SCS Client. b. Select Access Properties -> Tunnels -> GTP. c. Select the GTP tunnel and click Edit. d. Select the device under Device Specific Settings and click Edit to modify the device specific setting. e. Un-check the box for Disallow PDP Context Creation on GTP Tunnel Device Configuration window. f. Click OK at the bottom of the GTP Tunnel Device Configuration menu. g. Click OK at the bottom of the GTP Tunnel Configuration menu. h. Login to the GGSN to verify the GTP tunnel setting change. Make sure the Disallow PDP Context Creation is set to FALSE.
# show tunnel <- make a note of the Tunnel and ISP name with the Type column as gtp
# show tunnel <GTP tunnel name> <Gn ISP name>
13. Perform Step 4 in GGSN Pre-Upgrade Procedure on page 495 to ensure system integrity after rollback. 14. After the GGSN Rollback, rollback SCS Server and Client. Refer to: Rollback SCS 6.0 to SCS 4.1.2 on same server on page 165 or GGSNS6.0 to GGSNS5.0.1 on Same Server Roll-back on page 168 Note: There is no rollback procedure for the bootrom. The bootrom is compatible with all releases of GGSN software.
GPRS/UMTS
Upgrade Manual
GGSN6.0
554
40
The following checkpoint (summarized in Table 30 below) is recommended to be executed by the operation personnel after GGSN upgrade. This checkpoint should be carried out on a daily basis over the course of 7 days following GGSN upgrade. Contact Nortel support team in case any of the check points fail.
System Monitoring checkpoint GGSN upgrade follow-up
40
All items in Table 30 below should be executed to monitor the system stability and performance after the upgrade. Successful completion of this checkpoint doesnt mean there is absolutely no problem in the system. However, it can reflect the system status at that particular instance of time and identify any areas of concern that may impact the stability of GGSN system.
Table 30 System Monitoring checkpoint Item 1 Description Check if there is any alarms raised from the GGSN. Work Instruction Checkpoint 7 item 1, page 555 Checkpoint 7 item 2, page 555 Checkpoint 7 item 3, page 557 Checkpoint 7 item 4, page 558 Checkpoint 7 item 5, page 563 Checkpoint 7 item 6, page 565 Checkpoint 7 item 7, page 566 X
Check the general stability of software load and physical device at system level. Check the stability of communication to external network.
Check stability and performance for PDP context handling over the Gn interface. Check stability and performance for GTP billing over the Ga interface if GTP Accounting is enabled. Check stability and performance for subscriber authentication and accounting over the RADIUS interface if RADIUS Authentication or RADIUS Accounting is enabled. Check stability and performance for DHCP address allocation over the DHCP interface if it is applicable.
sheet 1 of 2
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Table 30 System Monitoring checkpoint (continued) Item 8 Description
555
Work Instruction Checkpoint 7 item 8, page 567 Checkpoint 7 item 9, page 568
Check stability and performance for Prepaid service over the CTP interface if it is applicable. Check stability and performance for Prepaid service over the DCC interface if it is applicable.
sheet 2 of 2
Checklist work instructions and details These sub-sections are referenced in Table 30. They provide details for item checklists that require it. System Monitoring checkpoint 7
Checkpoint 7 item 1- Check GGSN alarms
1. Log into PWI to retrieve GGSN alarms information if PWI is available. 2. Log into SCS client. 3. Click on alarms icon to see if there is any new alarms raised from the GGSN. Pay special attention to the alarms Switch CMC Initiated Internally, SSM Failed, SSM Reset, etc. Please refer to Nortel GGSN Alarms Reference Manual, 411-5221-921 for alarm information and remedial actions. Return to System Monitoring checkpoint on page 554
Checkpoint 7 item 2- Check general stability at system level
1. Log into GGSN console. 2. Type show uptime CLI command. Check the amount of time GGSN has been active and the cause of CMC restart. The CMC restart may be caused by CMC switch-over or SCS resync command.
shasta-20(SSU)# show uptime Up 5 mins, 57 secs CMC active 5 mins, 57 secs System restarted by CLI reload
GPRS/UMTS
Upgrade Manual
GGSN6.0
556
3. Type show card CLI command. Make sure that all cards are Enabled and their corresponding ports are UP, or the status matches the GGSN pre-check conditions. If the status does not match, contact your next level of support. 4. If there are two CMC cards, make sure they are redundant. If not, contact your next level of support.
ggsn-139(SSU)# show card
Tue 25-Mar-2008 11:03:38 CDT SSM/CT3/COC3 CPU states: A - auto-reset; N - need catchup; C - catching up; D - in delete U - up; X - failed; '-' - disabled; * - not present M - failover move in progress; v - uncommunicative; d - dumping core; L - loading T - temporarily down ~ - spared overflow pool; ^ - spared failover pool 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 ---1 2 3 4 5 6 7 8 10 11 12 13 14 Configured/Found ----------------------SSC /SSC SSC /SSC SSC /SSC SSC /SSC ALC /ALC ELC /ELC SFC /SFC SFC /SFC ELC /ELC SSC /SSC SSC /SSC CMC /CMC CMC /CMC Enabled -------Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Enabled Info ----U U U U U U - U U U U U U U U U U U U U [ICP Rev. 1.7] D U U U U U U U 10G Active [FPGA Rev. 2.0] 10G Standby [FPGA Rev. 2.0] U U U U U U U U U U U U U U U U Active Standby (Redundant)
5. Type show load CLI command. Check the GGSN load running on the active CMC. Make sure that most of the CPU is used by IDLE and the free cluster pools in Cluster Pool Table should not remain at 0.
shasta-20(SSU)# show load
PROCESSOR UTILIZATION SUMMARY: CMC CPUs busy since boot: Non Encryption SSPs busy since boot: Encryption SSPs busy since boot: CPU STATS (SLOT: 14 PORT: 1 CPU: 1) Total ticks : 70942 Ticks this period: 70942 TYPE -------IDLE KERNEL INTERRUPT total % (ticks) ---------------90% ( 64439) 0% ( 112) 0% ( 110) delta % (ticks) --------------90% ( 64439) 0% ( 112) 0% ( 110) 5% Delta: 30% Delta: 37% Delta: 5% 30% 37%
VXWORKS SYSTEM HEAP SUMMARY: status bytes blocks avg block max block %util ------ ---------- -------- ---------- ---------- ----current free 51493216 13 3961016 36623680 32.9% alloc 105182016 8354 12590 - 67.1% ----- ---------- -------- ---------- ---------- ----total 156675232 8367 cumulative alloc 154237920 12690 12154 CMC PROCESSOR HEAP SIZES: Current HEAP size (CPU 1) : 151 MB Current HEAP size (CPU 2) : 151 MB Reserved memory available to both CPU 1 & CPU 2: 1536 MB
411-5221-309
Standard
06.30 March 10, 2010

NETWORK MBUF STATS: Number of mbufs configured: 20000 Number of mbufs free : 19995 NETWORK CLUSTER BLOCK STATS: Number of cluster blocks configured: 18000 Number of cluster blocks free : 17995
557
NETWORK CLUSTER BUFFER STATS: __________________ CLUSTER POOL TABLE _______________________________________________________________________________ size clusters free usage ------------------------------------------------------------------------------64 4000 3996 6737 128 1000 1000 123122 256 1000 999 2014 512 1000 1000 23993 1024 1000 1000 570 2048 10000 8976 176416
6. Type show task CLI command. Make sure there is no task running on CMC processor 0 in SUSPEND state.
shasta-20(SSU)# show task
NAME ---------dogmgr tExcMon tExcTask almgr tmrsvc usermgr concli auxcli taskmgr tTaskMon redunmgr redmgr cardint heapmgr commgr lommgr disk_cap tNetTask dhcpRelay tftpd ..... ENTRY -----------dog_catcher excMonTask excTask almTask TimerTask user_main cli_loop __cli_aux __taskmgr_ch taskmon_run redun_task redmgr_task cardIntTask sn_heap_main comTask lomTask 4974024 netTask dhcpr_main tftpdTask TID PRI STATUS PC SP ERRNO DELAY -------- --- ---------- -------- -------- ------- ----7f6fbd0 0 DELAY 5116f34 7f6df20 0 10 7f6c8c0 0 PEND+T 50c3120 7f67ec8 3d0004 35 7f61d70 0 PEND 5123c80 7f5fe08 3d0001 0 7bd2db30 1 PEND+T 50c3120 7bd2bc80 3d0004 19 7ae8ba0 4 DELAY 5116f34 7ae3e58 0 1 7ec20a80 5 PEND+T 50c3120 7ec1bc98 3d0004 122 7abd7710 5 PEND+T 50c3120 7abbd238 3d0004 40 7ab3e400 5 PEND+T 50c3120 7aafd118 3d0004 185 7f145c0 16 DELAY 5116f34 7f0fd98 0 37 79c6910 16 PEND+T 50c3120 79c3ca0 110001 197 7f14f400 16 DELAY 5116f34 7f13fb68 3d0002 12 7f0a4500 16 PEND+T 50c3120 7f09fc88 3d0004 359 7ef38860 20 PEND 50c3120 7eeffed8 0 0 7ef32e0 40 DELAY 5116f34 7eefdd8 0 313 7eab0f30 45 PEND+T 50c3120 7ea9fc70 3d0004 22949 7ea63210 45 PEND+T 50c3120 7ea5fc68 0 35751 7bce7250 45 DELAY 5116f34 7bcdfea0 0 22258 7fb15230 50 PEND 50c3120 7fb0fe68 110001 0 7cd085c0 55 PEND+T 50c3120 7ccff5c8 3d0004 317 7bc9c340 55 PEND 50c3120 7bc8fa78 0 0
7. Check the tasks running on CMC processor 1 and make sure there is no task in SUSPEND state. Assume the active CMC card is on slot 13.
shasta-20(SSU)# show task node=p12/1/2
NAME ENTRY ---------- -----------tExcMon excMonTask tExcTask excTask tLogTask logTask tShell shell tTelnetd be_telnetd dataStreamCstartTask__1 tNetTask netTask mdbTask mdb_task TID PRI STATUS PC SP ERRNO DELAY -------- --- ---------- -------- -------- ------- ----13cb4218 0 PEND+T 116f41c 13cb4170 3d0004 71 13ca3c68 0 PEND 11761ec 13ca3b98 0 0 13c94158 0 PEND 11761ec 13c934a8 0 0 12b36970 1 PEND 116f41c 12b36600 d0003 0 12b56de0 2 PEND 116f41c 12b56c80 0 0 12b47878 47 PEND+T 116f41c 12b477b0 0 15870 12b6c9e0 50 READY 11738dc 12b6c8d8 110001 0 12b19fa8 50 READY 1127234 12b19f68 0 0
Checkpoint 7 item 3- Check the stability of external communication
1. Log into GGSN console. 2. Type show isp CLI command. Make sure that all ISPs are in Up status or they match the GGSN pre-check conditions. If not, contact your next level of support.
558
GGSN Upgrade Follow-up shasta-20(SSU)# show isp

ISP --ssg-20-isp-gi ssg-20-isp-gi2 ssg-20-isp-gn default Active Subs ----------0 0 0 0
Trunk Conns ----------1 1 2 1
Status -----Up Up Up Up
3. Type show conn CLI command. Make sure that all connections are in Up status or they match the GGSN pre-check conditions. If not, contact your next level of support.
shasta-20(SSU)# show conn
Connection ---------shasta-20-9-1-1 shasta-20-10-3-1 shasta-20-10-1-1 shasta-20-6-1-1 mgmt-eth0 Type ---trunk trunk trunk trunk trunk L2 Type ------ETHERNET ETHERNET ETHERNET ETHERNET ETHERNET Slot/Port/VPI/VCI ----------------9/1 10/3 10/1 6/1 14/5 Status -----Up Up Up Up Up
4. Type show interface CLI command. Make sure all interfaces are in Up status or they match the GGSN pre-check conditions. If not, contact your next level of support.
shasta-20(SSU)# show interface
Name mgmt-eth0(1) lo1(1) gn-4(3) gn-1(3) gi-3(4) gi(5) IP Address/Mask 47.104.4.166/22 127.0.0.1/8 10.129.52.21/23 10.129.46.21/23 10.129.68.22/23 10.129.84.21/23 Type mgmt mgmt trunk trunk trunk trunk Connection Ethernet Loopback Ethernet Ethernet Ethernet Ethernet Status Up Up Up Up Up Up
Return to System Monitoring checkpoint on page 554
Checkpoint 7 item 4- Check the stability and performance of Gn interface
1. Log into the GGSN console. 2. Type show tunnel to find out the name of Gn ISP. Gn ISP can be identified of tunnel type GTP.
shasta-20(SSU)# show tunnel Tunnel ISP -------gtp-tunnel ssg-20-isp-gn test-l2tp.11 ssg-20-isp-gi test-l2tp ssg-20-isp-gi Type ---gtp l2tp lns l2tp local Status -----n/a n/a local
411-5221-309
Standard
06.30 March 10, 2010
559
3. Type show stats hist sm isp=<Gn ISP> CLI command periodically (e.g. once every 10 seconds) and compare the outcome to previous captures. Make sure that the successfully established session counters are properly pegged and the session failure counters (marked as bold in the console display) dont get increased abnormally. Refer to GGSN Nodal Activation Success Rate Metric in Nortel GGSN Monitoring Guide, 4115221-924 for acceptable rate. Contact your next level of support if the activation success rate is not acceptable.
shasta-20(SSU)# show stats hist sm isp=ssg-20-isp-gn
SESSION MANAGEMENT HISTORICAL STATS for ISP <ssg-20-isp-gn>
1329 SM.ReportingInterval 0 SM.AttActPdpCtxt 0 SM.DupAttActPdpCtxt 0 SM.NbrActPdpCtxt 0 SM.MaxNbrActPdpCtxt 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SM.AttActPdpCtxt.Bgrd.Low SM.AttActPdpCtxt.Intact.Low SM.AttActPdpCtxt.Strm.Low SM.AttActPdpCtxt.Conv.Low SM.AttActPdpCtxt.Bgrd.Medium SM.AttActPdpCtxt.Intact.Medium SM.AttActPdpCtxt.Strm.Medium SM.AttActPdpCtxt.Conv.Medium SM.AttActPdpCtxt.Bgrd.High SM.AttActPdpCtxt.Intact.High SM.AttActPdpCtxt.Strm.High SM.AttActPdpCtxt.Conv.High SM.SuccActPdpCtxt.Bgrd.Low SM.SuccActPdpCtxt.Intact.Low SM.SuccActPdpCtxt.Strm.Low SM.SuccActPdpCtxt.Conv.Low SM.SuccActPdpCtxt.Bgrd.Medium SM.SuccActPdpCtxt.Intact.Medium SM.SuccActPdpCtxt.Strm.Medium SM.SuccActPdpCtxt.Conv.Medium SM.SuccActPdpCtxt.Bgrd.High SM.SuccActPdpCtxt.Intact.High SM.SuccActPdpCtxt.Strm.High SM.SuccActPdpCtxt.Conv.High
0 SM.FailActPdpCtxt.NORA 0 SM.FailActPdpCtxt.NORA.Admin 0 SM.FailActPdpCtxt.NORA.AllDynamicAddressesOccupied 0 SM.FailActPdpCtxt.NORA.Overload 0 SM.FailActPdpCtxt.NORA.NoMemory 0 SM.FailActPdpCtxt.NORA.UDPThresholdReject 0 SM.FailActPdpCtxt.NORA.Other 0 SM.FailActPdpCtxt.ADAO 0 SM.FailActPdpCtxt.NOMA 0 SM.FailActPdpCtxt.MAPN 0 SM.FailActPdpCtxt.UPAT 0 SM.FailActPdpCtxt.UAUF 0 SM.FailActPdpCtxt.UAUF.External 0 SM.FailActPdpCtxt.UAUF.Internal 0 SM.FailActPdpCtxt.UAUF.Other 0 SM.FailActPdpCtxt.SYSF 0 SM.FailActPdpCtxt.SYSF.Admin 0 SM.FailActPdpCtxt.SYSF.Other 0 SM.FailActPdpCtxt.SEME 0 SM.FailActPdpCtxt.IEIN 0 SM.FailActPdpCtxt.IMFT 0 SM.FailActPdpCtxt.OVLD 0 SM.FailActPdpCtxt.SVNS 0 SM.FailActPdpCtxt.SVNS.MissingAPN 0 SM.FailActPdpCtxt.SVNS.UnknownPdpAddressType 0 SM.FailActPdpCtxt.SVNS.Admin 0 SM.FailActPdpCtxt.SVNS.Other 0 SM.FailActPdpCtxt.NoResp 0 SM.FailActPdpCtxt.NoResp.Admin 0 SM.FailActPdpCtxt.NoResp.SGSNChange 0 SM.FailActPdpCtxt.NoResp.Duplicate
GPRS/UMTS
Upgrade Manual
GGSN6.0
560

0 SM.FailActPdpCtxt.NoResp.FallBackFallForward 0 SM.FailActPdpCtxt.NoResp.Other 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SM.AttSsmrPdpCtxt SM.SuccSsmrPdpCtxt SM.AttDeactPdpCtxtMsAndSgsn SM.AttDeactPdpCtxtGgsn SM.AttDeactPdpCtxtGgsn.Ssmr SM.SuccDeactPdpCtxtGgsn.Ssmr SM.SuccActBamCtxt SM.NbrActBamCtxt SM.SuccActIpsecCtxt SM.NbrActIpsecCtxt SM.SuccActL2ipCtxt SM.NbrActL2ipCtxt SM.SuccActL2tpCtxt SM.NbrActL2tpCtxt
0 SM.SuccActRoamerCtxt 0 SM.NbrActRoamerCtxt 0 SM.NbrBadGTPHeader 0 SM.NbrBadGTPPktSize 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SM.AttDeactPdpCtxtGgsn.Manual SM.SuccDeactPdpCtxtGgsn.Manual SM.AttDeactPdpCtxtGgsn.ITO SM.SuccDeactPdpCtxtGgsn.ITO SM.AttDeactPdpCtxtGgsn.MaxDur SM.SuccDeactPdpCtxtGgsn.MaxDur SM.AttDeactPdpCtxtGgsn.SgsnRstrt SM.SuccDeactPdpCtxtGgsn.SgsnRstrt SM.AttDeactPdpCtxtGgsn.Ssmr.NoResource SM.SuccDeactPdpCtxtGgsn.Ssmr.NoResource SM.AttDeactPdpCtxtGgsn.Ssmr.NoSecondMove SM.SuccDeactPdpCtxtGgsn.Ssmr.NoSecondMove SM.AttDeactPdpCtxtGgsn.Ssmr.SystemFailure SM.SuccDeactPdpCtxtGgsn.Ssmr.SystemFailure SM.AttDeactPdpCtxtGgsn.Ssmr.Disabled SM.SuccDeactPdpCtxtGgsn.Ssmr.Disabled SM.AttActAggrCtxt SM.SuccActAggrCtxt SM.NbrActAggrCtxt SM.NbrConfigMism SM.AttActAggrPPP
0 SM.SuccActGreCtxt 0 SM.NbrActGreCtxt 0 SM.NbrActPrepaidCtxt 0 0 0 0 0 0 0 0 0 0 0 0 0 SM.MaxNbrActBamCtxt SM.MaxNbrActIpsecCtxt SM.MaxNbrActL2tpCtxt SM.MaxNbrActL2ipCtxt SM.MaxNbrActGreCtxt SM.MaxNbrActPrepaidCtxt SM.MaxNbrAggrActCtxt SM.MaxNbrSvcActCtxt SM.AttActSecPdpCtxt SM.SuccActSecPdpCtxt SM.NbrActSecPdpCtxt SM.NbrActMsSecInUse SM.MaxNbrActMsSecInUse
0 SM.SuccActMPLSCtxt 0 SM.NbrActMPLSCtxt 0 SM.MaxNbrActMPLSCtxt 0 SM.SuccActCbbCtxt 0 SM.NbrActCbbCtx 0 SM.MaxNbrActCbbCtxt 0 SM.GTPDropPktUDPQueueOvfl 0 0 0 0 0 SM.spare1 SM.spare2 SM.spare3 SM.spare4 SM.spare5
Compare output with data captured with Checkpoint 1 item 2, page 83
411-5221-309
Standard
06.30 March 10, 2010
561
Data to be pulled daily (if this was collected during pre-checks). 4. Type show apn to find out the name of APN for the health checking. 5. Type show stats hist apn isp=<Connection ISP> apn=<APN name> CLI command periodically and compare the outcome to previous captures. Make sure that the successfully established session counters are properly pegged and the APN failure counters (marked as bold in the console display) dont get increased abnormally. Refer to GGSN Nodal Deactivation Success Rate Metric in Nortel GGSN Monitoring Guide, 411-5221-924 for acceptable rate. Contact your next level of support if the deactivation success rate is not acceptable.
shasta-51(SSU)# show stats hist apn isp=ssg-51-isp-gi apn=sat-apn
APN HISTORICAL STATS for ISP <ssg-51-isp-gi> & APN <sat-apn> 100 0 0 0 0 0 0 0 0 0 0 0 0 SM.ReportingInterval.Apn SM.NbrActPdpCtxt.Apn.Bgrd.Low SM.NbrActPdpCtxt.Apn.Intact.Low SM.NbrActPdpCtxt.Apn.Strm.Low SM.NbrActPdpCtxt.Apn.Conv.Low SM.NbrActPdpCtxt.Apn.Bgrd.Medium SM.NbrActPdpCtxt.Apn.Intact.Medium SM.NbrActPdpCtxt.Apn.Strm.Medium SM.NbrActPdpCtxt.Apn.Conv.Medium SM.NbrActPdpCtxt.Apn.Bgrd.High SM.NbrActPdpCtxt.Apn.Intact.High SM.NbrActPdpCtxt.Apn.Strm.High SM.NbrActPdpCtxt.Apn.Conv.High
0 SM.AttActPdpCtxt.Apn 0 SM.SuccActPdpCtxt.Apn 0 SM.AttDynActPdpCtxt.Apn 0 SM.SuccDynActPdpCtxt.Apn 0 0 0 0 0 0 0 SM.AttActPdpCtxtAutReq.Apn SM.FailActPdpCtxtAutReq.Apn SM.FailActPdpCtxtAuthReq.Radius.Apn SM.FailActPdpCtxtAuthReq.SCP.Apn SM.FailActPdpCtxtAuthReq.Diameter.Apn SM.AttSsmrPdpCtxt.Apn SM.SuccSsmrPdpCtxt.Apn
0 SM.AttDeactPdpCtxtMsAndSgsn.Apn 0 SM.SuccDeactPdpCtxtMsAndSgsn.Apn 0 0 0 0 0 0 0 0 0 0 0 0 SM.AttDeactPdpCtxtGgsn.Apn SM.SuccDeactPdpCtxtGgsn.Apn SM.AttDeactPdpCtxtGgsn.Ssmr.Apn SM.SuccDeactPdpCtxtGgsn.Ssmr.Apn SM.MaxNbrActPdpCtxt.Apn SM.AttUpdPdpCtxtMsAndSgsn.Apn SM.SuccUpdPdpCtxtMsAndSgsn.Apn SM.AttUpdPdpCtxtGgsn.Apn SM.SuccUpdPdpCtxtGgsn.Apn SM.FailActPdpCtxtApnDown.Apn SM.NbrDynActPdpCtxt.Apn SM.NbrStaticActPdpCtxt.Apn
0 SM.FailActPdpCtxtNoIPfound.Apn 0 0 0 0 0 0 0 0 0 SM.AttDeactPdpCtxtGgsn.Manual.Apn SM.SuccDeactPdpCtxtGgsn.Manual.Apn SM.AttDeactPdpCtxtGgsn.ITO.Apn SM.SuccDeactPdpCtxtGgsn.ITO.Apn SM.AttDeactPdpCtxtGgsn.MaxDur.Apn SM.SuccDeactPdpCtxtGgsn.MaxDur.Apn SM.AttDeactPdpCtxtGgsn.SgsnRstrt.Apn SM.SuccDeactPdpCtxtGgsn.SgsnRstrt.Apn SM.AttDeactPdpCtxtGgsn.Ssmr.NoResource.Apn
GPRS/UMTS
Upgrade Manual
GGSN6.0
562

0 0 0 0 0 0 0 0

SM.SuccDeactPdpCtxtGgsn.Ssmr.NoResource.Apn SM.AttDeactPdpCtxtGgsn.Ssmr.NoSecondMove.Apn SM.SuccDeactPdpCtxtGgsn.Ssmr.NoSecondMove.Apn SM.AttDeactPdpCtxtGgsn.Ssmr.SystemFailure.Apn SM.SuccDeactPdpCtxtGgsn.Ssmr.SystemFailure.Apn SM.AttDeactPdpCtxtGgsn.Ssmr.Disabled.Apn SM.SuccDeactPdpCtxtGgsn.Ssmr.Disabled.Apn SM.PdpCtxtAclRej.Apn
0 SM.NbrActCtxtPrepaid.Apn 0 0 0 0 0 SM.SuccActBamCtxt.Apn SM.SuccActIpsecCtxt.Apn SM.SuccActGreCtxt.Apn SM.SuccActL2tpCtxt.Apn SM.SuccActL2ipCtxt.Apn
0 SM.AttActSecPdpCtxt.Apn 0 SM.SuccActSecPdpCtxt.Apn 0 SM.FailActSecPdpCtxt.NoDataPlaneRsrc.Apn 0 SM.IMSIRuleMatchSucc.Apn 0 SM.IMSIRuleMatchFail.Apn 0 SM.IMSITotRuleComparisons.Apn 0 SM.SuccActMPLSCtxt.Apn 0 SM.SuccActCbbCtxt.Apn 0 SM.NbrActCbbCtxt.Apn 0 SM.MaxNbrActCbbCtxt.Apn 0 0 0 0 SM.SuccActCtxtPcscfDiscReq.Apn SM.SuccActCtxtPcscfDiscFailed.Apn SM.NbrActPcscfDiscCtxt.Apn SM.MaxNbrActPcscfDiscCtxt.Apn
0 SM.NbrBlacklist.Apn 0 SM.FailActPdpCtxtApnBlacklist.Apn 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SM.FailActPdpCtxt.NORA.Apn SM.FailActPdpCtxt.ADAO.Apn SM.FailActPdpCtxt.UAUF.Apn SM.FailActPdpCtxt.SYSF.Apn SM.FailActPdpCtxt.SEME.Apn SM.FailActPdpCtxt.IEIN.Apn SM.FailActPdpCtxt.IMFT.Apn SM.FailActPdpCtxt.SVNS.Apn SM.FailActPdpCtxt.NoResp.Apn SM.NbrDeactPdpCtxtCCFH.Apn SM.NbrCtxtPrepaidToNonPrepaid.CCFH.Apn SM.NbrCtxtPrepaidToNonPrepaid.CCNotApp.Apn SM.NbrDeactPdpCtxtDCCServer.Apn SM.spare1.Apn SM.spare2.Apn SM.spare3.Apn SM.spare4.Apn SM.spare5.Apn
Compare output with data captured with Checkpoint 1 item 2, page 83 Data to be pulled daily (if this was collected during pre-checks). 6. Type show stats hist gtpdata isp=<Gn ISP> CLI command periodically and compare the outcome to previous captures. Make sure that the GTP data transfer counters are properly pegged.
shasta-51(SSU)# show stats hist gtpdata isp=ssg-51-isp-gn
GTP DATA HISTORICAL STATS for ISP <ssg-51-isp-gn> 217 GTP.ReportingInterval 0 GTP.DiscDataPkt 0 0 0 0 GTP.IncDataPkt.Bgrd.Low GTP.IncDataPkt.Intact.Low GTP.IncDataPkt.Strm.Low GTP.IncDataPkt.Conv.Low
411-5221-309
Standard
06.30 March 10, 2010

0 0 0 0 0 60 0 0 0 0 0 0 0 0 0 0 0 44 0 0 0 0 0 0 0 0 0 0 0 3600 0 0 0 0 0 0 0 0 0 0 0 2640 0 0

GTP.IncDataPkt.Bgrd.Medium GTP.IncDataPkt.Intact.Medium GTP.IncDataPkt.Strm.Medium GTP.IncDataPkt.Conv.Medium GTP.IncDataPkt.Bgrd.High GTP.IncDataPkt.Intact.High GTP.IncDataPkt.Strm.High GTP.IncDataPkt.Conv.High GTP.OutDataPkt.Bgrd.Low GTP.OutDataPkt.Intact.Low GTP.OutDataPkt.Strm.Low GTP.OutDataPkt.Conv.Low GTP.OutDataPkt.Bgrd.Medium GTP.OutDataPkt.Intact.Medium GTP.OutDataPkt.Strm.Medium GTP.OutDataPkt.Conv.Medium GTP.OutDataPkt.Bgrd.High GTP.OutDataPkt.Intact.High GTP.OutDataPkt.Strm.High GTP.OutDataPkt.Conv.High GTP.IncDataOct.Bgrd.Low GTP.IncDataOct.Intact.Low GTP.IncDataOct.Strm.Low GTP.IncDataOct.Conv.Low GTP.IncDataOct.Bgrd.Medium GTP.IncDataOct.Intact.Medium GTP.IncDataOct.Strm.Medium GTP.IncDataOct.Conv.Medium GTP.IncDataOct.Bgrd.High GTP.IncDataOct.Intact.High GTP.IncDataOct.Strm.High GTP.IncDataOct.Conv.High GTP.OutDataOct.Bgrd.Low GTP.OutDataOct.Intact.Low GTP.OutDataOct.Strm.Low GTP.OutDataOct.Conv.Low GTP.OutDataOct.Bgrd.Medium GTP.OutDataOct.Intact.Medium GTP.OutDataOct.Strm.Medium GTP.OutDataOct.Conv.Medium GTP.OutDataOct.Bgrd.High GTP.OutDataOct.Intact.High GTP.OutDataOct.Strm.High GTP.OutDataOct.Conv.High
563
0 GTP.IncErrIndMsg 0 GTP.OutErrIndMsg 0 0 0 0 0 GTP.spare1 GTP.spare2 GTP.spare3 GTP.spare4 GTP.spare5
Compare output with data captured with Checkpoint 1 item 2, page 83 Data to be pulled daily (if this was collected during pre-checks). Refer to Nortel GGSN Monitoring Guide, 411-5221-924 for more detailed performance analysis information if necessary. Return to System Monitoring checkpoint on page 554
Checkpoint 7 item 5- Check the stability and performance of Ga interface
1. Log into GGSN console. 2. Type show isp to find out the name of ISPs.
GPRS/UMTS
Upgrade Manual
GGSN6.0
564
3. Type show gtpp_profile isp=<ISP> CLI command. Ga ISP is configured with CGF Profile and a GTP Profile. 4. Make sure that the Object State is not DISK_ALL_EMERGENCY which means G-CDR is written to the disk due to CGF unavailability. The CGF State in one of the CGFs should be IDLE or RUNNING. CGF state NOT_RESPONDING means the CGF is not properly connected.
shasta-19(SSU)# show gtpbill isp=ssg-19-isp-ga
GTP Accounting Object Spy ========================= RAM Buffer: State: Max Size: Currently: OK to send CDRs from disk: Ext Blks on Reg Unproc Lst: Ext Blks on Hot Unproc Lst: Ext Blk Proc Bunch Size: TOS: ISP: True - On 1500 ext blocks 0 ext blocks in buffer False 0 0 0 0x00
Name: ssg-19-isp-ga ISP ID: 5 IP Addr: 10.128.8.28 Object State: DISK_ALL_EMERGENCY RAM CDR Max File size: 1048576 bytes RAM CDR File Timeout: 1800 seconds Next Pkt Seq Num: 53877 Next Charge ID Num: 106800001 Next Local Rec Seq Num: 53400179 Stored Pkt Seq Num 53874 CDR Encoding Scheme: ASN.1 BER CDR Record Encoding Version: V3.2 CBB Mgmt Ext Version: 2 Include IMEISV Extension: No Include RAT Type Extension: No Include PLMN ID Extension: No Include Location Info: No Include HSDPA Extension: No Bulk Update In Prog: No Closed Unsent CDR files: 712AAAAA.13U POS_DUP_PKTs in Q: 0 Mtc Msg Q: 0 Messages CGF ID: 0 CGF State: IDLE CGF IP Addr: 47.104.4.216 CGF UDP Port: 3386 Pkt Ack Timeout: 7 seconds Max Number Rexmits: 3 Periodic Echo Timeout: 300 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 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: Disabled 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 : 615 secs
411-5221-309
Standard
06.30 March 10, 2010
565
5. Type show stats hist gtpp isp=<Ga ISP> CLI command periodically and compare the outcome to previous captures. Make sure that the GTP data transfer counters are properly pegged and the failure GTP counters (marked as bold in the console display) dont get increased abnormally. Refer to GGSN GTP' Accounting Transfer Success Rate Metric in Nortel GGSN Monitoring Guide, 411-5221-924 for acceptable rate. Contact your next level of support if the GTP accounting transfer success rate is not acceptable.
shasta-19(SSU)# show stats hist gtpp isp=ssg-19-isp-ga
GTPP HISTORICAL STATS for ISP <ssg-19-isp-ga> 909 0 0 0 0 0 0 0 GTPP.ReportingInterval GTPP.CdrTransfReq.CDRC GTPP.CdrTransfReq.AREL GTPP.CdrTransfReq.DVLM GTPP.CdrTransfReq.MCCC GTPP.CdrTransfReq.MGTI GTPP.CdrTransfReq.TLEX GTPP.CdrTransfReq.SCHG
0 GTPP.SuccCdrTransf 0 GTPP.FailCdrTransf.FQAF 0 0 0 0 0 0 0 0 0 0 3 1 0 0 0 0 0 0 GTPP.FailCdrTransf.INMF GTPP.FailCdrTransf.MIEI GTPP.FailCdrTransf.MIEM GTPP.FailCdrTransf.NRAV GTPP.FailCdrTransf.OIEI GTPP.FailCdrTransf.RQNF GTPP.FailCdrTransf.SVNS GTPP.FailCdrTransf.SYSF GTPP.FailCdrTransf.VNSU GTPP.RedirRequestRecvd GTPP.NbrGTPPTimeouts GTPP.NbrGTPPNoResp GTPP.NbrProtErrors GTPP.spare1 GTPP.spare2 GTPP.spare3 GTPP.spare4 GTPP.spare5
Compare output with data captured with Checkpoint 1 item 2, page 83 Data to be pulled daily (if this was collected during pre-checks). Return to System Monitoring checkpoint on page 554
Checkpoint 7 item 6- Check the stability and performance of RADIUS interface
1. Log into GGSN console. 2. Type show isp and show radius CLIs to find out the name of Connection ISP configured with RADIUS profiles. 3. Type show radius isp=<Connection ispname> to check the RADIUS Profile configuration and find out the IP address of RADIUS Server.
GPRS/UMTS
Upgrade Manual
GGSN6.0
566
4. Type show stats hist radius CLI command periodically and compare the outcome to previous captures. Make sure that the failure RADIUS counters (marked as bold in the console display) dont get increased abnormally. Refer to GGSN RADIUS Accounting Transfer Success Rate Metric in Nortel GGSN Monitoring Guide (NTP 411-5221-924) for acceptable rate. Contact your next level of support if the RADIUS accounting transfer success rate is not acceptable. 5. In addition, make sure that the RADIUS request/response counters are properly pegged.
shasta-19(SSU)# show stats hist radius isp=ssg-19-isp-gi server=47.104.4.144
Radius Accounting Server 47.104.4.144 statistics 2130 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 RAD.ReportingInterval RAD.AcctTransfReq RAD.AcctRetrans RAD.AcctResponseRcvd RAD.AcctAvgRTT RAD.AcctPendingRequests RAD.AcctMaxPendingRequests RAD.AcctTimeOuts RAD.AcctMalformedResponses RAD.AcctBadAuthenticators RAD.AcctUnknownTypes RAD.AcctPacketsDropped RAD.AuthAccessRequests RAD.AuthAccessRetransmissions RAD.AuthAccessAccepts RAD.AuthAccessRejects RAD.AuthAvgRTT RAD.AuthPendingRequests RAD.AuthMaxPendingRequests RAD.AuthTimeouts RAD.AuthMalformedAccessResponses RAD.AuthBadAuthenticators RAD.AuthUnknownTypes RAD.AuthPacketsDropped RAD.spare1 RAD.spare2 RAD.spare3 RAD.spare4 RAD.spare5
Compare output with data captured with Checkpoint 1 item 2, page 87 Data to be pulled daily (if this was collected during pre-checks). Refer to Nortel GGSN Monitoring Guide, 411-5221-924 for more detailed performance analysis information if necessary. Return to System Monitoring checkpoint on page 554
Checkpoint 7 item 7- Check the stability and performance of DHCP interface
1. Log into GGSN console.
411-5221-309
Standard
06.30 March 10, 2010
567
2. Type show isp and show dhcp CLIs to find out the name of Connection ISP configured with DHCP profiles. 3. Type show dhcp isp=<Connection ispname> to check the DHCP Profile configuration and find out the IP address of DHCP Server. 4. Type show stats hist CLI command periodically and compare the outcome to previous captures. Make sure that the failure DHCP counters (marked as bold in the console display) dont get increased abnormally. Additionally make sure the DHCP request/response counters are properly pegged.
shasta-19(SSU)# show stats hist dhcp isp=ssg-19-isp-gi server=47.104.60.34
DHCP Server <47.104.60.34> ISP <ssg-19-isp-gi> statistics 2466 0 0 0 0 0 0 0 0 0 0 0 0 0 0 DHCP.ReportingInterval DHCP.DiscoverSent DHCP.RequestSent DHCP.DeclineSent DHCP.ReleaseSent DHCP.OfferReceived DHCP.AckReceived DHCP.NakReceived DHCP.SendErrors DHCP.PktsDropped DHCP.spare1 DHCP.spare2 DHCP.spare3 DHCP.spare4 DHCP.spare5
Checkpoint 7 item 8- Check the stability and performance of CTP interface
1. Log into GGSN console. 2. Type show isp and show tariff CLIs to find out the name of Connection ISP configured with Tariff profiles. 3. Type show tariff isp=<Connection ispname> to check the Tariff Profile configuration and find out the IP address of Prepaid Server. 4. Type show stats hist scp CLI command periodically and compare the outcome to previous captures. Make sure that the failure SCP counters (marked as bold in the console display) dont get increased abnormally. Refer to Prepaid Success Rate Metric in Nortel GGSN Monitoring Guide, 411-5221-924 for acceptable rate. Contact your next level of support if the prepaid success rate is not acceptable. 5. Additionally make sure the CTP authorization/response counters are properly pegged.
shasta-51(SSU)# show stats hist scp isp=ssg-51-isp-gi server=47.103.64.67
SCP hist statistics for ISP: ssg-51-isp-gi Server: 47.103.64.67
GPRS/UMTS
Upgrade Manual
GGSN6.0
568

2899 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 SCP.ReportingInterval SCP.AttAuthReq SCP.SuccAuthReq SCP.AttReauthReq SCP.SuccReauthReq SCP.AttFinalReport SCP.SuccFinalReport SCP.ProtErr SCP.NoResp SCP.DeniedReq SCP.ReturnCoupon.IdleTimeOut SCP.ReturnCoupon.LifetimeExpiry SCP.NoCouponNoCBB SCP.AttRedirectionReq SCP.ReauthCommandsRcvd SCP.spare1 SCP.spare2 SCP.spare3 SCP.spare4 SCP.spare5
Checkpoint 7 item 9- Check the stability and performance of DCC interface
1. Log into GGSN console. 2. Type show diameter CLI to find out the name of Connection ISP and Diameter Profile. 3. Type show diameter profilename=<profilename> isp=<Connection ispname> to check the Diameter Profile configuration and find out the IP address of DCC Server. 4. Type show stats hist dcc CLI command periodically and compare the outcome to previous captures. Make sure that the failure DCC counters (marked as bold in the console display) dont get increased abnormally. Refer to Diameter Credit Control Success Rate Metric in Nortel GGSN Monitoring Guide, NTP 411-5221-924 for acceptable rate. Contact your next level of support if the diameter credit control success rate is not acceptable. 5. In addition, make sure the DCC request/answer counters are properly pegged.
shasta-51(SSU)# show stats hist dcc isp=ssg-51-isp-gi dcc_profile=dcc-san server=47.104.5.157
DCC hist statistics for ISP: ssg-51-isp-gi Profile dcc-san Server: 47.104.5.1 2041 DCC.ReportingInterval 0 DCC.AttInitialCcr 0 DCC.SuccInitialCca 0 DCC.AttUpdateCcr 0 DCC.SuccUpdateCca 0 DCC.AttTerminationCcr 0 DCC.SuccTerminationCca
411-5221-309
Standard
06.30 March 10, 2010

0 DCC.RedirectCcaRcvd 0 DCC.RarMsgsRcvd 0 DCC.AttNewRateReqs 0 DCC.SuccNewRateReqs 0 DCC.AttReauthReqs 0 DCC.SuccReauthReqs 0 DCC.QuotaRet.IdleTimeout 0 DCC.ReqTimerExpiry 0 DCC.ProtocolErrs 0 DCC.DeniedReq.Authentication 0 DCC.DeniedReq.Authorization 0 0 0 0 0 0 0 0 0 0 0 0 0 0 DCC.TermReason.Normal DCC.TermReason.BadAns DCC.TermReason.Admin DCC.TermReason.LinkBroken DCC.TermReason.SessionTimeout DCC.FailureHandling.NbrTerminated DCC.FailureHandling.NbrContinue DCC.InvalidChargingRuleBaseRcvd DCC.InvalidChargingRuleRcvd DCC.spare1 DCC.spare2 DCC.spare3 DCC.spare4 DCC.spare5
569
Compare output with data captured with Checkpoint 1 item 2, page 87 Data to be pulled daily (if this was collected during pre-checks).
GPRS/UMTS
Upgrade Manual
GGSN6.0
570
411-5221-309
Standard
06.30 March 10, 2010
571

This section explains:
41
GGSN management operations required when changing SCS server IP A change in the SCS IP address in GGSN quickstart is required when moving the SCS to a new server with a different IP address or when the current SCS server IP address is modified to a new IP address. When this address is changed, the GGSN quickstart must be modified and GGSN must be rebooted. During this time the GGSN is unable to handle traffic. GGSN upgrade functionality Resync with iSOS Ver. functionality for the GGSN is similar to the resync command except that the SCS builds the configuration for a different version. It can be used in both upgrade and roll back scenarios. Change the GGSNs SCS IP address When the IP address of the SCS is changed or the SCS is moved to a server with a different IP address, each GGSN must be reconfigured to accept the new SCS IP address before it can be managed. Note: In order for the change to take effect, a service-affecting reboot of the GGSN is required. To minimize traffic loss, follow the procedures in section Manual GGSN shutdown, resync, or CMC switchover in Nortel GGSN Hardware Installation and Maintenance Gude: 411-5221-923 prior to the GGSN reboot or resync. Setting quickstart is performed on the GGSNs CLI. Login to the GGSN with SSU privileges and modify quickstart parameter 1st SCS IP address : the new SCS server IP. Note: Hit Enter key to select the default value for other parameters. After setting the new IP in parameter 1st SCS IP address :, hit Enter key for all other options till you get the GGSN CLI prompt.
# set quickstart . . . >1st SCS IP address: <enter IP address of SCS server>
GPRS/UMTS
Upgrade Manual
GGSN6.0
572
After quickstart is modified, perform a GGSN reboot from the GGSN CLI.
# reboot
Resync with iSOS Ver. The Resync with iSOS Ver. functionality is used like a resync to force the GGSNs provisioning data to match the SCS. To compare, the default Resync functionality rebuilds the data for the existing version of GGSN software, whereas the Resync with iSOS Ver. can rebuild the data to match the needs of any supported load. For example, the following pictures shows the appearance of the command:
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Figure 8 Resync with iSOS functionality
573
Right click on one of the devices and the above menu will appear. Click on the Diagnostics and Maintenance. The following menu will appear.
GPRS/UMTS
Upgrade Manual
GGSN6.0
574
Figure 9 Device Maintenance window
Click on the Device Maintenance tab. Then Click on the Resync with iSOS Ver button. A drop down list box will appear. Select the appropriate iSOS Version and Click OK. The list of loads names indicates the supported versions. The load version must appear in the Resync with iSOS Ver. functionality. If it does not appear, the SCS may require an upgrade as well. This will open a confirm window. Read the content of the window and click Yes, to upgrade and Resync the device.
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Figure 10 Resync confirmation window
575
Although the functionality is named Resync with iSOS Ver., it can be used to roll back loads as well as upgrade loads on the GGSN. The load must be manually copied to the GGSN and the bootorder set appropriately (see GGSN Procedures Reference Manual, 411-5221-927 for more details) before the Resync with iSOS Ver. is executed.
GPRS/UMTS
Upgrade Manual
GGSN6.0
576
411-5221-309
Standard
06.30 March 10, 2010
577

Software Optionality Control (SOC)
42
42
The GGSN Software Optionality Control (SOC) supports license key enabled software feature(s). It allows customers to buy features which are activated on the product via supplied license keys entered via the Service Creation System (SCS) GUI. This feature provides optional feature control to prevent unauthorized use of the functionality offered. It also provides a mechanism to manage exclusivity that may be required for some custom development items. SOC Feature Activation An off-line PC based tool is used by Nortel Networks to generate license keys. Nortel Networks is responsible for generating, managing and shipping keys to the customer. Once the keys are available, customer should activate the features using the keys. The procedure for activating the features is described here. The SOC feature configuration is associated to license key management and activation. It provides a user interface (SCS GUI) for license key management (Add & Display keys) and inventory of all optional features currently available for provisioning. The GUI provides a mechanism to add new license keys. Keys can be added by SCS users belonging to default ISP with device owner privileges. Entered license keys are validated by SCS based on feature name and IP address of the SCS server. Other SCS users (with device owner privileges) can only display the inventory of features. The following GUI screen allow users to enter a license key to have control over the optional feature. Once the valid license key is entered, the corresponding operational feature is added to the table and displayed with "Disabled" status. 1. Logon to the SCS Client as device owner
GPRS/UMTS
578
2. Click on the File menu, and then click on SCS Configuration from the list 3. This will open the SCS configuration window. Click on the SOC Activation tab. Click on Add. The following window will appear.
4. Enter the License key for the feature to be activated as shown in the above picture. 5. Click on OK, after entering the Key 6. Once the right key is entered, the following window appears with the details of the feature, and the default state of the feature is disabled after the key is configured.
411-5221-309
Standard
06.30 March 10, 2010
579
7. Double click on the Feature name shown in the above picture to activate it. This will open a window as shown in the picture below.
GPRS/UMTS
580
8. Select Enable to enable the feature from Activation Status drop down list box. All the features that are required for the customer will have to be activated before proceeding with the other steps in the upgrade.
411-5221-309
Standard
06.30 March 10, 2010
581
43
You may be directed to this appendix after performing a rollback to a version prior to GGSN 6.0, or after performing an upgrade to GGSN 6.0. The reason is a potential problem which may occur after an upgrade or rollback. The procedure provided in this section helps you to identify whether this problem has manifested, and if so, how to recover from it. After a switch sfc, switch cmc or Resync command execution, it is possible that the qs1 ispdb.cfg may become corrupted and the auxiliary Ethernet management will not recover correctly. The quickstart configuration provides to the GGSN the configuration information required to establish communications with the management systems during the re-sync operation. Up to three auxiliary Ethernet management ports can be configured using the set quickstart command. The following example shows a configuration with two auxiliary Ethernet management ports.
Management ethernet IP address: 11.222.33.44/23 Standby CMC management ethernet IP address: 11.222.55.66/23 SCS 1: SCS IP Address: 11.222.77.88 Route via management interface: mgmt-eth0 SCS 2: SCS IP Address: Route via management interface: SCS 3: SCS IP Address: Route via management interface: Auxilliary ATM management interface 1: Configuration: Management interface local address: Management interface remote address: Auxilliary ATM management interface 2: Configuration: Management interface local address: Management interface remote address: Auxilliary ATM management interface 3: Configuration: Management interface local address: Management interface remote address: Auxilliary ethernet management interface 1: Configuration: 6/4/0/0/ether Management interface local address: 111.222.333.44/28 Auxilliary ethernet management interface 2: Configuration: 6/1/0/0/ether Management interface local address: 111.222.333.55/28 Auxilliary ethernet management interface 3: Configuration: Management interface local address: Default router: 11.222.33.1 Packet Core Upgrade Manual GPRS 6.0 / UMTS 4.0 (GGSNS4.1) Default route via: mgmt-eth0
GPRS/UMTS
582
The commands show conn and show interface can be used to verify that the mgmt-eth1 and mgmt-eth2 are up.
ssg-76(SSU)# show conn Connection Type L2 Type Slot/Port/VPI/VCI Status ---------- ---- ------- ----------------- -----ssg-76-isp-gelc-gn trunk ETHERNET 5/1 Up ssg-76-isp-gn-conn trunk ETHERNET 6/1 Up ssg-76-3-1-1 trunk ETHERNET 6/4 Up ssg-76-isp-gi-conn trunk ETHERNET 6/2 Up ssg-76-6-4-1 trunk ETHERNET 6/4 Up mgmt-eth0 trunk ETHERNET 14/5 Up mgmt-eth1 trunk ETHERNET 6/4 Up mgmt-eth2 trunk ETHERNET 6/1 Up ssg-76(SSU)# show interface Name IP Address/Mask Type Connection Status mgmt-eth0(1) 11.222.33.44/23 mgmt Ethernet Up lo1(1) 127.0.0.1/8 mgmt Loopback Up mgmt-eth2(1) 111.222.333.55/28 mgmt Ethernet Up mgmt-eth1(1) 111.222.333.44/28 mgmt Ethernet Up ssg-76-isp-gi-ti(4) 11.222.33.170/27 trunk Ethernet Up ssg-76-isp-gn-ti(5) 11.222.33.147/27 trunk Ethernet Up
After issuing switch sfc or switch cmc commands, or resync, GGSN upgrade, or GGSN rollback, the mgmt-eth1 and mgmt-eth2 might not recover correctly. show config qs1 db=ispdb might also reveal that some entries are missing. The following example shows mgmt-eth1 and mgmt-eth2 in the incorrect state. Also, there is a possibility of the default ISP being down. This can be verified with the show isp command on the GGSN.
ssg-76(SSU)# show isp ISP Active Subs ------------ssg-76-isp-gn 0 ssg-76-isp-gi 1 ssg-76-isp-ga 0 default 0 ssg-76(SSU)# Trunk Conns ----------2 3 1 0 Status -----Up Up Up Down
ssg-76(SSU)# show interface Name IP Address/Mask Type Connection Status mgmt-eth0(1) 11.222.33.44/23 mgmt Ethernet Up lo 1(1) 127.0.0. 1/8 mgmt Loopback Up mgmt-eth2(1) 111.222.333.55/28 mgmt Ethernet Down mgmt-eth1(1) 111.222.333.44/28 mgmt Ethernet Down ssg-76-isp-gi-ti(4) 11.222.33.170/27 trunk Ethernet Up ssg-76-isp-gn-ti(5) 11.222.33.147/27 trunk Ethernet Up ssg-76(SSU)# show conn Connection Type L2 Type Slot/Port/VPI/VCI Status ---------- ---- ------- ----------------- -----ssg-76-isp-gelc-gn trunk ETHERNET 5/1 Up ssg-76-isp-gn-conn trunk ETHERNET 6/1 Up ssg-76-3-1-1 trunk ETHERNET 6/4 Up ssg-76-isp-gi-conn trunk ETHERNET 6/2 Up ssg-76-6-4-1 trunk ETHERNET 6/4 Up 411-5221-309 Preliminary 02.20 July 2005 mgmt-eth2 trunk ETHERNET 6/1 CfgErr mgmt-eth1 trunk ETHERNET 6/4 CfgErr mgmt-eth0 trunk ETHERNET 14/5 Up ssg-76(SSU)#
411-5221-309
Standard
06.30 March 10, 2010
583
Fault recovery 28 43 The following set of recommendations provide details on the recovery of the GGSN when the Auxiliary Ethernet Management ports do not recover automatically. Backup the qs1 ispdb.cfg file It is recommended to make a copy of the qs1 ispdb.cfg while the GGSN is under a normal operating state: 1. Verify the file /disk/config/qs1/ispdb.cfg has the correct information:
#show file /disk/config/qs1/ispdb.cfg
2. Verify ispdb.cfg includes the following lines related to the mgmt-eth1 and mgmt-eth2 configuration. Any customer not using OSPF on the mgmteth1 and mgmt-eth2 port should ignore the OSPF configuration staring from create ospf isp=default.
set acctg mgmt profile device_stats=0 ip_stats=0 svc_stats=0 trunk_stats=0 mem_s tats=0 ovld_stats=0 add ipsec idletime isp=default idletime=0 add conn type=mgmt conn=mgmt-eth2 isp=default slot=6 port=1 encap=ether set conn type=mgmt conn=mgmt-eth2 isp=default l2type=ether commit conn type=mgmt conn=mgmt-eth2 isp=default encap=ether set conn type=mgmt conn=mgmt-eth1 isp=default l2type=ether commit conn type=mgmt conn=mgmt-eth1 isp=default add conn type=mgmt conn=mgmt-eth0 isp=default slot=13 port=5 encap=ether set conn type=mgmt conn=mgmt-eth0 isp=default l2type=ether commit conn type=mgmt conn=mgmt-eth0 isp=default add ip interface interface=mgmt-eth2 isp=default loc_addr=111.222.333.55/28 encap=ether type=ether spm_ifid=0 acctg=enable add ip interface interface=mgmt-eth1 isp=default loc_addr=111.222.333.44/28 encap=ether type=ether spm_ifid=0 acctg=enable add ip interface interface=mgmt-eth0 isp=default loc_addr=11.222.33.44/23 encap=ether type=ether spm_ifid=0 acctg=enable bind conn conn=mgmt-eth2 interface=mgmt-eth2 isp=default bind conn conn=mgmt-eth1 interface=mgmt-eth1 isp=default bind conn conn=mgmt-eth0 interface=mgmt-eth0 isp=default create ospf isp=default add ospf rtrid isp=default id=11.222.333.44 add ospf area isp=default area=0.0.0.22 type=normal nssa_redistribute=yes GPRS/UMTS Upgrade Manual GGSN6.0
584
report_isp_ipaddr=yes add ospf interface isp=default area=0.0.0.22 interface=mgmt-eth1 dr_priority=0 type=bcast add ospf interface isp=default area=0.0.0.22 interface=mgmt-eth2 dr_priority=0 type=bcast set global_attrib isp=default dedication=off tell_rt=on
3. Make a back up copy of the ispdb.cfg

#copy file /disk/config/qs1/ispdb.cfg /disk/config/qs1/ ispdb.bak
Recovery of management ports with backup-up ispdb.cfg file If a copy of backup ispdb.cfg is available. The following steps should be followed to recover after switch sfc. 1. Login using mgmt-eth0. 2. Restore the backed up ispdb.cfg file:
#copy file from=/disk/config/qs1/ispdb.bak to=/disk/config/ qs1/ispdb.cfg
3. Resync or reboot GGSN
Recovery of management ports without a backup-up ispdb.cfg file If the backup ispdb.cfg is not available. The following steps should be used for recovery. 1. Resync or reboot GGSN 2. Issue the command show config qs1 db=ispdb and identify which of the following command lines is missing.
ggsn# show config qs1 db=ispdb
add conn type=mgmt conn=mgmt-eth2 isp=default slot=6 port=1 encap=ether set conn type=mgmt conn=mgmt-eth2 isp=default l2type=ether commit conn type=mgmt conn=mgmt-eth2 isp=default add conn type=mgmt conn=mgmt-eth1 isp=default slot=6 port=4 encap=ether set conn type=mgmt conn=mgmt-eth1 isp=default l2type=ether commit conn type=mgmt conn=mgmt-eth1 isp=default add ip interface interface=mgmt-eth2 isp=default loc_addr=111.222.333.55/28 encap=ether type=ether spm_ifid=0 acctg=enable add ip interface interface=mgmt-eth1 isp=default loc_addr=111.222.333.44/28 encap=ether type=ether spm_ifid=0 acctg=enable bind conn conn=mgmt-eth2 interface=mgmt-eth2 isp=default
411-5221-309
Standard
06.30 March 10, 2010
585
bind conn conn=mgmt-eth1 interface=mgmt-eth1 isp=default add ospf interface isp=default area=0.0.0.22 interface=mgmt-eth1 dr_priority=0 type=bcast add ospf interface isp=default area=0.0.0.22 interface=mgmt-eth2 dr_priority=0 type=bcast
Note: The add ip interface and encap=ether should be entered as a single line. IP address used here are only or demonstration. Please replace with correct address. Note: Customers not using OSPF on the mgmt-eth1 and mgmt-eth2 port should ignore the add ospf interface command. 1. Manually enter the missing commands in the correct order. 2. Save the configuration
#save config qs1 db=ispdb
3. Make a backup copy of qs1 ispdb.cfg

#copy file /disk/config/qs1/ispdb.cfg /disk/config/qs1/ ispdb.bak
GPRS/UMTS
586
44
The mirrors of all the mounted file systems (critical and non-critical file systems) must be unmirrored before upgrading Solaris 8 to Solaris 9. Caution: Every step in this procedure must be carefully read and executed. An incorrect entry may cause the server reboot to fail. Use the following procedure to unmirror the critical file systems, including root(/), /usr, /opt and /var, swap and /export/home. Please refer to the tables Disk Mirroring Mapping for Critical File Systems on page 70 and Disk Mirroring Mapping for Non-critical File Systems on page 70 to find out the available partitions. The following tables are example Disk Mirroring Mapping for both mounted and non-critical file systems.
Table 31 Example disk mirror map for critical file system Mounted file system Metadevice name of the mirror d0 d5 d8 First submirror / disk partition (Partition for Solaris 8) d10/ c1t0d0s0 d15/ c1t0d0s5 d18/ c1t1d0s7 Second sub-mirror / disk partition (Partition for Solaris 9) d20/ c1t2d0s0 d25/ c1t2d0s5 d28/ c1t3d0s7
/ /var /opt
Table 32 Example disk mirror map for non-critical file system Non-critical file system /export/home swap Metadevice name of the mirror d7 d1 First submirror / disk partition d17/ c1t0d0s7 d11/ c1t0d0s1 Second sub-mirror / disk partition d27/ c1t2d0s7 d21/ c1t2d0s1
Pre-requisite: Check to ensure the file systems are ok. Perform Appendix J: Disk Check for SCS for mirrored server on page 664 before proceeding to un-mirror the server. Here is an overview of the steps required for disk un-mirroring: 1. Make sure that you have root privilege.
411-5221-309
Standard
06.30 March 10, 2010
587
2. Verify that all submirrors are in the "Okay" state. If the mirrors are not in the Okay state, the metaslices need to be corrected. Make a note of the mirror names, submirrors and partitions. # metastat 3. Run df -k to determine the mirrors and mount points. Verify the information with the Disk Mirroring Mapping above. 4. Run the metadetach command on all mirror that contains a file system to make a one-way mirror. 5. For all file systems except / (root): change the file system entry in the /etc/ vfstab file to use a non-Solaris Volume Manager device (slice). 6. For root (/) only: run the metaroot command. 7. Reboot the system. 8. Run the metaclear command to clear the mirror and submirrors. 9. Re-format the recovered partitions using newfs 10. Verify the hard disks are clean by checking fsck on all mounted partitions The following steps are an example of how to unmirror the server (using the information from Disk Mirroring Mapping for Critical File Systems on page 70 and Disk Mirroring Mapping for Non-critical File Systems on page 70. Step 1. Run metastat and df -k. Make sure the Disk Mirroring Mapping table information is correct. Unmirrored server partition convention. The physical partition size of mirrors are usually of equal size. To find if the sub-mirrors are of equal size: To verify all disk partitions for the mirrored disks are same block size go to Step 5 on 604. From the metastat output: d1<n> - Represents Sub-mirror 1 (example: d10): In Disk Mirroring Mapping for Critical File Systems on page 70 for Critical File System, the column First sub-mirror / disk partition -- Partition for Solaris 8 identifies d1<n>, where 1<n> represents Submirror 1. In Disk Mirroring Mapping for Non-critical File Systems on page 70 for Non-critical file systems, the column First sub-mirror / disk partition identifies d1<n>.
588
Use the physical partition assigned to d1<n> for Solaris 8. /etc/vfstab will be modified with the physical partition assigned to d1<n>. d2<n> - Represents Sub-mirror 2 (example: d20): Use Sub-mirror 2 during the metadetach procedure. Physical partitions assigned to submirror 2 are reformatted using newfs.
Step 2: Un-mirroring procedure - detaching Sub-mirror 2 Unmirror / : Root file system

# metadetach d0 d20 d0: submirror d20 is detached # metaroot /dev/dsk/c1t0d0s0
metaroot automatically adds /dev/dsk/c1t0d0s0 as the root partition in / etc/vfstab. All the other partitions needs to be updated manually. Physical partition in /etc/vfstab updated for / : /dev/dsk/c1t0d0s0
Important Step to determine server boot path:
Make a note of the server boot path. This is needed to make changes to Solaris boot environment during the reboot of the server after disk unmirroring. Here is a brief explanation and the steps: Use ls -al command on the partition that is being assigned for / file system. This path is needed as the server will look for the kernel executable in / during server reboot. To determine the server root device: Run ls -al for the physical partition assigned for / partition. In the below example, /dev/dsk/c1t0d0s0 is set for / and added to /etc/ vfstab.
411-5221-309
Standard
06.30 March 10, 2010
589
Make a note of this string, this is called solaris8_root for reference. This will be needed during reboot of the server after unmirroring all the partitions. solaris8_root - /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w500000e010188041,0:a
Unmirror swap:
# metadetach d1 d21 d1: submirror d21 is detached
Physical partition in /etc/vfstab updated for swap : /dev/dsk/c1t0d0s1 Next, run the following pre-check for Solaris dump partition. Here is an explanation. A partition is assigned by the system to dump memory in case of crash. Usually the same partition is set as 'swap' and dump partition. During mirroring, 1 of 2 partitions can be assigned as the dump device which may not match the swap partition. Here is an example: dump device is set to c1t0d0s1, swap is set as c1t8d0s1 Run dumpadm # dumpadm Dump content: kernel pages Dump device: /dev/dsk/c1t0d0s1 (dedicated)
590
Savecore directory: /var/crash/urc2y3pa Savecore enabled: yes Run swap -l # swap -l swapfile dev swaplo blocks free 16 16393520 16393520
/dev/dsk/c1t8d0s1 118,81
If there is a mismatch in the dump partition and swap partition, then run the following steps: 1. Check swap partition: # swap -l
2. Check dump device partition: # dumpadm
3. If swap partition does not match the dump partition, modify the dump partition: # dumpadm -d <swap partition> Example: # dumpadm -d /dev/dsk/c1t8d0s1 <-- swap partition
Unmirror /var:
411-5221-309
Standard
06.30 March 10, 2010
591
Physical partition in /etc/vfstab updated for /var : /dev/dsk/c1t0d0s5 Unmirror /export/home:

Physical partition in /etc/vfstab updated for /export/home : /dev/dsk/ c1t0d0s7 Unmirror /opt:
Physical partition in /etc/vfstab updated for /opt : /dev/dsk/c1t1d0s7
Step 3: Make a copy of /etc/vfstab

# cp /etc/vfstab /etc/vfstab.mirrored_solaris.<x> where <x> can be 8 (solaris.8) or 9 (solaris.9) depending on your current operating system.
To check the Solaris operating system you are running:

# uname -rm
5.9 indicates Solaris 9 5.8 indicates Solaris 8
Step 4: Modify /etc/vfstab Root file system / gets updated automatically while running metaroot /dev/ dsk/c1t0d0s0. Other partitions like swap, /var, /export/home and /opt must be updated so that when the server is rebooted, partitions are correctly mounted.
GPRS/UMTS
592
Make sure you have already made a copy of /etc/vfstab to say /etc/ vfstab.mirrored.solaris.x (where x is the version of Solaris OS running on the server). 1. Analyze the current /etc/vfstab
# cat /etc/vfstab
#device #to mount fd /proc /dev/md/dsk/d1 /dev/md/dsk/d0 /dev/md/dsk/d5 /dev/md/dsk/d7 /dev/md/dsk/d8 device to fsck /dev/fd fd /proc proc /dev/md/rdsk/d0 /dev/md/rdsk/d5 /dev/md/rdsk/d7 mount FS point type no no swap / ufs /var ufs /export/home ufs fsck pass no 1 1 ufs 1 mount mount at boot options no no 1 yes
yes -
/dev/md/rdsk/d8 /opt
2. Edit /etc/vfstab using unix editor vi and comment out (using #) the lines for /, swap, /var, /export/home and /opt (for d0, d1, d5, d7 and d8). 3. Add entries for the physical partitions for /, swap, /var, /export/home and / opt. Swap partition entry is different from the other partitions. For the root file system - /
#device device mount mount #to mount to fsck point options /dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 FS type / ufs fsck pass 1 mount at boot no
For - swap:
#device device mount #to mount to fsck boot options /dev/dsk/c1t0d0s1 mount point swap FS fsck type mount pass no at -
For - /var:
#device device mount mount #to mount to fsck point boot options /dev/dsk/c1t0d0s5 /dev/rdsk/c1t0d0s5 no FS fsck type /var mount pass ufs 1 at
For d7 - /export/home:
411-5221-309
Standard
06.30 March 10, 2010

FS fsck type
593
#device device mount mount #to mount to fsck point boot options /dev/dsk/c1t0d0s7 /dev/rdsk/c1t0d0s7 1 yes -
mount pass at ufs
/export/home
For d8 - /opt:
#device device mount mount #to mount to fsck point boot options /dev/dsk/c1t1d0s7 /dev/rdsk/c1t1d0s7 FS fsck type /opt mount pass ufs 1 yes at
Here is any updated /etc/vfstab with mirrors:

# cat /etc/vfstab
#device device mount FS fsck mount mount #to mount to fsck point type pass at boot options fd /dev/fd fd no /proc /proc proc no /dev/dsk/c1t0d0s1 swap no /dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no /dev/dsk/c1t0d0s5 /dev/rdsk/c1t0d0s5 /var ufs 1 no /dev/dsk/c1t0d0s7 /dev/rdsk/c1t0d0s7 /export/home ufs 1 yes /dev/dsk/c1t1d0s7 /dev/rdsk/c1t1d0s7 /opt ufs 1 yes swap /tmp tmpfs yes #/dev/md/dsk/d1 swap no #/dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no #/dev/md/dsk/d5 /dev/md/rdsk/d5 /var ufs 1 yes #/dev/md/dsk/d7 /dev/md/rdsk/d7 /export/home ufs 1 yes #/dev/md/dsk/d8 /dev/md/rdsk/d8 /opt ufs 1 yes -
Step 5: From /etc/vfstab, find out the root partition (/) disk. From the above example capture, c1t0d0s0 holds the root partition /. Next, using format < /dev/null determine the disk number associated c1t0d0s0. Here is an example capture of format < /dev/null, disk0 is associated with c1t0d0s0.
Searching for disks...done
GPRS/UMTS
594
AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010183a01,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010186a81,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b0b1,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0 6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0 10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 11. c1t13d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf786ffa,0 Specify disk (enter its number):
Make a note of the Boot Disk number: disk0. Also have solaris8_root handy explained inImportant Step to determine server boot path: on page 588.
Step 6: Stop SCS and LDAP server processes following Verify and Stopping SCS server and LDAP server processes on page 208, then execute lockfs -fa. # lockfs -fa
Step 7: Login to the server console and bring down the server to run level 0. # sync;sync;sync; # init 0
Step 8: At the server ok prompt, execute printenv and verify the value set for boot-device variable.
{6} ok printenv
Variable Name Value Default Value
411-5221-309
Standard
06.30 March 10, 2010

test-args diag-passes local-mac-address? fcode-debug? silent-mode? scsi-initiator-id oem-logo oem-logo? oem-banner oem-banner? ansi-terminal? screen-#columns screen-#rows ttyb-rts-dtr-off ttyb-ignore-cd ttya-rts-dtr-off ttya-ignore-cd ttyb-mode ttya-mode output-device input-device auto-boot-on-error? load-base auto-boot? boot-command diag-file diag-device boot-file boot-device use-nvramrc? nvramrc security-mode security-password security-#badlogins diag-out-console post-trigger power-on-res ... diag-script diag-level diag-switch? obdiag-trigger power-on-res ... error-reset-recovery 1 false false false 7 false
595
false true 80 34 false true false true 9600,8,n,1,9600,8,n,1,screen keyboard false 16384 true boot net disk1 disk6 false none 0 false error-reset power-on-res ... none min false error-reset power-on-res ... boot
1 false false false 7 No default false No default false true 80 34 false true false true 9600,8,n,1,9600,8,n,1,screen keyboard false 16384 true boot net disk net false No default No default No default false error-reset normal min false error-reset boot
Step 9: At the ok prompt, use the Solaris OpenBoot PROM nvalias command to define the solaris8_root device alias. From the solaris8_root captured in the example:
{2} ok nvalias solaris8_root /pci@8,600000/SUNW,qlc@2/ fp@0,0/disk@w500000e010188041,0:a
Redefine the boot-device alias to reference current_root. At the ok prompt:

{2} ok setenv boot-device solaris8_root boot-device = solaris8_root
GPRS/UMTS
596
Appendix C: Unmirroring the File Systems {2} ok nvstore {2} ok setenv use-nvramrc? true use-nvramrc? = true
Execute printenv and verify that the boot-device variable is set to current_root (under Value column). Verify variable use-nvramrc is set to true..
Step 10: Reboot the server

Note: In case the server is unable to reboot indicating a disk check is needed, please perform the following steps to fix the disk errors. Please have the follow tables handy -Disk Mirroring Mapping for Critical File Systems on page 70 and Disk Mirroring Mapping for Non-critical File Systems on page 70 Perform disk check procedure detailed in section Appendix I: Disk Check for SCS for non-mirrored servers on page 661
Step 11: Login to the server Step 12: Delete mirrors and the detached submirror. Note: While clearing the main mirror (example: d0), use -r option. This will clear Submirror 1 automatically. Then clear Submirror 2 without using the -r option.
# metaclear -r d0
d0: Mirror is cleared d10: Concat/Stripe is cleared
# metaclear d20
d20: Concat/Stripe is cleared
# metaclear -r d1
411-5221-309
Standard
06.30 March 10, 2010
597
# metaclear d21
# metaclear -r d5
# metaclear d25
# metaclear -r d7
# metaclear d27
# metaclear -r d8
# metaclear d28
Run the metastat command. The metastat command will now return no mirror or submirror information.
# metastat
Step 13: Clear metadb 1. Run metadb and find out the unique partitions used.
Example: # metadb
flags a m p luo a p luo a p luo a p luo a p luo first blk 16 1050 2084 16 1050 block count 1034 /dev/dsk/c1t0d0s3 1034 /dev/dsk/c1t0d0s3 1034 /dev/dsk/c1t0d0s3 1034 /dev/dsk/c1t1d0s3 1034 /dev/dsk/c1t1d0s3
GPRS/UMTS
598

a a a a a a a p p p p p p p luo luo luo luo luo luo luo 2084 16 1050 2084 16 1050 2084

1034 1034 1034 1034 1034 1034 1034 /dev/dsk/c1t1d0s3 /dev/dsk/c1t3d0s3 /dev/dsk/c1t3d0s3 /dev/dsk/c1t3d0s3 /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3
2. Delete the unique metabd partitions. Reformat the recovered partition using newfs.
# metadb -d /dev/dsk/c1t0d0s3 # newfs /dev/rdsk/c1t0d0s3 (type: y when prompted) # metadb -d /dev/dsk/c1t1d0s3 # newfs /dev/rdsk/c1t1d0s3 (type: y when prompted) # metadb -d /dev/dsk/c1t3d0s3 # newfs /dev/rdsk/c1t3d0s3 (type: y when prompted)
Note: While deleting the last metadb partition, use option -d -f. The last metadb partition cannot be deleted without the -f option.
# metadb -d -f /dev/dsk/c1t2d0s3 # newfs /dev/rdsk/c1t2d0s3 (type: y when prompted)
3. Run metadb to verify there are no partitions returned.
Step 14: Reformat the un-mirrored partitions All partitions assigned to submirror 2 (d2<n>) are reformatted.
Example: (Refer to table above Disk Mirroring Mapping) # newfs /dev/rdsk/c1t2d0s0 (assigned to d20) # newfs /dev/rdsk/c1t2d0s1 (assigned to d21) # newfs /dev/rdsk/c1t2d0s5 (assigned to d25) # newfs /dev/rdsk/c1t2d0s7 (assigned to d27) # newfs /dev/rdsk/c1t3d0s7 (assigned to d28)
Step 15: Perform Appendix J: Disk Check for SCS for mirrored server on page 664.
411-5221-309 Standard 06.30 March 10, 2010
599
End of un-mirroring procedure.
If the un-mirroring procedure was performed as part of the upgrade readiness checkpoint, return to Table 5, Upgrade readiness checkpoint #4 night before the upgrade, on page 46
GPRS/UMTS
600
Appendix D: Creating a Partition on a New Disk for Disk Mirroring
Appendix D: Creating a Partition on a New Disk for Disk Mirroring 45

Pre-requisite: Free unmounted disks available on the server This section explains the steps to create disk partitions on a new disk that will be used for disk mirroring. If your server was previously mirrored and you do not want to use the mirrored partitions, follow this procedure. 1. Perform 'df -k' to display the mounted disk partitions. The following example shows that disk c1t0d0 and c1t1d0 are mounted.
Example: # df -k
Filesystem /dev/dsk/c1t0d0s0 /proc fd mnttab /dev/dsk/c1t0d0s5 swap swap /dev/dsk/c1t1d0s7 /dev/dsk/c1t0d0s7 kbytes used avail capacity 10086988 450429 9535690 5% 0 0 0 0% 0 0 0 0% 0 0 0 0% 20174761 6494 19966520 1% 17326584 16 17326568 1% 17326792 224 17326568 1% 70577241 2178283 67693186 4% 20174761 428251 19544763 3% Mounted on / /proc /dev/fd /etc/mnttab /var /var/run /tmp /opt /export/home
2. Perform 'format' to display the available disks on the server. The following example indicates there are 12 disks available (with c1t0d0 and c1t1d0 already used).
Example: # format < /dev/null
Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010183a01,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010186a81,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b0b1,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0 6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0
411-5221-309
Standard
06.30 March 10, 2010
601
10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 11. c1t13d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf786ffa,0 Specify disk (enter its number):
3. To create a new partition, you need to choose a disk partition that is not mounted. Select a new disk and reformat it to match the already mounted disk partition. In the above example, disk 'c1t0d0' and 'c1t1d0' are mounted. The new 'c1t2d0' and 'c1t3d0' drives are used to create the new partitions. The following examples show the mounted 'c1t0d0' disk will mirror with the unmounted 'c1t2d0' disk. The mounted 'c1t1d0' disk will mirror with the unmounted 'c1t3d0' disk.
Example:
Use the following commands to reformat the new 'c1t2d0' disk to match the current mounted 'c1t0d0' disk partition. a. Determine the mounted partitions.
# more /etc/vfstab
#live-upgrade:<Wed Feb 8 14:41:55 CST 2006> <solaris9> #device device mount #to mount to fsck point options /dev/dsk/c1t0d0s1 swap /dev/dsk/c1t0d0s5 /dev/rdsk/c1t0d0s0 /dev/dsk/c1t0d0s5 /dev/rdsk/c1t0d0s5 /dev/dsk/c1t0d0s7 /dev/rdsk/c1t0d0s7 yes /dev/dsk/c1t1d0s7 /dev/rdsk/c1t1d0s7 updated boot environment FS type / /var fsck mount mount pass at boot no ufs ufs 1 1 ufs 2 no no 2 yes
/export/home /opt ufs
Important Note: The following steps involve creating a partition table on the new disk. When running the commands prtvtoc and fmthard, cautiously input the partitions as incorrect partition parameter can cause loss of data. The partition parameter after prtvtoc must be the currently mounted partition The partition parameter after fmthard must be the partitions on the new disk
b. Reformat the new 'c1t2d0' disk to match 'c1t0d0' using the following commands
GPRS/UMTS
602
Reformat for '/' (root) partition:

# prtvtoc /dev/rdsk/c1t0d0s0 | fmthard -s - /dev/rdsk/c1t2d0s0 # newfs /dev/rdsk/c1t2d0s0
newfs: /dev/rdsk/c1t2d0s0 last mounted as / newfs: construct a new file system /dev/rdsk/c1t2d0s0: (y/n)? y
Note: (answer 'y' when prompted) Reformat for 'swap' partition:

newfs: /dev/rdsk/c1t0d0s1 last mounted as swap newfs: construct a new file system /dev/rdsk/c1t2d0s1: (y/n)? y
Note: (answer 'y' when prompted) Reformat for '/var' partition:

newfs: /dev/rdsk/c1t0d0s5 last mounted as var newfs: construct a new file system /dev/rdsk/c1t2d0s5: (y/n)? y
Note: (answer 'y' when prompted) Reformat for '/export/home' partition:

newfs: /dev/rdsk/c1t0d0s7 last mounted as export/home newfs: construct a new file system /dev/rdsk/c1t2d0s7: (y/n)? y
Note: (answer 'y' when prompted) c. Reformat the new 'c1t3d0' disk to match the mounted 'c1t1d0' disk for '/opt' partition.
411-5221-309
Standard
06.30 March 10, 2010
603
newfs: /dev/rdsk/c1t1d0s7 last mounted as opt newfs: construct a new file system /dev/rdsk/c1t3d0s7: (y/n)? y
Note: (answer 'y' when prompted) 4. A partition for the metadb needs to be created on the new disks. Using format and find out the metadb partitions on the mounted disks. The metadb partitions on the mounted disk must already be created during server installation. In this example, slice 3 on c1t0d0 and slice 3 on c1t1d0 are partitions for metadb with 10 MB size.
Partition table for disk c1t0d0 partition> p Current partition table (original): Total disk cylinders available: 24620 + 2 (reserved cylinders) Part 0 Tag root Flag wm wm wm wm wm Cylinders 0 - 7088 Size 9.77GB Blocks (7089/0/0) 20480121 (2836/0/0) 8193204 (24620/0/0) 71127180 (8/0/0) 0 23112
1 unassigned 2 backup
7089 - 9924 0 - 24619 9925 - 9932 0 0
3.91GB 33.92GB
3 unassigned 4 unassigned 5 var
11.29MB (0/0/0)
wm
9933 - 17530 0
10.47GB 0
(7598/0/0) 21950622 0 (7089/0/0) 20480121
6 unassigned 7 home
wm
(0/0/0) 9.77GB
wm 17531 - 24619
Partition table for disk c1t1d0 partition> p Current partition table (original): Total disk cylinders available: 24620 + 2 (reserved cylinders) Part Tag Flag wm wm wm Cylinders 0 0 0 - 24619 Size 0 0 Blocks (0/0/0) (0/0/0) 33.92GB 0 0
0 unassigned 1 unassigned 2 backup
(24620/0/0) 71127180 Upgrade Manual GGSN6.0
GPRS/UMTS
604
Appendix D: Creating a Partition on a New Disk for Disk Mirroring 3 unassigned 4 unassigned 5 unassigned 6 unassigned 7 unassigned wm wm wm wm wm 00 0 0 8 - 24619 7 11.29MB 0 0 0
Nortel Networks Confidential (8/0/0) 0 0 0 (24612/0/0) 71104068 23112
(0/0/0) (0/0/0) (0/0/0) 33.91GB
a) Reformat slice 3 on the new disk c1t2d0 to match the mounted disk c1t0d0 # prtvtoc /dev/rdsk/c1t0d0s3 | fmthard -s - /dev/rdsk/c1t2d0s3 # newfs /dev/rdsk/c1t2d0s3
b) Reformat slice 3 on the new disk c1t3d0 to match the mounted disk c1t1d0 # prtvtoc /dev/rdsk/c1t1d0s3 | fmthard -s - /dev/rdsk/c1t3d0s3 # newfs /dev/rdsk/c1t3d0s3
5. Verify the newly created partitions are the same size. Run 'format' for the disk and verify the 'Block' sizes are the same for the partitions. The following is an example on how to verify the partition table and block sizes for Disk 0 and Disk 2.
Example:
# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf78714d,0 1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf7872e3,0 2. c1t2d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf787314,0 3. c1t3d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf787253,0 4. c1t4d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf78701b,0 Specify disk (enter its number):
411-5221-309
Standard
06.30 March 10, 2010
605
Specify disk (enter its number): 0 selecting c1t0d0 [disk formatted] Warning: Current Disk has mounted partitions. FORMAT MENU: disk type - select a disk - select (define) a disk type
partition - select (define) a partition table current - describe the current disk format repair label analyze defect backup verify save - format and analyze the disk - repair a defective sector - write label to the disk - surface analysis - defect list management - search for backup labels - read and display labels - save new disk/partition definitions
inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> quit format> format> p PARTITION MENU: 0 1 2 3 4 5 6 7 - change `0' partition - change `1' partition - change `2' partition - change `3' partition - change `4' partition - change `5' partition - change `6' partition - change `7' partition - execute <cmd>, then return
select - select a predefined table modify - modify a predefined partition table
GPRS/UMTS
606

name - name the current table print - display the current table label - write partition map and label to the disk !<cmd> - execute <cmd>, then return quit partition> partition> p Current partition table (original): Total disk cylinders available: 24620 + 2 (reserved cylinders)
Part 0
Tag Flag root wm
Cylinders 0 - 7088
Size
Blocks
9.77GB (7089/0/0) 20480121 3.91GB (2836/0/0) 8193204 33.92GB (24620/0/0) 71127180 11.29MB (8/0/0) 0 (0/0/0) 0 23112
1 unassigned wm 7089 - 9924 2 backup wm 0 - 24619
3 unassigned wm 9925 - 9932 4 unassigned wm 5 0
var wm 9933 - 17530 0
10.47GB (7598/0/0) 21950622 0 (0/0/0) 0
6 unassigned wm 7
home wm 17531 - 24619
9.77GB (7089/0/0) 20480121
partition> partition> partition> q FORMAT MENU: disk type - select a disk - select (define) a disk type
partition - select (define) a partition table current - describe the current disk format repair label analyze defect backup - format and analyze the disk - repair a defective sector - write label to the disk - surface analysis - defect list management - search for backup labels
411-5221-309
Standard
06.30 March 10, 2010

verify save

- read and display labels - save new disk/partition definitions
607
inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> quit format> format> format> disk 2 selecting c1t2d0 [disk formatted] format> format> p PARTITION MENU: 0 1 2 3 4 5 6 7 - change `0' partition - change `1' partition - change `2' partition - change `3' partition - change `4' partition - change `5' partition - change `6' partition - change `7' partition - execute <cmd>, then return
select - select a predefined table modify - modify a predefined partition table name - name the current table print - display the current table label - write partition map and label to the disk !<cmd> - execute <cmd>, then return quit partition> partition> p Current partition table (original): Total disk cylinders available: 24620 + 2 (reserved cylinders)
GPRS/UMTS
608

Part 0 Tag Flag root wm Cylinders 0 - 7088 Size Blocks
9.77GB (7089/0/0) 20480121 3.91GB (2836/0/0) 8193204 33.92GB (24620/0/0) 71127180 11.29MB (8/0/0) (0/0/0) 0 23112
1 unassigned wm 7089 - 9924 2 backup wm 0 - 24619
3 unassigned wm 9925 - 9932 4 unassigned wu 5 0 0
var wm 9933 - 17530 0 0
10.47GB (7598/0/0) 21950622 (0/0/0) 0
6 unassigned wu 7
home wm 17531 - 24619
9.77GB (7089/0/0) 20480121
partition> q FORMAT MENU: disk type - select a disk - select (define) a disk type
partition - select (define) a partition table current - describe the current disk format repair label analyze defect backup verify save - format and analyze the disk - repair a defective sector - write label to the disk - surface analysis - defect list management - search for backup labels - read and display labels - save new disk/partition definitions
inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> quit format> q - execute <cmd>, then return
411-5221-309
Standard
06.30 March 10, 2010
Appendix E: Creating Mirrors
609

Prerequisite:
46
Make sure you have verified the sanity of the server disks by following procedure Appendix J: Disk Check for SCS for mirrored server on page 664 before proceeding this section. After running through disk check, you can start mirroring the disks. Caution: Every step in this procedure must be carefully read and executed. An incorrect entry may cause the server reboot to fail.
Mirroring the Solaris server involves: 1. Creating metadb 2. Identifying the mounted partitions and partitions that will be used for creating the submirrors. 3. Re-formatting the partition identified as submirrors 4. Initializing the mirrors and submirrors. 5. Modifying boot device using metaroot 6. Editing /etc/vfstab 7. Rebooting the server 8. Attaching the submirrors to the mirrors 9. After server reboots, perform Disk Check for SCS for mirrored server 10. Update table Disk Mirroring Mapping for Critical File Systems on page 70 and Disk Mirroring Mapping for Non-critical File Systems on page 70 for reference.
Procedure: Step 1. Create metadb Create a new metadb by using the following form of the metadb command. Please choose an unmounted partition with size at least 10 MB. After creating the metadb, use metadb to verify if the metadb have been created.
GPRS/UMTS
610
Appendix E: Creating Mirrors # metadb -a -c n -f ctds-of-slice where
-a specifies to add a state database replica. -c n specifies the number of the replicas to add to the specified slice. Adding replicas will depend on the available size of the partition that will hold metadb. Each replica will occupy 4 MB. So if you have a 10 MB partition, then you can pass option -c 2. Run format to find out the disk space allocated for metadb. -f specifies to force the operation. ctds-of-slice specifies the number of the component that will hold the replica.
Example:
In this example, metadb is created on 4 partitions (10 MB each) creating 2 replicas

# metadb -a -f -c 2 /dev/dsk/c1t0d0s3 # metadb -a -f -c 2 /dev/dsk/c1t1d0s3 # metadb -a -f -c 2 /dev/dsk/c1t2d0s3 # metadb -a -f -c 2 /dev/dsk/c1t3d0s3 # metadb flags a a a a a a a a u u u u u u u u first blk 16 8208 16 8208 16 8208 16 8208 block count 8192 8192 8192 8192 8192 8192 8192 8192 /dev/dsk/c1t2d0s3 /dev/dsk/c1t2d0s3 /dev/dsk/c1t3d0s3 /dev/dsk/c1t3d0s3 /dev/dsk/c1t0d0s3 /dev/dsk/c1t0d0s3 /dev/dsk/c1t1d0s3 /dev/dsk/c1t1d0s3
Mirroring needs to be done for all mounted file systems including swap. Please refer to Partition Table for current SCS for details of the partitions. The procedure below explains how to retrieve relevant information from the Partition Table for current SCS and perform disk mirroring.
411-5221-309
Standard
06.30 March 10, 2010
Appendix E: Creating Mirrors 611
See Table 31 and Table 32 for examples of Disk Mirroring Mapping for both critical and non-critical file systems. Step 2a. Record the mounted partitions using df -k
# df -k
Filesystem /dev/dsk/c1t2d0s0 /proc mnttab fd /dev/dsk/c1t2d0s5 swap swap /dev/dsk/c1t3d0s7 /dev/dsk/c1t0d0s7 home kbytes used avail capacity Mounted on 10086988 1160821 8825298 12% / 0 0 0 0% /proc 0 0 0 0% /etc/mnttab 0 0 0 0% /dev/fd 20174761 29963 19943051 1% /var 17328928 32 17328896 1% /var/run 17334128 5232 17328896 1% /tmp 70577241 1778973 68092496 3% /opt 20174761 448267 19524747 3% /export/
Step 2b. Record the swap partition identified from /etc/vfstab

# cat /etc/vfstab | grep swap
/dev/dsk/c1t0d0s1 swap no -
From example Table 31 for Critical file system and df -k, we can identify that Column Second sub-mirror / disk partition-- partition for Solaris 9 has been used by the Solaris 9 system for File systems - /, / var and /opt. From example Table 32 for Non-critical file systems and /etc/vfstab, we can identify First sub-mirror / disk partition has been used by the Solaris 9 system for File systems - /export/home and swap.
Step 2c. Identify submirrors to use for mirroring From example Table 31 for Critical file system - identify the partition from column First sub-mirror / disk partition -- partition for Solaris 8. From example Table 32 for Non-critical file system - identify the partition for column Second sub-mirror / disk partition. Step 2d. Re-format using newfs all the partitions identified in Step 2c. This will clear up the partitions that will be used for mirroring.
Example: For d0: / # newfs /dev/rdsk/c1t0d0s0
GPRS/UMTS
612
newfs: /dev/rdsk/c1t0d0s0 last mounted as /tmp/.alt.lumkiconf.2286 newfs: construct a new file system /dev/rdsk/c1t0d0s0: (y/n)? y ......
Example: For d1: swap # newfs /dev/rdsk/c1t2d0s1
Example: For d5: /var # newfs /dev/rdsk/c1t0d0s5
Example: For d7: /export/home # newfs /dev/rdsk/c1t2d0s7
Example: For d8: /opt # newfs /dev/rdsk/c1t1d0s7
Step3: Make a copy of /etc/vfstab

# cp /etc/vfstab /etc/vfstab.nonmirrored_solaris.<x> where <x> can be 8 (solaris.8) or 9 (solaris.9) depending on your current operating system.
To check the Solaris OS you are running:

# uname -rm
5.9 indicates Solaris 9 5.8 indicates Solaris 8
Step 4: Mirroring the mounted file systems Mirroring convention used in this example:
d<n> - Mirror (example: d0)
411-5221-309
Standard
06.30 March 10, 2010
613
d1<n> - Represents Submirror 1 (example: d10). This is assigned the partitions that are currently mounted. Use the df -k command to display all the currently mounted partitions. In Table 31 for Critical File System, the column Second Submirror / Disk Partition -- Partition for Solaris 9 identifies d1<n>. In Table 32 for Non-critical file systems, the column First Submirror / Disk Partition identifies d1<n>. d2<n> - Represents Submirror 2 (example: d20): This is assigned the partitions that are currently un-mounted. In Table 31 for Critical File System, the column First Submiror / Disk Partition -- Partition for Solaris 8 identifies d2<n>. In Table 32 for Non-critical file systems, the column Second Submirror / Disk Partition identifies d2<n>.
Mirror / - d0: Note: Follow all the steps for mirroring d0. If any step is skipped, the server may not reboot. 1. Create a new RAID 0 volume on the slice by using the following command:
# metainit -f d10 1 1 c1t2d0s0 d10: Concat/Stripe is setup
Important Step to determine server boot path and alternate server boot path:
Make a note of the server boot path, server alternate boot path is explained when setting d20. This is needed to make changes to Solaris boot environment during the reboot of the server after disk mirroring. To determine the server root path: Run ls -al for the physical partition assigned for d10 submirror. From the above example, /dev/dsk/c1t2d0s0 is set for d10.
GPRS/UMTS
614
Make a note of this string, this is called current_root for reference. This will be needed during reboot of the server after mirroring all the partitions.
current_root - /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w21000004cf786ffa,0:a
2. Create a second RAID 0 volume (concatenation) on the unused slice to act as the second submirror.
Next, make a note of the server alternate boot path. This is appended to
current_root in the Solaris boot environment.
To determine the server backup root device: Run ls -al for the physical partition assigned for d20 partition. In the below example, /dev/dsk/c1t0d0s0 is set for d20.
Make a note of this string, this is called backup_root for reference. This will be needed during reboot of the server after mirroring all the partitions. backup_root - /pci@8,600000/SUNW,qlc@2/fp@0,0/
disk@w500000e010188041,0:a
411-5221-309
Standard
06.30 March 10, 2010
615
3. Create a one-way mirror by using the following command:

#metainit d0 -m d10 d0: Mirror is setup
4. Set d0 as the boot device

# metaroot d0
5. Verify /etc/vfstab. An entry for d0 will be added with mount point /.
Mirror swap - d1: Step a:

Step b:
Step c:
# metainit d1 -m d11 d1: Mirror is setup
Mirror /var - d5: Step a:

Step b:
GPRS/UMTS
616
Step c:
Step a: Mirror /export/home - d7:

#metainit -f d17 1 1 c1t0d0s7 d17: Concat/Stripe is setup
Step b:
Step c:
Mirror /opt - d8: Step a:

Step b:
# metainit -f d28 1 1 c1t1d0s7
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential d28: Concat/Stripe is setup
617
Step c:
Step 5: Modify /etc/vfstab d0 is updated automatically while running metaroot d0. Other mirrors like d1 (swap), d5 (/var), d7 (/export/home) and d8 (/opt) must be updated so that when the server is rebooted, mirrors are correctly mounted. Make sure you have already made a copy of /etc/vfstab to say /etc/ vfstab.unmirrored.solaris.<x> (where <x> is the version of Solaris OS running on the server). 1. Analyze /etc/vfstab
# cat /etc/vfstab
fd /dev/fd fd no /proc /proc proc no /dev/dsk/c1t2d0s1 /dev/rdsk/c1t2d0s1 / ufs no /dev/dsk/c1t0d0s1 swap no /dev/dsk/c1t2d0s5 /dev/rdsk/c1t2d0s5 /var ufs no /dev/dsk/c1t0d0s7 /dev/rdsk/c1t0d0s7 /export/home 2 yes /dev/dsk/c1t3d0s7 /dev/rdsk/c1t3d0s7 /opt ufs yes swap /tmp tmpfs yes -
1 1 ufs 2
2. Edit /etc/vfstab using unix editor vi and comment out (using #) the lines for swap, /var, /export/home and /opt. 3. Add entries for mirrors d5, d7 and d8. Swap partition d1 convention is different from the other partitions. 4. Important Note: While editing /etc/vfstab, make sure the partitions fd and /proc are not commented out, i.e partitions fd and /proc must not have a # in the begining of the line. Note: For System file partitions such as /, /var and usr, mount at boot option in /etc/vfstab must be set to no
GPRS/UMTS
618
For d0 - /: (Automatically added by metaroot d0)

#device device mount mount #to mount to fsck point boot options /dev/md/dsk/d0 /dev/md/rdsk/d0 / FS fsck type ufs 1 mount pass no at -
For d1 - swap:
#device device mount #to mount to fsck boot options /dev/md/dsk/d1 mount point swap FS fsck type no mount pass at
For d5 - /var:
#device device mount mount #to mount to fsck point boot options /dev/md/dsk/d5 /dev/md/rdsk/d5 /var FS fsck type ufs 1 mount pass no at -
For d7 - /export/home:
#device device mount FS fsck mount mount #to mount to fsck point type pass at boot options /dev/md/dsk/d7 /dev/md/rdsk/d7 /export/home ufs 1 yes -
For d8 - /opt:
#device device mount mount #to mount to fsck point boot options /dev/md/dsk/d8 /dev/md/rdsk/d8 /opt FS fsck type ufs 1 mount pass yes at -
Here is any updated /etc/vfstab with mirrors:

# cat /etc/vfstab
#device device mount mount #to mount to fsck point boot options fd /dev/fd fd /proc /proc proc /dev/md/dsk/d1 swap /dev/md/dsk/d0 /dev/md/rdsk/d0 / FS fsck type no no ufs no 1 mount pass at
no
411-5221-309
Standard
06.30 March 10, 2010
619
-
/dev/md/dsk/d5 /dev/md/rdsk/d5 /var ufs 1 yes /dev/md/dsk/d7 /dev/md/rdsk/d7 /export/home ufs 1 yes /dev/md/dsk/d8 /dev/md/rdsk/d8 /opt ufs 1 yes #/dev/dsk/c1t0d0s1 swap no #/dev/dsk/c1t2d0s5 /dev/rdsk/c1t2d0s5 /var ufs 1 no #/dev/dsk/c1t0d0s7 /dev/rdsk/c1t0d0s7 /export/home ufs 2 yes #/dev/dsk/c1t3d0s7 /dev/rdsk/c1t3d0s7 /opt ufs 2 yes swap /tmp tmpfs yes -
Step 6: Verify /etc/vfstab and find out the metadevice name associated with the root partition (/). In this example, metadevice d0 is associated with the root partition /. # more /etc/vfstab Filesystem /dev/md/dsk/d0 ... ... At this point of server mirroring, the second submirrors have not been attached. From the example, Metadevice d10 has been associated with d0. Since the server will be rebooted to continue the mirroring procedure, the correct boot device must be referenced. Step 7: Find out the physical device associated with metadevice d10 and d20. This is the physical disk that holds the root partition. Example:
# metastat d10 d10: Concat/Stripe Size: 22528422 blocks (10 GB) Stripe 0: Device c1t2d0s0 Start Block Dbase 0 No State Reloc Hot Spare Okay Yes
kbytes used avail capacity Mounted on 10086988 429705 9556414 5% /
Device Relocation Information: Device Reloc Device ID
GPRS/UMTS
620
Appendix E: Creating Mirrors c1t2d0 Yes id1,ssd@w21000004cf786ffa
# metastat d20 d20: Concat/Stripe Size: 22528422 blocks (10 GB) Stripe 0: Device c1t0d0s0 Start Block Dbase 0 No State Reloc Hot Spare Okay Yes
Device Relocation Information: Device Reloc Device ID c1t0d0 Yes id1,ssd@w500000e010188041
Here disk c1t2d0s0 is associated with metadevice d10 and disk c1t0d0s0 is associated with metadevice d20. Step 8: Execute format </dev/null and find out the disk number associated with the metadevice d10 submirror - c1t2d0s0 and d20 submirror c1t0d0s0
Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010183a01,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010186a81,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b0b1,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0 6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0 10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 11. c1t13d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf786ffa,0 Specify disk (enter its number):
411-5221-309
Standard
06.30 March 10, 2010
621
Make a note of the Boot Disk number: disk2 and disk0. Also have current_root and backup_root handy explained inImportant Step to determine server boot path and alternate server boot path: on page 613 Step 9: Bring down the server to server ok prompt.
# sync;sync;sync # lockfs -fa # init 0
Step 10: At the ok prompt, use the Solaris OpenBoot PROM nvalias command to define the current_root and backup_root device alias. From the current_root and backup_root captured in the example:
{2} ok nvalias current_root /pci@8,600000/SUNW,qlc@2/ fp@0,0/disk@w21000004cf786ffa,0:a {2} ok nvalias backup_root /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w500000e010188041,0:a
Redefine the boot-device alias to reference current_root and backup_root. At the ok prompt:
{2} ok setenv boot-device current_root backup_root boot-device = current_root backup_root {2} ok nvstore {2} ok setenv use-nvramrc? true use-nvramrc? = true
Execute printenv and verify that the boot-device variable is set to current_root and backup_root (under Value column). Verify variable usenvramrc is set to true.. Step 11: Reboot the server
{2} ok boot current_root
GPRS/UMTS
622
Note: In case the server is unable to reboot indicating a disk check is needed, please perform the following steps to fix the disk errors. Please have the follow tables handy -Disk Mirroring Mapping for Critical File Systems on page 70 and Disk Mirroring Mapping for Non-critical File Systems on page 70 Perform disk check procedure detailed in section Appendix J: Disk Check for SCS for mirrored server on page 664
Step 12: Login to the server Step 13: Attach mirrors Note: Convention used in this example: d<n> is attached with d2<n>
# metattach d0 d20 d0: submirror d20 is attached # metattach d1 d21 d1: submirror d21 is attached # metattach d5 d25 d5: submirror d25 is attached # metattach d7 d27 d7: submirror d27 is attached # metattach d8 d28 d8: submirror d28 is attached
Step 14: Check metastat for mirroring status and verify for data sync progress Check mirrors and attached submirrors:
# metastat
d0: Mirror Submirror 0: d10 State: Okay Submirror 1: d20 State: Resyncing Resync in progress: 1 % done
411-5221-309
Standard
06.30 March 10, 2010

Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 20484288 blocks (9.8 GB)
623
d10: Submirror of d0 State: Okay Size: 20484288 blocks (9.8 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t2d0s0 0 No Okay Yes d20: Submirror of d0 State: Resyncing Size: 20484288 blocks (9.8 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t0d0s0 0 No Okay Yes d1: Mirror Submirror 0: d11 State: Okay Submirror 1: d21 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 16780224 blocks (8.0 GB) d11: Submirror of d1 State: Okay Size: 16780224 blocks (8.0 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t0d0s1 0 No Okay Yes d21: Submirror of d1 State: Okay Size: 16780224 blocks (8.0 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t2d0s1 0 No Okay Yes d5: Mirror Submirror 0: d15 State: Okay Submirror 1: d25 State: Resyncing Resync in progress: 0 % done Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 40968576 blocks (19 GB) d15: Submirror of d5 State: Okay Size: 40968576 blocks (19 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t2d0s5 0 No Okay Yes d25: Submirror of d5 State: Resyncing Size: 40968576 blocks (19 GB)
GPRS/UMTS
624
Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t0d0s5 0 No Okay Yes d7: Mirror Submirror 0: d17 State: Okay Submirror 1: d27 State: Okay Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 40968576 blocks (19 GB) d17: Submirror of d7 State: Okay Size: 40968576 blocks (19 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t0d0s7 0 No Okay Yes d27: Submirror of d7 State: Okay Size: 40968576 blocks (19 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t2d0s7 0 No Okay Yes d8: Mirror Submirror 0: d18 State: Okay Submirror 1: d28 State: Resyncing Resync in progress: 0 % done Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 143318784 blocks (68 GB) d18: Submirror of d8 State: Okay Size: 143318784 blocks (68 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t3d0s7 0 No Okay Yes d28: Submirror of d8 State: Resyncing Size: 143318784 blocks (68 GB) Stripe 0: Device Start Block Dbase State Reloc Hot Spare c1t1d0s7 0 No Okay Yes Device Relocation Information: Device Reloc Device ID c1t1d0 Yes id1,ssd@SFUJITSU_MAN3735F_SUN72G_000239V40773 c1t3d0 Yes id1,ssd@w500000e01069b0b0 c1t0d0 Yes id1,ssd@SFUJITSU_MAN3735F_SUN72G_000239V41087 c1t2d0 Yes id1,ssd@SFUJITSU_MAN3735F_SUN72G_000239V40962
This command will help determine the mirror resync progress. When the mirroring resync completes, the command will not return an output.
# metastat | grep "Resync in progress*" 411-5221-309 Standard 06.30 March 10, 2010

Resync in progress: 0 % done Resync in progress: 0 % done Resync in progress: 2 % done
625
Step 15: Perform metastat and verify for all the mirrors and submirrors, the 'State' is 'Okay' (State: Okay) If case certain Submirrors indicate State as Maintenance, please perform the following steps to correct the error. Here is an example capture showing one of the submirrors with State as Maintenance. In this example, Submirror d20 has the State as Maintenance.
d0: Mirror Submirror 0: d11 State: Okay Submirror 1: d12 State: Needs maintenance Pass: 1 Read option: roundrobin (default) Write option: parallel (default) Size: 8517312 blocks d10: Submirror of d0 State: Okay Size: 8517312 blocks Stripe 0: Device Hot Spare c1t0d0s1
Start Block 0
Dbase State No Okay
d20: Submirror of d0 State: Needs maintenance Invoke: metareplace d10 c1t1d0s1 <new device> Size: 8517312 blocks Stripe 0: Device Start Block Dbase State Hot Spare c1t1d0s1 0 No Maintenance
Here are the steps to fix the Maintenance state to Okay state. Make a note of all the Submirrors that indicate Maintenance state using metastat. Execute metareplace -e command passing the following arguments:
state
metareplace -e <Mirror> <slice indicating Maintenance> Here is an example to fix Submirror d20: metareplace -e d0 c1t1d0s1
GPRS/UMTS
626
Run metastat and executing metareplace -e on all Submirrors that require maintenance and verify they are all State as Okay.
Step 16: Perform Appendix J: Disk Check for SCS for mirrored server on page 664 Step 17: Create a new spreadsheet and update table See Disk Mirroring Mapping for Critical File Systems on page 70 and See Disk Mirroring Mapping for Non-critical File Systems on page 70. End of mirroring procedure
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems
Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems for Mirrored Servers
47
For mirrored servers, full backup and restore script using NNBRSCS scripts performs backup and restore of critical file systems namely /, /usr, /var and / opt. This procedure explains the steps to backup and restore other mounted file systems. The example shows how to do a backup and restore of /export/home file system. Backup Procedure for backing up non-critical file system Note: If you are following this section from Full System backup and restore, please skip steps 1 through 5 below. 1. Login as root. 2. Determine the non-critical file systems to be backed up. Display the contents of the /etc/vfstab file. # more /etc/vfstab 3. Look in the mount point column for the name of the file system. 4. Use the directory name listed in the mount point column when you back up the file system. The file system to be backed up in the illustrated example is /export/home. Note: The column headings in /etc/vfstab may be shifted from the actual column values. Example:
# more /etc/vfstab #live-upgrade:<Thu Jan 19 17:14:51 CST 2006> updated boot environment <solaris9> #device device mount FS fsck mount mount #to mount to fsck point type pass at boot options # fd /dev/fd fd no /proc /proc proc no /dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no /dev/md/dsk/d1 - - swap - no /dev/md/dsk/d5 /dev/md/rdsk/d5 /var ufs 1 yes /dev/md/dsk/d7 /dev/md/rdsk/d7 /export/home ufs 1 yes /dev/md/dsk/d8 /dev/md/rdsk/d8 /opt ufs 1 yes -
GPRS/UMTS
628
5. Bring the system to run level S (single-user mode). Please refer to Rebooting the SCS server to single user mode on page 210 6. Unmount the non-critical file system to be backed up. Here is an example to unmount /export/home partition.
# umount /export/home
Note: If the partition is already unmounted, skip this step. User will get an error similar to the following:
# umount /export/home umount: warning: /export/home not in mnttab umount: /export/home not mounted
7. Check the file system for consistency.

# fsck -m /dev/md/dsk/<metadevice>
In this example metadevice for /export/home is /dev/md/dsk/d7. The fsck -m command checks for the consistency of file systems. For example, power failures can leave files in an inconsistent state. Example:
# fsck -m /dev/md/dsk/d7 ** /dev/md/dsk/d7 ufs fsck: sanity check: /dev/md/dsk/d7 okay
8. Identify the device name of the tape drive. The default tape drive is the /dev/rmt/0 device. 9. Insert a tape that is not write-protected into the tape drive. 10. Back up file systems using ufsdump.
# ufsdump options arguments filenames
0 specifies that this is a 0 level dump (or a full backup) u specifies that the /etc/dumpdates file is updated with the date of this backup c identifies a cartridge tape device f /dev/rmt/0 identifies the tape device /export/home is the file system being backed up Example:
# ufsdump 0ucf /dev/rmt/0 /export/home DUMP: Date of this level 0 dump: Mon Jan 23 02:02:04 2006 411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d7 (urc2y3pa:/export/home) to /dev/rmt/0. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Writing 63 Kilobyte records DUMP: Estimated 1763340 blocks (861.01MB). DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: Tape rewinding DUMP: 1763242 blocks (860.96MB) on 1 volume at 2918 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Mon Jan 23 02:02:04 2006
11. If prompted, remove the tape and insert the next tape volume. 12. Label each tape with the volume number, dump level, date, system name, disk slice, and file system. 13. Bring the system back to run level 3 by pressing Control-D. 14. Verify that the backup was successful. Here device-name is the tape device.
# ufsrestore tf device-name
Example:
# ufsrestore tf /dev/rmt/0
2 3 4 5 . ./lost+found ./patches.tar ./shasta.tar
15. Reboot the server to multi-user mode.

# init 6
Restore Procedure for restoring non-critical file system 1. Login as root. 2. Bring the system to run level S (single-user mode). Refer toRebooting the SCS server to single user mode on page 210 3. Unmount the file system. Verify /etc/vfstab (step 2-4 for backup procedure above) for the mount point
# umount file_system
Example:
# umount /dev/md/dsk/d7
4. Create the new file system.

# newfs file_system
GPRS/UMTS
630
You are asked if you want to construct a new file system on the raw device. Verify that the device-name is correct so you don't destroy the wrong file system. Example:
# newfs /dev/md/dsk/d7 newfs: /dev/md/rdsk/d7 last mounted as /export/home newfs: construct a new file system /dev/md/rdsk/d7: (y/n)? y /dev/md/rdsk/d7: 40968576 sectors in 4026 cylinders of 24 tracks, 424 sectors 20004.2MB in 403 cyl groups (10 c/g, 49.69MB/g, 6016 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, 102224, 204416, 306608, 408800, 510992, 613184, 715376, 817568, 919760, Initializing cylinder groups: ....... super-block backups for last 10 cylinder groups at: 39995600, 40097792, 40199984, 40302176, 40404368, 40506560, 40608752, 40710944, 40813136, 40915328,
5. Create a temporary directory, say /mnt. Mount the new file system on a temporary mount point.
# mount /dev/md/dsk/metadevice /mnt
Example:
# mkdir /mnt # mount /dev/md/dsk/d7 /mnt1
6. Change to the mount point directory.

# cd /mnt
7. (Optional) Write-protect the tapes for safety. 8. Insert the first volume of the level 0 tape into the tape drive. 9. Restore the files using ufsrestore. The level 0 dump is restored. If the dump required multiple tapes, you are prompted to load each tape in numeric order.
# ufsrestore rvf /dev/rmt/0
Example:
# ufsrestore rvf /dev/rmt/0 Verify volume and initialize maps Media block size is 126 Dump date: Mon Jan 23 02:02:04 2006 Dumped from: the epoch Level 0 dump of /export/home on urc2y3pa:/dev/md/dsk/d7
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems Label: none Begin level 0 restore Initialize symbol table. Extract directories from tape Calculate extraction list. Warning: ./lost+found: File exists Extract new leaves. Check pointing the restore extract file ./patches.tar extract file ./shasta.tar Add links Set directory mode, owner, and times. Check the symbol table. Check pointing the restore
10. Remove the tape and load the next level tape in the drive. Always restore tapes starting with 0 and continuing till you reach the highest level. 11. Repeat Step 8 through Step 10 for each dump level, from the lowest to the highest level (step 11-12 of backup procedure above). 12. Verify that the file system is restored.
# ls
13. Remove the restoresymtable file. The restoresymtable file that is created and used by the ufsrestore command to check-point the restore is removed.
# rm restoresymtable
14. Change to another directory.

# cd /
15. Unmount the newly restored file system.

# umount /mnt
16. Remove the last tape and insert a new tape that is not write-protected in the tape drive. 17. Always do an immediate backup of a newly created file system because ufsrestore repositions the files and changes the inode allocation. Make a level 0 backup of the newly restored file system.
# ufsdump 0uf /dev/rmt/0 /dev/md/dsk/metadevice
Example:
# ufsdump 0uf DUMP: Date of DUMP: Date of DUMP: Dumping dev/rmt/0. DUMP: Mapping /dev/rmt/0 /dev/md/dsk/d7 this level 0 dump: Mon Jan 23 13:00:31 2006 last level 0 dump: the epoch /dev/md/rdsk/d7 (urc2y3pa:/export/home) to / (Pass I) [regular files] GPRS/UMTS Upgrade Manual GGSN6.0
632
Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems for Mirrored Servers DUMP: DUMP: DUMP: DUMP: DUMP: DUMP: DUMP: DUMP: DUMP: Mapping (Pass II) [directories] Writing 32 Kilobyte records Estimated 1763278 blocks (860.98MB). Dumping (Pass III) [directories] Dumping (Pass IV) [regular files] Tape rewinding 1763262 blocks (860.97MB) on 1 volume at 2812 KB/sec DUMP IS DONE Level 0 dump on Mon Jan 23 13:00:31 2006
18. Mount the restored file system (verify /etc/vfstab for details).
# mount mount-point
Example:
# mount /export/home
19. Verify that the restored and mounted file system is available.
# ls mount-point
20. Reboot the server in multi-user mode

# init 6
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name 48
On old server: Find out LDAPRoot point zngdy0nm# more /opt/shasta/scs/bin/.scs.config # # This file was generated during SCS installation. # Please do not modify manually. # SCSHead=/opt/shasta/scs InstallDomainServer=yes InstallRegionServer=yes InstallMonitorServer=yes InstallPullServer=yes InstallLogServer=yes DomainServerIp=localhost RegionId=1 LDAPPath=/opt/shasta/ldap LDAPServerName=slapd-zngdy0nm LDAPServerIp=localhost LDAPServerPort=389 LDAPUsername="uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeR oot" LDAPPassword=admin LDAPRoot="uid=admin,ou=people,o=us.nortel.com" PullListenPort=4321 LogLogPort=4322 LogAccountPort=4323 RegionRootDir=/opt/shasta/scs DBAdminPassword=admin MaximumHeapSize=512 SCSBackup=/opt/shasta/scs/backup DBBackupTimeWait=150
GPRS/UMTS
634
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name LogUser=pmuser zngdy0nm# zngdy0nm# zngdy0nm# pwd /opt/shasta/ldap/shared/bin
Backup LDAP: zngdy0nm# cd /opt/shasta/ldap zngdy0nm# ls LICENSE.txt README.txt admin-serv adminacl admserv alias bin dist dsgw httpacl include install java lib manual plugins restart-admin setup shared slapd-zngdy0nm slapd-zngdy0nm1 start-admin startconsole stop-admin
uninstall
zngdy0nm# pwd /opt/shasta/ldap zngdy0nm# cd shared/bin zngdy0nm# ls NativeToAscii ldapdata admin_ip.pl ldapdelete ldapmodify ldapsearch modutil
zngdy0nm# ./ldapsearch -p 389 -T -b "uid=admin,ou=people,o=us.nortel.com" "objectclass=*" > ldap401backup
Backup solidDB: zngdy0nm# cd /opt/shasta/scs/bin zngdy0nm# ./SCSAdmin backup solidDB solid401_backup binDir is /opt/shasta/scs/bin head is /opt/shasta/scs configFile is /opt/shasta/scs/bin/.scs.config SOLID Remote Control v.03.51.0119 (C) Copyright Solid Information Technology Ltd 1993-2000 Exit by giving command: exit Backup started..
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and zngdy0nm# cd ../op*/so*/database/backup zngdy0nm# ls sol00021.log sol00022.log solid.db zngdy0nm# zngdy0nm# cd .. zngdy0nm# ls backup default scs401 scs401.tar solid solid401_backup solid.ini solmsg.out
Tar solidDB backup directory solid401_backup zngdy0nm# tar xvf solid401_backup.tar solid401_backup tar: solid401_backup.tar: No such file or directory zngdy0nm# tar cvf solid401_backup.tar solid401_backup a solid401_backup/ 0K a solid401_backup/solid.db 5232K a solid401_backup/sol00023.log 50K a solid401_backup/sol00024.log 46K a solid401_backup/solid.ini 2K a solid401_backup/solmsg.out 69K
Copy solid401_backup.tar and ldapdata to a temporary directory and FTP them to the new server.
ON NEW SERVER
Install LDAP server urc2y3pa# ./ns_server_setup.sh We could not find the following file(s) for installation: directory-4[1].16-export-us.sparc-sun-solaris2.6.tar or directory-4[1].16-domestic-us.sparc-sun-solaris2.6.tar Please specify the full path and file name of the Netscape Directory Server binaries: directory-4.16-export-us.sparc-sun-solaris2.6.tar ============================== Netscape Directory Server installation begins! GPRS/UMTS Upgrade Manual GGSN6.0
636
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name ============================== To accept the default machine name, press Enter key. [urc2y3pa]: To accept the default domain name, press Enter key. [us.nortel.com]: To accept the default IP address, press Enter key. [47.104.6.101]: Please specify the directory for Netscape Directory Server installation [/usr/netscape/ server4] :/opt/shasta/ldap Unpacking ... Start installation, please wait... Installing Netscape core components Installing Netscape Server Products Core Components Installing Netscape Directory Suite Installing Administration Services Extracting Netscape core components ... Extracting Netscape Server Products Core Components ... Extracting Netscape Core Java classes ... Extracting Java Runtime Environment ... Extracting Netscape Directory Server ... Extracting Netscape Directory Server Console ... Extracting Netscape Administration Server ... Extracting Administration Server Console ...
[slapd-urc2y3pa]: starting up server ... [slapd-urc2y3pa]: [16/Mar/2006:10:40:24 -0600] - Netscape-Directory/4.16 B01.300.2102 starting up [slapd-urc2y3pa]: [16/Mar/2006:10:40:26 -0600] - listening on all interfaces port 389 for LDAP requests [slapd-urc2y3pa]: [16/Mar/2006:10:40:26 -0600] - slapd started. Your new directory server has been started. Created new Directory Server Start Slapd Starting Slapd server configuration. Success Slapd Added Directory Server information to Configuration Server. Configuring Administration Server... Your parameters are now entered into the Administration Server database, and the Administration Server will be started.
Changing ownership to admin user root... Setting up Admininistration Server Instance...
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and Configuring Administration Tasks in Directory Server... Configuring Global Parameters in Directory Server... Netscape-Administrator/4.2 B2001.300.0126 startup: listening to http://urc2y3pa, port 23611 as root warning: daemon is running as super-user Info: Cache expiration set to 600 seconds Info: Cache expiration set to 600 seconds Installation is complete. See /opt/shasta/ldap/setup/setup.log for possible errors. Schema update, please wait... Info: Cache expiration set to 600 seconds Netscape-Administrator/4.2 B2001.300.0126 startup: listening to http://urc2y3pa, port 23611 as root warning: daemon is running as super-user Complete schema update Do you want to enable the LDAP autostart and watchdog processes (y/n)? [n]: y Where would you like to install these files? [/opt/shasta/scs]: /opt/shasta/scs/bin Please provide the LDAP path [/opt/shasta/ldap]: Please provide the LDAP port number [389]:
urc2y3pa# pwd /opt/shasta/scs
From the LDAP Console, create LDAPRoot point - set the root point to a value not matching the old server root point. urc2y3pa# cd ../ldap urc2y3pa# ./startconsole & [1] 13107
Example: New LDAPRoot: uid=ldap,ou=people,o=us.nortel.com Old LDAPRoot: uid=admin,ou=people,o=us.nortel.com Install SCS urc2y3pa# cd ../scs
GPRS/UMTS
638
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name urc2y3pa# ./setup.sh /opt/shasta/scs/install/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled This program will install Shasta Service Creation System. Version SCS GGSNS4.0.1_SCS4.0.1(4) ********************************************************************* * SCS 4.0 requires LDAP 4.16. If you are not running 4.16 Please * upgrade the LDAP server before starting the SCS Installation * Please refer to the SCS installation document and SCS Release * Notes for details on upgrading the Directory Server. * * * *
********************************************************************* Do you want to continue (Y/N)? [N]: y You have the following options: (C) Create a new SCS Server installation (U) Upgrade the current SCS Server (A) Abort this installation Please enter (C)reate, (U)pgrade or (A)bort? [A]: c Please specify the directory for the new SCS installation [/opt/shasta/scs]: SCS will be installed in /opt/shasta/scs. Checking the available space ... Required space 61440 Kbytes. Available space 34296666 Kbytes. Found enough space to install SCS.
Copying the required files ... Here are the possible server installation components for this machine: (1) SCS Domain Server (with SNMP Proxy) (2) SCS Region Server (with Monitor Server and SCS Trap Daemon) (3) SCS Pull Server (4) SCS Log Server Please select the server(s) to install (separated by spaces) [1 2 3 4]: You have selected the following server(s) to install: (1) SCS Domain Server (with SNMP Proxy) (2) SCS Region Server (with Monitor Server and SCS Trap Daemon) (3) SCS Pull Server (4) SCS Log Server Here are the possible deployment profile options:
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and (1) Large Scale Deployment, requires 1792M of virtual memory (for region with 15-20 devices, or multiple region servers) (2) Medium Scale Deployment, requires 896M of virtual memory (for single region server with 7-10 devices) (3) Small Scale Deployment, requires 448M of virtual memory (1 or 2 devices with limited number of subscribers)
This machine currently has 11297M of virtual memory available. Please select deployment profile [1]: Please provide this Region ID [1]:
Please provide the listening port for Pull Server [4321]: Please provide the logging port for Log Server [4322]: Please provide the accounting port for Log Server [4323]: We need to install Solid database server on this host. Please provide password for the SCS database users [admin]:
Please provide path for the SCS backup [/opt/shasta/scs/backup]:
checking if snmp default port 5001 has been used, please wait ...
snmp prxy will use port 5001.
checking if TrapDaemon default port 5002 has been used, please wait ...
TrapDaemon will use port 5002. Is LDAP server installed and running on this host (y/n)? [n]: y Please provide the LDAP path : /opt/shasta/ldap
We need to collect the LDAP information for the Domain/Pull/Log Server.
/opt/shasta/ldap is LDAP path slapd-urc2y3pa is LDAP server Please provide the LDAP Server IP address [localhost]: Please provide the LDAP Server port [389]: Please provide the LDAP username
GPRS/UMTS
640
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name [uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot]: Please provide the LDAP password [admin]: Please provide the LDAP root [uid=ushasta,ou=people,o=us.nortel.com]: uid=ldap,ou=people,o=us.nortel.com Do you want to run SCS server processes at boot time? (Y)es or (N)o? [N]: y
Installing the Solid Database Server ... [1] 13358 Start the solid server ... Solid Server is running ... Creating database tables for the SCS Domain Server ... 16-Mar-2006 10:46:01 292 INFO ldap.connection.info: localhost,389,uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot,u id=ushasta,ou=people,o=us.nortel.com 16-Mar-2006 10:46:01 463 INFO sni.7: Created a new LDAP connection... 1 Updating ISP: any Updating ISP: li_default_isp Adding Patch Server information in SCS Domain Server database ... Enabling tftp - tftp already enabled, no changes made Creating database tables for the SCS Region Server ... Adding Pull Server information in SCS Domain Server database ... Adding Log Server information in SCS Domain Server database ...
We have created the required SCS database tables. Now we will shutdown the Solid database server. Stopping Solid Database Server:.Stopped [1] + Done /opt/shasta/scs/opt/solidSolaris/bin/solid -f -c ...
LDAP schema files updated successfully Now stopping and restarting LDAP server slapd-urc2y3pa ...
To generate CSV formatted accounting data, a user id must be designated as the owner of the generated files. It is recommended that the user id not be the root user. The ownership of any existing CSV formatted accounting data file will also be changed to this user id.
Do you want to designate a user id for the CSV formated data.? 411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and (Y)es or (N)o? [Y]:
Please enter a user id. [pmuser]: The user id, pmuser, already exists and will be used by the SCS Log Server process for CSV generated files.
Please enter the number of days the individual CSV files should be preserved before the SCSCleanLogcsv.ksh script removes them. [4]: Do you want to install the SCS GGSNS4.0.1_SCS4.0.1(4) SCS Corba Server? (Y)es or (N)o? [Y]: Please enter full path and name of SCS GGSNS4.0.1_SCS4.0.1(4) Corba server tar file: / opt/shasta/scs/scs_corba_server.tar Extracting the Corba files, Please Wait... This program will install SCS Corba Server version SCS GGSNS4.0.1_SCS4.0.1(4) Please specify the directory for SCS Corba server installation [/opt/shasta/scs]: SCS Corba Server will be installed in /opt/shasta/scs. Found Domain server installed. New SCS Corba server version matches installed SCS version. Continuing... SCS Corba Server will be installed in /opt/shasta/scs. Checking the available space...
Required space 61440 Kbytes. Available space 34217122 Kbytes. Found enough space to install SCS Corba Server. Please specify the Domain Server IP adress [localhost]: Please specify the host IP address for the ORB [default]: Please specify the IIOP port, where server listens for Corba requests [0]: Copying the required files...... SCS Corba Server is now installed. You can use /opt/shasta/scs/bin/SCSCorbaServer to run SCS Corba Server. Cleaning up ... The installation logs are saved in /opt/shasta/scs/lib/install/*.log. The following SCS server(s) are currently installed on this machine: Version SCS GGSNS4.0.1_SCS4.0.1(4)
GPRS/UMTS
642
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name SCS Domain Server (LDAP Server IP = localhost) SCS Region Server (Region ID = 1) SCS Monitor Server SCS Pull Server (Listening Port = 4321) SCS Log Server (Logging Port = 4322, Accounting Port = 4323) SCS CORBA Server You can use '/opt/shasta/scs/bin/SCSAdmin start' to run SCS Server.
urc2y3pa# cd bin urc2y3pa# ./SCSAdmin start
/opt/shasta/scs/bin/SCSWatch-disable: SCSWatch is already disabled /opt/shasta/scs/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled /opt/shasta/scs/bin/SCSDiskUsageMonitor-disable: SCSDiskUsageMonitor is already disabled /opt/shasta/scs/bin/SCSCleanXmlExportFiles-disable: SCSCleanXmlExportFiles is already disabled [1] 13819 Starting Solid Database Server:.Started [2] 13837 Starting SCS Daemon:..Started [3] 13872 Starting SCS Domain server:.....Started [4] 13900 Starting SNMP Proxy:.Started [5] 13909 Starting SCS CORBA Server:......Started [6] 13928 Starting SCS Region server:.....Started [7] 13956 Starting SCS Monitor server:.....Started [8] 13984 Starting SCS Trap daemon:.....Started [9] 14013 Starting SCS Pull Server:...Started [10] 14052 Starting SCS Log Server:..Started 411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and ------------------------------------------Shasta Service Creation System Server Version SCS GGSNS4.0.1_SCS4.0.1(4) ------------------------------------------Adding SCSCleanLogcsv first time Added SCSCleanLogcsv to crontab Adding SCSWatch to Crontab for first time. Added SCSWatch to crontab Adding SCSDiskUsageMonitor first time Added SCSDiskUsageMonitor to crontab Adding SCSCleanXmlExportFiles first time Added SCSCleanXmlExportFiles to crontab urc2y3pa# pwd /opt/shasta/scs/bin
Backup directory with SCS and LDAP backup files from old server urc2y3pa# ls /tmp/backup412 ldap401backup solid401_backup.tar
Copy LDAP backup file to <LDAP_ROOT>/shared/bin urc2y3pa# cd /opt/shasta/ldap/shared/bin urc2y3pa# cp /tmp/backup412/ldap401backup urc2y3pa# ls NativeToAscii ldap401backup ldapmodify admin_ip.pl urc2y3pa# urc2y3pa# urc2y3pa# ls NativeToAscii ldap401backup ldapmodify admin_ip.pl ldapdelete ldapsearch modutil ldapdelete ldapsearch modutil
Restore LDAP urc2y3pa# ./ldapmodify -p 389 -D "cn=Directory Manager" -w password -c -a -f ldap401backup adding new entry uid=admin,ou=People, o=us.nortel.com adding new entry dc=ISPs,uid=admin,ou=people,o=us.nortel.com
GPRS/UMTS
644
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name adding new entry dc=Areas,uid=admin,ou=people,o=us.nortel.com adding new entry o=any,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=DomainGroups,o=any,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=DomainGroups,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Customers,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Isp,o=Customers,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=People,o=Isp,o=Customers,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.norte l.com adding new entry ou=Sites,o=Isp,o=Customers,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.nortel.c om adding new entry ou=Templates,o=Isp,o=Customers,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.n ortel.com adding new entry o=Realms,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=li_default_isp,o=Realms,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.nortel.c om adding new entry dc=li_default_isp,dc=li_default_isp,o=Realms,o=li_default_isp,dc=ISPs,uid=admin,ou=pe ople,o=us.nortel.com adding new entry dc=region1,dc=Areas,uid=admin,ou=people,o=us.nortel.com adding new entry ntlShastaDeviceName=Shasta90,dc=region1,dc=Areas,uid=admin,ou=people,o=us.nortel.c om adding new entry o=isp-consumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=People,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=Sites,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Realms,o=isp-
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and consumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=isp-consumer,o=Realms,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=isp-consumer,dc=isp-consumer,o=Realms,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=DomainGroups,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=isp-cda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Customers,o=isp-cda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=People,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=Sites,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Realms,o=isp-cda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=isp-cda,o=Realms,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=isp-cda,dc=isp-cda,o=Realms,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=DomainGroups,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=isp-diameter,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Customers,o=ispdiameter,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Isp,o=Customers,o=ispdiameter,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=People,o=Isp,o=Customers,o=ispdiameter,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=Sites,o=Isp,o=Customers,o=ispdiameter,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=Templates,o=Isp,o=Customers,o=ispdiameter,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Realms,o=ispdiameter,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=isp-diameter,o=Realms,o=ispdiameter,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=isp-diameter,dc=isp-diameter,o=Realms,o=ispdiameter,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=DomainGroups,o=ispdiameter,dc=ISPs,uid=admin,ou=people,o=us.nortel.com GPRS/UMTS Upgrade Manual GGSN6.0
646
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name adding new entry o=isp-gn,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Customers,o=isp-gn,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Isp,o=Customers,o=ispgn,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=People,o=Isp,o=Customers,o=ispgn,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=Sites,o=Isp,o=Customers,o=ispgn,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=Templates,o=Isp,o=Customers,o=ispgn,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Realms,o=isp-gn,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=isp-gn,o=Realms,o=ispgn,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=isp-gn,dc=isp-gn,o=Realms,o=ispgn,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=DomainGroups,o=ispgn,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=isp-ga,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Customers,o=isp-ga,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Isp,o=Customers,o=ispga,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=People,o=Isp,o=Customers,o=ispga,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=Sites,o=Isp,o=Customers,o=ispga,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ou=Templates,o=Isp,o=Customers,o=ispga,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Realms,o=isp-ga,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=isp-ga,o=Realms,o=ispga,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=isp-ga,dc=isp-ga,o=Realms,o=ispga,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=DomainGroups,o=ispga,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-web,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-web-tsh,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-wap,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-wap-tsh,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and adding new entry userid=st-trialwap,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-trial,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-opitest,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-mms,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-mms-tsh,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-blackberry,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-poc,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-trialvvm,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-tsnet-mi,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-cda,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-cda-nmc,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-mylan,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-mylan-tsh,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-ferrari,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-saiwa,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-galbani,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-dhl,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-ras,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-iss,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-deloitte,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-binda,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-mcd,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com GPRS/UMTS Upgrade Manual GGSN6.0
648
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name adding new entry userid=st-csi,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-aia,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-gd,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-smc,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-chiesigroup,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-snam,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-roche1,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-beretta,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-bconnect,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-yomo,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-gpi,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-kone,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-kpmg,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-bpm,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-gsk,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-unicredito,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-loreal,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-antalis,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-omnitel,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-crf,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-nestle,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-tntge,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and adding new entry userid=st-elsag,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-lloydadriatico,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-nav,ou=Templates,o=Isp,o=Customers,o=ispconsumer,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-eni,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-vidas,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-csp,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-mediaw,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-principe,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-autogerma,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-118bogprs,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-roche,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-ferrero,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-atr,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-lorealpdl,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-sanpellegrino,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-bykgul,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-aemto,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-agos,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-ivrimi,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-egalbani,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-mondialassistance,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-voto3,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com GPRS/UMTS Upgrade Manual GGSN6.0
650
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name adding new entry userid=st-sanpaoloimi,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-constriv,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-albacomtest,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-partesa,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-danieli,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=st-quidnovi,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=as-miipc01-mylan,ou=Sites,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=as-miipc01-cda,ou=Sites,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry shastaType=LDAP_REACH_ADDR+shastaId=1,userid=as-miipc01cda,ou=Sites,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=as-miipc01-cda-nmc,ou=Sites,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry shastaType=LDAP_REACH_ADDR+shastaId=3,userid=as-miipc01cda-nmc,ou=Sites,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry userid=as-miipc01-mylan-tsh,ou=Sites,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry shastaType=LDAP_REACH_ADDR+shastaId=4,userid=as-miipc01mylan-tsh,ou=Sites,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry shastaType=LDAP_REACH_ADDR+shastaId=5,userid=as-miipc01mylan,ou=Sites,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry ntlShastaDeviceName=ssg115,dc=region1,dc=Areas,uid=admin,ou=people,o=us.nortel.com
urc2y3pa# pwd /opt/shasta/ldap/shared/bin urc2y3pa# urc2y3pa# urc2y3pa# cd ../../ Verify LDAPRoot point has been created urc2y3pa# ./startconsole & [1] 14382 411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and urc2y3pa# pwd /opt/shasta/ldap [1] + Done urc2y3pa# ls LICENSE.txt README.txt admin-serv adminacl admserv alias bin dist dsgw httpacl include install java lib manual plugins start-admin ./startconsole
restart-admin startconsole setup shared stop-admin uninstall
slapd-urc2y3pa
urc2y3pa# cd ..
urc2y3pa# cd /tmp urc2y3pa# cd backup412 urc2y3pa# ls ldap401backup solid401_backup.tar
urc2y3pa# tar xvf solid401_backup.tar x solid401_backup, 0 bytes, 0 tape blocks x solid401_backup/solid.db, 5357568 bytes, 10464 tape blocks x solid401_backup/sol00023.log, 51200 bytes, 100 tape blocks x solid401_backup/sol00024.log, 47104 bytes, 92 tape blocks x solid401_backup/solid.ini, 1588 bytes, 4 tape blocks x solid401_backup/solmsg.out, 70165 bytes, 138 tape blocks urc2y3pa# ls ldap401backup solid401_backup solid401_backup.tar
Create SCS SOLID database backup directory urc2y3pa# cd solid401_backup urc2y3pa# mkdir -p /opt/shasta/scs/opt/solidSolaris/database/backup
Copy SCS SOLID database files to SCS SOLID database backup directory urc2y3pa# cp * /opt/shasta/scs/opt/solidSolaris/database/backup Restore SCS SOLID database urc2y3pa# cd /opt/shasta/scs/bin urc2y3pa# ./SCSAdmin restore solidDB
GPRS/UMTS
652
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name Edit /opt/shasta/scs/bin/.scs.config and modify LDAPRoot to match the old server root point Current LDAPRoot: uid=ldap,ou=people,o=us.nortel.com Modify LDAPRoot to: uid=admin,ou=people,o=us.nortel.com
urc2y3pa# more .scs.config # # This file was generated during SCS installation. # Please do not modify manually. # SCSHead=/opt/shasta/scs InstallDomainServer=yes InstallRegionServer=yes InstallMonitorServer=yes InstallPullServer=yes InstallLogServer=yes DomainServerIp=localhost RegionId=1 LDAPPath=/opt/shasta/ldap LDAPServerName=slapd-urc2y3pa LDAPServerIp=localhost LDAPServerPort=389 LDAPUsername="uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeR oot" LDAPPassword=admin LDAPRoot="uid=admin,ou=people,o=us.nortel.com" PullListenPort=4321 LogLogPort=4322 LogAccountPort=4323 RegionRootDir=/opt/shasta/scs DBAdminPassword=admin MaximumHeapSize=512 SCSBackup=/opt/shasta/scs/backup DBBackupTimeWait=150 LogUser=pmuser urc2y3pa#
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and Restart SCS server processes urc2y3pa# ./SCSAdmin restart Solid Database Server is running SCS Daemon is running SCS Domain Server is running SNMP Proxy is running SCS Region Server is running SCS Monitor Server is running SCS Trap Daemon is running SCS Pull Server is running SCS Log Server is running SCS CORBA Server is running
Some server processes are already running. Please choose to (R)estart or (Q)uit: r /opt/shasta/scs/bin/SCSWatch-disable: SCSWatch is already disabled /opt/shasta/scs/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled Removed SCSDiskUsageMonitor from crontab Removed SCSCleanXmlExportFiles from crontab [1] 15288 Stopping SCS CORBA Server:.[1] + Done .Stopped [1] 15305 Stopping SCS Log Server:.[1] + Done .Stopped [1] 15339 Stopping SCS Pull Server:.[1] + Done .Stopped [1] 15356 Stopping SCS Trap Daemon:.[1] + Done .Stopped [1] 15373 Stopping SCS Monitor Server:.[1] + Done Stopped [1] 15384 Stopping SCS Region Server:.[1] + Done /opt/shasta/scs/opt/jre/bin/java -cp ... /opt/shasta/scs/opt/jre/bin/java -cp ... /opt/shasta/scs/opt/jre/bin/java -cp ... /opt/shasta/scs/opt/jre/bin/java -cp ... /opt/shasta/scs/opt/jre/bin/java -cp ... /opt/shasta/scs/opt/jre/bin/java -cp ...
GPRS/UMTS
654
Appendix G: Example Capture of Migrating SCS to new server with different IP and same domain name Stopped Stopping SNMP Proxy:.Stopped [1] 15409 Stopping SCS Domain Server:.[1] + Done Stopped [1] 15420 Stopping SCS Daemon:.[1] + Done .Stopped Stopping Solid Database Server:.Stopped [1] 15478 Starting Solid Database Server:.Started [2] 15496 Starting SCS Daemon:..Started [3] 15515 Starting SCS Domain server:........Started [4] 15553 Starting SNMP Proxy:Started [5] 15559 Starting SCS CORBA Server:......Started [6] 15578 Starting SCS Region server:.....Started [7] 15624 Starting SCS Monitor server:.....Started [8] 15653 Starting SCS Trap daemon:.....Started [9] 15682 Starting SCS Pull Server:...Started [10] 15705 Starting SCS Log Server:..Started ------------------------------------------Shasta Service Creation System Server Version SCS GGSNS4.0.1_SCS4.0.1(4) ------------------------------------------Adding SCSCleanLogcsv first time Added SCSCleanLogcsv to crontab Adding SCSWatch to Crontab for first time. /opt/shasta/scs/opt/jre/bin/java -cp ... /opt/shasta/scs/opt/jre/bin/java -cp ...
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks ConfidentialAppendix G: Example Capture of Migrating SCS to new server with different IP and Added SCSWatch to crontab Adding SCSDiskUsageMonitor first time Added SCSDiskUsageMonitor to crontab Adding SCSCleanXmlExportFiles first time Added SCSCleanXmlExportFiles to crontab urc2y3pa#
End of migration procedure
GPRS/UMTS
656
Appendix H: Example capture of iPlanet server uninstallation
Appendix H: Example capture of iPlanet server uninstallation 49

Here is an example iPlanet uninstall capture:
# cd /opt/shasta/iplanet # ./uninstall Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------The following are the iPlanet components currently installed on your machine: Components with a number in () contain additional subcomponents which you can select using subsequent screens. Server Core Components (3) iPlanet Directory Suite (2) Administration Services (2) Select the components you wish to uninstall (default: all) [All]: (hit enter) Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------The following are the Server Core Components components currently installed on your machine: Components with a number in () contain additional subcomponents which you can select using subsequent screens. 1. Server Core Components 2. Core Java classes 3. Java Runtime Environment Specify the components you wish to uninstall [1, 2, 3]: (hit enter) CSun-Netscape Alliance DiPlanet Server Products Installation/Uninstallation --------------------------------------------------------------------------------
411-5221-309
Standard
06.30 March 10, 2010
657
The following are the iPlanet Directory Suite components currently installed on your machine: Components with a number in () contain additional subcomponents which you can select using subsequent screens. iPlanet Directory Server 2. iPlanet Directory Server Console Specify the components you wish to uninstall [1, 2]: (hit enter) Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -----------------------------------------------------------------------------The following are the Administration Services components currently installed on your machine: Components with a number in () contain additional subcomponents which you can select using subsequent screens. 1. iPlanet Administration Server 2. Administration Server Console Specify the components you wish to uninstall [1, 2]: (hit enter) Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation --------------------------------------------------------------------------------
The iPlanet Directory Server at ldap://zrc2s0q4.us.nortel.com:395/o=NetscapeRoot is down, unreachable, or the configured LDAP URL is not valid. It is recommended that you fix the problem with the registry then perform uninstallation again. To quit uninstallation, type CTRL-C. Alternatively, you can enter the correct URL or proceed with local uninstallation of the selected servers.
Would you like to continue with local uninstallation? [No]: yes

Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation
GPRS/UMTS
658
-------------------------------------------------------------------------------Uninstalling Administration Server Console... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------Uninstalling Administration Server Console... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------Uninstalling Administration Server Console... Uninstalling iPlanet Administration Server... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------Uninstalling Administration Server Console... Uninstalling iPlanet Administration Server... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------Uninstalling Administration Server Console... Uninstalling iPlanet Administration Server... Uninstalling iPlanet Directory Server Console... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------Uninstalling Administration Server Console... Uninstalling iPlanet Administration Server... Uninstalling iPlanet Directory Server Console... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------411-5221-309 Standard 06.30 March 10, 2010
659
Uninstalling Administration Server Console... Uninstalling iPlanet Administration Server... Uninstalling iPlanet Directory Server Console... Uninstalling iPlanet Directory Server... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------Uninstalling Administration Server Console... Uninstalling iPlanet Administration Server... Uninstalling iPlanet Directory Server Console... Uninstalling iPlanet Directory Server... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------Uninstalling Administration Server Console... Uninstalling iPlanet Administration Server... Uninstalling iPlanet Directory Server Console... Uninstalling iPlanet Directory Server... Uninstalling Java Runtime Environment... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------Uninstalling Administration Server Console... Uninstalling iPlanet Administration Server... Uninstalling iPlanet Directory Server Console... Uninstalling iPlanet Directory Server... Uninstalling Java Runtime Environment... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation -------------------------------------------------------------------------------Uninstalling Administration Server Console... GPRS/UMTS Upgrade Manual GGSN6.0
660
Appendix H: Example capture of iPlanet server uninstallation Uninstalling iPlanet Administration Server... Uninstalling iPlanet Directory Server Console... Uninstalling iPlanet Directory Server... Uninstalling Java Runtime Environment... Uninstalling Core Java classes... Sun-Netscape Alliance iPlanet Server Products Installation/Uninstallation
-------------------------------------------------------------------------------Uninstalling Administration Server Console... Uninstalling iPlanet Administration Server... Uninstalling iPlanet Directory Server Console... Uninstalling iPlanet Directory Server... Uninstalling Java Runtime Environment... Uninstalling Core Java classes... Sun-Netscape Alliance iPlanet Serve <end of iPlanet uninstall capture>
Remove iPlanet directory # cd /opt/shasta # \rm -rf iplanet
411-5221-309
Standard
06.30 March 10, 2010
Appendix I: Disk Check for SCS for non-mirrored servers 661
Appendix I: Disk Check for SCS for nonmirrored servers 50

Here are the steps to verify the hard disk on the Solaris server for nonmirrored servers are clean. Pre-requisites: Depending on the Solaris installation: Solaris 8 (Disk 1) or Solaris 9 (Disk 1) 1. Login in to the server as root 2. Verify the version of Solaris that is running on the server # uname -rm Example:
# uname -rm 5.9 sun4u
This indicates the server is running Solaris 9

This indicates the server is running Solaris 8 3. Insert the appropriate Solaris installation CD (Disk 1) 4. Reboot the server from the CDROM in single user mode
# sync; sync; sync # init 0
5. At the Solaris Open Boot Prompt (ok prompt) and boot from Solaris OS CDROM Disk 1 into single usermode.
GPRS/UMTS
662
Appendix I: Disk Check for SCS for non-mirrored servers {6} ok boot cdrom -rs
Boot device: /pci@8,700000/scsi@1/disk@6,0:f File and args: -rs ... ... INIT: SINGLE USER MODE #
6. Find out all the mounted and unmounted partitions. Refer to SCS Disk Partition Table for details of the partitions. 7. Run the system command fsck -m /dev/rdsk/<disk_partition> to find out if the partition has no errors Note: Dont run fsck for swap partition
# fsck -m /dev/rdsk/<disk_partition>
Example:
# fsck -m /dev/rdsk/c1t0d0s7 ** /dev/rdsk/c1t0d0s7 ufs fsck: sanity check: /dev/rdsk/c1t0d0s7 okay
If the sanity check returns okay proceed to the next partition till all partitions are checked and okay. If fsck -m returns errors or file system inconsistencies, correct the disk error by running fsck -y. After fsck exits, run fsck -m and make sure the sanity is okay. You may need to run fsck -y and fsck -m multiple times if the disk is badly corrupted.
# fsck -m /dev/rdsk/c1t0d0s7 If the check returns errors: # fsck -y /dev/rdsk/c1t0d0s7 # fsck -m /dev/rdsk/c1t0d0s7 Verify the sanity check is okay
If fsck -m returns errors and fsck -y is unable to correct it, then the disk may be badly corrupted. You will need to perform a Full Server Restore using the latest tape backup.
411-5221-309
Standard
06.30 March 10, 2010
Appendix I: Disk Check for SCS for non-mirrored servers 663
8. After completing the disk check on all the required partitions, reboot the server to multi-user mode. # init 6
End of procedure Disk Check for SCS for mirrored server
GPRS/UMTS
664
Appendix J: Disk Check for SCS for mirrored server
Appendix J: Disk Check for SCS for mirrored server

Pre-requisites: Depending on the Solaris installation: Solaris 8 (Disk 1) or Solaris 9 (Disk 1) 1. Login in to the server as root 2. Verify the version of Solaris that is running on the server # uname -rm Example:
51
Here are the steps to verify the hard disk on the Solaris server for mirrored servers are clean.

3. Insert the appropriate Solaris installation CD (Disk 1) 4. Reboot the server from the CDROM in single user mode
# sync; sync; sync # init 0
5. At the Solaris Open Boot Prompt (ok prompt)

{6} ok boot cdrom -rs
411-5221-309
Standard
06.30 March 10, 2010
Appendix J: Disk Check for SCS for mirrored server 665
Boot device: /pci@8,700000/scsi@1/disk@6,0:f File and args: -rs ... ... INIT: SINGLE USER MODE #
6. Find out all the mounted and unmounted partitions. Refer to Disk Mirroring Mapping for details of the partitions 7. Run the system command fsck -m /dev/rdsk/<disk_partition> to find out if the partition has no errors Note: Dont run fsck for swap partition
# fsck -m /dev/rdsk/<disk_partition>
Example:
# fsck -m /dev/rdsk/c1t0d0s7 ** /dev/rdsk/c1t0d0s7 ufs fsck: sanity check: /dev/rdsk/c1t0d0s7 okay
If the sanity check returns okay proceed to the next partition till all partitions are checked and okay. If fsck -m returns errors or file system inconsistencies, correct the disk error by running fsck -y. After fsck exits, run fsck -m and make sure the sanity is okay. You may need to run fsck -y and fsck -m multiple times if the disk is badly corrupted.
# fsck -m /dev/rdsk/c1t0d0s7 If the check returns errors: # fsck -y /dev/rdsk/c1t0d0s7 # fsck -m /dev/rdsk/c1t0d0s7 Verify the sanity check is okay
8. After completing the disk check on all the required partitions, reboot the server to multi-user mode. # init 6
GPRS/UMTS
666
Appendix K: Disk Analysis For Non-Mirrored Servers
Appendix K: Disk Analysis For NonMirrored Servers
52
The section explains the steps to analyze the SCS server disk availablity, disk usage, free space, identifying partitions for Solaris 9 and steps to partition a new disk.
Disk Space Analysis

1. Log in to the SCS server as root
52
2. At the command prompt, run df -k and make a note of the disk usage. Note, the size displayed in df -k are in kilobytes. Here is an example. The bolded text in the example indicate the mounted partitions. Make a note of the Filesystem column that starts with /dev/dsk/cvtwdxsz and the corresponding last column Mounterd On
# df -k Filesystem /dev/dsk/c1t0d0s0 /proc mnttab fd /dev/dsk/c1t0d0s5 swap swap /dev/dsk/c1t1d0s0 /dev/dsk/c1t0d0s7 kbytes used avail capacity 10086988 494516 9491603 5% 0 0 0 0% 0 0 0 0% 0 0 0 0% 20174761 42556 19930458 1% 16784376 88 16784288 1% 16803576 19288 16784288 1% 70477018 5911572 63860676 9% 20174761 20025 19952989 1% Mounted on / /proc /etc/mnttab /dev/fd /var /var/run /tmp /opt /export/home
3. Record the output of cat /etc/vfstab. Physical partition for swap partition is visible only in file /etc/vfstab.
# cat /etc/vfstab #device device mount FS fsck mount #to mount to fsck point type pass at options # fd /dev/fd fd no /proc /proc proc no /dev/dsk/c1t0d0s1 swap no /dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 /dev/dsk/c1t0d0s5 /dev/rdsk/c1t0d0s5 /var ufs 1 /dev/dsk/c1t0d0s7 /dev/rdsk/c1t0d0s7 /export/home ufs yes /dev/dsk/c1t1d0s0 /dev/rdsk/c1t1d0s0 /opt ufs 2 swap /tmp tmpfs yes mount boot
no no 2 yes
411-5221-309
Standard
06.30 March 10, 2010
667
4. From df -k, make a note of the Filesystem, kbytes (this is the total disk size in KB) and avail columns. swap partition on the current version of Solaris can be reused and may not require additional space. See Swap memory space allocation on page 228. Fill in Table 33, Partition Information for Non-Mirrored Servers, on page 667. Users can save this information in a MS Excel spreadsheet.
Table 33 Partition Information for Non-Mirrored Servers Partition (Mounted on column) swap Disk Partition (Filesystem column) taken from cat / etc/vfstab Total Partition Size (kbytes column) Available Partition Space (avail column)
Table 34 Example of Partition Information for Non-Mirrored Servers Partition (Mounted on column) Disk Partition (Filesystem column) Total Partition Size (kbytes column) Available Partition Space (avail column)
swap
/dev/dsk/c1t0d0s1 taken from cat / etc/vfstab /dev/dsk/c1t0d0s0 /dev/dsk/c1t0d0s5 /dev/dsk/c1t1d0s0 /dev/dsk/c1t0d0s7 10086988 (10.08 GB) 2017476 (2.01 GB) 70477018 (70.47 GB) 20174761 (20.17 GB) 9.582 GB 19.973 GB 64.135 GB 19.973 GB
/ /var /opt /export/home
GPRS/UMTS
668
Recommendations: For SCS server upgrade, depending on the size of the SCS and LDAP (or iPlanet) database size, free disk space must be available in the partition that has the current SCS server installation. During SCS rolling upgrade, the upgrade process makes a copy of the current SCS directory to the new SCS 6.0 directory and a new instance for LDAP is created in the current LDAP directory. This means the at lest twice the amount of disk space currently used by SCS and LDAP plus 3 GB free space is required to perform SCS 6.0 upgrade. To make SCS server backups simple, SCS 6.0 is recommended to be installed in the same partition as the current SCS and LDAP installation. The additional 3 GB is a conservative estimate and is assigned for SCS 6.0 upgrade and room for database and log directory usage increase over a period of time.
Identifying Unmounted Partitions required for Solaris 9 Boot Environment (BE) Creation 52
Note: Please skip this step if the SCS server has already been upgraded to Solaris 9 Solaris 9 upgrade on the current Solaris 8 server is done by a process called Live Upgrade. This process requires unmounted partitions on the SCS server. The unmounted partitions can be assigned from: Server has mounted disks available Unmounted partitions on the currently mounted disk. This case is usually rare. Recommendations: Identifying an unmounted disk would be the best option and chances of overwriting information on the currently mounted disk can be avoided. Steps to identify unmounted disk on the SCS server Understanding Sun hard disk naming convention Perform df -k or /etc/vfstab on your server. You will notice the Filesystem name is similar to cvtwdxsz. c - Disk Controller / v - Controller number t - Physical Bus Target / w - Target number d - Drive / x - Drive number
411-5221-309 Standard 06.30 March 10, 2010
669
s - Disk slice / z - Slice number With format, explained below, we can identify the total number of hard disks available on the server. With df -k and /etc/vfstab explained below, make a note of the disks currently used by the system. 1. Run format < /dev/null command to identify the number of disks available on the server.
Here is an example: # format < /dev/null Searching for disks...done
AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010183a01,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010186a81,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b0b1,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0 6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0 10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 Specify disk (enter its number):
2. From df -k identify the disks mounted on the server.

# df -k Here is an example: # df -k
Filesystem /dev/dsk/c1t0d0s0 /proc mnttab fd /dev/dsk/c1t0d0s5 kbytes 10086988 0 0 0 20174761 used avail capacity Mounted on 494516 9491603 5% / 0 0 0% /proc 0 0 0% /etc/mnttab 0 0 0% /dev/fd 42652 19930362 1% /var
GPRS/UMTS
670

swap swap /dev/dsk/c1t1d0s0 /dev/dsk/c1t0d0s7 home

1% 1% 9% 1% /var/run /tmp /opt /export/
16783776 88 16783688 16803128 19440 16783688 70477018 5911760 63860488 20174761 20025 19952989
3. From the above steps capturing format </dev/null and df -k, identify the disks that are not mounted. Filesystem (first column) in df -k output indicate the disk partition that are mounted for a specific file system (say /, /usr, /var, etc) From the above df -k example:
/ - /dev/dsk/c1t0d0s0 /var - /dev/dsk/c1t0d0s5 /opt - /dev/dsk/c1t1d0s0 /export/home - /dev/dsk/c1t0d0s7
Make a note of the disks with format < /dev/null that are not listed in df -k
From the example captured so far: Disks c1t0d0 and c1t1d0 are mounted Other disks on the server are unmounted and can be used for creating Solaris 9 Boot Environment.
Disk Partitioning of an Unmounted Disk 4. Pick an unused disk and partition it according to the current mounted partitions. a. Run df -k and find out the disks partitions that are mounted. Here is an example of df -k:
# df -k Filesystem /dev/dsk/c1t0d0s0 /proc mnttab fd /dev/dsk/c1t0d0s5 swap swap /dev/dsk/c1t1d0s0 /dev/dsk/c1t0d0s7 home kbytes used avail capacity Mounted on 10086988 494516 9491603 5% / 0 0 0 0% /proc 0 0 0 0% /etc/mnttab 0 0 0 0% /dev/fd 20174761 42652 19930362 1% /var 16783776 88 16783688 1% /var/run 16803128 19440 16783688 1% /tmp 70477018 5911760 63860488 9% /opt 20174761 20025 19952989 1% /export/
This example indicates: Disk

c1t0d0s0 c1t0d0s5 c1t1d0s0 c1t0d0s7
Partition
/
/var
/opt /export/home
411-5221-309
Standard
06.30 March 10, 2010
671
This indicates two disks c1t0d0 and c1t1d0 are used.
Recommendation: A good rule of thumb will be to find the same number of unmounted disks to match with the number of disks that are currently mounted. In cases where same number of unmounted disks cannot be identified, then partitioning of the unmounted disks need to be adjusted so that Solaris 9 Boot Environment can be created. Note on Space Requirement: Solaris 9 Live Upgrade commands make a copy of the existing mounted partitions into the unmounted partitions. Then the unmounted partitions are upgraded to Solaris 9. Setting the size limit on the unmounted disk partition depends on the amount of disk space currently used by the server. An equal amount of disk space used by the current partition plus at least 3 to 5 GB per mounted disk partition will be needed to perform Solaris 9 live upgrade. Please refer to Partition Information for Non-Mirrored Servers on page 667 for the current disk usage. 5. After identifying the unmounted disk/ disks on the server, re-partition the disk using format. Important Note: Please use caution when running format. To safe guard data, mounted disk partitions cannot be formatted.
Here is a capture when trying to partition an already mounted disk. partition> m Cannot modify disk partitions while it has mounted partitions.
a. Run format. Here is an example:

# format Searching for disks...done
AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010183a01,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010186a81,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b0b1,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0
GPRS/UMTS
672
6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0 10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 Specify disk (enter its number):
b. Select the disk that needs to be partitioned. To select the disk, type the number listed next to the disk and hit the enter key. Here is an example:
Specify disk (enter its number): 10
c. Type p (without the single quotes) twice to see the current partition table (partition table of the disk shows the different partitions already set on the disk). Here is an example:
format> p PARTITION MENU: 0 1 2 3 4 5 6 7 select modify name print label !<cmd> quit change `0' partition change `1' partition change `2' partition change `3' partition change `4' partition change `5' partition change `6' partition change `7' partition select a predefined table modify a predefined partition table name the current table display the current table write partition map and label to the disk execute <cmd>, then return
partition> p Current partition table (original): Total disk cylinders available: 14087 + 2 (reserved cylinders) Part Tag 0 unassigned 0 1 unassigned 0 2 backup 143349312 3 unassigned 30528 4 unassigned 0 5 unassigned 0 6 unassigned 0 7 unassigned 143318784 Flag wu wu wm wm wu wu wu wm Cylinders 0 0 0 - 14086 0 0 0 0 3 - 14086 2 0 0 Size (0/0/0) (0/0/0) 68.35GB 14.91MB 0 0 0 (14087/0/0) (3/0/0) (0/0/0) (0/0/0) (0/0/0) 68.34GB (14084/0/0) Blocks
d. Type m to modify the partition table. Here is an example:

411-5221-309 Standard 06.30 March 10, 2010
673
partition> m Select partitioning base: 0. Current partition table (original) 1. All Free Hog
e. Type 1 and hit enter. When prompted to create new partition table, type yes. Here is an example:
Choose base (enter number) [0]? 1
Part Tag 0 root 1 swap 2 backup 3 unassigned 4 unassigned 5 unassigned 6 usr 7 unassigned Flag wm wu wu wm wm wm wm wm Cylinders 0 0 0 - 14086 0 0 0 0 0 Size 0 0 68.35GB 0 0 0 0 0 Blocks (0/0/0) 0 (0/0/0) 0 (14087/0/0) 143349312 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0
Do you wish to continue creating a new partition table based on above table[yes]? yes
6. Hit enter key when prompted for Free Hog. Here is an example:
Free Hog partition[6]?
7. Enter the partition size for each partition in giga bytes or mega bytes. The partitions are [0, 1, 3, 4, 6, 5, 7]. Partition 2 will not be listed. Here is an example. In the example, partition 0 is assigned 20 GB, partition 3 is assigned 15 GB, partition 5 is assigned 25 GB and partition 7 is assigned 5 GB.
Enter Enter Enter Enter Enter Enter size size size size size size of of of of of of partition partition partition partition partition partition '0' '1' '3' '4' '5' '7' [0b, [0b, [0b, [0b, [0b, [0b, 0c, 0c, 0c, 0c, 0c, 0c, 0.00mb, 0.00mb, 0.00mb, 0.00mb, 0.00mb, 0.00mb,
Size 20.00GB 0 68.35GB 15.00GB 0 25.00GB 3.34GB 5.00GB
0.00gb]: 0.00gb]: 0.00gb]: 0.00gb]: 0.00gb]: 0.00gb]:
20gb 15gb 25gb 5gb
Part Tag 0 root 1 swap 2 backup 3 unassigned 4 unassigned 5 unassigned 6 usr 7 unassigned
Flag Cylinders wm 0 - 4121 wu 0 wu 0 - 14086 wm 4122 - 7213 wm 0 wm 7214 - 12366 wm 12367 - 13055 wm 13056 - 14086
Blocks (4122/0/0) 41945472 (0/0/0) 0 (14087/0/0) 143349312 (3092/0/0) 31464192 (0/0/0) 0 (5153/0/0) 52436928 (689/0/0) 7011264 (1031/0/0) 10491456
8. Type yes when prompted to make the modified partition table the current table. Here is an example:
Okay to make this the current partition table[yes]? yes
9. When prompted to enter the partition table name, type the disk name. This disk name can be indentified with format command output. Here is an example:
Enter table name (remember quotes): "c1t12d0"
GPRS/UMTS
674
10. Type yes when promoted to label the disk. Here is an example:
Ready to label disk, continue? yes
11. Type p to view the updated partition table. Here is an example:

partition> p Current partition table (c1t12d0):
Total disk cylinders available: 14087 + 2 (reserved cylinders) Part Tag 0 unassigned 1 unassigned 2 backup 3 unassigned 4 unassigned 5 unassigned 6 unassigned 7 unassigned Flag Cylinders wu 0 - 4121 wu 0 wm 0 - 14086 wm 4122 - 7213 wu 0 wu 7214 - 12366 wu 12367 - 13055 wm 13056 - 14086 Size 20.00GB 0 68.35GB 15.00GB 0 25.00GB 3.34GB 5.00GB Blocks (4122/0/0) 41945472 (0/0/0) 0 (14087/0/0) 143349312 (3092/0/0) 31464192 (0/0/0) 0 (5153/0/0) 52436928 (689/0/0) 7011264 (1031/0/0) 10491456
12. Type q twice to exit out of format. Here is an example:

partition> q FORMAT MENU: disk type partition current format repair label analyze defect backup verify save inquiry volname !<cmd> quit format> q select a disk select (define) a disk type select (define) a partition table describe the current disk format and analyze the disk repair a defective sector write label to the disk surface analysis defect list management search for backup labels read and display labels save new disk/partition definitions show vendor, product and revision set 8-character volume name execute <cmd>, then return
13. Format the disk partitions using newfs. newfs commands accepts the partition /dev/dsk/disk-slice as argument. The partition slice is the last two characters in disk-slice. For example, format for 0 is indicated as s0. When prompted to construct the new file system, type yes. Here is an example:
# newfs /dev/rdsk/c1t12d0s0 newfs: construct a new file system /dev/rdsk/c1t12d0s0: (y/ n)? y
This step needs to be execute newfs for all the partitions created with format. From the format example, slice 0, slice 3, slice 5 and slice 7 were created. So newfs on /dev/dsk/c1t12d0s0, /dev/dsk/
c1t12d0s3, /dev/dsk/c1t12d0s5, /dev/dsk/c1t12d0s7 needs to be executed.
411-5221-309
Standard
06.30 March 10, 2010
675
Use the formatted partitions when creating the Solaris 9 boot environment. For more details, please refer to Solaris 9 Boot Environment Creation on page 414. If users are visiting this section from Upgrade readiness checkpoint #0 28 days prior to upgrade on page 32 Checkpoint 0 item 7, page 57SCS server hardware analysis on page 52 OR Checkpoint 0 item 14, page 64Check the mirrors and record the mirror status on page 64
GPRS/UMTS
676
Appendix L: Procedure to mirror a server in case metadb partition is not assigned
Nortel Networks
Appendix L: Procedure to mirror a server in case metadb partition is not assigned 53

The following procedure can be followed to mirror a SCS server in case: At least 1 free (unmounted) disk is available the Solaris 9 server metadb partition has not been assigned which will prevent the user from performing disk mirroring. metadb partition has been assigned but partition size is less than 4 MB that will prevent the user from creting multiple metadb replicas. User requires to mirror a SCS server that was not mirrored previously. Also, additional free disks are available on the server that can be used to create mirrors.
Pre-requisites
53
Unmounted spare hard disk(s) are required to perform the disk mirroring. The number of spare disks required depends on the number of disks that are currently mounted. For example, if only one disk is mounted on the server, the user will need one umounted disk available on the server to perform the disk mirroring. If two disks are mounted, then the user will require two unmounted disks to perform the disk mirroring.
Procedure Overview
53
Here is an overview of the steps required to create mirrors on a non-mirrored server. The detailed steps are provided in the next section Detailed Procedure on page 677 a. Determine the number of mounted disks and disk partitions b. Determine the number of unmounted disks available on the server c. Partition the new disk to match as close as possible with the currently mounted disks. Assign one partition of 100 MB for the mirroring state database metadb d. Create a new file system for mountable partitions. This does not include swap e. Mount the partition from the new disk f. Use ufsdump and ufsrestore to replicate the data from the currently mounted disk partition to the new disk partitions
411-5221-309 Standard 06.30 March 10, 2010
Appendix L: Procedure to mirror a server in case metadb partition is not
g. Unmount the new disk partition h. Use installboot to install the bootblocks to the / raw disk partition on the new disk i. Mount the / partition from the new disk and edit </mountpoint>/etc/ vfstab to match the new disk partitions j. Modify eeprom for the system to recognize the new disk and boot from the new disk / partition k. Reboot the server to the new disk partitions l. Repartition the previously mounted disk to match the currently mounted new disk m. Start mirrroring procedure
Detailed Procedure
53
The following section explains the mirroring procedure by taking an example of a server with: Eleven disks One disk is currently mounted The mounted disk has 2 partitions: / and swap 1. Determine the number of currently mounted partitions using df -k and cat /etc/vfstab. Note, for example, if one disk is currently mounted, then identify 1 free unmounted disk. If 2 disks are currently mounted, then identify 2 free unmounted disks.
# df -k Filesystem kbytes used /dev/dsk/c1t5d0s0 61522236 27886148 /proc 0 0 fd 0 0 mnttab 0 0 swap 14528760 16 swap 14564568 35824 avail capacity 33020866 46% 0 0% 0 0% 0 0% 14528744 1% 14528744 1% Mounted on / /proc /dev/fd /etc/mnttab /var/run /tmp
# cat /etc/vfstab #device device mount FS #to mount to fsck point type # fd /dev/fd fd /proc /proc proc /dev/dsk/c1t5d0s1 swap /dev/dsk/c1t5d0s0 /dev/rdsk/c1t5d0s0 / swap /tmp tmpfs
fsck pass ufs -
mount mount at boot options no no no 1 yes no -
GPRS/UMTS
678
Nortel Networks
2. Determine the number of disks available on the server using format. Compare the output of format with the output of df -k to determine the unmonted disks. Also, determine if metadb partition is assigned for the mounted disks using format. Note, each mounted disk must have 1 metadb partition assigned. Usually the size of metadb partition is between 4 MB - 100 MB. For Solaris 9, it is recommended to have atleast 100 MB space assigned. The larger the size, more state database replicas can be created during disk mirroring.
# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a7ebe,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a8d24,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a851d,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a904e,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a9aae,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000011c67a93e0,0 6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0 10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 Specify disk (enter its number): 5 selecting c1t5d0 [disk formatted] Warning: Current Disk has mounted partitions. FORMAT MENU: disk type partition current format repair label analyze defect backup verify save inquiry volname !<cmd> quit format> p
select a disk select (define) a disk type select (define) a partition table describe the current disk format and analyze the disk repair a defective sector write label to the disk surface analysis defect list management search for backup labels read and display labels save new disk/partition definitions show vendor, product and revision set 8-character volume name execute <cmd>, then return
PARTITION MENU: 0 - change `0' partition 1 - change `1' partition 2 - change `2' partition 3 - change `3' partition 4 - change `4' partition 5 - change `5' partition 6 - change `6' partition
411-5221-309
Standard
06.30 March 10, 2010

7 select modify name print label !<cmd> quit change `7' partition select a predefined table modify a predefined partition table name the current table display the current table write partition map and label to the disk execute <cmd>, then return
partition> p Current partition table (original): Total disk cylinders available: 14087 + 2 (reserved cylinders) Part Tag 0 root 1 swap 2 backup 3 unassigned 4 unassigned 5 unassigned 6 unassigned 7 unassigned partition> q Flag Cylinders wm 0 - 12276 wu 12277 - 14086 wm 0 - 14086 wm 0 wm 0 wm 0 wm 0 wm 0 Size 59.57GB 8.78GB 68.35GB 0 0 0 0 0 Blocks (12277/0/0) 124930752 (1810/0/0) 18418560 (14087/0/0) 143349312 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0
Note: Here a partition for metadb is not assigned.
Table 35 Disk Partitions assigned for the non-mirrored server
Disk Partition /dev/dsk/c1t5d0s0 /dev/dsk/c1t5d0s1
File system
/ swap
3. Identify and partition the new disk. Assign slice 7 with 100 MB for the metadb partition. Here is an example capture to format disk 6 of size 72 GB. Use the output of df -k as a reference to partition the new disk. Here, slice 0 is assigned as /, slice 1 is assigned as swap and slice 7 is set as unassigned and has size set to 100 MB. Note: Make sure 'Flag' on all partition slices except swap are set as 'wm' and swap is set as 'wu'. Please refer to section Appendix N: Using format utility to modify the partition flag on page 687 to verify and modify the partition flag.
# format Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0
GPRS/UMTS
680
Nortel Networks
1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010183a01,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010186a81,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b0b1,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0 6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0 10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 Specify disk (enter its number): 6 selecting c1t8d0 [disk formatted] FORMAT MENU: disk type partition current format repair label analyze defect backup verify save inquiry volname !<cmd> quit format> p PARTITION MENU: 0 1 2 3 4 5 6 7 select modify name print label !<cmd> quit
select a disk select (define) a disk type select (define) a partition table describe the current disk format and analyze the disk repair a defective sector write label to the disk surface analysis defect list management search for backup labels read and display labels save new disk/partition definitions show vendor, product and revision set 8-character volume name execute <cmd>, then return
change `0' partition change `1' partition change `2' partition change `3' partition change `4' partition change `5' partition change `6' partition change `7' partition select a predefined table modify a predefined partition table name the current table display the current table write partition map and label to the disk execute <cmd>, then return
partition> p Current partition table (original): Total disk cylinders available: 14087 + 2 (reserved cylinders) Part Tag 0 root 1 swap 2 backup 3 unassigned 4 unassigned 5 var 6 unassigned Flag wm wu wm wm wu wm wu Cylinders 0 - 2012 2013 - 3623 0 - 14086 3624 - 3644 0 3645 - 7670 0 Size 9.77GB 7.82GB 68.35GB 104.34MB 0 19.54GB 0 Blocks (2013/0/0) 20484288 (1611/0/0) 16393536 (14087/0/0) 143349312 (21/0/0) 213696 (0/0/0) 0 (4026/0/0) 40968576 (0/0/0) 0
411-5221-309
Standard
06.30 March 10, 2010

7

home wm 7671 - 11696 19.54GB (4026/0/0) 40968576
Note: Use option m to modify the partition table partition> m Select partitioning base: 0. Current partition table (original) 1. All Free Hog Choose base (enter number) [0]? 1 Part Tag 0 root 1 swap 2 backup 3 unassigned 4 unassigned 5 unassigned 6 usr 7 unassigned Flag wm wu wu wm wm wm wm wm Cylinders 0 0 0 - 14086 0 0 0 0 0 Size 0 0 68.35GB 0 0 0 0 0 Blocks (0/0/0) 0 (0/0/0) 0 (14087/0/0) 143349312 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0
Do you wish to continue creating table based on above table[yes]? Free Hog partition[6]? Enter size of partition '0' [0b, Enter size of partition '1' [0b, Enter size of partition '3' [0b, Enter size of partition '4' [0b, Enter size of partition '5' [0b, Enter size of partition '7' [0b, Part Tag 0 root 1 swap 2 backup 3 unassigned 4 unassigned 5 unassigned 6 usr 7 unassigned
a new partition <-Type yes 0c, 0c, 0c, 0c, 0c, 0c, 0.00mb, 0.00mb, 0.00mb, 0.00mb, 0.00mb, 0.00mb, 0.00gb]: 60gb 0.00gb]: 8gb 0.00gb]: 0.00gb]: 0.00gb]: 0.00gb]: 100mb Blocks (12366/0/0) 125836416 (1649/0/0) 16780224 (14087/0/0) 143349312 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (51/0/0) 518976 (21/0/0) 213696
Flag Cylinders wm 0 - 12365 wu 12366 - 14014 wu 0 - 14086 wm 0 wm 0 wm 0 wm 14015 - 14065 wm 14066 - 14086
Size 60.00GB 8.00GB 68.35GB 0 0 0 253.41MB 104.34MB
Okay to make this the current partition table[yes]? yes Enter table name (remember quotes): "c1t8d0" Ready to label disk, continue? yes partition> p Current partition table (c1t8d0): Total disk cylinders available: 14087 + 2 (reserved cylinders) Part Tag 0 root 1 swap 2 backup 3 unassigned 4 unassigned 5 var 6 unassigned 7 home partition> q FORMAT MENU: disk type partition current format repair label analyze defect backup verify save inquiry volname Flag Cylinders wm 0 - 12365 wu 12366 - 14014 wm 0 - 14086 wm 0 wu 0 wm 0 wu 14015 - 14065 wm 14066 - 14086 Size 60.00GB 8.00GB 68.35GB 0 0 0 253.41MB 104.34MB Blocks (12366/0/0) 125836416 (1649/0/0) 16780224 (14087/0/0) 143349312 (0/0/0) 0 (0/0/0) 0 (0/0/0) 0 (51/0/0) 518976 (21/0/0) 213696
select a disk select (define) a disk type select (define) a partition table describe the current disk format and analyze the disk repair a defective sector write label to the disk surface analysis defect list management search for backup labels read and display labels save new disk/partition definitions show vendor, product and revision set 8-character volume name
GPRS/UMTS
682

!<cmd> quit format> q - execute <cmd>, then return
Nortel Networks
4. On the formatted new disk, run 'newfs' on all partitions except swap to create an ufs filesystem. Here is an example capture for creating a new filesystem on slice 0 and slice 7.
# newfs /dev/dsk/c1t8d0s0 newfs: /dev/rdsk/c1t8d0s0 last mounted as /mnt1 newfs: construct a new file system /dev/rdsk/c1t8d0s0: (y/n)? y /dev/rdsk/c1t8d0s0: 125836416 sectors in 12366 cylinders of 24 tracks, 424 sectors 61443.6MB in 1237 cyl groups (10 c/g, 49.69MB/g, 6016 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, 102224, 204416, 306608, 408800, 510992, 613184, 715376, 817568, 919760, Initializing cylinder groups: ........................ super-block backups for last 10 cylinder groups at: 124864304, 124966496, 125068688, 125170880, 125273072, 125375264, 125477456, 125579648, 125681840, 125784032, # newfs /dev/dsk/c1t8d0s7 newfs: construct a new file system /dev/rdsk/c1t8d0s7: (y/n)? y /dev/rdsk/c1t8d0s7: 213696 sectors in 21 cylinders of 24 tracks, 424 sectors 104.3MB in 3 cyl groups (8 c/g, 39.75MB/g, 19008 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, 81872, 163712,
5. Make a new directory for mounting the filesystem, example - /newmnt

# mkdir /newmnt
6. Mount the root partition / from the new disk on the newly created directory.
# mount -F ufs -o rw /dev/dsk/c1t8d0s0 /newmnt
7. Use ufsdump and ufsrestore to replicate the / partition from the currently mounted / partition onto the new disk / partition. Answer y when prompted to set mode.
# ufsdump 0f - / | (cd /newmnt;ufsrestore xvf -) ... extract file ./etc/vfstab Add links Set directory mode, owner, and times. set owner/mode for '.'? [yn] y Directories already exist, set modes anyway? [yn] y
8. Unmount the mounted partition (/newmnt) on the new disk.

# umount /newmnt
411-5221-309
Standard
06.30 March 10, 2010
9.
Repeat the above steps: Step 6 and Step 7 to replicate other mounted partitions on to the new disk. For example, if the server has /usr, /var, /opt, /home currently mounted from the primary drive, mount each partition one at a time (Step 6) and execute ufsdump and ufsrestore (Step 7) to replicate the data for these partitions on to the new disk partitions. Note, if multiple disks are currently mounted, then multiple free disks need to be identified, formatted and new file systems created before running ufsdump.
10. Install the boot image on the / partition on the new disk. Make sure the bootblk file exists running 'ls' command. Here is an example.
# ls -al /usr/platform/`uname -i`/lib/fs/ufs/bootblk -r--r--r-1 root sys 5936 Mar 18 2004 /usr/ platform/SUNW,Sun-Fire-880/lib/fs/ufs/bootblk
Syntax for installboot: /usr/sbin/installboot <path_to_bootblk> <raw-disk-device>

# /usr/sbin/installboot /usr/platform/`uname -i`/lib/fs/ufs/ bootblk /dev/rdsk/c1t8d0s0
11. Mount the / partition from the new disk. Example,

# mount -F ufs -o rw /dev/dsk/c1t8d0s0 /newmnt
12. Modify /newmnt/etc/vfstab on the new disk to match the partitions for the new disk.
# cd /newmnt/etc/
From the example, vfstab has been updated the partitions to match the new disk partitions c1t8d0s0 for '/' and c1t8d0s1 for 'swap'.
#device device #to mount to fsck # /dev/dsk/c1t8d0s1 /dev/dsk/c1t8d0s0 mount point FS type swap / fsck pass ufs mount mount at boot options no 1 no -
/dev/rdsk/c1t8d0s0
13. Unmount the mounted partition (/newmnt) on the new disk.

# umount /newmnt
14. Find the boot device address for the / partition on the current mounted disk and the new disk.
GPRS/UMTS
684
Nortel Networks
Here is an example for the current mounted disk /dev/dsk/c1t5d0d0:

# ls -la /dev/dsk/c1t5d0s0 lrwxrwxrwx 1 root root 70 Dec 22 2005 /dev/ dsk/c1t5d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@2/ fp@0,0/ssd@w21000011c67a93e0,0:a
Here is an example for the / partition on the new disk /dev/dsk/c1t8d0s0:

# ls -al /dev/dsk/c1t8d0s0 lrwxrwxrwx 1 root root 70 Dec 22 2005 /dev/ dsk/c1t4d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@2/ fp@0,0/ssd@w21000011c67a9aae,0:a
15. The server boot path must be updated so that the server can boot up from the new disk / partition. Modify the eeprom to set the boot-device. Set the primary boot disk to the new disk / partition and the backup boot disk as the current mounted / disk. Follow section Appendix M: Updating server eeprom on page 685. Here, the first boot-device in Step 6 on 686 must be set to the / disk address for the new disk and the backup boodevice must be set to the current mounted / partition disk address. 16. Reboot the server following section Rebooting the SCS server on page 210 17. Login to the server as root user. Verify the server partitions are mounted from the new disk using df -k. 18. Proceed to Appendix D: Creating a Partition on a New Disk for Disk Mirroring on page 600 to repartition the previously mounted disk partitions. 19. Fill out a table similar to Example disk mirror map for critical file system on page 586 and Example disk mirror map for non-critical file system on page 586 for both critical and non-critical file systems. Critical file systems include /, /usr, /var and /opt (and/ or partition where SCS and LDAP/ iPlanet are installed). Non-critical file systems include swap, /home (or any user specific mounted partitions) 20. After the disk has been repartitioned, proceed to Appendix E: Creating Mirrors on page 609 to create mirrors.
411-5221-309
Standard
06.30 March 10, 2010
685
54
The server eeprom stores the boot options that will be used during server reboot. In this section, the eeprom is updated so that server recognizes the bootable disk / partitions.
Detailed Steps
54
1. Make a note of the server boot path. Run ls -al for the physical partition assigned the / partition.
# ls -al /dev/dsk/c1t0d0s0 lrwxrwxrwx 1 root root 70 May 16 16:06 /dev/ dsk/c1t4d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@2/ fp@0,0/ssd@w500000e01069a8b1,0:a
In the above example, this disk address string is:

/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0:a
/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w500000e01069a8b1,0:a
Make a note of this string, this is called current_root for reference.

current_root - /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w500000e01069a8b1,0:a
2. In case the server is mirrored or about to be mirrored, determine the server backup / disk partition. Run ls -al for the physical partition assigned for the / partition.
# ls -al /dev/dsk/c0t8d0s0 lrwxrwxrwx 1 root root 70 May 16 16:06 /dev/ dsk/c1t5d0s0 -> ../../devices/pci@8,600000/SUNW,qlc@2/ fp@0,0/ssd@w500000e01069b101,0:a
In the above example, this disk address string is:

/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0:a
GPRS/UMTS
686
/pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w500000e01069b101,0:a
Make a note of this string, this is called backup_root for reference. This will be needed during reboot of the server after mirroring all the partitions.
backup_root - /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w500000e01069b101,0:a
3. Update the server eeprom with two device aliasis, one for the current_root and one for the backup_root. Here is an example.
Syntax: eeprom nvramrc=devalias device_alias address
From the above example, current_root and backup_root are added as device alias:
# eeprom "nvramrc=devalias current_root /pci@8,600000/ SUNW,qlc@2/fp@0,0/disk@w500000e01069a8b1,0:a devalias backup_root /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w500000e01069b101,0:a"
4. Store the eeprom settings using:

# eeprom "use-nvramrc?"=true
5. Verify the eeprom parameter use-nvramrc? is set to true.

# eeprom "use-nvramrc?" use-nvramrc?=true
6. Set the eeprom parameter boot-device to current_root and backup_root.

# eeprom boot-device="current_root backup_root"
411-5221-309
Standard
06.30 March 10, 2010
Appendix N: Using format utility to modify the partition flag
687

Flag wm means read/write mountable Flag wu means read/write unmountable
55
This section explains the steps required to change the partition flag using format utility.
On the SCS server, each mountable disk partition must have the flag set to wm. The swap partition's flag must be set to "wu". Here are steps to verify and modify partition flag:
# format < /dev/null Searching for disks...done AVAILABLE DISK SELECTIONS: 0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010188041,0 1. c1t1d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010183a01,0 2. c1t2d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e010186a81,0 3. c1t3d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b0b1,0 4. c1t4d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069a8b1,0 5. c1t5d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01069b101,0 6. c1t8d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a240c,0 7. c1t9d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a242d,0 8. c1t10d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w210000008719e404,0 9. c1t11d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000000871a20b8,0 10. c1t12d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01026c4c1,0 11. c1t13d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424> /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf786ffa,0 zrc2s0pw# Searching AVAILABLE 0. format for disks...done DISK SELECTIONS: c1t0d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cf27c6c6,0 1. c1t1d0 <SUN36G cyl 24620 alt 2 hd 27 sec 107> /pci@9,600000/SUNW,qlc@2/fp@0,0/ssd@w21000004cfa3b945,0 Specify disk (enter its number): 1 selecting c1t1d0 [disk formatted] Warning: Current Disk has mounted partitions. FORMAT MENU: disk - select a disk type - select (define) a disk type partition - select (define) a partition table current - describe the current disk
GPRS/UMTS
688
format - format and analyze the disk repair - repair a defective sector label - write label to the disk analyze - surface analysis defect - defect list management backup - search for backup labels verify - read and display labels save - save new disk/partition definitions inquiry - show vendor, product and revision volname - set 8-character volume name !<cmd> - execute <cmd>, then return quit format> verify Primary label contents: Volume name = < > ascii name = <SUN36G cyl 24620 alt 2 hd 27 sec 107> pcyl = 24622 ncyl = 24620 acyl = 2 nhead = 27 nsect = 107 Part Tag Flag Cylinders Size Blocks 0 root wm 0 - 24615 33.91GB (24616/0/0) 71115624 1 swap wu 24616 - 24619 5.64MB (4/0/0) 11556 2 backup wu 0 - 24619 33.92GB (24620/0/0) 71127180 3 wu 0 0 (0/0/0) 0 4 wu 0 0 (0/0/0) 0 5 var wm 0 0 (0/0/0) 0 6 usr wm 0 0 (0/0/0) 0 7 unassigned wm 0 0 (0/0/0) 0 To set these flags, please perform the following steps: #fomat >Specify disk (enter its number): <-----specify disk by entering number for choice > partition (or you can just enter 'p') > (enter number for partition) > Enter partition id tag[swap]: <----choose to change or keep remaining tag name > Enter partition permission flags[wu]: wm <---------change the flag to 'wm' here > Enter new starting cyl[24616]: (Hit Enter to select the default value) > Enter partition size[11556b, 4c, 5.64mb, 0.01gb]: (Hit Enter to select the default value) > partition> label <----type label at this prompt to save changes > Ready to label disk, continue? yes <-----type 'yes' here Exit format by entering q
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Appendix O: Procedure to modify SCS server IP, host name or domain name 689
Appendix O: Procedure to modify SCS server IP, host name or domain name

56
The following procedure explains the steps required to modify the SCS server IP address, host name or domain name. A fresh install of SCS and iPlanet is required if the SCS server IP address or host name or domain name is modified. A server reboot is required for this procedure. Please plan this activity in a maintanence window. A GGSN reboot followed by a resync is required for a SCS IP address change.
Terminologies
<SCS_ROOT>
56
- identifies the installation directory for the running version of SCS software. Example: /opt/shasta/scs502
<IPLANET_ROOT>
- identifies the installation directory of version of LDAP or iPlanet software SCS server is connecting to. Example: /opt/shasta/iplanet
Pre-requisites
Perform the following pre-requisite steps before proceeding.
56
It is recommended to have console access or a directly connected monitor to the SCS server. To launch the LDAP/ iPlanet GUI console, users will require either a directly connected monitor or xterm to the SCS server. Determine the current SCS and iPlanet installation directories and installation parameters. LDAPPath, LDAPRoot, LDAPServerPort, LDAPServerIp - make sure LDAPServerPort for the new installation matches the current value. Port assigned for LDAPPort must be open (free) prior to performing a new installation of LDAP/ iPlanet. LDAPServerIp can be set as localhost. SCSHead, Region ID - make sure the Region ID for the new installation matches the current settings.
GPRS/UMTS
690
Appendix O: Procedure to modify SCS server IP, host name or domain name Nortel Networks Confidential
Change directory to /etc/shasta. SCS config parameters can be found in file scs.config. Use the unix grep command to determine the following installation parameters.When performing the new installation of SCS and iPlanet, make sure the same parameters are set.
# cat scs.config | grep SCSHead # cat scs.config | grep LDAPPath # cat scs.config | grep RegionId # cat scs.config | grep LDAPServerPort # cat scs.config | grep LDAPRoot # cat scs.config | grep LDAPServerIp
Here is an example:
# cd /etc/shasta # cat scs.config # # This file was generated during SCS installation. # Please do not modify manually. # SCSHead=/opt/shasta/scs502 InstallDomainServer=yes InstallRegionServer=yes InstallMonitorServer=yes InstallPullServer=yes InstallLogServer=yes DomainServerIp=localhost RegionId=1 LDAPPath=/opt/shasta/iplanet LDAPServerName=slapd-urc2y1th LDAPServerIp=localhost LDAPServerPort=395 LDAPUsername="uid=admin,ou=Administrators,ou=TopologyManage ment,o=NetscapeRoot" LDAPPassword=admin LDAPRoot="uid=admin,ou=People,o=us.nortel.com" PullListenPort=4321 LogLogPort=4322 LogAccountPort=4323 RegionRootDir=/opt/shasta/scs502 DBAdminPassword=admin MaximumHeapSize=512 SCSBackup=/opt/shasta/scs502/backup DBBackupTimeWait=300 LogUser=pmuser
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Appendix O: Procedure to modify SCS server IP, host name or domain name 691 # cat scs.config | grep SCSHead SCSHead=/opt/shasta/scs502 This is referred to <SCS_ROOT> in this procedure. # cat scs.config | grep LDAPPath LDAPPath=/opt/shasta/iplanet This is referred to <IPLANET_ROOT> in this procedure. # cat scs.config | grep RegionId RegionId=1 # cat scs.config | grep LDAPServerPort LDAPServerPort=395 # cat scs.config | grep LDAPRoot LDAPRoot="uid=admin,ou=People,o=us.nortel.com" # cat scs.config | grep LDAPServerIp LDAPServerIp=localhost
Make sure /etc/resolv.conf, /etc/hosts, /etc/nsswitch.conf are set correctly. Please refer to Basic system settings required on the SCS: on page 200
Overview of the procedure

Users can perform an optional full server backup before starting the procedure.
56
A SCS solid db backup using SCSAdmin backup solidDB and LDAP backup using ldapsearch is first performed. The backups are then copied to a backup directory. It is also recommended to FTP the backup files to another server. The current SCS and iPlanet applications are stopped and the installation directories are renamed. The SCS server IP address and/ or host name and/ or domain name are modified. A server reboot is required to commit the changes. A fresh install of SCS and iPlanet using silent install procedure is performed. The new SCS installation parameters must match the old parameters. The parameters include SCSHead (<SCS_ROOT>), LDAPPath (<IPLANET_ROOT>), LDAServerPPort, LDAPServerIp, LDAPRoot (LDAP root point) and SCS server RegionID. The backup of iPlanet and SCS are then restored. SCS server processes are restarted. The SCS server IP is then modified from the SCS client. If a SCS IP address change was performed, the GGSN quickstart is modified to point to the new SCS server IP address. A GGSN reboot
692
followed by a resync is performed.
Detailed Procedure
1. Optional - Perform a full server backup to tape.
56
If a tape drive is mounted on the SCS server, perform a full server tape backup. This step is optional. Please refer to Full System backup and restore on page 393 for details. Please refer to Pre-requisites on page 689 to determine the SCS server parameters - <SCS_ROOT> and <IPLANET_ROOT> as they are needed to proceed. 2. Disable provisioning from the SCS server.
# cd <SCS_ROOT>/bin # ./SCSAdmin disableProvisioning
3. Create a backup directory to save the SCS solid and ldap databases. Make sure there is enough disk space to save the backup. Run df -k to determine the free disk space available.
# df -k # cd <destination_partition> # mkdir <SCS_LDAP_BACKUP>
Here is an example:
# df -k <-Determine a partition with enough free space. In this example, /opt is used. # cd /opt # mkdir SCS_LDAP_BACKUP
4. Perform a LDAP/ iPlanet backup using ldapsearch.

# cd <IPLANET_ROOT>/shared/bin # ./ldapsearch -p <LDAP Server Port #> -T -b <LDAP Root Point> objectclass=* > <filename>
The ldap database is now backed up in <filename> file. Use ls -l and cat to determine the file size and content of the backup. Make sure the backup is not 0 size. If the file size it 0, check the ldapsearch command that was entered, make sure it did not have any typing errors. Rerun the ldapsearch command.
411-5221-309
Standard
06.30 March 10, 2010
Here is an example:
# cd /opt/shasta/iplanet/shared/bin # ./ldapsearch -p 395 -T -b "uid=admin,ou=People,o=us.nortel.com" "objectclass=*" > iplanet502 # ls -lrt iplanet502 -rw-r--r-1 root other 181751 Jun 18 12:01 iplanet502
# cat iplanet502
version: 1 dn: uid=admin,ou=People, o=us.nortel.com objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson cn: admin user uid: admin givenName: admin sn: user dn: dc=ISPs,uid=admin,ou=people,o=us.nortel.com dc: ISPs objectClass: top objectClass: domain
...
5. If the SCS server domain name is to be modified, edit the LDAP/ iPlanet backup file and modify the old domain name with the new domain name. Refer to Modifying LDAP backup in case of server domain name change on page 211 for details. 6. Perform a SCS solid database backup using SCSAdmin backup solidDB. When the backup is complete, tar the backup directory. In SCS 5.0.2, the backup directory path is displayed in the output logs printed during the execution of the backup script. For SCS software version prior to SCS 5.0.2, the backup directory is located in <SCS_ROOT>/opt/solidSolaris/database directory.
Backup solid db using the following commands.

# cd <SCS_ROOT>/bin # ./SCSAdmin backup solidDB <backup_directory>
Here is an example:
# ./SCSAdmin backup solidDB scs502_bk binDir is /opt/shasta/scs502/bin head is /opt/shasta/scs502 configFile is /opt/shasta/scs502/bin/.scs.config backup_dir is /opt/shasta/scs502/opt/solidSolaris/database/ scs502_bk Solid Remote Control v.04.00.0025
GPRS/UMTS
694
Appendix O: Procedure to modify SCS server IP, host name or domain name Nortel Networks Confidential (C) Copyright Solid Information Technology Ltd 1993-2003 Exit by giving command: exit Backup started. ....
tar the solid db backup directory. Here is an example.

# cd /opt/shasta/scs502/opt/solidSolaris/database # tar cvf scs502_bk.tar scs502_bk
7. Copy the SCS solid db and LDAP/ iPlanet backup to the backup directory. tar the backup and FTP it to a different server. Copy SCS solid db to backup directory:
# cd <SCS_ROOT>/opt/solidSolaris/database # cp <scs_backup>.tar <SCS_LDAP_BACKUP>
Here is an example:
# cd /opt/shasta/scs502/opt/solidSolaris/database # cp scs502_bk.tar /opt/SCS_LDAP_BACKUP
Copy LDAP/ iPlanet backup to backup directory:

# cd <IPLANET_ROOT>/shared/bin # cp <iplanet_backup> <SCS_LDAP_BACKUP>
Here is an example:
# cd /opt/shasta/iplanet/shared/bin # cp iplanet502 /opt/SCS_LDAP_BACKUP
tar the backup directory

# tar cvf <SCS_LDAP_BACKUP>.tar <SCS_LDAP_BACKUP>
Here is an example:
# cd /opt # tar cvf SCS_LDAP_BACKUP.tar SCS_LDAP_BACKUP
FTP the tar file to a different server. 8. Perform a tar backup of SCS and iPlanet installation directories. Please refer to Option 1: SCS backup/ restore using tar on page 233 Here is an example where SCS and LDAP/ iPlanet are in the same root directory, in this case - /opt/shasta.
411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential Appendix O: Procedure to modify SCS server IP, host name or domain name 695 # cd /opt/shasta # tar cvf SCS502_TAR_BACKUP.tar scs502 iplanet # compress SCS502_TAR_BACKUP.tar
The compressed file will have a .Z extension added to the file. 9. FTP the SCS-LDAP/iPlanet tar/ compressed backup to another server. 10. Move the following SCS and iPlanet startup files to <SCS_LDAP_BACKUP>
# # # # mv mv mv mv /etc/rc3.d/S95scs <SCS_LDAP_BACKUP> /etc/rc3.d/S90ldap <SCS_LDAP_BACKUP> /etc/rc0.d/K04scs <SCS_LDAP_BACKUP> /etc/rc0.d/K05ldap <SCS_LDAP_BACKUP>
If the mv command returns an error indicating the file cannot be found, change directory to /etc/rc3.d and issue the commad ls *scs* and ls *ldap*. Move the SCS and LDAP files returned by the previous ls command to <SCS_LDAP_BACKUP>. Repeat the same steps for /etc/ rc0.d. 11. Stop SCS and LDAP/ iPlanet server processes. Refer to Verify and Stopping SCS server and LDAP server processes on page 208. 12. Rename the current <SCS_ROOT> - the SCS installation directory.
# mv <SCS_ROOT> <SCS_ROOT_old>
Here is an example.
# cd /opt/shasta # mv scs502 scs502_old
13. Rename the current <IPLANET_ROOT>. Here is an example.

# mv <IPLANET_ROOT> <IPLANET_ROOT_old>
Here is an example:
# cd /opt/shasta # mv iplanet iplanet_old
14. Verify the port assigned for <LDAPServerPort> is free. Please refer to Pre-requisites on page 689 to determine the <LDAPServerPort> configured for the server.
696
Here is an example where LDAPServerPort is set to 395. The netstat| grep command must not return an optput exactly matching 395.
# netstat -na | grep 395
15. Modify the SCS server IP address and/ or host name and/ or domain name. Users can refer to Modify SCS server IP address or hostname on page 218 and Modify SCS server domain name on page 220 for details. Users can also get information from Sun System Administration guide. Note: If the IP address of the server was modified using Solaris commands like sys-unconfig, the server /etc/resolv.conf, /etc/nsswitch.conf, /etc/defaultrouter files are reset to default values. These files must be configured immediately after rebooting the server. Please refer to Basic system settings required on the SCS on page 159 and verify and if needed, set the system files before proceeding. 16. Login to the console port (or monitor). Perform a server reboot. Refer to Rebooting the SCS server on page 210 17. Verify connectivity to the new IP address by telneting to the SCS server as root user. Verify the server IP, host name or domain name has been modified.
# uname -a # ifconfig -a
18. Perform a fresh install of SCS and iPlanet. Refer to Appendix P: Perform a SCS 6.0 new install on page 704 for details. 19. Verify LDAP/ iPlanet server and admin processes are running. Refer to Verify LDAP/ iPlanet server and admin process status on page 209. If the any of the process is not running, restart the processes. Refer to Start the LDAP / iPlanet server. Enable LDAPWatch on page 205 20. Start SCS server processes.
21. Enable LDAPWatch if not enabled earlier.

# ./LDAPWatch-enable
411-5221-309
Standard
06.30 March 10, 2010
22. Perform a restore of LDAP/ iPlanet database. Note: If the iPlanet is installed automatically during SCS 5.0.x new installation, the default Directory Manager password will be 'dmanager'. In SCS 4.1.2, the default password is 'password'. Note: If the LDAP/iPlanet Directory Manager settings were modified during installation, please refer to Resetting LDAP/ iPlanet Root DN name and password on page 212 to reset the settings.
# cd <IPLANET_ROOT>/shared/bin # ./ldapmodify -p <LDAP Server Port #> -D Root DN -w <Root DN Password> -c -a -f <LDAP data file name>
Here is an example capture for restoring iPlanet database for SCS 5.0.2. The Directory Manager password is dmanager.
# cd /opt/shasta/iplanet/shared/bin # ./ldapmodify -p 395 -D "cn=Directory Manager" -w dmanager -c -a -f iplanet502 adding new entry uid=admin,ou=People, o=us.nortel.com
adding new entry dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=Areas,uid=admin,ou=people,o=us.nortel.com adding new entry o=any,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=DomainGroups,o=any,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry dc=DomainGroups,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.nortel. com adding new entry o=Customers,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.nortel.com adding new entry o=Isp,o=Customers,o=li_default_isp,dc=ISPs,uid=admin,ou=people,o=us.norte l.com
... ...
adding new entry shastaType=LDAP_REACH_ADDR+shastaId=7,userid=ipsecsub,ou=Sites,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=People,o=us.nortel.com adding new entry userid=ipsecs,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=People,o=us.nortel.com adding new entry userid=l2tp-cisco,ou=Templates,o=Isp,o=Customers,o=ispcda,dc=ISPs,uid=admin,ou=People,o=us.nortel.com
GPRS/UMTS
698
23. Copy the solid db backup files to the backup directory.

# cp <SCS_LDAP_BACKUP>/<solid_backup>.tar <SCS_ROOT>/opt/ solidSolaris/database # cd <SCS_ROOT>/opt/solidSolaris/database # mkdir backup # tar cvf <solid_backup>.tar # cd <solid_backup> # cp * ../backup
Here is an example. Directory /opt/SCS_LDAP_BACKUP is <SCS_LDAP_BACKUP>, <SCS_ROOT> is /opt/shasta/scs502.

# cd /opt/SCS_LDAP_BACKUP # ls iplanet502
scs502_bk.tar
# cp *.tar /opt/shasta/scs502/opt/solidSolaris/database # cd /opt/shasta/scs502/opt/solidSolaris/database # ls default # mkdir backup # tar xvf scs502_bk.tar

x /opt/shasta/scs502/opt/solidSolaris/database/scs502_bk, 0 bytes, 0 tape blocks x /opt/shasta/scs502/opt/solidSolaris/database/scs502_bk/ solid.db, 12320768 bytes, 24064 tape blocks x /opt/shasta/scs502/opt/solidSolaris/database/scs502_bk/ sol00227.log, 110592 bytes, 216 tape blocks x /opt/shasta/scs502/opt/solidSolaris/database/scs502_bk/ sol00228.log, 139264 bytes, 272 tape blocks x /opt/shasta/scs502/opt/solidSolaris/database/scs502_bk/ solid.ini, 1588 bytes, 4 tape blocks x /opt/shasta/scs502/opt/solidSolaris/database/scs502_bk/ solmsg.out, 716859 bytes, 1401 tape blocks
scs502_bk.tar
# ls backup # cd scs502_bk # ls sol00227.log solmsg.out
default
scs502_bk
scs502_bk.tar
sol00228.log
solid.db
solid.ini
# cp * ../backup
411-5221-309
Standard
06.30 March 10, 2010
# cd ../backup # ls sol00227.log solmsg.out
sol00228.log
solid.db
solid.ini
24. Perform a SCS solid db restore.

Here is an example:
# cd /opt/shasta/scs502/bin # ./SCSAdmin restore solidDB This will overwrite database(s). Are you sure? (Y)es or (N)o: y Need to stop the solid database server... Delete the old database... Restore the database from /opt/shasta/scs502/opt/ solidSolaris/database/backup ... [1] 7766 Starting Solid Database Server:.Started Done. Finished restoring Solid Database, please restart SCS server manually.
25. Restart SCS server processes.

# pwd <SCS_ROOT>/bin # ./SCSAdmin restart
26. Verify /etc/shasta/scs.config has been updated. Verify SCSHead, LDAPPath, LDAPServerPort, RegionId are set correctly.
27. If the SCS server IP was modified - Modify SCS IP from SCS client. Note: After logging into SCS client, do not click the Region icon (center panel). Login to SCS client as device_owner user using the new SCS server IP address.
700
From the File menu, click on SCS Configuration.... Click on SCS Server Properties. Select each server type, click Edit. Modify the IP address to the new IP. Click OK. IP address for all server types must be modified to the new IP.
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Appendix O: Procedure to modify SCS server IP, host name or domain name 701 Figure 11 Modify SCS server IP in SCS Server Properties
28. Restart SCS server processes.

# pwd <SCS_ROOT>/bin # ./SCSAdmin restart
29. Login to the SCS client as device_owner user. Double click Regions in the middle panel. This will list the Region id and Name in the left panel. Click on the Region id, click Edit. Make sure Region Server and Monitor Server status are UP. If any of the servers indicate DOWN, then restart the SCS server processes. Refer to Step 28..to restart the server.
702
If a SCS IP address change was performed, the next step is to migrate the GGSN quickstart parameter to point to the new SCS server IP address. If a SCS IP address change was performed, proceed to migrate the GGSN to the new SCS server IP address following Step 30. through Step 35.. Note: Perform the GGSN migration in a maintenance window. Note: If there are multiple GGSNs on configured on the SCS Region, perform steps Step 30. through Step 35., one GGSN at a time. Make sure GGSN come insync before proceeding to modifying quickstart on the next GGSN. 30. Modify GGSN quickstart by logging to the GGSN with SSU privileges. Modify quickstart parameter using set quickstart. The 1st SCS IP address : parameter must be modified with the new SCS server IP. Note: Hit Enter key to select the default value for other parameters. After setting the new IP in parameter 1st SCS IP address :, hit Enter key for all other options till you get the GGSN CLI prompt.
# set quickstart . . >1st SCS IP address: <enter new IP address of SCS server>
31. Close all GTP sessions from GGSN CLI.

ggsn# close gtp session all
32. Flush billing records. Please refer to Nortel GGSN Hardware Installation and Maintenance Guide - NTP 411-5221-923 Section: Manual GGSN shutdown, resync, or CMC switchover Note: Skip the shutdown step mentioned in the above section in the GGSN hardware guide. 33. Login to the GGSN console (if available). Otherwise, telnet to the GGSN as admin user. Reboot GGSN from CLI.
ggsn# reboot
34. Login to SCS Client as device_owner user. Right click on the Resync GGSN.
411-5221-309
Standard
06.30 March 10, 2010
35. Verify GGSN is insync after reboot. 36. Modify the SOC key. Refer to SOC key update procedure on page 215. 37. After determining there are no issues with the migration, users can remove the previous SCS and iPlanet installation directories. Note: Make sure the old server tar backup has been FTPed to another server before deleting. Here is an example.
# cd /opt/shasta # rm -rf scs502_old
GPRS/UMTS
704

57
Here are the steps to perform a new install of SCS 6.0. The procedure used can also be referred as silent install. The following procedure assumes iPlanet is not installed on the server. If a new installation is performed as part of a server IP address, host name or domain name change, make sure the following SCS Server settings match the old installation. Please refer to Pre-requisites on page 689 Region ID - region ID assigned to the SCS server LDAPRoot - root point to which the SCS server connects to the iPlanet server LDAPPort - port on which iPlanet process is listening Optional - SCSHead and LDAPPath - installation directory for SCS 6.06.0 and iPlanet
Install Procedure
1. Create a directory for SCS 6.06.0. Make sure the partition has enough disk space. Use df -k to verify enough disk space is available. Please refer to Checkpoint 0 item 6, page 52 for details.
# cd /opt # mkdir -p shasta/scs502
57
2. FTP a copy of SCS 6.0 software to the SCS 6.0 installation directory. Refer to section Acquiring GPRS Packet Core software for the CS-LAN on page 24. The following files are required: scsserver.tar.Z directory-5[1].1sp3-us.sparc-sun-solaris2.8.tar Optional - scs_corba_server.tar.Z Optional - sslpkg.tar.Z
3. Uncompress and untar scsserver.tar file.

# cd /opt/shasta/scs502 # uncompress scsserver.tar.Z # tar xvf scsserver.tar
4. If SCS Corba Server is to be installation, uncompress file scs_corba_server.tar.Z. Do not untar the file.
# uncompress scs_corba_server.tar.Z
411-5221-309
Standard
06.30 March 10, 2010
705
5. Determine the following server information. These information are needed to edit the SCS installation parameter file .inputparms_install.scs.
Note: Use ls -al in the SCS installation directory to view the file listing for .inputparms_install.scs. Determine the server host name using the command uname -n. File .inputparms_install.scs - parameter LDAPServerName must be updated with the host name.
# uname -a <server host name is returned> LDAPServerName = slapd=<hostname>
Here is an example:
# uname -n urc2y1th LDAPServerName = slapd-urc2y1th
Verify the server port 395 is free using the command netstat -na | grep 395. This port will be set as LDAPPort in .inputparms_install.scs. If the port 395 is free, the above command will not return an output and give the user the command prompt. Here is an example:
# netstat -na | grep 395 # LDAPPort = 395
If the netstat -na | grep 395 has already been used by the server, verify the next available port 396 is free. Here an example where port 395 is already used by the server.
0 0 49152 0 LISTEN
# netstat -na | grep 389 *.389 *.* # netstat -na | grep 396 # LDAPPort = 396
6. Make sure iPlanet admin port 33611 is free using netstat -na | grep 33611. If the port is free, the netstat command will return just the command prompt. Here is an example.
706
Appendix P: Perform a SCS 6.0 new install # netstat -na | grep 33611 #
If the netstat command returns a result similar to the example below, iPlanet admin port is already used by the server. In this case, check and make sure iPlanet software is not used by any other applications running on the server. Un-installing iPlanet will be a good option to clean up old iPlanet installations. Please refer to Appendix H: Example capture of iPlanet server uninstallation on page 656 for details.
0 0 49152 0 LISTEN
# netstat -na | grep 33611 47.104.5.30.33611 *.*
7. Using vi editor, modify .inputparms_install.scs Here is an example with pointers for .inputparms_install.scs
bash-2.05# vi .inputparms_install.scs ".inputparms_install.scs" 143 lines, 4004 characters #SCS INPUT PARAMETERS FILE for SCS 5.1 #This file is used to read all the required input for SCS Silent new installation #Please read the Installtion IM before changing the parameters #General rules while editing this file #DO NOT LEAVE ANY WHITE SPACES AFTER THE = #USE ALL LOWER CASE LETTERS, for example y, n, /opt/shasta etc #THIS FILE WILL CONTAIN PASSWORDS for SOLID, LDAP #DO NOT CHANGE THE TAGS #DO NOT LEAVE ANY REQUIRED PARAMETERS EMPTY #Install parameters #Please change the following parameters if you are installing #Where do you want to install SCS #This should be your present working directory #Default is /opt/shasta/scs SCSHomeDir=/opt/shasta/scs #Is LDAP running on this Server? Answer y or n #Default is set to n LDAPInstalled=n #If LDAP not installed, would you like to install? Answer y or n #Default is set to y # For migration and Fresh Installation the value is y InstallLdap=y #Name of the directory server tar file #Copy it to the scs head directory LdapTar=directory-5[1].1sp3-us.sparc-sun-solaris2.8.tar #For LDAP specify directory below #Default is SCS root directory /opt/shasta/ldap #Specify the path where LDAP is installed currently #Or for fresh installation without migration LDAPPath=/opt/shasta/ldap
411-5221-309
Standard
06.30 March 10, 2010
707
#LDAP, Existing and new Installation specify port here #Default is set to 389. Do not change this unless required LDAPPort=389 #LDAP, Directory Server Name. #You should change "xxxxxx" by the name of LDAPServer. E.g : If your server name is "zrc2s036" , this parameter is "slapdzrc2s036" LDAPServerName=slapd-scs-sun44 #LDAP IP Address, where it is installed #Default is set to localhost. Local IP address is also ok LDAPhost=localhost #SCS BAckup Directory #Default is SCS root $head/backup SCSBackupDir=/opt/shasta/scs/backup #Do you want to start SCS processes at boot time? #Default is set to y. Answer y or n StartSCSatBoot=y #Do you want to configure an user for collecting Perf data #Default is y. Answer y or n ConfigPerfUser=y #What is the name of the user to be configured for Perf data #Default is pmuser PerfUserName=pmuser #Do you want to install Corba Server #Default is y, Answer y or n #If you are NOT interested in installing Corba you can ignore all other corba parms InstallCorbaServer=y #Corba Tar file name and its location. Path and name #Default location is SCS Root directory #corba tar file name is always scs_corba_server.tar CorbaTarFile=/opt/shasta/scs/scs_corba_server.tar #Installation directory for Corba #Default is SCS ROOT directory for SCS. CorbaInstallDir=/opt/shasta/scs #Corba IP Address #Default is localhost CorbaIPAddress=localhost #Corba Orb IP Address #Default is default CorbaOrbIPAddress=default #Which Corba Port will be used #Default is 0 CorbaPORT=0 #How many days do you want to retain the CSV Files #Default is 4 CSVRetainDays=4 #Ignore these parameters if you are upgrading #These are only required for Installation #Install the following servers #Default is yes to all servers #If you are installing Log server, pull server must also be installed
GPRS/UMTS
708

#Answer y or n InstallDomainServer=y InstallPullServer=y InstallRegionServer=y InstallLogServer=y
#Which Scale of Deployment is to be installed #1 for Large, 2 for Medium, 3 for small #Default is 1 #Refer to NTP for more details SCSDeployLevel=3 #Give the Region ID #Default is 1 SCSRegionID=1 #Input for Ports for Log (Accounting and Logging) and Pull Server SCSPullServerPort=4321 SCSLogLServerPort=4322 SCSLogAServerPort=4323 #LDAP Admin user #Do not change this, accept the default LDAPAdminUser=uid=admin,ou=Administrators,ou=TopologyManagement,o =NetscapeRoot #LDAP Root Point #User would have created this using the ldap admin #example root point looks like uid=uldap,ou=People,o=us.nortel.com LDAPRootPoint=uid=UShasta,ou=People,o=tma.com.vn #LDAP Root DN Password #This is the rootDn's(cn=Directory Manager) LDAPRootPassword=dmanager #LDAP Admin passwd LDAPAdminPassword=admin #Solid DB Admin password SolidDBPassword=admin
<<End of .inputparms_install.scs file>>
8. Execute setup.sh Here is an example capture.

bash-2.05# cd /opt/shasta/scs bash-2.05# ls directory-5[1].1sp3-us.sparc-sun-solaris2.8.tar scs_corba_server.tar.Z bash-2.05# uncompress scs_corba_server.tar.Z bash-2.05# zcat scsserver.tar.Z |tar -xvf -
scsserver.tar.Z
bash-2.05# ./setup.sh 5.9 is a supported Solaris version Logged in as User root Silent procedure is selected /opt/shasta/scs/install/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled This program will install Nortel Service Creation System. Version SCS GGSNS6.0_SCS6.0(17)
411-5221-309
Standard
06.30 March 10, 2010
709
***************************************************************** **** * SCS 5.0 requires IPlanet LDAP 5.1. If you are not running IPlanet * * LDAP 5.1, please upgrade the LDAP server before starting the SCS * * Installation. Please refer to the SCS installation document and * * SCS Release Notes for details on upgrading the Directory Server. * * * * SCS and LDAP require Solaris Recommended Patches. * * Make sure that the latest patches have been installed * * If you are not sure, please abort the setup and check Patch level * * Restart the setup.sh script after checking the patch level * ***************************************************************** **** You have the following options: (C) Create a new SCS Server installation (U) Upgrade the current SCS Server (A) Abort this installation Please enter (C)reate, (U)pgrade or (A)bort? [A]: C Found the parameters File, /opt/shasta/scs/.inputparms_install.scs Reading input Parameters from /opt/shasta/scs/ .inputparms_install.scs, Please wait Reading the input parameters and Validating... LDAP parameters will only be validated if the LDAP is installed on the localhost LDAP parameters are not being validated now Checking if the LDAP Schema files are present LDAP Schema Files are present in /opt/shasta/scs
================================================================= = The Following Parameters are read from the /opt/shasta/scs/ .inputparms_install.scs ================================================================= = SCS Will be installed in the following directory: /opt/shasta/ scs SCS processes will run after the reboot : y SCS Backup directory will be : /opt/shasta/ scs/backup SCS Pull Server port is : 4321 SCS Log Log Port is : 4322 SCS Log Acc Port is : 4323 SCS Deployment Profile is : 3 SCS Region ID is : 1 SCS Domain Server installed : y SCS Region Server installed : y SCS Pull Server installed : y SCS Log Server installed : y
GPRS/UMTS
710

SCS Solid DB Password is LDAP is installed on this Server Install New LDAP on this Server Is CSV user set on this Server Name of the User to collect the CSV files Days CSV files will be preserved Install Corba Server on this Server Corba Installation directory Corba file location and name scs/scs_corba_server.tar Corba Server will be installed in Corba Server IP Address Corba Server ORB IP Corba Port Please If the Change script

admin n y y pmuser 4 y : /opt/shasta/scs : /opt/shasta/ : : : : /opt/shasta/scs localhost default 0 : : : : : : :
check the input parameters and confirm input is not right, quit by answering n the /opt/shasta/scs/.inputparms_install.scs and restart the if you answer n
Do you want to continue (Y/N)? [N]: Y User accepted the parmeters, continuing with new SCS will be installed in /opt/shasta/scs. Checking the available space ... Required space 106636 Kbytes. Available space 14740672 Kbytes. Found enough space to install SCS. Copying the required files ... /opt/shasta/scs/bin/LDAPWatch-disable: LDAPWatch is already disabled LDAP Installation..... /opt/shasta/ldap ============================== iPlanet Directory Server 5.x installation begins! ============================== scs-sun44 tma.com.vn Unpacking ... Start installation, please wait... Installing Netscape core components Installing Server Core Components Installing iPlanet Directory Suite Installing Administration Services Installing nsPerl Installing PerLDAP Extracting Netscape core components ... Extracting Server Core Components ... Extracting Core Java classes ... Extracting Java Runtime Environment ... Extracting iPlanet Directory Server ... Extracting iPlanet Directory Server Console ... Extracting iPlanet Administration Server ... Extracting Administration Server Console ... Extracting nsPerl 5.005_03 ... Extracting PerLDAP 1.4.1 ... [slapd-scs-sun44]: starting up server ... [slapd-scs-sun44]: [07/Aug/2007:13:52:16 -0700] - iPlanetDirectory/5.1 Service Pack 3 B2003.324.1439 starting up [slapd-scs-sun44]: [07/Aug/2007:13:52:18 -0700] - slapd started. Listening on all interfaces port 389 for LDAP requests
411-5221-309
Standard
06.30 March 10, 2010
711
Your new directory server has been started. Created new Directory Server Start Slapd Starting Slapd server configuration. Success Slapd Added Directory Server information to Configuration Server. Configuring Administration Server... Your parameters are now entered into the Administration Server database, and the Administration Server will be started. Changing ownership to admin user root... Setting up Administration Server Instance... Configuring Administration Tasks in Directory Server... Configuring Global Parameters in Directory Server... iPlanet-WebServer-Enterprise/6.0SP2 B01/06/2003 22:24 warning: daemon is running as super-user [LS ls1] http://scs-sun44.tma.com.vn, port 33611 ready to accept requests startup: server started successfully Installation is complete. See /opt/shasta/ldap/setup/setup.log for possible errors. Schema update, please wait... Complete schema update Creating LDAP Root Point adding new entry uid=UShasta,ou=People,o=tma.com.vn This machine currently has 2315M of virtual memory available. We need to install Solid database server on this host. checking if snmp default port 5001 has been used, please wait ... snmp prxy will use port 5001. checking if TrapDaemon default port 5002 has been used, please wait ... TrapDaemon will use port 5002. We need to collect the LDAP information for the Domain/Pull/Log Server.
Installing the Solid Database Server ... [1] 1196 Start the solid server .... Solid Server is running ... Creating database tables for the SCS Domain Server ... 08-Aug-2007 03:53:01 063 INFO ldap.connection.info: localhost,389,uid=admin,ou=Administrators,ou=TopologyManagement,o =NetscapeRoot,uid=UShasta,ou=People,o=tma.com.vn 08-Aug-2007 03:53:01 626 INFO sni.7: Created a new LDAP connection... 1 Adding Patch Server information in SCS Domain Server database ... Enabling tftp - tftp already enabled, no changes made Creating database tables for the SCS Region Server ... Adding Pull Server information in SCS Domain Server database ...
GPRS/UMTS
712
Adding Log Server information in SCS Domain Server database ... We have created the required SCS database tables. Now we will shutdown the Solid database server. Stopping Solid Database Server:.Stopped [1] + Done /opt/shasta/scs/opt/solidSolaris/bin/ solid -f -c ... LDAP schema files updated successfully Now stopping and restarting LDAP server slapd-scs-sun44 ... To generate CSV formatted accounting data, a user id must be designated as the owner of the generated files. It is recommended that the user id not be the root user. The ownership of any existing CSV formatted accounting data file will also be changed to this user id. The user id, pmuser, already exists and will be used by the SCS Log Server process for CSV generated files. Extracting Corba files, please wait... This program will install SCS Corba Server version SCS GGSNS6.0_SCS6.0(17) SCS Corba Server will be installed in /opt/shasta/scs. Found Domain server installed. New SCS Corba server version matches installed SCS version. Continuing... SCS Corba Server will be installed in /opt/shasta/scs. Checking the available space... Required space 61440 Kbytes. Available space 14192560 Kbytes. Found enough space to install SCS Corba Server. Copying the required files...... SCS Corba Server is now installed. You can use /opt/shasta/scs/bin/SCSCorbaServer to run SCS Corba Server. The installation logs are saved in /opt/shasta/scs/lib/install/ *.log. INSTALLATION IS COMPLETED SUCCESSFULLY The following SCS server(s) are currently installed on this machine: Version SCS GGSNS6.0_SCS6.0(17) SCS SCS SCS SCS SCS SCS Domain Server (LDAP Server IP = localhost) Region Server (Region ID = 1) Monitor Server Pull Server (Listening Port = 4321) Log Server (Logging Port = 4322, Accounting Port = 4323) CORBA Server
411-5221-309
Standard
06.30 March 10, 2010
713
You can use '/opt/shasta/scs/bin/SCSAdmin start' to run SCS Server. bash-2.05# /opt/shasta/scs/bin/SCSAdmin start /opt/shasta/scs/bin/SCSWatch-disable: SCSWatch is already disabled /opt/shasta/scs/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled /opt/shasta/scs/bin/SCSDiskUsageMonitor-disable: SCSDiskUsageMonitor is already disabled /opt/shasta/scs/bin/SCSCleanXmlExportFiles-disable: SCSCleanXmlExportFiles is already disabled [1] 1615 Starting Solid Database Server:..Started [2] 1639 Starting SCS Daemon:...Started [3] 1658 Starting SCS Domain server:..............Started [4] 1711 Starting SNMP Proxy:.Started [5] 1720 Starting SCS CORBA Server:............................Started [6] 1785 Starting SCS Region server:.................Started [7] 1847 Starting SCS Monitor server:..................Started [8] 1912 Starting SCS Trap daemon:..................Started [9] 1978 Starting SCS Pull Server:........Started [10] 2013 Starting SCS Log Server:......Started ------------------------------------------Nortel Service Creation System Server Version SCS GGSNS6.0_SCS6.0(17) ------------------------------------------Adding SCSCleanLogcsv first time Added SCSCleanLogcsv to crontab Adding SCSWatch to Crontab for first time. Added SCSWatch to crontab Adding SCSDiskUsageMonitor first time Added SCSDiskUsageMonitor to crontab Adding SCSCleanXmlExportFiles first time Added SCSCleanXmlExportFiles to crontab
<<End of capture>>
9. Verify iPlanet server processes are running. Refer to Verify LDAP/ iPlanet server and admin process status on page 209 for details. If iPlanet and admin processes are not running, start the processes following Start the LDAP / iPlanet server. Enable LDAPWatch on page 205 10. Start SCS server processes. Refer to Start SCS server. Enable SCSWatch and LDAPWatch on page 201 for details.
GPRS/UMTS
714
Appendix Q: Fast Feature Migration Script examples 58

Here are screen captures for the following fast feature migration scripts. G501_FF01435785ACT_INF - L2TP Cabcharge on page 714 G501_FF01567650ACT_IPCMC - TCP MSS Clamping on page 717 G501_01407739ACT_INF and G501_01595094AACT_AAA on page 719 SGSN Change Partial Billing - G411_01339974AACT_GTPACCT on page 721 Consecutive Parking Meter feature on page 723
G501_FF01435785ACT_INF - L2TP Cabcharge
58
Manual SCS Pre-upgrade steps a. Verify if the patch G501_FF01435785ACT_INF has been activated. Please refer to Verify patch status information on page 224 for more details. Note: If the patch has been activated, proceed to the next step. Otherwise, skip this checkpoint. b. Login to the SCS client as a connection ISP (ISPs except Gn, Ga and LI ISP). c. From Access Properties, APN Group, select the APN and click Edit. i. Click on the Access tab. ii. Under Anonymous Radius Authentication, verify if options MSISDN or User name radio buttons are selected. Note, if one of the options are selected, a post SCS and GGSN upgrade steps must be executed. iii. If the User name option has the reserved strings - MSISDN or IMSI, make a note of the APN name. Note, if the User name has the reserved strings in the User name, a post SCS and GGSN upgrade steps must be executed. d. Repeat the above steps for all APNs configured on the APN Group. Also repeat the steps for all connection ISPs.
411-5221-309
Standard
06.30 March 10, 2010
715
Manual SCS post upgrade script execution Note: This procedure need not be executed if SCSUpgradeL2TPCabcharge.sh has been executed. i. Login to the SCS client and connection ISP (ISPs except Gn, Ga and LI ISPs). ii. From Access Properties, select APN Group. This will list the APNs configured on the ISP in the right pane. iii. Select each APN, and click the Access tab. iv. If Under Anonymous RADIUS Authentication: Step ii is true: If MSISDN or User Name was selected, check options - Add APN as domain - Override Mobile supplied username Step iii is true: If Username is set as string MSISDN, then select the radio button option MSISDN. Step iii is true: If Username is set as string IMSI, then select the radio button option IMSI. Repeat the above steps for all APNs with Step ii or Step iii under G501_FF01435785ACT_INF - L2TP Cabcharge on page 714 true.
SCS post upgrade script execution Execute the script: SCSUpgradeL2TPCabcharge.sh to update the APNs. - Change directory to <SCS6.0_ROOT>/bin
# cd /opt/shasta/scs6.0/bin # ./SCSUpgradeL2TPCabcharge.sh
- Here is an example:
# ./SCSUpgradeL2TPCabcharge.sh
*************** SCS UPGRADE L2TP CABCHARGE ******************* * This script will upgrade APN(s) on ISP(s) to set Anonymous Radius Authentication * * options as below: * * - If Anonymous Radius Authentication option is 'MSISDN' or 'User name' *
GPRS/UMTS
716
* -> Enable 'Add APN as domain' and 'Override Mobile supplied username' options * * - If User name has 'msisdn' * * -> set Anonymous Radius Authentication option to MSISDN * * - If User name has 'imsi' * * -> set Anonymous Radius Authentication option to IMSI * * * * Run the script only when the patch G501_FF01435785ACT_INF is activated on devices. * * * ***************************************************************** Do you want to continue? (Y)es or (N)o: y The upgrade L2TP Cabcharge is starting... G501_FF01435785ACT_INF patch rule checking... ISP_ID --3 4 5 6 ISP_NAME -----isp-ga isp-internet isp-blackberry isp-data
Enter ISP IDs to upgrade [all]:all
The upgrade will continue with below information: Selected ISP IDs: 3 4 5 6 Do you want to continue? (Y)es or (N)o: y Connect to server..... 11-Apr-2008 13:52:50 516 INFO session.client.connect: 127.0.0.1:1099/0,com.shasta.spm.server.SPMServer_Stub[RemoteStub [ref: [endpoint:[47.104.5.30:1100](remote),objID:[4e79f1:1193ed248db:8000, 0]]]] 11-Apr-2008 13:52:50 519 INFO session.client.serverFound: 127.0.0.1:1099/0,com.shasta.spm.server.SPMServer_Stub[RemoteStub [ref: [endpoint:[47.104.5.30:1100](remote),objID:[4e79f1:1193ed248db:8000, 0]]]] Sending message to SCS Clients... The upgrade will start in 1 minute Sleep for 1 minutes............. Skipped APN aaa.bb.net. "Anonymous Radius Authentication" is "IMSI" or disabled ... ... Updated APN uimsi Updated APN umsisdn Updated APN username Skipped APN ccc.net. "Anonymous Radius Authentication" is "IMSI" or disabled ... ...
411-5221-309
Standard
06.30 March 10, 2010
717
11-Apr-2008 13:53:53 613 INFO table.client.disconnectAll: 127.0.0.1:1099/1 Upgrade L2TP Cabcharge has completed successfully The upgrade proccess log file path: /opt/shasta/scs6.0/log/ servers/SCSUpgrageAPN/UpgradeL2TPCabcharge-041108_135215.log
G501_FF01567650ACT_IPCMC - TCP MSS Clamping
58
Manual SCS Pre-upgrade steps a. Verify if patch G501_FF01567650ACT_IPCMC has been actived. For details on patch verification, please refer to Verify patch status information on page 224. b. If the above patch has been activated, login to the GGSN and issue the command:
show tcp mss
Here is an example:
ggsn-158(SHASTA)# show tcp mss Thu 24-Jan-2008 12:33:37 CST TCP MSS value=1412
Note: The default value is 1412. Valid values are: 0, 512 - 1460 c. Make a note of the MSS value from the show tcp mss command. This value will be needed again after SCS 6.0 upgrade and prior to GGSN 6.0 upgrade. d. Mark a check in the last column in the checkpoint table after these steps are executed. Manual SCS post upgrade script execution Execute the following steps if Checkpoint 1 item 12, page 95 was executed. a. Login to the SCS client as a connection ISP (ISPs excluding Gn and Ga ISPs).
b. Click on Access Properties on the left pane, then click on APN Groups. This will list all the APNs configured on the connection ISP in the right pane. c. Select the first APN, then click Edit. This will open the APN Group window with General tab selected.
GPRS/UMTS
718
Under TCP MSS Clamping Settings, enable the checkbox - TCP MSS Clamping Enabled. Under TCP Maximum Segment Size, enter the value saved from show tcp mss output in Checkpoint 1 item 12, page 95.
d. Repeat the above step for all APNs in the ISP. e. Repeat the steps in this checkpoint for other connection ISPs configured on the GGSN. Repeat the above steps for other GGSNs managed by the SCS server. SCS post upgrade script execution Execute the script: SCSUpgradeTCPMSSClamping.sh to update the APNs. - Change directory to <SCS6.0_ROOT>/bin
# cd /opt/shasta/scs6.0/bin # ./SCSUpgradeTCPMSSClamping.sh
# ./SCSUpgradeTCPMSSClamping.sh
****************** UPGRADE TCP MSS CLAMPING FEATURE ************** * - This script will upgrade APN's on ISP(s) to enable TCP MSS Clamping option and * * set value for 'TCP Maximum Segment Size'. * * * * - Run the script only when the patch G501_FF01567650ACT_IPCMC is activated on devices. * * * ***************************************************************** Do you want to continue? (Y)es or (N)o: y The upgrade TCP MSS Clamping is starting... G501_FF01567650ACT_IPCMC patch rule checking... ISP_ID --3 4 5 6 ISP_NAME -----isp-ga isp-internet isp-blackberry isp-data
Enter ISP IDs to upgrade [all]:all Please input the TCP Maximum Segment Size [1424]:1469 Invalid value! Valid range of TCP Maximum Segment Size is [536..1460] Please input the TCP Maximum Segment Size [1424]:1460
411-5221-309
Standard
06.30 March 10, 2010
719
The upgrade will continue with below information: Selected ISP IDs: 3 4 5 6 TCP Maximum Segment Size is set to: 1460 Do you want to continue? (Y)es or (N)o: y Connect to server..... 11-Apr-2008 13:58:25 624 INFO session.client.connect: 127.0.0.1:1099/0,com.shasta.spm.server.SPMServer_Stub[RemoteStub [ref: [endpoint:[47.104.5.30:1100](remote),objID:[4e79f1:1193ed248db:8000, 0]]]] 11-Apr-2008 13:58:25 628 INFO session.client.serverFound: 127.0.0.1:1099/0,com.shasta.spm.server.SPMServer_Stub[RemoteStub [ref: [endpoint:[47.104.5.30:1100](remote),objID:[4e79f1:1193ed248db:8000, 0]]]] Sending message to SCS Clients... The upgrade will start in 1 minute Sleep for 1 minutes............. Updated APN aaa.net Updated APN bbb.net ... ... Updated APN ccc.net 11-Apr-2008 13:59:38 683 INFO table.client.disconnectAll: 127.0.0.1:1099/1 Upgrade TCP MSS Clamping has completed successfully The upgrade proccess log file path: /opt/shasta/scs6.0/log/ servers/UpgrageAPNlog/UpgradeTCPClamping-041108_135729.log urc2y1th#
G501_01407739ACT_INF and G501_01595094AACT_AAA
58
Manual SCS post upgrade script execution If the patch G501_01407739ACT_INF is deactivated in 5.0.1, no need to change the default value on the APN. The default value currently is "RFC compliant default behavior". If the patch G501_01407739ACT_INF is active in 5.0.1, the option "Send a padded and encrypted blank character as password to RADIUS" should be selected for all the APN's under each ISP. If both patches G501_01407739ACT_INF and G501_01595094AACT_AAA are active in 5.0.1, " Send only password attribute and no password value" should be selected for all the APN's under each ISP.
SCS post upgrade script execution
GPRS/UMTS
720
Execute the script: SCSUpgradeRadiusAuthentication.sh to update the APNs. - Change directory to <SCS6.0_ROOT>/bin
# cd /opt/shasta/scs6.0/bin # ./SCSUpgradeRadiusAuthentication.sh
# ./SCSUpgradeRadiusAuthentication.sh
**************** UPGRADE RADIUS AUTHENTICATION ******************* * - This script will upgrade APN(s) on ISP(s) to set Radius Authentication Type to * * 'Send a padded and encrypted blank character as password to RADIUS' for ISP has only * * G501_01407739ACT_INF patch is activated. * * and to 'Send only password attribute and no password value' for ISP has both of * * G501_01407739ACT_INF and G501_01595094AACT_AAA patches are activated. * * * * - Run the script only when G501_01407739ACT_INF patch is activated or both of * * G501_01407739ACT_INF and G501_01595094AACT_AAA patches are activated. * * * ***************************************************************** Do you want to continue? (Y)es or (N)o: y The upgrade Radius Authentication is starting... G501_01407739ACT_INF patch rule checking... G501_01595094AACT_AAA patch rule checking... List of isps have both G501_01407739ACT_INF and G501_01595094AACT_AAA patches are activated The Radius Authentication Type on APN(s) of these isps will be upgrade to'Send only password attribute and no password value' ISP_ID ISP_NAME -------3 isp-ga 4 isp-internet 5 isp-blackberry 6 isp-data Enter ISP ID to upgrade [all]:4 The upgrade will continue with below information: Selected ISP IDs: 4 Do you want to continue? (Y)es or (N)o: y Connect to server..... 11-Apr-2008 14:07:49 517 INFO session.client.connect: 127.0.0.1:1099/0,com.shasta.spm.server.SPMServer_Stub[RemoteStub [ref:
411-5221-309
Standard
06.30 March 10, 2010
721
[endpoint:[47.104.5.30:1100](remote),objID:[4e79f1:1193ed248db:8000, 0]]]] 11-Apr-2008 14:07:49 521 INFO session.client.serverFound: 127.0.0.1:1099/0,com.shasta.spm.server.SPMServer_Stub[RemoteStub [ref: [endpoint:[47.104.5.30:1100](remote),objID:[4e79f1:1193ed248db:8000, 0]]]] Sending message to SCS Clients... The upgrade will start in 1 minute Sleep for 1 minutes............. Updated APN aaa.net Updated APN bbb.net ... ... Updated APN ccc.net Skipped APN uimsi. "Radius Authentication Type" is disabled Skipped APN umsisdn. "Radius Authentication Type" is disabled Skipped APN username. "Radius Authentication Type" is disabled 11-Apr-2008 14:08:58 409 INFO table.client.disconnectAll: 127.0.0.1:1099/1 Upgrade Radius Authentication Type has completed successfully The upgrade proccess log file path: /opt/shasta/scs6.0/log/ servers/SCSUpgrageAPN/UpgradeRadiusAuthentication041108_140716.log
SGSN Change Partial Billing - G411_01339974AACT_GTPACCT

Manual SCS post upgrade script execution
58
1. Login to the SCS client using Device Owner privilege and select the Patch icon on the left image panel. 2. Select the Device tab and click on the Region name. Make a note of the active patch profile applied to the GGSN. 3. Select the Profile tab, click on the active patch profile and click Edit. 4. Click the drop down box next to Patchable Load. Select GGSNS4.1.1. 5. Verify if patch G411_01339974AACT_GTPACCT has been added to the patch profile and is activated. 6. If the above patch has been applied and activated, the following steps needs to be executed in order to maintain the same behavior in GGSN 5.0.x as GGSN 4.1.1. a. Login as the connection ISP. b. From Access Properties-> APN Groups, select an APN and click Edit. c. Select Accounting/ Billing tab. If Max SGSN Change Partial Billing checkbox is checked, uncheck it. d. Repeat Step b. and Step c. for all APNs in the connection ISP. Repeat Step 6 for all connection ISPs.
GPRS/UMTS
722

# cd /opt/shasta/scs6.0/bin # ./SCSUpgradeSGSNChangePartialBilling.sh SCS Upgrade SGSN Change Partial Billing ************* UPGRADE SGSN CHANGE PARTIAL BILLING ******** * - This script will upgrade APN(s) on ISP(s) to disable 'MAX SGSN Change Partial* * Billing' option. * * * * - Run the script only when the patch G411_01339974AACT_GTPACCT is activated on devices.* * * *********************************************************** ******************************* Do you want to continue? (Y)es or (N)o: y The upgrade SGSN Change Partial Billing is starting... G411_01339974AACT_GTPACCT patch rule checking...
ISP_ID ISP_NAME -------290 gn-139 291 gi-139 292 ga-139 361 gre-139 390 l2tp-139 419 li_default_isp 433 vlan-139 444 vprn Enter ISP ID to upgrade [all]:361
The upgrade will continue with below information: Selected ISP IDs: 361 Do you want to continue? (Y)es or (N)o: y Connect to server..... 23-Apr-2008 16:39:03 426 INFO session.client.connect: 127.0.0.1:1099/ 0,com.shasta.spm.server.SPMServer_Stub[RemoteStub [ref: [endpoint:[47.104.6.19:1100](remote),objID:[10e790c:1195e63 bd41:-8000, 0]]]] 23-Apr-2008 16:39:03 428 INFO session.client.serverFound: 127.0.0.1:1099/ 0,com.shasta.spm.server.SPMServer_Stub[RemoteStub [ref: [endpoint:[47.104.6.19:1100](remote),objID:[10e790c:1195e63 bd41:-8000, 0]]]] Sending message to SCS Clients...
411-5221-309
Standard
06.30 March 10, 2010
723
The upgrade will start in 1 minute Sleep for 1 minutes............. Updated APN gre Updated APN grevpnauthdhcp Updated APN grevpnauthstatic 23-Apr-2008 16:40:05 066 INFO table.client.disconnectAll: 127.0.0.1:1099/1 Upgrade SGSN Change Partial Billing has completed successfully The upgrade proccess log file path: /opt/shasta/scs6.0/log/ servers/SCSUpgrageAPN/SCSUpgradeSGSNChangePartialBilling042308_163846.log
Consecutive Parking Meter feature

58
# ./upgradeCBBPolicyByAddingContentTypeProfile.sh ************** UPGRADE CBB POLICY ************************* * This script will generate Content Type Profile and associate to the CBB Policy * * SCSBackup will be run automatically before running upgrade CBBPolicy script. * * TIME EVENT BILLING or CTP TIME EVENT BILLING SOCs must be enabled before * * running this script. * * Restart Server as a recommendation for affect after running this script!!! * * * ***********************************************************
Do you want to continue? (Y)es or (N)o: y <- type y to proceed The upgrade is starting... Coupon Profile data checking... Backup system Timestamp: GGSNS6.0_SCS6.0_47_20081208062839 Starting DomainAndRegion Backups sendMessageToClients: SCS BACKUP process will start in 5 seconds. All provisioning will be paused during the process. Please save your work SPMAdmin Backup in RegionCount+1: 1 SPMAdmin Backup in SPMAdmin Backup in SPMAdmin Backup in SPMAdmin Backup in SPMAdmin Backup in progress for servers serverCount: 0 progress: progress: progress: progress: progress:
GPRS/UMTS
724
SPMAdmin Backup in progress: SPMBackupAndRestoreMsgListenerImpl.showBackupRestoreStatus server areaId 0 status: SUCCESS SPMAdmin.displayBackupResoreStatus BACKUP server areaId:0 serverCount:1 status: SUCCESS SPMAdmin.displayBackupResoreStatus server areaId:0 BACKUP succeeded SPMAdmin.displayBackupResoreStatus backupPath: /opt/shasta/ scs6.0/backup timeStamp: GGSNS6.0_SCS6.0_47_20081208062839 SPMAdmin Backup finished. serverCount: 1 RegionCount+1: 1 Enable new Clients to login Enabled Clients to provision No match It is a good back up file. Disable Client provisioning to begin upgrade CBB Policies SCS CBB policy upgrading application starts... ISP id: 7 Create Content Type Profile: cp35 Add Content Type Profile: cp35 to CBB Policy: internet.cbb35.tf Add Content Type Id: 1 to Content Type Profile: cp35 Add Content Type Profile: cp35 to CBB Policy: internet.cbb36.tf ISP id: 9 Create Content Type Profile: cp36 Add Content Type Profile: cp36 to CBB Policy: blackberry.cbb1.tf CBB policies were upgraded successfully Enable Client provisioning The upgrade proccess log file path: /opt/shasta/scs6.0/ log/servers/upgradeContentProfile-DATE120808_TIME062833.log CBB policies were upgraded successfully ***************** RESTART WARNNING!!!********************** * Restart Server as a recommendation for affect after running this script!!! * ***********************************************************
Do you want to retstart server? (Y)es or (N)o: y <- type y to restart the SCS server processes The Server is restarting... /opt/shasta/scs6.0/bin/SCSWatch-disable: SCSWatch is already disabled /opt/shasta/scs6.0/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled Removed SCSDiskUsageMonitor from crontab Removed SCSCleanXmlExportFiles from crontab [1] 4108 Stopping SCS CORBA Server:.[1] + Done /opt/ shasta/scs6.0/opt/jre/bin/java ...
411-5221-309
Standard
06.30 March 10, 2010
725
.Stopped [1] 4122 Stopping SCS Log Server:.[1] + Done /opt/ shasta/scs6.0/opt/jre/bin/java ... .Stopped [1] 4136 Stopping SCS Pull Server:.[1] + Done /opt/ shasta/scs6.0/opt/jre/bin/java ... .Stopped [1] 4150 Stopping SCS Trap Daemon:.[1] + Done /opt/ shasta/scs6.0/opt/jre/bin/java ... .Stopped [1] 4164 Stopping SCS Monitor Server:.[1] + Done / opt/shasta/scs6.0/opt/jre/bin/java ... Stopped [1] 4172 Stopping SCS Region Server:.[1] + Done /opt/ shasta/scs6.0/opt/jre/bin/java ... ........................................................... Timeout, killing it! Stopping SNMP Proxy:.Stopped [1] 4579 Stopping SCS Domain Server:.[1] + Done /opt/ shasta/scs6.0/opt/jre/bin/java ... Stopped [1] 4587 Stopping SCS Daemon:.[1] + Done /opt/shasta/ scs6.0/opt/jre/bin/java ... .Stopped Stopping Solid Database Server:.Stopped [1] 4642 Starting Solid Database Server:.Started [2] 4660 Starting SCS Daemon:.Started [3] 4673 Starting SCS Domain server:........Started [4] 4708 Starting SNMP Proxy:Started [5] 4714 Starting SCS CORBA Server:.........Started [6] 4757 Starting SCS Region server:......Started [7] 4786 Starting SCS Monitor server:......Started [8] 4815 Starting SCS Trap daemon:......Started [9] 4845 Starting SCS Pull Server:...Started [10] 4865 Starting SCS Log Server:..Started ------------------------------------------Nortel Service Creation System Server Version SCS GGSNS6.0_SCS6.0(47)
GPRS/UMTS
726
------------------------------------------Adding SCSCleanLogcsv first time Added SCSCleanLogcsv to crontab Adding SCSWatch to Crontab for first time. Added SCSWatch to crontab Adding SCSDiskUsageMonitor first time Added SCSDiskUsageMonitor to crontab Adding SCSCleanXmlExportFiles first time Added SCSCleanXmlExportFiles to crontab
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs
727
Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs

The following are the guide lines to edit the .inputparms_install.scs file: General rules while editing this file
DO NOT LEAVE ANY WHITE SPACES AFTER THE = USE ALL LOWER CASE LETTERS, for example y, n, /opt/shasta etc THIS FILE WILL CONTAIN PASSWORDS for SOLID, LDAP DO NOT CHANGE THE TAGS DO NOT ADD ANY NEW LINES for Tags, change the existing value DO NOT LEAVE ANY REQUIRED PARAMETERS EMPTY
59
Procedure
1. Identify what are all the SCS Servers to be installed, whether corba is installed or not etc. This information will be required to edit the <SCS_ROOT>/.inputparms_install.scs file. Note: Normally all the SCS Servers, Domain, Region, Pull and Log servers will be installed on the same physical server. Also, the LDAP will be installed on the same physical server. If Corba is installed it will also be installed in the <SCS_ROOT> directory. Please check with the customer if the SCS is installed differently) The details of what servers installed, LDAP port number used, LDAP password etc will be available in this file. 2. The following table shows the details of the required tags for installation. Please carefully look at each tags listed and change the values in the <SCS_ROOT>/.inputparms_install.scs file.
Table 36 SCS 6.0 .inputparms_install.scs File S.No 1 2 Tag Name SCSHomeDir LDAPInstalled Value for the Tag This is the <SCS_ROOT> directory. This tag contains the value, if the LDAP is installed on this physical server or not. Details E.g.: /opt/shasta/scs. This parameter will be validated. Answer should be y or n. If the LDAP is installed on same physical server, the answer is y
GPRS/UMTS
728
Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs Nortel Networks Confidential
Table 36 SCS 6.0 .inputparms_install.scs File 3 InstallLdap This tag contains the value which indicates if LDAP needs to be installed. This tag contains the name of the directory server tar file. The tag contains the LDAP path on the server. This tag contains the LDAP port value. The tag contains the name of the LDAP server Answer should be y or n.If you would like to install the LDAP 5.1 the answer should be y. The name of the LDAP tar file that comes on the SCS installation CD. This is the path for new install LDAP 5.1 Default value for LDAP port is 389. The server name will typically be slapd-xxxxxxx. This parameter is used when performing the installation with the installed LDAP 5.1 If LDAP is installed on the same server, this tag will contain the value localhost. If LDAP is installed on a different server, provide with the IP address of the server.
LdapTar
5 6 7
LDAPPath LDAPPort LDAPServerName
LDAPhost
The tag contains the LDAP host name. Note: If LDAP is installed on the local host, use localhost as the value for this tag. Do not enter the IP address of the local host.
SCSBackupDir
This tag contains the value for the backup directory for SCS.
By default, the SCS backup directory should be in <SCS_ROOT>/backup. No validation is done for this parameter. Answer should be y or n. Default answer is y
10
StartSCSatBoot
This contains the value to determine whether to start the SCS processes after very reboot. This tag contains determines whether the customer wants to configure an user to collect the performance data. For example, the user could be pmuser. This tag contains the name of the user to be created for collecting performance data.
11
ConfigPerfUser
Answer to this tag should be y or n. Default answer is y Ignore the tag in row 12, if the answer to this tag is n.
12
PerfUserName
Default value for this tag is pmuser. This tag can be ignored if the answer to the tag in Row 11 is n
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs Table 36 SCS 6.0 .inputparms_install.scs File 13 InstallCorbaServer This tag determines if the customer uses Corba or not.
729
If customer uses corba, the answer to this question must be y. The default is set to y. Ignore the tags in rows 14,15,16,17,18 if the answer to this tag is n The upgrade procedure requires the Corba file to be copied to <SCS_ROOT> directory. The answer to this question should be <SCS_ROOT>/ scs_corba_server.tar Corba server must be installed in <SCS_ROOT> directory. Answer to this question must be <SCS_ROOT> Default is localhost Default is default Default value is 0. a. If default value (0) is set, the Corba Server will listen to any available port. b. If a static port number is set (for example, configuring firewall), it is highly recommended configuring a specific port (>1023) for SCS Corba Server incoming IIOP requests. The default value is 4. Any CSV files which are older than the value configured for this tag, will be purged by a cron job. Default value is y
14
CorbaTarFile
The tag contains the name and location of the SCS Corba server tar file.
15
CorbaInstallDir
This tag determines where the Corba server should be installed. This tag contains the IP address of the Corba Server. This tag contains the Corba Orb IP address This tag determines which port should be used for the Corba Server to listen to the incoming IIOP (Internet InterORB Protocol) requests.
16 17 18
CorbaIPAddress CorbaOrbIPAddress CorbaPORT
19
CSVRetainDays
This tag contains the no of days the CSV files are retained before purging. This tag contains the value to determine whether to install Domain Server This tag contains the value to determine whether to install Pull Server This tag contains the value to determine whether to install Region Server
20
InstallDomainServer
21
InstallPullServer
Default value is y
22
InstallRegionServer
Default value is y
GPRS/UMTS
730
Table 36 SCS 6.0 .inputparms_install.scs File 23 InstallLogServer This tag contains the value to determine whether to install Log Server This tag contains the value to determine whether to scale of Deployment is to be installed This tag contains the value to determine whether to give the Region ID This tag contains the value to determine whether to input for the port for Pull Server This tag contains the value to determine whether to input for the port for Log Logging Server This tag contains the value to determine whether to input for the port for Log Accounting Server This tag contains the value to configure LDAP server This tag contains the value to set up LDAP root point This tag contains the value of LDAP Root password This tag contains the value of LDAP Admin password This tag contains the value of Solid DB password Default value is y
24
SCSDeployLevel
Default value is 1
25
SCSRegionID
Default value is 1
26
SCSPullServerPort
Default value is 4321
27
SCSLogLServerPort
28
SCSLogAServerPort
29 30 31 32 33
LDAPAdminUser LDAPRootPoint LDAPRootPassword LDAPAdminPassword SolidDBPassword
Do not change this, accept the default Change this tag appropriate with your LDAP system Default value is dmanager Default value is admin Default value is admin
Here is a sample .inputparms_install.scs file.(The snap shot from the file is shown in Italics and the explanation is shown in normal text here)
zrc2s0ns# cat .inputparms_install.scs #SCS INPUT PARAMETERS FILE for SCS 5.1<- Note, the file indicates SCS 5.1. This is a typo error. #This file is used to read all the required input for SCS Silent new installation #Please read the Installtion IM before changing the parameters 411-5221-309 Standard 06.30 March 10, 2010
731
#General rules while editing this file #DO NOT LEAVE ANY WHITE SPACES AFTER THE = #USE ALL LOWER CASE LETTERS, for example y, n, /opt/shasta etc #THIS FILE WILL CONTAIN PASSWORDS for SOLID, LDAP #DO NOT CHANGE THE TAGS #DO NOT LEAVE ANY REQUIRED PARAMETERS EMPTY
#Install parameters #Please change the following parameters if you are installing
#Where do you want to install SCS #This should be your present working directory #Default is /opt/shasta/scs SCSHomeDir=/opt/shasta/scs
#Is LDAP running on this Server? Answer y or n #Default is set to n LDAPInstalled=n
#If LDAP not installed, would you like to install? Answer y or n #Default is set to y # For migration and Fresh Installation the value is y InstallLdap=y
#Name of the directory server tar file #Copy it to the scs head directory LdapTar=directory-5[1].1sp3-us.sparc-sun-solaris2.8.tar
#For LDAP specify directory below GPRS/UMTS Upgrade Manual GGSN6.0
732
Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs Nortel Networks Confidential #Default is SCS root directory /opt/shasta/ldap #Specify the path where LDAP is installed currently #Or for fresh installation without migration LDAPPath=/opt/shasta/ldap
#LDAP, Existing and new Installation specify port here #Default is set to 389. Do not change this unless required LDAPPort=389
#LDAP, Directory Server Name. #You should change "xxxxxx" by the name of LDAPServer. E.g : If your server name is "zrc2s036" , this parameter is "slapd-zrc2s036" LDAPServerName=slapd-xxxxxx
#LDAP IP Address, where it is installed #Default is set to localhost. Local IP address is also ok LDAPhost=localhost
#SCS BAckup Directory #Default is SCS root $head/backup SCSBackupDir=/opt/shasta/scs/backup
#Do you want to start SCS processes at boot time? #Default is set to y. Answer y or n StartSCSatBoot=y
#Do you want to configure an user for collecting Perf data #Default is y. Answer y or n ConfigPerfUser=y
#What is the name of the user to be configured for Perf data
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs #Default is pmuser PerfUserName=pmuser
733
#Do you want to install Corba Server #Default is y, Answer y or n #If you are NOT interested in installing Corba you can ignore all other corba parms InstallCorbaServer=y
#Corba Tar file name and its location. Path and name #Default location is SCS Root directory #corba tar file name is always scs_corba_server.tar CorbaTarFile=/opt/shasta/scs/scs_corba_server.tar
#Installation directory for Corba #Default is SCS ROOT directory for SCS. CorbaInstallDir=/opt/shasta/scs
#Corba IP Address #Default is localhost CorbaIPAddress=localhost
#Corba Orb IP Address #Default is default CorbaOrbIPAddress=default
#Which Corba Port will be used #Default is 0 CorbaPORT=0
#How many days do you want to retain the CSV Files #Default is 4 GPRS/UMTS Upgrade Manual GGSN6.0
734
Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs Nortel Networks Confidential CSVRetainDays=4
#Ignore these parameters if you are upgrading #These are only required for Installation
#Install the following servers #Default is yes to all servers #If you are installing Log server, pull server must also be installed #Answer y or n InstallDomainServer=y InstallPullServer=y InstallRegionServer=y InstallLogServer=y
#Which Scale of Deployment is to be installed #1 for Large, 2 for Medium, 3 for small #Default is 1 #Refer to NTP for more details SCSDeployLevel=1
#Give the Region ID #Default is 1 SCSRegionID=1
#Input for Ports for Log (Accounting and Logging) and Pull Server SCSPullServerPort=4321 SCSLogLServerPort=4322 SCSLogAServerPort=4323
#LDAP Admin user 411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs #Do not change this, accept the default
735
LDAPAdminUser=uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRo ot
#LDAP Root Point #User would have created this using the ldap admin #example root point looks like uid=uldap,ou=People,o=us.nortel.com LDAPRootPoint=uid=UShasta,ou=People,o=us.nortel.com
#LDAP Root DN Password #This is the rootDn's(cn=Directory Manager) LDAPRootPassword=dmanager
#LDAP Admin passwd LDAPAdminPassword=admin
#Solid DB Admin password SolidDBPassword=admin
3. After editing this file, please return back to the SCS installation section.
.inputparms_upgrade.scs
The following are the guide lines to edit the .inputparms_upgrade.scs file: General rules while editing this file
DO NOT LEAVE ANY WHITE SPACES AFTER THE = USE ALL LOWER CASE LETTERS, for example y, n, /opt/shasta etc DO NOT CHANGE THE TAGS DO NOT ADD ANY NEW LINES for Tags, change the existing value DO NOT LEAVE ANY REQUIRED PARAMETERS EMPTY
GPRS/UMTS
736
Procedure
1. Identify what are all the SCS Servers to be upgraded, whether corba is installed or not etc. This information will be required to edit the <SCS_ROOT>/.inputparms_upgrade.scs file. Please check the file <SCS_ROOT>/bin/.scs.config file. Here is the snap shot for the file. The required in this file are in bold. Note: Normally all the SCS Servers, Domain, Region, Pull and Log servers will be installed on the same physical server. Also, the LDAP will be installed on the same physical server. If Corba is installed it will also be installed in the <SCS_ROOT> directory. Please check with the customer if the SCS is installed differently)
# # This file was generated during SCS installation. # Please do not modify manually. # SCSHead=/opt/shasta/scs InstallDomainServer=yes InstallRegionServer=yes InstallMonitorServer=yes InstallPullServer=yes InstallLogServer=yes DomainServerIp=localhost RegionId=1 rollingSCS=y LDAPInstalled=y InstallLdap=n LdapTar=directory-5[1].1sp3-us.sparc-sun-solaris2.8.tar LDAPPath=/opt/shasta/ldap LDAPServerName=slapd-zrc2s0mc LDAPServerIp=localhost LDAPServerPort=389 LDAPMigration=n LDAPMigrationPath=/usr/iplanet/servers LDAPMigrationPort=395 LDAPUsername="uid=admin,ou=Administrators,ou=TopologyManagement,o=Netscape Root" LDAPPassword=admin LDAPRoot="uid=admin,ou=People,o=us.nortel.com" PullListenPort=4321 LogLogPort=4322 LogAccountPort=4323 RegionRootDir=/opt/shasta/scs DBAdminPassword=admin MaximumHeapSize=512 SCSBackup=/opt/shasta/scs/backup DBBackupTimeWait=300 LogUser=pmuser
411-5221-309
Standard
06.30 March 10, 2010
737
The details of what servers installed, whether LDAP is on the local host or not, LDAP port number used, LDAP password etc will be available in this file. This information should be used while editing the file. Note: Please first perform netstat -na|grep 395 to determine the port for LDAP Migration. If there is a match(even partial match), grep 396 and so on till the port doesnt have any match. Then, set that port as LDAPMigrationPort. For example: # netstat -na | grep 395 *.39504 *.* LISTEN *.39513 *.* LISTEN 0 0 0 24576 0 24576 0 0
This means there are two matches for the port 395. So perform the check netstat again till you find no match(i.e netstat -na| grep port must not return a matching line). 2. The following table shows the details of the required tags for upgrade. Please carefully look at each tags listed and change the values in the <SCS_ROOT>/.inputparms_upgrade.scs file.
Table 37 SCS 6.0 .inputparms_upgrade.scs S.No 1 Tag Name SCSHomeDir Value for the Tag This is the <SCS_ROOT> directory. Details E.g.: /opt/shasta/scs. This parameter will be validated, and if the upgrade directory is not correct, the script will exit Answer should be y or n. If the LDAP is installed on same physical server, the answer is y Answer should be y or n.If you would like to install the LDAP 5.1 the answer should be y. The name of the LDAP tar file that comes on the SCS installation CD.
LDAPInstalled
This tag contains the value, if the LDAP is installed on this physical server or not. This tag contains the value which indicates if LDAP needs to be installed. This tag contains the name of the directory server tar file.
InstallLdap
LdapTar
GPRS/UMTS
738
Table 37 SCS 6.0 .inputparms_upgrade.scs 5 LDAPPath The tag contains the LDAP path on the server. The value can also be found in the <SCS_ROOT>/bin/ .scs.config file. The LDAP path is also validated, and if the path is not correct, the upgrade script will exit. Default value for LDAP port is 389. The value can be found in the <SCS_ROOT>/bin/ .scs.config file. LDAP port value is validated and if the input is not correct, the script will exit the upgrade. The server name will typically be slapd-xxxxxxx. For SCS rolling upgrade there will be two directory servers. Choose the one that was setup as a duplicate server instance. The duplicate server instance value can also be found as a folder name under the LDAP 4.16 root path. Answer should be y or n. Default is n.
LDAPPort
This tag contains the LDAP port value.
LDAPServerName
The tag contains the name of the LDAP server
LDAPMigration
The tag contains the value that indicates if the existing LDAP data is migrated to the new LDAP 5.1 server. Should require the InstallLdap to be set to y The tag contains the value for the new LDAP 5.1 where the existing LDAP 4.16 data is going to be migrated to. The tag contains the value of the LDAP Migration port. The tag contains the LDAP host name. Note: If LDAP is installed on the local host, use localhost as the value for this tag. Do not enter the IP address of the local host.
LDAPMigrationPath
The path for the new LDAP 5.1. Default is /opt/shasta/iplanet/
10 11
LDAPMigrationPort LDAPhost
Default value is 395. If LDAP is installed on the same server, this tag will contain the value localhost. If LDAP is installed on a different server, provide with the IP address of the server. This value can be found in the .scs.config file.
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs Table 37 SCS 6.0 .inputparms_upgrade.scs 12 SCSBackupDir This tag contains the value for the backup directory for SCS. By default, the SCS backup directory should be in <SCS_ROOT>/backup. No validation is done for this parameter.
739
13
StartSCSatBoot
This contains the value to determine whether to start the SCS processes after very reboot. This tag contains determines whether the customer wants to configure an user to collect the performance data. For example, the user could be pmuser. This tag contains the name of the user to be created for collecting performance data. This tag determines if the customer uses Corba or not.
Answer should be y or n. Default answer is y
14
ConfigPerfUser
Answer to this tag should be y or n. Default answer is y Ignore the tag in row 15, if the answer to this tag is n.
15
PerfUserName
Default value for this tag is pmuser. This tag can be ignored if the answer to the tag in Row 14 is n If customer uses corba, the answer to this question must be y. The default is set to y. Ignore the tags in rows 17,18,19,20,21 if the answer to this tag is n The upgrade procedure requires the Corba file to be copied to <SCS_ROOT> directory. The answer to this question should be <SCS_ROOT>/ scs_corba_server.tar Corba server must be installed in <SCS_ROOT> directory. Answer to this question must be <SCS_ROOT> Default is localhost Default is default
16
InstallCorbaServer
17
CorbaTarFile
The tag contains the name and location of the SCS Corba server tar file.
18
CorbaInstallDir
This tag determines where the Corba server should be installed. This tag contains the IP address of the Corba Server. This tag contains the Corba Orb IP address
19 20
CorbaIPAddress CorbaOrbIPAddress
GPRS/UMTS
740
Table 37 SCS 6.0 .inputparms_upgrade.scs 21 CorbaPORT This tag determines which port should be used for the Corba Server to listen to the incoming IIOP (Internet InterORB Protocol) requests. Default value is 0. a. If default value (0) is set, the Corba Server will listen to any available port. b. If a static port number is set (for example, configuring firewall), it is highly recommended configuring a specific port (>1023) for SCS Corba Server incoming IIOP requests. The default value is 4. Any CSV files which are older than the value configured for this tag, will be purged by a cron job.
22
CSVRetainDays
This tag contains the no of days the CSV files are retained before purging.
Here is a sample .inputparms_upgrade.scs file.(The snap shot from the file is shown in Italics and the explanation is shown in normal text here)
zrc2s0ns# cat .inputparms_upgrade.scs #SCS INPUT PARAMETERS FILE for SCS 5.1 <-note, the file indicates SCS 5.1 which is a typo error. #This file is used to read all the required input only for SCS Silent upgrade #Please read the Upgrade NTP or Installtion IM before changing the parameters
#General rules while editing this file #DO NOT LEAVE ANY WHITE SPACES AFTER THE = #USE ALL LOWER CASE LETTERS, for example y, n, /opt/shasta etc #DO NOT CHANGE THE TAGS #DO NOT LEAVE ANY REQUIRED PARAMETERS EMPTY
#Upgrade parameters #Please change the following parameters if you are upgrading
#Where do you want to upgrade SCS #This should be your present working directory
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs #Default is /opt/shasta/scs SCSHomeDir=/opt/shasta/scs
741
#Is LDAP running on this Server? Answer y or n #Default is set to y. LDAPInstalled=y
#If LDAP not installed, would you like to install? Answer y or n #Default is set to n #For LDAP migration, the value is y InstallLdap=n
#Name of the directory server tar file #Copy it to the scs head directory LdapTar=directory-5[1].1sp3-us.sparc-sun-solaris2.8.tar
#For LDAP specify directory below #Default is SCS root directory /opt/shasta/ldap #Specify the path where LDAP is installed currently LDAPPath=/opt/shasta/ldap
#LDAP, Existing and new Installation specify port here #Default is set to 389. Do not change this unless required LDAPPort=389
#LDAP, Directory Server Name. #You should change "xxxxxx" by the name of LDAPServer. E.g: If your server name is "zrc2s036" , this parameter is "slapd-zrc2s036" LDAPServerName=slapd-xxxxxx
GPRS/UMTS
742
Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs Nortel Networks Confidential #Please Specify if LDAP data will be migrated #Answer y or n default is n LDAPMigration=n
#For LDAP Migration specify directory below #Default is /opt/shasta/iplanet LDAPMigrationPath=/opt/shasta/iplanet
#LDAP, Migration specify port here #Default is set to 395. Do not change this unless required #This port is for the new LDAP 5.1 where data will be migrated from 4.1 LDAP LDAPMigrationPort=395
#LDAP IP Address, where it is installed #Default is set to localhost. Local IP address is also ok LDAPhost=localhost
#SCS BAckup Directory #Default is SCS root $head/backup SCSBackupDir=/opt/shasta/scs/backup
#Do you want to start SCS processes at boot time? #Default is set to y. Answer y or n StartSCSatBoot=y
#Do you want to configure an user for collecting Perf data #Default is y. Answer y or n ConfigPerfUser=y
#What is the name of the user to be configured for Perf data #Default is pmuser 411-5221-309 Standard 06.30 March 10, 2010
Nortel Networks Confidential Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs PerfUserName=pmuser
743
#Do you want to install Corba Server #Default is y, Answer y or n #If you are NOT interested in installing Corba you can ignore all other corba parms InstallCorbaServer=y
#Corba Tar file name and its location. Path and name #Default location is SCS Root directory #corba tar file name is always scs_corba_server.tar CorbaTarFile=/opt/shasta/scs/scs_corba_server.tar
#Installation directory for Corba #Default is SCS ROOT directory for SCS. CorbaInstallDir=/opt/shasta/scs
#Corba IP Address #Default is localhost CorbaIPAddress=localhost
#Corba Orb IP Address #Default is default CorbaOrbIPAddress=default
#Which Corba Port will be used #Default is 0 CorbaPORT=0
#How many days do you want to retain the CSV Files #Default is 4 CSVRetainDays=4 GPRS/UMTS Upgrade Manual GGSN6.0
744
Appendix R: Details on inputparms_install.scs and inputparms_upgrade.scs Nortel Networks Confidential zrc2s0ns#
3. After editing this file, please return back to the SCS Upgrade section.
411-5221-309
Standard
06.30 March 10, 2010
745
60
The SCS now supports the Sun Netra T5220 server. The T5220 only supports Solaris 10, and is shipped with Solaris 10 already installed. There is no DAT drive shipped with the T5220. SCS version supported on Solaris 10 is SCS 6.0.1. The default disk partitions set on the server when shipped from the factory may not match the recommended partitioning required for the SCS server. A new installation of Solaris 10 will be required to update the server partitions. Here are the installation notes for Solaris 10 new installation on the Sun Netra T5220 server. The T5220 server has 2x146 GB drives. Only 1 disk is used during the installation. The other disk can be parititoned for later use or can be used to create disk mirroring for redundancy. For disk mirroring details, refer to Appendix E: Creating Mirrors on page 609. Here is the recommended disk partitions for 1x146 GB drive.
Table 38 Partition table for the Sun T5220 Slice 0 1 2 3 4 5 6 7 /opt 50 GB /var 500 MB 22 GB Partition Name / swap Size 45 GB 16 GB
GPRS/UMTS
746
Solaris 10 New Installation Example
60
Here is an example log capture of a Solaris 10 new installation. Note, installation parameters like IP address, subnet mask, host name, Region and Timezone settings must be updated to match the customer requirement. Note: The log captures are taken from a serial console. The key sequence to navigate through the installation is pressing the <Esc> key and a combination of a number listed on the screen.
Select a Language 0. 1. 2. 3. 4. 5. 6. 7. 8. 9. English French German Italian Japanese Korean Simplified Chinese Spanish Swedish Traditional Chinese
Please make a choice (0 - 9), or press h or ? for help: <0>
What type of terminal are you using? 1) ANSI Standard CRT 2) DEC VT52 3) DEC VT100 4) Heathkit 19 5) Lear Siegler ADM31 6) PC Console 7) Sun Command Tool 8) Sun Workstation 9) Televideo 910 10) Televideo 925 11) Wyse Model 50 12) X Terminal Emulator (xterms) 13) CDE Terminal Emulator (dtterm) 14) Other Type the number of your choice and press Return: 3
The Solaris Installation Program The Solaris installation program is divided into a series of short sections where you'll be prompted to provide information for the installation. At the end of each section, you'll be able to change the selections you've made before continuing. About navigation... - The mouse cannot be used - If your keyboard does not have function keys, or they do not respond, press ESC; the legend at the bottom of the screen will change to show the ESC keys to use for navigation. F2_Continue F6_Help <ESC 2>
<<For console users, press <Esc> 2 key sequence>>
411-5221-309
Standard
06.30 March 10, 2010
747
Identify This System On the next screens, you must identify this system as networked or non-networked, and set the default time zone and date/time. If this system is networked, the software will try to find the information it needs to identify your system; you will be prompted to supply any information it cannot find. > To begin identifying this system, press F2. Esc-2_Continue Esc-6_Help
Network Connectivity Specify Yes if the system is connected to the network by one of the Solaris or vendor network/communication Ethernet cards that are supported on the Solaris CD. See your hardware documentation for the current list of supported cards. Specify No if the system is connected to a network/communication card that is not supported on the Solaris CD, and follow the instructions listed under Help. Networked [X] Yes [ ] No Esc-2_Continue Esc-6_Help
DHCP for bge0 Specify whether or not this network interface should use DHCP to configure itself. Choose Yes if DHCP is to be used, or No if the network interface is to be configured manually. NOTE: DHCP support will not be enabled, if selected, till after the system reboots. Use DHCP for bge0 [ ] Yes [X] No Esc-2_Continue Esc-6_Help
Host Name for bge0 Enter the host name which identifies this system on the network. The name must be unique within your domain; creating a duplicate host name will cause problems on the network after you install Solaris.
GPRS/UMTS
748
A host name must have at least one character; it can contain letters, digits, and minus signs (-). Host name for bge0 zrc2s0q4 Esc-2_Continue Esc-6_Help
IP Address for bge0 Enter the Internet Protocol (IP) address for this network interface. It must be unique and follow your site's address conventions, or a system/network failure could result. IP addresses contain four sets of numbers separated by periods (for example 129.200.9.1). IP address for bge0 Esc-2_Continue Esc-6_Help 47.104.70.80
Subnet for bge0 On this screen you must specify whether this system is part of a subnet. If you specify incorrectly, the system will have problems communicating on the network after you reboot. > To make a selection, use the arrow keys to highlight the option and press Return to mark it [X]. System part of a subnet [X] Yes [ ] No Esc-2_Continue Esc-6_Help
Netmask On this default sure it sets of
for bge0 screen you must specify the netmask of your subnet. A netmask is shown; do not accept the default unless you are is correct for your subnet. A netmask must contain four numbers separated by periods (for example 255.255.255.0).
Netmask for bge0 255.255.248.0 Esc-2_Continue Esc-6_Help
IPv6 for bge0 Specify whether or not you want to enable IPv6, the next generation Internet Protocol, on this network interface. Enabling IPv6 will have no effect if this machine is not on a network that
411-5221-309
Standard
06.30 March 10, 2010

provides IPv6 service. is enabled.
749
IPv4 service will not be affected if IPv6
> To make a selection, use the arrow keys to highlight the option and press Return to mark it [X]. Enable IPv6 for bge0 [ ] Yes [X] No Esc-2_Continue Esc-6_Help
Set the Default Route for bge0 To specify the default route, you can let the software try to detect one upon reboot, you can specify the IP address of the router, or you can choose None. Choose None if you do not have a router on your subnet. > To make a selection, use the arrow keys to select your choice and press Return to mark it [X]. Default Route for bge0 [ ] Detect one upon reboot [X] Specify one ? [ ] None Esc-2_Continue Esc-6_Help
Default Route IP Address for bge0 Enter the IP address of the default route. This entry will be placed in the /etc/defaultrouter file and will be the default route after you reboot (example 129.146.89.225). Router IP Address for bge0 47.104.64.1 Esc-2_Continue Esc-6_Help
Confirm Information for bge0 > Confirm the following information. If it is correct, press F2; to change any information, press F4. Networked: Use DHCP: Host name: IP address: System part of a subnet: Netmask: Enable IPv6: Default Route: Router IP Address: Yes No zrc2s0q4 47.104.70.80 Yes 255.255.248.0 No Specify one 47.104.64.1
GPRS/UMTS
750

Esc-2_Continue Esc-4_Change

Esc-6_Help
Configure Security Policy: Specify Yes if the system will use the Kerberos security mechanism. Specify No if this system will use standard UNIX security. Configure Kerberos Security [ ] Yes [X] No Esc-2_Continue Esc-6_Help
Confirm Information > Confirm the following information. If it is correct, press F2; to change any information, press F4. Configure Kerberos Security: No Esc-2_Continue Esc-4_Change Esc-6_Help
Name Service On this screen you must provide name service information. Select the name service that will be used by this system, or None if your system will either not use a name service at all, or if it will use a name service not listed here. > To make a selection, use the arrow keys to highlight the option and press Return to mark it [X]. Name service [] NIS+ [ ] NIS [ ] DNS [ ] LDAP [X] None ? Esc-2_Continue Esc-6_Help
Confirm Information > Confirm the following information. If it is correct, press F2; to change any information, press F4. Name service: None Esc-2_Continue Esc-4_Change Esc-6_Help
411-5221-309
Standard
06.30 March 10, 2010
751
NFSv4 Domain Name NFS version 4 uses a domain name that is automatically derived from the system's naming services. The derived domain name is sufficient for most configurations. In a few cases, mounts that cross domain boundaries might cause files to appear to be owned by "nobody" due to the lack of a common domain name. The current NFSv4 default domain is: "" NFSv4 Domain Configuration [X] Use the NFSv4 domain derived by the system [ ] Specify a different NFSv4 domain Esc-2_Continue Esc-6_Help
Confirm Information for NFSv4 Domain > Confirm the following information. If it is correct, press F2; to change any information, press F4. NFSv4 Domain Name: Esc-2_Continue << Value to be derived dynamically >> Esc-6_Help
Esc-4_Change
Time Zone On this screen specify a time or oceans from - specify time you must specify your default time zone. You can zone in three ways: select one of the continents the list, select other - offset from GMT, or other zone file.
> To make a selection, use the arrow keys to highlight the option and press Return to mark it [X]. Continents and Oceans [ ] Africa [X] Americas [ ] Antarctica [ ] Arctic Ocean [ ] Asia [ ] Atlantic Ocean [ ] Australia [ ] Europe [ ] Indian Ocean Esc-2_Continue Esc-6_Help
x x x x x x x v
Country or Region > To make a selection, use the arrow keys to highlight the option and press Return to mark it [X].
GPRS/UMTS
752
Countries and Regions x x x x x x x x x x x v [X] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] United States Anguilla Antigua & Barbuda Argentina Aruba Bahamas Barbados Belize Bolivia Brazil Canada Cayman Islands Chile Esc-6_Help
Esc-2_Continue
Time Zone > To make a selection, use the arrow keys to highlight the option and press Return to mark it [X]. Time zones [ ] x [ ] x [ ] x [ ] x [ ] x [ ] Counties x [ ] x [ ] x [ ] x [ ] x [X] x [ ] v [ ] Eastern Eastern Eastern Eastern Eastern Eastern Eastern Eastern Eastern Eastern Central Central Central Time Time Time Time Time Time Time Time Time Time Time Time Time Michigan - most locations Kentucky - Louisville area Kentucky - Wayne County Indiana - most locations Indiana - Daviess, Dubois, Knox & Martin Indiana Indiana Indiana Indiana Starke County Pulaski County Crawford County Switzerland County
- Indiana - Perry County - Indiana - Pike County
Esc-2_Continue
Esc-6_Help
Date and Time > Accept the default date and time or enter new values. Date and time: 2009-01-14 12:26 Year Month Day Hour Minute (4 digits) (1-12) (1-31) (0-23) (0-59) : : : : : 2009 01 14 12 26
Esc-2_Continue
Esc-6_Help
411-5221-309
Standard
06.30 March 10, 2010

Confirm Information
753
> Confirm the following information. If it is correct, press F2; to change any information, press F4. Time zone: Central Time (US/Central) Date and time: 2009-01-14 12:26:00 Esc-2_Continue Esc-4_Change Esc-6_Help
Root Password Please enter the root password for this system. The root password may contain alphanumeric and special characters. For security, the password will not be displayed on the screen as you type it. > If you do not want a root password, leave both entries blank. Root password: Root password: Esc-2_Continue **** **** Esc-6_Help
Identify This System On the next screens, you must identify this system as networked or non-networked, and set the default time zone and date/time. If this system is networked, the software will try to find the information it needs to identify your system; you will be prompted to supply any information it cannot find. > To begin identifying this system, press F2. F2_Continue F6_Help
Enabling remote services Would you like to enable network services for use by remote clients? Selecting "No" provides a more secure configuration in which Secure Shell is the only network service provided to remote clients. Selecting "Yes" enables a larger set of services as in previous Solaris releases. If in doubt, it is safe to select "No" as any services can be individually enabled after installation. Note: This choice only affects initial installs. It doesn't affect upgrades. Remote services enabled [ ] Yes
GPRS/UMTS
754

[X] No Esc-2_Continue Esc-6_Help
System identification complete. Starting Solaris installation program... Executing JumpStart preinstall phase... Searching for SolStart directory... Checking rules.ok file... Using begin script: install_begin Using finish script: patch_finish Executing SolStart preinstall phase... Executing begin script "install_begin"... Begin script install_begin execution completed. Solaris Interactive Installation On the following screens, you can accept the defaults or you can customize how Solaris software will be installed by: - Selecting the type of Solaris software to install - Selecting disks to hold software you've selected - Selecting unbundled products to be installed with Solaris - Specifying how file systems are laid out on the disks After completing these tasks, a summary of your selections (called a profile) will be displayed. There are two ways to install your Solaris software: - "Standard" installs your system from a standard Solaris Distribution. Selecting "Standard" allows you to choose between initial install and upgrade, if your system is upgradable. - "Flash" installs your system from one or more Flash Archives. F2_Standard F4_Flash F5_Exit F6_Help
Eject a CD/DVD Automatically? During the installation of Solaris software, you may be using one or more CDs/DVDs. You can choose to have the system eject each CD/ DVD automatically after it is installed or you can choose to manually eject each CD/DVD. [X] Automatically eject CD/DVD [ ] Manually eject CD/DVD F2_Continue F3_Go Back F5_Exit
Reboot After Installation? After Solaris software is installed, the system must be rebooted. You can choose to have the system automatically reboot, or you can choose to manually reboot the system if you want to run scripts or do other customizations before the reboot. You can manually reboot a system by using the reboot(1M) command.
411-5221-309
Standard
06.30 March 10, 2010
755
[X] Auto Reboot [ ] Manual Reboot F2_Continue F3_Go Back F5_Exit
Solaris Interactive Installation This system is upgradable, so there are two ways to install the Solaris software. The Upgrade option updates the Solaris software to the new release, saving as many modifications to the previous version of Solaris software as possible. Back up the system before using the Upgrade option. The Initial option overwrites the system disks with the new version of Solaris software. This option allows you to preserve any existing file systems. Back up any modifications made to the previous version of Solaris software before starting the Initial option. After you select an option and complete the tasks that follow, a summary of your actions will be displayed. F2_Upgrade <ESC 4> F3_Go Back F4_Initial F5_Exit F6_Help
Initializing The system is being initialized. Loading install media, please wait... License Sun Microsystems, Inc. ("Sun") x SOFTWARE LICENSE AGREEMENT x x READ THE TERMS OF THIS AGREEMENT ("AGREEMENT") CAREFULLY x... v 1. Definitions. Esc-2_Accept License F5_Exit
Select Geographic Regions Select the geographic regions for which support should be installed. > > > > > > [ [ [ [ [ [ ] ] ] ] ] ] Australasia Asia Eastern Europe Northern Europe Northern Africa Middle East
GPRS/UMTS
756

> > > > > > [ [ [ [ [ [ ] ] ] ] ] ] Southern Europe South America Central America Central Europe North America Western Europe
Move left, right, up, down using the arrow keys Esc-2_Continue F3_Go Back F5_Exit F6_Help
<press ESC 2, need not select>
Select System Locale Select the initial locale to be used after the system has been installed. [X] POSIX C ( C ) F3_Go Back F5_Exit F6_Help
Esc-2_Continue
Additional Products To scan for additional products, select the location you wish to scan. Products found at the selected location that are in a Web Start Ready install form will be added to the Products list. Web Start Ready product scan location: [X] [ ] [ ] None CD/DVD Network File System F3_Go Back F5_Exit
Esc-2_Continue
If you have additional Solaris 10 CDs (Disk 2), use down arrow to CD/DVD, press Space bar Select Software Select the Solaris software to install on the system. NOTE: After selecting a software group, you can add or remove software by customizing it. However, this requires understanding of software dependencies and how Solaris software is packaged. [ ] [X] [ ] [ ] [ ] [ ] Entire Distribution plus OEM support ....... Entire Distribution ........................ Developer System Support ................... End User System Support .................... Core System Support ........................ Reduced Networking Core System Support ..... 5822.00 5777.00 5580.00 4592.00 875.00 822.00 MB MB MB MB MB MB
411-5221-309
Standard
06.30 March 10, 2010

Esc-2_Continue F6_Help F3_Go Back

F4_Customize F5_Exit
757
Select Disks Note: The example capture is taken from a Server with 7x69 GB drives. During installtion, the primary disk will be marked with [x]. Select the disk for repartitioning. Details of the disk partition layout is detailed below. On this screen you must select the disks for installing Solaris software. Start by looking at the Suggested Minimum field; this value is the approximate space needed to install the software you've selected. Keep selecting disks till the Total Selected value exceeds the Suggested Minimum value. NOTE: ** denotes current boot disk Disk Device Available Space =============================================================== [ ] ** c0t0d0 69994 MB [ ] c0t10d0 69994 MB [ ] c0t11d0 69994 MB [X] c0t1d0 69994 MB [ ] c0t2d0 69994 MB [ ] c0t3d0 69994 MB [ ] c0t9d0 69994 MB Total Selected: Suggested Minimum: Esc-2_Continue F3_Go Back F4_Edit 69994 MB 4475 MB F6_Help
F5_Exit
Boot Device Not Selected You have not selected the default boot device c0t0d0. If you do not go back and select the default boot device, the system will always reboot Solaris from some other device based on the option you select below: > To let the Solaris installation program configure a boot device for you choose OK. > To select a different boot device choose Select. Esc-2_OK Esc-3_Select Esc-5_Cancel
Preserve Data? Do you want to preserve existing data? At least one of the disks you've selected for installing Solaris software has file systems or unnamed slices that you may want to save.
GPRS/UMTS
758

Esc-2_Continue F6_Help Esc-3_Go Back

F4_Preserve F5_Exit
Automatically Layout File Systems? Do you want to use auto-layout to automatically layout file systems? Manually laying out file systems requires advanced system administration skills. F2_Auto Layout F6_Help Esc-3_Go Back F4_Manual Layout F5_Exit
File System and Disk Layout Note: It is recommended to use the following partition layout. The T5220 server has 2x146 GB disks. Only 1 disk is partitioned, the other disk can be used later and also configured for disk mirroring
Table 39 Partition table for the Sun T5220 Slice 0 1 2 3 4 5 6 7 /opt 50 GB /var 500 MB 22 GB Partition Name / swap Size 45 GB 16 GB
The summary below is your current file system and disk layout, based on the information you've supplied. NOTE: If you choose to customize, you should understand file systems, their intended purpose on the disk, and how changing them may affect the operation of the system. File sys/Mnt point Disk/Slice Size =============================================================== overlap c0t1d0s2 69994 MB Esc-2_Continue F6_Help Esc-3_Go Back F4_Customize F5_Exit
411-5221-309
Standard
06.30 March 10, 2010

Customize Disk: c0t1d0
759
Entry: / Recommended: 4686 MB Minimum: 3985 MB =============================================================== Slice Mount Point Size (MB) 0 / 35884 1 swap 4004 2 overlap 69994 3 104 4 0 5 0 6 0 7 /opt 30001 =============================================================== Capacity: 69994 MB Allocated: 69993 MB Rounding Error: 1 MB Free: 0 MB Esc-2_OK Esc-4_Options Esc-5_Cancel F6_Help
File System and Disk Layout The summary below is your current file system and disk layout, based on the information you've supplied. NOTE: If you choose to customize, you should understand file systems, their intended purpose on the disk, and how changing them may affect the operation of the system. File sys/Mnt point Disk/Slice Size =============================================================== / c0t1d0s0 35884 MB swap c0t1d0s1 4004 MB overlap c0t1d0s2 69994 MB c0t1d0s3 104 MB /opt c0t1d0s7 30001 MB Esc-2_Continue F6_Help Esc-3_Go Back F4_Customize F5_Exit
Mount Remote File Systems? Do you want to mount software from a remote file server? This may be necessary if you had to remove software because of disk space problems. Esc-2_Continue F6_Help Esc-3_Go Back F4_Remote Mounts F5_Exit
Profile The information shown below is your profile for installing Solaris software. It reflects the choices you've made on previous screens.
GPRS/UMTS
760
=============================================================== Installation Option: Boot Device: Client Services: System Locale: C Initial c0t1d0 None ( C )
Software: Solaris 10, Entire Distribution File System and Disk Layout: / c0t1d0s0 35884 MB swap c0t1d0s1 4004 MB /opt c0t1d0s7 30001 MB Esc-2_Begin Installation F4_Change F5_Exit F6_Help
Warning The following disk configuration condition(s) have been detected. Errors must be fixed to ensure a successful installation. Warnings can be ignored without causing the installation to fail. WARNING: CHANGING DEFAULT BOOT DEVICE You have either explicitly changed the default boot device, or accepted the default to "Reconfigure EEPROM". In either case, the system's EEPROM will be changed so it will always boot Solaris from the device that you've specified. If this is not what you had in mind, go back to the disk selection screens and change the "Reconfigure EEPROM" setting. Esc-2_OK Esc-5_Cancel
Preparing system for Solaris install Configuring disk (c0t1d0) - Creating Solaris disk label (VTOC) Creating and checking UFS file systems -Creating / (c0t1d0s0) -Creating /opt (c0t1d0s7) Solaris Initial Install MBytes Installed: MBytes Remaining: 73.30 3678.42
Installing: Core Solaris Devices
Configure Keyboard Layout Please specify the keyboard layout from the list below. > To make a selection, use the arrow keys to highlight the option and press Return to mark it [X].
411-5221-309
Standard
06.30 March 10, 2010

Keyboard Layout ^ x x x x x x x x x [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [X] Slovenian Slovakian Spanish Swedish Swiss-French Swiss-German Taiwanese TurkishQ TurkishF UK-English US-English F6_Help
761
F2_Continue
Creating new rsa public/private host key pair Creating new dsa public/private host key pair Jan 14 14:55:47 zrc2s0q4 sendmail[1043]: My unqualified host name (zrc2s0q4) unknown; sleeping for retry <<INSTALLATION PROGRESS AND COMPLETION>>
Log in to the server zrc2s0q4 console login: root Password: Jan 14 14:56:21 zrc2s0q4 login: ROOT LOGIN /dev/console Sun Microsystems Inc. SunOS 5.10 Generic January 2005 # uname -a SunOS zrc2s0q4 5.10 Generic_127127-11 sun4u sparc SUNW,Sun-FireV250
Verify Default router settings and verify IP connectivity
This completes the Solaris 10 new installation. Additional settings on the server must be updated. This includes, allowing users to login as root, enable root user access for FTP and applying Solaris 10 recommended patches - also referred as recommended patch cluster. Update Console settings to allow remote access to root user.
762
Edit file /etc/default/login Comment out (add a # at the beginning of the line) - CONSOLE=/dev/ console
#CONSOLE=/dev/console
Enable root access for FTP. Note, if enabling the option is determined a security risk, skip this step. Edit file /etc/ftpd/ftpusers. Comment out root.
# cat ftpusers # ident "@(#)ftpusers 1.4 01/08/27 SMI" # # List of users denied access to the FTP server, see ftpusers(4). #root
Set the default log in shell to C shell. Modify /etc/passwd and put in /usr/bin/csh instead of the pre-configured shell.
# which csh /usr/bin/csh
Use vi editor to modify the shell entry for root user.

After modifying /etc/passwd, login to the server as root from another telnet window. This way, if there was some error modifying /etc/passwd, and you are unable to log back in to the server, you are still logged into the server in the original window that was used to modify the file. Make sure to correct any errors in /etc/passwd in case of a login failure. Other system settings needed are: File /etc/nsswitch.conf contains: hosts: file dns Example: hosts:file dns File /etc/resolv.conf contains: domain <domain name>
411-5221-309 Standard 06.30 March 10, 2010
763
Example: domain my.company.com File /etc/hosts contains: <machines static ip address> <hostname> <fqdn> loghost Example: 99.100.100.100 scshost scshost.my.company.com loghost
After making the above changes, restart the Solaris system process for the new configuration to take affect.
# cd /etc/init.d # # # # ./inetinit stop ./inetsvc stop ./inetinit start ./inetsvc start
Apply Solaris 10 recommended patches. Sun releases Solaris operating system recommended patches, also referred as recommended patch cluster periodically. Users must download the patch cluster file from Sun and installation the cluster on the SCS server. For detailed instrutions, refer to Install Recommended Patches for Solaris 9 and Solaris 10 on page 452 .
GPRS/UMTS
764

61
Here are the steps to perform a new install of SCS 6.0.1. The procedure used can also be referred as silent install. The following procedure assumes iPlanet is not installed on the server. If a new installation is performed as part of a hardware migration or server IP address or host name or domain name change: Make sure the following SCS server settings match the old SCS installation. Please refer to Pre-requisites on page 689 Region ID - region ID assigned to the SCS server Optional - LDAPPort - port on which iPlanet process is listening
Make sure the following SCS server settings dont match the old SCS installation LDAPRoot - root point to which the SCS server connects to the iPlanet server. In other words, if the domain name has not changed on the SCS server, then the uid of LDAPRoot for the new SCS installation must be different from the current SCS installation. If the domain name on the server has changed, then the uid as well as the Organization (o=) will change.
Initial Server Configuration
61
The following system files must be updated prior to installing the SCS server software. A reboot of the server is required for the changes to take affect. 1. Edit file /etc/resolv.conf - include the key word domain <domainname>. Include nameserver if available. Here is an example:
# cat /etc/resolv.conf domain us.nortel.com <- modify to match the customer domain name nameserver 47.103.128.21 nameserver 47.103.121.21 nameserver 47.103.120.20 search internal.nortel.com
2. Edit the /etc/nsswitch.conf file to add the <dns> entry to the line for hosts. An example of file /etc/nsswitch.conf after editing:
passwd: files group: files hosts: files dns <- updated entry
411-5221-309
Standard
06.30 March 10, 2010
765
3. Edit file /etc/hosts by adding the Fully Qualified Domain Name of the server. Here is an example before and after updating /etc/hosts file. An example of file /etc/hosts prior to editing:
# Internet host table 127.0.0.1 localhost 47.162.48.109 gprs loghost
An example of file /etc/hosts after editing:

# Internet host table 127.0.0.1 localhost 47.162.48.109 gprs gprs.us.nortel.com loghost <- updated entry
4. Edit /etc/passwd. For user root, modify the default unix shell to csh. Here is an example of an updated /etc/passwd file.
# cat /etc/passwd root:x:0:1:Super-User:/:/usr/bin/csh <- updated entry
5. Reboot the server.

# sync; sync; sync; sync # init 6
Install Procedure
61
1. Create a directory for SCS 6.0.1. Make sure the partition has enough disk space. Use df -k to verify enough disk space is available. Please refer to Checkpoint 0 item 6, page 52 for details.
# cd /opt # mkdir -p shasta/scs6.0.1
2. FTP a copy of SCS 6.0.1 software (or copy the server installation files from CDROM/ ESD) to the SCS 6.0.1 installation directory. Refer to section Acquiring GPRS Packet Core software for the CS-LAN on page 24. The following files are required: scsserver.tar.Z directory-5[1].1sp3-us.sparc-sun-solaris2.8.tar Optional - scs_corba_server.tar.Z Optional - sslpkg.tar.Z
3. Uncompress and untar scsserver.tar file.

# cd /opt/shasta/scs6.0.1 # uncompress scsserver.tar.Z GPRS/UMTS Upgrade Manual GGSN6.0
766
Appendix T: Perform SCS 6.0.1 new installation # tar xvf scsserver.tar
4. If SCS Corba Server is to be installation, uncompress file scs_corba_server.tar.Z. Do not untar the file.
# uncompress scs_corba_server.tar.Z
5. Determine the following server information. These information are needed to edit the SCS installation parameter file .inputparms_install.scs.
Note: Use ls -al in the SCS installation directory to view the file listing for .inputparms_install.scs. Determine the server host name using the command uname -n. File .inputparms_install.scs - parameter LDAPServerName must be updated with the host name.
# uname -a <server host name is returned> LDAPServerName = slapd=<hostname>
Here is an example:
# uname -n urc2y1th LDAPServerName = slapd-urc2y1th
Verify the server port 389 is free using the command netstat -na | grep 389. This port will be set as LDAPPort in .inputparms_install.scs. If the port 389 is free, the above command will not return an output and give the user the command prompt. Here is an example:
# netstat -na | grep 389 # LDAPPort = 389
If the netstat -na | grep 389 has already been used by the server, verify the next available port 390 is free. Here an example where port 389 is already used by the server and port 390 is free.
0 0 49152 0 LISTEN
# netstat -na | grep 389 *.389 *.* # netstat -na | grep 390 #
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential LDAPPort = 390
767
6. Make sure iPlanet admin port 33611 is free using netstat -na | grep 33611. If the port is free, the netstat command will return just the command prompt. Here is an example.
# netstat -na | grep 33611 #
If the netstat command returns a result similar to the example below, iPlanet admin port is already used by the server. In this case, check and make sure iPlanet software is not used by any other applications running on the server. Un-installing iPlanet will be a good option to clean up old iPlanet installations. Please refer to Appendix H: Example capture of iPlanet server uninstallation on page 656 for details.
0 0 49152 0 LISTEN
# netstat -na | grep 33611 47.104.5.30.33611 *.*
7. Using vi editor, modify .inputparms_install.scs Here is an example with pointers for updating .inputparms_install.scs
# cat .inputparms_install.scs #SCS INPUT PARAMETERS FILE for SCS 5.1 #This file is used to read all the required input for SCS Silent new installation #Please read the Installtion IM before changing the parameters #General rules while editing this file #DO NOT LEAVE ANY WHITE SPACES AFTER THE = #USE ALL LOWER CASE LETTERS, for example y, n, /opt/shasta etc #THIS FILE WILL CONTAIN PASSWORDS for SOLID, LDAP #DO NOT CHANGE THE TAGS #DO NOT LEAVE ANY REQUIRED PARAMETERS EMPTY #Install parameters #Please change the following parameters if you are installing #Where do you want to install SCS #This should be your present working directory #Default is /opt/shasta/scs6.0.1 SCSHomeDir=/opt/shasta/scs6.0.1 <- update to match SCS 6.0.1 #Is LDAP running on this Server? Answer y or n #Default is set to n LDAPInstalled=n #If LDAP not installed, would you like to install? Answer y or n #Default is set to y # For migration and Fresh Installation the value is y InstallLdap=y #Name of the directory server tar file
GPRS/UMTS
768
#Copy it to the scs6.0.1 head directory LdapTar=directory-5[1].1sp3-us.sparc-sun-solaris2.8.tar #For LDAP specify directory below #Default is SCS root directory /opt/shasta/ldap #Specify the path where LDAP is installed currently #Or for fresh installation without migration LDAPPath=/opt/shasta/iplanet <- modify to /opt/shasta/iplanet #LDAP, Existing and new Installation specify port here #Default is set to 389. Do not change this unless required LDAPPort=389 #LDAP, Directory Server Name. #You should change "xxxxxx" by the name of LDAPServer. E.g : If your server name is "zrc2s036" , this parameter is "slapdzrc2s036" LDAPServerName=slapd-urc2y1th <- updade xxxxxx to match the current SCS hostname #LDAP IP Address, where it is installed #Default is set to localhost. Local IP address is also ok LDAPhost=localhost #SCS BAckup Directory #Default is SCS root $head/backup SCSBackupDir=/opt/shasta/scs6.0.1/backup #Do you want to start SCS processes at boot time? #Default is set to y. Answer y or n StartSCSatBoot=y #Do you want to configure an user for collecting Perf data #Default is y. Answer y or n ConfigPerfUser=y #What is the name of the user to be configured for Perf data #Default is pmuser PerfUserName=pmuser #Do you want to install Corba Server #Default is y, Answer y or n #If you are NOT interested in installing Corba you can ignore all other corba parms InstallCorbaServer=y <- if a SCS Corba Server license is available, set the option to - y #Corba Tar file name and its location. Path and name #Default location is SCS Root directory #corba tar file name is always scs6.0.1_corba_server.tar CorbaTarFile=/opt/shasta/scs6.0.1/scs_corba_server.tar #Installation directory for Corba #Default is SCS ROOT directory for SCS. CorbaInstallDir=/opt/shasta/scs6.0.1 #Corba IP Address #Default is localhost CorbaIPAddress=localhost #Corba Orb IP Address #Default is default CorbaOrbIPAddress=default
411-5221-309
Standard
06.30 March 10, 2010
769
#Which Corba Port will be used #Default is 0 CorbaPORT=0 #How many days do you want to retain the CSV Files #Default is 4 CSVRetainDays=4 #Ignore these parameters if you are upgrading #These are only required for Installation #Install the following servers #Default is yes to all servers #If you are installing Log server, pull server must also be installed #Answer y or n InstallDomainServer=y InstallPullServer=y InstallRegionServer=y InstallLogServer=y #Which Scale of Deployment is to be installed #1 for Large, 2 for Medium, 3 for small #Default is 1 #Refer to NTP for more details SCSDeployLevel=1 #Give the Region ID #Default is 1 SCSRegionID=1 <-If a new SCS installation is performed, the Region ID need not be modified. If migrating from a old SCS server to a new SCS server, make sure the region id matches the old server. #Input for Ports for Log (Accounting and Logging) and Pull Server SCSPullServerPort=4321 SCSLogLServerPort=4322 SCSLogAServerPort=4323 #LDAP Admin user #Do not change this, accept the default LDAPAdminUser=uid=admin,ou=Administrators,ou=TopologyManagement,o =NetscapeRoot #LDAP Root Point #User would have created this using the ldap admin #example root point looks like uid=uldap,ou=People,o=us.nortel.com LDAPRootPoint=uid=UShasta,ou=People,o=us.nortel.com If a new SCS installation is performed, the LDAPRootPoint settings need not be modified If migrating SCS from one host to another, make sure the LDAPRootPoint uid does not match the old SCS server LDAPRoot uid #LDAP Root DN Password #This is the rootDn's(cn=Directory Manager) LDAPRootPassword=dmanager #LDAP Admin passwd LDAPAdminPassword=admin #Solid DB Admin password SolidDBPassword=admin
GPRS/UMTS
770
Appendix T: Perform SCS 6.0.1 new installation <<End of .inputparms_install.scs file>>
8. Execute SCS server installation script: setup.sh Here is an example capture.

# ./setup.sh 5.10 is a supported Solaris version Logged in as User root Silent procedure is selected /opt/shasta/scs6.0.1/install/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled This program will install Nortel Service Creation System. Version SCS GGSNS6.0.1_SCS6.0(1) ***************************************************************** **** * SCS 6.0 requires IPlanet LDAP 5.1. If you are not running IPlanet * * LDAP 5.1, please upgrade the LDAP server before starting the SCS * * Installation. Please refer to the SCS installation document and * * SCS Release Notes for details on upgrading the Directory Server. * * * * SCS and LDAP require Solaris Recommended Patches. * * Make sure that the latest patches have been installed * * If you are not sure, please abort the setup and check Patch level * * Restart the setup.sh script after checking the patch level * ***************************************************************** **** You have the following options: (C) Create a new SCS Server installation (U) Upgrade the current SCS Server (A) Abort this installation Please enter (C)reate, (U)pgrade or (A)bort? [A]: c Found the parameters File, /opt/shasta/scs6.0.1/ .inputparms_install.scs Reading input Parameters from /opt/shasta/scs6.0.1/ .inputparms_install.scs, Please wait
Reading the input parameters and Validating... LDAP parameters will only be validated if the LDAP is installed on the localhost LDAP parameters are not being validated now Checking if the LDAP Schema files are present LDAP Schema Files are present in /opt/shasta/scs6.0.1
411-5221-309
Standard
06.30 March 10, 2010
771
================================================================= = The Following Parameters are read from the /opt/shasta/scs6.0.1/ .inputparms_install.scs ================================================================= = SCS Will be installed in the following directory: /opt/shasta/ scs6.0.1 SCS processes will run after the reboot : y SCS Backup directory will be : /opt/shasta/ scs6.0.1/backup SCS Pull Server port is : 4321 SCS Log Log Port is : 4322 SCS Log Acc Port is : 4323 SCS Deployment Profile is : 1 SCS Region ID is : 1 SCS Domain Server installed : y SCS Region Server installed : y SCS Pull Server installed : y SCS Log Server installed : y SCS Solid DB Password is : admin LDAP is installed on this Server : n Install New LDAP on this Server : y Is CSV user set on this Server : y Name of the User to collect the CSV files : pmuser Days CSV files will be preserved : 4 Install Corba Server on this Server : y Corba Installation directory : /opt/shasta/ scs6.0.1 Corba file location and name : /opt/shasta/ scs6.0.1/scs_corba_server.tar Corba Server will be installed in : /opt/shasta/ scs6.0.1 Corba Server IP Address : localhost Corba Server ORB IP : default Corba Port : 0 Please check the input parameters and confirm If the input is not right, quit by answering n Change the /opt/shasta/scs6.0.1/.inputparms_install.scs and restart the script if you answer n Do you want to continue (Y/N)? [N]: y User accepted the parameters, continuing with new SCS will be installed in /opt/shasta/scs6.0.1. Checking the available space ... Required space 106636 Kbytes. Available space 29794355 Kbytes. Found enough space to install SCS. Copying the required files ... /opt/shasta/scs6.0.1/bin/LDAPWatch-disable: LDAPWatch is already disabled LDAP Installation..... /opt/shasta/iplanet ============================== iPlanet Directory Server 5.x installation begins! ============================== urc2y1th us.nortel.com
GPRS/UMTS
772
Unpacking ... Start installation, please wait... Installing Netscape core components Installing Server Core Components Installing iPlanet Directory Suite Installing Administration Services Installing nsPerl Installing PerLDAP Extracting Netscape core components ... Extracting Server Core Components ... Extracting Core Java classes ... Extracting Java Runtime Environment ... Extracting iPlanet Directory Server ... Extracting iPlanet Directory Server Console ... Extracting iPlanet Administration Server ... Extracting Administration Server Console ... Extracting nsPerl 5.005_03 ... Extracting PerLDAP 1.4.1 ... [slapd-urc2y1th]: starting up server ... [slapd-urc2y1th]: [24/Mar/2009:11:50:49 -0500] - iPlanetDirectory/5.1 Service Pack 3 B2003.324.1439 starting up [slapd-urc2y1th]: [24/Mar/2009:11:50:50 -0500] - slapd started. Listening on all interfaces port 389 for LDAP requests Your new directory server has been started. Created new Directory Server Start Slapd Starting Slapd server configuration. Success Slapd Added Directory Server information to Configuration Server. Configuring Administration Server... Your parameters are now entered into the Administration Server database, and the Administration Server will be started. Changing ownership to admin user root... Setting up Administration Server Instance... Configuring Administration Tasks in Directory Server... Configuring Global Parameters in Directory Server... iPlanet-WebServer-Enterprise/6.0SP2 B01/06/2003 22:24 warning: daemon is running as super-user [LS ls1] http://urc2y1th.us.nortel.com, port 33611 ready to accept requests startup: server started successfully Installation is complete. See /opt/shasta/iplanet/setup/setup.log for possible errors. Schema update, please wait... Complete schema update Creating LDAP Root Point adding new entry uid=admin,ou=People,o=us.nortel.com This machine currently has 7077M of virtual memory available. We need to install Solid database server on this host. checking if snmp default port 5001 has been used, please wait ... snmp prxy will use port 5001.
411-5221-309
Standard
06.30 March 10, 2010
773
checking if TrapDaemon default port 5002 has been used, please wait ... TrapDaemon will use port 5002. We need to collect the LDAP information for the Domain/Pull/Log Server.
Installing the Solid Database Server ... [1] 8850 Start the solid server ... Solid Server is running ... Creating database tables for the SCS Domain Server ... 24-Mar-2009 11:51:26 553 INFO ldap.connection.info: localhost,389,uid=admin,ou=Administrators,ou=TopologyManagement,o =NetscapeRoot,uid=admin,ou=People,o=us.nortel.com 24-Mar-2009 11:51:26 794 INFO sni.7: Created a new LDAP connection... 1 Adding Patch Server information in SCS Domain Server database ... Enabling tftp - tftp already enabled, no changes made Creating database tables for the SCS Region Server ... Adding Pull Server information in SCS Domain Server database ... Adding Log Server information in SCS Domain Server database ... We have created the required SCS database tables. Now we will shutdown the Solid database server. Stopping Solid Database Server:.Stopped [1] + Done /opt/shasta/scs6.0.1/opt/solidSolaris/ bin/solid -f -c ... LDAP schema files updated successfully Now stopping and restarting LDAP server slapd-urc2y1th ... To generate CSV formatted accounting data, a user id must be designated as the owner of the generated files. It is recommended that the user id not be the root user. The ownership of any existing CSV formatted accounting data file will also be changed to this user id. The user id, pmuser, already exists and will be used by the SCS Log Server process for CSV generated files. Extracting Corba files, please wait... This program will install SCS Corba Server version SCS GGSNS6.0.1_SCS6.0(1) SCS Corba Server will be installed in /opt/shasta/scs6.0.1. Found Domain server installed. New SCS Corba server version matches installed SCS version. Continuing... SCS Corba Server will be installed in /opt/shasta/scs6.0.1. Checking the available space... Required space 61440 Kbytes. Available space 29368439 Kbytes. Found enough space to install SCS Corba Server.
GPRS/UMTS
774

Copying the required files...... SCS Corba Server is now installed.
You can use /opt/shasta/scs6.0.1/bin/SCSCorbaServer to run SCS Corba Server. The installation logs are saved in /opt/shasta/scs6.0.1/lib/ install/*.log. INSTALLATION IS COMPLETED SUCCESSFULLY The following SCS server(s) are currently installed on this machine: Version SCS GGSNS6.0.1_SCS6.0(1) SCS SCS SCS SCS SCS SCS You can Server. Domain Server (LDAP Server IP = localhost) Region Server (Region ID = 1) Monitor Server Pull Server (Listening Port = 4321) Log Server (Logging Port = 4322, Accounting Port = 4323) CORBA Server use '/opt/shasta/scs6.0.1/bin/SCSAdmin start' to run SCS
9. Start the SCS server processes.

# cd bin # ./SCSAdmin start /opt/shasta/scs6.0.1/bin/SCSWatch-disable: SCSWatch is already disabled /opt/shasta/scs6.0.1/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled /opt/shasta/scs6.0.1/bin/SCSDiskUsageMonitor-disable: SCSDiskUsageMonitor is already disabled /opt/shasta/scs6.0.1/bin/SCSCleanXmlExportFiles-disable: SCSCleanXmlExportFiles is already disabled [1] 9287 Starting Solid Database Server:.Started [2] 9305 Starting SCS Daemon:..Started [3] 9321 Starting SCS Domain server:.......Started [4] 9353 Starting SNMP Proxy:.Started [5] 9362 Starting SCS CORBA Server:............Started [6] 9395 Starting SCS Region server:.......Started [7] 9427 Starting SCS Monitor server:.......Started [8] 9459 Starting SCS Trap daemon:.......Started [9] 9492 Starting SCS Pull Server:....Started [10] 9515 Starting SCS Log Server:...Started ------------------------------------------Nortel Service Creation System Server Version SCS GGSNS6.0.1_SCS6.0(1) ------------------------------------------Adding SCSCleanLogcsv first time
411-5221-309
Standard
06.30 March 10, 2010
775
Added SCSCleanLogcsv to crontab Adding SCSWatch to Crontab for first time. Added SCSWatch to crontab Adding SCSDiskUsageMonitor first time Added SCSDiskUsageMonitor to crontab Adding SCSCleanXmlExportFiles first time Added SCSCleanXmlExportFiles to crontab
10. Run the ns_server_secure.sh script to enable iPlanet directory server security. Before the script is executed, set the unix PATH environment variable. Make sure you are in CSH.
# echo $SHELL
If you are not in CSH, type csh at the server prompt and hit enter. Set the PATH environment variable
# set path=(/opt/shasta/iplanet/shared/bin $path) <---manually set path before running script # cd /opt/shasta/scs6.0.1
Execute ns_server_secure.sh
# ./ns_server_secure.sh **** NOTE **** Please run this script on the machine where Netscape Directory Server is installed. There is no need to restart the Netscape Directory Server after running this script. Do you have SCS installed on this machine [Y/N]: Y <---answered Y Please specify the directory where SCS is installed. [/opt/shasta/scs6.0.1]: <--accepted default Please specify the root directory where the Netscape Directory Server is installed. [/space/netscape/server4]: /opt/shasta/iplanet <----notice difference here Please provide the LDAP Server IP address [localhost]: <---accepted default Please provide the LDAP Server Port Number [389]: <---accepted default Please provide the LDAP Root point for SCS [uid=admin,ou=People,o=us.nortel.com]: <---accepted default Please provide the Directory Manager password for Netscape Directory Server [password]: dmanager <----notice difference here **** CASE 1 **** Disable anonymous access to LDAP Directory Deleting Self entry modification ACL in o=us.nortel.com: Already deleted. Modification complete Deleting Anonymous access ACL in o=us.nortel.com: Already deleted. Modification complete **** CASE 2 **** Enable search on LDAP Configuration to authorized users only
GPRS/UMTS
776
Deleting anonymous access to LDAP configuration information : Already deleted. Modification complete Enable admin only access to LDAP configuration information : modifying entry cn=SNMP,cn=config Modification complete **** CASE 3 **** Enable search on LDAP Monitoring to authorized users only Deleting anonymous access to LDAP monitoring information : Already deleted. Modification complete Enable admin only access to LDAP monitoring information : modifying entry cn=monitor Modification complete **** CASE 4 **** Enable subtree search on LDAP NULL DN to authorized users only No changes need to be done as Netscape Directory Server does not allow this. No modifications need to be done **** CASE 5 **** Enable search on LDAP schema to authorized users only Enable admin only access to LDAP schema information : Already deleted. Modification complete Completed adding access control to Netscape Directory Server.
11. Perform installation of SCS client. The SCS client can be installed on the SCS server (or any Solaris server) or on Windows. Please refer toSCS Client upgrade procedures on page 355 12. Optional - Perform OS Hardening on the SCS server. OS Hardening on the Solaris server disables unused system services and improves security. The completes the SCS 6.0.1 server new installation.
If performing a server migration, please refer to Migrating SCS to a new physical server with Same or Different IP address on page 169 If performing a new deployment of the SCS server, please refer to the Nortel GGSN Provisioning Procedure NTP - 411-5221-927 to add and provision the GGSN.
411-5221-309
Standard
06.30 March 10, 2010
777
Appendix U: SCS 6.0.1 Database Migration Example 62

Here is an example capture of performing a database backup and restore for migration of the SCS server from one server to a new server.
SCS and iPlanet backup example for move to a new SCS server
1. On the old SCS server, make a note of the SCS installation directory.
62
2. Perform a SCS solid database backup.

# cd /opt/shasta/scs6.0/bin # ./SCSAdmin backup solidDB nortel_01062009 binDir is /opt/shasta/scs6.0/bin head is /opt/shasta/scs6.0 configFile is /opt/shasta/scs6.0/bin/.scs.config backup_dir is /opt/shasta/scs6.0/opt/solidSolaris/database/ solid_nortel_01062009 Solid Remote Control v.04.00.0025 (C) Copyright Solid Information Technology Ltd 1993-2003 Exit by giving command: exit Backup started. ...............
3. Change directory to the SCS database backup directory and tar the SCS solid database backup.
# cd /opt/shasta/scs6.0/opt/solidSolaris/database/ # a a a a a a tar cvf solid_nortel_01062009.tar nortel_01062009 solid_nortel_01062009/ 0K solid_nortel_01062009/solid.db 67232K solid_nortel_01062009/sol02152.log 410K solid_nortel_01062009/sol02153.log 288K solid_nortel_01062009/solid.ini 2K solid_nortel_01062009/solmsg.out 203K
4. Move the SCS solid backup tar file to a backup directory.

# ls /opt/BACKUP /opt/BACKUP: No such file or directory # mkdir -p /opt/BACKUP # mv solid_nortel_01062009.tar /opt/BACKUP
5. From the SCS config file /etc/shasta/scs.config, dertermine the iPlanet installation directory. Also make a note of LDAPRoot and LDAPServerPort. The parameters set for these attributes are requires are parameters for the iPlanet backup script.
GPRS/UMTS
778

LDAPPath=/opt/shasta/iplanet
# cat /etc/shasta/scs.config # # This file was generated during SCS installation. # Please do not modify manually. # InstallDomainServer=yes InstallRegionServer=yes InstallMonitorServer=yes InstallPullServer=yes InstallLogServer=yes DomainServerIp=localhost RegionId=1 LDAPUsername="uid=admin,ou=Administrators,ou=TopologyManagement,o =NetscapeRoot" LDAPPassword=admin LDAPRoot="uid=admin,ou=People,o=us.nortel.com" PullListenPort=4321 LogLogPort=4322 LogAccountPort=4323 DBAdminPassword=admin MaximumHeapSize=512 LDAPDIR=/opt/shasta/ldap/slapd-zrc2s0ns DBBackupTimeWait=300 DOMAIN_IP=localhost IIOP=0 RegionRootDir=/opt/shasta/scs6.0 SCSHead=/opt/shasta/scs6.0 LDAPServerIp=localhost LDAPServerPort=389 SCSBackup=/opt/shasta/scs6.0/backup LDAPPath=/opt/shasta/iplanet LDAPServerName=slapd-zrc2s0ns1 LogUser=pmuser zrc2s0ns#
6. Backup iPlanet database using iPlanet utility ldapsearch.

# cd /opt/shasta/iplanet/shared/bin # ./ldapsearch -p 389 -T -b "uid=admin,ou=People,o=us.nortel.com" "objectclass=*" > nortel_01062009
7. Copy the iPlanet database backup to the backup directory.

# cp nortel_01062009 /opt/BACKUP
8. Tar and compress the backup directory.

# cd /opt # tar cvf BACKUP_TO_MOVE.tar BACKUP # compress BACKUP_TO_MOVE.tar
9. FTP the tar/ compressed backup to a different server. This way the backup can be retrieved from the new server even if the old SCS server is down.
411-5221-309
Standard
06.30 March 10, 2010
779
Note: After perfoming a backup on the old SCS server, perform a new install of SCS 6.0.1 on the new server prior to starting the restore proceduer.
SCS and iPlanet restore example
62
1. Verify the tar/ compressed backup file from the old SCS server has been FTPed to the new SCS server. 2. Uncompress and untar the backup.
# uncompress BACKUP_TO_MOVE.tar.Z # tar xvf BACKUP_TO_MOVE.tar # cd BACKUP # ls nortel_01062009 solid_nortel_01062009.tar
3. Untar the SCS solid database backup.

# tar cvf solid_nortel_01062009.tar # cd solid_nortel_01062009 # ls sol00886.log sol00887.log solid.db solid.ini solmsg.out
4. Create a backup directory in the SCS database directory.

# mkdir -p /opt/shasta/scs6.0.1/opt/solidSolaris/database/backup
5. Copy the SCS solid database backup file to the backup directory.
# cp * /opt/shasta/scs6.0.1/opt/solidSolaris/database/backup # ls /opt/shasta/scs6.0.1/opt/solidSolaris/database/backup sol00886.log sol00887.log solid.db solid.ini solmsg.out
6. Remove the SCS database log files from the SCS database backup directory.
# rm /opt/shasta/scs6.0.1/opt/solidSolaris/database/backup/*.log
7. Copy the iPlanet backup to /opt/shasta/iplanet/shared/bin directory.

# cp vip* /opt/shasta/iplanet/shared/bin
8. Restore the iPlanet database backup.

# cd /opt/shasta/iplanet/shared/bin # ./ldapmodify -p 390 -D "cn=Directory Manager" -w dmanager -c -a -f nortel_iplanet_01062009 adding new entry uid=UShasta,ou=People, o=us.nortel.com adding new entry dc=ISPs,uid=UShasta,ou=People,o=us.nortel.com adding new entry dc=Areas,uid=UShasta,ou=People,o=us.nortel.com
GPRS/UMTS
780
adding new entry o=any,dc=ISPs,uid=UShasta,ou=People,o=us.nortel.com adding new entry dc=DomainGroups,o=any,dc=ISPs,uid=UShasta,ou=People,o=us.nortel.c om adding new entry o=li_default_isp,dc=ISPs,uid=UShasta,ou=People,o=us.nortel.com adding new entry dc=DomainGroups,o=li_default_isp,dc=ISPs,uid=UShasta,ou=People,o= us.nortel.com adding new entry o=Customers,o=li_default_isp,dc=ISPs,uid=UShasta,ou=People,o=us.n ortel.com adding new entry o=Isp,o=Customers,o=li_default_isp,dc=ISPs,uid=UShasta,ou=People, o=us.nortel.com adding new entry ou=People,o=Isp,o=Customers,o=li_default_isp,dc=ISPs,uid=UShasta, ou=People,o=us.nortel.com adding new entry ou=Sites,o=Isp,o=Customers,o=li_default_isp,dc=ISPs,uid=UShasta,o u=People,o=us.nortel.com adding new entry ou=Templates,o=Isp,o=Customers,o=li_default_isp,dc=ISPs,uid=UShas ta,ou=People,o=us.nortel.com adding new entry o=Realms,o=li_default_isp,dc=ISPs,uid=UShasta,ou=People,o=us.nort el.com adding new entry dc=li_default_isp,o=Realms,o=li_default_isp,dc=ISPs,uid=UShasta,o u=People,o=us.nortel.com adding new entry dc=li_default_isp,dc=li_default_isp,o=Realms,o=li_default_isp,dc= ISPs,uid=UShasta,ou=People,o=us.nortel.com ... ... <<restore logs not displayed completly>> adding new entry o=Customers,o=cbb,dc=ISPs,uid=UShasta,ou=People,o=us.nortel.com adding new entry o=Isp,o=Customers,o=cbb,dc=ISPs,uid=UShasta,ou=People,o=us.nortel .com adding new entry ou=People,o=Isp,o=Customers,o=cbb,dc=ISPs,uid=UShasta,ou=People,o =us.nortel.com adding new entry ou=Sites,o=Isp,o=Customers,o=cbb,dc=ISPs,uid=UShasta,ou=People,o= us.nortel.com
411-5221-309
Standard
06.30 March 10, 2010
781
adding new entry ou=Templates,o=Isp,o=Customers,o=cbb,dc=ISPs,uid=UShasta,ou=Peopl e,o=us.nortel.com adding new entry o=Realms,o=cbb,dc=ISPs,uid=UShasta,ou=People,o=us.nortel.com adding new entry dc=cbb,o=Realms,o=cbb,dc=ISPs,uid=UShasta,ou=People,o=us.nortel.c om adding new entry dc=cbb,dc=cbb,o=Realms,o=cbb,dc=ISPs,uid=UShasta,ou=People,o=us.n ortel.com adding new entry dc=DomainGroups,o=cbb,dc=ISPs,uid=UShasta,ou=People,o=us.nortel.c om
9. Restore the SCS solid database.

# cd /opt/shasta/scs6.0.1/bin # ./SCSAdmin restore solidDB This will overwrite database(s). Are you sure? (Y)es or (N)o: y Need to stop the solid database server... Delete the old database... Restore the database from /opt/shasta/scs503/opt/solidSolaris/ database/backup ... No match [1] 12155 Starting Solid Database Server:.Started Done. Finished restoring Solid Database, please restart SCS server manually.
10. Update the LDAPRoot uid parameter in SCS config file /opt/shasta/scs6.0.1/bin/.scs.config and /etc/shasta/scs.config to match the old SCS server. 11. In case the old and new SCS server have different IP addresses, modify the SCS server IP addresses from the SCS client. Refer to Procedure for Changing the SCS server IP address on page 347. 12. Restart the SCS server processes.
# ./SCSAdmin start /opt/shasta/scs6.0.1/bin/SCSWatch-disable: SCSWatch is already disabled /opt/shasta/scs6.0.1/bin/SCSLogcsv-disable: SCSCleanLogcsv is already disabled /opt/shasta/scs6.0.1/bin/SCSDiskUsageMonitor-disable: SCSDiskUsageMonitor is already disabled /opt/shasta/scs6.0.1/bin/SCSCleanXmlExportFiles-disable: SCSCleanXmlExportFiles is already disabled [1] 14261 Starting Solid Database Server:.Started [2] 14279 Starting SCS Daemon:.Started [3] 14292 Starting SCS Domain server:......Started
GPRS/UMTS
782

[4] 14321 Starting SNMP Proxy:.Started [5] 14330 Starting SCS CORBA Server:..........Started [6] 14359 Starting SCS Region server:......Started [7] 14388 Starting SCS Monitor server:......Started [8] 14417 Starting SCS Trap daemon:......Started [9] 14447 Starting SCS Pull Server:...Started [10] 14467 Starting SCS Log Server:..Started ------------------------------------------Nortel Service Creation System Server Version SCS GGSNS6.0.1_SCS6.0(1) ------------------------------------------Adding SCSCleanLogcsv first time Added SCSCleanLogcsv to crontab Adding SCSWatch to Crontab for first time. Added SCSWatch to crontab Adding SCSDiskUsageMonitor first time Added SCSDiskUsageMonitor to crontab Adding SCSCleanXmlExportFiles first time Added SCSCleanXmlExportFiles to crontab
411-5221-309
Standard
06.30 March 10, 2010
Appendix V: Log captures for SCS Full Server Backup and Restore
Full Server Backup
Full server backup for mirrored server capture:
1. Reboot server to single usermode urc2y3pa# sync;sync;sync urc2y3pa# init 0 urc2y3pa# INIT: New run level: 0 The system is coming down. Please wait. System services are now being stopped. Print services stopped. Mar 29 00:55:48 urc2y3pa syslogd: going down on signal 15 nfs umount: urc2y3pa:vold(pid234) server not responding: RPC: Program not registered Mar 29 00:55:49 /usr/sbin/vold[1616]: problem unmounting /vol; Interrupted system call Mar 29 00:55:51 in.rdiscd[119]: terminated umount: /opt busy The system is down. syncing file systems... done Program terminated
63
63
2. From the ok prompt, reboot the server into single usermode. Enter the root password when prompted {2} ok boot -rs Resetting ...
INIT: SINGLE USER MODE Type control-d to proceed with normal startup, (or give root password for system maintenance): root Login incorrect
GPRS/UMTS
784
Type control-d to proceed with normal startup, (or give root password for system maintenance): single-user privilege assigned to /dev/console. Entering System Maintenance Mode
3. Execute Full Server Backup script # cd /usr/local/nortel/tools/bin urc2y3pa# ls ds_backup.ksh ds_restore.sh ds_scsrestore.sh ds_exportEnv.awk ds_scsbackup.ksh
# ./ds_backup.ksh Wed Mar 29 01:00:07 CST 2006 : -----------------------------------------Wed Mar 29 01:00:07 CST 2006 : Checking /tmp/backup... Wed Mar 29 01:00:07 CST 2006 : /tmp/backup not found. Building it.
Wed Mar 29 01:00:07 CST 2006 : Checking /tmp/backup...Done Wed Mar 29 01:00:07 CST 2006 : -----------------------------------------Wed Mar 29 01:00:07 CST 2006 : ==== BACKUP PROCEDURE ================= Wed Mar 29 01:00:07 CST 2006 : Checking Current run level... Wed Mar 29 01:00:07 CST 2006 : Wed Mar 29 01:00:07 CST 2006 : Expected run level : S Current run level : S
Wed Mar 29 01:00:07 CST 2006 : Checking Current run level...Done Wed Mar 29 01:00:07 CST 2006 : -----------------------------------------starting rpc services: rpcbind done. Wed Mar 29 01:00:14 CST 2006 : -----------------------------------------Wed Mar 29 01:00:14 CST 2006 : Copying VTOCs in /tmp/backup... Wed Mar 29 01:00:14 CST 2006 : Wed Mar 29 01:00:14 CST 2006 : Wed Mar 29 01:00:14 CST 2006 : Wed Mar 29 01:00:14 CST 2006 : Wed Mar 29 01:00:14 CST 2006 : Dumping vtoc of c1t0d0s2 Dumping vtoc of c1t1d0s2 Dumping vtoc of c1t2d0s2 Dumping vtoc of c1t3d0s2 Dumping vtoc of c1t4d0s2
Wed Mar 29 01:00:14 CST 2006 : Copying VTOCs in /tmp/backup...Done Wed Mar 29 01:00:14 CST 2006 : -----------------------------------------Wed Mar 29 01:00:14 CST 2006 : ------------------------------------------
411-5221-309
Standard
06.30 March 10, 2010
Wed Mar 29 01:00:14 CST 2006 : Copying /usr/local/nortel/tools in /tmp/backup... Wed Mar 29 01:00:15 CST 2006 : Copying /usr/local/nortel/tools in /tmp/backup...Done Wed Mar 29 01:00:15 CST 2006 : -----------------------------------------Wed Mar 29 01:00:15 CST 2006 : -----------------------------------------Wed Mar 29 01:00:15 CST 2006 : Copying /etc/lvm/md.tab in /tmp/backup... Wed Mar 29 01:00:16 CST 2006 : Copying /etc/lvm/md.tab in /tmp/backup...Done Wed Mar 29 01:00:16 CST 2006 : Copying /etc/lvm/md.cf in /tmp/backup... Wed Mar 29 01:00:16 CST 2006 : Copying /etc/lvm/md.cf in /tmp/backup...Done Wed Mar 29 01:00:16 CST 2006 : Copying /etc/vfstab in /tmp/backup... Wed Mar 29 01:00:16 CST 2006 : Copying /etc/vfstab in /tmp/backup...Done Wed Mar 29 01:00:16 CST 2006 : -----------------------------------------Wed Mar 29 01:00:16 CST 2006 : -----------------------------------------Wed Mar 29 01:00:16 CST 2006 : Building backup library... Wed Mar 29 01:00:16 CST 2006 : Including / in /tmp/backup/catalogue.cfg... Wed Mar 29 01:00:17 CST 2006 : Including /var in /tmp/backup/catalogue.cfg... Wed Mar 29 01:00:18 CST 2006 : Including /home in /tmp/backup/catalogue.cfg... Wed Mar 29 01:00:18 CST 2006 : Including /opt in /tmp/backup/catalogue.cfg... Wed Mar 29 01:00:18 CST 2006 : Building backup library...Done Wed Mar 29 01:00:18 CST 2006 : -----------------------------------------Wed Mar 29 01:00:18 CST 2006 : -----------------------------------------Wed Mar 29 01:00:18 CST 2006 : Checking /tmp/backup total 34 -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -r--r--r-- 1 root -rw-r--r-- 1 root other other other other other other other other other other other other 0 Mar 29 01:00 830b4949.hostid 2653 Mar 29 01:00 backup.log 21 Mar 29 01:00 backuppos 692 Mar 29 01:00 c1t0d0s2.vtoc 586 Mar 29 01:00 c1t1d0s2.vtoc 692 Mar 29 01:00 c1t2d0s2.vtoc 586 Mar 29 01:00 c1t3d0s2.vtoc 480 Mar 29 01:00 c1t4d0s2.vtoc 74 Mar 29 01:00 catalogue.cfg 946 Mar 29 01:00 eeprom.cfg 124 Mar 29 01:00 hosts 301 Mar 29 01:00 md.cf
GPRS/UMTS
786
-rw-r--r-- 1 root -rw-r--r-- 1 root other other 622 Mar 29 01:00 md.db 293 Mar 29 01:00 md.tab 512 Mar 29 01:00 tools 709 Mar 29 01:00 vfstab
drwxr-xr-x 8 nortel nortel -rw-r--r-- 1 root other
c1t0d0s0;d0;/;system c1t0d0s5;d5;/var;system c1t1d0s0;d8;/opt;application Wed Mar 29 01:00:18 CST 2006 : -----------------------------------------Wed Mar 29 01:00:18 CST 2006 : ========================================= Wed Mar 29 01:00:18 CST 2006 : Building "SYSAPPDATA" tape... Wed Mar 29 01:00:18 CST 2006 : -----------------------------------------Wed Mar 29 01:00:18 CST 2006 : Checking SYSAPPDATA tape... Wed Mar 29 01:00:46 CST 2006 : Wed Mar 29 01:00:59 CST 2006 : Rewinding tape... Rewinding tape...Done
Wed Mar 29 01:00:59 CST 2006 : Checking SYSAPPDATA tape...Done Wed Mar 29 01:00:59 CST 2006 : -----------------------------------------Wed Mar 29 01:00:59 CST 2006 : ----------------------------------------Wed Mar 29 01:00:59 CST 2006 : Dumping "TAR0" to SYSAPPDATA tape... a /tmp/backup/ 0 tape blocks a /tmp/backup/backup.log 9 tape blocks a /tmp/backup/c1t0d0s2.vtoc 2 tape blocks a /tmp/backup/c1t1d0s2.vtoc 2 tape blocks a /tmp/backup/c1t2d0s2.vtoc 2 tape blocks a /tmp/backup/c1t3d0s2.vtoc 2 tape blocks a /tmp/backup/c1t4d0s2.vtoc 1 tape blocks a /tmp/backup/tools/ 0 tape blocks a /tmp/backup/tools/bin/ 0 tape blocks a /tmp/backup/tools/bin/ds_backup.ksh 42 tape blocks a /tmp/backup/tools/bin/ds_exportEnv.awk 1 tape blocks a /tmp/backup/tools/bin/ds_restore.sh 139 tape blocks a /tmp/backup/tools/bin/ds_scsbackup.ksh 28 tape blocks a /tmp/backup/tools/bin/ds_scsrestore.sh 58 tape blocks a /tmp/backup/tools/cfg/ 0 tape blocks a /tmp/backup/tools/cfg/ds_BR.env 4 tape blocks
411-5221-309
Standard
06.30 March 10, 2010
a /tmp/backup/tools/etc/ 0 tape blocks a /tmp/backup/tools/etc/init.d/ 0 tape blocks a /tmp/backup/tools/etc/init.d/mirror 2 tape blocks a /tmp/backup/tools/etc/init.d/nxt-step 2 tape blocks a /tmp/backup/tools/lib/ 0 tape blocks a /tmp/backup/tools/lib/ds_brLib.lib 28 tape blocks a /tmp/backup/tools/lib/ds_cmnLib.lib 14 tape blocks a /tmp/backup/tools/lib/ds_logMgt.lib 39 tape blocks a /tmp/backup/tools/lib/ds_system.lib 66 tape blocks a /tmp/backup/tools/log/ 0 tape blocks a /tmp/backup/tools/tmp/ 0 tape blocks a /tmp/backup/md.tab 1 tape blocks a /tmp/backup/md.cf 1 tape blocks a /tmp/backup/vfstab 2 tape blocks a /tmp/backup/md.db 2 tape blocks a /tmp/backup/eeprom.cfg 2 tape blocks a /tmp/backup/hosts 1 tape blocks a /tmp/backup/catalogue.cfg 1 tape blocks a /tmp/backup/backuppos 1 tape blocks a /tmp/backup/830b4949.hostid 0 tape blocks a /tmp/backup/SYSAPPDATA.label 0 tape blocks Wed Mar 29 01:01:05 CST 2006 : Dumping "TAR0" to SYSAPPDATA tape...Done Wed Mar 29 01:01:05 CST 2006 : ----------------------------------------Wed Mar 29 01:01:05 CST 2006 : / already mounted. No Sanity check needed Wed Mar 29 01:01:05 CST 2006 : /var already mounted. No Sanity check needed Wed Mar 29 01:01:05 CST 2006 : Dump of / (c1t0d0s0 - d0 - system)... Wed Mar 29 01:01:06 CST 2006 : Dump of /dev/md/rdsk/d0... DUMP: Writing 32 Kilobyte records DUMP: Date of this level 0 dump: Wed Mar 29 01:01:07 2006 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d0 (urc2y3pa:/) to /dev/rmt/0cn. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Estimated 879620 blocks (429.50MB).
GPRS/UMTS
788
DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files]
DUMP: 879614 blocks (429.50MB) on 1 volume at 1187 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Wed Mar 29 01:01:07 2006 Wed Mar 29 01:07:31 CST 2006 : Dump of / (c1t0d0s0 - d0 - system).Done Wed Mar 29 01:07:31 CST 2006 : Dump of /var (c1t0d0s5 - d5 - system)... Wed Mar 29 01:07:32 CST 2006 : Dump of /dev/md/rdsk/d5... DUMP: Writing 32 Kilobyte records DUMP: Date of this level 0 dump: Wed Mar 29 01:07:33 2006 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d5 (urc2y3pa:/var) to /dev/rmt/0cn. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Estimated 137998 blocks (67.38MB). DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 137982 blocks (67.37MB) on 1 volume at 1041 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Wed Mar 29 01:07:33 2006 Wed Mar 29 01:08:51 CST 2006 : Dump of /var (c1t0d0s5 - d5 - system).Done Wed Mar 29 01:08:51 CST 2006 : Dumping to "SYSAPPDATA" tape...Done Wed Mar 29 01:08:51 CST 2006 : ========================================= Wed Mar 29 01:08:51 CST 2006 : /opt not mounted. Processing sanity check... Wed Mar 29 01:08:52 CST 2006 : Sanity check of /opt OK. Wed Mar 29 01:08:52 CST 2006 : Dump of /opt (c1t1d0s0 - d8 - application)... Wed Mar 29 01:08:52 CST 2006 : Dump of /dev/md/rdsk/d8... DUMP: Writing 32 Kilobyte records DUMP: Date of this level 0 dump: Wed Mar 29 01:08:52 2006 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/md/rdsk/d8 (urc2y3pa:/opt) to /dev/rmt/0cn. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Estimated 2936300 blocks (1433.74MB).
411-5221-309
Standard
06.30 March 10, 2010
DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] Connection closed by foreign host. bash-2.02$ telnet 47.104.65.225 3000 Trying... Connected to 47.104.65.225. Escape character is '^]'.
DUMP: 51.88% done, finished in 0:09 DUMP: 2936254 blocks (1433.72MB) on 1 volume at 1296 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Wed Mar 29 01:08:52 2006 Wed Mar 29 01:28:08 CST 2006 : Dump of /opt (c1t1d0s0 - d8 - application).Done Wed Mar 29 01:28:08 CST 2006 : Dumping to "SYSAPPDATA" tape...Done Wed Mar 29 01:28:08 CST 2006 : ========================================= Wed Mar 29 01:28:11 CST 2006 : ejecting SYSAPPDATA tape.Please wait... Wed Mar 29 01:28:11 CST 2006 : Please write protect SYSAPPDATA tape.
Wed Mar 29 01:28:11 CST 2006 : ==== END of BACKUP PROCEDURE ==============
Reboot server
# init 6
End of full server backup for mirrored server capture End of full server backup for mirrored server capture. If additional non-critical filesystem partitions are mounted, please proceed to manually backup these partitions to tape following Appendix F: Performing Backup and Restore of Mounted Non-critical File Systems for Mirrored Servers on page 627
Full server backup for non-mirrored server capture:

1. Reboot server to run level 0 urc2y3pa# sync;sync;sync urc2y3pa# init 0 INIT: New run level: 0 The system is coming down. Please wait. System services are now being stopped. Print services stopped.
GPRS/UMTS
790
Mar 31 10:01:31 urc2y3pa syslogd: going down on signal 15 umount: /opt busy The system is down. syncing file systems... done Program terminated
2. At the ok prompt, reboot to single usermode {0} ok {0} ok boot -rs Resetting ... screen not found. keyboard not found. Keyboard not present. Using ttya for input and output. Sun Fire 880, No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.5, 4096 MB memory installed, Serial #51071305. Ethernet address 0:3:ba:b:49:49, Host ID: 830b4949. Rebooting with command: boot -rs Boot device: /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@0,0 File and args: -rs SunOS Release 5.8 Version Generic_117350-33 64-bit Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved. WARNING: Failed to install "bbc" driver. WARNING: Failed to install "gptwo" driver. configuring IPv4 interfaces: eri0 qfe3. Hostname: urc2y3pa metainit: urc2y3pa: there are no existing databases
Configuring /dev and /devices Configuring the /dev directory (compatibility devices) mount: /var/run already mounted
INIT: SINGLE USER MODE
3. Enter root password when prompted
411-5221-309
Standard
06.30 March 10, 2010
Type control-d to proceed with normal startup, (or give root password for system maintenance): single-user privilege assigned to /dev/console. Entering System Maintenance Mode
Mar 31 10:03:48 su: 'su root' succeeded for root on /dev/console Sun Microsystems Inc. SunOS 5.8 Generic Patch February 2004
4. Verify the tape is mounted urc2y3pa# mt status HP DDS-4 DAT (Sun) tape drive: sense key(0x6)= Unit Attention residual= 0 retries= 0 file no= 0 block no= 0
5. Perform full server backup urc2y3pa# cd /usr/local/nortel/tools/bin urc2y3pa# ls ds_backup.ksh ds_restore.sh ds_scsrestore.sh
ds_exportEnv.awk ds_scsbackup.ksh urc2y3pa# ./ds_backup.ksh Fri Mar 31 10:04:51 CST 2006 : backup SCS server with non-solaris volume manager configuration Fri Mar 31 10:04:51 CST 2006 : -----------------------------------------Fri Mar 31 10:04:51 CST 2006 : Checking /tmp/backup... Fri Mar 31 10:04:51 CST 2006 : Fri Mar 31 10:04:51 CST 2006 : /tmp/backup exists. Moving it to /tmp/backup.110 /tmp/backup not found. Building it.
Fri Mar 31 10:04:51 CST 2006 : Checking /tmp/backup...Done Fri Mar 31 10:04:51 CST 2006 : -----------------------------------------Fri Mar 31 10:04:51 CST 2006 : ========= BACKUP PROCEDURE ================= Fri Mar 31 10:04:51 CST 2006 : Checking Current run level... Fri Mar 31 10:04:51 CST 2006 : Fri Mar 31 10:04:51 CST 2006 : Expected run level : S Current run level : S
Fri Mar 31 10:04:51 CST 2006 : Checking Current run level...Done Fri Mar 31 10:04:51 CST 2006 : -----------------------------------------Fri Mar 31 10:04:51 CST 2006 : ------------------------------------------
GPRS/UMTS
792
Fri Mar 31 10:04:51 CST 2006 : Copying VTOCs in /tmp/backup... Fri Mar 31 10:04:51 CST 2006 : Fri Mar 31 10:04:51 CST 2006 : Fri Mar 31 10:04:51 CST 2006 : Fri Mar 31 10:04:51 CST 2006 : Fri Mar 31 10:04:51 CST 2006 : Dumping vtoc of c1t0d0s2 Dumping vtoc of c1t1d0s2 Dumping vtoc of c1t2d0s2 Dumping vtoc of c1t3d0s2 Dumping vtoc of c1t4d0s2
Fri Mar 31 10:04:51 CST 2006 : Copying VTOCs in /tmp/backup...Done Fri Mar 31 10:04:51 CST 2006 : -----------------------------------------Fri Mar 31 10:04:51 CST 2006 : -----------------------------------------Fri Mar 31 10:04:51 CST 2006 : Copying /usr/local/nortel/tools in /tmp/backup... Fri Mar 31 10:04:53 CST 2006 : Copying /usr/local/nortel/tools in /tmp/backup...Done Fri Mar 31 10:04:53 CST 2006 : -----------------------------------------Fri Mar 31 10:04:53 CST 2006 : -----------------------------------------Fri Mar 31 10:04:53 CST 2006 : Copying /etc/vfstab in /tmp/backup... Fri Mar 31 10:04:53 CST 2006 : Copying /etc/vfstab in /tmp/backup...Done Fri Mar 31 10:04:53 CST 2006 : -----------------------------------------Fri Mar 31 10:04:53 CST 2006 : -----------------------------------------Fri Mar 31 10:04:53 CST 2006 : Building backup library... Fri Mar 31 10:04:53 CST 2006 : Building backup library...Done Fri Mar 31 10:04:53 CST 2006 : -----------------------------------------Fri Mar 31 10:04:53 CST 2006 : -----------------------------------------Fri Mar 31 10:04:53 CST 2006 : Checking /tmp/backup total 24 -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -rw-r--r-- 1 root -r--r--r-- 1 root other other other other other other other other other other 0 Mar 31 10:04 830b4949.hostid 2037 Mar 31 10:04 backup.log 703 Mar 31 10:04 c1t0d0s2.vtoc 586 Mar 31 10:04 c1t1d0s2.vtoc 692 Mar 31 10:04 c1t2d0s2.vtoc 586 Mar 31 10:04 c1t3d0s2.vtoc 480 Mar 31 10:04 c1t4d0s2.vtoc 173 Mar 31 10:04 catalogue.cfg 887 Mar 31 10:04 eeprom.cfg 124 Mar 31 10:04 hosts 512 Mar 31 10:04 tools
drwxr-xr-x 8 nortel nortel
411-5221-309
Standard
06.30 March 10, 2010
other 715 Mar 31 10:04 vfstab
-rw-r--r-- 1 root
/dev/dsk/c1t0d0s0;/dev/rdsk/c1t0d0s0;/ /dev/dsk/c1t0d0s5;/dev/rdsk/c1t0d0s5;/var /dev/dsk/c1t0d0s7;/dev/rdsk/c1t0d0s7;/export/home /dev/dsk/c1t1d0s0;/dev/rdsk/c1t1d0s0;/opt Fri Mar 31 10:04:53 CST 2006 : -----------------------------------------Fri Mar 31 10:04:53 CST 2006 : ========================================= Fri Mar 31 10:04:53 CST 2006 : Building "SCS" tape... Fri Mar 31 10:04:53 CST 2006 : -----------------------------------------Fri Mar 31 10:04:53 CST 2006 : Checking SCS tape... Fri Mar 31 10:05:03 CST 2006 : Fri Mar 31 10:05:16 CST 2006 : Rewinding tape... Rewinding tape...Done
Fri Mar 31 10:05:16 CST 2006 : Checking SCS tape...Done Fri Mar 31 10:05:16 CST 2006 : -----------------------------------------Fri Mar 31 10:05:16 CST 2006 : ----------------------------------------Fri Mar 31 10:05:16 CST 2006 : Dumping "TAR0" to SCS tape... a /tmp/backup/ 0 tape blocks a /tmp/backup/backup.log 8 tape blocks a /tmp/backup/c1t0d0s2.vtoc 2 tape blocks a /tmp/backup/c1t1d0s2.vtoc 2 tape blocks a /tmp/backup/c1t2d0s2.vtoc 2 tape blocks a /tmp/backup/c1t3d0s2.vtoc 2 tape blocks a /tmp/backup/c1t4d0s2.vtoc 1 tape blocks a /tmp/backup/tools/ 0 tape blocks a /tmp/backup/tools/bin/ 0 tape blocks a /tmp/backup/tools/bin/ds_backup.ksh 42 tape blocks a /tmp/backup/tools/bin/ds_exportEnv.awk 1 tape blocks a /tmp/backup/tools/bin/ds_restore.sh 139 tape blocks a /tmp/backup/tools/bin/ds_scsbackup.ksh 28 tape blocks a /tmp/backup/tools/bin/ds_scsrestore.sh 58 tape blocks a /tmp/backup/tools/cfg/ 0 tape blocks a /tmp/backup/tools/cfg/ds_BR.env 4 tape blocks a /tmp/backup/tools/cfg/c1t0d0s2.vtoc 2 tape blocks a /tmp/backup/tools/cfg/c1t1d0s2.vtoc 2 tape blocks
GPRS/UMTS
794
a /tmp/backup/tools/cfg/c1t2d0s2.vtoc 2 tape blocks a /tmp/backup/tools/cfg/c1t3d0s2.vtoc 2 tape blocks a /tmp/backup/tools/cfg/c1t4d0s2.vtoc 1 tape blocks a /tmp/backup/tools/cfg/catalogue.cfg 1 tape blocks a /tmp/backup/tools/cfg/eeprom.cfg 2 tape blocks a /tmp/backup/tools/cfg/hosts 1 tape blocks a /tmp/backup/tools/cfg/md.cf 1 tape blocks a /tmp/backup/tools/cfg/md.db 2 tape blocks a /tmp/backup/tools/cfg/md.tab 1 tape blocks a /tmp/backup/tools/cfg/vtoc.lst 0 tape blocks a /tmp/backup/tools/cfg/boot-device.cfg 1 tape blocks a /tmp/backup/tools/etc/ 0 tape blocks a /tmp/backup/tools/etc/init.d/ 0 tape blocks a /tmp/backup/tools/etc/init.d/mirror 2 tape blocks a /tmp/backup/tools/etc/init.d/nxt-step 2 tape blocks a /tmp/backup/tools/etc/vfstab 2 tape blocks a /tmp/backup/tools/etc/lvm/ 0 tape blocks a /tmp/backup/tools/etc/lvm/md.cf 1 tape blocks a /tmp/backup/tools/etc/lvm/md.tab 1 tape blocks a /tmp/backup/tools/lib/ 0 tape blocks a /tmp/backup/tools/lib/ds_brLib.lib 28 tape blocks a /tmp/backup/tools/lib/ds_cmnLib.lib 14 tape blocks a /tmp/backup/tools/lib/ds_logMgt.lib 39 tape blocks a /tmp/backup/tools/lib/ds_system.lib 66 tape blocks a /tmp/backup/tools/log/ 0 tape blocks a /tmp/backup/tools/tmp/ 0 tape blocks a /tmp/backup/vfstab 2 tape blocks a /tmp/backup/eeprom.cfg 2 tape blocks a /tmp/backup/hosts 1 tape blocks a /tmp/backup/catalogue.cfg 1 tape blocks a /tmp/backup/830b4949.hostid 0 tape blocks a /tmp/backup/SCS.label 0 tape blocks
Fri Mar 31 10:05:22 CST 2006 : Dumping "TAR0" to SCS tape...Done Fri Mar 31 10:05:22 CST 2006 : -----------------------------------------
411-5221-309
Standard
06.30 March 10, 2010
Fri Mar 31 10:05:22 CST 2006 : / already mounted. No Sanity check needed Fri Mar 31 10:05:22 CST 2006 : /var already mounted. No Sanity check needed Fri Mar 31 10:05:22 CST 2006 : /export/home not mounted. Processing sanity check... Fri Mar 31 10:05:22 CST 2006 : Sanity check of /export/home OK. Fri Mar 31 10:05:22 CST 2006 : /opt not mounted. Processing sanity check... Fri Mar 31 10:05:22 CST 2006 : Sanity check of /opt OK. Fri Mar 31 10:05:22 CST 2006 : Dump of / ... Fri Mar 31 10:05:22 CST 2006 : Dump of /dev/rdsk/c1t0d0s0... DUMP: Writing 32 Kilobyte records DUMP: Date of this level 0 dump: Fri Mar 31 10:05:24 2006 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rdsk/c1t0d0s0 (urc2y3pa:/) to /dev/rmt/0cn. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Estimated 940966 blocks (459.46MB). DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 940926 blocks (459.44MB) on 1 volume at 4947 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Mar 31 10:05:24 2006 Fri Mar 31 10:07:04 CST 2006 : Dump of /.Done Fri Mar 31 10:07:04 CST 2006 : Dump of /var ... Fri Mar 31 10:07:04 CST 2006 : Dump of /dev/rdsk/c1t0d0s5... DUMP: Writing 32 Kilobyte records DUMP: Date of this level 0 dump: Fri Mar 31 10:07:04 2006 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rdsk/c1t0d0s5 (urc2y3pa:/var) to /dev/rmt/0cn. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Estimated 143492 blocks (70.06MB). DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 143486 blocks (70.06MB) on 1 volume at 2698 KB/sec DUMP: DUMP IS DONE
GPRS/UMTS
796
DUMP: Level 0 dump on Fri Mar 31 10:07:04 2006 Fri Mar 31 10:07:36 CST 2006 : Dump of /var.Done Fri Mar 31 10:07:36 CST 2006 : Dump of /export/home ... Fri Mar 31 10:07:37 CST 2006 : Dump of /dev/rdsk/c1t0d0s7... DUMP: Writing 32 Kilobyte records DUMP: Date of this level 0 dump: Fri Mar 31 10:07:37 2006 DUMP: Date of last level 0 dump: the epoch
DUMP: Dumping /dev/rdsk/c1t0d0s7 (urc2y3pa:/export/home) to /dev/rmt/0cn. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Estimated 340 blocks (170KB). DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 318 blocks (159KB) on 1 volume at 3974 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Mar 31 10:07:37 2006 Fri Mar 31 10:07:39 CST 2006 : Dump of /export/home.Done Fri Mar 31 10:07:39 CST 2006 : Dump of /opt ... Fri Mar 31 10:07:39 CST 2006 : Dump of /dev/rdsk/c1t1d0s0... DUMP: Writing 32 Kilobyte records DUMP: Date of this level 0 dump: Fri Mar 31 10:07:39 2006 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/rdsk/c1t1d0s0 (urc2y3pa:/opt) to /dev/rmt/0cn. DUMP: Mapping (Pass I) [regular files] DUMP: Mapping (Pass II) [directories] DUMP: Estimated 3775502 blocks (1843.51MB). DUMP: Dumping (Pass III) [directories] DUMP: Dumping (Pass IV) [regular files] DUMP: 3775486 blocks (1843.50MB) on 1 volume at 4261 KB/sec DUMP: DUMP IS DONE DUMP: Level 0 dump on Fri Mar 31 10:07:39 2006 Fri Mar 31 10:15:11 CST 2006 : Dump of /opt.Done Fri Mar 31 10:15:11 CST 2006 : Building "SCS" tape...Done Fri Mar 31 10:15:11 CST 2006 : =========================================
411-5221-309
Standard
06.30 March 10, 2010
Fri Mar 31 10:15:11 CST 2006 : ejecting SCS tape.Please wait... Fri Mar 31 10:15:11 CST 2006 : Please write protect SCS tape.
Fri Mar 31 10:15:11 CST 2006 : ===== END of BACKUP PROCEDURE ==============
End of Full server backup for non-mirrored server capture
Full Server Restore for Mirrored Servers on Solaris 8

1. Reboot server to single usermode urc2y3pa# sync;sync;sync urc2y3pa# init 0 urc2y3pa# INIT: New run level: 0 The system is coming down. Please wait. System services are now being stopped. Print services stopped. Mar 29 00:55:48 urc2y3pa syslogd: going down on signal 15 nfs umount: urc2y3pa:vold(pid234) server not responding: RPC: Program not registered Mar 29 00:55:49 /usr/sbin/vold[1616]: problem unmounting /vol; Interrupted system call Mar 29 00:55:51 in.rdiscd[119]: terminated umount: /opt busy The system is down. syncing file systems... done Program terminated
63
2. From the ok prompt, reboot the server into single usermode. Enter the root password when prompted {2} ok boot cdrom -rs Resetting ...
INIT: SINGLE USER MODE Entering System Maintenance Mode
GPRS/UMTS
798
3. Verify Backup Tape is mounted correctly
# mt status HP DDS-4 DAT (Sun) tape drive: sense key(0x6)= Unit Attention file no= 0 block no= 0
residual= 0
retries= 0
4. Extract backup from tape # cd / # tar xv x /tmp/backup, 0 bytes, 0 tape blocks x /tmp/backup/backup.log, 4518 bytes, 9 tape blocks x /tmp/backup/c1t0d0s2.vtoc, 692 bytes, 2 tape blocks x /tmp/backup/c1t1d0s2.vtoc, 586 bytes, 2 tape blocks x /tmp/backup/c1t2d0s2.vtoc, 692 bytes, 2 tape blocks x /tmp/backup/c1t3d0s2.vtoc, 586 bytes, 2 tape blocks x /tmp/backup/c1t4d0s2.vtoc, 480 bytes, 1 tape blocks x /tmp/backup/tools, 0 bytes, 0 tape blocks x /tmp/backup/tools/bin, 0 bytes, 0 tape blocks x /tmp/backup/tools/bin/ds_backup.ksh, 21041 bytes, 42 tape blocks x /tmp/backup/tools/bin/ds_exportEnv.awk, 177 bytes, 1 tape blocks x /tmp/backup/tools/bin/ds_restore.sh, 70827 bytes, 139 tape blocks x /tmp/backup/tools/bin/ds_scsbackup.ksh, 14058 bytes, 28 tape blocks x /tmp/backup/tools/bin/ds_scsrestore.sh, 29335 bytes, 58 tape blocks x /tmp/backup/tools/cfg, 0 bytes, 0 tape blocks x /tmp/backup/tools/cfg/ds_BR.env, 1703 bytes, 4 tape blocks x /tmp/backup/tools/etc, 0 bytes, 0 tape blocks
411-5221-309
Standard
06.30 March 10, 2010
x /tmp/backup/tools/etc/init.d, 0 bytes, 0 tape blocks x /tmp/backup/tools/etc/init.d/mirror, 520 bytes, 2 tape blocks x /tmp/backup/tools/etc/init.d/nxt-step, 861 bytes, 2 tape blocks x /tmp/backup/tools/lib, 0 bytes, 0 tape blocks x /tmp/backup/tools/lib/ds_brLib.lib, 13895 bytes, 28 tape blocks x /tmp/backup/tools/lib/ds_cmnLib.lib, 7118 bytes, 14 tape blocks x /tmp/backup/tools/lib/ds_logMgt.lib, 19593 bytes, 39 tape blocks x /tmp/backup/tools/lib/ds_system.lib, 33714 bytes, 66 tape blocks x /tmp/backup/tools/log, 0 bytes, 0 tape blocks x /tmp/backup/tools/tmp, 0 bytes, 0 tape blocks x /tmp/backup/md.tab, 293 bytes, 1 tape blocks x /tmp/backup/md.cf, 301 bytes, 1 tape blocks x /tmp/backup/vfstab, 709 bytes, 2 tape blocks x /tmp/backup/md.db, 622 bytes, 2 tape blocks x /tmp/backup/eeprom.cfg, 946 bytes, 2 tape blocks x /tmp/backup/hosts, 124 bytes, 1 tape blocks x /tmp/backup/catalogue.cfg, 74 bytes, 1 tape blocks x /tmp/backup/backuppos, 21 bytes, 1 tape blocks x /tmp/backup/830b4949.hostid, 0 bytes, 0 tape blocks x /tmp/backup/SYSAPPDATA.label, 0 bytes, 0 tape blocks # 5. Change directory to restore script location # cd /tmp/backup/tools/bin/ # ls ds_backup.ksh ds_restore.sh ds_scsrestore.sh
ds_exportEnv.awk ds_scsbackup.ksh
GPRS/UMTS
800
Appendix V: Log captures for SCS Full Server Backup and Restore 6. Execute restore script ds_restore.sh # ./ds_restore.sh START| START| START| START|
START| ################################################################## START| # NORTEL NETWORKS #
WARN |mkdir: "/usr/local/nortel": Operation not applicable START| ################################################################## WARN |mkdir: "/usr/local/nortel/tmp": Operation not applicable START| # DESC : FULL RESTORE #
WARN |mkdir: "/usr/local/nortel/data/backup-": Operation not applicable START| #----------------------------------------------------------------# START| # STARTING : ./ds_restore.sh START| # WITH : # # #
START| # LOG IN : /tmp/backup/tools/log/ds_restore.log START| #----------------------------------------------------------------# START| # DATE | VERSION | UID | HOSTNAME
START| #----------------------------------------------------------------# START| # 03/28/06 23:47:00 | V03_01.E05 | 0 | #
START| ################################################################## WARN |mkdir: "/etc/lvm": Read-only file system START| INFO | $NORTEL_DIR has read-only access.
411-5221-309
Standard
06.30 March 10, 2010
INFO | $NORTEL_TMPDIR has read-only access. INFO | $NORTEL_BACKUPDIR has read-only access. INFO | $SDS_CFG has read-only access. INFO | INFO |PRELIMINARY TASKS INFO | ================= INFO | INFO | INFO |TTY = /dev/syscon INFO | INFO | INFO | Ok INFO | INFO | INFO | Checking the OS CD-ROM ... OS CD-ROM = Solaris 8 Checking the eeprom ... Checking run level (must be in single user mode) ...
INFO |MNT = /mnt INFO |DEV = /dev/dsk/c1t0d0s0 INFO | Skip section <system> on device /dev/rmt/0 INFO |fmthard: New volume table of contents now in place. INFO |fmthard: New volume table of contents now in place. INFO |fmthard: New volume table of contents now in place. INFO |fmthard: New volume table of contents now in place. INFO |fmthard: New volume table of contents now in place. INFO | Create all the file systems for section <system>. INFO | --> device = /dev/dsk/c1t0d0s0 INFO | --> raw device= /dev/rdsk/c1t0d0s0 INFO | Create a new file system for /dev/rdsk/c1t0d0s0. GPRS/UMTS Upgrade Manual GGSN6.0
802
WARN |Cylinder groups must have a multiple of 16 cylinders with the given parameters WARN |Rounded cgsize up to 256 WARN |/dev/rdsk/c1t0d0s0: sectors 22528422 sectors in 7798 cylinders of 27 tracks, 107
WARN | 11000.2MB in 244 cyl groups (32 c/g, 45.14MB/g, 5632 i/g) WARN |super-block backups (for fsck -F ufs -o b=#) at: WARN | 32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072, WARN | 925632, 1018192, 1110752, 1203312, 1295872, 1388432, 1480992, 1573552, WARN | 1666112, 1758672, 1851232, 1943792, 2036352, 2128912, 2221472, 2314032, WARN | 2406592, 2499152, 2591712, 2684272, 2776832, 2869392, 2958368, 3050928, WARN | 3143488, 3236048, 3328608, 3421168, 3513728, 3606288, 3698848, 3791408, WARN | 3883968, 3976528, 4069088, 4161648, 4254208, 4346768, 4439328, 4531888, WARN | 4624448, 4717008, 4809568, 4902128, 4994688, 5087248, 5179808, 5272368, WARN | 5364928, 5457488, 5550048, 5642608, 5735168, 5827728, 5916704, 6009264, WARN | 6101824, 6194384, 6286944, 6379504, 6472064, 6564624, 6657184, 6749744, WARN | 6842304, 6934864, 7027424, 7119984, 7212544, 7305104, 7397664, 7490224, WARN | 7582784, 7675344, 7767904, 7860464, 7953024, 8045584, 8138144, 8230704, WARN | 8323264, 8415824, 8508384, 8600944, 8693504, 8786064, 8875040, 8967600, WARN | 9060160, 9152720, 9245280, 9337840, 9430400, 9522960, 9615520, 9708080, WARN | 9800640, 9893200, 9985760, 10078320, 10170880, 10263440, 10356000, 10448560, WARN | 10541120, 10633680, 10726240, 10818800, 10911360, 11003920, 11096480, WARN | 11189040, 11281600, 11374160, 11466720, 11559280, 11651840, 11744400, WARN | 11833376, 11925936, 12018496, 12111056, 12203616, 12296176, 12388736, WARN | 12481296, 12573856, 12666416, 12758976, 12851536, 12944096, 13036656, WARN | 13129216, 13221776, 13314336, 13406896, 13499456, 13592016, 13684576, WARN | 13777136, 13869696, 13962256, 14054816, 14147376, 14239936, 14332496,
411-5221-309
Standard
06.30 March 10, 2010
WARN | 14425056, 14517616, 14610176, 14702736, 14791712, 14884272, 14976832, WARN | 15069392, 15161952, 15254512, 15347072, 15439632, 15532192, 15624752, WARN | 15717312, 15809872, 15902432, 15994992, 16087552, 16180112, 16272672, WARN | 16365232, 16457792, 16550352, 16642912, 16735472, 16828032, 16920592, WARN | 17013152, 17105712, 17198272, 17290832, 17383392, 17475952, 17568512, WARN | 17661072, 17750048, 17842608, 17935168, 18027728, 18120288, 18212848, WARN | 18305408, 18397968, 18490528, 18583088, 18675648, 18768208, 18860768, WARN | 18953328, 19045888, 19138448, 19231008, 19323568, 19416128, 19508688, WARN | 19601248, 19693808, 19786368, 19878928, 19971488, 20064048, 20156608, WARN | 20249168, 20341728, 20434288, 20526848, 20619408, 20708384, 20800944, WARN | 20893504, 20986064, 21078624, 21171184, 21263744, 21356304, 21448864, WARN | 21541424, 21633984, 21726544, 21819104, 21911664, 22004224, 22096784, WARN | 22189344, 22281904, 22374464, 22467024, INFO | --> device = /dev/dsk/c1t0d0s5 INFO | --> raw device= /dev/rdsk/c1t0d0s5 INFO | Create a new file system for /dev/rdsk/c1t0d0s5. WARN |Cylinder groups must have a multiple of 16 cylinders with the given parameters WARN |Rounded cgsize up to 256 WARN |Warning: 1 sector(s) in last cylinder unallocated WARN |/dev/rdsk/c1t0d0s5: sectors 26044334 sectors in 9015 cylinders of 27 tracks, 107
WARN | 12717.0MB in 282 cyl groups (32 c/g, 45.14MB/g, 5632 i/g) WARN |super-block backups (for fsck -F ufs -o b=#) at: WARN | 32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072, WARN | 925632, 1018192, 1110752, 1203312, 1295872, 1388432, 1480992, 1573552, WARN | 1666112, 1758672, 1851232, 1943792, 2036352, 2128912, 2221472, 2314032, WARN | 2406592, 2499152, 2591712, 2684272, 2776832, 2869392, 2958368, 3050928, GPRS/UMTS Upgrade Manual GGSN6.0
804
WARN | 3143488, 3236048, 3328608, 3421168, 3513728, 3606288, 3698848, 3791408, WARN | 3883968, 3976528, 4069088, 4161648, 4254208, 4346768, 4439328, 4531888, WARN | 4624448, 4717008, 4809568, 4902128, 4994688, 5087248, 5179808, 5272368, WARN | 5364928, 5457488, 5550048, 5642608, 5735168, 5827728, 5916704, 6009264, WARN | 6101824, 6194384, 6286944, 6379504, 6472064, 6564624, 6657184, 6749744, WARN | 6842304, 6934864, 7027424, 7119984, 7212544, 7305104, 7397664, 7490224, WARN | 7582784, 7675344, 7767904, 7860464, 7953024, 8045584, 8138144, 8230704, WARN | 8323264, 8415824, 8508384, 8600944, 8693504, 8786064, 8875040, 8967600, WARN | 9060160, 9152720, 9245280, 9337840, 9430400, 9522960, 9615520, 9708080, WARN | 9800640, 9893200, 9985760, 10078320, 10170880, 10263440, 10356000, 10448560, WARN | 10541120, 10633680, 10726240, 10818800, 10911360, 11003920, 11096480, WARN | 11189040, 11281600, 11374160, 11466720, 11559280, 11651840, 11744400, WARN | 11833376, 11925936, 12018496, 12111056, 12203616, 12296176, 12388736, WARN | 12481296, 12573856, 12666416, 12758976, 12851536, 12944096, 13036656, WARN | 13129216, 13221776, 13314336, 13406896, 13499456, 13592016, 13684576, WARN | 13777136, 13869696, 13962256, 14054816, 14147376, 14239936, 14332496, WARN | 14425056, 14517616, 14610176, 14702736, 14791712, 14884272, 14976832, WARN | 15069392, 15161952, 15254512, 15347072, 15439632, 15532192, 15624752, WARN | 15717312, 15809872, 15902432, 15994992, 16087552, 16180112, 16272672, WARN | 16365232, 16457792, 16550352, 16642912, 16735472, 16828032, 16920592, WARN | 17013152, 17105712, 17198272, 17290832, 17383392, 17475952, 17568512, WARN | 17661072, 17750048, 17842608, 17935168, 18027728, 18120288, 18212848, WARN | 18305408, 18397968, 18490528, 18583088, 18675648, 18768208, 18860768, WARN | 18953328, 19045888, 19138448, 19231008, 19323568, 19416128, 19508688, WARN | 19601248, 19693808, 19786368, 19878928, 19971488, 20064048, 20156608, WARN | 20249168, 20341728, 20434288, 20526848, 20619408, 20708384, 20800944,
411-5221-309
Standard
06.30 March 10, 2010
WARN | 20893504, 20986064, 21078624, 21171184, 21263744, 21356304, 21448864, WARN | 21541424, 21633984, 21726544, 21819104, 21911664, 22004224, 22096784, WARN | 22189344, 22281904, 22374464, 22467024, 22559584, 22652144, 22744704, WARN | 22837264, 22929824, 23022384, 23114944, 23207504, 23300064, 23392624, WARN | 23485184, 23577744, 23666720, 23759280, 23851840, 23944400, 24036960, WARN | 24129520, 24222080, 24314640, 24407200, 24499760, 24592320, 24684880, WARN | 24777440, 24870000, 24962560, 25055120, 25147680, 25240240, 25332800, WARN | 25425360, 25517920, 25610480, 25703040, 25795600, 25888160, 25980720, INFO | Restoring / (/dev/dsk/c1t0d0s0) at 23:47:15
INFO | POS=1 ; OFFSET_POS=0 ; REAL_POS=1 INFO | fast forward tape to pos 1 INFO | /usr/sbin/ufsrestore rfy /dev/rmt/0n INFO |Warning: ./lost+found: File exists
INFO | Ok INFO | UFSRESTORE_CROSS_MSG, OFFSET_POS=0 INFO | Restoring /var (/dev/dsk/c1t0d0s5) at 23:56:36
INFO | POS=2 ; OFFSET_POS=0 ; REAL_POS=2 INFO | fast forward tape to pos 2
INFO | /usr/sbin/ufsrestore rfy /dev/rmt/0n INFO |Warning: ./lost+found: File exists
INFO | Ok INFO | UFSRESTORE_CROSS_MSG, OFFSET_POS=0 INFO | #### FS_LIST = / INFO |/var GPRS/UMTS Upgrade Manual GGSN6.0
806
Appendix V: Log captures for SCS Full Server Backup and Restore INFO | Mount all file systems for section <system>. INFO | Mount / on device /mnt/dev/dsk/c1t0d0s0. INFO | Mount /var on device /mnt/dev/dsk/c1t0d0s5. WARN |mkdir: "/etc/lvm": Read-only file system INFO | $SDS_CFG has read-only access. WARN |mv: cannot access /mnt/etc/init.d/svm.init WARN |mv: cannot access /mnt/etc/init.d/svm.sync INFO |79,96d78 INFO |< * Begin MDD root info (do not edit) INFO |< forceload: misc/md_trans INFO |< forceload: misc/md_raid INFO |< forceload: misc/md_hotspares INFO |< forceload: misc/md_sp INFO |< forceload: misc/md_stripe INFO |< forceload: misc/md_mirror INFO |< forceload: drv/pcisch INFO |< forceload: drv/qlc INFO |< forceload: drv/fp INFO |< forceload: drv/ssd INFO |< rootdev:/pseudo/md@0:0,0,blk INFO |< * End MDD root info (do not edit) INFO |< * Begin MDD database info (do not edit)
INFO |< set md:mddb_bootlist1="ssd:35:16 ssd:35:1050 ssd:35:2084 ssd:11:16" INFO |< set md:mddb_bootlist2="ssd:11:1050 ssd:11:2084 ssd:3:16 ssd:3:1050" INFO |< set md:mddb_bootlist3="ssd:3:2084 ssd:27:16 ssd:27:1050 ssd:27:2084" INFO |< * End MDD database info (do not edit) INFO | 411-5221-309 Standard Installing boot strap on /dev/rdsk/c1t0d0s0 ...
06.30 March 10, 2010
Nortel Networks Confidential INFO | Ok INFO |
Updating eeprom ...
INFO | BOOTDEV = /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w21000004cf78701b,0:a INFO | OLD BOOTDEV = /pci@8,600000/SUNW,qlc@2/fp@0,0/ disk@w21000004cf78701b,0:a disk0 disk6 INFO | NEW BOOTDEV = /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf78701b,0:a disk0 disk6 INFO | Ok INFO | INFO | before CopyBRTools, BR_DIR is /tmp/backup/tools tmp:
INFO |total 16 INFO |drwxr-xr-x 2 root INFO | INFO |log: INFO |total 48 INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO | INFO |lib: INFO |total 176 INFO |-r-xr-x--- 1 100 INFO |-r-xr-x--- 1 100 INFO |-r-xr-x--- 1 100 INFO |-r-xr-x--- 1 100 INFO | INFO |etc: GPRS/UMTS Upgrade Manual GGSN6.0 100 100 100 100 33714 Jan 20 12:28 ds_system.lib 19593 Jan 20 12:28 ds_logMgt.lib 7118 Jan 20 12:28 ds_cmnLib.lib 13895 Jan 20 12:28 ds_brLib.lib root root 36 Mar 28 23:47 globalLogFile.log 14685 Mar 28 23:58 ds_restore.log root 117 Mar 28 23:46 ds_restore200
808
Appendix V: Log captures for SCS Full Server Backup and Restore INFO |total 32 INFO |-rw-r--r-- 1 root INFO |dr-xr-x--- 2 100 INFO | INFO |cfg: INFO |total 208 INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO |-r--r--r-- 1 root INFO |-rw-r--r-- 1 root INFO |-r-xr-x--- 1 100 INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO |-rw-r--r-- 1 root INFO | INFO |bin: INFO |total 304 INFO |-r-xr-x--- 1 100 INFO |-r-xr-x--- 1 100 INFO |-r-xr-x--- 1 100 100 100 100 root other other other other other 100 other other other other other other root other other 100
709 Mar 28 23:00 vfstab 245 Mar 28 22:45 init.d
0 Mar 28 23:47 vtoc.lst 293 Mar 28 23:00 md.tab 622 Mar 28 23:00 md.db 301 Mar 28 23:00 md.cf 124 Mar 28 23:00 hosts 946 Mar 28 23:00 eeprom.cfg 1703 Jan 20 12:28 ds_BR.env 74 Mar 28 23:00 catalogue.cfg 480 Mar 28 23:00 c1t4d0s2.vtoc 586 Mar 28 23:00 c1t3d0s2.vtoc 692 Mar 28 23:00 c1t2d0s2.vtoc 586 Mar 28 23:00 c1t1d0s2.vtoc 692 Mar 28 23:00 c1t0d0s2.vtoc 71 Mar 28 23:58 boot-device.cfg 0 Mar 28 23:00 830b4949.hostid
29335 Jan 20 12:28 ds_scsrestore.sh 14058 Mar 28 22:47 ds_scsbackup.ksh 70827 Jan 20 12:28 ds_restore.sh
411-5221-309
Standard
06.30 March 10, 2010
Appendix V: Log captures for SCS Full Server Backup and Restore 809 100 100 177 Jan 20 12:28 ds_exportEnv.awk 21041 Mar 28 22:47 ds_backup.ksh
INFO |-r-xr-x--- 1 100 INFO |-r-xr-x--- 1 100
INFO | BR_DIR=/tmp/backup/tools ; MNTNORTEL_DIR=/mnt/usr/local/nortel INFO | cp -rp RC= 0 INFO | !!! INFO: Insert the first tape <application> in the drive. !!! INFO | *** INFO | *** If this server does not reboot in the next five minutes INFO | *** Please, enter 'reboot -- -rs' on the command line INFO | *** syncing file systems... done rebooting... Resetting ... Comment: Here the restore script reboots the server and proceeds with the restore procedure screen not found. keyboard not found. Keyboard not present. Using ttya for input and output. Sun Fire 880, No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.5, 4096 MB memory installed, Serial #51071305. Ethernet address 0:3:ba:b:49:49, Host ID: 830b4949. Rebooting with command: boot -rs Boot device: /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf78701b,0:a File and args: -rs SunOS Release 5.8 Version Generic_117350-33 64-bit Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved. WARNING: Failed to install "bbc" driver. GPRS/UMTS Upgrade Manual GGSN6.0
810
Appendix V: Log captures for SCS Full Server Backup and Restore WARNING: Failed to install "gptwo" driver. ifconfig: plumb: qfe3: Bad file number configuring IPv4 interfaces: eri0.
moving addresses from failed IPv4 interfaces: qfe3 (couldn't move, no alternative interface). Hostname: urc2y3pa Configuring /dev and /devices Configuring the /dev directory (compatibility devices) START| START| START| START| START| ################################################################## START| # NORTEL NETWORKS #
START| ################################################################## START| # DESC : FULL RESTORE #
START| #----------------------------------------------------------------# START| # STARTING : /usr/local/nortel/tools/bin/ds_restore.sh START| # WITH : RESTORE_STEP=mirror # # #
START| # LOG IN : /usr/local/nortel/tools/log/ds_restore.log START| #----------------------------------------------------------------# START| # DATE | VERSION | UID | HOSTNAME
START| #----------------------------------------------------------------# START| # 03/29/06 02:00:54 | V03_01.E05 | 0 | urc2y3pa #
START| ################################################################## START|
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential INFO |
INFO |PRELIMINARY TASKS INFO | ================= INFO | INFO | INFO |TTY = /dev/console INFO | INFO | INFO | Ok INFO | Checking the eeprom ... Checking run level (must be in single user mode) ...
INFO |MNT = /mnt INFO |DEV = /dev/md/dsk/d0 INFO |Starting IPv4 routing daemon. INFO |Setting netmask of eri0 to 255.255.252.0 INFO |Setting default IPv4 interface for multicast: add net 224.0/4: gateway urc2y3pa WARN |mv: cannot access /etc/init.d/svm.init.old WARN |mv: cannot access /etc/init.d/svm.sync.old INFO | Delete metadevices INFO | metadb -d -f /dev/dsk/c1t0d0s3 /dev/dsk/c1t1d0s3 /dev/dsk/c1t2d0s3 /dev/dsk/c1t3d0s3 INFO | Create metadevices INFO | metadb -a -f -c 3 mddb01 INFO | Clear metadevices INFO |d0: Mirror is cleared INFO |d10: Concat/Stripe is cleared INFO |d20: Concat/Stripe is cleared INFO |d1: Mirror is cleared GPRS/UMTS Upgrade Manual GGSN6.0
812
Appendix V: Log captures for SCS Full Server Backup and Restore INFO |d11: Concat/Stripe is cleared INFO |d21: Concat/Stripe is cleared INFO |d5: Mirror is cleared INFO |d15: Concat/Stripe is cleared INFO |d25: Concat/Stripe is cleared INFO |d7: Mirror is cleared INFO |d17: Concat/Stripe is cleared INFO |d27: Concat/Stripe is cleared INFO |d8: Mirror is cleared INFO |d18: Concat/Stripe is cleared INFO |d28: Concat/Stripe is cleared INFO | Initialize metadevices INFO |d10: Concat/Stripe is setup INFO |d20: Concat/Stripe is setup INFO |d11: Concat/Stripe is setup INFO |d21: Concat/Stripe is setup INFO |d15: Concat/Stripe is setup INFO |d25: Concat/Stripe is setup INFO |d17: Concat/Stripe is setup INFO |d27: Concat/Stripe is setup INFO |d18: Concat/Stripe is setup INFO |d28: Concat/Stripe is setup INFO |d0: Mirror is setup INFO |d1: Mirror is setup INFO |d5: Mirror is setup INFO |d7: Mirror is setup INFO |d8: Mirror is setup
411-5221-309
Standard
06.30 March 10, 2010
WARN |/usr/local/nortel/tools/bin/ds_restore.sh: /etc/init.d/mirror: not found WARN |/usr/local/nortel/tools/bin/ds_restore.sh: /etc/init.d/mirror: not found INFO | *** PLEASE, REBOOT NOW... INFO | *** Enter 'init 6' on the command line END | END | END | END | END | END | ################################################################## END | # END OF : ds_restore.sh END | # WITH : RESTORE_STEP=mirror # #
END | #----------------------------------------------------------------# END | # STATUS : 0 # # #
END | # LOG IN : /usr/local/nortel/tools/log/ds_restore.log END | # END DATE : 03/29/06 02:01:45
END | ################################################################## END | # NORTEL NETWORKS #
END | ##################################################################
Comment: Login to single usermode by entring root password INIT: SINGLE USER MODE
Type control-d to proceed with normal startup, (or give root password for system maintenance):
GPRS/UMTS
814
Appendix V: Log captures for SCS Full Server Backup and Restore single-user privilege assigned to /dev/console. Entering System Maintenance Mode
Mar 29 02:01:57 su: 'su root' succeeded for root on /dev/console Sun Microsystems Inc. SunOS 5.8 Generic Patch February 2004
Comment: Reboot the server manually urc2y3pa# init 6 INIT: New run level: 6 The system is coming down. Please wait. System services are now being stopped. Print services already stopped. The system is down. syncing file systems... done rebooting... Resetting ... screen not found. keyboard not found. Keyboard not present. Using ttya for input and output. Sun Fire 880, No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.5, 4096 MB memory installed, Serial #51071305. Ethernet address 0:3:ba:b:49:49, Host ID: 830b4949. Rebooting with command: boot Boot device: /pci@8,600000/SUNW,qlc@2/fp@0,0/disk@w21000004cf78701b,0:a File and args: SunOS Release 5.8 Version Generic_117350-33 64-bit
411-5221-309
Standard
06.30 March 10, 2010
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved. WARNING: forceload of misc/md_trans failed WARNING: forceload of misc/md_raid failed WARNING: forceload of misc/md_hotspares failed WARNING: forceload of misc/md_sp failed WARNING: Failed to install "bbc" driver. WARNING: Failed to install "gptwo" driver. configuring IPv4 interfaces: eri0 qfe3. Hostname: urc2y3pa START| START| START| START| START| ################################################################## START| # NORTEL NETWORKS #
START| #----------------------------------------------------------------# START| # STARTING : /usr/local/nortel/tools/bin/ds_restore.sh START| # WITH : RESTORE_STEP=application # # #
START| # LOG IN : /usr/local/nortel/tools/log/ds_restore.log START| #----------------------------------------------------------------# START| # DATE | VERSION | UID | HOSTNAME
START| #----------------------------------------------------------------# START| # 03/29/06 02:03:44 | V03_01.E05 | 0 | urc2y3pa #
GPRS/UMTS
816
START| ################################################################## START| INFO | INFO |PRELIMINARY TASKS INFO | ================= INFO | INFO | INFO |TTY = /dev/console INFO | INFO | INFO | Ok INFO | Checking the eeprom ... Checking run level (must be in single user mode) ...
INFO |MNT = /mnt INFO |DEV = /dev/md/dsk/d0 INFO |Machine is an IPv4 router. INFO |Setting netmask of eri0 to 255.255.252.0 INFO |Setting default IPv4 interface for multicast: add net 224.0/4: gateway urc2y3pa INFO |d0: submirror d20 is attached INFO |d1: submirror d21 is attached INFO |d5: submirror d25 is attached INFO |d7: submirror d27 is attached INFO |d8: submirror d28 is attached INFO | Check sub-mirrors INFO | ... Done WARN |/usr/local/nortel/tools/bin/ds_restore.sh: /etc/init.d/mirror: not found INFO | current OFFSET_POS=0
411-5221-309
Standard
06.30 March 10, 2010
INFO | OFFSET_POS=0 INFO | Create all the file systems for section <application>. INFO | --> device = /dev/md/dsk/d8 INFO | --> raw device= /dev/md/rdsk/d8 INFO | Create a new file system for /dev/md/rdsk/d8. WARN |Cylinder groups must have a multiple of 16 cylinders with the given parameters WARN |Rounded cgsize up to 256 WARN |/dev/md/rdsk/d8: 69208884 sectors in 23956 cylinders of 27 tracks, 107 sectors WARN | 33793.4MB in 749 cyl groups (32 c/g, 45.14MB/g, 5632 i/g) WARN |super-block backups (for fsck -F ufs -o b=#) at: WARN | 32, 92592, 185152, 277712, 370272, 462832, 555392, 647952, 740512, 833072, WARN | 925632, 1018192, 1110752, 1203312, 1295872, 1388432, 1480992, 1573552, WARN | 1666112, 1758672, 1851232, 1943792, 2036352, 2128912, 2221472, 2314032, WARN | 2406592, 2499152, 2591712, 2684272, 2776832, 2869392, 2958368, 3050928, WARN | 3143488, 3236048, 3328608, 3421168, 3513728, 3606288, 3698848, 3791408, WARN | 3883968, 3976528, 4069088, 4161648, 4254208, 4346768, 4439328, 4531888, WARN | 4624448, 4717008, 4809568, 4902128, 4994688, 5087248, 5179808, 5272368, WARN | 5364928, 5457488, 5550048, 5642608, 5735168, 5827728, 5916704, 6009264, WARN | 6101824, 6194384, 6286944, 6379504, 6472064, 6564624, 6657184, 6749744, WARN | 6842304, 6934864, 7027424, 7119984, 7212544, 7305104, 7397664, 7490224, WARN | 7582784, 7675344, 7767904, 7860464, 7953024, 8045584, 8138144, 8230704, WARN | 8323264, 8415824, 8508384, 8600944, 8693504, 8786064, 8875040, 8967600, WARN | 9060160, 9152720, 9245280, 9337840, 9430400, 9522960, 9615520, 9708080, WARN | 9800640, 9893200, 9985760, 10078320, 10170880, 10263440, 10356000, 10448560, WARN | 10541120, 10633680, 10726240, 10818800, 10911360, 11003920, 11096480, WARN | 11189040, 11281600, 11374160, 11466720, 11559280, 11651840, 11744400, GPRS/UMTS Upgrade Manual GGSN6.0
818
WARN | 11833376, 11925936, 12018496, 12111056, 12203616, 12296176, 12388736, WARN | 12481296, 12573856, 12666416, 12758976, 12851536, 12944096, 13036656, WARN | 13129216, 13221776, 13314336, 13406896, 13499456, 13592016, 13684576, WARN | 13777136, 13869696, 13962256, 14054816, 14147376, 14239936, 14332496, WARN | 14425056, 14517616, 14610176, 14702736, 14791712, 14884272, 14976832, WARN | 15069392, 15161952, 15254512, 15347072, 15439632, 15532192, 15624752, WARN | 15717312, 15809872, 15902432, 15994992, 16087552, 16180112, 16272672, WARN | 16365232, 16457792, 16550352, 16642912, 16735472, 16828032, 16920592, WARN | 17013152, 17105712, 17198272, 17290832, 17383392, 17475952, 17568512, WARN | 17661072, 17750048, 17842608, 17935168, 18027728, 18120288, 18212848, WARN | 18305408, 18397968, 18490528, 18583088, 18675648, 18768208, 18860768, WARN | 18953328, 19045888, 19138448, 19231008, 19323568, 19416128, 19508688, WARN | 19601248, 19693808, 19786368, 19878928, 19971488, 20064048, 20156608, WARN | 20249168, 20341728, 20434288, 20526848, 20619408, 20708384, 20800944, WARN | 20893504, 20986064, 21078624, 21171184, 21263744, 21356304, 21448864, WARN | 21541424, 21633984, 21726544, 21819104, 21911664, 22004224, 22096784, WARN | 22189344, 22281904, 22374464, 22467024, 22559584, 22652144, 22744704, WARN | 22837264, 22929824, 23022384, 23114944, 23207504, 23300064, 23392624, WARN | 23485184, 23577744, 23666720, 23759280, 23851840, 23944400, 24036960, WARN | 24129520, 24222080, 24314640, 24407200, 24499760, 24592320, 24684880, WARN | 24777440, 24870000, 24962560, 25055120, 25147680, 25240240, 25332800, WARN | 25425360, 25517920, 25610480, 25703040, 25795600, 25888160, 25980720, WARN | 26073280, 26165840, 26258400, 26350960, 26443520, 26536080, 26625056, WARN | 26717616, 26810176, 26902736, 26995296, 27087856, 27180416, 27272976, WARN | 27365536, 27458096, 27550656, 27643216, 27735776, 27828336, 27920896, WARN | 28013456, 28106016, 28198576, 28291136, 28383696, 28476256, 28568816, WARN | 28661376, 28753936, 28846496, 28939056, 29031616, 29124176, 29216736, 411-5221-309 Standard 06.30 March 10, 2010
WARN | 29309296, 29401856, 29494416, 29583392, 29675952, 29768512, 29861072, WARN | 29953632, 30046192, 30138752, 30231312, 30323872, 30416432, 30508992, WARN | 30601552, 30694112, 30786672, 30879232, 30971792, 31064352, 31156912, WARN | 31249472, 31342032, 31434592, 31527152, 31619712, 31712272, 31804832, WARN | 31897392, 31989952, 32082512, 32175072, 32267632, 32360192, 32452752, WARN | 32541728, 32634288, 32726848, 32819408, 32911968, 33004528, 33097088, WARN | 33189648, 33282208, 33374768, 33467328, 33559888, 33652448, 33745008, WARN | 33837568, 33930128, 34022688, 34115248, 34207808, 34300368, 34392928, WARN | 34485488, 34578048, 34670608, 34763168, 34855728, 34948288, 35040848, WARN | 35133408, 35225968, 35318528, 35411088, 35500064, 35592624, 35685184, WARN | 35777744, 35870304, 35962864, 36055424, 36147984, 36240544, 36333104, WARN | 36425664, 36518224, 36610784, 36703344, 36795904, 36888464, 36981024, WARN | 37073584, 37166144, 37258704, 37351264, 37443824, 37536384, 37628944, WARN | 37721504, 37814064, 37906624, 37999184, 38091744, 38184304, 38276864, WARN | 38369424, 38458400, 38550960, 38643520, 38736080, 38828640, 38921200, WARN | 39013760, 39106320, 39198880, 39291440, 39384000, 39476560, 39569120, WARN | 39661680, 39754240, 39846800, 39939360, 40031920, 40124480, 40217040, WARN | 40309600, 40402160, 40494720, 40587280, 40679840, 40772400, 40864960, WARN | 40957520, 41050080, 41142640, 41235200, 41327760, 41416736, 41509296, WARN | 41601856, 41694416, 41786976, 41879536, 41972096, 42064656, 42157216, WARN | 42249776, 42342336, 42434896, 42527456, 42620016, 42712576, 42805136, WARN | 42897696, 42990256, 43082816, 43175376, 43267936, 43360496, 43453056, WARN | 43545616, 43638176, 43730736, 43823296, 43915856, 44008416, 44100976, WARN | 44193536, 44286096, 44375072, 44467632, 44560192, 44652752, 44745312, WARN | 44837872, 44930432, 45022992, 45115552, 45208112, 45300672, 45393232, WARN | 45485792, 45578352, 45670912, 45763472, 45856032, 45948592, 46041152, WARN | 46133712, 46226272, 46318832, 46411392, 46503952, 46596512, 46689072, GPRS/UMTS Upgrade Manual GGSN6.0
820
WARN | 46781632, 46874192, 46966752, 47059312, 47151872, 47244432, 47333408, WARN | 47425968, 47518528, 47611088, 47703648, 47796208, 47888768, 47981328, WARN | 48073888, 48166448, 48259008, 48351568, 48444128, 48536688, 48629248, WARN | 48721808, 48814368, 48906928, 48999488, 49092048, 49184608, 49277168, WARN | 49369728, 49462288, 49554848, 49647408, 49739968, 49832528, 49925088, WARN | 50017648, 50110208, 50202768, 50291744, 50384304, 50476864, 50569424, WARN | 50661984, 50754544, 50847104, 50939664, 51032224, 51124784, 51217344, WARN | 51309904, 51402464, 51495024, 51587584, 51680144, 51772704, 51865264, WARN | 51957824, 52050384, 52142944, 52235504, 52328064, 52420624, 52513184, WARN | 52605744, 52698304, 52790864, 52883424, 52975984, 53068544, 53161104, WARN | 53250080, 53342640, 53435200, 53527760, 53620320, 53712880, 53805440, WARN | 53898000, 53990560, 54083120, 54175680, 54268240, 54360800, 54453360, WARN | 54545920, 54638480, 54731040, 54823600, 54916160, 55008720, 55101280, WARN | 55193840, 55286400, 55378960, 55471520, 55564080, 55656640, 55749200, WARN | 55841760, 55934320, 56026880, 56119440, 56208416, 56300976, 56393536, WARN | 56486096, 56578656, 56671216, 56763776, 56856336, 56948896, 57041456, WARN | 57134016, 57226576, 57319136, 57411696, 57504256, 57596816, 57689376, WARN | 57781936, 57874496, 57967056, 58059616, 58152176, 58244736, 58337296, WARN | 58429856, 58522416, 58614976, 58707536, 58800096, 58892656, 58985216, WARN | 59077776, 59166752, 59259312, 59351872, 59444432, 59536992, 59629552, WARN | 59722112, 59814672, 59907232, 59999792, 60092352, 60184912, 60277472, WARN | 60370032, 60462592, 60555152, 60647712, 60740272, 60832832, 60925392, WARN | 61017952, 61110512, 61203072, 61295632, 61388192, 61480752, 61573312, WARN | 61665872, 61758432, 61850992, 61943552, 62036112, 62125088, 62217648, WARN | 62310208, 62402768, 62495328, 62587888, 62680448, 62773008, 62865568, WARN | 62958128, 63050688, 63143248, 63235808, 63328368, 63420928, 63513488, WARN | 63606048, 63698608, 63791168, 63883728, 63976288, 64068848, 64161408, 411-5221-309 Standard 06.30 March 10, 2010
WARN | 64253968, 64346528, 64439088, 64531648, 64624208, 64716768, 64809328, WARN | 64901888, 64994448, 65083424, 65175984, 65268544, 65361104, 65453664, WARN | 65546224, 65638784, 65731344, 65823904, 65916464, 66009024, 66101584, WARN | 66194144, 66286704, 66379264, 66471824, 66564384, 66656944, 66749504, WARN | 66842064, 66934624, 67027184, 67119744, 67212304, 67304864, 67397424, WARN | 67489984, 67582544, 67675104, 67767664, 67860224, 67952784, 68041760, WARN | 68134320, 68226880, 68319440, 68412000, 68504560, 68597120, 68689680, WARN | 68782240, 68874800, 68967360, 69059920, 69152480,
INFO |
Restoring /opt (/dev/md/dsk/d8) at 02:05:07
INFO | POS=3 ; OFFSET_POS=0 ; REAL_POS=3 INFO | fast forward tape to pos 3 INFO | /usr/sbin/ufsrestore rfy /dev/rmt/0n INFO |Warning: ./lost+found: File exists INFO | Ok INFO | UFSRESTORE_CROSS_MSG, OFFSET_POS=0 INFO | Synchronize metadevice / system INFO | WARNING: This can be long, please wait... INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: Resync in progress: 19 % done Resync in progress: 24 % done Resync in progress: 19 % done Resync in progress: 25 % done Resync in progress: 20 % done Resync in progress: 25 % done Resync in progress: 20 % done Resync in progress: 26 % done Resync in progress: 21 % done GPRS/UMTS Upgrade Manual GGSN6.0
822
Appendix V: Log captures for SCS Full Server Backup and Restore INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: Resync in progress: 27 % done Resync in progress: 22 % done Resync in progress: 28 % done Resync in progress: 22 % done Resync in progress: 29 % done Resync in progress: 23 % done Resync in progress: 29 % done Resync in progress: 23 % done Resync in progress: 30 % done Resync in progress: 24 % done Resync in progress: 30 % done Resync in progress: 24 % done Resync in progress: 31 % done Resync in progress: 25 % done Resync in progress: 31 % done Resync in progress: 25 % done Resync in progress: 32 % done Resync in progress: 26 % done Resync in progress: 32 % done Resync in progress: 26 % done Resync in progress: 33 % done Resync in progress: 27 % done Resync in progress: 33 % done Resync in progress: 27 % done Resync in progress: 34 % done Resync in progress: 28 % done Resync in progress: 34 % done
411-5221-309
Standard
06.30 March 10, 2010
Nortel Networks Confidential INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0: INFO |d5: INFO | d0:
Appendix V: Log captures for SCS Full Server Backup and Restore 823 Resync in progress: 28 % done Resync in progress: 35 % done Resync in progress: 29 % done Resync in progress: 36 % done Resync in progress: 30 % done Resync in progress: 37 % done Resync in progress: 31 % done Resync in progress: 37 % done Resync in progress: 31 % done Resync in progress: 38 % done Resync in progress: 31 % done Resync in progress: 39 % done Resync in progress: 32 % done Resync in progress: 39 % done Resync in progress: 33 % done Resync in progress: 40 % done Resync in progress: 34 % done Resync in progress: 41 % done Resync in progress: 34 % done Resync in progress: 42 % done Resync in progress: 35 % done Resync in progress: 42 % done Resync in progress: 35 % done Resync in progress: 43 % done Resync in progress: 36 % done Resync in progress: 43 % done Resync in progress: 36 % done GPRS/UMTS Upgrade Manual GGSN6.0
824
411-5221-309
Standard
06.30 March 10, 2010
826
411-5221-309
Standard
06.30 March 10, 2010
828
411-5221-309
Standard
06.30 March 10, 2010
830
Appendix V: Log captures for SCS Full Server Backup and Restore INFO |d5: INFO | d0: INFO |d5: INFO | INFO | Server platform = SUNW,Sun-Fire-880 Resync in progress: 96 % done Resync in progress: 97 % done Resync in progress: 97 % done
WARN |/usr/local/nortel/tools/bin/ds_restore.sh: /etc/init.d/mirror: not found INFO | *** PLEASE, REBOOT NOW... INFO | *** Enter 'init 6' on the command line END | END | END | END | END | END | ################################################################## END | # END OF : ds_restore.sh END | # WITH : RESTORE_STEP=application # #
Comment: Login to single usermode by entering root password INIT: SINGLE USER MODE Type control-d to proceed with normal startup, (or give root password for system maintenance): Mar 29 05:58:48 su: 'su root' succeeded for root on /dev/console Sun Microsystems Inc. SunOS 5.8 Generic Patch February 2004
Comment: Reboot server urc2y3pa# init 6
411-5221-309
Standard
06.30 March 10, 2010
INIT: New run level: 6 The system is coming down. Please wait. System services are now being stopped. Print services already stopped. Mar 29 05:59:16 in.rdiscd[225]: terminated The system is down. syncing file systems... done rebooting... Resetting ... screen not found. keyboard not found. Keyboard not present. Using ttya for input and output. Sun Fire 880, No Keyboard Copyright 1998-2002 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.5, 4096 MB memory installed, Serial #51071305. Ethernet address 0:3:ba:b:49:49, Host ID: 830b4949. Rebooting with command: boot Boot device: disk0 File and args: SunOS Release 5.8 Version Generic_117350-33 64-bit Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved. WARNING: forceload of misc/md_trans failed WARNING: forceload of misc/md_raid failed WARNING: forceload of misc/md_hotspares failed WARNING: forceload of misc/md_sp failed WARNING: Failed to install "bbc" driver. WARNING: Failed to install "gptwo" driver. GPRS/UMTS Upgrade Manual GGSN6.0
832
Appendix V: Log captures for SCS Full Server Backup and Restore configuring IPv4 interfaces: eri0 qfe3. Hostname: urc2y3pa The system is coming up. Please wait. checking ufs filesystems /dev/md/rdsk/d8: is clean. /dev/md/rdsk/d7: is clean. Machine is an IPv4 router. starting rpc services: rpcbind done. Setting netmask of eri0 to 255.255.252.0
Setting default IPv4 interface for multicast: add net 224.0/4: gateway urc2y3pa syslog service starting. Print services started. volume management starting. The system is ready.
Comment: Login to the server and verify the mirrors urc2y3pa console login: root Password: Mar 29 07:28:39 urc2y3pa login: ROOT LOGIN /dev/console Last login: Wed Mar 29 00:52:37 from 192.168.1.1 Sun Microsystems Inc. SunOS 5.8 urc2y3pa# df -k Filesystem /dev/md/dsk/d0 /proc fd mnttab 411-5221-309 Standard kbytes used avail capacity Mounted on 4% / Generic Patch February 2004
11088511 425975 10551651 0 0 0 0 0 0 0 0 0 0% 0% 0% /proc /dev/fd
/etc/mnttab
06.30 March 10, 2010
Appendix V: Log captures for SCS Full Server Backup and Restore 833 12819106 66949 12623966 9853688 9853848 16 9853672 176 9853672 1% 1% 1% /var/run /tmp 5% /opt /var
/dev/md/dsk/d5 swap swap /dev/md/dsk/d8 /dev/md/dsk/d7
34065134 1451827 32272656 3008649 9 2948468 1%
/export/home
/vol/dev/dsk/c0t6d0/sol_8_204_sparc/s5 114 4 100 4% /cdrom/sol_8_204_sparc/s5
/vol/dev/dsk/c0t6d0/sol_8_204_sparc/s0 503232 503232 urc2y3pa# 0 100% /cdrom/sol_8_204_sparc/s0
End of full server restore (mirrored servers) log capture procedure
Full Server Restore for non-mirrored servers

1. Reboot server to single usermode urc2y3pa# sync;sync;sync urc2y3pa# init 0 urc2y3pa#
63
GPRS/UMTS
834
INIT: New run level: 0 The system is coming down. Please wait. System services are now being stopped. Print services stopped. Mar 29 00:55:48 urc2y3pa syslogd: going down on signal 15
nfs umount: urc2y3pa:vold(pid234) server not responding: RPC: Program not registered Mar 29 00:55:49 /usr/sbin/vold[1616]: problem unmounting /vol; Interrupted system call Mar 29 00:55:51 in.rdiscd[119]: terminated umount: /opt busy The system is down. syncing file systems... done Program terminated
2. From the ok prompt, reboot the server into single usermode. Enter the root password when prompted {2} ok boot cdrom -rs Resetting ... INIT: SINGLE USER MODE Type control-d to proceed with normal startup, (or give root password for system maintenance): root Login incorrect Type control-d to proceed with normal startup, (or give root password for system maintenance): single-user privilege assigned to /dev/console. Entering System Maintenance Mode
3. Extract backup from tape # cd / # tar xv x /tmp/backup, 0 bytes, 0 tape blocks x /tmp/backup/backup.log, 4090 bytes, 8 tape blocks x /tmp/backup/c0t0d0s2.vtoc, 838 bytes, 2 tape blocks
411-5221-309
Standard
06.30 March 10, 2010
x /tmp/backup/c0t1d0s2.vtoc, 480 bytes, 1 tape blocks x /tmp/backup/c0t2d0s2.vtoc, 533 bytes, 2 tape blocks x /tmp/backup/c0t3d0s2.vtoc, 552 bytes, 2 tape blocks x /tmp/backup/c0t9d0s2.vtoc, 533 bytes, 2 tape blocks x /tmp/backup/c0t10d0s2.vtoc, 534 bytes, 2 tape blocks x /tmp/backup/c0t11d0s2.vtoc, 544 bytes, 2 tape blocks x /tmp/backup/tools, 0 bytes, 0 tape blocks x /tmp/backup/tools/bin, 0 bytes, 0 tape blocks x /tmp/backup/tools/bin/ds_backup.ksh, 21040 bytes, 42 tape blocks x /tmp/backup/tools/bin/ds_exportEnv.awk, 177 bytes, 1 tape blocks x /tmp/backup/tools/bin/ds_restore.sh, 70601 bytes, 138 tape blocks x /tmp/backup/tools/bin/ds_scsbackup.ksh, 14057 bytes, 28 tape blocks x /tmp/backup/tools/bin/ds_scsrestore.sh, 29335 bytes, 58 tape blocks x /tmp/backup/tools/cfg, 0 bytes, 0 tape blocks x /tmp/backup/tools/cfg/ds_BR.env, 1703 bytes, 4 tape blocks x /tmp/backup/tools/etc, 0 bytes, 0 tape blocks x /tmp/backup/tools/etc/init.d, 0 bytes, 0 tape blocks x /tmp/backup/tools/etc/init.d/mirror, 520 bytes, 2 tape blocks x /tmp/backup/tools/etc/init.d/nxt-step, 861 bytes, 2 tape blocks x /tmp/backup/tools/lib, 0 bytes, 0 tape blocks x /tmp/backup/tools/lib/ds_brLib.lib, 13895 bytes, 28 tape blocks x /tmp/backup/tools/lib/ds_cmnLib.lib, 7118 bytes, 14 tape blocks x /tmp/backup/tools/lib/ds_logMgt.lib, 19593 bytes, 39 tape blocks x /tmp/backup/tools/lib/ds_system.lib, 33714 bytes, 66 tape blocks x /tmp/backup/tools/log, 0 bytes, 0 tape blocks x /tmp/backup/tools/tmp, 0 bytes, 0 tape blocks x /tmp/backup/vfstab, 591 bytes, 2 tape blocks x /tmp/backup/eeprom.cfg, 942 bytes, 2 tape blocks x /tmp/backup/hosts, 151 bytes, 1 tape blocks x /tmp/backup/catalogue.cfg, 262 bytes, 1 tape blocks x /tmp/backup/834f7fdd.hostid, 0 bytes, 0 tape blocks x /tmp/backup/SCS.label, 0 bytes, 0 tape blocks
# cd /tmp/backup/tools/bin
GPRS/UMTS
836
# ls ds_backup.ksh ds_restore.sh ds_scsrestore.sh
ds_exportEnv.awk ds_scsbackup.ksh
4. Execute Full Server Restore script # ./ds_restore.sh restore SCS server with no solaris volume manager configuration START| START| START| START| WARN |mkdir: "/usr/local/nortel": Operation not applicable START| ################################################################## WARN |mkdir: "/usr/local/nortel/tmp": Operation not applicable START| # NORTEL NETWORKS #
WARN |mkdir: "/usr/local/nortel/data/backup-": Operation not applicable START| #----------------------------------------------------------------# START| # STARTING : ./ds_scsrestore.sh START| # WITH : # # #
START| # LOG IN : /tmp/backup/tools/log/ds_scsrestore.log START| #----------------------------------------------------------------# START| # DATE | VERSION | UID | HOSTNAME
START| #----------------------------------------------------------------# START| # 12/27/05 15:11:06 | V03_01.E04 | 0 | #
START| ################################################################## START| INFO | $NORTEL_DIR has read-only access. INFO | $NORTEL_TMPDIR has read-only access. INFO | $NORTEL_BACKUPDIR has read-only access. INFO | INFO |PRELIMINARY TASKS INFO | =================
411-5221-309
Standard
06.30 March 10, 2010

INFO | INFO |
INFO |TTY = /dev/syscon INFO | INFO | INFO | Ok INFO | INFO | Checking the OS CD-ROM ... OS CD-ROM = Solaris 8 Checking run level (must be in single user mode) ...
INFO | Skip section on device /dev/rmt/0 INFO |fmthard: New volume table of contents now in place. INFO |fmthard: New volume table of contents now in place. INFO |fmthard: New volume table of contents now in place. INFO |fmthard: New volume table of contents now in place. INFO |fmthard: New volume table of contents now in place. INFO |fmthard: New volume table of contents now in place. INFO |fmthard: New volume table of contents now in place. INFO | Create all the file systems for SCS. INFO | --> device = /dev/dsk/c0t0d0s0 INFO | --> raw device= /dev/rdsk/c0t0d0s0 INFO | Create a new file system for /dev/rdsk/c0t0d0s0. WARN |/dev/rdsk/c0t0d0s0: 24 sectors WARN | 2052.1MB in 42 cyl groups (10 c/g, 49.69MB/g, 8064 i/g) WARN |super-block backups (for fsck -F ufs -o b=#) at: WARN | 32, 102224, 204416, 306608, 408800, 510992, 613184, 715376, 817568, 91976 0, WARN | 1021952, 1124144, 1226336, 1328528, 1430720, 1532912, 1635104, 1737296, WARN | 1839488, 1941680, 2043872, 2146064, 2248256, 2350448, 2452640, 2554832, WARN | 2657024, 2759216, 2861408, 2963600, 3065792, 3167984, 3256352, 3358544, WARN | 3460736, 3562928, 3665120, 3767312, 3869504, 3971696, 4073888, 4176080, INFO | --> device = /dev/dsk/c0t0d0s3 INFO | --> raw device= /dev/rdsk/c0t0d0s3 INFO | Create a new file system for /dev/rdsk/c0t0d0s3. WARN |/dev/rdsk/c0t0d0s3: 16780224 sectors in 1649 cylinders of 24 tracks, 4202688 sectors in 413 cylinders of 24 tracks, 4
GPRS/UMTS
838
424 sectors
WARN | 8193.5MB in 165 cyl groups (10 c/g, 49.69MB/g, 6016 i/g) WARN |super-block backups (for fsck -F ufs -o b=#) at: WARN | 32, 102224, 204416, 306608, 408800, 510992, 613184, 715376, 817568, 91976 0, WARN | 1021952, 1124144, 1226336, 1328528, 1430720, 1532912, 1635104, 1737296, WARN | 1839488, 1941680, 2043872, 2146064, 2248256, 2350448, 2452640, 2554832, WARN | 2657024, 2759216, 2861408, 2963600, 3065792, 3167984, 3256352, 3358544, WARN | 3460736, 3562928, 3665120, 3767312, 3869504, 3971696, 4073888, 4176080, WARN | 4278272, 4380464, 4482656, 4584848, 4687040, 4789232, 4891424, 4993616, WARN | 5095808, 5198000, 5300192, 5402384, 5504576, 5606768, 5708960, 5811152, WARN | 5913344, 6015536, 6117728, 6219920, 6322112, 6424304, 6512672, 6614864, WARN | 6717056, 6819248, 6921440, 7023632, 7125824, 7228016, 7330208, 7432400, WARN | 7534592, 7636784, 7738976, 7841168, 7943360, 8045552, 8147744, 8249936, WARN | 8352128, 8454320, 8556512, 8658704, 8760896, 8863088, 8965280, 9067472, WARN | 9169664, 9271856, 9374048, 9476240, 9578432, 9680624, 9768992, 9871184, WARN | 9973376, 10075568, 10177760, 10279952, 10382144, 10484336, 10586528, 1068 8720, WARN | 10790912, 10893104, 10995296, 11097488, 11199680, 11301872, 11404064, WARN | 11506256, 11608448, 11710640, 11812832, 11915024, 12017216, 12119408, WARN | 12221600, 12323792, 12425984, 12528176, 12630368, 12732560, 12834752, WARN | 12936944, 13025312, 13127504, 13229696, 13331888, 13434080, 13536272, WARN | 13638464, 13740656, 13842848, 13945040, 14047232, 14149424, 14251616, WARN | 14353808, 14456000, 14558192, 14660384, 14762576, 14864768, 14966960, WARN | 15069152, 15171344, 15273536, 15375728, 15477920, 15580112, 15682304, WARN | 15784496, 15886688, 15988880, 16091072, 16193264, 16281632, 16383824, WARN | 16486016, 16588208, 16690400, INFO | --> device = /dev/dsk/c0t0d0s6 INFO | --> raw device= /dev/rdsk/c0t0d0s6 INFO | Create a new file system for /dev/rdsk/c0t0d0s6. WARN |/dev/rdsk/c0t0d0s6: 424 sectors WARN | 6489.2MB in 131 cyl groups (10 c/g, 49.69MB/g, 6016 i/g) WARN |super-block backups (for fsck -F ufs -o b=#) at: 13289856 sectors in 1306 cylinders of 24 tracks,
411-5221-309
Standard
06.30 March 10, 2010
WARN | 32, 102224, 204416, 306608, 408800, 510992, 613184, 715376, 817568, 91976 0, WARN | 1021952, 1124144, 1226336, 1328528, 1430720, 1532912, 1635104, 1737296, WARN | 1839488, 1941680, 2043872, 2146064, 2248256, 2350448, 2452640, 2554832, WARN | 2657024, 2759216, 2861408, 2963600, 3065792, 3167984, 3256352, 3358544, WARN | 3460736, 3562928, 3665120, 3767312, 3869504, 3971696, 4073888, 4176080, WARN | 4278272, 4380464, 4482656, 4584848, 4687040, 4789232, 4891424, 4993616, WARN | 5095808, 5198000, 5300192, 5402384, 5504576, 5606768, 5708960, 5811152, WARN | 5913344, 6015536, 6117728, 6219920, 6322112, 6424304, 6512672, 6614864, WARN | 6717056, 6819248, 6921440, 7023632, 7125824, 7228016, 7330208, 7432400, WARN | 7534592, 7636784, 7738976, 7841168, 7943360, 8045552, 8147744, 8249936, WARN | 8352128, 8454320, 8556512, 8658704, 8760896, 8863088, 8965280, 9067472, WARN | 9169664, 9271856, 9374048, 9476240, 9578432, 9680624, 9768992, 9871184, WARN | 9973376, 10075568, 10177760, 10279952, 10382144, 10484336, 10586528, 1068 8720, WARN | 10790912, 10893104, 10995296, 11097488, 11199680, 11301872, 11404064, WARN | 11506256, 11608448, 11710640, 11812832, 11915024, 12017216, 12119408, WARN | 12221600, 12323792, 12425984, 12528176, 12630368, 12732560, 12834752, WARN | 12936944, 13025312, 13127504, 13229696, INFO | --> device = /dev/dsk/c0t0d0s4 INFO | --> raw device= /dev/rdsk/c0t0d0s4 INFO | Create a new file system for /dev/rdsk/c0t0d0s4. WARN |/dev/rdsk/c0t0d0s4: 424 sectors WARN | 8193.5MB in 165 cyl groups (10 c/g, 49.69MB/g, 6016 i/g) WARN |super-block backups (for fsck -F ufs -o b=#) at: WARN | 32, 102224, 204416, 306608, 408800, 510992, 613184, 715376, 817568, 91976 0, WARN | 1021952, 1124144, 1226336, 1328528, 1430720, 1532912, 1635104, 1737296, WARN | 1839488, 1941680, 2043872, 2146064, 2248256, 2350448, 2452640, 2554832, WARN | 2657024, 2759216, 2861408, 2963600, 3065792, 3167984, 3256352, 3358544, WARN | 3460736, 3562928, 3665120, 3767312, 3869504, 3971696, 4073888, 4176080, WARN | 4278272, 4380464, 4482656, 4584848, 4687040, 4789232, 4891424, 4993616, WARN | 5095808, 5198000, 5300192, 5402384, 5504576, 5606768, 5708960, 5811152, 16780224 sectors in 1649 cylinders of 24 tracks,
GPRS/UMTS
840
WARN | 5913344, 6015536, 6117728, 6219920, 6322112, 6424304, 6512672, 6614864, WARN | 6717056, 6819248, 6921440, 7023632, 7125824, 7228016, 7330208, 7432400, WARN | 7534592, 7636784, 7738976, 7841168, 7943360, 8045552, 8147744, 8249936, WARN | 8352128, 8454320, 8556512, 8658704, 8760896, 8863088, 8965280, 9067472, WARN | 9169664, 9271856, 9374048, 9476240, 9578432, 9680624, 9768992, 9871184, WARN | 9973376, 10075568, 10177760, 10279952, 10382144, 10484336, 10586528, 1068 8720, WARN | 10790912, 10893104, 10995296, 11097488, 11199680, 11301872, 11404064, WARN | 11506256, 11608448, 11710640, 11812832, 11915024, 12017216, 12119408, WARN | 12221600, 12323792, 12425984, 12528176, 12630368, 12732560, 12834752, WARN | 12936944, 13025312, 13127504, 13229696, 13331888, 13434080, 13536272, WARN | 13638464, 13740656, 13842848, 13945040, 14047232, 14149424, 14251616, WARN | 14353808, 14456000, 14558192, 14660384, 14762576, 14864768, 14966960, WARN | 15069152, 15171344, 15273536, 15375728, 15477920, 15580112, 15682304, WARN | 15784496, 15886688, 15988880, 16091072, 16193264, 16281632, 16383824, WARN | 16486016, 16588208, 16690400, INFO | --> device = /dev/dsk/c0t0d0s5 INFO | --> raw device= /dev/rdsk/c0t0d0s5 INFO | Create a new file system for /dev/rdsk/c0t0d0s5. WARN |/dev/rdsk/c0t0d0s5: 424 sectors WARN | 28674.7MB in 578 cyl groups (10 c/g, 49.69MB/g, 6016 i/g) WARN |super-block backups (for fsck -F ufs -o b=#) at: WARN | 32, 102224, 204416, 306608, 408800, 510992, 613184, 715376, 817568, 91976 0, WARN | 1021952, 1124144, 1226336, 1328528, 1430720, 1532912, 1635104, 1737296, WARN | 1839488, 1941680, 2043872, 2146064, 2248256, 2350448, 2452640, 2554832, WARN | 2657024, 2759216, 2861408, 2963600, 3065792, 3167984, 3256352, 3358544, WARN | 3460736, 3562928, 3665120, 3767312, 3869504, 3971696, 4073888, 4176080, WARN | 4278272, 4380464, 4482656, 4584848, 4687040, 4789232, 4891424, 4993616, WARN | 5095808, 5198000, 5300192, 5402384, 5504576, 5606768, 5708960, 5811152, WARN | 5913344, 6015536, 6117728, 6219920, 6322112, 6424304, 6512672, 6614864, WARN | 6717056, 6819248, 6921440, 7023632, 7125824, 7228016, 7330208, 7432400, WARN | 7534592, 7636784, 7738976, 7841168, 7943360, 8045552, 8147744, 8249936, 58725696 sectors in 5771 cylinders of 24 tracks,
411-5221-309
Standard
06.30 March 10, 2010
WARN | 8352128, 8454320, 8556512, 8658704, 8760896, 8863088, 8965280, 9067472, WARN | 9169664, 9271856, 9374048, 9476240, 9578432, 9680624, 9768992, 9871184, WARN | 9973376, 10075568, 10177760, 10279952, 10382144, 10484336, 10586528, 1068 8720, WARN | 10790912, 10893104, 10995296, 11097488, 11199680, 11301872, 11404064, WARN | 11506256, 11608448, 11710640, 11812832, 11915024, 12017216, 12119408, WARN | 12221600, 12323792, 12425984, 12528176, 12630368, 12732560, 12834752, WARN | 12936944, 13025312, 13127504, 13229696, 13331888, 13434080, 13536272, WARN | 13638464, 13740656, 13842848, 13945040, 14047232, 14149424, 14251616, WARN | 14353808, 14456000, 14558192, 14660384, 14762576, 14864768, 14966960, WARN | 15069152, 15171344, 15273536, 15375728, 15477920, 15580112, 15682304, WARN | 15784496, 15886688, 15988880, 16091072, 16193264, 16281632, 16383824, WARN | 16486016, 16588208, 16690400, 16792592, 16894784, 16996976, 17099168, WARN | 17201360, 17303552, 17405744, 17507936, 17610128, 17712320, 17814512, WARN | 17916704, 18018896, 18121088, 18223280, 18325472, 18427664, 18529856, WARN | 18632048, 18734240, 18836432, 18938624, 19040816, 19143008, 19245200, WARN | 19347392, 19449584, 19537952, 19640144, 19742336, 19844528, 19946720, WARN | 20048912, 20151104, 20253296, 20355488, 20457680, 20559872, 20662064, WARN | 20764256, 20866448, 20968640, 21070832, 21173024, 21275216, 21377408, WARN | 21479600, 21581792, 21683984, 21786176, 21888368, 21990560, 22092752, WARN | 22194944, 22297136, 22399328, 22501520, 22603712, 22705904, 22794272, WARN | 22896464, 22998656, 23100848, 23203040, 23305232, 23407424, 23509616, WARN | 23611808, 23714000, 23816192, 23918384, 24020576, 24122768, 24224960, WARN | 24327152, 24429344, 24531536, 24633728, 24735920, 24838112, 24940304, WARN | 25042496, 25144688, 25246880, 25349072, 25451264, 25553456, 25655648, WARN | 25757840, 25860032, 25962224, 26050592, 26152784, 26254976, 26357168, WARN | 26459360, 26561552, 26663744, 26765936, 26868128, 26970320, 27072512, WARN | 27174704, 27276896, 27379088, 27481280, 27583472, 27685664, 27787856, WARN | 27890048, 27992240, 28094432, 28196624, 28298816, 28401008, 28503200, WARN | 28605392, 28707584, 28809776, 28911968, 29014160, 29116352, 29218544, WARN | 29306912, 29409104, 29511296, 29613488, 29715680, 29817872, 29920064, WARN | 30022256, 30124448, 30226640, 30328832, 30431024, 30533216, 30635408, WARN | 30737600, 30839792, 30941984, 31044176, 31146368, 31248560, 31350752, WARN | 31452944, 31555136, 31657328, 31759520, 31861712, 31963904, 32066096,
GPRS/UMTS
842
WARN | 32168288, 32270480, 32372672, 32474864, 32563232, 32665424, 32767616, WARN | 32869808, 32972000, 33074192, 33176384, 33278576, 33380768, 33482960, WARN | 33585152, 33687344, 33789536, 33891728, 33993920, 34096112, 34198304, WARN | 34300496, 34402688, 34504880, 34607072, 34709264, 34811456, 34913648, WARN | 35015840, 35118032, 35220224, 35322416, 35424608, 35526800, 35628992, WARN | 35731184, 35819552, 35921744, 36023936, 36126128, 36228320, 36330512, WARN | 36432704, 36534896, 36637088, 36739280, 36841472, 36943664, 37045856, WARN | 37148048, 37250240, 37352432, 37454624, 37556816, 37659008, 37761200, WARN | 37863392, 37965584, 38067776, 38169968, 38272160, 38374352, 38476544, WARN | 38578736, 38680928, 38783120, 38885312, 38987504, 39075872, 39178064, WARN | 39280256, 39382448, 39484640, 39586832, 39689024, 39791216, 39893408, WARN | 39995600, 40097792, 40199984, 40302176, 40404368, 40506560, 40608752, WARN | 40710944, 40813136, 40915328, 41017520, 41119712, 41221904, 41324096, WARN | 41426288, 41528480, 41630672, 41732864, 41835056, 41937248, 42039440, WARN | 42141632, 42243824, 42332192, 42434384, 42536576, 42638768, 42740960, WARN | 42843152, 42945344, 43047536, 43149728, 43251920, 43354112, 43456304, WARN | 43558496, 43660688, 43762880, 43865072, 43967264, 44069456, 44171648, WARN | 44273840, 44376032, 44478224, 44580416, 44682608, 44784800, 44886992, WARN | 44989184, 45091376, 45193568, 45295760, 45397952, 45500144, 45588512, WARN | 45690704, 45792896, 45895088, 45997280, 46099472, 46201664, 46303856, WARN | 46406048, 46508240, 46610432, 46712624, 46814816, 46917008, 47019200, WARN | 47121392, 47223584, 47325776, 47427968, 47530160, 47632352, 47734544, WARN | 47836736, 47938928, 48041120, 48143312, 48245504, 48347696, 48449888, WARN | 48552080, 48654272, 48756464, 48844832, 48947024, 49049216, 49151408, WARN | 49253600, 49355792, 49457984, 49560176, 49662368, 49764560, 49866752, WARN | 49968944, 50071136, 50173328, 50275520, 50377712, 50479904, 50582096, WARN | 50684288, 50786480, 50888672, 50990864, 51093056, 51195248, 51297440, WARN | 51399632, 51501824, 51604016, 51706208, 51808400, 51910592, 52012784, WARN | 52101152, 52203344, 52305536, 52407728, 52509920, 52612112, 52714304, WARN | 52816496, 52918688, 53020880, 53123072, 53225264, 53327456, 53429648, WARN | 53531840, 53634032, 53736224, 53838416, 53940608, 54042800, 54144992, WARN | 54247184, 54349376, 54451568, 54553760, 54655952, 54758144, 54860336, WARN | 54962528, 55064720, 55166912, 55269104, 55357472, 55459664, 55561856, WARN | 55664048, 55766240, 55868432, 55970624, 56072816, 56175008, 56277200,
411-5221-309
Standard
06.30 March 10, 2010
WARN | 56379392, 56481584, 56583776, 56685968, 56788160, 56890352, 56992544, WARN | 57094736, 57196928, 57299120, 57401312, 57503504, 57605696, 57707888, WARN | 57810080, 57912272, 58014464, 58116656, 58218848, 58321040, 58423232, WARN | 58525424, 58613792, 58715984, INFO | --> device = /dev/dsk/c0t11d0s0 INFO | --> raw device= /dev/rdsk/c0t11d0s0 INFO | Create a new file system for /dev/rdsk/c0t11d0s0. WARN |/dev/rdsk/c0t11d0s0: s, 424 sectors WARN | 69989.8MB in 1409 cyl groups (10 c/g, 49.69MB/g, 6016 i/g) WARN |super-block backups (for fsck -F ufs -o b=#) at: WARN | 32, 102224, 204416, 306608, 408800, 510992, 613184, 715376, 817568, 91976 0, WARN | 1021952, 1124144, 1226336, 1328528, 1430720, 1532912, 1635104, 1737296, WARN | 1839488, 1941680, 2043872, 2146064, 2248256, 2350448, 2452640, 2554832, WARN | 2657024, 2759216, 2861408, 2963600, 3065792, 3167984, 3256352, 3358544, WARN | 3460736, 3562928, 3665120, 3767312, 3869504, 3971696, 4073888, 4176080, WARN | 4278272, 4380464, 4482656, 4584848, 4687040, 4789232, 4891424, 4993616, WARN | 5095808, 5198000, 5300192, 5402384, 5504576, 5606768, 5708960, 5811152, WARN | 5913344, 6015536, 6117728, 6219920, 6322112, 6424304, 6512672, 6614864, WARN | 6717056, 6819248, 6921440, 7023632, 7125824, 7228016, 7330208, 7432400, WARN | 7534592, 7636784, 7738976, 7841168, 7943360, 8045552, 8147744, 8249936, WARN | 8352128, 8454320, 8556512, 8658704, 8760896, 8863088, 8965280, 9067472, WARN | 9169664, 9271856, 9374048, 9476240, 9578432, 9680624, 9768992, 9871184, WARN | 9973376, 10075568, 10177760, 10279952, 10382144, 10484336, 10586528, 1068 8720, WARN | 10790912, 10893104, 10995296, 11097488, 11199680, 11301872, 11404064, WARN | 11506256, 11608448, 11710640, 11812832, 11915024, 12017216, 12119408, WARN | 12221600, 12323792, 12425984, 12528176, 12630368, 12732560, 12834752, WARN | 12936944, 13025312, 13127504, 13229696, 13331888, 13434080, 13536272, WARN | 13638464, 13740656, 13842848, 13945040, 14047232, 14149424, 14251616, WARN | 14353808, 14456000, 14558192, 14660384, 14762576, 14864768, 14966960, WARN | 15069152, 15171344, 15273536, 15375728, 15477920, 15580112, 15682304, WARN | 15784496, 15886688, 15988880, 16091072, 16193264, 16281632, 16383824, 143339136 sectors in 14086 cylinders of 24 track
GPRS/UMTS
844
411-5221-309
Standard
06.30 March 10, 2010
GPRS/UMTS
846
411-5221-309
Standard
06.30 March 10, 2010
WARN | 89146976, 89249168, 89351360, 89453552, 89555744, 89657936, 89760128, WARN | 89862320, 89964512, 90066704, 90168896, 90271088, 90373280, 90475472, WARN | 90577664, 90679856, 90782048, 90884240, 90986432, 91088624, 91176992, WARN | 91279184, 91381376, 91483568, 91585760, 91687952, 91790144, 91892336, WARN | 91994528, 92096720, 92198912, 92301104, 92403296, 92505488, 92607680, WARN | 92709872, 92812064, 92914256, 93016448, 93118640, 93220832, 93323024, WARN | 93425216, 93527408, 93629600, 93731792, 93833984, 93936176, 94038368, WARN | 94140560, 94242752, 94344944, 94433312, 94535504, 94637696, 94739888, WARN | 94842080, 94944272, 95046464, 95148656, 95250848, 95353040, 95455232, WARN | 95557424, 95659616, 95761808, 95864000, 95966192, 96068384, 96170576, WARN | 96272768, 96374960, 96477152, 96579344, 96681536, 96783728, 96885920, WARN | 96988112, 97090304, 97192496, 97294688, 97396880, 97499072, 97601264, WARN | 97689632, 97791824, 97894016, 97996208, 98098400, 98200592, 98302784, WARN | 98404976, 98507168, 98609360, 98711552, 98813744, 98915936, 99018128, WARN | 99120320, 99222512, 99324704, 99426896, 99529088, 99631280, 99733472, WARN | 99835664, 99937856, 100040048, 100142240, 100244432, 100346624, 100448816 , WARN | 100551008, 100653200, 100755392, 100857584, 100945952, 101048144, 1011503 36, WARN | 101252528, 101354720, 101456912, 101559104, 101661296, 101763488, 1018656 80, WARN | 101967872, 102070064, 102172256, 102274448, 102376640, 102478832, 1025810 24, WARN | 102683216, 102785408, 102887600, 102989792, 103091984, 103194176, 1032963 68, WARN | 103398560, 103500752, 103602944, 103705136, 103807328, 103909520, 1040117 12, WARN | 104113904, 104202272, 104304464, 104406656, 104508848, 104611040, 1047132 32, WARN | 104815424, 104917616, 105019808, 105122000, 105224192, 105326384, 1054285 76, WARN | 105530768, 105632960, 105735152, 105837344, 105939536, 106041728, 1061439 20, WARN | 106246112, 106348304, 106450496, 106552688, 106654880, 106757072, 1068592
GPRS/UMTS
848
64,
WARN | 106961456, 107063648, 107165840, 107268032, 107370224, 107458592, 1075607 84, WARN | 107662976, 107765168, 107867360, 107969552, 108071744, 108173936, 1082761 28, WARN | 108378320, 108480512, 108582704, 108684896, 108787088, 108889280, 1089914 72, WARN | 109093664, 109195856, 109298048, 109400240, 109502432, 109604624, 1097068 16, WARN | 109809008, 109911200, 110013392, 110115584, 110217776, 110319968, 1104221 60, WARN | 110524352, 110626544, 110714912, 110817104, 110919296, 111021488, 1111236 80, WARN | 111225872, 111328064, 111430256, 111532448, 111634640, 111736832, 1118390 24, WARN | 111941216, 112043408, 112145600, 112247792, 112349984, 112452176, 1125543 68, WARN | 112656560, 112758752, 112860944, 112963136, 113065328, 113167520, 1132697 12, WARN | 113371904, 113474096, 113576288, 113678480, 113780672, 113882864, 1139712 32, WARN | 114073424, 114175616, 114277808, 114380000, 114482192, 114584384, 1146865 76, WARN | 114788768, 114890960, 114993152, 115095344, 115197536, 115299728, 1154019 20, WARN | 115504112, 115606304, 115708496, 115810688, 115912880, 116015072, 1161172 64, WARN | 116219456, 116321648, 116423840, 116526032, 116628224, 116730416, 1168326 08, WARN | 116934800, 117036992, 117139184, 117227552, 117329744, 117431936, 1175341 28, WARN | 117636320, 117738512, 117840704, 117942896, 118045088, 118147280, 1182494 72, WARN | 118351664, 118453856, 118556048, 118658240, 118760432, 118862624, 1189648
411-5221-309
Standard
06.30 March 10, 2010

16,
GPRS/UMTS
850
68,
411-5221-309
Standard
06.30 March 10, 2010

44,
WARN | 143278112, INFO | Restoring / (/dev/dsk/c0t0d0s0) at 15:19:47
WARN |Warning: ./lost+found: File exists
INFO | Ok INFO | Restoring /var (/dev/dsk/c0t0d0s3) at 15:37:57
WARN |Warning: ./lost+found: File exists INFO | Ok INFO | Restoring /home (/dev/dsk/c0t0d0s6) at 16:01:17
WARN |Warning: ./lost+found: File exists INFO | Ok INFO | Restoring /opt (/dev/dsk/c0t0d0s4) at 16:36:44
WARN |Warning: ./lost+found: File exists INFO | Ok INFO | Restoring /opt/nortel (/dev/dsk/c0t0d0s5) at 17:21:45
WARN |Warning: ./lost+found: File exists INFO | Ok INFO | Restoring /newmnt (/dev/dsk/c0t11d0s0) at 17:50:07
WARN |Warning: ./lost+found: File exists INFO | Ok INFO | #### FS_LIST = / INFO |/var INFO |/home INFO |/opt INFO |/opt/nortel INFO |/newmnt INFO | Mount all file systems for SCS. INFO | Mount / on device /mnt/dev/dsk/c0t0d0s0. INFO | Mount /var on device /mnt/dev/dsk/c0t0d0s3. INFO | Mount /home on device /mnt/dev/dsk/c0t0d0s6. INFO | Mount /opt on device /mnt/dev/dsk/c0t0d0s4. INFO | Mount /opt/nortel on device /mnt/dev/dsk/c0t0d0s5. INFO | Mount /newmnt on device /mnt/dev/dsk/c0t11d0s0.
GPRS/UMTS
852
INFO | INFO | Ok INFO | Server platform = SUNW,Sun-Fire-V250 INFO | NEW BOOTDEV = disk:a disk6:a INFO | Set Autoboot true END | END | END | END | END | Installing boot strap on /dev/rdsk/c0t0d0s0 ...
END | ################################################################## END | # END OF : END | # WITH # #
: /tmp/backup/tools/log/ds_scsrestore.log
END | #----------------------------------------------------------------# END | # STATUS : ds_scsrestore.sh # # #
END | # LOG IN : /tmp/backup/tools/log/ds_scsrestore.log END | # END DATE : 12/27/05 17:50:18
END | ################################################################## END | # NORTEL NETWORKS #
END | ################################################################## INFO | *** PLEASE, REBOOT NOW... END | END | # # END | END | END | END | ################################################################## END | # END OF : ds_scsrestore.sh END | # WITH : # #
END | #----------------------------------------------------------------# END | # STATUS : 0 # # #
END | # LOG IN : /tmp/backup/tools/log/ds_scsrestore.log END | # END DATE : 12/27/05 17:50:20
END | ##################################################################
411-5221-309
Standard
06.30 March 10, 2010

END | #
NORTEL NETWORKS #
END | ##################################################################
Reboot server # init 6
End of Full server restore capture for non-mirrored server
GPRS/UMTS
854
411-5221-309
Standard
06.30 March 10, 2010

411-5221-309 v6 30

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

411-5221-309 v6 30

Caricato da

Copyright:

Formati disponibili

411-5221-309

Nortel GGSN and SCS

Nortel GGSN and SCS

Copyright1 Country of printing2 Confidentiality3 Legal statements4 Trademarks5

Nortel Networks Confidential

06.30 March 10, 2010

Nortel Networks Confidential

Upgrade Manual GGSN6.0

Nortel Networks Confidential

06.30 March 10, 2010

Nortel Networks Confidential

Upgrade Manual GGSN6.0

Nortel Networks Confidential

06.30 March 10, 2010

Nortel Networks Confidential

Upgrade Manual GGSN6.0

Nortel Networks Confidential

06.30 March 10, 2010

Nortel Networks Confidential

Upgrade Manual GGSN6.0

Nortel Networks Confidential

06.30 March 10, 2010

Nortel Networks Confidential

Nortel Networks Confidential

06.30 March 10, 2010

Nortel Networks Confidential

Upgrade Manual GGSN6.0

Nortel Networks Confidential

Nortel Networks Confidential

About this document

GGSN 6.0 Upgrade Overview and New Install Overview

GGSN/SCS pre upgrade checklists

SCS Upgrade Overview

SCS server preparation: Migration of the current SCS to new

Nortel Networks Confidential

hardware or New Install of SCS on new hardware

SCS Upgrade Prechecks

SCS Upgrade on the Same Physical Server

Basic SCS system administration

06.30 March 10, 2010

Nortel Networks Confidential

Database backup and restore procedures

SCS Software Upgrade

Nortel Networks Confidential

Modify partition level file permissions SCS Post-upgrade / Rollback checklists

Procedure for Changing the SCS server IP address

OS Hardening of GGSN SCS Server

OS unhardening procedure on Solaris 8 SCS Client upgrade procedures

OS hardening of SCS client machines

361 362 372

06.30 March 10, 2010

Nortel Networks Confidential

Full System backup and restore

Solaris 9 Boot Environment Creation

Deleting the Boot Environment

Nortel Networks Confidential

Copy the upgraded SCS 6.0 from Solaris 8 to Solaris 9

Install Recommended Patches for Solaris 9 and Solaris 10

GGSN Software Upgrade GGSN Pre-Upgrade Procedure

GGSN Upgrade Procedure

GGSN Post-Upgrade Procedure

Optional Post-Upgrade Procedures