Bandwidth Subscription Troubleshooting

Be aware of the following issues when configuring bandwidth subscription:

If you configure the subscription statement at the [edit protocols rsvp interface all] hierarchy level, and then configure a different value at the [edit protocols rsvp interface interface-name] hierarchy level, the value configured at the [edit protocols rsvp interface interface-name] hierarchy level overrides the other value.
Per-class-type subscription can only be configured if a bandwidth model is also configured. If no bandwidth model is configured, the configuration fails with the following error message:
user@host# commit check
```
[edit protocols rsvp interface all]
  'subscription'
RSVP: Must have a diffserv-te bandwidth model configured when configuring subscription per traffic class.
error: configuration check-out failed
```
If you configure the subscription statement for a specific class type, you cannot configure the subscription statement for the whole interface. The configuration commit operation fails with the following error message:
user@host# commit check
```
[edit protocols rsvp interface all]
  'subscription'
    RSVP: Cannot configure both link subscription and per traffic class subscription.
error: configuration check-out failed
```