This article provides instructions on how to configure subnet-based groups on a Cisco Business 350 series switch through the CLI.
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.
To learn how to configure the VLAN settings on your switch through the web-based utility, click here. For CLI-based instructions, click here.
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, you 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:
To configure Subnet-based VLAN groups on your switch, follow these guidelines:
1. Create the VLANs. To learn how to configure the VLAN settings on your switch through the web-based utility, click here. For CLI-based instructions, click here.
2. Configure interfaces to VLANs. For instructions on how to assign interfaces to VLANs through the web-based utility of your switch, click here. For CLI-based instructions, click here.
If the interface does not belong to the VLAN, the subnet-based groups to VLAN configuration setting will not take effect.
3. Configure subnet-based VLAN groups. For instructions on how to configure subnet-based VLAN Groups through the web-based utility of your switch, click here.
4. (Optional) You can also configure the following:
MAC-based VLAN Groups Overview - For instructions on how to configure subnet-based VLAN Groups through the web-based utility of your switch, click here. For CLI-based instructions, click here.
Protocol-based VLAN Groups Overview - For instructions on how to configure Protocol-based VLAN Groups through the web-based utility of your switch, click here. For CLI-based instructions, click here.
The subnet-based group VLAN classification enables packets to be classified according to their subnet. You can then define subnet-to-VLAN mapping per interface. You can also define several subnet-based VLAN groups, which each group containing different subnets. These groups can be assigned to specific ports or LAGs. Subnet-based VLAN groups cannot contain overlapping ranges of subnets on the same port.
Forwarding of packets based on their IP subnet requires setting up groups of IP subnets and then mapping these groups to VLANs.
Log in to the switch console. The default username and password is cisco/cisco. If you have configured a new username or password, enter the credentials instead.
The commands may vary depending on the exact model of your switch.
From the Privileged EXEC mode of the switch, enter the Global Configuration mode by entering the following:
CBS350#configure
In the Global Configuration mode, configure a subnet-based classification rule by entering the following:
CBS350(config)#vlan database
To map an IP subnet to a group of IP subnets, enter the following:
CBS350(config)#map subnet [ip-address] [prefix-mask] subnets-group [group-id]
The options are:
To exit the Interface Configuration context, enter the following:
CBS350(config)#exit
You have now configured the subnet-based VLAN groups on your switch through the CLI.
In the Global Configuration mode, enter the Interface Configuration context by entering the following:
CBS350#interface-id | range interface-range]
The options are:
In the Interface Configuration context, use the switchport mode command to configure the VLAN membership mode:
CBS350(config-if)#switchport mode general
To return the port to the default VLAN, enter the following:
CBS350(config-if)#no switchport mode general
To configure a subnet-based classification rule, enter the following:
CBS350(config-if)#switchport general map subnets-group [group] vlan [vlan-id]
The options are:
In this example, the interface is assigned to subnet-based group 10 which is mapped to VLAN 30.
To exit the Interface Configuration context, enter the following:
CBS350(config-if)#exit
To remove the classification rule from the port or range of ports, enter the following:
CBS350(config-if)#no switchport general map subnets-groups group
Repeat steps 1 to 6 to configure more general ports and assign to the corresponding subnet-based VLAN groups.
Enter the end command to go back to the Privileged EXEC mode:
CBS350(config-if-range)#end
You have now mapped subnet-based VLAN groups to the VLANs on your switch through the CLI.
To display the subnet addresses that belong to the defined subnet-based classification rules, enter the following in the Privileged EXEC mode:
CBS350#show vlan subnets-groups
To display the classification rules of a specific port on the VLAN, enter the following:
CBS350#show interfaces switchport [interface-id]
Each port mode has its own private configuration. The show interfaces switchport command displays all these configurations, but only the port mode configuration that corresponds to the current port mode displayed in Administrative Mode area is active.
In the Privileged EXEC mode of the switch, save the configured settings to the startup configuration file, by entering the following:
CBS350#copy running-config startup-config
Press Y for Yes or N for No on your keyboard once the Overwrite file [startup-config]… prompt appears.
You have now displayed the subnet-based VLAN group and port configuration settings on your Cisco Business 350 series switch.
To proceed with configuring the VLAN group settings on your switch, follow the guidelines above.
Revision | Publish Date | Comments |
---|---|---|
1.0 |
26-Jan-2021 |
Initial Release |