Home > Articles > Cisco Network Technology > General Networking > VLAN Access Control Lists

VLAN Access Control Lists

Article Description

The latest generation of Cisco switching engines open up security and QoS, presenting new concepts for the campus network. Learn the steps to be taken to change with the times.

Modifying VACLs

After implementing the policy and having it run in our network, some problems come to our attention that need modification. Note that our second statement that was supposed to deny IP traffic within the 172.16.101.0 subnet has an invalid destination network address (172.16.1.0). This must be corrected. Also, it happens that there is another router on this VLAN and our configured gateway keeps sending ICMP redirects to the clients to use this router for certain networks, but due to the entry in the list that stops all other ICMP traffic, these redirects are being blocked. After applying the list, we learn that one of the minor applications running on server 172.16.101.44 regularly sends out broadcasts on UDP port 6108 to determine whether or not clients are active. If these clients don't respond back on UDP port 18888, their sessions with the server times out. It is determined that the following adjustments need to be made to the access policy:

Cat6K (enable) set security acl ip accesspolicy deny ip 172.16.101.0 0.0.0.255 
172.16.101.0 0.0.0.255
accesspolicy editbuffer modified. Use 'commit' command to apply changes.
Cat6K (enable) set security acl ip accesspolicy permit icmp host 172.16.101.1 
any host-redirect
accesspolicy editbuffer modified. Use 'commit' command to apply changes.
Cat6K (enable) set security acl ip accesspolicy permit udp host 172.16.101.44 
host 255.255.255.255 eq 6108
accesspolicy editbuffer modified. Use 'commit' command to apply changes.
Cat6K (enable) set security acl ip accesspolicy permit udp any host 
172.16.101.44 eq 18888
accesspolicy editbuffer modified. Use 'commit' command to apply changes.

At this point, the changes have been written to the editbuffer, but not committed to the TCAM. If we view the VACL, we note no changes. However, if we view the editbuffer, the changes are clear:

Cat6K (enable) show security acl info accesspolicy
set security acl ip accesspolicy
---------------------------------------------------
1. permit icmp any host 172.16.101.1 
2. deny ip 172.16.101.0 0.0.0.255 172.16.1.0 0.0.0.255 
3. deny icmp any any echo 
4. permit ip any any 

Cat6K (enable) show security acl info accesspolicy editbuffer                       
set security acl ip accesspolicy
---------------------------------------------------
1. permit icmp any host 172.16.101.1
2. deny ip 172.16.101.0 0.0.0.255 172.16.1.0 0.0.0.255
3. deny icmp any any echo
4. permit ip any any
5. deny ip 172.16.101.0 0.0.0.255 172.16.101.0 0.0.0.255
6. permit icmp host 172.16.101.1 any host-redirect
7. permit udp host 172.16.101.44 host 255.255.255.255 eq 6108
8. permit udp any host 172.16.101.44 eq 18888
ACL accesspolicy Status: Not Committed

The problem is that we can't add these to the bottom of the list because they would have no effect after the permit ip any any statement. So when we make these changes, a keyword before will be used at the end of the set command followed by the index number in the editbuffer of the item that we want to place them before. For the statement that changes the address for entry number 2, we will use the keyword modify to change that entry. Before we can add the statements correctly, however, we need to remove all the changes to the editbuffer. Because the editbuffer has not been committed, we can use the rollback command to change the editbuffer back to the most recent committed state.

Cat6K (enable) rollback security acl accesspolicy
Editbuffer for 'accesspolicy' rolled back to last commit state.

Cat6K (enable) show security acl info accesspolicy editbuffer
set security acl ip accesspolicy
---------------------------------------------------
1. permit icmp any host 172.16.101.1 
2. deny ip 172.16.101.0 0.0.0.255 172.16.1.0 0.0.0.255 
3. deny icmp any any echo 
4. permit ip any any 
ACL accesspolicy Status: Committed

Now we need to re-enter the commands with the appropriate keywords. But we also need to know where to place the entries in respect with the current list, so we will view the current list with the show security acl info command:

Cat6K (enable) show security acl info accesspolicy
set security acl ip accesspolicy
---------------------------------------------------
1. permit icmp any host 172.16.101.1 
2. deny ip 172.16.101.0 0.0.0.255 172.16.1.0 0.0.0.255 
3. deny icmp any any echo 
4. permit ip any any 

Note that we need to modify entry number 2. Place the ICMP permit statement in before entry number 3 and the remaining two statements need to be placed in before entry number 2. As the first one is placed in before number 2, it will become entry 2. This means that all the original statements will move down one in the index; what was entry 2 is now entry 3. The next statement will now be placed in the list before what is now entry number 3:

Cat6K (enable) set sec acl ip accesspolicy deny ip 172.16.101.0 0.0.0.255 
172.16.101.0 0.0.0.255 modify 2
accesspolicy editbuffer modified. Use 'commit' command to apply changes.
Cat6K (enable) set security acl ip accesspolicy permit icmp host 172.16.101.1 
any host-redirect before 3
accesspolicy editbuffer modified. Use 'commit' command to apply changes.
Cat6K (enable) set security acl ip accesspolicy permit udp host 172.16.101.44 
host 255.255.255.255 eq 6108 before 2
accesspolicy editbuffer modified. Use 'commit' command to apply changes.
Cat6K (enable) set security acl ip accesspolicy permit udp any host 
172.16.101.44 eq 18888 before 3
accesspolicy editbuffer modified. Use 'commit' command to apply changes.

Cat6K (enable) show security acl info accesspolicy editbuffer
set security acl ip accesspolicy
---------------------------------------------------
1. permit icmp any host 172.16.101.1 
2. permit udp host 172.16.101.44 host 255.255.255.255 eq 6108 
3. permit udp any host 172.16.101.44 eq 18888 
4. deny ip 172.16.101.0 0.0.0.255 172.16.101.0 0.0.0.255 
5. permit icmp host 172.16.101.1 any host-redirect 
6. deny icmp any any echo 
7. permit ip any any 
ACL accesspolicy Status: Not Committed

Now one of the advanced features of the VACL is that these changes are not being applied to the active list. If you check the active ACL, none of these changes are in effect.

Cat6K (enable) show security acl info accesspolicy 
set security acl ip accesspolicy
---------------------------------------------------
1. permit icmp any host 172.16.101.1 
2. deny ip 172.16.101.0 0.0.0.255 172.16.1.0 0.0.0.255 
3. deny icmp any any echo 
4. permit ip any any 

You would have to commit the changes before it affected the traffic flow. At this point, you would use the show security acl info accesspolicy editbuffer to verify the changes. If you want to eliminate all the changes, you could issue a rollback security acl accesspolicy command and clear all the changes in the editbuffer, or you could clear individual entries by using the clear security acl accesspolicy <edditbuffer_index> command. After you are satisfied with the changes, commit them by using the commit security acl accesspolicy command. This adds the entries to the active list and changes the flow of traffic accordingly. Verify these changes with the show security acl info accesspolicy command:

Cat6K (enable) commit security acl accesspolicy
ACL commit in progress.

ACL 'accesspolicy' successfully committed.
Cat6K (enable) show security acl info accesspolicy
set security acl ip accesspolicy
---------------------------------------------------
1. permit icmp any host 172.16.101.1 
2. permit udp host 172.16.101.44 host 255.255.255.255 eq 6108 
3. permit udp any host 172.16.101.44 eq 18888 
4. deny ip 172.16.101.0 0.0.0.255 172.16.101.0 0.0.0.255 
5. permit icmp host 172.16.101.1 any host-redirect 
6. deny icmp any any echo 
7. permit ip any any 
6. Removing VACLs | Next Section Previous Section

Cisco Press Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from Cisco Press and its family of brands. I can unsubscribe at any time.

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about Cisco Press products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites; develop new products and services; conduct educational research; and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@ciscopress.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by Cisco Press. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.ciscopress.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020