RSVP is covered in the CCIE R&S Exam guide, but I have not heard of this protocol being used in production environments (although I'm sure it is in use). Given that it uses an Intergrated Services model where the protocol reserves bandwidth before a call is made, it's not as common as "per hop behavior" or DiffServ QoS treatment of traffic. The bandwidth reservation happens separately in both directions, so that one reservation is for source to destination traffic and a second one is for the opposite (destination to source).
While some devices might be capable of issuing RSVP reservation requests, the expected behavior is that a gateway device will issue the request for the end user device. The RSVP protocol uses PATH and RESV messages to request and reply to reservations, respectively. Upon receipt of a RESVCONF message, the gateway devices will allow the call (or other traffic) to proceed.
Configuring RSVP
After you decide on the amount of bandwidth to be reserved per call or per flow and the total amount of RSVP allocated bandwidth per interface, you'll need to configure each router that will run RSVP. Because you must take into consideration the interface bandwidth and configuration on each interface of each configured router, you can tell this will be a non-trivial task. It also doesn't scale well, which explains why RSVP and the Integrated Services model haven't been widely adopted.
Relevant Cisco commands are:
router(config-if)# ip rsvp bandwidth TOTAL-KBPS SINGLE-FLOW-KBPS
By default, RSVP will reserve 75% of the interface bandwidth (unless you configure this command). Also, any single flow can reserve the entire amount of bandwidth unless you specify otherwise with this command.
router(config-if)# ip rsvp signaling dscp DSCP-VALUE
This command sets the DSCP value for RSVP control messages.
While some devices might be capable of issuing RSVP reservation requests, the expected behavior is that a gateway device will issue the request for the end user device. The RSVP protocol uses PATH and RESV messages to request and reply to reservations, respectively. Upon receipt of a RESVCONF message, the gateway devices will allow the call (or other traffic) to proceed.
Configuring RSVP
After you decide on the amount of bandwidth to be reserved per call or per flow and the total amount of RSVP allocated bandwidth per interface, you'll need to configure each router that will run RSVP. Because you must take into consideration the interface bandwidth and configuration on each interface of each configured router, you can tell this will be a non-trivial task. It also doesn't scale well, which explains why RSVP and the Integrated Services model haven't been widely adopted.
Relevant Cisco commands are:
router(config-if)# ip rsvp bandwidth TOTAL-KBPS SINGLE-FLOW-KBPS
By default, RSVP will reserve 75% of the interface bandwidth (unless you configure this command). Also, any single flow can reserve the entire amount of bandwidth unless you specify otherwise with this command.
router(config-if)# ip rsvp signaling dscp DSCP-VALUE
This command sets the DSCP value for RSVP control messages.
Adao used to be very distressed to hear his acquaintances speaking in any such method due to the fact that he revered the forest and did not want to decrease more trees than had been needed. free online movies
ReplyDeleteBut his buddies have been not to be dissuaded and so they accumulated their savings and bought a big tractor and extra reducing apparatus.
Her tooth were white as snow and of an evenness to wonder at. Her lips had been thin and Download Videos Tips fantastically curved: purple lips in fact, crimson as iciness berries and tempting because the fruits of summer time.
ReplyDelete