Introduction
Virtual Routing and Forwarding Instances (VRFs) are used to segregate traffic at Layer 3. They are similar in concept to VLANs that are used to segregate traffic at Layer 2. VRFs create virtual routers with separate instances of the routing table (RIB) and forwarding table (FIB) independent from the global routing table. VRFs segment traffic in the data-plane and the control-plane based on the logical or physical interface that you assign to the VRF. The concept of VRFs is similar to that of virtual machines (VMs). It is important to note that the concept of VRF is locally significant to the device on which it is configured. VRFs improve network functionality because network paths can be segmented without requiring multiple physical routers. VRF-Lite is a feature of VRF that provides VRF without MPLS configuration.
If VRFs are configured on more than one router to ensure end to end connectivity, the links interconnecting the routers will need to be configured as a trunk (for layer 2 switches) or sub-interfaces (for routers) if a single link is to be shared with traffic from other separate VRFs or the default routing table. VRFs leverage trunk links with 802.1Q encapsulation to maintain connectivity with same VRFs on remote devices.
By default, all routers have single running VRF instance referred to as the global VRF instance. All interfaces, the global routing table, the forwarding table are assigned to this global VRF instance. One or more VRF instances can be configured on a single router that are separate from the global routing VRF instance. The configured VRF instances can then be identified by their configured VRF names. Interfaces or sub-interfaces are then assigned to the configured VRFs. IP addresses configured on these VRF instances can overlap if the interfaces are assigned to different VRFs. These IP addreses are not included in the global routing table. If routing protocols are configured for each VRF instance, then separate SFP (OSPF) or DUAL (EIGRP) calculation instances take place for each VRF instance.
VRFs generically segment traffic at Layer 3. However, it is possible to leak traffic between VRFs if such connectivity is required. This can be done through:
- Through importing or exporting routes between the multiple routing tables.
- Static routing.
- Physical cable to leak traffic.
Minimum configuration of VRF is called VRF Lite; VRFs without any MPLS configuration. The main reason for VRF Lite is separation of the control-plane.
The number of VRFs on a single device should be limited to a small number as each VRF instance consumes local resources.
Business Use Cases of VRF
- ISPs use VRFs to keep IP routing tables of customers logically separate to create separate VPNs for each customer when layer 3 end-to-end connectivity is provided; thus the technology is also referred to as VPN routing and forwarding.
- Network segmentation for different applications, departments
- Security concerns
- Corporate mergers
- Data Centre access
VRF-Aware Routing
To support dynamic routing in VRFs, the routing protocols in use should be VRF aware. Static routes support VRF. VRF-aware dynamic routing protocols include: RIP, EIGRP, OSPF, IS-IS, MP-BGP. Policy routing is also VRF-aware.
Configuration
Step 1: Specify Locally Significant VRF Name
VRFs can be configured in one of two ways:
-
ip vrf <vrf-name>: This global configuration command supports only IPv4 VRFs.R2(config)#ip vrf RESEARCH
R2(config)#ip vrf FINANCE
R2(config-vrf)#description Finance VRF
-
vrf definition <name>: This global configuration command supports IPv4 and IPv6 VRFs. It is generally recommended to configure VRFs using this format. The address family should be additionally configured using the VRF mode commandaddress-family ipv4. The address family needs to be explicitly configured after defining the VRF name.R3(config)#vrf definition RESEARCH
R3(config-vrf)#description Research and Development Department VRF
R3(config-vrf)#address-family ipv4
R3(config-vrf-af)#exit
R3(config-vrf)#exit
R3(config)#vrf definition FINANCE
R3(config-vrf)#description Finance Department VRF
R3(config-vrf)#address-family ipv4
Cisco IOS has additional commands that enable VRFs created using the command
ip vrf <vrf-name> to support IPv6.
To enable support for IPv6 VRFs, in global configuration mode issue the command
vrf upgrade-cli multi-af-mode common-policies vrf <vrf-name> .
By default all VRFs will be configured to support IPv4 and IPv6. If the optional
VRF name is configured, only the specified VRF will support IPv4 and IPv6.
The keyword common-policies copies the pre-configured
parameters such as route-target, route distinguisher to be applied to IPv6
as previously configured under IPv4.
Any IPv6 addresses configured on the interfaces assigned to any VRF will be
removed. When you view the running configuration file, the syntax will be
changed to vrf definition <vrf-name> which is the
new format.
The VRF description can be added to provide helpful information on the purpose of
the VRF. It can be added using the VRF mode command
description <description>.
CAUTION:
- If deleting a VRF using the command
no ip vrf <vrf-name>the IPv4 addresses configured on the interfaces assigned to that VRF will be removed. - VRF names are case sensitive. It is recommended to use all upper case letters for VRF names.
In VRF-lite, there is no need to specify the import and export route target (RT). and route distinguisher (RD).
Step 2: Apply VRF to the Interface
Interfaces, physical or logical, can belong to only one VRF at a time. Interfaces assigned to the VRF belong to that VRF's routing table instance. Interfaces not in a VRF are in the global or default VRF. Interfaces are assigned to VRFs depending on the way the VRF was created using one of the following interface mode commands:
ip vrf forwarding <vrf-name>: This command is used when the VRF was created using the global configuration commandip vrf <name>.R1(config)#interface gigabitethernet1/0
R1(config-if)#ip vrf forwarding FINANCE
vrf forwarding <vrf-name>: This command is used when the VRF was created using the global configuration commandvrf definition <vrf-name>.R3(config)#interface gigabitethernet3/0
R3(config-if)#vrf forwarding FINANCE
Step 3: Routing with the VRF
VRF-aware Static Route
To configure a static route for a VRF, run the global configuration command:
ip route vrf <vrf-name> <network> <mask> <next-hop>
R1(config)#ip route vrf FINANCE 172.17.1.0 255.255.255.0 10.20.13.2
VRF-Aware Dynamic Routing
The following routing protocols are VRF-aware: EIGRP, IS-IS, OSPF, BGP, RIP.
EIGRP
EIGRP is VRF-aware in both classic and named mode. The configuration of VRF routing for classic and named mode is similar.
EIGRP Named Mode
router eigrp EIGRP_NAMED
address-family ipv4 vrf <vrf-name> autonomous-system <id>
R2(config)#router eigrp EIGRP_NAMED
R2(config-router)#address-family ipv4 unicast vrf FINANCE autonomous-system 1
EIGRP Classic Mode
R2(config)#router eigrp 1 vrf FINANCE
OSPF
router ospf <process-id> vrf <vrf-name>
R2(config)#router ospf 1 vrf RESEARCH
R2(config-router)#capability vrf-lite
The command R2(config-router)#capability vrf-lite causes OSPF
to not perform PE specific checks.
BGP
Service providers use BGP VRFs extensively to segregate customer traffic. To utilize
VRFs in BGP, the route distinguisher needs to be configured to uniquely identify traffic.
Configuration of the route target is done using the VRF configuration mode command
rd <ASN:nn> or
rd <ip-address:nn>
The RD is used to keep the routes from various clients unique regardless of whether
the IP addresses used are overlapping; how we distinguish one route in one VRF
from a route in another VRF particularly when the IP addresses are overlapping
in prefix and prefix-length. In some versions of IOS, the RD needs to be configured
otherwise the following error message is displayed when configuring VRF support in BGP.
R2(config)#router bgp 65000
R2(config-router)#bgp router-id 2.2.2.2
R2(config-router)#address-family ipv4 unicast vrf FINANCE
% VRF FINANCE does not have an RD configured.
If two VRF instances X and Y have overlapping IP addresses, such as 10.0.0.0/24. and VRF X has a configured RD of 1:1 and Y 2:2, the addresses will be differentiated such that X's addresses will be 1:1:10.0.0.0/24 and Y 2:2:10.0.0./24. In the case of MP-BGP, these count as two separate routes.
R2(config)#ip vrf FINANCE
R2(config-vrf)#rd 65000:100
R2(config)#router bgp 65000
R2(config-router)#address-family ipv4 unicast vrf FINANCE
R2(config-router-af)#neighbor 10.20.13.2 ebgp-multihop 2
R2(config-router-af)#address-family vpnv4 unicast
On remote router:
R3(config-router)#vrf definition FINANCE
R3(config-vrf)#rd 65001:200
R3(config-if)#router bgp 65001
R3(config-router)#address-family ipv4 unicast vrf FINANCE
R3(config-router-af)#neighbor 10.20.12.2 remote-as 65000
R3(config-router-af)#neighbor 10.20.12.2 ebgp-multihop 2
R3(config-router-af)#network 10.3.10.0 mask 255.255.255.0
R3(config-router)#address-family vpnv4 unicast
Verification
All testing or verification commands have to include the specific VRF whose features you would like to view.
show ip route vrf <vrf-name>
To view the IP routing table of a specific VRF.
R2#show ip route vrf RESEARCH
Routing Table: RESEARCH
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 10 subnets, 3 masks
C 10.2.14.0/24 is directly connected, Loopback14
L 10.2.14.1/32 is directly connected, Loopback14
C 10.2.15.0/24 is directly connected, Loopback15
L 10.2.15.1/32 is directly connected, Loopback15
B 10.3.14.0/24 [20/0] via 10.10.13.2, 00:43:49
B 10.3.15.0/24 [20/0] via 10.10.13.2, 00:44:17
B 10.3.16.0/24 [20/0] via 10.10.13.2, 00:44:09
C 10.10.12.0/30 is directly connected, GigabitEthernet0/0.10
L 10.10.12.2/32 is directly connected, GigabitEthernet0/0.10
O 10.10.13.0/30 [110/2] via 10.10.12.1, 01:17:12, GigabitEthernet0/0.10
172.30.0.0/24 is subnetted, 1 subnets
O 172.30.0.0 [110/3] via 10.10.12.1, 01:17:12, GigabitEthernet0/0.10
172.31.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.31.1.0/24 is directly connected, GigabitEthernet1/0
L 172.31.1.1/32 is directly connected, GigabitEthernet1/0
R2#
ping vrf <vrf-name>
Check reachability of remote networks.
R2#ping vrf RESEARCH 10.2.14.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.2.14.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/6/12 ms
R2#
show run vrf <vrf-name>
To view VRF configurations for a specific vrf.
R2#show run vrf FINANCE
Building configuration...
Current configuration : 715 bytes
ip vrf FINANCE
description Finance VRF
rd 65000:100
!
!
interface GigabitEthernet0/0
no ip address
duplex auto
speed auto
media-type gbic
negotiation auto
!
interface GigabitEthernet0/0.20
encapsulation dot1Q 20
ip vrf forwarding FINANCE
ip address 10.20.12.2 255.255.255.252
!
interface FastEthernet4/0
ip vrf forwarding FINANCE
ip address 172.16.1.10 255.255.255.0
duplex auto
speed auto
!
router eigrp 1
!
address-family ipv4 vrf FINANCE autonomous-system 1
network 10.20.12.0 0.0.0.3
exit-address-family
!
router bgp 65000
!
address-family ipv4 vrf FINANCE
neighbor 10.20.13.2 remote-as 65001
neighbor 10.20.13.2 ebgp-multihop 2
neighbor 10.20.13.2 activate
exit-address-family
!
end
show ip vrf
To view configured VRFs.
R2#show ip vrf
Name Default RD Interfaces
FINANCE 65000:100 Gi0/0.20
Fa4/0
RESEARCH 65000:200 Gi0/0.10
Gi1/0
Lo14
Lo15
show ip route vrf *
To view the IP routing table for all VRFs at once.
R2#show ip route vrf *
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
Routing Table: FINANCE
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 7 subnets, 3 masks
B 10.3.10.0/24 [20/0] via 10.20.13.2, 04:25:16
B 10.3.11.0/24 [20/0] via 10.20.13.2, 02:22:08
B 10.3.12.0/24 [20/0] via 10.20.13.2, 02:21:21
B 10.3.13.0/24 [20/0] via 10.20.13.2, 01:45:26
C 10.20.12.0/30 is directly connected, GigabitEthernet0/0.20
L 10.20.12.2/32 is directly connected, GigabitEthernet0/0.20
D 10.20.13.0/30
[90/3072] via 10.20.12.1, 05:28:49, GigabitEthernet0/0.20
172.16.0.0/16 is variably subnetted, 3 subnets, 2 masks
C 172.16.1.0/24 is directly connected, FastEthernet4/0
L 172.16.1.10/32 is directly connected, FastEthernet4/0
D 172.16.2.0/24
[90/28672] via 10.20.12.1, 05:28:49, GigabitEthernet0/0.20
Routing Table: RESEARCH
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
+ - replicated route, % - next hop override
Gateway of last resort is not set
10.0.0.0/8 is variably subnetted, 10 subnets, 3 masks
C 10.2.14.0/24 is directly connected, Loopback14
L 10.2.14.1/32 is directly connected, Loopback14
C 10.2.15.0/24 is directly connected, Loopback15
L 10.2.15.1/32 is directly connected, Loopback15
B 10.3.14.0/24 [20/0] via 10.10.13.2, 01:24:15
B 10.3.15.0/24 [20/0] via 10.10.13.2, 01:24:43
B 10.3.16.0/24 [20/0] via 10.10.13.2, 01:24:35
C 10.10.12.0/30 is directly connected, GigabitEthernet0/0.10
L 10.10.12.2/32 is directly connected, GigabitEthernet0/0.10
O 10.10.13.0/30 [110/2] via 10.10.12.1, 01:57:38, GigabitEthernet0/0.10
172.30.0.0/24 is subnetted, 1 subnets
O 172.30.0.0 [110/3] via 10.10.12.1, 01:57:38, GigabitEthernet0/0.10
172.31.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.31.1.0/24 is directly connected, GigabitEthernet1/0
L 172.31.1.1/32 is directly connected, GigabitEthernet1/0
R2#
show ip interfaces vrf <vrf-name>
Display interfaces in specified VRF.
show ip protocols vrf <vrf-name>
View dynamic protocols running in a VRF.
R2#show ip protocols vrf FINANCE
*** IP Routing is NSF aware ***
Routing Protocol is "eigrp 1"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP-IPv4 Protocol for AS(1) VRF(FINANCE)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 172.16.1.10
Topology : 0 (base)
Active Timer: 3 min
Distance: internal 90 external 170
Maximum path: 4
Maximum hopcount 100
Maximum metric variance 1
Total Prefix Count: 3
Total Redist Count: 0
Automatic Summarization: disabled
Maximum path: 4
Routing for Networks:
10.20.12.0/30
Routing Information Sources:
Gateway Distance Last Update
10.20.12.1 90 04:45:54
Distance: internal 90 external 170
Routing Protocol is "bgp 65000"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
IGP synchronization is disabled
Automatic route summarization is disabled
Neighbor(s):
Address FiltIn FiltOut DistIn DistOut Weight RouteMap
10.20.13.2
Maximum path: 1
Routing Information Sources:
Gateway Distance Last Update
10.20.13.2 20 01:02:31
Distance: external 20 internal 200 local 200
R2#
EIGRP
show ip eigrp vrf <vrf-name> topology
R2#show ip eigrp vrf FINANCE topology
EIGRP-IPv4 Topology Table for AS(1)/ID(172.16.1.10) VRF(FINANCE)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 10.20.12.0/30, 1 successors, FD is 2816
via Connected, GigabitEthernet0/0.20
P 172.16.2.0/24, 1 successors, FD is 28672
via 10.20.12.1 (28672/28416), GigabitEthernet0/0.20
P 10.20.13.0/30, 1 successors, FD is 3072
via 10.20.12.1 (3072/2816), GigabitEthernet0/0.20
show ip eigrp vrf <vrf-name> neighbors
R2#show ip eigrp vrf FINANCE neighbors detail
EIGRP-IPv4 Neighbors for AS(1) VRF(FINANCE)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 10.20.12.1 Gi0/0.20 12 04:34:57 17 102 0 7
Version 10.0/2.0, Retrans: 0, Retries: 0, Prefixes: 2
Topology-ids from peer - 0
show ip eigrp vrf <vrf-name> interfaces
Alternative command show eigrp address-family ipv4 vrf <vrf-name> interfaces
R2#show ip eigrp vrf FINANCE interface detail
EIGRP-IPv4 Interfaces for AS(1) VRF(FINANCE)
Xmit Queue PeerQ Mean Pacing Time Multicast Pending
Interface Peers Un/Reliable Un/Reliable SRTT Un/Reliable Flow Timer Routes
Gi0/0.20 1 0/0 0/0 17 0/0 64 0
Hello-interval is 5, Hold-time is 15
Split-horizon is enabled
Next xmit serial
Packetized sent/expedited: 1/0
Hello's sent/expedited: 3579/2
Un/reliable mcasts: 0/1 Un/reliable ucasts: 1/1
Mcast exceptions: 0 CR packets: 0 ACKs suppressed: 0
Retransmissions sent: 0 Out-of-sequence rcvd: 1
Topology-ids on interface - 0
Authentication mode is not set
R2#
BGP
show bgp vpnv4 unicast all
To view all the shared prefixes in all VRFs
R2(config-if)#do show bgp vpnv4 unicast all
BGP table version is 10, local router ID is 2.2.2.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 65000:100 (default for vrf FINANCE)
*> 10.3.10.0/24 10.20.13.2 0 0 65001 i
*> 10.3.11.0/24 10.20.13.2 0 0 65001 i
*> 10.3.12.0/24 10.20.13.2 0 0 65001 i
*> 10.3.13.0/24 10.20.13.2 0 0 65001 i
Route Distinguisher: 65000:200 (default for vrf RESEARCH)
*> 10.2.14.0/24 0.0.0.0 0 32768 i
*> 10.2.15.0/24 0.0.0.0 0 32768 i
*> 10.3.14.0/24 10.10.13.2 0 0 65001 i
*> 10.3.15.0/24 10.10.13.2 0 0 65001 i
*> 10.3.16.0/24 10.10.13.2 0 0 65001 i
R2(config-if)#
show bgp vpnv4 unicast vrf <vrf-name> summary
To view routes in the BGP table in a specific VRF
R2(config-if)#do show bgp vpnv4 unicast vrf RESEARCH
BGP table version is 10, local router ID is 2.2.2.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 65000:200 (default for vrf RESEARCH)
*> 10.2.14.0/24 0.0.0.0 0 32768 i
*> 10.2.15.0/24 0.0.0.0 0 32768 i
*> 10.3.14.0/24 10.10.13.2 0 0 65001 i
*> 10.3.15.0/24 10.10.13.2 0 0 65001 i
*> 10.3.16.0/24 10.10.13.2 0 0 65001 i
show bgp vpnv4 unicast vrf <vrf-name> neighbor
To view BGP neighbors formed in a specific VRF
R2#show bgp vpnv4 unicast vrf RESEARCH neighbor
BGP neighbor is 10.10.13.2, vrf RESEARCH, remote AS 65001, external link
BGP version 4, remote router ID 3.3.3.3
BGP state = Established, up for 00:36:27
Last read 00:00:42, last write 00:00:27, hold time is 180, keepalive interval is 60 seconds
Neighbor sessions:
1 active, is not multisession capable (disabled)
Neighbor capabilities:
Route refresh: advertised and received(new)
Four-octets ASN Capability: advertised and received
Address family IPv4 Unicast: advertised and received
Enhanced Refresh Capability: advertised and received
Multisession Capability:
Stateful switchover support enabled: NO for session 1
Message statistics:
InQ depth is 0
OutQ depth is 0
Sent Rcvd
Opens: 1 1
Notifications: 0 0
Updates: 3 4
Keepalives: 40 41
Route Refresh: 0 0
Total: 44 46
Default minimum time between advertisement runs is 0 seconds
For address family: VPNv4 Unicast
Translates address family IPv4 Unicast for VRF RESEARCH
Session: 10.10.13.2
BGP table version 10, neighbor version 10/0
Output queue size : 0
Index 2, Advertise bit 0
2 update-group member
Slow-peer detection is disabled
Slow-peer split-update-group dynamic is disabled
Sent Rcvd
Prefix activity: ---- ----
Prefixes Current: 2 3 (Consumes 192 bytes)
Prefixes Total: 2 3
Implicit Withdraw: 0 0
Explicit Withdraw: 0 0
Used as bestpath: n/a 3
Used as multipath: n/a 0
Outbound Inbound
Local Policy Denied Prefixes: -------- -------
Bestpath from this peer: 3 n/a
Total: 3 0
Number of NLRIs in the update sent: max 1, min 0
Last detected as dynamic slow peer: never
Dynamic slow peer recovered: never
Refresh Epoch: 1
Last Sent Refresh Start-of-rib: never
Last Sent Refresh End-of-rib: never
Last Received Refresh Start-of-rib: never
Last Received Refresh End-of-rib: never
Sent Rcvd
Refresh activity: ---- ----
Refresh Start-of-RIB 0 0
Refresh End-of-RIB 0 0
Address tracking is enabled, the RIB does have a route to 10.10.13.2
Connections established 1; dropped 0
Last reset never
External BGP neighbor may be up to 2 hops away.
Transport(tcp) path-mtu-discovery is enabled
Graceful-Restart is disabled
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Connection is ECN Disabled, Mininum incoming TTL 0, Outgoing TTL 2
Local host: 10.10.12.2, Local port: 179
Foreign host: 10.10.13.2, Foreign port: 17911
Connection tableid (VRF): 2
Maximum output segment queue size: 50
Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes)
Event Timers (current time is 0x124CFC4):
Timer Starts Wakeups Next
Retrans 43 0 0x0
TimeWait 0 0 0x0
AckHold 45 41 0x0
SendWnd 0 0 0x0
KeepAlive 0 0 0x0
GiveUp 0 0 0x0
PmtuAger 0 0 0x0
DeadWait 0 0 0x0
Linger 0 0 0x0
ProcessQ 0 0 0x0
iss: 3387542972 snduna: 3387543921 sndnxt: 3387543921
irs: 2815833713 rcvnxt: 2815834735
sndwnd: 15436 scale: 0 maxrcvwnd: 16384
rcvwnd: 15363 scale: 0 delrcvwnd: 1021
SRTT: 997 ms, RTTO: 1025 ms, RTV: 28 ms, KRTT: 0 ms
minRTT: 16 ms, maxRTT: 1000 ms, ACK hold: 200 ms
Status Flags: passive open, gen tcbs
Option Flags: VRF id set, nagle, path mtu capable
IP Precedence value : 6
Datagrams (max data segment is 1460 bytes):
Rcvd: 90 (out of order: 0), with data: 46, total data bytes: 1021
Sent: 88 (retransmit: 0, fastretransmit: 0, partialack: 0, Second Congestion: 0), with data: 44, total data bytes: 948
Packets received in fast path: 0, fast processed: 0, slow path: 0
fast lock acquisition failures: 0, slow path: 0
TCP Semaphore 0x6AAD22B4 FREE
R2#
OSPF
OSPF commands do not require the inclusion of the VRF keyword and VRF name within the command.
show ip ospf
Displays the VRF operational state of OSPF.
R2#show ip ospf
Routing Process "ospf 1" with ID 172.31.1.1
Domain ID type 0x0005, value 0.0.0.1
Start time: 00:00:55.892, Time elapsed: 06:21:24.020
Supports only single TOS(TOS0) routes
Supports opaque LSA
Supports Link-local Signaling (LLS)
Supports area transit capability
Supports NSSA (compatible with RFC 3101)
Connected to MPLS VPN Superbackbone, VRF RESEARCH
Event-log disabled
It is an area border router
Router is not originating router-LSAs with maximum metric
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Incremental-SPF disabled
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Number of external LSA 0. Checksum Sum 0x000000
Number of opaque AS LSA 0. Checksum Sum 0x000000
Number of DCbitless external and opaque AS LSA 0
Number of DoNotAge external and opaque AS LSA 0
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Number of areas transit capable is 0
External flood list length 0
IETF NSF helper support enabled
Cisco NSF helper support enabled
Reference bandwidth unit is 100 mbps
Area BACKBONE(0)
Number of interfaces in this area is 2
Area has no authentication
SPF algorithm last executed 01:59:51.104 ago
SPF algorithm executed 12 times
Area ranges are
Number of LSA 5. Checksum Sum 0x01F6CD
Number of opaque link LSA 0. Checksum Sum 0x000000
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0
No comments:
Post a Comment