Home > BOOTCAMP, MULTICAST > HARI 5 MULTICAST

HARI 5 MULTICAST

Multicast Routing

Multicast
Dense Mode Trafic Multicast di flood disemua router yang mengaktifkan Multicast pada interface-nya
Sparse Mode Host harus request terlebih dahulu , baru kemudian traffic multicast dikirim, diperlukan RP ( rendezvous Point) sebagai pusat penghubung multicast source dan router2 yang memiliki client dibawahnya.Ada 3Cara penentuan RP :- Static RP- Auto RP ( cisco proprietary) – perlu dense mode untuk mapping agent , sehingga ada sparse-dense- BSR : candidate RP dan Mapping agent dikirimkan melalui PIM message Hop per hop

Mroute :

S,G : S menunjukan Source ke group, pada Dense-mode

*,G : * menunjukan RP groupe ( Sparse Mode )

—-

command mengaktifkan Multicast :

Router :  IP Multicast-routing

Switch : IP Multicast-routing distribute

IGMP
IGMP Versi 1 Paket tetap dikirim walaupun user dalam keadaan mati ( tidak efektif) , IGMP v1 sudah tidak dipakai
IGMP Versi 2 Sama dengan V1 , paket tetap dikirim, hanya saja jika berhenti, user memberikan notifikasi prune message, sehingga paket berhenti dikirim jika user selesai / mati
IGMP Versi 3 Support source Filtering

*************************

Lab 1 . Dense Mode
Lab 2 . Sparse Mode
Lab 3 . Sparse-Dense Mode – Auto RP 1
Lab 4 . Sparse-Dense Mode – Auto RP 2
Lab 5 . Sparse-Dense Mode – Auto RP–Multiple RP
Lab 6 . Sparse Mode – Auto RP
Lab 7 . Sparse Mode – BSR
Lab 8 . IPv6 – Static RP
Lab 9 . IPv6 – BSR

*************************

LAB1 Dense Mode

Skenario : lab Dense Mode

Note : Command untuk mengaktifkan dense mode , ip pim dense-mode di tiap interface yang akan join

R1

ip multicast-routing

interface Loopback0

ip address 1.1.1.1 255.255.255.255

ip pim dense-mode

ip ospf 1 area 0

interface FastEthernet0/0

ip address 12.12.12.1 255.255.255.0

ip pim dense-mode

ip ospf 1 area 0

router ospf 1

router-id 1.1.1.1

log-adjacency-changes

ip igmp join-group 239.0.0.1

VERIFIKASI

R3#ping 239.0.0.1

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 239.0.0.1, timeout is 2 seconds:

Reply to request 0 from 12.12.12.1, 224 ms

**************************

LAB 2 Sparse Mode – Static RP

Skenario : RP di define secara static di smua router.

Note :

R1

interface Loopback0

ip address 1.1.1.1 255.255.255.255

ip pim sparse-mode

ip igmp join-group 239.0.0.1

ip ospf 1 area 0

interface FastEthernet0/0

ip address 12.12.12.1 255.255.255.0

ip pim sparse-mode

ip ospf 1 area 0

router ospf 1

router-id 1.1.1.1

log-adjacency-changes

 

define di all router ( R1 , R2 dan R3)

ip pim rp-address 2.2.2.2

 

Verifikasi

R2(config)#do sh ip pim interface

 

Address          Interface                Ver/   Nbr    Query  DR     DR

                                          Mode   Count  Intvl  Prior

12.12.12.2       FastEthernet0/0          v2/S   1      30     1      12.12.12.2

23.23.23.2       FastEthernet0/1          v2/S   1      30     1      23.23.23.3

2.2.2.2          Loopback0                v2/S   0      30     1      2.2.2.2

 

 

R2(config)#do sh ip pim rp mapp

PIM Group-to-RP Mappings

 

Group(s): 224.0.0.0/4, Static

    RP: 2.2.2.2 (?)

 

IP Multicast Routing Table

Outgoing interface flags: H – Hardware switched, A – Assert winner

 Timers: Uptime/Expires

 Interface state: Interface, Next-Hop or VCD, State/Mode

 

(*, 224.0.1.40), 00:00:05/00:02:54, RP 2.2.2.2, flags: SJCL

  Incoming interface: Null, RPF nbr 0.0.0.0

  Outgoing interface list:

    FastEthernet0/0, Forward/Sparse, 00:00:05/00:02:54

 

 

Outgoing interface flags: H – Hardware switched, A – Assert winner

 Timers: Uptime/Expires

 Interface state: Interface, Next-Hop or VCD, State/Mode

 

(*, 224.0.1.40), 00:00:30/stopped, RP 2.2.2.2, flags: SJPCLF

  Incoming interface: FastEthernet0/0, RPF nbr 23.23.23.2

  Outgoing interface list: Null

 

(23.23.23.2, 224.0.1.40), 00:00:30/00:02:40, flags: PLFT

  Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0

  Outgoing interface list: Null

 

R3(config)#do ping 224.0.1.40

 

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 224.0.1.40, timeout is 2 seconds:

 

 

R1(config)#int lo 0

R1(config-if)#ip igmp join-group 239.0.0.1

 

R3(config)# do sh ip mroute

IP Multicast Routing Table

 Timers: Uptime/Expires

 Interface state: Interface, Next-Hop or VCD, State/Mode

 

(*, 239.0.0.1), 00:03:03/00:02:59, RP 2.2.2.2, flags: SPF

  Incoming interface: FastEthernet0/0, RPF nbr 23.23.23.2

  Outgoing interface list: Null

 

(*, 224.0.1.40), 00:04:29/stopped, RP 2.2.2.2, flags: SJPCLF

  Incoming interface: FastEthernet0/0, RPF nbr 23.23.23.2

  Outgoing interface list: Null

 

(1.1.1.1, 224.0.1.40), 00:01:16/00:01:44, flags: PLTX

  Incoming interface: FastEthernet0/0, RPF nbr 23.23.23.2

  Outgoing interface list: Null

 

(12.12.12.1, 224.0.1.40), 00:02:17/00:02:44, flags: PLTX

  Incoming interface: FastEthernet0/0, RPF nbr 23.23.23.2

  Outgoing interface list: Null

 

R3(config)#do ping 239.0.0.1

 

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 239.0.0.1, timeout is 2 seconds:

 

Reply to request 0 from 12.12.12.1, 276 ms

Reply to request 0 from 12.12.12.1, 276 ms

 

 

***************************************************

LAB 3 Sparse Mode – Auto RP

R1 jadi RP mapping agent ( discovery ) juga jadi RP candidate , berjalan hanya di mode sparse-dense which is propertiary CISCO, masih perlu flood ( dense) untuk  pemilihan RP –nya.

R1(config)#ip pim send-rp-announce loopback 0 scope 255

R1(config)#ip pim send-rp-discovery scope 255

 

Jika salah config, akan menjadi dense mode dengan sendirinya.

Verifikasi  :

 

R1(config)#do sh ip pim rp mapping

PIM Group-to-RP Mappings

This system is an RP (Auto-RP)

This system is an RP-mapping agent

 

Group(s) 224.0.0.0/4

  RP 1.1.1.1 (?), v2v1

    Info source: 1.1.1.1 (?), elected via Auto-RP

         Uptime: 00:04:58, expires: 00:01:59

 

R2(config)#do sh ip pim rp mapp

PIM Group-to-RP Mappings

 

Group(s) 224.0.0.0/4

  RP 1.1.1.1 (?), v2v1

    Info source: 12.12.12.1 (?), elected via Auto-RP

         Uptime: 00:06:37, expires: 00:01:14

 

R1(config)#do ping 239.0.0.1

 

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 239.0.0.1, timeout is 2 seconds:

 

Reply to request 0 from 1.1.1.1, 4 ms

******************************

LAB 5 Sparse-Dense Mode – Auto RP-Multiple RP

Note : dalam satu group hanya boleh ada 1 RP

R1

interface Loopback0

ip igmp join-group 239.0.0.1

ip pim send-rp-announce Loopback0 scope 255

ip pim send-rp-discovery scope 255

R2

interface Loopback0

ip igmp join-group 239.1.1.1

ip pim send-rp-announce Loopback0 scope 255

ip pim send-rp-discovery scope 255

VERIFIKASI

R3(config)#do ping 239.0.0.1

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 239.0.0.1, timeout is 2 seconds:

 

Reply to request 0 from 12.12.12.1, 228 ms

Reply to request 0 from 12.12.12.1, 328 ms

R3(config)#do ping 239.1.1.1

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 239.1.1.1, timeout is 2 seconds:

 

Reply to request 0 from 23.23.23.2, 188 ms

******************************

LAB 7 Sparse Mode – BSR

Skenario :

R1

ip pim bsr-candidate loopback 0  configurasi bsr

ip pim rp-candidate lo0  kandidat RP

 

cek hasilnya :

R2(config)#do sh ip pim rp mapp

PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4

RP 1.1.1.1 (?), v2

Info source: 1.1.1.1 (?), via bootstrap, priority 0, holdtime 150

Uptime: 00:00:19, expires: 00:02:09

Sparse – Dense Mode

R1

ip pim send-rp-announce lo0 scope 255

ip pim send-rp-discovery scope 255

R2(config)#do sh ip pim rp map

PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4

RP 1.1.1.1 (?), v2

Info source: 1.1.1.1 (?), via bootstrap, priority 0, holdtime 150

Uptime: 00:08:18, expires: 00:02:13

R2(config)#do ping 239.0.0.1

Type escape sequence to abort.

Sending 1, 100-byte ICMP Echos to 239.0.0.1, timeout is 2 seconds:

Reply to request 0 from 12.12.12.1, 156 ms

R1(config)#ip pim send-rp-announce lo0 scope 255

R2(config)#ip pim send-rp-discovery scope 255

R1(config)#do sh ip pim rp map

PIM Group-to-RP Mappings

This system is an RP (Auto-RP)

Group(s) 224.0.0.0/4

RP 1.1.1.1 (?), v2v1

Info source: 12.12.12.2 (?), elected via Auto-RP

Uptime: 00:14:10, expires: 00:03:42

R2(config)#do sh ip pim rp map

PIM Group-to-RP Mappings

This system is an RP-mapping agent

Group(s) 224.0.0.0/4

RP 1.1.1.1 (?), v2v1

Info source: 12.12.12.1 (?), elected via Auto-RP

Uptime: 00:14:03, expires: 00:03:26

Advertisement
Categories: BOOTCAMP, MULTICAST

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.