Release Note for Software Version 2.0

Regardless of whether the local device has begun running VTP or not, the trunk mapping of VLANs will occur as specified in the VTP database using VLAN id for ISL trunks and VLAN name for LANE trunks. Whether or not this mapping is appropriate for your configuration depends on which ports on a local Stack need to be members of the same VLAN (with other local assigned ports that exist on remote devices across the trunk and beyond).

Assigning local ports

To insure that the local VLAN port and parameter assignments resolve correctly and do not get deleted (once they are controlled by VTP):

• Determine which global VLANs (as determined by the VLAN id number and not the VLAN name in the global database) will need to contain the ports and parameters, now assigned to each local VLAN, that was created in the upgrade process. (Local VLANs corresponding to previously unused Virtual EtherSwitches are of no concern and may be ignored.)
  

For example, after the upgrade procedure, Virtual EtherSwitch 5, named Engineering, with five ports and an IP address of 192.5.5.5, will be changed to VLAN Engineering VTP id number 5 with the same port/IP assignments.

If you need to move VLAN Engineering from VTP id number 5 to another global VLAN with different VTP id number, follow the instructions in the Moving Local VLAN Assignments section.

Moving Local VLAN Assignments

If, in the example in the previous section, the user determines that the ports and address in local VLAN 5 need to be assigned to global VLAN 281 (because this will allow desired connectivity to other ports in global VLAN 281) the VLAN will need to be moved.

Procedure to move VLANs

First of all, VLAN 281 needs to exist in order to move ports and parameters there. (The VLANs corresponding to the pre-2.0 database created are assigned id numbers 1 through 64 and the mandatory non-ethernet default VLANs are assigned id numbers 1002 through 1005.)

Step 1 The VLAN 281 must be created using the VTP VLAN Configuration Sub-menu (under the VLAN and VTP Configuration Menu.) If integration into the global database is imminent, there is no need to be concerned with most of the VTP parameters assigned to VLAN 281 in the local database since these will ultimately be overwritten by the global database. However, since there is a limit of 68 VLANs on a local device, one of the existing VLANs will need to be deleted to make room for VLAN 281. Use the delete function in this menu to remove a VLAN that is not needed.

Step 2 Add VLAN 281 using the Add function in the VTP VLAN Configuration menu. The parameters that need to be configured are:

• the VLAN name (since all VLANs must have unique name of at least one character)
  

• the VLAN type (must be Ethernet)
  

• the VLAN MTU (must be 1500).
  

The last two values will default as desired (Ethernet type/1500 MTU) when using this function in the VTP VLAN Parameter Configuration Menu. (As covered in a later section, the new VLAN need not and probably should not be made Preferred in the Local Preferred VLANs Configuration menu.)

Step 3 Once VLAN 281 is created, ports and local parameters may be moved from VLAN 5 to VLAN 281. To move a local VLAN in a single step, use the Reassign Ports in Local VLAN sub-menu under the VLAN and VTP Configuration menu.

Step 4 The Reassign Ports in Local VLAN menu has four selectable items:

• source VLAN - The source VLAN assignment allows you to select a preferred VLAN from which the VLAN ports and parameters are being moved.
  

• destination VLAN - The destination VLAN allows you to select any existing VLANs to which to move the ports and parameters.
  

• the "Execute Reassignment" function
  

• the "Leave Unchanged" function.
  

Step 5 In this example, the source VLAN would be VLAN 5 and the destination VLAN would be VLAN 281. Select the Execute Reassignment function to complete the move. Check that all local static ports and parameters have been moved from VLAN 5 to VLAN 281.

Final Integration

After all local VLAN moves have been executed and the local VLAN configuration appears correct, integrate this information into the global VTP environment. This procedure must be performed carefully since it may have a drastic effect on local configuration. Use the following steps for this procedure:

Step 1 Do a TFTP save of the configuration database. To do this, go to the Downloads/Upload menu and the TFTP Download/Upload sub-menu.

Step 2 To allow access to the system from the outside, go to the VTP Administrative Configuration menu.

Step 3 Set the Local Mode parameter to either Server or Client mode. If the global VTP database contains no secret value (password) and assuming the local environment has only one VTP administrative domain, this is the only necessary procedure you need to do. However, if you have set a secret value, it also will need to be set in the VTP Administrative Configuration menu

The local device learns the administrative domain name from the first peer to subsequently advertise it to the rest.

Step 4 If necessary, the local mode may be reset to Transparent mode and the configuration uploaded back into the device. Do not simply reload the configuration database without resetting the local VTP mode.

Step 5 After a period of time (normally not exceeding five minutes), the global VTP configuration should be received over the default Ethernet VLAN of any ISL or LANE trunk from a VTP peer (not itself in Transparent mode).

Step 6 The local VTP configuration should now be identical to the global one. If the VLAN moves have been done correctly all the ports and parameters should be assigned as desired and connected to ports in remote devices on their corresponding VLANs.

Preferred VLANs as Destinations In The Reassign Ports in Local VLAN Menu

A preferred VLAN is a VLAN that contains configuration parameters such as IP/port assignments. A non-preferred VLAN does not have any local configuration parameters.

The source of a local VLAN move must be a preferred VLAN. This is because only preferred VLANs contain local port and (non-default) parameter assignments.

It is preferable to have the destination of a VLAN move be a non-preferred VLAN with no locally configured parameters.

However, if the destination VLAN of the move has configured values, you can perform one of the following actions:

• You can decide to swap the position of the two VLANs, taking all their ports and parameters with them. This is effectively a simultaneous two-way move.
  

• You can merge the two preferred VLANs into one. This would have the effect of combining all the ports of the source and destination VLANs into the destination VLAN.
  

A further selection on the VLAN and VTP Configuration menu will allow you to choose which of the two VLAN's local IP and Spanning Tree parameters are kept (assigned to the destination VLAN) and which are discarded.

Reassign Ports in Local VLAN

This display is used to move a fully configured Stack into a pre-existing VTP administrative domain.

Figure 1 : Reassign Ports in a Local VLAN Menu

An Example of How To Upgrade Into a VTP Environment

The following database (Table 1) assumes you would like to integrate the ports on the VLANs named local-(appropriate name) on the Stack being upgraded to 2.0, using VTP, into the correspond global VLANs name global-(appropriate name). For instance, it is desired that ports 2, 4, and 8 (which originally belonged to local-W on the local Stack will ultimately become members of the VLAN named global-W.

Table 1 : VTP Database

Local VTP Database		Global VTP Database
VLAN ID #	VLAN Name	Ports	VLAN ID#	VLAN Name
1	default	1, 3, 15	1	default
2	local-w	2, 4, 8	2	global-A
3	local-x	5, 10, 16	3	global-B
4	local-y	6, 12, 14	4	global-C
5	local-z	7, 9, 11, 13	5	global-W
6	VLAN 5		6	global-D
7	VLAN 6		8	global-E
8	VLAN 7		12	global-X
9	VLAN 8		25	global-F
10	VLAN 9		67	global-Y
11	VLAN 10		281	global-Z
.
.
.
.
64	VLAN 63

1. The Local VTP Database is an example of what might be found in the VTP VLAN configuration after the upgraded box boots up the first time. The "Global" database is the one found in any box in the network currently running VTP in non-transparent mode.
   

2. In the section, Analyze and Determine Local VLAN Modifications Needed for Integration, the user needs to move the local ports and parameters initially assigned to VLAN 2 into VLAN 5. Those assigned to VLAN 3 will be moved to VLAN 12. Those assigned to VLAN 4 will be moved to VLAN 67, and those assigned to VLAN 5 will be moved to VLAN 281. The user would not care about local VLANs numbers over 5 if there are no ports or parameters assigned to them.
   

3. In the section, Moving Local VLAN Assignments, the user would move the VLANs as planned in section, Analyze and Determine Local VLAN Modifications Needed for Integration. Since VLANs 67 and 281 do not exist on the local database, the user would need to first delete two unneeded local VLANs (for instance, VLAN 63 and VLAN 64), and then add VLANs 67 and 281. All of this is done in transparent mode.
   

4. Since VLAN 12 already exists and is preferred (all of the 64 Ethernet VLANs created during upgrade are created as preferred VLANs), it does not have to be created. However, the user needs to choose between swapping VLAN 3 with it or merging VLAN 3 into it. It doesn't matter how it is handled since the user didn't have anything in VLAN 12 that is needed to be saved.
   

5. Since VLAN 5 already exists and is important to the user, the user must take care to handle it correctly when doing the move from VLAN 2 to VLAN 5. Move local-z to the newly created VLAN 281 before moving local-w to VLAN 5.
   As an alternative, you could swap VLANs 2 and 5 first, thus moving the ports and parameters of local-z to local-w and vice versa. (Note that the names do not move.) Then move VLAN 2 to VLAN 281.
   

6. Once the four move operations are performed, the user (after TFTP saving the configuration), may change the local Stack into VTP server or client mode.
   After this has been done (and sufficient time has passed such the configuration has propagated from a neighboring device or Stack running VTP), the Local database should go away completely and the user will see the Global database implemented on the upgraded Stack . All the ports and parameters should have survived the move, however, and will be found in the VLANs they were assigned to by VLAN id number before the mode was changed.
   

Obtaining Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis.