Release Notes for the Cisco Media Gateway Controller Node Manager, Release 2.8(1)

Table Of Contents

Release Notes for the Cisco Media Gateway Controller Node Manager, Release 2.8(1)

Contents

Introduction

System Requirements

Software Requirements

Software Changes

Release 2.8(1)

Release 2.8(1) Patch 1

Supported Configurations

Supported Network Elements

Installation Notes

Installation Procedure

Installing the Cisco MNM 2.8(1)

Uninstalling the Cisco MNM 2.8(1)

Upgrade Procedure

Patch Procedure

Known Issues

Cisco MNM Aborts Installation

Cisco MNM Cannot Clear Some Alarms of the Cisco BAMS

Cisco MNM Cannot Discover an Interface or IP Address

Cisco MNM Still Starts Netscape in Some Dialog Boxes

Cisco MNM Shows the Incorrect Time Information in Object Properties

Resolved Problems

Release 2.8(1)

Release 2.8(1) Patch 1

Tips

Initial Cisco MNM Configuration

Installing Cisco EMF/MNM on a Server

Configuring the Cisco EMF Software for Maximum Performance

Troubleshooting

Viewing Core Files Generated by Cisco EMF and Cisco MNM

Cisco EMF Licensing

Viewing the Most Recently Changed Log File

Cisco MNM Log Files

Error Messages You Can Ignore

Resetting the User Password

Backing Up and Restoring the Cisco EMF/MNM Databases

Forcing an Uninstallation of an Element Manager

Managing Network Devices Over a Slow Link

Maximizing the Output of Log Files

Setting VNC Parameters

Product Documentation

Related Documentation

Obtaining Documentation and Submitting a Service Request

Release Notes for the Cisco Media Gateway Controller Node Manager, Release 2.8(1)

---

Revised: December 8, 2011, OL-18338-07

The Cisco Media Gateway Controller Node Manager (MNM) Release 2.8(1) provides support on new features introduced on Cisco PGW 2200 Softswitch Release 9.8(1).

This document contains release information for the Cisco MNM Release 2.8(1) software. For more information on the Cisco MNM software, please visit the Cisco website at

http://www.cisco.com/en/US/products/sw/netmgtsw/ps1912/tsd_products_support_series_home.html

Contents

•Introduction

•System Requirements

•Software Requirements

•Software Changes

•Supported Configurations

•Supported Network Elements

•Installation Notes

•Known Issues

•Resolved Problems

•Tips

•Troubleshooting

•Product Documentation

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

Introduction

The Cisco MNM is an element management system (EMS) for the Cisco PGW 2200 Softswitch node, a call control node based on the Cisco PGW 2200 Softswitch. The Cisco MNM provides basic management of the Cisco PGW 2200 Softswitch node devices, including fault, configuration (Cisco VSPT), performance, and user security management.

The Cisco MNM helps you manage the following components:

•Cisco PGW 2200 Softswitch

•Cisco ITP-L

•Cisco Integrated ITP-L

•Cisco LAN Switch (Cisco Catalyst 2900, 5500, and 6509 only)

•Cisco BAMS

•Cisco HSI

System Requirements

At a minimum, you need the following hardware and software to install and run Cisco MNM:

•Sun platforms in the UltraSPARC and T2000/T5220 families

–Sun platforms based on SUN Fire 240 and Sun Netra 240

–Sun Netra T2000 and Sun SPARC Enterprise T2000

–Sun Netra T5220 and Sun SPARC Enterprise T5220

•Minimum 4 GB of RAM

•8 GB (or greater) of swap

•Sun Solaris 10 operating system

–Latest patches recommended

–Open Windows with the Common Desktop Environment (CDE)

•Properly configured drives that are 36 GB or larger. The database drives should be configured with raw partitions for the Sun UltraSPARC platforms, and with RAID0 for the Sun T5220 platforms in order to get the best performance.

•The tmpfs file system must be mounted to /tmp for maximum performance.

The following are additional requirements if Cisco MNM coexists with CiscoView 6.1.8 on the Solaris 10 operating system:

•Version must be the November 2006 release or higher, and the minimum recommended cluster patch levels are those cluster patches released April 17, 2007.

---

Note•Cisco MNM Release 2.8(1) includes CiscoView for Solaris 10 only. CiscoView for Solaris 8 is not provided with the Cisco MNM media kit. However, previous CiscoView versions shipped with previous Cisco MNM media kits can be reused. New Cisco MNM users should be using Solaris 10 for best long-term satisfaction and full CiscoView support. New Cisco MNM users who use only Solaris 8 operating system must obtain CiscoView for Solaris 8 separately, possibly by purchasing the appropriate LMS 2.5.1 package.

•Cisco MNM is available on CD, and LMS 3.1 and CiscoView 6.1.8 are available on DVD.

---

Chapter 1 of the Cisco Media Gateway Controller Node Manager Installation Guide lists detailed system requirements for the Cisco MNM at

http://www.cisco.com/en/US/products/sw/netmgtsw/ps1912/prod_installation_guides_list.html

Review this chapter before installing or configuring the software.

Installing drives greater than 9 GB does not result in performance gains. The main restriction on the Cisco Element Management Framework (EMF) application speed is the hard disk input/output (I/O) capability, not capacity. Maximum performance is achieved using many drives of lower capacity instead of a few, larger capacity drives.

Software Requirements

The following are required for Cisco MNM installation:

•Server/Client: Solaris 10

•CiscoView (from LMS DVD-Solaris 10 only)

•CEMF 3.2, patches 7, 7.1, and 7.2

•CEMF Crypto Add-on Package Software (mandatory if ssh function is needed)

---

Note CEMF patches are required for Solaris 10 operating systems. For more information, see the Cisco Media Gateway Controller Node Manager Installation Guide, Release 2.8(1) at

http://www.cisco.com/en/US/docs/net_mgmt/mnm/2.8.1/install/guide/MNM_Install.html

---

•Cisco VSPT 2.8(1)

•Cisco MNM 2.8(1)

For operating requirements, see the "Supported Configurations" section.

Software Changes

This section describes software changes in the Cisco MNM Release 2.8(1) and Release 2.8(1) Patches.

Release 2.8(1)

Cisco MNM Release 2.8(1) supports Cisco PGW 2200 Softswitch Releases 9.6(1), 9.7(3), and 9.8(1) (up to Release 9.8(1) S1P1).

New MML Components

•outsipheader

•insipheader

•Domainprofile

•SIPIVersion

•gwpool

•ipgw

•profile

New Profile Properties

---

Note Old SIP and EISUP trunk group properties were moved to profile properties and deleted in trunk group properties.

---

•trustLevel

•topologyHidingEnabled

•useDomainProfile

•outboundDomainProfileSource

•commonProfile

•grprofile

•insipheadertable

•outsipheadertable

•LRNDigitCCPrefix

•LRNDigitCCrm

•SipIEgressHandling

•SipIConfusionHandling

•SipIFacilityRejectHandling

•SipICLICOLPreference

•SipICANCELEncapREL

•SipInsertReasonHeader

•SipIIngressVersionMAP

•SipIEgressMDO

•SipIEgressISUPVersion

•SipEgressGN2FromScreenInd

•SipEgressEarlyDialogRelType

•SipIngressLNPHandling

•SipIToiw2

•GatewayToneSupport

•GatewayAnnSupport

•GatewayCodecSupport

•GatewayDTMFSupport

•GatewaySelectionMethod

•GatewayPool

•AnchorMedia

•AnchorPolicy

•AnnouncementOption

•ToneOption

•DummyCodecString

•NATTraversalEnabled

•RestrictPresIfNoPAID

New SIP Properties

•sipTransportMode

•DelayedOfferToEarlyOfferInterworking

Updated SIP Properties

•sipMimeBodySupport

•Support183

New Misc Properties

•PropagateDelayCounter

Updated Analysis Routing Properties

•InhibitSipFromMapping

Updated Number Properties

•BDigitCCPrefix

•BDigitCCrm

•ADigitCCPrefix

•ADigitCCrm

•CCOrigin

Other New Properties

•NATTraversalMethod

•IPTermNumGroups

•IPTermNumInterfaces

•IPTerNumTerms

New Measurements

•For Cisco PGW 2200 Softswitch

–SIPSP: XMIT UDP MSG TOT

–SIPSP: RCV UDP MSG TOT

–SIPSP: XMIT TCP MSG TOT

–SIPSP: RCV TCP MSG TOT

–CALL: TimesTenLicRej TOT

New Alarms

•From Cisco PGW 2200 Softswitch

–MMDB: Database Permanent Memory nearly full

–MMDB: Database Temporary Memory nearly full

–SIP: Unsupported SIP-I call received

–Peer Config Mismatched

–Normal call rejected due to database oversubscription and restricted access to database

–Runtime database oversubscription

–More TimesTen entries configured than entitled

Other

•The button Version was added to display the version and patch level of Cisco MNM and Cisco VSPT.

•The dial plan feature is no longer supported in Cisco MNM Release 2.8(1).

Release 2.8(1) Patch 1

Cisco MNM Release 2.8(1) Patch 1 supports Cisco PGW 2200 Softswitch Releases 9.6(1), 9.7(3), and 9.8(1) (up to Release 9.8(1) S2P2).

New Profile Properties

•InsideVrfName

•OutsideVrfName

Removed Profile Properties

•VrfName

Supported Configurations

The following configurations are supported:

•Cisco MNM and Cisco VSPT installed together on a network management server (recommended)

•Cisco MNM installed on a network management server and Cisco VSPT installed on a Cisco PGW 2200 Softswitch host machine

•Cisco MNM installed on a network management server and Cisco VSPT installed on a separate server

---

Note Other element managers can be installed on the network management server.

---

---

Caution Cisco MNM is not supported on a Cisco PGW 2200 Softswitch host machine.

---

Supported Network Elements

Cisco MNM Release 2.8(1) supports the following network elements:

•Cisco PGW 2200 Softswitch:

–9.6(1)

–9.7(3)

–9.8(1)

•Cisco Billing and Measurements Server (BAMS):

–3.20

–3.30

•Cisco Catalyst 5500 (latest)

•Cisco Catalyst 2900XL (latest)

•Cisco ITP-L

–2611 (12.4(21))

–2651 (12.4(21))

–2811 (12.4(21))

•Cisco Catalyst 6509

•Cisco HSI adjunct

–4.2

–4.3(2)

•Cisco Integrated ITP-L (5400 & 5350) 12.4(19)a

Installation Notes

This section contains information and procedures you can use to remove, upgrade, or install the Cisco MNM software. It also contains information about software patches.

Installation Procedure

Before installing the Cisco MNM Release 2.8(1), make sure you read the Cisco Media Gateway Controller Node Manager Installation Guide, 2.8(1) at

http://www.cisco.com/en/US/docs/net_mgmt/mnm/2.8.1/install/guide/MNM_Install.html

Cisco MNM consists of server and client software. To set up a Client/Server architecture:

•Install the Cisco EMF and Cisco MNM software on both the client and server workstations. The Cisco MNM installation software determines whether the Client or Manger software should be installed.

•Verify that the minimum hardware requirements pertaining to your site have been met.

•Check to see if the computer is in the Domain Name System (DNS). If it is in the DNS, the computer must have a valid entry in the DNS, and if it is not in the DNS, you must disable Name Resolution completely and delete the /etc/resolv.conf file.

•Verify that the Cisco EMF software has been installed and is running.

---

Note The Cisco EMF software must be running before the Cisco MNM software can be installed.

---

Installing the Cisco MNM 2.8(1)

To install Cisco MNM Release 2.8(1), perform the following steps:

---

Step 1 Log in as the root user.

Step 2 Insert the Cisco MNM Release 2.8(1) product CD in the CD-ROM drive.

Step 3 Change to the /cdrom/cdrom0 directory.

Step 4 Run the command ./cmnminstall.

Step 5 Follow the on-screen prompts.

Step 6 Eject the Cisco MNM Release 2.8(1) product CD after the installation is complete.

---

Uninstalling the Cisco MNM 2.8(1)

To uninstall Cisco MNM Release 2.8(1), perform the following steps:

---

Step 1 Log in as the root user.

Step 2 Insert the Cisco MNM Release 2.8(1) product CD in the CD-ROM drive.

Step 3 Change to the /cdrom/cdrom0 directory.

Step 4 Run the command ./cmnminstall -r.

Step 5 Follow the on-screen prompts.

Step 6 Eject the Cisco MNM Release 2.8(1) product CD after the uninstall procedure is complete.

---

Upgrade Procedure

The Cisco MNM upgrade process enables you to upgrade the software from earlier releases easily.

To upgrade the Cisco MNM, perform the following steps:

---

Step 1 Log in as the root user.

Step 2 Insert the Cisco MNM Release 2.8(1) product CD in the CD-ROM drive.

Step 3 Change to the /cdrom/cdrom0 directory.

Step 4 Run the command ./cmnminstall -upgrade.

Step 5 Follow the on-screen prompts.

Step 6 Eject the Cisco MNM Release 2.8(1) product CD after the upgrade is complete.

---

Patch Procedure

The Cisco MNM patch process is cumulative. Downloading and installing the latest patch installs all previous patches. The software automatically determines which portions of the Cisco MNM need to be patched.

Before you install a patch on Cisco MNM Release 2.8(1), the initial release of Cisco MNM Release 2.8(1) must be installed.

To install the patch, use these steps:

---

Step 1 Verify that the initial release of Cisco MNM Release 2.8(1) is installed.

Step 2 Log in as the root user.

Step 3 Create a temporary installation directory /opt/cmnm_tmp_install.

Step 4 Download the patches:

a. Go to www.cisco.com.

b. Log in.

c. Navigate to Support > Download Software > Network Management Software.

d. Click Cisco Media Gateway Controller Node Manager.

The patch download page appears.

e. Download the patch to the temporary installation directory.

Step 5 Extract the patched software. For example, you can use

zcat CSCOmnm-2.8.1-Patch0x.tar.Z | tar xvf -

Step 6 Run the command ./cmnminstall

Step 7 Follow the on-screen prompts.

---

Known Issues

This section contains information on known issues and the corresponding workarounds.

Cisco MNM Aborts Installation

During installation, Cisco MNM detects how much disk space is available for installation. If the system does not have enough available space, you are asked whether you want to continue the installation.

Even if you enter Y to continue the Cisco MNM installation, the installation aborts. To avoid this problem, ensure that enough free disk space is available before Cisco MNM is installed.

For the amount of disk space required, see the "System Requirements" section. For more information, see the Cisco Media Gateway Controller Node Manager Installation Guide, Release 2.8(1) at

http://www.cisco.com/en/US/docs/net_mgmt/mnm/2.8.1/install/guide/MNM_Install.html

Cisco MNM Cannot Clear Some Alarms of the Cisco BAMS

Sometimes Cisco MNM cannot automatically clear some alarms of the Cisco BAMS. The workaround for this issue is to manually clear these alarms. For the procedure of manual alarms clearing, see the section "Using the Event Browser to Manager Events" in Chapter 6, "Manageing Faults with Cisco MNM", in the Cisco Media Gateway Controller Node Manager User Guide, Release 2.8(1) at

http://www.cisco.com/en/US/docs/net_mgmt/mnm/2.8.1/user/guide/MNM_UG.html

Cisco MNM Cannot Discover an Interface or IP Address

Sometimes Cisco MNM reports that it cannot discover an interface or IP address. This might be caused by the mib2agt state. You can restart mib2agt by stopping the current process. The new process mib2agt is restarted automatically.

To stop the current process, use the following commands:

ps -ef | grep mib2agt 

kill -9 <PID>

If the restart of mib2agt does not solve the problem, check if the type of the interface is one of the Ethernet, Serial, SCO/SLO, and Loopback.

Cisco MNM Still Starts Netscape in Some Dialog Boxes

Cisco MNM starts Mozilla in some dialog boxes. But there are still some functions that use Netscape as the web browser. If you take an action other than that one of those listed in Table 1, your system starts Netscape, rather than Mozilla.

Table 1 Cisco MNM Functions Starting Mozilla

Function	Select This View or Object	Command	Description
CiscoView	LAN Switch, ITP-L	Right-click and choose Tools > CiscoView	Opens CiscoView application
Web Browser	ITP-L	Right-click and choose Tools > Web Browser	Opens a Mozilla web browser, pointing to the internal web server on Cisco ITP-Ls
Cisco MNM User Manual	—	Click CMNM Manuals button on the CEMF launch pad	Opens a Mozilla web browser, pointing to the Cisco MNM user manual at Cisco website.

If you want to use Mozilla instead of Netscape, open Mozilla manually first. Then you can copy the web page address in the opened Netscape to the Mozilla address bar and press Enter.

Cisco MNM Shows the Incorrect Time Information in Object Properties

Sometimes the time information in object properties is incorrect. This issue occurs when the time measurement of that device exceeds 248 days. Table 2 describes the time information that might be wrong on Cisco MNM. The workaround for this issue is to restart the device which has the incorrect time information shown in the Cisco MNM.

Table 2 Time Information Improperly Displayed in Object Properties 

Incorrect Time Information	Objects Affected	Location of the Incorrect Time Information
Up-time	•Cisco PGW 2200 Softswitch •Cisco BAMS •Cisco HSI •LAN switches •Cisco ITP-L	Right-click the object and choose Tools > Properties (leads you to the General Tab)
Event Time	•Cisco ITP-L •Cisco Catalyst 2900XL LAN Switch	Right-click the object and choose Tools > Properties (leads you to the Configuration Tab)
Running Last Changed	•Cisco ITP-L •Cisco Catalyst 2900XL LAN Switch	Right-click the object and choose Tools > Properties (leads you to the Configuration Tab)
Running Last Saved	•Cisco ITP-L •Cisco Catalyst 2900XL LAN Switch	Right-click the object and choose Tools > Properties (leads you to the Configuration Tab)
Startup Last Changed	•Cisco ITP-L Cisco Catalyst 2900XLLAN Switch	Right-click the object and choose Tools > Properties (leads you to the Configuration Tab)
Last Config Change	•Cisco Catalyst 5500 LAN Switch •Cisco Catalyst 6509 LAN Switch	Right-click the object and choose Tools > Properties (leads you to the Network Tab)
Last Change	•Ethernet, serial, and generic interfaces on the Cisco PGW 2200 Softswitch, Cisco ITP-L, Cisco BAMS, Cisco Catalyst 5500 or 6509 LAN Switch and HSI •Ports on Cisco Catalyst 2900XL and Catalyst 5500 LAN Switch •TDM interfaces on Cisco ITP-L	Right-click the object and choose Tools > Properties (leads you to the Details Tab)

Resolved Problems

Release 2.8(1)

Table 3 describes resolved problems in Cisco MNM Release 2.8(1).

Table 3 Resolved Problems in Cisco MNM Release 2.8(1) 

Identifier	Severity	Summary
CSCso62029	3	EISUP path measurement is not right.
CSCso70859	3	The event on Host-View is not propagated.
CSCsu22866	3	The command cmnmstatus reports all CEMF processes as down.
CSCsm66942	6	The Launch VSPT option is missing when right-click the BAMS object.
CSCsm87286	6	SIP over TCP Phase 2.
CSCsm87290	6	PGW SIP-I.
CSCsm87292	6	PGW IP to IP gateway.
CSCsm87297	6	PGW SIP Profile.
CSCsq22988	6	Error returned for unsupported properties in non-TDM trunk group status.
CSCsq35870	6	Remove DialPlan from CMNM.
CSCsq64341	6	Need a button on the CMNM launch pad to show the version and patch information for Cisco VSPT and Cisco CMNM.
CSCsr42667	6	CMNM support Licensing for Database and SBE.
CSCsr42676	6	CMNM support Finnish SIP-I support on PGW.
CSCsr62113	6	Add support on PGW features introduced from Release 9.7(3) S14P14 to S17P17.

Release 2.8(1) Patch 1

Table 4 describes resolved problems in Cisco MNM Release 2.8(1) Patch 1.

Table 4 Resolved Problems in Cisco MNM Release 2.8(1) Patch 1 

Identifier	Severity	Summary
CSCsw44663	3	The version information of CMNM should be formatted.
CSCsv57579	6	CMNM supports to include egress TG vrf information in the originating side.

Tips

This section gives you the tips for configuring and installing Cisco MNM.

Initial Cisco MNM Configuration

Cisco MNM is initially configured with one user.

To configure the id and password for one user, enter the following:

id: admin

password: admin

Installing Cisco EMF/MNM on a Server

If you have installed Cisco EMF/MNM on a server and need to change the IP address/hostname, you must make the changes shown in the following procedure.

---

Note Set the environment variable CEMF_ROOT to the value of the directory that the CEMF installed, and then change the CEMF directory to $CEMF_ROOT.

---

The following example uses the hostname Cisco MNM and the IP address 10.1.1.1:

---

Step 1 Use the following commands to stop the CEMF.

# cd $CEMF_ROOT/bin

# ./cemf stop

Step 2 Edit /var/adm/Atlantech/system/info to reflect the following hostname and ip address:

MGRHOSTNAME=rambler

MGRIPADDRESS=10.1.1.1

COREHOSTNAME=rambler

Step 3 Edit $CEMF_ROOT/config/env/avCore.sh to reflect the hostname in the lines below and save the file.

MgrSystemManager=rambler1270; export MgrSystemManager

PortAllocator=rambler1270; export PortAllocator

transRouter=rambler1271; export transRouter;

Step 4 Edit /var/sadm/pkg/CSCOcemfm/pkginfo to reflect the following values:

MGRIPADDRESS=10.1.1.1

MGRHOSTNAME=10.1.1.1

COREHOSTNAME=10.1.1.1

LOCALHOSTNAME=10.1.1.1

Step 5 Make the same changes for each Element Manager by editing the following files:

/var/sadm/pkg/hostEM/pkginfo

/var/sadm/pkg/mgcEM/pkginfo

Step 6 Rename CEMFDirectory/ODI/OS5.1/ostore/hostname_server_parameter to reflect the new hostname.

You must obtain a new CEMF license. Refer to the "Cisco EMF Licensing" section.

Step 7 Use the following command to start the CEMF.

# <CEMF_ROOT>/bin/cemf start

---

Configuring the Cisco EMF Software for Maximum Performance

The following are tips for configuring Cisco EMF:

•Use the primary drive for the Solaris operating system and the ObjectStore transaction log.

•The second drive must contain the Cisco EMF software (/opt/cemf).

•Configure the ObjectStore database for Raw File Systems. The remaining hard drives must contain the RAW File System partitions for the Cisco EMF database (preferably on a separate SCSI controller).

Mount the tmpfs file system to /tmp so that the ObjectStore cache files can be kept in memory. ObjectStore is the database program included with Cisco EMF. Keeping the cache files in memory increases the performance.

This is how the tmpfs line should read in the /etc/vfstab file. (The blanks between the keywords are spaces):

swap - /tmp tmpfs - yes -

Troubleshooting

This section describes troubleshooting procedures for Cisco MNM.

Viewing Core Files Generated by Cisco EMF and Cisco MNM

Use the /opt/cemf/bin/listCores command to view all core files generated by Cisco EMF and Cisco MNM.

Cisco EMF Licensing

If you come with an error with Cisco EMF licensing when starting the Cisco EMF, stop and restart the license manager daemon by running the following commands:

/etc/rc2.d/S98avlm stop 

/etc/rc2.d/S98avlm start

If the problem is not resolved, please check that a valid license has already been uploaded into /opt/cemf/config/licenses, and use the following procedure:

---

Step 1 Add the following two lines in /opt/cemf/flexlm/avlm:

ulimit -n 1024

ulimit -H -n 1024

Step 2 Enter the following command to stop the lmgrd:

/opt/cemf/flexlm/lmdown

Step 3 Enter the following command to start the Cisco EMF again:

/opt/cemf/bin/cemf start

---

The Cisco EMF licenses are fixed for a particular machine. You cannot copy the license file from one machine to another. If you want to install the Cisco EMF software on another machine, you must contact Cisco TAC and ask for a new license. You are required to provide Cisco TAC with the hostname and hostid of the new machine.

Viewing the Most Recently Changed Log File

Cisco MNM log files are stored in $CEMF_ROOT/logs. You can view the most recently changed log file with the ls -lt command.

Cisco MNM Log Files

If Cisco MNM is not working well or you have some problems with Cisco MNM, you can check the log files for detail information or send the log files to customer support engineers. The following are examples of Cisco MNM log files:

•hostController.log (Cisco PGW 2200 Softswitch Host)

•mgcController.log (Cisco PGW 2200 Softswitch Node)

•trapLog.log (Incoming traps are logged here to separate them from Cisco EMF log messages that are collected in mgcTrapProcessor.log.)

Error Messages You Can Ignore

Most of the entries in the Cisco MNM log files are created by the Cisco EMF platform and are of limited value.

You can ignore the following error messages:

•SNMP and MIB parsing errors that appear when an EM controller starts:

–SNMP: ERROR mib.cc:1283 Mib Object is already on the tree for.

–SNMP: ERROR mibDependencyMgr.cc:191 mibDependencyMgr.cc:196 Mib . not defined.

–SNMP: ERROR mibParser.y:359 EXPORTS are currently ignored (;, line 8).

–SNMP: WARN mibParser.y:1154 Name and number form OIDs are not properly implemented.

•Database warning that appears when an EM controller is first installed:

–general: WARN Creating Database /opt/AV3/db/mgcController.db.

•General error messages that appear when the EM controller starts:

–General: ERROR Unable to get event channel ID for channel.

–General: ERROR EventChannelManager: Failed to find location for event channel.

–General: WARN OGManager::OGManager—Unable to get deleteEventChannel from .ini file.

–General: ERROR OGManager::processGroupClass—invalid class id.

–General: ERROR EventChannelManager: Failed to find location for event channel ERROR OGManager::processGroupClass—invalid class id.

–General: ERROR OGChangeEventHandler::process—could not find drep!

–General: ERROR IdAllocatorOS: Deprecated constructor called.

–Task: WARN PerfPollTask::createGroupsResult: group already exists.

–mgcController: WARN Controller::initialiseController Controller is configured NOT to auto populate tech tree on autodiscover.

•Other miscellaneous errors:

–General: WARN CommsBuffer::serialize - resizing buffer size.

–General: ERROR PersistentAttributeStore::PersistentAttributeStore() nameInit = xxx. is longer than 16 characters. All Objectstore segment comments will be truncated to use the first 16 characters.

Resetting the User Password

If you forget your password you can reset it. The following command removes all the passwords and resets the password for the administrator user ID:

<CEMF_ROOT>/bin/cemf shell 

<CEMF_ROOT>/bin/partitioningTool -r

Backing Up and Restoring the Cisco EMF/MNM Databases

To back up the Cisco EMF/MNM databases, you can use the following commands. By default the backup files are placed in /opt/AVBackup:

<CEMF_ROOT>/bin/cemf stop 

<CEMF_ROOT>/bin/cemf backup 

<CEMF_ROOT>/bin/cemf start

To restore a Cisco EMF/MNM database, you can use the following commands:

<CEMF_ROOT>/bin/cemf stop 

<CEMF_ROOT>/bin/cemf restore -t mm-dd-yyyy 

<CEMF_ROOT>/bin/cemf start

For more information on backing up and restoring Cisco EMF/MNM databases, refer to the "Cisco EMF Database Backup and Restore" section of the Cisco Element Management System Installation and Configuration Guide, 3.2 Service Pack 7 at

http://www.cisco.com/en/US/docs/net_mgmt/element_manager_system/3.2_service_pack_7/installation/guide/backup.html

Forcing an Uninstallation of an Element Manager

The Cisco EMF daemons must be running for the Element Managers (EMs) to uninstall. If you have trouble uninstalling an Element Manager, there are two ways to force an uninstallation of an EM (each causes a loss of all Cisco EMF/MNM data). Before running either of these commands, you should back up your databases.

1. The first method invokes the uninstallCSCOcmnm script with an undocumented option to force the removal of all or one EM. From a command line, as root, enter the command:

<CEMF_ROOT>/uninstall/uninstallCSCOcmnm -force [-em <EM>] 

To specify the removal of one EM or all EMs, omit the parameter. The list of EMs includes hostEM, mgcEM, and mgxEM.

Example:

<CEMF_ROOT>/uninstall/uninstallCSCOcmnm -force -em mgxEM -em mgcEM 

After you run this command, the Cisco EMF databases are corrupted. To correct this problem, reset the Cisco EMF databases by running the following commands. You must do this before using Cisco EMF again, even using Cisco EMF to reinstall Cisco MNM:

<CEMF_ROOT>/bin/cemf stop 

<CEMF_ROOT>/bin/cemf reset 

<CEMF_ROOT>/bin/cemf start

After you have successfully reset the database and restarted Cisco EMF, you must reinstall Cisco MNM. If you want to restore a Cisco EMF/MNM database after you have reinstalled Cisco MNM, see the "Backing Up and Restoring the Cisco EMF/MNM Databases" section.

2. If you receive a failure message that the first method does not remove the EMs, use this 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 (hostEMm, mgcEMm, and so forth). As the root user, enter the following for each EM that you want to remove:

<CEMF_ROOT>/bin/cemf stop 

touch /var/sadm/pkg/<EM>/install/.avload 

pkgrm <EM> 

<CEMF_ROOT>/bin/cemf reset 

<CEMF_ROOT>/bin/cemf start

In the following example, mgcEMm is uninstalled:

<CEMF_ROOT>/bin/cemf stop 

touch /var/sadm/pkg/mgcEMm/install/.avload 

pkgrm mgcEMm 

<CEMF_ROOT>/bin/cemf reset 

<CEMF_ROOT>/bin/cemf start

To restore a Cisco EMF/MNM database after you have reinstalled Cisco MNM, see the "Backing Up and Restoring the Cisco EMF/MNM Databases" section.

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 the values of SNMP parameters used by Cisco MNM for SNMP Get requests.

You can change the values of these parameters for any existing object by accessing the States dialog. You can also change the values of 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 MNM workstation is connected to network devices over a slow link.

•The default SNMP timeout value is 5000 milliseconds (5 seconds). You might need to increase this value when the Cisco MNM workstation is connected to network devices over a slow link.

Maximizing the Output of Log Files

By default, Cisco MNM 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.

---

Note Set the environment variable CEMF_ROOT to the value of the directory that the CEMF installed, and then change the CEMF directory to $CEMF_ROOT.

---

---

Step 1 Use the following commands to stop CEMF.

# cd $CEMF_ROOT/bin

# ./cemf stop 

Step 2 Change the directory using the following command:

# cd <CEMF_ROOT>/config/init 

Step 3 Edit loggercommon.include and add or change the following line:

loggingLevelMask = 12

Step 4 Change the directory and start the CEMF using the following command:

# cd <CEMF_ROOT>/bin

# ./cemf start 

Step 5 Add or change the following line to set the logging level back to warning:

loggingLevelMask = 10 

---

Setting VNC Parameters

If you are using VNC on Solaris 10 to access Cisco MNM, see the following URL for instructions on installing and configuring the VNC on the Solaris 10 platform from the Sun Microsystems website:

http://www.sun.com/bigadmin/jsp/descFile.jsp?url=descAll/install_and_configu

Set the parameter "depth" to 24 and the parameter "geometry" to 1024x768. The following example shows parameter settings. You can use this line to replace the corresponding line when you are editing /etc/dt/config/Xservers in the configuration procedure described in the above URL.

:1 Local local_uid@console root /opt/sfw/bin/Xvnc :1 -httpd /opt/sfw/vnc/classes -depth 24 
-geometry 1024x768 -r fbwait 120000 -rfbauth /opt/sfw/vnc/.vnc/passwd -rfbport 5901

-httpport 5801 -fp tcp/localhost:7100 -alwaysshared -co /usr/openwin/lib/X11/rgb

-fp /usr/openwin/lib/X11/fonts/misc/, /usr/openwin/lib/X11/fonts/75dpi/

Product Documentation

The documents that contain information related to the Cisco MNM Release 2.8(1) are at the following URL.

http://www.cisco.com/en/US/products/sw/netmgtsw/ps1912/tsd_products_support_series_home.html

Related Documentation

The documents that contain information related to the Cisco PGW 2200 Softswitch are at the following URL.

http://www.cisco.com/en/US/products/hw/vcallcon/ps2027/tsd_products_support_series_home.html

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation at

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)