- •Table of Contents
- •Cisco Switching Black Book
- •Introduction
- •Overview
- •Is This Book for You?
- •How to Use This Book
- •The Black Book Philosophy
- •Chapter 1: Network Switching Fundamentals
- •In Depth
- •Physical Media and Switching Types
- •A Bit of History
- •Networking Architectures
- •The Pieces of Technology
- •Repeaters
- •Hubs
- •Bridges
- •Routers
- •Switches
- •Network Design
- •Collision Domains
- •Broadcast Domains
- •Why Upgrade to Switches?
- •Switched Forwarding
- •Switched Network Bottlenecks
- •The Rule of the Network Road
- •Switched Ethernet Innovations
- •Fast Ethernet
- •Gigabit Ethernet
- •The Cisco IOS
- •Connecting to the Switch
- •Powering Up the Switch
- •The Challenges
- •Entering and Exiting Privileged EXEC Mode
- •Entering and Exiting Global Configuration Mode
- •Entering and Exiting Interface Configuration Mode
- •Entering and Exiting Subinterface Configuration Mode
- •Saving Configuration Changes
- •Chapter 2: Basic Switch Configuration
- •In Depth
- •Campus Hierarchical Switching Model
- •Access Layer
- •Distribution Layer
- •Core Layer
- •Remote Network Monitoring
- •Connecting to the Console Port
- •Console Cable Pinouts
- •Console Connectors
- •Switch IOSs
- •The IOS Configuration Modes
- •Limiting Telnet Access
- •Implementing Privilege Levels
- •Setting the Login Passwords
- •Setting Privilege Levels
- •Assigning Allowable Commands
- •Configuring the Hostname
- •Configuring the Date and Time
- •Configuring an IP Address and Netmask
- •Configuring a Default Route and Gateway
- •Configuring Port Speed and Duplex
- •Enabling SNMP Contact
- •Logging On to a Switch
- •Setting the Login and Enable Passwords
- •Changing the Console Prompt
- •Entering a Contact Name and Location Information
- •Configuring System and Time Information
- •Configuring an IP Address and Netmask
- •Configuring a Default Route and Gateway
- •Viewing the Default Routes
- •Configuring Port Speed and Duplex
- •Enabling SNMP
- •Configuring Trap Message Targets
- •Configuring the Console Port
- •Configuring Telnet
- •Configuring the Password
- •Configuring an IP Address and Default Gateway
- •Configuring SNMP
- •Configuring ROM
- •Entering ROM Configuration Mode
- •Booting ROM Mode from a Flash Device
- •Configuring SNMP
- •Configuring RMON
- •Using Set/Clear Command Set Recall Key Sequences
- •Chapter 3: WAN Switching
- •In Depth
- •WAN Transmission Media
- •Synchronous Transport Signal (STS)
- •Cisco WAN Switches
- •MGX 8200 Series
- •IGX 8400 Series
- •WAN Switch Hardware Overview
- •Cisco WAN Switch Network Topologies
- •Network Management
- •WAN Manager
- •Accessing and Setting Up IGX and BPX Switches
- •Adding New Users
- •Using the History Command
- •Displaying a Summary of All Card Modules
- •Displaying Detailed Information for a Card Module
- •Displaying the Power and Temperature of a Switch
- •Displaying the ASM Statistics for BPX
- •Configuring the ASM Setting for BPX
- •Logging Out
- •Resetting the Switch
- •Displaying Other Switches
- •Setting the Switch Name
- •Setting the Time Zone
- •Configuring the Time and Date
- •Configuring the Control and Auxiliary Ports
- •Modifying the Functions of the Control and Auxiliary Ports
- •Configuring the Printing Function
- •Configuring the LAN Interface
- •Accessing the MGX 8850 and 8220
- •Adding New Users
- •Changing Passwords
- •Assigning a Switch Hostname
- •Displaying a Summary of All Modules
- •Displaying Detailed Information for the Current Card
- •Changing the Time and Date
- •Displaying the Configuration of the Maintenance and Control Ports
- •Displaying the IP Address
- •Configuring the IP Interface
- •Displaying the Alarm Level of the Switch
- •Chapter 4: LAN Switch Architectures
- •In Depth
- •The Catalyst Crescendo Architecture
- •ASICs
- •The Crescendo Processors
- •Crescendo Logic Units
- •Other Cisco Switch Processors, Buses, ASICs, and Logic Units
- •AXIS Bus
- •CEF ASIC
- •Phoenix ASIC
- •SAGE ASIC
- •QTP ASIC
- •QMAC
- •Bridging Types
- •Source Route Bridging
- •Source Route Transparent Bridging
- •Source Route Translational Bridging
- •Transparent Bridging
- •Source Route Switching
- •Switching Paths
- •Process Switching
- •Fast Switching
- •Autonomous Switching
- •Silicon Switching
- •Optimum Switching
- •Distributed Switching
- •NetFlow Switching
- •System Message Logging
- •Loading an Image on the Supervisor Engine III
- •Booting the Supervisor Engine III from Flash
- •Setting the Boot Configuration Register
- •Configuring Cisco Express Forwarding
- •Enabling CEF
- •Disabling CEF
- •Enabling dCEF
- •Disabling dCEF
- •Disabling CEF on an Individual Interface
- •Configuring CEF Load Balancing
- •Disabling CEF Load Balancing
- •Enabling Network Accounting for CEF
- •Setting Network Accounting for CEF to Collect Packet Numbers
- •Viewing Network Accounting for CEF Statistics
- •Viewing the Adjacency Table on the 8500 GSR
- •Clearing the Adjacency Table on the 8500 GSR
- •Clearing the Server Logging Table
- •Disabling Server Logging
- •Displaying the Logging Configuration
- •Displaying System Logging Messages
- •Chapter 5: Virtual Local Area Networks
- •In Depth
- •The Flat Network of Yesterday
- •Why Use VLANs?
- •VLAN Basics
- •A Properly Switched Network
- •Switched Internetwork Security
- •Scaling with VLANs
- •VLAN Boundaries
- •VLAN Membership Types
- •Traffic Patterns Flowing through the Network
- •VLAN Trunking
- •Trunk Types
- •LAN Emulation (LANE)
- •VLAN Trunking Protocol (VTP)
- •VTP Versions
- •VTP Advertisements
- •VTP Switch Modes
- •Methods for VLAN Identification
- •Dynamic Trunking Protocol
- •InterVLAN Routing
- •Internal Route Processors
- •How InterVLAN Routing Works
- •Configuring a Static VLAN on a Catalyst 5000 Series Switch
- •Configuring Multiple VLANs on a Catalyst 5000 Series Switch
- •Creating VLANs on a Catalyst 1900EN Series
- •Assigning a Static VLAN to an Interface on a 1900EN Series
- •Viewing the VLAN Configuration on a 1900 Series
- •Viewing an Individual VLAN Configuration on a 1900 Series
- •Configuring a Trunk Port on a Cisco 5000 Series
- •Mapping VLANs to a Trunk Port
- •Configuring a Trunk Port on a Cisco 1900EN Series
- •Clearing VLANs from Trunk Links on a Cisco 5000 Series
- •Clearing VLANs from Trunk Links on a Cisco 1900EN Series
- •Verifying a Trunk Link Configuration on a 5000 Series
- •Verifying a Trunk Link Configuration on a 1900EN Series
- •Configuring the VTP Version on a Catalyst 5000 Switch
- •Configuring a VTP Domain on a Catalyst 1900 Switch
- •Setting a VTP Domain Password on a Catalyst Switch
- •Configuring a Catalyst 1900 Switch as a VTP Server
- •Configuring a Catalyst 1900 Switch as a VTP Client
- •Configuring a Catalyst 1900 Switch for Transparent Mode
- •Configuring VTP Pruning on a Catalyst 1900 Switch
- •Configuring VTP on a Set/Clear CLI Switch
- •Configuring VTP on a 1900 Cisco IOS CLI Switch
- •Verifying the VTP Configuration on a Set/Clear CLI
- •Displaying VTP Statistics
- •Configuring VTP Pruning on a Set/Clear CLI Switch
- •Disabling Pruning for Unwanted VLANs
- •Configuring IP InterVLAN Routing on an External Cisco Router
- •Configuring IPX InterVLAN Routing on an External Router
- •In Depth
- •Internal Route Processors
- •Available Route Processors
- •Routing Protocol Assignment
- •Supervisor Engine Modules
- •Supervisor Engines I and II
- •Supervisor Engine III
- •Using the Supervisor Engine
- •Etherport Modules
- •Port Security
- •Manually Configured MAC Addresses
- •Determining the Slot Number in Which a Module Resides
- •Accessing the Internal Route Processor from the Switch
- •Configuring a Hostname on the RSM
- •Assigning an IP Address and Encapsulation Type to an Ethernet Interface
- •Setting the Port Speed and Port Name on an Ethernet Interface
- •Configuring a Default Gateway on a Catalyst 5000
- •Verifying the IP Configuration on a Catalyst 5000
- •Enabling RIP on an RSM
- •Configuring InterVLAN Routing on an RSM
- •Configuring IPX InterVLAN Routing on the RSM
- •Configuring AppleTalk InterVLAN Routing on an RSM
- •Viewing the RSM Configuration
- •Assigning a MAC Address to a VLAN
- •Viewing the MAC Addresses
- •Configuring Filtering on an Ethernet Interface
- •Configuring Port Security on an Ethernet Module
- •Clearing MAC Addresses
- •Configuring the Catalyst 5000 Supervisor Engine Module
- •Changing the Management VLAN on a Supervisor Engine
- •Viewing the Supervisor Engine Configuration
- •Configuring the Cisco 2621 External Router for ISL Trunking
- •Configuring Redundancy Using HSRP
- •Chapter 7: IP Multicast
- •In Depth
- •IP Multicasting Overview
- •Broadcast
- •Unicast
- •Multicast
- •IP Multicasting Addresses
- •The Multicast IP Structure
- •Delivery of Multicast Datagrams
- •Multicast Distribution Tree
- •Multicast Forwarding
- •IGMP Protocols
- •Internet Group Management Protocol (IGMP)
- •IGMPv1
- •IGMPv2
- •Time to Live
- •Multicast at Layer 2
- •IGMP Snooping
- •Cisco Group Management Protocol
- •Router Group Management Protocol
- •GARP Multicast Registration Protocol
- •Configuring IP Multicast Routing
- •Disabling IP Multicast Routing
- •Enabling PIM on an Interface
- •Disabling PIM on an Interface
- •Configuring the Rendezvous Point
- •Adding a Router to a Multicast Group
- •Configuring a Router to Be a Static Multicast Group Member
- •Restricting Access to a Multicast Group
- •Changing the IGMP Version
- •Configuring Multicast Groups
- •Removing Multicast Groups
- •Configuring Multicast Router Ports
- •Displaying Multicast Routers
- •Removing the Multicast Router
- •Configuring IGMP Snooping
- •Disabling IGMP Snooping
- •Displaying IGMP Statistics
- •Displaying Multicast Routers Learned from IGMP
- •Displaying IGMP Multicast Groups
- •Configuring CGMP
- •Disabling CGMP
- •Displaying CGMP Statistics
- •Configuring RGMP on the Switch
- •Disabling RGMP on the Switch
- •Configuring RGMP on the Router
- •Disabling RGMP on the Router
- •Displaying RGMP Groups
- •Displaying RGMP VLAN Statistics
- •Configuring GMRP
- •Disabling GMRP
- •Enabling GMRP on Individual Ports
- •Disabling GMRP on Individual Ports
- •Configuring GMRP Registration
- •Displaying the GMRP Configuration
- •Setting GMRP Timers
- •Displaying GMRP Timers
- •Disabling Multicast Suppression
- •Chapter 8: WAN Cell Switching
- •In Depth
- •ATM Overview
- •LANE
- •ATM Protocols
- •ATM Circuit Switching
- •ATM Cells
- •The ATM Switch and ATM Endpoints
- •The ATM Reference Model
- •Specifying ATM Connections
- •ATM Addressing
- •Local Area Network Emulation (LANE)
- •LANE Components
- •Integrated Local Management Interface (ILMI)
- •LANE Communication
- •LANE Configuration Guidelines
- •How LANE Works
- •Implementing LANE
- •Configuring ATM on the 5000 Switch
- •Connecting in an ATM Network
- •Monitoring and Maintaining LANE
- •Accessing the ATM LANE Module
- •Displaying the Selector Field
- •Configuring the LES/BUS
- •Verifying the LES/BUS Configuration
- •Configuring a LEC for an ELAN
- •Verifying a LEC Configuration on an ELAN
- •Configuring the LECS
- •Viewing the LANE Database
- •Binding the LECS Address to an Interface
- •Verifying the LECS Configuration
- •Chapter 9: LightStream Switches
- •In Depth
- •LightStream 100
- •LightStream 1010
- •LightStream 2020
- •Neighborhood Discovery Function
- •Virtual Path Connections
- •LightStream Troubleshooting Tools
- •LightStream Boot Process
- •Supported Troubleshooting Protocols
- •Snooping Mechanisms
- •Multiprotocol Over ATM
- •Configuring the Hostname
- •Configuring an Enable Password
- •Configuring the Processor Card Ethernet Interface
- •Configuring Virtual Private Tunnels
- •Verifying an ATM Interface Connection Status
- •Viewing the Configured Virtual Connections
- •Configuring the LECS ATM Address on a LightStream 1010 Switch
- •Configuring the Advertised LECS Address
- •Viewing the LANE Configuration
- •Viewing the Installed Modules
- •Configuring the MPC
- •Configuring the MPS
- •Changing the MPS Variables
- •Monitoring the MPS
- •Enabling ILMI Autoconfiguration
- •Configuring LANE on a LightStream 1010
- •Powering on the LightStream 100 ATM Switch
- •Configuring the LS100 Switch
- •Recovering a Lost Password
- •Chapter 10: Layer 2 Redundant Links
- •In Depth
- •Layer 2 Switching Overview
- •Frames
- •Broadcast and Multicast Frames
- •Unknown Unicasts
- •Layer 2 Network Loops
- •Danger! Data Loops!
- •STP Root Bridges
- •Bridge Protocol Data Units
- •Root Bridge Selection
- •Spanning Tree Convergence Time
- •STP Port States
- •EtherChannel
- •Link Failure
- •Port Aggregation Protocol
- •Fast Convergence Components of STP
- •PortFast
- •UplinkFast
- •BackboneFast
- •Viewing the STP Configuration on a Command Line Switch
- •Configuring the STP Root Switch
- •Configuring the STP Secondary Root Switch
- •Verifying the VLAN Priority Settings
- •Preparing to Enable EtherChannel
- •Verifying the EtherChannel Configuration
- •Defining an EtherChannel Administrative Group
- •Viewing an EtherChannel Administrative Group
- •Identifying the Template Port
- •Verifying the EtherChannel Configuration on a Command Line Interface IOS
- •Verifying the PortFast Configuration
- •Verifying the UplinkFast Configuration
- •Viewing the BackboneFast Configuration
- •Chapter 11: Multilayer Switching
- •In Depth
- •How MLS Works
- •MLS Components
- •MLS Flows
- •Access List Flow Masks
- •MLS Troubleshooting Notes
- •Configuring MLS
- •MLS Cache
- •Aging Timers
- •VLAN ID
- •VTP Domain
- •Management Interfaces
- •Configuring an External MLS Route Processor
- •Assigning a VLAN ID
- •Adding an MLS Interface to a VTP Domain
- •Enabling MLS on an Individual Interface
- •Disabling MLS on an External Router Interface
- •Configuring the MLS Switch Engine
- •Disabling MLS on a Catalyst 6000
- •Disabling MLS on a Catalyst 5000
- •Configuring the MLS Cache on the Catalyst 5000
- •Configuring Fast Aging on a Catalyst 5000
- •Configuring Fast Aging on a Catalyst 6000
- •Disabling Fast Aging on a Catalyst 6000
- •Configuring Long Aging on the Catalyst 6000
- •Disabling Long Aging on the Catalyst 6000
- •Configuring Normal Aging on the Catalyst 6000
- •Disabling Normal Aging on the Catalyst 6000
- •Assigning MLS Management to an Interface on the Catalyst 5000
- •Disabling MLS Management on an Interface on the Catalyst 5000
- •Monitoring and Viewing the MLS Configuration
- •Viewing the MLS Aging Configuration on a Catalyst 6000
- •Displaying the IP MLS Configuration
- •Displaying MLS VTP Domain Information
- •Viewing the MLS VLAN Interface Information
- •Viewing MLS Statistics on the Catalyst 5000
- •Viewing MLS Statistics on the Catalyst 6000
- •Viewing MLS Entries
- •Chapter 12: Hot Standby Routing Protocol
- •In Depth
- •Routing Problems
- •Routing Information Protocol
- •Proxy ARP
- •ICMP Router Discovery Protocol
- •The Solution
- •HSRP Message Format
- •The HSRP States
- •HSRP Configuration
- •HSRP Interface Tracking
- •Opening a Session on an Internal Route Processor
- •Entering Configuration Mode on an RSM
- •Enabling HSRP and Assigning an IP Address to a Standby Group
- •Assigning an HSRP Interface Priority
- •Assigning a Preempt Delay to a Standby Group
- •Removing a Preempt Delay from a Standby Group
- •Setting the HSRP Hello and Hold Timers
- •Removing the HSRP Hello and Hold Timers
- •Configuring Two RSFC Interfaces as One HSRP Group
- •Enabling Interface Tracking
- •Using the show standby Command
- •Using the debug Command
- •Chapter 13: Policy Networking
- •In Depth
- •Access Security Policies
- •Core Layer Policies
- •Distribution Layer Policies
- •Security at the Access Layer
- •Configuring Passwords
- •Limiting Telnet Access
- •Implementing Privilege Levels
- •Configuring Banner Messages
- •Physical Device Security
- •Port Security
- •VLAN Management
- •Creating a Standard Access List
- •Creating an Extended Access List
- •Implementing Privilege Levels on a 1900EN
- •Configuring Banner Messages
- •Enabling HTTP Access
- •Enabling Port Security
- •Displaying the MAC Address Table
- •Chapter 14: Web Management
- •In Depth
- •Standard and Enterprise Edition CVSM
- •CVSM Client Requirements
- •CVSM Access Levels
- •CVSM Default Home Page
- •The Switch Image
- •Configuring the Switch with an IP Address and Setting the Default Web Administration Port
- •Connecting to the Web Management Console
- •Configuring the Switch Port Analyzer
- •Chapter 15: The Standard Edition IOS
- •In Depth
- •The 1900 and 2820 Series Switches
- •Main Menu Choices
- •[C] Console Settings
- •[A] Port Addressing
- •[R] Multicast Registration
- •Configuring Network Settings on the 1900 and 2820 Series
- •Configuring Broadcast Storm Control on Switch Ports
- •Configuring SNMP on the 1900 Series
- •Configuring Port Monitoring on the Standard Edition IOS
- •Configuring VLANs on the Standard Edition IOS
- •Configuring Spanning Tree Protocol
- •Chapter 16: Switch Troubleshooting
- •In Depth
- •Hardware Troubleshooting
- •No Power
- •POST
- •Indicator Lights
- •Switch Cabling
- •Cable Problems
- •Switch Troubleshooting Tools
- •CiscoWorks for Switched Internetworks
- •IOS Software Troubleshooting Commands
- •Viewing the Set/Clear IOS Configuration
- •Viewing the VTP Domain Configuration on a Set/Clear IOS
- •Viewing Port Statistics on a Set/Clear IOS
- •Launching the Diagnostic Console on a Cisco 1900 or 2820 Series Switch
- •Using the Diagnostic Console to Upgrade the Firmware on a Cisco 1900 or 2820 Series Switch
- •Using the Diagnostic Console for Debugging the Firmware and Hardware
- •Appendix A: Study Resources
- •Books
- •Cisco Group Study and Users Groups
- •Online Resources
- •Asynchronous Transfer Mode
- •Cisco IOS
- •Hot Standby Router Protocol
- •IP Multicast
- •Multilayer Switching
- •Quality of Service
- •Spanning Tree Protocol
- •TACACS+
- •VLANs
- •Standards Organizations
- •Cisco Job Search Sites
- •Overview
- •Appendix C: The Cisco Consultant
- •Overview
- •Establishing Credibility
- •Come Off As an Expert
- •Designing a Solution
- •Estimating the Cost
- •Presenting the Final Proposal and Creating Expectations
- •Contracting
- •Document, Document, Document
- •The Way to Fail
- •Failing to Be There When Promised, or Rushing through the Job
- •Failing to Manage Your Time
- •Assuming You Know What the Customer Needs
- •Failing to Take Responsibility
- •Conclusion
- •Required Equipment
- •Lab Objectives
- •Possible Solution
- •The 1912 Basic Configuration
- •The Catalyst 5000 Basic Configuration
- •Configuring the Cisco 2621 Interface for ISL Trunking
- •Appendix E: Switch Features
- •Access Layer Switches
- •Cisco Catalyst 1900
- •Cisco Catalyst 2820
- •Cisco Catalyst 2900
- •Cisco Catalyst 3000
- •Cisco Catalyst 3500 Series XL
- •Cisco Catalyst 3900 Series
- •Distribution Layer Switches
- •Cisco Catalyst 4000 Series
- •Catalyst 5000 Series
- •Catalyst 6000 Series
- •Core Layer/WAN Switches
- •Cisco Catalyst 8400 Series
- •Cisco Catalyst 8500 Series
- •BPX 8600 Series
- •MGX 8800 Series
- •12000 Series Gigabit Switch Routers
∙Variable bit rate−real time (VBR−RT)—Typically used for connections that carry VBR traffic in which a fixed timing relationship exists between either VBR video or voice compression.
∙Variable bit rate−non real time (VBR−NRT)—Used to carry VBR traffic in which no timing relationship exists for data traffic where a guarantee of bandwidth or latency is needed. This type of connection is used in Frame Relay where the committed information rate (CIR) of the Frame Relay connection is mapped into a bandwidth guarantee within the ATM network.
∙Unspecified bit rate−real time (UBR−RT)—Does not offer any service guarantees whatsoever. This type of connection is typically for the bursty or unpredictable traffic patterns from LAN protocols served by ATM routers.
ATM Addressing
ATM devices must have unique ATM addresses in order to connect to other ATM devices. The device at the other end of your circuit must know your address. ATM uses both private and public types of addresses. Because the ATM standard has adopted the subnetwork model of addressing, the ATM layer is responsible for mapping Network layer addresses to the ATM addresses.
Currently, two types of ATM addressing plans are used. The ATM UNI address format defined by ITU−T uses telephone−type E.164 addresses. This format is used to connect an endpoint to a telephone carrier’s network. One drawback to this type of address is that E.164 addresses are available only from large telephone carriers, which prevents the addresses from being assigned to competitors and private businesses.
The ISO has defined a second address type that uses a Network Service Access Point (NSAP) format. This format is used to connect an ATM endpoint to a private network. The ATM Forum has now used this method to incorporate the E.164 address of the public networks into the address of customers using NSAP addresses. The ATM Forum is also working on a method for the phone carriers to use NSAP−based addressing on their networks. Let’s take a look at the components of an NSAP address, as shown in Figure 8.5:
Figure 8.5: The format of an ATM NSAP address.
∙Authority and format identifier (AFI)—Used to indicate which standard is being used for the ATM address. An AFI of 47 indicates a British Standards Institute address (used by Cisco on all its ATM devices); an AFI of 39 indicates an ISO address and an E.164 address.
∙Initial domain identifier (IDI)—Indicates the address allocation and administrative authority.
∙Domain specific part (DSP)—Contains the actual routing information.
∙End−system identifier (ESI)—Places the end system’s MAC address in the frame.
∙NSAP selector field (SEL)—Identifies the LANE components.
Local Area Network Emulation (LANE)
In a LAN environment, broadcast support is an inherent part of the networking technology. Legacy networks have native broadcast support to perform address mapping resolution. In contrast, ATM networks are Non−Broadcast Multiple Access (NBMA) networks with no such support. The LANE standard was created by the ATM Forum in 1994 to provide connectivity for ATM networks to legacy Ethernet and Token−Ring networks.
LANE provides these broadcast services by making an ATM interface look like an Ethernet or Token Ring interface. LANE gives ATM devices MAC addresses, just like Ethernet or Token Ring devices. Because the ATM interfaces can use the same frame format as legacy devices, LAN−based applications can run without
167
changing the application itself or Layer 3 drivers.
This approach allows backward compatibility with existing LANs, broadcast support, and connectionless delivery. LANE has some drawbacks, however: It prevents the use of ATM−specific benefits such as QoS and doesn’t have the ability to provide flexible bandwidth allocations.
LANE is the primary component that provides connectivity between ATM devices and the devices residing on the Layer 2 LAN. This connectivity extends to devices attached to ATM stations and devices attached to LAN devices spanning the ATM network. This connectivity between ATM devices and other LAN devices is done through ELANs.
What Are ELANs?
ELANs are just like VLANs—one of their functions is to create independent broadcast domains in ATM, the same way that VLANs do in Ethernet and Token Ring networks. ELAN workstations are independent of the physical location, and like VLANs, ELANs must be connected to a Layer 3 device in order to communicate with members of another ELAN.
The Data Link layer’s MAC sublayer allows ELANs to use the Microsoft or Novell upper−level NDIS/ODI driver interfaces. This method allows ELANs to transmit Layer 3 protocols such as TCP/IP, IPX, and AppleTalk.
LANE is a standardized conversion process that allows a connectionless environment in a LAN to connect to a connection−oriented ATM environment. LANE fragments an incoming Layer 3 into a 48−byte payload and places a 5−byte ATM−specific identification header on the front of the packet, yielding a 53−byte cell. It then removes the checksum from the cell and forwards the cell through the ATM network. When the cell has traveled the ATM network, the ATM information is removed and the cell fragments are reassembled and returned to the LAN environment as a packet.
The LANE 1.0 standard can be summed up as a software interface for the Layer 3 protocol environment that encapsulates user data for either Ethernet or Token Ring packets. LANE isn’t actually the media access method for this conversion process—LANE uses three servers, which clients access over the ATM connections. The LANE servers provide address registration and resolution functions, including collecting address and route descriptor types based on the LANE standard. Let’s take a look at the LANE components.
Note FDDI can be used with LANE 1.0; however, it is not accurately defined like Ethernet and Token Ring protocols. ATM uses translational bridging techniques to map FDDI packets into either Ethernet or Token Ring.
LANE Components
LANE uses several components to provide LAN−based network connectivity. The interaction of these components allows address registration, address caching, and searchable databases. LANE uses the following components:
∙LAN Emulation Client (LEC)—Emulates a LAN interface to higher−layer protocols and applications of the OSI Reference Model.
∙LAN Emulation Server (LES)—Provides a database of LANE services, resolves addresses, manages stations that make up an ELAN, and provides registration services to LANE clients for the emulated LAN.
∙LAN Emulation Configuration Server (LECS)—Uses a database to track device memberships in each ELAN.
168
∙Broadcast and Unknown Server (BUS)—Sends broadcasts, sequences cells, controls unicast flooding, and distributes multicast packets.
Warning Notice that although LEC and LECS sound the same, they are completely different terms and components in LANE.
LAN Emulation Client (LEC)
The LEC resides in every ATM end system. It provides services to emulate the Data Link layer interface that allows communication of all higher−level protocols and applications to occur. It provides both ATM−attached devices and ATM−capable Token Ring, Ethernet, and legacy LAN topologies the ability to coexist within an ATM emulated LAN and WAN environment.
The LEC is the component responsible for passing traffic between separate VLANs on the Catalyst switches and between ELANs on the ATM switch. You can configure multiple LECs for one or more ELANs on the ATM modules. Prior to configuring a LEC on an ATM module, a VLAN must be configured on the switch, and the LES/BUS or an ELAN must be configured on one or more ATM module subinterfaces.
The LEC forwards data to other LANE components in the ELAN and performs control functions. Each LEC is a member of only one ELAN. In many instances, an Ethernet switch may have multiple LECs for each ELAN. Examples of LEC implementations include servers, routers, switches, or other network hosts. The LEC has the following functions:
∙Resolves MAC addresses
∙Transfers data
∙Performs address caching
∙Interfaces with other LANE components
∙Provides interface driver support
LAN Emulation Server (LES)
The LES for an ELAN is the central piece of LANE. It gives the LECs the information they need to establish ATM connections to other LECs in their ELAN. A single LES is responsible for address registry and resolution for an ELAN. When a LEC joins an ELAN, it forms a connection with the LES. The LEC registers its MAC and ATM addresses with the LES. The LES has the following functions:
∙Supports LECs
∙Registers addresses from LECs
∙Resolves addresses from LECs
∙Interfaces to the LEC, LECS, and BUS
The LES performs traffic control for all LECs connecting to an ELAN. This component provides the address resolution, registration, broadcast, and unknown server information that guides communication among LECs. When configuring each LEC, the LEC must request a connection from the LES. The request information contains the ATM address of the LEC, a LAN identifier, and an optional MAC address. This component also performs verification of each LEC during the initial connection with the server, checking to make sure that each LEC has permission to join the requested ELAN.
Address registration is also a function of the LES. It must maintain a database to aid in resolving addresses. This registration occurs after the LEC joins an ELAN. Each LEC provides the LES with one registered address with a join request, and no separate registrations are required.
The LES with the ATM address database responds to all address resolution queries and attempts to locate partnering LECs. The LES responds with the ATM addresses for the targeted ELANs. If no address can be found, the LES attempts to forward the request to other LECs on other ELANs.
169
The ultimate goal of the LES is to arrange and control connections with a LEC. This connection is commonly known as a control direct ATM virtual channel connection (VCC). After this connection is established, it will handle address resolution and registration responses.
Note |
The LES establishes communication with the LECS and provides verification information for |
|
LECs attempting to join. The LES does not maintain a constant connection with the BUS. |
|
The LES only provides each LEC with the ATM address of the BUS for forwarding. |
The LANE servers provide the address registration and resolution functions. These functions include collecting address and route descriptor types based on the LANE standard. Let’s take a look at the address resolution process, which is shown in Figure 8.6 and outlined as follows:
Figure 8.6: The LES address resolution process.
1.A workstation connects to a router or ATM switch and performs a physical outbound packet transmission. This example uses the Address Resolution Protocol (ARP) query to try to locate a device on a remote segment.
Note The local router is typically the ATM LEC and provides the circuit for the initial ATM address mapping.
2.The LEC takes an Ethernet frame and assigns an immediate LEC link, which is used to obtain the ATM address identifier needed to establish an ATM connection. If this process is not successful, the LEC must locate a LES.
3.The LES circuit holds the main ATM network address table and returns with the VCI assignment.
LAN Emulation Configuration Server (LECS)
The LECS provides key services such as registration for Integrated Local Management Interface (ILMI) and configuration support for the LES addresses for the corresponding emulated LAN identifiers.
The LECS contains a database of ATM addresses for the LES and BUS pairs for known ELANs. The LEC consults the LECS to determine the LES’s ATM address when it first joins an ELAN.
Note At least one LECS is required per ATM LANE switch cloud.
The LECS has the following functions:
∙Registers the LECS ATM addresses for known ELANs
∙Supplies LECs with LESs’ ATM addresses
∙Provides interfaces to the LEC and the LES
The registration process of the LECS ATM address uses the ILMI functions to connect to the ATM network; this situation usually includes an ATM switch. Support for configurations from the LECS ensures that the correct LES address is supplied to the LEC.
170
Broadcast and Unknown Server (BUS)
The BUS provides broadcasting support for an ELAN. The BUS distributes multicast data, sends or distributes unicast data, and connects the other LANE components. When the destination address of an Ethernet or Token Ring frame contains a local broadcast or a multicast address, the LEC forwards the traffic to the BUS, which forwards it to all the other LECs in the ELAN. At least one combined LES and BUS is required per ELAN. The BUS has the following functions:
∙Distributes multicast data
∙Sends or distributes unicast data
∙Interfaces to LEC and LES
The LES is the component responsible for resolving MAC addresses to ATM addresses, and the BUS is the component responsible for servicing multicast, Ethernet, and Token Ring broadcasts. The Cisco LANE implementation calls for the LES and the BUS to be configured in the same end−station.
ATM Module Subinterfaces
In order to configure ATM components on an ATM LANE module for the Catalyst 5000 or 6000 family of switches, you need to use subinterfaces. Depending on the level of traffic you expect on your network, you may want to place different LES/BUS components throughout the framework of your network. To configure a LES or BUS on the ATM module, you need to complete the following tasks:
1.Enter Interface Configuration mode.
2.Specify the subinterface for the ELAN.
3.Specify the type of link: Ethernet or Token Ring.
4.Enable the LES and BUS on the ELAN.
5.Repeat this process for each LES/BUS.
The BUS must be used to sequence and distribute broadcast data to all the LECs. However, sending a large volume of broadcast data to all the LECs can severely impact the overall performance of the network. For this reason, it may be necessary for the BUS to place restrictions on the LANE components to control the maximum throughput rate for each device. The BUS’s primary function is to provide broadcast management support for LANs. The BUS must supply the following services:
∙Distribute unicast and multicast data to all the LECs in the network
∙Connect interfaces to the ELAN
Distribution of unicast and multicast data includes the transmission of data to the LECs in the network. Whenever possible, the LEC will establish a direct connection to another LEC. If this isn’t possible, then data the BUS receives is broadcast to each LEC on the ELAN. This option can be enabled and disabled, and you should carefully consider whether you need this option, because it can eat up costly bandwidth.
Note When interfacing to ELANs, the BUS establishes a bi−directional connection that allows forwarding of multicast and unicast frames with unknown destinations.
LEC Queries
LECs send queries for configuration information to receive the LES address. The LECS then assigns the correct LES address for each LEC. The LES also has the ability to establish a connection with the LECS.
A reply to a query can be as simple as providing a single LES address or it can provide more information, such as:
171