Clients or servers not attached to the network
|
Step 1 Connect both clients and servers to the same network and verify that they can communicate.
Step 2 If they cannot communicate, check the configuration of the client and server. Refer to host software documentation for troubleshooting information.
Step 3 Attach a network analyzer to the network to which clients and servers are temporarily connected. Look for the source addresses of both.
Step 4 If you find the source addresses, the clients and servers are operating properly. If you do not find their addresses, check the configuration of the clients and servers. (Consult your client and server documentation for more information.) |
| Router interface not functioning |
Step 1 Use the show interfaces EXEC command to check the operation of the router.
Step 2 If the status line indicates that the interface is "administratively down," specify the no shutdown interface configuration command on the interface.
Step 3 If the status line indicates that the interface or protocol is "down," check cable connections from the router. If necessary, replace the cable.
Step 4 If, after replacing the cable, the show interfaces EXEC command still does not indicate that the interface and line protocol are "up," contact your router technical support representative. |
| VINES metric value not specified |
Step 1 Use the show vines interface EXEC command to check the operation of the router. Look for an interface that has the vines metric interface configuration command, which enables VINES processing on the interface.
Step 2 If the vines metric interface configuration command is not specified for the interface, specify that command for the interface. |
| Missing vines serverless or vines arpenable commands |
Step 1 Use the show vines interface EXEC command or the write terminal command to check the operation of the router. A network that does not have a server must be configured with the vines serverless and vines arp-enable router configuration commands.
Step 2 If the vines serverless and vines arp-enable commands are not specified for this interface, specify those commands for this interface. |
| Misconfigured access list |
Step 1 Remove the specification of any vines access-group commands on all relevant interfaces.
Step 2 Test the connection from the client to the target server to see whether traffic can get through.
- If the connection works, the access list needs modification.
Step 3 To isolate the bad access list specification, apply one access list statement at a time until you can no longer create connections.
Step 4 Make sure that access lists are applied to the correct interface. Normally, traffic filters are applied to outgoing interfaces. |
| Nonfunctional FDDI ring |
Step 1 Use the show interfaces fddi EXEC command to determine the status of the interface.
Step 2 If the output of the show interfaces fddi EXEC command indicates that the interface and line protocol are up, use the ping vines privileged EXEC command to test connectivity between routers.
Step 3 If the interface and line protocol are up, verify that the Media Access Control (MAC) addresses of upstream and downstream neighbors are as expected.
- If all zeros appear in either of the address fields for these neighbors, a physical connection problem is likely.
Step 4 In this case (or if status line does not indicate that the interface and line protocol are up), check patch-panel connections and check connectivity between routers using an optical time domain reflectometer (TDR) or light meter. Ensure that signal strength is within specification. |
| Nonfunctional serial link |
Step 1 Use the show interfaces serial command to determine the status of interface.
Step 2 If the show interfaces serial command indicates that the interface and line protocol are up, use the ping vines command to test connectivity between routers.
Step 3 If routers do not respond to the ping test, follow the troubleshooting techniques discussed in Chapter 3, "Troubleshooting Serial Line Problems." |
| Nonfunctional Ethernet backbone |
Step 1 Use the show interfaces ethernet command to determine the status of the interface.
Step 2 If the status line does not indicate that the interface and line protocol are up, check the physical attachment of the router to the Ethernet backbone.
Step 3 If the show interfaces ethernet command indicates that the interface and line protocol are up, use the ping vines command to test connectivity between routers.
Step 4 Obtain analyzer traces and look for packets from target servers, clients, and routers.
Step 5 Any nodes that do not appear as expected are potential problem nodes. Determine whether the node and its cables are functional. If not, replace or reconfigure as needed. |
| Nonfunctional Token Ring backbone |
Step 1 Use the show interfaces token command to determine the status of the interface.
Step 2 If the status line indicates that the interface and line protocol are not up, check the cable from the router to the multistation access unit (MAU). Make sure that the cable is good; replace the cable if necessary.
Step 3 If the show interfaces token command indicates that the interface and line protocol are up, use the ping vines command to test connectivity between routers.
Step 4 If the remote router does not respond, check the ring specification on all nodes attached to the Token Ring backbone. All of the nodes must have the same ring speed.
- If necessary, modify ring speed specifications for clients, servers, and routers.
Step 5 Use the ring-speed interface configuration command to modify the ring speed for Token Ring cards that support software speed configuration. Change jumpers as needed for modular router platforms. For more information about ring speed specification, refer to the hardware installation and maintenance manual for your system. |
| Mismatched MAC-level encapsulation methods in broadcast |
Step 1 Check the encapsulation type of each VINES interface.
Step 2 Compare the encapsulation type with the encapsulation type assigned on the router. Modify the router configuration as necessary.
- The vines encapsulation command only affects broadcasts from the router. The router keeps track of which encapsulation is used by each of its neighbors and uses that encapsulation type when it talks directly to a neighbor.
|
