Management VLANs

Communication with the switch management interfaces is through the switch IP address. The IP address is associated with the management VLAN, which by default is VLAN 1.

The management VLAN has these characteristics:

♦ It is created from CMS or through the CLI on static-access, dynamic-access, and trunk ports. You cannot create or remove the management VLAN through Simple Network Management Protocol (SNMP).

♦ Only one management VLAN can be administratively active at a time.

♦ With the exception of VLAN 1, the management VLAN can be deleted.

♦ When created, the management VLAN is administratively down.

Before changing the management VLAN on your switch network, make sure you follow these guidelines:

♦ The new management VLAN should not have a Hot Standby Router Protocol (HSRP) standby group configured on it.

♦ You must be able to move your network management station to a switch port assigned to the same VLAN as the new management VLAN.

♦ Connectivity through the network must exist from the network management station to all switches involved in the management VLAN change.

♦ On switches running a IOS software version that is earlier than Cisco IOS 12.0(5)XP, you cannot change the management VLAN. Switches running Cisco IOS 12.0(5)XP should be upgraded to the current software release as described in the release notes.

If you are using SNMP or CMS to manage the switch, ensure that the port through which you are connected to a switch is in the management VLAN.

For information about the role management VLANs play in switch clusters, see the "Management VLAN" section on page 6-20.

Determining the Management VLAN for a New Switch

If you add a new switch to an existing cluster and the cluster is using a management VLAN other than the default VLAN 1, the command switch automatically senses that the new switch has a different management VLAN and has not been configured. The command switch issues commands to change the management VLAN on the new switch to match the one used by the cluster. This automatic change occurs for new, out-of-box switches that do not have a config.text file and for which there have been no changes to the running configuration.

Before a new switch can be added to a cluster, it must be connected to a port that belongs to the cluster management VLAN. If the cluster is configured with a management VLAN other than the default, the command switch changes the management VLAN for new switches when they are connected to the cluster. In this way, the new switch can exchange Cisco Discovery Protocol (CDP) messages with the command switch and be proposed as a cluster candidate.

For the command switch to change the management VLAN on a new switch, there must have been no changes to the new switch configuration, and there must be no config.text file.

Because the switch is new and unconfigured, its management VLAN is changed to the cluster management VLAN when it is first added to the cluster. All ports that have an active link at the time of this change become members of the new management VLAN.

For information about the role management VLANs play in switch clusters, see the "Management VLAN" section on page 6-20.

Changing the Management VLAN for a Cluster

Beginning in privileged EXEC mode on the command switch, follow these steps to configure the management VLAN interface through a Telnet or Secure Shell (SSH) connection:

	Command	Purpose
Step 1	configure terminal	Enter global configuration mode.
Step 2	cluster management-vlan vlanid	Change the management VLAN for the cluster. This ends your Telnet session. Change the port through which you are connected to the switch to a port in the new management VLAN.
Step 3	show running-config	Verify the change.

Note

Continue reading here: VLAN Port Membership Modes

Was this article helpful?

0 0