ICX Static route not added to table

  • 1
  • Question
  • Updated 2 months ago
  • Acknowledged
ICX7450 running 10.1.16T215, when I configure additional static routes they aren't getting added to the routing table - so the destination is still just hitting the default route.
Tried different AD / cost and prefix length from /20 all the way to /32 without a difference.
Any ideas?
Photo of Simon Hamilton-Wilkes

Simon Hamilton-Wilkes

  • 5 Posts
  • 0 Reply Likes

Posted 2 months ago

  • 1
Photo of Jijo Panangat

Jijo Panangat, Employee

  • 102 Posts
  • 35 Reply Likes
Hello Simon,

Could you confirm if you are running a routing or switching code ?
'show version' o/p can help

Secondly, Is the next-hop reachable from switch ?  
Photo of NETWizz

NETWizz

  • 213 Posts
  • 66 Reply Likes
10.1.16T215 is the bootrom not the actual flash code.  Per Jijo Panagat, you need to run flash code with an R in it like SPR08090f.bin because that is  your Layer-3 firmware (R = Router).

SPS08090f.bin for example is Layer-2 firmware (S = Switch)... Does NOT do 

Also, you need to have at least one (1) operational up/up interface in the VLAN that has the VE attached to it.

For example

vlan 123 name test by port
untagged ethe 1/2/1
router-interface ve 123
!


interface ve 123
ip address 10.1.2.1 255.255.224.0
!

^^^ Above is a /20 example

It will add 10.1.0.0/20 to your routing table as DIRECT (directly-conneccted) via ve 123

However, it will ONLY add that to the routing table if untagged e 1/2/1 is up in this example.  Do a "show interfaces brief"


I hope that helps.
Photo of Simon Hamilton-Wilkes

Simon Hamilton-Wilkes

  • 5 Posts
  • 0 Reply Likes
The code is SPR08091.bin so a routing image - a bunch of other static and OSPF routes are working fine.  Including to the gateway I'm adding routes to...which is what I don't understand.
Photo of Jijo Panangat

Jijo Panangat, Employee

  • 102 Posts
  • 35 Reply Likes
Can you share a snippet of your routing table and static route you are trying to add ?
Photo of NETWizz

NETWizz

  • 213 Posts
  • 66 Reply Likes
Is the network you are attempting to route to reachable via a directly-connected subnet or a up interface?



Is the network you are trying to get to reachable via another layer-3 device connected to this one via a directly-connected network? You pr static route should be in the format: network/mask (where I need to get to) via next-hop or interface.


The next-hop should be an IP via a directly-connected network. To create a directly-connected network, you assign an IP with Mask to a Layer-3 interface (generally a ve interface) known as a virtual router interface (VRI).. if you come from the Cisco world these are referred to as SVIs (Software Virtual Interfaces), and they are your interface vlan 123 interfaces...


******


The below are generally for special use cases only, but they are worth understanding the behavior of the ICX...


Use a static route or even a routing protocol to resolve a static route (yikes):


device(config)# ip route next-hop-recursion 4


Resolve a static route with a default route:

Router(config)# ip route next-hop-enable-default
(Edited)
Photo of Simon Hamilton-Wilkes

Simon Hamilton-Wilkes

  • 5 Posts
  • 0 Reply Likes
Yes the next hop is directly connected (10.1.2.1) and the gateway has OSPF routes pointing at it which are working fine.
Type Codes - B:BGP D:Connected O:OSPF R:RIP S:Static; Cost - Dist/Metric
BGP  Codes - i:iBGP e:eBGP
OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2
        Destination        Gateway         Port          Cost          Type Uptime
1       0.0.0.0/0          10.1.1.1        ve 3          1/1           S    45d17h
2       10.0.0.0/8         10.1.1.1        ve 3          1/1           S    20d3h 
3       10.0.0.0/24        10.1.1.1        ve 3          110/10        O2   4d19h 
4       10.0.5.1/32        10.1.1.1        ve 3          110/61        O    4d19h 
5       10.0.6.0/24        10.1.2.1        ve 2          110/60        O    10d12h
...
14      10.1.1.0/29        DIRECT          ve 3          0/0           D    45d17h
15      10.1.2.0/29        DIRECT          ve 2          0/0           D    33d4h 
16      169.254.253.0/30   10.1.2.1        ve 2          110/1050      O    10d12h
17      169.254.253.4/30   10.1.2.1        ve 2          110/1050      O    10d12h

In the configuration I have:
ip route 172.31.0.0/20 10.1.2.1
ip route 172.31.4.0/24 10.1.2.1 name AWS
ip route 172.31.4.13/32 10.1.2.1
None of which make it to the table.

Thanks for any ideas.  I'm thinking I may need to try a reboot/code upgrade at this point.
Photo of Jijo Panangat

Jijo Panangat, Employee

  • 102 Posts
  • 35 Reply Likes

Thanks, Could you pls open a tac case for remote debugging ? Also o/p of 'show ip route 10.1.2.1' 



Photo of Simon Hamilton-Wilkes

Simon Hamilton-Wilkes

  • 5 Posts
  • 0 Reply Likes
I have a TAC case already, 01051607, I'll try and get it escalated to a remote session tomorrow.

[email protected]#sh ip route 10.1.2.1
Type Codes - B:BGP D:Connected O:OSPF R:RIP S:Static; Cost - Dist/Metric
BGP  Codes - i:iBGP e:eBGP
OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2
        Destination        Gateway         Port          Cost          Type Uptime
1       10.1.2.0/29        DIRECT          ve 2          0/0           D    35d13h
Photo of Jijo Panangat

Jijo Panangat, Employee

  • 102 Posts
  • 35 Reply Likes
Thanks Simon, I'll notify the team as well.
Photo of Simon Hamilton-Wilkes

Simon Hamilton-Wilkes

  • 5 Posts
  • 0 Reply Likes
It was suggested by support I 'clear IP route' 
Sure enough this fixed it and the routes went into the table and now work.  Still plan to upgrade to probably 8.0.92b at some point as the .91 release doesn't seem to be actively maintained.


Photo of Jijo Panangat

Jijo Panangat, Employee

  • 102 Posts
  • 35 Reply Likes
Got you, Do you remember how you landed into the problem state - May be a route flap, power outage,switch crash, etc..? If the issue resurface let us know.



Thanks
Jijo