|
|
This chapter presents operations and maintenance tasks related to the Cisco ASAP Solution and the PSTN gateway solutions that are provided from the application Cisco Media Gateway Controller Node Manager (Cisco MNM). Cisco MNM is a comprehensive element management system that operates and maintains the Cisco SC2200 (also known as the Cisco PGW 2200), as well as related network components, by integrating management interfaces and functionality into a single interface and data repository. With this application you can manage security; deploy a site, object, or network; use polling to monitor network performance; manage traps and events; and view information about network devices. The tasks in this chapter are listed below.
 |
Note The Cisco PGW 2200 configured for signaling is also referred to in a variety of documents as the Cisco SC2200, the earlier term. The term "Cisco SC2200" is applicable to the Cisco ASAP Solution and Release 1.3 of the Cisco SS7 Interconnect for Voice Gateways Solution, and the term "Cisco PGW 2200" is applicable to the Cisco PSTN Gateway Solution and Release 2.0 of the Cisco SS7 Interconnect for Voice Gateways Solution. |
This chapter presents the following major management topics:
 |
Tip See also Task Summary. |
The Cisco MGC Node Manager manages the following components of the Cisco ASAP Solution and the PSTN gateway solutions: Cisco MGC (Cisco SC2200/Cisco PGW 2200), Cisco SLT (Cisco 2611 or 2651), Cisco Catalyst 5500 switch, and Cisco BAMS.
Cisco MGC Release 7 (for the Cisco ASAP Solution and Release 1.3 of the Cisco SS7 Interconnect for Voice Gateways Solution) and Cisco MGC Release 9 (for Cisco PSTN Gateway Solution and Release 2.0 of the Cisco SS7 Interconnect for Voice Gateways Solution) require different versions of Cisco MNM. This chapter refers to procedures in Cisco MNM Release 1.5 only.
For the following procedures, refer to Cisco Media Gateway Controller Node Manager User's Guide 1.5 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel8/cmnmgr/
|
Note Cisco MNM is built on the Cisco Element Management Framework (CEMF), a carrier-class network management framework. To understand this framework, refer to the section Overview of CEMF in the above document. |
For documentation or Cisco MNM Release 2.1, refer to Cisco Media Gateway Controller Node Manager User's Guide, Version 2.1 at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/access/sc/rel9/cmnm21/index.htm
The tasks in this chapter are listed below, grouped by major category.
Summary | You must configure a variety of SNMP parameters (SNMP community strings, SNMP trap destinations, other miscellaneous SNMP settings) on a device before Cisco MNM can manage it. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch (see Note below), Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
|
Note The only LAN switch supported by Cisco MNM is the Cisco Catalyst 5500. |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To create, modify, or delete a UG group:
Step 1 In the above reference, refer to Chapter 3, "Configuring Network Devices for Management."
Step 2 Read the section Introduction to Device Configuration.
Step 3 As appropriate, follow the steps in one or more of the following sections:
a. Configuring the Cisco MGC
b. Configuring a Cisco SLT (Cisco 2611)
c. Configuring the LAN Switch (Catalyst 5500)
d. Configuring Cisco BAMS
Summary | Cisco MNM allows system administrators to control user access and user privileges. User accounts can be collected into user groups, and lists of accessible features can be established for a user. Tasks include setting up new accounts, creating new access specifications, creating typical types of users, modifying users, modifying user groups, modifying access specifications, and changing the administrative password. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To set up Cisco MNM security:
Step 1 In the above reference, refer to Chapter 5, "Setting Up CMNM Security."
Step 2 Read the section Introduction to Cisco MNM Security. That section lists and describes ready-made feature lists.
Step 3 As appropriate, follow the steps in one or more of the following sections:
a. Setting Up New Accounts
b. Creating User Groups
c. Creating New Access Specifications
d. Creating Typical Types of Users
e. Modifying Users
f. Modifying User Groups
g. Modifying Access Specifications
h. Changing the Administrative Password
Summary | Deployment is the addition of objects (sites, objects, or networks) to the CEMF network model. Cisco MNM allows you to deploy Cisco MGC nodes and subobjects either in bulk, through the use of a seed file, or manually. This task relates to the use of a seed file to deploy a Cisco MGC network. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To use a seed file to deploy a Cisco MGC network:
Step 1 In the above reference, refer to Chapter 6, "Deploying a Site, Object, or Network."
Step 2 Read the sections Introduction to Deployment and Deploying a Network Using a Seed File.
Step 3 Read the section Specifying a Deployment Seed File and follow the steps therein.
Summary | Deployment is the addition of objects (sites, objects, or networks) to the CEMF network model. Cisco MNM allows you to deploy Cisco MGC nodes and subobjects either in bulk, through the use of a seed file, or manually. This task relates to the manual deployment of a Cisco MGC network. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To deploy a site, object, or network manually:
Step 1 In the above reference, refer to Chapter 6, "Deploying a Site, Object, or Network."
Step 2 Read the sections Introduction to Deployment and Manually Deploying a Site, Object, or Network.
Step 3 Open the deployment wizard. Refer to the section Opening the Deployment Wizard.
Step 4 As appropriate, follow the steps in one or more of the following sections:
a. Deploying a Cisco MGC Node
b. Deploying a Cisco MGC Host
c. Deploying a Cisco SLT
d. Deploying a LAN Switch
e. Deploying a Billing and Measurements Server (Cisco BAMS)
Summary | When a Cisco SLT, LAN switch, Cisco MGC host, or BAMS is deployed, its subrack components are queried and deployed. Cisco MNM can discover the subrack components, and their relationships, of these devices. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To discover a Cisco SLT, LAN switch, Cisco MGC host, or BAMS:
Step 1 In the above reference, refer to Chapter 6, "Deploying a Site, Object, or Network."
Step 2 Read the section Subrack Discovery. Discovery varies according to the type of device or object.
Step 3 As appropriate, read the following sections for the type of discovery desired:
a. To discover a Cisco MGC host, BAMS, or unknown/unsupported device, read Cisco MGC Host and BAMS Discovery.
b. To discover a Cisco SLT, as well as TDM (DS1) interfaces and SS7 channels, read Cisco SLT Discovery.
c. To discover slots, VLANs, and ports on a Cisco Catalyst 5500 series LAN switch, read Catalyst 5500 Discovery.
d. To discover a Cisco MGC node, including trunking, signaling, and dial plan components, read Cisco MGC Node Discovery.
Summary | Cisco MNM lets you manage software images and configuration files on Cisco MGC nodes. Tasks include backing up (uploading) and restoring (downloading) configurations of the Cisco MGC host, BAMS, Cisco SLT, and LAN switch; downloading software modules and patches to Cisco MGC nodes; backing up software images from a Cisco SLT or LAN switch; and automating or scheduling configuration backups. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To upload or download an image or configuration file for a Cisco SLT, LAN switch, Cisco MGC host, or BAMS:
Step 1 In the above reference, refer to Chapter 6, "Deploying a Site, Object, or Network."
Step 2 Read the section Managing Software Images and Configurations.
Step 3 As appropriate, follow the steps in one or more of the following sections:
a. Uploading and Downloading Cisco SLT and LAN Switch Images and Configurations
b. Uploading and Downloading Cisco MGC Host and BAMS Images and Configurations
Summary | Cisco MNM lets you monitor performance statistics gathered from network elements. Tasks include setting polling frequencies; starting and stopping polling; decommissioning, rediscovering, and rebooting devices; viewing (graphing) performance data; viewing raw data; viewing charts; viewing logs; exporting performance data; and printing performance files. These tasks relate to viewing and managing performance data. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To view, archive, export, and print performance data:
Step 1 In the above reference, refer to Chapter 7, "Using Polling to Monitor Network Performance."
Step 2 Read the section Viewing Performance Data and follow the steps therein to set a variety of parameters and view the data of interest.
Step 3 As appropriate, follow the steps in one or more of the following sections:
a. Viewing Raw Data
b. Viewing a Chart
c. Viewing a Performance Log
d. Setting How Performance Data is Archived
e. Exporting Performance Data
f. Printing a Performance File
Summary | Cisco MNM lets you monitor performance statistics gathered from network elements. Tasks include setting polling frequencies; starting and stopping polling; decommissioning, rediscovering, and rebooting devices; viewing (graphing) performance data; viewing raw data; viewing charts; viewing logs; exporting performance data; and printing performance files. These tasks relate to setting polling frequencies and start and stop times, as well as decommissioning, rediscovering, and rebooting device. Decommissioning a device prevents it from being presence polled or performance polled. Commissioning it reinstates presence polling. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To set polling parameters and determine which devices are to be polled:
Step 1 In the above reference, refer to Chapter 7, "Using Polling to Monitor Network Performance."
Step 2 Read the sections Introduction to Performance Monitoring and How Performance Data is Collected. Note the performance counters and their descriptions for the various components and network interfaces
Step 3 Read the section Cisco MGC Host Configuration Performance Counters. There are a number of files on the Cisco MGC host that select performance counters and determine their frequency of collection. There are also measurement filters you can apply.
Step 4 Open the Performance Manager. Refer to the section Opening the Performance Manager and follow the steps therein.
Step 5 Read the section Setting Polling Frequencies.
Step 6 As appropriate, follow the steps in one or more of the following sections:
a. Changing Collection Defaults
b. Setting Different Polling Frequencies
c. Decommissioning, Rediscovering, and Rebooting Devices
d. Starting Polling on a Device
Summary | Critical to network management is the ability to identify specific undesirable system events (faults) and resolve them as soon as possible. Traps are connectivity-related messages about various events that are generated by an element. Traps are converted to alarms, which are displayed in the Cisco MNM Event Browser. An event is a notification from a managed entity that a certain condition has just occurred. Usually events represent error conditions on managed elements. These tasks relate to managing, clearing, and forwarding connectivity traps for Cisco MGC components. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To manage, clear, and forward traps and events on Cisco MGC components:
Step 1 In the above reference, refer to Chapter 8, "Managing Traps and Events."
|
Note As appropriate, apply the information presented in any or all of the following sections. |
Step 2 Read the sections Introduction to Fault Management, How CEMF Models Events, How Cisco MNM Manages Faults, and Presence/Status Polling.
Step 3 To manage traps, read the section How Traps are Managed for Network Devices. Note the alarms/traps definitions and explanations, as well as related MIBs, for the following components: Cisco SLT, Cisco Catalyst LAN switch, and Cisco MGC host.
Step 4 To clear traps, read the section How Traps Are Cleared Using Correlation Files. CEMF Clear Correlation files are used to clear traps for a Cisco MGC host, a Cisco SLT, and a Cisco Catalyst LAN switch.
Step 5 To forward traps (to northbound management systems), read the section Forwarding Traps to Other Systems and follow the steps therein. See Special issues, below.
Summary | Critical to network management is the ability to identify specific undesirable system events (faults) and resolve them as soon as possible. Traps are connectivity-related messages about various events that are generated by an element. Traps are converted to alarms, which are displayed in the Cisco MNM Event Browser. An event is a notification from a managed entity that a certain condition has just occurred. Usually events represent error conditions on managed elements. These tasks relate to managing events. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To manage, clear, and forward traps and events on Cisco MGC components:
Step 1 In the above reference, refer to Chapter 8, "Managing Traps and Events."
|
Note As appropriate, apply the information presented in any or all of the following sections. |
Step 2 Read the sections Introduction to Fault Management, How CEMF Models Events, How Cisco MNM Manages Faults, and Presence/Status Polling.
Step 3 To use the Event Browser, read the sections Opening the Event Browser and Overview of the Event Browser Screen.
Step 4 To filter events, read the section Filtering Events Using Queries. As appropriate, follow the steps in one or both of the following subsections:
a. Setting Filter Criteria
b. Modifying Filter Criteria
Step 5 To sort events, read the section Sorting Events and select the sorting options as appropriate.
Step 6 To manage events, read the section Managing Events. Ass appropriate, follow the steps in one or both of the following subsections:
a. Managing an Event from the Window
b. Managing an Event from the Menu Bar
Step 7 To view incoming events that are automatically updated in the Event Browser window, read the section Enabling Auto or Manual Update and select the auto option as appropriate. Deselect the option to revert to manual update mode.
Step 8 To color code events, read the section Setting How Events Are Color-Coded and select the appropriate option.
Step 9 To view event history, read the section Viewing the Event History and follow the steps therein. Note also the following related tasks:
a. Refreshing the Event Window
b. Viewing a Full Description of an Event
Summary | Critical to network management is the ability to identify specific undesirable system events (faults) and resolve them as soon as possible. Traps are connectivity-related messages about various events that are generated by an element. Traps are converted to alarms, which are displayed in the Cisco MNM Event Browser. An event is a notification from a managed entity that a certain condition has just occurred. Usually events represent error conditions on managed elements. You can manage Cisco MGC host faults and performance from the MGC Toolbar. These tasks relate to using the Cisco MGC toolbar to view alarms, measurements, CDRs, log files, and trace files, as well as to perform other management activities. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To use the Cisco MGC toolbar for miscellaneous management tasks:
Step 1 In the above reference, refer to Chapter 8, "Managing Traps and Events."
|
Note As appropriate, apply the information presented in any or all of the following sections. |
Step 2 Read the section Using the Cisco MGC Tool Bar. As appropriate, follow the steps in one or more of the following sections.
a. To view or search alarms and measurements, read the section Alarm and Measurements View and follow the steps therein.
b. To view or search call data records (CDRs), read the section CDR Viewer and follow the steps therein.
c. To view the contents of the configuration library, read the section CONFIG-LIB Viewer and follow the steps therein.
d. To view or search a log file, read the section Log Viewer and follow the steps therein.
e. To view a trace file, read the section Trace Viewer and follow the steps therein.
f. To verify a translation, read the section Translation Verification and follow the steps therein.
g. To manage the files associated with the Cisco MGC tool bar, read the section File Options and follow the steps therein.
Summary | Critical to network management is the ability to identify specific undesirable system events (faults) and resolve them as soon as possible. Traps are connectivity-related messages about various events that are generated by an element. Traps are converted to alarms, which are displayed in the Cisco MNM Event Browser. An event is a notification from a managed entity that a certain condition has just occurred. Usually events represent error conditions on managed elements. All alarms are automatically stored in the CEMF database. CEMF does not archive old alarms, but it can be configured to delete alarms of a specific age and state. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To set how long alarms are stored:
Step 1 In the above reference, refer to Chapter 8, "Managing Traps and Events."
Step 2 Read the section Setting How Long Alarms Are Stored and follow the steps therein.
Summary | You can use Cisco MNM to view a considerable amount of information related to Cisco MGC components: Cisco MGC host accounts, properties, and file systems; Cisco SLT accounts and properties; LAN switch accounts and properties; BAMS accounts, properties, and file systems; CIAgent device information; and Ethernet, TDM, and serial interface properties. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To view available information about network devices:
Step 1 In the above reference, refer to Chapter 9, "Viewing Information About Network Devices."
Step 2 Read the sections Introduction and Viewing Accounts and Properties. As appropriate, read the following sections and follow the steps therein:
a. Viewing Cisco MGC Host Accounts
b. Viewing Cisco MGC Host Properties
c. Viewing Cisco MGC Host File Systems
d. Viewing Cisco SLT Accounts
e. Viewing Cisco SLT Properties
f. Viewing LAN Switch Accounts
g. Viewing LAN Switch Properties
h. Viewing BAMS Accounts
i. Viewing BAMS Properties
j. Viewing BAMS File Systems
k. Viewing CIAgent Device Information
l. Viewing Ethernet Interface Properties
m. Viewing TDM Interface Properties
n. Viewing Serial Interface Properties
Summary | Cisco MNM provides a number of tools to monitor the health of network elements. These include ping and traceroute, as well as diagnostic and configuration tools that depend on the type of device being tested. Cisco MNM also provides an entire suite of tools for testing the operating status of the MGC host. Other diagnostic tasks include initiating a configuration audit, retrieving alarm logs, and monitoring file systems on devices where the supported SNMP agent is installed. |
Target Platform(s) | Cisco MGC (Cisco SC2200), Cisco SLT (Cisco 2611), Cisco Catalyst 5500 switch, Cisco BAMS |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To use diagnostic tools, initiate a configuration audit, retrieve alarm logs, or monitor file systems:
Step 1 In the above reference, refer to Chapter 9, "Viewing Information About Network Devices."
Step 2 To use a variety of diagnostic and configuration tools, read the section Using Diagnostic Tools and select the tools appropriate to the device in question.
Step 3 To view the status of the MGC host, read the section MGC Host Status Check and select from among the operation commands.
Step 4 To initiate a configuration audit (which compares the trunking information on the BAMS to that on associated Cisco MGC hosts), read the section Configuration Audit and use the MML command therein.
Step 5 To retrieve alarms and process status, read the section Processes and Alarms and use the MML commands therein.
Step 6 To monitor file systems on devices where the supported SNMP agent is installed, read the section File System Monitor and follow the instructions therein.
Summary | The Cisco MNM Event Browser can display event messages related to the BAMS, the Cisco MGC, and Cisco MNM internal messages. With respect to BAMS and Cisco MGC, it provides references to relevant documentation. With respect to Cisco MNM internal even messages, it provides a short explanation of the message and recommended actions. Tasks include solving deployment and discovery errors once they are found. |
Target Platform(s) | BAMS host, Cisco MGC (Cisco SC2200), Cisco MNM host |
Application | See Introduction |
Frequency | As needed |
Cisco Media Gateway Controller Node Manager User Guide 1.5
For all related documentation, see References.
To view BAMS, Cisco MGC, or Cisco MNM internal event messages, as well as solve deployment or discovery errors:
Step 1 In the above reference, refer to Appendix A, "BAMS, Cisco MGC, and Cisco MNM Messages."
Step 2 To view BAMS or Cisco MGC host messages, read the section Looking Up BAMS and Cisco MGC Messages and follow the steps therein.
Step 3 To interpret Cisco MGC host messages, read the section Cisco MGC Host Messages and follow the instructions therein.
Step 4 To interpret BAMS messages, read the section BAMS Messages and follow the instructions therein.
Step 5 To interpret Cisco MNM internal event messages and take corrective action, read Cisco MNM Internal Messages and note the table therein.
Step 6 To solve deployment and discovery errors, read the section Solving Deployment and Discovery Errors. As appropriate, follow the steps in one or more of the following sections:
a. Changing Password or Community Strings
b. Changing IP Address
c. Rediscovering a Device After a Problem
Posted: Wed Oct 2 12:32:21 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.