cancel
Showing results for 
Search instead for 
Did you mean: 

VOSS Static Route Showing 'INACTV'

VOSS Static Route Showing 'INACTV'

Anonymous
Not applicable

Have a horrible feeling this is going to be an obvious one…. but can’t find any literature as to the reason why the static routes below keep going into a status of ‘INACTV’?

Only reference I found is that it might if the IP address isn’t reachable, which isn’t the case here?

In essence I am just trying to add a default route, and as you can see I’ve tried many iterations but all show inactive, and are pingable. None of the next hop addresses are directly connected.

I believe in VOSS the next hop doesn’t need to be directly connected?


Core:1#show ip route static
************************************************************************************
Command Execution Time: Fri May 07 12:11:27 2021 GMT
************************************************************************************

==================================================================================================================================
IP Static Route - GlobalRouter
==================================================================================================================================
DEST MASK NEXT NH-VRF COST PREF LCLNHOP STATUS ENABLE NAME
----------------------------------------------------------------------------------------------------------------------------------
0.0.0.0 0.0.0.0 172.20.248.221 GlobalRouter 1 5 TRUE INACTV TRUE
0.0.0.0 0.0.0.0 172.20.250.210 GlobalRouter 1 1 TRUE INACTV TRUE
0.0.0.0 0.0.0.0 172.20.255.221 GlobalRouter 1 1 TRUE INACTV TRUE
10.119.192.0 255.255.255.0 172.20.255.221 GlobalRouter 1 1 TRUE INACTV TRUE

Total Static Routes Displayed: 4

----------------------------------------------------------------------------------------------------------------------------------
Core:1#ping 172.20.248.221

Sending ping in context grt
172.20.248.221 is alive

Any idea what might be happening here?

Many thanks.

 

1 ACCEPTED SOLUTION

Miguel-Angel_RO
Valued Contributor II

Martin,

The last trick (not reccomended but I don’t catch all your setup) would be to declare the next hop as non local changing the last flag in the screenshot here to false:

db7b0937929b4a589eb9254dad96b669_233ade97-1926-4851-aa9d-67c42bef4018.png

or via CLI with

no ip route 0.0.0.0 0.0.0.0 192.168.101.121 local-next-hop enable

 

Mig

View solution in original post

10 REPLIES 10

Miguel-Angel_RO
Valued Contributor II

Martin,

The next hop is probably not a direct hop.

could you share a traceroute to this next hop?

Mig

GTM-P2G8KFN