|
|
This guide describes how to install and de-install the Cisco Digital Subscriber Line Manager (CDM) Release 1.1 software.
The Installation Instructions detail how to install and de-install the Cisco DSL Manager (CDM) 1.1. Deployment options are described, and system requirements for different installations are specified. Details about setting up and administering a CDM workstation are included.
The CDM can be deployed in a distributed manner to utilize the power of multiple machines. Two types of deployment, Server, and Server and Client, are available.
Every 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, events etc. The Object Store database system should be installed on this machine.
 |
Note The server includes all client application GUIs. |
A CDM deployment may have the Client installation on separate workstations, which are used to run CDM applications to access objects on the Server. A Client installation contains only those parts of the CDM system necessary for a CDM user session. This user session communicates back to the CDM Server when required to retrieve management information. The CDM graphical user interface (GUI) runs on the CDM client machine, which frees system resources on the CDM server machine to process network information.
The CDM client installation process installs the client software on the local machine, therefore you need not 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 required to establish a client to server session on a single machine. Therefore, you can install the entire CDM system including both server and client, on the same machine. Thereafter, you can install the client on additional machines as required. |
The CDM can be deployed in a number of different configurations, from a single hardware system, to a multi-site distributed management system, using Sun Solaris/SPARC hardware with Solaris, Release 2.6.
Cisco recommends the following machine specifications:
|
Note For large scale deployments, fault tolerant options are available, for example, Sun Netra FT1800. |
Minimum Server
|
Note The additional disk is required for performance improvements of the database, not for additional storage capacity. Although the Sun Ultra 30 workstation is sufficient to run CDM, the Ultra 60 is recommended because it can include an additional CPU and will support future enhancements to CDM. |
In larger deployments with client-server configurations the recommended hardware specifications for typical client deployments are as follows:
Typical Client
|
Note It is useful to have a Sun color card (for example, 24 bit color) if many graphically intensive applications are also run on this workstation. A typical Server installation requires 370MB of free disk space in a file system, for example, /opt. The system also requires an appropriate amount of free disk space for database files. |
For a small deployments (for example, trials), the typical Client and Server can run together on a single workstation. The minimum specification for this scenario is:
To configure an Ethernet port via a terminal Console:
Switch> enable Switch# config terminal Switch (config)# enable password <ENABLE PASSWORD>
Step 2 To configure the Ethernet management port on the NI2 card, proceed as follows:
Switch> enable Password: <ENABLE PASSWORD> Switch# config terminal Switch (config)# interface Ethernet 0/0 Switch (config-if)# ip address <ADDRESS> <NETMASK> Switch (config-if)# exit Switch (config)# exit Switch#
Ensure that the 10BaseT ethernet port on the NI2 is connected to the same network as the CDM Server.
|
Note The Ultra 60 running the CDM should now be able to PING the NI2. |
Step 3 To configure the NI2 card to be SNMP manageable, proceed 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 AccessVision is installed. |
Switch (config)# exit
|
Note The read-only community string can be set to "public" and the read-write community string can be set to "private". |
Step 4 To configure the NI-2 card to accept a telnet session, proceed as follows:
|
Note You can check this after configuring the ethernet port by typing, from the Ultra 60 running the CDM. |
Connection Manager, telnet <IP ADDRESS OF DEVICE NI2> 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#
The CDM uses the AccessVision framework which requires a license key to operate. Information about how to obtain a license key are in the AccessVision User Guide, or you can contact the Cisco TAC Center for assistance.
To install software onto a system that does not have its own CD-ROM drive, mount the CD on the 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 in as Superuser on the remote host and check that the Volume Manager is running:
Type /usr/bin/ps -ef | grep vold
If the Volume Manager is running, a message similar to the one shown below will be returned:
root 591 1 0 Feb 26 ? 0 :01 /usr/sbin/vold
If the Volume Manager is not running, start the Volume Manager as follows:
Type /etc/rc2.d/S92volmgt start
Step 3 On the remote host export the CD-ROM device as follows:
Start the NFS related daemons:
Type /usr/lib/nfs/nfsd 8
Type /usr/lib/nfs/mountd
Share the mount point from the remote host:
Type share -F nfs -o ro /cdrom/cdrom0
To verify that this host has made the CD-ROM drive accessible:
Type share
|
Note The listing displayed should include the /cdrom mount point. |
Step 4 Mount the remote CD-ROM on the local host where the installation is to take place:
Create a mount point if none exists already:
Type mkdir /mnt/AVmnt
Mount the remote directory:
Type mount <remote-host> : /cdrom/cdrom0 /mnt/AVmnt
|
Note <remote-host> should be replaced by the host name of the remote device. |
The contents of the CD should now be listed under the /mnt/AVmnt mount point.
|
Note AccessVision (version 2.1.x or later) must already be installed before attempting to install the CDM software. |
To install the CDM, proceed as follows:
Step 2 Insert the CDM CD-ROM. Change directory into the CD-ROM area:
Type cd /cdrom/cdrom0
Step 3 Run the install script ./avinstall
|
Note The CDM software will be installed automatically into the <AVROOT> directory. |
Step 4 If the Manager System has multiple network interfaces, you will be prompted to select the appropriate interface.
Step 5 The utility will now perform the appropriate installation. As each part of the installation takes place, various informational messages will be displayed as an output to the screen. Some will require user input. A simple yes/no answer will usually be required.
Step 6 Once the installation is complete, remove the CDM CD.
Step 7 If an AccessVision Manager was installed, to perform a dataload type <AVROOT>/bin/av start
<AVROOT>/bin/av dataload
to initialize the system.
|
Note AccessVision dataload must be run (once only) after AccessVision is started for the first time. |
Step 8 The CDM is now ready to use.
All CDM processes will be automatically stopped and de-installed when the <avdeinstall> script is run.
Step 2 Log in as Superuser.
Step 3 Run the deinstallation script provided on the CD:
Type ./avinstall -r
You will be notified that the deinstallation is about to take place.
If you proceed with the de-installation the screen will scroll through the software being deleted and you will see the following message:
Removal of <package> was successful.
The CDM software is automatically started during system boot-up. To start this software at other times:
Step 2 Type <AVROOT>/bin/av start
Step 3 The CDM processes will start.
The CDM software is stopped during system shut down. To stop this software at any other time:
Step 2 Login a superuser.
Step 3 Type <AVROOT>/bin/av stop
Step 4 The CDM processes will stop.
To check the status of the CDM:
To start a client application (that is, the user GUI screens):
|
Note Clients refers to both clients on the CDM server and clients on a different host from the server. |
CDM prompts you to enter a user name and a password. The default user name is admin and the default password is admin.
Posted: Wed Feb 16 14:20:58 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.