Simulation Attribute: RSVP
We have already mentioned that RSVP uses the concept of a “soft state”, and that all states are refreshed every “Refresh Interval” seconds. If the routes do not change during the course of simulation (i.e. no failure/recovery or load balancing is used in the system), and if there is no packet loss in the network, then it can be assumed that all Path and Reservation states will not change during the lifetime of a session unless they are deleted. In such a scenario, there is no need to send refresh messages. This decreases the simulation time and memory requirements, what is the purpose of the RSVP Simulation Efficiency attribute. If enabled, no refresh messages are sent, and no Path and Resv refreshes are scheduled. If disabled, refresh messages are generated as defined by RFC 2205.
Figure 461: RSVP Simulation Efficiency Configuration
