Brocade MLX Series and NetIron Family (Supporting Multi-Service IronWare R05.6.xx) - Manual (Page 17)

Brocade MLX Series and NetIron Family Documentation Updates 9
53-1003301-07
PIM over MCT
1
route-map Outer_Mall permit 10000
rule-name Catch_All
match ip address v4_Permit_Any
match ipv6 address v6_Permit_Any
set interface null0
end
Configuration consideration for Route-map
Route-map instances (The complete route-map blah permit|deny xxxx configuration section) and
route-map configuration must meet the following conditions:
1. The last set of commands must be interface null0, this can be preceded by multiple set of
other commands. This prevents the matched traffic from going to the CPU for forwarding, when
the egress VLAN is not a valid next hop.
2. Rule names can only be used once per route-map.
3. The last route-map instance must be set as CATCH-ALL, to avoid all unmatched traffic going to
the CPU for forwarding. The only exception is if you have another routing protocol which picks
up the unmatched traffic, and allows the usage of deny statement in the ACLs and no need to
set CATCH-ALL. All denied and unmatched packets will be passed to the routing protocol for
forwarding.
PIM over MCT
The MCT feature interaction matrix has been updated to indicate that BFD is not supported in
NetIron 5.4.00 and later releases.
MCT feature interaction
Use the following feature matrix when configuring MCT:
Multicast snooping over MCT
The following configuration consideration is modified in the Configuration considerations list under
the Multicast snooping over MCT section of the Multi-Chassis Trunking (MCT) chapter.
• On Customer Client Edge Ports (CCEP), MCT does not support 802.1ah.
MCT feature interaction matrix
Supported Not Supported
BGP, IS-IS, and OSPF on CCEP. BFD on CCEP.