Configure Media Access Control (MAC)-Based Virtual Local Area Network (VLAN) Groups to VLAN on a Switch

Objective

A Virtual Local Area Network (VLAN) allows you to logically segment a Local Area Network (LAN) into different broadcast domains. In scenarios where sensitive data may be broadcast on a network, VLANs can be created to enhance security by designating a broadcast to a specific VLAN. Only users that belong to a VLAN are able to access and manipulate the data on that VLAN. VLANs can also be used to enhance performance by reducing the need to send broadcasts and multicasts to unnecessary destinations.

Networking devices on which multiple protocols are running cannot be grouped to a common VLAN. Non-standard devices are used to pass traffic between different VLANs in order to include the devices participating in a specific protocol. For this reason, the user cannot take advantage of the many features of VLAN.

VLAN groups are used to load balance the traffic on a Layer 2 network. The packets are distributed with respect to different classifications and are assigned to VLANs. Many different classifications exist, and if more than one classification scheme is defined, the packets are assigned to the VLAN in this order:

• Tag — The VLAN number is recognized from the tag.
• MAC-Based VLAN — The VLAN is recognized from the source Media Access Control (MAC)-to-VLAN mapping of the ingress interface.
• Subnet-Based VLAN — The VLAN is recognized from the source Subnet-to-VLAN mapping of the ingress interface. To learn how to configure this feature, click here for instructions.
• Protocol-Based VLAN — The VLAN is recognized from the Ethernet type Protocol-to-VLAN mapping of the ingress interface. To learn how to configure this feature, click here for instructions.
• PVID — VLAN is recognized from the port default VLAN ID.

The MAC-based VLAN classification enable packets to be classified according to their source MAC address. You can then define MAC-to-VLAN mapping per interface. You can also define several MAC-based VLAN groups, which each group containing different MAC addresses. These MAC-based groups can be assigned to specific ports or LAGs. MAC-based VLAN groups cannot contain overlapping ranges of MAC addresses on the same port.

This article provides instructions on how to configure MAC-Based groups on a switch.

If you are unfamiliar with terms in this document, check out Cisco Business: Glossary of New Terms.

Applicable Devices

• Sx350 Series
• SG350X Series
• Sx500 Series
• Sx550X Series

Software Version

• 1.4.7.05 – Sx500 Series
• 2.2.5.68 – Sx350 Series, Sx350X Series, Sx550X Series

Configure MAC-Based VLAN Groups to VLAN on the Switch

Map a MAC-Based VLAN Group to VLAN

Important: Before proceeding with the instructions below, make sure a MAC-Based VLAN group has already been configured. For instructions, click here.

Step 1. Log in to the web-based utility and chooseAdvanced from the Display Mode drop-down list.

Note: If you have an Sx500 Series switch, skip to Step 2.

Step 2. Choose VLAN Management >VLAN Groups > MAC-Based Groups to VLAN.

Note: The available menu options may vary depending on the device model. In this example, SG350X-48MP is used.

Step 3. In the Mapping Group to VLAN Table, click Add.

Step 4. The type of the group is displayed in the Group Type area automatically. Click one of the following interface type radio buttons in the Interface area to which the VLAN MAC-based group is assigned and choose the desired interface from the drop-down list.

The options are:

• Unit — From the Unit and Port drop-down lists choose the port to configure. The unit identifies whether the switch is the active or member in the stack.

Note: If you have an Sx500 Series switch, this option displays as Unit/Slot. The slot identifies which switch is connected to which slot. For example, Slot 1 is SF500 and Slot 2 is SG500.

• LAG — Choose the desired LAG from the LAG drop-down list. A Link Aggregate Group (LAG) is used to link multiple ports together. LAGs multiply bandwidth, increase port flexibility, and provide link redundancy between two devices to optimize port usage.

Note: In this example, Port GE20 of Unit 2 is used.

Step 5. From the Group ID drop-down list, choose the MAC-Based VLAN Group ID to filter the traffic through the chosen port or LAG.

Note: In this example, 5 is used.

Step 6. Enter the VLAN ID to which the traffic from the VLAN group is forwarded in the VLAN ID field.

Note: In this example, 30 is used. To know how to configure VLAN settings on your switch, click here for instructions.

Step 7. Click Apply then click Close. This mapping does not bind the interface dynamically to the VLAN; the interface must be manually added to the VLAN.

Step 8. (Optional) Click Save to save settings to the startup configuration file.

You should now have mapped a MAC-Based VLAN group to a VLAN on your switch.

Edit MAC-Based VLAN Group

Step 1. Choose VLAN Groups > MAC-Based Groups to VLAN.

Step 2. In the Mapping Group to VLAN Table, check the box next to the MAC-Based VLAN group you would like to edit.

Note: In this example, GE2/20 is clicked.

Step 3. Click the Edit button to edit a mapped MAC-Based VLAN group.

Step 4. (Optional) Enter the VLAN ID to which the traffic from the VLAN group is forwarded in the VLAN ID field.

Note: In this example, 20 is used.

Step 5. Click Apply then click Close.

Step 6. (Optional) Click Save to save settings to the startup configuration file.

The MAC-Based VLAN group mapping should now have been edited from your switch.

Delete MAC-Based VLAN Group

Step 1. Choose VLAN Groups > MAC-Based Groups to VLAN.

Step 2. In the Mapping Group to VLAN Table, check the box next to the MAC-Based VLAN group you would like to delete.

Note: In this example, GE2/20 is clicked.

Step 3. Click the Delete button to delete the MAC-Based VLAN group.

Step 4. (Optional) Click Save to save settings to the startup configuration file.

The MAC-Based VLAN group mapping should now have been deleted from your switch.

You should now have configured MAC-Based VLAN groups to VLAN on your switch.

Revision History

Revision	Publish Date	Comments
1.0	13-Dec-2018	Initial Release