Sofware-Defined Networking

Reply
Occasional Contributor
Posts: 10
Registered: ‎10-12-2017

import a static route from the default routing table

Hello,

 

I have vrf conifguration and need to import one statitc route from the default routing table?

I have not found the command yet. Can somebody please help me?

 

Here is my VRF config:

routing {
        routing-instance APLEONA {
                instance-type vrf
                interface vif1533

 

I know that I need a route-distingusher and route-target import.

 

Thanks for your help in advance.

 

Best regards

Roger

Brocade Moderator
Posts: 79
Registered: ‎06-10-2009

Re: import a static route from the default routing table

Hello Roger,

 

I am not sure that you can easily export/import routes to and from the default vrf since I can't find an easy way to set the route-target.  Between non-default vrfs is OK as you can easily specify the route-target for import/export but you will need to enable BGP as well to do the leaking of routes.

 

If it's just one route it might be simpler to just configure the same static route in the routing instance eg

 

vyatta@vrouter3# set rou rou APLEONA prot static route 1.1.1.0/24 next-hop-rout default next-hop 192.168.253.1

which results in routing table

 

IP Route Table for Routing-instance "vrf1"
S    *> 1.1.1.0/24 [1/0] via 192.168.253.1, dp0p192p1 (default)
C    *> 10.0.0.223/32 is directly connected, lo1
B    *> 10.0.1.223/32 [20/0] is directly connected, lo2 (vrf2), 00:04:46

Regards

Steve

Occasional Contributor
Posts: 10
Registered: ‎10-12-2017

Re: import a static route from the default routing table

Hi Steve,

 

thanks for your proposal. I have added the static route and the static route is the routing table of the VRF. I can not ping any device from the VRF. From the default routing table I can ping the gateway and the target system.

Also the next-hop I can not ping from the VRF. Do I miss something?

 

Best regards

Roger

Brocade Moderator
Posts: 79
Registered: ‎06-10-2009

Re: import a static route from the default routing table

Hello Roger,

I just realised that I forgot about the opposite direction.  You would therefore need static routes in the opposite direction.

 

It looks like you are trying to go from a directly connected subnet in one vrf to an indirectly connected subnet in another vrf.  Setting the static route for the indirectly connected subnet is not a problem since you can set the next-hop routing instance and the next-hop-ip.  However configuring the static route in the opposite direction ie within the default-vrf pointing to the other-vrf is going to be a problem if the target subnet is directly connected to the vrouter, since you do not have a next-hop-ip.

 

I did a quick test to try and use an interface-route, where the next-hop interface is in the other-vrf but this fails.

 

So at the moment the only other thing I could think of is to use BGP to directly import routes between the two vrfs but you would have to use two non-default-vrfs for this to work.  I'll have a look to see if there is any other way.

 

Regards

Steve

Occasional Contributor
Posts: 10
Registered: ‎10-12-2017

Re: import a static route from the default routing table

Hello,

 

I have now configured the import:
vyatta@ap5nfw001par-5400# run sh ip route routing-instance Apleona
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
       O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       L - LDP, V - RSVP-TE, I - IGP shortcut
       > - selected route, * - FIB route, p - stale info

IP Route Table for Routing-instance "Apleona"
C    *> 10.92.159.208/28 is directly connected, dp0bond0.1533
C    *> 10.92.159.209/32 is directly connected, dp0bond0.1533
B    *> 10.126.26.64/26 [20/0] is a summary, Null (Management), 00:35:40
[edit]
vyatta@ap5nfw001par-5400# run ping 10.126.26.65 routing-instance Apleona
connect: Invalid argument
[edit]
vyatta@ap5nfw001par-5400# run ping 10.126.26.65 routing-instance Apleona in
interface  interval
[edit]
vyatta@ap5nfw001par-5400# run ping 10.126.26.65 routing-instance Apleona interface dp0bond0.1533
PING 10.126.26.65 (10.126.26.65) from 10.92.159.211 dp0bond0.1533: 56(84) bytes of data.
From 10.92.159.211 icmp_seq=1 Destination Host Unreachable
From 10.92.159.211 icmp_seq=2 Destination Host Unreachable
From 10.92.159.211 icmp_seq=3 Destination Host Unreachable
^C
--- 10.126.26.65 ping statistics ---
6 packets transmitted, 0 received, +3 errors, 100% packet loss, time 5224ms
pipe 4
[edit]
vyatta@ap5nfw001par-5400# run sh ip route routing-instance Apleona
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
       O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       L - LDP, V - RSVP-TE, I - IGP shortcut
       > - selected route, * - FIB route, p - stale info

IP Route Table for Routing-instance "Apleona"
C    *> 10.92.159.208/28 is directly connected, dp0bond0.1533
C    *> 10.92.159.209/32 is directly connected, dp0bond0.1533
B    *> 10.126.26.64/26 [20/0] is a summary, Null (Management), 00:36:40
[edit]
vyatta@ap5nfw001par-5400# run sh ip route routing-instance Management
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
       O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
       L - LDP, V - RSVP-TE, I - IGP shortcut
       > - selected route, * - FIB route, p - stale info

IP Route Table for Routing-instance "Management"
S    *> 10.0.0.0/14 [1/0] via 10.126.36.65, dp0bond0
S    *> 10.85.56.128/26 [1/0] via 10.126.36.65, dp0bond0
C    *> 10.92.159.180/30 is directly connected, tun4
C    *> 10.92.159.188/30 is directly connected, tun2
B    *> 10.92.159.208/28 [20/0] is a summary, Null (Apleona), 00:36:45
C    *> 10.126.36.64/26 is directly connected, dp0bond0
S    *> 10.254.10.130/32 [1/0] via 10.126.36.65, dp0bond0
[edit]
vyatta@ap5nfw001par-5400# run ping 10.92.159.211 routing-instance Management in
interface  interval
[edit]
vyatta@ap5nfw001par-5400# run ping 10.92.159.211 routing-instance Management interface dp0bond0
PING 10.92.159.211 (10.92.159.211) from 10.126.36.88 dp0bond0: 56(84) bytes of data.
From 10.126.36.88 icmp_seq=1 Destination Host Unreachable
From 10.126.36.88 icmp_seq=2 Destination Host Unreachable
From 10.126.36.88 icmp_seq=3 Destination Host Unreachable
From 10.126.36.88 icmp_seq=4 Destination Host Unreachable
From 10.126.36.88 icmp_seq=5 Destination Host Unreachable
From 10.126.36.88 icmp_seq=6 Destination Host Unreachable
From 10.126.36.88 icmp_seq=7 Destination Host Unreachable
From 10.126.36.88 icmp_seq=8 Destination Host Unreachable
From 10.126.36.88 icmp_seq=9 Destination Host Unreachable
From 10.126.36.88 icmp_seq=10 Destination Host Unreachable
From 10.126.36.88 icmp_seq=11 Destination Host Unreachable
From 10.126.36.88 icmp_seq=12 Destination Host Unreachable
^C
--- 10.92.159.211 ping statistics ---
14 packets transmitted, 0 received, +12 errors, 100% packet loss, time 13547ms
pipe 4

The ping is still not working between the two VRFs.

Do I miss something?

 

Best regards

 

Roger

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook