Multicast Routing OA6850-48L

Nziokxs · Post by **Nziokxs** » 29 Mar 2010 11:08

hallo Experts,

in my setup
Multicast Source is on vlan 102 and Receiever is on vlan 105
wht do i need to configure so that members of vlan 105 can receive a muticast stream coming from a source on vlan 102

I will appreciate any pointers provided

MWLosRios · Post by **MWLosRios** » 30 Mar 2010 18:45

First, you need to load pim, then create PIM interfaces for vlan 102 and vlan 105. After that, you have some options. The easiest way is to create a PIM dense group for all multicast (224.0.0.0/4) and enable pim dense status. Then you should be able to multicast route between vlans 102 and 105.

Multicast routing requires multicast switching, so you will need to enable multicast switching on your 6850 as well.

Post by **silvio** » 31 Mar 2010 04:24

Hi,
best way is to activate MC-Routing-protocol like DVMRP at the switch.

ip load dvmrp
ip dvmrp interface if102
ip dvmrp interface if105
ip dvmrp status enable

regards
Silvio

Nziokxs · Post by **Nziokxs** » 31 Mar 2010 05:06

hi silvio,
in my setup the client wants to use PIM so i have the below configuration kindly advice on any parameters i might have left out on the setup

-> write terminal
! Stack Manager :
! Chassis :
system name Multicast_Switch
system timezone MSK
! Configuration:
! VLAN :
vlan 1 enable name "VLAN 1"
vlan 11 enable name "local_management"
vlan 100 enable name "OSS&NMS"
vlan 100 port default 1/1
vlan 100 port default 1/2
vlan 100 port default 1/3
vlan 100 port default 1/4
vlan 100 port default 1/5
vlan 100 port default 1/6
vlan 100 port default 1/7
vlan 100 port default 1/8
vlan 100 port default 1/9
vlan 100 port default 1/10
vlan 101 enable name "MS"
vlan 101 port default 1/11
vlan 101 port default 1/12
vlan 101 port default 1/13
vlan 101 port default 1/14
vlan 101 port default 1/15
vlan 101 port default 1/16
vlan 101 port default 1/17
vlan 101 port default 1/18
vlan 101 port default 1/19
vlan 101 port default 1/20
vlan 102 enable name "CXC"
vlan 102 port default 1/21
vlan 102 port default 1/22
vlan 102 port default 1/23
vlan 102 port default 1/24
vlan 102 port default 1/25
vlan 102 port default 1/26
vlan 102 port default 1/27
vlan 102 port default 1/28
vlan 102 port default 1/29
vlan 103 enable name "OAM"
vlan 103 port default 1/30
vlan 103 port default 1/31
vlan 103 port default 1/32
vlan 103 port default 1/33
vlan 103 port default 1/34
vlan 103 port default 1/35
vlan 103 port default 1/36
vlan 104 enable name "MPFG2"
vlan 104 port default 1/37
vlan 104 port default 1/38
vlan 104 port default 1/39
vlan 104 port default 1/40
vlan 105 enable name "Management"
vlan 105 port default 1/41
vlan 105 port default 1/42
vlan 105 port default 1/43
vlan 105 port default 1/44
vlan 105 port default 1/45
vlan 105 port default 1/46
! VLAN SL:
! IP :
ip service all
ip interface "vlan100" address 192.168.15.1 mask 255.255.255.128 vlan 100 ifindex 1
ip interface "vlan101" address 192.168.15.129 mask 255.255.255.192 vlan 101 ifindex 2
ip interface "vlan102" address 192.168.15.193 mask 255.255.255.224 vlan 102 ifindex 3
ip interface "vlan103" address 192.168.15.225 mask 255.255.255.224 vlan 103 ifindex 4
ip interface "vlan105" address 10.10.5.1 mask 255.255.255.0 vlan 105 ifindex 5
ip interface "local_management" address 10.0.4.210 mask 255.255.255.0 vlan 11 ifindex 8
! IPX :
! IPMS :
ip multicast status enable
ip multicast querying enable
ip multicast vlan 100 status enable
ip multicast vlan 101 status enable
ip multicast vlan 102 status enable
ip multicast vlan 103 status enable
ip multicast vlan 104 status enable
ip multicast vlan 105 status enable
! AAA :
aaa authentication console "local"
aaa authentication telnet "local"
aaa authentication ftp "local"
aaa authentication http "local"
aaa authentication ssh "local"
! PARTM :
! AVLAN :
! 802.1x :
! QOS :
! Policy manager :
! Session manager :
! SNMP :
! RIP :
! OSPF :
! BFD-STD :
! ISIS :
! IPv6 :
! IPSec :
! IP multicast :
ip load pim
ip pim interface "vlan100"
ip pim interface "vlan101"
ip pim interface "vlan102"
ip pim interface "vlan103"
ip pim interface "vlan105"
ip pim sparse status enable
ip pim dense status disable
ipv6 pim sparse status disable
ipv6 pim dense status disable
! RIPng :
! OSPF3 :
! BGP :
! Health monitor :
! Interface :
interfaces 1/2 alias "TO_7450_2/2/8"
interfaces transceiver ddm enable
! Udld :
! Netsec :
! Port Mapping :
! Link Aggregate :
! VLAN AGG:
! 802.1Q :
vlan 11 802.1q 1/2 "TAG PORT 1/2 VLAN 11"
vlan 102 802.1q 1/2 "TAG PORT 1/2 VLAN 102"
! Spanning tree :
bridge mode 1x1
! Bridging :
! Bridging :
! Port mirroring :
! UDP Relay :
! Server load balance :
! System service :
swlog console level info
! SSH :
! VRRP :
! Web :
! AMAP :
! LLDP :
! Lan Power :
! NTP :
! RDP :
! VLAN STACKING:
! Ethernet-OAM :
! EFM-OAM :
! ERP :
! SAA :
->

MWLosRios · Post by **MWLosRios** » 05 Apr 2010 19:07

If you are going to use PIM-SM (sparse mode), which from your config looks like what you are going to use, you need to have a Rendezvous Point configured for all multicast groups. PIM-SM cannot route multicast traffic enless there is a rendezvous point for it. You can achive this with static-rp, or by configuring your router as a candidate RP.

Static-RP method:
ip pim static-rp 224.0.0.0/4 192.168.15.1 --> must be one of your PIM-enabled interfaces on router

Candidate-RP Method
ip pim cbsr 192.168.15.1
ip pim candidate-rp 192.168.15.1 224.0.0.0/4

After either, verify your rendezvous points with
show ip pim group-map

Nziokxs · Post by **Nziokxs** » 06 Apr 2010 05:56

Experts,

has anyone spotted any mistake in my configuration, something i need to change because its seems not to be working

Post by **silvio** » 06 Apr 2010 06:42

Hi,
I haven't found any mistake.
I'm not sure .... Normaly Pim needs an other routing protocol like ospf or rip for working. But I don't know what is in your case - routing at the same switch.
You can try to activate ospf at your interfaces.
Silvio

Nziokxs · Post by **Nziokxs** » 06 Apr 2010 07:05

Hi Silvio,

I had not enabled any routing protocol in my OA6850-48L routing is happening on the same switch so i will activate OSPF as advised test again then i will revert back, much appreciation to your assistance.

MWLosRios · Post by **MWLosRios** » 06 Apr 2010 11:33

I think you need to enable PIM sparse mode with 'ip pim sparse status enable'. Take a look at the output of 'show ip pim interface' and see if any of them are enabled.

Again, you need a rendezvous point defined for PIM sparse to work. Issue the command 'show ip pim group-map'. If there is no output other than the column headings, you won't be able to route multicast traffic with PIM sparse mode. You can define a static RP with 'ip pim static-rp'.

Nziokxs · Post by **Nziokxs** » 07 Apr 2010 01:43

MWLosRios wrote:If you are going to use PIM-SM (sparse mode), which from your config looks like what you are going to use, you need to have a Rendezvous Point configured for all multicast groups. PIM-SM cannot route multicast traffic enless there is a rendezvous point for it. You can achive this with static-rp, or by configuring your router as a candidate RP.

Static-RP method:
ip pim static-rp 224.0.0.0/4 192.168.15.1 --> must be one of your PIM-enabled interfaces on router

Candidate-RP Method
ip pim cbsr 192.168.15.1
ip pim candidate-rp 192.168.15.1 224.0.0.0/4

After either, verify your rendezvous points with
show ip pim group-map

Hi MWLosRios

I have defined a RP using the second method {Candidate-RP Method}

Question: i believe i only need to define it once as you indicated above and it will be sufficient for the other interfaces.?

thank you very much for your assistance, i will ask the customer to test and i will revert back.