Table Of Contents

Getting Started With Campus Manager

Logging Into CiscoWorks

Before Using Campus

Starting Campus Manager Applications

Understanding New User Interface

Getting Started With Campus Manager

---

This chapter tells you how to get started with Campus Manager. The sections in this chapter are:

•Logging Into CiscoWorks

•Before Using Campus

•Starting Campus Manager Applications

•Understanding New User Interface

Logging Into CiscoWorks

To access Campus Manager, you need to log in to CiscoWorks. Depending on your CiscoWorks server platform (UNIX, Windows 2000, Windows 2003), different login modules are available.

CiscoWorks Common Services supports two modes of user authentication and authorization:

•ACS mode—Access Control Server (ACS) provides authentication and authorization services in this mode. To use this mode, you must install Cisco Secure ACS on your network.

•Non ACS mode—CiscoWorks Server provides authentication and authorization services in this mode.

CiscoWorks Common Services, set to default, uses CiscoWorks Server authentication (Non ACS), to authenticate users and authorize them to access CiscoWorks Common Services applications.

The CiscoWorks Server authentication scheme has five roles. You cannot change these roles, or the privileges assigned to those roles. The following is the list of privileges, sorted from least privileged to the most privileged:

•Help Desk

•Approver

•Network Operator

•Network Administrator

•System Administrator

You can also use Cisco Secure ACS to provide user authentication and authorization. Cisco Secure ACS allows you to create custom roles and privileges, so that you can customize Common Services client applications.

If you configure Common Services to use non ACS modes for authentication, CiscoWorks Server provides authorization services.

Before Using Campus

You need to ensure that you have a valid license before you start using Campus. Campus Manager uses the Common Services licensing framework for licensing. Licensing is based on the number of devices.

Devices managed by Campus Manager are determined during Data Collection and not during Device Discovery. Therefore, discovery process might discover more devices than indicated by the Campus Manager license.

Devices that have been deleted from DCR continue to be managed by Campus Manager if Campus Data Collection or User Tracking Acquisition are in progress.

The licence is validated while launching different applications of Campus Manager like Topology etc. If the license is expired or not valid, you are prompted to obtain a valid license.

Starting Campus Manager Applications

The Campus Manager Applications are:

Application	Allows you to...
Using Topology Services	Discover, view, and monitor the physical and logical services on your network.
Tracking Users	Locate and display data about users and hosts in the network.
Path Analysis	View the actual path that packets take between end nodes on your network.
Managing VLANs and VTP	Assign VLAN ports, display VLAN ports, or configure trunk ports.
Discrepancy Reporting	View the physical and logical discrepancies discovered on your network.

You can select these applications from:

•Campus Manager > Topology Services

•Campus Manager > Path Analysis

•Campus Manager > User Tracking

•Campus Manager > VLAN Port Assignment

•Campus Manager > Discrepancy Reports, then choose either Physical Discrepancy Report or Logical Discrepancy Report.

If you are prompted to install the Java plug-in, download and install it using the installation screens displayed. The next time you start the application, it automatically uses the plug-in.

For more information on the Java Plug-in, see User Guide for CiscoWorks Common Services.

Understanding New User Interface

The user interface (UI) for User Tracking application and Campus Manager Administration has moved to a light-weight user interface model.

The user interface in Campus Manager 3.x is based on Java applet. The use of heavy applet in the user interface slows the performance of the product.

Campus Manager 4.0 does not depend heavily on applets. The move to a light-weight HTML based UI model has improved product performance.