Installing and Starting Cisco IP Manager 2.0

The Cisco IP Manager software meets business requirements for scalable, reliable Layer 3, IOS-based element management in very large networks by:

• Enabling rapid, high-quality service deployment through automated infrastructure provisioning

• Integrating with an existing or new OSS via flow-through interfaces, including the Cisco Provisioning Center, order processing and management, subscriber management and billing, and workforce automation

• Supporting new end-to-end network services

• Allowing partitioning of domain control and permissions to conform to business requirements

• The Administration Server (ADMServer). Provides authorization services and authentication services; controls access to the system and its data for the other servers; manages domains; and manages user information.

• The Configuration Template Manager (CTMServer). Manages templates and template data.

• Event Server. Used by the individual elements of the system to keep track of events occurring throughout the rest of the system.

• GUI application. Provides a user interface for working with the Cisco IP Manager servers

• LOGServer. Maintains records of system activity

• Name Server (NS). Contains Orbix registry of servers and their locations.

• Network Element Manager server (NEMServer). Manages communications between CIPM and network elements. The NEM server calls upon the TG Server or the SG Server as appropriate.

• Oracle database---The data repository.

• The SNMP Gateway Server (SGServer). Uses the SNMP protocol to communicate with the network elements.

• Telnet Gateway Server (TGServer). Uses the Telnet protocol to communicate with the network elements.

• Version Control Manager Server (VCMServer). Archives network element and template configurations, and maintains a history of configuration changes.

Tips MPLS VPN Solution requires that you install all of these components, as well as the GUI package, on the same Cisco IP Manager host.

To install the Cisco IP Manager software, follow these steps:

admintool

Enter the following values:

User Name	ipmgr
User ID	any unique number
Primary Group	Group ID for the Staff group.
Login Shell	C
Password	ipmgr1
Home Directory	/opt/ipmgr

Step 2 Log in as the ipmgr user.

Step 3 Insert the CD-ROM into the CD-ROM drive.

Step 4 Go to the following directory:

cd /cdrom/cdrom0/cipm

Step 5 Install Cisco IP Manager in the /opt/ipmgr directory.

./ipmgr.install ./ /opt/ipmgr all

Step 6 In response to the prompt for the Installation log directory path, enter this command:

/opt/ipmgr

Step 7 In response to the prompt for the Source directory path, accept the default of ./ by pressing Enter.

Step 8 In response to the prompt for the Target directory path, accept the default of /opt/ipmgr by pressing Enter.

Step 9 In response to the prompt for the Packages to install, accept the default of all by pressing Enter.

The installation script begins to install all of the Cisco IP Manager packages.

Once all the packages have been installed, the installation script then offers to configure Cisco IP Manager by running the ipmgr.configure script.

Step 10 To run the ipmgr.configure script now, press Enter.

The ipmgr.configure script begins.

Tips In the event that you need to change the configuration options, you can run the ipmgr.configure script at any time after the installation is completed. As the ipmgr user, enter these commands: cd /opt/ipmgr/scripts source ipmgr.csh ./ipmgr.configure

Step 11 In response to the prompt for the Name Server Host Name, accept the default of the hostname where Cisco IP Manager is being installed by pressing Enter.

Step 12 In response to the prompt for the Event Server Host Name, accept the default of the hostname where Cisco IP Manager is being installed by pressing Enter.

Step 13 In response to the prompt for the Network Domain Name, enter the DNS domain name.

If there is no DNS domain name configured, enter two quotation marks: ""

Step 14 In response to the prompt for the Orbix Daemon Port, accept the default of 1570 by pressing Enter.

Step 15 In response to the prompt for the Starting Port, accept the default of 1590 by pressing Enter.

Step 16 In response to the prompt for the Oracle Home Directory, enter the following:

/opt/oracle/product/8.0.5

Step 17 In response to the prompt for the Oracle SID, enter the following:

CIPM

Step 18 In response to the prompt for the Oracle user ID, enter the following:

ipmgr

Step 19 In response to the prompt for the Oracle user password, enter the following:

ipmgr

Step 20 In response to the prompt for the IP Manager GUI path, accept the default of /opt/ipmgr by pressing Enter.

The installation script asks what type of GUI to install, and provides a list of three options.

Step 21 Enter a value of 2 to accept the ADMIN-GUI option.

This enables all the options in the Cisco IP Manager.

The installation script prompts for the superuser password.

Step 22 Enter the root password.

This concludes the Cisco IP Manager configuration.

Tips By default, MPLS VPN Solution software uses Telnet to upload and download configuration files to and from Provider Edge Routers (PEs) and Customer Edge Routers (CEs) in the service provider network. If you wish to change that setting after CIPM is installed and use the Trivial File Transfer Protocol (TFTP) instead, refer to "Using TFTP to Transport Router Configuration Files" in Chapter 2 of the Cisco VPN Solutions Center: MPLS Solution User Guide.

For detailed information on starting and running this product, refer to "Starting the Cisco IP Manager Software" in Chapter 3 of the Cisco IP Manager (Lite) User's Guide, Version 2.0.

To start the Cisco IP Manager, follow these steps:

source /opt/ipmgr/scripts/impgr.csh

In response to this command, you should see a message similar to the following:

[orbixd: Server "IT_daemon" is now available to the network. ]
[ Configuration TCP/1570/Orbix-XDR ]

Step 2 Register the CIPM servers with the Orbix Implementation Repository by entering the following command:

ipmgr.putit all

In response to this command, you should see many messages similar to the following:

[2427: New Connection 9<hostname>,IT_daemon,*,ipmgr,pid=2411,optimised)]

impgr.launch all

The system displays a lot of information at the startup of each of the IP Manager servers. You should see the following message:

All Cisco IP Manager servers should be running:

The servers that should be running are as follows:

• SGServer

• TGServer

• VCMServer

• NEMServer

• LOGServer

• NS

• ADMServer

• CTMServer

• ES

Following this message is a table that lists the active servers at the specified node. The table includes columns for the server names, marker (*), Code, Comms, Port, Launch, PerClient?, and OS-pid.

Cisco recommends that you source the opt/scripts/ipmgr.csh file and put the command in your .cshrc or .login file.

To launch the Cisco IP Manager graphical user interface (GUI), follow these steps:

./ipmgr.gui

The IP Manager Login window appears.

When you start the Cisco IP Manager for the first time, there is only one user in the system, the CIPM administrator. The default login name for this user is admin; the default password is password. For information on changing these default settings, see "Setting the Cisco IP Manager and Password" in Chapter 2 of the Cisco VPN Solutions Center: MPLS VPN Solutions User Guide.

Step 2 Enter the login name and password, then click OK.

For detailed information on running Cisco IP Manager's graphical user interface, refer to Chapter 2, "Running the GUI," in Cisco IP Manager (Lite) User's Guide, Version 2.0.

If you use a remote TFTP server, the /tftpboot directory must be mounted on the NEMServer host.

#tftp dgram udp wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot

Step 2 Remove the comment character (#) from the beginning of the line. Save your changes and exit the text editor.

If you are not able to do this, you must set up a symbolic link to your TFTP directory. (The user who launches the servers must have write permission to this directory.) If for some reason your network requires you to use something like myTftp, create a symbolic link by entering the following on the command line:

ln -s /myTftp /tftpboot 

Step 4 To verify that your workstation is TFTP-enabled, enter the following on the UNIX command line:

ps -ef | grep -v grep | grep inetd

The output displays the process identification number for the inetd configuration:

root 106 1 0 Sep 21 ? 0:00 /usr/sbin/inetd -s

The first column shows the user ID of the user who owns the process (inetd is owned by root). The process ID is the number in the second column. In the example, the process ID is 106.

Step 5 Issue a kill command with a -1 (the number one) or -HUP argument to force the inetd process to read the newly edited inetd.conf file:

kill -1 106

Step 6 Verify that TFTP is enabled by entering the following:

netstat -a | grep tftp

The Cisco IP Manager workstation is enabled as a TFTP server if you see the following:

*.tftp Idle

If there is no output from the netstat command, TFTP is not enabled. Check the /etc/inetd.conf file for errors and repeat the previous instructions. For more information about TFTP or the kill command, see the UNIX man pages for tftp, tftpd, and kill.

mkdir /tftpboot

Step 2 Modify the permissions for this directory to give all users read, write, and execute permissions, by entering the following command:

chmod 777 /tftpboot

Step 3 If you intend to specify a subdirectory of /tftpboot for your Cisco IP Manager TFTP communications from within the GUI (Domain Properties dialog box), you should create that at this time as well, and set its permissions to the same value.

Step 4 The Cisco IP Manager workstation is now enabled to act as a TFTP server.

Step 2 Issue the following commands:

svrmgrl

At the SVRMGR> prompt, enter these commands:

connect internal
shutdown