-
Cisco Media Gateway Control Node Manager User's Guide, 2.3.1
-
Preface
-
Overview of Cisco MGC Node Manager
-
Planning and Installation
-
Configuring Network Devices
-
Getting Started with Cisco MGC Node Manager
-
Setting Up Security
-
Deploying Your Network
-
Managing Faults with Cisco MNM
-
Managing Performance of Cisco MNM Devices
-
Other Network Management Tasks
-
System Administration
-
Appendix A - Alarm Message Reference
-
Appendix B - Performance Measurements Reference
-
Appendix C - Troubleshooting
-
Table Of Contents
Overview of Cisco Media Gateway Controller Node Manager
Overview of the Cisco MGC Node Architecture
How Cisco EMF Models the Network
How Cisco MNM Models the Network
The Cisco MGC Host Signaling, Trunking, and Dial Plan Components
Cisco MGC Host Trunking Objects
Cisco MGC Host Dial Plan Objects
Overview of Cisco Media Gateway Controller Node Manager
This chapter includes:
•
A description of key features of Cisco MNM
•
•
Introduction
Cisco Media Gateway Controller Node Manager (Cisco MNM) integrates the management interfaces and management functionality of the Cisco MGC node components into one comprehensive human interface and data repository. The Cisco MGC node consists of the Cisco MGC host, one or more Cisco Signaling Link Terminals (Cisco SLTs) or SLT functions integrated in the AS5350 or AS5400 access servers and the Cisco Catalyst 5500, Catalyst 6509, or Catalyst 2900 XL LAN switch. Optionally, the node may include a Billing and Measurement Server (BAMS) and H.323 Signaling Interface (HSI) server associated with the Cisco PGW (see Figure 1-1). Cisco MNM provides fault, configuration, and performance management for all components of the Cisco MGC node.
Cisco MNM provides the element-specific management features for the Cisco MGC node. It blends the management framework features of the Cisco Element Management Framework (Cisco EMF) with the individual interfaces and object structures of each managed element to produce an integrated management application.
Note
Figure 1-1 Cisco MGC Node Manager with Cisco MGC Node Detail
Terms Used in This Document
The following terms are used in this document:
•
•
•
•
•
•
•
•
Overview of the Cisco MGC Node Architecture
The Cisco MGC is key to Cisco's voice domain solutions.
The Cisco MGC node is comprised of a combination of the following components:
•
•
The Cisco SLT consists of a customized Cisco IOS Release 12.0(7)XR software image running on a Cisco router.
The integrated Cisco SLT consists of a customized Cisco IOS Release 12.0(7)XR software image running on an AS5350 or AS5400 access server.
•
A Cisco Catalyst 2900XL, 5500, or 6509 can be used as the LAN switch.
•
•
A Cisco MGC node is (optionally) fully redundant. This means that each Cisco MGC might have multiples of each type of subcomponent. At any given time, one Cisco MGC host is considered active and the other standby. If the active Cisco MGC host fails, the standby host becomes active. There is no concept of active or standby with the LAN switches or Cisco SLTs; if two are present, both are active at all times, providing redundancy.
Note
Key Features of Cisco MNM
The most common Cisco EMF installation includes plug-in modules referred to as Element Managers or Element Management Systems (EMS). In the Cisco MGC node architecture, Cisco MNM is a Cisco EMF-based EMS responsible for managing the Cisco MGC node. Cisco MNM adds specific graphical user interface (GUI) windows and modeling behavior to the standard Cisco EMF system to allow the management of specific network elements.
Cisco MNM uses Cisco EMF to manage the following components of the Cisco MGC node:
•
•
•
•
•
The key features of Cisco MNM are:
•
Cisco MNM provides fault management of the Cisco MGC node (the Cisco MGC host, the Cisco SLT, the Cisco LAN switch, HSI server, and BAMS). You see the alarms generated by these elements in the Cisco MNM system.
When the Cisco MGC host detects a problem with one of its logical connections, it generates a trap. Cisco MNM receives these traps and delegates them to the graphical object that represents that logical connection. For example, if Cisco MNM receives a trap that the link to a media gateway is down, Cisco MNM delegates that trap to the object that represents the media gateway link. You can acknowledge and clear alarms and forward traps.
In order to make the identification of potential problems easy, Cisco EMF propagates the alarm state of network elements upwards through the node and physical views. If an object receives an alarm, it changes color to reflect its new state, and all parent objects also change color to reflect the most severe alarm on any of the children.
Cisco MNM periodically polls each managed object to ensure that the device is still reachable using SNMP. If the device is not reachable, an annotation appears on the display in the Map Viewer, an alarm is generated, and the object is placed in an error state. After the object loses connectivity, Cisco MNM continues to poll the object until it can be reached. Once connectivity is re-established, the alarm is cleared, the annotation on the Map Viewer is removed, and the object is returned to the normal state.
For more information on fault management, see "Managing Faults with Cisco MNM."
•
Cisco MNM collects and displays performance information from the Cisco MGC node, helping you to monitor the health and performance of the network. Cisco MNM collects performance information from all the components of the Cisco MGC node.
You can:
–
–
–
–
•
Cisco MNM supports role-based access to its management functions. The administrator defines user groups and assigns users to these groups. Cisco MNM supports control of administrative state variables for Cisco MGC node resources. For more information on access control, see "Setting Up Cisco MNM Security."
•
Third-party billing packages are supported directly by the BAMS Server, an optional component of the Cisco MGC node.
•
You can open the following configuration tools from Cisco MNM:
–
–
–
•
Cisco MNM provides a full range of diagnostic and troubleshooting tools, such as IP and SNMP Ping, Alarm and System Log, Host Status Check, Cross-Device Audit, and the Cisco MGC Toolbar that includes CDR Viewer, Log Viewer, Trace Viewer, and Translation Verification Viewer.
Overview of Cisco EMF
Cisco MNM is based on the Cisco Element Management Framework (Cisco EMF), a carrier-class network management framework. This framework was designed to address the challenges of developing and deploying robust, large-scale, multivendor, multitechnology management solutions.
Cisco EMF has been designed to overcome the limitations of traditional enterprise network management solutions, particularly in the broadband access market and also in other network management applications where the aforementioned characteristics are important. Cisco EMF is used to quickly develop and deploy element, network, and service-level applications in technologies ranging from Digital Subscriber Line (DSL), used for high-speed Internet access; cable modems; and Voice over IP to complex ATM/IP routing multiservice switches.
Cisco EMF Components
Cisco EMF consists of:
•
•
Network Operations Center users typically interact with the Cisco EMF Client software by connecting from an X terminal workstation. Cisco MNM supports over 10 active, concurrent sessions.
Figure 1-2 Cisco EMF Processes
.
Cisco EMF comes with the following set of applications accessed from the Launchpad (see Figure 1-3) that opens when you start a Cisco MNM session:Figure 1-3
•
•
•
•
•
•
–
–
–
–
Netscape also displays a link to the Cisco Documentation Disk 2 CD-ROM, if it exists in the local CD-ROM drive.
•
–
–
–
Figure 1-3 Cisco EMF Launchpad Screen
How Cisco EMF Models the Network
Cisco EMF keeps a model of the managed network in its database. Cisco EMF uses this model to keep track of the current state of the network and network elements.
The Cisco EMF model of the network uses the following components:
•
An object can represent:
–
–
–
–
•
In the Map Viewer application, the class of the object is indicated with an icon used within the Map Viewer browser.
TClasses enable you to perform powerful queries on different objects. Examples of this type of query could be to show all events in the system from Cisco SLTs or to create a group of Cisco LAN Switch objects.
•
These attributes are associated with the object according to the granularity of object types. A type is simply a collection of related attributes, and each class usually has a number of types. An object's class defines which types and, therefore, which attributes it is allowed to have and which types it has by default.
An example of the association between classes and types is shown in Figure 1-4.
Figure 1-4 Example of Object Types and Attributes
.
In Figure 1-4, a UNIX Workstation class is specified. This class of object includes two types: System and snmpManageable. The System type includes the sysDesc, sysUpTime, and sysObjectId attributes. The snmpManageable type includes the read-community and write-community attributes.
•
•
Object groups can be built either manually or by building a query and are accessible through the Object Group Manager application.
How Cisco MNM Models the Network
Cisco MNM applies the Cisco EMF network object model to the Cisco MGC node. The hub of Cisco MNM network management is the Map Viewer. From the Map Viewer you can access network objects by navigating through one of the views to find the object. Each view represents a different way of containing and grouping the objects, such as by device type, by Cisco MGC node, and by physical or network view. Cisco MNM views are summarized in Table 1-1 and described on the following pages.
Note
Table 1-1 Cisco MNM Views in the Map Viewer
MGC-Node-View
Displays all of the Cisco MGC nodes in the network along with their logical children (Cisco SLTs, switches, and Cisco MGC hosts) and propagates child alarms to the parents. This view also includes all of the signaling, dial plan, and trunking components of the Cisco MGC node. For more information, see "The MGC Node View" section. If you are using BAMS Phase 3, this view displays each BAMS node associated with the MGC.
Host-View
Presents all of the Cisco MGC host devices in the network. For more information, see "The Host View" section.
SLT-View
Presents all of the Cisco SLT devices in the network, including integrated SLTs and integrated SLT coresident EMs. This view also contains all of the interfaces on each Cisco SLT. For more information, see "The SLT View" section.
Switch-View
Presents all of the LAN switch devices in the network. This view also shows all of the interfaces on each LAN switch. For more information, see "The Switch View" section.
BAMS-View
Presents all of the BAMS in the network. For more information, see "The BAMS View" section.
HSI-View
Presents all HSI devices in the network. For more information, see "The HSI View" section.
Physical
Displays all of the Cisco MGC network devices, grouped by physical location (buildings, sites, or regions), and propagates child alarms to the parents. For more information, see "The Physical View" section.
Network
Displays all IP devices within their relative networks and subnets. This is a standard Cisco EMF View. For more information, see "The Network View" section.
The MGC Node View
The MGC node view displays all of the Cisco MGC node elements in the network. For each Cisco MGC node, all of the logical components of the node are displayed, as illustrated in Figure 1-5.
Figure 1-5 MGC Node View
.
Each Cisco MGC node is represented with its child elements. These child elements include the Cisco MGC hosts, BAMS, HSI server, Cisco SLTs (including integrated SLTs and integrated SLT coresident EMs), and LAN switches, and each device's network interfaces. Depending on the configuration, there can be a maximum of two Cisco MGC host devices (active/standby pair), two BAMS (active/standby pair), two or more HSI servers, eight Cisco SLTs, and two LAN switches.
Note
In addition to the physical devices, the logical configuration of the active Cisco MGC host is also displayed. This logical configuration includes the signaling, trunking, and dial plan information from the active Cisco MGC host.
The Cisco MGC Host Signaling, Trunking, and Dial Plan Components
This section provides information about how Cisco MNM models the following components in the node view:
•
•
•
Cisco MGC Host Signaling Network
Cisco MNM displays the status of the Cisco MGC host signaling network on the Map Viewer interface. This includes showing the status of the logical connections from the active Cisco MGC host to the:
•
•
•
•
•
•
•
•
When the common Cisco MGC host object is first deployed, the object database is populated with objects that represent the logical connections from the active Cisco MGC host to the external devices. Cisco MNM then monitors the status of these connections and informs you of any loss of connectivity.
As new connections are deployed, the signaling network is updated to reflect the current configuration and network status of the active Cisco MGC host.
Cisco MNM monitors the status of the signaling network by processing and decoding alarms, known as traps, from the active Cisco MGC host. Upon receipt of an appropriate trap, Cisco MNM maps the trap to the node representing the logical connection, and an alarm associated with the node is displayed.
Cisco MNM communicates to the Cisco MGC host using:
•
•
•
Cisco MGC Host Signaling Objects
The Cisco MGC host software defines over 20 different types of network signaling component types. Cisco MNM queries the configuration of the active Cisco MGC host and represents the objects in the display.
The hierarchical structure or relationship of the components is based on the configuration defined by the active Cisco MGC host. This configuration can vary from installation to installation. Cisco MNM, however, is able to handle any type of configuration present on the host.
Cisco MNM defines a class to represent each network signaling element type. For example, there is a class for an IP link, point code, and external node. The attributes associated with each class exactly match the attributes of the MML command used to provision the object.
Table 1-2 describes the classes used to represent the signaling network in Cisco MNM.
Containment Hierarchy of the Signaling Network
When Cisco MNM retrieves the current configuration from the active Cisco MGC host, it establishes the containment hierarchy of the signaling network. An example is shown in Figure 1-6.
Figure 1-6 Hierarchical Example of Signaling Components
In the MML file, the destination point code (DPC) component represents a switch. The adjacent point code (APC) component represents an STP.
The external node component in the MML file represents one of a number of different elements. These include:
•
•
•
Cisco MGC Host Trunking Objects
Cisco MNM models all of the trunk groups on the active Cisco MGC host and makes trunk information available to northbound systems. Trunks represent the physical bearer channels, while trunk groups provide a higher-level grouping of trunks.
Trunk group components are stored in a separate logical folder, the Trunking Components folder. When the Cisco MGC host is using switched trunks, each trunk group is shown in the folder. In the case of nailed trunks, the Cisco MGC host does not have any trunk groups, and so no folder is created.
Cisco MNM defines a class to represent each type of trunking component. The attributes associated with each class typically match the attributes in the MML command used to provision the component.
The classes used to represent the trunking objects in Cisco MNM are described in Table 1-3.
Table 1-3 Classes Representing Trunking Objects
nailedtrnk
Nailed trunk component
switchtrnk
Switched trunk component
trnkgrp
Trunk group component
Containment Hierarchy of the Trunking Objects
When Cisco MNM retrieves the current configuration from the active Cisco MGC host, it establishes the containment hierarchy of the trunking objects. A hierarchical model example is shown in Figure 1-7.
Figure 1-7 Hierarchical Model Example of Trunking Objects
Cisco MGC Host Dial Plan Objects
Cisco MNM models the dial plan components on the active Cisco MGC host. The dial plan allows the Cisco MGC to perform pre-analysis, calling (A) number analysis, called (B) number analysis, and cause analysis. The routing components of the dial plan are used to identify the path for bearer traffic from the Cisco MGC host to its adjacent switch.
As with trunking components, dial plan components are stored in a separate folder.
Cisco MNM defines a class to represent each type of dial plan component. The attributes associated with each class typically match the attributes in the MML command used to provision the component.
The classes used to represent the dial plan objects in Cisco MNM are described in Table 1-4.
Containment Hierarchy of the Dial Plan Objects
When Cisco MNM retrieves the current configuration from the active Cisco MGC host, it establishes the containment hierarchy of the dial plan objects. A hierarchical model example is shown in Figure 1-8.
Figure 1-8 Hierarchical Model Example of Dial Plan Objects
The Host View
The Host View displays all of the Cisco MGC host devices along with their associated interfaces and system components, as illustrated in Figure 1-9.
Figure 1-9 Host View
.
This view collects all Cisco MGC hosts in a single location from which functions can be opened.
The SLT View
The SLT View displays all of the Cisco SLT devices in the network along with their associated interfaces, as illustrated in Figure 1-10.
Figure 1-10 SLT View
.
This view is used to collect all Cisco SLTs in a single location.
Note
The Switch View
The Switch View displays all of the LAN switches in the network. In addition, the slots and ports on the LAN switches are displayed, as illustrated in Figure 1-11.
Figure 1-11 LAN Switch View
.
This view is used to collect all LAN switches in a single location for viewing events or starting functions.
Note
The BAMS View
The BAMS View displays all of the BAMS in the network. For each BAMS, the network interfaces of the BAMS are displayed. In addition, each Cisco MGC host that is communicating with the BAMS is shown, as illustrated in Figure 1-12.
Figure 1-12 BAMS View
.
Each BAMS in the network is displayed, along with its network interfaces and system components. This view is used to collect all BAMS in a single location from which functions can be opened.
The HSI View
The HSI View displays all HSIs in the network. For each HSI, the network interfaces and the associated IP addresses and system components are displayed. This view is used to view faults and start services.
.
The Physical View
Cisco MNM uses the Physical View to represent the physical location of devices. You are free to set up different types of groupings based on the physical layout of your network.
You can create sites and regions to represent the physical locations of devices in your network. When Cisco MGC node devices are deployed, you can specify the physical location of these devices in one of the predefined regions or sites. In this way, you can use the PhysicalView to quickly see which network elements are at a given location. If a device fails, network operations center (NOC) operators can easily see where personnel should be dispatched.
An example of the Physical View is shown in Figure 1-13.
Figure 1-13 Physical View
.
During deployment you place devices in each region or site. Relationships between objects at a given site are not shown (these relationships are shown in other views); all devices in a given site are at the same level. Because the Cisco MGC node is not a physical device, it is not represented in this view.
The Network View
The Network View groups all IP-enabled devices in containers based on their subnet address. This view is a standard Cisco EMF view and is not controlled or managed in any way by Cisco MNM. With the Network View, you can see all of the devices on a particular subnet. This view is not often used in the typical Cisco MGC solution.
