Table Of Contents
Release Notes for Cisco Media Gateway Controller Node Manager Release 2.5(2)
Installation Procedure Checklist
Known Issues and Operational Recommendations
Cisco MGC Node Manager Checks for Available Disk Space For Installation
Cisco MGC Node Manager Cannot Discover an Interface or IP Address for BAMS
Initial Cisco MGC Node Manager Configuration
Installing CEMF/Cisco MGC Node Manager on a Server
Configuring the CEMF Software for Maximum Performance
Viewing Core Files Generated by CEMF and Cisco MGC Node Manager
Viewing the Most Recently Changed Log Files
Interesting Cisco MGC Node Manager Log Files
Error Messages That Are Safe to Ignore
Backing Up and Restoring the CEMF/Cisco MGC Node Manager Databases
Forcing an Uninstall of an Element Manager
Managing Network Devices Over a Slow Link
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco Media Gateway Controller Node Manager Release 2.5(2)
June 28, 2007
Contents
•
Installation Procedure Checklist
•
•
•
Introduction
The Cisco Media Gateway Controller (MGC) Node Manager (Cisco MGC Node Manager) is an element management system (EMS) for the Cisco Media Gateway Controller Node, a call control node based on the Cisco PGW 2200 Softswitch. Cisco MGC Node Manager provides basic management of the Cisco Media Gateway Controller Node devices including fault, configuration, performance and security.
Cisco MGC Node Manager 2.5(2) is built on version 3.2 of the Cisco Element Management Framework (CEMF) software package. This release adds support for Cisco MGC host call control software Release 9.5(2) and provides backward-compatibility across older versions of the software, including the 7.4(12) and 9.x releases. The Provisioning Tool formerly known as Cisco MGC Node Manager Provisioning Tool or MNM-PT in CMNM 2.5(2) release, now known as Voice Services Provisioning Tool (VSPT) is separated from MNM and becomes an independent tool again.
These release notes describe the features and caveats for Cisco MGC Node Manager. Please read this entire document prior to using Cisco MGC Node Manager as it contains pertinent information about installing, configuring, and using the software. This document provides up-to-date information about the current release of the Cisco MGC Node Manager from Cisco Systems, Inc.
For more information on the Cisco MGC Node Manager software, please visit Cisco's web site at:
http://www.cisco.com > Products and Services > Network Management > Cisco Media Gateway Controller Node Manager.
Note
Related Documentation
For installation instructions, see the Installation Guide available at
http://www.cisco.com/en/US/products/sw/netmgtsw/ps1912/prod_installation_guides_list.html
The Cisco MGC Node Manager User's Guide is available at
http://www.cisco.com/en/US/products/sw/netmgtsw/ps1912/products_user_guide_list.html
The Cisco Voice Services Provisioning Tool User's Guide contains information on getting started with VSPT and is available at
http://www.cisco.com/en/US/products/sw/netmgtsw/ps2272/products_user_guide_list.html
Software Release History
Release 2.5(2)
Release 2.5(2) Enhancements
Release 2.5(2) supports Cisco MGC Release 9.5(2) software.
Cisco MNM 2.5(2) adds support for managing the features new in Cisco MGC Release 9.5(2), as shown in Table 1. Enhancement identification numbers are listed where applicable.
Release 2.5(2) Open Caveats
Table 2 lists open caveats for this release.
System Requirements
The following is the minimum hardware and software you need to install and run Cisco MNM:
•
•
–
–
•
•
•
Detailed system requirements are documented in Chapter 1 of the Cisco MGC Node Manager Installation Guide at http://www.cisco.com/en/US/products/sw/netmgtsw/ps1912/products_user_guide_list.html.
Review this chapter prior to installing or configuring the software.
Note
Supported Configurations
These configurations are supported:
•
•
•
Note
Caution
Supported Network Elements
The following network elements have been tested and verified to work with this release 2.5(2) of the Cisco MGC Node Manager.
•
7.4(12), 9.2, 9.3(1), 9.3(2), 9.4(1) and 9.5(2)
•
2.68, 3.08, 3.10, 3.12, and 3.13
•
2.21 (backward compatible with 2.20), 4.1
•
5.x or higher
•
Cisco IOS Release 12.x
•
Cisco 2611 or 2651 router running Cisco IOS Release 12.1(x), 12.2(x)
Cisco 2611XM router running Cisco IOS Release 12.2(11)T2
•
Cisco AS5350 or AS5400 access server running Cisco IOS Release 12.2(15)T
•
Installation Procedure Checklist
Before installing the software, read Chapters 1 and 2 of the Installation Guide. If you are setting up a client/server architecture, then the CEMF and Cisco MGC Node Manager software must be installed on both the client and server workstations. The Cisco MGC Node Manager installation software determines whether the client or manager software should be installed.
•
•
–
The computer must have a valid entry in DNS.
–
•
Note
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Upgrade Procedure Checklist
The Cisco MGC Node Manager upgrade process enables you to easily upgrade from earlier releases.]
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Patch Procedure
The Cisco MGC Node Manager patch process is cumulative. Downloading and installing the latest patch installs all previous patches. The patch process automatically determines which portions of the Cisco MGC Node Manager need to be patched. In order for you to install a patch, the base Cisco MGC Node Manager software must be installed. Use the following steps to install the desired patch.
Step 1
Step 2
Step 3
Step 4
a.
b.
c.
d.
Step 5
zcat CSCOcmnmPatch_0x.tar.Z | tar xvf -Step 6
Step 7
Known Issues and Operational Recommendations
This section contains information about known issues and the corresponding workarounds.
Note
Cisco MGC Node Manager Checks for Available Disk Space For Installation
During installation, Cisco MGC Node Manager detects how much disk space is available for installation. If the system does not have enough available disk space, you are prompted whether you want to continue the installation routine. If you enter 'N' to stop the Cisco MGC Node Manager installation, the installation continues.
The workaround is to ensure that enough free disk space is available before Cisco MGC Node Manager is installed. The amount of disk space required is detailed in the Cisco MGC Node Manager installation guide.
Cisco MGC Node Manager Cannot Discover an Interface or IP Address for BAMS
Sometimes Cisco MGC Node Manager reports that it cannot discover an interface or IP address for BAMS. This might be caused by the mib2agt getting into a strange state. You can restart the mib2agt by stopping the current process. The new process mib2agt is restarted automatically.
ps -ef | grep mib2agt kill -9 <PID>Hints and Tips
Initial Cisco MGC Node Manager Configuration
Cisco MGC Node Manager is initially configured with one user:
id: admin password: adminInstalling CEMF/Cisco MGC Node Manager on a Server
If you have installed CEMF/Cisco MGC Node Manager on a server and need to change the IP address/hostname, you must make the changes shown in the following procedure:
Note
Step 1
Step 2
Step 3
MGRHOSTNAME=ramblerMGRIPADDRESS=10.1.1.1COREHOSTNAME=ramblerStep 4
MgrSystemManager=rambler1270; export MgrSystemManagerPortAllocator=rambler1270; export PortAllocatortransRouter=rambler1271; export transRouter;Step 5
MGRIPADDRESS=10.1.1.1MGRHOSTNAME=10.1.1.1COREHOSTNAME=10.1.1.1LOCALHOSTNAME=10.1.1.1Step 6
/var/sadm/pkg/hostEM/pkginfo/var/sadm/pkg/mgcEM/pkginfo/var/sadm/pkg/mgxEM/pkginfoStep 7
Note
Step 8
Configuring the CEMF Software for Maximum Performance
The following are guidelines for installing CEMF:
•
•
•
Mount the tmpfs file system to /tmp so the ObjectStore cache files can be kept in memory. ObjectStore is the database program included with CEMF. Keeping the cache files in memory provides for an enormous performance boost for CEMF. Here is how the tmpfs line should read in the /etc/vfstab file (the blank areas between the keywords are spaces):
swap - /tmp tmpfs - yes -Troubleshooting
Viewing Core Files Generated by CEMF and Cisco MGC Node Manager
Use the /opt/cemf/bin/listCores command to view all core files generated by CEMF and Cisco MGC Node Manager.
CEMF Licensing
If you are having problems with CEMF licensing, you might need to stop and restart the license manager daemon. To do so, execute the following commands:
#> /etc/rc2.d/S98alvm stop #> /etc/rc2.d/S98alvm start
Note
Viewing the Most Recently Changed Log Files
Cisco MGC Node Manager log files are stored in <CEMF Directory>/logs. You can view the most recently changed log file with ls -lt command.
Interesting Cisco MGC Node Manager Log Files
Some interesting Cisco MGC Node Manager log files are:
•
•
•
Error Messages That Are Safe to Ignore
Most of the entries in the Cisco MGC Node Manager log files are created by the CEMF platform and are of limited value. The following error messages are safe to ignore:
•
–
–
–
–
•
general : WARN Creating Database /opt/AV3/db/mgcController.db
•
–
–
–
–
–
–
–
–
–
•
–
–
Resetting the User Password
If you forget your password, you can reset the CEMF user IDs and passwords. The following command removes all passwords, and resets the admin user ID's password to admin.
<CEMF Directory>/bin/cemf shell <CEMF Directory>/bin/partitioningTool -rBacking Up and Restoring the CEMF/Cisco MGC Node Manager Databases
The following command backs-up the CEMF/Cisco MGC Node Manager databases. By default the backup files are placed in /opt/AVBackup.
/opt/CSCOcemf/bin/cemf stop /opt/CSCOcemf/bin/cemf backup /opt/CSCOcemf/bin/cemf startThe following command will restore a CEMF/Cisco MGC Node Manager database.
/opt/CSCOcemf/bin/cemf stop /opt/CSCOcemf/bin/cemf restore -t mm-dd-yyyy /opt/CSCOcemf/bin/cemf startFor more information on backing up and restoring CEMF/Cisco MGC Node Manager Databases refer to the "Cisco EMF Database Backup and Restore Procedures" section of the Installing, Licensing, and Configuring Cisco EMF Manual.
Forcing an Uninstall of an Element Manager
The CEMF daemons must be running for the Element Managers (EMs) to uninstall. There are two ways to force an uninstall of an EM; both cause loss of all CEMF/Cisco MGC Node Manager data. Before running these commands, it is recommended that you back up your databases.
The uninstallCSCOcmnm script can be invoked with an undocumented option to force the removal of all or one EM. From a command line, as root, type the command:
/opt/CSCOcemf/uninstall/uninstallCSCOcmnm -force [-em <EM>]
You can specify only one EM to remove or all EMs by omitting that parameter. The list of EMs includes hostEM, mgcEM, andmgxEM.
Example:
/opt/CSCOcemf/uninstall/uninstallCSCOcmnm -force -em mgxEM -em mgcEM
After you run this command, the CEMF databases are corrupted. To correct this problem, reset the CEMF databases by running the following command. You must do this before using CEMF again, even using CEMF to reinstall Cisco MGC Node Manager.
/opt/CSCOcemf/bin/cemf stop /opt/CSCOcemf/bin/cemf reset /opt/CSCOcemf/bin/cemf startAfter you have successfully reset the database and restarted CEMF, you must reinstall Cisco MGC Node Manager. If you want to restore a CEMF/Cisco MGC Node Manager database after you have reinstalled Cisco MGC Node Manager, refer to "Backing up and restoring the CEMF/CMNM Databases" in the preceding section.
If the above method doesn't remove the EMs, then you can try another method. When the EMs are installed, Solaris package information is placed in subdirectories of /var/sadm/pkg. The subdirectory is the name of the package, as specified above (that is, hostEMm, mgcEMm, and so on). As the root user, complete the following steps for each EM that you want to remove.
/opt/CSCOcemf/bin/cemf stop touch /var/sadm/pkg/<EM>/install/.avload pkgrm <EM> /opt/CSCOcemf/bin/cemf reset /opt/CSCOcemf/bin/cemf startExample:
/opt/CSCOcemf/bin/cemf stop touch /var/sadm/pkg/mgcEMm/install/.avload pkgrm mgcEMm /opt/CSCOcemf/bin/cemf reset /opt/CSCOcemf/bin/cemf startTo restore a CEMF/Cisco MGC Node Manager database after you have reinstalled Cisco MGC Node Manager, refer to the preceding "Backing Up and Restoring the CEMF/CMNM Databases".
Managing Network Devices Over a Slow Link
If you are managing network devices over a slow link (T1 or slower), you might need to alter SNMP parameters used by Cisco MGC Node Manager for SNMP Get Requests. You can change these parameters for any existing objects by accessing the States dialog. You can also change these parameters in the Advanced tab of the Seed File Deployment dialog.
The default number of SNMP retries is 2. You might need to increase this value when the Cisco MGC Node Manager workstation is connected to network devices over a slow link.
The default SNMP timeout value is 5000 milliseconds (5 seconds). You may need to increase this value when the Cisco MGC Node Manager workstation is connected to network devices over a slow link.
Maximizing Logfile Output
By default Cisco MGC Node Manager logs only warning and error messages. If you want to turn on debug messages in all log files, complete the following steps, as the root user:
Step 1
Step 2
Step 3
Step 4
loggingLevelMask = 12
Step 5
Step 6
Step 7
loggingLevelMask = 10
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
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:
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.htm
You can order Cisco documentation in these ways:
•
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Documentation Feedback
You can send comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
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. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553 2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
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. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
http://cisco.com/univercd/cc/td/doc/pcat/
•
•
•
http://www.cisco.com/go/iqmagazine
•
•
http://www.cisco.com/en/US/learning/index.html
