|
|
September 5, 2000
This document explains how to install and uninstall the Cisco Digital Subscriber Line Manager (CDM) software application. It describes deployment options and specifies system requirements for different installations. Details about setting up and administering a CDM workstation are also included.
 |
Note Cisco does not support Cisco Element Management Framework (EMF) and CDM running on the same machine as ViewRunner for HP OpenView. If you are installing CDM on a Sun UNIX server that is currently running ViewRunner for HP OpenView, you must uninstall ViewRunner and HP OpenView or bring HP OpenView down and disable them both from starting before you install Cisco EMF and CDM 3.0. If you do not uninstall or disable them, the system will try to start both HP OpenView and Cisco EMF/CDM when it boots. If this happens, traps sent from your DSLAM chassis will not be processed by CDM. HP OpenView must not be running when Cisco EMF is running. For further information, see the "Disabling ViewRunner and HP OpenView" section. |
This document includes the following sections:
You can deploy CDM in a distributed configuration to utilize the power of multiple computers. Two types of deployment are available:
|
Note To install the CDM Release 3.2 Manager package, the Cisco Element Management Framework (EMF) must be running. If you choose to install the CDM Release 3.2 Manager package, the installation software displays the message "Incompatible type C" next to any option that you should not attempt to install. |
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. You should also install the Object Store database system on this computer. See the Cisco Element Manager Framework Installation and Licensing Guide for details on installing Cisco EMF and the Object Store database system.
A CDM deployment allows CDM clients to be installed on workstations that are separate from the CDM server. This 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 back to the CDM server when required to retrieve management information. The CDM applications that generate the GUI run on the CDM client machine, which allows for a more scalable solution.
The CDM client installation process installs the client software on the local machine, which 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 to establish 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 machines as required. |
You can deploy CDM in a number of different configurations, from a single hardware system to a multiworkstation distributed management system, using Sun Solaris/SPARC hardware with Solaris, Release 2.6. Machine specifications are detailed in the following sections.
To manage a small site, consider the computer specifications that are described in the following sections.
The server computer must meet the following minimum requirements:
Cisco recommends that the server computer meets the following requirements:
For a large site, consider the computer specifications that are described in the following sections.
The server computer for a large site must meet the following minimum requirements:
Cisco recommends that the server computer meets the following requirements:
In larger deployments that have client-server configurations, Cisco recommends the following hardware specifications for typical client deployments:
|
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. |
This section includes information and instructions about the hardware requirements for your Cisco DSLAM configuration.
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 hardware is available at the following the web site:
http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/c6100/index.htm
The CDM software communicates with a Cisco DSLAM by transmitting 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:
Switch> enable Switch# config terminal Switch (config)# enable password <ENABLE PASSWORD>
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 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 Switch (config)# snmp-server host <ADDRESS>traps version 2c <Community Name>
|
Note Substitute ADDRESS above with the IP address of the manager server where Cisco EMF is installed. |
Switch (config)# exit
|
Note The read-only and read-write community strings on the NI-2 must match the read-only and read-write community strings that are used when you deploy the NI-2 in CDM. |
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, type telnet <ADDRESS> from the Sun Ultra 60 that is running CDM. |
To set up CDM so that you can backup or restore configuration data, you need to configure your CDM UNIX server to provide Trivial File Transfer Protocol (TFTP) services to Cisco DSLAM chassis as they boot. To do this, you must configure the workstation to support TFTP. To set up TFTP, complete the following steps:
tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s/tftpboot
Step 2 As the root user, execute the following commands:
mkdir /tftpboot
cd /tftpboot
1n -s . tftpboot
Step 3 Copy the Cisco 6100/6130 NI-1 Series images to the /tftpboot directory.
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 EMF user guide, or you can contact the Cisco Technical Assistance Center (TAC) for assistance.
Before you run CDM, you must either uninstall ViewRunner and HP OpenView or disable ViewRunner and HP OpenView from starting.
To disable the programs from starting, follow these steps:
Enter remove /etc/rc2.d/S85vrdb
Enter remove /etc/rc2.d86vr4hpov
Step 2 Disable HP OpenView:
Enter chmod -x /opt/OV/bin/ovstart
To install software onto a system that does not have its own CD-ROM drive, mount the 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 2 Log on to the remote host as superuser and 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 example displays:
root 591 1 0 Feb 26 ? 0 :01 /usr/sbin/vold
Step 3 If the Volume Manager is not running, start the Volume Manager by entering:
/etc/rc2.d/S92volmgt start
Step 4 On the remote host, export the CD-ROM device as follows:
a. Start the NFS-related daemons by entering:
b. Share the mount point from the remote host by entering:
c. Verify that this host has made the CD-ROM drive accessible by entering:
|
Note The listing display should include the /cdrom mount point. |
Step 5 Mount the remote CD-ROM on the local host where the installation is to take place as follows:
a. Create a mount point if none already exists by entering:
b. Mount the remote directory by entering:
c. 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.
To install CDM, complete the following steps.
|
Note Cisco EMF (Release 3.0.4) 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.2, to determine the correct Cisco EMF patch. |
Step 2 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 3 Insert the CDM CD-ROM and change to the CD-ROM directory by entering:
cd /cdrom/cdrom0
Step 4 Run the install script by entering the following command:
./cemfinstall
Two menu options display.
Step 5 Select one of the following installation options:
CDM automatically installs into 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 may require user input, usually 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 6 After the installation is complete, remove the CDM CD.
You are now ready to run CDM.
When you run the cemfdeinstall script, all CDM processes are automatically stopped and uninstalled. Complete the following steps to uninstall CDM:
Step 2 Make sure that Cisco EMF is running (see Step 2 in the "Installing CDM Using cemfinstall" section ).
Step 3 Run the uninstallation script provided on the CD by entering the following command:
host# <CEMF_ROOT>/bin/cemf install -r
Step 4 Choose one of the following uninstallation options:
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.
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 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.
When you stop Cisco EMF, you also stop the CDM software application. Complete the following steps to stop Cisco EMF and CDM:
After you exit from Launchpad, your user session terminates. You do not have to complete the following steps unless you want to entirely stop all Cisco EMF processes.
Step 2 Log in as superuser.
Step 3 Enter the following command:
<CEMF_ROOT>/bin/cemf stop
Step 4 Replace CEMF_ROOT with the directory on which Cisco EMF is installed.
The Cisco EMF and CDM processes stop.
To check the status of Cisco EMF, enter the following command:
<CEMF_ROOT>/bin/cemf query
If Cisco EMF is active, a list of running processes displays. If Cisco EMF is not active, a message that says "Cisco EMF system not running" displays.
|
Note When you run a cemf query, check to be sure the process cdmController is running. If this process is not running, CDM may not have installed correctly, in which case you may need to reinstall CDM. |
Refer to the following publications for related information:
Cisco 6015 Element Manager User Guide
Cisco 6100/6130 NI-2 Element Manager User Guide
Cisco 6160 Element Manager User Guide
Cisco 6260 Element Manager User Guide
Release Notes for the Cisco Digital Subscriber Line Manager NI-2, Release 3.2
Cisco 6100 NI-1 to NI-2 Upgrade Kit Conversion Procedures
The following sections list the CO publications that relate to the Cisco DSL product family.
A complete list of all released Cisco 6100 Series system with NI-1 related documentation is available on the World Wide Web at
http://www.cisco.com/univercd/cc/td/doc/product/dsl_prod/c6100/index.htm.
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly. Therefore, it is probably more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.
Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).
Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.
Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online 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.
CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, 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 CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.
You can access CCO in the following ways:
You can e-mail questions about using CCO to cco-team@cisco.com.
The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.
To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.
To contact by e-mail, use one of the following:
Language | E-mail Address |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate and value your comments.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Access Registrar, AccessPath, Any to Any, Are You Ready, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, the Cisco logo, Cisco Certified Internetwork Expert logo, CiscoLink, the Cisco Management Connection logo, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Capital, the Cisco Systems Capital logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, the Cisco Technologies logo, Fast Step, FireRunner, Follow Me Browsing, FormShare, GigaStack, IGX, Intelligence in the Optical Core, Internet Quotient, IP/VC, IQ Breakthrough, IQ Expertise, IQ FastTrack, IQ Readiness Scorecard, The IQ Logo, Kernel Proxy, MGX, Natural Network Viewer, NetSonar, Network Registrar, the Networkers logo, Packet, PIX, Point and Click Internetworking, Policy Builder, Precept, RateMUX, ReyMaster, ReyView, ScriptShare, Secure Script, Shop with Me, SlideCast, SMARTnet, SVX, The Cell, TrafficDirector, TransPath, VlanDirector, Voice LAN, Wavelength Router, Workgroup Director, and Workgroup Stack are trademarks; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, The Internet Economy, and The New Internet Economy are service marks; and Aironet, ASIST, BPX, Catalyst, Cisco, Cisco IOS, the Cisco IOS logo, Cisco Systems, the Cisco Systems logo, the Cisco Systems Cisco Press logo, CollisionFree, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastLink, FastPAD, FastSwitch, GeoTel, IOS, IP/TV, IPX, LightStream, LightSwitch, MICA, NetRanger, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries. All other trademarks mentioned in this document 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. (0005R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Posted: Tue Sep 5 12:41:14 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.