Installation Notes for the Cisco DSL Manager NI-2, Release 3.4.2
November , 2002
This document explains how to install and uninstall the Cisco Digital Subscriber Line Manager (CDM) software application and how to upgrade from CDM Release 3.3(x) to Release 3.4.2 and CDM Release 3.4 to Release 3.4.2. This document describes deployment options and specifies system requirements for different installations. The document also includes details about setting up and administering a CDM workstation.
You can deploy CDM in a distributed configuration to utilize the power of multiple computers. Two types of deployment are available:
CDM Release 3.4.2 Client—Includes only the client software
CDM Release 3.4.2 Manager—Includes the server and client software
Note For you to install the CDM Release 3.4.2 Manager package, Cisco EMF must be running. When
the installation menu displays, if you choose to install the CDM Release 3.4.2 Manager package
(rather than the Client package), the installation software displays the message "Incompatible
type C" next to any options that are incompatible with your configuration.
Note You can install CDM more quickly if you are installing CDM for the first time and you have
never run Cisco EMF or you have reset the database. The instructions for this faster type of
installation are included in the
"Installing CDM Using the
cdminstall Script" section.
CDM Server Installation
Each CDM deployment must have a CDM server installed. Processes on the CDM server keep track of the current state of the network model, user access, and events (alarms). You should also install the Object Store database system on the computer that is being used as the server. See the Cisco Element Manager Framework Installation and Licensing Guide for details on installing Cisco EMF and the Object Store database system.
CDM Client Installation
A CDM deployment allows CDM clients to be installed on workstations that are separate from the CDM server. This client workstation runs CDM applications to access objects on the server. A client installation contains only those parts of the CDM system that are necessary for a CDM user session. This user session communicates with the CDM server when it is required to retrieve management information. The CDM applications that generate the GUI run on the CDM client computer, which allows for a more scalable solution.
The CDM client installation process installs the client software on the local computer; this means that you do not need to mount files across a network. Network traffic occurs only when the client requires more data from the server.
Note The CDM server installation process also installs all of the files that are required for the establishing of
a client-to-server session on a single computer. Therefore, you can install the entire CDM system,
including both server and client, on the same computer. You can then install the client on additional
computers as required.
System Requirements
You can deploy CDM in a number of different configurations, from a single hardware system to a multiworkstation distributed management system that uses Sun Solaris/SPARC hardware with Solaris, Release 2.8. Computer specifications are detailed in the following sections.
Small Site Requirements
In the context of CDM Release 3.4.2, a small site is one that manages no more than 25 to 50 DSLAMs. As you add more DSLAMs, memory requirements increase. You might be able to manage a few more DSLAMs than you are already managing by increasing the memory and swap space on your computer. The CDM server requires about 2 GB RAM when it starts up. If your computer has less than 2 GB RAM, some processes will be swapped out to disk, and most processes will run more slowly. Always set up the swap space to be at least 2 to 3 times the amount of memory on the computer.
We recommend that you have no more than one to three users on the CDM server computer. If you need to support more users, it is recommended that you set up a separate computer with the CDM client software. A small site configuration that has a client and a server computer should be able to support from six to eight users.
The computer specifications for a small site are described in the following sections.
Minimum System Requirements for a Small Site
The server computer must meet the following minimum requirements:
Sun Blade 2000 Workstation
Two 1.05 GHz Ultra SPARC iii CPU @ 900 MHz
1 GB RAM or greater
Two 7200 rpm internal drives, 15 GB total
4 GB swap space
17-inch color monitor
Recommended System Configuration for a Small Site
We recommend the following configuration for the server computer of a small site:
Sun Blade 2000 Workstation
Two 1.05 GHz Ultra SPARC iii CPU @ 900 MHz
1.5 GB RAM
Three 40-Mbps 10 K rpm internal disks, 18.2 GB each
3 to 4 GB swap space or larger
21-inch color monitor
Large Site Requirements
In the context of CDM 3.4.2, a large site is one that manages more than 50 DSLAMs. As you add more DSLAMs, the memory requirements increase. You might be able to manage a few more DSLAMs if you increase the memory and swap space on your computer. The CDM server requires about 2 GB RAM when it starts up. If your computer has less memory, some processes will be swapped out to disk and most processes will run more slowly. You should always set up the swap space to be at least 2 to 3 times the amount of memory on the computer.
It is very important that you set up the Object Store database on RAW file systems and across as many disk drives as you can afford. Use striping to divide the database across as many disk drives as possible to increase database performance. See the "Allocating Disk Space" section for instructions on how to use the striping method.
We recommend that you have no more than one to three users on the CDM server computer. If you need to support more users, set up a separate computer with the CDM client software.
For a large site, consider the computer specifications that are described in the following sections.
Minimum System Requirements for a Large Site
The server computer for a large site must meet the following requirements:
Sun Enterprise 420R
Four Ultra SPARC iii processors @ 900 MHz
Four 10 K rpm hot plug drives, 9 GB each
Object Store database set up as RAW file system (rawfs)
4 GB RAM
8 GB swap space
17-inch color monitor
Recommended System Configuration for a Large Site
We recommend the following configuration for the server computer of a large site:
Sun Enterprise 420R or Sunfire V480Sun Enterprise 420R or Sunfire V480
Four Ultra SPARC iii processors @ 900 MHz
16 GB RAM
Six to eight 10,000 rpm 18-GB drives
Three Ultra SCSI controllers
Four disks configured as a rawfs for ObjectStore
24 GB swap space
21-inch color monitor
Client Workstation Requirements
You can have multiple client computers connected to the CDM server manager computer. The more CPU power you have on the client computer, the more client sessions you can support.
In larger deployments that have client-server configurations, we recommend the following hardware specifications for typical client deployments:
Sun Ultra 5/10 workstation
256 MB RAM
2 GB swap space
Support for one local session
Sun Ultra 60
2 CPUs
512 MB RAM
2 GB swap space
Support for four to seven X-Terminal sessions
Sun Blade 2000
8GB RAM
16 GB swap Space
CPU: 900 MHz (x1) Ultra SPARC iii
Client installation for more than one session
21-inch color monitor running at 1280 x 1024 resolution
Note You can use smaller monitors. We recommend the 17 to 21-inch monitors because they provide the best
view of the CDM GUI windows.
Note It is useful to have a Sun color card (for example, 24-bit color) if you are running many graphically
intensive applications on this workstation.
Recommended Solaris Patches and UNIX Kernel Parameters
This section includes recommendations about Solaris patches that you should install and UNIX kernel parameters that you should set.
Recommended Solaris Patches
It is recommended that a customer install the latest Solaris patches for Solaris 2.8. This patches can be downloaded from the Sun website at the following location:
CDM 3.4.2 scalability was tested with kernel patch 108528-16and related cluster patch that came out on August 2002. If you machine has this patch or later it should work with CEMF and CDM. It is also recommended that you install the year 2000 Solaris patches.
Note CEMF has been known to have problems with kernel patch 105181-04 and earlier.
To check the patches installed on your machine use the command showrev -a.
The applied patches are shown in the following output:
The following UNIX kernel parameters are recommended for running Cisco EMF/CDM server computers.
These parameters are recommended for Sun Enterprise 450 servers with 4 GB of RAM and four CPUs. These parameters are located in /etc/system file. You can verify the running parameters by running the /etc/sysdef report.
set priority_paging=1
set fastscan=131072
set handspreadpages=131072
set maxpgio=65536
Sun recommends setup priority paging as specified above. It may be normal to have high paging and scan rates; it is likely that the page scanner will be putting too much pressure on Cisco EMF/CDM's private process memory. If we scan a rate of several hundred pages or more per second, the amount of time that page scanner takes to check whether a page has been accessed falls to a few seconds. This means that pages that have not been used in the last few seconds will be taken by the page scanner when you are using the file system. This behavior can negatively affect application performance and is the reason why priority paging was introduced.
It is believed that the file system is being exercised quite a bit in CEMF to log information and for the transaction log file so it would be good to enable priority paging.
Hardware Configuration Requirements
This section includes information and instructions about the hardware requirements for your Cisco DSLAM configuration and configuration information for the UNIX server. This section includes the following topics:
If you have a large site, we recommend that you install the Object Store database on a RAW disk partition. This recommendation is based on the reasons that follow. (If you are not sure whether you should install the Object Store database on a RAW disk partition, read this section before you decide.)
1. With the version of Object Store that CEMF 3.2 uses, a database table cannot increase beyond 2 GB. This limitation can be a problem if you manage 150 DSLAMs or more, because the number of alarms in the alarm database might increase to the point of requiring more than 2 GB. The configuration information might also increase beyond 2 GB.
2. The Object Store transaction log file (journal file of database changes) can increase beyond 2 GB. This critical file is the most heavily written file in the system and performs better if striped (divided or distributed) across several RAW disk drives.
3. Performance should improve if you use RAW partitions because you do not incur the UNIX file system overhead.
We recommend the following configurations:
1. The RAW disk drives should be striped because Object Store does not efficiently spread the data among the disk drives. You should stripe the ObjectStore RAW disks to evenly distribute the disk I/O among the disk drives. To set up this type of configuration, you can use DiskSuite from Sun Microsystems or a third party product such as Veritas, or a hardware RAID controller.
2. You should also stripe the database across several disk drives to achieve the best performance.
Note If you are certain that your database will not increase beyond 2 GB and you are managing fewer than
100 DSLAMs, it is acceptable to place the database on a UNIX (cooked) file system. If you do that, we
recommend that you place the transaction log file on a disk drive that is separate from the drive on which
the database is located. Refer to the Cisco Element Management Framework Installation and
Administration Guide for instructions on putting the transaction log file on a separate disk. Here is the
URL for that book: http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cemf/3_2/index.htm
Allocating Disk Space
To maximize the performance of your CEMF/CDM system, you need to first plan how you will allocate your disk drives. Consider the following objectives as you plan your system configuration:
1. Use as many disk drives as you can. The disk drives should be as fast as possible, for example, 10,000 rpm.
2. Spread the disk drives across several SCSI controllers to prevent SCSI bottlenecks.
3. Set the swap space to be two to three times the amount of memory on the computer and to be at least 4 GB, if possible. The swap space should be RAW disk partitions across several drives. You can also put the swap partitions on the same disk drives as the Object Store database, because they have relatively low disk I/O activity.
4. Allocate some space for database backups. We recommend that you back up the database daily. The system defaults to performing a full backup on Sundays and an incremental backup each day. Try to allocate enough disk space to store at least 2 weeks of backups. For example, if you are managing 250 DSLAMs, you would need about 3 GB of disk space for a backup, or 6 GB for 2 weeks of backups.
5. Set aside at least 1 to 2 GB of disk space for the CEMF/CDM application log files, which can increase significantly when you are debugging system issues.
System Configuration for Four or Six Disk Drives
This section describes a way to partition your database across four disk drives or across six disk drives through the use of a concatenated meta device and a striped meta device. The partitions that are striped should all be the same size, but the concatenated partitions can vary in size.
For a system that has four disk drives, we recommend the disk drive setup that is shown in Figure 1:
Figure 1 Diagram of Disk Drive Setup for a System with Four Disk Drives
In the concatenated meta device shown in Figure 1, the disk space is concatenated across three drives. In the striped meta device shown in Figure 1, the RAW device file is striped across three drives.
For a system that has six disk drives, we recommend the disk drive setup that is shown in Figure 2.
Figure 2 Diagram of Disk Drive Setup for a System with Six Disk Drives
In the concatenated meta device shown in Figure 2, the disk space is concatenated across five drives. In the striped meta device shown in Figure 2, the RAW device file is striped across five drives.
The more disk drives your system includes, the better the disk performance will be for database access, especially if the disk drives are on different SCSI controllers.
Setting Up Disk Partitions
The Solaris operating system includes a utility for disk partitioning and maintenance called format. This utility lists all of the physical disk drives in the system and allows you to define the size of partitions and label the disk drives. You cannot modify a disk that is currently mounted, but you can use the format utility to partition all the drives for the Object Store database, as described in the previous section.
Each drive can have eight partitions, numbered from 0 to 7. Partition 2 is reserved for the total disk, and partition 1 is generally reserved for any swap space that you want to define. Remember that after you make any changes to the partition sizes, you need to label the disk to write (save) the partition map. For more information, see the UNIX man pages on format.
Setting Up Meta Devices Using DiskSuite
After you set up the disk partitions, spread the UNIX device files across the disk drives. This arrangement produces a meta device. You can use DiskSuite to set up the concatenated meta device as described in the previous section.
You can download DiskSuite and related documentation and information at the following web site:
You can use DiskSuite to set these meta devices as RAID 0, 1, and 5. You want to use RAID 0, which is also called disk striping. Disk striping allows you to spread I/O load across several disks. Doing so improves application performance by increasing the storage I/O throughput that is available to a single process.
Note Do not create the meta device for Object Store as a RAID 5 device, or performance quality will be poor.
Use RAID 3 or 5 for Object Store only if you have a hardware RAID controller because software RAID
is very slow.
After you create the meta device, use the UNIX utility newfs to create a UFS file system on the meta device.
Setting Up the Object Store Database on RAW File System
For specific instructions on installing Cisco EMF and setting up the Object Store database on a RAW file system (RAWFS), refer to the "RAW File System (RAWFS)" section in Chapter 5 of the Cisco Element Management Framework Installation and Administration Guide at:
During the Cisco EMF installation process, the installation script asks if you want the Object Store database on a UNIX (cooked) file system or on a RAW file system. If in your configuration plans you have chosen to install the database on a RAW file system, enter y for yes to that question in the Cisco EMF installation script. Allow the system to default to the path where the database is to be installed. After you install Cisco EMF and any related patches, and after you have configured your disk drives and set up striping, you need to configure the Object Store database with the device names of your RAW striped partitions.
Note The following procedure is an abbreviated set of steps. Refer to the "RAW File System (RAWFS)"
section in Chapter 5 of the Cisco Element Management Framework Installation and Administration
Guide for more detailed steps.
Complete the following steps to set up the Object Store disk to use RAW after you have installed Cisco EMF. In these steps, assume that you installed Cisco EMF in /opt/cemf. If this is not the case, modify the locations.
Step 1 Log into the CEMF shell as root by entering the following command:
Edit this file to define the RAW device for the striped meta device that you created, as shown in the example that follows. The meta device is most likely to be the following path: /dev/md/rdsk/d0. You should also remove the Log File line in this file so that the transaction.log file is placed on the RAW striped disk.
Replace the line, Log File: /ext/dblog/transact.log with Partition0: PARTITION /dev/md/rdsk/d0
The _server_parameters file after you make this change:
Partition0: PARTITION /dev/md/rdsk/d0
Cache Manager Ping Time: 20000
Cache Manager Ping Time In Transaction: 20000
Step 3 Save the file.
Step 4 Run the command to initialize the RAW disk so that ObjectStore can use it:
/opt/cemf/ODI/OS5.1/ostore/lib/osserver -i
Now you can continue installing CDM and then start Cisco EMF to create the database.
Setting Up the Cisco DSLAM Chassis Hardware
Make sure that you properly set up and configure your hardware (Cisco 6015, 6100, 6130, 6160, or 6260 DSLAM chassis with NI-2 card) and that you can communicate with the node from the CDM server.
Documentation for setting up Cisco DSLAM hardware is available at the following web site:
The CDM software communicates with a Cisco DSLAM by transmitting Simple Network Management Protocol (SNMP) messages from the Sun workstation on which CDM resides through the Ethernet port on the NI-2 card of the DSLAM.
To configure an Ethernet port using a terminal console, complete the following steps:
Step 1 Set a privileged command password as follows:
Step 2 Configure the Ethernet management port on the NI-2 card as follows:
Switch> enable
Password: <ENABLE PASSWORD>
Switch# config terminal
Switch (config)# interface Ethernet 0/0
Switch (config-if)# ip address <ADDRESS> <NETMASK>
Note When you configure the IP address, you can issue the command no shutdown to prevent the
Ethernet port from shutting down.
Switch (config-if)# exit
Switch (config)# exit
Switch#
Step 3 Ensure that the 10BaseT Ethernet port on the NI-2 card is connected to the same network as the CDM server.
Note The Sun Ultra 60 running CDM should now be able to ping the NI-2 card.
Step 4 Configure the NI-2 card to be SNMP manageable as follows:
Switch> enable
Password: <ENABLE PASSWORD>
Switch# config terminal
Note The read-only and read-write community strings on the NI-2 card must match the read-only and
read-write community strings that are used when you deploy the NI-2 in CDM.
Switch (config)# snmp-server community <Read Only Community Name> ro
Switch (config)# snmp-server community <Read Write Community Name> rw
Switch (config)# snmp-server enable traps
Note Substitute ADDRESS in the following command with the IP address of the manager server
where Cisco EMF is installed.
Switch (config)# snmp-server host <ADDRESS>traps version 2c <Community Name>
Switch (config)# exit
Step 5 Configure the NI-2 card to accept a Telnet session as follows:
Connection Manager, telnet <IP ADDRESS OF DEVICE NI-2>
Switch> enable
Password: <ENABLE PASSWORD>
Switch# config terminal
Switch (config)# line vty 0 4
Switch (config-line)# password <TELNET PASSWORD>
Switch (config-line)# login
Switch (config-line)# exit
Switch (config)# exit
Switch#
Note To confirm that Telnet is enabled after you configure the Ethernet port, enter telnet
<ADDRESS> from the Sun Ultra 60 that is running CDM.
Setting Up TFTP
To set up CDM so that you can back up or restore configuration data, you need to configure your CDM UNIX server to provide TFTP services to each Cisco DSLAM chassis as it boots. To do this, you must configure the workstation to support TFTP. To set up TFTP, complete the following steps:
Step 1 Verify that there is an entry for TFTP in /etc/intd.conf file.
Step 2 As the root user, execute the following commands:
mkdir /tftpboot
cd /tftpboot
ln -s . tftpboot
Step 3 Copy the Cisco 6100/6130 Series images to the /tftpboot directory.
License Requirements
CDM uses Cisco EMF, which requires a license key to operate. You can find information about how to obtain a license key in the Cisco Element Management Framework Installation and Administration Guide, or you can contact the Cisco Technical Assistance Center (TAC) for assistance.
Data Migration Utilities
This section tells you how to move data from CDM 3.3(x) to CDM 3.4.2. It includes the following sections:
Note You must use the migration utility that is described in this section, rather than the Cisco EMF upgrade
tool, because the object model for CDM 3.4.2 is different from that for CDM 3.3x. Therefore, you cannot
use the Cisco EMF upgrade tool to upgrade your CDM 3.3x database to CDM 3.4.2.
Downloading the Data Migration Utility Packages from the Cisco Web Site
To access the CDM 3.4.2 migration utility packages on the Cisco web site, complete the following steps:
Step 1 Access the Cisco web site in one of the following ways:
www.cisco.com
Telnet: cco.cisco.com
Use a modem, standard connection rates, and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.
From North America, call 408 526-8070
From Europe, call 33 1 64 46 40 82
Step 2 Click Software Center under Service and Support.
Step 3 Click Login on the menu bar.
Step 4 In the Login dialog box, type your user name and password, and click OK.
The Technical Assistance Center web page displays.
Step 7 Under Select a File to Download, click CDMUTL-3.4.2.tar.Z.
Step 8 Click CDMUTL-3.4.2.tar.Z next to Download to download the tar file.
A dialog opens that asks you what you want to do with the file.
Step 9 Select Save it to Disk, then specify the directory to which you want to save the tar file.
Step 10 Click Save to save the tar file to your local directory.
CDM 3.3.x to CDM 3.4.2 Upgrade Overview
This section tells you how to upgrade from CDM 3.3x to CDM 3.4.2. You must be running Cisco EMF 3.0.4 and CDM 3.3.x to use the CDM 3.4.2 migration utility. The data migration utility files include two packages—a CDM migration save package named CDMMigSav, and a CDM migration restore package named CDMMigR.
There are two basic scenarios for migrating your data from CDM 3.3x to CDM Release 3.4.2:
In-place Migration—The first scenario involves migrating data when you are running CDM 3.3x on one computer (Sun workstation). In this case, you back up your database, install the data migration save package, and then save your configuration data. Next, you must uninstall CDM 3.3.x, the data migration package, and Cisco EMF 3.0.4. Finally, you install Cisco EMF 3.2 and any patches, install CDM, install the data migration restore package, and then restore your data. Finally you remove the data migration restore package.
Cutover Migration—The second scenario involves migrating your data when you have one computer on which Cisco EMF 3.0.4 and CDM 3.3.x are installed and a second computer on which you can install the new versions. In this case, you perform a cutover backup and restore procedure. That is, you back up your configuration data on the computer that is running CDM 3.3.x, run the migration save package on this computer, install Cisco EMF 3.2 and any patches, and then install CDM 3.4.2 on the second computer. You use the ftp command to send your saved configuration data from the computer that is running CDM 3.3.x to the computer that is running CDM 3.4.2. Finally, you run the migration restore package on the computer that is running CDM 3.4.2. The sections that follow specify which steps are for the one-computer scenario and which are for the multiple-computer (cutover) scenario.
In summary in migrating from CDM 3.3.x to CDM 3.4, only CDM DM (consisting of DM-Save & DM-Restore) is use. For migration to CDM 3.4.2, we now have COM DM also.
CDM 3.3.x -> CDM 3.4.2:
Only need to run CDM DM.
DM-Save on the CDM 3.3.x system and
DM-Restore on the CDM 3.4.2 system.
CDM 3.4 -> CDM 3.4.2:
Only need to run COM DM on the CDM 3.4.2 system.
Note If your configuration includes a small number of DSLAMs, you might consider starting over rather than
using the data migration procedure that is described in this section. If you choose to install CDM 3.4.2
without running the data migration utilities, first back up your database, and uninstall the earlier versions
of Cisco EMF and CDM. Then install Cisco EMF 3.2 and any related patches and CDM 3.4.2. Finally,
use the autodiscovery process to discover the network objects in your configuration. By using this
method, you can retrieve most of the data from your previous configuration. However, the names of
PVCs, SPVCs, VCLs, and ATM QoS profiles will be different from those in your previous configuration.
Note The data migration utility depends on the auto-sync feature of CDM 3.4.2 to restore modules, interfaces,
and ATM QoS profile data from the DSLAM nodes. The utility does not upload ATM QoS profiles that
are not applied to a specific connection.
You can use the migration utility procedure to save and then restore the following information from your CDM 3.3.x configuration:
DSLAM topology (tree hierarchy)
Module data
Port data
PVC and SPVC names
ATM QoS profile names
Subtend topology
Subtend PVCs/SPVCs
Note The data migration save part of the utility does not save the module, port, and subtend topology data;
however, this data is restored from the node through subrack discovery when you commission the
DSLAMs. (Autodiscovery discovers the nodes and subrack discovery discovers line cards
and interfaces.)
Note After you have completed the migration utility procedure and synchronize the DSLAM,
CDM rediscovers the xDSL profiles that are resident on the node.
Note Any current active alarms are migrated, but alarm history,performance history, usernames and groups
data are not migrated. These will need to be setup manually after the data migration.
Table 1 outlines the basic steps for upgrading from CDM 3.3x to CDM 3.4.2 through the use of the in-place migration scenario. These steps are described in greater detail in the "Upgrading from CDM 3.3.x to CDM 3.4.2" section.
Table 1 CDM 3.3 to CDM 3.4.2 Upgrade Steps for In-Place Migration
Step
Description
1.
Back up the database.
2.
Install the data migration save package.
3.
Run the data migration save part of the utility.
4.
Verify that the data is properly saved by checking the data files and log files.
5.
Uninstall the data migration save package.
6.
Uninstall CDM 3.3x and Cisco EMF 3.04.
7.
Install Cisco EMF 3.2 and any Cisco EMF patches.
8.
Install CDM 3.4.2.2 on the server.
9.
Install the DM-Restore package.
10.
Run the data-migration restore utility. This part of the utility creates the DSLAMs, triggers commissioning (subrack discovery and autosync of PVCs and ATM QoS profiles), and creates subtend PVCs (but not the PVCs under them). You will choose 1 from the Data Migration Utility Restore menu for this step.
11.
Wait for commissioning and autosync to complete. Verify that the data is properly restored in the Map Viewer log files (the names of the log files will be different). You will choose 2 from the Data Migration Utility Restore menu for this step.
12.
Run data migration restore. This steps renames the PVCs, SPVCs, VCLs, and ATM QoS profiles. This step also adds subtend PVCs to the Subtend PVC hierarchy view. This steps corresponds to choice 3 from the Data Migration Utility Restore menu.
Table 2 outlines the basic steps for upgrading from CDM 3.3x to CDM 3.4.2 using the cutover migration scenario. The term "old computer" refers to the computer on which CDM 3.3x is installed; the term "new computer" refers to the computer on which you are installing CDM 3.4.2. These steps are described in greater detail in the "Upgrading from CDM 3.3.x to CDM 3.4.2" section.
Table 2 CDM 3.3 to 3.4.2 Upgrade Steps for Cutover Migration
Step
Description
1.
Install the data migration save package on the old computer.
2.
On the new computer, install Cisco EMF 3.2 and any patches, install CDM 3.4.2, and then start Cisco EMF.
3.
Install data migration restore package on the new computer.
4.
On the old computer, run the data migration save utility, verify the saved data and migrate log, and then use the ftp command to copy the saved data files over to the new computer.
5.
On the new computer, run the data-migration restore utility. This part of the utility creates the DSLAMs, triggers commissioning (subrack discovery and autosync of PVCs and ATM QoS profiles), and creates subtend PVCs (but not the PVCs under them). You will choose 1 from the Data Migration Utility Restore menu for this step.
6.
Wait for commissioning and autosync to complete. Verify that the data is properly restored in the Map Viewer log files (the names of the log files will be different). You will choose 2 from the Data Migration Utility Restore menu for this step.
7.
Run data migration restore. This steps renames the PVCs, SPVCs, VCLs, and ATM QoS profiles. This step also adds subtend PVCs to the Subtend PVC hierarchy view. This steps corresponds to choice 3 from the Data Migration Utility Restore menu.
8.
After you have verified that all data is properly restored, remove the data migration restore package.
Note If you perform a cutover migration, running DM-Save on the old computer "after" installing Cisco
EMF/CDM/DM-Restore and starting CEMF/CDM on the new computer can significantly reduce the
cutover time. This is the prefered method, but requires an additional or temporary machine
Upgrading from CDM 3.3.x to CDM 3.4.2
This section includes the steps for upgrading from CDM Release 3.3.x to CDM Release 3.4.2 and includes the following sections:
Complete the following steps to back up your database. You should have Cisco EMF 3.0.4 and CDM 3.3x installed.
Step 1 Make sure there are no client users on the system during the upgrade process.
Note We recommend that you install Cisco EMF in the /opt/cemf directory; this is the default.
Note We recommend that you back up your database (in case, for some reason, you decide to abort
the installation of the new release and restore the backup of the original software and database).
The default backup directory is /opt/AVBackup/<Date-Sunday-of-current-week>, unless you
have changed the directory for backups.
Step 2 Check the available space of the backup directory to ensure that it is sufficient for restoring your database.
Step 3 Back up your current Cisco EMF and CDM database by entering the following command or a similar backup command: /opt/cemf/bin/cemf backup
The CDM utility creates a subdirectory named CDMMigrateSave.
Step 2 Change to the CDMMigrateSave subdirectory by entering the following command:
cd CDMMigrateSave
Step 3 Install the package by entering the following command:
./dminstall
Step 4 Create a data subdirectory such as the one that follows:
mkdir /opt/DataMigration/data
Step 5 Make sure you have write permission to this directory by entering the following command:
chmod 666 /opt/DataMigration/data
Step 6 Make sure you are root, and then execute the Cisco EMF shell by entering:
/opt/cemf/bin/cemf shell
Step 7 Change to the following directory to run the perl command as follows:
cd /opt/cemf/config/extractInfoTool/perl
With this utility, the assumption is that CDM is installed in the /opt/cemf directory, which is the recommended directory. If it is not, We recommend that you make a symbolic link and name it /opt/cemf; this link will point to the directory in which CDM 3.3.x is installed. You must execute this script from the /opt/cemf/config/extractInfoTool/perl directory.
Step 8 Enter the following command to save the DSLAM data in CDM 3.3x:
Selecting option 1 creates several files in the current directory. CDM uses these files later to recreate the DSLAMs after you install and upgrade to CDM 3.4.2.
The following script displays on your screen:
Save CDM3.3 Dslams data will overwrite any previous saved data. Continue? [n]: y
Step 10 Enter y to overwrite any previous saved data.
The following script displays on your screen:
Please specify the full path of all the data migration output file
Note Make sure the CDMMigrateSave directory is located in a directory other than the cemf directory;
you will need the data after you have installed and upgraded CDM.
Step 11 Enter the following path (you created this subdirectory in Step 4):
/opt/DataMigration/data
The following script displays on your screen:
Migration In Progress...
1 = Save Dslam data
x = Exit
Enter the desired option:
x
Step 12 Enter x to exit.
Note The DM-Save utility can be run at any time and the out put generated can be used to analyse the
data that would need to be transfered in the event of a migration.
Downloading and Installing Cisco EMF 3.2 and Related Cisco EMF Patches
To download and install Cisco EMF and any related patches, you must refer to the Cisco Element Management Framework Installation and Administration Guide.
Note You must install Cisco EMF before you install CDM.
Uninstalling Cisco EMF and CDM
If you are installing Cisco EMF 3.2 and CDM 3.4.2 on one server, you must first uninstall any earlier versions of Cisco EMF and CDM that you currently have installed. Use the -r options at the end of the installation utility script to remove previously installed packages. Remove CDM first, and then remove Cisco EMF.
Installing CDM 3.4.2
Upgrade to CDM 3.4.2 by downloading CDM for NI-2 . Complete the following steps to continue the upgrade procedure and install CDM 3.4.2:
Step 1 Make sure that you have installed CEMF 3.2 and all the related Patches
Step 2 Change to the CDM342 subdirectory by entering the following command: cd CDM342
Step 3 Install the package by entering the following command: ./cdminstall
If you are running CDM on more than one computer, that is, if you are using the cutover migration method, you need to transfer your data from the computer that is running CDM 3.3x to the computer that is running CDM 3.4.2.
Complete the following steps:
Step 1 On the computer that is running CDM 3.4.2, create a data subdirectory such as the one that follows:
mkdir /opt/DataMigration/data
Step 2 Make sure you have write permission to this directory by entering the following command:
chmod 666 /opt/DataMigration/data
Step 3 Use the cd (change directory) command to change to this directory.
Step 4 Use the ftp (network file transfer system) utility to transfer the saved configuration files from the computer that is running CDM 3.3x:
a. Enter ftp <name or IP address of computer that is running CDM 3.3x>.
b. Enter your user name and password.
c. Make sure you are root and change to the CDMMigrateRestore directory: cd /opt/DataMigration/data
d. Use the following ftp utility commands to transfer the saved configuration data files:
Restoring the DSLAMs could take several minutes, depending on the number of DSLAMs that were commissioned in your previous version of CDM. This process redeploys all NI-2 cards that you saved previously and sends a commission request on any NI-2 cards that were not decommissioned in the previous system.
During the restoring data process a lot of disk space may be used if debug is on and the system may run out of disk space which would cause the restore process tohang. In order to track this a Disk Monitoring utility is provided. The utility can be used to periodically check a particular disk if it exceeds a given disk space. During restore this utility will run as a background process and alert the user if the system runs out of disk space.
This utility can also be executed independent to the restore script by the following command:
Note Creating and commissioning a large group of DSLAMs requires all of the system resources;
allow the process to complete before you use the system for anything else.
Complete the following steps to restore the data:
Step 1 Change to the CDMMigrateRestore subdirectory by entering the following command:
cd CDMMigrateRestore
Step 2 Install the package by entering the following command:
./dminstall
Step 3 Make sure you are working within the cemf shell by entering the following command:
/opt/cemf/bin/cemf shell
Step 4 Change to the /opt/cemf/config/restoreInfoTool/perl directory as follows:
cd /opt/cemf/config/restoreInfoTool/perl
Step 5 Enter the following command to restore the DSLAMs and synchronize profiles and PVC connections:
This steps checks to make sure that the DSLAMs are in a normal state before you proceed to select choice 3, to discover subtend topology, restore PVC/SPVC/VCL profiles, and reconstruct the subtend PVC view.
Caution It is important that you wait before you proceed with discovery until you are certain that all DSLAMs are in a normal state. Once the DSLAMs are in a normal state, you know that CDM has uploaded all PVCs, SPVCs, subtend PVCs, and ATM QoS profiles from the network. Once this initial network state has been reached, a small number of DSLAMs might briefly transition from normal to synchronizing and back; this is normal.
Note If one or two DSLAMs are in an errored state and the error is not something that you can correct at this
time, you can proceed and correct the error after the restore process is complete.
The following script displays on your screen:
Check Dslams status. Continue? [n]: y
Step 10 Enter y to continue; the following script displays on your screen:
Status of "Physical:/192.168.254.24-shelf/192.168.254.24-6130Chassis": normal
Status of "Physical:/192.168.254.22-shelf/192.168.254.22-6100Chassis": Performanceloggingon
Total Number of chassis in normal state: 2
Total Number of chassis in discovery state: 0
Total Number of chassis in synchronizing state: 0
Total Number of chassis in other states(discoverylostcomms,etc): 0
Please specify the full path of the Data Migration data directory
(NOTE: This directory should have the write permission)
Step 13 Enter the full path of the data migration directory, for example:
/opt/DataMigration/data
This process determines which DSLAMs are currently deployed. The server upgrade should now be complete. You can log in to CDM while the restore and synchronization process is occurring; however, not all the data is reflected in the GUI until the utility completes.
Step 14 Check the output file named restore_<pid>.rpt in the /opt/DataMigration/data directory for any errors. (Errors are marked with the message *** FAILED ***.)
Step 15 Remove the data migration restore package by entering the following command:
./dminstall -r
CDM 3.4 to CDM 3.4.2 Upgrade
This section includes the steps for upgrading from CDM Release 3.4 to CDM Release 3.4.2 and includes the following sections:
Complete the following steps to back up your database. You should have Cisco EMF 3.2 , all related CEMF patches and CDM 3.4 installed.
Step 1 Make sure there are no client users on the system during the upgrade process.
Note We recommend that you install Cisco EMF in the /opt/cemf directory; this is the default.
Note We recommend that you back up your database (in case, for some reason, you decide to abort
the installation of the new release and restore the backup of the original software and database).
The default backup directory is /opt/Backup/<Date-Sunday-of-current-week>, unless you have
changed the directory for backups.
Step 2 Check the available space of the backup directory to ensure that it is sufficient for restoring your database.
Step 3 Back up your current Cisco EMF and CDM database by entering the following command or a similar backup command: /opt/cemf/bin/cemf backup
Downloading CDM 3.4.2 and related CEMF 3.2 patches
You will have to download the CDM 3.4.2 release and any related Cisco EMF 3.2 patches.
Download CDM 3.4.2 from Need URL
Download Cisco EMF 3.2 related patches To download and install Cisco EMF and any related patches, you must refer to the Cisco Element Management Framework Installation and Administration Guide.
Note You must install Cisco EMF before you install CDM.
Note See the Release Notes for the Cisco DSL Manager, Release 3.4.2, to determine the correct Cisco
EMF patch.
Upgrading to CDM 3.4.2
Note In order to upgrade, CEMF 3.2 & related patches and CDM 3.4 must be installed and CEMF and CDM
process must be running.
Complete the following steps to Upgrade from CDM 3.4 to CDM 3.4.2.
Step 1 Change to the CDM342 subdirectory by entering the following command: cd CDM342
Step 2 Install the package by entering the following command: ./cdminstall
Step 4 Make sure you are root, and execute the Cisco EMF shell by entering: /opt/cemf/bin/cemf shell
Step 5 Run the dataMigrator tool as follows: /opt/cemf/bin/dataMigrator Once this is over the system is ready for normal CDM 3.4.2 operations.
Step 6 To upgrade the CEMF patch related to CDM 3.4.2 you must refer to the Cisco Element Management Framework Installation and Administration Guide
Note While installing CEMF related patch there is no need to stop CEMF OR CDM. The script first
removes the old patches and then installs the new one.
Installing from a Remote CD-ROM Drive
To install software onto a system that does not have its own CD-ROM drive, mount the product CD on a remote system and then export the device to make it accessible over the network. Both of these operations are done on the remote system with the CD-ROM drive. Then mount the remote CD on the local system where the installation is to take place.
Step 1 Insert the CD into the CD-ROM drive on the remote host.
Step 2 Log on to the remote host as superuser.
Step 3 Check that the Volume Manager is running, by entering:
/usr/bin/ps -ef | grep vold
If the Volume Manager is running, a message similar to the following displays:
root 591 1 0 Feb 26 ? 0 :01 /usr/sbin/vold
Step 4 If the Volume Manager is not running, start it by entering:
/etc/rc2.d/S92volmgt start
Step 5 On the remote host, export the CD-ROM device as follows:
a. Start the NFS-related daemons by entering:
/usr/lib/nfs/nfsd 8
/usr/lib/nfs/mountd
b. Share the mount point from the remote host by entering:
share -F nfs -o ro /cdrom/cdrom0
c. Verify that this host has made the CD-ROM drive accessible by entering:
share
Note The listing that displays should include the /cdrom mount point.
Step 6 Mount the remote CD-ROM on the local host where the installation is to take place:
a. Create a mount point if none already exists by entering:
mkdir /mnt/cemfmnt
b. Mount the remote directory by entering:
mount <REMOTE-HOST> : /cdrom/cdrom0 /mnt/cemfmnt
Replace <REMOTE-HOST>with the host name of the remote device.
The contents of the CD are now listed under the /mnt/cemfmnt mount point.
Installing CDM Using the cdminstall Script
To install CDM, complete the following steps.
Note Cisco EMF (Release 3.2) and the correct Cisco EMF patch must already be installed and running before
you attempt to install the CDM software. See the Release Notes for the Cisco DSL Manager, Release
3.4.2, to determine the correct Cisco EMF patch.
Step 1 Log in as superuser.
Step 2 If you are installing CDM for the first time and you have never run Cisco EMF, or if you have reset the database and you want a quicker installation, skip to Step 5.
Step 3 If Cisco EMF is not running, enter the following command:
host# <CEMF_ROOT>/bin/cemf start
Replace CEMF_ROOT with the directory on which Cisco EMF is installed. Cisco EMF processes start.
Step 4 Insert the CDM CD-ROM and change to the CD-ROM directory by entering:
cd /cdrom/cdrom0
Step 5 Run the install script by entering the following command:
./cdminstall
A set of menu options display.
Step 6 Select one of the following installation options:
CDM Manager
CDM Client
Initial—Choose this option if you are installing CDM for the first time and you have never run Cisco EMF or if you have reset the database. If you choose this option, install CDM and then start Cisco EMF by entering the following command:
<CEMF_ROOT>/bin/cemf start
CDM automatically installs in the CEMF_ROOT directory.
If the Manager system has multiple network interfaces, the install script prompts you to select the appropriate interface.
The installation utility runs the appropriate installation. As each part of the installation occurs, informational messages display on the screen. Some messages might require user input, usually just yes or no.
For example, if an error occurs during installation, the installation process stops. Before the installation process stops, the install script prompts you to remove any software that was installed up to that time.
Step 7 After the installation is complete, remove the CDM CD-ROM.
You are now ready to run CDM.
Uninstalling CDM Release 3.4.2
When you run the cemfdeinstall script, all CDM processes are automatically stopped and uninstalled. Complete the following steps to uninstall CDM:
Step 1 Log in as superuser to the computer on which CDM is installed.
Step 3 Run the uninstallation script provided on the CD by entering the following command:
host# <CEMF_ROOT>/bin/cemf install -r -a
Note Be sure to include the second option, -a, to remove all files or errors will result.
Step 4 Choose one of the following uninstallation options:
CDM Manager
CDM Client
The installation script informs you that the uninstallation process is about to occur.
If you proceed with the uninstallation process, the screen scrolls through the software as it is deleted, and then the following message displays:
Removal of <package> was successful.
Starting a Cisco EMF User Session
When you start a Cisco EMF user session, CDM automatically starts at the same time. To begin a Cisco EMF user session, complete the following steps:
Step 1 Log in as superuser.
Step 2 If you have not started Cisco EMF, enter the following command:
<CEMF_ROOT>/bin/cemf start
Replace CEMF_ROOT with the directory on which Cisco EMF is installed. If Cisco EMF is already running, go to Step 3.
Step 3 To start a Cisco EMF user session, enter the following command:
<CEMF_ROOT>/bin/cemf session
Replace CEMF_ROOT with the directory on which Cisco EMF is installed.
Note You must invoke the cemf start command on the client workstation before you start the client
application.
Cisco EMF prompts you to enter a user name and a password.
Note The default user name is admin and the default password is admin.
The Cisco EMF and CDM processes start.
Stopping Cisco EMF
When you stop Cisco EMF, you also stop the CDM software application. Complete the following steps to stop Cisco EMF and CDM:
Step 1 In the Map Viewer window click the Close icon in the toolbar or choose File > Close to end any CDM sessions that are running.
Step 2 In the Cisco EMF Launchpad window, click the Quit icon in the toolbar or choose File > Quit to terminate your Cisco EMF user session.
Complete the following steps if you want to entirely stop all Cisco EMF processes; otherwise, you do not need to complete these steps:
Step 3 Log in as superuser.
Step 4 Enter the following command:
<CEMF_ROOT>/bin/cemf stop
Replace CEMF_ROOT with the directory on which Cisco EMF is installed.
The Cisco EMF and CDM processes stop.
Checking the Status of Cisco EMF
Note You must be logged in as superuser
To check the status of Cisco EMF, enter the following command:
<CEMF_ROOT>/bin/cemf status
where <CEMF_ROOT> is the directory in which Cisco EMF is installed.
If Cisco EMF is active, a list of running and non-running processes displays. Table 3 lists the information that displays for each process. The message "Cisco EMF system not running" displays if Cisco EMF is inactive.
Table 3 Process Information
Displayed Information
Description
Level
Specifies the run level for this process.
Process-tag
Displays the unique name used to identify a process
PID
Specifies the process ID for this process
Run-Status
Indicates the current run status for this process. Unless you are installing new packages, stopping or starting Cisco EMF, or you have explicitly stopped a process, the run-status should be "running."
Command
Specifies the command used to start this process.
Caution Processes that show a run status of "tooManyRestarts" should be analyzed. This message indicates that something is wrong with the current system and that the relevant process is constantly exiting while starting up.
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription. Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
We appreciate your comments and feedback about Cisco documentation. There are several ways to submit comments to Cisco.
If you are reading Cisco product documentation on Cisco.com, you can obtain a comment form electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your technical documentation comments to bug-doc@cisco.com.
You can submit your comments by mail. Write to the following address:
Cisco Systems Attn: Document Resource Connection 170 West Tasman Drive San Jose, CA 95134-9883
If you are a registered Cisco.com user, you can submit comments electronically.
To report problems, click Feedback in the toolbar at the top of any document web page, press the Contact Cisco Now button, and under Problem Type, select CD/Online Documentation. After you complete the form, click Submit to send it to Cisco.
To send your opinion of the DSL documentation, go to the following URL:
and click here at the top of the page in the sentence "Is this Cisco documentation helpful? Click here to give us your feedback." This displays a Documentation Survey that you can complete and submit to Cisco electronically.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
Contacting TAC by Using the Cisco TAC Website
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.
P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.
CCIP, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0201R)
