topic Re: VOSS Static Route Showing 'INACTV' in ExtremeSwitching (VSP/Fabric Engine)

VOSS Static Route Showing 'INACTV'

Anonymous — Fri, 07 May 2021 19:19:44 GMT

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.

Re: VOSS Static Route Showing 'INACTV'

Miguel-Angel_RO — Fri, 07 May 2021 19:23:02 GMT

Martin,

The next hop is probably not a direct hop.

could you share a traceroute to this next hop?

Mig

Re: VOSS Static Route Showing 'INACTV'

Anonymous — Fri, 07 May 2021 19:35:12 GMT

Hi Mig,

Here is the traceroute:

Core:1#traceroute 172.20.248.221

Sending traceroute in context grt
traceroute to 172.20.248.221, 30 hops max, 56 byte packets
 1  172.20.248.221  1.291 ms 0.805 ms 0.759 ms

To add a little context here….. this VSP is connected to the network and natively sharing routes via ISIS, so it is aware of all other ISIS routes in the fabric.

The other routers though have both ISIS and OSPF enabled, and ISIS is being distributed into OSPF

This VSP is therefore only away of ISIS routes, but the Mgmt CIip is being advertised into the wider network and being learnt and shared by OSPF, so that direction is good.

I can’t reach the Mgmt Clip of this VSP via the wider network, only on local ISIS shared routes (all the other fabric switches) because I need to add a default route back into the network for the OSPF routes its not aware of.

I could redistribute OSPF into ISIS, or enable OSPF on this router, but it doesn’t need to know that level of detail, just point back to the primary routers that have the routing entries - that may break the concept of fabric, so interested on the response.

What has been perplexing me, this aside, is what address to use as the next-hop, seeing as it must be an ISIS learned IP.

Those static routes are pointing to MGMT and ISIS Clips of the other routers (as the ISIS learned IP’s), hence why they are reachable, but that could be part of the problem?

Appreciate you might need a little context here, so let me know if you need anymore detail.

Cheers,

Martin

Re: VOSS Static Route Showing 'INACTV'

Miguel-Angel_RO — Fri, 07 May 2021 20:12:54 GMT

Martin,

Without global overview it is not so easy to debug.

Can you share the result of

show ip interface
show ip route | in 172.20.248.
show vlan mac-address-entry XXX where XXX is the VLAN hpsting the subnet 172.20.248.

Mig

Re: VOSS Static Route Showing 'INACTV'

Dan15 — Fri, 07 May 2021 20:50:46 GMT

If it is a non-local-next-hop, you need to add a static ARP entry to make the route active:

==================================================================================================
IP Static Route - GlobalRouter
==================================================================================================
DEST MASK NEXT NH-VRF COST PREF LCLNHOP STATUS ENABLE
--------------------------------------------------------------------------------------------------
192.168.100.0 255.255.255.0 172.18.143.254 GlobalRouter 1 1 TRUE INACTV TRUE

From the VOSS guide:

Static routes

A static route is a route to a destination IP address that you manually create.
The Layer 3 redundancy feature supports the creation of static routes to enhance network stability.
Use the local next hop option to configure a static route with or without local next hop.
You can configure static routes with a next hop that is not directly connected, but that hop must be
reachable. Otherwise, the static route is not enabled.
Layer 3 redundancy supports only address resolution protocol (ARP) and static route. Static ARP
must configure the nonlocal next-hop of static routes. No other dynamic routing protocols provide
nonlocal next-hop.

Re: VOSS Static Route Showing 'INACTV'

Miguel-Angel_RO — Fri, 07 May 2021 21:12:11 GMT

Dany,

I wouldn’t do that static arp entry.

You can flag the route as non-local-hop in the config with an argument in the command or via the GUI.

Mig

Re: VOSS Static Route Showing 'INACTV'

Anonymous — Fri, 07 May 2021 21:48:54 GMT

Hi Mig,

See output below.

The only one I can’t get you is “show vlan mac-address-entry” as none of the address below in the routing table are associated to a VLAN they, are just CLIP address of all the other fabric routers.

If you was to hop on one of those other routers the routing table are very considerably larger because they contain all the OSPF routes.

You can see I’ve tried adding different static routes to different IP addresses listed below, which are reachable via ping?

I was wondering if the new management segmentation that come out in 8.2 (that these are running) has something to do with it, maybe something additional I need to add?

Is there a separate command to add a route in reference to the management CLIP, this is how I configured it. This is the address I am able to SSH to from the other fabric switches, just not the rest of the network because of that missing default route?

mgmt clip vrf GlobalRouter
ip address {{ mgmtClip }}/{{ mgmtClipMask }}
enable
exit

#show ip route
************************************************************************************
                Command Execution Time: Fri May 07 14:33:15 2021 GMT
************************************************************************************
=====================================================================================================
                                       IP Route - GlobalRouter
=====================================================================================================
                                                     NH                      INTER
DST             MASK            NEXT                 VRF/ISID         COST   FACE     PROT AGE TYPE PRF
-----------------------------------------------------------------------------------------------------
172.20.248.211  255.255.255.255 Cor-CEF-Core1        GlobalRouter     70     4051     ISIS 0   IBS  7
172.20.248.212  255.255.255.255 Cor-CEF-Core2        GlobalRouter     110    4051     ISIS 0   IBS  7
172.20.248.213  255.255.255.255 Cor-CEF-WAN01        GlobalRouter     80     4051     ISIS 0   IBS  7
172.20.248.221  255.255.255.255 Cor-2A22-Core1       GlobalRouter     10     4051     ISIS 0   IBS  7
172.20.248.222  255.255.255.255 Cor-2A22-Core2       GlobalRouter     60     4051     ISIS 0   IBS  7
172.20.248.223  255.255.255.255 172.20.248.223       -                1      0        LOC  0   DB   0
172.20.250.128  255.255.255.248 Cor-2A22-Core1       GlobalRouter     10     4051     ISIS 0   IBS  7
172.20.250.208  255.255.255.252 Cor-2A22-Core1       GlobalRouter     10     4051     ISIS 0   IBS  7
172.20.250.216  255.255.255.252 Cor-CEF-Core1        GlobalRouter     70     4051     ISIS 0   IBS  7
172.20.250.244  255.255.255.252 Col-2A22-Core2       GlobalRouter     60     4051     ISIS 0   IBS  7
172.20.250.248  255.255.255.252 172.20.250.250       -                1      4053     LOC  0   DB   0
172.20.255.211  255.255.255.255 Cor-CEF-Core1        GlobalRouter     70     4051     ISIS 0   IBS  7
172.20.255.212  255.255.255.255 Cor-CEF-Core2        GlobalRouter     110    4051     ISIS 0   IBS  7
172.20.255.213  255.255.255.255 Cor-CEF-WAN01        GlobalRouter     80     4051     ISIS 0   IBS  7

172.20.255.221  255.255.255.255 Cor-2A22-Core1       GlobalRouter     10     4051     ISIS 0   IBS  7
172.20.255.222  255.255.255.255 Cor-2A22-Core2       GlobalRouter     60     4051     ISIS 0   IBS  7
172.20.255.223  255.255.255.255 172.20.255.223       -                1      4090     LOC  0   DB   0

17 out of 17 Total Num of Route Entries, 17 Total Num of Dest Networks displayed.
--------------------------------------------------------------------------------------------------


#show ip route | in 172.20.248
************************************************************************************
                Command Execution Time: Fri May 07 14:34:16 2021 GMT
************************************************************************************
172.20.248.211  255.255.255.255 Cor-CEF-Core1        GlobalRouter     70     4051     ISIS 0   IBS  7
172.20.248.212  255.255.255.255 Cor-CEF-Core2        GlobalRouter     110    4051     ISIS 0   IBS  7
172.20.248.213  255.255.255.255 Cor-CEF-WAN01        GlobalRouter     80     4051     ISIS 0   IBS  7
172.20.248.221  255.255.255.255 Cor-2A22-Core1       GlobalRouter     10     4051     ISIS 0   IBS  7
172.20.248.222  255.255.255.255 Cor-2A22-Core2       GlobalRouter     60     4051     ISIS 0   IBS  7
172.20.248.223  255.255.255.255 172.20.248.223       -                1      0        LOC  0   DB   0

Nonlocal next hop, how do I configure that or set the flag if that is an option I should try?

#ip route 0.0.0.0 0.0.0.0 10.10.10.10 ?
  enable          Enable the route.
  local-next-hop  Enable static route local-next-hop
  name            Set the static route name
  preference      Route preference
  weight          Create a route;cost of hops

Thanks

Re: VOSS Static Route Showing 'INACTV'

Miguel-Angel_RO — Fri, 07 May 2021 22:14:21 GMT

I see the issue.

You cannot have a CLIP as next-hop.

A next-hop is an outgoing door for your fabric and must be associated with a VLAN interface or a brouter interface.

If your VOSS has no default route, the VSP hosting the outgoing VLAN must announce this default route in ISIS.

Mig

Re: VOSS Static Route Showing 'INACTV'

Anonymous — Fri, 07 May 2021 22:27:52 GMT

Hi Mig,

Thanks for confirming that.

That did cross my mind, but….

Am I right in thinking a VLAN interface will not come up without an active port, and to create a brouter I would need to associate with an interface.

Neither of those fit because all the interfaces are NNI interfaces, and where CLIP would be perfect.

… but then I’m stuck because I can’t use a CLIP in this instance

Sorry, might be obvious but just wondering what I do in this instance?

Thanks

Re: VOSS Static Route Showing 'INACTV'

Miguel-Angel_RO — Fri, 07 May 2021 22:32:05 GMT

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:

or via CLI with

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

Mig

Re: VOSS Static Route Showing 'INACTV'

Anonymous — Fri, 07 May 2021 22:42:10 GMT

Ok, that did it…. brilliant!

Thanks Mig and Danny 🙂