Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


aggregate (Protocols RSVP)


Hierarchy Level


Control the use of RSVP aggregate messages on an interface or peer interface, as described below.


Starting in Junos OS Release 15.2, the aggregate statement is deprecated at the [edit protocols rsvp interface interface-name] and [edit logical-systems logical-system-name protocols rsvp interface interface-name] hierarchy levels, as RSVP message aggregation is enabled by default.

  • aggregate—Use RSVP aggregate messages.

  • no-aggregate—Do not use RSVP aggregate messages.

    Aggregate messages can pack multiple RSVP messages into a single transmission, thereby reducing network overhead and enhancing efficiency. The number of supportable sessions and processing overhead are significantly improved when aggregation is enabled.

    Not all routers connected to a subnet need to support aggregation simultaneously. Each RSVP router negotiates its intention to use aggregate messages on a per-neighbor basis. Only when both routers agree are aggregate messages sent.

To have refresh reduction and reliable delivery, you must include the aggregate and reliable statements.


Aggregation is enabled.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced before Junos OS Release 7.4.