business plan

re assign ports

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

Change the listening port for Remote Desktop on your computer

Applies to: Windows Server 2022, Windows 10, Windows 8.1, Windows 8, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2, Windows Server 2008 R2

When you connect to a computer (either a Windows client or Windows Server) through the Remote Desktop client, the Remote Desktop feature on your computer "hears" the connection request through a defined listening port (3389 by default). You can change that listening port on Windows computers by modifying the registry.

The next time you connect to this computer by using the Remote Desktop connection, you must type the new port. If you're using a firewall, make sure to configure your firewall to permit connections to the new port number.

You can check the current port by running the following PowerShell command:

For example:

You can also change the RDP port by running the following PowerShell command. In this command, we'll specify the new RDP port as 3390 .

To add a new RDP Port to the registry:

Submit and view feedback for

Additional resources

Vault Products

re assign ports

How to re-assign HTTP ports and hostname used by Vault

re assign ports

0 contributions

Adding or Changing TCP/UDP Port Assignments

TCP and UDP are Transport layer protocols in the IP protocol suite. These transport layer protocols use ports to establish communication between application layer protocols. For example, all Web traffic uses the HTTP protocol. HTTP is an application layer protocol that uses the standard TCP/UDP port 80. The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the list of standard port numbers and their assignments. For an up-to-date listing of all standard TCP/UDP port assignments, visit www.iana.org .

When the analyzer reads a TCP, UDP or IPX packet, it infers the upper layer protocols by using pre-defined rules of traversal. For example, if the packet has a TCP source or destination port number 80, then the upper layer protocol is HTTP. These rules, which are built in to the software, determine the upper layers of the protocol stack based on the source or destination port numbers in the packet. The built-in rules are based on the standard port assignments. However, it is quite common to come across network systems in which upper layer protocols use user-defined port numbers for both standard and custom protocols. In such cases, the analyzer users can tell the software which port numbers are assigned to which protocols.

The analyzer autotraverses the stack from TCP, UDP and IPX based on the source or destination port number. Many systems use user-defined port numbers for both standard and custom protocols. Here’s how to tell the analyzer about a custom port assignment on the system you are monitoring.

Add a New Port Assignment

The system adds the new entry to the bottom of the port number list.

Modify an Existing Port Assignment

The system displays the changes in port assignment.

Delete a Port Assignment

The system deletes the port assignment.

Move a Port Assignment

If you need to move an entry to ensure it is processed before or after another entry, select the entry in the list and then click the Move Up or Move Down buttons.

Port Assignment Considerations

Help Categories

Additional Help

Get to Know Us

Industrial Network Infrastructure

Industrial Edge Connectivity

Industrial Computing

Industry Focus

Technology Focus

Don't Miss Out

Discover how our IIoT edge gateways use cloud services to simplify the integration of edge data.

Secure Your OT Networks

Explore our article library for a wealth of expert advice on improving your industrial network security.

Learn how to unlock the secrets of your OT data to succeed with your industrial digital transformation.

Product Support

Product FAQs

Repair & Warranty

Still need assistance with your Moxa product?

Get in Touch

Get to Know Moxa

We strive to implement environmental practices that have a positive impact.

Bringing out the best in our people is how we grow and succeed together.

Please sign in

How do i change the default com port setting for multiport serial boards.

Some user applications may use a specific COM port requiring a change in the default COM port setting for multiport serial boards.

To change the default COM port used to communicate with multiport serial boards, do the following:

faq-382-1.png

faq-382-3.png

Relevant Products

CP-102E/102EL Series · CP-102U/102UL Series · CP-104EL-A Series · CP-104UL/104JU Series · CP-116E-A · CP-118E-A-I/138E-A-I Series · CP-118EL-A · CP-118U/138U Series · CP-132EL Series · CP-132UL Series · CP-134EL-A-I Series · CP-134U Series · CP-168EL-A ·

Related Articles

Contact Moxa Support

Still need assistance with your Moxa product? Get help and save time by initiating an online support request and we will connect you to an expert.

This site uses cookies in order to improve your user experience and to provide content tailored specifically to your interests. By continuing to browse our site without changing your cookie settings (click the Learn More button for more information), or by clicking the OK button below, you hereby acknowledge and agree to our Privacy Policy and use of cookies.

{{ product.name }}

Service Name and Transport Protocol Port Number Registry

re assign ports

Contact Information

Configure Port to VLAN Interface Settings on a Switch through the CLI

Available languages, download options.

Bias-Free Language

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.

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.

You can configure the ports and specify whether the port should be in access or trunk mode, and assign specific ports to VLANs. This article provides instructions on how to configure an interface VLAN as an access or trunk port on your switch through the Command Line Interface (CLI).

Introduction

VLAN is a network that is usually segmented by function or application. VLANs behave much like physical LANs, but you can group hosts even if they are not physically co-located. A switch port can belong to a VLAN. Unicast, broadcast, and multicast packets are forwarded and flooded out ports in the same VLAN.

VLANs can also be used to enhance performance by reducing the need to send broadcasts and multicasts to unnecessary destinations. It also eases network configuration by logically connecting devices without physically relocating those devices.

Note: To learn how to configure the VLAN settings on your switch through the web-based utility, click here . For CLI-based instructions, click here .

The image below displays an SG350X switch that is configured with the following VLANs:

re assign ports

In a bigger network, the configured VLANs with interfaces assigned as access and trunk ports on switches could look like this:

re assign ports

The port modes are defined as follows:

Note: By default, all interfaces are in trunk mode, which means they can carry traffic for all VLANs. To know how to assign an interface VLAN as an Access or Trunk port through the web-based utility of the switch, click here .

To configure VLANs, 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. (Optional) Set the desired VLAN-related configuration for ports. For instructions on how to configure the VLAN interface settings on your switch through the web-based utility, click here . For CLI-based instructions, click here .

3. Assign interfaces to VLANs. For instructions on how to assign interfaces to VLANs through the web-based utility of your switch, click here .

4. (Optional) Configure VLAN groups on your switch. You can configure any of the following:

5. (Optional) Configure TV VLAN settings on your switch. You can configure any of the following:

Applicable Devices | Software Version

Configure VLAN Interface Settings on the Switch through the CLI

Configure interface as access port and assign to vlan.

Step 1. 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.

re assign ports

Note: The commands may vary depending on the exact model of your switch. In this example, the SG350X switch is accessed through Telnet.

Step 2. To display the current VLAN on the switch, enter the following:

re assign ports

Note: In this example, VLANs 1, 10, 20, and 30 are available with no manually assigned ports.

Step 3. From the Privileged EXEC mode of the switch, enter the Global Configuration mode by entering the following:

Step 4. In the Global Configuration mode, enter the Interface Configuration context by entering the following:

The options are:

re assign ports

Note: In this example, an interface range that covers ports 14 to 24 is entered.

Step 5. In the Interface Configuration context, use the switchport mode command to configure the VLAN membership mode.

re assign ports

Step 6. Use the switchport access vlan command to assign the port or range of ports into access ports. A port in access mode can have only one VLAN configured on the interface which can carry traffic for only one VLAN.

re assign ports

Note: In this example, the range of ports is assigned to VLAN 30.

Step 7. (Optional) To return the port or range of ports to the default VLAN, enter the following:

Step 8. To exit the Interface Configuration context, enter the following:

re assign ports

Step 9. (Optional) Repeat steps 4 to 6 to configure more access ports and assign to the corresponding VLANs.

re assign ports

Note: In this example, interface range 26 to 36 are assigned to VLAN 10, while interface range 38 to 48 are assigned to VLAN 20.

Step 10. Enter the end command to go back to the Privileged EXEC mode:

re assign ports

Step 11. (Optional) To display the configured ports on the VLANs, enter the following:

re assign ports

Note: The configured ports should be displayed according to the assigned VLANs. In this example, the interface range 26 to 36 are assigned in VLAN 10, 38 to 48 belong to VLAN 20, and 14 to 24 are configured to VLAN 30.

Step 12. (Optional) In the Privileged EXEC mode of the switch, save the configured settings to the startup configuration file, by entering the following:

re assign ports

Step 13. (Optional) Press Y for Yes or N for No on your keyboard once the Overwrite file [startup-config]… prompt appears.

re assign ports

You should now have configured the interfaces on your switch as access ports and assigned to their corresponding VLANs.

Configure Interface as Trunk Port and Assign to VLAN

Step 1. In the Privileged EXEC mode of the switch, enter the Global Configuration mode by entering the following:

Step 2. In the Global Configuration mode, enter the Interface Configuration context by entering the following:

re assign ports

Note: In this example, interface ge1/0/13 is used.

Step 3. In the Interface Configuration context, use the switchport mode command to configure the VLAN membership mode.

re assign ports

Step 4. (Optional) To return the port to the default VLAN, enter the following:

Step 5. Use the switchport trunk allowed vlan command to specify which VLANs the port belongs to when its mode is configured as trunk.

Note: In this example, port ge1/0/13 belongs to all VLANs except VLAN 10.

re assign ports

Step 6. To exit the Interface Configuration context, enter the following:

re assign ports

Step 8. (Optional) Repeat steps 2 to 6 to configure more trunk ports and assign to the corresponding VLANs.

re assign ports

Note: In this example, interface ge1/0/25 belongs to VLAN 10 and not in VLAN 20, while interface ge1/0/27 belongs to all VLANs except VLAN 10.

Step 9. Enter the end command to go back to the Privileged EXEC mode:

re assign ports

Step 10. (Optional) To display the configured ports on the VLANs, enter the following:

re assign ports

Note: The configured ports should be displayed according to the assigned VLANs. In this example, the trunk port gi1/0/25 belongs to VLAN 10 and VLAN 30, gi1/0/13 and gi1/0/37 both belong to VLAN 20 and VLAN 30.

Step 11. (Optional) In the Privileged EXEC mode of the switch, save the configured settings to the startup configuration file, by entering the following:

re assign ports

Step 12. (Optional) Press Y for Yes or N for No on your keyboard once the Overwrite file [startup-config]… prompt appears.

re assign ports

You should now have configured the interfaces on your switch as trunk ports and assigned to their corresponding VLANs.

Important: To proceed with configuring the VLAN group settings on your switch, follow the guidelines above.

Other links you might find valuable

Revision History

Was this document helpful.

Feedback

Contact Cisco

login required

re assign ports

Configuring VLANs

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. You can reconfigure the switch to support up to 2048 VLANs, with up to 4094 VIDs, by adding new VLAN names and VIDs and then assigning one or more ports to each VLAN.

Per-port static VLAN configuration options example

This example shows the options available to assign individual ports to a static VLAN.

Note that GVRP, if configured, affects these options and the VLAN behavior on the switch.

Comparing per-port VLAN options with and without GVRP

Comparing per-port VLAN options with and without GVRP

Per-port VLAN configuration options

Using the Menu to configure port-based VLAN parameters

In the factory default state, support is enabled for up to 256 VLANs. (You can reconfigure the switch to support up to 2048 (vids up to 4094) VLANs.) Also, in the default configuration, all ports on the switch belong to the default VLAN and are in the same broadcast/multicast domain. (The default VLAN is also the default Primary VLAN; see The primary VLAN .) In addition to the default VLAN, you can configure additional static VLANs by adding new VLAN names and VIDs, and then assigning one or more ports to each VLAN. (The maximum of 2048 VLANs includes the default VLAN, all additional static VLANs you configure, and any dynamic VLANs the switch creates if you enable GVRP; see GVRP .) Note that each port can be assigned to multiple VLANs by using VLAN tagging; see VLAN tagging rules .)

Changing VLAN support settings (Menu)

The following procedure provides instructions for changing the maximum number of VLANs to support, changing the primary VLAN selection and enabling or disabling dynamic VLANs.

From the Main Menu select: 2. Switch Configuration —> 8. VLAN Menu … —> 1. VLAN Support

You see the following screen:

The default VLAN support screen

The default VLAN support screen

Press E (for Edit) and then do one or more of the following:

To change the maximum number of VLANs, enter the new number (1 - 2048 allowed; default 256).

To designate a different VLAN as the Primary VLAN, select the Primary VLAN field and use the space bar to select from the existing options. The Primary VLAN must be a static, port-based VLAN.

To enable or disable dynamic VLAgNs, select the GVRP Enabled field and use the Space bar to toggle between options. For GVRP information, see GVRP .

Press Enter and then S to save the VLAN support configuration and return to the VLAN Menu screen.

If you changed the value for Maximum VLANs to support , an asterisk appears next to the VLAN Support option; see VLAN menu screen indicating the need to reboot the switch .

VLAN menu screen indicating the need to reboot the switch

VLAN menu screen indicating the need to reboot the switch

If you changed the VLAN Support option, you must reboot the switch before the maximum VLANs change takes effect. You can go on to configure other VLAN parameters first, but you must reboot the switch when you finish.

If you did not change the VLAN Support option, a reboot is not necessary.

Press 0 to return to the Main Menu.

Adding or editing VLAN names (Menu)

Use this procedure to add a new VLAN or to edit the name of an existing VLAN.

From the Main Menu select 2. Switch Configuration —> 8. VLAN Menu … —> 2. VLAN Names

If multiple VLANs are not yet configured, you will see a screen similar to The default VLAN names screen .

The default VLAN names screen

The default VLAN names screen

Press A (for Add).

You will be prompted for a new VLAN name and VLAN ID:

Type a VID (VLAN ID number). This can be any number from 2 to 4094 that is not already being used by another VLAN (the switch reserves 1 for the default VLAN).

Press ↓ key to move the cursor to the Name line and enter the VLAN name, using up to 12 characters with no spaces. Press Enter .

Press S (for Save).

The VLAN Names screen appears with the new VLAN listed.

VLAN Names screen with a new VLAN added

VLAN Names screen with a new VLAN added

Repeat steps 2 through 5 to add more VLANs.

You can add VLANs until you reach the number specified in the Maximum VLANs to support field on the VLAN Support screen. This includes any VLANs added dynamically due to GVRP operation.

Return to the VLAN Menu to assign ports to the new VLAN, as described in Adding or changing a VLAN port assignment (Menu) .

Adding or changing a VLAN port assignment (Menu)

Ports not specifically assigned to a VLAN are automatically in the default VLAN.

From the Main Menu select: 2. Switch Configuration —> 8. VLAN Menu … —> 3. VLAN Port Assignment

You will see a screen similar to the following:

Port-based VLAN port assignment screen in the menu interface

Port-based VLAN port assignment screen in the menu interface

To change a port's VLAN assignment:

Press E (for Edit).

Use the arrow keys to select a VLAN assignment you want to change.

Press the Space bar to make your assignment selection ( No , Tagged , Untagged , or Forbid . For information on VLAN tags, see 802.1Q VLAN tagging .

If you are finished assigning ports to VLANs, press Enter and then S (for Save) to activate the changes and return to the Configuration menu. (The console then returns to the VLAN menu.)

Return to the Main menu.

For ports A4 and A5 to belong to both DEFAULT_VLAN and VLAN-22 and ports A6 and A7 to belong only to VLAN-22, use the settings in The default VLAN names screen . This example assumes that the default GVRP setting is disabled and that you do not plan to enable GVRP later.

Displaying port-based VLAN assignments for specific ports

re assign ports

Using the CLI to configure port-based and protocol-based VLAN parameters

In the factory default state, all ports on the switch belong to the port-based default VLAN (DEFAULT_VLAN; VID=1) and are in the same broadcast/multicast domain.

The default VLAN is also the Primary VLAN. For more on this topic, see The primary VLAN .)

You can configure up to 255 additional static VLANs by adding new VLAN names and then assigning one or more ports to each VLAN.

The switch accepts a maximum of 2048 VLANs with VIDs numbered up to 4094. This must include the default VLAN and any dynamic VLANs the switch creates if you enable GVRP (see GVRP ).

Creating a new static VLAN (port-based or protocol-based) (CLI)

The vlan <vid> command operates in the global configuration context to configure a static VLAN and/or take the CLI to a specified VLAN's context.

vlan vid | <ascii-name-string>

[no] vlan <vid>

If <vid> does not exist in the switch, this command creates a port-based VLAN with the specified <vid> If the command does not include options, the CLI, moves to the newly created VLAN context. If an optional name is not specified, the switch assigns a name in the default format VLAN n , where n is the <vid> assigned to the VLAN. If the VLAN already exists and you enter either the <vid> or the <ascii-name-string> ,the CLI moves to the specified VLAN's context. The no form of the command deletes the VLAN as follows: If one or more ports belong only to the VLAN to be deleted, the CLI notifies you that these ports will be moved to the default VLAN and prompts you to continue the deletion. For member ports that also belong to another VLAN, there is no move prompt.

protocol [ ipx | ipv4 | ipv6 | arp | appletalk | sna | netbeui ]

Configures a static, protocol VLAN of the specified type. If multiple protocols are configured in the VLAN, the no form removes the specified protocol If a protocol VLAN is configured with only one protocol type and you use the no form of this command to remove that protocol, the switch changes the protocol VLAN to a port-based VLAN (if the VLAN does not have an untagged member port). If an untagged member port exists on the protocol VLAN, you must either convert the port to a tagged member or remove the port from the VLAN before removing the last protocol type from the VLAN. NOTE: If you create an IPv4 protocol VLAN, you must assign the ARP protocol option to it to provide IP address resolution. Otherwise, IP packets are not deliverable. A Caution message appears in the CLI if you configure IPv4 in a protocol VLAN that does not already include the ARP protocol option. The same message appears if you add or delete another protocol in the same VLAN.

name <ascii-name-string>

When included in a vlan command to create a new static VLAN, this command specifies a non-default VLAN name. Also used to change the current name of an existing VLAN. NOTE: Avoid spaces and the following characters in the <ascii-name-string> entry: @ , #: , $ , ^ , & , * , ( and ) . To include a blank space in a VLAN name, enclose the name in single or double quotes.
Designates a VLAN for VoIP use. For more on this topic, see Using voice VLANs . NOTE: You can use these options from the configuration level by beginning the command with vlan <vid> , or from the context level of the specific VLAN by just entering the command option.

Creating a new port-based static VLAN

The following example shows how to create a new port-based, static VLAN with a VID of 100 using the following steps:

To create the new VLAN, type the vlan 100 command.

To show the VLANs currently configured in the switch, type the show vlans command.

If the Management VLAN field ( Primary VLAN : DEFAULT_VLAN Management VLAN shown in the display information below) is empty, a Secure Management VLAN is not configured in the switch. For more information on configuring a secure management VLAN, see The secure Management VLAN .

Changing the VLAN context level

To go to a different VLAN context level, such as to the default VLAN:

Configuring or changing static VLAN per-port settings (CLI)

[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, as well as 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 . See GVRP .

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. For information on dynamic VLAN and GVRP operation, see GVRP .

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

Similarly, 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 config level, use:

At the VLAN 100 context level, use:

Converting a dynamic VLAN to a static VLAN (CLI)

static-vlan <vlan-id> Converts a dynamic, port-based VLAN membership to static, port-based VLAN membership (allows port-based VLANs only). For this command, <vlan-id> refers to the VID of the dynamic VLAN membership. Use show vlan to help identify the VID. This command requires that GVRP is running on the switch and a port is currently a dynamic member of the selected VLAN. After you convert a dynamic VLAN to static, you must configure the switch's per-port participation in the VLAN in the same way that you would for any static VLAN. For GVRP and dynamic VLAN operation, see GVRP .

Converting a dynamic VLAN to a port-based static VLAN

Suppose a dynamic VLAN with a VID of 125 exists on the switch. The following command converts the VLAN to a port-based, static VLAN:

Deleting a static VLAN (CLI)

no vlan <vid>

Deleting a static VLAN

Following VLAN Names screen with a new VLAN added , if ports B1-B5 belong to both VLAN 2 and VLAN 3 and ports B6-B10 belong to VLAN 3, deleting VLAN 3 causes the CLI to prompt you to approve moving ports B6 - B10 to VLAN 1 (the default VLAN). (Ports B1-B5 are not moved because they still belong to another VLAN.)

Deleting multiple VLANs

Enables the user to add or delete interfaces from multiple tagged or untagged VLANs or SVLANs using a single command. Interfaces can be added or deleted up to 256 VLANs at a time. If more than 256 VLANs are specified, an error displays. The forbid command option prevents specified ports from becoming members of specified VLANs or SVLANs when used with GVRP. The command is executed in the interface context.

[no] interface <port-list> <tagged | untagged | forbid> <vlan | svlan <vlan-id-list>> The specified interfaces are added to existing VLANs or SVLANs. If a VLAN or SVLAN does not exist, an error message displays. The [no] option removes the specified interfaces from the specified VLANs or SVLANs. The forbid option prevents an interface from becoming a member of the specified VLANs or SVLANs. It is executed in interface context.

Removing an interface from several VLANs

The vlan-id-list includes a comma-separated list of VLAN IDs and/or VLAN ID ranges.

To remove interface 1 from VLANs 1, 3, 5, 6, 7, 8, 9, 10

To specify that an interface cannot become a member of VLANs 4 and 5

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 config 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.

The show ip command displays disabled in the IP Config 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.

Displaying a VLAN disabled for Layer 3

For IPv6, the Layer 3 Status field displays the status of Layer 3 on that VLAN.

Displaying 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.

Changing the Primary VLAN (CLI)

For more information on Primary VLANs, see The primary VLAN .

primary-vlan vid | <ascii-name-string> In the default VLAN configuration, the port-based default VLAN ( DEFAULT_VLAN ) is the Primary VLAN. This command allows reassignment of the Primary VLAN function to an existing, port-based, static VLAN. The switch will not reassign the Primary VLAN function to a protocol VLAN. NOTE: If you reassign the Primary VLAN to a non-default VLAN, you cannot later delete that VLAN from the switch until you assign the Primary VLAN to another port-based, static VLAN. To identify the current Primary VLAN and list the available VLANs and their respective VIDs, use show vlans .

Re-assigning, renaming and displaying the VLAN command sequence

The following example shows how to re-assign the Primary VLAN to VLAN 22 (first command line), rename the VLAN 22-Primary (second command line) and then display the result (third command line):

Configuring a secure Management VLAN (CLI)

Preparation.

Determine a VID and VLAN name suitable for your Management VLAN.

Plan your topology to use HP switches that support Management VLANs. See The secure Management VLAN .

Include only the following ports:

Ports to which you will connect authorized management stations, such as Port A7 in Management VLAN control in a LAN .

Ports on one switch that you will use to extend the Management VLAN to ports on other HP switches, such as ports A1 and Management VLAN control in a LAN .

Half-duplex repeaters dedicated to connecting management stations to the Management VLAN can also be included in this topology. Note that any device connected to a half-duplex repeater in the Management VLAN will also have Management VLAN access.

Configure the Management VLAN on the selected switch ports.

Test the Management VLAN from all of the management stations authorized to use it, including any SNMP-based network management stations. Also test any Management VLAN links between switches.

Configuring an existing VLAN as the Management VLAN (CLI)

[no] management-vlan [ <vlan-id> | <vlan-name> ] Configures an existing VLAN as the Management VLAN. The no form disables the Management VLAN and returns the switch to its default management operation. Default: Disabled. In this case, the VLAN returns to standard VLAN operation.

Switch configuration

You have configured a VLAN named My_VLAN with a VID of 100 and want to configure the switch to do the following:

Use My_VLAN as a Management VLAN (tagged, in this case) to connect port A1 on switch "A" to a management station. The management station includes a network interface card with 802.1Q tagged VLAN capability.

Use port A2 to extend the Management VLAN to port B1 which is already configured as a tagged member of My_VLAN , on an adjacent HP switch that supports the Management VLAN feature.

Configuration Example

re assign ports

Obtaining an IP address using DHCP (CLI)

Use DHCP to obtain an IPv4 address for your Management VLAN or a client on that VLAN. The following examples illustrate when an IP address will be received from the DHCP server.

DHCP server on a Management VLAN

If Blue_VLAN is configured as the Management VLAN and the DHCP server is also on Blue_VLAN, Blue_VLAN receives an IP address. Because DHCP Relay does not forward onto or off of the Management VLAN, devices on Red_VLAN cannot get an IP address from the DHCP server on Blue_VLAN (Management VLAN) and Red_VLAN does not receive an IP address.

re assign ports

DHCP server on a different VLAN from the Management VLAN

If Red_VLAN is configured as the Management VLAN and the DHCP server is on Blue_VLAN, Blue_VLAN receives an IP address but Red_VLAN does not.

re assign ports

No Management VLANs configured

If no Management VLAN is configured, both Blue_VLAN and Red_VLAN receive IP addresses.

re assign ports

A client on a different Management VLAN from the DHCP server

If Red_VLAN is configured as the Management VLAN and the client is on Red_VLAN, but the DHCP server is on Blue_VLAN, the client will not receive an IP address.

re assign ports

A DHCP server and client on the Management VLAN

If Blue_VLAN is configured as the Management VLAN, the client is on Blue_VLAN and the DHCP server is on Blue_VLAN, the client receives an IP address.

re assign ports

Obtaining the IP address for a host that is on a different VLAN than the DHCP server

In the following example, the host is on VLAN 20 and is connected on port number 2 of the switch. The DHCP server, however, is in VLAN 10 and is connected on port 10 of the switch.

Disabling the Management feature (CLI)

You can disable the Secure Management feature without deleting the VLAN.

Disabling the secure management feature

The following commands disable the Secure Management feature in the above example:

For more information, see The secure Management VLAN .

Changing the number of VLANs allowed on the switch (CLI)

The default VLAN number is 1.

max-vlans <1-2048>

Default number of VLANs: 256

In the default VLAN configuration, the switch allows a maximum of 256 VLANs. Use this command to specify the maximum VLANs to allow and specify any value from 1 to 2048.

If GVRP is enabled, this setting includes any dynamic VLANs on the switch. As part of implementing a new setting, you must execute a write memory command to save the new value to the startup-config file and then reboot the switch. NOTE: If multiple VLANs exist on the switch, you cannot reset the maximum number of VLANs to a value smaller than the current number of VLANs.

Changing the number of allowed VLANs

The following example shows the command sequence for changing the number of VLANs allowed to 10. Note that you can execute the commands to write memory and boot at another time.

Copyright © 2015 Hewlett-Packard Development Company, L.P.

IMAGES

  1. How to deal with neglected tickets

    re assign ports

  2. How do I re-assign an assignment to my students?

    re assign ports

  3. Incident_request_for_re-assign_2.png

    re assign ports

  4. Assigning Port Roles and Port Groups

    re assign ports

  5. Assign audio

    re assign ports

  6. Assigning Audio

    re assign ports

VIDEO

  1. [Apple II] Lode Runner (1983) (Broderbund)

  2. Campgrounds: The Endorus Expedition

  3. 101€ in 7min ¡¡ WIN and WIN !! whit ships €1

  4. Wine Guide

  5. Power BI A-Z Chp #05(Hindi)| Next Level Matrix visuals, with add Hierarchy Expand hierarchy,Driillup

  6. Election 2022: Results and Repercussions

COMMENTS

  1. What Is My Computer’s Port Number?

    There is no one port number for a computer. Computers use multiple ports to accommodate different processes running on the computer. The port number in use varies on the software or service being used and the computer’s configuration.

  2. What Is Port 8080 Used For?

    Port 8080 is an alternative to port 80 and is used primarily for http traffic. It is named 8080 for its correlation to 80. Port 8080 is commonly used as proxy and caching port. It is also above the service port range. Port 8080 also can run...

  3. What Is a List of Algerian Ports?

    Algeria has 18 ports along the Mediterranean Sea capable of handling cargo, including Algiers, Annaba, Oran, Beni Saf, Cherchell, Dellys, Djen Djen, Ghazaouet, Mostaganem, Skikda and Tenes.

  4. Change the listening port in Remote Desktop

    The next time you connect to this computer by using the Remote Desktop connection, you must type the new port. If you're using a firewall

  5. How to re-assign HTTP ports and hostname used by Vault

    The Vault Server installation software, supports defining the Port number. There is no supported method to redefine the port that Vault Server

  6. Port assignments

    Port numbers are used on various socket calls. They are also included in both the header of a TCP segment and a UDP datagram. You can assign port numbers to

  7. Adding or Changing TCP/UDP Port Assignments

    Adding or Changing TCP/UDP Port Assignments ; Choose the Single Port radio button; Enter the port number in the Port Number ; Change the port number and/or choose

  8. How do I change the default COM port setting for multiport serial

    SOLUTION · Go to Windows Device manager > Multi-port serial adapters. · Select the adapter and right click to open the menu. · Click on the

  9. Re-Assigning COM Port Numbers Using the Windows Registry

    COM ports are assigned to FTDI devices during installation, based on the next free port as indicated by the PC registry.

  10. Need help to re-assign ports away from switch0

    Then assign the ports: set interfaces switch switch0 switch-port interface eth1 pvid 1 set interfaces switch switch0 switch-port interface eth2 pvid 10 set

  11. Service Name and Transport Protocol Port Number Registry

    Service names are assigned on a first-come, first-served process, as documented in [RFC6335]. Port numbers are assigned in various ways

  12. Re: Assigning Ports to VLANS on RV260W: Tagged, Untagged

    Assign VLANs to Ports · Considered an Access port. · The VLAN that is assigned this port should be labeled Untagged. · All other VLANs should be labeled Excluded

  13. Configure Port to VLAN Interface Settings on a Switch through the CLI

    Access Port - The frames received on the interface are assumed to not have a VLAN tag and are assigned to the specified VLAN. Access ports are

  14. Configuring VLANs

    Adding or changing a VLAN port assignment (Menu). Ports not specifically assigned to a VLAN are automatically in the default VLAN. From the Main Menu select: