|
|
The CMNM installation program and installation software are found on a CMNM product CD. Cisco Media Gateway Controller Manager (CMM) or Voice Services Provisioning Tool (VSPT) are required for voice provisioning, depending on the network configuration. Both must be installed before CMNM. CMM is found on the CMNM CD and Voice Services Provisioning Tool is downloaded from the Web.
Before you install CMNM you must have the required hardware and software and access to the CMNM Installation site on the Web.
Perform the following steps before beginning installation of the CMNM:
Step 2 Check the minimum hardware requirements.
Step 3 Check the software requirement list to be sure that you have all the necessary software.
Step 4 Partition hard drives on the workstation.
Step 5 Install CEMF 3.0.4 and latest patches (minimum Patch 7 is required).
Step 6 Make CEMF performance modifications.
Step 7 Install CMNM on client and manager workstations as appropriate.
Step 8 Install the relevant Cisco MGC host provisioning tool.
Both client and server minimum hardware requirements must be met.
 |
Note CMNM supports a maximum of six users at a time. |
The CMNM application runs on a separate machine than the Cisco MGC host. The requirements of this machine are described in Table 2-1.
|
Note Disk drive requirements are based on the number of drives. The CEMF host machine requires at least the number of drives indicated inTable 2-1. |
|
Note These are recommendations. The total amount of disk space required depends on the amount of alarm and performance data saved. |
By default, the CEMF software is installed with standard UNIX cooked partitions (partitions with readable directory structures.) However, raw partitions (partitions without a readable directory structure) offer the following advantages over cooked partitions:
Listed below are the suggested partitioning layouts for both cooked and raw partitions. For detailed information on configuring CEMF with raw files systems, refer to the "ObjectStore Installation Options" section in the Installing, Licensing, and Configuring Cisco EMF manual. CEMF uses ObjectStore for its database. ObjectStore is installed with CEMF.
|
Note ObjectStore requires all raw partitions to be identical in size. |
|
Note For information about suggested performance enhancements for cooked partitions, see the "Performance Enhancements for Cooked Partitions" section. |
The following tables give the mount point and size for creating cooked partitions.
The following tables give the mount point and size for creating raw partitions.
|
Note ObjectStore requires all raw partitions to be identical in size. |
|
Note For information about suggested performance enhancements for raw partitions, see the "Performance Enhancements for Raw Partitions" section. |
 |
Caution Adding, modifying, or deleting raw file systems resets the ObjectStore database and destroys any existing data. |
To configure raw file systems in ObjectStore:
Step 2 Stop the current CEMF processes (/etc/init.d/cemf stop).
Step 3 Shut down ObjectStore (for example, /etc/rc2.d/S80ostore4 stop).
Step 4 Shut down the AV License Manager (for example, /etc/rc2.d/S98avlm stop).
Step 5 Start a CEMF shell (for example, /etc/rc2.d/S99cemf shell).
Step 6 Change to the CEMF installation directory (for example, /opt/CSCOcemf).
Step 7 Change to the ./ODI/OS5.1/ostore/etc directory (under /opt/$INSTALL_DIR).
Step 8 Edit the host name server parameter file (for example, cemfserver_server_parameters) and make the following modifications:
For example (a cemfserver_server_parameters file):
unix-shell#> cd /opt/CSCOcemf/ODI/OS5.1/ostore/etc
unix-shell#> cat cemfserver_server_parameters
Partition0: PARTITION /dev/rdsk/c2t9d0s0
Partition1: PARTITION /dev/rdsk/c2t10d0s0
Partition2: PARTITION /dev/rdsk/c2t12d0s0
Partition3: PARTITION /dev/rdsk/c2t13d0s0
Step 9 Change to the CEMF_INSTALL/ODI/OS5.1/ostore/lib directory (for example, opt/CSCOcemf/ODI/OS5.1/ostore/lib).
Step 10 Run the command ./osserver -i to reinitialize ObjectStore. Answer yes when prompted to reinitialize the database.
Step 11 Run the command /etc/init.d/cemf reset to reset the CEMF database. Answer yes when prompted.
Step 12 Run the command /etc/init.d/cemf start to start the ObjectStore and CEMF processes.
Both client and server minimum software requirements must be met.
|
Caution Check the web site for the latest bulletins and upgrades for software before proceeding. |
CMNM interacts with other software running on the various components of the Cisco MGC node. The software requirements for these components are described in Table 2-10.
The following enhancements are designed to get the maximum performance from a CEMF installation. For cooked and raw partitions, select Option 1 or Option 2 based on the system's physical memory size.
|
Note Databases should be not be installed on the same drive as the CEMF software. |
|
Note For more information about cooked partitions, see the "Hard Drive Partitioning" section. |
If physical memory is less than 1 gigabyte, then the cache files should reside on a separate physical drive.
Step 2 Create the file localhost.sh in the CEMF Directory/config/env directory and add the lines:
OS-CACHE_DIR=/ostore_cache ; export OS_CACHE_DIR
OS_COMMSEG_DIR=/ostore_cache ; export OS_COMMSEG_DIR
Step 3 For the changes to take effect, you must restart the CEMF processes using the following commands.
If physical memory is greater than 1 gigabyte, then the cache files should reside in a memory file system (for example, tmpfs).
a. Type su - root to become the root user.
b. Change to the /etc directory.
c. Copy the vfstab file to a backup file.
d. Edit the vfstab file and add the following line:
e. Reboot for changes to take effect.
Step 2 Create the file localhost.sh in the CEMF Directory/config/env directory and add these lines:
Step 3 Verify that the entry for the database transaction log is correctly identified in the file hostname_server_parameter, where hostname is the host name of the workstation. Enter the command:
cat CEMF Directory/ODI/OS5.1/ostore/etc/hostname_server_parameter
Log File: /var/opt/cemf/logs/transact.log
Step 4 If the transact.log file is not correctly identified, edit the hostname_server_parameter file.
Step 5 For the changes to take effect, you must restart the CEMF processes using the following commands.
|
Note Raw partitions should be not be installed on the same drive as the CEMF software. |
|
Note For more information about raw partitions, see the "Hard Drive Partitioning" section. |
If physical memory is less than 1 gigabyte, then the cache files should reside on a separate physical drive and the database transaction log should be in the raw partition.
Step 2 Create the file localhost.sh in the CEMF Directory/config/env directory and add the lines:
OS-CACHE_DIR=/ostore_cache ; export OS_CACHE_DIR
OS_COMMSEG_DIR=/ostore_cache ; export OS_COMMSEG_DIR
Step 3 The transaction log should be in the raw partition. The file hostname_server_parameter, where hostname is the host name of the workstation, should not have an entry for the transaction log. If the hostname_server_parameter file has an entry for the transaction log, edit the file and remove the line (the file is located in CEMF Directory/ODI/OS5.1/ostore/etc/.
Step 4 For the changes to take effect, you must restart the CEMF processes using the following commands.
If physical memory is greater than 1 gigabyte, then the cache files should reside in a memory file system (for example, tmpfs) and the database transaction log should be in the raw partition.
a. Type su - root to become the root user.
b. Change to the /etc directory.
c. Copy the vfstab file to a backup file.
d. Edit the vfstab file and add the following line:
e. Reboot for changes to take effect.
Step 2 Create the file localhost.sh in the CEMF Directory/config/env directory and add these lines:
Step 3 The transaction log should be in the raw partition. The file hostname_server_parameter, where hostname is the host name of the workstation, should not have an entry for the transaction log. If the hostname_server_parameter file has an entry for the transaction log, edit the file and remove the line (the file is located in CEMF Directory/ODI/OS5.1/ostore/etc/.
Step 4 For the changes to take effect, you must restart the CEMF processes using the following commands.
The following sections list requirements for configuring domain name system (DNS).
If the workstation uses DNS, you must configure DNS on the workstation before installing CEMF.
|
Note If you change how DNS is configured after CEMF is installed, you must uninstall and reinstall CEMF. |
If the CEMF workstation is set up to use DNS, then the host name of the workstation must also be configured on the DNS server. Just having the local hostname in the /etc/hosts file is not sufficient—regardless of how /etc/nsswitch.conf is configured.
To verify that DNS is configured and that the CEMF workstation is in DNS, perform the following steps:
Step 2 Verify that the workstation is configured in DNS using the following command:
|
Note If the nslookup command fails, then CEMF cannot be installed until the CEMF workstation's host name is added to the DNS server. |
CEMF installs properly if a workstation does not use DNS. To verify this:
Step 2 Verify that the hosts entry in the file /etc/nsswitch.conf looks exactly like the following line:
|
Note If /etc/resolv.conf exists, or the hosts: line in /etc/nsswitch.conf has anything else configured, then CEMF does not install properly. |
If CEMF is not already installed, refer to the Cisco Element Manager Framework Installation and Licensing Guide.
|
Note You must install the CMNM software as root. |
The CEMF, and therefore CMNM software, has both a manager (server) and client portion. The client can be installed on the same workstation as the manager or a separate workstation. CMNM must be installed on the manager and all client workstations on which CEMF is installed.
The CMNM installation process automatically detects if the CEMF manager or CEMF client is installed and then installs the correct CMNM component.
|
Note The CMNM software is shipped with the Element Managers in Table 2-11. CMNM has not been tested with any other Element Managers. If you install additional Element Managers, they are not suppported by CMNM. |
Step 2 Type su - root to become the root user.
Step 3 Verify that the Volume Management daemon is running:
a. Type the command ps -ef | grep vold.
· If it is running, you see the following output:
root 363 1 0 May 23 ? 0:01 /usr/sbin/vold
· If the Volume Management daemon is not running, start the daemon using the following command:
b. Verify that the Volume Management daemon is running with the command provided above. If it is still not running, contact your system administrator.
Step 4 Place the CMNM installation media into the CD-ROM drive.
Step 5 Type cd /cdrom/cdrom0.
Step 6 Type ./installCSCOcmnm.
Verify that CMNM software is installed properly before starting CMNM.
The following message should appear:
application CSCOcmnm Cisco MGC-Node Manager
Step 2 Verify that the CMNM Element Managers have been installed. The CMNM software is shipped with the Element Managers in Table 2-11.
Step 3 Run the following script to display the installed CMNM Element Managers and compare this with the list in the table above.
CEMF Basedir/bin/cmnmversion -verbose
CSCOcmnm Element Manager Versions
------------------------------
------------------------------
To verify the installation of CiscoView 5.1:
application CSCOcmcv CiscoView 5.1 for Cisco MGC-Node Manager
ERROR: information for "CSCOcmcv" was not found
Step 2 Verify that the CiscoView Packages have been installed. CiscoView is shipped with the packages in Table 2-12.
Step 3 Run either of the following commands to determine if the CiscoView packages listed in Table 2-12 are installed.
CEMF Directory/ciscoview5.1/bin/dsu -query -all
The dsu application displays to STDOUT the installed CiscoView packages.
CEMF Directory/ciscoview5.1/bin/xdsu
The xdsu application displays a GUI that lists the installed CiscoView packages.
For information about CMNM patches and upgrades, check the web site.
Step 2 Download the latest CiscoView packages and place in a temporary directory; for example, /scratch/cvUpgrade.
Step 3 Make sure that the package files are readable by the root user. If not, the packages do not appear in the CiscoView upgrade tool.
Step 4 Type su - root to become the root user.
Step 5 Change the directory to /scratch/cvUpgrade.
Step 6 To run the CiscoView upgrade tool, type:
CEMF Directory/ciscoview5.1/bin/xdsu
Step 7 Click Install. Ignore the following exception:
ERROR: exception occurred while examining Integration Utility configuration: com.cisco.nm.nmim.nmic.IntgUtilCheckConfig
Step 8 Type in the exact location of the CiscoView packages in the Directory box and press Enter. Or click Browse, navigate to your CiscoView packages' temporary directory, and click Select.
Step 9 Select the CiscoView packages that you want to upgrade, click Install, and click the appropriate confirmation button.
Before uninstalling the CMNM software, be sure to back up your CEMF databases. See "Backing Up Your Databases" below.
See the "Cisco EMF Database Backup and Restore Procedures" section in the Installing, Licensing, and Configuring Cisco EMF manual.
To uninstall the CMNM software, type the following command:
CEMF Directory/uninstall/uninstallCSCOcmnm
The following message should appear:
ERROR: information for "CSCOcmnm" was not found
Step 2 Type pkginfo | grep EM to verify that no CMNM Element Managers are installed.
Step 3 Type pkginfo CSCOcmcv to verify that CiscoView is not installed.
The following message should appear:
ERROR: information for "CSCOcmcv" was not found
There are two different Cisco VSC3000 and Cisco SC2200 provisioning tools depending on what network architecture you are running. If you are running the Cisco SS7 PRI Gateway Solution or the Cisco Tandem Offload Solution, install the Voice Services Provisioning Tool (VSPT). For all other architectures, install CMM.
CMNM has been tested with the following Xserver software package:
For Reflection to display CMNM correctly, Reflection must be run in XDMCP mode.
Step 2 From the Connection menu, select New XDMCP Connection.
Step 3 From the Method pull-down menu, select Broadcast or Direct, then continue with one of the following set of steps:
b. Select the appropriate XDMCP computer. If you do not know which computer to select, contact your system administrator.
a. In the Host Name field, enter the host name of an XDMCP computer.
To fix the " insufficient colors available for CEMF Manager" problem, obtain a copy of the Sun Solaris file rgb.txt, download it your Winxx workstation, and configure Reflection to use the UNIX rgb.txt file as opposed to the Reflection default rgb.txt file.
Step 2 Back up your original rgb.txt file using the following command:
Step 3 Copy the UNIX file, /usr/openwin/lib/X11/rgb.txt, from your Sun Solaris workstation to your Winxx Reflection directory. You can use either FTP or RCP. If you are unable to use FTP or RCP to copy the rgb.txt file, contact your system administrator.
To use FTP, type the following commands:
Step 4 Configure Reflection:
Step 5 Stop Reflection and restart Reflection.
Posted: Thu Feb 13 11:53:01 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.