Configuring static VLAN per-port settings
[no] vlan vid
This command, used with the options listed below, changes the name of an existing static VLAN and the per-port VLAN membership settings.
tagged port-list
Configures the indicated port as Tagged for the specified VLAN. The no version sets the port to either No or (if GVRP is enabled) to Auto .
untagged port-list
Configures the indicated port as Untagged for the specified VLAN. The no version sets the port to either No or (if GVRP is enabled) to Auto .
forbid port-list
Used in port-based VLANs configures port-list as forbidden, to become a member of the specified VLAN, and other actions. Does not operate with option not allowed protocol VLANs. The no version sets the port to either No or (if GVRP is enabled) to Auto .
auto port-list
Available if GVRP is enabled on the switch. Returns the per-port settings for the specified VLAN to Auto operation. Auto is the default per-port setting for a static VLAN if GVRP is running on the switch.
Changing the VLAN name and set ports to tagged
Suppose there is a VLAN named VLAN100 with a VID of 100, and all ports are set to No for this VLAN. To change the VLAN name to Blue_Team and set ports A1 - A5 to Tagged, use the following commands:
Moving the context level
To move to the vlan 100 context level and execute the same commands:
Changing tagged ports
To change the tagged ports in the above examples to No (or Auto , if GVRP is enabled), use either of the following commands.
At the global configuration level, use:
At the VLAN 100 context level, use:
Using IP enable/disable for all VLANs
You can administratively disable the IP address on specified VLANs with static IP addresses without removing the Layer 3 configuration. The switch can be pre-configured as a backup router, then quickly transition from backup to active by re-enabling Layer 3 routing on one or more VLANs. While the switch is in “backup” mode, it will still performing Layer 2 switching.
A MIB object will be toggled to make Layer 3 routing active or inactive on a VLAN.
Interaction with other features
This feature affects management access to the switch as follows:
IP—SNMP, Telnet, SSH, HTTP, TFTP, SCP, SFTP
Routing—RIP, OSPF, PIM, VRRP
When the disable layer3 command is configured on a VLAN, the behavior is as if no IP address were configured for that VLAN. There is no other change in behavior.
[ no ] disable layer3 vlan [ vid vid range ]
In the configuration context, turns off Layer 3 routing for the specified VLAN or VLANs. When executed in vlan context, turns off Layer 3 routing for that VLAN. The no form turns on Layer 3 routing for the specified VLAN or VLANs. If QinQ is enabled, svlan can be configured as well.
The show ip command displays disabled in the display column if Layer 3 has been disabled, or if the VLAN has no IP configuration. You can tell which is the case by viewing the remaining columns; if there is no IP configuration, the remaining columns are blank.
Viewing a VLAN disabled for Layer 3
For IPv6, the Layer 3 Status field displays the status of Layer 3 on that VLAN.
Viewing IPv6 Layer 3 status for a VLAN
Interactions with DHCP
Disabling Layer 3 functionality and DHCP are mutually exclusive, with DHCP taking precedence over disable layer3 on a VLAN. The following interactions occur:
If the disable layer3 command is executed when DHCP is already configured, no disabling of the VLAN occurs. This error message displays: Layer 3 cannot be disabled on a VLAN that has DHCP enabled .
From the CLI: If disable layer3 is configured already, and an attempt is made to configure DHCP, DHCP takes precedence and will be set. The warning message displays: Layer 3 has also been enabled on this VLAN since it is required for DHCP .
From the CLI: When disabling a range of VLAN IDs, this warning message displays: Layer 3 will not be disabled for any LANs that have DHCP enabled .
From SNMP: If the disable layer3 command is executed when DHCP is already configured, no disabling of the VLAN occurs. An INCONSISTENT_VALUE error is returned.
From SNMP: If disable layer3 is configured already, and an attempt is made to configure DHCP, DHCP takes precedence and will be set.
Copyright © 2015 Hewlett-Packard Development Company, L.P.
IMAGES
COMMENTS
The Menu interface enables configuration and display of port-based VLANs only. The CLI configures and displays port-based and protocol-based VLANs. In the factory default state, the switch is enabled for up to 256 VLANs, all ports belong to the default primary VLAN and are in the same broadcast/multicast domain.
Port-based VLAN port assignment screen in the menu interface NOTE: The "VLAN Port Assignment" screen displays up to 32 static, port-based VLANs in ascending order, by VID. If the switch configuration includes more than 32 such VLANs, use the following CLI command to list data on VLANs having VIDs numbered sequentially higher than the first 32.
The show vlans command lists this data when GVRP is enabled and at least one port on the switch has dynamically joined the designated VLAN. HP Switch(config)#: show vlans 22 Status and Counters - VLAN Information - VLAN 22 VLAN ID : 33 Name : GVRP_33 Status : Dynamic Voice : No Jumbo : No Port Information Mode Unknown VLAN Status ...
at least one VLAN. HP routing switches support up to 4,096 port-based VLANs with a default of 8. Protocol-based VLANs By supporting the grouping of like protocols, protocol-based VLANs reduce the number of non-essential broadcasts on other ports by keeping all broadcasts for a given protocol within a defined VLAN.
Learn how to do an HP Switch Vlan configuration using the command-line, by following this simple step-by-step tutorial, you will be able to create a new Vlan and associate a Switch port to a specific Vlan.
same protocol. For example, a port-based VLAN cannot contain both an IP protocol VLAN and an IP sub-net VLAN. Layer 2 Port-Based VLANs A port-based VLAN is a subset of ports on a device that constitutes a Layer 2 broadcast domain. By default, all the ports on a device are members of the default VLAN. Thus, all the ports on the device constitute
HP ProCurve Switch 2512M, 2524M, A6713A, A6716A, A6717A; Note: If a switch is a Commander, the Stack options will appear at the top of the page. Note: When multiple VLANs exist on a switch, only one VLAN can be untagged for each port. When you first add a VLAN to a switch, the default setting on that VLAN is No for all ports.
Learn how to do an HP Switch Vlan configuration using the web interface, by following this simple step-by-step tutorial, you will be able to create a new Vlan and associate a Switch port to a specific Vlan.
Nov 28, 2013 · Well if you have HP Switches you have additional options to the 2 mentioned by mpk: In the HP switch configuration guide you will find the following: The modes are: •Tagged - When a port is tagged, it allows communication among the different VLANs to which it is assigned. •Untagged - When a port is untagged, it can only be a member on one VLAN.
HP Switch(config)#: vlan 100 HP Switch(vlan-100)#: name Blue_Team HP Switch(vlan-100)#: tagged a1-a5 Changing tagged ports To change the tagged ports in the above examples to No (or Auto , if GVRP is enabled), use either of the following commands.