If RADIUS is configured to provide traffic parameters for PVCs, a more recent, explicitly specified change in the VC class associated with that PVC overrides the PVC values applied through RADIUS.
In the following example, assume that RADIUS has been configured to apply a service category of CBR with a PCR of 400 Kbps to the PVC. Initially, the PVC uses the service category configured in my-premium-class, CBR with a PCR of 200 Kbps. However, when the subscriber logs in through RADIUS, the router applies the RADIUS-configured service category, CBR with a PCR of 400 Kbps.
While the subscriber is still logged in, my-premium-class is modified to change the service category to CBR with a PCR of 600 Kbps. Because this VC class modification results in the most recent, explicitly specified value for the service category, the router now uses CBR with a PCR of 600 Kbps as the service category for the PVC instead of the service category configured through RADIUS.
- host1(config)#interface atm 2/0.200
- host1(config-subif)#pvc 200 0/200
- host1(config-subif-vc)#class-vc my-premium-class
- host1(config-subif-vc)#exit
- ! Subscriber logs in through RADIUS, which applies service
category of CBR
- ! with a PCR of 400 Kbps to PVC.
- host1(config)#vc-class atm my-premium-class
- host1(config-vc-class)#cbr 600
- host1(config-vc-class)#exit
- ! Router now applies service category of CBR with a PCR
of 600 Kbps to PVC.