Installation and Setup Guide for Campus Manager 4.0 on Windows
Prerequisites
Downloads: This chapterpdf (PDF - 212.0KB) The complete bookPDF (PDF - 1.03MB) | Feedback

Prerequisites

Table Of Contents

Prerequisites

Product Overview

Campus Upgrade Paths

Server Requirements

Maximum Recommended Load

Server Recommendations

Client Requirements

Using Sun Java Plug-in 1.4.2_06

Supported Devices


Prerequisites


This chapter describes the factors that you should consider before installing Campus Manager 4.0 (Campus) on a Windows system.

This chapter contains:

Product Overview

Campus Upgrade Paths

Server Requirements

Client Requirements

Supported Devices

Product Overview

Campus, a member of the CiscoWorks Family of Products, is a suite of web-based network management tools that enable administrators to obtain various types of graphical views of their network topology and end-user information. Campus Manager is based on a client/server architecture that connects multiple web-based clients to a server on the network.

The CiscoWorks Server supplies tools and services to the Campus Manager applications, including the Asynchronous Networks Interface (ANI) Server. The ANI Server discovers information about network devices and saves it in the ANI database for Campus applications to access. For more information, see User Guide for Campus Manager, User Guide for CiscoWorks Common Services, online help for the CiscoWorks Common Services, and online help for the ANI Server.

The Campus Manager applications are:

Path Analysis—View the actual path that packets take between end nodes/devices on your network.

User Tracking—Locate and display data about users, IP Phones, hosts, and wireless clients in your network.

Topology Services—Discover, view, and monitor the physical and logical services on your network. View detailed network information about all devices, links, and ports in your network.

VLAN Port Assignment—View port information, create trunk, configure VLANs on a trunk, and move ports between VLANs on your network.

Discrepancy Reports—Discover and view physical and logical discrepancies in your network.

Campus Upgrade Paths

You can upgrade to Campus Manager 4.0 both from Campus Manager 3.3 and Campus Manager 3.2.

Campus Manager 4.0 requires CiscoWorks Common Services 3.0, which is the foundation for the CiscoWorks family of products. You must upgrade to CiscoWorks Common Services 3.0 before installing or upgrading to Campus Manager 4.0.

When you install CiscoWorks Common Services 3.0, the previous version of Campus Manager database is preserved. When you install Campus Manager 4.0, certain data from the previous database is converted to Campus Manager 4.0 format. This data includes:

Seed devices.

SNMP community strings.

Discovery schedule.

User Tracking manually entered data fields.

User Tracking queries and layouts.

Path preferences.

Job schedule.

Topology groups.


Note Topology groups and job schedules were not part of Campus Manager 3.2.


Server Requirements

This section describes the system requirements and recommendations for CiscoWorks Common Services 3.0 and Campus Manager 4.0.

The minimum system requirements for CiscoWorks Common Services 3.0 and Campus Manager 4.0 are shown in Table 1-1.

Table 1-1 Server System Requirements Summary 

Requirement Type
Minimum Requirement 1

System hardware

IBM PC-compatible computer with 500 MHz Intel Pentium processor.

Color monitor.

CD-ROM drive.

Memory (RAM)

512 MB.

Available drive space2

2 GB.

Virtual memory equal to double the amount of memory (RAM). For example, if your system has 1 GB of RAM, you need 2 GB of virtual memory.

NTFS file system required for secure operation.

At least 16 MB in Windows temporary directory (%TEMP%).

System software

ODBC Driver Manager 3.5.10 or later

Windows 2000 Professional or Server with Service Pack 3 or later, Windows 2003 Server Standard and Enterprise Edition.

Windows Advanced Server without enabling terminal Services.

Campus Manager supports only the US-English and Japanese versions of the Windows Operating System. It does not support any other language version. Set the default locale to US-English for US-English version and Japanese for Japanese version.

Additional software

(Optional)

One of these browsers:

Microsoft Internet Explorer 6.0 (version 6.0.2600.0000), and Internet Explorer 6.0 with Service Pack 1 (version 6.0.2800.1106).

Java Virtual Machine (JVM) 5.0.0.3802 and above, and Java plug-in version 1.4.2_043

To verify the JVM:
From Internet Explorer, select View > Java Console.
From Netscape Navigator, Tools > Server > Java Console.
From Mozilla, Help > About Plug-ins

Netscape 7.1.

Mozilla 1.7.1.

You must install CiscoWorks Common Services 3.0 before installing Campus. If you installed a version of CiscoWorks Common Services earlier than 3.0, upgrade to 3.0 before installing Campus Manager 4.0. See Installation and Setup Guide for CiscoWorks Common Services 3.0 on Windows.

1 If other applications are installed, or the number of devices on your network exceeds 500, the requirements might be greater.

2 Do not install CiscoWorks on a FAT file system.

3 You can install Java Plug-in version 1.4.2_06. See section Using Sun Java Plug-in 1.4.2_06 for more details.


Maximum Recommended Load

The maximum recommended load on servers configured with the minimum server requirements shown in Table 1-1 is 500 Cisco devices and one client at a time.

If other network management applications are installed on your server, additional resources might be required.

Server Recommendations

If your network has more than 500 Cisco devices, the following minimum requirements are recommended:

500 MHz Multiprocessor.

1 GB of memory (RAM).

2 GB of virtual memory.

4 GB drive space.

To select or configure a server system that best meets your needs, consider the number of managed devices. These factors affect server performance and user report response time.

Table 1-2 shows the recommendations for a server running Common Services and Campus. These recommendations produce optimal response time when running user reports.

Client Requirements

The minimum client system requirements for CiscoWorks Common Services 3.0 and Campus Manager 4.0 are shown in Table 1-2. The maximum recommended load on clients configured with the minimum requirements shown is 1000 Cisco devices.


Note Before you can access Campus from a client system, you must configure the system properly.


Table 1-2 Client System Requirements Summary 

Requirement Type
Minimum Requirement

System Software and Hardware

Client system:

IBM PC-compatible computer with 300 MHz Intel Pentium processor running on Windows 2000 with SP3 or later (Professional and Server), Windows XP with SP1 or Windows 2003 .

Solaris SPARC station or Sun Ultra 10 running Solaris 2.7, 2.8 or 2.9.

Color monitor with video card set to 256 colors.

Memory (RAM)

512 MB.

Browser

One of these browsers:

On Windows 2000 and Windows XP clients:

Microsoft Internet Explorer 6.0 (version 6.0.3790.0) in Windows 2003.

Java Virtual Machine (JVM) 5.0.0.3802 and above, and Java plug-in version 1.4.2_04.

To verify the JVM:
From Internet Explorer, select View > Java Console.
From Netscape Navigator, Tools > Server > Java Console.
From Mozilla, Help > About Plug-ins

Netscape 7.1.

Mozilla 1.7.1.

On Solaris clients, use Netscape 7.0 for Solaris 2.8 and
Solaris 2.9


Caution For Solaris, use Netscape downloaded only from the Sun site.

Using Sun Java Plug-in 1.4.2_06

A vulnerability in the Java Plug-in 1.4.2_04 may allow an untrusted applet to escalate privileges, through JavaScript calling into Java code, including reading and writing files with the privileges of the user running the applet. For more details, refer Sun Alert ID: 57591. This is fixed in Java plugin 1.4.2_06.

CiscoWorks neither exploits nor is impacted by this vulnerability. If you choose to use Sun Java Plug-in 1.4.2_06 instead of the one provided in Campus Manager (1.4.2_04), you can choose the plug-in manually.

To modify your CiscoWorks installation to use Sun Java Plug-in 1.4.2_06:


Step 1 On Campus Manager server, locate the Java Plug-in properties file

%NMSROOT%/lib/classpath/javaplugin.properties and change the following entries in the javaplugin.properties file:

WIN_IE_VERSION=clsid:CAFEEFAC-0014-0002-0006-ABCDEFFEDCBA
WIN_NS_VERSION=application/x-java-applet;jpi-version=1.4.2_06
SOL_VERSION=application/x-java-applet;jpi-version=1.4.2_06

Step 2 Save the modified javaplugin.properties file.

Step 3 Update each Windows client as follows:

a. Download Java Plug-in 1.4.2_06 for Windows from the Sun site.

b. Install the Java Plug-in on the client.

c. Close any running browser instances and start them again.

Step 4 Update each Solaris client as follows:

a. Download Java Plug-in 1.4.2_06 for Solaris from the Sun site.

b. Install the Java Plug-in on the client.

c. Locate the jpi.profile and jpi.cshrc files on the client, and change the MOZ_PLUGIN_PATH, to reflect the path to Java Plug-in 1.4.2_06.

For example, if you have installed 1.4.2_04 in /opt/jre14204, and you have installed 1.4.2_06 in /opt/jre14206:

Change

MOZ_PLUGIN_PATH=/opt/jre14204/j2re1.4.2_04/plugin/sparc/ns610

To

MOZ_PLUGIN_PATH=/opt/jre14206/j2re1.4.2_06/plugin/sparc/ns610

Step 5 Update each Solaris client using Netscape 7.0 or Mozilla as follows:

a. Modify the links to point to the links for Java Plug-in 1.4.2_06:

Change

NS7_HOME/plugins/libjavaplugin_oji.so

To

JPI1.4.2_06_HOME/plugin/sparc/ns610/libjavaplugin_oji.so

b. Source /jpi.cshrc or /jpi.profile.

c. Close any running browser instances and start them again.


Supported Devices

For information about supported devices, access the Supported Devices table at the following location: http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_campus_manager/4.0/device_support/table/cm40sdt.html