I configured 2 3550 switches with ISL trunk, and switch #1 is server and another is client under same VTP domain, switch #1 is root switch, There is a vlan named VLAN_A, here is thing, i'd like to change STP hello timer of VLAN_A
Q, I changed Hello timer of VLAN_A on root switch switch#1, but on switch#2 has still old Hello timer value, do I have to change Hello timer both switch manually? VTP is enabled and works fine.
In first place, I thought exact same as you, but like I said before, on switch#2, hello timer of VLAN_A is unchanged,,, then just ignore those unchanged hello timer of downstream switches, is this what you mean?
Yes that is what I mean you need not change it on downstream switch because BPDU is always generated by root switch so if you change it on root it will send with the change timer and it will be fwded by the switches on way with same timer.
So for suppose you change it on root bridge to 1 it will keep on sending the BPDU every 1 second to the downstream switches and each downtream switches will just fwd it.
Remember if it is a small network of few switches like in your case 2 switches it is ok to change the STP default timers but if incase it is a big network there are chances of loop also if you play around with the timers so just take care of that part.
Thanks for answering, one more thing, VTP makes share the vlan information between switches, once vlan information is changed on root switch(VTP server mode), then other switches under same VTP domain should share those vlan informations, how come switch#2 still have old Hello timer?
VTP indeed propagates the vlan information but the spanning tree parameter is not a vlan parameter. Actually, Cisco CLI is not very clear in this regards because it mixes the vlan and the STP instance running on the vlan. When you see "spanning-tree vlan X", you must understand "spanning instance-running-on-vlan X blah". This is because until recently Cisco switches were only running PVST (per-vlan STP) where each vlan has its own STP instance.
thanks for answering, so when i change STP parameter of a vlan on root switch then it will happen inconsistency of STP parameters and to fix this inconsistency, what do i have to do? changing STP parameters on every switches (include root switch) manually is only solution?
The timer values are propagated inside the BPDUs that are sent by the root. So if your other bridges see the correct root, they will also accept the timer values from this root. Considering the parallel you make with VTP, I have the feeling that you expect STP to change the configuration of your other switches to match the one of the root. This will not happen. Only the *operational* values of the timers (hello-time, max-age and forward-delay) are modified to match the root information. You should be able to see that with the "show spanning-tree [detail]" command. STP does not change the configuration of the switch: the "show run" will be unaffected.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...