To properly interpret this, a diagram of the network would be required. Do you use an MLTs? These would/should have STP disabled so the switch would not participate in Spanning Tree - Root Cost:0, Root Port:0. At least that's what I'm thinking. :-)
Hi
Thanks for your reply. I had been busy hence couldn't reply. May be following will be helpful to someone in future.
What I found was, STP Learning was disabled on the underlying ports in the MLT.
Avaya-5510-48T#show running-config module stp
! Embedded ASCII Configuration Generator Script
! Base model = Ethernet Routing Switch 5510-48T
!
!
!
!
! Displaying only parameters different to default
!================================================
enable
configure terminal
!
! *** RSTP (Phase 1) ***
!
!The Spanning tree operation mode cannot be changed without rebooting.
!The Spanning tree operation mode is required to be set to RSTP before
!loading this ASCII configuration file.
spanning-tree mode rstp
spanning-tree rstp priority 2000
!
! *** RSTP (Phase 2) ***
!
interface FastEthernet ALL
spanning-tree rstp port 45,47 learning disable
exit
Hence switches saw themselves as the root bridge. So I enabled Learning using the following commands
conf t
int fastEthernet 45,47
spanning-tree rstp port 45,47 learning enable
exit
Above config solved the root bridge issue. Furthermore I added some stp optimization commands to bring ports connected to edge devices like computers, printer up (forwarding state) asap without going usual spanning Blocking, Listening, Learning and then forwarding. Also to disable and auto recover if bpdu is detected on the port it shouldn't be seen on because of human error or a network loop.
conf t
interface fastEthernet 6-44
spanning-tree rstp port 6-44 edge-port true (this is same as Cisco spanning tree portfast)
spanning-tree bpdu-filtering port 6-44 enable timeout 60 (bpdu-filtering will block the port if a spanning tree bpdu is seen on ports between fastethernet 6 to 44 for sixty seconds and will automatically enable the port after checking if there are no more bpdu just after 60th sec. If bpdu are still seen after 60sec port will not be auto recovered. This feature is similar to Cisco error disable and error recovery. timeout is a must feature if you have a large network and you don't want to run around console to every switch to recover while the network is down for the business. One can also choose to leave the port disabled and not auto recover after 60 sec. By default timeout value is 120 sec on Avaya 5510 ). On cisco I think it use to be 300sec.
example command the output excerpt.
#sh running-config ver module stp
spanning-tree bpdu-filtering port 5/10 enable timeout 120
Thanks again.