04-07-2009 10:31 PM - edited 03-04-2019 04:17 AM
hello
when i set up vlan350 is a root bridge on switch 6500.
why failed mesg shown when i enter this command below.
kor-dc2-65sw1> (enable) set spantree root 350
and failed mesg show:
Failed to set hello time for spantree 350.
Failed to set max aging time for spantree 350.
Failed to set forward delay for spantree 350.
thak you.
04-07-2009 10:53 PM
Hello Worapun,
have you created vlan 350 before ?
sh vlan 350 what tells ?
Hope to help
Giuseppe
04-07-2009 11:15 PM
this is sh vlan 350
thank you
kor-dc2-65sw1> (enable) set spantree root 350
Failed to set hello time for spantree 350.
Failed to set max aging time for spantree 350.
Failed to set forward delay for spantree 350.
VLAN 350 bridge max aging time set to 20.
VLAN 350 bridge hello time set to 2.
VLAN 350 bridge forward delay set to 15.
Switch is now the root switch for active VLAN 350.
Switch is already the root switch for active VLAN 350.
kor-dc2-65sw1> (enable)
kor-dc2-65sw1> (enable) sh spantree 350
VLAN 350
Spanning tree mode RAPID-PVST+
Spanning tree type ieee
Spanning tree enabled
Designated Root 00-d0-02-0b-c5-5d
Designated Root Priority 1
Designated Root Cost 0
Designated Root Port 1/0
Root Max Age 20 sec Hello Time 2 sec Forward Delay 15 sec
Bridge ID MAC ADDR 00-d0-02-0b-c5-5d
Bridge ID Priority 1
Bridge Max Age 20 sec Hello Time 2 sec Forward Delay 15 sec
Port State Role Cost Prio Type
------------------------ ------------- ---- -------- ---- --------------------
3/10 forwarding DESG 3004 32 P2P, PEER(STP)
4/4 forwarding DESG 3004 32 P2P, PEER(STP)
04-08-2009 12:45 AM
Hello Worapun,
I think this is caused by the fact that the switch was already the root bridge for vlan 350.
Everything looks like fine so probably you can ignore this.
Hope to help
Giuseppe
04-08-2009 04:29 AM
Worapun:
The forward delay, hello and maxage timers are set by default in STP. You dont need to set them. Per-vlan Spanning Tree (PVST+) is on by default on Cisco switches.
Hello is every 2 secs.
Forward Delay is 15 secs.
Max age is 20 secs.
These messages appeared because you were telling the switch to be the root bridge for vlan 350, but it already was, so no changes were made.
Try making another switch that is not the root the root for a particular vlan and see the results.
HTH
Victor
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: