赫斯曼交换机配置说明-TTT_00_04_MC-HandsOn

Notes: Content

?Hands-on L2 multicasting

?Hands-on L3 multicasting (routing)

Tasks:

T k

?Build up a tree structure without and with IGMP and check the behavior

?Build up a HIPER Ring structure without and with IGMP …

?Build up a routed network with DVMRP and check the behavior

?Build up a routed network with PIM-DM and check the behavior

?Build up a HIPER Ring with routed networks …

B ild HIPER Ri ith t d t k

? Hirschmann Automation and Control GmbH

This presentation, and the material here in, have been prepared for the purposes of education and training. These slides are the sole property of Hirschmann and of education and training These slides are the sole property of Hirschmann and its subsidiaries, and are not to be altered, duplicated or distributed in any way without express written permission by Hirschmann.

?Microsoft Windows 95 and NT 4.0 support IGMPv1.

Notes:?Microsoft Windows 98 and 2000 support IGMPv2.

?Microsoft Windows XP supports IGMPv3. But there are still

a lot other devices in a network with v2 only. Thus IGMPv2

should be configured on devices (default of Hirschmann

g(

platform). A XP host receiving a v2 packet automatically

changes to v2 till a timer expires.

?The IGMP snooping release can be configured globally only, thus it is identical in all VLANs.

?On HIPER Ring ports “Forwarding All” should be configured.

In HIPER Ring one querier is enough

?In HIPER Ring one querier is enough.

?Querier selection is available as of IGMPv2. Please

remember the flooding problem mentioned in the appendix

of last presentation.

Local workaround is to configure static query ports in

direction of the MC source segment.

?Querier interval by default = 125 s. Minimum accepted in Querier interval by default=125s Minimum accepted in

3.0.03 = 2 s (depending on max response time)

(Config)# set igmp querier tx-interval

Notes:

Commands:?> enable

?# show igmpsnooping ?# show running-config [all]#fi

activates IGMPsnooping ?# config ?(Config)# set igmp

?(Config)# set igmp querier tx-interval ?Max response time must be less than querier interval. Default: 10 s

(Config)# set igmp querier max-response-time activates IGMPsnooping

(g)g p q p

?Note:a Windows XP notebook connected to v1 and v2 queriers changed from v3 to v1 after 83 minutes.

After changing querier version to v2 the XP client changed from v1to v2after 4:35minutes from v1 to v2 after 4:35 minutes.

The next change from v2 to v1 happened after a couple of seconds.

Notes:

1.Build up a tree structure and produce a MC stream

a)no IGMP: check behavior if producer is located in same

and in different branch of consumer

b)IGMPv1: check behavior if producer is located in same

and in different branch of consumer

and in different branch of consumer

c)IGMPv2: check behavior if producer is located in same

and in different branch of consumer

d)IGMPv3: check behavior if producer is located in same

and in different branch of consumer

2.Build up a HIPER Ring structure …

a)no IGMP: check behavior if producer is located in same

and in different branch of consumer

b)IGMPv1: check behavior if producer is located in same

and in different branch of consumer

c)IGMPv2: check behavior if producer is located in same

and in different branch of consumer

d)IGMPv3: check behavior if producer is located in same

and in different branch of consumer

?Due to its fast recovery time HIPER Ring is widely used as

Notes: link redundancy solution on layer 2 combined with routed

VLANs (VRRP for UCs).

?Thus regard special rules for MC routing over HIPER Ring.

,

?There should be no distributed VLANs, thus broadcasts need not be propagated over the backbone. The backbone

is a separate VLAN with separate subnet. This backbone

VLAN is routed (VLAN routing) to the other subnets

connected redundantly to router ports with VRRP.

?In the displayed application the use of DVMRP as MC

In the displayed application the use of DVMRP as MC

routing protocol is better than PIM-DM, because it uses its

own routing protocol and thus can detect …

?Please note: an IGMP enabled Hirschmann switch new connected first sends out querier packets to get all

registrations thus the next querier interval needs not to

registrations thus the next querier interval needs not to

expire.

?If a router port receives an IGMP packet with lower version

Notes: than globally configured then this port changes to that lower

release.

?IGMP snooping release should be configured same as IGMP release!

Please note: by default both are v2. IGMP snooping release

can be configured by web, IGMP release by CLI only (per

interface).

?Because IGMP snooping can be configured globally only IGMP snooping release is identical in all VLANs.

CLI commands:

?> enable

?# show igmpsnooping

?# show ip igmp interface

Example of configuration:

Notes:?(R1)> enable

?(R1)# configure

?(R1) (Configure)# ip igmp

?(R1) (Configure)# interface 1/1

?(R1) (Interface 1/1)# ip igmp

(R1)(Interface1/1)#ip igmp

?(R1) (Interface 1/1)# ip igmp version <1|2|3>

?(R1) (Interface 1/1)# exit

?(R1)# show ip igmp

Optional:

No.of Group Specific Queries sent(2default):

?No. of Group Specific Queries sent (2 default):

(R1) (Interface 1/1)# ip igmp last-member-query-count <1…20>

?Group Specific Query interval ( default):

?Query interval (125 s default):

(R1) (Interface 1/1)# ip igmp query-interval <1…3600>

?Query max response time (100 1/10 s):

(R1) (Interface 1/1)# ip igmp query-max-response-time <0…255>

?IGMP robustness (2 default):

(R1) (Interface 1/1)# ip igmp robustness <0…255>

(R1)(I t f1/1)#i i b t0255

?IGMP startup query count (2 default)

(R1) (Interface 1/1)# ip igmp startup-query-count <1…20>

?IGMP startup query interval (1 s default):

(R1) (Interface 1/1)# ip igmp startup-query-interval <1…300>

?IGMP snooping and thus the snooping querier is a global

Notes: function of a device.

?If the snoop-querier (IGMPv2 or v3) on a switch between two routers is active and the routers have a higher IP

address than the switch, the switch will win the querier

election and thus the snoop queriers of the connected

routers are disabled. As a result other switched ports at the

routers will loose their querier, if there is no other available

and thus multicasting doesn’t work anymore.

?GMRP cannot be used simultaneously to IGMP, thus it

Notes: cannot be used together with dynamic multicast routing.

CLI commands:

?(Config) # set gmrp adminmode or # no set…

(Config)#set gmrp adminmode or#no set

?(Config) # set gmrp interfacemode

?(Config) # set gmrp forward-all-groups

?(Interface x/y) #set gmrp interfacemode

?(Interface x/y) #set gmrp forward-all-groups

?> show gmrp configuration all

>show gmrp configuration all

?> show gmrp configuration

Notes: Multicast routing protocols are available in L3P firmware

package only!

Which MC routing protocol should be selected?

?DVMRP uses its own routing protocol while PIM-DM uses DVMRP uses its own routing protocol while PIM DM uses

the UC protocol in operation. DVMRP knows better the

topology with advantage in routed switched networks

especially together with HIPER Ring, static routes with

ECMP.

?The opt-out protocols DVMRP and PIM-DM start flooding, as

a result devices receive faster the streams.

a result devices receive faster the streams.

?As opt-out solutions after expiration of the hold timer MCs are flooded again thus producing high load condition till

prunes are sent again.

Holdtime DVMRP 2 h, fixed

Holdtime PIM-DM 210 s, configurable till 18 h.

?Convergence after topology changes is faster at PIM DM.

Convergence after topology changes is faster at PIM-DM.

?PIM offers configurable timers and thus a higher flexibility if necessary.

?DVMRP is limited to 32 hops.

?Enable unicast routing:

Notes: (R1) (Configure)# ip routing

?Enable multicast routing

(R1) (Configure)# ip multicast

?Note: if first “ip multicast” is entered with IGMP disabled and error message is displayed, but after “ip igmp” command the

configuration is o.k.

?To route MCs over one single PIM-DM router there is no need for unicast routing but for routing MCs over cascaded

need for unicast routing, but for routing MCs over cascaded

routers a UC routing protocol is needed (usually OSPF).

Notes: Example of configuration:

?(R1)> enable

?(R1)# configure

?(R1) (Configure)# ip igmp

(R1)(C fi)#i i

?(R1) (Configure)# ip multicast

?(R1) (Configure)# ip dvmrp

?(R1) (Configure)# interface 1/1

?(R1) (Interface 1/1)# ip igmp

?(R1) (Interface 1/1)# ip dvmrp

(R1)(Interface1/1)#ip dvmrp

?(R1) (Interface 1/1)# exit

?(R1) (Configure)# exit

?(R1)# show ip dvmrp

Note:For training purposes it’s sufficient to disable

DVMRP globally while it’s still enabled on the

interfaces and

then configure PIM-DM (see next slide).

Example of configuration:

Notes:?(R1)> enable

?(R1)# configure

?(R1) (Configure)# ip igmp

()(g)p

?(R1) (Configure)# ip multicast

?(R1) (Configure)# ip pimdm

?(R1) (Configure)# interface 1/1

?(R1) (Interface 1/1)# ip igmp

?(R1) (Interface 1/1)# ip pimdm mode

?(R1) (Interface 1/1)# exit

?(R1) (Configure)# exit

(R1)(C fi)#i

?(R1)# show ip pimdm

?(R1)# show ip mcast

?(R1)# show ip igmp

Optional:

?Configuration of holdtime in seconds (210 s default):

(R1) (Configure)# ip pimdm holdtimes <30…64800>

?Configuration of hello time in seconds:

(Interface s/p)# ip pimdm hello-interval <1…3600>

Notes:Consecutive order of minimum configuration:?Configure and enable router interfaces ?Set prompt for a better orientation ?Enable routing

CLI command sequence:(replace x by router number)> enable

# set prompt R x # configure

(Config)# ip routing (Config)#show ip brief ?Configure UC routing protocol globally

?Enable IGMP globally (automatically enables MC routing and IGMP snooping)?Enable multicast forwarding (routing)Enable PIM SM globally (Config)# show ip brief (Config)# router ospf

(Config-router)# router-id x .1.1.1(Config-router)# enable

(Config-router)# redistribute connected [subnets](Config-router)# exit (Config)# ip igmp (Config)# ip multicast (Config)#ip pimsm ?Enable PIM-SM globally ?Set static Rendezvous Point ?Configure routing interfaces

?Configure UC routing protocol per interface ?Enable IGMP per interface, and set version Optionally change version (default =2)(Config)# ip pimsm

(Config)# ip pimsm rp-address …(Config)# interface

(Interface s/p)# ip address (Interface s/p)# routing

(Interface s/p)# ip ospf area-id 0.0.0.0(Interface s/p)# ip ospf (Interface s/p)# ip igmp

(Interface s/p)#ip igmp version <1|?Optionally change version (default = 2)?Enable PIM-SM on respective interfaces

(Interface s/p)# ip igmp version <1|2|3>(Interface s/p)# ip pimsm mode (Interface s/p)# exit (Config)# exit # show ip pimsm

# copy system:running-config nvram:startup-config # logout

The IGMP version by default is 2.

Notes: Please note that a Rendezvous Point must be configured on all PIM-SM enabled routers, even at the RP itself.

The alternative is to define at least one Bootstrap router

(BSR) and at least one RP candidate. At a customer site it’s

g

recommended to configure 2 candidate RPs and 2 candidate BSRs for redundancy.

Further commands:

?(Interface s/p)# show

?# show ip pimsm

?# show ip mcast

#show ip mcast

?# show ip igmp

Optional:

?Configuration of DR priority:

(Interface s/p)# ip pimsm dr-priority <0…2,147,483,647>

Configuration of hello interval in seconds(30s default):

?Configuration of hello interval in seconds (30 s default): (Interface s/p)# ip pimsm hello-interval <0…18000>

?Pre-requisite of PIM-SM is a correctly running UC routing

Notes: protocol like OSPF.

?MC routing between 2 IFs on one router works if on this router an RP is defined. But the RP needs not to be

configured itself.

?MC routing between 2 IFs on two routers only works if RP is defined on both routers and on the RP itself.

?For MC routing protocols at neighbor expiry only a trap is defined. For IGMP there is no trap implemented.

?Instead of statically define RPs, now BSR and RP

Notes: candidates are configured from which a BSR and RP are

elected.

?CLI commands:

?(Config)# ip pimsm bsr-candidate interface

?(Config)# ip pimsm rp-candidate interface

Notes:

1.Build up a routed network with DVMRP

a)check behavior if producer is located in same and in

different branch of consumer

2.Build up a routed network with PIM-DM and check the

2Build up a routed network with PIM DM and check the

behavior

a)check behavior if producer is located in same and in

different branch of consumer

3.Build up a HIPER Ring with routed networks …

a)check behavior if producer is located in same and in

different branch of consumer

All MC packets with a TTL value less than the defined

Notes: threshold were discarded at the specific interface.