-
User Guide for Campus Manager 5.1 (With LMS 3.1)
-
Notices
-
Preface
-
Chapter 1 About Campus Manager
-
Chapter 2 Whats New in Campus Manager 5.1
-
Chapter 3 Getting Started With Campus Manager
-
Chapter 4 Integrating Campus Manager With CiscoWorks
-
Chapter 5 Administering Campus Manager
-
Chapter 6 Generating Reports
-
Chapter 7 Tracking Users
-
Chapter 8 Discrepancies and Best Practices Deviations
-
Chapter 9 Using Topology Services
-
Chapter 10 Managing VLANs
-
Chapter 11 Managing Network Spanning Trees
-
Chapter 12 Support for IPv6
-
Chapter 13 Data Extraction Engine
-
Index
-
Table Of Contents
What's New in Campus Manager 5.1
What's New in Campus Manager 5.1
New Features in This Release
The following are the new features and enhancements available in Campus Manager 5.1:
•
Integration with IPM, HUM and DFM for Topology Maps
•
•
•
Note
Auto Allocation of Devices
Devices can be added to Campus Manager in two modes:
•
•
In Auto Management mode, Campus Manager 5.1 allows you to manage devices in groups
There are two types of groups available:
•
System-defined groups are automatically created, based on the information in DCR.
•
You can create User-defined groups based on your requirements.
For example, if you want to manage only devices with IP address in the range 10.77.*.* in Campus Manager, create a group for those devices in Common Services and add it to Campus Manager in the Auto mode settings page. These devices will be managed in Campus Manager after you run Data Collection.
For details, see Device Management.
MAC Detection and Reporting
Campus Manager 5.1 detects New MACs, Rogue MACs and Dormant MACs that are in the network.
•
MAC Addresses that are inactive for the specified number of days.
•
MAC Addresses that are newly added to your network.
•
MAC Addresses that are not authorized to exist in your network.
This feature allows you to:
•
•
•
Integration with IPM, HUM and DFM for Topology Maps
From Topology Maps and N-Hop view Portlets, you can:
•
•
•
•
•
•
You can launch the application pages, if DFM, HUM, and IPM are installed on a local server or on a remote server with a Master-Slave setup.
For details see, Starting CiscoWorks Applications From Topology Views.
Enhanced Discrepancy and Best Practices Deviation Report
You can fix the following Best Practises Deviation through Campus Manager 5.1:
•
•
•
•
For details, see Interpreting Best Practices Deviations.
The following discrepancies are removed from Campus Manager 5.1:
•
•
•
•
•
Enhanced Topology in ACS Environment
Topology Maps normally display all the devices discovered by Campus Manager. When Campus Manager is integrated with the ACS server, you can set Topology Maps to display only the devices you are authorized to view.
For details, see Restricted Topology View.
User Tracking Summary Portlet
The User Tracking Summary Portlet displays the following data:
•
You can click the number link to launch the End Hosts Immediate Reports page.
•
End Hosts that are currently connected to the network are called Active End hosts. You can click the number link to launch the Active End Hosts Immediate Report page.
•
Displays the number of hosts that are inactive for 12 days. The number of days depends on the days configured in the Configuration screen.
•
Displays the number of new hosts in the last 12 days. The number of days depends on the days configured in the Configuration screen.
•
Displays the number of rogue hosts in the last 21 days. The number of days depends on the days configured in the Configuration screen.
For more details, see the User Guide for LMS Portal 1.1.
VSS Support
The Virtual Switching technology is the process of combining two standalone distribution switches in the local distribution layer, into a single management point. The Virtual Switching System (VSS) functions and appears as a single switch to the wiring closet and the core layer.
See the User Guide for Resource Manager Essentials 4.2, for more details on:
•
•
•
Note
If the following devices are available in DCR, Campus Manager manages VSS as follows:
•
–
–
•
–
–
Campus Manager manages these devices as normal Catalyst 6000 devices.
You can configure the above devices as VSS through RME, with Device A as the Master and Device B as the Slave. After this configuration, RME adds another device in DCR with the following credentials:
•
•
•
Now DCR contains three devices instead of two:
•
•
•
When Data Collection runs, the following occurs:
•
•
•
With this VSS device, you can perform all Campus Manager operations that are applicable for normal Catalyst 6000 devices.
VSS re-configuration is not supported in RME. You have to manually reconfigure the devices to remove VSS. In that case, all the above mentioned three devices will be present in DCR. You must delete the VSS device from DCR before running Data Collection. Otherwise the results will be unpredictable.
