Table Of Contents
IP Subscriber Awareness over Ethernet
Overview
Benefits
IP Subscriber Interfaces
IP Subscriber Session
IP Subscriber Session Features
QoS Recommendations
Bandwidth-Remaining Ratio Recommendations
BRR Configuration Guidelines
BRR Configuration Instructions
Priority-Rate Propagation Recommendations
Unsupported IP Subscriber Session Features
IP Subscriber Awareness over Ethernet Configuration Guidelines
Interaction with Other Features
Configuring IP Subscriber Awareness over Ethernet
Configuration Summary
Configuration Examples
Command Reference
interface access
IP Subscriber Awareness over Ethernet
This chapter provides information about how various Cisco 7600 features are being scaled to support the IP Subscriber Awareness over Ethernet feature (sometimes referred to as IP subscriber aggregation), which is being introduced for the Cisco 7600 series router in Cisco IOS Release 12.2SRB. This chapter contains the following sections:
•
Overview
•IP Subscriber Session Features
•IP Subscriber Awareness over Ethernet Configuration Guidelines
•Configuring IP Subscriber Awareness over Ethernet
•Command Reference
Overview
IP Subscriber Awareness over Ethernet is designed for use in an architecture in which the Cisco 7600 router is used as a DSLAM Gigabit Ethernet (GE) aggregator. In this scenario, the DSLAM is connected to the router through a physical port that can carry data for multiple VLANs.
The IP Subscriber Awareness over Ethernet feature supports two models of carrying services between the subscriber and the DSLAM:
•Per-service VLAN model—One or more ATM VCs is used to carry each type of service (video, voice, and data) between the subscriber and the VLAN.
•Per-subscriber VLAN model—A single ATM VC is used to carry all traffic (video, voice, and data) between the subscriber and the DSLAM.
Figure 22-1 shows an example of a wireline Ethernet architecture where IP Subscriber Awareness over Ethernet might be used.
Figure 22-1 Wireline Ethernet Architecture
The following sections provide more details about the IP Subscriber Awareness over Ethernet feature:
•Benefits
•IP Subscriber Interfaces
•IP Subscriber Session
•IP Subscriber Session Features
Benefits
The IP Subscriber Awareness over Ethernet feature provides the following benefits:
•IP session termination and IP session aggregation on the Cisco 7600 router.
•Support for up to 32000 IP subscribers on a router (with a maximum of 8000 subscribers on a single Cisco 7600 SIP-400).
•Interface scalability to support up to 32000 interfaces on the router.
–Support for up to 1000 subinterfaces on each physical port.
–Support for up to 8000 subinterfaces on each Cisco 7600 SIP-400.
•DHCP and Radius accounting for IP subscribers. Support for 256 DHCP pools, and DHCP can handle up to 150 calls per second for IP subscriber sessions.
•QoS support for individual IP subscribers (up to 32000 subscribers), including: classification (IP prec and DSCP), policing, shaping, marking, priority queues, and weighted random early detection (WRED).
•Per-subscriber statistics and accounting information.
•Support for up to 96000 ARP entries.
•RPR, RPR+, stateful switchover (SSO), and non-stop forwarding (NSF) are provided for the IP subscribers.
•Control plane protection (CoPP) protects against denial of service (DOS) and other attacks.
IP Subscriber Interfaces
Cisco IOS Release 12.2SRB introduces a new type of interface to represent IP subscribers:
•Access—A subinterface that represents an individual IP subscriber. The access subinterface can be configured for .1Q or Q-in-Q encapsulation.
You apply traffic shaping and policing policies (including HQoS) to the access interface to define the amount of bandwidth to allocate for different types of subscriber traffic (for example, voice and data).
Note You configure the access interface as a subinterface of the physical interface that the IP subscriber is connected to.
Example
The following example shows an access subinterface on the interface :
interface GigabitEthernet 1/0/0.100 access
IP Subscriber Session
An IP subscriber session exists while an IP subscriber is using its shared VLAN to access the network. To begin an IP subscriber session, the router must assign an IP address to the subscriber's access subinterface. You can either assign a static IP address to the subinterface, or you can allow DHCP to assign an address. Following are some notes about both methods of assigning an IP address:
•Static IP address—If you assign a static IP address to the access subinterface, the IP subscriber session is considered to always be Up. We recommend that you do not configure many IP subscribers with static IP addresses.
•DHCP-assigned IP address—You can allow DHCP to assign an IP address for the subscriber session. An IP subscriber session begins when the router receives a DHCP discover packet for the subscriber and an IP address is assigned for the subscriber. The session is terminated when the subscriber receives a DHCP release message and its IP address is released. If the subscriber session is VRF aware (that is, if the subscriber belongs to a VRF), the VRF-aware DHCP pool must be used.
Note•The router can be operating as a DHCP server or DHCP relay device.
•To configure an IP subscriber as part of a VRF (that is, to make the subscriber session VRF aware), configure the VRF under the access subinterface.
IP Subscriber Session Features
The following features are provided for IP subscriber sessions:
•Per-subscriber control plane policing and protection (CoPP)—Provides protection against denial of service (DOS) and other attacks for individual subscribers. When an attack occurs, the router notifies the network administrator and begins policing the malicious traffic. This feature allows policing of ARP, DHCP, and ICMP traffic. For information about how CoPP operates on the Cisco 7600 SIP-400, see:
/en/US/products/hw/routers/ps368/module_installation_and_configuration_guides_chapter09186a0080440138.html#wp1351662
•Per-subscriber security ACL—Allows you to apply security access control lists (ACLs) to individual subscribers. For information about how this feature works on the Cisco 7600 SIP-400, see:
/en/US/products/hw/routers/ps368/module_installation_and_configuration_guides_chapter09186a0080440138.html#wp1351562
•Per-subscriber Radius accounting—Enables system administrators to track IP session activity for individual subscribers, and to extract subscriber accounting records periodically. Per-subscriber Radius accounting works with DHCP IP address assignment, and improves the authentication, authorization, and accounting (AAA) of broadband service delivery. For information about this feature, see its feature description at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122sr/newft/122srb33/ipradacc.htm
•Lawful intercept—Enables a Law Enforcement Agency (LEA) to perform electronic surveillance on a subscriber as authorized by a court order. To assist in the surveillance, the service provider intercepts the subscriber's traffic as it passes through one of their routers, and sends a copy of the intercepted traffic to the LEA without the subscriber's knowledge. For information about this feature, see the documents at the following URLs:
http://www.cisco.com/univercd/cc/td/doc/product/core/cis7600/76licfg/index.htm
/en/US/products/hw/routers/ps368/module_installation_and_configuration_guides_chapter09186a0080440138.html#wp1351508
•Quality of Service—Standard QoS features are supported for individual subscribers (access subinterfaces), including classification, marking, policing, shaping, priority queuing, and weighted random early detection (WRED). For information about recommended QoS settings for IP Subscriber Awareness over Ethernet, see the following section ("QoS Recommendations"). For information about QoS features on the Cisco 7600 SIP-400, see the information about QoS features in the "Cisco 7600 SIP-400 Features" section of the document at this URL:
/en/US/products/hw/routers/ps368/module_installation_and_configuration_guides_chapter09186a008044013b.html#wp1094663
In addition to standard QoS features, the following new Cisco 7600 SIP-400 QoS features are being introduced to support the deployment of broadband services:
•Dual-priority queues—Provide two priority queues for voice and video traffic for 4000 to 8000 subscribers. You can assign a different priority level to each traffic class to configure the router to treat both types of traffic as priority traffic but to handle them differently (for example, by giving voice traffic precedence over video traffic).
•Bandwidth-remaining ratio (BRR)—Allows service providers to prioritize subscriber traffic during periods of congestion. You can use the Distribution of Remaining Bandwidth Using Ratio feature to specify the relative weight of a subinterface or class queue with respect to other subinterfaces or queues. For information about this feature, see the "Bandwidth-Remaining Ratio Recommendations" section.
•Priority-rate propagation—Takes the priority level and traffic rate assigned to priority traffic in a low-level queue and applies that level and rate to priority traffic at all higher-level queues in the queue hierarchy, even if those queues are not specifically configured for minimum rates or priority. For more information, see the "Priority-Rate Propagation Recommendations" section.
QoS Recommendations
When you configure QoS features on the Cisco 7600 SIP-400 for use with the IP Subscriber Awareness over Ethernet feature, note the following configuration guidelines and recommendations:
•The Cisco 7600 SIP-400 is capable of throughput of 5.1 to 5.6 gigabits per second (Gbps). We recommend that you do not oversubscribe the card beyond 8 Gbps. Beyond this limit, the card's behavior is unpredictable. [CSCsg67629]
•Oversubscription is supported only on the 5-Port Gigabit Ethernet SPA (SPA-5X1GE-V2).
Egress Oversubscription
•High-priority traffic (typically voice and video) must have an IP precedence value of 5, 6, or 7.
•IP precedence values of 0, 1, 2, 3, or 4 will result in drops if oversubscription occurs, even if the traffic is classified as priority traffic in a QoS policy. [CSCsg67721]
Note We strongly recommend that the IP precedence value and VLAN user priority values of packets match. If ingress oversubscription occurs, priority traffic with non-matching IP precedence and VLAN user priority values might be dropped at the SPA level. [CSCsg97434]
Ingress Oversubscription
•High-priority traffic (typically voice) must have VLAN user priority values of 5, 6, or 7. Priority values of 0, 1, 2, 3, or 4 will result in drops if oversubscription occurs, even if the traffic is classified as priority traffic by a QoS policy. [CSCsg97434, CSCsg67721]
QoS Counter Updates
•To obtain statistics for an individual IP subscriber session, issue the show policy-map interface command two or three times. This is necessary because the counters retain their existing values the first time you issue the command.
•If you issue the show policy-map interface command and do not specify an interface, the router must update all of the session counters. With 32000 subscribers, this can take up to 30 minutes.
Bandwidth-Remaining Ratio Recommendations
The Bandwidth-Remaining Ratio (BRR) feature (also called Distribution of Remaining Bandwidth Using Ratio) allows service providers to prioritize subscriber traffic during periods of congestion. You can use the feature to specify the relative weight of a subinterface or class queue with respect to other subinterfaces or queues. During congestion, the router uses the bandwidth-remaining ratio to optimize the scheduling of uncommitted bandwidth on subinterfaces and class queues. Without BRR, the unassigned bandwidth on a physical interface is equally distributed among all queues. For an overview of this feature, see its feature description at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122sb/newft/122sb31/bwratio.htm
This section provides recommendations and guidelines for configuring BRR on the Cisco 7600 SIP-400 to support IP Subscriber Awareness over Ethernet. It contains the following sections:
•BRR Configuration Guidelines
•BRR Configuration Instructions
BRR Configuration Guidelines
Observe the following Cisco 7600 specific guidelines and considerations as you configure this feature:
•Supported only on the Cisco 7600 SIP-400 with 2-port and 5-port Gigabit Ethernet (GE) SPAs.
•Available only on GE interfaces (because the feature is only supported on GE SPAs).
•Requires RSP720, Sup720, or Sup32.
•If two subinterfaces have bandwidth remaining ratios that vary greatly (for example, 1000 to 1), you must configure a low queue limit (between 2 and 50) for the child default class of the subinterface with the lower ratio. Without a low queue limit, the packets that are buffered due to the default queue-limit value are allowed to pass after traffic is stopped, which affects bandwidth remaining ratios significantly. Configuring a low queue limit ensures that the ratios are maintained even after the traffic is stopped.
Note We recommend that you use BRR with priority-rate propagation. See the "Priority-Rate Propagation Recommendations" section for more information.
BRR Configuration Instructions
Following is a summary of the steps required to configure configure a QoS policy that defines BRR for a subscriber (access) interface on the Cisco 7600 SIP-400. The following table provides detailed instructions.
Note The command lines include only those arguments and keywords required to configure BRR.
1. enable
2. configure terminal
3. qos scheduler priority-rate-propagation platform sip-400 (optional but recommended)
4. policy-map child-policy-name
5. class class-map-name
6. priority level level (optional but recommended)
7. police bps
8. exit
9. exit
10. policy-map parent-policy-name
11. class class-default
12. bandwidth remaining ratio ratio
13. shape average cir [bc] [be]
14. service-policy child-policy-name
15. exit
16. exit
17. interface type slot/module/port.subinterface access
18. service-policy output parent-policy-name
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
•Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
qos scheduler priority-rate-propagation
platform sip-400
Example:
Router(config)# qos scheduler
priority-rate-propagation platform sip-400
|
Enables the priority-rate propagation feature on the Cisco 7600 SIP-400. This feature applies a priority level and traffic rate for priority traffic to all higher-level queues in the queue hierarchy, even if the queues are not specifically configured for minimum rates or priority.
Note This step is optional; however, if you are using BRR, we recommend that you perform this step.
|
Step 4
|
policy-map child-policy-name
Example:
Router(config)# policy-map child
|
Creates or modifies a child policy map and enters policy-map configuration mode.
•child-policy-name is the name of the child policy map.
|
Step 5
|
class class-map-name
Example:
Router(config-pmap)# class precedence_0
|
Configures the class map that you specify. Enters policy-map class configuration mode.
•class-map-name is the name of a previously created class map.
|
Step 6
|
priority level level
Example:
Router(config-pmap-c)# priority level 1
|
Assigns a priority level to this traffic class.
•level is the priority level to assign. Valid values are: 1 (high) and 2 (low).
Note Do not specify the same priority level for two different classes in the same policy map.
|
Step 7
|
police bps
Example:
Router(config-pmap-c)# police 200000000
|
(Optional) Specifies the rate at which to police traffic belonging to this traffic class.
•bps specifies the average rate in bits per second (bps). Valid values are from 8,000 to 2,488,320,000 bps.
|
Step 8
|
exit
|
Exits policy-map class configuration mode.
|
Step 9
|
exit
|
Exits policy-map configuration mode.
|
Step 10
|
policy-map parent-policy-name
Example:
Router(config)# policy-map Parent
|
Creates or modifies a parent policy map. Enters policy-map configuration mode.
•parent-policy-name is the name of the parent policy map.
|
Step 11
|
class class-default
Example:
Router(config-pmap)# class class-default
|
Configures the class-default class. Enters policy-map class configuration mode.
Note The router interprets any features configured under the class-default class as aggregate features on the subinterface.
|
Step 12
|
bandwidth remaining ratio ratio
Example:
Router(config-pmap-c)# bandwidth remaining
ratio 10
|
Specifies the bandwidth-remaining ratio for the subinterface. The scheduler allocates the excess bandwidth relative to other subinterfaces.
•ratio is the value that is used to determine the amount of unused bandwidth to allocate to each queue on the subinterface during periods of congestion. Valid values are 1 to 1000. The default and minimum values are 1.
Note The CLI supports a ratio value of 1 to 65535 but you cannot apply a policy with a BRR value above 1000 to a Cisco 7600 SIP-400 interface.
|
Step 13
|
shape average cir [bc] [be]
Example:
Router(config-pmap-c)# shape average 100000000
|
(Optional) Shapes the average rate to the rate you specify.
•average specifies average rate shaping.
•cir specifies the committed information rate (CIR), in bits per second (bps).
•(Optional) bc specifies the committed burst size, in bits.
•(Optional) be specifies the excess burst size, in bits.
|
Step 14
|
service-policy child-policy-name
Example:
Router(config-pmap-c)# service-policy child
|
Applies the specified child policy map to the default traffic class of the parent policy. The router applies the QoS actions specified in the child policy to the traffic class.
•child-policy-name is the name of the child policy.
Note Do not include input or output keyword when applying a child policy to a parent policy.
Note On a subinterface, the child policy can be applied only to the parent's default traffic class.
|
Step 15
|
exit
|
Exits policy-map class configuration mode.
|
Step 16
|
exit
|
Exits policy-map configuration mode.
|
Step 17
|
interface type slot/module/port.subinterface
access
Example:
Router(config)# interface GigabitEthernet
1/0/0.1 access
|
Creates or modifies the access subinterface you specify. Enters subinterface configuration mode.
•type is the interface type (for example, Gigabit Ethernet).
•slot/module/port.subinterface identifies the subinterface (for example, 1/0/0.1).
•access identifies this as an IP subscriber interface.
|
Step 18
|
service-policy output parent-policy-name
Example:
Router(config-subif)# service-policy output
parent
|
Applies the parent policy to the subinterface.
•output applies the service policy to outbound traffic.
•parent-policy-name is the name of the parent policy.
Note A policy map with BRR can be used only in the egress direction.
The router shapes the subinterface traffic to the shaping rate specified in the parent class-default class and applies the QoS actions specified in the child policy to traffic matching the traffic classes.
During periods of congestion, the router uses the bandwidth-remaining ratio specified in the parent policy map to allocate unused bandwidth on this subinterface relative to other subinterfaces.
|
Priority-Rate Propagation Recommendations
Priority-rate propagation applies (propagates) a priority level and traffic rate from a lower-level queue to all of the upper-layer queues in the queue hierarchy, even if the upper-layer queues are not specifically configured for minimum rates or priority. For example, if you configure a priority level and traffic rate for a traffic class (such as video) in a child policy, you can use priority-rate propagation to apply that rate to video traffic at all queue levels (parent queue, subinterface queue, and interface queue).
Dual-priority queues enable you to define two classes of high-priority traffic in a single policy map. You can also use the priority level command to assign a priority (high or low) to each priority queue. The priority level command specifies that a class of traffic has latency requirements with respect to other classes. Currently, the router supports two priority levels: level 1 (high) and level 2 (low). The router places traffic with a high priority level on the outbound link ahead of traffic with a low priority level. High priority packets, therefore, are not delayed behind low priority packets.
The router associates a single priority queue with each priority level and services the high level priority queues until empty before servicing the next level priority queues and non-priority queues. While the router services a queue, the service rate is as fast as possible and is constrained only by the rate of the underlying link or parent node in a hierarchy. If a rate is configured and the router determines that a traffic stream has exceeded the configured rate, the router drops the exceeding packets during periods of congestion. If the link is currently not congested, the router places the exceeding packets onto the outbound link.
If bandwidth remaining ratio (BRR) has also been configured, the router services priority traffic first. After servicing the priority traffic bandwidth, the router allocates unused bandwidth to the logical queues based on the configured bandwidth-remaining ratio. In this default case, the three-level scheduler allocates an equal share of the unused bandwidth to each logical queue.
If high priority traffic is not policed appropriately, bandwidth starvation of low priority traffic can occur. Therefore, though not required, we recommend that you use the police command to configure a policer for high priority traffic. If you configure the police command for priority queues, the traffic rate is policed to the police rate for each of the priority queues.
Priority-Rate Propagation Configuration Guidelines
As you configure priority-rate propagation for use with BRR, consider the following guidelines:
•Use the [no] qos scheduler priority-rate-propagation platform sip400 command in global configuration mode to enable and disable the priority-rate propagation feature.
•The [no] qos scheduler priority-rate-propagation platform sip400 command has no effect on QoS policies that are already attached to interfaces. Therefore, we recommend that you issue the command before attaching QoS policies.
Note If you issue the [no] qos scheduler priority-rate-propagation platform sip400 command after attaching QoS policies to Cisco 7600 SIP-400 interfaces, you must save the configuration and reload the router for the command to take effect.
•Priority-rate propagation and BRR work together as follows:
–When priority-rate propagation is enabled, the router services the priority bandwidth for all subinterface policies. The remaining bandwidth is then distributed according to the bandwidth remaining ratios. In this scenario, the priority rate was propagated from the child level to the interface queue.
–When priority-rate propagation is disabled, the aggregate subinterface bandwidth (priority and best effort) is shared according to the bandwidth remaining ratios. In this scenario, the priority bandwidth is not propagated from the child queue to the interface queue.
Priority-Rate Propagation and BRR Configuration Example
Here is an example of a priority level (2) being assigned to video traffic in a child policy map and used with BRR, which is configured in the parent policy map:
bandwidth remaining ratio 1
Unsupported IP Subscriber Session Features
Due to the way that internal VLANs are allocated for sharing among IP subscribers, the following features are not available for individual subscribers:
•Policy-based routing (PBR), Network Address Translation (NAT), or unicast Reverse Path Forwarding (uRPF)
•IPv4 and IPv6 multicast
•Encoded address resolution logic (EARL) features, such as reflexive ACL, Generic Route Encapsulation (GRE) tunneling, Context-Based Access Control (CBAC), and server load balancing (SLB)
IP Subscriber Awareness over Ethernet Configuration Guidelines
Note The IP Subscriber Awareness over Ethernet feature is not available in the IP services software image (xxx-ipservices_wan-mz). Although the image shows the access keyword as being available for the interface command, the subscriber awareness functionality is not available.
Observe the following guidelines and limitations as you configure IP Subscriber Awareness over Ethernet on Cisco 7600 routers:
•Software and hardware requirements:
•Cisco IOS Release 12.2SRB or later
•RSP720 with PFC3C or PFC3CXL (other supervisor engines are not supported)
•Cisco 7600 SIP-400 and 5-Port Gigabit Ethernet SPA (SPA-5X1GE-V2)
•Oversubscription is supported only on the 5-Port Gigabit Ethernet SPA.
•A maximum of 32000 interfaces are supported on the router. To support 32000 interfaces:
–The RSP720 must have 2 GB of RP memory and 1 GB of SP memory.
–The Cisco 7600 SIP-400 must have 1 GB of memory.
•The Cisco 7600 SIP-400 supports a maximum of 8000 IP subscribers.
•The 5-Port Gigabit Ethernet SPA (SPA-5X1GE-V2) supports up to 8000 VLANs.
•The access subinterface that represents an IP subscriber must be configured for .1Q or Q-in-Q encapsulation.
•The MTU of the access subinterface is 1500 and this value cannot be changed.
•You can convert a regular GE subinterface to an access interface, but you cannot convert an access interface to a regular GE subinterface. Instead, you must delete the access subinterface.
•EARL-based features are not supported. This includes Network Address Translation (NAT), Reflexive ACL, Generic Route Encapsulation (GRE) tunneling, Context-Based Access Control (CBAC), and server load balancing (SLB).
•We recommend that you do not configure Hot Standby Routing Protocol (HSRP) for link redundancy.
•See the "QoS Recommendations" section for QoS guidelines.
Interaction with Other Features
The following list describes the interaction between IP Subscriber Awareness over Ethernet and other features that are configured on the router:
•Multicast traffic is not affected by the feature. The router can participate in IGMP functions and replication without being affected by IP Subscriber Awareness over Ethernet. In addition, the router supports multicast traffic without the authentication of data service. This allows basic video service to be provided without data service.
The DSLAM (not the router) is responsible for replicating multicast traffic and delivering it to IP subscribers. Therefore, it is not necessary for the IP Subscriber Awareness over Ethernet feature to support multicast traffic on IP subscriber interfaces (access interfaces).
Configuring IP Subscriber Awareness over Ethernet
The following sections provide information about configuring the IP Subscriber Awareness over Ethernet feature on a Cisco 7600 series router:
•Configuration Summary
•Configuration Examples
Configuration Summary
Following is a summary of the steps required to configure IP Subscriber Awareness over Ethernet on Cisco 7600 routers. Detailed configuration instructions are provided in the next section.
Before Starting
•Determine which VPN routing and forwarding (VRF) table each IP subscriber should be part of. All of the subscribers in a VRF share a single internal VLAN for data services. Use the ip vrf and rd commands to create each of the VRF tables that you need.
To use the same VRF, subscribers must all belong to the same network service provider (NSP), Internet service provider (ISP), or access service provider (ASP). If you do not assign a subscriber to a VRF, the subscriber is added to the default VRF, which the router creates during system bootup.
•Make sure that the router is configured as a DHCP server or a DHCP relay device in order to allow IP addresses to be dynamically assigned for IP subscriber sessions. Otherwise, you would have to assign a static IP address to each IP subscriber access subinterface (which is not recommended).
For information about configuring DHCP, see "Configuring DHCP" in the Cisco IOS IP Configuration Guide at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr_c/ipcprt1/1cfdhcp.htm
•Determine which physical interfaces are used by IP subscribers. For each IP subscriber, you configure an access subinterface on the physical interface that the subscriber is connected to.
Configure QoS and HQoS Policies for IP Subscribers
•Define QoS policies (class maps and policy maps) to define traffic bandwidth and shaping policies for subscriber traffic. You can use a hierarchical QoS (HQoS) policy to shape traffic at different levels. For example, the parent policy could define the total bandwidth for the subscriber, and the child policy could define the bandwidth for different types of subscriber traffic (such as video). On a subinterface, the child policy can be attached only at the default class of the parent.
•(Optional) You can create dual-priority queues to handle the subscriber's voice and video traffic.
•You can also define a class-based weighted fair queue (CBWFQ) or priority queue (PQ) for different types of subscriber traffic.
Configure Access Lists and Security ACLs
•Determine the security policies that are needed for IP subscribers. Create access lists and security ACLs to define these policies.
Here is an example of two access lists (2 and 3) that will be applied to IP subscribers:
access-list 2 permit 18.18.18.18
access-list 3 permit 23.23.23.23
access-list 101 deny ip 44.1.1.0 0.0.0.255 any
access-list 101 permit icmp any any
The following example configures an input and output security ACL for the IP subscriber session that is represented by the access subinterface gig0/1/1.100:
interface gig0/1/1.100 access
ip address 10.10.10.1 255.255.255.0
Configure IP Subscriber Interfaces
•Create an access interface for each IP subscriber. Create the access interface as a subinterface of the subscriber's physical interface. For example, if the subscriber is connected to Gig1/0/0, you could configure the access interface as Gig1/0/0.100.
•Configure the access interface as follows:
–If necessary, assign an IP address to the interface (this is a static IP address). We recommend that you do not configure many access interfaces with a static IP address. Instead, you should allow DHCP to dynamically assign IP addresses for IP subscriber sessions.
–If the IP subscriber belongs to a particular VRF table, include the ip vrf forwarding vrf-name command in the configuration to associate the interface with the table. If you do not specify a VRF table, the subscriber is added to the default VRF.
–Set the encapsulation type (.1Q or Q-in-Q) and specify which VLAN the interface is part of.
–Attach QoS policies to the interface to define traffic bandwidth and shaping policies for the subscriber traffic.
This example shows two IP subscriber access interfaces (gig1/0/0.100 and gig1/0/0.300). Since the subscribers connect through Gig1/0/0, the access interfaces are created as subinterfaces of Gig1/0/0. Notice that gig1/0/0.100 is assigned a static IP address and gig1/0/0.300 uses DHCP to obtain an IP address. In addition, notice that gig1/0/0.300 is VRF aware.
interface gig1/0/0.100 access
ip address 10.10.10.10 255.255.255.255
service-policy input bband-in1
service-policy output bband-out1
interface gig1/0/0.300 access
service-policy input bband-in1
service-policy output bband-out1
Verify the IP Subscriber Awareness over Ethernet Feature
Use the following commands to verify the status of each access interface that represents an IP subscriber. An access subinterface should exist for each subscriber and the interfaces should be in the Up state.
•Issue the show running-config interface interface.subinterface command to verify the configuration of each access subinterface (where interface is the physical interface and .subinterface is the access subinterface). For example, show running-config interface Gig1/0/2.1 displays the access subinterface (.1) that exists on the physical interface Gig1/0/2.
Configuration Examples
The following example shows a configuration with three subscribers (Gig3/2/0.10, Gig3/2/0.11, and Gig3/2/0.12), each receiving a different type of service: gold (30 Mbps), silver (15 Mbps), and bronze (5 Mbps). Each subscriber has per-subscriber accounting and per-subscriber ACL configured.
The QoS policy maps are configured so that video traffic is never dropped, and default traffic is shared in the ratio of 30:15:5 (which results in a bandwidth remaining ratio of 6:3:1).
aaa accounting network defaul start group radius
radius-server host 2.2.2.2
ip address 13.0.7.254 255.255.248.0
network 13.0.0.0 255.255.248.0
policy-map data_gold_child_out
policy-map data_gold_parent_out
bandwidth remaining ratio 6
service-policy data_gold_child_out
policy-map data_silver_child_out
policy-map data_silver_parent_out
bandwidth remaining ratio 3
service-policy data_silver_child_out
policy-map data_bronze_child_out
access-list 102 permit ip any any precedence 5
access-list 102 permit ip any any precedence 2
access-list 102 permit ip any any precedence 0
policy-map data_bronze_parent_out
bandwidth remaining ratio 1
service-policy data_bronze_child_out
policy-map data_silver_in
policy-map data_bronze_in
interface gig 3/2/0.10 access
service-policy output data_gold_parent_out
service-policy input data_gold_in
accounting dhcp source-ip aaa list default
interface gig 3/2/0.11 access
service-policy output data_silver_parent_out
service-policy input data_silver_in
accounting dhcp source-ip aaa list default
interface gig 3/2/0.12 access
service-policy output data_bronze_parent_out
service-policy input data_bronze_in
accounting dhcp source-ip aaa list default
Command Reference
This section describes the new commands for IP Subscriber Awareness over Ethernet. The following new command is being introduced as part of this feature:
•interface access
interface access
To create an access interface for an IP subscriber, use the interface access command in global configuration mode. Use the no form of the command to delete an IP subscriber access interface.
interface interface.subinterface access
no interface interface.subinterface access
Syntax Description
interface
|
Identifies the physical interface that this IP subscriber is connected to.
|
.subinterface
|
A subinterface number to assign to the access interface.
|
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.2(33)SRB
|
This command was introduced.
|
Usage Guidelines
This command creates an access interface for an IP subscriber. Create the access interface as a subinterface of the physical interface that the subscriber is connected to. For example, if the subscriber is connected to Gig1/0/0, you could configure the access interface as Gig1/0/0.1, Gig1/0/0.2, Gig1/0/0.3, and so on.
Include the ip vrf forwarding vrf-name command in the configuration to associate the IP subscriber with the specified VRF table. If you do not specify a VRF table, the subscriber is added to the default VRF table (which is created during router bootup).
Examples
The following command example creates an access interface for an IP subscriber and assigns the subscriber to the VRF table named vrf1. The access interface is created as subinterface .300 on the physical interface Gig2/0/1. You would issue additional commands to complete the configuration (for example, to specify encapsulation type, and to assign QoS policies).
Router(config)# interface Gig2/0/1.300 access
Router(config-if)# ip vrf forwarding vrf1
