Você está na página 1de 3

InformaCast Paging over MPLS

Overview

Traditionally, getting muticast to work over MPLS is difficult. The common workaround is GRE Tunneling. This allows us to encapsulate Multicast traffic inside of a GRE header and transport it through the MPLS network as standard unicast IP.

For the InformaCast customer below, a GRE tunnel has been configured between the Dallas and Houston locations. The GRE Tunnel terminates on the Dallas 2911 CPE Interface (10.251.29.2) and the Houston 3750 MPLS CPE Interface (10.249.1.2)

GRE Tunneled Networks

MCAST TX-H2W Voice Vlan InformaCast 10.1.29.128/25 Multicast Group Address 239.0.1.2 MPLS Gig0/1 Gig1/0/20 2911
MCAST
TX-H2W Voice Vlan
InformaCast
10.1.29.128/25
Multicast Group Address
239.0.1.2
MPLS
Gig0/1
Gig1/0/20
2911
3750
10.251.29.2
10.249.1.2
GRE Tunne
l Interfaces
TX-DAL
TX-HOU
I
n f o r m a C a s t

Vlan 3

Gig0/0.2

10.1.29.129/25

10.1.2.1/24

10.1.2.55

Configuration

At a high level, we configure GRE between the MPLS CPE routers and PIM enable any interfaces which require an mcast audio stream. In our case, this requires enabling PIM on the Dallas Voice Vlan and the Houston Voice Server Vlan. To ensure multicast routes across the GRE interface, we will add static mroutes for the respective subnets.

Dallas to Houston Multicast Tunnel Config Notes Dallas GRE Tunnel Interface: 10.251.29.2 Houston GRE Tunnel Interface:10.249.1.2 Houston PIM Rendezvous Point: 10.1.2.1 Houston InformaCast Server: 10.1.2.55 Houston InformaCast Group Address: 239.0.1.2

Houston 3750 ip multicast-routing distributed ip pim rp-address 10.1.2.1 ! Statically configure the Houston 3750 as the PIM rendezvous point. PIM uses RP’s to connect sources and receivers.

!

interface Tunnel0 description Tunnel to Dallas ip unnumbered GigabitEthernet1/0/20

ip pim dr-priority 255 ip pim sparse-mode tunnel source GigabitEthernet1/0/20 tunnel destination 10.251.29.2

!

ip mroute 10.1.29.128 255.255.255.128 Tunnel0

!

Static Mroute to the Dallas Voice Vlan

!

int vl 2 desc Voice Vlan ip add 10.1.29.1 255.255.255.0 ip pim sparse-mode

Dallas 2911 ip multicast-routing ip pim rp-address 10.1.2.1

!

Statically configure the Houston 3750 as the PIM rendezvous point.

!

interface Tunnel0 description Tunnel to Houston ip unnumbered GigabitEthernet0/1 ip pim sparse-mode tunnel source GigabitEthernet0/1 tunnel destination 10.249.1.2

!

int gig 0/0.2

desc voice server vlan ip add 10.1.29.129 255.255.255.128 ip pim sparse-mode

!

ip mroute 10.1.2.0 255.255.255.0 Tunnel 0

! Static Mroute to the Houston Voice Server Vlan

TX-DAL-2911#show ip pim int

10.1.29.129

GigabitEthernet0/0.2 v2/S 0 30 1 10.1.29.129

10.251.29.2

Tunnel0 v2/S 1 30 1 0.0.0.0

! PIM Configured on Dallas voice vlan and GRE tunnel

TX-DAL-2911#show ip pim neigh PIM Neighbor Table 10.249.1.2 Tunnel0 00:02:39/00:01:31 v2 255/ S P G

! Houston Corp 3750 joined as PIM Neighbor to Dallas 2911

TX-DAL-2911#show ip rpf 10.1.2.55 RPF information for (10.1.2.55) RPF interface: Tunnel0 RPF neighbor: (10.249.1.2) RPF route/mask: 10.1.2.0/24 RPF type: multicast (static) Doing distance-preferred lookups across tables RPF topology: ipv4 multicast base

! Houston InformaCast Server passes Reverse Path Forwarding (RPF) check

TX-DAL-2911#ping 239.0.1.2 source gig0/0.2 Sending 1, 100-byte ICMP Echos to 239.0.1.2, timeout is 2 seconds:

Packet sent with a source address of 10.1.29.129 Reply to request 0 from 10.249.1.2, 12 ms

! Successful test ping from Dallas Voice Vlan at 10.1.29.129 to the InformaCast Multicast Group at 239.0.1.2

TX-DAL-2911#show ip mroute IP Multicast Routing Table Interface state: Interface, Next-Hop or VCD, State/Mode (10.1.29.129, 239.0.1.2), 00:00:40/00:02:53, flags: FT Incoming interface: GigabitEthernet0/0.2, RPF nbr 0.0.0.0 Outgoing interface list:

Tunnel0, Forward/Sparse, 00:00:40/00:02:49

!

Houston InformaCast Group Address 239.0.1.2 with Dallas Voice Vlan 10.1.29.129 as source IP. Dallas will forward PIM

join requests to its PIM RP at 10.1.2.1.