Cisco · Cisco Reader Comment Card General Information 1 Years of networking experience: Years of...

Cisco Reader Comment CardGeneral Information

1 Years of networking experience: Years of experience with Cisco products:

2 I have these network types: LAN Backbone WANOther:

3 I have these Cisco products: Switches RoutersOther (specify models):

4 I perform these types of tasks: H/W installation and/or maintenance S/W configurationNetwork management Other:

5 I use these types of documentation: H/W installation H/W configuration S/W configurationCommand reference Quick reference Release notes Online helpOther:

6 I access this information through: Cisco.com CD-ROMPrinted docs Other:

7 I prefer this access method:

8 I use the following three product features the most:

Document Information

Document Title: Cisco Signaling Gateway Manager User Guide

Part Number: 78-15589-01 S/W Release (if applicable): 3.0

On a scale of 1–5 (5 being the best), please let us know how we rate in the following areas:

Please comment on our lowest scores:

Mailing Information

Company Name Date

Contact Name Job Title

Mailing Address

City State/Province ZIP/Postal Code

Country Phone ( ) Extension

Fax ( ) E-mail

Can we contact you further concerning our documentation? Yes No

You can also send us your comments by e-mail to [email protected], or by fax to 408-527-8089.When mailing this card from outside of the United States, please enclose in an envelope addressed to the location on the back of this card with the required postage or fax to 1-408-527-8089.

The document is written at mytechnical level of understanding.

The information is accurate.

The document is complete. The information I wanted was easy to find.The information is well organized. The information I found was useful to my job.

% %% %

NO POSTAGENECESSARY

IF MAILEDIN THE

UNITED STATES

BUSINESS REPLY MAILF I R S T - C L A S S M A I L P E R M I T N O . 4 6 3 1 S A N J O S E C A

POSTAGE WILL BE PAID BY ADDRESSEE

DOCUMENT RESOURCE CONNECTIONCISCO SYSTEMS INC170 WEST TASMAN DRSAN JOSE CA 95134-9916

Corporate HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000

800 553-NETS (6387)Fax: 408 526-4100

Cisco Signaling Gateway ManagerUser GuideSoftware Release 3.0

Customer Order Number: DOC-7815589=Text Part Number: 78-15589-01

http://www.cisco.com

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, iQ Net Readiness Scorecard, Networking Academy, and ScriptShare are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0303R)

Signaling Gateway Manager User GuideCopyright © 2003 Cisco Systems, Inc. All rights reserved.

78-15589-01

C O N T E N T S

About This Guide xvii

Document Objectives xviii

Document Audience xviii

Document Organization xviii

Document Conventions xix

Related Documentation xxi

Obtaining Documentation xxii

Cisco.com xxii

Documentation CD-ROM xxii

Ordering Documentation xxiii

Documentation Feedback xxiii

Obtaining Technical Assistance xxiv

Cisco.com xxiv

Technical Assistance Center xxiv

Cisco TAC Website xxv

Cisco TAC Escalation Center xxvi

Obtaining Additional Publications and Information xxvi

C H A P T E R 1 SGM Overview 1-1

What is ITP? 1-1

What is SGM? 1-2

What is Client/Server Architecture? 1-5

iiiCisco Signaling Gateway Manager User Guide

Contents

C H A P T E R 2 Getting Started with SGM 2-1

Starting SGM 2-2

Running Simultaneous SGM Sessions 2-7

Exiting the SGM Client 2-7

C H A P T E R 3 Managing ITP Networks Using SGM 3-1

Becoming the Root User (Solaris Only) 3-2

Configuring SNMP 3-2

Discovering the Network 3-6

Configuring Seed Files 3-20

Creating a New Seed File 3-20

Modifying an Existing Seed File 3-22

Creating and Modifying Seed Files Using a Text Editor 3-24

Working with Views 3-26

Creating a View 3-27

Loading the DEFAULT View 3-35

Loading a Client-Specific View 3-35

Working with Linksets 3-37

Viewing Basic Information for Linksets 3-38

Viewing Detailed Information for a Linkset 3-42

Viewing Real-Time Data for a Linkset 3-54

Editing a Linkset 3-84

Viewing Notes for a Linkset 3-87

Deleting a Linkset 3-88

Deleting a Linkset from Your Network 3-88

Deleting a Linkset from the SGM Database 3-88

Ignoring a Linkset 3-90

Viewing Ignored Linksets 3-90

ivCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

Working with Nodes 3-91

Viewing Basic Information for Nodes 3-92

Viewing Detailed Information for a Node 3-96

Viewing CPU Statistics for a Node 3-121

Editing a Node 3-124

Editing Node Properties 3-124

Attaching a Note to a Node 3-126

Editing SNMP IP Addresses for a Node 3-127

Viewing Notes for a Node 3-128

Deleting a Node 3-130

Deleting a Node from Your Network 3-130

Deleting a Node from the SGM Database 3-130

Deleting a Node from the SGM Discovery Database 3-132

Unmanaging and Managing a Node 3-133

Polling a Node 3-134

Excluding a Node from a View 3-136

Working with Signaling Points 3-136

Viewing Basic Information for Signaling Points 3-137

Viewing Detailed Information for a Signaling Point 3-141

Editing a Signaling Point 3-162

Editing Signaling Point Properties 3-163

Attaching a Note to a Signaling Point 3-165

Viewing Notes for a Signaling Point 3-166

Deleting a Signaling Point 3-167

Deleting a Signaling Point from Your Network 3-167

Deleting a Signaling Point from the SGM Database 3-167

Unmanaging and Managing a Signaling Point 3-169

Excluding a Signaling Point from a View 3-170

vCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

Working with Links 3-170

Viewing Basic Information for Links 3-171

Viewing Detailed Information for a Link 3-175

Viewing Real-Time Data for a Link 3-186

Editing a Link 3-230

Viewing Notes for a Link 3-232

Deleting a Link 3-233

Deleting a Link from Your Network 3-233

Deleting a Link from the SGM Database 3-234

Ignoring a Link 3-235

Viewing Ignored Links 3-235

Working with Events 3-235

Viewing Basic Information for All Events 3-236

Viewing Events for a Specific Object 3-240

Viewing Detailed Information for an Event 3-243

Viewing Real-Time Data for an Event 3-244

Setting an Event Filter 3-244

Viewing Event Properties 3-253

Attaching a Note to an Event 3-256

Viewing Notes for an Event 3-258

Viewing the Topology of the Network 3-259

Viewing Server Status Information 3-274

Finding Information in a Window 3-278

Resizing, Sorting, and Hiding Table Columns 3-279

Viewing Online Help 3-280

Editing an ITP Route Table File 3-281

Editing a Global Title Translation Table 3-290

viCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

Working with SGM Statistics Reports 3-334

Modifying the Way SGM Handles Statistics Reports (Solaris Only) 3-335

Changing the SGM Reports Directory (Solaris Only) 3-342

Viewing SGM Network Statistics Reports 3-343

Viewing the Linkset Statistics Hourly Reports 3-344

Viewing the Linkset Statistics Daily Summary Reports 3-346

Viewing the Link Statistics Hourly Reports 3-349

Viewing the Link Statistics Daily Summary Reports 3-354

Viewing the Five Day Link Utilization Report 3-359

Viewing the Hourly Network Statistics Export Files 3-361

Viewing the Daily Network Statistics Export Files 3-362

Viewing the Rolling Network Statistics Export Files 3-363

Viewing SGM Accounting Statistics Reports 3-364

Viewing the Accounting Statistics Daily Detail Reports 3-364

Viewing the Daily Accounting Statistics Export Files 3-368

Generating and Viewing Custom SGM Statistics Reports 3-369

Generating a Custom Network Statistics Report 3-369

Generating a Custom Accounting Statistics Report 3-372

Including Specific Nodes in Custom Reports 3-374

Including Specific Linksets in Custom Reports 3-376

Excluding Specific Nodes from Custom Reports 3-377

Excluding Specific Linksets from Custom Reports 3-378

Viewing the Custom Network Statistics Export Files 3-379

Viewing a Custom Accounting Statistics Report 3-380

Viewing a Custom Link Statistics Summary Report 3-383

Viewing a Custom Linkset Statistics Summary Report 3-387

Viewing SGM Point Code Inventory Reports 3-390

Viewing the Current Point Code Inventory 3-391

Viewing the Daily Point Code Inventory Daily Reports 3-392

Viewing the Daily Point Code Inventory Export Files 3-394

viiCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

Viewing SGM Statistics Reports Logs 3-394

Viewing the SGM System Reports Log 3-394

Viewing the SGM System Report Parameters and Timers 3-395

Printing SGM Windows 3-398

Connecting to a New Server 3-399

Integrating SGM with Other Products 3-401

Integrating SGM with HP OpenView 3-401

Integrating SGM with CiscoWorks2000 3-402

Launching the CiscoWorks2000 Device Center 3-402

Launching CiscoView 3-403

Using the Windows Start Menu 3-403

Launching the SGM Client 3-404

Launching the SGM GTT Client 3-404

Changing the Default SGM Server Name 3-404

Changing the Default SGM Telnet Path 3-405

Launching the SGM DOS Prompt 3-405

Launching the SGM SSL Certificate Tool 3-406

Uninstalling SGM 3-406

Viewing the SGM README File 3-406

C H A P T E R 4 Configuring SGM Security 4-1

Configuring SGM User-Based Access 4-1

Implementing SGM User-Based Access (Solaris Only) 4-2

Creating Secure Passwords 4-5

Configuring SGM User Authentication Levels (Solaris Only) 4-6

Basic User (Level 1) Access 4-6

Power User (Level 2) Access 4-7

Network Operator (Level 3) Access 4-8

viiiCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

Network Administrator (Level 4) Access 4-8

System Administrator (Level 5) Access 4-9

Automatically Disabling Users and Passwords (Solaris Only) 4-10

Manually Disabling Users and Passwords (Solaris Only) 4-13

Enabling and Modifying Users and Passwords (Solaris Only) 4-15

Maintaining Your SGM Security System (Solaris Only) 4-17

Specifying a Super User (Solaris Only) 4-22

Implementing SSL Support in SGM 4-24

Enabling SSL Support in SGM 4-25

Downloading the SGM Server’s Self-Signed SSL Certificate 4-28

Importing an SSL Certificate to an SGM Client 4-29

Exporting an SSL Certificate 4-32

Viewing Detailed Information About an SSL Certificate 4-34

Managing SSL Support in SGM 4-36

Disabling SSL Support in SGM 4-37

Limiting SGM Client Access to the SGM Server (Solaris Only) 4-38

C H A P T E R 5 Configuring SGM for Your Network 5-1

Importing SNMP Community Names from CiscoWorks2000 (Solaris Only) 5-2

Retaining Unknown Objects (Solaris Only) 5-3

Modifying Preference Settings 5-3

Modifying Overall Preference Settings 5-5

Modifying Node Table Column Settings 5-16

Modifying Linkset Table Column Settings 5-18

Modifying Event Table Column Settings 5-19

Modifying the Message Display 5-20

Changing the Location of SGM Message Log Files 5-20

Changing the Size of the SGM Message Log File 5-21

ixCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

Changing the Time Mode for Dates in Log Files 5-21

Changing the Age of the SGM Message Log Files 5-21

Setting the Point Code Format (Solaris Only) 5-21

Enabling SNMP Traps (Solaris Only) 5-23

Modifying the SGM Event Configuration File (Solaris Only) 5-26

Editing the SGM Event Configuration File 5-28

Modifying Basic Settings 5-28

Modifying the Size of the Event Database 5-28

Modifying the Maximum Age for Events 5-29

Modifying the Event Database Maintenance Interval 5-29

Modifying the Event Automation Timeout Interval 5-30

Enabling SGM to Process Events from Undiscovered Nodes 5-30

Modifying Event Categories, Severities, Colors, and Message Text 5-30

Modifying Event Categories 5-31

Modifying Event Severities and Colors 5-32

Modifying Event Message Text 5-32

Automating Events 5-33

Setting Sounds for Events at the SGM Server 5-35

Adding New Event Categories and Severities 5-35

Modifying Help for Events 5-37

Validating the Modified SGM Event Configuration File 5-38

Setting Sounds for Events at an SGM Client 5-40

Limiting Traps by IP Address (Solaris Only) 5-45

Setting the DISPLAY Variable (Solaris Only) 5-47

Backing Up or Restoring SGM Files (Solaris Only) 5-47

Removing SGM Data from the SGM Server 5-48

Configuring a Backup SGM Server (Solaris Only) 5-50

Configuring an SGM Client Connection Timer 5-51

Telnetting to an ITP 5-52

xCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

C H A P T E R 6 Troubleshooting SGM and the Network 6-1

Verifying Discovery 6-1

Clearing a Locked-Up SGM Display 6-2

Investigating Data Problems 6-2

Viewing the SGM Troubleshooting Log 6-3

Viewing SGM Data on the Web 6-4

Viewing Detailed Troubleshooting Instructions for Events 6-4

Diagnosing a Typical Network Problem 6-4

C H A P T E R 7 Accessing SGM Data from a Web Browser 7-1

Accessing SGM Data from the SGM Server Home Page 7-2

Modifying SGM Web Output (Solaris Only) 7-4

Viewing Network Status and Statistics Information for SGM 7-5

Viewing Information About Nodes 7-5

Viewing the Network Status Node Dashboard 7-6

Viewing ITP Node Status 7-6

Viewing ITP Node Details 7-10

Viewing ITP Node IOS Versions 7-16

Viewing ITP Node Information - CPU Processes 7-17

Viewing ITP Node Information - Syslog Messages 7-19

Viewing ITP Node Information - Trap Host Configuration 7-20

Viewing Information About Signaling Points 7-22

Viewing the Network Status Signaling Point Dashboard 7-22

Viewing ITP Signaling Point Status 7-23

Viewing ITP Signaling Point Details 7-26

Viewing ITP Signaling Point Information - Access Lists 7-29

Viewing ITP Signaling Point Information - GTT MAP Status 7-30

xiCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

Viewing ITP Signaling Point Information - MTP3 Event Log Messages 7-31

Viewing ITP Signaling Point Information - Route Detail 7-32

Viewing Information About Linksets 7-34

Viewing the Network Status Linkset Dashboard 7-34

Viewing ITP Linkset Status 7-35

Viewing ITP Linkset Details 7-38

Viewing ITP Linkset Information - Access Lists 7-49

Viewing Information About Links 7-50

Viewing the Network Status Link Dashboard 7-50

Viewing ITP Link Status 7-51

Viewing Q.752 Measurements for a Link 7-58

Viewing Interface Details for a Link 7-61

Viewing M2PA Peer Details for a Link 7-64

Viewing Information About Application Servers 7-69

Viewing Application Server Status 7-69

Viewing Application Server Details 7-71

Viewing Application Server Process Association Details 7-77

Viewing Information About Signaling Gateway Mated Pairs 7-82

Viewing Signaling Gateway Mated Pair Status 7-82

Viewing Signaling Gateway Mated Pair Details 7-84

Viewing Status Change and SNMP Trap Messages 7-86

Viewing Status Change and SNMP Trap Messages for SGM 7-86

Viewing Status Change Messages for SGM 7-90

Viewing SNMP Trap Messages for SGM 7-93

Viewing All Archived Status Change and SNMP Trap Messages 7-96

Modifying Network Status Message Colors 7-96

Viewing Network Status Metrics 7-97

Viewing Network Statistics Reports for Links and Linksets 7-97

Viewing Accounting Statistics Reports 7-98

xiiCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

Viewing Point Code Inventory Reports 7-98

Viewing Statistics Report Logs 7-99

Viewing SGM System Messages 7-99

Viewing SGM Error Messages 7-100

Viewing SGM Info Messages 7-101

Viewing SGM Action Messages 7-102

Viewing SGM Trace Messages 7-105

Viewing SGM Debug Messages 7-106

Viewing SGM Dump Messages 7-107

Viewing SGM SNMP Messages 7-108

Viewing All Current SGM Messages 7-109

Viewing All Archived SGM Messages 7-110

Viewing the SGM System Console Log 7-110

Viewing All Archived SGM System Console Log Messages 7-111

Viewing the SGM System Command Log 7-111

Viewing the SGM System Event Automation Log 7-112

Viewing the SGM System Security Log 7-113

Viewing the SGM System Web Server Error Log 7-114

Viewing the SGM System Web Access Log 7-115

Viewing System Status Information for SGM 7-115

Viewing Status Information for SGM 7-116

Viewing Version Information for SGM 7-116

Viewing SGM Client Information 7-116

Viewing SGM User Account Information 7-116

Viewing SGM Object Counts 7-118

Viewing the Troubleshooting Log for SGM (Solaris Only) 7-119

Viewing System Data Files for SGM 7-120

Viewing System Information for SGM 7-121

Viewing the SGM Technical Documentation 7-122

xiiiCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

Downloading the SGM Client from the Web 7-123

Downloading the SGM Server’s SSL Certificate from the Web 7-123

Accessing Software Updates and Additional Information 7-124

Displaying the ITP Home Page 7-124

A P P E N D I X A SGM FAQs A-1

What is SGM? A-2

Does SGM require any other NMS applications? A-2

What workstation and network devices do I need to run SGM? A-3

Can I run SGM on my Windows PC? A-3

How do I install the SGM client? A-3

What are the names of the MIBs used by SGM? A-3

Why can’t my remote workstation access SGM on my local workstation? A-5

What is a super user? A-5

Why did SGM not discover all of my ITP nodes? A-5

I moved the server on which I had installed SGM and now I can’t start the SGM client or server. Why? A-6

How often does SGM poll the ITP nodes? A-7

If I select the Clear Event Icon menu option, does that delete the event from the SGM database? A-8

What does the asterisk (*) mean next to an SLC number? A-8

How does “zoom in on an area” work in a topology map? A-8

My server has multiple IP addresses and I'm having problems connecting to the SGM server. How can I correct this problem? A-9

What does this message mean: DataModelMediatorService: Could not find service in RMI registry or the RMI Registry may be down. A-9

What does this message mean: MessageLoggerProxy:setMessageLogger(): Could not resolve. A-10

xivCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

Will the SGM server processes restart automatically after a system reboot? A-10

Some of my SGM windows are showing up very small, with illegible text and unusable text entry fields. How can I correct this? A-11

Sometimes my SGM display seems to lock up. Why? A-11

After a failed uninstall of the Windows SGM client, SGM prompted me to uninstall again, but the procedure does not work. Why? A-12

Why do I see strange character strings when I install SGM? A-13

Why doesn’t Netscape launch when I select a Web page menu option from the SGM Main Menu? A-13

A P P E N D I X B SGM Command Reference B-1

SGM Commands and Descriptions B-2

Output of sgm status Command B-70

Output of sgm export Command B-71

Output of sgm gttcheck Command B-71

Output of sgm gttcheck list Command B-72

Output of sgm gttcheck semantics Command B-72

Output of sgm gttcheck syntax Command B-74

A P P E N D I X C SGM MIB Reference C-1

A P P E N D I X D Configuring SGM to Run with Various Networking Options D-1

VPN Communication D-2

NAT Communication D-4

Firewall Communication D-5

Port-Forwarding Communication D-8

SSL Communication D-11

xvCisco Signaling Gateway Manager User Guide

78-15589-01

Contents

A P P E N D I X E Editing a Non-SGM ITP Route Table E-1

A P P E N D I X F SGM Statistics Export File Formats F-1

SGM Custom Network Statistics Export File Formats F-2

SGM Daily and Hourly Accounting Statistics Export File Format F-2

SGM Link Statistics Daily Export File Format F-3

SGM Link Statistics Hourly Export File Format F-4

SGM Linkset Statistics Daily Export File Format F-5

SGM Linkset Statistics Hourly Export File Format F-6

SGM Point Code Inventory Export File Format F-7

SGM Rolling Network Statistics Export File Formats F-7

GL O S S A R Y

IN D E X

xviCisco Signaling Gateway Manager User Guide

78-15589-01

About This Guide

This preface describes the objectives, audience, organization, and conventions of the Cisco Signaling Gateway Manager User Guide. It refers you to related publications and describes online sources of technical information.

The Cisco Signaling Gateway Manager (SGM) is a network management software product that enables network administrators to discover, manage, and troubleshoot networks that include Cisco ITPs. See the “SGM Overview” section on page 1 for a more detailed description of SGM.

The following information is included in this preface:

• Document Objectives, page xviii

• Document Audience, page xviii

• Document Organization, page xviii

• Document Conventions, page xix

• Related Documentation, page xxi

• Obtaining Documentation, page xxii

• Obtaining Technical Assistance, page xxiv

• Obtaining Additional Publications and Information, page xxvi

xviiCisco Signaling Gateway Manager User Guide

78-15589-01

About This GuideDocument Objectives

Document ObjectivesThis guide describes the architecture, supporting hardware and software, and IP Transfer Point (ITP) management procedures for SGM. Using the information provided in this guide, you can complete the tasks that are necessary to use SGM in your ITP system environment.

Document AudienceThis guide is for network administrators or operators who use the SGM software to manage ITP installations. Network administrators or operators should have the following skills:

• Basic network management skills

• Basic Solaris system administrator skills

• Basic IP, SS7, and ITP knowledge

Document OrganizationThis guide is divided into the following chapters:

• “SGM Overview” provides brief descriptions of Cisco IP Transfer Point (ITP), SGM, and SGM’s client/server architecture, and an overview of how to use SGM to manage your ITP installation.

• “Getting Started with SGM” provides procedures for confirming a successful installation, starting the software, implementing client security, running simultaneous SGM sessions, and exiting SGM.

• “Managing ITP Networks Using SGM” provides procedures for managing your ITP installation using SGM.

• “Configuring SGM Security” provides information about configuring SGM security and limiting access to SGM.

• “Configuring SGM for Your Network” provides figures and detailed descriptions of how SGM is configured on a variety of network configurations, and for operation with other NMS systems.

xviiiCisco Signaling Gateway Manager User Guide

78-15589-01

About This GuideDocument Conventions

• “Troubleshooting SGM and the Network” provides information for troubleshooting basic SGM and network problems, including how to verify Discovery, clearing a locked-up SGM display, and using SGM to diagnose a typical ITP network problem.

• “Accessing SGM Data from a Web Browser” describes how to access SGM data from a Web browser.

• “SGM FAQs” provides a list of frequently asked questions and troubleshooting tips for SGM.

• “SGM Command Reference” describes the IOS Commands used to set up and operate SGM.

• “SGM MIB Reference” describes the MIB variables that are polled by SGM.

• “Configuring SGM to Run with Various Networking Options” describes communication between the SGM client and the SGM server in different networking environments, including Virtual Private Network (VPN), Network Address Translation (NAT), firewall, port-forwarding, and Secure Sockets Layer (SSL).

• “Editing a Non-SGM ITP Route Table” describes how to edit a route table file that was created with a product other than SGM.

• “SGM Statistics Export File Formats” lists the formats for SGM statistics export files.

Document ConventionsThis guide uses basic conventions to represent text and table information.

Command descriptions use the following conventions:

• Commands and keywords are in boldface font.

• Arguments for which you supply values are in italic font.

• Elements in square brackets ([ ]) are optional.

• Alternate but required keywords are grouped in braces ({ }) and separated by a vertical bar (|).

xixCisco Signaling Gateway Manager User Guide

78-15589-01

About This GuideDocument Conventions

Examples use the following conventions:

• Terminal sessions and information that the system displays are printed in screen font.

• Information that you enter is in boldface screen font. Variables for which you enter actual data are printed in italic screen font.

• Nonprinting characters, such as passwords, are shown in angle brackets (< >).

• Information that the system displays is in screen font, with default responses in square brackets ([ ]).

This publication also uses the following conventions:

• Menu items and button names are in boldface font.

• Directories and filenames are in italic font.

• If items such as buttons or menu options are grayed out on application windows, it means that the items are not available either because you do not have the correct permissions or because the item is not applicable at this time.

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in the manual.

Caution Means reader be careful. You are capable of doing something that might result in equipment damage or loss of data.

Tip Means the following are useful tips.

xxCisco Signaling Gateway Manager User Guide

78-15589-01

About This GuideRelated Documentation

Related DocumentationAdditional information can be found in the following publications of the SGM documentation set:

• Cisco Signaling Gateway Manager Installation Guide

• Cisco Signaling Gateway Manager Release Note

• Cisco Signaling Gateway Manager Online Help System

Information about Cisco IOS software-related functions can be found in the following publication:

• Cisco Management Information Base (MIB) User Quick Reference

Information about Cisco IP Transfer Point (ITP) software, including procedures for configuring ITP nodes, signaling points, linksets, and links, can be found in the following publication:

• IP Transfer Point (ITP) feature module for Cisco IOS software release 12.2(4)MB5

Information about the Cisco ITPs can be found in the documentation that shipped with the ITP.

You can find answers to frequently asked questions about SGM in the SGM online help or in the Cisco Signaling Gateway Manager User Guide.

SGM includes a browser-based online help system that provides overviews, related information, procedures, and glossary terms for SGM. You can select underlined text to access additional help topics that provide related information.

When you access online help for SGM the first time there might be a slight pause while your client browser loads the online help.

xxiCisco Signaling Gateway Manager User Guide

78-15589-01

About This GuideObtaining Documentation

Obtaining DocumentationCisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.comYou can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:


International Cisco web sites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROMCisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:

http://www.cisco.com/go/subscription

xxiiCisco Signaling Gateway Manager User Guide

78-15589-01

http://www.cisco.com/univercd/home/home.htm


http://www.cisco.com/public/countries_languages.shtml


About This GuideObtaining Documentation

Ordering DocumentationYou can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

• Registered Cisco.com users can order the Documentation CD-ROM (Customer Order Number DOC-CONDOCCD=) through the online Subscription Store:


• Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation FeedbackYou can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.

You can e-mail your comments to [email protected].

You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:

Cisco SystemsAttn: Customer Document Ordering170 West Tasman DriveSan Jose, CA 95134-9883

We appreciate your comments.

xxiiiCisco Signaling Gateway Manager User Guide

78-15589-01


http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

http://www.cisco.com/en/US/partner/ordering/index.shtml


About This GuideObtaining Technical Assistance

Obtaining Technical AssistanceCisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.

Cisco.comCisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com provides a broad range of features and services to help you with these tasks:

• Streamline business processes and improve productivity

• Resolve technical issues with online support

• Download and test software packages

• Order Cisco learning materials and merchandise

• Register for online skill assessment, training, and certification programs

To obtain customized information and service, you can self-register on Cisco.com at this URL:


Technical Assistance CenterThe Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.

xxivCisco Signaling Gateway Manager User Guide

78-15589-01


About This GuideObtaining Technical Assistance

We categorize Cisco TAC inquiries according to urgency:

• Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

• Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

• Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

• Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

Cisco TAC Website

You can use the Cisco TAC website to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC website, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://tools.cisco.com/RPF/register/register.do

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:

http://www.cisco.com/en/US/support/index.html

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.

xxvCisco Signaling Gateway Manager User Guide

78-15589-01

http://www.cisco.com/tac

http://tools.cisco.com/RPF/register/register.do

http://www.cisco.com/en/US/support/index.html

About This GuideObtaining Additional Publications and Information

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

Obtaining Additional Publications and InformationInformation about Cisco products, technologies, and network solutions is available from various online and printed sources.

• The Cisco Product Catalog describes the networking products offered by Cisco Systems as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

• Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:

http://www.ciscopress.com

• Packet magazine is the Cisco monthly periodical that provides industry professionals with the latest information about the field of networking. You can access Packet magazine at this URL:

http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html

xxviCisco Signaling Gateway Manager User Guide

78-15589-01

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

http://www.ciscopress.com



• iQ Magazine is the Cisco monthly periodical that provides business leaders and decision makers with the latest information about the networking industry. You can access iQ Magazine at this URL:

http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html

• Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in the design, development, and operation of public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

• Training—Cisco offers world-class networking training, with current offerings in network training listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html

xxviiCisco Signaling Gateway Manager User Guide

78-15589-01


http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html

http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html


xxviiiCisco Signaling Gateway Manager User Guide

78-15589-01

Cisco S78-15589-01

C H A P T E R 1
SGM Overview
This chapter describes ITP, SGM, and SGM’s client/server architecture. It includes the following major sections:

• What is ITP?, page 1-1

• What is SGM?, page 1-2

• What is Client/Server Architecture?, page 1-5

What is ITP?Any discussion of SGM requires some knowledge of the hardware and software used by ITP.

ITP is part of Cisco’s hardware and software SS7-over-IP (SS7oIP) solution. ITP provides a reliable, cost-effective medium for migrating Signaling System 7 (SS7), the telecommunications network signaling technology, to the mobile wireless industry IP environment. ITP off-loads SS7 traffic onto the IP network, replacing the mobile service provider’s signaling network with a redundant IP cloud.

In ITP, a node is a Cisco ITP or a legacy SS7 device (SSP, SCP, or STP).

A Cisco ITP node can have multiple signaling points. Signaling points are identified with unique addresses called point codes. Point codes are carried in signaling messages exchanged between signaling points to identify the source and destination of each message.

1-1ignaling Gateway Manager User Guide

Chapter 1 SGM OverviewWhat is SGM?

Signaling points and legacy SS7 devices are connected by links, and multiple links are grouped in a linkset. Each link is assigned to a single linkset, but each linkset can have multiple links. Links within the same linkset must be parallel between the same signaling points or nodes.

In SGM, a linkset is a representation of two linksets associated with two signaling points or nodes, one for each side of a logical connection.

Collectively, nodes, signaling points, linksets, and links are known as managed objects.

For more information about ITP, including procedures for configuring ITP nodes, signaling points, linksets, and links, see the IP Transfer Point (ITP) feature module for Cisco IOS software release 12.2(4)MB4 or later.

What is SGM?SGM is a network management software product that enables network administrators to discover, manage, and troubleshoot networks that include Cisco ITPs. SGM provides the following key features:

• Uses client/server architecture. See the “What is Client/Server Architecture?” section on page 1-5 for more details.

• Runs on standard IP-connected networks, and transparently over Virtual Private Networks (VPNs). Also runs in Network Address Translation (NAT), firewall, port-forwarding, and Secure Sockets Layer (SSL) networking environments with minimal additional configuration. SGM can run in each of these environments individually or in any combination.

• Supports concurrent network indicators and variants, multiple secondary point codes, SS7 instance translation, and virtual linksets.

• Provides a Java-based, easy-to-use graphical user interface (GUI) on the client with extensive Web-based online help.

Also provides a powerful command-line interface (CLI) on the server.

Also provides an extensive HTML-based Web interface with:

– Access to network and server status information

– Access to link and linksets statistics summary reports

– Access to accounting statistics reports

1-2Cisco Signaling Gateway Manager User Guide

78-15589-01


– Access to point code inventory reports

– Ability to export reports for use in spreadsheet and graphics programs

– Installation, message, command, report, and security logs

– Client downloads

– Product documentation

– Other information about SGM. Most of the primary GUI client features are also available on the Web interface, with the exception of the topology map, real-time data charts and event management, and route table and GTT file configuration.

• Provides extensive security services, including:

– Management of SSL certificates via the GUI

– Multi-level password-protected access for multiple users

– Passwords that can be changed by users via the GUI

– Audit trails of all user actions and all access via the Web interface

– Security logs

– Optional access via VPN, Secure Shell (SSH), and SSL

• Automatically discovers the ITP network from any ITP device, with links to non-ITP devices, and creates both topological (graphical) and tabular (text) views of the network.

– The topology view displays nodes, signaling points, and linksets as color-coded glyphs on a topology map, with right-click menus and layout, zoom, find, grid, and save-as-JPEG functions.

– The tabular view displays detailed data in columns that can be resized, sorted, or hidden, depending on your preferences.

• Enables you to customize just about every aspect of the GUI, topology, and tabular views to meet your specific needs. Customized views can be saved for future use and reference, and shared with other users of the network.

• SGM automatically saves your preferences, such as the size of specific windows or the order of columns in a window, and automatically applies those preferences whenever you launch the SGM client.

• Polls the ITPs on demand, and at user-defined intervals, and reports the real-time status of all nodes, signaling points, linksets, links, and events, including the reason for any changes in status.


78-15589-01


• Enables you to annotate nodes, signaling points, linksets, and events, attaching important information such as detailed descriptions, locations, service history, what triggered the event, how often it has occurred, and so on.

• Enables you to customize the displayed category, severity, color, and message associated with events. You can even have SGM play unique sounds for different types of events.

• Enables you to automate events, calling UNIX scripts to drive automatic paging, e-mail, and so on, on the SGM server.

• Receives SNMP traps natively or via HP OpenView, to drive alarms and accurate and up-to-date status displays.

• Provides Web-based alarm viewing, sorting, filtering, archiving, metric calculations, and reason codes.

• Provides M3UA/SUA status displays.

• Supports high server uptime with multiple server support, primary and secondary configurations, dynamic routing, automatic process management, and many debugging and customization tools, including real-time drill-down diagnostic applications.

• Enables you to configure destination point code (DPC) route tables and Global Title Translation (GTT) tables. Supports GTT file format versions 2.0, 3.0, 3.1, and 4.0.

• Can integrate with the entire suite of CiscoWorks2000 products, including:

– Resource Manager Essentials, which provides network management for Cisco ITPs.

– Internetwork Performance Monitor, which enables you to measure and monitor key performance metrics in a Cisco IOS-based IP network.

– Access Control List Manager, which manages the access lists of Cisco devices.

– CiscoView Element Manager, which provides dynamic status, monitoring, and configuration information for a broad range of Cisco internetworking products.

You can launch the CiscoView Element Manager and the CiscoWorks2000 Device Center directly from the topology map, for quick drill-down network analysis.

• Supports printing of windows to a file or to a PostScript printer.


78-15589-01

Chapter 1 SGM OverviewWhat is Client/Server Architecture?

What is Client/Server Architecture?SGM provides central services and database functions on an SGM server, which communicates through a messaging interface with multiple SGM clients.

SGM recommends a maximum of 20 clients per SGM server. If you connect more than 20 clients to a single server, the server requires additional memory and a more powerful CPU.

SGM consists of server and client software components that can be installed on the same workstation or on different workstations. The SGM server is currently available only on Solaris, but the SGM client is available on Solaris, on Windows 2000 Professional, and on Windows XP Professional (Figure 1-1).

Figure 1-1 SGM Client/Server Architecture

Network

74

78

0

Solaris System(SGM server, client, and database)

SGM client onSolaris workstation

SGM client onWindows 2000Professionalworkstation

SGM client onWindows XPProfessionalworkstation


78-15589-01

Chapter 1 SGM OverviewWhat is Client/Server Architecture?

The client/server architecture is cross-platform compatible, which allows you to run the client and server software in mixed operating system environments. For example, you can run the SGM server on a Solaris workstation and access it from an SGM client running on a Windows 2000 Professional or Windows XP Professional workstation.

The SGM server software consists of a group of functional services that manage the data among the network, client workstations, and the centralized database. The SGM server manages the exchange of data between the SGM database and the network devices. The SGM process manager launches and manages all of the SGM server processes, providing a robust and reliable launching platform for SGM.

The SGM client software communicates with the SGM server. You can install the SGM client software on the same workstation as the SGM server software, or on a different workstation on the same network as the SGM server. After you install the SGM server, you can download the SGM client software from the Web, for easy distribution to users and easier access to important information.


78-15589-01

Cisco S78-15589-01

C H A P T E R 2
Getting Started with SGM
This chapter provides information about starting and stopping SGM, and provides an overview of how to use SGM to manage your Cisco IP Transfer Point (ITP) installation. It includes the following major sections:

• Starting SGM, page 2-2

• Running Simultaneous SGM Sessions, page 2-7

• Exiting the SGM Client, page 2-7

For detailed information about SGM’s supported platforms, and hardware and software requirements, see the Cisco Signaling Gateway Manager Installation Guide.

Note The default directory for installing SGM is /opt. In commands that call for the default directory, if you installed SGM in a different directory, you must specify that directory instead of /opt.


Chapter 2 Getting Started with SGMStarting SGM

Starting SGMBecause the SGM application is comprised of a server component and a client component, you must start both components to run the application.

Before starting an SGM server, verify the following prerequisite conditions:

• The ITP uses a supported IOS image with the ITP feature

• SNMP is enabled on the ITP

• (Optional) ITP traps are enabled on the ITP

• (Optional) A trap host is defined on the ITP

• The SGM server has IP connectivity to the ITPs

To start just the SGM server on a Solaris system, enter the following commands:

$ cd /opt/CSCOsgm/bin

$ ./sgm start

Note To issue the sgm start command, you must be logged in as the root user or as a super user, or your login must have administrator privileges. See the “Becoming the Root User (Solaris Only)” section on page 3-2 and the “Specifying a Super User (Solaris Only)” section on page 4-22 for more information.

To start just the SGM client on a Solaris system on which the SGM server is installed, make sure the SGM server is running, then enter the following commands:


$ ./sgm client

To start just the SGM client on a Solaris system other than the one on which the SGM server is installed, make sure the SGM server is running, then enter the following commands:

$ cd /opt/CSCOsgmClient/bin

$ ./sgm client


78-15589-01


To start the SGM client on a Solaris system on which the SGM server is installed, and connect to an SGM server other than the default server, make sure the SGM server is running, then enter the following commands:


$ ./sgm client server_name_or_ip_address

To start the SGM client on a Solaris system other than the one on which the SGM server is installed, and connect to an SGM server other than the default server, enter the following commands:

$ cd /opt/CSCOsgmClient/bin

$ ./sgm client server_name_or_ip_address

where server_name_or_ip_address is the name or IP address of the Solaris system on which the SGM server is running.

SGM presents its version, release, and patch level with the format x.y.z, where:

• x is the version number

• y is the release number

• z is the patch level.

When you start an SGM client, the version and release of the client must match that of the SGM server, and the patch level must be greater than or equal to that of the server. For example, the following SGM client-server connections are allowed:

Table 2-1 Allowed SGM Client-Server Connections

Client Level Server Level

3.0.0 3.0.0

3.0.1 3.0.0

3.0.9 3.0.3


78-15589-01


The following SGM client-server connections are not allowed:

If there is a client-server mismatch, SGM displays a warning message. If you have a Web browser installed, SGM opens a Web page enabling you to download an allowed, matching client. See the “Downloading the SGM Client from the Web” section on page 7-123 for more information about downloading the SGM client.

When you start SGM for the first time, SGM displays the Discovery Dialog (Figure 2-1) and the SGM Main Window (Figure 2-2).

Figure 2-1 Discovery Dialog

Table 2-2 Disallowed SGM Client-Server Connections

Client Level Server Level

2.1.3 2.1.9

2.2.0 2.1.0

3.0.0 2.2.0


78-15589-01


Figure 2-2 SGM Main Window

The SGM Main Window is the primary SGM window. It is the first window to appear when you launch the SGM client. It displays basic information about the events, nodes, signaling points, linksets, and links that SGM discovers.

When you start SGM for the first time, if you did not configure the SGM server to automatically discover your network the first time the server starts after installation, the SGM database contains no information, and the SGM Main Window is blank. The database is populated, and reflected in the SGM Main Window, when you run Discovery for the first time; SGM displays the Discovery Dialog to make it easier for you to do so. In fact, any time you start the SGM client and the SGM database is empty, SGM automatically opens the Discovery Dialog so you can run Discovery and populate the database. For more information about Discovery, see the “Discovering the Network” section on page 3-6.


78-15589-01


The events, nodes, signaling points, linksets, and links that SGM discovers are displayed in the left and right panes of the SGM Main Window.

• To see all events discovered by SGM, click Events in the left pane. SGM displays the Event Window in the right pane.

• To see all nodes discovered by SGM, click Nodes in the left pane. SGM displays the Node Window in the right pane.

To display all nodes discovered by SGM in the left pane, select the turner beside Nodes. Then, you can select one of the nodes to display the Node Details Window for that node in the right pane.

To display all signaling points discovered by SGM in the left pane, select the turner beside Signaling Points. Then, you can select one of the signaling points to display the Signaling Point Details Window for that signaling point in the right pane.

To display all linkset pairs discovered by SGM in the left pane, select the turner beside Linksets. Then, you can select one of the linksets to display the Linkset Details Window for that linkset in the right pane.

To display all link pairs discovered by SGM in the left pane, select the turner beside a linkset. Then, you can select one of the link pairs to display the Link Details Window for that link pair in the right pane.

• To see all signaling points discovered by SGM, click Signaling Points in the left pane. SGM displays the Signaling Point Window in the right pane. You can also display all of the signaling points, linksets, and links by selecting the appropriate turners, as described for nodes above.

• To see all linkset pairs discovered by SGM, click Linksets in the left pane. SGM displays the Linkset Window in the right pane. You can also display all of the linksets and links by selecting the appropriate turners, as described for nodes above.

• To see all link pairs discovered by SGM, click Links in the left pane. SGM displays the Link Window in the right pane. You can also display all of the links by selecting the turner, as described for nodes above.


78-15589-01

Chapter 2 Getting Started with SGMRunning Simultaneous SGM Sessions

Running Simultaneous SGM SessionsSGM uses a client/server architecture that allows you to run multiple sessions of the SGM client simultaneously. Central services and database functions are provided on an SGM server that communicates with multiple SGM clients. You can install the SGM client software on the same system as the SGM server, or on a different system on the same network as the SGM server.

Note Running more than one SGM client on the same workstation can degrade the workstation’s performance.

SGM recommends a maximum of 20 clients per SGM server. If you connect more than 20 clients to a single server, the server requires additional memory and a more powerful CPU.

Exiting the SGM ClientWhen you are finished monitoring network performance statistics, you can exit the SGM client using the following procedure:

Step 1 From the SGM Main Menu, select File > Exit. The Exit SGM confirmation window is displayed.

Step 2 Click Yes to close the SGM client application.


78-15589-01

Chapter 2 Getting Started with SGMExiting the SGM Client


78-15589-01

Cisco S78-15589-01

C H A P T E R 3
Managing ITP Networks Using SGM
This chapter provides details on using SGM to discover and manage your ITP networks. It includes the following sections:

• Becoming the Root User (Solaris Only), page 3-2

• Configuring SNMP, page 3-2

• Discovering the Network, page 3-6

• Configuring Seed Files, page 3-20

• Working with Views, page 3-26

• Working with Linksets, page 3-37

• Working with Nodes, page 3-91

• Working with Signaling Points, page 3-136

• Working with Links, page 3-170

• Working with Events, page 3-235

• Viewing the Topology of the Network, page 3-259

• Viewing Server Status Information, page 3-274

• Finding Information in a Window, page 3-278

• Resizing, Sorting, and Hiding Table Columns, page 3-279

• Viewing Online Help, page 3-280

• Editing an ITP Route Table File, page 3-281

• Editing a Global Title Translation Table, page 3-290

• Working with SGM Statistics Reports, page 3-334


Chapter 3 Managing ITP Networks Using SGMBecoming the Root User (Solaris Only)

• Printing SGM Windows, page 3-398

• Connecting to a New Server, page 3-399

• Integrating SGM with Other Products, page 3-401

• Using the Windows Start Menu, page 3-403

Becoming the Root User (Solaris Only)Some SGM procedures require you to be logged in as the root user.

Caution As the root user, you can adversely affect your operating environment if you are unaware of the effects of the commands you use. If you are a relatively inexperienced UNIX user, limit your activities as the root user to the tasks described in this manual.

If you are not logged in, log in as the root user:

> login: root

> Password: root-password

If you are already logged in, but not as the root user, use the su command to change your login to root:

# su

# Password: root-password

Configuring SNMPIf SGM User-Based Access is disabled, or if it is enabled and you are a Network Administrator or System Administrator, SGM enables you to view and change some SNMP settings. (For more information about user authorization levels in SGM, see the “Configuring SGM User Authentication Levels (Solaris Only)” section on page 4-6.)


78-15589-01

Chapter 3 Managing ITP Networks Using SGMConfiguring SNMP

Note If you want to change SNMP settings, do so before running Discovery.

To change SNMP settings in SGM:

Step 1 Start the SGM client, as described in the “Starting SGM” section on page 2-2.

Step 2 Select Edit > SNMP Configuration from the SGM Main Menu. (If you have implemented SGM User-Based Access, this option is available to users with authentication level Network Administrator [Level 4] and higher.) SGM displays the SNMP Configuration Dialog (Figure 3-1).

Figure 3-1 SNMP Configuration Dialog

The SNMP settings table displays SNMP information for nodes in SGM.

Step 3 (Optional) To delete a node, select it and click Delete.


78-15589-01


Step 4 (Optional) To change the IP address or DNS name of a node, select the node and enter the new address or name in the IP Address Range or Hostname field.

• IP addresses use the format x.x.x.x, where each x has one of the following values:

– An integer in the range 0 through 255.

– A range of integers separated by a dash (-), such as 10-60.

– An asterisk (*), which is equivalent to specifying 0-255.

• Unlike IP addresses, you cannot specify a range of node names or use wildcards in node names. Each node name corresponds to a single node in the network.

The default value for this field is the IP address *.*.*.*, which SGM uses for all nodes not covered by other IP address ranges or names.

Click Update to apply the new IP address to the selected node.

Step 5 (Optional) Nodes use SNMP community names for read access to the information maintained by the SNMP agent on the ITP. To change the SNMP community name for a node, select the node and enter the new name in the Read Community field. This name must match the name used by the node. The default name is public.

Click Update to apply the new SNMP community name to the selected node.

For information about exporting SNMP community names from CiscoWorks2000 Resource Manager Essentials (RME), see the “Importing SNMP Community Names from CiscoWorks2000 (Solaris Only)” section on page 5-2.

Step 6 (Optional) If you determine that SGM waits too long for a response from a node, or does not wait long enough, you can change the timeout value. To change the time, in seconds, that SGM waits for a response from a node, select the node and enter the new timeout value in the Timeout (secs) field. The valid range is 1 to 60 seconds. The default value is 1 second.

Click Update to apply the new timeout to the selected node.

Step 7 (Optional) If you determine that SGM retries a node too many times, or not enough times, you can change the number of retries. To change the number of times SGM attempts to connect to a node, select the node and enter the new number in the Retries field. The valid range is 0 to 99. The default value is 2 retries.

Click Update to apply the new retries value to the selected node.


78-15589-01


Step 8 (Optional) If you determine that SGM polls a node too often, or not often enough, you can change the poll interval. To change the time, in minutes, between polls for a node, select the node and enter the new interval in the Poll Interval (mins) field. The valid range is 5 to 1440. The default value is 15 minutes.

Click Update to apply the new poll interval to the selected node.

Step 9 (Optional) To add a new node or range of nodes, enter the SNMP information in the appropriate fields and click Add. The new SNMP settings are added to the SGM database.

When you are satisfied with all of your changes to the SNMP settings, select the File > Save menu option. SGM saves the changes, updates the SNMP information on the SGM server in real time, and closes the SNMP Configuration Dialog.

Note If another user modifies and saves the SNMP configuration before you save your changes, SGM asks if you want to overwrite that user’s changes. If you choose to do so, the other user’s changes are overwritten and lost. If you choose not to do so, your changes are lost.

For more information about SNMP, refer to “Configuring SNMP Support” in the Cisco IOS Release 12.2 Configuration Fundamentals Configuration Guide, Part 3, Cisco IOS System Management.

SGM also provides the following SNMP-related commands:

• To set a new default SNMP read community name, use the sgm snmpcomm command.

• To change the file used for SNMP parameters, such as community names, timeouts, and retries, use the sgm snmpconf command.

• To query a host using SNMP GetRequests, use the sgm snmpget command.

• To query a host using SNMP GetNextRequests, use the sgm snmpnext command.

• To query a host, using SNMP GetNextRequests to “walk” through the MIB, use the sgm snmpwalk command.

For more information on the use of these commands, see the “SGM Commands and Descriptions” section on page B-2.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMDiscovering the Network

Discovering the NetworkSGM uses a Discovery process to populate the SGM database, discovering the nodes, signaling points, linksets, and links in your network.

You can run Discovery if SGM User-Based Access is disabled, or if it is enabled and you are a Network Administrator or System Administrator. (For more information about user authorization levels in SGM, see the “Configuring SGM User Authentication Levels (Solaris Only)” section on page 4-6.)

Related Topics:

• Backing Up or Restoring SGM Files (Solaris Only), page 5-47

• Configuring Seed Files, page 3-20

• Investigating Data Problems, page 6-2

• Verifying Discovery, page 6-1


78-15589-01


To discover the network in SGM:

Step 1 Start the SGM client, as described in the “Starting SGM” section on page 2-2.

Step 2 Select Edit > Network Discovery from the SGM Main Menu. SGM displays the Discovery Dialog (Figure 3-2).

Figure 3-2 Discovery Dialog

If you start the SGM client and the SGM database is empty (including the very first time you start the SGM client), SGM automatically opens the Discovery Dialog so you can run Discovery and populate the database.

Step 3 Select the Seed Settings tab, if it is not already selected. SGM displays the Seed Settings panel, which enables you to create, save, load, and delete SGM seed files. Seed files are lists of seed nodes, which SGM uses to discover the nodes, signaling points, linksets, and links in your network.


78-15589-01


Step 4 Load one or more seed nodes, using one of the following procedures:

• Enter the name or IP address of a seed node in the IP Address or DNS Hostname field, and click Add Node.

SGM displays details of the SNMP settings for the seed nodes in the right pane of the window.

Continue adding seed nodes until you are certain that SGM will be able to discover the entire network.

• If you have already created and saved a seed file, select File > Load Seeds from the Discovery Dialog menu. SGM displays the Load File Dialog: Seed File List dialog (Figure 3-3).

Figure 3-3 Load File Dialog: Seed File List Dialog

The Load File Dialog: Seed File List dialog contains the following fields:

– Type—Icon indicating whether the item in the table is a file or a folder.

– Name—Name of the seed file or folder.

– Last Modified—Date and time the seed file or folder was last modified.


78-15589-01


– Size (bytes)—Size of the seed file or folder, in bytes.

– Make this my preferred start option—Specifies whether the selected seed file is to be loaded automatically whenever this SGM client is started or the Discovery Dialog is opened. By default, this checkbox is cleared for all seed files. That is, no seed file is loaded automatically when the SGM client is started or the Discovery Dialog is opened.

– Number of Files—Total number of seed files and folders (displayed in bottom left corner).

To load a seed file, select the seed file in the list and click OK.

SGM closes the Load File Dialog: Seed File List dialog, loads the seed file, and returns to the Discovery Dialog. SGM lists all of the seed nodes in the seed file in the left pane of the window, and displays details of the SNMP settings for the seed nodes in the right pane.

To close the Load File Dialog: Seed File List dialog without loading a seed file, click Cancel.

Step 5 Select the Discovery tab, or click Next. SGM displays the Discovery panel (Figure 3-4), which enables you to discover the nodes, signaling points, linksets, and links in your network. (If you enter a seed node IP address or name in the IP Address or DNS Hostname field, then click Next, SGM automatically adds the seed node before displaying the Discovery panel.)


78-15589-01


Figure 3-4 Discovery Panel

Step 6 (Optional) Specify the extent of the network discovery.

• To discover the entire network, select the Entire Network checkbox. This is called recursive discovery, and it is the default setting. Select this checkbox when you run Discovery for the very first time.

With this checkbox selected, SGM discovers all seed nodes and attempts to manage them; then attempts to discover and manage all ITP nodes that are adjacent to those seed nodes (unless the nodes are connected by serial links only); then attempts to discover and manage all ITP nodes that are adjacent to those nodes; and so on, until SGM has discovered the entire network.

• To rediscover only seed nodes, clear the Entire Network checkbox. This is called nonrecursive discovery.

With this checkbox cleared, SGM discovers all seed nodes and attempts to manage them, then labels all nodes that are adjacent to those seed nodes Unmanaged.


78-15589-01


If you run Discovery with Entire Network cleared, then you run Discovery with Entire Network selected, any Unmanaged nodes in the first Discovery are not rediscovered by the second Discovery.

To recover from this situation and generate a new, complete, and reliable SGM database, you must perform one of the following procedures:

a. Run Discovery again, with both Entire Network and Delete Existing Data selected.

b. Change the Unmanaged nodes to managed status. See the “Unmanaging and Managing a Node” section on page 3-133 for more information.

c. Poll the nodes that were Unmanaged in the first Discovery. See the “Polling a Node” section on page 3-134 for more information.

Step 7 (Optional) Specify whether SGM is to keep or delete the existing database when discovering the network:

• To keep all existing network data in the SGM database before rediscovering the network, clear the Delete Existing Data checkbox. This is the default setting. Clear this checkbox when you run Discovery for the very first time.

• To delete all existing network data from the SGM database before rediscovering the network, select the Delete Existing Data checkbox. Choose this option if you know that network elements have been deleted from your network since the last Discovery.

Note If you discover the network with Delete Existing Data selected, SGM stops any real-time polls that are running and issues appropriate messages.


78-15589-01


Step 8 Click Discover Network to begin Discovery.

When Discovery begins:

• The Discover Network button is grayed-out.

• The “Discovery In Progress” message is displayed at the bottom of the Discovery Dialog.

• The “Discovery In Progress” message is displayed in the title bar of all SGM client windows.

Discovery progresses in bursts. You might see a number of updates, followed by a pause, followed by more updates. The information displayed in SGM windows is not fully updated until Discovery is complete.

By default, Discovery times out after 600 seconds (10 minutes). To change the Discovery timeout, change the value of the DISCOVERY_TIMELIMIT entry in the Server.properties file:

• If you installed SGM in the default directory, /opt, then the location of the Server.properties file is /opt/CSCOsgm/properties/Server.properties.

• If you installed SGM in a different directory, then the Server.properties file is located in that directory.

Because SGM is an asynchronous system, with the SGM server contacting clients one at a time, and because clients might run at different speeds, the information displayed by SGM clients during Discovery might not always be synchronized.

Step 9 (Optional) To stop the Discovery process at any time, click Stop Discovery. For example, if you click Discover Network, then you realize that you loaded a seed node that you did not intend to load, you can click Stop Discovery to stop the Discovery process.

Note If you stop the Discovery process, the information in the SGM database is incomplete and unreliable. To generate a new, complete, and reliable SGM database, you must run Discovery again, with Delete Existing Data selected.

Step 10 When the “Discovery In Progress” message disappears, Discovery is complete. The Discovered Nodes section of the Discovery panel (Figure 3-5) lists all nodes that were discovered by SGM. By default, this table is sorted by Status.


78-15589-01


Figure 3-5 Discovery Panel with Discovered Nodes

By default, SGM displays all of the columns in the Discovered Nodes section except Internal ID, ITP Uptime, Reboot Reason, and Last Status Change. To display these columns, or to hide other columns, see the procedures in the “Modifying Node Table Column Settings” section on page 5-16.

To see mouse over help popup for each column in the table, place the cursor over a column header.

If a cell is too small to show all of its data, place the cursor over the cell to see the full data in a mouse over help popup.

You can resize each column, or sort the table based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.


78-15589-01


The Discovered Nodes section displays the following information for each discovered node:

• Internal ID—Internal ID of the event. The internal ID is a unique ID for every event, link, linkset, signaling point, and node, assigned by SGM for its own internal use. It can also be useful when the TAC is debugging problems.

• Name—Name or IP address of the discovered node.

• Primary SNMP Address—IP address of the node, used by SNMP to poll the node. (There might be other IP addresses on the node that are not the primary SNMP address.)

• CLLI Code—COMMON LANGUAGE Location Identification Code for the node. A CLLI code is a standardized 11-character identifier that uniquely identifies the geographic location of the node. If the node has no CLLI code configured, this field is blank.

• Device Type—Device type of the node. Possible values are:

– Cisco2650—Cisco 2650 series router

– Cisco2650XM—Cisco 2650XM series router




– Cisco7204VXR—Cisco 7204VXR series router




– Cisco7507mx—Cisco 7507mx series router

– Cisco7507z—Cisco 7507z series router




– IPDevice—IP device, other than those listed above. You can assign this icon to an unknown node if you know that it is an IP device.

– Unknown—SGM is unable to determine the device type.


78-15589-01


• ITP MIB Level—MIB conformance level used by the ITP, such as ITP MB5.

• ITP Uptime—Time the ITP has been up, in weeks, days, hours, minutes, and seconds.

• Reboot Reason—Reason for the last reboot of the ITP.

• Notes—Indicates whether there is a note associated with the node.

• Events—Indicates whether there is a recent event associated with the node.

During Discovery, SGM might flag most nodes with an event icon. If the event icons are too distracting, select Edit > Clear All Events from the SGM Main Menu to remove them.

• Last Status Change—Date and time that the status of the node last changed.

• Status—Current status of the node. Possible values are:

– Active (green ball)—The node is currently fully functional.

– Discovering (gray ball)—The node is being discovered, and SNMP queries have been sent to the device.

– Polling (gray ball)—The node is being polled.

– Unknown (red ball)—The node failed to respond to an SNMP request. SGM sets all associated signaling points, linksets, and links to Unknown.

– Unmanaged (gray ball)—One of the following situations exists:

– The node is known indirectly by SGM. In other words, SGM knows the device exists but there is no known SNMP stack on the device for SGM to query.

– An SGM user has set the node to Unmanaged status, to prevent SGM from polling the node.

If the associated signaling points are referenced via linksets to other signaling points, SGM automatically sets all associated signaling points to Unmanaged, and deletes all associated linksets and links, as well as all linksets and links that reference the node as an adjacent node.

If the associated signaling points are not referenced to other signaling points, SGM automatically deletes the signaling points, all associated linksets and links, and all linksets and links that reference the node as an adjacent node.


78-15589-01


– Waiting (gray ball)—The node is in the Discovery queue but is not currently being discovered.

– Warning (yellow ball)—The node is active, but one or more associated signaling points, linksets, or links is in Failed, Unavailable, Unknown, or Warning status and is not Ignored.

• Status Reason—Reason for the current status of the node. Possible values are:

– None

– SGM Restart

– Unsupported Configuration

– Unconfigured

– SNMP Timeout

– Device is unreachable, possibly wrong community string

– Not ITP Device

– Not Configured for ITP

– MIB Data Error

– SNMP Exception

– SignalingPoint Inactive

– Linkset Inactive

– Link Congested

– Link Send Utilization Threshold Exceeded

– Link Receive Utilization Threshold Exceeded

– Link Local Interface Inactive

– Link Remote Interface Inactive

– Link Inactive

If the cell is too small to show all of the status reason, place the cursor over the cell to see the full status reason in a mouse over help popup.

The status reasons are listed in order of decreasing magnitude. If two or more reasons apply, the reason of greatest magnitude is displayed.


78-15589-01


If the status reason is Unsupported Configuration, correct the configuration and enter the sgm cleandiscover command to delete all current network data and begin a clean discovery of the ITP network. If the status reason is still Unsupported Configuration, enter the sgm clean command to restore the SGM server to a “clean” state, such as would exist after a new installation of SGM. For more information on the use of these commands, see the “SGM Commands and Descriptions” section on page B-2.

The “Viewing Detailed Information for a Link” section on page 3-175 displays additional information about the causes of link failures.

The “Viewing Detailed Information for a Linkset” section on page 3-42 displays additional information about the causes of linkset failures.

All discovered nodes are placed in a DEFAULT configuration view, which is stored on the SGM server and shared by all SGM clients. Initially, all clients use the DEFAULT view. Clients can then create their own views, which are subsets of the DEFAULT view, to meet their individual needs. However, the DEFAULT view stored on the SGM server cannot be modified by the clients. It is always available, for users who need to view the entire network.

All other SGM windows (Node, Signaling Point, Linkset, Topology, and so on) are also populated with the newly discovered network data.

Step 11 (Optional) To delete a node or nodes from the Discovery database, select the nodes and click Delete Node. SGM deletes the nodes without asking for confirmation.

Step 12 (Optional) Examine the Discovered Nodes table to verify that SGM discovered all of the nodes in the network. If you suspect that SGM did not discover all of the nodes, see the “Verifying Discovery” section on page 6-1 for troubleshooting information. You might need to add more seed nodes and run Discovery again.

Step 13 When you are satisfied that SGM discovered all of the nodes in the network, save the list of seed nodes in a seed file, using one of the following procedures:

• To save the changes you have made to the seed file without changing the name of the file, select File > Save from the Discovery Dialog menu.

• To save the changes you have made to the seed file with a new name, select File > Save As from the Discovery Dialog menu. SGM displays the Save File Dialog: Seed File List dialog (Figure 3-6).


78-15589-01


Figure 3-6 Save File Dialog: Seed File List Dialog

The Save File Dialog: Seed File List dialog contains the following fields:

• Type—Icon indicating whether the item in the table is a file or a folder.

• Name—Name of the seed file or folder.

• Last Modified—Date and time the seed file or folder was last modified.

• Size (bytes)—Size of the seed file or folder, in bytes.

• Filename—Name by which you want to save the seed file.

If you create a new seed file name, you can use any letters, numbers, or characters in the name that are allowed by your operating system. However, if you include any spaces in the new name, SGM converts those spaces to dashes. For example, SGM saves file “a b c” as “a-b-c”.


78-15589-01


• Make this my preferred start option—Specifies whether the selected seed file is to be loaded automatically whenever this SGM client is started or the Discovery Dialog is opened. By default, this checkbox is cleared for all seed files. That is, no seed file is loaded automatically when the SGM client is started or the Discovery Dialog is opened.

• Number of Files—Total number of seed files and folders (displayed in bottom left corner).

To save the seed file with a new name, use one of the following procedures:

• To save the file with a completely new name, enter the new name and click OK.

• To save the file with an existing name, overwriting an old seed file, select the name in the list and click OK.

SGM saves the seed file with the new name, closes the Save File Dialog: Seed File List dialog, and returns to the Discovery Dialog.

Note If another user modifies and saves the seed file before you save your changes, SGM asks if you want to overwrite that user’s changes. If you choose to do so, the other user’s changes are overwritten and lost. If you choose not to do so, your changes are lost, unless you save the seed file to a different filename.

SGM stores the seed file in the seed file directory on the SGM server:

• If you installed SGM in the default directory, /opt, then the SGM seed file directory is /opt/CSCOsgm/seeds.

• If you installed SGM in a different directory, then the SGM seed file directory is located in that directory.

To delete a seed file from the seed file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.

To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Save File Dialog: Seed File List dialog.

To close the Save File Dialog: Seed File List dialog without saving the seed file or saving any changes to the seed file list, click Cancel.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMConfiguring Seed Files

You can run Discovery multiple times to attempt to discover additional nodes based on the IP address defined in the Stream Control Transmission Protocol (SCTP) linksets. If you are using a separate management VLAN to manage your nodes, but private or unreachable IP addresses for your SCTP connectivity, clear the Entire Network checkbox in the Discovery Dialog. Otherwise, Discovery attempts to reach those nodes continuously. Instead, enter all nodes to be discovered directly into the seed list and do a nonrecursive Discovery.

Configuring Seed FilesSGM enables you to create, save, load, and delete SGM seed files.

This section includes the following information:

• Creating a New Seed File, page 3-20

• Modifying an Existing Seed File, page 3-22

• Creating and Modifying Seed Files Using a Text Editor, page 3-24

Related Topics:


Creating a New Seed FileTo create a new seed file in SGM:


Step 2 Select the Seed Settings tab, if it is not already selected. SGM displays the Seed Settings panel.

Step 3 Enter the name or IP address of a seed node in the IP Address or DNS Hostname field, and click Add Node. SGM displays details of the SNMP settings for the seed node in the right pane of the window.

Continue to add as many seed nodes as necessary.


78-15589-01


Step 4 When you are ready to save the list of seed nodes in a new seed file, select File > Save As from the Discovery Dialog menu. SGM displays the Save File Dialog: Seed File List dialog (Figure 3-6).






• Filename—Name by which you want to save the seed file. You can use any letters, numbers, or characters in the name that are allowed by your operating system. However, if you include any spaces in the new name, SGM converts those spaces to dashes. For example, SGM saves file “a b c” as “a-b-c”.



Enter the new name and click OK. SGM saves the seed file with the new name, closes the Save File Dialog: Seed File List dialog, and returns to the Discovery Dialog.

SGM stores the new seed file in the seed file directory on the SGM server:




78-15589-01


Modifying an Existing Seed FileTo modify an existing seed file in SGM:


Step 2 Select the Seed Settings tab, if it is not already selected. SGM displays the Seed Settings panel.

Step 3 Select File > Load Seeds from the Discovery Dialog menu. SGM displays the Load File Dialog: Seed File List dialog (Figure 3-3).

The Load File Dialog: Seed File List dialog contains the following fields:







To load a seed file, select the seed file in the list and click OK.

SGM closes the Load File Dialog: Seed File List dialog, loads the seed file, and returns to the Discovery Dialog. SGM lists all of the seed nodes in the seed file in the left pane of the window, and displays details of the SNMP settings for the seed nodes in the right pane.

To close the Load File Dialog: Seed File List dialog without loading a seed file, click Cancel.

Step 4 (Optional) To add another seed node to the seed file, enter the name or IP address of the seed node in the IP Address or DNS Hostname field, and click Add Node.

Step 5 (Optional) To delete a seed node from the seed file, select the seed node and click Delete Node.


78-15589-01


Step 6 When you are ready to save the modified seed file, use one of the following procedures:

• To save the changes you have made to the seed file without changing the name of the file, select File > Save from the Discovery Dialog menu.

• To save the changes you have made to the seed file with a new name, select File > Save As from the Discovery Dialog menu. SGM displays the Save File Dialog: Seed File List dialog (Figure 3-6).






• Filename—Name by which you want to save the seed file.

If you create a new seed file name, you can use any letters, numbers, or characters in the name that are allowed by your operating system. However, if you include any spaces in the new name, SGM converts those spaces to dashes. For example, SGM saves file “a b c” as “a-b-c”.



To save the seed file with a new name, use one of the following procedures:


• To save the file with an existing name, overwriting an old seed file, select the name in the list and click OK.

SGM saves the seed file with the new name, closes the Save File Dialog: Seed File List dialog, and returns to the Discovery Dialog.


78-15589-01


Note If another user modifies and saves the seed file before you save your changes, SGM asks if you want to overwrite that user’s changes. If you choose to do so, the other user’s changes are overwritten and lost. If you choose not to do so, your changes are lost, unless you save the seed file to a different filename.

SGM stores the seed file in the seed file directory on the SGM server:



To delete a seed file from the seed file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.

To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: Seed File List dialog.

To close the Save File Dialog: Seed File List dialog without saving the seed file or saving any changes to the seed file list, click Cancel.

Creating and Modifying Seed Files Using a Text EditorA seed file is simply an unformatted list of seed node names. To create a seed file using a text editor, simply create a file and list the seed node names, one on each line, with no other formatting:

new-york-a

new-york-b

chicago-c


78-15589-01


When you save and name the seed file, keep the following considerations in mind:

• You can use any letters, numbers, or characters in the name that are allowed by your operating system.

• SGM saves the seed file with a .see file extension.

• SGM saves the seed file in the SGM server’s seed file directory, seeds:

– If you installed SGM in the default directory, /opt, then the seed file directory is /opt/CSCOsgm/seeds/.

– If you installed SGM in a different directory, then the seed file directory is located in that directory.

When SGM loads the seed file, it verifies the syntax of the file, deleting blank lines and extraneous leading and trailing spaces as needed. SGM also verifies that each seed node name resolves to a valid IP address. If a name does not resolve to a valid IP address, SGM logs the erroneous entry and ignores it.

For example, given the following seed file:

new-york-a<space>

<space>new-york-b

zzzzzzzzzzzz

<blank line>

<tab>chicago-c<tab>

SGM loads the following entries:

new-york-a

new-york-b

chicago-c


78-15589-01

Chapter 3 Managing ITP Networks Using SGMWorking with Views

Working with ViewsWhen SGM discovers your network, all discovered nodes, signaling points, linksets, and links are placed in a DEFAULT configuration view, which is stored on the SGM server and shared by all SGM clients. The DEFAULT view cannot be modified by the clients. It is always available, for users who need to view the entire network.

Initially, all clients use the DEFAULT view. However, SGM enables you to create your own, client-specific views, which are subsets of the DEFAULT view, to meet your individual needs.

You can choose the nodes you are interested in managing, remove all other nodes from your view, and modify the layout of the topology map in the Topology window. You can save all of this customized information in a view, set that view as the default view for the SGM client, and use the SGM client from then on to manage only the part of the network you are interested in, with the settings you prefer.

You can also create many different views on a given SGM client, with each view devoted to a different aspect of the network. You can then switch between views to manage different parts of the network, or switch to the DEFAULT view to see the entire network.

If a given SGM client is used by more than one person, each user can create his or her own personal view.

To help you keep track of which view you are currently using, most SGM windows display the following information:

• In the title bar, the name of the system on which the SGM server is running.

• In the bottom right corner:

– The name of the current view.

– The text (New Nodes Exist), if there is at least one newly discovered node or signaling point in the network that has not been added to your current view. To add the node to your current view, see the “Viewing the Topology of the Network” section on page 3-259. To exclude the node from your current view, see Step 6 in this section.

– The text (Modified), if the view has been modified but not yet saved. You must save the view if you want to save your changes. See Step 10 in this section for more details.


78-15589-01


If your personal default view has been deleted, then the next time you launch the client SGM informs you that your default view has been deleted and that your view has been reset to the DEFAULT view. To choose another view as your default view, use the Load File Dialog: View List. See the “Loading a Client-Specific View” section on page 3-35 for details.


• Creating a View, page 3-27

• Loading the DEFAULT View, page 3-35

• Loading a Client-Specific View, page 3-35

Related Topics:


• Modifying Preference Settings, page 5-3

• Modifying the Message Display, page 5-20


Creating a ViewTo create a client-specific network view:

Step 1 Before creating a client-specific network view, make sure that Discovery has been run at least once, and there is data in the server’s SGM database. See the “Discovering the Network” section on page 3-6 for details.

Step 2 Select Edit > Network Views from the SGM Main Menu. SGM displays the Network View Editor window (Figure 3-7).


78-15589-01


Figure 3-7 Network View Editor Window

The Nodes panel and Signaling Points panel display:

• New nodes and signaling points that have been found by SGM.

• All nodes and signaling points that are in the current view.

• All nodes and signaling points that have been excluded from the current view.

The Nodes panel and Signaling Points panel also enable you to move nodes and signaling points into and out of the current view. All changes made in these panels are reflected in topology tables and maps as soon as you make the changes.

To display the Nodes panel, select the Nodes tab.

To display the Signaling Points panel, select the Signaling Points tab.

Step 3 (Optional) If you have already saved a view and you want to modify it, select the File > Load menu option. SGM prompts you for the name of the view you want to load. Enter the name of the view, or accept the default view name, then click OK to load the view.


78-15589-01


Step 4 (Optional) The Nodes In Current View table lists the nodes that are in the current view. If there are nodes listed in the Nodes In Current View table that you do not want to manage, you can remove them from the current view. To do so, select one or more nodes in the Nodes In Current View table, then click the right-arrow button to move the nodes to the Nodes Excluded from View table.

Note If you are using an SGM client with the DEFAULT view set, SGM automatically adds all newly discovered nodes to the Nodes In Current View table as soon as they are discovered.

If you delete a node, SGM removes it from the Nodes In Current View table. If SGM then discovers the node, SGM places it in the New Nodes Found table. To see this node again in your current view, you must move it into the Nodes In Current View table.

At times, you might want to make an existing node a new node. To do so, select one or more nodes in the Nodes In Current View table, then click the left-arrow button to move the nodes to the New Nodes Found table.

Step 5 (Optional) The Nodes Excluded from View table lists the nodes that have been excluded from the current view. To add these nodes to the current view, select them in the Nodes Excluded from View table and click the left-arrow button to move the node to the Nodes In Current View table.

At times, you might want to make an excluded node a new node. To do so, select one or more nodes in the Nodes Excluded From View table, click the left-arrow button to move the node to the Nodes In Current View table, then click the next left-arrow button to move the nodes to the New Nodes Found table.

Step 6 (Optional) The New Nodes Found table displays newly discovered nodes, based on the following criteria:

• If you are using an SGM client with the DEFAULT view set, this table never contains any nodes. In the DEFAULT view, SGM adds all newly discovered nodes to the Nodes In Current View table as soon as they are discovered.

• If you are using an SGM client with a custom view set, this table contains all nodes discovered since the Network View Editor window was opened in this session that have not been excluded in the Nodes Excluded from View table, or that are not in the current view.


78-15589-01


When SGM discovers one or more new nodes in the network, SGM also takes the following actions:

• SGM broadcasts the discovery of the new nodes to all SGM clients.

• SGM displays the text (New Nodes Exist) in the bottom right corner of most SGM windows.

• SGM adds graphical elements for the newly discovered nodes to the topology new signaling point panel in the left pane of the Topology window. For more information, see the “Viewing the Topology of the Network” section on page 3-259.

To add a newly discovered node to the current view, select one or more nodes and click the right-arrow button to move them to the Nodes In Current View table.

To exclude a newly discovered node from the current view, select the node, click the right-arrow button to move the node to the Nodes In Current View table, then click the next right-arrow button to move the node to the Nodes Excluded From View table.

Step 7 (Optional) The Signaling Points In Current View table lists the signaling points that are in the current view. If there are signaling points listed in the Signaling Points In Current View table that you do not want to manage, you can remove them from the current view. To do so, select one or more signaling points in the Signaling Points In Current View table, then click the right-arrow button to move the signaling points to the Signaling Points Excluded from View table.

Note If you are using an SGM client with the DEFAULT view set, SGM automatically adds all newly discovered signaling points to the Signaling Points In Current View table as soon as they are discovered.

If you delete a signaling point, SGM removes it from the Signaling Points In Current View table. If SGM then discovers the signaling point, SGM places it in the New Signaling Points Found table. To see this signaling point again in your current view, you must move it into the Signaling Points In Current View table.

At times, you might want to make an existing signaling point a new signaling point. To do so, select one or more signaling points in the Signaling Points In Current View table, then click the left-arrow button to move the signaling points to the New Signaling Points Found table.


78-15589-01


Step 8 (Optional) The Signaling Points Excluded from View table lists the signaling points that have been excluded from the current view. To add these signaling points to the current view, select them in the Signaling Points Excluded from View table and click the left-arrow button to move the signaling point to the Signaling Points In Current View table.

At times, you might want to make an excluded signaling point a new signaling point. To do so, select one or more signaling points in the Signaling Points Excluded From View table, click the left-arrow button to move the signaling point to the Signaling Points In Current View table, then click the next left-arrow button to move the signaling points to the New Signaling Points Found table.

Step 9 (Optional) The New Signaling Points Found table displays newly discovered signaling points, based on the following criteria:

• If you are using an SGM client with the DEFAULT view set, this table never contains any signaling points. In the DEFAULT view, SGM adds all newly discovered signaling points to the Signaling Points In Current View table as soon as they are discovered.

• If you are using an SGM client with a custom view set, this table contains all signaling points discovered since the Network View Editor window was opened in this session that have not been excluded in the Signaling Points Excluded from View table, or that are not in the current view.

When SGM discovers one or more new signaling points in the network, SGM also takes the following actions:

• SGM broadcasts the discovery of the new signaling points to all SGM clients.

• SGM displays the text (New Signaling Points Exist) in the bottom right corner of most SGM windows.

• SGM adds graphical elements for the newly discovered signaling points to the topology new signaling point panel in the left pane of the Topology window. For more information, see the “Viewing the Topology of the Network” section on page 3-259.

To add a newly discovered signaling point to the current view, select one or more signaling points and click the right-arrow button to move them to the Signaling Points In Current View table.

To exclude a newly discovered signaling point from the current view, select the signaling point, click the right-arrow button to move the signaling point to the Signaling Points In Current View table, then click the next right-arrow button to move the signaling point to the Signaling Points Excluded From View table.


78-15589-01


Step 10 When you are satisfied with the changes you have made to the view, use one of the following procedures to save the view:

• To save the changes you have made to the view without changing the name of the file, select File > Save from the Network View Editor menu.

Note You cannot save changes to the DEFAULT view. If you are currently using the DEFAULT view and you select File > Save, SGM displays the Save File Dialog: View List dialog (Figure 3-8).

• To save the changes you have made to the view with a new name, select File > Save As from the Discovery Dialog menu. SGM displays the Save File Dialog: View List dialog (Figure 3-8).

Figure 3-8 Save File Dialog: View List Dialog


78-15589-01


The Save File Dialog: View List dialog contains the following fields:

– Type—Icon indicating whether the item in the table is a file or a folder.

– Name—Name of the view file or folder.

– Last Modified—Date and time the view file or folder was last modified.

– Size (bytes)—Size of the view file or folder, in bytes.

– Filename—Name by which you want to save the view. You must specify a name other than DEFAULT. You cannot save changes to the DEFAULT view.

If you create a new view name, you can use any letters, numbers, or characters in the name that are allowed by your operating system. However, if you include any spaces in the new name, SGM converts those spaces to dashes. For example, SGM saves file “a b c” as “a-b-c”.

– Make this my preferred start option—Specifies whether the selected view is to be loaded automatically whenever the associated preferences file is loaded:

- To load the selected view, select the view, then select this checkbox.

- To load the last-used view, clear the checkbox. This is the default setting.

– Number of Files—Total number of view files and folders (displayed in bottom left corner).

To save the view with a new name, use one of the following procedures:

– To save the file with a completely new name, enter the new name and click OK.

– To save the file with an existing name, overwriting an old view, select the name in the list and click OK.

SGM saves the view with the new name, closes the Save File Dialog: View List dialog, and returns to the Discovery Dialog.

Note If another user modifies and saves the view before you save your changes, SGM asks if you want to overwrite that user’s changes. If you choose to do so, the other user’s changes are overwritten and lost. If you choose not to do so, your changes are lost, unless you save the view to a different filename.


78-15589-01


SGM stores the view in the view file directory on the SGM server:

– If you installed SGM in the default directory, /opt, then the SGM view file directory is /opt/CSCOsgm/views.

– If you installed SGM in a different directory, then the SGM view file directory is located in that directory.

To delete a view from the view list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.

To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: View List dialog.

To close the Save File Dialog: View List dialog without saving the view or saving any changes to the view list, click Cancel.

Step 11 (Optional) To close the Network View Editor window at any time, click File > Close. If you have modified the view, SGM asks if you want to apply the changes before leaving the window:

• Click Yes to apply the changes to the current view. SGM applies the changes to all SGM windows immediately. SGM then asks if you want to make this the default view:

– Click Yes to make this view the new default view. In the future, when this client is started, this will be the default view.

– Click No to retain your old default view.

SGM closes the Network View Editor window.

• Click No to keep the current view as-is, without applying any changes. SGM closes the Network View Editor window.

• Click Cancel to close the prompt window and return to the Network View Editor window without applying any changes to the current view.

If you are working in a custom view (that is, not in the DEFAULT view) and you exit the SGM client, SGM automatically saves any changes you made to the view.


78-15589-01


Loading the DEFAULT ViewTo load the DEFAULT network view:


Step 2 Select File > Load DEFAULT View from the Discovery Dialog menu. SGM loads the DEFAULY view.

Loading a Client-Specific ViewTo load a client-specific network view:


Step 2 Select File > Load from the Discovery Dialog menu. SGM displays the Load File Dialog: View List dialog (Figure 3-9).


78-15589-01


Figure 3-9 Load File Dialog: View List Dialog

The Load File Dialog: View List dialog contains the following fields:


• Name—Name of the view file or folder.

• Last Modified—Date and time the view file or folder was last modified.

• Size (bytes)—Size of the view file or folder, in bytes.

• Make this my preferred start option—Specifies whether the selected view is to be loaded automatically whenever the associated preferences file is loaded:

– To load the selected view, select the view, then select this checkbox.

– To load the last-used view, clear the checkbox. This is the default setting.

• Number of Files—Total number of view files and folders (displayed in bottom left corner).

To load a view, select the view in the list and click OK.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMWorking with Linksets

SGM closes the Load File Dialog: View List dialog, loads the view, and returns to the Network View Editor window.

To close the Load File Dialog: View List dialog without loading a view, click Cancel.

Working with LinksetsSGM enables you to view information about all discovered linksets, including their associated nodes, status, and other important information.


• Viewing Basic Information for Linksets, page 3-38

• Viewing Detailed Information for a Linkset, page 3-42

• Viewing Real-Time Data for a Linkset, page 3-54

• Editing a Linkset, page 3-84

• Viewing Notes for a Linkset, page 3-87

• Deleting a Linkset, page 3-88

• Ignoring a Linkset, page 3-90

• Viewing Ignored Linksets, page 3-90

Related Topics:








78-15589-01


Viewing Basic Information for LinksetsTo view basic information for linksets, select Linksets in the left pane of the SGM Main Window. SGM displays the Linkset Window (Figure 3-10).

Figure 3-10 Linkset Window

The Linkset Window displays information about the linksets that have been discovered by SGM.

Linksets that are associated with nodes that are excluded from the current view are not displayed in the Linkset Window. See the “Creating a View” section on page 3-27 for more information about excluding nodes.

By default, SGM displays all of the columns in the Linkset Window except Internal ID, Name, Local Point Code, Adj Point Code, and Notes. To display these columns, or to hide other columns, see the procedures in the “Modifying Linkset Table Column Settings” section on page 5-18.




78-15589-01



The Linkset Window displays the following information for each discovered linkset:

• Internal ID—The internal ID of the linkset. The internal ID is a unique ID for every event, link, linkset, signaling point, and node, assigned by SGM for its own internal use. It can also be useful when the TAC is debugging problems.

• Name—Name of the linkset.

• Local Point Code—Point code of the primary node for the linkset.

• Adj Point Code—Point code of the adjacent node for the linkset.

• Linkset Type—Type of linkset, which SGM determines by examining the links defined in the linkset. Possible linkset types are:

– HSL—The links in this linkset use the SS7-over-ATM (Asynchronous Transfer Mode) high-speed protocol.

– SCTPIP—The links in this linkset use the Stream Control Transmission Protocol (SCTP) IP transport protocol.

– Serial—The links in this linkset use the serial SS7 signaling protocol.

– Mixed—The links in this linkset are of two or more types. (This arrangement is not recommended.)

– Virtual—The links in this linkset are virtual links, which connect signaling point instances running on the same device. SGM does not poll virtual linksets, nor does it display real-time data or accounting statistics for virtual linksets.

– Other—No links have been defined for this linkset.

• Links—Total number of links in the linkset.

• Active Links—Number of links in the linkset that are Active.

• Congested Links—Number of links in the linkset that are Congested.

• Ignored—Indicates whether the linkset is to be included when aggregating and displaying SGM status information.

• Notes— Indicates whether there is a note associated with the linkset.


78-15589-01


• Events—Indicates whether there is a recent event associated with the linkset.

– To delete the event icon from SGM displays for a specific linkset, for this SGM client only, select the linkset and click the icon.

– To delete the event icon from SGM displays for all linksets, for this SGM client only, select Edit > Clear All Events from the SGM Main Menu.

Note During Discovery, SGM might flag most linksets with an event icon. If the event icons are too distracting, use the Edit > Clear All Events menu option to remove them.

• Last Status Change—Date and time that the status of the linkset last changed.

• Status—Current status of the linkset. Possible values are:

– Active (green ball)—The linkset is currently fully functional.

– Unavailable (red ball)—An error is preventing traffic from flowing on this linkset.

– Shutdown (blue ball)—An ITP administrator has set the linkset to prevent traffic from flowing. When a linkset is set to Shutdown, all its associated links are set to Failed by Cisco IOS.

– Unknown (red ball)—Either the node associated with this linkset has failed to respond to an SNMP request, or SGM found that the linkset no longer exists.

– Warning (yellow ball)—The linkset is active, but one or more links in the linkset is congested or is in Failed, Unknown, or Warning status, and is not Ignored. At least one link is available and can carry traffic.

• Status Reason—Reason for the current status of the linkset. Possible values are:

– None

– SGM Restart


– Unconfigured

– SNMP Timeout



78-15589-01


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive







78-15589-01


Viewing Detailed Information for a LinksetSGM can display detailed information about a selected linkset, including its associated links, status, and other information.

To display detailed information for a linkset, use one of the following procedures:

• Select Linksets in the left pane of the SGM Main Window, right-click a linkset in the right pane, then select View> Configuration Details in the right-click menu.

• Select the turner beside Linksets in the left pane of the SGM Main Window, then select a linkset.

SGM displays the Linkset Details Window (Figure 3-11).

Figure 3-11 Linkset Details Window

Detailed information for the selected linkset is displayed in the left column, and for the adjacent linkset in the right column.

Updates for the linkset that are received from the SGM server are reflected automatically in this window.


78-15589-01


Changes you make in this pane might not be reflected throughout SGM until the next poll (by default, every 15 seconds). For information about changing the polling interval, see the “Viewing Detailed Information for a Link” section on page 3-175.

Note This window polls your network periodically. To prevent unnecessary traffic on your network, close this window when you no longer need to refer to it.

Links Tab

To view information about the links that are associated with the selected linkset, select the Links tab. SGM displays the linksets in the top table, and the links in the bottom table.




By default, SGM displays all of the columns in the Link Table except Internal ID, Congestion Level, and Last Status Change. To display these columns, or to hide other columns, see the procedures in the “Modifying Linkset Table Column Settings” section on page 5-18.

The Link Table displays the following information about links that are associated with the selected linkset:

• Internal ID—Internal ID of the link. The internal ID is a unique ID for every event, linkset, link, signaling point, and node, assigned by SGM for its own internal use. It can also be useful when the TAC is debugging problems.

• Node—Name of the node associated with the link.

• Signaling Point—Name of the signaling point associated with the link.

• Linkset—Name of the linkset associated with the link.

• SLC—Signaling link code (SLC) ID for the link.


78-15589-01


• Type—Type of link. Possible link types are:

– HSL—The link uses the SS7-over-ATM (Asynchronous Transfer Mode) high-speed protocol.

– SCTPIP—The link uses the Stream Control Transmission Protocol (SCTP) IP transport protocol.

– Serial—The link uses the serial SS7 signaling protocol.

– Virtual—The link is a virtual link, which connects signaling point instances running on the same device. SGM does not poll virtual links, nor does it display real-time data or accounting statistics for virtual links.

• Congestion Level—Indicates whether there is congestion on the link. A link is congested if it has too many packets waiting to be sent. This condition could be caused by the failure of an element in your network.

Possible values for the Congestion Level field are:

– None—The link is not congested.

– Low—The link is slightly congested.

– High—The link is congested.

– Very High—The link is very congested.

Low, High, and Very High correspond roughly to equivalent ANSI, China standard, and ITU congestion levels.

• Ignored—Indicates whether the link is to be included when aggregating and displaying SGM status information:

– Clear the checkbox to include the link. This is the default setting.

– Select the checkbox to exclude the link.

This field can be edited by users with authentication level Power User (Level 2) and higher.

• Notes—Indicates whether there is a note associated with the link.


78-15589-01


• Events—Indicates whether there is a recent event associated with the link.

– To delete the event icon from SGM displays for a specific link, select the link and click the icon.

– To delete the event icon from SGM displays for all links, select Edit> Clear All Events from the SGM Main Menu.

Note During Discovery, SGM might flag most links with an event icon. If the event icons are too distracting, use the Edit> Clear All Events menu option to remove them.

• Last Status Change—Date and time that the status of the link last changed.

• Status—Current status of the link. Possible values are:

– Active (green ball)—The link is currently fully functional.

– Blocked (red ball)—Traffic on this link is disabled by protocol.

– Failed (red ball)—An error is preventing traffic from flowing on this link, or the associated linkset has been set to Shutdown status.

A link can be Failed from an MTP3 perspective, but control messages might still be sent or received on the link, resulting in changing packet/second and bit/second rates. The rates might also be different at each end of the link, depending on the reason for the failure and the timing related to each endpoint.

– InhibitLoc (blue ball)—A local ITP administrator has set the link to prevent traffic from flowing.

– InhibitRem (blue ball)—A remote ITP administrator has set the link to prevent traffic from flowing.

– Shutdown (blue ball)—An ITP administrator has set the link to prevent traffic from flowing.


78-15589-01


– Unknown (red ball)—Either the node associated with this link has failed to respond to an SNMP request, or SGM found that the link no longer exists.

When you physically delete a link, the Status field displays Unknown until you delete the link from the SGM database.

– Warning (yellow ball)—The link is active and traffic is flowing, but one or more of the following situations has occurred:

– The link is congested.

– The link has exceeded the defined Receive Utilization % or Send Utilization %.

– One or more of the local or remote IP addresses defined for SCTP is not active.

• Status Reason—Reason for the current status of the link. Possible values are:

– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





78-15589-01



– Link Inactive




Configuration Data Tab: Naming Information

To view naming information for the selected linkset, select the Configuration Data tab.

The Naming Information sub-section displays the following information for the selected linkset:










78-15589-01





– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive




78-15589-01



Configuration Data Tab: Description

To view descriptive information for the selected linkset, select the Configuration Data tab.

The Description sub-section contains a description of the linkset. If the linkset has no description, this sub-section is blank.

Configuration Data Tab: General Information

To view general information for the selected linkset, select the Configuration Data tab.

The General Information sub-section displays the following information for the selected linkset:





– Mixed—The links in this linkset are of two or more types. (This configuration is not recommended.)




78-15589-01


• Is Ignored—Indicates whether the linkset is Ignored (that is, whether the linkset is to be included when aggregating and displaying SGM status information).

• Inbound ACL—Inbound IP access control list (ACL) number for the linkset. If there is no inbound ACL for the linkset, this field displays 0.

• Outbound ACL—Outbound ACL number for the linkset. If there is no outbound ACL for the linkset, this field displays 0.

Configuration Data Tab: Links Information

To view links information for the selected linkset, select the Configuration Data tab.

The Links Information sub-section displays the following information for the selected linkset:




Notes Tab

To view notes for the selected linkset, select the Notes tab.

The Notes section displays:

• Notes associated with the selected linkset in the left column.

• Notes associated with the adjacent linkset in the right column.

• The date and time the notes associated with each linkset were last updated, or the phrase Not Set if there are no notes associated with the linkset.

• The phrase No Notes if there are no notes associated with the linkset.

Recent Events Tab

To view information about all recent events associated with the linkset, select the Recent Events tab. SGM displays the Recent Events table for the linkset (Figure 3-12).


78-15589-01


Figure 3-12 Recent Events Table for a Linkset

By default, SGM displays all of the columns in the table except Internal ID, Note, Ack By, Ack Time, Node, SP, Linkset, and Link. To display these columns, or to hide other columns, see the procedures in the “Modifying Event Table Column Settings” section on page 5-19.




The Recent Events table enables you to perform event-related tasks, such as setting filters and acknowledging events. For more information about these tasks, see the “Working with Events” section on page 3-235.


78-15589-01


The Recent Events table displays the following information for the selected linkset:


• Ack—Indicates whether the event has been acknowledged:

– To acknowledge an unacknowledged event, use the Acknowledge toolbar button.

– To make a previously acknowledged event unacknowledged, use the Unacknowledge toolbar button.

• Category—Type of the event. Default values are:

– Create—Creation event, such as the creation of a seed file.

– Delete—Deletion event, such as the deletion of a node, signaling point, linkset, or file.

– Discover—Discovery event, such as Discovery beginning.

– Edit—Edit event. A user has edited a node, signaling point, linkset, or link.

– Ignore—Ignore event. A user has Ignored a link or linkset.

– Login—Login event. A user has logged in to SGM.

– LoginDisable—LoginDisable event. SGM has disabled a user’s User-Based Access authentication as a result of too many failed attempts to log in to SGM.

– LoginFail—LoginFail event. An attempt by a user to log in to SGM has failed.

– OverWrite—OverWrite event. An existing file, such as a seed file or route file, has been overwritten.

– Poll—Poll event, such as an SNMP poll.

– Purge—Purge event. A user has requested Discovery with Delete Existing Data selected, and SGM has deleted the existing SGM database.


78-15589-01


– Status—Status change message generated.

– Trap—SNMP trap message generated.

You can customize this field. See the “Modifying the SGM Event Configuration File (Solaris Only)” section on page 5-26 for more information.

• Severity—Severity of the event. Default values are:

– Admin—The default color is cyan.

– Error—The default color is coral.

– None—The default color is white.

– Normal—The default color is light green.

– Warning—The default color is yellow.


• Note—Indicates whether there is a note associated with the event.

• Time—Date and time the event was logged.

• Ack By—If you have not implemented SGM User-Based Access, name of the device that last acknowledged the event.

If you have implemented SGM User-Based Access, name of the user who last acknowledged the event.

If no one has acknowledged the event, this field is blank.

• Ack Time—Date and time the event was last acknowledged or unacknowledged.

• Node—Name of the node associated with the event. If there is no node associated with the event, None is displayed.

• SP—Name of the signaling point associated with the event. If there is no signaling point associated with the event, None is displayed.

• Linkset—Name of the linkset associated with the event. If there is no linkset associated with the event, None is displayed.


78-15589-01


• Link—Name of the link associated with the event. If there is no link associated with the event, None is displayed.

• Message—Text of the message.


ITP Access Lists Tab

To view information about all access lists associated with the selected linkset and its adjacent linkset, select the ITP Access Lists tab.

For each linkset, the ITP Access Lists section displays the following information:

• Current Poll Interval—Poll interval used to collect data for the table.

• Last Poll—Time the last poll was run. This field initially displays the phrase Polling device. After the first polling cycle, SGM populates this field with the actual time of the last poll.

• Linkset—Name of the linkset for which access lists are being displayed.

• In—Inbound access lists for the linkset. If the linkset has no inbound access lists, this field displays None.

• Out—Outbound access lists for the linkset. If the linkset has no outbound access lists, this field displays None.

• List #—Access list number configured on the node and applied to the linkset. ITP uses access list numbers 2700 through 2799.

• Access List—List of commands in the access list.

Viewing Real-Time Data for a LinksetSGM enables you to display detailed statistics for a selected linkset, including its associated links, status, and other information. Detailed information for the selected linkset is displayed in the left column, and for the adjacent linkset in the right column.

To display detailed statistics for a linkset, select Linksets in the left pane of the SGM Main Window, right-click a linkset in the right pane, then select View> Real-Time Data and Charts in the right-click menu. SGM displays the Statistics Details Window for a Linkset (Figure 3-13).


78-15589-01


Figure 3-13 Statistics Details Window for a Linkset

Updates for the linksets that are received from the SGM server are reflected automatically in this window.

Changes you make in this window might not be reflected throughout SGM until the next poll (by default, every 15 seconds). For information about changing the polling interval, see the “Viewing Detailed Information for a Link” section on page 3-175.



78-15589-01



To view naming information for the selected linkset, select the Configuration Data tab.

The Naming Information sub-section displays the following information for the selected linkset:












– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


78-15589-01



– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive





To view descriptive information for the selected linkset, select the Configuration Data tab.

The Description sub-section contains a description of the linkset. If the linkset has no description, this sub-section is blank.


78-15589-01



To view general information for the selected linkset, select the Configuration Data tab.

The General Information sub-section displays the following information for the selected linkset:








• Is Ignored—Indicates whether the linkset is Ignored (that is, whether the linkset is to be included when aggregating and displaying SGM status information).




78-15589-01


Configuration Data Tab: Links Information

To view links information for the selected linkset, select the Configuration Data tab.

The Links Information sub-section displays the following information for the selected linkset:




Notes Tab

To view notes for the selected linkset, select the Notes tab.


• Notes associated with the selected linkset in the left column.

• Notes associated with the adjacent linkset in the right column.

• The date and time the notes associated with each linkset were last updated, or the phrase Not Set if there are no notes associated with the linkset.

• The phrase No Notes if there are no notes associated with the linkset.

Recent Events Tab

To view information about all recent events associated with the linkset, select the Recent Events tab. SGM displays the Recent Events table for the linkset (Figure 3-12).






78-15589-01


The Recent Events section enables you to perform event-related tasks, such as setting filters and acknowledging events. For more information about these tasks, see the “Working with Events” section on page 3-235.

The Recent Events table displays the following information for the selected linkset:


















78-15589-01






















78-15589-01






To view information about all access lists associated with the selected linkset and its adjacent linkset, select the ITP Access Lists tab.

For each linkset, the ITP Access Lists section displays the following information:








Statistics Tab: Packet Information

To view packet information for the selected link, select the Statistics tab.


78-15589-01


The Packet Information sub-section displays the following information for the selected link:

• Sent Per Sec—Number of packets sent by the linkset per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Received Per Sec—Number of packets received by the linkset per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Drops—Total number of packets that have been dropped by the linkset.

Statistics Tab: Bit Information or Byte Information

To view bit information for the selected linkset (or byte information, if you cleared the Show Details in Bits Instead of Bytes checkbox in the Preferences Window), select the Statistics tab.

The Bit Information or Byte Information sub-section displays the following information for the selected linkset:

• Sent Per Sec—Number of bits or bytes (as set in the Preferences window) sent by the linkset per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Received Per Sec—Number of bits or bytes (as set in the Preferences window) received by the linkset per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.


78-15589-01


Statistics Tab: Utilization Information

To view utilization information for the selected linkset, select the Statistics tab.

The Utilization Information sub-section displays the following information for the selected linkset:

• Send Plan Capacity—Planned capacity of the linkset to send, in bits per second.

– For a linkset of type Serial or HSL, available bandwidth for the linkset.

– For a linkset of type SCTPIP or Mixed, set on the ITP using the plan-capacity CS7 linkset configuration command.

If Send Plan Capacity is not set on the ITP for this linkset, this field displays the value 0.

– For a linkset of type Other, this field always displays the value 0.

• Send Utilization—Amount of the linkset’s send capacity being used, as a percentage or in Erlangs (as set in the Preferences window), calculated using the following formula:

Send Utilization = (Bits Sent Per Sec)/Planned Capacity

This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

– For a linkset of type SCTPIP or Mixed, if Send Plan Capacity is not set on the ITP for this linkset, this field displays the phrase Set Plan Capacity on ITP.

– For a linkset of type Other, this field always displays the phrase Set Plan Capacity on ITP.

• Receive Plan Capacity—Planned capacity of the linkset to receive, in bits per second.



If Receive Plan Capacity is not set on the ITP for this linkset, this field displays the value 0.



78-15589-01


• Receive Utilization—Amount of the linkset’s receive capacity being used, as a percentage or in Erlangs (as set in the Preferences window), calculated using the following formula:

Receive Utilization = (Bits Received Per Sec)/Receive Plan Capacity


– For a linkset of type SCTPIP or Mixed, if Receive Plan Capacity is not set on the ITP for this linkset, this field displays the phrase Set Plan Capacity on ITP.

– For a linkset of type Other, this field always displays the phrase Set Plan Capacity on ITP.

Statistics Tab: Service Information

To view service information for the selected linkset, select the Statistics tab.

The Service Information sub-section displays the following information for the selected linkset:

• MTP3 Accounting Enabled—Indicates whether the collection of MTP3 accounting statistics is enabled for the linkset.

• GTT Accounting Enabled—Indicates whether the collection of GTT accounting statistics is enabled for the linkset. For Cisco IOS software releases prior to 12.2(4)MB10, this field displays Unknown.

• Duration In Service %—Percentage of time the linkset has been in service since the last reboot of the ITP, or since ITP last reset the counters.

• Duration Out Of Service %—Percentage of time the linkset has been out of service since the last reboot of the ITP, or since ITP last reset the counters.


78-15589-01


Charts Tab: ReceivedUtilization

To view real-time ReceivedUtilization information for the selected linkset, select the Charts tab. SGM displays the ReceivedUtilization chart (Figure 3-14).

Figure 3-14 ReceivedUtilization Chart for a Linkset


78-15589-01


The ReceivedUtilization chart displays the following information for the selected linkset:

• Linkset—Drop-down list box used to select the linkset from whose perspective data is to be displayed. By default, data is displayed from the perspective of the selected linkset. To display data from the perspective of the adjacent linkset, select it in this list box.

• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Received Utilization Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.

• Received Utilization Chart—Displays the average Receive Utilization % for all links on the linkset as a function of time, and optionally the Receive Utilization % for up to 16 individual links on the linkset.

To see the exact time and data coordinates for a data point, left-click the data point. The coordinates are displayed in the format (hh:mm:ss, dd.dd), where:

– hh:mm:ss is the time for that data point in hours, minutes, and seconds.

– dd.dd is the receive utilization percentage for that data point.

To remove the data for a link or for the average from the chart, click the icon in the SLC field. To return the data to the chart, click the icon again.

The total time displayed in the chart is specified in the Time Window (mins) field.

New data points are added to the right side of the chart. When the chart reaches the end of the time window (for example, after 5 minutes, if the Time Window (mins) field is set to 5), new data points continue to be added to the right side of the chart, while old data points “drop off” the left side of the chart.

If a poll is missed (for example, as a result of an SNMP timeout), SGM ignores the missing data point, stops drawing the line, and waits for the next valid data point to begin drawing the line again.

To scroll left, right, up, or down in the chart, drag the cursor while holding down Ctrl and the left mouse button.

To zoom in on a section of the chart, drag the cursor while holding down Shift and the left mouse button.

To reset the chart to the default view and scaling, click Reset.


78-15589-01


• SLC—Displays up to 17 color-coded icons:

– One for each link (SLC) in the Received Utilization Chart, up to 16 total links.

– One for the average of all SLCs.

To remove the data for a link or for the average from the chart, click the icon in this field. To return the data to the chart, click the icon again.

• Show threshold line for:—Draws a horizontal line on the Received Utilization Chart, indicating the receive threshold for the selected link.

If you do not want to draw a threshold line, select None. This is the default setting.

• Scale to threshold—Scales the Received Utilization Chart in order to draw the threshold selected in the Show threshold line for field:

– To scale the chart, select this checkbox.

– To remove the scaling from the chart, clear this checkbox. This is the default setting.

The Scale to threshold checkbox is not available if the Show threshold line for: field is set to None.

To superimpose a graphic grid on the chart, which can make the data easier to read, click Grid On.

To remove the graphic grid from the chart, click Grid Off.

To display online help for the window, click Help.


78-15589-01


Charts Tab: SendUtilization

To view real-time SendUtilization information for the selected linkset, select the Charts tab. SGM displays the SendUtilization chart (Figure 3-15).

Figure 3-15 SendUtilization Chart for a Linkset


78-15589-01


The SendUtilization chart displays the following information for the selected linkset:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Send Utilization Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.

• Send Utilization Chart—Displays the average Send Utilization % for all links on the linkset as a function of time, and optionally the Send Utilization % for up to 16 individual links on the linkset.



– dd.dd is the send utilization percentage for that data point.









78-15589-01



– One for each link (SLC) in the Send Utilization Chart, up to 16 total links.



• Show threshold line for:—Draws a horizontal line on the Send Utilization Chart, indicating the receive threshold for the selected link.

If you do not want to draw a threshold line, select None. This is the default setting.

• Scale to threshold—Scales the Send Utilization Chart in order to draw the threshold selected in the Show threshold line for field:

– To scale the chart, select this checkbox.

– To remove the scaling from the chart, clear this checkbox. This is the default setting.

The Scale to threshold checkbox is not available if the Show threshold line for: field is set to None.





78-15589-01


Charts Tab: PktsRcvdPerSec

To view real-time packets-received-per-second information for the selected link, select the Charts tab. SGM displays the PktsRcvdPerSec chart (Figure 3-16).

Figure 3-16 PktsRcvdPerSec Chart for a Linkset


78-15589-01


The PktsRcvdPerSec chart displays the following information for the selected link:

SGM displays the following information in the PktsRcvdPerSec chart:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Packets Received Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.

• Packets Received Chart—Displays the Packets Received Per Sec for the linkset as a function of time, including data for up to 16 links.



– dd.dd is the number of packets received per second for that data point.

To remove the data for a link from the chart, click the icon in the SLC field. To return the data to the chart, click the icon again.








78-15589-01



– One for each link (SLC) in the Packets Received Chart, up to 16 total links.






Charts Tab: PktsSentPerSec

To view real-time packets-sent-per-second information for the selected link, select the Charts tab. SGM displays the PktsSentPerSec chart (Figure 3-17).


78-15589-01


Figure 3-17 PktsSentPerSec Chart for a Linkset

The PktsSentPerSec chart displays the following information for the selected link:

SGM displays the following information in the PktsSentPerSec chart:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Packets Sent Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.


78-15589-01


• Packets Sent Chart—Displays the Packets Sent Per Sec for the linkset as a function of time, including data for up to 16 links.



– dd.dd is the number of packets sent per second for that data point.









– One for each link (SLC) in the Packets Sent Chart, up to 16 total links.







78-15589-01


Charts Tab: BitsRcvdPerSec

To view real-time bits-received-per-second information for the selected link (or bytes-received-per-second information, if you cleared the Show Details in Bits Instead of Bytes checkbox in the Preferences Window), select the Charts tab. SGM displays the BitsRcvdPerSec chart (Figure 3-18).

Figure 3-18 BitsRcvdPerSec Chart for a Linkset


78-15589-01


The BitsRcvdPerSec chart displays the following information for the selected link:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Bits Received Chart or Bytes Received Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.

• Bits Received Chart or Bytes Received Chart—Displays the Bits Received Per Sec or Bytes Received Per Sec for the linkset as a function of time, including data for up to 16 links.



– dd.dd is the number of bits or bytes (as set in the Preferences window) received per second for that data point.









78-15589-01



– One for each link (SLC) in the Bits Received Chart or Bytes Received Chart, up to 16 total links.






Charts Tab: BitsSentPerSec

To view real-time bits-sent-per-second information for the selected link (or bytes-sent-per-second information, if you cleared the Show Details in Bits Instead of Bytes checkbox in the Preferences Window), select the Charts tab. SGM displays the BitsSentPerSec chart (Figure 3-19).


78-15589-01


Figure 3-19 BitsSentPerSec Chart for a Linkset

The BitsSentPerSec chart displays the following information for the selected link:

SGM displays the following information in the BitsSentPerSec or BytesSentPerSec chart:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Bits Sent Chart or Bytes Sent Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.


78-15589-01


• Bits Sent Chart or Bytes Sent Chart—Displays the Bits Sent Per Sec or Bytes Sent Per Sec for the linkset as a function of time, including data for up to 16 links.



– dd.dd is the number of bits or bytes (as set in the Preferences window) sent per second for that data point.









– One for each link (SLC) in the Bits Sent Chart or Bytes Sent Chart, up to 16 total links.





78-15589-01




Charts Tab: Drops

To view drops information for the selected link, select the Charts tab. SGM displays the Drops chart (Figure 3-20).

Figure 3-20 Drops Chart for a Linkset


78-15589-01


The Drops chart displays the following information for the selected link:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Drops Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.

• Drops Chart—Displays the Drops for the linkset as a function of time, including data for up to 16 links.



– dd.dd is the number of drops for that data point.









78-15589-01



– One for each link (SLC) in the Drops Chart, up to 16 total links.






Editing a LinksetSGM enables you to annotate a linkset, attaching a descriptive string to the linkset.

To annotate a linkset:

Step 1 Right-click a linkset in a window.

Step 2 Select Edit Notes in the right-click menu. SGM displays the Edit Notes Dialog for a Linkset (Figure 3-21).


78-15589-01


Figure 3-21 Edit Notes Dialog for a Linkset

If both ends of the linkset are known to SGM, one is displayed in the top half of the Edit Notes Dialog for a Linkset, the other in the bottom half. If only one end is known to SGM, only that end is displayed.


78-15589-01


The Edit Notes Dialog for a Linkset displays the name of the linkset and the date and time the Notes field for the linkset was last updated. If there is no note currently associated with the linkset, the Notes Last Updated field displays the value Not Set.

Step 3 In the Notes field, enter any important information about the linkset, such as a detailed description, its location, its service history, and so on.

Step 4 Click Save to save the annotations and exit the Edit Notes Dialog for a Linkset.


78-15589-01


Viewing Notes for a LinksetSGM enables you to view the notes that have been attached to linksets.

To view a note, right-click a linkset in a window, then select View> Notes in the right-click menu. (The Notes option is grayed-out if there is no note associated with the selected linkset.) SGM displays the Linkset Notes dialog (Figure 3-22).

Figure 3-22 Linkset Notes Dialog

The Linkset Notes dialog displays the following information:


• Notes Last Updated—Date and time the Notes field for the linkset was last updated.

• Notes—Notes associated with the linkset.

Click OK to close the Linkset Notes dialog.


78-15589-01


Deleting a LinksetAfter Discovery, the linksets in your network are known to SGM and added to the SGM database. Physically deleting linksets from your network is not the same as deleting them from the SGM database. The following sections describe the differences between deleting linksets from your network and from the SGM database, and the procedures for doing so:

• Deleting a Linkset from Your Network, page 3-88

• Deleting a Linkset from the SGM Database, page 3-88

Deleting a Linkset from Your Network

If you physically delete a known linkset from your network, it remains in the SGM database, SGM labels it Unknown, and it is the system administrator’s responsibility to delete it from the SGM database, if you choose to do so. SGM labels all associated nodes Warning and all associated links Unknown.

When you redefine the linkset (that is, when you define a linkset with the same destination point code as the original linkset, but not necessarily with the same linkset name), SGM rediscovers the linkset and labels it with the appropriate status (such as Active).

Deleting a Linkset from the SGM Database

Typically, you delete a linkset in the SGM database for one of the following reasons:

• You have physically deleted the linkset from your network. This is the most common reason for deleting a linkset from the SGM database.

• The linkset is Unknown or Unavailable, you are aware of the reason, and you no longer want to see it in SGM displays. For example, the linkset might be associated with a node that was removed from the network, or it might be a previously discovered linkset associated with a test lab device.

If you have physically deleted a known linkset from your network, and you then delete it from SGM, it is no longer in the SGM database, it does not appear in SGM windows, and it is not discovered when you run Discovery.


78-15589-01


If you have not physically deleted a known linkset from your network, and you delete it from SGM, SGM also automatically deletes all associated links from the SGM database. However, at the next poll SGM finds the linkset and associated links and adds them back to the SGM database, setting the status appropriately. If this happens, do not delete the linkset again. Instead, set it to Ignored. See the “Ignoring a Linkset” section on page 3-90 for more information.

Note If you delete a linkset from the SGM database, the linkset is deleted for all SGM clients and views connected to that SGM server.

If you delete all linksets to an Unmanaged node, SGM does not automatically delete the node. Instead, you must manually delete the node. See the “Deleting a Node” section on page 3-130 for more information.

To delete a linkset from the SGM database, use one of the following procedures:

• Select one or more linksets in a window, then select Edit > Delete from the SGM Main Menu.

• Right-click a linkset in a window, then select Delete Item in the right-click menu. (You cannot delete more than one linkset at a time from the right-click menu.)

SGM asks you to confirm the deletion:

• Select Yes to delete the selected linksets. SGM deletes the linksets and all associated links from the SGM database. However, if the linksets were not physically deleted from your network, then at the next poll SGM finds the linksets and their associated links and adds them back to the SGM database, setting the status appropriately.

• Select No to return to the window without deleting any linksets or links from the SGM database.

You can also use the sgm delete linkset command to delete one or more linksets from the SGM database. See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of this command.


78-15589-01


Ignoring a LinksetYou can instruct SGM to ignore a linkset when it aggregates and displays network data. Setting linksets to Ignored prevents known linkset problems from affecting SGM displays for associated nodes. In effect, you are preventing a known problem from distracting you from other, more urgent network problems.

For example, you can set a linkset to Ignored before shutting down the linkset for maintenance.

Note If you set a linkset to Ignored, the linkset is ignored for all SGM clients and views connected to that SGM server.

Also, if you set a linkset to Ignored, make a note of the change, and do not forget to reset the linkset when the problem is corrected or the maintenance is complete.

To set a linkset to Ignored in the Linkset Window, select the Ignored checkbox for the linkset you want SGM to ignore.

To set a linkset to Ignored in the Topology window, select a linkset in the topology map, then, in the left pane, select the Ignored checkbox for the linkset you want SGM to ignore.

Viewing Ignored LinksetsTo display all linksets that are Ignored, display the Linkset Window and click the Ignored column header. SGM displays all ignored linksets at the top of the table.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMWorking with Nodes

Working with NodesSGM enables you to view information about all discovered nodes, including their IP addresses, status, and other important information.


• Viewing Basic Information for Nodes, page 3-92

• Viewing Detailed Information for a Node, page 3-96

• Viewing CPU Statistics for a Node, page 3-121

• Editing a Node, page 3-124

• Viewing Notes for a Node, page 3-128

• Deleting a Node, page 3-130

• Unmanaging and Managing a Node, page 3-133

• Polling a Node, page 3-134

• Excluding a Node from a View, page 3-136

Related Topics:








78-15589-01


Viewing Basic Information for NodesTo view basic information for nodes, select Nodes in the left pane of the SGM Main Window. SGM displays the Node Window (Figure 3-23).

Figure 3-23 Node Window

The Node Window displays information about the nodes that have been discovered by SGM.

By default, SGM displays all of the columns in the node table except Internal ID, ITP Uptime, Reboot Reason, and Last Status Change. To display these columns, or to hide other columns, see the procedures in the “Modifying Node Table Column Settings” section on page 5-16.



You can resize each column, or sort the table based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details. By default, this table is sorted by Status.


78-15589-01


The Node Window displays the following information for each discovered node:

• Internal ID—Internal ID of the node. The internal ID is a unique ID for every event, link, linkset, signaling point, and node, assigned by SGM for its own internal use. It can also be useful when the TAC is debugging problems.

• Name—Name or IP address of the node.




















• ITP MIB Level—MIB conformance level used by the ITP, such as ITP MB5.


78-15589-01




• Notes—Indicates whether there is a note associated with the node.

• Events—Indicates whether there is a recent event associated with the node.

– To delete the event icon from SGM displays for a specific node, for this SGM client only, select the node and click the icon.

– To delete the event icon from SGM displays for all nodes, for this SGM client only, select Edit > Clear All Events from the SGM Main Menu.

Note During Discovery, SGM might flag most nodes with an event icon. If the event icons are too distracting, use the Edit > Clear All Events menu option to remove them.












78-15589-01






– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive



78-15589-01






Viewing Detailed Information for a NodeSGM can display detailed information about a selected node, including its CLLI code, point code, status, and other information.

To display detailed information for a node, use one of the following procedures:

• Select Nodes in the left pane of the SGM Main Window, right-click a node in the right pane, then select View> Configuration Details in the right-click menu.

• Select the turner beside Nodes in the left pane of the SGM Main Window, then select a node.

SGM displays the Node Details Window (Figure 3-24).


78-15589-01


Figure 3-24 Node Details Window

Updates for the node that are received from the SGM server are reflected automatically in this window.

Changes you make in this window might not be reflected throughout SGM until the next poll (by default, every 15 seconds). For information about changing the polling interval, see the “Viewing Detailed Information for a Linkset” section on page 3-42.


Signaling Points Tab: Signaling Points

To view information about the signaling points that are associated with the selected node, select the Signaling Points tab. SGM displays the linksets in the top table, and the links in the bottom table.



78-15589-01




By default, SGM displays all of the columns in the Signaling Point Table except Internal ID, Instance ID, and Last Status Change. To display these columns, or to hide other columns, see the procedures in the “Modifying Node Table Column Settings” section on page 5-16.

The Signaling Point Table displays the following information about signaling points that are associated with the selected node:

• Internal ID—Internal ID of the signaling point. The internal ID is a unique ID for every event, link, linkset, node, and signaling point, assigned by SGM for its own internal use. It can also be useful when the TAC is debugging problems.

• Name—Name of the signaling point.

• Node—Name of the node associated with this signaling point.

• Instance ID—ID of the instance associated with the signaling point.

• Instance Name—Name of the instance associated with the signaling point.

• Point Code—Primary point code of the signaling point.

• Variant—SS7 protocol variant. Valid variants are:

– ANSI

– China

– ITU

• Network Indicator—Determines the type of call that is being placed. Valid values are:

– National—National-bound call. SGM routes national calls through the national network.

– NationalSpare—National-bound call, used in countries in which more than one carrier can share a point code. In those countries, networks are differentiated by the Network Indicator.


78-15589-01


– International—International-bound call. SGM forwards international-bound calls to an STP pair that acts as an international gateway.

– InternationalSpare—International-bound call, used in countries in which more than one carrier can share a point code. In those countries, networks are differentiated by the Network Indicator.

• Notes—Indicates whether there is a note associated with the signaling point.

• Events—Indicates whether there is a recent event associated with the signaling point. During Discovery, SGM might flag most signaling points with an event icon. If the event icons are too distracting, select Edit > Clear All Events from the SGM Main Menu to remove them.

• Last Status Change—Date and time that the status of the signaling point last changed.

• Status—Current status of the signaling point. Possible values are:

– Active (green ball)—The signaling point is currently fully functional.

– Unknown (red ball)—One of the following conditions occurred:

– SGM cannot poll the node associated with the signaling point. SGM sets all signaling points, linksets, and links associated with the node to Unknown.

– The signaling point has been unconfigured on the ITP, or the configuration is incomplete. At the next poll, SGM determines that the signaling point does not exist, and sets the signaling point and all associated linksets and links to Unknown.

– Unmanaged (gray ball)—An SGM user has set the signaling point to Unmanaged status, to prevent SGM from polling the signaling point. SGM automatically deletes all associated links and linksets.

– Warning (yellow ball)—The signaling point is active, but one or more associated links or linksets is in Failed, Unavailable, Unknown, or Warning status and is not flagged as Ignored.

• Status Reason—Reason for the current status of the signaling point. Possible values are:

– None

– SGM Restart



78-15589-01


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive




Signaling Points Tab: Linksets

To view information about the linksets that are associated with the selected node, select the Signaling Points tab. SGM displays the linksets in the top table, and the links in the bottom table.


78-15589-01





Linksets that are associated with nodes that are excluded from the current view are not displayed in the Linkset Table. See the “Creating a View” section on page 3-27 for more information about excluding nodes.

By default, SGM displays all of the columns in the Linkset Table except Internal ID, Congestion Links, and Last Status Change. To display these columns, or to hide other columns, see the procedures in the “Modifying Linkset Table Column Settings” section on page 5-18.

The Linkset Table displays the following information about linksets that are associated with the selected node:

• Internal ID—Internal ID of the linkset. The internal ID is a unique ID for every event, link, linkset, signaling point, and node, assigned by SGM for its own internal use. It can also be useful when the TAC is debugging problems.










78-15589-01







• Ignored—Indicates whether the linkset is to be included when aggregating and displaying SGM status information:

– Clear the checkbox to include the linkset. This is the default setting.

– Select the checkbox to exclude the linkset.


• Notes—Indicates whether there is a note associated with the linkset.


– To delete the event icon from SGM displays for a specific linkset, select the linkset and click the icon.

– To delete the event icon from SGM displays for all linksets, select Edit> Clear All Events from the SGM Main Menu.

Note During Discovery, SGM might flag most linksets with an event icon. If the event icons are too distracting, use the Edit> Clear All Events menu option to remove them.



78-15589-01









– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





78-15589-01



– Link Inactive




Signaling Points Tab: Links

To view information about the links that are associated with the selected node, select the Signaling Points tab. SGM displays the linksets in the top table, and the links in the bottom table.





The Link Table displays the following information about links that are associated with the selected node:




78-15589-01























78-15589-01




– To delete the event icon from SGM displays for all links, select Edit> Clear All Events from the SGM Main Menu.

Note During Discovery, SGM might flag most links with an event icon. If the event icons are too distracting, use the Edit> Clear All Events menu option to remove them.











78-15589-01









– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





78-15589-01



– Link Inactive





To view naming information for the selected node, select the Configuration Data tab.

The Naming Information sub-section displays the following information for the selected node:

• Display Name—Name of the node.

• IP Address or DNS Hostname—IP address or DNS name of the node, as discovered by SGM. However, if you modified your preferences to identify nodes by their IP addresses, then that is how the node is identified in this field. For more information, see the “Modifying Preference Settings” section on page 5-3.


• Icon Name—Name of the graphic icon to assign to this node in topology maps. SGM automatically assigns an appropriate icon to each discovered Cisco ITP, and to Unknown nodes, but you can use this field to assign a different icon.

When SGM discovers a single-instance node, it assigns the icon that corresponds to the node. When SGM discovers a multi-instance node, it assigns a separate icon for each unique signaling point instance.


78-15589-01


Valid values are:

– Cisco2600—Cisco 2650, Cisco 2650XM, Cisco 2651, Cisco 2651XM

– Cisco7204—Cisco 7204, Cisco 7204VXR


– Cisco7507—Cisco 7507, Cisco 7507mx, Cisco 7507z



– MSC—Mobile switching center. You can assign this icon to an unknown node if you know that it is an MSC.

– SCP—Service control point. You can assign this icon to an unknown node if you know that it is an SCP.

– SSP—Service switching point. You can assign this icon to an unknown node if you know that it is an SSP.

– STP—Signal transfer point. You can assign this icon to an unknown node if you know that it is an STP.

– SignalingPoint—An SCP, SSP, or STP, or an ITP instance.

– Unknown—SGM is unable to determine the node type.














78-15589-01



















78-15589-01





– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive




78-15589-01



Configuration Data Tab: Descriptive Information

To view descriptive information for the selected node, select the Configuration Data tab.

The Descriptive Information sub-section displays the following information for the selected node:

• MIB Level—MIB conformance level used by the ITP, such as ITP MB5.

Note ITP Version and MIB Level might not have a one-to-one correspondence, because multiple ITP versions can use the same MIB level if there are no changes to the MIBs between versions. For example, ITP versions 12.2(4)MB5 and 12.2(4)MB6 both use MIB level ITP MB5.

• ITP Version—Version of IOS that is installed on the ITP.

Configuration Data Tab: IP Addresses for SNMP

To view SNMP IP address information for the selected node, select the Configuration Data tab.

The IP Addresses for SNMP sub-section displays the following information for the selected node:

• IP Address—IP addresses associated with this node, including the primary SNMP address and all backup IP addresses, that are intended for SNMP.

• Last Regular Poll Time—Date and time of the last full poll of the node for ITP-related MIBs (as opposed to a demand poll for just one linkset’s worth of data).

If the IP address has never been polled, SGM displays the phrase Never Polled.

If there are no IP addresses defined for the node that are intended for SNMP, this field displays the phrase There are no other IP addresses defined for this node.


78-15589-01


Configuration Data Tab: IP Addresses Not for SNMP

To view non-SNMP IP address information for the selected node, select the Configuration Data tab.

The IP Addresses Not for SNMP sub-section displays the following information for the selected node:

• IP Address—IP addresses associated with this node that are not intended for SNMP.

If there are no IP addresses defined for the node that are not intended for SNMP, this field displays the phrase There are no other IP addresses defined for this node.

Configuration Data Tab: ITP Uptime Information

To view ITP uptime information for the selected node, select the Configuration Data tab.

The ITP Uptime Information sub-section displays the following information for the selected node:



Configuration Data Tab: Polling Information

To view polling information for the selected node, select the Configuration Data tab.

The Polling Information sub-section displays the following information for the selected node:

• First Discovered—Date and time that the node was first discovered by SGM.

• Last Poll IP Address—Last IP address that was polled for this node. For a non-ITP node, this field is left blank.

• Last Full Poll Time—Date and time of the last full poll of the node for ITP-related MIBs (as opposed to a demand poll for just one linkset’s worth of data). For a non-ITP node, this field is left blank.


78-15589-01


• Last SGM Poll Response (secs)—Time, in seconds, taken by this node to respond to the last SGM poll request. For a non-ITP node, this field is left blank.

• Avg. SGM Poll Response (secs)—Average time, in seconds, taken by this node to respond to SGM poll requests. For a non-ITP node, this field is left blank.

Notes Tab

To view notes for the selected node, select the Notes tab.


• Notes associated with the node.

• The date and time the notes associated with the node were last updated, or the phrase Not Set if there are no notes associated with the node.

• The phrase No Notes if there are no notes associated with the node.


78-15589-01


Recent Events Tab

To view information about all recent events associated with the node, select the Recent Events tab. SGM displays the Recent Events table for the node (Figure 3-25).

Figure 3-25 Recent Events Table for a Node






78-15589-01



The Recent Events table displays the following information for the selected node:


















78-15589-01






















78-15589-01





Syslog Tab

To view all messages in the ITP system log for the selected node, select the Syslog tab.

The Syslog table displays the following information for the selected node:



• Timestamp—Date and time of the syslog message from the ITP.

• Severity—Severity of the syslog message. Possible values are:

– Alert—Messages that require immediate action.

– Critical—Critical conditions.

– Debug—Debug messages, log FTP commands, and WWW URLs.

– Emergency—System unusable messages.

– Error—Error messages.

– Info—Information messages.

– Notice—Normal but significant conditions.

– Warning—Warning messages.

• Facility—Name of the facility that generated the syslog message, such as SYS, SNMP, CS7MTP3, or CS7PING.

• Name—Short text identifier for the message type. A facility name in conjunction with a message name uniquely identifies a syslog message type.

• Message—Text of the syslog message.


78-15589-01


CPU Processes Tab

To view CPU utilization information for the selected node, select the CPU Processes tab.

The CPU Processes table is not available if the node is in Discovery, Polling, Unknown, or Unmanaged status.

The CPU Processes table displays one CPU Utilization Percentage table for each active Route Switch Processor (RSP) CPU.

The CPU Utilization Processes table displays the following information for the selected node:



• PID—Process identifier.

• Name—Name of the process.

• Time Created—Total time since the process was created.

• Total Runtime—CPU time the process has used.

• Times Invoked—Number of times the process has been invoked.

• Average Runtime—Average CPU time for each process invocation.

• 5 Sec %—Average CPU utilization percentage for the node over the last 5 seconds.

• 1 Min %—Average CPU utilization percentage for the node over the last minute.

• 5 Min %—Average CPU utilization percentage for the node over the last 5 minutes.

• Priority—Process queue priority. Possible values are:

– Low

– Normal

– High

– Critical


78-15589-01


Trap Host Configuration

To view all trap settings for the selected node, as well as all hosts and port numbers to which the node sends traps, select the Trap Host Configuration tab.

If you have implemented SGM User-Based Access, this option is available to users with authentication level System Administrator (Level 5) and higher.

The Trap Host Configuration table displays the following information for the selected node:



• Release 2 Trap Settings—Indicates whether the following ITP release 12.2(4)MB4 trap settings are enabled:

– SCTP Remote Address Change

– Linkset State Change

– Link State Change

– Link Congestion State Change

– Link Receive Utilization Change

– Link Send Utilization Change

– Route State Change

– GTT MAP State Change

• Release 3 Trap Settings—Indicates whether the following ITP release 12.2(4)MB5 through 12.2(4)MB9a trap settings are enabled:

– ASP State Change

– AS State Change

– SGMP State Change

This column might not be displayed if the ITP does not support ITP release 12.2(4)MB5 through 12.2(4)MB9a traps.


78-15589-01








– Route Destination State Change

– Route Mgmt. State Change

– Route Table Load


– GTT Table Load

– ASP Congestion Change

– SGMP Congestion Change

This column might not be displayed if the ITP does not support ITP release 12.2(4)MB10 traps.

• IP Address—IP address of a host to which the node sends traps.

• Port—Port to which the node sends traps.

• Trap Version—Trap version sent to this IP address and port.

• Community String—SNMP community name used by the node for read access to the information maintained by the SNMP agent on the ITP.

Viewing CPU Statistics for a NodeSGM enables you to display the CPU utilization percentage for a node as a function of time. SGM displays one CPU Utilization Percentage chart for each active Route Switch Processor (RSP) CPU.

To display CPU Utilization Percentage charts for a node, right-click a node in a window, then select View> Real-Time Data and Charts from the right-click menu. (This option is available only if SGM can poll the node.) SGM displays the SGM Real-Time Statistics: CPU Statistics window (Figure 3-26).


78-15589-01


Figure 3-26 SGM Real-Time Statistics: CPU Statistics Window

The SGM Real-Time Statistics: CPU Statistics window displays the following information for the selected node:

• Node—Name of the node for which CPU statistics are being displayed. To see detailed information for the node, click the node name.

• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the CPU Utilization Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.

• Last Poll Error—Date and time the last polling error message was received by the node. If there have been no polling errors, SGM displays None.


78-15589-01


• CPU Utilization Chart—Displays the CPU utilization percentage for the node as a function of time.



– dd.dd is the CPU utilization percentage for that data point.







• Time Average—Displays three color-coded icons, one for each average calculation: 5 seconds, 1 minute, and 5 minutes.

To remove the data for a given average from the chart, click the icon in this field. To return the data to the chart, click the icon again.

• Reset—If you scrolled or zoomed the chart, resets the chart to the default view and scaling.

• Grid On—Superimposes a graphic grid on the chart. The grid can make the data easier to read.

• Grid Off—Removes the graphic grid from the chart.

• Close—Closes the SGM Real-Time Statistics: CPU Statistics window.

• Help—Displays online help for the current window.


78-15589-01


Editing a NodeSGM enables you to edit the following aspects of a node:

• Editing Node Properties, page 3-124

• Attaching a Note to a Node, page 3-126

• Editing SNMP IP Addresses for a Node, page 3-127

Editing Node Properties

To edit a node’s properties, such as its name, telnet address, or associated icon, right-click the node in a window, select Edit> Properties in the right-click menu. SGM displays the Edit Properties Dialog for a Node (Figure 3-27).

Figure 3-27 Edit Properties Dialog for a Node

By default, the Name field displays the node’s DNS name, as discovered by SGM. However, if you modified your preferences to identify nodes by their IP addresses, then that is how the node is identified in this field. For more information, see the “Modifying Preference Settings” section on page 5-3.

You can also use the Name field to specify a new, more meaningful name for the node, keeping in mind the following considerations:

• You can change an ITP node's name to a new name or IP address.

• A new name can be from 1 to 30 characters, and can contain any letters, numbers, or special characters, but no periods (.). If you enter a name that contains a period, SGM beeps and retains the current name.


78-15589-01


• A new IP address must use the x.x.x.x format, where x is between 0 and 255, and must contain only numbers and periods, but no letters or special characters. If you enter an IP address that contains any letters or special characters, SGM beeps and retains the current name.

• If you leave the Name field blank, SGM reverts to the node’s default name (the DNS name for an ITP node, the point code for a non-ITP node).

• The new node name is used when launching context-based applications, such as CiscoWorks2000. Therefore, if the new name you enter is not the node’s DNS name, and the application knows the node by its DNS name, context links into the application for that node might not work.

You can use the Telnet Address field to specify a new Telnet IP address and optional port number, to pass to the Telnet command. If you specify a port number, separate the IP address from the port number with a space, such as: sgm-sun8.cisco.com 2048

The Icon Name drop-down list box displays the name of the graphic icon to assign to this node in topology maps. SGM automatically assigns an appropriate icon to each discovered Cisco ITP, and to Unknown nodes, but you can use this field to assign a different icon (for example, if you know that a given Unknown node is a mobile switching center).


Valid values are:

• Cisco2600—Cisco 2650, Cisco 2650XM, Cisco 2651, Cisco 2651XM

• Cisco7204—Cisco 7204, Cisco 7204VXR


• Cisco7507—Cisco 7507, Cisco 7507mx, Cisco 7507z


• IPDevice—IP device, other than those listed above. You can assign this icon to an unknown node if you know that it is an IP device.

• MSC—Mobile switching center. You can assign this icon to an unknown node if you know that it is an MSC.

• SCP—Service control point. You can assign this icon to an unknown node if you know that it is an SCP.


78-15589-01


• SSP—Service switching point. You can assign this icon to an unknown node if you know that it is an SSP.

• STP—Signal transfer point. You can assign this icon to an unknown node if you know that it is an STP.

• SignalingPoint—An SCP, SSP, or STP, or an ITP instance.

• Unknown—SGM is unable to determine the node type.

At any time, you can click Cancel to exit the dialog without saving any changes.

When you are satisfied with your changes, click Save. SGM saves your changes and updates all SGM windows to reflect your changes.

Attaching a Note to a Node

To attach a note to a node, right-click the node in a window, then select Edit> Notes in the right-click menu. SGM displays the Edit Notes Dialog for a Node (Figure 3-28).

Figure 3-28 Edit Notes Dialog for a Node


78-15589-01


The Note Last Updated field displays the date and time the Notes field for this node was last updated. If there is no note currently associated with this node, this field displays the value Not Set.

In the Notes field, enter any important information about the node, such as a detailed description, its location, its service history, and so on. When you annotate a node, the topology map in the Topology window displays a note icon in the upper left corner of the node element.



Editing SNMP IP Addresses for a Node

SGM enables you to determine which IP addresses are to be used for SNMP polling.

To edit a node’s SNMP IP addresses, right-click an ITP node in a window, select Edit> SNMP IP Addresses in the right-click menu. SGM displays the Edit SNMP IP Addresses Dialog.

The IP Addresses for SNMP field lists all IP addresses associated with this ITP node that SGM can use for SNMP polling:

• By default, SGM places all discovered IP addresses in this list, in the order in which they are discovered. SGM uses the IP address at the top of the list as the primary SNMP address for the node.

During SNMP polling of the node (both status polling and demand polling), SGM first tries the primary SNMP address. If the primary is unavailable, SGM tries the other IP addresses, one-by-one, in descending order.

• To assign a new primary SNMP address, or to change the order of the secondary IP addresses, use the Raise Priority and Lower Priority buttons to move the IP addresses up and down in the list.


78-15589-01


• You can also select IP addresses that you do not want SGM to use for SNMP polling. This is useful, for example, to separate management traffic from SMS traffic. To remove an IP address from the list, click Remove. The IP address is removed from the IP Addresses for SNMP list and appears in the Available ITP IP Addresses list, and is no longer used by SGM for SNMP polling. The Available ITP IP Addresses field lists all P addresses associated with this ITP node that you do not want SGM to use for SNMP polling. SGM does not send SNMP queries to IP addresses in this list.

To enable an IP address for SNMP polling again, select the address in the Available ITP IP Addresses list and click Add. The IP address moves back into the IP Addresses for SNMP list and is again available for SNMP polling.

If you remove all IP addresses from the IP Addresses for SNMP list, the node is effectively removed from the network, and SGM automatically labels the node Unmanaged in all SGM windows.



Viewing Notes for a NodeSGM enables you to view the notes that have been attached to nodes.

To view a note, right-click a node in a window, then select View >Notes in the right-click menu. (The Notes option is grayed-out if there is no note associated with the selected node.) SGM displays the Notes for Node dialog (Figure 3-29).


78-15589-01


Figure 3-29 Notes for Node Dialog

The Notes for Node dialog displays the following information:

• The name of the node is displayed in the title of the window (for example, Notes for sgm-2600a.)

• Last Updated—Date and time the Notes field for the node was last updated.

• Notes—Notes associated with the node.

Click OK to close the Notes for Node dialog.


78-15589-01


Deleting a NodeAfter Discovery, the nodes in your network are known to SGM and added to the SGM database. Physically deleting nodes from your network is not the same as deleting them from the SGM database. The following sections describe the differences between deleting nodes from your network, from the SGM database, and from the SGM Discovery database, and the procedures for doing so:

• Deleting a Node from Your Network, page 3-130

• Deleting a Node from the SGM Database, page 3-130

• Deleting a Node from the SGM Discovery Database, page 3-132

Deleting a Node from Your Network

If you physically delete a known node from your network (for example, by powering down an ITP), it remains in the SGM database, SGM labels it Unknown, and it is the system administrator’s responsibility to delete it from the SGM database, if you choose to do so. SGM also labels all associated linksets and links Unknown because SGM attempts to poll the node and gets no response.

Deleting a Node from the SGM Database

Typically, you delete a node from the SGM database for one of the following reasons:

• You have physically deleted the node from your network. This is the most common reason for deleting a node from the SGM database.

• The node is Unknown or Unmanaged, you are aware of the reason, and you no longer want to see it in SGM displays. For example, the node might be a test lab device.

• If you delete all linksets to an Unmanaged node, SGM does not automatically delete the node. Instead, you must manually delete the node.

If you have physically deleted a known node from your network, and you then delete it from SGM, it is no longer in the SGM database, it does not appear in SGM windows, and it is not discovered when you run Discovery.


78-15589-01


Be aware of the following special situations:

• If you have not physically deleted a known node from your network, and you delete it from SGM, SGM removes the node from the poll list, and at the next poll SGM returns the node to the DEFAULT view, and labels the node as a new node if you are using a custom view.

• If a node has at least one adjacent node in Active, Discovering, Waiting, or Warning state, you cannot delete the node. If you try to do so, SGM cancels the deletion.

If either of these situations occurs, do not delete the node again. Instead, perform one of the following actions:

• Label the node Unmanaged. See the “Unmanaging and Managing a Node” section on page 3-133 for more details.

• Remove the node from your view. See the “Working with Views” section on page 3-26 for more details.

Note If you delete a node from the SGM database, the node is deleted for all SGM clients and views connected to that SGM server.

To delete a node from the SGM database, use one of the following procedures:

• Select one or more nodes in a window, then select Edit > Delete from the SGM Main Menu.

• Right-click a node in a window, then select Delete Item in the right-click menu. (You cannot delete more than one node at a time from the right-click menu.)


• Select Yes to delete the selected nodes. SGM deletes the nodes from the SGM database.

• Select No to return to the window without deleting any nodes from the SGM database.

You can also use the sgm delete node command to delete one or more nodes from the SGM database. See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of this command.


78-15589-01


Note If you delete a node, SGM removes it from the Nodes In Current View table of the Network View Editor window. If SGM then rediscovers the node, SGM places it in the New Nodes Found table of the Network View Editor window. To restore the node to your current view, you must move it into the Nodes In Current View table. For more information, see the “Working with Views” section on page 3-26.

Deleting a Node from the SGM Discovery Database

If you want to completely eliminate a given node from the SGM database, you can delete it from the SGM Discovery database, ensuring that it is never even discovered by SGM.

Note If you delete a node from the SGM Discovery database, the node is deleted for all SGM clients and views connected to that SGM server.

To delete a node from the SGM Discovery database:


Step 2 Select the Discovery tab. SGM displays the Discovery panel (Figure 3-4).

Step 3 In the Discovered Nodes table, select the node or nodes you want to delete.

Step 4 Click Delete Node. SGM deletes the nodes from the Discovery database, without asking for confirmation. The nodes will no longer be discovered by SGM.


78-15589-01


Unmanaging and Managing a NodeSGM enables you to label a node Unmanaged, and to remove the Unmanaged status from a node.

In some situations, you might not want to see a given node or nodes in SGM displays, but you might be unable to delete it from the SGM database. For example:

• If you have not physically deleted a known node from your network, and you delete it from SGM, SGM removes the node from the poll list, and at the next poll SGM returns the node to the DEFAULT view, and labels the node as a new node if you are using a custom view.

• If a node has at least one adjacent node in Active, Discovering, Waiting, or Warning state, you cannot delete the node. If you try to do so, SGM cancels the deletion.

If these situations, you can label the node Unmanaged. When you label a node Unmanaged, SGM removes the node from the poll list.

Note If you label a node Unmanaged, the node is Unmanaged for all SGM clients and views connected to that SGM server.

To label a node Unmanaged:

Step 1 Select a node in a window.

You cannot label a node Unmanaged if it has a Device Type of Unknown:

• If you select a node with a Device Type of Unknown, then this menu option is grayed-out and cannot be selected.

• If you select more than one node, and at least one of them has a Device Type of Unknown, then this menu option is grayed-out and cannot be selected.

Step 2 Select Edit > Unmanage from the SGM Main Menu, or Unmanage from the right-click menu. SGM labels the selected node Unmanaged and removes it from the poll list.


78-15589-01


You can also remove the Unmanaged status from a node, when you are ready to return the node to the SGM poll list. To remove the Unmanaged status from a node:

Step 1 Select a node in a window.

You cannot remove the Unmanaged status from a node with a Device Type of Unknown:

• If you select a node with a Device Type of Unknown, then this menu option is grayed-out and cannot be selected.

• If you select more than one node, and at least one of them has a Device Type of Unknown, then this menu option is grayed-out and cannot be selected.

Step 2 Select Edit > Manage from the SGM Main Menu, or Manage from the right-click menu. SGM removes the Unmanaged status from the selected node, returns it to the poll list, and polls it immediately.

Polling a NodeSGM automatically polls nodes at specified intervals. However, you can also request an immediate poll for a node.

To poll a node from the Discovery Dialog, use the following procedure:


Step 2 Select the Discovery tab. SGM displays the Discovery panel (Figure 3-5). The Discovered Nodes section of the Discovery panel lists all discovered nodes.

Step 3 Select one or more nodes. You cannot poll a node with a Primary SNMP Address of N/A:

• If you select a node with a Primary SNMP Address of N/A, then the Poll Node button is grayed-out and cannot be selected.

• If you select more than one node, and even one of them has a Primary SNMP Address of N/A, then the Poll Node button is grayed-out and cannot be selected.


78-15589-01


Step 4 Click Poll Node. SGM begins a poll of the selected nodes. During polling, the Poll Node button is grayed-out, the “Selected nodes are being polled” message is displayed at the bottom of the Discovery Dialog, and individual nodes might display the Polling status.

• If the node has only one IP address for SGM to poll, and the poll fails or times out, SGM issues an error message.

• If the node has more than one IP address for SGM to poll, and the polls of one or more IP addresses fail or time out, SGM issues warning messages. If all polls fail or time out, SGM issues an error message.

Step 5 When the “Selected nodes are being polled” message disappears and no nodes are in Polling status, polling is complete. The SGM database immediately reflects any new or changed data for the selected nodes.

To poll one or more nodes, retaining all currently known linksets in the SGM database, use one of the following procedures:

• Select one or more nodes in a window, then select Edit > Poll Nodes > Normal Poll in the SGM Main Menu. SGM polls all selected ITP nodes.

• Select one or more linksets in a window, then select Edit > Poll Nodes > Normal Poll in the SGM Main Menu. SGM polls all primary and adjacent ITP nodes associated with the selected linksets.

• Select an ITP node or adjacent node in the Details Window, then select Edit > Poll Nodes > Normal Poll in the SGM Main Menu. SGM polls that node.

• Select a linkset or link in the Details Window, then select Edit > Poll Nodes > Normal Poll in the SGM Main Menu. SGM polls the ITP node and adjacent node associated with the linkset or link.

• Right-click an ITP node in a window, then select Poll Node > Normal Poll in the right-click menu. SGM polls the node.

Normal Poll retains all linksets associated with polled nodes, even linksets that have been deleted and are therefore in Unknown status.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMWorking with Signaling Points

To poll one or more nodes, removing and then rediscovering all associated linksets, use one of the following procedures:

• Select one or more nodes in a window, then select Edit > Poll Nodes > Clean Poll in the SGM Main Menu. SGM polls all selected ITP nodes.

• Select one or more linksets in a window, then select Edit > Poll Nodes > Clean Poll in the SGM Main Menu. SGM polls all primary and adjacent ITP nodes associated with the selected linksets.

• Select an ITP node or adjacent node in the Details Window, then select Edit > Poll Nodes > Clean Poll in the SGM Main Menu. SGM polls that node.

• Select a linkset or link in the Details Window, then select Edit > Poll Nodes > Clean Poll in the SGM Main Menu. SGM polls the ITP node and adjacent node associated with the linkset or link.

• Right-click an ITP node in a window, then select Poll Node > Clean Poll in the right-click menu. SGM polls the node.

Clean Poll removes all associated linksets before polling the nodes.

Excluding a Node from a ViewTo exclude a node from the current view, right-click the node in a window, then select Exclude from View in the right-click menu. SGM excludes the node from the current view. See the “Creating a View” section on page 3-27 for more information about excluding nodes from views.

Working with Signaling PointsSGM enables you to view information about all discovered signaling points, including their associated nodes, status, and other important information.

Note In a multi-instance network, the signaling point name has the format pointcode:instanceName.

In a multi-instance network, SGM does not display signaling points that are only partly configured (that is, the variant and network name are configured, but not the primary point code).


78-15589-01



• Viewing Basic Information for Signaling Points, page 3-137

• Viewing Detailed Information for a Signaling Point, page 3-141

• Editing a Signaling Point, page 3-162

• Viewing Notes for a Signaling Point, page 3-166

• Deleting a Signaling Point, page 3-167

• Unmanaging and Managing a Signaling Point, page 3-169

• Excluding a Signaling Point from a View, page 3-170

Related Topics:







Viewing Basic Information for Signaling PointsTo view basic information for signaling points, select Signaling Points in the left pane of the SGM Main Window. SGM displays the Signaling Point Window (Figure 3-30).


78-15589-01


Figure 3-30 Signaling Point Window

The Signaling Point Window displays information about the signaling points that have been discovered by SGM.

By default, SGM displays all of the columns in the Signaling Point Window except Internal ID, Instance ID, and Last Status Change. To display these columns, or to hide other columns, see the procedures in the “Modifying Linkset Table Column Settings” section on page 5-18.





78-15589-01


The Signaling Point Window displays the following information for all discovered signaling points:

• Internal ID—Internal ID of the signaling point. The internal ID is a unique ID for every event, link, linkset, node, and signaling point, assigned by SGM for its own internal use. It can also be useful when the TAC is debugging problems.


• Node—Name of the node associated with this signaling point.





– ANSI

– China

– ITU






• Notes—Indicates whether there is a note associated with the signaling point.


78-15589-01


• Events—Indicates whether there is a recent event associated with the signaling point.

During Discovery, SGM might flag most signaling points with an event icon. If the event icons are too distracting, select Edit > Clear All Events from the SGM Main Menu to remove them.










– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device



78-15589-01


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive




Viewing Detailed Information for a Signaling PointSGM can display detailed information about a selected signaling point, including its associated linksets, links, status, and other information.

To display detailed information for a signaling point, use one of the following procedures:

• Select Signaling Points in the left pane of the SGM Main Window, right-click a signaling point in the right pane, then select View> Configuration Details in the right-click menu.

• Select the turner beside Signaling Points in the left pane of the SGM Main Window, then select a signaling point.


78-15589-01


SGM displays the Signaling Point Details Window (Figure 3-31).

Figure 3-31 Signaling Point Details Window

Updates for the signaling point that are received from the SGM server are reflected automatically in this window.

Changes you make in this window might not be reflected throughout SGM until the next poll (by default, every 15 seconds). For information about changing the polling interval, see the “Viewing Detailed Information for a Linkset” section on page 3-42.


Linksets Tab: Linksets

To view information about the linksets that are associated with the selected signaling point, select the Linksets tab. SGM displays the linksets in the top table, and the links in the bottom table.


78-15589-01





Linksets that are associated with nodes that are excluded from the current view are not displayed in the Linkset Table. See the “Creating a View” section on page 3-27 for more information about excluding nodes.

By default, SGM displays all of the columns in the Linkset Table except Internal ID, Congestion Links, and Last Status Change. To display these columns, or to hide other columns, see the procedures in the “Modifying Linkset Table Column Settings” section on page 5-18.

The Linkset Table displays the following information about linksets that are associated with the selected signaling point:

• Internal ID—Internal ID of the linkset. The internal ID is a unique ID for every event, link, linkset, signaling point, and node, assigned by SGM for its own internal use. It can also be useful when the TAC is debugging problems.










78-15589-01







• Ignored—Indicates whether the linkset is to be included when aggregating and displaying SGM status information:

– Clear the checkbox to include the linkset. This is the default setting.

– Select the checkbox to exclude the linkset.


• Notes—Indicates whether there is a note associated with the linkset.


– To delete the event icon from SGM displays for a specific linkset, select the linkset and click the icon.

– To delete the event icon from SGM displays for all linksets, select Edit > Clear All Events from the SGM Main Menu.

Note During Discovery, SGM might flag most linksets with an event icon. If the event icons are too distracting, use the Edit > Clear All Events menu option to remove them.






78-15589-01






– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive



78-15589-01




Linksets Tab: Links

To view information about the links that are associated with the selected signaling point, select the Linksets tab. SGM displays the linksets in the top table, and the links in the bottom table.





The Link Table displays the following information about links that are associated with the selected signaling point:







78-15589-01




















78-15589-01




– To delete the event icon from SGM displays for all links, select Edit > Clear All Events from the SGM Main Menu.

Note During Discovery, SGM might flag most links with an event icon. If the event icons are too distracting, use the Edit > Clear All Events menu option to remove them.











78-15589-01









– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





78-15589-01



– Link Inactive





To view naming information for the selected signaling point, select the Configuration Data tab.

The Naming Information sub-section displays the following information for the selected signaling point:




• Icon Name—Name of the graphic icon to assign to this signaling point in topology maps. SGM automatically assigns an appropriate icon to each discovered Cisco ITP, and to Unknown nodes, but you can use this field to assign a different icon.


Valid values are:

– Cisco2600—Cisco 2650, Cisco 2650XM, Cisco 2651, Cisco 2651XM





78-15589-01




– MSC—Mobile switching center. You can assign this icon to an unknown node if you know that it is an MSC.

– SCP—Service control point. You can assign this icon to an unknown node if you know that it is an SCP.

– SSP—Service switching point. You can assign this icon to an unknown node if you know that it is an SSP.

– STP—Signal transfer point. You can assign this icon to an unknown node if you know that it is an STP.

– SignalingPoint—An SCP, SSP, or STP, or an ITP instance.

– Unknown—SGM is unable to determine the node type.










78-15589-01



– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive





78-15589-01



To view descriptive information for the selected signaling point, select the Configuration Data tab.

The Description sub-section contains a description of the signaling point. If the signaling point has no description, this sub-section is blank.

Configuration Data Tab: Point Code

To view point code information for the selected signaling point, select the Configuration Data tab.

The Point Code sub-section displays the following information for the selected signaling point:



– ANSI

– China

– ITU






• Network Name—Name of the network associated with the signaling point.


78-15589-01


Configuration Data Tab: Capability Point Code

To view capability point code information for the selected signaling point, select the Configuration Data tab.

The Capability Point Code sub-section displays the following information for the selected signaling point:

• Point Code—Capability point code of the signaling point.


– ANSI

– China

– ITU






• Network Name—Name of the network associated with the signaling point.


78-15589-01


Configuration Data Tab: QoS Information

To view quality of service (QoS) information for the selected signaling point, select the Configuration Data tab.

The QoS Information sub-section displays the following information for the selected signaling point:

• QoS—Quality of service (QoS) class of the signaling point. Valid QoS classes range from 1 through 7. ALL indicates that the signaling point accepts all QoS classes.

• ToS—Type of service (ToS) of the signaling point.

• DSCP—IP differentiated-services-code-point (DSCP) of the signaling point.

Notes Tab

To view notes for the selected signaling point, select the Notes tab.


• Notes associated with the signaling point.

• The date and time the notes associated with the signaling point were last updated, or the phrase Not Set if there are no notes associated with the signaling point.

• The phrase No Notes if there are no notes associated with the signaling point.

Recent Events Tab

To view information about all recent events associated with the signaling point, select the Recent Events tab. SGM displays the Recent Events table for the signaling point (Figure 3-32).


78-15589-01


Figure 3-32 Recent Events Table for a Signaling Point







78-15589-01


The Recent Events table displays the following information for the selected signaling point:


















78-15589-01






















78-15589-01






To view information about all access lists associated with the selected signaling point, select the ITP Access Lists tab.

For each linkset associated with the selected signaling point, the ITP Access Lists section displays the following information:








Route Detail Tab

To view detailed information about routes associated with the selected signaling point, including dynamic and shadow routes, select the Route Detail tab.

The Route Detail table displays the following information for the selected signaling point:




78-15589-01


• Destination Point Code—Destination point code for packets on the selected signaling point. The destination point code is the point code to which a given packet is routed.

• Mask—Mask length for packets on the selected signaling point. The mask length is the number of significant leading bits in the point code. The mask length is always 14 for ITU and 24 for ANSI.

• Cost—Cost of the route to the destination, relative to other routes. The valid costs range from 1 (lowest cost and highest priority) through 9 (highest cost and lowest priority).

• Destination Linkset—Destination linkset associated with the destination point code. The destination linkset is also known as the output linkset.

• QoS—Quality of service (QoS) class of the route, as configured by the network administrator. Valid QoS classes range from 1 through 7; ALL indicates that the route accepts all QoS classes.

• Access—Status of the destination. Possible values are:

– Accessible

– Inaccessible

– Restricted

– Unknown

• Management Status—Accessibility of the destination from the adjacent point code at the remote end of the signaling point. Possible values are:

– Allowed—Traffic is allowed on the route without restriction.

– Prohibited—Traffic is prohibited on the route.

– Restricted—Traffic is restricted on the route.

– Unknown—Accessibility cannot be determined.

• Route Status—Status of the route. Possible values are:

– Available

– Restricted

– Unavailable


78-15589-01


GTT MAP Status Tab

To view detailed information about all GTT MAPs associated with the selected signaling point, select the GTT MAP Status tab.

The GTT MAP Status table displays the following information for the selected signaling point:



• Point Code—Primary point code for the GTT MAP.

• Subsystem Number—Primary subsystem number (SSN) for the GTT MAP.

• Point Code Status—Status of the primary point code. Possible values are:

– Allowed

– Prohibited—Either the point code cannot be reached, or the point code is labeled Prohibited by the SCCP protocol.

• Subsystem Number Status—Status of the primary SSN. Possible values are:

– Allowed

– Prohibited—Either the remote subsystem cannot be reached, or the subsystem is labeled Prohibited by the SCCP protocol.

• Congestion Level—MTP3 congestion level for the primary point code. Possible values are:

– No congestion—Corresponds to None. The link is not congested.

– Congestion level 1—Corresponds to Low. The link is slightly congested.

– Congestion level 2—Corresponds to High. The link is congested.

– Congestion level 3—Corresponds to Very High. The link is very congested.



78-15589-01


MTP3 Event Log Tab

To view the most recent MTP3 events associated with the selected signaling point, select the MTP3 Event Log tab.

The MTP3 Event Log table displays the following information for the selected signaling point:



• Logged Events—Total number of MTP3 events that have been logged for this signaling point.

• Dropped Events—Total number of MTP3 events that have been dropped for this signaling point.

• Max Events—Maximum number of events that the event history can contain. When event history table is full, the oldest entries are deleted as new entries are added.

• Allowed Events—ITP parameter that specifies the absolute maximum for the Max Events field. That is, for this ITP device, the Max Events field can range from 0 to the value specified by the Allowed Events field.

• Index—Event number, assigned to the event by SGM.

• Message—Message text for the event.

Editing a Signaling PointSGM enables you to edit the following aspects of a signaling point:

• Editing Signaling Point Properties, page 3-163

• Attaching a Note to a Signaling Point, page 3-165


78-15589-01


Editing Signaling Point Properties

To edit a signaling point’s properties, such as its name or associated icon, right-click the signaling point in a window, select Edit>Properties in the right-click menu. SGM displays the Edit Properties Dialog for a Signaling Point (Figure 3-33).

Figure 3-33 Edit Properties Dialog for a Signaling Point

By default, the Name field displays the signaling point’s point code and network name, as discovered by SGM (for example, 1.22.0:net0). However, you can use this field to specify a new, more meaningful name for the signaling point, keeping in mind the following considerations:

• The new name can be from 1 to 30 characters, and can contain any letters, numbers, or special characters. If you enter a name that is longer than 30 characters, SGM beeps and retains the current name.

• If you leave the Name field blank, SGM reverts to the signaling point’s point code, without the network name.

The Icon Name drop-down list box displays the name of the graphic icon to assign to this signaling point in topology maps. SGM automatically assigns an appropriate icon to each discovered Cisco ITP, and to Unknown signaling points, but you can use this field to assign a different icon (for example, if you know that a given Unknown signaling point is a mobile switching center).



78-15589-01


Valid values are:

• Cisco2600—Cisco 2650, Cisco 2650XM, Cisco 2651, Cisco 2651XM





• IPDevice—IP device, other than those listed above. You can assign this icon to an unknown signaling point if you know that it is an IP device.

• MSC—Mobile switching center. You can assign this icon to an unknown signaling point if you know that it is an MSC.

• SCP—Service control point. You can assign this icon to an unknown signaling point if you know that it is an SCP.

• SSP—Service switching point. You can assign this icon to an unknown signaling point if you know that it is an SSP.

• STP—Signal transfer point. You can assign this icon to an unknown signaling point if you know that it is an STP.

• SignalingPoint—An SCP, SSP, or STP, or an ITP instance.

• Unknown—SGM is unable to determine the signaling point type.




78-15589-01


Attaching a Note to a Signaling Point

To attach a note to a signaling point, right-click the signaling point in a window, then select Edit>Notes in the right-click menu. SGM displays the Edit Notes Dialog for a Signaling Point (Figure 3-34).

Figure 3-34 Edit Notes Dialog for a Signaling Point

The Note Last Updated field displays the date and time the Notes field for this signaling point was last updated. If there is no note currently associated with this signaling point, this field displays the value Not Set.

In the Notes field, enter any important information about the signaling point, such as a detailed description, its location, its service history, and so on. When you annotate a signaling point, the topology map in the Topology window displays a note icon in the upper left corner of the signaling point element.




78-15589-01


Viewing Notes for a Signaling PointSGM enables you to view the notes that have been attached to signaling points.

To view a note, right-click a signaling point in a window, then select View >Notes in the right-click menu. (The Notes option is grayed-out if there is no note associated with the selected signaling point.) SGM displays the Notes for Signaling Point dialog (Figure 3-35).

Figure 3-35 Notes for Signaling Point Dialog

The Notes for Signaling Point dialog displays the following information:

• The name of the signaling point is displayed in the title of the window (for example, Notes for 1.60.2:net2.)

• Last Updated—Date and time the Notes field for the signaling point was last updated.

• Notes—Notes associated with the signaling point.

Click OK to close the Notes for Signaling Point dialog.


78-15589-01


Deleting a Signaling PointAfter Discovery, the signaling points in your network are known to SGM and added to the SGM database. Physically deleting signaling points from your network is not the same as deleting them from the SGM database. The following sections describe the differences between deleting signaling points from your network and from the SGM database, and the procedures for doing so:

• Deleting a Signaling Point from Your Network, page 3-167

• Deleting a Signaling Point from the SGM Database, page 3-167

Deleting a Signaling Point from Your Network

If you physically delete a known signaling point from your network, it remains in the SGM database, SGM labels it Unknown, and it is the system administrator’s responsibility to delete it from the SGM database, if you choose to do so. SGM also labels all associated linksets and links Unknown because SGM attempts to poll the signaling point and gets no response.

Deleting a Signaling Point from the SGM Database

Typically, you delete a signaling point from the SGM database for one of the following reasons:

• You have physically deleted the signaling point from your network. This is the most common reason for deleting a signaling point from the SGM database.

• The signaling point is Unknown or Unmanaged, you are aware of the reason, and you no longer want to see it in SGM displays. For example, the signaling point might be a test lab device.

• If you delete all linksets to an Unmanaged signaling point, SGM does not automatically delete the signaling point. Instead, you must manually delete the signaling point.

If you have physically deleted a known signaling point from your network, and you then delete it from SGM, it is no longer in the SGM database, it does not appear in SGM windows, and it is not discovered when you run Discovery.


78-15589-01


Be aware of the following special situations:

• If you have not physically deleted a known signaling point from your network, and you delete it from SGM, SGM removes the signaling point from the poll list, and at the next poll SGM returns the signaling point to the DEFAULT view, and labels the signaling point as a new signaling point if you are using a custom view.

• If a signaling point has at least one adjacent signaling point in Active, Discovering, Waiting, or Warning state, you cannot delete the signaling point. If you try to do so, SGM cancels the deletion.

If either of these situations occurs, do not delete the signaling point again. Instead, perform one of the following actions:

• Label the signaling point Unmanaged. See the “Unmanaging and Managing a Signaling Point” section on page 3-169 for more details.

• Remove the signaling point from your view. See the “Working with Views” section on page 3-26 for more details.

Note If you delete a signaling point from the SGM database, the signaling point is deleted for all SGM clients and views connected to that SGM server.

To delete a signaling point from the SGM database, use one of the following procedures:

• Select one or more signaling points in a window, then select Edit> Delete from the SGM Main Menu.

• Right-click a signaling point in a window, then select Delete Item in the right-click menu. (You cannot delete more than one signaling point at a time from the right-click menu.)


• Select Yes to delete the selected signaling points. SGM deletes the signaling points from the SGM database.

• Select No to return to the window without deleting any signaling points from the SGM database.

You can also use the sgm delete sp command to delete one or more signaling points from the SGM database. See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of this command.


78-15589-01


Note If you delete a signaling point, SGM removes it from the Signaling Points In Current View table of the Network View Editor window. If SGM then rediscovers the signaling point, SGM places it in the New Signaling Points Found table of the Network View Editor window. To restore the signaling point to your current view, you must move it into the Signaling Points In Current View table. For more information, see the “Working with Views” section on page 3-26.

Unmanaging and Managing a Signaling PointSGM enables you to label a signaling point Unmanaged, and to remove the Unmanaged status from a signaling point.

In some situations, you might not want to see a given signaling point in SGM displays, but you might be unable to delete it from the SGM database. For example:

• If you have not physically deleted a known signaling point from your network, and you delete it from SGM, SGM removes the signaling point from the poll list, and at the next poll SGM returns the signaling point to the DEFAULT view, and labels the signaling point as a new signaling point if you are using a custom view.

• If a signaling point has at least one adjacent signaling point in Active or Warning state, you cannot delete the signaling point. If you try to do so, SGM cancels the deletion.

If these situations, you can label the signaling point Unmanaged. When you label a signaling point Unmanaged, SGM removes the signaling point from the poll list.

Note If you label a signaling point Unmanaged, the signaling point is Unmanaged for all SGM clients and views connected to that SGM server.

To label a signaling point Unmanaged, right-click a signaling point in a window, then select Unmanage from the right-click menu. SGM labels the selected signaling point Unmanaged and removes it from the poll list.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMWorking with Links

You can also remove the Unmanaged status from a signaling point, when you are ready to return the signaling point to the SGM poll list. To remove the Unmanaged status from a signaling point, right-click a signaling point in a window, then select Manage from the right-click menu. SGM removes the Unmanaged status from the selected signaling point, returns it to the poll list, and polls it immediately.

Excluding a Signaling Point from a ViewTo exclude a signaling point from the current view, right-click the signaling point in a window, then select Exclude from View in the right-click menu. SGM excludes the signaling point from the current view. See the “Creating a View” section on page 3-27 for more information about excluding signaling points from views.

Working with LinksSGM enables you to view detailed information about all discovered links, including their associated nodes, status, events, and other information.


• Viewing Basic Information for Links, page 3-171

• Viewing Detailed Information for a Link, page 3-175

• Viewing Real-Time Data for a Link, page 3-186

• Editing a Link, page 3-230

• Viewing Notes for a Link, page 3-232

• Deleting a Link, page 3-233

• Ignoring a Link, page 3-235

• Viewing Ignored Links, page 3-235

Related Topics:




78-15589-01





Viewing Basic Information for LinksTo view basic information for links, select Links in the left pane of the SGM Main Window. SGM displays the Link Window (Figure 3-36).

Figure 3-36 Link Window

The Link Window displays information about the links that have been discovered by SGM.

By default, SGM displays all of the columns in the link table except Internal ID, Congestion Level, and Last Status Change. To display these columns, or to hide other columns, see the procedures in the “Modifying Linkset Table Column Settings” section on page 5-18.



78-15589-01




The Link Window displays the following information:



















78-15589-01









– To delete the event icon from SGM displays for all links, select Edit > Clear All Events from the SGM Main Menu.

Note During Discovery, SGM might flag most links with an event icon. If the event icons are too distracting, use the Edit > Clear All Events menu option to remove them.










78-15589-01










– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





78-15589-01



– Link Inactive




Viewing Detailed Information for a LinkSGM can display detailed information about a selected link, including its associated node, status, and other information.

To display detailed information for a link, use one of the following procedures:

• Select Links in the left pane of the SGM Main Window, right-click a link in the right pane, then select View> Configuration Details in the right-click menu.

• Select the turner beside Links in the left pane of the SGM Main Window, then select a link.

SGM displays the Link Details Window (Figure 3-37).


78-15589-01


Figure 3-37 Link Details Window

Detailed information for links associated with the selected linkset is displayed in the left column, and for links associated with the adjacent linkset in the right column.

Updates for the links that are received from the SGM server are reflected automatically in this window.

Changes you make in this pane might not be reflected throughout SGM until the next poll (by default, every 15 seconds). For information about changing the polling interval, see the “Viewing Detailed Information for a Link” section on page 3-175.



78-15589-01



To view general information for the selected link, select the Configuration Data tab.

The General Information sub-section displays the following information for the selected link:






• Is Ignored—Indicates whether the link is Ignored (that is, whether the link is to be included when aggregating and displaying SGM status information).

• Association ID—For a link of type HSL, Serial, or Virtual, this field has a value of 0. For a link of type SCTP, the index into the SNMP SCTP association table.

Configuration Data Tab: Interface Information

To view interface information for the selected link, select the Configuration Data tab.

The Interface Information sub-section displays the following information for the selected link:

• QoS—(SCTP links only) Quality of service (QoS) class of the link.

• Local Port—(SCTP links only) Local port for the link.

• Remote Port—(SCTP links only) Remote port for the link.

• Interface Name—(HSL, Serial, and Virtual links only) Name of the interface.

• Interface Index—(HSL, Serial, and Virtual links only) Index into the SNMP interface table.


78-15589-01


Configuration Data Tab: Local IP Address Information (SCTP Links Only)

To view local IP address information for the selected SCTP link, select the Configuration Data tab.

The Local IP Address Information sub-section displays the following information for the selected link:

• IP Address—Local IP address associated with the link.

• Status—Current status of the IP address. Possible values are:

– Active (green ball)—The IP address is currently fully functional.

– Inactive (red ball)—The IP address is not currently functional.

Configuration Data Tab: Remote IP Address Information (SCTP Links Only)

To view remote IP address information for the selected SCTP link, select the Configuration Data tab.

The Remote IP Address Information sub-section displays the following information for the selected link:

• IP Address—Remote IP address associated with the link.

• Type—Indicates the designated primary IP address for the link (Primary) and the IP address currently being used by the link (Effective).

Usually, the same IP address is both Primary and Effective. However, if the primary IP address is down for some reason, a different IP address is used by the link and is labeled Effective.





78-15589-01


Configuration Data Tab: Configured Local IP Address Information (SCTP Links Only)

To view configured local IP address information for the selected SCTP link, select the Configuration Data tab.

The Configured Local IP Address Information sub-section displays the following information for the selected link:

• IP Address—Configured local IP address associated with the link.

• Interface Name—Primary IP address and interface name of the link. The primary IP address is the first CS7 local IP address configured in the ITP. For example, if the following IP addresses are configured in the ITP:

cs7 local-peer 4180local-ip 128.3.0.77local-ip 128.3.0.254

Then SGM uses 128.3.0.77 as the primary IP address. If at any time that IP address is deleted from the ITP configuration, or if a new IP address is added to the beginning of the list, SGM detects the change and automatically updates this field to reflect the new primary IP address.

If the link has no interface name, this field is blank.

Status Summary Tab: Status Information

To view status information for the selected link, select the Status Summary tab.

The Status Information sub-section displays the following information for the selected link:








78-15589-01


















• Receive Utilization—Indicates whether, on average, the link is under its configured receive utilization threshold (UnderThreshold) or over the threshold (OverThreshold).


78-15589-01


• Send Utilization—Indicates whether, on average, the link is under its configured send utilization threshold (UnderThreshold) or over the threshold (OverThreshold).


– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive




78-15589-01



Status Summary Tab: Local IP Address Information (SCTP Links Only)

To view local IP address information for the selected SCTP link, select the Status Summary tab.






Status Summary Tab: Remote IP Address Information (SCTP Links Only)

To view remote IP address information for the selected SCTP link, select the Status Summary tab.









78-15589-01


Notes Tab

To view notes for the selected link, select the Notes tab.


• Notes associated with the selected link in the left column.

• Notes associated with the adjacent link in the right column.

• The date and time the notes associated with each link were last updated, or the phrase Not Set if there are no notes associated with the link.

• The phrase No Notes if there are no notes associated with the link.

Recent Events Tab

To view information about all recent events associated with the link, select the Recent Events tab. SGM displays the Recent Events table for the link (Figure 3-38).

Figure 3-38 Recent Events Table for a Link



78-15589-01






The Recent Events table displays the following information for the selected link:















78-15589-01























78-15589-01







Viewing Real-Time Data for a LinkSGM enables you to display detailed statistics for a selected link. Detailed information for links associated with the selected linkset is displayed in the left column, and for links associated with the adjacent linkset in the right column.

To display detailed statistics for a link, select Links in the left pane of the SGM Main Window, right-click a link in the right pane, then select View >Real-Time Data and Charts in the right-click menu. SGM displays the Statistics Details Window for a Link (Figure 3-39).


78-15589-01


Figure 3-39 Statistics Details Window for a Link

Updates for the links that are received from the SGM server are reflected automatically in this window.

Changes you make in this window might not be reflected throughout SGM until the next poll (by default, every 15 seconds). For information about changing the polling interval, see the “Viewing Detailed Information for a Link” section on page 3-175.


78-15589-01


Note Each link is identified by its signaling link code ID (SLC). An asterisk indicates that a link is not configured, or that a poll could not get data for the link. For example, SLC (*)3 means there is no link associated with the selected linkset for SLC 3, and SLC 3(*) means there is no link associated with the adjacent linkset for SLC 3.

Select one of the SLCs. SGM displays the Statistics Details Window for a Link for that link.



To view general information for the selected link, select the Configuration Data tab.

The General Information sub-section displays the following information for the selected link:






• Is Ignored—Indicates whether the link is Ignored (that is, whether the link is to be included when aggregating and displaying SGM status information).

• Association ID—For a link of type HSL, Serial, or Virtual, this field has a value of 0. For a link of type SCTP, the index into the SNMP SCTP association table.


78-15589-01


Configuration Data Tab: Interface Information

To view interface information for the selected link, select the Configuration Data tab.

The Interface Information sub-section displays the following information for the selected link:

• QoS—(SCTP links only) Quality of service (QoS) class of the link.

• Local Port—(SCTP links only) Local port for the link.

• Remote Port—(SCTP links only) Remote port for the link.

• Interface Name—(HSL, Serial, and Virtual links only) Name of the interface.

• Interface Index—(HSL, Serial, and Virtual links only) Index into the SNMP interface table.

Configuration Data Tab: Local IP Address Information (SCTP Links Only)

To view local IP address information for the selected SCTP link, select the Configuration Data tab.







78-15589-01


Configuration Data Tab: Remote IP Address Information (SCTP Links Only)

To view remote IP address information for the selected SCTP link, select the Configuration Data tab.








Configuration Data Tab: Configured Local IP Address Information (SCTP Links Only)

To view configured local IP address information for the selected SCTP link, select the Configuration Data tab.

The Configured Local IP Address Information sub-section displays the following information for the selected link:

• IP Address—Configured local IP address associated with the link.






78-15589-01


Status Summary Tab: Status Information

To view status information for the selected link, select the Status Summary tab.


















78-15589-01









• Receive Utilization—Indicates whether, on average, the link is under its configured receive utilization threshold (UnderThreshold) or over the threshold (OverThreshold).

• Send Utilization—Indicates whether, on average, the link is under its configured send utilization threshold (UnderThreshold) or over the threshold (OverThreshold).


– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested



78-15589-01





– Link Inactive




Status Summary Tab: Local IP Address Information (SCTP Links Only)

To view local IP address information for the selected SCTP link, select the Status Summary tab.







78-15589-01


Status Summary Tab: Remote IP Address Information (SCTP Links Only)

To view remote IP address information for the selected SCTP link, select the Status Summary tab.








Notes Tab

To view notes for the selected link, select the Notes tab.


• Notes associated with the selected link in the left column.

• Notes associated with the adjacent link in the right column.

• The date and time the notes associated with each link were last updated, or the phrase Not Set if there are no notes associated with the link.

• The phrase No Notes if there are no notes associated with the link.

Recent Events Tab

To view information about all recent events associated with the link, select the Recent Events tab. SGM displays the Recent Events table for the link (Figure 3-38).




78-15589-01





The Recent Events table displays the following information for the selected link:
















78-15589-01























78-15589-01






Status Details Tab

To view detailed status information for the selected link, select the Status Details tab.

The Status Details section displays the following information for the selected link:

• Protocol State Details—Detailed information about the state of the protocol for this link. Possible values are:

– Changeback control(TCBC): Changeback control is buffering data on this link

– Changeover control(TCOC): Changeover control is buffering data on this link

– Link availability control(TLAC): Adjacent Signalling point is restarting

– Link availability control(TLAC): Emergency changeover is in progress on this link

– Link availability control(TLAC): Changeback is in progress on this link

– Link availability control(TLAC): Changeover is in progress on this link

– Link availability control(TLAC): The last changeover operation failed on this link

– Link availability control(TLAC): Inhibit command will be retried

– Link availability control(TLAC): Management request in progress for this link

– Link availability control(TLAC): Signalling point is in the process of a restart

– Signalling routing control(TSRC): Changeover request is complete


78-15589-01


– Signalling routing control(TSRC): Adjacent Signalling Point is restarting

– Link availability control(TLAC): Link has been inhibited by a local management operation

– Link availability control(TLAC): LInk has been inhibited by a remote management operation

– Link availability control(TLAC): Link is blocked because of a local processor outage

– Link availability control(TLAC): Link is blocked because of a remote processor outage

• Link Test Results—Indicates the results of the link test. Possible results are:

– No Errors—The link did not detect any errors.

– Undefined OPC (Origination Point Code)—A signaling link test message was received with an undefined OPC. This can occur when a serial link is connected incorrectly, or when an SCTP link is configured incorrectly. This differs from Incorrect OPC because the signaling point is unaware of the point code in question. The point code is not defined for any linkset on this ITP.

– Incorrect OPC (Origination Point Code)—A signaling link test message was received with an incorrect OPC. This can occur when a serial link is connected incorrectly, or when an SCTP link is configured incorrectly. This differs from Undefined OPC because the signaling point is aware of the point code in question, and the point code is defined for a linkset on this ITP, but the point code is not correct for the current linkset.

– Undefined SLC (Signaling Link Code)—A signaling link test message was received with an undefined SLC. This can occur when a serial link is connected incorrectly, or when an SCTP link is configured incorrectly. The link is connected to the correct linkset, but the linkset does not have a definition for the SLC in question.

– Incorrect SLC (Signaling Link Code)—A signaling link test message was received with an incorrect SLC. This can occur when a serial link is connected incorrectly, or when an SCTP link is configured incorrectly. The link is connected to the correct linkset, but to the wrong link within that linkset. That is, the signaling test receives the test packet on the wrong link.


78-15589-01


– Incorrect NI (Network Indicator)—A signaling link test message was received with an incorrect NI. This can occur when links are connected to the correct linkset and link, but the NIs of the two adjacent point codes are not the same.

– Bad Pattern—A signaling link test message was received with an incorrect test pattern. This error occurs because the test pattern is corrupt. This usually indicates a hardware or configuration issue related to the physical format of the data on the links, caused by a variant mismatch or incorrect definitions on the physical link.

– Non Adjacent—Received a signaling link test message from a non-adjacent node.

– Failed—Unable to run the test, or no response was received within the specified interval.

• Link Fail Reason—If the link failed the link test, indicates the reason for the failure. Possible reasons are:

– None—No additional reason available.

– Changeover in progress—Changeover is in progress. This message is used to divert traffic away from a failed link.

– Management disconnect request—An MTP3 sent a request to stop the link.

– Link alignment lost—Link alignment is lost.

A link is in alignment when signal units are received in sequence, and with the proper number of octets. The signal unit must be a total length of eight-bit multiples. If the signal unit is not of eight-bit multiples, or if the signaling information field (SIF) exceeds the 272-octet capacity, the signaling unit is considered to be in error. If excessive errors are encountered on a link, it is considered to be out of alignment.

For M2PA links, this state reason is generated when the M2PA alignment timer T1 expires. This could indicate that the remote link is shutdown, or that there are intermittent IP connectivity problems.

– Link connection lost—Link connection is lost.

– Local Disconnect—A request to disconnect the link has been received, but the link is already disconnected.

– Remote Disconnect—A remote disconnect request has been received.


78-15589-01


– Signal unit error rate monitor failure—The signal unit error rate monitor has failed.

– T1 timeout no FISU received—A T1 timeout no FISU has been received. This timer avoids message mis-sequencing during changeover.

– T2 timeout no SIO received—A T2 timeout no SIO has been received. This timer waits for a changeover acknowledgment.

– T3 timeout no SIN received—A T3 timeout no SIN has been received. This timer controls diversion-delay to avoid mis-sequencing on changeback.

– T6 timeout excessive congestion—A T6 timeout excessive congestion has been received. This timer avoids message mis-sequencing on controlled rerouting.

– T7 timeout excessive acknowledgement delay—A T7 timeout excessive acknowledgment delay has been received. The T7 timer prevents a signaling point from waiting too long for a positive or negative acknowledgment. Usually, an acknowledgment is sent when a signaling point becomes idle and does not have any more traffic to transmit. When congestion occurs at a signaling point, or an extreme amount of traffic is present, it is possible that T7 could time out and force retransmission of messages.

– Link proving failure—A link proving failure occurred.

– Abnormal BSN received—An abnormal Backward Sequence Number (BSN) has been received.

– Abnormal FIB received—An abnormal Forward Indicator Bit (FIB) has been received.

– Abnormal SIB received—An abnormal Status Indicator Busy (SIB) has been received.

– Abnormal LSSU received—An abnormal Link Status Signal Unit (LSSU) has been received.

– Peer not ready—An MTP3 tried to bring up a link that is still cleaning up after being stopped. In some cases, the MTP3 does not changeover after a link failure, so the M2PA/SCTP waits for an event that will not occur. When an MTP3 tries to bring up the link again, the previous control structures have to be cleaned up first. If M2PA gets a start request from an MTP3, and the previous structures are still being held, M2PA


78-15589-01


cleans them up and sends a “PEER NOT READY” to the MTP3. A subsequent request to start the link from the MTP3 will then cause the link to come up.

– Communication lost—M2PA/SCTP has determined that the remote end signaling point is no longer reachable. Possible reasons include:

– The maximum number of consecutive retries of a packet has been reached.

– In the absence of data, SGM failed to receive heartbeat ACKs in response to heartbeats, for the maximum number of retries.

– No Listen posted—An MTP3 tried to start a link, but the local-peer port associated with the link is not available, probably because of a bad configuration.

– Unable to allocate buffer—M2PA/SCTP cannot get buffers for sending or receiving packets. Buffer problems can be temporary or permanent. Temporary buffer problems will generally clear with little side effects. Permanent buffer problems can lead to failed linksets or links.

– Link card removed—A link card has been removed.

– Link card inserted—A link card has been inserted.

– False link congestion—A false link congestion indication has been received.

– Configuration downloading—The configuration is downloading.

Statistics Tab: Packet Information

To view packet information for the selected link, select the Statistics tab.

The Packet Information sub-section displays the following information for the selected link:

• Sent Per Sec—Number of packets sent by the link per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Received Per Sec—Number of packets received by the link per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Drops—Total number of packets that have been dropped by the link.


78-15589-01


• Transmit Queue Depth—Number of packets waiting to be sent on by the link.

• Transmit Queue High Depth—Highest level reached by the transmit queue since the last reboot of the ITP, or since ITP last reset the averages as a result of bad data.

• Transmit Queue High Reset—Level at which the link is to reset the transmit queue. If the link is never to reset the transmit queue, this field displays Never.

• Signal Link Test—Indicates whether test packets are being sent on the link. Valid values are:

– true (1)—Test packets are being sent.

– false (2)—Test packets are not being sent.

Statistics Tab: Bit Information or Byte Information

To view bit information for the selected link (or byte information, if you cleared the Show Details in Bits Instead of Bytes checkbox in the Preferences Window), select the Statistics tab.

The Bit Information or Byte Information sub-section displays the following information for the selected link:

• Sent Per Sec—Number of bits or bytes (as set in the Preferences window) sent by the link per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Received Per Sec—Number of bits or bytes (as set in the Preferences window) received by the link per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.


78-15589-01


Statistics Tab: LSSU Information

To view Links Status Signal Unit (LSSU) information for the selected link, select the Statistics tab.

The LSSU Information sub-section displays the following information for the selected link:

• LSSU Packets Sent—Total number of LSSU packets sent by the link.

• LSSU Packets Received—Total number of SS7 Message Transfer Part Layer 2 (MTP2) LSSU packets received by the link.

Statistics Tab: Utilization Information

To view utilization information for the selected link, select the Statistics tab.

The Utilization Information sub-section displays the following information for the selected link:

• Send Plan Capacity—Planned capacity of the link to send, in bits per second.

– For a link of type Serial or HSL, available bandwidth for the link.

– For a link of type SCTPIP, set on the ITP using the plan-capacity CS7 link configuration command.

If Send Plan Capacity is not set on the ITP for this link, this field displays the value 0.

– For a link of type Other, this field always displays the value 0.

• Send Utilization—Amount of the link’s send capacity being used, as a percentage or in Erlangs (as set in the Preferences window), calculated using the following formula:

Send Utilization = (Bits Sent Per Sec)/Planned Capacity


– For a link of type SCTPIP or Mixed, if Send Plan Capacity is not set on the ITP for this link, this field displays the phrase Set Plan Capacity on ITP.

– For a link of type Other, this field always displays the phrase Set Plan Capacity on ITP.


78-15589-01


• Send Threshold %—Indicates when a cItpSpLinkSentUtilChange is to be generated for the link, as a percent of its total send capacity. For example, if Send Plan Capacity is 64000 bits per second, and Send Threshold % is 50, then a cItpSpLinkSentUtilChange notification is generated when the link reaches 50% of 64000, or 32000 bits per second.

• Receive Plan Capacity—Planned capacity of the link to receive, in bits per second.


– For a link of type SCTPIP, set on the ITP using the plan-capacity CS7 link configuration command.

If Receive Plan Capacity is not set on the ITP for this link, this field displays the value 0.


• Receive Utilization—Amount of the link’s receive capacity being used, as a percentage or in Erlangs (as set in the Preferences window), calculated using the following formula:

Receive Utilization = (Bits Received Per Sec)/Receive Plan Capacity


– For a link of type SCTPIP or Mixed, if Receive Plan Capacity is not set on the ITP for this link, this field displays the phrase Set Plan Capacity on ITP.

– For a link of type Other, this field always displays the phrase Set Plan Capacity on ITP.

• Receive Threshold %—Indicates when a cItpSpLinkRcvdUtilChange is to be generated for the link, as a percent of its total receive capacity. For example, if Receive Plan Capacity is 64000 bits per second, and Receive Threshold % is 50, then a cItpSpLinkRcvdUtilChange notification is generated when the link reaches 50% of 64000, or 32000 bits per second.


78-15589-01


Statistics Tab: Service Information

To view service information for the selected link, select the Statistics tab.

The Service Information sub-section displays the following information for the selected link:

• Duration In Service %—Percentage of time the link has been in service since the last reboot of the ITP, or since ITP last reset the counters.

• Duration Out Of Service %—Percentage of time the link has been out of service since the last reboot of the ITP, or since ITP last reset the counters.

Q.752 Measurements Tab: Error Information

To view Q.752 error information for the selected link, select the Q.752 Measurements tab.

The Error Information sub-section displays the following information for the selected link:

• Link Failure Count—Number of times the link was unavailable for signaling.

• Alignment Error Count—Number of errors detected during link alignment. Link alignment takes place at start up, or when trying to bring up a failed link.

• Negative ACKs Count—Number of errors detected during link acknowledgement.

Q.752 Measurements Tab: Inhibited Information

To view Q.752 inhibited information for the selected link, select the Q.752 Measurements tab.

The Inhibited Information sub-section displays the following information for the selected link:

• Local Inhibit Onset—Number of times a local ITP administrator has inhibited the link (that is, set the link to prevent traffic from flowing).

• Local Inhibit Duration—Total time the link has been locally inhibited.

• Remote Inhibit Onset—Number of times a remote ITP administrator has inhibited the link.

• Remote Inhibit Duration—Total time the link has been remotely inhibited.


78-15589-01


Q.752 Measurements Tab: Retransmitted Information

To view Q.752 retransmitted information for the selected link, select the Q.752 Measurements tab.

The Retransmitted Information sub-section displays the following information for the selected link:

• Packet Retransmitted Count—Number of packets retransmitted by the link.

• Byte Retransmitted Count—Number of bytes retransmitted by the link.

Q.752 Measurements Tab: Congested Information

To view Q.752 congested information for the selected link, select the Q.752 Measurements tab.

The Congested Information sub-section displays the following information for the selected link:

• Congestion Occurrences—Number of times congestion has occurred on the link.

• Congestion Duration—Total time the link has been congested.

• Congestion Level—Level of congestion: 1, 2, or 3.

• Packets Lost—Number of packets lost by the link as a result of congestion at each level.

• Times At Level With Packet Loss—Number of times the link has been congested and has lost packets at each level.

Interface Details Tab: Configuration Information

To view detailed interface configuration information for the selected link, select the Interface Details tab.

The Configuration Information sub-section displays the following information for the selected link:

• Type—Type of interface, such as Ethernet.

• MTU—Size, in bytes, of the largest datagram that can be sent or received on the interface.

• Speed (Bits/Sec)—Estimate, in bits per second, of the interface's current bandwidth. If the interface does not vary in bandwidth, or if no accurate estimate can be made, this field displays the nominal bandwidth.


78-15589-01


• IP Address—(SCTP links only) IP address corresponding to the media-dependent “physical” address. If the interface does not have such an address (for example, a serial line), this field displays N/A.

• IP Mask—(SCTP links only) Subnet mask corresponding to the media-dependent “physical” address. If the interface does not have such an address (for example, a serial line), this field displays N/A.

• Physical Address—(SCTP links only) Address of the interface at the protocol layer immediately “below” the network layer in the protocol stack. If the interface does not have such an address (for example, a serial line), this field displays N/A.

Interface Details Tab: Status Information

To view detailed interface status information for the selected link, select the Interface Details tab.


• ITP Uptime—Time the link has been up, in weeks, days, hours, minutes, and seconds.

• Admin Status—Desired state of the interface. Possible values are:

– Up

– Down

– Testing

• Operational Status—Current operational state of the interface. Possible values are:

– Up

– Down

– Testing

– Unknown

– Dormant


78-15589-01


• Line Protocol Status—Current state of the line protocol. Possible values are:

– Up—Software processes that handle the line protocol consider the line to be usable (that is, keepalives are successful).

– Down—Software processes that handle the line protocol consider the line to be unusable.

You can use the Line Protocol together with Operational Status to troubleshoot interface connection problems. For example, if Operational Status is Up, but Line Protocol is Down, the interface has detected a carrier on the physical layer, but there might be clocking or framing problems.

Interface Details Tab: Statistics Information

To view detailed interface statistics information for the selected link, select the Interface Details tab.

The Statistics Information sub-section displays the following information for the selected link:

• Bytes In per Sec—Number of bytes received on the interface per second, including framing characters.

• Bytes Out per Sec—Number of bytes sent on the interface per second, including framing characters.

• Packets In per Sec—Number of packets delivered per second to a higher-layer protocol.

• Packets Out per Sec—Total number of packets that higher-level protocols requested to be sent to the network per second, including those that were discarded or not sent.


78-15589-01


Interface Details Tab: Errors Information

To view detailed interface errors information for the selected link, select the Interface Details tab.

The Errors Information sub-section displays the following information for the selected link:

• In Discards—Number of inbound packets that were discarded, even though no errors were detected to prevent their delivery to a higher-layer protocol. For example, a packet might be discarded to free buffer space.

• Out Discards—Number of outbound packets that were discarded, even though no errors were detected to prevent their delivery to a higher-layer protocol. For example, a packet might be discarded to free buffer space.

• In Errors—Number of inbound packets that contained errors that prevented their delivery to a higher-layer protocol.

• Out Errors—Number of outbound packets that were not sent because of errors.

M2PA Peer Config Details Tab: Configuration Information (SCTP Links Only)

To view detailed M2PA peer configuration information for the selected SCTP link, select the M2PA Peer Config Details tab.

The Configuration Information sub-section displays the following information for the selected link:

• Status—Current status of the SCTP association. Possible values are:

– Closed

– CookieWait

– CookieEchoed

– DeleteTCB

– Established

– ShutdownAckSent

– ShutdownPending

– ShutdownReceived

– ShutdownSent

For detailed information about each status, refer to RFC 2960, Stream Control Transmission Protocol.


78-15589-01


• Uptime—Time the link has been up, in weeks, days, hours, minutes, and seconds.

• Remote Port—Remote port number for the SCTP association.

• Local Port—Local port number for the SCTP association.

• Primary IP Address—Designated primary IP address for the SCTP association.

• Effective IP Address—IP address currently being used by the SCTP association.

M2PA Peer Config Details Tab: Local IP Address Information (SCTP Links Only)

To view detailed M2PA peer local IP address information for the selected SCTP link, select the M2PA Peer Config Details tab.


• IP Address—Local IP addresses associated with the link.

• Uptime—Time each local IP address associated with the link has been up, in weeks, days, hours, minutes, and seconds.

M2PA Peer Config Details Tab: Remote IP Address Information (SCTP Links Only)

To view detailed M2PA peer remote IP address information for the selected SCTP link, select the M2PA Peer Config Details tab.


• IP Address—Remote IP addresses associated with the link.

• Uptime—Time each remote IP address associated with the link has been up, in weeks, days, hours, minutes, and seconds.

• Retry Timeout (msecs)—Time, in milliseconds, that SGM waits between attempts to connect to the remote IP address.

• Maximum Retries—Maximum number of times SGM will attempt to connect to the remote IP address.

• Retries—Number of times SGM has attempted to connect to the remote IP address.


78-15589-01


M2PA Peer Config Details Tab: Transmission Configuration Information

To view detailed M2PA peer transmission configuration information for the selected link, select the M2PA Peer Config Details tab.

The Transmission Configuration Information sub-section displays the following information for the selected link:

• MTU—Maximum transmission unit (MTU) size to be used by this SCTP association. This is the smallest MTU size supported by any of the IP addresses used by the SCTP association.

• In Streams—Inbound streams as negotiated when the SCTP association was started.

• Out Streams—Outbound streams as negotiated when the SCTP association was started.

• Maximum Retries—Maximum number of data retransmissions in the SCTP association context.

• Local Receive Window Size—Current local receive window size for this SCTP association.

• Remote Receive Window Size—Current local send window size for this SCTP association.

• Initial Retry Timeout (msecs)—Initial timeout value, in milliseconds, permitted by the SCTP implementation for the retry timeout.

• Minimum Retry Timeout (msecs)—Minimum timeout value, in milliseconds, permitted by the SCTP implementation for the retry timeout.

• Maximum Retry Timeout (msecs)—Maximum timeout value, in milliseconds, permitted by the SCTP implementation for the retry timeout.

• Bundle Chunks—Indicates whether the SCTP protocol allows chunks to be bundled into a single datagram. Valid values are:

– true (1)—Chunks are bundled.

– false (2)—Chunks are not bundled.

• Bundle Timeout (msecs)—Time, in milliseconds, to wait to allow data chunks to accumulate so that they can be transmitted in the same datagram.


78-15589-01


M2PA Peer Stats Details Tab: Remote IP Address Information (SCTP Links Only)

To view detailed M2PA peer remote IP address statistics information for the selected SCTP link, select the M2PA Peer Stats Details tab.


• IP Address—Remote IP addresses associated with the link.

• Smoothed Round Trip Time (msecs)—Average, in milliseconds, of all round-trip times between the local and remote systems on an IP network.

• Failure Count—Number of times the remote IP address was marked as failed.

• Heartbeat Status—Current status of the heartbeat associated with the remote IP address. Valid values are Active and Inactive.

• IP Status—Current status of the remote IP address. Valid values are Active and Inactive.

M2PA Peer Stats Details Tab: Statistics Information (per sec) Rates

To view detailed M2PA peer statistics information for the selected link, select the M2PA Peer Stats Details tab.

The Statistics Information (per sec) Rates sub-section displays the following information for the selected link:

• Packets Sent—Number of IP datagrams sent per second by this SCTP association.

• Packets Received—Number of IP datagrams received per second by this SCTP association.

• Control Chunks Sent—Number of control chunks sent per second by this SCTP association.

• Control Chunks Received—Number of control chunks received per second by this SCTP association.

• Ordered Chunks Sent—Number of ordered chunks sent per second by this SCTP association.

• Ordered Chunks Received—Number of ordered chunks received per second by this SCTP association.

• Unordered Chunks Sent—Number of unordered chunks sent per second by this SCTP association.


78-15589-01


• Unordered Chunks Received—Number of unordered chunks received per second by this SCTP association.

• Retransmitted Chunks—Number of chunks retransmitted per second by this SCTP association.

• Retransmitted Fast Chunks—Number of fast chunks retransmitted per second by this SCTP association.

Charts Tab: ReceivedUtilization

To view real-time ReceivedUtilization information for the selected link, select the Charts tab. SGM displays the ReceivedUtilization chart (Figure 3-40).

Figure 3-40 ReceivedUtilization Chart for a Link


78-15589-01


The ReceivedUtilization chart displays the following information for the selected link:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Received Utilization Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.

• Received Utilization Chart—Displays the Receive Utilization % for the link as a function of time, as well as the average Receive Utilization % for all links on the linkset.



– dd.dd is the receive utilization percentage for that data point.









78-15589-01



– One for each link (SLC) in the Received Utilization Chart, up to 16 total links.







78-15589-01


Charts Tab: SendUtilization

To view real-time SendUtilization information for the selected link, select the Charts tab. SGM displays the SendUtilization chart (Figure 3-41).

Figure 3-41 SendUtilization Chart for a Link


78-15589-01


The SendUtilization chart displays the following information for the selected link:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Send Utilization Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.

• Send Utilization Chart—Displays the Send Utilization % for the link as a function of time, as well as the average Send Utilization % for all links on the linkset.



– dd.dd is the send utilization percentage for that data point.









78-15589-01



– One for each link (SLC) in the Send Utilization Chart, up to 16 total links.






Charts Tab: PktsRcvdPerSec

To view real-time packets-received-per-second information for the selected link, select the Charts tab. SGM displays the PktsRcvdPerSec chart (Figure 3-42).


78-15589-01


Figure 3-42 PktsRcvdPerSec Chart for a Link

The PktsRcvdPerSec chart displays the following information for the selected link:

SGM displays the following information in the PktsRcvdPerSec chart:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Packets Received Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.


78-15589-01


• Packets Received Chart—Displays the Packets Received Per Sec for the link as a function of time.



– dd.dd is the number of packets received per second for that data point.








• SLC—Displays up to 16 color-coded icons, one for each link (SLC) in the Packets Received Chart. To remove the data for a link from the chart, click the icon in this field. To return the data to the chart, click the icon again.




Charts Tab: PktsSentPerSec

To view real-time packets-sent-per-second information for the selected link, select the Charts tab. SGM displays the PktsSentPerSec chart (Figure 3-43).


78-15589-01


Figure 3-43 PktsSentPerSec Chart for a Link

The PktsSentPerSec chart displays the following information for the selected link:

SGM displays the following information in the PktsSentPerSec chart:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Packets Sent Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.


78-15589-01


• Packets Sent Chart—Displays the Packets Sent Per Sec for the link as a function of time.



– dd.dd is the number of packets sent per second for that data point.








• SLC—Displays up to 16 color-coded icons, one for each link (SLC) in the Packets Sent Chart. To remove the data for a link from the chart, click the icon in this field. To return the data to the chart, click the icon again.





78-15589-01


Charts Tab: BitsRcvdPerSec

To view real-time bits-received-per-second information for the selected link (or bytes-received-per-second information, if you cleared the Show Details in Bits Instead of Bytes checkbox in the Preferences Window), select the Charts tab. SGM displays the BitsRcvdPerSec chart (Figure 3-44).

Figure 3-44 BitsRcvdPerSec Chart for a Link


78-15589-01


The BitsRcvdPerSec chart displays the following information for the selected link:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Bits Received Chart or Bytes Received Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.

• Bits Received Chart or Bytes Received Chart—Displays the Bits Received Per Sec or Bytes Received Per Sec for the link as a function of time.



– dd.dd is the number of bits or bytes (as set in the Preferences window) received per second for that data point.









78-15589-01


• SLC—Displays up to 16 color-coded icons, one for each link (SLC) in the Bits Received Chart or Bytes Received Chart. To remove the data for a link from the chart, click the icon in this field. To return the data to the chart, click the icon again.




Charts Tab: BitsSentPerSec

To view real-time bits-sent-per-second information for the selected link (or bytes-sent-per-second information, if you cleared the Show Details in Bits Instead of Bytes checkbox in the Preferences Window), select the Charts tab. SGM displays the BitsSentPerSec chart (Figure 3-45).


78-15589-01


Figure 3-45 BitsSentPerSec Chart for a Link

The BitsSentPerSec chart displays the following information for the selected link:

SGM displays the following information in the BitsSentPerSec or BytesSentPerSec chart:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Bits Sent Chart or Bytes Sent Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.


78-15589-01


• Bits Sent Chart or Bytes Sent Chart—Displays the Bits Sent Per Sec or Bytes Sent Per Sec for the link as a function of time.



– dd.dd is the number of bits or bytes (as set in the Preferences window) sent per second for that data point.








• SLC—Displays up to 16 color-coded icons, one for each link (SLC) in the Bits Sent Chart or Bytes Sent Chart. To remove the data for a link from the chart, click the icon in this field. To return the data to the chart, click the icon again.





78-15589-01


Charts Tab: Drops

To view drops information for the selected link, select the Charts tab. SGM displays the Drops chart (Figure 3-46).

Figure 3-46 Drops Chart for a Link


78-15589-01


The Drops chart displays the following information for the selected link:


• Time Window (mins)—Drop-down list box used to specify the length of time displayed in the Drops Chart. Valid selections are 1, 2, 5, 10, 20, 40, or 60 minutes. The default selection is 5 minutes.

• Drops Chart—Displays the Drops for the link as a function of time.



– dd.dd is the number of drops for that data point.








• SLC—Displays up to 16 color-coded icons, one for each link (SLC) in the Drops Chart. To remove the data for a link from the chart, click the icon in this field. To return the data to the chart, click the icon again.


78-15589-01





Editing a LinkSGM enables you to annotate a link, attaching a descriptive string to the link.

To annotate a link, right-click a link in a window, then select Edit Notes in the right-click menu.

SGM displays the Edit Notes Dialog for a Link (Figure 3-47).


78-15589-01


Figure 3-47 Edit Notes Dialog for a Link

The Edit Notes Dialog for a Link displays the name of the link and the date and time the Notes field for the link was last updated. If there is no note currently associated with the link, the Last Update field displays the value Not Set.


78-15589-01


In the Notes field, enter any important information about the link, such as a detailed description, its location, its service history, and so on.

Click Save to save the annotations and exit the Edit Notes Dialog for a Link.

Viewing Notes for a LinkSGM enables you to view the notes that have been attached to links.

To view a note, right-click a link in a window, then select View> Notes in the right-click menu. (The Notes option is grayed-out if there is no note associated with the selected link.)

SGM displays the Link Notes dialog (Figure 3-48).

Figure 3-48 Link Notes Dialog


78-15589-01


The Link Notes dialog displays the following information:

• Name—Name of the link.

• Notes Last Updated—Date and time the Notes field for the link was last updated.

• Notes—Notes associated with the link.

Click OK to close the Link Notes dialog.

Deleting a LinkAfter Discovery, the links in your network are known to SGM and added to the SGM database. Physically deleting links from your network is not the same as deleting them from the SGM database. The following sections describe the differences between deleting links from your network and from the SGM database, and the procedures for doing so:

• Deleting a Link from Your Network, page 3-233

• Deleting a Link from the SGM Database, page 3-234

Deleting a Link from Your Network

If you physically delete a known link from your network, it remains in the SGM database, and SGM labels it Unknown, and it is the system administrator’s responsibility to delete it from the SGM database, if you choose to do so. The Link Details Window also displays -1 in the Xmit Queue field. SGM labels all associated nodes, signaling points, and linksets Warning.

When you redefine the link (that is, when you define a link with the same signaling link code ID [SLC] as the original link), SGM rediscovers the link and labels it with the appropriate status (such as Active).


78-15589-01


Deleting a Link from the SGM Database

Typically, you delete a link in the SGM database for one of the following reasons:

• You have physically deleted the link from your network. This is the most common reason for deleting a link from the SGM database.

• The link is Blocked, Failed, or Unknown, you are aware of the reason, and you no longer want to see it in SGM displays. For example, the link might be associated with a linkset that was removed from the network, or it might be a previously discovered link associated with a test lab device.

If you have physically deleted a known link from your network, and you then delete it from SGM, it is no longer in the SGM database, it does not appear in SGM windows, and it is not discovered when you run Discovery.

If you have not physically deleted a known link from your network, and you delete it from SGM, at the next poll SGM finds the link and adds it back to the SGM database, setting the status appropriately. If this happens, do not delete the link again. Instead, set it to Ignored. See the “Ignoring a Link” section on page 3-235 for more information.

Note If you delete a link from the SGM database, the link is deleted for all SGM clients and views connected to that SGM server.

To delete a link from the SGM database, use one of the following procedures:

• Select a link in the Link Details window (Figure 3-37), then select Edit > Delete from the SGM Main Menu.

• Right-click a link in the Link Details window, then select Delete Link from the right-click menu.

SGM asks you to confirm the deletion.

• Select Yes to delete the selected link. SGM deletes the link from the SGM database. However, if the link was not physically deleted from your network, then at the next poll SGM finds the link and adds it back to the SGM database, setting the status appropriately.

• Select No to return to the Link Details window without deleting the link from the SGM database.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMWorking with Events

Ignoring a LinkYou can instruct SGM to ignore a link when it aggregates and displays network data. Setting links to Ignored prevents known link problems from affecting SGM displays for associated linksets and nodes. In effect, you are preventing a known problem from distracting you from other, more urgent network problems.

For example, you can set a link to Ignored before shutting down the link for maintenance.

Note If you set a link to Ignored, the link is ignored for all SGM clients and views connected to that SGM server.

Also, if you set a link to Ignored, make a note of the change, and do not forget to reset the link when the problem is corrected or the maintenance is complete.

To set a link to Ignored, right-click the link in the Link Details window (Figure 3-37), then select Ignore from the right-click menu.

Viewing Ignored LinksTo display all links that are Ignored, display the Link Window and click the Ignored column header. SGM displays all ignored links at the top of the table.

Working with EventsSGM enables you to view detailed information about all discovered events, including their associated nodes, signaling points, linksets, links, and other information.


• Viewing Basic Information for All Events, page 3-236

• Viewing Events for a Specific Object, page 3-240

• Viewing Detailed Information for an Event, page 3-243

• Viewing Real-Time Data for an Event, page 3-244


78-15589-01


• Setting an Event Filter, page 3-244

• Viewing Event Properties, page 3-253

• Attaching a Note to an Event, page 3-256

• Viewing Notes for an Event, page 3-258

Related Topics:

• Modifying the SGM Event Configuration File (Solaris Only), page 5-26


• Setting Sounds for Events at an SGM Client, page 5-40





Viewing Basic Information for All EventsTo view basic information for all events, select Events in the left pane of the SGM Main Window. SGM displays the Event Window (Figure 3-49).


78-15589-01


Figure 3-49 Event Window

The Event Window displays information about the events delivered by the SGM event logger and event processor for all nodes, signaling points, linksets, and links in the current network view.

Note You can display more than one Event Window at one time. This enables you to view multiple Event Windows at the same time, with different event filtering in each window or dialog.

By default, SGM displays all of the columns in the table except Internal ID, Note, Ack By, Ack Time, Node, and Linkset. To display these columns, or to hide other columns, see the procedures in the “Modifying Event Table Column Settings” section on page 5-19.





78-15589-01


The Event Window provides the following toolbar buttons:

• Set Filter—Opens the Event Filter dialog.

• Apply Filter—Activates and deactivates the event filter specified in the Event Filter dialog:

– If the filter is activated, SGM displays only those events that pass the filter.

– If the filter is deactivated, SGM displays all events.

• Acknowledge—Makes s the selected event or events acknowledged.

• Unacknowledge—Makes the selected event or events unacknowledged.

• Event Properties—Opens the Event Properties window.

• Edit Notes—Opens the Edit Event Dialog.

• Time Difference—Displays the difference in days, minutes, hours, and seconds between two events.

• Find—Finds a specific event.

• Help for Event—Displays context-sensitive help for the selected event in a separate Web browser.

The Event Window displays the following information for each event:










78-15589-01























78-15589-01










• Message—Message associated with the event.


Viewing Events for a Specific ObjectTo display the Recent Events panel, with events displayed for only the selected node, signaling point, linkset, or link, right-click a node, signaling point, linkset, or link in a window, then select View >Events from the right-click menu.

• If you right-clicked a node, SGM displays the Recent Events panel for the node (Figure 3-25). For more information, see the “Viewing Detailed Information for a Node” section on page 3-96.

• If you right-clicked a signaling point, SGM displays the Recent Events panel for the signaling point (Figure 3-32).

• If you right-clicked a linkset, SGM displays the Recent Events panel for the linkset (Figure 3-12).

• If you right-clicked a link, SGM displays the Recent Events panel for the link (Figure 3-38).


78-15589-01


By default, SGM displays all of the columns in the Recent Events panel except Internal ID, Note, Ack By, Ack Time, Node, SP, Linkset, and Link. To display these columns, or to hide other columns, see the procedures in the “Modifying Event Table Column Settings” section on page 5-19.




The Recent Events panel enables you to perform event-related tasks, such as setting filters and acknowledging events. For more information about these tasks, see the “Working with Events” section on page 3-235.

The Recent Events panel displays the following information for the selected node:













78-15589-01























78-15589-01









Viewing Detailed Information for an EventSGM enables you to display detailed configuration information for the node, signaling point, linkset, or link associated with a specific event.

To display detailed information for an event, select Events in the left pane of the SGM Main Window, right-click an event in a window, then select View> Configuration Details in the right-click menu.

• If the event is associated with a node, SGM displays the Configuration Data tab of the Node Details Window (Figure 3-24). For more information, see the “Viewing Detailed Information for a Node” section on page 3-96.

• If the event is associated with a signaling point, SGM displays the Configuration Data tab of the Signaling Point Details Window (Figure 3-31). For more information, see the “Viewing Detailed Information for a Signaling Point” section on page 3-141.

• If the event is associated with a linkset, SGM displays the Configuration Data tab of the Linkset Details Window (Figure 3-11). For more information, see the “Viewing Detailed Information for a Linkset” section on page 3-42.


78-15589-01


• If the event is associated with a link, SGM displays the Configuration Data tab of the Link Details Window (Figure 3-37). For more information, see the “Viewing Detailed Information for a Link” section on page 3-175.

Viewing Real-Time Data for an EventSGM enables you to display detailed statistics for the node, linkset, or link associated with a specific event.

To display detailed statistics for an event, select Events in the left pane of the SGM Main Window, right-click an event in the right pane, then select View> Real-Time Data and Charts in the right-click menu.

• If the event is associated with a node, SGM displays the SGM Real-Time Statistics: CPU Statistics window (Figure 3-26). For more information, see the “Viewing CPU Statistics for a Node” section on page 3-121.

• If the event is associated with a linkset, SGM displays the Statistics Details Window for a Linkset (Figure 3-13). For more information, see the “Viewing Real-Time Data for a Linkset” section on page 3-54.

• If the event is associated with a link, SGM displays the Statistics Details Window for a Link (Figure 3-37). For more information, see the “Viewing Real-Time Data for a Link” section on page 3-186.

Setting an Event FilterTo modify the way SGM presents event information, use the following procedure:

Step 1 Select Event Tools > Set Filter from the SGM Main Menu. SGM displays the Event Filter dialog with the Properties tab selected (Figure 3-50).


78-15589-01


Figure 3-50 Event Filter Dialog, Showing Event Properties

Step 2 (Optional) To specify which event categories you want to display in the Event Window, select the Properties tab and modify the following settings:

• Status—Checkbox used to indicate whether Status events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Edit—Checkbox used to indicate whether Edit events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• OverWrite—Checkbox used to indicate whether OverWrite events are to be displayed in the Event Window. The default setting for this checkbox is selected.


78-15589-01


• Trap—Checkbox used to indicate whether Trap events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Ignore—Checkbox used to indicate whether Ignore events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Poll—Checkbox used to indicate whether Poll events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Create—Checkbox used to indicate whether Create events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Login—Checkbox used to indicate whether Login events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Purge—Checkbox used to indicate whether Purge events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Delete—Checkbox used to indicate whether Delete events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• LoginDisable—Checkbox used to indicate whether LoginDisable events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Discover—Checkbox used to indicate whether Discover events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• LoginFail—Checkbox used to indicate whether LoginFail events are to be displayed in the Event Window. The default setting for this checkbox is selected.

To select all event category checkboxes. click Select All.

To clear all event category checkboxes, click Deselect All.

Note These are the default categories; there might be additional categories, as defined by the SGM system administrator. For information about custom categories, see the “Modifying the SGM Event Configuration File (Solaris Only)” section on page 5-26.


78-15589-01


Step 3 (Optional) To specify which event severities you want to display in the Event Window, select the Properties tab and modify the following settings:

• None—Checkbox used to indicate whether events of severity None are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Normal—Checkbox used to indicate whether events of severity Normal are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Admin—Checkbox used to indicate whether events of severity Admin are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Warning—Checkbox used to indicate whether events of severity Warning are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Error—Checkbox used to indicate whether events of severity Error are to be displayed in the Event Window. The default setting for this checkbox is selected.

Note There might be additional custom severities, as defined by your SGM System Administrator. For information, see the “Modifying the SGM Event Configuration File (Solaris Only)” section on page 5-26.


78-15589-01


Step 4 (Optional) To further define the event filter for the Event Window, select the Properties tab and modify the following settings:

• Acknowledged—Checkbox used to indicate whether only acknowledged events are to be displayed in the Event Window. The default setting for this checkbox is cleared.

• Unacknowledged—Checkbox used to indicate whether only unacknowledged events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Time Before—Checkbox used to indicate whether only events logged by SGM prior to a specified date and time are to be displayed in the Event Window. The default setting for this checkbox is cleared.

• Time Before Field—Specifies the date and time prior to which events logged by SGM are to be displayed in the Event Window. This field is grayed-out unless the Time Before checkbox is selected.

• Time After—Checkbox used to indicate whether only events logged by SGM after a specified date and time are to be displayed in the Event Window. The default setting for this checkbox is cleared.

• Time After Field—Specifies the date and time after which events logged by SGM are to be displayed in the Event Window. This field is grayed-out unless the Time After checkbox is selected.

• Message Contains—Checkbox used to indicate whether only events that contain the specified message text are to be displayed in the Event Window. The default setting for this checkbox is cleared.

• Match Case—Checkbox used to indicate whether only events that match the case of the text in the Message Contains field are to be displayed in the Event Window. This field is grayed-out unless the Message Contains checkbox is selected. If the Message Contains checkbox is selected, the default setting for this checkbox is cleared.

These settings are applied to all event displays in the current view.


78-15589-01


Step 5 (Optional) To specify the node, signaling point, linkset, and link for which SGM is to display events in the Event Window, select the Selected Objects tab. SGM displays the Event Filter dialog with the Selected Objects tab highlighted (Figure 3-51).

Figure 3-51 Event Filter Dialog, Showing Event Selected Objects


78-15589-01


You can modify the following settings:

• Node—Drop-down list box of all nodes that have been discovered by SGM:

– If you want to filter events based on a node, select a node from the drop-down list box.

– If you do not want to filter events based on a node, select None. SGM grays-out the SP, Linkset, and Link fields. This is the default setting.

• SP—Drop-down list box of all signaling points associated with the selected node:

– If you want to filter events based on a signaling point, select a signaling point from the drop-down list box.

– If you do not want to filter events based on a signaling point, select None. SGM grays-out the Linkset and Link fields. This is the default setting.

• Linkset—Drop-down list box of all linksets associated with the selected signaling point:

– If you want to filter events based on a linkset, select a linkset from the drop-down list box.

– If you do not want to filter events based on a linkset, select None. SGM grays-out the Link field. This is the default setting.

• Link—Drop-down list box of all links that have been discovered by SGM:

– If you want to filter events based on a link, select a link from the drop-down list box.

– If you do not want to filter events based on a link, select None. This is the default setting.

• To restore Node to None, grays-out SP, Linkset, and Link, click Reset.

Step 6 (Optional) To load an existing event filter, click Load in the Event Filter dialog. SGM displays the Load File Dialog: Load Filter dialog (Figure 3-52).


78-15589-01


Figure 3-52 Load File Dialog: Load Filter Dialog

The Load File Dialog: Load Filter dialog contains the following fields:


• Name—Name of the event filter file or folder.

• Last Modified—Date and time the event filter file or folder was last modified.

• Size (bytes)—Size of the event filter file or folder, in bytes.

• Number of Files—Total number of event filter files and folders (displayed in bottom left corner).

To load an event filter file, enter the name of the file or select it in the list and click OK. SGM loads the event filter file, closes the Load File Dialog: Load Filter dialog, and returns to the Event Filter dialog.

To delete an event filter file from the event filter file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.


78-15589-01


To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: Load Filter dialog.

To close the Load File Dialog: Load Filter dialog without loading an event filter file or saving any changes to the event filter file list, click Cancel.

Step 7 (Optional) To apply any changes you made to the event filter without closing the Event Filter dialog, click Apply.

Step 8 (Optional) To close the Event Filter dialog without saving any changes to the event filter file or event filter file list, click Cancel.

Step 9 When you are satisfied with the filter settings, click Save. SGM displays the Save File Dialog: Save Filter dialog (Figure 3-53).

Figure 3-53 Save File Dialog: Save Filter Dialog

The Save File Dialog: Save Filter dialog contains the following fields:


• Name—Name of the event filter file or folder.


78-15589-01


• Last Modified—Date and time the event filter file or folder was last modified.

• Size (bytes)—Size of the event filter file or folder, in bytes.

• Filename—Name by which you want to save the event filter file.

If you create a new event filter file name, you can use any letters, numbers, or characters in the name that are allowed by your operating system. However, if you include any spaces in the new name, SGM converts those spaces to dashes. For example, SGM saves file “a b c” as “a-b-c”.

• Number of Files—Total number of event filter files and folders (displayed in bottom left corner).

To save the event filter file with a new name, use one of the following procedures:


• To save the file with an existing name, overwriting an old event filter file, select the name in the list and click OK.

SGM saves the event filter file with the new name, closes the Save File Dialog: Save Filter dialog, and returns to the Event Filter dialog.

To delete an event filter file from the event filter file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.

To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: Save Filter dialog.

To close the Save File Dialog: Save Filter dialog without saving the event filter file or saving any changes to the event filter file list, click Cancel.

Viewing Event PropertiesSGM enables you to view detailed information about a selected event, including its associated node, signaling point, linkset, status, and other information.

To view detailed information about an event, right-click the event in a window, then select Event Properties in the right-click menu.

SGM displays the Event Properties Dialog (Figure 3-54).


78-15589-01


Figure 3-54 Event Properties Dialog

The Event Properties dialog provides the following information for the selected event:

• Properties Tab—Displays detailed information about the selected event.








78-15589-01




















• Timestamp—Date and time the event was logged.

• Acknowledged—Indicates whether the event has been acknowledged.


78-15589-01


• Acknowledged By—Name of the device that last acknowledged the event. If no one has acknowledged the event, this field is blank.

• Ack Timestamp—Date and time the event was last acknowledged or unacknowledged.


• Signaling Point—Name of the signaling point associated with the event. If there is no signaling point associated with the event, None is displayed.



• Notes Tab—Displays notes associated with this event.

• Last Update—Date and time the Notes field for this event was last updated. If there is no note currently associated with this event, this field displays the value Not Set.

• Notes—Notes associated with this event. If there is no note currently associated with this event, this field displays the value No Notes.

Attaching a Note to an EventSGM enables you to annotate an event, attaching a descriptive string to the event.

To annotate an event, right-click an event in the Event Window, then select Edit Notes in the right-click menu.

SGM displays the Edit Event Dialog (Figure 3-55).


78-15589-01


Figure 3-55 Edit Event Dialog

The Edit Event Dialog displays the message text of the event and the date and time the Notes field for the event was last updated. If there is no note currently associated with the event, the Last Update field displays the value Not Set.

In the Notes field, enter any important information about the event, such as its associated node, signaling point, or linkset, what triggered the event, how often it has occurred, and so on.

Click Save to save the annotations and exit the Edit Event Dialog.


78-15589-01


Viewing Notes for an EventSGM enables you to view the notes that have been attached to events.

To view a note, use one of the following procedures:

• Select an event in a window, then select View > Notes from the SGM Main Menu.

• Right-click an event in the Event Window, then select View > Notes in the right-click menu.

If the event has an attached note, SGM displays the Event Notes dialog (Figure 3-56). (If the event does not have an attached note, SGM displays the message, “The event does not have any notes.”)

Figure 3-56 Event Notes Dialog


78-15589-01

Chapter 3 Managing ITP Networks Using SGMViewing the Topology of the Network

The Event Notes dialog displays the following information:

• Name—Message text of the event.

• Last Updated—Date and time the Notes field for the event was last updated.

• Notes—Notes associated with the event.

Click OK to close the Event Notes dialog.

Viewing the Topology of the NetworkIn addition to tabular (text) views of your network, SGM provides a topology (graphical) view of the signaling points and linksets in your network, including adjacent legacy SS7 devices, and enables you to customize the view to meet your needs.

Related Topics:





• Working with Views, page 3-26

To view the topology of your network:

Step 1 Use one of the following procedures:

• Select View > Show Topology from the SGM Main Menu.

• Right-click a signaling point, linkset, link, or event, then select View > Center in Topo in the right-click menu.

SGM displays the Topology window (Figure 3-57).


78-15589-01


Figure 3-57 Topology Window

The Topology Window displays tabular information about signaling points and linksets in the left pane and the graphical topology map in the right pane.

Linksets that are associated with signaling points that are excluded from the current view are not displayed in the topology map. See the “Creating a View” section on page 3-27 for more information about excluding signaling points.


78-15589-01


SGM automatically assigns the following node elements:

• Cisco 2650 series router

• Cisco 2650XM series router


• Cisco 2651XM series router


• Cisco 7204VXR series router


• Cisco 7206VXR series router


• Cisco 7507mx series router

• Cisco 7507z series router


• Cisco 7513mx series router

• Cisco 7513z series router

• IP device, other than other than those listed above (if assigned by a user; see the “Editing a Node” section on page 3-124 for more details)

• Signaling point—An SCP, SSP, or STP, or an ITP instance.

• SS7—SGM is unable to determine the node type.

In addition, users can assign the following node elements (see the “Editing a Node” section on page 3-124 for more details):

• MSC—Mobile switching center

• SCP—Service control point

• SSP—Service switching point

• STP—Signal transfer point


78-15589-01


A line indicates a single logical connection configured between two nodes:

• A line that ends in a diamond or circle indicates that the connection has a configured linkset, associated with that node.

• A line that does not end in a diamond or circle indicates that the linkset is not configured on that ITP or cannot be displayed because SGM is not managing that node.

• A heavy line indicates that there are two or more linksets configured between two signaling points.

The color of a graphical element indicates its current status.

• For nodes, the possible colors are:

– Green—The node is currently in Active status.

– Yellow—The node is currently in Warning status.

– Gray—The node is currently in Discovering, Polling, Unmanaged, or Waiting status.

– Red—The node is currently in Unknown status.

• For linksets (diamonds or circles), the possible colors are:

– Green—The linkset is in Active status.

– Blue—The linkset is in Shutdown status.

– Yellow—The linkset is in Warning status.

– Red—The linkset is in either Unavailable or Unknown status.

Note If there is more than one linkset configured on the connection, the status color is an aggregation of the status of every linkset on that connection.

A note icon in the upper left corner of a node element means the node has been annotated. That is, a user has attached a descriptive string to the node. A dot in the diamond or circle at the end of the line means a note has been attached to the linkset.

An event icon (orange triangle) in the upper right corner of a node element means there is a recent event associated with the node.

The topology map also provide right-click menus for linksets and signaling points.


78-15589-01


Step 2 The topology signaling point table in the left pane of the Topology window displays the name and status of the signaling points that are currently displayed in the topology map. To display the topology signaling point table, select the Tables tab in the left pane. By default, this table is sorted by Status.

To redraw the topology map centered on a specific signaling point, double-click on the signaling point in this table.

You cannot select more than one signaling point at a time in this table.

Step 3 The topology linkset table in the left pane of the Topology window displays the name and status of the linksets that are displayed in the topology map. To display the topology linkset table, select the Tables tab in the left pane of the Topology Window, then select a signaling point in the topology signaling point table, or a signaling point in the topology map. The topology linkset table is displayed below the topology signaling point table.

To redraw the topology map centered on a specific linkset, double-click on the linkset in this table.

You cannot select more than one linkset at a time in this table.

Step 4 (Optional) In the topology linkset table, you can select the Ignored checkbox to ignore a linkset when displaying SGM data, or clear the checkbox to include the linkset. For more information, see the “Ignoring a Linkset” section on page 3-90.

Step 5 (Optional) To highlight an element in the topology signaling point table or topology linkset table in the left pane, click it in the topology map:

• Click a signaling point to highlight the signaling point in the topology signaling point table, and to display any associated linksets in the topology linkset table.

• Click a single line, a heavy line, a diamond, or a circle, to display the following information:

– Highlight the closest associated node in the topology signaling point table. For example, if there is a line connecting node sgm-2600a and node sgm-2600b, and you click the line closer to node sgm-2600a, then that node is highlighted in the topology signaling point table.

– Display all linksets (if any) associated with that node in the topology linkset table.

– Highlight the clicked linkset (if it is configured) in the topology linkset table.


78-15589-01


Step 6 To see mouse over help popup in the topology map, place the cursor over a signaling point or linkset. When you place the cursor over a linkset, the mouse over help popup is displayed from the perspective of the closest signaling point.

Note You can turn off mouse over help. For details, see Step 5 in the “Modifying Overall Preference Settings” section on page 5-5.

Step 7 (Optional) To make the topology map twice as large, click the Zoom the map by a factor of 200% button, or select Topology Tools > Zoom > In from the SGM Main Menu.

Step 8 (Optional) To make the topology map half as large, click the Zoom the map by a factor of 50% button, or select Topology Tools > Zoom > Out from the SGM Main Menu.

Step 9 (Optional) To zoom the topology map by a selected percentage, click the Select a map viewing factor button, then either select a percentage from the drop-down list box, or enter a percentage and click Enter. Valid values are integers in the range 5 through 400.

Step 10 (Optional) To zoom in on a selected area of the topology map, click the Zoom in on an area button, or select Topology Tools > Zoom > Area from the SGM Main Menu, then click in the topology map and drag a rectangle around the area you want to zoom in on. SGM expands the selected area to fill the topology map.

Step 11 (Optional) To adjust the size of the topology map to fit in the window, click the Zoom to fit window button, or select Topology Tools > Zoom > Fit from the SGM Main Menu. This is the default setting the first time the map is displayed.

Step 12 (Optional) To display the topology map in a circular layout, click the Circular layout button, or select Topology Tools > Layout > Circular from the SGM Main Menu.


78-15589-01


Step 13 (Optional) To display the topology map in a spring layout, click the Spring layout button, or select Topology Tools > Layout > Spring In a spring layout, nodes with the most links are drawn closer to the center of the map, while nodes with fewer links are drawn farther away. This is the default setting the first time the map is displayed.

Note You can modify how far apart nodes are spaced when SGM draws the spring layout. For details, see Step 5 in the “Modifying Overall Preference Settings” section on page 5-5.

Step 14 (Optional) To create a custom layout for the topology map, move the signaling points around, grouping them or isolating them to meet your needs.

To move a single signaling point, click the left mouse button to select the signaling point in the map and, while holding down the left mouse button, move the mouse to move the signaling point to its new position.

To move more than one signaling point at the same time, use the following procedure:

a. Press and hold down the Shift key on your keyboard.

b. Still holding down Shift, click the left mouse button to select the signaling points you want to move in the map.

c. Still holding down Shift, select one of the signaling points you want to move and hold down the left mouse button.

d. Still holding down both Shift and the left mouse button, move the mouse to move the signaling points to their new position. The moved signaling points keep their positions relative to each other.

e. Release both Shift and the left mouse button.

When you are satisfied with the new topology map layout, select File > Save View from the SGM Main Menu. SGM saves the changes you have made to the network view, including any changes you have made to the topology map layout.

Step 15 (Optional) To restore the topology map to the way it looked in the last saved view, select Topology Tools > Restore Positions from the SGM Main Menu. SGM restores the view.


78-15589-01


Step 16 (Optional) Some topology maps are so large and complex that it can be difficult to find a specific signaling point or linkset.

If the signaling point or linkset is listed in the tables in the left pane of the Topology Window, simply select the signaling point or linkset, and SGM highlights it in the topology map.

If the signaling point or linkset is not listed in the tables, use the following procedure:

a. Click the Find signaling points or linksets (binoculars) button in the Topology Window, or select Edit > Find from the SGM Main Menu. SGM displays the Find Signaling Points or Linksets dialog, which enables you to find and highlight a signaling point or linkset in the Topology Window

b. In the Search string field, enter a character string for which SGM is to search.

c. To search for a linkset, select the Linksets checkbox. To search for a signaling point, select the Signaling Points checkbox, then select or clear the Name and Point Code checkboxes, to further widen or refine the search.

d. Click OK to launch the search.

If no matching signaling point or linkset is found, SGM displays an appropriate message.

If exactly one signaling point or linkset is found that matches the Search string, SGM highlights the signaling point or linkset in the Tables panel of the Topology window, and zooms in on the selected signaling point or linkset in the topology map.

If more than one signaling point or linkset is found that matches the Search string, SGM displays the Choose dialog, enabling you to select from a list of the found objects. SGM then highlights the selected signaling point or linkset in the Tables panel of the Topology window, and zooms in on the selected signaling point or linkset in the topology map.

Step 17 (Optional) To scroll around in the topology map, click anywhere in the map, then click the arrow, Page Up, and Page Down keys.

Step 18 (Optional) To redraw the topology map centered on a specific signaling point or linkset, double-click on the signaling point or linkset in the topology signaling point table in the left pane of the window.


78-15589-01


Step 19 (Optional) To display detailed information about an element in the map, double-click it, then respond to SGM’s prompts:

• Double-click a signaling point to display the Details Window for that signaling point.

• Double-click a single line, or a diamond or circle at the end of a single line, to display the Linkset Details Window for that linkset.

• Double-click a heavy line, or a diamond or circle at the end of a heavy line, to display the Selection Dialog. Then select one of the linksets to display the Linkset Details Window for that linkset.

Step 20 (Optional) To display the topology new signaling point panel, select the New Signaling Points tab in the left pane. The topology new signaling point panel displays graphical elements for newly discovered signaling points, based on the following criteria:

• If you are using an SGM client with the DEFAULT view set, this panel never contains any signaling points. In the DEFAULT view, SGM adds all newly discovered signaling points to the topology map as soon as they are discovered.

• If you are using an SGM client with a custom view set, this panel contains all signaling points discovered since the Topology window was opened in this session that have not been excluded in the Signaling Points Excluded from View table of the Network View Editor window, or that are not in the current view.

a. (Optional) To add a newly discovered signaling point to the topology map, select one or more signaling points in the topology new signaling point panel and drag them to the map while holding down the left mouse button.

b. (Optional) To exclude a newly discovered signaling point from the topology new signaling point panel, see the “Working with Views” section on page 3-26.


78-15589-01


Step 21 (Optional) To display the topology excluded signaling point panel, select the Excluded Signaling Points tab in the left pane. The topology new signaling point panel displays graphical elements for excluded signaling points. Excluded signaling points are signaling points that you have chosen not to manage, that you have moved to the Signaling Points Excluded from View table of the Network View Editor window. (See the “Creating a View” section on page 3-27 for more information about excluding signaling points from views.)

To add an excluded signaling point to the topology map, select the signaling point and drag it to the map while holding down the left mouse button. When you do so, the signaling point is no longer an excluded node, and it is removed from the Signaling Points Excluded from View table of the Network View Editor window.

Step 22 (Optional) To print the topology map, see the “Printing SGM Windows” section on page 3-398.

Step 23 (Optional) To save the topology map as a JPEG file, select Topology Tools > Save as JPEG from the SGM Main Menu. SGM displays the Save as JPEG dialog (Figure 3-58).

Figure 3-58 Save as JPEG Dialog


78-15589-01


The Save as JPEG dialog provides the following options:

• To save the entire topology map as a JPEG file, select All.

• To save just the portion of the topology map displayed in the current window as a JPEG file, select Current Window.

• To specify the quality of the JPEG file, select a Quality level, from 0 (lowest quality) to 1.0 (highest quality). The default setting is 0.7, which is sufficient for most JPEG files.

• To specify the size of the JPEG file, in pixels, choose a value from the Max. Size drop-down list box. The valid range is 400 pixels to 2400 pixels. The default value is 400 pixels, which is sufficient for most JPEG files.

• To specify a name for the JPEG file, enter the name in the Name field, or accept the default filename, out.jpg.

The default directory for the JPEG file is the directory in which you installed the SGM client:

– In Solaris, the default installation directory for the SGM client is /opt/CSCOsgmClient.

– In Windows, the default installation directory for the SGM client is C:\Program Files\SGMClient\.

– If you installed the SGM client in a different directory, then the installation directory is located in that directory.

To save the JPEG file in the default directory, click Save. SGM saves the JPEG file and closes the Save as JPEG dialog. Continue with Step 24.

If you do not want to save the JPEG file to the default directory, click Browse to select a different directory. SGM displays the Save dialog for a topology map (Figure 3-59).


78-15589-01


Figure 3-59 Save Dialog for a Topology Map

The Save dialog for a topology map provides the following options:

– To select the directory in which you want to save the topology map JPEG file, either accept the default directory displayed in the Save In field, or select a new directory from the drop-down list box.

– To display the sub-folders and files that are in the folder that is up one level from the currently displayed folder, click the Up One Level button.

– To display the sub-folders and files that are on your workstation desktop, click the Desktop button.

– To create a new sub-folder in the displayed folder, click the Create New Folder button.

– To display only icons for sub-folders and files, click the List button.

– To display detailed information for sub-folders and files, including their size, type, date they were last modified, and so on, click the Details button.


78-15589-01


– To specify a name for the JPEG file, enter the name in the File Name field, or select a file from those listed in the Save In field.

– To specify the type of file to save, and to display all files of that type in the selected directory, select a file type from the Files of Type drop-down list box:

– All files—Displays all files in the selected directory, and saves the topology map file as a JPEG file.

– jpg files—Displays only JPEG files in the selected directory, and saves the topology map file as a JPEG file.

When you are satisfied with the settings, click Save. SGM closes the Save dialog for a topology map and populates the Name field in the Save as JPEG dialog with the new name and directory.

To save the JPEG file in the new directory, click Save. SGM saves the JPEG file and closes the Save as JPEG dialog.

Step 24 (Optional) You can activate a magnetic grid on the topology map. With the grid activated, objects “snap” to align with the grid when you move them.

To activate or modify the magnetic topology grid, select Topology Tools > Magnetic Grid from the SGM Main Menu. SGM displays the Magnetic Grid Settings dialog (Figure 3-60).

Figure 3-60 Magnetic Grid Settings Dialog


78-15589-01


The Magnetic Grid Settings dialog provides the following options:

• To activate the grid, select the Grid Activated checkbox.

To deactivate the grid, clear the Grid Activated checkbox.

• To display the grid on the topology map, select the Grid Activated checkbox, then select the Display Grid checkbox.

To hide the grid on the topology map, clear the Display Grid checkbox.

• To specify the spacing between lines on the grid, in pixels, select the Grid Activated checkbox, then select a Grid Spacing level. The valid range is 0 pixels to 150 pixels. The default setting is 50 pixels, which is sufficient for most topology maps.

• To specify a color for the grid, select the Grid Activated checkbox, then click Select in the Grid Color field. SGM opens the Pick Grid Color dialog (Figure 3-61).

Figure 3-61 Pick Grid Color Dialog


78-15589-01


The Pick Grid Color dialog provides the following options:

– To select a grid color from a set of color swatches (the recommended method), click the Swatches tab and select a swatch.

– To select a grid color based on color hue, saturation, and brightness (HSB), click the HSB tab, then use one of the following procedures:

- Select a color range on the vertical color bar, then select a specific color by moving the cursor around on the color square.

- Enter specific values in the hue (H), saturation (S), and brightness (B) fields.

– To select a grid color based on the red, green, and blue (RGB) content of the color, click the RGB tab, then select values for the Red, Green, and Blue fields.

– To reset the grid color to its initial setting, click Reset.

Whichever method you choose, the selected color is displayed in the Preview field. When you are satisfied with the color, click OK. SGM saves the grid color setting and closes the Pick Grid Color dialog.

When you are satisfied with the magnetic grid settings, click OK. SGM saves the new grid settings and closes the Magnetic Grid Settings dialog

Note Magnetic grid settings, including the grid color, are not saved when you save the view.

To close the Magnetic Grid Settings dialog without changing any settings, click Cancel.

Step 25 (Optional) To hide all non-ITP nodes and linksets on the topology map (the default setting), click the Hide/Show Non-ITP Devices button. (The hidden signaling points and linksets are still shown in the left pane.) To display all hidden nodes and linksets on the topology map, click the Hide/Show Non-ITP Devices button again. This setting, with non-ITP nodes and linksets either hidden or shown, is saved when you save the view.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMViewing Server Status Information

Step 26 (Optional) To have SGM hide linkset lines as you drag an object around the topology map, then draw the linkset lines when you drop the object in its final position, click the Node Dragging Optimizer button to turn it on. This is the default setting.

To have SGM continually redraw linkset lines as you drag an object around the topology map, click the Node Dragging Optimizer button to turn it off.

This setting, with the Node Dragging Optimizer on or off, is saved when you save the view.

Step 27 When you are ready to close the Topology Window, select File > Save View from the SGM Main Menu. SGM prompts you to save any changes you made to the network view, including any changes you have made to the topology map layout, and closes the window.

Viewing Server Status InformationSGM can display detailed information about the processes, pollers, tasks, and clients for the server to which you are connected, and which is currently running the SGM server.

To display server status information, select View >Server> Status Information in the SGM Main Menu. SGM displays the Server Status Information window (Figure 3-62).


78-15589-01


Figure 3-62 Server Status Information Window

The Server Status Information window displays the following information about polling:



To force an immediate poll at any time, and to refresh the Server Status Information window with the latest data, click Update.

To close the Server Status Information window at any time, click Close.

The Processes section displays the following information about the processes that are managed by the SGM serve Process Manager:

• Name—Name of the process, such as sgmDataServer.

• Version—Version number of the process application, such as 3.0.0.L1.

• Process ID—Number to uniquely identify the process.


78-15589-01


• State—Current state of the process. Valid values are:

– Initial (yellow ball)—Process is being initialized.

– Starting (yellow ball)—Process has been started but is not yet in Ready state.

– Ready (green ball)—Process has been started and is currently running.

– Stopping (red ball)—Process is being stopped.

– Stopped (red ball)—Process has been stopped.

• Last Message—Status message that reflects the current state of the process, such as Running.

The Processes section displays the following information about the processes that are not managed by the SGM serve Process Manager:

• Name—Name of the process, such as sgmNameServer.

• Process ID—Number to uniquely identify the process.

• Is Running—Indicates whether the process is running (true) or not (false).

The Pollers table displays the following information about the detail and demand pollers that are currently being processed by the SGM server:

• Poller ID—Number to uniquely identify each SGM detail poller that is currently active. SGM detail pollers collect detailed data (such as real-time data, statistics, route detail, GTT MAP status, and so on) that is not collected by the regular SGM poller.

• Client Host—Name of the SGM client that started the detail poller.

• Interval—Poll interval for the detail poller, in hours, minutes, and seconds.

• Iteration—Number of times the detail poller is to poll. If this field displays Forever, the detail poller will never stop polling, until requested to stop by the SGM client.

• Next Poll—Time until the next poll, in hours, minutes, and seconds.

• Description—Description of the detail poller.


78-15589-01


The Tasks table displays the following information about the long-running services being performed by the SGM server:

• Task ID—Number to uniquely identify the task.

• Interval—Time between runs for the task, in hours, minutes, and seconds.

• Iteration—Number of times the task is to run. If this field displays Forever, the task will never stop polling.

• Next Execution—Time until the next run for the task, in hours, minutes, and seconds.

• State—Current state of the task. Valid values are:

– None—Task is stopped.

– Waiting—Task is waiting to transition to Ready or Running state.

– Ready—Task is ready to execute but is not yet in Running state.

– Running—Task has been started and is currently executing.

– Pending—Task was in Ready state when it was canceled by a user. The task is pending final removal from the scheduler.

– Error—Task encountered an error.

– Dying—Task was in Running state when it was canceled by a user. The task continues to run in Dying state until it completes, then it is removed from the scheduler.

• Description—Description of the task.

The Tasks table displays the following information about the SGM clients that are currently connected to the SGM server:

• Process Name—Name of an SGM client that is currently connected to the server.

• User Name—Name of an SGM client user who is currently logged in and connected to the server.

• Is Sleeping—Indicates whether the thread that is responsible for delivering messages is sleeping (true) or not (false).

• Sleep Time—Time in seconds the thread that is responsible for delivering messages has been sleeping.

• Queue Size—Number of messages waiting to be sent to the SGM client.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMFinding Information in a Window

Finding Information in a WindowSometimes it can be difficult to find a specific piece of information, such as a node name or event text, in a window. SGM enables you to search for a character string in the Node, Signaling Point, Linkset, and Event Windows.

Note To find a specific signaling point or linkset in the Topology Window, see Step 16 in the “Viewing the Topology of the Network” section on page 3-259.

Related Topics:




To find a character string in a window:

Step 1 In the Node, Signaling Point, Linkset, or Event Window, select Edit > Find from the SGM Main Menu. SGM displays the Find dialog (Figure 3-63).

Figure 3-63 Find Dialog

Step 2 In the What field, enter the character string for which you want SGM to search. This can be any character string: all or part of a node name, linkset name, point code, event text, status, and so on.

Step 3 (Optional) If you want SGM to search for only character strings that match the case of the text in the What field, select the Match Case checkbox. If you do not care about case-matching, clear the checkbox. (This is the default setting.)


78-15589-01

Chapter 3 Managing ITP Networks Using SGMResizing, Sorting, and Hiding Table Columns

Step 4 (Optional) If you want SGM to search forward (down and to the right) in the window, select the Search Forward radio button. This is the default setting.

If you want SGM to search backward (up and to the left) in the window, select the Search Backward radio button.

The Search Forward and Search Backward radio buttons are mutually exclusive.

Step 5 Click Find. SGM launches the search:

• If a matching character string is found in the window, SGM highlights the first line that contains the string.

To find the next occurrence of the string, click Find again.

You can continue to click Find until there are no more matches in the window. At that time, SGM displays an appropriate message in the dialog, such as Bottom of table reached.

• If no matching character string is found, SGM displays an appropriate message in the dialog, such as Bottom of table reached.

Step 6 When you are done searching, click Close. SGM closes the Find dialog.

Resizing, Sorting, and Hiding Table ColumnsThe columns in some tables in SGM can be resized, sorted, or hidden to meet your specific needs. SGM automatically saves your new settings and, thereafter, launches the client with the new settings.

• To make a column wider or narrower, click the column divider in the header and move the divider to the right or left while holding down the left or right mouse button.

Depending on your system, as well as other factors, SGM windows can sometimes display so small that text is illegible, and columns and text entry fields are very narrow and unusable. If this happens, resize the window and widen the individual columns until the information is again legible and the columns and text entry fields are usable.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMViewing Online Help

• To sort a table based on the data in a column, left-click in the column header. The table is sorted alphanumerically from top to bottom, based on the data in the selected column. To sort the table in reverse order, left-click in the column header a second time. If two entries in the selected column are identical, SGM sorts those rows based on the data in the remaining table columns, moving left to right.

• To sort a route table, click Sort Table. SGM sorts the entries in the route table field-by-field, beginning with Dest. Point Code, then Mask, Cost, Dest.Linkset, and finally QoS.

• To delete a column altogether, see the “Modifying Preference Settings” section on page 5-3.

Related Topics:





Viewing Online HelpSGM provides the following online help options in the SGM Main Menu:

• To display the table of contents for the SGM online help in a Web browser, select Help > Topics.

• To display online help for the current window in a Web browser, click Help > Window.

• To display build date, version, SSL support, and copyright information about the SGM application in a Web browser, click Help > About.

Related Topics:

• Viewing the SGM Technical Documentation, page 7-122


78-15589-01

Chapter 3 Managing ITP Networks Using SGMEditing an ITP Route Table File

Editing an ITP Route Table FileITP uses a route table to select the appropriate signaling path for each message, or signal unit, that it must forward. The route table provides the destination point code of the packet and the linkset name that can be used to forward the packet.

SGM enables you to edit ITP route table files for an ITP.

To edit a route table file using SGM:

Step 1 Open the route table file, using one of the following procedures:

• To open a route table file from a file, select Edit > Route Table > From File from the SGM Main Menu, select the name of a route table file, then click OK.

If the selected route table file contains incorrect linkset entries (for example, if your network configuration changed since the last time the route table file was saved), SGM displays the Replace Linkset Dialog (Figure 3-64).

Figure 3-64 Replace Linkset Dialog


78-15589-01


The Replace Linkset Dialog enables you to quickly replace incorrect linkset entries in route table files:

– To replace an incorrect linkset with a correct linkset, select an incorrect linkset in the Linksets That Are No Longer Valid table, then select a correct linkset from the Auto Replace with Linkset drop-down list box, then click Apply. SGM automatically replaces the incorrect linkset with the selected correct linkset in all affected entries in the route table file.

– To remove all entries that contain an incorrect linkset from the route table fie, select an incorrect linkset in the Linksets That Are No Longer Valid table, then select the Remove Entries Containing Selected Linkset checkbox, then click Apply. SGM automatically removes all entries that contain the incorrect linkset from the route table file.

– When you have corrected all incorrect linksets in the route table file, click Done. SGM displays the Route Table Dialog (Figure 3-66).

If the selected route table file does not contain any incorrect linkset entries, SGM displays the Route Table Dialog (Figure 3-66).

• To open a route table file from an ITP, use one of the following procedures:

– Select a node, signaling point, or linkset on a window, then select Edit > Route Table > From ITP from the SGM Main Menu. (If you select an Unmanaged node, this option is grayed-out and cannot be selected.)

– Right-click a signaling point on a window, then select Edit Route Table from the right-click menu. (If you select an Unmanaged signaling point, this option is grayed-out and cannot be selected.)

SGM displays the Choose Signaling Point dialog (Figure 3-65), which enables you to select the signaling point whose route table you want to edit.

Figure 3-65 Choose Signaling Point Dialog


78-15589-01


From the drop-down list box of signaling points, select the signaling point with the point code, variant, and network name that matches the route table file you want to edit.

– If you select a signaling point that has the wrong variant, SGM displays the message, “Point code out of range.”

– If you select a signaling point that has the correct variant but the wrong instance, SGM displays the Replace Linkset Dialog, prompting you to replace or remove most or all of the linksets.

SGM reads the active route table from the ITP and displays it in the Route Table Dialog (Figure 3-66).

Figure 3-66 Route Table Dialog

The route table lists destination point codes and associated destination linkset names, as well as other important information used to route packets on a node.

Press Enter to move down to the next row in the route table; press Tab to move to the next field.


78-15589-01


You can resize each column in the route table, but you cannot sort the table based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

Step 2 The Row Num field displays a unique number for each entry in the route table. You cannot edit this field, but the number might change as you add entries to or delete entries from the route table.

Step 3 The Destination Point Code field displays the destination point code for packets on the selected node. The destination point code is the point code to which a given packet is routed. To edit the destination point code, enter the new code in this field.

If you enter a new destination point code that is less restrictive than the mask, SGM displays a message to that effect at the bottom of the Route Table Dialog, and performs one of the following actions:

• If you modified an existing point code, SGM restores the previous point code.

• If you entered an entirely new point code, SGM leaves this field blank.

For example, a destination point code of 7.7.7, which specifies 14 bits, is less restrictive than a mask of 7.255.0, which specifies only 11 bits. SGM ignores the extra bits in the last digit of the destination point code and converts it to 7.7.0.

Step 4 The Mask field specifies the significant bits of the point code:

• For ANSI and China standard networks using the default 24-bit point code format, the default mask is 255.255.255.

• For ITU networks using the default 14-bit point code format, the default mask is 7.255.7.

To edit the mask, make the changes in this field.

If you enter a new mask, the binary conversion of the mask cannot contain ones (1) to the right of zeros (0). For example:

• 7.255.7 is a valid mask because it converts to binary 111.11111111.111.

• 7.255.1 is not a valid mask because it converts to binary 111.11111111.001.

If you enter an invalid mask, such as 7.255.1, SGM displays a message to that effect at the bottom of the Route Table Dialog, and performs one of the following actions:

• If you modified an existing mask, SGM restores the previous mask.

• If you entered an entirely new mask, SGM leaves this field blank.


78-15589-01


If you enter a new mask that is more restrictive than the destination point code, SGM asks if you want to adjust the point code automatically based on the new mask:

• Click Yes if you want to adjust the point code. For example, if the point code is 7.7.7, and you enter the new mask 7.255.0, SGM automatically adjusts the point code to 7.7.0.

• Click No if you do not want to adjust the point code:

– If you modified an existing mask, SGM restores the previous mask.

– If you entered an entirely new mask, SGM leaves this field blank.

Step 5 The Cost field displays the cost of the route to the destination, relative to other routes. To edit the cost, select a cost from the drop-down list box in this field. The valid costs range from 1 (lowest cost and highest priority) through 9 (highest cost and lowest priority).

Note If you configure two routes to the same device and do not specify a cost for one of them, then the cost for that device defaults automatically to 5. The default cost appears here in the Cost column, and in the output of the show cs7 route command.

Similarly, if you add a new line to this table and leave the Cost column blank, SGM automatically enters a default cost of 5.

Linksets with the same cost form a combined linkset. Do not specify more than two linksets with the same cost, under the same destination point code and mask.

Step 6 The Destination Linkset field displays the destination linkset associated with the destination point code. The destination linkset is also known as the output linkset. To edit the destination linkset, select a destination linkset from the drop-down list box in this field.

Step 7 (Optional) The QoS field displays the quality of service (QoS) class of the route, as configured by the network administrator. To edit the QoS class of the route, select a QoS class from the drop-down list box in this field.

When you change the QoS class for a route, SGM automatically changes the QoS classes for the all other routes in that route set (that is, all other routes with the same Destination Point Code) to the new class.


78-15589-01


Step 8 (Optional) To add a new route to the route table, select the Dest. Point Code field in a blank row, then fill in the fields with values for the new route.

Step 9 (Optional) To delete an existing route from the route table, select one or more routes and click Delete. SGM removes the selected route or routes from the route table, without asking for confirmation.

Step 10 (Optional) To load an existing route table file, or to modify the list of route table files, select File > Load from the route table menu. SGM displays the Load File Dialog: Route Table File List (Figure 3-67).

Figure 3-67 Load File Dialog: Route Table File List

The Load File Dialog: Route Table File List contains the following fields:


• Name—Name of the route table file or folder.

• Last Modified—Date and time the route table file or folder was last modified.


78-15589-01


• Size (bytes)—Size of the route table file or folder, in bytes.

• Number of Files—Total number of route table files and folders (displayed in bottom left corner).

To load a route table file, enter the name of the file or select it in the list and click OK. SGM loads the route table file, closes the Load File Dialog: Route Table File List, and returns to the Route Table Dialog.

To delete a route table file from the route table file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.

To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: Route Table File List.

To close the Load File Dialog: Route Table File List without loading a route table file or saving any changes to the route table file list, click Cancel.

Step 11 (Optional) To revert to the last saved version of the route table file, select File> Revert from the route table menu. SGM displays the last saved version of the file.

Step 12 (Optional) To save the changes you have made to the route table file, or to modify the list of route table files, use one of the following procedures:

• To save the changes you have made to the route table file without changing the name of the file, select File > Save from the route table menu.

• To save the changes you have made to the route table file with a new name, select File > Save As from the route table menu. SGM displays the Save File Dialog: Route Table File List dialog (Figure 3-68).


78-15589-01


Figure 3-68 Save File Dialog: Route Table File List Dialog

The Save File Dialog: Route Table File List dialog contains the following fields:


• Name—Name of the route table file or folder.

• Last Modified—Date and time the route table file or folder was last modified.

• Size (bytes)—Size of the route table file or folder, in bytes.

• Filename—Name by which you want to save the route table file.

If you create a new route table file name, you can use any letters, numbers, or characters in the name that are allowed by your operating system. However, if you include any spaces in the new name, SGM converts those spaces to dashes. For example, SGM saves file “a b c” as “a-b-c”.

• Number of Files—Total number of route table files and folders (displayed in bottom left corner).


78-15589-01


To save the route table file with a new name, use one of the following procedures:


• To save the file with an existing name, overwriting an old route table file, select the name in the list and click OK.

SGM saves the route table file with the new name, closes the Save File Dialog: Route Table File List dialog, and returns to the Route Table Dialog.

Note If another user modifies and saves the route table file before you save your changes, SGM asks if you want to overwrite that user’s changes. If you choose to do so, the other user’s changes are overwritten and lost. If you choose not to do so, your changes are lost, unless you save the route table file to a different filename.

SGM stores the modified route table file in the route table file directory on the SGM server:

• If you installed SGM in the default directory, /opt, then the SGM route table file directory is /opt/CSCOsgm/routes.

• If you installed SGM in a different directory, then the SGM route table file directory is located in that directory.

You can use the sgm routedir command to change the directory in which SGM stores ITP route table files. See the “SGM Commands and Descriptions” section on page B-2 for information about the use of this command.

To delete a route table file from the route table file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.

To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: Route Table File List dialog.

To close the Save File Dialog: Route Table File List dialog without saving the route table file or saving any changes to the route table file list, click Cancel.

Step 13 (Optional) To exit the Route Table Dialog without saving any changes, click Cancel.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMEditing a Global Title Translation Table

Step 14 Copy the modified route table file from the SGM routes directory to a location that the ITP can reach via TFTP.

Step 15 TFTP the modified route table file back to the ITP.

Editing a Global Title Translation TableSGM enables you to configure Global Title Translation (GTT) entries using the SGM GUI.

A global title is an application address, such as an 800 number, calling card number, or mobile subscriber identification number. GTT is the process by which the Signaling Connection Control Part (SCCP) translates a global title into the point code and subsystem number (SSN) of the destination service switching point (SSP) where higher layer protocol processing occurs. GTT entries are stored in GTT files, which are comma-separated value (CSV) text files with point codes written in hexadecimal notation.

Note SGM 3.0 supports only GTT files with file format versions 2.0, 3.0, 3.1, or 4.0. You can load GTT files that use lower or higher file format versions, but fields or features that are unique to the lower or higher version are not displayed, they are removed from the GTT file the next time it is saved, and the file is saved as a version 2.0, 3.0, 3.1, or 4.0 file.

For more detailed information about GTT, including configuration procedures and scenarios, see the IP Transfer Point (ITP) feature module for Cisco IOS software release 12.2(4)MB4 or later.


78-15589-01


To edit a GTT file using SGM:

Step 1 Launch the SGM GTT client, using one of the following procedures:

• Select Products > Global Title Configurator from the SGM Main Menu.

• Select Start > Programs > Cisco SGM Client > Launch SGM GTT Client in Windows.

• Enter the sgm gttclient command. See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of this command.

Note The GTT Configurator runs as a separate application in SGM, so it requires a separate login, just like the SGM client.

Step 2 SGM displays the Startup Options dialog, which enables you to load a specific GTT file, or to create a new GTT file.

• If you choose to load an existing GTT file, SGM displays the Load File Dialog: GTT File List. See Step 22 for more information. Select a GTT file to load.

• If you choose to create a new GTT file, SGM displays the Create New Table Dialog. See Step 21 for more information. Create the new GTT file.

SGM displays the GTT Configurator window, with the Selectors and GTA tab selected (Figure 3-69).


78-15589-01


Figure 3-69 GTT Configurator, Showing Selectors and GTA Tab

The GTT Configurator window provides a set of tabs, each of which launches a specific GTT panel. Each panel is composed of a series of tables that contain GTT data. Some of the tables might be blank at first, while others are populated with rows of data.

You can edit the values in each row in each table, either by typing over the current value, or by selecting a new value from a drop-down list box.

To reset a cell to its previous value, press Esc. (If you have edited more than one cell in a row, pressing Esc resets all cells in the row.) To commit your changes, click outside the row. Once you have committed your changes, pressing Esc does not reset the cells in the row.

Step 3 (Optional) SGM enables you to modify the following aspects of the GTT Configurator window to meet your needs:

• Size and location of the main GTT Configurator window

• Variant and version of the last saved GTT file


78-15589-01


• Current selected tab (Selectors and GTA, App Group, MAPs, CPC, or Address Conversion)

• For each panel, the location of tables on that panel

• For each table:

– Column widths

– Sort-by column, and whether the sort is ascending or descending

SGM also enables you to save your modifications in a GTT preferences file, load an existing GTT preferences file, and modify the list of GTT preferences files.

To save your current preferences, or to modify the list of GTT preferences files, use one of the following procedures:

• To save the changes you have made to the GTT preferences file without changing the name of the file, select Edit > Preferences > Save from the GTT menu.

• To save the changes you have made to the GTT preferences file with a new name, select Edit > Preferences > Save As from the GTT menu. SGM displays the Save File Dialog: GTT Preferences File List (Figure 3-70).


78-15589-01


Figure 3-70 Save File Dialog: GTT Preferences File List

The Save File Dialog: GTT Preferences File List contains the following fields:


• Name—Name of the GTT preferences file or folder.

• Last Modified—Date and time the GTT preferences file or folder was last modified.

• Size (bytes)—Size of the GTT preferences file or folder, in bytes.

• Filename—Name by which you want to save the GTT preferences file. If you create a new GTT preferences file name, you can use any letters, numbers, or characters in the name that are allowed by your operating system.

• Number of Files—Total number of GTT preferences files and folders (displayed in bottom left corner).


78-15589-01


To save the GTT preferences file with a new name, use one of the following procedures:


• To save the file with an existing name, overwriting an old GTT preferences file, select the name in the list and click OK.

SGM saves the GTT file with the new name, closes the Save File Dialog: GTT Preferences File List, and returns to the GTT Configuration window.

Note If another user modifies and saves the GTT preferences file before you save your changes, SGM asks if you want to overwrite that user’s changes. If you choose to do so, the other user’s changes are overwritten and lost. If you choose not to do so, your changes are lost, unless you save the GTT preferences file to a different filename.

When you save a GTT file or GTT preferences file, SGM makes note of your preferences on the SGM client and server, including the variant and version of GTT being used. SGM saves the user’s preferences to the SGM server when the GTT client exits successfully.

Thereafter, whenever you launch the GTT client, SGM searches for your GTT preferences. If SGM finds your preferences on the SGM server, SGM launches the GTT client with those preferences. Otherwise, SGM launches the GTT client with the default GTT preferences file (ITU variant and version 1.0).

To delete a GTT preferences file from the GTT preferences file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.

To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: GTT Preferences File List.

To close the Save File Dialog: GTT Preferences File List without saving the GTT preferences file or saving any changes to the GTT preferences file list, click Cancel.

Step 4 (Optional) To load an existing GTT preferences file, select Edit > Preferences > Load from the GTT menu. SGM displays the Load File Dialog: GTT Preferences File List (Figure 3-71).


78-15589-01


Figure 3-71 Load File Dialog: GTT Preferences File List

The Load File Dialog: GTT Preferences File List contains the following fields:


• Name—Name of the GTT preferences file or folder.

• Last Modified—Date and time the GTT preferences file or folder was last modified.

• Size (bytes)—Size of the GTT preferences file or folder, in bytes.

• Number of Files—Total number of GTT preferences files and folders (displayed in bottom left corner).

To load a GTT preferences file, enter the name of the file or select it in the list and click OK. SGM loads the GTT preferences file, closes the Load File Dialog: GTT Preferences File List, and returns to the GTT Configuration window.

To delete a GTT preferences file from the GTT file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.


78-15589-01


To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: GTT Preferences File List.

To close the Load File Dialog: GTT Preferences File List without loading a GTT preferences file or saving any changes to the GTT preferences file list, click Cancel.

Step 5 (Optional) To revert to the last saved version of the GTT file, select File> Revert from the route table menu. SGM displays the last saved version of the file.

Step 6 Select the Selectors and GTA tab if you are primarily interested in displaying data for a specific GTT selector, and seeing the GTA entries for that selector. SGM displays the Selectors and GTA panel.

A GTT selector defines the parameters that select the translation table used to translate an SCCP message to its next or final destination.

A Global Title Address (GTA) entry is associated with a selector and defines the result of a translation for a particular address mask. The result of a GTA entry can be either a final translation or an intermediate translation

When you launch the Selectors and GTA panel, the Selector Table and the other tables might or might not be populated with data.

• To populate the Selector Table, right-click within the table and select Add from the right-click menu.

See Step 12 for more information about adding entries to the Selector Table.

• To populate the GTA Table, select a row in the Selector Table. The GTA Table is populated with all associated GTA entries. If the GTA Table remains blank, the selected row has no associated GTA entries.

If the GTA Table remains blank, the selected row has no associated GTA entries. You can also add entries to the GTA Table, by right-clicking within the table and selecting Add from the right-click menu. See Step 13 for more information about adding entries to the GTA Table.

• To populate the App Group Table, select a row in the GTA Table that has an associated Application Group. The App Group Table is populated with all application group entries for that application group name.

You can also add entries to the App Group Table, by right-clicking within the table and selecting Add from the right-click menu. See Step 15 for more information about adding entries to the App Group Table.


78-15589-01


• To populate the MAP Table, select a row in the GTA Table that does not have an associated Application Group. The MAP Table is populated with all MAP entries that match the selected row's point code-SSN combination.

You can also add entries to the MAP Table, by right-clicking within the table and selecting Add from the right-click menu. See Step 16 for more information about adding entries to the MAP Table.

• To populate the CPC List, select a row in the MAP Table that has an associated CPC List Name. The CPC List is populated with all point codes in that CPC list.

You can also add entries to the CPC List, by right-clicking within the list and selecting Add from the right-click menu. See Step 17 for more information about adding entries to the CPC List.

The Selector Table displays the following information:

• Name—Name of the selector.

• Translation Type—Translation type used by the selector. Valid values are integers in the range 0 through 255.

• Global Title Indicator—Global title indicator for the selector. Valid values are integers in the range 2 and 4.

• Numbering Plan—(China and ITU only) Numbering plan for the selector. Valid values are integers in the range 0 through 15.

• Nature of Address Indicator—(China and ITU only) Nature of address indicator for the selector. Valid values are integers in the range 0 through 127.

• Pre-Address Conversion—GTT address conversion table to apply prior to performing local GTT translation.

If there is an address conversion table name in this field, the referenced table must exist, and it must contain at least one address conversion entry.

If this field is blank, no address conversion is needed.

• Post-Address Conversion—GTT address conversion table to apply after performing local GTT translation.



• QoS—Quality of service (QoS) class of the selector. Valid QoS classes range from 1 through 7. ALL indicates that the selector accepts all QoS classes.


78-15589-01


The GTA Table displays the following information:

• Name—Name of the selector associated with this GTA.

• Global Title Address Digits—Address digits for the GTA.

• Point Code—Destination point code for the GTA.

• Routing Indicator—Routing indicator for the GTA. Valid values are:

– none—No routing indicator.

– gt—Route on the global title.

– pcssn—Route on the point code and SSN.

This field is grayed-out if Configure By App Group is selected.

• Subsystem Number—Destination SSN for the GTA. Valid values are integers in the range 2 through 255.

• New Translation Type—Translation type to be used by the GTA. Valid values are integers in the range 0 through 255.

• Application Group—Name of the application group that is to provide the point code, routing indicator, and SSN to be used by the GTA.

• Application Server Name—Name of the application server that is to provide the point code, routing indicator, and SSN to be used by the GTA.

For ITPs with multiple-instances enabled, do not use the same application group name in two or more different instances. For example, if you use application group name appgrp1 in instance 1, then do not use appgrp1 in instance 0, or any other instance.

• QoS—Quality of service (QoS) class of the GTA. Valid QoS classes range from 1 through 7. ALL indicates that the GTA accepts all QoS classes.

The App Group Table displays the following information:

• Name—Name of the application group.

• Multiplicity—Multiplicity setting for the application group. Valid values are:

– sha—Share equally between all destinations.

– cos—Use the destination with the least cost, if available.

– cgp—Use SCCP calling party address (CGPA) load sharing, if available.


78-15589-01


• Cost—Relative cost of the application group. Valid values are integers in the range 1 through 8.

• Point Code—Destination point code for the application group.

• Routing Indicator—Routing indicator for the application group. Valid values are:

– none—No routing indicator.

– gt—Route on the global title. This is the default routing indicator.


• Subsystem Number—Destination SSN for the application group. Valid values are integers in the range 2 through 255.

• Application Server Name—Name of the application server.

The MAP Table displays the following information:

• Primary Pt. Code—Primary point code for the MAP.

• Primary SSN—Primary SSN for the MAP. Valid values are integers in the range 2 through 255.

• Multiplicity—Multiplicity setting for the MAP. Valid values are:

– dom—Dominant. Always translate to the primary point code-SSN combination if it is available. Translate to the backup point code-SSN combination only if the primary combination is not available.

– sha—Share equally between the primary point code-SSN combination and the backup point code-SSN combination.

– sol—Solitary MAP. There is no alternate if the point code or SSN is not available.

• Backup Pt. Code—Backup point code for the MAP.

• Backup SSN—Backup SSN for the MAP. Valid values are integers in the range 2 through 255.

• Re-route if Congested—Indicates whether the MAP is to be routed to the backup point code-SSN combination if the primary combination is congested:

– If the checkbox is selected, the MAP is routed to the backup combination when the primary combination is congested.

– If the checkbox is cleared, the MAP is not routed to the backup.


78-15589-01


• Adjacency—Indicates whether a point code-SSN combination is to be considered adjacent to the local node for SCCP management:

– If the checkbox is selected, the point code-SSN combination is considered adjacent to the local node.

– If the checkbox is cleared, the point code-SSN combination is not considered adjacent to the local node.

• CPC List Name—Name of the CPC list associated with this MAP.

The CPC List displays the following information:

• Point Code—Point codes in the selected CPC list.

Step 7 Select the App Group tab if you are primarily interested in displaying data for application groups. SGM displays the App Group panel.

An application group is an alternative result for the explicit point code and SSN in a GTA entry. You can use an application group entry for intermediate translation, for load-sharing across more than two destinations, or for load-sharing of intermediate translation.

When you launch the App Group panel, the App Group Table and Selector Table might or might not be populated with data.

• To add entries to the App Group Table, right-click within the table and select Add from the right-click menu. See Step 15 for more information about adding entries to the App Group Table.

• To add entries to the Selector Table, right-click within the table and select Add from the right-click menu. See Step 12 for more information about adding entries to the Selector Table.

• To populate the MAP Table, select a row in the App Group Table. The MAP Table is populated with all MAP entries that match the selected row's point code-SSN combination.

You can also add entries to the MAP Table, by right-clicking within the table and selecting Add from the right-click menu. See Step 16 for more information about adding entries to the MAP Table.


78-15589-01




• To populate the GTA Table, select a row in the Selector Table. The GTA Table is populated with all associated GTA entries.

If the GTA Table remains blank, the selected row has no associated GTA entries. You can also add entries to the GTA Table, by right-clicking within the table and selecting Add from the right-click menu. See Step 13 for more information about adding entries to the GTA Table.

The App Group panel displays the same information as the Selectors and GTA panel, but from the perspective of the application groups.

Step 8 Select the MAPs tab if you are primarily interested in displaying data for MAPs. SGM displays the MAPs panel.

A mated application (MAP) entry has two main purposes:

• MAP entries are used internally by the SCCP application to track point code states and SSN states, such as congestion and availability.

• MAP entries are used to define backups or alternates for point code-SSN combination.

When you launch the MAPs panel, the MAP Table and Selector Table might or might not be populated with data.

• To add entries to the MAP Table, right-click within the table and select Add from the right-click menu. See Step 16 for more information about adding entries to the MAP Table.

• To add entries to the Selector Table, right-click within the table and select Add from the right-click menu. See Step 12 for more information about adding entries to the Selector Table.




78-15589-01


• To populate the App Group Table and GTA Table, select a row in the MAP Table. The App Group Table and GTA Table are populated with all application group and GTA entries that match the selected row's point code-SSN combination.

If the App Group Table or GTA Table remains blank, the selected row has no associated application group or GTA entries.

You can add entries to the App Group Table, by right-clicking within the table and selecting Add from the right-click menu. See Step 15 for more information about adding entries to the App Group Table.

You can add entries to the GTA Table, by right-clicking within the table and selecting Add from the right-click menu. See Step 13 for more information about adding entries to the GTA Table.

The MAPs panel displays the same information as the Selectors and GTA panel, but from the perspective of the MAPs.


78-15589-01


Step 9 Select the CPC tab if you are primarily interested in displaying data for concerned point code names. SGM displays the CPC panel (Figure 3-72).

Figure 3-72 GTT Configurator, Showing CPC Tab

A concerned point code (CPC) is a node that is to be notified when the status of the associated SSN changes.

When you launch the CPC panel, the Concerned Pt. Code Name List is populated with data. To populate the CPC List and MAP Table, select a row in the Concerned Pt. Code Name List. The CPC List and MAP Table are populated with all point codes and MAP entries that match that concerned point code name.

The CPC panel displays the CPC List and MAP Table, as well as the Concerned Pt. Code Name List. The Concerned Pt. Code Name List displays the CPC List Name, which is the name of the CPC list to be added. Enter 1-to-12-character alphanumeric string.


78-15589-01


To copy one or more point codes from one CPC list to another, select a CPC list in the CPC List Name column. SGM displays the point codes associated with that CPC list in the Point Code column. Select one or more of the point codes and drag them to the new CPC list while holding down the left mouse button.

Note SGM copies the point codes to the new CPC list; it does not move them from the old CPC list. If you want to move the point codes, you must copy them to the new CPC list, then delete them from the old CPC list.

Step 10 Select the Address Conversion tab if you are primarily interested in displaying GTT address conversion tables. SGM displays the Address Conversion panel (Figure 3-73).

Figure 3-73 GTT Configurator, Showing Address Conversion Tab


78-15589-01


The Address Conversion Table displays the following information:

• Name—Name of the GTT address conversion table. Enter a 1-to-12 character name.

• Numbering Plan—(China and ITU only) Numbering plan associated with the address conversion table. For all addresses that are converted, the numbering plan is converted to the value of this field. The valid range is 0 to 15.

• Nature of Address Indicator—(China and ITU only) Nature of address indicator associated with the address conversion table. For all addresses that are converted, the nature of address indicator is converted to the value of this field. The valid range is 0 to 127.

The Conversion Entry Table displays the following information:

• In Address—Input SCCP address entry. Enter an address as a 1 to 15 digit hexadecimal string.

• Out Address—Output SCCP address entry. Enter an address as a 1 to 15 digit hexadecimal string.

• Numbering Plan—(China and ITU only) Numbering plan associated with this entry in the address conversion table. If specified, the value of this field overrides the value of the Numbering Plan field in the Address Conversion Table, for this entry. The valid range is 0 to 15.

• Nature of Address Indicator—(China and ITU only) Nature of address indicator associated with this entry in the address conversion table. If specified, the value of this field overrides the value of the Nature of Address Indicator field in the Address Conversion Table, for this entry. The valid range is 0 to 127.

The Selector Table for Address Conversion displays the following information:

• Name—Name of the selector.

• Translation Type—Translation type used by the selector. Valid values are integers in the range 0 through 255.

• Global Title Indicator—Global title indicator for the selector. Valid values are integers in the range 2 and 4.

• Numbering Plan—(China and ITU only) Numbering plan for the selector. Valid values are integers in the range 0 through 15.


78-15589-01


• Nature of Address Indicator—(China and ITU only) Nature of address indicator for the selector. Valid values are integers in the range 0 through 127.

• Pre-Address Conversion—GTT address conversion table to apply prior to performing local GTT translation.



• Post-Address Conversion—GTT address conversion table to apply after performing local GTT translation.



• QoS—Quality of service (QoS) class of the selector. Valid QoS classes range from 1 through 7. ALL indicates that the selector accepts all QoS classes.

Step 11 (Optional) To change the variant and instance ID associated with a GTT file select Edit> Version and Instance from the GTT menu. SGM displays the Edit GTT Table dialog (Figure 3-74).

Figure 3-74 Edit GTT Table Dialog


78-15589-01


The Edit GTT Table dialog contains the following fields and buttons:

• Variant—SS7 protocol variant. You cannot edit this field.

• Version—Version of the file format to be used by the GTT. Valid versions are:

– 2.0 (MB5, MB6)—Corresponds to ITP software releases 12.2(4)MB5 and 12.2(4)MB6. Allows GTT translation to an application server.

– 3.0 (MB7, MB8)—Corresponds to ITP software releases 12.2(4)MB7 and 12.2(4)MB8. Allows local point codes in GTT tables.

– 3.1 (MB9, MB9a)—Corresponds to ITP software releases 12.2(4)MB9 and 12.2(4)MB9a. Two or more entries in the same application group can have the same cost. This is the default version in SGM.

– 4.0 (MB10+)—Corresponds to ITP software release 12.2(4)MB10 or greater. Supports multiple instances on a single node.

SGM 3.0 does not support version 1.0, which corresponds to ITP software release 12.2(4)MB4. You can load a version 1.0 file into SGM, but fields or features that are unique to version 1.0 are not displayed, they are removed from the GTT file the next time it is saved, and the file is saved as a version 2.0 file.

• Instance ID—ID of the instance used by the GTT. Valid IDs are 0 to 7. The default instance ID is 0. This list box is available only if Version 4.0 or later is selected.

Enter or select values for the new variant and instance ID, then click OK. SGM saves your changes to the GTT file.

To close the Edit GTT Table dialog at any time without saving any changes to the GTT file, click Cancel.

Step 12 (Optional) To add a new selector to a Selector Table, select a Selector Table, then use one of the following procedures:

• Select Edit > Add from the GTT menu.

• Select Add from the right-click menu.

SGM displays the Selector Add Dialog (Figure 3-75).


78-15589-01


Figure 3-75 Selector Add Dialog

The Selector Add Dialog contains the following fields:

• Selector Name—Name of the selector to be added. Enter 1-to-12-character alphanumeric string.

• Translation Type—Translation type to be used by the selector. Enter an integer in the range 0 through 255.

• Global Title Indicator—Global title indicator for the selector. Select a value from the drop-down list box. Valid values are:

– 2

– 4—This is the default value.

• Numbering Plan—(China and ITU only) Numbering plan for the selector. Enter an integer in the range 0 through 15. This field is grayed-out if Global Title Indicator is set to 2.

• Nature of Addr. Indicator—(China and ITU only) Nature of address indicator for the selector. Enter an integer in the range 0 through 127. This field is grayed-out if Global Title Indicator is set to 2.

• Pre-Conversion Table name—GTT address conversion table to apply prior to performing local GTT translation.




78-15589-01


• Post-Conversion Table name—GTT address conversion table to apply after performing local GTT translation.



• QoS—Quality of service (QoS) class of the selector. Select a value from the drop-down list box. Valid QoS classes range from 1 through 7. Select ALL if you want the selector to accept all QoS classes. The default value is ALL.

Enter or select values for the new selector, then click Add. SGM adds the selector to the Selector Table.

When you are done adding selectors, click Close to close the Selector Add Dialog.

Step 13 (Optional) To add a new GTA entry to a GTA Table, select a GTA Table, then use one of the following procedures:



SGM displays the Selector Add Dialog (Figure 3-76).


78-15589-01


Figure 3-76 GTA Add Dialog

The GTA Add Dialog contains the following fields:

• Selector Name—Name of the selector associated with this GTA. You cannot edit this field.

• Global Title Addr. Digits—Address digits for the GTA. Enter a 1 to 15 digit hexadecimal string.

• QoS—Quality of service (QoS) class of the GTA. Select a value from the drop-down list box. Valid QoS classes range from 1 through 7. Select ALL if you want the GTA to accept all QoS classes. The default value is ALL.


78-15589-01


• Configure By Point Code—Indicates whether to configure the GTA by point code. To configure the GTA by point code, select this radio button.

SGM makes the Config By Point Code fields available, and grays-out the Config By App Group fields. This is the default setting.

• Configure By App Group—Indicates whether to configure the GTA by application group. To configure the GTA by application group, select this radio button.

SGM makes the Config By App Group fields available, and grays-out the Config By Point Code fields.

• Configure By Application Server Name—Indicates whether to configure the GTA by application server name. To configure the GTA by application server name, select this radio button.

SGM replaces the Config By Point Code fields with the Config By Application Server name fields, and grays-out the Config By App Group fields.

• Point Code—Destination point code for the GTA. Enter a point code. This field is available only if Configure By Point Code is selected.

• Routing Indicator—Routing indicator for the GTA. Select a value from the drop-down list box. Valid values are:



This field is available only if Configure By Point Code or Configure By Application Server Name is selected.

• Subsystem Number—Destination SSN for the GTA. Enter an integer in the range 2 through 255. This field is mutually exclusive with the New Translation Type field. This field is available only if Configure By Point Code or Configure By Application Server Name is selected.

• New Translation Type—Translation type to be used by the GTA. Enter an integer in the range 0 through 255. This field is mutually exclusive with the Subsystem Number field. This field is available only if Configure By Point Code or Configure By Application Server Name is selected.


78-15589-01


• App. Group—Name of the application group that is to provide the point code, routing indicator, and SSN to be used by the GTA. Enter the name of an application group. This field is available only if Configure By App Group is selected.

• Application Server Name—Name of the application server that is to provide the point code, routing indicator, and SSN to be used by the GTA. Enter the name of an application server. This field is available only if Configure By Application Server Name is selected.

Enter or select values for the new GTA entry, then click Add. SGM adds the GTA entry to the GTA Table.

When you are done adding GTA entries, click Close to close the GTA Add Dialog.

Step 14 (Optional) To search the GTA Table for the Global Title Address Digits for a specific selector, select the Selectors and GTA tab, then select View > Phone Number Config from the GTT menu. SGM displays the The Phone Number Lookup Dialog (Figure 3-77).


78-15589-01


Figure 3-77 Phone Number Lookup Dialog

The Phone Number Lookup Dialog contains the following tables, field, and buttons:

• Selector Table—Selector Table associated with the GTA Table to be searched. Select one or more Selector Tables. For descriptions of the fields in this table, and the other tables in the Phone Number Lookup Dialog, see Step 6.

• Phone Number—GTA digits to be searched for in the GTA Table.

• Perform Lookup—Launches the search for the GTA digits.


78-15589-01


• Pre-Address Conversion Entry Used—Entry in the GTT address conversion table used for pre-address conversion, if the Selector Table being searched performs pre-address conversion.

For China and ITU variants, pre-address conversion might result in a numbering plan or nature of address indicator that is different from the selected Selector Table. If this occurs, SGM searches for a selector in the Selector Table that matches the new numbering plan and nature of address indicator:

– If SGM finds a matching selector, SGM uses that selector to complete the search.

– If SGM does not find a matching selector, the search fails.

• Pre-Address Conversion Results—Results of the pre-address conversion (converted address, numbering plan, and nature of address indicator), if the Selector Table being searched performs pre-address conversion.

• Selector Entry Used—Selector Entry that was searched.

• GTA Entry Found—GTA Table in which the GTA digits were found.

• MAP Table—MAP Table, if any, associated with the GTA Table in which the GTA digits were found.

• CPC List—CPC List, if any, associated with the GTA Table in which the GTA digits were found.

• Post-Address Conversion Entry Used—Entry in the GTT address conversion table used for post-address conversion, if the Selector Table being searched performs post-address conversion.

• Post-Address Conversion Results—Results of the post-address conversion (converted address, numbering plan, and nature of address indicator), if the Selector Table being searched performs post-address conversion.

To search for Global Title Address Digits, select a Selector Table and enter a telephone number or prefix as a 1 to 15 digit hexadecimal string. For example, to search for a specific telephone number, such as 919-555-6384, enter 9195556384. To search for all entries that begin with the 919-555 telephone prefix, enter 919555.


78-15589-01


Click Perform Lookup to launch the search:

• If one or more matching entries are found, displays the entries that contained the GTA digits in the GTA Table.

• If the Selector Table being searched performs pre-address conversion, the converted address, numbering plan, and nature of address indicator are displayed in the Pre-Address Conversion Results field.

• If the Selector Table being searched performs post-address conversion, the converted address, numbering plan, and nature of address indicator are displayed in the Post-Address Conversion Results field.

• If no matching entries are found, or if the Selector Table has no associated GTA Table, displays Could not find GTA for selector and phone number at the bottom of the window.

Step 15 (Optional) To add a new application group entry to an App Group Table, select an App Group Table, then use one of the following procedures:



SGM displays the App Group Add Dialog (Figure 3-78).


78-15589-01


Figure 3-78 App Group Add Dialog

The App Group Add Dialog contains the following fields:

• App. Group—Name of the application group to be added. Enter 1-to-12-character alphanumeric string.

• Multiplicity—Multiplicity setting for the application group. Select a value from the drop-down list box. Valid values are:

– sha—Share equally between all destinations. This is the default value.

– cos—Use the destination with the least cost, if available.

– cgp—Use SCCP calling party address (CGPA) load sharing, if available.

• Cost—Relative cost of the application group. Select a relative cost, 1 through 8, from the drop-down list box. The default value is 1.

• Point Code—Destination point code for the application group. Select this radio button and enter a point code. This field is mutually exclusive with Application Server Name.

• Application Server Name—Name of the application server. Select this radio button and enter an application server name. This field is mutually exclusive with Point Code.


78-15589-01


• Routing Indicator—Routing indicator for the application group. Select a value from the drop-down list box. Valid values are:



• Subsystem Number—Destination SSN for the application group. Enter an integer in the range 2 through 255.

Enter or select values for the new application group entry, then click Add. SGM adds the application group entry to the App Group Table.

When you are done adding application group entries, click Close to close the App Group Add Dialog.

Step 16 (Optional) To add a new MAP entry to a MAP Table, select a MAP Table, then use one of the following procedures:



SGM displays the MAP Add Dialog (Figure 3-79).


78-15589-01


Figure 3-79 MAP Add Dialog

The MAP Add Dialog contains the following fields:

• Primary Pt. Code—Primary point code for the MAP. Enter a point code.

• Primary SSN—Primary SSN for the MAP. Enter an integer in the range 2 through 255.

• Multiplicity—Multiplicity setting for the MAP. Select a value from the drop-down list box. Valid values are:

– dom—Dominant. Always translate to the primary point code-SSN combination if it is available. Translate to the backup point code-SSN combination only if the primary combination is not available.

– sha—Share equally between the primary point code-SSN combination and the backup point code-SSN combination. This is the default value.

– sol—Solitary MAP. There is no alternate if the point code or SSN is not available.

• Backup Pt. Code—Backup point code for the MAP. Enter a point code.

• Backup SSN—Backup SSN for the MAP. Enter an integer in the range 2 through 255.


78-15589-01


• CPC List Name—Name of the CPC list to be associated with this MAP. Enter a CPC list name.

• Re-route if Congested—Indicates whether the MAP is to be routed to the backup point code-SSN combination if the primary combination is congested:

– If you want to route the MAP to the backup combination when the primary combination is congested, select the checkbox.

– If you do not want to route the MAP to the backup, clear the checkbox. This is the default setting.

• Adjacency—Indicates whether a point code-SSN combination is to be considered adjacent to the local node for SCCP management:

– If you want the point code-SSN combination be considered adjacent to the local node, select the checkbox.

– If you do not want the point code-SSN combination be considered adjacent to the local node, clear the checkbox. This is the default setting.

Enter or select values for the new MAP entry, then click Add. SGM adds the MAP entry to the MAP Table.

When you are done adding MAP entries, click Close to close the MAP Add Dialog.


78-15589-01


Step 17 (Optional) To add a new CPC list to a CPC Table, select a Concerned Pt. Code Name List or a CPC List, then use one of the following procedures:



SGM displays the CPC Add Dialog (Figure 3-80).

Figure 3-80 CPC Add Dialog

The CPC Add Dialog contains the following fields:

• CPC List Name—Name of the CPC list to be added. Enter 1-to-12-character alphanumeric string.

• Concerned Pt. Code List—One or more CPCs to be added to the new CPC list. Enter one or more CPCs, separated by spaces.

Enter or select values for the new CPC list, then click Add. SGM adds the CPC list to the MAP Table.

When you are done adding CPC lists, click Close to close the CPC Add Dialog.


78-15589-01


Step 18 (Optional) To add a new Address Conversion Table, select an Address Conversion Table, then use one of the following procedures:

• Select Edit> Add from the GTT menu.


SGM displays the Address Conversion Add Dialog for a Table (Figure 3-81).

Figure 3-81 Address Conversion Add Dialog for a Table

The Address Conversion Add Dialog for a Table contains the following fields:

• Name—Name of the GTT address conversion table. Enter a 1-to-12 character name.



Enter or select values for the new Address Conversion Table, then click Add. SGM adds the Address Conversion Table to the GTT file.

When you are done adding Address Conversion Tables, click Close to close the Address Conversion Add Dialog for a Table.


78-15589-01


Step 19 (Optional) To add a new entry to a Conversion Entry Table, select a Conversion Entry Table, then use one of the following procedures:

• Select Edit> Add from the GTT menu.


SGM displays the Address Conversion Add Dialog for an Entry (Figure 3-82).

Figure 3-82 Address Conversion Add Dialog for an Entry

The Address Conversion Add Dialog for an Entry contains the following fields:

• Name—Name of the GTT address conversion table. Enter a 1-to-12 character name. If the table name does not already exist, SGM creates a new address conversion table with this name.




78-15589-01


• In Address—Input SCCP address entry. Enter an address as a 1 to 15 digit hexadecimal string.

• Out Address—Output SCCP address entry. Enter an address as a 1 to 15 digit hexadecimal string.

• Numbering Plan—(China and ITU only) Numbering plan associated with this entry in the address conversion table. If specified, the value of this field overrides the value of the Numbering Plan field in the Address Conversion Table, for this entry. The valid range is 0 to 15.

• Nature of Address Indicator—(China and ITU only) Nature of address indicator associated with this entry in the address conversion table. If specified, the value of this field overrides the value of the Nature of Address Indicator field in the Address Conversion Table, for this entry. The valid range is 0 to 127.

Enter or select values for the new entry, then click Add. SGM adds the entry to the Conversion Entry Table.

When you are done adding entries, click Close to close the Address Conversion Add Dialog for an Entry.

Step 20 (Optional) To delete one or more rows from a table, select the rows, then select Edit > Delete from the GTT menu or Delete from the right-click menu. SGM displays the Confirm Delete Dialog to confirm the deletion:

• To delete the selected rows, click Yes. The rows are deleted from the table and the Confirm Delete Dialog is closed.

• To retain the selected rows, click No. The rows are kept in the table and the Confirm Delete Dialog is closed.

You can select more than one row to delete, but all selected rows must be in the same table. For example, you cannot delete rows from both the Selector Table and the MAP Table at the same time.

If deleting a row from a table “orphans” one or more rows in the table, such that no remaining entries reference the orphaned rows, SGM displays the number of orphaned rows and asks whether you want to also delete the orphaned rows. (SGM displays the number of rows and not the rows themselves, because there could be thousands of orphaned rows.)

Step 21 (Optional) To create a new GTT file, select File > New Table from the GTT menu. SGM displays the Create New Table Dialog (Figure 3-83).


78-15589-01


Figure 3-83 Create New Table Dialog

The Create New Table Dialog contains the following fields:

• Variant—SS7 p[rotocol variant. Valid variants are:

– ANSI

– China

– ITU







• Instance ID—ID of the instance to be used by the GTT. Valid IDs are 0 to 7. The default instance ID is 0. This list box is available only if Version 4.0 or later is selected.


78-15589-01


Select a variant, version, and instance for the new GTT file, then click OK. SGM creates the new GTT file and closes the Create New Table Dialog.

To close the Create New Table Dialog without creating a new GTT file, click Cancel.

Step 22 (Optional) To load an existing GTT file, or to modify the list of GTT files, select File > Load from the GTT menu. SGM displays the Load File Dialog: GTT File List (Figure 3-84).

Figure 3-84 Load File Dialog: GTT File List

The Load File Dialog: GTT File List contains the following fields:


• Name—Name of the GTT file or folder.

• Last Modified—Date and time the GTT file or folder was last modified.


78-15589-01


• Size (bytes)—Size of the GTT file or folder, in bytes.

• Number of Files—Total number of GTT files and folders (displayed in bottom left corner).

To load a GTT file, enter the name of the file or select it in the list and click OK. SGM closes the Load File Dialog: GTT File List and displays the Progress Dialog (Figure 3-85).

Figure 3-85 Progress Dialog

The Progress Dialog displays the progress of the GTT file load, as well as any messages generated while loading the file.

To stop loading the file, click Cancel.

When the file has been loaded, click OK. SGM closes the Progress Dialog, loads the GTT file, and returns to the GTT Configuration window.

When you load a GTT file, the name of the server associated with the GTT client and the filename are displayed in the window name:

SGM: GTT Configurator -- sgm-sun8 -- GTT.File.1


78-15589-01


If you have not yet loaded or saved a GTT file, SGM displays No File Loaded in place of the GTT file name.

To delete a GTT file from the GTT file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.

To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: GTT File List.

To close the Load File Dialog: GTT File List without loading a GTT file or saving any changes to the GTT file list, click Cancel.

Step 23 SGM strongly recommends that you to check the semantics of a GTT file against a specific ITP, validating the following data in the GTT file:

• ITP Point Code—For version 2.0 GTT files, the point code in the GTT file cannot be the same as the ITP's primary, secondary, or capability point code. If it is the same, SGM generates an Error.

This is not a restriction for GTT files of version 3.0 or later.

• Route Table—The ITP’s route table must contain all point codes in the GTT file, other than the ITP’s primary, secondary, or capability point code. If the route table does not contain the point codes, SGM generates an Error.

• Route Status—All route entries for point codes in the GTT file, other than the ITP’s primary, secondary, or capability point code, must be available. If they are not, SGM generates a Warning.

• GTA and Application Group—If either the GTA or the application group is configured by an application server, then that application server must exist on the ITP. If it does not exist, SGM generates an Error.

If the application server exists on the ITP, but it is not available, SGM generates a Warning.

For example, ITP limits XUA configuration to instance 0. The SGM semantic check verifies that XUA is not configured on any other instance.

To check the semantics of a GTT file, select File > Semantic Check from the GTT menu. SGM displays the Semantic Check GTT dialog (Figure 3-86).


78-15589-01


Figure 3-86 Semantic Check GTT Dialog

The Semantic Check GTT dialog contains the following fields:

• ITP Name or IP Address—Name or IP address of the ITP against which to check the GTT file.

Enter the name or IP address of an ITP and click OK. SGM closes the Semantic Check GTT dialog and opens the Progress Dialog (Figure 3-85).

The Progress Dialog displays the progress of the semantic check for the GTT file, as well as any messages generated while checking the file.

To cancel the check, click Cancel.

When the check is complete, click OK. SGM closes the Progress Dialog and returns to the Semantic Check GTT dialog.

To close the Semantic Check GTT dialog without checking the semantics of the GTT file, click Cancel.

Note You can also use the sgm gttcheck command to semantics of a GTT file. For more information on the use of this command, see the “SGM Commands and Descriptions” section on page B-2.

Step 24 (Optional) To display basic information about the currently displayed GTT file, select View > GTT Table Info from the GTT menu. SGM displays the GTT Table Info Dialog (Figure 3-87).


78-15589-01


Figure 3-87 GTT Table Info Dialog

The GTT Table Info Dialog contains the following fields:

• Filename—Name of the GTT file.







• Variant—SS7 p[rotocol variant. Valid variants are:

– ANSI

– China

– ITU


78-15589-01


• Instance ID—ID of the instance used by the GTT. Valid IDs are 0 to 7. The default instance ID is 0. If there is no instance associated with the GTT, this field displays N/A.

• Last Modified—Date and time the GTT file was last modified.

• Total Entries—Total number of entries in the GTT file.

Click OK to close the GTT Table Info Dialog.

Step 25 (Optional) To save the changes you have made to the GTT file, or to modify the list of GTT files, use one of the following procedures:

• To save the changes you have made to the GTT file without changing the name of the file, select File > Save from the GTT menu.

• To save the changes you have made to the GTT file with a new name, select File > Save As from the GTT menu. SGM displays the Save File Dialog: GTT File List (Figure 3-88).

Figure 3-88 Save File Dialog: GTT File List


78-15589-01


The Save File Dialog: GTT File List contains the following fields:


• Name—Name of the GTT file or folder.

• Last Modified—Date and time the GTT file or folder was last modified.

• Size (bytes)—Size of the GTT file or folder, in bytes.

• Filename—Name by which you want to save the GTT file.

If you create a new GTT file name, you can use any letters, numbers, or characters in the name that are allowed by your operating system. However, if you include any spaces in the new name, SGM converts those spaces to dashes. For example, SGM saves file “a b c” as “a-b-c”.

• Number of Files—Total number of GTT files and folders (displayed in bottom left corner).

To save the GTT file with a new name, use one of the following procedures:


• To save the file with an existing name, overwriting an old GTT file, select the name in the list and click OK.

SGM closes the Save File Dialog: GTT File List and displays the Progress Dialog (Figure 3-85).

The Progress Dialog displays the progress of the GTT file save, as well as any messages generated while saving the file.

To stop saving the file, click Cancel.

When the file has been saved, click OK. SGM closes the Progress Dialog, saves the GTT file with the new name, and returns to the GTT Configuration window.

Note If another user modifies and saves the GTT file before you save your changes, SGM asks if you want to overwrite that user’s changes. If you choose to do so, the other user’s changes are overwritten and lost. If you choose not to do so, your changes are lost, unless you save the GTT file to a different filename.


78-15589-01


To delete a GTT file from the GTT file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.

To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: GTT File List.

To close the Save File Dialog: GTT File List without saving the GTT file or saving any changes to the GTT file list, click Cancel.

Step 26 When you are ready to exit the GTT Configurator window, select File > Exit from the GTT menu.

If you have made any changes to the GTT file, SGM asks if you want to save the changes before leaving the window:

• Click Yes to save the changes.

SGM opens the Save File Dialog: GTT File List, which enables you to save the GTT file with a new name, or overwrite an existing GTT file.

SGM then opens the Save File Dialog: GTT Preferences File List, which enables you to save the GTT preferences file with a new name, or overwrite an existing GTT preferences file.

• Click No to close the prompt window.

SGM automatically saves your GTT preferences, then closes the GTT Configurator window without saving any changes to the GTT file.

By default, GTT files and GTT preferences files are located in the SGM installation directory:

• If you installed SGM in the default directory, /opt, then the default directory is /opt/CSCOsgm/gtt.

• If you installed SGM in a different directory, then the default directory is located in that directory.

To change the directory in which SGM stores GTT files, use the sgm gttdir command. See the “SGM Commands and Descriptions” section on page B-2 form more information on the use of this command.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMWorking with SGM Statistics Reports

Working with SGM Statistics ReportsOnce every hour, SGM gathers critical information from all known nodes, signaling points, linksets, and links. SGM then uses that information to calculate statistics, and generates reports based on those statistics.

SGM enables you to:

• View and export detailed network link and linkset statistics summary reports.

• View and export detailed accounting statistics reports.

• Create, view, and export custom statistics reports.

• View and export point code inventory reports.

• Modify the way SGM displays information in reports.

By default, SGM stores all reports in the report files directory, /reports:

• If you installed SGM in the default directory, /opt, then the default report files directory is /opt/CSCOsgm/reports.

• If you installed SGM in a different directory, then the default report files directory is located in that directory.

The /reports directory contains the following subdirectories:

• /daily—Contains all daily report files, stored in .Z format.

• /exportdaily—Contains all daily report files, edited and formatted for export, stored as Zip files.

• /hourly—Contains all hourly report files, stored in .Z format.

• /exporthourly—Contains all hourly report files, edited and formatted for export, stored as Zip files.

• /exportrolling—Contains all rolling report files, edited and formatted for export, stored as Zip files. SGM rebuilds the files in this subdirectory every hour.


78-15589-01


• /custom—Contains all custom report files. These are the report files generated using the sgm accstats and sgm linkstats commands.

Each file is identified with a unique ID tag, specified when the sgm accstats or sgm linkstats command was entered. If the user did not specify an ID tag, SGM uses the process ID of the sgm accstats or sgm linkstats command.

• /etc—Contains additional files used by the SGM reporting scripts and Web pages, including the nodes.include, linksets.include, nodes.exclude, and linksets.exclude files, if they exist.


• Modifying the Way SGM Handles Statistics Reports (Solaris Only), page 3-335

• Changing the SGM Reports Directory (Solaris Only), page 3-342

• Viewing SGM Network Statistics Reports, page 3-343

• Viewing SGM Accounting Statistics Reports, page 3-364

• Generating and Viewing Custom SGM Statistics Reports, page 3-369

• Viewing SGM Point Code Inventory Reports, page 3-390

• Viewing SGM Statistics Reports Logs, page 3-394

Modifying the Way SGM Handles Statistics Reports (Solaris Only)

SGM enables you to modify the following aspects of statistics reports:

• To specify whether SGM is to generate network statistics reports, enter the sgm statreps [disable | enable] command:

– To generate network statistics reports, enter sgm statreps enable. This is the default setting.

– To not generate network statistics reports, enter sgm statreps disable.


78-15589-01


• To specify whether SGM is to generate network statistics reports in export format, enter the sgm statreps [export | noexport] command:

– To generate network statistics reports in export format, enter sgm statreps export. This is the default setting.

– To not generate network statistics reports in export format, enter sgm statreps noexport.

• To specify whether SGM is to generate accounting statistics reports, enter the sgm statreps [acct | noacct] command:

– To generate accounting statistics reports, enter sgm statreps acct. Accounting must be enabled on the links in order for SGM to generate accounting statistics.

– To not generate accounting statistics reports, enter sgm statreps noacct. This is the default setting.

• To specify whether SGM is to include links that use the Stream Control Transmission Protocol (SCTP) IP transport protocol in network statistics reports, enter the sgm statreps [iplinks | noiplinks] command:

– To include SCTPIP links, enter sgm statreps iplinks. This is the default setting.

– To not include SCTPIP links, enter sgm statreps noiplinks.

• To specify whether SGM is to include links that do not have planned send and receive capacities in network statistics reports, enter the sgm statreps [nullcaps | nonullcaps] command:

– To include links that do not have planned send and receive capacities, enter sgm statreps nullcaps. This is the default setting.

– To not include links that do not have planned send and receive capacities, enter sgm statreps nonullcaps.

• To set the time mode for dates in network statistics reports, enter the sgm statreps timemode [12 | 24] command:

– To use 24-hour time, also called military time, enter sgm statreps timemode 24. 1:00 in the afternoon is 13:00. This is the default setting.

– To use 12-hour time, with AM and PM, enter sgm statreps timemode 12. 1:00 in the afternoon is 1:00 PM.


78-15589-01


• To specify whether SGM is to verify that a disk has at least 10 MB of space remaining before generating network statistics reports, enter the sgm statreps [diskcheck | nodiskcheck] command:

– To verify the disk space, enter sgm statreps diskcheck. This is the default setting.

– To not verify the disk space, enter sgm statreps nodiskcheck.

• To specify whether SGM is to display a gray background in the Send Utilization or Receive Utilization cell in a network statistics report, if the following condition is met:

Current Utilization > factor * Long-Term Utilization

enter the sgm statreps utilratio command. The default value for factor is 1.5.

• To specify whether SGM is to display a gray background in the InSrv cell in a network statistics report, if the following condition is met:

Current In-Service < factor * Long-Term In-Service

enter the sgm statreps servratio command. The default value for factor is 0.95.

• To set the maximum number of days SGM is to archive hourly network statistics reports, enter the sgm statreps hourlyage or sgm rephourlyage command. The default setting is 31 days.

• To set the maximum number of days SGM is to archive daily network statistics reports, enter the sgm statreps dailyage or sgm repdailyage command. The default setting is 90 days.

• To set the maximum number of days SGM is to archive custom network statistics reports, enter the sgm repcustage command. The default setting is 10 days.

• To specify whether SGM is to show real node names or display names in Web pages, enter the sgm webnames command:

– To show the real DNS names of nodes, as discovered by SGM, enter sgm webnames real. This is the default setting.

– To show display names, enter sgm webnames display. Display names are new names that you specify for nodes. For more information about display names, see the “Editing a Node” section on page 3-124.


78-15589-01


• To specify whether SGM is to display send and receive utilization for linksets and links as percentages or in Erlangs in Web pages, enter the sgm webutil command:

– To display utilization as a percentage, enter sgm webutil percent. This is the default setting.

– To show display utilization in Erlangs, enter sgm webutil erlangs.

See the “Working with SGM Statistics Reports” section on page 3-334 for more information on send and receive utilization for linksets and links.

• To display the current status of all SGM network statistics report parameters, enter the sgm statreps status command.

• To display the timer file for SGM network statistics reports, enter the sgm statreps timer command. The timer file is useful for identifying how much time SGM spends gathering report data and generating reports.

• To include only specific nodes or signaling points in reports, create the user-defined nodes.include file and list the nodes and signaling points in the file. Only those nodes and signaling points will be included in automatically generated SGM accounting statistics and network statistics reports, as well as in custom reports that were generated with the default keyword (or no node-list keyword at all) on the sgm accstats or sgm linkstats command.

Keep in mind the following considerations:

– If you installed SGM in the default directory, /opt, then the nodes.include file is located at /opt/CSCOsgm/reports/etc/nodes.include.

If you installed SGM in a different directory, or if you moved the report files directory using the sgm repdir command, then the /reports/etc/nodes.include file is located in that directory.

– Each line in the nodes.include file must contain a single node name, or node name and signaling point name, that matches exactly the real, fully qualified node name of the node, and each line must end with a colon (:). For example:

sgm-75-59a.cisco.com:



78-15589-01


To include a specific signaling point, specify the node name and signaling point:

sgm-75-59a.cisco.com;net0:


– Wildcard matching is not supported.

– If a node or signaling point appears in both the nodes.include file and the nodes.exclude file, it is excluded. That is, excluding a node or signaling point overrides including the same node or signaling point.

– If you specify a special include file on the sgm accstats or sgm linkstats command, SGM ignores the nodes.include file. See the “Including Specific Nodes in Custom Reports” section on page 3-374 for more information on the special include file.

• To include only specific linksets in reports, create the user-defined linksets.include file and list the linksets in the file. Only those linksets will be included in automatically generated SGM accounting statistics and network statistics reports, as well as in custom reports that were generated with the default keyword (or no node-list keyword at all) on the sgm accstats or sgm linkstats command.


– If you installed SGM in the default directory, /opt, then the linksets.include file is located at /opt/CSCOsgm/reports/etc/linksets.include.

If you installed SGM in a different directory, or if you moved the report files directory using the sgm repdir command, then the /reports/etc/linksets.include file is located in that directory.

– Each line in the linksets.include file must contain a single linkset name that matches exactly the real, fully qualified linkset name of the linkset, including the node name and signaling point name. For example:

sgm-75-59a.cisco.com;net0:linkset2




78-15589-01


– If a linkset appears in both the linksets.include file and the linksets.exclude file, it is excluded. That is, excluding a linkset overrides including the same linkset.

– If you specify a special include file on the sgm accstats or sgm linkstats command, SGM ignores the linksets.include file. See the “Including Specific Nodes in Custom Reports” section on page 3-374 for more information on the special include file.

• To exclude specific nodes or signaling points from reports, create the user-defined nodes.exclude file and list the nodes and signaling points in the file. Those nodes and signaling points will be excluded from automatically generated SGM accounting statistics and network statistics reports, as well as from custom reports that were generated with the default keyword (or no node-list keyword at all) on the sgm accstats or sgm linkstats command.


– If you installed SGM in the default directory, /opt, then the nodes.exclude file is located at /opt/CSCOsgm/reports/etc/nodes.exclude.

If you installed SGM in a different directory, or if you moved the report files directory using the sgm repdir command, then the /reports/etc/nodes.exclude file is located in that directory.

– Each line in the nodes.exclude file must contain a single node name, or node name and signaling point name, that matches exactly the real, fully qualified node name of the node, and each line must end with a colon (:). For example:



To exclude a specific signaling point, specify the node name and signaling point:





78-15589-01



– If you specify a special include file on the sgm accstats or sgm linkstats command, SGM ignores the nodes.exclude file. See the “Including Specific Nodes in Custom Reports” section on page 3-374 for more information on the special include file.

• To exclude specific linksets from reports, create the user-defined linksets.exclude file and list the linksets in the file. Those linksets will be excluded from automatically generated SGM accounting statistics and network statistics reports, as well as from custom reports that were generated with the default keyword (or no node-list keyword at all) on the sgm accstats or sgm linkstats command.


– If you installed SGM in the default directory, /opt, then the linksets.exclude file is located at /opt/CSCOsgm/reports/etc/linksets.exclude.

If you installed SGM in a different directory, or if you moved the report files directory using the sgm repdir command, then the /reports/etc/linksets.exclude file is located in that directory.

– Each line in the linksets.exclude file must contain a single linkset name that matches exactly the real, fully qualified linkset name of the linkset, including the node name and signaling point name. For example:




– If a linkset appears in both the linksets.include file and the linksets.exclude file, it is excluded. That is, excluding a linkset overrides including the same linkset.

– If you specify a special include file on the sgm accstats or sgm linkstats command, SGM ignores the linksets.exclude file. See the “Including Specific Nodes in Custom Reports” section on page 3-374 for more information on the special include file.


78-15589-01


• To use PAGER to display the contents of the system reports log, enter the sgm replog command. The reports log lists all messages related to the creation and maintenance of SGM reports.

To clear the log and restart the server, enter sgm replog clear.

To display the contents of the log in reverse order, with the most recent commands at the beginning of the log, enter sgm replog -r.

For more information about the reports log, see the “Viewing the SGM System Reports Log” section on page 3-394.

• To remove all data from SGM network statistics reports, restoring the reports to a “clean” state, enter the sgm statreps clean command.

• To remove all data from one or more SGM custom statistics reports, restoring the reports to a “clean” state, enter the sgm statreps cleancustom command.

– To clean all custom reports, enter sgm statreps cleancustom.

– To clean a single custom report, enter sgm statreps cleancustom tag, where tag is the ID tag of the custom report you want to clean.

For more information about each of these commands, including valid ranges and default settings, see the “SGM Commands and Descriptions” section on page B-2.

Each of these commands requires you to be logged in as the root user, as described in the “Becoming the Root User (Solaris Only)” section on page 3-2, or as a super user, as described in the “Specifying a Super User (Solaris Only)” section on page 4-22.

Changing the SGM Reports Directory (Solaris Only)You can change the directory in which SGM stores reports.

To change the SGM report files directory, log in as the root user, as described in the “Becoming the Root User (Solaris Only)” section on page 3-2, or as a super user, as described in the “Specifying a Super User (Solaris Only)” section on page 4-22, and enter the following commands:

# cd /opt/CSCOsgm/bin

# ./sgm repdir directory

where directory is the new directory.


78-15589-01


Note This command copies all files in the current directory to the new directory. If you are logged in as the super user, and you do not own the new directory, you might not be able to copy the files. If that is the case, you must specify a directory that you own, or you must log in as the root user.

Viewing SGM Network Statistics ReportsSGM enables you to view hourly and daily statistics summary reports for links and linksets. You can also export the reports.

SGM enables you to view the following network statistics reports for linksets:

• Viewing the Linkset Statistics Hourly Reports, page 3-344

• Viewing the Linkset Statistics Daily Summary Reports, page 3-346

SGM enables you to view the following network statistics reports for links:

• Viewing the Link Statistics Hourly Reports, page 3-349

• Viewing the Link Statistics Daily Summary Reports, page 3-354

• Viewing the Five Day Link Utilization Report, page 3-359

SGM enables you to view the following network statistics reports export files:

• Viewing the Hourly Network Statistics Export Files, page 3-361

• Viewing the Daily Network Statistics Export Files, page 3-362

• Viewing the Rolling Network Statistics Export Files, page 3-363


78-15589-01


Viewing the Linkset Statistics Hourly Reports

SGM enables you to view hourly summaries of statistics for all linksets known to SGM on the specified date and hour.

To view hourly summaries of statistics, select Linkset Hourly from the menu bar of any SGM Network Statistics or Accounting Statistics Web page. SGM displays the Linkset Statistics: Hourly Reports page, which displays hourly linkset statistics summary reports, archived by date, and by hour:

• To view an archived report showing all hourly linkset statistics summary reports for an entire day, click a date. SGM displays the Linkset Statistics: Daily All Hours Report page for that date.

• To view an archived report showing all hourly linkset statistics summary reports for a specific date and hour, click an hour. SGM displays the Linkset Statistics: Hourly Report page for that date and hour.

The Linkset Statistics: Daily All Hours Report and Linkset Statistics: Hourly Report pages both display the following information:

• Number and Sort Order (in header)—Displays the number of records in the table, the column by which the table is sorted, and whether the sort is in ascending or descending order.

• ID—Internal ID, assigned by SGM, of the selected hourly linkset statistics summary report.

To see the entire detailed report, click the ID. SGM displays the Linkset Data Record page for that linkset, date, and hour, in text format. The Linkset Data Record can be useful when the TAC is debugging problems.

• Hour—(Linkset Statistics: Daily All Hours Report page only) Hour for which the link statistics summary report was created, for the specified date.

• Node—Name of node for the linkset. To see statistics for only a selected node, click the node name.

• Inst Name—Name of instance for the linkset.

• Sig Point—Name of signaling point for the linkset. To see statistics for only a selected signaling point, click the signaling point.

• Linkset Name—Name of the linkset. To see statistics for only a selected linkset, click the linkset name.


78-15589-01


• Hourly InSrv—Percentage of time the linkset was in service on the specified date and hour.

• Long Term InSrv—Average percentage of time the linkset was in service since SGM polling began for the linkset, or since SGM last reset the averages as a result of bad data.

If a statistics calculation results in an impossible value, such as a number divided by zero, or a number that is impossible based on the configuration, SGM displays MathError in the field.

SGM enables you to modify the way information is presented in the Linkset Statistics: Daily All Hours Report and Linkset Statistics: Hourly Report pages:

• You can sort the pages based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

• To display only the top 10 or bottom 10 records, based on the column by which the table is sorted, click the Top 10 menu option:

– If the column is sorted in descending order, displays only the top 10 records.

– If the column is sorted in ascending order, displays only the bottom 10 records.

– To switch between the two displays, left-click the column header.










78-15589-01














• To display up to 15,000 records in the table, click the Max menu option.

• To reset the Top preferences for this Web page to the default settings for the SGM server, click the DefPrefs menu option.

Viewing the Linkset Statistics Daily Summary Reports

SGM enables you to view a daily summary of statistics for all linksets known to SGM on a specified date.

To view a daily summary of statistics, select Linkset Daily from the menu bar of any SGM Network Statistics or Accounting Statistics Web page. SGM displays the Linkset Statistics: Daily Summary Reports page, which displays daily linkset statistics summary reports, archived by date. Each archived file contains a daily summary of statistics for all linksets known to SGM on a specified date.


78-15589-01


To view an archived linkset statistic summary report, click a date. SGM displays the Linkset Statistics: Daily Summary Report page for that date.

The Linkset Statistics: Daily Summary Report table displays the following information:






• Daily InSrv—Average percentage of time the linkset was in service on the specified date.


• Daily Low InSrv—Lowest hourly in-service percentage for the linkset, for the specified date.

• Low Srv Hour—Hour in which the lowest in-service percentage occurred, for the specified date.



78-15589-01


SGM enables you to modify the way information is presented in the Linkset Statistics: Daily Summary Report page:

• You can sort the Linkset Statistics: Daily Summary Report page based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.


















78-15589-01












Viewing the Link Statistics Hourly Reports

SGM enables you to view hourly link statistics summary reports for an entire day, or for a specific date and hour.

To view hourly link statistics summary reports, select Link Hourly from the menu bar of any SGM Network Statistics or Accounting Statistics Web page. SGM displays the Link Statistics: Hourly Reports page, which displays hourly link statistics summary reports, archived by date, and by hour:

• To view an archived report showing all hourly link statistics summary reports for an entire day, click a date. SGM displays the Link Statistics: Daily All Hours Report page for that date.

• To view an archived report showing all hourly link statistics summary reports for a specific date and hour, click an hour. SGM displays the Link Statistics: Hourly Report page for that date and hour.


78-15589-01


The Link Statistics: Daily All Hours Report and Link Statistics: Hourly Report pages both display the following information:


• ID—Internal ID, assigned by SGM, of the selected hourly link statistics summary report.

To see the entire detailed report, click the ID. SGM displays the Link Data Record page for that link, date, and hour, in text format. The Link Data Record can be useful when the TAC is debugging problems.

• Hour—(Link Statistics: Daily All Hours Report page only) Hour for which the link statistics summary report was created, for the specified date.

• Node—Name of node for the link. To see statistics for only a selected node, click the node name.

• Inst Name—Name of instance for the link.

• Sig Point—Name of signaling point for the link. To see statistics for only a selected signaling point, click the signaling point.

• Link Name—Name of the link. To see statistics for only a selected link, click the link name.



– SCTP—The link uses the Stream Control Transmission Protocol (SCTP) IP transport protocol.



• Send Util or Send Erls—Average Send Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), for the specified date and hour.

If the planned send capacity is not set for the link, this field displays NoCap.


78-15589-01


• L Term Send Util or L Term Send Erls—Long-term average Send Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), since SGM polling began for the link, or since SGM last reset the averages as a result of bad data.


• Recv Util or Recv Erls—Average Receive Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), for the specified date and hour.

If the planned receive capacity is not set for the link, this field displays NoCap.

• L Term Recv Util or L Term Recv Erls—Long-term average Receive Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), since SGM polling began for the link, or since SGM last reset the averages as a result of bad data.


• Send MSUs—Total number of MTP3 MSUs sent on the specified date and hour.

• Recv MSUs—Total number of MTP3 MSUs received on the specified date and hour.

• Drop—Total number of drops on the specified date and hour.

• Hourly InSrv—Percentage of time the link was in service on the specified date and hour.

• Long Term InSrv—Average percentage of time the link was in service since SGM polling began for the link, or since SGM last reset the averages as a result of bad data.



78-15589-01


SGM enables you to modify the way information is presented in the Link Statistics: Daily All Hours Report and Link Statistics: Hourly Report pages:



















78-15589-01











• To display only records for links that are not of type SCTP, click the NoSCTP menu option.

To display all records, including those for links that are of type SCTP, click the YesSCTP menu option. This is the default setting.

• To display all records, including those for links that do not have planned send and receive capacities, click the YesNullCaps menu option.

To display only records for links that have planned send and receive capacities, click the NoNullCaps menu option. This is the default setting.

• To reset the Top, SCTP, and NullCaps preferences for this Web page to the default settings for the SGM server, click the DefPrefs menu option.


78-15589-01


Viewing the Link Statistics Daily Summary Reports

SGM enables you to view a daily summary of statistics for all links known to SGM on a specified date.

To view a daily summary of statistics, use one of the following procedures:

• Select View> Reports > Network Statistics from the SGM Main Menu.

• Select Network Statistics Reports from the SGM Server Home Page.

• Select Link Daily from the menu bar of any SGM Network Statistics or Accounting Statistics Web page.

SGM displays the Link Statistics: Daily Summary Reports page, which displays daily link statistics summary reports are archived by date. Each archived file contains a daily summary of statistics for all links known to SGM on a specified date.

To view an archived link statistic summary report, click a date. SGM displays the Link Statistics: Daily Summary Report page for that date (Figure 3-89).

Figure 3-89 Link Statistics: Daily Summary Report Page


78-15589-01


The Link Statistics: Daily Summary Report page displays the following information:











• Avg Send Util or Avg Send Erls—Average Send Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), for the specified date.


• Peak Send Util or Peak Send Erls—Highest hourly Average Send Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), for the specified date.

• Peak Send Hour—Hour in which the Peak Send Utilization for the link occurred, for the specified date.


78-15589-01




• Avg Recv Util or Avg Recv Erls—Average Receive Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), for the specified date.


• Peak Recv Util or Peak Recv Erls—Highest hourly Average Receive Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), for the specified date.

• Peak Recv Hour—Hour in which the Peak Receive Utilization for the link occurred, for the specified date.



• Send MSUs—Total number of MTP3 MSUs sent on the specified date.

• Recv MSUs—Total number of MTP3 MSUs received on the specified date.

• Drop—Total number of drops on the specified date.

• Daily InSrv—Average percentage of time the link was in service on the specified date.


• Daily Low InSrv—Lowest hourly in-service percentage for the link, for the specified date.

• Low Srv Hour—Hour in which the lowest in-service percentage occurred, for the specified date.


78-15589-01



SGM enables you to modify the way information is presented in the Link Statistics: Daily Summary Report page:

• You can sort the Link Statistics: Daily Summary Report page based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.














78-15589-01





















78-15589-01


Viewing the Five Day Link Utilization Report

The Five Day Link Utilization Report page displays send and receive utilization percentages for all links for the last five (5) days.

To access the Five Day Link Utilization Report page, select Five Day Link Util from the menu bar of any SGM Network Statistics or Accounting Statistics Web page. SGM displays the five day utilization report for the specified link.

The Five Day Link Utilization Report page displays the following information:


The default sort order is day one, Send Utilization for the link, descending.





• Send Util or Send Erls—Send Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), for each of the last five days. If the planned send capacity is not set for the link, this field displays NoCap.

• Recv Util or Recv Erls—Receive Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), for each of the last five days. If the planned receive capacity is not set for the link, this field displays NoCap.



78-15589-01


SGM enables you to modify the way information is presented in the Five Day Link Utilization Report page:

• You can sort the Five Day Link Utilization Report page based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.


















78-15589-01
















Viewing the Hourly Network Statistics Export Files

The Hourly Network Statistics Export Files page displays all archived SGM hourly network statistics summary reports, for all links and linksets known to SGM, for the server to which you are connected, stored as downloadable Zip files.

To access the Hourly Network Statistics Export Files page, select Hourly Export from the menu bar of any SGM Network Statistics or Accounting Statistics Web page.


78-15589-01


On the Hourly Network Statistics Export Files page, the Zip files are archived by type (linkset or link), date, and hour. For example, sgmLinksetStats.2002-10-15-08.csv.zip is the Zip file that contains the hourly linkset statistics summary report for the 8th hour on October 15, 2002.

Each archived Zip file contains a comma-separated value (CSV) text file with an hourly network statistics summary report for all links or linksets that were known to SGM on that date and hour. You can download the Zip files and unzip them.

To download a Zip file, click a filename, then save the file to a location of your choice.

See the “SGM Link Statistics Hourly Export File Format” section on page F-4 for detailed information about the format of hourly link statistics export files.

See the “SGM Linkset Statistics Hourly Export File Format” section on page F-6 for detailed information about the format of hourly link and linkset statistics export files.

Viewing the Daily Network Statistics Export Files

The Daily Network Statistics Export Files page displays all archived SGM daily network statistics summary reports, for all links and linksets known to SGM, for the server to which you are connected, stored as downloadable Zip files.

To access the Daily Network Statistics Export Files page, select Daily Export from the menu bar of any SGM Network Statistics or Accounting Statistics Web page.

On the Daily Network Statistics Export Files page, the Zip files are archived by type (linkset or link) and date. For example, sgmLinksetStats.DailySum.2002-10-15.csv.zip is the Zip file that contains the daily linkset statistics summary report for October 15, 2002.

Each archived Zip file contains a comma-separated value (CSV) text file with a daily network statistics summary report for all links or linksets that were known to SGM on that date and hour. You can download the Zip files and unzip them.


See the “SGM Link Statistics Daily Export File Format” section on page F-3 for detailed information about the format of daily link statistics export files.


78-15589-01


See the “SGM Linkset Statistics Daily Export File Format” section on page F-5 for detailed information about the format of daily link and linkset statistics export files.

Viewing the Rolling Network Statistics Export Files

The Rolling Network Statistics Export Files page displays concatenated SGM hourly and daily network statistics summary reports, for all links and linksets known to SGM, for the server to which you are connected, stored as downloadable Zip files.

To access the Rolling Network Statistics Export Files page, select Rolling Export from the menu bar of any SGM Network Statistics or Accounting Statistics Web page.

On the Rolling Network Statistics Export Files page, the Zip files are archived by type (linkset or link) and number of days (7 or 30). For example:

• sgmLinksetStats.RollingSevenDayAllHours.csv.zip is the Zip file that contains the hourly linkset statistics summary reports for the last seven (7) days, concatenated into one comma-separated value (CSV) text file.

• sgmLinksetStats.Rolling30DayAllDays.csv.zip is the Zip file that contains the daily linkset statistics summary reports for the last 30 days, concatenated into one comma-separated value (CSV) text file.

• sgmLinkStats.RollingSevenDayAllHours.csv.zip is the Zip file that contains the hourly link statistics summary reports for the last seven (7) days, concatenated into one comma-separated value (CSV) text file.

• sgmLinkStats.Rolling30DayAllDays.csv.zip is the Zip file that contains the daily link statistics summary reports for the last 30 days, concatenated into one comma-separated value (CSV) text file.

SGM creates a new set of files every hour.

You can download the Zip files and unzip them.


See the “SGM Rolling Network Statistics Export File Formats” section on page F-7 for detailed information about the format of rolling statistics export files.


78-15589-01


Viewing SGM Accounting Statistics ReportsSGM enables you to view accounting statistics reports. You can also export the reports.

SGM enables you to view the following accounting statistics reports:

• Viewing the Accounting Statistics Daily Detail Reports, page 3-364

• Viewing the Daily Accounting Statistics Export Files, page 3-368

Viewing the Accounting Statistics Daily Detail Reports

SGM enables you to view a daily summary of accounting statistics for SGM on a specified date. Accounting statistics are displayed based on the node, signaling point, linkset, originating point code (OPC), the destination point code (DPC), the type of SS7 traffic (such as ISUP or SCCP), and whether the traffic passed or failed the Gateway Screening test at the ITP.

To view a daily summary of accounting statistics, use one of the following procedures:

• Select View> Reports > Accounting Statistics from the SGM Main Menu.

• Select Accounting Statistics Reports from the SGM Server Home Page.

• Select Accounting Daily from the menu bar of any SGM Network Statistics or Accounting Statistics Web page.

SGM displays the Accounting Statistics: Daily Detail Reports page, which displays daily accounting statistics reports, archived by date. Each archived file contains a daily summary of accounting statistics for SGM on a specified date.

To view an archived accounting statistic report, click a date. SGM displays the Accounting Statistics: Daily Detail Report page for that date (Figure 3-90).


78-15589-01


Figure 3-90 Accounting Statistics: Daily Detail Report Page

The Accounting Statistics: Daily Detail Report page displays the following information:


• ID—Internal ID, assigned by SGM, of the selected hourly accounting statistics report.

To see the entire detailed report, click the ID. SGM displays the Accounting Data Record # X for Date for that date and hour. The Accounting Data Record # X for Date can be useful when the TAC is debugging problems.





78-15589-01


• Linkset—Name of the linkset. To see statistics for only a selected linkset, click the linkset name.

• Gateway Screening—Indicates whether the traffic passed or failed the Gateway Screening test at the ITP. To see only statistics that passed or failed for a specific linkset, select a linkset and click Pass or Fail.

• OPC—Originating point code of the traffic, which is a unique identifier for each set of statistics. To see only statistics that match a specific OPC for a given linkset, find the linkset and click the point code.

• DPC—Destination point code of the traffic. To see only statistics that match a specific DPC for a given linkset, find the linkset and click the point code.

• SI—Service indicator, which indicates the type of SS7 traffic, such as ISUP or SCCP. To see only detailed information for a specific type of SI, click the SI type.



• Send Bytes—Total number of bytes sent on the specified date.

• Recv Bytes—Total number of bytes received on the specified date.


SGM enables you to modify the way information is presented in the Accounting Statistics: Daily Detail Report page:

• You can sort the Accounting Statistics: Daily Detail Report page based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.






78-15589-01



















78-15589-01








Viewing the Daily Accounting Statistics Export Files

The Daily Accounting Statistics Export Files page displays all archived SGM daily accounting statistics reports for the server to which you are connected, stored as downloadable Zip files.

To access the Daily Accounting Statistics Export Files page, select Accounting Export from the menu bar of any SGM Network Statistics or Accounting Statistics Web page.

On the Daily Accounting Statistics Export Files page, the Zip files are archived by date. For example, sgmAccStats.DailyDetail.2002-10-15.csv.zip is the Zip file that contains the daily accounting statistics report for October 15, 2002.

Each archived Zip file contains a comma-separated value (CSV) text file with a daily accounting statistics report for that date. You can download the Zip files and unzip them.


See the “SGM Daily and Hourly Accounting Statistics Export File Format” section on page F-2 for detailed information about the format of accounting statistics export files.


78-15589-01


Generating and Viewing Custom SGM Statistics ReportsSGM enables you to create custom link and linkset statistics summary reports, and custom accounting reports. You can also export the reports.

This section contains the following information:

• Generating a Custom Network Statistics Report, page 3-369

• Generating a Custom Accounting Statistics Report, page 3-372

• Including Specific Nodes in Custom Reports, page 3-374

• Including Specific Linksets in Custom Reports, page 3-376

• Excluding Specific Nodes from Custom Reports, page 3-377

• Excluding Specific Linksets from Custom Reports, page 3-378

• Viewing the Custom Network Statistics Export Files, page 3-379

• Viewing a Custom Accounting Statistics Report, page 3-380

• Viewing a Custom Link Statistics Summary Report, page 3-383

• Viewing a Custom Linkset Statistics Summary Report, page 3-387

Generating a Custom Network Statistics Report

To create a custom link and linkset statistics summary report for SGM, use the following procedure:

Step 1 Log in as the root user, as described in the “Becoming the Root User (Solaris Only)” section on page 3-2, or as a super user, as described in the “Specifying a Super User (Solaris Only)” section on page 4-22.

Step 2 Enter the following commands:


# ./sgm linkstats [node-list [id-tag]] [sort-option] [quiet]


78-15589-01


• (Optional) To include or exclude specific nodes or linksets in the report, use the node-list argument. See the following sections for more information:

– Including Specific Nodes in Custom Reports, page 3-374

– Including Specific Linksets in Custom Reports, page 3-376

– Excluding Specific Nodes from Custom Reports, page 3-377

– Excluding Specific Linksets from Custom Reports, page 3-378

• (Optional) If you specify a node-list, you can also specify an id-tag to identify the report. The id-tag can be any meaningful character string, but it cannot contain any spaces. The default value for id-tag is the process ID of the sgm linkstats command.

• (Optional) To specify a sort order for the report, specify one of the following keywords for the sort-option argument:

– -sis—Sort based on average in-service percentage for each link (Daily InSrv), in descending order.

– -sls—Sort based on the linkset name, in ascending order.

– -sos—Sort based on the average out-of-service percentage for each link, in descending order.

– -sru—Sort based on the average Receive Utilization for each link (Avg Receive Util or Avg Receive Erls), in descending order.

– -ssu—Sort based on the average Send Utilization for each link (Avg Send Util or Avg Send Erls), in descending order. This is the default setting.

• (Optional) To disable automatic output to the terminal when running this command in a script, specify the quiet keyword. SGM generates the report in export format, which you can view using the SGM Web interface.

For example, to generate a custom link and linkset statistics summary report, that includes only links and linksets associated with node sgm-2600a.cisco.com, sorted in ascending order based on the linkset name, and identified by ID tag test1, enter the following command:

# ./sgm linkstats sgm-2600a.cisco.com test1 -sls


78-15589-01


Step 3 (Optional) If this is the first time you are using the sgm linkstats command to generate a report, you must enter the command two more times:

• The first entry gets the first set of raw data.

• The second entry calculates begins calculating useful link and linkset statistics.

• The third entry continues to calculate statistics, calculates long-term averages, and, if the data being collected appears valid, begins generating the report.

Thereafter, you need only enter this command once to generate the report.

Step 4 SGM generates the custom link and linkset statistics summary report and stores it in the /custom directory, identified by its ID tag.

For example, if you entered the command:

# ./sgm linkstats sgm-2600a.cisco.com test1 -sls

SGM generates the following reports:

sgmLinkStats.custom.test1.2002-10-27.csv.zip

sgmLinksetStats.custom.test1.2002-10-27.csv.zip

If you installed SGM in the default directory, /opt, then the /custom directory is located at /opt/CSCOsgm/reports/custom.

If you installed SGM in a different directory, or if you moved the report files directory using the sgm repdir command, then the /custom directory is located in that directory.

Step 5 For information on viewing the report, see the “Viewing the Custom Network Statistics Export Files” section on page 3-379.


78-15589-01


Generating a Custom Accounting Statistics Report

To create a custom accounting statistics report for SGM, use the following procedure:




# ./sgm accstats [node-list [id-tag]] [sort-option] [quiet]

• (Optional) To include or exclude specific nodes or linksets in the report, use the node-list argument. See the following sections for more information:

– Including Specific Nodes in Custom Reports, page 3-374

– Including Specific Linksets in Custom Reports, page 3-376

– Excluding Specific Nodes from Custom Reports, page 3-377

– Excluding Specific Linksets from Custom Reports, page 3-378

• (Optional) If you specify a node-list, you can also specify an id-tag to identify the report. The id-tag can be any meaningful character string, but it cannot contain any spaces. The default value for id-tag is the process ID of the sgm accstats command.

• (Optional) To specify a sort order for the report, specify one of the following keywords for the sort-option argument:

– -sdp—Sort based on the destination point code (DPC) of the node, in descending order.

– -sno—Sort based on the node name, in ascending order.

– -sop—Sort based on the originating point code (OPC) of the node, in descending order.

– -srb—Sort based on number of bytes received, in descending order.

– -srm—Sort based on number of MTP3 MSUs received, in descending order.

– -ssb—Sort based on number of bytes sent, in descending order.


78-15589-01


– -ssi—Sort numerically based on service indicator (SI), in ascending order.

– -ssm—Sort based on number of MTP3 MSUs sent, in descending order.

• (Optional) To disable automatic output to the terminal when running this command in a script, specify the quiet keyword. SGM generates the report in export format, which you can view using the SGM Web interface.

For example, to generate a custom accounting statistics report, that includes only information for node sgm-2600a.cisco.com, sorted in ascending order based on the node name, and identified by ID tag test1, enter the following command:

# ./sgm accstats sgm-2600a.cisco.com test1 -sno

Step 3 (Optional) If this is the first time you are using the sgm accstats command to generate a report, you must enter the command two more times:


• The second entry calculates begins calculating useful accounting statistics.



Step 4 SGM generates the custom accounting statistics report and stores it in the /custom directory, identified by its ID tag.

For example, if you entered the command:

# ./sgm accstats sgm-2600a.cisco.com test1 -sno

SGM generates the following reports:

sgmAccStats.custom.test1.2002-10-27.csv.zip

sgmAccStats.custom.test1.2002-10-27.csv.zip


78-15589-01


If you installed SGM in the default directory, /opt, then the /custom directory is located at /opt/CSCOsgm/reports/custom.

If you installed SGM in a different directory, or if you moved the report files directory using the sgm repdir command, then the /custom directory is located in that directory.

Step 5 For information on viewing the report, see the “Viewing the Custom Network Statistics Export Files” section on page 3-379.

Including Specific Nodes in Custom Reports

When you generate a custom accounting statistics or network statistics report, SGM enables you to limit the report to one or more specific nodes.

• To generate a report that includes all nodes known to SGM, specify all in place of the node-list argument in the sgm accstats or sgm linkstats command. For example, the following command generates an accounting statistics report for all nodes:

./sgm accstats all

• To generate a report for a single node, specify the node name in place of the node-list argument in the sgm accstats or sgm linkstats command. The node name must match exactly the node name as discovered by SGM, including the domain name. For example, the following command generates an accounting statistics report for node sgm-2600a.cisco.com:

./sgm accstats sgm-2600a.cisco.com

• To generate a report that includes only the nodes and signaling points listed in the user-defined nodes.include file, create the file, then specify default in place of the node-list argument in the sgm accstats or sgm linkstats command. This is also the default setting for this command, if you do not specify a node-list keyword.

For example, the following command generates an accounting statistics report that includes only the nodes and signaling points specified in the nodes.include file:

./sgm accstats default


78-15589-01



– If you installed SGM in the default directory, /opt, then the nodes.include file is located at /opt/CSCOsgm/reports/etc/nodes.include.

If you installed SGM in a different directory, or if you moved the report files directory using the sgm repdir command, then the /reports/etc/nodes.include file is located in that directory.

– Each line in the nodes.include file must contain a single node name, or node name and signaling point name, that matches exactly the real, fully qualified node name of the node, and each line must end with a colon (:). For example:








– If you specify a special include file on the sgm accstats or sgm linkstats command, SGM ignores the nodes.include file.

• To generate a report that includes only a group of nodes or signaling points other than the nodes and signaling points listed in the nodes.include file, create a file that contains the list of nodes and signaling points to be included and specify the full path and name of the file in place of the node-list argument in the sgm accstats or sgm linkstats command.

For example, the following command generates an accounting statistics report that includes only the nodes and signaling points specified in the /opt/CSCOsgm/reports/etc/specialnodes.include file:

./sgm accstats /opt/CSCOsgm/reports/etc/specialnodes.include


78-15589-01



– Each line in the special include file must contain a single node name, or node name and signaling point name, that matches exactly the real, fully qualified node name of the node, and each line must end with a colon (:). For example:







– If you specify a special include file on the sgm accstats or sgm linkstats command, SGM ignores the nodes.include, linksets.include, nodes.exclude, and linksets.exclude files, if they exist.

Including Specific Linksets in Custom Reports

When you generate a custom accounting statistics or network statistics report, SGM enables you to limit the report to one or more specific linksets.

To generate a report that includes only the linksets listed in the user-defined linksets.include file, create the file, then specify default in place of the node-list argument in the sgm accstats or sgm linkstats command.

For example, the following command generates an accounting statistics report that includes only the linksets specified in the linksets.include file:



78-15589-01



• If you installed SGM in the default directory, /opt, then the linksets.include file is located at /opt/CSCOsgm/reports/etc/linksets.include.

If you installed SGM in a different directory, or if you moved the report files directory using the sgm repdir command, then the /reports/etc/linksets.include file is located in that directory.

• Each line in the linksets.include file must contain a single linkset name that matches exactly the real, fully qualified linkset name of the linkset, including the node name and signaling point name. For example:



• Wildcard matching is not supported.

• If a linkset appears in both the linksets.include file and the linksets.exclude file, it is excluded. That is, excluding a linkset overrides including the same linkset.

• If you specify a special include file on the sgm accstats or sgm linkstats command, SGM ignores the linksets.include file.

Excluding Specific Nodes from Custom Reports

When you generate a custom accounting statistics or network statistics report, SGM enables you to exclude one or more specific nodes or signaling points from the report.

To generate a report that excludes the nodes and signaling points listed in the user-defined nodes.exclude file, create the file, then specify default in place of the node-list argument in the sgm accstats or sgm linkstats command.

For example, the following command generates an accounting statistics report that excludes the nodes and signaling points specified in the nodes.exclude file:



78-15589-01



• If you installed SGM in the default directory, /opt, then thenodes.exclude file is located at /opt/CSCOsgm/reports/etc/nodes.exclude.

If you installed SGM in a different directory, or if you moved the report files directory using the sgm repdir command, then the/reports/etc/nodes.exclude file is located in that directory.

• Each line in the nodes.exclude file must contain a single node name, or node name and signaling point name, that matches exactly the real, fully qualified node name of the node, and each line must end with a colon (:). For example:



To exclude a specific signaling point, specify the node name and signaling point:




• If a node or signaling point appears in both the nodes.include file and the nodes.exclude file, it is excluded. That is, excluding a node or signaling point overrides including the same node or signaling point.

• If you specify a special include file on the sgm accstats or sgm linkstats command, SGM ignores the nodes.exclude file.

Excluding Specific Linksets from Custom Reports

When you generate a custom accounting statistics or network statistics report, SGM enables you to exclude one or more specific linksets from the report.

To generate a report that excludes the linksets listed in the user-defined linksets.exclude file, create the file, then specify default in place of the node-list argument in the sgm accstats or sgm linkstats command.


78-15589-01


For example, the following command generates an accounting statistics report that excludes the linksets specified in the linksets.exclude file:



• If you installed SGM in the default directory, /opt, then the linksets.exclude file is located at /opt/CSCOsgm/reports/etc/linksets.exclude.

If you installed SGM in a different directory, or if you moved the report files directory using the sgm repdir command, then the /reports/etc/linksets.exclude file is located in that directory.

• Each line in the linksets.exclude file must contain a single linkset name that matches exactly the real, fully qualified linkset name of the linkset, including the node name and signaling point name. For example:




• If a linkset appears in both the linksets.include file and the linksets.exclude file, it is excluded. That is, excluding a linkset overrides including the same linkset.

• If you specify a special include file on the sgm accstats or sgm linkstats command, SGM ignores the linksets.exclude file.

Viewing the Custom Network Statistics Export Files

The Custom Network Statistics Export Files page displays all archived SGM custom network and accounting statistics reports for the server to which you are connected, stored as downloadable Zip files. Custom statistics reports are those that are generated using the sgm accstats and sgm linkstats commands.

To access the Custom Network Statistics Export Files page, select Custom Export from the menu bar of any SGM Network Statistics or Accounting Statistics Web page.


78-15589-01


The Custom Network Statistics Export Files page displays the following information:

• Export File—Name of the custom statistics export ZIP file, archived by type (linkset or link), date, and hour. For example, sgmLinksetStats.custom.20867.2002-10-15-16.csv.zip is the Zip file that contains the custom linkset statistics summary report with ID tag 20867 for the 16th hour on October 15, 2002.

Each archived Zip file contains a comma-separated value (CSV) text file with a daily statistics report for that date. You can download the Zip files and unzip them.


See the “SGM Custom Network Statistics Export File Formats” section on page F-2 for detailed information about the format of custom statistics export files.

• ID Tag—Identifier for the custom report, specified when you entered the sgm accstats or sgm linkstats command. If you did not specify an ID tag, this field displays the process ID of the command that generated the report.

• Start—Date and time the custom report began.

• Finish—Date and time the custom report ended.

• View—Enables you to view the custom report in HTML or ASCII.

For more information about viewing custom reports, see the following sections:

– Viewing a Custom Accounting Statistics Report, page 3-380

– Viewing a Custom Link Statistics Summary Report, page 3-383

– Viewing a Custom Linkset Statistics Summary Report, page 3-387

Viewing a Custom Accounting Statistics Report

The Accounting Statistics: Custom Detail Report page displays a custom summary of accounting statistics for SGM. Accounting statistics are displayed based on the node, signaling point, linkset, originating point code (OPC), the destination point code (DPC), the type of SS7 traffic (such as ISUP or SCCP), and whether the traffic passed or failed the Gateway Screening test at the ITP.


78-15589-01


To access the Accounting Statistics: Custom Detail Report page, click HTML in the View column beside a custom accounting statistics report on the Custom Network Statistics Export Files page. SGM displays the custom accounting statistics report.

The Accounting Statistics: Custom Detail Report page displays the following information:


• ID—Internal ID, assigned by SGM, of the selected hourly accounting statistics report.

To see the entire detailed report, click the ID. SGM displays the Accounting Data Record # X for Date for that date and hour, in text format. The Accounting Data Record # X for Date can be useful when the TAC is debugging problems.




• Linkset—Name of the linkset. To see statistics for only a selected linkset, click the linkset name.

• Gateway Screening—Indicates whether the traffic passed or failed the Gateway Screening test at the ITP. To see only statistics that passed or failed for a specific linkset, select a linkset and click Pass or Fail.

• OPC—Originating point code of the traffic, which is a unique identifier for each set of statistics. To see only statistics that match a specific OPC for a given linkset, find the linkset and click the point code.

• DPC—Destination point code of the traffic. To see only statistics that match a specific DPC for a given linkset, find the linkset and click the point code.

• SI—Service indicator, which indicates the type of SS7 traffic, such as ISUP or SCCP. To see only detailed information for a specific type of SI, click the SI type.



78-15589-01



• Send Bytes—Total number of bytes sent on the specified date.

• Recv Bytes—Total number of bytes received on the specified date.


SGM enables you to modify the way information is presented in the Accounting Statistics: Custom Detail Report page:

• You can sort the Accounting Statistics: Custom Detail Report page based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.














78-15589-01
















Viewing a Custom Link Statistics Summary Report

SGM enables you to view custom link statistics summary reports.

To view a custom link statistics summary report, click HTML in the View column beside a custom link statistics summary report on the Custom Network Statistics Export Files page. SGM displays the custom link statistics summary report, which is a custom summary of statistics for all links known to SGM when the report was generated.


78-15589-01


The Link Statistics: Custom Detail Report page displays the following information:


• ID—Internal ID, assigned by SGM, of the selected hourly link statistics summary report.

To see the entire detailed report, click the ID. SGM displays the Link Data Record page for that link, date, and hour, in text format. The Link Data Record can be useful when the TAC is debugging problems.

• Hour—Hour for which the link statistics summary report was created, for the specified date.










• Send Util or Send Erls—Average Send Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), for the specified date and hour.



78-15589-01




• Recv Util or Recv Erls—Average Receive Utilization for the link, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), for the specified date and hour.




• Send MSUs—Total number of MTP3 MSUs sent on the specified date and hour.

• Recv MSUs—Total number of MTP3 MSUs received on the specified date and hour.

• Drop—Total number of drops on the specified date and hour.

• Hourly InSrv—Percentage of time the link was in service on the specified date and hour.




78-15589-01


SGM enables you to modify the way information is presented in the Link Statistics: Custom Detail Report page:



















78-15589-01
















Viewing a Custom Linkset Statistics Summary Report

SGM enables you to view custom linkset statistics summary reports.

To view a custom linkset statistics summary report, click HTML in the View column beside a custom linkset statistics summary report on the Custom Network Statistics Export Files page. SGM displays the custom linkset statistics summary report, which is a custom summary of statistics for all linksets known to SGM when the report was generated.


78-15589-01


The Linkset Statistics: Custom Detail Report page displays the following information:


• ID—Internal ID, assigned by SGM, of the selected hourly linkset statistics summary report.

To see the entire detailed report, click the ID. SGM displays the Linkset Data Record page for that linkset, date, and hour, in text format. The Linkset Data Record can be useful when the TAC is debugging problems.

• Hour—Hour for which the link statistics summary report was created, for the specified date.





• Hourly InSrv—Percentage of time the linkset was in service on the specified date and hour.




78-15589-01


SGM enables you to modify the way information is presented in the Linkset Statistics: Custom Detail Report page:



















78-15589-01












Viewing SGM Point Code Inventory ReportsSGM enables you to view current and daily point code inventory reports. You can also export the reports.

SGM enables you to view the following point code inventory reports:

• Viewing the Current Point Code Inventory, page 3-391

• Viewing the Daily Point Code Inventory Daily Reports, page 3-392

• Viewing the Daily Point Code Inventory Export Files, page 3-394


78-15589-01


Viewing the Current Point Code Inventory

The Current Point Code Inventory page displays all point codes that are currently being used by all nodes that are known to SGM.

To access the Current Point Code Inventory page, use one of the following procedures:

• Select View> Reports > Point Code Inventory from the SGM Main Menu.

• Select Point Code Inventory Reports from the SGM Server Home Page.

• Select Current Point Codes from the menu bar of any SGM Point Code Inventory Web page.

SGM displays the Current Point Code Inventory page (Figure 3-91).

Figure 3-91 Current Point Code Inventory Page


78-15589-01


The Current Point Code Inventory page displays the following information:

• Number and Sort Order (in header)—Displays the number of point codes in the table, the column by which the table is sorted, and whether the sort is in ascending or descending order.

• Signaling Point—Signaling point that is currently being used by a node.

To sort the point codes by signaling point in descending order, click the Signaling Points header.

Click again to sort the point codes in ascending order.

• Point Code—Point code that is currently being used by a node.

To sort the point codes by point code in ascending order, click the Point Codes header. This is the default display.

Click again to sort the point codes in descending order.

• Node Name—Name or IP address of the node.

To see detailed information for the node, click the node name.

To sort the point codes by node in descending order, click the Node Name header.


• Point Code Type—Type of point code:

– Primary—Main point code used by a node.

– Secondary—Alternate or backup point code used by a node.

– Capability—Shared by more than one node, each of which is also assigned a “real” point code. Also called an alias point code.

To sort the point codes by type in ascending order, click the Point Code Type header.


Viewing the Daily Point Code Inventory Daily Reports

The Point Code Inventory: Daily Reports page displays all archived SGM daily point code inventory reports for the server to which you are connected.

To access the Point Code Inventory: Daily Reports page, select Daily Point Codes from the menu bar of any SGM Point Code Inventory Web page.


78-15589-01


On the Point Code Inventory: Daily Reports page, point code inventory reports are archived by date. Each archived file contains a list of all point codes that were being used by all nodes that were known to SGM on that date.

To view an archived point code inventory report, click a date. SGM displays the Point Code Inventory: Date page, which displays the archived list of point codes for that date, including the following information:

• Number and Sort Order (in header)—Displays the number of point codes in the table, the column by which the table is sorted, and whether the sort is in ascending or descending order.

• Signaling Point Name—Name of the signaling point.

To sort the point codes by signaling point in descending order, click the Signaling Point Name header.


• Point Code—Point code that was being used by a node on the specified date.

To sort the point codes by point code in ascending order, click the Point Codes header. This is the default display.


• Node Name—Name or IP address of the node.

To see detailed information for the node, click the node name.

To sort the point codes by node in descending order, click the Node Name header.


• Point Code Type—Type of point code:

– Primary—Main point code used by a node.

– Secondary—Alternate or backup point code used by a node.

– Capability—Shared by more than one node, each of which is also assigned a “real” point code. Also called an alias point code.

To sort the point codes by type in ascending order, click the Point Code Type header.



78-15589-01


Viewing the Daily Point Code Inventory Export Files

The Daily Point Code Inventory Export Files page displays all archived SGM daily point code inventory reports for the server to which you are connected, stored as downloadable Zip files.

To access the Daily Point Code Inventory Export Files page, select Daily Point Code Export from the menu bar of any SGM Point Code Inventory Web page.

On the Daily Point Code Inventory Export Files page, the Zip files are archived by date. For example, sgmPointCodes.DailyInv.2002-10-15.csv.zip is the Zip file that contains the daily point code inventory report for October 15, 2002.

Each archived Zip file contains a comma-separated value (CSV) text file with a list of all point codes that were being used by all nodes that were known to SGM on that date. You can download the Zip files and unzip them.


See the “SGM Point Code Inventory Export File Format” section on page F-7 for detailed information about the format of point code inventory export files.

Viewing SGM Statistics Reports LogsSGM enables you to view a log that contains all messages pertaining to SGM reports, and a display of the current values of SGM report parameters and timers.

This section contains the following information:

• Viewing the SGM System Reports Log, page 3-394

• Viewing the SGM System Report Parameters and Timers, page 3-395

Viewing the SGM System Reports Log

The SGM System Reports Log: Last X Messages page displays the message log for SGM reports for the server to which you are connected, and which is currently running the SGM server.


78-15589-01


To access the SGM System Reports Log: Last X Messages page, use one of the following procedures:

• Select System Report Log from the SGM Server Home Page.

• Select Log from the menu bar of any SGM Network Statistics or Accounting Statistics Web page.

• Enter the sgm replog command. See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of this command.

The SGM System Reports Log: Last X Messages page displays the following information:

• Last Update (in header)—Date and time the information on the page was last updated by SGM.

• Row—Message number, assigned to the message by SGM.

• Time—Date and time the message was logged.

• Type—Type of message. Possible types are:

– Error

– Info


Viewing the SGM System Report Parameters and Timers

The SGM System Report Parameters and Timers page displays the current values of report parameters and timers for the server to which you are connected, and which is currently running the SGM server.

To access the SGM System Report Parameters and Timers page, select System Report Parameters from the SGM Server Home Page, or select Params from the menu bar of any SGM Network Statistics or Accounting Statistics Web page.


78-15589-01


The SGM System Report Parameters and Timers page displays the following information:

• Server Name (in header)—Name of the SGM server for which report parameter and timer settings are being displayed.

• Report Dir—Path and name of the directory in which SGM stores reports. The default reports directory is /opt/CSCOsgm/reports, but you can change the reports directory using the sgm repdir command. For more information, see the description of the sgm repdir command in the “SGM Commands and Descriptions” section on page B-2.

• Status—Indicates whether SGM is to generate network statistics reports. For more information, see the description of the sgm statreps [disable | enable] command in the “SGM Commands and Descriptions” section on page B-2.

• ExportReports—Indicates whether SGM is to generate network statistics reports in export format. For more information, see the description of the sgm statreps [export | noexport] command in the “SGM Commands and Descriptions” section on page B-2.

• AcctReports—Indicates whether SGM is to generate accounting statistics reports. For more information, see the description of the sgm statreps [acct | noacct] command in the “SGM Commands and Descriptions” section on page B-2.

• IPLinks—Indicates whether SGM is to include links that use the Stream Control Transmission Protocol (SCTP) IP transport protocol in network statistics reports. For more information, see the description of the sgm statreps [iplinks | noiplinks] command in the “SGM Commands and Descriptions” section on page B-2.

• NullCaps—Indicates whether SGM is to include links that do not have planned send and receive capacities in network statistics reports. For more information, see the description of the sgm statreps [nullcaps | nonullcaps] command in the “SGM Commands and Descriptions” section on page B-2.

• TimeMode—Indicates the time mode for dates in network statistics reports. For more information, see the description of the sgm statreps timemode [12 | 24] command in the “SGM Commands and Descriptions” section on page B-2.


78-15589-01


• DiskCheck—Indicates whether SGM is to verify that a disk has at least 10 MB of space remaining before generating network statistics reports. For more information, see the description of the sgm statreps [diskcheck | nodiskcheck] command in the “SGM Commands and Descriptions” section on page B-2.

• UtilRatio—Indicates whether SGM is to display a gray background in the Send Utilization or Receive Utilization cell in a network statistics report, if the following condition is met:


For more information, see the description of the sgm statreps utilratio command in the “SGM Commands and Descriptions” section on page B-2.

• ServRatio—Indicates whether SGM is to display a gray background in the InSrv cell in a network statistics report, if the following condition is met:


For more information, see the description of the sgm statreps [disable | enable] command in the “SGM Commands and Descriptions” section on page B-2.

• HourlyAge—Indicates the maximum number of days SGM is to archive hourly network statistics reports. For more information, see the description of the sgm statreps hourlyage and sgm rephourlyage commands in the “SGM Commands and Descriptions” section on page B-2.

• DailyAge—Indicates the maximum number of days SGM is to archive daily network statistics reports. For more information, see the description of the sgm statreps dailyage and sgm repdailyage commands in the “SGM Commands and Descriptions” section on page B-2.

• CustomAge—Indicates the maximum number of days SGM is to archive custom network statistics reports. For more information, see the description of the sgm repcustage command in the “SGM Commands and Descriptions” section on page B-2.

• WebNames—Indicates whether SGM is to show real node names or display names in Web pages. For more information, see the description of the sgm webnames [display | real] command in the “SGM Commands and Descriptions” section on page B-2.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMPrinting SGM Windows

• WebUtil—Indicates whether SGM is to display send and receive utilization for linksets and links as percentages or in Erlangs, in Web pages. For more information, see the description of the sgm webutil [percent | erlangs] command in the “SGM Commands and Descriptions” section on page B-2.

• Timer file for last report run—Indicates timer activities during the last report run by SGM. The timer file is useful for identifying how much time SGM spends gathering report data and generating reports.

Printing SGM WindowsYou can print most SGM windows, as well as the topology map, for those times when you need hardcopy.

To print an SGM window, use one of the following procedures:

• From most SGM windows, select File > Print from the SGM Main Menu.

• From the Topology Window, select File > Print > All from the SGM Main Menu, if you want to print the map of your entire network, not just the part that is visible in the current topology map view.

• From the Topology Window, select File > Print > Display from the SGM Main Menu, if you want to print just the part of your network that is visible in the current topology map, not the map of your entire network.

SGM displays the Print dialog (Figure 3-92).


78-15589-01

Chapter 3 Managing ITP Networks Using SGMConnecting to a New Server

Figure 3-92 Print Dialog

The Print dialog enables you to specify print settings, such as which printer to print to, whether to send output to a file (the default location for the print file is your home directory), and whether to print duplex.

When you are satisfied with your print settings, click Print. SGM prints the map.

To exit the Print dialog at any time without printing, click Cancel.

Connecting to a New ServerSGM enables you to connect the client to a new SGM server. For example, you can monitor two or more networks from the same SGM client, simply by switching servers. Or, if you have two SGM servers monitoring the same network, and one server fails, the SGM client automatically switches to the secondary server.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMConnecting to a New Server

To connect the client to a new server:

Step 1 (Optional) If you want to determine the default host name before you connect to the new server, it is contained in the SERVER_NAME entry in the System.properties file:

• If you installed SGM in the default directory, /opt, then the location of the System.properties file is /opt/CSCOsgm/properties/System.properties.

• If you installed SGM in a different directory, then the System.properties file is located in that directory.

Step 2 Select File > Connect to New Server from the SGM Main Menu. SGM displays the Connect to New Server Dialog (Figure 3-93).

Figure 3-93 Connect to New Server Dialog

Step 3 Enter the name of the new server, or its IP address, in the Server Name or IP Address field.

Step 4 Enter the SGM Naming Server UDP port number for the new server in the Name Server Port field. The default value is 44742.

Step 5 Click OK. SGM stops the SGM client, then restarts the client connected to the new server.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMIntegrating SGM with Other Products

Integrating SGM with Other ProductsSGM does not require either CiscoWorks2000 or HP OpenView, but SGM does integrate with those products to provide added value. See the following sections for more information:

• Integrating SGM with HP OpenView, page 3-401

• Integrating SGM with CiscoWorks2000, page 3-402

Integrating SGM with HP OpenViewSGM can integrate with HP OpenView during installation, registering to receive forwarded traps. See the “Installing SGM on Solaris” chapter of the Cisco Signaling Gateway Manager Installation Guide for more information.

You can also integrate SGM with HP OpenView after installation, using the sgm trapsetup command. See the “SGM Command Reference” section on page B-1 for more information.

If you select HP OpenView as the source of traps in SGM, keep the following considerations in mind:

• If HP OpenView is not running when you start the SGM servers, SGM’s sgmTrapReceiver process cannot start and is labeled Stopped.

• If HP OpenView is running when you start the SGM servers, but ovtrapd (HP OpenView’s trap receiver process) is not running, sgmTrapReceiver starts and is reported as Running, but it cannot receive traps.

• If you start the SGM servers, then start HP OpenView, sgmTrapReceiver does not start automatically. You must start sgmTrapReceiver using the Process Manager.

• If sgmTrapReceiver is running and HP OpenView is stopped using the ovstop command, sgmTrapReceiver stops itself, and does not start automatically when HP OpenView is restarted. You must start sgmTrapReceiver using the Process Manager.

• If sgmTrapReceiver is running and ovtrapd stops running for any reason, sgmTrapReceiver cannot detect that ovtrapd is no longer running. sgmTrapReceiver continues running but cannot receive traps until ovtrapd is restarted. When ovtrapd is restarted, sgmTrapReceiver begins receiving traps again automatically.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMIntegrating SGM with Other Products

Integrating SGM with CiscoWorks2000SGM can integrate with CiscoWorks2000 during installation, registering with CiscoWorks2000 as an installed application. See the “Installing SGM on Solaris” and “Installing SGM on Windows” chapters of the Cisco Signaling Gateway Manager Installation Guide for more information.

You can also integrate SGM with CiscoWorks2000 after installation, using the sgm cw2ksetup command. See the “SGM Command Reference” section on page B-1 for more information.

When SGM is integrated with CiscoWorks2000, you can launch the CiscoWorks2000 Device Center and CiscoView from the SGM Main Menu. See the following sections for more information:

• Launching the CiscoWorks2000 Device Center, page 3-402

• Launching CiscoView, page 3-403

Launching the CiscoWorks2000 Device Center

The CiscoWorks2000 Device Center provides a number of useful Web-based device-monitoring functions, including reachability trends, response time trends, interface status, Syslog browsing, and a detailed inventory.

To link SGM to the Device Center:

Step 1 Make sure CiscoWorks2000 is installed in the network.

Step 2 Select a node that you know CiscoWorks2000 is monitoring, or an associated linkset, in a window. If you select a non-ITP node, or a node with a status of Unmanaged or a Device Type of Unknown, the CiscoWorks2000 menu option is grayed-out.

Step 3 Select Products > CiscoWorks2000 > Device Center from the SGM Main Menu.

Step 4 At the prompt, enter a CiscoWorks2000 user ID and password. SGM links to CiscoWorks2000 Device Center dashboard.


78-15589-01

Chapter 3 Managing ITP Networks Using SGMUsing the Windows Start Menu

Launching CiscoView

CiscoView provides a real-time, color-coded, graphical representation of Cisco ITPs. You can use CiscoView to quickly identify an incorrect status on a port or interface. If you are running CiscoWorks2000 on UNIX or Windows, you can access CiscoView through the link to the Web version of CiscoWorks2000.

To link SGM to CiscoView:

Step 1 Select a node that you know CiscoWorks2000 is monitoring, or an associated linkset, in a window. If you select a non-ITP node, or a node with a status of Unmanaged or a Device Type of Unknown, the CiscoWorks2000 menu option is grayed-out.

Step 2 Select Products > CiscoWorks2000 >CiscoView from the SGM Main Menu.

Step 3 At the prompt, enter a CiscoWorks2000 user ID and password. SGM links to CiscoView.

Using the Windows Start MenuThis section includes the following information:

• Launching the SGM Client, page 3-404

• Launching the SGM GTT Client, page 3-404

• Changing the Default SGM Server Name, page 3-404

• Changing the Default SGM Telnet Path, page 3-405

• Launching the SGM DOS Prompt, page 3-405

• Launching the SGM SSL Certificate Tool, page 3-406

• Uninstalling SGM, page 3-406

• Viewing the SGM README File, page 3-406


78-15589-01


Launching the SGM ClientTo launch the SGM Client, use one of the following procedures:

• Double-click the SGM icon on the desktop.

• Select Start > Programs > Cisco SGM Client > Launch SGM Client from the Windows Start menu.

SGM launches the SGM Client.

Launching the SGM GTT ClientTo launch the SGM GTT Client, select Start > Programs > Cisco SGM Client > Launch SGM GTT Client from the Windows Start menu.

SGM launches the SGM GTT Client.

Changing the Default SGM Server NameIf there is a failure of the IP address or host name to which your SGM client is bound, you can change the default SGM server name from the Windows Start menu.

To change the default SGM server name, use the following procedure:

Step 1 Close all open SGM windows.

Step 2 Select Start > Programs > Cisco SGM Client > Modify Default SGM Server Name. SGM opens a DOS window, and asks you to enter the name of the new default SGM server.

Step 3 Type the name of the new default SGM server, and press Enter. SGM sets the default server to the new name you entered.

See the “Connecting to a New Server” section on page 3-399 for more information about changing the default SGM server name.


78-15589-01


Changing the Default SGM Telnet PathSGM provides a default Telnet interface for Telnet sessions, but you can also specify a path to a different Telnet application, if you prefer.

To specify the path to the new Telnet application, use the following procedure:

Step 1 Select Start > Programs > Cisco SGM Client > Modify Default SGM Telnet Path. SGM opens a DOS window, and asks you to enter the full Telnet executable pathname.

Step 2 Type the new pathname, and press Enter. If you do not enter a new pathname, SGM uses the system default Telnet executable. SGM asks you to enter any special parameters you want to pass to the new Telnet application. The default is n, for no special parameters.

Step 3 Type the special parameters you want to pass to the new Telnet application, and press Enter. SGM uses the new Telnet application for all Telnet sessions on the SGM client, such as when you select View > Telnet to > ITP.

Step 4 Close the DOS window.

Launching the SGM DOS PromptTo launch a DOS prompt for SGM from the Windows Start menu, select Start > Programs > Cisco SGM Client > SGM DOS Prompt. SGM opens a DOS window, starting in the bin directory:

• If you installed the SGM client in the default directory, C:\Program Files, then the DOS prompt starts at C:\Program Files\SGMClient\bin.

• If you installed the SGM client in a different directory, then the bin directory is located in that directory.


78-15589-01


Launching the SGM SSL Certificate ToolTo launch the SGM SSL Certificate Tool from the Windows Start menu, select Start > Programs > Cisco SGM Client > SGM SSL Certificate Tool.

Uninstalling SGMYou can uninstall SGM from the Windows Start menu. For details, see the “Uninstalling SGM” section of the Cisco Signaling Gateway Manager Installation Guide.

Viewing the SGM README FileThe SGM README file contains late-breaking information about SGM that might not be found in the other product documentation. To open the SGM README file from the Windows Start menu, select Start > Programs > Cisco SGM Client > View README.


78-15589-01

Cisco S78-15589-01

C H A P T E R 4
Configuring SGM Security
This chapter provides the following information about configuring SGM security and limiting access to SGM:

• Configuring SGM User-Based Access, page 4-1

• Implementing SSL Support in SGM, page 4-24

• Limiting SGM Client Access to the SGM Server (Solaris Only), page 4-38

Configuring SGM User-Based AccessSGM enables you to control who is allowed to do what in SGM, beyond simply specifying root and non-root users. SGM calls this ability User-Based Access.

User-Based Access provides multi-level password-protected access to SGM features. Each user can have a unique user name and password. Each user can also be assigned to one of five levels of access, which control the list of SGM features accessible by that user.

To configure SGM User-Based Access, perform the tasks in the following sections. Required and optional tasks are indicated.

• Implementing SGM User-Based Access (Solaris Only), page 4-2 (Required)

• Creating Secure Passwords, page 4-5 (Required)

• Configuring SGM User Authentication Levels (Solaris Only), page 4-6 (Required)

• Automatically Disabling Users and Passwords (Solaris Only), page 4-10 (Optional)


Chapter 4 Configuring SGM SecurityConfiguring SGM User-Based Access

• Manually Disabling Users and Passwords (Solaris Only), page 4-13 (Optional)

• Enabling and Modifying Users and Passwords (Solaris Only), page 4-15 (Optional)

• Maintaining Your SGM Security System (Solaris Only), page 4-17 (Optional)

• Specifying a Super User (Solaris Only), page 4-22 (Optional)

Implementing SGM User-Based Access (Solaris Only)Before you can access SGM’s full suite of security commands, you must enable SGM User-Based Access, configure the type of security authentication you want to use, and begin adding users to your authentication lists.

To implement SGM User-Based Access, use the following procedure:




# ./sgm useraccess enable

SGM User-Based Access is enabled the next time you restart the SGM server.

Step 3 If you have already configured the type of SGM security authentication you want to use, skip to Step 4.

Otherwise, configure the type of SGM security authentication you want to use:

• Local authentication allows you to create user accounts and passwords local to the SGM system. When using this method, you can use SGM User-Based Access commands manage user names, passwords, and access levels.

To enable local authentication, enter the following command:

# ./sgm authtype local


78-15589-01


• Solaris authentication uses standard Solaris-based user accounts and passwords, as specified in the /etc/nsswitch.conf file. Authentication can be provided by the local /etc/passwd file or from a distributed Network Information Services (NIS) system. You can use all SGM User-Based Access commands except the following commands:

– sgm disablepass

– sgm passwordage

– sgm userpass

You must use Solaris commands, such as passwd, to manage passwords.

Users also cannot change their passwords using the SGM client. Instead, they must manage their passwords on the external authentication servers, using Solaris commands, such as passwd.

All new passwords take effect the next time SGM automatically synchronizes local SGM passwords with Solaris, or you can manually synchronize passwords at any time using the sgm syncusers command.

In addition, you must be logged in as the root user, not a super user, to use the following SGM commands:

– sgm adduser

– sgm disableuser

– sgm enableuser

– sgm updateuser

To enable Solaris authentication, enter the following command:

# ./sgm authtype solaris

See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of each of the above SGM commands.

Step 4 To add a user to your SGM User-Based Access authentication list, use the following command:

# ./sgm sgm adduser username

where username is the name of the user.


78-15589-01


Note If sgm authtype is set to solaris, you must be logged in as the root user, not as a super user, to enter this command.

SGM also prompts you for the authentication level for the user. Valid levels are:

• 1—Basic User

• 2—Power User

• 3—Network Operator

• 4—Network Administrator

• 5—System Administrator

For more information about authentication levels, see the “Configuring SGM User Authentication Levels (Solaris Only)” section on page 4-6.

If sgm authtype is set to local, SGM also issues the following prompts:

• SGM prompts you for the user’s password. When setting the password, follow the rules and considerations in the “Creating Secure Passwords” section on page 4-5.

• SGM asks whether you want to force the user to change the password at the next login. The default is not to force the user to change the password.

(Whenever a user needs to change a password, SGM issues an appropriate message and prompts for the user name and new password.)

Note If sgm authtype is set to solaris, users cannot change their passwords using the SGM client. Instead, they must manage their passwords on the external authentication servers, using Solaris commands, such as passwd. All new passwords take effect the next time SGM automatically synchronizes local SGM passwords with Solaris, or you can manually synchronize passwords at any time using the sgm syncusers command. See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of this command.


78-15589-01


At this point, you have implemented your basic SGM User-Based Access. Users must now log in before using the SGM client, the GTT client, and SGM Web-based functions. Use the remaining procedures in this section to customize your SGM security system.

Note After you implement SGM User-Based Access, if a user logs in on one SGM or GTT client, then logs in on a second SGM or GTT client, SGM closes the first client and records the event in the system security log.

Creating Secure PasswordsWhen setting passwords in SGM, keep in mind the following rules and considerations:

• The password must be at least 6 characters, up to an unlimited number of characters. However, passwords longer than 15 characters are not recommended.

• The password cannot be identical to the user name.

• The new password cannot be the same as the old password.

• SGM does not allow users to switch back-and-forth between two passwords.

• The password cannot be a common word. SGM uses the dictionary located at /usr/lib/share/dict/words to determine whether a word is common. To override the SGM dictionary, change the DICT_FILE entry in the System.properties file:

– To disable the SGM dictionary and allow common words, change the DICT_FILE entry to:

DICT_FILE=/dev/null

– To use a custom dictionary, change the DICT_FILE entry to:

DICT_FILE=/new-dictionary

where new-dictionary is the path and filename of the custom dictionary file, such as /users/rolive/words. Each line in the custom dictionary must contain a single word, with no leading or trailing spaces.


78-15589-01


Configuring SGM User Authentication Levels (Solaris Only)This section describes the user authentication levels in SGM, and the SGM functions and Web displays available at each level:

• Basic User (Level 1) Access, page 4-6

• Power User (Level 2) Access, page 4-7

• Network Operator (Level 3) Access, page 4-8

• Network Administrator (Level 4) Access, page 4-8

• System Administrator (Level 5) Access, page 4-9

The authentication level that includes a function is the lowest level with access to that function. The function is also available to all higher authentication levels. For example, a System Administrator also has access to all Network Administrator functions.

Note Access to SGM information and downloads on Cisco.com is already protected by Cisco.com, and is not protected by SGM.

To configure the authentication level for a user, use the sgm adduser command, as described in the “Implementing SGM User-Based Access (Solaris Only)” section on page 4-2, or the sgm updateuser or sgm newlevel command, as described in the “Enabling and Modifying Users and Passwords (Solaris Only)” section on page 4-15.

Basic User (Level 1) Access

Basic Users can view SGM data, load SGM files, and use SGM drill-down menus.

Basic Users have access to the following SGM functions:

• Connecting to a new server

• Applying changes to views

• Loading the DEFAULT view and existing views, but not saving them

• Editing, loading, and applying preferences files, but not saving them

• Viewing and manipulating the topology map, and saving it as a JPEG, but not saving icon locations


78-15589-01


• Viewing nodes, signaling points, linksets, events, details, and notes

• Viewing the ITP home page

• Loading existing event filters, but not saving them

• Printing SGM windows

Basic Users have access to the following SGM Web displays:

• Server Home Page

• System README

• Network Status

• System Data Files

– Notes

– Views

– Preferences

• Viewing SGM documentation

• Downloading client software

Power User (Level 2) Access

Power Users can change some aspects of the way SGM works.

Power Users have access to the following SGM functions:

• Editing nodes, signaling points, linksets, events, and views

• Ignoring and unignoring linksets and links

• Saving preferences files, event filters, and views

• Acknowledging events

• Viewing ITP real-time data and charts

Power Users have access to the following SGM Web displays:

• System Status, excluding User Accounts and System Troubleshooting

• Accounting Statistics Reports

• Network Statistics Reports


78-15589-01


Network Operator (Level 3) Access

Network Operators can make changes to SGM network files.

Network Operators have access to the following SGM functions:

• Launching CiscoWorks2000 and HP OpenView

• Polling nodes

• Telnetting to the ITP

• Viewing route table files and GTT files, but not editing them

Network Operators have access to the following SGM Web displays:

• Point Code Inventories

• System Data Files

– Route table files

– Global Title Translation (GTT) table files

– System ITP IOS README

Network Administrator (Level 4) Access

Network Administrators have access to all SGM client functions, but not all functions in Solaris.

Network Administrators have access to the following SGM functions:

• SNMP configuration

• Network Discovery

• Deleting nodes, signaling points, linksets, and links

• Managing and unmanaging nodes

• Editing and saving route table files and GTT files

Network Administrators have access to the following SGM Web displays:

• System Data Files: Discovery Seeds


78-15589-01


System Administrator (Level 5) Access

System Administrators have access to all functions in SGM and in Solaris.

System Administrators have access to the SGM Process Manager.

System Administrators have access to the following SGM Web displays:

• System Messages and Logs

• System Status, including User Accounts and System Troubleshooting

• Trap Host Configuration, including SNMP configuration information

• System Information

– System Command Log

– System Console Log

– System Event Automation Log

– System Install Log

– System Process Services

– System Properties

– System Report Parameters and Timers Page

– System Reports Log

– System Root Variables

– System Security Log

– System Web Access Log

– System Web Error Log


78-15589-01


Automatically Disabling Users and Passwords (Solaris Only)After you have implemented the basic SGM User-Based Access security system, you can customize the system to automatically disable users and passwords when certain conditions are met.

To automatically disable users and passwords, use the following procedures:


Step 2 Enter the following command:


Step 3 (Optional) You can configure SGM to generate an alarm after a specified number of unsuccessful login attempts by a user. To do so, enter the following command:

# ./sgm badloginalarm number-of-attempts

where number-of-attempts is the number of unsuccessful login attempts allowed before SGM generates an alarm.

The valid range is 1 unsuccessful attempt to an unlimited number of unsuccessful attempts. The default value is 5 unsuccessful attempts.

To disable this function (that is, to prevent SGM from automatically generating an alarm after unsuccessful login attempts), enter the following command:

# ./sgm badloginalarm clear

Step 4 (Optional) You can configure SGM to disable a user’s security authentication automatically after a specified number of unsuccessful login attempts. To do so, enter the following command:

# ./sgm badlogindisable number-of-attempts

where number-of-attempts is the number of unsuccessful login attempts allowed before SGM disables the user’s authentication. SGM does not delete the user from the authentication list, SGM only disables the user’s authentication.



78-15589-01


To re-enable the user’s authentication, use the sgm enableuser command.

To disable this function (that is, to prevent SGM from automatically disabling a user’s authentication after unsuccessful login attempts), enter the following command:

# ./sgm badlogindisable clear

Step 5 (Optional) SGM keeps track of the date and time each user last logged in. You can configure SGM to disable a user’s security authentication automatically after a specified number of days of inactivity. To do so, enter the following command:

# ./sgm inactiveuserdays number-of-days

where number-of-days is the number of days a user can be inactive before SGM disables the user’s authentication. SGM does not delete the user from the authentication list, SGM only disables the user’s authentication.

The valid range is 1 day to an unlimited number of days. There is no default setting.


This function is disabled by default. If you do not specify the sgm inactiveuserdays command, user accounts are never disabled as a result of inactivity.

If you have enabled this function and you want to disable it (that is, to prevent SGM from automatically disabling user accounts as a result of inactivity), enter the following command:

# ./sgm inactiveuserdays clear

Step 6 (Optional) If sgm authtype is set to local, you can configure SGM to force users to change their passwords after a specified number of days.

To configure SGM to force users to change their passwords after a specified number of days, enter the following command:

# ./sgm passwordage number-of-days

where number-of-days is the number of days allowed before users must change their passwords.

The valid range is 1 day to an unlimited number of days. There is no default setting.


78-15589-01


This function is disabled by default. If you do not specify the sgm passwordage command, users never need to change their passwords.

If you have enabled this function and you want to disable it (that is, prevent SGM from forcing users to change passwords), enter the following command:

# ./sgm passwordage clear

Note If sgm authtype is set to solaris, you cannot use the sgm passwordage command. Instead, you must manage passwords on the external authentication servers.

Step 7 (Optional) You can configure SGM to disconnect an SGM or GTT client automatically after a specified number of minutes of inactivity. To do so, enter the following command:

# ./sgm clitimeout number-of-minutes

where number-of-minutes is the number of minutes an SGM or GTT client can be inactive before SGM disconnects the client.

The valid range is 1 minute to an unlimited number of minutes. There is no default value.

This function is disabled by default. If you do not specify the sgm clitimeout command, clients are never disconnected as a result of inactivity.

If you have enabled this function and you want to disable it (that is, never disconnect a client as a result of inactivity), enter the following command:

# ./sgm clitimeout clear


78-15589-01


Manually Disabling Users and Passwords (Solaris Only)As described in the “Automatically Disabling Users and Passwords (Solaris Only)” section on page 4-10, you can customize SGM to automatically disable users and passwords when certain conditions are met. However, you can also manually disable SGM User-Based Access users and passwords when the need arises. To do so, use the following procedures:




Step 3 (Optional) To delete a user entirely from the SGM User-Based Access authentication list, enter the following command:

# ./sgm deluser username


If you later decide to add the user back to the authentication list, you must use the sgm adduser command.

Step 4 (Optional) If sgm authtype is set to local, you can disable a user’s password. To do so, enter the following command:

# ./sgm disablepass username

where username is the name of the user. SGM does not delete the user from the authentication list, SGM only disables the user’s password.

Note If sgm authtype is set to solaris, you cannot use the sgm disablepass command. Instead, you must manage passwords on the external authentication servers.

The user must change his password the next time he logs in.


78-15589-01


You can also re-enable the user’s authentication with the same password, or with a new password:

• To re-enable the user’s authentication with the same password as before, use the sgm enableuser command.

• To re-enable the user’s authentication with a new password, use the sgm userpass command.

Step 5 (Optional) To disable a user’s authentication, but not the user’s password, use the following command:

# ./sgm disableuser username



SGM does not delete the user from the authentication list, SGM only disables the user’s authentication. The user cannot log in until you re-enable the user’s authentication:




78-15589-01


Enabling and Modifying Users and Passwords (Solaris Only)Of course, SGM also enables you to re-enable users and passwords, and modify user accounts. To enable and modify users and passwords, use the following procedures:




Step 3 (Optional) To re-enable a user’s authentication, which had been disabled either automatically by SGM or by a super user, enter the following command:

# ./sgm enableuser username

where username is the name of the user. SGM re-enables the user’s authentication with the same password as before.


Step 4 (Optional) If sgm authtype is set to local, you can change a user’s password, or re-enable the user’s authentication with a new password, if the user’s authentication had been disabled either automatically by SGM or by a super user. To change a password or to re-enable a user’s authentication with a new password, enter the following command:

# ./sgm userpass username



78-15589-01


SGM prompts you for the new password. When setting the password, follow the rules and considerations in the “Creating Secure Passwords” section on page 4-5.

If the user’s authentication has also been disabled, SGM re-enables the user’s authentication with the new password.

Note If sgm authtype is set to solaris, you cannot use the sgm userpass command. Instead, you must manage passwords on the external authentication servers.

Step 5 (Optional) To change a user’s authentication level and password, enter the following command:

# ./sgm updateuser username



SGM prompts you for the new authentication level. Valid levels are:

• 1—Basic User

• 2—Power User





If sgm authtype is set to local, SGM also prompts you for the user’s new password. When setting the password, follow the rules and considerations in the “Creating Secure Passwords” section on page 4-5.


78-15589-01


Step 6 (Optional) To change a user’s authentication level, but not the user’s password, enter the following command:

# ./sgm newlevel username


SGM prompts you for the new authentication level. Valid levels are:

• 1—Basic User

• 2—Power User





Maintaining Your SGM Security System (Solaris Only)SGM provides the following procedures that help you monitor and maintain your security system:




Step 3 (Optional) You can configure SGM to display a message of the day (Figure 4-1), which is a user-specified SGM system notice. You can use the message of the day to inform users of important changes or events in the SGM system. The message of the day also gives users an opportunity to exit the SGM or GTT client before launching.


78-15589-01


Figure 4-1 Message of the Day Dialog

If the message of the day is enabled, it is displayed whenever a user attempts to launch an SGM or GTT client:

• If the user accepts the message, the client launches.

• If the user declines the message, the client does not launch.

If you want to configure SGM to display a message of the day, you must first enable the function. To do so, enter the following command:

# ./sgm motd enable

SGM displays the following prompt:

Enter location of the message of the day file: [/opt/CSCOsgm/etc/motd]


78-15589-01


To accept the default value, press Enter; or type a different location and press Enter. SGM displays the following messages:

Setting Message of the Day File to: [/opt/CSCOsgm/etc/motd]

Message of the Day File set to: [/opt/CSCOsgm/etc/motd]

SGM server must be restarted for changes to take effect.

Initially, the file is blank; enter the following command to specify the message text:

# ./sgm motd edit

You can also use the sgm motd edit command at any time to modify the text of the message of the day.

To display the contents of the message of the day file, enter the following command:

# ./sgm motd cat

To disable this function (that is, to stop displaying the message of the day whenever a user attempts to launch an SGM or GTT client), enter the following command:

# ./sgm motd disable

Step 4 (Optional) If sgm authtype is set to solaris, SGM automatically synchronizes local SGM passwords with Solaris at 11:59 each night. However, you can also manually synchronize passwords at any time by entering the following command:

# ./sgm syncusers

Note You must be logged in as the root user, not as a super user, to enter this command.


78-15589-01


Step 5 (Optional) To list all currently defined users in the SGM User-Based Access authentication list, enter the following command:

# ./sgm listusers

SGM displays the following information for each user:

• User name

• Last time the user logged in

• User’s authentication access level

• User’s current authentication status, such as Account Enabled or Password Disabled

To list information for only a specific user, enter the following command:

# ./sgm listusers username


Note You can also view user account information on the SGM User Accounts Web page. For more information, see the “Viewing SGM User Account Information” section on page 7-116.

Step 6 (Optional) To display the contents of the system security log with PAGER, enter the following command:

# ./sgm seclog

The following security events are recorded in the log:

• All changes to system security, including adding users

• Login attempts, whether successful or unsuccessful, and logoffs

• Attempts to switch to another user's account, whether successful or unsuccessful

• Attempts to access files or resources of higher authentication level

• Access to all privileged files and processes

• Operating system configuration changes and program changes, at the Solaris level


78-15589-01


• SGM restarts

• Failures of computers, programs, communications, and operations, at the Solaris level

To clear the log and restart the server, enter the following command:

# ./sgm seclog clear

The default path and filename for the system security log file is /opt/CSCOsgm/logs/sgmSecurityLog.txt. If you installed SGM in a directory other than /opt, then the system security log file is located in that directory.

Note You can also view the system security log on the SGM System Security Log Web page. For more information, see the “Viewing the SGM System Security Log” section on page 7-113.

Step 7 (Optional) If you inadvertently delete your user accounts, or make other unwanted changes to your SGM security information, SGM enables you to restore the security-related parts of the SGM data files from the previous night’s backup. To restore the files, enter the following command:

# ./sgm restore security

Note You must be logged in as the root user, not as a super user, to enter this command.

Step 8 (Optional) If for some reason you want to completely disable SGM User-Based Access, enter the following command:

# ./sgm useraccess disable

SGM User-Based Access is disabled the next time you restart the SGM server.


78-15589-01


Specifying a Super User (Solaris Only)SGM enables you to specify one or more super users. A super user can perform most functions that otherwise require the user to be logged in as the root user. (The root user can still perform those functions, too.) If you specify a super user, the server also runs as the super user and not as the root user.

Caution As a super user, you can adversely affect your operating environment if you are unaware of the effects of the commands you use. If you are a relatively inexperienced UNIX user, limit your activities as a super user to the tasks described in this document.

To specify a super user, use the following procedure:

Step 1 Log in as the root user, as described in the “Becoming the Root User (Solaris Only)” section on page 3-2.



# ./sgm superuser username


When you specify a super user, keep in mind the following considerations:

• The user must exist in the local /etc/passwd file. You cannot specify a user that is defined in a distributed Network Information Services (NIS) system.

• The super user does not have access to all SGM commands. You must still be logged in as the root user to enter the following commands:

– sgm backup

– sgm browserpath

– sgm certtool

– sgm clean

– sgm cleanall


78-15589-01


– sgm cw2ksetup

– sgm evilstop

– sgm jspport

– sgm keytool

– sgm killclients

– sgm reboot

– sgm restore

– sgm restoreprops

– sgm ssl

– sgm sslstatus

– sgm stopclients

– sgm superuser

– sgm syncusers

– sgm trapsetup

– sgm uninstall

– sgm webport

• If sgm authtype is set to solaris, you must still be logged in as the root user to enter the following commands:

– sgm adduser

– sgm disableuser

– sgm enableuser

– sgm updateuser


78-15589-01

Chapter 4 Configuring SGM SecurityImplementing SSL Support in SGM

• If the SNMP trap port number on the SGM server is less than 1024, you cannot use the sgm superuser command. To correct this situation, you must specify a new SNMP trap port number that is greater than 1024:

– To change the SNMP trap port number in the ITPs in your network, use the snmp-server host command. By default, SGM listens for traps from trap multiplexing devices and NMS applications on port 44750, so that is a good port number to choose. The SNMP trap port number must be the same on all ITPs in your network.

– See the description of the snmp-server host command in the “ITP Requirements” section of the Cisco Signaling Gateway Manager Installation Guide for more information.

– Use the sgm trapsetup command to change the SNMP trap port number in the SGM server to match the port number in the ITPs in your network. See the description of the sgm trapsetup command in the “SGM Command Reference” section on page B-1 for more information.

Implementing SSL Support in SGMYou can implement Secure Sockets Layer (SSL) support in your SGM system. When you do so, SGM uses secure sockets to encrypt all communication between the SGM clients and server.


• Enabling SSL Support in SGM, page 4-25

• Downloading the SGM Server’s Self-Signed SSL Certificate, page 4-28

• Importing an SSL Certificate to an SGM Client, page 4-29

• Exporting an SSL Certificate, page 4-32

• Managing SSL Support in SGM, page 4-36

• Disabling SSL Support in SGM, page 4-37


78-15589-01


Enabling SSL Support in SGMTo enable SSL support in SGM, perform the following tasks:

Step 1 Obtain the SSL-enabled version of SGM.

Due to US government restrictions on the export of SSL-enabled software, Cisco provides two versions of SGM: Basic SGM, which does not provide SSL support, and SSL-enabled SGM, which does.

To obtain SSL-enabled SGM, you must contact Cisco TAC or your Cisco Account Team. They will help you apply for an export licence and download and install SSL-enabled SGM.

Step 2 Install an SSL key/certificate pair in SGM, using one of the following procedures:

• To install a new SSL key and a self-signed certificate, generate the key and certificate by logging in as the root user on the SGM server and entering the sgm keytool genkey command.

SGM stops the SGM server and issues the following prompts:

Country Name (2 letter code) []:State or Province Name (full name) []:Locality Name (eg, city) []:Organization Name (eg, company) []:Organizational Unit Name (eg, section) []:Common Name (your hostname) []:Email Address []:

Enter the requested information.

SGM generates the following files:

– /opt/CSCOsgm/etc/ssl/server.key is the SGM server’s private key. Ensure that unauthorized personnel cannot access this key.

– /opt/CSCOsgm/etc/ssl/server.cer is the self-signed SSL certificate.

– /opt/CSCOsgm/etc/ssl/server.csr is a certificate signing request (CSR). It is not used if you are using a self-signed SSL certificate.


78-15589-01


• To install a new SSL key and a CA-signed certificate, generate the key and a CSR by logging in as the root user on the SGM server and entering the sgm keytool genkey command.

SGM stops the SGM server and issues the following prompts:

Country Name (2 letter code) []:State or Province Name (full name) []:Locality Name (eg, city) []:Organization Name (eg, company) []:Organizational Unit Name (eg, section) []:Common Name (your hostname) []:Email Address []:

Enter the requested information.

SGM generates the following files:

– /opt/CSCOsgm/etc/ssl/server.key is the SGM server’s private key. Ensure that unauthorized personnel cannot access this key.

– /opt/CSCOsgm/etc/ssl/server.csr is a CSR.

– /opt/CSCOsgm/etc/ssl/server.cer is the self-signed SSL certificate. It is not used if you are using a CA-signed SSL certificate; the CA-signed certificate overrides the self-signed certificate.

Print the CSR in X.509 format, by logging in as the root user on the SGM server and entering the sgm keytool print_csr command.

Send the CSR to a certificate authority (CA) to be signed.

After the CA signs the certificate, log in as the root user on the SGM server and enter the following command:

# ./sgm keytool import_cert cert_filename

where cert_filename is the name of the signed certificate.

SGM stops the SGM server and imports the certificate in X.509 format.


78-15589-01


• To use an existing signed key/certificate pair, log in as the root user on the SGM server and enter the following command:

# ./sgm keytool import_key key_filename cert_filename

where key_filename is the name of the existing SSL key and cert_filename is the name of the existing signed certificate.

SGM stops the SGM server and imports the SSL key in OpenSSL format and the signed SSL certificate in X.509 format.

Step 3 Enable SSL support in SGM, by logging in as the root user on the SGM server and entering the sgm ssl enable command.

Step 4 Set up the SGM client-side SSL certificate trust relationship, by downloading and importing the self-signed or CA-signed certificate on every remote SGM client, Windows as well as Solaris, that connects to the SGM server.

a. (Self-signed certificate only) Download the self-signed certificate (server.cer), using the procedure in the “Downloading the SGM Server’s Self-Signed SSL Certificate” section on page 4-28.

b. Import the self-signed or CA-signed certificate, using the procedure in the “Importing an SSL Certificate to an SGM Client” section on page 4-29.

Step 5 Restart the SGM client.

The SGM clients can now connect to the SGM server using SSL. All communication between the server and clients is encrypted.

If an SGM or GTT client that is not SSL-enabled attempts to connect to an SSL-enabled SGM server, SGM displays an appropriate warning message and opens the SGM client download page. The user can then download and install a new SGM client to use to connect to that SGM server.

If the client is SSL-enabled but does not have the correct certificate, SGM displays an appropriate warning message and opens the SGM Server SSL Certificate page. The user can then download the signed SSL certificate in X.509 format to the client.


78-15589-01


Downloading the SGM Server’s Self-Signed SSL CertificateIf you have implemented Secure Sockets Layer (SSL) support in your SGM system, you can download the SGM server’s signed SSL certificate to all remote SGM clients that connect to the server using SSL.

To download the certificate from the SGM Server SSL Certificate page, use the following procedure on each remote SGM client:

Step 1 Use one of the following procedures to access the SGM Server Home page:

• Select View > Server > Home Page from the SGM Main Menu.

• Enter the following URL in a Web browser:

https://server_name:1774

where server_name is the name or IP address of the server on which the SGM server is running and 1774 is the Web port being using by SGM. (1774 is the default port number.) If you do not know the name or Web port of the SGM Web Server, contact the system administrator who installed the SGM server software.

SGM displays the SGM Server Home page.

Step 2 Select Server SSL Certificate from the SGM Server Home Page. SGM displays the SGM Server SSL Certificate page.

Step 3 Right-click Download SGM Server SSL Certificate.

Step 4 Select Save Link As from the right-click menu.

Step 5 Select a directory in which to save the certificate (server.cer), and click Save. SGM downloads the server.cer file into the specified directory.


78-15589-01


Importing an SSL Certificate to an SGM ClientIf you have implemented Secure Sockets Layer (SSL) support in your SGM system, you can import the SGM server’s self-signed SSL certificate, or a CA-signed SSL certificate, to all remote SGM clients that connect to the server using SSL.

To import an SSL certificate, use the following procedure on each remote SGM client:

Step 1 Launch the SGM SSL Certificate Tool:

• In Solaris, log in as the root user and enter the following command:


# ./sgm certgui

See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of this command.

• In Windows, select Start > Programs > Cisco SGM Client > SGM SSL Certificate Tool.

SGM displays the SGM Certificate Tool dialog (Figure 4-1).


78-15589-01


Figure 4-2 SGM Certificate Tool Dialog

The SGM Certificate Tool dialog lists all SSL certificates that have been imported by the SGM client, and enables you to import, export, and display detailed information about SSL certificates.

The SGM Certificate Tool dialog displays the following information about each SSL certificate:

• Issued to—Host name of the SGM server to which the SSL certificate was issued.

• Issued by—Certificate authority (CA) that issued the SSL certificate. Self-signed SSL certificates display the host name of the SGM server.

• Expiration Date—Date on which the SSL certificate expires.


78-15589-01


Step 2 Click Import. SGM displays the Open dialog for SSL certificates (Figure 4-1).

Figure 4-3 Open Dialog for SSL Certificates

Use the Open dialog to locate the SSL certificate that you want to import. The Open dialog for an SSL certificate provides the following options:

• To select the directory in which the SSL certificate is located, either accept the default directory displayed in the Look In field, or select a new directory from the drop-down list box. For a self-signed certificate, locate the directory in which you downloaded the certificate.

• To display the sub-folders and files that are in the folder that is up one level from the currently displayed folder, click the Up One Level button.

• To display the sub-folders and files that are on your workstation desktop, click the Desktop button.

• To create a new sub-folder in the displayed folder, click the Create New Folder button.

• To display only icons for sub-folders and files, click the List button.


78-15589-01


• To display detailed information for sub-folders and files, including their size, type, date they were last modified, and so on, click the Details button.

• To specify the type of file to find, and to display all files of that type in the selected directory, select a file type from the Files of Type drop-down list box:

– All files—Displays all files in the selected directory.

When you have located the SSL certificate, select it. SGM displays the name of the certificate in the File Name field.

Step 3 Click Open. SGM closes the Open dialog for an SSL certificate and populates the SGM Certificate Tool dialog with the SSL certificate’s information.

Step 4 Click Exit. SGM imports the self-signed SSL certificate and closes the SGM Certificate Tool dialog.

Exporting an SSL CertificateIf you have implemented Secure Sockets Layer (SSL) support in your SGM system, you can export SSL certificates that have been imported to the SGM client.

To export an SSL certificate, use the following procedure:




# ./sgm certgui





78-15589-01


Step 2 Select a certificate from the list and click Export. SGM displays the Save dialog for SSL certificates (Figure 4-1).

Figure 4-4 Save Dialog for SSL Certificates

Use the Save dialog to export the SSL certificate to another directory. The Save dialog for an SSL certificate provides the following options:

• To select the directory in which the SSL certificate is located, either accept the default directory displayed in the Save In field, or select a new directory from the drop-down list box. For a self-signed certificate, locate the directory in which you downloaded the certificate.

• To display the sub-folders and files that are in the folder that is up one level from the currently displayed folder, click the Up One Level button.

• To display the sub-folders and files that are on your workstation desktop, click the Desktop button.

• To create a new sub-folder in the displayed folder, click the Create New Folder button.

• To display only icons for sub-folders and files, click the List button.

• To display detailed information for sub-folders and files, including their size, type, date they were last modified, and so on, click the Details button.


78-15589-01


• To specify a new name for the SSL certificate, enter the name in the File Name field, or select a file from those listed in the Save In field.

• To specify the type of file to export, and to display all files of that type in the selected directory, select a file type from the Files of Type drop-down list box:

– All files—Displays all files in the selected directory.

When you have located the SSL certificate, select it. SGM displays the name of the certificate in the File Name field.

Step 3 Click Save. SGM closes the Save dialog for an SSL certificate.

Step 4 Click Exit. SGM closes the SGM Certificate Tool dialog and exports the self-signed SSL certificate in X.509 format.

Viewing Detailed Information About an SSL CertificateIf you have implemented Secure Sockets Layer (SSL) support in your SGM system, you can view detailed information about SSL certificates that have been imported to the SGM client.

To view detailed information about an SSL certificate, use the following procedure:




# ./sgm certgui





78-15589-01


Step 2 Select a certificate from the list and click Details. SGM displays the Certificate Information dialog (Figure 4-1).

Figure 4-5 Certificate Information Dialog

You can also display the Certificate Information dialog by clicking the “locked padlock” symbol in the bottom left corner of any SGM window.

The Certificate Information dialog displays the following detailed information for the selected SSL certificate:

• Subject—Device to which the SSL certificate was issued.

The Subject field always includes the Common Name (CN) of the subject, which must match the fully qualified host name of your SGM server, such as sgm-sun8.cisco.com.

The Subject field might also contain other information, such as the Country (C), Organizational Unit (OU), or Organization (O) of the subject.


78-15589-01


• Issuer—CA that issued the SSL certificate.

The Issuer field might include the Common Name (CN) of the issuer, as well as the Country (C), Organizational Unit (OU), or Organization (O) of the issuer.

• Version—Version of the SSL certificate, such as V1.

• Serial number—Serial number associated with the SSL certificate.

• Signature algorithm—Asymmetric algorithm used to ensure that the digital signature is secure, such as MD5withRSA.

• Valid from—Date and time on which the SSL certificate was created or became valid.

• Valid to—Date and time on which the SSL certificate expires.

• Public key—Public key associated with the SSL certificate, used for encryption and for verifying signatures.

Step 3 When you are ready to close the dialog, click OK. SGM closes the Certificate Information dialog.

Step 4 Click Exit. SGM closes the SGM Certificate Tool dialog.

Managing SSL Support in SGMSGM enables you to perform the following tasks to make it easier to manage SSL support in SGM:

• To display the current status of SSL support in SGM, including whether SSL support is enabled or disabled and which SSL keys and certificates exist, use either the sgm ssl status or sgm sslstatus command.

• To print the SGM server’s SSL certificate in X.509 format, use the sgm keytool print_crt command.

• To list the SSL key/certificate pair on the SGM server, use the sgm keytool list command.

• To list all SSL certificates on the SGM client, launch the SGM SSL Certificate Tool. SGM lists each imported certificate, including to whom the certificate was issued, who issued the certificate, and when the certificate expires.


78-15589-01


See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of these commands.

See the “Importing an SSL Certificate to an SGM Client” section on page 4-29 for more information on launching the SGM SSL Certificate Tool.

Disabling SSL Support in SGMSGM enables you to disable SSL support in SGM, and to remove SSL keys and certificates from the SGM server and clients:

• To disable SSL support in SGM, use the sgm ssl disable command.


• To remove all SSL keys and certificates from the SGM server, use the sgm keytool clear command. SGM stops the SGM server, if necessary, and removes the keys and certificates. Before restarting the server, you must either generate new SSL keys using the sgm keytool genkey command, or you must completely disable SSL using the sgm ssl disable command.


• To remove an SSL certificate from the SGM client, launch the SGM SSL Certificate Tool. SGM lists each imported certificate. Select the certificate you want to remove, and click Remove. SGM deletes the certificate from the list.

See the “Importing an SSL Certificate to an SGM Client” section on page 4-29 for more information on launching the SGM SSL Certificate Tool.


78-15589-01

Chapter 4 Configuring SGM SecurityLimiting SGM Client Access to the SGM Server (Solaris Only)

Limiting SGM Client Access to the SGM Server (Solaris Only)

By default, when you first install SGM, all SGM client IP addresses are allowed to connect to the SGM server. However, SGM enables you to limit client access to the server by creating and maintaining the ipaccess.conf file.

You can create the ipaccess.conf file and populate it with a list of SGM client IP addresses that can connect to the SGM server. SGM allows connections from only those clients, plus the local host. If the file exists but is empty, SGM allows connections only from the local host. (SGM always allows connections from the local host.)

When you first install SGM, the ipaccess.conf file does not exist and SGM allows all client IP addresses to connect to the SGM server. To create the ipaccess.conf file and work with the list of allowed client IP addresses, use the following procedure:




Step 3 Create the ipaccess.conf file:

• To create the ipaccess.conf file and add a client IP address to the list, enter the following command:

# ./sgm ipaccess add

• To create the ipaccess.conf file and open the file to edit it directly, enter the following command:

# ./sgm ipaccess edit


78-15589-01


The default directory for the file is located in the SGM installation directory:

• If you installed SGM in the default directory, /opt, then the default directory is /opt/CSCOsgm/etc.


In the ipaccess.conf file, begin all comment lines with a pound sign (#).

All other lines in the file are SGM client IP addresses, with one address per line.

Wildcards (*) are allowed, as are ranges (for example, 1-100). For example, the address *.*.*.* allows all clients to connect to the SGM server.

After you create the ipaccess.conf file, you can use the full set of sgm ipaccess keywords to work with the file:

• clear—Remove all client IP addresses from the ipaccess.conf file, and allow connections from any SGM client IP address.

• list—List all client IP addresses currently in the ipaccess.conf file. If no client IP addresses are listed (that is, the list is empty), connections from any SGM client IP address are allowed.

• rem—Remove the specified client IP address from the ipaccess.conf file.

• sample—Print out a sample ipaccess.conf file.

See the description of the sgm ipaccess command in the See the “SGM Command Reference” section on page B-1 for more details.

Any changes you make to the ipaccess.conf file take effect when you restart the SGM server.


78-15589-01



78-15589-01

Cisco S78-15589-01

C H A P T E R 5
Configuring SGM for Your Network
This chapter provides the following information about configuring SGM to better suit your needs:

• Importing SNMP Community Names from CiscoWorks2000 (Solaris Only), page 5-2

• Retaining Unknown Objects (Solaris Only), page 5-3


• Modifying the Message Display, page 5-20

• Setting the Point Code Format (Solaris Only), page 5-21

• Enabling SNMP Traps (Solaris Only), page 5-23

• Modifying the SGM Event Configuration File (Solaris Only), page 5-26

• Setting Sounds for Events at an SGM Client, page 5-40

• Limiting Traps by IP Address (Solaris Only), page 5-45

• Setting the DISPLAY Variable (Solaris Only), page 5-47

• Backing Up or Restoring SGM Files (Solaris Only), page 5-47

• Removing SGM Data from the SGM Server, page 5-48

• Configuring a Backup SGM Server (Solaris Only), page 5-50

• Telnetting to an ITP, page 5-52


Chapter 5 Configuring SGM for Your NetworkImporting SNMP Community Names from CiscoWorks2000 (Solaris Only)

Importing SNMP Community Names from CiscoWorks2000 (Solaris Only)

SGM enables you to store all SNMP community names in a single database in CiscoWorks2000 Resource Manager Essentials (RME), and to export those names for use by SGM.

To export the database from CiscoWorks2000 RME to SGM, use the following procedure:

Step 1 Log in to CiscoWorks2000 and select Resource Manager Essentials > Administration > Inventory > Export to File.

Step 2 At the prompt, choose the following settings:

Filename Field = sgm

Comma Separated Value Format

Version 3.0

CiscoWorks2000 creates the /var/adm/CSCOpx/files/inventory/sgm file in the default export directory.

Step 3 When you start the SGM server, SGM looks for this file. If the file exists, SGM merges the file with its own community name database, the /opt/CSCOsgm/etc/communities.conf file.

For more information about SNMP, refer to “Configuring SNMP Support” in the Cisco IOS Release 12.2 Configuration Fundamentals Configuration Guide, Part 3, Cisco IOS System Management.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkRetaining Unknown Objects (Solaris Only)

Retaining Unknown Objects (Solaris Only)By default, SGM deletes all Unknown nodes, signaling points, linksets, and links from the SGM database after 7 days. To change the length of time unknown objects stay in the SGM database, use the sgm unknownage command. See the “SGM Command Reference” section on page B-1 for more information on the use of this command.

Each method requires you to be logged in as the root user or as a super user. See the “Becoming the Root User (Solaris Only)” section on page 3-2 and the “Specifying a Super User (Solaris Only)” section on page 4-22 for more information.

Modifying Preference SettingsWhen a user changes some aspect of the SGM client, such as the size of a window or the order of columns in a window, SGM makes note of the user’s preferences on the SGM client and server. SGM saves the user’s preferences to the SGM server when the SGM client exits successfully.

Thereafter, whenever the user launches the SGM client, SGM searches for the user’s SGM preferences. If SGM finds the user’s preferences on the SGM server, SGM launches the SGM client with those preferences. Otherwise, SGM launches the SGM client with the default SGM preferences file.

In addition to the user preferences that are automatically saved, SGM enables you to modify many GUI, data, topology, and table settings that affect the way SGM presents its information.

Note Anyone who uses this SGM client can modify its preference settings, and the changes affect all views running on this client.

The GTT preferences file is separate from the SGM preferences file. For information on modifying GTT preferences, see the “Editing a Global Title Translation Table” section on page 3-290.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkModifying Preference Settings


• Modifying Overall Preference Settings, page 5-5

• Modifying Node Table Column Settings, page 5-16

• Modifying Linkset Table Column Settings, page 5-18

Related Topics:







78-15589-01


Modifying Overall Preference SettingsTo modify overall preference settings, use the following procedure:

Step 1 Select Edit > Preferences from the SGM Main Menu. SGM displays the Preferences window (Figure 5-5).

Figure 5-1 Preferences Window

Step 2 (Optional) To restore all preference settings to the original system default settings, select the File > Load System Default menu option.

Step 3 (Optional) To load an existing preference settings file, select the File > Load menu option. SGM displays the Load File Dialog: Preferences File List dialog (Figure 5-2).


78-15589-01


Figure 5-2 Load File Dialog: Preferences File List Dialog

The Load File Dialog: Preferences File List dialog contains the following fields:


• Name—Name of the preference settings file or folder.

• Last Modified—Date and time the preference settings file or folder was last modified.

• Size (bytes)—Size of the preference settings file or folder, in bytes.

• Number of Files—Total number of preference settings files and folders (displayed in bottom left corner).

To load a preference settings file, enter the name of the file or select it in the list and click OK. SGM loads the preference settings file, closes the Load File Dialog: Preferences File List dialog, and returns to the Preferences window.

To delete a preference settings file from the preference settings file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.


78-15589-01


To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: Preferences File List dialog.

To close the Load File Dialog: Preferences File List dialog without loading a preference settings file or saving any changes to the preference settings file list, click Cancel.

Step 4 (Optional) The General GUI settings enable you to change general display settings for SGM, including which window to display first when starting SGM, and whether to display values in bits or bytes.

To display the General GUI settings, select General GUI in the left pane of the Preferences window. SGM displays the Startup/Exit Settings, General Display Settings, Node Name Setting, and Repaint Priority sections:

a. The Startup/Exit Settings section specifies whether you want to display the Topology Window when you launch the SGM client, and whether you want SGM to prompt you for confirmation when you exit the client.

– Select the SGM: Topology Window checkbox to display the Topology window when SGM is started. The default setting for this checkbox is cleared.

– Select the Confirm Exit checkbox if you want SGM to prompt you for confirmation when you exit the SGM client. The default setting for this checkbox is selected.

b. The General Display Settings section specifies the following settings:

– Select Show Node Domain Names if you want SGM is to show node domain names in its displays. The default setting for this checkbox is cleared (do not show node domain names).

– Select Show Details in Bits Instead of Bytes to specify whether SGM is to display data and data rates in bits or bytes:

– If you want SGM to display data in bits, and data rates in bits per second, select this checkbox. This is the default setting.

– If you want SGM to display data in bytes, and data rates in bytes per second, clear this checkbox.


78-15589-01


– Select Show Utilization as Percentage to specify whether SGM is to display receive and send utilization for linksets and links as a percentage or in Erlangs:

– If you want SGM to display utilization as a percentage, select this checkbox. This is the default setting.

– If you want SGM to display utilization in Erlangs, clear this checkbox.

c. Use the Node Name setting in the Data Display settings to specify how SGM is to display node names:

– If you want SGM to identify nodes by their DNS or user-defined names, select the Show DNS or User-Defined Names radio button. The default setting for this radio button is selected.

– If you want SGM to identify nodes by their IP addresses, select the Show IP Addr in Name Field radio button. The default setting for this radio button is cleared.

d. The Repaint Priority section balances the responsiveness versus efficiency of the SGM client, controlling how quickly the SGM client repaints its displays:

– Slide the selector toward High Repaint Priority if you want to maximize repainting (responsiveness) over communication (efficiency).

– Slide the selector toward High Comm. Priority if you want to maximize communication (efficiency) over repainting (responsiveness).

– The default setting is 3 (the fourth mark from the left).

Step 5 (Optional) The Topology settings enable you to change default settings for the Topology window.

To display the Topology settings, select Topology in the left pane of the Preferences window.

SGM displays the Topology settings:

a. Select Spring Layout Spacing Factor (1-10) to specify how far apart nodes are to be spaced when SGM draws the Spring Layout topology map. Valid values are 1 through 10, with 1 being closer together and 10 being farther apart. The default spacing factor is 5.

Even if you apply preferences and close the Preferences window, the new spacing factor is not reflected in the topology map until you select Topology Tools > Layout > Spring, or click the Spring Layout button.


78-15589-01


b. Select Show Mouse Overs to enable mouse over popups in topology maps. The default setting for this checkbox is selected.

c. Select Auto Save Icon Positions to specify how SGM is to save topology map changes:

– If you want SGM to ask you for confirmation before saving topology map changes when you close the Topology window, clear this checkbox. This is the default setting

– If you want SGM to save topology map changes automatically when you close the Topology window, without asking you for confirmation, select this checkbox.

d. Select Draw Linksets When Dragging Node to specify whether SGM is to draw linkset lines in the topology map as you move nodes:

– If you want SGM to draw the associated linkset lines dynamically as you move a node, select this checkbox.

– If you do not want SGM to draw the associated linkset lines until after you have finished moved a node, clear this checkbox. This is the default setting.

e. Select Show Small SS7 Icons to specify the size of the SS7 icons displayed in the topology map:

– If you want SGM to display large SS7 icons, clear this checkbox. This is the default setting.

– If you want SGM to display small SS7 icons, select this checkbox. This setting can save space in the topology map, making it easier to read.

f. Select Show Non-ITP Devices to specify whether SGM is to display non-ITP nodes and linksets in the topology map:

– If you want SGM to display non-ITP nodes and linksets in the topology map, select this checkbox. This is the default setting.

– If you want SGM to hide non-ITP nodes and linksets in the topology map, clear this checkbox. (Hidden signaling points and linksets are still shown in the left pane.)


78-15589-01


g. Select Show Point Code and Node Name to specify whether SGM is to display point codes as well as node names in the topology map:

– If you want SGM to display point codes but not node names, clear this checkbox. This is the default setting.

– If you want SGM to display both point codes and node names, select this checkbox.

Step 6 (Optional) The Event settings enable you to change the default background color for each type of event in the Event window, to specify whether to display acknowledged events, and to specify the types of event SGM is to display in the Event Window, including the category and severity of event, whether the event is acknowledged, and other properties.

To display the Event settings, select Events in the left pane of the Preferences window. SGM displays the Event settings.

Step 7 (Optional) SGM displays the current event background color settings in the Event Colors section of the Event settings:

• The default background color for None events is white.

• The default background color for Normal events is green.

• The default background color for Admin events is cyan.

• The default background color for Warning events is yellow.

• The default background color for Error events is coral.

To change the background color for any of the event types, click Set Color. SGM displays the Select a Color dialog, which contains the same information as the Pick Grid Color dialog (Figure 3-61).

The Select a Color dialog provides the following options:

• To select an event color from a set of color swatches (the recommended method), click the Swatches tab and select a swatch.

• To select an event color based on color hue, saturation, and brightness (HSB), click the HSB tab, then use one of the following procedures:

– Select a color range on the vertical color bar, then select a specific color by moving the cursor around on the color square.

– Enter specific values in the hue (H), saturation (S), and brightness (B) fields.


78-15589-01


• To select an event color based on the red, green, and blue (RGB) content of the color, click the RGB tab, then select values for the Red, Green, and Blue fields.

• To reset the event color to its initial setting, click Reset.

Whichever method you choose, the selected color is displayed in the Preview field. When you are satisfied with the color, click OK. SGM saves the event color settings and closes the Select a Color dialog.

Step 8 (Optional) The Categories section of the Event settings enables you to specify which event categories you want to display in the Event Window:

Step 9 (Optional) To specify which event categories you want to display in the Event Window, select the Categories section of the Event settings and modify the following settings:

• Status—Checkbox used to indicate whether Status events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Edit—Checkbox used to indicate whether Edit events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• OverWrite—Checkbox used to indicate whether OverWrite events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Trap—Checkbox used to indicate whether Trap events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Ignore—Checkbox used to indicate whether Ignore events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Poll—Checkbox used to indicate whether Poll events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Create—Checkbox used to indicate whether Create events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Login—Checkbox used to indicate whether Login events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Purge—Checkbox used to indicate whether Purge events are to be displayed in the Event Window. The default setting for this checkbox is selected.


78-15589-01


• Delete—Checkbox used to indicate whether Delete events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• LoginDisable—Checkbox used to indicate whether LoginDisable events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Discover—Checkbox used to indicate whether Discover events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• LoginFail—Checkbox used to indicate whether LoginFail events are to be displayed in the Event Window. The default setting for this checkbox is selected.

To select all event category checkboxes. click Select All.

To clear all event category checkboxes, click Deselect All.

Note These are the default categories; there might be additional categories, as defined by the SGM system administrator. For information about custom categories, see the “Modifying the SGM Event Configuration File (Solaris Only)” section on page 5-26.

Step 10 (Optional) To specify which event severities you want to display in the Event Window, select the Severities section of the Event settings and modify the following settings:

• None—Checkbox used to indicate whether events of severity None are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Normal—Checkbox used to indicate whether events of severity Normal are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Admin—Checkbox used to indicate whether events of severity Admin are to be displayed in the Event Window. The default setting for this checkbox is selected.


78-15589-01


• Warning—Checkbox used to indicate whether events of severity Warning are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Error—Checkbox used to indicate whether events of severity Error are to be displayed in the Event Window. The default setting for this checkbox is selected.

Note There might be additional custom severities, as defined by your SGM System Administrator. For information, see the “Modifying the SGM Event Configuration File (Solaris Only)” section on page 5-26.

Step 11 (Optional) To further define the event filter for the Event Window, select the Other section of the Event settings and modify the following settings:

• Acknowledged—Checkbox used to indicate whether only acknowledged events are to be displayed in the Event Window. The default setting for this checkbox is cleared.

• Unacknowledged—Checkbox used to indicate whether only unacknowledged events are to be displayed in the Event Window. The default setting for this checkbox is selected.

• Time Before—Checkbox used to indicate whether only events logged by SGM prior to a specified date and time are to be displayed in the Event Window. The default setting for this checkbox is cleared.

• Time Before Field—Specifies the date and time prior to which events logged by SGM are to be displayed in the Event Window. This field is grayed-out unless the Time Before checkbox is selected.

• Time After—Checkbox used to indicate whether only events logged by SGM after a specified date and time are to be displayed in the Event Window. The default setting for this checkbox is cleared.

• Time After Field—Specifies the date and time after which events logged by SGM are to be displayed in the Event Window. This field is grayed-out unless the Time After checkbox is selected.


78-15589-01


• Message Contains—Checkbox used to indicate whether only events that contain the specified message text are to be displayed in the Event Window. The default setting for this checkbox is cleared.

• Match Case—Checkbox used to indicate whether only events that match the case of the text in the Message Contains field are to be displayed in the Event Window. This field is grayed-out unless the Message Contains checkbox is selected. If the Message Contains checkbox is selected, the default setting for this checkbox is cleared.

These settings are applied to all event displays in the current view.

Step 12 (Optional) To close the Preferences window at any time, click File > Close. If you have changed any preferences, SGM asks if you want to apply the changes before leaving the window:

• Click Yes to apply the changes and close the prompt window and the Preferences window.

• Click No to close the prompt window and the Preferences window without applying or saving any changes.

• Click Cancel to close the prompt window without applying any changes. The Preferences window remains open.

Step 13 When you are satisfied with the preference settings, click Save. SGM displays the Save File Dialog: Preferences File List dialog (Figure 5-3).


78-15589-01


Figure 5-3 Save File Dialog: Preferences File List Dialog

The Save File Dialog: Preferences File List dialog contains the following fields:


• Name—Name of the preference settings file or folder.

• Last Modified—Date and time the preference settings file or folder was last modified.

• Size (bytes)—Size of the preference settings file or folder, in bytes.

• Filename—Name by which you want to save the preference settings file.

If you create a new preference settings file name, you can use any letters, numbers, or characters in the name that are allowed by your operating system. However, if you include any spaces in the new name, SGM converts those spaces to dashes. For example, SGM saves file “a b c” as “a-b-c”.

• Number of Files—Total number of preference settings files and folders (displayed in bottom left corner).


78-15589-01


To save the preference settings file with a new name, use one of the following procedures:


• To save the file with an existing name, overwriting an old preference settings file, select the name in the list and click OK.

SGM saves the preference settings file with the new name, closes the Save File Dialog: Preferences File List dialog, and returns to the Preferences window.

To delete a preference settings file from the preference settings file list, select a file and click Delete. SGM issues an informational message containing the name and location of the deleted file.

To save any changes you made to the list of files, click OK. SGM saves the changes and closes the Load File Dialog: Preferences File List dialog.

To close the Save File Dialog: Preferences File List dialog without saving the preference settings file or saving any changes to the preference settings file list, click Cancel.

Modifying Node Table Column SettingsTo specify the columns that SGM displays in node tables, right-click in the header of the node table in one of the following windows:

• Node Window

• Discovery panel of the Discovery Dialog

• Nodes Excluded from View table of the Network View Editor window

• Nodes In Current View table of the Network View Editor window

• Topology signaling point table in the left pane of the Topology Window

SGM displays the Node Table Preferences checkboxes:

• Select Internal ID to display the internal ID of the node. The default setting for this checkbox is cleared.

• Select Name to display the name of the node. The default setting for this checkbox is selected.


78-15589-01


• Select Primary SNMP Addr to display the IP address used by SNMP to poll the node. The default setting for this checkbox is selected in the Node Window, Discovery panel, and Network View Editor window. The default setting for this checkbox is cleared in the Topology Window.

• Select CLLI Code to display the CLLI code of the node. The default setting for this checkbox is cleared.

• Select Device Type to display the device type. The default setting for this checkbox is selected. The default setting for this checkbox is selected in the Node Window and Discovery panel. The default setting for this checkbox is cleared in the Network View Editor window and Topology Window.

• Select ITP MIB Level to display the MIB conformance level used by the ITP, such as ITP MB5. The default setting for this checkbox is selected.

• Select ITP Uptime to display the time the ITP has been up, in weeks, days, hours, minutes, and seconds. The default setting for this checkbox is cleared.

• Select Reboot Reason to display the reason for the last reboot of the ITP. The default setting for this checkbox is cleared.

• Select Notes to display the Notes column. The default setting for this checkbox is cleared.

• Select Events to display the Events column. The default setting for this checkbox is selected. The default setting for this checkbox is selected in the Node Window and Discovery panel. The default setting for this checkbox is cleared in the Network View Editor window and Topology Window.

• Select Last Status Change to display the date and time that the status of the node last changed. The default setting for this checkbox is cleared.

• You cannot edit the Status checkbox.

• Select Status Reason to display the reason for the current status of the node. The default setting for this checkbox is selected.



78-15589-01


Modifying Linkset Table Column SettingsTo specify the columns that SGM displays in linkset tables, right-click in the header of the linkset table in one of the following windows:

• Linkset Window

• Topology linkset table in the left pane of the Topology Window

SGM displays the Linkset Table Preferences checkboxes:

• Select Internal ID to display the internal ID of the linkset. The default setting for this checkbox is cleared.

• Select Name to display the name of the linkset. The default setting for this checkbox is cleared in the Linkset Window. The default setting for this checkbox is selected in the Topology Window.

• Select Local Point Code to display the point code of the primary node for the linkset. The default setting for this checkbox is cleared.

• Select Adj Point Code to display the point code of the adjacent node for the linkset. The default setting for this checkbox is cleared.

• Select Linkset Type to display the type of the linkset. The default setting for this checkbox is selected in the Linkset Window. The default setting for this checkbox is cleared in the Topology Window.

• Select Links to display the total number of links in the linkset. The default setting for this checkbox is selected in the Linkset Window. The default setting for this checkbox is cleared in the Topology Window.

• Select Active Links to display the number of links in the linkset that are Active. The default setting for this checkbox is selected in the Linkset Window. The default setting for this checkbox is cleared in the Topology Window.

• Select Congested Links to display the number of links in the linkset that are Congested. The default setting for this checkbox is selected in the Linkset Window. The default setting for this checkbox is cleared in the Topology Window.

• Select Ignored to display the Ignored column. The default setting for this checkbox is selected.

• Select Notes to display the Notes column. The default setting for this checkbox is cleared.


78-15589-01


• Select Events to display the Events column. The default setting for this checkbox is selected in the Linkset Window. The default setting for this checkbox is cleared in the Topology Window.

• Select Last Status Change to display the date and time that the status of the linkset last changed. The default setting for this checkbox is cleared.

• You cannot edit the Status checkbox.

• Select Status Reason to display the reason for the current status of the linkset. The default setting for this checkbox is selected.


Modifying Event Table Column SettingsTo specify the columns that SGM displays in event tables, right-click in the header of the event table in the Event Window. SGM displays the Event Table Preferences checkboxes:

• Select Internal ID to display the internal ID of the event. The default setting for this checkbox is cleared.

• Select Ack to display the acknowledged/unacknowledged setting for the event. The default setting for this checkbox is selected.

• Select Category to display the category of the event. The default setting for this checkbox is selected.

• Select Severity to display the severity of the event. The default setting for this checkbox is selected.

• Select Note to display the Notes column. The default setting for this checkbox is cleared.

• Select Time to display the date and time the event was logged. The default setting for this checkbox is selected.

• Select Ack By to display the SGM client that acknowledged the event. The default setting for this checkbox is selected.

• Select Ack Time to display the date and time the event was last acknowledged or unacknowledged. The default setting for this checkbox is cleared.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkModifying the Message Display

• Select Node to display the node associated with the event. The default setting for this checkbox is selected.

• Select SP to display the signaling point associated with the event. The default setting for this checkbox is selected.

• Select Linkset to display the linkset associated with the event. The default setting for this checkbox is selected.

• Select Link to display the link associated with the event. The default setting for this checkbox is selected.

• Select Message to display the event message. The default setting for this checkbox is selected.


Modifying the Message DisplayThe following sections provide information about modifying the way SGM displays and stores messages:

• Changing the Location of SGM Message Log Files, page 5-20

• Changing the Size of the SGM Message Log File, page 5-21

• Changing the Time Mode for Dates in Log Files, page 5-21

• Changing the Age of the SGM Message Log Files, page 5-21

Related Topics:

• Viewing Network Status and Statistics Information for SGM, page 7-5

• Viewing System Status Information for SGM, page 7-115

Changing the Location of SGM Message Log FilesBy default, all SGM system message log files are located on the SGM server at /opt/CSCOsgm/logs. To change the location of the system message log directory, use the sgm msglogdir command. See the “SGM Command Reference” section on page B-1 for more information on the use of this command.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkSetting the Point Code Format (Solaris Only)

Changing the Size of the SGM Message Log FileTo change the size of the message log file, use the sgm msglogsize command. See the “SGM Command Reference” section on page B-1 for more information on the use of this command.

Changing the Time Mode for Dates in Log FilesTo change the time mode for dates in log files, use the sgm logtimemode command. See the “SGM Command Reference” section on page B-1 for more information on the use of this command.

Changing the Age of the SGM Message Log FilesTo change the number of days SGM archives system message log files before deleting them from the SGM server, use the sgm msglogage command. See the “SGM Command Reference” section on page B-1 for more information on the use of this command.

Setting the Point Code Format (Solaris Only)SGM enables you to set a new point code format for an SGM server. The new point code format is used by the SGM server, and by all associated SGM clients. Normally, you need to do this only once, after installation.

The point code format configuration is contained in the PointCodeFormat.xml file.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkSetting the Point Code Format (Solaris Only)

To set the new point code format:




# ./sgm pcformat {edit | list | master | restore}

Where:

• edit—Opens the PointCodeFormat.xml file for editing.

• list—Displays the current contents of the PointCodeFormat.xml file.

• master—Restores the PointCodeFormat.xml file to the default settings.

• restore—Restores the PointCodeFormat.xml file to the last saved copy.

The PointCodeFormat.xml file provides the following default point code formats:

• <Variant value="ANSI" format="8.8.8"/>—Formats point codes using the 24-bit format American National Standards Institute (ANSI) standard, xxx.yyy.zzz format, where:

– xxx is the 8-bit network identification

– yyy is the 8-bit network cluster

– zzz is the 8-bit network cluster member

• <Variant value="China" format="8.8.8"/>—Formats point codes using the 24-bit format China standard, xxx.yyy.zzz format, where:

– xxx is the 8-bit network identification

– yyy is the 8-bit network cluster

– zzz is the 8-bit network cluster member


78-15589-01

Chapter 5 Configuring SGM for Your NetworkEnabling SNMP Traps (Solaris Only)

• <Variant value="ITU" format="3.8.3"/>—Formats point codes using the 14-bit format International Telecommunication Union (ITU) standards, x.yyy.z format, where:

– x is the 3-bit zone identification

– yyy is the 8-bit region identification

– z is the 3-bit signal-point

For information about customizing the point code formats, see the detailed instructions in the PointCodeFormat.xml file.

Any changes you make take effect when you restart the SGM server.

Enabling SNMP Traps (Solaris Only)By default, SGM cannot receive SNMP traps. To use SNMP traps with SGM, you must first configure SGM to receive traps.

Related Topics:

• Integrating SGM with Other Products, page 3-401


To view the current trap reception configuration for SGM, use the following procedure:




# ./sgm trapstatus


78-15589-01


SGM displays the current trap reception configuration for SGM, including:

• SNMP trap integration type:

– native—SGM receives traps natively on a UDP port.

– hpov—SGM receives traps using HP OpenView.

• For native, SGM also displays the UDP port number on which SGM receives traps natively.

• For hpov, SGM also displays the location of the HP OpenView home directory.

• Status for the sgmTrapReceiver (such as Running or Stopped).

To configure SGM to receive traps, using the following procedure:




# ./sgm trapsetup

SGM displays the following message and prompt:

The SGM server must also be stopped to perform this operation.

Do you wish to continue? [n]

Step 3 Type y and press Enter. SGM stops the SGM Process Manager and all managed processes and displays the following prompt:

Would you like to configure SGM to receive SNMP traps? [yes]


78-15589-01


Step 4 Press Enter. SGM displays the following message and prompt:

SGM can receive traps natively on a UDP port or receive traps via integration with HP OpenView.

Enter SNMP trap integration type: native or hpov? [native]

• If you want SGM to receive traps natively, press Enter. The SGM installation program displays the following messages and prompt:

SGM can receive traps natively on the standard UDP port number 162 or on any other UDP port chosen. If another application is already bound to the SNMP standard trap reception port of 162, an alternate port number for SGM must be specified.

UDP port number 44750 is the default alternate port.

Enter trap port number? [162]

By default, ITPs send traps to port 162. To accept the default value, press Enter.

If your ITPs have been configured to send traps to a different port, type that port number and press Enter.

By default, SGM listens for traps from trap multiplexing devices and NMS applications on port 44750. If you want SGM to monitor that port, and port 162 is not available on the SGM server device, type 44750 and press Enter.

If trap multiplexing devices and NMS applications in your network have been configured to send traps to a different port, type that port number and press Enter.

If you are a super user, you must specify a port number that is greater than 1024, then press Enter.

Do not enter a non-numeric port number. If you do, you are prompted to enter a numeric port number.

When you select an SNMP trap port number for the SGM server, make sure your ITPs use the same SNMP trap port number. See the description of the snmp-server host command in the “ITP Requirements” section of the Cisco Signaling Gateway Manager Installation Guide for more information.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkModifying the SGM Event Configuration File (Solaris Only)

• If you want SGM to receive traps using HP OpenView, type hpov and press Enter. The SGM installation program displays the following prompt:

Please enter location of HP OpenView home directory: [/opt/OV]

To accept the default value, press Enter; or type a different location and press Enter.

Step 5 SGM confirms your choices and restarts the SGM Process Manager and all managed processes.

SGM filters traps based on the contents of the SgmEvent.conf file. If a new trap becomes available that is of interest to SGM, you can modify the SgmEvent.conf file to enable SGM to recognize and process the new trap. For more information about modifying the SgmEvent.conf file, see the “Modifying the SGM Event Configuration File (Solaris Only)” section on page 5-26.

Modifying the SGM Event Configuration File (Solaris Only)

SGM processes events based on the contents of the SGM event configuration file, SgmEvent.conf. This file determines the size of the SGM event database, the maximum length of time SGM is to retain events, the default severity and color associated with each type of event, and all other aspects of SGM event processing.

If you want to change the way SGM processes events, you can modify the SgmEvent.conf file. After you save your changes and restart the SGM server, SGM reflects the changes on the SGM server and on all SGM clients that connect to that server, and reflects any new or changed categories and severities in its Web display navigation bars.


78-15589-01


When you modify the SgmEvent.conf file, keep the following considerations in mind:

• Changes you make to the SgmEvent.conf file can adversely affect your operating environment. In most environments, SGM recommends that you use the default file without modification.

• To view the current SgmEvent.conf file, enter the sgm eventconfig view command.

SGM creates a backup copy of the SgmEvent.conf file during installation. At any time, if you are unsatisfied with the changes you have made to the file, you can use the sgm restoreprops command to restore the backup copy of the SgmEvent.conf file.

To restore the SgmEvent.conf file from the previous version that was used, enter the sgm eventconfig restore command.

To restore the SgmEvent.conf file to the default SGM settings, enter the sgm eventconfig master command.


• After you save your modified SgmEvent.conf file, always validate it before restarting the SGM server. When you validate the file, you can detect errors before they negatively impact SGM. See the “Validating the Modified SGM Event Configuration File” section on page 5-38 for more information.

This section provides the following information:

• Editing the SGM Event Configuration File, page 5-28

• Modifying Basic Settings, page 5-28

• Modifying Event Categories, Severities, Colors, and Message Text, page 5-30

• Automating Events, page 5-33

• Setting Sounds for Events at the SGM Server, page 5-35

• Adding New Event Categories and Severities, page 5-35

• Modifying Help for Events, page 5-37

• Validating the Modified SGM Event Configuration File, page 5-38


78-15589-01


Editing the SGM Event Configuration FileTo edit the SgmEvent.conf file, use the following procedure:




# sgm eventconfig edit

Step 3 Modify the file as desired, then save the file.

Step 4 Validate the file. See the “Validating the Modified SGM Event Configuration File” section on page 5-38 for details.

The new configuration becomes effective when you restart the SGM server.

Modifying Basic SettingsSGM enables you to modify the following basic settings for the event database:

• Modifying the Size of the Event Database, page 5-28

• Modifying the Maximum Age for Events, page 5-29

• Modifying the Event Database Maintenance Interval, page 5-29

• Modifying the Event Automation Timeout Interval, page 5-30

• Enabling SGM to Process Events from Undiscovered Nodes, page 5-30

Modifying the Size of the Event Database

By default, the SGM event database can hold a maximum of 5000 events. If the database exceeds 5000 events, SGM deletes the oldest events until the database is reduced to 5000 events.


78-15589-01


To change the size of the SGM event database, modify the following line in the SgmEvent.conf file:

<MaxEventDbRecords value=”events” />

where events is the maximum number of events the database can hold.

Note The larger the event database, the greater the impact on the performance of the SGM server and clients.

Modifying the Maximum Age for Events

By default, the SGM event database retains events a maximum of 7 days. SGM deletes events that are older than 7 days.

To change the maximum age for events, modify the following line in the SgmEvent.conf file:

<MaxEventTimeToLive value=”days” />

where days is the maximum length of time, in days, SGM is to retain an event in the database.

Modifying the Event Database Maintenance Interval

By default, SGM performs maintenance on the event database every 60 minutes, deleting all events in excess of 5000 and all events older than 7 days.

To change the maintenance interval, modify the following line in the SgmEvent.conf file:

<CompressEventDbInterval value=”minutes” />

where minutes is the length of time, in minutes, between maintenance checks of the database.

Note The shorter the maintenance interval, the greater the impact on the performance of the SGM server and clients.


78-15589-01


Modifying the Event Automation Timeout Interval

By default, the SGM event database allows an event automation script to run for 300 seconds (5 minutes) before canceling the script and moving on.

To change the event automation timeout interval, modify the following line in the SgmEvent.conf file:

<AutomationTimeout value=”seconds” />

where seconds is the maximum length of time, in seconds, SGM is to allow an event automation script to run.

Enabling SGM to Process Events from Undiscovered Nodes

By default, SGM does not process events from undiscovered nodes.

To begin processing events from undiscovered nodes, change the following line in the SgmEvent.conf file:

<ProcessUndiscovered value=”False” />

to:

<ProcessUndiscovered value=”True” />

Modifying Event Categories, Severities, Colors, and Message Text

There are three main types of events in SGM:

• Trap events, which are incoming events that are not solicited by SGM.

• Status events, which are status changes detected by SGM.

• User Action events, which are events triggered by user actions.

Within those broad types, there are many subordinate types of events, each with a default associated category, severity, color, message text, and event help file. SGM enables you to modify the default characteristics of each type of event, tailoring them to meet your needs.


78-15589-01


This section provides the following information to help you modify event characteristics:

• Modifying Event Categories, page 5-31

• Modifying Event Severities and Colors, page 5-32

• Modifying Event Message Text, page 5-32

Modifying Event Categories

By default, SGM provides the following event categories:

• Create—Creation event, such as the creation of a seed file.

• Delete—Deletion event, such as the deletion of a node, signaling point, linkset, or file.

• Discover—Discovery event, such as Discovery beginning.

• Edit—Edit event. A user has edited an event, linkset, or node.

• Ignore—Ignore event. A user has Ignored a link or linkset.

• Login—Login event. A user has logged in to SGM.

• LoginDisable—LoginDisable event. SGM has disabled a user’s User-Based Access authentication as a result of too many failed attempts to log in to SGM.

• LoginFail—LoginFail event. An attempt by a user to log in to SGM has failed.

• OverWrite—OverWrite event. An existing file, such as a seed file or route file, has been overwritten.

• Poll—Poll event, such as an SNMP poll.

• Purge—Purge event. A user has requested Discovery with Delete Existing Data selected, and SGM has deleted the existing SGM database.

• Status—Status change message generated.

• Trap—SNMP trap message generated.

To change the name of an existing event category, find the category name in the SgmEvent.conf file and replace every occurrence with your new category name. For example, you could replace every occurrence of LoginFail with BadLogin.


78-15589-01


Modifying Event Severities and Colors

By default, SGM provides the following event severities and colors:

• Admin—The default color is cyan.

• Error—The default color is coral.

• None—The default color is white.

• Normal—The default color is light green.

• Warning—The default color is yellow.

To change the name of an existing event severity, find the severity name in the SgmEvent.conf file and replace every occurrence with your new severity name. For example, you could replace every occurrence of Error with Problem.

To change the color associated with an existing severity, find the line that defines the severity’s color in the SgmEvent.conf file and change the color. For example, to display Warning events in maroon instead of yellow, change the following line:

<SeverityName value=”Warning” /> <SeverityColor value="yellow" />

to:

<SeverityName value=”Warning” /> <SeverityColor value="maroon" />

You can assign any of the standard HTML/Web colors to SGM events. For a list of all supported HTML/Web colors, see the /opt/CSCOsgm/etc/SgmEvent.colors file.

Modifying Event Message Text

SGM provides default message text for each event defined in the SgmEvent.conf file.

To modify the message text for an event, find the line that defines the event’s message text in the SgmEvent.conf file and change the text. For example, the default message text for a Poll event is:

<Message value="Poll for $NodeDisplayName requested by user $User." />


78-15589-01


If you care more about the user than about the polled node, you could change that message text to:

<Message value="User $User requested a poll for $NodeDisplayName." />

Automating EventsSGM enables you to automate events. That is, you can configure SGM to call a UNIX script to drive automatic paging or e-mail, for example, whenever SGM logs an event for which you have defined an automation script.

To configure automation for an event, use the following procedure:

Step 1 Find the event in the SgmEvent.conf file.

Step 2 Find the event’s Help element, <HelpFile value="" />.

Step 3 Before the Help element, add an Action element. The Action element has the following format:

<Action Poll="[True|False]" Run="UNIXCommand EventParameters" />

where:

• Poll indicates whether SGM is to poll the associated nodes immediately (True) or not poll the nodes (False).

• Run spawns a UNIX process to execute the specified command or script.

• UnixCommand specifies either a binary command name or a shell script.

• EventParameters are information from the event that SGM sends to UnixCommand as parameters. The set of EventParameters is the same as the set of Message element parameters, and they are specified the same way.


78-15589-01


For example, the following Action element:

<Action Poll="True" Run="/users/sgrimes/auto-inhibit.exp $NodeDisplayName $LinksetName $User" />

causes the following automatic actions whenever SGM logs the associated event:

• SGM polls the associated nodes.

• SGM spawns a UNIX process to execute the /users/sgrimes/auto-inhibit.exp script.

• SGM passes the $NodeDisplayName, $LinksetName, and $User parameters to the script.

Step 4 When you are satisfied with the event automation changes you have made to the SgmEvent.conf file, validate your changes using the sgm testeventconfig command. See the “Validating the Modified SGM Event Configuration File” section on page 5-38 for more information.

Step 5 Restart the SGM server. Thereafter, the specified event causes the automation script to run.

When you are working with automated events, keep in mind the following considerations:

• Detailed information about event automation scripts, including the times they start and stop and any output produced by the scripts, is recorded in the SGM system event automation log file. For more information, see the “Viewing the SGM System Event Automation Log” section on page 7-112.

• SGM event automation scripts run separately from all other SGM processing.

• If SGM logs more than one automated event in rapid succession, SGM runs each automation script sequentially, not in parallel. SGM spawns a new UNIX process for each script, and waits for it to complete before running the next script.

• By default, SGM allows an event automation script to run for 300 seconds (5 minutes) before canceling the script and moving on to the next script. To change the maximum run-time for event automation scripts, see the “Modifying the Event Automation Timeout Interval” section on page 5-30.


78-15589-01


Setting Sounds for Events at the SGM ServerYou can configure the SGM server to play specific sounds when specific events are logged. (To configure sounds on the SGM client, see the “Setting Sounds for Events at an SGM Client” section on page 5-40.)

To configure event sounds on the SGM server, create a script to call the Solaris audioplay command, then configure automation for an event, with the script specified in place of the UnixCommand argument.

The audioplay command has the following basic format:

/usr/bin/audioplay soundfile

where soundfile is the full path and name of a sound file stored in the SGM server’s sounds directory:

• If you installed SGM in the default directory, /opt, then the sound file directory is /opt/CSCOsgm/sounds.

• If you installed SGM in a different directory, then the sound file directory is located in that directory.

See the audioplay command man page for more information about this command.

See the “Automating Events” section on page 5-33 for more information about configuring automation for an event.

To see the list of event automation sound files that are stored in the sounds directory, select Sounds from the Web page menu bar, if shown. SGM displays the SGM System Files: Server Event Automation Sounds page. The SGM server can play sound files with the formats that are supported by its audio system.

Adding New Event Categories and SeveritiesSGM also enables you to add entirely new categories and severities to the SgmEvent.conf file. This is useful if you want to group different events into logical groups for filtering.


78-15589-01


For example, you might want to create a new Trap category, LinkUtilization, that combines the cItpSpLinkRcvdUtilChange and cItpSpLinkSentUtilChange traps for easier filtering in the SGM GUI. To do so, find the following line in the SgmEvent.conf file:

<Categories>

and add the following line to the list of category definitions:

<CategoryName value="LinkUtilization" />

Now find each occurrence of the cItpSpLinkRcvdUtilChange and cItpSpLinkSentUtilChange trap, and change each category definition from Trap:

<CategoryName value="Trap" />

to LinkUtilization:

<CategoryName value="LinkUtilization" />

You can also change the severity, color, message text, or event help file generated by the cItpSpLinkRcvdUtilChange and cItpSpLinkSentUtilChange traps.

Now, after you save the SgmEvent.conf file, validate your changes, and restart the SGM server, whenever SGM processes a cItpSpLinkRcvdUtilChange or cItpSpLinkSentUtilChange trap, the SGM GUI and Web displays show the events with the new LinkUtilization category.

When processing events, SGM searches for the best match in the SgmEvent.conf file. For example, by default, NodeStateAdded has event definitions for the following NodeStates:

• Active—Generates a Normal event

• Unknown—Generates an Error event

• Unmanaged—Generates an Admin event

• Warning—Generates a Warning event

• <Blank>—Generates a None event


78-15589-01


If a node is added to the SGM database with a status of Unknown, SGM generates an Error event, as defined for NodeState value=”Unknown”.

However, if a node is added with a status of Waiting, SGM generates a None event, because that is the best match in the NodeStateAdded event definitions.

Modifying Help for EventsSGM provides extensive type-specific help for events. To see help for an event, right-click the event in the Event Window and select Help for Event. SGM displays context-sensitive help for the selected event in a separate Web browser.

However, you might prefer to provide your own enterprise-specific instructions to operators in the event help, and SGM enables you to do so.

To modify the help for an event, use the following procedure:

Step 1 Create a new HTML help file for the event.

You can use the default SGM event help file as a basis for your help file:

• If you installed SGM in the default directory, /opt, then the event help files are in the /opt/CSCOsgm/apache/share/htdocs/eventHelp directory.

• If you installed SGM in a different directory, then the event help directory and files are located in that directory.

If you use an SGM event help file as a basis for your event help file, rename it when you save it. Do not use the existing SGM name. If you do so, then the next time you install SGM, SGM overwrites the file and you lose your changes.

For example, the default SGM help file for cItpSpLinkRcvdUtilChange and cItpSpLinkSentUtilChange traps is cItpSpLinkRcvdUtilChange.html. If you use that file as the basis for your new help file, which covers all link utilization events, you might name your new file cMyLinkUtilChange.html.

Step 2 Store your new help file in the /opt/CSCOsgm/apache/share/htdocs/eventHelp directory.


78-15589-01


Step 3 In the SgmEvent.conf file, replace each occurrence of the SGM default event help file name with the name of your file. For example, given the preceding example, you would replace each occurrence of the following line:

<HelpFile value="/eventHelp/cItpSpLinkRcvdUtilChange.html" />

with this line:

<HelpFile value="/eventHelp/cMyLinkUtilChange.html" />

Step 4 Save the the SgmEvent.conf file.

Step 5 Validate the file. See the “Validating the Modified SGM Event Configuration File” section on page 5-38 for details.

Step 6 Restart the SGM server. Now, whenever you display help for a cItpSpLinkRcvdUtilChange or cItpSpLinkSentUtilChange trap event, SGM displays your custom event help.

Validating the Modified SGM Event Configuration FileAlways validate the SgmEvent.conf file after you save your changes and before you restart the SGM server. When you validate the file, you can detect errors before they negatively impact SGM.

To validate the SgmEvent.conf file, use the following procedure:




# ./sgm testeventconfig


78-15589-01


SGM parses the SgmEvent.conf file and generates a list of all found XML and non-XML errors:

• For XML errors, SGM points to the line that contains the error. The following is a sample XML error:

SgmEventConfig: Element "Parms" does not allow "SeverityNamex" here.SgmEventConfig: Unable to parse event configuration file.

• For non-XML errors, SGM points to the bottom of the Trap, Status, or User Action definition block that contains the error. The following is a sample XML error:

SgmEventConfig: Severity 'Normalx' is not contained in the valid severities list.SgmEventConfig: Unable to parse event configuration file.

If you prefer to dump the event configuration to STDOUT for visual validation, enter the following commands:


# ./sgm testeventconfig -print

Step 3 Correct the errors and continue to validate the file until SGM detects no further errors. SGM displays the following messages:

SgmEventConfig: Loaded xx categories, xx severities, and xx events definitions.Finished loading /opt/CSCOsgm/etc/SgmEvent.conf

Step 4 Restart the SGM server to begin processing events using the modified file.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkSetting Sounds for Events at an SGM Client

Setting Sounds for Events at an SGM ClientSGM enables you to create and modify event sound filters for the SGM client. Event sound filters determine the sounds that the SGM client plays when specific events are logged. The SGM client plays the sounds even if the Event Window is not currently displayed. (To configure sounds on the SGM server, see the “Setting Sounds for Events at the SGM Server” section on page 5-35.)

Related Topics:


To work with event sound filters:

Step 1 Select Edit > Event Sounds from the SGM Main Menu. SGM displays the Event Sound Filters List dialog (Figure 5-5).

Figure 5-4 Event Sound Filters List Dialog


78-15589-01


The Event Sound Filters List dialog lists all event sound filters that have been defined.

The Sound filters applied in order: list indicates the order in which sound filters are to be applied, from top to bottom. That is, if an event matches two or more filters in the list, the top-most filter determines the sound that the SGM client plays. (The Sound filters applied in order: list is blank until you have created at least one new sound filter for events.)

• To move an event sound filter up in the list, select the filter, then click Move Up.

• To move an event sound filter down in the list, select the filter, then click Move Down.

Step 2 (Optional) To create a new event sound filter, click New. SGM displays the Event Sound Filters dialog (Figure 5-5).


78-15589-01


Figure 5-5 Event Sound Filters Dialog

Enter a name for the filter, then specify filter criteria for this event sound filter:

• (Optional) To add a filter based on message text:

a.Select Message Text from the first drop-down list box.

b.Select Contains, Equals, Does Not Contain, or Does Not Equal from the second drop-down list box.

c.Enter the message text in the character string field.


78-15589-01


• (Optional) To add a filter based on event severity:

a.Select Severity from the first drop-down list box.

b.Select Equals or Does Not Equal from the second drop-down list box.

c.Select a severity, such as Normal or Error, from the third drop-down list box.the message text.

• (Optional) To add a filter based on event category:

a.Select Category from the first drop-down list box.


c.Select a category, such as Status or Purge, from the third drop-down list box.the message text.

• (Optional) To add a filter based on the name of the node associated with the event:

a.Select Node from the first drop-down list box.


c.Select a node from the third drop-down list box. SGM lists all nodes that have been discovered in the drop-down list box.

• (Optional) To add a filter criteria to the event sound filter, click More. SGM adds a new criteria to the bottom of the list.

• (Optional) To remove a filter criteria from the event sound filter, click Fewer. SGM deletes the last criteria in the list.

• (Optional) To specify the sound to be played when an event matches this event sound filter, select a sound file from the Play this sound: drop-down list box.

SGM client sound files are stored in the sounds directory:

– If you installed the SGM client for Solaris in the default directory, /opt, then the sound file directory is /opt/CSCOsgmClient/sounds.

– If you installed the SGM client for Windows in the default directory, /Program Files, then the sound file directory is C:\Program Files\SGMClient\sounds.

– If you installed the SGM client in a different directory, then the sound file directory is located in that directory.


78-15589-01


You can add sound files to the sounds directory. SGM can play the following sound file formats: AIFC, AIFF, AU, SND, and WAV.

If for some reason SGM cannot play a specified sound file, SGM plays a default beep. For example, SGM cannot play a sound file if one of the following conditions exists:

– The file has been moved or deleted from the sounds directory

– The sounds directory has been deleted or cannot be found

– Some other application is using all of the sound resources

– There is no sound card present

• (Optional) To play a sample of the sound selected in the Play this sound: drop-down list box, click Play.

• (Optional) To close the Event Sound Filters dialog at any time without applying any changes to the event sound filter criteria, click Cancel.

When you are satisfied with the changes you have made to the event sound filter criteria, click OK. SGM applies your changes and closes the Event Sound Filters dialog.

Step 3 (Optional) To modify an existing event sound filter, select the filter in the Sound filters applied in order: list, then click Edit. SGM displays the Event Sound Filters dialog (Figure 5-5), populated with the selected filter’s settings. Modify the settings as desired, then click OK. SGM applies your changes and closes the Event Sound Filters dialog.

Step 4 (Optional) To delete an event sound filter from the Sound filters applied in order: list, select the filter, then click Delete.

Step 5 (Optional) You can specify whether you want the SGM client to play event sounds:

• To play event sounds, clear the Mute Sounds checkbox. This is the default setting.

• To not play event sounds, select the Mute Sounds checkbox.

Step 6 (Optional) To apply any changes you made to the event sound filters list without closing the Event Sound Filters List dialog, click Apply.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkLimiting Traps by IP Address (Solaris Only)

Step 7 (Optional) To close the Event Sound Filters List dialog at any time without applying any changes to the event sound filters list, click Cancel.

Step 8 When you are satisfied with the changes you have made to the event sound filters list, click OK. SGM applies your changes and closes the Event Sound Filters List dialog.

On Solaris, the root user can access the sound feature from a local or remote device. However, users other than the root user must use a local device, and must use a local client, not a remote Solaris SGM client accessed using the xhost + UNIX command.

Limiting Traps by IP Address (Solaris Only)By default, when you first install SGM, all IP addresses are allowed to send traps to the SGM server. However, SGM enables you to limit the IP addresses that can send traps to the server by creating and maintaining the trapaccess.conf file.

You can create the trapaccess.conf file and populate it with a list of IP addresses that can send traps to the SGM server. SGM receives traps from only those IP addresses, plus the local host. If the file exists but is empty, SGM receives traps only from the local host. (SGM always receives traps from the local host.)

When you first install SGM, the trapaccess.conf file does not exist and SGM allows all IP addresses to send traps to the SGM server.

To create the trapaccess.conf file and work with the list of allowed IP addresses, use the following procedure:





78-15589-01

Chapter 5 Configuring SGM for Your NetworkLimiting Traps by IP Address (Solaris Only)

Step 3 Create the trapaccess.conf file:

• To create the trapaccess.conf file and add a client IP address to the list, enter the following command:

# ./sgm trapaccess add

• To create the trapaccess.conf file and open the file to edit it directly, enter the following command:

# ./sgm trapaccess edit

The default directory for the file is located in the SGM installation directory:

• If you installed SGM in the default directory, /opt, then the default directory is /opt/CSCOsgm/etc.


In the trapaccess.conf file, begin all comment lines with a pound sign (#).

All other lines in the file are SGM client IP addresses, with one address per line.

Wildcards (*) are allowed, as are ranges (for example, 1-100). For example, the address *.*.*.* allows all clients to send traps to the SGM server.

After you create the trapaccess.conf file, you can use the full set of sgm trapaccess keywords to work with the file. See the description of the sgm trapaccess command in the See the “SGM Command Reference” section on page B-1 for more details.

Any changes you make to the trapaccess.conf file take effect when you restart the SGM server.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkSetting the DISPLAY Variable (Solaris Only)

Setting the DISPLAY Variable (Solaris Only)The DISPLAY variable is set as part of your login environment on Solaris. However, if you Telnet into a remote workstation, you must set the DISPLAY variable to local display. To do so, enter the following command:

# setenv DISPLAY local_ws:0.0

where local_ws is your local workstation.

If your shell does not support the setenv command, enter the following command:

# export DISPLAY=local_ws:0.0

Backing Up or Restoring SGM Files (Solaris Only)SGM automatically backs up all SGM data files to the SGM installation directory at 11:59 PM each night.

To change the time at which SGM automatically backs up files, log in as the root user and modify the root crontab file.

To manually back up the SGM data files at any time, log in as the root user, as described in the “Becoming the Root User (Solaris Only)” section on page 3-2, and enter the following commands:


# ./sgm backup

SGM backs up the data files in the installation directory.

If you installed SGM in the default directory, /opt, then the default backup directory is also /opt. If you installed SGM in a different directory, then the default backup directory is that directory.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkRemoving SGM Data from the SGM Server

To change the directory in which SGM stores its nightly backup files, use the following procedure:




# ./sgm backupdir directory

where directory is the new backup directory. If the new directory does not exist, SGM does not change the directory, and issues an appropriate message.

To restore the SGM data files from the previous night’s backup, log in as the root user, as described in the “Becoming the Root User (Solaris Only)” section on page 3-2, and enter the following commands:


# ./sgm restore

SGM restores the data files.

Warning Do not interrupt this command. Doing so can corrupt your SGM data files.

Removing SGM Data from the SGM ServerThere might be times when you want to remove all SGM data from the SGM server, without uninstalling the product. There are two ways to do this, both of which restore the SGM server to a “clean” state, such as would exist after a new installation of SGM.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkRemoving SGM Data from the SGM Server

To remove all SGM data from the SGM server, excluding message log files, backup files, and report files, use the following procedure:




# ./sgm clean

Data removed includes all SGM data, notes, preferences, route files, and views, as well as any user-created files stored in SGM directories.

To remove all SGM data from the SGM server, including message log files, backup files, and report files, use the following procedure:




# ./sgm cleanall

Data removed includes all SGM data, notes, preferences, route files, views, message log files, backup files, and report files, as well as any user-created files stored in SGM directories.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkConfiguring a Backup SGM Server (Solaris Only)

Configuring a Backup SGM Server (Solaris Only)SGM enables you to configure a secondary SGM server as a backup for the primary SGM server. For best results, Cisco recommends that you configure the primary server and the secondary server as secondaries for each other.

To configure a secondary SGM server, use the following procedure:




# ./sgm secondaryserver hostname naming-port

where:

• hostname is the optional name of the host on which the secondary SGM server is installed.

• naming-port is the optional SGM Naming Server port number for the secondary SGM server. The default port number is 44742.

Note If you use the sgm secondaryserver command to configure a secondary SGM server, but the primary SGM server fails before you launch the SGM client, then the SGM client has no knowledge of the secondary server.

Step 3 (Optional) To list the secondary SGM server that has been configured for this primary SGM server, enter the following commands:


# ./sgm secondaryserver list


78-15589-01

Chapter 5 Configuring SGM for Your NetworkConfiguring an SGM Client Connection Timer

Configuring an SGM Client Connection TimerSGM enables you to specify how long an SGM client is to wait for the SGM server before exiting.

To configure an SGM client connection timer, use the following procedure:




# ./sgm cliconntimer number-of-seconds

where number-of-seconds is the time the SGM client is to wait for a message from the SGM server before exiting. The valid range is 10 seconds to an unlimited number of seconds. The default value is 60 seconds.

If the timer expires, the client pings the server and takes the following action:

• If the server responds to the ping, the client reconnects to the server.

• If the server does not respond to the ping, but there is a backup server configured, the client connects to the backup server.

• If the server does not respond to the ping, and there is no backup server configured, the client stops.

The timer takes effect when you restart the SGM server.

Step 3 (Optional) To restore the default timeout of 60 seconds, enter the following command:

# ./sgm cliconntimer clear

The timer is reset to 60 seconds when you restart the SGM server.


78-15589-01

Chapter 5 Configuring SGM for Your NetworkTelnetting to an ITP

Telnetting to an ITPSGM enables you to link to an ITP using Telnet.

To Telnet to an ITP, right-click a node in a window, then select ITP> Telnet to from the right-click menu.

Note If your client workstation does not have network access to the IP address of the ITP (that is, if the ITP is behind a firewall or NAT device), you might be unable to Telnet to the ITP.


78-15589-01

Cisco S78-15589-01

C H A P T E R 6
Troubleshooting SGM and the Network
This chapter provides the following information for troubleshooting basic SGM and network problems:

• Verifying Discovery, page 6-1

• Clearing a Locked-Up SGM Display, page 6-2

• Investigating Data Problems, page 6-2

• Viewing the SGM Troubleshooting Log, page 6-3

• Viewing SGM Data on the Web, page 6-4

• Diagnosing a Typical Network Problem, page 6-4

Verifying DiscoveryAfter you discover the network (see the “Discovering the Network” section on page 3-6), examine the Discovered Nodes table to verify that SGM discovered all of the ITP nodes in the network. If you suspect that SGM did not discover all of the ITP nodes, verify the following conditions:

• Verify that no nodes are excluded from your current view.

• Verify that the SGM server can ping the nodes.

• Verify that the nodes are running images that are compatible with the SGM server.


Chapter 6 Troubleshooting SGM and the NetworkClearing a Locked-Up SGM Display

• Verify that the SNMP is enabled on the nodes.

• Verify that SGM is configured with the correct SNMP community name. See the “Configuring SNMP” section on page 3-2 for details.

• Verify that the missing nodes are connected to the seed nodes by SCTP connections, not just serial connections. If they are not connected by SCTP connections, you must add the missing nodes to the seed file as seed nodes. See the “Configuring Seed Files” section on page 3-20 for more information.

• Verify that you selected Entire Network when you ran Discovery. If you suspect that you did not, run Discovery again with Entire Network selected.

Clearing a Locked-Up SGM DisplayIn SGM, events might cause message popups to remain in the background of your display, preventing you from interacting with other windows. If you suspect that your display has locked up, perform the following tasks:

• Make sure you are running SGM on a supporrted operating system. Refer to the “Solaris Software Requirements” and “Windows Software Requirements” sections of the Cisco Signaling Gateway Manager Installation Guide for more information about supported operating systems.

• Minimize windows and look for an SGM message popup in the background.

Investigating Data ProblemsIf you suspect that there are problems with the data that SGM is displaying, perform the following tasks:

• Enter equivalent show commands on the ITP. Is the data the same as that displayed by SGM?

• Send SNMP queries to the nodes. Do all queries complete?

The results of these tasks can help you distinguish between an ITP problem and an SGM problem.


78-15589-01

Chapter 6 Troubleshooting SGM and the NetworkViewing the SGM Troubleshooting Log

Viewing the SGM Troubleshooting LogSGM stores troubleshooting information in the /opt/CSCOsgm/tmp/cisco_sgm_tshoot.log file on the SGM server. This log, which is updated each time the SGM Server Troubleshooting page is accessed or the sgm tac command is run, contains information that might be requested by Cisco customer support personnel.

If you want to view the SGM troubleshooting log, Cisco strongly recommends that you do so in a Web browser. To view the log in a Web browser, select System Troubleshooting from the SGM Server Home Page.

You can also view the log from the command line, but this method displays the entire log, which can contain thousands of lines of output, line-by-line on your workstation screen. Therefore, Cisco strongly recommends that you view the log from the Web, as indicated above, or redirect the output from this command to a separate file, using the redirection symbol (>).

To view the log from the command line:




# ./sgm tac

This command might take a minute or more to complete. When it completes, SGM displays the following message and prompt:

Output is in /opt/CSCOsgm/tmp/cisco_sgm_tshoot.log

Would you like to view it? [y]

Step 3 Press Enter. SGM displays the contents of the /opt/CSCOsgm/tmp/cisco_sgm_tshoot.log file.


78-15589-01

Chapter 6 Troubleshooting SGM and the NetworkViewing SGM Data on the Web

Viewing SGM Data on the WebSGM provides an enormous amount of Web-based troubleshooting information. From the SGM Server Home Page, you can access many Web pages containing SGM data, including server status, network status, installation logs, message logs, product documentation, and other important troubleshooting information about SGM. For full details, see the “Accessing SGM Data from a Web Browser” section on page 7-1.

Viewing Detailed Troubleshooting Instructions for Events

SGM provides extensive type-specific help and troubleshooting instructions for events. To see help and troubleshooting instructions for an event, right-click the event in the Event Window and select Help for Event.

You can also provide your own enterprise-specific instructions to operators in the event help. For more information, see the “Modifying Help for Events” section on page 5-37.

Diagnosing a Typical Network ProblemWhen you use SGM to diagnose a problem in an ITP network, follow these basic steps:

1. Monitor the network using the Link, Linkset, Signaling Point, Node, and Topology windows. For example, an object in the topology map that changes color from green to yellow or red indicates a problem in the network.

2. Use SGM windows, especially the Details window, to begin investigating the problem.

3. As you identify the source of the problem, examine the messages logged by SGM for more detailed information about the sequence of events that led to the problem.

4. Telnet to the problematic ITP, if necessary.


78-15589-01

Chapter 6 Troubleshooting SGM and the NetworkDiagnosing a Typical Network Problem

The following real-life example provides detailed information about using SGM to diagnose a problem in an ITP network:

Step 1 A network operator (we’ll call him Joe) is using SGM to monitor an ITP network. Joe has customized his view, limiting it to only those nodes for which he is responsible.

(For more information about customizing views, see the “Working with Views” section on page 3-26.)

Step 2 In the topology map, Joe notices a signaling point that has changed color from green to yellow. Yellow indicates a status of Warning, which means that one or more links or linksets associated with that signaling point is in Unknown or Warning status and is not flagged as Ignored.

(For more information about signaling point status, see the “Working with Signaling Points” section on page 3-136.)

Step 3 Joe single-clicks the signaling point in the topology map.

SGM highlights the signaling point in the topology map, and in the topology signaling point table, in the left pane of the Topology window. With the signaling point highlighted, Joe can easily see that the name of the signaling point is sgm-7500j.

SGM also displays all associated linksets in the topology linkset table.

Joe double-clicks the signaling point’s name in the topology signaling point table.

SGM redraws the topology map, centered on sgm-7500j, making it easier for Joe to see the relevant portion of the map.

(For more information about the Topology window and how to use it, see the “Viewing the Topology of the Network” section on page 3-259.)

Step 4 Joe notices that one of sgm-7500j’s diamonds is red, indicating that the associated linkset is either Unavailable or Unknown. Joe single-clicks the red diamond.

SGM highlights the linkset in the topology map and in the topology linkset table. The table entry indicates that the linkset is Unavailable.

(For more information about linkset status, see the “Viewing Basic Information for Linksets” section on page 3-38.)


78-15589-01


Step 5 Joe right-clicks the linkset in the topology map and selects View > Configuration Details in the right-click menu.

SGM opens the Details window, showing detailed information for the linkset.

In the Details window, detailed information for the selected linkset is displayed in the left column and for the adjacent linkset in the right column

Immediately, Joe sees that the left column is populated with SGM data, but the right column is not. The problem is in the adjacent signaling point-to-primary signaling point linkset.

(For more information about linkset details, see the “Viewing Detailed Information for a Linkset” section on page 3-42.)

Step 6 The turner beside Linkset in the left pane displays the list of links associated with the linkset, identified by their signaling link code IDs (SLCs). In this case, there is only one link listed, SLC 0, and it is red, meaning it is Failed and there is no traffic flowing on the link.

Joe selects SLC 0, and SGM displays detailed information for the link in the left column. Normally SGM also displays detailed information for links associated with the adjacent linkset in the right column, but in this case, that column is blank.

(For more information about linkset status, see the “Viewing Detailed Information for a Link” section on page 3-175.)

Step 7 Joe decides to investigate the adjacent signaling point, so he double-clicks the adjacent signaling point in the topology map.

The resulting display shows that the adjacent signaling point, sgm-2600a, is Unmanaged.

(For more information about signaling point details, see the “Viewing Detailed Information for a Signaling Point” section on page 3-141.)

Step 8 Joe closes the Details window and returns to the Topology window. He tries to find sgm-2600a in the topology map, but the map is too complex. So Joe lets SGM find the node for him:

a. He selects Edit > Find in the SGM Main Menu. SGM displays the Find dialog.

b. He enters sgm-2600a in the Search string field, selects the Signaling Points checkbox, and makes sure the Name, checkbox is selected.


78-15589-01


c. He clicks OK to launch the search. Almost immediately, SGM finds the node and displays the Choose dialog, listing all found objects.

d. Joe selects sgm-2600a, and SGM automatically highlights sgm-2600a in the topology signaling point table and in the topology map, and redraws the map centered on sgm-2600a.

(For more information about finding objects in the topology map, see the “Viewing the Topology of the Network” section on page 3-259.)

Step 9 Joe wants to see recent events for sgm-2600a, so he clicks the node in the topology map and selects View > Events in the SGM Main Menu. SGM displays the Event Window, showing recent events for sgm-2600a.

(For more information about viewing events, see the “Working with Events” section on page 3-235.)

Step 10 Joe decides to see if SGM can manage the signaling point. He right-clicks sgm-2600a in the topology map and selects Manage in the right-click menu.

SGM changes the status of the signaling point from Unmanaged (red) to Warning (yellow), which means the signaling point is active, but one or more associated linksets or links has a status of Failed, Unavailable, Unknown, or Warning and is not flagged as Ignored.

(For more informations, see the “Unmanaging and Managing a Signaling Point” section on page 3-169.)

Step 11 Joe wants to see status change messages for sgm-2600a, so he right-clicks the signaling point again and selects Event History > Status Change Messages in the right-click menu. SGM displays recent status change messages for the signaling point in a Web browser.

Joe sees that many of the links and linksets associated with sgm-2600a have a status of Unknown.

(For more information about displaying messages on the Web, see the “Accessing SGM Data from a Web Browser” section on page 7-1.)


78-15589-01


Step 12 At this point, Joe needs to determine why so many of the links and linksets are Unknown. He needs to verify that the SGM server can ping the node (see the “Telnetting to an ITP” section on page 5-52), and that SGM is configured with the correct SNMP community name for the node (see the “Configuring SNMP” section on page 3-2).

(For a list of some other actions Joe can take, see the “Verifying Discovery” section on page 6-1.)

Step 13 Finally, Joe can use another product, such as CiscoView, to further investigate the problem.

(For more information about integrating SGM with CiscoView and other products, see the “Integrating SGM with Other Products” section on page 3-401.)


78-15589-01

Cisco S78-15589-01

C H A P T E R 7
Accessing SGM Data from a Web Browser
This chapter provides information about accessing SGM data from the SGM server home page, using a Web browser.

This chapter includes the following sections:

• Accessing SGM Data from the SGM Server Home Page, page 7-2

• Modifying SGM Web Output (Solaris Only), page 7-4


• Viewing SGM System Messages, page 7-99

• Viewing System Status Information for SGM, page 7-115

• Viewing System Data Files for SGM, page 7-120

• Viewing System Information for SGM, page 7-121

• Viewing the SGM Technical Documentation, page 7-122

• Downloading the SGM Client from the Web, page 7-123

• Downloading the SGM Server’s SSL Certificate from the Web, page 7-123

• Accessing Software Updates and Additional Information, page 7-124

• Displaying the ITP Home Page, page 7-124


Chapter 7 Accessing SGM Data from a Web BrowserAccessing SGM Data from the SGM Server Home Page

Accessing SGM Data from the SGM Server Home Page

From the SGM Server Home Page, you can access many Web pages containing SGM data, including server status, network status, installation logs, message logs, product documentation, Cisco.com, and other information about SGM. You can also download the SGM clients.

To access the SGM Server Home page, use one of the following procedures:

• Select Server > Homepage from the SGM Main Menu.

• Enter the following URL in a Web browser:

http://server_name:1774

Where server_name is the name or IP address of the server on which the SGM server is running and 1774 is the Web port being using by SGM. (1774 is the default port number.) If you do not know the name or Web port of the SGM Web Server, contact the system administrator who installed the SGM server software.

• Select Home from the menu bar of any of the SGM Web pages.

The SGM Server Home Page (Figure 7-1) is displayed.


78-15589-01

Chapter 7 Accessing SGM Data from a Web BrowserAccessing SGM Data from the SGM Server Home Page

Figure 7-1 SGM Server Home Page

The rest of this chapter provides detailed information about the SGM information you can access from the SGM Server Home Page.


78-15589-01

Chapter 7 Accessing SGM Data from a Web BrowserModifying SGM Web Output (Solaris Only)

Modifying SGM Web Output (Solaris Only)SGM enables you to modify the following aspects of its Web output:

• To control how often, in seconds, SGM updates certain Web output, use the sgm weblogupdate command. The valid range is 1 second to an unlimited number of seconds. The default value is 300 seconds (5 minutes).

• To set the maximum number of rows for SGM ASCII Web output, such as displays of detailed debugging information, use the sgm maxasciirows command. The valid range is 1 row to an unlimited number of rows. The default value is 6000 rows.

• To set the maximum number of rows for SGM HTML Web output, such as displays of statistics reports, status change messages, or SNMP trap messages, use the sgm maxhtmlrows command. The valid range is 1 row to an unlimited number of rows. The default value is 500 rows.

• To specify whether SGM is to show real signaling point names or display names in Web pages, enter the sgm webnames command:

– To show the real DNS names of signaling points, as discovered by SGM, enter sgm webnames real. This is the default setting.

– To show display names, enter sgm webnames display. Display names are new names that you specify for signaling points. For more information about display names, see the “Editing a Node” section on page 3-124.

• To specify whether SGM is to display send and receive utilization for linksets and links as percentages or in Erlangs in Web pages, enter the sgm webutil command:

– To display utilization as a percentage, enter sgm webutil percent. This is the default setting.

– To show display utilization in Erlangs, enter sgm webutil erlangs.

See the “Working with SGM Statistics Reports” section on page 3-334 for more information on send and receive utilization for linksets and links.

Each of these commands requires you to be logged in as the root user, as described in the “Becoming the Root User (Solaris Only)” section on page 3-2, or as a super user, as described in the “Specifying a Super User (Solaris Only)” section on page 4-22.


78-15589-01

Chapter 7 Accessing SGM Data from a Web BrowserViewing Network Status and Statistics Information for SGM

Viewing Network Status and Statistics Information for SGM

You can view the following SGM network status and statistics information from the SGM Server Home Page:

• Viewing Information About Nodes, page 7-5

• Viewing Information About Signaling Points, page 7-22

• Viewing Information About Linksets, page 7-34

• Viewing Information About Links, page 7-50

• Viewing Information About Application Servers, page 7-69

• Viewing Information About Signaling Gateway Mated Pairs, page 7-82

• Viewing Status Change and SNMP Trap Messages, page 7-86

• Viewing Network Status Metrics, page 7-97

• Viewing Network Statistics Reports for Links and Linksets, page 7-97

• Viewing Accounting Statistics Reports, page 7-98

• Viewing Point Code Inventory Reports, page 7-98

• Viewing Statistics Report Logs, page 7-99

Viewing Information About NodesSGM enables you to view the following information about nodes:

• Viewing the Network Status Node Dashboard, page 7-6

• Viewing ITP Node Status, page 7-6

• Viewing ITP Node Details, page 7-10

• Viewing ITP Node IOS Versions, page 7-16

• Viewing ITP Node Information: CPU Processes, page 7-17

• Viewing ITP Node Information: Syslog Messages, page 7-19

• Viewing ITP Node Information: Trap Host Configuration, page 7-20


78-15589-01


Viewing the Network Status Node Dashboard

The SGM: Node Dashboard page lists all discovered nodes, and provides links to messages and metrics for each node.

To access the SGM: Node Dashboard page, select Network Status Dashboard from the SGM Server Home Page, then click Node Dashboard.

To see status change messages and SNMP trap messages associated with a given node, click Messages.

To see network status metrics associated with a given node, click Metrics.

To see detailed information about all CPU processes associated with a given node, click ITP CPU Process.

To see all messages in the ITP system log associated with a given node, click Syslog.

To see all trap settings for a given node, as well as all hosts and port numbers to which the node sends traps, click Trap Host Configuration. If you have implemented SGM User-Based Access, this option is available to users with authentication level System Administrator (Level 5) and higher.

You can sort the table based on the information in the Nodes column. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

Viewing ITP Node Status

The SGM: ITP Node Status page displays information about all discovered nodes, including their names, events, status, and other important information.

To access the SGM: ITP Node Status page, select ITP Node Status from the SGM Server Home Page. SGM displays the SGM: ITP Node Status page (Figure 7-2).


78-15589-01


Figure 7-2 SGM: ITP Node Status Page

You can sort the SGM: ITP Node Status table based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

The SGM: ITP Node Status page displays the following information for each node:

• Server Name (in header)—Name of the SGM server associated with the node.

• Update Interval (in header)—Time between automatic updates for the page.


• Node Name—DNS name of the node, as discovered by SGM, or the new name that you specified for the node. For more information, see the “Editing a Node” section on page 3-124. To see detailed information for the node, click the node name.


78-15589-01


• Status—Current status of the node, with a color-coded background. Possible values are:

– Active (green)—The node is currently fully functional.

– Discovering (gray)—The node is being discovered, and SNMP queries have been sent to the device.

– Polling (gray)—The node is being polled.

– Unknown (red)—The node failed to respond to an SNMP request. SGM sets all associated nodes, linksets, and links to Unknown.

– Unmanaged (gray)—One of the following situations exists:





– Waiting (gray)—The node is in the Discovery queue but is not currently being discovered.

– Warning (yellow)—The active, but one or more associated nodes, linksets, or links is in Failed, Unavailable, Unknown, or Warning status and is not flagged as Ignored.


– None

– SGM Restart


– Unconfigured


78-15589-01


– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive







78-15589-01




















Viewing ITP Node Details

The SGM: Node Details page displays detailed information about each discovered node, including its CLLI code, point code, status, and other information.

To access the SGM: Node Details page, click a node name in a Web page. SGM displays the SGM: Node Details page (Figure 7-3).


78-15589-01


Figure 7-3 SGM: Node Details Page

The SGM: Node Details page displays the following information for the selected node:

• Node Name (in header)—DNS name of the node, as discovered by SGM.




• IP Address or DNS Hostname—DNS name of the node, as discovered by SGM.

• Messages—Opens the Network Status: Last X Status Change and Trap Messages Web page for the node.

• Metrics—Opens the Network Status Messages: Messages Web page for the node.


78-15589-01


• Syslog—(ITP nodes only) Opens the SGM: ITP Syslog Web page for the node.

• ITP CPU Process—(ITP nodes only) Opens the SGM: CPU Processes Web page for the node.

• Trap Host Configuration—(ITP nodes only) Opens the SGM: Trap Host Configuration Web page for the node. If you have implemented SGM User-Based Access, this option is available to users with authentication level System Administrator (Level 5) and higher.


Active—The node is currently fully functional.

Discovering—The node is being discovered, and SNMP queries have been sent to the device.

Polling (gray ball)—The node is being polled.

Unknown—The node failed to respond to an SNMP request. SGM sets all associated signaling points, linksets, and links to Unknown.

Unmanaged—One of the following situations exists:





Waiting—The node is in the Discovery queue but is not currently being discovered.

Warning—The node is active, but one or more associated signaling points, linksets, or links is in Failed, Unavailable, Unknown, or Warning status and is not flagged as Ignored.


78-15589-01


• Last State Change—Date and time that the status of the link last changed.


– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive



If the status reason is Unsupported Configuration, correct the configuration and enter the sgm cleandiscover command to delete all current network data and begin a clean discovery of the ITP network. If the status reason is still Unsupported Configuration, enter the sgm clean command to restore the


78-15589-01


SGM server to a “clean” state, such as would exist after a new installation of SGM. For more information on the use of these commands, see the “SGM Commands and Descriptions” section on page B-2.



• Display Name—New name that you specified for the node. If the node has no display name, this field is blank. For more information, see the “Editing a Node” section on page 3-124.

• First Discovered—Date and time that the node was first discovered by SGM.



















78-15589-01


• MIB Level—MIB conformance level used by the ITP, such as ITP MB5.

Note ITP Version String and MIB Level might not have a one-to-one correspondence, because multiple ITP versions can use the same MIB level if there are no changes to the MIBs between versions. For example, ITP versions 12.2(4)MB5 and 12.2(4)MB6 both use MIB level ITP MB5.

• ITP Uptime—Time the node has been up, in weeks, days, hours, minutes, and seconds.

• Reboot Reason—Reason for the last reboot of the node.

• ITP Version String—Version of IOS that is installed on the ITP.


• Last Polled Address—Last IP address that was polled for this node.

• IP Address List—List of all IP addresses associated with this node, including the primary SNMP address and all backup IP addresses.


• Avg. SGM Poll Response (secs)—Average time, in seconds, taken by this node to respond to SGM poll requests. For a non-ITP node, this field is left blank.

• Last SGM Poll Response (secs)—Time, in seconds, taken by this node to respond to the last SGM poll request. For a non-ITP node, this field is left blank.

• Last Full ITP Poll—Date and time of the last full poll of the node for ITP-related MIBs (as opposed to a demand poll for just one linkset’s worth of data). For a non-ITP node, this field is left blank.

• Note Timestamp—Date and time the note associated with this node was last updated. If there is no note associated with this node, this field is blank.

• Note—Note associated with this node. If there is no note associated with this node, this field is blank.


78-15589-01


• Internal ID—Internal ID of the node. The internal ID is a unique ID for every event, link, linkset, signaling point, and node, assigned by SGM for its own internal use. It can also be useful when the Cisco TAC is debugging problems.

• Signaling Points—Name and status of all signaling points associated with this node. To see detailed information for a signaling point, click the signaling point name.

Viewing ITP Node IOS Versions

The SGM: ITP Node IOS Versions page displays the version of IOS installed on each ITP node.

To access the SGM: ITP Node IOS Versions page, use one of the following procedures:

• Select View> Report> ITP Node IOS Versions from the SGM Main Menu.

• Select ITP Node IOS Versions from the SGM Server Home Page.

You can sort the SGM: ITP Node IOS Versions table based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

The SGM: ITP Node IOS Versions page displays the following information for each ITP node:


• Update Interval (in header)—Time between automatic updates for the page. None means the page is not automatically updated.


• Node—DNS name of the node, as discovered by SGM, or the new name that you specified for the node. For more information, see the “Editing a Node” section on page 3-124.

• IOS Version—Version of IOS installed on the node.


78-15589-01


• Recognized MIB Level—MIB conformance level used by the ITP, such as ITP MB5.

Note IOS Version and Recognized MIB Level might not have a one-to-one correspondence, because multiple ITP versions can use the same MIB level if there are no changes to the MIBs between versions. For example, ITP versions 12.2(4)MB5 and 12.2(4)MB6 both use MIB level ITP MB5.
















Viewing ITP Node Information: CPU Processes

The SGM: CPU Processes page displays detailed information about all CPU processes associated with the selected node.

To access the SGM: CPU Processes page, right-click a node in a window, then select Drill Down > Show ITP CPU Processes from the right-click menu. (This option is not available if the node is in Unknown or Unmanaged status.)


78-15589-01


The SGM: CPU Processes page displays the following information for the selected node:

• Node Name (in header)—Name of the node for which CPU processes are being displayed.




• Node—Name of the node for which CPU processes are being displayed. To see detailed information for the node, click the node name.

• CPU—Number of the CPU for which processes are being displayed.

• PID—Process identifier.

• Name—Name of the process.

• Time Created—Total time since the process was created.

• Total Runtime—CPU time the process has used.

• Times Invoked—Number of times the process has been invoked.

• Average Runtime—Average CPU time for each process invocation.

• 5 Sec %—Average CPU utilization percentage for the node over the last 5 seconds.

• 1 Min %—Average CPU utilization percentage for the node over the last minute.

• 5 Min %—Average CPU utilization percentage for the node over the last 5 minutes.

• Priority—Process queue priority. Possible values are:

– Low

– Normal

– High

– Critical


78-15589-01


Viewing ITP Node Information: Syslog Messages

From the SGM: ITP Syslog page, you can view all messages in the ITP system log for the selected node.

To access the SGM: ITP Syslog page, select Syslog in the SGM: Node Details page. (This option is not available if the node is in Unknown or Unmanaged status.) SGM displays the SGM: ITP Syslog page, populated with the most recent syslog messages for the selected node.

The SGM: ITP Syslog table displays the following information for the selected node:

• Node Name (in header)—Name of the node for which syslog messages are being displayed.




• Node—Name of the node for which syslog messages are being displayed. To see detailed information for the node, click the node name.

• Timestamp—Time since ITP reboot of the syslog message.

• Severity—Severity of the syslog message. Possible values are:

– Alert—Messages that require immediate action.

– Critical—Critical conditions.

– Debug—Debug messages, log FTP commands, and WWW URLs.

– Emergency—System unusable messages.

– Error—Error messages.

– Info—Information messages.

– Notice—Normal but significant conditions.

– Warning—Warning messages.

• Facility—Name of the facility that generated the syslog message, such as SYS, SNMP, CS7MTP3, or CS7PING.


78-15589-01


• Name—Short text identifier for the message type. A facility name in conjunction with a message name uniquely identifies a syslog message type.

• Message—Text of the syslog message.

Viewing ITP Node Information: Trap Host Configuration

The SGM: CPU Processes page displays detailed information about all trap settings associated with the selected node.

If you have implemented SGM User-Based Access, this option is available to users with authentication level System Administrator (Level 5) and higher.

To access the SGM: Trap Host Configuration page, select Trap Host Configuration in the SGM: Node Details page. (This option is not available if the node is in Unknown or Unmanaged status.) SGM displays the SGM: ITP Syslog page, populated with the most recent syslog messages for the selected node.

The SGM: Trap Host Configuration page displays the following information for the selected node:

• Node Name (in header)—Name of the node for which trap settings are being displayed.




• Node—Name of the node for which trap settings are being displayed. To see detailed information for the node, click the node name.


– SCTP Remote Address Change







78-15589-01


– Route State Change


• Release 3 Trap Settings—Indicates whether the following ITP release 12.2(4)MB5 through 12.2(4)MB9a trap settings are enabled:

– ASP State Change

– AS State Change

– SGMP State Change

This column might not be displayed if the ITP does not support ITP release 12.2(4)MB5 through 12.2(4)MB9a traps.







– Route Destination State Change

– Route Mgmt. State Change

– Route Table Load


– GTT Table Load

– ASP Congestion Change

– SGMP Congestion Change

This column might not be displayed if the ITP does not support ITP release 12.2(4)MB10 traps.

• IP Address—IP address of a host to which the node sends traps.

• Port—Port to which the node sends traps.


78-15589-01


• Trap Version—Trap version sent to this IP address and port.

• Community String—SNMP community name used by the node for read access to the information maintained by the SNMP agent on the ITP.

Viewing Information About Signaling PointsSGM enables you to view the following information about signaling points:

• Viewing the Network Status Signaling Point Dashboard, page 7-22

• Viewing ITP Signaling Point Status, page 7-23

• Viewing ITP Signaling Point Details, page 7-26

• Viewing ITP Signaling Point Information: Access Lists, page 7-29

• Viewing ITP Signaling Point Information: GTT MAP Status, page 7-30

• Viewing ITP Signaling Point Information: MTP3 Event Log Messages, page 7-31

• Viewing ITP Signaling Point Information: Route Detail, page 7-32

Viewing the Network Status Signaling Point Dashboard

The SGM: Signaling Point Dashboard page lists all discovered signaling points, and provides links to messages and metrics for each signaling point.

To access the SGM: Signaling Point Dashboard page, select Network Status Dashboard from the SGM Server Home Page, then click Signaling Point Dashboard.

To see status change messages and SNMP trap messages associated with a given signaling point, click Messages.

To see network status metrics associated with a given signaling point, click Metrics.

To see all access lists associated with a given signaling point, click Access Lists.

To see detailed information about routes associated with a given signaling point, click Route Detail.

To see detailed information about all GTT MAPs associated with a given signaling point, click GTT MAP Status.


78-15589-01


To see detailed information about all MTP events associated with a given signaling point, click MTP Event Log.

You can sort the table based on the information in the Signaling Points column. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

Viewing ITP Signaling Point Status

The SGM: ITP Signaling Point Status page displays information about all discovered signaling points, including their names, status, and other important information.

To access the SGM: ITP Signaling Point Status page, select ITP Signaling Point Status from the SGM Server Home Page.

The SGM: ITP Signaling Point Status page displays the following information for each signaling point:

• Server Name (in header)—Name of the SGM server associated with the signaling point.



• Node—DNS name of the node associated with the signaling point, as discovered by SGM, or the new name that you specified for the node. For more information, see the “Editing a Node” section on page 3-124. To see detailed information for the node, click the node name.

• SP Name—Name of the signaling point, as discovered by SGM, or the new name that you specified for the signaling point. For more information, see the “Editing a Signaling Point” section on page 3-162. To see detailed information for the signaling point, click the signaling point name.


78-15589-01










– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested


78-15589-01






– Link Inactive







• Secondary Point Code—Secondary point code of the signaling point. If the signaling point has no secondary point code, this field is blank.

• Capability Point Code—Capability point code of the signaling point. A capability, or alias, point code is one that is shared by more than one signaling point, each of which is also assigned a “real” point code. If the signaling point has no capability point code, this field is blank.


78-15589-01


Viewing ITP Signaling Point Details

The SGM: Signaling Point Details page displays detailed information about each discovered signaling point, including its point code, status, and other information.

To access the SGM: Signaling Point Details page, click a signaling point name in the SGM: ITP Node Status, SGM: ITP Linkset Status, or SGM: ITP Node IOS Versions page.

The SGM: Signaling Point Details page displays the following information for the selected signaling point:

• Signaling Point Name (in header)—Name of the signaling point, as discovered by SGM, or the new name that you specified for the signaling point. For more information, see the “Editing a Signaling Point” section on page 3-162.




• Name—Name of the signaling point, as discovered by SGM, or the new name that you specified for the signaling point. For more information, see the “Editing a Signaling Point” section on page 3-162.

• Messages—Opens the Network Status: Last X Status Change and Trap Messages Web page for the signaling point.

• Metrics—Opens the Network Status Messages: Messages Web page for the signaling point.

• Access Lists—(ITP signaling points only) Opens the SGM: ITP Access Lists Web page for the signaling point.

• Route Detail—(ITP signaling points only) Opens the SGM: Route Detail Web page for the signaling point.

• GTT MAP Status—(ITP signaling points only) Opens the SGM: GTT MAP Status Web page for the signaling point.

• MTP3 Event Log—(ITP signaling points only) Opens the SGM: MTP3 Event Log Web page for the signaling point.


78-15589-01











– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception




78-15589-01


– Link Congested





– Link Inactive







• Node Name—Name of the node associated with this signaling point. To see detailed information for the node, click the node name.

• Description—Description of the signaling point. If the signaling point has no description, this field is blank.


• Secondary Point Code—Secondary point code of the signaling point. If the signaling point has no secondary point code, this field is blank.

• Capability Point Code—Capability point code of the signaling point. A capability, or alias, point code is one that is shared by more than one signaling point, each of which is also assigned a “real” point code. If the signaling point has no capability point code, this field is blank.


78-15589-01


• Note Timestamp—Date and time the note associated with this signaling point was last updated. If there is no note associated with this signaling point, this field is blank.

• Note—Note associated with this signaling point. If there is no note associated with this signaling point, this field is blank.

• Internal ID—Internal ID of the signaling point. The internal ID is a unique ID for every event, link, linkset, signaling point, and node, assigned by SGM for its own internal use. It can also be useful when the Cisco TAC is debugging problems.

• QoS—Quality of service (QoS) class of the signaling point, mapped to the type of service (ToS) or IP differentiated-services-code-point (DSCP).

• Linksets—Name and status of all linksets associated with this signaling point. To see detailed information for a linkset, click the linkset name.

Viewing ITP Signaling Point Information: Access Lists

The SGM: ITP Access Lists page displays all access lists associated with the selected signaling point.

To access the SGM: ITP Access Lists page for a signaling point, select Access List in the SGM: Signaling Point Details page. (This option is not available if the associated signaling point is in Unknown or Unmanaged status.)

The SGM: ITP Access Lists page displays the following information for the selected signaling point:

• Node Name, Signaling Point Name, and Linkset Name (in header)—Name of the signaling point, signaling point, and linkset for which access lists are being displayed.




• Node/Signaling Point/Linkset—Name of the signaling point, signaling point, and linkset for which access lists are being displayed. To see detailed information for the signaling point, signaling point, or linkset, click the signaling point, signaling point, or linkset name.


78-15589-01


• List #—Access list number configured on the signaling point and applied to the linkset. ITP uses access list numbers 2700 through 2799.


Viewing ITP Signaling Point Information: GTT MAP Status

The SGM: GTT MAP Status page displays detailed information about all GTT MAPs associated with the selected signaling point.

To access the SGM: GTT MAP Status page, select GTT MAP Status in the SGM: Signaling Point Details page. (This option is not available if the signaling point is in Unknown status.)

The SGM: GTT MAP Status page displays the following information for the selected signaling point:

• Node Name and Signaling Point Name (in header)—Name of the signaling point and signaling point for which GTT MAPs are being displayed.




• Node—Name of the signaling point for which GTT MAPs are being displayed. To see detailed information for the signaling point, click the signaling point name.

• Signaling Point—Name of the signaling point for which GTT MAPs are being displayed. To see detailed information for the signaling point, click the signaling point name.

• Point Code—Primary point code for the GTT MAP.

• SSN—Primary subsystem number (SSN) for the GTT MAP.

• Point Code Status—Status of the primary point code. Possible values are:

– Allowed

– Prohibited—Either the point code cannot be reached, or the point code is labeled Prohibited by the SCCP protocol.


78-15589-01


• SSN Status—Status of the primary SSN. Possible values are:

– Allowed

– Prohibited—Either the remote subsystem cannot be reached, or the subsystem is labeled Prohibited by the SCCP protocol.

• Congestion Level—MTP3 congestion level for the primary point code. Possible values are:

– No congestion—Corresponds to None. The link is not congested.

– Congestion level 1—Corresponds to Low. The link is slightly congested.

– Congestion level 2—Corresponds to High. The link is congested.

– Congestion level 3—Corresponds to Very High. The link is very congested.


Viewing ITP Signaling Point Information: MTP3 Event Log Messages

From the SGM: MTP3 Event Log page, you can view the most recent MTP3 events associated with the selected signaling point.

To access the SGM: MTP3 Event Log page, select MTP3 Event Log in the SGM: Signaling Point Details page. (This option is not available if the signaling point is in Unknown status.)

The SGM: MTP3 Event Log table displays the following information for the selected signaling point:

• Node Name and Signaling Point Name (in header)—Name of the signaling point and signaling point associated with the MTP3 event log.




• Node—Name or IP address of the signaling point. To see detailed information for the signaling point, click the signaling point name.


78-15589-01


• Signaling Point—Name of the signaling point. To see detailed information for the signaling point, click the signaling point name.

• Logged Events—Total number of MTP3 events that have been logged for this signaling point.

• Dropped Events—Total number of MTP3 events that have been dropped for this signaling point.

• Max Events—Maximum number of events that the event history can contain. When event history table is full, the oldest entries are deleted as new entries are added.

• Allowed Events—ITP parameter that specifies the absolute maximum for the Max Events field. That is, for this ITP device, the Max Events field can range from 0 to the value specified by the Allowed Events field.

• Index—Event number, assigned to the event by SGM.


Viewing ITP Signaling Point Information: Route Detail

From the SGM: Route Detail page, you can view detailed information about routes associated with the selected signaling point, including dynamic and shadow routes.

To access the SGM: Route Detail page, use one of the following procedures:

• Right-click a signaling point in a window, then select Drill Down > Route to Point Code from the right-click menu.

• Select Route Detail in the SGM: Signaling Point Details page.

These options are not available if the signaling point is in Unknown status.

The SGM: Route Detail table displays the following information for the selected signaling point:

• Node Name and Signaling Point Name (in header)—Name of the signaling point and signaling point for which route detail is being displayed.




78-15589-01



• Node—Name of the signaling point for which route detail is being displayed. To see detailed information for the signaling point, click the signaling point name.

• Signaling Point—Name of the signaling point for which route detail is being displayed. To see detailed information for the signaling point, click the signaling point name.

• Destination—Destination point code and mask length for packets on the selected signaling point.

The destination point code is the point code to which a given packet is routed.

The mask length is the number of significant leading bits in the point code. The mask length is always 14 for ITU and 24 for ANSI.

• Cost—Cost of the route to the destination, relative to other routes. The valid costs range from 1 (lowest cost and highest priority) through 9 (highest cost and lowest priority).

• Destination Linkset—Destination linkset associated with the destination point code. The destination linkset is also known as the output linkset. To see detailed information for the linkset, click the linkset name.

• QoS—Quality of service (QoS) class of the route, as configured by the network administrator. Valid QoS classes range from 1 through 7; ALL indicates that the route accepts all QoS classes.

• Access—Status of the destination. Possible values are:

– Accessible

– Inaccessible

– Restricted

– Unknown


78-15589-01


• Management Status—Accessibility of the destination from the adjacent point code at the remote end of the linkset. Possible values are:

– Allowed—Traffic is allowed on the route without restriction.

– Prohibited—Traffic is prohibited on the route.

– Restricted—Traffic is restricted on the route.

– Unknown—Accessibility cannot be determined.

• Route State—Status of the route. Possible values are:

– Available

– Restricted

– Unavailable

Viewing Information About LinksetsSGM enables you to view the following information about linksets:

• Viewing the Network Status Linkset Dashboard, page 7-34

• Viewing ITP Linkset Status, page 7-35

• Viewing ITP Linkset Details, page 7-38

• Viewing ITP Linkset Information: Access Lists, page 7-49

Viewing the Network Status Linkset Dashboard

The SGM: Linkset Dashboard page lists all discovered linksets, and provides links to messages and metrics for each linkset.

To access the SGM: Linkset Dashboard page, select Network Status Dashboard from the SGM Server Home Page, then click Linkset Dashboard.

To see status change messages and SNMP trap messages associated with a given linkset, click Messages.

To see network status metrics associated with a given linkset, click Metrics.

To see all access lists associated with a given linkset, click Access Lists.


78-15589-01


You can sort the table based on the information in the Linksets column. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

Viewing ITP Linkset Status

The SGM: ITP Linkset Status page displays information about the linksets that have been discovered by SGM.

To access the SGM: ITP Linkset Status page, select ITP Linkset Status from the SGM Server Home Page. SGM displays the SGM: ITP Linkset Status page (Figure 7-4).

Figure 7-4 SGM: ITP Linkset Status Page

You can sort the SGM: ITP Linkset Status table based on the information in one of the columns. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.


78-15589-01


The SGM: ITP Linkset Status page displays the following information for each linkset:

• Server Name (in header)—Name of the SGM server associated with the linkset.



• Linkset Name—Name of the linkset. To see detailed information for the linkset, click the linkset name.

• Node—Name of signaling point for the linkset. To see detailed information for the signaling point, click the signaling point name.

• SP Name—Name of signaling point for the linkset. To see detailed information for the signaling point, click the signaling point name.

• Point Code—Point code of the primary signaling point for the linkset.

• Adjacent Linkset Name—Name of adjacent linkset. To see detailed information for the linkset, click the linkset name.

• Adjacent Node—Name of adjacent signaling point for the linkset. To see detailed information for the signaling point, click the signaling point name.

• Adjacent SP—Name of adjacent signaling point for the linkset. To see detailed information for the signaling point, click the signaling point name.

• Adjacent Point Code—Point code of the adjacent signaling point for the linkset.

• Status—Current status of the linkset, with a color-coded background. Possible values are:

– Active (green)—The linkset is currently fully functional.

– Unavailable (red)—An error is preventing traffic from flowing on this linkset.

– Shutdown (blue)—An ITP administrator has set the linkset to prevent traffic from flowing. When a linkset is set to Shutdown, all its associated links are set to Failed by Cisco IOS.


78-15589-01


– Unknown (red)—Either the signaling point associated with this linkset has failed to respond to an SNMP request, or SGM found that the linkset no longer exists.

– Warning (yellow)—The linkset is active, but one or more links in the linkset is congested or is in Failed, Unknown, or Warning status, and is not flagged as Ignored. At least one link is available and can carry traffic.


– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





– Link Inactive




78-15589-01





• Type—Type of linkset, which SGM determines by examining the links defined in the linkset. Possible linkset types are:







Viewing ITP Linkset Details

The SGM: Linkset Details page displays detailed information about all discovered linksets, including their associated signaling points, links, events, status, and other information.

To access the SGM: Linkset Details page, click a linkset name in the SGM: ITP Linkset Status page. SGM displays the SGM: Linkset Details page (Figure 7-5).


78-15589-01


Figure 7-5 SGM: Linkset Details Page

The SGM: Linkset Details page displays the following information for the selected linkset:

• Node Name, Signaling Point Name, and Linkset Name (in header)—DNS name of the node, as discovered by SGM, signaling point name, and linkset name.





• Messages—Opens the Network Status: Last X Status Change and Trap Messages Web page for the linkset.

• Metrics—Opens the Network Status Messages: Messages Web page for the linkset.


78-15589-01


• Access Lists—Opens the SGM: ITP Access Lists Web page for the linkset.

• Status—Current status of the linkset, with a color-coded background. Possible values are:

– Active (green)—The linkset is currently fully functional.

– Unavailable (red)—An error is preventing traffic from flowing on this linkset.

– Shutdown (blue)—An ITP administrator has set the linkset to prevent traffic from flowing. When a linkset is set to Shutdown, all its associated links are set to Failed by Cisco IOS.

– Unknown (red)—Either the signaling point associated with this linkset has failed to respond to an SNMP request, or SGM found that the linkset no longer exists.

– Warning (yellow)—The linkset is active, but one or more links in the linkset is congested or is in Failed, Unknown, or Warning status, and is not flagged as Ignored. At least one link is available and can carry traffic.


– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested



78-15589-01





– Link Inactive






• Description—Description of the linkset. If the linkset has no description, this field is blank.

• Poll Error Message—Last error message received by the linkset.

• Node—Name of primary signaling point for the linkset. To see detailed information for the signaling point, click the signaling point name.

• Signaling Point—Name of primary signaling point for the linkset. To see detailed information for the signaling point, click the signaling point name.

• Local Point Code—Point code of the primary signaling point for the linkset.

• Adjacent Node—Name of adjacent signaling point for the linkset. To see detailed information for the adjacent signaling point, click the signaling point name.

• Adjacent Signaling Point—Name of adjacent signaling point for the linkset. To see detailed information for the adjacent signaling point, click the signaling point name.


78-15589-01


• Adjacent Point Code—Point code of the adjacent signaling point for the linkset.











• Note—Note associated with this linkset. If there is no note associated with this linkset, this field is blank.

• Note Timestamp—Date and time the note associated with this linkset was last updated. If there is no note associated with this linkset, this field is blank.

• Internal ID—Internal ID of the linkset. The internal ID is a unique ID for every event, link, linkset, signaling point, and signaling point, assigned by SGM for its own internal use. It can also be useful when the Cisco TAC is debugging problems.

• MTP3 Accounting Enabled—Indicates whether the collection of MTP3 accounting statistics is enabled for the linkset.

• GTT Accounting Enabled—Indicates whether the collection of GTT accounting statistics is enabled for the linkset. For Cisco IOS software releases prior to 12.2(4)MB10, this field displays Unknown.


78-15589-01


• Packets Received Per Sec.—Number of packets received by the linkset per second.


• Packets Sent Per Sec.—Number of packets sent by the linkset per second.


• Bits Received Per Sec.—Number of bits received by the linkset per second.


• Bits Sent Per Sec.—Number of bits sent by the linkset per second.


• Receive Utilization—Amount of the linkset’s receive capacity being used, as a percentage or in Erlangs (as set in the Preferences window), calculated using the following formula:

Receive Utilization = (Bits Received Per Sec.)/Planned Capacity

Planned Capacity is the planned capacity of the linkset in bits per second.

– For a linkset of type Serial, Planned Capacity is the available bandwidth for the linkset.

– For a linkset of type SCTPIP or of type Mixed, Planned Capacity is set on the ITP using the plan-capacity CS7 linkset configuration command.If Planned Capacity is not set on the ITP for this linkset, this field displays the phrase Planned Capacity for ITP Not Set.

– For a linkset of type Other, this field displays the phrase Planned Capacity for ITP Not Set.


If the planned receive capacity is not set for the link, this field displays Set Plan Capacity on ITP.


78-15589-01


• Send Utilization—Amount of the linkset’s send capacity being used, as a percentage or in Erlangs (as set in the Preferences window), calculated using the following formula:

Send Utilization = (Bits Sent Per Sec.)/Planned Capacity

Planned Capacity is the planned capacity of the linkset in bits per second.

– For a linkset of type Serial, Planned Capacity is the available bandwidth for the linkset.

– For a linkset of type SCTPIP or of type Mixed, Planned Capacity is set on the ITP using the plan-capacity CS7 linkset configuration command.If Planned Capacity is not set on the ITP for this linkset, this field displays the phrase Planned Capacity for ITP Not Set.

– For a linkset of type Other, this field displays the phrase Planned Capacity for ITP Not Set.


If the planned send capacity is not set for the link, this field displays Set Plan Capacity on ITP.

• Receive Plan Capacity—Planned capacity of the linkset to receive, in bits per second.



If Receive Plan Capacity is not set on the ITP for this linkset, this field displays the value 0.



78-15589-01


• Send Plan Capacity—Planned capacity of the linkset to send, in bits per second.



If Send Plan Capacity is not set on the ITP for this linkset, this field displays the value 0.


• Drops—Total number of packets that have been dropped by the linkset.



• Duration In Service %—Percentage of time the linkset has been in service since the last reboot of the ITP, or since ITP last reset the counters.

• Duration Out Of Service %—Percentage of time the linkset has been out of service since the last reboot of the ITP, or since ITP last reset the counters.

The SGM: Linkset Details page also displays the following information about links associated with the selected linkset:

• SLC—Identifier for the link, assigned by SGM.







78-15589-01






• Ports—Local and remote ports for the link.

• QoS—Quality of service (QoS) class of the link.

• Congestion—Indicates whether there is congestion on the link. A link is congested if it has too many packets waiting to be sent. This condition could be caused by the failure of an element in your network.

Possible values for the Congestion field are:






• Utilization—Receive Utilization (Rcvd) and Send Utilization (Sent) for the link, expressed as either a utilization percentage or a number of Erlangs.


If the planned send or receive capacity is not set for the link, this field displays Set Plan Capacity on ITP.

• Bits/Sec—Number of bits received (Rcvd) and sent by the link per second.



78-15589-01


• Ignored—Indicates whether the link has been flagged as Ignored (that is, whether the link is to be included when aggregating and displaying SGM status information).

• Status—Current status of the link, with a color-coded background. Possible values are:

– Active (green)—The link is currently fully functional.

– Blocked (red)—Either the signaling point associated with this link has failed to respond to an SNMP request, or SGM found that the link no longer exists.

– Failed (red)—An error is preventing traffic from flowing on this link, or the associated linkset has been set to Shutdown status.


– InhibitLoc (blue)—A local ITP administrator has set the link to prevent traffic from flowing.

– InhibitRem (blue)—A remote ITP administrator has set the link to prevent traffic from flowing.

– Shutdown (blue)—An ITP administrator has set the link to prevent traffic from flowing.


78-15589-01


– Unknown (red)—Either the signaling point associated with this link has failed to respond to an SNMP request, or SGM found that the link no longer exists.


– Warning (yellow)—The link is active and traffic is flowing, but one or more of the following situations has occurred:

- The link is congested.

- The link has exceeded the defined Receive Utilization % or Send Utilization %.

- One or more of the local or remote IP addresses defined for SCTP is not active.

There is no Unshut or No Shut status.


– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





78-15589-01



– Link Inactive






• Status Summary—Opens the SGM: Link Status Summary Web Page.

Viewing ITP Linkset Information: Access Lists

The SGM: ITP Access Lists page displays all access lists associated with the selected linkset.

To access the SGM: ITP Access Lists page for a linkset, select Access List in the SGM: Linkset Details page. (This option is not available if the associated signaling point is in Unknown or Unmanaged status.)

The SGM: ITP Access Lists page displays the following information for the selected linkset:

• Node Name, Signaling Point Name, and Linkset Name (in header)—Name of the signaling point, signaling point, and linkset for which access lists are being displayed.




78-15589-01



• Node/Signaling Point/Linkset—Name of the signaling point, signaling point, and linkset for which access lists are being displayed. To see detailed information for the signaling point, signaling point, or linkset, click the signaling point, signaling point, or linkset name.

• List #—Access list number configured on the signaling point and applied to the linkset. ITP uses access list numbers 2700 through 2799.


Viewing Information About LinksSGM enables you to view the following information about links:

• Viewing the Network Status Link Dashboard, page 7-50

• Viewing ITP Link Status, page 7-51

• Viewing Q.752 Measurements for a Link, page 7-58

• Viewing Interface Details for a Link, page 7-61

• Viewing M2PA Peer Details for a Link, page 7-64

Viewing the Network Status Link Dashboard

The SGM: Link Dashboard page lists all discovered links, and provides links to messages and metrics for each link.

To access the SGM: Link Dashboard page, select Network Status Dashboard from the SGM Server Home Page, then click Link Dashboard.

To see status change messages and SNMP trap messages associated with a given link, click Messages.

To see network status metrics associated with a given link, click Metrics.

To see detailed network performance measurements for a given link, based on ITU-T Recommendation Q.752, click Q.752 Measurements. (This field is displayed only if the selected link has a status of Active or Warning and is connected to an ITP device.)


78-15589-01


To see detailed interface information for a given link, click Interface Details. (This field is displayed only if the selected link has a status of Active or Warning and is connected to an ITP device.)

To see detailed SCTP association information for a given link, click M2PA Peer Details. (This field is displayed only if the selected link has a status of Active or Warning and is connected to an ITP device.)

You can sort the table based on the information in the Links column. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

Viewing ITP Link Status

The SGM: Link Status Summary page displays status information for a single link.

To access the SGM: Link Status Summary page, click a linkset name in the SGM: ITP Linkset Status page to display the SGM: Linkset Details page, then click Summary beside a link at the bottom of the page. SGM displays the SGM: Link Status Summary page (Figure 7-6).


78-15589-01


Figure 7-6 SGM: Link Status Summary Page

The SGM: Link Status Summary page displays the following information for the selected link:

• Node Name, Signaling Point Name, Linkset Name, and SLC (in header)—Name of the signaling point, signaling point, and linkset associated with the link, and the SLC of the link.

• Server Name (in header)—Name of the SGM server associated with the link.



• Node—Name of the signaling point associated with the link. To see detailed information for the signaling point, click the signaling point name.

• Signaling Point—Name of the signaling point associated with the link. To see detailed information for the signaling point, click the signaling point name.


78-15589-01


• Linkset—Name of the linkset associated with the link. To see detailed information for the linkset, click the linkset name.

• Link SLC—Signaling link code (SLC) ID for the link.

• Messages—Opens the Network Status: Last X Status Change and Trap Messages Web page for the link.

• Metrics—Opens the Network Status Messages: Messages Web page for the link.

• Q.752 Measurements—Opens the SGM: Q.752 Measurements Web page for the link. This link is not displayed for virtual links.

• Interface Details—Opens the SGM: Interface Details Web page for the link. This field is displayed only if the selected link is not a virtual link, has a status of Active or Warning, and is connected to an ITP device.

• M2PA Peer Details—Opens the SGM: M2PA Peer Details Web page for the link. This field is displayed only if the selected link is not a virtual link, has a status of Active or Warning, and is connected to an ITP device.

• Status—Current status of the link, with a color-coded background. Possible values are:

– Active (green)—The link is currently fully functional.

– Blocked (red)—Either the signaling point associated with this link has failed to respond to an SNMP request, or SGM found that the link no longer exists.

– Failed (red)—An error is preventing traffic from flowing on this link, or the associated linkset has been set to Shutdown status.


– InhibitLoc (blue)—A local ITP administrator has set the link to prevent traffic from flowing.

– InhibitRem (blue)—A remote ITP administrator has set the link to prevent traffic from flowing.

– Shutdown (blue)—An ITP administrator has set the link to prevent traffic from flowing.


78-15589-01


– Unknown (red)—Either the signaling point associated with this link has failed to respond to an SNMP request, or SGM found that the link no longer exists.


– Warning (yellow)—The link is active and traffic is flowing, but one or more of the following situations has occurred:

- The link is congested.

- The link has exceeded the defined Receive Utilization % or Send Utilization %.

- One or more of the local or remote IP addresses defined for SCTP is not active.

There is no Unshut or No Shut status.


– None

– SGM Restart


– Unconfigured

– SNMP Timeout


– Not ITP Device


– MIB Data Error

– SNMP Exception



– Link Congested





78-15589-01



– Link Inactive






• Last State Change—Date and time that the status of the link last changed.








• Receive Utilization—Amount, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), that the link is under (UnderThreshold) or over (OverThreshold) its configured receive utilization threshold.


78-15589-01


• Send Utilization—Amount, expressed as either a utilization percentage or a number of Erlangs (as set in the Preferences window), that the link is under (UnderThreshold) or over (OverThreshold) its configured send utilization threshold.

• Receive Plan Capacity—Planned capacity of the link to receive, in bits per second.


– For a link of type SCTPIP or Mixed, set on the ITP using the plan-capacity CS7 link configuration command.

If Receive Plan Capacity is not set on the ITP for this link, this field displays the value 0.


• Send Plan Capacity—Planned capacity of the link to send, in bits per second.


– For a link of type SCTPIP or Mixed, set on the ITP using the plan-capacity CS7 link configuration command.

If Send Plan Capacity is not set on the ITP for this link, this field displays the value 0.


• Receive Threshold—Indicates when a cItpSpLinkRcvdUtilChange is to be generated for the link, as a percent of its total receive capacity. For example, if Receive Plan Capacity is 64000 bits per second, and Receive Threshold % is 50, then a cItpSpLinkRcvdUtilChange notification is generated when the link reaches 50% of 64000, or 32000 bits per second.

• Send Threshold—Indicates when a cItpSpLinkSentUtilChange is to be generated for the link, as a percent of its total send capacity. For example, if Send Plan Capacity is 64000 bits per second, and Send Threshold % is 50, then a cItpSpLinkSentUtilChange notification is generated when the link reaches 50% of 64000, or 32000 bits per second.

• Local Addresses—Local IP addresses associated with the link, and their status.

• Remote Addresses—Remote IP addresses associated with the link, and their status.


78-15589-01







• QoS—Quality of service (QoS) class of the link.

• Ignored—Indicates whether the link is Ignored (that is, whether the link is to be included when aggregating and displaying SGM status information).

• Signal Link Test—Indicates whether the link acknowledged a Signal Link Test Message (SLTM), which tests the link's ability to carry data.

• Packets Received Per Sec.—Number of packets received by the link per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Packets Sent Per Sec.—Number of packets sent by the link per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Bits Received Per Sec.—Number of bits received by the link per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Bits Sent Per Sec.—Number of bits sent by the link per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• LSSU Packets Received—Total number of SS7 Message Transfer Part Layer 2 (MTP2) Links Status Signal Unit (LSSU) packets received by the link.

• LSSU Packets Sent—Total number of LSSU packets sent by the link.

• Drops—Total number of packets that have been dropped by the link.

• Transmit Queue Depth—Number of packets waiting to be sent on by the link.


78-15589-01


• Ports—Local and remote ports for the link.

• Config. Local IP Address—Configured local IP address associated with the link.

Viewing Q.752 Measurements for a Link

The SGM: Q.752 Measurements page displays network performance measurements for a link, based on ITU-T Recommendation Q.752.

To access the SGM: Q.752 Measurements page, use the following procedure:

Step 1 Click a linkset name in the SGM: ITP Linkset Status page to display the SGM: Linkset Details page.

Step 2 Click Summary beside a link at the bottom of the page to display the SGM: Link Status Summary page.

Step 3 Click Q.752 Measurements to display the SGM: Q.752 Measurements page (Figure 7-9).


78-15589-01


Figure 7-7 SGM: Q.752 Measurements Page

The SGM: Q.752 Measurements table displays the following information for the selected link:

• Server Name (in header)—Name of the SGM server associated with this link.



• Node—Name of the node associated with this link. To see detailed information for the node, click the node name.

• Signaling Point—Name of the signaling point associated with this link. To see detailed information for the signaling point, click the signaling point name.

• Linkset—Name of the linkset associated with this link. To see detailed information for the linkset, click the linkset name.


78-15589-01


• Link SLC—Signaling link code (SLC) ID for the link. To see detailed information for the link, click the link name.

• Link Failures Count—Number of times the link was unavailable for signaling.

• Alignment Error Count—Number of errors detected during link alignment. Link alignment takes place at start up, or when trying to bring up a failed link.

• Negative ACK Count—Number of errors detected during link acknowledgement.

• Local Inhibit Onset—Number of times a local ITP administrator has inhibited the link (that is, set the link to prevent traffic from flowing).

• Local Inhibit Duration—Total time, in seconds, the link has been locally inhibited.

• Remote Inhibit Onset—Number of times a remote ITP administrator has inhibited the link.

• Remote Inhibit Duration—Total time, in seconds, the link has been remotely inhibited.

• Packets Retransmitted Count—Number of packets retransmitted by the link.

• Bytes Retransmitted Count—Number of bytes retransmitted by the link.

• Congestion Occurrences—Number of times congestion has occurred on the link.

• Congestion Duration—Total time the link has been congested.

• Congestion Level—Level of congestion: 1, 2, or 3.

• Packets Lost—Number of packets lost by the link as a result of congestion at each level.

• Times At Level With Packet Loss—Number of times the link has been congested and has lost packets at each level.


78-15589-01


Viewing Interface Details for a Link

The SGM: Interface Details page displays detailed interface information for a link, with one column of information for each of the link’s interfaces.

To access the SGM: Interface Details page, use the following procedure:



Step 3 Click Interface Details to display the SGM: Interface Details page (Figure 7-8).

Figure 7-8 SGM: Interface Details Page


78-15589-01


The SGM: Interface Details table displays the following information for the selected link:


• Server Name (in header)—Name of the SGM server associated with the link.



• Node—Name of the signaling point associated with the link. To see detailed information for the signaling point, click the signaling point name.

• Signaling Point—Name of the signaling point associated with the link. To see detailed information for the signaling point, click the signaling point name.

• Linkset—Name of the linkset associated with the link. To see detailed information for the linkset, click the linkset name.

• Link SLC—Signaling link code (SLC) ID for the link. To see detailed information for the link, click the link name.

• Description—Text string containing information about the interface.

• IP Address—(SCTP links only) IP address corresponding to the media-dependent “physical” address. If the interface does not have such an address (for example, a serial line), this field displays N/A.

• Mask—(SCTP links only) Subnet mask corresponding to the media-dependent “physical” address. If the interface does not have such an address (for example, a serial line), this field displays N/A.

• Type—Type of interface, such as Ethernet.

• MTU—Size, in bytes, of the largest datagram that can be sent or received on the interface.

• Speed (Bits/Sec)—Estimate, in bits per second, of the interface's current bandwidth. If the interface does not vary in bandwidth, or if no accurate estimate can be made, this field displays the nominal bandwidth.


78-15589-01


• Physical Address—(SCTP links only) Address of the interface at the protocol layer immediately “below” the network layer in the protocol stack. If the interface does not have such an address (for example, a serial line), this field displays N/A.

• Admin Status—Desired state of the interface. Possible values are:

– Up

– Down

– Testing

• Operational Status—Current operational state of the interface. Possible values are:

– Up

– Down

– Testing

– Unknown

– Dormant

• Line Protocol—Current state of the line protocol. Possible values are:

– Up—Software processes that handle the line protocol consider the line to be usable (that is, keepalives are successful).

– Down—Software processes that handle the line protocol consider the line to be unusable.

You can use the Line Protocol together with Operational Status to troubleshoot interface connection problems. For example, if Operational Status is Up, but Line Protocol is Down, the interface has detected a carrier on the physical layer, but there might be clocking or framing problems.

• Bytes In/Sec—Number of bytes received on the interface per second, including framing characters.

• Bytes Out/Sec—Number of bytes sent on the interface per second, including framing characters.

• Packets In/Sec—Number of packets delivered per second to a higher-layer protocol.

• Packets Out/Sec—Total number of packets that higher-level protocols requested to be sent to the network per second, including those that were discarded or not sent.


78-15589-01


• Discards In—Number of inbound packets that were discarded, even though no errors were detected to prevent their delivery to a higher-layer protocol. For example, a packet might be discarded to free buffer space.

• Discards Out—Number of outbound packets that were discarded, even though no errors were detected to prevent their delivery to a higher-layer protocol. For example, a packet might be discarded to free buffer space.

• Errors In—Number of inbound packets that contained errors that prevented their delivery to a higher-layer protocol.

• Errors Out—Number of outbound packets that were not sent because of errors.

Viewing M2PA Peer Details for a Link

The SGM: M2PA Peer Details page displays detailed SCTP association information for a link.

To access the SGM: M2PA Peer Details page, use the following procedure:



Step 3 Click M2PA Peer Details to display the SGM: M2PA Peer Details page (Figure 7-9).


78-15589-01


Figure 7-9 SGM: M2PA Peer Details Page

The SGM: M2PA Peer Details table displays the following information for the selected link:


• Server Name (in header)—Name of the SGM server to which this SCTP association belongs.



• Node—Name of the signaling point to which this SCTP association belongs. To see detailed information for the signaling point, click the signaling point name.

• Signaling Point—Name of the signaling point to which this SCTP association belongs. To see detailed information for the signaling point, click the signaling point name.


78-15589-01


• Linkset—Name of the linkset to which this SCTP association belongs. To see detailed information for the linkset, click the linkset name.

• Link SLC—Signaling link code (SLC) ID to which this SCTP association corresponds.

• Status—Current status of the SCTP association. Possible values are:

– Closed

– CookieWait

– CookieEchoed

– DeleteTCB

– Established

– ShutdownAckSent

– ShutdownPending

– ShutdownReceived

– ShutdownSent

For detailed information about each status, refer to RFC 2960, Stream Control Transmission Protocol.

• Uptime—Time the link has been up, in weeks, days, hours, minutes, and seconds.

• Remote Port—Remote port number for the SCTP association.

• Local Port—Local port number for the SCTP association.

• Primary Address—Designated primary IP address for the SCTP association.

• Effective Address—IP address currently being used by the SCTP association.

• Local IP Address Configuration: IP Address—Local IP addresses associated with the link.

• Local IP Address Configuration: Uptime—Time each local IP address associated with the link has been up, in weeks, days, hours, minutes, and seconds.

• Remote IP Address Configuration: IP Address—Remote IP addresses associated with the link.


78-15589-01


• Remote IP Address Configuration: Uptime—Time each remote IP address associated with the link has been up, in weeks, days, hours, minutes, and seconds.

• Remote IP Address Configuration: Retry Timeout (msecs)—Time, in milliseconds, that SGM waits between attempts to connect to the remote IP address.

• Remote IP Address Configuration: Maximum Retries—Maximum number of times SGM will attempt to connect to the remote IP address.

• Remote IP Address Configuration: Retries—Number of times SGM has attempted to connect to the remote IP address.

• Remote IP Address Status: Smoothed Round Trip Time (msecs)—Average, in milliseconds, of all round-trip times between the local and remote systems on an IP network.

• Remote IP Address Status: Failure Count—Number of times the remote IP address was marked as failed.

• Remote IP Address Status: Heartbeat Status—Current status of the heartbeat associated with the remote IP address. Valid values are Active and Inactive.

• Remote IP Address Status: IP Status—Current status of the remote IP address. Valid values are Active and Inactive.

• Packets Sent per Sec.—Number of IP datagrams sent per second by this SCTP association.

• Packets Received per Sec.—Number of IP datagrams received per second by this SCTP association.

• Control Chunks Sent per Sec.—Number of control chunks sent per second by this SCTP association.

• Control Chunks Received per Sec.—Number of control chunks received per second by this SCTP association.

• Ordered Chunks Sent per Sec.—Number of ordered chunks sent per second by this SCTP association.

• Ordered Chunks Received per Sec.—Number of ordered chunks received per second by this SCTP association.

• Unordered Chunks Sent per Sec.—Number of unordered chunks sent per second by this SCTP association.


78-15589-01


• Unordered Chunks Received per Sec.—Number of unordered chunks received per second by this SCTP association.

• Retransmitted Chunks per Sec.—Number of chunks retransmitted per second by this SCTP association.

• Retransmitted Fast Chunks per Sec.—Number of fast chunks retransmitted per second by this SCTP association.

• MTU—Maximum transmission unit (MTU) size to be used by this SCTP association. This is the smallest MTU size supported by any of the IP addresses used by the SCTP association.

• In Streams—Inbound streams as negotiated when the SCTP association was started.

• Out Streams—Outbound streams as negotiated when the SCTP association was started.

• Maximum Retries—Maximum number of data retransmissions in the SCTP association context.

• Local Receive Window Size—Current local receive window size for this SCTP association.

• Remote Receive Window Size—Current local send window size for this SCTP association.

• Initial Retry Timeout (msecs)—Initial timeout value, in milliseconds, permitted by the SCTP implementation for the retry timeout.

• Minimum Retry Timeout (msecs)—Minimum timeout value, in milliseconds, permitted by the SCTP implementation for the retry timeout.

• Maximum Retry Timeout (msecs)—Maximum timeout value, in milliseconds, permitted by the SCTP implementation for the retry timeout.

• Bundle Chunks—Indicates whether the SCTP protocol allows chunks to be bundled into a single datagram as follows. Valid values are:

– true (1)—Chunks are bundled.

– false (2)—Chunks are not bundled.

• Bundle Timeout (msecs)—Time, in milliseconds, to wait to allow data chunks to accumulate so that they can be transmitted in the same datagram.


78-15589-01


Viewing Information About Application ServersSGM enables you to view the following information about application servers:

• Viewing Application Server Status, page 7-69

• Viewing Application Server Details, page 7-71

• Viewing Application Server Process Association Details, page 7-77

Viewing Application Server Status

The SGM: Application Server Status page displays information about all discovered application servers, including their names, status, and other important information.

To access the SGM: Application Server Status page, select ITP Application Server Status from the SGM Server Home Page.

You can sort the Application Server Status table based on the information in any column. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

The SGM: Application Server Status page displays the following information:




• AS Name—Name of the application server. To see detailed information for the application server, click the application server name.

• Node—Name of the node associated with the application server. To see detailed information for the node, click the node name.

• SP—Name of the signaling point associated with the application server. To see detailed information for the signaling point, click the signaling point name.


78-15589-01


• Status—Current status of the application server, with a color-coded background. Possible values are:

– Active (green)—The application server is available and application traffic is active. At least one application server process serving this application server is Active.

– Deleted (red)—The application server has been deleted from the SGM database.

– Down (red)—The application server is not available. All application server processes that serve this application server are Down. This is the initial status for application servers.

– Inactive (red)—The application server is available, but no application traffic is active (that is, at least one application server process is Inactive, and no application server process is Active).

– Pending (yellow)—The last remaining Active application server process serving this application server has become Inactive or Down. The next status for this application server will be Active, Inactive, or Down, depending on the recovery timer, and whether an application server process can become Active.

– Shutdown (blue)—An administrator has forced the application server to an unavailable state.

– Unknown (red)—SGM cannot determine the current status of the application server.

– Warning (yellow)—The application server is Active, but at least one application server process association for this application server is not fully functional.

• Mate Status—Current status of the application server on the signaling gateway mate, with a color-coded background. Possible values are:





78-15589-01







• Number of ASP Associations—Total number of application server processes associated with the application server.

• Active ASP Associations—Number of currently active application server processes associated with the application server.

• Protocol—Protocol associated with the application server. Possible values are:

– M3UA—MTP3-User Adaptation.

– SUA—SCCP-User Adaptation.

• Routing Key—Routing key associated with the application server. The routing key is the value upon which the routing decisions are made for the application server.

Viewing Application Server Details

The SGM: Application Server Detail page displays detailed information for an application server.

To access the SGM: Application Server Detail page, click the application server name on the SGM: Application Server Status page.


78-15589-01


You can sort the Application Server Detail table based on the information in any column. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

The SGM: Application Server Detail page displays the following information:

Server Name (in header)—

Name of the SGM server associated with the node.



• Name—Name of the application server.

• Status—Current status of the application server, with a color-coded background. Possible values are:








78-15589-01




• Poll Timestamp—Date and time of the last poll of the application server.

• Poll Error Message—Last error message received by the application server.

• Node—Name of the node associated with the application server. To see detailed information for the node, click the node name.

• Signaling Point—Name of the signaling point associated with the application server. To see detailed information for the signaling point, click the signaling point name.

• Protocol—Protocol associated with the application server. Possible values are:



• Mate Status—Current status of the application server on the signaling gateway mate, with a color-coded background. Possible values are:







78-15589-01





• Routing Key—Routing key associated with the application server. The routing key is the value upon which the routing decisions are made for the application server.

• ASP Associations—Total number of application server processes associated with the application server.

• Active ASP Associations—Number of currently active application server processes associated with the application server.

• Internal ID—Internal ID of the application server. The internal ID is a unique ID for every event, link, linkset, signaling point, and node, assigned by SGM for its own internal use. It can also be useful when the Cisco TAC is debugging problems.

• MTP3 Packets Per Sec.—Number of MTP3 packets received by the application server per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• ASP Packets Per Sec.—Number of application server process packets sent by the application server per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Active Time—Time, in weeks, days, hours, minutes, and seconds, that the application server process has been Active.

• Note—Note associated with this application server. If there is no note associated with this application server, this field is blank.

• Note Timestamp—Date and time the note associated with this application server was last updated. If there is no note associated with this application server, this field is blank.


78-15589-01


• Traffic Mode—Method by which the application server forwards requests to its active application server processes. Possible values are:

– overRide—One application server process takes over all traffic for the application server, possibly overriding any currently active application server process in the application server.

– broadcast—Every active application server process receives the same message.

– loadBind—Each application server process shares in the traffic distribution with every other currently active application server process, based on application server process bindings.

– loadRndRobin—Each application server process shares in the traffic distribution with every other currently active application server process, using a roundrobin algorithm.

– undefined—The traffic mode is not defined. The first application server process that becomes active defines the traffic mode.

• Name—Name of an application server process serving this application server.

• Adjacent Node—Name of the adjacent node associated with the application server process. To see detailed information for the adjacent node, click the adjacent node name.

• Adjacent ASP—Name of the adjacent application server process.

• Status—Current status of the application server process, with a color-coded background. Possible values are:






78-15589-01






• Instance Status—Current status of the protocol associated with the application server process, with a color-coded background. Possible values are:

– Active (green)—The protocol is available.

– Shutdown (blue)—An administrator has forced the protocol to an unavailable state.

– Unknown (red)—SGM cannot determine the current status of the protocol.

• Congestion—Indicates whether there is congestion on the application server process. An application server process is congested if it has too many packets waiting to be sent. This condition could be caused by the failure of an element in your network.

Possible values for the Congestion field are None, indicating no congestion, and 1 to 7, indicating levels of congestion from very light (1) to very heavy (7).

• Status Summary—Opens the SGM: Application Server Process Association Detail Web Page.


78-15589-01


Viewing Application Server Process Association Details

The SGM: Application Server Process Association Detail page displays detailed information for an application server process.

To access the SGM: Application Server Process Association Detail page, click Summary beside an application server process association at the bottom of the SGM: Application Server Detail page.

You can sort the Application Server Process Association Detail table based on the information in any column. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

The SGM: Application Server Process Association Detail page displays the following information:




• ASP Name—Name of the application server process.

• Status—Current status of the application server process, with a color-coded background. Possible values are:

– Active (green)—The remote peer at the application server process is available and application traffic is active.

– Blocked (red)—The application server process cannot receive normal data traffic, but it can send and receive control messages.

– Deleted (red)—The application server process has been deleted from the SGM database.

– Down (red)—The remote peer at the application server process is not available, or the related SCTP association is down. This is the initial status for application server processes.

– Inactive (red)—The remote peer at the application server process is available, and the related SCTP association is up, but application traffic has stopped. The application server process should not receive any DATA or SNMM messages for the application server.


78-15589-01


– Shutdown (blue)—An administrator has forced the application server process to an unavailable state.

– Unknown (red)—SGM cannot determine the current status of the application server process.

– Warning (yellow)—The application server process is Active, but some underlying facility is not fully functional.

• Poll Timestamp—Date and time of the last poll of the application server process.

• Poll Error Message—Last error message received by the application server process.

• Node—Name of the node associated with the application server process. To see detailed information for the node, click the node name.

• Signaling Point—Name of the signaling point associated with the application server process. To see detailed information for the signaling point, click the signaling point name.

• Application Server—Name of the application server associated with the application server process. To see detailed information for the application server, click the application server name.

• Protocol—Protocol associated with the application server process. Possible values are:



• Instance Status—Current status of the protocol associated with the application server process, with a color-coded background. Possible values are:





78-15589-01


• Congestion—Indicates whether there is congestion on the application server process. An application server process is congested if it has too many packets waiting to be sent. This condition could be caused by the failure of an element in your network.


• QoS—Quality of service (QoS) class of the application server process.

• Config Local Port—Local port number that was configured for the application server process.

• Local Port—Local port number that is currently in use for the application server process.

• Local Addresses—Local IP addresses associated with the application server process, and their status.

• Config Remote Port—Remote port number that was configured for the application server process.

• Remote Port—Remote port number that is currently in use for the application server process.

• Remote Addresses—Remote IP addresses associated with the application server process, and their status.

• From ASP Packets per Sec.—Number of application server process packets sent by the application server process per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• To ASP Packets per Sec.—Number of application server process packets received by the application server process per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• From MTP3 Packets per Sec.—Number of MTP3 packets sent by the application server process per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.


78-15589-01


• To MTP3 Packets per Sec.—Number of MTP3 packets received by the application server process per second. This field initially displays the phrase Waiting for second poll. After two polling cycles, SGM populates this field with actual calculated rates.

• Note—Note associated with this application server process. If there is no note associated with this application server process, this field is blank.

• Note Timestamp—Date and time the note associated with this application server process was last updated. If there is no note associated with this application server process, this field is blank.

• ASP UP Received—Total number of application server process up (ASPUP) messages received by the application server process.

• ASP UP ACK Sent—Total number of application server process up acknowledgement (UPACK) messages sent by the application server process.

• ASP DOWN Received—Total number of application server process down (ASPDN) messages received by the application server process.

• ASP DOWN ACK Sent—Total number of application server process down acknowledgement (DOWNACK) messages sent by the application server process.

• ASP Active Received—Total number of application server process active messages received by the application server process.

• ASP Active ACK Sent—Total number of application server process active acknowledgement messages sent by the application server process.

• ASP Inactive Received—Total number of application server process inactive messages received by the application server process.

• ASP Inactive ACK Sent—Total number of application server process inactive acknowledgement messages sent by the application server process.

• ERR Received—Total number of error (ERR) messages received by the application server process.

• ERR Sent—Total number of error (ERR) messages sent by the application server process.

• Notify Sent—Total number of notify messages sent by the application server process.

• DUNA Received—Total number of destination unavailable (DUNA) messages received by the application server process.


78-15589-01


• DUNA Sent—Total number of destination unavailable (DUNA) messages sent by the application server process.

• DAVA Received—Total number of destination available (DAVA) messages received by the application server process.

• DAVA Sent—Total number of destination available (DAVA) messages sent by the application server process.

• DUPU Received—Total number of destination user part unavailable (DUPU) messages received by the application server process.

• DUPU Sent—Total number of destination user part unavailable (DUPU) messages sent by the application server process.

• DAUD Received—Total number of destination state audit (DAUD) messages received by the application server process.

• DAUD Sent—Total number of destination state audit (DAUD) messages sent by the application server process.

• SCON 0 Received—Total number of signaling congestion level 0 (SCON0) messages received by the application server process.

• SCON 0 Sent—Total number of signaling congestion level 0 (SCON0) messages sent by the application server process.








78-15589-01


Viewing Information About Signaling Gateway Mated PairsSGM enables you to view the following information about signaling gateway mated pairs:

• Viewing Signaling Gateway Mated Pair Status, page 7-82

• Viewing Signaling Gateway Mated Pair Details, page 7-84

Viewing Signaling Gateway Mated Pair Status

The SGM: Signaling Gateway Mated Pairs Status page displays information about all discovered signaling gateway mated pairs, including their names, status, and other important information.

To access the SGM: Signaling Gateway Mated Pairs Status page, select ITP SGMP Status from the SGM Server Home Page.

You can sort the Signaling Gateway Mated Pairs Status table based on the information in any column. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

The SGM: Signaling Gateway Mated Pairs Status page displays the following information:




• SGMP Name—Name of the signaling gateway mated pair. To see detailed information for the signaling gateway mated pair, click the signaling gateway mated pair name.

• Node—Name of the node associated with the signaling gateway mated pair. To see detailed information for the node, click the node name.

• Signaling Point—Name of the signaling point associated with the signaling gateway mated pair. To see detailed information for the signaling point, click the signaling point name.


78-15589-01


• Status—Current status of the signaling gateway mated pair, with a color-coded background. Possible values are:

– Active (green)—The signaling gateway mated pair is available and application traffic is active.

– Deleted (red)—The signaling gateway mated pair has been deleted from the SGM database.

– Down (red)—The signaling gateway mated pair is not available.

– Inactive (red)—The signaling gateway mated pair is available, but application traffic has stopped.

– Shutdown (blue)—An administrator has forced the signaling gateway mated pair to an unavailable state.

– Unknown (red)—SGM cannot determine the current status of the signaling gateway mated pair.

– Warning (yellow)—The signaling gateway mated pair is Active, but some underlying facility is not fully functional.

• Instance Status—Current status of the protocol associated with the signaling gateway mated pair, with a color-coded background. Possible values are:




• Congestion—Indicates whether there is congestion on the signaling gateway mated pair. A signaling gateway mated pair is congested if it has too many packets waiting to be sent. This condition could be caused by the failure of an element in your network.



78-15589-01


Viewing Signaling Gateway Mated Pair Details

The SGM: Signaling Gateway Mated Pairs Details page displays detailed information about a signaling gateway mated pair.

To access the SGM: Signaling Gateway Mated Pairs Details page, click the signaling gateway mated pair name on the SGM: Signaling Gateway Mated Pairs Status page.

You can sort the Signaling Gateway Mated Pairs Details table based on the information in any column. See the “Resizing, Sorting, and Hiding Table Columns” section on page 3-279 for more details.

The SGM: Signaling Gateway Mated Pairs Details page displays the following information:




• SGMP Name—Name of the signaling gateway mated pair. To see detailed information for the signaling gateway mated pair, click the signaling gateway mated pair name.

• Status—Current status of the signaling gateway mated pair, with a color-coded background. Possible values are:

– Active (green)—The signaling gateway mated pair is available and application traffic is active.

– Deleted (red)—The signaling gateway mated pair has been deleted from the SGM database.

– Down (red)—The signaling gateway mated pair is not available.

– Inactive (red)—The signaling gateway mated pair is available, but application traffic has stopped.

– Shutdown (blue)—An administrator has forced the signaling gateway mated pair to an unavailable state.


78-15589-01


– Unknown (red)—SGM cannot determine the current status of the signaling gateway mated pair.

– Warning (yellow)—The signaling gateway mated pair is Active, but some underlying facility is not fully functional.

• Node—Name of the node associated with the signaling gateway mated pair. To see detailed information for the node, click the node name.

• Signaling Point—Name of the signaling point associated with the signaling gateway mated pair. To see detailed information for the signaling point, click the signaling point name.

• Instance Status—Current status of the protocol associated with the signaling gateway mated pair, with a color-coded background. Possible values are:




• Congestion—Indicates whether there is congestion on the signaling gateway mated pair. A signaling gateway mated pair is congested if it has too many packets waiting to be sent. This condition could be caused by the failure of an element in your network.


• QoS—Quality of service (QoS) class of the signaling gateway mated pair.

• Passive—Indicates whether the signaling gateway can initiate the connection with the mate. Possible values are:

– True—The signaling gateway cannot initiate the connection. The mate must initiate the connection.

– False—The signaling gateway can initiate the connection.

• Config Local Port—Local port number that was configured for the signaling gateway mated pair.

• Local Port—Local port number that is currently in use for the signaling gateway mated pair.


78-15589-01


• Config Remote Port—Remote port number that was configured for the signaling gateway mated pair.

• Remote Port—Remote port number that is currently in use for the signaling gateway mated pair.

• Note—Note associated with this signaling gateway mated pair. If there is no note associated with this signaling gateway mated pair, this field is blank.

• Note Timestamp—Date and time the note associated with this signaling gateway mated pair was last updated. If there is no note associated with this signaling gateway mated pair, this field is blank.

Viewing Status Change and SNMP Trap MessagesSGM enables you to view the following status change and SNMP trap messages:

• Viewing Status Change and SNMP Trap Messages for SGM, page 7-86

• Viewing Status Change Messages for SGM, page 7-90

• Viewing SNMP Trap Messages for SGM, page 7-93

• Viewing All Archived Status Change and SNMP Trap Messages, page 7-96

• Modifying Network Status Message Colors, page 7-96

Viewing Status Change and SNMP Trap Messages for SGM

The Network Status: Last X Status Change and Trap Messages page displays status change messages and SNMP trap messages in the SGM network log.

To access the Network Status: Last X Status Change and Trap Messages page and display all status change and trap messages, use one of the following procedures:

• Select View> Event History > Status and Trap Messages from the SGM Main Menu.

• Select Status & SNMP Trap Messages from the SGM Server Home Page.

To access the Network Status: Last X Status Change and Trap Messages page and display status change and trap messages for a specific signaling point, signaling point, linkset, or event, right-click a signaling point, signaling point, linkset, or event in a window, then select Event History > Status and Trap Messages from the right-click menu.


78-15589-01


SGM displays the Network Status: Last X Status Change and Trap Messages page (Figure 7-10).

Figure 7-10 Network Status: Last X Status Change and Trap Messages Page

The Network Status: Last X Status Change and Trap Messages page displays the following information for each message:

• Severity (in header)—Message severity currently being displayed.


• Timestamp (in header)—Date and time the information on the page was last updated by SGM.



• Type—Type of message:

– Status—Status change message

– Trap—SNMP trap message



78-15589-01


To sort the messages by time, type, or alphabetically by message text, click the Time, Type, or Message header.

SGM enables you to modify the way information is presented in the Network Status: Last X Status Change and Trap Messages page:


















78-15589-01












By default, SGM displays status change and SNMP trap messages of all types on the Network Status: Last X Status Change and Trap Messages page. However, menu options are provided that enable you to display only messages of a specific type on the page. To display only messages of a specific type, select one of the following options:

• Admin—Displays only administrative messages. SGM displays administrative messages with a cyan background.

• Error—Displays only error messages. SGM displays error messages with a coral background.

• Warning—Displays only warning messages. SGM displays warning messages with a yellow background.

• Normal—Displays only normal messages. SGM displays normal messages with a light green background.

• Unclassified—Displays only messages that do not fall into one of the above classifications. SGM displays unclassified messages with a white background.

• All—Displays all status change and SNMP trap messages.


78-15589-01


The list of messages displayed in the Last Status Change and Trap Messages table is continually refreshed as new messages are received.

• To pause the message display, select Pause from the menu bar.

• To resume the message display, select Resume from the menu bar.

Viewing Status Change Messages for SGM

The Network Status: Last X Status Change Messages page displays status change messages in the SGM network log.

To access the Network Status: Last X Status Change Messages page and display all status change messages, use one of the following procedures:

• Select View> Event History > Status Changes from the SGM Main Menu.

• Select Status Change Messages from the SGM Server Home Page.

To access the Network Status: Last X Status Change Messages page and display status change messages for a specific signaling point, signaling point, linkset, or event, right-click a signaling point, signaling point, linkset, or event in a window, then select Event History> Status Change Messages from the right-click menu.

The Network Status: Last X Status Change Messages page displays the following information for each message:







To sort the messages by time or alphabetically by message text, click the Time or Message header.


78-15589-01


SGM enables you to modify the way information is presented in the Network Status: Last X Status Change Messages page:


















78-15589-01












By default, SGM displays status change messages of all types on the Network Status: Last X Status Change Messages page. However, menu options are provided that enable you to display only messages of a specific type on the page. To display only messages of a specific type, select one of the following options:

• Admin—Displays only administrative messages. SGM displays administrative messages with a cyan background.

• Error—Displays only error messages. SGM displays error messages with a coral background.

• Warning—Displays only warning messages. SGM displays warning messages with a yellow background.

• Normal—Displays only normal messages. SGM displays normal messages with a light green background.

• Unclassified—Displays only messages that do not fall into one of the above classifications. SGM displays unclassified messages with a white background.

• All—Displays all status change messages.


78-15589-01


The list of messages displayed in the Last Status Change Messages table is continually refreshed as new messages are received.



Viewing SNMP Trap Messages for SGM

The Network Status: Last X SNMP Trap Messages page displays SNMP trap messages in the SGM network log.

To access the Network Status: Last X SNMP Trap Messages page and display all SNMP trap messages, use one of the following procedures:

• Select View> Event History > SNMP Traps from the SGM Main Menu.

• Select SNMP Trap Messages from the SGM Server Home Page.

To access the Network Status: Last X SNMP Trap Messages page and display SNMP trap messages for a specific signaling point, signaling point, linkset, or event, right-click a signaling point, signaling point, linkset, or event in a window, then select Event History > SNMP Trap Messages from the right-click menu.

The Network Status: Last X SNMP Trap Messages page displays the following information for each message:






• Node—Node that sent the trap. To see only SNMP trap messages for that signaling point, click the signaling point name.




78-15589-01


SGM enables you to modify the way information is presented in the Network Status: Last X SNMP Trap Messages page:


















78-15589-01












By default, SGM displays SNMP trap messages of all types on the Network Status: Last X SNMP Trap Messages page. However, menu options are provided that enable you to display only messages of a specific type on the page. To display only messages of a specific type, select one of the following options:

• Admin—Displays SNMP trap administrative messages. SGM displays administrative messages with a cyan background.

• Error—Displays SNMP trap error messages. SGM displays error messages with a coral background.

• Warning—Displays SNMP trap warning messages. SGM displays warning messages with a yellow background.

• Normal—Displays normal SNMP trap messages. SGM displays normal messages with a light green background.

• Unclassified—Displays SNMP trap messages that do not fall into one of the above classifications. SGM displays unclassified messages with a white background.

• All—Displays all SNMP trap messages.


78-15589-01


The list of messages displayed in the Last SNMP Trap Messages table is continually refreshed as new messages are received.



Viewing All Archived Status Change and SNMP Trap Messages

The Network Status Daily Archives: Status and SNMP Trap Messages page displays all archived status change and SNMP trap messages.

To access the Network Status Daily Archives: Status and SNMP Trap Messages page, use one of the following procedures:

• Select View> Event History > Network Status Archives from the SGM Main Menu.

• Select Network Status Archives from the SGM Server Home Page.

On the Network Status Daily Archives: Status and SNMP Trap Messages page, messages are archived by time stamp. SGM automatically archives the messages at 11:59 PM each night; each archived file contains messages from a single calendar day.

To view archived messages, click a time stamp. SGM displays the message archive, with columns and features as described in the “Viewing Status Change and SNMP Trap Messages for SGM” section on page 7-86.

Modifying Network Status Message Colors

By default, SGM displays network status messages with the following background colors:

• Admin—cyan background

• Error—coral background

• Normal—light green background

• Warning—yellow background

• Unclassified—white background

For information about customizing the background colors for network status messages, see the “Modifying the SGM Event Configuration File (Solaris Only)” section on page 5-26.


78-15589-01


Viewing Network Status MetricsThe Network Status Messages: Messages page displays a number of metrics for SGM, based on the number of messages of each type and severity received by SGM.

To access the Network Status Messages: Messages page and display all metrics, use one of the following procedures:

• Select View> Event History > Network Status Metrics from the SGM Main Menu.

• Select Network Status Metrics from the SGM Server Home Page.

To access the Network Status Messages: Messages page and display metrics for a specific signaling point, signaling point, linkset, or event, right-click a signaling point, signaling point, linkset, or event in a window, then select Event History> Network Status Metrics from the right-click menu.

The Network Status Messages: Messages page displays both raw numbers and calculated metrics for the following information:

• Total number of messages of each type and severity received by SGM.

• Messages sorted by severity.

• Messages sorted by type (status change messages and SNMP trap messages)

• Status change messages sorted by severity.

• SNMP trap messages sorted by severity.

• Names of all files processed by SGM.

• Beginning and ending date and time for the displayed metrics.

Viewing Network Statistics Reports for Links and LinksetsYou can view the following SGM network statistics reports for links and linksets from the SGM Server Home Page:

• Linkset Statistics Hourly Summary Reports

• Linkset Statistics Daily Summary Reports

• Link Statistics Hourly Summary Reports

• Link Statistics Daily Summary Reports


78-15589-01


• Five Day Link Utilization Report

• Hourly Network Statistics Export Files

• Daily Network Statistics Export Files

• Rolling Network Statistics Export Files

• Custom Network Statistics Export Files

For more information, see the “Viewing SGM Network Statistics Reports” section on page 3-343.

Viewing Accounting Statistics ReportsYou can view the following SGM accounting statistics reports from the SGM Server Home Page:

• Accounting Statistics Daily Detail Reports

• Daily Accounting Statistics Export Files

• Custom Network Statistics Export Files

For more information, see the “Viewing SGM Accounting Statistics Reports” section on page 3-364.

Viewing Point Code Inventory ReportsYou can view the following SGM point code inventory reports from the SGM Server Home Page:

• Current Point Code Inventory

• Daily Point Code Inventory Daily Reports

• Daily Point Code Inventory Export Files

For more information, see the “Viewing SGM Point Code Inventory Reports” section on page 3-390.


78-15589-01

Chapter 7 Accessing SGM Data from a Web BrowserViewing SGM System Messages

Viewing Statistics Report LogsYou can view the following SGM network and accounting statistics report logs from the SGM Server Home Page:

• SGM System Reports Logs

• SGM System Report Parameters and Timers

For more information, see the “Viewing SGM Statistics Reports Logs” section on page 3-394.

Viewing SGM System MessagesYou can view the following SGM system messages from the SGM Server Home Page.

Note These messages are all related to the SGM system itself, not to your network.

• Viewing SGM Error Messages, page 7-100

• Viewing SGM Info Messages, page 7-101

• Viewing SGM Action Messages, page 7-102

• Viewing SGM Trace Messages, page 7-105

• Viewing SGM Debug Messages, page 7-106

• Viewing SGM Dump Messages, page 7-107

• Viewing SGM SNMP Messages, page 7-108

• Viewing All Current SGM Messages, page 7-109

• Viewing All Archived SGM Messages, page 7-110

• Viewing the SGM System Console Log, page 7-110

• Viewing All Archived SGM System Console Log Messages, page 7-111

• Viewing the SGM System Command Log, page 7-111

• Viewing the SGM System Event Automation Log, page 7-112

• Viewing the SGM System Security Log, page 7-113


78-15589-01


• Viewing the SGM System Web Server Error Log, page 7-114

• Viewing the SGM System Web Access Log, page 7-115

Viewing SGM Error MessagesThe System Messages: Last X Error Messages page displays error messages stored in the ITP system log. These messages can be useful when diagnosing and correcting SGM operational problems.

To access the System Messages: Last X Error Messages page, use one of the following procedures:

• Select System Error Messages from the SGM Server Home Page.

• Select Error from the menu bar of any SGM System Messages Web page.

The Last Error Messages table provides the following information for each message:

• Period (in header)—Collection period of the table, such as Since Server Restart.


• Index—Message number, assigned to the message by SGM.

• Time—Date and time the message was logged. To sort the messages by time, click the Time header.

• Source—Source for the message, with the format process.host.id, where:

– process is the process that logged the message.

– host is the host name of the process that logged the message.

– id is an SGM ID that uniquely identifies the process that logged the message, in the event that there are two or more clients running on the same device, connected to the same SGM server.

• Task—Task, or thread, that logged the message.

• Message—Text of the message. To sort the messages alphabetically by message text, click the Message header.



78-15589-01


Viewing SGM Info MessagesThe System Messages: Last X Info Messages page displays informational messages stored in the ITP system log. These messages can be useful when diagnosing and correcting SGM operational problems.

To access the System Messages: Last X Info Messages page, select Info from the menu bar of any SGM System Messages Web page.

The Last Info Messages table provides the following information for each message:




• Time—Date and time the message was logged. To sort the messages by time, click the Time header.






• Message—Text of the message. To sort the messages alphabetically by message text, click the Message header.



78-15589-01


Viewing SGM Action MessagesThe System Messages: Last X Action Messages page displays action messages stored in the ITP system log. These messages can be useful when diagnosing and correcting SGM operational problems, and when monitoring audit trails of user actions.

To access the System Messages: Last X Action Messages page, use one of the following procedures:

• Select View> User Audit > User Actions from the SGM Main Menu.

• Select User Actions from the SGM Server Home Page.

• Select Action from the menu bar of any SGM System Messages Web page.

SGM displays the System Messages: Last X Action Messages page (Figure 7-11).

Figure 7-11 System Messages: Last X Action Messages Page


78-15589-01


The Last Action Messages table provides the following information for each message:





• Class—Class of the message. Possible classes are:


– Delete—Deletion event, such as the deletion of a signaling point, signaling point, linkset, or file.


– Edit—Edit event. A user has edited an event, linkset, or signaling point.

– Ignore—Ignore event. A user has flagged a link or linkset as Ignored.








To sort the messages by time, class, or alphabetically by message text, click the Time, Class, or Message header.


78-15589-01


By default, SGM displays action messages of all classes on the System Messages: Last X Action Messages page. However, menu options are provided that enable you to display only messages of a specific class on the page. To display only messages of a specific class, select one of the following options:

• All—Opens the System Messages: Last X Action Messages Web page, which displays all action messages.

• Create—Opens the System Messages: Last X Action: Create Messages Web page, which displays only Create action messages.

• Delete—Opens the System Messages: Last X Action: Delete Messages Web page, which displays only Delete action messages.

• Discover—Opens the System Messages: Last X Action: Discover Messages Web page, which displays only Discover action messages.

• Edit—Opens the System Messages: Last X Action: Edit Messages Web page, which displays only Edit action messages.

• Ignore—Opens the System Messages: Last X Action: Ignore Messages Web page, which displays only Ignore action messages.

• Login—Opens the System Messages: Last X Action: Login Messages Web page, which displays only Login action messages.

• OverWrite—Opens the System Messages: Last X Action: OverWrite Messages Web page, which displays only OverWrite action messages.

• Poll—Opens the System Messages: Last X Action: Poll Messages Web page, which displays only Poll action messages.

• Purge—Opens the System Messages: Last X Action: Purge Messages Web page, which displays only Purge action messages.


78-15589-01


Viewing SGM Trace MessagesThe System Messages: Last X Trace Messages page displays trace messages stored in the ITP system log. These messages can be useful when diagnosing and correcting SGM operational problems.

To access the System Messages: Last X Trace Messages page, select Trace from the menu bar of any SGM System Messages Web page.

The Last Trace Messages table provides the following information for each message:












78-15589-01


Viewing SGM Debug MessagesThe System Messages: Last X Debug Messages page displays debug messages stored in the ITP system log. These messages can be useful when diagnosing and correcting SGM operational problems.

To access the System Messages: Last X Debug Messages page, select Debug from the menu bar of any SGM System Messages Web page.

Note The Debug option is displayed only when enabled at the request of Cisco TAC.

The Last Debug Messages table provides the following information for each message:












78-15589-01


Viewing SGM Dump MessagesThe System Messages: Last X Dump Messages page displays dump messages stored in the ITP system log. These messages can be useful when diagnosing and correcting SGM operational problems.

To access the System Messages: Last X Dump Messages page, select Dump from the menu bar of any SGM System Messages Web page.

Note The Dump option is displayed only when enabled at the request of Cisco TAC.

The Last Dump Messages table provides the following information for each message:












78-15589-01


Viewing SGM SNMP MessagesThe System Messages: Last X SNMP Messages page displays SNMP messages stored in the ITP system log. These messages can be useful when diagnosing and correcting SGM operational problems.

Note These are not SNMP trap messages. These are debugging messages from internal, low-level SNMP encoding and decoding routines.

To access the System Messages: Last X SNMP Messages page, select SNMP from the menu bar of any SGM System Messages Web page.

Note The SNMP option is displayed only when enabled at the request of Cisco TAC.

The Last SNMP Messages table provides the following information for each message:












78-15589-01


Viewing All Current SGM MessagesThe System Messages: Last X All Messages page displays all current messages in the ITP system log.

To access the System Messages: Last X All Messages page, select All from the menu bar of any SGM System Messages Web page.

The Last All Messages table provides the following information for each message:





• Type—Type of message. Possible types are:

– Action

– Debug

– Dump

– Error

– Info

– SNMP

– Trace








78-15589-01


Viewing All Archived SGM MessagesThe System Message Archives: All Messages page displays all archived messages in the ITP system logs, including error messages, informational messages, trace messages, debug messages, dump messages, and SNMP messages.

To access the System Message Archives: All Messages page, use one of the following procedures:

• Select System Message Archives from the SGM Server Home Page.

• Select Archives from the menu bar of any SGM System Messages Web page.

On the System Message Archives: All Messages page, messages are archived by time stamp. Each archived file contains all SGM system messages for a single session for the server to which you are connected, and which is currently running the SGM server. (If you restart the server, SGM creates a new file.)

To view archived messages, click a time stamp. SGM displays the archived messages.

Viewing the SGM System Console LogThe SGM System Console Log page displays the contents of the SGM system console log file for the server to which you are connected, and which is currently running the SGM server. The console log file contains unexpected error and warning messages from the SGM server, such as those that might occur if the SGM server cannot start.

To access the SGM System Console Log page, use one of the following procedures:

• Select System Console Log from the SGM Server Home Page.

• Select Console from the menu bar of any SGM System Messages Web page.


78-15589-01


Viewing All Archived SGM System Console Log MessagesThe Console Archives: All Messages page displays all archived SGM system console log messages for the server to which you are connected, and which is currently running the SGM server. The archived console logs contain unexpected error and warning messages from the SGM server, such as those that might occur if the SGM server cannot start.

To access the Console Archives: All Messages page, select Console Archives from the menu bar of any SGM System Messages Web page.

On the Console Archives: All Messages page, messages are archived by time stamp. Each archived file contains all SGM system console log messages for a single session for the server to which you are connected, and which is currently running the SGM server. (If you restart the server, SGM creates a new file.)

To view archived messages, click a time stamp. SGM displays the archived messages.

Viewing the SGM System Command LogThe SGM System Command Log: Last X Commands page displays the contents of the SGM system command log file for the server to which you are connected, and which is currently running the SGM server. The system command log lists all sgm commands that have been entered for the SGM server, the time each command was entered, and the user who entered the command.

To access the SGM System Command Log: Last X Commands page, use one of the following procedures:

• Select View> User Audit > Command Log from the SGM Main Menu.

• Select System Command Log from the SGM Server Home Page.

• Select Command Log from the menu bar of any SGM System Messages Web page.

SGM displays the SGM System Command Log: Last X Commands page (Figure 7-12).


78-15589-01


Figure 7-12 SGM Command Page: Last X Commands Page

The Last Commands table provides the following information for each command:

• Last Updated (in header)—Date and time the information on the page was last updated by SGM.

• Row—Command number, assigned to the command by SGM.

• Time—Date and time the command was entered.

• User—User who entered the command.

• Command—Text of the command.

To sort the commands by time, by user, or alphabetically by command text, click the Time, User, or Command header.

Viewing the SGM System Event Automation LogThe SGM System Event Automation Log page displays the contents of the SGM system event automation log file for the server to which you are connected, and which is currently running the SGM server. The system event automation log lists all messages generated by scripts launched by event automation.


78-15589-01


The default path and filename for the system event automation log file is /opt/CSCOsgm/logs/eventAutomationLog.txt. If you installed SGM in a directory other than /opt, then the system event automation log file is located in that directory.

To access the SGM System Event Automation Log page, use one of the following procedures:

• Select System Event Automation Log from the SGM Server Home Page.

• Select EventAuto from the menu bar of any SGM System Messages Web page.

Viewing the SGM System Security LogThe SGM System Security Log: Last X Entries page displays the contents of the SGM system security log file for the server to which you are connected, and which is currently running the SGM server. The system security log lists all SGM security events that have occurred for the SGM server, the time each event occurred, the user and command that triggered the event, and the text of any associated message.


To access the SGM System Security Log: Last X Entries page, use one of the following procedures:

• Select View> User Audit > Security Log from the SGM Main Menu.

• Select System Security Log from the SGM Server Home Page.

• Select Security Log from the menu bar of any SGM System Messages Web page.


78-15589-01


The Last Security Entries table provides the following information for each entry:


• Row—Entry number, assigned to the entry by SGM.

• Time—Date and time the security event occurred.

• User—User who triggered the security event.

• Message—Text of the security event message.

• Command—Text of the command that triggered the security event.

To sort the entries by time, user, or alphabetically by message or command text, click the Time, User, Message, or Command header.

Viewing the SGM System Web Server Error LogThe SGM System Web Server Error Log: Last X Messages page displays the contents of the SGM system Web server error log file for the server to which you are connected, and which is currently running the SGM server. The system Web server error log lists all SGM system Web error messages that have been logged for the SGM Web server.

To access the SGM System Web Server Error Log: Last X Messages page, select Web Server Errors from the SGM Server Home Page, or enter the sgm weberrorlog command. (You must be logged in as the root user or as a super user to use the sgm weberrorlog command.)

The SGM System Web Server Error Log: Last X Messages page provides the following information:



• Message—Text of the Web server error message.


78-15589-01

Chapter 7 Accessing SGM Data from a Web BrowserViewing System Status Information for SGM

Viewing the SGM System Web Access LogThe SGM System Web Access Log: Last X Messages page displays the contents of the SGM system Web access log file for the server to which you are connected, and which is currently running the SGM server. The system Web access log lists all SGM system Web access messages that have been logged for the SGM server. This provides an audit trail of all access to the SGM server via the Web interface.

To access the SGM System Web Access Log: Last X Messages page, select Web Access Log from the SGM Server Home Page, or enter the sgm webaccesslog command. (You must be logged in as the root user or as a super user to use the sgm webaccesslog command.)

The SGM System Web Access Log: Last X Messages page provides the following information:



• Message—Text of the Web error message.

Viewing System Status Information for SGMYou can view the following SGM system status information from the SGM Server Home Page:

• Viewing Status Information for SGM, page 7-116

• Viewing Version Information for SGM, page 7-116

• Viewing SGM Client Information, page 7-116

• Viewing SGM User Account Information, page 7-116

• Viewing SGM Object Counts, page 7-118

• Viewing the Troubleshooting Log for SGM (Solaris Only), page 7-119


78-15589-01


Viewing Status Information for SGMThe SGM System Status page displays the status of all SGM servers, local clients, and processes. To access the SGM System Status page, select System Status. (SGM might take a few seconds to display this page.)

Viewing Version Information for SGMThe SGM System Versions page displays version information for all SGM servers, clients, and processes. To access the SGM System Versions page, select System Versions. (SGM might take a few seconds to display this page.)

Viewing SGM Client InformationThe SGM System Connected Clients page lists all SGM clients that are currently connected to the SGM server. It also lists all Solaris users that are logged in to the SGM server.

To access the SGM System Connected Clients page, use one of the following procedures:

• Select View> User Audit > Connected Clients from the SGM Main Menu.

• Select Connected Clients from the SGM Server Home Page.

• Select Clients from the menu bar of any SGM System Status Web page.

Viewing SGM User Account InformationThe SGM User Accounts page displays information about all user accounts that have been defined for the SGM server. If no user accounts have been defined, SGM displays the message, “User Database is Empty.”

To access the SGM User Accounts page, use one of the following procedures:

• Select View> User Audit > User Accounts from the SGM Main Menu.

• Select System User Accounts from the SGM Server Home Page.

• Select Users from the menu bar of any SGM System Status Web page.


78-15589-01


The SGM User Accounts page provides the following information:

• Server Name (in header)—Name of the SGM server for which user accounts are being displayed.

• User—SGM user for whom a User-Based Access account has been set up.

• Last Login—Date and time the user last logged in to SGM.

• Level Name—Authentication level for the user. Valid levels are:

– Basic User

– Power User

– Network Operator

– Network Administrator

– System Administrator

• Level Number—Authentication level for the user, expressed as a number. Valid levels are:

– 1—Basic User

– 2—Power User

– 3—Network Operator

– 4—Network Administrator

– 5—System Administrator


78-15589-01


• Status—Current status of the user’s account. Valid status settings are:

– Account Enabled—The account has been enabled and is functioning normally.

– Account Disabled—The account has been disabled for one of the following reasons:

– A System Administrator disabled the account. See the descriptions of the sgm disablepass and sgm disableuser commands in the “SGM Command Reference” for more information.

– SGM disabled the account as a result of too many failed attempts to log in using the account. See the description of the sgm badlogindisable command in the “SGM Command Reference” for more information.

– SGM disabled the account because it was inactive for too many days. See the description of the sgm inactiveuserdays command in the “SGM Command Reference” for more information.

To sort the SGM User Accounts page based on the contents of any column, click the column header.

Viewing SGM Object CountsThe SGM Object Counts page displays counts of objects in the SGM database, including nodes, signaling points, linksets, links, and so on.

To access the SGM Object Counts page, select System Object Counts from the SGM Server Home Page.

The SGM Object Counts page displays the following counts:

• Nodes—Number of nodes that are in the following states: Active, Warning, Unmanaged, Unknown, and Total.

• SigPoints—Number of signaling points that are in the following states: Active, Warning, Unmanaged, Unknown, and Total.

• Linksets—Number of linksets that are in the following states: Active, Warning, Unknown, Shutdown, Failed, Unavailable, Inactive, and Total.

• Links—Number of links that are in the following states: Active, Warning, Unknown, Shutdown, Failed, Unavailable, Inactive, Inhibited, InhibitLoc, InhibitRem, Blocked, and Total.


78-15589-01


• Application Servers—Number of application servers that are in the following states: Active, Warning, Unknown, Down, Pending, and Total.

• AS Processes—Number of application server processes that are in the following states: Active, Warning, Unmanaged, Unknown, Down, and Total.

• ASP Associations—Number of application server process associations that are in the following states: Active, Warning, Unknown, Down, and Total.

• SG Mated Pairs—Number of signaling gateway mated pairs that are in the following states: Active, Warning, Inactive, Unknown, Down, and Total.

Viewing the Troubleshooting Log for SGM (Solaris Only)The SGM System Troubleshooting page displays the troubleshooting information that is stored in the /opt/CSCOsgm/tmp/cisco_sgm_tshoot.log file on the SGM server. This log, which is updated each time the SGM System Troubleshooting page is accessed or the sgm tac command is run, contains information that might be requested by Cisco customer support personnel.

To access the SGM System Troubleshooting page, select System Troubleshooting from the SGM Server Home Page, or from the Web page menu bar, if shown.

Note SGM might take several minutes to create and display the troubleshooting log, and the resulting log might be several MB, depending on the size of the network and system logs.


78-15589-01

Chapter 7 Accessing SGM Data from a Web BrowserViewing System Data Files for SGM

Viewing System Data Files for SGMYou can view the following SGM system data files from the SGM Server Home Page:

• ITP SNMP MIBs—Displays a list of the MIBs on the server to which you are connected, and which is currently running the SGM server. To access the ITP SNMP MIBs page, select ITP MIBs from the menu bar of any SGM System Files Web Page.

• SGM System Files: Discovery Seeds—Displays a list of the seed files that have been created on this SGM server. To access the SGM System Files: Discovery Seeds page, select Discovery Seeds from the SGM Server Home Page.

• SGM System Files: GTT—Displays a list of the GTT files that have been created on this SGM server. To access the SGM System Files: Global Title Tables page, select Global Title Tables from the SGM Server Home Page. Click a GTT file name to view its contents.

• SGM System Files: Network Views—Displays a list of the network view files that have been created on this SGM server. To access the SGM System Files: Network Views page, select Views from the menu bar of any SGM System Files Web Page.

• SGM System Files: Notes—Displays a list of the note files that have been created on this SGM server. The notes are listed by the name of the signaling point, signaling point, or linkset, or by the internal ID of the event. To access the SGM System Files: Notes page, select Notes from the SGM Server Home Page. Click a signaling point name, linkset name, or event ID to view the contents of the note.

• SGM System Files: Routes—Displays a list of the route table files that have been created on this SGM server. To access the SGM System Files: Routes page, select DPC Route Tables from the SGM Server Home Page. Click a route table file name to view its contents.

In the route table file, linksets are listed with the format Lnumber:name, where:

– L indicates that the line is for a linkset.

– number is the linkset number.

– name is the name of the linkset.


78-15589-01

Chapter 7 Accessing SGM Data from a Web BrowserViewing System Information for SGM

In the route table file, routes are listed with the format Rcode:bits:Inumber:cost:qos, where:

– R indicates that the line is for a route.

– code is the destination point code in hexadecimal format.

– bits is the number of bits in the mask, in hexadecimal format. For example, e indicates that there are 14 bits in the mask (7.255.7 = 111.11111111.111).

– I indicates the information for the route.

– number is the linkset number to use, which matches one of the linkset numbers from the above list.

– cost is the cost or priority of the route to the destination, relative to other routes. The valid costs range from 1 (lowest cost and highest priority) through 9 (highest cost and lowest priority).

– qos is the quality of service (QoS) class of the route, as configured by the network administrator. A value of ff means the QoS is not set.

• SGM System Files: Server Event Automation Sounds—Displays a list of event automation sound files on this SGM server. To access the SGM System Files: Server Event Automation Sounds page, select Sounds from the menu bar of any SGM System Files Web Page.

Viewing System Information for SGMYou can view the following SGM system information from the SGM Server Home Page:

• SGM Install Log—Displays the contents of the SGM system installation log. The installation log contains messages and other information recorded during installation, which can be useful when troubleshooting problems. To access the SGM System Install Log page, select System Install Log.

• SGM ITP IOS README—Displays the versions of IOS with which SGM is compatible. To access the SGM System ITP IOS README page, select System ITP IOS README from the SGM Server Home Page.


78-15589-01

Chapter 7 Accessing SGM Data from a Web BrowserViewing the SGM Technical Documentation

• SGM Process Services—Displays the processes that are started and managed by the SGM Process Manager. To access the SGM System Process Services page, select System Process Services, or enter the sgm services command. (You must be logged in as the root user or as a super user to use the sgm services command.)

• SGM README—Contains late-breaking information about SGM that might not be found in the other product documentation. To access the SGM System README page, select System README.

• SGM Root Variables—Displays the contents of the /etc/CSCOsgm.sh file, which determines the root location of the SGM server and client installation. To access the SGM System Root Variables page, select System Root Variables, or enter the sgm rootvars command.

• SGM System Properties—Displays SGM server and client properties that control various SGM configuration parameters. To access the SGM System Properties page, select System Properties.

Viewing the SGM Technical DocumentationFrom the SGM Server Home Page, you can view the following SGM technical documentation:

• To access the Cisco Signaling Gateway Manager Help System, select Help Home Page.

• To view Frequently Asked Questions (FAQs) about SGM, select Frequently Asked Questions.

• To view the entire SGM Installation Guide as a PDF file on the Web, select Installation Guide.

• To view the entire SGM User Guide as a PDF file on the Web, select User Guide.

• To view the entire SGM Release Notes as a PDF file on the Web, select Release Notes.

• To view the syntax for every SGM command, select Output of sgm help command from the SGM Server Home Page.


78-15589-01

Chapter 7 Accessing SGM Data from a Web BrowserDownloading the SGM Client from the Web

Downloading the SGM Client from the WebYou can access the SGM client installation software for Linux, Solaris, and Windows from the SGM Server Home Page. This access is useful if you do not have the CD-ROM, or if you prefer to download the software using your Web browser. Once you have downloaded the SGM client installation software to your workstation, you must install the software on your local system.

For more information about installing the SGM client software using a Web server, see the “Installing SGM on Solaris” and “Installing SGM on Windows” chapters of the Cisco Signaling Gateway Manager Installation Guide.

• To access the SGM Client for Solaris page, select Download Solaris Client.

• To access the SGM Client for Windows page, select Download Windows Client.

• To access the SGM Client for Linux page, select Download Linux Client. (The SGM client for Linux is not a supported feature of SGM. Use it under advisement.)

Downloading the SGM Server’s SSL Certificate from the Web

If you have implemented Secure Sockets Layer (SSL) support in your SGM system, you can download the SGM server’s signed SSL certificate to all remote SGM clients that connect to the server using SSL.

To access the SGM Server SSL Certificate page, select Server SSL Certificate from the SGM Server Home Page.

For more information about downloading the certificate, or about enabling SSL in SGM, see the “Implementing SSL Support in SGM” section on page 4-24.


78-15589-01

Chapter 7 Accessing SGM Data from a Web BrowserAccessing Software Updates and Additional Information

Accessing Software Updates and Additional Information

You can access the following additional information about SGM from the SGM Server Home Page:

• To read Cisco literature associated with SGM, including product data sheets, Q and As, and helpful presentations, select SGM Home Page from the SGM Server Home Page.

• To view information about SGM or any other Cisco product available on Cisco.com (also known as Cisco Connection Online), use one of the following procedures:

– Select View> Cisco.com from the SGM Main Menu.

– Select Cisco Home Page from the SGM Server Home Page.

• To access the Network Management Software page, which includes the latest downloads for SGM, select Network Management Software Center from the SGM Server Home Page.

• To access software updates for SGM from Cisco.com for FTP, select Engineering Software Updates. The SGM Software Home page is displayed.

Displaying the ITP Home PageSGM enables you to display the home page of a selected ITP in a new Web browser window.

To view an ITP’s home page, right-click a signaling point in the Node or Topology window, then select ITP> Home Page from the right-click menu.


78-15589-01

Cisco S78-15589-01

A
P P E N D I X A SGM FAQs
This appendix provides answers to the following frequently asked questions about SGM:

• What is SGM?, page A-2

• Does SGM require any other NMS applications?, page A-2

• What workstation and network devices do I need to run SGM?, page A-3

• Can I run SGM on my Windows PC?, page A-3

• How do I install the SGM client?, page A-3

• What are the names of the MIBs used by SGM?, page A-3

• Why can’t my remote workstation access SGM on my local workstation?, page A-5

• What is a super user?, page A-5

• Why did SGM not discover all of my ITP nodes?, page A-5

• I moved the server on which I had installed SGM and now I can’t start the SGM client or server. Why?, page A-6

• How often does SGM poll the ITP nodes?, page A-7

• If I select the Clear Event Icon menu option, does that delete the event from the SGM database?, page A-8

• What does the asterisk (*) mean next to an SLC number?, page A-8

• How does “zoom in on an area” work in a topology map?, page A-8

• My server has multiple IP addresses and I can’t connect to the SGM server. How can I correct this problem?, page A-9

A-1ignaling Gateway Manager User Guide

Appendix A SGM FAQsWhat is SGM?

• What does this message mean: DataModelMediatorService: Could not find service in RMI registry or the RMI Registry may be down., page A-9

• What does this message mean: MessageLoggerProxy:setMessageLogger(): Could not resolve., page A-10

• Will the SGM server processes restart automatically after a system reboot?, page A-10

• Some of my SGM windows are showing up with small, unusable text entry fields. How can I correct this?, page A-11

• Sometimes my SGM display seems to lock up. Why?, page A-11

• After a failed uninstall of the Windows client, I’m prompted to uninstall again, but the procedure does not work. Why?, page A-12

• Why do I see strange character strings when I install SGM?, page A-13

• Why doesn’t Netscape launch when I select a Web page menu option from the SGM Main Menu?, page A-13

What is SGM?SGM provides a powerful, easy-to-use solution that enables network administrators to manage and troubleshoot IP Transfer Point (ITP) networks. For a more detailed description of SGM, see the “What is SGM?” section on page 1-2.

Does SGM require any other NMS applications?SGM is functionally a standalone product and does not require any other products. However, you can integrate SGM with other products to provide added value.

For example, you can integrate SGM with CiscoWorks2000, which provides access to the full suite of CiscoWorks2000 products, including the Device Center, the CiscoView Element Manager, Resource Manager Essentials (RME), the Internetwork Performance Monitor (IPM), and the Access Control List Manager.

You can also integrate SGM with the HP OpenView SNMP manager to enable SGM to receive traps via HP OpenView.

A-2Cisco Signaling Gateway Manager User Guide

78-15589-01

Appendix A SGM FAQsWhat workstation and network devices do I need to run SGM?

What workstation and network devices do I need to run SGM?

SGM comprises two distinct pieces of functionality.

• The SGM server application runs on Solaris only.

• The SGM client application, including the user interface, runs on Solaris, Windows 2000 Professional, and Windows XP Professional. For Solaris, the SGM client can run on the same system as the SGM server, or on a different system.

For further hardware and software requirements, see the “Preparing to Install SGM” chapter of the Cisco Signaling Gateway Manager Installation Guide.

Can I run SGM on my Windows PC?You can run the SGM client on Windows 2000 Professional or Windows XP Professional on your PC. However, the SGM server must run on a Solaris system.

How do I install the SGM client?You can install the SGM client either from the CD distributed with SGM, or by using a Web browser to download the SGM client from an SGM server. See the Cisco Signaling Gateway Manager Installation Guide for full details.

What are the names of the MIBs used by SGM?SGM configures and queries the following MIBs:

• MIB-II mib (RFC1213-MIB.my): (1.3.6.1.2.1)

• CISCO-IETF-SCTP-MIB.my: (1.3.6.1.4.1.9.10.75)

• CISCO-IETF-SCTP-EXT-MIB.my: (1.3.6.1.4.1.9.10.76)

• CISCO-ITP-ACL-MIB.my: (1.3.6.1.4.1.9.9.227)


78-15589-01

Appendix A SGM FAQsWhat are the names of the MIBs used by SGM?

• CISCO-ITP-ACT-MIB.my: (1.3.6.1.4.1.9.9.230)

• CISCO-ITP-GACT-MIB.my: (1.3.6.1.4.1.9.9.333)

• CISCO-ITP-GRT-MIB.my: (1.3.6.1.4.1.9.9.334)

• CISCO-ITP-GSCCP-MIB.my: (1.3.6.1.4.1.9.9.335)

• CISCO-ITP-GSP-MIB.my: (1.3.6.1.4.1.9.9.336)

• CISCO-ITP-GSP2-MIB.my: (1.3.6.1.4.1.9.9.332)

• CISCO-ITP-RT-MIB.my: (1.3.6.1.4.1.9.9.228)

• CISCO-ITP-SCCP-MIB.my: (1.3.6.1.4.1.9.9.233)

• CISCO-ITP-SP-MIB.my: (1.3.6.1.4.1.9.9.232)

• CISCO-ITP-SP2-MIB.my: (1.3.6.1.4.1.9.9.248)

• CISCO-ITP-TC-MIB.my: (1.3.6.1.4.1.9.9.231)

• CISCO-ITP-XUA-MIB.my: (1.3.6.1.4.1.9.9.253)

• CISCO-PROCESS-MIB.my: (1.3.6.1.4.1.9.9.109)

• CISCO-SYSLOG-MIB.my: (1.3.6.1.4.1.9.9.41)

You can obtain the latest versions of these MIBs from one of the following locations:

• The Zip file mibs.zip, located at the top of the SGM CD Image, contains these MIBs.

• You can download these MIBs from the Cisco Website:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

For more information about these MIBs, see the “SGM MIB Reference” section on page C-1.


78-15589-01


Appendix A SGM FAQsWhy can’t my remote workstation access SGM on my local workstation?

Why can’t my remote workstation access SGM on my local workstation?

Keep in mind that performance is better if you access SGM by installing the SGM client on the remote workstation.

However, if you want to enable a remote Solaris workstation to access SGM on a local workstation, enter the xhost + remote_workstation UNIX command on your local workstation, where remote_workstation is the remote device you are enabling to access your local workstation.

To enable a remote Windows workstation to access SGM on a local workstation, you can use an X-Window system emulator such as eXceed or Reflection X, but be aware that there may be display problems. For example, the window borders might disappear, or the keyboard focus might be missing.

What is a super user?A super user is an SGM user who has been enabled to perform most of the SGM functions that otherwise require the user to be logged in as the root user.

For a complete description of the functions that a super user can and cannot perform, as well as instructions for enabling a super user, see the “Specifying a Super User (Solaris Only)” section on page 4-22.

Why did SGM not discover all of my ITP nodes?After you discover the network, examine the Discovered Nodes table to verify that SGM discovered all of the nodes in the network. If you suspect that SGM did not discover all of the nodes, verify the following conditions:

• Verify that the SGM server can ping the nodes.

• Verify that the nodes are running ITP IOS images that are compatible with the SGM server.

• Verify that the SNMP is enabled on the nodes.


78-15589-01

Appendix A SGM FAQsI moved the server on which I had installed SGM and now I can’t start the SGM client or server. Why?

• Verify that SGM is configured with the correct SNMP community name. See the “Configuring SNMP” section on page 3-2 for details.

• Verify that the missing nodes are connected to the seed nodes by SCTP connections, not just serial connections.

• Verify that you selected Entire Network when you ran Discovery. If you suspect that you did not, run Discovery again with Entire Network selected.

I moved the server on which I had installed SGM and now I can’t start the SGM client or server. Why?

If you change the IP address of the server on which you installed SGM, or if you move the server to a new network, you must reboot the server to prevent SGM connection problems.

To reboot the server, use the following procedure:




# ./sgm reboot


78-15589-01

Appendix A SGM FAQsHow often does SGM poll the ITP nodes?

If you change the server’s Solaris host name, you must reset the default host name on the SGM server and client, using the following procedure:




# ./sgm evilstop

SGM stops all SGM servers on the local host.


# ./sgm servername hostname

where hostname is the new default host name. Make sure the new name is valid and is defined in your /etc/hosts file.

SGM resets the default host name for the SGM server and client and automatically restarts the SGM server.

How often does SGM poll the ITP nodes?By default, SGM polls the nodes in the network every 15 minutes. However, you can initiate a poll for one or more nodes at any time by selecting the nodes in the Discovery panel of the Discovery Dialog and pressing Poll.

You can also change the default poll interval for one or more nodes in the SNMP Configuration Dialog. You must be logged in as the root user or as a super user to access this dialog.

Finally, the Node Details Window polls the displayed node and its adjacent node every 15 seconds, but you can change that poll interval, too.


78-15589-01

Appendix A SGM FAQsIf I select the Clear Event Icon menu option, does that delete the event from the SGM database?

If I select the Clear Event Icon menu option, does that delete the event from the SGM database?

No. When you select the Clear Event Icon menu option for a node, signaling point, linkset, or link, SGM does not delete the actual event from its database. SGM only deletes the event icon (an orange triangle) from its displays for the selected node, signaling point, linkset, or link, and only for the SGM client on which you are currently working.

What does the asterisk (*) mean next to an SLC number?

In SGM, each link is identified by its signaling link code ID (SLC). An asterisk indicates that a link is not configured, or that a poll could not get data for the link. For example, SLC (*)3 means there is no link associated with the selected linkset for SLC 3, and SLC 3(*) means there is no link associated with the adjacent linkset for SLC 3.

How does “zoom in on an area” work in a topology map?

“Zoom in on an area” enables you to zoom in on a selected area of the topology map in the Topology Window. To do so, click the Zoom in on an area button, or select Topology Tools >Zoom > Area from the SGM Main Menu, then click in the topology map and drag a rectangle around the area you want to zoom in on. SGM expands the selected area to fill the topology map.


78-15589-01

Appendix A SGM FAQsMy server has multiple IP addresses and I can’t connect to the SGM server. How can I correct this problem?

My server has multiple IP addresses and I can’t connect to the SGM server. How can I correct this problem?

This problem occurs because the SGM client does not know which address to use when connecting to the server. When this problem occurs, SGM displays the following error message: “This client is not allowed to connect to the server.”

To correct this problem, use the sgm servername command on the SGM client to set the IP address to be used at both the SGM server and client. See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of this command.

(In Windows, select Start> Programs > Cisco SGM Client> Modify Default SGM Server Name, then you can enter the sgm servername command.)

What does this message mean: DataModelMediatorService: Could not find service in RMI registry or the RMI Registry may be down.

Either you specified an incorrect port number when installing SGM, or the server or RMI registry is unavailable. To correct this problem, use the following procedure:

Step 1 Verify that you specified a correct port number.

Step 2 Enter the sgm status command on the server to determine the status of all SGM servers on the local host.

Step 3 Enter the sgm restart command to restart any servers that are not running.


78-15589-01

Appendix A SGM FAQsWhat does this message mean: MessageLoggerProxy:setMessageLogger(): Could not resolve.

What does this message mean: MessageLoggerProxy:setMessageLogger(): Could not resolve.

One of the following conditions has occurred:

• The host or port number of the Message Log Server is configured incorrectly. Verify that the host or port number is valid.

• SGM cannot reach the Message Log Server, probably because it is restarting. SGM recovers the connection when the Message Log Server restarts.

Will the SGM server processes restart automatically after a system reboot?

Yes. When you install the SGM server, SGM modifies your system startup scripts to ensure that the SGM server processes start up again after a system reboot. To accomplish this, SGM adds the following lines to your system startup scripts:

/etc/init.d/sgm

/etc/rc0.d/K99sgm

/etc/rc1.d/K99sgm

/etc/rc2.d/K99sgm

/etc/rc3.d/K99sgm

/etc/rc3.d/S99sgm

These lines ensure that the SGM shutdown and startup scripts run in the correct order for each system initiation state.


78-15589-01

Appendix A SGM FAQsSome of my SGM windows are showing up with small, unusable text entry fields. How can I correct this?

Some of my SGM windows are showing up with small, unusable text entry fields. How can I correct this?

Depending on your system, as well as other factors, SGM windows can sometimes display so small that text is illegible, and columns and text entry fields are very narrow and unusable. If this happens, resize the window and widen the individual columns until the information is again legible and the columns and text entry fields are usable.

To make a column wider or narrower, click the column divider in the header and move the divider to the right or left while holding down the right mouse button.

Sometimes my SGM display seems to lock up. Why?In SGM, events might cause message popups to remain in the background of your display, preventing you from interacting with other windows. If you suspect that your display has locked up, perform the following tasks:

• Make sure you are running SGM on a supporrted operating system. Refer to the “Solaris Software Requirements” and “Windows Software Requirements” sections of the Cisco Signaling Gateway Manager Installation Guide for more information about supported operating systems.

• Minimize windows and look for an SGM message popup in the background.


78-15589-01

Appendix A SGM FAQsAfter a failed uninstall of the Windows client, I’m prompted to uninstall again, but the procedure does not work. Why?

After a failed uninstall of the Windows client, I’m prompted to uninstall again, but the procedure does not work. Why?

If for some reason the Windows SGM client uninstall procedure fails before the client is completely uninstalled, SGM prompts you to uninstall the client again. However, this might not be possible using the standard Add/Remove Programs icon in the Windows Control Panel, or from the Windows Start menu.

If you cannot uninstall the SGM client using the standard procedure, use the following procedure:

Step 1 Delete the SGM client installation directory and its contents:

• If you installed the SGM client in the default directory, C:\Program Files, then the installation directory is C:\Program Files\SGMClient\.

• If you installed the SGM client in a different directory, then the installation directory is located in that directory.

Step 2 Delete the following directory: /Program Files/Installshield Installation Information/{FD024E16-48AE-11D5-934C-00108335E3DE}.

Note This directory might be hidden.

Step 3 Delete the Cisco SGM Client registry key and its contents:

HKEY_LOCAL_MACHINE\SOFTWARE\Cisco Systems, Inc.\Cisco SGM Client

Step 4 Delete the SGM Client entries from the Windows Start menu and desktop.


78-15589-01

Appendix A SGM FAQsWhy do I see strange character strings when I install SGM?

Why do I see strange character strings when I install SGM?

The setting of the LANG environment variable can cause syntax errors in the SGM setup scripts, which can result in messages that contain strange character strings such as ?y?d@O. To correct this problem, unset the LANG environment variable in the workstation from which you are installing SGM, using one of the following commands:

• If you are running sh, enter the unset LANG command.

• If you are running csh, enter the unsetenv LANG command.

Then install SGM again.

Why doesn’t Netscape launch when I select a Web page menu option from the SGM Main Menu?

If Netscape is not already running on Solaris, and you select a menu option that displays a Web page, such as View> Reports> Network Statistics, SGM might not be able to launch Netscape.

To avoid this problem, make sure you are running Netscape Communicator 4.7 or later, and make sure Netscape is already running before selecting a menu option that displays a Web page.


78-15589-01

Appendix A SGM FAQsWhy doesn’t Netscape launch when I select a Web page menu option from the SGM Main Menu?


78-15589-01

Cisco S78-15589-01

A
P P E N D I X B SGM Command Reference
This appendix provides the following information:

• SGM Commands and Descriptions, page B-2

• Output of sgm status Command, page B-70

• Output of sgm export Command, page B-71

• Output of sgm gttcheck Command, page B-71

B-1ignaling Gateway Manager User Guide

Appendix B SGM Command ReferenceSGM Commands and Descriptions

SGM Commands and DescriptionsTable B-1 provides the format and a brief description of each SGM command. Each command is available in both Solaris and Windows, except as indicated.

Table B-1 SGM Commands

Command Description

sgm Displays the command syntax for the sgm command and all of its options. The function of this command is identical to sgm help. For a sample output for this command, see the “Viewing the SGM Technical Documentation” section on page 7-122.

sgm ? Displays the command syntax for the sgm command and all of its options. The function of this command is identical to sgm help. For a sample output for this command, see the “Viewing the SGM Technical Documentation” section on page 7-122.

To see the command syntax for a specific keyword, enter sgm ? followed by that keyword. For example, if you enter sgm help restart, SGM displays:

sgm restart - Restarts all SGM Servers on the local host.sgm restart web - Restarts Web servers on the local host.sgm restart jsp - Restarts JSP servers on the local host.sgm restart pm - Restarts Process Manager on the local host.

B-2Cisco Signaling Gateway Manager User Guide

78-15589-01


sgm accstats [node-list [id-tag]] [sort-option] [quiet]

(Solaris only) Generate SGM accounting statistics reports:

• To include or exclude specific nodes, signaling points, or linksets in the reports, use the node-list argument:

– To include all nodes, specify all.

– To include a single node or signaling point, specify a single node name, or node name and signaling point name, as the node-list argument. The node name must match exactly the node name as discovered by SGM, including the domain name, and each line must end with a colon (:). For example:


To specify a node name and signaling point:


– To include or exclude nodes, signaling points, or linksets based on the contents of the user-defined nodes.include, linksets.include, nodes.exclude, and linksets.exclude files, create the files, then specify default. This is also the default setting for this command; you only need to specify default if you also want to specify an id-tag, sort-option, or quiet.

– To include a group of nodes or signaling points other than the one specified in the nodes.include file, create a file that contains the list of nodes and signaling points to included and specify the full path and name of the file as the node-list argument.

If you specify a node-list, you can also specify an id-tag to identify the reports. The id-tag can be any meaningful character string, but it cannot contain any spaces. The default value for id-tag is the process ID of the sgm accstats command.

Table B-1 SGM Commands (continued)

Command Description


78-15589-01



(continued)

• To specify the sort order for the reports, specify one of the following keywords for the sort-option argument:

– -sdp—Sort based on the destination point code (DPC) of the node, in descending order.

– -sno—Sort based on the node name, in ascending order.

– -sop—Sort based on the originating point code (OPC) of the node, in descending order.

– -srb—Sort based on number of bytes received, in descending order.

– -srm—Sort based on number of MTP3 MSUs received, in descending order.

– -ssb—Sort based on number of bytes sent, in descending order.

– -ssi—Sort numerically based on service indicator (SI), in ascending order.

– -ssm—Sort based on number of MTP3 MSUs sent, in descending order.

• To disable automatic output to the terminal when running this command in a script, specify the quiet keyword. SGM generates the report in export format, which you can view using the SGM Web interface.

The first time you use the sgm accstats command to generate a report, you must enter the command at least three times:


• The second entry begins calculating useful accounting statistics and, if the data being collected appears valid, begins generating the report.



Command Description


78-15589-01



(continued)

See the “Generating and Viewing Custom SGM Statistics Reports” section on page 3-369 for more information on the use of this command.

You must be logged in as the root user or as a super user to use this command.

sgm adduser [username] (Solaris only) If SGM User-Based Access is enabled, adds the specified user to the authentication list.

When you add a user, SGM prompts you for the following information:

• User’s password. When setting the password, follow the rules and considerations in the “Creating Secure Passwords” section on page 4-5.

• Whether to force the user to change the password at the next login. The default is not to force the user to change the password.

• Authentication level for the user. Valid levels are:

– 1—Basic User

– 2—Power User

– 3—Network Operator

– 4—Network Administrator

– 5—System Administrator

See the “Implementing SGM User-Based Access (Solaris Only)” section on page 4-2 for more information on authentication levels, and on the use of this command.



Command Description


78-15589-01


sgm authtype [local | solaris] (Solaris only) Configures SGM security authentication, as follows:

• local—Allows creation of user accounts and passwords local to the SGM system. When using this method, user names, passwords, and access levels are managed using SGM commands.

• solaris—Uses standard Solaris-based user accounts and passwords, as specified in the /etc/nsswitch.conf file. Authentication can be provided by the local /etc/passwd file or from a distributed Network Information Services (NIS) system.

You can use all SGM User-Based Access commands except the following commands:

– sgm disablepass

– sgm passwordage

– sgm userpass

You must use Solaris commands to manage passwords.

Users also cannot change their passwords using the SGM client. Instead, they must manage their passwords on the external authentication servers, using Solaris commands.

All new passwords take effect the next time SGM automatically synchronizes local SGM passwords with Solaris.

In addition, you must be logged in as the root user, not a super user, to use the following SGM commands:

– sgm adduser

– sgm disableuser

– sgm enableuser

– sgm updateuser

See the “Implementing SGM User-Based Access (Solaris Only)” section on page 4-2 for more information on the use of this command.



Command Description


78-15589-01


sgm backup (Solaris only) Backs up SGM data files to the SGM installation directory. SGM automatically backs up all data files at 11:59 PM each night, but you can use this command to back up the files at any other time.

• If you installed SGM in the default directory, /opt, then the locations of the backup files are /opt/sgm30-client-backup.tar.Z and /opt/sgm30-server-backup.tar.Z.

• If you installed SGM in a different directory, then the backup files are located in that directory.

To restore the SGM data files from the previous night’s backup, use the sgm restore command. Do not try to manually extract the backup files.

You must be logged in as the root user (not as a super user) to use this command.

sgm backupdir [directory] (Solaris only) Enables you to change the directory in which SGM stores its nightly backup files. The default backup directory is the directory in which SGM is installed:

• If you installed SGM in the default directory, /opt, then the default backup directory is also /opt.

• If you installed SGM in a different directory, then the default backup directory is that directory.

If you specify a new directory that does not exist, SGM does not change the directory, and issues an appropriate message.



Command Description


78-15589-01


sgm badloginalarm [number-of-attempts | clear]

(Solaris only) If SGM User-Based Access is enabled, number of unsuccessful login attempts allowed before SGM generates an alarm.


SGM records alarms in the system security log file. The default path and filename for the system security log file is /opt/CSCOsgm/logs/sgmSecurityLog.txt. If you installed SGM in a directory other than /opt, then the system security log file is located in that directory.

To view the system security log file, enter sgm seclog. You can also view the system security log on the SGM System Security Log Web page. For more information, see the “Viewing the SGM System Security Log” section on page 7-113.

To disable this function (that is, to prevent SGM from automatically generating an alarm after unsuccessful login attempts), enter sgm badloginalarm clear.

See the “Automatically Disabling Users and Passwords (Solaris Only)” section on page 4-10 for more information on the use of this command.



Command Description


78-15589-01


sgm badlogindisable [number-of-attempts | clear]

(Solaris only) If SGM User-Based Access is enabled, number of unsuccessful login attempts by a user allowed before SGM disables the user’s authentication. SGM does not delete the user from the authentication list, SGM only disables the user’s authentication. To re-enable the user’s authentication, use the sgm enableuser command.


To disable this function (that is, to prevent SGM from automatically disabling a user’s authentication after unsuccessful login attempts), enter sgm badlogindisable clear.



sgm browserpath (Solaris only) Sets a user-defined SGM Web browser path, and verifies that the browser specified by the user exists.


sgm certgui (Solaris only) If Secure Sockets Layer (SSL) is implemented in your SGM system, opens the SGM Certificate Tool window, which enables you to manage SSL certificates on the SGM client.

Note If you installed the SGM server and client on the same workstation, this command is unnecessary. Instead, when you use the sgm keytool command to manage SSL certificates on the server, SGM automatically manages the certificates on the client.

You must be logged in as the root user (not as a super user) to use this command in Solaris.


Command Description


78-15589-01


sgm certtool [clear | delete alias | export alias [-file filename] | import alias [-file filename] | list]

If Secure Sockets Layer (SSL) is implemented in your SGM system, enables you to manage SSL certificates on the SGM client from the command line.

Note If you installed the SGM server and client on the same workstation, this command is unnecessary. Instead, when you use the sgm keytool command to manage SSL certificates on the server, SGM automatically manages the certificates on the client.

Use the following keywords and arguments with this command:

• import alias [-file filename]—Imports a signed SSL certificate in X.509 format. This is the most common use for this command.

The alias argument can be any character string; the host name of the server from which you are importing the certificate is a good choice.

To import the certificate from a file, specify the optional -file keyword and a filename.

• export alias [-file filename]—Exports the specified SSL certificate in X.509 format.

To export the certificate to a file, specify the optional -file keyword and a filename.

• list—Lists all SSL certificates on the SGM client.

• delete alias—Removes the specified SSL certificate from the SGM client.

• clear—Removes all SSL certificates from the SGM client.

(Solaris only) You must be logged in as the root user (not as a super user) to use this command in Solaris.


Command Description


78-15589-01


sgm clean (Solaris only) Removes all SGM data from the SGM server, excluding message log files, backup files, and report files. This command restores the SGM server to a “clean” state, such as would exist after a new installation of SGM, except for the presence of the retained files.

Data removed includes all SGM data, notes, preferences, route files, and views, as well as any user-created files stored in SGM directories.


sgm cleanall (Solaris only) Removes all SGM data from the SGM server, including message log files, backup files, and report files. This command restores the SGM server to a “clean” state, such as would exist after a new installation of SGM.

Data removed includes all SGM data, notes, preferences, route files, views, message log files, backup files, and report files, as well as any user-created files stored in SGM directories.


sgm cleandiscover [seed-node] [seed-node]...

(Solaris only) Enables you to delete all current network data and begin a clean discovery of the ITP network from the command line. Use the seed-node arguments to specify the DNS names or IP addresses of one or more seed nodes.

Note When you begin a clean discovery, SGM stops any real-time polls that are running and issues appropriate messages.

Running this command does not remove any notes, preferences, route files, views, message log files, backup files, or report files, nor any user-created files stored in SGM directories.



Command Description


78-15589-01


sgm cliconntimer [number-of-seconds | clear]

(Solaris only) Specifies how long, in seconds, an SGM client is to wait for a message from the SGM server before exiting. If the timer expires, the client pings the server and takes the following action:

• If the server responds to the ping, the client reconnects to the server.

• If the server does not respond to the ping, but there is a backup server configured, the client connects to the backup server.

• If the server does not respond to the ping, and there is no backup server configured, the client stops.

The valid range is 10 seconds to an unlimited number of seconds. The default value is 60 seconds.

To restore the default timeout of 60 seconds, enter the sgm cliconntimer clear command.



sgm client [hostname] (Solaris only) Starts an SGM client on the specified host. If no host name is specified, starts an SGM client on the default host, as specified during installation. See the “Connecting to a New Server” section on page 3-399 for information about determining the default host.

If you Telnet into a remote workstation, the DISPLAY variable must be set to your local display, or you cannot use this command. If the DISPLAY variable is not set automatically, you must set it manually. See the “Setting the DISPLAY Variable (Solaris Only)” section on page 5-47 for details.


Command Description


78-15589-01


sgm clientlogs (Solaris only) Uses PAGER to display the SGM client log files.

The SGM client log files contain client console output for all SGM clients, one file per local or remote client. The file for a client is created by SGM automatically when the client starts.

• If you installed SGM in the default directory, /opt, then the SGM client log file is located in the /opt/CSCOsgm/logs/clientLogs directory.

• If you installed SGM in a different directory, then the file is located in that directory.

sgm clitimeout [number-of-minutes | clear]

(Solaris only) Specifies how long, in minutes, an SGM client can be inactive before being disconnected automatically by SGM.

This function is disabled by default. If you do not specify this command, clients are never disconnected as a result of inactivity.

If you enter the sgm clitimeout command, the valid range is 1 minute to an unlimited number of minutes. There is no default value.

If you have enabled this function and you want to disable it (that is, never disconnect a client as a result of inactivity), enter the sgm clitimeout clear command.




Command Description


78-15589-01


sgm cmdlog [clear | -r] (Solaris only) Uses PAGER to display the contents of the system command log. The system command log lists all sgm commands that have been entered for the SGM server, the time each command was entered, and the user who entered the command.

To clear the log and restart the server, enter sgm cmdlog clear.

To display the contents of the log in reverse order, with the most recent commands at the beginning of the log, enter sgm cmdlog -r.


sgm console (Solaris only) Displays the contents of the console log file, sgmConsoleLog.latest. The console log file contains unexpected error and warning messages from the SGM server, such as those that might occur if the SGM server cannot start.


sgm countas (Solaris only) Displays a count of application servers in the current SGM database.


sgm countasp (Solaris only) Displays a count of application server processes in the current SGM database.


sgm countaspa (Solaris only) Displays a count of application server process applications in the current SGM database.


sgm countlinks (Solaris only) Displays a count of links in the current SGM database.



Command Description


78-15589-01


sgm countlinksets (Solaris only) Displays a count of linksets in the current SGM database.


sgm countnodes (Solaris only) Displays a count of nodes in the current SGM database.


sgm countobjects (Solaris only) Displays a count of all nodes, signaling points, linksets, links, application servers, application server processes, application server process associations, and signaling gateway mated pairs in the current SGM database.


sgm countsps (Solaris only) Displays a count of signaling points in the current SGM database.


sgm countsgmp (Solaris only) Displays a count of signaling gateway mated pairs in the current SGM database.



Command Description


78-15589-01


sgm cw2ksetup [install | uninstall]

(Solaris only) Manages the integration of SGM with CiscoWorks2000:

• install—Checks to see which CiscoWorks2000 files are installed, and installs additional files as necessary. Use this command to integrate SGM and CiscoWorks2000 in the following instances:

– You installed CiscoWorks2000 after you installed SGM.

– SGM and CiscoWorks2000 are no longer integrated for some reason.

• uninstall—Removes SGM files from the CiscoWorks2000 area.

Always run sgm cw2ksetup uninstall before uninstalling CiscoWorks2000 from your system.



Command Description


78-15589-01


sgm delete [all | node [all | node [node]...] | sp [all | point-code:net [point-code:net]...] | linkset [all | node/linkset [node/linkset]...]

(Solaris only) Deletes objects from the SGM database.

• all—Deletes all nodes, signaling points, and linksets from the SGM database.

• node all—Deletes all nodes from the SGM database.

• node node [node]...—Deletes one or more nodes from the SGM database. Use the node arguments to specify one or more nodes.

• sp all—Deletes all nodes from the SGM database.

• sp point-code:net [point-code:net]...—Deletes one or more signaling points from the SGM database. Use the point-code:net arguments to specify one or more signaling points, identified by point code and network name (for example, 1.22.0:net0).

• linkset all—Deletes all linksets from the SGM database.

• linkset node/linkset [node/linkset]...—Deletes one or more linksets from the SGM database. Use the node/linkset arguments to specify one or more linksets associated with specific nodes.

See the “Deleting a Linkset” section on page 3-88, “Deleting a Node” section on page 3-130, and “Deleting a Signaling Point” section on page 3-167 for more information.


sgm deluser [username] (Solaris only) If SGM User-Based Access is enabled, deletes the specified user from the authentication list. To add the user back to the list, use the sgm adduser command.

See the “Manually Disabling Users and Passwords (Solaris Only)” section on page 4-13 for more information on the use of this command.



Command Description


78-15589-01


sgm disablepass [username] (Solaris only) If SGM User-Based Access is enabled and sgm authtype is set to local, disables the specified user’s authentication and password. SGM does not delete the user from the authentication list, SGM only disables the user’s authentication and password.



If sgm authtype is set to solaris, you cannot use this command. Instead, you must manage passwords on the external authentication servers.



sgm disableuser [username] (Solaris only) If SGM User-Based Access is enabled, disables the specified user’s authentication. SGM does not delete the user from the authentication list, SGM only disables the user’s authentication.






Command Description


78-15589-01


sgm discover [seed-node] [seed-node]...

(Solaris only) Enables you to discover the ITP network from the command line. Use the seed-node arguments to specify the DNS names or IP addresses of one or more seed nodes.

Note This command does not perform a clean discovery. To do so, see the sgm cleandiscover command.


sgm enableuser [username] (Solaris only) If SGM User-Based Access is enabled, re-enables the specified user’s authentication, which had been disabled either automatically by SGM or by a super user.

The user’s authentication is re-enabled with the same password as before.

See the “Enabling and Modifying Users and Passwords (Solaris Only)” section on page 4-15 for more information on the use of this command.



Command Description


78-15589-01


sgm eventconfig [edit | master | restore | view]

(Solaris only) Manages the SGM event configuration file, SgmEvent.conf. This file determines the size of the SGM event database, the maximum length of time SGM is to retain events, the default severity and color associated with each type of event, and all other aspects of SGM event processing.

To manage the SgmEvent.conf file, specify one of the following keywords:

• edit—Open and edit the SgmEvent.conf file directly.

• master—Restore the SgmEvent.conf file to the default settings.

• restore—Restore the SgmEvent.conf file from the previous version that was used.

• view—View the current contents of the SgmEvent.conf file.

Any changes you make take effect when you restart the SGM server. SGM reflects the changes on the SGM server and on all SGM clients that connect to that server, and reflects any new or changed categories and severities in its Web display navigation bars.

See the “Modifying the SGM Event Configuration File (Solaris Only)” section on page 5-26 for important considerations to keep in mind when modifying the SgmEvent.conf file, and for more information about using this command.


sgm eventlog [clear | -r] (Solaris only) Uses PAGER to display the contents of the SGM event automation log. The event automation log lists all messages generated by scripts launched by event automation.

To clear the log and restart the server, enter sgm eventlog clear.

To display the contents of the log in reverse order, with the most recent events at the beginning of the log, enter sgm eventlog -r.



Command Description


78-15589-01


sgm evilstop (Solaris only) Forcefully stops all SGM servers on the local host. This command can be useful if a normal sgm stop does not stop the servers.


sgm export [all | as | asp | aspa | links | linksets | nodes | sgmp | sps]

(Solaris only) Exports current SGM data, with fields separated by vertical bars (|).

• all—Export all current SGM data.

• as—Exports only application server data.

• asp—Exports only application server process data.

• aspa—Exports only application server process association data.

• links—Export only link data.

• linksets—Export only linkset data.

• nodes—Export only node data.

• sgmp—Exports only signaling gateway mated pair data.

• sps—Exports only signaling point data.

For a sample output for this command, see the “Output of sgm export Command” section on page B-71.


sgm fontstyle [linux | solaris] (Solaris only) Font style to send to remote X SGM clients.

• linux—Sends Linux fonts to remote X SGM clients.

• solaris—Sends Solaris fonts to remote X SGM clients. This is the default value.



Command Description


78-15589-01


sgm gttcheck [list | semantics nodename filename| syntax filename]

(Solaris only) Checks the semantics or syntax of the specified GTT file.

• list—List all current GTT filenames.

• semantics nodename filename—Check the semantics of the specified GTT file on the specified node.

• syntax filename—Check the syntax of the specified GTT file.

For a sample output for this command, see the “Output of sgm gttcheck Command” section on page B-71.


sgm gttclient [hostname] (Solaris only) Starts an SGM GTT client on the specified host. If no host name is specified, starts an SGM GTT client on the default host, as specified during installation. See the “Connecting to a New Server” section on page 3-399 for information about determining the default host.



Command Description


78-15589-01


sgm gttdir [directory] (Solaris only) Sets the directory in which SGM stores GTT files. See the “Editing a Global Title Translation Table” section on page 3-290 for information about GTT files.

The default directory for GTT files is located in the SGM installation directory:

• If you installed SGM in the default directory, /opt, then the default directory is /opt/CSCOsgm/gtt.


Use this command if you want to use a different directory for GTT files, such as /tftboot, or such as a Network File System location on another server, used as the Trivial File Transfer Protocol (TFTP) server for server configuration files for ITPs in the network.


Do not set the new directory to any of the following: /usr, /var, /opt, or /tmp.

Do not set the new directory to the same directory in which you are storing message log files (sgm msglogdir), report files (sgm repdir), or route table files (sgm routedir).

After you change the directory, SGM asks if you want to restart the SGM server. The new directory takes effect when you restart the SGM server.



Command Description


78-15589-01


sgm help [keyword] Displays the command syntax for the sgm command and all of its options. The function of this command is identical to sgm ?. For a sample output for this command, see the “Viewing the SGM Technical Documentation” section on page 7-122.

To see the command syntax for a specific keyword, enter sgm help followed by that keyword. For example, if you enter sgm help restart, SGM displays:

sgm restart - Restarts all SGM Servers on the local host.sgm restart web - Restarts Web servers on the local host.sgm restart jsp - Restarts JSP servers on the local host.sgm restart pm - Restarts Process Manager on the local host.

sgm inactiveuserdays [number-of-days | clear]

(Solaris only) If SGM User-Based Access is enabled, number of days a user can be inactive before disabling that user account.

This function is disabled by default. If you do not specify this command, user accounts are never disabled as a result of inactivity.

If you enter the sgm inactiveuserdays command, the valid range is 1 day to an unlimited number of days. There is no default setting.

If you have enabled this function and you want to disable it (that is, prevent SGM from automatically disabling user accounts as a result of inactivity), enter sgm inactiveuserdays clear.




sgm iosinfo (Solaris only) Displays the versions of IOS with which SGM is compatible.


Command Description


78-15589-01


sgm installlog [server | client] (Solaris only) Displays the latest install log for the server or client. If you do not specify server or client, displays the latest install log for both the server and client.



Command Description


78-15589-01


sgm ipaccess [add [ip-addr] | clear | edit | list | rem [ip-addr] | sample]

(Solaris only) Enables you to create and manage a list of client IP addresses allowed to connect to the SGM server.

The list of allowed client IP addresses is contained in the ipaccess.conf file. By default, when you first install SGM, the ipaccess.conf file does not exist and SGM allows all client IP addresses to connect to the SGM server. To create the ipaccess.conf file and work with the list of allowed client IP addresses, specify one of the following keywords:

• add—Add the specified client IP address to the ipaccess.conf file. If the ipaccess.conf file does not already exist, this command creates a file with the first entry.

• clear—Remove all client IP addresses from the ipaccess.conf file, and allow connections from any SGM client IP address.

• edit—Open and edit the ipaccess.conf file directly. If the ipaccess.conf file does not already exist, this command creates an empty file.

• list—List all client IP addresses currently in the ipaccess.conf file. If no client IP addresses are listed (that is, the list is empty), connections from any SGM client IP address are allowed.

• rem—Remove the specified client IP address from the ipaccess.conf file.

• sample—Print out a sample ipaccess.conf file.


See the “Limiting SGM Client Access to the SGM Server (Solaris Only)” section on page 4-38 for more information about using this command.



Command Description


78-15589-01


sgm jspport [port-number] (Solaris only) Sets a new port number for the JSP server, where port-number is the new, numeric port number. SGM verifies that the new port number is not already in use.

This command is needed only if you must change the port number after you install SGM, because another application must use the current port number.

The new port number must contain only numbers. If you enter a port number that contains non-numeric characters, such as sgm13, SGM displays an error message and returns to the command prompt without changing the port number.



Command Description


78-15589-01


sgm keytool [clear | genkey | import_cert cert_filename | import_key key_filename cert_filename | list | print_csr | print_crt]

(Solaris only) If SSL is implemented in your SGM system, manages SSL keys and certificates on the SGM server.

If you installed the SGM server and client on the same workstation, also automatically manages the certificates on the client.

Use the following keywords and arguments with this command:

• clear—Stops the SGM server, if necessary, and removes all SSL keys and certificates from the server. Before restarting the server, you must either generate new SSL keys using the sgm keytool genkey command, or you must completely disable SSL using the sgm ssl disable command.

• genkey—Stops the SGM server, if necessary, and generates a new self-signed public/private SSL key pair on the SGM server. The new keys take effect when you restart the server.

• import_cert cert_filename—Imports the specified signed SSL certificate in X.509 format.

• import_key key_filename cert_filename—Imports the specified SSL key in OpenSSL format and the specified signed SSL certificate in X.509 format.

• list—Lists all SSL key/certificate pairs on the SGM server.

• print_csr—Prints a certificate signing request (CSR) in X.509 format.

• print_crt—Prints the SGM server’s SSL certificate in X.509 format.

See the “Implementing SSL Support in SGM” section on page 4-24 for more information on the use of this command.


sgm killclients (Solaris only) Forcefully stops all SGM clients, including all GTT clients, on the local host.



Command Description


78-15589-01


sgm linkstats [node-list [id-tag]] [sort-option] [quiet]

(Solaris only) Generate SGM link and linkset statistics summary reports:

• To include or exclude specific nodes, signaling points, or linksets in the reports, use the node-list argument:

– To include all nodes, specify all.

– To include a single node or signaling point, specify a single node name, or node name and signaling point name, as the node-list argument. The node name must match exactly the node name as discovered by SGM, including the domain name, and each line must end with a colon (:). For example:


To specify a node name and signaling point:


– To include or exclude nodes, signaling points, or linksets based on the contents of the user-defined nodes.include, linksets.include, nodes.exclude, and linksets.exclude files, create the files, then specify default. This is also the default setting for this command; you only need to specify default if you also want to specify an id-tag, sort-option, or quiet.

– To include a group of nodes or signaling points other than the one specified in the nodes.include file, create a file that contains the list of nodes and signaling points to included and specify the full path and name of the file as the node-list argument.

If you specify a node-list, you can also specify an id-tag to identify the reports. The id-tag can be any meaningful character string, but it cannot contain any spaces. The default value for id-tag is the process ID of the sgm linkstats command.


Command Description


78-15589-01



(continued)

• To specify the sort order for the reports, specify one of the following keywords for the sort-option argument:

– -sis—Sort based on average in-service percentage for each link (Daily InSrv), in descending order.

– -sls—Sort based on the linkset name, in ascending order.

– -sos—Sort based on the average out-of-service percentage for each link, in descending order.

– -sru—Sort based on the average Receive Utilization for each link (Avg Receive Util or Avg Receive Erls), in descending order.

– -ssu—Sort based on the average Send Utilization for each link (Avg Send Util or Avg Send Erls), in descending order. This is the default setting.

• To disable automatic output to the terminal when running this command in a script, specify the quiet keyword. SGM generates the report in export format, which you can view using the SGM Web interface.

The first time you use the sgm linkstats command to generate a report, you must enter the command at least three times:


• The second entry begins calculating useful link and linkset statistics.




Command Description


78-15589-01



(continued)

See the “Generating and Viewing Custom SGM Statistics Reports” section on page 3-369 for more information on the use of this command.


sgm listusers [username] (Solaris only) If SGM User-Based Access is enabled, lists all currently defined users in the authentication list, including the following information for each user:

• User name

• Last time the user logged in

• User’s authentication access level

• User’s current authentication status, such as Account Enabled or Password Disabled

To list information for a specific user, use the username argument to specify the user.

See the “Maintaining Your SGM Security System (Solaris Only)” section on page 4-17 for more information on the use of this command.


sgm logger (Solaris only) Displays the system messages messageLog.txt file with tail -f.

To stop the display, enter Ctrl-c.

sgm logtimemode [12 | 24] (Solaris only) Sets the time mode for dates in log files:

• 12—Use 12-hour time, with AM and PM. 1:00 in the afternoon is 1:00 PM.

• 24—Use 24-hour time, also called military time. 1:00 in the afternoon is 13:00. This is the default setting.



Command Description


78-15589-01


sgm maxasciirows [number-of-rows]

(Solaris only) Sets the maximum number of rows for SGM ASCII Web output, such as displays of detailed debugging information.

If you enter this command without the number-of-rows argument, SGM displays the current maximum number of rows. You can then change that value, or leave it as-is. The valid range is 1 row to an unlimited number of rows. The default value is 6000 rows.


sgm maxhtmlrows [number-of-rows]

(Solaris only) Sets the maximum number of rows for SGM HTML Web output, such as displays of statistics reports, status change messages, or SNMP trap messages.

If you enter this command without the number-of-rows argument, SGM displays the current maximum number of rows. You can then change that value, or leave it as-is. The valid range is 1 row to an unlimited number of rows. The default value is 500 rows.



Command Description


78-15589-01


sgm mldebug [mode] (Solaris only) Sets the mode for logging SGM debug messages:

• normal—Logs all action, error, and info messages. Use sgm mldebug normal to revert to the default settings if you accidentally enter the sgm mldebug command.

• list—Displays the current settings for the sgm mldebug command.

• all—Logs all messages, of any type.

• none—Logs no messages at all.

• minimal—Logs all error messages.

• action—Logs all action messages.

• debug—Logs all debug messages.

• dump—Logs all dump messages.

• error—Logs all error messages.

• info—Logs all info messages.

• snmp—Logs all SNMP messages.

• trace—Logs all trace messages.

This command can adversely affect SGM performance. Use this command only under guidance from the Cisco TAC.



Command Description


78-15589-01


sgm motd [cat | disable | edit | enable]

(Solaris only) Manages the SGM message of the day file, which is a user-specified SGM system notice. You can use the message of the day to inform users of important changes or events in the SGM system. The message of the day also gives users an opportunity to exit the SGM or GTT client before launching.

If the message of the day is enabled, it is displayed whenever a user attempts to launch an SGM or GTT client:

• If the user accepts the message, the client launches.

• If the user declines the message, the client does not launch.

Use the following keywords with this command:

• enable—Enables the message of the day function. Initially, the message of the day file is blank; use the sgm motd edit command to specify the message text.

• edit—Enables you to modify the message of the day.

• cat—Displays the contents of the message of the day file.

• disable—Disables this function (that is, stops displaying the message of the day whenever a user attempts to launch an SGM or GTT client).



sgm msglog [clear | -r] (Solaris only) Uses PAGER to display the contents of the system message log.

To save the current contents of the log, clear the log, and restart the server, enter sgm msglog clear.

To display the contents of the log in reverse order, with the most recent messages at the beginning of the log, enter sgm msglog -r.



Command Description


78-15589-01


sgm msglogage [number-of-days]

(Solaris only) Sets the maximum number of days to archive system message log files before deleting them from the SGM server.

If you enter this command without the number-of-days argument, SGM displays the current maximum number of days. You can then change that value, or leave it as-is. The valid range is 1 day to an unlimited number of days. The default value is 31 days.


sgm msglogdir [directory] (Solaris only) Changes the default location of all SGM system message log files. By default, the system message log files are located on the SGM server at /opt/CSCOsgm/logs.

Note Do not set the new directory to any of the following: /usr, /var, /opt, or /tmp.

Do not set the new directory to the same directory in which you are storing GTT files (sgm gttdir), report files (sgm repdir), or route table files (sgm routedir).


You must be logged in as the root user or as a super user to use this command. If you are changing to a default location outside SGM, you must have appropriate permissions for that location.


Command Description


78-15589-01


sgm msglogsize [number-of-lines]

(Solaris only) Sets the maximum number of messages to write to the message log file before starting a new file.

If you enter this command without the number-of-lines argument, SGM displays the current maximum number of messages. You can then change that value, or leave it as-is.

The valid range is 1000 messages to an unlimited number of messages. The default value is 10000 messages (approximately 2 MB). Therefore, the default message log file and its copy require approximately 4 MB, combined. If you specify a larger message log file size, the message log file and its copy require proportionally more space.

When changing the number of messages to display, keep in mind that every 5000 messages require approximately 1 MB. You need to balance your need to refer to old messages against the amount of space they take up.


sgm netlog [clear | -r] (Solaris only) Uses PAGER to display the contents of the network status log.

To save the current contents of the log, clear the log, and restart the server, enter sgm netlog clear.

To display the contents of the log in reverse order, with the most recent network status messages at the beginning of the log, enter sgm netlog -r.


sgm netlogger (Solaris only) Displays the current contents of the network status log file with tail -f.

To stop the display, enter Ctrl-c.


Command Description


78-15589-01


sgm newlevel [username] (Solaris only) If SGM User-Based Access is enabled, changes the authentication level for the specified user. Valid levels are:

• 1—Basic User

• 2—Power User






sgm passwordage [number-of-days | clear]

(Solaris only) If SGM User-Based Access is enabled and sgm authtype is set to local, number of days allowed before forcing users to change passwords.

This function is disabled by default. If you do not specify this command, users never need to change their passwords.

If you enter the sgm passwordage command, the valid range is 1 day to an unlimited number of days. There is no default setting.

If you have enabled this function and you want to disable it (that is, prevent SGM from forcing users to change passwords), enter sgm passwordage clear.

Note If sgm authtype is set to solaris, you cannot use this command. Instead, you must manage passwords on the external authentication servers.




Command Description


78-15589-01


sgm pcformat {edit | list | master | restore}

(Solaris only) Enables you to set the point code format to be used for this SGM server, and for all associated SGM clients. Normally, you need to set the point code format only once, after installation.

The point code format configuration is contained in the PointCodeFormat.xml file. To work with the file, specify one of the following keywords:

• edit—Opens the PointCodeFormat.xml file for editing.

• list—Displays the current contents of the PointCodeFormat.xml file.

• master—Restores the PointCodeFormat.xml file to the default settings.

• restore—Restores the PointCodeFormat.xml file to the last saved copy.


See the “Setting the Point Code Format (Solaris Only)” section on page 5-21 for more information about using this command.


sgm pclist (Solaris only) Lists all point codes that are currently being used by all nodes that are known to SGM.


sgm poll [node] [node]... (Solaris only) Enables you to poll one or more known nodes from the command line. Use the node arguments to specify the DNS names or IP addresses of one or more known nodes.


sgm print {all | data | snmp | task}

(Solaris only) Displays information about server internal data, SNMP settings, running tasks, or all three.



Command Description


78-15589-01


sgm props (Solaris only) Displays the contents of the System.properties files for both SGM server and client installs.


sgm readme Displays the contents of the README file for SGM.

sgm reboot (Solaris only) Reboots the Solaris SGM system.


sgm repcustage [number-of-days]

(Solaris only) Maximum number of days SGM is to archive custom reports.


See the “Modifying the Way SGM Handles Statistics Reports (Solaris Only)” section on page 3-335 for more information on the use of this command.


sgm repdailyage [number-of-days]

(Solaris only) Maximum number of days SGM is to archive daily reports.





Command Description


78-15589-01


sgm repdir [directory] (Solaris only) Sets the directory in which SGM stores report files. See the “Working with SGM Statistics Reports” section on page 3-334 for information about SGM reports.

The default directory for report files is located in the SGM installation directory:

• If you installed SGM in the default directory, /opt, then the default directory is /opt/CSCOsgm/reports.


Use this command if you want to use a different directory for report files, such as a Network File System location on another server.



Do not set the new directory to the same directory in which you are storing GTT files (sgm gttdir), message log files (sgm msglogdir), or route table files (sgm routedir).



sgm rephelp (Solaris only) Displays help for all commands related to SGM reports.



Command Description


78-15589-01


sgm rephourlyage [number-of-days]

(Solaris only) Maximum number of days SGM is to archive hourly reports.




sgm replog [clear | -r] (Solaris only) Uses PAGER to display the contents of the system reports log. The reports log lists all messages related to the creation and maintenance of SGM reports.

To clear the log and restart the server, enter sgm replog clear.

To display the contents of the log in reverse order, with the most recent commands at the beginning of the log, enter sgm replog -r.

The default path and filename for the system reports log file is /opt/CSCOsgm/reports/sgmReportLog.txt. If you installed SGM in a directory other than /opt, then the system reports log file is located in that directory.




Command Description


78-15589-01


sgm restart [jsp | pm | web] (Solaris only) Restarts SGM servers on the local host:

• jsp—Restarts the SGM JSP Server.

• pm—Restarts the SGM Process Manager and all managed processes.

• web—Restarts the SGM Web Server.

• If you do not specify a keyword, sgm restart restarts all SGM servers.



Command Description


78-15589-01


sgm restore [gtt | logs | reports | routes | security]

(Solaris only) Restores the SGM data files from the previous night’s backup, stored in the SGM installation directory:

• If you installed SGM in the default directory, /opt, then the locations of the backup files are /opt/sgm30-client-backup.tar.Z and /opt/sgm30-server-backup.tar.Z.

• If you installed SGM in a different directory, then the backup files are located in that directory.

To restore only specific parts of the SGM data files, use the following keywords:

• gtt—Restores only SGM GTT files.

• logs—Restores only SGM log files, such as the message log files.

• reports—Restores only SGM report files, such as the statistics report files.

• routes—Restores only SGM ITP route table files.

• security—Restores only the security-related parts of the SGM data files. This command is useful if you inadvertently delete your user accounts or make other unwanted changes to your SGM security information.

To change the directory in which SGM stores these backup files, use the sgm backupdir command.


sgm restoreprops (Solaris only) Restores the SGM server and client System.properties files, and other important configuration files, to “clean” backup versions of the files.


sgm rootvars (Solaris only) Displays the contents of the /etc/CSCOsgm.sh file, which determines the root location of the SGM server and client installation.


Command Description


78-15589-01


sgm routedir [directory] (Solaris only) Sets the directory in which SGM stores ITP route table files. See the “Editing an ITP Route Table File” section on page 3-281 for information about ITP route table files.

The default directory for ITP route table files is located in the SGM installation directory:

• If you installed SGM in the default directory, /opt, then the default directory is /opt/CSCOsgm/routes.


Use this command if you want to use a different directory for ITP route table files, such as /tftboot, or such as a Network File System location on another server, used as the Trivial File Transfer Protocol (TFTP) server for server configuration files for ITPs in the network.



Do not set the new directory to the same directory in which you are storing GTT files (sgm gttdir), message log files (sgm msglogdir), or report files (sgm repdir).




Command Description


78-15589-01


sgm sechelp (Solaris only) Displays help for all commands related to SGM security.



Command Description


78-15589-01


sgm seclog [clear | -r] (Solaris only) Uses PAGER to display the contents of the system security log.

The following security events are recorded in the log:

• All changes to system security, including adding users

• Login attempts, whether successful or unsuccessful, and logoffs

• Attempts to switch to another user's account, whether successful or unsuccessful

• Attempts to access files or resources of higher authentication level

• Access to all privileged files and processes

• Operating system configuration changes and program changes, at the Solaris level

• SGM restarts

• Failures of computers, programs, communications, and operations, at the Solaris level

To clear the log and restart the server, enter sgm seclog clear.

To display the contents of the log in reverse order, with the most recent security events at the beginning of the log, enter sgm seclog -r.





Command Description


78-15589-01


sgm secondaryserver [hostname [naming-port] | list]

(Solaris only) Configures a secondary SGM server, where:

• hostname is the name of the host on which the secondary SGM server is installed.

• naming-port is the SGM Naming Server port number for the secondary SGM server. The default port number is 44742.

For best results, Cisco recommends that you configure the primary server and the secondary server as secondaries for each other.

If you use the sgm secondaryserver command to configure a secondary SGM server, but the primary SGM server fails before you launch the SGM client, then the SGM client has no knowledge of the secondary server.

To list the secondary SGM server that has been configured for this primary SGM server, enter the sgm secondaryserver list command.



Command Description


78-15589-01


sgm servername [hostname] Resets the default host name, where hostname is the new default host name:

• Make sure the new default host name is valid and is defined in your /etc/hosts file. If it is not, you might not be able to start the SGM server.

• If you are not logged in as the root user or as a super user when you enter this command from an SGM client, the default host name is changed only for that SGM client, and for the user who entered the command.

• If you are logged in as the root user or as a super user when you enter this command, the default host name is changed for the SGM server and for the client, and the SGM server is restarted. The new default host name is used by the SGM server to register RMI services, and by SGM clients to connect to the server.

• If you are logged into a client-only installation as the root user or as a super user when you enter this command, the default host name is changed only for that SGM client. The new default host name is used by the SGM client to connect to the SGM server.

sgm services (Solaris only) Displays the processes started and managed by the Process Manager, as set in the Services.conf file.


sgm snmpcomm [name] (Solaris only) Enables you to set a new default SNMP read community name. SGM automatically updates the name in the SNMP parameters file. The default path and filename for the SNMP parameters file is /opt/CSCOsgm/etc/communities.conf.



Command Description


78-15589-01


sgm snmpconf [filename] (Solaris only) Sets the file used for SNMP parameters, such as community names, timeouts, and retries.

The default path and filename for the SNMP parameters file is /opt/CSCOsgm/etc/communities.conf. If you installed SGM in a directory other than /opt, then the file is located in that directory.

When you specify a new path or filename, SGM restarts the servers.

Note The SNMP parameters file uses the HP OpenView format. Therefore, you can set this path and filename to point to the HP OpenView ovsnmp.conf file in an existing OpenView system.

For information about exporting SNMP community names from CiscoWorks2000 Resource Manager Essentials (RME), see the “Importing SNMP Community Names from CiscoWorks2000 (Solaris Only)” section on page 5-2.


sgm snmpget [hostname] [oid] [oid]...

(Solaris only) Queries the specified hostname using SNMP GetRequests. Use the oid arguments to specify one or more OIDs or variable names.


sgm snmphelp (Solaris only) Displays help for all commands related to SNMP queries.


sgm snmpnext [hostname] [oid] [oid]...

(Solaris only) Queries the specified hostname using SNMP GetNextRequests. Use the oid arguments to specify one or more OIDs.



Command Description


78-15589-01


sgm snmpwalk [hostname] [oid] [oid]...

(Solaris only) Queries the specified hostname, using SNMP GetNextRequests to “walk” through the MIB. Use the oid arguments to specify one or more OIDs.


sgm sounddir [directory] (Solaris only) Sets the directory in which the SGM server stores event automation sound files. See the “Automating Events” section on page 5-33 for information about sound files.

The default directory for sound files is located in the SGM installation directory:

• If you installed SGM in the default directory, /opt, then the default directory is /opt/CSCOsgm/sounds.


Use this command if you want to use a different directory for SGM server event automation sound files, such as a Network File System location on another server.




Command Description


78-15589-01


sgm ssl [enable | disable | status]

(Solaris only) If SSL is implemented in your SGM system, manages SSL support in SGM:

• enable—Enables SSL support. If you enter this command and SSL has not been implemented in your SGM system, SGM prompts you to contact Cisco TAC or your Cisco Account Team for help in implementing SSL.

• disable—Disables SSL support.

• status—Displays the current status of SSL support in SGM, including whether SSL support is enabled or disabled and which SSL keys and certificates exist.



sgm sslstatus (Solaris only) If SSL is implemented in your SGM system, displays current status for SSL support in SGM, including whether SSL support is enabled or disabled and which SSL keys and certificates exist.



sgm start (Solaris only) Starts all SGM servers on the local host.



Command Description


78-15589-01


sgm start client [hostname] (Solaris only) Starts an SGM client on the specified host. If no host name is specified, starts an SGM client on the default host, as specified during installation. See the “Connecting to a New Server” section on page 3-399 for information about determining the default host.


This command has the same function as the sgm client command.

sgm start gttclient [hostname] (Solaris only) Starts an SGM GTT client on the specified host. If no host name is specified, starts an SGM GTT client on the default host, as specified during installation. See the “Connecting to a New Server” section on page 3-399 for information about determining the default host.


This command has the same function as the sgm gttclient command.

sgm start jsp (Solaris only) Starts the SGM JSP Server on the local host.


sgm start pm (Solaris only) Starts the SGM Process Manager and all managed processes on the local host.



Command Description


78-15589-01


sgm start web (Solaris only) Starts the SGM Web Server on the local host.


sgm statreps [acct | noacct] (Solaris only) Specifies whether SGM is to generate accounting statistics reports:

• acct—Generate accounting statistics reports. Accounting must be enabled on the links in order for SGM to generate accounting statistics.

• noacct—Do not generate accounting statistics reports. This is the default setting.

See the “Viewing SGM Accounting Statistics Reports” section on page 3-364 for more information on the use of this command.


sgm statreps clean (Solaris only) Removes all data from SGM network statistics reports, restoring the reports to a “clean” state.




Command Description


78-15589-01


sgm statreps cleancustom [tag] (Solaris only) Removes all data from one or more SGM custom statistics reports, restoring the reports to a “clean” state:

• To clean all custom reports, enter sgm statreps cleancustom.

• To clean a single custom report, enter sgm statreps cleancustom tag, where tag is the ID tag of the custom report you want to clean.



sgm statreps dailyage [number-of-days]

(Solaris only) Maximum number of days SGM is to archive daily network statistics reports.



This command has the same function as the sgm repdailyage command.



Command Description


78-15589-01


sgm statreps [disable | enable] (Solaris only) Enables SGM to generate network statistics reports:

• enable—Generate network statistics reports. This is the default setting.

• disable—Do not generate network statistics reports.



sgm statreps [diskcheck | nodiskcheck]

(Solaris only) Specifies whether SGM is to verify that a disk has at least 10 MB of space remaining before generating network statistics reports:

• diskcheck—Verify the disk space. This is the default setting.

• nodiskcheck—Do not verify the disk space.

If your system does not return the necessary amount of free space, in a correct format that SGM can parse, this command enables SGM to disable checking to allow reporting to continue.




Command Description


78-15589-01


sgm statreps [export | noexport]

(Solaris only) Specifies whether SGM is to generate network statistics reports in export format:

• export—Generate network statistics reports in export format. This is the default setting.

• noexport—Do not generate network statistics reports in export format.



sgm statreps hourlyage [number-of-days]

(Solaris only) Maximum number of days SGM is to archive hourly network statistics reports.



This command has the same function as the sgm rephourlyage command.



Command Description


78-15589-01


sgm statreps [iplinks | noiplinks]

(Solaris only) Specifies whether SGM is to include links that use the Stream Control Transmission Protocol (SCTP) IP transport protocol in network statistics reports:

• iplinks—Include SCTPIP links. This is the default setting.

• noiplinks—Do not include SCTPIP links.



sgm statreps [nullcaps | nonullcaps]

(Solaris only) Specifies whether SGM is to include links that do not have planned send and receive capacities in network statistics reports:

• nullcaps—Include links that do not have planned send and receive capacities. This is the default setting.

• nonullcaps—Do not include links that do not have planned send and receive capacities.




Command Description


78-15589-01


sgm statreps servratio [factor] (Solaris only) Displays a gray background in the InSrv cell in a network statistics report, if the following condition is met:


The default value for factor is 0.95.



sgm statreps status (Solaris only) Displays the current status of all SGM network statistics report parameters. These are the parameters that are set using the other sgm statreps commands, such as sgm statreps [disable | enable] and sgm statreps [diskcheck | nodiskcheck].



sgm statreps timemode [12 | 24]

(Solaris only) Sets the time mode for dates in network statistics reports:

• 12—Use 12-hour time, with AM and PM. 1:00 in the afternoon is 1:00 PM.

• 24—Use 24-hour time, also called military time. 1:00 in the afternoon is 13:00. This is the default setting.




Command Description


78-15589-01


sgm statreps timer (Solaris only) Displays the timer file for SGM network statistics reports. The timer file is useful for identifying how much time SGM spends gathering report data and generating reports.



sgm statreps utilratio [factor] (Solaris only) Displays a gray background in the Send Utilization or Receive Utilization cell in a network statistics report, if the following condition is met:


The default value for factor is 1.50.



sgm status (Solaris only) Displays the status of all SGM servers on the local host. For a sample output for this command, see the “Output of sgm status Command” section on page B-70.

sgm stop (Solaris only) Stops all SGM servers on the local host.


sgm stopclients (Solaris only) Stops all SGM clients running on the local host.


sgm stop jsp (Solaris only) Stops the SGM JSP Server on the local host.



Command Description


78-15589-01


sgm stop pm (Solaris only) Stops the SGM Process Manager and all managed processes on the local host.


sgm stop web (Solaris only) Stops the SGM Web Server on the local host.


sgm superuser [username] (Solaris only) Enables the specified user to perform most functions that otherwise require the user to be logged in as the root user. (The root user can still perform those functions, too.) The specified user account must exist in the local /etc/passwd file. You cannot specify a user that is defined in a distributed Network Information Services (NIS) system.

Note As a super user, you can adversely affect your operating environment if you are unaware of the effects of the commands you use. If you are a relatively inexperienced UNIX user, limit your activities as a super user to the tasks described in this document.

For a complete list of the SGM commands that a super user cannot use, as well as other super user considerations, see the “Specifying a Super User (Solaris Only)” section on page 4-22.


sgm syncusers (Solaris only) If SGM User-Based Access is enabled and sgm authtype is set to solaris, synchronizes local SGM passwords with Solaris.




Command Description


78-15589-01


sgm tac (Solaris only) Collects important troubleshooting information for the Cisco Technical Assistance Center, and writes the information to the /opt/CSCOsgm/tmp/cisco_sgm_tshoot.log file.


sgm telnetpath Specifies the path to the Telnet application to use for Telnet sessions on the SGM client, as well as any special parameters to pass to the Telnet application.

• On Solaris, the default path is /usr/bin/telnet.

• On Windows, you do not need to specify a path. Windows detects and launches the Telnet application wherever it is located.


sgm testeventconfig [-print] [filename]

(Solaris only) Parses and validates the specified event configuration file before you load it into SGM.

The default filename is SgmEvent.conf. If you use a different event configuration file, it must reside in the same directory as the eventconfiguration.dtd file.

The -print keyword dumps the event configuration to STDOUT for visual validation.



Command Description


78-15589-01


sgm tnproxy [disable | enable | start | status | stop]

(Solaris only) Manages a Telnet proxy. A Telnet proxy resides on a server and forwards Telnet requests from clients to ITPs that are accessible only from that server. A Telnet proxy is typically used to enable remote clients on desktop networks to Telnet to ITPs that otherwise would be unreachable.

• disable—Disables SGM Telnet proxy support. This is the default setting.

• enable—Enables SGM to use a Telnet proxy.

• start—Starts the Telnet proxy process.

• status—Indicates whether SGM Telnet proxy support is currently enabled or disabled.

• stop—Stops the Telnet proxy process.



Command Description


78-15589-01


sgm trapaccess [add [ip-addr] | clear | edit | list | rem [ip-addr] | sample]

(Solaris only) Enables you to create and manage a list of ITP IP addresses allowed to send traps to the SGM server.

The list of allowed ITP IP addresses is contained in the trapaccess.conf file. By default, when you first install SGM, the trapaccess.conf file does not exist and SGM allows all IP addresses to send traps to the SGM server. To create the trapaccess.conf file and work with the list of allowed client IP addresses, specify one of the following keywords:

• add—Add the specified IP address to the trapaccess.conf file. If the file does not already exist, this command creates the file containing the first entry.

• clear—Remove all IP addresses from the trapaccess.conf file, and allow traps from any SGM client IP address.

• edit—Open and edit the trapaccess.conf file directly. If the trapaccess.conf file does not already exist, this command creates an empty file.

• list—List all IP addresses currently in the trapaccess.conf file. If no IP addresses are listed (that is, the list is empty), traps from any SGM IP address are allowed.

• rem—Remove the specified IP address from the trapaccess.conf file.

• sample—Print out a sample trapaccess.conf file.


See the “Limiting Traps by IP Address (Solaris Only)” section on page 5-45 for more information about using this command.



Command Description


78-15589-01


sgm trapsetup [disable] (Solaris only) Stops the SGM server, configures SGM to receive SNMP traps (or prevents SGM from receiving traps), then restarts the SGM server. SGM gives you the option to receive traps natively or using HP OpenView.

When you select an SNMP trap port number for the SGM server, make sure your ITPs use the same SNMP trap port number. See the description of the snmp-server host command in the “ITP Requirements” section of the Cisco Signaling Gateway Manager Installation Guide for more information.

To prevent SGM from receiving traps, enter the sgm trapsetup disable command. SGM restarts the SGM server.


sgm trapstatus (Solaris only) Displays the current trap reception configuration for SGM, including:

• SNMP trap integration type:

– native—SGM receives traps natively on a UDP port.

– hpov—SGM receives traps using HP OpenView.

• For native, SGM also displays the UDP port number on which SGM receives traps natively.

• For hpov, SGM also displays the location of the HP OpenView home directory.

• Status for the sgmTrapReceiver (such as Running or Stopped).

sgm uninstall (Solaris only) Uninstalls SGM.



Command Description


78-15589-01


sgm unknownage [number-of-days]

(Solaris only) Sets the maximum number of days to retain Unknown nodes, signaling points, linksets, and links before deleting them from the SGM database.

If you enter this command without the number-of-days argument, SGM displays the current maximum number of days. You can then change that value, or leave it as-is. The valid range is 1 day to an unlimited number of days. The default value is 7 days. Setting this value to 0 days means delete all Unknown nodes, signaling points, linksets, and links at the next poll.


sgm updateuser [username] (Solaris only) If SGM User-Based Access is enabled, changes the authentication level for the specified user. Valid levels are:

• 1—Basic User

• 2—Power User




If sgm authtype is set to local, this command also enables you to change the following settings:

• User’s password. When setting the password, follow the rules and considerations in the “Creating Secure Passwords” section on page 4-5.

See the “Enabling and Modifying Users and Passwords (Solaris Only)” section on page 4-15 for more information on authentication levels, and on the use of this command.



Command Description


78-15589-01


sgm useraccess [disable | enable]

(Solaris only) Enables or disables SGM User-Based Access.

User-Based Access provides multi-level password-protected access to SGM features. Each user can have a unique user name and password. Each user can also be assigned to one of five levels of access, which control the list of SGM features accessible by that user.

You must enable SGM User-Based Access in order to use the associated SGM security commands.

See the “Implementing SGM User-Based Access (Solaris Only)” section on page 4-2 for more information.


sgm userpass [username] (Solaris only) If SGM User-Based Access is enabled and sgm authtype is set to local, changes the specified user’s SGM security authentication password.

If the user’s authentication has been disabled, either automatically by SGM or by a super user, this command re-enables the user’s authentication with a new password.

If sgm authtype is set to solaris, you cannot use this command. Instead, you must manage passwords on the external authentication servers.



sgm version (Solaris only) Displays version information for SGM servers and clients on the local host.

sgm viewlog (Solaris only) Uses PAGER to display the system messages messageLog.txt file.

This command has the same function as the sgm msglog command.


Command Description


78-15589-01


sgm wall message_string (Solaris only) Sends a message to all clients connected to the server. For example:

./sgm wall Server going down at 9:00 pm tonight.

sends the following message:

Server going down at 9:00 pm tonight.

SGM ignores quotation marks in message_string. To include quotation marks, use the escape character (\) in combination with quotation marks. For example:

./sgm wall Example of the \”sgm wall\” command.

sends the following message:

Example of the “sgm wall” command.


sgm webaccesslog [clear | -r] (Solaris only) Uses PAGER to display the SGM system Web access log file for the server to which you are connected, and which is currently running the SGM server. The system Web access log lists all SGM system Web access messages that have been logged for the SGM server. This provides an audit trail of all access to the SGM server via the Web interface.

To clear the log and restart the server, enter sgm webaccesslog clear.

To display the contents of the log in reverse order, with the most recent Web access messages at the beginning of the log, enter sgm webaccesslog -r.



Command Description


78-15589-01


sgm weberrorlog [clear | -r] (Solaris only) Uses PAGER to display the SGM Web server error log file for the server to which you are connected, and which is currently running the SGM server. The Web server error log lists all SGM Web error messages that have been logged for the SGM Web server.

To clear the log and restart the server, enter sgm weberrorlog clear.

To display the contents of the log in reverse order, with the most recent Web error messages at the beginning of the log, enter sgm weberrorlog -r.


sgm weblogupdate [interval | disable]

(Solaris only) Controls how often, in seconds, SGM updates certain Web output.

When you enter this command, SGM displays the current interval. You can then change that value, or leave it as-is. The valid range is 1 second to an unlimited number of seconds. The default value is 300 seconds (5 minutes).

To disable the update interval, enter the sgm weblogupdate disable command. This option lessens SGM’s CPU usage on both the server and client.


sgm webnames [display | real] (Solaris only) Specifies whether SGM is to show real node names or display names in Web pages:

• real—Show the real DNS names of nodes in Web pages, as discovered by SGM. This is the default setting.

• display—Show display names in Web pages. Display names are new names that you specify for nodes. For more information about display names, see the “Editing a Node” section on page 3-124.



Command Description


78-15589-01


sgm webport [port-number] (Solaris only) Sets a new port number for the Web server, where port-number is the new, numeric port number. SGM verifies that the new port number is not already in use.

The new port number must contain only numbers. If you enter a port number that contains non-numeric characters, such as sgm13, SGM displays an error message and returns to the command prompt without changing the port number.


sgm webutil [percent | erlangs] (Solaris only) Specifies whether SGM is to display send and receive utilization for linksets and links as percentages or in Erlangs, in Web pages:

• percent—SGM displays utilization as a percentage. This is the default setting.

• erlangs—SGM displays utilization in Erlangs.

See the “Working with SGM Statistics Reports” section on page 3-334 for more information on the use of this command.


sgm who (Solaris only) Displays a list of all client user names and processes connected to the server.

sgm xtermpath (Solaris only) Specifies the path to the xterm application to use for xterm sessions on the SGM client, as well as any special parameters to pass to the xterm application.

The default path is /usr/openwin/bin/xterm.

If one of the special parameters that you pass to the xterm application is a title, the title can contain dashes (-) and underscores (_), but it cannot contain any spaces.



Command Description


78-15589-01

Appendix B SGM Command ReferenceOutput of sgm status Command

Output of sgm status CommandThe following example shows the status information displayed when you enter the sgm status command:

# ./sgm status============================================================SGM Server Package Version: 3.0.0SGM Server Package Build Date: Sun Oct 27 03:03 EDT 2002SGM Server Package Hostname: sgm-sun8============================================================ sgmProcessManager: 3.0.0 Sun Oct 27 03:01 EDT 2002 sgmMsgLogServer: 3.0.0 Sun Oct 27 03:01 EDT 2002 sgmDataServer: 3.0.0 Sun Oct 27 03:01 EDT 2002 sgmTrapReceiver: 3.0.0 Sun Oct 27 03:01 EDT 2002============================================================SGM Naming Server IS Running.SGM Web Server IS Running.SGM JSP Server IS Running.SGM Process Manager IS Running with processes:

PROCESS STATUS PID Last Message

sgmDataServer Ready 24785 RunningsgmMsgLogServer Ready 24771 RunningsgmTrapReceiver Ready 24799 Running

SSL Support is Disabled.

SGM Server was last restarted: Sun Oct 27 12:05:06 EDT 2002

Solaris uptime: 2:12pm up 26 day(s), 16:29, 1 user, load average: 0.32, 0.14, 0.11

============================================================SGM Client Package Version: 3.0.0SGM Client Package Build Date: Sun Oct 27 03:03 EDT 2002============================================================

sgmClient: 3.0.0 Sun Oct 27 03:01 EDT 2002============================================================

Current time is: 2002/10/31 14:12:52


78-15589-01

Appendix B SGM Command ReferenceOutput of sgm gttcheck Command

Output of sgm gttcheck list Command# ./sgm gttcheck listlarge.ansi.samplelargest.samplemidsize.samplesmall.ansi.samplesmall.sample

Output of sgm gttcheck semantics Command# ./sgm gttcheck semantics sgm-seed1 small.sample===================================Parsing and syntax checking GTT file: small.sample===================================Loading GTT file: small.sample==> parsing GTT file...==> resolving GTT entries...Operation completed successfully.===================================GTT file info:=================================== Version = 1.0 Variant = itu Selector entries = 4 GTA entries = 8 App Group entries = 4 MAP entries = 12

Concerned PC entries = 4===================================Performing semantics checking for GTT file: small.sample===================================Validating GTT table for sgm-75-70a.cisco.com==> retrieving ITP information from sgm-75-70a.cisco.com==> validating GTA table ...Error #1: no route to destination 2.2.2 gtest,349,1012,gt,100, , ,Error #2: no route to destination 2.2.2 gtest,828,1012,gt, ,100, ,Error #3: no route to destination 2.2.2 gtest,828258,1012,pcssn,129, , ,Error #4: no route to destination 2.2.2 gtest,8282588595,1012,pcssn,100, , ,1Error #5: no route to destination 1.11.1 gtest,980,859,pcssn,10, , ,


78-15589-01


==> validating App Group table ...Error #6: no route to destination 1.12.1 atest,sha,1,861,gt,Error #7: no route to destination 1.11.1 atest,sha,2,859,pcssn,Error #8: no route to destination 2.2.2 atest,sha,3,1012,pcssn,10

Error #9: no route to destination 1.12.7 atest2,sha,1,867,gt,100==> validating MAP table ...Error #10: no route to destination 1.1.1 m809,10,sol, , , ,0,0Error #11: no route to destination 1.11.1 m859,10,sol, , , ,0,0Error #12: no route to destination 1.12.1 m861,10,sol, , , ,0,0Error #13: no route to destination 1.12.7 m867,10,sol, , , ,0,0Error #14: no route to destination 1.12.7 m867,100,sol, , , ,0,0Error #15: no route to destination 2.2.2 m1012,10,sol, , , ,0,0Error #16: no route to destination 2.2.2 m1012,100,sol, , , ,0,0Error #17: no route to destination 2.2.2 m1012,129,sol, , , ,0,0Error #18: no route to destination 1.11.1 m859,20,sha,861,20,list1,0,1Error #19: no route to destination 1.12.1 m859,20,sha,861,20,list1,0,1Error #20: no route to destination 1.12.1 m861,20,sha,859,20,list1,0,1Error #21: no route to destination 1.11.1 m861,20,sha,859,20,list1,0,1Error #22: no route to destination 1.11.1 m859,25,dom,861,25,list7,1,0Error #23: no route to destination 1.12.1 m859,25,dom,861,25,list7,1,0Error #24: no route to destination 1.12.1 m861,25,dom,859,25,list7,1,0Error #25: no route to destination 1.11.1 m861,25,dom,859,25,list7,1,0


78-15589-01


==> validating Concerned PC List table ...Error #26: no route to destination 1.1.1 clist1,809Error #27: no route to destination 1.11.1 clist1,859Error #28: no route to destination 2.2.2 clist3,1012Error #29: no route to destination 2.2.2 clist7,1012

Operation completed with errors: Total 29 errors, 0 warnings===================================

Output of sgm gttcheck syntax Command# ./sgm gttcheck syntax small.sample===================================Parsing and syntax checking GTT file: small.sample===================================Loading GTT file: small.sample==> parsing GTT file...==> resolving GTT entries...Operation completed successfully.===================================GTT file info:=================================== Version = 1.0 Variant = itu Selector entries = 4 GTA entries = 8 App Group entries = 4 MAP entries = 12

Concerned PC entries = 4===================================


78-15589-01

Cisco S78-15589-01

A
P P E N D I X C SGM MIB Reference
SGM queries the following MIBs:

MIB Description

MIB-II mib (RFC1213-MIB.my)(1.3.6.1.2.1)

Provides basic management information on the ITP (RFC 1213).

CISCO-ENVMON-MIB.my(1.3.6.1.4.1.9.9.13)

Provides environmental monitoring information on Cisco ITPs.

CISCO-IETF-SCTP-MIB.my(1.3.6.1.4.1.9.10.75)

Manages SCTP (RFC 2960).

CISCO-IETF-SCTP-EXT-MIB.my(1.3.6.1.4.1.9.10.76)

Extension to CISCO-IETF-SCTP-MIB.my that provides additional information to manage SCTP (RFC 2960).

CISCO-ITP-ACL-MIB.my(1.3.6.1.4.1.9.9.227)

Manages access lists that control messages sent over SS7 networks using ITP.

CISCO-ITP-ACT-MIB.my(1.3.6.1.4.1.9.9.230)

Provides information specified in ITU Q752 Monitoring and Measurements for SS7 networks. This information is used to manage messages sent over SS7 networks using ITP.

CISCO-ITP-GACT-MIB.my:(1.3.6.1.4.1.9.9.333)


CISCO-ITP-GRT-MIB.my:(1.3.6.1.4.1.9.9.334)

Manages information required to route messages sent over SS7 networks using ITP.

C-1ignaling Gateway Manager User Guide

Appendix C SGM MIB Reference

CISCO-ITP-GSCCP-MIB.my:(1.3.6.1.4.1.9.9.335)

Provides information specified in ITU Q752 Monitoring and Measurements for SS7 networks. This information is used to manage Signaling Connection Control Part (SCCP) messages sent over SS7 networks using ITP.

CISCO-ITP-GSP-MIB.my:(1.3.6.1.4.1.9.9.336)

Manages signaling points and associated messages sent over SS7 networks using ITP. This MIB replaces the CISCO-ITP-SP-MIB and supports multiple instances of a signaling point within the same configuration.

CISCO-ITP-GSP2-MIB.my:(1.3.6.1.4.1.9.9.332)


CISCO-ITP-RT-MIB.my(1.3.6.1.4.1.9.9.228)

Manages the route tables used to control messages sent over SS7 networks using ITP.

CISCO-ITP-SCCP-MIB.my(1.3.6.1.4.1.9.9.233)

Manages SCCP messages sent over SS7 networks using ITP, and provides information specified in ITU Q752 Monitoring and Measurements for SS7 networks.

CISCO-ITP-SP-MIB.my(1.3.6.1.4.1.9.9.232)

Manages Signaling Points and associated linksets and links in SS7 networks using ITP.

CISCO-ITP-SP2-MIB.my(1.3.6.1.4.1.9.9.248)

Provides Quality of Service (QoS) information related to the configuration of an SS7 network. Also provides MTP3 event history information.

CISCO-ITP-TC-MIB.my(1.3.6.1.4.1.9.9.231)

Defines textual conventions used to manage devices related to the SS7 network. The ITU documents that describe this technology are the ITU Q series, including:

• ITU Q.700: Introduction to CCITT SS7

• ITU Q.701: Functional description of the message transfer part (MTP) of SS7.

CISCO-ITP-XUA-MIB.my:(1.3.6.1.4.1.9.9.253)

Manages MTP3 User Adaptation (M3UA) and SCCP User Adaptation (SUA) for ITP.

MIB Description

C-2Cisco Signaling Gateway Manager User Guide

78-15589-01


You can obtain the latest versions of these MIBs from one of the following locations:

• The Zip file mibs.zip, located at the top of the SGM CD Image, contains these MIBs.

• You can download these MIBs from the Cisco Website:


CISCO-PROCESS-MIB.my(1.3.6.1.4.1.9.9.109)

Displays estimated memory and CPU utilization on Cisco devices. CPU utilization gives a general idea of how busy the processor is. The numbers are a ratio of the current idle time divided by the longest idle time.

CISCO-SYSLOG-MIB.my(1.3.6.1.4.1.9.9.41)

Provides a means of gathering syslog messages generated by the Cisco IOS.

MIB Description


78-15589-01




78-15589-01

Cisco S78-15589-01

A
P P E N D I X D Configuring SGM to Run with Various Networking Options
In addition to running on standard IP-connected networks, SGM has the flexibility to adapt to a variety of different networking environments, including Virtual Private Network (VPN), Network Address Translation (NAT), firewall, port-forwarding, and Secure Sockets Layer (SSL). SGM can run in each of these environments individually, or in any combination of networking environments.

This appendix describes communication between the SGM client and the SGM server. As shown in Figure D-1, this includes:

• Two-way RMI communication between a Java-based GUI client and Java-based server processes. The client can send requests to and receive responses from the server, and the server can send unsolicited notifications to the client. For example, if the server detects that an ITP’s state has changed, it sends a notification to all SGM clients to update their Topology windows.

• One-way HTTP communication between a Web browser and an SGM-embedded Web server, using the request/response model.

D-1ignaling Gateway Manager User Guide

Appendix D Configuring SGM to Run with Various Networking OptionsVPN Communication

Figure D-1 SGM Communication

Note This appendix does not address communication between the SGM server and the ITP, which uses the SNMP protocol for network management.

This appendix includes the following sections:

• VPN Communication, page D-2

• NAT Communication, page D-4

• Firewall Communication, page D-5

• Port-Forwarding Communication, page D-8

• SSL Communication, page D-11

VPN CommunicationSGM client/server communication can run transparently through a VPN tunnel, which is a secure IP layer, without any user intervention. You can use VPN to connect to a corporate network, then start the SGM client to connect through the VPN tunnel to an SGM server in the corporate network.

When the client host establishes a VPN tunnel, the operating system (or system library) sees this as another virtual IP interface. The VPN tunnel does not affect HTTP communication between the Web browser and server, it only affects RMI communication between the SGM client and server processes.

SGM Client SGM Server

Java-basedGUI client

Webbrowser

Serverprocesses

RMI SNMP

ITP

HTTP Web server/CGI/JSP

7471

1

D-2Cisco Signaling Gateway Manager User Guide

78-15589-01

Appendix D Configuring SGM to Run with Various Networking OptionsVPN Communication

For HTTP communication, the virtual IP address is transparent to the upper layer. The operating system automatically chooses the correct IP address to send out the request packet. For RMI communication, the SGM client needs to register with the SGM server server using the correct IP address, so that the server can invoke RMI callbacks and send unsolicited notifications to the client.

SGM solves this problem by automatically detecting the local IP interface so that the SGM server can send unsolicited notification to the correct IP address.

Figure D-2 shows a sample VPN network with the following characteristics:

• The SGM client with IP address 192.168.0.1 is connected to the SGM server network through a VPN tunnel.

• The SGM client host has obtained VPN IP address 10.1.1.2, which is a virtual IP interface.

Figure D-2 VPN Communication

When connecting to the SGM server, the SGM client automatically recognizes its VPN IP address, 10.1.1.2, and uses that address to register with the SGM server to receive RMI callbacks. This configuration is transparent to the user; no manual configuration is needed.

SGMClient

VPN IP10.1.1.2

VPN accessgateway SGM Server

192.168.0.1 10.0.0.1Non-trusted

networkVPN connection

Trustednetwork

IP connection

7471

7


78-15589-01

Appendix D Configuring SGM to Run with Various Networking OptionsNAT Communication

NAT CommunicationSGM client/server communication can run through one or more static NAT-connected networks. (SGM does not support dynamic NAT or dynamic NAT pool overloading.)

In a static NAT network, the SGM client and server are located on different sides of the NAT network, with no routes between the client network and the server network. The NAT device statically maps the client IP address to a NAT address in the server network, and the server IP address to a NAT address in the client network.

The NAT device translates packets between the SGM client and server by replacing IP address headers when packets pass through. From the client's point of view, the server appears to be at a NAT IP address in the client network, and vice versa. For most protocols, this technique is sufficient to enable the client and server to communicate.

However, for RMI protocol, this is not sufficient. RMI protocol requires the client and server to keep remote object references by remote stubs. These remote stubs contain the remote objects' IP addresses, and are passed between the client and server using Java serialization. The NAT device only converts the IP addresses in the IP packet header, but the remote stub object is within the packet content. Therefore, the NAT device cannot recognize the IP address inside the packet, and fails to route it correctly.

SGM solves this problem by creating a specialized NAT-aware socket factory. Some manual configuration on the part of the user is required to enable SGM to “know” the network NAT configuration.

Figure D-3 shows a sample static NAT network with the following characteristics:

• A static NAT device connects Network A (192.168.*.*) to Network B (10.*.*.*), with no routes between Network A and Network B.

• The NAT device maps SGM client IP address 192.168.0.1 in Network A to 10.1.1.2 in Network B.

• The NAT device maps SGM server IP address 10.0.0.1 in Network B to 192.168.1.2 in Network A.


78-15589-01

Appendix D Configuring SGM to Run with Various Networking OptionsFirewall Communication

Figure D-3 Static NAT Communication

To configure SGM in this static NAT network, you must modify the SGM client's RMIOverNAT.properties file.

• If you installed SGM in the default directory, /opt, then the location of the file is /opt/properties/RMIOverNAT.properties.


For the example shown in Figure D-3, you must add the following line to the file:

10.0.0.1 = 192.168.1.2

This line maps the SGM server's real IP address, 10.0.0.1 in Network B, to its NAT address, 192.168.1.2, in Network A, which is the server's IP address as seen by the client.

Note The SGM server automatically detects the SGM client's NAT address. No manual configuration on the part of the user is needed at the server side.

Firewall CommunicationTo enable SGM client/server communication through a firewall, you need to set up the firewall so that it allows SGM communication packets to pass through freely.

Note The SGM client and server communicate using TCP sockets. All port numbers in this section are TCP ports.

SGM Client Static NATdevice SGM Server

192.168.0.1 10.0.0.1

ServerNAT address192.168.1.2

ClientNAT address10.1.1.2

Network A192.168.*.*

Network B10.*.*.* 74

713


78-15589-01


The port number used by SGM is configured in the System.properties file:

• If you installed SGM in the default directory, /opt, then the location of the file is /opt/properties/System.properties.


Set the following parameters on the server side of the file:

RMIREGISTRY_PORT = 44742

DATASERVER_PORT = 0

MLSERVER_PORT = 0

PMSERVER_PORT = 0

WEB_PORT = 1744

where:

• RMIREGISTRY_PORT is the port on which the RMI naming server listens. You must specify a port number; 0 is not allowed.

• DATASERVER_PORT is the port on which the sgmDataServer process listens. If you specify 0, SGM uses any available port, 1024 and above.

• MLSERVER_PORT is the port on which the sgmMsgLogServer process listens. If you specify 0, SGM uses any available port, 1024 and above.

• PMSERVER_PORT is the port on which the sgmProcMgrServer process listens. If you specify 0, SGM uses any available port, 1024 and above.

• WEB_PORT is the port on which the SGM Web server listens. You must specify a port number; 0 is not allowed. To change the WEB_PORT number, use the sgm webport command. See the “SGM Commands and Descriptions” section on page B-2 for more information on the use of this command.

If any of these port numbers changes, you must restart the SGM server before the changes take effect.


78-15589-01


Set the following parameters on the client side of the file:


CLIENT_PORT = 0

where:

• RMIREGISTRY_PORT is the port on which the server-side RMI naming server listens. This port number must match the one specified for the RMIREGISTRY_PORT on the server side.

• CLIENT_PORT is the port on which the SGM client listens for RMI callbacks (unsolicited notifications). If you specify 0, SGM uses any available port, 1024 and above. If you specify CLIENT_PORT with a value other than 0, you can run only one SGM client process at a time.

If any of these port numbers changes, you must restart the SGM client before the changes take effect.

Figure D-4 shows a sample firewall network with the following parameters set in the System.properties file:

• On the SGM server side:


DATASERVER_PORT = 44751

MLSERVER_PORT = 44752

PMSERVER_PORT = 44753

WEB_PORT = 1774

• On the SGM client side:


CLIENT_PORT = 56173


78-15589-01

Appendix D Configuring SGM to Run with Various Networking OptionsPort-Forwarding Communication

Figure D-4 Firewall Communication

Port-Forwarding CommunicationTo enable SGM to operate in a TCP port-forwarding environment, perform the following configuration tasks:

Step 1 Configure the server hostname and port number mapping in the SGM client’s RMIOverNAT.properties file, as described in the “NAT Communication” section on page D-4.

Step 2 Configure the port numbers used by the SGM client and server in the System.properties file, as described in the “Firewall Communication” section on page D-5.

Step 3 Configure the port-forwarding tunnel to forward each side’s TCP connection to the other side.

Figure D-5 shows a sample network that uses Secure Shell (SSH) port-forwarding. Other port-forwarding configurations might use a single host with dual interfaces at the client’s and server's networks. While other port-forwarding configurations may differ from this example, the general rules to configure SGM to operate in a port-forwarding environment are the same.

SGM Client Firewalldevice SGM Server

192.168.1.1 192.168.2.2

Allow TCP connection from 192.168.1.1 to 192.168.2.2,ports 44742, 44751, 44752, 44753, and 1774

Network A192.168.1.*

Network B192.168.2.*

7471

6

Allow TCP connection from 192.168.2.2 to 192.168.1.1,port 56173


78-15589-01


Figure D-5 Port-Forwarding Communication

The port-forwarding network shown in Figure D-5 has the following parameters set;

• In the System.properties file, on the SGM server side:


DATASERVER_PORT = 44751

MLSERVER_PORT = 44752

PMSERVER_PORT = 44753

WEB_PORT = 1774

• In the System.properties file, on the SGM client side:


CLIENT_PORT = 56173

SGM Client

SSHClient host

SSH tunnel

SGM Server

SSHServer host

192.168.0.1

192.168.1.2

10.0.0.1

10.1.1.2

Network A192.168.*.*

Network B10.*.*.*

7471

4


78-15589-01


• In the SGM client's RMIOverNAT.properties file:

10.0.0.1/44742 = 192.168.1.2/25742

10.0.0.1/44751 = 192.168.1.2/25751

10.0.0.1/44752 = 192.168.1.2/25752

10.0.0.1/44753 = 192.168.1.2/25753

10.0.0.1/1774 = 192.168.1.2/8080

• In the port-forwarding network:

Local port 25751 => remote host 10.0.0.1, port 44742





Remote port 56173 => local host 192.168.0.1, port 56173

Note For port-forwarding setup, the backward-forwarding port numbers must match each other. In the above example, both are 56173. The forward-forwarding port number do not need to match each other.


78-15589-01

Appendix D Configuring SGM to Run with Various Networking OptionsSSL Communication

SSL CommunicationIf SSL is implemented and enabled in your SGM system, SGM uses secure socket communication for both RMI and HTTP communication between the SGM client and server.

SGM supports standard-based SSL encryption algorithms, including RSA, DSA public key algorithms, and 40-bit or 128-bit encryption. SGM can generate an X.509 certificate and a certificate signing request (CSR), which is interoperable with most certificate authorities (CAs).

Both the SGM Web server and the SGM server processes share the same SSL key/certificate pair. Both the SGM client and the Web browser can examine the server's certificate.

For more information, including descriptions of the SGM commands and procedures used to implement, enable, manage, and monitor SSL support, see the “Implementing SSL Support in SGM” section on page 4-24.

Figure D-6 shows a sample SGM-over-SSL network with the following characteristics:

• A user-generated SSL key pair on the SGM server.

• The server's certificate is trusted on the SGM client.

• Communication between the client and server is RMI-over-SSL and HTTPS. Both protocols are encrypted and secure.

Figure D-6 SSL Communication

SGM Client SGM Server

Java-basedGUI client

Webbrowser

Serverprocesses

RMI-over-SSL

HTTP

Trust servercertificate

SSLkey pair

Web server/CGI/JSP

7471

8


78-15589-01

Appendix D Configuring SGM to Run with Various Networking OptionsSSL Communication


78-15589-01

Cisco S78-15589-01

A
P P E N D I X E Editing a Non-SGM ITP Route Table
ITP uses a route table to select the appropriate signaling path for each message, or signal unit, that it must forward. The route table provides the destination point code of the packet and the linkset name that can be used to forward the packet.

SGM enables you to create and edit ITP route table files for an ITP. See the “Editing an ITP Route Table File” section on page 3-281 for more information.

If you want to edit a route table file that was created with a product other than SGM, you must take the following actions to ensure that SGM can use the file:

Step 1 Make sure the route table file uses the SGM route table file extension, .rou.

Step 2 Place the route table file in the SGM route table directory on the SGM server:

• If you installed SGM in the default directory, /opt, then the SGM route table directory is /opt/CSCOsgm/routes.

• If you installed SGM in a different directory, then the SGM route table directory is located in that directory.

E-1ignaling Gateway Manager User Guide

Appendix E Editing a Non-SGM ITP Route Table

Step 3 Make sure the SGM header lines in the file precede the ITP route table entries. The SGM header lines use the following format:

!! Created by SGM 3.0.0 on Oct 27, 2002 6:42:54 PM!! Do not edit this file by hand.!v3.0.0!ted220dbc4a!p2851:2

where:

• Comment lines begin with double exclamation points (!!).

• The version line begins with !v. This line indicates the version of SGM that was used to create the file.

• The time line begins with !t. This line indicates the date and time, in hex, that the file was created.

• The point code line begins with !p. This line indicates the point code used by the ITP, in hex, followed by an integer that indicates the point code variant being used. Valid point code variants are:

– - 1—ANSI

– - 2—ITU

– - 3—CHINA

E-2Cisco Signaling Gateway Manager User Guide

78-15589-01

Cisco S78-15589-01

A
P P E N D I X F SGM Statistics Export File Formats
This appendix lists the formats for the following SGM statistics export files:

• SGM Custom Network Statistics Export File Formats, page F-2

• SGM Daily and Hourly Accounting Statistics Export File Format, page F-2

• SGM Link Statistics Daily Export File Format, page F-3

• SGM Link Statistics Hourly Export File Format, page F-4

• SGM Linkset Statistics Daily Export File Format, page F-5

• SGM Linkset Statistics Hourly Export File Format, page F-6

• SGM Point Code Inventory Export File Format, page F-7

• SGM Rolling Network Statistics Export File Formats, page F-7

F-1ignaling Gateway Manager User Guide

Appendix F SGM Statistics Export File FormatsSGM Custom Network Statistics Export File Formats

SGM Custom Network Statistics Export File FormatsExport files for custom network statistics reports use the same format as the corresponding accounting, link, and linkset statistics reports:

• The export file for a custom accounting statistics report uses the same format as the daily and hourly accounting statistics report export file, as shown in the “SGM Daily and Hourly Accounting Statistics Export File Format” section on page F-2.

• The export file for a custom link statistics summary report uses the same format as the daily link statistics report export file, as shown in the “SGM Link Statistics Daily Export File Format” section on page F-3.

• The export file for a custom linkset statistics summary report uses the same format as the daily linkset statistics report export file, as shown in the “SGM Linkset Statistics Daily Export File Format” section on page F-5.

SGM Daily and Hourly Accounting Statistics Export File Format

Export files for SGM daily and hourly accounting statistics reports use the following format:

# ================================================================# Format of Accounting Statistics Daily and Hourly Files:# Any value = 999.2 means a math error occurred# ================================================================

# Field Variable Description# ----------------------------------------------------------------# 1 Row Id# 2 Calendar Date in Excel Import Format# 3 Calendar Date Good for Sorting# 4 Node Name# 5 Linkset Name Name of Linkset# 6 ACL Test Passed or Failed# 7 DPC Destination Point Code# 8 OPC Originating Point Code# 9 SI Service Indicator# 10 Received MSUs Number of MSUs sent this period# 11 Sent MSUs Number of MSUs received this period# 12 Received Bytes Number of bytes sent this period

F-2Cisco Signaling Gateway Manager User Guide

78-15589-01

Appendix F SGM Statistics Export File FormatsSGM Link Statistics Daily Export File Format

# 13 Sent Bytes Number of bytes received this period# 14 Node DisplayName Display Name of Node from SGM Server# 15 Linkset DisplayName Display Name of Linkset from ITP# 16 Period Length of this period in seconds# 17 Day String Textual value for day. Sun, Mon, etc# 18 Node SGMId Internal Id of node in SGM server# 19 Version File version# 20 Signaling Point Name Name of Signaling Point from ITP# 21 Signaling Point SGMId Internal Id of SP in SGM server# ================================================================

SGM Link Statistics Daily Export File FormatExport files for SGM daily link statistics summary reports use the following format:

# ================================================================# Format of Link Statistics Daily Export File:# Any value = 999.1 means link capacity not set# Any value = 999.2 means a math error occurred# ================================================================

# Field Variable Description# ----------------------------------------------------------------# 1 Row Id# 2 Calendar Date in Excel Import Format# 3 Calendar Date Good for Sorting# 4 Node Name# 5 Linkset Name Val cItpSpLinksetName# 6 SLC Val cItpSpLinkSlc# 7 Node DisplayName Display Name of Node from SGM Server# 8 Link DisplayName Val cItpSpLinkDisplayName# 9 Link Type (integer) Val cItpSpLinkType# 10 Link Type (text)# 11 MIB-II ifIndex of link. Serial/HSL Only.# 12 Plan send capacity of link in bits/sec.# Val cItpSpLinkPlanCapacitySent# 13 Plan receive capacity of link in bits/sec.# Val cItpSpLinkPlanCapacityRcvd# 14 MIB-II ifSpeed of link. Serial/HSL Only. In bits/sec.# 15 Hours in Day with Data# 16 Day String

# 17 DailyAvgSndU# 18 DailyAvgRcvU# 19 PeakSndU


78-15589-01

Appendix F SGM Statistics Export File FormatsSGM Link Statistics Hourly Export File Format

# 20 PeakSndHour# 21 PeakRecvU# 22 PeakRecvHour# 23 TotSendMSUs - In Kilos# 24 TotRecvMSUs - In Kilos# 25 Drops# 26 DailyAvgInSrv# 27 LowInSrv# 28 LowHour# 29 LTAvgInSrv# 30 LTAvgSndU# 31 LTAvgRcvU# 32 Node SGMId# 33 Version# 34 Signaling Point Name# 35 Signaling Point SGMId# ================================================================

SGM Link Statistics Hourly Export File FormatExport files for SGM hourly link statistics reports use the following format:

# ================================================================# Format of Link Statistics Hourly Export File:# Possible values of Link Type are:# other(1),serial(2),sctpIp(3),hsl(4)# Any value = 999.1 means link capacity not set# Any value = 999.2 means a math error occurred# ================================================================

# Field Variable Description# ----------------------------------------------------------------# 1 Row Id# 2 Calendar Date in Excel Import Format# 3 Calendar Date Good for Sorting# 4 Node Name# 5 Linkset Name Val cItpSpLinksetName# 6 SLC Val cItpSpLinkSlc# 7 Node DisplayName Display Name of Node from SGM Server# 8 Link DisplayName Val cItpSpLinkDisplayName # 9 Link Type (integer) Val cItpSpLinkType# 10 Link Type (text)# 11 MIB-II ifIndex of link. Serial/HSL Only.# 12 Plan send capacity of link in bits/sec.# Val cItpSpLinkPlanCapacitySent# 13 Plan receive capacity of link in bits/sec.


78-15589-01

Appendix F SGM Statistics Export File FormatsSGM Linkset Statistics Daily Export File Format

# Val cItpSpLinkPlanCapacityRcvd# 14 MIB-II ifSpeed of link. Serial/HSL Only. In bits/sec.# 15 Length of this period in seconds# 16 Day String# 17 Send utilization this time period. In Erlangs, not percent.# 18 Average send utilization since reboot. In Erlangs, not percent.# 19 Recv utilization this time period. In Erlangs, not percent.# 20 Average recv utilization since reboot. In Erlangs, not percent.# 21 Number of MTP3 MSUs sent this period# 22 Number of MTP3 MSUs received this period# 23 Number of drops this period# 24 Percentage of time in service this period# 25 Avg Percentage of time in service since reboot# or last counter wrap# 26 Percentage of time out of service this period# 27 Avg Percentage of time out of service since reboot# or last counter wrap# 28 Number of MTP3 Bytes sent this period# 29 Number of MTP3 Bytes received this period# 30 Node SGMId# 31 Version# 32 Signaling Point Name# 33 Signaling Point SGMId# ================================================================

SGM Linkset Statistics Daily Export File FormatExport files for SGM daily linkset statistics summary reports use the following format:

# ================================================================# Format of Linkset Statistics Daily Export File:# ================================================================

# Field Variable Description# ----------------------------------------------------------------# 1 Row Id# 2 Calendar Date in Excel Import Format# 3 Calendar Date Good for Sorting# 4 Node Name# 5 Linkset Name Val cItpSpLinksetName# 6 Node DisplayName Display Name of Node from SGM Server# 7 Linkset DisplayName# 8 Hours# 9 DayStr# 10 DailyAvgInSrv


78-15589-01

Appendix F SGM Statistics Export File FormatsSGM Linkset Statistics Hourly Export File Format

# 11 LowInSrv# 12 LowHour# 13 LTAvgInSrv# 14 NodeSGMId# 15 Version# 16 Signaling Point Name# 17 Signaling Point SGMId# ================================================================

SGM Linkset Statistics Hourly Export File FormatExport files for SGM hourly linkset statistics reports use the following format:

# ================================================================# Format of Linkset Statistics Hourly Export File:# ================================================================

# Field Variable Description# ----------------------------------------------------------------# 1 Row Id# 2 Calendar Date in Excel Import Format# 3 Calendar Date Good for Sorting# 4 Node Name# 5 Linkset Name Val cItpSpLinksetName# 6 Node DisplayName Display Name of Node from SGM Server# 7 Linkset DisplayName Val cItpSpLinksetDisplayName # 8 Length of this period in seconds# 9 Day String# 10 Percentage of time in service this period# 11 Avg Percentage of time in service since reboot# 12 Percentage of time out of service this period# 13 Avg Percentage of time out of service since reboot# 14 Node SGMId# 15 Version# 16 Signaling Point Name# 17 Signaling Point SGMId# ================================================================


78-15589-01

Appendix F SGM Statistics Export File FormatsSGM Point Code Inventory Export File Format

SGM Point Code Inventory Export File FormatExport files for SGM point code inventory reports are comma-separated value (CSV) text files. Each line of the file has the following format:

# ================================================================# Format of Point Code Inventory Export File:# ================================================================

# PointCode,NodeName,NodeDisplayName,PCType,SGMId# ================================================================

SGM Rolling Network Statistics Export File FormatsExport files for 7-day and 30-day rolling network statistics reports use the same format as the corresponding link and linkset statistics reports:

• The export file for a 7-day link statistics summary report uses the same format as the hourly link statistics report export file, as shown in the “SGM Link Statistics Hourly Export File Format” section on page F-4.

• The export file for a 7-day linkset statistics summary report uses the same format as the hourly linkset statistics report export file, as shown in the “SGM Linkset Statistics Hourly Export File Format” section on page F-6.

• The export file for a 30-day link statistics summary report uses the same format as the daily link statistics report export file, as shown in the “SGM Link Statistics Daily Export File Format” section on page F-3.

• The export file for a 30-day linkset statistics summary report uses the same format as the daily linkset statistics report export file, as shown in the “SGM Linkset Statistics Daily Export File Format” section on page F-5.


78-15589-01

Appendix F SGM Statistics Export File FormatsSGM Rolling Network Statistics Export File Formats


78-15589-01

Cisco Sig78-15589-01

G L O S S A R Y

A

accounting Collection of SS7 accounting statistics.

adjacent node In SGM, for a given pair of connected nodes, the node that SGM discovered second. See primary node.

adjacent point code Point code of the adjacent node for the linkset. Contrast with local point code.

alias point code See capability point code.

annotation User-defined descriptive string attached to a node, signaling point, or linkset.

ANSI American National Standards Institute.

application server Logical entity serving a specific routing key. The application server implements a set of one or more unique application server processes, of which one or more is normally actively processing traffic. See application server process, application server process association, routing key, signaling gateway mated pair.

application server

process

IP-based instance of an application server, such as Call Agents, HLRs, SMSCs, and so on. An application server process can implement more than one application server. See application server, application server process association, routing key, signaling gateway mated pair.

application server

process association

ITP’s virtual view of an application server process. The application server process association is defined on, and resides on, the ITP. See application server, application server process, routing key, signaling gateway mated pair.

GL-1naling Gateway Manager User Guide

Glossary

auto save Setting that enables SGM to save changes automatically when you exit SGM.

auto start Setting that enables SGM to start a process automatically when the Process Manager is started. See Data Server, Message Log Server, Process Manager, Trap Receiver.

B

browser GUI-based hypertext client application, such as Internet Explorer and Netscape Navigator, used to access hypertext documents and other services located on innumerable remote servers throughout the World Wide Web (WWW) and Internet.

C

capability point

code

Point code shared by more than one node, each of which is also assigned a “real” point code. Also called alias point code.

circle In topology maps, indicator for a link that is part of a virtual linkset, associated with the closest node. See topology.

circle layout Topology map layout in which nodes are arranged in a circle, connected by links. Contrast with spring layout. See topology map.

Cisco IOS software Cisco Internetwork Operating System software. Cisco system software that provides common functionality, scalability, and security for many Cisco products. The Cisco IOS software allows centralized, integrated, and automated installation and management of internetworks, while ensuring support for a wide variety of protocols, media, services, and platforms.

CLI Command line interface. An interface that allows the user to interact with the Cisco IOS software operating system by entering commands and optional arguments.

client Node or software program that requests services from a server. The SGM user interface is an example of a client. See also server.

GL-2Cisco Signaling Gateway Manager User Guide

78-15589-01

Glossary

client view User-customized subset of the DEFAULT view. See also DEFAULT view, view.

CLLI code COMMON LANGUAGE Location Identification Code for a node. A CLLI code is a standardized 11-character identifier that uniquely identifies the geographic location of the node.

command line

interface

See CLI.

community name See community string.

community string Text string that acts as a password and is used to authenticate messages sent between a management station and an ITP containing an SNMP agent. The community string is sent in every packet between the manager and the agent. Also called community name, read community.

congestion Condition in which a link has too many packets waiting to be sent. This condition could be caused by the failure of an element in the network. Possible levels are None, Low, High, and Very High, which correspond roughly to equivalent ANSI, China standard, and ITU congestion levels.

console log Log containing unexpected error and warning messages from the SGM server, such as those that might occur if the SGM server cannot start.

cost Measure of the suitability of a route to a destination, relative to other routes. Costs range from 1 (lowest cost and highest priority) through 9 (highest cost and lowest priority).

current view View that is currently in use on an SGM client. The view can be the DEFAULT view or a customized view. Also called current view. See client view, DEFAULT view.

D

Data Server Multi-threaded process that handles most of the work done by SGM, including Discovery, polling, and scheduling. See also Message Log Server, Process Manager, Trap Receiver.


78-15589-01

Glossary

DEFAULT view View into which SGM places all discovered nodes, signaling points, linksets, and links when discovering the network. The DEFAULT view is stored on the SGM server and shared by all SGM clients, but it cannot be modified by the clients. See current view, view.

demand polling User-initiated poll of selected nodes. Contrast with status polling.

destination linkset In ITP route tables, linkset associated with the destination point code. Also called the output linkset. See linkset, destination point code, route table.

destination point

code

In ITP route tables, point code of the adjacent node, the destination for packets on the selected node. See destination linkset, point code, route table.

device See node.

device type In SGM, the type of a discovered device, either a Cisco ITP or a legacy SS7 device. Also called system object ID. See legacy device.

diamond In topology maps, indicator for a link that is part of a configured linkset, associated with the closest node. See topology.

discovered Node, signaling point, linkset, or link that has been discovered by SGM. Also called known. Contrast with unknown.

Discovery Process by which SGM discovers nodes, signaling points, linksets, and links in your network. See also nonrecursive Discovery, recursive Discovery.

display name User-specified name for a node. Contrast with DNS name. See also node name.

domain name The style of identifier—a sequence of case-insensitive ASCII labels separated by dots (“bbn.com.”)—defined for subtrees in the Internet Domain Name System [R1034] and used in other Internet identifiers, such as host names, mailbox names, and URLs.

Domain Name

System

See DNS.


78-15589-01

Glossary

DNS Domain Name System. System used on the Internet for translating names of network nodes into addresses.

DNS name Initial name of a node, as discovered by SGM. Contrast with display name. See also node name.

E

Erlang (E) The international (dimensionless) unit of the average traffic intensity (occupancy) of a facility during a period of time, normally, a busy hour. The number of Erlangs is the ratio of the time during which a facility is occupied (continuously or cumulatively) to the time this facility is available for occupancy. Another definition is the ratio of the average call arrival rate into the system, to the average call duration. One Erlang is equivalent to 36 ccs (completed call seconds), which is another traffic intensity unit.

exclude Removing a node from a view, while retaining the node in the SGM database.

G

graphical element Graphical representation of a node, signaling point, linkset, or link in the topology map. See topology map.

graphical user

interface

See GUI.

GUI Graphical user interface. User environment that uses pictorial as well as textual representations of the input and output of applications and the hierarchical or other data structure in which information is stored. Conventions such as buttons, icons, and windows are typical, and many actions are performed using a pointing device (such as a mouse). Microsoft Windows and the Apple Macintosh are prominent examples of platforms utilizing a GUI.


78-15589-01

Glossary

H

host Computer system on a network. Similar to the term node except that host usually implies a computer system, whereas node generally applies to any network system, including access servers and ITPs. See also node.

host address See host number.

host number Part of an IP address that designates which node on the subnetwork is being addressed. Also called a host address.

HSL High-speed link. An HSL link is one that uses use the SS7-over-ATM (Asynchronous Transfer Mode) high-speed protocol.

HTML Hypertext Markup Language. Simple hypertext document formatting language that uses tags to indicate how a given part of a document should be interpreted by a viewing application, such as a Web browser. See also hypertext and browser.

hypertext Electronically-stored text that allows direct access to other texts by way of encoded links. Hypertext documents can be created using HTML, and often integrate images, sound, and other media that are commonly viewed using a browser. See also HTML and browser.

Hypertext Markup

Language

See HTML.

I

ignore Exclude a linkset or link when aggregating and displaying SGM status information.

installation log Log containing messages and other information recorded during installation.

internal ID Unique identifier assigned by SGM, for its own internal use, to every event, link, linkset, and node.

Internet Protocol See IP.


78-15589-01

Glossary

IP Internet Protocol. Network layer protocol in the TCP/IP stack offering a connectionless internetwork service. IP provides features for addressing, type-of-service specification, fragmentation and reassembly, and security. Documented in RFC 791.

IP address 32-bit address assigned to hosts using TCP/IP. An IP address belongs to one of five classes (A, B, C, D, or E) and is written as 4 octets separated by periods (dotted decimal format). Each address consists of a network number, an optional subnetwork number, and a host number. The network and subnetwork numbers together are used for routing, while the host number is used to address an individual host within the network or subnetwork. A subnet mask is used to extract network and subnetwork information from the IP address. CIDR provides a new way of representing IP addresses and subnet masks. See also IP.

ITP Part of Cisco’s hardware and software SS7-over-IP (SS7oIP) solution. ITP provides a reliable, cost-effective medium for migrating Signaling System 7 (SS7), the telecommunications network signaling technology, to the mobile wireless industry IP environment. ITP off-loads SS7 Short Messaging Service (SMS) traffic onto the IP network, replacing the mobile service provider’s signaling network with a redundant IP cloud.

ITU International Telecommunication Union.

K

known See discovered.

L

legacy device In SGM, an SS7 device that is not a Cisco ITP. Legacy devices include MSCs, SCPs, SSPs, and STPs. See MSC, SCP, SS7, SSP, STP.

link In ITP, the connection between nodes. See ITP, linkset, node.

link type In SGM, the type of a discovered link, either SCTP IP or serial. See SCTP, serial.


78-15589-01

Glossary

linkset In ITP, a grouped set of links. In SGM, a representation of two linksets associated with two nodes, one for each side of a logical connection. See ITP, link, node.

linkset type In SGM, the type of a discovered linkset, either SCTP IP, serial, HSL, mixed, or other. Other means no links have been defined for the linkset. See HSL, SCTP, serial.

local authentication Type of SGM security authentication that allows the creation of user accounts and passwords local to the SGM system. When using this method, user names, passwords, and access levels are managed using SGM commands. Contrast with Solaris authentication.

For more information on Solaris authentication, see the “Implementing SGM User-Based Access (Solaris Only)” section on page 4-2.

local IP address IP address used by the SGM client to connect to the SGM server.

local point code Point code of the primary node for a linkset. Contrast with adjacent point code.

local VPN IP address IP address used by the SGM client to connect to the SGM server via VPN. See local IP address, VPN.

M

managed object Node, signaling point, linkset, or link that is being managed by SGM. See link, linkset, node.

Management

Information Base

See MIB.

mask Bit combination used in SGM to indicate the significant bits of the point code.

For ANSI and China standard networks using the default 24-bit point code format, the default mask is 255.255.255.

For ITU networks using the default 14-bit point code format, the default mask is 7.255.7.


78-15589-01

Glossary

Message Log Server Multi-threaded process that logs messages from the Data Server, Process Manager, and SGM client. See also Data Server, Process Manager, Trap Receiver.

MIB Management Information Base. Database of network management information that is used and maintained by a network management protocol such as SNMP. The value of a MIB object can be changed or retrieved using SNMP commands, usually through a GUI network management system. MIB objects are organized in a tree structure that includes public (standard) and private (proprietary) branches.

mobile switching

center

See MSC.

mouse over help Popups that display information about nodes, signaling points, linksets, and table entries.

MSC Mobile switching center. Provides telephony switching services and controls calls between telephone and data systems.

N

name server Server connected to a network that resolves network names into network addresses.

network

management

system

See NMS.

network view See view.

new node Node that SGM has newly discovered, and that has not yet been added to the current view.


78-15589-01

Glossary

node Endpoint of a network connection or a junction common to two or more lines in a network. Nodes can be processors, controllers, or workstations. Nodes, which vary in routing and other functional capabilities, can be interconnected by links, and serve as control points in the network.

In ITP, a node is a Cisco ITP or a legacy SS7 device (SSP, SCP, or STP).

See legacy device.

node name Name of a node. This is either the DNS name of the node, or a user-specified name. See display name, DNS name.

nonrecursive

Discovery

Discovery of seed nodes only. SGM discovers all seed nodes and attempts to manage them, then marks all nodes that are adjacent to those seed nodes as Unmanaged. Contrast with recursive Discovery.

NMS Network management system. System responsible for managing at least part of a network. An NMS is generally a reasonably powerful and well-equipped computer such as an engineering workstation. NMSes communicate with agents to help keep track of network statistics and resources.

O

output linkset See destination linkset.

P

ping Packet internet groper. ICMP echo message and its reply. Often used in IP networks to test the reachability of a network device.

point code A unique address code that identifies a service provider within a signaling network. Also called primary point code. See capability point code, destination point code, local point code, secondary point code.


78-15589-01

Glossary

polling Access method in which a primary network device inquires, in an orderly fashion, whether secondaries have data to transmit. The inquiry occurs in the form of a message to each secondary that gives the secondary the right to transmit.

poll interval Time between polls.

poll response Time taken by a node to respond to SGM poll requests.

port In IP terminology, an upper-layer process that receives information from lower layers. Ports are numbered, and each numbered port is associated with a specific process. For example, SMTP is associated with port 25. A port number is also called a well-known address.

preferences Settings that enable a user to modify the way SGM presents information.

primary node In SGM, for a given pair of connected nodes, the node that SGM discovered first. See adjacent node.

primary point code See point code.

primary SNMP

address

IP address used by SNMP to poll the node. (There might be other IP addresses on the node that are not the primary SNMP address.) Contrast with secondary IP address.

process Internal component of SGM. See Data Server, Message Log Server, Process Manager, Trap Receiver.

Process Manager Multi-threaded process that handles the management of registered SGM processes. See also Data Server, Message Log Server, Trap Receiver.


78-15589-01

Glossary

Q

QoS Quality of service. Measure of performance for a transmission system that reflects its transmission quality and service availability.

Quality of Service See QoS.

R

read community See community string.

recursive Discovery Discovery of the entire network. SGM discovers all seed nodes and attempts to manage them; then attempts to discover and manage all ITP nodes that are adjacent to those seed nodes (unless the nodes are connected by serial links only); then attempts to discover and manage all ITP nodes that are adjacent to those nodes; and so on, until SGM has discovered the entire network.

Contrast with nonrecursive Discovery.

route Path through an internetwork.

route table Table used in ITP to locate a destination linkset for a packet whose destination point code does not match the ITP's local point code.

routing key Set of SS7 parameters that uniquely define the range of signaling traffic to be handled by a particular application server or application server route table. Thus, the routing key identifies an application server or an application server route table. See application server, application server process, application server process association, signaling gateway mated pair

S

SCP Service control point. An element of an SS7-based Intelligent Network that performs various service functions, such as number translation, call setup and teardown, and so on.


78-15589-01

Glossary

SCTP Stream Control Transmission Protocol. An end-to-end, connection-oriented protocol that transports data in independent sequenced streams.

secondary IP

address

Alternate or backup IP address used by a node. Contrast with primary SNMP address.

secondary point

code

Alternate or backup point code used by a node. See point code.

seed file List of seed nodes. See seed node.

seed node Node used by SGM to discover the other nodes, signaling points, linksets, and links in your network.

serial Method of data transmission in which the bits of a data character are transmitted sequentially over a single channel.

server Node or software program that provides services to clients. See client.

service control point See SCP.

service switching

point

See SSP.

signaling gateway

mated pair

Pair of signaling gateways that exchange necessary state information using the Signaling Gateway Mate Protocol (SGMP). See application server, application server process, application server process association, routing key

signaling point See SP.

signal transfer point See STP.

Signaling System 7 See SS7.

Simple Network

Management

Protocol

See SNMP.

SNMP Simple Network Management Protocol. Network management protocol used almost exclusively in TCP/IP networks. SNMP provides a means to monitor and control network devices, and to manage configurations, statistics collection, performance, and security.


78-15589-01

Glossary

Solaris

authentication

Type of SGM security authentication that uses standard Solaris-based user accounts and passwords, as specified in the /etc/nsswitch.conf file. Authentication can be provided by the local /etc/passwd file or from a distributed Network Information Services (NIS) system. Contrast with local authentication.

For more information on Solaris authentication, see the “Implementing SGM User-Based Access (Solaris Only)” section on page 4-2.

SP Signaling point. An SCP, SSP, or STP, or an ITP instance. See SCP, SSP, or STP.

spring layout Topology map layout in which nodes are arranged in a spring layout. Nodes with the most links are drawn closer to the center of the map, while nodes with fewer links are drawn farther away. Contrast with circle layout. See topology map.

SS7 Signaling System 7. Standard CCS system used with BISDN and ISDN. Developed by Bellcore.

SSP Service switching point. Element of an SS7-based Intelligent Network that performs call origination, termination, or tandem switching.

status Current condition, such as Active or Unknown, of a node, signaling point, linkset, or link.

status polling Regularly scheduled polling of nodes performed by SGM. Contrast with demand polling.

STP Signal transfer point. Element of an SS7-based Intelligent Network that performs routing of the SS7 signaling.

Stream Control

Transmission

Protocol

See SCTP.

super user User specified in SGM to be able to perform most functions that otherwise require the user to be logged in as the root user.

For more information, see the “Specifying a Super User (Solaris Only)” section on page 4-22.

system object ID See device type.


78-15589-01

Glossary

T

TCP Transmission Control Protocol. Connection-oriented transport layer protocol that provides reliable full-duplex data transmission. TCP is part of the TCP/IP protocol stack. See also TCP/IP.

TCP/IP Transmission Control Protocol/Internet Protocol. Common name for the suite of protocols developed by the U.S. DoD in the 1970s to support the construction of worldwide internetworks. TCP and IP are the two best-known protocols in the suite. See also IP and TCP.

thread name Task name.

timeout Event that occurs when one network device expects to hear from another network device within a specified period of time, but does not. The resulting timeout usually results in a retransmission of information or the dissolving of the session between the two devices.

topology See topology map.

topology map Graphical representation by SGM of the network. Also called topology.

Transmission

Control Protocol

See TCP.

Transmission

Control

Protocol/Internet

Protocol

See TCP/IP.

trap Unsolicited message sent by an SNMP agent to an NMS, console, or terminal to indicate the occurrence of a significant event, such as a specifically defined condition or a threshold that has been reached.

Trap Receiver Multi-threaded process that receives SNMP traps for SGM. See also Data Server, Message Log Server, Process Manager.


78-15589-01

Glossary

U

UDP User Datagram Protocol. Connectionless transport layer protocol in the TCP/IP protocol stack. UDP is a simple protocol that exchanges datagrams without acknowledgments or guaranteed delivery, requiring that error processing and retransmission be handled by other protocols. UDP is defined in RFC 768.

unknown Device type for which SGM is unable to determine the device type. If a node, the node failed to respond to an SNMP request. If a linkset or link, either the associated node failed to respond to an SNMP request, or SGM found that the linkset or link no longer exists. Contrast with discovered.

unmanaged Node status in which the node is known indirectly by SGM (SGM knows the device exists but there is no known SNMP stack on the device for SGM to query), or a user has set the node to this status to prevent SGM from polling the node.

User-Based Access SGM security scheme that provides multi-level password-protected access to SGM features. Each user can have a unique user name and password. Each user can also be assigned to one of five levels of access, which control the list of SGM features accessible by that user.

For more information, see the “Configuring SGM User-Based Access” section on page 4-1.

User Datagram

Protocol

See UDP.


78-15589-01

Glossary

V

view View that is currently in use on an SGM client. The current view can be the DEFAULT view or a customized view. See client view, current view, DEFAULT view.

Virtual Private

Network

See VPN.

VPN Virtual Private Network. Enables IP traffic to travel securely over a public TCP/IP network by encrypting all traffic from one network to another. A VPN uses “tunneling” to encrypt all information at the IP level.

W

World Wide Web See WWW.

WWW World Wide Web. Large network of Internet servers providing hypertext and other services to terminals running client applications such as a browser. See also browser.


78-15589-01

Glossary


78-15589-01

Cisco Sig78-15589-01

I N D E X

A

accessing

Cisco.com 7-124

SGM Server Home Page 7-2

SGM Software Home Page 7-124

SGM Software Page 7-124

software updates 7-124

all archived messages, viewing on Web 7-110

all archived status change and SNMP trap messages, viewing on Web 7-96

all current messages, viewing on Web 7-109

annotating

events 3-256

linksets 3-84

nodes 3-124

ANSI point code format, setting 5-21

architecture, client/server 1-5

attaching notes

to events 3-256

to linksets 3-84

to nodes 3-124

audience, document xviii

B

backing up SGM database 5-47

basic information

for events 3-236

for linksets 3-38

for nodes 3-92

becoming the root user 3-2

C

changing

age of message log files 5-21

default server name 3-404, 3-405

default view 3-26

directory for messages 5-20

size of message log file 5-21

time mode for message log files 5-21

circle layout, topology 3-259

CiscoView, launching 3-403

CiscoWorks2000

integrating with SGM 3-402

launching CiscoView 3-403

launching Device Center 3-402

clearing locked-up display 6-2

IN-1naling Gateway Manager User Guide

Index

client, launching SGM client in Windows 3-404

client access, limiting 4-38

client information, viewing on Web 7-116

client software, description 1-5

CLLI Code 3-92

colors

meaning in topology 3-259

modifying for network status messages 7-96

columns, making wider or narrower 3-279

command log, viewing on Web 7-111

commands B-1

output of sgm export B-71

output of sgm gttcheck B-71

output of sgm status B-70

configuring

backup SGM server 5-50

security 4-1

seed files 3-20

SGM User-Based Access 4-1

SNMP 3-2

user authentication level 4-6

connecting to new server 3-399

console log, viewing on Web 7-110

console log archives, viewing on Web 7-111

conventions, document xix

CPU processes for a node, viewing on Web 7-17

creating

seed files 3-20

views 3-26

IN-2Cisco Signaling Gateway Manager User Guide

current view 3-26

custom point code format, setting 5-21

D

data problems, investigating 6-2

debug messages, viewing on Web 7-106

default server name, changing 3-404, 3-405

DEFAULT view 3-26

deleting links

from SGM database 3-234

from your network 3-233

overview 3-233

deleting linksets

from SGM database 3-88, 3-167

from your network 3-88, 3-167

overview 3-88

deleting nodes

from Discovery database 3-132

from SGM database 3-130

from your network 3-130

overview 3-130

detailed information

for events 3-243

for links 3-175

for linksets 3-42

for nodes 3-96

Device Center, launching 3-402

diagnosing typical network problems 6-4

78-15589-01

Index

discovering the network 3-6

Discovery

database, deleting nodes from 3-132

nonrecursive 3-6

procedure 3-6

recursive 3-6

verifying 6-1

displaying ITP home page 7-124

DISPLAY variable, setting 5-47

document

audience xviii

conventions xix

objectives xviii

organization xviii

documentation

Cisco IOS software xxi

Cisco SGM xxi

online Help xxi

DOS prompt, launching from Windows Start Menu 3-405

downloading

SGM client software 7-123

SSL certificate 4-28

dump messages, viewing on Web 7-107

78-15589-01

E

editing

events 3-256

GTT table file 3-290

linksets 3-84

nodes 3-124

non-SGM route table E-1

route table file 3-281

seed files 3-24

enabling

SNMP traps 5-23

error messages, viewing on Web 7-100

event configuration, modifying 5-26

events

annotating 3-256

attaching notes to 3-256

editing 3-256

filtering 3-244

viewing basic information 3-236

viewing detailed information 3-243

viewing notes for 3-258

viewing overview 3-235

working with 3-235

excluding nodes from views 3-26

exiting the SGM client 2-7


Index

F

FAQs A-1

filtering events 3-244

finding

linksets in the topology 3-259

nodes in the topology 3-259

firewall network option D-5

format

of GTT table files 3-290

of route table files 3-281

of seed files 3-24

frequently asked questions A-1

G

GTT client, launching SGM client in Windows 3-404

GTT MAP status, viewing on Web 7-30

GTT table files

editing 3-290

format of 3-290

modifying 3-290

saving 3-290

viewing on Web 7-120


H

hiding tables 3-279

highlighting elements in topology 3-259

HP OpenView, integrating with SGM 3-401

I

ignoring

links 3-235

linksets 3-90

importing SNMP community names 5-2

informational messages, viewing on Web 7-101, 7-102

installation, SGM client 7-123

integrating SGM

with CiscoWorks2000 3-402

with HP OpenView 3-401

with other products 3-401

interface details for a link, viewing on Web 7-61

investigating data problems 6-2

IOS information, viewing on Web 7-121

IOS version for a node, viewing on Web 7-16

ITP, Telnetting to 5-52

ITP home page, displaying 7-124

ITP overview 1-1

ITU point code format, setting 5-21

78-15589-01

Index

L

launching

CiscoView 3-403

Device Center 3-402

DOS prompt 3-405

SGM client 3-404

SGM GTT client 3-404

SGM SSL Certificate Tool 3-406

limiting

client access 4-38

traps by IP address 5-45

link dashboard, viewing on Web 7-50

links

deleting 3-233

ignoring 3-235

overview 3-170

status, viewing on Web 7-51


working with 3-170

linkset dashboard, viewing on Web 7-34

linkset details, viewing on Web 7-38

linksets

annotating 3-84


deleting 3-88

editing 3-84

ignoring 3-90


78-15589-01



viewing notes 3-87

loading

seed files 3-22

views 3-26

locked-up display, clearing 6-2

M

M2PA peer details for a link, viewing on Web 7-64

magnetic grid, topology 3-259

making columns wider or narrower 3-279

managing nodes 3-133

messages

action 7-102

all archived 7-110

all archived status change and SNMP trap 7-96

all current 7-109

changing age of file 5-21

changing directory 5-20

changing size of file 5-21

changing time mode for file 5-21

debug 7-106

dump 7-107

error 7-100

informational 7-101

modifying age of file 5-21


Index

modifying colors for network status messages 7-96

modifying directory 5-20

modifying display 5-20

modifying size of file 5-21

modifying time mode for file 5-21

network status 7-5

SNMP 7-108

SNMP trap 7-93

SNMP trap and status change combined 7-86

status change 7-90

status change and SNMP trap combined 7-86

trace 7-105

viewing on Web 7-1

MIBs reference C-1

modifying

age of message log files 5-21

colors for network status messages 7-96

directory for messages 5-20

event configuration 5-26

GTT table file 3-290

message display 5-20

number of rows in Web output 7-4

preference settings 5-3

route table file 3-281

seed files 3-22

SgmEvent.conf file 5-26

size of message log file 5-21

time mode for message log files 5-21

views 3-26


Web output 7-4

Web update interval 7-4

mouse over help in topology 3-259

moving nodes in topology 3-259

multiple clients, starting 2-7

N

naming, preferences file 5-3

NAT network option D-4

network

deleting links from 3-233

deleting nodes from 3-130

diagnosing problems in 6-4

discovering 3-6

network option

firewall D-5

NAT D-4

overview D-1

port-forwarding D-8

SSL D-11

VPN D-2

network status information, viewing on Web 7-5

network status metrics, viewing on Web 7-97

network views, viewing on Web 7-120

new nodes

in topology 3-259

in views 3-26

new server, connecting to 3-399

78-15589-01

Index

node dashboard, viewing on Web 7-6

nodes

annotating 3-124


deleting 3-130

details, viewing on Web 7-10

editing 3-124

managing 3-133

polling 3-134


unmanaging 3-133



viewing notes 3-128

nonrecursive Discovery 3-6

notes

attaching to events 3-256

attaching to linksets 3-84

attaching to nodes 3-124

viewing, for events 3-258

viewing, for linksets 3-87

viewing, for nodes 3-128

viewing, on Web 7-120

number of rows in Web output, modifying 7-4

O

objectives, document xviii

online help, viewing 3-280

78-15589-01

organization, document xviii

other products, integrating SGM with 3-401

output

sgm export command B-71

sgm gttcheck command B-71

sgm status command B-70

P

passwords

automatically disabling 4-10

enabling 4-15

manually disabling 4-13

modifying 4-15

point code format, setting 5-21

polling nodes 3-134

port-forwarding network option D-8

preferences

file naming 5-3

modifying settings 5-3

saving 5-3


printing

SGM windows 3-398

topology 3-259

problems, diagnosing 6-4


Index

Q

Q.752 measurements for a link, viewing on Web 7-58

questions about SGM A-1

R

README file, viewing from Windows Start Menu 3-406

recursive Discovery 3-6

redrawing topology 3-259

related documentation xxi

removing nodes from a view 3-26

removing SGM data from server 5-48

resizing tables 3-279

resorting tables 3-279

restoring SGM database 5-47

retaining unknown objects 5-3

root access, becoming the root user 3-2

root variables, viewing on Web 7-121

route detail, viewing on Web 7-32

route table files

editing 3-281

format of 3-281

modifying 3-281

non-SGM E-1, F-1

saving 3-281


SGM 3-281


running simultaneous sessions 2-7

S

saving

GTT table files 3-290

preferences 5-3

route table files 3-281

seed files 3-20

views 3-26

security

configuring 4-1

maintaining 4-17

security log, viewing on Web 7-112, 7-113

seed files

configuring 3-20

creating 3-20

editing 3-24

format of 3-24

loading 3-22

modifying 3-22

saving 3-20


server

changing default name 3-404, 3-405

connecting to new 3-399

78-15589-01

Index

software, description 1-5

viewing status information 7-116

services, viewing on Web 7-121

setting DISPLAY variable 5-47

setting point code format 5-21

SGM

client, launching from Windows Start Menu 3-404

commands B-1

configuring backup server 5-50

data, removing from server 5-48

FAQs A-1

GTT client, launching from Windows Start Menu 3-404

help output, viewing on Web 7-121

integrating with CiscoWorks2000 3-402

integrating with HP OpenView 3-401

integrating with other products 3-401

network options D-1

overview 1-2

starting 2-2

technical documentation, viewing on Web 7-122

uninstalling, from Windows Start Menu 3-406

viewing data on Web 6-4

SGM client

exiting 2-7

installing 7-123

78-15589-01

SGM database

backing up 5-47

deleting linksets from 3-88, 3-167

deleting links from 3-234

deleting nodes from 3-130

ignoring linksets 3-90

restoring 5-47

SgmEvent.conf file, modifying 5-26

SGM Server Home Page, accessing 7-2

SGM Software Home Page, accessing 7-124

SGM Software Page, accessing 7-124

SGM SSL Certificate Tool, launching from Windows Start Menu 3-406

SGM User-Based Access, configuring 4-1

signaling point details, viewing on Web 7-26

sizing tables 3-279

SNMP

community names, importing 5-2

configuring 3-2

messages, viewing on Web 7-108

trap messages, viewing on Web 7-93

traps, enabling 5-23

SNMP trap and status change messages, viewing on Web 7-86

software

SGM client description 1-5

SGM server description 1-5

updates, accessing 7-124

sorting tables 3-279

spring layout, topology 3-259


Index

SSL

downloading certificate 4-28

implementing in SGM 4-24

network option D-11

starting

multiple clients 2-7

SGM 2-2

status change and SNMP trap messages combined, viewing on Web 7-86

status change messages, viewing on Web 7-90

super user

access 4-22

specifying 4-22

system data files, viewing on Web 7-120

system information, viewing on Web 7-121

system log messages, viewing

on Web 7-19

system properties, viewing on Web 7-121

system status information, viewing on Web 7-115

T

tables

hiding 3-279

resizing 3-279

sorting 3-279

technical documentation for SGM, viewing on Web 7-122

Telnetting to an ITP 5-52


topology

circle layout 3-259

colors in 3-259

displaying detailed information 3-259

finding linksets in 3-259

finding nodes in 3-259

highlighting elements in 3-259

magnetic grid 3-259

mouse over help 3-259

moving nodes in 3-259

new nodes in 3-259

printing 3-259

redrawing 3-259

spring layout 3-259

viewing 3-259

zooming 3-259

trace messages, viewing on Web 7-105

trap host configuration for a node, viewing on Web 7-20

traps, enabling SNMP 5-23

troubleshooting

clearing locked-up display 6-2

diagnosing typical problems 6-4

investigating data problems 6-2

verifying Discovery 6-1

viewing for events 6-4

viewing SGM data on Web 6-4

viewing troubleshooting log 6-3

78-15589-01

Index

troubleshooting log, viewing

from SGM Server Home Page 7-119

from the command line 6-3

on Web 7-119

U

uninstalling SGM from Windows Start Menu 3-406

unknown objects, retaining 5-3

unmanaging nodes 3-133

user account information, viewing on Web 7-116, 7-118

user accounts

automatically disabling 4-10

enabling 4-15

manually disabling 4-13

modifying 4-15

user authentication level

Basic User 4-6

configuring 4-6

Level 1 4-6

Level 2 4-7

Level 3 4-8

Level 4 4-8

Level 5 4-9

Network Administrator 4-8

Network Operator 4-8

Power User 4-7

System Administrator 4-9

78-15589-01

User-Based Access, configuring 4-1

using Windows Start Menu 3-403

V

verifying Discovery 6-1

version information, viewing on Web 7-116

viewing

action messages, on Web 7-102

all archived messages, on Web 7-110

all archived status change and SNMP trap, on Web 7-96

all current messages, on Web 7-109

basic information for events 3-236

basic information for linksets 3-38

basic information for nodes 3-92

client information, on Web 7-116

command log, on Web 7-111

console log, on Web 7-110

console log archives, on Web 7-111

CPU processes for a node, on Web 7-17

debug messages, on Web 7-106

detailed information for events 3-243

detailed information for links 3-175

detailed information for linksets 3-42

detailed information for nodes 3-96

dump messages, on Web 7-107

error messages, on Web 7-100

events, overview 3-235

GTT files, on Web 7-120


Index

GTT MAP status, on Web 7-30

informational messages, on Web 7-101

installation log, on Web 7-121

interface details for a link, on Web 7-61

IOS information, on Web 7-121

IOS version for a node, on Web 7-16

link dashboard, on Web 7-50

links, overview 3-170

linkset dashboard, on Web 7-34

linkset details, on Web 7-38

linksets 3-37

linkset status, on Web 7-35

link status, on Web 7-51

M2PA peer details for a link, on Web 7-64

messages, on Web 7-1

network status information, on Web 7-5

network status metrics, on Web 7-97

network views, on Web 7-120

node dashboard, on Web 7-6

node details, on Web 7-10

nodes 3-91

node status, on Web 7-6

notes, on Web 7-120

notes for events 3-258

notes for linksets 3-87

notes for nodes 3-128

online help 3-280

preferences, on Web 7-120

Q.752 measurements for a link, on Web 7-58


README file, from Windows Start Menu 3-406

README file, on Web 7-121

root variables, on Web 7-121

route detail, on Web 7-32

route table files, on Web 7-120

security log, on Web 7-112, 7-113

seed files, on Web 7-120

server status, on Web 7-116

services, on Web 7-121

SGM data, on Web 6-4

SGM help output, on Web 7-121

SGM technical documentation, on Web 7-122

signaling point details, on Web 7-26

SNMP messages, on Web 7-108

SNMP trap messages, on Web 7-93

status change and SNMP trap messages combined, on Web 7-86

status change messages, on Web 7-90

system data files, on Web 7-120

system information, on Web 7-121

system log messages, on Web 7-19

system properties, on Web 7-121

system status information, on Web 7-115

topology, overview 3-259

trace messages, on Web 7-105

trap host configuration for a node, on Web 7-20

troubleshooting for events 6-4

troubleshooting log, from the command line 6-3

78-15589-01

Index

troubleshooting log, on Web 7-119

user account information, on Web 7-116, 7-118

version information, on Web 7-116

Web access log, on Web 7-115

Web error log, on Web 7-114

views

changing the default view for an SGM client 3-26

creating 3-26

current view 3-26

customizing 3-26

DEFAULT view 3-26

excluding nodes from 3-26

loading 3-26

modifying 3-26

new nodes in 3-26

removing nodes from 3-26

saving 3-26

switching between 3-26

VPN network option D-2

W

Web

access log 7-115

client information 7-116

command log 7-111

console log 7-110

console log archives 7-111

CPU processes for a node 7-17

78-15589-01

error log 7-114

GTT MAP status 7-30

interface details for a link 7-61

IOS version for a node 7-16

link dashboard 7-50

linkset dashboard 7-34

linkset details 7-38

linkset status 7-35

link status 7-51

M2PA peer details for a link 7-64

network status metrics 7-97

node dashboard 7-6

node details 7-10

node status 7-6

output, modifying 7-4

Q.752 measurements for a link 7-58

route detail 7-32

security log 7-112, 7-113

signaling point details 7-26

system log messages 7-19

trap host configuration for a node 7-20

update interval, modifying 7-4

user account information 7-116, 7-118

Web access log 7-115

Web error log 7-114

windows

printing 3-398


Index

Windows Start Menu

changing default server name 3-404, 3-405

launching DOS prompt 3-405

launching SGM client 3-404

launching SGM GTT client 3-404

launching SGM SSL Certificate Tool 3-406

overview 3-403

uninstalling SGM 3-406

viewing README file 3-406

working

with events 3-235

with links 3-170

with linksets 3-37

with nodes 3-91

Z

zooming topology 3-259


78-15589-01

Cisco · Cisco Reader Comment Card General Information 1 Years of networking experience: Years of...

Documents

Transcript of Cisco · Cisco Reader Comment Card General Information 1 Years of networking experience: Years of...