|
|
To apply an access list to an interface, use the vines access-group command in interface configuration mode. To remove the access list, use the no form of this command.
vines access-group access-list-number
Syntax Description
access-list-number Number of the access list. All outgoing packets defined with either standard or extended access lists and forwarded through the interface are filtered by the entries in this access list. For standard access lists, access-list-number is a decimal number from 1 to 100. For extended access lists, access-list-number is a decimal number from 101 to 200.
Defaults
No access list is applied.
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The vines access-group command applies an access list created with the vines access-list (standard) command to an interface.
You can apply only one access list to an interface.
Examples
The following example applies access list 1 to Ethernet interface 0:
interface ethernet 0 vines access-group 1
Related Commands
Creates an extended VINES access list.
Command
Description
To create an extended VINES access list, use this version of the vines access-list command in global configuration mode. To remove an extended access list, use the no form of this command.
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]
Syntax Description
access-list-number Number of the access list. This is a decimal number from 101 to 200. deny Denies access if the conditions are matched. permit Allows access if the conditions are matched. protocol VINES protocol ID number or name. The number can be a value from 1 to 255, or one of the following protocol keywords: source-address Address of the network from which the packet is being sent. This is a 6-byte hexadecimal number in the format network:host, where network is 4 bytes, and host is 2 bytes. source-mask Mask to be applied to source-address. This is a 6-byte hexadecimal value. Place ones in the bit positions you want to mask. These bits correspond to the bits in the address that should be ignored. source-port (Optional) Number of the local port from which the packet is being sent. This argument is required when the protocol specified is IPC or SPP, and is not accepted when any other protocol is specified. It can be a number from 0x0000 to 0xFFFF. Well-known local port numbers have values from 0x0001 to 0x01FF. Transient local port numbers have values from 0x0200 to 0xFFFE. The "Usage Guidelines" section lists some IPC port numbers. source-port-mask (Optional) Mask to be applied to the source-port argument. This argument is required when the protocol specified is IPC or SPP, and is not accepted when any other protocol is specified. It can be a number from 0x0000 to 0xFFFF. These bits correspond to the bits in the port that should be ignored. destination-address VINES address of the network to which the packet is being sent. This is a 6-byte hexadecimal number in the format network:host, where network is 4 bytes and host is 2 bytes. destination-mask Mask to be applied to destination-address. This is a 6-byte hexadecimal value. Place ones in the bit positions you want to mask. These bits correspond to the bits in the address that should be ignored. destination-port (Optional) Number of the local port to which the packet is being sent. This argument is required when the protocol specified is IPC or SPP, and is not accepted when any other protocol is specified. It can be a number from 0x0000 to 0xFFFF. Well-known local port numbers have values from 0x0001 to 0x01FF. Transient local port numbers have values from 0x0200 to 0xFFFE. Table 17 in the "Usage Guidelines" section lists some IPC port numbers. destination-port-mask (Optional) Mask to be applied to destination-port. This argument is required when the protocol specified is IPC or SPP, and is not accepted when any other protocol is specified. It can be a number from 0x0000 to 0xFFFF. These bits correspond to the bits in the port that should be ignored.
Defaults
No extended VINES access list is specified.
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
An extended VINES access list filters packets based on their protocol, source and destination addresses, and source and destination address masks, and optionally on their source and destination ports, and source and destination port masks. This differs from the standard access list filters in that you can specify port masks.
Use the vines access-group command to assign an access list to an interface.
Keep the following in mind when configuring VINES network access control:
If you specify a protocol type of IPC, the port (either source-port or destination-port) can be one of the values shown in Table 17.
| IPC Port Number (Hexadecimal) | Service |
|---|---|
0x0003 | Back End (only on PCs; it is the 25th line notification) |
0x0004 | Mail Service |
0x0006 | "VINES Files" File Service |
0x0007 | Server Service |
0x000F | StreetTalk Service |
0x0012 | Network Management |
0x0013 | VINES Security |
0x0016 | StreetTalk Directory Assistance |
0x0017 | StreetTalk Directory Assistance Service Listening Port |
0x0019 | Systems and Network Management |
Examples
In the following example, the first line prohibits communication from any client process to the service on IPC port 0x14; the second line permits all other communication.
vines access-list 101 deny IPC 0:0 ffffffff:ffff 0x14 0 0:0 ffffffff:ffff 0 0xFFFF vines access-list 101 permit IP 0:0 ffffffff:ffff 0:0 ffffffff:ffff
Related Commands
priority-list protocol Establishes queueing priorities based on the protocol type. show vines access Displays the VINES access lists currently defined. Applies an access list to an interface. Creates a simple VINES access list.
Command
Description
To create a simple VINES access list, use this version of the vines access-list command in global configuration mode. To remove a simple access list, use the no form of this command.
vines access-list access-list-number {deny | permit} source-address source-mask
Syntax Description
access-list-number Access list number. It is a number from 201 to 300. deny Denies access if the conditions are matched. permit Allows access if the conditions are matched. source-address Address of the network from which the packet is being sent. This is a 6-byte hexadecimal number in the format network:host, where network is 4 bytes and host is 2 bytes. source-mask Mask to be applied to source-address. This is a 6-byte hexadecimal value. Place ones in the bit positions you want to mask. These bits correspond to the bits in the address that should be ignored.
Defaults
No simple VINES access list is specified.
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
A simple VINES access list filters packets based on their source address and source address mask. These access lists are used to decide from which stations to accept time updates.
Use the vines access-group command to assign an access list to an interface.
Keep the following in mind when configuring VINES network access control:
Examples
The following example defines an access list that accepts time updates only from the servers on networks 30015800 and 30004355; it denies time updates from all other sources.
vines access-list 201 permit 30015800:0001 00000000:0000 vines access-list 201 permit 30004355:0001 00000000:0000 vines access-list 201 deny 00000000:0000 FFFFFFFF:FFFF interface ethernet 0 vines time access-group 201
Related Commands
show vines access Displays the VINES access lists currently defined. Applies an access list to an interface. Creates an extended VINES access list. Controls the servers from which the router will accept VINES network time. Enables participation in synchronizing time across a VINES network. Enables the Cisco IOS to provide time services for VINES clients and enables participation in the synchronization of time across a VINES network. Sets VINES network time based on the internal time.
Command
Description
To specify a standard VINES access list, use this version of the vines access-list command in global configuration mode. To remove the access list, use the no form of this command.
vines access-list access-list-number {deny | permit} protocol source-address source-mask [source-port] destination-address destination-mask [destination-port]
Syntax Description
access-list-number Number of the access list. This is a decimal number from 1 to 100. deny Denies access if the conditions are matched. permit Allows access if the conditions are matched. protocol VINES protocol ID number or name. It can be a value from 1 to 255 or one of the following protocol keywords: source-address Address of the network from which the packet is being sent. This is a 6-byte hexadecimal number in the format network:host, where network is 4 bytes and host is 2 bytes. source-mask Mask to be applied to source-address. This is a 6-byte hexadecimal value. Place ones in the bit positions you want to mask. These bits correspond to the bit in the address that should be ignored. source-port (Optional) Number of the local port from which the packet is being sent. This argument is required when the protocol specified is IPC or SPP, and is not accepted when any other protocol is specified. It can be a number from 0x0000 to 0xFFFF. Well-known local port numbers have values from 0x0001 to 0x01FF. Transient local port numbers have values from 0x0200 to 0xFFFE. Table 18 lists some IPC port numbers. destination-address Address of the network to which the packet is being sent. This is a 6-byte hexadecimal number in the format network:host, where network is 4 bytes and host is 2 bytes. destination-mask Mask to be applied to destination-address. This is a 6-byte hexadecimal value. Place ones in the bit positions you want to mask. These bits correspond to the bits in the address that should be ignored. destination-port (Optional) Number of the local port to which the packet is being sent. This argument is required when the protocol specified is IPC or SPP, and is not accepted when any other protocol is specified. It can be a number from 0x0000 to 0xFFFF. Well-known local port numbers have values from 0x0001 to 0x01FF. Transient local port numbers have values from 0x0200 to 0xFFFE. Table 18 in the "Usage Guidelines" section lists some IPC port numbers.
Defaults
No standard VINES access list is specified.
Command Modes
Global configuration
Command History
10.3 This command was introduced.
Release
Modification
Usage Guidelines
A standard VINES access list filters packets based on their protocol, source and destination addresses, and source and destination address masks, and optionally on their source and destination ports.
Use the vines access-group command to apply an access list to an interface.
Keep the following in mind when configuring VINES network access control:
If you specify a protocol type of IPC, the port (either source-port or destination-port) can be one of the values shown in Table 18.
| IPC Port Number (Hexadecimal) | Service |
|---|---|
0x0003 | Back End (only on PCs; it is the 25th line notification) |
0x0004 | Mail Service |
0x0006 | "VINES Files" File Service |
0x0007 | Server Service |
0x000F | StreetTalk Service |
0x0012 | Network Management |
0x0013 | VINES Security |
0x0016 | StreetTalk Directory Assistance |
0x0017 | StreetTalk Directory Assistance Service Listening Port |
0x0019 | Systems and Network Management |
Examples
In the following example, the first line prohibits any communication on StreetTalk port (port number 0xF); the second line permits all other communication.
vines access-list 1 deny IPC 0:0 ffffffff:ffff 0xf 0:0 ffffffff:ffff 0xf vines access-list 1 permit IP 0:0 ffffffff:ffff 0:0 ffffffff:ffff
The following example filters all mail service on Ethernet interface 0 and permits all other traffic:
interface Ethernet 0 vines access-group 101 ! vines access-list 101 deny ipc 0:0 FFFFFFFF:FFFF 4 0 0:0 FFFFFFFF:FFFF 0 0xF FFF
Related Commands
priority-list protocol Establishes queueing priorities based on the protocol type. show vines access Displays the VINES access lists currently defined. Applies an access list to an interface. Creates an extended VINES access list. Creates a simple VINES access list.
Command
Description
To enable the processing of ARP packets, use the vines arp-enable command in interface configuration mode. To disable the processing of ARP packets, use the no form of this command.
vines arp-enable [dynamic]
Syntax Description
dynamic (Optional) Responds to ARP and SARP requests on this interface only if there are no other VINES servers present.
Defaults
The interface always responds to ARP and SARP requests.
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
Client systems on VINES networks are assigned network addresses dynamically. When a VINES client boots, it has no knowledge of their addresses and preferred servers. Immediately after it initializes its hardware interface, the client sends broadcast requests asking a server to provide it with a network-layer address. In a network that has a server, Cisco routers do not normally respond to these broadcast requests. However, on a network that has only clients and no servers (called a serverless network), the Cisco IOS software does need to respond to the broadcast requests so that all the clients on that serverless network can acquire network addresses. By default, the software responds to ARP requests and assigns addresses to network clients only if there is no VINES server present on that network segment. When it does, the software then acts as a network communication service provider for the client. You may configure the software to respond to these requests even if a VINES servers is present, or never to respond to these requests. If the software assigns an address, it generates a unique network number based on its own VINES address.
A VINES file server must still be present somewhere on the network in order for the client to continue the booting process.
Examples
The following example configures a router when Ethernet interface 1 is a network that does not contain any VINES servers:
interface ethernet 0 vines metric 2 ! interface ethernet 1 vines metric 2
The following example configures a router to always provide ARP service on Ethernet interface 1, even when VINES servers are present on that network:
interface ethernet 0 vines metric 2 ! interface ethernet 1 vines metric 2 vines arp-enable
Related Commands
Modifies how the Cisco IOS software forwards a broadcast packet. Configures a Banyan VINES network that does not have a server.
Command
Description
To display VINES addresses in decimal notation, use the vines decimal command in global configuration mode. To return to displaying the addresses in hexadecimal, use the no form of this command.
vines decimalSyntax Description
This command has no arguments or keywords.
Defaults
Addresses are displayed in hexadecimal.
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
When displaying addresses, the Cisco IOS software always uses a name if one has been configured via the vines enhancements command. The vines decimal command affects the radix in which the address is presented when a name is not available.
Examples
The following example displays VINES addresses in decimal:
vines decimal
Related Commands
clear vines cache Deletes entries from the VINES fast-switching cache. clear vines neighbor Deletes entries from the neighbor table. clear vines route Deletes network addresses from the routing table. show vines cache Displays the contents of the VINES fast-switching cache. Associates a host name with a VINES address.
Command
Description
To set the MAC-level encapsulation used for VINES broadcast packets, use the vines encapsulation command in interface configuration mode. To disable encapsulation, use the no form of this command.
vines encapsulation [arpa | snap | vines-tr]
Syntax Description
arpa (Optional) Advanced Research Projects Agency (ARPA) encapsulation. This is the default encapsulation for Ethernet interfaces. snap (Optional) Subnetwork Access Protocol (SNAP) encapsulation. This encapsulation uses an IEEE 802.2 SNAP header. It is the default encapsulation for all media except Ethernet and Token Ring. vines-tr (Optional) Our VINES Token Ring encapsulation. This is the default encapsulation for Token Ring interfaces.
Defaults
ARPA encapsulation for Ethernet
VINES-TR Token Ring encapsulation for Token Ring
SNAP encapsulation for all other media
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
You can choose a MAC-level encapsulation type for each Ethernet, Token Ring, or IEEE 802.2 interface.
Setting the MAC-level encapsulation type with the vines encapsulation command affects broadcast packets sent by the Cisco IOS software. The software keeps track of which encapsulation is used by each of its neighbors and uses the same style of encapsulation when talking directly to a neighbor.
You should not use this command with the current versions of VINES software that are available. This command is present for future interoperability when Banyan begins using encapsulations other than the current default ones.
Examples
The following example configures IEEE 802.2 SNAP encapsulation on Ethernet interface 0:
vines routing ! interface ethernet 0 vines metric 2 vines encapsulation snap
To enable split-horizon for routing updates and to generate flash updates, use the vines enhancements command in global configuration mode. To turn VINES enhancement off, use the no form of this command.
vines enhancementsSyntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The vines enhancements command applies only to non-sequenced RTP protocol and deals only with routing updates.
The vines enhancements command helps VINES enable split horizon when generating regular, periodic routing updates (routes learned from an interface are not advertised back to the same interface) and helps generates flash updates that are sent out to indicate topology changes for only the changed routes instead of full updates. Full updates are still sent periodically. When periodic or flash updates are sent out on a given interface, the updates do not include any information that was originally sent from that interface. This behavior is slightly different from the VINES server running pre-5.5.x Banyan VINES OS, which sends out the entire routing table in a flash update, even if only one route changed.
 |
Note For 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 entered. Split horizon remains enabled because vines split-horizon on individual VINES interface, in addition to controlling RTP updates, also controls whether or not retransmission of broadcasts is permitted on the receiving interface. |
Examples
The following example specifies the VINES enhancements:
vines routing vines enhancements
Related Commands
Uses split horizon when sending routing updates. Modifies the manner in which routing updates are sent. Modifies the frequency at which routing updates are sent.
Command
Description
To associate a host name with a VINES address, use the vines host command in global configuration mode. To delete the association, use the no form of this command.
vines host name address
Syntax Description
name VINES host name. It can be any length and sequence of characters separated by white space. address Number of a VINES network. You enter it in the current VINES radix, in the format network:host, where network is 4 bytes and host is 2 bytes.
Defaults
Hosts are displayed by address.
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The Cisco IOS software maintains a table of the mappings between host names and addresses.
When displaying addresses, the software uses the name instead of the numerical address if you have configured one with the vines host command.
Cisco IOS software provides only static name-to-address bindings for the VINES protocol. This is completely separate from Banyan's distributed naming system, StreetTalk. The software does not learn names from StreetTalk, nor does the software provide names to StreetTalk.
Examples
The following example assigns names to four VINES servers:
! Cisco names vines host FARSLAYER 30002A2D:0001 vines host DOOMGIVER 30000A83:0001 ! VINES PS/2 server vines host COINSPINNER 0027AF92:0001 ! PC clone client vines host STUFF 0027AF92:8001
Related Commands
clear vines neighbor Deletes entries from the neighbor table. clear vines route Deletes network addresses from the routing table. show vines host Displays the entries in the VINES host name table. Displays VINES addresses in decimal notation.
Command
Description
To filter the information contained in routing messages received from other stations, use the vines input-network-filter command in interface configuration mode. To disable this filtering, use the no form of this command.
vines input-network-filter access-list-number
Syntax Description
access-list-number Number of the access list. It is a decimal number from 201 to 300.
Defaults
No filtering.
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
VINES routing messages contain topological entries that allow service and client nodes to select the best paths to destinations. This command provides filtering ability to administrators so that they may selectively determine which routing entries should be accepted from other routers and which routing entries should be dropped. This command may be useful in enforcing administrative policies of local server usage.
Examples
The following example prevents a route to one specific server from ever being learned via Ethernet interface 0:
vines routing ! vines access-list 201 deny 27AF9A:1 0:0 vines access-list 201 permit 0:0 FFFFFFFF:FFFF ! interface ethernet 0 vines metric 2 vines input-network-filter 201
To filter received routing messages based upon the address of the sending station, use the vines input-router-filter command in interface configuration mode. To disable this filtering, use the no form of this command.
vines input-router-filter access-list-number
Syntax Description
access-list-number Number of the access list. It is a decimal number from 201 to 300.
Defaults
No filtering.
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
VINES routing messages contain topological entries that allow service and client nodes to select the best paths to destinations. This command provides filtering ability to administrators so that they may selectively determine the routers from which routing entries are accepted.
Examples
The following example prevents the Cisco IOS software from ever learning routing information from a specific server on Ethernet interface 0:
vines routing ! vines access-list 201 deny 27AF9A:1 0:0 vines access-list 201 permit 0:0 FFFFFFFF:FFFF ! interface ethernet 0 vines metric 2 vines input-router-filter 201
To enable VINES routing on an interface, use the vines metric command in interface configuration mode. To disable VINES routing, use the no form of this command.
vines metric [whole [fractional]]
Syntax Description
whole (Optional) Integer cost value associated with the interface. It is optional for all interface types. If you omit whole, the Cisco IOS software automatically chooses a reasonable value. These values are listed in Table 19 in the "Usage Guidelines" section. For additional information, refer to the discussion and to Table 17. If whole is zero, then a fractional portion must be supplied. fractional (Optional) Fractional cost value associated with the interface expressed in 10,000ths. It is optional for all interface types, but may only be present if a whole number portion is specified. This number is rounded to the nearest 1/16. If you omit both whole and fractional numbers, the software automatically chooses a reasonable value. These values are listed in Table 19. For additional information, refer to the discussion in the "Usage Guidelines" section and to Table 17.
Defaults
Disabled
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The metric is the cost value associated with the interface media type. It is generally inversely proportional to the speed of the interface. The lower the delay metric, the more likely it is that the software will use that interface.
The Cisco IOS software automatically chooses a reasonable metric. These numbers match as closely as possible the numbers a Banyan server would choose for an interface of the same type and speed.
When enabling VINES for a serial interface, you should keep in mind that the VINES metric is based upon the configured bandwidth for the interface. To ensure that the software selects the correct VINES metric, you must make sure that the correct bandwidth is configured. To do this, first issue the show interface command to determine the speed of the interface. Then issue the bandwidth command to set the bandwidth rate that is appropriate for that interface type and speed. After that, issue the vines metric command and the software will choose a metric appropriate to that speed. If you do not issue the bandwidth command first, you must either reissue the vines metric command or issue it with a metric number to get an appropriate metric.
Banyan servers use these metrics to compute timeouts when communicating with other hosts. If you do specify a metric, be careful that you do not set this number too high or too low. Doing so could disrupt the normal function of the Banyan servers.
Table 19 lists some example delay metric values.
| Interface Type | Old Format | New Internal Format | New Configuration File Format | Seconds |
|---|---|---|---|---|
FDDI | 1 | 0010 | 1 0000 | 0.2000 |
Ethernet | 2 | 0020 | 2 0000 | 0.4000 |
16-Mb Token Ring | 2 | 0020 | 2 0000 | 0.4000 |
4-Mb Token Ring | 4 | 0040 | 4 0000 | 0.8000 |
T1 High-Level Data Link Control (HDLC) | 35 | 0230 | 35 0000 | 7.0000 |
56-kb HDLC | 45 | 02D0 | 45 0000 | 9.0000 |
9600-baud HDLC | 90 | 05A0 | 90 0000 | 18.0000 |
4800-baud HDLC | 150 | 0960 | 150 0000 | 30.0000 |
2400-baud HDLC | 250 | 0F00 | 250 0000 | 50.0000 |
1200-baud HDLC | 450 | 1C20 | 450 0000 | 90.0000 |
T1 X.25 | 45 | 02D0 | 45 0000 | 9.0000 |
56-kb X.25 | 55 | 0370 | 55 0000 | 11.0000 |
9600-baud X.25 | 100 | 0640 | 100 0000 | 20.0000 |
4800-baud X.25 | 160 | 0A00 | 160 0000 | 32.0000 |
2400-baud X.25 | 260 | 1040 | 260 0000 | 52.0000 |
1200-baud X.25 | 460 | 1CC0 | 460 0000 | 92.0000 |
Examples
The following example enables VINES routing on Ethernet interface 0 and sets the metric to 2:
vines routing ! interface ethernet 0 vines metric 2
The following example enables VINES routing on FDDI interface 0 and sets the metric to 0.25:
vines routing ! interface fddi 0 vines metric 0 2500
Related Commands
bandwidth Sets a bandwidth value for an interface. Enables VINES routing. Modifies the manner in which routing updates are sent. Modifies the frequency at which routing updates are sent.
Command
Description
To specify a static path to a neighbor station, use the vines neighbor command in interface configuration mode. To remove a static path from the neighbor table, use the no form of this command.
vines neighbor address mac-address encapsulation [whole [fractional]]
Syntax Description
address VINES IP address of the station to which to add or remove a static path. mac-address MAC-level address used to reach the neighbor station. encapsulation Encapsulation type to use on the media. It can be one of the following values: whole (Optional) Delay metric to use on the neighbor. If you omit this argument, the metric used is that specified with the vines metric command for the selected interface. fractional (Optional) Fractional metric value associated with this neighbor. This number is rounded to the nearest 1/16. If you omit both whole and fractional numbers, the interface metric is used.
Defaults
No static paths are specified.
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
You can configure static neighbor entries only on Ethernet, FDDI, and Token Ring interfaces.
The decision to use a static path or a dynamic path is always determined by the relative metric numbers.
Be careful when assigning static paths. If a static path is assigned with a better metric than the dynamic paths and the link associated with the static path is lost, traffic may stop being forwarded, even though an alternative path might be available.
The metric is the cost value associated with the interface media type. It is generally inversely proportional to the speed of the interface. The lower the delay metric, the more like it is that the software will use that interface.
This command is useful for testing VINES networks with test equipment that does not generate hello packets.
See Table 19 earlier in this chapter for examples of delay metric values.
Examples
The following example defines a static path to the neighbor station at address 12345678:0001 using ARPA encapsulation:
interface ethernet 0 vines neighbor 12345678:0001 0001.0002.0003 arpa 20
Related Commands
clear vines neighbor Deletes entries from the neighbor table. show vines neighbor Displays the entries in the VINES neighbor table. show vines route Displays the contents of the VINES routing table. Specifies a static route to a server.
Command
Description
To filter the information contained in routing updates transmitted to other stations, use the vines output-network-filter command in interface configuration mode. To disable this filtering, use the no form of this command.
vines output-network-filter access-list-number
Syntax Description
access-list-number Number of the access list. It is a decimal number from 201 to 300.
Defaults
No filtering.
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
VINES routing messages contain topological entries that allow service and client nodes to select the best paths to destinations. This command provides filtering ability to administrators so that they may selectively determine which routing entries should be passed on to other routers. This command may be useful in enforcing administrative policies of local server usage.
Examples
The following example prevents all routes from being advertised to Ethernet interface 0 except the route to a single server:
vines routing ! vines access-list 201 permit 27AF9A:1 0:0 vines access-list 201 deny 0:0 FFFFFFFF:FFFF ! interface ethernet 0 vines metric 2 vines output-network-filter 201
To modify how the Cisco IOS software forwards a broadcast packet, use the vines propagate command in interface configuration mode. To return to the default forwarding scheme, use the no form of this command.
vines propagate [dynamic]
Syntax Description
dynamic (Optional) Propagate broadcasts on this interface only if there are no servers on any local network.
Defaults
Dynamic forwarding.
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
If you specify the vines propagate command with no keywords, broadcast messages are always propagated on the interface.
The vines propagate command affects how the software decides whether to forward a broadcast packet out an interface. The normal decision is based on the settings of both the "hop count" and "class" fields of the VINES IP header, and also whether any servers are present on any of the local network segments. In the default configuration, the software first looks to see if there are any local servers, and if so, follows the normal rules of VINES IP and forwards the broadcast out this interface based upon the "hop count" and the "class" field. If there are no local servers, then the software looks only at the "hop count" field before forwarding the broadcast out this interface. Enabling this command with no argument tells the software to always ignore the "class" field and make the forwarding decision based solely upon the "hop count" field. The no form of this command tells the software to always examine both the "hop count" and "class" fields.
Examples
The following example always ignores the "class" field of the VINES IP header when deciding whether to forward a broadcast packet on serial interface 0:
interface serial 0 vines propagate
Related Commands
Enables the processing of ARP packets. Configures a Banyan VINES network that does not have a server.
Command
Description
To determine how frequently the Cisco IOS software sends an RTP redirect message on an interface, use the vines redirect command in interface configuration mode. To restore the default, use the no form of this command.
vines redirect [seconds]
Syntax Description
seconds (Optional) Interval, in seconds, that the software waits after sending a redirect message on an interface before it sends another redirect message on that same interface. If you specify a value of 0, the software never sends redirect messages on that interface.
Defaults
1 second
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
VINES routing redirect packets contain topological entries that allow service and client nodes to select the best paths to destinations. When a service node determines that it should not be forwarding packets between two nodes, it sends a redirect packet to the sending node informing it of the better path.
Examples
The following example prevents redirect messages from ever being sent on Ethernet interface 0:
vines routing ! interface ethernet 0 vines metric 2 vines redirect 0
To specify a static route to a server, use the vines route command in global configuration mode. To remove a static route from the routing table, use the no form of this command.
vines route number address [whole [fractional]]
Syntax Description
number Number of the server to which to add or remove the static route. address VINES IP address of the neighbor station to use to reach the server. whole (Optional) Metric value assigned to this route. fractional (Optional) Fractional cost value associated with this route.
Defaults
No static routes are specified.
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The decision to use a static route or a dynamic route is always determined by the relative metric numbers.
Be careful when assigning static routes. If a static route is assigned with a better metric than the dynamic routes and the links associated with the static routes are lost, traffic may stop being forwarded, even though an alternative route might be available.
To configure a floating static route, assign a metric to the static route that is worse (higher) than all dynamic routes. If you configure a floating static route, the Cisco IOS software checks to see if an entry for the route already exists in its routing table. If a dynamic route already exists, the floating static route is placed in reserve as part of a floating static route table. When the software detects that the dynamic route is no longer available, it replaces the dynamic route with the floating static route for that destination. If the route is later relearned dynamically, the dynamic route replaces the floating static route and the floating static route is again placed in reserve.
|
Note By default, floating static routes are not redistributed into other dynamic protocols. |
Examples
The following example establishes a static route to the server at ABCD1234:
vines route ABCD1234 12345678:1 35
The following example establishes a floating static route to the server at 3000000:
vines route 3000000 3001000:1
Related Commands
clear vines neighbor Deletes entries from the neighbor table. clear vines route Deletes network addresses from the routing table. show vines neighbor Displays the entries in the VINES neighbor table. show vines route Displays the contents of the VINES routing table. Specifies a static path to a neighbor station. Filters the information contained in routing updates sent to other stations.
Command
Description
To enable fast switching, use the vines route-cache command in interface configuration mode. To disable fast switching, use the no form of this command.
vines route-cacheSyntax Description
The command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The vines route-cache command enables the fast switching of VINES packets being transmitted out of the interface. However, forwarding of broadcast packets and responding to packets destined for the local router still occurs at the process level. When fast switching is disabled, all packets are forwarded at the process level.
Fast switching allows higher throughput by switching a packet using a cache created by previous packets. Fast switching provides load sharing on a per-packet basis just as slow switching does. Fast switching is enabled by default on all interfaces where it is supported. It is not supported on very old Ethernet, serial, and Token Ring interfaces, nor is it supported on serial interfaces using an encapsulation other than HDLC.
Packet transfer performance is generally better when fast switching is enabled. However, you may want to disable fast switching in order to save memory space on interface cards and help avoid congestion when high-bandwidth interfaces are writing large amounts of information to low-bandwidth interfaces.
When fast switching is enabled, the Cisco IOS software maintains a fast-switching cache table. When transmitting a packet that is eligible to be fast switched, the software first checks the fast-switching cache table. If it finds an entry for the destination, the software uses that path. Otherwise, it searches the standard routing table and places the route it finds into the fast-switching cache table. The next time the software receives a packet for that destination, it uses the route in the fast-switching cache table.
Examples
The following example disables fast switching on serial interface 0:
interface serial 0 bandwidth 19200 vines metric no vines route-cache
Related Commands
clear vines cache Deletes entries from the VINES fast-switching cache. show vines cache Displays the contents of the VINES fast-switching cache. show vines route Displays the contents of the VINES routing table.
Command
Description
To enable VINES routing, use the vines routing command in global configuration mode. To disable VINES routing, use the no form of this command.
vines routing [address | recompute]
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
Enabling VINES routing with the vines routing command starts both the VINES RTP and SRTP protocols. The Cisco IOS software dynamically determines which version of the VINES routing protocol stations on the network are using and then uses one or the other, or both protocols, as appropriate.
If a router contains Ethernet or FDDI interfaces, you do not need to specify an address because the Cisco IOS software automatically maps itself into the VINES address space that is reserved for Cisco routers. If you do specify an address, the software will use the specified address.
If a router contains only Token Ring interfaces (or Token Ring and serial interfaces), either the Token Ring interface must be fully initialized before you issue the vines routing command or you must specify an address in the vines routing command. This is because Token Ring interfaces have MAC addresses of 0000.0000.0000 until they are fully initialized.
Banyan has assigned Cisco a portion of the overall VINES network number space. This portion is the set of all numbers that begin with the first 11 bits (of the 32) of 0011 0000 000. This number set appears in all Cisco IOS software displays as a hexadecimal number beginning with 0x300 or 0x301. Devices attempt to automatically map themselves into our number space based upon the first nonzero Ethernet, Token Ring, or FDDI address found.
In theory, address conflicts are impossible, because VINES servers use their Banyan-assigned, unique key serial numbers as their network numbers and use a subnetwork number of one. Because the keys are unique, the server addresses are unique. VINES clients do not have addresses, per se. The clients use a modified version of the address of the first file server found on the physical network: they assume the server's network number and are assigned a subnetwork number by that server. This address-assignment scheme means that it is likely that two clients on the same physical LAN will have different addresses. It requires that the Cisco IOS software keep a cache of local neighbors as well as a cache of routing entries.
If you do not specify a network address and the software cannot compute one from a MAC address, the software selects a random address. There is no guarantee that this will be a unique address.
If you find that two routers have the same VINES network address, you should issue the vines routing recompute command on both routers. When recomputing its address, the software uses the same method used when originally determining its network address. If you issue this command on a router on which you have enabled the processing of ARP packets (with the vines arp-enable command) and if the device's address changes when it is recomputed, any clients that received their VINES network addresses from the router will lose all network connectivity, and you will have to reboot them.
Older implementations of our software mapped themselves to numbers beginning with 0xF80. This was done before Banyan made the address assignment.
Examples
The following example enables VINES routing on Ethernet interface 0:
vines routing ! interface ethernet 0 vines metric 2
Related Commands
Enables the processing of ARP packets. Enables VINES routing on an interface. Maintains only one route per server.
Command
Description
To configure a Banyan VINES network that does not have a server, use the vines serverless command in interface configuration mode. To disable this feature, use the no form of this command.
vines serverless [dynamic | broadcast]
Syntax Description
dynamic (Optional) Forward broadcasts toward one server only if there are no servers present on this interface. broadcast (Optional) Always flood broadcasts out all other router interfaces to reach all servers.
Defaults
Dynamic forwarding.
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
If all keywords are omitted, broadcasts are always forwarded toward one server.
The vines serverless command provides special processing for certain broadcast packets and certain packets directed at the router.
When you have a Banyan VINES network that has no server, by default the Cisco IOS software provides special processing for certain broadcast packets and certain packets directed at the router. This is necessary for proper functioning of the clients on a network without a server. This special processing allows a client to find the services that are provided by a server on another network. The dynamic nature of this processing allows the software to switch over from not providing serverless support to providing serverless support if the last server on a network fails. If you want the router to always provide serverless support, even when there are local servers present, you may override the default processing by issuing the vines serverless command with no argument. If you do not want the router to ever provide serverless support, you may also override the default in this way by issuing the no vines serverless command.
When the Cisco IOS software receives a zero-hop broadcast on a serverless network, it does not follow the normal processing rules for VINES packets and discard the frames. Instead, it looks in its routing table for the nearest Banyan server. If this server is on a directly connected network, the software resends the broadcast message on that network as a MAC-level broadcast so that server and any others present can respond to it. If the nearest Banyan server is not on a directly connected network, the software resends the broadcast message on that network as a MAC-level unicast message directed at the first hop to that server. The next router will perform these same steps, assuming it is also configured for serverless support. The router can also be configured to always flood these broadcasts on all interfaces by using the command vines serverless broadcast. The decision on whether or not to flood is a trade-off between network bandwidth and finding more servers.
If you have configured this interface to forward toward a single destination, you may see which server has been selected as the forwarding target by looking at the output of the show vines route command. All servers on the same physical network as the target server receive the broadcast.
Examples
The following example configures Ethernet interface 1, which is a network with no VINES servers:
interface ethernet 0 vines metric 2 ! interface ethernet 1 vines metric 2
The vines serverless command is not necessary because the default setting is what is desired.
The following example configures Ethernet interface 1, which is a network with no VINES servers to always flood broadcasts to all other interfaces in the router:
interface ethernet 0 vines metric 2 ! interface ethernet 1 vines metric 2 vines serverless broadcast
The vines serverless command is necessary here because a nondefault setting is desired.
Related Commands
show vines route Displays the contents of the VINES routing table. Enables the processing of ARP packets. Modifies how the Cisco IOS software forwards a broadcast packet.
Command
Description
To maintain only one route per server, use the vines single-route command in global configuration mode. To allow multiple routes per server, use the no form of this command.
vines single-route
no vines single route
Syntax Description
This command has no arguments or keywords.
Defaults
Multiple routes
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
VINES servers and clients do not handle out-of-sequence packets well. If a VINES connection experiences slow performances due to low window size, enable the vines single-route command. This command can be enabled at any time after VINES routing has been enabled.
Examples
The following example specifies the VINES single route:
vines routing
vines single-route
Related Commands
Enables VINES routing.
Command
Description
To use split horizon when sending routing updates, use the vines split-horizon command in interface configuration mode. To disable split horizon, use the no form of this command.
vines split-horizonSyntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The vines split-horizon command also affects whether broadcasts packets received on an interface are resent on the same interface. If enabled, broadcasts will not be resent on the same interface.
The vines split-horizon command determines how much information is included in routing updates sent out on an interface. It also determines whether received broadcasts are retransmitted on the same interface. When you enable split horizon, routing updates sent out on a given interface will not include any information that was originally learned from that interface, and broadcasts will not be retransmitted on the receiving interface. This is because split horizon is designed for networks that are either broadcast networks, or are fully connected mesh networks. In these types of networks, resending this information is a waste of network bandwidth because all other stations on that network have already heard the information. Disabling split horizon causes the Cisco IOS software to include all information in routing updates, and to resend broadcast packets on the network from which they were received.
|
Note 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 entered. Split horizon remains enabled because vines split-horizon on individual VINES interface, in addition to controlling RTP updates, also controls whether or not retransmission of broadcasts is permitted on the receiving interface. |
You can use this command on any interface, but generally it makes sense to use it only for X.25 and Frame Relay interfaces. You should disable split horizon on X.25 and Frame Relay networks that are not fully connected mesh topologies.
Examples
The following example disables split horizon on an X.25 network:
interface serial 0 no vines split-horizon
Related Commands
Enables split-horizon for routing updates and to generate flash updates.
Command
Description
To enable SRTP, use the vines srtp-enabled command in global configuration mode. To disable SRTP, use the no form of this command.
vines srtp-enabledSyntax Description
This command has no arguments or keywords.
Defaults
The router runs Banyan's RTP routing protocol only.
Command Modes
Global configuration
Command History
10.3 This command was introduced.
Release
Modification
Usage Guidelines
When SRTP is enabled, the Cisco IOS software dynamically determines whether it needs to send RTP messages, SRTP messages, or both.
Examples
The following example enables SRTP:
interface serial 0 vines routing vines srtp-enabled
Related Commands
Enables VINES routing.
Command
Description
To control the servers from which the router will accept VINES network time, use the vines time access-group command in global configuration mode. To accept VINES network time messages from any server, use the no form of this command.
vines time access-group access-list-number
Syntax Description
access-list-number Number of the access list. It is a decimal number from 201 to 300.
Defaults
Disabled
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Examples
The following example applies an access list to incoming time messages:
vines access-list 201 permit 27AF9A:1 0:0 vines access-list 201 deny 0:0 FFFFFFFF:FFFF ! vines time participate vines time access-group 201
Related Commands
show vines service Displays information about the application layer support. Creates a simple VINES access list. Controls the servers to which the Cisco IOS software sends VINES network time. Enables participation in synchronizing time across a VINES network. Enables the Cisco IOS to provide time services for VINES clients and enables participation in the synchronization of time across a VINES network. Sets VINES network time based on the internal time.
Command
Description
To control the servers to which the Cisco IOS software sends VINES network time, use the vines time destination command in global configuration mode. To send VINES network time messages to all servers, use the no form of this command.
vines time destination address
Syntax Description
address Destination VINES address for the network time messages.
Defaults
Disabled
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
By default, the software sends VINES network time messages to the broadcast address.
You can enter the vines time destination command up to 20 times for 20 destination addresses.
Examples
The following example specifies the servers to receive VINES time messages:
vines time participate vines time destination 0027AF9F:0001 vines time destination 300001239:001
Related Commands
show vines service Displays information about the application layer support. Controls the servers from which the router will accept VINES network time. Enables participation in synchronizing time across a VINES network. Enables the Cisco IOS to provide time services for VINES clients and enables participation in the synchronization of time across a VINES network. Sets VINES network time based on the internal time.
Command
Description
To enable participation in synchronizing time across a VINES network, use the vines time participate command in global configuration mode. To disable this participation, use the no form of this command.
vines time participateSyntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The Cisco IOS software listens to time-synchronization messages on the network and tracks the network time. This command controls only the sending of time-synchronization messages by the software. Thus you can use the show vines service EXEC command to see the network time, even if the router is not actively participating in time synchronization.
 |
Caution The use of the vines time services global configuration command can affect the behavior of this command. Refer to the vines time services command for more information. |
Examples
The following example disables participation in the sending of VINES time messages:
no vines time participate
Related Commands
show vines service Displays information about the application layer support. Creates a simple VINES access list. Applies an access list to an interface. Controls the servers to which the Cisco IOS software sends VINES network time. Enables the Cisco IOS to provide time services for VINES clients and enables participation in the synchronization of time across a VINES network. Sets the internal time based on the received VINES network time. Sets VINES network time based on the internal time.
Command
Description
To enable the Cisco IOS to provide time services for VINES clients and to enable participation in the synchronization of time across a VINES network, use the vines time services command in global configuration mode. To disable participation in time synchronization and services, use the no form of this command.
vines time servicesSyntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Command History
11.0(21) This command was introduced.
Release
Modification
Usage Guidelines
By default the Cisco IOS software participates in sending and listening to time-synchronization messages on the network. If participation is disabled via the no form of this command, the Cisco IOS software will neither listen to nor send time-synchronization messages to the network.
|
Caution To enable participation in synchronizing time across a VINES network, use the vines time participate global configuration command in conjunction with the vines time services command. If you use the no vines time services command, all time services and synchronization will be automatically disabled, even if you have issued the vines time participate separately. |
Examples
The following example disables participation in the sending of VINES time messages and services:
no vines time services
Related Commands
show vines service Displays information about the application layer support. Creates a simple VINES access list. Applies an access list to an interface. Controls the servers to which the Cisco IOS software sends VINES network time. Enables participation in synchronizing time across a VINES network. Sets the internal time based on the received VINES network time. Sets VINES network time based on the internal time.
Command
Description
To set the internal time based upon the received VINES network time, use the vines time set-system command in global configuration mode. To uncouple the time from VINES network time, use the no form of this command.
vines time set-systemSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
You should not use the vines time set-system command when running NTP on a router, because this command has no effect on these systems. NTP is considered to be a higher-priority clock than VINES, because it is a much more accurate timekeeping system.
Examples
The following example sets the time from received VINES time messages:
vines time participate vines time set-system
Related Commands
show vines service Displays information about the application layer support. Creates a simple VINES access list. Controls the servers to which the Cisco IOS software sends VINES network time. Enables participation in synchronizing time across a VINES network. Sets VINES network time based on the internal time.
Command
Description
To set VINES network time based on the internal time, use the vines time use-system command in global configuration mode. To uncouple VINES network time from the time, use the no form of this command.
vines time use-systemSyntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The vines time use-system command causes the Cisco IOS software to import the locally available time source (such as NTP, the calendar system, or DNSIX time) into the VINES time world as an authoritative clock. This is most useful when running NTP on the router. The router appears to the VINES network as a server dialing the NIST clock.
When you specify the vines time use-system command, VINES extracts the system time and propagates it into the VINES world only if the system time is valid. If you are running NTP, the system time becomes valid when NTP synchronizes with a master. If you are not running NTP, but you do have an internal calendar system, you can force that time to be valid by specifying the clock calendar-valid command. This allows VINES to propagate time based upon the clock chip of the calendar system.
Examples
The following example sets VINES network time from the router's internal time:
ntp peer 131.108.13.111 version 2 ! vines time participate vines time use-system
Related Commands
clock calendar-valid Configures a router as a time source for a network based on its calendar. show vines service Displays information about the application layer support. Creates a simple VINES access list. Controls the servers from which the router will accept VINES network time. Controls the servers to which the Cisco IOS software sends VINES network time. Sets VINES network time based on the internal time. Enables the Cisco IOS to provide time services for VINES clients and enables participation in the synchronization of time across a VINES network.
Command
Description
To modify the manner in which routing updates are sent, use the vines update deltas command in interface configuration mode. To return to the default method, use the no form of this command.
vines update deltasSyntax Description
This command has no arguments or keywords.
Defaults
No deltas
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The vines update deltas command significantly modifies the way that routing information is propagated across the network.
On LAN media, using this command causes the Cisco IOS software to stop transmitting and to stop expecting periodic routing updates. Instead, the software transmits and expects a periodic hello message. The difference between these two messages is whether routing information is included. The software continues to send flash updates to inform its neighbors of any changes to current routing table information. This is the same frequency and type of routing updates used on LANs by VINES version 5.50, but Cisco's packet format differs from the VINES format.
On WAN media, using this command causes the software to transmit three normally spaced routing updates and then cease transmission. The software does not send periodic hello messages. The software will, however, continue to send flash updates to inform its neighbors of any changes to current routing table information. This is the same frequency and type of routing updates used on LANs by all versions of VINES, but Cisco's packet format differs from the VINES format.
Examples
The following example modifies the propagation of routing update information on the WAN interface connected to serial interface 0:
interface serial 0 vines metric vines update deltas
Related Commands
show vines interface Displays status of the VINES interfaces configured in the Cisco IOS software and the parameters configured on each interface. show vines neighbor Displays the entries in the VINES neighbor table. show vines route Displays the contents of the VINES routing table. Enables VINES routing on an interface.
Command
Description
To modify the frequency at which routing updates are sent, use the vines update interval command in interface configuration mode. To return to the default frequency, use the no form of this command.
vines update interval [seconds]
Syntax Description
seconds (Optional) Interval, in seconds, between the sending of periodic VINES routing updates. This can be a number in the range 0 to 232 and is rounded up to the nearest 5 seconds. The default value is 90 seconds. If you omit seconds or specify a value of 0, the default value of 90 seconds is used.
Defaults
90 seconds
Command Modes
Interface configuration
Command History
10.0 This command was introduced.
Release
Modification
Usage Guidelines
The vines update interval command controls the interval at which the Cisco IOS software sends routing updates. The routing update interval should be the same on all VINES-speaking entities on the same physical network.
For networks on which other vendors' entities are present, it is safe to use any setting in the range 30 to 100 seconds on networks. This is the range of update intervals supported by Banyan servers. You should use values outside of this range (with the exception of zero) only on networks that contain only Cisco routers. You can use a value of zero on networks with only Cisco routers or on WAN links connecting Cisco routers and Banyan servers. In this configuration, you must also address application-level security requirements.
For Banyan VINES sites that support "change-only" updates on LAN networks, you can use the vines update interval command in LAN networks with both Cisco routers and Banyan servers.
Examples
The following example sets the update interval on serial interface 0 to a value of 270 seconds:
interface serial 0 vines metric vines update interval 270
Related Commands
show vines interface Displays status of the VINES interfaces configured in the Cisco IOS software and the parameters configured on each interface. show vines neighbor Displays the entries in the VINES neighbor table. show vines route Displays the contents of the VINES routing table. Enables VINES routing on an interface.
Command
Description
Posted: Thu Mar 16 21:24:28 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.