8300: Static default route stays inactive even with no ospf default routes

[firstlastcase]

Can anybody tell me in which cases the static route stays in "inactive" state while the destination is reachable from the switch?

what i understand is that even if that route is not populated in the routing table due to high cost or pref value, the static route should show "active". in my switch case, it shows inactive!

[Flintstone]

Hi firstlastcase and welcome to the forum,

I have 'floating statics' configured in my Network and they only become active when the primary route is lost, they then populate the routing table.   I believe 'floating statics' should be inactive or they will be used for routing traffic?

CheerZ

[firstlastcase]

Thanks Flinststone for the reply,

I have tested enabling a static default route with higher pref. value than the ospf advsertised default route and it became active but not populated in the routing table (which is what is required) where it should only be populated there when the default ospf route is unavailable.


can you agree?
have you tested your scenario and it became really active?
The avaya document (ip routing) mentions multiple events where the static route changes its state (e.g become inactive). such events are like deleting a vlan, etc. so i think even if the static route shows "active" it does not mean that it is populated in the routing table cause that still depends on its pref. value and cost.

Regards,
firstlastcase

[Michael McNamara]

You mention OSPF, do you have a policy to redistribute the static routes into OSPF? They won't just redistribute on their own.

Cheers!

[firstlastcase]

Thanks Michael for the reply.
well .. i have changed this reply!

i know where to find it but still in doubt why i need to use it. all what i need is to let the routing switch to use the static default route in case the ospf default route is unavailable. so i want the static route to be shown in the routing table and i dont care about advertising it through ospf (if that was the use of the policies).

in this case i can configure a static route with higher pref. value and higher metric than the existing ospf default routes, right?

[Flintstone]

Hi firstlastcase,

I have to confess that my routing is done by my Cisco core, so my experience could be different to the way Nortel/Avaya do their routing?

CheerZ

[Michael McNamara]

Hi firstlastcase,

I have to confess that my routing is done by my Cisco core, so my experience could be different to the way Nortel/Avaya do their routing?

CheerZ

Thanks Michael for the reply.
well .. i have changed this reply!

i know where to find it but still in doubt why i need to use it. all what i need is to let the routing switch to use the static default route in case the ospf default route is unavailable. so i want the static route to be shown in the routing table and i dont care about advertising it through ospf (if that was the use of the policies).

in this case i can configure a static route with higher pref. value and higher metric than the existing ospf default routes, right?

Yes you can... you only need a route policy if you want to redistribute the static route into OSPF. If you just want the static route to exist on that router only then you just need to create the route and enable it. Perhaps you could show use the routing table in question "show ip route info" and "show ip static-route info".

You can check the default preference values between the different routing protocols with "show ip route preference info". Again this is on an ERS 8600 but it should be pretty close on an ERS 8300.

Here's an example of a route policy on an ERS 8600;


ip route-policy "staticOSPF" seq 1 create
ip route-policy "staticOSPF" seq 1 enable
ip route-policy "staticOSPF" seq 1 match-protocol static
ip route-policy "staticOSPF" seq 1 set-metric-type type2

ip ospf redistribute static create
ip ospf redistribute static route-policy "staticOSPF"
ip ospf redistribute static enable


Cheers!

[lsimonet]

Hello Firstlastcase,

I would just like to understand the issue you are having.

Are you saying that the static route you have created on your 8300, shows as inactive in the Static route table?

If that is the case it is mostly because the switch cannot resolve the MAC address of the next hop.

Hope this helps.

L.

[firstlastcase]

thanks lsimonet,

could that reason be possible while i was able to ping the next hop successfully and it says alive?!!