cc/td/doc/product/rtrmgmt/carm/rel_1_0
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Installing and Uninstalling
System Requirements
Installation Workflow
Supported Objects
Server and Client Installation
Installing or Upgrading from a Remote CD-ROM Drive
Installing or Upgrading Using the Install Script
Uninstalling

Installing and Uninstalling


Installing and uninstalling procedures are described in the following sections:

System Requirements

The EM can be deployed in a number of different configurations, from a single hardware system to a multisite distributed management system.

All Cisco EMF-based solutions run on Sun Solaris/SPARC hardware running the Solaris operating environment, release 8.

Use the Cisco Access Router Manager only with Cisco Access Router routers using a supported Cisco IOS Release. For a list of the supported Cisco IOS releases, see the accompanying release notes. Other IOS versions may be used; however, some functionality may not be compatible with other IOS software.

Cisco Access Router Manager servers and clients operate with the following software:

System requirements are described in the following sections:

License Requirements

The EM uses Cisco EMF, which requires a license key to operate.


Note   For information about how to obtain a license key, see the Cisco Element Management Framework v3.2 User Guide, or contact Cisco Technical Assistance Center (TAC) for assistance.

Server Requirements

The recommended minimum hardware requirements for servers are:

If a number of graphically intensive applications are run on a workstation, it is helpful to use a 24-bit Sun color card. A typical manager installation requires 500 MB of free disk space in a file system. An appropriate amount of free disk space for database files is also required.

Client Requirements

The recommended minimum hardware requirements for clients are Sun Microsystems SunBlade 100, Ultra 10 or similar with the following:

If a number of graphically intensive applications are run on a workstation, it is helpful to use a 24-bit Sun color card. A typical manager installation requires 500 MB of free disk space in a file system.

Installation Workflow

Installing the EM involves the following:

1. System requirements—Confirm the proper preinstallation procedures by reviewing the "System Requirements" section.

2. Cisco EMF—Verify that you have the following required Cisco EMF 3.2 server/client software installed before proceeding:

    a. Cisco EMF 3.2

    b. Cisco EMF 3.2 patch 5


Note    For information on installing Cisco EMF and related patches, see the Cisco Element Management Framework Installation and Administration and the relevant Cisco Element Management Framework Release Notes.

3. Installation—Install the Cisco Access Router Manager software according to the instructions in one of the following sections:

"Installing or Upgrading from a Remote CDROM Drive" section

"Installing or Upgrading Using the Install Script" section

4. EM Setup—

    a. Perform configuration tasks on the Cisco Access routers. For details, see the "Configuration" section.

    b. Set trap notifications. For details, see the "Enabling Traps" section.

    c. Enable Configuration Backup/Restore. For details, see the "Setting Up a Workstation as a TFTP Server" section.

5. EM Session—To begin working with the EM, see the "Starting a User Session" section.

Supported Objects

The following are categories of physical objects supported by the Cisco Access Router Manager software:

The following table displays a list of routers supported by Cisco Access Router Manager.

 

Table 2-1   Supported Routers

Cisco Router Description

Cisco 2610
Cisco 2610-DC
Cisco 2610-RPS

2610 with AC power supply
2610 with DC power supply
2610 with redundant power supply (RPS) adapter plate installed

Cisco 2611
Cisco 2611-DC
Cisco 2611-RPS

2611 with AC power supply
2611 with DC power supply
2611 with RPS adapter plate installed

Cisco 2612
Cisco 2612-DC
Cisco 2612-RPS

2612 with AC power supply
2612 with DC power supply
2612 with RPS adapter plate installed

Cisco 2613
Cisco 2613-DC
Cisco 2613-RPS

2613 with AC power supply
2613 with DC power supply
2613 with RPS adapter plate installed

Cisco 2620
Cisco 2620-DC
Cisco 2620-RPS

2620 with AC power supply, includes IP software only
2620 with DC power supply, includes IP software only
2620 with RPS adapter plate installed, includes IP software only

Cisco 2621
Cisco 2621-DC
Cisco 2621-RPS

2621 with AC power supply, includes IP software only
2621 with DC power supply, includes IP software only
2621 with RPS adapter plate installed, includes IP software only

Cisco 2650
Cisco 2650-DC
Cisco 2650-RPS

2650 with AC power supply, includes IP software only
2650 with DC power supply, includes IP software only
2650 with RPS adapter plate installed, includes IP software only

Cisco 2651
Cisco 2651-DC
Cisco 2651-RPS

2651 with AC power supply, includes IP software only
2651 with DC power supply, includes IP software only
2651 with RPS adapter plate installed, includes IP software only

Cisco 3620
Cisco 3620-DC
Cisco 3620-RPS

3620 with AC power supply
3620 with DC power supply
3620 with RPS adapter plate installed

Cisco 3640
Cisco 3640-DC
Cisco 3640-RPS

3640 with AC power supply
3640 with DC power supply
3640 with RPS adapter plate installed

Cisco 3661-AC
Cisco 3661-DC

10/100 Ethernet Cisco 3660 6-slot CO Modular Router-AC
10/100 Ethernet Cisco 3660 6-slot CO Modular Router-DC

Cisco 3662-AC
Cisco 3662-DC
Cisco 3662-AC-CO
Cisco 3662-DC-CO

Dual 10/100 Ethernet Cisco 3660 6-slot CO Modular Router-AC
Dual 10/100 Ethernet Cisco 3660 6-slot CO Modular Router-DC
Dual 10/100 Ethernet Cisco 3660 6-slot CO Modular Router-AC
Dual 10/100 Ethernet Cisco 3660 6-slot CO Modular Router-DC

The following tables displays the generic, ATM, and ethernet module supported by Cisco Access Router Manager.

Table 2-2   Supported Generic Modules

Module Description

NM-2V

2 Voice/Fax interface card

NM-HDV-2T1-48

2 Port 48 channel T1 Voice/Fax interface card

NM-HDV-2E1-60

2 Port 60 channel E1 Voice/Fax interface card

VIC-2EM

2 Port E&M Voice/Fax interface card

VIC-2FX0

2 Port Foreign Exchange Office (FXO) Voice/Fax interface card

VIC-2FXS

2 Port Foreign Exchange Station (FXS) Voice/Fax interface card

VWIC-2MFT-E1D1

2 Port RJ-48 Multiflex Truck-E1 with drop and insert card

VWIC-2MFT-T1D1

2 Port RJ-48 Multiflex Truck-T1 with drop and insert card

WIC-2T

2 Port High-Speed Serial WAN interface card

Table 2-3   Supported ATM Modules

Module Description

NM-1A-OC3MM

1 Port 155-Mbps multimode OC-3 ATM card

NM-4T1-IMA

4 Port T1 ATM with Inverse Multiplexing over ATM (IMA) card

Table 2-4   Supported Ethernet Modules

Module Description

NM-1FE-TX

1 10/100 Fast Ethernet card

NM-2FE2W

2 10/100 Ethernet 2 WAN card

Server and Client Installation

The EM can be deployed in a distributed manner to utilize the power of multiple machines. Two types of deployment are available: server and client. Server and client installations, however, cannot run on the same workstation. You can install either a server or a client on one machine, but not both.

Note that the EM installation type, server or client, must match that of the installed Cisco EMF software.


Note   For information regarding Cisco EMF server and client deployment, see the Cisco Element Management Framework Installation and Administration Guide.

Server and client installations are described in the following sections:

Server Installation

Every EM deployment must have a server installed. Processes on the server keep track of the current state of the network model, user access, and events.

Client Installation

EM deployment allows for client installations on separate workstations. The client installations run EM applications that access objects on the server. A client installation contains only those parts of the EM software necessary to run a user session. The user session communicates with the server when required to retrieve management information. When management information is retrieved, all window updates are processed locally on the client machine, freeing resources on the manager to process network information.

The client installation copies the client software onto the local machine; therefore, there is no need to mount files across the network. Network traffic occurs only when the client requires more data from the server.

The server installation includes all files that run a user session on the server system. The EM can therefore be installed on a single system with server and client functionality, and can be upgraded by adding separate client machines later as necessary.

Installing or Upgrading from a Remote CD-ROM Drive

To install the EM software on a system that does not have its own CD-ROM drive, proceed as follows:


Tip EM installation is significantly faster when Cisco EMF is not initialized. Before beginning the installation process, you can choose to determine if Cisco EMF is initialized. For additional information, see the "Checking the Status of the EM" section. If Cisco EMF is initialized, you can choose to exit the application accordingly. For further information, see the "Stopping a User Session" section.


Step 1   Insert the EM CD-ROM into the CD-ROM drive of the remote host.

Step 2   Log in as a root user on the remote host.

Step 3   Verify if the Volume Manager is running by entering the following:

/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

Or, if the Volume Manager is not running, start the Volume Manager by entering the following:

/etc/rc2.d/S92volmgt start

Step 4   Export the CD-ROM device to the remote host:

    a. If the NFS-related daemons are not already running, start them by entering the following:

/usr/lib/nfs/nfsd 8
/usr/lib/nfs/mountd

    b. Share the mount point from the remote host by entering the following:

share -F nfs -o ro /cdrom/cdrom0

    c. Verify that the remote host has made the CD-ROM drive accessible by entering the following:

share

The listing which displays includes the /cdrom mount point.

Step 5   Mount the remote CD-ROM on the local host (where the EM will be installed):

    a. Create a mount point if none exists already by entering the following:

mkdir /mnt/cdfiles

    b. Mount the remote directory, by entering the following:

mount -r remote-host:/cdrom/cdrom0 /mnt/cdfiles

Replace remote-host with the host name of the remote device.

The contents of the CD-ROM should now be visible under the /mnt/cdfiles mount point. To continue the installation, proceed to Step 3 in the following section.



Installing or Upgrading Using the Install Script

After you install Cisco EMF (and the required patches) and acquire a valid license, you can install Cisco Access Router Manager using the appropriate install script.


Note   For details on installing Cisco EMF, see the Cisco Element Management Framework Installation and Administration Guide.

The install script can be used for first-time installations as well as upgrades to previously installed versions. Before loading the software, the Cisco Access Router Manager install script checks the system for existing packages. If an existing package is found, the script compares the existing version to the version on the CD. If the version on the CD is more recent, the previously installed version is upgraded. If the version on the CD is older than the installed version, no system change occurs. If an existing package is not found, the version on the CD is installed.


Tip EM installation is significantly faster when Cisco EMF is not initialized. Before beginning the installation process, you can choose to determine if Cisco EMF is initialized. For additional information, see the "Checking the Status of the EM" section. If Cisco EMF is initialized, you can choose to exit the application accordingly. For further information, see the "Stopping a User Session" section.


Step 1   Log in as a root user.

Step 2   Perform one of the following, as appropriate:

    a. Insert the Cisco Access Router Manager CD-ROM and make the CD-ROM area your working directory by entering the following:

cd /cdrom/cdrom0

    b. Navigate to the directory where the EM package exists by entering the following:

cd CEMF_Root/bin

(Replace CEMF_ROOT with the name of the directory where Cisco EMF is installed.)

Step 3   Run the install script by entering the following:

./CAccessRouterMGRinstall

The installation script automatically detects what type of Cisco EMF installation exists (server or client) and whether Cisco EMF is initiated or not.

If Cisco EMF is not initialized, the terminal window lists the compatible installation options:

Because the EM installation must match that of Cisco EMF, if the Cisco EMF server is installed, then the EM client install will be incompatible and vice versa. The script hides the incompatible options on the terminal window. Furthermore, the script detects whether Cisco EMF is currently running and hides the invalid option.

The following depicts an example of a terminal window which would display when the Cisco EMF server package exists on a workstation and Cisco EMF is not initialized.

INSTALL PACKAGE:
1) Cisco Access Router Manager Server and its required COM Components—(No CEMF Initialization Required)
q) Quit
Which package do you wish to install? (Def:1) [?,q]

Tip Enter ? for help or q to quit.

Step 4   Choose the appropriate installation option.

The utility determines the package upgrade and install list. For first time EM installations, all COM components and the selected EM component (e.g., C2636MGRm for server installation or C2636MGRc for client installation) must be installed. If an earlier version of the EM exists on the workstation, only those packages that are out of date or missing will install. A listing of the redundant packages that will not install displays. Next, the installation option selected displays followed by a prompt used to specify the interface polling rate if installing a server.

The interface polling rate is the interval in which the installed software performs heartbeat polling on managed interface objects. The default interface polling rate is listed as the COM version and is necessary when Cisco Access Router Manager is installed with other coresident EMs. The default interface polling rate occurs at the 5-minute interval.

Should you want to improve system performance, you can choose to install the EM customized interface polling rate. This is the recommended option for non-coresident systems. The EM customized interface polling rate modifies the default interface heartbeat polling rate from a 5-minute interval to a 15-minute interval. Furthermore, the revised rate is extended for interface objects in the errored or lostcommspoll states. Interface objects in these two states are polled at a 30-minute interval under the customized rate.

The interface polling options presented are as follows.

Please choose from the following:
1) Use COM version interface polling rate for co-residency purpose.
2) Use EM customized interface polling rate for better performance.
Which option do you wish to choose? [1 2]:

Step 5   Enter the appropriate polling rate option at the prompt (1 or 2).

A confirmation prompt for the selected installation parameters appears as follows:

Do you want to proceed with the installation [yes]?

Step 6   Enter the appropriate confirmation at the prompt (yes or no).

The entry of no cancels the installation procedure and returns you to the previous installation terminal window, while yes proceeds with the installation of all components listed.

You cannot select individual components for installation.

As installation of each package takes place, the following displays:

Installation of <package name> was successful.

At the completion of the installation, the following displays:

The option install "installation option" was completed successfully.

The interface polling rate configuration option selected in Step 5 is verified and listed with installation results.

Step 7   When the installation is complete, exit the CD-ROM area as necessary by entering the following:

cd /

You can start a user session, if needed, and begin using the installed package. For additional information, see the "Starting a User Session" section.



Uninstalling

You can uninstall the EMs using the provided scripts. Use any of the three options listed here to remove the software:

You need not uninstall the EM to install a later version. For additional information, see the "Installing or Upgrading Using the Install Script" section.

To prepare to remove an EM, log in as a root user on the machine where the EM is installed.


Tip The EM can be uninstalled whether Cisco EMF is initialized (i.e., running) or not. You can choose to determine if Cisco EMF is initialized prior to beginning the uninstall process. For additional information, see the "Checking the Status of the EM" section. If Cisco EMF is initialized, you can choose to stop the application. For further information, see the "Stopping a User Session" section.

Removing Packages Using the cemf install Script

You can use the cemf install script to list all the EM packages installed, and remove selected packages. The cemf install script removes the shared components and the EM package (e.g., Cisco Access Router Manager and all required COM components).

Some options cannot be removed. For example, Cisco EMF cannot be removed until the EM is removed. Dependent software (for example, Cisco Access Router Manager) must be removed before the primary software (in this case, Cisco EMF) can be removed.


Note   To remove packages using the cemf install script, see the Cisco Element Management Framework Installation and Administration guide.

Removing EM Packages Using the Install Script

You can selectively remove an EM package (e.g., Cisco Access Router Manager server or Cisco Access Router Manager client) using the appropriate install script with the -r command. The -r command allows you to leave the shared components on the system and only remove the EM package (i.e., the associated COMs are not removed).

If the Cisco Access Router Manager was installed with the customized interface polling rate and you plan to reinstall the EM for coresident purposes, you must uninstall the EM and all associated COMs using the -r -all command. For further information, see the "Removing EM Packages and COM Components Using the Install Script" section.

If the Cisco Access Router Manager was installed with the customized interface polling rate and you plan to reinstall the EM with the customized rate at a future time, the following procedure is applicable.

To remove EM packages using the install script:


Step 1   Ensure that you are logged in as a root user on the workstation where the EM package you want to remove is installed.

Step 2   At a command prompt, enter:

cd CEMF_Root/bin

(Replace CEMF_ROOT with the name of the directory where Cisco EMF is installed.)

Step 3   After navigating to the Cisco EMF root directory, enter the following:

./CAccessRouterMGRinstall -r

A list of all the packages installed appears in a terminal window. The options presented in the terminal window includes Cisco EMF (Server or Client), Cisco EMF patches, and each EM (Server or Client) installed (e.g., Cisco Access Router Manager). Typically EM packages do not require Cisco EMF initialization, and such information appears beside the relevant option.

If an installed package contains dependencies to other installed packages, the following appears beside the affected option(s):

[cannot be removed]

The following figure is an example of a terminal window which would display during an uninstall when the Cisco EMF server package, Cisco EMF patches, and the Cisco Access Router Manager server package are installed on a workstation.

REMOVE PACKAGE:
1) Cisco Element Manager Framework — Server [cannot be removed]
2) Cisco Access Router Manager Server and its required COM Components — (CEMF Initialization Required)
3) CEMF Server 3.2 Patch 170005-5
q) Quit
Which package do you wish to remove? (Def:1) [?,q]

Tip Enter ? for help or q to quit.

Step 4   To uninstall a package, enter the appropriate option at the prompt.

The utility verifies the option selected and a confirmation of the uninstall appears.

If the option entered in the previous step is invalid, the script notifies you of the error, lists the valid option(s), and redisplays the selection prompt. Enter a valid selection and continue.

Step 5   Enter the appropriate confirmation at the prompt (y or n).

The entry of n indicates no and cancels the uninstall procedure and returns you to the previous uninstall terminal window, while an entry of y, indicating yes, proceeds with the uninstall of the selected package.

As the uninstall takes place, the following displays for each package:

Removal of "<package name>" was successful.

At the completion of the installation, the following displays:

The option remove of "uninstall option" was completed successfully.

The EM package is uninstalled (e.g., Cisco Access Router Manager). The associated COM components, however, remain installed.



Removing EM Packages and COM Components Using the Install Script

You can selectively remove an EM package and all associated COM components using the install script with the -r -all command. The -r -all command does not allow you to leave shared components on the system (i.e., the EM package and all associated COMs are removed).

To remove an EM including the associated COM components using the install script:


Step 1   Ensure that you are logged in as a root user on the workstation where the EM and COM package you want to remove are installed.

Step 2   At a command prompt, enter:

cd CEMF_Root/bin

(Replace CEMF_ROOT with the name of the directory where Cisco EMF is installed.)

Step 3   After navigating to the Cisco EMF root directory, enter the following:

./CAccessRouterMGRinstall -r -all

A list of all the packages installed appears in a terminal window. The options presented in the terminal window includes Cisco EMF (Server or Client), Cisco EMF patches, and each EM (Server or Client) installed (e.g., Cisco Access Router Manager). Typically EM packages do not required Cisco EMF initialization, and such information appears beside the relevant option.

If an installed package contains dependencies to other installed packages, the following appears beside the affected option(s):

[cannot be removed]

The following figure is an example of the terminal window displayed during an uninstall when the Cisco EMF server package, Cisco EMF patches, and the Cisco Access Router Manager server package are installed on a workstation.

REMOVE PACKAGE:
1) Cisco Element Manager Framework — Server [cannot be removed]
2) Cisco Access Router Manager Server and its required COM Components — (CEMF Initialization Required)
3) CEMF Server 3.2 Patch 170005-5
q) Quit
Which package do you wish to remove? (Def:1) [?,q]

Tip Enter ? for help or q to quit.

Step 4   To uninstall a package, enter the appropriate option at the prompt.

The utility verifies the option selected and lists the packages to be uninstalled, including the EM (C2636MGRm for server package or C2636MGRc for client package) and COMs. A confirmation of the uninstall appears.

If the option entered in the previous step is invalid, the script notifies you of the error, lists the valid option(s), and redisplays the selection prompt. Enter a valid selection and continue.

Step 5   Enter the appropriate confirmation at the prompt (y or n).

The entry of n indicates no and cancels the uninstall procedure and returns you to the previous uninstall terminal window, while an entry of y, indicating yes, proceeds with the uninstall of the selected package.

As each package is unistalled, the following displays:

Removal of "<package name>" was successful.

At the completion of the uninstall, the following displays:

The option remove of "uninstall option" was completed successfully.

The EM package and each of its associated COM components are uninstalled.




hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Feb 12 08:51:37 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.