RSVP message pacing
Load mpls.te.base.config.with.ospf.cfg
On R8, configure RSVP message pacing so that 1000 messages are sent every second. Use a 100msec brust period. The max number of messages that can be queued should be 1500 messages.
On XR11, configure RSVP message pacing so that 1000 messages are sent every second. Use a 500msec burst period.
Answer
Explanation
RSVP message pacing can be very useful in networks where there are huge numbers of RSVP tunnels (perhaps in the 1000s). A link flap can result in tons of PathErr and ResvErr messages being generated all at once. By setting RSVP message pacing, we can have some control over this flood of RSVP messages.
On IOS-XE, we set RSVP message pacing using the ip rsvp signalling rate-limit command. This is set globally per-device. The burst is how many messages are sent in the burst period. The period defines the burst period in msec. The maxsize is how many messages can be held in queue.
On IOS-XR, it seems we can only set RSVP message pacing on a per-interface basis. We have less knobs to adjust on IOS-XR. We set the number of messages to send in the burst period using the rate parameter, and the interval to define the burst period in msec. Note that we have to enable rate-limiting in one command, plus change the rates in a separate command.
Verification
First notice that IOS-XE already has RSVP message pacing on by default. For example, we’ll look at R9. Nothing has been configured, but we can see RSVP rate-limits are already set:
We can use this command to verify our custom settings on R8:
On IOS-XR, RSVP message pacing is off by default. We can see this on XR12 by looking at the show rsvp interface detail output:
On XR11, we should see our custom rate-limit settings on every interface:
Last updated
