[j-nsp] RSVP LSP BW reservations

[Guy Davies]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Harpreet,

Without some external (to RSVP and MPLS) mechanism to police the traffic
entering an LSP, then traffic associated with either LSP can consume the
entire 155Mbps (minus the overhead, obviously ;-).  The mechanisms in
RSVP-TE are simply used at the time the LSP is setup to derive a path from
end to end over which there is sufficient un-reserved capacity.  So if,
subsequent to setting up LSP A and LSP X, you try to setup LSP P with a
reservation of 100 Mbps, then assuming that LSPs A and X use the same egress
interface from the LSR, LSP P will have to find an alternative path using a
different egress interface (60 + 40 + 100 > 155) with a minimum of 100 Mbps
of un-reserved bandwidth.  If no such link exists, then the setup of LSP P
fails.

Regards,

Guy

> -----Original Message-----
> From: Harpreet Singh [mailto:Harpreet.Singh at relianceinfo.com]
> Sent: 22 January 2004 11:34
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] RSVP LSP BW reservations
> 
> 
> 
> 
> 
> 
> If I have 2 RSVP signalled LSPs on my network with BW 
> reservations of 60
> Mbps for LSP A and 40 Mbps for LSP X on a STM-1 link (155 Mbps)
> 
> LSP A is dedicated only to traffic classified as abc and LSP 
> X is dedicated
> for traffic classified as xyz.
> 
> What can the traffic abc burst upto
> 
> (1) 60 Mbps (BW for LSP A)
> (2) 60 + 55 Mbps (BW for LSP A + spare BW)
> (3) 155 Mbps (All link BW)
> 
> Thanks in advance
> 
> HS
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
> 

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.0

iQA/AwUBQA/BWo3dwu/Ss2PCEQJYgwCfVszp4WVOq4WDn6a7KkiDnk8noZsAmQGs
7bH4WQuB0w8JUqY+GDURby4Z
=o/JD
-----END PGP SIGNATURE-----