RSVP TE reservations are downstream...
In this example R1 is MPLS transit between R3 and R4. S2/1 is facing R3
therefore it holds 10M reserved for the tunnel R4-R3. Interface F0/0 is exit
to R4, therefore it has 10M for tunnel R3-R4.
Rack1R1# sh ip rsvp reservation
To From Pro DPort Sport Next Hop I/F Fi Serv
BPS
150.1.3.3 150.1.4.4 0 1 39 150.1.13.3 Se2/1 SE LOAD
10M
150.1.4.4 150.1.3.3 0 1 29 150.1.12.2 Fa0/0 SE LOAD
10M
Rack1R1# sh ip rsvp interface
interface allocated i/f max flow max sub max
Fa0/0 10M 100M 100M 0
Se2/1 10M 155M 155M 0
Rack1R1#sh mpls traffic-eng link-management bandwidth-allocation
System Information::
Links Count: 2
Bandwidth Hold Time: max. 15 seconds
Link ID:: Fa0/0 (150.1.12.1)
Local Intfc ID: 5
Link Status:
Intfc Switching Capability Descriptors:
Default: Intfc Switching Cap psc1, Encoding ethernet
Link Label Type: Packet
Physical Bandwidth: 100000 kbits/sec
Max Res Global BW: 100000 kbits/sec (reserved: 10% in, 10% out)
Max Res Sub BW: 0 kbits/sec (reserved: 100% in, 100% out)
BW Descriptors: 1
MPLS TE Link State: MPLS TE on, RSVP on, admin-up, flooded,
allocated
Inbound Admission: reject-huge
Outbound Admission: allow-if-room
Admin. Weight: 1 (IGP)
IGP Neighbor Count: 1
Up Thresholds: 15 30 45 60 75 80 85 90 95 96 97 98 99 100
(default)
Down Thresholds: 100 99 98 97 96 95 90 85 80 75 60 45 30 15
(default)
Downstream Global Pool Bandwidth Information (kbits/sec):
KEEP PRIORITY BW HELD BW TOTAL HELD BW LOCKED BW TOTAL LOCKED
0 0 0 0 0
1 0 0 0 0
2 0 0 0 0
3 0 0 0 0
4 0 0 0 0
5 0 0 0 0
6 0 0 0 0
7 0 0 10000 10000
Downstream Sub Pool Bandwidth Information (kbits/sec):
KEEP PRIORITY BW HELD BW TOTAL HELD BW LOCKED BW TOTAL LOCKED
0 0 0 0 0
1 0 0 0 0
2 0 0 0 0
3 0 0 0 0
4 0 0 0 0
5 0 0 0 0
6 0 0 0 0
7 0 0 0 0
>>>>>
2009/10/21 TCP IP4 <[email protected]>
> Thanks Andre and Bryan's comments. You all make good sense.
>
> I think task 6.3 lab5 R7 and R8 fa0/0.807 interface the correct rsvp
> bandwidth should be: ip rsvp bandwidth 1280 512. I don't understand
> why R8's ingress doesn't need rsvp. Is rsvp only for egress
> bandwidth reservation?
>
> 2009/10/20 André Luiz Bernardes <[email protected]>:
> > I think you're missing something... when you tell the router " ip rsvp
> > bandwidth XXX" you are not reserving anything... you are just making such
> a
> > defined bandwidth "reservable" for TE tunnels... lets say you configure
> “ip
> > rsvp bandwidth 10000” (10M) on a FastEthernet (100Mbps), in this case the
> > router will allow up to 10M reservations on that interface. If your first
> > tunnel (transit or local) needs 1Mbps, then you have another 9M available
> > for reservations an so on. RFC 3209 is good reading to understand RSVP TE
> > extensions.
> >
> > Andre
> >
> > On Tue, Oct 20, 2009 at 8:27 PM, TCP IP4 <tcp....@gou mail.com> wrote:
> >>
> >> Thanks for the explanation. While doing vol 2 lab E task 6.3
> >> question comes up with rsvp bandwidth value on R8. I see in the
> >> Proctor's guide that R7's fa0/0.807 has a rsvp bandwidth value. Do I
> >> also need to add "ip rsvp bandwidth xxxx" to fa0/0.807? Can rsvp
> >> be reserved more granulate to TE tunnels?
> >>
> >> On Tue, Oct 20, 2009 at 2:03 PM, Bryan Bartik <[email protected]>
> >> wrote:
> >> > I am not sure what you mean by "different direction TEs." The RSVP
> >> > command
> >> > under the interface specifies the total bandwidth that can be reserved
> >> > (by
> >> > all tunnels for example). The bandwidth configured under the tunnel
> >> > determines how much is reserved for that tunnel - this is done through
> >> > RSVP.
> >> > If this doesn't answer your question, can you give us more specific
> >> > example
> >> > of what you mean?
> >> >
> >> > On Tue, Oct 20, 2009 at 2:43 PM, TCP IP4 <[email protected]> wrote:
> >> >>
> >> >> I understand that TE is unidirectional. Can rsvp also be
> >> >> unidirectional or reserve different bandwidth for different
> direction
> >> >> TEs?
> >> >>
> >> >> On Tue, Oct 20, 2009 at 12:14 PM, Bryan Bartik <[email protected]
> >
> >> >> wrote:
> >> >> > Use the "tunnel mpls traffic-eng bandwidth" command under the
> tunnel
> >> >> > interface. TE Tunnels are unidirectional so the bandwidth
> >> >> > requirements
> >> >> > can
> >> >> > be different in either direction.
> >> >> >
> >> >> > On Tue, Oct 20, 2009 at 11:10 AM, TCP IP4 <[email protected]>
> wrote:
> >> >> >>
> >> >> >> If I have 2 TE tunnels going through the same router with
> different
> >> >> >> bandwidth requirements, I have to use the higher bandwidth
> >> >> >> reservation
> >> >> >> number in "ip rsvp bandwidth <reservation number>". Can rsvp
> >> >> >> bandwidth be done more specific to the tunnel e.g. one rsvp
> >> >> >> reservation in one direction and other rsvp reservation for other
> >> >> >> direction?
> >> >> >>
> >> >> >> Thanks,
> >> >> >> Bill
> >> >> >> _______________________________________________
> >> >> >> For more information regarding industry leading CCIE Lab training,
> >> >> >> please
> >> >> >> visit www.ipexpert.com
> >> >> >
> >> >> >
> >> >> >
> >> >> > --
> >> >> > Bryan Bartik
> >> >> > CCIE #23707 (R&S), CCNP
> >> >> > Sr. Support Engineer - IPexpert, Inc.
> >> >> > URL: http://www.IPexpert.com <http://www.ipexpert.com/>
> >> >> >
> >> >> _______________________________________________
> >> >> For more information regarding industry leading CCIE Lab training,
> >> >> please
> >> >> visit www.ipexpert.com
> >> >
> >> >
> >> >
> >> > --
> >> > Bryan Bartik
> >> > CCIE #23707 (R&S), CCNP
> >> > Sr. Support Engineer - IPexpert, Inc.
> >> > URL: http://www.IPexpert.com <http://www.ipexpert.com/>
> >> >
> >> _______________________________________________
> >> For more information regarding industry leading CCIE Lab training,
> please
> >> visit www.ipexpert.com
> >
> >
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
