You are on page 1of 2

MULTICAST

Igmp to request to join the multicast group


pim join - prune
a dist tree is used to prevent loops and perform packet duplication

pim : dense - sparse - sparse with ssm - sparse bidir


224.0.0.0/24 local network control (ttl 1) - 224.0.1.0/24 (.39;.40)
232/8 ssm (used in pim sparse mode ; does not need an RP
233/8 glop ( allocated to any orga_ with 16 bit as number . as is split in two at
the binary )
239/8 administratively scoped (local , global scoped )

layer 2

mospf dvmrp cbt pim


inter-domain multicast : mp bgp - msdp

multicast traffic can be limited to an are with the ttl scoping


address scoping with acl at the border

pim is enbaled on all intf whre multicast traffic will flow

------------------------------------
igmp join is sent with a ttl of one
pim always takes igp path
sparse dense mode for auto rp support
can use sparse mode with auto rp , but you have to configure auto rp listerner on
all listener
state refresh helps dense mode not doing flood every 3 minutes

bootstrap router pim v2 is preffered

ipv6 flags 0rpt 0 set to 0 ; if r is set to 1 , p and t must also be set to a 1 .


indicates there is a rp embedded in the multicast address .

01.00.5e.
- convert the last three octets to binary
- change the leftmost bit to 0
- convert each nibble into hex

each group can have a different rp


bi dir is used to avoid many s,g entries

no pim register which was used to create an s,g entry in rp table

df election : AD ; metric ; higher ip

--------------------------------
- routeurs familles , roles , redondance architecture
- backbone
- igw , wacs ...
- sdh ,fo , dwdm ...
- PON
-------------------------------

You might also like