network protocols handbook.pdf

More documents

Recommendations

Info

158Protocols GuideWAN - ATM ProtocolsProtocol NameLANE NNI: ATM LAN EmulationNNIProtocol DescriptionThe ATM LAN Emulation (LANE) enables the implementationof emulated LANs over an ATM network. An emulated LAN providescommunication of user data frames among all its users,similar to a physical LAN. One or more emulated LANs couldrun on the same ATM network. However, each of the emulatedLANs is logically independent of the others. Communicationbetween emulated LANs requires some type of interconnectiondevice (bridge, router, etc.), even though direct ATM connectionsbetween emulated LANs are explicitly allowed in some circumstances.The LAN Emulation LUNI defines the protocols andinteractions between LAN Emulation Clients (LE Clients) andthe LAN Emulation Service. Each LE Client connects across theLUNI to a single LES and BUS, may connect to a single LECS,and may have connections to multiple SMSs.The LAN Emulation NNI (LNNI) defines the behavior of theseLANE service components as seen by each other, the proceduresnecessary to provide a distributed and reliable LAN EmulationService. A single ELAN may be served by multiple LECSs,LESs, BUSs and SMSs. Each LES, BUS, and SMS serves asingle ELAN, while an LECS may serve multiple ELANs. LANEservice components interconnect with multiple VCCs for Configuration,Status, Database Synchronization, Control and Dataforwarding. The LNNI specification provides multivendor interoperabilityamong the components serving an ELAN so thatconsumers may mix and match the LANE Service implementationsof different vendors.LANE service consists of four major components:• LAN emulation client (LEC) - located in ATM end systems,implements the LUNI interface, serves as a proxyfor LAN systems to perform data forwarding and addressresolution, provides a MAC level emulated Ethernet/IEEE802.3 or IEEE 802.5 service interface to higherlevel software.• LAN emulation server (LES) - supports the address resolutionprotocol (LE-ARP), and is used to determine theATM address of the target LEC responsible for a certaindestination MAC address. An LE Client is connected toonly one LE Server. An LE Client may register LAN Destinationsit represents and/or multicast MAC addressesit wishes to receive with its LE Server. An LE Client willalso query its LE Server to resolve a MAC address orroute descriptor of an ATM address.• Broadcast/Unknown Server (BUS) - handles all multicasttraffic forwarding to all attached LECs. An LE Clientsees a single Broadcast and Unknown Server.• Selective Multicast Server (SMS) - may be used tooffload much of the multicast processing from the BUSs,which also have to forward broadcast frames and framesfor unresolved LAN destinations, to efficiently forwaqrdmulticast frames.The multiple LANE Service entities serving an ELAN need to cooperateand communicate in order to provide a distributed andreliable LAN Emulation Service. The communications requiredfor LNNI may be partitioned as follows:a) Control Plane• Configuration and Status Communications - LESs andSMSs obtain configuration information from an LECSover Configuration Direct VCCs. LECSs obtain the statusof LESs and SMSs over the same connection.• LANE Control Communications - Each LES is responsiblefor distributing LE_ARP requests for unregistereddestinations from local LE Clients to local LE Clientsand to other LESs. LESs must also forward LE_ARP responsesback to the originator. Additionally, LESs mustbe able to forward LE_FLUSH responses and LE_TO-POLOGY requests to the correct destination(s).b) SynchronizationPlane• LECS Synchronization - A particular LECS may not directlyreceive status from all service components. Thus,LECSs must exchange LES and SMS status informationamong themselves. In order to distribute this statusinformation, all LECSs participating in an ELAN mustmaintains an LECS Synchronization VCC to all otherLECSs in the network.• LES-SMS Database Synchronization – LESs and SMSsuse SCSP to synchronize their databases.c) Data Plane• BUS Data Communications - Each BUS is assumed tobe logically paired with an LES, and the BUS is assumedto have access to the registration database maintainedby the LES, which includes the ATM address of all BUSs.No protocol is defined between a paired LES and BUS.• SMS Data Communications – Every SMS (and LES)obtains a complete copy of the registration database forthe entire ELAN via SCSP, so every SMS knows of everyother SMS and BUS. When an LE Client LE_ARPsfor a multicast address, the LES should assign the clientto an SMS as a sender if an SMS is available forthat destination, otherwise a BUS’s ATM address is returnedin the LE_ARP response. An ELAN, and henceall the ELAN’s SMSs, may operate in either distributedor stand-alone mode, as determined by the network administrator.
159Protocols GuideWAN - ATM ProtocolsProtocol StructureLANE Data Frames:The LNNI Control frame format is shown below:LANEControlFrame0 LLC = X”AAAA03” OUI4 OUI Frame Type8 ELAN-ID12 REQUESTER-LECID FLAGS16 SOURCE-LAN-DESTINATION24 TARGET-LAN-DESTINATION32 SOURCE-ATM-ADDRESS52 LAN-TypeMAX-Frame-SizeNumber-TLVS56 TARGET-ATM-ADDRESS76 ELAN-NAME108 TLVs BEGINELAN-Name-SizeRelated protocolsATM, SONET, AAL0-AAL5, LAN Emulation (LANE), CES, UNI,NNI and Q.2931.Sponsor SourceThe ATM protocols are based on standards developed by theITU.http://www.atmforum.com/standards/approved.htmlATM Forum approved specificationsReferencehttp://www.atmforum.com/standards/approved.htmlATM Forum approved specificationshttp://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/atm.htmATM Overview• LLC - Logical Link Control: The Control CoordinateVCCs are all LLC encapsulated.• OUI - Organizationally Unique Identifier = X”00A03E”which indicates ATM Forum.• FRAME-TYPE = X”000F”• ELAN-ID - Emulated LAN ID• OP-CODE (2 Bytes) - Control frame Operation type.Some defined OP-Code are:OP-CODE ValueX”000b”X”000C”X”000d”X”000d”X”000e”X”000e”OP-CODE FunctionLNNI_CONFIGURE_TRIGGERLNNI_LECS_SYNC_REQUESTLNNI_KEEP_ALIVE_REQUESTLNNI_KEEP_ALIVE_RESPONSELNNI_VALIDATE_REQUESTLNNI_VALIDATE_RESPONSE• Status - (2 Bytes) Control frame Operation status.• TLV - Type/ Length / Value Encoded Parameter, Examplesof LNNI TLVs are:Item Type LEN DescriptionServerId 00-A0-3E-14 2ServerGroupId 00-A0-3E-15 2SynchronizationPeerServerSmsModeOf-Operation00-A0-3E-16 2000-A0-3E-19 1Unique identifier for aserver within an ELANUniquely correlates to anELAN-ID. Required forSCSP.Multiplexed ATM Addressof ES or SMS to synchronizeDB using SCSP.Indicates SMS operationalmode.0 = STAND_ALONE1 = DISTRIBUTED
Page 1 and 2:
www.dbeBooks.com - An Ebook Library
Page 3 and 4:
ITable of ContentsTable of Contents
Page 6 and 7:
IVTable of ContentsCR-LDP: Constrai
Page 8 and 9:
VITable of ContentsCOPS: Common Ope
Page 10 and 11:
VIIITable of ContentsGARP: Generic
Page 12 and 13:
XTable of ContentsIGRP: Interior Ga
Page 14 and 15:
XIIFigureFigureFigure 1-1: Communic
Page 16 and 17:
XIVPerfacePrefaceWe are living in t
Page 18 and 19:
2Network Communication Architecture
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
10Network Communication Architectur
Page 28 and 29:
12Protocols GuideTCP/IP Protocolspo
Page 30 and 31:
14Protocols GuideTCP/IP - Applicati
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
52Protocols GuideTCP/IP - Session L
Page 70 and 71:
54Protocols GuideTCP/IP - Transport
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
64Protocols GuideTCP/IP - Network L
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
98Protocols GuideTCP/IP - Data Link
Page 116 and 117:
100Protocols GuideTCP/IP - Data Lin
Page 118 and 119:
102Protocols GuideSecurity and VPNP
Page 120 and 121:
104Protocols GuideSecurity and VPN
Page 122 and 123:
106Protocols GuideSecurity and VPN
Page 124 and 125: 108Protocols GuideSecurity and VPN
Page 136 and 137: 120Protocols GuideVoice Over IP(VOI
Page 166 and 167: 150Protocols GuideWANOtherxDSL: Dig
Page 168 and 169: 152Protocols GuideWAN - ATM Protoco
Page 186 and 187: 170Protocols GuideWAN - Broadband A
Page 194 and 195: 178Protocols GuideWAN - PPP Protoco
Page 204 and 205: 188Protocols GuideWAN - Other WAN P
Page 212 and 213: 196Protocols GuideLAN - Ethernet Pr
Page 220 and 221: 204Protocols GuideLAN - Virtual LAN
Page 222 and 223: 206Protocols GuideLAN - Virtual LAN
Page 224 and 225:
208Protocols GuideLAN - Virtual LAN
Page 226 and 227:
210Protocols GuideLAN - Wilress LAN
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
216Protocols GuideLAN - Other Proto
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
222Protocols GuideMAN ProtocolsProt
Page 240 and 241:
224Protocols GuideMAN Protocols(0).
Page 242 and 243:
226Protocols GuideStorage Area Netw
Page 244 and 245:
228Protocols GuideSAN ProtocolsProt
Page 246 and 247:
230Protocols GuideSAN ProtocolsThe
Page 248 and 249:
232Protocols GuideSAN Protocols•
Page 250 and 251:
234Protocols GuideSAN ProtocolsSpon
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
240Protocols GuideISO Protocols in
Page 258 and 259:
242Protocols GuideISO Protocols - A
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
262Protocols GuideISO Protocols - N
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
268Protocols GuideCisco ProtocolsPr
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
278Protocols GuideCisco Protocolsti
Page 296 and 297:
280Protocols GuideNovell NetWare an
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
288Protocols GuideIBM ProtocolsSNAT
Page 306 and 307:
290Protocols GuideIBM ProtocolsProt
Page 308 and 309:
292Protocols GuideIBM ProtocolsSNA
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
300Protocols GuideAppleTalk: Apple
Page 318 and 319:
302Protocols GuideDECnet and Protoc
Page 320 and 321:
304Protocols GuideSS7 / C7 Protocol
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
318Protocols GuideOther Protocols
Page 336 and 337:
320Protocols GuideOther ProtocolsPr
Page 338 and 339:
322Protocols GuideOther ProtocolsPr
Page 340 and 341:
324Network Protocols Dictionary: Fr
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
342Network Communication Protocols
show all

network protocols handbook.pdf

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?