System information

Troubleshooting Banyan VINES
Book Title
13-296
VINES: Clients Cannot Communicate with Servers over Router
Symptom: Clients cannot connect to VINES servers over one or more routers. Clients might or
might not be able to connect to servers on their directly connected networks.
Table 13-1 outlines the problems that might cause this symptom and describes solutions to those
problems.
Table 13-1 VINES: Clients Cannot Communicate with Servers over Router
Possible Problem Solution
Router interface is down
Step 1 Use the show interfaces exec command to check the status of the router
interfaces.
Step 2 If the status line indicates that an interface that should be up is
“administratively down,” use the no shutdown interface configuration
command on the interface.
Refer to the troubleshooting chapter that covers the media type used in your
network.
Hardware or media problem For information on troubleshooting hardware problems, refer to the troubleshooting
chapter that covers the media type used in your network.
Addressing problem
Step 1 On a serverless segment, use the show vines route exec command to make
sure the router is seeing server network layer addresses.
Step 2 If the router is not seeing server addresses, make sure that the server and
router addresses are correct. To change the address, use the following
syntax:
vines routing [address | recompute]
Syntax Description:
• address (Optional)—Network address of the router. You should specify
an address on a router that does not have any Ethernet or FDDI
1
interfaces. You can also specify an address in the unlikely event that two
routers map themselves to the same address.
• recompute (Optional)—Dynamically redetermines the router’s network
address.
VINES metric value is not
specified
Step 1 Use the show vines interface exec command to check the status of VINES
interfaces on the router. Make sure all VINES interfaces have the
vines metric interface configuration command configured. The metric
command enables VINES processing on the interface.
Step 2 If the vines-metric interface configuration command is not configured on
the interface, specify the command for the interface.
Configure the vines metric based on whether the interface is LAN or
WAN connected. Suggested metrics for LAN and WAN connections
follow:
• Ethernet and 16-Mbps Token Ring: vines-metric 2
• 4-Mbps Token Ring: vines-metric 4
• T1 line: vines-metric 35
• Other WAN link: vines-metric 45