|
|
Cisco MGM automatically discovers network elements and displays them on the Map Viewer screen. From this map you can view operational status and navigate to screens that support node configuration and software upgrades. This chapter includes the following network management topics:
Cisco MGM organizes Cisco MGX 8260 Media Gateway nodes by site. An MGX 8260 site contains all nodes with the same sysLocation attribute. The autodiscovery procedure queries the sysLocation value of each MGX 8260 chassis it discovers, and either adds the chassis to an existing site or creates a new one for it. If the sysLocation of a MGX 8260 chassis is an empty string, then it is added to default Cisco MGM site. MGX 8260 sites are displayed in hierarchy display only, not in the topology map. A Cisco MGM site remains in the system even if you delete all its nodes. Use Deployment>Delete Object to remove an empty site.
For more information on configuring the sysLocation, see Configuring System Parameters.
Automatic discovery occurs in two phases:
1. Automatic discovery of MGX 8260 nodes in a subnet
2. Subchassis synchronization of MGX 8260 subcomponents
You initiate Automatic Discovery from the Cisco EMF GUI by specifying the desired IP address range. Cisco EMF then automatically discovers MGX 8260 nodes with IP addresses that fall within this range. For more information, see the "Cisco MGM Community String Configuration" section.
When you initiate automatic discovery, Cisco EMF pings each IP addresses in the given range. If a response is received, it initiates an SNMP GET request for the enterprise object id (OID). If the OID matches any of the predefined Cisco EMF Class mappings, such as MGX 8260, an object of that class is created and displayed. If no mapping is found, the process creates a generic SNMP device under the Physical level of the hierarchy. Generic devices can't be managed.
To discover network elements, follow these steps:
<CEMF_ROOT>/cemf/bin/cemf session
Step 2 Log on to Cisco EMF. The Launchpad screen opens.
Step 3 Click the Discovery button. The Discover Network Devices screen opens.
Step 4 Configure the discovery parameters:
| Parameter | Description |
|---|---|
Device Name | Fixed as LaunchPad |
Device Address | The IP address from which to start the discovery process, expressed in standard dot notation |
Discovery Method | The method of discovery, IP, SNMP, or IP and SNMP. Specify SNMP to discover all MGX 8260 components. |
Hop Count | The number of routing hops to allow. Default: 0 |
Ping Retries | The number of times to ping each address in the range. Default: 1 |
SNMP Retries | The number of SNMP retries to allow. Default: 1 |
SNMP Timeout | The timeout of SNMP tries. Default: 10 |
New Community | Add or Remove SNMP communities. |
Physical Location | The physical path in the Cisco EMF hierarchy. Click Use Physical Path to use an existing path. |
Interface Attributes | The subnet and range of IP addresses to search. Double click to specify or change the range. |
Step 5 Click Start.
Step 6 At the end of the discovery process, click Close.
Subchassis synchronization searches for entities within a Cisco MGX 8260 Media Gateway and displays them on the user interface. This process is automatically invoked after autodiscovery.
Subchassis discovery inspects SNMP MIBs for the following configurable objects:
Upon completion of subchassis discovery, Cisco MGM adds the subchassis components to the site hierarchy display. You can expand the hierarchy to display cards and profiles by clicking the + sign next to the MGX 8260 icons. Similarly, you can expand the hierarchy to display lines by clicking the + sign next to each card. A number next to the MGX 8260 object indicates the number of contained cards or lines.
The SCC contains either SONET or Fast Ethernet lines. The NSCs contain Dsx1or E1 lines. The BSCs contains Dsx3 lines, which may be channelized for Dsx1 lines. DMCs contain Dsx3 lines that map to NSC Dsx1 lines.
You can manually invoke the subchassis syncup process from the pulldown menu of Cisco EMF GUI. The subchassis discovery process retrieves subchassis component information from each Cisco MGX 8260 Media Gateway and displays corresponding objects on the user interface.
To synchronize subchassis components, follow these steps:
Step 2 Click the Viewer button. The MapViewer screen opens.
Step 3 Expand the tree of objects to display the list of MGX 8260 sites and nodes.
Step 4 Right click the desired site or MGX 8260 node; then click Open SubChassis Sync Up. The SubChassis Sync Up screen opens.
Step 5 Select the desired MGX 8260 nodes from the list.
Step 6 Click Start Sync Up.
The system synchronizes the user display with subchassis components.
Periodic subchassis synchronization discovers the subchassis components of each Cisco MGX 8260 Media Gateway without user intervention. This background task runs on a fixed interval, once every 24 hours, rather than at a fixed time. Therefore, the time of day when this task runs depends on the last time the Cisco MGM controller was initialized.
The software download feature facilitates downloading of software image files for the System Controller Card (SCC), Narrowband Service Card (NSC), and Broadband Service Card (BSC) on multiple systems. Downloading the software does not automatically activate it; the system continues to operate on the current software until you perform the upgrade procedure. When downloading software images, Cisco MGM accepts a list of MGX 8260 nodes and the fully-qualified name of the image or configuration file. After download, the system reports successes and failures by chassis name.
To download software, follow these steps:
Step 2 Click the Viewer button. The Map Viewer screen opens.
Step 3 Expand the tree of objects to display the list of MGX 8260 sites and nodes.
Step 4 Right-click on the icon for the desired site; then click Open Software DownLoad Dialog. The Software Downlaod screen opens.
Step 5 Select one or more MGX 8260 nodes from the list.
Step 6 Enter the file information:
| Field | Description |
|---|---|
Image/Config Source File Name | The fully-qualified name and path of the file to download. |
Image/Config Destination File Name | The name of the software image or configuration file. The file format for a software image is: <card type>_<software version>.img.<key> The card type is scc, bsc, or nsc. The version indicates the major release, minor release, and version. The file extension is .img for software images and .cnf for configuration files. The key is the tftp security key for the destination chassis. You can view the key using the MGX 8260 command, lskey. For example: scc_r01.02.03.img.123456 indicates SCC software for release 1.2.3. The release and version information (r01.02.03) must be exactly 9 characters in length; the key (123456) is exactly 6 characters long. |
Step 7 Click Start Image/Config File Download.
The system downloads the software to each chassis and reports the results.
Step 8 Repeat steps 1 to 4 for other card images. Each card type in your system, such as SCC or BSC, has its own software image file.
The upgrade process for redundant cards is graceful and does not interrupt service. When you invoke the process, the system upgrades and restarts only the standby card. You then have the option to commit or cancel the upgrade. When you commit the software, the system switches to the standby card and then upgrades the other card.
 |
Warning Upgrading nonredundant cards interrupts service. Perform nonredundant upgrades during light traffic periods or during a prearranged maintenance window. |
Although you can download software in bulk to multiple nodes, you have to upgrade the software image manually, one card type at a time. You perform this task from the Cisco WebViewer tool.
To upgrade the software image:
Step 2 Log in as the SuperUser or a user with level 1 privileges
Step 3 Click Card>Up/Down Grade. The Upgradeable or Downgradeable Logical Card display opens.
Step 4 Click the + icon for the card you want to upgrade. The Upgrade Software Image and DBM form opens.
Step 5 Specify the name of the upgrade file.
| Parameter | Description |
|---|---|
Upgrade FileName | The name of the software image. This name indicates the card type, major release, minor release, and version, followed by the .fw extension. For example, SCC_R01.02.03.FW indicates SCC software release 1.2.3. The release and version information (R01.02.03) must be 9 characters in length. This name is the same as the downloaded file name except for the extension. |
Step 6 Click Up-Grade.
Step 7 For redundant cards, click Up-Grade Commit. The system switches to the standby card and upgrades the other one. If you don't want to use the new software, click Up-Grade Cancel.
 |
Note You cannot cancel an upgrade for nonredundant cards. |
Step 8 For redundant BSC or NSC upgrades, force a switchback. This is important because the standby card cannot protect the active card. To force a switchback, click Card>All-Cards; then click the S icon of the desired card.
Step 9 Repeat this procedure for each card type and each Cisco MGX 8260 Media Gateway.
Posted: Thu Jul 18 00:21:27 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.