Question

Which are the routing tables of Versa FlexVNF? 


Solution


These are the routing tables of Versa FlexVNF:

Routing Table
Description
ipv4.unicast
This table shows the IPv4 unicast routes received through BGP family inet-unicast from BGP peers.
l3vpn.ipv4.unicast
This table shows L3VPN IPv4 unicast received through MP-BGP with family inet-vpn unicast.
Versa-private
This table shows the SDWAN routes received through MP-BGP with family inet versa-private. These routes are required to build SDWAN overlay.



Examples

  1. Ipv4.unicast routes received from EBGP neighbor
    Run the show route table ipv4.unicast routing-instance MPLS-Transport-VR receive-protocol bgp detail CLI command to display Ipv4.unicast routes received from EBGP neighbor.
    admin@Branch-cli> show route table ipv4.unicast routing-instance MPLS-Transport-VR receive-protocol bgp detail  
    
    Routes for Routing instance : MPLS-Transport-VR  AFI: ipv4
    
    
    Routing entry for 192.168.20.0/24
        Peer Address     : 192.168.22.1
        Next-hop         : 192.168.22.1
        MED              : 0
        Local preference : 100
        AS path          : 64000
        Origin           : Igp
        Community        : [ 100:100 ]
        ExtCommunity     : [ target:1L:2 ]
    
    
    Routing entry for 192.168.32.0/24
        Peer Address     : 192.168.22.1
        Next-hop         : 192.168.22.1
        MED              : 0
        Local preference : 100
        AS path          : 64000
        Origin           : Igp
        Community        : [ 100:100 ]
        ExtCommunity     : [ target:1L:2 ]
  2. l3vpn.Ipv4.unicast routes received from IBGP neighbor
    Run show route table l3vpn.ipv4.unicast routing-instance Customer1-Control-VR receive-protocol bgp CLI command to display l3vpn.Ipv4.unicast routes received from IBGP neighbor.
    admin@Branch-cli> show route table l3vpn.ipv4.unicast routing-instance Customer1-Control-VR receive-protocol bgp
    
    Routes for Routing instance : Customer1-Control-VR  AFI: ipv4
    
    Routing entry for 10.10.10.0/24
       Route Distinguisher: 3L:3
       Peer Address       : 10.2.64.2
       VPN Label          : 25728
       Community          : [ 8009:8009 ]
       Extended community : [ target:3L:3 ]
       Next-hop           : 10.2.64.105
       MED                : 0
       Local Preference   : 100
       Origin             : Igp 
       AS Path            : N/A
    
    Routing entry for 172.16.1.0/24
       Route Distinguisher: 3L:3
       Peer Address       : 10.2.64.2
       VPN Label          : 25472
       Community          : [ 8009:8009 ]
       Extended community : [ target:3L:3 ]
       Next-hop           : 10.2.64.101
       MED                : 0
       Local Preference   : 100
       Origin             : Igp
       AS Path            : N/A
    
    Routing entry for 172.16.2.0/24
       Route Distinguisher: 3L:3
       Peer Address       : 10.2.64.2
       VPN Label          : 25472
       Community          : [ 100:100 300:300 8009:8009 ]
       Extended community : [ target:3L:3 ]
       Next-hop           : 10.2.64.101
       MED                : 0
       Local Preference   : 100
       Origin             : Igp
       AS Path            : 64513 64005 64000 64001
  3. Versa-private routes received from IBGP neighbor
    Run these CLI commands to display Versa-private routes received from IBGP neighbor.
    admin@Branch-cli> show route table versa-private routing-instance  receive-protocol bgp                
    
    Possible completions:
    
    Broadband-Failover-VR  Provider-Control-VR  Customer1-Control-VR  Customer1-LAN-VR  MPLS-Transport-VR  global
    
    admin@Branch-cli> show route table versa-private routing-instance Customer1-Control-VR  receive-protocol bgp
    
    Routes for Routing instance : Customer1-Control-VR  AFI: ipv4
       Routing entry for RouterId 10.2.64.1
       Route Type         : 1
       Community          : [ N/A ]
       Extended community : [ N/A ]
       Next-hop           : 10.2.64.1
       MED                : 0
       Local Preference   : 100
       Origin             : Incomplete
       AS Path            : N/A
    
    
    Routing entry for RouterId 10.2.64.1
       Route Type         : 3
       Community          : [ N/A ]
       Extended community : [ N/A ]
       Next-hop           : 10.2.64.1
       MED                : 0
       Local Preference   : 100
       Origin             : Incomplete
       AS Path            : N/A