Configuring the ATM SPAs

Transcription

1 CHAPTER 7 This chapter provides information about configuring the ATM SPAs on the Catalyst 6500 Series switch. It includes the following sections:, page 7-1 Verifying the Interface Configuration, page 7-61 Configuration Examples, page 7-63 For information about managing your system images and configuration files, refer to the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2 and Cisco IOS Configuration Fundamentals Reference, Release 12.2 publications. For more information about the commands used in this chapter, see the Catalyst 6500 Series Cisco IOS Reference, 12.2SX publication. Also refer to the related Cisco IOS Release 12.2 software command reference and master index publications. For more information about accessing these publications, see the Related Documentation section on page xlv. This section describes the most common configurations for the ATM SPAs on a Catalyst 6500 Series switch. It contains procedures for the following configurations: Required, page 7-2 Specifying the Interface Address on a SPA, page 7-3 Modifying the Interface MTU Size, page 7-3 Creating a Permanent Virtual Circuit, page 7-6 Creating a PVC on a Point-to-Point Subinterface, page 7-8 Configuring a PVC on a Multipoint Subinterface, page 7-10 Configuring RFC 1483 Bridging for PVCs, page 7-12 Configuring RFC 1483 Bridging for PVCs with IEEE 802.1Q Tunneling, page 7-15 Configuring ATM RFC 1483 Half-Bridging, page 7-17 Configuring ATM Routed Bridge Encapsulation, page 7-20 Configuring RFC 1483 Bridging of Routed Encapsulations, page 7-22 Configuring MPLS over RBE, page 7-25 Configuring Aggregate WRED for PVCs, page

2 Creating and Configuring Switched Virtual Circuits, page 7-33 Configuring Traffic Parameters for PVCs or SVCs, page 7-37 Configuring Virtual Circuit Classes, page 7-40 Configuring Virtual Circuit Bundles, page 7-42 Configuring Multi-VLAN to VC Support, page 7-45 Configuring Link Fragmentation and Interleaving with Virtual Templates, page 7-45 Configuring the Distributed Compressed Real-Time Protocol, page 7-48 Configuring Automatic Protection Switching, page 7-50 Configuring SONET and SDH Framing, page 7-56 Configuring for Transmit-Only Mode, page 7-57 Saving the Configuration, page 7-58 Shutting Down and Restarting an Interface on a SPA, page 7-58 Shutting Down an ATM Shared Port Adapter, page 7-60 Required The ATM SPA interface must be initially configured with an IP address to allow further configuration. Some of the required configuration commands implement default values that might or might not be appropriate for your network. If the default value is correct for your network, then you do not need to configure the command. To perform the basic configuration of each interface, perform this task beginning in global configuration mode: Step 1 Router(config)# interface atm slot/subslot/port Enters interface configuration mode for the indicated port on the specified ATM SPA. Step 2 Router(config-if)# ip address address mask [secondary] (Optional in some configurations) Assigns the specified IP address and subnet mask to the interface. Repeat the command with the optional secondary keyword to assign additional, secondary IP addresses to the port. Step 3 Router(config-if)# description string (Optional) Assigns an arbitrary string, up to 80 characters long, to the interface. This string can identify the purpose or owner of the interface, or any other information that might be useful for monitoring and troubleshooting. Step 4 Router(config-if)# no shutdown Enables the interface. Repeat Step 1 through Step 4 for each port on the ATM SPA to be configured. Step 5 Router(config-if)# end Exits interface configuration mode and returns to privileged EXEC mode. 7-2

3 Specifying the Interface Address on a SPA Two ATM SPAs can be installed in a SIP. SPA interface ports begin numbering with 0 from left to right. Single-port SPAs use only the port number 0. To configure or monitor SPA interfaces, you need to specify the physical location of the SIP, SPA, and interface in the CLI. The interface address format is slot/subslot/port, where: slot Specifies the chassis slot number in the Catalyst 6500 Series switch where the SIP is installed. subslot Specifies the secondary slot of the SIP where the SPA is installed. port Specifies the number of the individual interface port on a SPA. The following example shows how to specify the first interface (0) on a SPA installed in the first subslot of a SIP (0) installed in chassis slot 3: Router(config)# interface serial 3/0/0 This command shows a serial SPA as a representative example, however the same slot/subslot/port format is similarly used for other SPAs (such as ATM and POS) and other non-channelized SPAs. For more information about identifying slots and subslots, see the Identifying Slots and Subslots for SIPs, SSCs, and SPAs section on page 4-2. Modifying the Interface MTU Size The maximum transmission unit (MTU) values might need to be reconfigured from their defaults on the ATM SPAs to match the values used in your network. Interface MTU Configuration Guidelines When configuring the interface MTU size on an ATM SPA, consider the following guidelines. The Cisco IOS software supports several types of configurable MTU options at different levels of the protocol stack. You should ensure that all MTU values are consistent to avoid unnecessary fragmentation of packets. These MTU values are the following: Interface MTU Configured on a per-interface basis and defines the maximum packet size (in bytes) that is allowed for traffic received on the network. The ATM SPA checks traffic coming in from the network and drops packets that are larger than this maximum value. Because different types of Layer 2 interfaces support different MTU values, choose a value that supports the maximum possible packet size that is possible in your particular network topology. IP MTU Configured on a per-interface or per-subinterface basis and determines the largest maximum IP packet size (in bytes) that is allowed on the IP network without being fragmented. If an IP packet is larger than the IP MTU value, the ATM SPA fragments it into smaller IP packets before forwarding it on to the next hop. Multiprotocol Label Switching (MPLS) MTU Configured on a per-interface or per-subinterface basis and defines the MTU value for packets that are tagged with MPLS labels or tag headers. When an IP packet that contains MPLS labels is larger than the MPLS MTU value, the ATM SPA fragments it into smaller IP packets. When a non-ip packet that contains MPLS labels is larger than the MPLS MTU value, the ATM SPA drops it. 7-3

4 All devices on a particular physical medium must have the same MPLS MTU value to allow proper MPLS operation. Because MPLS labels are added on to the existing packet and increase the packet s size, choose appropriate MTU values so as to avoid unnecessarily fragmenting MPLS-labeled packets. If the IP MTU or MPLS MTU values are currently the same size as the interface MTU, changing the interface MTU size also automatically sets the IP MTU or MPLS MTU values to the new value. Changing the interface MTU value does not affect the IP MTU or MPLS MTU values if they are not currently set to the same size as the interface MTU. Different encapsulation methods and the number of MPLS MTU labels add additional overhead to a packet. For example, SNAP encapsulation adds an 8-byte header, IEEE 802.1Q encapsulation adds a 2-byte header, and each MPLS label adds a 4-byte header. Consider the maximum possible encapsulations and labels that are to be used in your network when choosing the MTU values. Tip The MTU values on the local ATM SPA interfaces must match the values being used in the ATM network and remote ATM interface. Changing the MTU values on an ATM SPA does not reset the local interface, but be aware that other platforms and ATM SPAs do reset the link when the MTU value changes. This could cause a momentary interruption in service, so we recommend changing the MTU value only when the interface is not being used. The interface MTU value on the ATM SPA also determines which packets are recorded as giants in the show interfaces atm command. The interface considers a packet to be a giant packet when it is more than 24 bytes larger than the interface MTU size. For example, if using an MTU size of 1500 bytes, the interface increments the giants counter when it receives a packet larger than 1524 bytes. Interface MTU Configuration Task To change the MTU values on the ATM SPA interfaces, perform this task beginning in global configuration mode: Step 1 Router(config)# interface atm slot/subslot/port Enters interface configuration mode for the indicated port on the specified ATM SPA. Step 2 Router(config-if)# mtu bytes (Optional) Configure the maximum transmission unit (MTU) size for the interface. The valid range for bytes is from 64 to 9216 bytes, with a default of 4470 bytes. As a general rule, do not change the MTU value unless you have a specific application need to do so. If the IP MTU or MPLS MTU values are currently the same size as the interface MTU, changing the interface MTU size also automatically sets the IP MTU or MPLS MTU values to the same value. Step 3 Router(config-if)# ip mtu bytes (Optional) Configures the MTU value, in bytes, for IP packets on this interface. The valid range for an ATM SPA is 64 to 9288, with a default value equal to the MTU value configured in Step

5 Step 4 Router(config-if)# mpls mtu bytes (Optional) Configures the MTU value, in bytes, for MPLS-labeled packets on this interface. The valid range for an ATM SPA is 64 to 9216 bytes, with a default value equal to the MTU value configured in Step 2. Verifying the MTU Size Repeat Step 1 through Step 4 for each interface port on the ATM SPA to be configured. Step 5 Router(config-if)# end Exits interface configuration mode and returns to privileged EXEC mode. To verify the MTU sizes for an interface, use the show interface, show ip interface, and show mpls interface commands, as in the following example: Router# show interface atm 4/1/0 ATM4/1/0 is up, line protocol is up Hardware is SPA-4XOC3-ATM, address is 000d.2959.d5ca (bia 000d.2959.d5ca) MTU 4470 bytes, sub MTU 4470, BW Kbit, DLY 80 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ATM, loopback not set Encapsulation(s): AAL maximum active VCs, 0 current VCCs VC idle disconnect time: 300 seconds 0 carrier transitions Last input never, output never, output hang never Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue: 0/0 (size/max) 30 second input rate 0 bits/sec, 0 packets/sec 30 second output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 output buffer failures, 0 output buffers swapped out Router# show ip interface atm 4/1/0 ATM4/1/0 is up, line protocol is up Internet address is /24 Broadcast address is Address determined by non-volatile memory MTU is 4470 bytes Helper address is not set Directed broadcast forwarding is disabled Multicast reserved groups joined: Outgoing access list is not set Inbound access list is not set Proxy ARP is enabled Security level is default Split horizon is enabled ICMP redirects are always sent ICMP unreachables are always sent ICMP mask replies are never sent IP fast switching is enabled IP fast switching on the same interface is disabled 7-5

6 IP Flow switching is disabled IP Feature Fast switching turbo vector IP Null turbo vector VPN Routing/Forwarding "vpn2600-2" IP multicast fast switching is enabled IP multicast distributed fast switching is disabled IP route-cache flags are Fast, CEF Router Discovery is disabled IP output packet accounting is disabled IP access violation accounting is disabled TCP/IP header compression is disabled RTP/IP header compression is disabled Probe proxy name replies are disabled Policy routing is disabled Network address translation is disabled WCCP Redirect outbound is disabled WCCP Redirect exclude is disabled BGP Policy Mapping is disabled Router# show mpls interface atm 4/1/0 detail Interface ATM3/0: IP labeling enabled (ldp) LSP Tunnel labeling not enabled MPLS operational MPLS turbo vector MTU = 4470 ATM labels: Label VPI = 1 Label VCI range = Control VC = 0/32 To view the maximum possible size for datagrams passing out the interface using the configured MTU value, use the show atm interface atm command: Router# show atm interface atm 4/1/0 Interface ATM4/1/0: AAL enabled: AAL5, Maximum VCs: 4096, Current VCCs: 2 Maximum Transmit Channels: 0 Max. Datagram Size: 4528 PLIM Type: SONET Kbps, TX clocking: LINE Cell-payload scrambling: ON sts-stream scrambling: ON 8359 input, 8495 output, 0 IN fast, 0 OUT fast, 0 out drop Avail bw = Config. is ACTIVE Creating a Permanent Virtual Circuit To use a permanent virtual circuit (PVC), configure the PVC in both the switch and the ATM switch. PVCs remain active until the circuit is removed from either configuration. To create a PVC on the ATM interface and enter interface ATM VC configuration mode, perform this task beginning in global configuration mode: 7-6

7 Step 1 Router(config)# interface atm slot/subslot/port or Router(config)# interface atm slot/subslot/port.subinterface Enters interface or subinterface configuration mode for the indicated port on the specified ATM SPA. Step 2 Router(config-if)# ip address address mask Assigns the specified IP address and subnet mask to the interface or subinterface. Step 3 Router(config-if)# atm tx-latency milliseconds (Optional) Configures the default transmit latency for VCs on this ATM SPA interface. The valid range for milliseconds is from 1 to 200, with a default of 100 milliseconds. Step 4 Router(config-if)# pvc [name] vpi/vci [ilmi qsaal] Step 5 Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are: vpi Specifies the VPI ID. The valid range is 0 to 255. vci Specifies the VCI ID. The valid range is 1 to Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC. You can also configure the following options: name (Optional) An arbitrary string that identifies this PVC. ilmi (Optional) Configures the VC to exclusively carry ILMI protocol traffic (default). qsaal (Optional) Configures the VC to exclusively carry qsaal protocol traffic. When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC s configuration and automatically switches to its parent subinterface. Router(config-if-atm-vc)# protocol protocol {protocol-address inarp} [[no] broadcast] Configures the PVC for a particular protocol and maps it to a specific protocol-address. protocol Typically set to either ip or ppp, but other values are possible. protocol-address Destination address or virtual interface template for this PVC (if appropriate for the protocol). inarp Specifies that the PVC uses Inverse ARP to determine its address. [no] broadcast (Optional) Specifies that this mapping should (or should not) be used for broadcast packets. Step 6 Router(config-if-atm-vc)# inarp minutes (Optional) If using Inverse ARP, configures how often the PVC transmits Inverse ARP requests to confirm its address mapping. The valid range is 1 to 60 minutes, with a default of 15 minutes. Step 7 Router(config-if-atm-vc)# encapsulation aal5snap (Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap. 7-7

8 Step 8 Router(config-if-atm-vc)# tx-limit buffers (Optional) Specifies the number of transmit buffers for this VC. The valid range is from 1 to 57343, with a default value that is based on the current VC line rate and on the latency value that is configured with the atm tx-latency command. Repeat Step 4 through Step 8 for each PVC to be configured on this interface. Step 9 Router(config-if-atm-vc)# end Exits ATM VC configuration mode and returns to privileged EXEC mode. Verifying a PVC Configuration To verify the configuration of a particular PVC, use the show atm pvc command: Router# show atm pvc 1/100 ATM3/0/0: VCD: 1, VPI: 1, VCI: 100 UBR, PeakRate: AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0 OAM frequency: 0 second(s), OAM retry frequency: 1 second(s) OAM up retry count: 3, OAM down retry count: 5 OAM Loopback status: OAM Disabled OAM VC status: Not Managed ILMI VC status: Not Managed InARP frequency: 15 minutes(s) Transmit priority 6 InPkts: , OutPkts: , InBytes: , OutBytes: InPRoc: 1, OutPRoc: 1, Broadcasts: 0 InFast: 0, OutFast: 0, InAS: , OutAS: InPktDrops: 0, OutPktDrops: 0 CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0 Out CLP=1 Pkts: 0 OAM cells received: 0 F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0 F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0 OAM cells sent: 0 F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0 F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0 OAM cell drops: 0 Status: UP VC 1/100 doesn't exist on 7 of 8 ATM interface(s) Tip To verify the configuration and current status of all PVCs on a particular interface, you can also use the show atm vc interface atm command. Creating a PVC on a Point-to-Point Subinterface Use point-to-point subinterfaces to provide each pair of switches with its own subnet. When you create a PVC on a point-to-point subinterface, the switch assumes it is the only point-to-point PVC that is configured on the subinterface, and it forwards all IP packets with a destination IP address in the same subnet to this VC. To configure a point-to-point PVC, perform this task beginning in global configuration mode: 7-8

9 Step 1 Router(config)# interface atm slot/subslot/port.subinterface point-to-point Creates the specified point-to-point subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode. Step 2 Router(config-subif)# ip address address mask Assigns the specified IP address and subnet mask to this subinterface. Step 3 Step 4 Step 5 Router(config-subif)# pvc [name] vpi/vci [ilmi qsaal] Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are: vpi Specifies the VPI ID. The valid range is 0 to 255. vci Specifies the VCI ID. The valid range is 1 to Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC. You can also configure the following options: name (Optional) An arbitrary string that identifies this PVC. ilmi (Optional) Configures the PVC to use ILMI encapsulation (default). qsaal (Optional) Configures the PVC to use QSAAL encapsulation. When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC s configuration and automatically switches to its parent subinterface. Router(config-if-atm-vc)# protocol protocol protocol-address [[no] broadcast] Router(config-if-atm-vc)# encapsulation aal5snap Configures the PVC for a particular protocol and maps it to a specific protocol-address. protocol Typically set to ppp for point-to-point subinterfaces, but other values are possible. protocol-address Destination address or virtual template interface for this PVC (as appropriate for the specified protocol). [no] broadcast (Optional) Specifies that this mapping should (or should not) be used for broadcast packets. The protocol command also has an inarp option, but this option is not meaningful on point-to-point PVCs that use a manually configured address. (Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap. Repeat Step 1 through Step 5 for each point-to-point subinterface to be configured on this ATM SPA. Step 6 Router(config-if)# end Exits interface configuration mode and returns to privileged EXEC mode. 7-9

10 Verifying a Point-to-Point PVC Configuration To verify the configuration of a particular PVC, use the show atm pvc command: Router# show atm pvc 3/12 ATM3/1/0.12: VCD: 3, VPI: 3, VCI: 12 UBR, PeakRate: AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0 OAM frequency: 0 second(s), OAM retry frequency: 1 second(s) OAM up retry count: 3, OAM down retry count: 5 OAM Loopback status: OAM Disabled OAM VC status: Not Managed ILMI VC status: Not Managed InARP frequency: 15 minutes(s) Transmit priority 6 InPkts: , OutPkts: , InBytes: , OutBytes: InPRoc: 1, OutPRoc: 1, Broadcasts: 0 InFast: 0, OutFast: 0, InAS: , OutAS: InPktDrops: 0, OutPktDrops: 0 CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0 Out CLP=1 Pkts: 0 OAM cells received: 0 F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0 F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0 OAM cells sent: 0 F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0 F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0 OAM cell drops: 0 Status: UP Tip To verify the configuration and current status of all PVCs on a particular interface, you can also use the show atm vc interface atm command. Configuring a PVC on a Multipoint Subinterface Creating a multipoint subinterface allows you to create a point-to-multipoint PVC that can be used as a broadcast PVC for all multicast requests. To create a PVC on a multipoint subinterface, perform this task beginning in global configuration mode: Step 1 Router(config)# interface atm slot/subslot/port.subinterface multipoint Creates the specified point-to-multipoint subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode. Step 2 Router(config-subif)# ip address address mask Assigns the specified IP address and subnet mask to this subinterface. Step 3 Router(config-subif)# no ip directed-broadcast (Optional) Disables the forwarding of IP directed broadcasts, which are sometimes used in denial of service (DOS) attacks. 7-10

11 Step 4 Step 5 Router(config-subif)# pvc [name] vpi/vci [ilmi qsaal] Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are: vpi Specifies the VPI ID. The valid range is 0 to 255. vci Specifies the VCI ID. The valid range is 1 to Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC. You can also configure the following options: name (Optional) An arbitrary string that identifies this PVC. ilmi (Optional) Configures the PVC to use ILMI encapsulation (default). qsaal (Optional) Configures the PVC to use QSAAL encapsulation. When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC s configuration and automatically switches to its parent subinterface. Router(config-if-atm-vc)# protocol protocol {protocol-address inarp} broadcast Configures the PVC for a particular protocol and maps it to a specific protocol-address. protocol Typically set to ip for multipoint subinterfaces, but other values are possible. protocol-address Destination address or virtual template interface for this PVC (if appropriate for the protocol). inarp Specifies that the PVC uses Inverse ARP to determine its address. broadcast Specifies that this mapping should be used for multicast packets. Step 6 Router(config-if-atm-vc)# inarp minutes (Optional) If using Inverse ARP, configures how often the PVC transmits Inverse ARP requests to confirm its address mapping. The valid range is 1 to 60 minutes, with a default of 15 minutes. Step 7 Router(config-if-atm-vc)# encapsulation aal5snap (Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap. Repeat Step 1 through Step 7 for each multipoint subinterface to be configured on this ATM SPA. Step 8 Router(config-if)# end Exits interface configuration mode and returns to privileged EXEC mode. 7-11

12 Verifying a Multipoint PVC Configuration To verify the configuration of a particular PVC, use the show atm pvc command: Router# show atm pvc 1/120 ATM3/1/0.120: VCD: 1, VPI: 1, VCI: 120 UBR, PeakRate: AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0 OAM frequency: 0 second(s), OAM retry frequency: 1 second(s) OAM up retry count: 3, OAM down retry count: 5 OAM Loopback status: OAM Disabled OAM VC status: Not Managed ILMI VC status: Not Managed InARP frequency: 15 minutes(s) Transmit priority 6 InPkts: , OutPkts: , InBytes: , OutBytes: InPRoc: 1, OutPRoc: 1, Broadcasts: 0 InFast: 0, OutFast: 0, InAS: 94964, OutAS: InPktDrops: 0, OutPktDrops: 0 CrcErrors: 0, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0 Out CLP=1 Pkts: 0 OAM cells received: 0 F5 InEndloop: 0, F5 InSegloop: 0, F5 InAIS: 0, F5 InRDI: 0 F4 InEndloop: 0, F4 InSegloop: 0, F4 InAIS: 0, F4 InRDI: 0 OAM cells sent: 0 F5 OutEndloop: 0, F5 OutSegloop: 0, F5 OutRDI: 0 F4 OutEndloop: 0, F4 OutSegloop: 0, F4 OutRDI: 0 OAM cell drops: 0 Status: UP To verify the configuration and current status of all PVCs on a particular interface, you can also use the show atm vc interface atm command. Configuring RFC 1483 Bridging for PVCs RFC 1483, Multiprotocol Encapsulation over ATM Adaptation Layer 5, specifies the implementation of point-to-point bridging of Layer 2 PDUs from an ATM interface. Figure 7-1 shows an example in which the two routers receive VLANs over their respective trunk links and then forward that traffic out through the ATM interfaces into the ATM cloud. In this example, the device with the ATM SPA is shown as a router, but it can also be a Catalyst 6500 series switch. Figure 7-1 Example of RFC 1483 Bridging Topology Trunk ports RFC 1483 Trunk ports ports Switch 1 Router 1 Router 2 Switch 2 ATM Tip RFC 1483 has been updated and superseded by RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer

13 RFC 1483 Bridging for PVCs Configuration Guidelines When configuring RFC 1483 bridging for PVCs, consider the following guidelines: PVCs must use AAL5 Subnetwork Access Protocol (SNAP) encapsulation. To use the Virtual Trunking Protocol (VTP), ensure that each main interface has a subinterface that has been configured for the management VLANs (VLANs 1 and ). VTP is not supported on bridged VCs on a Cisco 7600 SIP-200. RFC 1483 bridging in a switched virtual circuit (SVC) environment is not supported. The 1-Port OC-48c/STM-16 ATM SPA does not support RFC 1483 bridging. RFC 1483 Bridging for PVCs Configuration Task To configure RFC 1483 bridging for PVCs, perform this task beginning in global configuration mode: Step 1 Step 2 Router(config)# interface atm slot/subslot/port.subinterface point-to-point Router(config-subif)# pvc [name] vpi/vci [ilmi qsaal] (Optional) Creates the specified point-to-point subinterface on the given port on the specified ATM SPA card, and enters subinterface configuration mode. Although it is most common to create the PVCs on subinterfaces, you can also omit this step to create the PVCs for RFC 1483 bridging on the main interface. Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are: vpi Specifies the VPI ID. The valid range is 0 to 255. vci Specifies the VCI ID. The valid range is 1 to Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC. You can also configure the following options: name (Optional) An arbitrary string that identifies this PVC. ilmi (Optional) Configures the PVC to use ILMI encapsulation (default). qsaal (Optional) Configures the PVC to use QSAAL encapsulation. 7-13

14 Step 3 Step 4 Router(config-if-atm-vc)#bridge-domain vlan-id [access dot1q dot1q-tunnel] [ignore-bpdu-pid] {pvst-tlv CE-vlan} [increment] [split-horizon] Router(config-if-atm-vc)# encapsulation aal5snap Binds the PVC to the specified vlan-id. You can optionally specify the following keywords: dot1q (Optional) Includes the IEEE 802.1Q tag, which preserves the VLAN ID and class of service (CoS) information across the ATM cloud. dot1q-tunnel (Optional) Enables tunneling of IEEE 802.1Q VLANs over the same link. See the Configuring RFC 1483 Bridging for PVCs with IEEE 802.1Q Tunneling section on page ignore-bpdu-pid (Optional) Ignores bridge protocol data unit (BPDU) packets, to allow interoperation with ATM customer premises equipment (CPE) devices that do not distinguish BPDU packets from data packets. Without this keyword, IEEE BPDUs are sent out using a PID of 0x00-0E, which complies with RFC With this keyword, IEEE BPDUs are sent out using a PID of 0x00-07, which is normally reserved for RFC 1483 data. pvst-tlv When transmitting, the pvst-tlv keyword translates PVST+ BPDUs into IEEE BPDUs. When receiving, the pvst-tlv keyword translates IEEE BPDUs into PVST+ BPDUs. split-horizon (Optional) Enables RFC 1483 split horizon mode to globally prevent bridging between PVCs in the same VLAN. (Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap. Repeat Step 1 through Step 4 for each interface on the ATM SPA to be configured. Step 5 Router(config-if-atm-vc)# end Exits ATM VC configuration mode and returns to privileged EXEC mode. Verifying the RFC 1483 Bridging Configuration To verify the RFC 1483 bridging configuration and status, use the show interface atm command: Router# show interface atm 6/1/0.3 ATM6/1/0.3 is up, line protocol is up Hardware is SPA-4XOC3-ATM Internet address is /24 MTU 4470 bytes, BW Kbit, DLY 80 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ATM 5 packets input, 566 bytes 5 packets output, 566 bytes 1445 OAM cells input, 1446 OAM cells output 7-14

15 Layer 2 Protocol Tunneling Topology CLI Configuration Task To enable BPDU translation for the Layer 2 Protocol Tunneling (L2PT) topologies, use the following command: bridge-domain PE-vlan dot1q-tunnel ignore-bpdu-pid pvst-tlv CE-vlan Configuring RFC 1483 Bridging for PVCs with IEEE 802.1Q Tunneling RFC 1483 bridging (see the Configuring RFC 1483 Bridging for PVCs section on page 7-12) can also include IEEE 802.1Q tunneling, which allows service providers to aggregate multiple VLANs over a single VLAN, while still keeping the individual VLANs segregated and preserving the VLAN IDs for each customer. This tunneling simplifies traffic management for the service provider, while securing the customer networks. Also, the IEEE 802.1Q tunneling is configured only on the service provider switches, so it does not require any additional configuration on the customer-side switches. The customer side is not aware of the configuration. For complete information on IEEE 802.1Q tunneling on the Catalyst 6500 series switch, see the Catalyst 6500 Series Cisco IOS Software Configuration Guide, 12.2SX at the following URL: l RFC 1483 has been updated and superseded by RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5. RFC 1483 Bridging for PVCs with IEEE 802.1Q Tunneling Configuration Guidelines When configuring RFC 1483 bridging for PVCs with IEEE 802.1Q tunneling, consider the following guidelines: Customer equipment must be configured for RFC 1483 bridging with IEEE 802.1Q tunneling, using the bridge-domain dot1q ATM VC configuration command. See the Configuring RFC 1483 Bridging for PVCs section on page 7-12 for more information. PVCs must use AAL5 encapsulation. RFC 1483 bridged PVCs must terminate on the ATM SPA, and the traffic forwarded over this bridged connection to the edge must be forwarded through an Ethernet port. To use the Virtual Trunking Protocol (VTP), each main interface should have a subinterface that has been configured for the management VLANs (VLANs 1 and ). RFC 1483 bridging in a switched virtual circuit (SVC) environment is not supported. 7-15

16 RFC 1483 Bridging for PVCs with IEEE 802.1Q Tunneling Configuration Task To configure RFC 1483 bridging for PVCs with IEEE 802.1Q tunneling, perform this task beginning in global configuration mode: Step 1 Step 2 Step 3 Step 4 Router(config)# interface atm slot/subslot.port.subinterface point-to-point Router(config-subif)# pvc [name] vpi/vci [ilmi qsaal] (Optional) Creates the specified point-to-point subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode. Although it is most common to create the PVCs on subinterfaces, you can also omit this step to create the PVCs for RFC 1483 bridging on the main interface. Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are: vpi Specifies the VPI ID. The valid range is 0 to 255. vci Specifies the VCI ID. The valid range is 1 to Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC. You can also configure the following options: name (Optional) An arbitrary string that identifies this PVC. ilmi (Optional) Configures the PVC to use ILMI encapsulation (default). qsaal (Optional) Configures the PVC to use QSAAL encapsulation. When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC s configuration and automatically switches to its parent subinterface. Router(config-if-atm-vc)# bridge-domain vlan-id dot1q-tunnel Router(config-if-atm-vc)# encapsulation aal5snap Binds the PVC to the specified vlan-id and enables the use of IEEE 802.1Q tunneling on the PVC. This preserves the VLAN ID information across the ATM cloud. (Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The default and only supported type is aal5snap. Repeat Step 1 through Step 4 for each interface on the ATM SPA to be configured. Step 5 Router(config-if-atm-vc)# end Exits ATM VC configuration mode and returns to privileged EXEC mode. 7-16

17 Verifying the RFC 1483 for PVCs Bridging with IEEE 802.1Q Tunneling Configuration To verify the IEEE 802.1Q tunneling on an ATM SPA, use the show 12-protocol-tunnel command: Router# show l2protocol-tunnel COS for Encapsulated Packets: 5 Port Protocol Shutdown Drop Encapsulation Decapsulation Drop Threshold Threshold Counter Counter Counter Gi4/2 cdp stp vtp ATM6/2/1 cdp n/a n/a n/a stp n/a n/a n/a vtp n/a n/a n/a The counters in the output of the show l2protocol-tunnel command are not applicable for ATM interfaces when IEEE 802.1Q tunneling is enabled. Use the following command to display the interfaces that are configured with an IEEE 802.1Q tunnel: Router# show dot1q-tunnel LAN Port(s) Gi4/2 ATM Port(s) ATM6/2/1 Configuring ATM RFC 1483 Half-Bridging The ATM SPA supports ATM RFC 1483 half-bridging, which routes IP traffic from a stub-bridged ATM LAN over bridged RFC 1483 Ethernet traffic, without using integrated routing and bridging (IRB). This allows bridged traffic that terminates on an ATM PVC to be routed on the basis of the destination IP address. For example, Figure 7-2 shows a remote bridged Ethernet network connecting to a routed network over a device that bridges the Ethernet LAN to the ATM interface. Figure 7-2 ATM RFC 1483 Half-Bridging ATM 4/1/ Ethernet subnet When half-bridging is configured, the ATM interface receives the bridged IP packets and routes them according to each packet s IP destination address. Similarly, when packets are routed to this ATM PVC, it then forwards them out as bridged packets on its bridge connection. 7-17

18 This use of a stub network topology offers better performance and flexibility over integrated routing and bridging (IRB). This also helps to avoid a number of issues such as broadcast storms and security risks. In particular, half-bridging reduces the potential security risks that are associated with normal bridging configurations. Because the ATM interface allocates a single virtual circuit (VC) to a subnet (which could be as small as a single IP address), half-bridging limits the size of the nonsecured network that can be allowed access to the larger routed network. This makes half-bridging configurations ideally suited for customer access points, such digital subscriber lines (DSL). RFC 1483 has been updated and superseded by RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5. However, to avoid confusion, this document continues to use the previously-used terminology of RFC 1483 ATM half-bridging. To configure a point-to-multipoint ATM PVC for ATM half-bridging, use the configuration task in the following section. Use the following configuration task when you want to configure point-to-multipoint PVCs for half-bridging operation. Use the configuration task in the next section, Configuring ATM Routed Bridge Encapsulation, to configure a point-to-point PVC for similar functionality. ATM RFC 1483 Half-Bridging Configuration Guidelines When configuring ATM RFC 1483 half-bridging, consider the following guidelines: Supports only IP traffic and access lists. Supports only fast switching and process switching. Supports only PVCs that are configured on multipoint subinterfaces. SVCs are not supported for half-bridging. A maximum of one PVC can be configured for half-bridging on each subinterface. Other PVCs can be configured on the same subinterface, as long as they are not configured for half-bridging as well. The same PVC cannot be configured for both half-bridging and full bridging. ATM RFC 1483 Half-Bridging Configuration Task To configure ATM RFC 1483 half-bridging, perform this task beginning in global configuration mode: Step 1 Step 2 Router(config)# interface atm slot/subslot/port.subinterface multipoint Router(config-subif)# ip address address mask [secondary] Creates the specified point-to-point subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode. Assigns the specified IP address and subnet mask to this subinterface. This IP address should be on the same subnet as the remote bridged network (the Ethernet network). 7-18

19 Step 3 Step 4 Router(config-subif)# pvc [name] vpi/vci [ilmi qsaal] Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are: vpi Specifies the VPI ID. The valid range is 0 to 255. vci Specifies the VCI ID. The valid range is 1 to Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC. You can also configure the following options: name (Optional) An arbitrary string that identifies this PVC. ilmi (Optional) Configures the PVC to use ILMI encapsulation (default). qsaal (Optional) Configures the PVC to use QSAAL encapsulation. When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC s configuration and automatically switches to its parent subinterface. Router(config-if-atm-vc)# encapsulation aal5snap bridge (Optional) Configures the ATM adaptation layer (AAL) and encapsulation type, and specifies that half-bridging should be used. Step 5 Router(config-if-atm-vc)# end Exits ATM VC configuration mode and returns to privileged EXEC mode. Verifying the ATM RFC 1483 Half-Bridging Configuration To verify the ATM RFC 1483 half-bridging configuration, use the show atm vc command: Router# show atm vc 20 ATM4/0/0.20: VCD: 20, VPI: 1, VCI: 20 UBR, PeakRate: AAL5-LLC/SNAP, etype:0x0, Flags: 0xC20, VCmode: 0x0 OAM frequency: 0 second(s) InARP frequency: 15 minutes(s), 1483-half-bridged-encap Transmit priority 6 InPkts: 2411, OutPkts: 2347, InBytes: , OutBytes: InPRoc: 226, OutPRoc: 0 InFast: 0, OutFast: 0, InAS: 2185, OutAS: 2347 InPktDrops: 1, OutPktDrops: 0 InByteDrops: 0, OutByteDrops: 0 CrcErrors: 139, SarTimeOuts: 0, OverSizedSDUs: 0, LengthViolation: 0, CPIErrors: 0 Out CLP=1 Pkts: 0 OAM cells received: 0 OAM cells sent: 0 Status: UP 7-19

20 Configuring ATM Routed Bridge Encapsulation The ATM SPAs support ATM Routed Bridge Encapsulation (RBE), which is similar in functionality to RFC 1483 ATM half-bridging, except that ATM half-bridging is configured on a point-to-multipoint PVC, while RBE is configured on a point-to-point PVC (see the Configuring ATM RFC 1483 Half-Bridging section on page 7-17). The 1-Port OC-48c/STM-16 ATM SPA does not support RBE. Use the following configuration task to configure a point-to-point subinterface and PVC for RBE bridging. RFC 1483 has been updated and superseded by RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5. ATM Routed Bridge Encapsulation Configuration Guidelines When configuring ATM RBE, consider the following guidelines: Supported only on ATM SPAs in a Cisco 7600 SIP-200. RBE is not supported when using a Cisco 7600 SIP-400. Supports only AAL5SNAP encapsulation. Supports only IP access lists, not MAC-layer access lists. Supports only fast switching and process switching. Supports distributed Cisco Express Forwarding (dcef). Supports only PVCs on point-to-point subinterfaces. SVCs are not supported for half-bridging. The bridge-domain command cannot be used on any PVC that is configured for RBE, because an RBE PVC acts as the termination point for bridged packets. The atm bridge-enable command, which was used in previous releases on other ATM interfaces, is not supported on ATM SPA interfaces. The IS-IS protocol is not supported with point-to-point PVCs that are configured for RBE bridging. RBE Configuration Limitation Supports Only One Remote MAC Address On the Catalyst 6500 Series switch with the Supervisor Engine 720 and the following port adapters, an ATM PVC with an RBE configuration can send packets to only a single MAC address: ATM SPA on the Cisco 7600 SIP-200 line card This restriction occurs because the Catalyst 6500 Series switch keeps only one MAC address attached to an RBE PVC. The MAC address-to-pvc mapping is refreshed when a packet is received from the host. If there are multiple hosts connected to the PVC, the mapping will not be stable and traffic forwarding will be affected. 7-20

21 The solution to this problem is as follows: 1. Configure the ATM PVC for RFC 1483 bridging using the bridge domain vlan x command line interface. 2. Configure an interface vlan vlan x with the IP address of the RBE subinterface. ATM Routed Bridge Encapsulation Configuration Task To configure ATM routed bridge encapsulation, perform this task beginning in global configuration mode: Step 1 Router(config)# interface atm slot/subslot/port.subinterface point-to-point Creates the specified multipoint subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode. Step 2 Router(config-subif)# atm route-bridge ip Enables ATM RFC 1483 half-bridging (RBE bridging). Step 3 Step 4 Step 5 Router(config-subif)# ip address address mask [secondary] Router(config-subif)# pvc [name] vpi/vci [ilmi qsaal] The atm route-bridge ip command can be given either before or after you create the PVC. Assigns the specified IP address and subnet mask to this subinterface. This IP address should be on the same subnet as the remote bridged network (the Ethernet network). Configures a new ATM PVC by assigning its VPI/VCI numbers and enters ATM VC configuration mode. The valid values for vpi/vci are: vpi Specifies the VPI ID. The valid range is 0 to 255. vci Specifies the VCI ID. The valid range is 1 to Values 1 to 31 are reserved and should not be used, except for 5 for the QSAAL PVC and 16 for the ILMI PVC. You can also configure the following options: name (Optional) An arbitrary string that identifies this PVC. ilmi (Optional) Configures the PVC to use ILMI encapsulation (default). qsaal (Optional) Configures the PVC to use QSAAL encapsulation. When using the pvc command, remember that the vpi/vci combination forms a unique identifier for the interface and all of its subinterfaces. If you specify a vpi/vci combination that has been used on another subinterface, the Cisco IOS software assumes that you want to modify that PVC s configuration and automatically switches to its parent subinterface. Router(config-if-atm-vc)# encapsulation aal5snap (Optional) Configures the ATM adaptation layer (AAL) and encapsulation type. The only supported encapsulation for an RBE PVC is aal5snap. Step 6 Router(config-if-atm-vc)# end Exits ATM VC configuration mode and returns to privileged EXEC mode. 7-21

22 The atm route-bridge ip command, like other subinterface configuration commands, is not automatically removed when you delete a subinterface. If you want to remove a subinterface and recreate it without the half-bridging, be sure to manually remove the half-bridging configuration, using the no atm route-bridge ip command. Verifying the ATM Routed Bridge Encapsulation Configuration To verify the RBE bridging configuration, use the show ip cache verbose command: Router# show ip cache verbose IP routing cache 3 entries, 572 bytes 9 adds, 6 invalidates, 0 refcounts Minimum invalidation interval 2 seconds, maximum interval 5 seconds, quiet interval 3 seconds, threshold 0 requests Invalidation rate 0 in last second, 0 in last 3 seconds Last full cache invalidation occurred 00:30:34 ago Prefix/Length Age Interface Next Hop / :30:10 Ethernet3/1/ C9F2A81D BB / :00:04 ATM1/1/ AA030080C F5D201C / :06:09 ATM1/1/ AA030080C E01E8D3F901C0800 Configuring RFC 1483 Bridging of Routed Encapsulations Bridging of routed encapsulations (BRE) enables the ATM SPA to receive RFC 1483 routed encapsulated packets and forward them as Layer 2 frames. In a BRE configuration, the PVC receives the routed PDUs, removes the RFC 1483 routed encapsulation header, and adds an Ethernet MAC header to the packet. The Layer 2 encapsulated packet is then switched by the supervisor engine to the Layer 2 interface determined by the VLAN number and destination MAC. The 1-Port OC-48c/STM-16 ATM SPA does not support bridging. Figure 7-3 shows a topology where an interface on an ATM SPA receives routed PDUs from the ATM cloud and encapsulates them as Layer 2 frames. It then forwards the frames to the Layer 2 customer device. In this example, the device with the ATM SPA is shown as a Cisco 7600 series router, but it can also be a Catalyst 6500 series switch. Figure 7-3 Example BRE Topology CPE 1 Cisco 7600 Edge router CPE 2 Ethernet frames ATM RFC 1483 Routed Encapsulated ATM PDUs CE

23 RFC 1483 Bridging of Routed Encapsulations Configuration Guidelines When configuring RFC 1483 bridging of routed encapsulations, consider the following guidelines: BRE requires that the ATM SPAs are installed in a Cisco 7600 SIP-200. PVCs must use AAL5 encapsulation. RFC 1483 bridged PVCs must terminate on the ATM SPA, and the traffic forwarded over this bridged connection to the edge must be forwarded through an Ethernet port. To use the Virtual Trunking Protocol (VTP), each main interface should have a subinterface that has been configured for the management VLANs (VLANs 1 and ). BRE is not supported when using a Cisco 7600 SIP-400. Concurrent configuration of RFC 1483 bridging and BRE on the same PVC and VLAN is not supported. Bridging between RFC 1483 bridged PVCs is not supported. RFC 1483 bridging in a switched virtual circuit (SVC) environment is not supported. RFC 1483 Bridging of Routed Encapsulations Configuration Task To configure RFC 1483 bridging of routed encapsulations, perform this task beginning in global configuration mode: Step 1 Router(config)# interface atm slot/subslot/port Enters interface configuration mode for the indicated port on the specified ATM SPA. Step 2 Router(config-if)# no ip address Assigns no IP address to the interface. Step 3 Router(config-if)# spanning-tree bpdufilter enable (Optional) Blocks all Spanning Tree BPDUs on the ATM interface. This command should be used if this ATM interface is configured only for BRE VLANs. If this ATM interface is configured for both BRE and RFC 1483 bridged VLANs, do not enter this command unless you want to explicitly block BPDUs on the interface. Step 4 Router(config-if)# no shutdown Enables the interface. Step 5 Router(config-if)# interface atm slot/subslot/port.subinterface point-to-point Creates the specified point-to-point subinterface on the given port on the specified ATM SPA, and enters subinterface configuration mode. Step 6 Router(config-subif)# no ip address Assigns no IP address to the subinterface. 7-23