[c-nsp] MPLS TE Q

[Eric Osborne]

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



Pete Templin wrote:
| OK, so I've deployed MPLS TE with auto bandwidth.  Looks to me like
| things are hunky dory, until last night when I think to check on things
| and see something like this:
|
| core2-dlls#sh ip rs int
| interface    rsvp  allocated  i/f max  flow max sub max
| Fa0/0/0      ena   24403K     95M      95M      0
| Se0/1/0      ena   41310K     40M      40M      0
| Se0/1/1      ena   0          40M      40M      0
| Fa4/0/0      ena   0          95M      95M      0
| Fa4/1/0      ena   0          95M      95M      0
| Tu2          ena   0          0        0        0
|
| 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.



eric

|   For what it's worth, MRTG has never shown that interface any higher
| than 27.2M.
|
| Thanks,
|
| pt
| _______________________________________________
| cisco-nsp mailing list  cisco-nsp at puck.nether.net
| https://puck.nether.net/mailman/listinfo/cisco-nsp
| archive at http://puck.nether.net/pipermail/cisco-nsp/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)

iD8DBQFCA+ewYR4YGS5xhWIRAnUeAKCLHBjMlF9OB+kVZvpg0pRx9mDwswCfcM8h
o7xR5CfubT1xgiK6IsiqpEc=
=NZnH
-----END PGP SIGNATURE-----