
•
The Dell Networking OS implementation of MTRACE is in accordance with IETF draft
draft-fenner-traceroute-ipm
.
•
Multicast is not supported on secondary IP addresses.
•
Egress L3 ACL is not applied to multicast data traffic if you enable multicast routing.
Multicast Policies
The Dell Networking OS supports multicast features for IPv4.
IPv4 Multicast Policies
The following sections describe IPv4 multicast policies.
•
Limiting the Number of Multicast Routes
•
Preventing a Host from Joining a Group
•
Preventing a PIM Router from Forming an Adjacency
•
Preventing a Source from Registering with the RP
•
Preventing a PIM Router from Processing a Join
Limiting the Number of Multicast Routes
When the total number of multicast routes on a system limit is reached, the Dell Networking OS does not process any IGMP or
multicast listener discovery protocol (MLD) joins to PIM — though it still processes leave messages — until the number of entries
decreases below 95% of the limit.
When the limit falls below 95% after hitting the maximum, the system begins relearning route entries through IGMP, MLD, and
MSDP.
•
If the limit is increased after it is reached, subsequent join requests are accepted. In this case, increase the limit by at least 10%
for IGMP and MLD to resume.
•
If the limit is decreased after it is reached, Dell Networking OS does not clear the existing sessions. Entries are cleared after a
timeout (you may also clear entries using the
clear ip mroute
command).
NOTE: Dell Networking OS waits at least 30 seconds between stopping and starting IGMP join processing. You may
experience this delay when manipulating the limit after it is reached.
When the multicast route limit is reached, Dell Networking OS displays the following:
3w1d13h: %RPM0-P:RP2 %PIM-3-PIM_TIB_LIMIT: PIM TIB limit reached. No new routes will
be learnt until TIB level falls below low watermark.
3w1d13h: %RPM0-P:RP2 %PIM-3-PIM_TIB_LIMIT: PIM TIB below low watermark. Route learning
will begin.
To limit the number of multicast routes, use the following command.
•
Limit the total number of multicast routes on the system.
CONFIGURATION mode
ip multicast-limit
The range if from 1 to 16000.
The default is
4000
.
NOTE: The IN-L3-McastFib CAM partition is used to store multicast routes and is a separate hardware limit that exists
per port-pipe. Any software-configured limit may supersede this hardware space limitation. The opposite is also true, the
CAM partition might not be exhausted at the time the system-wide route limit is reached using the
ip multicast-
limit
command.
558
Multicast Features
Содержание S4048-ON
Страница 1: ...Dell Configuration Guide for the S4048 ON System 9 9 0 0 ...
Страница 146: ...Figure 14 BFD Three Way Handshake State Changes 146 Bidirectional Forwarding Detection BFD ...
Страница 477: ...Figure 68 Inspecting Configuration of LAG 10 on ALPHA Link Aggregation Control Protocol LACP 477 ...
Страница 480: ...Figure 70 Inspecting a LAG Port on BRAVO Using the show interface Command 480 Link Aggregation Control Protocol LACP ...
Страница 481: ...Figure 71 Inspecting LAG 10 Using the show interfaces port channel Command Link Aggregation Control Protocol LACP 481 ...
Страница 522: ...Figure 87 Configuring Interfaces for MSDP 522 Multicast Source Discovery Protocol MSDP ...
Страница 523: ...Figure 88 Configuring OSPF and BGP for MSDP Multicast Source Discovery Protocol MSDP 523 ...
Страница 524: ...Figure 89 Configuring PIM in Multiple Routing Domains 524 Multicast Source Discovery Protocol MSDP ...
Страница 528: ...Figure 91 MSDP Default Peer Scenario 1 528 Multicast Source Discovery Protocol MSDP ...
Страница 529: ...Figure 92 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 529 ...
Страница 530: ...Figure 93 MSDP Default Peer Scenario 3 530 Multicast Source Discovery Protocol MSDP ...
Страница 633: ...Policy based Routing PBR 633 ...
Страница 777: ...Figure 119 Single and Double Tag TPID Match Service Provider Bridging 777 ...
Страница 778: ...Figure 120 Single and Double Tag First byte TPID Match 778 Service Provider Bridging ...