beautypg.com

Mct snooping, Events handling, Ccep down event to mct – Brocade Multi-Service IronWare Switching Configuration Guide (Supporting R05.6.00) User Manual

Page 715: Mct remote ccep down event, Mct local ccep up event

background image

Multi-Service IronWare Switching Configuration Guide

685

53-1003036-02

MCT Snooping

18

client MCT_CLIENT1

rbridge-id 101

client-interface e 1/1

[vll-pw-redundancy-active]

deploy

MCT Snooping

All VLAN IGMP and PIM snooping features are supported on the MCT links. Brocade supports both
IPv4 and IPv6 snooping over MCT links.

Events Handling

CCEP down event to MCT

CCEP down event to MCT peer is generated only if,

The CCEP port is replaced in the SG entry's OIF to ICL ports, if CCEP ports exists in the OIF list.
The new periodic IGMP joins now coming through the remote CCEP ports will reach us as
MDUP messages on the ICL ports. This will ensure that the ICL ports in the SG/WG OIF list and
IGMPv3 DB are refreshed.

MCT remote CCEP down event

MCT remote CCEP down event is generated only if,

The CCEP ports of the MCT peer (remote CCEP ports) goes down. Two possible scenarios exist:

SG entry with ICL as IIF already exists (because there was a local CEP receiver for that SG). In
this case, a CCEP link (only if it exists in WG entry or IGMPv3 DB due to joins received) will be
added to SG OIF list. If no joins were received from CCEP, then the CCEP will not be added to
the OIF list, unless it is a flooding scenario.

SG entry with ICL as IIF didn't exist because there are only remote CCEP receivers and no local
CEP receivers. In this case when remote CCEP goes down we'll start getting SG flows thru ICL
and we'll create SG and add local CCEP ports to the OIF (copied from WG entry).

MCT local CCEP up event

MCT local CCEP up event is generated only,

After the local CCEP comes up, two possible scenarios exist:

IGMP joins may start coming thru the local CCEP links or

IGMP joins may continue to come thru the remote CCEP link as before.

In case1, you stop receiving MDUP message from the MCT peer through the ICL link and the ICL
ports are eventually aged out from the WG/SG OIF list. Local CCEP ports are added to the OIF list.

In case2, you will continue to get MDUP messages from MCT peer through the ICL link and the local
CCEP is up and the local CCEP is added to the OIF. The ICL ports will eventually age out, if the
MDUP join messages with remote CEP flag set were not received. The CCEP up event is sent to the
MCT PEER.