IOS XRv 9000

Overview

The IOS XRv 9000 image is a virtual router that runs the current Cisco IOS XR software. Cisco licenses this VM as a virtual router, but the VM runs in demo mode in CML without any additional licensing. Use the IOS XRv 9000 image in CML when you want to simulate a platform that runs IOS XR and have sufficient resources for the IOS XRv 9000 CPU and memory requirements.

For more details about IOS XRv 9000, refer to the following resources:

Limitations

IOS XRv 9000 is performance limited when forwarding traffic. Achieved throughputs are ~168 Kbits/sec when passing traffic through one IOS XRv 9000 device, and ~145 Kbits/sec when chained over two IOS XRv 9000 devices.

Features Tested with CML

Each CML release is tested with the bundled version of IOS XRv 9000. The tests validate the following features:

Test Name Result
L3 MPLS VPN PASS
L2 MPLS VPN PASS

The lab used for the tests is IOS XRv 9000 Feature Tests, which is one of the sample labs included with CML on the Tools > Sample Labs page.

IOS XRv 9000 Feature Test Topology

Specific XR 9000v tests:

  • L3 MPLS VPN
    • IS-IS (PE-P-P-P-PE routing)
    • MPLS (LDP)
    • VRF
    • mBGP (PE-PE routing, import/export routes to VRF)
    • OSPF (CE-PE routing)
  • L2 MPLS VPN
    • Point-to-point L2 VPN between CE routers

L3 MPLS VPN

  • L3 MPLS VPN created from one side of provider network to another
  • All components needed for L3 VPN are working (mBGP MPLS, VRFs, internal routing (IS-IS), CE-PE routing (OSPF) )
  • Verification: Customer on one side, can successfully ping his private network on the other side

IS-IS

  • Connectivity between all P and PE routers successfully established using IS-IS
  • Verification: ping from one PE to another
RP/0/RP0/CPU0:xr9kv-5#sh ip route
C    10.12.0.0/24 is directly connected, 1d19h, GigabitEthernet0/0/0/1
L    10.12.0.1/32 is directly connected, 1d19h, GigabitEthernet0/0/0/1
i L1 10.23.0.0/24 [115/20] via 10.12.0.2, 1d19h, GigabitEthernet0/0/0/1
i L1 10.34.0.0/24 [115/30] via 10.12.0.2, 1d19h, GigabitEthernet0/0/0/1
i L1 10.45.0.0/24 [115/40] via 10.12.0.2, 1d19h, GigabitEthernet0/0/0/1
L    10.255.255.1/32 is directly connected, 1d20h, Loopback0
i L1 10.255.255.2/32 [115/20] via 10.12.0.2, 1d19h, GigabitEthernet0/0/0/1
i L1 10.255.255.3/32 [115/30] via 10.12.0.2, 1d19h, GigabitEthernet0/0/0/1
i L1 10.255.255.4/32 [115/40] via 10.12.0.2, 1d19h, GigabitEthernet0/0/0/1
i L1 10.255.255.5/32 [115/50] via 10.12.0.2, 1d19h, GigabitEthernet0/0/0/1

MPLS

  • MPLS enabled on all interfaces inside of the provider network
  • Labels are successfully generated and distributed using LDP
  • Verification: traceroute from one PE to another shows that Label Switched Path is used
RP/0/RP0/CPU0:xr9kv-5#traceroute 10.255.255.5 source 10.255.255.1
Fri Aug  6 08:21:34.389 UTC

Type escape sequence to abort.
Tracing the route to 10.255.255.5

 1  10.12.0.2 [MPLS: Label 16204 Exp 0] 17 msec  12 msec  12 msec
 2  10.23.0.2 [MPLS: Label 16304 Exp 0] 15 msec  10 msec  12 msec
 3  10.34.0.2 [MPLS: Label 16404 Exp 0] 13 msec  9 msec  10 msec
 4  10.45.0.2 12 msec  *  11 msec

VRF

  • VRF instances for different customers created on PE routers
  • Interfaces connected to different CE routers assigned to different VRFs
  • Routes from different customers are not stored in global routing table but in VRF
RP/0/RP0/CPU0:xr9kv-4#show route vrf 101:Customer1
O    192.168.1.0/24 [110/2] via 192.168.101.2, 00:14:21, GigabitEthernet0/0/0/2
C    192.168.101.0/30 is directly connected, 01:19:06, GigabitEthernet0/0/0/2
L    192.168.101.1/32 is directly connected, 01:19:06, GigabitEthernet0/0/0/2

OSPF

  • OSPF used for CE-PE routing
  • Routes successfully exchanged between CE and PE
  • Routes are successfully added to VRF on PE router

mBGP

  • mBGP is configured to exchange VPNv4 routes between PE routers
  • Customer routes in VRF on PE router are advertised to another PE router and stored in correct VRF
RP/0/RP0/CPU0:xr9kv-4#show route vrf 101:Customer1

B    172.16.1.0/24 [200/2] via 10.255.255.1 (nexthop in vrf default), 00:03:59
B    172.16.101.0/30 [200/0] via 10.255.255.1 (nexthop in vrf default), 00:03:59
O    192.168.1.0/24 [110/2] via 192.168.101.2, 00:35:49, GigabitEthernet0/0/0/2
C    192.168.101.0/30 is directly connected, 01:40:34, GigabitEthernet0/0/0/2
L    192.168.101.1/32 is directly connected, 01:40:34, GigabitEthernet0/0/0/2

L2 MPLS VPN

  • Point-to-point L2 MPLS VPN configured between CE routers
RP/0/RP0/CPU0:xr9kv-5#show l2vpn xconnect
Wed Aug 11 07:54:27.182 UTC
Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,
        SB = Standby, SR = Standby Ready, (PP) = Partially Programmed,
        LU = Local Up, RU = Remote Up, CO = Connected

XConnect                   Segment 1                       Segment 2
Group      Name       ST   Description            ST       Description            ST
------------------------   -----------------------------   -----------------------------
P2P        xconnect   UP   Gi0/0/0/0              UP       10.255.255.5    2      UP
----------------------------------------------------------------------------------------
  • Interfaces on CE routers placed into same subnet
  • Ping from CE-CE is successfully
  • verification of L2 connectivity: CDP shows CE router to the other side as neighbor
csr1000v-0#show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
                  D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID        Local Intrfce     Holdtme    Capability  Platform  Port ID
csr1000v-1       Gig 1             47               R I   CSR1000V  Gig 1

Total cdp entries displayed : 1