Technical Documentation



(aggregate | no-aggregate);

Hierarchy Level

[edit logical-systems logical-system-name protocols rsvp interface interface-name],[edit logical-systems logical-system-name protocols rsvp peer-interface peer-interface-name],[edit protocols rsvp interface interface-name],[edit protocols rsvp peer-interface peer-interface-name]

Release Information

Statement introduced before JUNOS Release 7.4.


Control the use of RSVP aggregate messages on an interface or peer interface:

  • 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.


Aggregation is disabled.

Required Privilege Level

routing—To view this statement in the configuration.

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

Published: 2010-04-28