270 likes | 289 Views
This article discusses the general architecture of ATM, LAN Emulation (LANE), native mode, Classical IP over ATM, NHRP and shortcut switching, and Multiprotocol over ATM (MPOA). It explores the peering model and overlay model, comparing emulation and native mode. The article concludes with insights and issues related to ATM QoS, performance, and scaling.
E N D
Overlay Models Reference: “ATM Internetworking” by Anthony Alles http://www.cisco.com/warp/public/614/12.html
Outline • ATM in General • LAN Emulation (LANE) • Native Mode Models • Classical IP over ATM • Classical IP over ATM Extension • Next-Hop Address Resolution (NHRP) and shortcut switching • Multiprotocol over ATM (MPOA)
ATM in General • ATM was envisioned to be the ultimate winner which will take over the whole Internet • By all means, it’s a networking layer technology with its own routing and addressing architecture, just like IP • The seven-layer OSI model is imperfect in modeling it • In practice, due to the adoption of overlay model, ATM has been downgraded as a layer 2 or even layer 1 like technology
ATM in General (cont’d) • Architecture
ATM in General (cont’d) • Label Swapping
ATM in General (cont’d) • 2-layer label stacking:
ATM in General (cont’d) • PNN-I Hierarchical Routing:
ATM in General (cont’d) • Signaling: based on source routing
Peering or Overlaying? • Peering model
Peering or Overlaying? (cont’d) • Overlay Model:
Emulation or Native Mode?(cont’d) • Emulation: • Quick deployment without driver changes • Supporting any networking layers, e.g., IP, IPX • More overhead per bit sent • No QoS
Emulation or Native Mode?(cont’d) • Native mode: • More effort • QoS possible
LANE Architecture • A single ELAN
LANE Architecture (cont’d) • Protocol Architecture
LANE Architecture (cont’d) • Building blocks:
ELAN Architecture (cont’d) • Control connections:
LANE Architecture (cont’d) • Data Connections:
ELAN Architecture (cont’d) • Inter-ELAN communications:
Native Mode • Classical IP over ATM • Classical IP over ATM Extension: • NHRP and shortcut switching • MPOA
Classical IP over ATM: Architecture • Encapsulations (RFC1483/2684): • LLC/SNAP • VC multiplexing
Classical IP over ATM: Architecture (cont’d) • IP over ATM forwarding mechanism
Classical IP over ATM: Architecture (cont’d) • Routing between LISs in classical IP model
Classical IP over ATM Extension • NHRP and shortcut switching
MPOA • As its name implies, MPOA intended to support multiprotocols over ATM • NHRP for shortcut switching • Separating routing functions from forwarding functions using “edge devices”
Conclusions • ATM QoS feature cannot be fully exploited • No QoS for ELAN • Complex QoS mapping between IP and ATM for classical IP and performance bottleneck at multiservice switch between LISs • No hard QoS for shortcut switching due to its flow driven nature • Having to manage multi signaling/routing protocols at different layers • NHRP for shortcut switching does not scale and has performance issues • Have to revisit peering model!!