IOS-XRv 9000 VRR v1

Cisco dCloud
Cisco IOS-XRv 9000 Virtual Route Reflector v1

Last Updated: 5 May 2015
About This Cisco Solution

Cisco IOS XRv 9000 is a High Performance IOS-XR virtual router. Known internally as Sunstone, it provides feature sets of the
IOS-XR operating system on a Virtualized x86 compute platform and can be deployed as a virtualized network function (VNF) in the
form of a route reflector.
For more information on IOS XRv 9000, visit the http://xrv.cisco.com
About This Demonstration

IMPORTANT: Please set your customer’s expectation correctly regarding the performance/convergence they will see in this demo.
This demo is running on dCloud, which hosts hundreds of other demos running concurrently, all of which are virtualized. What this
means is that there is a lot of contention of the physical CPU. Hence, performance and convergence is slower compared to running
these services on a dedicated CPU (using resource allocation or CPU pinning). Please make this clear when you show this to your
customers to avoid giving a false sense of Cisco IOS XRv performance.
This demonstration requires familiarity with BGP and Route Reflector operations. Use this demonstration to showcase the
capabilities of the IOS XRv 9000 as a Virtual Route Reflector. It is required that you go through the scenario in consecutive order.
 Scenario 1. vRR Peering with Non-client and Clients.
 Scenario 2. Add additional Non-client iBGP Peers to the vRR
 Scenario 3. Filtering the prefixes advertised to the RR Clients.
There are also two appendix sections attached to this demonstration:
 Appendix A. Various outputs from commands used throughout this demo
 Appendix B. Configurations used under different Scenarios in this demo
Demonstration Requirements
The table below outlines the requirements for this preconfigured demonstration.
Table 1. Demonstration Requirements
Required Optional
 Computer with Internet Access  Cisco AnyConnect
 Cisco.com login
Demonstration Configuration
This demonstration contains preconfigured users and components to illustrate the capabilities available to you within the VIRL
sandbox.
© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 1 of 20
All information needed to complete the access components is located in the Topology and Servers menus of your active
demonstration.
Topology Menu. Click on any server in the topology and a popup window will appear with available server options.
Servers Menu. Click on or next to any server name to display the available server options and credentials.
Demonstration Topology
GigabitEthernet0/0/0/0 on vRR is directly connected to eth1 of the CentOS VM that hosts the Routem (Route Emulator) application.
The Routem simulates 10 BGP speakers that each advertises the full 420K routes that were recorded from the Internet and another
10 BGP speakers that advertise 10 prefixes each. The logical topology is shown in Figure 2 below.
Figure 1. Physical Topology
Figure 2. Logical Topology
192.168.1.2
Table 1. Router ID
IOS XRv vRR Router: 192.168.1.2
Non-Clients Clients
Device Router ID Device Router ID
RR1 192.168.1.1 Client1 192.168.1.12
RR2 192.168.1.3 Client2 192.168.1.13
RR3 192.168.1.4 Client3 192.168.1.14
RR4 192.168.1.5 Client4 192.168.1.15
RR5 192.168.1.6 Client5 192.168.1.16
RR6 192.168.1.7 Client6 192.168.1.17
RR7 192.168.1.8 Client7 192.168.1.18
RR8 192.168.1.9 Client8 192.168.1.19
RR9 192.168.1.10 Client9 192.168.1.20
RR10 192.168.1.11 Client10 192.168.1.21
Demonstration Preparation
BEFORE DEMONSTRATING
We strongly recommend that you go through this process at least once, before presenting in front of a live audience. This will allow
you to become familiar with the structure of the document and the demonstration.
PREPARATION IS KEY TO A SUCCESSFUL CUSTOMER PRESENTATION.
Follow the steps below to schedule your demonstration and configure your demonstration environment.
1. Browse to dcloud.cisco.com and login with your Cisco.com credentials.
2. Schedule a demonstration [Show Me How].
3. Test your connection from the demonstration location before performing any demonstration scenario. [Show Me How]
4. Verify your demonstration has a status of Active under My Demonstrations on the My Dashboard page in the dCloud UI.
 It may take up to 30 minutes for your demonstration to become active.
5. Connect to the Demonstration, using one of the following two options:
 Using Cisco AnyConnect [Show Me How] ********RECOMMENDED METHOD********
o After connecting to the demonstration via AnyConnect, use your local RDP client to connect to workstation
located at 198.18.133.252.
 Using Cisco dCloud Remote Desktop client [Show Me How]
NOTE: If you are running RDP, it is highly recommended that you use HTML5 as the default client. [Show Me How].
TIP: If using the dCloud webRDP, you can make your RDP session screen larger. To resize, select the corners of the remote
desktop window and drag to the desired size. Right-click anywhere within the grey space of the remote desktop window and select
Reload.
6. Log into the workstation with the credentials: Administrator / C1sco12345
7. Once connected to the workstation, on the Windows Desktop launch both the sunstone putty (Terminal) session and the
routem putty Session by double-clicking the perspective icons.
8. Login to Sunstone (198.18.1.47) with the credentials: admin / cisco
9. At the router prompt RP/0/RP0/CPU0:IOS-XRv-9000_vRR#, replace the existing configuration with the vrr base
configuration located in the disk0:vrr_base.cfg. To do this, type the following commands:
RP/0/RP0/CPU0:IOS-XRv-9000_vRR#conf t
RP/0/RP0/CPU0:IOS-XRv-9000_vRR(config)#load disk0:vrr_base.cfg
Loading.
2068 bytes parsed in 1 sec (2065)bytes/sec
RP/0/RP0/CPU0:IOS-XRv-9000_vRR(config)#commit replace
This commit will replace or remove the entire running configuration. This
operation can be service affecting.
Do you wish to proceed? [no]: yes
RP/0/RP0/CPU0:IOS-XRv-9000_vRR(config)#
10. On the Routem Terminal (root@host1:~), start the routem function by typing the following commands
cd vrr_demo
./routem –f routem_demo_conf1
11. Check the status of BGP neighbors to verify convergence using the command:
show bgp summary
 You should have 11 neighbors up. One neighbor advertising 420,025 prefixes, and 10 neighbors advertising 10 prefixes
each.
NOTE: If the St/PfxRcd does not show 1 entry of 420,025 and 10 entries of 10, wait approximately 1 minute and repeat the
command.
12. Check that InQ and OutQ are zero, using the following command:
show bgp convergence
Logging into the Routem VM is not required. The Routem is pre-configured to accept BGP peers from the vRR. You would only
need to login to the Routem VM if the status of the BGP neighbors from the vRR are DOWN.
Scenario 1: vRR Peering with Non-client and Clients
In this scenario, we will have the vRR peer with 1 non-client iBGP neighbor and 10 client iBGP peers.
 The non-client (simulated by Routem) will advertise around 420K prefixes, which is replayed from a capture of the full
internet routing table that were recorded sometime in early 2013. The vRR then takes this and reflects to its 10 clients.
 Each client advertises 10 routes and the vRR reflects these routes to other clients. See Table 2.
Figure 3. Logical diagram of the vRR, non-client, and clients
192.168.1.
2
Table 2. Client Router ID and Advertised Routes
Device Router ID Advertised Routes
Client1 192.168.1.12 10 prefixes starting from 1.1.1.0/30
Demonstration Steps
1. On the IOS XRv vRR router node, show the relevant configurations (BGP, session group, address-family group, neighbor
group, route-policy, table-policy)
show run
show run router bgp
2. To show the state of the iBGP neighbors and number of routes received, use the following command:
show bgp summary (See sample output in Appendix A: Figure 6)
3. To show all the BGP prefixes received by the vRR, use the following command:
show bgp
 Type q to exit the output at any time
IMPORTANT: The output of this command is really long (~420K lines). Your terminal length should not be qset to 0 (no page
breaks) before executing this command. If you have not modified the terminal length, do not worry about this.
4. To show the amount of memory being used by BGP, use the following command:
monitor processes
 Type m to sort it from highest to lowest memory usage, then look for ‘bgp’. Note the amount of memory used.
 Type q to exit the output at any time
NOTE: The monitor process command displays the top 10 processes of CPU in descending order. This list updates constantly. In
scenario 1, BGP may not initially show as one of the top 10 processes consuming memory, so you may not notice it initially. If you
do not see it, you can choose to monitor the output for approximately one minute to see if it comes up, otherwise, simply move on.
5. To show what is being advertised to a client iBGP peer (choose from 192.168.1.[12-21]), use the following command:
show bgp advertised neighbor 192.168.1.12 summary (See sample output in Appendix A: Figure 7)
6. To show what is being advertised to the non-client iBGP peer, use the following command:
 You should have 100 prefixes advertised to this peer.
***THIS CONCLUDES SCENARIO 1: vRR Peering with Non-clients***
Scenario 2: Add additional Non-client iBGP Peers to the vRR
From Scenario 1, we have one non-client iBGP peer to the vRR. In this scenario, we will add an additional nine non-client peerings.
Each will advertise the full 420K Internet routing table to the vRR. On the vRR, it will then have a total of approximately 4.2M
prefixes across 10 paths.
Figure 4. Logical Diagram of vRR, 10 non-clients, and 10 clients
192.168.1.
2
Demonstration Steps
1. Configure additional iBGP neighbors as non-client (IP: 192.168.1.[3-11]), use the following configuration to configure a peer:
router bgp 65000

neighbor 192.168.1.3
use neighbor-group RR_NONCLIENT
!
 Repeat these commands for 192.168.1.[4-11]
13. Commit all changes using the command: commit
 Alternatively, you can load the configuration stored as disk0:vrr_scenario2.cfg
NOTE: For reference on how to load the configuration, please refer to step 9 in the Demonstration Preparation section.
 All the ~3.7M (9*420K) prefixes will be advertised by the Routem to the vRR. In the dCloud environment, this process takes
approximately three minutes for convergence.
NOTE: The convergence time of three minutes is specific to this setup in dCloud. It is due to the heavily used virtual environment
that leads to CPU contention among VMs. Average convergence time for most deployments should be significantly lower.
2. Check for convergence using the following commands: (response will be slow while convergence is happening):
show bgp summary (See sample output in Appendix A: Figure 9)
 It is converged when the vRR has received all 420,025 routes from each of the non-clients peers
show bgp convergence
3. After BGP is converged, show the current prefixes that vRR has received from all the iBGP peers (non-clients and clients):
show bgp
 Each prefix advertised from the non-clients should have 10 paths
4. Show the total memory that BGP is currently using with all ~4.2M prefixes in its RIB, by typing following command:
monitor processes
 Type ‘m’ to sort it from highest to lowest memory usage, then look for ‘bgp’. Type ‘q’ to exit from the ‘monitor process’
screen.
 Compare to the previous memory consumption by BGP when it was only receiving 420K prefixes versus the current 4.2M.
5. To show what is being advertised to a client iBGP peer (choose from 192.168.1.[12-21]), use the following command:
 show bgp advertised neighbor 192.168.1.12 summary (See sample output in Appendix A: Figure 10)
NOTE: The output of this command is really long (~420K lines). Make sure your terminal length is not set to 0 (no page breaks)
before executing this command. If you haven’t modified the terminal length, you shouldn’t worry about this.
***THIS CONCLUDES THE DEMO ACTIVITY FOR THIS SCENARIO***
Scenario 3: Filtering the prefixes advertised to the RR Clients
Consider this scenario: What if the RR Clients do not need the full internet routing table? It is possible to filter the prefixes that are
being reflected to the clients by the vRR.
 Create a prefix-list or prefix-set to filter only certain prefixes to be reflected to the clients
Figure 5. Filter the prefixes advertised by non-clients to reflect only certain prefixes to clients
192.168.1.2
Demonstration Steps
1. As shown in Scenario 1 and 2, the clients are currently receiving the full internet routing table from the vRR. To create a p refix-
list or a prefix-set, use the following configuration:
prefix-set ADV_SET
1.22.0.0/16 le 32
end-set
!
2. Use the newly configured prefix-set in a route-policy. Use the following configuration:
route-policy ADV_FILTER
if destination in ADV_SET then
pass
else
drop
endif
end-policy
!
3. Apply the route-policy into the Address-family-group configuration for the RR Clients. Use the following configuration:
router bgp 65000
af-group CLIENT address-family ipv4 unicast
route-policy ADV_FILTER out
!
!
14. Commit all changes using the command: commit
 Alternatively, for steps 1 through 3, you can load the configuration stored as disk0:vrr_scenario3.cfg.
NOTE: For reference on how to load the configuration, please refer to step 8.f.b in the Demonstration Preparation section.
4. The filter should take effect on all RR clients after committing the configurations. To show the effect of the filter, show w hat is
advertised to one of the clients (choose from 192.168.1.[12-21]) using the following command:
 The only prefixes that you should see are the 1.22.x.x.
5. The non-clients should still be getting the routes advertised by the clients. To show this, use the following command:
 show bgp advertised neighbor 192.168.1.1 summary
You can use other non-clients as well (choose from 192.168.1.[3-11]).
***THIS CONCLUDES THE DEMO ACTIVITY FOR THIS SCENARIO***
Appendix A. Various command outputs used in this demo
Figure 6. ‘show bgp summary’ output with the 1 non-client and 10 clients
RP/0/RP0/CPU0:IOS-XRv-9000_vRR#show bgp summary

Wed Apr 1 23:41:12.635 UTC
BGP router identifier 198.18.1.47, local AS number 65000
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0xe0000000 RD version: 421412
BGP main routing table version 421412
BGP scan interval 60 secs
BGP is operating in STANDALONE mode.
Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer

Speaker 421412 421412 421412 421412 421412 421412
Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd

192.168.1.1 0 65000 69699 36 421412 0 0 00:00:44 420025
192.168.1.12 0 65000 1572 71230 421412 0 0 00:00:44 10
192.168.1.13 0 65000 1572 71230 421412 0 0 00:00:44 10
192.168.1.14 0 65000 1572 71230 421412 0 0 00:00:44 10
192.168.1.15 0 65000 1572 71230 421412 0 0 00:00:44 10
192.168.1.16 0 65000 1572 71230 421412 0 0 00:00:44 10
192.168.1.17 0 65000 1572 71230 421412 0 0 00:00:44 10
192.168.1.18 0 65000 1572 71230 421412 0 0 00:00:44 10
192.168.1.19 0 65000 1572 71230 421412 0 0 00:00:44 10
192.168.1.20 0 65000 1572 71230 421412 0 0 00:00:44 10
192.168.1.21 0 65000 1572 71230 421412 0 0 00:00:44 10
Return to Scenario 1
Figure 7. show bgp advertised neighbor 192.168.1.12 summary
RP/0/RP0/CPU0:IOS-XRv-9000_vRR#show bgp advertised neighbor 192.168.1.12 summary

Thu Apr 2 00:12:07.346 UTC
Network Next Hop From AS Path
1.0.0.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 15169i
1.0.4.0/22 192.168.1.1 192.168.1.1 64555 65109 64530 109 701 4323 7545 7545
7545 7545 56203i
1.0.16.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2914 2519i
1.0.18.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2914 2519i
1.0.20.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2914 2519i
1.0.22.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2914 2519i
1.0.24.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2914 2519i
1.0.26.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 3320 2519i
1.0.28.0/22 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 3320 2519i
1.0.64.0/18 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2497 7670
18144i
1.0.128.0/17 192.168.1.1 192.168.1.1 64555 65109 64530 109 701 38040 9737i
1.0.128.0/18 192.168.1.1 192.168.1.1 64555 65109 64530 109 701 38040 9737i
1.0.129.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 701 38040 9737
23969i
1.0.192.0/18 192.168.1.1 192.168.1.1 64555 65109 64530 109 701 38040 9737i
1.1.1.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 15169i
1.1.1.0/30 198.18.1.47 192.168.1.12 i
1.1.1.4/30 198.18.1.47 192.168.1.12 i
1.1.1.8/30 198.18.1.47 192.168.1.12 i
1.1.1.12/30 198.18.1.47 192.168.1.12 i
1.1.1.16/30 198.18.1.47 192.168.1.12 i
1.1.1.20/30 198.18.1.47 192.168.1.12 i
1.1.1.24/30 198.18.1.47 192.168.1.12 i
<snipped>
Figure 8. ‘show bgp advertised neighbor 192.168.1.1 summary’

Thu Apr 2 00:25:02.101 UTC
1.1.1.0/30 192.168.1.12 192.168.1.12 i
1.1.1.4/30 192.168.1.12 192.168.1.12 i
1.1.1.8/30 192.168.1.12 192.168.1.12 i
1.1.1.12/30 192.168.1.12 192.168.1.12 i
1.1.1.16/30 192.168.1.12 192.168.1.12 i
1.1.1.20/30 192.168.1.12 192.168.1.12 i
1.1.1.24/30 192.168.1.12 192.168.1.12 i
1.1.1.28/30 192.168.1.12 192.168.1.12 i
1.1.1.32/30 192.168.1.12 192.168.1.12 i
1.1.1.36/30 192.168.1.12 192.168.1.12 i
1.1.2.0/30 192.168.1.13 192.168.1.13 i
1.1.2.4/30 192.168.1.13 192.168.1.13 i
1.1.2.8/30 192.168.1.13 192.168.1.13 i
1.1.2.12/30 192.168.1.13 192.168.1.13 i
1.1.2.16/30 192.168.1.13 192.168.1.13 i
1.1.2.20/30 192.168.1.13 192.168.1.13 i
1.1.2.24/30 192.168.1.13 192.168.1.13 i
1.1.2.28/30 192.168.1.13 192.168.1.13 i
1.1.2.32/30 192.168.1.13 192.168.1.13 i
1.1.2.36/30 192.168.1.13 192.168.1.13 i
1.1.3.0/30 192.168.1.14 192.168.1.14 i
1.1.3.4/30 192.168.1.14 192.168.1.14 i
<snipped>
Figure 9. ‘show bgp summary’
RP/0/RP0/CPU0:IOS-XRv-9000_vRR#show bgp summary

Thu Apr 2 00:11:10.496 UTC
BGP router identifier 198.18.1.47, local AS number 65000
BGP generic scan interval 60 secs
BGP table state: Active
Table ID: 0xe0000000 RD version: 4202433
BGP main routing table version 4202433
BGP scan interval 60 secs
BGP is operating in STANDALONE mode.
Process RcvTblVer bRIB/RIB LabelVer ImportVer SendTblVer StandbyVer

Speaker 4202433 4202433 4202433 4202433 4202433 4202433
Neighbor Spk AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down St/PfxRcd
192.168.1.1 0 65000 69729 66 4202433 0 0 00:30:42 420025
192.168.1.3 0 65000 69686 13 4202433 0 0 00:00:53 420025
192.168.1.4 0 65000 69686 13 4202433 0 0 00:00:53 420025
192.168.1.5 0 65000 69686 13 4202433 0 0 00:00:53 420025
192.168.1.6 0 65000 69686 13 4202433 0 0 00:00:53 420025
192.168.1.7 0 65000 69686 13 4202433 0 0 00:00:53 420025
192.168.1.8 0 65000 69686 13 4202433 0 0 00:00:53 420025
192.168.1.9 0 65000 69686 13 4202433 0 0 00:00:53 420025
192.168.1.10 0 65000 69686 13 4202433 0 0 00:00:53 420025
192.168.1.11 0 65000 69686 13 4202433 0 0 00:00:53 420025
192.168.1.12 0 65000 1602 140785 4202433 0 0 00:30:42 10
192.168.1.13 0 65000 1602 140785 4202433 0 0 00:30:42 10
192.168.1.14 0 65000 1602 140785 4202433 0 0 00:30:42 10
192.168.1.15 0 65000 1602 140785 4202433 0 0 00:30:42 10
192.168.1.16 0 65000 1602 140785 4202433 0 0 00:30:42 10
192.168.1.17 0 65000 1602 140785 4202433 0 0 00:30:42 10
192.168.1.18 0 65000 1602 140785 4202433 0 0 00:30:42 10
192.168.1.19 0 65000 1602 140785 4202433 0 0 00:30:42 10
192.168.1.20 0 65000 1602 140785 4202433 0 0 00:30:42 10
192.168.1.21 0 65000 1602 140785 4202433 0 0 00:30:42 10
Figure 10. ‘show bgp advertised neighbor 192.168.1.12 summary’ without filter

Thu Apr 2 00:12:07.346 UTC
1.0.0.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 15169i
1.0.4.0/22 192.168.1.1 192.168.1.1 64555 65109 64530 109 701 4323 7545 7545
7545 7545 56203i
1.0.16.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2914 2519i
1.0.18.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2914 2519i
1.0.20.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2914 2519i
1.0.22.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2914 2519i
1.0.24.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2914 2519i
1.0.26.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 3320 2519i
1.0.28.0/22 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 3320 2519i
1.0.64.0/18 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 2497 7670
18144i
1.0.128.0/17 192.168.1.1 192.168.1.1 64555 65109 64530 109 701 38040 9737i
1.0.128.0/18 192.168.1.1 192.168.1.1 64555 65109 64530 109 701 38040 9737i
1.0.129.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 701 38040 9737
23969i
1.0.192.0/18 192.168.1.1 192.168.1.1 64555 65109 64530 109 701 38040 9737i
1.1.1.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 15169i
1.1.1.0/30 198.18.1.47 192.168.1.12 i
1.1.1.4/30 198.18.1.47 192.168.1.12 i
1.1.1.8/30 198.18.1.47 192.168.1.12 i
1.1.1.12/30 198.18.1.47 192.168.1.12 i
1.1.1.16/30 198.18.1.47 192.168.1.12 i
1.1.1.20/30 198.18.1.47 192.168.1.12 i
1.1.1.24/30 198.18.1.47 192.168.1.12 i
<snipped>
Figure 11. ‘show bgp advertised neighbor 192.168.1.12 summary’ after applying the filter

Thu Apr 2 00:23:49.068 UTC
1.22.6.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.10.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.10.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 3356 55410 45528i
1.22.11.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.12.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.12.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.14.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.14.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 3356 55410 45528i
1.22.15.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.16.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.18.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.24.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.24.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.25.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.27.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.30.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.31.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 3356 55410 45528i
1.22.36.0/23 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.36.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.37.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 6453 4755 45528i
1.22.40.0/22 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 3356 55410 45528i
1.22.40.0/24 192.168.1.1 192.168.1.1 64555 65109 64530 109 1239 3356 55410 45528i
<Snipped>
Appendix B. Configurations used in each Scenarios in this demo
Figure 12. Base Configuration – disk0:vrr_base.cfg
hostname IOS-XRv-9000_vRR router bgp 65000
bgp router-id 198.18.1.47

service timestamps log datetime msec
address-family ipv4 unicast
service timestamps debug datetime msec
table-policy DROP
telnet vrf default ipv4 server max-server 10
!
domain lookup disable
af-group NONCLIENT address-family ipv4 unicast
line console
maximum-prefix 4294967295 75
exec-timeout 0 0 soft-reconfiguration inbound always
! !
line default af-group CLIENT address-family ipv4 unicast
exec-timeout 720 0 route-reflector-client
! maximum-prefix 4294967295 75
soft-reconfiguration inbound always

interface Loopback0
!
ipv4 address 10.1.1.2 255.255.255.255
session-group MY_AS
!
remote-as 65000
interface MgmtEth0/0/CPU0/0
!
shutdown
neighbor-group RR_NONCLIENT
! use session-group MY_AS
interface GigabitEthernet0/0/0/0 address-family ipv4 unicast
description to CentOS Routem use af-group NONCLIENT
ipv4 address 198.18.1.47 255.255.255.0 !

!
no shutdown
neighbor-group RR_CLIENT
!
use session-group MY_AS
route-policy DROP
address-family ipv4 unicast
drop
use af-group CLIENT
end-policy
!
!
neighbor 192.168.1.12
use neighbor-group RR_CLIENT
!
neighbor 192.168.1.13
!
neighbor 192.168.1.14
!
neighbor 192.168.1.15
!
neighbor 192.168.1.16
!
neighbor 192.168.1.17
!
neighbor 192.168.1.18
!
neighbor 192.168.1.19
!
neighbor 192.168.1.20
!
neighbor 192.168.1.21
!
!
Figure 13. Incremental Configuration for Scenario2 – disk0:vrr_scenario2.cfg
router bgp 65000

!
!
!
!
!
!
!
neighbor 192.168.1.10
!
neighbor 192.168.1.11
!
!
Figure 14. Incremental Configuration for Scenario3 – disk0:vrr_scenario3.cfg
prefix-set ADV_SET
1.22.0.0/16 le 32
end-set
!
route-policy ADV_FILTER
if destination in ADV_SET then
pass
else
drop
endif
end-policy
!
router bgp 65000
af-group CLIENT address-family ipv4 unicast
route-policy ADV_FILTER out
!

IOS-XRv 9000 VRR v1

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

IOS-XRv 9000 VRR v1

Caricato da

Copyright:

Formati disponibili

Cisco dCloud

Cisco IOS-XRv 9000 Virtual Route Reflector v1

About This Cisco Solution

For more information on IOS XRv 9000, visit the http://xrv.cisco.com

About This Demonstration

 Scenario 1. vRR Peering with Non-client and Clients.

 Scenario 2. Add additional Non-client iBGP Peers to the vRR

 Scenario 3. Filtering the prefixes advertised to the RR Clients.

There are also two appendix sections attached to this demonstration:

 Appendix A. Various outputs from commands used throughout this demo

 Appendix B. Configurations used under different Scenarios in this demo

Table 1. Demonstration Requirements

Figure 1. Physical Topology

Figure 2. Logical Topology

IOS XRv vRR Router: 192.168.1.2

Device Router ID Device Router ID

RR1 192.168.1.1 Client1 192.168.1.12

RR2 192.168.1.3 Client2 192.168.1.13

RR3 192.168.1.4 Client3 192.168.1.14

RR4 192.168.1.5 Client4 192.168.1.15

RR5 192.168.1.6 Client5 192.168.1.16

RR6 192.168.1.7 Client6 192.168.1.17

RR7 192.168.1.8 Client7 192.168.1.18

RR8 192.168.1.9 Client8 192.168.1.19

RR9 192.168.1.10 Client9 192.168.1.20

RR10 192.168.1.11 Client10 192.168.1.21

PREPARATION IS KEY TO A SUCCESSFUL CUSTOMER PRESENTATION.

1. Browse to dcloud.cisco.com and login with your Cisco.com credentials.

2. Schedule a demonstration [Show Me How].

 It may take up to 30 minutes for your demonstration to become active.

5. Connect to the Demonstration, using one of the following two options:

 Using Cisco AnyConnect [Show Me How] ********RECOMMENDED METHOD********

 Using Cisco dCloud Remote Desktop client [Show Me How]

6. Log into the workstation with the credentials: Administrator / C1sco12345

8. Login to Sunstone (198.18.1.47) with the credentials: admin / cisco

show bgp summary

show bgp convergence

Figure 3. Logical diagram of the vRR, non-client, and clients

Table 2. Client Router ID and Advertised Routes

Device Router ID Advertised Routes

Client1 192.168.1.12 10 prefixes starting from 1.1.1.0/30

Client2 192.168.1.13 10 prefixes starting from 1.1.2.0/30

Client3 192.168.1.14 10 prefixes starting from 1.1.3.0/30

Client4 192.168.1.15 10 prefixes starting from 1.1.4.0/30

Client5 192.168.1.16 10 prefixes starting from 1.1.5.0/30

Client6 192.168.1.17 10 prefixes starting from 1.1.6.0/30

Client7 192.168.1.18 10 prefixes starting from 1.1.7.0/30

Client8 192.168.1.19 10 prefixes starting from 1.1.8.0/30

Client9 192.168.1.20 10 prefixes starting from 1.1.9.0/30

Client10 192.168.1.21 10 prefixes starting from 1.1.10.0/30

show bgp summary (See sample output in Appendix A: Figure 6)

 Type q to exit the output at any time

 Type q to exit the output at any time

 You should have 100 prefixes advertised to this peer.

***THIS CONCLUDES SCENARIO 1: vRR Peering with Non-clients***

router bgp 65000

 Repeat these commands for 192.168.1.[4-11]

13. Commit all changes using the command: commit

 Alternatively, you can load the configuration stored as disk0:vrr_scenario2.cfg

show bgp summary (See sample output in Appendix A: Figure 9)

show bgp convergence

 Each prefix advertised from the non-clients should have 10 paths

***THIS CONCLUDES THE DEMO ACTIVITY FOR THIS SCENARIO***

 Using Cisco AnyConnect [Show Me How] RECOMMENDED METHOD

THIS CONCLUDES SCENARIO 1: vRR Peering with Non-clients

THIS CONCLUDES THE DEMO ACTIVITY FOR THIS SCENARIO

THIS CONCLUDES THE DEMO ACTIVITY FOR THIS SCENARIO