[f-nsp] Routes being ignored with MLX4

Mike Allen mkallen at gmail.com
Wed Oct 1 16:32:56 EDT 2014


Jose', first thing to check are ip cache and ip route system max commands.
Default settings for those are not enough for a full table.

Mike
On Oct 1, 2014 12:22 PM, "José Santos" <santosmcjose at gmail.com> wrote:

> Hi,
>
> We are new to Brocade and we are experiencing an unexpected behavihor:
>
> We have an MLX 4 with 5.6b, receiving a full routing table, including
> default route from our ISP.
>
> We are receiving multiple routes from our internal devices like
> 192.168.0.0/25, 192.168.0.128/25 and aggregating with aggregate-address
> 192.168.0.0/24 summary-only.
>
> We have this same setup with other networks that work perfectly, however
> before had this same issue and worked intermitently. This one give us
> always TTL exceeded with ping test from outside and in a traceroute we can
> see it looping towards our ISP. From the router we are able to ping the
> IPs.
>
> We tried to advertise the /24 route from another device with iBGP, however
> it's ignored and the traffic is still is routed to our ISP.
>
> Even after configuring an static route to an internal device, it's ignored
> as well and the 0.0.0.0/0 route is used to route traffic.
>
> If we poing the default route to null0 we lose the TTL exceeded messages
> but we lose connectivity as well. We pointed a static to the device where
> our /25s and /24 is being advertised right now (192.168.0.26) and
> everything started working...
>
> We thought about no free CAM space to install routes, however we don't
> have any warning/error message in logs and we have 50 free routes.
>
> May this this be related with classless / classful routing
> implementations? We find very weird to have a more specific route ignored
> to a default-route, even when a "show ip route" shows the more specific one
> choosen. We never had this behavior before.
>
> Thank you in advance for your help!
>
> --
> Best Regards,
> José
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20141001/6d09b7cc/attachment.html>


More information about the foundry-nsp mailing list