Reference Guide

C 11.11.11.0/24 [0/1] directly connected, 0/11
S 10.3.2.0/24 [1/0] via 1.1.1.2, 0/11
The following example shows CLI display output for the command to indicate a truncated route.
(router) #show ip route
Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, S - Static
B - BGP Derived, IA - OSPF Inter Area
E1 - OSPF External Type 1, E2 - OSPF External Type 2
N1 - OSPF NSSA External Type 1, N2 - OSPF NSSA External Type 2
L-Leaked Route K - Kernel P - Net Prototype
O E1 100.1.161.0/24 [110/10] via 172.20.11.100, 00h:00m:13s, 2/11 T
O E1 100.1.162.0/24 [110/10] via 172.20.11.100, 00h:00m:13s, 2/11 T
O E1 100.1.163.0/24 [110/10] via 172.20.11.100, 00h:00m:13s, 2/11 T
The following shows an example of output that displays leaked routes.
Subnetwork 9.0.0.0/24 is a connected subnetwork in global table and subnet 56.6.6.0/24 is reachable
via a gateway 9.0.0.2 in the global table. These two routes leak into the virtual router Red and leak the
connected subnet 8.0.0.0/24 from Red to global table.
When leaking connected route in the global routing table to a virtual router, the /32 host route for the
leaked host is added in the virtual router instance’s route table. Leaking of non /32 connected routes
into the virtual router table from global routing table is not supported.
This enables the nodes in subnet 8.0.0.0/24 to access shared services via the global routing table. Also
we add a non-leaked static route for 66.6.6.0/24 subnetwork scoped to the domain of virtual router
Red.
(Router) (Config)#ip route vrf Red 9.0.0.2 255.255.255.255 9.0.0.2 0/26
(Router) (Config)#ip route vrf Red 56.6.6.0 255.255.255.0 9.0.0.2 0/26
(Router) (Config)#ip route vrf Red 66.6.6.0 255.255.255.0 8.0.0.2
(Router) (Config)#ip route 8.0.0.0 255.255.255.0 0/27
(Router) #show ip route vrf Red
Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, S - Static
B - BGP Derived, IA - OSPF Inter Area
E1 - OSPF External Type 1, E2 - OSPF External Type 2
N1 - OSPF NSSA External Type 1, N2 - OSPF NSSA External Type 2
L – Leaked Route K - Kernel P - Net Prototype
C 8.0.0.0/24 [0/1] directly connected, 0/27
S L 9.0.0.2/32 [1/1] directly connected, 0/26
S L 56.6.6.0/24 [1/1] via 9.0.0.2, 02d:22h:15m, 0/26
S 66.6.6.0/24 [1/1] via 8.0.0.2, 01d:22h:15m, 0/27
(Router) #show ip route
Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, S - Static
B - BGP Derived, IA - OSPF Inter Area
E1 - OSPF External Type 1, E2 - OSPF External Type 2
N1 - OSPF NSSA External Type 1, N2 - OSPF NSSA External Type 2
L – Leaked Route
C 9.0.0.0/24 [0/1] directly connected, 0/26
S L 8.0.0.0/24 [1/1] directly connected, 0/27
The following shows an example of the output that displays with a hardware failure.
(Router) (Config)#interface 0/1
(Router) (Interface 0/1)#routing
(Router) (Interface 0/1)#ip address 9.0.0.1 255.255.255.0
(Router) (Interface 0/1)#exit
(Router) (Config)#ip route net-prototype 56.6.6.0/24 9.0.0.2 1
(Router) #show ip route
Route Codes: R - RIP Derived, O - OSPF Derived, C - Connected, S - Static
Routing Commands
ExtremeSwitching 200 Series: Command Reference Guide for version 01 .02.04.0007 524