"Peer-switch" command on vPC domain and spanning-tree priority interaction

Hi guy,
We have 2 N7K (N7KA and N7KB) which will be running vPC in hybird and pure vPC environment.
I have a question about the Hybird and pure vPC environment. With the "peer-switch" command enable, should i tune the spanning-tree priority to be the same for all the vlan running on vPC on both N7KA and N7KB? This way, when i enter the "sh spanning-tree vlan X(vPC vlan) detail" command on N7K, it will list both N7K announc itself as "We are the root of the spanning tree".Also the switch running spanning-tree with N7K vPC vlan (Hybird), will see both N7K has the same priority (4096), and it is not desirable for a spanning-tree environment. Therefore, i used the "spanning-tree pseudo-information" on N7KB to tune the spanning-tree priority to "8192" and the switch running spanning-tree with N7K will list N7KB has a priority of 8192(perfect).
However, I notice some strange "show" output on the switch running Port-channel with the N7KA and N7KB. The "Designated bridge" priority is flapping as show on the switch. It is constantly changing between "4096 and 8192" with the same vPC system wide mac address.
Entering the "sh spanning-tree vlan X detail" command repeatly on switch with port-channel toward N7KA and N7KB.
>>sh spanning-tree vlan 10 detail
Port 65 (Port-channel1) of VLAN10 is root forwarding
Port path cost 3, Port priority 128, Port Identifier 128.65.
Designated root has priority 4106, address 0013.05ee.bac8
Designated bridge has priority 4106, address 0013.05ee.bac8
Designated port id is 144.2999, designated path cost 0
Timers: message age 15, forward delay 0, hold 0
Number of transitions to forwarding state: 1
Link type is point-to-point by default
BPDU: sent 5, received 603
one sec later.
>>sh spanning-tree vlan 10 detail
Port 65 (Port-channel1) of VLAN10 is root forwarding Port path cost 3, Port priority 128, Port Identifier 128.65. Designated root has priority 4106, address 0013.05ee.bac8 Designated bridge has priority 8202, address 0013.05ee.bac8 Designated port id is 144.2999, designated path cost 0 Timers: message age 15, forward delay 0, hold 0 Number of transitions to forwarding state: 1 Link type is point-to-point by default BPDU: sent 5, received 603
Configuration:
N7KA
spanning-tree vlan 1-10 priority 4096
vpc domain 200
peer-switch
N7KB
spanning-tree vlan 1-10 priority 4096spanning-tree pseudo-information vlan 1-10 designated priority 8192
vpc domain 200
peer-switch

We have a issue similar to this in our environment. I am trying to upgrade the existing 3750 stack router with 2 Nexus 5596 running VPC between them. For the transition I have planned to create a channel between 3750 stack and 5596's. Once this environment is set, my plan is to migrate all the access switches to N5k.
The issue is when I connect the 3750 port channel to both N5Ks, all the Vlans on 3750 started to flap. If I connect the port channel to only one N5K everything is normal; but when I connect the port channel to both N5K running VPC, vlans are flapping. Any idea what is going wrong here? Am I missing something?

Similar Messages

How to implement uplink redundancy and spanning tree in SFP-300 switches

We have several Small Business 300 Series Managed Switches, the 10/100 ones with PoE, the first generation ones.
We've been advised to implement uplink redundancy and spanning tree on these switches.
I'm sure spanning tree is a checkbox somewhere in the web interface.
How does one implement uplink redundancy besides interconnecting the switches plus turning on spanning tree (RSTP)??
Thank you, Tom
P.S. I also tried to file a service request but it does not work, I get: "Error 500: Request processing failed; nested exception is java.lang.NullPointerException"

Hello Thomas,
Thanks for using the Cisco Small Business eSupport Community. I've looked through the articles that are available in our Knowledge Base and found a few that I hope will be able to assist you in setting up spanning tree and link redundancy on your SFP300s:
In regards to link redundancy, the following article on LAG can hopefully provide some guidance:
Link Aggregate Group (LAG) Configuration on 200/300 Series Managed Switches
And for your question on setting up STP, here are a few articles with additional information:
Configure Spanning Tree Protocol (STP) Status and Global Settings on 200/300 Series Managed Switches
Setup Spanning Tree Protocol (STP) on a Interface on the 300 Series Managed Switches
I hope that this information helps! Please remember to mark your question as answered and rate if this solves your problem.
Best,
Gunner

Switching between the Classic View and the Tree View in transaction FEBA

Hi All
I would like to know how to switch between the Classic View and the Tree View on transaction FEBA for post processing of bank statements. I have a scenario where in the DEV client the transaction is calling up the Tree View and in my QA environment it calls up the Classic View, and I would like to know if there is a way to easily switch between the two views.
I'd appreciate your assistance.

Hi,
I think you can do the same using transaction codes FEBA and FEBAN.
Thanks
Aravind

2960X 15.0(2)EX5 Stack Bug? Master Switch Ports link in Orange, no spanning Tree

Is anyone aware of a bug in version 15.0(2)EX5 for 2960X Switches that would cause a switch in the master role to stop linking in new ports in green (and passing traffic). I have 2 2960X-48FPD-L Switches in a stack and whichever switch I designate master will only link new connections in orange and not pass traffic. All ports linked in show up/up and can be seen in a show cdp neighbor but won't pass any other traffic.
If I unplug the Stacking cables both switches become masters and ports linked in green on the previous member switch stay green, but after it switches to master any new connections plugged in only link in orange.
If I switch priorities and reboot the problem switches to the new master switch and the problem goes away on the member switch.
Also, a switch in the master role does not show any spanning tree instances for ports in the orange link state.
Has anyone seen this issue and do you know of a solution?
Jim

A quick update for those with this same problem.
1. 15.2(3)E turned out to be very unstable causing my switch stack to randomly lockup/reboot one of the switches about once a week.
2. I downgraded back to 15.0(2)EX5 but found a workaround. It turns out the switch stack with the 15.0 versions does not like the switchport voice vlan command on any of the interfaces on the master switch. I simply removed the voice vlan configuration on the interfaces and all the switch ports linked in just fine. I would prefer to run the phones on a voice vlan, but it still works without, just the PC's and phones are on the same vlan.
Jim

CSS Bridging and Spanning-tree

Greetings:
I have a configuration where I have two CSS attached to two WS 3550 switches. I'd like to connect an interface from each VLAN on each CSS to both 3550 switches (see attached). I have a problem when both of the interfaces are active in a VLAN. The spanning tree breaks down (both CSS see themselves as the root and one of the 3550's becomes the root for the two 3550's). Additionally, I had a situation where the ISL link between the 3550's shut down due to excessive spanning-tree errors.
I looked into using unconditional bridging, but that would cause problems on the "outside" interfaces as we can't predict how the VLAN's will be configured on that side of the CSS. We actually have a split situation where layer-3 path forwarding decisions are preferable on hte outside and layer-2 path forwarding descisions are preferable inside.

Wiwells,
Honestly, when I look at what you are doing, I feel you are making it overly redundant on the bridged side of things.
Why not simply connect each load balancer to only one switch rather than cross-connecting everything and then put a APP session between the load balancers?

Metro link and Spanning tree problem

HI all,
We have 4 switches connected like the diagram given below.
What happens when link between mux to mux goes down mean any fiber cut in SP network our ethernet interface from switch 1 doesn't go down and for vlan 2 all data goes black holed.
bcos switch 1 interface connected to mux is getting keepalive from tejas mux and it remains up even if fiber goes down between both the mux's.
and if link doesn't go down than all the data from vlan 2 goes black holed
please help ASAP

Sorry, still not clear to me.
If STP does not unblock a port as a result of a failure between the mux and the provider network, it means that it keeps receiving BPDUs through the mux. That means that the mux is switching traffic for the corresponding vlan between the two switches, and that means that no way STP can unblock without creating a loop (which is not the desired effect I guess).
Now, when this link between the mux and the provider network fails, why do you lose connectivity? You have two links between the mux and the provider network and the vlan exists in the two mux. Does it mean that the link between the mux and the provider network only carry one vlan? If this is the case, can't you prevent the mux from switching traffic between the two switches for the given vlan.
You see that there are way too many "ifs" in what I've just written. We need to understand what the "muxes" are.
Regards,
Francois

Discussion for spanning tree

If I want to connect the core switch (SW C3650S) in the corporate network to the core switch in the Data center (C6509E), anything i need to take note of its vtp mode and spanning tree? Will it affect the network in data center for propagation of vlan and spanning tree priority?
vtp mode for corporate core switch is transparent and its spanning tree setting is spanning-tree vlan 1-4000 priority 4096.

From your description, you shouldn't be too concerned. If vtp is transparent, it will ignore and pass along any vtp advertisements that it receives if needed. The stp priority is pretty low. The lowest is 0, and has to be done in increments of 4096. Which switch do you want to keep as the root bridge? If it's the corporate switch, you should be fine as long as the data center doesn't have the same priority or lower.
HTH,
John

VPC - peer gateway and peer switch

I understand that we need to use peer gateway on a vPC pair when HSRP is running, but why do we use peer switch if the vPC pair is not the root or seconday root of the network? Does it matter they send out different BIDs? What would be the worst case scenario when not using peer switch?

If you read the vPC Best Practices Design Guide the peer-switch feature reduces convergence time as a result of a spanning-tree failure from 3 seconds to sub-second.

Can I disable spanning-tree in a vpc domain ?

i have two N7718s in a vpc domain and each have a vpc connection to 300+ TORs(non cisco switch).
each 7718 have 300+ trunk port and a trunk port carring 80 vlans . so the logical port number is 300*80 = 24000
the problem is n7k r-pvst logical ports limit is 16000,it causes the vpc primary 7718 ping latancy time exceed 1000ms
2 ways to solve this problem : use mst instead of rpvst or disable spanning-tree
if i use mst , the logical ports limit is 90000, the problem will appear one day
so i want to disable spanning-tree . 7718s' vpc link to TOR use lacp ,it will prevent some layer2 loops. can i do it?

I have the same problem. :)

SGE2010 switches, VLAN's and a blocked port in spanning-tree

Folks,
I have 2 switch groups.
2 SGE2010's with VLAN's defined as 10,20 and 30
Vlan 10 is the management VLAN, and it uplinks to our border router.
Vlan 20 is the workstation VLAN, and all workstations point to the switch as their default GW
Vlan 30 is the ip phone VLAN, and all phones use this as their gateway.
I would like to put a LAG between said switches, we have some servers on the ip phone switch that need to be accessed by the workstation clients, and the single 100mb link through the router is probably not going to be enough.
As I understand it, because the switches have different networks on them, a simple lag will not work. I did create a lag, and assign ip addresses to each side, however in that mode, it doesn't appear I can block vlan 10 from transiting the LAG, and with out that block I will end up with a logical loop, and spanning-tree will block one of the uplinks, or the LAG itself.
I have attached an image with a diagram of our current set up.
Any help/advice would be much appreciated.

Tom,
I remember our conversation a few weeks ago. I did not get a chance to have a go at MSTP, mainly because I have no expierence with it, and looking at the configuration properities, it looks a little daunting.
It has also been a very busy few weeks with the deployment of 200+ phones across several sites, and the system is functioning great with out the LAG trunk, I am just trying to plan for the future.
I made a few postings a few weeks ago, one here and one on the Cisco forums on reddit, and a user there gave me some advice I have been unable to make work (I think it's just wrong), but I would love to go this route if it is in fact possible.
Here is the thread : http://www.reddit.com/r/Cisco/comments/x91tc/vlan_trunks_spanning_tree_and_a_port_blocked/c5kskch
This user implies it's possible to block a VLAN across the LAG which would end the logical loop problems.
It looks like his advice is to make the LAG into a trunk, and then block specific VLAN's from transiting it, but in trunk mode, I can't assign it an IP, so I am sorta wondering how exactly you transport packets across it.
Can you confirm that his advice is in fact incorrect?
If MSTP is my only route, then I suppose it's time to dig into the docs and see If I cant get it up and running.

N7K Peer-switch Konfiguration

Hi I have a question regarding peer-switch konfiguration on a vPC/vPC+ pair of N7K with vPC and non vPC attached switches
If I understood correctly with following configuration
for vPC attached switches (assuming the have default STP-prio) the vPC-bundle acts as one Switch with the priority of 4096
for STP non-VPC attached switches for VLAN1-1960 the N7K-A is the root-bridge and for VLAN 1961-3920 the N7K-B is the root-bridge,
N7K-A
vpc domain 20
peer-switch
role priority 1
spanning-tree pseudo-information
vlan 1-3920 root priority 4096
vlan 1-1960 designated priority 4096
vlan 1961-3920 designated priority 8192
N7K-B
vpc domain 20
peer-switch
role priority 2
spanning-tree pseudo-information
vlan 1-3920 root priority 4096
vlan 1-1960 designated priority 8192
vlan 1961-3920 designated priority 4096
Is that coorect so far ?
If yes then I have one outstandig question.
Do we need the global configuration for spanning-tree priority in this case?
spanning-tree vlan 1-3920 priority 4096
as we configure it in a pure vPC environment
N7K-A
spanning-tree vlan 1-3920 priority 4096
vpc domain 20
peer-switch
role priority 1
N7K-B
spanning-tree vlan 1-3920 priority 4096
vpc domain 20
peer-switch
role priority 2
Thanks
Hubert

Here is a description of the use of the Spanning-tree Pseudo-information and the Peer switch command on the Nexus 7000. Maybe this will help clarify some misunderstanding:
SETUP:
7K1 and 7K2 are vPC peers and have a higher priority      than 7K3. So 7K1 and 7K2s ports to 7K3 will all be DESIGNATED.
7K3 is connected to both 7K1 and 7K2 using individual      STP links.
7K4 is connected to both 7K1 and 7K2 in a vPC.
Common Points for all Scenarios:
If vPC fails for whatever reason; all links will revert      to regular spanning-tree.
The root priority on 7K1 and 7K2 will be the vPC System-MAC (same on both) and the Designated priority will use the respective non-vPC System-MACs of 7k1 and 7K2
Even if the STP Priority is configured globally and lower, the Pseudo Root Priority and Designated Priorities are still used for STP calculations.
The STP Pseudo-information HACK:
Allows you to set a different root priority and different designated priority. To satisfy the requirement for the Peer switch command and still be able to perform VLAN load balancing for non-vPC dual connected links.
Root Priority: Used in Root Bridge Election
Designated Priority: Used in Designated Bridge Election
SCENARIO 1: Same STP Priority configured Globally with the Peer switch Enabled (Individual STP links)
The Root priority and Designated priority on 7K1 and 7K2 will be the same as the globally configured or default STP priority
One of the links to 7K1 and 7K2 becomes the "Root Port" and the other becomes "ALTN BLK"
Since they have the same Root Priority and the same vPC system MAC, the lower port will be selected as the root port.
SCENARIO 2: BOTH STP Pseudo-information Root and Designated Priorities Configured with Peer Switch Enabled (Individual STP links)
The Root priority may be different from the Designated Priority based on the STP Pseudo-information configuration.
VLAN traffic from 7K3 is load balanced between 7K1 and 7K2 based on the configured Pseudo-Designated Priority. So the Root port for a VLAN from 7K3 will be to the device with a lower Pseudo-Designated priority.
SCENARIO 3: ONLY STP Pseudo-information Root Priority Configured with Peer Switch Enabled (Individual STP links)
The Root priority and Designated Priority are the same as the Pseudo Root Priority.
No VLAN load balancing occurs
The Root port is the link to the vPC primary switch. The Link to the vPC Secondary is “ALTN BLK”.
SCENARIO 4: ONLY STP Pseudo-information Designated Priority Configured with Peer Switch Enabled (Individual STP links)
The Root priority will be the Globally configured or default STP Priority
The Designated priority will still be the Pseudo-Designated priority
VLAN load balancing will still occur.
SCENARIO 5: Same STP Priority configured Globally with the Peer switch Enabled (vPC links on 7K4)
The Root priority and Designated priority on 7K1 and 7K2 will be the same as the globally configured or default STP priority.
If the vPC Peer-link fails, the interface going to the secondary vPC device (7K2) will be shut DOWN.
SCENARIO 6: BOTH STP Pseudo-information Root and Designated Priorities Configured with Peer Switch Enabled (vPC links on 7K4)
The Root priority and Designated Priority are the same as the configured Pseudo-Root Priority.
If the vPC Peer-link fails, the interface going to the secondary vPC device (7K2) will be shut DOWN.
SCENARIO 7: ONLY STP Pseudo-information Root Priority Configured with Peer Switch Enabled (vPC links on 7K4)
The Root priority and Designated Priority are the same as the configured Pseudo-Root Priority.
If the vPC Peer-link fails, the interface going to the secondary vPC device (7K2) will be shut DOWN.
SCENARIO 8: ONLY STP Pseudo-information Designated Priority Configured with Peer Switch Enabled (vPC links on 7K4)
The Root priority and Designated priority on 7K1 and 7K2 will be the same as the globally configured or default STP priority.
If the vPC Peer-link fails, the interface going to the secondary vPC device (7K2) will be shut DOWN

Mono spanning-tree and PVST

Refering to these two links
http://www.cisco.com/en/US/tech/tk389/tk390/technologies_tech_note09186a0080094665.shtml
http://www.experts-exchange.com/Hardware/Routers/Q_21349385.html
IEEE 802.1Q defines a single instance of spanning tree running on the native VLAN for all the VLANs in the network which is called Mono Spanning Tree (MST). This lacks the flexibility and load balancing capability of PVST available with ISL. However, PVST+ offers the capability to retain multiple Spanning Tree topologies with 802.1Q trunking.
IEEE 802.1Q defines a single instance of spanning tree running on the native VLAN for all the VLANs in the network which is called Mono Spanning Tree (MST). This lacks the flexibility and load balancing capability of PVST available with ISL. However, PVST+ offers the capability to retain multiple Spanning Tree topologies with 802.1Q trunking.
http://networking.ringofsaturn.com/Certifications/BCMSN.php
Per-VLAN Spanning Tree (PVST) ? A Cisco proprietary method of connecting through 802.1Q VLAN trunks, the switches maintain one instance of the spanning tree for each VLAN allowed on the trunk, versus non-Cisco 802.1Q switches which maintain one instance for ALL VLANs. This is the default STP used on ISL trunks.
http://www.informit.com/content/images/1587051427/samplechapter/1587051427content.pdf
The 802.1Q standard defines one unique Spanning Tree instance to be used by all VLANs in the network. STP runs on the Native VLAN so that it can communicate with both 802.1Q and non-802.1Q compatible switches. This single instance of STP is often referred to as 802.1Q Mono Spanning Tree or Common Spanning Tree (CST). A single spanning tree
lacks flexibility in how the links are used in the network topology. Cisco implements a protocol known as Per-VLAN Spanning Tree Plus (PVST+) that is compatible with 802.1Q CST but allows a separate spanning tree to be constructed for each VLAN. There is only one active path for each spanning tree; however, in a Cisco network, the active path can be
I could not get exactly what these Terminology (PVST, instance, PVST+, MST, etc) trying to achieve ?
Any URL and online resource help me to do some extar reading to clarify these terminology

Hi,
The URLs that you have provided all explains the same technical details in different fashion.
I will summarise them here for better clarity.
There are two separate technologies that needs clarity.
1) Method of Trunking many vlans across a link
2) Spanning tree
Now for point 1, we have the IEEE standard 802.1q, which mentions how multiple vlans can be carried across a link. As per this standard a 4 byte tag will be inserted in the ethernet packet, ( inserted between the Destination mac address field and the ethertype field)
This tag will contain the vlan identifier info and some other details ( available in the urls that you have highlighted)
Cisco has a proprietary technology called ISL which effectively does the same job in a different fashion but can only be used in cisco devices.
Now for point 2, again we have IEEE standards like 802.1d ( common/mono spanning tree), 802.1w/RSTP ( Rapid spanning tree) and 802.1s/MSTP.
In 802.1d, there will be only one spanning tree process/instance running for the whole network, irrespective of how many vlans are involved in the network. Hence the whole network is treated as one common domain by the STP protocol.
So, there can be only one root bridge in the network and other bridges will intelligently block the redundant links, we wont have much control to effectively utilise the redundant links.
IEEE 802.1w/RSTP also works in the same fashion, but the convergence time is very fast in this protocol.
Here also there is only one spanning tree instance involved.
In both the above STP protocols, there is only one instance/process of the protocol running in the network, which is common for all vlans. Hence these protocols consume only very less CPU utilisation.
In 802.1s/ MSTP ( multiple spanning tree), extends the 802.1w Rapid Spanning Tree Protocol (RSTP) to have multiple STP instances. In this protocol, we can group the desired vlans in to one Instance of the protocol.
Say for example, lets assume a typical campus network with multiple access switches, 2 distribution/core switches.
Access switches having dual connectivity to the distribution/core switches.
In this topology if we deploy 802.1d or 802.1w, the redundant links from the access switches to the distribution/core switches will be blocked. Only one uplink from the access switch to the distribution layer will be working at any point.
In this network, only one distribution/core switch will be root bridge for the entire network.
But if we deploy 802.1s for this network, we can design it as follows.
We can split the vlans in to two groups,
Group1 => vlan 1 to 50
Group2 => vlan 51 to 100
We can create two instance of MSTP protocol with the following mappings
Instance 1 => for Group 1, with one distribution/core switch as the root bridge
Instance 2 => for Group 2, with another distribution switch as the root bridge
--Continued

Cldg switch command hangs for long time

Hello Experts ,
We have renamed the veritas volumes vol1 and vol2 of disk group "dg", which is under cluster control.
The renaming of volumes are successfully completed and modification updated in Cluster CCR (cldg sync dg) and volumes are mounted successfully in node002.
We have switch over the disk group "dg" from node002 to node004. The disk group switch over to the node node004 successfully and able to mount the volumes.
Again, we have switch over the disk group "dg" from node004 to node002, but the switch command is not successful and hanged for long time. When we check the /var/adm/messages in node002, the below messages appeared
Oct 22 11:49:39 node002 scsi: [ID 107833 kern.warning] WARNING: /pci@0,600000/pci@0/scsi@1 (mpt0):
Oct 22 11:49:39 node002 Disconnected command timeout for Target 0
Oct 22 11:50:49 node002 scsi: [ID 107833 kern.warning] WARNING: /pci@0,600000/pci@0/scsi@1 (mpt0):
Action plan followed for renaming the volume:*
node002:/var/tmp/bak# umount /local/mqm/log/mq_log
node002:/var/tmp/bak# umount /local/mqm/qmgrs/mq_qmgr
node002:/var/tmp/bak# vxvol -g dg stop vol1
node002:/var/tmp/bak# vxvol -g dg stop vol2
node002:/var/tmp/bak# vxedit -g dg rename vol1 vol1_log
node002:/var/tmp/bak# vxedit -g dg rename vol2 vol2_qmgf
node002:/var/tmp/bak# vxvol -g dg start vol1_log
node002:/var/tmp/bak# vxvol -g dg start vol2_qmgf
node002:/var/tmp/bak# cldg sync dg
Please advice on this error and how to resolve this.
Regards,
R. Rajesh Kannan

But what is device mtp0? It doesn't sound like a disk name. It is having SCSI problems. I don't know if these messages are relevant though.
I don't use VxVM as a rule, but your procedure seems reasonable to me.
Tim
---

Nexus spanning tree pseudo configuration

Hi
I am trying to understand the pseudo configuration commands in a Nexus hybrid topology.
I have vlans a, b and c only in the vPC side of the topology. I have peer switch configured and the same stp priority on both switches.
In the standard Spaning-tree topology I have completely seperate vlans x, y and z.
What should I be configuring in the pseudo config section ? Do I define a pseudo root priority for all vlans a, b, c and x, y, z or just for the standard spanning tree vlans x, y and z. I need to avoid and, even short, spanning tree outages if I take one Nexus out of service for a short time.
My thinking is that if one Nexus is out of service the physical mac will be used and potentially reduce the root priority of the vPC vlans causing a TCN and STP recalculation in vlans a, b and c. This can be avoided by configuring a pseudo root priority for all Vlans lower than the current spanning tree priority shared by the vPC peers. Is this correct ? However, since I have a shared priority of 8192 on current vPC vlans will configuring, for example, a pseudo root priority of 4096 on those vPC vlans won't this also cause the TCN and recalculation I am trying to avoid ? Is the benefit of the pseudo root config only obtained if it is configured at the start when the vPC is formed and prior to the peer switch command being issued ?
Thanks, Stuart.

Hi Ajay,
It is recommended that switch-to-switch links are configured with the spanning-tree port type normalcommand. The one exception is the vPC peer-link which is recommended to configure with the spanning-tree port type network command.
Take a read of the Best Practices for Spanning Tree Protocol Interoperability from page 56 of the vPC Best Practice Design Guide for further information on this.
Regards

Spanning Tree on RV220W

Hello,
I'm using the RV220W in a small office. Now I would like to add two switches with spanning tree activated. I can see from the RV220W datasheet that it supports spanning tree. I also found a manual to configure it.
http://sbkb.cisco.com/CiscoSB/ukp.aspx?login=1&pid=2&app=search&vw=1&articleid=2296
Article ID 2296
The problem is I can't find this settings on my router which has got the newest firmware 1.0.5.8
Is it activated by default, or was this function deleted in later firmware versions?
Regards
Timo Ostendarp

The 7ks as roots with the priority and peer-switch commands as you show above would be best practice. With that, you wouldn't have to make any non-default spanning-tree settings on the 5k switches.

"Peer-switch" command on vPC domain and spanning-tree priority interaction

Similar Messages

Maybe you are looking for