Technical Tip: How to check VRF in a session table

• Interface configuration:

config system interface

    edit "LB-10"

        set vdom "root"

        set vrf 10

        set ip 200.10.10.1 255.255.255.0

        set allowaccess ping

        set type loopback

        set role lan

        set snmp-index 17

        set ip-managed-by-fortiipam disable

    next

end

    edit "LB-20"

        set vdom "root"

        set vrf 20

        set ip 200.10.20.1 255.255.255.0

        set allowaccess ping

        set type loopback

        set role lan

        set snmp-index 18

        set ip-managed-by-fortiipam disable

    next

end

• Ping Test on VRF10:

• Session Table VRF10:

• Similarly, the information can be extracted from Session Table VRF20:
  

Understanding vd=0:20.
The parameter vd=0:20 provides information about Virtual Domains (VDOMs) and Virtual Routing and Forwarding (VRF).

vd=0: This indicates that the VDOM index is 0, which is typically associated with the root VDOM. To verify the VDOM index, execute the following command in the global VDOM: diagnose sys vd list.

In most cases, the root VDOM is assigned an index of 0.

20 (VRF Information): The number following the colon represents VRF (Virtual Routing and Forwarding) information. This value provides insight into the routing table instance associated with the VDOM.

Example:

FortiGate-100E (global) # diagnose sys vd list | grep index
name=root/root index=0 enabled fib_ver=73 rpdb_ver=0 use=373 rt_num=29 asym_rt=0 sip_helper=0, sip_nat_trace=1, mc_fwd=0, mc_ttl_nc=0, tpmc_sk_pl=0
name=vsys_ha/vsys_ha index=1 enabled fib_ver=5 rpdb_ver=1 use=263 rt_num=0 asym_rt=0 sip_helper=0, sip_nat_trace=1, mc_fwd=0, mc_ttl_nc=0, tpmc_sk_pl=0
name=vsys_fgfm/vsys_fgfm index=2 enabled fib_ver=4 rpdb_ver=0 use=260 rt_num=0 asym_rt=0 sip_helper=0, sip_nat_trace=1, mc_fwd=0, mc_ttl_nc=0, tpmc_sk_pl=0
name=test/test index=3 enabled fib_ver=18 rpdb_ver=0 use=313 rt_num=35 asym_rt=0 sip_helper=0, sip_nat_trace=1, mc_fwd=0, mc_ttl_nc=0, tpmc_sk_pl=0