[nsp] load balancing bug?
Dan Hollis
goemon at anime.net
Wed Dec 17 19:16:34 EST 2003
On Wed, 17 Dec 2003 jlewis at lewis.org wrote:
> On Wed, 17 Dec 2003, Dan Hollis wrote:
> > On Wed, 17 Dec 2003, Voll, Scott wrote:
> > > Use per packet rather then the Per destination.
> > fwiw, that didnt work either. its still always using only one path.
> What are the interfaces for the paths?
fwiw this was working fine up until a few days ago, then it mysteriously
stopped working -- without any configuration changes at all.
i'm suspecting an IOS bug, but this is a particularly busy core router i
am loathe to reboot.
#sh ip cef 0.0.0.0 0.0.0.0 det
0.0.0.0/0, version 1361, per-destination sharing
0 packets, 0 bytes
via x.x.110.177, 0 dependencies, recursive
traffic share 1
next hop x.x.110.177, ATM1/0.4034 via x.x.110.176/30
valid adjacency
via y.y.180.2, 0 dependencies, recursive
traffic share 1
next hop y.y.180.2, ATM1/0.4032 via y.y.180.0/30
valid adjacency
0 packets, 0 bytes switched through the prefix
tmstats: external 0 packets, 0 bytes
internal 0 packets, 0 bytes
More information about the cisco-nsp
mailing list