An empty access-list (containing no access control elements) cannot be applied on an interface.
Note
Controlling Access to an Interface
This task applies an access list to an interface to restrict access to that interface. Access lists can be applied
on either outbound or inbound interfaces.
SUMMARY STEPS
1. configure
2. interface type instance
3. ethernet-services access-group access-list-name { ingress | egress }
4. Use the commit or end command.
DETAILED STEPS
Step 1 configure
Example:
RP/0/RSP0/CPU0:router# configure
Enters the Global Configuration mode.
Step 2 interface type instance
Example:
RP/0/RSP0/CPU0:router(config)# interface gigabitethernet 0/2/0/
Configures an interface and enters interface configuration mode.
• The type argument specifies an interface type. For more information on interface types, use the question mark (?)
online help function.
• The instance argument specifies either a physical interface instance or a virtual instance.
• The naming notation for a physical interface instance is rack/slot/module/port. The slash (/) between values is
required as part of the notation.
• The number range for a virtual interface instance varies depending on the interface type.
Step 3 ethernet-services access-group access-list-name { ingress | egress }
Example:
RP/0/RSP0/CPU0:router(config-if)# ethernet-services access-group p-in-filter ingress
RP/0/RSP0/CPU0:router(config-if)# ethernet-services access-group p-out-filter egress
L2VPN and Ethernet Services Configuration Guide for Cisco ASR 9000 Series Routers, IOS XR Release 6.3.x
468
Implementing of Layer 2 Access Lists
Controlling Access to an Interface
To Next Page
Loading...
Need help?
General
