Header Only - DO NOT REMOVE - Extreme Networks

Routing between VRFs on S8?


The below configuration works on an N1 running 07.62.06.0004, but not on an S8 running 08.11.04.0006. By working, I mean the interface in vrf test2 can be pinged from the CLI in vrf test1 and vice versa. Does anyone know if the behaviour has changed from 7.x to 8.x? # **** VRF test1 **** set router vrf create test1 context test1 router test1 configure terminal ! interface vlan.0.1000 ip address 192.168.1.1 255.255.255.0 primary no shutdown exit ! # Static routes configured on routed interfaces ip route 192.168.2.0/24 vrf test2 1 ! ! exit exit ! # **** VRF test2 **** set router vrf create test2 context test2 router test2 configure terminal ! interface vlan.0.2000 ip address 192.168.2.1 255.255.255.0 primary no shutdown exit ! # Static routes configured on routed interfaces ip route 192.168.1.0/24 vrf test1 1 ! ! exit exit

6 replies

GTAC has advised that on the S-Series 07.73.01.0003 code the pings work, but on S-Series 08.11.04.0006 the pings do not work. Further investigation continues.
Userlevel 1
Patrick,

Thank you for bringing your configuration to our attention. As you indicated the GTAC is working directly with you and the problem continues to be under investigation. We will post the resolution for the entire community once the solution is available.

Brian Townsend
GTAC have advised that this issue will be addressed in firmware version 8.21.01 which is expected to be generally available by 30 Dec 2013.
From the Problems Corrected section of the release notes for firmware 8.21.02.0002:

"From device command line, a ping to device's address configured in another VRF fails even though VRF route leaking is provided by static routes."

However, route leaking via static routes is now not working at all, i.e. the routes to the remote VRF do not appear at all in the local VRF routing table.

GTAC in contact with developers...
This has finally been corrected in firmware release 8.22.01.0022 / 8.22.01.0023 that was released yesterday 🙂

From the Problems Corrected section of the release notes:

"Static route leaking between non-global VRFs does not work. The routes are not promoted to the FIB."
Userlevel 2
Thank you for the update Patrick!

Reply