06-22-2010 04:09 AM - last edited on 03-25-2019 04:11 PM by ciscomoderator
I am trying to connect a Cat3560G switch to an N7K pair via a vPC. The VLANs I wish to trunk are being suspended, I am getting the following error messages:
2010 Jun 22 17:03:36 N7K-Core1 %ETHPORT-3-IF_ERROR_VLANS_SUSPENDED: VLANs 2,301 on Interface port-channel2 are being suspended. (Reason: Vlan is not allowed on Peer-link)
06-22-2010 04:15 AM
Hi,
Allow the vlan 2 and 301 over the trunk using the below command
Nk-1(config-if)# switchport trunk allowed vlan 2,301
http://conft.com/en/US/prod/collateral/switches/ps9441/ps9670/configuration_guide_c07-543563.html
Hope to Help !!
Ganesh.H
Remember to rate the helpful post
06-22-2010 04:29 AM
it trunks all vlans by default
06-22-2010 04:34 AM
my bad, spotted the obvious mistake
06-22-2010 11:06 AM
Can you send the po2 config on Nexus?
08-13-2010 01:37 PM
I'm having the same issue between a pair of vPC'd 5020s going to a 6500 using a vPC.
All VLANs which are supposed to go over the trunk/vPC, are showing as err-disable on trunk. I've checked all configs and they are the same... allowed vlans match on all po interfaces and physical interfaces.
6509:
interface Port-channel78
description Connection to n5020s @ in the MDC
switchport
switchport trunk encapsulation dot1q
switchport trunk native vlan 2240
switchport trunk allowed vlan 2002-2006,2010,2014,2018,2022,2024,2026,2240
switchport trunk allowed vlan add 2244,2248,2252,2254,4050,4052,4054
switchport mode trunk
end
N5020-1:
interface port-channel100
description Uplink to dist01 @ A building
switchport mode trunk
switchport trunk native vlan 2240
switchport trunk allowed vlan 2002-2006,2010,2014,2018,2022,2024
switchport trunk allowed vlan add 2026,2240,2244,2248,2252,2254,4050
switchport trunk allowed vlan add 4052,4054
vpc 100
08-13-2010 01:53 PM
You did what I did, omitted the trunk command on the vPC peer-link. Your config is:
08-13-2010 02:45 PM
Hi - thanks for the quick reply!
I also noticed that running the command "switchport trunk allowed vlan all" told the peer-link to allow all vlans. I didn't see it doing that by default... ?
Also, I changed the port-type to "normal" for the spanning-tree config. I had an issue with one of the downstream devices wanting to be STP root for some VLANs... I changed the peer-links to "spanning-tree port type normal" and that solved the problem of the 5010 wanting to be root instead of our 6509 upstream.
Thanks,
Chris
08-21-2012 03:55 PM
Answer
interface port-channel1
description * vPC Peer-Link *
vpc peer-link
spanning-tree port type network
You do need one more command. to turn peer link as trunk. otherwise it will not transfer any vlan through Peer-link
"switchport mode trunk"
01-30-2013 05:58 PM
Hi,
I got the same issue but the difference is the configuration is in fabricpath.
interface port-channel1
switchport
switchport mode fabricpath
spanning-tree port type network
vpc peer-link
%ETHPORT-3-IF_ERROR_VLANS_SUSPENDED: VLANs 971 on Interface port-channel1 are being suspended. (Reason: Vlan is not allowed on Peer-link)
01-13-2015 11:02 AM
01-13-2015 10:58 AM
We have some issues with creating new vlans on the N7K switches. This is due to a bug (CSCtr08143) on the current software version we are running.
The permanent fix is to upgrade the switches to new version as we are running a really old code but there is a simple workaround that resolves the issue if you see it..
Here is the workaround:
-Create vlan on both switches
-Confirm that both switches have vlan created by using command ‘show vlan’ or ‘show vlan id xxxx’
-Perform a ‘no spanning-tree vlan xxxx’
-Then perform ‘spanning-tree vlan xxxx’
-Use ‘show spanning-tree vlan xxxx’ to see if the vlan has now been created and if forwarding
Cheers!!
Vinod
04-04-2016 12:29 PM
NEVER disable spanning tree on a production switch!
You will create a loop!
If you create a loop you may need to reboot the switch in order to recover from it!
05-17-2016 03:56 AM
What version has this issue ? I'm having the same issue while creating a new VLAN. it's showing suspend.
03-02-2015 11:34 PM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
We have some issues with creating new vlans on the N7K switches. This is due to a bug (CSCtr08143) on the current software version we are running.
The permanent fix is to upgrade the switches to new version as we are running a really old code but there is a simple workaround that resolves the issue if you see it..
Here is the workaround:
-Create vlan on both switches
-Confirm that both switches have vlan created by using command ‘show vlan’ or ‘show vlan id xxxx’
-Perform a ‘no spanning-tree vlan xxxx’
-Then perform ‘spanning-tree vlan xxxx’
-Use ‘show spanning-tree vlan xxxx’ to see if the vlan has now been created and if forwarding
Cheers!!
Vinod