-
User Guide for Campus Manager 4.0
-
Preface
-
About Campus Manager
-
Campus Manager 4.0 Changes and Enhancements
-
Getting Started With Campus Manager
-
Administering Campus Manager
-
CiscoWorks Common Services Integration
-
User Tracking
-
Discrepancy Reporting
-
Topology Services
-
VLAN and VTP Management
-
Managing Network Spanning Trees
-
Support for Internet Protocol v6
-
ATM Management
-
Path Analysis Using Campus Manager
-
Data Extraction Engine
-
Index
-
Feedback
Table Of Contents
Understanding Topology Services
Using Topology Services Legend
Understanding Topology Services Main Window
Using Topology Services Main Window
Understanding Network Topology Views
Navigating in Network Topology Views
Connecting Securely to Devices From Clients
Using Panner to View Topology Maps
Customizing Network Topology Views
Saving Network Topology View Layouts
Deleting Devices From Network View
Changing Network Topology View Layouts
Modifying Network View Features
Changing Network Topology View Properties for One User Role
Changing Network Topology View Properties for All Users
Setting Background Images for Topology Views
Using Find in Network Topology Views
Highlighting Devices From Summary View
Interpreting Summary Information
Interpreting Network View Summary Information
Interpreting Unconnected Device View Summary Information
Upgrading Network Topology Views
Using Microsoft Visio With Topology Views
Downloading the Cisco Visio Stencil File
Exporting Network Topology Views to Visio
Displaying Aggregate Link Attributes
Interpreting Aggregate Link Attributes
Time Domain Reflectometry Reports
Understanding Time Domain Reflectometry
Using Time Domain Reflectometry Reports
Running TDR Test From Campus Manager
Performing Data Collection for Devices
Interpreting Device Attributes
Setting Preferred Management Addresses
Working With Application Servers
Displaying Device Service Modules
Interpreting Service Attributes
Monitoring Protocol Filter by Port
Understanding Protocol Filtering
Displaying Protocol Filter Information
Viewing ANI Data Collection Metrics
Interpreting Topology Groups Summary Information
Getting Started With Topology Groups
Overview of Subnet Based Groups
Understanding Hierarchical Maps
Topology Services Menu Reference
Topology Services Main Window Menu Reference
Network Topology View Menu Reference
Inter-Switch Link (ISL) Protocol
Troubleshooting Topology Services
Troubleshooting Time Domain Reflectometry Reports
Using Topology Services
Topology Services is an application that enables you to view, monitor, and configure the physical and logical services in your network.
•
Understanding Topology Services
•
•
•
•
•
•
•
•
•
•
•
•
Understanding Topology Services
You can use Topology Services to:
•
•
•
•
•
•
•
•
This topic contains:
Starting Topology Services
Start Campus Manager > Topology Services from the CiscoWorks Homepage.
You must install the Java Plug-in to access Topology Services from a client. 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.
Step 1
Step 2
For information about the ANI Server, see "About ANI Server" section.
Using Topology Services Legend
The Topology Services Legend explains the use of icons and colors in network views. You can refer the Legend to identify devices in your network and their status. The Legend includes all manageable devices, including devices that might be present in your network.
Color indicators described in the Legend enable you to quickly determine the status of your network. To display the Legend:
Step 1
The Topology Services main window appears.
Step 2
The Campus Manager Color and Icon Legend window opens. For details, see Table 8-1.
Step 3
Table 8-1 Color and Icon Legend
ATM Switch
ATM-VLAN
Ethernet VLAN
Ethernet ATM-VLAN
ATM-Domain
Filter On
FDDI Ring
LE Client
LE Config Server
LE/Broadcast Server
Link Port
Network Topology View (Topology Map)
Switch Port
Router
Serial Bus
Switch
Switch Cloud
Token Ring CRF
Token Ring BRF
Token Ring ATM-VLAN
Unknown VLAN
WAN Switch
Embedded Router
Embedded Switch
Embedded SBC
End Station
Integrated Communications System
Layer 2 and Layer 3 Switch Router
Application Server
Hub
Switch Probe
Voice Gateway
Access Point
Optical Services Router
Cisco ONS Series Device
Content Engine
Content Server Switch
DSL Switch
Switch Stack
Storage Switch
Add Row
ANI Server Unknown
ANI Server Idle or Running
ATM Switch Cloud
Backup LECs
Backup LE Bus
Broadband Router
Cisco CallManager
Command Switch
Device
Navigate Down
Fabric
Fabric Cloud
Link in Forwarding State
Link in Blocking State
Isolated VLAN
Community VLAN
Two-way Community VLAN
Closed Folder
Domain Folder
Fabric Folder
Open Folder
Layer Map
Route Switch Module (RSM) Switch
Display All Rows
Begin
Stop Tree
Open Saved Path Trace File
Unknown Device
Zoom to Fit
Major Fault (red)1
OK (green)
Minor Fault (yellow)
Testing (magenta)
Unknown (blue)
Active (black)
Inactive (red)
Not in network (red dashes)
Unknown (blue)
1 Device is not reachable using SNMP or the device is down.
Table 8-2 lists the special scenarios for Layer 2/Layer 3 Switch Routers.
For example, the switch is running Catalyst operating system and the router is an RSM or MSFC module, and if either the switch or the router is unreachable the topology map displays the icon as:
Understanding Topology Services Main Window
You can access the LAN Edge, Layer 2, and Unconnected Devices network views of managed domains discovered in your network, and you can filter, access, or view network information or status. For more information, see Table 8-3.
Table 8-3 Topology Services Main Window Components
Menu
Contains Topology Services commands.
See Topology Services Main Window Menu Reference for more information.
Toolbar
Provides quick access to frequently used menu options.
To show or hide the toolbar, select View > Show Toolbar.
Tree View
Access the LAN Edge, Layer 2, and Unconnected Devices network views of managed domains.
•
•
Summary View
Displays configuration information about the items displayed in the Tree View.
Click and drag column headings to change the order in which they appear.
Status Bar
Displays Topology Services system messages on the left and the Status button on the right.
Click the color-coded Discovery Status button to open Discovery Information window.
In this window you can view Data Collection and User Tracking discovery status.
Understanding Tree View
The Tree View displays the discovered network objects in a hierarchical list. This list includes managed domains and available network views.
Using Topology Services Main Window
You can use Topology Services Main Window for displaying the discovered tVTP domains, VLANs, and ATM domains. Access the LAN Edge, Layer 2, and Unconnected Devices.The topic contains:
Navigating in Main Window
You can display VTP domains, VLANs, ATM domains, and ATM-VLANs from the main window. You can also access the LAN Edge, Layer 2, and Unconnected Devices network views of managed domains discovered in your network, and you can filter, access, or view network information or status.
Figure 8-1 displays the Topology Services Main Window.
Figure 8-1 Topology Services Main Window
Table 8-5 describes different parts in the Topology Services Main Window.
Table 8-5 Using Main Window
Menu
Contains Topology Services commands.
See "Topology Services Main Window Menu Reference" section for more information.
Toolbar
Provides quick access to frequently used menu options.
To show or hide the toolbar, select View > Show Toolbar.
Tree View
Displays discovered VTP domains, VLANs, and ATM domains. Access the LAN Edge, Layer 2, and Unconnected Devices network views of managed domains.
Right-click items that you want to display, and select View > Display View to display network views.
Single-click items to display summary information in the Summary View.
Summary View
Displays configuration information about the items displayed in the Tree View.
Click and drag column headings to change the order in which they appear.
Status Bar
Displays Topology Services system messages on the left and the Status button on the right.
Click the color-coded Status button to view the ANI Information window, which provides you Data Collection and User Tracking acquisition status.
Click the ANI Status to display the ANI Information dialog box.
This dialog box displays your Data Collection and User Tracking Acquisition status, and the time at which the most recent Data Collection and User Tracking discoveries were completed.
Understanding Status Bar
The status bar displays information about the current status of the Topology Services application, and includes a button that you can click to view current network Data Collection and User Tracking Acquisition statistics.
Figure 8-2 describes sections of the status bar.
Figure 8-2 Status Bar
Table 8-6 describes different parts of a Status Bar.
For more information about the ANI Server, see ANI Server Admin Online Help.
Using Find in Main Window
You can use Find to locate specific items in your network. Your search is restricted to either the Tree View or Summary View. You cannot search both views simultaneously in Topology Services. Select the view based on the item you want to locate.
To use Find option in the Main Window:
Step 1
Enter the required information as described in the Main Window Find Field Descriptions table.
Step 2
Tip
Understanding Network Topology Views
A Network View is a graphical representation of the devices in your network. You can use Network Views to see different aspects of your network. Only devices and links discovered in your network are displayed.
While you use Topology Services, the listed devices and links change dynamically to display what the ANI Server discovers in your network.
Network Views provide various abstract views of your network. Table 8-3 describes the Network Topology window components.
You can use Network Views to see different aspects of your network. Only devices and links discovered in your network are displayed in topology maps.
As you use Network Topology Views, listed devices and links change dynamically to display devices and links that ANI Data Collection performs in your network.
Table 8-8 provides a list of functions that you can perform in Network Topology Views.
Navigating in Network Topology Views
You can use Network Topology Views to see different aspects of your network. Only devices and links discovered in your network are displayed in network views.
As you use network views, devices and links change dynamically to display changes that the ANI Server discovers in your network.
Table 8-9 Network Topology View Features
Menu
Contains Topology Services commands.
See Network Topology View Menu Reference for more information.
Toolbar
Provides quick access to frequently used menu options.
To show or hide the toolbar, select View > Show Toolbar.
Topology Filters
Allows you to filter and display devices and links.
Filter device types, LANE components, link types, discrepancies in your network, and ATM components.
Status Bar
Displays Topology Services system messages on the left and the Discovery Status button on the right.
Click the color-coded Status to view the ANI Information.
This window provides you Data Collection and User Tracking acquisition status.
Figure 8-3 Network Topology View
Connecting Securely to Devices From Clients
You can connect securely to a device using SSH. To connect to a device from a client, Microsoft Windows clients must perform the SSH executable configuration. Solaris clients must use the default SSH client provided by the operating system.
To connect to the devices securely:
•
For Microsoft Windows Clients
You must provide the location to an SSH client executable in the Java Runtime Parameter field.
To Specify the SSH Client
Step 1
The Java Plug-in Control Panel appears.
Step 2
Step 3
For example, if the ssh executable is located at E:\PROGRA~1\SSHCOM~1\SSHSEC~1\ssh2.exe,
add the following in the the Java Runtime Parameter field:-DCMSSH=E:\PROGRA~1\SSHCOM~1\SSHSEC~1\ssh2.exe(Directory and file names must follow the 8.3 naming format.)
Step 4
To Connect to the Device
Step 1
Step 2
Or
From a Summary View, right-click a device entry, and select SSH from the popup menu.
The SSH dialog box opens.
Step 3
Step 4
An SSH terminal window opens.
For Solaris Clients
Step 1
Or
From a summary view, right-click a device entry, and select SSH from the popup menu.
The SSH dialog box opens.
Step 2
Step 3
An SSH terminal window opens.
Displaying Network Views
A Network Topology View is a graphical representation of the devices in your network. To access and display several network and domain views:
Step 1
A popup menu appears.
Step 2
The Network Topology window opens, displaying the specified network or domain view. See Table 8-9 for more information.
Using Panner to View Topology Maps
Figure 8-4 Panning the Topology Map
Using Network Views
You can select a network view from the Tree View to display different segments of your network in a Network Topology window. See Table 8-10 for more information.
Table 8-10 Network View Item Descriptions
LAN Edge View
Shows network connectivity between Layer 3 devices that have routing characteristics. Devices without Layer 3 connectivity are placed in ATM Domain or Switch Cloud network views.
View:
•
•
•
•
•
•
•
Switch Cloud View
Displays the Layer 2 devices between two Layer 3 devices in your network.
View:
•
•
•
•
•
•
•
•
•
•
•
•
Layer 2 View
Displays the Layer 2 information about your network, including ATM and LAN switches, routers, MLS devices, hubs, and switch probes.
View:
•
•
•
•
•
•
•
•
•
•
•
•
Unconnected Devices View
Displays devices for which connectivity information could not be obtained, including devices not supported by Topology Services.
This can include non-Cisco ATM devices discovered through Integrated Local Management Interface (ILMI), since it is an industry standard.
View:
•
•
•
•
•
•
•
VTP Views
Shows the devices that are participating in VTP domains. VTP Views also shows the non-VTP devices and ATM domains connected directly to the VTP domain.
View:
•
•
•
•
•
•
•
•
•
•
•
Customizing Network Topology Views
You can modify the Network Topology Views to change the location of device icons or links, save Network Topology Views, and remove devices from the Network Topology View.
Saving Network Topology View Layouts
You can customize Network Topology Views by rearranging and dragging devices and links to different locations on the view. This allows multiple users to customize the way the Network Topology Views appear.
To do this:
Step 1
Step 2
Deleting Devices From Network View
To delete devices from any Network Topology View.
Step 1
Step 2
This step only removes the device from the ANI Server database. If the device still exists in your network and is discoverable by the ANI Server, it reappears during the next Data Collection.
If devices that you do not want displayed in Topology Services continue to reappear on the Network Topology View, modify the discovery settings on the Device Discovery.
Changing Network Topology View Layouts
To change the layout for each Network Topology View.
Step 1
Step 2
Modifying Network View Features
You can modify and customize various Network Topology View features to suit your operating environment. For example, you can change the display colors and view layout of the Network Topology View.
You can also customize the view features for individual user roles, or modify the default features for all users.
Changing Network Topology View Properties for One User Role
You can change client map properties for one user role without affecting the Network Topology View properties for other user roles.
To do this:
Step 1
The Client Map Properties window opens.
Step 2
Step 3
Changing Network Topology View Properties for All Users
To change the Network Topology View properties for all users:
Step 1
Step 2
The Client Default Properties window opens.
Step 3
To trim Sysname based on Domain suffix, enable Trim Domain Suffix On Labels, specify Domain Suffix value and ensure that Truncate Sysname On Labels is not enabled.
Step 4
Setting Background Images for Topology Views
You can set an image as the background of the Network Topology Views in Topology Services. Campus Manager allows you to upload images and set the image, where the image is in GIF, JPEG, or JPG image formats.
To set the background image, you must do the following:
Step 1
Step 2
Uploading the Image
To upload and set the background image:
Step 1
Step 2
The Network Topology window appears.
Step 3
The Client Map Properties window appears.
Step 4
Step 5
Selecting the Image
After you finish uploading the image, you can select and set the background for each network view.
To select an image for the background:
Step 1
The Client Map Properties window appears.
•
•
Step 2
Step 3
Deleting the Image
To delete the image from the list of images that you have uploaded.
Step 1
The Client Map Properties window appears.
Step 2
Step 3
Using Topology Filters
You can filter devices, links, and networking services, and locate these items on the Network Topology Views. Many different filters are available, but the availability of specific filters varies among each of the different Network Topology Views.
You can use multiple filters at the same time to display more than one media type.
To filter devices:
Step 1
The Topology Services Main Window appears.
Step 2
The Network Topology View appears.
Step 3
Table 8-14 describes various filters.
Step 4
•
This requires that all criteria be met to highlight devices on the Network Topology View. Therefore, only those devices supporting active links of the selected type are displayed.
•
This requires that any criteria be met in order to highlight the selection on the Network Topology View. However, for discrepancy filters, selecting multiple options from the same top level filter will assume an AND operation.
•
However, you must complete the Displaying Service Attributes procedure to determine whether the specified Service (or any other Service) is currently active on the application server.
Step 5
To deselect items and check boxes that you have selected and return to the normal view, select Edit > Clear Highlighting.
Highlighting Filtered Devices
You can highlight the devices that you have filtered using the Topology filters.
Step 1
Step 2
Or
Right-click the topology map and select Highlight Filtered from the popup menu.
The topology map highlights the devices that are being filtered.
Step 3
Using Find in Network Topology Views
You can locate specific devices in your network by searching for the device name or device address. You can do this by using the Find option.
Step 1
Step 2
Step 3
In LAN Edge view, if you try to locate a device present within a switch cloud or within an ATM fabric, though you will not be able to locate the device, the corresponding switch cloud or ATM fabric will be highlighted.
Understanding Summary View
You can use the Summary View to monitor the current configuration of your network and easily find devices in your network.
The Summary View allows you to obtain summary information about the managed domains, logical components, and physical topology of your network. See Interpreting Summary Information for details on summary information.
Note
This topic contains:
•
•
•
•
Highlighting Devices From Summary View
You can select a device and choose to highlight the device in the Network View from the Summary View in the Topology Services Main Window.
Step 1
The Topology Services Main Window appears.
Step 2
Step 3
The Topology Map appears with the highlighted device.
Interpreting Summary Information
You can find help for interpreting summary information in Topology Services through these topics:
•
•
•
•
•
Interpreting Network View Summary Information
To display summary information about items in the network views, click a Network View from the Tree View in Topology Services.
See Table 8-16 to interpret this information.
Interpreting Unconnected Device View Summary Information
To display summary information about items in the unconnected device views, click Unconnected Devices View from the Tree View in Topology Services.
See Table 8-17 to interpret the fields in the Unconnected Devices View Summary.
Upgrading Network Topology Views
After an upgrade installation or manual data import from Campus Manager 3.2 or Campus Manager 3.3, you may upgrade the Layer 2 View, LAN Edge View, or Unconnected Devices View that was saved in Campus Manager 3.2 or 3.3 to the new Campus Manager 4.0 format.
If this upgrade is not performed, you can directly use the default views, with enhanced features, generated by Campus Manager 4.0.
You can perform the following upgrade procedure more than once. To do this:
Step 1
The Upgrade Topology Views window appears.
Step 2
Step 3
Step 4
Step 5
Using Microsoft Visio With Topology Views
You can export the network clouds, aggregate links, device nodes, links, buses, and all associated labels into a text file that can be converted into a Visio drawing. Refer to a Visio manual on how to create drawings from external data.
Note
To export network views to Microsoft Visio
•
This file stores images of Cisco devices that Visio uses to create the drawing. For more details, see "Downloading the Cisco Visio Stencil File" section.
•
For more details, see "Exporting Network Topology Views to Visio" section.
Downloading the Cisco Visio Stencil File
You must download the Cisco stencil file if you want to export Network Topology Views to Visio. See Exporting Network Topology Views to Visio for more details. To do this:
Step 1
Step 2
The directory path is usually Visio\Solutions
Caution
Step 3
Exporting Network Topology Views to Visio
You must download the Cisco stencil file (cm_cisco.vss). This file stores images of Cisco devices that Visio uses to create the drawing. See Downloading the Cisco Visio Stencil File for more details. To do this:
Step 1
Step 2
The Export window appears.
Step 3
Step 4
Step 5
When you open the saved text file in Visio, select the comma as the delimiter to use.
Working With Links
You can use Network Topology Views to display information about links between discovered devices and the type of link connecting the devices.
•
Interpreting Link Tooltips
Link tooltips provide detailed information about links. They appear as popup windows as you move the cursor over different items in the discovered network.
Some network types display additional information in the tooltips. For example, Token Ring devices, links, and buses also include the Token Ring Concentrator Relay Function (trCRF) ring number in hexadecimal digits.
Use Table 8-18 to help you interpret the tooltips that appear.
Displaying Link Attributes
You can display information about the links between devices in your network.
From a Network Topology View, right-click a link and select Link Attributes from the popup menu, or select Reports > Link Attributes.
The Link Attributes window opens. See Interpreting Link Attributes for more information.
Interpreting Link Attributes
See Table 8-19 to interpret the fields shown in the Link Attributes window.
Displaying Aggregate Link Attributes
The aggregation of multiple physical Ethernet links into a single, virtual link allows network managers to speed the flow of traffic through their networks, reaching speeds that would not be possible otherwise.
For example, if you have no access to links any faster than 100 Mbps, you might aggregate four separate channels of 100 Mbps each into a single 400 Mbps channel.
If there are any aggregate links between devices in your network, you can use Topology Services to display information about those aggregate links.
To display information about the aggregate links:
•
Or
•
The Aggregate Link Attributes window opens. See Interpreting Aggregate Link Attributes for more information.
Interpreting Aggregate Link Attributes
See Table 8-20 to interpret the fields shown in the Aggregate Link Attributes window.
Time Domain Reflectometry Reports
Time Domain Reflectometry (TDR) is used to detect faults in a cable. TDR checks and locates open circuits, short circuits, sharp bends, crimps, kinks, impedance mismatches, and other such defects.
Time Domain Reflectometry is required when the application cannot establish a link, or if the link does not perform as expected.
This usually occurs if you:
•
•
•
In such cases, the nature of the defect in the cables are important. To detect the defects, you can perform TDR test on the link. TDR test checks the various aspects of the performance of physical links and its reliability, and reports status and failure.
This topic contains:
•
•
Understanding Time Domain Reflectometry
Time Domain Reflectometry detects the defects by sending a signal through a cable, and reflecting it from the end of the cable. Open circuits, short circuits, sharp bends and other defects in the cable, reflects the signal back, at different amplitudes, depending on the severity of the defect.
The TDR measures the time taken by the signal to reflect back and thus calculates the distance to the defect in the cable. When the signal reaches the end of the cable, it reflects at a very low amplitude.
Thus, Time Domain Reflectometry can also measure:
•
•
Using Time Domain Reflectometry Reports
Campus Manager supports TDR Cable Diagnostic Test and generates a report listing the results of the test on Cisco Catalyst 6000 switches.
See Running TDR Test From Campus Manager for more details.
Running TDR Test From Campus Manager
To run the TDR test for a link:
Step 1
Step 2
This view in the Tree View in the Topology Services Main Window.
Step 3
The Network Topology window for the View appears.
Step 4
Step 5
Step 6
A message appears:
Running TDR Report may affect data traffic in the link. Do you like to run the TDR Test.
Step 7
The TDR Report window appears. See Table 8-21 for details on the report.
After you generate the TDR Report you can:
•
•
To run TDR Test for a port:
Step 1
Step 2
Step 3
Step 4
The Port Attributes for the device window appears.
Step 5
Step 6
A message appears:
Running TDR Report may affect data traffic in the link. Do you like to run the TDR Test.
Step 7
The TDR report window appears.
See Table 8-22, for more details on the TDR report.
To view the links that have support for TDR:
Step 1
Step 2
This view in the Tree View in the Topology Services Main Window.
Step 3
The Network Topology window for the View appears.
The Topology Filters panel has a filter TDR.
Step 4
Step 5
The links, which are supported are highlighted.
Working With Devices
You can use a Network Topology View to display information about the routers and switches in your network. This section contains:
•
•
•
•
Performing Data Collection for Devices
You can perform data collection for each device or a group of devices from Topology Services.
Step 1
Step 2
Step 3
Or
From the topology map, select the device.
Select Edit > Perform Data Collection, or right-click the device and select Perform Data Collection from the popup menu.
The status bar displays the message:
Request data collection for n device(s) accepted by ANI.The discovery status button on the status bar shows the status as Running.
Once the data collection is complete, the status bar displays a message:
Data Collection done, and the discovery status on the status bar shows the status as Idle.
Interpreting Device Tooltips
A tooltip is a text message that clarifies the purpose or meaning of a user interface element such as a button, a line, or an icon.
Generally, tooltips appear whenever your pointer rests on any user interface element for which a tooltip has been defined. Tooltip messages are displayed against a colored background (typically yellow or lavender) in a rectangle that hovers above the user interface element being described.
Tooltips in Topology Services provide detailed information about devices and links in Network Topology Views.
Some device types display additional information in the tooltips. For example, Token Ring devices, links, and buses also include the Token Ring Concentrator Relay Function (trCRF) ring number in hexadecimal digits.
Tooltip for a device, for example, 172.18.2.11(C3900), contains the device name or the IP address, and the device type in parentheses.
Displaying Device Labels
To display device information labels in Network Topology Views.
Step 1
Step 2
Interpreting Device Labels
The device labels are then displayed. See Table 8-23.
Table 8-23 Device Labels
IP Address
The IP address of the device
Device Name
The name of the device
SysName
The SysName of the device
Clearing Device Labels
To clear device information labels in the Network Topology Views.
From a Network Topology View, select View > Display Labels > Clear Labels. The device labels are then hidden from display.
Displaying Device Attributes
To display information about a specific device.
•
Or
•
The Device Attributes window opens. See Interpreting Device Attributes for more information.
Interpreting Device Attributes
See Table 8-24 to interpret the fields shown in the Device Attributes window.
Displaying Port Attributes
To display information about the status of the ports in your network.
•
Or
•
The Port Attributes window opens. See Interpreting Port Attributes for more information.
Interpreting Port Attributes
See Table 8-25 to interpret the fields shown in the Port Attributes window.
Select View > Unused Ports from the menu to view the list of unused ports. Deselect View > Unused Ports to view the complete list of ports. You can also save or print the lists.
Setting Preferred Management Addresses
Some devices, such as routers, can have multiple IP addresses. You can set a preferred management address to be used by Campus Manager using either of the following procedures.
Note
To navigate from Topology Services Main Window:
Step 1
This view is in the Tree View in Topology Services main window.
Step 2
Step 3
The Select Management IP Address window containing the multiple IP addresses of the selected device appears.
Step 4
Step 5
Step 6
To navigate from Topology View:
Step 1
Step 2
A topology map appears.
Step 3
Step 4
The Select Management IP Address window containing the multiple IP addresses of the selected device appears.
Step 5
Step 6
Step 7
Starting CiscoView
You can display specific device configuration and diagnostic information by starting CiscoView.
CiscoView is a graphical user interface (GUI) based device management software application that provides dynamic status, statistics, and comprehensive configuration information for Cisco internetworking devices.
CiscoView allows you to configure and monitor the port level information.
To start CiscoView:
Step 1
The VLAN Port Assignment window appears.
Step 2
Step 3
Step 4
Step 5
CiscoView starts if it has been configured with information about the selected device.
Starting Telnet
You can initiate a remote terminal connection with the Cisco Systems Console on a device that supports Telnet and that appears in the VTP Domain table.
To do this:
Step 1
The Topology Services Main Window appears.
Step 2
Step 3
Or
Start Campus Manager > VLAN Port Assignment from the CiscoWorks Homepage.
The VLAN Port Assignment window appears.
Select the VTP domain and enter appropriate search criteria, if necessary. For more information, see Querying Ports in Specified VTP Domains.
Select the row that contains the device from the VTP Domain table. For more information, see VTP Domain Table.
Right-click the selected device and select Telnet from the popup menu.
A Telnet session window opens.
Starting Device Center
Device Center provides the summary of details for a device. The application launches troubleshooting tools, management tasks, and reports for the selected device. As the application is based on a device-centric navigation paradigm, Device Center helps you to focus on device centric features and information from one location.
After launching Device Center, you can change device attributes, update inventory, and initiate telnet with a device that is selected from the Device Center Window. For more details on Device Center, see Using Device Center under User Guide for CiscoWorks Common Services 3.0.
To launch Device Center from Topology Services.
Step 1
The Topology Services Main Window appears.
Step 2
Or,
From a Network Topology View, right-click a device icon, and select Device Center from the popup menu.
Device Center launches for that device.
To launch Device Center from VLAN Port Assignment.
Step 1
The VLAN Port Assignment window appears.
Step 2
The VTP Domain table lists the ports, which are in that VTP domain.
Step 3
Device Center launches for that device.
Working With MLS Devices
If you are using Multilayer Switching (MLS) in your network, Campus Manager displays MLS switches and routers in the network view.
MLS provides high-performance Layer 3 switching for Cisco routers and switches. MLS switches IP data packets between subnets while using standard routing protocols for route determination.
MLS also provides traffic statistics as part of its switching function. These statistics are used for identifying traffic characteristics for administration, planning, and troubleshooting.
Displaying MLS Reports
You can obtain information about devices in your network that are participating in multilayer switching.
Step 1
Step 2
Or,
You can select Reports > Multi-Layer Switching > Switch Engines to display the relationship between Layer 3 switching and forwarding devices in your network.
Interpreting MLS Reports
You can use MLS reports to display the relationships among multilayer switching (MLS) devices in your network.
The Route Processors Report displays information about the routers in your network that support multilayer switching, and their relationship with the MLS switches.
The Switching Engines Report displays information about the switches in your network that support Layer 3 switching (MLS), and their relationship with the MLS routers. This report also provides information about how the flow is Layer 3 switched.
Interpreting the Route Processors Report
See Table 8-26 to interpret information shown in the Route Processors report.
Interpreting Switching Engines Report
See Table 8-27 to interpret information displayed in the Switching Engines report.
Note About Unified Icon
Network Topology View of the Campus displays a single icon for Cisco Catalyst 6000 with MSFC and Cisco Catalyst 5000 with RSM devices. The unified icon is Layer 2 and Layer 3 Switch Router icon.
In previous versions of Campus, the these devices were represented using different icons.
Working With Application Servers
Application servers are high-availability workflow systems that provide categories of service on a network, such as Cisco AVVID (Architecture for Voice, Video and Integrated Data) services.
For example, a Media Convergence Server (MCS) is an application server providing such AVVID-related applications as Cisco CallManager.
Cisco CallManager provides signaling and call control services to Cisco integrated multimedia applications as well as third-party applications. Cisco CallManager services can be distributed and clustered over an IP network, thereby allowing scale to 10,000 users and triple call processing redundancy.
The ANI Server component of CiscoWorks manages application servers, and Topology Services displays them in the Layer 2 view.
You can access application servers and start Cisco CallManager from Topology Services.
Topology Services cannot distinguish a Windows server (NT and 2000) from an application server running Cisco CallManager.
Topology Services will always display a Windows server or a Media Convergence Server as an application server.
To start an application server:
Step 1
•
or
•
The Service Attributes window opens.
Step 2
The application server starts. See the documentation included with the application server for more information.
Displaying Device Service Modules
To view the details on service modules for the devices:
Step 1
Step 2
Step 3
The Service Modules window appears.
See Table 8-28 to interpret the fields shown in the Service Modules window.
Table 8-28 Service Modules Field Descriptions
Device Name
Name of the device.
Module IP Address
IP Address of the module on the device.
Device Type
Cisco product name for the device, such as C6506.
Module Type
Type of module.
Module ID
Module identification, such as slot number.
Module Status
Current operational status, that is whether the module is active or inactive.
Launch
If IP Address is available, and Status is Ok, this button allows you to start the administration screen of the service.1
1 In case of a switch with a VPN card, the launch point is enabled with the IP address of the switch.
Select File > Print from the menu to print Service Modules information.
Select File > Export from the menu to save the details to a text file.
Displaying Service Attributes
Services are server processes on the application servers in your network. Examples might include Cisco CallManager, Cisco Application Engine, and Cisco Trivial File Transfer Protocol (TFTP) Server.
You can use Topology Services to display information about the available services in your network. To do is:
Step 1
Step 2
The Network Topology Window opens.
Step 3
Device icons in the network topology map become dimmed, except for those devices configured to run the specified service. The icons that are not dimmed in the map are highlighted.
Step 4
The Software Service Attributes window appears.
Interpreting Service Attributes
See Table 8-29 to interpret the fields shown in the Software Service Attributes window.
Displaying Campus Reports
Campus Manager 4.0 allows you to generate Campus reports for switch clouds and VTP Domains.
You can view any of the three reports on: port attributes, device attributes, or VLAN reports, for VTP domain or the switch cloud from the Campus reports window.
You can also view the reports on port attributes, device attributes, or VLAN reports separately.
•
•
•
To see these reports:
Step 1
Step 2
Step 3
The Campus Manager Report(s) window appears.
Step 4
Step 5
•
•
•
Step 6
Step 7
You can remove the VTP domain or the switch cloud from the list of Selected Aggregate Entities. Click Remove to remove each from the list or click Remove All to remove all entries from the list.
Step 8
The report window for the report you selected, appears.
Monitoring Protocol Filter by Port
You can monitor protocol filtering by each port on devices that support this feature and have NetFlow Feature Cards installed.
This section contains:
•
•
Understanding Protocol Filtering
On Cisco Catalyst 5000 series switches with NetFlow Feature Cards installed, you can filter broadcast traffic by protocol on a port-by-port basis.
You can display relevant ports on these switches and their protocol filtering status. This can help you troubleshoot end-user host connectivity problems based on mismatched protocols.
Displaying Protocol Filter Information
You can display protocol filter information for each port on switches with NetFlow Feature Cards.
Protocol filtering is supported on Ethernet VLANs only, and the ports must be non-trunking; trunking ports are members of all protocol groups. Verify that the port for which you want to display filter information is a non-trunking port.
To display protocol filter information:
Step 1
Step 2
Step 3
A mismatch between these fields suggests connectivity problems.
Viewing ANI Data Collection Metrics
To view a tabular report, containing statistics for the last n Data Collection cycles.
From the main Topology window, select Reports > Data Collection Report. The Data Collection Metrics window opens. See Table 8-30 for information displayed in the Data Collection Metrics window.
Topology Groups
The Topology Groups feature in Campus allows you to create customized views, of the network, in which devices are grouped according to various criteria. A view may be considered as a group of devices or device elements.
You can define the criteria (called a rule) which will determine the settings of your custom view. The rule will determine the group of devices to be displayed in the view.
These groups are subsets of Layer 2 maps, the members being defined by a set of rule expressions. In a network with a large number of devices, a Topology Group helps you to perform operations in a subset of the large network.
You can use Topology Groups Administration to manage the Topology Groups in your system.
The following topics provide you with information about:
•
•
Understanding Topology Groups
A Topology Group can be thought of as a convenience view that allows you to view a subset of the entire network based on the group rule defined while creating the view.
These views, which are subsets of the Layer 2 views, can be accessed by a user or a set of users. These custom views are generated using a Campus Manager feature called Grouping Services, which helps manage groups of devices. Grouping Services determines the membership of a group by interpreting and applying the rule associated with the group.
Hence, Topology Groups provides multiple benefits:
•
•
•
See the following sections for a better understanding of Topology Groups concepts:
Concept of a Group
A group is a named set of devices. The group is characterized by a set of properties such as a name, description, type, access permission, etc. Most importantly, a group has an associated rule. The rule determines the membership of a group, which may change whenever the rule is evaluated.
Topology Groups manages groups in a hierarchical organization and supports subgrouping. Two predefined top level parent groups are available:
•
•
By default, only the admin user will have necessary privileges to create groups under System Defined Groups. However, the admin user can edit the group to provide write access to other users. Access permissions are maintained on a username basis, not a role basis.
If you possess appropriate permissions, you can create subgroups under groups. Hence, each child group is a subgroup of a parent group.
Note the following:
•
•
•
•
Membership Update
The membership of a group is governed by the rule associated with a group. The changes in the membership is reflected in the Network Topology View of the group. To view a topology view, select Campus Manager > Topology Views. For more information, see Open a Network Topology View., page 2-26.
Moreover, while groups with evaluation type Automatic have membership that is current, groups with evaluation type Only Upon User Request retain the membership at creation time or on subsequent re-evaluation.
Two modes of membership updates are available:
•
The membership of a group is recomputed automatically on a periodic basis.
If the node or view has been displayed, you must close all of Topology Services and re-open it to display the revised group membership.
•
The membership of the group is recomputed only when an explicit request is made, using the Refresh option. For more information on the Refresh option, see Recomputing Group Membership.
Rules Editor
Every group is defined by a set of rules. You may select an item from the drop down menus, enter a rule in the free-form Rule Text area, or use a combination of the two.
A rule set contains a Boolean combination of individual rule expressions. A rule expression is made of the following components:
Object type
The type of devices which form the group. Rules are evaluated on the list of devices discovered. Campus supports only one object type:
:Campus:OGS:DeviceVariable
Any of the attributes of a device. The following variables are available:
•
•
•
•
•
•
•
•
•
•
Operator
The operator used in forming a rule. The following operators are available:
•
•
When the variable DiscoveryStatus is used, only one operator is available:
•
Value
A free flow operand forming the last part of the rule.
When the variable DiscoveryStatus is used, only the following values are available:
•
•
•
Example of Rule
Let us consider a scenario where you need to define a rule for a set of devices in the State Street Campus. The Campus has devices at two locations: Bldg 1 Devices and Bldg 2 Devices.
In this scenario, we will create rules for the System Defined Groups and the User Defined Groups.
Rule for a System Defined Group
•
:Campus:OGS:Device.SystemLocation equals "Bldg 1 Devices"where
Variable is SystemLocation
Operator is equals
Value is Bldg 1 Devices
•
:Campus:OGS:Device.IpAddress equals "172.20.121.10"In addition you can use the contains operator to match a value anywhere in the attribute:
:Campus:OGS:Device.IpAddress contains "10"The above rule, will match devices with IP address like 172.20.10.3, 172.25.3.101 etc.
Rule for a User Defined Group
•
:Campus:OGS:Device.DeviceLabel equals "Lab Test Setup"where
Variable is DeviceLabel
Operator is equals
Value is Lab Test Setup
•
:Campus:OGS:Device.DeviceLabel equals "J Smith Devices"A Composite Rule
A Boolean set of such rules form a composite rule. In the example, to create a group whose member devices are labelled Lab Test Setup, have a common system contact person, J Smith Devices, the composite rule is:
:Campus:OGS:Device.DeviceLabel equals "Lab Test Setup" AND:Campus:OGS:Device.SystemContact equals "J Smith Devices"Access Controls
You must explicitly set access permissions for the group you create. You can set permissions for the list of all Campus users. The list displays the default permissions assigned to each of them. As a convenience, you can automatically assign username access to the group based on role.
Campus does not maintain role-based access control, rather it is immediately translated into username-based access control.
For example, if while creating a group you set allow read and write access to Network Operators, then at that time all users with Network Operator role are determined and those users given read and write access.
If a user is added to the Network Operator list, the new user will not be automatically given access to the group. You would need to edit the group access list to explicitly add the new user to the list.
Managing Topology Groups
From the CiscoWorks desktop, select Campus Manager > Administration > Topology Groups. The Campus Manager Topology Groups Administration page appears.
When you start Topology Groups, the Topology Groups Administration page appears. You can access the Topology Groups Administration wizard, you can choose to:
•
•
•
•
•
•
Access control to groups is controlled on a username basis.
By default, read permission is granted to System Defined Groups, and read and write permissions are granted to User Defined Groups.
Usually, the admin user creates groups that are to be generally shared among users under the System Defined Groups folder. For example, the admin may wish to create device groupings based on IP address, subnet, location or contact.
The User Defined Groups folder is meant to hold a users private group and/or groups that are more transient in nature.
By default, read permission will be granted to System Defined Groups and read, write, and evaluate permissions will be granted to User Defined Groups.
See Table 8-31 for a description of the elements in the Topology Groups Administration wizard.
Using Topology Groups
The main tasks that you can perform using Topology Groups administration are:
All actions begin from the Topology Groups administration page, unless otherwise specified.
Creating Groups
You can create groups under System Defined Groups and User Defined Groups. This involves:
Creating Group Properties
Access to group creation is based on permission levels. You can create groups under User Defined Groups.
By default, only the CiscoWorks admin user can create under System Defined Groups; however, the admin user can modify the access permission to the System Defined Group to enable edit privilege (i.e., create permission) to other Campus usernames.
To create Group Properties:
Step 1
Step 2
•
•
Step 3
Step 4
Step 5
Creating Group's Rule
To create group's rule, either use the parameters specified, or manually enter the rule text.
To create group rules using parameters:
Step 1
Step 2
Step 3
The rule is added to the Rules Text field.
To create a group rule by entering the rule text:
Step 1
Step 2
You can use the Boolean operators to create composite rules.
•
•
Step 3
Creating Memberships
You can create memberships to specify the devices available to the group. The devices appear in Available Objects or Objects in Group, based on the properties and rules you specified in the previous steps.
Available Objects is the set of objects in the parent group not selected by the child group's rule.
To add the selected devices from the Available Objects list to the Objects in Group list:
Step 1
The devices appear in Available Objects or Objects in Group, based on the properties and rules you specified in the previous steps.
Step 2
To remove the selected devices from the Objects in Group list:
Step 1
Step 2
Creating Access Controls
You can set access permissions for the group from the list of all Campus users. The list displays the default permissions assigned to each of them. To do this:
Step 1
If you want to quickly set the username permission to the group, based on the user role, click Set Default Permissions.
Step 2
Viewing Create Summary
You can view a summary of the group attributes.
Click Finish to create the group according to the properties and rules you specified.
Modifying Groups
You can modify most attributes of a group in the edit mode; except the parent group. To do this:
Step 1
You can modify the Group Name, Description, and Membership Update Type.
Step 2
•
Click Next.
•
Click Next.
•
Click Next.
Step 3
Viewing Group Details
To view the attributes of a group.
Step 1
Step 2
Group information is displayed in the right window.
•
•
•
Recomputing Group Membership
You can re-evaluate and re-apply the group's rule to recompute the membership of groups.
Step 1
Step 2
Step 3
Step 4
Removing a Group
You can remove a topology group and all child groups under it from the Campus desktop.
Step 1
Step 2
Step 3
Step 4
Interpreting Topology Groups Summary Information
You can display summary information about devices in Topology Groups.
Step 1
See Table 8-32 to interpret Topology Groups summary information.
Refreshing Topology Group
You can recompute the membership of a topology group by re-evaluating the group's rule. The membership of Automatic groups is recomputed dynamically; while the membership of Only-upon-user-request groups is recomputed only when explicitly refreshed with this option.
Note
To refresh a Topology Group:
Step 1
The Campus Manager Topology Group Administration and Configuration window appears.
Step 2
The Group Info fields on the right side displays details of the selected group.
Step 3
The Campus Manager Topology Group Administration and Configuration window prompts you for confirmation.
Step 4
The selected topology group is recomputed and the window refreshed.
Whenever you delete devices from a Group, refresh the group so that group membership is recomputed.
Getting Started With Topology Groups
When Campus is installed, these folders are created under Topology Groups:
These groups are provided as a way to categorize groups at your site, and each of these contains a list of all the devices in the ANI Database.
Note
•
System Defined Groups
System Defined Groups is a top-level container for standard groups that are accessible to and used by most Campus users. By default, only the Campus admin user has necessary privilege to create groups under the System Defined Groups folder.
A user must have write permission to a group in order to create a child group under it. Although by default, only the Campus admin user has write permission to System Defined Groups, the admin user can grant write privilege to other users by editing the access permission to System Defined Groups.
A system administrator will typically define and configure their own System Defined Groups based on the partitioning requirements of the network.
The admin may choose to partition views based on any of the attributes that can be grouped; however, IP address, device name, sysLocation, and subnet will be common selections.
Notional examples of groups that might appear under System Defined Groups are:
•
•
User Defined Groups
User Defined Groups is a top-level container where individual Campus users can create their own groups. Typically, the groups under User Defined Groups would be used and accessible to the user who created the group, and perhaps a small group of additional users, or these groups may be transient in nature. A notional example would be that Joe Smith wants create a group that contains all devices where he is the System Contact, and he uses the following rule to form this group:
:Campus:OGS:Device.SystemContact equals "Joe Smith" OR:Campus:OGS:Device.SystemContact equals "jsmith"Overview of Subnet Based Groups
Subnet based groups are automatically created when devices are managed. Subnet based groups help you work on smaller subsets of devices that are logically grouped. They are automatically deleted when all the devices in a subnet are deleted.
Accessing Subnet Based Groups
From the Campus Manager desktop, select Administration > Groups.
This displays the Topology Groups Administration and Configuration page. The Group Selector field will already have two names, System Defined Groups and User Defined Groups. The Subnet Based Groups are created under System Defined Groups.
Understanding Subnet Based Groups
The Subnet based groups use the following name format:
Subnet -- Subnet Mask.The rule expression for Subnet Based Groups has the following components:
Class.attribute operator "value"For example,
:Campus:OGS:Device.IP.Subnet equals "172.20.104.192" AND :Campus:OGS:Device.IP.SubnetMask equals "255.255.255.240"
The rule above will select all devices of subnet 172.20.104.192 and subnet mask 255.255.255.240.
Creating Groups Based on Subnet
For example, the following rules might be used to create two groups based on the IP address subnet:
:Campus:OGS:Device.IP.Subnet equals "172.29.252.32":Campus:OGS:Device.IP.Subnet equals "172.29.252.64"The examples provided here are simple; however the Grouping Service allows arbitrarily complex rules to be formed by combining rule expressions with AND, OR or the EXCLUDE operators. This gives the administrator the power and flexibility to create view partitions tailored to the needs of their site.
Hierarchical Maps
Hierarchical maps are the Network Topology Views, which display the devices listed under Topology Groups in a hierarchical organization. Each map displays the selected group as a cloud of devices.
Understanding Hierarchical Maps
Hierarchical Maps provide a hierarchical view for the devices under the Topology Groups.
These Maps display each Topology Group as a cloud. If a Topology Group contains a sub-group, the Network Topology View of the parent group displays a cloud icon to represent the sub-group. Similarly, each sub-group is displayed inside the corresponding parent group as a cloud icon.
The Network Topology View for the parent topology Group displays an aggregate link for all the links from the sub-group to the devices in the parent group.
•
•
Viewing Hierarchical Maps
To view hierarchical maps from the Topology Services window:
Step 1
Step 2
Step 3
The Network Topology View window displays the hierarchical map for the selected group. If there are sub-groups, the Network Topology View displays each sub-group as a cloud icon in the map represents the sub-group.
Step 4
The Network Topology View window for the sub-group appears.
Or
Double-click the cloud to view the sub-group.
Displaying the Device Label
To display the name of the cloud or the sub-group in the Network Topology View:
Select the cloud, select View > Display Labels, and select either IP address, Device name, or SysName.
The Network Topology View displays the sub-group device category names.
Filters for Topology Groups
Filters are provided for the Topology Groups, in Network Topology Views. You can use these filters to filter the clouds, which are the sub-groups. For more details, see Using Topology Filters.
Displaying Aggregate Links in Hierarchical Maps
You can view the aggregate links between the clouds. The network view displays the aggregate links if a device in a cloud is linked to another cloud or the sub-group. Aggregate links may contain one or more links.
For more details, see Displaying Aggregate Link Attributes.
To view the aggregate links between the clouds, right-click the cloud and select Show Aggregate Links.
To clear the display of aggregate links, right the cloud and select Clear Aggregate Links.
Notes:
•
•
For more details, see Using Find in Network Topology Views.
•
For more details, see Getting Started With Topology Groups.
Topology Services Menu Reference
See the command references for understanding the Topology Services windows.
This section contains:
•
•
Topology Services Main Window Menu Reference
Network Topology View Menu Reference
Supported Protocols
The following concepts are important for understanding how to use Topology Services:
•
•
•
•
You must make sure that the applicable protocols are implemented correctly in your network; otherwise, the information gathered might be incomplete.
Inter-Switch Link (ISL) Protocol
Inter-Switch Link (ISL) is a Cisco-proprietary protocol that allows VLAN trunking by maintaining VLAN information as traffic flows between switches and routers.
You can pass VLAN information between devices by configuring links between the switches. If you want a link to carry more than one VLAN, you must use ISL. To use ISL, you must configure the ports on both sides of the link as trunk ports.
When two VTP domains are interconnected using an ISL trunk between two LAN switches, by default, no VLAN traffic is forwarded. However, you can configure the ports on each switch to receive and forward specific VLANs.
To configure the ports, the VLANs on either side of the ISL trunk must be identical and share the same VLAN characteristics such as VLAN names, VLAN indexes, and so on.
IEEE 802.1Q
IEEE 802.1Q is the industry-standard for trunking. A standard for encapsulation protocol to carry traffic for multiple VLANs over a single link. You can use this standard when you want to interconnect a Cisco device with a trunk link to a non-Cisco device.
You can use the encapsulation dot1q command on Cisco IOS version 12.0.1(t) or higher for the Cisco routers.
Token Ring Bridging Protocols
Two Token Ring bridging protocols are supported:
•
If the trCRF is configured for SRB, ports configured in the trCRF are members of the broadcast domain for the non-source route (NSR) broadcast issued by stations seeking their designation station. Stations belonging to a different trCRF do not receive these broadcasts.
When the NSR broadcast fails to find the destination station, the station sends an All Routes Explorer (ARE) frame. The ARE propagates to all trCRFs belonging to the trBRF. This broadcast frame is not propagated to trCRFs belonging to other trBRFs unless there is an external connection between the trBRFs.
•
If the trCRF is configured for SRT, non-source route (NSR) broadcasts are forwarded to other trCRFs (within the same parent trBRF). The trBRF transparently bridges these NSR broadcasts to other trCRFs configured for SRT. All NSR and NSR-configured trCRF children view the trBRF as a traditional transparent bridge.
See the "Token Ring VLANs" section for information about Token Ring VLANs.
Troubleshooting Topology Services
Use the information in the following topics to help troubleshoot Topology Services:
Troubleshooting Time Domain Reflectometry Reports
Time Domain Reflectometry (TDR) report does not display the entries, and provides a blank report when you run TDR Cable Diagnostic Test on devices, which support TDR. This occurs even when Campus supports the CISCO-CABLE-DIAG-MIB, and if the read and write community strings are correct. For more details on running TDR test on devices, see Running TDR Test From Campus Manager.
When the TDR test fails, an error message appears:
Unable to get TDR related information from one or more devices.Probable CauseOne or more devices:-May not support TDR-May be Unreachable-have incorrect read/write credentials in DCRRecommended ActionDo the following:1. Entercorrect credentials in DCR.2. Initiate Data Collection for the devices.3. Run TDR report.In the log file for Data Collection, you can find the error message:
ERROR: Unable to get Running Status of TDR Test.Probable Cause: Time Taken to complete the TDR test in the device takes long time/Mib support is not available/ Device is not SNMP reachableAction : Add the property TDRTestTimeout and set value for the property in ANIServer.properties to value greater than 7000 and restart ANIServer process.Check SNMP reachability/Check TDR Support on the deviceTo view the log file for Data Collection, go to:
•
•
Probable Cause
When you run TDR Cable Diagnostic Test from Campus Manager, the report generation might take longer. The default time value set for generating the report is 7 seconds. Hence, when TDR test takes more than 7 seconds, the process times out and Campus fails to generate the report.
Possible Solution
When the TDR report fails to generate data, you must modify the ANIServer.properties file. To modify the file, you must:
Step 1
Enter pdterm ANIServer at the command line to stop the ANI server.
Step 2
Step 3
Step 4
Enter pdexec ANIServer at the command line to start the ANI server.
