The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The MAC Address Limiting on Service Instances, Bridge Domains, and EVC Port Channels feature addresses port security with service instances by providing the capability to control and filter MAC address learning behavior at the granularity of a per-service instance. When a violation requires a shutdown, only the customer who is assigned to a given service instance is affected and--not all customers who are using the port.
MAC address limiting is a type of MAC security and is also referred to as a MAC security component or element.
An understanding of service instances and bridge domains.
An understanding of how port channels and EtherChannels work in a network.
MAC address limiting for service instances and bridge domains is configured under a service instance and is permitted only after the service instance is configured under a bridge domain. If a service instance is removed from a bridge domain, all the MAC address limiting commands under it are also removed. If a bridge domain is removed from a service instance, all the MAC address limiting commands are also removed.
The MAC Address on RSP1 port channel overlaps with the interface MAC address and the traffic is dropped from ports 1 to 8 when an interface module is placed on slot 4.
System wide, the following limits apply to the total configured allowed list and learned MAC addresses:
Total number of MAC addresses supported under MAC Security is limited to 64K (65536).
Total number of secure EFPs in the system is limited to 64K (65536).
Total number of MAC addresses supported under MAC Security, per EFP, is limited to 1K (1024).
Total number of EFPs per bridge domain 4000.
Total number of bridge domains per system 16000.
You can configure or remove the various MAC security elements irrespective of whether MAC security is enabled on the EFP. However, these configurations become operational only after MAC security is enabled.
It is recommended that you enable MAC address security feature on all the EFPs in a bridge-domain.
When you enable the MAC address security for EVC bridge domain feature, existing MAC address table entries on the EFP are removed.
When you enable the MAC address security, the traffic is forwarded once the device learns the MAC address.
The MAC address security for EVC bridge domain feature can be configured on an EFP only if the EFP is a member of a bridge domain.
you can configure non-MAC address security on an EVC and enable MAC address security on a different EVC, which are in the same bridge-domain.
If you disassociate the EFP from the BD, the MAC security feature is completely removed.
For port-channel, this configuration is propagated to all member links in the port-channel. Consistent with the already implemented bridge domain EVC port-channel functionality, packets on a secured EFP are received on any member link, but all the egress packets are sent out to one of the selected member links.
System does not permit addition of multicast/broadcast MAC address as a permit address. However, addition of multicast/broadcast MAC address is allowed in deny address configuration to verify such invalid packets.
When EVC with the same EFP or service instance is created between ports 1 and 2 and MAC address m1 is configured as permit address (allowed list) on port1, the same MAC address can be configured as deny address (blocked list) on port2 and vice versa.
An Ethernet virtual circuit (EVC) as defined by the Metro Ethernet Forum is a port-level point-to-point or multipoint-to-multipoint Layer 2 circuit. It is an end-to-end representation of a single instance of a Layer 2 service being offered by a provider to a customer. An EVC embodies the different parameters on which the service is being offered. A service instance is the instantiation of an EVC on a given port.
Support for Ethernet bridging is an important Layer 2 service that is offered on a router as part of an EVC. Ethernet bridging enables the association of a bridge domain with a service instance.
For information about the Metro Ethernet Forum standards, see the “Standards” table in the “Additional References” section.
An EtherChannel bundles individual Ethernet links into a single logical link that provides the aggregate bandwidth of up to eight physical links. The Ethernet Virtual Connection Services (EVCS) EtherChannel feature provides support for EtherChannels on service instances.
 Note |
The MAC Address Security on EVC Port Channel services is supported only on bridge domains over Ethernet and is not supported on xconnect services. |
EVCS uses the concepts of EVCs and service instances.
Load balancing is done on an Ethernet flow point (EFP) basis where a number of EFPs exclusively pass traffic through member links.
MAC security is enabled on a service instance by configuring the mac security command. Various MAC security elements can be configured or removed regardless of whether the mac security command is presently configured, but these configurations become operational only when the mac security command is applied.
In this document, the term “secured service instance” is used to describe a service instance on which MAC security is configured. The MAC addresses on a service instance on which MAC security is configured are referred to as “secured MAC addresses.” Secured MAC addresses can be either statically configured (as a permit list) or dynamically learned.
A permit list is a set of MAC addresses that are permitted on a service instance. Permitted addresses permanently configured into the MAC address table of the service instance.
On a service instance that is a member of a bridge domain, the operator is permitted to configure one or more permitted MAC addresses.
For each permitted address, eligibility tests are performed and after the address passes these tests, it is either:
Programmed into the MAC address table of the bridge domain, if MAC security is enabled on the service instance or,
Stored in an area of memory referred to as “MAC table cache” if MAC security is not enabled on the service instance. When MAC security is enabled, the addresses from the MAC table cache are added to the MAC address table as secure addresses.
The eligibility tests performed when a user tries to add a MAC address to the permit list on a service instance are as follows:
If the address is already a denied address on the service instance, the configuration is rejected with an appropriate error message.
If the acceptance of this address would increase the secure address count on the service instance beyond the maximum number allowed, an attempt is made to make room by removing an existing address from the MAC address table. The only candidate for removal is a dynamically learned address on the service instance. If sufficient room cannot be made, the configuration is rejected. If the acceptance of this address would increase the secure address count on the bridge domain beyond the maximum number allowed, an attempt is made to make room by removing an existing address from the MAC address table. The only candidate for removal is a dynamically learned address on the service instance. If room cannot be made, the configuration is rejected.
A deny list is a set of MAC addresses that are not permitted on a service instance. An attempt to learn a denied MAC address will fail. On a service instance that is a member of a bridge domain, the operator is permitted to configure one or more denied MAC addresses. The arrival of a frame with a source MAC address that is part of a deny list will trigger a violation response.
Before a denied address can be configured, the following test is performed:
If the address is already configured as a permitted address on the specific service instance or if the address has been learned and saved as a sticky address on the service instance, the configuration is rejected with an appropriate error message.
In all other cases, the configuration of the denied address is accepted. Typical cases include:
The address is configured as a permitted address on another service instance in the same bridge domain, or the address has been learned and saved as a sticky address on another service instance.
The address is present in the MAC table of the bridge domain as a dynamically learned address on the specific service instance and is deleted from the MAC table before the configuration is accepted.
An upper limit for the number of secured MAC addresses allowed on a bridge domain service instance can be configured. This limit includes addresses added as part of a permit list and dynamically learned MAC addresses.
Before an unknown MAC address is learned, a series of checks are run against a set of configured and operational constraints. If any of these checks fails, the address is not learned, and a configured violation response is triggered.
A static MAC address is specified as permitted on a service instance, by a mac security permit command. A dynamic MAC address is a source MAC address encountered by the service instance that is not present in the MAC table but is allowed into and learned by the MAC address table.
Dynamic MAC address learning occurs when the bridging data path encounters an ingress frame whose source address is not present in the MAC address table for the ingress secured service instance.
The MAC security component is responsible for permitting or denying the addition of the new source address into the MAC table. The following constraints apply:
If a MAC address is to be learned, a check is performed to determine whether the number of secured MAC addresses exceed the maximum number that are permitted to be learned on the individual service instance and on the bridge domain.
A check is performed to determine if the MAC address on an another service instance is learned on a secured service instance in the same bridge domain.
A check is performed to verify if the new dynamic MAC address is in a deny list.
The user can configure the maximum number of MAC addresses that can exist in the MAC table that is associated with a service instance. This number includes statically configured and dynamically learned (including sticky) addresses.
On a service instance that has MAC security enabled and that does not have the maximum number of MAC addresses configured, the number of addresses allowed is one. This means that if the service instance has an associated permit list, that permit list can have only one address, and no addresses are learned dynamically. If the service instance does not have an associated permit list, one MAC address may be learned dynamically.
An upper limit for the number of MAC addresses that can reside in the MAC address table of a bridge domain can be set. This is set independently of the upper limit of secured MAC addresses on the service instance. An attempted violation of this bridge domain MAC address limit will cause the MAC address learn attempt to fail, and the frame to be dropped.
If the bridge domain MAC address limit is not configured, then by default, the maximum number of MAC addresses allowed on a bridge domain is the maximum number that can be supported by that platform.
You can specify the maximum count of MAC table entries on a bridge domain and on a service instance simultaneously. However, there are no restrictions on the count that is configured on the service instance.
The table below shows an example of an initial configuration where three service instances are configured on a bridge domain:
|
Bridge-Domain / Service-Instance Number |
MAC Address Limit |
|---|---|
|
Bridge Domain 1000 |
20 |
|
Service Instance 1001 |
5 |
|
Service Instance 1002 |
10 |
|
Service Instance 1003 |
To be configured |
If you wish to configure MAC security on service instance 1003, any value can be configured for the maximum count. For example:
service instance 1003 ethernet
bridge-domain 1
mac security
mac security maximum addresses 35
A MAC address limit of 35 is permitted, even though the total MAC address limit for the three service instances (5 + 10 + 35) would exceed the count (20) configured on the bridge domain. Note that during actual operation, the bridge domain limit of 20 is in effect. The dynamic secure address count cannot exceed the lowest count applicable, so it is not possible for service instance 1003 to learn 35 addresses.
If a MAC address is present in the MAC address table for a service instance (for example, service instance 1) on which MAC security is configured, the same MAC address cannot be learned on another service instance (for example, service instance 2) in the same bridge domain.
If service instance 2 attempts to learn the same MAC address, the violation response configured on service instance 2 is triggered. If MAC security is not configured on service instance 2 and a violation response is not configured, the “shutdown” response sequence is triggered on service instance 2.
If MAC security is not enabled on service instance 1, the violation is not triggered. service instance 2 learns the MAC address and moves it from service instance 1.
For some platforms, MAC address moves are allowed but moves between secured service instances and nonsecured service instances cannot be detected.
For example, if you do not configure MAC security on service instance 2 because of a hardware limitation, a MAC move from secured service instance 1 to service instance 2 is accepted. Therefore, it is recommended that all service instances within the same bridge-domain be configured as secured service instances.
A violation response is a response to a MAC security violation or a failed attempt to dynamically learn a MAC address due to an address violation. MAC security violations are of two types:
Type 1 Violation --The address of the ingress frame cannot be dynamically learned due to a deny list, or because doing so would cause the maximum number of secure addresses to be exceeded .
Type 2 Violation --The address of the ingress frame cannot be dynamically learned because it is already “present” on another secured service instance .
There are three possible sets of actions that can be taken in response to a violation:
Shutdown
The ingress frame is dropped.
The service instance on which the offending frame arrived is shut down.
The event and the response are logged to SYSLOG.
Restrict
The ingress frame is dropped.
The event and the response are logged to SYSLOG.
Protect
The ingress frame is dropped.
Note |
The ingress frame is dropped silently, without sending any violation report to the SYSLOG. |
If a violation response is not configured, the default response mode is shutdown. The violation response can be configured to protect or restrict mode. A “no” form of a violation response, sets the violation response to the default mode of shutdown.
You are allowed to configure the desired response for a Type 1 and Type 2 violations on a service instance. For a Type 1 violation on a bridge domain (that is, if the learn attempt conforms to the policy configured on the service instance, but violates the policy configured on the bridge domain), the response is always “Protect.” This is not configurable.
In Restrict mode, the violation report is sent to SYSLOG at level LOG_WARNING.
Support for the different types of violation responses depends on the capabilities of the platform. The desired violation response can be configured on the service instance. The configured violation response does not take effect unless and until MAC security is enabled using the mac security command.
A specific time scheduler can be set to age out secured MAC addresses that are dynamically learned or statically configured on both service instances and bridge domains, thus freeing up unused addresses from the MAC address table for other active subscribers.
The set of rules applied to age out secured MAC addresses is called secure aging. By default, the entries in the MAC address table of a secured service instance are never aged out. This includes permitted addresses and dynamically learned addresses.
The mac security aging time aging-time command sets the aging time of the addresses in the MAC address table to <n > minutes. By default, this affects only dynamically learned (not including sticky) addresses--permitted addresses and sticky addresses are not affected by the application of this command.
By default, the aging time <n> configured via the mac security aging time aging-time command is an absolute time. That is, the age of the MAC address is measured from the instant that it was first encountered on the service instance. This interpretation can be modified by using the mac security aging time aging-time inactivity command, which specifies that the age <n> be measured from the instant that the MAC address was last encountered on the service instance.
The mac security aging static and mac security aging sticky commands specify that the mac security aging time aging-time command must be applicable to permitted and sticky MAC addresses, respectively. In the case of permitted MAC addresses, the absolute aging time is measured from the time the address is entered into the MAC address table (for example, when it is configured or whenever the mac security command is entered--whichever is later).
If the mac security aging time command is not configured, the mac security aging static command has no effect.
The ability to make dynamically learned MAC addresses on secured service instances permanent even after interface transitions or device reloads can be set up and configured. A dynamically learned MAC address that is made permanent on a secured service instance is called a “sticky MAC address”. The mac security sticky command is used to enable the sticky MAC addressing feature on a service instance.
With the “sticky” feature enabled on a secured service instance, MAC addresses learned dynamically on the service instance are kept persistent across service instance line transitions and device reloads.
The sticky feature has no effect on statically configured MAC addresses. The sticky addresses are saved in the running configuration. Before the device is reloaded, it is the responsibility of the user to save the running configuration to the startup configuration. Doing this will ensure that when the device comes on, all the MAC addresses learned dynamically previously are immediately populated into the MAC address table.
The mac security sticky address mac-address command can configure a specific MAC address as a sticky MAC address. The use of this command is not recommended for the user because configuring a MAC address as a static address does the same thing. When sticky MAC addressing is enabled by the mac security sticky command, the dynamically learned addresses are marked as sticky and a mac security sticky address mac-address command is automatically generated and saved in the running configuration for each learned MAC address on the service instances.
MAC addresses learned on a service instance that has the sticky behavior enabled are subject to aging as configured by the mac security aging time and mac security aging sticky commands. In other words, for the purpose of aging functionality, sticky addresses are treated the same as dynamically learned addresses.
This section contains a description of the expected behavior of the different MAC security elements when various triggers are applied; for example, configuration changes or link state transitions.
When MAC security is enabled on a service instance, all existing MAC table entries for the service instance are purged. Then, permitted MAC address entries and sticky addresses are added to the MAC table, subject to the prevailing MAC address limiting constraints on the bridge domain.
If MAC address limits are exceeded, any MAC address that fails to get added is reported via an error message to the console, the attempt to enable MAC security on the service instance fails, and the already added permitted entries are backed out or removed.
The aging timer for all entries is updated according to the secure aging rules.
The existing MAC address table entries for this service instance are purged.
This transition sequence applies to all service instances, whether or not they have MAC security configured. All the MAC addresses on this service instance in the MAC address table of the old bridge domain are removed. The count of dynamically learned addresses in the old bridge domain is decremented. Then, all the MAC security commands are permanently erased from the service instance.
All the MAC addresses in the MAC address table that attributable to this service instance are removed, and the count of dynamically learned addresses in the bridge domain is decremented. Since MAC security is applicable only on service instances that are members of a bridge domain, removing a service instance from a bridge domain causes all the MAC security commands to be erased permanently.
All dynamically learned MAC addresses in the MAC address table are removed, and all the other MAC security state values are left unchanged. The only change is that no traffic is forwarded, and therefore no learning can take place.
The MAC tables of all the affected bridge domains are cleared of all the entries attributable to the service instances that are down.
The static and sticky address entries in the MAC tables of the affected bridge domains are re-created to the service instances that are activated.
When the value of the MAC address limit on the service instance is changed initially, a sanity check is performed to ensure that the new value of <n> is greater than or equal to the number of permitted entries. If not, the command is rejected. The MAC table is scanned for addresses that are attributable to this service instance, and dynamically learned MAC addresses are removed when the new MAC address limit is less than the old MAC address limit.
Existing dynamically learned MAC addresses remain unchanged. All new addresses learned become “sticky” addresses.
Disabling sticky addresses causes all sticky secure MAC addresses on the service instance to be removed from the MAC address table. All new addresses learned become dynamic addresses on the service instance and are subject to aging.
Perform this task to enable MAC address security on a service instance.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example:Enters global configuration mode. |
|
Step 3 |
interface type number Example:Specifies the interface type and number, and enters interface configuration mode. |
|
Step 4 |
service instance id ethernet Example:Creates a service instance on an interface and enters service instance configuration mode. |
|
Step 5 |
encapsulation dot1q vlan-id Example:Defines the matching criteria to be used in order to map ingress dot1q frames on an interface to the appropriate service instance. |
|
Step 6 |
bridge-domain bridge-id Example:Binds the service instance to a bridge- domain instance where bridge-id is the identifier for the bridge- domain instance. |
|
Step 7 |
mac security Example:Enables MAC security on the service instance. |
|
Step 8 |
end Example:Returns to user EXEC mode. |
Note |
|
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example:Enters global configuration mode. |
|
Step 3 |
interface port-channel channel-group Example:Specifies the port channel group number and enters interface configuration mode.
|
|
Step 4 |
service instance id ethernet Example:Creates a service instance on an interface and enters service instance configuration mode. |
|
Step 5 |
encapsulation dot1q vlan-id Example:Defines the matching criteria to be used in order to map ingress dot1q frames on an interface to the appropriate service instance. |
|
Step 6 |
bridge-domain bridge-id Example:Binds the service instance to a bridge- domain instance where bridge-id is the identifier for the bridge- domain instance. |
|
Step 7 |
mac security Example:Enables MAC security on the service instance. |
|
Step 8 |
end Example:Returns to user EXEC mode. |
Perform this task to configure permitted MAC addresses on a service instance that is a member of a bridge domain.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example:Enters global configuration mode. |
|
Step 3 |
interface type number Example:Specifies the interface type and number, and enters interface configuration mode. |
|
Step 4 |
service instance id ethernet Example:Creates a service instance (an instance of an EVC) on an interface and enters service instance configuration mode. |
|
Step 5 |
encapsulation dot1q vlan-id Example:Defines the matching criteria to be used for mapping ingress dot1q frames on an interface to the appropriate service instance. |
|
Step 6 |
bridge-domain bridge-id Example:Binds the service instance to a bridge- domain instance where bridge-id is the identifier for the bridge- domain instance. |
|
Step 7 |
mac security address permit mac-address Example:Adds the specified MAC address as a permit MAC address for the service instance. |
|
Step 8 |
mac security address permit mac-address Example:Adds the specified MAC address as a permitted MAC address for the service instance. |
|
Step 9 |
mac security address permit mac-address Example:Adds the specified MAC address as a permitted MAC address for the service instance. |
|
Step 10 |
mac security address permit mac-address Example:Adds the specified MAC address as a permitted MAC address for the service instance. |
|
Step 11 |
mac security address permit mac-address Example:Adds the specified MAC address as a permitted MAC address for the service instance. |
|
Step 12 |
mac security Example:Enables MAC security on the service instance. |
|
Step 13 |
end Example:Returns to user EXEC mode. |
Perform this task to configure a list of MAC addresses that are not allowed on a service instance that is a member of a bridge domain.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example:Enters global configuration mode. |
|
Step 3 |
interface type number Example:Specifies the interface type and number, and enters interface configuration mode. |
|
Step 4 |
service instance id ethernet Example:Creates a service instance (an instance of an EVC) on an interface and enters service instance configuration mode. |
|
Step 5 |
encapsulation dot1q vlan-id Example:Defines the matching criteria to be used in order to map ingress dot1q frames on an interface to the appropriate service instance. |
|
Step 6 |
bridge-domain bridge-id Example:Binds the service instance to a bridge- domain instance where bridge-id is the identifier for the bridge- domain instance. |
|
Step 7 |
mac security address deny mac-address Example:Adds the specified MAC address as a denied MAC address for the service instance. |
|
Step 8 |
mac security address deny mac-address Example:Adds the specified MAC address as a denied MAC address for the service instance. |
|
Step 9 |
mac security address deny mac-address Example:Adds the specified MAC address as a denied MAC address for the service instance. |
|
Step 10 |
mac security address deny mac-address Example:Adds the specified MAC address as a denied MAC address for the service instance. |
|
Step 11 |
mac security address deny mac-address Example:Adds the specified MAC address as a denied MAC address for the service instance. |
|
Step 12 |
mac security Example:Enables MAC security on the service instance. |
|
Step 13 |
end Example:Returns to user EXEC mode. |
Perform this task to configure an upper limit for the number of secured MAC addresses that reside in a bridge domain.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
bridge-domain bridge-id Example: |
Configures components on a bridge domain and enters bridge-domain configuration mode. |
|
Step 4 |
mac limit maximum addresses maximum-addresses Example: |
Sets the MAC limit maximum addresses. |
|
Step 5 |
end Example: |
Returns to user EXEC mode. |
Perform this task to configure an upper limit for the number of secured MAC addresses allowed on a service instance. This number includes addresses added as part of a permit list as well as dynamically learned MAC addresses. If the upper limit is decreased, all learned MAC entries are removed. If the upper limit is decreased, one or more learned MAC entries may be removed. The EFP secure MAC address limitation range is [1-1024], so the maximum is 1024.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
interface type number Example: |
Specifies the interface type and number, and enters interface configuration mode. |
|
Step 4 |
service instance id ethernet Example: |
Creates a service instance (an instance of an EVC) on an interface and enters service instance configuration mode. |
|
Step 5 |
encapsulation dot1q vlan-id Example: |
Defines the matching criteria to be used to map ingress dot1q frames on an interface to the appropriate service instance. |
|
Step 6 |
bridge-domain bridge-id Example: |
Binds the service instance to a bridge- domain instance where bridge-id is the identifier for the bridge- domain instance. |
|
Step 7 |
mac security maximum addresses Example: |
Sets the maximum number of secure addresses permitted on the service instance. |
|
Step 8 |
mac security Example: |
Enables MAC security on the service instance. |
|
Step 9 |
end Example: |
Returns to user EXEC mode. |
Perform this task to specify the expected behavior of a device when an attempt to dynamically learn a MAC address fails because the configured MAC security policy on the service instance was violated.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example:Enters global configuration mode. |
|
Step 3 |
interface type number Example:Specifies the interface type and number, and enters interface configuration mode. |
|
Step 4 |
service instance id ethernet Example:Creates a service instance (an instance of an EVC) on an interface and enters service instance configuration mode. |
|
Step 5 |
encapsulation dot1q vlan-id Example:Defines the matching criteria to be used to map ingress dot1q frames on an interface to the appropriate service instance. |
|
Step 6 |
bridge-domain bridge-id Example:Binds the service instance to a bridge- domain instance where bridge-id is the identifier for the bridge- domain instance. |
|
Step 7 |
Do one of the following:
Example:Example:Sets the violation mode (for Type 1 and 2 violations) to restrict. or Sets the violation mode (for Type 1 and 2 violations) to protect.
|
|
Step 8 |
mac security Example:Enables MAC security on the service instance. |
|
Step 9 |
end Example:Returns to user EXEC mode. |
Perform this task to configure the aging of secured MAC addresses under MAC security. Secured MAC addresses are not subject to the normal aging of MAC table entries. If aging is not configured, secured MAC addresses are never aged out.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example:Enters global configuration mode. |
|
Step 3 |
interface type number Example:Specifies the interface type and number, and enters interface configuration mode. |
|
Step 4 |
service instance id ethernet Example:Creates a service instance (an instance of an EVC) on an interface and enters service instance configuration mode. |
|
Step 5 |
encapsulation dot1q vlan-id Example:Defines the matching criteria to be used in order to map ingress dot1q frames on an interface to the appropriate service instance. |
|
Step 6 |
bridge-domain bridge-id Example:Binds the service instance to a bridge- domain instance where bridge-id is the identifier for the bridge- domain instance. |
|
Step 7 |
mac security aging time aging-time [ inactivity ] Example:Sets the aging time for secure addresses, in minutes. The optional inactivity keyword specifies that the aging out of addresses is based on inactivity of the sending hosts (as opposed to absolute aging). |
|
Step 8 |
mac security Example:Enables MAC security on the service instance. |
|
Step 9 |
end Example:Returns to user EXEC mode. |
If sticky MAC addressing is configured on a secured service instance, MAC addresses that are learned dynamically on the service instance are retained during a link-down condition. Perform this task to configure sticky MAC addresses on a service instance.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example:Enters global configuration mode. |
|
Step 3 |
interface type number Example:Specifies the interface type and number, and enters interface configuration mode. |
|
Step 4 |
service instance id ethernet Example:Creates a service instance (an instance of an EVC) on an interface and enters service instance configuration mode. |
|
Step 5 |
encapsulation dot1q vlan-id Example:Defines the matching criteria to be used to map ingress dot1q frames on an interface to the appropriate service instance. |
|
Step 6 |
bridge-domain bridge-id Example:Binds the service instance to a bridge- domain instance where bridge-id is the identifier for the bridge- domain instance. |
|
Step 7 |
mac security sticky address mac-address Example:Sets up a MAC address to be declared as a sticky MAC address on the service instance. |
|
Step 8 |
mac security Example:Enables MAC security on the service instance. |
|
Step 9 |
end Example:Returns to user EXEC mode. |
Perform this task to display the MAC security status of a service instance.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
show ethernet service instance id id interface type number mac security Example:Displays the MAC security status of a specific service instance. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
Perform this task to display all the service instances with MAC security enabled.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
show ethernet service instance mac security Example:Displays all the service instances with MAC security enabled. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
Perform this task to display the service instances on a specific bridge domain that have MAC security enabled.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
show bridge-domain id mac security Example:Displays all the service instances with MAC security enabled on a specific bridge domain. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
show ethernet service instance mac security address Example:Displays the secured addresses on all the service instances. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
show ethernet service instance id id interface type number mac security address Example:Displays the addresses of a specific service instance. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
show bridge-domain id mac security address Example:Displays the secured addresses of all the service instances on a specified bridge domain. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
This section describes how to display the MAC security statistics of a specific service instance.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
show ethernet service instance id id interface type number mac security statistics Example:Displays the MAC security statistics of a specific service instance. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
Perform this task to display the MAC security statistics of all the service instances on a specific bridge domain.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
show bridge-domain bridge-id mac security statistics Example:Displays the MAC security statistics of all service instances that belong to a specific bridge domain. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
Perform this task to display the last violation recorded on each service instance on a specific bridge domain. Service instances on which there have been no violations are excluded from the output.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
show bridge-domain bridge-id mac security last violation Example:Displays information about the last violation recorded on each of the service instances that belong to the bridge domain. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
Perform this task to clear all dynamically learned Secure MAC addresses on a service instance.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
clear ethernet service instance id id interface type number mac table Example:Clears all the dynamically learned Secure MAC addresses on the specified service instance. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
Perform this task to clear all dynamically learned MAC addresses on a bridge domain.
|
Step 1 |
enable Example:Enables privileged EXEC mode.
|
|
Step 2 |
clear bridge-domain bridge-id mac table Example:Clears all dynamically learned MAC addresses on the specified bridge domain. |
|
Step 3 |
end Example:Returns to user EXEC mode. |
Perform this task to bring a specific service instance out of the error-disabled state.
| Command or Action | Purpose | |
|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
|
Step 3 |
interface type number Example: |
Specifies the interface type and number, and enters interface configuration mode. |
|
Step 4 |
service instance id ethernet Example: |
Creates a service instance (an instance of an EVC) on an interface and enters service instance configuration mode. |
|
Step 5 |
encapsulation dot1q vlan-id Example: |
Defines the matching criteria to be used to map ingress dot1q frames on an interface to the appropriate service instance. |
|
Step 6 |
bridge-domain bridge-id Example: |
Binds the service instance to a bridge-domain instance where bridge-id is the identifier for the bridge-domain instance. |
|
Step 7 |
mac security Example: |
Enables MAC security on the service instance. |
|
Step 8 |
end Example: |
Returns to user EXEC mode. |
The following example shows how to enable MAC security on a service instance:
Device> enable
Device# configure terminal
Device(config)# interface gigabitethernet 3/0/1
Device(config-if)# service instance 100 ethernet
Device(config-if-srv)# encapsulation dot1Q 100
Device(config-if-srv)# bridge-domain 100
Device(config-if-srv)# mac security
Device(config-if-srv)# end
The following example shows how to enable MAC Security on an EVC port channel:
Device> enable
Device# configure terminal
Device(config)# interface port-channel 2
Device(config-if)# service instance 100 ethernet
Device(config-if-srv)# encapsulation dot1Q 100
Device(config-if-srv)# bridge-domain 100
Device(config-if-srv)# mac security
Device(config-if-srv)# end
The following example shows how to configure a MAC address permit list:
The following example shows how to configure a MAC address deny list:
Device> enable
Device# configure terminal
Device(config)# interface gigabitethernet 3/0/1
Device(config-if)# service instance 100 ethernet
Device(config-if-srv)# encapsulation dot1Q 100
Device(config-if-srv)# bridge-domain 100
Device(config-if-srv)# mac security address deny a2aa.aaaa.aaaa
Device(config-if-srv)# mac security address deny a2aa.aaaa.aaab
Device(config-if-srv)# mac security address deny a2aa.aaaa.aaac
Device(config-if-srv)# mac security address deny a2aa.aaaa.aaad
Device(config-if-srv)# mac security address deny a2aa.aaaa.aaae
Device(config-if-srv)# mac security
Device(config-if-srv)# end
Device> enable
Device# configure terminal
Device(config)# bridge-domain 100
Device(config-bdomain)# mac limit maximum addresses 1000
Device(config-bdomain)# end
Device> enable
Device# configure terminal
Device(config)# interface gigabitethernet 3/0/1
Device(config-if)# service instance 100 ethernet
Device(config-if-srv)# encapsulation dot1Q 100
Device(config-if-srv)# bridge-domain 100
Device(config-if-srv)# mac security maximum addresses 10
Device(config-if-srv)# mac security
Device(config-if-srv)# end
Device> enable
Device# configure terminal
Device(config)# interface gigabitethernet 3/0/1
Device(config-if)# service instance 100 ethernet
Device(config-if-srv)# encapsulation dot1Q 100
Device(config-if-srv)# bridge-domain 100
Device(config-if-srv)# mac security address permit a2aa.aaaa.aaaa
Device(config-if-srv)# mac security violation protect
Device(config-if-srv)# mac security
Device(config-if-srv)# end
Device> enable
Device# configure terminal
Device(config)# interface gigabitethernet 4/0/1
Device(config-if)# service instance 100 ethernet
Device(config-if-srv)# encapsulation dot1q 100
Device(config-if-srv)# bridge-domain 100
Device(config-if-srv)# mac security aging time 10
Device(config-if-srv)# mac security
Device(config-if-srv)# end
Device> enable
Device# configure terminal
Device(config)# interface gigabitethernet 3/0/1
Device(config-if)# service instance 100 ethernet
Device(config-if-srv)# encapsulation dot1Q 100
Device(config-if-srv)# bridge-domain 100
Device(config-if-srv)# mac security sticky address 1111.2222.3333
Device(config-if-srv)# mac security
|
Related Topic |
Document Title |
|---|---|
|
CFM commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples |
Cisco IOS Carrier Ethernet Command Reference |
|
Configuring Ethernet connectivity fault management in a service provider network (Cisco pre-Standard CFM Draft 1) |
"Configuring Ethernet Connectivity Fault Management in a Service Provider Network” module in the Cisco IOS Carrier Ethernet Configuration Guide |
|
Ethernet Local Management Interface on a provider edge device |
"Configuring Ethernet Local Management Interface on a Provider Edge Device” module in the Cisco IOS Carrier Ethernet Configuration Guide |
|
IP SLAs for Metro Ethernet |
"IP SLAs for Metro Ethernet" |
|
NSF/SSO and MPLS |
"NSF/SSO - MPLS LDP and LDP Graceful Restart" |
|
ISSU feature and functions |
"Cisco IOS Broadband High Availability In Service Software Upgrade" |
|
Performing an ISSU |
"Cisco IOS In Service Software Upgrade Process and Enhanced Fast Software Upgrade Process" |
|
SSO |
“Stateful Switchover” chapter of the Cisco IOS High Availability Configuration Guide |
|
Standard |
Title |
|---|---|
|
IEEE 802.1ag Standard |
802.1ag - Connectivity Fault Management |
|
IEEE 802.3ah |
IEEE 802.3ah Ethernet in the First Mile |
|
IETF VPLS OAM |
L2VPN OAM Requirements and Framework |
|
ITU-T |
ITU-T Y.1731 OAM Mechanisms for Ethernet-Based Networks |
|
MIB |
MIBs Link |
|---|---|
|
CISCO-ETHER-CFM-MIB |
To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL: |
|
RFC |
Title |
|---|---|
|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified. |
-- |
|
Description |
Link |
|---|---|
|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
MAC Address Limiting on Service Instances and Bridge Domains |
Cisco IOS XE 3.7S Cisco IOS XE Gibraltar 16.11.a |
The MAC Address Limiting on Service Instances and Bridge Domains feature addresses port security with service instances by providing the capability to control and filter MAC address learning behavior at the granularity of a per-service instance. When a violation requires a shutdown, only the customer that is assigned to a given service instance is affected. MAC address limiting is a type of MAC security and is also referred to as a MAC security component or element. The following commands were introduced or modified: bridge-domain (global), bridge-domain (service instance), clear bridge-domain mac-table, clear ethernet service instance, errdisable recovery cause mac-security, interface, mac limit maximum addresses,mac security,show bridge-domain, show ethernet service instance . Support was added in Cisco IOS XE Gibraltar 16.11.a for Cisco ASR 1000 Series Aggregation Services Routers, Cisco Cloud Services Router 1000v, and Cisco 4000 Series Integrated Services Routers. |
Feedback