umts, gprs nortel wireless network management...

411-5221-305

UMTS, GPRS

Nortel Wireless Network Management SystemAdministrator GuideOAM 4.2 Standard 04.10 December 2005

What’s inside...

About this documentAbout W-NMSFault management and configuration managementAlarm on thresholdPerformance managementSecurity administrationTools and utilitiesWireless Network Management System usersAppendix A: SNMP and Multiservice Switch-based network element

proceduresAppendix B: Filtering alarmsAppendix C: Patching W-NMS

UMTS, GPRS

Nortel Wireless Network Management SystemAdministrator Guide

Document number: 411-5221-305Product release: OAM 4.2Document version: Standard 04.10 Date: December 2005

Copyright Country of printing Confidentiality Legal statements Trademarks

Copyright © 2002–2005 Nortel Networks, All Rights Reserved

Originated in North America/Canada

NORTEL NETWORKS 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.

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

* Nortel Networks, the Nortel Networks logo, the Globemark, and Unified Networks are trademarks of Nortel Networks. Citrix and MetaFrame are trademarks of Citrix Systems, Inc. in the United States. Exceed is a trademark of Hummingbird Communications Ltd. Mycom and NIMS-PrOptima are trademarks of Mycom International. Solaris is a trademark of Sun Microsystems Inc. Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.

ii Nortel Networks Confidential

411-5221-305 Standard 04.10 December 2005

Nortel Networks Confidential iii

Publication historyDecember 2005

OAM 4.2—Standard, Issue 04.10.

October 2005

OAM 4.2—Standard, Issue 04.09.

September 2005

OAM 4.2—Preliminary, Issue 04.08.

July 2005


April 2005


March 2005


March 2005

OAM 4.2—Draft, Issue 04.04.

February 2005


February 2005


December 2004


UMTS, GPRS W-NMS Administrator Guide OAM 4.2

iv Publication history Nortel Networks Confidential

October 2003

Standard 1.16 release - point release for Server Of Clients feature. Procedures for configuring explicit user on the Server of Clients added to “Preside for Wireless Internet Users”

October 2003

Standard 1.15 release:

August 2003


June 2003



Nortel Networks Confidential v

Contents 1

About this document xi

About this document ixAudience for this document ixOrganization of this document ixRelated documents xRoad map to the W-NMS documentation xSpecial text conventions in this document xiiIndication of hypertext links xii

About W-NMS 1Network Services Platform 1Process management 1SNMP-managed devices for fault management 1About network element releases 1About the procedures in this document 1

Fault management and configuration management 3Requirements 3Applications Switch 5Audio Provisioning Server 8Border Gateway 11Business Policy Switch 2000 14Data Server 16Ethernet Switch 450 21Funk Steel-Belted Radius 24GGSN 32HLR 100, HLR 200, MSC, combined MSC/HLR, or Signaling Gateway 35IP Services Edge Router 5500 48LIG-D Comverse 51MetaSolv Network Mediation 54MetaSolv Policy Services DNS/DHCP 58Mobile Location Center 62Multiservice Switch 7400, 15000, 20000, AN, MGW, IWF 65Net Guardian 67Ethernet Routing Switch 8600 70Service Location Register 74


vi Contents Nortel Networks Confidential

SGSN/UMTS, SGSN/GPRS 75Signalling Gateway 76SS7 IP Gateway 77Universal Number Portability Master 83USP-based Universal Number Portability Master 87VPN Router 91Web Switch 184 92

94

Alarm on threshold 95Configuring alarm on threshold 96

Performance management 105Verifying the performance server processes 105Multiservice Switch-based network elements 107SGSN debug statistics 117GGSN 124Verifying the granularity period for the performance data files 130SS7 IP Gateway 131Voice core network elements 137Verifying that the performance data has been processed 141Disabling data collection 142The Performance Application Manager 147

Security administration 155OS hardening 156The OS hardening log files 157Hardening the OS 157Unhardening the OS 159Verifying the current OS hardening package 162Optional OS hardening features 163Activating or deactivating an optional OS hardening feature 164The audit trail 165Scope of the audit trail 166The audit log files 168Accessing the audit trail configuration menu 170Enabling the audit trail 174Disabling the audit trail 176OpenSSH 178Verifying that the OpenSSH server is running 179Stopping or starting the OpenSSH server 180Access control 180Account password management 187Default passwords 187Changing account passwords 190Changing hardware passwords 230Encrypting clear text passwords 237

Tools and utilities 241Performance management administration 241


Nortel Networks Confidential Contents vii

The log files 244Configuring NetRx 251CLI*manager 252GGSN command line user interface 255Import and export of configuration management XML files 261The Wireless Provisioning System for core network 264Removing a server from the Orbix Trader 265

Wireless Network Management System users 267Default shell for the root and nortel user Ids 267sdmuser user ID 267admin user ID 267Add, delete and modify users 268Configuring a user on the server of clients 268Configuring NIMS-PrOptima for W-NMS on the server of clients 271Configuring the SRS on the server of clients 273

Appendix A: SNMP and Multiservice Switch-based network element procedures 277Discovering an SNMP network element 277Configuring a Multiservice Switch 285

Appendix B: Filtering alarms 297Core DA alarm filtering 297

Appendix C: Patching W-NMS 307Obtaining a patch 307Downloading a patch 307Installing a patch on the SRS 309Applying a patch 310

Index 311

FiguresFigure 1 PAM main window 150

TablesTable 1 SGW configurations 76Table 2 GGSN accounting elements 125Table 3 Untitled 133Table 4 Untitled 138Table 5 Untitled 141Table 6 Menu bar 148Table 7 Display modes 149Table 8 Job Browser tabs 149Table 9 Security administration procedures 155Table 10 Optional feature scripts 164Table 11 Optional features applicable servers 164Table 12 Level 1 auditing 166


viii Contents Nortel Networks Confidential

Table 13 Level 2 auditing 167Table 14 Level 3 auditing 168Table 15 Events sent to CSAL 168Table 16 Parameter definitions 169Table 17 Supported OpenSSH commands 178Table 18 Local session launch resources 181Table 19 Remote session launch resources 183Table 20 UNIX accounts 187Table 21 NDS accounts 189Table 22 W-NMS application accounts 189Table 23 MDM accounts 223Table 24 Hardware accounts 231Table 25 Untitled 244Table 26 Log levels for the PDI, SDI, CDI 245Table 27 Log levels for the ADC, GDI, and SGSN Debug 245Table 28 Untitled 260Table 29 Untitled 297

ProceduresProcedure 1 Configuring the Applications Switch 5Procedure 2 Generating an alarm on the Applications Switch 7Procedure 3 Configuring the APS 8Procedure 4 Configuring the Border Gateway 11Procedure 5 Generating an alarm on the Border Gateway 13Procedure 6 Configuring the BPS 2000 14Procedure 7 Configuring the Data Server 16Procedure 8 Enroll the Data Server on the main server 18Procedure 9 Verify the Data Server 19Procedure 10 Deleting the Data Server 20Procedure 11 Configuring the Ethernet Switch 450 22Procedure 12 Configuring the Funk SBR 3.0 SPE or 4.6 SPE 24Procedure 13 Configuring the Funk SBR 4.7.8 SPE 28Procedure 14 Enable rsh and rexec 30Procedure 15 Configuring GGSN SNMP agent 33Procedure 16 Configuring OMC-S security on the SDM 36Procedure 17 Method 1: Deleting OM files by retention period 39Procedure 18 Method 2: Deleting OM files by date 40Procedure 19 Migrate an SDM from stand-alone mode to server-based mode 41Procedure 20 Generating an alarm for an MSC, HLR 100, HLR 200, combined

MSC/HLR, or Signaling Gateway 45Procedure 21 Recover from failed migration attempt 46Procedure 22 Remove an SDM in server-based mode 47Procedure 23 Configuring IP Services Edge Router 5500 SNMP agent 48Procedure 24 Configuring the LIG-D Comverse 52Procedure 25 Generating an alarm on the LIG-D Comverse 53Procedure 26 Configuring the MetaSolv Network Mediation server 54Procedure 27 Generating an alarm on a Network Mediation server 56Procedure 28 Configuring SNMP for Policy Services 58Procedure 29 Generating an alarm on a Policy Services server 61Procedure 30 Configuring the MLC 62


Nortel Networks Confidential Contents ix

Procedure 31 Generating an alarm on the MLC 64Procedure 32 Configuring the Net Guardian 67Procedure 33 Generating an alarm on the Net Guardian 68Procedure 34 Configuring the Ethernet Routing Switch 8600 70Procedure 35 Generating an alarm on the Ethernet Routing Switch 8600 72Procedure 36 Configuring the SIG 4.0 77Procedure 37 Configuring the SIG 5.0, 6.0 79Procedure 38 Generating an alarm on the SIG 81Procedure 39 Configuring the UNPM SNMP agent 83Procedure 40 Discover the UNPM 84Procedure 41 Generating an alarm on the UNPM 85Procedure 42 Configuring the USP-based UNPM 87Procedure 43 Adding the USP-based UNPM to a network layout 89Procedure 44 Deleting the USP-based UNPM 90Procedure 45 Configuring the Web Switch 184 92Procedure 46 Connecting the performance server to the main server 96Procedure 47 Configuring the MDP for an existing network element 99Procedure 48 Configuring the ADC 101Procedure 49 Configuring the threshold alarm rate 102Procedure 50 Verifying the performance server processes 105Procedure 51 Configuring a Multiservice Switch-based network element 107Procedure 52 Importing the HGDS configuration file 110Procedure 53 Configuring the MDP 111Procedure 54 Optimizing the File Prober Manager 114Procedure 55 Increasing MNMPDI memory 116Procedure 56 Adding the SGSN to the MDM host 117Procedure 57 Configuring the MDP for SGSN debug statistics 118Procedure 58 Creating the configuration files 122Procedure 59 Verifying SGSN debug statistics collection 123Procedure 60 Configuring the GGSN 126Procedure 61 Configuring the Log Server and the Pull Server 128Procedure 62 Verifying the granularity period for the performance data files 130Procedure 63 Configuring the SIG 131Procedure 64 Configuring the ADC 134Procedure 65 Accessing the ADC configuration tool from the Network Services

Platform 136Procedure 66 Enabling data collection for a voice core network element 138Procedure 67 Verifying that the performance data has been processed 141Procedure 68 Disabling data collection for Multiservice Switch-based network

elements 142Procedure 69 Disconnecting a network element from the ADC 145Procedure 70 Disabling data collection for a voice core network element 146Procedure 71 Opening the PAM main window 150Procedure 72 Configuring a profile 151Procedure 73 Configuring a job for a profile 152Procedure 74 Modifying a profile 153Procedure 75 Deleting a profile 154Procedure 76 Hardening the OS 157Procedure 77 Unhardening the OS 160Procedure 78 Verifying the current OS hardening package 162Procedure 79 Activating or deactivating an optional OS hardening feature 165


x Contents Nortel Networks Confidential

Procedure 80 Accessing the audit trail configuration menu 170Procedure 81 Enabling the audit trail 174Procedure 82 Disabling the audit trail 176Procedure 83 Verifying that the OpenSSH server is running 179Procedure 84 Stopping or starting the OpenSSH server 180Procedure 85 Changing the password for a UNIX account 191Procedure 86 Changing the password for an NDS account 192Procedure 87 Changing the password for admin 193Procedure 88 Changing the password for bkp_usr 195Procedure 89 Changing the password for cemftp 196Procedure 90 Changing the password for dfsnortel 198Procedure 91 Changing the password for dfsnortel on each W-NMS server 199Procedure 92 Changing the password for hfbguest in Oracle 202Procedure 93 Updating alarmDataExtract.cfg 203Procedure 94 Changing the password for PPXfer 205Procedure 95 Changing the password for SMCAdmin or SMCUser 207Procedure 96 Changing the password for SMCneop 209Procedure 97 Changing the password for a data collector 211Procedure 98 Changing the password for administrator for install/upgrade 213Procedure 99 Changing the password for anontmpl 215Procedure 100 Changing the password for demo 217Procedure 101 Changing the password for a BTS telnet session 218Procedure 102 Changing the password for a BTS TIL session 219Procedure 103 Changing the password for the ftp user or usp user 220Procedure 104 Changing the password for the nortel account used by NIMS-

PrOptima 224Procedure 105 Changing the password for omc 226Procedure 106 Changing the password for pm_omcs 227Procedure 107 Changing the password for pm_pdi 229Procedure 108 Changing the password for sridwl 230Procedure 109 Changing the password for SunFire 4800, E4900 232Procedure 110 Changing the password for SunFire V250 234Procedure 111 Changing the password for a T3 external disk storage array 235Procedure 112 Finding an existing clear text password 237Procedure 113 Encrypting a password 238Procedure 114 Inserting the encrypted password 238Procedure 115 Accessing the Performance Management Administration

menu 243Procedure 116 Setting XML compression for the ADI 250Procedure 117 Configuring NetRx 252Procedure 118 Installing the CLI*manager for Windows 253Procedure 119 Installing the CLI*manager for Solaris 253Procedure 120 Starting the GGSN provisioning CLUI 255Procedure 121 Adding an SCS connection 255Procedure 122 Deleting an SCS connection 257Procedure 123 Editing an SCS connection 258Procedure 124 Testing an SCS connection 259Procedure 125 Updating the refresh interval 260Procedure 126 Viewing the refresh interval 261Procedure 127 Exporting an XML snapshot file 262Procedure 128 Importing an XML workorder 263


Nortel Networks Confidential Contents xi

Procedure 129 Exporting an XML snapshot file for the network 264Procedure 130 Removing a server from the Orbix Trader 265Procedure 131 Configuring a user on the server of clients 268Procedure 132 Configuring NIMS-PrOptima for W-NMS on the server of

clients 272Procedure 133 Configuring SRS on the server of clients 273Procedure 134 Discovering an SNMP network element 278Procedure 135 Discovering an MLC 280Procedure 136 Discovering a GGSN 282Procedure 137 Removing an SNMP network element 283Procedure 138 Configuring a Multiservice Switch 285Procedure 139 Grouping Multiservice Switches 289Procedure 140 Setting a Multiservice Switch as an Aggregation Node 291Procedure 141 Ungrouping a Multiservice Switch group 292Procedure 142 Deleting a Multiservice Switch 293Procedure 143 Starting the alarm filtering CLI 300Procedure 144 Passing alarm Ids or alarm groups 301Procedure 145 Blocking alarm Ids or alarm groups 303Procedure 146 Viewing the current filters 304Procedure 147 Passing previously blocked alarms 305Procedure 148 Downloading a patch 308Procedure 149 Installing a patch on the SRS 309


xii Contents Nortel Networks Confidential


Nortel Networks Confidential ix

About this document 1This document provides procedures for fault, configuration, and performance management of the core network elements in the Nortel Wireless Network Management System (W-NMS). It also provides procedures for enabling the W-NMS security features. There is also information about users in W-NMS.

Audience for this document 1This document is for W-NMS administrators who:

• Add core network elements to the W-NMS for fault management, configuration management or performance management.

• Control the working state of components in the W-NMS.

• Administer the security features of the W-NMS.

Organization of this document 1This document contains the following sections:

“About W-NMS” explains where to find descriptive information on W-NMS, and describes the Performance Server.

“Fault management and configuration management” contains procedures for adding a new network element to W-NMS. Some of the network elements allow you to monitor only faults through the Main Server of W-NMS, while others allow you to monitor faults and manage configuration of the device.

“Alarm on threshold” describes the near real time alarm on performance threshold crossing feature. These types of alarms are generated by W-NMS based on performance data received from a network element.

“Performance management” contains procedures for configuring W-NMS to collect performance data from a particular network element.

“Security administration” contains procedures for administering the security features of W-NMS.

“Tools and utilities” contains procedures for using the tools and utilities in W-NMS.


x About this document Nortel Networks Confidential

“Wireless Network Management System users” describes some of the user IDs that are specific to W-NMS and what they are used for. It also provides a reference to information on user administration tasks.

“Appendix A: SNMP and Multiservice Switch-based network element procedures” contains procedures that are used for more than one network element. They are referenced in “Fault management and configuration management”.

“Appendix B: Filtering alarms” contains procedures for enabling alarm filtering at the coreDA level and at the MDM level.

“Appendix C: Patching W-NMS” explains how to download a patch, install it on the SRS server, and then apply the patch to the server.

Related documents 1The following Nortel Technical Publications (NTPs) provide more information about the products and services described in this document:

• Preside MDM Performance Management User Guide, 241-6001-031

• Preside Multiservice Data Manager SNMP Surveillance Adapter Guide, 241-6001-118

• Preside MDM Administrator Guide, 241-6001-303

• Preside Multiservice Data Manager Server Reference Guide, 241-6001-310

• Preside Generic Device Integration Installation Guide, 241-6003-100

• Wireless Network Management System Core Network Observation Counters, 411-5221-401

• UMTS Global OAM Overview, 411-8111-502

• Wireless Network Management System Engineering Guide, 450-3101-638

Road map to the W-NMS documentation 1The following diagrams show the NTPs in the W-NMS documentation suite.


Nortel Networks Confidential Road map to the W-NMS documentation xi


xii About this document Nortel Networks Confidential

Special text conventions in this document 1The following text conventions are used in this document:

• Commands, menu selections and GUI buttons are shown in Bold Text.

• Parameters (values that you enter or are specific to your system) are shown <inside angle brackets>.

• Explanations and descriptions of system responses are shown in Italic Text.

• Verbatim system output is shown in non-proportional text.

Indication of hypertext links 1Hypertext links in this document are indicated in blue. If viewing a PDF version of this document, click on the blue text to jump to the associated section or page.


Nortel Networks Confidential 1

About W-NMS 2Wireless Network Management System (W-NMS) is a system for management of access and core networks, including fault management, configuration management, and performance management. For more information about W-NMS, see the UMTS Global OAM Overview, 411-8111-502.

Network Services Platform 2The Network Services Platform (NSP) provides access to the network elements. Refer to the Wireless Network Management System Engineering Guide, 450-3101-638, for a description of NSP. For procedures used to administer NSP, see the Wireless Network Management System Network Services Platform User Guide, 411-5221-211.

Process management 2The Nortel version of the Sun Management Center, known as System ManaGement (SMG), is used to manage the processes running on the W-NMS servers. For information about the SMG, refer to Wireless Network Management System Management, 411-8111-538.

SNMP-managed devices for fault management 2W-NMS monitors SNMP-managed network elements through the use of fault cartridges and the Preside Multiservice Data Manager SNMP Surveillance Adapter feature. For more information about SNMP network elements, see the Generic Device Integration Installation Guide, 241-6003-100.

About network element releases 2The procedures in this document are meant to be used with specific software releases of a network element. For information about the supported software releases for the network elements, see the Wireless Network Management System Engineering Guide, 450-3101-638.

About the procedures in this document 2For the procedures that are applicable to a main server, they apply for both a primary main server and a secondary main server, unless otherwise indicated.


2 About W-NMS Nortel Networks Confidential


Nortel Networks Confidential Requirements 3

Fault management and configuration management 3

This section contains network element integration procedures for W-NMS. The procedures explain the process for making a network element communicate with the servers responsible for fault and configuration management so that the network element can be managed using W-NMS. There are common procedures in “Appendix A: SNMP and Multiservice Switch-based network element procedures” and the W-NMS Operator Guide, 411-5221-505. These common procedures are referenced in this section in the procedures for each network element.

The procedures listed in this section describe how to integrate the network elements for fault management in W-NMS. For the following network elements, fault management integration provides integration for configuration management as well:

• Multiservice Switch 7400, 15000, 20000

• MSC, HLR 100, HLR 200, and combined MSC/HLR through SDM

• Aggregation Node (AN), Media Gateway (MGW), Interworking Function (IWF)

• SGSN

If your implementation of W-NMS contains both a primary main server and a secondary main server, you must ensure that the network elements being administered are configured in either the primary main server or the secondary main server, not both.

Requirements 3Before performing the procedures in this section:

• Install all software related to each network element to be integrated. Some of the network elements are integrated through the use of the MDM SNMP Surveillance Adapter feature, which requires the use of fault cartridge or network element integration software. For information on fault cartridge installation, see the Generic Device Integration Installation Guide, 241-6003-100.

• You must know how to use a text editor installed on the OAM server, for example, the UNIX text editor vi.

• IP connectivity must be established between the main server and the network elements.


4 Fault management and configuration management Nortel Networks Confidential

ATTENTIONIf a new server instance has been added, or if network elements have been moved from one server to another, you must reset access permissions to allow users to view the details and alarms of the network elements associated with the new or changed server instance. To reset access permissions, clear and then reselect all of the user group columns for the Network Element resource type in the Access Control window.


Nortel Networks Confidential Applications Switch 5

Applications Switch 3The procedures in this section explain how to configure, discover, verify, and delete the Nortel Applications Switch.

Configuring the Applications SwitchPerform Procedure 1 to configure the Applications Switch to communicate with the main server.

PrerequisitesBefore performing Procedure 1 you must know the following information about the Applications Switch you are configuring:

• the IP address of the main server that the Applications Switch is connected to

• the IP address of the Applications Switch

• the admin password of the Applications Switch

• write community string

• read community string, first trap destination community string, second trap destination community string (the values for these community strings must be the same)

Do not use "public" as the value for any of the community strings.

Procedure 1:Configuring the Applications Switch

Step Action

1 Telnet to and log into the Applications Switch.

2 Type the following command to modify the first SNMP trap destination to the IP address of the main server:

/cfg/sys/ssnmp/trap1 <main server IP address>

3 Type the following command to modify the second SNMP trap destination to the IP address of the main server:

/cfg/sys/ssnmp/trap2 <main server IP address>

4 Type the following command to modify the read community string:

/cfg/sys/ssnmp/rcomm <read community string>

—sheet 1 of 2—



Network element discoveryPerform Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the Applications Switch on the main server. Use idi_AAS as the value for the Discover As field.

VerificationPerform Procedure 2 to generate an authentication failure alarm on the Applications Switch. The alarm appears in the NSP Alarm Manager.

5 Type the following command to modify the write community string:

/cfg/sys/ssnmp/wcomm <write community string>

6 Type the following command to modify the community string used in trap sending to the first trap destination:

/cfg/sys/ssnmp/t1comm <trap1 community string>

7 Type the following command to modify the community string used in trap sending to the second trap destination:

/cfg/sys/ssnmp/t2comm <trap2 community string>

8 Type the following commands:

apply

save

The following message displays:

Request will first copy the FLASH "active" config to "backup",then overlay FLASH "active" with new config.Confirm saving to FLASH [y/n]:

9 Type:

y

10 Type:

exit

You are finished configuring the Applications Switch to communicate with the main server.

Procedure 1:Configuring the Applications Switch (continued)

Step Action

—sheet 2 of 2—


Nortel Networks Confidential Applications Switch 7

PrerequisitesBefore performing Procedure 2, you must know a user ID and password for the NSP.

Restrictions and limitationsNone.

DeletionTo delete the Applications Switch from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete it from the main server. Remove the main server IP address from the SNMP Configuration Menu of the Applications Switch.

Procedure 2:Generating an alarm on the Applications Switch

Step Action

1 Telnet to the Applications Switch.

2 Try to log in, using an invalid password.

3 Try to log in again, using an invalid password.

4 In NSP, open a layout that contains the Applications Switch.

5 Click on the Applications Switch icon and right-click on the network element then select Show Alarms to open the Alarm Manager window. Verify that a altSwLoginFailure alarm appears in the alarm list.

You are finished verifying that the Applications Switch communicates with the main server.



Audio Provisioning Server 3The procedures in this section explain how to configure, discover, and delete the Audio Provisioning Server (APS).

Configuring the APSThis procedure explains how to configure APS and discover the it on the main server.

Procedure 3:Configuring the APS

Step Action

Configuring the APS server

1 Log into the APS server using the root user Id and password.

2 In a command line window, type:

apscli

The APS Command Line Interface MAIN menu displays.

3 Type the number of the APS SNMP Agent, configure, start, stop menu item:

6

The APS Command Line Interface SNMP menu displays:

4 Type the number of the Stop APS SNMP agent menu item:

1

5 Wait for the message "Hit return to continue" to appear.

6 Press Enter.

7 Type the number of the Configure APS SNMP Agent menu item:

3

8 Type the number of the Enter New Configuration Data selection:

1

9 Type the number of the default element manager’s IP address (192.168.20.26):

1

10 Type the number for the 162 port (used by the element manager to receive traps or alarms/logs):

1

—sheet 1 of 3—


Nortel Networks Confidential Audio Provisioning Server 9

11 Type the number of the answer yes to the question should the agent forward alarms/logs to syslog?:

1

12 Type the number of the error, warning, and informational messages logging level:

3

13 Type the number of the port that the agent uses to receive SNMP messages from the element manager (5161):

1

14 Type the number of the non-public Read community string selection (Other Read community string):

2

15 Type the read community string that the SNMP agent should use to authenticate SNMP GET messages. Do not use the value "public".

16 Type the number of the non-admin Write community string selection (Other Write community string):

2

17 Type the write community string that the agent should use to authenticate SNMP SET messages. Do not use the value "admin".

18 Type the number of the v2 SNMP version:

2


20 Press Enter.

21 Type the selection to exit the APS Command Line Interface SNMP menu:

x

22 Type the number of the APS SNMP Agent, configure, start, stop menu item:

6

23 Type the number of the Start APS SNMP agent menu item:

2

Procedure 3:Configuring the APS (continued)

Step Action

—sheet 2 of 3—




DeletionTo delete the APS from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete it from the main server.


25 Press Enter.

26 Type the selection to exit the APS Command Line Interface SNMP menu:

x

27 Type the selection to exit the APS Command Line Interface MAIN menu:

x

28 Log off of the APS.

Discovering the APS

29 Log into the main server using a user Id that has MDM administrative privileges


cd /opt/MagellanNMS/bin

31 Type:

./dcdAddNode APS <devName> <addr> <community string> 5161 186

where <devName> is an alphanumeric name for the APS, <addr> is the IP address of the APS, and <community string> is the name of the community string. Do not use the value "public".

You are finished configuring the APS.

Procedure 3:Configuring the APS (continued)

Step Action

—sheet 3 of 3—


Nortel Networks Confidential Border Gateway 11

Border Gateway 3This section explains how to configure, discover, verify, and delete the Border Gateway (BG).

Network element integration summaryTo make the Border Gateway communicate with the main server, you must perform the following procedures:

1. configure the Border Gateway SNMP agent to send traps to the main server

2. enroll the Border Gateway network element on the main server using the IP Discovery tool installed on the main server

Network element configurationPerform Procedure 4 to configure the Border Gateway SNMP agent to communicate with the main server.

PrerequisitesBefore performing Procedure 4 you must know:

• the IP address of the main server

• the management IP address of the Border Gateway

• the user Id and password of the Border Gateway

The community string must be defined on the Border Gateway with an access mode of READ. Do not use the community string "public".

Procedure 4:Configuring the Border Gateway

Step Action

1 Open a web browser. Type in the URL http: //<management IP address of the Border Gateway> to launch the login window.

2 Click on Manage Switch.

3 Type a User name and Password and click on OK.

4 Click on ADMIN and select SNMP from the navigation menu on the left side of the window.

—sheet 1 of 2—



Network element discoveryDiscover the network element using Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the Border Gateway on the main server. Use the value idi_bg as the value for the Discover As field.

VerificationPerform Procedure 5 to generate a login authentication failure alarm by entering an invalid user ID or password in the login window. The alarm appears in the NSP Alarm Manager.

5 Type values for the following fields:

• Host Name or IP address: the IP address of the main server

• Community Name: the GET community string on the network element. Do not use "public".

6 Select the Enable check box to the left of the Host Name or IP address field.

7 Click on OK.

8 Click on ADMIN and select SNMP TRAPS from the navigation menu on the left side of the window.


• Host Name or IP address: the IP address of the main server

• Community Name: the TRAP community string on the network element. Do not use "public".

10 Select the Enable check box to the left of the Host Name or IP address field.

11 Click OK to save.

You are finished configuring the Border Gateway to communicate with the main server.

Procedure 4:Configuring the Border Gateway (continued)

Step Action

—sheet 2 of 2—


Nortel Networks Confidential Border Gateway 13


• the management IP address of the Border Gateway

• the user Id and password for the Border Gateway

• the password for the admin user in NSP


DeletionTo delete the Border Gateway from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the Border Gateway network element from the main server. Refer to the Border Gateway configuration procedure and remove all reference to the main server IP address from the SNMP Configuration Menu of the Border Gateway.

Procedure 5:Generating an alarm on the Border Gateway

Step Action

1 Open a web browser. Type in the URL http: //<management IP address of the Border Gateway> to launch the login window.

2 Enter User name and Password to open the navigation window.

3 From the navigation window select SNMP TRAPS.

4 Click on the Configure button at the last row of the TRAP GROUPS section.

5 Click on the Enable check box beside the Failed Login of the first row.

6 Click OK to save, log off, and close the web browser.

7 Launch the login window.

8 Enter an invalid User name and Password combination nine times in less than five minutes to generate a MAJOR alarm.

9 In NSP, open a layout containing the Border Gateway. Right-click on the Border Gateway network element icon and select Show Alarms to open the Alarm Manager window. Verify that a login authentication failure alarm appears in the alarm list.

You have verified that the Border Gateway communicates with the main server.



Business Policy Switch 2000 3This section explains how to configure, discover, verify, and delete the Business Policy Switch (BPS) 2000.

PrerequisitesBefore performing this procedure you must know:



• the IP address of the BPS 2000

• a password for the BPS 2000 that has Read-Write privileges

In addition, BPS 2000 must be configured to allow you to set the trap destinations through a telnet session:

• UDP port 161 must be set for public access (this is a requirement for the BPS 2000 that is not related to the community string.)

Network element integration summaryTo make the BPS 2000 and the main server communicate management information, you must perform the following procedures:

1. configure the BPS 2000 SNMP agent to send traps to the main server

2. enroll the BPS 2000 on the main server using the IP Discovery tool installed on the main server

Network Element configurationPerform Procedure 6 to enable the BPS 2000 to communicate with the main server.

Prerequisites Before performing Procedure 6 you must know the trap community string and the read community string for the BPS2000. The trap community string and the read community string must be the same value and the value must not be "public".

Procedure 6:Configuring the BPS 2000

Step Action

1 Telnet to the BPS 2000.

2 Enter Ctrl-y and enter the password that has Read-Write privileges.

3 From the Main Menu: use the arrow key to select the SNMP Configuration option, then press the Enter key.

—sheet 1 of 2—


Nortel Networks Confidential Business Policy Switch 2000 15

Network element discovery and main server configurationUse the Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the BPS 2000 on the main server. Do not use BPS 2000 as the value for the Discover As field, unless the device type cannot be determined using normal IP discovery methods.

VerificationConsult your local BPS 2000 expert for a method for generating a non service-affecting trap on the BPS 2000. Refer to the cartridge installation manual for a description of alarms for the BPS 2000 and ensure that the procedure generates a trap rather than state change that results in a polling alarm. The integration of the network element is verified when an alarm resulting from a trap appears in the NSP Alarm Manager.


DeletionUse Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the BPS 2000 from the main server. Refer to the BPS 2000 integration procedure for the location of the trap destination list (Trap #) and delete the entry containing the IP address of the main server.

4 In the Read-Only Community String field, type the NE read community string.

5 From the SNMP Configuration Menu, use the arrow key to scroll down to the Trap # slot that is available.

6 From the Trap # slot, type the main server IP address in the IP address field.

7 Press <Return> or <Enter>.

8 In the Community String field, type the community string that has read access to the network element.

9 Press <Return> or <Enter>.

10 Press Ctrl-c to save the setting and return to Main Menu.

11 Use the arrow key to scroll to the Logout option, then press the Enter key to log out of the BPS 2000.

You are finished configuring the BPS 2000 to send traps to the main server.

Procedure 6:Configuring the BPS 2000 (continued)

Step Action

—sheet 2 of 2—



Data Server 3This section explains how to configure, verify, and delete the Data Server. These procedures apply to the primary main server only. Do not configure a Data Server on the secondary main server.

To make the Data Server communicate with the main server, you must perform the following procedures:

• configure the Data Server

• enroll the Data Server on the main server

Configuring the Data ServerThis procedure configures the SMC agent on the Data Server to send traps to the main server. You must perform this procedure for each node of the mated pair Data Server.

PrerequisitesBefore performing this procedure you must:

• have the SunMC agent installed on the Data Server (For more information, see the section that describes OAM boxes in System Management, 411-8111-538.)

• know a maint-type user ID and password for the Data Server

• know the password for the root user on the Data Server

• know the IP address and host name of the Data Server

• know the IP address and host name of the main server

Procedure 7:Configuring the Data Server

Step Action

1 Telnet to the Data Server and log in a maint-type user ID.

2 Type:

su - root

3 Edit the /etc/hosts file.


Nortel Networks Confidential Data Server 17

Enroll the Data Server on the main serverThis procedure enrolls the Data Server on the main server, using the coreEMS Commissioning Manager.


• know the IP addresses of both nodes in the mated pair Data Server

4 Add the following the line to the file:

<IP address> <host name> sunmcsrv

where <IP address> is the IP address of the main server

where <host name> is the host name of the main server

Note: The file must contain only one line that has this format. Remove all other instances of the alias "sunmcsrv" that exist in the file.

5 Save the /etc/hosts file.

6 Stop the SMC agent by typing the following command:

/opt/SUNWsymon/sbin/es-stop -a

Obey any messages that display. You might be instructed to wait five minutes before proceeding.

7 Start the SMC agent:

/opt/SUNWsymon/sbin/es-start -a &

You are finished configuring the Data Server.

Procedure 7:Configuring the Data Server (continued)

Step Action



Procedure 8:Enroll the Data Server on the main server

Step Action

1 Log into a Unix platform using Exceed on the W-NMS client PC. Refer to the W-NMS Operator Guide, 411-5221-505 for information about Exceed.

2 Log into the main server using the nortel user ID.

3 Set the DISPLAY variable to the IP address of your workstation. Refer to the W-NMS Operator Guide, 411-5221-505 for information about how to set the DISPLAY variable.


cd /opt/nortel/data/coreEMS/nodes/server/bin

./configCEMS &

The coreEMS Commissioning Manager opens in the X display window.

In the Node Configuration tab:

5 In the Command field, select Create from the list.

6 In the Device Type field, select DS.

7 In the Element Name field, type <element name>

where <element name> is the name for the network element.The name should be a string of up to 15 characters drawn from the alphabet (a - z), digits (0 - 9), and minus (-). The first character must be alphabetic and the last character must not be a minus sign.

8 In the IPAddressDS1 field, type the IP address of the first node of the mated pair Data Server.

9 In the IPAddressDS2 field, type the IP address of the second node of the mated pair Data server.

10 Leave the AgentPortDS1 and AgentPortDS2 at the default value of 6161.

11 In the AuditTime field, type a value between 30 and 1440 minutes. The default value is 60.

12 In the PollingTime field, type a value between 30 and 120 minutes. The default value is 60.

13 Click on Submit.

The Confirm your action window opens, asking for confirmation of the changes.

14 Click on the Yes button.


Start all applications for node <node name>?

—sheet 1 of 2—


Nortel Networks Confidential Data Server 19

VerificationPerform the following procedure to verify that the Data Server has been successfully configured.



Command complete successfully!

16 Click on the OK button.

Under Navigator, The Data Server appears in the Nodes/DS folder.

17 Log into NSP and add the Data Server to a network layout using the procedures in the Network Services Platform User Guide, 411-5221-211.

You are finished enrolling the Data Server.

Procedure 9:Verify the Data Server

Step Action

1 Log into NSP.

2 In the main window of NSP, click on SMC in the lower left hand corner.

3 Log into the SMC using the SMCAdmin user ID.

4 Under SMC Domains, select Network Management from the list.

Under Location:Network Management, the Data Server shows up.

You are finished verifying that the Data Server communicates with the main server.

Procedure 8:Enroll the Data Server on the main server (continued)

Step Action

—sheet 2 of 2—



Deleting the Data ServerPerform the following procedure to delete the Data Server from the main server.

Procedure 10:Deleting the Data Server

Step Action






./configCEMS &


In the Node Configuration tab:

5 In the Command field, select Delete from the list.

6 In the Element Name field, type <element name>

where <element name> is the name of the Data Server you want to delete.

7 Click on Submit.


Proceed to delete the node <node name>?



Command complete successfully!

Under Navigator, The Data Server disappears from the Nodes/DS folder.

9 Log into NSP and verify that the Data Server has been removed from the Data Store and all network layouts.

You are finished deleting the Data Server.


Nortel Networks Confidential Ethernet Switch 450 21

Ethernet Switch 450 3This section explains how to configure, discover, verify, and delete the Nortel Ethernet Switch 450.

Network element integration summaryTo make the Ethernet Switch 450 and the main server communicate management information, you must perform the following procedures:

1. configure the Ethernet Switch 450 SNMP agent to send traps to the main server

2. enroll the Ethernet Switch 450 on the main server using the IP Discovery tool installed on the main server

Network element configurationPerform Procedure 11 to configure the Ethernet Switch 450 SNMP agent to communicate information with the main server.



• the IP address of the Ethernet Switch 450

• a password for the Ethernet Switch 450 that has Read-Write privileges (required for logging into the network element)

In addition, the Ethernet Switch 450 must be configured to allow you to set the trap destinations through a telnet session. UDP port 161 must be set for public access (this is a Ethernet Switch 450 setting that is not related to the community string.)



Network element discoveryUse Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the Ethernet Switch 450 on the main server. Do not use B450 for the value of the Discover As field unless the device type cannot be determined using normal IP discovery methods.

VerificationConsult your local Ethernet Switch 450 expert for a non service-impacting procedure for generating a trap on the Ethernet Switch 450. Refer to the cartridge installation manual for a description of alarms for the Ethernet Switch 450 and ensure that the procedure generates a trap rather than state change that results in a polling alarm. The integration of the network element is verified when an alarm resulting from a trap appears in the NSP.

Procedure 11:Configuring the Ethernet Switch 450

Step Action

1 Telnet and log on to the Ethernet Switch 450.

2 Enter Ctrl-y and enter the password that has Read-Write privileges.

3 From the Main Menu, use the arrow key to select the SNMP Configuration option, then press the Enter key.

4 From the SNMP Configuration Menu, use the arrow key to scroll down to a Trap # slot that is available.

5 In the Trap # slot, enter the following information:

a. IP address: enter <main server IP address>

Press <Return> or <Enter>.

b. Community String: enter <community string>

where <community string> is the community string that has read access to the network element. Do not use the value "public".

Press <Return> or <Enter>.

6 Press Ctrl-c to save the setting and return to Main Menu.

7 Use the arrow key to scroll to the Logout option and press the Enter key to log out of the Ethernet Switch 450.

You are finished configuring the Ethernet Switch 450 to send traps to the main server.


Nortel Networks Confidential Ethernet Switch 450 23


DeletionPerform Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the Ethernet Switch 450 from the main server. Refer to the network element configuration procedure for the location of the trap destination list (Trap #) and delete the entry with the main server IP address.



Funk Steel-Belted Radius 3For more information about the Funk Steel-Belted Radius (SBR), refer to the Funk SBR documentation.

Network element integration summaryTo make the Funk SBR communicate with the main server, you must perform the following procedures:

• Configure the Funk SBR SNMP agent to send traps to the main server

• Enroll the Funk SBR network element on the main server using the IP Discovery tool installed on the main server

Configuring the Funk SBR 3.0 SPE or 4.6 SPEPerform Procedure 12 to configure the Funk SBR 3.0 SPE or 4.6 SPE SNMP agent.


• the IP address of the Funk SBR

• the password for the root user on the Funk SBR

• the read community string, trap community string, and the read/write community string for the network element (all three must have the same value and it must not be "public")

• the write community string for the network element (must not be "public")

• the host name of the main server or host name of the MDM server

Procedure 12:Configuring the Funk SBR 3.0 SPE or 4.6 SPE

Step Action

1 Telnet and login to the Funk SBR using the root user ID.

2 Change directory to /etc/snmp/conf.

—sheet 1 of 4—


Nortel Networks Confidential Funk Steel-Belted Radius 25

3 Open the enterprises.oid file.

4 Verify that the following line appears in the file exactly as shown. If the line is not in the file, add it:

"funkSbrTraps" "1.3.6.1.4.1.1411.1.1"

5 If you changed the enterprises.oid file, save it.

6 Close the enterprises.oid file.

7 Use a text editor to edit the snmpd.conf file. For example:

vi snmpd.conf

8 Modify the community string of the Master Agent. Change the lines as shown:

system-group-read-community <read community string>

system-group-write-community <write community string>

read-community <read community string>

write-community <write community string>

trap localhost, <host name>

trap-community <trap community string>

where <read community string> is the read community string, <write community string> is the write community string, <trap community string> is the trap community string for generic traps, and <host name> is the host name of main server or MDM server.

9 Save and close the snmpd.conf file.

Procedure 12:Configuring the Funk SBR 3.0 SPE or 4.6 SPE (continued)

Step Action

—sheet 2 of 4—



10 Use a text editor to edit the snmpdx.acl file. For example:

vi snmpdx.acl

11 In the Access Control section of the file, modify the following lines as shown:

acl = { { communities = public, <read/write community string> access = read-write managers = * }}

where <read/write community string> is the read/write community string.

12 In the Trap Parameters section of the file, modify the following lines as shown:

trap = { { trap-community = <trap community string> hosts = < host name >

{ enterprise = "funkSbrTraps" trap-num = 100-110, 5000-5027, 10000-10050 } }}

where <trap community string> is the community string for the specific traps shown, and <host name> is the host name of the main server or MDM workstation.

13 Save and close the snmpdx.acl file.

14 Use a text editor to edit the radsnmp.acl file. For example:

vi /etc/snmp/conf/radsnmp.acl


Step Action

—sheet 3 of 4—



15 In the Access Control section of the file, modify the following lines as shown:

acl = {{

communities = <read/write community string>access = read-writemanagers = *

}}

where <read/write community string> is the read/write community string.

16 In the Trap Parameters section of the file, modify the following lines as shown

trap = {

{

trap-community = <trap community string> hosts = <host name> { enterprise = “funkSbrTraps” trap-num = 100-110, 5000-5027, 10000-10050 }}

where <trap community string> is the community string for the specific traps shown, and <host name> is the host name of the main server or MDM workstation.

17 Save and close the radsnmp.acl file.

18 Stop the SNMP Master Agent (snmpdx) by typing:

/etc/rc2.d/K07snmpdx stop

19 Start the SNMP Master Agent (snmpdx) by typing:

/etc/rc2.d/K07snmpdx start

You are finished configuring the Funk SBR to communicate with the main server.


Step Action

—sheet 4 of 4—



Configuring the Funk SBR 4.7.8 SPEPerform Procedure 13 to configure the Funk SBR SNMP agent for the Funk SBR release 4.7.8 SPE.


• the IP address of the Funk SBR

• the password for the root user on the Funk SBR

• the host name or IP address of the main server

• the SNMP community string, trap community string, and NMS community string for the network element (all three community strings must have the same value and it must not be "public")

• the main server listener port for SNMP traps

Procedure 13:Configuring the Funk SBR 4.7.8 SPE

Step Action

1 Telnet and login to the Funk SBR using the root user ID.

2 Change to the directory in which the Funk SBR is installed. Then change to the subdirectory radius/snmp/conf.

3 Use a text editor to edit the funksnmpd.conf file.

4 Modify the following line as shown:

com2sec <security name> <source> <community string>

where <security name> is an existing security name. If you want to use a new security name, you must create it. Refer to the Funk SBR documentation for information on how to create a security name.

where <source> is a host name, subnet, or the work default of the main server. If you specify a subnet, it can be an IP address and mask in the form nnn.nnn.nnn.nnn/ nnn.nnn.nnn.nnn or an IP address and Classless Inter-Domain Routing (CIDR) bits in the form nnn.nnn.nnn.nnn/nn

where <community string> is the SNMP community string


trapcommunity <trap community string>

where <trap community string> is the SNMP trap community string

—sheet 1 of 2—



Network element discoveryUse Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the Funk SBR. Use idi_funksbr as the value for the Discover As field.

VerificationConsult your local Funk SBR expert for a non-service affecting procedure to generate a trap on the Funk SBR. Refer to the cartridge installation manual for a description of alarms for the Funk SBR and ensure that the procedure generates a trap rather than state change that results in a polling alarm. The integration of the network element is verified when an alarm resulting from a trap appears in the NSP Alarm Manager.

Restrictions and limitationsThe Funk SBR Administration tool can be launched from the NSP context menu for the Funk SBR server. However, this functionality is disabled when OS hardening is installed and active on the Funk SBR server. This normally


trapsink <host><trap community string><port>

where <host> is the host name or IP address of the main server, <trap community string> is the SNMP trap community string, <port> is the main server listener port for SNMP traps

7 Save and close the funksnmpd.conf file.

Update the SNMP agent

Update the SNMP agent configuration data by performing either step 8 or step 9.


/etc/init.d/init.funksnmpd stop

/etc/init.d/init.funksnmpd start

9 Type the following command:

Kill -HUP <process ID>

where <process ID> is the process ID for the funksnmpd process.

End of procedure.

Procedure 13:Configuring the Funk SBR 4.7.8 SPE (continued)

Step Action

—sheet 2 of 2—



occurs when the Funk SBR software is installed on the same server as the MetaSolv Policy Services software. OS hardening is required to secure the MetaSolv Policy Services server, but not the Funk SBR. To work around this limitation, either install Funk SBR on its own hardware, or perform Procedure 14.

DeletionTo delete the Funk SBR from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the Funk SBR network element from the main server. For Funk SBR 3.0 SPE or 4.6 SPE, remove the trap host from the /etc/snmp/conf/snmpdx.acl file on the Funk SBR server. For Funk SBR 4.7.8 SPE, remove the modification in <funksbr_install_dir>/radius/snmp/conf/funksnmpd.conf file on the Funk SBR server.

Enabling rsh and rexec This procedure enable rsh and rexec on a combined MetaSolv Policy Services and Funk SBR server.

Procedure 14:Enable rsh and rexec

Step Action

1 Log into the Funk SBR using the root user Id.

2 Edit the file /etc/inet/inetd.conf and uncomment the following lines:

shell stream tcp nowait root /usr/sbin/in.rshd in.rshd

shell stream tcp6 nowait root /usr/sbin/in.rshd in.rshd

exec stream tcp nowait root /usr/sbin/in.rexecd in.rexecd

exec stream tcp6 nowait root /usr/sbin/in.rexecd in.rexecd

3 Restart inetd to bring the change into effect. Get the process ID of the inetd by entering:

# ps -ef | grep inetd

A line of output similar to the following displays:

root <inetdpid> 1 0 Dec 11 ? 0:00 /usr/sbin/inetd -s

Take note of the <inetdpid> and enter the following command:

# kill -1 <inetdpid>

The inetd stops and restarts.

—sheet 1 of 2—



You are finished enabling rsh and rexec on the combined MetaSolv Policy Services and Funk SBR server.

Procedure 14:Enable rsh and rexec (continued)

Step Action

—sheet 2 of 2—



GGSN 3This section explains how to configure, discover, verify, and delete the GGSN.

Network element integration summaryDetermine whether management cable redundancy is required. Management cable redundancy means that if someone disconnects the cable to one of two CMC cards in the GGSN, the other one is used to send traps to the W-NMS. The configuration for management cable redundancy results in the W-NMS taking up to three times longer to recover from a total loss of communications to the GGSN compared to no management cable redundancy.

To make the GGSN and the main server communicate with each other without management cable redundancy, you must:

1. configure the GGSN SNMP agent to send traps to the main server

2. enroll the GGSN network element on the main server using the IP Discovery tool installed on the main server

To make the GGSN and the main server communicate with each other with management cable redundancy, you must:

1. configure the GGSN Management IP address, the first Auxiliary Management Interface IP address, and the default IP address (see Nortel Networks GGSN User Guide, 411-5221-926 and Nortel GGSN Provisioning Procedures, 411-5221-927)

2. configure the GGSN SNMP agent to send traps to the main server

3. enroll the default Gi ISP address network element on the main server using the dcd_AddNode script on the main server

4. enroll the IP addresses of the management ports on the two CMC cards using the dcd_addAddress script on the main server

Network element configurationPerform Procedure 15 to configure the GGSN SNMP agent to communicate with the main server.

PrerequisitesBefore performing Procedure 15 you must:

• have an SCS client installed on the client workstation

• know the IP address, device owner user ID, and password for the SCS

• know the IP address of the main server (if you are using IP network multipathing (IPMP), this is the IP address of the main server which corresponds to OAM_NE port)


Nortel Networks Confidential GGSN 33

• determine if statics routes are required to manage the GGSN. If static routes are required, ensure that they are configured in the directory /etc/rc2.d/xxx to manage the OAM_NE port traffic for the GGSN.

• know the community string you want to use for READ access to the network element (do not use "public")

• know the primary management Ethernet IP address for the GGSN (mgmt-eth0) or, for management cable redundancy, the primary management Ethernet IP address (mgmt-eth0), the secondary management Ethernet IP address (mgmt-eth1) and the default IP address for this network element on the Gi ISP (default Gi ISP IP address)

Procedure 15:Configuring GGSN SNMP agent

Step Action

1 From a workstation that has the SCS client installed, log into the SCS client as device owner:

username: <username> password: <xxxxx>SCS server: <IP_Address of SCS server>

2 Select Access Properties from the icons on the left hand side of the screen.

3 Select the SNMP Profiles tab.

4 Click on the Add button.

5 Type a name for the profile (an alphanumeric string).

6 Enter the community string you want to use for READ access to the network element. Do not use "public" as the value for community string.

7 Select the SNMP clients tab and click on the Add button.

8 Enter <IP address of main server>.

9 Click Enable for Relay SNMP Traps.


11 In the main window, click on the Devices icon on the left side of the screen.

12 Select the region containing the GGSN.

13 In the list that appears, right-click on the GGSN, select Configure, then click on Access Properties.

14 Under Direct Access SNMP Profile, select the profile you defined in step 5.

—sheet 1 of 2—



Network element discovery without management cable redundancyDiscover the network element using Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the GGSN on the main server. Use GSNS-5000 as the value for the Discover As field. Use the primary management Ethernet IP address (mgmt-eth0) for the network element IP address.

Network element discovery with management cable redundancyIt is possible to provide cable-level redundancy for the management connection between a GGSN network element and the main server. However, doing so will increase the time it takes to rediscover the GGSN following a loss of communications by up to three times. To enable management cable redundancy, discover the network element using Procedure 136 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the GGSN on the main server.

VerificationConsult your local GGSN expert for a procedure to generate a non-service affecting trap on the GGSN. Refer to the cartridge installation manual for a description of alarms for the GGSN and ensure that the procedure generates a trap rather than state change that results in a polling alarm. The integration of the network element is verified when an alarm resulting from a trap appears in the NSP Alarm Manager.


DeletionTo delete the GGSN network element from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the network element from the main server. Refer to the GGSN configuration procedure and delete the entries for the main server in the SNMP configuration.


You are finished configuring the GGSN.

Procedure 15:Configuring GGSN SNMP agent (continued)

Step Action

—sheet 2 of 2—


Nortel Networks ConfidentialHLR 100, HLR 200, MSC, combined MSC/HLR, or Signaling Gateway 35

HLR 100, HLR 200, MSC, combined MSC/HLR, or Signaling Gateway3The SuperNode Data Manager hosts services and applications that provide OAM&P services for the HLR 100, HLR 200, MSC, combined MSC/HLR, or the Signaling Gateway network elements. One SDM is required for each network element. The procedures in this section apply for a server-based SDM. If you have a stand-alone SDM you must first migrate it server-based mode before performing the other procedures in this section.

Migrate SDM from stand-alone mode to server-based modeThe procedures in this section explain how to migrate the SDM from stand-alone mode to server-based mode.

PrerequisitesBefore performing the procedures in this section, the OMC-S must be running in stand-alone mode on the SDM.

To configure the security of OMC-S to allow you to integrate the SDM with the CEM, you must have the GEM Applications tape.

To migrate to server-based mode, you must have the following information:

• the IP address and password for the nortel user Id on the main server

• the IP address and password for the root user Id on the SDM

• user Id and password for the network element (HLR 100, HLR 200, or combined MSC/HLR)

• USP primary host IP address, secondary host IP address, and the user Id and password (only for the HLR 200).

Migration summaryThis procedure migrates an SDM in stand-alone mode to server-based mode. To migrate the SDM, you must

1. configure OMC-S security on the SDM (Procedure 16)

2. delete OM files (Procedure 17 or Procedure 18)

3. run the migration script (Procedure 19)

After completion of the migration script:

• certain processes and data are transferred from the SDM to the main server

• the main server manages the fault and configuration management capabilities of the SDM - management workstations that previously had monitoring access to this SDM are excluded.



• Wireless Internet Command Language operations can be performed on the associated network element (MSC, HLR 100, HLR 200 or combined MSC/HLR)

Procedure 16:Configuring OMC-S security on the SDM

Step Action

1 Log into the SDM using the root user Id.

2 Start the OMC-S configuration tool:

cd /tmp/upgrade

./omcconfig

3 Perform the following dialog. Your responses are shown in bold text; explanations are shown in italic text and definitions of fields are shown in plain text.

** Main Menu **

1 - Install / Upgrade / Add ...2 - SDM configuration ...3 - SDM administration ...4 - Backup/Restore ...7 - UNIX Shell8 - Help

X - exit

Choice : 2

Configuration Menu

1 - Configure DCE2 - Add hosts3 - Increase paging space4 - Change OMC_S Security option8 - Help9 - # back to main menu #

X - exit

Choice : 4

—sheet 1 of 3—



This procedure will require OMC_S to be briefly brought down and restarted. Do you wish to continue? (Y)es or (N)o? YYou will need to obtain the GEM16 Application tape.

Please insert the GEM16 Applications tape into the LEFT tape drive.Press <Enter> to continue.

Insert the GEM16 Applications tape and press <Enter>

Please choose a security option for OMC_S: a) DCE-based b) LDAP-based c) no securityPlease select one-->b

You have entered ’b’, is this correct (Y)es or (N)o? Y

You have selected LDAP for security authentication.

For authentication to function properly, your LDAP Administrator must ensure:

* An LDAP Server has been installed in the network * Users have been created with accounts in LDAP and that these users have the appropriate group attributes defined.

Consult the IM 24-9020 for additional details.

Are you sure you wish to use LDAP-based security? (Y)es or (N)o? Y

Do you wish to use SSL? (Y)es or (N)o? N

Please enter the Distinguished Name --> ou=People,o=nortel.com

You have entered ’ou=People,o=nortel.com’, is this correct? (Y)es or (N)o? Y

Please enter the IP address of the LDAP Server --> <IP_Address>

where <IP_Address> is the IP address of the primary main server in the ROC.

You have entered ’<IP_Address>’, is this correct? (Y)es or (N)o? Y

Procedure 16:Configuring OMC-S security on the SDM (continued)

Step Action

—sheet 2 of 3—



Modifying /mscomc/OMC_S/EMAdapter/dat/lapd.config file ... done.

/mscomc/OMC_S/EMAdapter/dat/ldap.config modified successfully.

Restarting OMC_S...

Bsying the applicationsRTSing the applicationsdone.

The security option for OMC_S has been successfully changed.

Press enter to return to the menu.

Press <Enter>.

Configuration Menu

1 - Configure DCE2 - Add hosts3 - Increase paging space4 - Change OMC_S Security option8 - Help9 - # back to main menu #

X - exit

Choice : X

Really quit ? (Y)es or (N)o? Ygood bye...

4 Verify that the OMC-S is running in stand-alone mode on the SDM. Type the following command:

ps -ef | grep objectManager | grep -v grep

Verify that the following process is running on the SDM:

./objectManager sdm

You are finished configuring the SDM to allow you to integrate it with the main server.

Procedure 16:Configuring OMC-S security on the SDM (continued)

Step Action

—sheet 3 of 3—



Deleting operational measurement filesIf the SDM has been collecting OM (Operational Measurement) information, the associated files can be large and numerous, and can extend the migration process. To speed up the migration process, use either Procedure 17 or Procedure 18 to reduce the volume of OM data.

Procedure 17 deletes OM archive files by setting the retention period to a lower value. This deletes all OM files older than the specified retention period. Procedure 18 deletes OM archive files by selecting and deleting individual files.

Procedure 17:Method 1: Deleting OM files by retention period

Step Action

1 Log into the SDM as using the root user Id.

2 Start the Archive Admin tool:

cd /mscomc/OMC_S/archive/bin./archiveAdmin.start

The ARCHIVEADMIN TOOLS main menu appears.

3 Selection option 6 (retention period setting).

The following message appears:

Would you like to set a new retention period value now (Y/N)?

4 Enter Y.


New Retention Period (days) [Q=Quit] =

5 Enter the number of days of archives you want retained. 30 days is a typical period. You must ensure that you have enough disk space to accommodate the OM archive files for the retention period you specify.

All files in the archive that are older than the specified retention period are deleted. The following message appears:

SET_RET_REPLY -- Configuration file is updated!

The ARCHIVEADMIN TOOLS main menu appears again.

6 Enter 0 to exit the Archive Admin tools.

You are finished deleting excess OM from the SDM.



Procedure 18:Method 2: Deleting OM files by date

Step Action

1 Ensure that all required OM archives from the SDM are saved to mass storage.


3 Start the Archive Admin tool:

cd /mscomc/OMC_S/archive/bin

./archiveAdmin.start

The ARCHIVEADMIN TOOLS main menu displays.

4 Select option 3 (delete_date)


Version Status------- ------ 1 OPENWhich archive version [Q=Quit]?

5 Enter 1.

A list of all the available archives files displays, followed by a prompt for the date of the archive file to be deleted:

Which DATE [Q=Quit]?

6 Enter 1 to delete the oldest file.


DELETE_DATE -- The DATE is deleted successfully.

The ARCHIVEADMIN TOOLS main menu displays.

7 Repeat step 4 through step 6 for each OM file you want to delete.

8 Enter 0 to exit the Archive Admin Tools.

You have deleted excess OMs from the SDM.



Migrating an SDM from stand-alone mode to server-based modeUse Procedure 19 to migrate an SDM with the OMC-S running in stand-alone mode to server-based mode. If the migration process fails, use Procedure 21 to restore the SDM to a known state.

CAUTIONInterruption of supervision, loss of dataOperational Measurement and Log delivery is deactivated while data is being transferred from the SDM to the main server. Logs generated during this time are saved, but operational measurement files are lost.

Procedure 19:Migrate an SDM from stand-alone mode to server-based mode

Step Action

1 Log into a Unix platform using Exceed on the W-NMS client PC. Refer to the W-NMS Operator Guide, 411-5221-505 information about Exceed.


3 Set the DISPLAY variable to point to your workstation. Refer to the W-NMS Operator Guide, 411-5221-505 for information about how to set the DISPLAY variable.



./configCEMS &


—sheet 1 of 4—



5 In the Node Configuration tab:

a. In the Command field, select Create from the list.

b. In the Device Type field:

i. If the SDM is connected to an MSC, HLR 100, combined MSC/HLR, or a Signaling Gateway network element, select DMS from the list.

ii. If the SDM is connected to an HLR 200, select HLR200 from the list.

c. In the Element Name field, type <element name>

where <element name> is the name for the MSC, HLR 100, HLR 200, or combined MSC/HLR. The name should be a string of up to 15 characters drawn from the alphabet (a - z), digits (0 - 9), and minus (-). The first character must be alphabetic and the last character must not be a minus sign.

d. In the Target SDM IP Address field, type <SDM IP address>

where <SDM IP address> is the IP address of the SDM

6 If you selected DMS for the Device Type in step 5, define the following fields:

Enable Call Trace: If the network element is a combined MSC/HLR, select Yes from the list. If the network element is an MSC or HLR 100, select No from the list.

Install Billing Manager: If the network element is an MSC or a combined MSC/HLR, select Yes from the list. If the network element is an HLR 100, select No from the list.

Does this DMS have USP: If the DMS does not have a USP, select No from the list. Go to step 10. If the DMS has a USP, select Yes from the list. Go to step 7.


USP Primary Host IP Address: IP address of the primary USP

USP Secondary Host IP Address: IP address of the secondary USP

USP User ID: user Id to log into the USP

USP User Password: password for the USP user Id

Confirm USP User Password: password for the USP user Id (Do not copy and paste this field. You must type the value.)

FTP User ID: FTP User Id used to transfer data between the USP and the CEM Server

FTP User Password: password for the FTP user Id

Confirm FTP User Password: password for the FTP user Id (Do not copy and paste this field. You must type the value.)

MSC or TRI node?: From the list, select MSC for an MSC. Select TRI for a combined MSC/HLR.

8 Go to step 10.

Procedure 19:Migrate an SDM from stand-alone mode to server-based mode (continued)

Step Action

—sheet 2 of 4—



9 If you selected HLR200 for the Device Type in step 5, type values for the following fields:

USP Primary Host IP Address: IP address of the primary USP

USP Secondary Host IP Address: IP address of the secondary USP

USP User ID: user Id to log into the USP

USP User Password: password for the USP user Id

Confirm USP User Password: password for the USP user Id (Do not copy and paste this field. You must type the value.)

FTP User ID: FTP User Id used to transfer data between the USP and the CEM Server

FTP User Password: password for the FTP user Id

Confirm FTP User Password: password for the FTP user Id (Do not copy and paste this field. You must type the value.)

Target CMT Server IP Address: IP address of the CMT server

CMT Server Resynchronization Interval: CMT server resynchronization interval in seconds. Type an integer between 60 and 7200.

SN Version: select SN06 or SN07 from the list.

10 Click on Submit.

A message displays, asking for confirmation of the changes.



Is the SDM already in Server Mode?

12 If the SDM has not been newly installed in Server Mode, click on the No button. Go to step 15.

13 If the SDM has been newly installed in Server Mode, click on the Yes button. This eliminates the migration of processes. There is no data to migrate because the SDM was just installed.


Start all applications for node <node name>?



Applications of node <node name> were started.


Step Action

—sheet 3 of 4—




The SDM Migration window opens:

Please start /mscomc/gemCommon/bin/migrationclient.pl on the target sdm.Click the “ok” button after the migrationclient is started on the sdm.

16 Log into the target SDM using the root user and type:

/mscomc/gemCommon/bin/migrationClient.pl

17 Click on the OK button on the main server Commissioning Manager.

The SDM Cutover window opens:

Start SDM cutover process:


Important Information: cancel the cutover process may leave the SDM in a bad state. Only cancel the process when absolutely necessary.


19 Wait until the process finishes. When the process finishes, the following message displays:

SDM cutover completed.


21 A message box opens: Start all applications for node <node name>?


23 A message box opens: Applications of node <node name> were started.


25 Verify the new node is listed under DMS or HLR200 on the right side of the window.

26 Add the network element to a network layout using the procedures in the Network Services Platform User Guide, 411-5221-211.

You are finished integrating the network element that is supported by CEM in server-based mode.


Step Action

—sheet 4 of 4—



VerificationVerify that integration has been successful by finding the MSC, HLR 100, HLR 200, combined MSC/HLR, or Signaling Gateway managed by the SDM in the NSP NE Store, adding it to a layout and viewing the alarms for the network element. Perform Procedure 20 to generate a test alarm.

Procedure 20:Generating an alarm for an MSC, HLR 100, HLR 200, combined MSC/HLR, or Signaling Gateway

Step Action

1 Log into the network element.

2 Enter: willtrap

3 Enter: logout to log out from the network element.

4 In NSP, open a layout containing the network element, click on the icon for it, right-click on the icon, and select Show alarms from the object menu to open NSP alarm manager. Verify that the alarm message includes the word “trap”, and the “time raised” is the time you generated the alarm.

You are finished verifying that the network element communicates with the main server.



Recover from a failed migration attemptIf the migration attempt fails, use Procedure 21 to restore supervision of the MSC, HLR 100, HLR 200, combined MSC/HLR, or Signaling Gateway with the OMC-S on the SDM in stand-alone mode.

Procedure 21:Recover from failed migration attempt

Step Action

1 Log into the main server using the nortel user Id.

2 Set the DISPLAY variable to point to the client workstation. Refer to the W-NMS Operator Guide, 411-5221-505 for more information

3 Start the Commissioning Manager:


./configCEMS &


a. In the Command field, select Delete from the list.

b. In the Target SDM IP Address field, type <SDM IP address>

where <SDM IP address> is the IP address of the SDM to be deleted

5 Click on Submit.


7 Change the working directory:

cd /mscomc/gemCommon/bin

8 Run reRegister.sh

./reRegister.sh

Correct the problem that caused the migration to fail and perform Procedure 19 again.



DeletionPerform Procedure 22 to remove an SDM integrated with the CEM in server-based mode from W-NMS.


Procedure 22:Remove an SDM in server-based mode

Step Action






./configCEMS &

The Commissioning Manager displays in the Exceed window.

5 In the Node Management tab, select Delete, and select the SDM node name connected to the Device to be deleted, click Submit.

A dialog box appears to confirm deletion of the node.


The message “Command completed successfully” appears.

7 Log into the target SDM as the root user and enter /mscomc/gemCommon/bin/reRegister.sh


Please run “mscomc/gemCommon/bin/reRegister.sh” on the SDM to convert it back to a stand-alone SDM.


You are finished deleting the SDM from W-NMS.



IP Services Edge Router 5500 3This section explains how to configure, discover, verify, and delete the IP Services Edge Router 5500.

Network element integration summaryTo make the IP Services Edge Router 5500 and the main server communicate with each other, you must perform the following procedures:

1. configure the IP Services Edge Router 5500 SNMP agent to send traps to the main server

2. enroll the IP Services Edge Router 5500 on the main server using the IP Discovery tool installed on the main server

Network element configurationPerform Procedure 23 to configure the IP Services Edge Router 5500 SNMP agent to communicate with the main server.



• the IP address, device owner user Id and password for the SCS

• the community string you want to use for READ access to the network element (do not use "public" for the value of the community string)

• the primary management Ethernet IP address for the IP Services Edge Router (mgmt-eth0)

An SCS client must be installed on the client workstation.

Procedure 23:Configuring IP Services Edge Router 5500 SNMP agent

Step Action

1 From the PC with an SCS client installed, log into the SCS client as device owner:

username: <username> password: <xxxxx>SCS server: <IP_Address>

2 Select Access Properties from the icons on the left hand side of the screen.

3 Select the SNMP Profiles tab.


5 Type a name for the profile (an alphanumeric string).

—sheet 1 of 2—


Nortel Networks Confidential IP Services Edge Router 5500 49

Network element discoveryDiscover the network element using Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the IP Services Edge Router 5500 on the main server. Use SER-5500 as the value for the Discover As field. Use the primary management Ethernet IP address (mgmt-eth0) as the network element IP address.

VerificationConsult your local IP Services Edge Router 5500 expert for a procedure to generate a non-service affecting alarm on the IP Services Edge Router 5500. Refer to the cartridge installation manual for a description of alarms for the IP Services Edge Router 5500 and ensure that the procedure generates a trap rather than state change that results in a polling alarm. The integration of the network element is verified when an alarm resulting from a trap appears in the NSP Alarm Manager.


6 Enter the community string you want to use for READ access to the network element. Do not use "public" as the value for the community string.

7 Select the SNMP clients tab and click on the Add button.

8 Enter <main server IP>.

9 Click Enable for Relay SNMP Traps.


11 In the main window, click on the Devices icon on the left side of the screen.

12 Select the region containing the IP Services Edge Router 5500.

13 In the list that appears, right-click on the IP Services Edge Router 5500, select Configure, then click on Access Properties.

14 Under Direct Access SNMP Profile, select the name you defined in step 5.


You are finished configuring the IP Services Edge Router 5500.

Procedure 23:Configuring IP Services Edge Router 5500 SNMP agent (continued)

Step Action

—sheet 2 of 2—



DeletionTo delete the IP Services Edge Router 5500 from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the network element from the main server. Refer to the IP Services Edge Router 5500 configuration procedure and delete the entries for the main server in the SNMP configuration.


Nortel Networks Confidential LIG-D Comverse 51

LIG-D Comverse 3This section explains how to configure, discover, verify, and delete the LIG-D Converse network element.

Network element integration summaryTo make the LIG-D Comverse server communicate with the main server, you must perform the following procedures:

1. configure the LIG-D Comverse SNMP agent to send traps to the main server:

— modify the snmpd (Speed dial type) file

— restart the SNMP-related process

2. enroll the LIG-D Comverse network element on the main server using the IP Discovery tool installed on the main server

Network element configurationPerform Procedure 24 to configure the LIG-D Comverse SNMP agent to communicate with the main server.



• the IP address of the LIG-D Comverse network element.



Network element discoveryUse Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the LIG-D Comverse on the main server. Do not use idi_comligd as the value for the Discover As field, except if the device type cannot be determined using normal IP Discovery methods.

Procedure 24:Configuring the LIG-D Comverse

Step Action

1 Log into NTGL (LIGD).

2 Edit the D:\Comverse\SMAgent\srconf\agt\snmpd file (Speed dial type) file. Make the changes shown in bold type.

a. Save a separate copy of the snmpd file (Speed dial type) as a back up.

b. Refer to the following example and insert the IP address of the main server in the file. Note that the backslash characters (\) shown in the example exist in the file .Lines beginning with # in the file are comments:

snmpTargetAddEntry MFM1_Notifications snmpUDPDomain <IP_Address:0> 100 3 \Destination v2cExampleParams nonVolatile 255.255.255.255:0 2048

snmpTargetAddrEntry MFM1_Requests snmpUDPDomain <IP_Address:0> 0 0 - - \nonVolatile 255.255.255.255:0 2048

snmpTargetAddrEntry MFM1_V1Requists snmpUDPDomain <IP_Address:0> 0 0 - - \nonVolatile 255.255.255.255:0 2048

where <IP_Address> is the IP address of the main server

Note: Do not change the text v2cExampleParams.

3 From the Control Panel, select Services. Stop the following processes in the order shown:

a. SNMP Infosys Agent

b. SNMP Emanate Adapter for NT

c. SNMP EMANATE Master Agent

4 From the Control Panel, select Services. Start the following processes in the order shown:

a. SNMP EMANATE Master Agent

b. SNMP Emanate Adapter for NT

c. SNMP Infosys Agent

You are finished configuring the LIG-D Comverse to communicate with the main server.


Nortel Networks Confidential LIG-D Comverse 53

VerificationPerform Procedure 25 to generate a IOPSMcm down alarm by stopping the IOPSmcm process from Task manager. The alarm appears in the NSP Alarm Manager.


• the user Id and password of the machine that has the LIG-D Comverse installed.

• a user ID and password for NSP


DeletionPerform Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the LIG-D Comverse from W-NMS. Remove the main server IP address from the SNMP Configuration Menu of the LIG-D Comverse.

Procedure 25:Generating an alarm on the LIG-D Comverse

Step Action

1 Log into the workstation that has the LIG-D software installed.

2 Open a command window.

3 Shut down the IOPS mcm process. Type the following command:

net stop mcm

4 Verify that the processes have stopped. Enter prms to list all the services that are running. If you see the message “No Services running”, go to step 6. If you see any services running, go to step 5.

5 If you see any services, enter killall. Repeat step 4.

6 In NSP, open a layout that contains the LIG-D Comverse. Select the LIG-D Comverse, right-click it and then select Show Alarms to open the Alarm Manager. Check that a critical alarm “IOPSMCM” appears in alarm list.

7 Restart the IOPS mcm process by executing net start mcm from the command console. Verify that the alarm disappears from the Alarm Manager.

You are finished verifying that the LIG-D Comverse communicates with the main server.



MetaSolv Network Mediation 3This section explains how to configure, discover, verify, and delete the MetaSolv Network Mediation server.

Network element integration summaryTo make the MetaSolv Network Mediation server communicate with the main server, you must perform the following procedures:

1. configure the Network Mediation SNMP agent to send traps to the main server

2. enroll the Network Mediation network element on the main server using the IP Discovery tool installed on the main server

Network element configurationPerform Procedure 26 to configure the Network Mediation SNMP agent to communicate with the main server.


• the IP address of the Network Mediation server

• the password for the root user on the Network Mediation server

• read community string, write community string, trap community string (do not use "public" for any of the community strings)

• a user ID and password for the NSP

• the password for the admin user in the Metasolv Network Mediation Administration GUI


Procedure 26:Configuring the MetaSolv Network Mediation server

Step Action

1 Telnet and login to the Metasolv Network Mediation server using the root user ID.

2 Change directory to /etc/snmp/conf.

3 Use a text editor to edit the smnpd.conf file. For example:

vi snmpd.conf

—sheet 1 of 2—


Nortel Networks Confidential MetaSolv Network Mediation 55

4 Modify the community string of the Master Agent. Change the lines as shown:

system-group-read-community <read community string>

system-group-write-community <write community string>

read-community <read community string>

write-community <write community string>

trap-community <trap community string>

where <read community string> is the read community string, <write community string> is the write community string, and <trap community string> is the trap community string for generic traps. Do not use "public" for any of the community strings.

5 Save and close the file.

6 Stop the SNMP Master Agent (snmpdx) by typing:

/etc/rc2.d/K07snmpdx stop

7 Start the SNMP Master Agent (snmpdx) by typing:

/etc/rc2.d/K07snmpdx start

8 In NSP, open the Metasolv Network Mediation Administration GUI and log in as the admin user.

9 From the Administrative Function menu, choose SNMP Trap Hosts, or click on the SNMP Trap hosts icon in the tool bar.

10 Click on New.

The Add New Host dialog box opens.

11 In the Target Host field, type the IP address of the main server. Do not type the host name of the main server.

12 In the Community field, type the read community string you used in step 4.

13 From the Version list, choose the Snmp_Version1.

14 Click on Save.

The new SNMP target host appears in the SNMP trap host list.

You are finished configuring the MetaSolv Network Mediation server communicate with the main server.

Procedure 26:Configuring the MetaSolv Network Mediation server (continued)

Step Action

—sheet 2 of 2—



Network element discoveryUse Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the MetaSolv Network Mediation server on the main server. Use idi_MNM as the value for the Discover As field.

VerificationPerform Procedure 27 to generate a Server Control alarm by sending a test trap.


• the IP address of the Network Mediation server

• the password for the root user on the Network Mediation server

• the installation path for the Network Mediation software on the Network Mediation server

• a user ID and password for the NSP


DeletionTo delete the MetaSolv Network Mediation server from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the MetaSolv Network Mediation

Procedure 27:Generating an alarm on a Network Mediation server

Step Action

1 Log into a console terminal on the Network Mediation server using the root user Id.


/<MNM_Home>/bin/ProcessControlSendTrap ldap abnormalstop

where <MNM_Home> is the installation path for the Network Mediation server software.

3 In NSP, open a layout containing the Network Mediation server. Highlight the server, right-click on it and select Show Alarms to open the NSP Alarm Manager. Verify that a Server Control alarm appears in the alarm list.

You are finished verifying that the MetaSolv Network Mediation communicates with the main server.


Nortel Networks Confidential MetaSolv Network Mediation 57

network element from the main server. Refer to the Network Element configuration procedure for the location of the SNMP Trap Hosts dialog and use the Delete button to remove the main server from the list of trap hosts.



MetaSolv Policy Services DNS/DHCP 3This section explains how to configure, discover, verify, and delete the MetaSolv Policy Services DNS/DHCP.

Network element integration summaryTo make the Policy Services server communicate with the main server, you must:

1. configure the Policy Services SNMP agent to send traps to the main server

2. enroll the Policy Services network element on the main server using the IP Discovery tool installed on the main server

Network element configurationUse Procedure 28 to configure the Policy Services SNMP agent to communicate with the main server.


• the IP address of the Policy Services server

• the password for the root user on the Policy Services server

• the installation path for the Policy Services software on the Policy Services server


Procedure 28:Configuring SNMP for Policy Services

Step Action

1 Login to the Policy Services server using the root user Id.

2 Abort the EMANATE Master Agent snmpdm by typing the following commands:

ps -ef|grep snmpd

A list of processes is displayed.

kill <pid>

where <pid> is the process ID associated with /<PS_HOME>/bin/snmpdm

where <PS_HOME> is the installation path for the Policy Services server software.

—sheet 1 of 3—


Nortel Networks Confidential MetaSolv Policy Services DNS/DHCP 59

3 Modify the snmpd.cnf file in the /<PS_HOME/>conf/ directory. Replace the default public values in the following entries with private values:

• snmpCommunityEntry

• vacmSecurityToGroupEntry

• snmpTargetParamsEntry

4 Locate the snmpTargetAddrEntry field, follow the pattern, and add more entries. The first entry is generated at network element installation time. Add additional SNMP manager entries (MDM or main server IP address), following the same syntax. The following lines are examples:

snmpTargetAddrEntry Destination1 snmpUDPDomain <HostAddress>:0 100 1 TrapSink \

v2cPSParams nonVolatile 255.255.255.255:0 2048

snmpTargetAddrEntry Destination2 snmpUDPDomain <TrapDestinationAddress>:0 100 1 TrapSink \

v2cPSParams nonVolatile 255.255.255.255:0 2048

where <TrapDestinationAddress> is the main server IP address.

Note: The new entry must follow the same syntax with the first entry, including the new line character "\". After the process is restarted, Policy Services verifies the snmpd.cnf file. If file contains lines with incorrect syntax, Policy Services attempts to correct file or even delete the lines. This can cause the Policy Services configuration to fail.

5 Save and close the file.

Procedure 28:Configuring SNMP for Policy Services (continued)

Step Action

—sheet 2 of 3—



Network element discoveryUse Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the Policy Services network element. Use idi_PS as the value for the Discover As field.

VerificationPerform Procedure 29 to shut down the monitor. All processes managed by the monitor will send out an alarm.


• the IP address of the Policy Services Server

• the password for the root user on the Policy Services Server

• the installation path for the Policy Services software on the Policy Services server


6 Start monitord. Type:

cd /<PS_HOME>/bin

where <PS_Home> is the installation path for the Policy Services server software.

If you are configuring a network element with Policy Services v4.2 SP2, type:

./pps stop

./pps start

If you are configuring a network element with Policy Services v5.2 SP1 or v5.3, type:

./mps stop

./mps start

You are finished configuring the DNS or DHCP host to communicate with the main server.

Procedure 28:Configuring SNMP for Policy Services (continued)

Step Action

—sheet 3 of 3—


Nortel Networks Confidential MetaSolv Policy Services DNS/DHCP 61

Restrictions and limitationsOn the IP Discovery tool, the SNMP version shown is the version of SNMP initially used for polling messages. This version defaults to SNMPv1. When the first SNMPv2c trap comes in, the SNMP version shown in the IP Discovery tool automatically updates to SNMPv2c.

DeletionTo delete the Policy Services network element from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the PS network element from the main server. Remove the main server IP address from the snmpd.cnf file.

Procedure 29:Generating an alarm on a Policy Services server

Step Action

1 Telnet and login to the Policy Services server using the root user Id.


cd /<PS_HOME>/bin

where <PS_HOME> is the installation path for the Policy Services server software.

3 Stop the monitor. If you are configuring a network element with Policy Services v4.2 SP2, type:

./pps stop


./mps stop

4 In NSP, open the layout with the Policy Services (DNS/DHCP) host, highlight the Policy Services (DNS/DHCP) host, right-click on Show alarms to open the NSP Alarm Manager. Verify that all processes managed by the monitor which sent out an alarm when you shut down monitor appear in the alarm lists.

5 Start the monitor. If you are configuring a network element with Policy Services v4.2 SP2, type:

./pps start


./mps start

You are finished verifying that the Policy Services network element communicates with the main server.



Mobile Location Center 3This section explains how to configure, discover, verify, and delete the Mobile Location Center (MLC).

Network element integration summaryTo make the MLC communicate with the main server, you must perform the following procedures:

1. configure the MLC NMA to send unsolicited SNMP traps to the server

2. if a non-standard SNMP port or read community string is configured on the MLC, configure the appropriate network setting in MDM

3. use the dcdAddNode and dcdAddAddress scripts to enroll the network element on the main server

Network element configurationUse Procedure 30 to configure the MLC to communicate with the main server. If you want to change the community string on the MLC, contact Nortel technical support.


• IP address of the MLC database server

• an MLC user Id and password that has NMA registration and deregistration privileges


Procedure 30:Configuring the MLC

Step Action

1 Start a web browser.

2 Enter the URL for the web interface of the MLC database server:

http://<IP_Address>:8080/oamp/login.jsp

where <IP_Address> is the IP address of the MLC database server

3 Enter Username and Password.

4 Click on the Operations link from the Main Menu.

5 Click on the Network Management Station Administration link from the Operations menu. The browser displays the Network Management Station Administration page.

—sheet 1 of 2—


Nortel Networks Confidential Mobile Location Center 63

Network element discovery and main server configurationUse Procedure 135 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the MLC on the main server. Refer to the GMLC/SMLC Product Description and Deployment Guide, 411-2142-105, for descriptions of the VIP and NAT addresses. You must use the OAM VIP and OAM NAT to enroll the network element.

VerificationPerform Procedure 31 to generate a trap from the MLC. The alarm appears in the NSP Alarm Manager. To perform this procedure you must have physical access to the network element.


• ensure that both power supplies of the Ethernet Routing Switch 8600 node in the MLC are working

• know a valid user ID and password for NSP

6 Click on the Add a Network Management Station link. The browser displays the Add a Network Management Station page.

7 Enter the main server IP address in the IP address field.

8 Enter 162 in the Port field. This is the main server listener port for SNMP traps.

9 Check the Log, Alarm and Audit boxes.

10 Check your entries and click on the Register button to submit the information.

11 If the changes are correct, click on the OK button. The browser displays the Confirmation page confirming that the registration has been successful.

12 If the changes are incorrect, click on the Modify button to change the information and click on the Create button to submit the changes.

13 Click on the Return to Network Management Station link to return to the Network Management Station page.

14 Log off of the MLC.

You are finished configuring the MLC to communicate with the main server.

Procedure 30:Configuring the MLC (continued)

Step Action

—sheet 2 of 2—




DeletionPerform Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the MLC from the main server. Remove the main server IP address from the SNMP Configuration Menu of the MLC.

Procedure 31:Generating an alarm on the MLC

Step Action

1 Turn off one of the Ethernet Routing Switch 8600 power supplies.

2 Log into NSP and open a network layout containing the MLC.

3 Select the MLC, right-click on the MLC, and then select Show Alarms to open the NSP Alarm Manager window.

4 Verify that an alarm with ID resmon55 appears in the alarm list.

5 Turn the Ethernet Routing Switch 8600 power supply on.

The alarm is cleared from the Alarm Manager.

You are finished verifying that the MLC communicates with the main server.


Nortel Networks Confidential Multiservice Switch 7400, 15000, 20000, AN, MGW, IWF 65

Multiservice Switch 7400, 15000, 20000, AN, MGW, IWF 3This section explains how to configure, discover, verify, and delete Multiservice Switches. Note that the MGW 3.0.1 shows up in NSP as WG.


• the IP address and root password of the main server

• the IP address of the Multiservice Switch network elements

• the user Id and password of the Multiservice Switch network elements

• the password for the Admin user for Preside MDM on the main server

Network element integration summaryTo make the Multiservice Switch communicate with the main server, you must enroll the Multiservice Switch on the main server using the MDM tools installed on the main server.

Network element configurationThe correct user Ids and passwords must be configured on the Multiservice Switch network elements. This is performed during the installation and commissioning of the Multiservice Switch network elements. The user Ids and passwords must be defined to support the creation of appropriate Multiservice Switch groups. For example, the MDP user Id must have debug impact. If appropriate user Ids and passwords have not been defined, refer to the Preside MDM Administrator Guide, 241-6001-303, for more information on Multiservice Switch groups.

Network element discovery and main server configurationUse Procedure 138 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to enroll the Multiservice Switch on the main server.

If the Multiservice Switch is an AN, MGW, or IWF, use Procedure 138 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to enroll the Multiservice Switch on the main server and then use Procedure 140 to designate the special configuration for the network element.

VerificationConsult your local Multiservice Switch expert for a non service-affecting procedure for generating an alarm on the Multiservice Switch.



DeletionUse Procedure 142 located in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the Multiservice Switch from the main server.



Nortel Networks Confidential Net Guardian 67

Net Guardian 3This section explains how to configure, discover, verify, and delete the Net Guardian.

Network element integration summaryTo make the Net Guardian communicate with the main server, you must:

1. configure the Net Guardian SNMP agent to send traps to the main server

2. enroll the Net Guardian (NETG) on the main server using the IP Discovery tool installed on the main server

Network element configurationPerform Procedure 32 to configure the Net Guardian SNMP agent to communicate with the main server.

There is more than one way to configure the Net Guardian to send traps in response to alarm conditions. This procedure assumes that you want to send traps to multiple destinations.


• the IP address of the Net Guardian

• the password for the Net Guardian Web Client

• Get community string, Trap community string (these must have the same value and the value must not be "public")

• Set community string (value must not be "public")

Procedure 32:Configuring the Net Guardian

Step Action

1 Open a web browser. Type in the URL http: //<IP address of Net Guardian> to launch the Net Guardian Web Client page.

2 Type the password for the Net Guardian Web Client and click on the Submit button to log in.

3 Click on Edit on the left side of the page.

4 Under System, type community string values for the following fields:

a. Get

b. Set

c. Trap

—sheet 1 of 2—



Network element discoveryUse Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the Net Guardian on the main server. Do not use idi_NETG as the value for the Discover As field, except if the device type cannot be determined using normal IP Discovery methods.

VerificationUse Procedure 33 to generate an alarm on Net Guardian. The alarm appears in the NSP Alarm Manager.


• the IP address of the Net Guardian

• the password for the Net Guardian Web Client


5 Scroll down to bottom of the page and click on the Submit Data button.

The following message appears: All Data Successfully Submitted. NvRam write in progress.

6 Click on the OK button on the message dialog.

7 Click on Reboot.

8 Click on Logout to log out of the Net Guardian Web Client.

You are finished configuring the Net Guardian to communicate with the main server.

Procedure 33:Generating an alarm on the Net Guardian

Step Action

1 Open a web browser. Type in http: //<IP address of Net Guardian> in the URL to launch the NETG Web Client page.

2 Enter <password> of Net Guardian Web Client and click Submit button to log in.

—sheet 1 of 2—

Procedure 32:Configuring the Net Guardian (continued)

Step Action

—sheet 2 of 2—


Nortel Networks Confidential Net Guardian 69


DeletionPerform Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the NETG network element from the main server. Refer to the Net Guardian network element integration procedure for the location of the trap destination information on the Net Guardian. Delete all references to the SNMP pager that points to the main server and then delete the SNMP pager definition.

3 Click on the green Edit button at the bottom of the menu on the left hand side of the page, then under Edit menu, click Base Alarms.

4 In the Base Alarms page, find an alarm point that you would expect to be inactive and which has only the SNMP pager you set up listed as an associated pager.

5 For the alarm you selected, set the Polarity to Reversed, check the Trap check box, scroll down to bottom and click Submit Data button.


All Data Successfully Submitted. NvRam write in progress.


7 In NSP, open the layout with this Net Guardian (NETG), highlight the NETG, right-click and select Show alarms to open NSP alarm manager, verify alarms appear.

8 In the Base Alarms page, reset the Polarity and Trap check box to what they were originally. Scroll down to the bottom and click on the Submit Data button. The following message appears:

All Data Successfully Submitted. NvRam write in progress.


10 Click on the Logout button to log out of the NETG Web Client.

You are finished verifying that the Net Guardian communicates with the main server.

Procedure 33:Generating an alarm on the Net Guardian (continued)

Step Action

—sheet 2 of 2—



Ethernet Routing Switch 8600 3This section explains how to configure, discover, verify, and delete the Ethernet Routing Switch 8600.

Network element integration summaryTo make the network element communicate with the main server, you must perform the following procedures:

1. configure the network element SNMP agent to send traps to the main server

2. enroll the network element on the main server using the IP Discovery tool installed on the main server

Network element configurationPerform Procedure 34 to configure the Passport SNMP agent to communicate with the main server.


• the IP address of the Ethernet Routing Switch 8600

• the password for the rwa user on the Passport

• community string configured with READ access on the network element

Procedure 34:Configuring the Ethernet Routing Switch 8600

Step Action

1 Open a telnet window to one of the Passport IP addresses.

2 Log in using user ID rwa.


config

4 If you are configuring an Ethernet Routing Switch 8600 with version 3.7 software, go to step 9.

5 If you are configuring an Ethernet Routing Switch 8600 with version 3.2.3 or 3.5 software, go to step 6.

—sheet 1 of 2—


Nortel Networks Confidential Ethernet Routing Switch 8600 71

6 Type:

sys set snmp community rwa <community string>

where <community string> is a community string configured with READ access on the network element

7 Type:

sys set snmp trap-recv <IP_Address> <SNMP version> <community string>

where <IP_Address> is the IP address of the main server, <SNMP version> is one of v1 or v2c, and <community string> is the community string configured with READ access on the network element

8 Go to step 11.

9 To configure the community string, type:

snmp-v3 community create <Comm Idx> <name> <security> [tag <value>]

where <Comm Idx> is the community index of length 1 to 32, <name> is the community name of length 1 to 32, <security> is the security name of length 1 to 32

where tag <value> is an optional parameter and <value> is the transport tag name of length 1 to 32.

10 To configure the trap receiver, type:

snmp-v3 target-addr create <Target Name> <Ip addr:port> <Target parm> [timeout <value>] [retry <value>] [taglist <value>] [mask <value>] [mms <value>]

where <Target Name> is the target name of length 1 to 32, <Ip addr:port> is the target address e.g.(1.2.3.4:161) of length 1 to 32, <Target parm> is the target parameter of length 1 to 32

where the following are optional parameters: timeout <value> is the timeout value of 1 to 2147483647, retry <value> is the retry count value from 1 to 255, taglist <value> is the tag list of length 1 to 255, mask <value> is a mask {0x00:00...} of length 1 to 255, mms <value> is the maximum message size value from 1 to 2147483647

11 Log out of the network element:

logout

You are finished configuring the Ethernet Routing Switch 8600 to communicate with the main server.

Procedure 34:Configuring the Ethernet Routing Switch 8600 (continued)

Step Action

—sheet 2 of 2—



Network element discoveryDiscover the network element using Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures”.

VerificationPerform Procedure 35 to generate a login authentication failure trap. The alarm appears in the NSP Alarm Manager. If you perform this procedure incorrectly, you will not be able to log into the network element for five minutes while a security timer expires.


• IP address of the Ethernet Routing Switch 8600

• a user ID and password on the Passport

• a user ID and password for NSP

Procedure 35:Generating an alarm on the Ethernet Routing Switch 8600

Step Action

1 Open a telnet window to any of the Passport IP addresses and log in.

2 Type:

config sys set sendAuthenticationTrap true

This command enables the authentication functionality.

3 Log off.

4 Attempt to log in twice with an invalid User ID and password.

5 Log into the Ethernet Routing Switch 8600 using a valid user ID and password.

6 Log off.

7 Repeat step 1 through step 6 two more times, for a total six failed log in attempts.

8 In NSP, open a layout containing the network element. Right-click on the network element and select Show Alarms from the object menu to open the Alarm Manager window. Verify that you see a login authentication failure alarm in the alarm list.

You are finished verifying that the Ethernet Routing Switch 8600 is sending traps to the main server.


Nortel Networks Confidential Ethernet Routing Switch 8600 73


DeletionTo delete the Ethernet Routing Switch 8600 from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the network element from the main server. Refer to the Ethernet Routing Switch 8600 configuration procedure and use the set snmp del-trap-recv <IP_address> command to remove the main server IP address from the SNMP Configuration Menu of the Ethernet Routing Switch 8600.



Service Location Register 3The Service Location Register (SLR) uses the same software as the USP-based UNPM. To configure the SLR, use the procedures for the USP-based UNPM. See “USP-based Universal Number Portability Master”.


Nortel Networks Confidential SGSN/UMTS, SGSN/GPRS 75

SGSN/UMTS, SGSN/GPRS 3This section explains how to configure, discover, verify, and delete the SGSN.


• the IP address and root password of the main server

• the IP address of the SGSN

• the user Id and password of the SGSN

• the admin password for Preside MDM on the main server

Network element integration summaryThe SGSN consists of multiple Multiservice Switch 15000 network elements. To make these network elements communicate with the main server, you must enroll all of the Multiservice Switches that make up the network element on the main server using HGDS.cfg configuration file on the main server. You must then restart the mdm_primary application group.

Network element configurationThe correct user Ids and passwords must be configured on the Multiservice Switch network elements. This is performed during the installation and commissioning of the Multiservice Switch network elements. The user Ids and passwords must be defined to support the creation of appropriate Multiservice Switch groups. If appropriate user Ids and passwords have not been defined, refer to the Preside MDM Administrator Guide, 241-6001-303, for more information on Multiservice Switch groups.

Main server configurationPerform Procedure 138 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to enroll the Multiservice Switch on the main server. Perform Procedure 139 to group the individual Multiservice Switch network element icons into a single SGSN. Grouping the Multiservice Switches into one network element allows you access to the network element through the Wireless Internet Command Language (WICL).

VerificationConsult your local SGSN expert for a non service-affecting procedure to generate an alarm on the network element.

DeletionPerform Procedure 142 located in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the network element from the main server.




Signalling Gateway 3The following table shows the possible configurations of the Signalling Gateway (SGW) and the corresponding configuration procedure:

Table 1:SGW configurations

Description Configuration procedure

SGW based on USP 10.0(standalone SGW)

see “USP-based Universal Number Portability Master”

SGW based on USP 10.0 combined with an MSC

see “HLR 100, HLR 200, MSC, combined MSC/HLR, or Signaling Gateway”


Nortel Networks Confidential SS7 IP Gateway 77

SS7 IP Gateway 3This section explains how to configure, discover, verify, and delete the SS7 IP Gateway (SIG).

Network element integration summaryTo make the SIG communicate with the main server, you must perform the following procedures:

1. Configure the SIG SNMP agent to send traps to the main server. (Procedure 36 for SIG 4.0 or Procedure 37 for SIG 5.0 or 6.0)

2. Enroll the SIG network element on the main server using the IP Discovery tool on the main server.

Network element configurationPerform Procedure 36 to configure the SIG SNMP agent to communicate with the main server for the SIG 4.0. This procedure configures the community string used by the SIG network element.


• the IP address of the SIG

• the password for the root user on the SIG

• IP address of the main server

Procedure 36:Configuring the SIG 4.0

Step Action

1 Telnet and login to the SIG using the root user ID.

2 Change to the snmp agent directory:

cd /etc/SnmpAgent.d

3 Use a text editor to edit the snmp configuration file:

vi snmpd.conf

—sheet 1 of 2—



Perform Procedure 37 to configure the SIG SNMP agent to communicate with the main server for the SIG 5.0 or SIG 6.0.


• if you are configuring an NE with SIG 5.0, ensure snmp version 15.3 and SNMP Patch PHSS_29299 have been installed on the SIG

• if you are configuring an NE with SIG 6.0, ensure snmp version 15.3 and SNMP Patch PHSS_30687 have been installed on the SIG

• know the password for the root user on the SIG

• know the IP address of the SIG

• know the IP address of the main server

• know the community string for the SIG (must not be "public")

4 Add the following entry to the snmpd.conf file to configure the main server on the SIG device to receive traps:

trap_dest: <IP_address>

where <IP_address> is the main server IP address.

Note: The maximum permissible of trap destinations in the snmpd.conf file is 20. If there are more than 20 destination IP addresses in the snmpd.conf file, remove any unnecessary trap destinations.

5 Look for the line that contains the get-community-name variable. Change the line as shown:

get-community-name: <community string>

where <community string> is sendtrap.

6 Save the snmpd.conf file.

7 Shut down and restart the SIG:

/sbin/shutdown -r -y 0

You have finished configuring the SIG to communicate with the main server.

Procedure 36:Configuring the SIG 4.0 (continued)

Step Action

—sheet 2 of 2—



Procedure 37:Configuring the SIG 5.0, 6.0

Step Action

1 Telnet and login to the SIG using the root user ID.

2 Change to the snmp agent directory: cd /etc/SnmpAgent.d

3 Use a text editor to edit the snmp configuration file:

vi snmpd.conf

4 Look for the line that contains the get-community-name variable. Change the line as shown:

get-community-name: public IP: <Local IP Address>

where <Local IP Address> is the IP address of the SIG

5 Change the following lines as shown:

snmpCommunityEntry 31 <community string> <community string> localSnmpID - Console nonVolatile

vacmViewTreeFamilyEntry All iso - included nonVolatile

vacmAccessEntry myV1Group - snmpv1 noAuthNoPriv exact All All All nonVolatile

vacmSecurityToGroupEntry snmpv1 <community string> myV1Group nonVolatile snmpNotifyEntry 31 Console trap nonVolatile

snmpTargetAddrEntry myV1Manager_allRequests snmpUDPDomain <IP Address>:0 100 3 Console myV1ExampleParams nonVolatile 255.255.255.255:0

snmpTargetParamsEntry myV1ExampleParams 0 snmpv1 <community string> noAuthNoPriv nonVolatile

where <community string> is a community string and <IP address> is the IP address of the main server

6 Save the snmpd.conf file.

—sheet 1 of 2—



Network element discoveryUse Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the SIG on the main server. Use SIG as the value for the Discover As field.

Some SIG installations have two static IP addresses and one relocateable (also known as floating) IP address. Discover both static addresses. Do not discover the floating IP address.

VerificationPerform Procedure 38 to generate an alarm with faultCode C1200101. The alarm appears in the NSP Alarm Manager.


• a user ID and password for the SIG


7 Restart the snmpd master and subagents. Enter the following commands:

/sbin/init.d/SnmpMib2 stop

/sbin/init.d/SnmpTrpDst stop

/sbin/init.d/SnmpHpunix stop

/sbin/init.d/SnmpMaster stop

/sbin/init.d/SnmpMaster start

/sbin/init.d/SnmpMib2 start

/sbin/init.d/SnmpTrpDst start

/sbin/init.d/SnmpHpunix start

8 Check /var/adm/snmpd.log to make sure that the restart worked.

You have finished configuring the SIG to communicate with the main server.

Procedure 37:Configuring the SIG 5.0, 6.0 (continued)

Step Action

—sheet 2 of 2—



Procedure 38:Generating an alarm on the SIG

Step Action


2 Start the System Administration Manager on the SIG:

a. log into the SIG using telnet

b. set the DISPLAY variable to point to your workstation. Refer to the W-NMS Operator Guide, 411-5221-505 for information about how to set the DISPLAY variable.

c. change the directory to /usr/sbin: cd /usr/sbin

d. execute “sam” to open System Administration Manager: ./sam &

The System Administration Manager appears in the Exceed window.

3 From the System Administration Manager, double click on Resource Management icon

4 Double click on Event Monitoring Service icon.

An Event Monitoring Service window opens.

5 If a resource is available, then go to step 7; if a resource is not available, go to step 6.

6 Create a resource:

a. From the Event Monitoring Service window, click on Actions from the menu bar, then select Add Monitoring Request….

An Add or Copy Monitoring Request window opens.

b. Double click on Resource Classes to navigate the resource hierarchy.

c. Continue to double click on Resource Classes until some instances appear in the Resource Instances box.

d. Select one of the instances and click on the OK button.

—sheet 1 of 2—




DeletionTo delete the SIG from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the SIG network element from the main server. Remove the main server IP address from the SNMP Configuration Menu of the SIG.

7 Configure a resource to produce an alarm:

a. Double click on the resource.

A Monitoring Request Parameter window appears.

b. From the Notify label, select when value is … from the first pull down menu, and Not equal from the second pull down menu.

c. From the Severity label, select one of the severity levels.

d. From the Options level, put check marks in Initial, Repeat, and Return check boxes.

e. Click on OK button.

A “Note” window pops up.

f. Click on the OK button.

8 In NSP, open the layout that has the SIG. Point to the SIG, right-click on it, and then select Show alarms to open the alarm manager window. Check that the alarm with the selected severity and resource name is displayed in the alarm’s description appears in the alarm list.

9 To clear the alarm, un-configure the resource you configured in step 7.

You are finished verifying that the SIG communicates with the main server.

Procedure 38:Generating an alarm on the SIG (continued)

Step Action

—sheet 2 of 2—


Nortel Networks Confidential Universal Number Portability Master 83

Universal Number Portability Master 3This section explains how to configure, discover, verify, and delete the Universal Number Portability Master.

This procedure applies to Universal Number Portability Master (UNPM) version SSR3.4.8 and SNMP v2c. To configure the UNPM that uses USP software, see “USP-based Universal Number Portability Master”.

Network element integration summaryTo make the UNPM communicate with the main server, you must perform the following procedures:

1. configure the UNPM SNMP agent to send traps to the main server

2. enroll the UNPM on the main server using the dcdAddNode command line on the main server (Do not use the IP Discovery tool.)

Network element configurationUse Procedure 39 to configure the UNPM SNMP agent to communicate with the main server. In this procedure, the community string FIELD has been configured with READ access.


• the user Id and password of the UNPM

• the host name and IP address of the main server

• community string for the UNPM (do not use "public")

You must have access the Broadband STP client.

Procedure 39:Configuring the UNPM SNMP agent

Step Action

1 Launch the UNPM client by selecting Start, Programs, Broadband STP and then Broadband STP

2 Select the appropriate UNPM site and enter a valid userid and password. Click on the Connect button.

3 Select Administration and then SNMP.

—sheet 1 of 2—



Network element discoveryPerform Procedure 40 to discover the UNPM on the main server. This procedure uses the dcdAddNode command to discover the UNPM. Do not use the IP Discovery tool to discover this network element. If the UNPM is redundant, perform the discovery once for each IP address.

Prerequisites Before performing Procedure 40 you must know:

• a user ID and password on the main server that has MDM administration privileges

• the IP addresses of the UNPM (both active and inactive RTCs)

4 In the SNMP Administration window, type the main server name in the Manager Name field.

5 Type the main server IP Address in the Manager IP Address field.

6 Type the community string in the SNMP Notification User Name field.

7 Type the same community string in the SNMP Get/Set User Name field.

8 Select the desired SNMP protocol version (v2c) and click on the Apply button.

9 When the SNMP settings have been applied, click Apply and Close on the main toolbar to terminate the connection to the UNPM.

You are finished configuring the UNPM SNMP agent to communicate with the main server.

Procedure 40:Discover the UNPM

Step Action

1 Log into the main server as a user with MDM administration privileges.

2 Type:


—sheet 1 of 2—

Procedure 39:Configuring the UNPM SNMP agent (continued)

Step Action

—sheet 2 of 2—


Nortel Networks Confidential Universal Number Portability Master 85

VerificationIf there are active alarms on the UNPM, use Procedure 41 to resend the current alarm states to the main server. If there are no active alarms on the UNPM, consult your local UNPM expert to generate a non-service affecting trap on the UNPM that will be forwarded to the main server.

3 Type:

./dcdAddNode

The following usage message displays:

dcdAddNode <devType> <devName> <addr> <community> <port> <devTypeNum>

4 Type:

./dcdAddNode UNPM <devName> <addr> FIELD 161 178

where <devName> is an alphanumeric name for the network element and <addr> is the IP address of the UNPM.

You are finished discovering the UNPM.

Procedure 41:Generating an alarm on the UNPM

Step Action

1 From the PC, launch the UNPM client by selecting Start, Programs, Broadband STP and then Broadband STP.

2 Select the appropriate UNPM site and enter a valid userid and password. Click on the Connect button.

3 Click on System Management on the tool bar at the bottom of the window.

The System Configuration window displays.

4 Click MODIFY.

Do not change the value of SYSTEM NAME. Clicking on the MODIFY button triggers a re-send of all trap information associated with outstanding alarms on the network element.

—sheet 1 of 2—

Procedure 40:Discover the UNPM (continued)

Step Action

—sheet 2 of 2—



Restrictions and limitationsYou must use the dcdAddNode command to integrate the UNPM network element to the main server to properly discover the two SNMP agents present on the UNPM when the UNPM is running in redundant mode.

DeletionTo delete the UNPM from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the UNPM from the main server. Refer to the UNPM configuration procedure and remove all references to the main server IP address from the SNMP settings list on the UNPM.

5 In NSP, open a layout containing the UNPM. Select the UNPM, right-click and select Show Alarms from the pop-up menu to open the Alarm Manager. Verify that the outstanding alarms on the UNPM appear in the Alarm List.

You are finished verifying that the UNPM communicates with the main server.

Procedure 41:Generating an alarm on the UNPM (continued)

Step Action

—sheet 2 of 2—


Nortel Networks Confidential USP-based Universal Number Portability Master 87

USP-based Universal Number Portability Master 3Perform the procedures in this section for the Universal Number Portability Master (UNPM) network element that uses USP 8.0 or USP 10.0. Upon completion of the procedures in this section, W-NMS receives fault data from the UNPM.

The procedures in this section also apply for the standalone SGW and the SLR.

To configure the UNPM, perform the following procedures in the order listed:

• Procedure 42: Configuring the USP-based UNPM

• Procedure 43: Adding the USP-based UNPM to a network layout

Configuring the USP-based UNPMThis procedure configures the UNPM using the coreEMS Commissioning Manager.


• a user Id and password for the main server that has permission to run the coreEMS Commissioning Manager

• the following information for the UNPM network element:

— target IP address (RTC-12 IP address)

— secondary IP address (RTC-15 IP address)

— user ID

— user password

— FTP user ID

— FTP user password

Procedure 42:Configuring the USP-based UNPM

Step Action


2 Set the DISPLAY variable to the IP address of your workstation. Refer to the W-NMS Operator Guide, 411-5221-505 for more information.

—sheet 1 of 3—





4 Type:

./configCEMS &

5 In the coreEMS Commissioning Manager window, Node Configuration tab:

a. In the Command field, select Create from the drop-down list, if it is not already displayed.

b. In the Device Type field, select USP_NES from the drop-down list.

c. In the Element Name field, enter a text string consisting of up to 15 characters drawn from the alphabet (a-z), digits (0-9) and minus sign (-). The first character must be an alpha character and the last character must not be a minus sign.

d. Do not change the Region field.

e. Do not change the Software Release field.

6 Click on the field under USP_TYPES and select one of the following items from the drop-down list:

• UNPM, if you are configuring a UNPM network element

• SLR, if you are configuring an SLR network element

• SGW, if you are configuring an SGW network element

7 Enter the following fields by clicking on the blank space under the field and typing in it:

a. Target IP Address

b. Secondary IP Address

c. User ID

d. User Password

e. FTP User ID

f. FTP User Password

8 Click on Submit.

9 In the Confirm Your Action box that appears, click on Yes.

10 In the Message box that appears, click on OK.

11 In the Message box that appears, click on Yes.


13 Verify that the new node appears under USP_NES in the Navigator on the right side of the window.

Procedure 42:Configuring the USP-based UNPM (continued)

Step Action

—sheet 2 of 3—


Nortel Networks Confidential USP-based Universal Number Portability Master 89

Adding the USP-based UNPM to a network layoutThis procedure adds the UNPM network element to a network layout in the Network Services Platform by adding it to a group.



• a user Id and password for the Network Services Platform

14 In the coreEMS Commissioning Manager window, click on Exit.

You are finished configuring the UNPM. Continue on to Procedure 43: Adding the USP-based UNPM to a network layout.

Procedure 43:Adding the USP-based UNPM to a network layout

Step Action

1 Start the Network Services Platform on the main server. For information about how to do this, see the Wireless Network Management System OAM Operator Guide, 411-5221-505.

2 Add the UNPM network element to a network layout by adding it to a group. You can find information about grouping network elements in the Wireless Network Management System Network Services Platform User Guide, 411-5221-211.

3 Verify that the UNPM is enrolled in the CEM and that it appears as a subcomponent of the Universal Number Portability Master.

You are finished adding the UNPM to a network layout.

Procedure 42:Configuring the USP-based UNPM (continued)

Step Action

—sheet 3 of 3—



Deleting the USP-based UNPMUse this procedure to delete the UNPM from the W-NMS. This procedure also applies for the standalone SGW and the SLR.

PrerequisitesBefore performing this procedure you must know a user Id and password for the main server that has permission to run the coreEMS Commissioning Manager.

Procedure 44:Deleting the USP-based UNPM

Step Action


2 Set the DISPLAY variable to point to the client workstation. Refer to the W-NMS Operator Guide, 411-5221-505 for more information.

3 Type:


4 Type:

./configCEMS &

5 In the coreEMS Commissioning Manager, in the Navigator pane, expand the USP_NES folder.

6 Click on the node that contains the UNPM that you want to delete.

7 In the Command field, select Delete from the drop-down list.

8 Click on Submit.

9 In the Warning message box that appears, click on OK.

If the server is busy, an Information window appears showing the time left to complete the deletion. Wait for it to close before performing the next step.


11 In the coreEMS Commissioning Manager window, click on Exit.

12 Verify that the UNPM has been removed from NSP and the CEM.

You are finished deleting the UNPM from W-NMS.


Nortel Networks Confidential VPN Router 91

VPN Router 3The VPN Router includes the:

• VPN Router 600

• VPN Router 1010/1050/1100

• VPN Router 1500, 2500, 4500

• VPN Router 1600/2600/4600

• VPN Router 1700/2700

Network element integration summaryTo make the VPN Router communicate with the main server, you must perform the following procedures:

1. configure the VPN Router SNMP agent to send traps to the main server

2. enroll the VPN Router network element on the main server using the IP Discovery tool installed on the main server

Network element configurationThe procedure to configure the VPN Router is the same as the procedure to configure the Border Gateway. See Procedure 4.

Network element discoveryDiscover the network element using Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the VPN Router on the main server. Use idi_vpn as the value for the Discover As field.

VerificationThe procedure to verify that the VPN Router has been configured correctly is the same as the procedure for the Border Gateway. Perform Procedure 5 as described , but instead of logging into a VPN Router, log into a Border Gateway.


DeletionTo remove the VPN Router network element from W-NMS, perform Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete the VPN Router network element from the main server. Refer to the VPN Router configuration procedure and remove all reference to the main server IP address from the SNMP Configuration Menu of the VPN Router.



Web Switch 184 3To make the Nortel Web Switch 184 communicate with the main server, you must perform the following procedures:

1. configure the Web Switch 184 SNMP agent to send traps to the main server

2. enroll the Web Switch 184 on the main server using the IP Discovery tool installed on the main server

Configuring the Web Switch 184Use Procedure 45 to configure the Web Switch 184 SNMP agent to communicate with the main server.

PrerequisitesBefore performing this procedure you must know the following information about the Web Switch 184 you are configuring:

• the IP address of the main server that the Web Switch 184 is connected to

• the IP address of the Web Switch 184

• the admin password of the Web Switch 184

• write community string

• read community string, first trap destination community string, second trap destination community string (the values for these community strings must be the same)

Do not use "public" as the value for any of the community strings.

Procedure 45:Configuring the Web Switch 184

Step Action

1 Telnet and log into the Web Switch 184.

2 Type the following command to modify the first SNMP trap destination to the IP address of the main server:

/cfg/snmp/trap1 <main server IP address>

3 Type the following command to modify the second SNMP trap destination to the IP address of the main server:

/cfg/snmp/trap2 <main server IP address>

—sheet 1 of 2—


Nortel Networks Confidential Web Switch 184 93

Network element discoveryUse Procedure 134 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to discover the Web Switch 184 on the main server. Use idi_alteon as the value for the Discover As field.

VerificationUse the same procedure as for the Applications Swtich (Procedure 2) to generate an authentication failure alarm on the Web Switch 184.

4 Type the following command to modify the read community string:

/cfg/snmp/rcomm <read community string>

5 Type the following command to modify the write community string:

/cfg/snmp/wcomm <write community string>

6 Type the following command to modify the community string used in trap sending to the first trap destination:

/cfg/snmp/t1comm <trap1 community string>

7 Type the following command to modify the community string used in trap sending to the second trap destination:

/cfg/snmp/t2comm <trap2 community string>


apply

save


Request will first copy the FLASH "active" config to "backup",then overlay FLASH "active" with new config.Confirm saving to FLASH [y/n]:

9 Type:

y

10 Type:

exit

You are finished configuring the Web Switch 184 to communicate with the main server.

Procedure 45:Configuring the Web Switch 184 (continued)

Step Action

—sheet 2 of 2—




DeletionTo delete the Web Switch 184 from W-NMS, use Procedure 137 in “Appendix A: SNMP and Multiservice Switch-based network element procedures” to delete it from the main server. Remove the main server IP address from the SNMP Configuration Menu of the Web Switch 184.

3



Alarm on threshold 4Alarm on threshold is a feature of W-NMS that generates an alarm based on performance management data. Performance data is collected on the both the main server and the performance server and forwarded to the Core Element Manager (CEM) performance data archive on the main server. A value is calculated using performance management counters contained in the archive (observed value). If the observed value crosses a predetermined threshold (threshold value) an alarm is raised in the Alarm Manager of the Network Services Platform. Alarms are raised at the end of a performance measurement granularity period. Alarm on threshold provides alarms on user defined thresholds for the following network elements:

• HLR 100, HLR 200, combined MSC/HLR

• SLR

• UNPM

• Media Gateway

• SGSN

• Interworking Function (IWF)

• GGSN

• SS7 IP Gateway (SIG)

For information about defining alarm thresholds see the GSM NSS/UMTS VCN OAM Manual, 411-8111-503.

The GPRS SGSN alarms A7068 001 and A7068 002 have preconfigured thresholds. The alarms are disabled at installation time, so you must use the CEM to enable them.

Troubleshooting threshold alarmsThreshold alarms are raised for specific network elements. The cause of the alarm can be due to network conditions and not a problem with the network element itself.


96 Alarm on threshold Nortel Networks Confidential

Configuring alarm on threshold 4Perform the following procedures to enable alarm on threshold:

• Connecting the performance server to the main server

• Configuring the MDP for a new network element or Configuring the MDP for an existing network element

• Configuring the ADC for a new network element or Configuring the ADC for an existing network element

• Configuring the threshold alarm rate

Connecting the performance server to the main serverThis procedure connects the main and performance servers together to allow the performance data to be sent to the main server.

Procedure 46:Connecting the performance server to the main server

Step Action

1 Start the Exceed server on your workstation.


3 Set the DISPLAY variable to the IP address of your workstation. Refer to the W-NMS Operator Guide, 411-5221-505 for more information.



5 Type:

./configCEMS &

6 In the coreEMS Commissioning Manager window, in the Navigator section, select Device Type MDM and then select element/slice autoinstall.


a. In the Does this MDM have performan... field, select YES from the drop-down list.

b. In the Performance Server IP Address field, type the IP address of the performance server.

8 Click on Submit.


Do you really want to submit the configuration change?

—sheet 1 of 3—


Nortel Networks Confidential Configuring alarm on threshold 97

9 Click on Yes.


Commissioning Manager has to stop all applications for this node for reconfiguration. Proceed to reconfigure the node autoinstall?

10 Click on OK.

An Information window opens with a message stating that the action may take a few minutes. It closes by itself.

When the process is complete the following message displays:

Command completed successfully!

11 Click on OK.


Start all applications for node autoinstall?

12 Click on Yes.


Applications of node autoinstall were started.

13 Click on OK.

Verifying that the processes are running on the performance server

14 Log onto the main server SMC using the nortel user Id.

15 Open the Performance Server processes and select Local Applications.

Procedure 46:Connecting the performance server to the main server (continued)

Step Action

—sheet 2 of 3—



Configuring the MDP for a new network elementIf you have a network element that you want to configure for both performance management and alarm on threshold, perform Procedure 53.

Configuring the MDP for an existing network elementIf you have an existing network element that is already configured for performance management and you want to enable alarm on threshold for it, perform Procedure 47.


• the IP address of the client workstation from which you are accessing the MDP

• the host name of the main server

• the IP address of the performance server

• the password for the nortel user ID on the performance server

16 Click on application management(mdm_perf).

Verify that the following applications are running:

• HGDS

• MDM Context Server

• MDP Data Model Manager

• MDP Disk Manager

• MDP File Mover Manager

• MDP PP File Manager

• MDP PP Prober Manager

• MNSD Agent

17 If any of the processes listed in step 16 are not running, use the SMC to start them.

18 Verify that the following directory exists on the performance server:

/opt/nortel/data/coreEMS/nodes/<host name>MDM/dataCollector/dat/bdfdata


You are finished connecting the performance server to the main server.

Procedure 46:Connecting the performance server to the main server (continued)

Step Action

—sheet 3 of 3—



Procedure 47:Configuring the MDP for an existing network element

Step Action

1 Start the Exceed server on your PC.

2 Use the SMC to verify that the HGDS process is running. If it is not running, start it.

3 Log on to the performance server using the nortel user ID.

4 In the command line, enter:

cd /opt/MagellanMDP/bin/

setenv DISPLAY <IP address>:0.0

where <IP address> is the IP address of the client workstation

5 Enter:

./gmdpconfig&

The Management Data Provider Configuration window opens in the Exceed window.

6 Click on the Passport tab.

The Passport Data Management information displays.

7 Click on the File Mover tab.

8 In the File Type drop-down list, click on Passport Statistics BDF.

9 Click on Edit Host.

—sheet 1 of 2—



10 Check that the following host exists. If not, create it:

• Hostname: IP address of the performance server

• Userid: nortel

• Password: password for the nortel user ID on the performance server

Leave the Use Shortened Names check box clear.

11 If you have created a new host, click on Save Host.

12 Click on Cancel.

13 Under Customer Host 2, click on the enabled check box.

14 In the hostname drop-down list, click on the entry that shows the IP address of the performance server and the nortel user ID.

15 Select the Set destination ftp directory check box.

16 In the field under the Set destination ftp directory check box enter:

/opt/nortel/data/coreEMS/nodes/<host name>MDM/dataCollector/dat/bdfdata


17 Click on the Save File Mover button.

18 Click on the Exit button.

19 Use the SMC to verify that the following processes are running:

• HGDS







• MNSD Agent

• Log Collector

20 If any of the processes shown in step 19 are not running, use the SMC to start them.

You have configured the MDP.

Procedure 47:Configuring the MDP for an existing network element (continued)

Step Action

—sheet 2 of 2—



Configuring the ADC for a new network elementIf you have a network element that you want to configure for both performance management and alarm on threshold, perform Procedure 64. Make sure you leave the default values for the Incoming Dir field as they are configured in Procedure 64.

Configuring the ADC for an existing network elementIf you have an existing network element that is already configured for performance management and you want to enable alarm on threshold for it, perform Procedure 48.


• the password for the nortel user on the performance server

• the collector name for each network element that you want to configure alarm on threshold for

Note: You can have only one instance of the ADC configuration tool running at one time.

Procedure 48:Configuring the ADC

Step Action

1 Log onto the performance server GUI. If you do not have direct access to a GUI on the performance server, refer to Procedure 65 to launch the ADC GUI from a W-NMS client.

2 Log on to the performance server using telnet or an xterm as nortel.

3 Enter:

cd /opt/nortel/shell/packet/adc

4 Enter:

./adcGUI&

The ASCII Data Collector Configuration - Edit Window opens.

5 Select the collector for the device that you want to configure alarm on threshold for.

6 Click on the Edit button.

The ASCII Data Collector Configuration - Registration Window opens.

—sheet 1 of 2—



Configuring the threshold alarm rateThis procedure sets the rate at which the generated threshold alarms are sent from the CEM to the Core DA. For the new rate to take effect, the procedure explains how to stop and start the dataprocessor process using the CEM Server Application Management tool. For more information about the CEM Server Application Management tool, see the GSM NSS/UMTS VCN OAM Manual, 411-8111-503.

See the Wireless Network Management System Engineering Guide, 450-3101-638, for more information on the threshold alarm rate, including the recommended value.

7 Under Collection Information, in the Incoming Dir field, add one of the following values. If there is an existing value in the field, type a comma, then type the additional value:

• for a SIG: /opt/nortel/data/coreEMS/SIGdata

• for a GGSN: /opt/nortel/data/coreEMS/GGSNdata

8 Click on the Activate button.

The ASCII Data Collector Configuration - Edit Window closes.

9 Perform step 5 through step 8 for each network element.


You are finished configuring the ADC for alarm on threshold.

Procedure 49:Configuring the threshold alarm rate

Step Action

1 Log into the main server.

2 Type:

su -root <password>

where <password> is the password for the root user Id.

—sheet 1 of 2—

Procedure 48:Configuring the ADC (continued)

Step Action

—sheet 2 of 2—



3 Edit the following file:

/opt/nortel/data/coreEMS/nodes/<element_name>/dataProcessor/dat/thresholds.cfg

where <element_name> is the MDM slice name specified when the CEM was configured.

4 In the thresholds.cfg file, look for the following line:

alarmSendRate = "<alarm rate>";

where <alarm rate> is an integer value of the alarms per second

5 Change the value of <alarm rate> to an appropriate value.

6 Save the thresholds.cfg file.

7 Log into NSP using the sdmuser Id.

8 In the Resource Browser, right-click on a core network element and select CEM -> Open from the object menu.

9 In the Nortel Element Browser (CEM), from the Administration menu, select Server Application Management.

10 In the coreEMS Application Management Tool, click on the IP address of the main server.

11 Click on the + sign beside OMC-S.

12 Click on the + sign beside mdm-main.

13 Click on, and then right-click on the line that shows the dataprocessor process, and select ManB from the object menu.

14 In the Select on Option window, click on OK.

15 Click on, and then right-click on the line that shows the dataprocessor process, and select Rts from the object menu.

16 For the dataprocessor process, ensure that the value in the State column shows InSv. If the state is not InSv, go to step 13.

17 Close the CEM.

You are finished configuring the threshold alarm rate.

Procedure 49:Configuring the threshold alarm rate (continued)

Step Action

—sheet 2 of 2—



Performance management 5This section contains procedures for configuring network elements and the performance server to enable and disable collection of performance data.

Verifying the performance server processes 5Before you configure the performance server components, there are a number of processes that must be running on the performance server. Perform this procedure to verify that the appropriate performance server processes are running. Perform this procedure before performing any of the other procedures in this chapter.


• how to use the Sun Management Center (SMC) to monitor, stop, and start processes (The System Management (SMG) solution is Nortel’s implementation of the SMC. For information about the SMG, see Wireless Network Management System System Management, 411-8111-538.)

• a user ID and password for accessing the SMC

• the IP address or node name of the primary main server

Procedure 50:Verifying the performance server processes

Step Action

1 Start the SMC client application from the Network Services Platform or use the stand-alone client application from a PC.

2 Log on to the SMC on the primary main server. If you are using the stand-alone client on a PC, you will have to enter the IP address or the node name of the primary main server when you log on.


106 Performance management Nortel Networks Confidential

3 For the performance server, verify that all processes in the following applications are running:

• Application Management (BackupRestore_perf)

• Application Management (cem_perf)

• Application Management (commonServices_perf)

• Application Management (core_perf)

• MDM Application Management (mdm_perf)

• Application Management (thirdparties_perf)

• Application Management (mycom_perf) (required only if you are using the NIMS-PrOptima performance management tool)

4 If a process for the applications listed in step 3 is not running, start it using the SMC. Do not use command line commands to start the process.

You are finished verifying that the required performance server processes are running.

Procedure 50:Verifying the performance server processes (continued)

Step Action


Nortel Networks Confidential Multiservice Switch-based network elements 107

Multiservice Switch-based network elements 5The procedures in this section apply to the following network elements:

• Aggregation Node

• Interworking Function (IWF)

• Media Gateway (MGW) (MGW 3.0.1 shows up as WG)

• Multiservice Switch 7420 (NAM), 7400, 15000, 20000

• SGSN/GPRS

• SGSN/UMTS (SGSN/UMTS 3.0.1 shows up as WG)

To enable performance data collection by the performance server for a Multiservice Switch-based network element you must perform the following procedures in the order listed:

1. Procedure 51: Configuring a Multiservice Switch-based network element

2. Procedure 52: Importing the HGDS configuration file

3. Procedure 53: Configuring the MDP

4. Procedure 54: Optimizing the File Prober Manager (optional)

5. Procedure 55: Increasing MNMPDI memory (optional)

6. Procedure 67: Verifying that the performance data has been processed

Configuring a Multiservice Switch-based network elementThis procedure enables performance data collection on a Multiservice Switch-based network element.

PrerequisitesBefore performing this procedure you must have a user ID and password for the network element. The user ID must have the following privileges:

• a scope of network or greater

• an impact of debug or greater

• AllowedAccess including local, telnet, FMIP and FTP

Procedure 51:Configuring a Multiservice Switch-based network element

Step Action

1 Log on to the network element.

2 Start provisioning mode. Enter:

start prov

—sheet 1 of 3—



3 This step is optional. To reset the statistics agent queue size on a logical processor enter:

add logicalprocessor/<n> engineering datastream/stats override

where <n> is the number of the logical processor

Note: To receive all of the counters, you must perform this step for each logical processor.

4 Set the maximum agent queue size for each logical processor. Enter:

set logicalprocessor/<n> engineering datastream/stats override agentqueuesize <size>


where <size> is a number between 20 and 200 specifying the maximum number of records in the queue, typically 100

5 Turn spooling option on. Enter:

set col/stats spool spool on

6 Set the maximum number of files that can exist in a closed directory. Enter:

set col/stats spool maxfile <number>

where <number> is a number between 1 and 200 specifying the maximum number of files to be kept on disk. A value of 0 (zero) allows an unlimited number of files on the disk. Use 0 with caution.

7 Enter:

display logicalprocessor/<n> engineering datastream/stats


display logicalprocessor/* engineering datastream/stats override agentqueuesize

display collector/stats spooler

display collector/stats agent/* statistics, agentstatistics

8 Verify that the settings are correct.

9 Verify that the changes are correct:

check prov

If there are errors, correct them, and enter the command again.

Procedure 51:Configuring a Multiservice Switch-based network element (continued)

Step Action

—sheet 2 of 3—



Importing the HGDS configuration fileThis procedure imports the Multiservice Switch host group directory server (HGDS) configuration file from the main server to the performance server. The HGDS.cfg file contains configuration information for Multiservice Switch network elements. You can use this procedure to help when you configure the performance server with the applicable Multiservice Switch-based network element connection information.


• password for the root user ID on the performance server

• IP address of the client workstation you are working from

• host name or IP address of the main server

10 Save the changes. Enter:

save prov

11 Activate the provisioning changes immediately. Enter:

activate prov

confirm prov

commit prov

12 Exit provisioning mode. Enter:

end prov

13 Verify that there is statistics data on the network element. Enter:

cd -p(spooled) filesystem

cd -p(closed) filesystem

cd -p(stats) filesystem

ls filesystem

A list of files displays. The names of the files start with ppc_stats.yyyymmdd.

14 Log off of the network element.

You are finished configuring the network element for performance management.

Procedure 51:Configuring a Multiservice Switch-based network element (continued)

Step Action

—sheet 3 of 3—



• a user ID and password for the main server

Procedure 52:Importing the HGDS configuration file

Step Action


2 Log on to the performance server using the root user ID.


DISPLAY=<IP address>:0.0


export DISPLAY

4 Enter:

/opt/MagellanNMS/bin/hgadmin

The Host Group Administration window opens in the Exceed window.

5 From the File menu, select Load and Merge Remote Host Group File.

The Load and Merge Remote Host Group File window opens.

6 Enter the following fields:

Remote Workstation: host name or IP address of the main server

User ID: FTP user ID on the main server

Password: password for FTP user ID on the main server


8 From the File menu, select Save.

9 From the File menu, select Exit.

10 Use the SMC to stop the MDM process group.

11 Restart the MDM process group. Make sure that the HGDS process is running.

You are finished importing the HGDS configuration file.



Configuring the MDPThis procedure explains how to configure the Management Data Provider (MDP) to support the Packet Data Interface (PDI). Upon completion of this procedure, the MDP is configured to convert the performance data files into bulk data format (BDF) files and send them to the PDI.


• the IP address of the client workstation from which you are accessing the MDP

• the host name of the performance server

• the password for the pm_pdi user ID on the performance server

• a name that identifies the group of network elements managed by the MDP

• the user ID and password that is common for the all network elements in the group

— this common user ID must have the following privileges:

– a scope of device or greater

– an impact of config or greater

– AllowedAccess including FMIP and FTP

Procedure 53:Configuring the MDP

Step Action




4 Set the DISPLAY variable to the IP address of your workstation. For information on how to do this, see the W-NMS Operator Guide, 411-5221-505:

5 Enter:


./gmdpconfig&


—sheet 1 of 4—




The Passport Data Management information displays.

7 Ensure that the following fields are set to the values shown (under the Stats column):

• BDF in dump directories is selected.

• BDF field delimiter value is 0X7F.

• BDF output compression box is selected.

• RDF Backwards Compatibility box is selected.

• (All other check boxes are not selected.)

• BDF converter log level value is 3.

• Passport File Manager log level value is 3.

8 If you changed any of the fields in step 7, click on the Save Passport button, and answer yes to the next two questions.





• Hostname: host name of the performance server

• Userid: pm_pdi

• Password: password for the pm_pdi user ID


13 Click on Save Host.

14 Click on Cancel.


16 In the hostname drop-down list, click on the host name Login ID that you added in step 12.

17 Make sure that the Set destination ftp directory check box is not selected.

18 Click on the Save File Mover button and answer yes to the next two questions.

19 Click on the File Prober tab.

20 In the File Prober window, click on the Collection Options tab.

Procedure 53:Configuring the MDP (continued)

Step Action

—sheet 2 of 4—



21 In the drop-down list under Passport Group, click on the group name that identifies the group of network elements managed by the MDP.


• User: the common user ID used to log on to all the network elements in the group

• Password: password for the user ID

23 Under Primary MDP Host, enter the following fields:

• Host: host name of the performance server

• User: nortel

• Password: password for user ID nortel

If your OAM network contains a secondary performance server and you want to define a backup MDP host, under Backup MDP Host:

24 Select the check box.


• Host: host name of the secondary performance server

• User: nortel


26 Under Options:

• Select the Rollover check box.

• Make sure that the No erase on Passport check box is not selected.

• Set Loglevel to 3.

• Set DataType to sta.

• Click on the Node name button.

27 In the File Prober window, click on the Collection Time tab.

28 Under Data Collection Start Time, clear all the granularity periods by clearing the All check box under Minute.

29 In the list box under Minute, hold the Ctrl key down and click on each time interval you want to collect performance statistics for. If you are using MyCom as your OSS, the granularity period must be every 15 minutes, so you would click on 0,15, 30, and 45.


31 Click on the Save File Prober button.


Step Action

—sheet 3 of 4—



Optimizing the File Prober ManagerPerform this procedure to improve the performance of the File Prober Manager. It is optional to perform this procedure although it is recommended that you perform it.


• a valid user ID and password for the performance server (not root)

• the password for the root user ID on the performance server.


33 Use the SMC to verify that the following processes are running in the mdm_perf group:

• HGDS







• MNSD Agent

• Log Collector

34 If any of the processes shown in step 33 are not running, use the SMC to start them.

You are finished configuring the MDP.

Procedure 54:Optimizing the File Prober Manager

Step Action


2 Log onto the performance server using a user ID that is not the root user ID.


Step Action

—sheet 4 of 4—



3 In a terminal window, type:

su -root

<root password>

where <root password> is the password for the root user ID

4 Set the DISPLAY variable to the IP address of your workstation. For information on how to do this, see the W-NMS Operator Guide, 411-5221-505.

5 Type:


./nmstool ‘Admin.tsets’ &

6 From the application main window, select System -> Administration -> Server Administration.

The Server Administration window opens.

7 From the Security menu select Authorize.

The SVM Enter Authorization Password window opens.

8 Type the password in the Password field. The default password is <blank>.

9 Click on OK.

10 In the server list, right-click on the MDP PP Prober Manager entry.

11 From the pop-up menu, select Edit Server.

The SVM Edit Server window opens.

12 In the Startup command field, type:

/opt/MagellanMDP/bin/mdpfpmgr -max_concurrent 8

13 Click on Save and Restart.

14 Click on Cancel.

15 In the Server Administration window, from the File menu, select Exit.

16 In the application main window, from the File menu, select Exit.

You are finished optimizing the File Prober Manager.

Procedure 54:Optimizing the File Prober Manager (continued)

Step Action



Increasing MNMPDI memoryThe SGSN/GPRS has a group of GSC based counters which give statistics on a per cell basis. If you enable this counter group on the SGSN/GPRS, you must increase the amount of memory allocated to the MNMPDI. The MNMPDI is responsible for merging the XML files together. Refer to the Nortel Wireless Network Management System Engineering Guide, 450-3101-638 for more information and the recommendations for the memory settings. The MNMPDI has a default of 1 GB of memory. This procedure increases the amount of memory available to the MNMPDI.

Procedure 55:Increasing MNMPDI memory

Step Action

1 Start the SMC client application from the Network Services Platform or use the stand-alone client application from a PC.

2 Log onto the SMC on the primary main server. If you are using the stand-alone client on a PC, you will have to enter the IP address or the node name of the primary main server when you log on.

3 Select the performance server.

4 Stop the Core_Perf group. For information about the SMG, see Wireless Network Management System System Management, 411-8111-538. Keep the SMC open.

5 Log into the performance server as user nortel.

6 Type:

cd /opt/nortel/config/packet/pdi

7 Using the text editor of your choice, edit the pdi.cfg file. For example:

vi pdi.cfg

8 Change the line which starts with ppMaximumJavaHeapSize. Possible examples of values that could be used are shown in the following lines. Do not include spaces and follow the upper and lower case formatting as shown. Do not exceed 2 GB (Xmx2048m).

ppMaximumJavaHeapSize=-Xmx1536m

ppMaximumJavaHeapSize=-Xmx2048m

9 Save the pdi.cfg file.

10 Use the SMC to restart the core_perf group.

11 Perform Procedure 50: Verifying the performance server processes to verify that the core_perf group has started.

End of procedure.


Nortel Networks Confidential SGSN debug statistics 117

SGSN debug statistics 5This section explains how to provision the SGSN to generate the SGSN debug statistics data files and enable collection of the data files on the performance server. When the debug statistics data is on the performance server, you can look at it using the Performance Manager. In the Performance Manager, the data is stored in the folder named debug:AvailableOMGroups. For more information about the Performance Manager, see the GSM NSS/UMTS VCN OAM Manual, 411-8111-503.

To enable the collection of SGSN debug statistics, perform the following procedures:

• Procedure 56: Adding the SGSN to the MDM host

• Procedure 57: Configuring the MDP for SGSN debug statistics

• Procedure 58: Creating the configuration files

• Procedure 59: Verifying SGSN debug statistics collection

Adding the SGSN to the MDM hostThis procedure adds the SGSN network element and the SGSN group to the MDM host using the Host Group Administration tool.

PrerequisitesBefore performing this procedure you must provision the SGSN network element to generate the debug statistics data files. For information about how to do this speak to your Nortel representative.

Procedure 56:Adding the SGSN to the MDM host

Step Action


2 Log onto the performance server using a user ID that is not the root user ID.


su -root

<root password>



—sheet 1 of 2—



Configuring the MDP for SGSN debug statisticsThis procedure configures the MDP to receive debug statistics from the SGSN.

5 Type:

/opt/MagellanNMS/loads/<MDM load name>/bin/hgadmin

where <MDM load name> is the name of the MDM load

6 In the Host Group Administration window, select the Passport tab.

7 In the Passport Table section, click on Add.

8 In the Add New Passport window, type the name of the SGSN network element in the Passport Name field.

9 Type the IP address of the SGSN network element in the IP Address field.

10 Click OK.

11 In the Passport Groups section, click on Add.

12 In the Add New Passport Group window, type a name for the group that the SGSN belongs to in the Passport Group Name field.

13 Click OK.

14 In the File menu, select Save.

15 Close the Host Group Administration window.

16 Use the SMC to stop the processes in the mdm_perf group.

17 Use the SMC to start the processes in the mdm_perf group.

Procedure 57:Configuring the MDP for SGSN debug statistics

Step Action


2 Log onto the performance server using the nortel user ID.

—sheet 1 of 4—

Procedure 56:Adding the SGSN to the MDM host (continued)

Step Action

—sheet 2 of 2—




4 Enter:


./gmdpconfig&


File Prober Tab

5 Click on the File Prober tab.

6 In the File Prober window, click on the Collection Options tab.

7 In the drop-down list under Passport Group, click on the group name that identifies the group that the SGSN belongs to. It is recommended that you create one group for the NEs from which you are collecting both SGSN debug statistics and other performance data, and create another group for the NEs from which you are collecting other performance data not including debug statistics. This prevents the CPU from being overloaded.

8 Type the following fields:

• User: the common user ID used to log on to all the network elements in the group

• Password: password for the user ID

9 Under Primary MDP Host, type the following fields:

• Host: host name of the performance server

• User: nortel


10 Under Options, type the values indicated for the following fields:

• Max. files to collect: 61

• FTP timeout (sec): 911

• Data Type: acc

11 Click on the Collection Time tab.

12 Under Data Collection Start Time, clear all the granularity periods by clearing the All check box under Minute.

13 In the list box under Minute, hold the Ctrl key down and click on each time interval you want to collect performance statistics for. Select either 15 minute intervals or 30 minute intervals.

Procedure 57:Configuring the MDP for SGSN debug statistics (continued)

Step Action

—sheet 2 of 4—





File Mover tab

The following steps configure the File Mover. This causes the MDPMover.cfg file to be updated with new configuration information. You will disable the configuration and it will be used in Procedure 58. SGSN debug statistics requires two of the three Customer Host entries in the File Mover tab for the File Type Passport Accounting BDF.


17 In the Process Log Level list, select a log level.

18 In the File Type list, select Passport Accounting BDF.


20 In the Edit Host window, click on New Host.


• Hostname: host name of the performance server

• Userid: pm_pdi

• Password: password for the pm_pdi user ID



23 In the Edit Host window, click on New Host.


• Hostname: IP address of the performance server

• Userid: nortel

• Password: password for the nortel user ID




Step Action

—sheet 3 of 4—




27 In the hostname drop-down list, click on the entry that shows the host name of the performance server and the pm_pdi user ID (the host you created in step 21).


29 Type the following value in the field below the Set destination ftp directory check box:

/opt/nortel/data/packet/gdi/debug-sgsn/incoming


31 In the hostname drop-down list, click on the entry that shows the IP address of the performance server and the nortel user ID (the host you created in step 24).


33 Type the following value in the field below the Set destination ftp directory check box:

/opt/nortel/data/coreEMS/PDSdata

34 Under Customer Host 1, clear the enabled check box.

35 Under Customer Host 2, clear the enabled check box.

36 Click on the Save File Mover button and answer yes to the next two questions.


You are finished configuring the MDP.


Step Action

—sheet 4 of 4—



Creating the configuration filesThis procedure creates and modifies configuration files which are required for SGSN debug statistics.

Procedure 58:Creating the configuration files

Step Action

1 Log onto the performance server using the nortel user ID.


su -root

<root password>


3 Type:

cd /opt/nortel/shell/packet/gdi

./sgsnMDPcfg -n

4 Wait for the script to finish running.

5 Use the SMC to start the processes in the mdm_perf group.

6 Log off of the performance server.



Verifying SGSN debug statistics collectionThis procedure verifies that the MDP is collecting the debug statistics data files.

Procedure 59:Verifying SGSN debug statistics collection

Step Action

1 Verify that the collection log files are in the following directory:

/opt/MagellanMDP/data/mdp/admin/mdprober/debug

The collection log files are of the form mdprober_15KPP022X_20041118.log

2 Verify that the conversion log files are in the following directory:

/opt/MagellanMDP/data/mdp/admin

The conversion log files are of the form err.pp_<load name>_debug.20041119T110000.773.15KPP022X.cc

3 Verify that the debug statistics data files are in the following directories:

/opt/nortel/data/packet/gdi/debug-sgsn/incoming

/opt/nortel/data/coreEMS/PDSdata



GGSN 5To enable performance data collection by the performance server for a GGSN network element you must perform the following procedures in the order listed:

1. Procedure 60: Configuring the GGSN

2. Procedure 61: Configuring the Log Server and the Pull Server

3. Procedure 64: Configuring the ADC

4. Procedure 62: Verifying the granularity period for the performance data files


6. Ensure that the pmuser user ID on the SCS server has the appropriate privileges to delete the CSV data files found in all directories under /opt/shasta/scs/log/preside. The pmuser user ID is the OAM user on the SCS server. If the OAM user ID for your system is a different value, you must ensure that it has the appropriate privileges.

To configure the GGSN, you use the Service Creation System (SCS). For more information about the SCS, see the following NTPs:

• GGSN User Guide, 411-5221-926

• GGSN Provisioning Procedures, 411-5221-927

Configuring the GGSNThis procedure configures the GGSN to collect performance data. For each Internet Service Provider (ISP), you can use this procedure to configure statistics collection for the Gn, Gi, Ga, and Device Owner profiles. For detailed information about configuring the GGSN to collect performance data, see the section about provisioning accounting in the GGSN Provisioning Procedures, 411-5221-927.

PrerequisitesBefore performing this procedure you must have:

• the SCS client software installed on your work station in the directory C:\Program Files\shasta (The SCS client software must be compatible with the SCS server software.)

• a user ID and password with a Gn ISP User profile on the SCS

• a user ID and password with a Gi ISP User profile on the SCS

• a user ID and password with a Ga ISP User profile on the SCS

• a user ID and password with a Device Owner user profile on the SCS

• the IP address of the SCS server



For each ISP User profile, you must also know which accounting elements you want to collect statistics for. Table 2 shows the valid accounting elements for which you can collect statistics

Table 2:GGSN accounting elements

Accounting Group Scope User Privilege GGSN release

Memory Active CMC Device Owner 3.2, 4.0, 4.1

Session Management Gn ISP ISP 3.2, 4.0, 4.1

GTP Data Gn ISP ISP 3.2, 4.0, 4.1

GTP Accounting Gn ISP or Ga ISP ISP 3.2, 4.0, 4.1

RADIUS Accounting per RADIUS Server per Gi ISP ISP 3.2, 4.0, 4.1

APN per APN per Gi ISP ISP 3.2, 4.0, 4.1

CGF per CGF on Gn ISP or Ga ISP ISP 3.2, 4.0, 4.1

L2TP per Gi ISP ISP 3.2, 4.0, 4.1

L2IP per Gi ISP ISP 3.2, 4.0, 4.1

IPSec per Gi ISP ISP 3.2, 4.0, 4.1

Overload Device Device Owner 3.2, 4.0, 4.1

Wireless Services per Gi ISP ISP 3.2, 4.0, 4.1

GRE per Gi ISP ISP 3.2, 4.0, 4.1

SCP per SCP server per Gi ISP ISP 3.2, 4.0, 4.1

ISP-IP per Gi ISP Device Owner and ISP 3.2, 4.0, 4.1

Ancillary APN per APN per Gi ISP ISP 3.2, 4.0, 4.1

APN Data Plane per APN per Gi ISP ISP 3.2, 4.0, 4.1

MPLS per Gi ISP ISP 4.0, 4.1

VRF Accounting per Gi ISP ISP 4.0, 4.1

DCC per DCC server per Diameter Profile per ISP

ISP 4.0, 4.1

DHCP per DHCP Server per Gi ISP ISP 4.1



Local Address Pool per Local Address Pool per Gi ISP

ISP 4.1

Procedure 60:Configuring the GGSN

Step Action

1 Start the SCS client on your workstation.

2 Log on to the SCS using the appropriate ISP User ID (Gn, Gi, Ga, or Device Owner) and password, and the IP address of the SCS server.

3 On the left side of the Device Manager window, click on the Devices icon.

4 Double-click on Regions folder.

5 Click on a node in the Regions folder.

6 Double-click on any GGSN network element that has a status of In Sync.

The Configuration - Device window opens for the network element.

7 Click on the Access Properties tab.

8 If you are logged in as Gn, Gi, or Ga, click on the Select... button that is beside ISP Accounting Profile. If you are logged in as Device Owner, click on the Select... button that is beside Device Owner Accounting Profile.

The Accounting Profile Selection window opens.

9 Click on the New... button in the ISP Accounting Profile selection window.

The New Accounting Profile window opens.

10 In the Accounting Profile Name field, enter a name for this profile.


The Accounting Profile window opens.

—sheet 1 of 3—

Table 2:GGSN accounting elements

Accounting Group Scope User Privilege GGSN release



12 Under Accounting Elements, click on the accounting element that you want to collect statistics for in the Type column. See Table 2 for the accounting elements you can choose from.


The Accounting Element Selection window opens.

14 Click on the New... button.

The Accounting Element window opens.

15 Enter a name for the accounting element in the Name field.

16 From the Type drop-down list, select the statistic you want to collect. It must be the same type as you selected in step 12.

17 Set a value for interval (min) field. The supported values are 15, 30, and 60. A value of 15 is recommended.


The Accounting Element Selection window comes into focus. The accounting element you created shows up in the list.

19 In the Accounting Element Selection window, click on the Accounting Element you just created.


The Accounting Profile window comes into focus. The Accounting Element you created shows up under the Accounting Element Name for the type of statistic and interval you selected.

21 Perform step 12 through step 20 for each of the accounting elements that you want to collect statistics for.

22 In the Accounting Profile window, click on the OK button.

The new accounting profile shows up in the ISP Accounting Profile selection window.

23 In the list of accounting profiles, click on the accounting profile you just created.


The Access Properties tab displays. The new accounting profile shows up beside ISP Accounting Profile (or if you created a new Device Owner Accounting profile, it shows up beside Device Owner Accounting Profile).

25 Click on the OK button in the Access Properties tab.

Procedure 60:Configuring the GGSN (continued)

Step Action

—sheet 2 of 3—



Configuring the Log Server and the Pull ServerThis procedure configures the SCS Log Server and the Pull Server to generate the performance data files.


• the SCS client software installed on your workstation in the directory C:\Program Files\shasta (The SCS client software must be compatible with the SCS server software.)

• a user ID and password with a Device Owner profile on the SCS server

• the IP address of the SCS server

26 Close the SCS client.

You are finished configuring the GGSN for performance management.

Procedure 61:Configuring the Log Server and the Pull Server

Step Action

1 Start the SCS client on your workstation.

2 Log on to the SCS using a user ID that has a Device Owner profile and the IP address of the SCS server.

3 On the left side of the Device Manager window, click on the Devices icon.

4 Double-click on Regions folder.

5 Double-click on any GGSN network element that has a status of In Sync.

The Configuration - Device window opens for the network element.

6 Click on the Management tab.

—sheet 1 of 2—

Procedure 60:Configuring the GGSN (continued)

Step Action

—sheet 3 of 3—



7 Under Auxiliary Servers, verify that a Log Server and a Pull Server are configured. If there is at least one IP address and port number under Log Servers and at least one IP address and port number under Pull Servers, then you are finished this procedure. Go to step 17.

8 If the Log Server has not been set up, click on the Change... button under Auxiliary Servers.

The Auxiliary Server window opens.

9 In the Auxiliary Server window under Log Servers, click on the Add... button.

The Log Server Selection window opens.

10 Click on the IP address of the Log Server.

11 In the Log Server Selection window, click on the OK button.

12 In the Auxiliary Server window under Pull Servers, click on the Add... button.

The Pull Server Selection window opens.

13 Click on the IP address of the Pull Server.

14 In the Pull Server Selection window, click on the OK button.

15 In the Auxiliary Server window, click on the OK button.

16 In the Configuration - Management window, click on the OK button.

17 Close the SCS client.

You are finished configuring the Log Server and the Pull Server.

Procedure 61:Configuring the Log Server and the Pull Server (continued)

Step Action

—sheet 2 of 2—



Verifying the granularity period for the performance data files 5This procedure ensures that the granularity period specified in the SCSLogTimerInterval.config file matches the value specified in the SCS.

PrerequisitesBefore performing this procedure you must know the password for the root user ID on the SCS server.

Procedure 62:Verifying the granularity period for the performance data files

Step Action

1 Log onto the SCS server using the root user ID.

2 In the command line of a terminal window, enter:

cd /shasta/scs/log

more SCSLogTimerInterval.config

3 Make sure that the following line is in the file as shown:

CSVFileInterval=<granularity period>

where <granularity period> is the same value that you specified for the granularity period value on the GGSN in Procedure 60.

4 If the granularity period is not the same, open the SCSLogTimerInterval.config file for editing, change the value, and save the file.

5 Log off of the SCS server.

You are finished verifying the granularity period for the performance data files.



SS7 IP Gateway 5To enable performance data collection by the performance server for an SS7 IP Gateway (SIG) network element you must perform the following procedures in the order listed:

1. Procedure 63: Configuring the SIG

2. Procedure 64: Configuring the ADC


Configuring the SIGThis procedure sets up a cron job to generate the operational measurement (OM) file for the SIG.


• the password for the root user ID on the SIG

• the OAM user ID on the SIG

— This procedure uses pmuser as the OAM user ID. If the OAM user ID for your system is a different value, use that value in the procedure where pmuser is shown.

— The OAM user ID must have permissions to execute omstore.sh and to write to the /siglog directory.

• the name of the directory that contains the latest release of the SIG software

This procedure applies for SIG 5.0. You must have the SIG 5.0 release software installed.

Procedure 63:Configuring the SIG

Step Action

1 Log onto the SIG network element using the root user ID.

2 In the command line of a terminal window, enter:

more /etc/passwd

3 Ensure that pmuser shows up in the list that displays.

4 Ensure that the directory /home/pmuser exists.

—sheet 1 of 2—



5 Enter:

EDITOR=vi ; export EDITOR

6 Enter:

chown pmuser siglog

7 Enter:

crontab -e pmuser

8 If you want an OM file to be generated every 60 minutes, add the following line:

0 * * * * /sig/pkg/<release dir>/executables/omstore.sh > /dev/null

where <release dir> is the name of the directory that contains the latest release of the SIG software

9 If you want an OM file to be generated every 15 minutes, add the following line:

0,15,30,45 * * * * /sig/pkg/<release dir>/executables/omstore.sh > /dev/null

The first five values in the line indicate the minutes, hour, day of month, month, and day of week. Valid values are:

• minutes: 0 to 59

• hours: 0 to 23, where 0 is midnight

• day of month: 1 to 31

• month: 1 to 12

• day of week: 0 to 6, where 0 is Sunday

10 Save the file and quit the editor. Enter:

wq!

You are finished configuring the SIG for performance management.

Procedure 63:Configuring the SIG (continued)

Step Action

—sheet 2 of 2—



Configuring the ADCThis procedure explains how to use the ASCII Data Collector (ADC) configuration tool to configure the ADC to collect performance data from the following network elements:

• GGSN

• SIG

For the SIG, which has a duplex configuration, you must perform this procedure twice, once for each static IP address of the two HP servers (active server and standby server). Note that only the active server sends performance data to the performance server.

The following table lists the default values for the ADC parameters for each network element:

Table 3

ADC parameter network element

GGSN SIG

Collection Interval 15 15

File Format *.csv om.*

File Rename *.[collectorname].csv om.*.[collectorname]

Source Directory(If your data files are stored in a different directory then use that directory for this parameter.)

/shasta/scs/log/preside /siglog

Incoming Dir

/opt/nortel/data/packet/gdi/shasta-ggsn/incoming

/opt/nortel/data/coreEMS/GGSNdata

/opt/nortel/data/packet/sdi/collection/incoming

/opt/nortel/data/coreEMS/SIGdata

Collection Per(FTP granularity)

Device Top-level

File Exclusion not applicable not applicable



PrerequisitesBefore performing this procedure you must have the following information for the network element (For the GGSN, use the information for the SCS server. For the SIG, you must know the IP address and host name of both HP servers in the duplex configuration):

• host name

• IP address

• user ID

• password

• collector name (This is a name which identifies the collector for the network element in the ADC.)

Note: You can have only one instance of the ADC configuration tool running at one time.

Deletion Exclusion not applicable not applicable

File Limit per FTP 20 100

Minutes past Interval 5 5

Recursive Directory Search

yes no

Port Number 21 21

Procedure 64:Configuring the ADC

Step Action



setenv DISPLAY <IP address client>:0.0

3 Enter:


—sheet 1 of 3—

Table 3

ADC parameter network element

GGSN SIG



4 Enter:

./adcGUI&

The ASCII Data Collector Configuration - Collector Window opens.

5 In the Device Type For New Collector drop-down list, click on one of the available device types in the list. Do not select “DEFAULT”. It is for future use.


The ASCII Data Collector Configuration - Registration Window opens.

7 Under Device Information, enter:

Host Name: <host name>

IP address: <IP address NE>

User ID: pmuser

Password: <password>

where <host name> is the host name of the network element

where <IP address NE> is the IP address of the network element. For the GGSN, this value must be the IP address of the SCS server.

where <password> is the password for <user ID>

The Source Dir field contains a default value based on the Device Type you entered in step 5. For the default values, see Table 3.

8 Under Collector Information, enter:

Collector Name: <collector name>

where <collector name> is a text string which identifies the collector for the network element in the ADC

The Collector Interval, File Format, File Rename, and Incoming directory fields contain default values based on the Device Type you entered in step 5. For the default values, see Table 3.

For the GGSN, the Collector Interval must be one of 15, 30, or 60 minutes. The recommended value is 15.

For the Incoming directory:

i. you can specify multiple directories separated by commas

ii. the directory(s) must be under the /opt/nortel/data directory


Step Action

—sheet 2 of 3—



Accessing the ADC configuration tool from the Network Services Platform

Use this procedure to start the ADC configuration tool from the Network Services Platform window. You can perform this procedure in place of step 1 through step 4 of Procedure 64.

PrerequisitesBefore performing this procedure you must know the password for the nortel user ID on the performance server.

9 Click on the Activate button.

The ASCII Data Collector Configuration - Registration Window closes. In the ASCII Data Collector Configuration - Collector Window, the new collector appears in the Collector List with a Collector State of Activated.

10 Perform step 7 through step 9 for each network element.


You are finished configuring the ADC.

Procedure 65:Accessing the ADC configuration tool from the Network Services Platform

Step Action


2 From the Configuration menu of the Network Services Platform window, select Launch ADC GUI from performance server <host name>

where <host name> is the name of the performance server

A Login window opens.

3 Enter the nortel user ID and password for the performance server.

The ASCII Data Collector Configuration - Collector Window opens in the Exceed window.


Step Action

—sheet 3 of 3—


Nortel Networks Confidential Voice core network elements 137

Voice core network elements 5The voice core network elements that are supported for performance management are:

• HLR100

• HLR200

• MSC

• combined MSC/HLR

• Service Location Register (SLR)

• Signaling Gateway (SGW)

• R4 BICN MSC

• Universal Number Portability Master (UNPM)

The MGW and IWF are also supported for performance management. See “Multiservice Switch-based network elements” for the procedures to enable performance management for these network elements.

To enable performance data collection by the performance server for the previously listed network elements, you must perform the following procedures in the order listed:

1. Procedure 66: Enabling data collection for a voice core network element


Enabling data collection for a voice core network elementThis procedure explains how to use the Core Element Manager (CEM) to configure a mass export of the data files to the CDI. The CEM is the graphical user interface for the voice core network elements. You access the CEM through the Network Services Platform. For more information about the Network Services Platform see the Network Services Platform User Guide, 411-5221-211.

PrerequisitesBefore performing this procedure you must

• perform the main server device integration for the network element

• know how to use the Network Services Platform

• know the password for the admin user ID on the Network Services Platform. The admin user ID must be created on the NSP LDAP server. For more information, see “admin user ID” in this NTP.



• set the granularity period for the network element to the value shown in the following table:

Table 4

network element supported granularity period

recommended granularity period

HLR 100 15, 30 30

HLR 200 15, 30 30

MSC 15, 30 30

combined MSC/HLR 15, 30 30

SLR 30 30

SGW 30 30

R4 BICN MSC 15, 30 30

UNPM 30 30

USP component of HLR 200 or MSC

30 30

Procedure 66:Enabling data collection for a voice core network element

Step Action

1 Log on to the Network Services Platform using the admin user ID.

2 In the Resource Browser, open a network layout that contains a voice core network element. See “Voice core network elements” for a list of supported voice core network elements.

3 Right-click on the network element.

The object menu for the network element opens.

4 From the object menu, select CEM and then select Open.

The Nortel Element Browser window opens.

5 From the Performance menu, select Mass Export.

The Export Status Window window opens.

6 From the File menu, select Start Editor and then select Archive Export Profile.

The Archive Export Profile Editor window opens.

—sheet 1 of 3—


Nortel Networks Confidential Voice core network elements 139

7 Under Selected Group, click on the plus (+) sign beside the network element you want to collect data for.

The network element tree expands.

8 Click on each of the plus signs in the lower levels to completely expand the network element tree.

The operational measurement (OM) groups display.

9 Select the OM group that you want to export by clicking on the box beside the OM group name. To export all the OM groups, click on the box at the highest level.

10 Ensure that the following fields are defined as indicated:

a. Field Separator: select the Tab button.

b. Reporting Period: select the Switch button.

c. Hours of Backup: in the drop-down list, select 1.

11 Under Export to:, enter values for the following fields:

Login: <login name>

where <login name> is a valid user ID for the performance server

Password: <password>

where <password> is the password for the user ID

IP Address: <IP address>

where <IP address> is the IP address of the performance server

Directory: <directory>

where <directory> is the incoming directory for the CDI, /opt/nortel/data/circuit/collection/incoming.

12 Click on the Save button.

The Re-Enter Password window opens.

13 Enter the password and click on the OK button.

The Input window opens.

14 Enter a name for the profile and click on the OK button.

15 From the File menu, select Close.

The Archive Export Profile Editor window closes. In the Export Status window, the profile you created displays in the Profile tab with a Status of DISABLED .

Procedure 66:Enabling data collection for a voice core network element (continued)

Step Action

—sheet 2 of 3—



16 In the Export Status window, click on the profile to select it.

17 Right-click on the profile and select Enable/Disable.

The Status of the profile changes to ENABLED.

18 Close the Export Status window.

19 Close the Nortel Element Browser window.

You are finished enabling data collection for the voice network element

Procedure 66:Enabling data collection for a voice core network element (continued)

Step Action

—sheet 3 of 3—


Nortel Networks Confidential Verifying that the performance data has been processed 141

Verifying that the performance data has been processed 5Use this procedure to verify that the performance data has been successfully collected and processed for a network element.

Table 5

network element log directory data file

Multiservice Switch-based network elements

/opt/nortel/logs/packet/pdi/traces BDF data file

GGSN /opt/nortel/logs/packet/gdi/traces CSV data file

SIG /opt/nortel/logs/packet/sdi/traces text data file

HLR 100HLR 200MSCcombined MSC/HLRSLRSGWR4 BICN MSCUNPM

/opt/nortel/logs/circuit/traces tab-delimited data file

SGSN/GPRSSGSN/UMTS

/opt/nortel/logs/packet/gdi/traces/GDIsgsn*.log

BDF data file

Procedure 67:Verifying that the performance data has been processed

Step Action


2 Go to the appropriate directory from Table 5 and view the log file. The format for the log file names is explained in the chapter that describes the Performance Management log files.

For example, enter the following command to view the log file for a Multiservice Switch:

tail -f /opt/nortel/logs/packet/pdi/traces/<yyyymmdd>.log

3 Make sure that the log file contains messages that indicate the appropriate data file as shown in Table 5 has been received and processed at the correct granularity period.

4 Look at the appropriate XML file directory and verify that the XML file is in the directory and that it is correctly named. For information about the XML file directories and XML file names, see the Wireless Network Management System Core Network Observation Counters, 411-8111-401.

You are finished verifying that the performance data has been processed.



Disabling data collection 5The procedures in this section explain how to stop the performance server from collecting performance data from a network element.

Disabling data collection for Multiservice Switch-based network elements

Perform this procedure to stop the performance server from collecting data from the following network elements:


• IWF

• MGW (MGW 3.0.1 shows up as WG)

• Multiservice Switch 7420 (NAM), 7400, 15000, 20000

• SGSN/GPRS


This procedure:

• disables the transfer of data files from the MDP to the PDI

• deletes the data collection entry for each network element

• deletes a group and all network elements in the group

For more information about the previously mentioned tasks, refer to the Preside Multiservice Data Manager Management Data Provider User Guide, 241-6001-309.

Procedure 68:Disabling data collection for Multiservice Switch-based network elements

Step Action




3 Enter:

cd /opt/MagellanMDP/bin

4 Enter:

./gmdpconfig&

The Management Data Provider Administration window opens.

—sheet 1 of 3—


Nortel Networks Confidential Disabling data collection 143

Disabling the data collector

5 In the list on the left side of the window, click on the File Prober tab.

6 In the Entries section, clear the check box for the collector group that you want to disable.

7 At the bottom of the Management Data Provider Administration window, click on the Save File Prober button.

The Confirm Changes window opens.


The Confirm Process Restart window opens.


The data collector is disabled. The data files will not be transferred from the MDP to the PDI. If you want to stop the data files from being collected by MDP, go to step 10. Otherwise you are finished this procedure.

Deleting the data collection entry

10 In the Entries list, click on the row (not the check box) of the collector group that you want to delete.

11 Click on the Delete button.

The entry disappears from the Entries list.

12 Perform step 10 and step 11 for each entry that you want to delete.

13 At the bottom of the Management Data Provider Administration window, click on the Save File Prober button.

The Confirm Changes window opens.


The Confirm Process Restart window opens.


16 At the bottom of the Management Data Provider Administration window, click on the Exit button.

Deleting the Multiservice Switch group and network elements


Procedure 68:Disabling data collection for Multiservice Switch-based network elements (continued)

Step Action

—sheet 2 of 3—



18 Log on to the performance server using the root user ID.


DISPLAY=<IP address>:0.0


export DISPLAY

20 Enter:

/opt/MagellanNMS/bin/hgadmin

The Host Group Administration window opens in the Exceed window.

21 In the Passport Groups section of the Passport tab, click on the group you want to delete.

22 Click on the Delete button under Passport Groups.

The Delete Passport Group window opens.


24 In the Passport Table section of the Passport tab, click on the Multiservice Switch name that you want to delete.

25 Click on the Delete button under Passport Table.

The Delete Passport window opens.


27 From the File menu, click on Save.

28 From the File menu, click on Exit.

You are finished disabling data collection for the Multiservice Switch network element.

Procedure 68:Disabling data collection for Multiservice Switch-based network elements (continued)

Step Action

—sheet 3 of 3—


Nortel Networks Confidential Disabling data collection 145

Disconnecting a network element from the ADCUse this procedure to disconnect a GGSN, or a SIG network element from the ADC.

Procedure 69:Disconnecting a network element from the ADC

Step Action




3 Enter:


4 Enter:

./adcGUI&

The ASCII Data Collector Configuration - Collector Window opens.

Deactivating the collector

5 Click on the collector name that you want to deactivate.

6 Click on the Deactivate button.

The collector shows Deactivate.

Deleting the collector

7 Click on the collector name that you want to delete.

8 Click on the Delete button.

The collector disappears from the Collector Window.

You are finished disconnecting a network element from the ADC.



Disabling data collection for a voice core network elementPerform this procedure to disable data collection for a voice core network element. See “Voice core network elements” for a list of the supported voice core network elements.

Procedure 70:Disabling data collection for a voice core network element

Step Action

1 Perform step 1 through step 5 of Procedure 66. (Start the CEM.)

2 In the Export Status window, click on the profile that you want to disable.

Note: If you create a profile and do not enable it, it is accessible only on the workstation on which it was created. To make it accessible to all users, you must enable it.


The Status of the profile changes to DISABLED.

4 If you want to delete the profile, right-click on the profile and select Delete.

The profile disappears from the Export Status window.

Note: If you disable a profile without deleting it, the Login and Password values are deleted. The profile is accessible only from the workstation on which it was created. To enable the profile you must edit it and enter the Login and Password values again.


6 Close the Network Element Browser window.

You are finished disabling data collection for the voice core network element.


Nortel Networks Confidential The Performance Application Manager 147

The Performance Application Manager 5The Performance Application Manager (PAM) allows you to:

• configure a profile that specifies which measurement object instance IDs (MOIDs) are to be included in the 3GPP XML file for a particular network element type

• specify the times and days of the week that a profile is applied by configuring a job for the profile

When you configure a profile, you select MOIDs or groups for components or sub-components of the network element. When you configure a job for the profile, you specify the days of the week and the times (in one hour increments) for which you want the profile to be applied. Jobs can be active or inactive. Profiles for active jobs are applied to the performance data files; profiles for inactive jobs are not applied to the performance data files.

The performance data file is filtered using the profile. The MOIDs specified in the profile are included in the XML file on the day and time interval specified in the job. The time stamp contained in the performance data file is used to determine if the file is filtered. The time stamp contained in a performance data file for a particular network element is based on the time zone where the network element is located. The performance server can be in a different time zone from the network element. To ensure that the filtering is applied consistently for all network elements, regardless of the time zone where they are located, the filtering is performed based on a calculated value using Greenwich Mean Time (GMT).

A performance data file for a packet network element contains a value called the GMT offset. The GMT offset is the number of hours from GMT of the time zone that the network element exists in. The performance data files for voice core network elements do not contain the GMT offset, so for those files the GMT offset of the performance server is used in the calculation. Here is an example that explains the calculation:

There is a performance server in Dallas with a GMT offset of GMT - 06:00. There is a packet network element in New York City with a GMT offset of GMT - 05:00. There is a voice core network element in Denver. When processing Monday 9:00 am data from the New York City network element, the filter used for the performance data file is determined by performing the calculation: 9 - (-5) + (-6) = Monday 8:00 am. When processing Monday 8:00 am data from the Denver network element, the filter used for the performance data file is determined by performing the calculation: 8 - (-6) + (-6) = Monday 8:00 am. The filtering done by the profile is based on these calculated times.



Here are some points to consider when configuring profiles and jobs:

• If more than one job is active for a particular day and time interval for the same network element type, the filter is the union of the MOIDs from the associated profiles.

• If a profile is configured with no MOIDs in it and has an active job associated with it, the resulting XML does not contain any measurement type data.

PAM main windowThe PAM main window is described in this section. Interaction with the PAM is performed through the PAM main window. See Figure 1.

Menu barThe menu bar contains the following menus and commands:

Network element tabsWhen you open the PAM main window, one tab is active for a specific network element. The tab contains the Job Browser window for the network element. Click on a tab to make it active. For information about the Job Browser window see the section titled “Job Browser window”.

When you select a command from the Configuration menu, the command launches in the context of the network element for the network element tab that is active. For example, if the network element tab for the MGW is active, and you select MOID Builder from the Configuration menu, the MGW MOID Builder window opens. For information about the MOID Builder window, see the section titled “Configuring a profile”.

Table 6Menu bar

Menu Command Description

File Exit exit the PAM main window

Configuration MOID Builder configure a profile

Scheduler schedule a profile to run

Window Cascade arrange the sub windows in the main window in a cascade

Tile arrange the sub windows in the main window beside each other.

Help About Application display version information about the MOP Automation Tool



Display modeYou can filter the profiles that are displayed in the Job Browser window by selecting a display mode in the View section of the Job Browser window. Table 7 shows the display modes available.

Job Browser windowTable 8 shows the tabs in the Job Browser window.

The top section of the Job Browser window (“Profiles” section in Figure 1) displays the profiles that have been configured for a network element. For information about profiles and how to configure them, see “Configuring a profile”.

The bottom section of the Job Browser window (“Definitions” section in Figure 1) shows the MOIDs in the profile that is selected in the top section of the window.

Status barThe status bar at the bottom of the window shows actions currently taking place and the status of actions that have been completed.

Table 7Display modes

Radio button Description

All displays all profiles

Active displays only the active profiles (indicated by a green icon beside the profile name)

Inactive displays only the inactive profiles (indicated by a red icon beside the profile name)

Table 8Job Browser tabs

Tab Description

By Profile displays the profiles in alphabetical order by profile name

By Day displays the profiles organized by day of the week and time that they are scheduled to run



Figure 1PAM main window

Opening the PAM main windowThis procedure opens the PAM main window of the PAM client. You can have only one instance of the PAM client active at a time.

Configuring a profileThis procedure defines a profile that specifies which measurement object instance IDs (MOIDs) to include in the 3GPP XML file for a network

Procedure 71:Opening the PAM main window

Step Action

1 Start Network Services Platform (NSP). For information about how to do this, see the W-NMS Operator Guide, 411-5221-505.

2 From the Configuration menu of the NSP main window, select Launch PAM Configuration.

3 End of procedure.

Menu barNetworkelementDisplaymode

Definition

Status

ProfilesJob Browserwindow



element. The profile filters the content of an XML output file that contains the performance data.

Procedure 72:Configuring a profile

Step Action

1 Open the PAM main window. See “Opening the PAM main window”.

2 Click on the tab of the network element for which you want to define a profile.

3 From the Configuration menu, select MOID Builder.

4 In the MOID Builder window, type a description for the profile in the Description (Optional) field.

5 In the MOID section, you can:

a. Click on the plus sign (+) beside a component or MOID to show its sub-levels. The names of components are shown in gray and the names of MOIDs are shown in black.

b. Click on the minus sign (-) beside a component or MOID to hide its sub-levels.

c. Select a check box beside a component to select all of the sub-components and MOIDs below it.

d. Select a check box beside an MOID to select all the measurement types associated with the MOID. The names of MOIDs are shown in black.

e. Clear a check box beside a component to deselect it and all of the subcomponents and MOIDs below it.

f. Clear a check box beside an MOID to deselect it.

When you click on an MOID that has measurement types or groups associated with it, they are displayed under Group/Measurement Type. Place the mouse cursor over a measurement type to display a description of the measurement type or operational measurement (OM) group. For voice core network element types, only OM groups are displayed due to their large number of OM group registers.

6 Click on Save As.

7 In the Save As window, type a name for the profile (maximum 32 characters).

8 Click on Save.

9 In the MOID Builder window, click on Close.

The profile shows up in the By Profile tab of the Job Browser window for the network element. The profile does not show up in the By Day tab of the Job Browser window until you configure a job for it. See “Configuring a job for a profile” for more information.



Configuring a job for a profileThis procedure specifies times and days of the week for which a profile is applied.

Procedure 73:Configuring a job for a profile

Step Action


2 Click on the tab of the network element for which you want to define a job.

3 From the Configuration menu, select Scheduler.

4 Select a profile from the Profile list.

5 In the Scheduler window, under Add New Time:

a. Select a Start Time from the list.

b. Select an End Time from the list.

c. Select a day(s) of the week.

d. Click on Add.

The day(s) of the week with the start and end times show up under Time Table.

6 If you want to remove a day and start and end time from the Time Table, click on the line in the Time Table, then click on Delete.

7 If you want to activate the job immediately after creating it, select the Activate check box. If you want the job to be inactive, leave the check box empty (or clear it, if it is selected).

8 When you have finished defining the job, click on Apply.

9 Click on Close.

10 In the Job Browser window under View, click on the All radio button.

11 Click on the By Day tab. Click on the plus sign (+) beside each day and time range. The job shows up for each day and time range that you specified, with an icon indicating if the job is active or inactive. If you activated the job in step 7, the icon is green. If you did not activate the job, the icon is red. You can also see the job in the By Profile tab.



Modifying a profileThis procedure modifies a profile.

Procedure 74:Modifying a profile

Step Action


2 Click on the tab of the network element which contains the profile you want to modify.


4 In the MOID Builder window, select the profile from the Profile drop-down list.

5 In the MOID section, you can:

a. Click on the plus sign (+) beside a component or MOID to show its sub-levels. The names of components are shown in gray and the names of MOIDs are shown in black.

b. Click on the minus sign (-) beside a component or MOID to hide its sub-levels.

c. Select a check box beside a component to select all of the sub-components and MOIDs below it.

d. Select a check box beside an MOID to select all the measurement types associated with the MOID. The names of MOIDs are shown in black.

e. Clear a check box beside a component to deselect it and all of the subcomponents and MOIDs below it.

f. Clear a check box beside an MOID to deselect it.

6 Click on Save.




Deleting a profileThis procedure deletes a profile.

PrerequisitesBefore deleting a profile, you must deactivate the job for the profile. For information about active and inactive jobs, see “Configuring a job for a profile”.

Procedure 75:Deleting a profile

Step Action


2 Click on the tab of the network element which contains the profile you want to delete.


4 In the MOID Builder window, select the profile from the Profile drop-down list.

5 Click on Delete.

6 In the Delete window, click on Yes.




Security administration 6This chapter contains information and procedures for administration of security features in W-NMS.

W-NMS provides:

• operating system (OS) hardening

• optional OS hardening features

• the audit trail

• OpenSSH support

• access control

• account password management

Table 9 shows the administrative procedures in this chapter for each of the security enhancements:

Table 9: Security administration procedures

Security Enhancement Procedure

OS hardening Procedure 76: Hardening the OS

Procedure 77: Unhardening the OS

Procedure 78: Verifying the current OS hardening package

optional OS hardening features

Procedure 79: Activating or deactivating an optional OS hardening feature

the audit trail Procedure 80: Accessing the audit trail configuration menu

Procedure 81: Enabling the audit trail

Procedure 82: Disabling the audit trail

OpenSSH Procedure 83: Verifying that the OpenSSH server is running

Procedure 84: Stopping or starting the OpenSSH server


156 Security administration Nortel Networks Confidential

Note: Some of the procedures in this chapter cause a brief interruption of communication between the network elements and the operations, administration, and maintenance (OAM) servers.

OS hardening 6This section contains procedures for administration of the OS hardening for W-NMS. The OS hardening is applied to OAM servers and clients that have the Solaris* 8 operating environment software installed.

What the OS hardening doesThe OS hardening:

• disables unused services

• removes unused or unnecessary users

• strengthens access control

• secures network communication

Disable unused servicesSome services are enabled by default when the operating system is installed. These services pose potential security risks. Disabling services that are not required by the OAM applications strengthens security on the servers.

The OS hardening disables potentially exploitable services from the inetd.conf file.

The OS hardening also disables unused services from the start up directories (/etc/rc*.d/). These services have known security risks.

Remove unused usersThe base Solaris 8 operating environment provides several default user names. The OS hardening removes the user names that are not required for network operation.

Strengthen access controlLimiting and controlling access to the servers is an important aspect of security. The OS hardening limits access to the root user on the system console. Users that require root access from a remote location to a server must log in to the server with their own login credentials and then switch user to the root user. This will leave an entry in the system logs that is useful in investigations.


Nortel Networks Confidential The OS hardening log files 157

Secure network communicationFile transfer protocol (FTP) is used to transfer data over the network. FTP does not secure the data being transferred. The OS hardening prevents the root user from using the inbound FTP service and allows only authorized users to use the inbound FTP service.

The OS hardening log files 6When you run the OS hardening (Procedure 76) or OS unhardening (Procedure 77) scripts, a log file is created that documents the changes made to the OS files and services. The most recent log file is in /SECURITY/Current_Release/log/Last.log. Historical log files are in /opt/nortel/logs/osharden/OS_Hardening_history.log.

The log files provide detailed information about the changes made to the OS files at the time the OS hardening was applied. You can use this information to see if changes were made to the OS files other than the ones made by the OS hardening or OS unhardening scripts. There are no log files generated for the optional OS hardening features.

Hardening the OS 6This procedure runs the hardening scripts. Perform this procedure on each of the following W-NMS servers:

• main server (primary and secondary)

• performance server

• SCS server

• Server of Clients (SOC)

• Solaris client workstation

• MetaSolv Network Mediation Server (MNMS)

• MetaSolv Policy Services Server (MPS)

RequirementsYou must perform this procedure at the system console for the server. Do not perform this procedure through a remote session.

Procedure 76:Hardening the OS

Step Action

1 At the system console, log in using the root user ID.




init s

The system shuts down, starts up in single user mode, and prompts you for the root password.

3 Enter the root password.

Messages display indicating that the system is in single user mode.

4 Enter:

cd /SECURITY/Current_Release/bin

5 Enter:

./Solaris8_OsHarden

A menu displays with the server(s) to harden or to exit. An example for the main server follows:

OSH OAM 4.2 Server OS Security Hardening Menu

1) Main Server

2) Exit

6 Enter:

1

The hardening scripts are run. Any attempt to interrupt execution of the hardening scripts is ignored until the hardening is complete. For example, the commands Ctrl C, Ctrl Z, or Ctrl \ have no effect.

Note: If you enter an invalid choice three consecutive times, the script exits.

7 The following message displays:

Reboot is required after OS hardening. Do you want to reboot now (default=y) [y/n]?

8 Enter y and press the Enter key.

The system reboots.

9 Look at the OS hardening log file found in /SECURITY/Current_Release/log/Last.log to verify that the scripts have run successfully.

Procedure 76:Hardening the OS (continued)

Step Action


Nortel Networks Confidential Unhardening the OS 159

Unhardening the OS 6This procedure returns the OS services back to the state they were in prior to hardening the OS.

RequirementsYou must perform this procedure at the system console for the server. Do not perform this procedure through a remote session.

Removing the Performance Meter icon from the CDEThe following steps explain how to remove the Performance Meter icon from the Front Panel of the Common Desktop Environment. The OS hardening disables the kernel statistic server which in turn affects the Performance Meter, causing it to report CPU usage incorrectly. To avoid confusion, remove the Performance Meter icon from the Front Panel.

10 Login using the root user ID.

The Common Desktop Environment (CDE) opens.

11 Right-click on the Performance Meter icon found in the Front Panel.

The Performance Meter object menu opens.

12 Select Delete Icon from the menu.

The Workspace Manager - Delete Icon window opens with the following message:

Are you sure you want to delete this icon control?


The Workspace Manager - Customize Front Panel window opens with the following message:

The Workspace Manager has to be restarted for the changes to take effect.


The Workspace Manager restarts. The Performance Manager icon does not appear in the Front Panel.

You have completed hardening the OS.

Procedure 76:Hardening the OS (continued)

Step Action



Note: The system accounts that are deleted as part of the hardening process are not reinstated by performing this procedure.

Procedure 77:Unhardening the OS

Step Action

1 At the system console, log in using the root user ID.


init s

The system shuts down, starts up in single user mode, and prompts you for the root password.

3 Enter the root password.

Messages display indicating that the system is in single user mode.

4 Enter


5 Enter:

./Solaris8_OsUnHarden

A menu displays with the choices of the server to unharden or to exit. An example for the main server follows:

OSH OAM 4.2 Server OS Security UnHardening Menu

1) Main Server

2) Exit

6 Enter:

1

The scripts to unharden the OS run. Any attempt to interrupt execution of the scripts is ignored until the execution is complete. For example, the commands Ctrl C, Ctrl Z, or Ctrl \ have no effect.

Note: If you enter an invalid choice three consecutive times, the script exits.

7 The following message displays:

Reboot is required after OS hardening. Do you want to reboot now (default=y) [y/n]?

8 Enter y and press the Enter key.

The system reboots.


Nortel Networks Confidential Unhardening the OS 161

9 Look at the OS hardening log file found in /SECURITY/Current_Release/log/Last.log to verify that the scripts have run successfully.

You have completed unhardening the OS.

Procedure 77:Unhardening the OS (continued)

Step Action



Verifying the current OS hardening package 6Perform this procedure to confirm the version of the OS hardening package that is installed and hardened on a server.

Procedure 78:Verifying the current OS hardening package

Step Action

1 Log into the server using a user ID that is not the root user ID.

2 Enter:

su -root

<root password>


3 Enter:



Nortel Networks Confidential Optional OS hardening features 163

Optional OS hardening features 6This section describes the optional OS hardening features that you can activate to suit your security requirements. These features are separate from the ones previously described and must be activated and deactivated individually.

If you are performing an upgrade of W-NMS, you must deactivate the optional OS hardening features that are activated, before performing the upgrade.

4 Enter:

./showstatus

The status of the system is displayed. The following sample messages are displayed if you are working on the main server.

If the main server has the hardening package installed and the server has been hardened, the following message is displayed:

The system is hardened with version “MAIN_V04_02.E01”, patch level “none”.

The system is installed with version “MAIN_V04_02.E01”, patch level “none”.

If the main server has been hardened with the hardening package with patch ID 20045101 (meaning that the patch was released in 2004, week 51, first patch of the week), the following message is displayed:

The system is hardened with version “MAIN_V04_02.E01”, patch level “20045101”.

The system is installed with version “MAIN_V04_02.E01”, patch level “20045101”.

If the system is not hardened but has the hardening package installed, the following message is displayed:

The system is not hardened.

The system is installed with version “MAIN_V04_02.E01”, patch level “none”.

You have completed verifying the current OS hardening package.

Procedure 78:Verifying the current OS hardening package (continued)

Step Action



Table 10 shows the scripts for the optional features.

Table 11 shows the servers on which you can run the optional OS hardening scripts.

Activating or deactivating an optional OS hardening feature 6Use this procedure to activate or deactivate one of the optional OS hardening

Table 10: Optional feature scripts

Feature Activate script Deactivate script User Id

disable graphical login support for local or remote console

/SECURITY/supplement/disable_X11

/SECURITY/supplement/enable_X11

root

disable the SMTP mail server /SECURITY/supplement/disable_sendmail

/SECURITY/supplement/enable_sendmail

root

disable router discovery daemon /SECURITY/supplement/disable_rdisc

/SECURITY/supplement/enable_rdisc

root

enable Oracle valid node checking

/opt/nortel/3rd_party/oracle_supplement/enable_valid_node_check_smc

/opt/nortel/3rd_party/oracle_supplement/disable_valid_node_check_smc

smcorau

enable NFS server /SECURITY/supplement/enable_NFSserver

SECURITY/supplement/disable_NFSserver

root

enable autoFS /SECURITY/supplement/enable_autofs

/SECURITY/supplement/disable_autofs

root

Table 11: Optional features applicable servers

Feature Main PM SOC Client SCS MNMS MPS CEM

disable graphical login support for local or remote console

X X X X X X X X

disable the SMTP mail server X

disable router discovery daemon X X X X X X X X

enable Oracle valid node checking Xa

a. primary main server only

enable NFS server Xb

b. primary main server only, configured with SRS function by auto install script

enable autoFS X X X X


Nortel Networks Confidential The audit trail 165

features. Refer to Table 10 for the path and script name and user Id to use.

The audit trail 6An audit trail is a series of records of computer events. These records contain

Procedure 79:Activating or deactivating an optional OS hardening feature

Step Action

1 Log into the server using a user Id that is not the root user Id. Refer to Table 11 to ensure that you are logging on to a server for which the script is applicable.

2 Enter:

su -<User Id>

where <User Id> is the user Id for the script you want to activate or deactivate from Table 10.

3 Enter:

<password>

where <password> is the password for the user Id

4 Enter:

<path and script name>

where <path and script name> is the path and script name for the feature you want to activate or deactivate from Table 10

If you are activating the disable graphical login support for local or remote console feature, a warning message appears, followed by the option to abort the activation:

Please select the number next to the menu selection:

1) Continue execution

2) Exit

5 If you received the warning message in step 4, and you want to continue with the activation, enter:

1


Graphical support for the system console has been successfully disabled.

You have completed activating or deactivating the optional OS hardening feature.



information about an operating system, an application, or user activities.

The W-NMS security enhancements use the Solaris operating environment capability to audit activity on a network. The auditing ability is part of the Solaris SunShield Basic Security Module (BSM). The BSM monitors certain events on an OAM server and converts the information into audit log files. Some of the data in the audit log files is sent to the Centralized Security Audit Logging (CSAL) system. The CSAL system is a service in the Network Services Platform that manages the network audit log files. For more information about CSAL, see the Wireless Network Management System Network Services Platform User Guide, 411-5221-211.

For information about the events that are logged in the audit log files, see the section titled “Events audited”. For a list of events that are sent to CSAL, see Table 15.

Scope of the audit trail 6The audit trail supports the following servers:

• main

• performance

• Server of clients

Events auditedThere are three levels of event auditing. When the audit level is set to 1, the events in Table 12 are logged in the audit log files. Level 1 is the default audit level. When the audit level is set to 2, the events in Table 12 and Table 13 are logged in the audit log files. When the audit level is set to 3, the events in Table 12, Table 13, and Table 14 are logged in the audit log files. For information about setting the audit level, see Procedure 80.

For more information about the audit events, refer to the Solaris SunShield Basic Security Module documentation.

Table 12: Level 1 auditing

AUE_ACLSET AUE_FCHROOT AUE_rshd

AUE_admin_authenticate AUE_ftpd AUE_SETAUDIT

AUE_AUDITON_GETCAR AUE_GETAUDIT AUE_SETAUDIT_ADDR

AUE_AUDITON_GETCLASS AUE_GETAUDIT_ADDR AUE_SETAUID

AUE_AUDITON_GETCOND AUE_GETAUID AUE_SETEGID

AUE_AUDITON_GETCWD AUE_inetd_connect AUE_SETEUID


Nortel Networks Confidential Scope of the audit trail 167


AUE_AUDITON_GETKMASK AUE_KILL AUE_SETGID

AUE_AUDITON_GPOLICY AUE_LCHOWN AUE_SETGROUPS

AUE_CHDIR AUE_login AUE_SETPGRP

AUE_CHMOD AUE_logout AUE_SETREGID

AUE_CHOWN AUE_mountd_mount AUE_SETREUID

AUE_CHROOT AUE_mountd_umount AUE_SETUID

AUE_ENTERPROM AUE_NICE AUE_su

AUE_EXITPROM AUE_passwd AUE_SYSTEMBOOT

AUE_FACLSET AUE_PRIOCNTLSYS AUE_telnet

AUE_FCHDIR AUE_rexd AUE_UTIME

AUE_FCHMOD AUE_rexecd AUE_UTIMES

AUE_FCHOWN AUE_rlogin AUE_VTRACE

AUE_ACCESS AUE_EXIT AUE_OPEN_RWC

AUE_allocate_fail AUE_FORK AUE_OPEN_RWT

AUE_allocate_succ AUE_FORK1 AUE_OPEN_RWTC

AUE_CORE AUE_halt_solaris AUE_OPEN_W

AUE_CREAT AUE_init_solaris AUE_OPEN_WC

AUE_create_user AUE_LINK AUE_OPEN_WT

AUE_cron_invoke AUE_listdevice_fail AUE_OPEN_WTC

AUE_crontab_create AUE_listdevice_succ AUE_poweroff_solaris

AUE_crontab_delete AUE_MKDIR AUE_READLINK

AUE_crontab_mod AUE_MKNOD AUE_RENAME

AUE_deallocate_fail AUE_modify_user AUE_RMDIR

AUE_deallocate_succ AUE_MOUNT AUE_STATFS

AUE_delete_user AUE_MUNMAP AUE_SYMLINK

AUE_disable_user AUE_OPEN_RC AUE_uadmin_solaris

AUE_enable_user AUE_OPEN_RT AUE_UMOUNT2



Table 15 lists audit events in the audit log files that are translated and sent to CSAL.

The audit log files 6The name of a completed audit log file has the following format:

<startyyyymmddhhmmss>.<endyyyymmddhhmmss>.<servername>

AUE_EXEC AUE_OPEN_RTC AUE_UNLINK

AUE_EXECVE AUE_OPEN_RW AUE_VFORK


AUE_CLOSE AUE_LSTAT AUE_STAT

AUE_FCNTL AUE_OPEN_R

Table 15: Events sent to CSAL

AUE_login AUE_rshd AUE_rexd

AUE_logout AUE_su AUE_ftpd

AUE_telnet AUE_rexecd AUE_admin_authenticate

AUE_rlogin AUE_passwd

DO NOT MODIFY THE FOLLOWING FILES:/etc/security/audit_user/etc/security/audit_class/etc/security/audit_control/etc/security/audit_eventModifying these files can cause the audit trail to malfunction.


Nortel Networks Confidential The audit log files 169

See Table 16 for descriptions of the parameters.

An example of a completed audit log file is: 20020426162021.20020426162729.wngc01b

If the audit log is still active (records are being written to it), then it is named <startyyyymmddhhmmss>.not_terminated.<servername>. An example of an active audit log file is:

20020426162021.not_terminated.wngc01b

The audit trail periodically searches for audit logs that have been left open by the BSM and attempts to close them. The time that the file is closed is used in the <endyyyymmddhhmmss> parameter in the file name and an "R" is added to indicate that this is a file that has been recovered. The data in this file may be unreadable. An example of a recovered audit log file is

20020426162021.20020426162729R.wngc0b1

The audit log files are stored in one of the following directories:

• /opt/nortel/data/audit/secondary

• /var/audit/primary

The BSM alternates between the two previously mentioned directories when it stores the audit log files.

Archiving the audit log filesTo support the archive and retrieval feature of W-NMS, the audit log files are moved to a directory named /opt/nortel/data/audit/archive/<yyyymmdd>, where <yyyymmdd> is the year, month and day that the audit log files are

Table 16: Parameter definitions

Parameter Description

<startyyyymmddhhmmss> is the year, month, day, hour, minute, and seconds that the first record was written to the file. The ddhhmmss is Greenwich mean time.

<endyyyymmddhhmmss> is the year, month, day, hour, minute, and seconds that the last record was written to the file. The ddhhmmss is Greenwich mean time.

<servername> is the name of the server being audited



created. The audit log files are compressed using gzip when they are moved to the archive directory and have a .gz extension.

For more information about archive and retrieval, see the Wireless Network Management System Backup and Restore User Guide, 411-8111-521.

Accessing the audit trail configuration menu 6This procedure allows you to:

• change the CSAL server connection information

• change the schedule for sending audit logs to CSAL

• send the existing audit logs to CSAL

• stop or start BSM auditing

• find out how to change the auditing level

Procedure 80:Accessing the audit trail configuration menu

Step Action


2 Enter:

su -root

<root password>


3 In a terminal window command line, enter the following command:

/opt/nortel/shell/AuditTrail/auditMenu

The Audit Trail Configuration Menu displays.The information in brackets under each menu item shows the current value or status of the item.

Choice 1: Update the CSAL server connection information

4 Enter:

1

The following prompt displays:

Enter new IP address:


Nortel Networks Confidential Accessing the audit trail configuration menu 171

5 Enter the IP address of the server where the CSAL database is located. This is usually the main server.


Enter port [1099]:

6 Press the Enter key to accept the default port of 1099. 1099 is the default port that is monitored by CSAL.


[Please hit ENTER to continue]

7 Press the Enter key.

The main Audit Trail Configuration Menu displays. The new IP address and port number show up under menu item 1.

Choice 2: Update the frequency for sending audit logs to CSAL

8 Enter:

2


Enter new frequency in hours.Valid frequencies are 1, 2, 3, 4, 6, 8, 12, 24.Please enter new frequency:

9 Enter the frequency with which audit logs are sent to the CSAL. For servers that have a high activity level, such as the performance server, enter 4 or higher.


Updating frequency now.... done[Please hit ENTER to continue]


The main Audit Trail Configuration Menu displays. The new frequency shows up under menu item 2.

Procedure 80:Accessing the audit trail configuration menu (continued)

Step Action



Choice 3: Send all current audit logs to CSAL now

11 Enter:

3


MUST enter ’y’ or ’Y’ to confirm (no):

12 Enter y or Y.


Activating sending logs to CSAL .... done[Please hit ENTER to continue]


The main Audit Trail Configuration Menu displays. The status of the process shows up under menu item 3. “idle” means that nothing is being sent CSAL at the moment. “ongoing” means that the audit log files are currently being sent to CSAL.

Choice 4: Stop/Start BSM auditingThis menu item allows you to temporarily stop the BSM auditing without having to disable the BSM. Disabling the BSM requires a reboot of the server which causes an interruption of all applications running on the server. This menu item also allows you start the BSM auditing without having to enable the BSM.

14 Enter:

4


Start BSM Auditing?Enter Y or y to confirm (no):

15 Enter y or Y.


Activating BSM auditing now .... done[Please hit ENTER to continue]


Step Action


Nortel Networks Confidential Accessing the audit trail configuration menu 173


The main Audit Trail Configuration Menu displays. The new status of BSM auditing shows up under menu item 4. “enable” means that the BSM is enabled. “disable” means that the BSM is disabled. “inactive” means that BSM auditing is stopped. “active” means that auditing is currently running (the BSM can only be active if it is enabled)

Choice 5: How to change auditing levelThis menu item explains how to change the auditing level. Valid auditing levels are 1, 2, or 3. See the section titled “Events audited” for lists of the audit events associated with each auditing level. If you set the auditing level to 3, you must ensure that there is enough disk space to accommodate the large audit log files that are generated.

17 Enter:

5

The following information displays:

5. How to change auditing level(current auditing level:1)

Instructions to change auditing level

1. Logon to server from console as root user.2. Bring down server to System Administrative mode.

> init 13. Relogin as root user from console.4. Go to this directory

> cd /opt/nortel/shell/Audit Trail5. Invoke the BSMrun script as follow to change audit level.

> ./BSMrun auditlevel6. Follow onscreen instructions to complete.



The main Audit Trail Configuration Menu displays.

End of procedure.


Step Action



Enabling the audit trail 6Perform this procedure to enable the audit trail. This procedure enables the BSM. Do not use the bsmconv script to enable the BSM. The bsmconv script does not include the customized configuration required for the W-NMS audit trail.

RequirementsYou must perform this procedure at the system console of the server on which you want to enable the audit trail.

Procedure 81:Enabling the audit trail

Step Action

1 Log into the server using the nortel user Id.

2 Stop the OAM server processes. Enter the following command:

/opt/nortel/shell/sysmgt/wam_stopall.sh -d

3 Wait for all processes to stop. Enter the following command to verify that all processes have stopped:

/opt/nortel/shell/sysmgt/wam_checkall.sh


Verify - Nb started groups : 0

4 Enter:

exit

5 Enter:

su -root

<root password>


6 Change the run level to system administrator mode. Enter:

init 1

The following message is displayed:

Change to state 1 has been completed

Type Control-d to proceed with normal startup,

(or give root password for system maintenance):


Nortel Networks Confidential Enabling the audit trail 175

7 Enter the password for the root user ID.

A message similar to the following is displayed:

single-user privilege assigned to /dev/console.

Entering System Maintenance Mode

8 Enter:

/opt/nortel/shell/AuditTrail/BSMRun enable

Messages related to enabling the BSM display, followed by:

Do you want to proceed to enable SunSHEILD BSM? [y/n]:

9 Enter:

y

Messages related to enabling the BSM display, followed by:

Press [Enter] key to continue


A series of message display, followed by the Update auditing level menu and the message:

Please select new auditing level [1-3]:

11 Enter 1, 2, or 3, depending on the level of auditing you want.

A message stating that the auditing level is being set displays, followed by:




Successfully completed enabling SunSHIELD BSM.

Reboot is required before system changes can take effect. Do you want to reboot now (default = y)? [y/n]:

13 Press the Enter key to reboot the system.

14 Wait for the reboot to finish. Log into the server using the nortel user Id.

Procedure 81:Enabling the audit trail (continued)

Step Action



Disabling the audit trail 6Perform this procedure to disable the audit trail. This procedure disables the BSM. Do not use the bsmuconv script to disable the BSM.

RequirementsYou must perform this procedure at the system console of the server on which you want to disable the audit trail.

15 Start the OAM server processes. Enter:

/opt/nortel/shell/sysmgt/wam_startall.sh -a

16 Verify that all processes have started. Enter:



Verify - Nb stopped groups : 0

17 Enter:

exit

Procedure 82:Disabling the audit trail

Step Action

1 Log into the server using the nortel user Id.

2 Stop the OAM server processes. Enter the following command:

/opt/nortel/shell/sysmgt/wam_stopall.sh -d

3 Wait for all processes to stop. Enter the following command to verify that all processes have stopped:



Verify - Nb started groups : 0

4 Enter:

exit

Procedure 81:Enabling the audit trail (continued)

Step Action


Nortel Networks Confidential Disabling the audit trail 177

5 Enter:

su -root

<root password>


6 Change the run level to system administrator mode. Enter:

init 1


Change to state 1 has been completed

Type Control-d to proceed with normal startup,

(or give root password for system maintenance):

7 Enter the password for the root user ID.

A message similar to the following displays:

single-user privilege assigned to /dev/console.

Entering System Maintenance Mode

8 Enter the following command:

/opt/nortel/shell/AuditTrail/BSMRun disable

A series of messages related to the BSM display, followed by:

Do you want to proceed to disable SunSHIELD BSM? [y/n]:

9 Enter:

y

A series of messages related to the BSM display, followed by:

Reboot is required before system changes can take effect. Do you want to reboot now (default = y)? [y/n]:

10 Enter:

y

11 Wait for the reboot to finish. Log into the server using the nortel user Id.

Procedure 82:Disabling the audit trail (continued)

Step Action



OpenSSH 6OpenSSH is a version of the secure shell (SSH) protocol suite of network connectivity tools. W-NMS supports the following OpenSSH features:

• sftp and ssh supporting SSH2 protocol

• strong encryption

• strong authentication

• FTP port forwarding

• interoperability

• X11 forwarding

• data compression

W-NMS supports the commands and programs shown in the following table. For more information about these commands and programs go to the following Web address: http://www.openssh.org/.

12 Start the OAM server processes. Enter:

/opt/nortel/shell/sysmgt/wam_startall.sh -a

13 Verify that all processes have started. Enter:



Verify - Nb stopped groups : 0

14 Enter:

exit

You have disabled the audit trail.

Table 17: Supported OpenSSH commands

Command or program Description

ssh Client program used to log into another machine or to execute commands on another machine. Also known as slogin. Use ssh in place of the rlogin, rsh, and telnet client programs.

scp Copies files securely from one machine to another. Use scp in place of the rcp client program.

Procedure 82:Disabling the audit trail (continued)

Step Action


Nortel Networks Confidential Verifying that the OpenSSH server is running 179

Verifying that the OpenSSH server is running 6Perform this procedure to verify that the OpenSSH server is running.

sftp Secure file transfer program that works over the SSH2 protocol. Use sftp in place of the ftp client program.

sshd Server program that runs on the server machine. sshd listens for connections from client machines. When it receives a connection it performs authentication and starts serving the client. Use sshd in place of rlogin/rsh, telnet, and ftp services.

ssh-agent Authentication program that holds private keys used for public key authentication (RSA, DSA).

ssh-add Tool that registers new keys with the authentication agent

ssh-keygen Tool that generates host keys and user authentication keys.

ssh-keyscan Utility for gathering public host keys from a number of hosts.

sftp-server SFTP server subsystem started automatically by sshd.

Procedure 83:Verifying that the OpenSSH server is running

Step Action


2 Enter:

su -root

<root password>


3 Enter:

ps -ef | grep sshd

A response similar to the following displays:

root 14986 1 0 14:09:04 ? 0:01 /opt/nortel/3rd_party/NNobsdssh/sbin/sshd

You have verified that the OpenSSH server is running.

Table 17: Supported OpenSSH commands

Command or program Description



Stopping or starting the OpenSSH server 6This procedure explains how to stop or start the OpenSSH server.

Access control 6W-NMS allows you to control access to the OAM system features and tools by setting user permissions for resources and their associated functions. Table 18 shows the resources for the local session launch resource type. Table 19 shows the resources for remote session launch resource type.

If you give a user group permissions to a particular resource, it allows the users in the user group to control or change settings for a feature or tool. The Description column in the tables is an explanation of what the resource controls. You can use this information to help you decide the resource permissions settings for a particular user group.

The Admin user only column in the tables shows the resources that apply if you are the Admin user in NSP. “yes” means that the permissions apply only to the Admin user. If you are not the Admin user you will not have permissions to the Resource, even if they are granted to the user group you belong to. “no” means that any user can have permissions to the resource.

Procedure 84:Stopping or starting the OpenSSH server

Step Action


2 Enter:

su -root

<root password>


Stopping the OpenSSH server

3 Enter:

/etc/rc3.d/S25openssh.server stop

Starting the OpenSSH server

4 Enter:

/etc/rc3.d/S25openssh.server start

You have stopped or started the OpenSSH server.


Nortel Networks Confidential Access control 181

You set permissions for these resources using the Access Control window in Network Services Platform. For more information about setting access control permissions, see the Wireless Network Management System Network Services Platform User Guide, 411-5221-211.

Table 18: Local session launch resources

Resource Description Admin user only

AC Group Maintenance

Allow deletion or renaming of a user group; available in the Security menu.

yes

AccessMODIFY Allow access to update Radio Access plug-ins (menu items that allow you to modify the network).

no

AccessREAD Allow access to read only Radio Access plug-ins (menu items that allow you to read information).

no

AdminTool Allow NSP custom command configuration. yes

Advanced Alarm Filter Administration

Allow management of private advanced alarm filters. no

Alarm Stream Management

Allow turning the alarm stream management on or off. no

Alarm Stream Rule Set

Allow creation of rule sets to define the content of the managed alarm stream.

yes

Alarm Summary Show alarm summary counts in navigator, network banner and the resource browser.

no

AlarmHelpPlugin Allow launch of Selected Item Help from alarms in NSP Alarm Manager.

no

Backup Dialog Plugin

Allow display of a message notifying the NSP user of a backup in progress. Message displays during a backup on the primary main or secondary main servers.

no

Cem Plugin Allow launch of the CEM from network element icon or from an alarm. no

Configure Alarm Colours

Allow modification of the alarm severity colors. no

Default Allow default permissions for newly added resources and newly added user groups.

yes



Fault Allow launch of the following network element specific applications from the network element icon:

Policy Services (NE type Id 274): Launch Policy Services Web Admin

Net Guardian (NE type Id 284): Launch NETG Web Client

UNPM (NE type Id 311): Launch UNPM App Client

GGSN (NE type Id 319): Launch SCS Client

no

Fault Details Enable or disable the Show Alarms option available in the navigator, resource browser, and the fault menu.

no

Network Definition Tool

Allow Edit, delete & create of Links and NE Properties no

Hard Limit Allow setting of the fault hard limit. The fault hard limit is the maximum number of alarms that are loaded into the alarm manager.

no

Node Allow launch of the listed applications from the network element icon:

e-Mobility Location Center (NE type Id 272): Launch OAM&P Web GUI

VPN Router (NE type Id 304): Launch Contivity VPN Client

Border Gateway (NE type Id 307): Launch Contivity Border Gateway Client

IP Services Edge Router 5500 (NE type Id 191): Launch SCS Client

no

Node State Allow display of node state indicators. no

PrOptima Allow launch of the NIMS-PrOptima* for W-NMS web client from NSP. no

sysmgt Allow launch of the SMC from NSP health bar. no

TT Details Allow creation of a trouble ticket and viewing of the Trouble Ticket column in the Alarm Manager.

no

Warning Banner Editing

Allow edit of the security warning banner from Security Menu. no

Table 18: (continued)Local session launch resources




Change Password Application

Allow change of the NSP password. no

Technology Layer Filter

Allow filtering of network elements by technology layer in the Resource Browser.

yes

Table 19: Remote session launch resources


AdminTool Allow launch of the following tools:

NSP Application Config and Monitoring ManagerUser Administration GUI (iPlanet) from NSP Radius Administration GUI from NSP

yes

Configuration Allow launch of the following tools from the Configuration menu in NSP:

MDM ToolsetMDM Toolset (Security)MDM Toolset for AdministrationADC GUI from Performance server <hostname>

noyesyesno

Table 18: (continued)Local session launch resources




Controller Allow launch of the listed applications from the network element icon:

RADIUS (NE type Id 118): MDM Toolsets, Discover Data Devices, Edit Community Strings

IP Services Edge Router 5500 (NE type Id 191): MDM Toolsets, Discover Data Devices, Edit Community Strings

SS7 IP Gateway (NE type Id 247): MDM Toolsets, Discover Data Devices, Edit Community Strings

PP8600 Series (NE type Id 248): MDM Toolsets, Discover Data Devices, Edit Community Strings, Login to Controller, Auto Login to Controller

Ethernet Switch 450 (NE type Id 249): MDM Toolsets, Discover Data Devices, Edit Community Strings, Login to Controller, Auto Login to Controller

BPS 2000 (NE type Id 250): MDM Toolsets, Discover Data Devices, Edit Community Strings, Login to Controller, Auto Login to Controller

MNM (NE type Id 267): MDM Toolsets, Discover Data Devices, Edit Community Strings

Comverse LIGD (NE type Id 269): MDM Toolsets, Discover Data Devices, Edit Community Strings

e-Mobility Location Center (NE type Id 272): MDM Toolsets, Discover Data Devices, Edit Community Strings

Policy Services (NE type Id 274): MDM Toolsets, Discover Data Devices, Edit Community Strings

Web Switch 184 (NE type Id 276): MDM Toolsets, Discover Data Devices, Edit Community Strings

Net Guardian (NE type Id 284): MDM Toolsets, Discover Data Devices, Edit Community Strings

no

Table 19: (continued)Remote session launch resources




Controller VPN Router (NE type Id 304): MDM Toolsets, Discover Data Devices, Edit Community Strings

Border Gateway (NE type Id 307): MDM Toolsets, Discover Data Devices, Edit Community Strings

FUNKSBR (NE type Id 310): MDM Toolsets, Discover Data Devices, Edit Community Strings

UNPM (NE type Id 311): MDM Toolsets, Discover Data Devices, Edit Community Strings

no

Default Allow default permissions for newly added resources and newly added user groups.

yes

Fault Allow launch of the listed applications from the network element icon:

MNM (NE type Id 267): Telnet to network element

RADIUS (NE type Id 118): Launch Radius Admin from network element icon, telnet client to Radius

Policy Services (NE type Id 274): Login to network element from icon

Net Guardian (NE type Id 284): Login to network element from icon

FUNKSBR (NE type Id 310): Launch Funksbr Administration, Login to network element

UNPM (NE type Id 311): Login to network element

GGSN (NE type Id 319): Login to network element

no





Login_to_NE Allow log into the following network elements from the network element icon:

Multiservice Switch 7000 (NE type Id 137): Login to NE


HLR (NE type Id 215): Login to NE

MSC (NE type Id 214): Login to NE

IWF (NE type Id 321): Login to NE



MGW (NE type Id 3744): Login to NE

UMTS SGSN (NE type Id 381): Login to NE

no

Node Allow launch of the listed applications from the network element icon:

SS7 IP Gateway (NE type Id 247): Login to network element

PP8600 Series (NE type Id 248): Login to network element

Ethernet Switch 450 (NE type Id 249): Login to network element

BPS 2000 (NE type Id 250): Login to network element

Mobile Location Center (NE type Id 272): Login to network element

IP switch (NE type Id 276): Login to network element

VPN Router (NE type Id 304): Login to network element

Border Gateway (NE type Id 307): Login to network element

no




Nortel Networks Confidential Account password management 187

Account password management 6This section explains how to change the passwords for the accounts on the W-NMS servers. The password files that are stored on the W-NMS servers are encrypted.

It is recommended that you change W-NMS account passwords at regular intervals, including after W-NMS installation or upgrade. After changing a password, verify that the change was successful.

The accounts documented in this section may or may not be applicable for your network, depending on your W-NMS deployment configuration.

Default passwords 6Table 20 shows the default password and servers for the UNIX accounts. pMS is the primary main server, sMS is the secondary main server, PS is the performance server, SOC is the server of clients server, and SRS is the software repository server. A default password of —none— indicates that there is no default password. A password must be specified when the application is installed.

Table 20: UNIX accounts

Account Default password Exists on

pMS sMS PS SOC SRSa

admin oam_admin X X X

admin X

iutadmin —none— X X X X

master oam_master X X X

master X

netmgr oam_netmgr X X X X

nortel oam_nortel X X X X

operator oam_operator X X X

operator X

root —none— X X X X

apache oam_apache X X X

dbsa oam_dbsa X X X



oracle oam_oracle X X

orbixusr —none— X X X

dfsnortel nortelwifmk X X X X

mdmadmin nortel X X X

cemftp —none— X X

ttbuser oam_ttbuser X X

domadmin oam_domadmin X

hlradmin oam_hlradmin X

hlrops oam_hlrops X

PPXfer nortelPP X

SMCAdmin p4smcA X

SMCneop —none— b X

smcorau p4smcU X

SMCUser p4smcU X

pm_omcs oam_pm_omcs X

pm_pdi oam_pm_pdi X

anontmpl oam_anontmpl X

ctxnfuse oam_ctxnfuse X

ctxssl oam_ctxssl X

ctxsrvr oam_ctxsrvr X

sridwl sripass X

a. The SRS server is located on the same physical server as the primary main server. b. The password is set to a random value at installation time.

Table 20: UNIX accounts

Account Default password Exists on

pMS sMS PS SOC SRSa


Nortel Networks Confidential Default passwords 189

Table 21 shows the default passwords for the NDS accounts. These accounts exist only on the primary main server.

Table 22 shows the default passwords for accounts related to an application or network element. pMS is the primary main server, sMS is the secondary main server, PS is the performance server, SOC is the server of clients server, and SRS is the software repository server. A default password of —none— indicates that there is no default password. A password must be specified when the application is installed.

Table 21: NDS accounts

Account Default password

admin admin

bkp_usr bkp_usr

nortel nortel

NspUser NspUser

sdmuser sdmuser

Table 22: W-NMS application accounts

Account Default password Exists on Procedure

administrator (for NIMS PrOptima

—none— PS “Changing the password for administrator”

administrator (for install, upgrade GUI)

jollyjumper pMS, sMS, PS,SOC

Procedure 98

demo —none— PS Procedure 100

BTS telnet user —none— pMS, sMS Procedure 101

BTS TIL user —none— pMS, sMS Procedure 102

CEM ftp user —none— pMS, sMS Procedure 103

BTSXfer See note a pMS, sMS not applicable

connection to SCS server

—none— pMS, sMS “Changing the password for the GGSN device inventory system”

hfbguest az67hfbnortel pMS Procedure 92

other MDM accounts see Table 23



Changing account passwords 6This section contains procedures on how to change the passwords for each of the W-NMS accounts. The first two procedures in this section explain how to change the password for a UNIX account (Procedure 85)and for an NDS account (Procedure 86). They are intended to be used with the other procedures in this section to change the password for a specific account.

Changing the password for a UNIX accountThis procedure changes the password for a UNIX account in W-NMS. This procedure is referenced by the other procedures in this section, where there is a requirement to change the password for a UNIX account.

nortel in NIMS-PrOptima

see “Changing the password for the nortel account used by NIMS-PrOptima for W-NMS”

omc —none— PS Procedure 105

usp user —none— pMS, sMS Procedure 103

a. The password for BTSXfer cannot be changed so it is not shown.

SOME UNIX ACCOUNTS DEPEND ON OTHER W-NMS ACCOUNTSBefore performing Procedure 85, refer to the specific password change procedure for the account whose password you want to change. The procedure explains if there are other accounts that are affected when the UNIX password is changed.

Table 22: W-NMS application accounts

Account Default password Exists on Procedure


Nortel Networks Confidential Changing account passwords 191

Changing the password for an NDS accountThis procedure changes the password for an NDS account. This procedure is referenced by the other procedures in this section, where there is a requirement to change the password for an NDS account. The NDS accounts in W-NMS exist only on the primary main server.

Procedure 85:Changing the password for a UNIX account

Step Action

1 Log into the server on which you want to change the UNIX password, using a user ID that is not the root user ID.

2 Enter:

su - root

3 At the Password prompt, type:

<password>

where <password> is the password for the root user ID.

4 Enter

/usr/bin/passwd <user_id>

where <user_id> is the UNIX user ID for which you want to change the password.

5 At the New password: prompt, enter the new password.

6 At the Re-enter new password: prompt, confirm the new password by entering it again.

7 Log off of the server.

SOME NDS ACCOUNTS DEPEND ON OTHER W-NMS ACCOUNTSBefore performing Procedure 86, refer to the specific password change procedure for the account whose password you want to change. The procedure explains if there are other accounts that are affected when the NDS password is changed.



Procedure 86:Changing the password for an NDS account

Step Action

1 Log into NSP on the primary main server using the account whose password you want to change.

2 From the Security menu, select Change Password.

3 Change and save the password.

4 Log off of NSP.



Accounts on W-NMS servers onlyThe accounts in this section exist on the main (primary and secondary), performance, SOC, T3, or SRS servers only. They do not have any dependencies on network elements in the network.

Changing the password for admin in UNIXSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

Changing the password for admin in NDSThe NDS admin account is associated with the following applications:

• WICL: used in the cmXMLExportNetwork.sh script

• Fault cartridges: used for application launch configuration

Perform the following procedure to change the password for the admin user ID. This procedure changes the password for the NDS account as well as the password stored in the configuration file.

Procedure 87:Changing the password for admin

Step Action

1 Perform Procedure 86 to change the password for the NDS account.

2 Log into the primary main server using the nortel user ID.

3 In the command line, type the following commands:

sh

. /opt/nortel/shell/sysmgt/profile_oam

/opt/nortel/exe/fmk/fmk_crypto.x -s <new password> ALGO1

where <new password> is the new password you specified in step 1.

A text string that is the password in encrypted form displays. It can contain a blank character(s).

4 Open the /opt/nortel/config/wicl/script/common.cfg file in a text editor.

5 Add the following line to the file (Or modify the line, if it already exists.):

WICLSH_WICL_PWD.CRYPTED="<encrypted password>"

where <encrypted password > is the text string output from step 3.

—sheet 1 of 2—



Changing the password for apacheSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

6 Add the following line to the file (If the line already exists in the file, go to the next step.):

WICLSH_WICL_PWD.CRYPTO_ALGO=ALGO1

7 Save the common.cfg file.

Procedure 87:Changing the password for admin

Step Action

—sheet 2 of 2—



Changing the password for bkp_userThe bkp_user account is used to backup and restore the Multiservice Switch. Perform the following procedure to change the password for bkp_usr on the primary main server.

Procedure 88:Changing the password for bkp_usr

Step Action

1 Perform Procedure 86 to change the password for the NDS account.


3 In a terminal window, type the following commands:

sh



where <new password> is the new password. It must match the password of the NDS account you changed in step 1.


4 Open the /opt/nortel/config/wicl/script/common.cfg file in a text editor.

5 Add the following line to the file (Or modify the line if it already exists.):

WICLSH_WICL_BR_PWD.CRYPTED="<encrypted password>"


6 Add the following line to the file (If the line already exists, then go to the next step.):

WICLSH_WICL_BR_PWD.CRYPTO_ALGO=ALGO1

7 Save the /opt/nortel/config/wicl/script/common.cfg file.



Changing the password for cemftpThe cemftp account is used for transferring and storing user preferences on the CEM server.

Perform the following procedure to change the password for the cemftp account on the primary main server or secondary main server. Do not use Procedure 85 to change the password.

Procedure 89:Changing the password for cemftp

Step Action

1 Log into the primary main server or secondary main server using a user ID that is not the root user ID.

2 Type:

su - root


<password>

where <password> is the password for the root user ID

4 In the command line, type:


./cemFtpPasswd


cemftp password change in progress. Please wait...

Password change successful



Changing the password for dbsaThe dbsa account is used to back up and restore the Versant database. Perform Procedure 85 to change the password for dbsa on the primary main or secondary main servers.



Changing the password for dfsnortelThe dfsnortel user exists on the primary main, secondary main, performance, and SRS servers in W-NMS. The dfsnortel user is associated with the logical file system which is used by the following functions:

• import/export CM XML

• upgrade network elements

• audit result

• WICL file management

There are two ways to change the password for dfsnortel. Perform Procedure 90 if you want to use the same password for primary main, secondary main, performance, and SRS servers. Perform Procedure 91 if you want to set a different password for each server.

Procedure 90:Changing the password for dfsnortel

Step Action

1 Perform Procedure 85 to change the UNIX password.

2 Log into the server (primary main, secondary main, performance, or SRS) using the nortel user ID.


sh



where <new password> is the new password. It must match the password for the UNIX account.


4 Open the /opt/nortel/config/fmk/fmk_dfssrv.cfg file in a text editor.

5 Add the following lines to the file (Or modify the lines if they already exist.):

DFS_PASSWORD.CRYPTED="<encrypted password>"

SRS_SERVER_DFS_PASSWORD.CRYPTED="<encrypted password>"


—sheet 1 of 2—



Procedure 91 allows you to set a different password for each of the W-NMS servers for the dfsnortel account.

On each server for which you want to change the password, you must:

1. change the password for the UNIX account

2. update the fmk_dfssrv.cfg file with the passwords for all servers whose passwords you changed

Procedure 91 explains the previously listed steps.

6 Add the following lines to the file (If the line already exists, then go to the next step.):

DFS_PASSWORD.CRYPTO_ALGO=ALGO1

SRS_SERVER_DFS_PASSWORD.CRYPTO_ALGO=ALGO1

7 Save the fmk_dfssrv.cfg file.

8 Perform step 1 through step 7 for each of the primary main server, secondary main server, performance, and the SRS server. Use the same password for all servers.

9 Log into the SMC and restart the CommonServices group.

Procedure 91:Changing the password for dfsnortel on each W-NMS server

Step Action

1 Perform Procedure 85 to change the UNIX password. Perform this on each server (primary main, secondary main, performance, or SRS) whose password you want to change. Make note of each password.

2 For each server whose password you changed in step 1, perform step 3 through step 7:

3 Log into the server using the nortel user ID.

—sheet 1 of 2—

Procedure 90:Changing the password for dfsnortel

Step Action

—sheet 2 of 2—




sh



where <new password> is the new password. It must match the password for the UNIX account on the server.

A text string that is the password in encrypted form is displayed. It can contain a blank character(s).

5 Open the /opt/nortel/config/fmk/fmk_dfssrv.cfg file in a text editor.

Perform step 6 for each server whose password you changed in step 1.

6 Add the following two lines to the file (Or modify the lines, if they already exist.):

<W-NMS server>_DFS_PASSWORD.CRYPTED="<encrypted password>"

<W-NMS server>_DFS_PASSWORD.CRYPTO_ALGO=ALGO1

where <W-NMS server> is one of the following:

i. UMAINSERV1 for the primary main server

ii. UMAINSERV2 for the secondary main server

iii. UPERFSERV1 for the performance server

iv. SRS_SERVER for the SRS server


Example: If you changed the passwords for the primary main server and the SRS server, you must add the following lines to the file:

UMAINSERV1_DFS_PASSWORD.CRYPTED="<encrypted password X>"

UMAINSERV1_DFS_PASSWORD.CRYPTO_ALGO=ALGO1

SRS_SERVER_DFS_PASSWORD.CRYPTED="<encrypted password Y>"


7 Save the fmk_dfssrv.cfg file.

8 Log into the SMC and restart the CommonServices group.

Procedure 91:Changing the password for dfsnortel on each W-NMS server

Step Action

—sheet 2 of 2—



Changing the password for domadminSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.



Changing the password for hfbguestThe hfbguest account is used by the alarmDataExtract.sh script. To change the password for hfbguest, perform the following procedures:

1. Procedure 92: Changing the password for hfbguest in Oracle

2. Procedure 93: Updating alarmDataExtract.cfg

Procedure 92:Changing the password for hfbguest in Oracle

Step Action

1 Log into the primary main server using a user ID that is not the root user ID.

2 Enter:

su - root


<password>


4 In a terminal window, type the following command:

su - oracle

5 Type:

sqlplus ’/ as sysdba’

6 Type:

drop user hfbguest;

create user hfbguest identified by <new password> default tablespace alarms temporary tablespace temp quota unlimited on alarms quota unlimited on alarms_idx;

where <new password> is the new password for hfbguest

7 Type:

grant connect, create session to hfbguest;

grant select on hfbmaster.alarms to hfbguest;

exit



Procedure 93:Updating alarmDataExtract.cfg

Step Action


2 In a terminal window, type the following commands:

sh



where <new password> is the new password that you specified in Procedure 92.


3 Edit the alarmDataExtract.cfg file in the directory /opt/nortel/config/stability.

4 Make sure that the following line appears as shown:

HFB_USER = hfbguest

5 Modify the following line in the file, as shown:

HFB_PASSWORD.CRYPTED="<encrypted password>"


6 Add the following line to the file (If the line already exists, then go to the next step.):

HFB_PASSWORD.CRYPTO_ALGO=ALGO1

7 Save the alarmDataExtract.cfg file.



Changing the password for hlradminSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

Changing the password for hlropsSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

Changing the password for iutadminSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

Changing the password for masterSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

Changing the password for mdmadminSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

Changing the password for netmgrThe netmgr account is used when a launch script is invoked for a fault cartridge. See Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

Changing the password for operatorSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

Changing the password for oracleThe oracle account is used to backup and restore the Mycom Oracle database and to rebuild HFB Oracle database. See Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

Changing the password for orbixusrSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.



Changing the password for PPXferThe PPXfer account is used to perform software downloads between a Multiservice Switch network element and the SRS. Perform the following procedure to change the password for the PPXfer account.

Procedure 94:Changing the password for PPXfer

Step Action



sh



where <new password> is the new password.


3 Open the /opt/nortel/config/access/int_srs.cfg file in a text editor.

4 Add the following line to the file (Or modify the line, if it already exists.):

SRS_SERVER_DFS_PASSWORD.CRYPTED="<encrypted password>"


5 Add the following line to the file (If the line already exists in the file, go to the next step.):


6 Save the int_srs.cfg file.

7 Use the SMC to restart the process upg_intSrs.x in the access_primary module.



Changing the password for rootThe root account is associated with the following applications:

• Application Launch: install/uninstall application launch package

• MDM administration: read/write/execute for all MDM files and processes; installing, configuring, and maintaining MDM software

• Backup and restore: install/uninstall backup and restore software; invoke the backup and restore scripts

• Fault cartridges: used for installation and uninstallation and can also do all other operations

• Performance management: install and uninstall software

See Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.



Changing the password for SMCAdmin or SMCUserThere are two accounts for System ManaGement (SMG) that are UNIX accounts in the Sun Management Center. The SMCAdmin account is the administrator of the OAM supervision domain. The SMCUser account has SMC operator privileges.

The following procedure:

1. changes the password for the UNIX account on the primary main server

2. updates the common.cfg file in /opt/nortel/config/sysmgt on each of the servers in the ROC

Procedure 95:Changing the password for SMCAdmin or SMCUser

Step Action

1 Perform Procedure 85 to change the password for the UNIX account on the primary main server.

2 Log into the server (primary main, secondary main, performance server, SOC, or SRS) using the nortel user ID.


sh



where <new password> is the new password.


4 Open the /opt/nortel/config/sysmgt/common.cfg file in a text editor.

5 If you are changing the SMCAdmin password, change the following line as shown:

SMCAdminPasswd.CRYPTED="<encrypted password>"


6 If you are changing the SMCUser password, change the following line as shown:

userPassword.CRYPTED="<encrypted password>"


—sheet 1 of 2—



7 Save the common.cfg file.

8 Perform step 2 through step 7 for each of the servers in the ROC.

9 If you updated the password for SMCUser, use the SMC to restart ss_sysmgt_healthInfoServer process in the sysmgt_primary module.

Procedure 95:Changing the password for SMCAdmin or SMCUser

Step Action

—sheet 2 of 2—



Changing the password for smcorauSee Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.

Changing the password for SMCneopSee Table 20 for information about the servers on which this account exists. Perform Procedure 96 to change the password.

Procedure 96:Changing the password for SMCneop

Step Action


2 Type:

su - root


<password>


4 In the command line, type the following command:

/opt/nortel/data/coreEMS/nodes/server/bin/changeDSpasswd.sh

5 Follow the prompts in the script to change the password.



Changing the password for ttbuserThe ttbuser account is a UNIX account is used in the Trouble Ticketing application. See Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password.



Accounts on W-NMS servers and on network elementsThe accounts in this section have a dependency on the accounts that exist on network elements or other applications.

Changing the password for an ADC data collectorEach ADC data collector has a user name and password associated with it. The user name corresponds to a UNIX account on the network element. The UNIX account name on the network element must match the user name on the performance server and the passwords must also match.

Perform the following procedure to change the user name and password for the data collector for a network element.

Procedure 97:Changing the password for a data collector

Step Action

1 Log into the performance server using the nortel user ID.




/opt/nortel/shell/packet/adc/adcGUI &

The ASCII Data Collector Configuration - Collector window opens.

4 In the Collector List, click on the line which contains the collector for the network element you want to change.


The ASCII Data Collector Configuration - Edit window opens.

6 Enter values in the User ID field and the Password field.



9 You must also change the user ID and password on the network element itself to match the user ID and password on the performance server. Use the UNIX passwd command to update the UNIX account and password that corresponds to the user ID and password on the performance server.



Changing the password for administratorThe administrator account is used for identification authentication in the NIMS-PrOptima for W-NMS applications. Use the NIMS-PrOptima for W-NMS User Manager to change the password for the administrator account. Refer to the NIMS-PrOptima for W-NMS User Manager User Manual for information about how to do this.



Changing the password for administrator for install/upgradeThere is an administrator account associated with the install/upgrade GUI. This account exists on the primary main server, secondary main server, performance server, and the server of clients server. If you change the password on one server, you must change it on the other servers, using the same password. Perform the following procedure to change the password for this account.

Procedure 98:Changing the password for administrator for install/upgrade

Step Action


2 Type:

su - root


<password>


4 Find the name of the file that contains the password. Type:

grep -h AuthUserFile /opt/nortel/3rd_party/iut_tools/current_apache/conf/httpd.conf | sort -u


AuthUserFile <Password File>

where <Password File> = path name of the file containing the encrypted password

5 Type:

/opt/nortel/3rd_party/iut_tools/current_apache/bin/htpasswd <Password File> administrator


New password



6 Type the new password.


Re-type new password

7 Type the new password.


Updating password for user administrator

Procedure 98:Changing the password for administrator for install/upgrade (continued)

Step Action



Changing the password for anontmplThe anontmpl, ctxnfuse, ctxsrvr, and ctxssl accounts are associated with the Citrix* MetaFrame* application. Perform the following procedure to change the password for the anontmpl, ctxnfuse, ctxsrvr, or ctxssl accounts.

Procedure 99:Changing the password for anontmpl

Step Action

1 Log into the Server of clients using the nortel user ID.


/opt/nortel/shell/sysmgt/wam_stopgroup.sh metaframe_soc

3 Perform Procedure 85 starting from step 4 to change the UNIX account password.


/opt/nortel/shell/sysmgt/wam_startgroup.sh metaframe_soc



Changing the password for ctxnfuse, ctxsrvr, or ctxsslSee “Changing the password for anontmpl”.



Changing the password for demoThe demo account is used for identification authentication in NIMS-PrOptima for W-NMS applications and is also used in the synchronisation.properties file. Perform the following procedure to change the password for the demo account.

PrerequisitesBefore performing this procedure, you must know:

• How to change a password using the User Manager. Refer to the NIMS-PrOptima for W-NMS User Manager User Manual for information about how to do this.

• How to stop and start the NIMS-PrOptima processes. Refer to the NIMS-PrOptima for W-NMS System Administration Manual for information about how to do this.

Procedure 100:Changing the password for demo

Step Action

1 Change the password for the account using the User Manager.

2 Stop the NIMS-PrOptima processes.


4 Open the /opt/nortel/config/proptima/server/res/Synchronisation.properties file in a text editor.


ReportScheduler.Password=<password>

where <password> is the new password from step 1.

6 Save the Synchronisation.properties file.

7 Start the NIMS-PrOptima processes.



Changing the password for a BTS telnet sessionThis procedure sets a password for a telnet session used to access a Base Transceiver Station (BTS). You can also perform this procedure to set no password required,

Procedure 101:Changing the password for a BTS telnet session

Step Action

1 Log into the primary main or secondary main server using the nortel user ID.





/opt/nortel/shell/access/BTSpwd.sh set TELNET

4 Follow the command line prompts. You are required to enter the password two times. If you want to set telnet access so that no password is required, do not type a password when the password prompt is displayed; press the Enter key to indicate that no password is required.

The password update is complete when messages are displayed indicating the number of successful BTS updates and the number of failed BTS updates.

5 If there were some failed BTS updates in step 4, go to step 6. If there were no failed BTS updates, go to step 9.

6 Enter the following command to synchronize the passwords:

/opt/nortel/shell/access/BTSpwd.sh update

7 Enter:

/opt/nortel/shell/access/BTSpwd.sh unsynclist

This command shows all BTS network elements whose telnet passwords are not the same as the password stored on the main server (unsynchronized).

8 If there are still unsynchronized passwords, go to step 6. If there are no unsynchronized passwords, go to step 9.

9 Log off of the main server.



Changing the password for a BTS TIL sessionThis procedure sets a password for a Terminal for Local Installation (TIL) session used to access a Base Transceiver Station (BTS). You can also perform this procedure to set no password required,

Procedure 102:Changing the password for a BTS TIL session

Step Action






/opt/nortel/shell/access/BTSpwd.sh set TIL

4 Follow the command line prompts. You are required to enter the password two times. If you want to set TIL access so that no password is required, do not type a password when the password prompt is displayed; press the Enter key to indicate that no password is required.

The password update is complete when messages are displayed indicating the number of successful BTS updates and the number of failed BTS updates.

5 If there were some failed BTS updates in step 4, go to step 6. If there were no failed BTS updates, go to step 9.

6 Enter the following command to synchronize the passwords:

/opt/nortel/shell/access/BTSpwd.sh update

7 Enter:

/opt/nortel/shell/access/BTSpwd.sh unsynclist

This command shows all BTS network elements whose TIL passwords are not the same as the password stored on the main server (unsynchronized).

8 If there are still unsynchronized passwords, go to step 6. If there are no unsynchronized passwords, go to step 9.

9 Log off of the main server.



Changing the password for a CEM ftp user or usp userThe ftp user and usp user provide access between the CEM and the network element.

Perform the following procedure to change the password for the ftp user or usp user in the CEM. If you change the usp or ftp user password on the network element, you must also perform this procedure to change the password in the CEM. If you perform this procedure to change the password on the main server, you must also change the password on the network element.

Procedure 103:Changing the password for the ftp user or usp user

Step Action






/opt/nortel/data/coreEMS/nodes/server/bin/configCEMS

The coreEMS Commissioning Manager menu displays.

4 For a DMS with a USP or an HLR200 network element:

a. In the Navigator pane, click on a DMS network element.

b. Change the values for the USP User Password field and the FTP User Password to the new password that you defined on the network element.

c. Go to step 6.

5 For a USP or UNPM network element:

a. In the Navigator pane, click on a USP or UNPM network element.

b. In the table, in the row with the USP or UNPM, click on the cell under User Password or FTP Password.

c. Type in the new password.

d. Go to step 6.

6 Click on Submit.

7 Click on Yes.



8 Click on OK.

9 Close the coreEMS Commissioning Manager.

Procedure 103:Changing the password for the ftp user or usp user

Step Action



Changing the password for the GGSN device inventory systemThe GGSN device inventory system requires a connection to the SCS server. The GGSN CLUI is used to create the connection. See procedure Procedure 121: Adding an SCS connection in the Tools and utilities section of this document for more information.

The connections provisioned in the GGSN device inventory are dependent on the SCS server. The ftp user ID and password you configure in the SCS connection must match the account on the SCS server. If the ftp user ID or password is updated on the SCS server then they must also be updated in the SCS connection.

The same rule applies to the CORBA login Id and password configured in the SCS connection. They must match the information on the SCS server.

For information on how to change the password for the GGSN device inventory system, see Procedure 123: Editing an SCS connection in the Tools and utilities section of this document.



Changing passwords for other MDM accountsThe following table describes the MDM tools for which defining a password is optional. By default there are no passwords associated with these tools.

Table 23: MDM accounts

Application Account or user ID

Default password

Description

Server Administration tool

—none— —none— Allows access control to the edit mode of Server Manager. See the Preside Multiservice Data Manager Administrator Guide, 241-6001-303, for information on how to set the password. Look at the section that describes the Security menu of the Server Administration tool.

GMDR Administration tool

—none— —none— Allows access control to the edit mode of GMDR Admin application. See the Preside Multiservice Data Manager Administrator Guide, 241-6001-303, for information on how to set the password. Look at the section that describes the Security menu of the GMDR Administration tool.

IP Discovery —none— —none— Allows access control to the IP Discovery tool. See the Preside Multiservice Data Manager Fault Management User Guide, 241-6001-011. Look at the section that describes the IP Discovery application.



Changing the password for nortel The nortel account is associated with the following applications:

• Application launch: used to launch other application launch scripts

• Backup and restore: used in system backup to query, stop, and restart applications managed by the SMC

• CEM: configures, edits, and deletes network elements in the CEM system; BSY/RTS applications in the CEM environment

• Fault cartridges: performs most cartridge operations except installation and uninstallation

• MDP Administration, MDP file mover: Read/write/execute on all MDP files and processes; access to the performance server

• Performance management: executes commands under directory /opt/nortel/shell on the performance server

• Performance reporting: used to log into the main server to retrieve performance data through FTP

See Table 20 for information about the servers on which this account exists. Perform Procedure 85 to change the password. If you change the password for the nortel UNIX account on the primary main server and you are using NIMS-PrOptima for W-NMS, you must also perform Procedure 104.

Changing the password for the nortel account used by NIMS-PrOptima for W-NMSThe nortel account is used for ftp connection authentication into the primary main server from the performance server. NIMS-PrOptima for W-NMS uses the account to retrieve cm xml data.

PrerequisitesBefore performing this procedure, you must know how to stop and start the NIMS-PrOptima processes. Refer to the NIMS-PrOptima for W-NMS System Administration Manual for more information.

Procedure 104:Changing the password for the nortel account used by NIMS-PrOptima

Step Action

1 Stop the NIMS-PrOptima for W-NMS processes.





/opt/nortel/3rd_party/proptima/java/j2sdk_1.4.2_02/bin/java -Djava.ext.dirs="/opt/nortel/jar/proptima:/opt/nortel/jar/proptima/lib" mycom.util.TestCryptedTool <passwd>

where <password> is the new password for the nortel account

The password is displayed in encrypted form.


chmod +w /opt/nortel/config/proptima/dataimport/ftp/DrfFtp.tx

5 Open the /opt/nortel/config/proptima/dataimport/ftp/DrfFtp.txt file.


source1.ftp.password=<encrypted password>

where <encrypted password> is the encrypted password from step 3.

7 Save the DrfFtp.txt file.

8 Start the NIMS-PrOptima for W-NMS processes.

Procedure 104:Changing the password for the nortel account used by NIMS-PrOptima

Step Action



Changing the password for omcThe omc account is used for ftp connection authentication into the GSM SDO server from the performance server. NIMS-PrOptima for W-NMS uses the ftp connection to retrieve performance data. If the password for the omc account on the GSM SDO server is changed, you must update the password on the performance server. Perform the following procedure to update the password on the performance server.

PrerequisitesBefore performing this procedure, you must know how to stop and start the NIMS-PrOptima for W-NMS processes. Refer to the NIMS-PrOptima for W-NMS System Administration Manual for more information.

Procedure 105:Changing the password for omc

Step Action

1 Stop the NIMS-PrOptima for W-NMS processes.



/opt/nortel/3rd_party/proptima/java/j2sdk_1.4.2_02/bin/java -Djava.ext.dirs="/opt/nortel/jar/proptima:/opt/nortel/jar/proptima/lib" mycom.util.TestCryptedTool <password>

where <password> is the password on the GSM SDO server

The encrypted password is displayed.

4 Open the /opt/nortel/config/proptima/server/res/FtpMediation.properties file.

5 Look for the following line:

source<number>.Password=<password>

where <number> is the number of the SDO server whose password has changed

where <password> is the current encrypted password

6 Modify the line as shown:

source<number>.Password=<password>

where <number> is the number of the SDO server whose password has changed

where <password> is the encrypted password from step 3.



Changing the password for pm_omcsThe pm_omcs account is used to send operational measurement files (performance data) to the CDI. The pm_omcs account exists on the performance server. Perform the following procedure to change the password for pm_omcs. This procedure changes both the UNIX account password and the password for the pm_omcs account specified in the CEM export profile.

7 Save the FtpMediation.properties file.

8 Start the NIMS-PrOptima for W-NMS processes.

Procedure 106:Changing the password for pm_omcs

Step Action

1 Perform Procedure 85 to change the password for the UNIX account on the performance server.

2 Log on to the Network Services Platform using the admin user Id.

3 In the Resource Browser, open a network layout that contains a voice core network element.

4 Right-click on the network element.

The object menu for the network element opens.

5 From the object menu, select CEM and then select Open.

The Nortel Element Browser window opens.

6 From the Performance menu, select Mass Export.

The Export Status Window window opens.

7 From the File menu, select Start Editor and then select Archive Export Profile.

The Archive Export Profile Editor window opens.

8 Under Export to, if the value for the Login field is pm_omcs, change the value of the Password field to the same password you specified in step 1.

9 Click on the Save button.

The Re-Enter Password window opens.

—sheet 1 of 2—

Procedure 105:Changing the password for omc

Step Action



10 Enter the password and click on the OK button.

The Input window opens.

11 Enter a name for the profile and click on the OK button.

12 From the File menu, select Close.

The Archive Export Profile Editor window closes. In the Export Status window, the profile you created displays in the Profile tab with a Status of DISABLED .

13 In the Export Status window, click on the profile to select it.


The Status of the profile changes to ENABLED.


16 Close the Nortel Element Browser window.

You are finished enabling data collection for the voice core network element

Procedure 106:Changing the password for pm_omcs (continued)

Step Action

—sheet 2 of 2—



Changing the password for pm_pdiThe pm_pdi account is used to send BDF files (performance data) to the PDI. The pm_pdi account exists on the performance server. Perform the following procedure to change the password for pm_pdi. This procedure changes both the UNIX account password and the password for the pm_pdi account specified in the MDP File Mover.

Procedure 107:Changing the password for pm_pdi

Step Action

1 Perform Procedure 85 to change the password for the UNIX account on the performance server.



4 Log on to the performance server using the nortel user Id.





6 Enter:

./gmdpconfig&





10 Change the Password field to the same password you specified for the UNIX account in step 1.


12 Click on Cancel.





Changing the password for sridwlThe sridwl account is used to download software from the SRM client onto the SRS server. Perform the following procedure to change the password for sridwl. This procedure changes the UNIX account password and the password on the SRM application.

Changing hardware passwords 6This section explains how to change the passwords for the following hardware components:

• SunFire 4800

• SunFire E4900

• SunFire V250

• T3 external disk storage array

Procedure 108:Changing the password for sridwl

Step Action

1 Perform Procedure 85 to change the UNIX account password.

2 Log into the SRM client.

3 Open a web browser.

4 Type the following URL in the address field of the web browser:

http://<server name>:8080/srm/services/changePassword.jsp

where <server name> is the name of the SRS server

5 Follow the instructions in the application to change the password to the same password you set in step 1.


Nortel Networks Confidential Changing hardware passwords 231

Table 24 shows the default passwords for the hardware components.

Table 24: Hardware accounts

Hardware component Account Default password

SunFire 4800, E4900:

System Controllerspare System Controllerdomain Adomain Bdomain Cdomain D

not applicable

—none—

SunFire V250 not applicable

—none—

T3 external disk storage array

root umpump



Changing the password for SunFire 4800 or E4900This procedure changes the password for the SunFire 4800 or the SunFire E4900. There are separate passwords associated with the System Controller (SC), domain A, domain B, domain C, domain D, and spare SC.

Procedure 109:Changing the password for SunFire 4800, E4900

Step Action

1 Connect to the master SC.

Changing the password for the SC


password


Enter new password:

3 Type:

<password>

where <password> is the new password for the SC.


Enter new password again:

4 Type:

<password>

where <password> is the new password for the SC.

Changing the password for domain a, domain b, domain c, or domain d


console <domain>

where <domain> is one of {a, b, c, d} for domain A, domain B, domain C, or domain D for the domain whose password you want to change.

6 Type:

password


Enter new password:



7 Type:

<password>

where <password> is the new password for the domain.



8 Type:

<password>

where <password> is the new password for the domain.

9 Type:

disconnect

Changing the password for the spare SC

10 Connect to the spare SC.


password


Enter new password:

12 Type:

<password>

where <password> is the new password for the spare SC.



13 Type:

<password>

where <password> is the new password for the spare SC.

Procedure 109:Changing the password for SunFire 4800, E4900 (continued)

Step Action



Changing the password for SunFire V250This procedure changes the password for the SunFire V250.

Procedure 110:Changing the password for SunFire V250

Step Action

1 Connect to the SC.


password


password changing for <name>

Setting password for <name>

New password:

3 Type:

<password>

where <password> is the new password for the SunFire V250.


Re-enter new password:

4 Type:

<password>

where <password> is the new password for the SunFire V250.



Changing the password for a T3 external disk storage arrayEach T3 external disk storage array has a root account that is used to log into the storage arrays through telnet and to launch commands for configuration.

To change the password for a T3 external disk storage array you must:

• change the password for the root account on the T3 external disk storage array

• update the configuration file with the new password

Procedure 111:Changing the password for a T3 external disk storage array

Step Action

1 Log into the server connected to the storage array whose root password you want to change.

2 Look at the /opt/nortel/config/iut_tools/roc/iut_rocconfig.cfg file.

3 Look for a line similar to the following:

Server.3.T3_<server number>.Passwd=<encrypted password>

where <server number> is the number of the storage array, and <encrypted password> is the encrypted password of the storage array

The following example shows that the number of the storage array is 1 and the encrypted password is 6b5b623454a:

Server.3.T3_1.Passwd=6b5b623454a

4 Write down the server number and the encrypted password.


/opt/nortel/exe/iut_tools/fmk_install_pwd.x -d <encrypted password>

where <encrypted password> is the password from step 4.

The unencrypted password is displayed.

6 Log into the storage array using the root account and unencrypted password from step 5.

7 Use the UNIX passwd command to change the password for the root account.

8 Log into the primary main server using a user ID that is not the root user ID.

—sheet 1 of 2—



9 Enter:

su - root


<password>



/opt/nortel/exe/iut_tools/fmk_install_pwd.x <unencrypted password>

where <unencrypted password> is the password for the root account from step 7.

The encrypted password is displayed.


/opt/nortel/shell/iut_tools/common/iut_addmachineinroc.sh -SE -H0<server name> -T<x>P<new password>

where <server name> is the host name of the server to which the storage array is connected, <x> is the number of the storage array you wrote down in step 4, and <new password> is the encrypted password from step 11.

The following example shows the command where <server name> is potter, <x> is 1, and <new password> is t31pwd:

/opt/nortel/shell/iut_tools/common/iut_addmachineinroc.sh -SE -H0potter -T1Pt31pwd

13 Type:

/opt/nortel/shell/iut_tools/common/iut_addmachineinroc.sh -export

Procedure 111:Changing the password for a T3 external disk storage array

Step Action

—sheet 2 of 2—


Nortel Networks Confidential Encrypting clear text passwords 237

Encrypting clear text passwords 6The procedures in this section explain how to find existing passwords in the SVMList.cfg file that are shown in clear text and encrypt them. The SVMList. cfg file contains passwords for the FMDR servers. The procedures do not change an existing password.

Perform the following procedures in the order listed to encrypt a password. You must perform these procedures once for each password that is stored in clear text:

• Procedure 112: Finding an existing clear text password

• Procedure 113: Encrypting a password

• Procedure 114: Inserting the encrypted password

Finding an existing clear text passwordThis procedure finds the clear text password for each FMDR server.

Procedure 112:Finding an existing clear text password

Step Action

1 Log into the main server using the root user ID.

2 Start the MDM toolset.

3 From the MDM toolset System menu, click Administration->Server Administration.

4 From the Server name list area, right-click on the name of a FMDR server for which you want to check a password.

5 From the Server Functions object menu, click View server.

6 In the Startup command field, note the current argument that is displayed in the following text:

–p <argument>

If the value of <argument> is a single string that looks like a password then it is a password in clear text that needs to be encrypted.

If the value of <argument> is a file name like "/opt/MagellanNMS/cfg/private/<filename>"then the password is already encrypted. You have completed this procedure and you do not have to perform any of the other procedures in this section for this FMDR server.

7 Click OK to return to the Server Administration tool main window.

8 Click File -> Exit to return to MDM Toolset.

9 End of procedure.



Encrypting a passwordThis procedure encrypts a password.

Inserting the encrypted password This procedure replaces a clear text password with a file that contains the encrypted password.

Procedure 113:Encrypting a password

Step Action

1 From the System menu, click Security->Password Encryption.

2 In the Enter Password field, type the clear text password you found in Procedure 112.

3 Type the same password again in the Confirm Password field.

4 Type a name for the file in which you want the encrypted password to be stored. Use a different file name for each password. The file containing the encrypted password is stored in the directory /opt/MagellanNMS/cfg/private.

5 Click Save.

6 Click Close.

7 End of procedure.

Procedure 114:Inserting the encrypted password

Step Action

1 From the MDM toolset System menu, click Administration->Server Administration.

2 From the Security menu, click Authorize Editing.

3 Click OK at the password prompt in the SVM Enter Authorization Password dialog box.

4 From the Server name list area, right-click on the name of a FMDR server for which you want to set a secure password.

5 From the Server Functions object menu, click Edit.

6 In the Startup command field, replace the current password text with the full path and file name of the file that contains the secure password. Example:

/opt/MagellanNMS/bin/fmdr -g <group> -u <user> -p /opt/MagellanNMS/cfg/private/<password file name> -l AL


Nortel Networks Confidential Encrypting clear text passwords 239

7 Click Save and Restart.

8 Click Cancel to return to the Server Administration tool main window.

9 End of procedure.

Procedure 114:Inserting the encrypted password (continued)

Step Action



Tools and utilities 7This section describes the following tools and utilities in the W-NMS solution:

• Performance Management Administration Menu

• logging that is controlled through the Performance Management Administration Menu

• XML file and directory structure descriptions for the XML files for which you can configure compression and rotation through the Performance Management Administration Menu.

• NetRx

• Command Line Interface Manager (CLI*manager)

• GGSN command line user interface (CLUI)

• Import and export of configuration management XML files

• Wireless Provisioning System for core network

• Removing a server from the Orbix Trader

Performance management administration 7The Performance Management Administration Menu contains administration tools for the following performance server components:

• Circuit Data Interface (CDI) (CCN CS, CCN HLR, USP, HLR 200 (CCN HLR with a USP), R4 BICN MSC, combined MSC/HLR, SGW, UNPM, SLR, IWF, MGW)

• Packet Data Interface (PDI) (SGSN, Aggregation Node, Multiservice Switch)

• SIG Data Interface (SDI) (SS7 IP Gateway)

• Generic Data Interface (GDI) (GGSN, SGSN debug statistics)

• ASCII Data Collector (ADC) (SS7 IP Gateway, GGSN)


242 Tools and utilities Nortel Networks Confidential

For each of the previously listed components, you can configure parameters related to:

• logging levels

• application file rotation

• XML file rotation

• XML file compression

• saving data files

The parameters for the components are set to default values when the components are installed. The default values are documented in the following sections. Talk to your Nortel technical representative before changing any of these values.

Accessing the Performance Management Administration menuUse the following procedure to access the Performance Management Administration menu. You can use tools on the menu to change the default values that are defined when the performance server components are installed.


• the password for one of the following user Ids on the performance server:

— the nortel user Id

— the root user Id


Nortel Networks Confidential Performance management administration 243

Procedure 115:Accessing the Performance Management Administration menu

Step Action

1 Log on to the performance server using either the nortel user Id or the root user Id.

2 In the command line, enter the following commands:

cd /opt/nortel/shell/common/config

./pm_admin

Do not enter the previous command with the ampersand (&), which will cause the command to be run in the background. The Performance Management Administration menu requires user input and must be run in the foreground.

The following menu is displayed:

Performance Management Adminstration Menu

1.CDI Menu

2.PDI Menu

3.SDI Menu

4.GDI Menu

5. ADC Menu

6. SGSN Debug Menu

7. Exit

Enter selection please:

3 Enter the number of the menu item you want to access. See the following sections for more information about the items in the Performance Management Administration Menu.



The log files 7The following table shows the log files that are generated by each of the performance management components:

The maximum size of a log file is approximately 500 kilobytes. When a log file reaches the 500 kilobyte limit, it is renamed to <yyyymmdd>T<hhmmss>.log, where <hhmmss> is the time the log file was renamed. Subsequent log file messages are written to the original log file named <yyyymmdd>.log.

Table 25

Component Location of log file log file name log file entry format

PDI /opt/nortel/logs/packet/pdi/traces <yyyymmdd>.log <hh:mm:ss:SSS> <text message>

GDI /opt/nortel/logs/packet/gdi/traces GDI-Log<yyyymmdd>.log

GDI-ErrorLog<yyyymmdd>.log

SDI /opt/nortel/logs/packet/sdi/traces <yyyymmdd>.log

ADC /opt/nortel/logs/packet/adc/traces ADC-Log<yyyymmdd>.log

ADC-ErrorLog<yyyymmdd>.log

CDI /opt/nortel/logs/circuit/traces <yyyymmdd>.log

SGSN Debug

/opt/nortel/logs/packet/gdi/traces GDIsgsn-Log<yyyymmdd>.log

GDIsgsn-ErrorLog<yyyymmdd>.log

where: is<hh:mm:ss:SSS> hh = hour of day (00-23)

mm = minutes of hour (00-59)ss = second of minute (00-59)SSS = milliseconds (000-999)

<text message> is a text string<yyyymmdd> the start date of the report


Nortel Networks Confidential The log files 245

Setting log levelsYou can set log levels for files associated with the following performance server components:

• CDI

• PDI

• SDI

• GDI

• ADC

• SGSN Debug

View/Set Log LevelThe following items are available from this menu:

1. View Log Level

2. Set Log Level

View Log Level shows the current log level setting. This setting determines the level of the detail recorded in the log file.

Set Log Level allows you to change the level of logging. The valid values are shown in the following tables:

Table 26Log levels for the PDI, SDI, CDI

Value Description

off No log is generated.

info Log the basic information about the status of the transaction. For example, successful, warning, and error messages. This is the default value.

verbose Log the basic information plus the debug level of step-by-step status. Use this value with caution because it creates a large amount of data.

terse Log error and critical messages.

Table 27Log levels for the ADC, GDI, and SGSN Debug

Value Description

false Log status message. This is the default value.

true Log status and debug messages.



For more information about the log files, see the Wireless Network Management System Core Network Observation Counters, 411-8111-401.

Setting file rotationYou can set file rotation for files associated with the following performance server components:

• CDI

• PDI

• SDI

• ADC

• GDI

• SGSN Debug

View/Set File Rotation for CDI, PDI, and SDIThe following items are available from this menu:

1. View File Rotation Status

2. Set File Rotation Status

3. View Application File Rotation

4. Set Application File Rotation

5. View XML File Rotation

6. Set XML File Rotation

View File Rotation Status shows the value of the File Rotation Status (ON or OFF). The default value is OFF. If the value is ON, the CDI (or PDI or SDI) purges files based on the file rotation settings. If the value is OFF, the CDI does not purge files.

Note: The SMC also performs file purging. It is recommended that you use the SMC file purging feature to manage your disk space. For more information about the SMC file purging feature, refer to Wireless Network Management System System Management, 411-8111-538.

Set File Rotation Status allows you to change value of the File Rotation Status.

View Application File Rotation shows the current archive period of the files located in the following directories for each performance server component:

• CDI

— /opt/nortel/data/circuit/collection/successful

— /opt/nortel/data/circuit/collection/failedfiles

— /opt/nortel/logs/circuit/traces



• PDI

— /opt/nortel/data/packet/pdi/collection/successful

— /opt/nortel/data/packet/pdi/collection/failedfiles

— /opt/nortel/logs/packet/pdi/traces

• SDI

— /opt/nortel/data/packet/sdi/collection/successful

— /opt/nortel/data/packet/sdi/collection/failedfiles

— /opt/nortel/logs/packet/sdi/traces

Set Application File Rotation allows you to set the archive period for files located in the directories in the previous list. The valid range is 1 to 15 days. The default is 15 days.

View XML File Rotation shows the current archive period of the XML files located in the following directories:

• CDI

— /opt/nortel/data/circuit/observation/msc

— /opt/nortel/data/circuit/observation/hlr

— /opt/nortel/data/circuit/observation/msc_hlr

— /opt/nortel/data/circuit/observation/mgw

— /opt/nortel/data/circuit/observation/sgw

— /opt/nortel/data/circuit/observation/unpm

— /opt/nortel/data/circuit/observation/slr

— /opt/nortel/data/circuit/observation/iwf

— /opt/nortel/data/circuit/pp/late

• PDI

— /opt/nortel/data/packet/observation/2g-sgsn

— /opt/nortel/data/packet/observation/3g-sgsn

— /opt/nortel/data/packet/observation/transmission

— /opt/nortel/data/packet/pdi/pp/late

• SDI

— /opt/nortel/data/packet/observation/sig

— /opt/nortel/data/packet/sdi/pp/late



Set XML File Rotation allows you to set the archive period for XML files. The valid range is 1 to 90 days. The default is 30 days. A period of more than 30 days is not recommended.

View/Set File Rotation for GDI, ADC, and SGSN DebugThe following items are available from this menu:

1. View File Rotation Status

2. Set File Rotation Status

3. View File Rotation Settings

4. Set File Rotation Settings

View File Rotation Status shows the value of the File Rotation Status (ON or OFF). The default value is OFF. If the value is ON, the GDI (or ADC or SGSN Debug) purges files based on the file rotation settings. If the value is OFF, the GDI does not purge files.

Note: The SMC also performs file purging. It is recommended that you use the SMC file purging feature to manage your disk space. For more information about the SMC file purging feature, refer to Wireless Network Management System System Management, 411-8111-538.

Set File Rotation Status allows you to change value of the File Rotation Status.

View File Rotation Settings shows the current archive period of the files located in the following directories:

• /opt/nortel/data/packet/gdi/shasta-ggsn

• /opt/nortel/logs/packet/gdi/traces

• /opt/nortel/data/packet/observation/shasta-ggsn

• /opt/nortel/logs/packet/adc/traces

• /opt/nortel/data/packet/adc

• /opt/nortel/data/packet/gdi/debug-sgsn

• /opt/nortel/data/packet/observation/debug-sgsn

Set File Rotation Settings contains the following menu:

Setting GDI (or ADC or SGSN Debug) File Rotation

1. Change purge age for directory

WARNINGSetting the XML file rotation to more than 30 days can affect the disk capacity.



2. Add new directory to purge list

3. Remove directory from purge list

The valid range for the purge age is 1 to 90. The default purge age for the GDI directories is:

/opt/nortel/data/packet/gdi/shasta-ggsn - 14 days

/opt/nortel/logs/packet/gdi/traces - 14 days

/opt/nortel/data/packet/observation/shasta-ggsn - 30 days

/opt/nortel/data/packet/gdi/debug-sgsn - 14 days

/opt/nortel/data/packet/observation/debug-sgsn - 30 days

The default purge age for the ADC directories is:

/opt/nortel/logs/packet/adc/traces - 14 days

/opt/nortel/data/packet/adc - 14 days

Setting XML compressionYou can set XML compression for the following performance server components:

• CDI

• PDI

• SDI

• GDI

• ADI

• SGSN Debug

XML compression is not applicable for the ADC.

Enable/Disable XML compressionThe following items are available from this menu:

• View XML Compression Status

• Enable XML Compression

• Disable XML Compression

Use this menu to enable or disable XML compression for the CDI, PDI, SDI, GDI, and SGSN Debug. See “Setting XML compression for the ADI” for information about how to enable or disable XML compression for the ADI.

View XML Compression Status shows the current setting for XML compression (ON or OFF). The default value is ON.



Enable XML Compression turns XML compression on. When XML compression is on, the XML file is compressed and it has an extension of .gz.

Disable XML Compression turns XML compression off.

For more information about the XML files and operational measurements, see the Wireless Network Management System Core Network Observation Counters, 411-8111-401.

Setting XML compression for the ADIPerform the following procedure to enable or disable XML file compression on the Access Data Interface (ADI).

Saving data filesYou can save the network element data files after they have been translated to 3GPP XML format. If the translation is unsuccessful they are also saved. This feature applies to the following performance server components:

• CDI

• PDI

Procedure 116:Setting XML compression for the ADI

Step Action

1 Log into the performance server.


cd /opt/nortel/shell/access

pm_xmlcompress.sh -s <server type> -d <rocName> -c <clusterId> -f <compressFlag>

where <servertype> is "observation" for observation files or "calltrace" for call trace files.

where <rocName> is optional and is the ROC name for the performance server. If this parameter is not specified, the default ROC name is used. To determine the default ROC name, type the command: pm_xmlcompress.sh

where <clusterId> is optional and is the cluster Id for the performance server. If this parameter is not specified, the default cluster ID is used. To determine the default cluster ID, type the command: pm_xmlcompress.sh

where <compressFlag> is 1 to enable compression or 0 to disable compression. When XML compression is on, the XML file is compressed and the file has an extension of .gz.

3 End of procedure.


Nortel Networks Confidential Configuring NetRx 251

• SDI

• GDI

• SGSN Debug

Saving data files is not applicable for the ADC.

Enable/Disable Successful File SaveThe following items are available from this menu:

• View Successful File Save Status

• Enable Successful File Save

• Disable Successful File Save

View Successful File Save Status shows the status of the Successful File Save (ON or OFF). The default value is OFF.

Enable Successful File Save turns the Successful File Save on. When the data file has been successfully translated to 3GPP XML format, the file is compressed and saved in the successful directory for the performance server component. For example, data files for the PDI are saved to /opt/nortel/data/packet/pdi/collection/successful. If the translation is unsuccessful the data files are saved to /opt/nortel/data/packet/pdi/collection/failedfiles.

Disable Successful File Save turns the Successful File Save off. After processing by the performance server component (CDI, PDI, SDI, GDI, SGSN Debug) the file is deleted.

Configuring NetRx 7Use this procedure to configure NetRx on the main server. The data collected by NetRx can be used to analyze and diagnose problems with a Multiservice Switch. For information about how to use NetRx, refer to netRx_Collector_User_Guide.doc or netRx_Collector_User_Guide.pdf in /opt/netRx2/doc.

PrerequisitesBefore performing this procedure:

• Verify that the required supported modules have been installed on the main server. Read the instructions in /opt/netRx2/doc/INSTALL for more information. If the required modules are not installed, refer to /opt/netRx2/doc/INSTALL_PERL_MODULES for information on how to install them.

• you must have general operating knowledge of UNIX

• you must know the password for the root user on the main server

• you must know the password for the nortel user on the main server



CLI*manager 7CLI*manager (Command Line Interface Manager) is an optional tool that can be used to speed up and simplify operations and provisioning of network elements. For information about how to get the CLI*manager software, speak to your Nortel representative. For detailed information about CLI*manager, refer to the CLI*manager documentation.

CLI*manager is installed on a client workstation and is available for the Windows operating system and the Solaris operating system.

Installing the CLI*manager for WindowsThis procedure explains how to install the CLI*manager for the Windows operating system.

Procedure 117:Configuring NetRx

Step Action


2 If the MDM Passport encryption feature is enabled, switch user to the root user. If the MDM Passport encryption feature is not enabled, go to step 3.

3 Enter:

/opt/netRx2/bin/install

4 Follow the instructions and reply to the prompts in the configuration script.

You are finished configuring NetRx.

SECURITY ALERTIt is possible to store passwords for the network elements in the CLI*manager. For security reasons it is recommended that you do not store passwords in the CLI*manager.


Nortel Networks Confidential CLI*manager 253

PrerequisitesBefore performing this procedure you must have the Java Runtime Environment (JRE) 1.4.2_04 installed on your workstation.

Installing the CLI*manager for SolarisThis procedure explains how to install the CLI*manager for the Solaris operating system.

PrerequisitesBefore performing this procedure you must have the Java Runtime Environment (JRE) 1.4.2_04 installed on your workstation.

Procedure 118:Installing the CLI*manager for Windows

Step Action

Installing the CLI*manager

1 Download the executable installation file from the Nortel FTP site to your workstation.

2 Double-click on the executable file. Follow the instructions in the installation window that opens.

Starting the CLI*manager

3 To start the CLI*manager:

a. From the Start menu, select Programs and then select CLImanager.

You are finished installing and starting the CLI*manager.

Procedure 119:Installing the CLI*manager for Solaris

Step Action

Installing the CLI*manager

1 Download the executable installation file from the Nortel FTP site to your workstation.

2 Set executable permissions to the file:

chmod +x CLImanager_3_0_1.bin

3 Set the DISPLAY variable to the IP address of the workstation you are located at.

—sheet 1 of 2—



4 Start the installer:

./CLImanager_3_0_1.bin LAX_VM <1.4.2 java path>

where <1.4.2 java path> is the path to the JRE 1.4.2_04

For example:

./CLImanager_3_0_1b14.bin LAX_VM /home/nortel/client/j2re1.4.2/bin/java

5 Follow the instructions in the installation window that opens.

Starting the CLI*manager

6 To start the CLI*manager:

a. Change directory to the installation folder defined during the installation.

b. Run the CLImanager file:

./CLImanager

You are finished installing and starting the CLI*manager.

Procedure 119:Installing the CLI*manager for Solaris

Step Action

—sheet 2 of 2—


Nortel Networks Confidential GGSN command line user interface 255

GGSN command line user interface 7The GGSN command line user interface (CLUI) allows you to provision

• an SCS connection to the GGSN Device Inventory system

• the refresh interval for the GGSN Device Inventory system cache

Starting the GGSN provisioning CLUIThis procedure starts the GGSN provisioning CLUI.

Adding an SCS connectionThis procedure adds provisions an SCS connection which enables the SCS interface to connect to the SCS server. Refer to Table 28 for descriptions of the variables used in the procedure.

Procedure 120:Starting the GGSN provisioning CLUI

Step Action



/opt/nortel/shell/deviceinv/client/configClui.sh

The following menu displays:

*** Main Menu ***

1 - Provision Shasta SCS Connection2 - Provision Refresh Interval3 - ExitEnter menu option:[1 - 3]:

3 End of procedure.

Procedure 121:Adding an SCS connection

Step Action

1 Start the provisioning CLUI as described in Procedure 120.

2 In the Main Menu, select Provision Shasta SCS Connection. Type:

1

—sheet 1 of 3—



3 Select Add New Shasta SCS Connection. Type:

1

4 Type:

<IP address>

5 Type:

<ftp login user Id>

6 Type:

<ftp login password>

As you type the password the characters do not display and the cursor does not move.

7 Type:

<ftp login password>

As you type the password the characters do not display and the cursor does not move.

8 Type:

<SCS CORBA IOR file location>

9 Type:

<Corba API Login Id>

10 Type:

<Corba API Login password>

As you type the password, the characters do not display and the cursor does not move.


Step Action

—sheet 2 of 3—



Deleting an SCS connectionThis procedure deletes an SCS connection. Refer to Table 28 for descriptions of the variables used in the procedure.

11 Type:

<SCS login password>

As you type the password, the characters do not display and the cursor does not move.

The system displays the values you entered and validates the SCS connection.

If the connection is valid, the following message displays:

Do you want to save the Shasta SCS connection? [y/n]

12 If the connection is not valid, the following message displays:

Error in provisioning data. Check ftp user and/or password. Do you want to save this Shasta connection anyway? [y/n]

13 If you want to save the connection, type:

y

14 End of procedure.

Procedure 122:Deleting an SCS connection

Step Action


2 In the Main Menu, select Provision Shasta SCS Connection. Type:

1

3 Select Delete Existing Shasta SCS Connection. Type:

2

A list of existing connections by IP address displays.

4 Type:

<IP address>

—sheet 1 of 2—


Step Action

—sheet 3 of 3—



Editing an SCS connectionThis procedure allows you to change the values for an SCS connection. Refer to Table 28 for descriptions of the variables used in the procedure.

5 Type:

y

6 End of procedure.

Procedure 123:Editing an SCS connection

Step Action


2 In the Main Menu, select Provision Shasta SCS connection. Type:

1

3 Select Edit Existing Shasta SCS connection. Type:

3


4 Type:

<IP address>

The CLUI displays the current value for each of the variables. You can either type a new value or press the Enter key to keep the current value.

5 When the last variable has been displayed, the system validates the information and displays the following message:

Do you want to save the Shasta SCS connection? [y/n]

6 Type:

y

7 End of procedure.

Procedure 122:Deleting an SCS connection

Step Action

—sheet 2 of 2—



Testing an SCS connectionThis procedure allows you to validate an existing SCS connection. Refer to Table 28 for descriptions of the variables used in the procedure.

Procedure 124:Testing an SCS connection

Step Action


2 In the Main Menu, select Provision Shasta SCS connection. Type:

1

3 Select Test Existing Shasta SCS connection. Type:

4


4 Type:

<IP address>

The system checks the connection.

If the connection is valid, the following message displays:

<IP address>: success

You are finished this procedure. Go to step 8.

5 If the connection is not valid, the following message displays:

<IP address>: Error in provisioning data. Check ftp user and/or password.

Do you want to Edit this connection? [y/n]

6 If you want to change the values for the connection, type:

y

Edit the values for the connection as explained in Procedure 123.

7 If you do not want to change the values for the connection, type:

n

8 End of procedure.



Updating the refresh intervalThis procedure allows you to change the refresh interval. The refresh interval can be between 15 and 1440 minutes (one day ). The default value is 60.

Table 28

Variable Description

<IP address> IP address of the SCS server

<ftp login user Id> user Id used to log into the SCS server for ftp

<ftp login password> password for the ftp login user Id

<SCS CORBA IOR file location> the directory path to the CORBA IOR file (the IOR file is stored on SCS server)

<Corba API Login Id> user Id used to log into the SCS GUI (for example, device_owner)

<Corba API Login password> password for the Corba API Login Id

Procedure 125:Updating the refresh interval

Step Action


2 In the Main Menu, select Provision Refresh Interval. Type:

2

3 Select Update Refresh Interval. Type:

1

The current refresh interval in minutes displays.

4 Type a value between 15 and 1440.

The new refresh value displays. The time to the next refresh displays.

5 End of procedure.


Nortel Networks Confidential Import and export of configuration management XML files 261

Viewing the refresh IntervalThis procedure allows you to see the current value of the refresh interval.

Import and export of configuration management XML files 7You can import and export the XML files that contain configuration management (CM) information for the following network elements:


• Media Gateway

• SGSN/GPRS

• SGSN/UMTS

You can only export CM XML files for the GGSN.

The import and export functions are performed from the Network Services Platform (NSP) window. Before performing the following procedures you must be familiar with NSP. For more information about NSP, see the W-NMS Network Services Platform User Guide, 411-5221-211.

Creating an SCS connectionBefore you can export CM XML files for the GGSN, you must:

• Create the SCS user cm-xml-user with device_owner_isp privileges. Refer to the GGSN Provisioning Procedures, 411-5221-927 for information about how to create an SCS user.

• Create an SCS connection to the GGSN by performing Procedure 121 using an <Corba API Login Id> = cm-xml-user.

Procedure 126:Viewing the refresh interval

Step Action


2 In the Main Menu, select Provision Refresh Interval. Type:

2

3 Select Update Refresh Interval. Type:

2

The current refresh interval in minutes displays.

4 End of procedure.



Exporting an XML snapshot fileThis procedure explains how to export an XML snapshot file. You can export an XML snapshot file for a single network elements, multiple network elements, or a network element group.

Procedure 127:Exporting an XML snapshot file

Step Action

1 In the Resource Browser window, select one or more network elements. To select multiple network elements, press the Shift key, and click on each network element.

2 Perform one of the following:

a. From the NSP configuration menu, select CM XML -> CM XML export.

b. In the Resource Browser window, right-click on the network element you selected in step 1, and select Configuration -> CM XML -> CM XML export from the object menu.

The CM XML Export window opens. The network element you selected is displayed under Network objects selection.

3 If you want to compress the XML file, select the Compressed check box.

4 In the File field, type a name for the snapshot file.

5 Click on Export.

The Command Manager window opens and shows the progress of the export.

6 In the Current Commands tab, look for the line that contains the export you are performing. The export is finished when the value under Progression is 100%. Wait for the export to finish before performing the next step.

7 In the Current Commands tab, click on the line that contains the export you performed.

8 In the Logs tab, click on the following line:

Click here to view export report

The CM XML Export report window opens.

9 If you want to save the report for viewing later on, click on Save Report. The exported snapshot is saved to the following directory: /opt/nortel/data/cmXML.



Nortel Networks Confidential Import and export of configuration management XML files 263

Importing an XML workorderThis procedure explains how to import an XML workorder file. The Wireless Provisioning System is used to create XML workorders. See “The Wireless Provisioning System for core network” for more information about XML workorders.

Procedure 128:Importing an XML workorder

Step Action

1 From the NSP Configuration menu, select CM XML -> CM XML import.

2 On the left side of the CM XML Import window, under XML Tables, click on the XML file you want to import.

3 Click on the right arrow.

The XML file you selected shows up under Selected XML files.

4 Click on OK.

The Command Manager window shows the progress of the import. When the import is finished, in the Current Commands tab, the field under Progression shows 100%.

5 In the Current Commands tab, click on the line that contains the import you performed.

6 In the Logs tab, click on the following line:

Click here to view import report

The CM XML Import report window opens.

7 If you want to save the report for viewing later on, click on Save Report.

8 Save the report to a directory of your choice.

9 End of procedure.



Exporting an XML snapshot file for the networkThis procedure explains how to export an XML snapshot file for the core network elements in the network (Aggregation Node, GGSN, MGW, and SGSN).

The Wireless Provisioning System for core network 7The Wireless Provisioning System (WPS) for core network is PC-based application which allows you to configure the Aggregation Node (AN), GSM Media Gateway (MGW), SGSN/GPRS, and the SGSN/UMTS.

You can perform the following functions using the WPS for core network:

• modify network element parameters that can be provisioned

• network view of network elements and their parameters

For detailed information about the WPS for core network, see About WPS, 411-8111-916. This NTP describes the WPS application and its functionality. The following restrictions apply for the WPS for core network to the About WPS NTP:

• There is a plug-in API provided for the access network elements that provides custom import/export wizards, templates, navigators, checks, and operations that are specific to the access network elements. These wizards, templates, navigators, checks, and operations are not applicable for the SGSN and MGW network elements. However, you can define your own import/export wizards and templates.

• The only format supported for the AN, MGW, and SGSN network elements is Configuration Management (CM) XML.

Procedure 129:Exporting an XML snapshot file for the network

Step Action

1 From the NSP Configuration window, select CM XML -> CM XML Export Network.

The CM XML Export window opens.

2 Under Export Network Options, click the Core Network check box.

3 The rest of this procedure is the same as for exporting an XML snapshot file for an individual network element. Go to step 3 of Procedure 127.

4 End of procedure.


Nortel Networks Confidential Removing a server from the Orbix Trader 265

Removing a server from the Orbix Trader 7This procedure removes a server from the Orbix Trader. You can use this procedure to remove the secondary main server or the performance server from the ROC. For example, you can perform this procedure to remove the secondary main server from the ROC, when the secondary main server is unreachable but you still want to use W-NMS to manage the network.

PrerequisitesBefore performing this procedure, the Orbix Trader must be running.

Procedure 130Removing a server from the Orbix Trader

Step Action

1 Log into the primary main server.


su -root

<password>


3 Type:

/opt/nortel/shell/fmk/fmk_rm_cluster_from_trader.sh -cluster <cluster name>

or

/opt/nortel/shell/fmk/fmk_rm_cluster_from_trader.sh -host <host name>

where <cluster name> is one of

— UMAINSERV2 for the secondary main server

— UPERFSERV1 for the performance server

where <host name> is the host name of the secondary main server or the performance server

4 Reply to the prompt to delete the trader offers for the cluster by typing:

y


Nortel Networks Confidential Default shell for the root and nortel user Ids 267

Wireless Network Management System users 8

This section describes some of the user IDs in the W-NMS. It also provides a reference to information on user administration tasks.

Default shell for the root and nortel user Ids 8The UNIX users root and nortel are used for system administration tasks. The default login shell for the root user is the Bourne shell (/sbin/sh). The default login shell for the nortel user is the csh (/bin/csh). W-NMS provides shell scripts for various system administration tasks. These scripts have been tested with the previously mentioned shells. If you change the default shell for either user, some of these scripts will not work as intended.

sdmuser user ID 8The user ID sdmuser allows you to do the following tasks in the Core Element Manager (CEM):

• access the Table Access menu item for configuration management

• export operational measurement data (counters) from the SuperNode Data Manager Fault (SDM) to the performance server

• activate and deactivate trace for Call Trace

• manage trace records for Call Trace

Use the sdmuser user Id to log into the Network Services Platform (NSP). When you launch the CEM from NSP, you have access to the previously listed functions. If you do not log in as the sdmuser, you do not have access to the previously listed functions.

Change the password for sdmuser immediately after you have completed commissioning W-NMS. See the Security section in this NTP for information about changing account passwords.

admin user ID 8The admin user Id must be created on the NSP LDAP server with the proper access rights for CEM operations. For more information, see the procedure that explains how to create a user on the NSP LDAP sever in the GSM UMTS Voice Core Network OAM User Administration, Maintenance and Troubleshooting Guide, 411-8111-937.


268 Wireless Network Management System users Nortel Networks Confidential

Add, delete and modify users 8Use the procedures in the Wireless Network Management System Network Services Platform User Guide, 411-5221-211, to add, delete, and modify information about W-NMS users.

Configuring a user on the server of clients 8This procedure explains how to configure an explicit user on the server of clients. Upon completion of this procedure, the user can log into the server of clients from a client workstation and access W-NMS.


• know the IP address of the primary main server

• know a user name and password for the primary main server

• know the password for the root user on the server of clients

• have previously created a UNIX user name for the explicit user and know the following information for this user:

— UNIX group name

— UNIX password

— home directory path

Procedure 131:Configuring a user on the server of clients

Step Action

1 Log onto the server of clients using the UNIX user name for which you are creating an explicit user.

2 Enter:

ls -la

A list of directories appears.

3 Verify that .cshrc and .cshrc.nortel are in the list. If they are not in the list, enter:

cp -p /home/nortel/.cshrc .

cp -p /home/nortel/.cshrc.nortel .

—sheet 1 of 4—


Nortel Networks Confidential Configuring a user on the server of clients 269

Modifying the .cshrc file

4 Open the .cshrc file that exists in the UNIX user home directory, using an editor such as vi.

5 Ensure that the line for the j2re directory path is:

set JRE_DIR = “‘/bin/sh -c ’ls -d ${HOME}/j2re* 2>/dev/null’‘”

6 Ensure that the following environment variables are set to the same values as the environment variables found in the .cshrc file for the UNIX user nortel:

• OPENWINHOME

• MOTIFHOME

• XMBINDDIR

• XKEYSYMDB

• XFILESEARCHPATH

• path

• LD_LIBRARY_PATH

• NPX_PLUGIN_PATH

7 Save the .cshrc file.

8 Log off of the server of clients.

9 Log onto the server of clients using the UNIX user name.

Note: Logging on and logging off causes the environment variables of the UNIX user to be updated.

Procedure 131:Configuring a user on the server of clients (continued)

Step Action

—sheet 2 of 4—



10 Enter:

netscape &

The Netscape browser opens.

11 In the Location field enter:

http://<main server IP address>:8080/NSP

where <main server IP address> is the IP address of the primary main server

12 From the Edit menu, select Preferences...

13 On the left side of the window, under Category, click on Navigator.

14 On the right side of the window, click on the Use Current Page button.

15 Click on OK.

16 In the Netscape browser, click on the download link in:

First download and install the JRE 1.4.2_04 (Java Runtime Environment)

The Save As... (type application/x-sh) window opens.

17 Select the j2re-1_4_2_04-solsparc.sh file.

18 Click on OK.


cd <user home directory path>

where <user home directory path> is the home directory path of the UNIX user

chmod 755 j2re-1_4_2_04-solsparc.sh

./j2re-1_4_2_04-solsparc.sh



Verifying that the user can access W-NMS


Step Action

—sheet 3 of 4—


Nortel Networks Confidential Configuring NIMS-PrOptima for W-NMS on the server of clients 271

Configuring NIMS-PrOptima for W-NMS on the server of clients 8This procedure explains how to configure access to NIMS-PrOptima for W-NMS for an explicit user on the server of clients. Upon completion of this procedure, the user can log into the server of clients from a client workstation and access NIMS-PrOptima for W-NMS.

22 Enter:

netscape &

23 Click on LAUNCH GUI.

24 If a Proxy Configuration dialog box appears, click on None and click on OK. If a Security Warning dialog box appears, click on Start.

25 Log onto the Network Services Platform as a W-NMS user.

26 Make sure that you can access the appropriate OAM functions.

27 Log off of the Network Services Platform.

Verifying that the dfs client has the correct owner and rights

28 Enter:

cd /var/tmp

ls -l | grep dfs

A message similar to the following displays:

drwxrwxrwx 2 anontmpl ctxanon 512 Sep 18 15:14 dfs

29 If the access rights do not show up as shown in the previous example (rwxrwxrwx), perform the following steps:

a. Log into the server of clients using the root user name.

b. Enter the following command:

chmod 777 /var/tmp/dfs

c. Log off of the server of clients.


You are finished configuring an explicit user on the server of clients. If you want this user to be able to access NIMS-PrOptima for W-NMS, perform Procedure 132, If you want this user to be able to access the Software Repository Server, perform Procedure 133.


Step Action

—sheet 4 of 4—




• have performed Procedure 131, : Configuring a user on the server of clients

• know the following information for the user:

— UNIX user name

— UNIX password


Procedure 132:Configuring NIMS-PrOptima for W-NMS on the server of clients

Step Action


2 Enter:

cd <user home directory path>/j2re1.4.2_04/javaws

./javaws

The Java Web Start Application Manager window opens.

3 From the File menu, select Preferences.

4 Click on the Java tab.


6 enter the information for the jre to be used by PrOptima client:

• Platform Version: mycom

• Product Version: 1.4.2_04

• Product location: http://java.sun.com/products/autodl/j2se

• Command: <user home directory path>/j2re1.4.2_04/bin/java

where <user home directory path> is the full path of the explicit user’s home directory.


8 Close the Java Web Start Application Manager window.


You are finished configuring access to NIMS-PrOptima for W-NMS on the server of clients for the user.


Nortel Networks Confidential Configuring the SRS on the server of clients 273

Configuring the SRS on the server of clients 8This procedure explains how to configure access to the Software Repository Server (SRS) for a user on the server of clients. Upon completion of this procedure, the user can log into the server of clients from a client workstation and access the SRS.


• have performed Procedure 131: Configuring a user on the server of clients

• know the following information for the user on the server of clients:

— UNIX user name

— UNIX password


• know the password for the root user on the server of clients

• know the host name of the primary main server

• know a user Id and password that has access to the SRS

Procedure 133:Configuring SRS on the server of clients

Step Action

1 Log onto the server of clients using the UNIX user name you want to have access to the SRS.

2 Display the values of the environment variables by entering:

env

3 Ensure that the following variables are defined as shown:

LD_LIBRARY_PATH=/usr/lib:/usr/openwin/lib:/usr/dt/lib:/usr/ucblib:/opt/netRx2/lib:<user home directory path>/j2re1.4.2_04/plugin/sparc

NPX_PLUGIN_PATH=:<user home directory path>/j2re1.4.2_04/plugin/sparc

where <user home directory path> is the full path of the user’s home directory.

—sheet 1 of 3—



configuring the SRI plugin

4 Enter:

netscape &

The Netscape web browser window opens.

5 From the File menu, select Open Page.

The Netscape:File Browser window opens.

6 In the Selection field, enter <user home directory path>/j2re1.4.2_04/ControlPanel.html.


The Netscape:Open Page window opens, with the path you defined in step 6 in the URL field.

8 Click on the Open in Navigator button.

9 The Java Plug-in Control Panel opens in the Netscape web browser window.

10 Select the Enable Java Plug-in check box.

11 Under Java Console, click on the Show console radio button.

12 Select the Show Exception Dialog Box check box.

13 Click on the Apply button.

14 Click on the Advanced tab.

15 Click on the arrow in the drop-down list to open the list.

16 In the list, click on JRE 1.4.2_04 in /opt/nortel/3rd_party/java/j2sdk_1.4.2_04/jre.

17 Click on the Apply button.

18 Click on the Cache tab.

19 Click on the Clear Cache button.

The Clear Cache message displays.


21 Close the Netscape browser window.

Procedure 133:Configuring SRS on the server of clients (continued)

Step Action

—sheet 2 of 3—


Nortel Networks Confidential Configuring the SRS on the server of clients 275

Configuring the Java policy file

22 Log onto the server of clients using the root user name.

23 Enter the following command:

/opt/nortel/shell/iut_tools/install/iut_updatejavapolicy.sh -N<ServerHostName> -P<JavaPluginPath> -Osrm

where <ServerHostName> is the host name of the primary main server

where <JavaPluginPath> is <user home directory path>/j2re1.4.2_04

24 logout from the root account.

25 Log onto the server of clients using the UNIX user name that you want to have access to the SRS.

26 Enter:

netscape &

27 In the location field, enter:

http://<ServerHostName>:8080/srm

where <ServerHostName> is the host name of the primary main server

28 When you are prompted for a login ID and password, enter admin for the login and the password for the admin user.

29 Verify that you can log into the SRS.


You are finished configuring access to the SRS on the server of clients for the user.

Procedure 133:Configuring SRS on the server of clients (continued)

Step Action

—sheet 3 of 3—


277Nortel Networks Confidential Copyright © 2002–2005 Nortel Networks

Appendix A: SNMP and Multiservice Switch-based network element procedures 0

The procedures in this section are used for discovering or configuring SNMP and Multiservice Switch-based network elements. They are referenced from other sections of this document.

Discovering an SNMP network element 8Perform this procedure to discover a network element that uses SNMP. This procedure is referenced from some of the procedures in the Fault management and configuration management section of this document.

PrerequisitesBefore performing this procedure you must know the following information for the network element:

• IP address

• read community string

• read/write community string

• read/write port

• idi network element name (from the Network element discovery section for the network element)

• SNMP version number (the Restrictions and limitations section for the network element lists restrictions on the SNMP version)

SECURITY WARNINGDo not use community string “public” in the procedures in this section.


278 Appendix A: SNMP and Multiservice Switch-based network element proceduresNortel Networks Confidential Copyright © 2002–2005 Nortel Networks

Procedure 134:Discovering an SNMP network element

Step Action

1 If you are using W-NMS on a PC, log into a UNIX platform using Exceed. Refer to for an explanation and configuration information. If you are using W-NMS on a UNIX workstation, go to step 2.

2 Start the MDM toolset from the NSP:

a. Use a web browser on the W-NMS client computer to start the NSP. Log in as the admin user or a user with admin privileges

b. Select Configuration/Launch MDM Toolset for Administration.

The MDM Toolset window opens in the Exceed window on a PC, or on the desktop of a UNIX workstation.

3 Select Fault/IP Discovery.

An Alert window opens.

4 Click OK button.

The IP Device Discovery window opens.

5 In the IP Device Discovery window, click on the Network Settings tab.

6 Look at the bottom of the IP Discover window and confirm that the message “Edit Network Setting” appears. If it does not appear and the message “Viewing as read only” appears instead, you are not in edit mode and cannot continue the procedure. Possible reasons for this include that another user has the Network Settings panel open, or that network element discovery is in progress. Ask the other user(s) to leave the network settings pane or wait for the discovery process to complete.

7 Click on Edit / Add Row.

8 In the IP Device Discovery window, type the following information for each column on the new row added for the network element:

<IP Address> <Read Community string> <Read Write Community string> <Port>

The community strings must not be public.

9 Click and Select the correct idi <deviceName> under "Device Type" column. Then click and select the correct <SNMP version> under “SNMP Version” column.

10 In the IP Device Discovery window, click on Device/Discover.

The Discovery window opens.

11 Type <Device IP address> in the IP Address slot.

—sheet 1 of 2—


Appendix A: SNMP and Multiservice Switch-based network element procedures 279Nortel Networks Confidential Copyright © 2002–2005 Nortel Networks

Discovering an Mobile Location CenterThe Mobile Location Center (MLC) is configured so that W-NMS must poll the MLC on one IP address and receive traps on a different IP address. The two addresses are the OAM VIP address and the OAM NAT address respectively. Procedure 135 explains how to configure W-NMS to support this.

12 Select Method Direct. Do not Register to Receive Traps.

13 Refer to the network element integration procedure for the value of the Discover As field. The value is either no network element or a specific network element as noted in the procedure.

14 Click Start.

Status messages appear as the network element is being discovered. A success message appears.

15 In the IP Device Discovery window, click on File > Save.

16 Close the Discover window, IP Device Discovery window, and the MDM Toolset window.

17 Verify that alarms are being reported to the NSP Alarm Manager. The Discover As option overrides a number of validation operations performed by Device Discovery. This is required for some network elements where Device Discovery might incorrectly identify the network element if the validation was performed.

You are finished discovering the network element.

Procedure 134:Discovering an SNMP network element

Step Action

—sheet 2 of 2—



Note: When the connection to the network element is interrupted, it can take up to twice as long for W-NMS to recognize that the network element is reachable as it would if polling and traps were on the same IP address.

Procedure 135:Discovering an MLC

Step Action

1 Log in to the main server using the nortel user Id using a text terminal. For example, xterm or telnet.

2 Manually discover the network element by entering:

/opt/MagellanNMS/bin/dcdAddNode <devType> <devName> <addr> <community> <port> <devTypeNum>

where <devType> is the category name for the network element. For the MLC, use ELC<devName> is the name of the network element<addr> is the IP address of the network element. For the MLC, use the VIP address <community> is the polling (READ/WRITE) community string for the network element<port> is the polling port for the network element<devTypeNum> is 156 for the MLC

For example, assuming an IP address of 10.1.1.5, a polling community string of “xyz” and a GET port (SnmpRequestPort) of 8005, the command for the ELC is:

/opt/MagellanNMS/bin/dcdAddNode ELC EMLC 10.1.1.5 xyz 8005 156

Note: if the <devType> and <devName> are incorrect, the network element is discovered by other information in the command and the correct values are retrieved from the network element itself.

—sheet 1 of 2—



Discovering a GGSN You must use the procedures in this section to implement management cable redundancy for a GGSN network element. The GGSN can send traps from different IP addresses depending on which cables are connected at any given time. The main server must be configured to accept traps from any of these IP addresses. Procedure 136 configures W-NMS to support this. This procedure replaces Procedure 134; perform one procedure or the other for the network element, but not both.

Note: When the connection to the network element has been interrupted, it can take up to three times as long for W-NMS to recognize that the

3 Manually add the second address as a second polling address. (This is required because the trap address cannot be retrieved from the network element mib.) Type:

/opt/MagellanNMS/bin/dcdAddAddress <devType> <devName> <addr> <community> poll

where <devType> is the category name for the network element<devName> is the name of the network element <addr> is the IP address of the network element. For the ELC, this is the NAT address. <community> is the trap community string for the network element

For example, assuming an IP address of 10.1.1.6, and a trap community string of “xyz”, the command for the ELC is:

/opt/MagellanNMS/bin/dcdAddAddress ELC EMLC 10.1.1.6 xyz poll

You are finished discovering the network element. Add the network element to all appropriate layouts using the procedures in the Network Services Platform User Guide, 411-5221-211.

Procedure 135:Discovering an MLC

Step Action

—sheet 2 of 2—



network element is reachable as it would without management cable redundancy.

Procedure 136:Discovering a GGSN

Step Action

1 Log in to the main server using the nortel user Id using a text terminal. For example, xterm or telnet .

2 Manually discover the network element by entering:

/opt/MagellanNMS/bin/dcdAddNode <devType> <devName> <addr> <community> <port> <devTypeNum>

where <devType> is the category name for the network element. For the GGSN, use GSNS.<devName> is the name of the network element.<addr> is the IP address of the network element. For the GGSN, use the default IP address of this network element on the Gi ISP.<community> is the polling (READ/WRITE) community string for the network element (do not use the value “public”)<port> is the polling port for the network element<devTypeNum> is 183 for the GGSN.

For example, assuming an IP address of 10.1.1.5, a polling community string of “xyz” and the SNMP interaction port 161, the command for a GGSN named “GGSN” is

/opt/MagellanNMS/bin/dcdAddNode GSNS GGSN 10.1.1.5 xyz 161 183

3 Manually add the Management IP address (mgmt-eth0) and the first Auxiliary Management Interface IP address (mgmt-eth1) as polling addresses. For each of the two addresses, type:

/opt/MagellanNMS/bin/dcdAddAddress <devType> <devName> <addr> <community> poll

where <devType> is the category name for the network element<devName> is the name of the network element <addr> is the IP address of the interface. Perform this command twice, once with the mgmt-eth0 IP address and once with mgmt-eth1 IP address. <community> is the trap community string for the network element (do not use the value “public”)

For example, assuming mgmt-eth0 IP address of 10.1.1.6, and a trap community string of “xyz”, the command for the GGSN is:

./opt/MagellanNMS/bin/dcdAddAddress GSNS GGSN 10.1.1.6 xyz poll

You are finished discovering the network element. Add the network element to all appropriate layouts using the procedures in the Network Services Platform User Guide, 411-5221-211.



Removing an SNMP network elementUse the following procedure to remove an SNMP network element from the W-NMS.

Procedure 137:Removing an SNMP network element

Step Action

1 If you are using W-NMS on a PC, log into a UNIX platform using Exceed. Refer to the W-NMS Operator Guide, 411-5221-505 for information about Exceed. If you are using W-NMS on a UNIX workstation, go to step 2.

2 Open the NSP and open a layout containing the network element you want to delete.

3 Copy down the second line of text under the network element (for example, ALT184-10.0.10.5)

4 Start the MDM Toolset for Administration from the NSP:

a. Use a web browser on the W-NMS Client computer to start the NSP. Log in as the admin user or a user with admin privileges.

b. Open a layout containing the network element that you want to remove from W-NMS and click on the network element.

c. Select Configuration/Launch MDM Toolset for Administration

The MDM Toolset window opens in the Exceed window on a PC, or on the desktop of a UNIX workstation.

5 Select Fault/IP Discovery.

An Alert window opens.

6 Click the OK button.

The IP Device Discovery window opens.

7 Select the network element you wanted to delete from the Device list.

The entire row of the network element you selected is highlighted.

8 Select Device/Delete.

A Confirm window opens.

9 Click on both choices for Delete Options.

10 Click OK button.

A message “<NE Name/IP address> deleted” appears at the bottom of the IP Device Discovery window.

11 Close the IP Device Discovery window and the MDM Toolset window by selecting File/Exit in both windows.



12 If the network element does not show up in the layout you viewed in the NSP in step 2, you have completed this procedure.

13 If the network element is still in the layout, perform step 14 through step 17.

14 Open a text terminal on the main server using either telnet or an X-windows terminal emulator and log in using the nortel user Id.

15 Change the default directory to the directory containing W-NMS deletion tool for MDM-managed network elements:

cd /opt/nortel/exe/coreDA/current_coreDA

16 Verify that the identification of the network element you copied down matches that used by NeStore.sh by using NeStore.sh to list the network element:

./NeStore.sh -list | grep <NE_name>

where <NE_name> is the name you copied down in step 3.

The name of the network element is displayed. If it is not displayed, use ./NeStore.sh -list | more to list all of the NEs and use the d key to scroll through the list until you find the network element and copy down the name. Use the q key to quit from more.

17 Type:

./NeStore.sh -remove <NE_name>

where <NE_name> is the correct name of the network element.

The system confirms deletion of the network element:

<NE_name> removed from neStore.txt

notifying coreDA...

coreDA is notified!

The network element disappears from the NE Store and all layouts.

You are finished deleting the SNMP managed network element.

Procedure 137:Removing an SNMP network element

Step Action



Configuring a Multiservice Switch 8Use this procedure to configure the following Multiservice Switch-based network elements

• Multiservice Switch 7400, 15000, 20000


• Media Gateway (Media Gateway 3.0.1 shows up as WG)

• Interworking Function


• SGSN/GPRS

Procedure 138:Configuring a Multiservice Switch

Step Action

1 Log into a UNIX platform using Exceed on the W-NMS client PC. Refer to the W-NMS Operator Guide, 411-5221-505, for an explanation and configuration information.

2 From a web browser on the W-NMS Client PC, start the NSP on the main server. Log in as the admin user or a user with admin privileges.

3 In the Configuration menu, select Launch MDM Toolset (Security) from Main Server.

The Login window opens.

4 Log in using the root user ID and password.

The MDM Toolset window opens in the Exceed window.

5 From the System menu, select Administration and then Host Group Administration.

The Host Group Administration Window opens.


7 Click Add underneath the panel Passport Table (or select Options -> Passport Table Options -> Add Passport).

8 Type the Multiservice Switch node name in the Passport Name field.

9 Type the Multiservice Switch IP address in the IP Address field.

10 Click OK.

The Add New Passport dialog closes and the new Multiservice Switch node is added to the Passport Table.

—sheet 1 of 4—



11 If the Multiservice Switch belongs to an existing Multiservice Switch group (which means it shares its user ID and password with an existing Multiservice Switch) go to step 12. Otherwise, perform the following steps:

a. Click Add below the Passport Groups panel.

The Add New Passport Group dialog opens.

b. Type the name of the Multiservice Switch Group in the data entry box Passport Group Name.

c. Click OK.

The Add New Passport Group dialog closes. The new Multiservice Switch is added to the Passport Groups panel.

12 Select the new Multiservice Switch in the Passport Table panel.

13 If the Multiservice Switch belongs to an existing Multiservice Switch group (meaning that it has the same user ID and password as the other members of the group), select that group in the Passport Groups panel. If the Multiservice Switch does not belong to an existing Multiservice Switch group, select the group you just created in step 11 in the Passport Groups panel.

The button Add Passport <nodename> to group <group_name> below the Passport Attributes panel is activated.

14 Click Add Passport <nodename> to group <group_name>

The new Multiservice Switch is added to the selected group.

15 Select the new Multiservice Switch in the Passport Table panel.

16 Create a Multiservice Switch group called PPALL. See step 11 for instructions on how to create a group.

17 Select the PPALL group in the Passport Groups panel.

The button Add Passport <nodename> to group PPALL below the Passport Attributes panel is activated.

18 Click Add Passport <nodename> to group PPALL

The new Multiservice Switch is added to PPALL.

19 If you have no more Multiservice Switches to add, select File->Save.


Step Action

—sheet 2 of 4—



20 Click OK.

The Save Host Group File dialog closes. The current version of the file /opt/MagellanNMS/cfg/HGDS.cfg is saved with a time-stamped suffix. The contents of the Host Group Administration window are written to the file /opt/MagellanNMS/cfg/HGDS.cfg on the main server. The HGDS.cfg data is loaded into the HGDS the next time the HGDS is started.

21 Using the SMC, verify that the HGDS process in the group mdm_perf is running. If the HGDS process is not running, start it.

22 The Reload HGDS Configuration window opens with the following message:

Do you want to signal the related MDM servers to reload the HGDS configuration now?

23 Click Yes.

The related servers restart.

24 Close the Host Group Administration window.

Note: If the Multiservice Switch belongs to an existing Multiservice Switch group in MDM, you are finished this procedure.

25 Select System -> Administration -> Server Administration from the MDM Toolset menu.


26 Select Security -> Authorize. Leave the password field empty.

27 Click OK.

28 Select Edit/New Server.

29 Select the FMDR_<Group Name> and click on Edit.

30 Type:

/opt/MagellanNMS/bin/fmdr –u <userid> -p /opt/MagellanNMS/cfg/private/<password file name> -g <Group Name>

where <userid> is the user Id for logging into the Multiservice Switch (mdmuser), <password file name> is the name of the file that contains the encrypted password for mdmuser, and <Group Name> is the name of the group that the Multiservice Switch belongs to.

31 Select the Automatic startup at boot time check box.

32 Click Save and Start.


Step Action

—sheet 3 of 4—



Grouping Multiservice SwitchesThe Multiservice Switch 7400 and Multiservice Switch 15000 can be configured into the following network elements:


• SGSN/GPRS


33 Verify that the new group is running. In the Server Administration window, scroll down and look for the FMDR_<Group Name> in the list with Running State.

34 Select System/Administration/GMDR Administration from the MDM Toolset menu.

The GMDR <Server Name> Administration window opens.

35 Select Security/Login as Admin. Leave the password field empty.

36 Click OK.

37 Click Add.

The GMDR <Server Name> Add Server window opens.

38 Click Find Available Server. Find the FMDR_<Group Name> and select it. Click OK.

The Server Name and Host Name shows.

39 Type the User/Capability ID with the user ID for the Multiservice Switch.

40 Type the Password with the password for the Multiservice Switch.

41 Click OK.

42 In the GMDR <Server Name> Administration window, select the new GMDR Subserver name and click Connect.

The State changes from “Disconnected” to “Connecting” to “Connected”.

43 Select File/Exit.

44 You are finished enrolling the Multiservice Switch. If you do not need to perform further configuration for the network element (that is, if it is not a SGSN/UMTS, SGSN/GPRS, or IWF), add the network element to all appropriate layouts using the procedures in the Network Services Platform User Guide, 411-5221-211.


Step Action

—sheet 4 of 4—



This configuration changes the way the network elements are displayed in the Resource Browser and allows them to be managed using Wireless Internet Command Language.

Use Procedure 139 to group the individual Multiservice Switches so that they appear as a single network element in the Network Services Platform resource browser.

Procedure 139:Grouping Multiservice Switches

Step Action

1 Ensure that the Multiservice Switches you want to group have been integrated into W-NMS as described in the network element integration procedures.


3 Log into the main server as root or nortel using telnet or an xterm window.

4 Set the DISPLAY variable to the IP address of your workstation. Refer to the W-NMS Operator Guide, 411-5221-505, for more information.

5 Start the configuration tool by entering:


./MDMConfig &

The MDM Configuration Tool window opens in the X display window.

6 Click on the NE that you want add to a group (this is not the same as a Multiservice Switch Group as described in Procedure 138; it affects only the display of the NE in NSP, not the access privileges for the NE.)

7 Under the Group Type menu, select one of the following:

G_SGSN: if you want to group multiple SGSN/GPRS shelves (Element Type is G-SGSN)

U_SGSN: if you want to group multiple SGSN/UMTS shelves (Element Type is U-SGSN) and an AN

Note: Do not group an AN with an SGSN if the AN is set to local time and the AN is not in the same time zone as the main server.

WG: if you want to group multiple Wireless Gateway shelves (Element Type WG) and an AN

8 Under Group Name, type a name for the group.

—sheet 1 of 2—



9 On the File menu, click Save.


The change will be activated within 30 seconds for <MDM node name>.

10 In the command line terminal window on the main server, type:


11 Type:


where <NE_name> is the name of the network element.

Perform step 11 for each Multiservice Switch that you added to the group.

12 Log in to Network Services Platform as the admin user.

13 Edit an existing layout or create a new layout.

14 Verify that group has been successfully created. Search the NE store for an NE named GPRS_SGSN-<name> for a SGSN/GPRS, or UMTS_SGSN-<name> for a SGSN/UMTS where <name> is the name of the group you entered in step 8.

15 Add the grouped network element to all appropriate layouts using the procedures in the Network Services Platform User Guide, 411-5221-211.

You are finished grouping Multiservice Switch network elements in the NSP.

Procedure 139:Grouping Multiservice Switches

Step Action

—sheet 2 of 2—



Setting a Multiservice Switch as an Aggregation NodeUse Procedure 140 to designate a Multiservice Switch as an Aggregation Node application type.

Procedure 140:Setting a Multiservice Switch as an Aggregation Node

Step Action Step Action

1 Ensure that the Multiservice Switch that you want to designate as an Aggregation Node has been integrated into W-NMS using the network element integration procedures in this document.




5 To start the configuration tool, type:


./MDMConfig &


6 Click on the network element which you want to designate as an Aggregation Node. The Element Type must be PP.

7 Under the Application Type menu, select AN.




9 Add the network element to all appropriate network layouts using the procedures in the Network Services Platform User Guide, 411-5221-211.

You are finished setting a Multiservice Switch as an Aggregation Node.



Ungrouping a Multiservice Switch groupUse this procedure to ungroup a set of Multiservice Switches that are grouped into one node.

Procedure 141:Ungrouping a Multiservice Switch group

Step Action




4 Start the configuration tool by entering:


./MDMConfig &


5 In the line that contains the node you want to ungroup, click in the field under Group Type and remove the text.

The Group Type field and the Group Name field are both cleared.




7 In the command line terminal window on the main server, type:


8 Type:


where <NE_name> is the name of the node that you ungrouped.

9 Log in to Network Services Platform as the admin user.

10 Edit an existing layout or create a new layout.

11 Verify that group has been successfully removed and that the individual Multiservice Switch network elements show up in the layout.

You are finished ungrouping the Multiservice Switch node.



Deleting a Multiservice SwitchUse this procedure to delete a Multiservice Switch network element from a network layout in the Network Services Platform.

Procedure 142:Deleting a Multiservice Switch

Step Action

1 If you are using W-NMS on a PC, log into a UNIX platform using Exceed. Refer to the W-NMS Operator Guide, 411-5221-505, for an explanation and configuration information. If you are using W-NMS on a UNIX workstation, go to step 2.

2 Open the NSP and open a layout containing the network element you want to delete.

3 Copy down the second line of text underneath the network element (for example, 15KVSS172X).

4 On the Configuration menu, select Launch MDM Toolset (Security).

The MDM login window opens.

5 Log in using the root user Id and password.

The MDM Toolset window opens in the Exceed window.

6 Select the Host Group Administration tool:

System -> Administration -> Host Group Administration

The Host Group Administration Window opens.

7 Select the Passport tab.

8 Select the Multiservice Switch node in the Passport Table.

9 Click Delete below the Passport Table panel(or select Options -> Passport Table Options -> Delete Passport).

The Delete Passport dialog opens.

10 Click OK.

The Delete Passport dialog closes. The Multiservice Switch Node is removed from the Passport Table and from all of the Multiservice Switch groups of which it is a member.

11 If you have no more Multiservice Switches to delete, select File->Save.

12 Click Save.

—sheet 1 of 4—



13 If the HGDS is currently running, the following message displays:

The Host Group Directory Server configuration file has been modified.

An edit or deletion of the HGDS configuration was detected and cannot take effect by signaling MDM servers. The related MDM servers must be restarted later with the Server Administration tool.

14 Click OK.

15 Select System -> Administration -> GMDR Administration from the MDM Toolset menu

The GMDR <Server Name> Administration window opens.

16 Select Security -> Login as Admin and type the Admin password.

17 Click OK.

18 In the GMDR Subserver section, select the group name that Multiservice Switch NEs were removed from.

19 Click Show Components.

The GMDR Components window opens.

20 In the Components section, select the component.

21 Click Delete and then click OK to confirm the deletion. The Multiservice Switch is removed from the subcomponent list in GMDR Admin.

22 Click Close to close the GMDR components window.

23 On the File menu, click Exit.

24 Select System -> Administration -> Server Administration from the MDM Toolset menu.


25 Select Security -> Authorize and type the Admin password.

26 Click OK.

27 Right click the Host Group Directory Server (HGDS) and select Stop.

28 Right click the Passport Communications Manager (PP Comms Mgr) and select Stop.

29 Right click the GMDR process and select Stop.

30 Right click the Host Group Directory Server (HGDS) and select Start.


Step Action

—sheet 2 of 4—



31 Right click the Passport Communications Manager (PP Comms Mgr) and select Start.

32 Right click the GMDR process and select Start.

33 Right click the SNMP IP Discover Svr and select Stop then Start.

34 Right click (select/add selection) the FMDR_<Group Name> servers for any Multiservice Switch groups that were stopped due to the restart of the Passport Communications Manager and select Start.

35 In the Preside MDM window, select Fault -> Network Viewer.

36 On the Network Model Edit menu, select Enable Network Model Editing.

37 If the NV Network Model Edit Node Position Dialog window opens, click the Send Current Position to NM button.

38 If the icons are not expanded, click the Default_SITE/ALL ICON and select the first square on the menu bar to Expand in Place. Select the Multiservice Switch icon you want to delete.

39 On the Network Model Edit menu, select Delete Selected Components.

40 In the Delete Components window, highlight the Multiservice Switch and click Delete.

41 On the Network Model Edit menu, select Leave Network Model Editing.

42 Click the Exit and Save button and type a file name.

43 Click Save.

The network element does not show up in the layout you viewed in the NSP in step 2. You have completed this procedure.

44 If the network element is still in the layout, perform step 45 through step 49.

45 Open a text terminal on the main server and log in using the nortel user Id.

46 Change to the directory with the CEM de-enrollment script for MDM-managed network elements:



Step Action

—sheet 3 of 4—



47 Verify that identification of the network element you copied down matches that used by NeStore.sh by using NeStore.sh to list the network element:

./NeStore.sh -list | grep <NE_name>

where <NE_name> is the name you copied down in step 3.

The name of the network element is displayed.

48 If the name of the network element is not displayed, use ./NeStore.sh -list | more to list all of the NEs and use the d key to scroll through the list until you find the network element and copy down the name. Use the q key to quit from more.

49 Type:


where <NE_name> is the name of the network element.

The system confirms the deletion of the network element:

<NE_name> removed from neStore.txt

notifying coreDA...

coreDA is notified!

The network element will be gone from the NE Store and all layouts.

You are finished deleting the Multiservice Switch from W-NMS.


Step Action

—sheet 4 of 4—



Appendix B: Filtering alarms 9This appendix explains the Core device adapter (DA) alarm filtering feature of W-NMS.

Core DA alarm filtering 9This section contains procedures for administering Core DA alarm filtering. Core DA alarm filtering is used to specify filters for message alarms (Manual Clear Alarms) and message alarm groups for network elements that are managed by MDM. The alarms are filtered by the Core DA before they are passed to NSP. Core DA alarm filtering cannot be used for filtering set type alarms.

Core DA alarm filtering allows you to pass specific alarms or alarm groups, block specific alarms or alarm groups, pass all alarms, or block all alarms. You can also view the current alarm filtering settings. The default setting for Core DA alarm filtering is to block all message alarms except for the alarms listed in Table 29. The alarms listed in Table 29 are passed even if the filtering is set to block all message alarms.

PASSING MESSAGE ALARMSIf you set a filter to pass message alarms, you must monitor the alarm rate and total number of active alarms. Passing all message alarms can lead to system failure.

Table 29

Alarm number Description

70060002 NMIS Alarm: nmiLoginFailedIndex_c

70071000 Frame Relay Alarm: frsLmiSubIndex_c

70120101 PCS Alarm: indexCardTrapDataInfo_c

70120201 PCS Alarm: indexLpSwitchImminent_c

70120203 PCS Alarm: indexLastInServiceTime_c


298 Appendix B: Filtering alarmsNortel Networks Confidential Copyright © 2002–2005 Nortel Networks

70263002 PmsLan Alarm: pmsLanOamEnetInitTestSo_c

70650000 SG Alarm: sgIndexMappingTableFull_c

70660100 SS7 Alarm: ss7IndexSignallingLinkTestFail_c

70681001 SGSN Alarm: sasDiskFull

70681002 SGSN Alarm: sasDiskFailed

70681005 SGSN Alarm: gscOutOfResources

70681006 SGSN Alarm: gscMaxSubscribers

70681009 SGSN Alarm: gsdMaxAttSubscribers

70681012 SGSN Alarm: gsdMaxAllocatedLle

70681016 SGSN Alarm: sasMemPreAllocDone

70681018 SGSN Alarm: gscInitFailed

70681020 SGSN Alarm: gtlMaxBvcsPerNseExceeded

70681041 SGSN Alarm: sigBvcReset

70681499 SGSN Alarm: gtlBvcMismatch

70681500 SGSN Alarm: uscOutOfResources

70681507 SGSN Alarm: uscInitialization

70681521 SGSN Alarm: cpuOverload

70681528 SGSN Alarm: lispDfFailure

70681531 SGSN Alarm: attachThreshold

70681532 SGSN Alarm: pdpActivationsThrld

70681533 SGSN Alarm: sigSs7Problem

70681554 SGSN Alarm: sgsnAuditMemCorruption

70681566 SGSN Alarm: sasReadyForSwitchover

70681572 SGSN Alarm: scRedundancySyncLossAlarm

70681573 SGSN Alarm: switchoverDuringCheckpointing

70681996 SGSN Alarm: gmmResourcesLow

Table 29

Alarm number Description


Appendix B: Filtering alarms 299Nortel Networks Confidential Copyright © 2002–2005 Nortel Networks

For a list of message alarms for the managed network element refer to the documentation associated with the network element. For example:

• for the GGSN refer to the GGSN Fault Cartridge User Guide, 411-8111-531

• for the SGSN refer to SGSN Alarms Reference Manual, 411-5221-500

• for the Wireless Gateway refer to Wireless Gateway Alarms Reference Manual, 411-8111-500

• for SNMP device alarms refer to the relevant fault cartridge user guide

To pass a specific message alarm from the NE, you must add the message alarm to the list of passed alarms. Refer to the following procedures for more information.



Starting the alarm filtering CLIPerform this procedure to start the alarm filtering command line interface (CLI). You can have one and only one instance of the alarm filtering CLI running at a time.

PrerequisitesBefore making changes to the alarm filtering settings, ensure that all processes in the adapters_primary group are running. You can look at the processes in the adapters_primary group using the SMC.

Procedure 143:Starting the alarm filtering CLI

Step Action


2 In a terminal window type:


./alarmFilter.start

The ALARMFILTER menu displays.

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

ALARMFILTER

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

1. PASS ALARM IDs or ALARM GROUPS

2. BLOCK ALARM IDs or ALARM GROUPS

3. LIST CURRENT FILTERS

0. EXIT

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

Enter your choice (0-3):

3 Refer to the following procedures for information about the ALARMFILTER menu items.

4 If you made any changes to the alarm filtering settings, verify that they have taken effect. If the changes have not taken effect, restart the adapters_primary group using the SMC.

5 End of procedure.



Passing alarm Ids or alarm groupsPerform this procedure to specify:

• alarm numbers to be passed

• alarm groups to be passed

• pass all alarms

Procedure 144:Passing alarm Ids or alarm groups

Step Action

1 Start the alarm filtering CLI as described in: Starting the alarm filtering CLI.

2 Type:

1

The PASS MENU menu displays.

Passing alarm numbers

3 Type:

1


Enter the alarm to be passed [Q = end of list]:

4 Type an eight digit alarm number and press the Enter key.

5 Repeat step 4 for each alarm number that you want to pass to NSP.

6 Type q or Q when you are finished entering the alarm numbers.

7 Perform Procedure 147.

Passing alarm groups

8 Type:

2


Enter the alarm group to be passed [Q = end of list]:

9 Type a four digit number and press the Enter key. (All alarms that start with the four digits will be passed.)

—sheet 1 of 2—



Blocking alarm Ids or alarm groupsPerform this procedure to specify:

• alarm numbers to be blocked

• alarm groups to be blocked

• block all alarms

10 Repeat step 9 for each alarm group that you want to pass to NSP.

11 Type q or Q when you are finished entering the alarm groups.


Passing all alarms

13 Type:

3


Selecting PASS ALL alarms will clear all existing filter settings in the database

Passing ALL alarms may affect performance

Are you sure you want to continue?

Enter Y/N:

14 Type:

Y



Procedure 144:Passing alarm Ids or alarm groups

Step Action

—sheet 2 of 2—



Procedure 145:Blocking alarm Ids or alarm groups

Step Action


2 Type:

2

The BLOCK MENU menu displays.

Blocking alarm numbers

3 Type:

1


Enter the alarm to be blocked [Q = end of list]:

4 Type an eight digit alarm number and press the Enter key.

5 Repeat step 4 for each alarm number that you want to block from NSP.

6 Type q or Q when you are finished entering the alarm numbers.

Block alarm groups

7 Type:

2


Enter the alarm group to be blocked [Q = end of list]:

8 Type a four digit number and press the Enter key. (All alarms that start with the four digits will be blocked.)

9 Repeat step 8 for each alarm group that you want to block from NSP.

10 Type q or Q when you are finished entering the alarm groups.

—sheet 1 of 2—



Viewing the current filtersPerform this procedure to view the current alarm filter settings.

Passing previously blocked alarmsAfter you have removed the filtering of previously blocked alarms using the ALARMFILTER menu, you must perform Procedure 147. This procedure

Blocking all alarms

11 Type:

3


Selecting BLOCK ALL alarms will clear all existing filter settings in the database

Are you sure you want to continue?

Enter Y/N:

12 Type:

Y


Procedure 146:Viewing the current filters

Step Action


2 Type:

3

The current alarm filtering settings display.

3 End of procedure.

Procedure 145:Blocking alarm Ids or alarm groups

Step Action

—sheet 2 of 2—



clears the alarms from the raw feed so that they are passed through to the managed feed.

Procedure 147:Passing previously blocked alarms

Step Action

1 Log into NSP.

2 Open the network layout that contains the NE from which you removed the filtering.

3 Right-click on the NE and Select CEM -> Open from the object menu.

4 In the Nortel Element Browser window, make sure that the Managed Feed icon is not selected. ie. Cancel the selection if the Managed Feed icon is selected. This enables Raw Feed.

5 In the Selected Time Range area, select a date at least 30 days prior to the current date.

6 Clear all previous instances of the specific alarm number which is no longer being filtered.

7 Perform step 6 for each alarm number that is no longer being filtered.

8 End of procedure.



Appendix C: Patching W-NMS 10This appendix explains how to apply software patches to the W-NMS. There are three steps in applying a W-NMS patch:

1. Obtain the patch

2. Install the patch on the Software Repository Server (SRS)

3. Apply the patch to the appropriate server

Obtaining a patch 10You can obtain a patch by:

• copying it from a compact disc supplied by Nortel

• downloading it from the Nortel web site, www.nortel.com

If you have a software patch compact disc supplied by Nortel, copy the appropriate patch from the compact disc to your workstation. See the following procedure for instructions on how to download a patch from the Nortel web site.

Downloading a patch 10Use this procedure to download a software patch from the Nortel web site www.nortel.com.

PrerequisitesBefore performing this procedure, you must know:

• a User ID and password that allows you to access the Nortel Customer Support Software web page

• the name of the software patch that you want to download


308 Appendix C: Patching W-NMSNortel Networks Confidential Copyright © 2002–2005 Nortel Networks

Procedure 148:Downloading a patch

Step Action

1 In the address field of a web browser (on the SRS) enter the following URL:

http://www.nortelnetworks.com

2 Under Support & Training, click on Software Downloads.

3 On the left side of the window, click on Log In.

4 In the Log In window, type a User ID and Password.

5 Click on Log In.

6 Click on the Browse Product Support tab.

7 Click on the Product Families link.

8 Click on Wireless & Mobility.

9 To download a patch for GPRS, click on Software under General Packet Radio Services (GPRS/EDGE).

10 To download a patch for UMTS, click on Software under UMTS Networks.

11 Use the filters at the top of the page to search for the patch you want or you can scroll through the list.

12 Click on the title of the patch.

13 In the Software Detail Information window, do one of the following:

a. Beside Readme File, click on the hyperlink to view the documentation for the patch.

b. Beside Readme File, right-click on the hyperlink and select Save Target As to save the documentation for the patch to the server.

14 Right-click on the hyperlink beside File Download and select Save Target As to save the patch file to the SRS. Save the patch file to a temporary location.


Appendix C: Patching W-NMS 309Nortel Networks Confidential Copyright © 2002–2005 Nortel Networks

Installing a patch on the SRS 10Perform this procedure to install a patch on the SRS using the Software Repository Manager (SRM).

PrerequisitesBefore performing this procedure, you must know the host name of the SRS.

Procedure 149:Installing a patch on the SRS

Step Action

1 Open the web browser on the SRS.

2 In the address field, type the following URL:

http://<SRS host name>:8080/srm/

where <SRS host name> is the host name of the SRS

A window opens with the following message:

Enter Network Password

3 Type values for the user name and password for the admin user ID.

4 Click on Install Software Release.

A window opens with the following message:

Password Needed - Networking

5 Type values for the user name and password for the admin user ID.

6 In the Software Repository Installation window, do one of the following:

a. To install a patch that is on a compact disc, go to step 7. To use this option, the patch must be compressed with a "srs.gz" filename extension on the compact disc. If the patch has been recompressed in a different format on the compact disc, then you must copy the patch file from the compact disc to the server, decompress it to restore the "srs.gz" format, and then perform the instructions for step b.

b. To install a patch that is located on in a directory on the server, go to step 11.


310 Appendix C: Patching W-NMSNortel Networks Confidential Copyright © 2002–2005 Nortel Networks

Applying a patch 10Refer to the readme file that comes with the patch for information on how to apply it.

7 Click on the CD-ROM button to install a patch that is on a compact disc.

8 Select the drive which contains the compact disc.

9 Click on the Ok button.


SRM - Software Installation Message

Do you want to install the version <patch CD version>?

10 Go to step 13.

11 Click on the Local Software Delivery File button to install a patch that is located in a directory on the server.

12 Click on the Browse button and select the location of the patch file.

13 Click on the Ok button.

A window opens, showing the progress of the installation.

14 Click on Save Details.

Procedure 149:Installing a patch on the SRS

Step Action



Index 11

Aaccess control 155, 156accounts

admin 193, 205passwords 187

ADC 145configuration tool 133in NSP 136restrictions 101, 134

admin 193, 205, 267Aggregation Node 65, 285, 291alarm filtering 297Alarm on threshold 95AllowedAccess 107Application Switch 5ASCII Data Collector, see ADCaudit logs

sending to CSAL 171audit trail 155, 165

disabling 176enabling 174log files 168processing menu 170

Bbackup and restore 166Border Gateway 11BPS 2000 14BSM 166Business Policy Switch 2000, see BPS 2000

CCDI 137CEM 137Centralized Security Audit Logging, see

CSALchanging passwords 187Circuit Data Interface, see CDICLI*manager 252combined MSC/HLR 137configuring

crontab 131Configuring the USP-based UNPM 87Core Element Manager 267Core Element Manager, see CEMcron job 131CSAL 166, 170

audit events sent to 168


312 Index Nortel Networks Confidential

DData Server 16debug statistics 117default shell 267Deleting a Multiservice Switch 293deleting devices 283, 293Deleting the USP-based UNPM 90Device Owner 124DHCP, see MetaSolv Policy ServicesDMS Trinode

server-based 35DNS, see MetaSolv Policy Services

EEthernet Routing Switch 8600 70Ethernet Switch 450 21explicit users 268

FFile Prober Manager 114FTP 157Funk SBR 24Funk Steel-Belted Radius, see Funk SBR

GGa 124GGSN 32, 131, 133, 141, 145, 281Gi 124Gn 124grouping Multiservice Switches 288

Hhardening the OS 157, 179hardware 230HLR

server-based 35

HLR 100 35, 137, 141HLR 200 35, 137, 141HP-SIG 77

IInternet Service Provider, see ISPInterworking Function 285Interworking Function, see IWFIP network multipathing, See IPMPIP Services Edge Router 5500 48IPMP 32ISP 124IWF 65, 137, 288

Jjob

in PAM 152

LLIG-D Comverse 51LIG-D, see LIG-D Comverselog file

performance management 141log files

audit trail 168

MMain Server 166managing passwords 187MDP 99, 100, 111, 114, 118, 119, 142, 229Media Gateway 65, 285MetaSolv Network Mediation 54MetaSolv Policy Services 58MGW 137MLC 62, 279MNN, see MetaSolv Network MediationMobile Location Center, see MLCMSC 137

server-based 35Multiservice Switch 285

as an AN 291configuring 285deleting 293grouping 288ungrouping 292


Nortel Networks Confidential Index 313

Multiservice Switch 15000 65, 288Multiservice Switch 20000 65Multiservice Switch 7440 65, 288Multiservice Switch 7480 65, 288mycom client, see NIMS-PrOptima client

NNDS account 189, 191Net Guardian 67NetRX 251network element discovery 277Network Services Platform 1Network Services Platform, see NSPNIMS-PrOptima client 271nortel 267NSP 1, 136, 137

OOpenSSH 155OS hardening 155, 156, 157

access control 156disabling 159disabling services 156enabling 157network communication 157optional features 163overview 156remove users 156system accounts 160verifying 162

PPAM 147

configuring a job 152configuring a profile 150deleting a profile 154main window 150modifying a profile 153

passwordsadmin 193, 205changing 187, 190, 191default 187, 189, 231encryption 187hardware 230recommendations 187

PDI 111, 142Performance Application Manager, see PAMperformance data

verifying 141performance management 105

ADCdisabling data collection 142, 145GGSN 131log file 141MDP 111SCS 128SIG 131Wireless Gateway 107

Performance Manager 117Performance Meter icon 159performance server 166

verifying processes on 105profile

in PAM 150PrOptima client, see NIMS-PrOptima client

RR4 BICN MSC 137Radius 24removing devices 283, 293root 267

SSCS 124

Log Server 128SDM 35sdmuser 267security 155

audit trail 165BSM 166CSAL 166OS hardening 156

Server of Clients 268Service Creation System, see SCSSGSN 288

debug statistics 117SGSN/GPRS 285

fault and configuration 75SGSN/UMTS 285

fault and configuration 75


314 Index Nortel Networks Confidential

SGW 76, 137SIG 77, 131, 133, 141, 145Signalling Gateway, see SGWSLR 137

fault and configuration 74SMC 105SMG 1SNMP network element

discovering 277removing 283

SNMP networrk element 283software patch 307

applying 310downloading 307installing on SRS 309

software repository server, see SRSSolaris SunShield Basic Security Module, See

BSMSRS 273, 309SS7 IP Gateway, see SIGSystem ManaGement, see SMG

Ttools 241

Uunhardening the OS 159un-integration 283, 293Universal Number Portability Master, see

UNPMUNIX accounts 190UNPM 137

deleting 90SSR-based 83USP-based 87

unused services 156user administration 267user ID

admin 267nortel 267root 267sdmuser 267see also passwords 187

utilities 241

Vverifying

OS hardening 162verifying performance data 141VPN Router 91

WWeb Switch 184 92Wireless Network Management, see W-NMSW-NMS 1www.nortelnetworks.com 307

XXML 141


Family Product Manual Contacts Copyright Confidentiality Legal

UMTS, GPRS

Nortel Wireless Network Management SystemAdministrator Guide

To order documentation from Nortel Networks Global Wireless Knowledge Services, call (1) (877) 662-5669

To report a problem in this document, call(1) (877) 662-5669or send e-mail from the Nortel Networks Customer Training & Documentation World Wide Web site athttp://www.nortelnetworks.com/td

Copyright © 2002–2005 Nortel Networks, All Rights Reserved

NORTEL NETWORKS 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.

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

* Nortel Networks, the Nortel Networks logo, the Globemark, and Unified Networks are trademarks of Nortel Networks. Citrix and MetaFrame are trademarks of Citrix Systems, Inc. in the United States. Exceed is a trademark of Hummingbird Communications Ltd. Mycom and NIMS-PrOptima are trademarks of Mycom International. Solaris is a trademark of Sun Microsystems Inc. Trademarks are acknowledged with an asterisk (*) at their first appearance in the document.Document number: 411-5221-305Product release: OAM 4.2Document version: Standard 04.10Date: December 2005Originated in North America/Canada

umts, gprs nortel wireless network management...

Documents