Home

Avaya Configuring OSI Services User's Manual

Contents

1. Designated M i Router PVCL di WEE MP E PVC3 nm Interface 1 PVC1 UE Direct access mode Br E Interface 2 PVC2 PVC3 Group access mode Frame Relay Network OSI0023A Figure 2 8 Frame Relay Mixed Access Modes Direct and Group Topology Consider the following issues in implementing OSI over group access mode Frame Relay circuits in a full or partial mesh topology Full Mesh Topology Full mesh topology in OSI over Frame Relay means that all routers are connected to each other with PVCs Figure 2 9 Using group access mode in a full mesh topology models the Frame Relay network as a LAN 2 12 114052 Rev A Designated Router OSI Implementation Notes All routers connected with PVCs OSI0020A Figure 2 9 Full Mesh Topology If a router fails or the link to the Frame Relay network fails the topology remains full mesh If a PVC fails however the network changes from a full mesh to a partial mesh topology This can introduce connectivity problems in the resulting network For example if a non designated router loses a PVC to the designated router it will attempt to elect another designated router Since the other systems are still in contact with the active designated router the link state databases of the routers will not be
2. ssesesssss 1 7 Basic NSAP Address Strogi iiec erret ot E rre ERR te etae 1 8 GOSIP NSAP Address Format lt ciesiai iwi ed ot tb Metu pie ais 1 9 ANSINSAP Address POTIS 2 ciet pantera base naea 1 11 pin dg irte is br DEPT E NE 1 13 Campus Routing Domain ERE T 1 14 Assigning NSAP AJddIGSBBS siecisrm entra het od HERR n HERR cee 1 16 Router 1 Floods Area A with LSPs about the new End System 1 19 Lowest Cost Path Router Ao B to ES uisi trennt ic entices 1 21 Foule Fodrocini orisa 1 25 Static Inter Domain Routing T huius 1 27 Original Area Addresses for Area XY sss 2 2 Assign Area Address Alias 456 to All Routers in Area XY 2 3 Assign Area Address 456 to Specific End Systems 2 4 Divide Area XB into Area X and Area Y sse 2 5 Routers B and C in an Area Partition Due to Improper pub orisni iabsetans bbdecinahidadeecacnladseieesiiedens 2 6 Frame Relay Direct Access Mode ccccccseseeceeeeeeeeneeeeeeeeeeeeaeeeneneeees 2 10 Frame Relay Group Access Mode H 2 11 Frame Relay Mixed Access Modes Direct and Group 2 12 qui Hee TET 2 13 Partial Mesh in Hub and Spoke Topology sese 2 14 Ger contidilaticH VINO istae in aei e etc bo ae dde dedo 3 2 Configuration Manager Window
3. 4 2 Edit OSI Global Parameters WINDOW iuuat recupero irn ese eic Son r ard naa 4 4 NI Ge Liste WENCH MNEELT 4 13 OSI Static ES Adjacency List WIDOOW scis cdscicictdasseenhesiectietatadsanetonadzane 4 21 Figure 4 5 OSI Static ES Adjacency Configuration Window sssss 4 22 Figure 4 6 OSI External Address Adjacency List Window sssssss 4 25 Figure 4 7 OSI External Address Adjacency Configuration Window 4 26 Figure 8 OSI Static Routes VIDODW uec tie bird ee S od ee E EXE HERR rx PEE ENDO CR 4 30 Figure 4 9 Static Route Configuration Window A E rod 4 31 Figure 4 10 Selecting Protocols gt OSI gt Create DECnet IV to V Transition 4 35 Figure 4 11 Edit DECnet IV to V Transition Parameters Window 4 36 Figure A 1 Clase A Internet Address aussen i e iia beth pedo ru ise eP Red Sk tatu Dus RE exa ann A 4 Figure A Glass B Internet Address io oce edit a inet adii d et iced A 5 Figure A 3 Class C Internet Address sssesseseseeeeenne A 6 X 114052 Rev A Tables Table 1 1 OSI Reference Model and Common ISO Standards 1 3 Table 1 2 NSAP Address Structure Assigned by the ICD 0005 Subdomain 1 10 Table 1 3 NSAP Address Structure Assigned by the DCC 840 Subdomain 1 12 Table 1 4 Link Ste Packet TUDBB cosa arciecn er ti d entis
4. Enter the entire area address portion of the NSAP address that reflects the location of the router including the routing domain and area portions that identify where in the local network the router resides Either you or your administrative authority should provide the identifiers for the local routing domain and area portions of the address Ifyou have not registered your OSI network with an addressing authority then you can accept the default area address of 0x490040 MIB Object ID 1 3 6 1 4 1 18 3 5 6 1 16 local area You must assign different area addresses to routers that reside in different areas Note You must assign the same area address to all routers residing in the same gt 4 10 114052 Rev A Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Parameter Default Range Function Instructions MIB Object ID Editing OSI Parameters Area Address Alias 1 hex None Any valid area address Assigns the first area address alias to the router An area address alias is a different area address that is assigned to the same router For the DECnet IV to V Transition feature the area address alias defines the Phase IV prefix and Phase IV area fields of the Phase IV compatible address Enter the area address alias in hexadecimal format For the DECnet IV to V Transition feature enter
5. DECrwt 4 to 5 Transition Enable frees Address Alias P hex Figure 4 11 Edit DECnet IV to V Transition Parameters Window 2 Edit the parameters using the descriptions that follow as a guide 3 Click on OK to implement your changes and exit the screen Parameter DECnet 4 to 5 Transition Enable Default Disable Options Enable Disable Function Enables or disables DECnet IV to V Transition Instructions To enable the transition set this parameter to Enable Otherwise set it to Disable to turn the transition off MIB Object ID 1 3 6 1 4 1 18 3 5 6 12 2 4 36 114052 Rev A Editing OSI Parameters Parameter Area Address Alias 1 hex Default None Options Any valid area address Function Assigns the first area address alias to the router An area address alias is a different area address that is assigned to the same router For the DECnet IV to V Transition feature the area address alias defines the Phase IV prefix and Phase IV area fields of the Phase IV compatible address Instructions Enter the area address alias in hexadecimal format For the DECnet IV to V Transition feature enter the Phase IV prefix from 1 to 9 bytes followed by 2 bytes of the Phase IV area address Otherwise leave this field blank MIB Object ID 1 3 6 1 4 1 18 3 5 6 1 17 Deleting DECnet IV to V Transition To delete DECnet IV to V Transition 1 Select Protocols OSI Delete DECnet IV to V Transition from the
6. Inter Domain Routing Inter domain routing is possible when paths to other domains are statically defined To enable inter domain routing you must manually enter the set of reachable address prefixes into each L1 L2 router that is linked to an external domain Such routers are called bordering routers The address prefixes describe which NSAP addresses are reachable over that L1 L2 router s external link The next time the L1 L2 routers in the domain exchange LSPs they become aware of the existence of the reachable external addresses and update their link state databases with this information As traffic is routed throughout the network a router directs packets to a bordering router if the leading bytes of the destination addresses match the statistically defined reachable address prefixes The bordering router then transmits the packet out of the domain The next domain assumes responsibility for routing the packet to its final destination Inter domain routing is strictly between L1 L2 routers Figure 1 13 demonstrates inter domain routing between Domain A and Domain B For example the L1 L2 bordering router receives a packet from within Domain A and forwards it to the L1 L2 bordering router in Domain B 1 28 114052 Rev A Chapter 2 OSI Implementation Notes This chapter contains information about configuring Bay Network routers with special network considerations Before you implement the enabling Chapter 3 and general co
7. OSI0006A GOSIP NSAP Address Format The AFI for these NSAP addresses is 47 which shows that the network belongs to an ICD subdomain The IDI is 0005 specifying the ICD 0005 subdomain which is reserved for use by the U S government The Domain Format Identifier DFI is 80 specifying that the DSP portion of NSAP is in GOSIP format Currently the only DSP format defined by the ICD 0005 subdomain is that defined by GOSIP The Administrative Authority Identifier AAT portion of these NSAP addresses is a globally unique number assigned by the ICD 0005 subdomain It identifies the network within the ICD 0005 subdomain where the NSAP resides and the authority responsible for organizing the network into routing domains and areas Note that the authority specified by the AAI assigns values to the Routing Domain ID Area ID System ID and NSAP Selector portions of the NSAP address Table 1 2 describes the contents of each field for this type of NSAP address 114052 Rev A Configuring OSI Services Table 1 2 NSAP Address Structure Assigned by the ICD 0005 Subdomain Field Value Meaning AFI 47 Identifies the subdomain as ICD Specifies the syntax of the DSP as binary octets IDI 0005 Indicates that the subdomain is ICD 0005 DFI 80 Specifies that the format of the DSP is GOSIP AAI variable Identifies the network within the ICD 0005 subdomain where the NSAP resides and the authority respon
8. Configuring OSI Services Router Software Version 11 0 Site Manager Software Version 5 0 Part No 114052 Rev A August 1996 rS Bay Networks Bay Networks 4401 Great America Parkway 8 Federal Street Santa Clara CA 95054 Billerica MA 01821 Copyright 1988 1996 Bay Networks Inc All rights reserved Printed in the USA August 1996 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 any 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 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 Notice for All Other Executive Agencies 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
9. Function Instructions MIB Object ID IIH Hello Timer 8 21418115130160112013001 6001 1800 2400 3600 The IIH intermediate to intermediate hello timer specifies in seconds how often other routers need to send ISH intermediate system hello messages to this router This router includes this value in the intermediate system hello messages it sends to the other routers Accept the default value or select any valid option 1 3 6 1 4 1 18 3 5 6 3 10 ISH Hello Timer 30 21418115 13016011201 300 6001 1800 2400 3600 The ISH intermediate system hello timer specifies the interval in seconds between LAN hello messages transmitted across the interface between a router L1 or L1 L2 and an end system in the local area Accept the default value or select any valid option 1 3 6 1 4 1 18 3 5 6 3 11 ESH Configuration Time 600 21418115130 160 120 I 300 600 18001 2400 3600 The ESH end system hello configuration timer specifies in seconds how often end systems need to send system hello messages to this router This value is included in the intermediate system hello messages the router sends to end systems Accept the default value or select any valid option 1 3 6 1 4 1 18 3 5 6 3 12 4 18 114052 Rev A Parameter Default Range Function Instructions MIB Object ID Parameter Default Range Function Instructions MIB Object ID Parameter Default Range Function In
10. The router sends the RD packet back to the originating end system which has the option of using the RD packet to update its routing information base with the more direct route Intermediate System to Intermediate System Intra Domain Routing Exchange Protocol The Intermediate System to Intermediate System Intra Domain Routing Exchange Protocol ISO 10589 defines the way in which intermediate systems routers within a routing domain exchange configuration and routing information It works with ISO 8473 and ISO 9542 to define how routers can communicate and route packets within and between areas Intra Domain Routing Intra domain routing functions within a single routing domain The domain may consist of various types of subnetworks that have been administratively divided into separate routing areas Under this protocol L1 routers keep track of the routing that occurs within their own areas Thus each L1 router must know the topology of its local area including the location of all other routers and end systems from LSP and hello packets that are exchanged throughout the network Note that an L1 router does not need to know the identity of those systems residing outside of its local area because it forwards all packets destined for other areas to the nearest L1 L2 router Similarly each L1 L2 router must know the topology of the other L1 L2 routers located in the domain and the addresses that are reachable through each L1 L2 router
11. 114052 Rev A OSI Overview e Level 2 L2 routing for routing data between areas You can configure a Bay Networks router running OSI to function as an L1 router an L2 router or an L1 L2 router Figure 1 2 Routing Domain L1 Routing L2 Routing End System L1 Router L1 L2 Router OSI0003A Figure 1 2 L1 Routing within an Area and L2 Routing between Areas Level 1 Routing An L1 router exchanges data with systems located within its area and forwards packets destined for a different area or domain to the nearest L1 L2 router for processing 114052 Rev A 1 5 Configuring OSI Services Level 2 Routing Level 2 routing exchanges data with systems located in a different area In addition L2 routing forwards data externally between routing domains as long as you statically define an external link To support routing between areas every area must contain at least one router configured to support L2 routing services OSI Network Addressing The OSI addressing scheme is based on the hierarchical structure of the OSI global network A unique Network Service Access Point NSAP address identifies each system within an OSI network The NSAP address specifies the point at which the end system or intermediate system performs OSI network layer services The complete set of NSAP addresses contained within the OSI network is the global network addressing domain This domain is divided into subsets called network ad
12. 3 Repeat Steps 1 and 2 to delete additional static routes 4 Click on Done to exit the screen Configuring DECnet IV to V Transition You create edit and delete DECnet IV to V Transition from the Configuration Manager You can only access the DECnet IV to V Transition parameters using OSI To enable the DECnet IV to V Transition feature you must configure at least one DECnet interface on the router See Configuring DECnet Services for more information about the DECnet IV to V Transition feature 4 34 114052 Rev A Editing OSI Parameters Creating the DECnet IV to V Transition From the Configuration Manager window select Protocols gt OSI gt Create DECnet IV to V Transition Figure 4 10 This enables the DECnet IV to V Transition feature If you select Protocols gt OSI you see that the edit and delete options are now available Descriptio Hoe dual Ethernet Single Sync ASYHC Sin Eepty Slot Aystes Resource Honule Figure 4 10 Selecting Protocols gt OSI gt Create DECnet IV to V Transition Editing the DECnet IV to V Transition Parameters To edit the DECnet IV to V Transition parameters 1 Select Protocols OSI Edit DECnet IV to V Transition from the Configuration Manager window refer to Figure 4 10 114052 Rev A 4 35 Configuring OSI Services The Edit DECnet IV to V Transition Parameters window appears Figure 4 11 porn frak WM te V Traraition Parametarz 000 Cance
13. A XV Configuring OSI Services ITU T International Telecommunications Union Telecommunication Standardization Sector L1 Level 1 L2 Level 2 LAN local area network LSP Link State Packet MAC Media Access Control MIB Management Information Base MOM Maintenance Operations Module MOP Maintenance Operations Protocol OSI Open Systems Interconnection NSAP Network Service Access Point PDN Public Data Network PPP Point to Point Protocol PSNP Partial Sequence Number Packet PVC Permanent Virtual Circuit RFC Request for Comment RIP Routing Information Protocol SNAP Subnetwork Access Protocol SNMP Simple Network Management Protocol SNPA Subnetwork Point of Attachment TCP Transmission Control Protocol VT Virtual Terminal Ordering Bay Networks Publications To purchase additional copies of this document or other Bay Networks publications order by part number from the Bay Networks Press at the following telephone or fax numbers Telephone U S Canada 1 888 4BAYPRESS Telephone International 1 510 490 4752 Fax 1 510 498 2609 You can also use these numbers to request a free catalog of Bay Networks Press product publications xvi 114052 Rev A Technical Support and Online Services To ensure comprehensive network support to our customers and partners worldwide Bay Networks Customer Service has Technical Response Centers in key locations around the globe e Billerica Massachusetts e Santa Cl
14. CCITT now ITU T recommended set of standards for international open systems support and vendor interoperability These layers are physical data link and network Table 1 1 lists some of the most common ISO standards implemented by OSI 1 2 114052 Rev A OSI Overview Table 1 1 OSI Reference Model and Common ISO Standards 8571 File Transfer and Access Management FTAM Application Layer 8649 OSI Association Control Service Element ACSE 9040 Virtual Terminal Protocol VT 8822 OSI connection oriented and connectionless presentation services Presentation Layer 8824 Abstract Syntax Notation One ASN 1 9576 OSI connectionless protocol to provide connectionless service 8326 Session service definitions Session Layer 8327 Session layer protocols 8072 Transport service definition both connection and connectionless Transport Layer 8073 Transport connection oriented protocol definition 8602 Transport definition for connectionless mode protocol 8473 Connectionless mode network service Network Layer 9542 End System to Intermediate System routing exchange protocol 10589 Intermediate System to Intermediate System routing exchange protocol 8802 Local area network standards mostly derived from IEEE standards 8471 HDLC balanced link address information 8886 Data link service definition for OSI Data Link Layer 9314 Fiber Distributed Data Interface FDDI Physical Layer 9543 Synchronous transmission quality at DTE DCE interface 9
15. Configuration Manager window refer to Figure 4 10 A window pops up and prompts Do you REALLY want to delete OSI DECnet IV to V Transition 2 Click on OK The system returns you to the Configuration Manager window The DECnet IV to V Transition feature is no longer configured on the router Deleting OSI from the Router To delete the OSI routing protocol from all router circuits on which it is currently enabled 1 Select Protocols gt OSI gt Delete OSI from the Configuration Manager window refer to Figure 4 1 A window pops up and prompts Do you REALLY want to delete OSI 114052 Rev A 4 37 Configuring OSI Services 2 Click on OK The Configuration Manager window appears OSI is no longer configured on the router If you examine the Configuration Manager window you see that the connectors for circuits on which OSI was the only protocol enabled are no longer highlighted You must reconfigure the circuits for these connectors See Configuring Routers for details on configuring circuits 4 38 114052 Rev A Appendix A IP to X 121 Address Mapping for DDN This appendix describes how to convert an IP address to an X 121 address if you are configuring OSI over DDN X 25 You enter this converted address when you add static end system adjacencies or an external address See Chapter 4 for additional information This appendix includes e An overview of the IP address classes e Address conver
16. Link state routing algorithm Routing protocols Note This document uses the terms intermediate system and router interchangeably 114052 Rev A Configuring OSI Services OSI Basic Reference Model OSI is a nonproprietary distributed processing architecture The International Organization for Standardization ISO developed OSI to provide communication standards These standards allow computer systems from different vendors to communicate The OSI basic reference model combines a structured computer system architecture with a set of common communication protocols It comprises seven layers Each layer provides specific functions or services and follows the corresponding OSI communication protocols to perform those services OSI is an open system architecture Peer to peer common layers between systems abolish the vendor specific restrictions imposed by other architectures The principles of the OSI layering scheme include the following e Similar services are on the same layer e Services provided by lower layers are transparent to the layers above it e The lower the layer the more basic the services it provides e The higher layers build upon the services offered by the layers below them OSI services for Bay Networks Version 7 60 and later software are United States Government OSI Profile GOSIP Version 2 0 compliant In addition Bay Networks router software provides support for the first three layers of the ISO
17. 24 Hub and spoke topology 2 13 Hybrid circuit mode 2 11 Implementation notes 2 1 InfoFACTS service xxi Inter domain routing 1 28 Interface parameters Circuit Password 4 19 editing 4 13 to 4 19 Enable 4 14 ESH Configuration Time 4 18 IIH Hello Timer 4 18 IIH Hold Time Multiplier 4 19 ISH Hello Timer 4 18 ISH Hold Time Multiplier 4 19 L1 Default Metric 4 15 L1 Designated Router Priority 4 16 L2 Default Metric 4 16 L2 Designated Router Priority 4 17 Routing Level 4 14 Intermediate System to Intermediate System Intra Domain Routing Exchange Protocol 1 26 to 1 28 inter domain routing and 1 28 intra domain routing and 1 26 to 1 27 Index 2 114052 Rev A Intermediate System to Intermediate System Routing Exchange Protocol 1 22 2 5 Intermediate systems 2 9 Internet Protocol IP 2 7 A 2 Intra domain routing 1 26 ISO standards 1 2 L Level 1 routing 1 5 1 21 2 6 Level 2 routing 1 21 2 6 Lifetime control function 1 23 Link state database 2 13 4 8 4 9 Link state packet 1 18 to 1 19 Mixed access circuit mode 2 11 N Neighbor detection 2 15 Network addressing domain 1 6 Network configuration 2 1 NSAP address 1 6 to 1 16 area address 1 12 to 1 13 authority and format identifier AFI 1 8 domain specific part DSP 1 7 initial domain identifier IDI 1 8 initial domain part IDP 1 7 OSI accessing parameters 4 2 addressing authority 1 6 administrative domain 1
18. 4 area address alias 2 2 to 2 5 areas 1 4 basic reference model 1 2 configuring over DDN X 25 2 7 A 1 Index OSI continued conversion algorithm for X 121 address A 7 to A 10 defaults B 1 deleting from the router 4 37 enabling on a circuit 3 1 end systems 1 6 1 23 external domain 1 28 2 7 forwarding database 1 21 intermediate systems 1 23 1 26 level 1 routing 1 5 1 21 level 2 routing 1 6 1 21 link state database 1 20 to 1 21 link state packet LSP 1 18 to 1 19 lowest cost path 1 20 network addressing domain 1 6 network organization 1 3 to 1 16 network overview 1 1 Network Service Access Point NSAP address 1 6 to 1 15 over Frame Relay 2 8 to 2 15 packet segmentation 1 23 path costs 4 15 reachable address prefixes 1 28 2 7 routing algorithm 1 17 to 1 22 decision process 1 17 1 20 to 1 21 forwarding process 1 17 1 21 to 1 22 update process 1 17 to 1 20 routing domain 1 4 routing protocols 1 22 to 1 28 static end system adjacency adding 4 21 configuring 4 20 to 4 24 copying 4 24 deleting 4 24 editing 4 24 static external address adjacency adding 4 26 configuring 4 25 to 4 29 copying 4 29 deleting 4 29 editing 4 29 static external adjacencies 2 7 114052 Rev A Index 3 Configuring OSI Services OSI continued static route adding 4 30 configuring 4 30 to 4 34 copying 4 33 deleting 4 34 editing 4 33 OSI parameters editing global 4 3 to 4 12 editing
19. Delete OSI globally from the Bay Networks router 114052 Rev A 4 1 Configuring OSI Services Accessing OSI Parameters You access all OSI parameters from the Configuration Manager window shown in Figure 4 1 Refer to Configuring Routers for details on accessing this window LLL um graum ge Configuration Mode local LOCAL FILE c ftp mnbAusrzL bechpubis ibaosi efa Backbone Link Hodo 2 BDH 2 3 00 Color Key sed Deaocriptinn Lonnectorz gaa Dual Ethernet a Single Sumc ASHO Sin ECO Esptu Slot Empty Slot Systes Aesource Rodale Figure 4 1 Configuration Manager Window To customize the router software for OSI services you can edit any of these types of OSI parameters e Global e Interface e Static adjacency e Static route e DECnet IV to V Transition For each OSI parameter this chapter describes the default setting all valid setting options the parameter function instructions for setting the parameter and the MIB object ID 4 2 114052 Rev A Editing OSI Parameters The Technician Interface lets you modify parameters by issuing set and commit commands that specify the MIB object ID This process is equivalent to modifying parameters using Site Manager For more information about using the Technician Interface to access the MIB refer to Using Technician Interface Software Caution The Technician Interface does not verify that the value you enter for a parameter is v
20. L2 routers router in the domain that are reachable over within the domain the broadcast subnetwork and any routes to external domains L2 router L2 The links to the L1 L2 designated All L1 L2 routers non pseudonode router and static external links within the domain In addition on broadcast subnetworks the subnetwork itself is conceptually viewed as a node called a pseudonode in the OSI network One router on the subnetwork is elected as the designated router for the pseudonode The designated router is responsible for creating and transmitting an LSP on behalf of the pseudonode Thus the designated router generates a pseudonode LSP By generating a single LSP that represents the pseudonode the router reduces the amount of link state information that traverses the subnetwork The L1 designated router and the L2 designated router for a subnetwork are elected independently If there is only a single L1 or L1 L2 router on a LAN segment it becomes the designated L1 or L2 router by default 1 18 114052 Rev A OSI Overview Note A Bay Networks router can have multiple OSI interfaces to separate subnetworks You can configure the interfaces independently so that the router can act as the designated router for some subnetworks but not for others OSI routers generate LSPs periodically and also when there is a change in the network topology For example in Figure 1 10 a new end system is added to Area A Router 1 generates an L1 LSP and
21. OSI over Frame Relay 2 15 Domain specific part 1 7 E Enable OSI 3 1 114052 Rev A Index 1 Configuring OSI Services Enabling parameters Area Address 3 3 Router ID 3 3 End System to Intermediate Station Routing Exchange Protocol 1 22 End System to Intermediate System Routing Exchange Protocol 1 23 to 1 26 configuration report and 1 23 to 1 24 redirection and 1 24 to 1 26 End systems 1 3 1 6 External domain 2 7 External routing level 2 7 F Forwarding router process 1 21 Frame Relay 2 8 to 2 15 G Getting help from a Bay Networks Technical Response Center xxi from the Support Source CD xx through CompuServe xx through Customer Service FTP xix through InfoFACTS service xxi through World Wide Web xix Global parameters Area Address 4 10 Area Address Alias 1 4 11 Area Address Alias 2 4 11 CLNP Source Route Support 4 12 editing 4 3 to 4 12 Enable 4 4 IS Checksum 4 8 L1 LSP Password 4 8 L2 LSP Password 4 9 Load Balancing 4 6 Max Area Addresses 4 6 Max End Systems 4 6 Max External Addresses 4 7 Max L1 Intermediate Systems 4 7 Global parameters continued Max L2 Intermediate Systems 4 7 Max Learned End Systems 4 11 Max Learned L1 Intermediate Systems 4 12 Max Learned L2 Intermediate Systems 4 12 Router ID 4 5 Router Type 4 5 Government OSI Profile GOSIP Version 2 0 1 2 1 8 GSA 1 6 H Hello packet exchange 1 23 Holding timer 1
22. SPF algorithm to define the set of paths to a destination The router does not define shortest in terms of distance The OSI router defines the shortest path as the lowest cost path based on the relative cost metric of routing a packet along each path Every circuit on the OSI network receives a default cost You can assign a new relative cost to a circuit as needed During the decision process the OSI router calculates the total path cost of forwarding a packet along each possible path toward the destination The total path cost is the sum of the costs of the circuits that make up the path The router chooses the lowest cost path Note When you configure the Bay Networks OSI router you can change the default cost metric assigned to OSI interfaces For example you can assign a high cost to limit the use of a certain low speed interface See the section Editing OSI Interface Parameters in Chapter 4 for instructions When deciding among multiple paths to a destination the router will choose the path that is assigned a lower path cost over one assigned a higher cost even if the lower cost path is longer in the number of hops For example in Figure 1 11 the lowest cost path from router A to destination ES is the path through router B cost of 15 rather than the direct path cost of 20 1 20 114052 Rev A OSI Overview Ato B to ES 15 Ato B cost 5 B to ES cost 10 Direct A to ES cost 20 OSI0012A F
23. a listing of support cases and determine the current status of any open case Case history data includes severity designation and telephone e mail or other logs associated with the case e Customize the listing of cases according to a variety of criteria including date severity status and case ID e Log notes to existing open cases e Create new cases for rapid efficient handling of noncritical network situations Communicate directly via e mail with the specific technical resources assigned to your case The Bay Networks URL is http www baynetworks com Customer Service is a menu item on that home page Customer Service FTP Accessible via URL ftp support baynetworks com 134 177 3 26 this site combines and organizes support files and documentation from across the Bay Networks product suite including switching products from our Centillion and Xylogics business units Central management and sponsorship of this FTP site lets you quickly locate information on any of your Bay Networks products 114052 Rev A xix Configuring OSI Services Support Source CD This CD ROM sent quarterly to all contracted customers is a complete Bay Networks Service troubleshooting knowledge database with an intelligent text search engine The Support Source CD contains extracts from our problem tracking database information from the Bay Networks Forum on CompuServe comprehensive technical documentation such as Cust
24. and disclosure are as set forth in the Commercial Computer Software Restricted Rights clause at FAR 52 227 19 Trademarks of Bay Networks Inc ACE AFN AN BCN BLN BN BNX CN FN FRE GAME LN Optivity PPX SynOptics SynOptics Communications Wellfleet and the Wellfleet logo are registered trademarks and ANH ASN BayeSIS BCNX BLNX EZ Install EZ Internetwork EZ LAN PathMan PhonePlus Quick2Config RouterMan SPEX Bay Networks Bay Networks Press the Bay Networks logo and the SynOptics logo are trademarks of Bay Networks Inc Third Party Trademarks All other trademarks and registered trademarks are the property of their respective owners 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 University 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 acknowle
25. determines path costs on the basis of the sum of the individual circuit costs The cost that you assign to a particular circuit typically reflects the speed of the transmission medium Low costs reflect high speed media while high costs reflect slower media Refer to Table 4 1 for a list of suggested OSI circuit costs The OSI router always selects the interfaces with the lowest cost when defining a path so assigning each interface a cost is in effect a way of assigning it a priority If you do not want this interface to route Level 1 traffic on a regular basis assign it a high cost Otherwise accept the default 20 1 3 6 1 4 1 18 3 5 6 3 6 Table 4 1 Suggested OSI Circuit Cost Values Speed Cost Speed Cost 100 Mb s 1 64 Kb s 54 16 Mb s 19 56 Kb s 55 10 Mb s 20 38 4 Kb s 56 4 Mb s 21 32 Kb s 57 1 54 Mb s 45 19 2 Kb s 58 1 25 Mb s 48 9 6 Kb s 59 833 Kb s 49 7 2 Kb s 60 625 Kb s 50 4 8 Kb s 61 420 Kb s 51 2 4 Kb s 62 230 4 Kb s 52 1 2 Kb s 63 125 Kb s 53 114052 Rev A 4 15 Configuring OSI Services Parameter Default Range Function Instructions MIB Object ID Parameter Default Range Function Instructions MIB Object ID L2 Default Metric 20 1 to 63 Specifies the relative cost of routing Level 2 traffic over this interface OSI determines path costs on the basis of the sum of the individual circuit costs The cost that you assi
26. edit or delete static end system adjacencies Adding a Static End System Adjacency To add a static end system adjacency 1 Click on Add in the OSI Static ES Adjacency List window refer to Figure 4 4 The OSI Static ES Adjacency Configuration window appears Figure 4 5 114052 Rev A 4 21 Configuring OSI Services Figure 4 5 OSI Static ES Adjacency Configuration Window Parameter Default Options Function Instructions MIB Object ID Define the static end system parameters using the descriptions that follow as a guide Click on OK The End System Adjacency List window displays the new adjacency you defined Repeat Steps 1 3 to add additional static end system adjacencies Enable Enable Enable Disable Enables the end system adjacency as defined by the ESID and SNPA parameters The default Enable appears after you add a static end system adjacency in the OSI Static ES Adjacency window 1 3 6 1 4 1 18 3 5 6 5 1 2 4 22 114052 Rev A Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Editing OSI Parameters ESID None Any valid 6 byte end system ID Specifies the end system ID ESID of the adjacent end system Enter the 6 byte end system ID assigned to the adjacent end system in hexadecimal format 1 3 6 1 4 1 18 3 5 6 5 1 3 SNPA None Depends on the circ
27. end connectivity between a router and remote Data Circuit Terminating Equipment DTE devices that support X 25 DDN Standard Service Internet Protocol IP uses DDN service to transmit IP datagrams over the X 25 network Each network interface that connects to the X 25 network uses an X 121 address For additional information about the X 25 network and X 121 addresses see Configuring X 25 Services If you want to run OSI over DDN X 25 you must Configure IP over an X 25 DDN circuit See Configuring IP Services for details Convert the remote IP address to an X 121 address You use the converted address as the Subnetwork Point of Attachment SNPA for a static end system adjacency or a static external address adjacency See Chapter 4 for details on the SNPA parameter and Appendix A for details on address conversion 114052 Rev A 2 7 Configuring OSI Services Configuring DECnet IV to V Transition You can only access the DECnet IV to V Transition parameters using OSI To enable the DECnet IV to V Transition feature you must configure at least one DECnet interface on the router See Configuring DECnet Services for more information about the DECnet IV to V Transition feature and Configuring DECnet IV to V Transition in Chapter 4 for information about editing the parameters Configuring OSI over Frame Relay Frame Relay is a high speed shared bandwidth wide area networking protocol Frame Relay performs only basic proc
28. resulting software available for use by any third party Neither title nor ownership to Software passes to licensee Licensee shall not provide or otherwise make available any Software in whole or in part in any form to any third party Third parties do not include consultants subcontractors or agents of licensee who have licensee s permission to use the Software at licensee s facility and who have agreed in writing to use the Software only in accordance with the restrictions of this license Third party owners from whom Bay Networks has acquired license rights to software that is incorporated into Bay Networks products shall have the right to enforce the provisions of this license against licensee Licensee shall not remove or obscure any copyright patent trademark trade secret or similar intellectual property or restricted rights notice within or affixed to any Software and shall reproduce and affix such notice on any backup copy of Software or copies of software resulting from modification or combination performed by licensee as permitted by this license 114052 Rev A iii Bay Networks Software License continued 10 11 12 Licensee shall not reverse assemble reverse compile or in any way reverse engineer the Software Note For licensees in the European Community the Software Directive dated 14 May 1991 as may be amended from time to time shall apply for interoperability purposes Licensee must notify B
29. the Phase IV prefix from 1 to 9 bytes followed by 2 bytes of the Phase IV area address Otherwise leave this field blank 1 3 6 1 4 1 18 3 5 6 1 17 Area Address Alias 2 None Any valid area address Assigns the second area address alias to the router Enter the area address alias in hexadecimal format Otherwise leave this field blank 1 3 6 1 4 1 18 3 5 6 1 18 Max Learned End Systems 1024 1 to 4000 Specifies the maximum number of end systems per slot that the router can learn about dynamically through the exchange of hello packets Unless the area in which this router resides contains more than 1024 end systems accept the default value 1024 1 3 6 1 4 1 18 3 5 6 1 28 114052 Rev A Configuring OSI Services Parameter Default Range Function Instructions MIB Object ID Parameter Default Range Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Max Learned L1 Intermediate Systems 64 1 to 4000 Specifies the maximum number of L1 routers per slot that this router can learn about dynamically through the exchange of hello packets Unless the area in which this router resides contains more than 64 L1 intermediate systems accept the default value 64 1 3 6 1 4 1 18 3 5 6 1 29 Max Learned L2 Intermediate Systems 64 1 to 4000 Specifies the maximum number of L2 routers per slot that the router can learn abou
30. used to access the external domain accept the default value If there are multiple interfaces configured to the same external adjacency and you want this interface to be used regularly then assign it the lowest external address metric Similarly assign it a high cost if you do not want it to be used regularly MIB Object ID 1 3 6 1 4 1 18 3 5 6 4 7 4 28 114052 Rev A Editing OSI Parameters Copying Static External Address Adjacencies To copy a static external address adjacency 1 mo PF Y P Select the adjacency you want to copy from the list in the OSI External Address Adjacency List window refer to Figure 4 6 Click on Copy Define the external address for the new adjacency Click on Save Repeat Steps 1 4 to copy additional adjacencies Editing Static External Address Adjacencies To edit a static external address adjacency 1 Select the adjacency you want to edit from the list in the OSI External Address Adjacency List window refer to Figure 4 6 Edit the static external address adjacency parameters Click on Update to implement your changes Repeat Steps 1 3 to edit additional adjacencies Deleting Static External Address Adjacencies To delete a static external address adjacency 1 Select the adjacency you want to delete from the list in the OSI External Address Adjacency List window refer to Figure 4 6 Click on Delete The static external address adjacency is no longe
31. whether an OSI interface sends a redirect packet back to the originating system informing it of a more direct path to a destination system You should disable redirects when they are inappropriate for particular media and topology combinations For example if you are operating OSI over a Frame Relay circuit configured for group access and the underlying topology is hub and spoke you should disable redirects because the systems cannot communicate directly with each other Set this parameter to Disable to prevent redirect packets from being sent over the OSI interface 1 3 6 1 4 1 18 3 5 6 3 66 Configuring Static End System Adjacencies You must define a static end system adjacency with any end system serviced by a router that 1 resides in the same area as the OSI router 2 is reachable over a single interface and 3 does not have ISO ESIS 9542 enabled To configure a static end system adjacency 1 Select Protocols OSI Interfaces from the Configuration Manager window refer to Figure 4 1 The OSI Interface Lists window appears refer to Figure 4 3 Click on Static ES Adjacencies The OSI Static ES Adjacency List window appears Figure 4 4 It lists all defined static end system adjacencies If you did not add any end system adjacencies none will be listed 4 20 114052 Rev A Editing OSI Parameters Figure 4 4 OSI Static ES Adjacency List Window Continue to the following sections to add copy
32. 114052 Rev A 2 15 Chapter 3 Enabling OSI Services This chapter describes how to enable OSI services It assumes you have read Configuring Routers and that you have 1 Opened a configuration file in local remote or dynamic mode Remember that local mode requires that you specify router hardware 2 Selected the link or net module connector on which you are enabling OSI or configured a WAN circuit if this connector requires one When you initially enable OSI services you are required to configure only a few parameters The Configuration Manager supplies default values for the remaining parameters If you want to edit these default values refer to Chapter 4 Initial Configuration of OSI Services You enable OSI services by 1 Opening the OSI Configuration window Figure 3 1 2 Specifying the router ID See the Router ID parameter below for information 3 Clicking on OK A pop up window appears prompting Do you want to edit the OSI interface details 114052 Rev A 3 1 Configuring OSI Services 4 Clicking on Cancel to enable default OSI services and to display the next protocol specific pop up window or clicking on OK to edit the default values If you want to edit these default values refer to Chapter 4 COo IELEWIHERIIN 7 Lance Ruuter TD hes fees fdedress mex Figure 3 1 OSI Configuration Window 3 2 114052 Rev A Parameter Default Options Function Instructions MIB O
33. 13527 AFI IDI DFI ORG Rsvd RDI Area ID S 4 amp Area Address 9 pomo mum m iom mcum ei iei uni eee renim iem vns m m Cre retium gm Pere rm eri enim iue cem rt eget ees renim 1 l l l 1 IDP l DSP NSAP for I I Router in Area B 47 0005 00004e 0000 0001 AFI IDI DFI AAI Rsvd RDI Area ID S 4 Area Address OSI0010A Figure 1 9 Assigning NSAP Addresses Similarly after receiving the AAI for the campus network from the ICD 0005 subdomain the administrator assigned a full NSAP address to the router and end systems in Area C The DSP portion is structured according to ICD 0005 subdomain standard format 1 16 114052 Rev A OSI Overview OSI Basic Routing Algorithm The OSI routing algorithm is based on link state information Each OSI router periodically generates link state packets LSPs that describe the status of all of the router s immediate or adjacent data links The router propagates these link state packets throughout the network It also compiles a database of the link state information from every router and uses it to calculate the paths to all reachable destinations in the domain The OSI routing algorithm uses these three processes Update In response to changes in network topology routers transmit and receive LSPs Each time a router receives an LSP the router uses it to update its link
34. 4052 Rev A 4 5 Configuring OSI Services Parameter Default Options Function Instructions MIB Object ID Parameter Default Range Function Instructions MIB Object ID Parameter Default Range Function Instructions MIB Object ID Load Balancing False True False Specifies whether the router should balance the data traffic flow over two equal cost paths to the same destination Load balancing keeps one path from becoming overloaded while taking advantage of the bandwidth available on an additional path The paths must be of equal cost To enable load balancing reset this parameter to True 1 3 6 1 4 1 18 3 5 6 1 7 Max Area Addresses 63 1 to 1000 Specifies the maximum number of local areas in the domain Unless there are more than 63 areas in the router s domain accept the default value 63 1 3 6 1 4 1 18 3 5 6 1 8 Max End Systems 512 1 to 4000 Specifies the maximum number of end systems contained within this local area Unless there are more than 1023 end systems in the local area accept the default value 512 1 3 6 1 4 1 18 3 5 6 1 9 4 6 114052 Rev A Parameter Default Range Function Instructions MIB Object ID Parameter Default Range Function Instructions MIB Object ID Parameter Default Range Function Instructions MIB Object ID Editing OSI Parameters Max L1 Intermediate Systems 15 1 t
35. 578 Communications connectors used in LANs OSI0001A OSI Network Organization An OSI network is made up of end systems and intermediate systems routers that are organized hierarchically e End systems originate and receive data They do not perform any routing services Examples of end systems on a network include work stations file servers and printers 114052 Rev A 1 3 Configuring OSI Services Intermediate systems originate and receive data as well as forward route data The Bay Networks OSI router is an intermediate system End systems and intermediate systems are divided administratively into separate routing areas A collection of areas that are under the control of a single administration and operate common routing protocols is a routing domain A network manager defines the boundaries of routing domains An entire group of routing domains that are under one administrative authority for example a company or a university is an administrative domain Figure 1 1 Administrative Domain Routing Domain End Systems and Routers OSI0002A Figure 1 1 OSI Network Organization Level 1 and Level 2 Routing In an OSI network the router runs Connectionless mode Network Service CLNS and transfers data in a connectionless packet format using the Connectionless Network Protocol CLNP The router routes data through the network using e Level I LI routing for routing data within an area
36. NSAP destination area address fields The router compares its own NSAP area address es with the NSAP destination address contained in the packet s header If they match then the destination system is in that router s area If the addresses do not match then the destination system is located in a different area and the router must route the packet outside of the local area using L2 routing services Allocating NSAP Addresses To demonstrate how NSAP addresses are allocated Figure 1 8 shows a sample OSI network set up on a college campus in the United States To obtain and allocate NSAP addresses for the OSI network the network administrator did the following 1 Divided the campus OSI network into areas The administrator divided the campus OSI network into Areas A B and C These three areas make up the campus routing domain 114052 Rev A 1 13 Configuring OSI Services 2 Assigned identifiers to the campus routing domain and local areas as follows Campus Routing Domain Identifier 0001 Area A Identifier 0001 Area B Identifier 0002 Area C Identifier 0003 Routing Domain 0001 l AreaB 0002 L gt To External GOSIP OSI Network AreaC 0003 Key L1 L2 Router L End System OSI0009A Figure 1 8 Campus Routing Domain 3 Registered the campus network with the addressing authorities 1 14 114052 Rev A OSI Overview Because Area A and Area B are not linked to any areas ou
37. ZZ SS Where ZZZZ 0000 F 1 because the address is a logical address RRRRR is five decimal digit representation of the result r of the calculation r h 256 i note that the decimal representation of r will always require five digits ZZ 00 SS is optional The address 26 83 0 207 corresponds to the DDN X 25 logical address 000012145500 A 8 114052 Rev A IP to X 121 Address Mapping for DDN Example IP Address 26 80 0 122 Format n h l i DDN X 25 Physical ZZZZ F RRRRR ZZ SS Address Format X 121 Address 0000 1 20602 00 00 Where r h 256 i Class B For Class B IP addresses the h and i fields will always consist of 8 bits each taken from the REST field of the Internet address The mapping follows the same rules as Class A Examples For h lt 64 IP Address 137 80 1 5 Format n n h i DDN X 25 Physical ZZZZ F Il HH ZZ SS Address Format X 121 Address 0000 0 005 01 00 00 For h gt or 64 IP Address 137 80 75 2 Format n n h i 114052 Rev A A 9 Configuring OSI Services Class C DDN X 25 Physical Address Format ZZZZ i RRRRR SS X 121 Address 0000 1 19202 00 00 Where r h 256 i For Class C IP addresses the h and i fields will always consist of 4 bits each taken from the REST field of the Internet address The m
38. a ad debes Mum add 4 34 Coniquring DEDn et IV te V TEADSIUON cai ropa debet pde e io Dil eR a be totu bed E otubiSuk 4 34 Creating ihe DEGhet Pi to Y Transition oua aequ cest D t ice to n tid 4 35 Editing the DECnet IV to V Transition Parameters eee 4 35 Deleting DEC db ECREIil Pet 4 37 Delsing OSI from ihe ROUET M EO EET 4 37 Appendix A IP to X 121 Address Mapping for DDN 19095121 Address NIBBDIFIG nene NRR NS A 2 S MENTRE E ER A 2 rw cM A 3 Standard IP to X 121 Address Mapping 223 neret n tr sete ERR ANR A 7 uror mE emeneee A 7 ERAN ites et ec ene ec ie A 8 LER B saree tt ered wren reer eee mnt eee reer ener mir cena LAM Ed ener rte reer EU IDEE A 9 Class C sees Seii PE T ici deputatus ga bends P PE E T PEN A 10 114052 Rev A vii Appendix B Site Manager Default Settings for OSI Index viii 114052 Rev A Figure 1 1 Figure 1 2 Figure 1 3 Figure 1 4 Figure 1 5 Figure 1 6 Figure 1 7 Figure 1 8 Figure 1 9 Figure 1 10 Figure 1 11 Figure 1 12 Figure 1 13 Figure 2 1 Figure 2 2 Figure 2 3 Figure 2 4 Figure 2 5 Figure 2 6 Figure 2 7 Figure 2 8 Figure 2 9 Figure 2 10 Figure 3 1 Figure 4 1 Figure 4 2 Figure 4 3 Figure 4 4 114052 Rev A Figures OsrNebworoD ganz TIE adde S Ceci bot A 1 4 L1 Routing within an Area and L2 Routing between Areas 1 5 Hierarchical Addressing Authority Structure
39. able Enable Enable Disable Enables or disables the selected static route To disable the static route set to Disable 1 3 6 1 4 1 18 3 5 6 2 1 2 114052 Rev A 4 81 Configuring OSI Services Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Destination NSAP Address None Any valid NSAP address Specifies the NSAP address of the destination end system Enter the address assigned to the destination end system in hexadecimal format 1 3 6 1 4 1 18 3 5 6 2 1 4 Route Type None End System Area External Domain Specifies the route type Select the route type for this static route 1 3 6 1 4 1 18 3 5 6 2 1 6 Next Hop IS NSAP Address None Any valid NSAP address Specifies the NSAP address of the intermediate system that is the next hop on the path to the destination end system Enter the address assigned to the next hop intermediate system in hexadecimal format 1 3 6 1 4 1 18 3 5 6 2 1 5 Note The next hop that you specify for this parameter must be an intermediate system with which this router has a dynamic or static adjacency 4 32 114052 Rev A Parameter Default Range Function Instructions MIB Object ID Editing OSI Parameters Default Route Metric 20 to 1023 Specifies the defaul
40. again through LSPs and hello packets The set of all L1 L2 routers is a type of backbone network for interconnecting all areas in the domain Note that an L1 L2 router that supports L1 routing also needs to know the topology within its local area 1 26 114052 Rev A OSI Overview For example when an L1 router receives a data packet it compares the destination area address in the packet with its own area address If the destination area address is different then the packet is destined for another area and needs to be routed using L2 routing The router forwards the packet to the nearest L1 L2 router in its own area regardless of what the destination area is The L1 L2 router then forwards the packet to a peer L1 L2 router that is the next hop on the path to the destination system The packet will continue to be routed between L1 L2 routers until it reaches its destination area where it will be forwarded using L1 routing to the destination end system In Figure 1 13 demonstrates intra domain routing within Domain A and Domain B Within Domain A for example intra domain routing occurs within each area and between areas 1 and 2 Routing Domain A Routing Domain B Figure 1 13 D Area 3 Inter domain Routing Intra Domain Routing End System L1 Router L1 L2 Router L1 L2 Bordering Router OSI0014A Static Inter Domain Routing 114052 Rev A 1 27 Configuring OSI Services
41. alid Entering an invalid value can corrupt your configuration Editing OSI Global Parameters To edit the OSI global parameters 1 Select Protocols gt OSI gt Global from the Configuration Manager window refer to Figure 4 1 The Edit OSI Global Parameters window appears Figure 4 2 114052 Rev A 4 3 Configuring OSI Services Edit O50 Global Pamiara Enable Router Type a8 amp LEEI Hrarter ED Chex en 2346578 Losd Halancinmgz FALSE Ares Addresses Emi aperte Li Intermedimbe Sperber L Intermedimts Caprtemn x 8 External Addresses I5 Check Figure 4 2 Edit OSI Global Parameters Window 2 Edit the parameters using the descriptions in the next section as a guide 3 Click on OK to save your changes and exit the window Site Manager returns you to the Configuration Manager window Parameter Enable Default Enable Options Enable Disable Function Enables or disables OSI routing on the router Instructions Set to Disable only if you want to globally disable OSI routing on all interfaces on which it is configured MIB Object ID 1 3 6 1 4 1 18 3 5 6 1 2 4 4 114052 Rev A Parameter Default Options Function Instructions MIB Object ID Editing OSI Parameters Router Type Level 1 and Level 2 Level 1 Level 1 and Level 2 Specifies whether the router functions as an L1 router Level 1 or an L1 L2 router Level 1 and Level 2 An L1 router can support onl
42. ame Relay in group access mode in a hub and spoke topology because the spoke systems cannot communicate directly with each other Set the Redirect Enable Disable parameter to Disabled when operating OSI over Frame Relay in group mode in a hub and spoke topology Accept the default value Enabled in full mesh topologies 2 14 114052 Rev A OSI Implementation Notes Designated Router Selection OSI over group access Frame Relay uses the highest system ID for designated router selection This feature is needed to break a tie when the designated router priority is the same for two or more routers on a subnetwork Normally the IS IS specification in OSI calls for the comparison of local SNPA addresses in breaking ties in designated router elections but Frame Relay interfaces do not have a local SNPA address See the Update Process section of Chapter 1 for more information about designated routers IS Neighbor Detection Two way connectivity checking in adjacency establishment does not operate in OSI over group mode Frame Relay Normally two intermediate systems on an OSI broadcast subnetwork report each other in their LAN hello packets An IS must see its own subnet address in a LAN hello packet from a neighbor to form an active adjacency A local subnet address does not exist on a Frame Relay interface so this function is not used Circuits per Slot A maximum of 48 OSI interfaces per slot are supported in this release
43. apping follows the same rules as Class A Example For h 64 IP Address 192 33 50 19 Format n n n h i h i n n n 0001 0011 1 3 subnet 1 submask 3 DDN X 25 Physical ZZZZ F I HH ZZ SS Address Format X 121 Address 0000 JO 003 01 00 00 Note The mapping of X 121 address for Class C networks for h gt 64 is not applicable since the h field can never exceed 15 A 10 114052 Rev A Appendix B Site Manager Default Settings for OSI This appendix contains tables that describe the Site Manager default parameter settings for the Open System Interconnection OSI protocol Use the Configuration Manager to edit the Site Manager default settings Table B 1 OSI Initial Configuration Parameters Parameter Default Router ID None Area Address None Table B 2 OSI Global Parameters Parameter Default Enable Enable Router Type Level 1 amp Level 2 Router ID Router ID set at initial configuration Load Balancing Disable Max Area Addresses 63 areas Max End Systems 512 systems Max L1 Intermediate 15 systems Systems Max L2 Intermediate 63 systems Systems Max External Addresses 1 address continued 114052 Rev A B 1 Configuring OSI Services Table B 2 OSI Global Parameters continued Parameter Default IS Checksum Enable L1 LSP Password None L2 LSP Pas
44. ara California e Sydney Australia e Tokyo Japan e Valbonne France The Technical Response Centers are connected via a redundant Frame Relay Network to a Common Problem Resolution system enabling them to transmit and share information and to provide live around the clock support 365 days a year Bay Networks Information Services complement the Bay Networks Service program portfolio by giving customers and partners access to the most current technical and support information through a choice of access retrieval means These include the World Wide Web CompuServe Support Source CD Customer Support FTP and InfoFACTS document fax service 114052 Rev A xvii Configuring OSI Services Bay Networks Customer Service If you purchased your Bay Networks product from a distributor or authorized reseller contact that distributor s or reseller s technical support staff for assistance with installation configuration troubleshooting or integration issues Customers can also purchase direct support from Bay Networks through a variety of service programs As part of our PhonePlus M program Bay Networks Service sets the industry standard with 24 hour 7 days a week telephone support available worldwide at no extra cost Our complete range of contract and noncontract services also includes equipment staging and integration installation support on site services and replacement parts delivery within approximately 4 hours To purchas
45. arts 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 nets you enter either show at routes or show at nets but not both Xiv 114052 Rev A Acronyms AAI ACSE AFI ANSI ARP ASN 1 CLNP CLNS CSNP DCA DCC DCE DDN DFI DLCI DSP DTE ES IS FDDI FTAM GOSIP GSA HDLC ICD IDI IDP IEEE ILI IP IS IS ISO About This Guide Administrative Authority Identifier Association Control Service Element Authority and Format Identifier American National Standards Institute Address Resolution Protocol Abstract Syntax Notation One Connectionless Network Protocol Connectionless mode Network Service Complete Sequence Number Packets Defense Communication Agency Data Country Code Data Circuit Terminating Equipment Defense Data Network Domain Format Identifier Data Link Connection Identifier Domain Specific Part Data Circuit Terminating Equipment End System to Intermediate System Fiber Distributed Data Interface File Transfer Access Management Government OSI Profile General Services Administration High Level Data Link Control International Code Designator Initial Domain Identifier Initial Domain Part Institute of Electrical and Electronic Engineers Intelligent Link Interface Internet Protocol Intermediate System to Intermediate System International Organization for Standardization 114052 Rev
46. ation The translation method described below is totally independent of IP subnetting and of any masking that may be used in support of IP subnetting MIL STD X 25 Defense Data Network X 25 Host Interface Specification Defense Communications Agency BBN Communications Corporation 1983 December Volume 1 of the DDN Protocol Handbook NIC 50004 Also available on line at the DDN NIC as NETINFO X 25 DOC A 2 114052 Rev A IP to X 121 Address Mapping for DDN Background All Internet hosts are assigned a four octet 32 bit address composed of a network field and a local address field also known as the REST field refer to Figures A 1 through A 3 Two basic forms of addresses are provided 1 physical addresses which correspond to the node number and DCE port number of the node to which the DTE is connected and 2 logical addresses which are mapped transparently by DCE software into a corresponding physical network address To provide flexibility Internet addresses are divided into three primary classes Class A Class B and Class C These classes allow for a large number of small and medium sized networks The network addresses used within the Internet in Class A B and C networks are divided between Research Defense Government Non Defense and Commercial uses As described in the MIL STD X25 an IP address consists of the ASCII text string representation of four decimal numbers separated by periods correspond
47. ay Networks in writing of any such intended examination of the Software and Bay Networks may provide review and assistance Notwithstanding any foregoing terms to the contrary if licensee licenses the Bay Networks product Site Manager licensee may duplicate and install the Site Manager product as specified in the Documentation This right is granted solely as necessary for use of Site Manager on hardware installed with licensee s network This license will automatically terminate upon improper handling of Software such as by disclosure or Bay Networks may terminate this license by written notice to licensee if licensee fails to comply with any of the material provisions of this license and fails to cure such failure within thirty 30 days after the receipt of written notice from Bay Networks Upon termination of this license licensee shall discontinue all use of the Software and return the Software and Documentation including all copies to Bay Networks Licensee s obligations under this license shall survive expiration or termination of this license 114052 Rev A Contents About This Guide Bere VOU BON gao a srk ttt rr Rond Quo crt a rrr cl du aU ER AR Uu Loan tre xiii CONIA IOUS ocsdisdesnriunteleuedcsndtus eet ee E AE aceasta E E T xiv IGI SS ease dias A A eiat dd e DP Pri wd T IA MIE A eaa ETE O E xd ita Sap ce edi XV Ordering Bay Networks Publications sis sisccasascugerscez sinner innana nhai aux dta mnacieasnmenie xvi Te
48. bject ID Parameter Default Options Function Instructions MIB Object ID Enabling OSI Services Router ID Variable Any valid 6 byte system ID Identifies the router within its local area The system ID is the ID portion of the router s NSAP address See Chapter 1 for more information You specify a router ID only the first time you configure an OSI interface Site Manager uses this router ID for any additional OSI interfaces you configure Enter a system ID in hexadecimal format The router ID must be exactly 6 bytes Note the following guidelines Every router in a domain must have a unique system ID Using a router s MAC address for its system ID ensures this If this router is located in an area that also supports DECnet Phase IV end systems then the system ID must be within the DECnet Phase IV legal range that is Ox1 to Ox3ff hexadecimal 1 3 6 1 4 1 18 3 5 6 1 6 Area Address None Any valid OSI address in hexadecimal notation Identifies the OSI area to which this interface belongs Enter the appropriate area ID in hexadecimal notation 1 3 6 1 4 1 18 3 5 6 1 16 114052 Rev A 3 3 Chapter 4 Editing OSI Parameters Once you enable an OSI interface you can use Site Manager to edit OSI parameters and customize OSI services This chapter describes how to e Edit OSI parameters e Add edit or delete a static route static adjacency or the DECnet IV to V Transition feature e
49. cal Address 14 bits 16 bits Rest field OSI0025A Figure A 2 Class B Internet Address 114052 Rev A A 5 Configuring OSI Services Class C e The three highest order bits are set to 1 1 0 e 2 bits define the network number e 8 bits define the local address e This allows up to 2 097 152 Class C networks Network Local Address 21 bits 8 bits Rest field OSI0026A Figure A 3 Class C Internet Address The fourth type of address Class D is used as a multicast address The four highest order bits are set to 1 1 1 0 Note No addresses are allowed with the four highest order bits set to 1 1 1 1 These addresses called Class E are reserved The MIL STD X 25 states that All DDN addresses are either twelve or fourteen BCD binary coded decimal digits in length The last two digits are referred to as the Sub Address and are not used on the DDN The Sub Address is carried across the network without modification Its presence is optional Therefore a DTE may generate either twelve or fourteen BCD X 121 address but must accept both twelve and fourteen BCD X 121 addresses A 6 114052 Rev A IP to X 121 Address Mapping for DDN Standard IP to X 121 Address Mapping Class A This section describes the algorithm that you use to convert IP addresses to X 121 addresses Note that h is always listed as greater than or less than the number 64 This number is used to differentiate between PSN phy
50. chnical Support and Online Services Bay Networks Customer Senie Me xviii Bay Networks Intorraalion Services icai en i eret ni reaa AR XIX Woa NE Na E E E ELSE SETS xix Customer Seite dj erre cau renter r E xix cli a als fils sto Eds a esed meee errr eeepc ead edi eer mr nr eer mt rreee rete XX DanpuS Sl Vll crises T TEE XX Jule pip P Jw xxi o 35 MS acs nite ETT xxi Chapter 1 OSI Overview O51 Basie Reietence Model me De ie aeia 1 2 OSI Network Organization E E E E E E E E E T PEEN 1 3 Level 1 and Level 2 ROUNO sceradxmecc er nece metet ote Edad TE 1 4 Lever TROUD ENT EO 1 5 Level 2 lIpopc t T 1 6 CSI NEDVSIK Address iieri reete do e ee tace id eei radere edo cu 1 6 NSAP Structure docs 1 7 Allocating NSAP BOOBS SS E 1 13 OSI Basic FLUENCY AIO sad uses ca lati io crash D euaa dase ncaa aa e oes und chi 1 17 MCAS PIOOSSS suele sani deno nit epp RU esM Fam soalucncut STU este iced ies 1 18 Ro en gos c AM e T 1 20 lass aN d uio rs ci RR RENS RIEN e c er Sm 1 21 114052 Rev A V EST outil PEDIDOS casis d tradi i ar OF EER pc cip aa para gt rci pira duda n b RN uci 1 22 Connectionless mode Network Service Protocol sss 1 22 End System to Intermediate System Routing Exchange Protocol 1 23 ionge REDOT cocer hc aH SR a ER baee od Ao s Rd 1 23 Rou
51. dge 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 114052 Rev A Bay Networks Software License Note This is Bay Networks basic license document In the absence of a software license agreement specifying varying terms this license or the license included with the particular product shall govern licensee s use of Bay Networks software This Software License shall govern the licensing of all software provided to licensee by Bay Networks Software Bay Networks will provide licensee with Software in machine readable form and related documentation Documentation The Software provided under this license is proprietary to Bay Networks and to third parties from whom Bay Networks has acquired license rights Bay Networks will not grant any Software license whatsoeve
52. dressing domains which can be further divided into various subdomains A network addressing domain is a set of NSAP addresses regulated by the same addressing authority The addressing authority is the administration responsible for allocating unique NSAP addresses to OSI networks Each addressing authority operates independently of other authorities at the same level An addressing authority for a higher domain can authorize the addressing authorities for its subdomains to assign NSAP addresses Figure 1 3 The subdomain specifies the format of the NSAP addresses allocated to the network Two of the addressing authorities that administer NSAP addresses for OSI networks in the United States are the United States General Services Administration GSA which allocates NSAPs that are intended primarily for government use and the American National Standards Institute ANSI 1 6 114052 Rev A OSI Overview Global Network Addressing Domain Domain Addressing Authority A Domain Addressing Authority B Subdomain Subdomain Subdomain Subdomain Addressing Addressing Addressing Addressing Authority A 1 Authority A 2 Authority B 1 Authority B 2 OSI0004A Figure 1 3 Hierarchical Addressing Authority Structure NSAP Structure The basic NSAP address structure reflects the hierarchal assignment of NSAPs throughout the global network addressing domain NSAP addresses must be globally unique They can be up to 20 bytes long and contain two bas
53. e any of the Bay Networks support programs or if you have questions on program features use the following numbers Region Telephone Number Fax Number United States and 1 800 2LANWAN enter Express Routing 508 670 8766 Canada Code ERC 290 when prompted 508 436 8880 direct Europe 33 92 968 300 33 92 968 301 Asia Pacific Region 612 9927 8800 612 9927 8811 Latin America 407 997 1713 407 997 1714 In addition you can receive information on support programs from your local Bay Networks field sales office or purchase Bay Networks support directly from your authorized partner xviii 114052 Rev A Technical Support and Online Services Bay Networks Information Services Bay Networks Information Services provide up to date support information as a first line resource for network administration expansion and maintenance This information is available from a variety of sources World Wide Web The Bay Networks Customer Support Web Server offers a diverse library of technical documents software agents and other important technical information to Bay Networks customers and partners A special benefit for contracted customers and resellers is the ability to access the Web Server to perform Case Management This feature enables your support staff to interact directly with the network experts in our worldwide Technical Response Centers registered contact with a valid Site ID can e View
54. e destination address of the external adjacency Enter the address assigned to the external adjacency in hexadecimal format 1 3 6 1 4 1 18 3 5 6 4 5 SNPA None Depends on the circuit type see Instructions Specifies an SNPA for the adjacent end system Enter the SNPA for the adjacent end system as follows fthis circuit is an X 25 PDN circuit then enter a valid X 121 address for the remote router in decimal format If this circuit is an X 25 DDN circuit then enter a valid X 121 address for the remote router in decimal format 114052 Rev A 4 27 Configuring OSI Services If this circuit uses PPP then leave this field blank If this circuit is of any other type then enter any valid MAC address MIB Object ID 1 3 6 1 4 1 18 3 5 6 4 6 Note To enter a valid X 121 address for an X 25 DDN circuit you must convert the remote IP address to an X 121 address See Appendix A for the conversion algorithm Parameter External Address Metric Default 20 Range 1to 63 Function Specifies the relative cost of using this interface to reach the external adjacency If there are multiple interfaces configured to the same external adjacency the OSI router will route all external domain traffic using the interface that has been assigned the lowest external address metric Instructions If you only have a single link to the external adjacency or have no preference regarding which interface is
55. elay 2 9 Pseudonode 1 18 R Record route options 1 22 Redirection 1 24 2 14 4 20 Relative cost 1 20 Routing domain 1 4 Routing process 1 21 Routing protocols 1 22 Index 4 114052 Rev A S Shortest path first algorithm 1 20 Source routing 1 22 Static end system adjacency adding 4 21 configuring 4 20 to 4 24 copying 4 24 deleting 4 24 editing 4 24 Static end system adjacency parameters Enable 4 22 ESID 4 23 SNPA 4 23 Static external address adjacency adding 4 26 configuring 4 25 to 4 29 copying 4 29 deleting 4 29 editing 4 29 Static external address adjacency parameters Enable 4 27 External Address 4 27 External Address Metric 4 28 SNPA 4 27 Static external adjacencies configuring 2 7 Static external adjacency parameters SNPA 2 7 Static route adding 4 30 configuring 4 30 to 4 34 copying 4 33 deleting 4 34 editing 4 33 Static route parameters Default Route Metric 4 33 Destination NSAP Address 4 32 Enable 4 31 Next Hop IS NSAP Address 4 32 Route Type 4 32 Support Source CD xx Index T Timers 1 24 4 18 Topology 2 12 to 2 14 and area partitions 2 6 hub and spoke 2 13 partial mesh 2 13 Total path cost 1 20 W World Wide Web Bay Networks home page on XIX X X 121 address conversion algorithm A 7 to A 10 X 25 network 2 7 114052 Rev A Index 5
56. em S Level 1 Router gl Leve 1 Router OSI0016A Figure 2 2 Assign Area Address Alias 456 to All Routers in Area XY 2 Assigns the area address alias 456 to those end systems that will eventually belong to area Y when area XY is divided Figure 2 3 Unchanged end systems are still able to communicate using the originally assigned area address 123 so this can be done gradually 114052 Rev A 2 3 Configuring OSI Services Area XY Assign area address alias 456 to specific end systems Key End System L Level 1 Router Bl eve 1 Router OSI0017A Figure 2 3 Assign Area Address 456 to Specific End Systems 3 Finally to divide Area XY completely deletes area address alias 456 from those routers that will remain in area X and deletes area address 123 from those routers and end systems that will be part of the new area Y Because the end systems in both area X and area Y have already been assigned corresponding area addresses they do not have to be reconfigured and the division is complete Figure 2 4 2 4 114052 Rev A OSI Implementation Notes Delete 456 from Systems in X Delete 123 from systems in Y Key End System Level 1 Router HE eve 1 Router OSI0018A Figure 2 4 Divide Area XB into Area X and Area Y See Editing OSI Interface Parameters in Chapter 4 for instructions
57. essing on each packet allowing Frame Relay networks to operate at high speeds with few delays but with little error detection See Configuring Frame Relay Services for general information about the protocol Configuration Overview If you want to run OSI over Frame Relay you must 1 Configure a Frame Relay circuit using Site Manager See Configuring Frame Relay Services for Frame Relay configuration information Configure OSI to operate over Frame Relay See Chapter 3 for initial OSI configuration information Customize Frame Relay and OSI for your network s circuit mode and topology See the following sections for information on running OSI over Frame Relay based on the circuit mode and topology of your network In direct access mode repeat Steps 1 through 3 for each permanent virtual circuit PVC See the Direct Access section 2 8 114052 Rev A OSI Implementation Notes Frame Relay Circuit Modes Our implementation of OSI over Frame Relay operates as a subnetwork in either of these two types of Intermediate System to Intermediate System IS IS operation modes e Point to Point e Broadcast The OSI router implements these IS IS operation modes over Frame Relay circuits Table 2 1 lists the Frame Relay modes used for IS IS operations Table 2 1 Frame Relay Modes Used for OSI IS IS Operations Frame Relay Mode IS IS Operation Mode Direct access Point to Point Group access Broadcast H
58. floods it to all other L1 routers in the area Each router that receives the LSP uses it to update its link state database then floods it out all interfaces except for the one that it was received on Area A VP To other L1 Routers in Area A End System L1 Router New End System p LSP Path OSIO011A Figure 1 10 Router 1 Floods Area A with LSPs about the new End System Similarly if a new L1 L2 router is added to the network L1 L2 routers flood both L1 and L2 LSPs throughout the domain When an L1 L2 router receives a new LSP it updates its corresponding L1 or L2 link state database with the new information The router then forwards the LSP on all links except the one that it was received on Note that the L1 L2 routers that support both types of traffic maintain separate L1 and L2 link state databases 114052 Rev A Configuring OSI Services The router refers to its link state database s when deciding the shortest path between itself and all other routers it can reach Decision Process During the decision process the OSI router uses the link state database information that it has accumulated during the update process to e Define a set of paths to every reachable destination in the domain e Calculate the shortest path to each destination e Record the identity of the first hop on the shortest path to each destination into a forwarding database The router uses a shortest path first
59. ge Click on Apply to implement your changes Repeat Steps 1 3 to edit additional static adjacencies Click on Done to exit the window Deleting a Static End System Adjacency To delete a static end system adjacency 1 Select the adjacency you want to delete from the list in the OSI Static ES Adjacency List window refer to Figure 4 4 Click on Delete The static end system adjacency is no longer listed Repeat Steps 1 and 2 to delete additional adjacencies Click on Done to exit the window 4 24 114052 Rev A Editing OSI Parameters Configuring Static External Address Adjacencies You configure static external adjacencies to enable interdomain routing routing between domains To configure a static external address adjacency 1 Select Protocols OSI Interfaces from the Configuration Manager window refer to Figure 4 1 The OSI Interface Lists window appears refer to Figure 4 3 2 Click on External Address Adjacency The OSI External Address Adjacency List window appears refer to Figure 4 6 It lists all defined external address adjacencies If you did not add any adjacencies none will be listed Externas fdiress Sete ic Figure 4 6 OSI External Address Adjacency List Window Note To configure static external address adjacencies for the OSI interface set the Routing Level parameter in the OSI Interface Lists window to an option that includes External for example Level 2 and Ex
60. gn to a particular circuit typically reflects the speed of the transmission medium Low costs reflect high speed media while high costs reflect slower media Refer to Table 4 1 for a list of suggested OSI circuit costs The OSI router always selects the interfaces with the lowest cost when defining a path so assigning each interface a cost is in effect a way of assigning it a priority If you do not want this interface to route Level 2 traffic on a regular basis assign it a high cost Otherwise accept the default 20 1 3 6 1 4 1 18 3 5 6 3 7 L1 Designated Router Priority 64 1 to 127 Specify which L1 router becomes the L1 designated router for the LAN segment See the section entitled Update Process in Chapter 1 for more information about the designated router You can control which L1 router becomes the L1 designated router for the LAN segment by assigning a priority value to each L1 router Then the L1 router assigned the highest priority becomes the L1 designated router for that LAN segment If all routers have the same priority then the L1 router with the highest MAC address becomes the L1 designated router for the LAN segment If you want this L1 router to become the L1 designated router for the LAN segment then assign it the highest priority value among L1 routers on the LAN 1 3 6 1 4 1 18 3 5 6 3 8 4 16 114052 Rev A Editing OSI Parameters then the routers on each end of the connection must ha
61. hat interface Parameter Enable Default Enable Options Enable Disable Function Enables OSI routing on this interface Instructions Disable only if you want to disable OSI routing on this interface MIB Object ID 1 3 6 1 4 1 18 3 5 6 3 2 Parameter Routing Level Default Level 1 and Level 2 Options Level 1 Level 21 Level 1 and Level 2 External L2 External L1 and L2 External ES IS only Function Specifies the type of traffic that is routed over this interface Instructions Select the routing level that matches the level of traffic you want to route MIB Object ID on this interface Note that if you set the global Router Type parameter to Level 1 then you can only route Level 1 traffic on this interface See Editing OSI Global Parameters earlier in this chapter for instructions on setting the global Router Type parameter If this interface will route traffic between domains then select an option that includes External In addition you must statically define the external adjacencies with which this router communicates See Configuring Static External Address Adjacencies later in this chapter for instructions 1 3 6 1 4 1 18 3 5 6 3 5 4 14 114052 Rev A Parameter Default Range Function Instructions MIB Object ID Editing OSI Parameters L1 Default Metric 20 to 63 Specifies the default metric relative cost of routing Level 1 traffic over this interface OSI
62. he network into routing domains and areas Rsvd 0000 Indicates that this field is reserved RDI variable Identifies the routing domain where the NSAP resides assigned by the authority identified in the ORG field Area variable Specifies the local area where the NSAP resides assigned by either the authority identified in the ORG field or the local administrative authority that the ORG authority has delegated to this routing domain ID variable Identifies the system where the NSAP resides assigned by the local area administrator that a higher authority has delegated to this area S 0 or 1 Selects the transport layer entity the system uses This entity is specified in the ID field The IDP and the first part of the DSP called the high order part of the DSP are the NSAP s area address The area address identifies the area in an OSI network where an NSAP resides refer to Figure 1 7 1 12 114052 Rev A OSI Overview 48 Area Address M Organization Identifier Initial Domain part Reserved Domain Specific Part Routing Domain Identifier Area Identifier Authority and Format Identifier Initial Domain Identifier System Identifier Domain Format Identifier NSAP Selector Administrative Authority Identifier OSI0008A Figure 1 7 NSAP Area Address When a router receives a packet it examines the contents of the packet s
63. ic parts the Initial Domain Part IDP and the Domain Specific Part DSP Figure 1 4 114052 Rev A 1 7 Configuring OSI Services IDP AFI IDI DSP Domain Specific Part Figure 1 4 Initial Domain part Authority and Format Identifier Intitial Domain Identifier OSIOO0SA Basic NSAP Address Structure The IDP consists of an Authority and Format Identifier AFD and an Initial Domain Identifier IDI The AFI is 1 octet in length and specifies the format of the IDI the network addressing authority responsible for allocating values to the IDI and the abstract syntax of the DSP The IDI is variable in length It specifies the addressing authority responsible for allocating values to the DSP and the subdomain from which they come The authority identified by the IDI determines the structure and semantics of the DSP For example if you register your OSI network with the GSA it will probably assign your network to the ISO International Code Designator ICD 0005 subdomain The DSP portion of the NSAP addresses allocated from this subdomain follows the Government OSI Profile Version 2 structure illustrated in Figure 1 5 1 8 114052 Rev A Figure 1 5 OSI Overview Initial Domain part Reserved Domain Specific Part Routing Domain Identifier Authority and Format Identifier Area Identifier Initial Domain Identifier System Identifier Domain Format Identifier NSAP Selector Administrative Authority Identifier
64. igure 1 11 Lowest Cost Path Router A to B to ES Once the router determines the lowest cost path to a destination it stores the identity of the corresponding adjacent router into its forwarding database The adjacent router is the next hop on the path toward the destination The router executes the decision process separately for each routing level and keeps separate forwarding databases for L1 and L2 routing It uses the L1 link state database to calculate the L1 forwarding database which describes the shortest paths to destination systems located in the same area If a router also routes L2 traffic it uses its L2 link state database to create an L2 forwarding database which describes the shortest paths to other destination areas The OSI router bases its routing decisions on the most current network topology its link state database is updated every time the network changes Forwarding Process The OSI router begins the forwarding process after it receives a packet First it examines the destination address contained in the packet to determine whether the packet requires L1 routing or L2 routing It then refers to the corresponding forwarding database for information on where to forward the packet Ifthe router is an L1 router and the packet s destination address is within the local area the router checks its L1 forwarding database and forwards the packet to the next hop along the path to the destination If the destination addres
65. iguring Routers 114052 Rev A xiii Configuring OSI Services Conventions angle brackets gt bold text brackets ellipsis points italic text quotation marks screen text separator gt vertical line I Indicate that you choose the text to enter based on the description inside the brackets Do not type the brackets when entering the command Example if command syntax is ping lt p_address gt you enter ping 192 32 10 12 Indicates text that you need to enter command names and buttons in menu paths Example Enter wfsm amp Example Use the dinfo command Example ATM DXI gt Interfaces gt PVCs identifies the PVCs button in the window that appears when you select the Interfaces option from the ATM DXI menu Indicate optional elements You can choose none one or all of the options Horizontal and vertical ellipsis points indicate omitted information Indicates variable values in command syntax descriptions new terms file and directory names and book titles Indicate the title of a chapter or section within a book Indicates data that appears on the screen Example Set Bay Networks Trap Monitor Filters 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 Indicates that you enter only one of the p
66. ing to the four octets of a thirty two bit Internet address The four decimal numbers are referred to in this appendix as network n host h logical address 1 and Interface Message Processor IMP or Packet Switch Node PSN i Thus an Internet address may be represented as n h l i Class A n n h i Class B or n n n hi Class C depending on the Internet address class Each of these four numbers will have one two or three decimal digits and will never have a value greater than 255 For example in the Class A IP address 26 9 0 122 n 26 h 9 l 0 and i 122 MIL STD 1777 Internet Protocol 1983 August Volume 1 of the DDN Protocol Handbook NIC 50004 114052 Rev A A 3 Configuring OSI Services The different classes of Internet addresses are illustrated Class A e The highest order bit is set to 0 e 7 bits define the network number e 24 bits define the local address e This allows up to 126 Class A networks e Networks 0 and 127 are reserved Network Local Address 7 bits 24 bits Rest field OSI0024A Figure A 1 Class A Internet Address Kirkpatrick S M Stahl and M Recker Internet Numbers RFC 1166 DDN NIC July 1990 A 4 114052 Rev A IP to X 121 Address Mapping for DDN Class B e The two highest order bits are set to 1 0 e 14 bits define the network number e 16 bits define the local address e This allows up to 16 384 Class B networks Network Lo
67. interface 4 13 to 4 19 enabling Area Address 3 3 Router ID 3 3 global Area Address 4 10 Area Address Alias 1 4 11 Area Address Alias 2 4 11 CLNP Source Route Support 4 12 Enable 4 4 IS Checksum 4 8 L1 LSP Password 4 8 L2 LSP Password 4 9 Load Balancing 4 6 Max Area Addresses 4 6 Max End Systems 4 6 Max External Addresses 4 7 Max L1 Intermediate Systems 4 7 Max L2 Intermediate Systems 4 7 Max Learned End Systems 4 11 Max Learned L1 Intermediate Systems 4 12 Max Learned L2 Intermediate Systems 4 12 Router ID 4 5 Router Type 4 5 interface Circuit Password 4 19 Enable 4 14 ESH Configuration Time 4 18 IIH Hello Timer 4 18 IIH Hold Time Multiplier 4 19 ISH Hello Timer 4 18 ISH Hold Time Multiplier 4 19 L1 Default Metric 4 15 4 16 OSI parameters continued L1 Designated Router Priority 4 16 L2 Designated Router Priority 4 17 Redirect Enable Disable 4 20 Routing Level 4 14 static end system adjacency Enable 4 22 ESID 4 23 SNPA 4 23 static external address adjacencies Enable 4 27 External Address 4 27 static external address adjacency External Address Metric 4 28 SNPA 4 27 static route Default Route Metric 4 33 Destination NSAP Address 4 32 Enable 4 31 Next Hop IS NSAP Address 4 32 Route Type 4 32 P Partial mesh topology 2 13 Partition area 2 5 Password 4 8 4 9 4 19 Path costs 4 15 Point to point mode and direct access mode 2 10 and Frame R
68. itate the routing and relaying functions of the network layer ISO 10589 Intermediate System to Intermediate System Routing Exchange Protocol which defines how L1 and L2 routing works Connectionless mode Network Service Protocol Connectionless mode Network Service Protocol ISO 8473 is the network layer protocol that specifies the procedures for the connectionless transmission of data and control information from one network system to a peer network system using CLNP packets An OSI router processes each CLNP packet it receives independently and does not require an established network connection router bases its decision on how to process a CLNP packet solely on the information found in the packet header The header information tells the router whether the packet has reached its destination or requires additional processing 1 22 114052 Rev A OSI Overview A router partitions a CLNP packet into two or more new packets segments if the size of the packet is greater than the maximum size supported by the outbound network The values contained in the header fields of the segmented packets are identical to those contained in the original packet except for the segment length and checksum fields The router sends the partitioned packets out on the network When all of the packet segments finally arrive at the destination system the system reconstructs the original packet before sending it up to the next layer for further proces
69. nerates and accepts The router uses LSP information to make routing decisions and PSNP and CSNP information to make sure that its LSP database is up to date You use the L1 LSP password as a security device for restricting the routing of data If you add a password to LSPs from a router only routers with the password accept and exchange LSPs To restrict routing you assign identical L1 LSP passwords to all routers located in the area through which you wish to route data When the OSI router floods Level 1 LSPs through the area only those routers with the same password accept the LSPs If you do not want to assign an L1 LSP password to this router then leave this field blank If you assign an L1 LSP password to this router then you must assign the same L1 LSP password to every router in the area with which this router communicates 1 3 6 1 4 1 18 3 5 6 1 14 4 8 114052 Rev A Editing OSI Parameters Parameter L2 LSP Password Default None Options Any text string 8 characters maximum Function X Assigns a password to the Level 2 link state packets LSP partial sequence number packets PSNP and complete sequence number packets CSNP that the router L1 L2 generates and accepts The router uses LSP information to make routing decisions and PSNP and CSNP information to make sure that its LSP database is up to date You use the L2 LSP password as a security device for restricting the routing of data If you add a passwo
70. nfiguration Chapter 4 procedures review the following sections in this chapter for information that might affect your network Configuring Area Address Aliases Correcting Partitioned Areas Configuring Static External Adjacencies Configuring OSI over DDN X 25 Configuring DECnet IV to V Transition Configuring OSI over Frame Relay 114052 Rev A 2 1 Configuring OSI Services Configuring Area Address Aliases You configure area address aliases if you plan on dividing a large area into two or more smaller areas An area address alias is a second or third area address configured for systems residing in a single area When used appropriately the area address alias feature can make network management easier For example consider the OSI network shown in Figure 2 1 All routers and end systems belong to the area XY This area had originally been assigned the area address 123 Sometime in the near future the network administrator plans to divide the area into two smaller more manageable areas Area X and Area Y Area XY C End System Level 1 Router B Level 1 Router OSI0015A Figure 2 1 Original Area Addresses for Area XY Taking advantage of the area address alias feature the administrator 1 Assigns the area address alias 456 to all routers within area XY Figure 2 2 2 2 114052 Rev A OSI Implementation Notes Area XY Assign area address alias 456 to all routers in XY Key End Syst
71. nsition Parameters Parameter Default DECnet 4 to 5 Transition Enable Disable Area Address Alias 1 hex None B 4 114052 Rev A A Address conversion 2 7 Addressing authority 1 6 Administrative domain 1 4 ANSI 1 6 Area address 1 12 to 1 13 Area address alias 2 2 to 2 5 Area partition 2 5 Areas 1 4 Bay Networks CompuServe forum xx Customer Service FTP xix home page on World Wide Web xix InfoFACTS service xxi publications ordering xvi support programs xviii Support Source CD xx Technical Response Center xvii xxi technical support xvii Broadcast mode and Frame Relay 2 9 and group access 2 10 C Circuit costs See Path costs Circuit modes 2 9 to 2 11 Circuits 2 15 Class of Internet address A 3 CompusServe Bay Networks forum on xx Index Configuration initial 3 1 network 2 1 OSI over Frame Relay 2 8 to 2 15 Configuration reports 1 23 Configuration timer 1 24 Connectionless Network Protocol 1 4 Connectionless mode Network Service Protocol 1 4 1 22 to 1 23 4 12 Cost metric 1 20 Customer Service FTP xix Customer support See getting help D DECnet IV to V Transition feature configuring 4 34 to 4 37 deleting 4 37 editing 4 35 to 4 37 DECnet IV to V Transition parameters Area Address Alias 1 4 37 Enable 4 36 Defaults for OSI parameters B 1 Defense Data Network DDN A 2 configuring OSI over X 25 2 7 Designated router 1 18 selection in
72. ntifier NSAP Selector OSI0007A ANSI NSAP Address Format The AFI for these NSAP addresses is 39 which shows that the network is registered with ANSI and belongs to a DCC subdomain The IDI is 840 specifying the DCC 840 subdomain which is reserved for use by networks located in the United States The DFI is not standardized and is assigned by the DCC 840 subdomain The Organization ORG Identifier portion of the NSAP address is a globally unique number that is assigned by the DCC 840 subdomain It identifies the network within the DCC 840 subdomain where the NSAP resides and the authority responsible for organizing the network into routing domains and areas The Organization Identifier serves the same purpose as the Administrative Authority portion of a NSAP assigned by the ICD 0005 subdomain refer to Table 1 2 Table 1 3 describes the contents of each field for this type of NSAP address 114052 Rev A Configuring OSI Services Table 1 3 NSAP Address Structure Assigned by the DCC 840 Subdomain Field Name Value Meaning AFI 39 Identifies the subdomain as DCC 840 Specifies the syntax of the DSP as binary octets IDI 840 Indicates that the subdomain is DCC 840 DFI variable Identifies the format of the DSP The subdomain identified in the IDI specifies this value ORG variable Specifies the network within the DCC 840 subdomain where the NSAP resides and the authority responsible for organizing t
73. o 1000 Specifies the maximum number of Level 1 OSI routers contained within this local area Unless there are more than 15 Level 1 OSI routers in this local area accept the default value 15 1 3 6 1 4 1 18 3 5 6 1 10 Max L2 Intermediate Systems 63 1 to 1000 Specifies the maximum number of L1 L2 OSI routers contained within this local area Unless there are more than 63 L1 L2 OSI routers in this local area accept the default value 63 1 3 6 1 4 1 18 3 5 6 1 11 Max External Addresses 1 1 to 500 Specifies the number of external domain addresses imported into the local domain If you do not have any links to external domains then accept the default value 1 Otherwise enter the maximum number of external domains linked to the local domain 1 3 6 1 4 1 18 3 5 6 1 12 114052 Rev A 4 7 Configuring OSI Services Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID IS Checksum Enable Enable Disable Enables or disables the generation of a non zero checksum for IS packets To allow checksum processing accept the default value Enable 1 3 6 1 4 1 18 3 5 6 1 13 L1LSP Password None Any text string 8 characters maximum Assigns a password to the Level 1 link state packets LSP partial sequence number packets PSNP and complete sequence number packets CSNP that the router L1 or L1 L2 ge
74. omer Support Bulletins Release Notes software patches and fixes and complete information on all Bay Networks Service programs You can run a single version on Macintosh Windows 3 1 Windows 95 Windows NT DOS or UNIX computing platforms A Web links feature enables you to go directly from the CD to various Bay Networks Web pages CompuServe For assistance with noncritical network support issues Bay Networks Information Services maintain an active forum on CompusServe a global bulletin board system This forum provides file services technology conferences and a message section to get assistance from other users The message section is monitored by Bay Networks engineers who provide assistance wherever possible Customers and resellers holding Bay Networks service contracts also have access to special libraries for advanced levels of support documentation and software To take advantage of CompuServe s recently enhanced menu options the Bay Networks Forum has been re engineered to allow links to our Web sites and FTP sites We recommend the use of CompuServe Information Manager software to access these Bay Networks Information Services resources To open an account and receive a local dial up number in the United States call CompuServe at 1 800 524 3388 Outside the United States call 1 614 529 1349 or your nearest CompuServe office Ask for Representative No 591 When you are on line with your CompuServe account you can reach u
75. on how to configure area address alias parameters Correcting Area Partitions An area is partitioned when one or more nodes cannot communicate with other nodes in the area either directly or indirectly at Level 1 Partitions happen through improper network design or when one or more links fail in an area Area partition repair as specified in ISO 10589 Intermediate System to Intermediate System Routing Exchange Protocol is currently not supported by this implementation of OSI See Chapter 1 for information on the role of areas and Level 1 and 2 routing in OSI network organization 114052 Rev A 2 5 Configuring OSI Services Figure 2 5 Figure 2 5 demonstrates an improper network design Area 490130 Router A JL Router C Router B Area 490050 Partition 2 Area 490050 Partition 1 OSI0022A Routers B and C in an Area Partition Due to Improper Network Design In this hub and spoke topology Router A in Area 490130 recognizes two separate routes to Area 490050 Routers B and C do not have a Level 1 link between them therefore each is in a different partition of the area They cannot exchange Level 1 information and neither one knows about end systems in the other partition If Router A sends a
76. packet to an end system in Area 490050 it may choose Router B in Partition 1 as the lowest cost route If the packet is intended for an end system attached to Router C Router B will reject the packet because it does not know about the end system in Partition 2 One solution is to modify the topology by creating a link between Routers B and C Another solution is to create another area for Router C or B the routers could then use Level 2 routing to communicate 2 6 114052 Rev A OSI Implementation Notes Configuring Static External Adjacencies A static external adjacency links an L1 L2 router to an address in an external domain to route traffic between the domains To configure one you must Configure external routing support on each interface that connects the L1 L2 router to an external domain You do this by setting the Routing Level parameter in the OSI Interface List window to an external option External L2 External or L1 and L2 External See the section Editing OSI Interface Parameters in Chapter 4 for details Manually enter the set of reachable address prefixes into each L1 L2 bordering router that is linked to an external domain The address prefixes describe which NSAP addresses are reachable over that L1 L2 router s external link See the section Configuring Static External Address Adjacencies in Chapter 4 for details Configuring OSI over DDN X 25 The X 25 Defense Data Network DDN provides end to
77. r either explicitly or implicitly except by acceptance of an order for either Software or for a Bay Networks product Equipment that is packaged with Software Each such license is subject to the following restrictions 1 Upon delivery of the Software Bay Networks grants to licensee a personal nontransferable nonexclusive license to use the Software with the Equipment with which or for which it was originally acquired including use at any of licensee s facilities to which the Equipment may be transferred for the useful life of the Equipment unless earlier terminated by default or cancellation Use of the Software shall be limited to such Equipment and to such facility Software which is licensed for use on hardware not offered by Bay Networks is not subject to restricted use on any Equipment however unless otherwise specified on the Documentation each licensed copy of such Software may only be installed on one hardware item at any time Licensee may use the Software with backup Equipment only if the Equipment with which or for which it was acquired is inoperative Licensee may make a single copy of the Software but not firmware for safekeeping archives or backup purposes Licensee may modify Software but not firmware or combine it with other software subject to the provision that those portions of the resulting software which incorporate Software are subject to the restrictions of this license Licensee shall not make the
78. r listed Repeat Steps 1 and 2 to delete additional adjacencies Click on Done to exit the window 114052 Rev A 4 29 Configuring OSI Services Configuring Static Routes You configure static routes when you want to control which path the router uses to route OSI traffic To configure a static route select Protocols OSI Static Routes in the Configuration Manager window refer to Figure 4 1 The OSI Static Routes window appears Figure 4 8 It lists all static routes that are defined If you did not add any static routes none will be listed 3 iei Ear eee NEM I Arki Delete Apply Me lp ss Enable Nest Hop I5 NSAP fdiress Chex Route Type DieFmalt Beste Aetric Figure 4 8 OSI Static Routes Window Adding Static Routes To add a static route 1 Click on Add in the OSI Static Routes window refer to Figure 4 8 The Static Route Configuration window appears Figure 4 9 4 30 114052 Rev A Editing OSI Parameters Lance Destination KSAP Address hex ext Hop 5 WSP Address nex Figure 4 9 Static Route Configuration Window Parameter Default Options Function Instructions MIB Object ID Define the static route parameters using the descriptions that follow as a guide Click on OK to implement your changes The OSI Static Routes window displays the new static route you defined Repeat Steps 1 3 to add additional static routes En
79. ra pameia dE Roo Pre asa tcd acess 1 18 Table 2 1 Frame Relay Modes Used for OSI IS IS Operations 2 9 Table 4 1 Suggested OSI Circuit Cost Values ssssssesseeeee 4 15 Table B 1 OSI Initial Configuration Parameters sse B 1 Table B 2 OSI Global Parameters ssss TERT T B 1 Table B 3 OSI Interface Parameters qucseveregiterex hen n eror eR Ce REX HET CHER PR OrERR Cone B 2 Table B 4 OSI Static ES Adjacency Parameters sesssssss B 3 Table B 5 OSI External Adjacency Parameters s sss B 3 Table B 6 OS rat ROUES viscera ESO VOU P EEEUR D EXE DRU SEU GO n Eon CR B 3 Table B 7 DECnet 4 to 5 Transition Parameters Tm B 4 114052 Rev A xi About This Guide If you are responsible for configuring and managing Bay Networks routers read this guide to discover how to customize Bay Networks router software for OSI services Refer to this guide for e An overview of the OSI routing protocol and a description of how Bay Networks routing services work Chapter 1 e Implementation notes on configuring Bay Networks OSI routers with special network requirements Chapter 2 e Instructions on Enabling OSI services Chapter 3 Configuring and editing OSI parameters Chapter 4 Before You Begin Before using this guide you must be familiar with the general configuration procedures in Conf
80. rd to LSPs from a router only routers with the same password accept and exchange LSPs To restrict routing you assign identical L2 LSP passwords to all routers located in the domain through which you wish to route data When the OSI router floods Level 2 LSPs through the area only those routers that have been assigned the same password accept the LSPs Instructions If you do not want to assign an L2 LSP password to this router then leave this field blank If you assign an L2 LSP password to this router then you must assign the same L2 LSP password to every router in the domain with which this router communicates MIB Object ID 1 3 6 1 4 1 18 3 5 6 1 15 Note If you set the Router Type parameter for this router to Level 1 only then the router ignores this parameter 114052 Rev A 4 9 Configuring OSI Services Parameter Area Address Default 0x490040 Options Any area address entered in hexadecimal format that is between 3 and 13 bytes long Function Identifies the local area in the routing domain where the router resides Instructions If you have registered your OSI network with an addressing authority then the area address will also reflect the location of the router in the global addressing domain Enter the entire area address portion of the NSAP address allocated to your network as follows Check with your administrative authority to determine the NSAP addresses that have been allocated to your OSI network
81. roadcast packet Figure 2 7 shows group access mode with multiple PVCs on a single subnetwork configured on the same interface 2 10 114052 Rev A OSI Implementation Notes Frame Relay Network Interface 1 PVC 1 PVC2 OSI0027A Figure 2 7 Frame Relay Group Access Mode Group access works best in either full mesh environments or partial mesh environments set up in a hub and spoke topology where communication between systems that are not directly connected to one another goes through the hub In planning OSI over Frame Relay in group mode note the following information about hybrid and mixed access circuit modes and network topology Hybrid For OSI hybrid Frame Relay circuit mode is the same as group access Mixed Access You can mix both group and direct access mode in a configuration as long as you do not violate the group access restrictions Figure 2 8 shows mixed access mode on a designated router with PVC 1 configured in direct access mode on Interface 1 on and PVC 2 and PVC 3 configured in group access mode on Interface 2 114052 Rev A 2 11 Configuring OSI Services Mixed modes PVCs
82. s is not local the router checks its forwarding database for the location of the nearest L1 L2 router in the area It then forwards the packet to the next hop along that path 114052 Rev A 1 21 Configuring OSI Services When an L1 L2 router receives a packet it checks its L2 forwarding database to see which L1 L2 router is the next hop on the path to the destination area It then forwards the packet to that L1 L2 router It continues to forward the packet between L1 L2 routers until the packet arrives at its destination area at which point it will be routed using L1 routing to its destination system The Bay Networks OSI router also supports source routing and record route options That is if a packet has a statically entered path in the optional field of the packet header the router forwards the packet toward the next hop The record route function records the path s followed by a packet as it traverses a series of routers OSI Routing Protocols This section summarizes the following OSI routing protocols that the Bay Networks OSI router uses at the networking level ISO 6473 Connectionless mode Network Service Protocol CLNP which defines the data packet format procedures for the connectionless transmission of data and control information ISO 9542 End System to Intermediate System Routing Exchange Protocol which defines how end systems and intermediate systems exchange configuration and routing information to facil
83. s of the most desirable route to a particular destination either e Through a different router or Directly to an end system on the same subnetwork After the router forwards a data packet to the next hop toward the destination end system the router checks to see whether a more direct route exists The router determines whether the next hop is e The destination system and whether it is attached to the same subnetwork as the originating system Figure 1 12 Example 1 e Another router that is connected to the same subnetwork as the originating end system Figure 1 12 Example 2 1 24 114052 Rev A OSI Overview Example 1 Destination system is on Example 2 Next hop is another router the same subnetwork on the same subnetwork Preffered path Key O Originating End System D Destination System M End System Eg Router OSI0013A Figure 1 12 Route Redirecting If the next hop is either a destination system or another router on the same subnetwork then there is a better path one that does not traverse the router to the destination The router constructs a redirect RD packet which contains the following information Destination address of the original packet e Subnetwork address of the preferred next hop e Network entity title of the next hop unless it is the destination end system e Holding Timer and Maintenance Security and Priority options 114052 Rev A 1 25 Configuring OSI Services
84. s with the command GO BAYNET XX 114052 Rev A InfoFACTS Technical Support and Online Services InfoFACTS is the Bay Networks free 24 hour fax on demand service This automated system has libraries of technical and product documents designed to help you manage and troubleshoot your Bay Networks products The system responds to a fax from the caller or to a third party within minutes of being accessed To use InfoFACTS in the United States or Canada call toll free 1 800 786 3228 Outside North America toll calls can be made to 1 408 764 1002 In Europe toll free numbers are also available for contacting both InfoFACTS and CompuServe Please check our Web page for the listing in your country How to Get Help Use the following numbers to reach your Bay Networks Technical Response Center Technical Response Center Telephone Number Fax Number Billerica MA 1 800 2LANWAN 508 670 8765 Santa Clara CA 1 800 2LANWAN 408 764 1188 Valbonne France 33 92 968 968 Sydney Australia 612 9927 8800 612 9927 8811 Tokyo Japan 81 3 5402 0180 33 92 966 998 81 3 5402 0173 114052 Rev A xxi Chapter 1 OSI Overview This chapter provides a general OSI networking overview and describes how OSI routing services for Bay Networks routers work It includes information on OSI Network organization Level 1 and Level 2 routing Network addressing
85. sible for organizing the network into routing domains and areas RSVD 0000 Indicates that this field is reserved RDI variable Specifies the routing domain where the NSAP resides assigned by the authority identified in the AAI field Area variable Identifies the local area where the NSAP resides assigned by either the authority identified in the AAI field or the local administrative authority that the AAI authority has delegated to this routing domain ID variable Specifies the system where the NSAP resides assigned by the local area administrator that a higher authority has delegated to this area S 0 or 1 Selects the transport layer entity the system uses This entity is specified in the ID field Similarly if you register your OSI network with the ANSI it is assigned to the ISO Data Country Code DCC 840 subdomain Currently the structure of the DSP portion of NSAP addresses allocated by the DCC 840 subdomain is not standardized However the most recent proposal suggests a structure identical to that specified by GOSIP with the Administrative Authority Identifier field replaced by an Organization Identifier field refer to Figure 1 6 114052 Rev A Figure 1 6 IDI OSI Overview Organization Identifier IDP Initial Domain part Reserved DSP Domain Specific Part Routing Domain Identifier AFI Authority and Format Identifier Area Identifier Initial Domain Identifier System Identifier DFI Domain Format Ide
86. sical and logical host port addresses Note that at the time of this writing the DDN does not make use of the PSN s logical addressing feature which allows hosts to be addressed independently of their physical point of attachment to the network The following describes Class A B and C IP address to DDN X 25 address conversion To convert a Class A IP address to a DDN X 25 address For h 64 If the host field h is less than 64 h 64 the address corresponds to the following DDN X 25 physical address ZZZZ F III HH ZZ SS Where e ZZZZ 0000 e F 0 because the address is a physical address e IIT is a three decimal digit representation of i right adjusted and padded with leading zeros if required e HH isa two decimal digit representation of h right adjusted and padded with leading zeros if required e ZZz00is optional e SS is an optional Sub Address field that is ignored in the DDN this field is either left out or filled with zeros The address 26 9 0 122 corresponds to the DDN X 25 physical address 000001220900 114052 Rev A A 7 Configuring OSI Services Example IP Address 26 29 0 122 Format n h l i DDN X 25 Physical ZZZZ F I HH ZZ SS Address Format X 121 Address 0000 O 122 29 00 00 For h gt or 64 If the host field h is greater than or equal to 64 h 2 64 the address corresponds to the following DDN X 25 physical address ZZZZ F RRRRR
87. sing To control data misdirection and congestion throughout the network CLNP includes a lifetime control function The originating system can assign a specific lifetime value in units of 500 milliseconds to the lifetime field of the packet header before sending the system the packet out onto the network Every system that receives the packet decrements its lifetime If the lifetime value reaches zero before the packet reaches its destination system the packet is dropped A system also discards a packet if its checksum is incorrect if the destination address is unknown or if the network is too congested to process the packet CLNP includes an error reporting option that when enabled sends an error report data packet back to the originating system whenever a data packet is lost or discarded End System to Intermediate System Routing Exchange Protocol The End System to Intermediate System Routing Exchange Protocol ISO 9542 defines the way end systems computers etc and intermediate systems routers on the same subnetwork exchange configuration and routing information See Intermediate System to Intermediate System Intra Domain Routing Exchange Protocol later in this chapter for information about communication between routers Configuration Reporting The ISO 9542 configuration report function allows end systems and routers that are attached to the same physical network subnetwork to dynamically discover each other s iden
88. sion methods e Example address conversions Note The information in this appendix was taken from RFC 1236 IP to X 121 Address Mapping 114052 Rev A A 1 Configuring OSI Services IP to X 121 Address Mapping Overview This section defines a standard way of converting IP addresses to CCITT X 121 addresses and is the recommended standard for use on the Internet specifically for the Defense Data Network DDN This section provides information for the Internet community It does not specify an Internet standard The Defense Communication Agency DCA has stated that DDN specifies a standard for mapping Class A addresses to X 121 addresses Additionally DCA has stated that Class B and C IP to X 121 address mapping standards are the responsibility of the administration of the Class B or C network in question Therefore there is no defined standard way of converting Class B and Class C IP addresses to X 121 addresses This is an important issue because currently there is no way for administrators to define IP to X 121 address mapping Without a single standard in a multi vendor network environment there is no assurance that devices using IP and DDN X 25 will communicate with each other The IP to X 121 address mapping of Class B and Class C IP addresses shall be implemented as described below This translation method is a direct expansion of the algorithm described in the MIL STD X 25 DDN X 25 Host Interface Specific
89. state database with the new link state information Decision Each router calculates the shortest paths from itself to all other systems that it can reach using information it retrieves from its link state database It then stores the paths in a forwarding database Forwarding When the router receives a CLNP packet it forwards the packet to the next hop specified in its forwarding database 114052 Rev A Configuring OSI Services Update Process In an OSI network every router must decide which systems it can reach directly It finds out the identity and reachability of its immediate or adjacent neighbors and adds an assigned link cost The router then uses this information to construct an LSP LSPs describe what the router knows about the network topology Depending on its configuration the router generates different types of LSPs see Table 1 4 L1 routers generate only L1 LSPs L1 L2 routers generate both L1 and L2 LSPs Table 1 4 Link State Packet Types Router type Generates ESE Describing Sent to type L1 designated L1 pseudonode The links to all dynamically learned All L1 routers within router L1 routers and end systems in the the area local area that are reachable over the broadcast subnetwork L1 router L1 The links to the L1 designated router All L1 routers within non pseudonode and static links the area L2 designated L2 pseudonode The links to all L1 and L1 L2 routers All L1
90. structions MIB Object ID Editing OSI Parameters Circuit Password None Any text string 8 characters maximum Assigns a password to the interface A router will route packets only to those routers that have been assigned the same circuit password The circuit password is carried to other routers when intermediate systems exchange hello packets If a router discovers that another router has a different password it will not route traffic to that router Therefore to communicate adjacent routers on either end of a point to point connection must have the same circuit password To assign a circuit password enter a text string 1 3 6 1 4 1 18 3 5 6 3 13 IIH Hold Time Multiplier 3 1to5 You set a multiplier value to extend the hold time set in the intermediate to intermediate hello packets transmitted on this interface Setting a value multiplies the IIH Hello Timer parameter by this factor Set to the appropriate value 1 3 6 1 4 1 18 3 5 6 3 64 ISH Hold Time Multiplier 3 1to5 You set a multiplier value to extend the hold time set in the intermediate system hello packets transmitted on this interface Setting a value multiplies the ISH Hello Timer parameter by this factor Set to the appropriate value 1 3 6 1 4 1 18 3 5 6 3 65 114052 Rev A 4 19 Configuring OSI Services Parameter Default Options Function Instructions MIB Object ID Redirect Enable Disable Enable Enable Disable Specifies
91. sword None Area Address 0x490040 Area Address Alias 1 None Area Address Alias 2 None Max Learned End Systems 1024 systems Max Learned L1 64 systems Intermediate Systems Max Learned L2 64 systems Intermediate Systems CLNP Source Route Support Enable Table B 3 OSI Interface Parameters Parameter Default Enable Enable Routing Level Level 1 amp Level 2 L1 Default Metric 20 L2 Default Metric 20 L1 Designated Router 64 Priority L2 Designated Router 64 Priority IIH Hello Timer 8s ISH Hello Timer 30s ESH Configuration Timer 600 s Circuit Password None IIH Hold Time Multiplier 3 continued 114052 Rev A Site Manager Default Settings for OSI Table B 3 OSI Interface Parameters continued Parameter Default ISH Hold Time Multiplier 3 Redirect Enable Disable Enable Table B 4 OSI Static ES Adjacency Parameters Parameter Default Enable Enable ESID None SNPA None Table B 5 OSI External Adjacency Parameters Parameter Default Enable Enable External Address None SNPA None External Address Mode 20 Table B 6 OSI Static Routes Parameter Default Enable Enable Destination NSAP Address None Route Type None Next Hop IS NSAP Address None Default Route Metric 20 114052 Rev A B 3 Configuring OSI Services Table B 7 DECnet 4 to 5 Tra
92. synchronized which could result in connectivity problems between systems Partial Mesh Topology If you use a partial mesh topology with group access mode you need to arrange the network in a hub and spoke topology with the designated router as the hub Figure 2 10 114052 Rev A 2 13 Configuring OSI Services Spoke routers E JL e Hub designated ps Router ge f a Frame Relay Network OSI0021A Figure 2 10 Partial Mesh in Hub and Spoke Topology A PVC that goes down will only cause communication failure between the hub designated router and the spoke on the PVC However in a partial mesh topology losing the hub router causes all communication links on the subnetwork to fail Route Redirecting When you configure OSI over Frame Relay the Redirect Enable Disable parameter appears in the OSI Interface Lists window See Chapter 4 for the Redirect parameter description Redirects specify whether an OSI interface sends a redirect packet ES IS message back to the originating system informing it of a more direct path to a destination system This function is valid in a full mesh topology because all systems can communicate directly Redirects are invalid when running OSI over Fr
93. t dynamically through the exchange of hello packets Unless the domain in which this router resides contains more than 64 L2 routers accept the default value 64 1 3 6 1 4 1 18 3 5 6 1 30 CLNP Source Route Support Enable Enable Disable Enables or disables the processing of source routing options in CLNP packets Set to Disable if this router requires GOSIP v2 support 1 3 6 1 4 1 18 3 5 6 1 38 4 12 114052 Rev A Editing OSI Parameters Editing OSI Interface Parameters To edit an OSI interface 1 Select Protocols gt OSI gt Interfaces from the Configuration Manager window refer to Figure 4 1 The OSI Interface Lists window appears Figure 4 3 It displays all interfaces on which OSI is enabled Done Stet ES frj cxt Adr Adj Apply LE TET PS Help Routing Laimi L1 Default Beteic LZ Default Metric L1 Designated Router Priority L Designated Roster Priority Figure 4 3 OSI Interface Lists Window 2 Click on an interface to select it 3 Edit the parameters using the descriptions that follow as a guide Use the scroll bar to scroll through the list of parameters for the interface 4 Implement your changes by clicking on Apply 114052 Rev A 4 13 Configuring OSI Services 5 Exit the window by clicking on Done Site Manager returns you to the Configuration Manager window Note When you reconfigure an interface in dynamic configuration mode OSI restarts on t
94. t metric relative cost of routing Level 1 traffic over this interface The OSI router always selects the circuit with the lowest cost when defining a path so assigning each circuit a cost is in effect a way of assigning it a priority If you do not want to use this interface to route Level 1 traffic on a regular basis assign it a high cost Otherwise accept the default 20 1 3 6 1 4 1 18 3 5 6 2 1 7 Copying Static Routes To copy a static route 1 Select the static route you want to copy from the list in the OSI Static Routes window refer to Figure 4 8 Click on Copy Define the static route parameters Click on OK to implement your changes The OSI Static Routes window displays the new static route you defined Repeat Steps 1 4 to copy additional static routes Click on Done to exit the screen Editing Static Routes To edit a static route 1 Select the static route you want to edit from the list in the OSI Static Routes window refer to Figure 4 8 Edit the static route parameters Click on Apply to implement your changes Repeat Steps 1 3 to edit additional static routes 114052 Rev A 4 33 Configuring OSI Services 5 Click on Done to exit the screen Deleting Static Routes To delete a static route 1 Select the static route you want to delete from the list in the OSI Static Routes window refer to Figure 4 8 2 Click on Delete The static route is no longer listed
95. te Heclrectihng 22 cspre cito cedann ET ET Tu m incus 1 24 Intermediate System to Intermediate System Intra Domain Routing Exchange ig sinere e MEN NS A A ERN PEE EET 1 26 pire Doman ROUNO e a AS 1 26 Mier DOR RONU soseri o esr hacia TAS 1 28 Chapter 2 OSI Implementation Notes Conmiguring Area Addiess Aliases ene qu t R 2 2 COEGI ATGA IPSFIUDIRS 2uriake repone ciao a a peu nd erai aa p du o SL TRUE a 2 5 Configuring Static External AG SCOIDIBS uiis inse iere d atr RES e sep RIS nee IXR DE REDE MRR EEG 2 7 Conpaudpu OS ovs DON NOB srian NANETA 2 7 bonhidguring DEDRmETV tav ISl Oll qxxsasecenisditetegaikibttu I pede aeS 2 8 Gonmiguiitig OS Over Pantie Melay Pt 2 8 Conkguration pei puc TP 2 8 Frame Relay Circuit Modes ielas T TEN brutos Isi Sor ODE snas cturatootediiu cor artist ace baa Tor ieee uda d eed Sca pci 2 9 Eo eg ire c APTENT E D dsb duesmen tall 2 10 UL ONL E E E tico eatis ctas aide rear een tore ere ater ere rere reece rrr 2 11 MENADO E ios RP ates dre snl deena aaa 2 11 fc clots quet Tt ET aa mea dixe TE TE 2 12 EUN UI Mero ET 2 12 artists TODO uisus eae ee nnd ery eter meee Mirra ee ter Nr ener du sdt Miler Et dad 2 13 POUT PS CIRCLE e REL 0 o 5 Do 0 2 14 Designated Router SelBCHOE 220 tratados D peto ed edd va OR Ia dede 2 15 PoWie tele lalele MNT uc n ERR DTE TOT 2 15 yj dc 2 15 Chapter 3 Enabling OSI Services Ini
96. ternal 114052 Rev A 4 25 Configuring OSI Services Continue to the following sections to add remove copy or edit external address adjacencies from this window Adding Static External Address Adjacencies To add a static external address adjacency 1 Click on Add in the OSI External Address Adjacency List window refer to Figure 4 6 The OSI External Address Adjacency Configuration window appears Figure 4 T External Address nex SHPh Figure 4 7 OSI External Address Adjacency Configuration Window 2 Define the static external address adjacency parameters using the descriptions in the next section as a guide 3 Click on OK to implement your changes and exit the window The OSI External Address Adjacency List window displays the new adjacency you defined 4 Repeat Steps 1 3 to add additional adjacencies 4 26 114052 Rev A Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions Editing OSI Parameters Enable Enable Enable Disable Enables the external adjacency defined by the SNPA parameter The default Enable appears after you add a static external address adjacency in the OSI External Address Adjacency Configuration window 1 3 6 1 4 1 18 3 5 6 4 2 External Address None Any valid address Specifies th
97. tia Goniguraton of OSI SORES 44 5 IA TSER ES HD P IRE IEEE RbCA pL mien 3 1 vi 114052 Rev A Chapter 4 Editing OSI Parameters Perros peg OSI RID E ETE CE E T T 4 2 Ediinq OSI Glopa PasYelbEe eise added er bea badido aa ai dc ia dade ER 4 3 Editing ssl Intertace Parler isisctiiimuteiistu itn DEP Cbr obdu seu equ Mise TERI obe dgdE 4 13 Configuring Static End System Adjacencies sse 4 20 Adding a Static End System Adjacenoy eeesesssseeeeennes 4 21 Copying a Staic End System AUJBOOOV arinina ian aa 4 24 Editing a Static End System Adjacenoy serwriannirasnirsnirni tada 4 24 Deleting a Static End System Adjacenoy ssssesseeeeeee 4 24 Configuring Static External Address Adjacencies eee 4 25 Adding Static External Address Adjacencies sse 4 26 Copying Static External Address Adjacencies ssssessessess 4 29 Editing Static External Address Adjacencies cc ccccscceeeeeeeeeeeeeeeeeeeseeeeeeneeeeeas 4 29 Deleting Static External Address Adjacencies sessssssssss 4 29 Conmigurno State ROES e em 4 30 PU SIC PROMES Lido ecd tin Ced Doa dd vni ose Quad leve Lada dgad aa o tet skagen 4 30 Copying Static Routes m TEN iuis came TRE 4 33 Eding TAU ROUES P 4 33 Deleting Stalig ROUTES risers siduri ticis dennis a aderat pe b dad dl
98. tity by periodically generating and exchanging hello packets The hello packet exchange process tells the router which NSAPs it can access 114052 Rev A 1 23 Configuring OSI Services End systems generate hello packets that contain the end system s subnetwork address and specify which NSAPs the end system services When a router receives an end system hello packet it extracts the configuration information from the packet matching the subnetwork address with the corresponding NSAPs and stores it in its routing information base Routers generate hello packets that contain the router s own subnetwork address When an end system receives a router hello packet the end system extracts the router s subnetwork address and stores it in its own routing information base Two types of timers control how often hello packets are exchanged a configuration timer and a holding timer The configuration timer which is maintained by each individual system determines how often a system reports its availability or any change in its configuration to the other systems attached to the same subnetwork The holding timer which is a value set by the originating system is contained in the holding time field of a hello packet It specifies how long a receiving system should retain the configuration information before it is flushed from the routing information base Route Redirecting The ISO 9542 route redirection function allows routers to inform end system
99. tside of the campus routing domain the administrator obtained NSAP addresses for Area A and Area B simply by registering the campus network with ANSI ANSI assigned the network to the DCC 840 subdomain which in turn assigned an organization identifier of 113527 to the network Area C however is linked to an external domain that is operated by the federal government So besides registering the network with ANSI the administrator also registered the network with the GSA to receive NSAP addresses in GOSIP format for those systems residing in Area C The GSA assigned the network to the ICD 0005 subdomain which in turn assigned an Administrative Authority Identifier of 00004e to the network Assigned full NSAP addresses to the routers and end systems in Area A Area B and Area C After receiving the organization ID for the campus network from the DCC 840 subdomain the administrator assigned full NSAP addresses to the routers and end systems in Area A and Area B Figure 1 9 Note that the DSP portion is structured according to DCC 840 subdomain standard format 114052 Rev A Configuring OSI Services r NSAP for IDE Router in Area A 39 840 81 113527 AFI IDI DFI ORG Rsvd RDI Area ID S 4 amp Area Address SSS o pero ee tm ee m m mm erOPT UP emper m mm em memo emo elemen m m emm m Im m fem 1 l l l l l l NSAP for j IDP I DSP I Router in Area B 39 840 81 1
100. uit type see Instructions Specifies an SNPA for the adjacent end system Enter the SNPA for the adjacent end system Ifthis circuit is an X 25 PDN circuit then enter any valid X 121 address in decimal format If this circuit is an X 25 DDN circuit then enter a valid X 121 address for the remote router in decimal format If this circuit uses PPP then leave this field blank If this circuit is of any other type then enter any valid MAC address 1 3 6 1 4 1 18 3 5 6 5 1 5 Note To enter a valid X 121 address for an X 25 DDN circuit you must convert the remote IP address to an X 121 address See Appendix A for the conversion algorithm 114052 Rev A 4 23 Configuring OSI Services Copying a Static End System Adjacency To copy a static end system adjacency 1 Click on the adjacency you want to copy from the list in the OSI Static ES Adjacency List window refer to Figure 4 4 Define the ESID parameter for that adjacency Click on OK The OSI Static ES Adjacency List window displays the new adjacency you copied Repeat Steps 1 3 to copy additional static end system adjacencies Click on Done to exit the window Editing a Static End System Adjacency To edit a static end system adjacency 1 u FPF WR Select the adjacency you want to edit from the list in the OSI Static ES Adjacency List window refer to Figure 4 4 Edit the static adjacency parameters you want to chan
101. ve different values for this parameter or it is ignored This applies only to Bay Networks standard point to point and X 25 point to point service It does not apply to a synchronous circuit running Point to Point Protocol PPP or X 25 Public Data Network PDN or DDN service Note If the network is synchronous for example point to point or X 25 gt Parameter L2 Designated Router Priority Default 64 Range to 127 Function Specifies which L2 router becomes the L2 designated router for the LAN segment See the section entitled Update Process in Chapter 1 for information about designated routers You can control which L2 router becomes the L2 designated router for the LAN segment by assigning a priority value to each L2 router Then the L2 router assigned the highest priority becomes the L2 designated router for that LAN segment If all routers have the same priority then the L2 router with the highest MAC address becomes the L2 designated router for the LAN segment Instructions If you want this L2 router to become the L2 designated router for the LAN segment then assign it the highest priority value among L2 routers on the LAN MIB Object ID 1 3 6 1 4 1 18 3 5 6 3 9 114052 Rev A 4 17 Configuring OSI Services Parameter Default Options Function Instructions MIB Object ID Parameter Default Options Function Instructions MIB Object ID Parameter Default Options
102. y Level 1 routing within its own area An L1 L2 router can support Level 1 routing Level 2 routing between areas and external routing between domains You can further define the type of traffic that router supports by editing the interface parameters For example if you want a certain interface to route only Level 2 traffic then you designate the individual interface as an L2 interface see Editing OSI Interface Parameters later in this chapter for instructions Select the appropriate router type 1 3 6 1 4 1 18 3 5 6 1 5 Note To support routing between areas you must specify at least one L1 L2 router per area However each L1 L2 router can serve only a single area Parameter Default Options Function Instructions MIB Object ID Router ID The router ID set when you initially enabled OSI services Any valid 6 byte system ID Identifies the router within its local area The system ID is the ID portion of the router s NSAP address See the section OSI Network Addressing in Chapter 1 for more information You set the router ID when you initially enable OSI services in the OSI Configuration window see Chapter 3 If necessary enter a new 6 byte system ID in hexadecimal format If the system ID is not 6 bytes add leading zeroes Since every router in a domain must have a unique system ID using a router s MAC address for its system ID ensures this requirement 1 3 6 1 4 1 18 3 5 6 1 6 11
103. ybrid Broadcast Direct Access In direct access mode OSI treats a PVC as a point to point connection OSI views each PVC as an individual network interface In direct access mode you configure each Frame Relay PVC manually and configure the OSI protocol to run over it The OSI router treats each PVC as a separate OSI interface Figure 2 6 shows direct access mode with each PVC configured as a separate OSI interface See Configuring Frame Relay Services for information about configuring PVCs 114052 Rev A 2 9 Configuring OSI Services Frame Relay Network Interface 1 PVC 1 Interface 2 PVC 2 OSI0019A Figure 2 6 Frame Relay Direct Access Mode OSI point to point operation over Frame Relay uses circuit bandwidth more efficiently than OSI broadcast operation It also complies with the ISO standards for point to point operation However point to point operation uses proportionally more memory resources on the router per PVC than broadcast operation Group Access In group access mode OSI treats each Frame Relay network interface as a single access point to the subnetwork DLCIs on the subnetwork are treated like MAC addresses on actual broadcast media A router broadcasts an OSI packet on a particular Frame Relay circuit over all known PVCs on that circuit OSI assumes that all systems on the subnetwork will receive a b

Download Pdf Manuals

Related Search

Related Contents

Sanyo VPC-GH1GX User's Manual  Lichttechnik  IDEP for Windows  Lenovo ThinkPad T430  3 - SmartThings Support  000821MAN-01 (ISSUE 02) - RH-Series Two-Stage R410a  1. Manuel d`utilisation du Menu LEGENDE  HTC SM-TP001-0704 User's Manual  Kinetis L - ADC  

Copyright © All rights reserved. Failed to retrieve file