Avaya VINES User Manual
Configuring VINES
Services
BayRS V ersion 12.00
Site Manager Software Version 6.00
Part No. 117372-A Rev. A
September 1997
4401 Great America Parkway 8 Federal Street
Santa Clara, CA 95054 Billerica, MA 01821
Copyright © 1997 Bay Networks, Inc.
All rights reserved. Printed in the USA. September 1997.
The information in this document is subject to change without notice. The statements, configurations, technical data,
and recommendations in this document are believed to be accurate and reliable, but are presented without express or
implied warranty . Users must take full responsibility for their applications of an y products specified in this document.
The information in this document is proprietary to Bay Networks, Inc.
The software described in this document is furnished under a license agreement and may only be used in accordance
with the terms of that license. A summary of the Software License is included in this document.
Trademarks
ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, Optivity, PPX, Bay Networks, SynOptics,
SynOptics Communications, Wellfleet and the Wellfleet logo are registered trademarks and Advanced Remote Node,
ANH, ARN, ASN, Bay•SIS, BayStack, BayStream, BCNX, BLNX, EZ Install, EZ Internetwork, EZ LAN,
IP AutoLearn, PathMan, PhonePlus, Quick2Config, RouterMan, SN, SPEX, Switch Node, Bay Networks Press,
the Bay Networks logo and the SynOptics logo are trademarks of Bay Networks, Inc.
All other trademarks and registered trademarks are the property of their respective owners.
Restricted Rights Legend
Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer
software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in
the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.
Statement of Conditions
In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the
right to make changes to the products described in this document without notice.
Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or
circuit layout(s) described herein.
Portions of the code in this software product are Copyright © 1988, Regents of the Univ ersity of California. All rights
reserved. Redistribution and use in source and binary forms of such portions are permitted, provided that the above
copyright notice and this paragraph are duplicated in all such forms and that any documentation, advertising materials,
and other materials related to such distribution and use acknowledge that such portions of the software were
developed by the University of California, Berkeley. The name of the University may not be used to endorse or
promote products derived from such portions of the software without specific prior written permission.
SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
In addition, the program and information contained herein are licensed only pursuant to a license agreement that
contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed
by third parties).
ii
117372-A Rev. A
Bay Networks, Inc. Software License Agreement
NOTICE:
installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement).
BY COPYING OR USING THE SOFTWARE, YOU A CCEPT ALL OF THE TERMS AND CONDITIONS OF THIS
LICENSE A GREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER
WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and
conditions, return the product, unused and in the original shipping container, within 30 days of purchase to obtain a
credit for the full purchase price
1. License Grant.
nonexclusive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single
authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup
purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in
support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend
to Bay Networks Agent software or other Bay Networks software products. Bay Networks Agent software or other
Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software
License Agreement that accompanies such software and upon payment by the end user of the applicable license fees
for such software.
2. Restrictions on use; reservation of rights.
Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any
revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any
copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use
for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user
manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or
transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and
its licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise
disclose to any third party the Software, or any information about the operation, design, performance, or
implementation of the Software and user manuals that is confidential to Bay Networks and its licensors; however,
Licensee may grant permission to its consultants, subcontractors, and agents to use the Software at Licensee’s f acility,
provided they have agreed to use the Software only in accordance with the terms of this license.
3. Limited warranty.
installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function
substantially as described in its accompanying user manual during its warranty period, which begins on the date
Software is first shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole
remedy Bay Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be
included in a future Software release. Bay Networks further warrants to Licensee that the media on which the
Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days
from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is
returned to Bay Networks during the warranty period along with proof of the date of shipment. This warranty does not
apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility
for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained
from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the
Licensee’s requirements, b) that the Software will operate in the hardw are or software combinations that the Licensee
may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the
operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot
be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered,
except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’ s product,
resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE
FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL
OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of
Please carefully read this license agreement before copying or using the accompanying software or
Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal,
The Software and user manuals are protected under copyright laws.
Bay Networks warrants each item of Software, as delivered by Bay Networks and properly
117372-A Rev. A
iii
its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or
altered files, data, or programs.
4. Limitation of liability.
COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR
PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN
IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT
SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT
EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.
5. Government Licensees.
by or on behalf of the United States Government. The Software and documentation are commercial products, licensed
on the open market at market prices, and were developed entirely at private expense and without the use of any U.S.
Government funds. The license to the U.S. Gov ernment is granted only with restricted rights, and use, duplication, or
disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial
Computer Software––Restricted Rights clause of F AR 52.227-19 and the limitations set out in this license for civilian
agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS
252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable.
6. Use of Software in the European Community.
European Community. If Licensee uses the Software within a country in the European Community, the Software
Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the
examination of the Software to facilitate interoperability. Licensee agrees to notify Bay Networks of any such
intended examination of the Software and may procure support and assistance from Bay Networks.
7. Term and termination.
Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the
Bay Networks copyright; those restrictions relating to use and disclosure of Bay Networks’ confidential information
shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if
Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason,
Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay
Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.
8. Export and Re-export.
or information without first obtaining any required export licenses or other governmental approvals. Without limiting
the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first
obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert
any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports
are restricted or embargoed under United States export control laws and regulations, or to any national or resident of
such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any
military end user or for any military end use, including the design, development, or production of any chemical,
nuclear, or biological weapons.
9. General.
jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement
will be governed by the laws of the state of California.
Should you have any questions concerning this Agreement, contact Bay Netw orks, Inc., 4401 Great America P arkway,
P.O. Box 58185, Santa Clara, California 95054-8185.
LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND
AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS
AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND
LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND
COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS
AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY
NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN
EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.
If any provision of this Agreement is held to be invalid or unenforceable by a court of competent
IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY
This provision applies to all Software and documentation acquired directly or indirectly
This provision applies to all Software acquired for use within the
This license is effective until terminated; however, all of the restrictions with respect to
Licensee agrees not to export, directly or indirectly, the Software or related technical data
iv
117372-A Rev. A
Contents
About This Guide
Before You Begin .............................................................................................................. xi
Conventions ......................................................................................................................xii
Acronyms .........................................................................................................................xiii
Ordering Bay Networks Publications ...............................................................................xiii
Bay Networks Customer Service .....................................................................................xiv
How to Get Help ..............................................................................................................xiv
Chapter 1
VINES Overview
VINES Networks .............................................................................................................1-1
VINES Architecture ..................................................................................................1-2
VINES Network Addressing .....................................................................................1-4
How the Router for VINES Services Works ....................................................................1-6
VINES Data Link Protocols ......................................................................................1-7
VINES Routing Protocols .........................................................................................1-8
VINES Internet Protocol ....................................................................................1-8
VINES Nonsequenced Routing Update Protocol ............................................1-10
VINES Sequenced Routing Update Protocol ..................................................1-14
VINES Nonsequenced Address Resolution Protocol ......................................1-15
VINES Sequenced Address Resolution Protocol ............................................1-16
VINES Internet Control Protocol ......................................................................1-16
For More Information ....................................................................................................1-17
Chapter 2
VINES Implementation Notes
Enabling VINES on a Synchronous Line ........................................................................2-1
Using the Inverse Address Resolution Protocol for VINES
Internet Address Resolution ...........................................................................................2-2
Assigning a Network ID to Your Router ...........................................................................2-2
117372-A Rev. A
v
Configuring Routers for Serverless Network Segments .................................................2-2
VINES Security Limitation for Serverless Network Segments .................................2-3
Configuring Routers for Multiple-Hop Topologies ...........................................................2-3
Configuring Routers to Source Route over Token Ring Networks ..................................2-4
Making the Transition from Bridging VINES to Routing VINES .......................................2-5
Fragmentation Protocol and VINES Performance ..........................................................2-7
Help Thy Neighbor Support ............................................................................................2-7
Using Multipath with Load Sharing .................................................................................2-8
Partially Meshed Frame Relay Network Support ............................................................2-8
Avoiding Address Numbering Problems in LNs and CNs ...............................................2-9
Chapter 3
Enabling VINES Services
Enabling VINES on an Interface .....................................................................................3-1
Chapter 4
Editing VINES Parameters
Accessing VINES Parameters ........................................................................................4-2
Editing VINES Global Parameters ............................................................................4-3
VINES Global Parameter Descriptions ..............................................................4-3
Editing VINES Interface Parameters ........................................................................4-7
VINES Interfaces Parameter Descriptions .........................................................4-8
Deleting VINES from the Router ...................................................................................4-14
Appendix A
VINES Default Settings
Index
vi
117372-A Rev. A
Figures
Figure 1-1. VINES Server and Its Clients ...................................................................1-2
Figure 1-2. VINES Network ........................................................................................1-5
Figure 1-3. VINES Internet Address Format ..............................................................1-6
Figure 1-4. VINES Fragmentation Protocol Header ...................................................1-7
Figure 1-5. VINES Internet Protocol Header ..............................................................1-9
Figure 1-6. VINES Nonsequenced Routing Update Protocol Header ......................1-11
Figure 1-7. VINES Nonsequenced Address Resolution Protocol Header ................1-15
Figure 1-8. VINES Internet Control Protocol Header ...............................................1-16
Figure 2-1. Routers Configured on a Serverless Network Segment ..........................2-3
Figure 2-2. Source Routing across a Token Ring Network .........................................2-5
Figure 2-3. Configuring Multiple Loops in a Bridged Environment .............................2-6
Figure 3-1. Edit Interface Details Window ..................................................................3-2
Figure 3-2. Edit Connector Window ............................................................................3-3
Figure 3-3. Edit SYNC Parameters Window ...............................................................3-3
Figure 4-1. Configuration Manager Window ...............................................................4-2
Figure 4-2. Edit VINES Global Parameters Window ...................................................4-3
Figure 4-3. VINES Interfaces Window ........................................................................4-7
117372-A Rev. A
vii
Tables
Table 1-1. VINES Protocol Stack ..............................................................................1-2
Table 1-2. Assignment of Subnetwork Numbers ......................................................1-6
Table 1-3. VINES Routing Tables ............................................................................1-12
Table 4-1. Broadcast Class Options .........................................................................4-5
Table A-1. VINES Global Parameters ...................................................................... A-1
Table A-2. VINES Interface Parameters ................................................................... A-2
117372-A Rev. A
ix
About This Guide
If you are responsible for configuring VINES serviceson a Bay Networks® router,
you need to read this guide.
If you want to Go to
Learn about the VINES protocol Chapter
Learn about special aspects of the Bay Networks implementation of
VINES
Start VINES on a router and get it running with default settings for
parameters
Change default settings for VINES parameters Chapter 4
See a list of VINES parameter defaults Appendix A
Before Y ou Begin
Before using this guide, you must complete the following procedures. For a new
router:
• Install the router (refer to the installation manual that came with your router).
• Connect the router to the network and create a pilot configuration file (refer to
Quick-Starting Routers, Configuring BayStack Remote Access
ASN Routers to a Network)
Make sure that you are running the latest version of Bay Networks Site Manager
and router software. For instructions, refer to
7–11.xx to Version 12.00
1
Chapter 2
Chapter 3
, or
Connecting
.
Upgrading Routers from Version
.
117372-A Rev. A
xi
Configuring VINES Services
.
.
Conventions
angle brackets (< >) Indicate that you choose the text to enter based on the
description inside the brackets. Do not type the
brackets when entering the command.
ping
Example: if command syntax is
you enter
ping 192.32.10.12
<ip_address>
,
bold text
Indicates text that you need to enter, command names,
and buttons in menu paths.
Example: Enter
Example: Use the
Example: ATM DXI > Interfaces >
wfsm &
dinfo
command.
PVCs
identifies the
PVCs button in the window that appears when you
select the Interfaces option from the ATM DXI menu.
brackets ([ ]) Indicate optional elements. You can choose none, one,
or all of the options.
.
ellipsis points Horizontal (. . .) and vertical ellipsis points indicate
()
omitted information.
italic text
Indicates variable values in command syntax
descriptions, new terms, file and directory names, and
book titles.
quotation marks (“ ”) Indicate the title of a chapter or section within a book.
screen text
Indicates data that appears on the screen.
Example:
Set Bay Networks Trap Monitor Filters
separator ( > ) Separates menu and option names in instructions and
internal pin-to-pin wire connections.
Example: Protocols > AppleTalk identifies the
AppleTalk option in the Protocols menu.
Example: Pin 7 > 19 > 20
vertical line (|) Indicates that you enter only one of the parts of the
command. The vertical line separates choices. Do not
type the vertical line when entering the command.
Example: If the command syntax is
|
show at routes
show at routes
xii
, you enter either
nets
or
show at nets
, but not both.
117372-A Rev. A
Acronyms
About This Guide
ARP Address Resolution Protocol
HDLC High-level Data Link Control
ICMP Internet Control Message Protocol
ICP Internet Control Protocol
IPC Interprocess Communication
IEEE Institute of Electrical and Electronic Engineers
IP Internet Protocol
ISO International Organization for Standardization
MAC media access control
OSI Open Systems Interconnection
RTP Routing Update Protocol
SMDS Switched Multimegabit Data Services
SNAP Subnetwork Access Protocol
SPP Sequenced Packet Protocol
TCP Transmission Control Protocol
UDP User Datagram Protocol
VINES Virtual Networking System
Ordering Bay Networks Publications
To purchase additional copies of this document or other Bay Networks
publications, order by part number from Bay Networks Press™ at the following
numbers:
• Phone--U.S./Canada: 888-422-9773
• Phone--International: 510-490-4752
• FAX--U.S./Canada and International: 510-498-2609
The Bay Networks Press catalog is available on the World Wide Web at
support.baynetworks.com/Library/GenMisc
available on the W orld W ide Web at
117372-A Rev. A
support.baynetworks.com/Library/tpubs
. Bay Networks publications are
.
xiii
Configuring VINES Services
Bay Networks Customer Service
You can purchase a support contract from your Bay Networks distributor or
authorized reseller, or directly from Bay Networks Services. For information
about, or to purchase a Bay Networks service contract, either call your local Bay
Networks field sales office or one of the following numbers:
Region Telephone number Fax number
United States and
Canada
Europe 33-4-92-96-69-66 33-4-92-96-69-96
Asia/Pacific 61-2-9927-8888 61-2-9927-8899
Latin America 561-988-7661 561-988-7550
Information about customer service is also available on the World Wide Web at
support.baynetworks.com
How to Get Help
If you purchased a service contract for your Bay Networks product from a
distributor or authorized reseller, contact the technical support staff for that
distributor or reseller for assistance.
If you purchased a Bay Networks service program, call one of the following Bay
Networks Technical Solutions Centers:
800-2LANWAN; then enter Express
Routing Code (ERC) 290, when prompted,
to purchase or renew a service contract
508-916-8880 (direct)
.
508-916-3514
xiv
Technical Solutions Center Telephone number Fax number
Billerica, MA 800-2LANWAN 508-916-3514
Santa Clara, CA 800-2LANWAN 408-495-1188
Valbonne, France 33-4-92-96-69-68 33-4-92-96-69-98
Sydney, Australia 61-2-9927-8800 61-2-9927-8811
Tokyo, Japan 81-3-5402-0180 81-3-5402-0173
117372-A Rev. A
This overview of the Virtual Networking System (VINES) looks briefly at
• VINES network organization, architecture, and addressing scheme
• Router software for VINES services, including the data link and routing
protocols
VINES Networks
Chapter 1
VINES Overview
117372-A Rev. A
Banyan Systems developed VINES as a network for personal computers. Based
on UNIX System 5.3, VINES uses a distributed system environment wherein PC
users easily communicate and share hardware (such as printers, disk space, and
modems) and software (such as files and applications) transparently on a network.
To a PC user, VINES presents a complex, multivendor network as if it were a
single-vendor network. Resources from all servers on the network are a vailable to
individual PCs with system administrators controlling access to those resources.
A VINES network employs servers, clients, and various communications
hardware connected over LANs and WANs (F
•
Servers
and services, such as file and print services, to PC users. Banyan and several
other vendors manufacture VINES server hardware.
•
Clients
by servers.
are computers that run VINES serv er software to provide connecti vity
are PCs that run VINES client software and use the services provided
igure 1-1):
1-1
Configuring VINES Services
VINES
server
Figure 1-1. VINES Server and Its Clients
VN0001A
Datagrams called
environment. Within each packet is the source and destination address needed to
route the packet between nodes on the network. Each packet is a discrete unit of
data that travels independently on the network layer.
VINES Architecture
VINES architecture reflects the International Organization for Standardization
(ISO) for Open Systems Interconnection (OSI). Banyan designed VINES to
support both existing and future OSI model requirements. The VINES protocol
stack has seven layers; the lower three layers deliver and route data, while the
upper layers handle application-specific processes (T
Table 1-1. VINES Protocol Stack
Layer Protocol or Application
Application VINES services, VINES Tasker, UNIX, DOS, and
Presentation VINES Matchmaker Data Type Representations
Session VINES Matchmaker Remote Procedure Calls
VINES internet packets
StreetTalk
carry information across a VINES
able 1-1).
1-2
(continued)
117372-A Rev. A
VINES Overview
Table 1-1. VINES Protocol Stack
Layer Protocol or Application
Transport VINES Interprocess Communication (IPC) Protocol
VINES Sequenced Packet Protocol (SPP), Transmission Control
Protocol (TCP), and User Datagram Protocol (UDP)
Network VINES Internet Protocol (IP)
VINES Internet Control Protocol (ICP)
VINES Nonsequenced Address Resolution Protocol (ARP)
VINES Sequenced ARP
VINES Nonsequenced Routing Update Protocol (RTP)
VINES Sequenced RTP
X.25, X.3, X.29, and IP used by TCP, ICMP, and NetBIOS
Data Link VINES Fragmentation Protocol
Drivers for Block Asynchronous, High Data Link Control (HDLC),
Token Ring, Ethernet, other LANS, and Institute of Electrical and
Electronic Engineers (IEEE) 802.x standards
Physical Broadband, baseband, point-to-point, and twisted pair
(continued)
At the data link level, VINES currently supports se veral IEEE standards, including
Ethernet, Token Ring, and 802.x. VINES also provides its own proprietary data
link protocol, VINES Fragmentation Protocol, which breaks up and reassembles
packets that are too large to travel over certain media. However, only routers
configured over synchronous lines support VINES Fragmentation Protocol.
117372-A Rev. A
At the networking level, VINES supports both industry standard protocols such as
TCP/IP, X.25, and AppleTalk, and its own set of networking protocols. The latter
include VINES
• Internet Protocol
• Nonsequenced Routing Update Protocol
• Sequenced Routing Update Protocol
• Nonsequenced Address Resolution Protocol
• Sequenced Address Resolution Protocol
• Internet Control Protocol
Upper-layer protocols include VINES print and file service applications and the
VINES naming protocol, StreetTalk.
1-3
Configuring VINES Services
StreetTalk is a distributed directory service that contains the names and attributes
of all critical network resources. Each resource on a VINES network has a
StreetTalk name that is globally unique.
StreetTalk names have the following format:
item@group@organization
where
item
identifies a user or resource on the network
group
identifies the group to which the item belongs
organization
identifies the organization to which the group belongs
VINES adapts to changes in the network topology; because the VINES network
refers to each resource by name, you can move or replace it and the PCs can still
locate it. System administrators control which resources end users on the network
can access.
VINES Network Addressing
Each node grouping on a VINES network consists of a service node and the client
nodes to which the service node provides address resolution and routing services
igure 1-2). Note that this is a logical grouping; client nodes may or may not map
(F
directly to the same physical media.
1-4
117372-A Rev. A
VINES Overview
VINES Address
00008A42.8001
VINES Address
00008A42.8002
VINES Address
00008A42.8003
PC
PC
PC
LAN 20 LAN 50
Key
LAN = LAN Address
Serial = Serial Number
VINES Address
= Network Number. Subnetwork Number
Figure 1-2. VINES Network
When a client node becomes active on the network, it broadcasts a query request
to all servers. All reachable servers respond. The client node chooses the first
server that responds and requests a VINES internet address from that server. The
service node assigns a unique, 48-bit VINES internet address to the client node.
Server 1
Serial
VINES Address
Server 2
Serial
EC258A42
VINES Address
EC25.18A42.1
PC
PC
PC
VINES Address
EC25.8001
VINES Address
EC25.8002
VINES Address
EC25.8003
VN0002A
117372-A Rev. A
The VINES internet address is independent of any data-link-layer address
assigned to a node on a physical medium. The 48-bit VINES internet address
consists of two fields (F
igure 1-3):
• The 32-bit network number field
The network number is the serial number of the server node and identifies the
logical grouping of nodes on a VINES network.
• The 16-bit subnetwork number field
The subnetwork number identifies the node within the server node’s logical
grouping.
1-5
Configuring VINES Services
Network number
Subnetwork number
Server
32 bits 16 bits
Client
VN00003A
Figure 1-3. VINES Internet Address Format
The internet address for each service node in a VINES network is its network
number, integrated with the subnetwork number 1. The service node assigns
unique internet addresses to all other client nodes in its subnetwork by integrating
its network number with a unique subnetwork number for each node. The service
node assigns subnetwork numbers as shown in T
Table 1-2. Assignment of Subnetwork Numbers
Subnetwork Number Node Type
1 Server only
2 to 0x7fff Unused
0x8001 to 0xfffe Clients only
ffff Broadcast
able 1-2.
How the Router for VINES Services Works
On a VINES network, the router maintains the network topology and uses both
IEEE standard and VINES proprietary protocols to route packets through the
network. The router supplies client nodes with addresses only if there are no other
servers on the network.
The following sections describe the VINES data link and routing protocols that
the router uses.
1-6
117372-A Rev. A
Loading...