Adtran ATLAS User Manual

ATLAS Frame Relay

User Manual

Part Number 1200263L1-1

61200263L1-1.1D May 2000

901 Explorer Boulevard

P.O. Box 140000

Huntsville, AL 35814-4000

(256) 963-8000

Printed in U.S.A.

Table of Contents

ListofFigures ..........................................................................vii

ListofTables...........................................................................xi

Chapter1 IntroducingATLASFrameRelay..............................................1-1

FrameRelayOverview.................................................................. 1-1

FrameRelayFeatures ................................................................... 1-2

Specifications ..........................................................................1-2

Chapter2 TechnologyOverview ....................................................... 2-1

OSIModel ............................................................................2-1

Example1: OSIModelRelatedtoProcessofMailingaLetter.................................2-2

Example2: OSIModelRelatedtoProcessofMovingDataPacket.............................2-3

FrameRelay ...........................................................................2-3

VirtualCircuits.....................................................................2-3

PVCPhysicalConnections........................................................ 2-4

DataLinkConnectionIdentifier(DLCI)................................................ 2-5

User-to-NetworkInterface ........................................................... 2-5

LocalManagementInterface(LMI) ................................................2-6

AnnexAandAnnexD...........................................................2-6

CommittedInformationRate(CIR).................................................... 2-6

ManagingNetworkCongestion....................................................... 2-7

TBOP................................................................................. 2-8

PPP ..................................................................................2-8

LinkControlProtocol................................................................2-8

NetworkControlProtocols...........................................................2-8

Chapter3 EnablingFrameRelay .......................................................3-1

InstallingtheTemporaryLicenseKey..................................................... 3-2

ObtainingthePermanentLicenseKey ....................................................3-2

InstallingthePermanentLicenseKey ..................................................... 3-3

61200263L1-1.1 ATLAS Frame Relay User Manual iii

Table of Contents

Chapter 4 Defining Packet Endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Overview..............................................................................4-1

Passwords .............................................................................4-1

NavigatingtheTerminalMenus ..........................................................4-1

ThePacketManagerMenu ...............................................................4-2

PacketEndpnts .........................................................................4-2

Status..............................................................................4-2

EndpntName ...................................................................4-2

Prot............................................................................4-3

SigRole.........................................................................4-3

SigType........................................................................4-3

Active(FrameRelay).............................................................4-3

Active(PPP).....................................................................4-3

CurrentPort.....................................................................4-4

Performance........................................................................4-5

EndpntName ...................................................................4-5

Protocol ........................................................................4-5

LinkStats(FrameRelay)..........................................................4-5

LinkStats(TBOP)................................................................4-6

LinkStats(PPP)..................................................................4-7

SublinkStats ....................................................................4-8

Config .............................................................................4-9

EndpntName ...................................................................4-9

Protocol ........................................................................4-9

Config..........................................................................4-9

ChoosingtheSignalingRoleforBackupLinks ..................................4-11

Sublinks.......................................................................4-15

SublinksExample...............................................................4-18

Usage .........................................................................4-19

Test...............................................................................4-19

EndpntName ..................................................................4-19

Protocol .......................................................................4-19

Sublink........................................................................4-20

EndpntCount......................................................................4-21

EndpntsSort.......................................................................4-21

PacketCncts ..........................................................................4-22

From:PEP.........................................................................4-22

Sublink............................................................................4-22

To:PEP............................................................................4-22

Sublink............................................................................4-22

Protocol...........................................................................4-23

Config ............................................................................4-23

Conflict........................................................................4-23

From..........................................................................4-23

To.............................................................................4-23

CnctsSort.............................................................................4-23

FrameRelayIQ........................................................................4-23

Chapter5 ConnectingPacketEndpoints.................................................5-1

DedicatedMaps ........................................................................5-1

DialPlan ..............................................................................5-1

iv ATLAS Frame Relay User Manual 61200263L1-1.1

Table of Contents

PktEndpt .......................................................................... 5-2

Slot/Svc........................................................................5-2

Prt/PEP........................................................................5-2

Sig.............................................................................5-2

In#Accept ...................................................................... 5-2

Out#Rej........................................................................5-2

IfceConfig......................................................................5-2

PktVoice...........................................................................5-6

Slot/Svc........................................................................5-6

Prt/PEP........................................................................5-6

Sig.............................................................................5-6

In#Accept ...................................................................... 5-6

Out#Rej........................................................................5-6

IfceConfig......................................................................5-6

CallerID....................................................................... 5-7

SourceID....................................................................... 5-7

NetworkTerm...................................................................... 5-8

DIDDigitsTransferred...........................................................5-8

DIDPrefix...................................................................... 5-8

TrunkNumber.................................................................. 5-8

UserTerm .........................................................................5-8

DIDDigitsTransferred...........................................................5-8

CallerIDNumber............................................................... 5-8

SourceID....................................................................... 5-8

Chapter6 FrameRelayConfigurationExamples..........................................6-1

Example1: IPRoutingNetwork—ATLASastheCentral-SiteRouter..........................6-2

Example2: IPRoutingNetwork—ExternalRouters.........................................6-4

Example3: PrivateFrameRelayNetwork—ATLASCentral-SiteRouter.......................6-6

Example4: PublicFrameRelayNetwork—IPDataandPacketVoice..........................6-8

Example5: PrivateFrameRelayNetwork—PacketVoice...................................6-10

Example6: IPRoutingNetworkwithDialBackup.........................................6-13

Example7: PrivateframerelayNetworkwithDedicatedBackup............................6-17

Example8: IPRoutingUsingPPP.......................................................6-20

Chapter7 UsingFrameRelayIQ ....................................................... 7-1

FrameRelayIQ ........................................................................ 7-1

EnableIQStats .....................................................................7-1

PortEnables........................................................................7-1

Name..........................................................................7-1

EnablePort..................................................................... 7-2

AllSublinks .................................................................... 7-2

Sublinks........................................................................ 7-2

Config.............................................................................7-2

CurrentPIVs.................................................................... 7-2

IntervalPeriod.................................................................. 7-2

MaxDays ......................................................................7-2

MaxIntervals...................................................................7-2

ViewIQStatistics................................................................... 7-3

61200263L1-1.1 ATLAS Frame Relay User Manual v

Table of Contents

Interval/Day(Link).............................................................7-3

Sublink.........................................................................7-5

AppendixA Troubleshooting..........................................................A-1

AppendixB Glossary ................................................................. B-1

Index..............................................................................Index-1

vi ATLAS Frame Relay User Manual 61200263L1-1.1

List of Figures

Figure1-1. TypicalPoint-to-PointCircuit................................................1-1

Figure1-2. FrameRelayCircuit........................................................ 1-2

Figure2-1. ThreeVirtualCircuitsinOnePhysicalCircuit..................................2-4

Figure2-2. FrameRelayNetworkusingVirtualCircuits................................... 2-4

Figure2-3. NetworkUsingDLCIAssignments...........................................2-5

Figure2-4. NetworkCongestionandFlowControl....................................... 2-7

Figure4-1. PacketManagerMenu...................................................... 4-2

Figure4-2. StatusMenuTree .......................................................... 4-2

Figure4-3. PerformanceMenuTree .................................................... 4-5

Figure4-4. FrameRelayLinkStatsMenuTree ...........................................4-5

Figure4-5. TBOPLinkStatsMenuTree................................................. 4-6

Figure4-6. PPPLinkStatsMenuTree................................................... 4-7

Figure4-7. FrameRelaySublinkStatsMenuTree......................................... 4-8

Figure4-8. ConfigMenuTree.......................................................... 4-9

Figure4-9. Config/ConfigMenuTree(FrameRelay).....................................4-10

Figure4-10. Config/ConfigMenuTree(PPP)............................................ 4-13

Figure4-11. SublinksMenuTree....................................................... 4-15

Figure4-12. TestMenuTree...........................................................4-19

Figure4-13. EndpntCountMenuTree..................................................4-21

Figure4-14. EndpntsSortMenuTree................................................... 4-21

Figure4-15. PacketConnectsMenu.....................................................4-22

Figure4-16. CnctsSortMenu.......................................................... 4-23

Figure5-1. DedicatedMapsMenu...................................................... 5-1

Figure5-2. DialPlanMenu............................................................5-1

Figure5-3. Port/PEPOptionsintheDialPlan ...........................................5-2

Figure5-4. PacketLinkInterfaceConfiguration..........................................5-3

Figure5-5. PacketLinkInterfaceConfigurationwithFRBackupSupport.................... 5-3

Figure5-6. PacketLinkGROUPInterfaceConfiguration................................... 5-3

Figure5-7. CallRoutingTableforRoutingUsingIncomingNumber........................5-5

Figure5-8. CallRoutingTableforRoutingUsingCallPartyNumber .......................5-5

Figure5-9. CallRoutingTableforRoutingUsingDBUHandshake .........................5-5

Figure5-10. PacketSwitchedVoiceOptions ..............................................5-6

Figure5-11. InterfaceConfigurationPanel................................................5-6

Figure6-1. ATLAStoSupportPacketDataConfiguration................................. 6-1

61200263L1-1.1 ATLAS Frame Relay User Manual vii

List of Figures

Figure6-2. IPRoutingNetworkwithATLASastheCentral-SiteRouter......................6-2

Figure6-3. MenuforCreatingPacketEndpoints..........................................6-2

Figure6-4. MenuforCreatingSublinksorDLCIs.........................................6-2

Figure6-5. MenuforConnectingIPTraffictoInternalRouter...............................6-3

Figure6-6. MenuforAttachingPacketEndpointtoPhysicalInterface .......................6-3

Figure6-7. IPNetworkWithExternalRouters............................................6-4

Figure6-8. MenuforCreatingthePacketEndpoints.......................................6-4

Figure6-9. MenuforConfiguringPacketEndpoints(1)Sublinks............................6-5

Figure6-10. MenuforConfiguringPacketEndpoints(2)Sublinks............................6-5

Figure6-11. MenuforMakingthePacketConnections......................................6-5

Figure6-12. MenuforConnectingPacketEndpointstoPhysicalPort.........................6-5

Figure6-13. PrivateFrameRelayNetwork—ATLASCentral-SiteRouter......................6-6

Figure6-14. MenuforCreatingPacketEndpoints..........................................6-6

Figure6-15. MenuforCreatingSublinks..................................................6-6

Figure6-16. MenuforConnectingPacketEndpoints........................................6-7

Figure6-17. MenuforConnectingPacketEndpointtoPhysicalInterface......................6-7

Figure6-18. PublicFrameRelayNetwork.................................................6-8

Figure6-19. MenuforCreatingPacketEndpoint...........................................6-8

Figure6-20. MenuforConfiguringSublinks...............................................6-9

Figure6-21. MenuforConnectingPacketData.............................................6-9

Figure6-22. MenuforConfiguringDialPlan..............................................6-9

Figure6-23. MenuforConnectingPacketEndpoints........................................6-9

Figure6-24. PrivateFrameRelayNetworkUsingCompressedVoice ........................6-10

Figure6-25. MenuforCreatingPacketEndpoints.........................................6-10

Figure6-26. MenuforConfiguringSublinks..............................................6-11

Figure6-27. MenuforConnectingtheTBOPEndpoints....................................6-11

Figure6-28. MenuforConnectingPacketEndpointstoPhysicalLinks.......................6-11

Figure6-29. ConnectingPBXDS0toFrameRelayEndpoint................................6-12

Figure6-30. ConnectingFREndpointtoFRPrivateNetwork...............................6-12

Figure6-31. IPRoutingNetworkwithDialBackup........................................6-13

Figure6-32. MenuforCreatingthePacketEndpoints......................................6-13

Figure6-33. MenuforConfiguringPacketEndpoint1(Server)Sublinks......................6-14

Figure 6-34. Menu for Configuring Packet Endpoint 2

(XYZNetwork)Sublinks....................................................6-14

Figure 6-35. Menu for Configuring Packet Endpoint 3

(ChicagoBackup)Sublink ..................................................6-14

Figure 6-36. Menu for Configuring Packet Endpoint 4

(NewYorkBackup)Sublink.................................................6-14

Figure 6-37. Menu for Configuring Packet Endpoint 5

(BostonBackup)Sublink....................................................6-14

Figure6-38. MenuforConfiguringBackupSublink1......................................6-15

Figure6-39. MenuforMakingthePacketConnections.....................................6-15

Figure6-40. MenuforConnectingPacketEndpointstoPhysicalPort........................6-15

Figure6-41. MenuforAddingBackupPacketEndpointstotheDialPlan.....................6-16

viii ATLAS Frame Relay User Manual 61200263L1-1.1

List of Figures

Figure 6-42. Menu for Configuringthe Switched Packet Endpoint

InterfaceConfiguration.................................................... 6-16

Figure6-43. MenuforConfiguringthePRIConnectionstothePSTN........................6-16

Figure6-44. PrivateFrameRelayNetworkwithDedicatedBackup.........................6-17

Figure6-45. MenuforCreatingPacketEndpoints ........................................ 6-17

Figure6-46. MenuforConfiguringSublinks.............................................6-18

Figure6-47. MenuforConfiguringSublinks.............................................6-18

Figure6-48. MenuforConfiguringBackupVoiceSublink .................................6-18

Figure6-49. MenuforConfiguringBackupSignalingSublink.............................. 6-18

Figure6-50. MenuforMakingthePacketConnections.................................... 6-19

Figure6-51. MenuforConnectingPacketEndpointstoPhysicalPorts....................... 6-19

Figure6-52. MenuforConnectingPacketEndpointstoPhysicalPorts....................... 6-19

Figure6-53. PrivateFrameRelayNetworkwithDedicatedBackup.........................6-20

Figure6-54. MenuforCreatingPacketEndpoints ........................................ 6-20

Figure6-55. MenuforConfiguringSublinks.............................................6-20

Figure6-56. MenuforConfiguringSublinks.............................................6-21

Figure6-57. MenuforConfiguringBackupVoiceSublink .................................6-21

Figure6-58. MenuforMakingthePacketConnections.................................... 6-21

Figure6-59. MenuforConnectingPacketEndpointstoPhysicalPorts....................... 6-21

Figure7-1. FrameRelayIQMenus .....................................................7-1

Figure7-2. ViewIQStatisticsMenuTree................................................ 7-3

61200263L1-1.1 ATLAS Frame Relay User Manual ix

List of Figures

x ATLAS Frame Relay User Manual 61200263L1-1.1

List of Tables

Table1-1. FrameRelaySpecifications....................................................1-3

Table2-1. Seven-LayerOSIModel....................................................... 2-1

Table2-2. LMI(GroupofFour)DLCIAssignments........................................2-6

Table2-3. AnnexAandAnnexDDLCIAssignments...................................... 2-6

Table4-1. SuggestedFragmentationValuesBasedonthePVCCIR.........................4-16

61200263L1-1.1 ATLAS Frame Relay User Manual xi

List of Tables

xii ATLAS Frame Relay User Manual 61200263L1-1.1

Chapter 1

Introducing ATLAS Frame Relay

FRAME RELAY OVERVIEW

Frame relay is a packet-switched service that allows efficient transfer of bursty trafficinawidearea network (WAN) environment (see also Frame Re- lay on page 2-3). It offers lower-cost data transfer, when compared to typical point-to-point applications, by using virtual connections within the frame relay network and by combining those connections into a single physical connection at each location. Frame relay providers use a frame relay switch to route the data on each virtual circuit to the appropriate destination.

Figure 1-1 and Figure 1-2 illustrate a conversion from a typical point-topoint application to a frame relay application.

Router

PBX

Long Haul DDS

PBX

DDS

Figure 1-1. Typical Point-to-Point Circuit

Router

PBX

Router

PBX

61200263L1-1.1 ATLAS Frame Relay User Manual 1-1

Chapter 1. Introducing ATLAS FrameRelay

Router

PBX

Router

PBX

Router

PBX

ATLAS800

Router

PLUS

Fr ame

Relay

DDS

Figure 1-2. Frame Relay Circuit

The ATLAS Frame Relay/Router option allows the ATLAS series of Integrated Access Devices to act as a voice/data frame relay access device (FRAD), a private network frame relay switch, a frame relay concentrator, and an internal IP router. In addition, the ATLAS Frame Relay/Router option manages currently available bandwidth and switching applications.

FRAME RELAY FEATURES

The Frame Relay/Router option provides the following functions:

• Routes Internet Protocol(IP)trafficbetweenapublic or private framerelay network and the integral 10BaseT Ethernet port.

• Concentrates IP traffic from a public or private frame relay network to one or more serial ports (V.35). The protocol passed over the serial port is frame relay.

• Passes Systems Network Architecture (SNA), Bisync, and other legacy protocols between a public or private frame relay network and an external DTE running frame relay to ATLAS. (May require the HDLC Module—P/N 1200222L1.)

• Performs voice compression/decompression (G.723.1)and interfaces to either a Private Branch Exchange (PBX) or the Public Switched Telephone Network (PSTN). (This feature requires an additional option module, the VCOM Module—P/N 1200221L1.)

SPECIFICATIONS

Table 1-1 lists the specifications for the frame relay features.

1-2 ATLAS Frame Relay User Manual 61200263L1-1.1

Option Feature Specification

Frame Relay

Chapter 1. Introducing ATLAS Frame Relay

Table 1-1. Frame Relay Specifications

Packet throughput 7000 pkts/sec (minimum)

IP Routing

Management signaling interfaces

UNI (user and network) NNI

Management signaling types ANSI T1.617-D (Annex D)

ITU-T Q.933-A (Annex A) LMI (Group of four)

Auto Encapsulation RFC 1490 for IP and LLC2 PVC support 1000 PVCs Congestion control FECN / BECN

Discard eligible (DE) Quality of service (QOS) Prioritization on a per-PVC basis Testing (ADTRAN proprietary) PVC loopback

Round trip delay measurement SNMP support RFC 1315

Route discovery RIP V1

Voice Compression

RIP V2

ICMP

ARP

IARP

UDP Relay

OSPF Virtual connections supported 100 PVCs SNMP support MIB II

Algorithm G.723.1 or Netcoder (proprietary) Number of channels supported Up to 64 compression channels PCM coding MU-Law, A-Law (future) Fax support 9600 bps DTMF generation and

TIA 464A detection

61200263L1-1.1 ATLAS Frame RelayUser Manual 1-3

Chapter 1. Introducing ATLAS FrameRelay

1-4 ATLAS Frame Relay User Manual 61200263L1-1.1

Chapter 2

OSI MODEL

Technology Overview

This chapter discusses the OSI Model, Frame Relay Protocol, and Transparent Bit Oriented Protocol (TBOP).

The Open Systems Interconnection (OSI) model is an internationally accepted standard forcommunication between multiple vendors’ communication equipment. It relies on a seven-layer model to allow communication between communication equipment. Table 2-1 describes these layers.

Table 2-1. Seven-Layer OSI Model

Layer Title Description

Layer 7 Application Contains functions for end-user services. These

include FTP, remote file access, andnetwork management. This is not the application, but the interface.

Layer 6 Presentation Provides transparent communication by creating

code and syntax compatibility between systems.

Layer 5 Session Takes care of the communication facility

providedby the transport layer (layer 4). Allows sessions to be established, recovered, and terminated.

Layer 4 Transport Provides some error correction and end-to-end

flow control. Also decides best routefor the information being transmitted.

Layer 3 Network Determines the method for transmitting data and

also deals with routing the data between networks. Moves data based on addressing.

Layer 2 Data Link Deals with procedures and protocols for

controlling the transmission line. Provides some error detection and correction.

Layer 1 Physical Deals with the electrical, mechanical, and

functional control of sending data over the transmission lines.

61200263L1-1.1 ATLAS Frame Relay User Manual 2-1

Chapter 2. Technology Overview

By definingstandardinterfacesbetweeneachof the seven layers, an individual layer only has to know about the interface to the layer above, to the layer below, and to the same layer on the other end of the network. This interface definition simplifies the process of networking.

TheRouterandFrameRelaysoftwareinATLASinvolveslayer3andlayer2 data processing. The OSI model is not limited to digital data networks, but canbeextendedtosuchnetworksastheU.S.PostalService.Theexamples belowshouldclarifytherolesofthefirstthreelayersandhowtheyinterface with each other. Example 1 relates the OSI model to the process of mailing a letter.

Example 1: OSI Model Related to Process of Mailing a Letter

Upper Layers Letters and Advertisements Layer 3 Network Envelopes and Boxes Layer 2 Data Link Mailbags Layer 1 Physical Planes and Trucks

Send Process Receive Process

Person A writes a letter. Upper Layers Person B reads the letter. Person A placesthe letter in

an envelope, addresses it to person B, and puts envelope in mailbox.

The envelope is collected from mailbox and placed into a mailbag destined for post office B.

A truck takes the mailbag and drives to post office B.

Since the postal service specifies how mail is t ransferred betweenlayers,the person addressing the letter only needs to know the address of the person receiving the letter to pass the letter down to the next layer. The letter writer has no knowledge of the details of mailbags and moving letters between post offices, but knows to place the letter in the mailbox so that the post office delivers the letter to the reader. The lower layers have no knowledge of the letter, but take responsibility for getting it to the appropriate location.

Layer 3

Layer 2

Layer 1

Roads and

Interstates

Person B opens envelope and removes the letter.

The mailbag is opened and the en velope is placed in person B’s post office box.

The truck delivers the mailbag to post office B.

2-2 ATLAS Frame Relay User Manual 61200263L1-1.1

Chapter 2. Technology Overview

Example 2: OSI Model Related to Process of Moving Data

Packet

A more typical example of the OSI model involves moving a data packet across an IP network.

Upper Layers E-mail message

Layer 3 Network - IP/IPX Layer 2 Data Link - FrameRelay/PPP Layer 1 Physical - T1/DDS

Send Process Receive Process

Creates a data packet. Upper Layers Data packet is processed.

FRAME RELAY

Wraps the data in an IP packet, specifies the IP address of the far end computer,anddetermines the appropriate route.

TheIPpacketisplacedinside aframerelaypacketwiththe appropriate DLCI and placed on the correct DS-1.

The frame relaypacket is placed in the appropriate DS0s.

Frame relay is one of several layer 2 (data link)protocolsthattransportdata across a serial data network. These protocols also include Point-to-Point Protocol (PPP) and High-level Data Link Connection Protocol (HDLC). Frame relay networks are composed of virtual circuits that connect customer locations. To reduce a customer’s overall monthly connection, multiple virtual circuits could be delivered to the customer’s location over a single physical connection.

Layer 3

Layer 2

Layer 1

LEC and IXC

The IP wrapper is removed and the data is then passed to the upper layers.

The frame packet is unwrapped and the IP packet is sent to layer 3.

The frame relaypacket is removed and passed to layer 2.

Virtual Circuits

Virtual circuits can be either permanent (PVC) or switched (SVC). PVC bandwidths are determined when the circuit is ordered from the frame relay provider. PVCs are always active, even when no data is being transmitted. SVC bandwidths are created and used only when needed and allow for negotiation of the bandwidth parameters during the circuit setup. SVCs are currently unavailable from most frame relay providers, and ATLAS only supports PVCs.

61200263L1-1.1 ATLAS Frame RelayUser Manual 2-3

Chapter 2. Technology Overview

PVC Physical Connections

Figure 2-1 illustrates three PVCs being delivered over one physical circuit. The frame relay switch within the frame relay provider’s circuit makes a physical connection for each PVC. Each of the PVCs could connect to a different physical location at the other endofthe circuit. Figure 2-2 illustrates a frame relay network topology.

PVC Z

32 kbps

PVC X

768 kbps

PVC Y

128 kbps

FrameRelay/Router

Figure 2-1. Three Virtual Circuits in One Physical Circuit

FrameRelay

Network Virtual circuit X Virtual circuitY Virtual circuit Z

FrameRelay/Router

Figure 2-2. Frame Relay Network using Virtual Circuits

2-4 ATLAS Frame Relay User Manual 61200263L1-1.1

Data Link Connection Identifier (DLCI)

An address called a Data Link Connection Identifier (DLCI) uniquely identifies each of the virtual circuits in the frame relay network. A DLCI does not address the equipment at the far end of the virtualcircuit, but addresses the next piece of frame relay equipment within the network. The next piece of frame relayequipment nowbecomesresponsiblefortransportingallframes from the incoming port to the appropriate outgoing port.

Figure 2-3 illustrates a network using DLCI assignments. In this example, the router at site A sends a frame packet to site B, by placing the data on DLCI 100. Knowingthat all packets coming in DLCI 100 must go out DLCI 225, Frame Relay Switch A places the packets on DLCI 225 and sends them out to Frame Relay Switch B. Frame Relay Switch B then takes the frame packets from DLCI 225 and places them on DLCI 35 for delivery to the site B router. From this example, you can see that each piece of frame relay equipment only knows about the DLCIs local to it. Hence, you will hear “DLCIs only have local significance.”

Chapter 2. Technology Overview

FrameRelay/Router

User-to-Network Interface

The interface between the customer and the frame relay switch is called the User-to-Network Interface (UNI). Three different types of signaling can transmit across this interface: LMI (Group of Four), Annex A (ITU-T Q.933-A), and Annex D (ANSI T1.617-D). Unfortunately, due to signaling differences among the three types, they are incompatible with one another, and DLCI assignments vary among the three types. Tables 2-2 and 2-3 give the assignments for the three types.

DLCI 100

DLCI 200

FrameRelay/Router

FrameRelay

Switch A

DLCI 225

DLCI 650

FrameRelay

Switch B

DLCI 35

DLCI 501

FrameRelay/Router

Figure 2-3. Network Using DLCI Assignments

61200263L1-1.1 ATLAS Frame RelayUser Manual 2-5

Chapter 2. Technology Overview

Local Management Interface (LMI)

LMI is the standard published by the Frame Relay Consortium in 1990 to create a defined interface on the UNI. The Consortium, composed of Cisco Systems,DEC,Nortel,andStrataCom, is commonlyreferredtoas the Group of Four.

Annex A and Annex D

The International Telecommunications Union Telecommunication StandardizationSector(ITU-T) adoptedAnnexAa s the interface standardforinternational frame relay applications. The American National Standards Institute(ANSI) modified theFrameRelayConsortium’sinterface specification and ratified it as Annex D—an interface standard for the United States.

Table 2-2. LMI (Group of Four) DLCI Assignments

DLCI Use

0 Call control signaling channel. 1-15 Reserved for future use. 16-1007 Available for customer data. 1008-1022 Reserved for future use. 1023 LMI channel.

Committed Information Rate (CIR)

Customers can order a circuit with a guaranteed amount of bandwidth for their virtual connections. This amount is called the Committed Information Rate (CIR), and it defines how muchbandwidth the customer is guaranteed during normal network operation. Any data transmitted above this purchased rate is discard eligible (DE) by the network. That is, this data can be discarded in the event of network congestion.

TheCIRcanbethoughtofasthesizeofthevirtualconnectionfromendto end. The CIR canbe purchased in different increments up to the wire speed of the slowest link. For example, if the circuit in Figure 2-3 had T1 access fromsiteAtotheframerelaynetworkanda56-kbpsDDSlinefromsiteBto the frame relay network, the largest CIR available for purchase would be

Table 2-3. Annex A and Annex D DLCI Assignments DLCI Use

0 Carries frame relay signaling (LMI channel). 1-15 Reserved for future use. 16-991 Available for customer data. 992-1007 Management DLCIs for layer 2. 1008-1022 Reserved for future use. 1023 Higher layer protocol communication channel.

2-6 ATLAS Frame Relay User Manual 61200263L1-1.1

56k. Although data could burst from site A to the frame relay network at the full T1 speed of 1.536 Mbps, it would queue up in the frame relay network until it could be sent across the 56-kbps DDS circuit. This queue could cause network congestion.

Managing Network Congestion

If congestion becomes a problem within the network due to excessive data being delivered fromoneofthesites, theframerelayswitchattemptstoflow control the data by sending bits that notify networkdevices that transmissions in the opposite direction are congested. These bits are called Backward Explicit Congestion Notification (BECN) and Forward Explicit Congestion Notification (FECN).

Forexample,ifa frame relayswitchbeginsto experience congestion, itsends the upstreamsiteaFECNand the downstream site aBECN.Thisnotification indicates to the frame relay equipment that the frame relay switch is experiencingdifficultyandthat the framerelay device shouldbegin to flowcontrol its traffic.

Figure 2-4 shows an example of FECN and BECN messagesbeing transmitted to the frame relayequipment when congestion occurs. Both ends are notified that congestion isoccurringwithintheswitch.Youmightwonderwhy the receiving end should receive notification of congestion and then flow control its data when the other end is causing the problem by sending large amountsofdata.Flowcontrol is used by thereceivingendsothatupper layer acknowledgments from the destination slow down, thereby reducing the amount of data being transmitted from the source.

Chapter 2. Technology Overview

Data Source

FrameRelay/ Router

Data Destination

FrameRelay/Router

Switch Congestion

BECN

Frame

Switch

Frame Switch

FrameRelay/Router

Figure 2-4. Network Congestion and Flow Control

This overview is not intended to beall inclusive of the operation of a frame relay network. It is intended to help simplify the frame relay configuration within ATLAS.

61200263L1-1.1 ATLAS Frame RelayUser Manual 2-7

Chapter 2. Technology Overview

TBOP

Transparent Bit Oriented Protocol (TBOP) is an ADTRAN-proprietary protocol that is used to transmit HDLC-formatted traffic across the frame relay network. TBOP allows the transportation of protocols “unknown” to ATLAS to be encapsulated in frame relay and sent to a remote location via frame relay. This protocol can be useful in transporting other vendors’ proprietary protocols across the WAN.

ATLAS accepts HDLC-formatted data on one of the V.35 or T1 ports and forwards that data across a frame relay network to another ATLAS or an ADTRAN frame relay device (for instance, if ATLAS is communicating with an IQ product).

PPP

The Point-to-Point Protocol, PPP, is the Internet standard for the transmission of IPpacketsoverseriallines. PPP is not confined to serial links though; it runs on async or sync lines. PPP is also a multi-protocol transport mechanism. This means that PPP transports several differenttypes of other protocols: IP, IPX, Appletalk, Bridged Ethernet, etc. All of these protocols can be transported at the same time. There are various compression protocols to increase the transmission rate of the link. The ATLAS only supports the IP protocol over dedicated links. As per RFC 1661, PPP comprises three main components:

1. A method for encapsulating multi-protocol datagrams.

2. A Link ControlProtocol(LCP)forestablishing,configuring, and testing the data-link connection.

3. A family of Network Control Protocols (NCPs) for establishing and configuring different network-layerprotocols (such as IP).

Link Control Protocol

To be portable to a wide variety of environments, PPP provides an LCP. The LCP is used to automatically agree upon the encapsulation format o ptions, handle varying limits on sizes of packets, detect a looped-back link and other common misconfiguration errors, and terminate the link. Other optional facilities provided are authentication of the identity of its peer on the link, and determination of when a link is functioning properly and when it is failing.

Network Control Protocols

Point-to-Point links tend to exacerbate many problems with the current family of network protocols. For instance, assignment and management of IP addresses, which is a problem even in LAN environments, is especially difficult over circuit-switched point-to-point links (such as dial-up modem servers).Theseproblems are handledbyafamily ofNCPs,andeach manage the specific needs required by their respective network-layer protocols.

2-8 ATLAS Frame Relay User Manual 61200263L1-1.1

Chapter 3

Enabling Frame Relay

The Frame Relay upgrade for the ATLAS 800

• ATLAS Software Activation Request Fax Form

• ATLAS Frame Relay User Manual

• Alphanumeric temporary license key The temporary license key enables the Frame Relay software for 30 continu-

ous days of operation. Within this 30-day period, you must fax the registration sheet to ADTRAN with the upgraded unit’s serial number. A unique, permanent software key for the upgradedATLAS is then faxed back to you.

If a permanent license key is not installed within 30 days, the Frame Relay portion of ATLAS will cease operation.

If a temporary license key expires before the permanent license key is installed, the system willreboot and all frame relay configuration will be lost.

PLUS

includes the following:

61200263L1-1.1 ATLAS Frame Relay User Manual 3-1

Chapter 3. Enabling Frame Relay

INSTALLING THE TEMPORARY LICENSE KEY

Instructions for Installing the Temporary License Key

Step Action

1 Select S 2 Select L 3 Select F

Under L

license for 30 days. Enter the serial number on the registration sheet into the S

UMBER

YSTEMCONFIG

ICENSES

RAMERELAY

ICENSECODE

from S

field.

from the ATLAS main menu.

YSTEMCONFIG

, enter F

RAMERELAY

After installing the temporary license key, you must reboot the system to enable Frame Relay. ATLAS will automatically prompt for a reboot when a Frame Relay license key is installed.

OBTAINING THE PERMANENT LICENSE KEY

To obtain a permanent license key, complete the Fax Form and fax it to ADTRAN at (256) 963-8030.

to enable thetemporary

ERIAL

Instructions for Completing the Fax Form

Step Action

Telnet from S

S F

Revision

Find the product number located on the outside of the unit, and

enter it into the field

Optional:

information to ADTRAN about how you are using the

ATLAS 800

a. A Telnet utility is provided on the ADTRAN Utilities diskettes that come with

the ATLAS 800

to your ATLAS unit and locate the following information

YSTEMINFO ERIALNUMBER IRMWAREREVISION

: Enter into the field

System Serial Number

ATLAS Chassis Software

ATLAS Chassis Part Number.

Fill in

PLUS

unit. See the

Application Used (Optional)

ATLAS User Manual

. This field provides

for instructions.

3-2 ATLAS Frame Relay User Manual 61200263L1-1.1

INSTALLING THE PERMANENT LICENSE KEY

Instructions for Installing the Permanent License Key

Step Action

Chapter 3. Enabling Frame Relay

1 Select S 2 Select L 3 Select F

Enter the license key faxed from ADTRAN into the L

field. Enter the serial number faxed from ADTRAN into the S

Continuously press the left arrow key until you see a message

asking to confirm the change. Enter Y. End the Telnet session and reconnect to the unit. The S

under S

YSTEMCONFIG

ICENSES

RAMERELAY

UMBER

field.

YSTEMCONFIG/LICENSES

from S

from the ATLAS main menu.

YSTEMCONFIG

now reads P

ERMANENT

If the frame relay featurewas not previously enabled, the system will automatically reboot to enable the new feature.

ICENSECODE

ERIAL

TATUS

field

If a temporary key expires before the permanent key is installed, the system will automatically reboot, and all frame relay configuration will be lost.

61200263L1-1.1 ATLAS Frame RelayUser Manual 3-3

Chapter 3. Enabling Frame Relay

3-4 ATLAS Frame Relay User Manual 61200263L1-1.1

Chapter 4

OVERVIEW

Defining Packet Endpoints

A packet endpoint is a virtual port within ATLAS into which a specified physical port (a T1 or an Nx56/64) terminates its data for furth er routing by the system. All packet services, including frame relay or PPP, must have defined packet endpoints. The P used to define packet endpoints.

Your frame relay provider furnishes specific information on defining the packet endpoint. This information includes signaling type (Annex A, Annex D, or LMI) and definitions for all active PVCs. The P submenu map connects protocols from packet endpointto packet endpoint.

For PPP, the only information needed is IP address and user name/password.

In addition to defining packet endpoints, you must also configure the physical port before it can run frame relay (see Chapter 5).

For a detailedlook at configuring frame relay connections, refer to Chapter 6, Frame R elay ConfigurationExamples.

ACKETMANAGER

menu contains submenus

ACKETCNCTS

PASSWORDS

You must have the appropriate password leveltoedit items using the terminal menu. Security level 1 users can view and edit every available field. Security level 5 users can view any field, but they cannot edit. (See the section

Access Passwords in the ATLAS 800 on working with passwords.)

PLUS

UserManualfordetailed information

NAVIGATING THE TERMINAL MENUS

ATLAS uses hierarchical menus to access all of its features. All menus display in the terminal window. The top-most menu level (in this case, the

ACKETMANAGER NCTSSORT

fer to the ATLAS 800 navigate through the terminal menu.

61200263L1-1.1 ATLAS Frame Relay User Manual 4-1

) leads to submenus (P

RAMERELAY

,andF

PLUS

User Manual for detailed instructions on how to

IQ) which are grouped by functionality.Re-

ACKETENDPNTS

ACKETCNCTS

, P

Chapter 4. Defining Packet Endpoints

THE PACKET MANAGER MENU

ACKETMANAGER

The P layer 2 connections, including frame relay endpoints. These submenus, discussed in this chapter, include P

ORT

.TheF

discussed separately in Chapter 6.

RAMERELAY

submenus (see Figure 4-1) define and configure all

ACKETENDPNTS

ACKETCNCTS

, P

,andC

NCTS

IQ sub menu provides frame relay statistics and is

Figure 4-1. Packet Manager Menu

ACKETENDPNTS

STATUS

Packet Endpnts Performance Sig Role Network

Packet Manager Packet Cncts Config Both

Cncts Sort Test Sig Type AnnexA Frame Relay IQ Endpnt Count Active AnnexD

ACKETENDPNTS

The P Submenus include S

NDPNTSSORT

and E

TATUS

submenus display the status of each packet endpoint including the

packet endpoint name (E ing role (S

TIVE

IGROLE

), and the connections (C

menu defines, monitors, and tests a packet endpoint.

TATUS

ERFORMANCE

, P

NDPNTNAME

), the signaling type (S

URRENTPORT

), the protocol type (P

IGTYPE

each of these fields. Figure 4-2 shows the S

Endpnt Name

Status Prot User

Endpnts Sort Current Port LMI

ONFIG

, C

). The following sections discuss

TATUS

EST

, T

NDPNTCOUNT

, E

ROT

), the signal-

), the signaling activity (A

menu tree.

Figure 4-2. Status Menu Tree

NDPNTNAME

4-2 ATLAS Frame Relay User Manual 61200263L1-1.1

Read Security: 5 Displays the packet endpoint name as defined in the P

ONFIGMENU

(also see Config on page 4-9).

ACKETENDPNTS

+ 76 hidden pages