The Per Interface Mroute State Limit feature allows you to specify limits according to the direction of traffic that is, it allows you to specify limits for outgoing interfaces, incoming interfaces, and for incoming interfaces having directly connected multicast sources. As such, the IGMP State Limit feature is more specific in application because it specifically limits IGMP joins. The Per Interface Mroute State Limit feature has a wider application in that it can be configured to limit IGMP joins on an outgoing interface, to limit PIM joins (for Any Source Multicast groups or Source Specific Multicast channels) on an outgoing interface connected to other routers, to limit sources behind an incoming interface from sending multicast traffic, or to limit sources directly connected to an incoming interface from sending multicast traffic.Īlthough the PIM Interface Mroute State Limit feature allows you to limit both IGMP and PIM joins, it does not provide the capability to limit PIM or IGMP joins separately because it does not take into account whether the state is created as a result of an IGMP or PIM join. The IGMP State Limit feature, thus, is more limited in application in that it is best suited to be configured on an edge router to limit the number of groups that receivers can join on an outgoing interface.
The Per Interface Mroute State Limit feature can be used to limit both IGMP and PIM joins, whereas the IGMP State Limit feature can only be used to limit IGMP joins. The Per Interface Mroute State Limit feature, thus, is more flexible than the IGMP State Limit feature in that it allows multiple limits to be configured for different sets of multicast traffic on an interface. The Per Interface Mroute State Limit feature allows multiple limits to be configured on an interface, whereas the IGMP State Limit feature allows only one limit to be configured on an interface. The main differences between the Per Interface Mroute State Limit feature and the IGMP State Limit feature are as follows:
The Per Interface Mroute State Limit feature, moreover, is more flexible and powerful (albeit more complex) than the IGMP State Limit feature but is not intended to be a replacement for it because there are applications that suit both features. The Per Interface Mroute State Limit feature essentially is a complete superset of the IGMP State Limit feature (with the exception that it does not support a global limit). This feature can be used to prevent DoS attacks or to provide a multicast CAC mechanism when all the multicast flows roughly utilize the same amount of bandwidth.
CISCO IOS XE LIMIT BANDWIDTH ON INTERFACE PLUS
O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.The Per Interface Mroute State Limit feature provides the capability to limit the number of mroute states on an interface for different ACL-classified sets of multicast traffic. Get Cisco IOS Cookbook, 2nd Edition now with O’Reilly online learning. In the following example, we have manually reduced bandwidth value on this 128 kbps interface to 32 kbps to affect the EIGRP metric. Network convergence times when EIGRP needs to suddenly exchange a Increase the fraction that EIGRP can use. The real physical bandwidth of the interface, you might want to If this value is significantly lower than
CISCO IOS XE LIMIT BANDWIDTH ON INTERFACE HOW TO
Specified on an interface is not accurate.ħ.6, we discussed how to change what the router thinks the Sometimes you need to reduce this fraction to However, this default isn’tĪlways appropriate. More than 50 percent of a link’s capacity. Limits its own bandwidth utilization to ensure that it never takes
Percent of the available capacity of this link. The example above shows how to restrict EIGRP to use at most 40