|
|
Cisco 6400 Service Connection Manager (SCM) software, providing simplified Asynchronous Transfer Mode (ATM) and Layer 2 and 3 IP services to access servers and Digital Subscriber Line Access Multiplexers (DSLAMs) through network and service management of the Cisco 6400 universal access concentrator (UAC) hardware.
The next generation internet access environment combines multiple forms of narrowband and broadband access with common core-services and deployment. Rapid deployment of these complex access networks to serve millions of subscribers is known as Telephony Scale Data Networking (TSDN). The Cisco 6400 SCM is the first of a new generation of products addressing the need for service aggregation in TSDN deployments. The Cisco 6400 SCM provides integrated management capabilities through a simplified, service-oriented user interface.
The Cisco 6400 UAC plays an integral part in the network architecture. It is located within the service provider's infrastructure and acts as a central point of control for Layer 2 and Layer 3 services. These services can include ATM Virtual Channel Connections (VCCs); Point-to-Point Protocol (PPP) tunneling via Layer 2 Tunneling Protocol (L2TP); or PPP termination into local routing and to local or cached content.
The Cisco 6400 SCM Element Manager software adds custom windows and modeling behavior to the standard Cisco Element Management Framework (Cisco EMF) system to allow the management of the Cisco 6400 UAC hardware.
The Cisco 6400 SCM software assists you in making network connections by eliminating the need to have Simple Network Management Protocol (SNMP) and Cisco IOS technical knowledge of the commands required to establish these connections. It also streamlines the deployment process for the Cisco 6400 UAC. The Cisco 6400 SCM provides a service-oriented management view of the Cisco 6400 UACs inbound and outbound connections.
Multiple Element Managers can be installed onto a single Cisco EMF server, thereby allowing multi-device and multi-vendor management from a single system.
This section describes the recommended workflow for installing the Cisco 6400 Service Connection Manager (SCM) application. See Figure 1-1 for further details.
 |
Note Note: Please check Cisco Connection Online (CCO) for details of the latest patch releases for the Cisco 6400 SCM application. Refer to the "Cisco Connection Online" section at the front of this guide for further details. |
The Cisco 6400 SCM can be deployed in a distributed manner, utilizing the power of multiple machines. Two types of installation (server and client) can be performed from the CD-ROM. Figure 1-2 shows a typical deployment.
Every Cisco 6400 SCM deployment must have a Cisco 6400 SCM server installed. The Cisco 6400 SCM server contains all the server processes that keep track of the current state of the network, such as models, user access, and events. The server also includes all client application windows.
A Cisco 6400 SCM deployment can have client installations on separate workstations. These client installations run Cisco 6400 SCM applications that access objects on the server. A client installation contains only those parts of the Cisco 6400 SCM system necessary to run a Cisco 6400 SCM user session. This user session communicates with the Cisco 6400 SCM server when required to retrieve management information. In this case, all window updates are processed locally on the client machine, freeing more resources on the Cisco 6400 SCM server to process network information.
The client install copies the client software onto the local machine; therefore, there is no need to mount files across the network. The only network traffic occurs when the client requires more data from the server.
|
Note A Cisco 6400 SCM server installation also includes all files that run a Cisco 6400 SCM user session on the server system. The Cisco 6400 SCM system can therefore be installed on a single system with server and client functionality, and can be upgraded by adding separate client machines later as required. |
The Cisco 6400 SCM is a Cisco EMF based solution and can be deployed in a number of configurations, from a "single hardware system" solution to a multi-site distributed management system. All Cisco EMF-based solutions run on Sun Solaris/SPARC hardware running the Solaris operating environment, release 2.6.
Use the Cisco 6400 SCM with the following Cisco IOS releases:
Sun Ultra 60 configured as follows:
Sun Enterprise 450 configured as follows:
|
Note If a number of graphically intensive applications are being run on this workstation, it is helpful to use a Sun color card (for example, 24-bit color). A typical server installation requires 300 MB of free disk space in a file system (for example, /opt). An appropriate amount of free disk space for database files is also required. |
The following list of prerequisites must be met before the Cisco 6400 SCM can manage a Cisco 6400 UAC.
Complete these steps through a Console Terminal session to the Node Switch Processor (NSP):
Switch (config)# enable password <ENABLE PASSWORD>
Step 2 If the NSP does not have a configured management ethernet port:
Switch (config)# interface Ethernet 0/0/0
Switch (config-if)# ip address <ADDRESS> <NETMASK>
|
Note Be sure that the 10BaseT Ethernet port on the NSP is connected to the same network as the Cisco 6400 SCM. |
The Ultra 60 running the Cisco 6400 SCM is now able to ping the NSP.
Step 3 If the NSP is not SNMP-manageable:
Switch (config)# snmp-server community <Read Only Community Name> ro
Switch (config)# snmp-server community <Read Write Community Name> rw
Step 4 Check to see if the NSP accepts a Telnet session by entering: telnet <IP ADDRESS OF NSP> from the Ultra 60 running the Cisco 6400 SCM. If the NSP does not accept a Telnet session:
Switch (config-line)# password <TELNET PASSWORD>
Step 5 If WebConsole access is required, refer to CISCO NSP documentation for set up details.
Complete the following steps through a Console Terminal session to each NRP:
If there is currently no privileged command password:
Router (config)# enable password <ENABLE PASSWORD>
Step 6 When the NRP does not have a configured management ethernet port:
Router (config)# interface Ethernet 0/0/0
Router (config-if)# ip address <IP ADDRESS> <NETMASK>
|
Note Make sure that the 10BaseT Ethernet port on the NRP is connected to the same network as the Cisco 6400 SCM. |
The Ultra 60 running the Cisco 6400 SCM is now able to ping the NRP.
Step 7 If the device is not SNMP-manageable:
Router (config)# snmp-server community <Read Only Community Name> ro
Router (config)# snmp-server community <Read Write Community Name> rw
Step 8 If the device is not set up to send SNMPv1 traps to the management station:
Router(config)# snmp-server host <management station ipaddress> version 1 <Read Write Community Name>
Step 9 Check to see if the NRP accepts a Telnet session by entering: telnet <IP ADDRESS OF NRP> from the Ultra 60 running the Cisco 6400 SCM. If the NRP does not accept a Telnet session:
Router (config-line)# password <TELNET PASSWORD>
Traps should be enabled so that the Cisco 6400 UAC sends traps to the SCM server at the appropriate IP address.
To enable traps to be sent to the appropriate Cisco 6400 SCM server, follow these steps:
Step 2 Enter:
enable
Step 3 Enter the enable password (this is the second one in the NSP/NRP Element Manager Configuration window)
Step 4 Enter:
config t
snmp-server enable traps
snmp-server-host <IP address of SCM Server> <read community name of NSP>
|
Note To obtain help when using a Cisco IOS command, type the command, followed by ?. |
The Cisco EMF, upon which the Cisco 6400 SCM is based, requires a license key to operate. Refer to the Cisco Element Management Framework User Guide for details, or contact the Cisco Technical Assistance Center (TAC) for assistance.
To install software onto a system that does not have its own CD-ROM drive, you need to mount the CD on the remote system and then export the device to make it accessible over the network. These operations are done on the remote system where the CD-ROM drive exists. Finally, on the local system where the installation is to take place, you need to mount the remote CD.
Step 2 Log in as superuser on the remote host and see if the volume manager is running. Enter: /usr/bin/ps -ef | grep vold
When the Volume Manager is running, a message similar to this one is returned:
root 591 1 0 Feb 26 ? 0 :01 /usr/sbin/vold
Step 3 If a message similar to the one shown above is not displayed, start the Volume Manager and Enter:
/etc/rc2.d/S92volmgt start
Step 4 Export the CD-ROM device on the remote host:
A) When they are not already running, start the NFS related daemons. Enter:
/usr/lib/nfs/nfsd 8
/usr/lib/nfs/mountd
B) Share the mount point from the remote host. Enter:
share -F nfs -o ro /cdrom/cdrom0
C) Verify that this host has now made the CD-ROM drive accessible. Enter:
share
The listing displayed includes the /cdrom mount point.
Step 5 Mount the remote CD-ROM on the local host (from where the installation is to take place):
A) Create a mount point when none exists already. Enter:
mkdir /mnt/cdfiles
B) Mount the remote directory. Enter:
mount -r <remote-host> : /cdrom/cdrom0 /mnt/cdfiles
The contents of the CD-ROM are visible under the /mnt/cdfiles mount point.
|
Note The following process assumes that you have already installed the Cisco EMF server from the Cisco EMF CD-ROM and that you have a valid license key. Refer to the Cisco Element Management Framework Installation and Licensing Guide for further details. |
To install a Cisco 6400 SCM using cemfinstall:
Step 2 Insert the Cisco 6400 SCM CD-ROM. Change the directory into the CD-ROM area:
cd /cdrom/cdrom0
Step 3 Run the install script:
./cemfinstall
A menu listing the SCM client and SCM server installation options (see Figure 1-3) appears.
|
Note When the required Cisco EMF server/client is not installed, the Cisco 6400 SCM installation option is not available. |
Step 4 Select the installation you require.
The utility performs the appropriate installation.
Step 5 When the installation is complete, exit the CD-ROM area. Enter:
cd /
Then remove the Cisco 6400 SCM CD-ROM. Enter:
eject cdrom
Step 6 Start the Cisco EMF and Cisco 6400 SCM processes. Enter:
<CEMF>/bin/cemf start.
Step 7 Initialize the system: Enter:
<CEMF> cemf dataload
Step 8 Start the application set. Enter:
<CEMF>/bin/cemf session.
The Cisco 6400 SCM is now ready to use.
|
Note When your system includes both the Cisco CDM (Cisco DSLAM Manager for the Cisco 6130 / 6260 DSLAMs) and Cisco 6400 SCM applications (and you have recently de-installed the Cisco CDM application) you must perform the procedure described in the "De-Installing the Cisco 6400 SCM Application (Having Removed the Cisco CDM Application First)" section 1-11, to de-install the Cisco 6400 SCM application. |
All Cisco 6400 SCM processes stop and are de-installed when the cemfinstall script is run with the -r option.
Step 2 Insert the Cisco 6400 SCM CD-ROM.
Step 3 Change the directory into the CD-ROM area. Enter:
cd /cdrom/cdrom0.
Step 4 Run the deinstallation script provided. Enter:
./cemfinstall -r
A menu appears, listing SCM client and SCM server deinstallation options (see Figure 1-4).
|
Note Figure 1-4 indicates that a client SCM is not installed on the system. However, an SCM server is installed on the system and can be de-installed through option S. |
Step 5 Select the de-installation you require.
You are notified that the deinstallation is about to take place. When you proceed with the de-installation, the window scrolls through the software as it is deleted and the following message appears:
Removal of <package> was successful.
The option remove <Cisco 6400 SCM Manager> was completed successfully
When your system includes both Cisco CDM (Cisco DSLAM Manager for the Cisco 6130 / 6260 DSLAMs) and Cisco 6400 SCM applications (and you have recently de-installed the Cisco CDM application), you need to perform the following procedure to de-install the Cisco 6400 SCM application:
Step 2 Change directory. Enter:
cd /var/sadm/pkg
Step 3 Enter the following command. Enter:
Step 4 Enter the following command. Enter:
Configuring a Trivial File Transfer Protocol (TFTP) server enables the configuration backup/restore to operate. This section describes how to configure the TFTP server to run on the SCM server.
Configuring the SCM server as a TFTP server is optional. You can alternatively choose to use a different machine as the TFTP server, or not to use the backup/restore functionality at all. If you decide to use another machine as a TFTP server, make sure that empty backup files exist on the TFTP server. You also need the appropriate permissions set to allow read and write access. The NSP backup files have the filename NSPaa.bb.cc.dd where aa.bb.cc.dd is the IP address of the NSP, and the NRP backup files have the filename NRPaa.bb.cc.dd where aa.bb.cc.dd is the IP address of the NRP. A backup file is created for the active NSP and each active NRP in the Cisco 6400 chassis.
|
Note When the SCM server is set up to be the TFTP server, the SCM ensures that the backup files exist and have the correct permissions. |
TFTP enables you to transfer files to and from remote systems. The configuration backup/restore window in the SCM allows you to backup and restore the configuration of a Cisco 6400 SCM (NSP and NRPs). TFTP transfers the configuration files from a device to your system through the network.
Verify the following information: that the TFTP daemon is enabled; that the TFTP environment variable is set correctly; and that a tftpboot directory exists.
The TFTP daemon must be enabled for the Cisco 6400 SCM to upload or download a configuration file.
If you are using standard Sun software, verify that TFTP daemon (tftpd) is enabled:
Step 2 Edit the /etc/inetd.conf file using a text editor (such as vi).
Step 3 Look in the file /etc/inetd.conf for the line that invokes tftpd. When the line is commented out (starts with a pound sign [#] as in the following example), use a text editor to remove the pound sign.
tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot
Step 4 Save the changes in the edited file and exit.
Step 5 Reboot the system.
Step 6 Now verify that TFTP daemon is enabled. Enter:
hostname# netstat -a | grep tftp
The output should be similar to the following:
*.tftp Idle
|
Note When there is no output, tftpd is not enabled. For additional information on TFTP, refer to the UNIX mon pages on tftp and tftpd. |
The tftpboot directory stores the configuration files from the Cisco 6400 SCM NSP and NRPs.
Step 2 The tftpboot directory must have the appropriate permissions. Modify the permissions. Enter:
hostname# chmod 777 /tftpboot
The Cisco 6400 SCM software is automatically started during system bootup. Otherwise, start the software as follows:
Step 2 Enter:
<CEMF>/bin/cemf start.
The Cisco 6400 SCM processes start.
The Cisco 6400 SCM software is stopped during system shutdown. Otherwise, stop the software as follows:
Step 2 Log in as superuser. Enter:
<CEMF>/bin/cemf stop
The Cisco 6400 SCM processes cease.
You can check the status of Cisco 6400 SCM as follows:
Step 2 The system responds with a list of running processes when the Cisco 6400 SCM is active or with the following message when the SCM is inactive:
Cisco 6400 SCM system not running
 |
Tip Type cemf -h to obtain help information. |
|
Note Client refers to both clients on the SCM server and clients on a remote host. |
Start a client application as follows:
Step 2 You are prompted to enter a username and password. The default user name is admin and the default password is also admin.
Posted: Tue Mar 4 05:17:00 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
