[Contents] [Prev] [Next] [Index] [Report an Error]

Configuring RSVP Refresh Reduction

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 5 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 5: RSVP Refresh Reduction Behavior
Configuration Statement
Send Capability
Receive Capability

aggregate or
aggregate and reliable

RR bit = 1
Bundle
Message ID (Path/Resv messages)
Ack/Nack (all messages)
Summary Refresh

Bundle
Ack/Nack (all messages)
Summary Refresh

aggregate and no-reliable

RR bit = 1
Bundle
Ack/Nack (all messages)

Bundle
Message ID (all messages)

reliable or
reliable and no-aggregate

RR bit = 0
Message ID (Path/Resv messages)
Ack/Nack (all messages)

Bundle
Message ID (all messages)
Ack/Nack

The send capability shown in Table 5 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 5 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 and no-reliable statements 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, to 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:

Determining the Refresh Reduction Capability of RSVP Neighbors

To determine the RSVP refresh reduction capability of an RSVP neighbor, you need the following information:

To obtain this information, you can issue a show rsvp neighbor detail command. The following is a sample of output from this command:

user@host> show rsvp neighbor detail

RSVP neighbor: 6 learned

    Address: 192.168.224.178 via: fxp1.0 status: Up

      Last changed time: 10:06, Idle: 5 sec, Up cnt: 1, Down cnt: 0

      Message received: 36

      Hello: sent 69, received: 69, interval: 9 sec

      Remote instance: 0x60b8feba, Local instance: 0x74bc7a8d

      Refresh reduction:  not operational

    

    Address: 192.168.224.186 via: fxp2.0 status: Down

      Last changed time: 10:17, Idle: 40 sec, Up cnt: 0, Down cnt: 0

      Message received: 6

      Hello: sent 20, received: 0, interval: 9 sec

      Remote instance: 0x0, Local instance: 0x2ae1b339

      Refresh reduction:  incomplete

        Remote end: disabled, Ack-extension: enabled

    

    Address: 192.168.224.188 via: fxp2.0 status: Up

      Last changed time: 4:15, Idle: 0 sec, Up cnt: 1, Down cnt: 0

      Message received: 55

      Hello: sent 47, received: 31, interval: 9 sec

      Remote instance: 0x6436a35b, Local instance: 0x663849f0

      Refresh reduction:  operational

        Remote end: enabled, Ack-extension: enabled

For more information on the show rsvp neighbor detail command, see the JUNOS Protocols, Class of Service, and System Basics Command Reference.

[Contents] [Prev] [Next] [Index] [Report an Error]