Home

Avaya Configuring OSI Services User's Manual

1. Table 1 6 TARP Packet Fields Length Name in Bytes Description tar lif 2 TARP lifetime hops If the network entity receives a TARP packet with a tar lif field equal to 0 it discards the packet Before forwarding a TARP packet a receiving device decrements this field by 1 If the field then has a value of 0 the device can drop the packet rather than forwarding it to a recipient that will drop it tar seq 2 TARP sequence number The originating network entity assigns a sequence number to each packet it originates For each new packet the sequence number increments by 1 tar pro 1 Protocol Address Type This field must have a value of FE tar tcd 1 TARP type code The type of TARP packet tar tin 1 Target TID length The number of octets present in the tar tor field tar oln 1 Originator TID length The number of octets present in the tar tor field tar pln 1 NSAP length The number of octets in the tar por field tar ttg N Target TID tar tor N Originator TID tar por N NSAP of originator 1 30 308637 14 00 Rev 00 OSI Overview Originating TARP Requests For the router to act as a TARP client it must be able to originate all five types of packets The router maintains a data cache that contains the results of TARP requests it has made and generates a Type 3 response to Type 1 or Type 5 packets The router also generates TARP requests via Technician Interface commands Before they send o
2. 308637 14 00 Rev 00 1 19 Configuring OSI Services The router refers to its link state databases 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 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 Nortel 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
3. 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 2 10 308637 14 00 Rev 00 Topology OSI Implementation Notes 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 and PVC 2 and PVC 3 configured in group access mode on Interface 2 Mixed modes PVCs Designated P di router PVCL e E LS a oem PVC2 si ws E PIOS ipe Interface 1 PVC1 Ei Direct access mode DEOS E Interface 2 PVC2 PVC3 Group access mode Frame Relay Network OSI0023A Figure 2 8 Frame Relay Mixed Access Modes Direct and Group Conside
4. 308637 14 00 Rev 00 1 13 Configuring OSI Services 2 Assigned identifiers to the campus routing domain and local areas as follows Campus Routing Domain Identifier 2 0001 Area A Identifier 0001 Area B Identifier 0002 Area C Identifier 0003 Routing Domain 0001 Area A 2 0001 AreaB 20002 L To External GOSIP OSI Network Area C 2 0003 Key is L1 L2 Router L End System OSI0009A Figure 1 8 Campus Routing Domain 3 Registered the campus network with the addressing authorities 1 14 308637 14 00 Rev 00 OSI Overview Because Area A and Area B are not linked to any areas outside 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 organiza
5. You do this System responds 1 In the Configuration Manager window The TARP Interface Lists window opens choose Protocols OSI Tarp Circuits 2 Edit one or more of the following parameters Enable Circuit Propagate Pkts Circuit Originate Pkts Click on Help or see the parameter descriptions beginning on page D 27 3 When you are finished click on Done You return to the Configuration Manager window Configuring TARP Static Adjacencies If you want the router to forward TARP packets to specific NSAP addresses you must configure TARP static adjacencies The following sections describe how to add enable or delete TARP static adjacencies Adding TARP Static Adjacencies To add a TARP static adjacency Site Manager Procedure You do this System responds 1 In the Configuration Manager window The TARP Static Adjacencies window choose Protocols OSI Tarp opens ADJ TARP 2 Click on Add The Static Adjacencies Configuration window opens continued 308637 14 00 Rev 00 4 19 Configuring OSI Services Site Manager Procedure continued You do this 3 Set the Static Adjacent NSAP Address parameter Include a 00 NSEL value at the end of the NSAP address Click on Help or see the parameter description on page D 28 Click on OK System responds The TARP Static Adjacencies window opens When you are finished click on Done
6. Deleting TARP Static Adjacencies To delete a TARP static adjacency You return to the Configuration Manager window Site Manager Procedure You do this System responds 1 In the Configuration Manager window choose Protocols gt OSI gt Tarp gt ADJ TARP The TARP Static Adjacencies window opens Select a static adjacency address and then click on Delete The address no longer appears in the list When you are finished click on Done You return to the Configuration Manager window 4 20 308637 14 00 Rev 00 Editing OSI and TARP Parameters To enable or disable a TARP Static Adjacency setting Site Manager Procedure You do this System responds 1 In the Configuration Manager window choose Protocols gt OSI gt Tarp gt ADJ TARP The TARP Static Adjacencies window opens Select a static adjacent NSAP address and then click on Values The Values Selection window opens Set the Enable parameter Click on Help or see the parameter description on page D 28 Click on OK The TARP Static Adjacencies window opens When you are finished click on Done You return to the Configuration Manager window 308637 14 00 Rev 00 4 21 Configuring OSI Services Configuring TARP to Ignore a Static Adjacency To configure TARP to ignore a defined static adjacency Site Manager Procedure You do this S
7. You return to the Configuration Manager window 4 10 308637 14 00 Rev 00 Deleting a Static End System Adjacency To delete a static end system adjacency Site Manager Procedure Editing OSI and TARP Parameters You do this System responds 1 In the OSI Static ES Adjacency List window click on the adjacency that you want to delete 2 Click on Delete The static end system adjacency is no longer listed 3 Repeat steps 1 and 2 to delete additional adjacencies 4 When you are finished click on Done You return to the Configuration Manager window Configuring Static External Address Adjacencies You configure static external adjacencies to enable interdomain routing routing between domains To configure a static external address adjacency Site Manager Procedure You do this System responds 1 In the Configuration Manager window choose Protocols gt OSI gt Interfaces The OSI Interface Lists window opens 2 Click on External Address Adjacency The OSI External Address Adjacency List window opens which lists all defined external address adjacencies If you did not add any adjacencies none will be listed 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 External For
8. 5 SEO NUM 00000004 AREA ADDR IS NBR IS NBR 00000001 IS NBR IS NBR 00000008 AREA ADDR IS NBR IS NBR IS NBR 00000005 AREA ADDR AREA ADDR AREA ADDR IS NBR PREFIX 00000002 IS NBR IS NBR TTL 0472 490040 06060606060601 07070707070700 0472 06060606060600 07070707070700 0473 490040 06060606060601 06060606060600 46464646464602 04B0 490030 500040 51500040 46464646464602 500011 04B0 46464646464600 07070707070700 0034 0045 0042 0034 CKSUM 3778 14 14 C1AA 00 00 580B 14 14 14 3F79 14 3A2D 00 00 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 80 B 6 308637 14 00 Rev 00 Appendix C Enabling the wfOsiFletchRelaxedEnable Attribute Using the Technician Interface When an OSI LSP packet is transmitted a checksum value is sent along with the packet The value of the checksum is set to either e Zero which indicates that checksumming is disabled e The value of the Fletcher checksum for the packet However if the value of one of the bytes of the checksum is zero then the byte is replaced with 255 To prevent OSI from replacing the checksum byte with 255 you can enable the global OSI MIB attribute wfOsiFletchRelaxedEnable When you enable this attribute the zero bytes are replaced
9. Example 2 OSI Overview Next hop is another router on the same subnetwork OSI0013A 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 e 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 308637 14 00 Rev 00 1 25 Configuring OSI Services 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 separ
10. Options Function Instructions MIB Object ID Circuit Originate Pkts Configuration Manager gt Protocols gt OSI gt Tarp gt Circuits Enable Enable Disable Specifies whether this circuit can originate TARP packets If you want this circuit to originate TARP packets accept the default Enable 1 3 6 1 4 1 18 3 5 6 15 1 6 TARP Static Adjacency Parameters Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID This section describes the TARP static adjacency parameters Enable Configuration Manager gt Protocols gt OSI gt Tarp gt ADJ TARP Enable Enable Disable Enables the adjacency that you define using the Static Adjacent NSAP Address parameter The default Enable appears after you add a static adjacent NSAP address 1 3 6 1 4 1 18 3 5 6 17 1 2 Static Adjacent NSAP Address Configuration Manager gt Protocols gt OSI gt Tarp gt ADJ TARP None Any valid NSAP address Links the router to a specific NSAP address to which it forwards TARP packets Enter the address in hexadecimal format 1 3 6 1 4 1 18 3 5 6 17 1 3 D 28 308637 14 00 Rev 00 Site Manager Parameters TARP Ignore Adjacencies Parameters Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID This sectio
11. 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 308637 14 00 Rev 00 D 7 Configuring OSI Services Parameter Area Address hex Path Configuration Manager Protocols OSI Global 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 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 e f you 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 13 1 Note You must assign the same area address to all ro
12. 6 byte system ID of the station that originated the LSP the 1 byte pseudonode ID and the LSP number Sequence number in hexadecimal notation of the LSP entry Time to live in hexadecimal notation for the LSP Size in bytes of the LSP A 2 byte checksum value in hexadecimal notation The following example shows the output that displays when you do not specify the f option osi lsp OSI LEVEL 1 LSP DATABASE ID 4646464646460000 4646464646460200 Total LSPs 2 OSI LEVEL 2 LSP DATABASE ID 0606060606060000 0606060606060100 0707070707070000 4646464646460000 4646464646460200 Total LSPs 5 SEO NUM 00000005 00000001 SEO NUM 00000004 00000001 00000008 00000005 00000002 TTL 04B0 04B0 TTL 0472 0472 0473 04B0 04B0 0044 0029 003A 0034 0045 0042 0034 CKSUM 04C2 4BD3 CKSUM 3778 C1AA 580B 3F79 3A2D 308637 14 00 Rev 00 B 3 Configuring OSI Services With the f option specified output includes the information in the previous output table on page B 3 and the following information Area IS NBR ES NBR AREA ADDR PREFIX Any valid OSI area address in hexadecimal notation configured for this intermediate system The address is from 3 to 11 bytes long Intermediate system and pseudonode neighbors of the station that originated the LSP The value is a 7
13. 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 308637 14 00 Rev 00 Nortel Networks NA Inc Software License Agreement NOTICE Please carefully read this license agreement before copying or using the accompanying software or installing the hardware unit with pre enabled software each of which is referred to as Software in this Agreement BY COPYING OR USING THE SOFTWARE YOU ACCEPT ALL OF THE TERMS AND CONDITIONS OF THIS LICENSE AGREEMENT THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER WHICH NORTEL NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE If you do not accept these terms and conditions return the product unused and in the original shipping container within 30 days of purchase to obtain a credit for the full purchase price 1 License Grant Nortel Networks NA Inc Nortel Networks grants the end user of the Software Licensee a personal nonexclusive nontransferable license a to use the Software either on a single computer or if applicable on a single authorized device identified by host ID for which it was originally acquired b to copy the Software solely for backup purposes in support of authorized use of the Software and c to use and copy the associated u
14. Manager Procedure continued 3 You do this Specify the external address for the new adjacency Click on Help or see the parameter description on page D 20 System responds Click on Save Site Manager saves the new adjacency to the list Repeat steps 1 through 4 to copy additional adjacencies When you are finished click on Done You return to the Configuration Manager window Editing Static External Address Adjacencies To edit a static external address adjacency Site Manager Procedure You do this System responds 1 In the OSI External Address Adjacency List window select the adjacency that you want to edit Edit one or more of the following parameters Enable External Address hex SNPA External Address Metric Click on Help or see the parameter descriptions beginning on page D 19 Click on Apply to implement your changes The new values appear in the OSI External Address Adjacency window Repeat steps 1 through 3 to edit additional adjacencies When you are finished click on Done You return to the Configuration Manager window 308637 14 00 Rev 00 4 13 Configuring OSI Services Deleting Static External Address Adjacencies To delete a static external address adjacency Site Manager Procedure You do this System responds 1 In the OSI External Address Adjacency List window select the
15. Mapping for DDN Background AII 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 corresponding to the four octets of a 32 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 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
16. Notes Spoke routers E JL i Hub designated router E JL e 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 Appendix D Site Manager Parameters 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 frame 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 Disable when operating OSI over frame relay in group mode in a hub and spoke topology Accept the default value Enable in
17. 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 identity by periodically generating and exchanging Hello packets The Hello packet exchange process tells the router which NSAPs it can access 308637 14 00 Rev 00 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 ar
18. adjacency that you want to delete Click on Delete The static external adjacency is no longer listed Repeat steps 1 and 2 to delete additional adjacencies When you are finished click on Done 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 Site Manager Procedure You do this System responds 1 In the Configuration Manager window choose Protocols OSI Static Route The OSI Static Routes window opens which lists all static routes that are defined If you did not add any static routes none will be listed 2 Click on External Address Adjacency The OSI External Address Adjacency List window opens which lists all defined external address adjacencies If you did not add any adjacencies none will be listed Continue to the following sections for instructions on adding copying editing or removing static routes 308637 14 00 Rev 00 Adding Static Routes To add a static route Site Manager Procedure Editing OSI and TARP Parameters You do this System responds 1 In the OSI Static Routes window click on Add The Static Route Configuration window opens Configure the following parameters Enable Destination NSAP Address Route Type Next Hop IS NSAP Address Default Route Metric Click on Help or see t
19. and the American National Standards Institute ANSI 1 6 308637 14 00 Rev 00 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 hierarchical 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 basic parts the Initial Domain Part IDP and the Domain Specific Part DSP Figure 1 4 308637 14 00 Rev 00 1 7 Configuring OSI Services IDP Initial Domain Part AFI Authority and Format Identifier IDI Intitial Domain Identifier DSP Domain Specific Part Figure 1 4 OSIO005A Basic NSAP Address Structure The IDP consists of an Authority and Format Identifier AFI 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 struct
20. 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 Configuration Manager Protocols OSI Interfaces 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 IH 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 Configuration Manager Protocols OSI Interfaces 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 D 16 308637 14 00 Rev 00 Parameter Path Default Options Function Instructions MIB Object ID Site Manager Parameters Redirect Enable Disable Configuration Manager gt Protocols gt OSI gt Interfaces Enable Enable Disable Specifies whether an OSI interface sends
21. byte ID consisting of the 6 byte system ID and 1 byte pseudonode in hexadecimal notation followed by four fields default metric delay metric expense metric and error metric End station neighbors of the station that originated the LSP The value is a 6 byte system ID in hexadecimal notation followed by four fields default metric delay metric expense metric and error metric If the system supports partition repair the set of partition area addresses for this intermediate system If the System does not support partition repair the set of area addresses for this intermediate system Reachable address prefixes The value is from 3 to 11 bytes 308637 14 00 Rev 00 Using the Technician Interface osi Isp Command The following example shows the output that displays when you specify the f option osi lsp f OSI LEVEL 1 LSP DATABASE ID 4646464646460000 4646464646460200 Total LSPs 2 n EQ_NUM 00000005 AREA AREA AREA IS_NBR ES_NBR 00000001 IS_NBR TTL 04B0 490030 50004 0 51500040 46464 46464 04B0 46464 646464602 6464646 646464600 0029 CKSUM 04C2 14 80 80 00 80 80 4BD3 00 80 80 80 80 80 308637 14 00 Rev 00 B 5 Configuring OSI Services OSI LEVEL 2 LSP DATABASE ID 0606060606060000 0606060606060100 0707070707070000 4646464646460000 4646464646460200 Total LSPs
22. for a response to a Type 2 request it originated Accept the default or choose another value 1 3 6 1 4 1 18 3 5 6 14 13 D 26 308637 14 00 Rev 00 Parameter Path Default Options Function Instructions MIB Object ID Site Manager Parameters Tarp T3 Timer Configuration Manager gt Protocols gt OSI gt Tarp gt Global 40 1 to 3600 Specifies the number of seconds the router waits for a response to a Type 5 request it originated Accept the default or choose another value 1 3 6 1 4 1 18 3 5 6 14 14 TARP Circuit Parameters Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID This section describes the TARP circuit parameters Enable Configuration Manager gt Protocols gt OSI gt Tarp gt Circuits Enable Enable Disable Enables TARP on this circuit For TARP to operate properly OSI must also be configured on this circuit To use TARP on the circuit accept the default Enable 1 3 6 1 4 1 18 3 5 6 15 1 2 Circuit Propagate Pkts Configuration Manager gt Protocols gt OSI gt Tarp gt Circuits Enable Enable Disable Specifies whether this circuit can forward TARP packets If you want this circuit to forward TARP packets accept the default Enable 1 3 6 1 4 1 18 3 5 6 15 1 5 308637 14 00 Rev 00 D 27 Configuring OSI Services Parameter Path Default
23. information about the Routing Level parameter see the description on page D 11 308637 14 00 Rev 00 Configuring OSI Services Continue to the following sections for instructions on adding copying editing or removing external address adjacencies Adding Static External Address Adjacencies To add a static external address adjacency Site Manager Procedure You do this System responds 1 In the OSI External Address Adjacency The OSI External Address Adjacency List window click on Add Configuration window opens 2 Configure the following parameters Enable External Address SNPA External Address Metric Click on Help or see the parameter descriptions beginning on page D 19 3 Click on OK to implement your changes The new adjacency you defined appears in the OSI External Address Adjacency List window 4 Repeat steps 1 through 3 to add additional adjacencies 5 When you are finished click on Done You return to the Configuration Manager window Copying Static External Address Adjacencies To copy a static external address adjacency Site Manager Procedure You do this System responds 1 In the OSI External Address Adjacency List window select the adjacency that you want to copy 2 Click on Copy Site Manager prompts you for an external address continued 4 12 308637 14 00 Rev 00 Editing OSI and TARP Parameters Site
24. model 1 2 configuring over DDN X 25 2 7 A 1 conversion algorithm for X 121 address A 7 to A 10 deleting from the router 4 24 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 B 1 lowest cost path 1 20 manual area address configuring 4 6 described 2 2 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 ATM 2 14 over frame relay 2 8 to 2 14 packet segmentation 1 23 path costs D 11 308637 14 00 Rev 00 reachable address prefixes 1 28 2 7 routing algorithm 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 8 configuring 4 8 copying 4 9 deleting 4 11 editing 4 10 static external address adjacency adding 4 12 configuring 4 11 copying 4 12 deleting 4 14 editing 4 13 static external adjacencies 2 7 static route adding 4 15 configuring 4 14 copying 4 15 deleting 4 16 editing 4 16 osi Isp command B 1 OSI parameters editing global 4 4 editing interface 4 5 global Area Address D 8 CLNP Source Route Support D 10 Enable D 1 IS Checksum D
25. osi lsp command B 1 text conventions Xiv TID target identifier defined 1 28 finding using TARP 1 31 TID Address Resolution Protocol TARP 1 28 timers 1 24 D 15 308637 14 00 Rev 00 topology and area partitions 2 6 frame relay 2 11 total path cost 1 20 V viewing TARP data caches 4 23 X X 121 address conversion algorithm A 7 to A 10 X 25 network 2 7 Index 5
26. 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 308637 14 00 Rev 00 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 nternet Numbers RFC 1166 DDN NIC July 1990 A 4 308637 14 00 Rev 00 IP to X 121 Address Mapping for DDN Class B The two highest order bits are set to 1 0 14 bits define the network number 16 bits define the local address This allows up to 16 384 Class B networks Network Local Address 14 bits 16 bits rest field OSI0025A Figure A 2 Class B Internet Address 308637 14 00 Rev 00 A 5 Configuring OSI Services Class C e The three highest order bits are set to 1 1 0 e 21 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
27. the Configuration Manager window choose Protocols gt OSI gt Manual Area Address The OSI Area Address Configuration window opens 2 Click on Add The OSI Area Address Configuration Add window opens 3 Setthe Area Address parameter Click on Help or see the parameter description on page D 17 4 Click on OK 5 To add more area addresses repeat steps 4 through 6 When you are finished click on Done You return to the Configuration Manager window 308637 14 00 Rev 00 Deleting a Manual Area Address To delete a manual area address Site Manager Procedure Editing OSI and TARP Parameters You do this System responds 1 In the Configuration Manager window choose Protocols gt OSI gt Manual Area Address Select the address that you want to delete from the list The OSI Area Address Configuration window opens The OSI Area Address Configuration Add window opens Click on Delete The manual area address is no longer listed Repeat steps 2 and 3 to delete additional addresses When you are finished click on Done You return to the Configuration Manager window 308637 14 00 Rev 00 Configuring OSI Services 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 inte
28. the NSAP address of the intermediate system that is the next hop on the path to the destination end system Instructions Enter the address assigned to the next hop intermediate system in hexadecimal MIB Object ID 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 D 22 308637 14 00 Rev 00 Site Manager Parameters Parameter Path Default Options Function Instructions MIB Object ID Default Route Metric Configuration Manager gt Protocols gt OSI gt Global 20 1 to 1023 Specifies the default 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 TARP Global Parameters Parameter Path Default Options Function Instructions MIB Object ID This section describes the TARP global parameters Router ID Configuration Manager gt Protocols gt OSI gt Tarp gt Global The router ID set when you initially enable OSI services Any valid 6 byte system ID Identifies the router within its local area The sy
29. 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 308637 14 00 Rev 00 1 9 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 responsible 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 ANSI it is assigned to
30. the remote IP address to an X 121 address See Appendix A TP to X 121 Address Mapping for DDN for the conversion algorithm Static External Address Adjacency Parameters This section describes the static external address adjacency parameters Parameter Enable Path Configuration Manager gt Protocols gt OSI gt Interfaces gt External Address Adjacency gt Add Default Enable Options Enable Disable Function Enables the external adjacency defined by the SNPA parameter Instructions The default Enable appears after you add a static external address adjacency in MIB Object ID the OSI External Address Adjacency Configuration window 1 3 6 1 4 1 18 3 5 6 4 2 308637 14 00 Rev 00 Configuring OSI Services Parameter External Address hex Path Configuration Manager gt Protocols gt OSI gt Interfaces gt External Address Adjacency gt Add Default None Options Any valid address Function Specifies the destination address of the external adjacency Instructions Enter the address assigned to the external adjacency in hexadecimal format MIB Object ID 1 3 6 1 4 1 18 3 5 6 4 5 Parameter SNPA Path Configuration Manager gt Protocols gt OSI gt Interfaces gt External Address Adjacency gt Add Default None Options Depends on the circuit type see Instructions Function Specifies an SNPA for the adjacent end system Instructions Enter the SNPA for the adjacent end system as follows
31. window opens OSI is no longer configured on the router 3 Click on Done You return to the Configuration Manager window 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 For details on configuring circuits see Configuring and Managing Routers with Site Manager 4 24 308637 14 00 Rev 00 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 a static end system adjacency or a static external address adjacency see Configuring Static End System Adjacencies on page 4 8 and Configuring Static External Address Adjacencies on page 4 11 This appendix includes e An overview of the IP address classes e Address conversion methods e Examples of address conversions Note The information in this appendix was taken from RFC 1236 IP to X 121 Address Mapping 308637 14 00 Rev 00 A 1 Configuring OSI Services IP to X 121 Address Mapping Overview This section defines a standard way of converting IP addresses to CCITT now ITU T 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 In
32. with 255 only for checksum validation No permanent change is made to the received LSP packet Thus the value of the Fletcher checksum is still zero bytes To enable the wfOsiFletchRelaxedEnable attribute using the Technician Interface enter set wfOsi wfOsiFletchRelaxedEnable 0 1 commit where 7 indicates enabled To disable the attribute enter set wfOsi wfOsiFletchRelaxedEnable 0 2 commit where 2 indicates disabled The default value is disabled 308637 14 00 Rev 00 C 1 Appendix D Site Manager Parameters This appendix contains parameter descriptions for OSI and TARP parameters Note The information in this appendix is the same information you get when you click on Help in a Site Manager window OSI Global Parameters This section describes the OSI global parameters Parameter Enable Path Configuration Manager Protocols OSI Global 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 308637 14 00 Rev 00 D 1 Configuring OSI Services Parameter Path Default Options Function Instructions MIB Object ID Router Type Configuration Manager Protocols OSI Global Level 1 and Level 2 Level 1 Level 1 and Level 2 Specifies whether the router functions as
33. 18 3 5 6 3 6 308637 14 00 Rev 00 Configuring OSI Services Parameter Path Default Options Function Instructions MIB Object ID Table D 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 L2 Default Metric Configuration Manager Protocols OSI Interfaces 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 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 D 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 308637 14 00 Rev 00 Site Manager Parameters Parameter L1 Designated Router Priority Path Configurati
34. 3 Manual Area Address 456 Assigned to Specific End Systems 2 4 Area XY Divided into Area X and Area Y sse 2 5 Routers B and C in an Area Partition Due to Improper Network Design 2 6 Frame Relay Direct Access Mode a sccesssccciisseese cien errat n an 2 9 Frame Relay Group Access Mode sse 2 10 Frame Relay Mixed Access Modes Direct and Group 2 11 Poll Mesh TOPO o M 2 12 Partial Mesh in Hub and Spoke Topology esses 2 13 Configuration Manager WINDOW uui rarae rti tiir etn aaa een v urge 4 2 Glass A Intermet AGDITeSS ases erttci en E a eb P Ert P X EC A 4 Class B Imetnetr BSS sens aarti paannieas sada ud saccis a bed ad d a A 5 eredi Ree RN A 6 308637 14 00 Rev 00 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 sigle Packet YPES masiina pros Sa pacer bg ae ai Fa ibn beanies 1 18 Table 1 5 TARP Packet Types RE MEERIAS er meets iterate 1 29 Table 1 6 TARF Packet Fleece sett rapidum ceti bue rapi een eee eit 1 30 Table 2 1 Frame Relay Modes Used for OSI IS IS Operations 2 9 Table D 1 Suggested OSI Circuit Cost Valu
35. 5 L1 LSP Password D 6 L2 LSP Password D 7 Load Balancing D 3 Max Area Addresses D 4 Max st External Addresses D 5 Max L1 Intermediate Systems D 4 Max L2 Intermediate Systems D 5 Max Learned End Systems D 9 Max Learned L1 Intermediate Systems D 9 Max Learned L2 Intermediate Systems D 9 Router ID D 3 Router Type D 2 Index 3 interface Circuit Password D 16 Enable D 10 ESH Configuration Time D 15 HH Hello Timer D 14 IIH Hold Time Multiplier D 16 ISH Hello Timer D 15 ISH Hold Time Multiplier D 16 L1 Default Metric D 11 L1 Designated Router Priority D 13 L2 Designated Router Priority D 14 Redirect Enable Disable D 17 Routing Level D 11 static end system adjacency Enable D 18 ESID D 18 SNPA D 19 static external address adjacency Enable D 19 External Address D 20 External Address Metric D 21 static route Default Route Metric D 23 Destination NSAP Address D 22 Enable D 21 Next Hop IS NSAP Address D 22 Route Type D 22 P partial mesh topology frame relay 2 12 partition area 2 5 password D 6 D 7 D 16 path costs 1 20 D 11 point to point mode frame relay 2 9 Port Number parameter D 17 product support xviii pseudonode 1 18 publications hard copy xvii Index 4 R record route options 1 22 redirection 1 24 2 13 D 17 relative cost 1 20 routing domain 1 4 routing process 1 21 routing protocols 1 22 S sending TARP requests 4 23 shorte
36. ARP discards the packet If the timer is not running the tar seq remains 0 and the TARP LDB timer is started Loop Detection Buffer Size You can configure the maximum number of entries for the loop detection buffer When a loop detection buffer that contains the maximum number of entries receives a new entry TARP removes the oldest entry Loop Detection Timer Each tar seq field with a value of 0 has an associated timer the TARP LDB timer that you can configure When this timer expires TARP removes the entry from the buffer 308637 14 00 Rev 00 1 33 Configuring OSI Services Flush Timer The loop detection buffer also has a flush timer When it expires TARP empties the entire buffer You can configure this timer to any value from 0 to 1440 minutes The default is 5 minutes 1 34 308637 14 00 Rev 00 Chapter 2 OSI Implementation Notes This chapter contains information about configuring Nortel Networks routers with special network considerations Before you implement the enabling Chapter 3 and general configuration Chapter 4 procedures review the following sections in this chapter for information that might affect your network Configuring manual area addresses Correcting area partitions Configuring static external adjacencies Configuring OSI over DDN X 25 Configuring DECnet IV to V Transition Configuring OSI over frame relay Configuring OSI over ATM 308637 14 00 Rev 00 2 1 Configuring OSI Servic
37. ATM Services 2 14 308637 14 00 Rev 00 To configure OSI to run over ATM OSI Implementation Notes You do this Site Manager Procedure System responds 1 In the Configuration Manager window click on an ATM link module interface ATM1 The Add Circuit window opens 2 Click on OK The Initial ATM Signaling Config window opens Click on Help for more information about any field For OSI over ATM Protocol Standard can be either UNI_V30 or UNI V31 3 Edit any parameters you need to change 4 Click on OK The Edit ATM Connector window opens 5 Click on Service Attributes 6 Click on Add The ATM Service Records List window opens The ATM Service Record Parameters window opens 7 Setthe Data Encapsulation Type parameter to LLC SNAP or NLPID 8 Press the Enter or Tab key to advance to 9 Setthe Virtual Connection Type parameter to PVC the Virtual Connection Type parameter 10 Click on OK The Select Protocols window opens 11 Click on OSI and then click on OK The OSI Configuration window opens 12 Set the Router ID parameter Click on Help for more information 13 Click on OK Site Manager asks if you want to edit the OSI interface details 14 Click on OK to edit OSI interface parameters or Cancel to accept the default values The ATM Virtual Channel Link window opens 15 Click on Add The ATM Virtual Ch
38. BayRS Version 14 00 Part No 308637 14 00 Rev 00 September 1999 4401 Great America Parkway Santa Clara CA 95054 Configuring OSI Services NORTEL NETWORKS Copyright 1999 Nortel Networks All rights reserved Printed in the USA September 1999 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 Nortel Networks NA Inc The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that license A summary of the Software License is included in this document Trademarks NORTEL NETWORKS is a trademark of Nortel Networks Bay Networks is a registered trademark and ASN BayRS and BayStack are trademarks of Nortel Networks All other trademarks and registered trademarks are the property of their respective owners Restricted Rights Legend Use duplication or disclosure by the United States Government is subject to restrictions as set forth in subparagraph c 1 ii of the Rights in Technical Data and Computer Software clause at DFARS 252 227 7013 Notwithstanding any other license agreement that may pertain to or acco
39. Frame Relay arenarie Era EHI XIGE E rnin 2 8 Gonarigared od COEPI sisiriha dai abet boda a ub gat gc RI prd aan PRAE 2 8 Fame Platos COMUNE ausos pasara annii AA dea Oca bd cd 2 9 Rl e 2 9 sWcplcrl c 2 10 PUEDEN adsscte sitet PUER ERE BEER E E EE E E Bo be E REUS s 2 10 Lb ife o 2 11 Esos quest p T 2 11 Full Mesh Topology PICS memes reino seis rare icine aaan Genie 2 11 Furia Mesh TODSIBUN dissert piede riu ese una ll raa peer anata 2 12 gis Ups 61122 e MET DE m 2 13 Designated Router Seletti MENT 2 14 vi 308637 14 00 Rev 00 ps Respir DEDSOUDE Lair eadeni abo dete aab bob tp danda cc cia db d 2 14 TEMAS ENN SOM ina ee asec n Hcc 2 14 COMM OS OVS Pip et 2 14 Chapter 3 Enabling OSI and TARP Services Chapter 4 Editing OSI and TARP Parameters Prec ct p O rci EDO T 4 2 Editing OSI Global Parameters Nose dben QS seman T ora isein en 4 4 Biting OS Intemace Paraielt ES 25 arcsec os aet etre a LE x DER E Ra POI E DR BA 4 5 Configuring Manual Area Addresses ssssssssssssseseeeeee nennen 4 6 Deleting a Manual Area AOUIGSS iius ciissessetes tees ptex esee petu IE ep Ett a nonesa annaa 4 7 Configuring Static End System Adjacencies sess 4 8 Adding a Static End System Adjacency no eni UT iube qus E 48 Copying a Static End System AdISGelg
40. Help or see the parameter description on page D 23 5 Click on OK A dialog box prompts Do you want to edit the OSI Interface details 6 Click on Cancel The TARP Parameters window opens 7 Setthe Target Identifier parameter Click on Help or see the parameter description on page D 24 8 Click on OK The Edit OSI Interface window opens 9 Acceptthe defaults or edit the parameters as your network requires When you are finished click on OK You return to the Configuration Manager window 308637 14 00 Rev 00 Configuring OSI Services Editing TARP Global Parameters To edit TARP global parameters complete the following tasks Site Manager Procedure You do this System responds 1 In the Configuration Manager window The Edit TARP Global Parameters choose Protocols OSI Tarp window opens Global 2 Edit one or more of the following parameters Enable Target Identifier Tarp Originate Pkt Lifetime Start Sequence Number Tarp Data Cache Tarp L2 Data Cache Tarp T1 Timer Tarp T2 Timer Tarp T3 Timer Click on Help or see the parameter descriptions beginning on page D 23 3 When you are finished click on OK You return to the Configuration Manager window 4 18 308637 14 00 Rev 00 Editing OSI and TARP Parameters Editing TARP Circuit Parameters To edit TARP circuit parameters Site Manager Procedure
41. LUSIVE AGREEMENT BETWEEN NORTEL NETWORKS AND LICENSEE WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS AGREEMENT NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST NORTEL NETWORKS UNLESS NORTEL NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT INCLUDING AN EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT iv 308637 14 00 Rev 00 Contents Preface rn pes De nisus I ee ET OO LT xiii TOE I serio stcoes teats A A E P N cada ea deep meat net eet xiv PO DI EMT TIE UU I TE M XV Hard Gopy Technical Manuals Luisa ederadatni iaou aud Sex ex Ra xvii Fon to Get HoN aeracion nira aE Da i A xviii Chapter 1 OSI Overview Oo Bask Relorance Monel em 1 2 GSI Ia COPIED SOR nanai a aD E ARA 1 8 Lavel 1 and Lovell CMMI ER T p 1 4 E RE Fg 1 5 Laele Bau ancossstipbaagen ectveus saanaceate R PU RPG RU APA Mn qud HIER RN 1 6 95 Newark Addressing ooi or tat sped EAAS 1 6 eiie nir Mt N 1 7 Allocating NSAP AOOFOSEOB 1s is eupnesa d xni edes and eee RE e 1 13 OSI Basic Routing Algorithm bh sisted HM Edd idd esheets bes Td 1 17 EDO POPE e A dq pump Da D eet ase iia e UR ROTE an ee 1 18 DEES On Pe A TT d 1 20 FOP RONG PIG SS A 1 21 CoS Pp PETDIOOOLS esci gets ra rta a donat abus entrado eret ante eee 1 22 Connectionless Network Service Protocol PAE TE E NES 1 22 End System to Intermedi
42. MIB Object ID e If this circuit is an X 25 PDN circuit then enter a valid X 121 address for the remote router in decimal format e Tf this circuit is an X 25 DDN circuit then enter a valid X 121 address for the remote router in decimal format e If this circuit uses PPP then leave this field blank e If this circuit is of any other type then enter any valid MAC address 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 TP to X 121 Address Mapping for DDN for the conversion algorithm D 20 308637 14 00 Rev 00 Parameter Path Default Options Function Instructions MIB Object ID Site Manager Parameters External Address Metric Configuration Manager gt Protocols gt OSI gt Interfaces gt External Address Adjacency gt Add 20 1 to 63 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 If you only have a single link to the external adjacency or have no preference regarding which interface is used to access the external domain accept the default value If there are multiple interfaces configured to the same external adjacency and yo
43. 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 I 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 308637 14 00 Rev 00 A 9 Configuring OSI Services Class C DDN X 25 Physical Address Format ZZZZ 1 RRRRR ZZ 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 mapping follows the same rules as for Class A Example For h lt 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 0 003 01 00 00 Note The mapping of X 121 address for Class C networks for h gt 64 is not applicable because the h field can never exceed 15 A 10 308637 14 00 Rev 00 Appendix B Using the Technic
44. SI gt Interfaces gt Static ES Adjacencies gt Add 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 ESID Configuration Manager gt Protocols gt OSI gt Interfaces gt Static ES Adjacencies gt Add 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 308637 14 00 Rev 00 Site Manager Parameters Parameter SNPA Path Configuration Manager gt Protocols gt OSI gt Interfaces gt Static ES Adjacencies gt Add Default None Options Depends on the circuit type see Instructions Function Specifies an SNPA for the adjacent end system Instructions Enter the SNPA for the adjacent end system MIB Object ID e If this circuit is an X 25 PDN circuit then enter any valid X 121 address in decimal format e If this circuit is an X 25 DDN circuit then enter a valid X 121 address for the remote router in decimal format e 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
45. a 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 308637 14 00 Rev 00 2 3 Configuring OSI Services Area XY Assign manual area address 456 to specific end systems Key C End System Oo L1 Router E 11 2 Router OSI0017A Figure 2 3 Manual Area Address 456 Assigned to Specific End Systems 3 Finally to divide area XY completely delete area address 456 from those routers that will remain in area X and delete area address 123 from those routers that will be part of the new area Y Because the end systems in both area X and area Y are assigned corresponding area addresses you do not need to reconfigure them and the division is complete Figure 2 4 2 4 308637 14 00 Rev 00 OSI Implementation Notes Delete 456 from routers in X Delete 123 from routers in Y Key End System W L1 Router BB 1 2 Router OSI0018A Figure 2 4 Area XY Divided into Area X and Area Y For instructions on how to configure manual area address parameters see Configuring Manual Area Addresses on page 4 6 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 occur when there is an improper netwo
46. 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 Manual Area Address Parameter Parameter Path Default Options Function Instructions MIB Object ID This section describes the Area Address parameter Area Address Configuration Manager gt Protocols gt OSI gt Manual Area Addresses gt Add None Any valid OSI area address in hexadecimal notation from 3 to 13 bytes long Specifies a synonymous area address configured on the same intermediate system Enter an area address in hexadecimal notation 1 3 6 1 4 1 18 3 5 6 13 1 308637 14 00 Rev 00 Configuring OSI Services Static End System Adjacency Parameters Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID This section describes the static end system adjacency parameters Enable Configuration Manager gt Protocols gt O
47. 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 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 subaddress and are not used on the DDN The subaddress 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 12 and 14 BCD X 121 addresses A 6 308637 14 00 Rev 00 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 physical 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 physica
48. address 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 308637 14 00 Rev 00 1 41 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 the 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 call
49. an L1 router Level 1 or an L1 L2 router Level 1 and Level 2 An L1 router can support only 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 on page 4 5 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 D 2 308637 14 00 Rev 00 Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Site Manager Parameters Router ID hex Configuration Manager Protocols OSI Global 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 OSI Network Addressing on page 1 6 for more information You set the router ID when you initially enable OSI services in the OSI Configuration window see Chapter 3 Enabling OSI and TARP Se
50. annel Link Parameters window opens continued 308637 14 00 Rev 00 2 15 Configuring OSI Services Site Manager Procedure continued You do this System responds 16 Set the VPI Number parameter Click on Help for more information 17 Set the VCI Number parameter Click on Help for more information 18 Click on OK You return to the ATM Virtual Channel Link window 19 Click on Done You return to the ATM Service Records List window 20 Click on Done You return to the Edit ATM Connector window 21 Click on Done You return to the Configuration Manager window 2 16 308637 14 00 Rev 00 Chapter 3 Enabling OSI and TARP Services This chapter describes how to enable OSI and TARP by specifying values for required parameters only and accepting default values for all other parameters of these services To configure OSI and TARP you must first create and save a configuration file For information about working with configuration files see Configuring and Managing Routers with Site Manager To enable OSI and TARP services Site Manager Procedure You do this System responds ae In the Configuration Manager window choose a link or net module The Add Circuit window opens 2 Click on OK 3 Choose OSI and TARP and then click on OK The Select Protocols window opens The OSI Configuration window opens Set the Router ID parameter Cli
51. as a result of accident misuse or abuse The Licensee assumes all responsibility for selection of the Software to achieve Licensee s intended results and for the installation use and results obtained from the Software Nortel Networks does not warrant a that the functions contained in the software will meet the Licensee s requirements b that the Software will operate in the hardware or software combinations that the Licensee may select c that the operation of the Software will be uninterrupted or error free or d that all defects in the operation of the Software will be corrected Nortel Networks is not obligated to remedy any Software defect that cannot be reproduced with the latest Software release These warranties do not apply to the Software if it has been i altered except by Nortel Networks or in accordance with its instructions ii used in conjunction with another vendor s product resulting in the defect or iii damaged by improper environment abuse misuse accident or negligence THE FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL OTHER WARRANTIES EXPRESS OR IMPLIED INCLUDING WITHOUT LIMITATION ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE Licensee is responsible 308637 14 00 Rev 00 iii for the security of its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or altered files data or programs 4 Limitatio
52. ate System Routing Exchange Protocol 1 23 G niguration Reporting 2axosuszeunanse uat lakc dot e cea aa i Y ad UBER cR 1 23 gl g e pepe Et 1 24 308637 14 00 Rev 00 V Intermediate System to Intermediate System Intra Domain Routing Exchange Protocol Se re E carrie beber net ee ron ene dens 1 26 Ins Doman MOWING asser pico eer a v abc rene EOD eed 1 26 Inter Dermgln ROUN eee meee creer d da ru bur an Ur eum ter eon faoc tr ENENGE pad rt 1 28 MOSES tie Settee pein cae see 1 28 Pow PAREP VON ossis spot qe ka aud ud ane ea eR UE 1 29 TARP Packet Typos ca ccsdsoscoteeinasaccocsianctoovas TT E 1 29 TARP Packet Fieldo M 1 30 A ULI TARP IES iondsstarebenid annia ddl d dtp ccc UR dt aO dra nd 1 31 Finding an NSAP rere A reed dde sends PAT ere E arunan w 1534 miis ys A TID anA 1 31 Receiving TARP Reguesis RR m eE 1 32 Loop DECON sacerdo A OE 1 33 Loop Detection Buiter S SB auia parasti eros uade a dr dea a MD Loop Detection Timer TT TU T ene Scien TT T UT T a 1 838 aim seriosas aaa 1 34 Chapter 2 OSI Implementation Notes Configuring Manual Area Addresses cscs ucccempepece een Ep cen edea 2 2 Gorec Area PaEDHODIB asustivat E Aaa 2 5 Configuring Static External Adjacencies denn TUR esie beset TT TS 2 7 Conmiguring OSl ove DDN duree 2 7 Configuring DECnet IV to V Transition 11i sereni tis repa kun aod aia sai 2 8 toonilgurmg OSI over
53. ate 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 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 308637 14 00 Rev 00 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
54. bnetwork 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 308637 14 00 Rev 00 OSI Overview Note A Nortel 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 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 gt To other L1 routers in Area A End System L1 Router New End System pP 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
55. ce Protocol 1 4 1 22 D 10 conventions text xiv cost metric 1 20 D 11 customer support xviii D Defense Data Network DDN configuring OSI over X 25 2 7 converting IP addresses to X 121 addresses A 2 designated router described 1 18 selection in OSI over frame relay 2 14 detection of loops for TARP 1 33 domain specific part 1 7 E Enable parameter OSI global D 1 OSI interface D 10 Enable Static Adjacency Parameter D 29 enabling OSI and TARP 3 1 End System to Intermediate System Routing Exchange Protocol 1 23 to 1 26 end systems 1 3 1 6 Index 1 external domain 2 7 external routing level 2 7 F forwarding router process 1 21 frame relay 2 8 to 2 14 G global parameters Area Address D 8 CLNP Source Route Support D 10 Enable D 1 L1 LSP Password D 6 L2 LSP Password D 7 Load Balancing D 3 Max Area Addresses D 4 Max End Systems D 4 Max External Addresses D 5 Max L1 Intermediate Systems D 4 Max L2 Intermediate Systems D 5 Max Learned End Systems D 9 Max Learned L1 Intermediate Systems D 9 Max Learned L2 Intermediate Systems D 9 Router ID D 3 Router Type D 2 Government OSI Protocol GOSIP Version 2 0 1 2 1 8 GSA 1 6 H Hello packet exchange 1 23 holding timer 1 24 hub and spoke topology frame relay 2 12 hybrid circuit mode frame relay 2 10 Ignore Adjacent NSAP Address D 29 Ignore Adjacent NSAP Address Static Adjace
56. cessing 1 22 308637 14 00 Rev 00 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 processing 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 0 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
57. chnician Interface View TARP data caches using the Technician Interface Delete OSI globally from the Nortel Networks router 308637 14 00 Rev 00 4 1 Configuring OSI Services Accessing OSI Parameters You access all OSI parameters from the Configuration Manager window Figure 4 1 Refer to Configuring and Managing Routers with Site Manager for details about accessing this window E Gmfigatio Waagr fd Configuration Mode local SNMP Agent LOCAL FILE File Name tmp_mnt usr21 techpubs jbb osi cfg Model Backbone Link Node 2 BLN 2 MIB Version 9 00 Soe Used MIES Description Connectors 5405 Dual Ethernet XCVR2 XCVR1 5720 Single Sync ASYNC Sin comi TOKEN1 O o EmtyS5Siot o o Empty Sio o System Resource Module EEE 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 Manual area address e Static adjacency e Static route e TARP 4 2 308637 14 00 Rev 00 Editing OSI and TARP Parameters For each OSI and TARP parameter this chapter describes the default setting all valid setting options the parameter function instructions for setting the parameter and the MIB object ID 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 Fo
58. ck on Help or see the parameter description on page D 3 Set the Area Address parameter if necessary Click on Help or see the parameter description on page D 8 Click on OK A dialog box prompts Do you want to edit the OSI Interface details Click on Cancel The TARP Parameters window opens continued 308637 14 00 Rev 00 3 1 Configuring OSI Services Site Manager Procedure continued You do this System responds 8 Set the Target Identifier parameter Click on Help or see the parameter description on page D 24 9 Click on OK The Edit OSI Interface window opens 10 Click on OK You return to the Configuration Manager window OSI and TARP services are now enabled with default parameter values To customize any of these values see Chapter 4 Editing OSI and TARP Parameters 3 2 308637 14 00 Rev 00 Chapter 4 Editing OSI and TARP Parameters After you enable an OSI interface you can use Site Manager to edit OSI parameters and customize OSI services This chapter describes how to Access OSI parameters Edit OSI global parameters Edit OSI interface parameters Configure manual area addresses Configure static end system adjacencies Configure static external address adjacencies Configure static routes Edit TARP global parameters Edit TARP circuit parameters Configure TARP static adjacencies Send TARP requests using the Te
59. e 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 systems of the most desirable route to a particular destination either Through a different router or e 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 308637 14 00 Rev 00 Destination system is on the same subnetwork Example 1 Preferred path Key O Originating End System D Destination System Lu End System T Router Figure 1 12 Route Redirecting
60. ecifies whether the router can originate TARP packets for this interface The only reason for the router to originate TARP packets is for debugging purposes A router can forward TARP packets even if it cannot originate TARP packets If you want the router to originate TARP packets accept the default Otherwise choose Disable 1 3 6 1 4 1 18 3 5 6 14 5 D 24 308637 14 00 Rev 00 Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Site Manager Parameters Pkt Lifetime Configuration Manager Protocols OSI Tarp Global 25 1 to 100 Specifies the maximum number of hops a TARP packet that this router originates can make Choose a value within the valid range or accept the default value 1 3 6 1 4 1 18 3 5 6 14 6 Start Sequence Number Configuration Manager gt Protocols gt OSI gt Tarp gt Global 1 1 to 65535 Each TARP packet that the router originates has a sequence number that increments by one for each packet sent Choose the number that you want the router to use for the first packet 1 3 6 1 4 1 18 3 5 6 14 7 Tarp Data Cache Configuration Manager gt Protocols gt OSI gt Tarp gt Global Enable Enable Disable Specifies the Level 1 database of the TID to NSAP mappings that the router learns from
61. ed 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 BayRS Version 7 60 and later software are United States Government OSI Protocol GOSIP Version 2 0 compliant In addition Nortel Networks router software provides support for the first three layers of the ISO 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 308637 14 00 Rev 00 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 connect
62. ed 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 Figure 1 7 1 12 308637 14 00 Rev 00 OSI Overview 4 Area Address Organization Identifier 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 OSIO008A Figure 1 7 NSAP Area Address When a router receives a packet it examines the contents of the packet s NSAP destination area address fields The router compares its own NSAP area addresses 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 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
63. eesessss 4 23 308637 14 00 Rev 00 vii Viewing TARP Data Caches Using the Technician Interface ssessss 4 23 Deleting OSI from the Router ere RA Tonu TATE T TOUT m 4 24 Appendix A IP to X 121 Address Mapping for DDN IP t0 X 121 cp cial ees A 2 Wu T A 2 Ba OUI M M A 3 Standard IP to X 121 Address Mapping ere adani T T TT Mores s A 7 RII RR A 7 LISSE B aevo mit pM od a adi uU asi e NE n SR HUM SIM A 9 MC cce M A 10 Appendix B Using the Technician Interface osi Isp Command Appendix C Enabling the wfOsiFletchRelaxedEnable Attribute Using the Technician Interface Appendix D Site Manager Parameters OSI Global Parameters Lee EA AEn errr ttre bipes oe PA E M EPA ERRETRN D 1 OSI Interface Parameters L uovcs iR vn XR ann ies E REPRE Cog ERR Feo FE DUCP POE RR CLI PO Ein D 10 Manual Ares Address Parameter 1 2 aie ipid docere aea ona Urna Din ua tax caa D 17 Static End System Adjacency Parameters esses torcien tree nomeu nian anaes D 18 Static External Address Adjacency Parameters essen D 19 Static Route Parametere ansien ciet reed aat bet dus EN D 21 TP Cleat Para E m D 23 TARP CURE PAS arriarekin nor aiaa E tama dede x ord a DRE x da D 27 TARP Static Adjacency Parameters ere bein EIT abends re TUR i D 28 TARP Ignore Adjacencies Paramoel
64. ers iere enden rank ne anne Er bn rY Er ana cedi D 29 Index viii 308637 14 00 Rev 00 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 4 1 Figure A 1 Figure A 2 Figure A 3 Figures OSI Neo DEQaBIZSOUE 2 250 pn eR RE brred aa xe cd tea tra ine Ud DAR ERR 1 4 L1 Routing within an Area and L2 Routing Between Areas 1 5 Hierarchical Addressing Authority Structure ssesssssss 1 7 Basie NSAP Address SIFUCUIB usse iere n o eec a ica cd e PSO GOSIP NSAP Address Format uss Rinnai T TT E ANSIMSAP Address Format ideis Liban tenir teases er reste 1 11 NGAP Area Address oues ote EU Rc pedro Roa pU PLE e e UE apres a Eun 1 13 Campus Roung DCB a sscssiteseex en t EP nanna 1 14 Assigning NSAP Addresses sess 1 16 Router 1 Floods Area A with LSPs About the New End System 1 19 Lowest Cost Path Router A to B IO ES 1usceicadisete trt ap ib ren tette 1 21 Pouto Rodec pm T 1 25 Static Intet Domai FOUND 4 ooe toca Fete daa Forti dates exigi pee es Iona beer vigens 1 27 Original Area Addresses for Area XY sess 2 2 Manual Area Address 456 Assigned to All Routers in Area XY 2
65. es Configuring Manual Area Addresses Manual area addresses are synonymous area addresses configured on the same intermediate system You may want to configure manual area addresses when more than one addressing authority can assign addresses to the routing domain or to allow a routing domain to be reconfigured during operation A manual area address is a second or third area address configured for systems residing in a single area When used appropriately the manual area address 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 was originally assigned the area address 123 The network administrator plans to divide the area into two smaller more manageable areas area X and area Y Area XY End System L1 Router BB 1 2 Router OSI0015A Figure 2 1 Original Area Addresses for Area XY To take advantage of the manual area address feature the administrator can 1 Assign the area address 456 to all routers within area XY Figure 2 2 2 2 308637 14 00 Rev 00 OSI Implementation Notes Area XY Assign manual area address 456 to all routers in XY Key End System E L1 Router Bl 11 2 Router OSI0016A Figure 2 2 Manual Area Address 456 Assigned to All Routers in Area XY 2 Assign the area address 456 to those end systems that will eventually belong to area Y when are
66. es see cer rro nino annu re Yu XRRE D 12 308637 14 00 Rev 00 xi Preface This guide describes Open Systems Interconnection OSI architecture and services and what you do to start and customize OSI services on a Nortel Networks router Before You Begin Before using this guide you must complete the following procedures For a new router e Install the router see the installation guide that came with your router e Connect the router to the network and create a pilot configuration file see Quick Starting Routers Configuring BayStack Remote Access or Connecting ASN Routers to a Network Make sure that you are running the latest version of Nortel Networks BayRS and Site Manager software For information about upgrading BayRS and Site Manager see the upgrading guide for your version of BayRS 308637 14 00 Rev 00 xiii Configuring OSI Services Text Conventions This guide uses the following text conventions angle brackets lt gt bold text brackets italic text 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 the command syntax is ping ip address you enter ping 192 32 10 12 Indicates command names and options and text that you need to enter Example Enter show ip alerts routes Example Use the dinfo command Indicate optional elements in syntax descriptions Do n
67. es 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 OSI and TARP OSI uses the TID Address Resolution Protocol TARP to map OSI network service access point NSAP Level 3 addresses to target identifier TID addresses It is similar to the DNS protocol that IP uses where names are converted to IP addresses A TID is a name that applies to an entire router It can be any text string up to 40 characters long and is similar to a UNIX host name OSI addresses also apply to an entire router An OSI NSAP address consists of the domain address area address the router ID and a value called the N selector which is always 00 It can be up to 13 bytes long TARP locates either the OSI NSAP address of a particular TID address or the TID address of a particular OSI NSAP address 1 28 308637 14 00 Rev 00 How TARP Works OSI Overview TARP resolves the NSAP to TID mapping by flooding requests that network management stations originate throughout the OSI domain When a request reaches the network entity that owns the requested TID or NSAP that entity sends a respon
68. esignated Router Priority Configuration Manager gt Protocols gt OSI gt Interfaces 64 1 to 127 Specifies which L2 router becomes the L2 designated router for the LAN segment See Update Process on page 1 18 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 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 1 3 6 1 4 1 18 3 5 6 3 9 IIH Hello Timer Configuration Manager Protocols OSI Interfaces 8 2 4181151301601 12013001 600 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 308637 14 00 Rev 00 Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Functi
69. evel 1 and Level 2 adjacencies except the one that sent the packet and resets the sequence number of this packet If the tar tcd field has a value of 5 it is a request for this router s TID The router responds with a Type 3 packet or by forwarding a Type 5 packet to another router If none of the above cases is true the router forwards the packet to its appropriate adjacencies 1 32 308637 14 00 Rev 00 OSI Overview Loop Detection To prevent TARP storms and recursive loops in a looped topology TARP maintains a loop detection buffer LDB that keeps a record of the last sequence number received from a particular NSAP It checks each TARP protocol data unit PDU that it receives against any corresponding entry in the loop detection buffer If it finds no match t processes the packet and adds a new entry to the loop detection buffer e It checks the tar seq field If the value is 0 it starts a timer set to the value of the TARP LDB timer When this timer expires the entry is removed If there is a match TARP compares the tar seq value in the received packet with the value in the LDB entry e Ifthe packet s tar seq value is nonzero and is lower than the value in the buffer it discards the packet e If the packet s tar seq value is greater than the value in the buffer TARP processes the packet and assigns this tar seq value to the buffer e Ifthe packet s tar seq value is 0 and the TARP LDB timer is running T
70. formation 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 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 308637 14 00 Rev 00 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 LSP
71. full mesh topologies 308637 14 00 Rev 00 2 13 Configuring OSI Services Designated Router Selection OSI over group access frame relay uses the highest system ID for designated router selection This feature breaks 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 For more information about designated routers see Update Process on page 1 18 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 Configuring OSI over ATM Asynchronous transfer mode ATM is a connection oriented cell based technology that relays traffic across a Broadband Integrated Services Digital Network B ISDN ATM provides a cost effective way of transmitting voice video and data across a network For complete instructions on configuring ATM see Configuring
72. ge D 29 4 Click on OK The TARP Ignore Adjacencies window opens 5 When you are finished click on Done You return to the Configuration Manager window Sending TARP Requests Using the Technician Interface To request that the router originate a TARP packet you use the Technician Interface tarp pkt command This command accepts the following arguments t lt type gt Specifies the type of TARP packet to send 1 2 4 or 5 i TID TID to include in the request Valid only for Type 1 Type 2 and Type 4 packets The request is for the NSAP that maps to this TID n NSAP NSAP to include in the request Valid only for Type 4 or Type 5 packets The request is for the TID that maps to this NSAP f Enables you to find an NSAP by going through a timer sequence see Finding an NSAP on page 1 31 Viewing TARP Data Caches Using the Technician Interface The following commands display TARP data caches tarp Idb Displays the loop detection buffer entries tarp tdc Displays the TARP data cache 308637 14 00 Rev 00 4 23 Configuring OSI Services Deleting OSI from the Router To delete the OSI routing protocol from all router circuits on which it is currently enabled Site Manager Procedure You do this System responds 1 In the Configuration Manager window A window prompts choose Protocols OSI Delete OSI Do you REALLY want to delete OSI 2 Click on OK The Configuration Manager
73. he parameter descriptions beginning on page D 21 The static external adjacency is no longer listed Click on OK to implement your changes The new static route you defined appears in the OSI Static Routes window Repeat steps 1 through 3 to add additional static routes Copying Static Routes To copy a static route complete the following tasks Site Manager Procedure You do this System responds 1 In the OSI Static Routes window select the static route that you want to copy Click on Copy 3 Specify the static route parameters Click on Help or see the parameter descriptions beginning on page D 21 The new static route you defined appears in the OSI Static Routes window 4 Click on OK Repeat steps 1 through 4 to copy additional static routes When you are finished click on Done You return to the Configuration Manager window 308637 14 00 Rev 00 4 15 Configuring OSI Services Editing Static Routes To edit a static route Site Manager Procedure You do this System responds 1 In the OSI Static Routes window select the static route that you want to edit Edit one or more of the following parameters Enable Destination NSAP Address Route Type Next Hop IS NSAP Address Default Route Metric Click on Help or see the parameter descriptions beginning on page D 21 Click on Apply to imple
74. ian Interface osi Isp Command The Technician Interface osi Isp command displays all or a subset of the link state packet LSP elements in the OSI link state database You can use this information to help solve network problems You can use the following command filters and arguments with this command S lt slot gt lt evel gt i lsp id Displays information from the specified slot only If you do not specify a slot the Technician Interface retrieves information from the slot where OSI is currently running If OSI is not running on a local slot the Technician Interface retrieves information from the lowest numbered slot that is running OSI Displays information from either the OSI Level 1 or Level 2 link state database If you do not specify a level the Technician Interface searches both databases Displays the LSP that has the specified sp id The sp id is an 8 byte value consisting of the 6 byte system ID the 1 byte N selector and the 1 byte LSP number To display a range of LSPs enter the first x bytes of the Isp id For example in the OSI Level 1 link state database there are two LSPs and their IDs are 4646464646460000 and 4646464646460200 To display both LSPs enter i 464646464646 308637 14 00 Rev 00 B 1 Configuring OSI Services n nbr id p prefix Displays those LSP elements that contain the specified nbr id The nbr idis a 7 byte value consisting of the 6 byte syste
75. ica MA 800 2LANWAN 800 252 6926 Santa Clara CA 800 2LANWAN 800 252 6926 Valbonne France 33 4 92 96 69 68 Sydney Australia 61 2 9927 8800 Tokyo Japan 81 3 5402 7041 xviii 308637 14 00 Rev 00 Chapter 1 OSI Overview This chapter provides a general overview of OSI networking and describes how OSI routing services for Nortel Networks routers work It includes information about the following topics OSI basic reference model OSI network organization Level 1 and Level 2 routing Network addressing Link state routing algorithm Routing protocols OSI and TARP Note This guide uses the terms intermediate system and router interchangeably 308637 14 00 Rev 00 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 impos
76. ices If you want to run OSI over DDN X 25 you must e Configure IP over an X 25 DDN circuit See Configuring IP Services for details e 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 For details about the address conversion see Chapter 4 Editing OSI and TARP Parameters See Appendix D Site Manager Parameters for details about the SNPA parameter 308637 14 00 Rev 00 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 For information about the DECnet IV to V Transition feature see Configuring DECnet Services Configuring OSI over Frame Relay Frame relay is a high speed shared bandwidth wide area networking protocol Frame relay performs only basic processing on each packet allowing frame relay networks to operate at high speeds with few delays but with little error detection For general information about the protocol see Configuring Frame Relay Services Configuration Overview To run OSI over frame relay you must 1 Configure a frame relay circuit using Site Manager For frame relay configuration information see Configuring Frame Relay Services C
77. interface For information about configuring PVCs see Configuring Frame Relay Services Frame Relay Network Interface 1 PVC 1 Interface 2 PVC 2 OSI0019A Figure 2 6 Frame Relay Direct Access Mode 308637 14 00 Rev 00 2 9 Configuring OSI Services 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 broadcast packet Figure 2 7 shows group access mode with multiple PVCs on a single subnetwork configured on the same interface Frame Relay Network Interface 1 PVC 1 PVC2
78. ion 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 9578 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 workstations file servers and printers 308637 14 00 Rev 00 1 3 Configuring OSI Services Intermediate systems originate and receive data as well as forward route data The Nortel 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 r
79. ket toward the next hop The record route function records the paths followed by a packet as it traverses a series of routers OSI Routing Protocols This section summarizes the following OSI routing protocols that the Nortel Networks OSI router uses at the networking level SO 6473 Connectionless mode Network Service Protocol CLNP which defines the data packet format procedures for the connectionless transmission of data and control information e ISO 9542 End System to Intermediate System Routing Exchange Protocol which defines how end systems and intermediate systems exchange configuration and routing information to facilitate the routing and relaying functions of the network layer e ISO 10569 Intermediate System to Intermediate System Routing Exchange Protocol which defines how L1 and L2 routing work Connectionless Network Service Protocol Connectionless 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 A 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 pro
80. l address ZZZZ F III HH ZZ SS Where e ZZZZ 0000 e F 0 because the address is a physical address e ll is a three decimal digit representation of i right adjusted and padded with leading zeros if required e HH is a two decimal digit representation of h right adjusted and padded with leading zeros if required e ZZ 00 is optional e SS is an optional subaddress 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 308637 14 00 Rev 00 A 7 Configuring OSI Services Example IP Address 26 29 0 122 Format n h l i DDN X 25 Physical ZZZZ F il HH ZZ SS Address Format X 121 Address 0000 JO 122 29 00 00 For h gt or 64 If the host field h is greater than or equal to 64 the address corresponds to the following DDN X 25 physical address ZZZZ F RRRRR 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 308637 14 00 Rev 00 IP to X 121 Address Mapping for DDN Example IP Address 26 80 0 122 Format n h l i DDN X 25
81. m ID and the 1 byte N selector The Technician Interface searches both the intermediate system IS neighbors and end station ES neighbors section of the Level 1 link state database and the IS neighbors section of the Level 2 link state database To display a range of neighbors enter the first x bytes of the nbr id For example in the OSI Level 1 link state database there are two IS neighbors and their IDs are 46464646464602 and 46464646464600 To display both LSP elements enter n 464646 Displays those LSP elements that contain the specified address prefix The Technician Interface searches both the area address section and the prefix neighbors section of the Level 2 link state database If you specify the l option for Level 1 this option is ignored To display a range of reachable address prefix neighbors enter the first x bytes of the prefix For example in the OSI Level 2 link state database there are two area addresses 490040 and 490030 To display both LSP elements enter n 4900 Displays all information about the LSP By default only the LSP header displays LSP ID SEQ NUM TTL LEN and CKSUM Displays the total count of LSPs that match the options entered 308637 14 00 Rev 00 Using the Technician Interface osi Isp Command When you omit the f option which is the default the output includes the following information ID SEQ NUM TTL LEN CHECKSUM An 8 byte value consisting of the
82. ment your changes Repeat steps 1 through 3 to edit additional static routes When you are finished click on Done You return to the Configuration Manager window Deleting Static Routes To delete a static route Site Manager Procedure You do this System responds 1 In the OSI Static Routes window select the static route that you want to delete 2 Click on Delete The static route is no longer listed Repeat steps 1 and 2 to delete additional static routes 4 When you are finished click on Done You return to the Configuration Manager window 308637 14 00 Rev 00 Editing OSI and TARP Parameters Configuring TARP You can use Site Manager to configure TARP parameters However to originate TARP requests and to view the contents of the TARP data caches and the L2 data cache you must use the Technician Interface To configure TARP you need to provide a target ID TID for the first circuit you configure All other parameters have default values which you can edit according to your network requirements Site Manager Procedure You do this System responds 1 In the Configuration Manager window select a link or net module The Add Circuit window opens 2 Click on OK The Select Protocols window opens 3 Choose OSI and TARP then click on OK The OSI Configuration window opens 4 Setthe Router ID parameter Click on
83. mpany the delivery of this computer software the rights of the United States Government regarding its use reproduction and disclosure are as set forth in the Commercial Computer Software Restricted Rights clause at FAR 52 227 19 Statement of Conditions In the interest of improving internal design operational function and or reliability Nortel Networks NA Inc reserves the right to make changes to the products described in this document without notice Nortel Networks NA 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 may be 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 acknowledge that such portions of the software were developed by the University of California Berkeley The name of the University may not be used to endorse or promote products derived from such portions of the software without specific prior written permission SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED AS IS AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY
84. n describes the TARP ignore adjacency parameters Enable Configuration Manager gt Protocols gt OSI gt Tarp gt Adj Ignore None Enable Disable Enables the router to ignore the static adjacency that you defined using the Ignore Adjacent NSAP Address parameter Select Enable or Disable 1 3 6 1 4 1 18 3 5 6 18 1 2 Ignore Adjacent NSAP Address Configuration Manager gt Protocols gt OSI gt Tarp gt Adj Ignore None Any valid NSAP address Specifies the adjacency that you want the router to ignore for purposes of forwarding TARP packets Enter the address in hexadecimal format 1 3 6 1 4 1 18 3 5 6 18 1 3 308637 14 00 Rev 00 D 29 A acronyms xv address conversion IP to X 121 A 1 addressing authority 1 6 administrative domain 1 4 ANSI 1 6 area address described 1 12 area address manual configuration example 2 2 configuring 4 6 deleting 4 7 area partition 2 5 areas 1 4 ATM 2 14 Broadband Integrated Services Digital Network B ISDN 2 14 broadcast mode frame relay 2 9 C circuit costs 1 20 D 11 circuit modes frame relay 2 9 circuits 2 14 class of Internet address A 3 command osi Isp B 1 configuration reports 1 23 configuration timer 1 24 308637 14 00 Rev 00 Index configuring OSI considerations 2 1 initial 3 1 over ATM 2 14 over frame relay 2 8 to 2 14 configuring TARP 3 1 Connectionless Network Protocol 1 4 Connectionless Network Servi
85. n of liability IN NO EVENT WILL NORTEL NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY COST OF SUBSTITUTE PROCUREMENT SPECIAL INDIRECT INCIDENTAL OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE EVEN IF NORTEL NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES IN NO EVENT SHALL THE LIABILITY OF NORTEL NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT EXCEED THE PRICE PAID TO NORTEL NETWORKS FOR THE SOFTWARE LICENSE 5 Government Licensees This provision applies to all Software and documentation acquired directly or indirectly by or on behalf of the United States Government The Software and documentation are commercial products licensed on the open market at market prices and were developed entirely at private expense and without the use of any U S Government funds The license to the U S Government is granted only with restricted rights and use duplication or disclosure by the U S Government is subject to the restrictions set forth in subparagraph c 1 of the Commercial Computer Software Restricted Rights clause of FAR 52 227 19 and the limitations set out in this license for civilian agencies and subparagraph c 1 ii of the Rights in Technical Data and Computer Software clause of DFARS 252 227 7013 for agencies of the Department of Defense or their successors whichever is applicable 6 Use of Sof
86. ncy Parameters D 29 implementation notes 2 1 inter domain routing 1 28 Index 2 interface parameters Circuit Password D 16 editing 4 5 Enable D 10 ESH Configuration Time D 15 IIH Hello Timer D 14 IIH Hold Time Multiplier D 16 ISH Hello Timer D 15 ISH Hold Time Multiplier D 16 L1 Default Metric D 11 L1 Designated Router Priority D 13 L2 Default Metric D 12 L2 Designated Router Priority D 14 Redirect Enable Disable D 17 Routing Level D 11 Intermediate System to Intermediate System Intra Domain Routing Exchange Protocol inter domain routing and 1 28 intra domain routing and 1 26 to 1 27 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 1 20 2 12 D 6 D 7 link state packet 1 18 to 1 19 B 1 manual area address configuration example 2 2 configuring 4 6 deleting 4 7 mixed access circuit mode frame relay 2 11 308637 14 00 Rev 00 N neighbor detection 2 14 network addressing domain 1 6 NSAP address area address 1 12 to 1 13 authority and format identifier AFD 1 8 defined 1 6 domain specific part DSP 1 7 finding with TARP 1 31 initial domain identifier IDI 1 8 initial domain part IDP 1 7 OSI accessing parameters 4 2 addressing authority 1 6 administrative domain 1 4 areas 1 4 basic reference
87. oV ues cecus ece tape annia aenea 4 9 Editing a Static End System Adjacency ccccccccceeseeeeseeeseceeeeeeeeeecaeseaeessaeeneeeaes 4 10 Deleting a Static End System Adjacency T er errr ee reani 4 11 Configuring Static External Address Adjacencies ssesssseeenee 4 11 Adding Static External Address Adjacencies sssssssssssss 4 12 Copying Static External Address Adjacencies ssssessseeee 4 12 Editing Static External Address Adjacencies sssssssssses 4 13 Deleting Static External Address Adjacencies pa T MT mea 4 14 COMMUNIC State FOULS eT 4 14 Stole Ture AUS PNM MN RR ise ceeds daniase 4 15 Copying Static Routes anini ees T e lenis aieea T ATTE 4 15 Eding skatit PUPS gorun Dar m ER DER TA od CCo re RARE 4 16 Deleting Stake Route seis cu duas toton Fo asa Eu Aat ua a A uum ana 4 16 snper e 4 17 Editing TARP Global ParametelB iui inr tmt Fl rr etl n ecce APR OR Editing TARP Circuit Parameters biegen due P RT ET ere Recents 419 Coniguring TARP Static AdjacongigS csie aa E 4 19 Adding TARP Static Adjacencies sue ie tee nik cera x Ra et d UA iaai 4 19 Deleting TARP Static Adjacencies m T i pene 4 20 Configuring TARP to Ignore a Static Adjacency seessseeeeenee 4 22 Sending TARP Requests Using the Technician Interface eess
88. ocal domain 1 3 6 1 4 1 18 3 5 6 1 12 IS Checksum Configuration Manager gt Protocols gt OSI gt Global Enable Enable Disable Enables or disables the generation of a nonzero 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 308637 14 00 Rev 00 D 5 Configuring OSI Services Parameter Path Default Options Function Instructions MIB Object ID L1 LSP Password Configuration Manager gt Protocols gt OSI gt Global 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 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 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 pas
89. 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 Max L1 Intermediate Systems Configuration Manager gt Protocols gt OSI gt Global 15 1 to 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 D 4 308637 14 00 Rev 00 Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Site Manager Parameters Max L2 Intermediate Systems Configuration Manager gt Protocols gt OSI gt Global 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 Configuration Manager gt Protocols gt OSI gt Global 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 l
90. on Instructions MIB Object ID Site Manager Parameters ISH Hello Timer Configuration Manager Protocols OSI Interfaces 30 2 4181151301601 12013001 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 Timer Configuration Manager gt Protocols gt OSI gt Interfaces 600 214181151301601 12013001 6001 1800 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 308637 14 00 Rev 00 Configuring OSI Services Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Circuit Password Configuration Manager Protocols OSI Interfaces 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
91. on Manager Protocols OSI Interfaces Default 64 Options 1to 127 Function Specify which L1 router becomes the L1 designated router for the LAN segment See Update Process on page 1 18 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 Instructions 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 MIB Object ID 1 3 6 1 4 1 18 3 5 6 3 8 Note If the network is synchronous for example point to point or X 25 then the routers on each end of the connection must have different values for this parameter or it is ignored This applies only to Nortel 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 PDN or DDN service 308637 14 00 Rev 00 D 13 Configuring OSI Services Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID L2 D
92. onfigure OSI to operate over frame relay For initial OSI configuration information see Chapter 3 Enabling OSI and TARP Services 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 For instructions see Direct Access on page 2 9 2 8 308637 14 00 Rev 00 OSI Implementation Notes Frame Relay Circuit Modes The Nortel Networks 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 Hybrid 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 Figure 2 6 shows direct access mode with each PVC configured as a separate OSI
93. or B the routers could then use Level 2 routing to communicate 2 6 308637 14 00 Rev 00 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 a static external adjacency you must e 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 Editing OSI Interface Parameters on page 4 5 for details e 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 Configuring Static External Address Adjacencies on page 4 11 for details Configuring OSI over DDN X 25 The X 25 Defense Data Network DDN provides end to 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 Serv
94. or any information about the operation design performance or implementation of the Software and user manuals that is confidential to Nortel Networks and its licensors however Licensee may grant permission to its consultants subcontractors and agents to use the Software at Licensee s facility provided they have agreed to use the Software only in accordance with the terms of this license 3 Limited warranty Nortel Networks warrants each item of Software as delivered by Nortel Networks and properly installed and operated on Nortel Networks hardware or other equipment it is originally licensed for to function substantially as described in its accompanying user manual during its warranty period which begins on the date Software is first shipped to Licensee If any item of Software fails to so function during its warranty period as the sole remedy Nortel Networks will at its discretion provide a suitable fix patch or workaround for the problem that may be included in a future Software release Nortel Networks further warrants to Licensee that the media on which the Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days from the date Software is first shipped to Licensee Nortel Networks will replace defective media at no charge if it is returned to Nortel Networks during the warranty period along with proof of the date of shipment This warranty does not apply if the media has been damaged
95. ot type the brackets when entering the command Example If the command syntax is show ip interfaces alerts you can enter either show ip interfaces or show ip interfaces alerts Indicates file and directory names new terms book titles and variables in command syntax descriptions Where a variable is two or more words the words are connected by an underscore Example If the command syntax is show at valid route valid routeis one variable and you substitute one value for it Xiv 308637 14 00 Rev 00 Screen text separator gt Acronyms Preface Indicates system output for example prompts and system messages Example Set Trap Monitor Filters Shows menu paths Example Protocols IP identifies the IP option on the Protocols menu This guide uses the following acronyms AAI ACSE AFI ANSI ARP ASN 1 CLNP CLNS CSNP DCA DCC DCE DDN DFI DLCI DSP DTE ES IS FDDI administrative authority identifier association control service element authority and format identifier American National Standards Institute Address Resolution Protocol abstract syntax notation Connectionless Network Protocol connectionless network service Complete Sequence Number Packet Defense Communication Agency data country code data circuit terminating equipment Defense Data Network domain format identifier data link connection identifier domain specific part data terminal equipment end system to in
96. outing 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 L1 routing for routing data within an area e Level 2 L2 routing for routing data between areas 308637 14 00 Rev 00 OSI Overview You can configure a Nortel Networks router running OSI to function as an L1 router an L2 router or an L1 L2 router Figure 1 2 Routing Domain Area B Area A T 1t 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 308637 14 00 Rev 00 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 ex
97. 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 308637 14 00 Rev 00 D 9 Configuring OSI Services Parameter Path Default Options Function Instructions MIB Object ID CLNP Source Route Support Configuration Manager Protocols OSI Global Enable Enable Disable Enables or disables the processing of source routing options in CLNP packets Set toDisable if this router requires GOSIP v2 support 1 3 6 1 4 1 18 3 5 6 1 38 OSI Interface Parameters Parameter Path Default Options Function Instructions MIB Object ID This section describes the OSI interface parameters Enable Configuration Manager gt Protocols gt OSI gt Interfaces Enable Enable Disable Enables OSI routing on this interface Disable only if you want to disable OSI routing on this interface 1 3 6 1 4 1 18 3 5 6 3 2 308637 14 00 Rev 00 Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Site Manager Parameters Routing Level Configuration Manager gt Protocols gt OSI gt Interfaces Level 1 and Level 2 Level 1 Level 2 Level 1 and Level 2 External L2 External L1 and L2 External ES IS only Specifies the type of traffic that is routed over this interface Select the rou
98. pplication that the NSAP could not be resolved 308637 14 00 Rev 00 1 31 Configuring OSI Services Receiving TARP Requests After OSI processes an inbound OSI packet and determines that it is a TARP packet the TARP software examines the packet If the tar lif field has a value of 0 it discards the packet If the tar pro field has a value other than FE it discards the packet It performs the loop detection procedure on the tar seq field If the packet passes all these checks TARP then checks to see whether the packet is for itself as follows If the tar tcd field has a value of 1 or 2 and the tar ttg field is the router s TID the request is for this router It responds with a Type 3 packet If the tar tcd field has a value of 3 it is either for this router or it could be a Type 3 response packet to another router The router checks to see whether it has any outstanding requests of Type 1 2 or 5 that match this response If so it removes the request from the queue of outstanding requests that it has sent and creates an entry in the TARP data cache for the NSAP TID pair that the response describes If not it drops the packet If the tar tcd field has a value of 4 the router processes and floods it to its adjacencies It checks the TARP data cache for an entry that matches the TID in the tar tor field If found it updates the TID NSAP pair in the data cache with the new information Then it floods the Type 4 packet to all of its L
99. r 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 valid Entering an invalid value can corrupt your configuration 308637 14 00 Rev 00 4 3 Configuring OSI Services Editing OSI Global Parameters To edit the OSI global parameters Site Manager Procedure You do this System responds 1 In the Configuration Manager window choose Protocols gt OSI gt Global The Edit OSI Global Parameters window opens 2 Edit one or more of the following parameters Enable Router Type Router ID Load Balancing Max Area Addresses Max End Systems Max L1 Intermediate Systems Max L2 Intermediate Systems Max External Addresses S Checksum L1LSP Password L2LSP Password Area Address Max Learned End Systems Max Learned L1 Intermediate Systems Max Learned L2 Intermediate Systems CLNP Source Route Support Click on Help or see the parameter descriptions beginning on page D 1 3 When you are finished click on OK You return to the Configuration Manager window 308637 14 00 Rev 00 Editing OSI Interface Parameters To edit an OSI interface Editing OSI and TARP Parameters Site Manager Procedure You do this System responds 1 In the Configura
100. r 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 308637 14 00 Rev 00 2 11 Configuring OSI Services Designated Router 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 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 308637 14 00 Rev 00 OSI Implementation
101. requests it originates When it receives a response the TARP software stores the new entry in the data cache The only reason to disable this parameter is to conserve resources Accept the default or choose Disable 1 3 6 1 4 1 18 3 5 6 14 10 308637 14 00 Rev 00 D 25 Configuring OSI Services Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Tarp L2 Data Cache Configuration Manager gt Protocols gt OSI gt Tarp gt Global Enable Enable Disable Specifies the Level 2 database of the TID to NSAP mappings This cache functions as a proxy to store mappings at remote sites If the router receives a request that is not for it but that is in the Level 2 cache it responds to the request instead of flooding the request to all of its adjacencies Accept the default or choose Disable 1 3 6 1 4 1 18 3 5 6 14 11 Tarp T1 Timer Configuration Manager gt Protocols gt OSI gt Tarp gt Global 15 1 to 3600 Specifies the number of seconds the router waits for a response to a Type 1 request it originated Accept the default or choose another value 1 3 6 1 4 1 18 3 5 6 14 12 Tarp T2 Timer Configuration Manager gt Protocols gt OSI gt Tarp gt Global 25 1 to 3600 Specifies the number of seconds the router waits
102. rface and 3 does not have ISO ES IS 9542 enabled To configure a static end system adjacency You do this Site Manager Procedure System responds 1 In the Configuration Manager window choose Protocols OSI Interfaces The OSI Interface Lists window opens 2 Click on Static ES Adjacencies The OSI Static ES Adjacency List window opens which lists all defined static end System adjacencies If you did not add any end system adjacencies none will be listed Continue to the following sections for instructions on adding copying editing or deleting static end system adjacencies Adding a Static End System Adjacency To add a static end system adjacency Site Manager Procedure You do this System responds 1 In the OSI Static ES Adjacency List window click on Add The OSI Static ES Adjacency Configuration window opens 2 Configure the following parameters Enable ESID SNPA Click on Help or see the parameter descriptions beginning on page D 18 continued 4 8 308637 14 00 Rev 00 Editing OSI and TARP Parameters Site Manager Procedure continued static end system adjacencies You do this System responds 3 Click on OK The new adjacency you defined appears in the End System Adjacency List window 4 Repeat steps 1 through 3 to add additional 5 When you are finished click on Done You return to
103. rk design or when one or more links fail in an area Area partition repair as specified in SO 10589 Intermediate System to Intermediate System Routing Exchange Protocol is currently not supported by this implementation of OSI For information about the role of areas and Level 1 and 2 routing in OSI network organization see Chapter 1 OSI Overview 308637 14 00 Rev 00 2 5 Configuring OSI Services Figure 2 5 demonstrates an improper network design Area 490130 Router A Router B Router C Area 490050 Partition 1 Area 490050 Partition 2 OSI0022A Figure 2 5 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 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
104. rvices 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 Load Balancing Configuration Manager Protocols OSI Global 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 308637 14 00 Rev 00 D 3 Configuring OSI Services Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Max Area Addresses Configuration Manager gt Protocols gt OSI gt Global 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 Configuration Manager gt Protocols gt OSI gt Global 512 1 to 4000 Specifies the maximum number
105. s 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 Generates Router Type LSP Type Describing Sent to L1 designated L1 pseudonode The links to all dynamically learned L1 All L1 routers within router routers and end systems in the local the area area that are reachable over the broadcast subnetwork L1 router L1non pseudonode The links to the L1 designated router All L1 routers within and static links the area L2 designated L2 pseudonode The links to all L1 and L1 L2 routers in All L1 L2 routers router the domain that are reachable over the within the domain broadcast subnetwork and any routes to external domains L2 router L2 non pseudonode The links to the L1 L2 designated All L1 L2 routers 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 su
106. se that contains its NSAP and TID back to the originator When the management station obtains the address it requested it can proceed with its operation such as polling the device for alarms The router s role is to propagate the requests throughout the network forwarding them to Level 1 or Level 2 adjacencies as appropriate TARP Packet Types TARP has five types of packets Table 1 5 Table 1 5 TARP Packet Types Packet Type Function Type 1 Request for the OSI NSAP address that maps to the TID address that the request packet supplies Type 1 requests are only flooded within the originating network entity s routing area Level 1 adjacencies Type 2 Same request as Type 1 but the requests are flooded throughout the OSI domain both Level 1 and Level 2 adjacencies Type 3 Response to either a Type 1 Type 2 or Type 5 request This response is sent directly to the originator of the request Type 4 Notification of a change made to either the TID or NSAP address of a network entity Type 4 packets are flooded throughout the OSI domain Type 5 Request for the TID that maps to the OSI NSAP address included in the request packet Because the destination NSAP is known the request is sent directly to the network entity 308637 14 00 Rev 00 1 29 Configuring OSI Services TARP Packet Fields Each TARP packet includes the following fields Table 1 6
107. ser manual solely in support of authorized use of the Software by Licensee This license applies to the Software only and does not extend to Nortel Networks Agent software or other Nortel Networks software products Nortel Networks Agent software or other Nortel Networks software products are licensed for use under the terms of the applicable Nortel Networks NA Inc Software License Agreement that accompanies such software and upon payment by the end user of the applicable license fees for such software 2 Restrictions on use reservation of rights The Software and user manuals are protected under copyright laws Nortel Networks and or its licensors retain all title and ownership in both the Software and user manuals including any revisions made by Nortel Networks or its licensors The copyright notice must be reproduced and included with any copy of any portion of the Software or user manuals Licensee may not modify translate decompile disassemble use for any competitive analysis reverse engineer distribute or create derivative works from the Software or user manuals or any copy in whole or in part Except as expressly provided in this Agreement Licensee may not copy or transfer the Software or user manuals in whole or in part The Software and user manuals embody Nortel Networks and its licensors confidential and proprietary intellectual property Licensee shall not sublicense assign or otherwise disclose to any third party the Software
108. speed interface See Editing OSI Interface Parameters on page 4 5 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 308637 14 00 Rev 00 OSI Overview Ato Bto ES 15 Ato B cost 5 B to ES cost 10 5 Direct A to ES cost 20 OSI0012A Figure 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 s
109. st path first algorithm 1 20 source routing 1 22 Static Adjacency Parameter D 29 Static Adjacency Parameters Enable D 29 static end system adjacency adding 4 8 configuring 4 8 copying 4 9 deleting 4 11 editing 4 10 static end system adjacency parameters Enable D 18 ESID D 18 SNPA D 19 static external address adjacency adding 4 12 configuring 2 7 4 11 copying 4 12 deleting 4 14 editing 4 13 static external address adjacency parameters Enable D 19 External Address Metric D 21 SNPA 2 7 D 20 static route adding 4 15 configuring 4 14 copying 4 15 deleting 4 16 editing 4 16 308637 14 00 Rev 00 static route parameters Default Route Metric D 23 Destination NSAP Address D 22 Enable D 21 Next Hop IS NSAP Address D 22 Route Type D 22 support Nortel Networks xviii T target identifier TID defined 1 28 finding using TARP 1 31 TARP Adjacency Ignore parameter adding 4 22 TARP circuits enabling or disabling 4 19 TARP global parameters editing 4 18 TARP Ignore Adjacency parameter deleting 4 22 enabling or disalbling 4 23 TARP packet fields 1 30 TARP packet types 1 29 TARP requests originating 1 31 4 23 receiving 1 32 TARP Static Adjacencies parameter adding 4 19 deleting 4 20 TARP static adjacencies adding or deleting 4 19 TARP enabling 3 1 technical publications xvii technical support xviii Technician Interface enabling the Fletcher checksum B 1
110. stem ID is the ID portion of the router s NSAP address You specify the router ID only the first time you configure an OSI interface Site Manager uses this router ID for any additional interfaces you configure Enter a new 6 byte system ID in hexadecimal format If the ID is not 6 bytes add leading zeros Every router in a domain must have a unique system ID using a router s MAC address for the system ID meets this requirement 1 3 6 1 4 1 18 3 5 6 1 6 308637 14 00 Rev 00 D 23 Configuring OSI Services Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Enable Configuration Manager Protocols OSI Tarp Global Enable Enable Disable Enables or disables TARP on this interface If you want to use TARP on the interface accept the default Otherwise choose Disable 1 3 6 1 4 1 18 3 5 6 14 2 Target Identifier Configuration Manager gt Protocols gt OSI gt Tarp gt Global None Any text string from 4 to 40 characters spaces not allowed Identifies the router This is the value that OSI TARP maps to the NSAP address Enter the name that identifies this router 1 3 6 1 4 1 18 3 5 6 14 4 Tarp Originate Configuration Manager gt Protocols gt OSI gt Tarp gt Global Enable Enable Disable Sp
111. sword 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 D 6 308637 14 00 Rev 00 Site Manager Parameters Parameter L2LSP Password Path Configuration Manager Protocols OSI Global Default None Options Any text string 8 characters maximum Function 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 password 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
112. 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 Figure 1 13 illustrates 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 B Routing Domain A Inter domain Routing Intra Domain Routing End System L1 Router L1 L2 Router L1 L2 Bordering Router OSI0014A Figure 1 13 Static Inter Domain Routing 308637 14 00 Rev 00 1 27 Configuring OSI Services 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 prefix
113. tate 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 about where to forward the packet e If the 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 address 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 308637 14 00 Rev 00 1 21 Configuring OSI Services e 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 Nortel 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 pac
114. termediate system Fiber Distributed Data Interface 308637 14 00 Rev 00 XV Configuring OSI Services FTAM GOSIP GSA HDLC ICD IDI IDP IEEE ILI IP IS IS ISO ITU T L1 L2 LAN LDB LSP MAC MIB MOM MOP NSAP OSI PDN PDU PPP PSNP File Transfer and Access Management Government OSI Protocol 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 International Telecommunication Union Telecommunication Standardization Sector formerly CCITT Level 1 Level 2 local area network loop detection buffer link state packet media access control management information base maintenance operations module Maintenance Operations Protocol network service access point Open Systems Interconnection Public Data Network protocol data unit Point to Point Protocol partial sequence number packet xvi 308637 14 00 Rev 00 Preface PVC permanent virtual circuit RFC Request for Comments RIP Routing Information Protocol SNAP Subnetwork Access Protocol SNMP Simple Network Management Protocol SNPA subnetwork point of attachment TARP TID Address Resolution Protocol TCP Transmission Control Protocol TID target identifier VT virt
115. ternal 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 addressing 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
116. ternet 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 multivendor 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 MIL STD X 25 DDN X 25 Host Interface Specification The translation method described in this appendix 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 308637 14 00 Rev 00 IP to X 121 Address
117. the Configuration Manager window Copying a Static End System Adjacency To copy a static end system adjacency Site Manager Procedure You do this System responds 1 In the OSI Static ES Adjacency List window click on the adjacency that you want to copy from the list Click on Copy Set the ESID parameter for that adjacency Click on Help or see the parameter description on page D 18 Site Manager prompts you for the end system ID ESID Click on OK The new adjacency you copied appears in the OSI Static ES Adjacency List window Repeat steps 1 through 4 to copy additional static end system adjacencies When you are finished click on Done You return to the Configuration Manager window 308637 14 00 Rev 00 4 9 Configuring OSI Services Editing a Static End System Adjacency To edit a static end system adjacency Site Manager Procedure You do this System responds 1 In the OSI Static ES Adjacency List window click on the adjacency that you want to edit Edit one or more of the following parameters Enable ESID SNPA Click on Help or see the parameter descriptions beginning on page D 18 Click on Apply to implement your changes Site Manager displays the new values for the parameters you edited Repeat steps 1 through 3 to edit additional static adjacencies When you are finished click on Done
118. 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 Figure 1 6 308637 14 00 Rev 00 OSI Overview octets 1 2 1 3 2 2 2 6 1 Organization Identifier IDP Initial Domain Part Reserved DSP Domain Specific Part Routing Domain Identifier AFI Authority and Format Identifier Area Identifier IDI Initial Domain Identifier System Identifier DFI Domain Format Identifier NSAP Selector OSI0007A Figure 1 6 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 an NSAP
119. ting level that matches the level of traffic you want to route 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 on page 4 4 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 on page 4 11 for instructions 1 3 6 1 4 1 18 3 5 6 3 5 L1 Default Metric Configuration Manager Protocols OSI Interfaces 20 1 to 63 Specifies the default metric relative cost of routing Level 1 traffic over this interface OSI 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 D 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
120. tion 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 308637 14 00 Rev 00 Configuring OSI Services i l DSP l l l NSAP for IBF router in Area A 39 840 81 113527 AFI IDI DFI ORG Rsvd RDI Area ID S amp Area address pomme ae Se Se SS mium mmy uy mmm m um ee cm m Mm murem m emm m em Sa mmm 1 I l l l l l NSAP for IDP i DSP i router in Area B 39 840 81 113527 AFI IDI DFI ORG Rsvd RDI Area ID S dM Areaaddress gt pm p M e 1 l l l l DSP NSAP for I l router in Area B Rsvd RDI Area ID S lt Area address OSIO010A 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 308637 14 00 Rev 00 OSI Overview OSI Basic Routing Algorithm The OSI routing algorithm is based on link state in
121. tion Manager window choose Protocols OSI Interfaces The OSI Interface Lists window opens which displays all interfaces on which OSI is enabled 2 Click on an interface to select it Edit one or more of the following parameters Enable Routing Level L1 Default Metric L2 Default Metric L1 Designated Router Priority L2 Designated Router Priority IIH Hello Timer ISH Hello Timer ESH Configuration Timer Circuit Password IIH Hold Time Multiplier ISH Hold Time Multiplier Redirect Enable Disable Click on Help or see the parameter descriptions beginning on page D 10 4 Click on Apply to implement your changes 5 When you are finished click on Done You return to the Configuration Manager window 308637 14 00 Rev 00 Configuring OSI Services Configuring Manual Area Addresses Manual area addresses are synonymous area addresses configured on the same intermediate system router You may want to configure manual area addresses when more than one addressing authority can assign addresses to the routing domain or to allow a routing domain to be reconfigured during operation Note The OSI Area Address Alias 1 and Area Address Alias 2 parameters used in previous releases to configure manual area addresses no longer exist To configure manual area addresses for OSI Site Manager Procedure You do this System responds 1 In
122. tware in the European Community This provision applies to all Software acquired for use within the European Community If Licensee uses the Software within a country in the European Community the Software Directive enacted by the Council of European Communities Directive dated 14 May 1991 will apply to the examination of the Software to facilitate interoperability Licensee agrees to notify Nortel Networks of any such intended examination of the Software and may procure support and assistance from Nortel Networks 7 Term and termination This license is effective until terminated however all of the restrictions with respect to Nortel Networks copyright in the Software and user manuals will cease being effective at the date of expiration of the Nortel Networks copyright those restrictions relating to use and disclosure of Nortel Networks confidential information shall continue in effect Licensee may terminate this license at any time The license will automatically terminate if Licensee fails to comply with any of the terms and conditions of the license Upon termination for any reason Licensee will immediately destroy or return to Nortel Networks the Software user manuals and all copies Nortel Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license 8 Export and Re export Licensee agrees not to export directly or indirectly the Software or related technical data or information witho
123. u 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 1 3 6 1 4 1 18 3 5 6 4 7 Static Route Parameters Parameter Path Default Options Function Instructions MIB Object ID This section describes the static route parameters Enable Configuration Manager gt Protocols gt OSI gt Static Route 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 308637 14 00 Rev 00 D 21 Configuring OSI Services Parameter Destination NSAP Address hex Path Configuration Manager Protocols OSI Static Route Default None Options Any valid NSAP address Function Specifies the NSAP address of the destination end system Instructions Enter the address assigned to the destination end system in hexadecimal format MIB Object ID 1 3 6 1 4 1 18 3 5 6 2 1 4 Parameter Route Type Path Configuration Manager Protocols OSI Static Route Default None Options End System Area External Domain Function Specifies the route type Instructions Select the route type for this static route MIB Object ID 1 3 6 1 4 1 18 3 5 6 2 1 6 Parameter Next Hop IS NSAP Address hex Path Configuration Manager Protocols OSI Static Route Default None Options Any valid NSAP address Function Specifies
124. ual terminal Hard Copy Technical Manuals You can print selected technical manuals and release notes free directly from the Internet Go to support baynetworks com library tpubs Find the product for which you need documentation Then locate the specific category and model or version for your hardware or software product Using Adobe Acrobat Reader you can open the manuals and release notes search for the sections you need and print them on most standard printers You can download Acrobat Reader free from the Adobe Systems Web site www adobe com You can purchase selected documentation sets CDs and technical publications through the collateral catalog The catalog is located on the World Wide Web at support baynetworks com catalog html and 1s divided into sections arranged alphabetically e The CD ROMs section lists available CDs The Guides Books section lists books on technical topics e The Technical Manuals section lists available printed documentation sets 308637 14 00 Rev 00 xvii Configuring OSI Services How to Get Help If you purchased a service contract for your Nortel Networks product from a distributor or authorized reseller contact the technical support staff for that distributor or reseller for assistance If you purchased a Nortel Networks service program contact one of the following Nortel Networks Technical Solutions Centers Technical Solutions Center Telephone Number Biller
125. ure 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 GOSIP Version 2 structure illustrated in Figure 1 5 308637 14 00 Rev 00 OSI Overview octets IDP Initial Domain Part Reserved DSP Domain Specific Part Routing Domain Identifier AFI Authority and Format Identifier Area Identifier IDI Initial Domain Identifier System Identifier DFI Domain Format Identifier NSAP Selector AAI Administrative Authority Identifier OSI0006A Figure 1 5 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
126. ut a TARP request the TARP entities check the TARP data network s caches for a mapping and send out the request only if they do not find one Because the main purpose of the Nortel Networks implementation of TARP is to forward TARP packets the router originates TARP requests for debugging purposes only and so sends out requests whether or not there is a match in the data cache Finding an NSAP If you use the f option with the Technician Interface tarp pkt command on the router you can learn the NSAP of a particular TID The router sends a Type 1 packet to all Level 1 OSI adjacencies and the T1 timer is set If T1 expires before the router receives a response it sends a Type 2 request to all Level 1 and Level 2 OSI adjacencies and the T2 timer is set If T2 expires before the router receives a response the T4 timer is started and an error recovery procedure begins When the T4 timer expires the router generates a second Type 2 request and the T2 timer starts again If T2 expires before the router receives a response the router reports back to the application that the TID could not be resolved Finding a TID To learn the TID of a particular NSAP the router sends a Type 5 packet Because it knows the destination NSAP it does not flood the request out all adjacencies It sends the Type 5 request directly to that NSAP and starts the T3 timer If the T3 timer expires before the router receives a response the router reports back to the a
127. ut first obtaining any required export licenses or other governmental approvals Without limiting the foregoing Licensee on behalf of itself and its subsidiaries and affiliates agrees that it will not without first obtaining all export licenses and approvals required by the U S Government i export re export transfer or divert any such Software or technical data or any direct product thereof to any country to which such exports or re exports are restricted or embargoed under United States export control laws and regulations or to any national or resident of such restricted or embargoed countries or ii provide the Software or related technical data or information to any military end user or for any military end use including the design development or production of any chemical nuclear or biological weapons 9 General If any provision of this Agreement is held to be invalid or unenforceable by a court of competent jurisdiction the remainder of the provisions of this Agreement shall remain in full force and effect This Agreement will be governed by the laws of the state of California Should you have any questions concerning this Agreement contact Nortel Networks 4401 Great America Parkway PO Box 58185 Santa Clara California 95054 8185 LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT UNDERSTANDS IT AND AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS LICENSEE FURTHER AGREES THAT THIS AGREEMENT IS THE ENTIRE AND EXC
128. uters residing in the same local area You must assign different area addresses to routers that reside in different areas D 8 308637 14 00 Rev 00 Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Parameter Path Default Options Function Instructions MIB Object ID Site Manager Parameters Max Learned End Systems Configuration Manager Protocols OSI Global 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 Max Learned L1 Intermediate Systems Configuration Manager gt Protocols gt OSI gt Global 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 Configuration Manager gt Protocols gt OSI gt Global 64 1 to 4000 Specifies the maximum number of L2 routers per slot that the router can learn about dynamically through the exchange of Hello
129. ystem responds 1 In the Configuration Manager window choose Protocols OSI Tarp ADJ Ignore Click on Add The TARP Ignore Adjacencies window opens The Ignore Adjacencies Configuration window opens Set the Ignore Adjacent NSAP Address parameter Click on Help or see the parameter description on page D 29 Click on OK Click on Done The TARP Ignore Adjacencies window opens You return to the Configuration Manager window To delete a TARP Ignore Adjacency setting Site Manager Procedure You do this System responds 1 In the Configuration Manager window choose Protocols OSI Tarp ADJ Ignore The TARP Ignore Adjacencies window opens Select an ignore adjacency address and then click on Delete The selected address no longer appears When you are finished click on Done You return to the Configuration Manager window 4 22 308637 14 00 Rev 00 Editing OSI and TARP Parameters To enable or disable a TARP Ignore Adjacency setting Site Manager Procedure You do this System responds 1 In the Configuration Manager window The TARP Ignore Adjacencies window choose Protocols OSI Tarp opens ADJ Ignore 2 Select an ignore adjacency NSAP The Values Selection window opens address and then click on Values 3 Set the Enable parameter Click on Help or see the parameter description on pa

Avaya Configuring OSI Services User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents