Topology:
Use configuration from L3VPN task #11 as initial configuration for this task.
Requirements:
Change the configuration from the previous task to comply with the new requirements.
1. AS 23 shall not rely on rendezvous point for forwarding Customer A multicast traffic.
2. When possible, optimize the use of AS23 backbone, by only delivering Customer A multicast traffic to PE routers, when attached Customer site is subscribed to the multicast stream.
Solution:
Highlight the text below to reveal the solution.
This task requires understanding of PIM SSM and MVPN MDT default and MDT data groups, distributing the MDT information using IPv4 MDT address-family.
Requirement #1 - configure PIM-SSM in AS23, and reconfigure the MDT default and data to use SSM groups.
Requirement #2 - configure MDT data with minimal threshold. This will cause the switchover of high throughput multicast streams to data MDT, which is only delivered to PEs that subscribe to the specific data group (vs default MDT which is delivered to all PEs).
!
vrf definition CUST_A
rd 100:100
route-target export 100:100
route-target import 100:100
!
address-family ipv4
mdt default 232.0.0.1
mdt data 232.0.1.0 0.0.0.255 threshold 1
exit-address-family
!
!
vrf definition CUST_A
rd 100:100
route-target export 100:100
route-target import 100:100
!
address-family ipv4
mdt default 232.0.0.1
mdt data 232.0.1.0 0.0.0.255
exit-address-family
!
router bgp 23
bgp cluster-id 23.0.3.3
address-family vpnv4 unicast
!
address-family ipv4 mdt
!
neighbor-group CLIENTS
remote-as 23
update-source Loopback0
address-family vpnv4 unicast
route-reflector-client
!
address-family ipv4 mdt
route-reflector-client
!
!
neighbor 23.0.1.1
use neighbor-group CLIENTS
!
neighbor 23.0.2.2
use neighbor-group CLIENTS
!
neighbor 23.0.4.4
use neighbor-group CLIENTS
!
neighbor 23.0.5.5
remote-as 23
update-source Loopback0
address-family vpnv4 unicast
!
!
!
!
router bgp 23
address-family vpnv4 unicast
!
address-family ipv4 mdt
!
neighbor 23.0.3.3
remote-as 23
update-source Loopback0
address-family vpnv4 unicast
!
address-family ipv4 mdt
!
!
neighbor 23.0.5.5
remote-as 23
update-source Loopback0
address-family vpnv4 unicast
!
address-family ipv4 mdt
!
!
vrf CUST_A
rd 100:100
address-family ipv4 unicast
redistribute connected
redistribute static
!
!
!
multicast-routing
address-family ipv4
mdt source Loopback0
interface all enable
!
vrf CUST_A
address-family ipv4
interface all enable
mdt default ipv4 232.0.0.1
mdt data 232.0.1.0/24
!
!
!
router bgp 23
bgp cluster-id 23.0.5.5
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor CLIENTS peer-group
neighbor CLIENTS remote-as 23
neighbor CLIENTS update-source Loopback0
neighbor 23.0.1.1 peer-group CLIENTS
neighbor 23.0.2.2 peer-group CLIENTS
neighbor 23.0.3.3 remote-as 23
neighbor 23.0.3.3 update-source Loopback0
neighbor 23.0.4.4 peer-group CLIENTS
!
address-family ipv4
exit-address-family
!
address-family vpnv4
neighbor CLIENTS send-community both
neighbor CLIENTS route-reflector-client
neighbor 23.0.1.1 activate
neighbor 23.0.2.2 activate
neighbor 23.0.3.3 activate
neighbor 23.0.3.3 send-community both
neighbor 23.0.4.4 activate
exit-address-family
!
address-family ipv4 mdt
neighbor CLIENTS send-community both
neighbor CLIENTS route-reflector-client
neighbor 23.0.1.1 activate
neighbor 23.0.2.2 activate
neighbor 23.0.4.4 activate
exit-address-family
This task requires understanding of PIM SSM and MVPN MDT default and MDT data groups, distributing the MDT information using IPv4 MDT address-family.
Requirement #1 - configure PIM-SSM in AS23, and reconfigure the MDT default and data to use SSM groups.
Requirement #2 - configure MDT data with minimal threshold. This will cause the switchover of high throughput multicast streams to data MDT, which is only delivered to PEs that subscribe to the specific data group (vs default MDT which is delivered to all PEs).
R1:
!
vrf definition CUST_A
rd 100:100
route-target export 100:100
route-target import 100:100
!
address-family ipv4
mdt default 232.0.0.1
mdt data 232.0.1.0 0.0.0.255 threshold 1
exit-address-family
!
!
router bgp 23
bgp log-Neighbor-changes
no bgp default ipv4-unicast
neighbor 23.0.3.3 remote-as 23
neighbor 23.0.3.3 update-source Loopback0
neighbor 23.0.5.5 remote-as 23
neighbor 23.0.5.5 update-source Loopback0
!
address-family ipv4
exit-address-family
!
address-family vpnv4
neighbor 23.0.3.3 activate
neighbor 23.0.3.3 send-community both
neighbor 23.0.5.5 activate
neighbor 23.0.5.5 send-community both
exit-address-family
!
address-family ipv4 mdt
neighbor 23.0.3.3 activate
neighbor 23.0.3.3 send-community both
neighbor 23.0.5.5 activate
neighbor 23.0.5.5 send-community both
exit-address-family
!
address-family ipv4 vrf CUST_A
redistribute connected
redistribute static
exit-address-family
!
ip pim ssm default
!
R2:
!
vrf definition CUST_A
rd 100:100
route-target export 100:100
route-target import 100:100
!
address-family ipv4
mdt default 232.0.0.1
mdt data 232.0.1.0 0.0.0.255
exit-address-family
!
!
router bgp 23
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor 23.0.3.3 remote-as 23
neighbor 23.0.3.3 update-source Loopback0
neighbor 23.0.5.5 remote-as 23
neighbor 23.0.5.5 update-source Loopback0
!
address-family ipv4
exit-address-family
!
address-family vpnv4
neighbor 23.0.3.3 activate
neighbor 23.0.3.3 send-community both
neighbor 23.0.5.5 activate
neighbor 23.0.5.5 send-community both
exit-address-family
!
address-family ipv4 mdt
neighbor 23.0.3.3 activate
neighbor 23.0.3.3 send-community both
neighbor 23.0.5.5 activate
neighbor 23.0.5.5 send-community both
exit-address-family
!
address-family ipv4 vrf CUST_A
redistribute connected
redistribute static
exit-address-family
!
ip pim ssm default
!
R3:
router bgp 23
bgp cluster-id 23.0.3.3
address-family vpnv4 unicast
!
address-family ipv4 mdt
!
neighbor-group CLIENTS
remote-as 23
update-source Loopback0
address-family vpnv4 unicast
route-reflector-client
!
address-family ipv4 mdt
route-reflector-client
!
!
neighbor 23.0.1.1
use neighbor-group CLIENTS
!
neighbor 23.0.2.2
use neighbor-group CLIENTS
!
neighbor 23.0.4.4
use neighbor-group CLIENTS
!
neighbor 23.0.5.5
remote-as 23
update-source Loopback0
address-family vpnv4 unicast
!
!
!
R4:
!
router bgp 23
address-family vpnv4 unicast
!
address-family ipv4 mdt
!
neighbor 23.0.3.3
remote-as 23
update-source Loopback0
address-family vpnv4 unicast
!
address-family ipv4 mdt
!
!
neighbor 23.0.5.5
remote-as 23
update-source Loopback0
address-family vpnv4 unicast
!
address-family ipv4 mdt
!
!
vrf CUST_A
rd 100:100
address-family ipv4 unicast
redistribute connected
redistribute static
!
!
!
multicast-routing
address-family ipv4
mdt source Loopback0
interface all enable
!
vrf CUST_A
address-family ipv4
interface all enable
mdt default ipv4 232.0.0.1
mdt data 232.0.1.0/24
!
!
!
R5:
router bgp 23
bgp cluster-id 23.0.5.5
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor CLIENTS peer-group
neighbor CLIENTS remote-as 23
neighbor CLIENTS update-source Loopback0
neighbor 23.0.1.1 peer-group CLIENTS
neighbor 23.0.2.2 peer-group CLIENTS
neighbor 23.0.3.3 remote-as 23
neighbor 23.0.3.3 update-source Loopback0
neighbor 23.0.4.4 peer-group CLIENTS
!
address-family ipv4
exit-address-family
!
address-family vpnv4
neighbor CLIENTS send-community both
neighbor CLIENTS route-reflector-client
neighbor 23.0.1.1 activate
neighbor 23.0.2.2 activate
neighbor 23.0.3.3 activate
neighbor 23.0.3.3 send-community both
neighbor 23.0.4.4 activate
exit-address-family
!
address-family ipv4 mdt
neighbor CLIENTS send-community both
neighbor CLIENTS route-reflector-client
neighbor 23.0.1.1 activate
neighbor 23.0.2.2 activate
neighbor 23.0.4.4 activate
exit-address-family
Verification:
Note: in order to case the switchover from default to data mdt, you need to generate a high bandwidth stream. If using ICMP, time "timeout 0".
