CorpHQ# Feb 16 23:00:41.997: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: Received Path message from 127.0.0.1 (on sender host) Feb 16 23:00:41.997: RSVP: new path message passed parsing, continue... Feb 16 23:00:41.997: RSVP: Triggering outgoing Path due to incoming Path change or new Path Feb 16 23:00:41.997: RSVP: Triggering outgoing Path refresh Feb 16 23:00:42.001: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: Path refresh, Event: rmsg not enabled or ack rcvd, State: trigger to normal Feb 16 23:00:42.001: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: Path refresh (msec), config: 30000 curr: 30000 xmit: 30000 Feb 16 23:00:42.001: RSVP: Triggering outgoing Path due to incoming Path change or new Path Feb 16 23:00:42.001: RSVP: Triggering outgoing Path refresh Feb 16 23:00:42.001: RSVP: session 172.21.254.1_19352[0.0.0.0]: Received Resv message from 127.0.0.1 (on receiver host) Feb 16 23:00:42.005: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Successfully parsed Resv message from 127.0.0.1 (on receiver host) Feb 16 23:00:42.005: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: this RESV has a confirm object Feb 16 23:00:42.005: RSVP-MSG: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: no matching path state for Resv Feb 16 23:00:42.005: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: Path refresh, Event: rmsg not enabled or ack rcvd, State: trigger to normal Feb 16 23:00:42.005: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: Path refresh (msec), config: 30000 curr: 30000 xmit: 30000 Feb 16 23:00:42.005: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: Sending Path message to 172.21.254.3 Feb 16 23:00:42.025: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: building hop object with src addr: 172.20.201.1 Feb 16 23:00:42.037: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Received Path message from 172.20.201.2 (on Serial0/0/1:0.2) Feb 16 23:00:42.037: RSVP: new path message passed parsing, continue... Feb 16 23:00:42.041: RSVP: session 172.21.254.1_19352[0.0.0.0]: Received Resv message from 127.0.0.1 (on receiver host) Feb 16 23:00:42.041: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Successfully parsed Resv message from 127.0.0.1 (on receiver host) Feb 16 23:00:42.041: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: this RESV has a confirm object Feb 16 23:00:42.041: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: reservation not found--new one Feb 16 23:00:42.041: RSVP-RESV: Admitting new reservation: 4B1BA500 Feb 16 23:00:42.041: RSVP-RESV: Locally created reservation. No admission/traffic control needed Feb 16 23:00:42.041: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: start requesting 40 kbps FF reservation on Serial0/0/1:0.2, neighbor 172.20.201.2 Feb 16 23:00:42.045: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: start requesting 40 kbps FF reservation on Serial0/0/1:0.2, neighbor 172.20.201.2 Feb 16 23:00:42.049: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Refresh RESV, req=4B1BF5A8 [cleanup timer is not awake] Feb 16 23:00:42.049: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Resv refresh, Event: rmsg not enabled or ack rcvd, State: trigger to normal Feb 16 23:00:42.049: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Resv refresh (msec), config: 30000 curr: 30000 xmit: 30000 Feb 16 23:00:42.049: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: building Resv_Conf object with receiver addr: 172.20.201.1 Feb 16 23:00:42.049: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Sending Resv message to 172.20.201.2 Feb 16 23:00:42.061: RSVP: session 172.21.254.3_16672[0.0.0.0]: Received Resv message from 172.20.201.2 (on Serial0/0/1:0.2) Feb 16 23:00:42.061: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: Successfully parsed Resv message from 172.20.201.2 (on Serial0/0/1:0.2) Feb 16 23:00:42.061: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: this RESV has a confirm object Feb 16 23:00:42.061: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: reservation not found--new one Feb 16 23:00:42.061: RSVP-RESV: Admitting new reservation: 4B1BA398 Feb 16 23:00:42.061: RSVP-RESV: reservation was installed: 4B1BA398 Feb 16 23:00:42.065: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: building error_spec object with err-node addr: 172.20.201.1 Feb 16 23:00:42.069: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: building Resv_Conf object with receiver addr: 172.20.201.1 Feb 16 23:00:42.069: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: building hop object with src addr: 172.20.201.1 Feb 16 23:00:42.069: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: Sending ResvConf message to 172.20.201.2 Feb 16 23:00:42.097: RSVP-MSG: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Received ResvConf message from 172.20.201.2 (on Serial0/0/1:0.2) Feb 16 23:00:46.185: RSVP: session 172.21.254.1_19352[0.0.0.0]: Received Resv message from 127.0.0.1 (on receiver host) Feb 16 23:00:46.185: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Successfully parsed Resv message from 127.0.0.1 (on receiver host) Feb 16 23:00:46.185: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Resv changed: POLICY_DATA, FLOWSPEC, Feb 16 23:00:46.185: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: process_reservation_change: Resv change requires triggering of Resv upstream Feb 16 23:00:46.189: RSVP-RESV: accept_reservation_change: 4B1BA500 Feb 16 23:00:46.189: RSVP-RESV: Locally created reservation. No admission/traffic control needed Feb 16 23:00:46.189: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: start requesting 24 kbps FF reservation on Serial0/0/1:0.2, neighbor 172.20.201.2 Feb 16 23:00:46.193: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Refresh RESV, req=4B1BF5A8 [cleanup timer is not awake] Feb 16 23:00:46.193: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Resv refresh, Event: rmsg not enabled or ack rcvd, State: trigger to normal Feb 16 23:00:46.193: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Resv refresh (msec), config: 30000 curr: 30000 xmit: 30000 Feb 16 23:00:46.193: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: Sending Resv message to 172.20.201.2 Feb 16 23:00:46.213: RSVP: 172.21.254.3_16672->172.21.254.1_19352[0.0.0.0]: building hop object with src addr: 172.20.201.1 Feb 16 23:00:46.213: RSVP: session 172.21.254.3_16672[0.0.0.0]: Received Resv message from 172.20.201.2 (on Serial0/0/1:0.2) Feb 16 23:00:46.217: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: Successfully parsed Resv message from 172.20.201.2 (on Serial0/0/1:0.2) Feb 16 23:00:46.217: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: Resv changed: POLICY_DATA, FLOWSPEC, Feb 16 23:00:46.217: RSVP: 172.21.254.1_19352->172.21.254.3_16672[0.0.0.0]: process_reservation_change: Resv change requires triggering of Resv upstream Feb 16 23:00:46.217: RSVP-RESV: accept_reservation_change: 4B1BA398 Feb 16 23:00:46.217: RSVP-RESV: reservation was installed: 4B1BA398 CorpHQ#sh ip rsvp reservation To From Pro DPort Sport Next Hop I/F Fi Serv BPS 172.21.254.1 172.21.254.3 UDP 19352 16672 none none FF LOAD 24K 172.21.254.3 172.21.254.1 UDP 16672 19352 172.20.201.2 Se0/0/1: FF LOAD 24K