Cisco Cisco Configuration Engine 3.5.3 Guía Para Resolver Problemas
Troubleshooting Guide for Cisco Configuration Engine 3.5.3
Troubleshooting Logging and Connection Issues
3
Troubleshooting Guide for Cisco Configuration Engine 3.5.3
OL-17767-03
System Cannot Connect to the Network
Problem
The system cannot connect to the network.
Possible Cause
This problem can occur for the following reasons:
–
The network cable is not connected to an Ethernet port.
–
The Ethernet interface is disabled or misconfigured.
–
The system is configured correctly, but the network is down or misconfigured.
–
The system is not configured correctly.
Solution
To resolve this problem, follow these steps:
Step 1
Verify that the network cable is connected to an Ethernet port and the link light is on.
•
If the network cable is not connected, connect it.
•
If the network cable is connected but the link light is not on, check for these probable causes:
–
The network cable is faulty.
–
The network cable is the wrong type (for example, a crossover type is used, instead of the
required straight-through type).
required straight-through type).
–
The port on the default gateway to which the system connects is down.
Step 2
If you still cannot connect to the network, use the ping command to perform the following tests:
a.
Try to connect to a well-known host on the network. A Domain Name System (DNS) server is a good
target host.
target host.
If the ping command can reach the well-known host and the system is connected to the network. If
it cannot connect to the host, the problem is with the network configuration or the host. Contact your
network administrator for assistance.
it cannot connect to the host, the problem is with the network configuration or the host. Contact your
network administrator for assistance.
b.
If the ping command cannot reach the well-known host, try to reach another host on the same subnet
as the system.
as the system.
If the ping command can reach a host on the same subnet, but cannot reach a host on a different
subnet, the default gateway is probably down or misconfigured.
subnet, the default gateway is probably down or misconfigured.
Step 3
If the ping command cannot reach any hosts, use the ifconfig command to determine whether the
Ethernet interface is disabled or misconfigured.
Ethernet interface is disabled or misconfigured.
If the Ethernet interface is disabled, enable it. If it is misconfigured, configure it correctly.
Step 4
If the interface is enabled and correctly configured but you still cannot connect to the network, ensure
that all the network settings are configured correctly. Run the set up program again by entering the setup
command in the shell prompt.
that all the network settings are configured correctly. Run the set up program again by entering the setup
command in the shell prompt.
Note
You cannot run the set up program second time by logging in as setup. For security reasons, the
account is disabled after it is used once successfully.
account is disabled after it is used once successfully.
Step 5
Contact your network administrator to verify that there are no conditions on the network that prevents
the system from connecting to the network.
the system from connecting to the network.