Table Of Contents
Configuring the SIPs and SSC
Configuration Tasks
Required Configuration Tasks
Identifying Slots and Subslots for SIPs, SSCs, and SPAs
Configuring Compressed Real-Time Protocol
Configuring Frame Relay Features
Configuring Layer 2 Interworking Features on a SIP
Configuring MPLS Features on a SIP
Configuring QoS Features on a SIP
Configuring Lawful Intercept on a Cisco 7600 SIP-400
Configuring Security ACLs on an Access Interface on a Cisco 7600 SIP-400
Configuring Per-Subscriber/Per-Protocol CoPP on Access Interfaces on a Cisco 7600 SIP-400
Resetting a SIP
Configuration Examples
Layer 2 Interworking Configuration Examples
MPLS Configuration Examples
QoS Configuration Examples
Configuring the SIPs and SSC
This chapter provides information about configuring SIPs and SSCs on the Cisco 7600 series router. It includes the following sections:
•
Configuration Tasks
• Configuration Examples
For information about managing your system images and configuration files, refer to the Cisco IOS Configuration Fundamentals Configuration Guide and Cisco IOS Configuration Fundamentals Command Reference publications that correspond to your Cisco IOS software release.
For more information about the commands used in this chapter, see first Chapter 40, "SIP, SSC, and SPA Commands," which documents new and modified commands, and then any related Cisco 7600 Series Router Command Reference publication for your release. Also refer to the related Cisco IOS software command reference and master index publications. For more information about accessing these publications, see the "Related Documentation" section on page xlviii.
Configuration Tasks
This section describes how to configure the SIPs and SSCs and includes information about verifying the configuration.
It includes the following topics:
• Required Configuration Tasks
• Identifying Slots and Subslots for SIPs, SSCs, and SPAs
• Configuring Compressed Real-Time Protocol
• Configuring Frame Relay Features
• Configuring Layer 2 Interworking Features on a SIP
• Configuring MPLS Features on a SIP
• Configuring QoS Features on a SIP
• Configuring Lawful Intercept on a Cisco 7600 SIP-400
• Configuring Security ACLs on an Access Interface on a Cisco 7600 SIP-400
• Configuring Per-Subscriber/Per-Protocol CoPP on Access Interfaces on a Cisco 7600 SIP-400
• Resetting a SIP
This section identifies those features that have SIP-specific configuration guidelines for you to consider and refers you to the supporting platform documentation.
Many of the Cisco IOS software features on the Cisco 7600 series router that the FlexWAN and Enhanced FlexWAN modules support, the SIPs also support. Use this chapter while also referencing the list of supported features on the SIPs in "Overview of the SIPs and SSC."
Note When referring to the other platform documentation, be sure to note any SIP-specific configuration guidelines described in this document.
For information about configuring other features supported on the Cisco 7600 series router but not discussed in this document, refer to the Cisco 7600 Series Cisco IOS Software Configuration Guide, 12.2SX at the following URL:
http://www.cisco.com/en/US/products/hw/routers/ps368/products_configuration_guide_book09186a00801d4269.html
Required Configuration Tasks
As of Cisco IOS Release 12.2(18)SXE, there are not any features that require direct configuration on the SIP or SSC. This means that you do not need to attach to the SIP or SSC itself to perform any configuration.
However, the Cisco 7600 SIP-200 and Cisco 7600 SIP-400 do implement and support certain features that are configurable at the system level on the Route Processor (RP).
Identifying Slots and Subslots for SIPs, SSCs, and SPAs
This section describes how to specify the physical locations of a SIP and SPA on the Cisco 7600 series routers within the command-line interface (CLI) to configure or monitor those devices.
Note For simplicity, any reference to "SIP" in this section also applies to the SSC.
Specifying the Slot Location for a SIP or SSC
The Cisco 7600 series router supports different chassis models, each of which supports a certain number of chassis slots.
Note The Cisco 7600 series router SIPs are not supported with a Supervisor Engine 1, Supervisor Engine 1A, Supervisor Engine 2, or Supervisor Engine 720-3A.
Figure 4-1 shows an example of a SIP installed in slot 6 on a Cisco 7609 router. The Cisco 7609 router has nine vertically-oriented chassis slots, which are numbered 1 to 9 from right to left.
Figure 4-1 SIP and SPA Installed in a Cisco 7609 Router
1
|
SIP subslot 0
|
4
|
SIP subslot 3
|
2
|
SIP subslot 1
|
5
|
Chassis slots 1-9 (numbered from right to left)
|
3
|
SIP subslot 2
|
|
|
Some commands allow you to display information about the SIP itself, such as show module, show sip-disk, show idprom module, show hw-module slot, and show diagbus. These commands require you to specify the chassis slot location where the SIP that you want information about is installed.
For example, to display status and information about the SIP installed in slot 6 as shown in Figure 4-1, enter the following command:
For more information about SIP commands, see the "Command Summary for the SIPs and SSC" and the "SIP, SSC, and SPA Commands" chapters in the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide.
Specifying the SIP or SSC Subslot Location for a SPA
SIP subslots begin their numbering with "0" and have a horizontal or vertical orientation depending on the orientation of the SIP in the router chassis slot, as shown in the "SIP, SSC, and SPA Product Overview" chapter of the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide.
Figure 4-1 shows an example of a Cisco 7600 SIP-200 installed with a vertical orientation on a Cisco 7609 router. The Cisco 7600 SIP-200 supports four subslots for the installation of SPAs. In this example, the subslot locations are vertically oriented as follows:
•SIP subslot 0—Top-right subslot
•SIP subslot 1—Bottom-right subslot
•SIP subslot 2—Top-left subslot
•SIP subslot 3—Bottom-left subslot
Figure 4-2 shows the faceplate for the Cisco 7600 SIP-200 in a horizontal orientation.
Figure 4-2 Cisco 7600 SIP-200 Faceplate
In this view, the subslot locations in a horizontal orientation are as follows:
•SIP subslot 0—Top-left subslot
•SIP subslot 1—Top-right subslot
•SIP subslot 2—Bottom-left subslot
•SIP subslot 3—Bottom-right subslot
The SIP subslot numbering is indicated by a small numeric label beside the subslot on the faceplate.
Just as with the SIPs, some commands allow you to display information about the SPA itself, such as show idprom module and show hw-module subslot. These commands require you to specify both the physical location of the SIP and SPA in the format, slot/subslot, where:
•slot—Specifies the chassis slot number in the Cisco 7600 series router where the SIP is installed.
•subslot—Specifies the secondary slot of the SIP where the SPA is installed.
For example, to display the operational status for the SPA installed in the first subslot of the SIP in chassis slot 6 shown in Figure 4-1, enter the following command:
Router# show hw-module subslot 6/0 oir
For more information about SPA commands, see the command summary chapter for that SPA, and the "SIP, SSC, and SPA Commands" chapter in the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide.
Configuring Compressed Real-Time Protocol
Compressed Real-Time Protocol (CRTP), from RFC 1889 (RTP: A Transport Protocol for Real-Time Applications), provides bandwidth efficiencies over low-speed links by compressing the UDP/RTP/IP header when transporting voice. With CRTP, the header for Voice over IP traffic can be reduced from 40 bytes to approximately 2 to 5 bytes offering substantial bandwidth efficiencies for low-speed links. CRTP is supported over Frame Relay, ATM, PPP, distributed MLPPP (dMLP PP), and HDLC encapsulated interfaces.
Table 4-1 provides information about where the CRTP feature for SPA interfaces is supported.
Table 4-1 CRTP Feature Compatibility by SIP and SPA Combination
Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Hardware-based CRTP
|
In Cisco IOS Release 12.2(18)SXE and later:
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port Channelized T3 SPA
|
Not supported.
|
Not supported.
|
Hardware- and software-based CRTP
|
In Cisco IOS Release 12.2(33)SRA:
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port Channelized T3 SPA
•1-Port Channelized OC-3/STM-1 SPA
|
Not supported.
|
Not supported.
|
CRTP with dLFIoLL—Only supported with one link present on the multilink interface
|
In Cisco IOS Release 12.2(18)SXE and later:
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port Channelized T3 SPA
Support for the following SPA was added in Cisco IOS Release 12.2(33)SRA:
•1-Port Channelized OC-3/STM-1 SPA
|
Not supported.
|
Not supported.
|
CRTP with dMLPPP
|
Supported. Not supported if LFI is enabled.
|
Not supported.
|
Not supported.
|
CRTP with dMLPPP and MPLS
|
Not supported.
|
Not supported.
|
Not supported.
|
CRTP Configuration Guidelines
To support CRTP on the Cisco 7600 SIP-200, consider the following guidelines:
•High-level Data Link Control (HDLC), PPP, or Frame Relay encapsulation must be configured.
•TCP or RTP header compression, or both, must be enabled.
•When distributed fast-switching is enabled, the detail option is not available with the show ip rtp header-compression and show ip tcp header-compression commands. Users who need the detailed information for either of these commands can retrieve this information by disabling distributed fast-switching and then entering the show ip rtp header-compression detail or show ip tcp header-compression detail commands.
•When using CRTP with distributed features on the Cisco 7600 SIP-200, consider the following guidelines and restrictions:
–Hardware- and software-based CRTP is supported with Distributed Link Fragmentation and Interleaving over Leased Lines (dLFIoLL) if only one link is present on the multilink interface.
–The following restrictions apply to Multilink PPP interfaces that use LFI:
If RTP header compression is configured, RTP packets originating on or destined to the router will be fast-switched if the link is limited to one channel. If the link has more than one channel, the packets will be process-switched.
CRTP should not be configured on a multilink interface when LFI is enabled on the multilink interface if the multilink bundle has more than one member link, and a QoS policy with a feature is enabled on the multilink interface.
Note In a dMLPPP/dLFI configuration, packets do not carry the MLPPP header and sequence number. Thus, MLPPP distributes the packets across all member links. As a result, packets that are compressed by CRTP may arrive out-of-order at the receiving router. This prohibits CRTP from decompressing the packet header and forces CRTP to drop the packets.
For information on configuring CRTP, see Configuring Distributed Compressed Real-Time Protocol at the following URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800b75cd.html
Configuring Frame Relay Features
Many of the Frame Relay features supported on the FlexWAN and Enhanced FlexWAN modules on the Cisco 7600 series router are also supported by the SIPs. For a list of the supported Frame Relay features on the SIPs, see "Overview of the SIPs and SSC."
This section describes those Frame Relay features that have SIP-specific configuration guidelines. After you review the SIP-specific guidelines described in this document, then refer to the referenced URLs for more information about configuring Frame Relay features.
The Frame Relay features for SIPs and SPAs are qualified as distributed features because the processing for the feature is handled by the SIP or SPA, or a combination of both.
Configuring Distributed Multilink Frame Relay (FRF.16) on the Cisco 7600 SIP-200
The Distributed Multilink Frame Relay (dMLFR) feature provides a cost-effective way to increase bandwidth for particular applications by enabling multiple serial links to be aggregated into a single bundle of bandwidth. Multilink Frame Relay is supported on the User-Network Interface (UNI) and the Network-to-Network Interface (NNI) in Frame Relay networks.
Note Based on your link configuration, dMLFR can be either software-based on the Cisco 7600 SIP-200, or hardware-based on the 8-Port Channelized T1/E1 SPA, 2-Port and 4-Port Channelized T3 SPAs, and 1-Port Channelized OC-3/STM-1 SPA. For more information about the hardware-based configuration, see also Chapter 22, "Configuring the 8-Port Channelized T1/E1 SPA," and Chapter 24, "Configuring the 2-Port and 4-Port Channelized T3 SPAs."
Table 4-2 provides information about where the dMLFR feature for SPA interfaces is supported.
Table 4-2 dMLFR Feature Compatibility by SIP and SPA Combination
Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Hardware- and software-based dMLFR
|
In Cisco IOS Release 12.2(18)SXE and later:
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port Channelized T3 SPA
In Cisco IOS Release 12.2(33)SRA and later:
•1-Port Channelized OC-3/STM-1 SPA
|
Not supported.
|
Not supported.
|
This section includes the following topics:
• Overview of dMLFR
• dMLFR Configuration Guidelines
• dMLFR Configuration Tasks
• Verifying dMLFR
Overview of dMLFR
The Distributed Multilink Frame Relay feature enables you to create a virtual interface called a bundle or bundle interface. The bundle interface emulates a physical interface for the transport of frames. The Frame Relay data link runs on the bundle interface, and Frame Relay virtual circuits are built upon it.
The bundle is made up of multiple serial links, called bundle links. Each bundle link within a bundle corresponds to a physical interface. Bundle links are invisible to the Frame Relay data-link layer, so Frame Relay functionality cannot be configured on these interfaces. Regular Frame Relay functionality that you want to apply to these links must be configured on the bundle interface. Bundle links are visible to peer devices. The local router and peer devices exchange link integrity protocol control messages to determine which bundle links are operational and to synchronize which bundle links should be associated with which bundles.
For link management, each end of a bundle link follows the MLFR link integrity protocol and exchanges link control messages with its peer (the other end of the bundle link). To bring up a bundle link, both ends of the link must complete an exchange of ADD_LINK and ADD_LINK_ACK messages. To maintain the link, both ends periodically exchange HELLO and HELLO_ACK messages. This exchange of hello messages and acknowledgments serves as a keepalive mechanism for the link. If a router is sending hello messages but not receiving acknowledgments, it will resend the hello message up to a configured maximum number of times. If the router exhausts the maximum number of retries, the bundle link line protocol is considered down (unoperational).
The bundle link interface's line protocol status is considered up (operational) when the peer device acknowledges that it will use the same link for the bundle. The line protocol remains up when the peer device acknowledges the hello messages from the local router.
The bundle interface's line status becomes up when at least one bundle link has its line protocol status up. The bundle interface's line status goes down when the last bundle link is no longer in the up state. This behavior complies with the Class A bandwidth requirement defined in FRF.16.
The bundle interface's line protocol status is considered up when the Frame Relay data-link layer at the local router and peer device synchronize using the Local Management Interface (LMI), when LMI is enabled. The bundle line protocol remains up as long as the LMI keepalives are successful.
dMLFR Configuration Guidelines
To support dMLFR on the Cisco 7600 SIP-200, consider the following guidelines:
•dMLFR must be configured on the peer device.
•The dMLFR peer device must not send frames that require assembly.
•The Cisco 7600 SIP-200 supports distributed links under the following conditions:
–All links are on the same Cisco 7600 SIP-200.
–T1 and E1 links cannot be mixed in a bundle.
–Member links in a bundle are recommended to have the same bandwidth.
•QoS is implemented on the Cisco 7600 SIP-200 for dMLFR.
•dMLFR is supported with Frame Relay over MPLS (FRoMPLS) on the Cisco 7600 SIP-200 between the customer edge (CE) and provider edge (PE) of the MPLS network.
•The Cisco 7600 SIP-200 only supports the RPR+ High Availability (HA) feature with dMLFR.
•dMLFR is supported in software by the Cisco 7600 SIP-200, or in hardware by the supported SPA. This support is determined by your link configuration.
•dMLFR is supported in software if bundle link members are on different SPAs in the same SIP.
Software-Based Guidelines
dMLFR will be implemented in the software if any of the following conditions are met:
•Any one bundle link member is a fractional T1 or E1 link.
•There are more than 12 T1 or E1 links in a bundle.
Hardware-Based Guidelines
dMLFR will be implemented in the hardware when all of the following conditions are met:
•All bundle link members are T1 or E1 only.
•All bundle links are on the same SPA.
•There are no more than 12 links in a bundle.
dMLFR Restrictions
When configuring dMLFR on the Cisco 7600 SIP-200, consider the following restrictions:
•FRF.9 hardware compression is not supported.
•Software compression is not supported.
•Encryption is not supported.
•The maximum differential delay supported is 50 ms when supported in hardware, and 100 ms when supported in software.
•Fragmentation is not supported on the transmit side.
dMLFR Configuration Tasks
The following sections describe how to configure dMLFR:
• Creating a Multilink Frame Relay Bundle (required)
• Assigning an Interface to a dMLFR Bundle (required)
Creating a Multilink Frame Relay Bundle
To configure the bundle interface for dMLFR, use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface mfr number
|
Configures a multilink Frame Relay bundle interface and enters interface configuration mode, where:
•number—Specifies the number for the Frame Relay bundle.
|
Step 2
|
Router(config-if)# frame-relay multilink bid name
|
(Optional) Assigns a bundle identification name to a multilink Frame Relay bundle, where:
•name—Specifies the name for the Frame Relay bundle.
Note The bundle identification (BID) will not go into effect until the interface has gone from the down state to the up state. One way to bring the interface down and back up again is by using the shutdown and no shutdown commands in interface configuration mode.
|
Step 3
|
Router(config-if)# frame-relay intf-type dce
|
Configures the router to function as a digital communications equipment (DCE) device, or as a switch.
|
Assigning an Interface to a dMLFR Bundle
To configure an interface link and associate it as a member of a dMLFR bundle, use the following commands beginning in global configuration mode. Repeat these steps to assign multiple links to the dMLFR bundle.
Note If you use this task to assign more than 12 T1 or E1 interface links as part of the same bundle, or if any of the T1/E1 interface links are fractional T1/E1, or any links reside on multiple SPAs as part of the same bundle, then software-based dMLFR is implemented automatically by the Cisco 7600 SIP-200.
| |
Command
|
Purpose
|
Step 1
|
1-Port Channelized OC-3/STM-1 SPA
Router(config)# interface serial address
2-Port and 4-Port Channelized T3 SPA
Router(config)# interface serial slot/subslot/port/t1-number:channel-group
8-Port Channelized T1/E1 SPA
Router(config)# interface serial slot/subslot/port:channel-group
|
Specifies a serial interface and enters interface configuration mode, where:
•address—For the different supported syntax options for the address argument for the 1-Port Channelized OC-3/STM-1 SPA, refer to the "Interface Naming" section of the "Configuring the 1-Port Channelized OC-3/STM-1 SPA" chapter.
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
•t1-number—Specifies the logical T1 number in channelized mode.
•channel-group—Specifies the logical channel group assigned to the time slots within the T1 or E1 group.
Note If you configure a fractional T1/E1 interface on the SPA using a channel group and specify that fractional T1/E1 channel group as part of this task, then software-based dMLFR is implemented automatically by the Cisco 7600 SIP-200 when you assign the interface to the dMLFR bundle.
|
Step 2
|
Router(config-if)# encapsulation frame-relay mfr number [name]
|
Creates a multilink Frame Relay bundle link and associates the link with a bundle, where:
•number—Specifies the number for the Frame Relay bundle. This number should match the dMLFR interface number specified in the interface mfr command.
•name—(Optional) Specifies the name for the Frame Relay bundle.
|
Step 3
|
Router(config-if)# frame-relay multilink lid name
|
(Optional) Assigns a bundle link identification name with a multilink Frame Relay bundle link, where:
•name—Specifies the name for the Frame Relay bundle.
Note The bundle link identification (LID) will not go into effect until the interface has gone from the down state to the up state. One way to bring the interface down and back up again is by using the shutdown and no shutdown commands in interface configuration mode.
|
Step 4
|
Router(config-if)# frame-relay multilink hello seconds
|
(Optional) Configures the interval at which a bundle link will send out hello messages, where:
•seconds—Specifies the number of seconds between hello messages sent out over the multilink bundle. The default is 10 seconds.
|
Step 5
|
Router(config-if)# frame-relay multilink ack seconds
|
(Optional) Configures the number of seconds that a bundle link will wait for a hello message acknowledgment before resending the hello message, where:
•seconds—Specifies the number of seconds a bundle link will wait for a hello message acknowledgment before resending the hello message. The default is 4 seconds.
|
Step 6
|
Router(config-if)# frame-relay multilink retry number
|
(Optional) Configures the maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment, where:
•number—Specifies the maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment. The default is 2 tries.
|
Verifying dMLFR
To verify dMLFR configuration, use the show frame-relay multilink command. If you use the show frame-relay multilink command without any options, information for all bundles and bundle links is displayed.
The following examples show output for the show frame-relay multilink command with the serial number and detailed options. Detailed information about the specified bundle links is displayed.
Router# show frame-relay multilink serial6 detailed
Bundle: MFR49, State = down, class = A, fragmentation disabled
No. of bundle links = 1, Peer's bundle-id =
Serial6/0/0:0, HW state = up, link state = Add_sent, LID = test
Cause code = none, Ack timer = 4, Hello timer = 10,
Max retry count = 2, Current count = 0,
Add_link sent = 21, Add_link rcv'd = 0,
Add_link ack sent = 0, Add_link ack rcv'd = 0,
Add_link rej sent = 0, Add_link rej rcv'd = 0,
Remove_link sent = 0, Remove_link rcv'd = 0,
Remove_link_ack sent = 0, Remove_link_ack rcv'd = 0,
Hello sent = 0, Hello rcv'd = 0,
Hello_ack sent = 0, Hello_ack rcv'd = 0,
outgoing pak dropped = 0, incoming pak dropped = 0
Configuring Distributed Multilink PPP on the Cisco 7600 SIP-200
The Distributed Multilink Point-to-Point Protocol (dMLPPP) feature allows you to combine T1/E1 lines into a bundle that has the combined bandwidth of multiple T1/E1 lines. This is done by using a dMLPPP link. You choose the number of bundles and the number of T1/E1 lines in each bundle. This allows you to increase the bandwidth of your network links beyond that of a single T1/E1 line without having to purchase a T3 line.
Note Based on your link configuration, dMLPPP can be either software-based on the Cisco 7600 SIP-200, or hardware-based on the 8-Port Channelized T1/E1 SPA and 2-Port and 4-Port Channelized T3 SPAs. For more information about the hardware-based configuration, see also Chapter 22, "Configuring the 8-Port Channelized T1/E1 SPA," Chapter 24, "Configuring the 2-Port and 4-Port Channelized T3 SPAs.", and Chapter 25, "configuring the 1-Port Channelized OC3/STM-1 SPA.
Table 4-3 provides information about where the dMLppp feature for SPA interfaces is supported.
Table 4-3 dMLPPP Feature Compatibility by SIP and SPA Combination
Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Hardware-based dMLPPP
|
Supported
|
Not supported.
|
Not supported.
|
Hardware- and software-based dMLPPP
|
In Cisco IOS Release 12.2(18)SXE and later:
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port Channelized T3 SPA
In Cisco IOS Release 12.2(33)SRA and later:
•1-Port Channelized OC3/STM-1 SPA
|
Not supported.
|
Not supported.
|
This section includes the following topics:
• dMLPPP Configuration Guidelines
• dMLPPP Configuration Tasks
• Verifying dMLPPP
dMLPPP Configuration Guidelines
dMLPPP is supported in software by the Cisco 7600 SIP-200, or in hardware by the supported SPA. This support is determined by your link configuration.
The Cisco 7600 SIP-200 supports distributed links under the following conditions:
•All links are on the same Cisco 7600 SIP-200.
•T1 and E1 links cannot be mixed in a bundle.
•Member links in a bundle are recommended to have the same bandwidth.
•QoS is implemented on the Cisco 7600 SIP-200 for dMLPPP.
Software-Based Guidelines
dMLPPP will be implemented in the software if any of the following conditions are met:
•Any one bundle link member is a fractional T1 or E1 link.
•There are more than 12 T1 or E1 links in a bundle.
•To enable fragmentation for software-based dMLPPP, you must configure the ppp multilink interleave command. This command is not required to enable fragmentation for hardware-based dMLPPP.
Hardware-Based Guidelines
dMLPPP will be implemented in the hardware when all of the following conditions are met:
•All bundle link members are T1 or E1 only.
•All bundle links are on the same SPA.
•There are no more than 12 links in a bundle.
dMLPPP Restrictions
When configuring dMLPPP on the Cisco 7600 SIP-200, consider the following restrictions:
•Hardware and software compression is not supported.
•Encryption is not supported.
•The maximum differential delay supported is 50 ms when supported in hardware, and 100 ms when supported in software.
dMLPPP Configuration Tasks
The following sections describe how to configure dMLPPP:
• Enabling Distributed CEF Switching (required)
• Creating a dMLPPP Bundle (required)
• Assigning an Interface to a dMLPPP Bundle (required)
• Configuring Link Fragmentation and Interleaving over dMLPPP (optional)
Enabling Distributed CEF Switching
To enable dMLPPP, you must first enable distributed CEF switching. Distributed CEF switching is enabled by default on the Cisco 7600 series router.
To enable dCEF, use the following command in global configuration mode:
Command
|
Purpose
|
Router(config)# ip cef distributed
|
Enables distributed CEF switching.
|
Creating a dMLPPP Bundle
To configure a dMLPPP bundle, use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface multilink group-number
|
Creates a multilink interface and enters interface configuration mode, where:
•group-number—Specifies the group number for the multilink bundle.
|
Step 2
|
Router(config-if)# ip address ip-address mask
|
Sets the IP address for the multilink group, where:
•ip-address—Specifies the IP address for the interface.
•mask—Specifies the mask for the associated IP subnet.
|
Step 3
|
Router(config-if)# ppp multilink interleave
|
(Optional—Software-based LFI) Enables fragmentation for the interfaces assigned to the multilink bundle. Fragmentation is disabled by default in software-based LFI.
|
Step 4
|
Router(config-if)# ppp multilink mrru [local | remote] mrru-value
|
Configures the MRRU value negotiated on a multilink bundle when MLP is used.
•local—(Optional) Configures the local MRRU value. The default values for the local MRRU are the value of the multilink group interface MTU for multilink group members, and 1524 bytes for all other interfaces.
•remote—(Optional) Configures the minimum value that software will accept from the peer when it advertises its MRRU. By default, the software accepts any peer MRRU value of 128 or higher. You can specify a higher minimum acceptable MRRU value in a range from 128 to 16384 bytes.
|
Step 5
|
Router(config-if)# mtu bytes
|
(Optional) Adjusts the maximum packet size or MTU size.
•Once you configure the MRRU on the bundle interface, you enable the router to receive large reconstructed MLP frames. You may want to configure the bundle MTU so the router can transmit large MLP frames, although it is not strictly necessary.
•The maximum recommended value for the bundle MTU is the value of the peer's MRRU. The default MTU for serial interfaces is 1500. The software will automatically reduce the bundle interface MTU if necessary, to avoid violating the peer's MRRU.
|
Step 6
|
Router(config-if)# ppp multilink fragment delay delay
|
(Optional) Sets the fragmentation size satisfying the configured delay on the multilink bundle, where:
•delay—Specifies the delay in milliseconds.
|
Assigning an Interface to a dMLPPP Bundle
To configure an interface PPP link and associate it as a member of a multilink bundle, use the following commands beginning in global configuration mode. Repeat these steps to assign multiple links to the dMLPPP bundle.
Note If you use this task to assign more than 12 T1 or E1 interface links as part of the same bundle, or if any of the T1/E1 interface links are fractional T1/E1, or any links reside on multiple SPAs as part of the same bundle, then software-based dMLPPP is implemented automatically by the Cisco 7600 SIP-200.
| |
Command
|
Purpose
|
Step 1
|
1-Port Channelized OC-3/STM-1 SPA
Router(config)# interface serial address
2-Port and 4-Port Channelized T3 SPA
Router(config)# interface serial slot/subslot/port/t1-number:channel-group
8-Port Channelized T1/E1 SPA
Router(config)# interface serial slot/subslot/port:channel-group
|
Specifies a serial interface and enters interface configuration mode, where:
•address—For the different supported syntax options for the address argument for the 1-Port Channelized OC-3/STM-1 SPA, refer to the "Interface Naming" section of the "Configuring the 1-Port Channelized OC-3/STM-1 SPA" chapter.
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
•t1-number—Specifies the logical T1 number in channelized mode.
•channel-group—Specifies the logical channel group assigned to the time slots within the T1 or E1 group.
Note If you configure a fractional T1/E1 interface on the SPA using a channel group and specify that fractional T1/E1 channel group as part of this task, then software-based dMLPPP is implemented automatically by the Cisco 7600 SIP-200 when you assign the interface to the dMLPPP bundle.
|
Step 2
|
Router(config-if)# encapsulation ppp
|
Enables PPP encapsulation.
|
Step 3
|
Router(config-if)# ppp multilink
|
(Optional) Enables dMLPPP on the interface.
|
Step 4
|
Router(config-if)# ppp authentication chap
|
(Optional) Enables Challenge Handshake Authentication Protocol (CHAP) authentication.
|
Step 5
|
Router(config-if)# ppp chap hostname name
|
(Optional) Assigns a name to be sent in the CHAP challenge.
•name—Specifies an alternate username that will be used for CHAP authentication
|
Step 6
|
Router(config-if)# ppp multilink group group-number
|
Assigns the interface to a multilink bundle, where:
•group-number—Specifies the group number for the multilink bundle. This number should match the dMLPPP interface number specified in the interface multilink command.
|
Configuring Link Fragmentation and Interleaving over dMLPPP
Link fragmentation and interleaving (LFI) over dMLPPP is supported in software on the Cisco 7600 SIP-200, or in hardware on the 2-Port and 4-Port Channelized T3 SPA and the 8-Port Channelized T1/E1 SPA. This support is determined by your link configuration.
Software-Based Guidelines
When configuring LFI over dMLPPP, consider the following guidelines for software-based LFI:
•LFI over dMLPPP will be configured in software if there is more than one link assigned to the dMLPPP bundle.
•LFI is disabled by default in software-based LFI. To enable LFI on the multilink interface, use the ppp multilink interleave command.
•Fragmentation size is calculated from the delay configured and the member link bandwidth.
•You must configure a policy map with a class under the multilink interface.
•CRTP should not be configured on a multilink interface when LFI is enabled on the multilink interface if the multilink bundle has more than one member link, and a QoS policy with a feature is enabled on the multilink interface.
Hardware-Based Guidelines
When configuring LFI over dMLPPP, consider the following guidelines for hardware-based LFI:
•LFI over dMLPPP will be configured in hardware if you only assign one link (either T1/E1 or fractional T1/E1) to the dMLPPP bundle.
•LFI is enabled by default in hardware-based LFI with a default size of 512 bytes. To enable LFI on the serial interface, use the ppp multilink interleave command.
•A policy map having a class needs to be applied to the multilink interface.
Verifying dMLPPP
To verify dMLPPP configuration, use the show ppp multilink command, as shown in the following example:
Router# show ppp multilink
Multilink2, bundle name is group2
0 lost fragments, 0 reordered, 0 unassigned
0 discarded, 0 lost received, 1/255 load
0x0 received sequence, 0x0 sent sequence
Member links: 2 active, 0 inactive (max not set, min not set)
Se4/3/0/1:0, since 00:01:21, no frags rcvd
Se4/3/0/1:1, since 00:01:19, no frags rcvd
If hardware-based dMLPPP is configured on the SPA, the show ppp multilink command displays "Multilink in Hardware" as shown in the following example:
Router# show ppp multilink
Multilink1, bundle name is group1
0 lost fragments, 0 reordered, 0 unassigned
0 discarded, 0 lost received, 206/255 load
0x0 received sequence, 0x0 sent sequence
Member links: 2 active, 0 inactive (max not set, min not set)
Se4/2/0/1:0, since 00:00:13, no frags rcvd
Se4/2/0/2:0, since 00:00:10, no frags rcvd
Distributed fragmentation on. Fragment size 512. Multilink in Hardware.
Configuring Distributed Link Fragmentation and Interleaving for Frame Relay and ATM Interfaces
The Distributed Link Fragmentation and Interleaving (dLFI) feature supports the transport of real-time traffic, such as voice, and non-real-time traffic, such as data, on lower-speed Frame Relay and ATM virtual circuits (VCs) and on leased lines without causing excessive delay to the real-time traffic.
This feature is implemented using dMLPPP over Frame Relay, ATM, and leased lines. The feature enables delay-sensitive real-time packets and non-real-time packets to share the same link by fragmenting the large data packets into a sequence of smaller data packets (fragments). The fragments are then interleaved with the real-time packets. On the receiving side of the link, the fragments are reassembled and the packets reconstructed.
The dLFI feature is often useful in networks that send real-time traffic using Distributed Low Latency Queueing, such as voice, but have bandwidth problems that delay this real-time traffic due to the transport of large, less time-sensitive data packets. The dLFI feature can be used in these networks to disassemble the large data packets into multiple segments. The real-time traffic packets then can be sent between these segments of the data packets. In this scenario, the real-time traffic does not experience a lengthy delay waiting for the low- data packets to traverse the network. The data packets are reassembled at the receiving side of the link, so the data is delivered intact.
The ability to configure Quality of Service (QoS) using the Modular QoS CLI while also using dMLPPP is also introduced as part of the dLFI feature.
For specific information about configuring dLFI, refer to the FlexWAN and Enhanced FlexWAN Module Installation and Configuration Note located at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/cfgnotes/flexport/combo/index.htm
For information about configuring dLFI on ATM SPAs, see the "Configuring Link Fragmentation and Interleaving with Virtual Templates" section on page 8-46 in Chapter 8, "Configuring the ATM SPAs."
Table 4-4 provides information about where the dLFI feature for SPA interfaces is supported.
Table 4-4 dLFI Feature Compatibility by SIP and SPA Combination
Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Hardware-based dLFI
|
In Cisco IOS Release 12.2(18)SXE and later:
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port Channelized T3 SPA
|
In Cisco IOS Release 12.2(18)SXE and later:
•2-Port OC-3c/STM-1 ATM SPA
•1-Port OC-12c/STM-4 ATM SPA
|
Not supported.
|
Hardware- and software-based dLFI
|
In Cisco IOS Release 12.2(33)SRA:
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port Channelized T3 SPA
•1-Port Channelized OC-3/STM-1 SPA
|
Not supported.
|
Not supported.
|
dLFI with MPLS
|
Not supported.
|
Not supported.
|
Not supported.
|
dLFI with MPLS on VPN
|
Supported between the CE and PE devices, and with virtual routing and forwarding (VRF) configuration.
|
Not supported.
|
Not supported.
|
Cisco 7600 Series Router LFI Restrictions
When configuring LFI on the Cisco 7600 series router, consider the following restrictions:
•A maximum number of 200 permanent virtual circuits (PVCs) or switched virtual circuits (SVCs) using Link Fragmentation and Interleaving (LFI) is supported for all ATM SPAs (or other ATM modules) in a Cisco 7600 series router.
•LFI using FRF.12 is supported in hardware only for the 2-Port and 4-Port Channelized T3 SPA and 8-Port Channelized T1/E1 SPA.
•LFI over dMLPPP is supported in software or hardware depending on your link configuration. For more information about software-based LFI over dMLPPP, see the "Configuring Link Fragmentation and Interleaving over dMLPPP" section. For more information about hardware-based LFI over dMLPPP, refer to the Chapter 22, "Configuring the 8-Port Channelized T1/E1 SPA," and Chapter 24, "Configuring the 2-Port and 4-Port Channelized T3 SPAs."
•QoS is implemented on the Cisco 7600 SIP-200 for dLFI.
Configuring Voice over Frame Relay FRF.11 and FRF.12
Voice over Frame Relay (VoFR) enables a router to carry voice traffic (for example, telephone calls and faxes) over a Frame Relay network using the FRF.11 protocol. This specification defines multiplexed data, voice, fax, dual-tone multi-frequency (DTMF) digit-relay, and channel-associated signaling (CAS)/robbed-bit signaling frame formats. The Frame Relay backbone must be configured to include the map class and Local Management Interface (LMI).
The Cisco VoFR implementation enables dynamic- and tandem-switched calls and Cisco trunk calls. Dynamic-switched calls have dial-plan information included that processes and routes calls based on the telephone numbers. The dial-plan information is contained within dial-peer entries.
Note Because the Cisco 7600 series router does not support voice modules, the Cisco 7600 series router can act only as a VoFR tandem switch when FRF.11 or FRF.12 is configured on the SIPs.
Tandem-switched calls are switched from incoming VoFR to an outgoing VoFR-enabled data-link connection identifier (DLCI) and tandem nodes enable the process. The nodes also switch Cisco trunk calls.
Permanent calls are processed over Cisco private-line trunks and static FRF.11 trunks that specify the frame format and coder types for voice traffic over a Frame Relay network.
VoFR connections depend on the hardware platform and type of call. The types of calls are:
•Switched (user dialed or auto-ringdown and tandem)
•Permanent (Cisco trunk or static FRF.11 trunk)
Note FRF.11 support was removed in Cisco IOS Release 12.2(18)SXF on the Cisco 7600 series router.
Table 4-5 provides information about where the VoFR feature for SPA interfaces is supported.
Table 4-5 VoFR Feature Compatibility by SIP and SPA Combination
Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
FRF.11
|
In Cisco IOS Releases 12.2(18)SXE and 12.2(18)SXE2:
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port Channelized T3 SPA
|
Not supported.
|
Not supported.
|
FRF.12
|
In Cisco IOS Release 12.2(18)SXE and later, and in Cisco IOS Release 12.2(33)SRA:
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port Channelized T3 SPA
•1-Port Channelized OC-3/STM-1 SPA
|
Not supported.
|
Not supported.
|
For specific information about configuring voice over Frame Relay FRF.11 and FRF.12, refer to the Cisco IOS Voice, Video, and Fax Configuration Guide located at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fvvfax_c/vvfvofr.htm
Configuring Layer 2 Interworking Features on a SIP
This section provides SIP-specific information about configuring the Layer 2 interworking features on the Cisco 7600 series router. It includes the following topics:
• Configuring Bridging for ATM Interfaces (RFC 1483/RFC 2684)
• Configuring Multipoint Bridging
• Configuring PPP Bridging Control Protocol Support
Configuring Bridging for ATM Interfaces (RFC 1483/RFC 2684)
The following types of bridging are supported on ATM SPAs in the Cisco 7600 series router. For information about SIP and SPA compatibility with each of these features, see Table 4-6.
Note RFC 1483 has been obsoleted and superseded by RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5. To avoid confusion, this document continues to refer to the original RFC numbers.
•RFC 1483/RFC 2684 bridging for point-to-point PVCs —RFC 1483 has been obsoleted and superseded by RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5. RFC 2684 specifies the implementation of point-to-point bridging of Layer 2 PDUs from an ATM interface.
•RFC 1483/RFC 2684 bridging with IEEE 802.1Q tunneling—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 keeping customer networks secure.
•RFC 1483/RFC 2684 half-bridging—Routes IP traffic from a stub-bridged Ethernet LAN over a bridged RFC 1483/RFC 2684 ATM interface, 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.
•ATM routed bridge encapsulation (RBE)—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.
•Bridging of routed encapsulations (BRE)—Enables an ATM SPA to receive RFC 1483/2684 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 forwarding engine to the Layer 2 interface determined by the VLAN number and destination MAC.
•Per VLAN Spanning Tree (PVST) to PVST+ Bridge Protocol Data Unit (BPDU) interoperability—PVST is a Cisco proprietary protocol that allows a Cisco device to support multiple spanning tree topologies on a per-VLAN basis. PVST uses the BPDUs defined in IEEE 802.1D, but instead of one STP instance per switch, there is one STP instance per VLAN. PVST+ is a Cisco proprietary protocol that creates one STP instance per VLAN (as in PVST). However, PVST+ enhances PVST and uses Cisco proprietary BPDUs with a special 802.2 Subnetwork Access Protocol (SNAP) Organizational Unique Identifier (OUI) instead of the standard IEEE 802.1D frame format used by PVST. PVST+ BPDUs are also known as Simple Symmetric Transmission Protocol (SSTP) BPDUs.
Table 4-6 provides information about where the bridging features for ATM SPA interfaces are supported. For more details about the implementation and information about configuring bridging for ATM SPA interfaces, see Chapter 8, "Configuring the ATM SPAs."
Table 4-6 Bridging for ATM Interfaces Feature Compatibility by SIP and SPA Combination
Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
RFC 1483/RFC 2684 Bridging for Point-to-Point PVCs (bridge-domain command)
|
In Cisco IOS Release 12.2(18)SXE and later, and in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
|
In Cisco IOS Release 12.2(18)SXE and later, and in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
•1-Port OC-12c/STM-4 ATM SPA
|
Not supported.
|
RFC 1483/RFC 2684 Bridging with IEEE 802.1Q Tunneling for Point-to-Point PVCs (bridge-domain dot1q-tunnel command)
|
In Cisco IOS Release 12.2(18)SXE and later, and in Cisco IOS Release 12.2(33)SRA and later:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
|
In Cisco IOS Release 12.2(18)SXE and later, and in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
•1-Port OC-12c/STM-4 ATM SPA
In Cisco IOS Release 12.2(18)SXF and Cisco IOS Release 12.2(33)SRA and later:
•1-Port OC-48c/STM-16 ATM SPA
|
Not supported.
|
RFC 1483/RFC 2684 Half-Bridging for Point-to-Multipoint PVCs
|
In Cisco IOS Release 12.2(18)SXE and later, and in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
|
Not supported.
|
Not supported.
|
RFC 1483/RFC 2684 Routed Bridge Encapsulation (RBE) for Point-to-Point PVCs
|
In Cisco IOS Release 12.2(18)SXE and later, and in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
|
Not supported.
|
Not supported.
|
RFC 1483/RFC 2684 Bridging of Routed Encapsulations (BRE) for PVCs
|
In Cisco IOS Release 12.2(18)SXE and later, and in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
|
Not supported.
|
Not supported.
|
Enhancements to RFC 1483/RFC 2684 Spanning Tree Interoperability (PVST to PVST+ BPDU Interoperability)
|
In Cisco IOS Release 12.2(18)SXF2 and later, and in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
|
In Cisco IOS Release 12.2(18)SXF2 and later, and in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
•1-Port OC-12c/STM-4 ATM SPA
•1-Port OC-48c/STM-16 ATM SPA
|
Not supported.
|
Multi-VLAN to VC
|
In Cisco IOS Release 12.2(18)SXE and later, and in Cisco IOS Release 12.2(33)SRA and later:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
|
In Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
•1-Port OC-12c/STM-4 ATM SPA
•1-Port OC-48c/STM-16 ATM SPA
|
Not supported.
|
Configuring Multipoint Bridging
Multipoint bridging (MPB) enables the connection of multiple ATM PVCs, Frame Relay PVCs, Bridge Control Protocol (BCP) ports, and WAN Gigabit Ethernet subinterfaces into a single broadcast domain (virtual LAN), together with the LAN ports on that VLAN. This enables service providers to add support for Ethernet-based Layer 2 services to the proven technology of their existing ATM and Frame Relay legacy networks. Customers can then use their current VLAN-based networks over the ATM or Frame Relay cloud. This also allows service providers to gradually update their core networks to the latest Gigabit Ethernet optical technologies, while still supporting their existing customer base.
ATM interfaces use RFC 1483/RFC 2684 bridging, and Frame Relay interfaces use RFC 1490/RFC 2427 bridging, both of which provide an encapsulation method to allow the transport of Ethernet frames over each type of Layer 2 network.
Beginning in Cisco IOS Release 12.2(33)SRA, MPB support is added on the Cisco 7600 SIP-400 to multiplex different VLANs that are configured across multiple Gigabit Ethernet subinterfaces into a single broadcast domain. Gigabit Ethernet interfaces can also reside on different Cisco 7600 SIP-400s and belong to the same bridge domain.
Table 4-7 provides information about where the MPB features for SPA interfaces are supported.
Table 4-7 MPB Feature Compatibility by SIP and SPA Combination
Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
MPB—60 VCs or interfaces per VLAN globally in system
|
In Cisco IOS Release 12.2(18)SXE and later:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
•2-Port and 4-Port Channelized T3 SPA
•2-Port and 4-Port Clear Channel T3/E3 SPA
•8-Port Channelized T1/E1 SPA
|
In Cisco IOS Release 12.2(18)SXE and later:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
•1-Port OC-12c/STM-4 ATM SPA
|
Not supported.
|
MPB—112 VCs or interfaces per VLAN on each SIP
Note If you are using Virtual Private LAN Service (VPLS), see the MPB configuration guidelines.
|
In Cisco IOS Release 12.2(33)SRA:
•1-Port Channelized OC-3/STM-1 SPA
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
•2-Port and 4-Port OC-3c/STM-1 POS SPA
•2-Port and 4-Port Channelized T3 SPA
•2-Port and 4-Port Clear Channel T3/E3 SPA
•8-Port Channelized T1/E1 SPA
|
Not applicable.
|
Not supported.
|
MPB—120 VCs or interfaces per VLAN on each SIP
Note If you are using VPLS, see the MPB bridging configuration guidelines.
|
Not supported.
|
In Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-3c/STM-1 ATM SPA
•1-Port OC-12c/STM-4 ATM SPA
•1-Port OC-48c/STM-16 ATM SPA
•2-Port and 4-Port OC-3c/STM-1 POS SPA
•1-Port OC-12c/STM-4 POS SPA
•1-Port OC-48c/STM-16 POS SPA
|
Not supported.
|
MPB on Gigabit Ethernet—Layer 2 bridging of frames between subinterfaces on different physical Gigabit Ethernet ports
|
Not supported.
|
In Cisco IOS Release 12.2(33)SRA:
•2-Port Gigabit Ethernet SPA
|
Not supported.
|
PIM snooping for MPB
|
Not supported.
|
Supported for all SPAs in Cisco IOS Release 12.2(33)SRA.
|
Not supported.
|
Configuring MPB for ATM PVCs
You can configure MPB manually on individual PVCs, or you can configure a range of PVCs to configure all of the PVCs at one time. ATM interfaces use RFC 1483/RFC 2684 bridging, which provides an encapsulation method to allow the transport of Ethernet frames over the Layer 2 network.
Note RFC 1483 has been obsoleted and superseded by RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5. To avoid confusion, this document continues to refer to the original RFC numbers.
MPB for ATM PVCs Configuration Guidelines
•Only ATM permanent virtual circuits (PVCs) are supported. SVCs are not supported.
•MPB is not supported on VLAN IDs 0, 1, 1002-1005, and 4095.
•Refer to Table 4-7 for limitations on the number of supported VCs.
•If you are using VPLS on a VC, then the total number of supported VC connection points for MPB (112 for the Cisco 7600 SIP-200, or 120 for the Cisco 7600 SIP-400) is reduced by one for each VPLS VC configured on that bridged VLAN. This reduces the total available number of VC connection points for MPB on that VLAN globally for that SIP. For example, if you configure 10 VPLS VCs on bridged VLAN 100, for a SPA on a Cisco 7600 SIP-200 in slot 4, then 10 connection points are allocated to the VPLS VCs for VLAN 100 across the SIP in slot 4. The total number of connection points available for MPB on VLAN 100 for the Cisco 7600 SIP-200 in slot 4 is 112 minus 10, or 102. A different VLAN (for example, VLAN 300) on that same Cisco 7600 SIP-200 in slot 4, without any VPLS VCs, will have the full 112 VCs available.
•Routing and bridging is supported on the same interface or subinterface, but for security reasons, routing and bridging is not supported on any given PVC. Therefore, you should not configure an IP address on a point-to-point subinterface and then configure bridging on a PVC on that subinterface.
•For a limited form of trunking on ATM PVCs supporting multiple VLANs to a single VC, you can configure dot1q tag. However, this configuration can lead to a performance penalty. When using this configuration, you can specify up to 32 bridge-domain command entries for a single PVC. The highest tag value in a group of bridge-domain commands must be greater than the first tag entered (but less than 32 greater than the first tag entered).
To configure MPB for ATM PVCs, perform the following steps beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# vlan {vlan-id | vlan-range}
|
Adds the specified VLAN IDs to the VLAN database and enters VLAN configuration mode, where:
•vlan-id—Specifies a single VLAN ID. The valid range is from 2 to 4094.
•vlan-range—Specifies multiple VLAN IDs, as either a list or a range. The vlan-range can contain a list of the VLAN IDs, separated by a comma (,), dash (-), or both.
Note Before you can use a VLAN for multipoint bridging, you must manually enter its VLAN ID into the VLAN database.
|
Step 2
|
Router(config)# interface atm slot/subslot/port
|
Specifies or creates an ATM interface, where:
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
|
Step 3
|
Router(config)# interface atm slot/subslot/port.subinterface {point-to-point | multipoint}
|
Specifies or creates a subinterface and enters subinterface configuration mode, where:
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
•.subinterface—Specifies the number of the subinterface on the interface port.
•point-to-point—Specifies a point-to-point subinterface.
•multipoint—Specifies a multipoint subinterface that allows multiple PVCs to use the same subinterface.
|
Step 4
|
Router(config-subif)# no ip address
|
Disables IP processing on the subinterface by removing its IP address.
|
Use the following commands (pvc and bridge-domain) to create and configure PVCs individually. Repeat these commands as desired. Or, use the range pvc and bridge-domain command with the increment keyword to configure a range of PVCs.
|
Step 5
|
Router(config-subif)# pvc [name] vpi/vci
or
Router(config-subif)# range [range-name] pvc start-vpi/start-vci end-vpi/end-vci
|
Configures a new ATM PVC or range of ATM PVCs with the specified VPI and VCI numbers and enters VC configuration mode or PVC range configuration mode, where:
•name—(Optional) Specifies the descriptive name to identify this PVC.
•vpi/vci—Specifies the virtual path identifier (VPI) and virtual channel identifier (VCI) for this PVC.
•range-name—(Optional) Specifies the descriptive name of the range, up to a maximum of 15 characters.
•start-vpi/—Specifies the beginning value for the range of virtual path identifiers (VPIs). The valid range is from 0 to 255, with a default of 0.
•start-vci—Specifies the beginning value for a range of virtual channel identifiers (VCIs). The valid range is from 32 to 65535.
•end-vpi/—Specifies the end value for the range of VPIs. The valid range is from 0 to 255, with a default that is equal to the start-vpi value.
•end-vci—Specifies the end value for a range of virtual channel identifiers (VCIs). The VCI value ranges from 32 to 65535.
|
Step 6
|
Router(config-if-atm-vc)# bridge-domain vlan-id [access | dot1q [tag]| dot1q-tunnel] [ignore-bpdu-pid] [pvst-tlv CE-vlan] [increment] [split-horizon]
|
Enables RFC 1483 bridging to map a bridged VLAN to an ATM PVC, where:
•vlan-id—Specifies the number of the VLAN to be used in this bridging configuration. The valid range is from 2 to 4094. The VLAN ID must have been previously added to the VLAN database in Step 1.
•access—(Optional) Enables access-only bridging access mode, in which the bridged connection does not transmit or act upon bridge protocol data unit (BPDU) packets.
•dot1q—(Optional) Enables IEEE 802.1Q tagging to preserve the class of service (CoS) information from the Ethernet frames across the ATM network. If not specified, the ingress side assumes a CoS value of 0 for QoS purposes. Using the dot1q keyword helps avoid misconfiguration because incoming untagged frames, or tagged frames that don't match the specified vlan-id are dropped.
•tag—(Optional—ATM PVCs only) Specifies the IEEE 802.1Q value in the range 1 to 4095. You can specify up to 32 bridge-domain command entries using dot1q tag for a single PVC. The highest tag value in a group of bridge-domain commands must be greater than the first tag entered (but less than 32 greater than the first tag entered).
•dot1q-tunnel—(Optional) Enables IEEE 802.1Q tunneling mode, so that service providers can use a single VLAN to support customers who have multiple VLANs, while preserving customer VLAN IDs and keeping traffic in different customer VLANs segregated.
Note The access, dot1q, and dot1q-tunnel options are mutually exclusive. If you do not specify any of these options, the connection operates in "raw" bridging access mode, which is similar to access, except that the connection processes and transmits BPDU packets.
•ignore-bpdu-pid—(Optional—ATM PVCs only) Ignores the protocol-ID field in RFC 1497 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.
|
| |
|
•pvst-tlv CE-vlan—(Optional) When transmitting, translates PVST+ BPDUs into IEEE BPDUs. When receiving, translates IEEE BPDUs into PVST+ BPDUs. CE-vlan specifies the customer-edge VLAN in the SSTP Tag-Length-Value (TLV) to be inserted in an IEEE BPDU to a PVST+ BPDU conversion.
•increment—(Optional—PVC range configuration mode only) Increments the bridge domain number for each PVC in the range. This keyword is used when you are configuring a range of PVCs using the range pvc command.
•split-horizon—(Optional) Drops egress traffic going out a VC or interface with split-horizon configured, that arrived on an interface with split-horizon configured.
|
Verifying MPB for ATM PVCs
To display information about the PVCs that have been configured on ATM interfaces, use the following commands:
•show atm pvc—Displays a summary of the PVCs that have been configured.
•show atm vlan—Displays the connections between PVCs and VLANs.
Note Use the show atm vlan command instead of the show interface trunk command to display information about ATM interfaces being used for multipoint bridging.
The following shows an example of each command:
Interface Name VPI VCI Type Encaps SC Kbps Kbps Cells Sts
5/0/0 1 0 102 PVC SNAP UBR 599040 UP
5/0/0 2 0 103 PVC SNAP UBR 599040 UP
5/0/0 3 0 111 PVC SNAP UBR 599040 UP
5/0/0 3 0 111 PVC SNAP UBR 599040 UP
5/0/0 3 0 111 PVC SNAP UBR 599040 UP
Options Legend: DQ - dot1q; DT - dot1q-tunnel; MD - multi-dot1q;
AC - access; SP - split-horizon; BR - broadcast;
Interface VCD VPI Network Customer PVC Options
/VCI Vlan ID Dot1Q-ID Status
ATM5/0/0 1 0/102 102 1002 UP MD
ATM5/0/0 2 0/103 103 1003 UP MD
ATM5/0/0 3 0/111 111 1111 UP MD
ATM5/0/0 3 0/111 112 1112 UP MD
ATM5/0/0 3 0/111 113 1113 UP MD
Configuring MPB for Frame Relay
You can configure MPB for Frame Relay on individual DLCI circuits. You can optionally add 802.1Q tagging or 802.1Q tunneling. Frame Relay interfaces use RFC 1490/RFC 2427 bridging, which provides an encapsulation method to allow the transport of Ethernet frames over the Layer 2 network.
Note RFC 1490 has been obsoleted and superseded by RFC 2427, Multiprotocol Interconnect over Frame Relay. To avoid confusion, this document continues to refer to the original RFC numbers.
MPB for Frame Relay Configuration Guidelines
•Multipoint bridging on Frame Relay interfaces supports only IETF encapsulation. Cisco encapsulation is not supported for MPB.
•MPB is not supported on VLAN IDs 0, 1, 1002-1005, and 4095.
•Refer to Table 4-7 for limitations on the number of supported VCs.
•If you are using VPLS, then the total number of supported DLCI connection points for MPB (112 for the Cisco 7600 SIP-200, or 120 for the Cisco 7600 SIP-400) is reduced by one for each VPLS instance configured on that bridged VLAN. This reduces the total available number of DLCI connection points for MPB on that VLAN globally for that SIP. For example, if you configure 10 VPLS instances on a bridged VLAN 100, for a SPA on a Cisco 7600 SIP-200 in slot 4, then 10 connection points are allocated to the VPLS instances for VLAN 100 across the SIP in slot 4. The total number of connection points available for MPB on VLAN 100 for the Cisco 7600 SIP-200 in slot 4 is 112 minus 10, or 102. A different VLAN (for example, VLAN 300) on that same Cisco 7600 SIP-200 in slot 4, without any VPLS DLCIs, will have the full 112 DLCIs available.
•Routing and bridging is supported on the same interface or subinterface, but for security reasons, routing and bridging is not supported on any given DLCI. Therefore, you should not configure an IP address on a point-to-point subinterface and then configure bridging on a DLCI on that subinterface.
To configure MPB for Frame Relay on serial or POS SPAs, perform the following steps beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# vlan {vlan-id | vlan-range}
|
Adds the specified VLAN IDs to the VLAN database and enters VLAN configuration mode, where:
•vlan-id—Specifies a single VLAN ID. The valid range is from 2 to 4094.
•vlan-range—Specifies multiple VLAN IDs, as either a list or a range. The vlan-range can contain a list of the VLAN IDs, separated by a comma (,), dash (-), or both.
Note Before you can use a VLAN for multipoint bridging, you must manually enter its VLAN ID into the VLAN database.
|
Step 2
|
Router(config)# interface serial slot/subslot/port
or
Router(config)# interface pos slot/subslot/port
|
Specifies or creates a serial or POS interface, where:
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
|
Step 3
|
Router(config-if) encapsulation frame-relay ietf
|
Enables Frame Relay encapsulation on the interface, using IETF encapsulation. You must specify the ietf keyword either here or in Step 6 for each individual DLCI.
Note Multipoint bridging does not support Cisco encapsulation using the cisco keyword.
|
Step 4
|
2-Port and 4-Port Clear Channel T3/E3 SPA
Router(config)# interface serial slot/subslot/port.subinterface {point-to-point | multipoint}
2-Port and 4-Port Channelized T3 SPA
Router(config)# interface serial slot/subslot/port/t1-number:channel-
group.subinterface {point-to-point | multipoint}
8-Port Channelized T1/E1 SPA
Router(config)# interface serial slot/subslot/port:channel-group.subinterface {point-to-point | multipoint}
|
Specifies or creates a subinterface and enters subinterface configuration mode, where:
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
•.subinterface—Specifies the number of the subinterface on the interface port.
•t1-number—Specifies the logical T1 number in channelized mode.
|
| |
1-Port OC-12c/STM-4 POS SPA or 2-Port and 4-Port OC-3c/STM-1 POS SPA
Router(config)# interface pos slot/subslot/port.subinterface {point-to-point | multipoint}
|
•channel-group—Specifies the logical channel group assigned to the time slots within the T1 or E1 group.
•point-to-point—Specifies a point-to-point subinterface.
•multipoint—Allows multiple PVCs to use the same subinterface.
|
Step 5
|
Router(config-subif)# no ip address
|
Disables IP processing on a particular interface by removing its IP address.
|
Step 6
|
Router(config-subif)# frame-relay interface-dlci dlci [ietf]
|
Creates the specified DLCI on the subinterface and enters DLCI configuration mode, where:
•dlci—Specifies the DLCI number to be used on the specified subinterface.
•ietf—(Optional) Specifies IETF encapsulation. This option is required if you did not specify IETF encapsulation in Step 4.
Note This command includes other options that are not supported when using multipoint bridging.
|
Step 7
|
Router(config-fr-dlci)# bridge-domain vlan-id [access | dot1q | dot1q-tunnel] [pvst-tlv CE-vlan] [split-horizon]
|
Enables RFC 1490 bridging to map a bridged VLAN to a Frame Relay DLCI, where:
•vlan-id —Specifies the number of the VLAN to be used in this bridging configuration. The valid range is from 2 to 4094. The VLAN ID must have been previously added to the VLAN database in Step 1.
•access—(Optional) Enables access-only bridging access mode, in which the bridged connection does not transmit or act upon bridge protocol data unit (BPDU) packets.
•dot1q—(Optional) Enables IEEE 802.1Q tagging to preserve the class of service (CoS) information from the Ethernet frames across the Frame Relay network. If not specified, the ingress side assumes a CoS value of 0 for QoS purposes. Using the dot1q keyword helps avoid misconfiguration because incoming untagged frames, or tagged frames that do not match the specified vlan-id are dropped.
•dot1q-tunnel—(Optional) Enables IEEE 802.1Q tunneling mode, so that service providers can use a single VLAN to support customers who have multiple VLANs, while preserving customer VLAN IDs and keeping traffic in different customer VLANs segregated.
|
| |
|
Note The access, dot1q, and dot1q-tunnel options are mutually exclusive. If you do not specify any of these options, the connection operates in "raw" bridging access mode, which is similar to access, except that the connection processes and transmits BPDU packets.
•pvst-tlv CE-vlan—(Optional) When transmitting, translates PVST+ BPDUs into IEEE BPDUs. When receiving, translates IEEE BPDUs into PVST+ BPDUs. CE-vlan specifies the customer-edge VLAN in the SSTP Tag-Length-Value (TLV) to be inserted in an IEEE BPDU to a PVST+ BPDU conversion.
•split-horizon—(Optional) Drops egress traffic going out a VC or interface with split-horizon configured, that arrived on an interface with split-horizon configured.
|
| |
|
|
Verifying MPB for Frame Relay
To display information about the DLCIs that have been configured on Frame Relay interfaces, use the show frame-relay vlan command.
Router# show frame-relay vlan
Interface Bridge DLCI Domain
Configuring MPB for Gigabit Ethernet
Beginning in Cisco IOS Release 12.2(33)SRA, MPB support is added on the Cisco 7600 SIP-400 to multiplex different VLANs that are configured across multiple Gigabit Ethernet subinterfaces into a single broadcast domain. Gigabit Ethernet interfaces can also reside on different Cisco 7600 SIP-400s and belong to the same bridge domain.
MPB for Gigabit Ethernet Configuration Guidelines
•The Cisco 7600 SIP-400 can support a total of up to 4096 subinterfaces and bridge-domain instances per VLAN. For example, one subinterface with a configured VLAN using MPB will consume two of the available 4096 total allowable subinterfaces and bridge domains combined.
•Up to 60 subinterfaces can be put into the same bridge domain on the Cisco 7600 SIP-400.
To configure MPB for Gigabit Ethernet, perform the following steps beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# vlan {vlan-id | vlan-range}
|
Adds the specified VLAN IDs to the VLAN database and enters VLAN configuration mode, where:
•vlan-id—Specifies a single VLAN ID. The valid range is from 2 to 4094.
•vlan-range—Specifies multiple VLAN IDs, as either a list or a range. The vlan-range can contain a list of the VLAN IDs, separated by a comma (,), dash (-), or both.
Note Before you can use a VLAN for multipoint bridging, you must manually enter its VLAN ID into the VLAN database.
|
Step 2
|
Router(config)# interface gigabitethernet slot/subslot/port.subinterface
|
Specifies or creates a Gigabit Ethernet subinterface and enters subinterface configuration mode, where:
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
•.subinterface—Specifies the number of the subinterface on the interface port.
|
Step 3
|
Router(config-subif) encapsulation dot1q vlan-id
|
Enables IEEE 802.1Q encapsulation on the interface, where vlan-id specifies the virtual LAN identifier. The allowed range is from 1 to 4095.
|
Step 4
|
Router(config-subif)# bridge-domain vlan-id [dot1q | dot1q-tunnel] [bpdu {drop | transparent}] [split-horizon]
|
Enables bridging of VLANs across Gigabit Ethernet subinterfaces, where:
•vlan-id —Specifies the number of the VLAN to be used in this bridging configuration. The valid range is from 2 to 4094. The VLAN ID must have been previously added to the VLAN database in Step 1.
•dot1q—(Optional) Enables IEEE 802.1Q tagging to preserve the class of service (CoS) information from the Ethernet frames across the ATM network. If not specified, the ingress side assumes a CoS value of 0 for QoS purposes.
•dot1q-tunnel—(Optional) Enables IEEE 802.1Q tunneling mode, so that service providers can use a single VLAN to support customers who have multiple VLANs, while preserving customer VLAN IDs and keeping traffic in different customer VLANs segregated.
Note The dot1q and dot1q-tunnel options are mutually exclusive. If you do not specify either of these options, the connection operates in "raw" bridging access mode, which is similar to access, except that the connection processes and transmits BPDU packets.
•bpdu {drop | transparent}—(Optional) Specifies whether or not BPDUs are processed or dropped, where:
–drop—Specifies BPDU packets are dropped on the subinterface.
–transparent—Specifies BPDU packets are forwarded as data on the subinterface, but not processed.
•split-horizon—(Optional) Drops egress traffic going out a VC or interface with split-horizon configured, that arrived on an interface with split-horizon configured.
|
Configuring PPP Bridging Control Protocol Support
The Bridging Control Protocol (BCP) feature on the SIPs and SPAs enables forwarding of Ethernet frames over serial and SONET networks, and provides a high-speed extension of enterprise LAN backbone traffic through a metropolitan area. The implementation of BCP on the SPAs includes support for IEEE 802.1D Spanning Tree Protocol, IEEE 802.1Q Virtual LAN (VLAN), and high-speed switched LANs.
The Bridging Control Protocol (BCP) feature provides support for BCP to Cisco devices, as described in RFC 3518, Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP). The Cisco implementation of BCP is a VLAN infrastructure that does not require the use of subinterfaces to group Ethernet 802.1Q trunks and the corresponding PPP links. This approach enables users to process VLAN encapsulated packets without having to configure subinterfaces for every possible VLAN configuration.
BCP operates in two different modes:
•Trunk mode BCP (switchport)—A single BCP link can carry multiple VLANs.
•Single-VLAN BCP (bridge-domain)—A single BCP link carries only one VLAN.
In addition, in Cisco IOS Release 12.2(33)SRA, BCP is supported over dMLPPP links on the Cisco 7600 SIP-200 with the 2-Port and 4-Port Channelized T3 SPA and 8-Port Channelized T1/E1 SPA. BCP over dMLPPP is supported in trunk mode only.
BCP Feature Compatibility
Table 4-8 provides information about where the BCP features are supported.
Table 4-8 BCP Feature Compatibility by SIP and SPA Combination
Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Trunk mode BCP (switchport)
|
In Cisco IOS Release 12.2(18)SXE and later:
•2-Port and 4-Port Channelized T3 SPA
•2-Port and 4-Port Clear Channel T3/E3 SPA
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port OC-3c/STM-1 POS SPA
Support for the following SPA was added in Cisco IOS Release 12.2(33)SRA:
•1-Port Channelized OC-3/STM-1 SPA
|
In Cisco IOS Release 12.2(18)SXE and later:
•1-Port OC-12c/STM-4 POS SPA
•2-Port and 4-Port OC-3c/STM-1 POS SPA
•1-Port OC-48c/STM-16 POS SPA
|
Not supported.
|
| |
|
|
|
Tag-native Mode for Trunk BCP (switchport)
|
•In Cisco IOS 12.2SX releases—Not supported.
•In Cisco IOS Release 12.2(33)SRA:
–2-Port and 4-Port Channelized T3 SPA
–2-Port and 4-Port Clear Channel T3/E3 SPA
–8-Port Channelized T1/E1 SPA
–2-Port and 4-Port OC-3c/STM-1 POS SPA
–1-Port Channelized OC-3/STM-1 SPA
|
•In Cisco IOS 12.2SX releases—Not supported.
•In Cisco IOS Release 12.2(33)SRA:
–1-Port OC-12c/STM-4 POS SPA
–2-Port and 4-Port OC-3c/STM-1 POS SPA
–1-Port OC-48c/STM-16 POS SPA
|
Not supported.
|
Single-VLAN BCP (bridge-domain)
|
In Cisco IOS Release 12.2(18)SXE and later:
•2-Port and 4-Port Channelized T3 SPA
•2-Port and 4-Port Clear Channel T3/E3 SPA
•8-Port Channelized T1/E1 SPA
•2-Port and 4-Port OC-3c/STM-1 POS SPA
Support for the following SPA was added in In Cisco IOS Release 12.2(33)SRA:
•1-Port Channelized OC-3/STM-1 SPA
|
In Cisco IOS Release 12.2(33)SRA:
•1-Port OC-12c/STM-4 POS SPA
•2-Port and 4-Port OC-3c/STM-1 POS SPA
•1-Port OC-48c/STM-16 POS SPA
|
Not supported.
|
BCP over dMLPPP (trunk mode only)
|
In Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port Channelized T3 SPA
•8-Port Channelized T1/E1 SPA
|
Not supported.
|
Not supported.
|
BCP Configuration Guidelines
When configuring BCP support for SPAs on the Cisco 7600 SIP-200 and Cisco 7600 SIP-400, consider the following guidelines:
•Be sure to refer to Table 4-8 for feature compatibility information.
•Beginning in Cisco IOS Release 12.2(33)SRA, QoS is supported on bridged interfaces. In Cisco IOS Release 12.2(18)SXF2 and earlier, QoS is not supported on bridged interfaces.
•Although RFC 3518 specifies support for Token Ring and Fiber Distributed Data Interface (FDDI), BCP on the Cisco 7600 SIP-200 and Cisco 7600 SIP-400 supports only Ethernet currently.
Configuring BCP in Trunk Mode
When BCP is configured in trunk mode, a single BCP link can carry multiple VLANs. This usage of BCP is consistent with that of normal Ethernet trunk ports.
Trunk Mode BCP Configuration Guidelines
When configuring BCP support in trunk mode for SPAs on the Cisco 7600 SIP-200 and Cisco 7600 SIP-400, consider the following guidelines:
•Be sure to refer to Table 4-8 for feature compatibility information.
•There are some differences between the Ethernet trunk ports and BCP trunk ports.
–Ethernet trunk ports support ISL and 802.1Q encapsulation, but BCP trunk ports support only 802.1Q.
–Ethernet trunk ports support Dynamic Trunk Protocol (DTP), which is used to automatically determine the trunking status of the link. BCP trunk ports are always in trunk state and no DTP negotiation is performed.
–The default behavior of Ethernet trunk ports is to allow all VLANs on the trunk. The default behavior of BCP trunks is to disallow all VLANs. This means that VLANs that need to be allowed have to be explicitly configured on the BCP trunk port.
•Use the switchport command under the WAN interface when configuring trunk mode BCP.
•The SIPs support the following maximum number of BCP ports on any given VLAN:
–In Cisco IOS Release 12.2(18)SXE and later—Maximum of 60 BCP ports
–In Cisco IOS Release 12.2(33)SRA—Maximum of 112 BCP ports on Cisco 7600 SIP-200 and maximum of 120 BCP ports on Cisco 7600 SIP-400.
•To use VLANs in trunk mode BCP, you must use the vlan command to manually add the VLANs to the VLAN database. The default behavior for trunk mode BCP allows no VLANs.
•Trunk mode BCP is not supported on VLAN IDs 0, 1006-1023, and 1025.
•The native VLAN (VLAN1) has the following restrictions for trunk mode BCP:
–In Cisco IOS Release 12.2SX—The native VLAN is not supported.
–Beginning in Cisco IOS Release 12.2(33)SRA—The native VLAN is supported.
•For trunk mode BCP (switchport), STP interoperability is the same as that of Ethernet switchports. This means that the STP path cost of WAN links can be changed and other STP functionality such as BPDU Guard and PortFast will work on the WAN links. However, it is not recommended to change the default values.
•VLAN Trunking Protocol (VTP) is supported.
Note The management VLAN, VLAN 1, must be explicitly enabled on the trunk to send VTP advertisements.
To configure BCP in trunk mode, perform the following steps beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# vlan dot1q tag native
|
(Optional) Enables dot1q tagging for all VLANs in a trunk. By default, packets on the native VLAN are sent untagged. When you enable dot1q tagging, packets are tagged with the native VLAN ID.
|
Step 2
|
1-Port Channelized OC-3/STM-1 SPA
Router(config)# interface serial address
2-Port and 4-Port Channelized T3 SPA
Router(config)# interface serial slot/subslot/port/t1-number:channel-group
8-Port Channelized T1/E1 SPA
Router(config)# interface serial slot/subslot/port:channel-group
1-Port OC-12c/STM-4 POS SPA or 2-Port and 4-Port OC-3c/STM-1 POS SPA
Router(config)# interface pos slot/subslot/port
|
Specifies an interface and enters interface configuration mode, where:
•address—For the different supported syntax options for the address argument for the 1-Port Channelized OC-3/STM-1 SPA, refer to the "Interface Naming" section of the "Configuring the 1-Port Channelized OC-3/STM-1 SPA" chapter.
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
•t1-number—Specifies the logical T1 number in channelized mode.
•channel-group—Specifies the logical channel group assigned to the time slots within the T1 or E1 group.
|
Step 3
|
Router(config-if)# switchport
|
Puts an interface that is in Layer 3 mode into Layer 2 mode for Layer 2 configuration. PPP encapsulation is automatically configured, and the interface is automatically configured for trunk mode and nonegotiate status.
|
Step 4
|
Router(config-if)# shutdown
|
Disables the interface.
|
Step 5
|
Router(config-if)# no shutdown
|
Restarts the disabled interface.
|
Step 6
|
Router(config-if)# switchport trunk allowed vlan {all | {add | remove | except} vlan-list [,vlan-list...] | vlan-list [,vlan-list...]}
|
(Optional) Controls which VLANs can receive and transmit traffic on the trunk, where:
•all—Enables all applicable VLANs.
•add vlan-list [,vlan-list...]—Appends the specified list of VLANs to those currently set instead of replacing the list.
•remove vlan-list [,vlan-list...]—Removes the specified list of VLANs from those currently set instead of replacing the list.
•except vlan-list [,vlan-list...]—Excludes the specified list of VLANs from those currently set instead of replacing the list.
•vlan-list [,vlan-list...]—Specifies a single VLAN number from 1 to 4094, or a continuous range of VLANs that are described by two VLAN numbers from 1 to 4094. You can specify multiple VLAN numbers or ranges using a comma-separated list.
To specify a range of VLANs, enter the smaller VLAN number first, separated by a hyphen and the larger VLAN number at the end of the range.
Note Do not enable the reserved VLAN range (1006 to 1024) on trunks when connecting a Cisco 7600 series router running the Cisco IOS software on both the supervisor engine and the MSFC to a Cisco 7600 series router running the Catalyst operating system. These VLANs are reserved in Cisco 7600 series routers running the Catalyst operating system. If enabled, Cisco 7600 series routers running the Catalyst operating system may error-disable the ports if there is a trunking channel between these systems.
|
Verifying BCP in Trunk Mode
Because the PPP link has to flap (be brought down and renegotiated), it is important that you run the following show commands after you configure BCP in trunk mode to confirm the configuration:
Command
|
Purpose
|
1-Port Channelized OC-3/STM-1 SPA
Router# show interfaces [serial address] trunk [module number]
2-Port and 4-Port Channelized T3 SPA
Router# show interfaces [serial slot/subslot/port/t1-number:channel-group] trunk [module number]
8-Port Channelized T1/E1 SPA
Router# show interfaces [serial slot/subslot/port:channel-group] trunk [module number]
1-Port OC-12c/STM-4 POS SPA or 2-Port and 4-Port OC-3c/STM-1 POS SPA
Router# show interfaces [pos slot/subslot/port] trunk [module number]
|
Displays the interface-trunk information, where:
•address—For the different supported syntax options for the address argument for the 1-Port Channelized OC-3/STM-1 SPA, refer to the "Interface Naming" section of the "Configuring the 1-Port Channelized OC-3/STM-1 SPA" chapter.
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
•t1-number—Specifies the logical T1 number in channelized mode.
•channel-group—Specifies the logical channel group assigned to the time slots within the T1 or E1 group.
•module number—(Optional) Specifies the chassis slot number of the SIP and displays information for all interfaces of the SPAs in that SIP.
|
Command
|
Purpose
|
1-Port Channelized OC-3/STM-1 SPA
Router# show interfaces [serial address] switchport [module number]
2-Port and 4-Port Channelized T3 SPA
Router# show interfaces [serial slot/subslot/port/t1-number:channel-group] switchport [module number]
8-Port Channelized T1/E1 SPA
Router# show interfaces [serial slot/subslot/port:channel-group] switchport [module number]
1-Port OC-12c/STM-4 POS SPA or 2-Port and 4-Port OC-3c/STM-1 POS SPA
Router# show interfaces [pos slot/subslot/port] switchport [module number]
|
Displays the administrative and operational status of a switching (nonrouting) port, where:
•address—For the different supported syntax options for the address argument for the 1-Port Channelized OC-3/STM-1 SPA, refer to the "Interface Naming" section of the "Configuring the 1-Port Channelized OC-3/STM-1 SPA" chapter.
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
•t1-number—Specifies the logical T1 number in channelized mode.
•channel-group—Specifies the logical channel group assigned to the time slots within the T1 or E1 group.
•module number—(Optional) Specifies the chassis slot number of the SIP and displays information for all interfaces of the SPAs in that SIP.
|
The following output of the show interfaces commands provide an example of the information that is displayed when BCP is configured in trunk mode.
Note When switchport is configured, the encapsulation is automatically changed to PPP.
Router# show interfaces trunk
Port Mode Encapsulation Status Native vlan
PO4/1/0 on 802.1q trunking 1
Port Vlans allowed on trunk
PO4/1/0 1-1005,1025-1026,1028-4094
Port Vlans allowed and active in management domain
Port Vlans in spanning tree forwarding state and not pruned
Router# show interfaces switchport
Administrative Mode: trunk
Administrative Trunking Encapsulation: dot1q
Negotiation of Trunking: Off
Access Mode VLAN: 1 (default)
Trunking Native Mode VLAN: 1 (default)
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk private VLANs: none
Operational private-vlan: none
Trunking VLANs Enabled: 100
Pruning VLANs Enabled: 2-1001
Capture VLANs Allowed: ALL
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Router# show interfaces pos4/1/0
POS4/1/0 is up, line protocol is up
Hardware is Packet over Sonet
MTU 4470 bytes, BW 155000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, crc 16, loopback not set
Last input 00:00:05, output 00:00:05, output hang never
Last clearing of "show interface" counters 18:48:09
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Output queue: 0/40 (size/max)
5 minute input rate 1000 bits/sec, 1 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
13161719 packets input, 1145463122 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1685 packets output, 620530 bytes, 0 underruns
0 output errors, 0 applique, 30 interface resets
0 output buffer failures, 0 output buffers swapped out
Configuring BCP in Single-VLAN Mode
When BCP is configured in single-VLAN mode, a single BCP link carries only one VLAN. This is considered BCP in access mode.
Single-VLAN Mode BCP Configuration Guidelines
When configuring BCP support in single-VLAN mode for SPAs on the Cisco 7600 SIP-200 and Cisco 7600 SIP-400, consider the following guidelines:
•Be sure to refer to Table 4-8 for feature compatibility information.
•Use the bridge-domain vlan-id dot1q form of the command under a WAN interface or an ATM PVC. The dot1q keyword is necessary. It indicates that all frames on the BCP link will be tagged with a 802.1Q header. Untagged frames received on a BCP link will be dropped.
•For serial and POS SPA interfaces, the encapsulation of the interface must be PPP; otherwise, the bridge-domain command will not be accepted.
•The ATM SPAs on the Cisco 7600 series router do not support single-VLAN BCP.
•For single-VLAN BCP, you can configure the following maximum number of VCs per VLAN:
–In Cisco IOS Release 12.2SX—60 VCs or interfaces per VLAN per chassis.
–Beginning in Cisco IOS Release 12.2(33)SRA—112 VCs or interfaces per VLAN per Cisco 7600 SIP-200; 120 VCs or interfaces per VLAN per Cisco 7600 SIP-400.
•VLANs must be manually added to the VLAN database, using the vlan command, to be able to use those VLANs in single-VLAN BCP.
•BCP is not supported on VLAN IDs 0, 1 (native), 1006-1023, and 1025.
•For single-VLAN BCP, only basic Spanning Tree Protocol (STP) interoperability is supported. This means that single-VLAN BCP interfaces will participate in the STP domain and the correct path cost of the links will be calculated; however, changing any STP parameters for the link is not supported.
•VLAN Trunking Protocol (VTP) is not supported on single-VLAN BCP.
To configure BCP in single-VLAN mode on serial or POS SPAs, perform the following steps beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
1-Port Channelized OC-3/STM-1 SPA
Router(config)# interface serial address
2-Port and 4-Port Channelized T3 SPA
Router(config)# interface serial slot/subslot/port/t1-number:channel-group
8-Port Channelized T1/E1 SPA
Router(config)# interface serial slot/subslot/port:channel-group
1-Port OC-12c/STM-4 POS SPA or 2-Port and 4-Port OC-3c/STM-1 POS SPA
Router(config)# interface pos slot/subslot/port
|
Specifies an interface and enters interface configuration mode, where:
•address—For the different supported syntax options for the address argument for the 1-Port Channelized OC-3/STM-1 SPA, refer to the "Interface Naming" section of the "Configuring the 1-Port Channelized OC-3/STM-1 SPA" chapter.
•slot—Specifies the chassis slot number where the SIP is installed.
•subslot—Specifies the secondary slot number on a SIP where a SPA is installed.
•port—Specifies the number of the interface port on the SPA.
•t1-number—Specifies the logical T1 number in channelized mode.
•channel-group—Specifies the logical channel group assigned to the time slots within the T1 or E1 group.
|
Step 2
|
Router(config-if)# no ip address
|
Disables IP processing on a particular interface by removing its IP address.
|
Step 3
|
Router(config-if)# encapsulation ppp
|
Configures the interface for PPP encapsulation.
|
Step 4
|
Router(config-if)# bridge-domain vlan-id [dot1q | dot1q-tunnel]
|
Establishes a domain and tags all Ethernet frames on the BCP link with the 802.1Q header, where:
•vlan-id—Specifies the number of the VLAN to be used in this bridging configuration. The valid range is from 2 to 4094. The VLAN ID must have been previously added to the VLAN database.
•dot1q—(Optional) Enables IEEE 802.1Q tagging to preserve the class of service (CoS) information from the Ethernet frames across the WAN interface. If not specified, the ingress side assumes a CoS value of 0 for QoS purposes. Using the dot1q keyword helps avoid misconfiguration because incoming untagged frames, or tagged frames that do not match the specified vlan-id are dropped.
•dot1q-tunnel—(Optional) Enables IEEE 802.1Q tunneling mode, so that service providers can use a single VLAN to support customers who have multiple VLANs, while preserving customer VLAN IDs and keeping traffic in different customer VLANs segregated.
|
Step 5
|
Router(config-if)# shutdown
|
Disables the interface.
|
Step 6
|
Router(config-if)# no shutdown
|
Restarts the disabled interface.
|
Verifying BCP in Single-VLAN Mode
Because the PPP link has to flap (be brought down and renegotiated), it is important that you run the following show command after you configure BCP in single-VLAN mode to confirm the configuration:
Router# show interfaces pos4/1/0
POS4/1/0 is up, line protocol is up
Hardware is Packet over Sonet
MTU 4470 bytes, BW 155000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation PPP, crc 16, loopback not set
Last input 00:00:09, output 00:00:09, output hang never
Last clearing of "show interface" counters 00:00:24
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1
Output queue: 0/40 (size/max)
5 minute input rate 1000 bits/sec, 1 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
32 packets input, 1709 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicast)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
17 packets output, 1764 bytes, 0 underruns
0 output errors, 0 applique, 3 interface resets
0 output buffer failures, 0 output buffers swapped out
Configuring BCP over dMLPPP
Beginning in Cisco IOS Release 12.2(33)SRA, BCP is supported over dMLPPP links on the Cisco 7600 SIP-200 with the 2-Port and 4-Port Channelized T3 SPA and 8-Port Channelized T1/E1 SPA. BCP over dMLPPP is supported in trunk mode only.
For more information about configuring the BCP over dMLPPP feature, see Chapter 22, "Configuring the 8-Port Channelized T1/E1 SPA," and Chapter 24, "Configuring the 2-Port and 4-Port Channelized T3 SPAs."
Configuring Virtual Private LAN Service
Virtual Private LAN Service (VPLS) enables geographically separate LAN segments to be interconnected as a single bridged domain over a packet switched network, such as IP, MPLS, or a hybrid of both.
VPLS solves the network reconfiguration problems at the CE that are associated with Layer 2 Virtual Private Network (L2VPN) implementations. The current Cisco IOS software L2VPN implementation builds a point-to-point connection to interconnect the two attachment VCs of two peering customer sites. To communicate directly among all sites of an L2VPN network, a distinct emulated VC needs to be created between each pair of peering attachment VCs. For example, when two sites of the same L2VPN network are connected to the same PE, it requires that two separate emulated VCs be established towards a given remote site, instead of sharing a common emulated VC between these two sites. For a L2VPN customer who uses the service provider backbone to interconnect its LAN segments, the current implementation effectively turns its multiaccess broadcast network into a fully meshed point-to-point network, which requires extensive reconfiguration on the existing CE devices.
VPLS is a multipoint L2VPN architecture that connects two or more customer devices using EoMPLS bridging techniques. VPLS with EoMPLS uses an MPLS-based provider core, where the PE routers have to cooperate to forward customer Ethernet traffic for a given VPLS instance in the core.
VPLS uses the provider core to join multiple attachment circuits together to simulate a virtual bridge that connects the multiple attachment circuits together. From a customer point of view, there is no topology for VPLS. All of the CE devices appear to connect to a logical bridge emulated by the provider core.
Hierarchical Virtual Private LAN Service with MPLS to the Edge
In a flat or non-hierarchical VPLS configuration, a full mesh of pseudowires (PWs) is needed between all PE nodes. A pseudowire defines a VLAN and its corresponding pseudoport.
Hierarchical Virtual Private LAN Service (H-VPLS) reduces both signaling and replication overhead by using a combination of full-mesh and hub-and-spoke configurations. Hub-and-spoke configurations operate with split horizon to allow packets to be switched between pseudowires (PWs), which effectively reduce the number of PWs between PEs.
Figure 4-3 H-VPLS with MPLS to the Edge Network
In the H-VPLS with MPLS to the edge architecture, Ethernet Access Islands (EAIs) work in combination with a VPLS core network, with MPLS as the underlying transport mechanism. EAIs operate like standard Ethernet networks. In Figure 4-3, devices CE1, CE2a and CE2b reside in an EAI. Traffic from any CE devices within the EAI are switched locally within the EAI by the user-facing provider edge (UPE) device along the computed spanning-tree path. Each user-facing provider edge device is connected to one or more network-facing provider edge devices using PWs. The traffic local to the UPE is not forward to any network-facing provider edge devices.
VPLS Configuration Guidelines
When configuring VPLS on a SIP, consider the following guidelines:
•For support of specific VPLS features by SIP, see Table 4-9.
•The SIPs support up to 4000 VPLS domains per Cisco 7600 series router.
•The SIPs support up to 60 VPLS peers per domain per Cisco 7600 series router.
•The SIPs support up to 30,000 pseudowires, used in any combination of domains and peers up to the 4000-domain or 60-peer maximums. For example, support of up to 4000 domains with 7 peers, or up to 60 peers in 500 domains.
•When configuring VPLS on a Cisco 7600 SIP-600, consider the following guidelines:
–Q-in-Q (the ability to map a single 802.1Q tag or a random double tag combination into a VPLS instance, a Layer 3 MPLS VPN, or an EoMPLS VC) is not supported.
–H-VPLS with Q-in-Q edge—Requires a Cisco 7600 SIP-600 in the uplink, and any LAN port or Cisco 7600 SIP-600 on the downlink.
•H-VPLS with MPLS edge requires either an OSM module, Cisco 7600 SIP-600, or Cisco 7600 SIP-400 in both the downlink (facing UPE) and uplink (MPLS core).
•The Cisco 7600 SIP-400 and Cisco 7600 SIP-600 provide Transparent LAN Services (TLS) and Ethernet Virtual Connection Services (EVCS).
•The Cisco 7600 SIP-400 does not support redundant PW links from a UPE to multiple NPEs.
•For information about configuring VPLS on the SIPs, consider the guidelines in this document and then refer to the "Virtual Private LAN Services on the Optical Services Modules" section of the Optical Services Module Software Configuration Note for the Cisco 7600 series router at the following URL:
http://www.cisco.com/application/pdf/en/US/guest/products/ps368/c1069/ccmigration_09186a008069bfcc.pdf
VPLS Feature Compatibility
Table 4-9 provides information about where the VPLS features are supported.
Table 4-9 VPLS Feature Compatibility by SIP and SPA Combination
Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
H-VPLS with MPLS edge
|
Not supported.
|
In Cisco IOS Release 12.2(33)SRA:
•2-Port Gigabit Ethernet SPA
•2-Port and 4-Port OC-3c/STM-1 POS SPA
•1-Port OC-12c/STM-4 POS SPA
•1-Port OC-48c/STM-16 POS SPA
|
In Cisco IOS Release 12.2(18)SXF and later:
•1-Port 10-Gigabit Ethernet SPA
•5-Port Gigabit Ethernet SPA
•10-Port Gigabit Ethernet SPA
•1-Port OC-192c/STM-64 POS/RPR SPA
•2-Port and 4-Port OC-48c/STM-16 POS SPA
Support for the following SPAs was added in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-48c/STM-16 POS SPA
|
H-VPLS with Q-in-Q edge
|
Not supported.
|
Not supported.
|
In Cisco IOS Release 12.2(18)SXF and later:
•1-Port 10-Gigabit Ethernet SPA
•5-Port Gigabit Ethernet SPA
•10-Port Gigabit Ethernet SPA
•1-Port OC-192c/STM-64 POS/RPR SPA
•2-Port and 4-Port OC-48c/STM-16 POS SPA
Support for the following SPAs was added in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-48c/STM-16 POS SPA
|
VPLS with point-to-multipoint EoMPLS and fully-meshed PE configuration
|
Not supported.
|
In Cisco IOS Release 12.2(33)SRA:
•2-Port Gigabit Ethernet SPA
•2-Port and 4-Port OC-3c/STM-1 POS SPA
•1-Port OC-12c/STM-4 POS SPA
•1-Port OC-48c/STM-16 POS SPA
|
In Cisco IOS Release 12.2(18)SXF and later:
•1-Port 10-Gigabit Ethernet SPA
•5-Port Gigabit Ethernet SPA
•10-Port Gigabit Ethernet SPA
•1-Port OC-192c/STM-64 POS/RPR SPA
•2-Port and 4-Port OC-48c/STM-16 POS SPA
Support for the following SPAs was added in Cisco IOS Release 12.2(33)SRA:
•2-Port and 4-Port OC-48c/STM-16 POS SPA
|
Configuring MPLS Features on a SIP
Many of the MPLS features supported on the FlexWAN and Enhanced FlexWAN modules on the Cisco 7600 series router are also supported by the SIPs. For a list of the supported MPLS features on the SIPs, see "Overview of the SIPs and SSC."
This section describes those MPLS features that have SIP-specific configuration guidelines. After you review the SIP-specific guidelines described in this document, then refer to the following URL for more information about configuring MPLS features:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/cfgnotes/flexport/combo/flexmpls.htm
This section includes the following topics:
• Configuring Any Transport over MPLS on a SIP
• Configuring Hierarchical Virtual Private LAN Service (H-VPLS) with MPLS to the Edge
• Configuring MPLS Traffic Engineering Class-Based Tunnel Selection (CBTS) on the Cisco 7600 SIP-600
Configuring Any Transport over MPLS on a SIP
Any Transport over MPLS (AToM) transports Layer 2 packets over a Multiprotocol Label Switching (MPLS) backbone. AToM uses a directed Label Distribution Protocol (LDP) session between edge routers for setting up and maintaining connections. Forwarding occurs through the use of two levels of labels, switching between the edge routers. The external label (tunnel label) routes the packet over the MPLS backbone to the egress Provider Edge (PE) at the ingress PE. The VC label is a demuxing label that determines the connection at the tunnel endpoint (the particular egress interface on the egress PE as well as the virtual path identifier [VPI]/virtual channel identifier [VCI] value for an ATM Adaptation Layer 5 [AAL5] protocol data unit [PDU], the data-link connection identifier [DLCI] value for a Frame Relay PDU, or the virtual LAN [VLAN] identifier for an Ethernet frame).
For specific information about configuring AToM features, refer to the FlexWAN and Enhanced FlexWAN Module Installation and Configuration Note located at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/cfgnotes/flexport/combo/flexmpls.htm
Note When referring to the FlexWAN documentation, be sure to note any SIP-specific configuration guidelines described in this document.
Cisco 7600 SIP-200 AToM Features
The Cisco 7600 SIP-200 supports the following AToM features:
•ATM over MPLS (ATMoMPLS)—AAL5 VC mode
•Ethernet over MPLS (EoMPLS)—(Single cell relay) VC mode
•Frame Relay over MPLS (FRoMPLS)
•FRoMPLS with dMLFR—Supported between the CE and PE devices.
•High-Level Data Link Control (HDLC) over MPLS (HDLCoMPLS)
•PPP over MPLS (PPPoMPLS)—Not supported with dMLPPP or dLFI
•Hierarchical QoS for EoMPLS VCs
Cisco 7600 SIP-200 AToM Configuration Guidelines
When configuring AToM with a Cisco 7600 SIP-200, consider the following guidelines:
•You cannot use a SIP-200 and an Ethernet SPA on the customer-facing side because the Ethernet SPA is a Layer 3 only interface.
•Because the SIP-200 supports WAN interfaces, you can use the SIP-200 for non-Ethernet access (FR,HDLC,ATM,PPP) at the customer-facing side.
•For VLAN-based xconnect (also called linecard-based EoMPLS), the customer-facing port must be a Layer 2 port and the backbone-facing card must be a Layer 3 port.
•The SIP-200 does not supportdot1q subinterface-based xconnect towards the edge.
Cisco 7600 SIP-400 AToM Features
The Cisco 7600 SIP-400 supports the following AToM features:
•ATMoMPLS—AAL0 mode (single cell relay only)
•ATMoMPLS—AAL5 mode
•EoMPLS—Port mode
•EoMPLS—VLAN mode
•FRoMPLS—DLCI mode
•Beginning in Cisco IOS Release 12.2(33)SRA:
–Hierarchical QoS for EoMPLS VCs
–HDLCoMPLS
–PPPoMPLS
–ATM local switching
Cisco 7600 SIP-400 AToM Configuration Guidelines
When configuring AToM with a Cisco 7600 SIP-400, consider the following guidelines:
•The Cisco 7600 SIP-400 is not supported with a Supervisor Engine 1, Supervisor Engine 1A, Supervisor Engine 2, or Supervisor Engine 720 PFC3A.
•The Cisco 7600 SIP-400 is not supported with PFC-2-based systems.
•For AToM in Cisco IOS 12.2SX releases, the Cisco 7600 SIP-400 does not support the following features when they are located in the data path. This means you should not configure the following features if the SIP is facing the customer edge (CE) or the MPLS core:
–HDLCoMPLS
–PPPoMPLS
–VPLS
•For AToM beginning in Cisco IOS Release 12.2(33)SRA, the Cisco 7600 SIP-400 supports the following features on CE-facing interfaces:
–HDLCoMPLS
–PPPoMPLS
–VPLS
•The Cisco 7600 SIP-400 supports EoMPLS with directly connected provider edge (PE) devices when the Cisco 7600 SIP-400 is on the MPLS core side of the network.
•The Cisco 7600 SIP-400 does not support the ability to enable or disable tunneling of Layer 2 packets, such as for the VLAN Trunking Protocol (VTP), Cisco Discovery Protocol (CDP), and bridge protocol data unit (BPDU). The Cisco 7600 SIP-400 tunnels BPDUs, and always blocks VTP and CDP packets from the tunnel.
•In ATMoMPLS AAL5 and cell mode, the Cisco 7600 SIP-400 supports non-matching VPIs/VCIs between PEs if the Cisco 7600 SIP-400 is on both sides of the network.
•The Cisco 7600 SIP-400 supports matching on FR-DE to set MPLS-EXP for FRoMPLS.
•The Cisco 7600 SIP-400 supports use of the xconnect command to configure AToM circuits for all AToM connection types except ATMoMPLS. For ATMoMPLS, you must use the mpls l2 transport route command.
For information about configuring the xconnect command for AToM circuits, refer to the MPLS examples using the xconnect command at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/cfgnotes/optical/122sx/mpls.htm
•The Cisco 7600 SIP-400 does not support the following QoS classification features with AToM:
–Matching on data-link connection identifier (DLCI) is unsupported.
–Matching on virtual LAN (VLAN) is unsupported.
–Matching on class of service (CoS) is unsupported in Cisco IOS Release 12.2(18)SXE and Cisco IOS Release 12.2(18)SXE2 only. Beginning in Cisco IOS Release 12.2(18)SXF, it is supported with the 2-Port Gigabit Ethernet SPA.
–Matching on input interface is unsupported.
–Matching on packet length is unsupported.
–Matching on media access control (MAC) address is unsupported.
–Matching on protocol type, including Border Gateway Protocol (BGP), is unsupported.
Understanding MPLS Imposition on the Cisco 7600 SIP-400 to Set MPLS Experimental Bits
The MPLS imposition function encapsulates non-MPLS frames (such as Ethernet, VLAN, Frame Relay, ATM, or IP) into MPLS frames. MPLS disposition performs the reverse function.
An input QoS policy map is applied to ingress packets before MPLS imposition takes place. This means that the packets are treated as non-MPLS frames, so any MPLS-related matches have no effect. In the case of marking experimental (EXP) bits using the set mpls experimental command, the information is passed to the AToM or MPLS component to set the EXP bits. After imposition takes place, the frame becomes an MPLS frame and an output QoS policy map (if it exists) can apply MPLS-related criteria.
On the egress side, an output QoS policy map is applied to the egress packets after MPLS disposition takes place. This means that packets are treated as non-MPLS frames, so any MPLS-related criteria has no effect. Before disposition, the frame is an MPLS frame and the input QoS policy map (if it exists) can apply MPLS-related criteria.
The Encoded Address Recognition Logic (EARL) is a centralized processing engine for learning and forwarding packets based upon MAC address on the Cisco 7600 series router supervisor engines. The EARL stores the VLAN, MAC address, and port relationships. These relationships are used to make switching decisions in hardware. The EARL engine also performs MPLS imposition, and the MPLS EXP bits are copied either from the IP TOS field (using trust dscp or trust precedence mode), or from the DBUS header QoS field (using trust cos mode).
When using the 2-Port Gigabit Ethernet SPA with the Cisco 7600 SIP-400 as the customer-side interface configured for 802.1Q encapsulation for IP imposition with MPLS, the Layer 2 CoS value is not automatically copied into the corresponding MPLS packet's EXP bits. Instead, the value in the IP precedence bits is copied.
To maintain the 802.1Q CoS values, classify the imposition traffic on the customer-facing Gigabit Ethernet interface in the input direction to match on CoS value, and then set the MPLS experimental action for that class as shown in the following example:
Router(config)# class-map cos0
Router(config-cmap)# match cos 0
Router(config-cmap)# exit
Router(config)# class-map cos1
Router(config-cmap)# match cos 1
Router(config-cmap)# exit
Router(config)# policy-map policy1
Router(config-pmap)# class cos0
Router(config-pmap-c)# set mpls experimental imposition 0
Router(config-pmap-c)# exit
Router(config-pmap)# class cos1
Router(config-pmap-c)# set mpls experimental imposition 1
Cisco 7600 SIP-600 AToM Features
The Cisco 7600 SIP-600 supports the following AToM features:
•Any Transport over MPLS (AToM) support—EoMPLS only (Encoded Address Recognition Logic [EARL]-based and SIP-based EoMPLS)
Configuring Hierarchical Virtual Private LAN Service (H-VPLS) with MPLS to the Edge
The Cisco 7600 SIP-400 and Cisco 7600 SIP-600 support the H-VPLS with MPLS to the Edge feature. For more information about VPLS support on the SIPs, see the "Configuring Virtual Private LAN Service" section.
Configuring MPLS Traffic Engineering Class-Based Tunnel Selection (CBTS) on the Cisco 7600 SIP-600
Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Class-Based Tunnel Selection (CBTS) enables you to dynamically route and forward traffic with different class of service (CoS) values onto different TE tunnels between the same tunnel headend and the same tailend. The TE tunnels can be regular TE or DiffServ-aware TE (DS-TE) tunnels.
The set of TE (or DS-TE) tunnels from the same headend to the same tailend that you configure to carry different CoS values is referred to as a "tunnel bundle." Tunnels are "bundled" by creating a master tunnel and then attaching member tunnels to the master tunnel. After configuration, CBTS dynamically routes and forwards each packet into the tunnel that meets the following requirements:
•Is configured to carry the CoS of the packet
•Has the right tailend for the destination of the packet
Because CBTS offers dynamic routing over DS-TE tunnels and requires minimum configuration, it greatly eases deployment of DS-TE in large-scale networks.
CBTS can distribute all CoS values on eight different tunnels.
CBTS also allows the TE tunnels of a tunnel bundle to exit headend routers through different interfaces.
CTBS configuration involves performing the following tasks:
•Creating multiple (DS-) TE tunnels withe same headend and tailend and indicating on each of these tunnels which COSs are to be transported on the tunnel.
•Creating a master tunnel, attaching the member tunnels to it, and making the master tunnel visible for routing.
MPLS Traffic Engineering Class-Based Tunnel Selection (CBTS) Configuration Guidelines
When configuring MPLS Traffic Engineering Class-Based Tunnel Selection (CBTS), consider the following guidelines:
•CBTS has the following prerequisites:
–MPLS enabled on all tunnel interfaces
–Cisco Express Forwarding (CEF) or distributed CEF (dCEF) enabled in general configuration mode
•CBTS has the following restrictions:
–For a given destination, all CoS values are carried in tunnels terminating at the same tailend. Either all CoS values are carried in tunnels or no values are carried in tunnels. In other words, for a given destination, you cannot map some CoS values in a DS-TE tunnel and other CoS values in a Shortest Path First (SPF) Label Distribution Protocol (LDP) or SPF IP path.
–No LSP is established for the master tunnel and regular traffic engineering attributes (bandwidth, path option, fast reroute) are irrelevant on a master tunnel. TE attributes (bandwidth, bandwidth pool, preemption, priorities, path options, and so on) are configured completely independently for each tunnel.
–CBTS does not allow load-balancing of a given EXP value in multiple tunnels. If two or more tunnels are configured to carry a given experimental (EXP) value, CBTS picks one of these tunnels to carry this EXP value.
–CBTS supports aggregate control of bumping (that is, it is possible to define default tunnels to be used if other tunnels go down. However, CBTS does not allow control of bumping if the default tunnel goes down. CBTS does not support finer-grain control of bumping. For example, if the voice tunnel goes down, redirect voice to T2, but if video goes down, redirect to T3.
–The operation of CBTS is not supported with Any Transport over MPLS (AToM), MPLS TE Automesh, or label-controlled (LC)-ATM.
Creating Multiple MPLS Member TE or DS-TE Tunnels from the Same Headend to the Same Tailend
Perform the following task to create multiple MPLS member TE or DS-TE tunnels with the same headend and same tailend and to configure EXP values to be carried by each of these tunnels. The procedure begins in global configuration mode.
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface tunnel number
|
Configures a tunnel interface type and enters interface configuration mode.
•number—Number of the tunnel interface that you want to create or configure.
|
Step 2
|
Router(config-if)# ip unnumbered type number
|
Enables IP processing on an interface without assigning an explicit IP address to the interface.
•type—Type of another interface on which the router has an assigned IP address.
•number—Number of another interface on which the router has an assigned IP address. It cannot be another unnumbered interface.
|
Step 3
|
Router(config-if)# tunnel destination {hostname | ip-address}
|
Specifies the destination of the tunnel for this path option.
•hostname—Name of the host destination.
•ip-address—IP address of the host destination expressed in four-part, dotted decimal notation.
|
Step 4
|
Router(config-if)# tunnel mode mpls traffic-eng
|
Sets the mode of a tunnel to MPLS for TE.
|
Step 5
|
Router(config-if)# tunnel mpls traffic-eng bandwidth [sub-pool | global] bandwidth
|
Configures the bandwidth for the MPLS TE tunnel. If automatic bandwidth is configured for the tunnel, use the tunnel mpls traffic-eng bandwidth command to configure the initial tunnel bandwidth, which is adjusted by the auto-bandwidth mechanism.
•sub-pool—(Optional) Indicates a subpool tunnel.
•global—(Optional) Indicates a global pool tunnel. Entering this keyword is not necessary, for all tunnels are global pool in the absence of the sub-pool keyword. But if users of pre-DiffServ-aware Traffic Engineering (DS-TE) images enter this keyword, it is accepted.
•bandwidth—Bandwidth, in kilobits per second, set aside for the MPLS traffic engineering tunnel. Range is between 1 and 4294967295.
Note You can configure any existing mpls traffic-eng command on these TE or DS-TE tunnels.
|
Step 6
|
Router(config-if)# tunnel mpls traffic-eng exp [list-of-exp-values] [default]
|
Specifies an EXP value or values for an MPLS TE tunnel.
•list-of-exp-values—EXP value or values that are are to be carried by the specified tunnel. Values range from 0 to 7.
•default—The specified tunnel is to carry all EXP values that are:
–Not explicitly allocated to another tunnel
–Allocated to a tunnel that is currently down
|
Step 7
|
Router(config-if)# exit
|
Exits to global configuration mode.
|
Step 8
|
|
Repeat steps 1 through 7 on the same headend router to create additional tunnels from this headend to the same tailend.
|
Creating a Master Tunnel, Attaching Member Tunnels, and Making the Master Tunnel Visible
Perform the followings task to create a master tunnel, attach member tunnels to it, and make the master tunnel visible for routing. The procedure begins in global configuration mode.
| |
Command
|
Purpose
|
Step 1
|
Router(config)# interface tunnel number
|
Configures a tunnel interface type and enters interface configuration mode.
•number—Number of the tunnel interface that you want to create or configure.
|
Step 2
|
Router(config-if)# ip unnumbered type number
|
Enables IP processing on an interface without assigning an explicit IP address to the interface.
•type—Type of another interface on which the router has an assigned IP address.
•number—Number of another interface on which the router has an assigned IP address. It cannot be another unnumbered interface.
|
Step 3
|
Router(config-if)# tunnel destination {hostname | ip-address}
|
Specifies the destination of the tunnel for this path option.
•hostname—Name of the host destination.
•ip-address—IP address of the host destination expressed in four-part, dotted decimal notation.
|
Step 4
|
Router(config-if)# tunnel mode mpls traffic-eng exp-bundle master
|
Specifies this is the master tunnel for the CBTS configuration.
|
Step 5
|
Router(config-if)# tunnel mode mpls traffic-eng exp-bundle member tunnel-id
|
Attaches a member tunnel to the master tunnel.
•tunnel-id—Number of the tunnel interface to be attached to the master tunnel.
Repeat this command for each member tunnel.
|
Step 6
|
Router(config-if)# tunnel mpls traffic-eng autoroute announce
|
Specifies that the Interior Gateway Protocol (IGP) should use the tunnel (if the tunnel is up) in its enhanced SPF calculation.
|
Step 7
|
Router(config-if)# tunnel mpls traffic-eng autoroute metric {absolute | relative} value
|
(Optional) Specifies the MPLS TE tunnel metric that the IGP enhanced SPF calculation uses.
•absolute—Indicates the absolute metric mode; you can enter a positive metric value.
•relative—Indicates the relative metric mode; you can enter a positive, negative, or zero value.
•value—Metric that the IGP enhanced SPF calculation uses. The relative value can be from -10 to 10.
Note Even though the value for a relative metric can be from -10 to +10, configuring a tunnel metric with a negative value is considered a misconfiguration. If the metric to the tunnel tailend appears to be 4 from the routing table, then the cost to the tunnel tailend router is actually 3 because 1 is added to the cost for getting to the loopback address. In this instance, the lowest value that you can configure for the relative metric is -3.
|
Note Alternatively, static routing could be used instead of autoroute to make the TE or DS-TE tunnels visible for routing.
Verifying That the MPLS TE or DS-TE Tunnels Are Operating and Announced to the IGP
The following show commands can be used to verify that the MPLS TE or DS-TE tunnels are operating and announced to the IGP. The commands are all entered in privileged EXEC configuration mode.
Command
|
Purpose
|
Router# show mpls traffic-eng topology {A.B.C.D | igp-id {isis nsap-address | ospf A.B.C.D} [brief]
|
Shows the MPLS traffic engineering global topology as currently known at this node.
•A.B.C.D—Specifies the node by the IP address (router identifier to interface address).
•igp-id—Specifies the node by IGP router identifier.
•isis nsap-address—Specifies the node by router identification (nsap-address) if you are using IS-IS.
•ospf A.B.C.D—Specifies the node by router identifier if you are using OSPF.
•brief—Provides a less detailed version of the topology.
|
Router# show mpls traffic-eng exp
|
Displays EXP mapping.
|
Router# show ip cef [type number] [detail]
|
Displays entries in the forwarding information base (FIB) or displays a summary of the FIB.
•type number —Identifies the interface type and number for which to display FIB entries.
•detail—Displays detailed FIB entry information.
|
Router# show mpls forwarding-table [network {mask | length} [detail]
|
Displays the contents of the MPLS label forwarding information base (LFIB).
•network—Identifies the destination network number.
•mask—Identifies the network mask to be used with the specified network.
•length—Identifies the number of bits in the destination mask.
•detail—Displays information in long form (includes length of encapsulation, length of MAC string, maximum transmission unit [MTU], and all labels).
|
Router# show mpls traffic-eng autoroute
|
Displays tunnels that are announced to the Interior Gateway Protocol (IGP).
|
The show mpls traffic-eng topology command output displays the MPLS TE global topology:
Router# show mpls traffic-eng topology 10.0.0.1
IGP Id: 10.0.0.1, MPLS TE Id:10.0.0.1 Router Node (ospf 10 area 0) id 1
link[0]: Broadcast, DR: 180.0.1.2, nbr_node_id:6, gen:18
frag_id 0, Intf Address:180.0.1.1
TE metric:1, IGP metric:1, attribute_flags:0x0
physical_bw: 100000 (kbps), max_reservable_bw_global: 1000 (kbps)
max_reservable_bw_sub: 0 (kbps)
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
link[1]: Broadcast, DR: 180.0.2.2, nbr_node_id:7, gen:19
frag_id 1, Intf Address:180.0.2.1
TE metric:1, IGP metric:1, attribute_flags:0x0
physical_bw: 100000 (kbps), max_reservable_bw_global: 1000 (kbps)
max_reservable_bw_sub: 0 (kbps)
Total Allocated Reservable Reservable
BW (kbps) BW (kbps) BW (kbps)
--------------- ----------- ----------
The show mpls traffic-eng exp command output displays EXP mapping information about a tunnel:
Router# show mpls traffic-eng exp
Master: Tunnel10 Status: IP
Members: Status Conf EXP Actual EXP
Tunnel2 UP/ACTIVE default 0 1 2 3 4 6 7
(T)=Tailend is different to master
(NE)=There is no exp value configured on this tunnel.
The show ip cef detail command output displays detailed FIB entry information for a tunnel:
Router# show ip cef tunnel1 detail
IP CEF with switching (Table Version 46), flags=0x0
31 routes, 0 reresolve, 0 unresolved (0 old, 0 new), peak 2
2 instant recursive resolutions, 0 used background process
8 load sharing elements, 8 references
6 in-place/0 aborted modifications
34696 bytes allocated to the FIB table data structures
universal per-destination load sharing algorithm, id 9EDD49E1
Resolution Timer: Exponential (currently 1s, peak 1s)
short mask protection disabled
31 leaves, 23 nodes using 26428 bytes
Table epoch: 0 (31 entries at this epoch)
Adjacency Table has 13 adjacencies
10.0.0.9/32, version 45, epoch 0, per-destination sharing
tag information set, all rewrites inherited
via 0.0.0.0, Tunnel1, 0 dependencies
next hop 0.0.0.0, Tunnel1
tag rewrite with Tu1, point2point, tags imposed {12304}
0 packets, 0 bytes switched through the prefix
tmstats: external 0 packets, 0 bytes
internal 0 packets, 0 bytes
The show mpls forwarding-table detail command output displays detailed information from the MPLS LFIB:
Router# show mpls forwarding 10.0.0.9 detail
Local Outgoing Prefix Bytes tag Outgoing Next Hop
tag tag or VC or Tunnel Id switched interface
Tun hd Untagged 10.0.0.9/32 0 Tu1 point2point
MAC/Encaps=14/18, MRU=1500, Tag Stack{12304}, via Fa6/0
00027D884000000ED70178A88847 03010000
No output feature configured
Untagged 10.0.0.9/32 0 Tu2 point2point
MAC/Encaps=14/18, MRU=1500, Tag Stack{12305}, via Fa6/1
00027D884001000ED70178A98847 03011000
No output feature configured
Untagged 10.0.0.9/32 0 Tu3 point2point
MAC/Encaps=14/18, MRU=1500, Tag Stack{12306}, via Fa6/1
00027D884001000ED70178A98847 03012000
No output feature configured
Untagged 10.0.0.9/32 0 Tu4 point2point
MAC/Encaps=14/18, MRU=1500, Tag Stack{12307}, via Fa6/1
00027D884001000ED70178A98847 03013000
No output feature configured
The show mpls traffic-eng autoroute command output displays tunnels that are announced to the Interior Gateway Protocol (IGP).
Router# show mpls traffic-eng autoroute
MPLS TE autorouting enabled
destination 10.0.0.9, area ospf 10 area 0, has 4 tunnels
Tunnel1 (load balancing metric 20000000, nexthop 10.0.0.9)
Tunnel2 (load balancing metric 20000000, nexthop 10.0.0.9)
Tunnel3 (load balancing metric 20000000, nexthop 10.0.0.9)
Tunnel4 (load balancing metric 20000000, nexthop 10.0.0.9)
Configuring QoS Features on a SIP
This section describes configuration of the SIP-specific QoS features using the Modular QoS command-line interface (CLI). Before referring to any other QoS documentation for the platform or in the Cisco IOS software, use this section to determine SIP-specific QoS feature support and configuration guidelines.
For additional details about QoS concepts and features in Cisco IOS 12.2 releases, you can then refer to the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2, at
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_book09186a00800c5e31.html
This section includes the following topics:
• General QoS Feature Configuration Guidelines
• Configuring QoS Features Using MQC
• Configuring QoS Traffic Classes on a SIP
• Configuring QoS Class-Based Marking Policies on a SIP
• Configuring QoS Congestion Management and Avoidance Policies on a SIP
• Configuring Dual Priority Queuing on a Cisco 7600 SIP-400
• Configuring Percent Priority and Percent Bandwidth Support on a Cisco 7600 SIP-400
• Configuring QoS Traffic Shaping Policies on a SIP
• Configuring QoS Traffic Policing Policies on a SIP
• Attaching a QoS Traffic Policy to an Interface
• Configuring Network-Based Application Recognition and Distributed Network-Based Application Recognition
• Configuring Hierarchical QoS on a SIP
• Configuring PFC QoS on a Cisco 7600 SIP-600
General QoS Feature Configuration Guidelines
This section identifies some general QoS feature guidelines for certain types of SPAs. You can find other feature-specific SIP and SPA configuration guidelines and restrictions in the other QoS sections of this chapter.
ATM SPA QoS Configuration Guidelines
For the 2-Port and 4-Port OC-3c/STM-1 ATM SPA, the following applies:
•In the ingress direction, all Quality of Service (QoS) features are supported by the Cisco 7600 SIP-200.
•In the egress direction:
–All queueing-based features (such as class-based weighted fair queueing [CBWFQ], and ATM per-VC WFQ, WRED, and shaping) are implemented on the segmentation and reassembly (SAR) processor on the SPA.
–Policing is implemented on the SIP.
–Class queue shaping is not supported.
Ethernet SPA QoS Configuration Guidelines
For the Ethernet SPAs, the following QoS behavior applies:
•In both the ingress and egress directions, all QoS features calculate packet size similarly to how packet size calculation is performed by the FlexWAN and Enhanced FlexWAN modules on the Cisco 7600 series router.
•Specifically, all features consider the IEEE 802.3 Layer 2 headers and the Layer 3 protocol payload. The CRC, interframe gap, and preamble are not included in the packet size calculations.
Note For Fast Ethernet SPAs, QoS cannot change the speed of an interface (for example, Fast Ethernet SPAs cannot change QoS settings whenever an interface speed is changed between 100 and 10 Mbps). When the speed is changed, the user must also adjust the QoS setting accordingly.
Configuring QoS Features Using MQC
The Modular QoS CLI (MQC) is a CLI structure that allows users to create traffic policies and attach these policies to interfaces. A traffic policy contains a traffic class and one or more QoS features. A traffic class is used to select traffic, while the QoS features in the traffic policy determine how to treat the classified traffic.
If you apply a traffic policy at a main interface that also contains subinterfaces, then all of the traffic that goes through the subinterfaces is processed according to the policy at the main interface. For example, if you configure a traffic shaping policy at the main interface, all of the traffic going through the subinterfaces is aggregated and shaped to the rate defined in the traffic shaping policy at the main interface.
To configure QoS features using the Modular QoS CLI on the SIPs, complete the following basic steps:
Step 1 Define a traffic class using the class-map command.
Step 2 Create a traffic policy by associating the traffic class with one or more QoS features (using the policy-map command).
Step 3 Attach the traffic policy to the interface using the service-policy command.
For a complete discussion about MQC, refer to the "Modular Quality of Service Command-Line Interface Overview" chapter of the Cisco IOS Quality of Service Solutions Configuration Guide,
Release 12.2 publication at:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800bd908.html
Configuring QoS Traffic Classes on a SIP
Use the QoS classification features to select your network traffic and categorize it into classes for further QoS processing based on matching certain criteria. The default class, named "class-default," is the class to which traffic is directed for any traffic that does not match any of the selection criteria in the configured class maps.
QoS Traffic Class Configuration Guidelines
When configuring traffic classes on a SIP, consider the following guidelines:
•You can define up to 256 unique class maps.
•A single class map can contain up to 8 different match command statements.
•For ATM bridging, Frame Relay bridging, MPB, and BCP features, the following matching features are supported on bridged frames beginning in Cisco IOS Release 12.2(33)SRA:
–Matching on ATM CLP bit (input interface only)
–Matching on CoS
–Matching on Frame Relay DE bit (input interface only)
–Matching on Frame Relay DLCI
–Matching on inner CoS
–Matching on inner VLAN
–Matching on IP DSCP
–Matching on IP precedence
–Matching on VLAN
•The Cisco 7600 SIP-600 does not support combining matches on QoS group or input VLAN with other types of matching criteria (for example, access control lists [ACLs]) in the same class or policy map.
•The Cisco 7600 SIP-400 supports matching on ACLs for routed traffic only. Matching on ACLs is not supported for bridged traffic.
•The SIP-400 does not support dynamic, time-based, or tos-matching ACLs. The SIP-400 also does not support the log option in ACL.
•When configuring hierarchical QoS on the Cisco 7600 SIP-600, if you configure matching on an input VLAN in a parent policy, then only matching on a QoS group is supported in the child policy.
•For support of specific matching criteria by SIP, see Table 4-10.
To create a user-defined QoS traffic class, use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# class-map [match-all | match-any] class-name
|
Creates a traffic class, where:
•match-all—(Optional) Specifies that all match criteria in the class map must be matched, using a logical AND of all matching statements defined under the class. This is the default.
•match-any—(Optional) Specifies that one or more match criteria must match, using a logical OR of all matching statements defined under the class.
•class-name—Specifies the user-defined name of the class.
Note You can define up to 256 unique class maps.
|
Step 2
|
Router(config-cmap)# match type
|
Specifies the matching criterion to be applied to the traffic, where type represents one of the forms of the match command supported by the SIP as shown in Table 4-10.
Note A single class-map can contain up to 8 different match command statements.
|
Table 4-10 provides information about which QoS classification features are supported for SIPs on the Cisco 7600 series router. For more information about most of the commands documented in this table, refer to the Cisco IOS Quality of Service Solutions Command Reference.
Table 4-10 QoS Classification Feature Compatibility by SIP
Feature (match command)
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Matching on access control list (ACL) number
(match access-group command)
|
Supported for all SPAs with the following types of ACLs:
•Protocols—ICMP, IGMP, EIGRP, OSPF, PIM, and GRE
•Source and destination port
•TCP flags
•ToS (DSCP and precedence)
|
Supported for all SPAs with the following types of ACLs:
•Source and destination port
•TCP flag (IPv4 only)
•IP address (IPv6 compress mode only)
|
Supported for all SPAs with the following types of ACLs:
•IPv4 and IPv6
•Protocols—ICMP, IGMP, UDP, and MAC
•Source and destination ports
•TCP flags
•ToS
|
Matching on ACL name (match access-group name command)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Match on any packet
(match any command)
Note Not supported for user-defined class maps.
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Matching on ATM cell loss priority (CLP) (match atm clp command)
|
•Supported for all ATM SPAs.
•Cisco IOS Release 12.2(33)SRA—Support added for ATM CLP matching with RFC 1483 bridging features.
|
•Supported for all ATM SPAs on ATM input interface only.
•Cisco IOS Release 12.2(33)SRA—Support added for ATM CLP matching with RFC 1483 bridging features on ATM input interface only.
|
Not supported.
|
Matching on class map
(match class-map command)
|
Supported for all SPAs.
|
Not supported.
|
Not supported.
|
Matching on Class of Service (CoS) (match cos command)
|
Supported in Cisco IOS Release 12.2(33)SRA on the 4-Port and 8-Port Fast Ethernet SPA using dot1q encapsulation.
|
•2-Port Gigabit Ethernet SPA only—Input and output 802.1Q tagged frames.
•Cisco IOS Release 12.2(33)SRA—Support added for inner CoS matching with bridging features.
|
Supported in Cisco IOS Release 12.2(33)SRA for switchport queueing.
Note CoS classification is available through PFC QoS using MAC address ACLs.
|
Matching on inner CoS (match cos inner command)
|
•Supported for all SPAs.
•Cisco IOS Release 12.2(33)SRA—Supported added for inner CoS matching with bridging features.
|
Supported in Cisco IOS Release 12.2(33)SRA on the 2-Port Gigabit Ethernet SPA:
•Input and output interfaces
•Inner CoS matching with bridging features
|
Not supported.
|
Match on Frame Relay discard eligibility (DE) bit (match fr-de command)
|
•Supported for Frame Relay input and output interfaces.
•Cisco IOS Release 12.2(33)SRA—Support added for Frame Relay DE matching with Frame Relay bridging features.
|
•Supported for a Frame Relay input interface only.
•Cisco IOS Release 12.2(33)SRA—Support added for Frame Relay DE matching with Frame Relay bridging features on input Frame Relay interface only.
Note Because the Cisco 7600 SIP-400 acts as a Frame Relay data terminal equipment (DTE) device only, and not a data communications equipment (DCE) device, the Cisco 7600 SIP-400 does not support dropping of frames that match on FR DE bits; however, other QoS actions are supported.
|
Not supported.
|
Match on Frame Relay data-link connection identifier (DLCI) (match fr-dlci command)
|
•Supported for Frame Relay input and output interfaces.
•Cisco IOS Release 12.2(33)SRA—Support added for Frame Relay DLCI matching with Frame Relay bridging features.
|
Supported in Cisco IOS Release 12.2(33)SRA on Frame Relay input and output interfaces, and with Frame Relay bridging features.
|
Not supported.
|
Match on input VLAN
(match input vlan command—Matches the VLAN from an input interface)
|
Supported for EoMPLS interfaces.
|
Supported in Cisco IOS Release 12.2(33)SRA—Output interface only, and with bridging features.
Note Service policy is applied on the output interface of the Cisco 7600 SIP-400 to match the VLAN from the input interface.
|
Supported in Cisco IOS Release 12.2(33)SRA—Output interface only for software-based EoMPLS.
Note The service policy is applied on the output interface of the Cisco 7600 SIP-600 to match the VLAN from the input interface. If you configure matching on an input VLAN in a parent policy with hierarchical QoS, then only matching on QoS group is supported in the child policy.
|
Match on IP DSCP (match ip dscp command)
|
•Supported for all SPAs.
•Cisco IOS Release 12.2(33)SRA—Support added for IP DSCP matching with bridging features on an input interface only.
|
•Supported for all SPAs.
•Cisco IOS Release 12.2(33)SRA—Support added for IP DSCP matching with bridging features.
|
Supported for all SPAs.
|
Match on IP precedence (match ip precedence command)
|
Supported for all SPAs.
|
•Supported for all SPAs.
•Cisco IOS Release 12.2(33)SRA—Support added for IP precedence matching with bridging features.
|
Supported for all SPAs.
|
Match on IP Real-Time Protocol (RTP)
(match ip rtp command)
|
Supported for all SPAs.
|
Not supported.
|
Not supported.
|
Match on MAC address for an ACL name
(match mac address command)
|
Not supported.
|
Not supported.
|
Not supported.
|
Match on destination MAC address
(match destination-address mac command)
|
Not supported.
|
Not supported.
|
Not supported.
|
Match on source MAC address
(match source-address mac command)
|
Not supported.
|
Not supported.
|
Not supported.
|
Match on MPLS experimental (EXP) bit (match mpls experimental command)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Match on Layer 3 packet length in IP header (match packet length command)
|
Supported for all SPAs.
|
Not supported.
|
Not supported.
|
Match on QoS group (match qos-group command)
|
Not supported.
|
Supported in Cisco IOS Release 12.2(33)SRA—Output interface only.
|
Supported in software-based EoMPLS configurations only using hierarchical QoS, where the parent policy configures matching on input VLAN and the child policy configures matching on QoS group.
|
Match on protocol
(match protocol command
|
Supported for NBAR.
|
Not supported.
|
Supports matching on IP and IPv6.
|
Match on VLAN
(match vlan command—Matches the outer VLAN of a Layer 2 802.1Q frame)
|
Not supported.
|
Supported in Cisco IOS Release 12.2(33)SRA:
•Input and output interfaces
•Outer VLAN ID matching for 802.1Q tagged frames
|
Supported in Cisco IOS Release 12.2(33)SRA:
•Output interface only
•Outer VLAN ID matching for 802.1Q tagged frames
|
Match on VLAN Inner
(match vlan inner command—Matches the innermost VLAN of the 802.1Q tag in the Layer 2 frame)
|
•Supported for all SPAs.
•Cisco IOS Release 12.2(33)SRA—Support added for inner VLAN ID matching with bridging features.
|
Supported in Cisco IOS Release 12.2(33)SRA:
•Input and output interface
•Inner VLAN ID matching with bridging features
|
Not supported.
|
No match on specified criteria
(match not command)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Not supported.
|
Configuring QoS Class-Based Marking Policies on a SIP
After you have created your traffic classes, you can configure traffic policies to configure marking features to apply certain actions to the selected traffic in those classes.
In most cases, the purpose of a packet mark is identification. After a packet is marked, downstream devices identify traffic based on the marking and categorize the traffic according to network needs. This categorization occurs when the match commands in the traffic class are configured to identify the packets by the mark (for example, match ip precedence, match ip dscp, match cos, and so on). The traffic policy using this traffic class can then set the appropriate QoS features for the marked traffic.
In some cases, the markings can be used for purposes besides identification. Distributed WRED, for instance, can use the IP precedence, IP DSCP, or MPLS EXP values to detect and drop packets. In ATM networks, the CLP bit of the packet is used to determine the precedence of packets in a congested environment. If congestion occurs in the ATM network, packets with the CLP bit set to 1 are dropped before packets with the CLP bit set to 0. Similarly, the DE bit of a Frame Relay frame is used to determine the priority of a frame in a congested Frame Relay network. In Frame Relay networks, frames with the DE bit set to 1 are dropped before frames with the DE bit set to 0.
QoS Class-Based Marking Policy Configuration Guidelines
When configuring class-based marking on a SIP, consider the following guidelines:
•Packet marking is supported on interfaces, subinterfaces, and ATM virtual circuits (VCs). In an ATM PVC, you can configure packet marking in the same traffic policy where you configure the queueing actions, on a per-VC basis. However, only PVC configuration of service policies is supported for classes using multipoint bridging (MPB) match criteria.
•For ATM bridging, Frame Relay bridging, MPB, and BCP features, the following marking features are supported on bridged frames beginning in Cisco IOS Release 12.2(33)SRA:
–Set ATM CLP bit (output interface only)
–Set Frame Relay DE bit (output interface only)
–Set inner CoS
•If a service policy configures both class-based marking and marking as part of a policing action, then the marking using policing takes precedence over any class-based marking.
•The Cisco 7600 SIP-600 supports marking on input interfaces only.
•For support of specific marking criteria by SIP, see Table 4-11.
To configure a QoS traffic policy with class-based marking, use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# policy-map policy-map-name
|
Creates or modifies a traffic policy and enters policy map configuration mode, where:
•policy-map-name—Specifies the name of the traffic policy to configure. Names can be a maximum of 40 alphanumeric characters.
|
Step 2
|
Router (config-pmap)# class {class-name | class-default}
|
Specifies the name of the traffic class to which this policy applies and enters policy-map class configuration mode, where:
•class-name—Specifies that the policy applies to a user-defined class name previously configured.
•class-default—Specifies that the policy applies to the default traffic class.
|
Step 3
|
Router(config-pmap-c)# set type
|
Specifies the marking action to be applied to the traffic, where type represents one of the forms of the set command supported by the SIP as shown in Table 4-11.
|
Table 4-11 provides information about which QoS class-based marking features are supported for SIPs on the Cisco 7600 series router.
Table 4-11 QoS Class-Based Marking Feature Compatibility by SIP
Marking Feature (set command)
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Set ATM CLP bit
(set atm-clp command—Marks the ATM cell loss bit with value of 1)
|
•Supported for ATM output interfaces only.
•Cisco IOS Release 12.2(33)SRA—Support added for ATM CLP marking on output interfaces only with RFC 1483 bridging features.
|
Supported for ATM SPA output interfaces only.
|
Not supported.
|
Set discard class
(set discard-class command—Marks the packet with a discard class value for per-hop behavior)
|
Not supported.
|
Not supported.
|
Not supported.
|
Set Frame Relay DE bit
(set fr-de command—Marks the Frame Relay discard eligibility bit with value of 1)
|
•Supported for Frame Relay output interfaces only.
•Cisco IOS Release 12.2(33)SRA—Support added for Frame Relay DE marking on output interfaces only with Frame Relay bridging features.
|
Supported for Frame Relay output interfaces only.
|
Not supported.
|
Set IP DSCP
(set ip dscp command—Marks the IP differentiated services code point [DSCP] in the type of service [ToS] byte with a value from 0 to 63)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs on an input interface.
|
Set IP precedence
(set ip precedence command—Marks the precedence value in the IP header with a value from
0 to 7.)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs on an input interface.
|
Set Layer 2 802.1Q CoS
(set cos command—Marks the CoS value from 0 to 7 in an 802.1Q tagged frame)
|
•Supported for all SPAs.
•In Cisco IOS Release 12.2(33)SRA—Not supported with set cos-inner command on the same interface.
|
Supported in Cisco IOS Release 12.2(33)SRA.
|
Not supported.
|
Set Layer 2 802.1Q CoS
(set cos-inner command—Marks the inner CoS field from 0 to 7 in a bridged frame)
|
Supported in Cisco IOS Release 12.2(33)SRA with bridging features on the 4-Port and 8-Port Fast Ethernet SPA.
|
Supported in Cisco IOS Release 12.2(33)SRA with bridging features.
|
Not supported.
|
Set MPLS experimental (EXP) bit on label imposition
(set mpls experimental imposition command)
|
Supported for all SPAs.
|
Supported for any SPA IP input interface.
Note The table keyword is not supported.
|
Supported for all SPAs on an input interface.
|
Set MPLS EXP topmost
(set mpls experimental topmost command)
|
Supported for all SPAs.
|
Supported for any SPA MPLS interface.
|
Not supported.
|
Set QoS group
(set qos-group command—Marks the packet with a QoS group association)
|
Not supported.
|
Not supported.
|
Supported only for software-based EoMPLS on an input SPA switchport interface.
|
For more detailed information about configuring class-based marking features, refer to the Class-Based Marking document located at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/cbpmark2.htm
Note When referring to other class-based marking documentation, be sure to note any SIP-specific configuration guidelines described in this document.
Configuring QoS Congestion Management and Avoidance Policies on a SIP
This section describes SIP- and SPA-specific information for configuring QoS traffic policies for congestion management and avoidance features. These features are generally referred to as queueing features.
QoS Congestion Management and Avoidance Policy Configuration Guidelines
When configuring queueing features on a SIP, consider the following guidelines:
•The Cisco 7600 series router supports different forms of queueing features. See Table 4-12 to determine which queueing features are supported by SIP type.
•The Cisco 7600 SIP-200 and Cisco 7600 SIP-400 do not support ingress queueing features.
•When configuring queueing on the Cisco 7600 SIP-400, consider the following guidelines:
–A queue on the Cisco 7600 SIP-400 is not assured any minimum bandwidth.
–You cannot configure bandwidth or shaping with queueing under the same class in a service policy on the Cisco 7600 SIP-400.
–If you want to define bandwidth parameters under different classes in the same service policy on the Cisco 7600 SIP-400, then you only can use the bandwidth remaining percent command. The Cisco 7600 SIP-400 does not support other forms of the bandwidth command with queueing in the same service policy.
•You can use policing with queueing to limit the traffic rate.
•On the Cisco 7600 SIP-400, WRED is supported on bridged VCs with classification on precedence and DSCP values. On other SIPs, WRED does not work on bridged VCs (for example, VCs that implement MPB).
•When configuring WRED on the Cisco 7600 SIP-400, consider the following guidelines:
–WRED is supported on bridged VCs with classification on precedence and DSCP values.
–WRED explicit congestion notification (ECN) is not supported for output traffic on ATM SPAs.
–ECN is supported for IP traffic on output POS interfaces only.
–You can use the low-order TOS bits in the IP header for explicit congestion notification (ECN) for WRED. If you configure random-detect ecn in a service policy and apply it to either a POS interface or a VC on a POS interface, then if at least one of the ECN bits is set and the packet is a candidate for dropping, the Cisco 7600 SIP-400 marks both ECN bits. If either one of the ECN bits is set, the Cisco 7600 SIP-400 will not drop the packet.
–WRED ECN is not support for MPLS packets.
•On the Cisco 7600 SIP-400, the default queue limit is calculated based on the number of 250-byte packets that the SIP can transmit in one half of a second. For example, for an OC-3 SPA with a rate of 155 Mbps, the default queue limit is 38,750 packets (155000000 x 0.5 / 250 x 8).
•For more detailed information about configuring congestion management features, refer to the Cisco IOS Quality of Service Solutions Configuration Guide document corresponding to your Cisco IOS software release.
Table 4-12 provides information about which QoS queueing features are supported for SIPs on the Cisco 7600 series router.
Table 4-12 QoS Congestion Management and Avoidance Feature Compatibility by SIP and SPA Combination
Congestion Management and Avoidance Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Aggregate Weighted Random Early Detection
(random-detect aggregate, random-detect dscp (aggregate), and random-detect precedence (aggregate) commands)
|
Supported for ATM SPA PVCs only—Cisco IOS Release 12.2(18)SXE and later and in Cisco IOS Release 12.2(33)SRA
|
Supported for ATM SPA PVCs only—Cisco IOS Release 12.2(18)SXE and later and in Cisco IOS Release 12.2(33)SRA.
|
Supported for all SPAs.
For more information on configuring aggregate WRED, see the "Configuring Aggregate WRED for PVCs" section on page 8-27.
|
Class-based Weighted Fair Queueing (CBWFQ)
(bandwidth, queue-limit commands)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Dual-Queue Support
(priority and priority level commands)
|
Not supported.
|
Supported for all SPAs—Cisco IOS Release 12.2(33)SRB and later.
|
Not supported.
|
Flow-based Queueing (fair queueing/WFQ)
(fair-queue command)
|
Supported for all SPAs.
|
Not supported.
|
Not supported.
|
Low Latency Queueing (LLQ)/ Queueing
(bandwidth command)
|
Strict priority only—Supported for all SPAs.
|
Strict priority only—Supported for all SPAs.
|
Supported for all SPAs.
|
Random Early Detection (RED)
(random-detect commands)
|
Supported for all SPAs.
|
Supported for all SPAs.
•ATM SPAs—Up to 106 unique WRED minimum threshold (min-th), maximum threshold (max-th), and mark probability profiles supported.
•Other SPAs—Up to 128 unique WRED min-th, max-th, and mark probability profiles supported.
|
Not supported.
|
Weighted RED (WRED)
|
Supported for all SPAs, with the following exception:
•WRED is not supported on bridged VCs.
|
Supported for all SPAs, with the following restriction:
•WRED is supported on bridged VCs with classification on precedence and DSCP values.
|
Not supported.
|
To configure a QoS CBWFQ policy, use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# policy-map policy-map-name
|
Creates or modifies a traffic policy and enters policy map configuration mode, where:
•policy-map-name—Specifies the name of the traffic policy to configure. Names can be a maximum of 40 alphanumeric characters.
|
Step 2
|
Router (config-pmap)# class {class-name | class-default}
|
Specifies the name of the traffic class to which this policy applies and enters policy-map class configuration mode, where:
•class-name—Specifies that the policy applies to a user-defined class name previously configured.
•class-default—Specifies that the policy applies to the default traffic class.
|
Step 3
|
Router(config-pmap-c)# bandwidth {bandwidth-kbps | percent percent}
|
Specifies the bandwidth allocated to a class belonging to a policy map.
Note The amount of bandwidth configured should be large enough to also accommodate Layer 2 overhead.
•bandwidth-kbps—Specifies the amount of bandwidth, in number of kbps, to be assigned to a class.
•percent—Specifies the amount of guaranteed bandwidth, based on the absolute percent of available bandwidth.
•percentage—Used in conjunction with the percent keyword, the percentage of the total available bandwidth to be set aside for the priority classes.
|
Step 4
|
Router(config-pmap-c)# queue-limit number-of-packets
|
Specifies the maximum number of packets the queue can hold for a class policy configured in a policy map.
•number-of-packets—A number in the range 1 to 64 specifying the maximum number of packets that the queue for this class can accumulate.
|
Configuring Dual Priority Queuing on a Cisco 7600 SIP-400
When configuring Dual Priority Queuing, consider the following guidelines:
•Only two priority levels are supported.
•Level 1 is higher than level 2.
•Propagation is supported on both levels.
•A priority without a level is mapped to level 1.
•The sum of bandwidth percentage and another queues' bandwidth reservation must not exceed 100% bandwidth.
•The police rate includes a Layer 2 header but not cyclic redundancy check (CRC), preamble, or interframe gap.
•Dual priority queuing is not supported on ATM SPAs.
To configure dual priority queuing, use the following commands:
Command or Action
|
Purpose
|
Router(config-pmap-c)# priority
|
Gives priority to a class of traffic belonging to a policy map.
|
Router(config-pmap-c)# priority level
|
Configures multiple priority queues.
•level—A range of priority levels. Valid values are from 1 (high priority) to 4 (low priority). The default is 1.
|
Router(config-pmap-c)# priority y ms
|
•ms—Specifies the burst size in bytes. The burst size configures the network to accommodate temporary bursts of traffic.
|
Router(config-pmap-c)# priority x kbps y bytes
|
•x kbps—Specifies the burst size in kbps.
•y bytes—Specifies the burst size in bytes.
|
Router(config-pmap-c)# priority percent x% | y ms
|
Enables conditional policing rate (kbps or link percent). Conditional policing is used if the logical or physical link is congested.
|
Configuring Percent Priority and Percent Bandwidth Support on a Cisco 7600 SIP-400
To configure percent priority and percent bandwidth, use the following commands:
Command or Action
|
Purpose
|
Router(config-pmap-c)# bandwidth x kbps
|
Specifies or modifies the bandwidth allocated for a class belonging to a policy map.
|
Router(config-pmap-c)# bandwidth percent x%
|
Specifies the amount of guaranteed bandwidth, based on an absolute percent of available bandwidth.
|
Router(config-pmap-c)# bandwidth remaining percent x%
|
•remaining percent—Amount of guaranteed bandwidth, based on a relative percent of available bandwidth.
|
Configuring QoS Traffic Shaping Policies on a SIP
This section describes SIP- and SPA-specific information for configuring QoS traffic policies for shaping traffic.
QoS Traffic Shaping Policy Configuration Guidelines
When configuring queueing features on a SIP, consider the following guidelines:
•The Cisco 7600 series router supports different forms of queueing features. See Table 4-13 to determine which traffic shaping features are supported by SIP type.
•Use a hierarchical policy if you want to achieve minimum bandwidth guarantees using CBWFQ with a Frame Relay map class. First, configure a parent policy to shape to the total bandwidth required (on the Cisco 7600 SIP-400, use the class-default in Cisco IOS Release 12.2(18)SXF, or a user-defined class beginning in Cisco IOS Release 12.2(33)SRA). Then, define a child policy using CBWFQ for the minimum bandwidth percentages.
•ATM SPAs do not support MQC-based traffic shaping. You need to configure traffic shaping for ATM interfaces using ATM Layer 2 VC shaping.
•For more detailed information about configuring congestion management features, refer to the Cisco IOS Quality of Service Solutions Configuration Guide document corresponding to your Cisco IOS software release.
Table 4-13 provides information about which QoS traffic shaping features are supported for SIPs on the Cisco 7600 series router.
Table 4-13 QoS Traffic Shaping Feature Compatibility by SIP and SPA Combination
Traffic Shaping Feature (shape command)
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Adaptive shaping for Frame Relay
(shape adaptive command)
|
Supported for all SPAs.
|
Not supported.
|
Not supported.
|
Class-based shaping
(shape average, shape peak commands)
|
Supported for all SPAs.
|
Supported for all SPAs, with the following exceptions:
•Committed burst (bc)—Not supported.
•Excess burst (be)—Not supported.
|
Supports shape average only for all SPAs.
|
Policy-map class shaping of average-rate of traffic by percentage of bandwidth
(shape average percent command)
|
Not supported.
|
Supported for all SPAs.
|
Not supported.
|
Policy-map class shaping with adaptation to backward explicit congestion notification (BECN)
(shape adaptive command)
|
Supported for all SPAs.
|
Not supported.
|
Not supported.
|
Policy-map class shaping with reflection of forward explicit congestion notification (FECN) as BECN
(shape fecn-adapt command)
|
Supported for all SPAs.
|
Not supported.
|
Not supported.
|
Policy-map class shaping of peak-rate of traffic by percentage of bandwidth
(shape peak percent command)
|
Not supported.
|
Not supported.
|
Not supported.
|
Configuring QoS Traffic Policing Policies on a SIP
This section describes SIP- and SPA-specific information for configuring QoS traffic policing policies.
QoS Traffic Policing Policy Configuration Guidelines
When configuring traffic policing on a SIP, consider the following guidelines:
•The Cisco 7600 series router supports different forms of policing using the police command. See Table 4-14 to determine which policing features are supported by SIP type.
•When configuring policing on the Cisco 7600 SIP-600, consider the following guidelines:
–The Cisco 7600 SIP-600 supports conform-action policing on input interfaces only, unless it is being implemented with queueing.
–The Cisco 7600 SIP-600 does not support any policing actions (shown in Table 4-15) using the exceed-action or violate-action keywords on an input interface.
–The Cisco 7600 SIP-600 supports exceed-action policing on an output interface with a drop action only, when the policing is being implemented with queueing.
–The Cisco 7600 SIP-600 supports marking for exceed-action policing only using the set-dscp-transmit command.
•When configuring a policing service policy and specifying the CIR in bits per second without specifying the optional conform (bc) or peak (be) burst in bytes, the Cisco 7600 SIP-400 calculates the burst size based on the number of bytes that it can transmit in 250 ms using the CIR value. For example, a CIR of 1 Mbps (or 1,000,000 bps) is equivalent to 125,000 bytes per second, which is 125 bytes per millisecond. The calculated burst is 250 x 125 = 31250 bytes. If the calculated burst is less than the interface maximum transmission unit (MTU), then the interface MTU is used as the burst size.
•You can use policing with queueing to limit the traffic rate.
•If a service policy configures both class-based marking and marking as part of a policing action, then the marking using policing takes precedence over any class-based marking.
•When configuring policing with MPB features on the Cisco 7600 SIP-200 and Cisco 7600 SIP-400, the set-cos-inner-transmit action is supported beginning in Cisco IOS Release 12.2(33)SRA.
Table 4-14 provides information about which policing features are supported for SIPs on the Cisco 7600 series router.
Table 4-14 QoS Policing Feature Compatibility by SIP and SPA Combination
Policing Feature (police command)
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Policing by aggregate policer
(police aggregate command)
|
Not supported.
|
Not supported.
|
Supported for all SPAs.
|
Policing by bandwidth using token bucket algorithm
(police command)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAS.
|
Policing by committed information rate (CIR) percentage
(police (percent) command—police cir percent form)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Not supported.
|
Policing with 2-color marker (CIR and peak information rate [PIR])
(police (two rates) command—police cir pir form)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Policing by flow mask
(police flow mask command)
|
Not supported.
|
Not supported.
|
Supported for all SPAs.
|
Policing by microflow
(police flow command)
|
Not supported.
|
Not supported.
|
Supported for all SPAs.
|
To create QoS traffic policies with policing, use the following commands beginning in global configuration mode:
| |
Command
|
Purpose
|
Step 1
|
Router(config)# policy-map policy-map-name
|
Creates or modifies a traffic policy and enters policy map configuration mode, where:
•policy-map-name—Specifies the name of the traffic policy to configure. Names can be a maximum of 40 alphanumeric characters.
|
Step 2
|
Router (config-pmap)# class {class-name | class-default}
|
Specifies the name of the traffic class to which this policy applies and enters policy-map class configuration mode, where:
•class-name—Specifies that the policy applies to a user-defined class name previously configured.
•class-default—Specifies that the policy applies to the default traffic class.
|
Use one of the following forms of police commands to evaluate traffic for the specified class. See Table 4-14 to determine which SIPs support the different policing features.
|
Step 3
|
Router(config-pmap-c)# police bps [burst-normal] [burst-max] conform-action action exceed-action action violate-action action
|
Specifies a maximum bandwidth usage by a traffic class through the use of a token bucket algorithm, where:
•bps—Specifies the average rate in bits per second. Valid values are 8000 to 200000000.
•burst-normal—(Optional) Specifies the normal burst size in bytes. Valid values are 1000 to 51200000. The default normal burst size is 1500 bytes.
•burst-max—(Optional) Specifies the excess burst size in bytes. Valid values are 1000 to 51200000.
•action—Specifies the policing command (as shown in Table 4-15) for the action to be applied to the corresponding conforming, exceeding, or violating traffic.
|
Step 4
|
Router(config-pmap-c)# police cir percent percentage [burst-in-msec] [bc conform-burst-in-msec] [pir percent percentage] [be peak-burst-in-msec] [conform-action action [exceed-action action [violate-action action]]]
|
Configures traffic policing on the basis of a percentage of bandwidth available on an interface, where:
•cir percent percentage—Specifies the committed information rate (CIR) bandwidth percentage. Valid values are 1 to 100.
•burst-in-msec—(Optional) Burst in milliseconds. Valid values are 1 to 2000.
•bc conform-burst-in-msec—(Optional) Specifies the conform burst (bc) size used by the first token bucket for policing traffic in milliseconds. Valid values are
1 to 2000.
•pir percent percentage—(Optional) Specifies the peak information rate (PIR) bandwidth percentage. Valid values are 1 to 100.
•be peak-burst-in-msec—(Optional) Specifies the peak burst (be) size used by the second token bucket for policing traffic in milliseconds. Valid values are 1 to 2000.
•action—Specifies the policing command (as shown in Table 4-15) for the action to be applied to the corresponding conforming, exceeding, or violating traffic.
|
Step 5
|
Router(config-pmap-c)# police {cir cir} [bc conform-burst] {pir pir} [be peak-burst] [conform-action action [exceed-action action [violate-action action]]]
|
Configures traffic policing using two rates, the committed information rate (CIR) and the peak information rate (PIR), where:
•cir cir—Specifies the CIR at which the first token bucket is updated as a value in bits per second. Valid values are 8000 to 200000000.
•bc conform-burst—(Optional) Specifies the conform burst (bc) size in bytes used by the first token bucket for policing. Valid values are 1000 to 51200000.
•pir pir—Specifies the PIR at which the second token bucket is updated as a value in bits per second. Valid values are 8000 to 200000000.
•be peak-burst—(Optional) Specifies the peak burst (be) size in bytes used by the second token bucket for policing. The size varies according to the interface and platform in use.
•action—(Optional) Specifies the policing command (as shown in Table 4-15) for the action to be applied to the corresponding conforming, exceeding, or violating traffic.
|
Step 6
|
Router(config-pmap-c)# police flow {bits-per-second [normal-burst-bytes] [maximum-burst-bytes] [pir peak-rate-bps]} | [conform-action action] [exceed-action action] [violate-action action]
|
Configures a microflow policer, where:
•bits-per-second—Specifies the CIR in bits per second. Valid values are from 32000 to 4000000000 bits per second.
•normal-burst-bytes—(Optional) Specifies the CIR token bucket size. Valid values are from 1000 to 512000000 bytes.
•maximum-burst-bytes—(Optional) Specifies the PIR token-bucket size. Valid values are from 1000 to 32000000 bytes.
•pir peak-rate-bps—(Optional) Specifies the PIR in bits per second. Valid values are from 32000 to 4000000000 bits per second.
•action—Specifies the policing command (as shown in Table 4-15) for the action to be applied to the corresponding conforming, exceeding, or violating traffic.
|
Step 7
|
Router(config-pmap-c)# police flow mask {dest-only | full-flow | src-only} {bits-per-second [normal-burst-bytes] [maximum-burst-bytes]} [conform-action action] [exceed-action action]
|
Configures a flow mask to be used for policing, where:
•dest-only—Specifies the destination-only flow mask.
•full-flow—Specifies the full-flow mask.
•src-only—Specifies the source-only flow mask.
•bits-per-second—Specifies the CIR in bits per second. Valid values are from 32000 to 4000000000 bits per second.
•normal-burst-bytes—(Optional) Specifies the CIR token bucket size. Valid values are from 1000 to 512000000 bytes.
•maximum-burst-bytes—(Optional) Specifies the PIR token bucket size. Valid values are from 1000 to 32000000 bytes.
•action—Specifies the policing command (as shown in Table 4-15) for the action to be applied to the corresponding conforming or exceeding traffic.
|
Step 8
|
Router(config-pmap-c)# police aggregate name
|
Specifies a previously defined aggregate policer name and configures the policy-map class to use the specified name of the aggregate policer.
|
Table 4-15 provides information about which policing actions are supported for SIPs on the Cisco 7600 series router.
Note For restrictions on use of certain marking features with different types of policing actions (conform, exceed, or violate actions), be sure to see the "QoS Traffic Policing Policy Configuration Guidelines" section.
Table 4-15 QoS Policing Action Compatibility by SIP and SPA Combination
Policing Action (set command)
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Drop the packet
(drop command)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs—Input interface only.
|
Set the ATM CLP bit to 1 and transmit
(set-clp-transmit command)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Not supported.
|
Set the inner CoS value and transmit
(set-cos-inner-transmit command)
|
Supported in Cisco IOS Release 12.2(33)SRA with bridging features.
|
Supported in Cisco IOS Release 12.2(33)SRA with bridging features.
|
Not supported.
|
Set the Frame Relay DE bit to 1 and transmit
(set-frde-transmit command)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Not supported.
|
Set the IP precedence and transmit
(set-prec-transmit command)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs —Input interface only.
|
Set the IP DSCP and transmit
(set-dscp-transmit command)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs—Input interface only.
|
Set the MPLS EXP bit (0-7) on imposition and transmit
(set-mpls-experimental-imposition-transmit command
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Set the MPLS EXP bit in the topmost label and transmit
(set-mpls-experimental-topmost-transmit command)
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Supported for all SPAs.
|
Transmit all packets without alteration
(transmit command)
|
Supported for all SPAs.
|
Supported for all SPAs
|
Supported for all SPAs.
|
Attaching a QoS Traffic Policy to an Interface
Before a traffic policy can be enabled for a class of traffic, it must be configured on an interface. A traffic policy also can be attached to an ATM permanent virtual circuit (PVC) subinterface, Frame Relay data-link connection identifier (DLCI), and Ethernet subinterfaces.
Traffic policies can be applied for traffic coming into an interface (input), and for traffic leaving that interface (output).
Attaching a QoS Traffic Policy for an Input Interface
When you attach a traffic policy to an input interface, the policy is applied to traffic coming into that interface. To attach a traffic policy for an input interface, use the following command beginning in interface configuration mode:
Command
|
Purpose
|
Router(config-if)# service-policy input policy-map-name
|
Attaches a traffic policy to the input direction of an interface, where:
•policy-map-name—Specifies the name of the traffic policy to configure.
|
Attaching a QoS Traffic Policy to an Output Interface
When you attach a traffic policy to an output interface, the policy is applied to traffic leaving that interface. To attach a traffic policy to an output interface, use the following command beginning in interface configuration mode:
Command
|
Purpose
|
Router(config-if)# service-policy output policy-map-name
|
Attaches a traffic policy to the output direction of an interface, where:
•policy-map-name—Specifies the name of the traffic policy to configure.
|
Configuring Network-Based Application Recognition and Distributed Network-Based Application Recognition
Note Network-Based Application Recognition (NBAR) and Distributed Network-Based Application Recognition (dNBAR) are supported on the Cisco 7600 SIP-200 only.
The purpose of IP quality of service (QoS) is to provide appropriate network resources (bandwidth, delay, jitter, and packet loss) to applications. QoS maximizes the return on investments on network infrastructure by ensuring that mission-critical applications get the required performance and noncritical applications do not hamper the performance of critical applications.
IP QoS can be deployed by defining classes or categories of applications. These classes are defined by using various classification techniques available in Cisco IOS software. After these classes are defined and attached to an interface, the desired QoS features, such as marking, congestion management, congestion avoidance, link efficiency mechanisms, or policing and shaping can then be applied to the classified traffic to provide the appropriate network resources amongst the defined classes.
Classification, therefore, is an important first step in configuring QoS in a network infrastructure.
NBAR is a classification engine that recognizes a wide variety of applications, including web-based and other difficult-to-classify protocols that utilize dynamic TCP/UDP port assignments. When an application is recognized and classified by NBAR, a network can invoke services for that specific application. NBAR ensures that network bandwidth is used efficiently by classifying packets and then applying QoS to the classified traffic. Some examples of class-based QoS features that can be used on traffic after the traffic is classified by NBAR include:
•Class-based marking (the set command)
•Class-based weighted fair queueing (the bandwidth and queue-limit commands)
•Low latency queueing (the priority command)
•Traffic policing (the police command)
•Traffic shaping (the shape command)
Note The NBAR feature is used for classifying traffic by protocol. The other class-based QoS features determine how the classified traffic is forwarded and are documented separately from NBAR.
Furthermore, NBAR is not the only method of classifying network traffic so that QoS features can be applied to classified traffic.
For information on the class-based features that can be used to forward NBAR-classified traffic, see the individual feature modules for the particular class-based feature as well as the Cisco IOS Quality of Service Solutions Configuration Guide.
Many of the non-NBAR classification options for QoS are documented in the "Modular Quality of Service Command-Line Interface" section of the Cisco IOS Quality of Service Solutions Configuration Guide. These commands are configured using the match command in class map configuration mode.
NBAR introduces several new classification features that identify applications and protocols from Layer 4 through Layer 7:
•Statically assigned TCP and UDP port numbers
•Protocols that are non-UDP and non-TCP
•Dynamically assigned TCP and UDP port numbers. Classification of such applications requires stateful inspection; that is, the ability to discover the data connections to be classified by parsing the connections where the port assignments are made.
•Sub-port classification or classification based on deep packet inspection; that is, classification by looking deeper into the packet.
NBAR can classify static port protocols. Although access control lists (ACLs) can also be used for this purpose, NBAR is easier to configure and can provide classification statistics that are not available when using ACLs.
NBAR includes a Protocol Discovery feature that provides an easy way to discover application protocols that are transversing an interface. The Protocol Discovery feature discovers any protocol traffic supported by NBAR. Protocol Discovery maintains the following per-protocol statistics for enabled interfaces: total number of input and output packets and bytes, and input and output bit rates. The Protocol Discovery feature captures key statistics associated with each protocol in a network that can be used to define traffic classes and QoS policies for each traffic class.
For specific information about configuring NBAR and dNBAR, refer to the Network-Based Application Recognition and Distributed Network-Based Application Recognition feature documentation located at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/dtnbarad.htm
Configuring Hierarchical QoS on a SIP
Table 4-16 provides information about where the hierarchical QoS features for SPA interfaces are supported.
Table 4-16 Hierarchical QoS Feature Compatibility by SIP and SPA Combination
Feature
|
Cisco 7600 SIP-200
|
Cisco 7600 SIP-400
|
Cisco 7600 SIP-600
|
Hierarchical QoS for EoMPLS VCs
|
Supported for all SPAs in Cisco IOS Release 12.2(18)SXE and later, and in Cisco IOS Release 12.2(33)SRA.
|
Supported for all SPAs beginning in Cisco IOS Release 12.2(33)SRA.
|
Supported for all SPAs in Cisco IOS Release 12.2(18)SXF and later, and in Cisco IOS Release 12.2(33)SRA.
|
Hierarchical QoS—Tiered policy maps with parent policy using class-default only on the main interface.
|
Not applicable.
|
Supported for all SPAs in Cisco IOS Release 12.2(18)SXF and later.
|
Supported in Cisco IOS Release 12.2(18)SXF and later, and in Cisco IOS Release 12.2(33)SRA using match vlan command in parent policy.
|
Hierarchical QoS—Tiered policy maps with parent policy in user-defined or class-default classes on the main interface.
|
Supported for all SPAs in Cisco IOS Release 12.2(18)SXF and later, and in Cisco IOS Release 12.2(33)SRA.
|
Supported for all SPAs in Cisco IOS Release 12.2(33)SRA.
|
Not supported.
|
Configuring Hierarchical QoS with Tiered Policy Maps
Hierarchical QoS with tiered policy maps is a configuration where the actions associated with a class contain a queuing action (such as shaping) and a nested service policy, which in itself is a policy map with classes and actions. This hierarchy of the QoS policy map is then translated into a corresponding hierarchy of queues.
Hierarchical QoS with Tiered Policy Maps Configuration Guidelines
When configuring hierarchical QoS with tiered policy maps on a SIP, consider the following guidelines:
•For information about where hierarchical QoS with tiered policy maps is supported, see Table 4-16.
•You can configure up to three levels of hierarchy within the policy maps.
•The parent policy map has the following restrictions on a main interface:
–In Cisco IOS Release 12.2(18)SXF and later—Supports the shape queueing action in the default class (class-default) only.
–In Cisco IOS Release 12.2(33)SRA—Supports VLAN or ACL matching, and shape or bandwidth queueing actions in any class, user-defined and class-default.
•When configuring hierarchical QoS for software-based EoMPLS on the Cisco 7600 SIP-600, if you configure match input vlan in the parent policy, then you can only configure match qos-group in the child policy.
•In hierarchical QoS, you cannot configure just a set command in the parent policy. The set command works only if you configure other commands in the policy.
•The child policy map supports shape, bandwidth, and WRED QoS features.
•With hierarchical QoS on a subinterface, the parent policy map supports hierarchical QoS using the shape average command as a queueing action in the default class (class-default) only.
•If you configure shaping at both the parent policy and the child policy, the traffic is shaped first according to the parameters defined in the parent policy, followed by the parameters of the child policy.
•If you configure service policies at the main interface, subinterface, and VC levels, then the policy applied at the VC level takes precedence over a policy at the interface.
•In a Frame Relay configuration, if you need to define service policies at the interface, subinterface, and PVC at the same time, then you can use a map class.
•For a POS subinterface with a Frame Relay PVC, a service policy can be applied either at the subinterface or at the PVC, but not both.
•Use a hierarchical policy if you want to achieve minimum bandwidth guarantees using CBWFQ with a map class. First, configure a parent policy to shape to the total bandwidth required (use the class-default in Cisco IOS Release 12.2(18)SXF, or a user-defined class beginning in Cisco IOS Release 12.2(33)SRA). Then, define a child policy using CBWFQ for the minimum bandwidth percentages.
•You can configure hierarchical QoS up to the following limits, according to the current Cisco IOS software limits:
–Up to 1024 class maps
–Up to 1024 policy maps
–Up to 256 classes within a policy map
Configuring Hierarchical QoS for EoMPLS VCs
The Hierarchical Quality of Service (HQoS) for EoMPLS VCs feature extends support for hierarchical, parent and child relationships in QoS policy maps. This feature also provides EoMPLS per-VC QoS for point-to-point VCs.
The new feature adds the ability to match the virtual LAN (VLAN) IDs that were present on a packet when the packet was originally received by the router. It also supports the ability to match on a QoS group that is set to the same value of the IP precedence or 802.1P class of service (CoS) bits that are received on the incoming interface. This allows service providers to classify traffic easily for all or part of a particular EoMPLS network, as well as to preserve the customer's original differentiated services (DiffServ) QoS values.
In EoMPLS applications, the parent policy map typically specifies the maximum or the minimum bandwidth for a group of specific VCs in an EoMPLS network. Then child policy maps in the policy can implement a different bandwidth or perform other QoS operations (such as traffic shaping) on a subset of the selected VCs.
This feature enables service providers to provide more granular QoS services to their customers. It also gives service providers the ability to preserve customer IP precedence or CoS values in the network.
Note For information about where hierarchical QoS for EoMPLS VCs is supported, see Table 4-16.
For more information about configuring hierarchical QoS for EoMPLS VCs, refer to the Optical Services Module Configuration Note located at the following URL:
http://www.cisco.com/application/pdf/en/US/guest/products/ps368/c1069/ccmigration_09186a008069bfcc.pdf
Configuring PFC QoS on a Cisco 7600 SIP-600
The Cisco 7600 SIP-600 supports most of the same QoS features as those supported by the Policy Feature Card on the Cisco 7600 series router.
This section describes those QoS features that have SIP-specific configuration guidelines. After you review the SIP-specific guidelines described in this document, then refer to the Cisco 7600 Series Cisco IOS Software Configuration Guide, 12.2SX located at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/software/122sx/swcg/index.htm
PFC QoS on a Cisco 7600 SIP-600 Configuration Guidelines
•Output policing is not supported.
Configuring Lawful Intercept on a Cisco 7600 SIP-400
This section describes configuring Lawful Intercept on a Cisco 7600 SIP-400. For initial configuration of the Lawful Intercept feature, see the Cisco 7600 Lawful Intercept Configuration Guide at the following URL:
http://www.cisco.com/en/US/products/hw/routers/ps368/products_configuration_guide_book09186a00807e0acb.html
To configure Lawful Intercept on a Cisco 7600 SIP-400, use the following commands:
Command
|
Purpose
|
Router(config)# snmp-server view viewA ciscoTap2MIB included
Router(config)# snmp-server view viewA ciscoIpTapMIB included
|
Creates a view having access to the MIBS.
|
Router(config)# snmp-server group groupA v3 auth read viewA write viewA notify viewA
|
Creates a group having access to this view.
|
Router(config)# snmp-server user user1 groupA v3 auth md5 cisco
|
Creates a user who is a member of groupA.
|
Configuring Security ACLs on an Access Interface on a Cisco 7600 SIP-400
This section describes configuration of the SIP-specific ACL features on access interfaces. Before referring to any other ACL documentation for the platform or in the Cisco IOS software, use this section to determine SIP-specific ACL feature support and configuration guidelines.
An Access Control List (ACL) is a collection of ordered permit and deny statements, referred to as Access Control Entries (ACEs), which determine whether a particular packet will be forwarded or dropped. An ACL offers application layer awareness, providing operational staff with some flexibility in the level of isolation of a host. For instance, an ACL may be applied to enforce complete host isolation, denying all traffic to and from that particular host or, alternately, to just filter certain traffic flows, while permitting all others.
For additional details about ACL concepts and features in Cisco IOS Release 12.2, refer to the Cisco IOS Security Configuration Guide, Release 12.2, at the following URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca7c0.html
This section includes the following topics:
• Security ACL Configuration Guidelines
• Configuring Security ACL
Security ACL Configuration Guidelines
•Up to 100 unique ACLs are recommended per chassis, with a maximum of 24 ACEs per ACL for Security ACL.
•Up to one input ACL and one output ACL are recommended for all 8K subinterfaces on the SIP.
•Source and Destination IPv4 Address, Port Number, ToS/DSCP, Protocol type, and TCP flags can be specified in the ACEs. As of Cisco IOS Release 12.2(33)SRB, IPV6 is not supported.
•Template Security ACL is not supported as of Cisco IOS Release 12.2(33)SRB.
•Security ACLs are only supported on a Route Switch Processor 720 (RSP720) with a Cisco 7600 SIP-400.
•Standard, extended, and named ACLs are supported; other ACL types such as reflexive and time-based ACLs are not supported.
Configuring Security ACL
| |
Command or Action
|
Purpose
|
Step 1
|
Router(config)# access-list access list
number permit ip host ip address any
|
Configures an access list.
|
Step 2
|
Router(config-int)# interface gigabitethernet slot/subslot/port access
|
Selects the gigabitethernet interface.
|
Step 3
|
Router(config-int)# ip address address
|
Specifies the IP address.
|
Step 4
|
Router(config-int)# encapsulation dot1q vlan-id
|
Enables traffic encapsulation.
•vlan-id—Virtual LAN identifier; valid values are from 1 to 4094.
|
Step 5
|
Router(config-int)# ip access-group access-list-number in
|
Sets filtering method.
•access-list-number—Number of an access list. This is a decimal number from 1 to 199 or 1300 to 2699.
•in—Filters on inbound packets.
|
Step 6
|
Router(config-int)# ip access-group access-list-number out
|
Sets filtering method.
•access-list-number—Number of an access list. This is a decimal number from 1 to 199 or 1300 to 2699.
•out—Filters on outbound packets.
|
Verifying ACL Configuration
Use the following command to verify ACL configuration:
Command or Action
|
Purpose
|
Router# show access-list [access-list-number | name]
|
Displays access list configuration.
•access-list-number—(Optional) Access list number to display. The range is 0 to 1199. The system displays all access lists by default.
•name—(Optional) Name of the IP access list to display.
|
Configuring Per-Subscriber/Per-Protocol CoPP on Access Interfaces on a Cisco 7600 SIP-400
This section describes configuring Per-Subscriber/Per-Protocol Control Plane Policing (CoPP) on a Cisco 7600 SIP-400.
Because the majority of control plane processing is done on the CPU, a malicious user can attack a router by simply pumping control plane traffic to the router. On an unprotected router, this would result in the CPU utilization nearing 100%, resource exhaustion, and the command line console getting locked, which would intensify the problem as the user would not be able to apply any rectifying action on the router. This feature allows per-subscriber, per-protocol CoPP policing.
CoPP Per-Subscriber/Per-Protocol Configuration Guidelines
•The Cisco 7600 CoPP feature is supported with a Route Switch Processor 720 (RSP720) and Cisco 7600 SIP-400 combination only.
•When enabling the RP-based aggregate CoPP functionality, the required class maps should be configured for each of the protocol-matching criteria. The CoPP policy maps should be created for all the protocols that need to be policed.
•Once the router processor decides to install a rate limiter on an interface, there will be a delay for actually installing the rate limiter on the Cisco 7600 SIP-400. During this interval, it is possible that the aggregate rate limiter would start dropping good user packets, if the per-interface rates are not chosen carefully. For example, consider that there are 10 interfaces and 100 pps is used as the aggregate rate and 15 pps as the per-interface rate. If there are seven attacks on the router at a time, the aggregate limit would be exceeded and user traffic would be affected.
•As of Cisco IOS Release 12.2(33)SRB, the CoPP Per-subscriber/Per-Protocol feature is only supported for DHCP, ARP, and ICMP protocols. DHCP and ARP policing are performed on the SPA, while ICMP policing is performed at the router processor level.
To configure Per-Subscriber/Per-Protocol CoPP support, use the following commands.
Command or Action
|
Purpose
|
Router(config)# class-map arp-peruser
|
Creates a class map for ARP.
|
Router(config-cmap)# match protocol arp
|
Matches ARP traffic.
|
Router(config-cmap)# match subscriber access
|
Defines the class map for access interfaces.
|
Router(config)# class-map dhcp-peruser
|
Creates a class map for DHCP.
|
Router(config-cmap)# match protocol dhcp
|
Configures the match criterion for a DHCP class map.
|
Router(config-cmap) match subscriber access
|
Defines the class map for access interfaces.
|
Router(config)# policy-map copp-peruser
|
Specifies CoPP as the policy map.
|
Router(config-pmap)# class arp-peruser
|
Creates an ARP peruser class.
|
Router(config-pmap-c)# police rate units pps burst burst-in-packets packets
|
Specifies the burst rate.
•units—Rate at which traffic is policed in packets per second. Valid values are 1 to 2000000 pps.
•burst-in-packets—(Optional) Specifies the burst rate that is used for policing traffic. Valid values are 1 to 512000 packets.
|
Router(config-pmap-c)# class dhcp-peruser
|
Creates a DHCP peruser class.
|
Router(config-pmap-c)# police rate units pps burst burst-in-packets packets
|
Specifies the burst rate.
•units—Rate at which traffic is policed in packets per second. Valid values are 1 to 2000000 pps.
•burst-in-packets—(Optional) Specifies the burst rate that is used for policing traffic. Valid values are 1 to 512000 packets.
|
Router(config)# control-plane user-type access
|
Applies the policy on control-plane-user interface.
|
Router(config-cp-user)# service-policy input copp-peruser
|
Configures the per-user policy map.
|
Router(config)# platform copp observation-period time
|
Configures the observation window.
•time—Amount of time in minutes.
|
Router# platform copp interface arp off
|
Clears a per-subinterface rate limiter for ARP on an interface.
•interface—Defines interface.
|
Verifying Per-Subscriber/Per-Protocol CoPP
To verify Per-Subscriber/Per-Protocol CoPP configuration, use the following commands:
Command or Action
|
Purpose
|
Router# show platform copp rate-limit [arp | dhcp | all]
|
Displays configuration settings.
•arp—Displays ARP information.
•dhcp—Displays DHCP information.
•all—Displays ARP and DHCP information.
|
Router# show policy-map policy-map-name
|
Verifies that packets match the desired class.
•policy-map-name—(Optional) Name of the policy map.
|
Resetting a SIP
To reset a SIP, use the following command in privileged EXEC configuration mode:
Command
|
Purpose
|
Router# hw-module module slot reset
|
Turns power off and on to the SIP in the specified slot, where:
•slot—Specifies the chassis slot number where the SIP is installed.
|
Configuration Examples
This section includes the following examples for configuring SIPs installed in a Cisco 7600 series router:
• Layer 2 Interworking Configuration Examples
• MPLS Configuration Examples
• QoS Configuration Examples
Layer 2 Interworking Configuration Examples
This section includes the following Layer 2 interworking configuration examples:
• BCP in Trunk Mode Configuration Example
• BCP in Single-VLAN Mode Configuration Example
BCP in Trunk Mode Configuration Example
The following example shows how to configure BCP in trunk mode:
! Enter global configuration mode.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
! Specify the interface address.
Router(config)# interface pos4/1/0
! Put the interface in Layer 2 mode for Layer 2 configuration.
Router(config-if)# switchport
%Please shut/no shut POS4/1/0 to bring up BCP
! When the switchport command is configured, the interface is automatically configured for
! trunk mode and nonegotiate status.
! Restart the interface to enable BCP.
Router(config-if)# shutdown
Router(config-if)# no shutdown
! Enable all VLANs for receiving and transmitting traffic on the trunk.
Router(config-if)# switchport trunk allowed vlan all
%Internal vlans not available for bridging:1006-1018,1021
The following example shows sample output from the show running-config command for this configuration. The switchport mode trunk and switchport nonegotiate commands are automatically NVgened when the switchport command is configured:
Router# show running-config interface pos4/1/0
Building configuration...
Current configuration : 191 bytes
switchport trunk allowed vlan all
