Cisco Media Gateway Manager 5.0 User Guide Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.
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.
C O N T E N T S Preface xxvii Changes to the User Guide Audience xxvii xxvii Documentation xxvii Technical Manual Order of Use xxvii Technical Manual Titles and Descriptions xxviii Obtaining Documentation xxviii Cisco.
Contents 2.1.4 Using Control Panel 2-7 2.1.5 Using Wizards 2-8 2.1.6 Paging through Data 2-9 2.1.7 Finding Data 2-9 2.1.7.1 Finding Data in the Domain Explorer 2-9 2.1.7.2 Finding Data in the Diagnostic Center, Statistics Report, Chassis View, and Configuration Center 2-9 2.1.8 Navigating the Client Desktop 2-9 2.1.8.1 Using Popup Menus 2-10 2.1.9 Using Mnemonics 2-10 2.1.10 Using the Online Help 2-10 2.1.11 Using the Pin Tool 2-11 2.2 What Basic Functions Can I Perform in Cisco MGM? 2-11 2.2.
Contents 2.3.6.3 Diagnostic Operations for Connections 2-25 2.3.7 Managing Cisco MGM CORBA Interfaces 2-26 CHAPTER 3 Planning the Network 3.1 Network Planning 3-1 3-1 3.2 What Network Elements Are Available to a Network Planner? 3.2.1 Cisco MGX 8880 Media Gateway 3-2 3.2.2 Cisco MGX 8850 Multiservice Switch 3-2 3.2.3 Cisco PXM-45 Processor Switch Module 3-2 3.2.4 Cisco Voice Switch Service Module 3-3 3.2.5 Cisco Voice Interworking Service Module 3-4 3.2.6 Cisco Route Processor Module 3-4 3.2.
Contents 4.3.4.2 Deleting Multiple Groups 4-14 4.4 How Do I Configure the SNMP Community String? 4-14 4.4.1 Setting Up Nonstandard Community Strings 4-15 4.4.2 Changing Community Strings Using the Domain Explorer 4-16 4.4.3 Changing Community Strings Using the CLI 4-16 4.4.4 Changing Service Level Passwords Using the Domain Explorer 4-17 4.4.5 Changing the Service Level Passwords Using the CLI 4-17 4.5 How Do I Build Network Maps? 4-18 4.5.1 Customizing a Network Map 4-18 4.5.
Contents 5.1.4 Pruning the Database 5-13 5.1.4.1 Setting the Time and Date for Automatic Pruning 5-13 5.1.4.2 Using Pruning Scripts 5-14 5.1.5 Using the SQL*PLUS Client to Manage the Database 5-16 5.1.6 Basic SQL Commands for Cisco MGM Schema Objects 5-17 5.1.7 Enhancing Database Performance 5-18 5.1.8 Removing an Old Version of the Cisco MGM Database 5-18 5.2 How Do I Monitor the Network? 5-19 5.2.1 Establishing a Telnet Session to a Node 5-19 5.2.2 Connecting to Nodes Through Secured Shell 5-20 5.2.
Contents 5.3.6.1 Updating the Configuration Files after Changing the Cisco MGM Server IP Address 5-42 5.3.7 Viewing and Modifying Server Configuration Information 5-43 5.3.8 Restoring Server Configuration Files 5-43 5.3.9 Initializing the Node Resync Process 5-44 5.3.10 Configuring Application-Specific Parameters 5-45 5.3.11 Using UNIX-Level Scripts 5-45 5.4 How Do I Manage the Network Software? 5-46 5.4.1 Downloading Software Images 5-47 5.5 How Do I Manage Redundancy and Failover? 5-49 5.5.
Contents 6.4.2 Displaying Cards Within a Node 6-15 6.4.3 Verifying a Specific Card for the Node 6-16 6.4.4 Managing Node Peripherals 6-19 6.4.4.1 Displaying IP Interfaces 6-19 6.4.4.2 Configuring Serial Interfaces 6-20 6.4.4.3 Displaying Sensors 6-23 6.4.5 Viewing Node Controllers 6-25 6.4.6 Managing Node Clocking 6-26 6.4.6.1 Configuring Global Clocking 6-26 6.4.6.2 Viewing Available Clock Sources 6-27 6.4.6.3 Viewing or Creating Manual Clock Sources 6.5 How Do I Create or Modify APS? 6-28 6-31 6.
Contents 6.7.5.2 Creating a VIF for VXSM 6-74 6.7.5.3 Viewing or Modifying VIF Configuration 6-76 6.7.6 Configuring MG-MGC Interfaces 6-77 6.7.6.1 Setting Up MGCs and MGC Groups 6-79 6.7.6.2 Configuring H.248 Protocol and Profiles 6-87 6.7.6.3 Configuring XGCP Protocol 6-96 6.7.6.4 Configuring MGC XGCP Profiles 6-98 6.7.6.5 Configuring MGC Redundancy 6-101 6.7.7 How Do I Configure VXSM Features? 6-101 6.7.7.1 Creating a RUDP Session 6-102 6.7.7.2 Configuring Voiceband Data 6-108 6.7.7.
Contents CHAPTER 7 Provisioning Connections 7-1 7.1 What Is Connection Provisioning? 7-1 7.2 What Types of Connection Are Available? 7-1 7.2.1 What Are the Supported Connection Service Types? 7-2 7.3 Where Do I Find Information About Connections? 7-2 7.3.1 Finding Information in the Connection List Tab 7-2 7.3.2 Displaying All Existing Connections 7-4 7.3.3 Displaying Connections of the Same Type 7-4 7.3.4 Editing the Filter Settings 7-5 7.
Contents 8.3.3.4 Deleting a User Profile 8-12 8.3.3.5 Duplicating a User Profile 8-12 8.3.4 Performing User Administration 8-13 8.3.4.1 Managing the Cisco MGM Default User Profiles 8-13 8.3.4.2 Viewing the Cisco MGM Users Table 8-17 8.3.4.3 Creating a Cisco MGM User 8-18 8.3.4.4 Modifying a Cisco MGM User’s Properties 8-20 8.3.4.5 Deleting a Cisco MGM User 8-23 8.3.4.6 Viewing Logged In Cisco MGM Users 8-23 8.3.4.7 Ending an Active Cisco MGM User Session 8-23 8.3.4.
Contents 9.4 Is the Service Working? 9-13 9.4.1 Viewing Service Status 9-14 9.4.2 Viewing Alarms 9-15 9.4.3 Setting Up and Viewing Alarm Configuration Parameters 9-15 9.4.4 Displaying the Status of all Nodes in the Network 9-18 9.4.5 Displaying the Status of a Node 9-19 9.4.6 Displaying the Status of a Card 9-19 9.4.7 Displaying the Status for Lines or Ports 9-20 9.4.8 Displaying the Status for Paths in a Loopback for the VXSM-OC3 Card 9-21 9.4.9 Displaying the Status for Lines in a Loopback 9-22 9.4.
Contents 9.7.3 Filtering Data by Time 9-47 9.8 Who Is Responsible for Managing the Fault? 9-48 9.8.1 Configuring Alarm Acknowledgement and Alarm Notes 9.8.2 Acknowledging and Unacknowledging Alarms 9-49 9.9 How Did You Manage the Fault? 9-50 9.9.1 Archiving Alarm Log 9-50 9.9.2 Exporting Alarms and Events to a Text File CHAPTER 10 Managing Performance 9-48 9-52 10-1 10.1 What Is Performance Management? 10-1 10.2 What Performance Data Is Available? 10-2 10.2.1 Types of Report 10-3 10.2.1.
Contents 10.6 How Is Performance Data Stored? 10-21 10.6.1 Importing and Exporting Data to and from the Oracle Database CHAPTER 11 Managing Inventory 11-1 11.1 What is Inventory Management? CHAPTER 12 10-22 11-1 11.2 Domain NE Tables 11-2 11.2.1 Viewing a Domain NE Table 11-2 11.2.2 Filtering Results in a Domain NE Table 11-3 11.3 Equipment Inventory Tables 11-4 11.3.1 Viewing an Equipment Inventory Table 11-4 Managing CORBA Interfaces 12-1 12.1 What is Cisco MGM GateWay/CORBA? 12-1 12.1.
Contents A.5 Inspector View Icons A-19 A.6 Network Map Icons A-20 A.6.1 Icon States A-20 A.6.2 Icon Colors A-21 A.6.3 Operational and Communication State Icons A.6.4 Network Map Edit Menu A-23 APPENDIX B Error Messages B-1 B.1 Cisco MGM Client Error and Warning Messages APPENDIX C B.2 Cisco MGM Server Error Messages B.2.1 Critical Server Error Messages B.2.2 Major Server Error Messages B.2.3 Minor Server Error Messages B.2.4 Debug Server Error Messages B-61 B.
Contents C.3.4 C.3.5 C.3.6 C.3.7 Cannot Customize the Network Map C-11 Color Settings when the Cisco MGM Client Is Run on a Sun Ultra 5 Workstation? How Do I Collect Thread Dumps? C-12 Launching Help on a Solaris Client C-13 C-11 C.4 Topology Problems C-14 C.4.1 Discovery Mechanism C-14 C.4.2 Discovery Issues at Startup C-14 C.4.2.1 No Nodes Are Discovered C-14 C.4.2.2 Node Name Is Incorrect in Database C-15 C.4.2.3 Node IP Is Incorrect in Database C-15 C.4.2.
Contents C.6.2.1 Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs Do Not Show Any Nodes C-35 C.6.2.2 Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs Are Unable to Connect to Server C-36 C.6.2.3 Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs Do Not Show a Newly Added Node C-36 C.6.3 Topology Discovery Issues C-37 C.6.3.
Contents C.7.7 RPM Card Status not Updated C-53 C.7.8 RPM Secondary Card Status Is Blue C-53 C.7.9 Lines Not Displayed in Secondary Card C-53 C.7.10 Lines Not Selectable C-53 C.7.11 Wrong Tooltip Is Displayed C-53 C.8 Configuration Management - Elements C-54 C.8.1 Configuration Center Framework C-54 C.8.1.1 Cannot Launch Configuration Center C-55 C.8.1.2 Cannot Launch Other Application from Configuration Center C-55 C.8.1.3 Exception Raised When Configuration Center Is Launched C-56 C.8.1.
Contents C.9.1.7 Cross Application—Connection List as Drag Source C-70 C.9.1.8 Cross Application—Connection Tab's Content Pane as Drop Target C-70 C.9.1.9 Configuration Center's Connection Tab Does Not Respond (GUI Is Grayed-Out) C-71 C.9.2 Configuration Center GUI; CM Server Reported Errors C-71 C.9.2.1 Connection Creation/Modification/Deletion/Retrieval Errors C-71 C.9.2.2 Connection Template Creation/Modification/Deletion/Retrieval Errors C-73 C.9.3 Cmsvr Errors C-74 C.9.3.
Contents C.10.2.4 Node Resync Fails C-100 C.10.2.5 Polling of Real Time Counters Fails C-100 C.10.2.6 Some Real Time Counters Are Not Shown C-101 C.10.2.7 Unable to Start/Stop/Modify BERT Operations C-101 C.10.2.8 Unable to Start/Stop IMA Link Test Patterns C-102 C.10.2.9 Cannot Perform Connection Diagnostics C-102 C.10.2.10 Miscellaneous Issues / Problems in Diagnostics Center C-103 C.11 Performance Management Collection and Parsing Problems C-103 C.11.1 PM Collection Issues C-103 C.11.1.
Contents C.15 Miscellaneous Problems C-114 C.15.1 NTS C-114 C.15.1.1 Nodes Stay in Mode 1 After Cold Start C-114 C.15.1.2 Config Change or Provisioning Activity Not Reflected on Cisco MGM C-115 C.15.1.3 How To Interpret NTS Log C-115 C.15.2 Data Inconsistency C-116 C.15.2.1 Connection Inconsistency Between the Switch and GUI C-116 C.15.2.2 Inconsistent Connection Status C-119 C.15.2.3 Inconsistent Connection Secondary Status C-120 C.15.2.4 Incomplete Connections C-120 C.15.3 Cisco MGM FTP Daemon C-121 C.
Contents D.4.1 AXSM Card Statistics D-30 D.5 Path Statistics D-32 D.5.1 VXSM STS Path Statistics D-32 D.5.2 VXSM DS3 Path Statistics D-34 D.5.3 VXSM DS1 N DS3 Path Statistics D-35 D.5.4 VXSM DS1 VT Path Statistics D-38 D.6 PNNI Network Statistics D-41 D.6.1 PNNI Nodal Statistics D-41 D.6.2 PNNI Port Statistics D-42 D.7 Protocol Statistics D-43 D.7.1 VXSM Megaco Statistics D-43 D.7.2 VXSM Megaco Physical Termination Protocol Statistics D-46 D.7.
Contents E.16 RPM-EndPoint-Connection—Supported Real-Time Counters E.17 RPM-ETHERNET-Line—Supported Real-Time Counters E.18 RPM-Port—Supported Real-Time Counters E-56 E-56 E-60 E.19 RPM-SONET-Line—Supported Real-Time Counters E-60 E.20 RPM-VirtualPort—Supported Real-Time Counters E-64 E.21 MGX2-SRM-Card—Supported Real-Time Counters E-64 E.22 MGX2-SRM-DS3-Line—Supported Real-Time Counters E-65 E.23 MGX2-SRM-SONET-Line—Supported Real-Time Counters E-70 E.
Contents F.2 Bouncy Castle F.3 jacORB F-3 F-4 GLOSSARY INDEX Cisco Media Gateway Manager 5.
Contents Cisco Media Gateway Manager 5.
Preface The Cisco Media Gateway Manager 5.0 User’s Guide describes how to use the Cisco Media Gateway Manager (Cisco MGM) 5.0 software. Changes to the User Guide This User Guide is updated as follows: • Part numbers for VXSM Front and Back cards updated. See Table 1-1. Audience This guide is designed for system administrators and users who are responsible for the operation of the Cisco MGM application. Documentation A Guide to Cisco Multiservice Switch Documentation ships with your product.
Preface Obtaining Documentation Step 7 Additional books, such as command reference guides and error message books, can help with the daily operation and maintenance of your switch. Technical Manual Titles and Descriptions Table 1 lists the technical manuals and release notes that support this release. Table 1 Technical Manuals and Release Notes for Cisco Media Gateway Manager Document Title and Part Number Part Number Description Release Notes for Cisco Media Gateway Manager 5.
Preface Documentation Feedback Cisco.com You can access the most current Cisco documentation at this URL: http://www.cisco.com/univercd/home/home.htm You can access the Cisco website at this URL: http://www.cisco.com You can access international Cisco websites at this URL: http://www.cisco.com/public/countries_languages.shtml Ordering Documentation You can find instructions for ordering documentation at this URL: http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.
Preface Obtaining Technical Assistance Cisco Technical Support Website The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL: http://www.cisco.com/techsupport Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password.
Preface Obtaining Additional Publications and Information Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation. Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional.
Preface Obtaining Additional Publications and Information Cisco Media Gateway Manager 5.
C H A P T E R 1 Introduction This chapter describes Cisco Media Gateway Manager, and gives a basic sequence of tasks to get started. It contains the following sections: • 1.1 What Is Cisco Media Gateway Manager? • 1.2 What Are the NE Modules Supported by Cisco MGM? • 1.3 What Are the Key Features of Cisco MGM? • 1.4 A Typical Workflow in Cisco MGM 1.
Chapter 1 Introduction What Are the NE Modules Supported by Cisco MGM? 1.2 What Are the NE Modules Supported by Cisco MGM? Table 1-1 lists the modules in the MGX8880 chassis and the MGX8850 chassis that can be managed by the element management functions provided by Cisco MGM Release 5.0.
Chapter 1 Introduction What Are the NE Modules Supported by Cisco MGM? Table 1-1 MGX8880 and MGX8850 Modules and Cards (continued) Module Front Card Back Card VISM-PR MGX-VISM-PR-8T1 AX-RJ48-8T1 AX-R-RJ48-8T1 MGX-VISM-PR-8E1 AX-RJ48-8E1 AX-R-RJ48-8E1 AX-SMB-8E1 AX-R-SMB-8E1 SRME/B MGX-SRME/B MGX-SMFIR-1-155 MGX-STM1-EL-1 MGX-BNC-3T3-M SRME MGX-SRME MGX-SMFIR-1-155 MGX-STM1-EL-1 Cisco MGM provides a comprehensive management solution as illustrated in Figure 1-1.
Chapter 1 Introduction What Are the Key Features of Cisco MGM? Figure 1-1 Cisco MGM Comprehensive Management Solution Cisco Media Gateway Manager Fault Management System EMS CIC HA Traditional Multiservice Switch Controller Class 5 GK Softswitch Mobility Network Cisco MGX V Media Gateway CSR Cisco MGX Media Gateway PSTN V IP/MPLS Network Radio V IP IP 113776 Mobility Applications Hosted and Managed IP Telephony Broadband Local Infrastructure Solutions (Cable, Ethernet, T1, E1) 1.
Chapter 1 Introduction A Typical Workflow in Cisco MGM • Diagnostic capabilities using the Diagnostic Center • Real-time network surveillance with configurable popup alarm and event notifications • Real-time shelf views with full alarm and operational status indicators • Automated configuration backup with manual restore capabilities, plus remote software download capability across the entire network domain • GUI-based NE configuration • Extensive performance monitoring (PM) statistics collecte
Chapter 1 Introduction A Typical Workflow in Cisco MGM Table 1-2 describes the tools you will use to get started: Table 1-2 Item Getting Started Tools Tool Description Create a New User Displays the Create New Cisco Media Gateway Manager User wizard, which allows you to add a new user. Add a New Group Displays the New Group dialog box. From here, you can add a new user group, give the group a name, and provide a brief description of the group.
Chapter 1 Introduction A Typical Workflow in Cisco MGM To stop the Cisco MGM server: Step 1 Log into the Cisco MGM server workstation as the root user. Step 2 On the command line, enter the following: mgms-stop 1.4.2 Adding a User When Cisco MGM is installed, the System Administrator must create users, who can then perform tasks such as adding network elements. To add a new Cisco MGM user, go to the Domain Explorer window and choose Administration > Cisco MGM Users.
Chapter 1 Introduction A Typical Workflow in Cisco MGM 1.4.4 Adding a Network Element To add a network element (NE): Step 1 In the Domain Explorer window, click the Add Network Element(s) tool, or choose File > Add Network Element(s). Step 2 Enter the requested information. Change the operational state for the NE to In Service. Make sure you entered the IP address correctly. Step 3 Click Finish. Step 4 (Optional) Add more network elements.
C H A P T E R 2 Basic Concepts This chapter covers the details the basic concepts of Cisco MGM, including the following topics: • 2.1 How Do I Navigate within Cisco MGM? • 2.2 What Basic Functions Can I Perform in Cisco MGM? • 2.3 What Are the General Features of Cisco MGM? 2.1 How Do I Navigate within Cisco MGM? This section helps you understand Cisco MGM navigation tools and actions, including: Note • 2.1.1 Using the Domain Explorer • 2.1.2 Navigating Physical Views • 2.1.
Chapter 2 Basic Concepts How Do I Navigate within Cisco MGM? 2.1.1 Using the Domain Explorer The Domain Explorer is the Cisco MGM home window and provides a logical view of the network plus alarm, connectivity, and operational status. The Domain Explorer displays a hierarchical view of all NEs and groups currently being monitored by Cisco MGM. Domain Explorer windows are divided into two sections: a tree (at left) and a pane (at right).
Chapter 2 Basic Concepts How Do I Navigate within Cisco MGM? 2.1.1.1.1 Status Tab Table 2-1 describes the Status tab fields. Table 2-1 Field Descriptions for the Status Tab Field Description Domain Name User-defined name of the management domain. Description User-defined description of the management domain. Total NEs Total number of NEs within the management domain. Unavailable NEs Number of NEs within the management domain that Cisco MGM cannot currently connect to.
Chapter 2 Basic Concepts How Do I Navigate within Cisco MGM? 2.1.1.2 Group Properties The Group Properties pane displays information about the group that is currently selected in the topology tree. A group consists of other groups or NEs. Groups give you the flexibility of subdividing the management domain you are monitoring. For example, a group can represent all NEs within a geographical location.
Chapter 2 Basic Concepts How Do I Navigate within Cisco MGM? 2.1.1.3 Network Element Properties The Network Element Properties pane displays information about the NE that is currently selected in the tree. An NE represents a Cisco MGX 8880 or a Cisco MGX 8850. The same NE can have multiple instances in the tree. The contents of all instances of the same NE are always the same. Any changes to one NE instance are reflected in all instances of that NE.
Chapter 2 Basic Concepts How Do I Navigate within Cisco MGM? 2.1.1.3.3 NE Authentication Tab The NE Authentication tab allows you to specify usernames and passwords for Cisco MGM server. Table 2-7 describes the fields in the NE Authentication tab. Fields shown depend on the type of NE selected. Table 2-7 Field Descriptions for the NE Authentication Tab Field Subfield Description MGM Server NE Connection NE Service Username that the Cisco MGM server uses to connect to NEs.
Chapter 2 Basic Concepts How Do I Navigate within Cisco MGM? After zooming in on a region on the map, scroll bars at the bottom and right side of the screen allow you to pan the view to a different region. You can also use the focus box in the top left panel to pan and zoom the view. All groups are shown on a single map, and it is the zoom level and pan position that determine what groups are visible at any time. Depending on the selected layer rate, certain NEs are shown.
Chapter 2 Basic Concepts How Do I Navigate within Cisco MGM? • Database Properties—for Configuration, Pruning and Database Backup • Alarm Properties—for Threshold EMS Alarms and Non Threshold EMS Alarms • Error Log Properties—for the Cisco MGM Server and Gateway/SNMP, SM Service and SNMP Trap Service • NE Service—for NE Poller, NE AutoBackup and NE Manual Backup • PM Service—for PM Status and Properties • Gateway CORBA Service—for Global and OSS Clients The right side of the window displays t
Chapter 2 Basic Concepts How Do I Navigate within Cisco MGM? • Topology management • Automatic NE memory backup, on-demand restoration • General operation on multiple NEs 2.1.6 Paging through Data Some Cisco MGM tables return large numbers of rows. To support large tables, Cisco MGM provides a paging feature. If more than 1,000 rows of data are returned, data is grouped in pages of up to 1,000 rows. You can page forward and page back to view the entire set of data. 2.1.
Chapter 2 Basic Concepts How Do I Navigate within Cisco MGM? 2.1.8.1 Using Popup Menus The popup menus are available from any application. The popup menu options are enabled based on your security profile. To display the popup menus, you can right-click from the following options: • Away from the network in Graphical View. • A network from the Hierarchical Tree or Graphical View. • A node from the Hierarchical Tree or Graphical View.
Chapter 2 Basic Concepts What Basic Functions Can I Perform in Cisco MGM? To view the online help for any Cisco MGM dialog box, click the Help tool within the dialog box. Tip Use the print option in the browser that displays the online help to print the selected page. 2.1.11 Using the Pin Tool The Dashboard, Configuration Center, Diagnostic Center, Chassis View, and Statistics Report applications have a pin tool. The pin point is up when the tool in pinned up, and down when the tool is pinned down.
Chapter 2 Basic Concepts What Basic Functions Can I Perform in Cisco MGM? 2.2.2 Filtering Data Filter dialog boxes filter user-specified data. Many Cisco MGM tables have Filter dialog boxes that enable you to filter data in different ways and display the results in a table. 2.2.3 Exporting Data Most Cisco MGM tables support an export function to export the table contents to a flat file.
Chapter 2 Basic Concepts What Basic Functions Can I Perform in Cisco MGM? Table 2-9 Field Descriptions for the Event Export Manager Field Description Network Elements Allows you to export alarms (NE alarms and Cisco MGM-specific EMS alarms) and events for selected NEs. Choose from the list of available NEs and add them to the Selected list. If you have the appropriate user permission and you want to export EMS alarms and events, check the Export MGM EMS Alarms/Events check box.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? The following options are provided to control the pruning for each category of data: • Enable/disable • Retention period • Time of day to perform the pruning 2.3 What Are the General Features of Cisco MGM? This section describes some of the general Cisco MGM features, including: • 2.3.1 What is FCPS? • 2.3.2 Understanding Fault Management • 2.3.3 Understanding Configuration Management • 2.3.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? Table 2-10 FCPS Framework Functionality (continued) Function Description For More Information, See Performance management Gathers and reports the behavior of NEs, network, and services, including quality assurance, monitoring, management control, and analysis. Chapter 10, “Managing Performance” Performance management can be performed in the Configuration Center or in the Statistics Report.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? Figure 2-2 Dashboard 1 8 7 2 3 6 5 4 113455 172.16.0.0 Cisco Media Gateway Manager on 172.16.0.0 16 15 14 13 12 11 10 9 1 Layers the Domain Explorer window as the top active 9 window. The Domain Explorer is the Cisco MGM home window1. 2 Opens the Alarm Browser window; this highlights NE-specific critical, major, minor, and warning alarms. Displays online help for the Dashboard.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? 6 Minimizes all Cisco MGM windows, except for the Dashboard window itself. 14 Lists the number of minor alarms in the domain. The alarm count includes minor alarms on NEs and on the EMS. Click the counter to open the Alarm Browser window, filtered to show all minor alarms. 7 Restores all minimized Cisco MGM windows. 15 Lists the number of major alarms in the domain. The alarm count includes major alarms on NEs and on the EMS.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? • Inspector View—Provides a list of detailed information for the selected network element from the hierarchy view. Click the Show static data button to update the information in the Inspector View. 2.3.3.1.1 Network Elements Overview By performing network element configuration tasks, you can: • Communicate with individual network elements, for example, a switch or a concentrator, using Simple Network Management Protocol (SNMP).
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? 2.3.3.3.1 Adding New NEs to the Cisco MGM Domain The Add New NE wizard allows you to add a new NE, or to add several new NEs at once. The wizard allows you to enter multiple NE IP addresses one at a time, or enter a beginning and ending IP address and automatically add a range of NEs. 2.3.3.3.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? The following NE administration features are available for the Cisco MGX 8880 and Cisco MGX 8850: • Software download • Memory backup and restore • Job monitoring • NE Software table (used to commit or revert software images) 2.3.3.4.1 Software Download Dialog Box Use the Software Download dialog box to download software to NEs. After the download is complete you can use the NE Software table to activate the software.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? To launch Statistics Report, choose Performance > MGX 8880/8850MG > Statistics Report. Depending upon the report selected, you can identify certain criteria, such as network object, type of statistics, granularity, report interval, and graphical format. Note VISM cards are supported for the Statistics Report. Table 2-12 lists the report types that are supported for each network element from the Hierarchical Tree.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? • OSS security domain: OSS-to-Cisco MGM sessions are configured by the Cisco MGM GateWay EMS-to-NMS interface architectural component. • NE security domain: At the NE level, a username and password are configured to enable the user to connect directly through the console port (EIA/TIA-232), through the management port (10BASE-T), or remotely through an SSH or Telnet session. NE passwords are stored using base-64 two-way encryption.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? You can: • Define the network partitions from the associated list of nodes. • Define, modify, and view the areas within your network. • Manage only the areas under your security profile. • Manage connections that originate and terminate within the assigned area(s). The domain can include multiple areas. 2.3.5.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? By configuring user access, you can: • Provide user-access profiles that can be customized for each user. The user-access profile is a list of operations or actions a user can perform coupled with assigned access privileges for each action. • Assign access privileges to read, create (write), modify, and delete profiles. By default, only the root user can start and stop the Cisco MGM core processes.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? 2.3.6 Using the Diagnostic Center Note For detailed information about using the Diagnostic Center, see Chapter 9, “Managing Faults.” You can launch the Diagnostic Center from various Cisco MGM applications, such as the Statistics Report, Configuration Center, or Chassis View. The Diagnostic Center tool appears in the toolbar. To launch the Diagnostic Center, you can: • Choose Fault > MGX 8880/8850MG > Diagnostic Center.
Chapter 2 Basic Concepts What Are the General Features of Cisco MGM? 2.3.7 Managing Cisco MGM CORBA Interfaces Chapter 12, “Managing CORBA Interfaces.” describes the management of Cisco MGM GateWay/CORBA, which allows another program or application to communicate with the Cisco MGM server, and also about CORBA management, which allows communication between the Cisco MGM client and server. Cisco Media Gateway Manager 5.
C H A P T E R 3 Planning the Network This chapter describes the basics of planning a network and identifies some of the resources available to the network planner using Cisco MGM: • 3.1 Network Planning • 3.2 What Network Elements Are Available to a Network Planner? 3.1 Network Planning Network planning is the process of deciding the topology and capacity of a network.
Chapter 3 Planning the Network What Network Elements Are Available to a Network Planner? • 3.2.2 Cisco MGX 8850 Multiservice Switch • 3.2.3 Cisco PXM-45 Processor Switch Module • 3.2.4 Cisco Voice Switch Service Module • 3.2.5 Cisco Voice Interworking Service Module • 3.2.6 Cisco Route Processor Module • 3.2.7 Cisco AXSM Broadband ATM Switch Module • 3.2.8 Cisco MGX Service Resource Module 3.2.
Chapter 3 Planning the Network What Network Elements Are Available to a Network Planner? The Cisco PXM-45 provides the following features: • 45-Gbps nonblocking switching • Hot card insertion/removal • 1:1 hot-standby redundancy • User-selectable primary and secondary clock sources with graceful switchover • Internal Stratum-3, external building integrated timing supply (BITS), or inband clock sources • Inband or out-of-band management via EIA/TIA-232 or 10BaseT control ports • Support for na
Chapter 3 Planning the Network What Network Elements Are Available to a Network Planner? 3.2.5 Cisco Voice Interworking Service Module The Cisco Voice Interworking Service Module (VISM-PR) is a packet voice module for the Cisco MGX 8880 Media Gateway and the Cisco MGX 8000 Series multiservice switches. The Cisco VISM-PR offers robust packet voice functions for service providers and enterprise customers, and supports full 8 T-1s/E-1s capacity for G.711, G.726 and G.729ab codecs.
Chapter 3 Planning the Network What Network Elements Are Available to a Network Planner? The Cisco RPM-PR is a double-height line card, which connects to the MGX midplane through an internal OC-6 ATM cell bus. The Cisco RPM-PR supports up to two single-height back cards: four-port Ethernet and one-port Fast Ethernet.
Chapter 3 Planning the Network What Network Elements Are Available to a Network Planner? • Support for all ATM service classes, with up to 16 classes of service (CoS). Supports carrier-class implementation of standards-based PNNI, SVC/SVP, SPVC/SPVP, and MPLS services.
C H A P T E R 4 Building the Network Once you have planned your network (see Chapter 3, “Planning the Network”), you can begin building network elements and their related aspects, such as groups, network partitions, and Network Maps. This chapter contains the following sections: • 4.1 What Network Elements Are Available? • 4.2 How Do I Add and Delete Network Elements? • 4.3 How Do I Build Groups? • 4.4 How Do I Configure the SNMP Community String? • 4.5 How Do I Build Network Maps? • 4.
Chapter 4 Building the Network How Do I Add and Delete Network Elements? • 4.2.4 Network Element Discovery • 4.2.5 Copying a Network Element from One Group to Another • 4.2.6 Moving a Network Element from One Group to Another • 4.2.7 Deleting Network Elements • 4.2.8 Restoring a Deleted Network Element 4.2.1 Prerequisites for Adding Network Elements You must enable the NE service before you can add an NE.
Chapter 4 Building the Network How Do I Add and Delete Network Elements? Step 3 Select an NE type. Step 4 In the property sheet of the Control Panel, click Activate in the Service Status field. Step 5 In Error Level, choose the error level for alarms on the selected NE to include in the Error Log (Critical, Major, Minor, Informational, Debug, or Trace). Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Chapter 4 Building the Network How Do I Add and Delete Network Elements? Step 4 Enter the following information: a. NE ID Note Do not use “MGM” as an NE ID because the Alarm Browser might contain Cisco MGM alarms with the source ID “MGM.” It will be difficult to distinguish between NE alarms and Cisco MGM alarms if they both have the same source ID (“MGM”). For the same reason, do not cause Cisco MGM to automatically populate an NE whose NE ID is “MGM.
Chapter 4 Building the Network How Do I Add and Delete Network Elements? 4.2.3.2 Adding Multiple Network Elements From the Domain Explorer, you can add multiple NEs Step 1 Select a node in the Domain Explorer; then, choose File > Add Network Element(s). You can also click the Add Network Element(s) tool. The Add Network Element(s) wizard appears. See Figure 4-1. Note Step 2 Step 3 Enter the following information (see Table 4-1 for more details): a. NE Model b. NE Type c.
Chapter 4 Building the Network How Do I Add and Delete Network Elements? Table 4-1 Field Descriptions for the Add Network Element(s) Wizard Screen Field Description NE Addition NE Model Allows you to select the NE model (Cisco MGX 8880/Cisco MGX 8850). NE Type The NE Type is not available. NE Addition Select Single NE Addition to add only one NE. Select Bulk NE Addition to add several NEs simultaneously. The available fields will change, depending on which item you select.
Chapter 4 Building the Network How Do I Add and Delete Network Elements? Table 4-1 Screen Field Descriptions for the Add Network Element(s) Wizard (continued) Field Description NE NE ID Properties Allows you to enter a unique name for the NE in the form of an ASCII text string. Apostrophes (') and quotation marks (“) are not accepted. The NE ID you enter should be the same as the NE ID that is configured on the NE itself. If it is not the same, this field will be updated with the NE hostname.
Chapter 4 Building the Network How Do I Add and Delete Network Elements? 4.2.5 Copying a Network Element from One Group to Another Groups for multiple NEs can easily be created in Cisco MGM. For information about creating groups, see Section 4.3 How Do I Build Groups? The same NE can be copied into different groups. Step 1 In the Domain Explorer Hierarchy pane, select the NE to be copied. Step 2 Choose Edit > Copy (or click the Copy tool). This copies the NE to the clipboard.
Chapter 4 Building the Network How Do I Add and Delete Network Elements? 4.2.7 Deleting Network Elements From the Domain Explorer Hierarchy pane, you can delete a single NE, multiple NEs, or out-of-service NEs: • 4.2.7.1 Deleting a Single Network Element • 4.2.7.2 Deleting Multiple Network Elements • 4.2.7.3 Removing a Deleted Network Element 4.2.7.1 Deleting a Single Network Element To delete a single NE: Step 1 In the Domain Explorer Hierarchy pane, select the NE that will be deleted.
Chapter 4 Building the Network How Do I Add and Delete Network Elements? – In the Status tab of the Network Element Properties sheet, set the Operational State field to Out of Service; then, click Save. – In the Domain Explorer, right click on the node and choose Mark Out of Service. Step 2 In the Domain Explorer Hierarchy pane, select again all the NEs that will be deleted. To select multiple NEs, press and hold down the Ctrl button; then, click each NE that will be deleted.
Chapter 4 Building the Network How Do I Build Groups? 4.2.8 Restoring a Deleted Network Element You can restore an NE to its previous location in the Domain Explorer Hierarchy pane from the Deleted Network Elements group. Step 1 In the Domain Explorer Hierarchy pane, click the Deleted Network Elements group. Step 2 Click the NE that will be restored. Step 3 Choose Edit > Undelete. All instances of the NE are restored to their previous locations in the Domain Explorer Hierarchy pane.
Chapter 4 Building the Network How Do I Build Groups? Step 3 Enter the following information in the New Group dialog box. Table 4-2 Step 4 Field Descriptions for the New Group Dialog Box Field Description Group ID Enter a unique name for the group. Location Name Enter a geographic location for the group. Description Enter a description of the group. Click OK. 4.3.2 Copying Groups Domains for multiple users can easily be created in Cisco MGM.
Chapter 4 Building the Network How Do I Build Groups? Note Tip Groups cannot be moved into the Discovered NEs or Deleted NEs groups. The Cut and Paste tools can also be used to move groups. Since they cannot see the entire domain, users with the Assign NEs property (Provisioner, Operator, and some custom user profiles) are not allowed to modify topology using copy, cut, paste, or drag and drop. 4.3.4 Deleting Groups Cisco MGM allows you to delete a single group or multiple groups: • 4.3.4.
Chapter 4 Building the Network How Do I Configure the SNMP Community String? 4.3.4.2 Deleting Multiple Groups Step 1 In the Domain Explorer Hierarchy pane, select the group to be deleted. Select multiple groups by pressing and holding down the Ctrl key, then click each group that will be deleted.
Chapter 4 Building the Network How Do I Configure the SNMP Community String? Table 4-3 SNMP Configuration Options Option Description Domain Explorer, Network Element Property pane, NE Authentication tab After saving the community strings information, the Cisco MGM processes use the new community strings for SNMP accesses.
Chapter 4 Building the Network How Do I Configure the SNMP Community String? 4.4.2 Changing Community Strings Using the Domain Explorer To change the SNMP get and set community strings for selected nodes: Step 1 In the Domain Explorer Hierarchy pane, select the node. Step 2 In the NE Authentication tab, you can change the SNMP Community String to change the SNMP get community string, or change the SNMP Set Only Community String. Step 3 Click Save. 4.4.
Chapter 4 Building the Network How Do I Configure the SNMP Community String? Step 2 Enter the cnfsnmp command to change the SNMP set community string for all nodes as follows: xxyyzz% cnfsnmp community private rw xxyyzz% Then check that the community string has changed. Enter: dspsnmp You will see output similar to the following example: xxyyzz.7.PXM.a > dspsnmp xxyyzz System Rev: 05.00 Dec.
Chapter 4 Building the Network How Do I Build Network Maps? Step 3 When you are prompted for a password, you must: a. Enter the existing password. b. Enter the new password. c. Reenter the new password for confirmation. 4.5 How Do I Build Network Maps? Network map backgrounds are provided by default as part of Cisco MGM, and are used to display a geographical layout of the network.
Chapter 4 Building the Network How Do I Build Network Maps? Table 4-4 Step 3 Step 4 Step 5 Edit Menu Options (continued) Edit Menu Option Description Change Map Background Choose a different geographic background image for the selected view. Choose one of the image files packaged with Cisco MGM, or use another image file (not packaged with Cisco MGM). Change Node Icon Choose a new icon for the selected node. Zoom In Choose to change the magnification of the icons.
Chapter 4 Building the Network How Do I Build Network Maps? Figure 4-2 Network Map Window 4.5.2 Viewing a Node in the Network Map Icons in the Network Map are displayed based on the nodes you select in the Domain Explorer. Launching the Network Map from the following nodes displays different results: • From the Cisco MGM domain in the Domain Explorer—Displays all the groups in the Cisco MGM Domain.
Chapter 4 Building the Network How Do I Build Network Maps? 4.5.2.1 Adjusting the Zoom Level or Pan Position Step 1 In the Domain Explorer Hierarchy pane, click a node and choose File > Network Map. The Network Map appears and the node is preselected. See Figure 4-2. Step 2 In the Network Map, choose Edit > Zoom In, Edit > Zoom Out, or Edit > Zoom Area to adjust the zoom level. You can also click the Zoom In, Zoom Out, or Zoom Area tool.
Chapter 4 Building the Network How Do I Build Network Maps? 4.5.3.2 Modifying a Map Background Step 1 In the Domain Explorer Hierarchy pane, click a node and choose File > Network Map. See Figure 4-2. Step 2 In the Network Map window, click in the map background and choose Edit > Change Map Background or right-click in the map background and choose Change Map Background. The Select Background Map dialog box appears.
Chapter 4 Building the Network How Do I Discover the Network? • Note Revert To Default—Choose File > Revert to Default to cancel your settings and revert to previous settings. Any custom map you created for the nodes under subgroups currently displayed in the Network Map will be erased. The Network Map reverts to the default map assigned to these nodes. Revert to Default is only available for nodes under sub-groups. 4.
Chapter 4 Building the Network How Do I Synchronize the Network? 4.6.1 Discovering NEs The network discovery service in Cisco MGM collects information from individual NEs, discovers new NEs added to the network, and computes network-level information, such as physical topology, and discrepancies. When you add a new NE to Cisco MGM, the discovery process starts.
Chapter 4 Building the Network How Do I Synchronize the Network? Step 6 The Distribution Method is manual. This specifies that the network clock source is statically configured in the device. Step 7 Enter the maximum network diameter, measured in hops, in the Max Diameter field. The range is from 3-20. The default value is 20. Note Step 8 Change Time—The time when the global clocking was configured.
Chapter 4 Building the Network How Do I Synchronize the Network? Step 3 Click the Clocking tab to display Clocking Configuration window. See Figure 4-3. Step 4 Choose Available Clock Sources to display the list of available clock sources from the Category drop-down arrow. 4.7.1.3 Displaying the List of Manual Clock Sources To display a list of manual clock sources: Step 1 In the Domain Explorer, right-click the PNNI node from the Hierarchy pane and choose Configuration Center.
Chapter 4 Building the Network How Do I Test Connectivity? 4.8 How Do I Test Connectivity? Note A diagnostic check can be run at the node level to verify that selected nodes are being managed correctly by Cisco MGM. See “5.2.10.2 Running a Diagnostic Check at the Node Level”. Testing NE connectivity occurs at the management protocol level (SNMP, or CORBA). Step 1 In the Domain Explorer Hierarchy pane, select the NE and choose Fault > Diagnostic Center.
Chapter 4 Building the Network How Do I Test Connectivity? Cisco Media Gateway Manager 5.
C H A P T E R 5 Maintaining an Efficient Network This chapter contains the following information to help you maintain an efficient network: Note • 5.1 How Do I Manage the Database? • 5.2 How Do I Monitor the Network? • 5.3 How Do I Modify the Network? • 5.4 How Do I Manage the Network Software? • 5.5 How Do I Manage Redundancy and Failover? • 5.6 Which Ports Are Reserved in Cisco MGM? • 5.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? A useful tool for managing the database is the Oracle Enterprise Manager, part of the Oracle9i Client CD. The Oracle Enterprise Manager provides an integrated solution for managing heterogeneous environment and combines a graphical console, agents, common services, and tools to provide a comprehensive systems-management platform for managing Oracle products. This section contains the following information: • 5.1.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Step 3 (Optional) Click the Configuration tab. Table 5-1 describes the fields within the Database Properties Configuration tab. Step 4 (Optional) Click the Pruning tab. Table 5-2 describes the fields within the Database Properties Pruning tab. Note Step 5 Step 6 For more details, see section 5.1.4 Pruning the Database, page 5-13. (Optional) Click the Database Backup tab.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Figure 5-1 Table 5-1 Control Panel—Database Properties Pane Field Descriptions for the Database Properties—Configuration Tab Field Description Database Server Configuration Displays the size of the database server. Server Installed in ARCHIVELOG If set to True, Cisco MGM supports automatic pruning of the /db05 partition when the database is in ARCHIVELOG mode. Cisco Media Gateway Manager 5.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Table 5-1 Field Descriptions for the Database Properties—Configuration Tab (continued) Field Description Configuration Mode Configuration Mode tells the Cisco MGM server the values to use to log into the Oracle database. When set to Auto, the Cisco MGM server uses the configuration that was set when Cisco MGM was installed.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Table 5-2 Field Description for the Database Properties—Pruning Tab Field Description PM Data Specifies the number of days to save performance monitoring (PM) data before Cisco MGM runs the database pruning script. The default value is 7. You can also specify the time of day when the PM data will be saved by choosing the hour and minute from the HH, MM, and AM/PM fields. Minutes are listed in 5-minute intervals.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? 5.1.2 Importing and Exporting Data to and from the Oracle Database Use the Oracle Export utility to write data from an Oracle database to an operating system file in binary format. The file is stored outside the database and read to another Oracle database by using the Import utility. For more information about using Oracle Import and Export utilities, refer to the Oracle9i Utilities document.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Caution Whenever a back up is done, it must include both the database and all other Cisco MGM directories. Likewise, whenever a restore is done, it must include both the database and all other Cisco MGM directories. 5.1.3.1 Overview of the Oracle Logical Backup It is recommended to backup the Oracle database using a logical backup. A logical backup involves reading a set of database records and writing them to a file.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? 5.1.3.3 Performing a Logical Backup (Export) Complete the following steps to perform a full export of the entire database: Note Step 1 The export command is located in the /oraclesw9i/product/9.2/bin directory. Enter the following commands: # su - oracle % echo $ORACLE_SID Note Step 2 Make sure that the value of the ORACLE_SID environment variable matches the system identifier (SID) of the database instance to export.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Step 2 Enter the following commands to create the mgmanager user: %sqlplus /nolog << EOF SVRMGR> connect sys/change_on_install as sysdba SVRMGR> @/cdrom/cdrom0/mgms/create_user.sql SVRMGR> exit >EOF Step 3 Enter the following command to import the mgmanager schema: % imp system/manager file=export_filename fromuser=ctmanager touser=ctmanager commit=y ignore=y buffer=1000000 log=mgm-imp.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? 5.1.3.7 Restoring the Database To restore the database: Caution Do not restore the database unless it is corrupted and inaccessible. If your database is inaccessible, your Cisco MGM server will not be running. The restore will overwrite the existing data files and restore the database from the backup files.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Table 5-4 NE Service—NE Manual Backup Tab Field Subfield Description Select Modify Mode — Allows you to specify whether the manual backup should apply to a specific NE model or to all applicable NE models. Configuration Parameters Number of Backup Copies Allows you to specify the number of backup copies to keep (the default is 7). Each time Cisco MGM creates a new backup file it checks the existing number of backup copies.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? 5.1.4 Pruning the Database Cisco MGM provides features to prune the database. Pruning is the removal of information that is deemed old or less significant, and can include the following data: • Fault Management data • Performance data • Audit Trail data • Audit Log data • System Log Error Log • Self Monitor data • Job Monitor data You can change the pruning settings using the Control Panel.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? 5.1.4.2 Using Pruning Scripts Running database pruning scripts allows you to prune Cisco MGM data from the Oracle database at any given time.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Table 5-6 Database Pruning (continued) What to Prune (Script Name) Tables Affected Input Parameters Remarks Prune alarm and event data (prune_fm.sh) alarm_event_table Number of days 1–31 Removes all alarm and event entries that were created before n days. Prune admin job table (prune_admin_job_table.sh) admin_job_table Number of days 1–31 Removes all admin job entries that were created before n days.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Table 5-6 Database Pruning (continued) What to Prune (Script Name) Remove an NE (prune_ne.sh) (continued) Tables Affected Input Parameters Remarks ???_table NE SYS ID Removes all information about the NE from the database. Use this script with extreme caution. Number of days 1–31 Removes all server monitoring data.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Step 3 On the command line, enter the following command: sqlplus ctmanager/mgm123! The message “Connected to: Oracle9i...” and the SQL> prompt should appear. If not, enter the username and password again. Step 4 Enter any SQL command supported by Oracle upon connection to SQL*PLUS. For a list of SQL commands supported by Oracle, refer to the SQL*PLUS User Guide. 5.1.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Database? Step 5 Enter the following command to start the Cisco MGM server: mgms-start 5.1.7 Enhancing Database Performance To improve database performance when Cisco MGM clients access Cisco MGM data, tune the Oracle database as outlined in “Part IV: Optimizing Oracle Instance Performance” in the Oracle9i Tuning Guide. 5.1.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Step 10 Change the directory to the location of the Cisco MGM Index tablespace. This was the third directory specified during the Cisco MGM server installation. The default location is /db04. Step 11 Enter the following command: /bin/rm -rf mgmindex/ORACLE_SID* 5.2 How Do I Monitor the Network? Note For specific fault monitoring informationoracle9oracle9, see Chapter 9, “Managing Faults.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Step 2 When the login prompt appears in the Telnet window, you must: a. Enter the Service Level name. b. Enter the Service Level password. You have successfully established a telnet session to a node. 5.2.2 Connecting to Nodes Through Secured Shell When you connect as an Operator to an MGX node through Cisco MGM, or when Cisco MGM connects to MGX, secured shell (SSH) enhances the security.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Step 2 Press Enter. The chosen NE is displayed along with the current status for each card. Step 3 Click the Front View tab or Rear View tab of the NE. The default is the front view. Step 4 Check the status of the NE from Inspector View. 5.2.4 Monitoring a Card with Chassis View You can select a card to monitor when the objects are associated with a particular card.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Figure 5-2 Chassis View - Front View 5.2.5 Monitoring a Line or Port with Chassis View You can select a port if managed objects are associated with a particular port, line, or interface. To monitor a line or port: Step 1 Step 2 In Chassis View, there are two ways to choose the line or port: • Choose the line or port from the Hierarchy pane, or • Click the line or port that you want to display from the node view.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? 5.2.6 Monitoring Scheduled Tasks The Job Monitor table provides information about scheduled administrative tasks—memory backup, memory restore, and software download. For example, you can see the system username of the person who entered a specific task, the time that the task began, and the time that the task ended. Note A job consists of multiple tasks.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Table 5-8 Job Monitor Table Descriptions Column Name Description Job ID ID number corresponding to the selected job. Task ID ID number corresponding to the task. If a job includes more than one NE, each NE has a separate task ID for the job.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Table 5-9 Job Monitor Filter Dialog Box Descriptions Tab Description Creation Time (time zone) Allows you to filter job monitor data for a specified time period, ranging from the past hour to the past 180 days. Additionally, you can click the User Specified radio button to specify an exact filter starting and ending time by month, day, year, and hour.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? 5.2.6.3 Canceling a Scheduled Job or Task To cancel a scheduled job or task from the Job Monitor table list: Step 1 In the Domain Explorer window, choose Administration > Job Monitor. Step 2 Select a task to cancel; then, click the Cancel Task or Cancel Job tool (or choose Edit > Cancel Task, or Edit > Cancel Job). Note Step 3 Cancel is enabled only for jobs and tasks with a Queued status.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Table 5-11 Note Column Name Descriptions for the Service Monitor Table Column Name Description Service Name Displays the name of the selected service. Logged In At Displays the last time the user logged in. IP Address Displays the IP address of the selected service. Session ID Displays the unique session ID. The showmgm command is an alternate way of viewing processes or services that are running in the Cisco MGM server.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Table 5-12 Cisco MGM Properties Descriptions Tab Field Description Server Configuration Server Name Displays the workstation name where the Cisco MGM server application resides. IP Address Displays the IP address of the Cisco MGM server. Server Port Displays TCP port number of the Cisco MGM server. Software Version Shows the Cisco MGM software version that is running.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? 5.2.10.1 Running a Diagnostic Check at the Network Level In the Diagnostic Center, you can verify that all the nodes in the network are being managed correctly by Cisco MGM. To run a diagnostic check at the network level: Step 1 In the Diagnostic Center, double-click or drag and drop the network from the Hierarchy pane to the right hand pane, to display the diagnostics at the network level. Step 2 Click the Manageability tab.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Figure 5-3 Diagnostic Center—Manageability Tab 5.2.10.2 Running a Diagnostic Check at the Node Level In the Diagnostic Center, you can verify that selected nodes are being managed correctly by Cisco MGM. To run a diagnostic check at the node level: Step 1 In the Diagnostic Center, double-click or drag and drop the node from the Hierarchy pane to the right hand pane, to display the diagnostics at the node level.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? For parameter definitions, see Table 5-13. Step 6 In the Node Login Information area: a. Enter the user name in the User Id field. b. Enter password in the Password field. Step 7 Click Check Manageability to run a diagnostic check for the node. Step 8 Verify the check results from the Manageability Check Results area. For parameter definitions, see Table 5-14. 5.2.10.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Table 5-13 Health Related Parameters (continued) Name Description Transfer Timeout Specifies the transfer timeout is the estimated period when the transfer is completed. The transfer is done by FTP from the previous transfer of the throughput data for a node. If the file transfer fails to complete within the period, transfer is aborted and an error is reported.
Chapter 5 Maintaining an Efficient Network How Do I Monitor the Network? Step 7 Click Send to send the trouble ticket to recipient. Step 8 Click Save to save the trouble ticket in the directory. 5.2.11 Managing the VSI Controllers These tasks are used to work with VSI controllers: • 5.2.11.1 Creating a VSI Controller • 5.2.11.2 Displaying a VSI Controller • 5.2.11.3 Deleting a VSI Controller 5.2.11.1 Creating a VSI Controller A VSI controller must be added when a new node is added.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? 5.2.11.2 Displaying a VSI Controller To display a VSI controller, complete the following procedure: Step 1 In the Domain Explorer, right-click the node from the Hierarchy pane and choose Configuration > MGX8880/8850 MG > Configuration Center. Step 2 Click the Elements tab to display the Configuration Window for Elements. Step 3 Click the Controllers tab to display the Controllers Table.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? 5.3.1 Changing the Operational State of an NE You need to change the operational state of a NE to carry out certain tasks. For example, the operational state field of an NE must be changed to Out of Service before the NE can be deleted. To change the operational state of an NE: Step 1 In the Domain Explorer tree, select the NE that will be changed. The Network Element Properties pane appears.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? 5.3.2 Backing Up and Restoring Memory Cisco MGM allows you to backup and restore memory for selected NEs. For example, if you wanted to save your settings for a particular NE, you can backup the memory for just that NE. Cisco MGM backs up configuration and provisioning information residing in the flash memory of an NE.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? • Available NEs • (Optional) Job Comments • Tag Name • Time (time zone) The time zone can be Greenwich mean time (GMT), a user-defined offset from GMT, or local time, depending on what is specified in the User Preferences dialog box. Note Click Finish to initiate the memory backup procedure. The configuration file is copied to the /opt/CiscoMGMServer/admin/nodename/MGX-timestamp-bkp.cfg file.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? Table 5-15 Memory Backup Dialog Box Descriptions (continued) Field Description Tag Name Add a tag to the system-generated filename. If you select System Default, no tag name is added. If you select User Specified, you can enter a tag name. The length of a filename including a user specified name should not exceed 40 characters. If a long filename is chosen, it will be truncated to 15 characters.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? Table 5-16 Memory Restore Dialog Box Descriptions Field Description NE Model Select the NE model that you want to restore. The model you select determines the NEs that are displayed in the Network Elements field. Network Elements Use the Add and Remove buttons to move the NE that you want to restore to the Selected NE list. You can run the Memory Restore procedure for only one NE at a time.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? Note • Recovery Properties—View a list of servers that clients will log into if access to the primary server is disrupted and view a list of critical services that the server monitors. • Database Properties—View database configuration, pruning time periods, and information that the server uses to log into the Oracle database. • Alarm Configuration Properties—View threshold and non-threshold parameters.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? Table 5-17 Recovery Properties—Session Recovery Tab Field Description Wait Time If disruption to the primary Cisco MGM server occurs, the Wait Time field provides the number of seconds the client waits before attempting to log into the backup server. No.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? c. Enter the following command to change the IP address in the etc/hostname.xxx file, where xxx is the IP interface that is defined in the Solaris server: # vi /etc/hostname.xxx d. Enter the following command to change the default router file, if required: # vi /etc/defaultrouter e.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? Table 5-18 Configuration Files that Require Updating (continued) Filename Location Oracle Configuration Files tnsnames.ora /oraclesw9i/product/9.2/network/admin listener.ora /oraclesw9i/product/9.2/network/admin Cisco MGM Server Configuration File MGMServer.cfg Note /opt/CiscoMGMServer/cfg The default directory /opt/CiscoMGMServer may have been changed during installation of the Cisco MGM server. 5.3.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? Table 5-19 Field Description for the NE Service Properties Field Description Service Status Displays the current status of the service: Active or Not Active. Service Control Allows you to stop or start a process. Notice that the Service Control button toggles between Activate and Deactivate, and that the Service Status field changes accordingly.
Chapter 5 Maintaining an Efficient Network How Do I Modify the Network? 5.3.10 Configuring Application-Specific Parameters Note Table 5-20 describes the fields in the User Interface Properties pane. The User Interface (UI) Properties pane allows you to configure application-specific parameters. Specifically, you can do the following: • Fault Management—Specify automatic or manual alarm acknowledgement, overwrite alarm notes, and un-acknowledge alarms (for more details, see Chapter 9, “Managing Faults”.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Network Software? • getinfo.sh • prune_auditlog.sh • prune_errlog.sh • prune_audittrail.sh • prune_fm.sh • prune_pm.sh • prune_ne.sh • prune_server_monitor.sh These scripts should normally be run as root. However, Cisco MGM facilitates running these scripts as non-root users using sudo.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Network Software? 5.4.1 Downloading Software Images Note Table 5-21 describes the fields in the Download Software Dialog. Note If a software download has a status of Queued, and if it has a task in the running list, the download cannot be canceled. Caution If you mark an NE as an Out of Service while a software download is in progress on that NE, the software download might not complete successfully.
Chapter 5 Maintaining an Efficient Network How Do I Manage the Network Software? Step 4 Click Finish to initiate the software download to the standby memory on the NE. Step 5 Cisco MGM stores two software versions: active and standby. When you download software, it is saved as the standby version. Figure 5-4 Table 5-21 Software Download Window Field Description for the Software Download Dialog Field Description NE Model Select the NE type to which you want to download software.
Chapter 5 Maintaining an Efficient Network How Do I Manage Redundancy and Failover? Table 5-21 Field Description for the Software Download Dialog (continued) Field Description Source Specify the location of the software: Time (time zone) • Local allows you to select an image on the current client system. • Server allows you to select an image on the Cisco MGM server to which your client is connected. • Remote option is grayed out. Set a time for the download.
Chapter 5 Maintaining an Efficient Network How Do I Manage Redundancy and Failover? Step 5 Enter the slot number of the Primary module in the redundant configuration in the Primary Slot Num field. Step 6 Enter the slot number of the Secondary module in the redundant configuration in the Secondary Slot Num field.
Chapter 5 Maintaining an Efficient Network Which Ports Are Reserved in Cisco MGM? Step 3 Choose Redundancy Info from the Category drop-down arrow to display the redundancy status for the node. Step 4 Select the card from the list of redundant cards. Step 5 Click Details to display the Redundancy Configuration window. See Figure 5-5. Step 6 Enter the slot number of the Secondary module in the redundant configuration in the Secondary Slot Num field.
Chapter 5 Maintaining an Efficient Network Which Ports Are Reserved in Cisco MGM? 5.6.2 Ports between the Cisco MGM Server and Clients Table 5-22 lists the ports that the Cisco MGM server uses to communicate with the Cisco MGM clients.
Chapter 5 Maintaining an Efficient Network How Do I Export Information in Tables? 5.6.3 Ports between the Cisco MGM Server and MGX Switches Table 5-22 lists the ports that the Cisco MGM server uses to communicate with the Cisco MGX switches. Table 5-23 Cisco MGM Server and MGX Switches Module or Protocol Port Daytime port 13 SSH port 22 Telnet port 23 UDP port to receive traps 2500 5.6.
Chapter 5 Maintaining an Efficient Network How Do I Export Information in Tables? • Service Monitor • Supported NE Table Most Cisco MGM tables support an export function to export the table contents to a flat file. It is possible to select the separator as comma, tab, or a user specified character. Other options include the ability to check for the separator in the exported data. All rows in the active page of the selection can be exported or only selected rows.
Chapter 5 Maintaining an Efficient Network How Do I Export Information in Tables? Step 4 In the HTML Report dialog box, select either of the following: • Selected row(s)—Export only the selected rows. • All rows in current page—Export all rows in the table. A maximum of 1000 rows per page can be exported. Note Step 5 To save more than 1000 rows of data, export them to a text file. For information about exporting to a text file, see section 5.7 How Do I Export Information in Tables?, page 5-53.
Chapter 5 Maintaining an Efficient Network How Do I Export Information in Tables? Cisco Media Gateway Manager 5.
C H A P T E R 6 Configuring Hardware This chapter helps you configure your hardware using the Cisco MGM Configuration Center and Chassis View, and contains the following sections: • 6.1 How Do I Manage My Network with the Chassis View?, page 6-1 • 6.2 How Do I Manage My Network with the Configuration Center?, page 6-5 • 6.3 How Do I Manage Templates for Network Elements?, page 6-11 • 6.4 How Do I Configure Cisco MGX 8880 and 8850 Nodes?, page 6-13 • 6.
Chapter 6 Configuring Hardware How Do I Manage My Network with the Chassis View? 6.1.1 Launching Chassis View To launch Chassis View from the Domain Explorer: • Click on a node, then choose Configuration > MGX 8880/8850 MG > Chassis View.
Chapter 6 Configuring Hardware How Do I Manage My Network with the Chassis View? 6.1.2 Navigating with Chassis View The Chassis View main window contains the following components: • Menu bar—See Table 6-1 • Toolbar—See Table 6-2 • Hierarchy, Configuration, and Inspector panes—See Table 6-3 Table 6-1 Chassis View—Menu Bar Options Menu Bar Options Task File Close Closes the current Chassis View main window when you are running multiple sessions of the Chassis View.
Chapter 6 Configuring Hardware How Do I Manage My Network with the Chassis View? Table 6-2 Chassis View—Toolbar Buttons Option Task Chassis View Launches Chassis View for the selected object. If no object is selected, Chassis View launches, and the right hand area is empty. Configuration Center Launches Configuration Center for the selected object. If no object is selected, Configuration Center launches, and the right hand area is empty.
Chapter 6 Configuring Hardware How Do I Manage My Network with the Configuration Center? 6.1.2.2 Chassis View LED Colors The following LED colors are used in the Chassis View: Table 6-4 LED Colors for Chassis View Color State Red Critical Orange Major Yellow Minor Green Up, OK, and Clear Purple Self-test (loopback) Gray Down (unmanaged) Blue Unknown Cyan Not defined 6.
Chapter 6 Configuring Hardware How Do I Manage My Network with the Configuration Center? 6.2.1 Launching Configuration Center To launch Configuration Center from the Domain Explorer: • Click on a node, then choose Configuration > MGX 8880/8850 MG > Configuration Center. The Configuration pane for that node appears.
Chapter 6 Configuring Hardware How Do I Manage My Network with the Configuration Center? 6.2.2 Navigating with Configuration Center The Configuration Center main window contains the following components: • Menu bar—See Table 6-5 • Toolbar—See Table 6-6 • Hierarchy, Configuration, and Inspector panes—See Table 6-7 Table 6-5 Configuration Center—Menu Bar Options Menu Bar Options Task File Save Saves the content. Print Displays the Print window to process printing.
Chapter 6 Configuring Hardware How Do I Manage My Network with the Configuration Center? Table 6-5 Configuration Center—Menu Bar Options (continued) Menu Bar Options Administration Task Allows you to perform adminstration-type tasks, such as: • Cisco MGM Audit Trail—Allows you to access audit trail files for specified days. • Telnet—(Only available when a NE is selected) Opens a command line tool to telnet to MGX switches.
Chapter 6 Configuring Hardware How Do I Manage My Network with the Configuration Center? Table 6-7 Configuration Center—Hierarchy, Configuration and Inspector Pane Descriptions (continued) Options Task Configuration pane Depending on the active tab (Elements or Connections), the configuration details for the selected object appear. If an object is not selected, the Configuration pane is empty. Fields within the Configuration pane with a * indicate required fields.
Chapter 6 Configuring Hardware How Do I Manage My Network with the Configuration Center? Figure 6-3 Configuration Center—Peripherals Tab, Serial Interfaces Category If you select the Create or Details button, a new window appears. This window contains five buttons: Note Some of these buttons may be grayed out, depending on availability.
Chapter 6 Configuring Hardware How Do I Manage Templates for Network Elements? Figure 6-4 Configuration Center—Peripherals Tab, Serial Interface Details 6.3 How Do I Manage Templates for Network Elements? • 6.3.1 Saving Templates for Network Elements, page 6-11 • 6.3.2 Loading or Deleting Templates for Network Elements, page 6-12 6.3.
Chapter 6 Configuring Hardware How Do I Manage Templates for Network Elements? Figure 6-5 Save Template Window Step 2 Enter the new name for the template in the Save As field. Step 3 Enter a description for the template in the Description field. Step 4 Ensure that the listed categories are correct in the Selected Categories area. Step 5 Click Save to save the current network element template, or Cancel to exit without saving. 6.3.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? 6.4 How Do I Configure Cisco MGX 8880 and 8850 Nodes? • 6.4.1 Configuring a Node, page 6-13 • 6.4.2 Displaying Cards Within a Node, page 6-15 • 6.4.4 Managing Node Peripherals, page 6-19 • 6.4.5 Viewing Node Controllers, page 6-25 • 6.4.6 Managing Node Clocking, page 6-26 6.4.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Step 2 Check or configure each field, as applicable. Note Step 3 Some fields are grayed out, meaning they are not configurable. Click Apply to apply the current node configuration settings. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Table 6-8 Field Descriptions for the Node Tab Field Name Description Description Description of the managed node.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? 6.4.2 Displaying Cards Within a Node Displaying cards within a node allows you to verify that the correct cards are installed in the correct slots, and that the back cards installed are indeed compatible with the front cards they serve. Step 1 From the Domain Explorer window, select the node from the Hierarchy pane and choose Configuration > MGX 8880/8850 MG > Configuration Center.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? 6.4.3 Verifying a Specific Card for the Node You can verify a card when the objects to be managed are associated with a particular card. Step 1 Within the Cards tab (see 6.4.2 Displaying Cards Within a Node, page 6-15) select the card from the summary report, then click Details. or Within the Configuration Center Hierarchy pane, double-click the card you want to view details for.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Note Step 3 The Back Card Configuration or Sec Back Card Configuration options are read-only. (Optional) Within the Front Card Configuration option, enter the card descriptor in the Descriptor field. Note The Descriptor field is valid for the whole Card Configuration, but is available only from the first category of that card configuration, in this case the Front Card Configuration.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Table 6-9 Field Descriptions for the Cards Tab (continued) Category Field Name Description Front, Back, and Sec Back Card Configuration (continued) Secondary Description (RPM only) Secondary back card description. Secondary Serial Number (RPM only) Secondary back card serial number. Secondary Secondary back card hardware revision.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Table 6-9 Field Descriptions for the Cards Tab (continued) Category Field Name Description Entity Sensors, Sensor Threshold Tab Threshold Index Index that uniquely identifies an entry in the entSensorThreshold table. This index permits the same sensor to have several different thresholds. Threshold Severity Severity of this threshold.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Figure 6-9 Step 3 Configuration Center—Peripherals Tab, IP Interfaces Category (Optional) Click Refresh to refresh the table. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. 6.4.4.2 Configuring Serial Interfaces Step 1 From the Domain Explorer window, select the node from the Hierarchy pane and choose Configuration > MGX 8880/8850 MG > Configuration Center.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Figure 6-10 Step 4 Configuration Center—Serial Interfaces Category (Optional) Click Details to view or modify information about a selected controller. The Serial Interface tab appears. Note For a description of all buttons within this table, see section 6.2.3 Navigating Within Tables, page 6-9. Cisco Media Gateway Manager 5.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Figure 6-11 Configuration Center—Peripherals Tab, Serial Interface Tab a. Enter the Speed, and configure the Stop Bits and Parity, if applicable. b. Click Apply. Note Table 6-10 describes the fields in the Serial Interfaces tab. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Cisco Media Gateway Manager 5.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Table 6-10 Field Descriptions for the Serial Interfaces Tab Field Name Description Port Index Interface index of the port. Speed (Bits Per Second) The input speed of the port. Stop bits The number of stop bits on the port: Parity • NA • one • two • oneAndHalf • dynamic The port’s sense of a character parity bit: • NA • none • odd • even • mark • space 6.4.4.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Figure 6-12 Note Step 4 Configuration Center—Peripherals Tab, Sensors Category Table 6-11 describes the fields in the Sensors table. (Optional) Click Refresh to refresh the table. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? 6.4.5 Viewing Node Controllers Step 1 From the Domain Explorer window, select the node from the Hierarchy pane and choose Configuration > MGX 8880/8850 MG > Configuration Center. The Configuration window for the selected node opens. Step 2 Click the Controllers tab. Figure 6-13 Note Step 3 Configuration Center—Controllers Tab Table 6-12 describes fields in the Controllers table.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Table 6-12 Field Descriptions for the Controllers Table Field Name Description Controller ID Unique value for VSI controller (VSI master). Controller Type Identifies the controller type. Controller Name Name chosen by the user for the VSI controller. Controller Shelf Location Identifies the location of the controller shelf. Controller Location Identifies the location of the controller. 6.4.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Figure 6-14 Note Configuration Center—Clocking Tab, Global Clocking Configuration Category Table 6-13 describes fields in the Clocking tab. Step 3 (Optional) Modify the fields as desired.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Figure 6-15 Note Step 4 Configuration Center—Clocking Tab, Available Clock Sources Category Table 6-13 describes fields in the Clocking tab. (Optional) Click Refresh to reload the table data. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. 6.4.6.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Figure 6-16 Note Step 4 Configuration Center—Clocking Tab, Manual Clock Sources Category Table 6-13 describes fields in the Clocking tab. To create a new clock source, proceed as follows: a. Click Create. Complete the following fields: – Priority – Clock Source Index b. Note Click Apply. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure Cisco MGX 8880 and 8850 Nodes? Table 6-13 Field Descriptions for the Clocking Tab Category Field Name Description Global Clocking Configuration Distribution Method Method used to distribute the network clock for the device. Stratum This variable contains the stratum level of the node. Max Diameter The maximum possible height of a network clock distribution tree in the network.
Chapter 6 Configuring Hardware How Do I Create or Modify APS? 6.5 How Do I Create or Modify APS? Automatic Protection Switching (APS) can be configured on SONET lines within SRME or AXSM and VXSM OC-type cards. If you are setting up APS on multiple cards, you must first set up an APS connector and then set up redundancy on the node (for details on setting up redundancy, see 5.5.1 Configuring Card Redundancy, page 5-49.
Chapter 6 Configuring Hardware How Do I Create or Modify APS? Note Table 6-27 describes fields in the Sonet Line APS tab. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Table 6-14 Field Descriptions for the Sonet Line APS Tab Field Name Description Working Bay Working bay number. Working Line Working line number. Protection Slot Protection slot number. Protection Bay Protection bay number. Protection Line Protection line number.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? 6.6 How Do I Configure AXSM Cards? Figure 6-18 Process for Configuring AXSM Cards Enable the AXSM line (Optional) Create or modify APS Create a port Create a resource partition 130001 Create a connection ATM Switch Service Module, or AXSM cards, can be configured in Cisco MGM by performing the following steps: Step 1 Enable the AXSM line—See the following sections: • For an OC-type AXSM card, see 6.6.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Step 3 Create a port—See 6.6.5 Creating a Port for AXSM, page 6-55. Step 4 Create a resource partition—See 6.6.6 Creating a Resource Partition for AXSM, page 6-57. Step 5 Create a connection—For information on creating connections, see Chapter 7, “Provisioning Connections.” 6.6.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Step 4 Choose the Up option from the Enable drop-down arrow. Step 5 (Optional) Verify or modify additional fields, as desired. Note Table 6-15 describes fields in the AXSM Line Config tab, Sonet Line Config category. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? 6.6.1.1 Configuring Sonet Medium Config Step 1 Within the Line Config tab (see 6.6.1 Enabling SONET Lines for AXSM, page 6-34) choose the Sonet Medium Config option from the Category drop-down arrow. Figure 6-20 Note Configuration Center—AXSM Sonet Line Config Tab, Sonet Medium Config Category Table 6-16 describes fields in the AXSM Line Config tab, Sonet Medium Config category.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-16 Field Descriptions for the AXSM Line Config Tab, Sonet Medium Config Category Field Name Description Medium Type Identifies whether a SONET or SDH signal is used across the interface. Time Elapsed Number of seconds (including partial seconds) elasped since the beginning of the current measurement period. Valid Intervals Number of previous 15 minute intervals for which data was collected.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? 6.6.1.2 Configuring the Sonet Line Alarm Step 1 Within the Line Config tab (see 6.6.1 Enabling SONET Lines for AXSM, page 6-34) choose the Sonet Line Alarm option from the Category drop-down arrow. Figure 6-21 Note Configuration Center—AXSM Line Config Tab, Sonet Line Alarm Category Table 6-17 describes fields in the AXSM Line Config tab, Sonet Line Alarm category.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Note The following thresholds are the same for Far End and Near End. Table 6-17 Field Descriptions for the AXSM Line Config Tab, Sonet Line Alarm Category Field Name Description Alarm Severity Setting this option to major or minor raises a corresponding severity alarm when any statistical threshold is exceeded. Note For alarm severity definitions, see Chapter 9, “Managing Faults.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? 6.6.1.3 Configuring the Sonet Section Alarm Step 1 Within the Line Config tab (see 6.6.1 Enabling SONET Lines for AXSM, page 6-34) choose the Sonet Section Alarm option from the Category drop-down arrow. Figure 6-22 Note Configuration Center—AXSM Line Config Tab, Sonet Section Alarm Category Table 6-18 describes fields in the AXSM Line Config tab, Sonet Section Alarm category.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Note The following thresholds are the same for Far End and Near End. Table 6-18 Field Descriptions for the AXSM Line Config Tab, Sonet Section Alarm Category Field Name Description Alarm Severity Setting this option to major or minor raises a corresponding severity alarm when any statistical threshold is exceeded. Note For alarm severity definitions, see Chapter 9, “Managing Faults.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? 6.6.1.4 Configuring the Sonet Path Alarm Step 1 Within the Line Config tab (see 6.6.1 Enabling SONET Lines for AXSM, page 6-34) choose the Sonet Path Alarm option from the Category drop-down arrow. Figure 6-23 Note Configuration Center—AXSM Line Config Tab, Sonet Path Alarm Category Table 6-19 describes fields in the AXSM Line Config tab, Sonet Path Alarm category.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Note The following thresholds are the same for Far End and Near End. Table 6-19 Field Descriptions for the AXSM Line Config Tab, Sonet Path Alarm Category Field Name Description Alarm Severity Setting this option to major or minor raises a corresponding severity alarm when any statistical threshold is exceeded. By default, TCA crossing does not raise any alarm. For alarm severity definitions, see Chapter 9, “Managing Faults.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? 6.6.1.5 Configuring the ATM Cell Layer Step 1 Within the Line Config tab (see 6.6.1 Enabling SONET Lines for AXSM, page 6-34) choose the ATM Cell Layer option from the Category drop-down arrow. Figure 6-24 Note Configuration Center—AXSM Line Config Tab, ATM Cell Layer Category Table 6-20 describes fields in the AXSM Line Config tab, ATM Cell Layer category.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-20 Field Descriptions for the AXSM Line Config Tab, ATM Cell Layer Category Field Name Description Cell Layer Description This string should include the name of the manufacturer, the product name, and the version of the hardware interface. Status Current operational state of the interface. The testing state indicates that no operational packets can be passed.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Figure 6-25 Configuration Center—AXSM DS1 Line Config Tab Step 4 Choose the Up option from the Admin Status drop-down arrow. Step 5 (Optional) Verify or modify additional fields, as desired. Note Table 6-21 describes fields in the AXSM DS1 Line Config tab. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-21 Field Descriptions for the AXSM DS1 Line Config Tab (continued) Field Name Description Line Length (meters) Length of the DS1 line. Only useful if the interface has configurable line build out circuitry. Loopback Status Current state of loopback on the DS1 interface. Descriptor Line descriptor. 6.6.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Step 4 Choose the Up option from the Interface Status drop-down arrow. Step 5 (Optional) Verify or modify additional fields, as desired. Note Table 6-22 describes fields in the AXSM DS3 Line Config tab, Line Config category. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-22 Field Descriptions for the AXSM DS3 Line Config Tab, Line Config Category (continued) Field Name Description Invalid Intervals Number of intervals in the range from 0 to dsx3ValidIntervals for which no data is available. Line Length (meters) Length of the DS3 line. Descriptor Line descriptor. 6.6.3.1 Setting Up Statistical Alarm Severity Step 1 Within the AXSM DS3 Line Config tab (for details, see 6.6.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-23 Field Descriptions for the AXSM DS3 Line Config Tab, 15 Min Alarm Config Category (continued) Field Name Description 15 Min LCV Threshold If this value is exceeded in a 15 minute window, a statistical alarm will be declared.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-24 Field Descriptions for the AXSM DS3 Line Config Tab, Dsx3 24 Hr Alarm Config Category Field Name Description 24 Hr LCV Threshold If this value is exceeded in a sliding 24 hour window, a statistical alarm will 24 Hr LES Threshold be declared. The threshold is checked every 15 minutes for the preceding 24 hour interval.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-25 Field Descriptions for the AXSM DS3 Line Config Tab, ATM Cell Layer Category Field Name Description Cell Layer Description This string should include the name of the manufacturer, the product name and the version of the hardware interface. Status Current operational state of the interface. The testing state indicates that no operational packets can be passed.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-26 Field Descriptions for the AXSM DS3 Line Config Tab, Plcp Alarm Category Field Name Description Plcp Statistical Alarm Severity of PLCP statistical alarm. Severity 15 Min BIP8Cv Threshold If this value is exceeded in a 15 minute or sliding 24 hour window, a statistical alarm will be declared.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Step 3 Click the AXSM Sonet Line APS tab. Within the Sonet Line APS tab, you can: a. Click Create to create a new Sonet Line APS or b. Select the line you want to modify, then click Details Figure 6-27 Configuration Center—AXSM Sonet Line APS Tab Step 4 Configure the fields. Step 5 Click Apply to save any changes. Note Table 6-27 describes fields in the AXSM Sonet Line APS tab.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-27 Field Descriptions for the AXSM Sonet Line APS Tab (continued) Field Name Description APS Mode Configures APS architecture mode on the working/protection line pairs. Active Line Indicates which line is active. Signal Fault BER Contains the bit error rate threshold for signal fault detection on the working line. Signal Degrade BER Contains the bit error rate threshold for signal degrade detection on the working line.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Figure 6-28 Step 4 Complete the active fields as desired. Note Step 5 Configuration Center—AXSM Port Config Tab Table 6-28 describes fields in the AXSM Port Config tab. Click Apply. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Table 6-28 Field Descriptions for the AXSM Port Config Tab Field Name Description Virtual Port Unique value for the ATM virtual interface.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-28 Field Descriptions for the AXSM Port Config Tab (continued) Field Name Description Interface Type Type of ATM virtual interface that can be configured within a physical interface. Values include: • uni • nni • vnni • vuni • evuni • evnni Vpi No (VUNI/VNNI) Vpi number. Min Vpi No (EVUNI/EVNNI) Minimum Vpi number. Max Vpi No (EVUNI/EVNNI) Maximum Vpi number. Descriptor Port descriptor. 6.6.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Figure 6-29 Step 4 Configuration Center—AXSM Resource Partitions Tab, ATM Resource Partition Category Input or modify the data as desired, then click Apply. Note Table 6-29 describes fields in the AXSM Resource Partitions tab, ATM Resource Partition category. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? Table 6-29 Field Descriptions for the AXSM Resource Partitions Tab, ATM Resource Partition Category (continued) Field Name Description Ingress Max BW Maximum percentage bandwidth for the resource partition in ingress direction. Range is 0 to 1000000. Min VPI Beginning of the VPI range for this partition. Max VPI End of the VPI range for this partition. Min VCI Beginning of the VCI range for this partition.
Chapter 6 Configuring Hardware How Do I Configure AXSM Cards? 6.6.6.1 Modifying ILMI Configuration Step 1 Within the AXSM Resource Partitions tab (see 6.6.6 Creating a Resource Partition for AXSM, page 6-57) choose the ILMI Configuration option from the Category drop-down arrow. Figure 6-30 Step 2 Configuration Center—AXSM Resource Partitions Tab, ILMI Configuration Category Choose the appropriate options from the ILMI Enabled and ILMI Trap Enable drop-down arrows, and modify data as desired.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-30 Field Descriptions for the AXSM Resource Partitions Tab, ILMI Configuration Category (continued) Field Name Description ILMI Est Conn Poll Intervals Time S between successive transmissions of ILMI messages on this interface for the purpose of detecting establishment of ILMI connectivity.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-31 Process for Configuring VXSM Cards Create a resource partition Create AAL5+control connections (Optional) Enable the mapping mode Create and assign an IP address for the connection Configure voice interfaces Check for existing VIFs Create a VIF View or modify VIF configuration Configure the TDM interface Enable SONET/SDH lines and paths (Optional) Change the line type to SDH Configure the MG and MGC interfaces 130014 C
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? To configure VXSM cards, you must perform the following steps: Step 1 Create a resource partition—See 6.7.1 Creating a Resource Partition for VXSM, page 6-63. Step 2 Create AAL5+control VXSM connections—See Chapter 7, “Provisioning Connections.” Step 3 (Optional, for OC3 cards only) Enable the mapping mode—See 6.7.2 Enabling the Mapping Mode for VXSM, page 6-65 Step 4 Create and assign an IP address for the connection—See 6.7.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-32 Step 8 Configure the fields. Note Step 9 Configuration Center—VXSM Create Resource Partitions Window Table 6-31 describes fields in the VXSM Create Resource Partitions window. Click Apply to create the resource partition. Table 6-31 Field Descriptions for the VXSM Create Resource Partitions Window Field Name Description Resource Partition ID Value for the resource partition identifier. The range is from 1-10.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-31 Field Descriptions for the VXSM Create Resource Partitions Window (continued) Field Name Description Min VPI Beginning of the VPI range for this partition. For RPM VCC partitions, the range is 0-0. For RPM VPC partitions, the range is 1-255. For VXSM, the range is 0-255. Max VPI End of the VPI range for this partition. For RPM VCC partitions, the range is 0-0. For RPM VPC partitions, the range is 1-255.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-32 Field Descriptions for the VXSM Media Gateway Tab, Gateway Capabilities Category Field Name Description Gateway Domain Name Domain name under which the media gateway could also be registered in a DNS name server. VT Mapping Mode Represents the VT mapping mode, which can be either: • standard—standard mapping mode • titan—Titan 5500 mapping mode.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-33 Field Descriptions for the VXSM Create PVC IP Address Window (continued) Field Name Description Prefix Length Specifies the number of leading one bits which from the mask to be logical and-ed with the media gateway address before being compared to the value in the cmgwIpCofigAddress. IP Address Type IP address type. Default Gateway IP Specifies the IP address of the entry will become the default gateway address. 6.7.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-33 Step 4 In the Medium Type field, click on the drop-down arrow to choose SDH. Note Step 5 Configuration Center—VXSM Line Config Tab, Sonet Medium Config Category Table 6-34 describes fields in the VXSM Line Config tab, Sonet Medium Config category. Click Apply to change the line type to SDH. Note Changing the line type to SDH on the first line trickles down to the other lines.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-34 Field Descriptions for the VXSM Line Config Tab, Sonet Medium Config Category (continued) Field Name Description Valid Intervals Number of previous 15 minute intervals for which data was collected. Circuit ID The transmission vendor’s circuit identifier, for the purpose of facilitating troubleshooting. Note The circuit identifier, if available, is also represented by ifPhysAddress. 6.7.4.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Note f. Click Apply. Note Step 3 Table 6-36 describes fields in the VXSM Path Config tab, Paths category. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Enable the DS1/E1 line: a. Under the Elements tab, within the node, expand the VXSM OC3 card and expand the SONET line, STS path, and VT path that contain the DS1/E1 line you want to enable. Double-click on the DS1/E1 line.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-35 Field Descriptions for the VXSM Line Config Tab, Sonet Line Config Category (continued) Field Name Description RDIV Type Specifies the type of Remote Defect Indication - Virtual Tributary/Container (RDI-V) sent by this NE to the remote NE.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-37 Field Descriptions for the VXSM DS1/E1 Path Tab, DS1/E1 Line Info Category (continued) Field Name Description Line Type Indicates the variety of DS1 line implementing this circuit. Values include: • For T1 interfaces only: – dsx1ESF—Extended SuperFrame DS1 (T1.107) – dsx1D4—AT&T D4 format DS1 (T1.107) • For E1 interfaces only: – dsx1E1—ITU-T Recommendation G.704 (Table 4a). – dsx1E1CRC—ITU-T Recommendation G.704 (Table 4b).
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? 6.7.4.3 Enabling SDH Lines and Paths for VXSM If you are using SDH, you must enable the lines and paths in the following order: 1. SDH line 2. STM path 3. DS1/E1 line Perform the following steps: Step 1 Step 2 Enable the SDH line: a. From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. b. Under the Elements tab, within the node, expand the VXSM OC3 card and double-click on the SDH line.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? 6.7.5 Configuring Voice Interfaces A voice interface (VIF) is a set of parameters applied to a group of DS0s within a DS1 in the TDM voice network. To configure voice interfaces, proceed as follows: Step 1 Check to see if there are existing VIFs—See 6.7.5.1 Checking for Existing VIFs for VXSM, page 6-74. If there are no existing VIFs, proceed to Step 2 or if there are existing VIFs, skip Step 2. Step 2 (Optional) Create a VIF—See 6.7.5.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-34 Step 5 Configure the fields. Note Step 6 Configuration Center—VXSM Create DSX0 Group Window Table 6-38 describes the fields in the VXSM Create DSX0 Group window. Click Apply to add the VIF. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? 6.7.5.3 Viewing or Modifying VIF Configuration Step 1 From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. Step 2 Under the Elements tab, within the node, expand the VXSM card until you see the DS1 path you want to view VIFs under. Double-click the DS1 path. The DS1 Path tab appears. Step 3 Choose DSX0 Voice Parameters or Extended DSX0 Voice Parameters from the Category drop-down arrow.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-40 Field Descriptions for the VXSM DS1 Path, Extended DSX0 Voice Parameters Category Field Name Description DSX0 Grp Index Index that uniquely identifies a DS0 group in a T1/E1. LIF Number Logical InterFace number associated with this voice interface. Call Control Profile Index of call control profile used by this DS0 group.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-35 Process for Configuring MG-MGC Interfaces 1. Prerequisites: Create a resource partition Create AAL5+control connections 2. To configure MG-MGC interfaces: Set up MGC and MGC groups Configure H.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? 6.7.6.1 Setting Up MGCs and MGC Groups Figure 6-36 Process for Setting Up MGCs and MGC Groups Create a domain name for the MGC Change the IP address resolution and (optionally) create an IP address for the domain (XGCP only) Configure the MGC group for XGCP 130006 Add a MGC to a MGC group Step 1 Create an MGC by assigning it a domain name, and specify how the domain name is to be resolved: a.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-37 e. Configure the fields. Note f. Step 2 Configuration Center—VXSM Create MGC Domain Names Window Table 6-41 describes fields in the VXSM Create MGC Domain Name window. Click Apply to create the domain name. Change the IP address resolution and (optionally) create an IP address for the domain: a. Under the Elements tab, within the node, double-click the VXSM card. b. Click on the MG Controller tab. c.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-38 e. Configuration Center—VXSM Media Gateway Controllers Tab Configure the IP Address Resolution field. Note Table 6-42 describes fields in the VXSM Media Gateway Controllers tab. f. Click Apply to configure the IP address resolution. g. If you selected internalOnly, proceed to step h to create an IP address for the domain. If you selected externalOnly, skip the rest of these steps and proceed to step 3. h.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-39 j. Configure the fields. Note k. Step 3 Configuration Center—VXSM Create MGC IP Addresses Window Table 6-43 describes fields in the VXSM Create MGC IP Addresses window. Click Apply to create the MGC IP address. (XGCP only, skip to step 4 if you are using H.248) Configure the MGC group for XGCP: a. Under the Elements tab, within the node, double-click the VXSM card. b. Click on the XGCP tab. c.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-40 d. Configure the fields. Note e. Step 4 Configuration Center—XGCP Tab, XGCP MGC Association Category Table 6-44 describes fields in the VXSM XGCP tab, XGCP MGC Association category. Click Apply to configure the MGC group for XGCP. Add a MGC to a MGC group: a. Under the Elements tab, within the node, double-click the VXSM card. b. Click on the MG Controller tab. c.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-41 e. Complete the fields. Note f. Configuration Center—VXSM Create MGC Groups Window Table 6-45 describes fields in the VXSM Create MGC Groups window. Click Apply to add a specific MGC to a particular MGC group. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Cisco Media Gateway Manager 5.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-41 Field Descriptions for the VXSM Create MGC Domain Name Window Field Name Description Domain Index Enter an integer to identify a MGC domain name. The following values are valid: Domain Name Type Domain Name Table 6-42 • For MGC, The range is from 1-4. • For a gateway, the value is 13. • For dnsServer, the value is 14.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-43 Field Descriptions for the VXSM Create MGC IP Address Window (continued) Field Name Description IP Address Type IP address type for the MGC (call agent): unknown ipv4 ipv6 ipv4z ipv6z dns Preference Table 6-44 Preference value of the IP address for the specific MGC (call agent). If the value is lower, the preference of the IP address is higher. For example, the value 1 has a higher preference than the value 2.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-45 Field Descriptions for the VXSM Create MGC Groups Window Field Name Description MGC Grp Index Unique index value to identify the particular MGC group. The range is 1-12. MGC Index Unique index value to identify each MGC (call agent) that communicates with the media gateway. The range is 1-4. Preference value of the IP address for the specific MGC (call agent). If the value is lower, the preference of the IP address is higher.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-42 Process for Configuring H.248 Protocol and Profiles Add an MG and MGC association Configure a port for the MG-MGC link Add an H.248 profile Configure terminations for the SCN side of VXSM 130004 Configure terminations for the PDN side of VXSM Step 1 Add an MG and MGC Association: a. From the Domain Explorer window, select the node from the Hierarchy pane and choose Configuration > MGX 8880/8850 MG > Configuration Center.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-43 f. Complete the fields. Note g. Step 2 Configuration Center—VXSM Create MG-MGC Association Window Table 6-46 describes fields in the VXSM Create MG-MGC Association window. Click Apply to add an H.248 association between the MG and MGC. Once you have created an MG-MGC association, an entry will appear in the H.248 tab, Extended Association category. Configure a port for the MG-MGC link: a.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-44 e. Configure the Gateway Port, and other fields as desired. Note f. Step 3 Configuration Center—VXSM Extended Association Tab Table 6-47 describes fields in the VXSM Extended Association tab. Click Apply to configure the port for the MG-MGC link. Add an H.248 profile: a. Within the H.248 tab, choose the Profile Properties option from the Category drop-down arrow. b. Click Create. The Create H.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-45 c. Configure the fields. Note d. Step 4 Step 5 Configuration Center—VXSM Create H.248 Profile Properties Window Table 6-48 describes fields in the VXSM Create H.248 Profile Properties window. Click Apply to create the H.248 profile. Configure terminations for the switch circuit network (SCN) side of VXSM: a. Add a voice interface (VIF)—See 6.7.5 Configuring Voice Interfaces, page 6-74. b.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-46 c. Configure the fields. Note d. Configuration Center—VXSM Create H.248 Termination Types Window Table 6-49 describes fields in the VXSM Create H.248 Termination Types window. Click Apply to create the H.248 termination type. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-46 Field Descriptions for the VXSM Create MG-MGC Association Window (continued) Field Name Description Transport Protocol Choose one of the following options that is used for the signaling traffic associated with the H.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-47 Field Descriptions for the VXSM Extended Association Tab (continued) Field Name Description Restart Delay Time delay before the MG accepts any call from MGC after it sends the command “service change” with a “restart.” Response Retention Time Time till the responses should be retained before they are sent if they receive a repetition of a transaction that is still being executed.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-48 Field Descriptions for the VXSM Create H.248 Profile Properties Window (continued) Field Name Description Detect Long CP Tone Duration (milliseconds) Duration for detecting a long call progressing tone. Detect Long Digit Duration (milliseconds) Duration for detecting a long digit tone signal. Echo Cancellation Specifies whether or not the echo cancellation is enabled. Echo Canceller Tail Echo canceller coverage.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? 6.7.6.3 Configuring XGCP Protocol Once you have completed the steps in 6.7.6.1 Setting Up MGCs and MGC Groups, page 6-79, perform the following steps to configure XGCP (TGCP) protocol: Step 1 From the Domain Explorer window, select the node from the Hierarchy pane and choose Configuration > MGX 8880/8850 MG > Configuration Center. The Configuration window for the selected node opens.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-50 Field Descriptions for the VXSM XGCP Tab, Media Gateway XGCP Configuration Category Field Name Description Request Timeout (milliseconds) Period that the XGCP (TGCP) protocol waits before re-transmitting an unacknowledged message. It is the responsibility of the requesting entity to provide suitable timeouts for all outstanding commands, and to retry commands when timeouts exceeded.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-50 Field Descriptions for the VXSM XGCP Tab, Media Gateway XGCP Configuration Category (continued) Field Name Description Dtmf Relay When the value is true, the digits will be sent as peer-to-peer packet in the bearer. When the value is false, the digits will be sent as regular voice packets in the bearer.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-48 Step 6 Configure the fields. Note Step 7 Configuration Center—VXSM Create XGCP Call Control Profile Window Table 6-51 describes fields in the VXSM Create XGCP Call Control Profile window. Click Apply to create the XGCP (TGCP) call control profile. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-51 Field Descriptions for the VXSM Create XGCP Call Control Profile Window (continued) Field Name Description Max1 DNS Lookup Enabled Enables or disables the Max1 domain name server (DNS) query operation when Max1 expires. Disconnect Error Threshold Contains the disconnect error threshold for signaling messages. Max2 DNS Lookup Enabled Enables or disables the Max2 domain name server (DNS) query operation when Max2 expires.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-51 Field Descriptions for the VXSM Create XGCP Call Control Profile Window (continued) Field Name Description Dial Tone Timeout (seconds) Specifies the time for which the dial tone will be generated unless interrupted. A value of zero indicates that the tone will be generated indefinitely unless interrupted.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? 6.7.7.1 Creating a RUDP Session Figure 6-49 Process for Creating a RUDP Session 1. Prerequisites: Create a resource partition Create AAL5+control connections 2.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? To proceed with the creation of a RUDP session, complete the following steps: Step 1 Create a MGC session set—See 6.7.7.1.1 Creating a MGC Session Set, page 6-103. Step 2 Create a MGC session group—See 6.7.7.1.2 Creating a MGC Session Group, page 6-104. Step 3 Create a RUDP session—See 6.7.7.1.3 Creating a RUDP Session, page 6-106. 6.7.7.1.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Step 6 Complete the fields. Note Step 7 Table 6-52 describes fields in the VXSM Create Session Set window. Click Apply to add a MGC session set. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Table 6-52 Field Descriptions for the VXSM Create Session Set Window Field Name Description Session Set Number Logical index of this table.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-51 Step 6 Complete the fields. Note Step 7 Configuration Center—VXSM Create Session Group Window Table 6-53 describes fields in the VXSM Create Session Group window. Click Apply to add a MGC session group. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-53 Field Descriptions for the VXSM Create Session Group Window (continued) Field Name Description Number of Fail Attempts Keeps track of failed attempts to switch between sessions in this group. Number of Success Attempts Keeps track of successful attempts to switch between sessions in this group. 6.7.7.1.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Step 6 Complete the fields. Note Step 7 Table 6-54 describes fields in the VXSM Create RUDP Session window. Click Apply to add a RUDP session. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Table 6-54 Field Descriptions for the VXSM Create RUDP Session Window Field Name Description Session Number Index for this table. One group can have a maximum of four sessions.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-54 Field Descriptions for the VXSM Create RUDP Session Window (continued) Field Name Description Accumulated Acknowledgement TimeOut (ms) (in milliseconds) Timeout value for sending an acknowledgment segment if another segment is not sent. Max Number Of Out Of Sequence Packets Max number of out of sequence packets that will be accumulated before an EACK segment is sent.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-53 c. Configure the fields. Note d. Step 5 Configuration Center—VXSM Create VBD Profile Window Table 6-55 describes the fields in the VXSM Create VBD Profile window. Click Apply to create the VBD profile. Create two event mapping indexes: a. Choose the Event Mapping option from the Category drop-down arrow. b. Click Create. The Create Event Mapping window appears. Cisco Media Gateway Manager 5.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-54 c. Configure the fields. Make sure to create one Event Index as ced, and a second Event Index as v21Tone. Note d. Note Configuration Center—VXSM Create Event Mapping Window Table 6-56 describes the fields in the VXSM Create Event Mapping window. Click Apply to create one event mapping index. Perform Step 5 again, and create a second index. For a description of all buttons within this tab, see section 6.2.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-56 Field Descriptions for the VXSM Create Event Mapping Window Field Name Description Profile Index This object uniquely identifies the VBD profile. Upspeed CODEC Type Specifies the CODEC type to use for upspeed. Jitter Buffer Delay Mode Specifies the jitter buffer mode applied to the VBD call connection. Jitter Maximum Delay Specifies the maximum jitter buffer size in the VBD connection.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Figure 6-55 Step 6 Configure the fields. Note Step 7 Configuration Center—VXSM PRI-BH Create Window Table 6-57 describes the fields in the VXSM PRI-BH Create window. Click Apply to create PRI-BH. Table 6-57 Field Descriptions for the VXSM PRI-BH Create Window Field Name Description DS0 Number DS0 number. Application Type Specifies the application type for the corresponding LAPD D channel.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-57 Field Descriptions for the VXSM PRI-BH Create Window (continued) Field Name Description T200 Specifies the maximum time to wait for acknowledgment of a transmit frame. T203 Specifies the maximum time in milliseconds allowed without frames being exchanged. This value should be greater than the value for T200. 6.7.7.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? Table 6-58 Field Descriptions for the VXSM Voice Features Tab, Announcement Controls Category Field Name Description Announcement Server Specifies the domain name of an announcement file server that resides in an Domain Name IP network and is reachable from the media gateway. The default value of this object is NULL string (size is 0). Before using any object in this table, this object should be configured to non-NULL.
Chapter 6 Configuring Hardware How Do I Configure VXSM Cards? To map an announcement name number to the announcement filename: Step 1 Within the VOICE Features tab, choose the Announcement Files option from the Category drop-down arrow. Step 2 Click Create to display the Announcement Files Configuration window. Step 3 Configure the fields. Note Step 4 Table 6-58 describes fields in the VXSM Voice Features tab, Announcement Files category.
Chapter 6 Configuring Hardware How Do I Configure RPM Cards? Table 6-59 Field Descriptions for the VXSM Voice Features Tab, Announcement Files Category (continued) Field Name Description File Type Announcement file type. Values include: • dynamic (default)—specifies the dynamic file is removed from the cache when the age of the file reaches a specified limit or in accordance with a Least Replaceable Unit (LRU) algorithm when the cache is full.
Chapter 6 Configuring Hardware How Do I Configure RPM Cards? 6.8.1 Creating a Resource Partition for RPM Step 1 From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. Step 2 Under the Elements tab, within the node, double-click the RPM card. Step 3 Click the Resource Partitions tab. Step 4 Click Create. The Create Resource Partitions window appears. Figure 6-57 Step 5 Configure the fields.
Chapter 6 Configuring Hardware How Do I Configure RPM Cards? Table 6-60 Field Descriptions for the RPM Create Resource Partitions Window (continued) Field Name Description Controller ID Value for the controller identifier. The range is from 2-255. The value 2 is reserved for PNNI, the others are for LSC. Egress Guaranteed BW Guaranteed percentage bandwidth reserved for the resource partition in egress direction. The range is from 0-1000000.
Chapter 6 Configuring Hardware How Do I Configure RPM Cards? 6.8.2 Creating or Modifying an ATM Subinterface By preparing to create the master end of the connection to the VXSM card, you must create an ATM subinterface on the RPM card. Step 1 From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. Step 2 Under the Elements tab, within the node, double-click the RPM card. Step 3 Click the Ports tab to display the entries for the Ports Table for RPM.
Chapter 6 Configuring Hardware How Do I Configure RPM Cards? Table 6-61 Field Descriptions for the RPM Ports Create/Details Window Field Name Description Main Interface Specifies the main interface. Subinterface Num Specifies the subinterface. Adapter IF Maps to the RPMs port adapter interface. Currently only one port adapter interface (switch 1) is supported. IfType Specifies the link type of this subinterface. IP Address Specifies the 4-octet IP address of this subinterface.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9 How Do I Configure VISM-PR Cards? Figure 6-59 Process for Configuring VISM-PR Cards Set up the VISM-PR card Configure Time Division Multiplexing (TDM) Configure jitter 130012 Configure VoIP switching In order to configure Voice Inter-working Service Module Premium (VISM-PR) cards, you must perform the following steps: Step 1 Set up the VISM-PR card—See 6.9.1 Setting Up a VISM-PR Card, page 6-122.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.1 Setting Up a VISM-PR Card Figure 6-60 Process for Setting Up a VISM-PR Card Create a virtual port Create a resource partition (Optional) View the CODEC templates 130009 (Optional) View the current configuration settings In order to set up a VISM-PR card, you must perform the following steps: Step 1 Create a virtual port—See 6.9.1.1 Creating a Virtual Port for VISM-PR, page 6-123. Step 2 Create a resource partition—See 6.9.1.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.1.1 Creating a Virtual Port for VISM-PR Note Only one virtual port is allowed on a VISM-PR card. To create a virtual port for the VISM-PR card: Step 1 From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. Step 2 Under the Elements tab, within the node, double-click the VISM-PR card. Step 3 Click the Port tab to display the port table.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-62 Field Descriptions for the VISM-PR Create Port Window Field Name Description Port Number Virtual port number for the VISM-PR card. Port Type Indicates the network port. Value of this object is always set to VoIP. Port Speed Advertises virtual port bandwidth to the controller, SVC and PVC connection admission control, and aggregate traffic clipping. Port State Current state of the port. Descriptor Port descriptor. 6.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Step 8 Complete the fields. Note Step 9 Table 6-63 describes fields in the VISM-PR Create Resource Partitions window. Click Apply to create the resource partition. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9 Table 6-63 Field Descriptions for the VISM-PR Create Resource Partitions Window Field Name Description Logical Port Num Index to this table.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? To view a list of all possible CODEC templates on the VISM-PR card: Step 1 From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. Step 2 Under the Elements tab, within the node, double-click the VISM-PR card. Step 3 Click the CODECs tab. The CODECs Supported category appears by default. All supported CODEC templates are listed in the table.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Note Table 6-65 describes fields in the VISM-PR Media Gateway tab, Gateway Capabilities category. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. 6.9.1.3.1 Configuring VoIP CODECs Step 1 From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. Step 2 Under the Elements tab, within the node, double-click the VISM-PR card.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Step 5 Complete the fields. Note Table 6-64 describes the fields in the VISM-PR Codec Configuration window. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Step 6 Click Apply to configure the VoIP CODEC. Table 6-64 Field Descriptions for the VISM-PR Codec Configuration Window Field Name Description Index Index to this table.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-65 Field Descriptions for the VISM-PR Media Gateway Tab, Gateway Capabilities Category Field Name Description Features Enabled Features enabled on this VISM-PR card. Available Ds0 EndPoints Number of DS0s available for new connections on VISM-PR. This is modified by the VISM-PR firmware after each connection is setup. Codec Template Number of the CODEC template currently configured on the VISM-PR card.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.2 Configuring TDM for VISM-PR Figure 6-65 Process for Configuring TDM for VISM-PR Configure T1/E1 lines (Optional) Place T1/E1 lines in or out of service (Optional) Add bulk distribution 130011 Configure Echo Cancellation (ECAN) In order to configure the Time Division Multiplexing (TDM) on a VISM-PR card, you must perform the following steps: Step 1 Configure T1/E1 lines—See 6.9.2.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.2.1 Configuring T1 and E1 Lines for VISM-PR You can have eight physical T1 or E1 ports on the VISM-PR back card. For detailed information on how to configure CAS signaling for the TDM side of the network application, refer to the Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.3 To configure T1 and E1 lines on VISM-PR, complete the following steps: Step 1 Add a T1 or E1 line—See 6.9.2.1.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Step 3 Step 4 Choose one of the following options to enable or disable the line in the Line Enable drop-down arrow: • disable • enable • modify Configure additional parameters as desired. Note Step 5 Table 6-66 describes fields in the VISM-PR Line Config tab, Physical Line Config (DSX1) category. Click Apply to add the T1 or E1 line. Note For a description of all buttons within this tab, see section 6.2.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-66 Field Descriptions for the VISM-PR Line Config Tab, Physical Line Config (DSX1) Category (continued) Field Name Description Loopback Command Loopback configuration of the DS1 interface. Values include: Code Sent • dsx1NoLoop • dsx1RemoteLoop • dsx1LocalLoop • dsx1PayloadLoop Indicates the type of code being sent across the DS1 interface by the device.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-67 Step 4 Step 5 Choose one of the following options to configure signaling on the line in the Signaling Type drop-down arrow: • cas • ccs • none Configure additional parameters as desired. Note Step 6 Configuration Center—VISM-PR Specific DS1 Tab, VISM Line Config Category Table 6-67 describes fields in the VISM-PR Specific DS1 tab, VISM Line Config category. Click Apply to configure signaling on the T1 or E1 line.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-67 Field Descriptions for the VISM-PR Specific DS1 Tab, VISM Line Config Category Field Name Description Line Number T1/E1 line number. Ecan Enable Indicates whether the echo cancellation feature is enabled or disabled. Maximum tail. Should be set just higher than the worst rount trip delay anticipated. Convergence times might increase for longer tails, and more resources are used.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-67 Field Descriptions for the VISM-PR Specific DS1 Tab, VISM Line Config Category (continued) Field Name Description Sa4 Byte Spare bit on T1/E1 framer reserved for international standardization. Sa5 Byte Sa6 Byte Sa7 Byte Sa8 Byte Line State Allows the line administrative state (in service and out of service) to be persistent.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-68 Step 4 Configure the parameters as desired. Note Step 5 Configuration Center—VISM-PR Line Config Tab, Physical Line Alarm Config (DSX1) Category Table 6-68 describes fields in the VISM-PR Line Config tab, Physical Line Alarm Config (DSX1) category. Click Apply to configure alarm conditioning handling on the T1 or E1 line. Note For a description of all buttons within this tab, see section 6.2.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-68 Field Descriptions for the VISM-PR Line Config Tab, Physical Line Alarm Config (DSX1) Category Field Name Description Setup Red Alarm Severity Allows you to set up the severity of a RED alarm, so that when a LOS alarm is detected, VISM-PR will send the alarm with the appropriate severity status.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.2.2 Placing T1 or E1 Lines In or Out of Service Step 1 From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. Step 2 Under the Elements tab, within the node, double-click the DS1 line under the VISM-PR card. Step 3 Click the VISM Specific DS1 tab. The VISM Line Config option appears by default in the Category drop-down arrow.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-69 Step 5 Complete the fields. Note Step 6 SRME Create Line Distribution Window Table 6-69 describes fields in the SRME Create Line Distribution window. Click Apply to add bulk distribution. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.2.4 Configuring ECAN for VISM-PR Step 1 From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. Step 2 Under the Elements tab, within the node, double-click the DS1 line under the VISM-PR card. Step 3 Click the VISM Specific DS1 tab. The VISM Line Config option appears by default in the Category drop-down arrow.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-70 Step 6 Complete the fields. Note Step 7 Configuration Center—VISM-PR Jitter Buffer Window Table 6-70 describes fields in the VISM-PR Jitter Buffer window. Click Apply to configure the jitter parameters. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? To configure VoIP switching for VISM-PR cards, complete the following steps: Step 1 (Optional) Configure VoIP parameters—See 6.9.4.1 Configuring VoIP Parameters for VISM-PR, page 6-144. Step 2 Configure the ATM network—See 6.9.4.2 Configuring the ATM Network for VISM-PR, page 6-146. Step 3 Configure the call agent interface—See 6.9.4.3 Configuring the Call Agent Interface for VISM-PR, page 6-146.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-71 Field Descriptions for the VISM-PR Media Gateway Tab, VoIP Parameters Option (continued) Field Name Description RTP Receive Timer Defines whether the RTP packets receive timer on the VISM needs to be enabled or not. DTMF Relay Defines whether the Dual Tone, Multi-Frequency digits need to be transported to the other endpoint via Named Signal Event (NSE) packets.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.4.2 Configuring the ATM Network for VISM-PR To configure the ATM network for VISM-PR cards by adding and configuring connections, please see Chapter 7, “Provisioning Connections.” 6.9.4.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.4.3.1 Specifying the Domain Name, IP Address and Subnet Mask for VISM-PR Step 1 From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. Step 2 Under the Elements tab, within the node, double-click the VISM-PR card. Step 3 Click the Media Gateway tab. Step 4 Choose the Gateway IP Address option from the Category drop-down arrow.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Step 5 Complete the fields. Note Step 6 Table 6-72 describes fields in the VISM-PR Media Gateway tab, Gateway IP Address category. Click Apply to configure the parameters. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.4.3.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? To set up call agents and protocols for VISM-PR, complete the following steps: Step 1 Configure the domain name server for the external domain name resolution: a. From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. b. Under the Elements tab, within the node, double-click the VISM-PR card. c. Click the Media Gateway tab.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Step 3 If you have not set the Resolution Type to externalOnly in Step 2, proceed to Step 4 or If you have set the Resolution Type to externalOnly in Step 2, proceed to Step 5. Step 4 (Optional, see Step 3) Add the IP address for the Domain Name you created in Step 2: a. Within the MG Controller tab, choose the IP Address Resolution option from the Category drop-down arrow. b. Click Create.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-77 c. Note d. Step 6 Configuration Center—VISM-PR Create Media Gateway Controllers Window Complete the fields. Table 6-73 describes fields in the VISM-PR MG Controller tab, Media Gateway Controllers category. Click Apply. Add the MGC to a redundancy group: a. Within the MG Controller tab, choose the MGC Group option from the Category drop-down arrow. b. Click Create. The VISM-PR Create MGC Group window appears.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-78 c. Note d. Step 7 Configuration Center—VISM-PR Create MGC Group Window Complete the fields. Table 6-73 describes fields in the VISM-PR MG Controller tab, MGC Group category. Click Apply. Change the parameters of the MGC group: a. Within the MG Controller tab, choose the MGC Group Params option from the Category drop-down arrow. b. Click on the MG group entry you want to modify, then click Details.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-79 c. Note d. Step 8 Configuration Center—VISM-PR MGC Group Params Window Complete the fields. Table 6-73 describes fields in the VISM-PR MG Controller tab, MGC Group Params category. Click Apply. Associate a call agent redundancy group with a gateway control protocol: a. Within the MG Controller tab, choose the MGC Group Protocols option from the Category drop-down arrow. b. Click Create.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-80 c. Note d. Configuration Center—VISM-PR Create MGC Group Protocols Window Complete the fields. Table 6-73 describes fields in the VISM-PR MG Controller tab, MGC Group Protocols category. Click Apply. Once you have created the MGC group protocol, Cisco MGM automatically adds an SRCP peer. For details on configuring SRCP peers, see Step 7 in section 6.9.4.3.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-73 Field Descriptions for the VISM-PR MG Controller Tab Category Field Name Description Domain Names Index Index to this table. Domain Name Domain name of MGCs, tftp server, external DNS server, or announcement server. Resolution Type Type of DNS resolution to be applied for a particular domain name.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-73 Field Descriptions for the VISM-PR MG Controller Tab (continued) Category Field Name Description MGC Group Params MGC Group Num MGC group number. A group can contain more than one MGC. Association State Control Enables or disables sending state change notifications to the call agent. MGC Group Protocols State of Association Represents the state of the communication between the MG and the MGC (call agent) groups.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? 6.9.4.3.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? To configure the gateway control protocol port for VISM-PR, complete the following steps: Step 1 Configure a port number for a particular call agent and protocol: a. From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center. b. Under the Elements tab, within the node, double-click the VISM-PR card. c. Click the XGCP tab. d. Choose the XGCP Peers option from the Category drop-down arrow. e.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-83 b. Note c. Step 3 Configuration Center—VISM-PR XGCP Tab, XGCP Parameters Category Configure the Restart in Progress MWD field. Table 6-74 describes fields in the VISM-PR XGCP tab, XGCP Parameters category. Click Apply. Specify the VISM-PR minimum and maximum wait time for a call agent message acknowledgment: a. Within the XGCP tab, choose the XGCP Enhancement Parameters option from the Category drop-down arrow.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-84 b. Note c. Step 4 Configure the fields. Table 6-74 describes fields in the VISM-PR XGCP tab. XGCP Enhancement Parameters category. Click Apply. Specify the VISM-PR number of retries for a call agent message acknowledgment: a. Within the XGCP tab, choose the XGCP Parameters option from the Category drop-down arrow (see Figure 6-83). b. Configure the Request Retries field. Note c.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-85 c. Note d. Step 6 Configuration Center—VISM-PR Media Gateway Tab, Bearer Traffic Category Configure the Bearer N/W Type, Bearer VC Type, and Bearer Connection Type fields. Table 6-75 describes fields in the VISM-PR Media Gateway tab, Bearer Traffic category. Click Apply. Designate XGCP events as persistent: a. Within the XGCP tab, choose the XGCP Persistent Events option from the Category drop-down arrow. b.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-86 c. Note d. Step 7 Configuration Center—VISM-PR Create XGCP Persistent Events Window Configure the Event Number and Event Name fields. Table 6-74 describes fields in the VISM-PR XGCP tab, XGCP Persistent Events category. Click Apply. Specify the SRCP parameters for communication between VISM-PR and the call agent: a. Within the XGCP tab, choose the SRCP Peers option from the Category drop-down arrow. b.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-87 c. Note d. Step 8 Configuration Center—VISM-PR SRCP Peers Tab Complete the fields. Table 6-74 describes fields in the VISM-PR XGCP tab, SRCP Peers category. Click Apply. Configure the SRCP heartbeat interval and maximum UDP size for a specified call agent redundancy group: a. Within the XGCP tab, choose the SRCP Peer Group Parameters option from the Category drop-down arrow. b. Click on a peer entry, then click Details.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-88 c. Note d. Note Configuration Center—VISM-PR SRCP Peer Group Parameters Tab Complete the fields. Table 6-74 describes fields in the VISM-PR XGCP tab, SRCP Peer Group Parameters category. Click Apply. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-74 Field Descriptions for the VISM-PR XGCP Tab (continued) Category Field Name Description XGCP Parameters Bad Versions Total number of incoming messages that were delivered to the protocol entity and were for an unsupported protocol version. Unrecognized Packets Request Retries Specifies the number of retries for a request that exceeds timeout.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-75 Configuration Center—VISM-PR Media Gateway Tab, Bearer Traffic Category Field Name Description Bearer N/W Type Network type to transport bearer traffic. Values are IP or ATM. Bearer VC Type VC type to transport bearer traffic. Values are PVC or SVC. Bearer Connection Type Connection type used to transport bearer traffic. If the Bearer N/W Type is set to IP, then the value of this object must be set to not applicable.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-89 f. Note g. Step 2 Configuration Center—VISM-PR Create RUDP Session Set Window Complete the fields. Table 6-76 describes fields in the VISM-PR MG Controller tab, RUDP Session Set category. Click Apply to add a RUDP session set. Create a session group for a session set and a call agent: a. Within the MG Controller tab, choose the RUDP Session Group option from the Category drop-down arrow. b. Click Create.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-90 c. Note d. Step 3 Configuration Center—VISM-PR Create RUDP Session Group Window Complete the fields. Table 6-76 describes fields in the VISM-PR MG Controller tab, RUDP Session Group category. Click Apply to add a session group. Create an ISDN PRI backhaul RUDP session within a specified group: a. Within the MG Controller tab, choose the RUDP Session option from the Category drop-down arrow. b. Click Create.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-91 c. Note d. Note Configuration Center—VISM-PR Create RUDP Session Window Complete the fields. Table 6-76 describes fields in the VISM-PR MG Controller tab, RUDP Session category. Click Apply to add a session group. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Cisco Media Gateway Manager 5.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-76 Configuration Center—VISM-PR MG Controller Tab Category Field Name Description RUDP Session Set Session Set Number Logical index of this table. Currently only set 1 is used, and all the signaling channels are implicity mapped to set 1. Session Set State Denotes the state the set is in. Total Session Groups Keeps track of the number of session groups that has been added to a session set.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-76 Configuration Center—VISM-PR MG Controller Tab (continued) Category Field Name Description RUDP Session Session Number Index for this table. One group can have a maximum of four sessions. Session Group Number A mandatory parameter if session type is backhaul, indicates the session group that this session belongs to. Session Type Indicates if the session is configured for trunking or PRI backhaul.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-76 Configuration Center—VISM-PR MG Controller Tab (continued) Category Field Name Description RUDP Session (continued) Max Attempts to Synchronize Max number of attempts to synchronize with other side (MGC). Max Segment Size Max number of octets that can be received by the peer sending the SYN segment. Max Auto Resets Max number of consecutive auto reset that will be performed before a connection is reset.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-92 Step 5 Configure the fields. Note Step 6 Configuration Center—VISM-PR Create LAPD Channel Parameters Window Table 6-77 describes fields in the VISM-PR Create LAPD Channel Parameters window. Click Apply to create a LAPD channel. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-77 Field Descriptions for the VISM-PR Create LAPD Channel Parameters Window (continued) Field Name Description LAPD Side (User or N/W) Specifies whether the LAPD stack is on the user or network side. This object can be set when the row is created, but cannot be modified for an existing row. LAPD Trunk Type Indicates if the line is configured for trunking or PRI-BH. 6.9.4.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-93 Step 5 Complete the fields. Note Step 6 Configuration Center—VISM-PR Create Endpoints Config Window Table 6-78 describes fields in the VISM-PR Create Endpoints Config window. Click Apply to add the DS0 endpoint to the line. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Cisco Media Gateway Manager 5.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-78 Field Descriptions for the VISM-PR Create Endpoints Config Window Field Name Description Endpoint Number Identifies endpoint as it is known by the NE. Index to this table. The range is from 1-248. DS0 Number Bitmap of DS0s used by the endpoint. Bit positions set to 1 represent DS0s used by the endpoint. The position corresponds to the DS0 number.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-94 Step 5 Complete or modify the fields. Note Step 6 Configuration Center—VISM-PR DSX0 Parameters Window, DSX0 Parameters Category Table 6-79 describes fields in the VISM-PR DSX0 Parameters window, DSX0 Parameters category. Click Apply to configure the DSX0 parameters. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-79 Field Descriptions for the VISM-PR DSX0 Parameters Window, DSX0 Parameters Category (continued) Field Name Description Received Code Contains the code being received in the ABCD bits. Bundle Mapped Indicates endpoint number as specified by mgEndpointNumber of endpoint table. If it is not associated with any endpoint, then it is set to -1. ds0IfType Indicates the interface type associated with the DS0.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-79 Field Descriptions for the VISM-PR DSX0 Parameters Window, DSX0 Parameters Category (continued) Field Name Description CAS Outgoing MGCP Controls (in conjunction with the card level persistentXgcpEventsTable) how Package persistent CAS events (like answer, disconnect, etc.) related to an outgoing call observed on this DS0 are notified to the MGC. Music Threshold Music on hold threshold in dBm.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-95 Step 5 Complete the fields. Note Step 6 Configuration Center—VISM-PR Create CAS Parameters Window Table 6-80 describes fields in the VISM-PR Create CAS Parameters window. Click Apply to add the CAS variant to the card. Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Table 6-80 Field Descriptions for the VISM-PR Create CAS Parameters Window (continued) Field Name Description Config Status Configuration status of the CAS variant. Variant Source Specifies where the file defining this CAS variant resides. 6.9.4.6.2 Configuring the CAS Variant and Timing Parameters Step 1 From the Domain Explorer window, choose Configuration > MGX 8880/8850 MG > Configuration Center.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Note For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9. Table 6-81 Field Descriptions for the VISM-PR CAS Backhaul Management Tab Field Name Description Variant Name String identifier for the CAS variant, used as an index to the table. File Name Name of the fiel that contains the signal definition and the Finite State Machine definition for the CAS variant.
Chapter 6 Configuring Hardware How Do I Configure VISM-PR Cards? Figure 6-97 Step 5 Configuration Center—VISM-PR Media Gateway Tab, Gateway State Category Set the Admin State Control to the desired state. Note Table 6-82 describes fields in the VISM-PR Media Gateway tab, Gateway State category. For a description of all buttons within this tab, see section 6.2.3 Navigating Within Tables, page 6-9.
C H A P T E R 7 Provisioning Connections This chapter details the tasks required to create new connections, and display, modify, and delete existing connections, and includes the following information: • 7.1 What Is Connection Provisioning? • 7.2 What Types of Connection Are Available? • 7.3 Where Do I Find Information About Connections? • 7.4 How Do I Create, Modify and Delete Voice Connections? • 7.5 How Do I Configure Connection Templates? • 7.6 How Can I Test the Connections? 7.
Chapter 7 Provisioning Connections Where Do I Find Information About Connections? Table 7-1 Supported Connection and Card Types (continued) Connection Type Card RPM RPM-PR RPM-XF VISM VISM-PR-8T1E1 VXSM 48T1E1 7.2.1 What Are the Supported Connection Service Types? Connections can be made between: • VISM- RPM • VISM- ATM When adding a new connection from the Configuration Center application, the service type and protocol is SPVC.
Chapter 7 Provisioning Connections Where Do I Find Information About Connections? Table 7-2 Configuration Center—New Connection Tabs Access Tab Task Advanced Mode Configures the following tasks for connections in Advanced Mode: Quick Mode Creates and modifies connections. • Saves connection templates. • Changes and applies all the parameters listed in the Connection Category pane. • Displays and modifies local end parameters, remote end parameters, and connection parameters.
Chapter 7 Provisioning Connections Where Do I Find Information About Connections? 7.3.2 Displaying All Existing Connections To display all existing connections: Step 1 In the Configuration Center, click the Connections tab to display the Connections Hierarchy pane. Select the NE, and double-click, or drag and drop the NE into the right-hand pane to display the New Connection details.
Chapter 7 Provisioning Connections Where Do I Find Information About Connections? 7.3.4 Editing the Filter Settings In the Configuration Center, the filtering scheme defines the types of connections displayed in the Connection Browser window. By default, all connections for the selected device are displayed. To edit the filter settings: Step 1 In the Configuration Center, click the Connections tab to display the Connections Hierarchy pane.
Chapter 7 Provisioning Connections How Do I Create, Modify and Delete Voice Connections? Step 7 Click OK to apply the selected filter settings. Figure 7-2 Filter Settings Window 7.4 How Do I Create, Modify and Delete Voice Connections? These tasks describe how to create and manage voice connections for VXSM and VISM-PR cards: • 7.4.1 Creating a VISM-RPM Connection in Connection Mode • 7.4.2 Modifying a Connection in Connection Mode • 7.4.3 Deleting Connections • 7.4.
Chapter 7 Provisioning Connections How Do I Create, Modify and Delete Voice Connections? 7.4.1.1 Creating a VISM-RPM Connection in Advanced Mode To create a VISM-RPM connection in Advanced Mode for VXSM and VISM-PR cards: Step 1 In the Configuration Center, click the Connections tab to display the Connections Hierarchy pane. Select the NE, and double-click, or drag and drop the NE into the right-hand pane to display the New Connection details. Step 2 Click the Advanced Mode tab.
Chapter 7 Provisioning Connections How Do I Create, Modify and Delete Voice Connections? Step 13 Optional: Enter the text in the Connection Descriptor field. For example, for a VISM to RPM connection, enter: vism-rpm-dallas-washington Step 14 Click Create to create a new VISM-RPM connection for the node in Advanced Mode. 7.4.1.2 Creating a VISM-RPM Connection in Quick Mode Note You must have a predefined template set up to create connections in Quick Mode. See 7.5.1 Creating Connection Templates.
Chapter 7 Provisioning Connections How Do I Create, Modify and Delete Voice Connections? 7.4.2 Modifying a Connection in Connection Mode You have two options to modify a connection for VXSM and VISM-PR cards: • 7.4.2.1 Modifying a Connection in Advanced Mode • 7.4.2.2 Modifying a Connection in Quick Mode 7.4.2.1 Modifying a Connection in Advanced Mode To modify a connection in Advanced Mode: Step 1 In the Configuration Center, click the Connections tab to display the Connections Hierarchy pane.
Chapter 7 Provisioning Connections How Do I Create, Modify and Delete Voice Connections? Step 8 Click the Quick Mode tab to display all the values for each parameter for the selected VISM-RPM connection type. Step 9 Choose the template from the Select Template drop-down arrow. Step 10 Click Get Template List to retrieve the templates for local and remote endpoints from the Connection Template List window. Step 11 Click Modify to modify the parameters. 7.4.
Chapter 7 Provisioning Connections How Do I Create, Modify and Delete Voice Connections? Note The Local End ID field must be completed in order to retrieve connection information. Step 3 Click the Connection List tab to display the Connection List details. Step 4 Enter the number of connections you want to retrieve in the Connection Count to be retrieved field. To retrieve all the connections, enter *. By default, * is displayed. Step 5 Click Get.
Chapter 7 Provisioning Connections How Do I Configure Connection Templates? Figure 7-3 Unused Descriptor List Dialog 7.5 How Do I Configure Connection Templates? These tasks are used to configure connection templates: • 7.5.1 Creating Connection Templates • 7.5.2 Displaying Connection Templates • 7.5.3 Modifying Connection Templates • 7.5.4 Deleting Connection Templates You can configure templates for new or modified connection parameters.
Chapter 7 Provisioning Connections How Do I Configure Connection Templates? Note Step 8 VISM and VXSM endpoints are shown as VISM endpoints. See Table 7-1 details the types of connections. Enter values in the following fields for the connection parameters: • Local End Parameters • Remote End Parameters • Connection Parameters Note Tooltips provide descriptions of the fields within the Template Configuration window.
Chapter 7 Provisioning Connections How Do I Configure Connection Templates? 7.5.2 Displaying Connection Templates To display connection templates: Step 1 In the Configuration Center, click the Connections tab to display the Connections Hierarchy pane. Select the NE, and double-click, or drag and drop the NE into the right-hand pane to display the New Connection details.
Chapter 7 Provisioning Connections How Can I Test the Connections? Step 7 Rename the current connection template in the Save As field. Or save the template under the same name. Step 8 Click OK to save the connection template with the changed configuration settings. 7.5.4 Deleting Connection Templates To delete templates: Step 1 In the Configuration Center, click the Connections tab to display the Connections Hierarchy pane.
Chapter 7 Provisioning Connections How Can I Test the Connections? Step 3 Click More Filters to display the Filter Settings window. Step 4 Choose the filter settings from the Filter Settings window. For example, check both the Status check box and the OK check box if you want to retrieve only active connections. Step 5 Click OK to apply the filter settings. Step 6 Enter the number of connections that you want to retrieve in the Connection Count to be retrieved field.
Chapter 7 Provisioning Connections How Can I Test the Connections? Step 9 Click the Down Connection radio button. Step 10 Click Start Operation to up the connection. If successful, the Down Connection window appears. 7.6.3 Loopback a Connection You can test a connection by creating a loopback on the connection. All types of connections in Cisco MGM support loopback. An SPVC connection is used as an example. Note Before you can down a connection, ensure that the connection is up first.
Chapter 7 Provisioning Connections How Can I Test the Connections? Cisco Media Gateway Manager 5.
C H A P T E R 8 Managing Security This chapter describes Cisco MGM security and how to manage users. This includes an overview of security domains and a description of the user security and NE security features available in Cisco MGM. This chapter contains the following sections: • 8.1 What Is Security Management? • 8.2 How Do I Customize the Login Advisory Message? • 8.3 How Do I Manage User Security? • 8.4 How Do I Manage the Audit Log? 8.
Chapter 8 Managing Security How Do I Customize the Login Advisory Message? 8.2 How Do I Customize the Login Advisory Message? After logging into the Cisco MGM client, a login advisory message is shown. By default, the advisory message reads: NOTICE: This is a private computer system. Unauthorized access or use may lead to prosecution. You can customize the default advisory message as follows: Step 1 Log into the Cisco MGM server as the root user.
Chapter 8 Managing Security How Do I Manage User Security? Table 8-1 Configuration Center Access Privileges Access Privilege Operation Read Enables the following read operations: Read/Write • Reads the element attributes. • Reads the templates and loads the template parameters into the configuration internal frame. Enables the following create operations: • Changes the attribute values in a create internal frame. • Commits changes on the switch.
Chapter 8 Managing Security How Do I Manage User Security? To perform security-controlled operations within Chassis View and Statistics Reporting Tool applications, Read is the only access privilege allowed. The Read access privilege enables all operations that are supported by the application. 8.3.
Chapter 8 Managing Security How Do I Manage User Security? Table 8-3 Field Descriptions for the Cisco MGM Audit Trail Viewer (continued) Name Description Host Name Specifies the host workstation name where the audit trail record is generated. If the Host Name field is not checked, all host names are displayed. This field corresponds to the Terminal column in the table. The exact hostname must be specified. Note User Id Specifies the user ID used to log into the Cisco MGM desktop.
Chapter 8 Managing Security How Do I Manage User Security? The following sections describe how to view, add, modify, delete, and duplicate a user profile: • 8.3.3.1 Viewing User Profiles • 8.3.3.2 Adding a Custom User Profile • 8.3.3.3 Modifying a User Profile • 8.3.3.4 Deleting a User Profile • 8.3.3.5 Duplicating a User Profile 8.3.3.1 Viewing User Profiles The Cisco MGM User Profiles table displays basic information about Cisco MGM user profiles. Use the menu options to manage user profiles.
Chapter 8 Managing Security How Do I Manage User Security? 8.3.3.2 Adding a Custom User Profile Cisco MGM allows SuperUsers and SysAdmins to generate custom user profiles with certain privileges. Custom user profiles are grouped into categories and each category has a set of operations (see Table 8-6). After the user profiles are generated, they can be assigned to new Cisco MGM users.
Chapter 8 Managing Security How Do I Manage User Security? Table 8-5 Field Descriptions for the Create New User Profile Wizard Field Description User Profile Name Enter the name of the new user profile. The profile name must contain between six and twenty alphanumeric characters (A-Z, a-z, 0-9). Alphabetic characters are case-sensitive. The profile name must be unique in Cisco MGM and cannot contain a space or any special characters.
Chapter 8 Managing Security How Do I Manage User Security? Table 8-6 Cisco MGM Custom User Profiles Category Operations Description Privileges Administration Audit/Error Log Launch the Audit Log and Error Log. Read Only or No Access Control Panel Launch the Control Panel and related tables. Read/Write or No Access Logged In MGM Users Launch the Logged In MGM Users Table.
Chapter 8 Managing Security How Do I Manage User Security? Table 8-6 Cisco MGM Custom User Profiles (continued) Category NE CM Operations 1 Description Privileges Audit Logging in Chassis View Activates or deactivates the Audit Trail in Chassis Read Only, View. Read/Write, or No Access NE FM2 NE Management NE PM Audit Logging in Configuration Activates or deactivates the Audit Trail in Center Configuration Center.
Chapter 8 Managing Security How Do I Manage User Security? 8.3.3.3 Modifying a User Profile Use the Modify User Profile wizard to modify Cisco MGM user profiles. Table 8-5 describes the fields in the wizard. Note Users created with a certain profile cannot be changed to another profile. To change profiles, the user must be deleted, then recreated with the new profile. Modifying a profile will log out all users who are logged in with that profile.
Chapter 8 Managing Security How Do I Manage User Security? 8.3.3.4 Deleting a User Profile Step 1 In the Domain Explorer window, choose Administration > Cisco MGM Users. Step 2 In the Cisco MGM Users table, choose Administration > Cisco MGM User Profiles (or click the Launch User Profiles Table tool). Step 3 In the Cisco MGM User Profiles table, select the profile you want to delete; then, choose Edit > Delete (or click the Delete User Profile tool).
Chapter 8 Managing Security How Do I Manage User Security? 8.3.4 Performing User Administration This section describes how to perform user administration, including: • 8.3.4.1 Managing the Cisco MGM Default User Profiles • 8.3.4.2 Viewing the Cisco MGM Users Table • 8.3.4.3 Creating a Cisco MGM User • 8.3.4.4 Modifying a Cisco MGM User’s Properties • 8.3.4.5 Deleting a Cisco MGM User • 8.3.4.6 Viewing Logged In Cisco MGM Users • 8.3.4.7 Ending an Active Cisco MGM User Session • 8.3.4.
Chapter 8 Managing Security How Do I Manage User Security? Table 8-8 Cisco MGM Default User Profiles Functional Area Operation SysAdmin NetworkAdmin Provisioner Operator Domain Explorer File > New Group Deny Allow Deny Deny File > Add Network Element(s) Deny Allow Deny Deny File > Dashboard Allow Allow Allow Allow File > Network Map Deny Allow Allow Allow File > Domain NE table Deny Allow Allow Allow File > Notify Users Allow Allow Allow Allow File > Refresh Data All
Chapter 8 Managing Security How Do I Manage User Security? Table 8-8 Cisco MGM Default User Profiles (continued) Functional Area Operation SysAdmin NetworkAdmin Provisioner Operator Domain Explorer (continued) Fault > Event Export Manager Allow Allow Allow Allow Fault > Ping NE (not applicable) Deny Deny Deny Deny Fault > Test NE Connectivity (not applicable) Deny Deny Deny Deny Fault > Stop Continuous Beep Deny Allow Allow Allow Fault > MGX 8880/8850 MG > Diagnostic Center Den
Chapter 8 Managing Security How Do I Manage User Security? Table 8-8 Cisco MGM Default User Profiles (continued) Functional Area Operation SysAdmin NetworkAdmin Provisioner Operator Network Map File > Open Deny Allow Allow Allow File > Parent Deny Allow Allow Allow File > Save Deny Allow Allow Allow File > Save As Default Deny Allow Deny Deny File > Revert To Default Deny Allow Allow Allow File > Notify Users Deny Allow Allow Allow File > Refresh Data Deny Allow Al
Chapter 8 Managing Security How Do I Manage User Security? Table 8-8 Cisco MGM Default User Profiles (continued) Functional Area Operation SysAdmin NetworkAdmin Provisioner Operator Cisco MGM Users Edit > Create Allow — — — Edit > Modify Allow — — — Edit > Delete Allow — — — Edit > Unlock Allow Deny Deny Deny Administration > Cisco MGM User Profiles Allow Deny Deny Deny Administration > Logged In Cisco MGM Allow Users Deny Deny Deny Edit > Create Allow Deny Deny Den
Chapter 8 Managing Security How Do I Manage User Security? Table 8-9 Field Descriptions for the MGM Users Table (continued) Field Description Description Description of the user. Password Change Current state (Enabled or Disabled) of the password change option. Multiple Login Whether this user is allowed to perform multiple logins simultaneously. 8.3.4.3 Creating a Cisco MGM User Use the Create New MGM User wizard to add new Cisco MGM users to the domain.
Chapter 8 Managing Security How Do I Manage User Security? Step 6 c. To remove groups or NEs from the Assigned Objects list, select the group or NE from the Assigned Objects list and click Remove. d. Click Next (or Finish). Click Finish. The new user is listed in the MGM Users table. Table 8-10 Field Descriptions for the Create New MGM User Wizard Screen Field User Properties Username Description Name that the user will use to access the system.
Chapter 8 Managing Security How Do I Manage User Security? Table 8-10 Field Descriptions for the Create New MGM User Wizard (continued) Screen Field User Properties Domain Name (continued) Description Domain name. When the user logs into the system, he or she sees all of the devices contained within this domain. Login State Permit (enable) or prevent (disable) the user from logging into the system. Password Change Permit (enable) or prevent (disable) the user from changing his or her password.
Chapter 8 Managing Security How Do I Manage User Security? • Enable check box • Period • User login sessions Step 5 (Optional) For Provisioner, Operator, and custom user profiles, modify the list of assigned objects by adding groups or NEs to the Assigned Objects list or removing groups or NEs from the list. Click Next. Step 6 Click Finish. The user whose properties were modified is listed in the MGM Users table.
Chapter 8 Managing Security How Do I Manage User Security? Table 8-11 Field Descriptions for the Modify MGM User Properties Wizard (continued) Screen Field Description Cisco Media Gateway Manager User Properties (continued) Confirm Password Retype the password to confirm it. User Privilege (Read-only) User’s privilege level. Note The user privilege level cannot be modified without deleting the user. Domain Name Domain name.
Chapter 8 Managing Security How Do I Manage User Security? 8.3.4.5 Deleting a Cisco MGM User Step 1 In the Domain Explorer window, choose Administration > Cisco MGM Users. Step 2 In the Cisco MGM Users table, select the user to be deleted. Note A user cannot be deleted from the database until that user logs out. However, an active user session can be ended. See 8.3.4.7 Ending an Active Cisco MGM User Session, page 8-23. Step 3 Choose Edit > Delete (or click the Delete User tool).
Chapter 8 Managing Security How Do I Manage User Security? Step 4 Click Yes at the following prompt: This operation will log out the selected Cisco MGM user. It will take approximately a minute and this Cisco MGM client will be unusable until then. Do you wish to continue? Wait while the Cisco MGM server logs out the selected Cisco MGM client. The Cisco MGM GUI is frozen for approximately 1 minute until the request is complete. 8.3.4.
Chapter 8 Managing Security How Do I Manage User Security? 8.3.4.10 Changing Your User Password Cisco MGM users can use the Change Password dialog box to change their Cisco MGM passwords at any time. The password change applies to the Cisco MGM user who is currently logged in. There is an enforced password change request when the default user logs in for the first time. If the user does not change the password, the Cisco MGM session is canceled.
Chapter 8 Managing Security How Do I Manage User Security? Note Do not change the Cisco MGM passwords at the same time in the Change Password dialog box. It is possible to set up the user account such that the change password function is disabled. See the description of the Password Change field in 8.3.4.3 Creating a Cisco MGM User, page 8-18. 8.3.4.11 Setting User Preferences Use the User Preferences dialog box to configure the Cisco MGM user interface.
Chapter 8 Managing Security How Do I Manage User Security? Table 8-15 Field Descriptions for the User Preferences Dialog Box (continued) Tab Field Description Miscellaneous Time Zone for Date/Time Display Change the time zone selection. You can select one of the following: Display Log/15-min PM Data • Local—Displays time information adjusted for the time zone that is configured on the PC or workstation where the Cisco MGM client is running.
Chapter 8 Managing Security How Do I Manage User Security? 8.3.4.13 Configuring Cisco MGM Security Parameters Use the Security Properties pane to configure Cisco MGM security parameters and password complexity rules. You can also specify usernames and passwords. Note Passwords that are already in the system are not affected by modification(s) to the password complexity rules.
Chapter 8 Managing Security How Do I Manage User Security? Table 8-16 Field Descriptions for the Security Properties Pane Tab Field Description Cisco MGM Security Password Aging Number of days before the password expires. The user is prompted to change the password after the specified number of days. The range is 0 to 999 days; the default is 30 days. A value of 0 disables this feature. Max Retries Maximum number of login attempts a user is allowed before being denied access.
Chapter 8 Managing Security How Do I Manage User Security? 8.3.4.14 Sending Messages to Other Users Use the Notify Users dialog box to type and send a message to all Cisco MGM users, or to all Cisco MGM users with the same user privileges. For example, you might want to use the Notify Users dialog box to alert all Cisco MGM users before shutting down the Cisco MGM server. Table 8-17 describes the fields in the dialog box. Step 1 In the Domain Explorer window, choose File > Notify Users.
Chapter 8 Managing Security How Do I Manage the Audit Log? 8.4 How Do I Manage the Audit Log? The Audit Log table contains information about significant events (user-initiated changes and activities) that occurred on the Cisco MGM server during a specified time period. By default, the Audit Log displays information about significant events that occurred during the last four hours. You can change the default time period in the User Preferences dialog box.
Chapter 8 Managing Security How Do I Manage the Audit Log? 8.4.1 Viewing the Audit Log To view the Audit Log, choose Administration > Audit Log in the Domain Explorer window. Table 8-19 describes the fields in the Audit Log. Table 8-19 Field Descriptions for the Audit Log Field Description Source ID Source of the event. Events performed by the Cisco MGM server show Cisco MGM as the source ID. Username Name of the user performing the logged event.
C H A P T E R 9 Managing Faults This chapter describes the process of fault management, and details the options available in Cisco MGM to locate, diagnose and correct network problems. This chapter includes the following information: • 9.1 What Is Fault Management? • 9.2 Where Can I Get Information on Affected Services and Customers? • 9.3 What Fault Information Can I See? • 9.4 Is the Service Working? • 9.5 Where Is the Fault? • 9.
Chapter 9 Managing Faults What Is Fault Management? Service assurance is the overall process of ensuring that the purchased level of service is delivered. The Element Management System (EMS) plays a key role in maintaining the health of both network elements and transmission facilities. This is done in conjunction with other systems, typically at the network management layer and service management layer.
Chapter 9 Managing Faults Where Can I Get Information on Affected Services and Customers? 9.1.2.1 Proactive Maintenance Automated detection tests and surveillance software enable rapid initiation of the repair process, sometimes even before customers have noticed a problem. This is called proactive maintenance and promotes customer satisfaction.
Chapter 9 Managing Faults Where Can I Get Information on Affected Services and Customers? Then you need to identify the alarms: • 9.3.1 How Are Alarms Displayed? When a module is under maintenance, you can suppress the alarms so that they are not displayed on the Cisco MGX Alarm or History tab or on any other client: • 9.3.2 Suppressing Alarms 9.2.1 Dashboard The Dashboard shows useful alarm and NE information in one easily accessible location. See Figure 9-1.
Chapter 9 Managing Faults Where Can I Get Information on Affected Services and Customers? Note If you click an alarm count box in the Dashboard, the Alarm Browser appears (see Figure 9-3), prefiltered for the selected alarm severity. If there is a change in the alarm count, and the pushpin is up, the Dashboard is moved to the front of the other windows. 9.2.2 Tooltips A tooltip appears with the actual alarm counters when the cursor is positioned over a managed object (domain, group, NE, or board).
Chapter 9 Managing Faults Where Can I Get Information on Affected Services and Customers? Figure 9-2 Domain Explorer SuperUsers or Network Administrators use the Domain Explorer to create groups of NEs and to organize the domain in a hierarchy. By default, the Domain Explorer contains the following groups that are visible to SuperUsers and Network Administrators only: • Discovered NEs—Contains NEs that have been automatically discovered by the server.
Chapter 9 Managing Faults Where Can I Get Information on Affected Services and Customers? Note Clicking Refresh Data in the Domain Explorer window refreshes all data for the entire client and closes all open windows (except the Domain Explorer window). Depending on the number of NEs in the network, there might be some delay while the data refreshes. The status bar shows the status after the Domain Explorer refreshes. It will show “Refresh Data Complete.
Chapter 9 Managing Faults Where Can I Get Information on Affected Services and Customers? Table 9-1 Field Descriptions for the Alarm Browser Window Column Name Description Alarm ID Indicates the unique number that the system uses to identify a particular alarm. Perceived Severity Displays the perceived severity of the selected alarm (critical, major, minor, or warning).
Chapter 9 Managing Faults Where Can I Get Information on Affected Services and Customers? 9.2.5 Network Map The Network Map window displays a geographical layout of the network. (See Figure 9-4.) It consists of three areas: • The right side displays a map with the individual groups and NEs icons. • The upper left side displays the position of the map on the right side with respect to a larger world map. • The lower left side displays the NE, or group properties, including the number of alarms and ID.
Chapter 9 Managing Faults Where Can I Get Information on Affected Services and Customers? 9.2.6 Diagnostic Center The Diagnostic Center provides a hierarchical representation of network elements, which include networks, nodes, cards, lines and ports displayed in tree format in the Hierarchy pane of the Diagnostic Center’s main window. Associated information about a selected network element is displayed in table format in the right panel of the Diagnostic Center window (See Figure 9-5).
Chapter 9 Managing Faults What Fault Information Can I See? Figure 9-5 Diagnostic Center 9.3 What Fault Information Can I See? An alarm is represented by a notification from a managed NE that a certain condition has just occurred. These alarms usually represent error conditions on NEs. Each alarm is associated with the NE for which it provides notification, and an NE can have a number of alarms related to itself at any time.
Chapter 9 Managing Faults What Fault Information Can I See? 9.3.1 How Are Alarms Displayed? Each node displays an icon, which uses an industry-standard color scheme that indicates the current alarm status. The multicolor displays are updated in real-time in response to events occurring in the network. Icons representing network nodes change color dynamically to reflect the status of the node, which allows rapid recognition of network faults as they occur.
Chapter 9 Managing Faults Is the Service Working? 9.3.2 Suppressing Alarms Suppressing alarms prevents alarms from appearing on the Cisco MGX Alarm or History tab or on any other clients. Alarms are suppressed when the NE is under maintenance. See 5.3.1 Changing the Operational State of an NE. 9.4 Is the Service Working? Network devices will report symptoms of problems by generating events.
Chapter 9 Managing Faults Is the Service Working? These tasks are used to diagnose network elements with the Diagnostic Center: • 9.4.4 Displaying the Status of all Nodes in the Network • 9.4.5 Displaying the Status of a Node • 9.4.6 Displaying the Status of a Card • 9.4.7 Displaying the Status for Lines or Ports • 9.4.8 Displaying the Status for Paths in a Loopback for the VXSM-OC3 Card • 9.4.
Chapter 9 Managing Faults Is the Service Working? 9.4.2 Viewing Alarms The Alarm Browser has a specific selection context, which means that it displays alarm information that corresponds to the view where it was launched. If you launch the Alarm Browser from the management domain node, the browser shows all NE alarms, and all EMS alarms (if you have permission to see EMS alarms). If you launch the Alarm Browser from a group, or NE node, the browser shows only NE alarms for that group, or NE node.
Chapter 9 Managing Faults Is the Service Working? Table 9-4 Alarm Configuration—Threshold EMS Alarms Tab Field Description Poll Frequency Displays the polling interval, in minutes, at which the Cisco MGM server checks parameters. Parameter Name This column displays the name of the parameter as follows: • CPU Usage (%): Percentage of CPU time utilized for executing user, system, and I/O tasks.
Chapter 9 Managing Faults Is the Service Working? Note Step 2 If an alarm is outstanding when you disable it, the system clears the alarm. In the Non-Threshold EMS Alarms tab, you can select the severity level that will be assigned to the non-threshold alarm parameter. See Table 9-5 for details.
Chapter 9 Managing Faults Is the Service Working? Table 9-5 Alarm Configuration—Non-Threshold EMS Alarm Tab (continued) Field Parameter Name (continued) Severity Step 3 Description • Sync-up Failed • Stats File Error • Stats File Transfer Error • SNMP Throttle Error • Backoff failed • SNMP timeout • FTP Session timeout • FTP Transfer timeout • Unknown Error • Initialization Error • Configuration Error • Communication Error in ILOG • Communication Error in shared memory • C
Chapter 9 Managing Faults Is the Service Working? Step 2 The status of the following attributes at the network level are displayed: • Node ID • Node Name • Current sync status of all the nodes of the network • All out-of-sync nodes in the network • A total of partially synced and failed synced nodes 9.4.
Chapter 9 Managing Faults Is the Service Working? 9.4.7 Displaying the Status for Lines or Ports To display the status for lines or ports: Step 1 In the Diagnostic Center, click the Elements tab, and double-click or drag the line or port from the Hierarchy pane to the right hand pane to display the diagnostics at the line or port level. See Figure 9-6. Depending upon the card type, you can also configure Bit Error Rate Test (BERT). For more information, see 9.4.17 Configuring Bit Error Rate Test.
Chapter 9 Managing Faults Is the Service Working? Figure 9-6 Diagnostic Center—Line Status 9.4.8 Displaying the Status for Paths in a Loopback for the VXSM-OC3 Card To display the paths for a loopback for the VXSM-OC3 card: Step 1 In the Diagnostic Center, click the Elements tab, and double-click or drag the card from the Hierarchy pane to the right hand pane to display the diagnostics at the path level. Step 2 Click the Paths In Loopback tab.
Chapter 9 Managing Faults Is the Service Working? 9.4.9 Displaying the Status for Lines in a Loopback To display the lines for a loopback: Step 1 In the Diagnostic Center, click the Elements tab, and double-click or drag the card from the Hierarchy pane to the right hand pane to display the line in the loopback. Step 2 Click the Lines In Loopback tab.
Chapter 9 Managing Faults Is the Service Working? Figure 9-7 Diagnostic Center—Paths in Loopback 9.4.11 Displaying the Status for a Bit Error Rate Test for the Voice Cards You can setup BERT options on the looped back connection and use the available test patterns displayed in the BERT Configuration window. See 9.4.
Chapter 9 Managing Faults Is the Service Working? Step 4 Click the Delta Mode radio button or Absolute Mode radio button. See Table 9-6. Step 5 Choose the polling interval time from the Poll Interval (Sec) drop-down arrow. Step 6 Verify the statistics name and statistics value for the real-time counters. Step 7 Check the Poll All check box to initiate polling for the statistics. To select individual counters for polling, check the counter check box.
Chapter 9 Managing Faults Is the Service Working? Step 3 Verify the following parameters for the path: • Line Number • Loopback Type Step 4 Click the Delta Mode radio button or Absolute Mode radio button. See Table 9-6. Step 5 Choose the polling interval time from the Poll Interval (Sec) drop-down arrow. Step 6 Verify the statistics name and statistics value for the real-time counters. Step 7 Check the Poll All check box to initiate polling for the statistics.
Chapter 9 Managing Faults Is the Service Working? Step 6 Verify the statistics name and statistics value for the real-time counters. Step 7 Check the Poll All check box to initiate polling for the statistics. To select individual counters for polling, check the counter check box. Step 8 Click Refresh to update the settings for the Media Gateway Links for VXSM. 9.4.13.
Chapter 9 Managing Faults Is the Service Working? Figure 9-9 Diagnostic Center—Reliable User Datagram Protocol for Voice Card 9.4.13.3 Displaying the Status for Xternal Gateway Control Protocol for the Voice Cards Note A session of the type of object must be available before it can be polled.
Chapter 9 Managing Faults Is the Service Working? Step 6 Choose the polling interval time from the Poll Interval (Sec) drop-down arrow. Step 7 Verify the statistics name and statistics value for the real-time counters. Step 8 Check the Poll All check box to initiate polling for the statistics. To select individual counters for polling, check the counter check box. Appendix E, “Real-Time Counters” gives details of the real-time counters displayed in the Diagnostic Center.
Chapter 9 Managing Faults Is the Service Working? 9.4.15 Diagnosing Connections The Diagnostic Center is used to diagnose connections.The key functions are the ability to test status, delay and integrity of SPVC connections. This task is used to test SPVC connection: • 9.4.15.1 Polling a Connection for an SPVC You can test the integrity of any existing connection that is nondisruptive to user traffic. The operation is similar to the tstcon command.
Chapter 9 Managing Faults Is the Service Working? Step 15 Verify the statistics name and statistics value for the real-time counters. Step 16 Click Start Test Connection to proceed with testing. Step 17 Click Abort Test Connection to stop the test. 9.4.16 Bit Error Rate Test Bit Error Rate Test (BERT) verifies the integrity of a network element by measuring error statistics that result from sending known bit patterns, analyzing a remote interface, and analyzing the pattern that is returned.
Chapter 9 Managing Faults Is the Service Working? To configure a BERT session: Step 1 In the Diagnostic Center, double-click or drag the line or port that is supported by BERT from the Hierarchy pane to the right hand pane to display the Line and Port Configuration window. Step 2 Click the Bert tab to display the BERT Configuration window. See Figure 9-10. Note Step 3 Not all the BERT configuration parameters are applicable for all card types.
Chapter 9 Managing Faults Is the Service Working? Figure 9-10 Diagnostic Center—BERT Options 9.4.17.1 Stopping Bit Error Rate Test While the BERT session is running, you can stop the session from the BERT Configuration window that is applicable to your selected line or port. From the BERT Configuration window, click Stop Bert to stop the session. 9.4.17.2 Modifying Bit Error Rate Test After you stop a BERT session, you can modify the session.
Chapter 9 Managing Faults Where Is the Fault? 9.4.18 Displaying Bit Error Rate Test After initiating a BERT session, you can view the status of all initiated BERT sessions at once. To display BERT status: Step 1 In the Diagnostic Center, double-click or drag the line or port that is supported by BERT from the Hierarchy pane to the right hand pane to display the Line and Port Configuration window. Step 2 Click the Monitored BERTs tab to display the Monitored BERTs window. See Figure 9-10.
Chapter 9 Managing Faults Where Is the Fault? 9.5.1 Sources of Information Fault management receives and processes information from the following sources: • Autonomous reports of failures from NEs • Trouble reports from customers and peer systems • Results of diagnostics, exercises and audits from NEs • Impairment indications from performance management • Network configuration data from configuration management.
Chapter 9 Managing Faults Where Is the Fault? Note No alarms or events will be generated in the Alarm Browser if Oracle shuts down. 9.5.3 Using Visual and Audible Alarm Notifications To use visual and audible alarm notifications: Step 1 In the Domain Explorer window, choose Edit > User Preferences. Step 2 The User Preferences dialog box appears.
Chapter 9 Managing Faults Where Is the Fault? Table 9-8 Event Notification Dialog Box Descriptions (continued) Field Description Description Displays a brief description of the alarm or event. Service Affecting Indicates whether the alarm or event affects service. 9.5.4 Sources of EMS Raised Alarms In addition to reporting NE-generated alarms, the EMS monitors and reports alarms on the EMS itself; for example, loss of connectivity to NE, and so forth.
Chapter 9 Managing Faults Where Is the Fault? Table 9-10 Non-NE-Specific Alarms Non-NE-Specific Alarms Description Maximum number of login attempts By default, users have a maximum of five login attempts. The user account is locked exceeded after the fifth unsuccessful login attempt and an EMS alarm is generated in the Alarm Browser. The alarm is cleared once the user account is unlocked or the account is deleted.
Chapter 9 Managing Faults How Can I Use Advanced Debugging to Find the Cause of the Fault? 9.6 How Can I Use Advanced Debugging to Find the Cause of the Fault? Advanced debugging captures additional information about defects. The EMS should correlate events and determine the faults that exist in the network. To correlate events means to look for relationships between them. Advanced debugging can be carried out using information from the following sources: • 9.6.
Chapter 9 Managing Faults How Can I Use Advanced Debugging to Find the Cause of the Fault? Table 9-11 Recovery Properties—Process Monitoring Tab Field Description Service Name Displays the process monitoring service name. Critical If checked, the selected service is designated as critical for process monitoring. Service Manager, Oracle Service, and OS Agent cannot be unchecked. 9.6.
Chapter 9 Managing Faults How Can I Use Advanced Debugging to Find the Cause of the Fault? Table 9-12 Field Descriptions for the Error Log Properties Field Description Cisco MGM Server and GateWay/SNMP Allows you to choose the error level to include in the Error Log for services related to the Cisco MGM server and GateWay/SNMP. Critical, major, minor, and informational errors are logged to the database; trace and debug information is logged to a log file.
Chapter 9 Managing Faults How Can I Use Advanced Debugging to Find the Cause of the Fault? Table 9-13 Column Name Description Cisco MGM Time Stamp Displays the date and time when the error occurred on the Cisco MGM server. Module Displays the name of the module where the error occurred. Severity Displays the severity level of the error (see Table 9-15 for a description of the severity levels). Submodule Displays the name of the submodule where the error occurred.
Chapter 9 Managing Faults How Can I Use Advanced Debugging to Find the Cause of the Fault? The Error Log window shows Cisco MGM server error information that is useful for debugging purposes. The Error Log captures abnormal and significant events based on severity. Table 9-15 shows the severity levels.
Chapter 9 Managing Faults How Can I Use Advanced Debugging to Find the Cause of the Fault? Table 9-16 Cisco MGM Processes and Configuration Files Process ConfigFile Parameter Range Default AuditLogger AuditLogger.conf DB_LEVEL [1..5] 5 cmgrd -none- -none- cmsvr cmsvr.conf LOG_LEVEL [1..7] 7 configserver configserver.conf LOG_LEVEL [1..7] 7 cwmftpd cwmftpd.conf LOG_LEVEL [1..7] 7 cwmsmap -none- -none- DCServer DCServer.conf LOG_LEVEL [1..7] 7 dmd dmd.
Chapter 9 Managing Faults How Can I Use Advanced Debugging to Find the Cause of the Fault? Table 9-17 Field Descriptions for the Debug Options Dialog Box Field Subfield Description Modules — Select modules that will display debug messages. Use the Add and Remove buttons to move modules to the Selected list or remove modules from the list. Debug Level Fatal Instructs the Debug Log to display messages with a severity level of at least Fatal.
Chapter 9 Managing Faults What Is the Fault Priority? Table 9-17 Field Descriptions for the Debug Options Dialog Box (continued) Field Subfield Description Display Options File Check the File check box to write the Debug Log to a specific file. You can click Browse to browse for a local client directory for the Debug Log. After you specify the filename, the log is stored at 0.log and 1.log when 0.log is filled to its maximum size.
Chapter 9 Managing Faults What Is the Fault Priority? 9.7.1 Alarm Severity Levels Cisco MGM supports the following alarm severities in the Alarm Browser: • Critical (CR)—Red • Major (MJ)—Orange • Minor (MN)—Yellow • Warning (WR)—Cyan (blue-green) 9.7.2 Filtering the Alarm Log By default, the Alarm Log shows alarm and event information that occurred during the last 4 hours.
Chapter 9 Managing Faults What Is the Fault Priority? Table 9-18 Field Descriptions for the Alarm Log Filter Dialog Box (continued) Tab Description Affected Object Allows you to specify which objects you want to include in the filter. The objects displayed depend on the NE selection in the Domain Explorer Hierarchy pane when the Alarm Log is opened. Use the Add and Remove buttons to filter the display to specific objects.
Chapter 9 Managing Faults Who Is Responsible for Managing the Fault? Step 3 Step 4 Note In the Filter dialog box, click the NE Alarm Time tab. Click one of the following radio buttons: • Past Hour to Past Month—Filters data for a specified time period, ranging from the past hour to the past month. • From Now Onward—Sets the filter time to start immediately and continue until filter parameters are changed. • No Time Specified—Filters data without specifying a time period.
Chapter 9 Managing Faults Who Is Responsible for Managing the Fault? Note Active alarms are not automatically acknowledged. If the alarms are initially set to Manual Alarm Acknowledgement, and then you switch to Automatic Alarm Acknowledgement, all the alarms in the Alarm Browser will be cleared and acknowledged automatically. This might take a while, depending on the number of alarms in the database that have not been acknowledged manually.
Chapter 9 Managing Faults How Did You Manage the Fault? Step 3 Click the Acknowledge Selected Alarm(s) tool again to unacknowledge the selected alarms. Click Yes in the confirmation dialog box. Click Refresh Data to see the changes. The check mark will be removed, indicating that the alarm has been unacknowledged. Note Step 4 Alarm unacknowledgement is disabled by default. Make sure to enable the alarm unacknowledgement feature in the Control Panel before unacknowledging an alarm. See the “9.8.
Chapter 9 Managing Faults How Did You Manage the Fault? By default, the Alarm Log shows alarm and event information that occurred during the last 4 hours. To view the Alarm Log: Step 1 In the Domain Explorer Hierarchy pane, select a domain, group, or NE. Step 2 Choose Fault > Alarm Log. The Alarm Log appears and displays the information detailed in Table 9-19.
Chapter 9 Managing Faults How Did You Manage the Fault? Table 9-19 Field Descriptions for the Alarm Log Window (continued) Field Description Acknowledged Username Login name of the user who acknowledged the alarm or event. Note Acknowledged Time Date and time when the alarm or event was acknowledged. Note Note MGM is the username registered for alarms that are automatically acknowledged. Automatic acknowledgement does not overwrite the username of manually acknowledged alarms.
C H A P T E R 10 Managing Performance Cisco MGM collects performance data which is used to manage and improve the performance of the network. This chapter includes the following information: • 10.1 What Is Performance Management? • 10.2 What Performance Data Is Available? • 10.3 How Is Performance Data Collected? • 10.4 Where Can I See the Performance Data? • 10.5 What Types of Data Reports Are Available? • 10.6 How Is Performance Data Stored? 10.
Chapter 10 Managing Performance What Performance Data Is Available? The performance management process is as follows: 1. Gather network data and statistics 2. Analyze network performance and identify network critical issues 3. Optimize network performance 4. Plan customer capacity 5. Plan network capacity 10.
Chapter 10 Managing Performance What Performance Data Is Available? statistic refers to a counter value for a single entity, for example, a line. If you enable statistics on an NE that has 100 lines, you are dealing with 100 entities that are associated with separate sets of counters. If you requested Cisco MGM to collect statistics for that NE, this will collect all the counter values for all the lines under that NE.
Chapter 10 Managing Performance What Performance Data Is Available? 10.2.1.1 Raw Data Report Raw Data Report selects and displays statistics data from the database: • Lines • Cards • Ports • PhysLine (physical lines) • IMA • Paths • Connections • Protocol • PNNI Statistics By using the Raw Data Report, you can: • Select the statistics for the report and time period.
Chapter 10 Managing Performance How Is Performance Data Collected? 10.3 How Is Performance Data Collected? Performance data collection is the process of collecting performance-related data from network devices and storing them in a database or data file. This information can then be used for locating, diagnosing, and correcting network problems to increase network reliability and effectiveness, and to ensure that fault management can be more than just handling emergencies.
Chapter 10 Managing Performance How Is Performance Data Collected? Figure 10-1 Table 10-2 Self Monitor Table Self Monitor Table Descriptions Column Name Description NE ID Displays the name of the EMS (MGM). Parameter Name Displays the name of the parameter. See the Alarm Configuration property sheet in the Control Panel for a list of monitored parameters. Model Type As NE model types are not applicable, “System” is displayed as the model type.
Chapter 10 Managing Performance How Is Performance Data Collected? Table 10-3 Self Monitor Table Filter Descriptions Tab Description Collection Time (time zone) Allows you to filter data for a specified time period, ranging from the past hour to the past 180 days. Additionally, you can click the User Specified radio button to specify an exact filter starting and ending time by month, day, year, and hour.
Chapter 10 Managing Performance Where Can I See the Performance Data? 10.4 Where Can I See the Performance Data? Cisco MGM gives you the power to collect large amounts of performance data, so it is important that you be able to display only the required data. Data can be displayed in normal mode, where all performance data is collected and displayed in the PM data tables.
Chapter 10 Managing Performance What Types of Data Reports Are Available? Table 10-4 Report Types for Each Network Element Network Element Report Types Network Supports the following report types: Node Card • Raw Data Report for cards, lines, ports, physical lines, protocol, and PNNI, in the network. • Performance Data Report for ports in the network. • Utilization Data Report for ports in the network.
Chapter 10 Managing Performance What Types of Data Reports Are Available? 10.5.1 Viewing Raw Data Reports The Raw Data Report Parameters pane in the Statistics Report displays the history statistics data for the selected statistics and the time period parameters. You can select the statistics from the different cards, for example, service lines, and physical lines, which are applicable for a line type. These tasks are used to configure the Raw Data Reports: • 10.5.1.
Chapter 10 Managing Performance What Types of Data Reports Are Available? Note If you want to stop generating the Raw Data Report, click Stop Report Generation. Figure 10-2 Statistics Report Window—Raw Data Report 10.5.1.2 Exporting the Raw Data Report After generating the Raw Data Report, you can verify that the report is exported. To export the Raw Data Report at the node level, see the “10.5.4 Exporting the Data Report” section on page 10-21. 10.5.1.
Chapter 10 Managing Performance What Types of Data Reports Are Available? Step 4 Click the Connection List tab, enter the number of connections you want to retrieve in the Connection Count to be retrieved field. To retrieve all the connections, enter *. Step 5 Click Get to retrieve the connections. For example, you can retrieve connections for both local and remote endpoints for the node. The Connection Browser window appears with the number of connections matching the filtering criteria.
Chapter 10 Managing Performance What Types of Data Reports Are Available? 10.5.2 Viewing Utilization Data The Utilization Data Report verifies all ports, and connections. Utilization is based on percentage of total bits received in seconds and total bits transmitted in seconds. You specify the parameters listed that crosses the threshold value. These tasks are used to configure Utilization Data Reports: • 10.5.2.1 Calculating the Percent Utilization for Top Utilization Reports • 10.5.2.
Chapter 10 Managing Performance What Types of Data Reports Are Available? 10.5.2.2 Generating a Utilization Data Report Multiple Utilization Data Reports can be generated at the same time. To generate a Utilization Data Report at the node level: Step 1 In the Statistics Report, move the node from the Hierarchy pane to the right hand pane. Step 2 Choose Utilization Data Report from the drop-down arrow. See Figure 10-3. Step 3 Choose Utilization Report for Port from the drop-down arrow.
Chapter 10 Managing Performance What Types of Data Reports Are Available? Figure 10-3 Statistics Report Window—Utilization Report 10.5.2.3 Exporting the Utilization Data Report After generating the Utilization Data Report, you can verify that the report is exported. To export the Utilization Data Report at the node level, see the “10.5.4 Exporting the Data Report” section on page 10-21. 10.5.2.
Chapter 10 Managing Performance What Types of Data Reports Are Available? Step 5 Click Get to retrieve the connections. For example, you can retrieve connections for both local and remote endpoints for the node. The Connection Browser window appears with the number of connections matching the filtering criteria. A list of connections that have either local or remote endpoints are displayed in the connection list.
Chapter 10 Managing Performance What Types of Data Reports Are Available? For more information on the supported objects for each report type, see Table 10-4. These tasks are used to configure Performance Data Reports: • 10.5.3.1 Calculating the Statistics Percentages for the Performance Data Report • 10.5.3.2 Generating the Performance Data Report for a Port • 10.5.3.3 Displaying Performance Data Report for a Port • 10.5.3.4 Generating the Performance Data Report for Connections • 10.5.3.
Chapter 10 Managing Performance What Types of Data Reports Are Available? 10.5.3.2 Generating the Performance Data Report for a Port Multiple Performance Data Reports can be generated at the same time. To generate the Performance Data Report at the port level: Step 1 In the Statistics Report Tool, drag the port from the Hierarchy pane to the right hand pane. Step 2 Choose Performance Data Report from the drop-down arrow. See Figure 10-4.
Chapter 10 Managing Performance What Types of Data Reports Are Available? Figure 10-4 Statistics Report Window—Performance Data Report 10.5.3.3 Displaying Performance Data Report for a Port After you finished generating the Performance Data Report (see 10.5.3.2 Generating the Performance Data Report for a Port), you must ensure that the graphical information is correct. For example, you must verify that the report shows the correct port object identifier according to the entity label specifications.
Chapter 10 Managing Performance What Types of Data Reports Are Available? Step 3 Drag the node to the right hand pane to display the Connection Browser window. Step 4 Click the Connection List tab. Step 5 Enter the number of connections you want to retrieve in the Connection Count to be retrieved field. To retrieve all the connections, enter *. Step 6 Click Get to retrieve the connections. For example, you can retrieve connections for both local and remote endpoints for the node.
Chapter 10 Managing Performance How Is Performance Data Stored? Step 2 Click Close to close the report summary. 10.5.4 Exporting the Data Report After generating the Data Report, you can verify that the report is exported. To export the Data Report at the node level: Step 1 After generating a raw data report, click Export Report to export the report data.
Chapter 10 Managing Performance How Is Performance Data Stored? Figure 10-5 Database Properties—Pruning Tab 10.6.1 Importing and Exporting Data to and from the Oracle Database You can use the Oracle Export utility to write data from an Oracle database to an operating system file in binary format. The file is stored outside the database and read to another Oracle database by using the Import utility.
C H A P T E R 11 Managing Inventory This chapter describes inventory management, and how to use Cisco MGM to provide the required information. This chapter contains the following sections: • 11.1 What is Inventory Management? Cisco MGM provides two levels of inventory reports: • A complete list of all the NEs that belong to a specific group or to the entire domain (see 11.2 Domain NE Tables.) • A detailed list of cards and modules installed on the NEs (see 11.3 Equipment Inventory Tables.) 11.
Chapter 11 Managing Inventory Domain NE Tables Cisco MGM allows you to export inventory reports to a flat text file with a user specified delimiter character. This file can then be easily imported into a spreadsheet application for further analysis. 11.2 Domain NE Tables The Domain NE tables displays an inventory of all the NEs in the Cisco MGM domain or group selected.
Chapter 11 Managing Inventory Domain NE Tables Table 11-1 Field Descriptions for the Domain NE Table Field Description NE ID Displays the name of the selected NE. NE Model Displays the NE model:Cisco MGX 8880/8850 Active IP Address Displays the active IP address of the selected NE. Communication State Displays the connectivity state between Cisco MGM and the selected NE (either Available or Unavailable).
Chapter 11 Managing Inventory Equipment Inventory Tables Table 11-2 Domain NE Table Filter Dialog Box Descriptions Tab Field Description NE ID Available NE ID/Selected NE ID Displays the list of available NE IDs. Click Add and Remove to move NE IDs to and from the Selected NE ID list. Inventory Communication State Allows you to filter NEs according to their communication state (Unavailable or Available).
Chapter 11 Managing Inventory Equipment Inventory Tables Table 11-3 Equipment Inventory Table Descriptions—Cisco MGX8880/8850 Column Description NE ID Displays the name of the selected NE. Physical Location Displays the name of the location where the NE is installed. MODULENAME Displays the name of the module. MODULEDESCRIPTION Displays any information that was previously entered to describe the selected NE. FCSERIALNUM Displays the serial number of the front card.
Chapter 11 Managing Inventory Equipment Inventory Tables Figure 11-2 Equipment Inventory Table Cisco Media Gateway Manager 5.
C H A P T E R 12 Managing CORBA Interfaces This chapter contains the following information: Note • 12.1 What is Cisco MGM GateWay/CORBA? • 12.2 Using a Static CORBA Listener Port on the Cisco MGM Server • 12.3 Configuring the CORBA Timeout Cisco MGM GateWay/CORBA is only mentioned briefly here. For more information about Cisco MGM GateWay/CORBA, including how to enable username and password encryption, set the heartbeat event, and create OSS clients, refer to the Cisco Media Gateway Manager 5.
Chapter 12 Managing CORBA Interfaces What is Cisco MGM GateWay/CORBA? Figure 12-1 Cisco MGM GateWay/CORBA Communications Architecture Service provider's OSS 83273 CORBA GIOP IIOP TCP IP Ethernet 10BASE-T Cisco Media Gateway Manager Cisco MGM GateWay/CORBA is based on the following TMF standards: • TMF513 v2.0 (October 2001): Multi-Technology Network Management Business Agreement • TMF608 v2.0 (October 2001): Multi-Technology Network Management Information Agreement • TMF814 v2.
Chapter 12 Managing CORBA Interfaces What is Cisco MGM GateWay/CORBA? Table 12-1 Field Descriptions for GateWay/CORBA Service—Global Tab (continued) Field Description Heartbeat for Notification Channel Notifies the OSS if a failure in the notification service has occurred. The heartbeat is measured in minutes ranging from 0 to 1440 minutes. A zero value implies that the heartbeat is disabled. Error Level Allows you to select the error level for the Cisco MGM GateWay/CORBA service.
Chapter 12 Managing CORBA Interfaces Using a Static CORBA Listener Port on the Cisco MGM Server 12.1.2 Viewing the Cisco MGM GateWay/CORBA Client Configuration Table The Cisco MGM GateWay/CORBA Client Configuration Table displays information about Operations Support System (OSS) CORBA client properties.
Chapter 12 Managing CORBA Interfaces Configuring the CORBA Timeout Step 2 Set the CORBA_Call_Timeout_Seconds parameter to the desired value. The default timeout is 120 seconds; the recommended range is 120 to 300 seconds. Note Step 3 If the NE is busy or if the Cisco MGM server is processing many requests, you might need to increase the CORBA timeout parameter accordingly. Save and close the ems-client.cfg file. Cisco Media Gateway Manager 5.
Chapter 12 Managing CORBA Interfaces Configuring the CORBA Timeout Cisco Media Gateway Manager 5.
A P P E N D I X A Icons and Menus This appendix describes the icons and menus used in Cisco MGM, and contains the following sections: • A.1 Launching Applications • A.2 Toolbar Options • A.3 Menu Options • A.4 Hierarchy Pane Icons • A.5 Inspector View Icons • A.6 Network Map Icons A.1 Launching Applications Applications in Cisco MGM can be launched from the toolbar and dashboard, as well as from menu options. Table A-1 list the icons.
Appendix A Icons and Menus Toolbar Options Table A-1 Cisco MGM Applications Icons (continued) Application Icon Domain Explorer EMS Alarm Browser Statistics Report A.2 Toolbar Options The various Cisco MGM toolbar tools are described in . Table A-2 Toolbar Tools Description Tool Item Description Acknowledge Alarms Acknowledge the selected alarm(s). Click again to unacknowledge the selected alarm(s). To enable alarm unacknowledgement, go to Control Panel > UI Properties.
Appendix A Icons and Menus Toolbar Options Table A-2 Toolbar Tools Description (continued) Tool Item Description Cancel Job Allows you to cancel a scheduled job. Cancel is enabled only for jobs with a Queued status. Cancel Task Allows you to cancel a task. Clear Selected Alarm(s) Clear selected alarms. A message displays, informing you that only PM failed and PM lost alarms on NEs in your domain will be cleared.
Appendix A Icons and Menus Toolbar Options Table A-2 Toolbar Tools Description (continued) Tool Item Description Enable Drag Enables drag and drop functionality for all nodes within the Network Map window. Enable Offview Enables the display of off-view icons within the Network Map window. Error Log Opens the Error Log window. Expand Expands the management domain or group to display all groups or NEs in that management domain or group. Export Data To File Opens the Export dialog box.
Appendix A Icons and Menus Toolbar Options Table A-2 Toolbar Tools Description (continued) Tool Item Description Hide Cleared Alarms Hides all alarms that have been cleared. Launch User Profiles Table Opens the Cisco MGM User Profiles Table. Log Out User Logs out the selected user from the Cisco MGM application. Logged in Cisco MGM Users Opens the Logged In Cisco MGM Users Table, which lists the Cisco MGM users who are currently logged into the Cisco MGM application.
Appendix A Icons and Menus Toolbar Options Table A-2 Toolbar Tools Description (continued) Tool Item Description Paste Pastes the NE on the clipboard into the selected group. Print Graph Prints the graphical display. Refresh Data Refreshes all data being displayed by Cisco MGM. There are two icons, and both refresh data from either the server or the database. The Refresh Data icon with blue and red arrow (as seen in Circuit Table) flashes when updates are available.
Appendix A Icons and Menus Menu Options Table A-2 Toolbar Tools Description (continued) Tool Item Description Show Parent Network Map See Parent. Unlock User Allows you to unlock a user account. Zoom Area Allows you to pan and zoom the view to a different region. Zoom In Allows you to zoom in on the Network Map. Zoom Out Allows you to zoom out on the Network Map. A.3 Menu Options The various Cisco MGM menu options are described below, in the order they appear on each menu.
Appendix A Icons and Menus Menu Options Table A-3 Domain Explorer—File Menu Tools Description Item Description New Group Opens the New Group dialog box. From here, you can add a new group, give the group a name, specify the group's geographic location, and provide a brief description of the group. Add Network Element(s) Opens the Add New Network Element wizard, which allows you to add a new NE or add several new NEs at once.
Appendix A Icons and Menus Menu Options Table A-4 Network Map—File Menu Tools Description (continued) Item Description Save as Default Saves your customizations (map background, node icons, and x and y coordinates) as the default map view. Revert to Default Reverts your map customizations. Notify Users Opens the Notify Users dialog box. Refresh Data Refreshes all data being displayed by Cisco MGM. There are two icons, and both refresh data from either the server or the database.
Appendix A Icons and Menus Menu Options Table A-5 Alarm Browser, Alarm Log, Domain NE Table, Equipment Inventory Table, and Control Panel—File Menu Tools Description (continued) Item Description Refresh Data Refreshes all data being displayed by Cisco MGM. There are two icons, and both refresh data from either the server or the database. The Refresh Data icon with blue and red arrow (as seen in Circuit Table) flashes when updates are available.
Appendix A Icons and Menus Menu Options Table A-6 Domain Explorer Edit Menu Tools Descriptions (continued) Item Description Delete Deletes the selected instance of the NE or group. If this is the last instance of the NE, the NE is placed in the Deleted NEs group. Only out-of-service NEs can be placed in the Deleted NEs group. To delete the NE from the database, select the NE in the Deleted NEs group and choose Edit > Delete; then, click OK.
Appendix A Icons and Menus Menu Options Table A-7 Network Map Edit Menu Tools Descriptions (continued) Item Description Change Node Icon Opens the Select Node Icon File dialog box, which allows you to select a new icon for the selected node. Zoom In Allows you to zoom in on the Network Map. Zoom Out Allows you to zoom out on the Network Map. Zoom Area Allows you to pan and zoom the view to a different region. User Preferences Opens the User Preferences dialog box.
Appendix A Icons and Menus Menu Options A.3.3 Fault Menu Table A-10 describes the tools within the Fault menu. Table A-10 Fault Menu Tools Description Item Description Alarm Browser Opens the Alarm Browser window. Alarm Log Opens the Alarm Log window. Event Export Manager Opens the Event Export Manager window. MGX8880/8850 MG > Diagnostic Center Launch Diagnostic Center.
Appendix A Icons and Menus Menu Options Table A-13 Configuration Menu Tools Description (continued) Item Description MGX8880/8850 MG > Chassis View Launch Chassis View MGX8880/8850 MG > Configuration Center Launch Configuration Center. A.3.
Appendix A Icons and Menus Menu Options Table A-16 Control Panel Administration Menu Tools Description Item Description Audit Log Opens the Audit Log window. Error Log Opens the Error Log window. Supported NE Table Opens the Supported NE Table window. GW/CORBA Client Configuration Table Opens the Cisco MGM GateWay/CORBA Client Configuration Table window. A.3.7 Window Menu Table A-17 describes the tools within the Window menu.
Appendix A Icons and Menus Hierarchy Pane Icons A.4 Hierarchy Pane Icons The following tables describe the icons shown in the Hierarchy pane: • A.4.1 Object Icons • A.4.2 Communication State Icons • A.4.3 Operational State Icons • A.4.4 Severity Icons • A.4.5 Hierarchy Pane Navigation Icons A.4.1 Object Icons Table A-19 describes the object icons in the Hierarchy pane.
Appendix A Icons and Menus Hierarchy Pane Icons Table A-19 Object Icons (continued) Object Icon RPM Subinterface Sensor Unknown NE Virtual Port A.4.2 Communication State Icons Table A-20 describes the communication state icons within the Domain Explorer Hierarchy pane. Table A-20 Communication State Icons State Icon Available Unavailable Not Applicable A.4.3 Operational State Icons Table A-21 describes the operational state icons within the Domain Explorer Hierarchy pane.
Appendix A Icons and Menus Hierarchy Pane Icons Table A-21 Operational State Icons (continued) State Icon In Service - Synch Configuration In Service - Undiscovered Under Maintenance Out of Service A.4.4 Severity Icons Table A-22 describes the severity icons in the Domain Explorer Hierarchy pane. Table A-22 Severity Icons Severity Color Critical Red Major Orange Minor Yellow Warning Light Blue Cleared Green Unknown Gray Icon A.4.
Appendix A Icons and Menus Inspector View Icons Table A-23 Hierarchy Pane Navigation Icons Item Icon Find Find Next Find Previous Expand One Level Expand Two Levels Expand Three Levels Sort Ascending/Descending A.5 Inspector View Icons In the Configuration Center and Statistics Report, the Inspector View provides a list of detailed information for the selected network element from the hierarchy view. Click the Show static data button to update the information in the Inspector View.
Appendix A Icons and Menus Network Map Icons A.6 Network Map Icons The Network Map allows you to visualize the structure of your network. Table A-25 gives examples of the icons that appear in the Network Map. When you open the Network Map from a selected NE in the Domain Explorer, the selected NEs is pre-selected on the map. The icon has white text displayed on a black background. This allows you to distinguish the previously selected NE from the other NEs in the same map.
Appendix A Icons and Menus Network Map Icons Table A-26 Icon States State Icon Color Overlay Loss of communications Icon color indicates whether the NE is reachable Red and white border Under maintenance Icon color indicates whether the NE is under maintenance Yellow and black border Unacknowledged alarms Icon color indicates whether an unacknowledged alarm is present on the NE Cream border Initializing Icon color indicates that the NE is Blue and white initializing border Synch configurati
Appendix A Icons and Menus Network Map Icons Table A-27 Icon Colors Status Colors Critical Red Major Orange Minor Yellow Warning Light blue Clear Green Out of service Gray Example A.6.3 Operational and Communication State Icons Table A-28 describes the operational and communication state map representation icons in the Network Map pane. Cisco Media Gateway Manager 5.
Appendix A Icons and Menus Network Map Icons Table A-28 Operational and Communication State Map Representation Icons State Icon Icon Color Border Color Loss of Communication (Communication State is Unavailable) Red Red/White In Service Orange None In Service - Initializing Gray Blue/White In Service - Synch Configuration Red Blue/Black Under Maintenance Red Black/Yellow Out of Service Gray None A.6.
Appendix A Icons and Menus Network Map Icons Note Use the File > Save as Default menu option to save your customizations (map background, node icons, and x and y coordinates) as the default map view. The Save as Default option is disabled for the root or Cisco MGM domain node. By default, the customized map background and node icons are saved on your local workstation under /images/mapbkgnds/custom/default and /images/mapicons/custom/default.
A P P E N D I X B Error Messages This appendix describes the error messages and recommends solutions. It contains the following sections: • B.1 Cisco MGM Client Error and Warning Messages, page B-1 • B.2 Cisco MGM Server Error Messages, page B-61 – B.2.1 Critical Server Error Messages, page B-61 – B.2.2 Major Server Error Messages, page B-68 – B.2.3 Minor Server Error Messages, page B-87 – B.2.4 Debug Server Error Messages, page B-104 • B.3 Cisco MGM Server Audit Messages, page B-104 B.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-103: Fatal error: Connection to the EMS server was lost. The application will be shut down. Recommended Action Restart the application after verifying that the Cisco MGM server is operational and available from the client LAN. Error Message EID-104: Cisco MGM internal error: Invalid help URL. Recommended Action Contact your service provider or Cisco technical support.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-111: Your password has expired. You need to set a new password. Do you want to continue? Recommended Action Enter a new password. Error Message EID-112: You are entering a protected Cisco domain. Do you want to continue? Recommended Action Click OK to continue. Error Message EID-113: Invalid password: The password cannot contain the same characters as the user ID, even in a different order.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-117: Cannot launch a browser. MGM uses the default browser to display the online help. If you want to use a specific browser to launch MGM online help, make the default browser for your workstation “javascript:scrollTo(0,3400) Scroll down to Save Issue. Recommended Action Check your $PATH variable and make sure that “netscape” is included in the PATH.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-132: User disabled due to a security violation. Contact administrator to enable user account. Recommended Action Contact the administrator to re-enable the user account. Error Message EID-133: Specify a username. Recommended Action Enter the username. Error Message EID-134: Enter or select an IP address. Recommended Action Enter the IP address. Error Message EID-136: No Undeleted NEs in the Selection Context.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-145: Illegal record count. Enter a positive integer. Recommended Action Enter a positive integer. Error Message EID-146: Event Export Manager - Cannot create or append to filename. Check access rights and disk space. Recommended Action Check access rights and disk space. Error Message EID-147: Event Export Manager - Cannot write to filename. Check access rights and disk space.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-159: Selected NEs for software download are of different model types. Recommended Action Reselect the NEs. All NEs selected for software download must be the same model type. Error Message EID-160: Year entered is before the current year. Enter a year greater than or equal to the current year. Recommended Action Enter a year that is equal to or greater than the current year.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-167: Selected NE list is empty. Select NEs from the Available NEs list. Recommended Action Select at least one NE for the memory backup or software download operation. Note You can run the memory restore operation for only one NE at a time. Error Message EID-168: An error occurred while scheduling the software download operation. Recommended Action The software download operation could not be scheduled.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-178: An error occurred while modifying the global MGM configuration. Changes might not be communicated to other MGM clients. Recommended Action Restart the Cisco MGM client and retry. Error Message EID-180: An error occurred while starting this service. Verify that this service is installed on the MGM server and retry.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-186: The request to open the current configuration file was denied. Recommended Action An incorrect server configuration appears on the Control Panel window. Reopen it and verify that the server parameters are correct. Error Message EID-187: There is a problem opening the current configuration file. Recommended Action An incorrect server configuration appears on the Control Panel window.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-194: A maximum of n can be configured. You must remove an existing host if you want to add another host. Recommended Action Remove an existing Simple Network Management Protocol (SNMP) host; then, add a new host. Error Message EID-196: An error occurred while sending the truncate queue event to the server. Recommended Action Error while sending event to the server. Restart client.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-209: Could not cancel selected job(s). Action failed. Recommended Action The selected task or job is already running or has already been cancelled. Click the Refresh Data tool to see the current status. Error Message EID-210: Could not activate selected task(s). Action failed. Recommended Action Activate (Commit) fails when the active software version is newer than the standby software version.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-218: Some NEs have no associated partitions to download the image file. Proceed anyway? Recommended Action One or more of the selected NEs have no partition selected for downloading the image. Select appropriate Flash partitions for all NEs. If you proceed anyway, those NEs will not be scheduled for image download. Error Message EID-219: Some selected NE Flash partitions do not have enough space for the image.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-229: An EFD with the same name already exists. Specify a unique EFD name and retry. Recommended Action Enter a unique EFD name and retry. Error Message EID-230: An OSS IP address with the same name already exists. Specify a unique IP address and retry. Recommended Action Enter a unique IP address and retry. Error Message EID-231: An error occurred while reading the database. Restart the MGM client and retry.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-238: At least one network element should be allowed. Recommended Action Add at least one NE to the EFD. Error Message EID-239: At least one access element should be allowed. Recommended Action Add at least one access element to the EFD. Error Message EID-241: An error occurred while logging out a MGM user. Recommended Action Retry. Error Message EID-242: The OSS client name cannot be . Enter another name.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-248: TID/SID for MGM is mandatory. Enter a value. Recommended Action Enter a target identifier (TID) or source identifier (SID) value. Error Message EID-249: Threshold values must follow the order Critical > Major > Minor. Enter valid values. Recommended Action Enter threshold values where the critical value is greater than the major value, which is greater than the minor value.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-259: Select a user to modify. Recommended Action Select a user. Error Message EID-260: Select an NE for the user. Recommended Action Select an NE. Error Message EID-261: This user is already defined on some or all of your selected NEs. Recommended Action Select a different user. Error Message EID-262: Select at least one user. Recommended Action Select at least one user.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-269: Database error: Cannot change the user password. Recommended Action A database error occurred during this operation. Verify that the Cisco MGM database is up and running properly. Restart the Cisco MGM client and retry. Error Message EID-273: The change password feature has been disabled by the administrator for this user.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-301: Export data error: Table not instantiated. Recommended Action You cannot export data before the table is fully open. Wait until the table opens fully; then, click the Export tool. Error Message EID-302: Export data: Error in opening file filename to export data. Recommended Action The file could not be opened for writing the data. This could be due to insufficient permission in the selected directory.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-310: Graph is not available at this time. Recommended Action The graph could not be started because the NE could not be contacted. Verify that the NE is available and retry. Error Message EID-311: BER statistics are not available at this time. Recommended Action The bit error rate (BER) window could not be opened because the NE could not be contacted. Verify that the NE is available and retry.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-319: Error while sorting data in the database. Recommended Action Restart the Cisco MGM client and retry. Error Message EID-320: Error while attempting read/write to the database. Recommended Action Restart the Cisco MGM client and retry. Error Message EID-321: Error while sending request for alarm changed. Recommended Action Restart the Cisco MGM client and retry.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-331: Error occurred. Table will be closed. Recommended Action Restart the Cisco MGM client and retry. Error Message EID-332: Exception while creating metadata for object. Recommended Action Restart the Cisco MGM client and retry. Error Message EID-333: Database timeout occurred. Reduce the scope of the query or increase the timeout. Recommended Action Your database query is too broad.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-353: This operation will result in deleting the selected user(s) from the database. Press 'OK' to continue and 'Cancel' to abort the operation. Recommended Action Click OK to delete the selected user(s), or click Cancel. Error Message EID-354: This operation will result in deleting the selected user profile(s) from the database. Press ‘OK’ to continue and ‘Cancel’ to abort operation.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-408: Error occurred while reading the DS1 port configuration from the database. The data shown may be inconsistent with the network element's actual configuration. Recommended Action Wait for a few minutes; then, click the Refresh Data tool to refresh the view. Error Message EID-409: Error occurred while reading the OC-3 configuration from the database.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-422: Error occurred while reading the VC3 configuration from the database. The data shown may be inconsistent with the network element’s actual configuration. Recommended Action Wait for a few minutes; then, click the Refresh Data tool to refresh the view. Error Message EID-423: Error occurred while reading the VC2 configuration from the database.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-453: Protection group must have working card(s). Recommended Action Select a protection group that contains at least one working card. Error Message EID-454: Enter valid values for the protection group name, type, protect module, and working entities. Recommended Action Enter valid values. Error Message EID-455: Enter a valid value for Protection Group Name. Recommended Action Enter a valid protection group name.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-463: 0.0.0.0 is not a valid SNTP server IP address. Enter a valid IP address. Recommended Action Enter a valid IP address. Error Message EID-464: Cannot create Ethernet thresholds on the following ports: port_number(s). Recommended Action Try creating the thresholds again. Error Message EID-465: The change was not saved successfully. Data will be reset to the previous value.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-505: Database error: Error occurred while adding the new group to the database. Recommended Action A database error occurred while adding the new group. Verify that the Cisco MGM database is up and running properly. Restart the Cisco MGM client and retry adding a new group. Error Message EID-506: Group name is too long. Restrict the name to 32 characters.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-520: Database error: Error occurred while adding the new NE to the database. Recommended Action A database error occurred while adding the new NE. Verify that the Cisco MGM database is up and running properly. Restart the Cisco MGM client and retry adding a new NE. Error Message EID-521: Network element description is too long. Restrict the description to 256 characters.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-530: An error occurred while reading data from the database. Recommended Action Exit and restart the Cisco MGM client. Error Message EID-531: A domain with the same name already exists. Specify a unique domain name and retry. Recommended Action Specify a unique domain name. Error Message EID-532: Database error: Cannot modify the domain description. Recommended Action A database error occurred during this operation.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-539: Database error: Cannot modify the network element name. Recommended Action A database error occurred during this operation. Verify that the Cisco MGM database is up and running properly. Restart the Cisco MGM client and retry. Error Message EID-540: Database error: Cannot modify the network element IP address. Recommended Action A database error occurred during this operation.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-549: Database error: Cannot set the NE type in the database. Recommended Action A database error occurred during this operation. Verify that the Cisco MGM database is up and running properly. Restart the Cisco MGM client and retry. Error Message EID-550: Database error: Cannot set the NE PM collection state in the database. Recommended Action A database error occurred during this operation.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-559: User Password is a mandatory field. Enter a unique user password and retry. Recommended Action Enter a unique user password. Error Message EID-560: Enter a username with at least 6 characters. Recommended Action Enter a username that contains at least 6 characters. Error Message EID-561: Username must start with an alphabetic character (A - Z, a - z). Enter a valid username and retry.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-569: No objects are assigned to the user. Assign at least one object to the user. Recommended Action Assign an object to the user. Error Message EID-570: Database error: Cannot create the new user type. Recommended Action This error occurs when a new user profile is being created or if an existing profile is being modified.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-576: Database error: Cannot assign ports to the user. Recommended Action A database error occurred during this operation. Verify that the Cisco MGM database is up and running properly. Restart the Cisco MGM client and retry. Error Message EID-577: Enter a user type name that contains at least 6 characters. Recommended Action Enter a user type name that contains at least 6 characters.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-585: The “to” IP Address is lower than the “from” IP Address. Recommended Action This error occurs during the addition of bulk NEs. Make sure that the To IP Address is greater than the From IP Address. Error Message EID-586: The selected GNE ID is no longer present. Select another GNE ID. Recommended Action This error occurs while adding an NE.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-598: A database error occurred while deleting the selected group from all references of its parent. The group might not be deleted completely. Recommended Action Restart the Cisco MGM client. Check if the deleted group still exists under all references of its parents. If it does, select each reference in the Domain Explorer Hierarchy pane and choose Edit > Delete.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-623: An error occurred in response to a topology change. Refresh the view. Recommended Action Close, then reopen the topology window. Error Message EID-628: MGM initialization failed. Cannot connect to the MGM database. Recommended Action The Cisco MGM client cannot read a required table from the database. Restart the application and start the Debug Log (choose File > Debug Options).
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-638: A MGM administrator has modified the MGM domain. As a result, your request to modify the MGM topology is invalid. Try again. Recommended Action While you were adding an NE or group to an existing group, another administrator deleted the existing group. Consequently, your request to add an NE or group is now invalid. Reselect the node and retry.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-649: A duplicate target is not allowed. Recommended Action Specify a target that has not been used before. Error Message EID-650: Specify a target. Recommended Action Specify a target. Error Message EID-651: Target cannot contain string. Recommended Action Specify a target that does not contain this string. Error Message EID-652: Target must contain 4 dot-separated integers.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-663: Circuit ID length cannot exceed 64 characters. Recommended Action Enter a circuit ID that does not exceed 64 characters. Error Message EID-664: Circuit description cannot exceed 256 characters. Recommended Action Enter a circuit description that does not exceed 256 characters. Error Message EID-665: Config exception: Cannot change EMS identification.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-676: Some of the data was not exported correctly. See the file filename for details. Recommended Action A malfunction occurred while displaying data in the property sheet. A parameter cannot be exported, but the export operation will continue processing other parameters. Contact Cisco technical support. Error Message EID-677: Cannot execute the operation. Another NE configuration report is in progress.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-700: An error occurred while saving node coordinates to the database. Refresh the view and retry. Recommended Action Click the Refresh Data tool to refresh the view and recustomize the coordinates. Error Message EID-701: An error occurred while saving the node icon to the database. Refresh the view and retry. Recommended Action Click the Refresh Data tool to refresh the view and recustomize the node icons.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-712: An error occurred while loading the link from the database. Recommended Action Restart the Network Map. If the error persists, exit the Cisco MGM client and retry. Error Message EID-713: An error occurred while opening the node. Recommended Action Restart the Network Map. If the error persists, exit the Cisco MGM client and retry. Error Message EID-714: An error occurred while opening the parent node.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-722: Circuits must be created between two nodes that are in service and available. Recreate the circuit. Recommended Action Recreate the circuit. Error Message EID-723: Links cannot be created between two offview nodes. Recreate the link. Recommended Action Recreate the link. Error Message EID-724: Exception occurred while launching the Circuit Table.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-733: The node is not available or there are no available physical termination points for the given link size. Recommended Action All link termination points have links for the specified link size. Delete existing links and perform the operation again. Error Message EID-735: Create link action was not completed or was partially completed for link: link_ID. Recommended Action A link already exists with the same name.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-800: Selected NEs are invalid or unreachable. Recommended Action This error occurs because all NEs under a group are in service or under maintenance but are not reachable, or because the NEs are reachable but in different network partitions. Make sure that the selected NEs are in the same network partition. Error Message EID-801: None of the NEs contain ML cards or all ML cards are used for L2 topology.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-817: Select a topology to delete. Recommended Action Select a topology to delete. Error Message EID-833: Invalid source or destination selected for routing. Recommended Action Select a valid source or destination. Error Message EID-834: Error retrieving topology segments from server. Recommended Action This error occurs because the server is still initializing.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-857: Failed to provision L2 service. Recommended Action If the topology is not synchronized, close the L2 service wizard and try again after the topology synchronization is complete. If there is an invalid username or password, make sure that the username and password configured in the ML-series card are synchronized with the NE username and password. Close the L2 service wizard and try again.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-866: Select only one L2 service from the table. Recommended Action Select one L2 service. Error Message EID-868: No L2 service is selected to show drops. Select an L2 service. Recommended Action Select one L2 service. Error Message EID-869: Select only one L2 service from the table. Recommended Action Select one L2 service. Error Message EID-871: PIR should be greater than or equal to CIR.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-878: Failed to Reset General attributes of L2 Service. Recommended Action Close the modify L2 service window and try again. Error Message EID-879: Failed to Reset QoS values for L2 Service. Recommended Action Close the modify L2 service window and try again. Error Message EID-880: Failed to Reset Enable/Disable value for the drops in the L2 Service. Recommended Action Close the modify L2 service window and try again.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-906: Destination is not fully specified. Recommended Action Specify the destination NE and CTPs. Error Message EID-907: Slot selection is mandatory. Select the slot and retry. Recommended Action Select a slot and retry. Error Message EID-908: Port selection is mandatory. Select the port and retry. Recommended Action Select a port and retry. Error Message EID-909: STS/VT selection is mandatory.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-917: Sources cannot be the same. Recommended Action You cannot select the same CTPs for the source and secondary source. Select a different source or secondary source and retry. Error Message EID-918: Destinations cannot be the same. Recommended Action You cannot select the same CTPs for the destination and secondary destination. Select a different destination or secondary destination and retry.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-932: Failed to route circuit. Recommended Action The server is not ready. Wait several minutes; then, reopen the Circuit wizard and try again. Error Message EID-934: Failed to add drops. Recommended Action The underlying circuit might have been deleted. Reopen the Circuit wizard and try again. Error Message EID-935: Failed to set the circuit end points for editing.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-942: Delete job already in progress on the selected circuit(s). Wait until the job completes. Recommended Action You cannot delete this circuit because the delete request has been submitted on this circuit already. Error Message EID-943: Circuit deletion failure. Recommended Action Cisco MGM reports this error message if any associated cross-connections from the NEs could not be deleted.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-949: Number of circuits must be greater than or equal to 1. Enter a valid number and retry. Recommended Action Enter a value that is greater than or equal to 1. Error Message EID-950: Failed to upgrade the selected circuit(s). Recommended Action Select another circuit. Only circuits that are in an upgradable state can be upgraded. Wait for the source node to be discovered.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-960: Failed to change the circuit state. Recommended Action Check if the Cisco MGM server is up and running. Try again when the server is available. Error Message EID-961: The circuit name already exists. Enter a unique circuit name. Recommended Action Enter unique circuit name. Error Message EID-962: No active NEs are available. Recommended Action Launch the Circuit Table only on NEs available for circuit creation.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-972: When 'Ignore All Customer IDs' is not selected, at least one customer ID must be added to the Selected Names list. Recommended Action Add at least one customer ID to the Selected Names list. Error Message EID-973: When 'Ignore All Service IDs' is not selected, at least one service ID must be added to the Selected Names list. Recommended Action Add at least one service ID to the Selected Names list.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-987: There are no possible Ethernet nodes to add. Recommended Action No action. Error Message EID-988: Cannot create monitor circuits on this termination point. Recommended Action No action. Error Message EID-1001: Failed to retrieve circuit service provider object. Recommended Action Verify that the Cisco MGM server and the database is up and running. Error Message EID-1002: Failed to retrieve Sys ID for the NE.
Appendix B Error Messages Cisco MGM Client Error and Warning Messages Error Message EID-1015: Failed to retrieve received text. Recommended Action Verify that the Cisco MGM server is up and running. Check the NE connectivity. Verify that the provisioned card is present in the slot. Error Message EID-1016: Failed to set transmit text. Recommended Action Verify that the Cisco MGM server is up and running. Check the NE connectivity. Error Message EID-1017: Failed to set expected text.
Appendix B Error Messages Cisco MGM Server Error Messages B.2 Cisco MGM Server Error Messages Cisco MGM server error messages appear in the Error Log and have the following syntax: Date time: filename(line number): module-severity-error_ID: error_message Example: 01/01/03 09:56:01 PM: cliroutines.c(80): CONFIG-DEBUG-1201: Unknown_ETHERNET_PORT 0 The following error messages are categorized by severity (critical, major, minor, and debug) and are listed in ascending numeric order within each category.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-404: Unable to connect to database. Recommended Action The application failed to log into the Oracle database. Verify that the database and the listeners are running. There might be a license problem. Also, verify that the username and password are correct. Error Message EID-405: Failed to start main poller thread. Recommended Action Restart the server. Error Message EID-601: Failed to open trap listener socket.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-1025: Could not get access to one of the circuit nodes. Verify that you have user privileges for all of the nodes in this circuit. Contact the administrator if the problem persists. Recommended Action Verify that you have user privileges for all the nodes in the circuit. If the problem persists, contact your system administrator. Error Message EID-1026: This circuit has been deleted from another interface.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-1034: Failed to cancel the roll. Recommended Action Contact your system administrator. Error Message EID-1035: Failed to finish the roll. Recommended Action Contact your system administrator. Error Message EID-1036: Failed to retrieve LAP spans. Recommended Action Contact your system administrator. Error Message EID-1037: Failed to retrieve LO options. Recommended Action Contact your system administrator.
Appendix B Error Messages Cisco MGM Server Error Messages Step 3 Correct the problem and perform the operation again. Step 4 If the problem persists, contact the system administrator. Error Message EID-1052: Error occurred while adding the span. Recommended Action Click the Details button to view the reason why the span was not added. If reason is “not sufficient,” contact your system administrator. Error Message EID-1053: Error occurred while removing the span.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-1060: Error deleting. Recommended Action Click the Details button to view the reason why the deletion failed. For more information, contact Cisco technical support. Error Message EID-1061: Error creating ring provisioner: Could get data for the selected ring. Recommended Action Mark the NEs in the ring as out of service (OOS) and in service (IS). Error Message EID-1062: Error occurred while retrieving protect port details.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2026: Exception string occurred while initializing the NE Service. Trying to stop the service. Recommended Action Restart the Cisco MGM server. If the problem persists, contact Cisco technical support with the output from the getinfo script. Error Message EID-3101: init: Exception value occurred while initializing trap service. The snmpTrapDispatcher or snmpTrapHandler could not be started.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-6050: Exception. This method is not implemented for this network element. Recommended Action Contact Cisco technical support. Error Message EID-6051: Exception occurred while retrieving NE information. Recommended Action Contact Cisco technical support. B.2.2 Major Server Error Messages Error Message EID-202: Error destroying thread. Recommended Action The MGMServer.cfg file has been corrupted. Reinstall the Cisco MGM server.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-212: Error waiting on a semaphore. Recommended Action If the Cisco MGM server starts, ignore this internal error. If the server does not start, increase the memory or swap space on the server workstation. Error Message EID-218: Memory corruption: bad header. Recommended Action Restart the Cisco MGM server. Error Message EID-219: Memory corruption: bad footer. Recommended Action Restart the Cisco MGM server.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-237: Timer thread exiting. Recommended Action If the timer thread exits, the software and configuration upload/download will not work properly. Restart the server. Error Message EID-238: Unable to schedule timer work. Recommended Action This is an internal error; no action is required. Error Message EID-313: Length of request is more than expected. Recommended Action This is an internal protocol error.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-606: Active alarm recovery looping for NE ID. Recommended Action The Cisco MGM server cannot recover the active or standing alarms on the NE because of a loop in the SNMP agent on the NE. Restart the NE. Error Message EID-801: Failed to connect to a socket. Recommended Action The MGMServer.cfg file has been corrupted. Reinstall the Cisco MGM server.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-819: Selected topology is undergoing Resync. Please wait until the L2 Topology Resync is completed. Recommended Action Wait until the topology resynchronization is completed. Error Message EID-820: Some of the selected L2 topologies is undergoing Resync. Please wait until the L2 Topology Resync is completed. Please click details to see the list of L2 topologies undergoing resync.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-828: There are no M-cards in the topology. Recommended Action Check whether all the ML-series cards are present and try again. If the problem persists, contact Cisco technical support. Error Message EID-902: Cannot allocate memory. Recommended Action Increase the available memory or swap space on the server workstation and restart the application. Error Message EID-903: Cannot find table element.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2014: Exception: string. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-2015: Null NetElement for NE: NE_ID. Recommended Action If you are having operational problems, contact Cisco technical support with this error message.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2030: EventDispatcher received is null. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-2031: CerentCMService is null. Recommended Action If you are having operational problems, contact Cisco technical support with this error message.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2045: Exception_string occurred while deleting from Circuit Destination Table. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-2046: Exception_string occurred while deleting from Circuit Span Table.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2060: Cannot add discovered NE. Error occurred while converting the IP address to a long value. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-2061: Cannot add discovered node. NE information for GNE is null.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2069: Exception string occurred while updating NE IP address. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-2070: Exception string occurred while initializing discovered NE that exists in the database.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2086: Exception: value occurred while reading the ons15454-callback-iiop-listen-port parameter value from the MGMServer.cfg file. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-2104: Exception string occurred while adding discovered NE with IP address IP_address.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2204: Software download operation failed on NE ID because the standby agent version is running. Recommended Action The standby agent version is running. A download operation is allowed only when the active agent version is running. There are two options to correct the error: – Reset the NE to run the active agent version; then, overwrite the standby agent version by using the download operation.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2212: Software download operation failed because of invalid path parameter. Recommended Action Verify that the path name (representing the path on the TFTP server where the catalog.txt file is located) has the correct format. Error Message EID-2214: NE User Management failed - Selected user doesn’t exist on NE ID. Recommended Action None. Error Message EID-2217: NE User Management failed - Duplicated username for NE ID.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-3016: Cannot register for events. Recommended Action Open the Control Panel. Expand MGM and PM Service. Stop and restart the PM service. If the problem persists, contact the Cisco MGM administrator. Error Message EID-3017: Cannot open tables. Recommended Action Open the Control Panel. Expand MGM and PM Service. Stop and restart the PM service. If the problem persists, contact the Cisco MGM administrator.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-3031: Error in parsing tick rate XML. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-3033: Error in getting time zone. XML received is null. Recommended Action If you are having operational problems, contact Cisco technical support with this error message.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-4001: Exception: string occurred while connecting the CORBA object to the Object Request Broker (ORB). Recommended Action Restart the Cisco MGM server. If the problem persists, contact Cisco technical support with this error message. Error Message EID-4002: Exception: string occurred while creating the ConfigManager Interoperable Object Reference (IOR). Recommended Action Restart the Cisco MGM server.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-4018: Exception: string while registering for the internal Cisco MGM events with the main server. Recommended Action Restart the Cisco MGM server. If the problem persists, contact Cisco technical support with this error message. Error Message EID-4020: Exception: string while configuring the Internet Inter Orb Protocol (iiop) listen port in CORBA ORB. Recommended Action Restart the Cisco MGM server.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-4242: Exception: deletelink () unable to delete manual link. Link ID is string. Recommended Action Review the reason for failure stated in the error message. Retry after some time. If the problem persists, contact Cisco technical support. Error Message EID-5000: Exception: string occurred while initializing ServiceManager.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-5031: Exception: string occurred while launching service process. Recommended Action Verify that the server has adequate RAM and swap space as listed in the Cisco Media Gateway Manager 5.0 Installation Guide. Do not run other unapproved software on the server. Error Message EID-5041: Exception: string occurred while trying to connect to Service Manager.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-412: No free UDP sockets in pool. Recommended Action This is an internal error. Restart Cisco MGM if the application is not communicating with any NEs. Error Message EID-413: Invalid SNMP type in packet. Recommended Action This is an internal error. Restart Cisco MGM if the application is not communicating with any NEs. Error Message EID-414: Failed to open SNMP session. Recommended Action This is an internal error.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-603: Incorrect trap recvfrom with errno = value. Recommended Action This is an internal processing error. If the problem persists, contact Cisco technical support with this error message. Error Message EID-604: Failed to parse SNMP trap definition file filename. Recommended Action The traps.lst file in the bin directory where the Cisco MGM server was installed is corrupted. Delete the traps.lst file and restart the application.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-1404: The ping to the OSI daemon failed. Recommended Action This is an internal processing error. If the problem persists, contact Cisco technical support with this error message. Error Message EID-1405: Failed to start the OPS daemon for logging. Recommended Action This is an internal processing error. If the problem persists, contact Cisco technical support with this error message.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2009: Null object is passed in. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-2010: Invalid object type is passed in. Recommended Action If you are having operational problems, contact Cisco technical support with this error message.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2024: Exception string occurred while reading the ne-service-thread-pool-size parameter value from the MGMServer.cfg file. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-2029: Exception: string for NE: exception_string while exception_string.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2052: Invalid object passed to Circuit Module work. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-2053: Exception string occurred while adding circuit. Recommended Action If you are having operational problems, contact Cisco technical support with this error message.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-2082: Exception: value occurred while reading snmp-trap-queue-size parameter value from the MGMServer.cfg file. Recommended Action Check the MGMServer.cfg file for possible corruption. If the problem persists, contact Cisco technical support with this error message. Error Message EID-2084: Exception: value occurred while reading snmp-trap-forwarding-port parameter value from the MGMServer.cfg file.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-3004: Incorrect IP address passed in IPADDR_CHANGED Event value. Recommended Action Check the newly changed IP address and modify it if you entered the wrong information. Error Message EID-3005: Cannot write DS-1 PM for value. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-3014: Cannot collect PM. Writer creation failed. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-3047: PM Comm Session is null for NE_name. Recommended Action Verify that the NE has available connections.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-4011: The Configuration resync operation cannot be completed because of the non-working operational state of the network element. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-4012: The Configuration resync is already in progress for this network element. Try after some time.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-4021: Exception: string while reading configuration request queue size from the MGMServer.cfg file. Using the default request queue size. Recommended Action Restart the Cisco MGM server. If the problem persists, contact Cisco technical support with this error message. Error Message EID-4022: Cisco MGM server is busy syncing the configuration information for this network element. Retry after some time.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-4205: Failed to {activate | revert} for NE_name: Detailed_error_message. Recommended Action Follow the instructions given in the detailed error message. Error Message EID-4206: Exception: The node is not managed by the NEService. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-4214: Exception: Failed to get link in database. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-4215: Exception: Failed to modify link in database. Recommended Action If you are having operational problems, contact Cisco technical support with this error message.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-4224: Exception: deleteLink() Cannot Delete an Auto. Discovered Link. Link ID is string. Explanation If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-4225: Exception: getNetLinks() DBException Raised while getting Network Links from DB.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-4500: Exception: Invalid model type for this operation. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-4501: Exception: Backup/Restore internal exception. Recommended Action If you are having operational problems, contact Cisco technical support with this error message.
Appendix B Error Messages Cisco MGM Server Error Messages Error Message EID-5024: Exception: string occurred while trying to purge NE. Recommended Action If you are having operational problems, contact Cisco technical support with this error message. Otherwise, ignore this error message; no action is required. Error Message EID-5025: The MGM Service is currently connected to Service Manager. Recommended Action Wait until the AUD-5004 message is displayed; then, click the Activate button again.
Appendix B Error Messages Cisco MGM Server Audit Messages B.2.4 Debug Server Error Messages Error Message EID-4028: String communication state: NE_ID; string = NESysID, NE_ID = NE connection state. Recommended Action Try and restore the connection to the NE. Note Detailed actions are NE-dependent. Error Message EID-4029: String operational state: NE_ID; string = NESysID, NE_ID = NE operational state. Recommended Action Set the NE state to In Service.
Appendix B Error Messages Cisco MGM Server Audit Messages Audit Message AUD-102: Cisco MGM user username logged out from location. Audit Message AUD-105: Job# number succeeded for NE: NE_name. Audit Message error_message. AUD-106: Job# number failed for NE: NE_name with the error: Recommended Action The job can fail to start if the NE is unavailable or if the configured SNMP community string does not have write privileges.
Appendix B Error Messages Cisco MGM Server Audit Messages Audit Message state. AUD-116: State for port number of NE_ID changed from state to Audit Message AUD-117: GNE for NE_ID changed from old_GNE_name to new_GNE_name. Audit Message AUD-118: Cisco MGM server started. Audit Message AUD-119: Cisco MGM server stopped. Audit Message AUD-120: The NE configured as NE_ID is actually NE_ID. Audit Message AUD-121: Administrative task number deleted.
Appendix B Error Messages Cisco MGM Server Audit Messages Audit Message AUD-135: NE name Port port_number state changed to In Service. Audit Message AUD-136: NE name Port port_number state changed to Out of Service. Audit Message AUD-138: NE name Port port_number state changed to In Maintenance. Audit Message AUD-139: NE name property changed - New Sys ID value. Audit Message AUD-140: NE name property changed - New IP address value.
Appendix B Error Messages Cisco MGM Server Audit Messages Audit Message AUD-159: Subnet value topology changed. Audit Message AUD-160: Subnet value GNE changed. Audit Message AUD-161: Subnet value name changed. Audit Message AUD-162: Subnet value user label changed. Audit Message AUD-163: Topology changed - Group value added. Audit Message AUD-164: Topology changed - Group value deleted. Audit Message AUD-165: Topology changed - NE NE_ID added.
Appendix B Error Messages Cisco MGM Server Audit Messages Audit Message changed. AUD-182: MGM user username profile changed - Domain description Audit Message AUD-184: Failed login threshold exceeded for user username. Audit Message AUD-185: Password aged out for user username. Audit Message IP_address. AUD-186: MediaGatewayManager user username forced to log out from Audit Message username. AUD-187: MediaGatewayManager service service_name logged in from Audit Message username.
Appendix B Error Messages Cisco MGM Server Audit Messages Audit Message number. AUD-207: Rejected a user login from IP address IP_address, port Audit Message number. AUD-208: User username logged out from IP address IP_address, port Audit Message AUD-209: NE ID reported. Audit Message AUD-2000: Cisco MGM successfully contacted NE: name. Audit Message AUD-2001: Cisco MGM was unable to contact NE: name. Recommended Action Check network connectivity.
Appendix B Error Messages Cisco MGM Server Audit Messages Audit Message AUD-2206: Software download operation failed because it is not supported by the running agent version. Audit Message AUD-2207: Software download operation failed because of a Flash reading/writing problem. Audit Message AUD-2208: Software download operation failed because of a problem during transfer from the TFTP server to the master CMP.
Appendix B Error Messages Cisco MGM Server Audit Messages Audit Message is value. AUD-3056: Processing NE time offset for string. New offset value Audit Message AUD-3057: Data format error while obtaining PM data for string for interval string. Audit Message AUD-3060: PM Comm Session is null for NE_name. Audit Message AUD-3062: Exception during PM collection for NE_name. Audit Message AUD-3063: Cannot write PM data for NE_name. Audit Message blank.
Appendix B Error Messages Cisco MGM Server Audit Messages Audit Message Manager. AUD-5003: The MGM Service service name has connected to Service Recommended Action The service has started. You can perform a service Stop operation. Audit Message Manager. AUD-5003: The MGM Service service name has connected to Service Audit Message AUD-5004: The MGM Service service name has disconnected from Service Manager. Recommended Action The service has shut down. You can perform a service Start operation.
Appendix B Error Messages Cisco MGM Server Audit Messages Cisco Media Gateway Manager 5.
A P P E N D I X C Troubleshooting This appendix offers troubleshooting steps to help solve high-level problems while operating Cisco MGM or Cisco MGM GateWay. This chapter includes the following troubleshooting information: • C.1 Server Problems • C.2 Client Connectivity Problems • C.3 Client Operational Problems • C.4 Topology Problems • C.5 Equipment Management Problems • C.6 Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems • C.
Appendix C Troubleshooting Server Problems Note This chapter assumes that the server is installed under the default /opt/CiscoMGMServer directory and the client is installed under the default /opt/CiscoMGMClient or C:\Cisco\MediaGatewayManagerClient directory. If a directory other than the default installation directory is specified, replace the default path with the installed path during setup. C.
Appendix C Troubleshooting Server Problems Note Step 3 You can also check the mgmop.log file found in /opt/CiscoMGMServer/log to check whether the server was stopped by another user or it stopped abnormally. If it stopped abnormally, proceed to Step 3. Run the getinfo.sh Cisco MGM server tool and send the data to Cisco technical support for analysis.
Appendix C Troubleshooting Server Problems Step 5 The server should have at least the following four processes running: root root root root Step 6 3778 3771 3876 3798 0.1 0.1567 9592 ? S 16:57:36 0:00 /opt/CiscoMGMServer/bin/CTMServer 0.1 0.4 6208 pts/1 S 16:57:34 0:00 /opt/CiscoMGMServer/bin/CTMServer 0.5 0.6129464 8648 ? R 16:58:12 SnmpTrapService 26.8 4.115732060968 ? S 16:57:37 0:29 SMService Manually stop the server if you see fewer than four processes running.
Appendix C Troubleshooting Server Problems C.1.3 NE Connection State Is Listed as Unavailable If the connection state of an NE is listed as Unavailable in the Domain Explorer window, a connectivity or configuration problem exists. Wait 5 to 10 minutes after adding the NE to the Cisco MGM domain; then, complete the following steps: Step 1 To see the NE IP address, select the NE in the Domain Explorer window. The Address tab of the Network Element Properties sheet lists the IP address of the selected NE.
Appendix C Troubleshooting Server Problems C.1.5 SNMP Traps Are Not Forwarded from NEs SNMP traps might not be forwarded, either because the trap port is already in use, or because the NE is not properly configured. C.1.6 Trap Port Is Unavailable The Cisco MGM server requires exclusive access to the SNMP trap port to receive SNMP traps from the NE.
Appendix C Troubleshooting Server Problems C.1.9 NE Model Type Appears as Unknown If an in-service NE is added to the Domain Explorer, but the model type appears as unknown, the software version of the NE might not be prepopulated in the database. In other words, Cisco MGM cannot match the NE with a recognizable version. C.1.
Appendix C Troubleshooting Client Connectivity Problems C.2 Client Connectivity Problems The Cisco MGM client might not be able to connect to the Cisco MGM server for various reasons. Complete the following procedures in the order listed until the problem is resolved: • C.2.1 Database Is Not Available • C.2.2 Database Timeout Occurred • C.2.3 Are the Cisco MGM Client and the Cisco MGM Server Connected? • C.2.4 Cannot Log In as Provisioner or Operator • C.2.
Appendix C Troubleshooting Client Connectivity Problems C.2.3 Are the Cisco MGM Client and the Cisco MGM Server Connected? If the database is available, check connectivity between the client and the server: Step 1 To see the Cisco MGM server IP address, enter the following command on the Solaris workstation that is running the Cisco MGM server: ifconfig -a The command output looks similar to the following example: hme0:flags=863mtu 1500 inet 192.168.120.
Appendix C Troubleshooting Client Operational Problems C.2.5 “Cannot Authenticate User” Message Appears If the “Cannot authenticate user” error message is received when logging into the Cisco MGM client, the Cisco MGM server might be initializing. Wait for five minutes while the Cisco MGM server finishes initializing; then, try to log in again. Alternately, check your username and password and enter them again. The username and password are case sensitive. C.
Appendix C Troubleshooting Client Operational Problems C.3.3 Cannot Schedule Jobs The Cisco MGM client is used to schedule three types of administrative tasks: • Software download • Memory backup • Memory restore Cisco MGM maintains an Error Log and audit log to track potential problems. To view the Error Log or audit log: Step 1 In the Domain Explorer window, choose Administration > Audit Log or Administration > Error Log.
Appendix C Troubleshooting Client Operational Problems Command output looks similar to the following example: --- Hardware Configuration for /dev/fbs/m640 --ASIC: version 0x7c004750 DAC: version 0x0 PROM: version 104 Card possible resolutions: 720x400x88, 640x480x60, 640x480x72, 640x480x75, 800x600x56, 800x600x60, 800x600x72, 800x600x75, 1024x768x87, 1024x768x60, 1024x768x70, 1024x768x75, 1280x1024x75, 1280x1024x60, 1152x900x66, 1152x900x76, 1280x1024x67, 1280x800x76, 1280x1024x85 1280x1024x76, 1152x864x
Appendix C Troubleshooting Client Operational Problems • Service is the service name for which the thread dump is required. It can be: – SMService – SNMPTrapService – CORBAGWService – MGX8880NEService – MGX8850NEService – UnmanagedNEService C.3.7 Launching Help on a Solaris Client To launch help on a Solaris Client, Netscape must be in the PATH environment variable.
Appendix C Troubleshooting Topology Problems C.4 Topology Problems This section includes the following information: C.4.1 Discovery Mechanism C.4.2 Discovery Issues at Startup C.4.1 Discovery Mechanism Cisco MGM manages the PNNI network. The ILMITopoc process discovers the physical PNNI network using SNMP protocol. All the discovered nodes are displayed in all the MGX NE GUIs such as Configuration Center (CC), Diganostic Center (DC), Statistics Report (SR), Chassis View (CV) GUI.
Appendix C Troubleshooting Topology Problems Step 3 If it is a MGX2 node and If persistent topology is enabled on the switch gateway and some nodes in a peer group are not getting discovered, verify that persistent topology is enabled on the gateway in the peer group using the CLI dsptopogw.
Appendix C Troubleshooting Topology Problems Step 2 If the node table does not have the ipAddress set correctly: • In Cisco MGM, since the node does not have any PNNI trunks and the persistent topology feature is not enabled on this node, by default this node will be managed using the lan ip address. Verify if this is the case. Defect Information—Collect the following information for further analysis: • Save ILMITopoc.log and topod.log • Save the dump outputs of ILMITopoc, topod.
Appendix C Troubleshooting Topology Problems Step 2 If the node table has alarm state of an MGX node as unreachable: • Verify that the node is ipreachable from Cisco MGM Ping the active ip address of the node. The active ip will be the ip address of the node that is populated in the node table. • Verify that the community string in the node_info table is the same as the community string on the node. The community string of a node can be got using the CLI dspsnmp.
Appendix C Troubleshooting Topology Problems C.4.3 Discovery Issues at Runtime This section includes the following information: • C.4.3.1 Node Added Not Shown in Cisco MGM Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs • C.4.3.2 Node Name Change Not Getting Updated in Cisco MGM Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs • C.4.3.
Appendix C Troubleshooting Topology Problems C.4.3.2 Node Name Change Not Getting Updated in Cisco MGM Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs Changes in the name of a node not reflected on the Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs. Step 1 If the node table has an entry for the node with the correct name • Step 2 Dump the cache of NMServer, Topod and ILMITopoc. To dump the cache issue a kill -USR1 signal to the process.
Appendix C Troubleshooting Equipment Management Problems Defect Information—Collect the following information for further analysis: • Collect the ILMITopoc.log, topod.log, NMServer.*.log, nts.*.log • Collect the dump outputs of ILMITopoc, topod and NMServer. The dump can be captured by issuing a kill -USR1 signal to the process. • Collect the output of the switch CLI, selnd and dbnds. Possible alternative workaround—None C.
Appendix C Troubleshooting Equipment Management Problems The following is the flow of events which are involved in OOEMC coldstart sync up process: 1. Topo process discovers a node in the network. The process will change the node mode in node DB table to -1. Then it notifies OOEMC component for the discovery. Then OOEMC will change the node mode from -1 to 1 after the component starts managing the node. 2.
Appendix C Troubleshooting Equipment Management Problems C.5.1.3 Node Mode Remains in 1 The node has been discovered by network topology process in Cisco MGM and its node mode has been changed from -1 to 1 in node table entry, but it stays in mode 1 for a long period of time. Step 1 If the Cisco MGM stays in mode 1 for a long time after Cisco MGM core has been started, you need to check the trap manger on the switch. See C.5.1.
Appendix C Troubleshooting Equipment Management Problems Step 4 If the trap IP is not an issue, then check whether there is SNMP request failure. Normally, after node resync is triggered, OOEMC will send SNMP request to the switch to start configuration upload file creation. If the request fails, then OOEMC will retry SNMP request until it exceeds maximum retrials and declares node resync failure with node mode equal to 5.
Appendix C Troubleshooting Equipment Management Problems 10. PNNI_01_CC.CF Files 1 and 2 are uploaded for each NBSM. Files 4 to 7 are uploaded for each AXSM. File 9 is uploaded for all RPM/RPM-PR cards on the switch. The following list the files uploaded from MGX NE for VISM, AXSM, VXSM, SRM, RPM/RPM-PR, and RPM-XF cards: 1. CARD_01_CC.CF 2. SM_1_slot#.CF 3. SM_1_slot#.CS 4. SM_CARD_01_slot#.CF 5. SM_CONN_01_slot#.CF 6. SM_ALARM_01_slot#.CF 7. SM_CON_UPDATE_01_slot#.CF 8.
Appendix C Troubleshooting Equipment Management Problems 3. OOEMC will receive bulk file creation related traps: 60901, 60902, and 60903. 4. OOEMC will FTP config upload files from switch after it has received 60901 and 60902 from switch. 5. OOEMC will parse the config upload files 6. OOEMC will declare sync up done. When mode 5 problem occurs on one of the nodes, you should ask yourself the following questions: 1.
Appendix C Troubleshooting Equipment Management Problems C.5.1.6 Cisco MGM DB Inconsistent With Switch Data After Successful Coldstart (Cisco MGM Server stop/start) or Periodic Resync After successful node resync triggered by periodic resync, the Cisco MGM DB is found inconsistent with switch data. Step 1 For this issues, what user can do is to collect ooemc log files and all config upload files for the node. OOEMC implement node based cache. User can dump and save the cache.
Appendix C Troubleshooting Equipment Management Problems Defect Information—Collect ooemc log files and dbroker log files in /opt/svplus/log. Also collect config upload files in /opt/svplus/tmp Possible alternative workaround—User can manually resync the node. If the problem persists, user should try coldstart. If the problem is still not able to be resolved, collect log files and report the problem. C.5.1.
Appendix C Troubleshooting Equipment Management Problems Step 3 Step 4 To determine whether or not OOEMC sends newly provisioned or updated DB data to NMServer, grep "ComposeNMSMsg" from OOEMC log files.
Appendix C Troubleshooting Equipment Management Problems Possible alternative workaround—User can manually resync the node. If the problem persists, user should try coldstart. If the problem is still not able to be resolved, collect log files and report the problem. C.5.2 Cisco MGM DB and Switch Data Inconsistency Issues After Node Provisioning for MGX This section includes the following information: • C.5.2.1 DB Table Population Through Traps and SNMP Upload • C.5.2.
Appendix C Troubleshooting Equipment Management Problems For other kinds of traps, you can use the following key words to supplement "TRAPLIST" in your grep statement: 1. Port Trap 2. RscPart Trap 3. Svc Trap 4. SonetLn Trap 5. SctCard Trap 6. SonetPath Trap 7. FunMod Trap 8. LineMod Trap 9. RedCard Trap 10. TrapMiss Trap 11. VsiCtrlr Trap 12. DS3Line Trap 13. AtmPhy Trap 14. Peripheral Trap 15. CoreSwth Trap 16. TrapLost Trap 17. AtmAddr Trap 18. Restart Trap 19. Node Trap 20.
Appendix C Troubleshooting Equipment Management Problems 37. CesmChan Trap 38. HsFrPort Trap 39. HsFrChan Trap 40. LineDist Trap 41. DS3Path Trap 42. Chan Upload 43. Party Trap 44. PrefRoute Trap 45. CardIma Trap 46. DS1 Line Trap 47. SctPort Trap 48. SvcDerouteGroomTrap 49. Channel Trap 50. TUG3Path Trap 51. Cug Trap 52. AddrCug Trap 53. RSC Upload 54. APS Upload 55. FrPort State Upload 56. MPSM Upload 57. Vism ToneDetect Trap 58. License Trap 59. PortAtmIf Trap 60. VxsmPvcRed Trap 61. ChanProt Trap 62.
Appendix C Troubleshooting Equipment Management Problems 75. VxsmAal2CrossConn Trap 76. VxsmAal25DataProfileTrap 77. VxsmSensor Trap 78. VxsmSensorThrhd Trap 79. VxsmModule Trap 80. DS0Grp Trap 81. VxsmAnnounce Trap 82. VxsmAudioFile Trap 83. VxsmDs0XConn Trap 84. VxsmMegaco Trap 85. VxsmCrr Trap 86. VxsmTone Trap 87. VxsmAs Trap 88. VxsmAsp Trap 89. VxsmAs Trap 90. VxsmLapd Trap 91.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems To verify that the trap has been put into queue, you can do the following grep EMC_TrapQueue_c::append ooemc_log | grep trap_num You should see something like the following: INFO: entering.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems Figure C-1 Cisco MGM End-to-End Architecture Chassis View Tree View Topology View Alarm List View Presentation Layer Alarm Service Inventory Service Object Repository Data and Interface Layer Alarm Repository Event Handler Fault Management Equipment Manger and Sync-up Business Logic Layer Multiservice WAN Network 120752 Network Topology Management NMServer provides Inventory an
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems • nmClient—This utility is used to isolate an issue between client and server. It is used to query the NMServer the same way as the Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUI queries the Server. It allows the following operations. Output is redirected to /opt/svplus/log/nmClient.log. Cache dumps are redirected to /opt/svplus/log/nmClient.dump.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems Defect Information—Collect the following information for further analysis: • Collect topod.log, ILMITopoc.log, NMServer.log • Collect nmControl.dump for option 3. • Collect CMSCclient.log Possible alternative workaround—Open a new GUI and a new Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUI. C.6.2.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems C.6.3 Topology Discovery Issues This section includes the following information: • C.6.3.1 Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs Do Not Show a Node • C.6.3.2 Node Information Incorrect on Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs • C.6.3.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems C.6.3.2 Node Information Incorrect on Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs The node information like node name, IP Address, alarm state, etc., of a node shows incorrectly on the Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs. Step 1 Check the node information in database using selnd command.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems Defect Information—Collect the following information for further analysis: • Collect the ILMITopoc.log, topod.log, NMServer.log • Collect the dump outputs of ILMITopoc, topod and NMServer. The dump can be captured by issuing a kill -USR1 signal to the process. • Collect the output of the switch CLI, selnd and dbnds. Possible alternative workaround—None C.6.3.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems Step 3 If duplicate nodes do not exist in database, then check the cache of NMServer using nmControl (Option 3). Step 4 Check the CMSCclient.log for the node. Step 5 Using nmClient, use getTopology option to retrieve the node information and verify whether it matches with database and the GUI.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems Step 7 If cards are present in NMServer cache, Open a New GUI and verify whether the cards are shown in the new GUI. Defect Information—Collect the following information for further analysis: • Collect topod.log, ILMITopoc.log, NMServer.log • Collect nmControl.dump for option 4. • Collect CMSCclient.log Possible alternative workarounds: 1.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems C.6.4.3 Card/Line/Port Information Incorrect on Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs The entity information like type, alarm state, etc., of an element shows incorrectly on the Configuration Center, Chassis View, Diagnostic Center or Statistics Report GUIs. Step 1 Check whether the node is synced up.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems Step 5 If element is not in the database, check the NMServer cache. This can be done by using the command nmControl (Option 4) on the Cisco MGM CLI. Check the nmControl..dump Step 6 Use nmClient and verify whether getChildren for FDN, returns the element in the nmClient..dump file.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems 6. Alarm List displays mostly active alarms, however some 'Events' are also displayed. For details on 'Events vs. Alarms' see Figure 7.5.2, "INF: XML Schema for alarm rules," on page 153. 7. Some alarms result in the network element having a different alarm severity then the actual alarm. For details on 'Object Severity vs. Alarm Severity' see Figure 7.5.3, "INF: Alarm Severity vs.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems Figure C-3 Correlated Alarm Rule Diagram Figure C-3 XML annotation can be read as follows. A CorrelatedRule can have any of the following: • 1 AlwaysClear (Used when a given element never has an alarm, such as top level Network) • 0 or more ClearAlarmCondIds • 1 New Alarm (which consists of NewAlarmConditionID, NewAlarmServAffect, etc.) 2.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems Figure C-4 XML annotation can be read as follows. A CorrelatedBmRule can have any of the following: • 0 or more ClearAlarmCondIds • 1 New Alarm (which consists of NewAlarmConditionID, NewAlarmServAffect, etc.) 3. Transient Alarm Rule Type The Transient Alarm rule type is used to distinguish events vs. alarms. Alarm List does show some events.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems 6 7 Sync-Up has not started yet This alarm will occur if the southbound processes (EMs) send a node message with EM syncup status as 1 or -1. If that does occur, then the node should be unreachable severity (value 7) in the tree view.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems Step 4 Step 5 Verify whether discrepancy is caused by aggregated connection alarms a. NMServer does more aggregation of alarms then the platform. For instance, NMServer aggregates connection alarms up the port and the switch does not. Therefore, if the tree view displays a higher severity then the switch, it maybe caused by one or more aggregated port alarms. b.
Appendix C Troubleshooting Configuration Center, Chassis View, Diagnostic Center and Statistics Report Problems Step 2 If the suspect alarm is not in the list above, and it is displayed in the alarm list and not on the platform, it may be defect. See below for troubleshooting further a. Verify whether DB has correct alarm state, refer to the DB schema document for information on what table to lookup for this particular entity type. b. Collect the information requested in Defect information section.
Appendix C Troubleshooting Chassis View Problems C.6.5.7 Port in Tree View Displays an Aggregate Alarm, However No Children Exist Under Port The tree view in Cisco MGM client GUIs display network elements from the top-level 'Physical View' down to the 'Port'. Alarm severities are aggregated from children up to parents.
Appendix C Troubleshooting Chassis View Problems C.7.1 Chassis View Basics Chassis View is a read-only application which provides the physical view of WAN devices. For a specific node, it displays node, cards and lines. Chassis View does not display port.
Appendix C Troubleshooting Chassis View Problems Possible alternative workaround—You can select the lines from the Tree View to launch other applications. C.7.3 Card Not Displayed in MGX Nodes Card is not displayed in the Chassis View in MGX nodes. Step 1 Check that entries for the card is available in the card table. Step 2 Check whether the lines are defined in the XML file ChassisView.xml. Step 3 Make sure that the node is in sync (mode is 3).
Appendix C Troubleshooting Chassis View Problems C.7.7 RPM Card Status not Updated Dynamic event updates are not generated for RPM cards on MGX PXM1-based nodes. So, Chassis View does not get event updates on hot insertion or removal of RPM cards. Anyway the card will be identified when cold start is done. C.7.8 RPM Secondary Card Status Is Blue For RPM cards, stand-by state will show the card status in blue color as the card has only one LED(CPUOK) to show the status of the card unlike the other cards.
Appendix C Troubleshooting Configuration Management - Elements Defect Information—Collect the following information for further analysis: • Get the copy of XML file used. ChassisView.xml for MGX nodes and BPXIGX.xml for BPX/IGX nodes. • Take a copy of the "chassisview.jar" from the location "/opt/svplus/java/jars/cwm/". We need to check that gif files used to draw the lines. Possible alternative workaround—Try selecting from the Tree View. C.
Appendix C Troubleshooting Configuration Management - Elements • C.8.1.10 Cross Application—Configuration Center Element Tab as Drop Target • C.8.1.11 Element Tab—Internal Frame Displays Incorrect Object or Object Data • C.8.1.12 Configuration Center's Element Tab Does Not Respond (GUI Is Grayed-Out) C.8.1.
Appendix C Troubleshooting Configuration Management - Elements C.8.1.3 Exception Raised When Configuration Center Is Launched When the Configuration Center is launched, using one of the methods described above, an exception is raised and the Java Console shows the exception trace information. Defect Information—Collect the following information for further analysis: • Collect Java Console information. • Collect CMSCclient.
Appendix C Troubleshooting Configuration Management - Elements C.8.1.6 Element Tab—Drag and Drop Does not Launch An Internal Frame When Element tab is selected, the Drag and Drop of supported network elements to the Element tab's content pane does not create an internal frame or recycle the content of an existing internal frame to display the dropped object. Defect Information—Collect the following information for further analysis: • Collect CMSCclient.
Appendix C Troubleshooting Configuration Management - Elements Defect Information—Collect the following information for further analysis: • Collect CMSCclient.log file under the D:\Documents and Settings\username\log directory. • Collect Java Console information (In particular any java raised exceptions) • Collect screen snapshots. In particular, error/information message dialog boxes. • Collect cmsvr.log file under the /opt/svplus/log directory. • Collect configserver.
Appendix C Troubleshooting Configuration Management - Elements Defect Information—Collect the following information for further analysis: • Collect CMSCclient.log file under the D:\Documents and Settings\username\log directory. • Collect screen snapshots. In particular, error/information message dialog boxes. • Collect Java Console information (In particular any java raised exceptions) • Collect cmsvr.log file under the /opt/svplus/log directory. • Collect configserver.
Appendix C Troubleshooting Configuration Management - Elements This section includes the following information: • C.8.2.1 XML Parsing Error • C.8.2.2 SNMP No Data Error • C.8.2.3 Details/Create/Delete/Refresh Buttons Are Not Enabled (highlighted) • C.8.2.4 SNMP Timeout Error • C.8.2.5 SNMP Set Error • C.8.2.6 Object Not Found In Tree View Error • C.8.2.7 Element Data Inconsistent With Switch • C.8.2.8 Config Server Reported Error Messages C.8.2.
Appendix C Troubleshooting Configuration Management - Elements d. If the EntityName part of the XML file name is incorrect, contact Cisco MGM engineers, with the Defect Information required (as given below). Defect Information—Collect the following information for further analysis: • Collect CMSCclient.log file under the D:\Documents and Settings\\log folder • Collect Java Console information. • /opt/svplus/log/configserver.
Appendix C Troubleshooting Configuration Management - Elements C.8.2.3 Details/Create/Delete/Refresh Buttons Are Not Enabled (highlighted) These buttons are enabled or disabled based on the requirement in the tabular view. A button is disabled when the corresponding operation is not supported. Open /opt/svplus/log/configserver.log for the MIB Step 1 If "Create" button is disabled, use any SNMP tool to create the object using SNMP SET operation.
Appendix C Troubleshooting Configuration Management - Elements C.8.2.5 SNMP Set Error This error occurs when SNMP SET operation is done on an unmodifiable MIB object or with invalid values. A sample snapshot of SNMP SET Error is shown below. Step 1 Open the /opt/svplus/log/configserver.log. Step 2 Check for the document name being used. Look for the last part of the document name. For Example, if the document name is AAA-BBB-CCC.xml, then the document AAA-BBB-CCC.
Appendix C Troubleshooting Configuration Management - Elements c. For a line, the window title will have .. d. For a port, the window title will have .. and so on. Step 2 Step 3 With the information obtained from Step1, Check if that object is appearing in the tree view. a. If it does appear, go to step 3. b.
Appendix C Troubleshooting Configuration Management - Elements Step 6 Check the datatype of the MIB object that shows inconsistent data. If the datatype of the MIB object in the configserver.log is same as the datatype as defined in the MIB object definition (available at /opt/svplus/mibs/ directory), go to step 7: , else contact Cisco MGM engineers with defect information. Step 7 Check the datatype of the MIB object. a.
Appendix C Troubleshooting Connection Management Problems Defect Information—Collect the following information for further analysis: • Collect all complete screen snapshots for the investigative commands used for debugging this issue. • Contents of /opt/svplus/log/CMSCclient.log file. Possible alternative workaround—None C.9 Connection Management Problems This section includes the following information: • C.9.1 Configuration Center GUI; Framework Issues • C.9.
Appendix C Troubleshooting Connection Management Problems This section includes the following information: • C.9.1.1 Connections Tab—Double Click on a Tree View Does not Launch Connection's Internal Frame • C.9.1.2 Connections Tab—Drag and Drop Does Not Launch Connection's Internal Frame • C.9.1.3 Connection List Tab—Cannot Launch Internal Frame To Modify An Existing Connection (Using the Modify Button) • C.9.1.
Appendix C Troubleshooting Connection Management Problems C.9.1.2 Connections Tab—Drag and Drop Does Not Launch Connection's Internal Frame The Drag and Drop (DnD) of a network element from the Configuration Center Tree View to the Connections tab's content pane (a) fails to open an internal frame, (b) fails to recycle the contents of an existing frame to display the dropped object's attributes or (c) results in the 'Operation Not Supported' message dialog box.
Appendix C Troubleshooting Connection Management Problems C.9.1.4 Advanced Mode Tab—Cannot Launch Connection Details Dialog (Using the 'Detail' Button) The 'Details' button on the Advanced Mode tab fails to launch the 'Connection Details Dialog'. Defect Information—Collect the following information for further analysis: • Collect CMSCclient.log file under the D:\Documents and Settings\username\log directory. • Collect Java Console information (In particular any java raised exceptions).
Appendix C Troubleshooting Connection Management Problems C.9.1.7 Cross Application—Connection List as Drag Source As drag source, the DnD of a connection from Configuration Center's connection list to another CMSC application fails to display the selected connection in the target application. Step 1 Determine target application supports connection object drop operations. Determine that the target application supports the DnD operation for connection objects.
Appendix C Troubleshooting Connection Management Problems C.9.1.9 Configuration Center's Connection Tab Does Not Respond (GUI Is Grayed-Out) The Configuration Center's connection tab does not respond and the GUI is grayed-out. Step 1 Try to reproduce the problem in order to collect additional Java related data using Java DOS Window. Defect Information—Collect the following information for further analysis: • Collect CMSCclient.
Appendix C Troubleshooting Connection Management Problems NO_SUCH_SERVICE_TYPE_ENUM: "No such service type enum [%d]" NO_SUCH_ENDPOINT_TYPE_ENUM: "No such endpoint type enum [%d]" NO_PORT_TABLE_INFO_FOR_CARD: "No port table information for card family [%d]" NO_LINE_TABLE_INFO_FOR_CARD: "No line table information for card family [%d]" FILTER_REQUIRED:"Filter [%s] is required" UNEXPECTED_PARAMSET: "CM Server does not expect parameter set [%d].
Appendix C Troubleshooting Connection Management Problems Defect Information—Collect the following information for further analysis: • Collect CMSCclient.log file under the D:\Documents and Settings\username\log directory. • Collect screen snapshots. In particular, error/information message dialog boxes. • Collect Java Console information (In particular any java raised exceptions). • Collect cmsvr.log file under the /opt/svplus/log directory. • Collect configserver.
Appendix C Troubleshooting Connection Management Problems Defect Information—Collect the following information for further analysis: • Collect CMSCclient.log file under the D:\Documents and Settings\username\log directory. • Collect screen snapshots. In particular, error/information message dialog boxes. • Collect Java Console information (In particular any java raised exceptions). • Collect cmsvr.log file under the /opt/svplus/log directory. • Collect configserver.
Appendix C Troubleshooting Connection Management Problems C.9.3.2 Unsupported Service Type for the Foresight Connections for PNNI/SPVC Endpoints During connection addition, an eror in the return error window on the screen could state "CM Server does not support Connection type[], Service type[], and Endtoend type []between Card type and []." The parenthesis are filled with appropriate values. We need to determine if the service type is applicable to the endpoints.
Appendix C Troubleshooting Connection Management Problems C.9.3.5 Cannot Add Connection Between -byte Port Header and -byte Port Header for chan type NIW and NIW-replace During a connection addition between two FRSM_12 ports, the cmsvr checks to see if the port headers are the same (4-byte or 2-byte) for both the end points. An error is thrown if they are not. "Cannnot add Connection between 4 byte port header to 2 byte port header for chan type NIW or NIW-replace.
Appendix C Troubleshooting Connection Management Problems C.9.3.8 Cmsvr—Connection Diagnostics Issues The cmsvr processes validates and services the Connection provisioning requests from the CM GUI. If the request is for connection addition, modification, deletion or connection trace, the request is forwarded to cmgrd process through ILOG(IPC) request. If the request is for connection diagnostics like testdelay, testconn etc. (except conntrace), cmsvr sends to snmpcomm process for forwarding to switch.
Appendix C Troubleshooting Connection Management Problems C.9.3.10 Connection Up/Down/Reroute Failed Connection up/down/reroute diagnostics failures with switch error Step 1 Query the connection information from the user_connection table for that connection Step 2 Query the connection information from the switch CLI and verify the connection status (dspcon, dspchan etc.
Appendix C Troubleshooting Connection Management Problems Possible alternative workaround: 1. Check the status of the connection and clear any alarms due to line/port issues (adding loopback, correcting the physical cable issues by verifying the physical port connections etc.). After the connection comes up and fine in clear state, rerun the trace diagnostics again. 2. Verify the connection status. If the connection status is down trace cannot be executed on the connection.
Appendix C Troubleshooting Connection Management Problems The Connection subsystem comprises the following modules: • ConnProxy—Is the SNMP Agent Interface for Connection Management, client to cmgrd. • CmServer—Provides the backend functionality to the Connection Management GUI, client to cmgrd. • Cmgrd—Is the backend module which accepts requests from ConnProxy, CmsServer Clients and issues the SNMP Varbinds to the Switch for Addition, Modification and Deletion.
Appendix C Troubleshooting Connection Management Problems Defect Information: • stack trace of the sdbroker process "pstack " • sdbroker and cmgrd logs. Possible alternative workaround—None. C.9.4.2.2 Cmgrd—Sdbroker Addition/Modification/Deletion Errors. Provisioning a Connection Results in an Error "sDatabroker process busy. Please retry" Related key index entries: cmgrd, sdbroker The return error window on the screen states "sDatabroker process busy. Please retry".
Appendix C Troubleshooting Connection Management Problems C.9.4.2.3 Cmgrd—Sdbroker Addition Errors. Adding a Connection Results in an Error "MGM syncup in progress". Related key index entries: cmgrd, sdbroker, sync-up While the system is in the process of syncing up, the user cannot provision connections. The user will be returned the error "MGM syncup in progress" We need to determine if the system is really in syncup or not. If the system is still syncing up then this is proper operation.
Appendix C Troubleshooting Connection Management Problems Defect Information—If the switch and DMD cache are not in sync, we will need the DMD logs and message logs, dmd cache dump and the EM logs for the node in question. We will also need the switch CLI screen shot of the connection in question. Possible alternative workaround—If there is a cache inconsistency, the only work around is a complete cache resync(/opt/svplus/tools/CacheResync).
Appendix C Troubleshooting Connection Management Problems C.9.4.2.6 Cmgrd—Sdbroker Modification/Deletion Errors. Modifying or Deleting a Connection Results in an Error "sDatabroker Could not lock connection entry.". Related key index entries: cmgrd, sdbroker, lock connection During a Connection Modification or Deletion request the above error could result when sdbroker could not find the connection in its cache. All scenarios of modify/delete connection failures display the same error to the user.
Appendix C Troubleshooting Connection Management Problems C.9.4.3.1 Cmgrd—Addition/Modification/Deletion Errors. Provisioning a Connection Results in an Error "Fail due to Switch Timeout" Related key index entries: cmgrd, time-out When any Connection Add/Mod/Del request is made, cmgrd issues a request to the switch with a Snmp community string, either a SET or GET string. These community strings are overwritten by the process snmpcomm.
Appendix C Troubleshooting Connection Management Problems Defect Information: • If after re-issuing the request and still getting the same time-out error than collect the cmgrd.log and snmpcomm .log. • And if after warm-starting the snmpcomm process does not run, then collect the watchdog.log file. Possible alternative workaround—Re-issue the request after some time, this interval could enable snmpcomm to clear its pending requests. Do a warm-start to ensure that the snmpcomm process starts up. C.9.
Appendix C Troubleshooting Connection Management Problems The reason for the error is that cmgrd could not establish and ILOG connection with iosmgr. The following basic check can be done: Step 1 Issue the command "psg iosmgr" to ensure that the process is indeed running. Step 2 Check for iosmgr coredumps in the corefilesdir directory. If it is indeed noticed that iosmgr process is not running, then a warm-start has to be done to ensure that the process does come up.
Appendix C Troubleshooting Connection Management Problems C.9.4.3.6 Cmgrd—Addition/Modification/Deletion Errors. Provisioning a Connection Results in an Error "Can't get segment info from Data-base." Related key index entries: cmgrd, segment info The above error will be returned by cmgrd when it could not get a row from one of the Cisco MGM database tables for the current connection request.
Appendix C Troubleshooting Connection Management Problems C.9.4.4.1 Cmgrd—Addition/Modification Errors. Provisioning a Connection Results in a Switch Error "Agent reported bad/wrong value for one of the variables in the request." Related key index entries: cmgrd, bad value When any Connection Add or Mod request is issued, an SNMP VarBind is SET on the switch via cmgrd. The switch can reject this VarBind with the above error.
Appendix C Troubleshooting Connection Management Problems C.9.4.4.3 Cmgrd—Addition/Modification Errors.
Appendix C Troubleshooting Connection Management Problems C.9.4.4.5 Cmgrd—Addition Errors. Provisioning a Connection Results in a Switch Error "Local Channels not enough." Related key index entries: cmgrd, channels During a connection Addition request it is possible that the user endpoint port or card that the connection is being SET on, has already reached its limit of allowable connections. Check the port or card of the user endpoints on the CLI.
Appendix C Troubleshooting Diagnostics Center Problems C.9.4.4.8 Cmgrd—Modification Errors. Modifying a Connection Results in a Switch Error "Connection does not exist in CproDb/Agent returned no such name" Related key index entries: cmgrd, cprodb During a connection Modification the switch could return the above error when the connection is truly not present on the switch. The user should check the connection in the user_connection table.
Appendix C Troubleshooting Diagnostics Center Problems Port Diagnostics • Retrieve the Port Level Attributes such as Port Status etc. • Perform Loopback. • Perform start/stop/modify BERT • Retrieve the results and/or current status of the BERT • Monitor the Scheduled Grooming Results • Configure the On Demand Grooming • Retrieve the Port Level Real Time Statistics Line Diagnostics • Retrieve the Line Level Attributes such as Line Status, Loopback Status etc.
Appendix C Troubleshooting Diagnostics Center Problems The Diagnostics Server would interface with the CM Server to support the following Connection related Diagnostics Operations: • Connection Loopback • Up Connection • Down Connection • Connection Trace • Test Connection • Test Delay • Test Connection Segment • Test Ping OAM This section includes the following information: • C.10.1 Diagnostics Center Framework • C.10.2 11.2 Diagnostic Server (DCServer) Specific Issues C.10.
Appendix C Troubleshooting Diagnostics Center Problems 3. Collect cmsvr.log file under the /opt/svplus/log directory. 4. Collect DCSserver.log file under the /opt/svplus/log directory. Possible alternative workaround—None C.10.1.2 Cannot Launch Other Applications from Diagnostics Center The Diagnostics Center cannot launch other applications using one of the following methods: Step 1 • Choose the target application under the Tools menu item.
Appendix C Troubleshooting Diagnostics Center Problems 3. Collect screen snapshots. In particular, error/information message dialog boxes. 4. Collect cmsvr.log file under the /opt/svplus/log directory. 5. Collect DCServer.log file under the /opt/svplus/log directory. Possible alternative workaround—None C.10.1.
Appendix C Troubleshooting Diagnostics Center Problems Defect Information—Collect the following information for further analysis: 1. Collect CMSCclient.log file under the D:\Documents and Settings\username\log directory 2. Collect cmsvr.log file under the /opt/svplus/log directory. 3. Collect DCServer.log file under the /opt/svplus/log directory. Possible alternative workaround—None C.10.1.
Appendix C Troubleshooting Diagnostics Center Problems Defect Information—Collect the following information for further analysis: 1. Collect Java DOS Window data: 2. Select the Java DOS box. 3. Issue a 'Ctrl and Break' command. Hold the 'Ctrl' key down and click on the 'Break' (Pause) key. 4. This action should result in the DOS showing Java thread related information. 5. Copy the data to a log file for further analysis. 6. Collect CMSCclient.
Appendix C Troubleshooting Diagnostics Center Problems Step 2 Step 3 Open /opt/svplus/log/DCServer.log file and look for the message information when this error occurred a. A typical message in the log looks like this: ERR: Fatal Error at file, line 0, char 0, Message: An exception occurred! Type:RuntimeException, Message:The primary document entity could not be opened. Id=/opt/svplus/xml/diagcenter/XXX/XXX-XXX.xml ( : ) ERR: InternalError: XML Parsing Error b. If the .
Appendix C Troubleshooting Diagnostics Center Problems Defect Information—Collect the following information for further analysis: • Collect CMSClient.log file under the D:\Documents and Settings\username\log directory. • Collect DCServer.log file under the /opt/svplus/log directory. Possible alternative workaround—None C.10.2.
Appendix C Troubleshooting Diagnostics Center Problems Step 4 Narrow down the problem by selecting one counter at a time and find out for what all counters the polling fails. Defect Information—Collect the following information for further analysis: • Collect the DCServer.log file from /opt/svplus/log directory. • Collect screen snapshots. In particular, error/information message dialog boxes. • CLI output of dspcd for that card. Output of any appropriate CLI commands used.
Appendix C Troubleshooting Diagnostics Center Problems Defect Information—Collect the following information for further analysis: • Collect the DCServer.log file from /opt/svplus/log directory. • Collect screen snapshots. In particular, the DC GUI BERT window, error/information message dialog boxes. Possible alternative workaround—Use CLI/DiagProxy for BERT operations. C.10.2.
Appendix C Troubleshooting Performance Management Collection and Parsing Problems Defect Information—Collect the following information for further analysis: • Collect the DCServer.log and cmsvr.log files from /opt/svplus/log directory. • Collect screen snapshots. In particular, error/information message dialog boxes. Possible alternative workaround—Use CLI/ SNMP Conn Proxy for connection diagnostics. C.10.2.
Appendix C Troubleshooting Performance Management Collection and Parsing Problems • C.11.1.5 PM Collection Fails for the Node - Logfile Shows "Snmp failed" • C.11.1.6 PM Collection Fails for the Node - Logfile Shows "Ftp failed" • C.11.1.
Appendix C Troubleshooting Performance Management Collection and Parsing Problems C.11.1.3 PM Collection Fails for the Node - Logfile Shows "Card not discovered" This can happen when the card is not in the active state.
Appendix C Troubleshooting Performance Management Collection and Parsing Problems Defect Information—Collect the following information for further analysis: • pmcollector.log • Related key index entries • pmcollector, manual snmp results Workaround—If the community strings are different on Cisco MGM and node, lookup troubleshooting for Topology module C.11.1.
Appendix C Troubleshooting Performance Management Collection and Parsing Problems Defect information—Collect the following information for further analysis: • pmcollector.log, dump of node_info and coll_info. • Related key index entries • pmcollector Workaround—Use the atm or lan ip which is reachable. C.11.2 PM Parsing Issues This section includes the following information: • C.11.2.1 StatsParser—Generic Troubleshooting • C.11.2.
Appendix C Troubleshooting Statistics Report Problems C.12 Statistics Report Problems This section includes the following information: • C.12.1 Statistics Report • C.12.2 If You Collected Data and You See No Data Available • C.12.3 If You Generate Report and Don't See Data for a Long Time • C.12.4 You See FDNs for Other Entities When You Generate Report • C.12.5 You See Wrong FDN for Raw Report • C.12.6 The Utilization Report Value Is Greater Than 100% C.12.
Appendix C Troubleshooting Statistics Report Problems C.12.4 You See FDNs for Other Entities When You Generate Report You see FDNs for other entites when you generate reports. For example: When you generate raw report for trunk data for one card, you might see trunk data from different card also. This is because some of the tables doesn't have slot information and hence we get data only with node information Step 1 This is not an error.
Appendix C Troubleshooting Service Agent Problems C.13 Service Agent Problems RtmProxy is the only component in Service agent that is used in Cisco MGM. Service Agent processes user request through SNMP and convey to switch agent and finally return the result to user. This section includes the following information: C.13.1 RtmProxy • C.13.1 RtmProxy RtmProxy is Cisco MGM's northbound SNMP interface to provide traps from all switches to the customer applications.
Appendix C Troubleshooting Service Agent Problems Step 3 Verify that the community string for the snmpset is set to private Step 4 Verify that the mib objects that are being set are correct. The mib objects that should be set for the manager's registration are stratacom.rtm.trapsConfig.trapConfigTable.trapConfigEntry.managerRowStatus mstratacom.rtm.trapsConfig.trapConfigTable.trapConfigEntry.trapFilterRegisterCategory stratacom.rtm.trapsConfig.trapConfigTable.trapConfigEntry.
Appendix C Troubleshooting Service Agent Problems C.13.1.3 Manager Gets Deregistered The Manager keeps getting de-registered from RtmProxy after a while Step 1 Verify that the Keep Alive script is running. The manager will automatically get de-registered if no snmp is done on any of the tables in RtmProxy.
Appendix C Troubleshooting Audit Trail Log Problems C.14 Audit Trail Log Problems This section includes the following information: • C.14.1 Audit Trail Logging Mechanism C.14.1 Audit Trail Logging Mechanism This provides Cisco MGM with the ability to record user activities across different modules in a persistent file. All Cisco MGM Java front GUI application will send the information of user activities to Audit Logger server via CORBA interface.
Appendix C Troubleshooting Miscellaneous Problems Step 3 Check if any CORBA related exception thrown on the console. a. If so, collect those error messages and/or call stacks. Defect Information—Collect the following information for further analysis: • Collect all, complete screen snapshots of the Cisco MGM GUI. • Collect all the errors/exceptions thrown on the console, if any. • Collect log: /opt/svplus/log/AuditLogger.log*, /opt/svplus/log/LogServer.log*, AuditTrail*.
Appendix C Troubleshooting Miscellaneous Problems Step 3 Check the Trap Manager List on the switch. SSH or Telnet to the switch. Run "dsptrapmgr" command to show the trap manager list. Check whether the Cisco MGM is in the table. If so, go to Step. 4. Otherwise, if the table is already full, remove unwanted entries with "deltrapmgr" command. The NTS should be able to register the Cisco MGM into the table within a few minutes. If not, go to Step. 4. Step 4 Check the SNMP community strings.
Appendix C Troubleshooting Miscellaneous Problems In normal case, you see the following cluster for each trap in NTS log.
Appendix C Troubleshooting Miscellaneous Problems This section will give a list of steps to try to determine more precisely the cause of the inconsistency. These steps should be performed in order. Step 1 Step 2 1. Verify Node's Sync States 2. Isolate via Database Query 3. Isolate via Message Flow One common reason for inconsistency is nodes in a non-ok state after startup. This will result in connection counts being incorrect or the presence of incomplete connections. a.
Appendix C Troubleshooting Miscellaneous Problems Find the dmd on interest by using the command /opt/svplus/dbcmap -d the output will provide you with the dmd whose logs need to be queried. grep "node slot .* port .
Appendix C Troubleshooting Miscellaneous Problems b. If the DMD received the message but it is not reflected in the database. Identify which databroker module dropped the ball. First check the DMD to see if it forwarded the message. If it didn't check for the reason. The format may be wrong etc. one easy search/grep is node/slot/port/vpi/vci. This is output every time a cache query is done. grep "DROP MSG: validation error" dmd..* - prints out dropped messages. c.
Appendix C Troubleshooting Miscellaneous Problems Defect Information: See C.15.2.1 Connection Inconsistency Between the Switch and GUI . Possible alternative workaround—See C.15.2.1 Connection Inconsistency Between the Switch and GUI Related key index entries: inconsistency, connection C.15.2.3 Inconsistent Connection Secondary Status The GUI display of 'Secondary Status' is from the 'Secondary_status' field of the user_connection table.
Appendix C Troubleshooting Miscellaneous Problems a. select num_segs, status, inseg_tbl_1, inseg_tbl_2, inseg_tbl_3 from user_connection where l_node_id = x and l_slot=y and l_port=z and l_subchnl_1 = v and l_subchnl_2 = w. Defect Information—We need the logs of the processes on both sides of the interface which the message was dropped. A dump of the specific user_connection table entry that is incorrect is also useful.
Appendix C Troubleshooting Miscellaneous Problems • Check the free disk space. df -k /opt/svplus • Check whether target switch/MGM is reachable. • Check for debug level. If logs are not giving detailed information, debug level can be increased by editing ~svplus/config/cwmftpd.conf. • Set config parameter, LOG_LEVEL, to 7 to get detailed logs. Related key index entries: ftp C.15.3.
Appendix C Troubleshooting Miscellaneous Problems Defect Information—If file is available, but file is not ftp'd and FTPERR_550 exception is thrown, then collect cwmftpd.log, cwmftpd.request_log and logs of the process for which files are not getting transferred by cwmftpd and report the problem. Possible alternative workaround—None Related key index entries: file unavailable, ftperr_550, requested action not taken. C.15.3.6 FTP Sessions in Switch Switch allows only four ftp sessions.
Appendix C Troubleshooting Miscellaneous Problems Possible alternative workaround—None Related key index entries: service not available, closing control connection, 421, session limit reached, ftperr_421 C.15.3.8 499 Session Limit Reached For SWSW MGX8850 Release 4 and later, switch will respond with "499 Session limit reached, queuing key ", when it reached the limitation of four ftp sessions.
Appendix C Troubleshooting Miscellaneous Problems C.15.3.10 Failed to Acquire Session After All Retries cwmftpd failed to acquire a session with switch with all retries. Step 1 Check whether really all four sessions are opened by opening a manual FTP session to switch. Step 2 Check whether it succeeds. Defect Information—If manually opening the FTP session succeeds, but still cwmftpd throws SESSION_FAIL exception, then report the problem with cwmftpd.log, cwmftpd.
Appendix C Troubleshooting Miscellaneous Problems Cisco Media Gateway Manager 5.
A P P E N D I X D Statistics Summary This appendix defines the statistics that are collected from the following nodes: • Cisco MGX 8880 PXM45-based • Cisco MGX 8850 PXM45-based D.1 Data Transmission Process Overview details how data travels through two cards that are connected across the bus. The statistics are categorized under a major grouping known by an object type name and organized by the subobject type number. Within the subtype, each statistic contains a statistic type number.
Appendix D Statistics Summary Data Transmission Process Overview D.1 Data Transmission Process Overview Statistics are collected at different points during data transmission. Figure 1 shows how data travels through two cards that are connected across the bus.
Appendix D Statistics Summary Connection Statistics D.1 Connection Statistics The following connection statistics are applicable: • D.1.1 AXSM Connection • D.1.2 AXSM-E Connection • D.1.3 VXSM ATM Connection Statistics D.1.1 AXSM Connection This section provides information about the statistics contained in the AXSM_ATM_conn group. This group contains statistics that are applicable AXSM card on the Cisco MGX 8850 PXM45-based switch.
Appendix D Statistics Summary Connection Statistics Table D-2 AXSM Connection Statistics—Descriptions (continued) Stat ID AXSM Connection Statistics 2 Ingress CLP0 cells discarded Subset of Other Statistics Ingress/Egress Measurement Point Ingress CLP0+1 cells discarded Ingress–2, 8 Description Provides a count of the ingress cells with CLP equal to 0 that are discarded due to policing.
Appendix D Statistics Summary Connection Statistics D.1.2 AXSM-E Connection This section provides information about the statistics contained in the AXSME_ATM_conn group. The AXSM-E connection statistics in this group are applicable to the Cisco MGX 8850 PXM45-based switch. Table D-3 lists the attributes that are common to the AXSM-E connection statistics.
Appendix D Statistics Summary Connection Statistics Table D-4 AXSM-E Connection Statistics—Descriptions (continued) Stat ID AXSM-E Connection Statistics Subset of Other Ingress/Egress Statistics Measurement Point 5 CLP0 cells from port No Ingress–1 Description Provides a count of the cells with CLP equal to 0. These cells are received from the port before policing. Range: 0 to (240–1) cells 6 CLP1 cells from port No Ingress–1 Provides a count of the cells with CLP equal to 1.
Appendix D Statistics Summary Connection Statistics Table D-4 AXSM-E Connection Statistics—Descriptions (continued) Stat ID AXSM-E Connection Statistics Subset of Other Ingress/Egress Statistics Measurement Point 30 Egress CLP0 cells discarded in qe No Description Egress–13 Provides a count of the cells with CLP equal to 0 that are discarded due to an overflow in the queuing engine.
Appendix D Statistics Summary Service Line Statistics Table D-6 VXSM ATM Connection Statistics—Descriptions (continued) Stat ID VXSM ATM Connection Statistics Subset of Other Statistics Ingress/Egress Measurement Point 3 EFCI=1 CLP0 cells from the port — Ingress Description Provides a count of the CLP0 cells with the explicit forward congestion indication (EFCI) equal to 1. These cells are received from the port.
Appendix D Statistics Summary Service Line Statistics D.2.1 CESM, FRSM, SRM, and SRME T3/E3 Service This section provides information about the statistics contained in the MGX-T3/E3 group. The CESM, FRSM, SRM, and SRME T3/E3 service line statistics are applicable to the Cisco MGX 8230, Cisco MGX 8250, Cisco MGX 8850 PXM1-based nodes. Table D-7 lists the attributes that are common to all of the CESM, FRSM, SRM, and SRME T3/E3 service line statistics.
Appendix D Statistics Summary Service Line Statistics Table D-8 CESM, FRSM, SRM, and SRME T3/E3 Service Line Statistics—Descriptions (continued) Stat ID CESM, FRSM, SRM, and SRME Subset of Other Ingress/Egress T3/E3 Service Line Statistics Statistics Measurement Point 29 Line Errored Seconds No Ingress–1 Description Provides a count of the line code violation errored seconds that occur within the collection interval.
Appendix D Statistics Summary Service Line Statistics Table D-8 CESM, FRSM, SRM, and SRME T3/E3 Service Line Statistics—Descriptions (continued) Stat ID CESM, FRSM, SRM, and SRME Subset of Other Ingress/Egress T3/E3 Service Line Statistics Statistics Measurement Point 39 Unavailable Seconds No Ingress–1 Description Provides a count of the unavailable seconds that occur within the collection interval.
Appendix D Statistics Summary Service Line Statistics Table D-8 CESM, FRSM, SRM, and SRME T3/E3 Service Line Statistics—Descriptions (continued) Stat ID CESM, FRSM, SRM, and SRME Subset of Other Ingress/Egress T3/E3 Service Line Statistics Statistics Measurement Point 227 PLCP HCS Errors No Ingress–1 Description Provides a count of the cell header checksum errors that are encountered by the PLCP interface.
Appendix D Statistics Summary Service Line Statistics D.2.2 SRM and SRME SONET Service Line This section provides information about the statistics contained in the SONET group. The SONET line statistics are applicable to the SRM and SRME cards on the Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 PXM1-based nodes. Table D-9 lists the attributes that are common to all of the SONET line statistics.
Appendix D Statistics Summary Service Line Statistics Table D-10 SRM and SRME SONET Line Statistics—Descriptions (continued) Stat ID SRM and SRME SONET Line Statistics Subset of Other Statistics Ingress/Egress Measurement Point 240 Sonet Line Alarm indication signal — — Description Provides a count of the times that an alarm indication signal is detected on the line.
Appendix D Statistics Summary Service Line Statistics Table D-12 Stat ID 0 AXSM Line Statistics—Descriptions AXSM Line Statistics Subset of Other Statistics Ingress/Egress Measurement Point Ingress CLP0 Cells From Port Ingress CLP0+1 Ingress–2, 8 Cells Description Provides a count of the ingress cells with cell loss priority (CLP) equal to 0 that are received.
Appendix D Statistics Summary Service Line Statistics Table D-12 AXSM Line Statistics—Descriptions (continued) Stat ID AXSM Line Statistics Subset of Other Statistics Ingress/Egress Measurement Point 9 Ingress non-zero GFC cells No Ingress–2, 8 Description Provides a count of the cells with a non-zero generic flow control (GFC) field. This statistic is applicable only for UNI and ingress directions.
Appendix D Statistics Summary Service Line Statistics Table D-12 Stat ID 20 AXSM Line Statistics—Descriptions (continued) AXSM Line Statistics Egress OAM/RM Errored Cells Subset of Other Statistics Ingress/Egress Measurement Point No Egress–7, 13 Description Provides a count of the errored OAM and RM cells in the egress direction.
Appendix D Statistics Summary Service Line Statistics Table D-14 Stat ID 0 AXSM-E Line Statistics—Descriptions AXSM-E Line Statistics Ingress CLP0 cells received Subset of Other Ingress/Egress Statistics Measurement Point Cells received Ingress–1 Description Provides a count of the ingress cells with cell loss priority (CLP) equal to 0 that are received.
Appendix D Statistics Summary Port Statistics Table D-14 Stat ID 10 AXSM-E Line Statistics—Descriptions (continued) AXSM-E Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point Description Egress valid RM cells received Cells transmitted Provides a count of the RM cells that are received at the port in the egress direction.
Appendix D Statistics Summary Port Statistics Table D-15 Attributes Common to all AXSM Port Statistics Object Attribute Front Cards MGX-AXSM-16-T3E3, MGX-AXSM-16-155, MGX-AXSM-4-622, MGX-AXSM-1-2488 Back Cards MGX-SMB-8-T3, MGX-SMB-8-E3, MGX-SMB-4-155, MGX-SMFIR-8-155, MGX-SMFLR-8-155, MGX-MMF-8-155, MGX-SMFLR-2-622, MGX-SMFIR-2-622, MGX-SMFSR-1-2488, MGX-SMFLR-1-2488, MGX-SMFXLR-1-2488 Object Type 3 Subobject Type 9 Default Peak Interval 300 seconds The AXSM port statistics are used primar
Appendix D Statistics Summary Port Statistics Table D-16 Stat ID 5 AXSM Port Statistics—Descriptions (continued) AXSM Port Statistics Ingress CLP1 Cells to backplane Subset of Other Statistics Ingress/Egress Measurement Point No Ingress–3, 9 Description Provides a count of the cells with CLP equal to 1 that travel from the queueing engine to the bus.
Appendix D Statistics Summary Port Statistics D.3.2 AXSM-E Port This section provides information about the statistics contained in the AXSME_ATM_port group. The AXSM-E port statistics in this group are applicable to the Cisco MGX 8850 PXM45-based switch. Table D-17 lists the attributes that are common to the AXSM-E port statistics.
Appendix D Statistics Summary Port Statistics Table D-18 AXSM-E Port Statistics—Descriptions (continued) Stat ID AXSM-E Port Statistics Subset of Other Ingress/Egress Statistics Measurement Point 4 CLP0 cells not discarded No Egress Description Provides a count of the cells with CLP equal to 0 that are received at the port. Range: 0 to (240–1) cells 5 CLP1 cells not discarded No Egress Provides a count of the cells with CLP equal to 1 that are received at the port.
Appendix D Statistics Summary Port Statistics Table D-18 Stat ID 16 AXSM-E Port Statistics—Descriptions (continued) AXSM-E Port Statistics Cells discarded by Qbin 1 Subset of Other Ingress/Egress Statistics Measurement Point — — Description Provides a count of the cells that are discarded on Qbin 1. Range: 0 to (240–1) cells 17 Cells transmitted by Qbin 1 — — Provides a count of the cells that are transmitted by Qbin 1.
Appendix D Statistics Summary Port Statistics Table D-18 Stat ID 29 AXSM-E Port Statistics—Descriptions (continued) AXSM-E Port Statistics Cells transmitted by Qbin 5 Subset of Other Ingress/Egress Statistics Measurement Point — — Description Provides a count of the cells that are transmitted by Qbin 5. Range: 0 to (240–1) cells 30 Cells received by Qbin 6 — — Provides a count of the cells that are received on Qbin 6.
Appendix D Statistics Summary Port Statistics Table D-18 AXSM-E Port Statistics—Descriptions (continued) Stat ID AXSM-E Port Statistics Subset of Other Ingress/Egress Statistics Measurement Point 42 Cells received by Qbin10 — — Description Provides a count of the cells that are received on Qbin 10. Range: 0 to (240–1) cells 43 Cells discarded by Qbin10 — — Provides a count of the cells that are discarded on Qbin 10.
Appendix D Statistics Summary Port Statistics Table D-18 AXSM-E Port Statistics—Descriptions (continued) Stat ID AXSM-E Port Statistics Subset of Other Ingress/Egress Statistics Measurement Point 51 Cells received by Qbin13 — — Description Provides a count of the cells that are received on Qbin 13. If Qbin 13 is not assigned a traffic service, the count returns a value of 0. Range: 0 to (240–1) cells 52 Cells discarded by Qbin13 — — Provides a count of the cells that are discarded on Qbin 13.
Appendix D Statistics Summary Port Statistics Table D-18 Stat ID 58 AXSM-E Port Statistics—Descriptions (continued) AXSM-E Port Statistics Cells discarded by Qbin15 Subset of Other Ingress/Egress Statistics Measurement Point — — Description Provides a count of the cells that are discarded on Qbin 15. If Qbin 15 is not assigned a traffic service, the count returns a value of 0.
Appendix D Statistics Summary Port Statistics Table D-18 Stat ID 70 AXSM-E Port Statistics—Descriptions (continued) AXSM-E Port Statistics RM cells received (Ingress) Subset of Other Ingress/Egress Statistics Measurement Point No Ingress–1 Description Provides a count of the RM cells that are received at the port.
Appendix D Statistics Summary Card Statistics Table D-20 Stat ID 0 VXSM Port Statistics—Descriptions VXSM Port Statistics Ingress CLP0 cells transmitted Subset of Other Statistics Ingress/Egress Measurement Point — Ingress Description Provides a count of the ingress cells with CLP equal to 0 that are transmitted. Range: 0 to (2 64–1) 1 Ingress CLP1 cells transmitted — Ingress Provides a count of the ingress cells with CLP equal to 1 that are transmitted.
Appendix D Statistics Summary Card Statistics Table D-21 Attributes Common to all AXSM Card Statistics Object Attribute Front Cards MGX-AXSM-16-T3E3, MGX-AXSM-16-155, MGX-AXSM-4-622, MGX-AXSM-1-2488 Back Cards MGX-SMB-8-T3, MGX-SMB-8-E3, MGX-SMB-4-155, MGX-SMFIR-8-155, MGX-SMFLR-8-155, MGX-MMF-8-155, MGX-SMFLR-2-622, MGX-SMFIR-2-622, MGX-SMFSR-1-2488, MGX-SMFLR-1-2488, MGX-SMFXLR-1-2488 Object Type 4 Subobject Type 0 Default Peak Interval 300 seconds The AXSM card statistics are used primari
Appendix D Statistics Summary Path Statistics Table D-22 AXSM Card Statistics—Descriptions (continued) Stat ID AXSM Card Statistics Subset of Other Statistics Ingress/Egress Measurement Point 5 Undefined Cells from port No Ingress–3, 9 Egress–6, 12 Description Provides a count of the undefined cells from the queuing engine. An undefined cell can be routed, but it might not be discarded.
Appendix D Statistics Summary Path Statistics Table D-23 Attributes Common to all VXSM Path Statistics Object Attribute Front Card VXSM Back Card VXSM-BC-4-155 Object Type 6 Subobject Type 2 Default Peak Interval 300 seconds Table D-24 includes the description of each statistic.
Appendix D Statistics Summary Path Statistics D.5.2 VXSM DS3 Path Statistics This section provides information about the statistics contained in the VXSM_DS3 Path group. The VXSM DS3 path statistics are applicable to the VXSM cards on the Cisco MGX 8880 PXM45-based nodes and the Cisco MGX 8850 PXM45-based nodes. Table D-25 lists the attributes that are common to all of the VXSM DS3 path statistics.
Appendix D Statistics Summary Path Statistics Table D-26 VXSM DS3 Path Statistics—Descriptions (continued) Stat ID VXSM DS3 Path Statistics Subset of Other Statistics 6 P-bit Errored Seconds for Path — Ingress/Egress Measurement Point — Description Provides a count of the errored seconds (ES) for the DS3 path. Range: 0 to (2 64–1) 7 C-bit Errored Seconds for Path — — Provides a count of the errored seconds (ES) for the DS3 path.
Appendix D Statistics Summary Path Statistics Table D-28 VXSM DS1 N DS3 Path Statistics—Descriptions Stat ID VXSM DS1 N DS3 Path Statistics Subset of Other Statistics Ingress/Egress Measurement Point 0 Errored Seconds for Path — — Description Provides a count of the errored seconds (ES) for the DS1 path. Range: 0 to (2 64–1) 1 Severely errored seconds for path — — Provides a count of the severely errored seconds (SES) for the DS1 path.
Appendix D Statistics Summary Path Statistics Table D-28 VXSM DS1 N DS3 Path Statistics—Descriptions (continued) Stat ID VXSM DS1 N DS3 Path Statistics Subset of Other Statistics 11 Errored seconds for DS1 path — at far end Ingress/Egress Measurement Point — Description Provides a count of the ES for the DS1 path at the far end. Range: 0 to (2 64–1) 12 Severely errored seconds for DS1 path at far end — — Provides a count of the SES for the DS1 path at the far end.
Appendix D Statistics Summary Path Statistics Table D-28 VXSM DS1 N DS3 Path Statistics—Descriptions (continued) Stat ID VXSM DS1 N DS3 Path Statistics Subset of Other Statistics Ingress/Egress Measurement Point 22 Degraded Minutes — — Description Provides a count of the degraded minutes (60-second periods where the cumulative errors exceed 1E-6 but does not exceed 1E-3) for the DS1 path.
Appendix D Statistics Summary Path Statistics Table D-30 VXSM DS1 VT Path Statistics—Descriptions Stat ID VXSM DS1 VT Path Statistics Subset of Other Statistics Ingress/Egress Measurement Point 0 Errored Seconds for Path — — Description Provides a count of the errored seconds (ES) for the DS1 path. Range: 0 to (2 64–1) 1 Severely errored seconds for path — — Provides a count of the severely errored seconds (SES) for the DS1 path.
Appendix D Statistics Summary Path Statistics Table D-30 Stat ID 11 VXSM DS1 VT Path Statistics—Descriptions (continued) VXSM DS1 VT Path Statistics Subset of Other Statistics Errored seconds for DS1 path — at far end Ingress/Egress Measurement Point — Description Provides a count of the ES for the DS1 path at the far end. Range: 0 to (2 64–1) 12 Severely errored seconds for DS1 path at far end — — Provides a count of the SES for the DS1 path at the far end.
Appendix D Statistics Summary PNNI Network Statistics Table D-30 VXSM DS1 VT Path Statistics—Descriptions (continued) Stat ID VXSM DS1 VT Path Statistics Subset of Other Statistics Ingress/Egress Measurement Point 22 Degraded Minutes — — Description Provides a count of the degraded minutes (60-second periods where the cumulative errors exceed 1E-6 but does not exceed 1E-3) for the DS1 path.
Appendix D Statistics Summary PNNI Network Statistics The PNNI node statistics are used for gathering information about SPVCs and SPVPs. Note To collect PNNI SPVC and SPVP statistics in Cisco MGM, first enable the statistics on the switch by executing the CLI command cnfpnstat. Table D-32 includes the description of each statistic and the point during the data flow at which the statistic gathers the appropriate information. Each measurement point refers to the corresponding point in Figure 1.
Appendix D Statistics Summary Protocol Statistics Table D-34 PNNI Port Statistics—Descriptions Stat ID PNNI Port Statistics Subset of Other Statistics Ingress/Egress Measurement Point 0 Con success at orig node — — Provides a count of the successful connections at the originating node. 1 Con failed at orig node — — Provides a count of the failed connections at the originating node. 2 Received crankback at orig node — — Provides a count of the crankbacks at the originating node.
Appendix D Statistics Summary Protocol Statistics Table D-35 Attributes Common to all VXSM Card Statistics (continued) Object Attribute Object Type 8 Subobject Type 0 Default Peak Interval 300 seconds Table D-36 includes the VXSM megaco statistics. Table D-36 VXSM Megaco Path Statistics—Descriptions Stat ID VXSM Megaco Statistics Subset of Other Statistics Ingress/Egress Measurement Point Description 0 Total messages received — — Provides a count of the total ingress cells.
Appendix D Statistics Summary Protocol Statistics Table D-36 Stat ID 9 VXSM Megaco Path Statistics—Descriptions (continued) VXSM Megaco Statistics Total successful MOVE commands Subset of Other Statistics Ingress/Egress Measurement Point — — Description Provides a count of the total number of MOVE commands that were successful. Range: 0 to (2 64–1) 11 Total failed MODIFY commands — — Provides a count of the total number of MODIFY commands that have failed.
Appendix D Statistics Summary Protocol Statistics Table D-36 Stat ID 20 VXSM Megaco Path Statistics—Descriptions (continued) VXSM Megaco Statistics Total failed Service Change commands from the MGC to the MG Subset of Other Statistics Ingress/Egress Measurement Point — — Description Provides a count of the total number of Service Change commands from the MGC to the MG that failed in the MGC.
Appendix D Statistics Summary Protocol Statistics Table D-38 Stat ID 0 VXSM Megaco Physical Termination Protocol Statistics—Descriptions VXSM Megaco Physical Termination Protocol Statistics Total physical termination ADD commands Subset of Other Statistics Ingress/Egress Measurement Point — — Description Provides a count of the total number of ADD commands that have been initiated.
Appendix D Statistics Summary Protocol Statistics Table D-40 Stat ID 0 VXSM Megaco Ephemeral Termination Protocol Statistics—Descriptions VXSM Megaco Ephemeral Termination Protocol Statistics Total ephemeral termination ADD commands Subset of Other Statistics Ingress/Egress Measurement Point — — Description Provides a count of the total number of ADD commands that have been initiated.
Appendix D Statistics Summary Protocol Statistics Table D-42 VXSM LAPD Protocol Statistics—Descriptions (continued) Stat ID VXSM LAPD Protocol Statistics Subset of Other Statistics Ingress/Egress Measurement Point 3 Total receiver ready frames transmitted — — Description Provides a count of the total number of receiver ready frames transmitted. Range: 0 to (2 64–1) 4 Total receiver not ready frames — received — Provides a count of the total number of receiver not ready frames received.
Appendix D Statistics Summary Physical Line Statistics Table D-42 VXSM LAPD Protocol Statistics—Descriptions (continued) Stat ID VXSM LAPD Protocol Statistics Subset of Other Statistics Ingress/Egress Measurement Point 15 Total frame reject frames transmitted — — Description Provides a count of the total number of frame reject frames transmitted. Range: 0 to (2 64–1) 16 Total exchange ID frames received — — Provides a count of the total number of exchange ID frames received.
Appendix D Statistics Summary Physical Line Statistics D.8.1 AXSM-E T1/E1 Physical Line This section provides information about the statistics contained in the AXSME_Phyline_T1E1 group. The AXSM-E T1/E1 physical line statistics in this group are applicable to the Cisco MGX 8850 PXM45-based switch. Table D-43 lists the attributes that are common to the AXSM-E T1/E1 physical line statistics.
Appendix D Statistics Summary Physical Line Statistics Table D-44 AXSM-E T1/E1 Physical Line Statistics—Descriptions (continued) Stat ID AXSM-E T1/E1 Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point 3 Unavailable Seconds No Ingress–1 Description Provides a count of the unavailable seconds on the T1/E1 line. Unavailable seconds are defined as 10 contiguous severely errored seconds.
Appendix D Statistics Summary Physical Line Statistics Table D-44 AXSM-E T1/E1 Physical Line Statistics—Descriptions (continued) Stat ID AXSM-E T1/E1 Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point 12 Far-end severely Errored Seconds — — Description Provides a count of the far end SES that occur within the collection interval. Severely errored seconds are classified as errored seconds that are greater than the total line bits per second multiplied by 10-6.
Appendix D Statistics Summary Physical Line Statistics Table D-45 Attributes Common to all AXSM-E T3/E3 Physical Line Statistics (continued) Object Attribute Subobject Type 4 Allowable Peak Intervals 60 seconds, 300 seconds Default Peak Interval 300 seconds The AXSM-E T3/E3 physical line statistics are used primarily for gathering troubleshooting and performance data.
Appendix D Statistics Summary Physical Line Statistics Table D-46 AXSM-E T3/E3 Physical Line Statistics—Descriptions (continued) Stat ID AXSM-E T3/E3 Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point 7 Far end blocked errors No Ingress–1 Description Provides a count of the far end block errors that occur within the collection interval on the T3 line.
Appendix D Statistics Summary Physical Line Statistics Table D-46 AXSM-E T3/E3 Physical Line Statistics—Descriptions (continued) Stat ID AXSM-E T3/E3 Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point 18 PLCP bip 8-errors No Ingress–1 Description Provides a count of the PLCP BIP-8 errors on the T3 line.
Appendix D Statistics Summary Physical Line Statistics Table D-46 AXSM-E T3/E3 Physical Line Statistics—Descriptions (continued) Stat ID AXSM-E T3/E3 Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point 29 Occurrences of loss of cell No delineation Ingress–1 Description Provides a count of the loss of cell delineation defect states on the T3 line.
Appendix D Statistics Summary Physical Line Statistics Table D-46 AXSM-E T3/E3 Physical Line Statistics—Descriptions (continued) Stat ID AXSM-E T3/E3 Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point 57 Seconds with at least one LCV + number of LOS No Ingress–1 Description Provides a count of the seconds with at least one line code violation (LCV) and one loss of signal (LOS) on the E3 line.
Appendix D Statistics Summary Physical Line Statistics Table D-46 AXSM-E T3/E3 Physical Line Statistics—Descriptions (continued) Stat ID AXSM-E T3/E3 Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point Description 66 Far end severely errored seconds Far end errored Ingress–1 seconds Provides a count of the severely errored seconds (SES) that occur at the far end of the E3 line.
Appendix D Statistics Summary Physical Line Statistics Table D-48 AXSM-E SONET Physical Line Statistics—Descriptions Stat ID AXSM-E SONET Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point 0 LOS defect state occurrences No Ingress–1 Description Provides a count of the times a loss of signal (LOS) is detected on the SONET line. The count includes the number of LOS alarms.
Appendix D Statistics Summary Physical Line Statistics Table D-48 AXSM-E SONET Physical Line Statistics—Descriptions (continued) Stat ID AXSM-E SONET Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point 12 Aps_chan_mis No Ingress–1 Description Provides a count of the APS channel mismatches that are detected on the SONET line. Range: 0 to (240–1) cells 13 Aps_mode_mis No Ingress–1 Provides a count of the APS mode mismatches that are detected on the SONET line.
Appendix D Statistics Summary Physical Line Statistics Table D-48 AXSM-E SONET Physical Line Statistics—Descriptions (continued) Stat ID AXSM-E SONET Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point 21 Severely errored seconds for line No Ingress–1 Description Provides a count of the severely errored seconds that occur within the collection interval on the SONET line.
Appendix D Statistics Summary Physical Line Statistics Table D-48 AXSM-E SONET Physical Line Statistics—Descriptions (continued) Stat ID AXSM-E SONET Physical Line Statistics Subset of Other Ingress/Egress Statistics Measurement Point 30 Unavailable seconds for path No Ingress–1 Description Provides a count of the path unavailable seconds for the line. Unavailable seconds are defined as 10 contiguous severely errored seconds.
Appendix D Statistics Summary Physical Line Statistics Table D-50 includes the VXSM SONET physical line statistics. Table D-50 VXSM SONET Physical Line Statistics—Descriptions Stat ID VXSM SONET Physical Line Statistics Subset of Other Statistics Ingress/Egress Measurement Point 0 LOS defect state occurrences — — Description Provides a count of the times a loss of signal (LOS) is detected.
Appendix D Statistics Summary Physical Line Statistics Table D-50 VXSM SONET Physical Line Statistics—Descriptions (continued) Stat ID VXSM SONET Physical Line Statistics Subset of Other Statistics Ingress/Egress Measurement Point 12 Severely Errored seconds for section — — Description Provides a count of the severely errored seconds (SES) for the section. Range: 0 to (2 64–1) 13 Unavailable seconds for section — — Provides a count of the unavailable seconds for the section.
Appendix D Statistics Summary Physical Line Statistics Table D-52 VXSM T1/E1 Physical Line Statistics—Descriptions Stat ID VXSM T1/E1 Physical Line Statistics Subset of Other Statistics Ingress/Egress Measurement Point 0 Errored Seconds — — Description Provides a count of the line code violation errored seconds. Range: 0 to (2 32–1) 1 Severely Errored Seconds — — Provides a count of the near end severely errored seconds (SES) that occur within the collection interval.
Appendix D Statistics Summary Physical Line Statistics Table D-52 VXSM T1/E1 Physical Line Statistics—Descriptions (continued) Stat ID VXSM T1/E1 Physical Line Statistics Subset of Other Statistics Ingress/Egress Measurement Point 8 Far-end severely Errored Seconds — — Description Provides a count of the far end SES that occur within the collection interval. Severely errored seconds are classified as errored seconds that are greater than the total line bits per second multiplied by 10-6.
Appendix D Statistics Summary Physical Line Statistics Table D-52 VXSM T1/E1 Physical Line Statistics—Descriptions (continued) Stat ID VXSM T1/E1 Physical Line Statistics Subset of Other Statistics Ingress/Egress Measurement Point 15 Bursty Errored Seconds — — Description Provides a count of the bursty errored seconds (BES). Range: 0 to (2 64–1) 16 Controlled Slip Seconds — — Provides a count of the controlled slip seconds (CSS).
A P P E N D I X E Real-Time Counters Real-time counters (RTCs) are available through the Diagnostics Center. When the GUI displays the RTCs, the applicability rules would be evaluated by the Cisco MGM server, and the counters will appear in the GUI only if the counters are applicable for the selected entity. This appendix includes the following information: • E.1 AXSM-Card—Supported Real-Time Counters • E.2 AXSM-DS1-Line—Supported Real-Time Counters • E.
Appendix E Real-Time Counters AXSM-Card—Supported Real-Time Counters • E.25 Common/Card-RudpSession—Supported Real-Time Counters • E.26 Common/Card-SrcpPeer—Supported Real-Time Counters • E.27 Common/Card-XgcpPeer—Supported Real-Time Counters • E.28 VISM-Card—Supported Real-Time Counters • E.29 VISM-DS1-Line—Supported Real-Time Counters • E.30 VISM-EndPoint-Connection—Supported Real-Time Counters • E.31 VISM-VirtualPort—Supported Real-Time Counters • E.
Appendix E Real-Time Counters AXSM-DS1-Line—Supported Real-Time Counters Table E-1 ATM Cell Layer Counters—cellLayer EQ true Applicability Counter Name MIB Object Name Description All Versions CLP0 Cells (Ingress) caclInRcvCLP0Cells The number of cells received on the interface with CLP0 bit set. All Versions CLP1 Cells (Ingress) caclInRcvCLP1Cells The number of cells received on the interface with CLP1 bit set.
Appendix E Real-Time Counters AXSM-DS1-Line—Supported Real-Time Counters Table E-2 Line Current Counters Applicability Counter Name MIB Object Name Description All Versions ESs dsx1CurrentESs The number of Errored Seconds. All Versions SESs dsx1CurrentSESs The number of Severely Errored Seconds. All Versions SEFSs dsx1CurrentSEFSs The number of Severely Errored Framing Seconds. All Versions UASs dsx1CurrentUASs The number of Unavailable Seconds.
Appendix E Real-Time Counters AXSM-DS3-Line—Supported Real-Time Counters Table E-3 Line Alarm Statistics—cardFamily EQ VXSM Applicability Counter Name MIB Object Name Description All Versions LOS Count cds1LOSCounts The number of times the Loss Of Signal defect was detected with or without integrating to LOS alarm. All Versions OOF Count cds1OOFCounts The number of times the Out of Frame (OOF) was detected with or without integrating to OOF alarm.
Appendix E Real-Time Counters AXSM-DS3-Line—Supported Real-Time Counters Table E-4 ATM Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Err OAM Cells (Egress) caclOutErrOAMCells The number of errored OAM cells received by the interface from the switch fabric. All Versions Corrected HecErr Cells (Ingress) caclInHecErrCorrectedCells The number of received cells which had HEC errors that were corrected.
Appendix E Real-Time Counters AXSM-DS3-Line—Supported Real-Time Counters Table E-5 Line Current Counters (continued) Applicability Counter Name MIB Object Name Description cardFamily not equal to AXSMXG SEFSs dsx3CurrentSEFSs The counter associated with the number of Severely Errored Framing Seconds. All Versions UASs dsx3CurrentUASs The counter associated with the number of Unavailable Seconds.
Appendix E Real-Time Counters AXSM-DS3-Line—Supported Real-Time Counters Table E-5 Line Current Counters (continued) Applicability Counter Name MIB Object Name Description cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM OR cardFamily EQ FRSM12 CCVs (Far End) dsx3FarEndCurrentCCVs The counter associated with the number of Far End C-bit Coding Violations reported via the far end block error count.
Appendix E Real-Time Counters AXSM-DS3-Line—Supported Real-Time Counters Table E-6 Line Current 24 Hour Counters—cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM OR cardFamily EQ FRSM12 (continued) Applicability Counter Name MIB Object Name Description All Versions UASs cds3UASCurrent24Hr The number of UASs encountered by the line since the start of current 24 hour period.
Appendix E Real-Time Counters AXSM-DS3-Line—Supported Real-Time Counters Table E-7 Line Alarm Statistics (continued) Applicability Counter Name MIB Object Name Description cardFamily not equal to AXSME AND cardFamily not equal to AXSMXG AND cardFamily not equal to PXM1E AND cardFamily not equal to MPSM FE Count cds3FECount The number of Framing Errors encountered by a T3/E3 interface.
Appendix E Real-Time Counters AXSM-DS3-Line—Supported Real-Time Counters Table E-7 Line Alarm Statistics (continued) Applicability Counter Name MIB Object Name Description CPE Count cardFamily not equal to AXSM AND cardFamily not equal to AXSME AND cardFamily not equal to AXSMXG AND cardFamily not equal to PXM1E AND cardFamily not equal to MPSM cds3CPECount The number of C-bit parity errors(CPERR) on a DS3 interface. This value is calculated over noninformation bits in the DS3 frame.
Appendix E Real-Time Counters AXSM-DS3-Line—Supported Real-Time Counters Table E-8 PLCP Counters—cardFcType not equal to 160 (continued) Applicability Counter Name MIB Object Name Description All Versions CurrentBIP-8ES cds3PlcpBip8ESCurrent The number of BIP-8 Errored Seconds(ES) encountered by the line in the current 15 minute period. All Versions Current24HrBIP-8ES cds3PlcpBip8ES24HrBucket The number of BIP-8 ES encountered by the line in the last 24 hour.
Appendix E Real-Time Counters AXSM-EndPoint-Connection—Supported Real-Time Counters Table E-8 PLCP Counters—cardFcType not equal to 160 (continued) Applicability Counter Name MIB Object Name Description cardFamily EQ AXSME Num of FEBE cds3PlcpFEBECount The count of Far End Block Errors (FEBE) detected. cardFamily EQ AXSME Num of FEBESec cds3PlcpFEBESecCount The number of FEBE errored seconds.
Appendix E Real-Time Counters AXSM-Port—Supported Real-Time Counters E.
Appendix E Real-Time Counters AXSM-Port—Supported Real-Time Counters Table E-10 Port Counters (continued) Applicability Counter Name MIB Object Name Description All Versions Xmt CLP1 Cells (Ingress) caviIngXmtClp1Cells The number of CLP-1 cells transmitted to the switch after traffic management and policing in ingress direction. All Versions Xmt CLP1 Cells (Egress) caviEgrXmtClp1Cells The number of CLP-1 cells transmitted to the network after traffic management and policing.
Appendix E Real-Time Counters AXSM-Port—Supported Real-Time Counters Table E-11 Call Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions In Resource Failures cwspInResrcFailures This object shows the number of incoming Point-to-Point(p2p) and Point-to-MulitPoint(p2mp) SVC/SPVC call attempts on this interface which failed because there were not enough resources as requested in the parameters of the call.
Appendix E Real-Time Counters AXSM-Port—Supported Real-Time Counters Table E-11 Call Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions Out Resource Failures cwspOutResrcFailures This object shows the number of outgoing Signaling messages for call establishment on this interface which failed because the resource requested was not available.
Appendix E Real-Time Counters AXSM-Port—Supported Real-Time Counters Table E-12 Load Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions Available BW UBR cwspLoadAvlBwUbr The available bandwith for UBR service. All Versions Available VCs cwspLoadVcAvail The total number of available VCs of the interface. All Versions Avaailable VCs CBR cwspLoadAvlVcCbr The number of VCs used by CBR service.
Appendix E Real-Time Counters AXSM-Port—Supported Real-Time Counters Table E-12 Load Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions cwspLoadClr0Abr cwspLoadClr0Abr The cell loss ratio-0 of ABR service, -1 implies N/A. All Versions cwspLoadClr0Ubr cwspLoadClr0Ubr The cell loss ratio-0 of UBR service, -1 implies N/A. All Versions cwspLoadClr01Cbr cwspLoadClr01Cbr The cell loss ratio-1 of CBR service, -1 implies N/A.
Appendix E Real-Time Counters AXSM-Port—Supported Real-Time Counters Table E-13 Signalling Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions cwspReleaseRcv cwspReleaseRcv Number of RELEASE messages received on this interface. All Versions cwspReleaseComplRcv cwspReleaseComplRcv Number of RELEASE COMPLETE messages received on this interface.
Appendix E Real-Time Counters AXSM-Port—Supported Real-Time Counters Table E-13 Signalling Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions cwspCallProcXmt cwspCallProcXmt Number of CALL PROCEEDING messages transmitted from this interface. All Versions cwspConnectXmt cwspConnectXmt Number of CONNECT messages transmitted from this interface.
Appendix E Real-Time Counters AXSM-SONET-Line—Supported Real-Time Counters Table E-13 Signalling Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions cwspDropPtyXmt cwspDropPtyXmt Number of DROP PARTY messages transmitted from this interface. All Versions cwspSscopStatus cwspSscopStatus Sscop link status on an NNI interface, object is meaningful along with ciscoWANSscopLinkChange trap. E.
Appendix E Real-Time Counters AXSM-SONET-Line—Supported Real-Time Counters Table E-14 ATM Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Err OAM Cells (Egress) caclOutErrOAMCells The number of errored OAM cells received by the interface from the switch fabric. All Versions Corrected HecErr Cells (Ingress) aclInHecErrCorrectedCells The number of received cells which had HEC errors that were corrected.
Appendix E Real-Time Counters AXSM-SONET-Line—Supported Real-Time Counters Table E-15 Line Current Counters Applicability Counter Name MIB Object Name Description All Versions ESs sonetLineCurrentESs The counter associated with the number of Errored Seconds encountered by a SONET/SDH Line in the current 15 minute interval.
Appendix E Real-Time Counters AXSM-SONET-Line—Supported Real-Time Counters Table E-16 Section Current Counters Applicability Counter Name MIB Object Name Description All Versions ESs sonetSectionCurrentESs The counter associated with the number of Errored Seconds encountered by a SONET/SDH Section in the current 15 minute interval.
Appendix E Real-Time Counters AXSM-SONET-Line—Supported Real-Time Counters Table E-17 Path Current Counters—cardFamily not equal to AXSMXG AND cardFamily not equal to VXSM AND cardFamily not equal to MPSM (continued) Applicability Counter Name MIB Object Name Description cardFamily not equal to VXSM AND cardFamily not equal to SRM ESs (Far End) sonetFarEndPathCurrentESs The counter associated with the number of Far End Errored Seconds encountered by a SONET/SDH interface in the current 15 minute
Appendix E Real-Time Counters AXSM-SONET-Line—Supported Real-Time Counters Table E-18 Line Current 24 Hour Counters—cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM (continued) Applicability Counter Name MIB Object Name Description All Versions CVs (Far End) cwsFELineCurrent24HrCVs Number of far end CVs encountered in current 24 hour interval. All Versions UASs (Far End) cwsFELineCurrent24HrUASs Number of far end UASs encountered in current 24 hour interval.
Appendix E Real-Time Counters AXSM-SONET-Line—Supported Real-Time Counters Table E-20 Path Current 24 Hour Counters—cardFamily not equal to AXSM AND cardFamily not equal to AXSMXG AND cardFamily not equal to VXSM AND cardFamily not equal to MPSM (continued) Applicability Counter Name MIB Object Name Description cardFamily not equal to VXSM CVs (Far End) cwsFEPathCurrent24HrCVs Number of far end CVs encountered in current 24 hour interval.
Appendix E Real-Time Counters AXSME-Card—Supported Real-Time Counters Table E-21 Applicability Alarm Statistics (continued) Counter Name MIB Object Name Description Path AISs (cardFamily not equal to MPSM) OR (cardFamily EQ MPSM AND entityType EQ PATH) cspAISs The number of alarm indication signals (AIS) encountered by a SONET/SDH Path. A high value for this object may indicate a problem with the Sonet Path layer.
Appendix E Real-Time Counters AXSME-DS1-Line—Supported Real-Time Counters Table E-22 ATM Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Err OAM Cells (Egress) caclOutErrOAMCells The number of errored OAM cells received by the interface from the switch fabric. All Versions Corrected HecErr Cells (Ingress) caclInHecErrCorrectedCells The number of received cells which had HEC errors that were corrected.
Appendix E Real-Time Counters AXSME-DS1-Line—Supported Real-Time Counters Table E-23 Line Current Counters Applicability Counter Name MIB Object Name Description All Versions ESs dsx1CurrentESs The number of Errored Seconds. All Versions SESs dsx1CurrentSESs The number of Severely Errored Seconds. All Versions SEFSs dsx1CurrentSEFSs The number of Severely Errored Framing Seconds. All Versions UASs dsx1CurrentUASs The number of Unavailable Seconds.
Appendix E Real-Time Counters AXSME-DS3-Line—Supported Real-Time Counters Table E-24 Line Alarm Statistics—cardFamily EQ VXSM Applicability Counter Name MIB Object Name Description All Versions LOS Count cds1LOSCounts The number of times the Loss Of Signal defect was detected with or without integrating to LOS alarm. All Versions OOF Count cds1OOFCounts The number of times the Out of Frame (OOF) was detected with or without integrating to OOF alarm.
Appendix E Real-Time Counters AXSME-DS3-Line—Supported Real-Time Counters Table E-25 ATM Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Err OAM Cells (Ingress) caclInErrOAMCells The number of errored OAM cells received on the interface. All Versions Err OAM Cells (Egress) caclOutErrOAMCells The number of errored OAM cells received by the interface from the switch fabric.
Appendix E Real-Time Counters AXSME-DS3-Line—Supported Real-Time Counters Table E-26 Category—Line Current Counters Applicability Counter Name MIB Object Name Description cardFamily not equal to AXSMXG PESs dsx3CurrentPESs The counter associated with the number of P-bit Errored Seconds. cardFamily not equal to AXSMXG PSESs dsx3CurrentPSESs The counter associated with the number of P-bit Severely Errored Seconds.
Appendix E Real-Time Counters AXSME-DS3-Line—Supported Real-Time Counters Table E-27 Line Current 24 Hour Counters—cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM OR cardFamily EQ FRSM12 Applicability Counter Name MIB Object Name Description All Versions LCVs cds3LCVCurrent24Hr The number of LCVs encountered by the line since the start of current 24 hour period.
Appendix E Real-Time Counters AXSME-DS3-Line—Supported Real-Time Counters Table E-28 Applicability Line Alarm Statistics (continued) Counter Name MIB Object Name Description FE Count cardFamily not equal to AXSME AND cardFamily not equal to AXSMXG AND cardFamily not equal to PXM1E AND cardFamily not equal to MPSM cds3FECount The number of Framing Errors encountered by a T3/E3 interface.
Appendix E Real-Time Counters AXSME-DS3-Line—Supported Real-Time Counters Table E-28 Applicability Line Alarm Statistics (continued) MIB Object Name Description FEBE Count cardFamily not equal to AXSM AND cardFamily not equal to AXSME AND cardFamily not equal to AXSMXG AND cardFamily not equal to PXM1E AND cardFamily not equal to MPSM cds3FEBECount The number of Far End Block Errors(FEBE) encountered by a T3/E3 interface.
Appendix E Real-Time Counters AXSME-EndPoint-Connection—Supported Real-Time Counters Table E-29 PLCP Counters—cardFcType not equal to 160 (continued) Applicability Counter Name MIB Object Name Description All Versions CurrentUAS cds3PlcpUASCurrent The number of Unavailable Seconds(UAS) encountered by the line in the current 15-minute period. All Versions Current24HrUAS cds3PlcpUAS24HrBucket The number of BIP-8 UAS encountered by the line in the last 24 hour.
Appendix E Real-Time Counters AXSME-ImaGroup—Supported Real-Time Counters Table E-30 ATM Connection Statistics (continued) Applicability Counter Name MIB Object Name Description All Versions Rcv EFCI1 (Ingress) cwacsIngRcvEFCI1 Ingress Rcv EFCI1 All Versions Rcv EOF1(Ingress) cwacsIngRcvEOF1 Ingress Rcv EOF1 All Versions Queue Depth (Ingress) cwacsIngVCQueueDepth Ingress Queue Depth All Versions Rcv CLP0 (Egress) cwacsEgrRcvCLP0 Egress Rcv CLP0 All Versions Rcv CLP1 (Egress) cwacsE
Appendix E Real-Time Counters AXSME-ImaGroup—Supported Real-Time Counters Table E-31 ATM Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Last Unknown VPI (Ingress) caclInLastUnknVpi The last unknown Vpi value. This object is valid only if 'caclInVpiVciErrCells' is non-zero. All Versions Lask Unknown VCI (Ingress) caclInLastUnknVci The last unknown Vci value. This object is valid only if 'caclInVpiVciErrCells' is non-zero.
Appendix E Real-Time Counters AXSME-ImaLink—Supported Real-Time Counters Table E-32 IMA Group Alarm Counters (continued) Applicability Counter Name MIB Object Name Description All Versions Tx Avail Cell rate imaGroupTxAvailCellRate The current cell rate (truncated value in cells per second) provided by this IMA group in the transmit direction, considering all the transmit links in the Active state.
Appendix E Real-Time Counters AXSME-ImaLink—Supported Real-Time Counters Table E-33 IMA Link Counters (continued) Applicability Counter Name MIB Object Name Description All Versions Fe Unavail Secs imaLinkFeUnavailSecs Count of unavailable seconds at far-end: unavailability begins at the onset of 10 contiguous SES-IMA-FE and ends at the onset of 10 contiguous seconds with no SES-IMA-FE.
Appendix E Real-Time Counters AXSME-Port—Supported Real-Time Counters Table E-33 IMA Link Counters (continued) Applicability Counter Name MIB Object Name Description All Versions Rx Stuffs imaLinkRxStuffs Count of stuff events detected in the receive direction. This is an optional attribute. All Versions Num Rx ICP Cells cimaLinkNumRxIcpCells Number of error-free received ICP cells on this link of the IMA group. E.
Appendix E Real-Time Counters AXSME-Port—Supported Real-Time Counters Table E-34 Port Counters (continued) Applicability Counter Name MIB Object Name Description All Versions Xmt CLP0 Cells (Ingress) caviIngXmtClp0Cells The number of CLP-0 cells transmitted to the switch after traffic management and policing in ingress direction. All Versions Xmt CLP0 Cells (Egress) caviEgrXmtClp0Cells The number of CLP-0 cells transmitted to the network after traffic management and policing.
Appendix E Real-Time Counters AXSME-Port—Supported Real-Time Counters Table E-35 Call Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions In Route Failures cwspInRouteFailures This object shows the number of incoming Point-to-Point(p2p) and Point-to-MulitPoint(p2mp) SVC/SPVC call attempts on this interface which failed because there was no route to the destination available.
Appendix E Real-Time Counters AXSME-Port—Supported Real-Time Counters Table E-35 Call Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions Out Route Failures cwspOutRouteFailures This object shows the number of outgoing Signaling messages for call establishment on this interface which failed because the route was not available.
Appendix E Real-Time Counters AXSME-Port—Supported Real-Time Counters Table E-36 Load Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions Available BW ABR cwspLoadAvlBwAbr The available bandwith for ABR service. All Versions Available BW UBR cwspLoadAvlBwUbr The available bandwith for UBR service. All Versions Available VCs cwspLoadVcAvail The total number of available VCs of the interface.
Appendix E Real-Time Counters AXSME-Port—Supported Real-Time Counters Table E-36 Load Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions cwspLoadClr0Ubr cwspLoadClr0Ubr The cell loss ratio-0 of UBR service, -1 implies N/A. All Versions cwspLoadClr01Cbr cwspLoadClr01Cbr The cell loss ratio-1 of CBR service, -1 implies N/A.
Appendix E Real-Time Counters AXSME-Port—Supported Real-Time Counters Table E-37 Signalling Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions cwspRestartAckRcv cwspRestartAckRcv Number of RESTART ACK messages received on this interface. All Versions cwspStatusRcv cwspStatusRcv Number of STATUS messages received on this interface.
Appendix E Real-Time Counters AXSME-SONET-Line—Supported Real-Time Counters Table E-37 Signalling Statistics—evaluate_isPnPortPresent (continued) Applicability Counter Name MIB Object Name Description All Versions cwspRestartXmt cwspRestartXmt Number of RESTART messages transmitted from this interface. All Versions cwspRestartAckXmt cwspRestartAckXmt Number of RESTART ACK messages transmitted from this interface.
Appendix E Real-Time Counters AXSME-SONET-Line—Supported Real-Time Counters Table E-38 • Section Current 24 Hour Counters— cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM • Path Current 24 Hour Counters—cardFamily not equal to AXSM AND cardFamily not equal to AXSMXG AND cardFamily not equal to VXSM AND cardFamily not equal to MPSM ATM Cell Layer Counters—cellLayer EQ true Applicability Counter Name MIB Object Name Description All Versions CLP0 Cells (Ingress) caclInRcvCLP0Cell
Appendix E Real-Time Counters AXSME-SONET-Line—Supported Real-Time Counters Table E-39 Line Current Counters Applicability Counter Name MIB Object Name Description All Versions ESs sonetLineCurrentESs The counter associated with the number of Errored Seconds encountered by a SONET/SDH Line in the current 15 minute interval.
Appendix E Real-Time Counters AXSME-SONET-Line—Supported Real-Time Counters Table E-40 Section Current Counters (continued) Applicability Counter Name MIB Object Name Description All Versions SEFSs sonetSectionCurrentSEFSs The counter associated with the number of Severely Errored Framing Seconds encountered by a SONET/SDH Section in the current 15 minute interval.
Appendix E Real-Time Counters AXSME-SONET-Line—Supported Real-Time Counters Table E-42 Line Current 24 Hour Counters—cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM Applicability Counter Name MIB Object Name Description All Versions ESs cwsLineCurrent24HrESs Number of errored seconds encountered in current 24 hour interval. All Versions SESs cwsLineCurrent24HrSESs Number of SESs encountered in current 24 hour interval.
Appendix E Real-Time Counters MGX2-RPM-Card—Supported Real-Time Counters Table E-44 Path Current 24 Hour Counters—cardFamily not equal to AXSM AND cardFamily not equal to AXSMXG AND cardFamily not equal to VXSM AND cardFamily not equal to MPSM (continued) Applicability Counter Name MIB Object Name Description All Versions UASs cwsPathCurrent24HrUASs Number of UASs encountered in current 24 hour interval.
Appendix E Real-Time Counters RPM-EndPoint-Connection—Supported Real-Time Counters E.16 RPM-EndPoint-Connection—Supported Real-Time Counters No Real-Time Counters supported for the RPM-EndPoint-Connection E.
Appendix E Real-Time Counters RPM-ETHERNET-Line—Supported Real-Time Counters Table E-46 Category—Interface Counters (continued) Applicability Counter Name MIB Object Name Description All Versions In Discarded Packets (Unknown Protocol) ifInUnknownProtos For packet-oriented interfaces, the number of packets received via the interface which were discarded because of an unknown or unsupported protocol.
Appendix E Real-Time Counters RPM-ETHERNET-Line—Supported Real-Time Counters Table E-46 Category—Interface Counters (continued) Applicability Counter Name MIB Object Name Description All Versions Ignored In Packets locIfInIgnored Number of input packets which were simply ignored by this interface. All Versions Internal Resets locIfResets Number of times the interface internally reset.
Appendix E Real-Time Counters RPM-ETHERNET-Line—Supported Real-Time Counters Table E-47 Category—Ethernet Counters (continued) Applicability Counter Name MIB Object Name Description All Versions Late Collisions dot3StatsLateCollisions The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet. Five hundred and twelve bit-times corresponds to 51.2 microseconds on a 10 Mbit/s system.
Appendix E Real-Time Counters RPM-Port—Supported Real-Time Counters E.18 RPM-Port—Supported Real-Time Counters No Real-Time Counters supported for the RPM-Port E.
Appendix E Real-Time Counters RPM-SONET-Line—Supported Real-Time Counters Table E-48 Category—Interface Counters (continued) Applicability Counter Name MIB Object Name Description All Versions In Discarded Packets (Unknown Protocol) ifInUnknownProtos For packet-oriented interfaces, the number of packets received via the interface which were discarded because of an unknown or unsupported protocol.
Appendix E Real-Time Counters RPM-SONET-Line—Supported Real-Time Counters Table E-48 Category—Interface Counters (continued) Applicability Counter Name MIB Object Name Description All Versions Ignored In Packets locIfInIgnored Number of input packets which were simply ignored by this interface. All Versions Internal Resets locIfResets Number of times the interface internally reset. All Versions Output Collisions locIfCollisions The number of output collisions detected on this interface.
Appendix E Real-Time Counters RPM-SONET-Line—Supported Real-Time Counters Table E-49 Category—Line Current Counters (continued) Applicability Counter Name MIB Object Name Description cardFamily not CVs (Far End) equal to VXSM AND cardFamily not equal to SRM sonetFarEndLineCurrentCVs The counter associated with the number of Far End Coding Violations reported via the far end block error count encountered by a SONET/SDH Medium/Section/Line interface in the current 15 minute interval.
Appendix E Real-Time Counters RPM-VirtualPort—Supported Real-Time Counters Table E-51 Category—Path Current Counters—cardFamily not equal to AXSMXG AND cardFamily not equal to VXSM AND cardFamily not equal to MPSM (continued) Applicability Counter Name MIB Object Name Description All Versions CVs sonetPathCurrentCVs The counter associated with the number of Coding Violations encountered by a SONET/SDH Path in the current 15 minute interval.
Appendix E Real-Time Counters MGX2-SRM-DS3-Line—Supported Real-Time Counters E.
Appendix E Real-Time Counters MGX2-SRM-DS3-Line—Supported Real-Time Counters Table E-52 Category—ATM Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Rcv Idle Cells (Ingress) caclInRcvIdleCells The number of idle cells received from the interface. All Versions Discard HecErr Cells (Ingress) caclInHecErrDiscCells Header Error Check (HEC) calculation is used to provide error detection and correction from the ATM cell header.
Appendix E Real-Time Counters MGX2-SRM-DS3-Line—Supported Real-Time Counters Table E-53 Category—Line Current Counters (continued) CCVs (Far End) dsx3FarEndCurrentCCVs cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM OR cardFamily EQ FRSM12 The counter associated with the number of Far End C-bit Coding Violations reported via the far end block error count.
Appendix E Real-Time Counters MGX2-SRM-DS3-Line—Supported Real-Time Counters Table E-55 Category—Line Alarm Statistics Applicability Counter Name MIB Object Name Description cardFamily not equal to AXSMXG LOS Count cds3RcvLOSCount The number of times Loss of Signal was detected with or without integrating to LOS alarm. cardFamily not equal to AXSMXG OOF Count cds3RcvOOFCount The number of times Out of Frame was detected with or without integrating to OOF alarm.
Appendix E Real-Time Counters MGX2-SRM-DS3-Line—Supported Real-Time Counters Table E-55 Applicability Category—Line Alarm Statistics (continued) MIB Object Name Description CPE Count cardFamily not equal to AXSM AND cardFamily not equal to AXSME AND cardFamily not equal to AXSMXG AND cardFamily not equal to PXM1E AND cardFamily not equal to MPSM cds3CPECount The number of C-bit parity errors(CPERR) on a DS3 interface. This value is calculated over noninformation bits in the DS3 frame.
Appendix E Real-Time Counters MGX2-SRM-SONET-Line—Supported Real-Time Counters Table E-56 PLCP Counters—cardFcType not equal to 160 (continued) Applicability Counter Name MIB Object Name Description All Versions CurrentSEFs cds3PlcpSEFSCurrent The number of BIP-8 Severely Errored Framing Seconds(SEFS) encountered by the line in the current 15-minute period. All Versions Current24HrSEFs cds3PlcpSEFS24HrBucket The number of BIP-8 SEFS encountered by the line in the last 24 hour.
Appendix E Real-Time Counters MGX2-SRM-SONET-Line—Supported Real-Time Counters Table E-57 • Section Current 24 Hour Counters— cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM • Path Current 24 Hour Counters—cardFamily not equal to AXSM AND cardFamily not equal to AXSMXG AND cardFamily not equal to VXSM AND cardFamily not equal to MPSM • Alarm Statistics ATM Cell Layer Counters—cellLayer EQ true Applicability Counter Name MIB Object Name Description All Versions CLP0 Cells (Ing
Appendix E Real-Time Counters MGX2-SRM-SONET-Line—Supported Real-Time Counters Table E-58 Line Current Counters Applicability Counter Name MIB Object Name Description All Versions ESs sonetLineCurrentESs The counter associated with the number of Errored Seconds encountered by a SONET/SDH Line in the current 15 minute interval.
Appendix E Real-Time Counters MGX2-SRM-SONET-Line—Supported Real-Time Counters Table E-59 Section Current Counters (continued) Applicability Counter Name MIB Object Name Description All Versions SEFSs sonetSectionCurrentSEFSs The counter associated with the number of Severely Errored Framing Seconds encountered by a SONET/SDH Section in the current 15 minute interval.
Appendix E Real-Time Counters MGX2-SRM-SONET-Line—Supported Real-Time Counters Table E-61 Line Current 24 Hour Counters—cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM Applicability Counter Name MIB Object Name Description All Versions ESs cwsLineCurrent24HrESs Number of errored seconds encountered in current 24 hour interval. All Versions SESs cwsLineCurrent24HrSESs Number of SESs encountered in current 24 hour interval.
Appendix E Real-Time Counters MGX2-SRM-SONET-Line—Supported Real-Time Counters Table E-63 Path Current 24 Hour Counters—cardFamily not equal to AXSM AND cardFamily not equal to AXSMXG AND cardFamily not equal to VXSM AND cardFamily not equal to MPSM (continued) Applicability Counter Name MIB Object Name Description All Versions UASs cwsPathCurrent24HrUASs Number of UASs encountered in current 24 hour interval.
Appendix E Real-Time Counters Common/Card-BearerEndPoint—Supported Real-Time Counters E.24 Common/Card-BearerEndPoint—Supported Real-Time Counters This section includes the following information: • Table E-65 Bearer Counters—platform EQ NOTARES Bearer Counters—platform EQ NOTARES Applicability Counter Name MIB Object Name Description All Versions Channel Id bearerCid This attribute defines the CID (Channel ID associated with this bearer connection.
Appendix E Real-Time Counters Common/Card-BearerEndPoint—Supported Real-Time Counters Table E-65 Bearer Counters—platform EQ NOTARES (continued) Applicability Counter Name MIB Object Name Description All Versions AAL2 External AIS Count bearerAal2ExtAISCnts This object contains the number of external AIS aal2 Type3 packets received.
Appendix E Real-Time Counters Common/Card-RudpSession—Supported Real-Time Counters E.25 Common/Card-RudpSession—Supported Real-Time Counters This section includes the following information: • Table E-66 RUDP Session Counters RUDP Session Counters Applicability Counter Name MIB Object Name Description All Versions vismRudpSessionAutoResets vismRudpSessionAutoResets Auto reset is also known as soft reset. VISM (gateway) initiates an auto reset when it detects that a connection has failed.
Appendix E Real-Time Counters Common/Card-SrcpPeer—Supported Real-Time Counters E.26 Common/Card-SrcpPeer—Supported Real-Time Counters This section includes the following information: • Table E-67 SRCP Peer Counters SRCP Peer Counters Applicability Counter Name MIB Object Name Description All Versions SRCP Peer Name srcpStatsPeerName Denotes the name of the SRCP peer. If MGMIB is supported, this is the same as the mgcName from the mgcTable.
Appendix E Real-Time Counters Common/Card-XgcpPeer—Supported Real-Time Counters Table E-67 SRCP Peer Counters (continued) Applicability Counter Name MIB Object Name Description All Versions RQNT Fail Count rqntFailCnts Media Gateway —The total number of RQNT commands received that were responded to with a failure return code. Media Gateway Controller—The total number of RQNT commands sent which were timed out without a response or for which a response with failure return code was received.
Appendix E Real-Time Counters Common/Card-XgcpPeer—Supported Real-Time Counters Table E-68 XGCP Message Counters (continued) Applicability Counter Name MIB Object Name Description All Versions MDCX Count vismXgcpMdcxCnts This refers to the count of MDCX (Modify Connection) messages received from the call agent since reset.
Appendix E Real-Time Counters VISM-Card—Supported Real-Time Counters Table E-68 XGCP Message Counters (continued) Applicability Counter Name MIB Object Name Description All Versions RSIP Count vismXgcpRsipCnts This refers to the count of RSIP (Restart In Progress) messages sent to the call agent since reset.
Appendix E Real-Time Counters VISM-DS1-Line—Supported Real-Time Counters E.29 VISM-DS1-Line—Supported Real-Time Counters This section includes the following information: Table E-72 • Line Counters • DS0 Information—cardVersion Greater or Equal to 3.2 Line Counters Applicability Counter Name MIB Object Name Description All Versions Rcv LOS Count rcvLOSCount The number of times the Loss of Signal was detected with or without integrating to LOS alarm.
Appendix E Real-Time Counters VISM-DS1-Line—Supported Real-Time Counters Table E-72 Line Counters (continued) Applicability Counter Name MIB Object Name Description All Versions CRC 24Hr Bucket cRC24HrBucket This counter counts the number of P Bit code violations in the last 24 hours encountered by the interface. All Versions CRC ES Current cRCESCurrent This counter counts the number of PCV Errored Seconds encountered by the interface.
Appendix E Real-Time Counters VISM-EndPoint-Connection—Supported Real-Time Counters Table E-73 DS0 Information—cardVersion Greater or Equal to 3.2 Applicability Counter Name MIB Object Name Description All Versions Configured DS0s Count lineTotalDs0Count This is the total number of ds0s configured on this DS1 line. All Versions Free DS0s Count lineFreeDs0Count This is the total number of free ds0s on this DS1 line.
Appendix E Real-Time Counters VISM-EndPoint-Connection—Supported Real-Time Counters Table E-74 Channel Counters (continued) Applicability Counter Name MIB Object Name Description All Versions AAL2 Invalid CID CPS vismChanAal2CpsInvCidPkts The count of AAL2 CPS packets dropped in the egress direction due to invalid CID (Channel ID). The CID may be considered as invalid if - a) It is out of range.
Appendix E Real-Time Counters VISM-VirtualPort—Supported Real-Time Counters Table E-74 Applicability Channel Counters (continued) Counter Name MIB Object Name Description cardVersion Current Rcv Cell greater or equal Rate to 3.2.1 vismChanCurrentRcvCellRate This object counts the current receive cell rate (cells per second) for the channel. cardVersion AIS Suppress greater or equal Count to 3.2.
Appendix E Real-Time Counters Common/Card-MGMGLink—Supported Real-Time Counters Table E-76 Command Statistics Applicability Counter Name MIB Object Name Description All Versions Command ADD Fail Count cmedxCmdNumAddFails Total number of cumulative ADD commands failed in the media gateway link. All Versions Command ADD Succeed Count cmedxCmdNumAddSucceeds Total number of cumulative ADD command succeeded in the media gateway link.
Appendix E Real-Time Counters Common/Card-VxsmXgcp—Supported Real-Time Counters Table E-76 Command Statistics (continued) Applicability Counter Name MIB Object Name Description All Versions Command Service Change from MG to MGC Fail Count cmedxCmdNumSrvChgFromMgF ails Total number of cumulative ServiceChange commands from MG to MGC failed in MGC.
Appendix E Real-Time Counters Common/Card-VxsmCid—Supported Real-Time Counters Table E-78 XGCP Counters Applicability Counter Name MIB Object Name Description All Versions Successful Messages cXgcpMsgStatsSuccessMessage s This object indicates the count of successful messages that communicate with the Media Gateway Controller All Versions Fail Messages cXgcpMsgStatsFailMessages This object indicates the count of failed messages that communicate with the Media Gateway Controller All Versions
Appendix E Real-Time Counters Common/Card-VxsmCid—Supported Real-Time Counters Table E-79 CID Counters—platform EQ NOTARES (continued) Applicability Counter Name MIB Object Name Description All Versions External AIS Count catmtCidExtAISCnts This object contains the number of external AIS AAL2 Type3 packets received.
Appendix E Real-Time Counters Common/Card-RudpSession—Supported Real-Time Counters Table E-79 CID Counters—platform EQ NOTARES (continued) Applicability Counter Name All Versions catmtCidNx64Invalid catmtCidNx64InvalidFCSFrame FCSFrames s This object contains the number of invalid frames received with invalid Frame Check Sequence (FCS) error. This object is only applicable when catmtCidNx64Mode is set to to 'hdlc'.
Appendix E Real-Time Counters Common/Card-MGMGLink—Supported Real-Time Counters Table E-80 RUDP Session Counters (continued) Applicability Counter Name MIB Object Name Description All Versions Number Of Packets Received Out Of Sequence vismRudpSessionRcvdOutSeqs Number of packets received out of sequence. All Versions Number Of Sent Packets vismRudpSessionSentPackets This is the number of packets sent by VISM. Including SYN message.
Appendix E Real-Time Counters Common/Card-MGMGLink—Supported Real-Time Counters Table E-81 Gateway Counters (continued) Applicability Counter Name MIB Object Name Description All Versions Timer Recovery Events Count cmedNumTimerRecovery Total Number of timer recovery events since the statistics was last reset. This reflects all protocol timers that are supported (For H.
Appendix E Real-Time Counters VXSM-VT-Path—Supported Real-Time Counters Table E-82 Command Statistics (continued) Applicability Counter Name All Versions Command Service cmedxCmdNumSrvChgFromMg Change from MGC to cFails MG Fail Count Total number of cumulative ServiceChange commands from MGC to MG failed in the media gateway link.
Appendix E Real-Time Counters VXSM-VirtualPort—Supported Real-Time Counters E.38 VXSM-VirtualPort—Supported Real-Time Counters This section includes the following information: • Table E-84 Port Counters Port Counters Applicability Counter Name MIB Object Name Description All Versions Rcv CLP0 Cells (Egress) cpAtmIfEgrRcvClp0Cells The number of CLP-0 cells received from switch at the traffic management and policing device.
Appendix E Real-Time Counters VXSM-STS-Path—Supported Real-Time Counters E.
Appendix E Real-Time Counters VXSM-STS-Path—Supported Real-Time Counters Table E-85 Atm Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Rcv Idle Cells (Ingress) caclInRcvIdleCells The number of idle cells received from the interface. All Versions Discard HecErr Cells (Ingress) caclInHecErrDiscCells Header Error Check (HEC) calculation is used to provide error detection and correction from the ATM cell header.
Appendix E Real-Time Counters VXSM-STM-Path—Supported Real-Time Counters Table E-87 Path Current 24 Hour Counters—cardFamily EQ MPSM Applicability Counter Name MIB Object Name Description All Versions ESs cwsPathCurrent24HrESs Number of errored seconds encountered in current 24 hour interval. All Versions SESs cwsPathCurrent24HrSESs Number of SESs encountered in current 24 hour interval. All Versions CVs cwsPathCurrent24HrCVs Number of CVs encountered in current 24 hour interval.
Appendix E Real-Time Counters VXSM-STM-Path—Supported Real-Time Counters Table E-88 Atm Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Err OAM Cells (Egress) caclOutErrOAMCells The number of errored OAM cells received by the interface from the switch fabric. All Versions Corrected HecErr Cells (Ingress) caclInHecErrCorrectedCells The number of received cells which had HEC errors that were corrected.
Appendix E Real-Time Counters VXSM-STM-Path—Supported Real-Time Counters Table E-89 Path Current Counters—cardFamily EQ AXSMXG OR cardFamily EQ VXSM OR cardFamily EQ MPSM (continued) Applicability Counter Name MIB Object Name Description cardFamily not equal to VXSM AND cardFamily not equal to SRM ESs (Far End) sonetFarEndPathCurrentESs The counter associated with the number of Far End Errored Seconds encountered by a SONET/SDH interface in the current 15 minute interval.
Appendix E Real-Time Counters VXSM-SONET-Line—Supported Real-Time Counters E.
Appendix E Real-Time Counters VXSM-SONET-Line—Supported Real-Time Counters Table E-91 Atm Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Rcv Valid RM Cells (Ingress) caclInValidRMCells The number of Valid RM cells received from the interface. All Versions Rcv Valid RM Cells (Egress) caclOutRcvValidRMCells The number of Valid RM cells received by the interface from the switch fabric.
Appendix E Real-Time Counters VXSM-SONET-Line—Supported Real-Time Counters Table E-92 Line Current Counters (continued) Applicability Counter Name MIB Object Name Description cardFamily not equal to VXSM AND cardFamily not equal to SRM CVs (Far End) sonetFarEndLineCurrentCVs The counter associated with the number of Far End Coding Violations reported via the far end block error count encountered by a SONET/SDH Medium/Section/Line interface in the current 15 minute interval.
Appendix E Real-Time Counters VXSM-SONET-Line—Supported Real-Time Counters Table E-94 Path Current Counters—cardFamily not equal to AXSMXG AND cardFamily not equal to VXSM AND cardFamily not equal to MPSM (continued) Applicability Counter Name MIB Object Name Description All Versions UASs sonetPathCurrentUASs The counter associated with the number of Unavailable Seconds encountered by a Path in the current 15 minute interval.
Appendix E Real-Time Counters VXSM-SONET-Line—Supported Real-Time Counters Table E-95 Line Current 24 Hour Counters—cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM (continued) Applicability Counter Name MIB Object Name Description All Versions CVs (Far End) cwsFELineCurrent24HrCVs Number of far end CVs encountered in current 24 hour interval. All Versions UASs (Far End) cwsFELineCurrent24HrUASs Number of far end UASs encountered in current 24 hour interval.
Appendix E Real-Time Counters VXSM-EndPoint-Connection—Supported Real-Time Counters Table E-98 Alarm Statistics Applicability Counter Name MIB Object Name Description All Versions Section LOSs cssLOSs The number of Loss of signals(LOS) encountered by a SONET/SDH Section. A high value for this object may indicate a problem with the Sonet Section layer. All Versions Section LOFs cssLOFs The number of Loss of Frames (LOF) encountered by a SONET/SDH Section.
Appendix E Real-Time Counters VXSM-EndPoint-Connection—Supported Real-Time Counters Table E-99 Channel Counters Applicability Counter Name MIB Object Name Description All Versions Xmt CLP0 (Ingress) cwacsIngXmtCLP0 The number of valid CLP=0 ATM cells in the ingress direction of this Channel after the traffic management entity. All Versions Xmt CLP1 (Ingress) cwacsIngXmtCLP1 The number of valid CLP=1 ATM cells in the ingress direction of this Channel after the traffic management entity.
Appendix E Real-Time Counters VXSM-DS3-Path—Supported Real-Time Counters E.
Appendix E Real-Time Counters VXSM-DS3-Path—Supported Real-Time Counters Table E-100 Atm Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Rcv Idle Cells (Ingress) caclInRcvIdleCells The number of idle cells received from the interface. All Versions Discard HecErr Cells (Ingress) caclInHecErrDiscCells Header Error Check (HEC) calculation is used to provide error detection and correction from the ATM cell header.
Appendix E Real-Time Counters VXSM-DS3-Path—Supported Real-Time Counters Table E-101 Line Current Counters (continued) Applicability Counter Name MIB Object Name Description cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM OR cardFamily EQ FRSM12 CSESs (Far End) dsx3FarEndCurrentCSESs The counter associated with the number of Far End C-bit Severely Errored Seconds.
Appendix E Real-Time Counters VXSM-DS3-Path—Supported Real-Time Counters Table E-102 Line Current 24 Hour Counters—cardFamily EQ AXSME OR cardFamily EQ PXM1E OR cardFamily EQ MPSM OR cardFamily EQ FRSM12 (continued) Applicability Counter Name MIB Object Name Description All Versions CESs cds3CESCurrent24Hr The number of CESs encountered by the line since the start of current 24 hour period.
Appendix E Real-Time Counters VXSM-DS3-Path—Supported Real-Time Counters Table E-103 Applicability Line Alarm Statistics (continued) Counter Name MIB Object Name Description LCV Count cardFamily not equal to AXSM AND cardFamily not equal to AXSME AND cardFamily not equal to AXSMXG AND cardFamily not equal to PXM1E AND cardFamily not equal to MPSM cds3LCVCount The count of both BPVs(Bipolar Violations) and EXZs(Excessive Zeros) encountered by a T3/E3 interface.
Appendix E Real-Time Counters VXSM-DS3-Path—Supported Real-Time Counters Table E-103 Applicability Line Alarm Statistics (continued) MIB Object Name Description FEBE Count cardFamily not equal to AXSM AND cardFamily not equal to AXSME AND cardFamily not equal to AXSMXG AND cardFamily not equal to PXM1E AND cardFamily not equal to MPSM cds3FEBECount The number of Far End Block Errors(FEBE) encountered by a T3/E3 interface.
Appendix E Real-Time Counters VXSM-DS1-Path—Supported Real-Time Counters Table E-104 Plcp Counters—cardFcType not equal to 160 (continued) Applicability Counter Name MIB Object Name Description All Versions Current24HrSEFs cds3PlcpSEFS24HrBucket The number of BIP-8 SEFS encountered by the line in the last 24 hour. All Versions CurrentUAS cds3PlcpUASCurrent The number of Unavailable Seconds(UAS) encountered by the line in the current 15-minute period.
Appendix E Real-Time Counters VXSM-DS1-Path—Supported Real-Time Counters Table E-105 Atm Cell Layer Counters—cellLayer EQ true Applicability Counter Name MIB Object Name Description All Versions CLP0 Cells (Ingress) caclInRcvCLP0Cells The number of cells received on the interface with CLP0 bit set. All Versions CLP1 Cells (Ingress) caclInRcvCLP1Cells The number of cells received on the interface with CLP1 bit set.
Appendix E Real-Time Counters VXSM-DS1-Path—Supported Real-Time Counters Table E-106 Line Current Counters (continued) Applicability Counter Name MIB Object Name Description All Versions SEFSs dsx1CurrentSEFSs The number of Severely Errored Framing Seconds. All Versions UASs dsx1CurrentUASs The number of Unavailable Seconds. cardFcType EQ CSSs 602 dsx1CurrentCSSs The number of Controlled Slip Seconds. All Versions PCVs dsx1CurrentPCVs The number of Path Coding Violations.
Appendix E Real-Time Counters VXSM-DS1-Line—Supported Real-Time Counters E.
Appendix E Real-Time Counters VXSM-DS1-Line—Supported Real-Time Counters Table E-109 Line Current Counters Applicability Counter Name MIB Object Name Description All Versions ESs dsx1CurrentESs The number of Errored Seconds. All Versions SESs dsx1CurrentSESs The number of Severely Errored Seconds. All Versions SEFSs dsx1CurrentSEFSs The number of Severely Errored Framing Seconds. All Versions UASs dsx1CurrentUASs The number of Unavailable Seconds.
Appendix E Real-Time Counters VXSM-AU-Path—Supported Real-Time Counters E.
Appendix E Real-Time Counters VXSM-AU-Path—Supported Real-Time Counters Table E-111 Atm Cell Layer Counters—cellLayer EQ true (continued) Applicability Counter Name MIB Object Name Description All Versions Rcv Idle Cells (Ingress) caclInRcvIdleCells The number of idle cells received from the interface. All Versions Discard HecErr Cells (Ingress) caclInHecErrDiscCells Header Error Check (HEC) calculation is used to provide error detection and correction from the ATM cell header.
Appendix E Real-Time Counters VXSM-AU-Path—Supported Real-Time Counters Table E-113 Path Current 24 Hour Counters—cardFamily EQ MPSM Applicability Counter Name MIB Object Name Description All Versions ESs cwsPathCurrent24HrESs Number of errored seconds encountered in current 24 hour interval. All Versions SESs cwsPathCurrent24HrSESs Number of SESs encountered in current 24 hour interval. All Versions CVs cwsPathCurrent24HrCVs Number of CVs encountered in current 24 hour interval.
A P P E N D I X F Open Source License Acknowledgement Cisco Media Gateway Manager 5.0 uses third-party open source software subject to the following licenses: • F.1 OpenSSL • F.2 Bouncy Castle • F.3 jacORB F.1 OpenSSL LICENSE ISSUES ============== The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses.
Appendix F Open Source License Acknowledgement OpenSSL * * 4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to * endorse or promote products derived from this software without * prior written permission. For written permission, please contact * openssl-core@openssl.org. * * 5. Products derived from this software may not be called "OpenSSL" * nor may "OpenSSL" appear in their names without prior written * permission of the OpenSSL Project. * * 6.
Appendix F Open Source License Acknowledgement Bouncy Castle * * Redistribution and use in source and binary forms, with or without * modification, are permitted provided that the following conditions * are met: * 1. Redistributions of source code must retain the copyright * notice, this list of conditions and the following disclaimer. * 2.
Appendix F Open Source License Acknowledgement jacORB F.3 jacORB Copyright (C) Gerald Brose 1997-2002 This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version.
G L O S S A RY Numbers 3R retime, reshape, and regenerate A AC alternating current ACO alarm cutoff ADA Add/Drop Amplifier module AIC Alarm Interface Controller card AID access identifier AIP Alarm Interface Panel AIS alarm indication signal AIS-L line alarm indication signal AIS-P path alarm indication signal AIU Alarm Interface Unit module AMI alternate mark inversion ANS automatic node setup ANSI American National Standards Institute API Application Programming Interface AP
Glossary AXSM ATM switch service module for the MGX 8850 (double height card) AXSM-E Enhanced AXSM (double height card) B B8ZS binary 8-zero substitution BAT Battery Management module BBA Blue-band Booster Amplifier module BBE background block errors BCS-ELH Band Combiner and Splitter–Extended Long Haul module BCS-LH Band Combiner and Splitter–Long Haul module BER bit error rate BIOS basic input/output system BIP bit interleaved parity BITS building integrated timing supply BLSR bi
Glossary CLEI Common Language Equipment Identifier CLI command-line interface CLIP Client Layer Interface Port CM configuration management CMP Control and Monitoring Processor module CMP-W Control and Monitoring Processor module CMP-W-2E Control and Monitoring Processor module–2 Ethernet CO central office CORBA Common Object Request Broker Architecture CPBIT C-bit parity bit CPU central processing unit CRS-1 Cisco Carrier Router System 1 CSMA/CD carrier sense multiple access collis
Glossary DCE data circuit-terminating equipment DCN data communications network DCS Digital Cross-connect System DCU dispersion compensation unit DDS digital data service DHCP Dynamic Host Configuration Protocol DLC digital loop carrier DOS disk operating system DRI dual-ring interconnect DS1 digital service 1 DS-1 digital signal level 1 DS3-12 Digital Signal Level Three (12 ports) card DS3N-12 Digital Signal Level Three (N-12 ports) card DSL digital subscriber line DSU data se
Glossary EP extra pump ES errored seconds ESF Extended Super Frame ES-L line errored seconds ES-P path errored seconds ESP-P errored seconds path ES-S section errored seconds ES-V errored seconds VT layer ETSI European Telecommunications Standards Institute EXZ excessive zeros F FC-L line failure count FC-P path failure count FCS frame check sequence FDI forward defect indication FDL Facility Data Link FEAC Far End Action Code FEC forward error correction FEPM far-end per
Glossary GFP generic framing procedure GHz gigahertz GMT Greenwich mean time GNE gateway network element GOS grade of service GUI Graphical User Interface H H.248 H.248, also known as the Megaco protocol, is the international standard for media gateway control. Primarily used to separate the call control logic from the media processing logic in a gateway.
Glossary J JRE Java Runtime Environment K kbps kilobits per second km kilometer L LAN local-area network LAP low-order aggregation point LAPB Link Access Procedure, Balanced LAPD Link Access Procedure on the D channel LAPS linear automatic protection switching LCAS link capacity adjustment scheme LCI local craft interface LCP link control protocol LCT local craft terminal LED light-emitting diode LEM Line Extender Module LEM-10G-Mxx Line Extender Module–10 Gbps–B1 Monitoring L
Glossary LHS left-hand side LIP Loop Initialization Primitive LLC Logical Link Control LOF loss of function, loss of frame LOH line overhead LOP loss of pointer LOS loss of signal LOSS-L loss-of-signal seconds line LOT loss of traffic LSM-W Line Service Modem module LTE line terminating equipment M mA milliampere MAC Media Access Control MAN metropolitan-area network MB megabyte Mbps megabits per second MCU Multichannel Unit Megaco See H.
Glossary N NAT network address translation NCB Network Controller Board NCP Network Control Protocol NE network element NEID network element identifier nm nanometer NMA Network Management and Analysis NML Network Management Layer NMS network management system NOC network operation center NP network partition NPJC-Pdet negative pointer justification count, STS path detected NPJC-Pgen negative pointer justification count, STS path generated NSA non-service-affecting NSAP network
Glossary ORB object request broker OS operating system, operations system OSI Open Systems Interconnection OSPF Open Shortest Path First OSS operations support system P P protect PAD packet assembler/disassembler PAP Password Authentication Protocol PBIT parity bit PBX private branch exchange PCA protection channel access PDH plesiochronous digital hierarchy PDI-P payload defect indication path PDU protocol data unit PIR peak information rate PLF Power Line Filter module PLC
Glossary PPMN Path Protected Mesh Network PPP MP Point-to-Point Multilink Protocol PRE-L Pre-Line Amplifier module PRE-L-IR Pre-Line Amplifier–Infrared band module PRI Primary Rate Interface PS perceived severity PSC protection switching count PSC-R protection switching count-ring PSC-S protection switching count-span PSC-W protection switching count-working PSD protection switching duration PSD-R protection switching duration-ring PSD-S protection switching duration-span PSD-W p
Glossary RFC request for comments RFI remote failure indication RHS right-hand side RIP Routing Information Protocol RMON remote monitoring RPM Route Processor Module Rx receive RX CVRD code violations and running disparity errors encountered in the receive direction RX HEC number of CDL header errors encountered in the receive direction S SA service affecting SA/DA service address/destination address SAM SONET Access Module, SDH Access Module SAS-L line severely errored frame/alar
Glossary SES-L line severely errored seconds SES-P path severely errored seconds SESP-P severely errored seconds path SES-S section severely errored seconds SES-V severely errored seconds VT layer SF signal failure, Super Frame SFP small form factor pluggable sid system identifier SLIP Serial Line Internet Protocol SMDS Switched Multimegabit Data Service SNH Supervision Network Hub module SNMP Simple Network Management Protocol SNS Supervision Network Switch module SNTP simple ne
Glossary T TC threshold crossing TCA threshold crossing alert TCC Timing Communications and Control Card TCC+ Timing Communications and Control+ Card TCP Transmission Control Protocol TCP/IP Transmission Control Protocol/Internet Protocol TDS time-division switching TFTP Trivial File Transfer Protocol TID target identifier TIM trace identifier mismatch TLAN transparent local-area network TMF TeleManagement Forum TMN Telecommunications Management Network TOH transport overhead TP
Glossary UAS-P path unavailable seconds UAS-V unavailable seconds VT layer UCR uncorrected codeword rate UDC User Data Channel module UDP User Datagram Protocol UI user interface UPSR unidirectional path switched ring UTC Coordinated Universal Time UTP unshielded twisted-pair V V volt VAP VT aggregation point VC virtual channel VCAT virtual concatenation VCI virtual channel identifier VCG virtual concatenation group VCL virtual channel link VISM-PR Voice Inter-working Servi
Glossary W W working WAN wide-area network WCM Wavelength Converter Module WCM-10G-Fxx Wavelength Converter Module–10 Gbps–Forward Error Correction WCM-10G-Mxx Wavelength Converter Module–10 Gbps–B1 Monitoring WCM-10G-Nxx Wavelength Converter Module–10 Gbps–Normal WCM-10H-Mxx Wavelength Converter Module–10 Gbps High Output Power–B1 Monitoring WCM-622-Nxx Wavelength Converter Module–622 Mbps–Normal WCM-EM-Fxx Wavelength Converter Module–Externally Modulated–Forward Error Correction WCM-EM-
I N D EX acknowledgment A acknowledged alarms, viewing Abort, Test Connection button testing a connection for an SPVC 9-30 accessing Network Elements 6-4, 6-9 disabling and enabling 9-49 memory backup failure Configuration Center Diagnostic Center 8-3 exporting 8-3 access security, SNMP 2-12 background color 8-26 display preferences Bulk Distribution using SRME CAS Variant to a VISM-PR Card 6-139 announcements, how to 6-175 6-77 2-19 network elements 1-8 Control Panel 2-7 Network M
Index audit trail AXSM-Port—Supported Real-Time Counters activities log files E-14 AXSM-SONET-Line—Supported Real-Time Counters E-22 8-4 8-4 automatic database pruning discovery 5-13 B 9-6 Automatic Protection Switching, Sonet line backing up 6-53 Average Throughput, health related parameter memory 5-31 procedures AXSM troubleshooting statistics ATM line card connection C-7 BERT D-14 in diagnosing NEs D-30 port 5-37 in Diagnostic Center D-3 9-10 BERT Operation Status paramete
Index diagnostic Diagnostic Center Abort Test Connection, testing a connection for an SPVC 9-30 Attach 5-32 Modify Bert 5-31 5-33 Send 5-33 Cards tab 9-31 7-16, 7-17 Start Test Connection, testing a connection for an SPVC 9-30 Trouble Ticket 5-32 Stop Report Generation, stop generating utilization data report 10-14 buttons, audit trail 6-135 cautions, DCN bandwidth for downloading software images to NEs 5-47 ccs parameter 6-135 8-4 application 6-3 card status 5-21 launching 6-2 LED c
Index Cisco MGM server audit messages Error Logs configuring hardware B-104 4-26 3-2 Cisco MGX 8850 PXM-45 Processor Switch Module, description 3-2 Cisco MGX 8880 Media Gateway, description 3-2 Cisco MGX Service Resource Module-Enhanced (SRME), description 3-6 Cisco Route Processor Module, description 10-3 client C-8 2-22 login, troubleshooting, cannot authenicate user troubleshooting C-10 connectivity with server operational problems See CLI 10-3 commands changing Service Level passwords 4
Index create 7-12 Sonet Path Alarm delete 7-15 Sonet Section Alarm 6-42 6-40 display 7-14 T1 and E1 Lines for VISM-PR modify 7-14 TDM for VISM-PR templates (network elements) 6-131 6-130 TDM Signaling for CAS on VISM-PR 6-180 load 6-12 Time-Division Multiplexing Interface for VXSM save 6-11 Voiceband Data 6-108 configuration management Voice Interfaces 6-74 Configuration Center VoIP CODECs connections overview network elements overview overview hardware, configuring managin
Index Create button viewing configuration of adding redundancy database properties-Configuration Tab, field descriptions 5-4 5-49 creating a manual clock source creating a VSI controller 5-3 4-26 data transmission (figure) 5-33 D-2 data transmission process overview creating MGC Session Group MGC Session Set Date parameter 6-104 PRI-BH Deleted Network Elements group 6-119 5-34 9-6 deleting 6-55 cannot delete an NE, troubleshooting 6-111 Resource Partition for AXSM Resource Partition
Index resource partition Identification tab 6-63 Diagnostic Center Status tab access privileges card status elements NE Authentication tab 2-25 Status tab 2-25 line status 9-5 Network Element properties 9-19 connections 2-3 managing faults 8-3 2-3 overview 9-20 loopback, display using 2-5 2-6 2-5 2-2 2-2 lines 9-22 Domain NE Table, field description paths 9-21 Domain NE Table Filter Dialog Box, field description 11-4 network manageability 2-25 network elements network st
Index cannot authenticate user Cisco MGM client Alarm Browser C-10 Alarm Configuration--Non-Threshold EMS Alarm Tab 9-17 B-1 Cisco MGM server critical Alarm Configuration--Threshold EMS Alarms Tab 9-16 B-61 major B-68 minor B-87 9-8 Database Properties-Configuration Tab Domain NE Table Event Export Manager 9-52 11-3 Error Log Properties Event Notification Dialog Box, field descriptions events 9-35 9-40 Event Notification Dialog Box 9-35 Job Monitor Note Dialog Box exporting 2-12 v
Index G How Do I Configure Cisco MGX 8850 and 8880 Nodes? 6-13 GateWay CORBA How Do I Configure RPM Cards? How Do I Configure the SNMP Community String? Client Configuration table viewing How Do I Configure VISM-PR Cards? 12-4 communications architecture (figure) what is How Do I Configure VXSM Cards? 12-2 How Do I Discover the Network? viewing 6-101 4-23 viewing 5-53 How Do I Manage My Network with the Chassis View? 6-1 12-2 OSS Clients tab How Do I Manage My Network with the Configura
Index login J lockout time, configuring jacORB F-4 8-28 maximum number of attempts, setting job monitor (table) 2-20 maximum number of retries, setting Job Monitor Filter Dialog Box, tab descriptions Job Monitor Note Dialog Box, field descriptions Job Monitor Table descriptions 5-25 8-28 8-28 troubleshooting 5-26 cannot authenticate user 5-24 C-10 cannot log in as provisioner and operator jobs C-9 login advisory message canceling 5-26 monitoring 5-26 scheduling 5-26 customizing o
Index displaying RUDP status displaying status for MGL displaying XGCP status Copy 9-26 Cut 9-25 Paste 9-27 memory manual Close Exit 5-36 procedures 6-7 troubleshooting, NE-specific alarm Contents 9-36 C-7 restoring C-7 Memory Restore Dialog box menu-bar options (Chassis View), Edit 6-7 A-7 5-39 mgms-start command 1-6 mgms-stop command 1-6 8-30 C-3 MGX2-RPM-Card—supported Real-Time Counters E-55 MGX2-SRM-Card—supported Real-Time Counters E-64 MGX2-SRM-DS3-Line—supported Real
Index network element N adding navigating with Chassis View 6-3 navigating with Configuration Center navigating Within Tables 6-9 NE release management job monitor table adding a single 4-3 adding multiple 4-5 network elements, manage of 2-19 card 2-20 display, list of memory backup dialog box 2-20 memory restore dialog box 2-20 NE software table 6-7 1-8 6-15 redundancy, overview Chassis View 2-20 2-18 clocking sources software download dialog box 2-20 4-24 IP interface, disp
Index Level 1 5-44 Multicast Level 2 5-44 Service Type Node tab Type 6-13 none parameter 7-5 7-5 7-5 parameters, health-related 6-135 nonstandard community strings, SNMP 4-15 Average Throughput 5-31 File Size Mismatch Generic Error O object type name D-1 online help, using OpenSSL 5-31 Min Throughput 5-31 5-31 Node Name F-1 operational states Protocol 2-19 operator users, privileges overview 5-32 Max Throughput Node Id 2-10 2-23 5-31 5-31 Queue Full 8-5 5-32 Retry E
Index parameters, VXSM dynamic IP interface, display of sensor, display of 6-116 externalOnly h248 permanent parameter 9-27 Gateway UDP Port permanent PNNI Network Statistics 9-27 Administration Chassis View 9-26 RUDP Session Number 6-183 D-41 popup menu options 9-26 RUDP session 2-10 2-10 Configuration Center 9-26 Diagnostics Center 9-26 Statistics Report 6-93 udp 6-139 placing the VISM-PR Card In or Out of Service 6-116 Local IP D-46 placing T1 or E1 Lines In or Out of Ser
Index VXSM megaco physical termination Protocol Statistics 8-5 pruning, database using scripts 5-38 5-44 Retry Exceeded parameter 5-31 RPM, configure ATM subinterface 2-23 automatically restoring memory Resync button D-43 provisioner users, privileges overview D-46 RPM-EndPoint-Connection—supported Real-Time Counters E-56 5-13 RPM-ETHERNET-Line—supported Real-Time Counters E-56 5-14 pruning databases 6-119 2-13 RPM-Port—supported Real-Time Counters E-60 RPM-SONET-Line—supported Real-
Index connectivity with client no response get C-9 nonstandard C-2 procedures 4-16 set C-7 Service Level password configuration change Service Level users Service Line statistics 4-16 traps not forwarded from NEs 4-17 port number D-8 Service Monitor Table, column name descriptions Service Type parameter 4-15 5-27 C-6 C-6 troubleshooting unavailable ports C-6 software 7-5 downloading Session Failure parameter procedures 5-31 Timeout parameter troubleshooting 5-31 set community
Index AXSM Submit button D-30 connection AXSM 8-4 subobjects D-3 AXSM-E D-5 line, physical AXSM-E SONET D-59 AXSM_ATM_card D-30 AXSM_ATM_conn D-3 AXSM_ATM_line D-14 AXSM_ATM_port D-19 AXSM-E T1/E1 D-51 AXSME_ATM_conn D-5 AXSM-E T3/E3 D-53 AXSME_ATM_line D-17 VXSM SONET D-63 AXSME_ATM_port D-22 VXSM T1E1 AXSME_Phyline_SONET D-65 D-59 line, service AXSME_Phyline_T1E1 D-51 AXSM AXSME_Phyline_T3E3 D-53 D-14 AXSM-E SONET MGX-T3/E3 D-17 SONET (service line) D-13 T3/E
Index Rear View, monitoring a node Cisco MGM Properties pane Test Connection, testing an SPVC connection 5-21 VISM features, displaying status for SRCP 5-28 Configuration Center VXSM features, displaying RUDP 9-26 Advanced Mode VXSM features, displaying XGCP 9-27 Cards 7-3 Diagnostic Center, Miscellaneous Operations 6-15 Clocking Job Monitor Filter dialog box 6-26 clocking, configuring global clocking canceling 4-26 clocking, displaying list of available clock sources 4-26 clocking, di
Index transfer Failure parameter 5-31 Timeout parameter SNMP traps not forwarded C-6 unavailable SNMP trap ports C-6 See also error messages 5-32 trap B-1 Trouble Ticket IP Configuration parameter button 5-32 Manager Configuration parameter 5-32 operation 5-32 troubleshooting 5-32 tstcon command SNMP traps not forwarded Type parameter C-6 9-29 7-5 troubleshooting client/server connectivity C-9 U client login cannot authenicate user C-10 Up Connection radio button cannot log
Index duplicating virtual port 8-12, 8-13 modifying VISM, diagnostic 8-11 network administrator overview operator CODEC templates, viewing VISM mode, viewing 2-23 advanced mode 8-5 quick mode 8-5 display 8-6 user properties, modifying users, viewing logged in 7-4 quick mode 8-23 7-9 7-9 VISM-DS1-Line—Supported Real-Time Counters utilization data report, how to generate 7-8 advanced mode 8-23 8-17 calculate percentages 7-7 modify 8-20 user session, ending active user table, vi
Index VXSM ATM statistics, connections VXSM cards, configuring What Network Elements Are Available to a Network Planner? 3-1 D-7, D-8 6-61 VXSM Ephemeral Termination protocol statistics D-47 10-2 What Types of Data Reports Are Available? VXSM Features tab displaying RUDP 9-26 displaying XGCP 9-27 10-9 Where Can I Get Information on Affected Services and Customers? 9-3 Where Can I See the Performance Data? VXSM H.
Index Cisco Media Gateway Manager 5.
