 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
Using VC classes to configure and assign attributes to ATM data PVCs provides the following benefits:
In a typical scenario, you might group subscribers based on their OAM and traffic requirements, and then create a VC class for each subscriber group. For example, you might create two VC classes: premium-subscriber-class and economy-subscriber-class.
In premium-subscriber-class, you might enable F5 OAM VC integrity (with the oam-pvc manage command), and configure a traffic class that has a higher scheduling priority, such as CBR (with the cbr command). Conversely, in economy-subscriber-class, you might retain the default setting that disables F5 OAM VC integrity, and configure a traffic class that has a lower scheduling priority, such as UBR with or without a PCR (with the ubr command). By assigning each VC class to the appropriate interfaces or individual circuits, you can group and manage the PVCs associated with the VC class based on the network requirements of the subscribers they serve.
If the OAM or traffic requirements change for a particular subscriber group, you can simply reconfigure the VC class associated with the PVCs for that subscriber group. This method is easier and less time-consuming than having to modify the attributes for a large number of PVCs by using individual CLI commands.
Modifications to the attributes in a VC class affect PVCs that are already associated with this VC class as well as PVCs subsequently created for this class.
| Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |