-
User Guide for Campus Manager 3.3
-
Preface
-
Overview
-
Managing Physical and Logical Network Services with Topology Services
-
Locating Users in the Network with User Tracking
-
Managing VLAN Ports with VLAN Port Assignment
-
Tracking Packet Flow Using Path Analysis
-
Setting up support for CiscoWorks ANI Server
-
Administering Campus Manager
-
Diagnosing Network Connectivity Problems
-
Diagnosing Voice Problems
-
Implementing VLANs in Your Ethernet Network
-
Synchronizing Device Information Between the ANI Server and Resource Manager Essentials
-
Printing Network Topology Information
-
Configuring and Monitoring LANE Services
-
Troubleshooting Connectivity Problems Using Campus Manager Applications
-
Discovering Preferred Management Addresses for Routers
-
Index
-
Table Of Contents
Troubleshooting Browser and Connectivity Problems Using Campus Manager Applications
Why does Campus not work optimally when I connect to the network through a proxy server?
How do I configure browser telnet?
Troubleshooting Browser and Connectivity Problems Using Campus Manager Applications
A common network problem is loss of IP connectivity between two end points (A and B). The table below shows the Campus tools to use to verify and localize this type of problem.
The steps listed here are not exhaustive. You may need to perform other steps to further identify and troubleshoot the failure. However, this table attempts to guide you to investigate connectivity problems using Campus tools.
You can refer to the Frequently Asked Questions for answers to other browser related troubleshooting questions.
Step 1
Make sure the ANI server has the most current network information.
1.
Select Campus Manager > Topology Services.
2.
If there have been no network changes since the last discovery, you can proceed.
If there have been changes to the network since the last discovery cycle, do a rediscovery of the network.
Step 2
Locate the affected end-user host in the network.
1.
2.
Obtain IP addresses of end-user hosts.
Step 3
Check for duplicate MAC addresses.
1.
2.
If there are duplicate MAC addresses, User Tracking reports the offending end-user hosts. Investigate further.
Step 4
Check for duplicate IP addresses.
1.
2.
If there are duplicate IP addresses, User Tracking reports the offending end-user hosts. Investigate further.
Step 5
Run a path trace from end-user host A (source) to end-user host B (destination).Step 5
Run a path trace from end-user host A (source) to end-user host B (destination).
1.
2.
3.
4.
If there is no trace or if an error message
Could not reach source
appears, there may be a problem is related to IP connectivity at end-user host A (source).Step 6
Run a reverse path trace from end-user host B (source) to end-user host A (destination).A partial trace helps you localize the problem.
A successful trace indicates that there may not be an IP connectivity problem.
However, there may be a problem, perhaps at the application layer.
Step 14
Check firewall and filter configuration on each potentially affected device.or
Step 6
Run a reverse path trace from end-user host B (source) to end-user host A (destination).
1.
2.
3.
4.
If the reverse trace is also unsuccessful or if an error message
Could not reach source
appears, there might be a problem between the CiscoWorks server and the end-user hosts.This error may prevent Path Analysis from performing the trace between end-user hosts A and B.
Step 7
Run a path trace between the CiscoWorks server and both end-user hosts.If the reverse trace provides a partial trace, this information helps you localize the problem.
Step 7
Run a path trace between the CiscoWorks server and both end-user hosts.
1.
2.
3.
4.
5.
An unsuccessful or partial trace might indicate that there is a connectivity problem related to the subnet where the CiscoWorks server resides.
A successful path trace might indicate that you are able to reach both end points independently.
However, the end points cannot communicate with each other.
Diagnose and correct the problem.
Continue localizing the original problem with Step 5.
Step 8
Highlight trace in Topology view.
1.
2.
3.
Locate the highlighted path, and check for possible signs of failure, for example, a red link.
This could indicate a port failure (bad NIC or MAU), loose connector, or bad cable.
If none of these are the cause, do one of the following:
•
Step 9
Investigate link attributes.
1.
2.
Check the following fields for information:
•
•
•
Step 10
Investigate port attributes.
1.
2.
3.
4.
5.
Check the following fields for:
•
•
•
•
•
•
•
•
Step 11
Check physical discrepancies in Topology Services
Select Campus Manager > Discrepancy Reports > Physical Discrepancies.
Check for physical discrepancies, such as link, duplex, and speed mismatch and trunk/non-trunk mismatch.
Step 12
Check logical discrepancies in Topology Services.
Select Campus Manager > Discrepancy Reports > Logical Discrepancies.
Check for logical discrepancies, such as VLAN and VTP inconsistencies or ATM network misconfiguration.
Step 13
Use CiscoView (or telnet) to reach suspect devices and investigate further.Step 13
Use CiscoView (or telnet) to reach suspect devices and investigate further.
1.
2.
3.
4.
Variable.
Step 14
Check firewall and filter configuration on each potentially affected device.Step 14
Check firewall and filter configuration on each potentially affected device.
1.
2.
3.
4.
Firewall or filter could be blocking traffic that needs to pass through.
Step 15
Check servers and applications.
None.
Variable.
Variable.
Frequently Asked Questions
Use the information in the section to answer some of your common questions:
•
•
Why does Campus not work optimally when I connect to the network through a proxy server?
Campus will not be able to load Topology Services if proxy configuration is enabled on the browser. This is due to CORBA bug. While there is no fix available, you can work around the problem by disabling the proxy for local addresses and connecting directly to your network.
On Netscape Navigator, do the following:
Step 1
Step 2
But, if it is not feasible to disable the proxy, you would need to bypass the proxy server by modifying the proxy.pac file or using manual configuration.
On Internet Explorer, do the following:
Step 1
The Local Area Network (LAN) Settings dialog box appears.
Step 2
Step 3
But, if it is not feasible to disable the proxy, you would need to bypass the proxy server. For this, do the following:
Step 1
The Local Area Network (LAN) Settings dialog box appears.
Step 2
Step 3
The Proxy Settings dialog box appears.
Step 4
How do I configure browser telnet?
For Campus in Windows, the telnet protocol is used to launch telnet. So this makes telnet a part of browser handling of the protocol, with respect to the Operating System. You can specify any telnet application of your choice for use as the default telnet helper application by your browser, and hence, Campus.
On Netscape Navigator for Solaris
Step 1
Step 2
The telnet helper application is the application listed in the Handled by field.
Step 3
Step 4
xterm -e telnet %h %pto
dtterm -e telnet %h %pOn Netscape Navigator for Windows:
Step 1
Step 2
The telnet helper application is the application listed in the Handled by field.
Step 3
Step 4
rundll32.exe url.dll,TelnetProtocolHandler %lOn Internet Explorer for Windows:
In the case of Internet Explorer on windows, change the following registry setting:
Step 1
Step 2
rundll32.exe url.dll,TelnetProtocolHandler %lInternet Explorer will now use the normal Windows command window to launch telnet.