Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the test case to verify the route type(routes learned via) #884

Open
vitthalmagadum opened this issue Oct 15, 2024 · 0 comments · May be fixed by #925
Open

Add the test case to verify the route type(routes learned via) #884

vitthalmagadum opened this issue Oct 15, 2024 · 0 comments · May be fixed by #925
Assignees

Comments

@vitthalmagadum
Copy link
Collaborator

vitthalmagadum commented Oct 15, 2024

Verify the route's type, such as whether it was learned via:

  • Directly connected interfaces
  • Static configurations
  • Dynamic routing protocols (e.g., BGP, OSPF, EIGRP)

Sample output:

leaf2-dc1#show ip route vrf all

VRF: default
Codes: C - connected, S - static, K - kernel, 
       O - OSPF, IA - OSPF inter area, E1 - OSPF external type 1,
       E2 - OSPF external type 2, N1 - OSPF NSSA external type 1,
       N2 - OSPF NSSA external type2, B - Other BGP Routes,
       B I - iBGP, B E - eBGP, R - RIP, I L1 - IS-IS level 1,
       I L2 - IS-IS level 2, O3 - OSPFv3, A B - BGP Aggregate,
       A O - OSPF Summary, NG - Nexthop Group Static Route,
       V - VXLAN Control Service, M - Martian,
       DH - DHCP client installed default route,
       DP - Dynamic Policy Route, L - VRF Leaked,
       G  - gRIBI, RC - Route Cache Route,
       CL - CBF Leaked Route

Gateway of last resort is not set

 B E      10.10.0.1/32 [200/0] via 10.100.0.12, Ethernet1
                               via 10.100.0.14, Ethernet2
 C        10.100.0.12/31 is directly connected, Ethernet1
 C        10.100.0.14/31 is directly connected, Ethernet2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant