Page 1 MPLS Module Installation and User Guide Extreme Networks, Inc. 3585 Monroe Street Santa Clara, California 95051 (888) 257-3000 http://www.extremenetworks.com Published: February 2002 Part number: 100084-00 Rev. 02...
Page 2 ©2002 Extreme Networks, Inc. All rights reserved. Extreme Networks and BlackDiamond are registered trademarks of Extreme Networks, Inc. in the United States and certain other jurisdictions. ExtremeWare, Extreme Standby Router Protocol, ESRP, Summit, and the Extreme Networks logo are trademarks of Extreme Networks, Inc., which may be registered or pending registration in certain jurisdictions.
Page 3: Table Of Contents
Contents Preface Introduction Conventions Related Publications Overview Summary of Features MPLS Module Physical Description BlackDiamond 6800 Series Switch Overview About the MPLS Module About MPLS About MPLS Layer-2 VPNs MPLS Module Installation and User Guide Terminology MPLS IP Unicast Forwarding...
Page 4 MPLS Module Slot Locations LED Indicators Displaying Slot Status Information Identifying Problem Categories Fixing Configuration Errors Upgrading the Switch Software Image Upgrading the MPLS Module Software Image Fixing Power-Related Problems Identifying Conditions for Replacing an MPLS Module Tools and Equipment...
Page 5 MPLS Layer Configuring MPLS Configuring the Label Distribution Protocol Overview of LDP Configuring LDP Configuration Example MPLS Module Installation and User Guide MPLS Label Stack Penultimate Hop Popping Label Binding Label Space Partitioning Commands for MPLS Configuring Interfaces Configuring the Maximum Transmission Unit Size Configuring the Propagation of IP TTL Configuring Penultimate Hop Popping Configuring QoS Mappings...
Page 6 Configuring RSVP-TE RSVP Elements Traffic Engineering RSVP Features Configuring RSVP-TE Message Types Path Message Reservation Message Path Error Message Reservation Error Message Path Tear Message Reservation Tear Message Reservation Confirm Message Reservation Styles Fixed Filter Shared Explicit Wildcard Bandwidth Reservation Bandwidth Accounting RSVP State RSVP Tunneling...
Page 7 Configuration Example MPLS and IP Routing Routing Using LSPs LSPs and IBGP Next Hops Optimized Forwarding of Non-MPLS IP Traffic Configuring MPLS Layer-2 VPNs Overview of MPLS Layer-2 VPNs TLS VPN Characteristics Configuring MPLS Layer-2 VPNs MPLS Module Installation and User Guide Configuring an RSVP-TE LSP Adding a Path to an RSVP-TE LSP Displaying RSVP-TE LSP Configuration Information...
Page 8 TLS VPN Configuration Examples Using ESRP with MPLS TLS Configuring Destination-Sensitive Accounting Overview of Destination-Sensitive Accounting Basic Accounting Configuration Information Configuring Access Profiles Configuring Route Maps viii Basic MPLS TLS Configuration Example Full Mesh TLS Configuration mpls1 mpls2 mpls3 mpls4 Hub and Spoke TLS Configuration mpls1 mpls2...
Page 9 Retrieving Accounting Statistics Additional MPLS Module Support Topics General Switch Attributes Image and Configuration Attributes 802.1p and 802.1Q Commands VLAN Commands FDB Commands Basic IP Commands ICMP Commands IP Multicast and Flow Redirection Commands OSPF Commands BGP Commands Route Map Commands...
Page 10 Supported MIBs and Standards Standards Supported for MPLS MIBs Supported for MPLS Index Index of Commands MPLS Module Installation and User Guide...
Page 11: Preface
This guide provides the required information to install the MPLS module in a ® BlackDiamond 6800 series switch from Extreme Networks and perform the initial module configuration tasks. This guide is intended for use by network administrators who are responsible for installing and setting up network equipment.
Page 12: Terminology
Terminology Switches and switch modules that use naming conventions ending in “i” have additional capabilities that are documented throughout this user guide. For the most current list of products supporting the “i” chipset, consult your release notes. Unless otherwise specified, a feature requiring the “i” chipset requires the use of both an “i”...
Page 13: Related Publications
• ExtremeWare Command Reference Guide • BlackDiamond 6800 Series Switch Hardware Installation Guide • BlackDiamond Module Installation Note Documentation for Extreme Networks products is available on the World Wide Web at the following location: http://www.extremenetworks.com/ MPLS Module Installation and User Guide Description Key names are written with brackets, such as [Return] or [Esc].
Page 14 MPLS Module Installation and User Guide...
Page 15 IP services for the other input/output (I/O) modules installed in the chassis. The MPLS module contains a powerful set of packet processing resources that operate in a one-armed fashion: receiving frames from the switch fabric, processing the frames, and transmitting the frames back into the switch fabric.
Page 16: Overview
The MPLS module consists of a printed circuit board mounted on a metal carrier that acts as the insertion vehicle in a BlackDiamond 6800 series switch. The module carrier also includes ejector/injector handles and captive retaining screws at each end of the module front panel.
Page 17 A maximum of four MPLS modules can be placed in a BlackDiamond 6800 series switch. Captive retaining screw Ejector/injector handle Service ports Figure 1-1: MPLS module The MPLS module has the following key components: • Two high-performance network processors •...
Page 18: Mpls Module Led Indicators
Overview The network processors are high-performance, programmable devices that enhance the Extreme “i” chipset to support expanded functionality, features, and flexibility. The GPP subsystem handles system control and MPLS module management functions. The GPP subsystem resides outside the packet-forwarding data path to optimize routing and billing performance.
Page 19: Service Port
Service Port The MPLS module is equipped with one front-panel service port. The port is reserved for use only by Extreme Networks technical support personnel for diagnostic purposes. Console Port The MPLS module is equipped with one front-panel serial port. The port is reserved for use only by Extreme Networks technical support personnel for diagnostic purposes.
Page 20: About The Mpls Module
Ethernet ports. The MPLS module operates in a one-armed fashion: receiving frames from the switch fabric, processing the frames, and transmitting the frames back into the switch fabric to the appropriate I/O module output port. MPLS modules are only compatible with Inferno-series MSM modules. They are compatible with both Inferno-series and Summit-series I/O modules.
Page 21: About Mpls Layer-2 Vpns
MPLS creates a Label Switched Path (LSP) along which each Label Switch Router (LSR) can make forwarding decisions based solely upon the content of the labels. At each hop, the LSR simply strips off the existing label and applies a new one that tells the next LSR how to forward the packet.
Page 22: About Ip Unicast Forwarding
BlackDiamond chassis can be scaled up to 16 Gbps by adding up to four MPLS modules. MPLS modules interface to the BlackDiamond switch fabric via four 1 Gbps internal links. IP unicast traffic is internally forwarded from the BlackDiamond I/O modules using one of three backplane load-sharing policies: port-based, address-based, or round-robin.
Page 23 About Destination-Sensitive Accounting You use accounting statistics to bill your customers. For a given set of statistics, the source VLAN ID identifies the customer and the accounting bin number corresponds to a billing rate. Use the ExtremeWare function to configure policies that assign accounting route-map bin numbers to IP routes.
Page 24 Overview 1-10 MPLS Module Installation and User Guide...
Page 25: Installing Or Replacing An Mpls Module
Installing or Replacing an MPLS Module This chapter covers the following topics: • Preparing for Installation on page 2-1 • Inserting and Securing a Module on page 2-6 • Verifying the Module Installation on page 2-8 • Troubleshooting on page 2-9 •...
Page 26: Software And Hardware Version Requirements
Installing or Replacing an MPLS Module Software and Hardware Version Requirements MPLS modules are compatible with “i” -series MSM modules, Summit and “i” -series I/O modules, and Packet over SONET (PoS) modules. For the most current list of I/O and PoS modules supported for use with the MPLS module, consult your release notes. Software support for the MPLS module is provided in an ExtremeWare technology release, which is a software release that provides specialized hardware support or additional functionality not found in the current mainstream ExtremeWare release.
Page 27: Safety Information
Safety Information Before you begin the process of installing or replacing an MPLS module in a BlackDiamond 6800 series switch, read the safety information in this section. Failure to observe the necessary safety guidelines can lead to personal injury or damage to the equipment.
Page 28: Tools
ESD-preventive wrist strap and ensure that the leash is securely grounded before handling a bare circuit assembly. Tools You need the following tools to install an Extreme Networks MPLS module in a BlackDiamond 6800 series chassis: • ESD-preventive wrist strap and grounding leash that is provided with the BlackDiamond 6800 series chassis.
Page 29 ESD wrist strap connector Power supplies Figure 2-1: Slot locations in a BlackDiamond 6808 series chassis MPLS Module Installation and User Guide MSM module I/O module slots slots 50015 CONSOLE MODEM MGMT LINK / ACTIVITY PCMCIA POWER DC OUT AC IN 50021 V-50/60Hz 200-240V, 15A...
Page 30: Inserting And Securing A Module
ESD-preventive wrist strap that is provided with the chassis, and connect the metal end of the grounding leash to the ground receptacle located on the top-left corner of the BlackDiamond 6800 series switch front panel. Leave the ESD-preventive wrist strap permanently connected to the BlackDiamond 6800 series chassis so that it is always available when you need to handle ESD-sensitive switch components.
Page 31 (a) Loosen captive screws (b) Pivot ejector/injector handles Figure 2-2: Inserting and securing an MPLS module When the module is pushed into the chassis slot, the ejector/injector handles begin pivoting to their closed position. d Close the ejector/injector handles by pushing them toward the center of the module.
Page 32: Verifying The Module Installation
Installing or Replacing an MPLS Module e Use a #1 Phillips-head screwdriver to tighten the captive screw on each end of the module front panel to prevent the module from being dislodged from the backplane connectors and to ensure satisfactory protection from EMI. Repeat this procedure for additional modules, if applicable.
Page 33: Troubleshooting
The information in this section should be used in conjunction with the “Troubleshooting” appendix in the ExtremeWare Software User Guide and the release notes that accompanied your Extreme Networks product. If you encounter a problem that is not discussed in one of these documents, contact Extreme Networks technical support.
Page 34: Identifying Problem Categories
Solid amber Diagnostics failed 2-10 Corrective action No action required. See “Fixing Configuration Errors” on page 2-11. See “Upgrading the Switch Software Image” on page 2-11. See “Upgrading the MPLS Module Software Image” on page 2-11. See “Identifying Conditions for Replacing an MPLS Module”...
Page 35: Fixing Configuration Errors
The first two commands listed here, clear the slot of a previously assigned module type. The third command replaces the existing module type configuration with a new module type configuration. Upgrading the Switch Software Image If the STATUS LED on the MPLS module turns amber and blinks, use the show slot <slot>...
Page 36: Fixing Power-Related Problems
If the LEDs on all other modules are off, verify that the BlackDiamond 6800 series switch is connected to an appropriate power source and is turned on. If the LEDs on the new module are off, but the LEDs on other modules are on, try ejecting and reseating the unpowered module.
Page 37: Identifying Conditions For Replacing An Mpls Module
The <slot> command also displays operational information related to the MPLS module. Information displayed includes the BlackDiamond switch fabric card state, Network Processor status, General Purpose Processor status, hardware serial number and type, and image version and boot settings.
Page 38: Removing And Replacing An Mpls Module
BlackDiamond 6800 series switch front panel. 2 Identify the MPLS module to be replaced and write down the following information for later use: —...
Page 39 6 Grasp the module front panel with one hand and place your other hand under the metal card carrier to support the weight of the module. Slide the module completely out of the chassis slot. Place the module immediately into an antistatic sack to protect it from ESD damage and prevent dust from collecting on the module’s optical fiber connectors.
Page 40 Installing or Replacing an MPLS Module 2-16 MPLS Module Installation and User Guide...
Page 41: Configuring The Mpls Module
ExtremeWare Software User Guide. For hardware installation information for the BlackDiamond 6800 series switch, see the BlackDiamond Hardware Installation Guide. Documentation for Extreme Networks products is available at the Extreme Networks home page at http://www.extremenetworks.com/. This chapter covers the following topics: •...
Page 42: Mpls Terms And Acronyms
Configuring the MPLS Module Conceptually, label switching is straightforward. A label is a relatively short, fixed-length identifier that is used to forward packets received from a given link. The label value is locally significant to a particular link and is assigned by the receiving entity.
Page 43 Label Distribution Protocol. A protocol defined by the IETF used to establish an MPLS Label Switched Path (LSP). Label Edge Router. A Label Switch Router that is at the beginning (ingress) or end (egress) of a Label Switched Path. Label Switched Path. The unidirectional MPLS connection between two routers over which packets are sent.
Page 44: Label Switched Paths
Configuring the MPLS Module Table 3-1: MPLS Terms and Acronyms (continued) Term or Acronym Description TLS Tunnel A specific type of VC tunnel that carries only VLAN tagged Ethernet traffic. Tunnel LSP Any active RSVP-TE LSP used to forward IP traffic through an MPLS network.
Page 45: Label Retention Modes
DU mode be used when a conflict exists. Label request messages can still be used when MPLS is operating in unsolicited mode. The Extreme LDP implementation supports DU mode only. RSVP-TE, by definition, is DoD. Label Retention Modes MPLS provides two modes for label retention: •...
Page 46: Lsp Control Modes
MPLS protocols are designed primarily for routed IP networks and are implemented by Label Switch Routers (LSRs). The router where an LSP originates is called the ingress LSR, while the router where an LSP terminates is called the egress LSR.
Page 47: Supporting Quality Of Service Features
Ingress Source IP network Figure 3-2: LSR types The functions of the LSR types are described in Table 3-2. Table 3-2: LSR Functions Ingress LER Intermediate LSR Egress LER Supporting Quality of Service Features Quality of Service (QoS) LSP support is an important attribute of MPLS. MPLS supports the Differentiated Services (DiffServ) model of QoS.
Page 48: Mpls Layer
Configuring the MPLS Module MPLS Layer MPLS can be thought of as a shim-layer between layer 2 and layer 3 of the protocol stack. MPLS provides connection services to layer-3 functions while making use of link-layer services from layer-2. To achieve this, MPLS defines a shim header that is inserted between the link layer header and the network layer header of transmitted frames.
Page 49 Figure 3-5 illustrates the format of a unicast MPLS frame on an Ethernet link. The MAC addresses are those of the adjacent MPLS router interfaces. The x8847 Ethertype value indicates that the frame contains a MPLS unicast packet. A different Ethertype value (x8848) is used to identify MPLS multicast packets.
Page 50: Penultimate Hop Popping
Remotely assigned labels are labels that are assigned based on binding information received from another LSR. Label Space Partitioning The Extreme MPLS implementation supports approximately 64 K locally-assigned labels. The label space is partitioned as described in Table 3-3. 3-10...
Page 51 The MPLS module does not limit the number of labels that can be popped by the egress LSR function, as indicated in Table 3-4. When the switch performs label swapping as a transit or intermediate LSR, no hard limits are imposed on the maximum size of the label stack, other than the constraint of not exceeding the maximum frame size supported by the physical links comprising the LSP.
Page 52: Configuring Mpls
VLAN. Enables and disables penultimate hop popping (PHP) at the egress LSR. When enabled, PHP is requested on all LSPs for which the switch is the egress LSR. The default setting is disabled. MPLS Module Installation and User Guide...
Page 53 Disables MPLS on the switch. Disabling MPLS causes all LSPs to be released and all LDP neighbor sessions to be terminated. Enables MPLS on the switch. By default, MPLS is disabled. Displays MPLS configuration information for one or all VLANs. Omitting the vlan keyword, displays information for all VLANs.
Page 54 Configuring the MPLS Module Table 3-5: MPLS Configuration Commands (continued) Command show mpls forwarding {summary | detail | inactive | host <ipaddress> {detail | inactive} | prefix <ipaddress/masklength> {detail | inactive} | rsvp-te <ipaddress> {detail}} show mpls interface {ldp | targeted-ldp | rsvp-te} show mpls label {summary | detail | <label_number>...
Page 55: Configuring Interfaces
VLAN. The specified VLAN must be configured with an IP address, and have IP forwarding enabled. IGMP snooping must also be enabled on the switch. VLANs are selected, MPLS is enabled on all VLANs that have an IP address and IP forwarding enabled.
Page 56: Configuring The Maximum Transmission Unit Size
Configuring the MPLS Module Configuring the Maximum Transmission Unit Size After you have enabled MPLS, you can configure the maximum transmission unit (MTU) size using the following command: config mpls vlan [<name> | all] ip-mtu <number> This command configures the IP MTU for frames transmitted onto MPLS LSPs via the specified egress VLAN.
Page 57: Configuring Penultimate Hop Popping
[enabled | disabled] This command enables or disables whether PHP is requested by the egress LER. When PHP is enabled, PHP is requested on all LSPs for which the switch is the egress LER. PHP is requested by assigning the Implicit Null Label in an advertised mapping. PHP is always performed when requested by an egress LSR (for example, when the switch is acting as an intermediate LSR).
Page 58: Dot1P-To-Exp Mappings
Exp-to-dot1p Mappings The exp-to-dot1p mappings are used when the switch performs label swapping as an intermediate LSR and when the switch is the egress LSR. In both of these cases, the MPLS module receives an MPLS-encapsulated frame. The EXP field in the frame is used as an to the exp-to-dot1p table.
Page 59: Resetting Mpls Configuration Parameter Values
The frame is then assigned to a QoS profile, based on the retrieved 802.1p priority value. The mappings between 802.1p priority values and QoS profiles are configured using the following command: config dot1p type For more information on QoS, see the ExtremeWare Software User Guide. For more information on the PoS module, see the PoS Module Installation and User Guide.
Page 60: Displaying Mpls Configuration Information
When the parameter is omitted, this command displays the values of all MPLS vlan configuration parameters that apply to the entire switch, the current status of peer LSRs, and a list of the VLANs for which MPLS is enabled. When the...
Page 61: Displaying Mpls Label Mapping Information
MPLS packets. When the parameter is omitted, summary information is displayed for label_number all incoming label assignments that have been made by the switch. When the is specified, summary information is displayed for the label. label_number Use the keyword to display the label associated with an FEC.
Page 62: Displaying Mpls Qos Mapping Information
Configuring the MPLS Module • Interface number of the outgoing VLAN • FEC associated with the incoming label If the detail keyword is specified, the following additional information is displayed: • Outgoing port number • Counts of packets and bytes that have been received with the incoming label •...
Page 63: Configuring The Label Distribution Protocol
Configuring the Label Distribution Protocol This chapter describes the Label Distribution Protocol (LDP) and covers the following topics: • Overview of LDP on page 4-1 • Configuring LDP on page 4-3 • Configuration Example on page 4-10 Overview of LDP The Label Distribution Protocol (LDP) is a protocol defined by the IETF for the purpose of establishing an MPLS LSP.
Page 64: Advertising Labels
Configuring the Label Distribution Protocol Hello messages must continue to be received periodically for the hello-adjacency to be maintained. The hold time that specifies the duration for which a hello message remains valid defaults to 15 seconds in the basic discovery mechanism and can be negotiated by the peer LSRs as part of the HELLO exchange.
Page 65: Configuring Ldp
Configuring LDP Configuring LDP This section describes the following tasks: • Configuring LDP on a VLAN on page 4-6 • Configuring LDP Filters on page 4-6 • Configuring LDP Session Timers on page 4-8 • Restoring LDP Session Timers on page 4-9 •...
Page 66 Configuring the Label Distribution Protocol Table 4-1: LDP Configuration Commands Command config mpls [ldp | targeted-ldp] [hello | keep-alive] <hold_time> <interval_time> config mpls add vlan [<name> | all] {ldp} config mpls delete vlan [<name> | all] {ldp} Description Configures LDP session timers. Specify one of the following: ldp —...
Page 67 Table 4-1: LDP Configuration Commands (continued) Command config mpls ldp advertise [add | delete] vlan <name> config mpls ldp advertise [direct | rip | static] [all | none | route-map <route_map>] config mpls vlan [<name> | all] ldp propagate [all | none | route-map <route_map>] MPLS Module Installation and User Guide Description Configures LDP to originate an unsolicited label...
Page 68: Configuring Ldp On A Vlan
Configuring the Label Distribution Protocol Table 4-1: LDP Configuration Commands (continued) Command show mpls ldp {<ipaddress>} {detail} Configuring LDP on a VLAN To configure LDP on a VLAN, use the following command: config mpls add vlan [<name> | all] {ldp} This command enables LDP on one of all VLAN.
Page 69: Configuring An Ldp Label Advertisement Filter
You can configure the propagation filter, as follows: • — All unsolicited label mappings are propagated to the VLAN. This is the default setting. • — No unsolicited label mappings are propagated to the VLAN. none • route-map <route_map> propagation of unsolicited label mappings to the VLAN. The only supported route map match operation keyword is the access_profile parameter of the is associated with each label mapping.
Page 70: Configuring Ldp Session Timers
Configuring the Label Distribution Protocol • — The specified route map is used to permit or deny the route-map <route_map> origination of unsolicited label mappings for all routes of the specified type. The only supported route map match operation keyword is the access_profile parameter of the is associated with each route.
Page 71: Restoring Ldp Session Timers
Configuring LDP The default values are as follows: • ldp hello <hold_time> – 15 • targeted-ldp hello <hold_time> – 45 • ldp hello <interval_time> – 5 • targeted-ldp hello <interval_time> – 15 • ldp keep-alive <hold_time> – 40 • targeted-ldp keep-alive <hold_time> – 60 •...
Page 72 The four switches, labeled LSR 1, LSR 2, LSR 3, and LSR 4, have the same physical hardware configuration. Each switch contains an F48ti module, a G8xi module, an MPLS module, and an MSMi module. The switches are all interconnected via Gigabit...
Page 73 2 module f48t config slot 3 module g8x config slot 7 module mpls The following command sets the maximum jumbo frame size for the switch chassis to 1600: config jumbo-frame size 1600 The following commands create the VLANs:...
Page 74 10 ase-type-1 The following commands configure the OSPF router ID on the switch and enable the distribution of a route for the OSPF router ID in the router LSA. Originating the router ID as a host route allows other routers in the same OSPF area to establish indirect LSPs for external routes to this router: config ospf routerid 11.0.1.11...
Page 75: Configuration Example
Configuring RSVP-TE This chapter describes the Resource Reservation Protocol (RSVP), traffic engineering (TE) extensions to RSVP, and how you configure RSVP-TE using ExtremeWare. This chapter covers the following topics: • RSVP Elements on page 5-2 • Traffic Engineering on page 5-8 •...
Page 76: Rsvp Elements
Configuring RSVP-TE terms of peak data rate, average data rate, burst size, and minimum/maximum packet sizes. RSVP-TE is a set of traffic engineering extensions to RSVP. RSVP-TE extensions enable RSVP to be used for traffic engineering in MPLS environments. The primary extensions add support for assigning MPLS labels and specifying explicit paths as a sequence of loose and strict routes.
Page 77: Path Message
Previous hops Figure 5-1: RSVP Messages In addition to the path and reserve messages, RSVP has the following additional message types: • Path error message • Reservation error message • Path tear message • Reserve tear message • Reservation confirm message Path Message The RSVP path message is used to store state information about each node in the path.
Page 78: Reservation Message
Configuring RSVP-TE Reservation Message Each receiver host transmits an RSVP reservation request to its upstream neighbor. Reservation messages follow the reverse path that the data packets use. The reservation message creates and maintains a reservation state in each node on the path. Reservation messages are eventually delivered to the sender, so that the sender can configure appropriate traffic control parameters for the first hop node.
Page 79: Reservation Tear Message
Reservation Tear Message The reservation tear message deletes the matching reservation state. If there is no matching reservation state, the message is discarded. The reservation tear message can delete any subset of the filter specification in FF-style or SE-style reservation state. Reservation styles are described in Table 5-2.
Page 80: Fixed Filter
This style permits a receiver to specify the set of senders to be included. The Extreme MPLS implementation does not support SE reservation style. Wildcard The wildcard (WF) reservation style uses the shared reservation and wildcard sender options.
Page 81: Bandwidth Accounting
Flowspec is added to the total reserved bandwidth for the appropriate VLANs. LSP path message setup and hold priorities are not used to preempt previously established LSPs established through an Extreme LSR. ExtremeWare does not support SE style labels. Therefore, increasing the reserved bandwidth parameter for an LSP will force the LSP to be torn down.
Page 82: Traffic Engineering
Configuring RSVP-TE as topology changes that alter the routed path for a flow. However, the increased control traffic load can be a scalability concern. For this reason, considerable work has been done towards reducing RSVP refresh overhead through the implementation of RFC 2961, RSVP Overhead Refresh Reduction Extensions.
Page 83: Rsvp Objects
MPLS. Therefore, the layer-3 Protocol ID (PID) value must be set in the Label Request Object, so that the egress node can properly handle the tunneled data. Extreme switches only support the IP PID value (0x0800). To create an RSVP-TE LSP, the sender on the MPLS path creates an RSVP path message and inserts the label request object into the path message.
Page 84: Rsvp Features
Configuring RSVP-TE If any of the above criteria are met, the sender can decide to use the explicit route for some or all of its sessions. To do this, the sender node adds an explicit route object to the path message. After the session has been established, the sender node can dynamically reroute the session (if, for example, if discovers a better route) by changing the explicit route object.
Page 85: Route Recording
LSP to include the advertised downstream label in a label object as part of the RRO. If an Extreme LSR receives a path message with the label recording flag set in the RRO, the LSR does not push a label subobject onto the RRO.
Page 86: Redundant Lsps
Secondary path TE /32 routes remain the preferred route unless a primary path is configured for the LSP, the active secondary path fails, or the active secondary path is deleted. Thus, no switch-back to the original secondary path is performed if the original secondary path fails and is later reestablished.
Page 87: Ping Health Checking
LSP is no longer active. RSVP sessions are torn down if an RSVP refresh message is not received from a neighbor within [(keep-multiplier + 0.5) * 1.5 * refresh-time] seconds.
Page 88: Configuring Rsvp-Te
Configuring RSVP-TE is not enabled. The bundle-time value can be set to any value between zero and 30 (or 3 seconds). Configuring RSVP-TE This section describes the following tasks: • Configuring RSVP-TE on a VLAN on page 5-16 • Configuring RSVP-TE Protocol Parameters on page 5-17 •...
Page 89 Table 5-2: RSVP-TE Configuration Commands (continued) Command config mpls rsvp-te add lsp <lsp_name> path <path_name> {<profile_name>} {primary | secondary} config mpls rsvp-te add path <path_name> [<ipaddress> | <host_name>] {from <local_endpoint_vlan>} config mpls rsvp-te add profile <profile_name> {bandwidth <bps>} {setup-priority <priority>} {hold-priority <priority>} {retry-timeout <seconds>} {hop-count <number>} {ping-interval <seconds>} {metric [<metric>...
Page 90: Configuring Rsvp-Te On A Vlan
Configuring RSVP-TE Table 5-2: RSVP-TE Configuration Commands (continued) Command config mpls rsvp-te profile <profile_name> {bandwidth <bps>} {setup-priority <priority>} {hold-priority <priority>} {retry-timeout <seconds>} {hop-count <number>} {ping-interval <seconds>} {metric [<metric> | igp-tracking} {record [enabled | disabled]} config mpls rsvp-te vlan [<name> | all] {hello-interval <seconds>} {refresh-time <seconds>} {summary-refresh-time <seconds>} {bundle-time <seconds>}...
Page 91: Configuring Rsvp-Te Protocol Parameters
The RSVP-TE keyword RSVP-TE enabled VLANs. hello-interval RSVP hello packet is used by the switch to detect when a RSVP-TE peer is no longer reachable. If an RSVP hello packet is not received from a peer with [hello-interval * keep-multiplier from that peer are torn down.
Page 92: Configuring An Rsvp-Te Path
31 additional alphanumeric characters. Each a routed path to a single IP destination. If the is specified, the DNS client on the switch must be configured so that <host_name> > can first be resolved to an IP address. Alternate routed paths to the <host_name...
Page 93: Configuring An Explicit Route
If the subobject matches a direct router interface or a directly attached subnet, the switch verifies that the path message is received on the matching router interface. If the LSR specified matches the OSPF router ID or a configured loopback IP address, the router interface which the packet is received is ignored.
Page 94: Configuring An Rsvp-Te Profile
Configuring RSVP-TE follows. Thus, the LSP path follows the configured path of the IP prefix with the order value from low to high. If the keyword is not specified, the number value for the order LSR defaults to a value 100 higher than the current highest number value. If the list of IP prefixes, added to the path, does not reflect an actual path through the network topology, the path message is returned with an error from a downstream LSR and the LSP is not established.
Page 95 A default profile is provided are optional parameters indicating the LSP hold-priority parameter is compared to the setup-priority keyword specifies the maximum number of seconds the switch retry-timeout hop-count is used to determine if an established RSVP-TE LSP will actually be Configuring RSVP-TE...
Page 96: Configuring An Existing Rsvp-Te Profile
Configuring RSVP-TE The valid metric values range from 1 to 65535. Specifying the keyword igp-tracking forces the route metric to track the underlying IGP metrics. If no IGP metric exists for the LSP (for example, the LSP traverses a RIP network), the metric is ignored. Tracking IGP metrics is the default behavior.
Page 97: Configuring An Rsvp-Te Lsp
<lsp_name> <path_name> <lsp_name> a character string that is to be used to identify the LSP within the switch. The string must begin with an alphabetic character and can contain up to 31 <lsp_name> additional alphanumeric characters. The is optional. If omitted, the <profile_name>...
Page 98: Displaying Rsvp-Te Lsp Configuration Information
Configuring RSVP-TE All configured primary and secondary paths for the endpoint IP address. For example, three paths can be configured for the but all paths should represent different topological paths through the network to the same LSP endpoint. Adding a secondary <path_name>...
Page 99: Displaying The Rsvp-Te Routed Path
Configuring RSVP-TE Displaying the RSVP-TE Routed Path To display the RSVP-TE routed path, use the following command: show mpls rsvp-te path {<path_name>} {detail} This command displays the configuration and status information for MPLS RSVP-TE routed paths. Information is listed in tabular format and includes the path name, path endpoint LSR IP address, and local VLAN (if configured).
Page 100: Configuration Example
Configuring RSVP-TE Configuration Example RSVP-TE LSPs comprise profiles, paths, and the actual LSP. This section describes how to configure an RSVP-TE LSP. Configuring RSVP LSPs is a multi-step process with some optional steps, depending on the specific requirements of the LSP. Conceptually, a number of mandatory elements must be configured to create an RSVP-TE LSP.
Page 101 The typical steps used to configure and verify an RSVP-TE LSP are as follows: 1 Configure a path (mandatory). 2 Configure a profile (optional). 3 Configure an ERO for a path (optional). 4 Configure a primary/secondary LSP (mandatory). 5 Add a secondary LSP (optional). 6 Verify LSP status (recommended).
Page 102 Configuring RSVP-TE The configuration example, shown in Figure 5-2, creates primary and secondary LSP between the node Glasgow and and the node Birmingham. The steps specifically create an LSP between Glasgow and Birmingham based on an explicitly routed path via London with bandwidth, and setup and hold priority profile requirements.
Page 103 The following commands configure two RSVP-TE LSPs; one is the primary and the other is a secondary or backup LSP. Each LSP uses the same profile but different paths. config mpls rsvp add lsp Glasgow-Birmingham-lsp path Glasgow-Birmingham-pri-path Glasgow-Birmingham-pro primary config mpls rsvp lsp Glasgow-Birmingham-lsp add path Glasgow-Birmingham-sec-path Glasgow-Birmingham-pro secondary The secondary LSP is signaled, however it remains in a standby state unless the primary path becomes unavailable.
Page 104 Configuring RSVP-TE 5-30 MPLS Module Installation and User Guide...
Page 105: Mpls And Ip Routing
MPLS and IP Routing This chapter describes how MPLS and IP routing work together to forward information on your network. This chapter covers the following topics: • Routing Using LSPs on page 6-2 • LSPs and IBGP Next Hops on page 6-5 •...
Page 106: Routing Using Lsps
MPLS and IP Routing Routing Using LSPs This section describes the following topics: • Routing Using Direct and Indirect LSPs on page 6-2 • LSP Precedence and Interaction on page 6-4 • Equal Cost LSPs on page 6-4 • Overriding IBGP Metrics for RSVP-TE LSPs on page 6-5 Routing Using Direct and Indirect LSPs Using MPLS, two types of LSPs can be used to route a packet to its destination: •...
Page 107 For example, in a network where all the LSRs implement this feature (such as an all-Extreme MPLS network), labels only need to be advertised for the direct interfaces of the LSRs. Yet, LSPs can still be used to route traffic destined for non-MPLS domains.
Page 108: Lsp Precedence And Interaction
MPLS and IP Routing problem with using routes summarized by OSPF ABRs is that route summarization can prevent label mappings from being propagated for the links internal to the area being summarized, since a LSR will typically only propagate labels for FECs that exactly match a routing table entry.
Page 109: Overriding Ibgp Metrics For Rsvp-Te Lsps
LSPs and IBGP Next Hops TLS tunnels use a two-label stack to tunnel Layer 2 traffic across an IP MPLS domain. If multiple equal-cost LSPs exist to the egress tunnel LSR, TLS tunnel traffic is distributed across the LSPs using multiple two-label stack MPLS headers. Each two-label stack MPLS header has a different outer label, each outer label representing a different NHLFE, with the same inner label representing the TLS VLAN.
Page 110: Multivendor Support For Indirect Lsps
MPLS and IP Routing Multivendor Support for Indirect LSPs To support the use of indirect LSPs, Extreme LSRs automatically advertise a label mapping for a /32 LSP to its OSPF router ID (configured using the config ospf command). routerid Unfortunately, some MPLS implementations do not support indirect LSPs, and they require that a label mapping be advertised for each FEC.
Page 111 Configuring MPLS Layer-2 VPNs The chapter describes Layer-2 VPN services and the following topics: • Overview of MPLS Layer-2 VPNs on page 7-1 • TLS VPN Characteristics on page 7-5 • Configuring MPLS Layer-2 VPNs on page 7-6 • TLS VPN Configuration Examples on page 7-10 •...
Page 112: Configuring Mpls Layer-2 Vpns
9100. By changing the configured dot1q ethertype value, the Ethernet switch ports treat 8100 tagged traffic as untagged and insert a new dot1q tag with the configured ethertype value. By inserting a new dot1q tag, all traffic received on a single port can be aggregated into a single VLAN and transported across an MPLS domain as a VLAN service.
Page 113: Transporting 802.1Q Tagged Frames
To ensure that the tunnel LSP is established, both an OSPF route and a MPLS label mapping must be advertised for the configured IP address. When the peer LSR is also an Extreme switch, the following options are available for ensuring that an OSPF route is advertised for the tunnel endpoint IP address: •...
Page 114: Lsp Selection
Layer-2 VPN domain. Integrated MAC caching is supported on the MPLS module. This allows the switch to learn MAC addresses of devices that are located on the TLS tunnel egress LER. If the destination MAC address is known, the packet is forwarded into the learned TLS tunnel or onto the local VLAN.
Page 115: Spanning Tree Protocols
MAC addresses to become associated with an incorrect TLS tunnel. To prevent these scenarios from causing lengthy connectivity interruptions, the Extreme switch relearns source MAC addresses on all received packets and withdraws VC labels for the associated TLS tunnels when a local TLS VLAN port goes down.
Page 116: Configuring Mpls Layer-2 Vpns
• VLAN IDs can be different at each end of a TLS tunnel, the VLAN ID is set by the egress switch to match that of the locally configured VLAN. • Support for full-mesh and hub-and-spoke VPN architectures with an integrated 256k tunnel MAC cache.
Page 117 Configuring MPLS Layer-2 VPNs Description Adds a TLS tunnel. Specify the following: <tunnel_name> — Used to identify the TLS tunnel within the switch. [lsp <lsp_name> | <ipaddress> | <host_name>] — Identifies the peer LSR that is the tunnel endpoint. The DNS client must be configured to use the <host_name>.
Page 118: Adding A Tls Tunnel
This IP address should be configured with a 32-bit prefix on the peer LSR. When the peer LSR is also an Extreme switch, either OSPF must also be enabled on the VLAN to which the IP address is assigned (using the...
Page 119: Deleting A Tls Tunnel
MPLS header of Layer-2 frames forwarded onto the tunnel LSP by this switch, and must be meaningful to the peer TLS node. All traffic received from the tunnel LSP that contains the forwarded to the local VLAN identified by the...
Page 120: Displaying Tls Configuration Information
Configuring MPLS Layer-2 VPNs tunnel and the local TLS VLAN are treated as separate bridge ports within a single layer 2 broadcast domain. When the mode is configured as received broadcast and unknown unicast packets are flooded out every port, except for the port on which the packet was received.
Page 121: Basic Mpls Tls Configuration Example
Basic MPLS TLS Configuration Example This MPLS TLS network configuration shown in Figure 7-1, is based on the routed MPLS network configuration example, shown in Figure 4-1. 9.9.9.0/24 LSR 1 Router ID =11.0.1.11 Figure 7-1: MPLS TLS configuration example In this configuration example, a new VLAN, unc-wilmington, is configured on LSR 4, with a router interface of 9.9.9.1/24.
Page 122: Full Mesh Tls Configuration
Configuring MPLS Layer-2 VPNs The following command creates a TLS tunnel to the 11.0.1.11 network for traffic originating from VLAN unc-wilmington: config mpls add tls-tunnel rt40 11.0.1.11 unc-wilmington tls-labels 8f004 8f001 Full Mesh TLS Configuration The example, shown in Figure 7-2, configures a four-node full-mesh MPLS TLS configuration.
Page 123: Mpls1
TLS VPN Configuration Examples mpls1 The following command configures the VPN VLAN ncsu for mesh mode. This instructs the LER to not flood packets received from a TLS tunnel onto any other TLS tunnel. config mpls tls-tunnel ncsu mode mesh Each of the following commands configure a TLS tunnel to an LER for which the VLAN ncsu has a PoP.
Page 124: Hub And Spoke Tls Configuration
Configuring MPLS Layer-2 VPNs Hub and Spoke TLS Configuration The following example, shown in Figure 7-3 , configures a four-node hub-and-spoke MPLS TLS configuration. The hub LER MPLS configuration includes a TLS tunnel to every other LER. Each spoke LER MPLS configuration includes a TLS tunnel to only the hub LER.
Page 125: Mpls1
MPLS domain. If an OC-3 or OC-12 SONET module is installed in the BlackDiamond chassis, PPP traffic received on a SONET port that is a member of a TLS VLAN is transparently transported across the MPLS domain to the destination switch to be transmitted out of a matching SONET interface.
Page 126 Configuring MPLS Layer-2 VPNs OC-3 SONET LSR 1 Router ID = 11.0.1.11 Figure 7-4: TLS configuration example using PPP transparent mode The configuration commands for this example follow. The following command configures the OC-3 module for slot 1: configure slot 1 module oc3 The following command creates the VLAN that is used to configure the TLS tunnel for transparently transporting PPP traffic: create vlan sonet...
Page 127: Using Esrp With Mpls Tls
Using ESRP with MPLS TLS The following commands disable BCP mode and enable POS transparent mode on the OC-3 interface that is a member of the TLS VLAN: config ppp bcp off port 1:1 config ppp pos transparent-mode on port 1:1 The following command creates the TLS tunnel to LSR 4 for SONET PPP traffic received on VLAN sonet: config mpls add tls-tunnel sonet 11.0.4.11 tls-vlan 8f002 8f005...
Page 128: Tunnel Endpoint Vlans
Configuring MPLS Layer-2 VPNs ESRP is run over the Ethernet VLAN connecting the two hub-LSRs, and the redundant IP address configured for ESRP is also being used as the tunnel endpoint address. Using this configuration, the LSRs at the spoke sites automatically connect to the active hub-LSR and rapidly adapt to failures.
Page 129 CUSTOMER SITE 1 LSR A ESRP master Active Tunnel LSPs LSR C ESRP master CUSTOMER SITE 2 Figure 7-6: Tunnel endpoint VLANs In Figure 7-6, redundant LSRs are installed at both ends of a TLS tunnel. This example takes advantage of the IP multinetting feature in ExtremeWare by creating an overlay tunnel endpoint VLAN that shares the same Ethernet ports as the user VLAN that is extended across the MPLS backbone network.
Page 130 Configuring MPLS Layer-2 VPNs on the user VLAN ensures that only one LSR (the ESRP master) forwards traffic for the VLAN at each site. The redundant IP address configured on the tunnel endpoint VLAN (IP ) is also used as the tunnel endpoint address in the same manner as described for the preceding example.
Page 131: Lsp Tracking
ESRP to track add track-lsp up to eight LSPs. Fail over to the slave switch is based on the total number of established tracked LSPs. The switch with the greatest number of established tracked LSPs is elected the master switch for the specified VLAN. Specifying the parameter <...
Page 132: Configuration Example
Configuring MPLS Layer-2 VPNs Configuration Example The MPLS TLS ESRP configuration example, shown in Figure 7-7, illustrates how to configure a pair of BlackDiamond switches to provide redundant Layer-2 VPN services over an MPLS domain. Two additional switches have been added to the TLS MPLS network configuration example shown in Figure 7-1, LSR 5 and LSR 6.
Page 133 The following command enables ESRP and VLAN mplsesrp and unc: enable esrp vlan unc The following command creates a TLS tunnel from VLAN unc to the master switch providing connectivity for VLAN unc-wilmington: config mpls add tls-tunnel rt40 10.10.10.2 unc tls-labels 8f001 8f004 From an ESRP perspective, LSR 5 is configured identically as LSR 1.
Page 134 Configuring MPLS Layer-2 VPNs 7-24 MPLS Module Installation and User Guide...
Page 135: Configuring Destination-Sensitive Accounting
Configuring Destination-Sensitive Accounting This chapter covers the following topics: • Overview of Destination-Sensitive Accounting on page 8-1 • Basic Accounting Configuration Information on page 8-2 • Configuring Access Profiles on page 8-3 • Configuring Route Maps on page 8-9 • Retrieving Accounting Statistics on page 8-18 Overview of Destination-Sensitive Accounting Destination-sensitive accounting collects statistics that are maintained for forwarded IP traffic to support billing on a destination basis.
Page 136: Basic Accounting Configuration Information
Configuring Destination-Sensitive Accounting and the column index being a bin number. Thus, when an IP frame is forwarded, the input VLAN ID selects the row and the bin number from the forwarding database entry selects the column. The use of input VLAN ID enables billing statistics to be maintained on a per customer basis where the VLAN ID identifies the customer.
Page 137: Configuring Access Profiles
Configuring Access Profiles Configuring Access Profiles Destination-sensitive significance is assigned to specific accounting bin numbers through ExtremeWare commands. To configure accounting route map access route-map policies, it may be necessary to define an access profile. This section describes commands used to configure access profiles for MPLS modules. This section provides information on the following topics: •...
Page 138 Configuring Destination-Sensitive Accounting Table 8-2: Routing Access Policy Configuration Commands Command config access-profile <access_profile> add {<seq-number>} {permit | deny} [ipaddress <ipaddress> <mask> {exact} | as-path <path_expression> | bgp-community [internet | no-advertise | no-export | no-export-subconfed | <as_no:number> | number <community]] config access-profile <access_profile>...
Page 139: Creating An Access Profile
— A list of IP addresses and mask pairs. as-path — A list of AS path expressions. bgp-community — A list of BGP community numbers. Deletes an access profile. Displays access-profile related information for the switch. Configuring Access Profiles and is defined cold...
Page 140: Configuring An Access Profile Mode
Configuring Destination-Sensitive Accounting Configuring an Access Profile Mode After the access profile is created, you must configure the access profile mode. The access profile mode determines whether the items in the list are to be permitted access or denied access. Three access profile modes are available: •...
Page 141: Specifying Subnet Masks
Configuring Access Profiles Specifying Subnet Masks The subnet mask specified in the access profile command is interpreted as a prefix mask. A prefix mask indicates the bits that are significant in the IP address. In other words, a prefix mask specifies the part of the address that must match the IP address to which the profile is applied.
Page 142: Autonomous System Expressions
Configuring Destination-Sensitive Accounting Autonomous System Expressions keyword uses a regular expression string to match against the AS path. AS-path Regular expression notation can include any of the characteristics listed in Table 8-3. Table 8-3: Regular Expression Notation Character Definition Specifies a range of numbers to be matched. Matches any number.
Page 143: Configuring Route Maps
Configuring Route Maps Route maps are used to conditionally assign accounting bin numbers to route destinations. Route maps are used in conjunction with the match and set operations. A match operation specifies a criteria that must be matched. A set operation specifies a change that is made to the route when the match operation is successful.
Page 144 Configuring Destination-Sensitive Accounting Table 8-4: Route Map Commands (continued) Command config route-map <route-map> <sequence number> add match [nlri-list <access_profile> | as-path [<access_profile> | <as_no> | community [access-profile <access_profile> | <as_num:number : number <community>] | next-hop <ipaddress> | med <number> | origin [igp | egp | incomplete]] config route-map <route-map>...
Page 145: Creating A Route Map
Creating a Route Map To create a route map, use the following command: create route-map <route-map> Adding Entries to the Route Map To add entries to the route map, use the following command: config route-map <route-map> add <sequence number> [permit | deny] {match-one | match-all} Where the following is true: •...
Page 146 Configuring Destination-Sensitive Accounting Where the following is true: • The is the name of the route map. route-map • The identifies the entry in the route map to which this statement sequence number is being added. • The , and match goto an entry, the statements are sequenced in the order of their operation.
Page 147: Route Map Operation
Route Map Operation The entries in the route map are processed in the ascending order of the sequence number. Within the entry, the match statements are processed first. When the match operation is successful, the set and goto statements within the entry are processed, and the action associated with the entry is either applied, or else the next entry is processed.
Page 148: Configuring Destination-Sensitive Accounting Based On Destination Ip Subnets
Figure 8-1: Destination-sensitive accounting based on destination IP subnets In this example, all IP unicast traffic is forwarded by the BlackDiamond switch to one of three IP subnets. Each IP subnet is mapped to a different accounting bin. The steps that follow describe how to configure the accounting feature.
Page 149: Configuring Destination-Sensitive Accounting Based On Bgp Community Strings
create access-profile arm2 type ipaddress config access-profile arm2 mode none config access-profile arm2 add 10 permit ipaddress 192.168.101.0/24 create access-profile arm3 type ipaddress config access-profile arm3 mode none config access-profile arm3 add 10 permit ipaddress 192.168.102.0/24 2 Create a route map named ip_example. create route-map ip_example config route-map ip_example add 100 permit match-one config route-map ip_example 100 add match nlri-list arm1...
Page 150 64-bit packet Figure 8-2: Destination-sensitive accounting based on BGP community strings In this example, all IP unicast traffic forwarded by the BlackDiamond switch to one of two BGP communities is counted. Each IP subnet associated with the configured BGP community is mapped to a different accounting bin. The steps that follow describe how to configure the accounting feature.
Page 151: Applying The Route Map To The Ip Routing Table
2 Apply the route map to the e-bgp routes. config iproute route-map e-bgp bgp_example Applying the Route Map to the IP Routing Table To configure how the specified route map is applied to IP routing table entries, use the following command: config iproute route-map [ospf-intra | ospf-inter | ospf-extern1 | ospf-extern2 | ospf | rip | static | e-gbp | i-bgp | direct] <route-map>...
Page 152: Retrieving Accounting Statistics
Configuring Destination-Sensitive Accounting Retrieving Accounting Statistics Accounting statistics are used to bill your customers. Destination-sensitive accounting gives you the flexibility to bill your customers at predetermined and different rates. For a given set of counts, the source VLAN ID identifies the customer and the accounting bin number corresponds to a billing rate.
Page 153 See the ExtremeWare Software User Guide for more information related to configuring SNMP. See your SNMP Manager documentation for information on how to load MIBs for use within the network manager. MPLS Module Installation and User Guide Retrieving Accounting Statistics 8-19...
Page 154 Configuring Destination-Sensitive Accounting 8-20 MPLS Module Installation and User Guide...
Page 155 MPLS module that is not covered in previous chapters of this document. This chapter covers the following topics: • General Switch Attributes on page 9-2 • Image and Configuration Attributes on page 9-4 • 802.1p and 802.1Q Commands on page 9-4 •...
Page 156: Additional Mpls Module Support Topics
General Switch Attributes Except as described below, the MPLS module supports all of the general ExtremeWare switch commands. Table 9-1 describes the changes to existing ExtremeWare general switch commands to support the MPLS module. Table 9-1: Changes to General Switch Commands...
Page 157 Table 9-1: Changes to General Switch Commands (continued) Command show diag backplane utilization show diagnostics {<slot>} show diag slot <slot_number> fdb {<mac_address> | vlan <name> | tls-tunnel <tunnel_name>} show diag slot <slot_number> iproute show diag slot <slot_number> mpls show slot <slot>...
Page 158: Image And Configuration Attributes
Additional MPLS Module Support Topics Table 9-1: Changes to General Switch Commands (continued) Command unconfig switch {all} Image and Configuration Attributes Except as described below, the MPLS module supports all of the ExtremeWare commands associated with managing image and configuration attributes. See the “Software Upgrade and Boot Options”...
Page 159: Vlan Commands
VLAN Commands Most of the VLAN commands are not directly applicable to the MPLS module. The two exceptions are: • The show vlan or disabled on the VLAN. • Implementations of the commands have been augmented to support the MPLS module. ipaddress All frames received and transmitted by the MPLS module include a VLAN tag.
Page 160: Show Ipconfig Command
Additional MPLS Module Support Topics • show iproute {priority | vlan <vlan> | permanent | <ipaddress> <netmask> | route-map | origin [direct | static | blackhole | rip | bootp | icmp | ospf-intra | ospf-inter | ospf-as-external | ospf-extern1 | ospf-extern2]} {sorted} show ipconfig Command The output of the show ipconfig...
Page 161: Icmp Commands
show iproute table entry. The modified syntax of the show iproute {priority | vlan <name> | permanent | <ipaddress> <mask> | origin [direct | static | blackhole | rip | bootp | icmp | ospf-intra | ospf-inter | ospf-as-external | ospf-extern1 | ospf-extern2 | te] | route-map <route_map>...
Page 162: Ospf Commands
Additional MPLS Module Support Topics OSPF Commands The commands described in Table 9-3 have been added to control whether a route for the OSPF router ID is distributed by OSPF. Table 9-3: New OSPF Commands Command enable ospf originate-router-id disable ospf originate-router-id The implementation of the config ospf routerid support automatic advertisement of a label mapping for the OSPF router ID.
Page 163: Ppp Commands
This command configures which LSPs should be used by ESRP to track for determining the ESRP state of the specified VLAN. The track up to eight LSPs. Fail over to the slave switch is based on the total number of established tracked LSPs. The switch with the greatest number of established tracked LSPs is elected the master switch for the specified vlan name.
Page 164: Layer-2 And Layer-3 Switching Attributes
The MPLS module relies on the MSM switch fabric to support the layer-2 switching functions. If MPLS is enabled, the switch fabric hardware does not perform layer-3 switching for any protocols. The MPLS module performs layer-3 forwarding for IP. All of the IP routing protocols are supported: RIP, OSPF, BGP, DVMRP, PIM.
Page 165 • Spanning Tree Protocol (STP) • RMON • Access list The MPLS module relies on the ingress switch fabric to support access list functions. Thus, access list functions are not applicable to MPLS-encapsulated packets. • IGMP snooping OSPF and LDP session establishment require the MSM to receive and process IP multicast frames.
Page 166 Additional MPLS Module Support Topics 9-12 MPLS Module Installation and User Guide...
Page 167 “Supported Standards” appendix in the ExtremeWare Software User Guide . Standards Supported for MPLS The Extreme Networks MPLS implementation complies with the following standards: • RFC 2212 — Specification of Guaranteed Quality of Service • RFC 2961 — RSVP Overhead Refresh Reduction Extensions •...
Page 168 MIBs Supported for MPLS The initial Extreme MPLS implementation provides read-only (GET but not SET) support for a subset of the MPLS LSR MIB, as defined in the Internet Draft draft-ietf-mpls-lsr-mib-07.txt, and a subset of the MPLS LDP MIB, as defined in the Internet Draft draft-ietf-mpls-ldp-mib-07.txt.
Page 169 AS path expression notations (table) Autonomous System Expressions. See AS path MPLS Module Installation and User Guide 7-2, 7-3 BCP and TLS BGP Next Hop binding labels, description of BlackDiamond switch I/O modules overview slot preconfiguration configuring accounting bins label advertisement filters...
Page 170 TLS configuration example (figure) failover redundancy route table tracking tunnel endpoint VLAN EXP field explicit route Extreme Standby Routing Protocol. See ESRP ExtremeWare base version identifier technology release versions failover, ESRP failover, RSVP features destination-sensitive accounting IP unicast forwarding...
Page 171 NULL label, advertising popping propagating remotely assigned retention modes space partitioning swapping label-switch forwarding algorithms layer-3 switching advertising label mappings in TLS configuration commands (table) configuring filters definition of hello-adjacency message exchange neighbor discovery protocol propagation filters...
Page 172 ordered LSP control OSPF MPLS domain new commands (table) SFP algorithm SPF recalculation path error message path message path tear message Penultimate Hop Popping. See PHP configuring definition of implicit NULL labels port commands power-related problems propagating labels and RSVP configuring mapping DiffServ model displaying mapping information...
Page 173 (table) switching, layer-3 technology release version identifier 802.1Q encapsulation advertising label mappings and BCP and ESRP and LSPs basic configuration example (figure)
Page 174 vi - Index MPLS Module Installation and User Guide...
Page 175: Index Of Commands
Index of Commands clear accounting counters clear counters clear fdb clear slot config access-profile add config access-profile delete config access-profile mode config debug-trace mpls config debut-trace mpls-signalling config dot1p type config dot1q ethertype config fdb agingtime config ip-mtu vlan config iproute route-map config iproute-map config jumbo-frame size config mpls...
Page 176 3-13 show vlan 2-2, 2-12, 9-4 unconfig icmp unconfig mpls unconfig mpls qos-mapping unconfig slot unconfig switch unconfig vlan ipaddress use image 3-13, 3-15 9-5, 9-6 2-13, 9-2 8-2, 8-15, 8-18 2-13 9-5, 9-6 8-15...

This manual is also suitable for:

Blackdiamond 6800 series

Extreme Networks BlackDiamond 6800 MPLS Installation And User Manual

Preface

Introduction

Conventions

Related Publications

1 Overview

Summary of Features

MPLS Module Physical Description

Blackdiamond 6800 Series Switch Overview

About the MPLS Module

About MPLS

About MPLS Layer-2 Vpns

About IP Unicast Forwarding

About Destination-Sensitive Accounting

2 Installing or Replacing an MPLS Module

Preparing for Installation

Inserting and Securing a Module

Verifying the Module Installation

Troubleshooting

Removing and Replacing an MPLS Module

3 Configuring the MPLS Module

Overview of MPLS

MPLS Layer

Configuring MPLS

4 Configuring the Label Distribution Protocol

Overview of LDP

Configuring LDP

5 Configuring RSVP-TE

Configuration Example

RSVP Elements

Traffic Engineering

RSVP Features

Configuring RSVP-TE

Configuration Example

6 MPLS and IP Routing

Routing Using Lsps

Lsps and IBGP Next Hops

Optimized Forwarding of Non-MPLS IP Traffic

7 Configuring MPLS Layer-2 Vpns

TLS VPN Characteristics

Configuring MPLS Layer-2 Vpns

TLS VPN Configuration Examples

Using ESRP with MPLS TLS

8 Configuring Destination-Sensitive Accounting

Overview of Destination-Sensitive Accounting

Basic Accounting Configuration Information

Configuring Access Profiles

Configuring Route Maps

Retrieving Accounting Statistics

9 Additional MPLS Module Support Topics

General Switch Attributes

Image and Configuration Attributes

VLAN Commands

FDB Commands

Basic IP Commands

ICMP Commands

IP Multicast and Flow Redirection Commands

OSPF Commands

BGP Commands

Route Map Commands

PPP Commands

ESRP and VRRP Commands

Layer-2 and Layer-3 Switching Attributes

Debug Trace Commands

Attributes Not Directly Applicable to the MPLS Module

Quick Links

Related Manuals for Extreme Networks BlackDiamond 6800 MPLS

Summary of Contents for Extreme Networks BlackDiamond 6800 MPLS