
7
Access Control List (ACL) VLAN Groups and
Content Addressable Memory (CAM)
This chapter describes the access control list (ACL) virtual local area network (VLAN) group and content addressable memory
(CAM) enhancements.
Optimizing CAM Utilization During the Attachment of ACLs to VLANs
To minimize the number of entries in CAM, enable and configure the ACL CAM feature. Use this feature when you apply ACLs to a
VLAN (or a set of VLANs) and when you apply ACLs to a set of ports. The ACL CAM feature allows you to effectively use the Layer
3 CAM space with VLANs and Layer 2 and Layer 3 CAM space with ports.
To avoid using too much CAM space, configure ACL VLAN groups into a single group. A class identifier (Class ID) is assigned for
each of the ACLs attached to the VLAN and this Class ID is used as an identifier or locator in the CAM space instead of the VLAN
ID. This method of processing reduces the number of entries in the CAM area and saves memory space by using the Class ID for
filtering in CAM instead of the VLAN ID.
When you apply an ACL separately on the VLAN interface, each ACL has a mapping with the VLAN and you use more CAM space.
To maximize CAM space, create an ACL VLAN group and attach the ACL with the VLAN members.
The ACL manager application on the router processor (RP1) contains all the state information about all the ACL VLAN groups that
are present. The ACL handler on the control processor (CP) and the ACL agent on the line cards do not contain any information
about the group. After you enter the
acl-vlan-group
command, the ACL manager application performs the validation. If the
command is valid, it is processed and sent to the agent, if required. If a configuration error is found or if the maximum limit has
exceeded for the ACL VLAN groups present on the system, an error message displays. After you enter the
acl-vlan-group
command, the ACL manager application verifies the following parameters:
•
Whether the CAM profile is set in virtual flow processing (VFP).
•
Whether the maximum number of groups in the system is exceeded.
•
Whether the maximum number of VLAN numbers permitted per ACL group is exceeded.
•
When a VLAN member that is being added is already a part of another ACL group.
After these verification steps are performed, the ACL manager considers the command valid and sends the information to the ACL
agent on the line card. The ACL manager notifies the ACL agent in the following cases:
•
A VLAN member is added or removed from a group and previously associated VLANs exist in the group.
•
The egress ACL is applied or removed from the group and the group contains VLAN members.
•
VLAN members are added or deleted from a VLAN, which itself is a group member.
•
A line card returns to the active state after going down and this line card contains a VLAN that is a member of an ACL group.
•
The ACL VLAN group is deleted and it contains VLAN members.
The ACL manager does not notify the ACL agent in the following cases:
•
The ACL VLAN group is created.
•
The ACL VLAN group is deleted and it does not contain VLAN members.
•
The ACL is applied or removed from a group and the ACL group does not contain a VLAN member.
106
Access Control List (ACL) VLAN Groups and Content Addressable Memory (CAM)
Содержание 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 ...