Skip to main content
virg9454
New Member
May 7, 2021
Question

VRF Leaking 6.4.5 with more the 2 VRFs

  • May 7, 2021
  • 6 replies
  • 9723 views

FortiGate 60F FortiOS 6.4.5

 

I am trying to figure out how to build the npu0_vlink to be able to create VRF-Leaking with up to 5 VRFs.   I followed the instructions on https://docs.fortinet.com/document/fortigate/6.4.0/new-features/834664/route-leaking-between-vrfs, but to keeps things simple I am using static routes to add the routes, which works fine.  With 2 VRF.  But now I need to allow VRF 30 to also access VRF 10, and VRF 3 to access VRF 5.   I create new npu0_vlink2 and so one, but they don't seem to work if I  do a diag sys session list, it looks like it has a problem getting a mac for the remote side of the npu link.   

 

 

This works!

edit "npu0_vlink0"
set vdom "root"
set vrf 10
set ip 172.16.201.1 255.255.255.0
set allowaccess ping https ssh snmp http
next
edit "npu0_vlink1"
set vdom "root"
set vrf 20
set ip 172.16.201.2 255.255.255.0
set allowaccess ping https ssh snmp http telnet
next
end

The below does not work!

edit "npu0_vlink3" set vdom "root" set vrf 3 set ip 172.16.201.3 255.255.255.0 set allowaccess ping https ssh snmp http set device-identification enable set role lan set snmp-index 28 set interface "internal5" set vlanid 3 next edit "npu0_vlink4" set vdom "root" set vrf 4 set ip 172.16.201.4 255.255.255.0 set allowaccess ping https ssh snmp http set device-identification enable set role lan set snmp-index 29 set interface "internal4" set vlanid 4 next end

    6 replies

    Toshi_Esumi
    SuperUser
    SuperUser
    May 7, 2021

    npuX_vlinks are physical interfaces based on your model's npu chip(s). You can't create or remove them.

    Each npu vlink has only two interfaces 0 and 1, like npu0_vlink0 and npu0_vlink1. Nothing more. Then you can use 0 on one end and 1 to the other as in the example.

    If you need to have more than one pair on one npu-vlink, you have to use VLAN subinterfaces on the vlink. The most common cases are bridging between VDOMs, like connecting root vdom to all other vdoms, which could be many. In that case one VLAN interface on npu0_vlink0 is on root vdom side, another VLAN interface with the same VLAN ID on npu0_vlank1 is on the other vdom side. Then they can communicate each other over the VLAN after you put proper routing&policy in place.

     

    Kangming
    Staff
    Staff
    May 7, 2021

    Hi Virg, 

     

     

    In my lab environment, One VLINK can only meet the route leaking of 2 VRFs. If all 5 VRFs need to route leaking, that need to establish a FULL-MESH V-LINK(10 * V-LINK/10 * carry VLAN-TAG interface by VLINK) to meet the requirements, or use a normal physical interface and cooperate with an external switch.

     

    The configuration of the second inter-connected VRF line is not correct, and it cannot communicate with different VLAN-IDs.

     

        edit "npu0_vlink3"     ----This is actually a VLAN interface, not a V-LINK interface

        set vdom "root"

        set vrf 3

        set ip 172.16.201.3 255.255.255.0

        set allowaccess ping https ssh snmp http

        set device-identification enable

        set role lan

        set snmp-index 28

        set interface "internal5"

        set vlanid 3

        next

        edit "npu0_vlink4"

        set vdom "root"

        set vrf 4

        set ip 172.16.201.4 255.255.255.0

        set allowaccess ping https ssh snmp http

        set device-identification enable

        set role lan

        set snmp-index 29

        set interface "internal4"

        set vlanid 4

        next

        end

    For example, the following interconnection method:

    internal5 --------Direct interconnection------------- internal4

    internal5_tag-vlan-3 (VRF 3)-----------------------------internal4_tag-vlan-3(VRF4)

    virg9454
    virg9454Author
    New Member
    May 8, 2021

    Using an external switch is a last resort.    Really need this to work on box, do you have a sample config on how to configure FULL-MESH V-LINK(10 * V-LINK/10 * carry VLAN-TAG interface by VLINK?  

    Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
    Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!