Skip to main content
Viptela is now part of Cisco.
Support
Product Documentation
Viptela Documentation

show omp routes

show omp routes—Display information about OMP routes (on vSmart controllers and vEdge routers only). OMP routes carry information that the vEdge router learns from the routing protocols running on its local network, including routes learned from BGP and OSPF, as well direct, connected, and static routes.

Command Syntax

show omp routes [prefix/length | ip-address] [family family] [vpn vpn-id] [detail]
show omp routes vpn vpn-id (prefix/length | ip-address) [detail]

Options

None
List routing information about all OMP peering sessions on the local device.
Detailed information
detail
List detailed route information about OMP peering sessions on the local device.
Family
family family
List OMP route information for the specified IP family. family can be ipv4 or ipv6.
IP Address
ip-address
List OMP route information for the specified IP address.
Route Prefix
prefix/length
prefix vpn vpn-id
List OMP route information for the specified route prefix. If you omit the prefix length, you must specify a VPN identifier so that the Viptela software can find the route that best matches the prefix.
VPN-Specific Routes
vpn vpn-id
List the OMP routes for the specified VPN.

Output Fields

The output fields are self-explanatory.

Example Output

vSmart# show omp routes 
Code:
C   -> chosen
I   -> installed
Red -> redistributed
Rej -> rejected
L   -> looped
R   -> resolved
S   -> stale
Ext -> extranet
Inv -> invalid
U   -> TLOC unresolved
                                            PATH                      ATTRIBUTE                                                       
VPN    PREFIX              FROM PEER        ID     LABEL    STATUS    TYPE       TLOC IP          COLOR            ENCAP  PREFERENCE  
--------------------------------------------------------------------------------------------------------------------------------------
1      10.2.2.0/24         172.16.255.11    16     2        C,R       installed  172.16.255.11    lte              ipsec  -           
                           172.16.255.20    120    2        C,R       installed  172.16.255.11    lte              ipsec  -           
                           172.16.255.21    17     2        R         installed  172.16.255.21    lte              ipsec  -           
1      10.2.3.0/24         172.16.255.11    17     2        R         installed  172.16.255.11    lte              ipsec  -           
                           172.16.255.20    121    2        C,R       installed  172.16.255.21    lte              ipsec  -           
                           172.16.255.21    16     2        C,R       installed  172.16.255.21    lte              ipsec  -           
1      10.20.24.0/24       172.16.255.15    14     2        C,R       installed  172.16.255.15    lte              ipsec  -           
                           172.16.255.20    154    2        C,R       installed  172.16.255.15    lte              ipsec  -           
1      10.20.25.0/24       172.16.255.16    21     2        C,R       installed  172.16.255.16    lte              ipsec  -           
                           172.16.255.20    131    2        C,R       installed  172.16.255.16    lte              ipsec  -           
1      56.0.1.0/24         172.16.255.15    15     2        C,R       installed  172.16.255.15    lte              ipsec  -           
                           172.16.255.20    153    2        C,R       installed  172.16.255.15    lte              ipsec  -           
1      60.0.1.0/24         172.16.255.16    22     2        C,R       installed  172.16.255.16    lte              ipsec  -           
                           172.16.255.20    130    2        C,R       installed  172.16.255.16    lte              ipsec  -           
1      61.0.1.0/24         172.16.255.16    23     2        C,R       installed  172.16.255.16    lte              ipsec  -           
                           172.16.255.20    129    2        C,R       installed  172.16.255.16    lte              ipsec  -           
1      172.16.255.112/32   172.16.255.11    23     2        C,R       installed  172.16.255.11    lte              ipsec  -           
                           172.16.255.20    122    2        C,R       installed  172.16.255.11    lte              ipsec  -           
                           172.16.255.20    123    2        C,R       installed  172.16.255.21    lte              ipsec  -           
                           172.16.255.21    18     2        C,R       installed  172.16.255.21    lte              ipsec  -           
1      172.16.255.117/32   172.16.255.15    13     2        C,R       installed  172.16.255.15    lte              ipsec  -           
                           172.16.255.20    152    2        C,R       installed  172.16.255.15    lte              ipsec  -           
1      172.16.255.118/32   172.16.255.16    24     2        C,R       installed  172.16.255.16    lte              ipsec  -           
                           172.16.255.20    128    2        C,R       installed  172.16.255.16    lte              ipsec  -

When you configure BGP to propagate AS path information into BGP, the command output shows the AS path that OMP receives from BGP:

vEdge# show running-config vpn 1 router bgp
vpn 1
 router
  bgp 1
   router-id        172.16.255.16
   propagate-aspath
   timers
    keepalive 1
    holdtime  3
   !
   address-family ipv4-unicast
    redistribute static
    redistribute omp
   !
   neighbor 10.20.25.18
    no shutdown
    remote-as 2
    timers
     connect-retry          2
     advertisement-interval 1
    !
    password  $8$3w2P/jZ95uTcMf2u7Xr4ibkyHEi88zoDa4Gz3a30shU=
   !
  !
 !
!

vEdge# show bgp routes 172.16.255.118/32

                        INFO                       LOCAL                      AS                              
VPN  PREFIX             ID    NEXTHOP      METRIC  PREF   WEIGHT  ORIGIN      PATH  PATH STATUS          TAG  
--------------------------------------------------------------------------------------------------------------
1    172.16.255.118/32  0     10.20.25.18  0       -      0       incomplete  2     valid,best,external  0 

vEdge# show omp routes 172.16.255.118/32 detail

---------------------------------------------------
omp route entries for vpn 1 route 172.16.255.118/32
---------------------------------------------------
            RECEIVED FROM:                   
peer            0.0.0.0
path-id         38
label           2
status          C,Red,R
loss-reason     not set
lost-to-peer    not set
lost-to-path-id not set
    Attributes:
     originator       172.16.255.16
     type             installed
     tloc             172.16.255.16, lte, ipsec
     ultimate-tloc    not set
     domain-id        not set
     overlay-id        1
     site-id          600
     preference       not set
     tag              not set
     origin-proto     eBGP
     origin-metric    0
     as-path          "2"
     unknown-attr-len not set
            ADVERTISED TO:                   
peer    172.16.255.19
    Attributes:
     originator       172.16.255.16
     label            2
     path-id          38
     tloc             172.16.255.16, lte, ipsec
     ultimate-tloc    not set
     domain-id        not set
     site-id          600
     overlay-id        1
     preference       not set
     tag              not set
     origin-proto     eBGP
     origin-metric    0
     as-path          "2"
     unknown-attr-len not set
            ADVERTISED TO:                   
peer    172.16.255.20
    Attributes:
     originator       172.16.255.16
     label            2
     path-id          38
     tloc             172.16.255.16, lte, ipsec
     ultimate-tloc    not set
     domain-id        not set
     site-id          600
     overlay-id        1
     preference       not set
     tag              not set
     origin-proto     eBGP
     origin-metric    0
     as-path          "2"
     unknown-attr-len not set
vEdge# 

Release Information

Command introduced in Viptela Software Release 14.1.

  • Was this article helpful?