FCE Multicast

Adam Allen IN CONFIDENCE Jan 2009

FCE Multicast
CORE DESIGN

Multicast vs Unicast
Multicast has been a significant development on BT MPLS. There are two flavours of Multicast:
Intranet between sites of a common customer Extranet Provider/Member model

Multicast Traffic is not label switched across the core network.

However VPNs are still used to control reach ability of Multicast Sources and RPs

Access to the Multicast service needs to be provisioned on the PE router giving strong Service Level Entitlement. Start Simple
1 Multicast Provider in the network providing 1 Multicast Service with 1 Multicast Group
British Telecommunications plc

Default - Multicast Distribution Tree

The provider is allocated a Default MDT address (239.232.56.1), configured against the London PE
RR P PE

CE1-LFA

As clients subscribe to the multicast service P the Default MDT is extended to the client serving PE routers.
P P

239.232.56.1

PE

CE1-NYK CE2-NYK
British Telecommunications plc

CE

CE1-HKK

The MDT addresses are controlled by BT and are not visible or connected to the customer. The default MDT is always active.

Transport VRFs
The mechanism by which Default MDTs are extended to PE routers are by the configuration of Transport VRFs The Transport VRF is configured on an egress client PE router and is associated with the Default MDT
The Tranposrt VRF is shared by all customers on that PE router who subscribe to the Multicast service.

ip vrf fe-ctv-adammcast-1 rd 12641:3824211 mdt default 239.232.56.1 mdt data 232.232.156.4 0.0.0.0 threshold 1
British Telecommunications plc

Data - Multicast Distribution Tree

Initially Multicast traffic is sent via the Default MDT until the traffic rate crosses the CE1-LFA threshold (1Kbits).
RR P PE

239.232.56.1 239.232.156.4
P

PE

CE1-NYK CE2-NYK
British Telecommunications plc

CE

CE1-HKK

Then a Data MDT (239.2323.156.4) will dynamically created to carry traffic to the interested PEs. Traffic remains on the Default MDT for 13 seconds after the Data MDT is created.

C packets / P packets
Source 155.0.0.2 Destination 224.31.1.1

RR P

PE

GRE Packet
P

239.232.56.1 Source 239.232.156.4 155.0.0.2

P

Destination 224.31.1.1 Source 212.31.220.44 Destination 239.232.156.4

PE

GRE Packet Source 155.0.0.2 Destination 224.31.1.1 Source 212.31.220.44 Destination 239.232.156.4

CE

Source 155.0.0.2 Destination 224.31.1.1

British Telecommunications plc

Extranet Functionality
Transport VRF CE1-LFA ip vrf fe-ctv-adammcast-1 rd 12641:3824211 RR PE P mdt default 239.232.56.1 mdt data 232.232.156.4 0.0.0.0 threshold 1 Client Client 1s VRF 239.232.56.1 2s VRF P ip vrf ex-finance-126414 ip vrf ex-finance-126415 239.232.156.4 rd 12641:5 rd 12641:4
P P PE

CE1-NYK
Service 3

CE

CE2-NYK
Service 3

British Telecommunications plc

CE1-HKK
Service 3

Multicast Extranet is a recent feature development on the PE router to allow a single Transport VRF to be shared by multiple customers on the same PE router.

Extranet
ip multicast vrf ex-finance-126414 rpf select vrf fe-ctv-adammcast-mtv1 grouplist ACL-FE-mcast-adammcast_1 The rpf select command creates a link between the client VRF and the Transport VRF when accessing the multicast groups defined in the ACL
ACL-FE-mcast-adammcast_1 224.31.1.1

Only customers subscribing to this multicast service will have the rpf select command configured.
British Telecommunications plc

Transport VPN Mapping.

Service 1
232.31.1.1 232.31.1.2

Transport VPN 1
groups 232.31.1.1 default mdt 239.232.56.1 data mdt 239.232.156.4

Transport VPN 2 Service 2

232.31.1.1 232.31.1.4 groups 232.31.1.4 default mdt 239.232.56.2 data mdt 239.232.156.5

Service 3
232.31.1.1

Transport VPN 3
groups 232.31.1.2 default mdt 239.232.56.3 data mdt 239.232.156.6

Transport VPN Mapping is a trade-off between core-state and corebandwidth. If the Multicast-group 232.31.1.1 supports a high bandwidth feed this could be carried multiple times across the core network. The solution for this situation is to create 3 Transport VPNs for this provider.
The previous examples show Service 3
British Telecommunications plc

Transport VPNs
CE1-LFA
Traffic associated with 232.31.1.1 is only transported to PE1-NYK once.
P RR P PE

239.232.156.5 239.232.56.2 239.232.56.1 239.232.156.4

P

PE

Traffic associated with 232.31.1.4 will never head to Hong Kong as no clients subscribe to Service 2 In this example CE1 has subscribed to Service 3. and CE2 has subscribed to 3, Service 2. CE1-HKK
Service 3

CE1-NYK
Service 3

CE

CE2-NYK
Service 2

British Telecommunications plc

RP

RP 155.155.155.1

CE1-LFA
RR P PE

239.232.56.1 239.232.156.4
P

PE

CE1-NYK
Service 3

CE

Head-end CEs router are configured to act as a Rendevouz Point. The RP is configured as an Anycast RP CE1-HKK

British Telecommunications plc

RP
ip pim vrf ex-finance-126414 rp-address 155.155.155.1 ACL-FE-mCast-Groups

The Anycast RP is configured for each VRF on the client PE router.

ACL-FE-mCast-Groups matches the aggregated set of FCE group addresses.
ip pim vrf fe-ctv-adammcast-mtv1 rp-address 155.155.155.1 ACL-FE-mCast_adammcast

The Transport VRF is configured to maps its own Multicast groups to the Anycast RP Routing to the RP and Source is provided by importing a per-serviceRP-RT and per-service-Source-RT
British Telecommunications plc

Live-Live
CE1-LFA
RR P239.232.156.9 PE

239.232.56.8 239.232.56.6 239.232.156.7

P

PE

Feed-A and Feed-B will map to different Transport VPNs. Feed-A and Feed-B will map to different RP addresses.

CE1-NYK
Service 4

CE

CE2-NUT
Service 4

British Telecommunications plc

FCE Multicast
CLIENT DESIGN

 British Telecommunications plc

Service/VLAN mapping

VLAN 180

VLAN 170

Multicast Services are associated with specific VLANs

Unlike Unicast this extends to the configuration (SLE ACL, IGMP Static-group statements) Services are only available via the VLANs they have been ordered by Services may be delivered via the Generic FE VLAN (170) or via separate VLANs
British Telecommunications plc

BT Managed Switch VLANS

In addition to the list of VLANs presented earlier as part of the FCE High Level Design additional VLANs are available. The following VLANs do not have default port allocations All are allocated over the ISL.
SPARE VLANs VLANs 220 - 235 VLANs 237 - 249 ThomsonOne VLAN 210 Instinet VLAN 110 State Street VLAN 120 Comstock VLAN 236
British Telecommunications plc

Always On

Interface GigabitEthernet0/0.170 ip igmp static-group 224.31.1.1

VLAN 170

By default all Multicast Groups the customer has subscribed to will be explicitly configured on the client CE router However it is possible for the customers to order the service without static IGMP joins.
In this case the customer will either send IGMP joins or speak PIM in order to control the Multicast service. DR Priority can be modified on the MPLS CEs
Default 200 Primary / 100 Secondary
British Telecommunications plc

SLE

VLAN 170

The CE router has a set of ACLs configured which provide a mapping between the groups to RP
The groups listed in the ACL are the groups which the customer has subscribed to. PIM/IGMP Joins received for groups not listed in the ACL will be marked invalid.

Service Level Entitlements are also enforced at the PE router.

British Telecommunications plc

PIM

VLAN 180

VLAN 170

Upto 10 PIM Talkers can be specified on the customer LAN. The PIM talkers will be configured into an PIM Boundary ACL. PIM neighbourships are established over the ICRL link if provided. Ordering PIM requires the use of Customer LAN Routing.
RIP is selected by default The RP address is redistributed into the Customer LAN Routing
British Telecommunications plc

Live Live
A B

VLAN 170

Live-Live is carried out by using separate S,G pairs for the A-Feed (Red) and the B-Feed (Blue) Live-Live services use a different RP to Live-Standby services. Where a customer is not a pim talker/using static joins the intial joins for the B-Feed will be directed to the Designated Router
British Telecommunications plc

The PIM join redirects to the secondary router The Traffic flow does not converge

SSM
Source Specific Multicast is supported with the BT MPLS network designs. Where the service is not configured as an Always On service.
IGMP Version 2 does not allow the source address to be specified. IGMP Version 3 or PIM needs to be used

British Telecommunications plc

UDP Broadcast/Multicast Conversion

Broadcast Multicast conversion allows for providers to send UDP broadcast traffic at the head-end. The Head-end CE router converts the traffic to a Multicast Feed before sending into the BT MPLS network. At the Member CE router the traffic is re-converted back to UDP traffic before broadcasting on the LAN

British Telecommunications plc