|
|
This appendix provides troubleshooting information. It consists of the following sections:
You cannot log on to the system.
If no, run the setup program as described in the "Configuring the VLAN Policy Server" section.
Step 2 Do you know the password for any system user accounts?
If no, reconfigure the system to create a new user account. Refer to the "Recovering from the Loss of All Administrator Passwords" section for more information.
Step 3 If you are certain you entered a valid username and password, contact the Cisco Technical Assistance Center (TAC) for assistance.
The system cannot connect to the network.
If the network cable is connected and the Ethernet indicator is on but the system cannot connect to the network, continue.
Step 2 Use the ping command to perform the following tests:
If the ping command gets a response, the system is connected to the network. If it cannot connect to a particular host, the problem is either with the network configuration or that host. Contact your network administrator for assistance.
If the ping command does not get a response, continue.
If the ping command can connect to a host on the same subnet, but cannot connect to a host on a different subnet, the default gateway is probably down.
If the ping command cannot connect to any hosts, continue.
Step 3 Use the show interfaces command to determine if the Ethernet 0 interface is disabled or misconfigured. For more information, refer to the "show syslog" section.
If the Ethernet 0 interface is disabled, enable it. If it is misconfigured, configure it correctly. For more information, refer to "Configuring the Ethernet Ports" section.
If the interface is enabled and correctly configured, continue.
Step 4 Contact your network administrator to verify that there are no conditions on the network that prevent the system from connecting to the network.
If conditions prevent the system from connecting to the network, have your network administrator correct them.
Step 5 If no conditions are preventing the system from connecting to the network, contact the Cisco Technical Assistance Center (TAC).
You cannot connect to the system by entering its IP address in a web browser.
If you cannot connect, continue.
Step 2 If you are attempting to connect via HTTP, verify that the IP address is appended with :1741.
Step 3 If you are attempting to connect via HTTP, verify that HTTP is enabled. If you are attempting to connect via HTTPS, verify that HTTPS is enabled. For more information, see the "Configuring the Ethernet Ports" section.
Step 4 Verify that the browser is configured correctly, and attempt to connect to the VLAN Policy Server. For more information, see the "Configuring the Web Browser" section. If you cannot connect, continue to step 5.
Step 5 At the system console, or through Telnet, verify that the web server and the tomcat log are running by entering the following:
If they are running, go to step 7. If they are not running, continue to step 5.
Step 6 Stop the system services by entering the following:
Step 7 Restart the system services by entering the following:
Step 8 Try to connect the system using a web browser.
If you cannot connect, continue to step 9.
Step 9 Reboot the system by entering the reload command.
For more information about the reload command, refer to the "reload" section.
Step 10 If you still cannot connect to the system using a web browser, contact the Cisco Technical Assistance Center (TAC) for assistance.
The system time or date is incorrect.
Refer to the "Setting System Date and Time" section for information about maintaining the system time and date.
The system cannot boot from the hard drive during a reboot.
If the VLAN Policy Server cannot boot from the hard drive, the hard drive needs to be reimaged. Use the recovery CD to reimage your VLAN Policy Server. For more information, see the "Using the Recovery CD" section.
You cannot connect to the system using Telnet or Telnet interaction, even though the system is connected to the network.
 |
Note If you are not using name recognition, slow or nonexistent Telnet interaction is an expected problem. For more information, see the "Name Resolution" section. |
If the problem is not in the network, perform the following steps (connect to the console port if you cannot Telnet to the VLAN Policy Server):
Step 2 If you have specified hosts in telnetenable, make sure the host from which you are attempting to Telnet is on the list.
Step 3 If you are using a DNS server, perform the following steps:
where ip-address is the IP address of the DNS server.
If you are using the import command-line interface (CLI) command, proceed to Step 4.
where dns-name is the DNS name of a host on the network that is registered in DNS and hostname, and ip-address is the same IP address specified in
Step 2. The command returns the IP address of the host.
c. If the system cannot resolve DNS names to IP addresses, the DNS server it is using is not working properly.
Resolve the network DNS problem, then continue.
Step 4 If you are using the import CLI command to resolve hostnames, verify that the VLAN Policy Server can resolve hostnames by entering the following command:
where hostname is a hostname that has been mapped to an IP address, or imported in a host file, using the import command.
Step 5 If the system can resolve DNS names to IP addresses but you still cannot connect to the system using Telnet, or if Telnet interaction with the system is extremely slow, contact the Cisco Technical Assistance Center (TAC).
The VLAN Policy Server does not discover certain devices.
For information on resolving these problems, see the VLAN Policy Server online help.
To access the online help relevant to these problems:
Step 2 Click Help. A new browser window containing the online help appears.
Step 3 Select Performing Administrative Tasks.
Posted: Wed May 21 10:34:03 PDT 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.