Are you sure is not just your filtering at the "show route ospf" command, that
leads you to believe there you only send over the 2nd bundle?
>From the "show ip route" command it looks like both paths are installed and
>you are sending traffic over both paths equally.
Did you try the following config:
router ospf 12345
area XXXX ! <--- your area number where the Bundle-Ether
interfaces are
interface Bundle-Ether1
cost 10
interface Bundle-Ether2
cost 20
The above will affect all prefixes learned from these paths, i.e. routes will
be preferred via Bundle-Ether1 , while Bundle-Ether2 will be just a backup path.
On 4 Apr 2013, at 11:42, Lee Starnes wrote:
> Hello,
>
> We are trying to change the administrative distance on one of the OSPF
> neighbors of our router and no matter what it is set to, the value does not
> seem to change.
>
> #sh ip route x.x.0.102
> Thu Apr 4 02:36:05.122
>
> Routing entry for x.x.0.102/32
> Known via "ospf 12345", distance 110, metric 2, type intra area
> Installed Apr 4 02:14:55.059 for 00:21:10
> Routing Descriptor Blocks
> x.x.25.19, from x.x.0.102, via Bundle-Ether1
> Route metric is 2
> x.x.25.34, from x.x.0.102, via Bundle-Ether2
> Route metric is 2
> No advertising protos.
>
> #sh route ospf | incl x.x.0.102
> Thu Apr 4 03:31:36.554
> O x.x.0.102/32 [110/2] via x.x.25.34, 01:16:40, Bundle-Ether2
>
>
> The issue here is that we are trying to avoid sending a majority of our
> traffic through Bundle-Ether2 which it seems OSPF has decided is the best
> Path. The 0.102 address is a loopback interface of a neighbor (6500b)
> directly connected to Bundle-Ether1, where Bundle-Ether2 is connected to
> 6500a with less capacity on it's links. This is causing the links on
> bundle2 to get saturated at peak times.
>
> XR-bundle2--->6500a--->6500b
> XR-bundle1--->6500b--->6500a
>
> Configured XR router:
>
> router ospf 12345
> log adjacency changes
> distance 120 x.x.25.34 0.0.0.0
>
> Is this a bug or am I going about this all wrong?
> _______________________________________________
> cisco-nsp mailing list [email protected]
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
