[c-nsp] MPLS TE Q

[Eric Osborne]

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



Pete Templin wrote:
| Eric Osborne wrote:
|
|> | How can I have 41.3M allocated on an interface with an allotment of
|> 40M?
|>
|> You'd have to look at the tunnels going out that interface.  First
|> make sure
|> that the sum of all your (outbound) reservations are really 41M, but
|> assuming
|> they are, see if you can find something in the size of each tunnel's
|> reservations that isn't right.  It's certainly possible for autobw to
|> have
|> resized itself to the largest value it'd seen in some time, and if
|> each tunnel
|> has a largest value seen at a different time, the sum of these largest
|> values
|> could easily add up to more than MTRG tells you you're actually seeing
|> at once.
|
|
| I'm running auto-bw at 900 second intervals, so it should be tracking
| real life fairly closely.  I did "sh mpls traff tun int out s0/1/0" and
| saw 20.8M of bandwidth reserved.  12.0(27)S3 on a 7507 if that matters.
|

And if you do 'sh mpls tr tun int out $IF' and 'sh ip rsvp int' at the same
time, you get two vastly different numbers?  From your original email, it looks
like you have 41.3M of bw allocated, which is close enough to 2*20.8M to
suggest that either it's a simple bug or it's supposed to look like that, but I
wouldn't mind knowing what both numbers were when taken at the same time.
If your traffic values are changing a lot you could also be looking at a
temporary result of make-before-break, but I'd be pretty surprised if that
would explain this big of a discrepancy.


eric

| Any thoughts on next steps?
|
| pt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)

iD8DBQFCB5gvYR4YGS5xhWIRAihnAJwJ6kodXzuvLNgPkkTQsFL1PMiosQCgiHL1
M0jJ6Zrk7Mxe4e77z2cIhfU=
=DA27
-----END PGP SIGNATURE-----