- Configuring ATM
- ATM Conditional Debug Support
- ATM OAM Ping
- ATM OAM Traffic Reduction
- Local Template-Based ATM PVC Provisioning
- ATM PVC Range
- ATM SNMP Trap and OAM Enhancements
- ATM PVC F5 OAM Recovery Traps
- ATM VP Average Traffic Rate
- ATM Hierarchical Shaping�ATM VC into VP Shaping
- Autosense of MUX/SNAP Encapsulation and PPPoA/PPPoE on ATM PVCs
ATM Hierarchical Shaping—ATM VC into VP Shaping
Traffic shaping is a quality of service (QoS) mechanism that is used to manage the network traffic by shaping the traffic to a specified rate. Traffic shaping enables the network administrator to:
•
Control access to the available bandwidth.
•
Ensure that the traffic conforms to the policies.
•
Regulate the flow of traffic to avoid congestion that can occur when the transmitted traffic exceeds the access speed of its remote target interface.
Traffic shaping uses queues to constrain data bursts, limit peak data rate, and smooth jitters so that traffic will fit within the promised envelope. Traffic shaping limits the throughput by buffering excess traffic instead of dropping packets.
ATM VP/VC hierarchical shaping provides two levels of traffic shaping—per-VC and per-VP—to control or modify the flow of traffic on an interface. The shaping function also ensures that the traffic from one VC does not adversely impact another VC, thus preventing the loss of data. The traffic is shaped first at the VC level and then at the VP level.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for ATM Hierarchical Shaping" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Restrictions for ATM Hierarchical Shaping
•
Information About ATM Hierarchical Shaping
•
How to Configure ATM Hierarchical Shaping
•
Configuration Examples for ATM Hierarchical Shaping
•
Feature Information for ATM Hierarchical Shaping
Restrictions for ATM Hierarchical Shaping
All virtual channels (VCs) within a given virtual path (VP) must belong to the same ATM service category.
Information About ATM Hierarchical Shaping
ATM Hierarchical Shaping
If a service (or an application) wants to use an ATM network to transport a particular kind of traffic, it must first inform the network about what kind of traffic is to be transported, and the performance requirements of that traffic. The ATM service categories provide a method to relate traffic characteristics and QoS requirements to network behavior. Hierarchical shaping requires that all VCs belonging to a given VP have the same ATM service category. This hierarchy ensures that packets are shaped first at the VC level and then at the VP level. At the interface level, the priority is based on the ATM service category. The service category is determined by the first PVC that is configured under a VP. The priority is in the following order:
1.
Constant Bit Rate (CBR)
2.
Unspecified Bit Rate (UBR)
3.
Variable Bit Rate Non Real-Time (VBR-nRT)
4.
Real-time Variable Bit Rate (VBR-RT)
If no service category is specified at the VC level, the default is unshaped UBR. The ATM Hierarchical Shaping feature is supported for the following ATM traffic service categories:
•
VBR-nRT
•
UBR
For VBR-nRT traffic the output sustainable cell rate (SCR) value that is configured will be taken into account for VC shaping. For UBR traffic, the output peak cell rate (PCR) value that is configured will be taken into account for VC shaping.
The ATM Hierarchical Shaping feature supports over-subscription. Over-subscription occurs when the sum of the configured rate of UBR and VBR PVCs exceeds the line rate.
How to Configure ATM Hierarchical Shaping
•
Configuring ATM Hierarchical Shaping (required)
Configuring ATM Hierarchical Shaping
Perform this task to configure ATM hierarchical shaping.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface atm interface-number [.subinterface-number {mpls | multipoint | point-to-point}]
4.
atm pvp vpi [peak-rate]
5.
pvc vpi/vci
6.
exit
7.
range [range-name] pvc [start-vpi/]start-vci [end-vpi/]end-vci
8.
ubr output-pcr
9.
exit
10.
atm pvp vpi [peak-rate]
11.
pvc vpi/vci
12.
vbr-nrt output-pcr output-scr [output-maxburstsize]
13.
create on-demand
14.
end
15.
show atm pvc
16.
show atm vp
DETAILED STEPS
Configuration Examples for ATM Hierarchical Shaping
•
Example: Configuring ATM Hierarchical Shaping
Example: Configuring ATM Hierarchical Shaping
The following example shows how to configure ATM hierarchical shaping:
enable
configure terminal
interface atm 0/3/2.1 multipoint
atm pvp 2
pvc 2/200
exit
range range1 pvc 2/100 2/102
ubr 4000
exit
atm pvp 3
pvc 3/100
vbr-nrt 1000 1000
create on-demand
end
Additional References
Related Documents
|
|
|
|---|---|
Cisco IOS commands |
|
ATM commands |
Standards
|
|
|
|---|---|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
MIBs
RFCs
|
|
|
|---|---|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature. |
— |
Technical Assistance
Feature Information for ATM Hierarchical Shaping
Table 1 lists the release history for this feature.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Feedback