Table Of Contents
Preparing to Use Campus Manager
Overview of Campus Manager Setup Tasks
Accessing the CiscoWorks Server
Performing Administrator Tasks
Logging In as Administrator
Setting Up Campus Manager Applications
Setting Up Your Network
Configuring Device Discovery
Verifying Device Discovery
Configuring Data Collection
Verifying Data Collection
Setting Up Topology Services
Verifying Topology Services
Setting Up Path Analysis
Verifying Path Analysis
Logging Out as Administrator
Preparing to Use Campus Manager
This chapter describes the various administrator and application setup tasks that you must perform after installing Campus Manager 4.0.6.
This chapter contains:
•
Overview of Campus Manager Setup Tasks
•
Accessing the CiscoWorks Server
•
Performing Administrator Tasks
•
Setting Up Campus Manager Applications
•
Logging Out as Administrator
Overview of Campus Manager Setup Tasks
Table 3-1 provides an overview of Campus Manager 4.0.6 setup tasks and gives references to detailed information about each task.
Accessing the CiscoWorks Server
To access Campus Manager, enter the URL of the CiscoWorks Server in your web browser:
https://server_name:443 (for SSL mode)
where server_name is the name of the CiscoWorks Server and 443 is the port on which it was installed. If you were prompted to supply a different port number for the CiscoWorks Server during the installation, use that port number in the URL.
If you cannot access the CiscoWorks Server or the CiscoWorks Home page is not displayed correctly, see Appendix A, "Troubleshooting the Installation".
After you access the CiscoWorks Server, continue to the "Performing Administrator Tasks" section.
Performing Administrator Tasks
To perform administrator tasks, you must log in as administrator and set up the server for other users.
Logging In as Administrator
To log in as administrator:
Step 1
Enter the system administrator username and password in the Login page.
Step 2
Click Login.
The CiscoWorks Homepage appears.
After you log in as the administrator, continue to the section Setting Up Campus Manager Applications
To log out of the CiscoWorks Server, see the section Logging Out as Administrator for information.
Setting Up Campus Manager Applications
This section describes the tasks that you must perform to set up the
Campus Manager 4.0.6 applications. Some of these tasks require the administrator login.
This section contains:
•
Setting Up Your Network
•
Configuring Device Discovery
•
Setting Up Topology Services
•
Setting Up Path Analysis
Setting Up Your Network
To ensure that the Campus Manager Server successfully discovers the devices in your network, you must set up your network correctly. Table 3-2 lists the required tasks for each application, marked by x.
See the User Guide for Campus Manager 4.0.6 for more information.
Table 3-2 Network Setup Tasks
Network Setup Requirement
|
Topology Services
|
User Tracking
|
Path Analysis
|
VLAN Port Assignment
|
Discrepancy Reports
|
Connect to seed device
|
x
|
x
|
x
|
x
|
x
|
Enable Simple Network Management Protocol (SNMP)
|
x
|
x
|
x
|
x
|
x
|
Enable Cisco Discovery Protocol (CDP)
|
x
|
x
|
x
|
x
|
x
|
Enable Call Detail Record (CDR)
|
-
|
-
|
x
|
-
|
-
|
Set a unique sysName variable on devices
|
x
|
x
|
x
|
x
|
-
|
Enable Integrated Local Management Interface (ILMI) on ATM devices
|
x
|
x
|
x
|
x
|
x
|
Configure DNS
|
x
|
x
|
x
|
x
|
x
|
Configure VLAN Trunk Protocol (VTP)
|
x
|
x
|
x
|
x
|
x
|
Configure VLAN trunks on Fast Ethernet and Gigabit Ethernet
|
x
|
x
|
x
|
x
|
x
|
Create the default configuration server for ATM LAN Emulation (LANE)
|
x
|
x
|
x
|
x
|
x
|
Enable source routing
|
-
|
-
|
x
|
-
|
-
|
After you set up your network, continue to the "Configuring Device Discovery" section.
Configuring Device Discovery
You can modify SNMPv2 and SNMPv3 credentials using the Discovery > SNMP Settings option from the Admin tab in the Campus Manager Administration window.
To configure Device Discovery Settings:
Step 1
Go to the Campus Manager > Administration > Device Discovery > Discovery Settings.
The Device Discovery Settings dialog box appears.
Step 2
Specify the seed device and IP address range.
Step 3
Click Apply to save the changes.
Step 4
Click OK to start Device Discovery.
If you do not specify the IP address range, Device Discovery tries to discover as many devices as it can based on the community strings and connectivity.
For more information, see Specifying Seed Device Online help.
After you set up your network, you must configure data collection. See the "Configuring Data Collection" section.
Verifying Device Discovery
To verify the status of Device Discovery, go to Campus Manager > Administration. In the Campus Manager Administration dashboard that appears, you can view the status of Device Discovery.
Configuring Data Collection
You should have run Device Discovery atleast once before starting Data Collection, or the devices should be available in Device and Credential Repository (DCR).
To configure Data Collection, go to Campus Manager > Administration > Campus Data Collection > Data Collection Filters. The Data Collection Filter Settings dialog box appears.
To Specify VTP Domain
Step 1
Go to the Data Collection Filter Settings dialog box and select VTP Domain and click Configure.
The VTP Domain Filter dialog box appears.
Step 2
Go to the drop-down list and select either of these options:
–
Manage devices in specified VTP domains.
–
Do not manage devices in specified VTP domains.
Step 3
Enter the VTP domains that are to be used to limit data collection and click Apply.
You will be prompted to click OK to start Data Collection or to click Cancel to apply only the settings.
To Specify IP Address Range
Step 1
Go to the Data Collection Filter Settings dialog box and select IP Address Range and click Configure.
The IP Range Filter dialog box appears.
Step 2
Go to the drop-down list and select either of these options:
•
Manage devices in specified IP Address Range
•
Do not manage devices in specified IP Address Range
Step 3
Specify the IP Address Range and click Apply.
A confirmation dialog box appears.
Step 4
Click OK to start Data Collection.
Note
You can apply either the VTP domain or the IP Address Range, but not both.
If you do not specify the IP address range or VTP domain, Campus Manager takes all devices from the Device and Credential Repository. The number of devices for which data can be collected depends upon your licence limit.
Verifying Data Collection
To verify the status of Data Collection, go to Campus Manager > Administration. In the Campus Manager Administration dashboard that appears, you can view the status of Data Collection.
Setting Up Topology Services
To set up Topology Services:
Step 1
Verify that the Campus Manager Server is running.
Step 2
Make sure the Campus Manager Server has managed the devices.
To verify this, go to the Data Collection Metrics page. (Campus Manager > Administration > Campus Data Collection > Data Collection Metrics)
Step 3
Select Campus Manager > Topology Services from CiscoWorks Homepage.
For more information, see the Topology Services Online help.
Verifying Topology Services
To verify that Topology Services is working correctly:
•
Verify that all devices and interfaces are discovered.
Correctly discovered devices and interfaces appear in green in the Topology Services window.
•
Verify that devices displayed in red are SNMP reachable and have correct community strings.
•
Verify that all VLANs and ELANs are discovered and that their port assignments are correct.
The devices are displayed in Topology services only after data collection.
For more information, see the Topology Services Online help.
Setting Up Path Analysis
To set up Path Analysis:
Step 1
Install and configure a DNS server on your network.
A DNS server is required for Campus Manager. For devices with multiple IP addresses, there should be a single DNS entry that includes all IP addresses.
Step 2
Specify correct read community strings on all devices.
Step 3
Specify correct write community strings for multi-layer switching shortcut path determination on Catalyst 5000 devices.
Step 4
Edit the VLAN/ELAN Mapping Table.
This table provides mapping of VLANs and ELANs to subnets.
These mappings are auto-discovered based on information gathered by Topology Services and User Tracking.
In some cases, the information might be incomplete. In these cases, you can edit a VLAN/ELAN mapping table to supplement the Topology Services and User Tracking information. If subnet mappings are not correct, Layer 2 traces on those subnets might fail.
Step 5
Enable Cisco Discovery Protocol (CDP) on all Cisco devices.
If CDP is not enabled, these devices will not appear on Layer 2 path traces.
Step 6
Enable source routing on your network.
This is required if you plan to run path traces outside of the domain known to Topology Services.
For more information, see the Path Analysis Online help.
Verifying Path Analysis
To verify that Path Analysis is working correctly, do the following:
•
Start Topology Services and make sure that all devices, interfaces, and links are managed correctly.
Correctly managed devices appear in green in the Topology Services window.
•
Verify that all VLANs and ELANs are managed with correct port assignments.
•
Start User Tracking and run User Tracking major acquisition with the Ping Sweep option enabled to verify that all end-user stations are managed.
•
Run nslookup on several known devices in the command shell.
•
Verify that DNS lookup works and takes one second or less.
•
Verify the Subnet Mapping table entries.
Each VLAN and ELAN entry should have any corresponding subnets listed. Any subnets that do not correspond to a VLAN or ELAN should be in a Subnet row.
•
Run a few traces between endpoints known to User Tracking or Topology Services and verify that the trace completed successfully.
For troubleshooting information, see the Path Analysis Online help.
Logging Out as Administrator
To end your administrator tasks, you must log out of Campus Manager 4.0.6.
To logout as administrator:
Step 1
Close all secondary browser windows.
You should have only one browser window opened displaying the
Campus Manager interface.
Step 2
Click Logout.
The Login page replaces the navigation tree.