|
|
Cisco Media Gateway Controller Node Manager (CMNM) 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 itself, one or more Cisco Signaling Link Terminals (Cisco SLTs) and the Catalyst 2900, Catalyst 5000, or Catalyst 5500 LAN switch. CMNM provides fault, configuration, and performance management for all components of the
Cisco MGC node.
CMNM provides the element-specific management features for the Cisco MGC node. It blends the management framework features of the Cisco Element Management Framework (CEMF) with the individual interfaces and object structures of each managed element to produce an integrated management application.
The following terms are used in this document:
You can use two different Cisco VSC3000 and Cisco SC2200 provisioning tools, depending on the network architecture you are running. If you are running the Cisco SS7 PRI Gateway Solution or the Cisco Tandem Offload Solution, you use VSPT. For all other architectures, you use CMM.
The Cisco Virtual Switch Controller (VSC) and the Cisco Signaling Controller (SC) (collectively referred to as the Cisco MGC) are key to Cisco's voice domain solutions.
The Cisco MGC node itself comprises the:
The standard Cisco MGC node design defines that a Cisco 2611 should be configured as the
Cisco SLT and that a Catalyst 2900XL, 5500, or 5000 should be used as the LAN switch.
A Cisco MGC node is (optionally) fully redundant. This means that each Cisco Virtual Switch Controller or Cisco Signaling Controller may actually have multiples of each type of subcomponent. At any given time, one Cisco MGC host is considered active and the other standby. When the active Cisco MGC host goes down, the standby host becomes active. There is no concept of active or standby with the LAN switches or Cisco SLTs (both are active at all times).
The most common form of a CEMF installation includes plug-in modules referred to as Element Managers or Element Management Systems (EMS). In the Cisco MGC node architecture, CMNM is a CEMF-based EMS that is responsible for managing the Cisco MGC node. CMNM adds custom graphical user interface (GUI) windows and modeling behavior to the standard CEMF system to allow the management of specific types of network elements. For more information about the Element Managers installed with CMNM, see Table 2-11 in the "Verifying Element Managers" section.
CMNM uses CEMF to manage the following components of the Cisco MGC node:
CMNM collects and displays performance information from the Cisco MGC node, allowing you to monitor the health and performance of the network. CMNM collects performance information from all the components of the Cisco MGC node.
For more information on performance monitoring, see "Using Polling to Monitor Network Performance."
CMNM provides fault management of the Cisco MGC node, including the Cisco MGC host, the
Cisco MGX 8260, the Cisco SLT, and the LAN switch. You see the traps generated by these elements in the CMNM system.
When the Cisco MGC host detects a problem with one of its logical connections, it generates a trap. CMNM receives these traps and delegates them to the object that represents that logical connection. For example, if CMNM receives a trap that the link to a media gateway is down, CMNM delegates that trap to the object that represents the media gateway link. You can acknowledge and clear alarms and forward traps.
CMNM 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 map display, an alarm is generated, and the object is placed in an errored state. After the object loses connectivity, CMNM continues to poll the object until it can be reached. Once connectivity is reestablished, 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 Traps and Events."
CMNM supports role-based access to its management functions. The administrator defines user groups and assigns users to these groups. CMNM supports control of administrative state variables for Cisco MGC node resources. For more information on access control, see "Setting Up CMNM Security."
Third-party accounting and billing packages are supported directly on the Billing and Measurements Server (BAMS), a component of the Cisco MGC node.
You can launch the following configuration tools from CMNM:
CMNM provides CDR Viewer, Log Viewer, Trace Viewer, and Translation Verification Viewer for diagnostic and troubleshooting information.
CMNM is based on the Cisco Element Management Framework (CEMF), 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.
CEMF 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. CEMF 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.
CEMF comes with the following set of applications:
CEMF keeps a model of the managed network within its database. This model is used to keep track of the current state of the various network elements and various abstractions of this network.
The CEMF model of the network uses the following components:
In the Map Viewer application, the class of the object is indicated with a different icon used within the Map View browser.
The use of classes also allows powerful queries to be carried out based upon the kind of object. Examples of this type of query could be: show all events in the system from cable modems or create a group of router 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-2.
In Figure 1-2, a UnixWorkstation 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.
You can access CEMF objects by navigating through one of the views to find the object. Each view represents a different way of containing and grouping the objects. The standard views provided are the Physical view and the Network view. CMNM adds additional views onto the standard set supplied by CEMF.
Object groups can be built either manually or by building a query. Object groups are accessible through the Object Group Manager application.
This section provides information about how CMNM models:
In CMNM, the network interfaces for the Cisco MGC host, BAMS, Cisco SLT, LAN switch, and
Cisco MGX 8260 are modeled. These include all Ethernet interfaces and, on the Cisco SLT, all time-division multiplexing (TDM) and serial interfaces.
Figure 1-4 shows a graphical view of the model.
CMNM displays the status of the Cisco MGC host connectivity 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 CEMF object database is populated with nodes that represent the logical connections from the active Cisco MGC host to the external devices. CMNM then monitors the status of these connections and, when necessary, informs you of any loss of connectivity.
As new connections are deployed, the connectivity network is updated to reflect the current configuration and network status of the active Cisco MGC host.
CMNM monitors the status of the connectivity network by processing and decoding traps from the active Cisco MGC host. Upon receipt of an appropriate trap, CMNM maps the trap to the node representing the logical connection. An alarm associated with the node is displayed.
The logical connections from the active Cisco MGC host are shown as subnodes under the common Cisco MGC host object. If the standby Cisco MGC host is not processing calls, only the network connectivity of the active host is shown.
CMNM communicates to the Cisco MGC host using:
The Cisco MGC host software defines over 20 different types of network connectivity component types. CMNM queries the configuration of the active Cisco MGC host and represents them 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. CMNM, however, is able to handle any type of configuration that may be present on the host.
CMNM defines a class representing each network connectivity 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.
The classes used to represent the connectivity network in CMNM are described in Table 1-1.
Table 1-1 Classes Representing Connectivity Network
When CMNM retrieves the current configuration from the active Cisco MGC host, it establishes the containment hierarchy of the connectivity network. A hierarchical model example is shown in Figure 1-5.
In the MML file, the destination point code (DPC) component represents a TDM switch. Likewise, 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:
To view the Network Connectivity Map:
Step 2 In the Physical view, navigate to the Cisco MGC host, expand its tree, then click the Connectivity icon.
You see a map of the network and object connections as shown in Figure 1-6.
Posted: Thu Feb 13 11:58:08 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
