Migration of vlan IDs

I need to change the ID for a vlan and would like to minimize the outage for migrating the hosts. Our environment are Nexus cores using a VPCs to 5ks. The SVI for the vlan resides on the Nexus cores and only L2 on the Nexus 5ks. For example I have vlan100 with an SVI of 10.1.1.0/24 on the cores and it is trunked down to the Nexus 5ks using a vPC. I need to keep the same IP scheme but change the vlan ID to 300. I am trying to do this with very little down time.
I am thinking I could create the new vlan300 as an L2 only on the cores and trunk it down to the 5ks. On nexus core 1, connect a cable from a port that is in vlan100 to vlan300 with the ports being configured as access ports. Essentially I am creating a path for vlan300 to communicate with vlan100. Would this solution work? Of course this would be only temporary to migrate the hosts over the new vlan and then I would move the SVI address to the new vlan300.
See diagram

I haven't used Nexus switches but I am struggling to see what you gain from your solution.
I know with vPCs Nexus handles STP differently but with other switches I have used joining two vlans together in the core of the network is not something I would really consider, or at least not for this.
The IPs are staying the same. So the main issue is when you shut the existing SVI and bring up the new one it could have a different virtual mac address which means all the servers mac to IP mapping for the default gateway would need clearing.
I just checked the N7K configuration guide and if you use the same HSRP group it should generate the same virtual mac. And if you don't you can actually configure your own virtual mac.
So that just leaves migrating the hosts and the Nexus switches support ranges of interfaces.
So I would just have the SVIs ready, then simply move all servers at once into the new vlan, shutdown the old SVI and bring up the new one.
There will obviously be an outage but there would anyway when you switch SVIs.
Like I say I haven't used Nexus so perhaps there is something I am overlooking but I cannot see what benefit you get and creating that link could potentially have a far bigger impact on your environment.
Jon

Similar Messages

I need to see what VLAN-ids are present on a trunk interface. What debugs would help me achieve this?

Currently, i have an Cisco IE3000 switch, with an interface defined as a trunk. The other end is unknown to me, but I know it transmits tagged frames. I just don't know which VLAN-ids are in use - so I was thinking on doing some debugs to learn the VLAN-ids. Remote end does not transmit BPDUs

That would require me to define all VLANs, which may be to much for the IE3000. It supports only 1005.
A debug telling me that a packet have been dropped because the VLAN is not defined - would be the way...

ALC-UPG-221-002: Errors while migrating archive session Ids.

I am doing an out of place upgrade from ES2 to ES4. I have run the Turnkey ES4 upgrade, installed SP1, copied the GDS from the old location to the new location and run Configuration Manager. When I get to the "Perform
critical tasks before component deployment" screen and click the Start button I get this error:
10:07] ALC-UPG-002-505: Disabling UserManager synchronization.
[10:07] ALC-UPG-001-501: Executing [Application Manager] plugin ...
[10:07] ALC-UPG-001-503: [Application Manager] plugin execution failed, error message from plugin is [ALC-UPG-221-002: Errors while migrating archive session Ids.]. See LCM logs for details.
[10:07] ALC-UPG-002-506: Enabling UserManager synchronization.
The LCM log has this:
[2014-08-06 10:32:58,555], INFO, AWT-EventQueue-0, com.adobe.livecycle.upgrade.gui.UpgradePhaseDialog, ALC-UPG-002-505: Disabling UserManager synchronization.
[2014-08-06 10:32:58,560], INFO, Thread-32, com.adobe.livecycle.lcm.feature.lcServer.LCServerConnector, LC Connection properties: {DSC_DEFAULT_SOAP_ENDPOINT=http://localhost:8080, DSC_TRANSPORT_PROTOCOL=SOAP, DSC_CREDENTIAL_PASSWORD=********, DSC_REQUEST_TIMEOUT=1200000, DSC_CREDENTIAL_USERNAME=administrator, }
[2014-08-06 10:32:58,560], INFO, Thread-32, com.adobe.livecycle.lcm.feature.lcServer.LCServerConnector, Validating connection...
[2014-08-06 10:32:59,961], SEVERE, Thread-32, com.adobe.livecycle.upgrade.control.PhaseRunner, Aborting. Invocation of method [configurePreDeploy] failed for com.adobe.livecycle.upgrade.plugins.from9xto100.applicationmanager.Upgrade9xTo100Applicat ionManagerPlugin. Caught com.adobe.livecycle.upgrade.UpgradeException, message: ALC-UPG-221-002: Errors while migrating archive session Ids.
com.adobe.livecycle.upgrade.UpgradeException: ALC-UPG-221-002: Errors while migrating archive session Ids.
at com.adobe.livecycle.upgrade.plugins.from9xto100.applicationmanager.Upgrade9xTo100Applicat ionManagerPlugin.configurePreDeploy(Upgrade9xTo100ApplicationManagerPlugin.java:110)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at com.adobe.livecycle.upgrade.control.PhaseRunner.run(PhaseRunner.java:244)
at java.lang.Thread.run(Thread.java:724)
[2014-08-06 10:33:01,763], INFO, AWT-EventQueue-0, com.adobe.livecycle.upgrade.gui.UpgradePhaseDialog, ALC-UPG-002-506: Enabling UserManager synchronization.
Nothing tells what the errors are.

Dear Pallavi,
Very useful post!
I am looking for similar accelerators for
Software Inventory Accelerator
Hardware Inventory Accelerator
Interfaces Inventory
Customization Assessment Accelerator
Sizing Tool
Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
Request help on such accelerators... Any clues?
Any reply, help is highly appreciated.
Regards
Manish Madhav

Migrate Default VLAN to another vlan

Hi
We are replacing our core stack of 3750 with a new core setup as a VSS. As part of this migration I want to connect the new core to the old core via trunk links as I migrate the configs over and connections.
My management vlan is currently vlan 1 but want to move this to vlan 5 as part of the change. I want to keep the same management subnet tho. How can I co-exist management IPs on both switches as part of the same subnet but different vlan. Is this possible or is there an easier way.
I know I can configure the new switch without connecting to the exisiting but the plan is that during the migration, I want to migrate the L2 links first and test and then migrate the L3 links which is why I want to connect the new core to the existing core
Thanks

Hi,
Since you need to trunk the new vss to the old 3750 stack, you need to have the same vlan tags on both side of the link. So, on the old core the mgmt vlan is 1 (tagged) and if you change it to vlan 5 (tagged) on the link between vss and 3750 stack than even though both vlans are in the same subnet they will not be able to communicate with each other because the tags are different. Also, if you have specified vlan 1 as native on your current trunks and when you connect the new core to the old core and if your native vlan is 5, you will see mismatch native vlan. So, what you can do it use vlan 1 on the trunk connecting vss to the old core with unused IPs (if you have any available) than once you migrate to the new core you can have a maintenance window and change vlan 1 to 5.
HTH

Using more than 1000 VLAN Ids with VTP

How do I overcome the 1000 VLAN Id limitation with VTP ?

Hi,
you need VTP version 3 for that matter or set the switches to transparent. Unfortunately VTPv3 is only available in CatOS 8.1(1) or later. See also
Understanding How VTP Version 3 Works
VTP version 3 differs from earlier VTP versions in that it does not directly handle VLANs. VTP version 3 is a protocol that is only responsible for distributing a list of opaque databases over an administrative domain. When enabled, VTP version 3 provides the following enhancements to previous VTP versions:
•Support for extended VLANs.
http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide_chapter09186a008019f048.html#wp1017196
Hope this helps! Please rate all posts.
Regards, Martin

VLAN IDs not showing up in 2960 switch configuration

We have Layer 2 2960 switches that all connect back to our 4500 core. the core has the Interface VLAN defs. But, in the access switches I can do a SHO VLAN and see all the VLANs in my network, but they do not show up in my running config. The guides all say to use the VLAN global command to define VLANs, but will just entering the switchport access vlan x put them in the VLAN database as well? We also do not have VTP defined. Any ideas?

Hello Kmattison,
>> but will just entering the switchport access vlan x put them in the VLAN database as well?
yes this is correct. And it may explain what you see vlan entries in the vlan database without a corresponding vlan command in the running config.
Hope to help
Giuseppe

Errors during VM migration

Hi,
I have an SCVMM 2012 R2 instance (with CU1), and when I perform a VM migration I get a status of Completed w/ Info
In the details pane of the Jobs window I have 9 errors and a warning every time
Error 23801 - No available connection to selected VM Network can be found
Error 23810 - There is no host NIC with required classification
Error 23806 - All available ports on switch extenstion has been used
Error 23808 - All available ports on port profile has been used
Error 23807 - The switch extension has reached maximum supoprted ports on this host
Error 23809 - The port profile has reached maximum support ports on this host
Error 23811 - Ports are not available for VM Subnet
Error 23825 - The virtual machine requires a logical switch connection and the host network adapter is not attached to a logical switch or operating sytem doesn't support logical switch
Error 23753 - The virtual machine or tier load balancer configuration requires an IP pool and there are no appropraite IP pools accessible from the host
Warning 23830 - Unable to find compliant logical switch
Even with all of these warnings the migrated VM works just fine.
In our environment we are using a layer 3 switch with VLANs, so I have a logical network using the 'VLAN-based independent networks' option, with two sites
Each site has an assoicated VLAN ID, and IP subnet
I've created a logical switch (without SR-IOV), using only the Microsoft Windows Filtering platform extension
The uplink on the logical switch is not a team, and has a port profile associated with the host group including all my Hyper-V hosts, and including all sites from the logical network
The virtual port on the logical switch has High bandwidth and medium bandwidth port classifications associated
I have VM Networks created for each of the sites on my logical network
The network configuration on my VM is as follows:
Connected to a VM network, enable VLAN
IP address is greyed out as Static IP (from a static IP pool) - This was configured as Dynamic at creation time as I do not use IP pools
MAC address is dynamic
Virtual switch - using the logical switch mentioned above and High Bandwidth classification
The hosts have a dedicated interface on a trunked network port for VM data. Available for placement is checked, used by management is not (as i have a dedicated interface for that)
It has the logical network mentioned above assigned, and all IP sites are shown with their VLAN IDs
I believe I have everything configured correctly (after all the VM works correctly regardless of which host is running it), but i still see these errors during a VM migration
Has anybody seen this before, or have any pointers to resolving them?
The hosts are Server 2012 R2 Datacenter and the VM is Server 2012 R2 Standard
Thanks,
Phil

I am also getting these errors when manually migrating machines between hosts. And indeed, the VM is moved and keeps working.
But when I try to put an host in maintenance, it instantly fails with:
Error (10434)
No suitable host is available for migrating the existing highly available virtual machines.
Not quite the same network setup, but running all Server 2012R2 and VMM2012R2.
In my production environment I do not have these issues, which is running Server 2012 and VMM2012SP1.
Regards,
Ramon

Nexus1000v vlan conflict

Hi All,
I will try and make this short.
Basically client is currently using esxi5 hosts using vswitch. they have a totally sperated monitoring network & swtiches from their prod network and swtiches.
Today they are wanting implement the 1000v platform and migrate the hosts to the n1k.
Upon preparing for their migration I notieced they would have an uplink to their mon network with a primary private-vlan ID # 825 and isolated vlan 826 no biggy here. We currently setup similar n1k on their staging network. However I noticed that they also have vlan#825 defined on their prod network for web servers.
So using the nexus creating port-profiles I am sure that the creating a primary pvlan 825 will conflict with web-prod vlan 825 I don't think we can have two vlan IDs the same and ask them to perform differently.
I've given the recommendation to change either the prod or mon vlan tag to something that does not conflict and of course that will cause an outage of sorts for a small periord of time.
One of my co-workers mentioned a VLAN NAT to rewrite the vlan ID, have to admit sounds like a hack.
So any ideas if there is a way to have the same vlan ID on the nexus with two different port-profiles? One for normal vlan 825 while the other is a primary pvlan 825 assocated with an isolated 826 vlan?
thanks for any input.

Hi David,
The management VLAN is the only VLAN which needs to match between the Nexus 1010 and Nexus 1000v. This means the mgmt0 interface on the VSM needs to be on the same subnet as the mgmt0 interface that the Nexus 1010 appliance uses.
The control VLAN could be the same between the N1010 and N1Kv but it doesn't have to be.
Additionally, the Domain ID used needs to be different between the N1010 and N1Kv. Each svs-domain pair must have a unique domain-id. For example, the N1010 pair could share a domain-id of 10 and the first N1Kv pair would share domain-id 20.
So to make this specific to your example:
* Nexus 1010
   - Management: VLAN 100
   - Control: Could be VLAN 300 or something different (up to you)
   - Domain ID: XX
* Nexus 1000v
   - Management: VLAN 100
   - Control: VLAN 300
   - Domain ID: YY
   - Packet: VLAN 200
Hope that helps clarify things for you.
Thanks,
Michael

When setting up converged network in VMM cluster and live migration virtual nics not working

Hello Everyone,
I am having issues setting up converged network in VMM. I have been working with MS engineers to no avail. I am very surprised with the expertise of the MS engineers. They had no idea what a converged network even was. I had way more
experience then these guys and they said there was no escalation track so I am posting here in hopes of getting some assistance.
Everyone including our consultants says my setup is correct.
What I want to do:
I have servers with 5 nics and want to use 3 of the nics for a team and then configure cluster, live migration and host management as virtual network adapters. I have created all my logical networks, port profile with the uplink defined as team and
networks selected. Created logical switch and associated portprofle. When I deploy logical switch and create virtual network adapters the logical switch works for VMs and my management nic works as well. Problem is that the cluster and live
migration virtual nics do not work. The correct Vlans get pulled in for the corresponding networks and If I run get-vmnetworkadaptervlan it shows cluster and live migration in vlans 14 and 15 which is correct. However nics do not work at all.
I finally decided to do this via the host in powershell and everything works fine which means this is definitely an issue with VMM. I then imported host into VMM again but now I cannot use any of the objects I created and VMM and have to use standard
switch.
I am really losing faith in VMM fast.
Hosts are 2012 R2 and VMM is 2012 R2 all fresh builds with latest drivers
Thanks

Have you checked our whitepaper http://gallery.technet.microsoft.com/Hybrid-Cloud-with-NVGRE-aa6e1e9a for how to configure this through VMM?
Are you using static IP address assignment for those vNICs?
Are you sure your are teaming the correct physical adapters where the VLANs are trunked through the connected ports?
Note; if you create the teaming configuration outside of VMM, and then import the hosts to VMM, then VMM will not recognize the configuration.
The details should be all in this whitepaper.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

VLAN's in Oracle VM 3.0.1

hi all
i have made a trunk on the cisco switch for my port eth1. i trunk vlan16 and vlan20. when i create this two vlan segments in oracle vm, i have no connect. when i make a untagged vlan than it works with both networks. but i want split it in 2 segments. can oracle vm 3.0.1 work with this function / trunk from a cisco switch? or what must i do that i can define 2 segments over vlan on oracle vm?
greetz
franco

francok wrote:
i go to the hardware tab - vlan groups - create a VLAN with 2 Segments - VLAN16 Segment and VLAN20 Segment. This VLAN is running on the second networkinterface / eth1. eth0 is bonded / original / for Management. on ifconfig i see eth1 and eth1.16 and eth1.20. but i get no network contact on the vm's. when i make the vlan with a untagged vlan than i can give ip adresses from vlan16 and vlan20! what can i do that i can work with this two segments?If your IP addresses work with an untagged VLAN, then the VLAN stuff isn't working properly on your switch. Once you enable the VLAN stuff, it'll start tagging the packets with those VLAN IDs. I have several VLANs working in my OVM 3.0.1 install, so I know it works. :)

Ise & vlan load balancing (user balancing)

As far as I know anb based on some esperience in a test environment it seems that cisco ISE among two load balancing radius kind of attributes supports only vlan gropu assignment, this means that on the switches vlan group assignment is required.
A second method of passing multiple vlans or vlan IDs by radius attributes is not allowed.
Am I wrong?
The issue I'm trying to overcome is the following
Subnet1 /24
Subnet2 /22
Many, many switches
(and the situation can't be changed)
Assuming the vlan assignment is local to the switch and with a round robin method, once the IPs are exhausted on Subnet1 only half of the clients that authenticate will obtain an IP (on Subnet2) while the rest will get stuck on Subnet1 without an IP
The same situation comes up when considering an odd number of authenticated clients on every switch and with two /24 subnets: it is likely possible that Subnet1 will be "full" before the second subnet does falling in the previous situation.
is there any solution?
thank you in advance

Don,
You are right. I should have said - Forte uses its own partitioning scheme
not the default scheme you see when you open partition workshop.
Nirmal
From: Don Nelson <[email protected]>
To: Nirmal P Uppalapati <[email protected]>
Cc: [email protected]
Subject: Re: Load Balancing, User Visible Service objects, Running man
Date: Wednesday, October 22, 1997 10:45 PM
Nirmal,
One note on the "running man"...
At 08:12 PM 10/22/97 -0500, Nirmal P Uppalapati wrote:
3. Running Man
When you run an application by clicking on the running man Forte uses
its
default partitioning scheme and runs the application. The partitionscheme
that you made will be used only when you run the application distributedor
from the partition workshop. This is the time you might encounter errorsif
your partitioning is not right.
Actually, clicking on the "running man" from the repository or project
workshop will cause the application to be run VERY differently thanrunning
it distributed.
It's not technically correct to say that the default partitioning schemeis
used with the running man.
Forte consulting offers a deployment workshop that covers the finerpoints
of this and other distributed issues.
Don
============================================
Don Nelson
Regional Consulting Manager - Rocky Mountain Region
Forte Software, Inc.
Denver, CO
Corporate voice mail: 510-986-3810
aka: [email protected]
============================================
"If you ask me, though, any game without push-ups, hits, burns or noogies
is a sissy game." - Calvin

Cisco Layer 3, Voice, & VLAN

I have a vSphere 5.5 install and I'm in the process of a network upgrade in preparation for a VOIP implementation. The Switch hardware I'm using is a stack of Cisco 3850 Layer 3 switches and I've been going in circles on getting vlan traffic to work correctly. Hopefully someone can point me in the right direction.
I have one NIC connected to the switch (10GB fiber) that will handle all traffic for the esxi host (except for management). VLAN ID is set to None (0) and load balancing is set to Route based on originating virtual port.
I have 2 subnets, 10.1.0.0/16 (data & management, VLAN 1) and 10.10.1.0/24 (Voice, VLAN 10)
On the host I have a Win 2012 R2 server that will be a VOIP PBX host. It must be able to communicate with the IP phones (VLAN 10) and other servers (VLAN 1).
The switches will do the intervlan routing.
Finally my question - Can anyone give me some hints on how to set up the interface on the Cisco for the 10GB fiber connection from my host? Actual port settings would be extremely helpful. Anything I'm doing at the vmware end that I should be doing differently?

In case anyone comes across this in a search, here's what I ended up with, 1st the Cisco switch:
switchport trunk allowed vlan 1,10
switchport mode trunk
switchport nonegotiate
switchport voice vlan 10
macro description cisco-switch
spanning-tree portfast
spanning-tree link-type point-to-point
The virtual switch I set to all vlan IDs and Route based on originating virtual port.

Mesh Ethernet Bridging with VLAN Tagging Issue

Hi all.
I'm a little stuck with a 4400 7.0.220.0 + RAP 1550 + MAP 1260 Ethernet bridging issue. I'm using the VLAN tagging functionality and I'm finding that periodically a VLAN that I've tagged on the MAP will deregister from the backhaul and stop passing traffic. If I go into the Mesh tab on the MAP, select the wired interface, remove the VLAN from the list of tagged VLAN IDs and then add it right back to the list, its starts passing traffic again.
Has anyone else seen this? I can't find any relevant bugs.
Justin

Hi Saravanan,
It is one RAP and three MAPs. After a TAC call and 30 hours of monitoring, my VLANs have remained registered. I think the issue was mismatched VLANs to bridge groups an it looks like the mesh bridge may be stable for now. Here is what I was seeing on the RAP and MAPs when the VLANs were deregistering unexpectedly. Notice how VLANs 2 and 10 are mapped to opposite bridge groups on the RAP and MAP:
After I removed all the VLAN IDs from the Trunk configuration on the MAPs (through each AP's Mesh tab -- Ethernet Bridging config) and then rebuilt the VLAN IDs, I ran the same commands and now see this:
My very unscientific theory here is that the mismatching was causing consistency checks to fail, so the RAP was just tearing down the registrations after getting bogus or non- responses from the MAPs during the periodic VLAN registration maintenance checks (debug mesh ethernet registration).
If I have continued issues, I'll post back with updates.
Thanks for the response!
Justin

Flexconnect static mapping of WLAN to VLAN

5508 running 7.4
I want to create a definition for a particular site that maps WLANs (SSIDs) to switched VLANs. I know that I can go to Wireless => Select AP => VLAN mappings on an individual AP basis. But is there a way to create a group that will do this? I thought it could be done with flexconnect groups but I just could not find a way to make it happen there. Then I ran across this Architecting Network for Branch Offices with Cisco Unified Wireless Cisco Live presentation:
http://d2zmdbbm9feqrf.cloudfront.net/2013/usa/pdf/BRKEWN-2016.pdf
And on page 28 it states:
AP groups give the ability to statically map Wi-Fi service (WLAN) to VLAN based on physical location
And it then goes on to give a Configuration/VLAN mapping example in which I fail to see where VLANs are mentioned at all.
Is what I am trying to do possible?
Thanks,
-JEff

Hi Scott, thanks for the reply
I have a main campus with several different distribution blocks that each use unique VLAN IDs. And I have about a dozen remote sites that will all use common VLAN IDs. I am configuring a single SSID (WLAN 2) to be used across all of these locations. So at my main campus building "A" will have WLAN 2 mapped to VLAN 55 while building "B" will have WLAN 2 mapped to VLAN 65. At each of the remote sites WLAN 2 needs to be maped to VLAN 15.
So let's say I want to configure the main campus buildings A and B. I create a dynamic interface for vlan 55 and name it something creative like vlan-55, Likewise for vlan 65. Then I create an AP group named APG-55, add WLAN 2 to it and add all of my APs in that buliding. What I don't understand is where the dynamic interface comes into play. From your explanation it would seem that I need to assoiciate the dynamic interface to an AP group somehow. What am I missing?
Thanks!
-Jeff

Unable to add allowed VLANs to TenGig trunk port

Hi,
I've got a ten gig interface on a 6509 running 12.2(33) configured as a trunk, but I've not been able to add any allowed VLANs as I've done before on other ten gig ports on different 6509 chassis. Am I missing something obvious?
I'm assuming that the reason I'm unable to set the encapsulation to dot1q is because the new hardware doens't support ISL, hence no need. The command to add the VLANs however doesn't get rejected, it just doesn't appear to do anything.
I've tried adding single VLANs and multiples, but no joy. Any ideas?
Here's what I've done:
SWITCH_1631(config)#default int t4/1
Interface TenGigabitEthernet4/1 set to default configuration
SWITCH_1631#sh ru int t4/12
Building configuration...
Current configuration : 65 bytes
interface TenGigabitEthernet4/12
no ip address
shutdown
end
SWITCH_1631(config)#int t4/1
SWITCH_1631(config-if)#switchport
SWITCH_1631(config-if)#switchport mode trunk
SWITCH_1631(config-if)#switchport trunk allowed vlan ?
WORD VLAN IDs of the allowed VLANs when this port is in trunking mode
add add VLANs to the current list
all all VLANs
except all VLANs except the following
none no VLANs
remove remove VLANs from the current list
SWITCH_1631(config-if)#switchport trunk allowed vlan add 700
SWITCH_1631(config-if)#
SWITCH_1631#sh vlan id 700
VLAN Name Status Ports
700 VLAN_NAME active <snip>
SWITCH_1631#sh ru int t4/1
Building configuration...
Current configuration : 74 bytes
interface TenGigabitEthernet4/1
switchport
switchport mode trunk
end

Steve,
Thanks for getting back to me. You're right that it is by default a dot1q trunk allowing all VLANs, therefore it should work for what I want to do.
Port Mode Encapsulation Status Native vlan
Gi3/39 on 802.1q trunking 1
Te4/1 on 802.1q trunking 1
Po1 on 802.1q trunking 50
Po2 on 802.1q trunking 50
Po3 on 802.1q trunking 50
Po4 on 802.1q trunking 50
Po5 on 802.1q trunking 50
Port Vlans allowed on trunk
Gi3/39 15-16,20-23,30,401,608
Te4/1 1-4094
Po1 10,13,20-21,25,30,50,52,61,70,600,700-701,950
Po2 10,20,30,50,52,61,70,600,700-701,950
Po3 10,20,30,50,61,70,600,700-701,950
Po4 10,20,30,50,61,70,600,700-701,950
Po5 2-3,10-23,25-26,30,35-36,40,50-53,56,58,61,65,70,77,101-102,145-146,155-158,401-402,600-602,608,700-701,800,950
The problem was that I've always been advised that best practise is to only allow the VLANs that are actually required on a trunk to avoid broadcasting traffic unnecessarily. I worked out what the issue was though, and it was a pretty simple one!
Once I saw that 1-4094 was allowed I tried "switchport trunk allowed vlan remove 700" which worked and left me with 1-699,701-4094.
Then I realised what the problem was trying to use the "add" command when all possible VLANs had already been added. As soon as I got rid of it and used "switchport trunk allowed vlan 700" followed by "switchport trunk allowed vlan add 701" I was back in business.
So it was a very simple issue, but thank you Steve for pointing me in the right direction and confirming that all the VLANs were already allowed!

Migration of vlan IDs

Similar Messages

Maybe you are looking for