 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
You can configure RSVP refresh reduction on each interface. The following statements allow you to configure the RSVP refresh reduction features:
For more information on RSVP refresh reduction, see RSVP Refresh Reduction.
Table 10 lists various combinations of the RSVP refresh reduction configuration statements and how they alter the behavior of the JUNOS software. The table describes only the expected behavior based on the configuration on the router. The actual behavior is dictated not only by the local configuration on this router, but also on the refresh reduction capabilities of its RSVP neighbors. Note that by configuring the aggregate statement, you enable all RSVP refresh reduction features, including reliable message delivery.
Table 10: RSVP Refresh Reduction Behavior
The send capability shown in Table 10 lists the RSVP messages and objects related to RSVP refresh reduction that the router is capable of sending. This does not mean that all these messages are exchanged between this router and a neighbor. For example, if the router is configured with the aggregate statement, but RSVP refresh reduction is not enabled on its neighbor, then no Summary Refresh message is sent to this neighbor even though the router is capable of sending it.
The receive capability shown in Table 10 lists the messages and objects related to RSVP refresh reduction that the router is capable of receiving and processing without generating any errors or resulting in error conditions.
If the no-reliable statement is configured on the router (reliable message delivery is disabled), the router accepts RSVP messages that include the Message ID object but ignore the Message ID object and continue performing standard message processing. No error is generated in this case, and RSVP operates normally.
However, not all combinations between two neighbors with different refresh reduction capabilities function correctly. For example, a router is configured with either the aggregate statement and no-reliable statement or with the reliable and no-aggregate statements. If an RSVP neighbor sends a Summary Refresh object to this router, no error is generated, but the Summary Refresh object cannot be processed. Consequently, RSVP states can time out on this router if the neighbor is relying only on Summary Refresh to refresh those RSVP states.
We recommend, unless there are specific requirements, that you configure RSVP refresh reduction in a similar manner on each RSVP neighbor.
To enable all RSVP refresh reduction features on an interface, include the aggregate statement:
-
aggregate;
You can include this statement at the following hierarchy levels:
To disable RSVP message bundling and summary refresh, include the no-aggregate statement:
-
no-aggregate;
You can include this statement at the following hierarchy levels:
To enable RSVP message ID and reliable message delivery on an interface, include the reliable statement:
-
reliable;
You can include this statement at the following hierarchy levels:
To disable RSVP message ID, reliable message delivery, and summary refresh, include the no-reliable statement:
-
no-reliable;
You can include this statement at the following hierarchy levels:
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |