Configuring Banyan VINES

3000577A:0001
 

In this address, the server number (or more specifically, the serial number of the service node) is 3000577A and the host number is 0001, indicating that this is a service node. Both portions of the address are expressed in hexadecimal format.

	Command	Purpose
Step1	vines routing [address]	Enable VINES RTP routing on the router.
Step2	vines srtp-enabled	Enable VINES SRTP routing on the router.

To enable VINES routing on an interface other than a serial interface, use the following command in EXEC configuration mode:

Command	Purpose
vines metric [whole [fractional]]	Enable VINES routing on an interface.

To enable VINES routing on a serial interface, use the following commands in interface configuration mode:

	Command	Purpose
Step1	show interface	Determine the bandwidth of the interface.
Step2	vines metric [whole [fractional]]	Enable VINES routing, explicitly setting the metric.

For a list of metric values, refer to the "Banyan VINES Commands" chapter in the Cisco IOS ApolloDomain, Banyan VINES, DECnet, ISO CLNS, and XNS Command Reference publication.

Command	Purpose
bridge crb	Enable concurrent routing and bridging for the router.

Client systems on VINES networks are assigned network addresses dynamically. When a VINES client boots, it has no knowledge of its address or preferred server. Immediately after it initializes its hardware interface, the client sends a broadcast request asking a server to provide it with a network-layer address. One of our routers will respond to this broadcast request if there are no VINES servers on the physical network segment. The Cisco IOS software then assigns an address to the network client. (In previous releases, the software would not respond by default.) The software generates a unique network number for the client based on its own VINES address. If the software assigns an address to a client, the router or access server then acts as a network communication service provider for that client. A VINES file server must still be present somewhere on the network in order for the client to connect to all other network services.

• Filters on packet protocol, source and destination addresses, address masks, and explicit port numbers

• Filters on packet protocol, source and destination addresses, address masks, port numbers, and port masks

• Filters on routing updates

Remember these points when you configure VINES network access control:

• You can assign only one access list to an interface.

• The conditions in the access list are applied to all outgoing packets not sourced by the router.

• Access list entries are scanned in the order you enter them. The first matching entry is used.

• An implicit deny everything entry is defined at the end of an access list unless you include an explicit permit everything entry at the end of the list.

• All new entries to an existing list are placed at the end of the list. You cannot add an entry to the middle of a list. Consequently, if you have previously included an explicit permit everything entry, new entries will never be scanned. The solution is to delete the access list and retype it with the new entries.

To control access to the VINES network, first create an access list and then apply an access list to an interface.

To create a VINES access list, use one or more of the following commands in global configuration mode:

Command	Purpose
vines access-list access-list-number {deny | permit} protocol source-address source-mask [source-port] destination-address destination-mask [destination-port]	Create a standard access list.
vines access-list access-list-number {deny | permit} protocol source-address source-mask [source-port source-port-mask] destination-address destination-mask [destination-port destination-port-mask]	Create an extended access list.
vines access-list access-list-number {deny | permit} source-address source-mask	Create a simple access list.

To apply a standard or extended access list to an interface, use the following command in interface configuration mode. Remember that you can apply only one access list to each interface.

Command	Purpose
vines access-group access-list-number	Apply a VINES access list to an interface.

To control routing update frequency and propagation, use one or both of the following commands in interface configuration mode:

Command	Purpose
vines update interval seconds	Change the frequency of sending routing updates.
vines update deltas	Change how routing information is propagated.

NoteThe vines update deltas command does not apply to the SRTP routing protocol.

To control the content of sent or received routing updates, or to control the source address of received routing updates, use one or more of the following commands in interface configuration mode:

Command	Purpose
vines input-router-filter access-list-number	Control the source address of received routing information.
vines input-network-filter access-list-number	Filter the content of received routing information.
vines output-network-filter access-list-number	Filter the content of sent routing information.

To disable split horizon when generating regular periodic routing updates and to disable flash updates to indicate topology change for a changed route, use the following command in global configuration mode:

Command	Purpose
no vines enhancements	Disable split horizon and flash updates.

To disable split horizon on networks that are not fully connected mesh interfaces like X.25 and Frame Relay, use the following command in interface configuration mode:

Command	Purpose
no vines split-horizon	Disable split horizon when sending routing updates.

NoteFor routing updates only, when vines enhancements is enabled in global configuration mode by default, vines split-horizon is also enabled on the interface by default. In this case, if required, you can disable vines split-horizon on an interface like Frame Relay and X.25. When vines enhancements is disabled in global configuration mode, vines split-horizon for RTP routing updates is disabled on all interfaces; however, one may still see vines split-horizon as enabled on the VINES interface when show vines interface interface command is used. Split horizon remains enabled because vines split-horizon on individual VINES interfaces, in addition to controlling RTP updates, also controls whether retransmission of broadcasts is permitted on the receiving interface.

NoteSRTP updates do not use split horizon.

To control the frequency of redirect messages on a specified interface, use the following command in interface configuration mode:

Command	Purpose
vines redirect [seconds]	Set the frequency of RTP and SRTP redirect messages.

Packet transfer performance is generally better when fast switching is enabled. However, you might want to disable fast switching in order to save memory space on interface cards and to help avoid congestion when high-bandwidth interfaces are writing large amounts of information to low-bandwidth interfaces.

To disable fast switching on an interface, use the following command in interface configuration mode:

Command	Purpose
no vines route-cache	Disable fast switching.

To set the VINES network time, use one or more of the following commands in global configuration mode:

Command	Purpose
vines time participate	Enable the sending of time-synchronization messages across a VINES network.
vines time set-system	Periodically synchronize the time of the router with the VINES network time.
vines time services	Provide time services for VINES clients and enable participation in the synchronization of time across a VINES network.
vines time use-system	Periodically synchronize the VINES network time with the time of the router.
vines time access-group access-list-number	Accept time updates from the stations permitted by the specified simple access list.
vines time destination address	Send time updates only to the specified station.

To add a static route to the routing table, use the following command in global configuration mode:

Command	Purpose
vines route number address [whole [fractional]]	Add a static route to the routing table.

You can configure static routes that can be overridden by dynamically learned routes. These types of static routes are referred to as floating static routes. You can use a floating static route to create a path of last resort that is used only when no dynamic routing information is available.

To avoid the possibility of a routing loop occurring, by default, floating static routes are not redistributed into other dynamic protocols. Floating static routes must not be advertised on interfaces that are paths to the destination. To configure a floating static route, assign a metric to the static route that is worse (higher) than all dynamic routes.

To add a floating static route to the routing table, use the following command in global configuration mode:

Command	Purpose
vines route number address [whole [fractional]]	Add a floating static route to the routing table.

To add a static path to a neighbor station, use the following command in interface configuration mode:

Command	Purpose
vines neighbor address mac-address encapsulation [whole [fractional]]	Add a static path to the neighbor station.

To have the software modify how it forwards broadcast packets, use one of the following commands in interface configuration mode:

Command	Purpose
no vines propagate	Ensure that the software never ignores the "class" field when forwarding broadcast packets.
vines propagate	Ensure that the software always ignores the "class" field when forwarding broadcast packets.

Command	Purpose
clear vines cache [interface interface | neighbor address | server network | counters]	Delete entries from the VINES fast-switching cache table.
clear vines ipc number	Delete VINES IPC connection blocks from the router.
clear vines neighbor {address | *}	Delete entries from the neighbor table.
clear vines route {network | *}	Delete network addresses from the routing table.
clear vines traffic	Zero the VINES-related traffic statistics displayed by the showvines traffic command.
ping vines [address]	Send datagrams to a host to determine network connectivity.
show vines access [access-list-number]	Display the VINES access lists currently defined.
show vines cache [address | interface type number | neighboraddress | server network]	Display the contents of the VINES fast-switching cache table.
show vines host [name]	Display the entries in the VINES host name table.
show vines interface [type number]	Display VINES-related interface settings.
show vines ipc	Display information about any currently active IPC connections.
show vines neighbor [address | interface type number | servernumber]	Display the contents of the VINES neighbor table.
show vines route [number | neighbor address | metric]	Display the contents of the VINES routing table.
show vines service [fs | nsm | ss | vs]	Display information about the application layer support of the router.
show vines traffic [type number]	Display the statistics about VINES protocol traffic.
trace [vines | oldvines] [address]	Determine the path a packet takes when traversing a VINES network.

If you find that two routers have the same VINES network address, you can have the routers dynamically recompute their addresses. To recompute the addresses on each of the two routers, use the following command in global configuration mode:

Command	Purpose
vines routing recompute address	Dynamically redetermine the address of the router.

The following example shows how to configure Routers A and B:

vines routing
!
interface ethernet 0
 vines metric 2
!
interface ethernet 1
 vines metric 2

Configuration for Router A

vines routing
!
interface ethernet 0
 vines metric 2
!
interface serial 0
 vines metric 45

Configuration for Router B

vines routing
!
interface ethernet 0
 vines metric 2
!
interface serial 0
 vines metric 45
 

Configuration for Router A

vines routing
!
interface ethernet 0
 vines metric 2
!
interface serial 0
 vines metric 55

Configuration for Router B

vines routing
!
interface ethernet 0
 vines metric 2
!
interface serial 0
 vines metric 55
 

The best way to configure this topology is shown in the following configuration:

Configuration for Router A

vines routing
!
interface ethernet 0
 vines metric 2
 vines serverless broadcast
!
interface fddi 0
 vines metric 1

Configuration for Routers B and C

vines routing
!
interface ethernet 0
 vines metric 2
!
interface fddi 0
 vines metric 1
 

The following example shows how to configure Router B:

vines routing
vines access-list 1 deny IP 274113:1 0:0 274111:1 0:0
vines access-list 1 permit IP 0:0 FFFFFFFF:FFFF 0:0 FFFFFFFF:FFFF
!
interface ethernet 0
 vines metric 2
 vines access-group 1
!
interface fddi 0
 vines metric 1
 

The first line in the access list prohibits any communication between the two servers, and the second line allows all other communication to pass through the router.

The following example shows how to only allow mail traffic between these two servers. Port 4 is the VINES Mail port.

vines routing
vines access-list 101 permit IPC 274113:1 0:0 0 FFFF 274111:1 0:0 4 0
vines access-list 101 permit IPC 274111:1 0:0 4 0 274113:1 0:0 0 FFFF
vines access-list 101 deny IP 274111:1 0:0 274113:1 0:0
vines access-list 101 permit IP 0:0 FFFFFFFF:FFFF 0:0 FFFFFFFF:FFFF
!
interface ethernet 0
 vines metric 2
 vines access-group 101
!
interface fddi 0
 vines metric 1
 

The first line in the access list allows mail messages being sent from the server in the lower-right to the server in the upper-left. The second line allows mail messages in the other direction. The third line prohibits all other communication between these two servers. The last line allows all other communication to pass through the router.