Thanks for reviewing Edison. I wanted a second opinion. We ran BPDU guard and loop detection tests by using multilpe hubs and switches and looping them back into the network. Switches and RSPT handled the loop detection and port err_disablement perfectly. The network didn't skip a beat.

Thanks again,

Brad

With RSTP I though portfast was an inherent state or role of ports connected to none STP speaking devices??

Hi

If i understand you correctly then yes portfast is the equivalent of an "edge" port in RSTP. However you still need to use portfast keyword ie. from Cisco doc

=============================================

Edge Ports

The edge port concept is already well known to Cisco spanning tree users, as it basically corresponds to the PortFast feature. All ports directly connected to end stations cannot create bridging loops in the network. Therefore, the edge port directly transitions to the forwarding state, and skips the listening and learning stages. Neither edge ports or PortFast enabled ports generate topology changes when the link toggles. Unlike PortFast, an edge port that receives a BPDU immediately loses edge port status and becomes a normal spanning tree port. At this point, there is a user-configured value and an operational value for the edge port state. The Cisco implementation maintains that the PortFast keyword be used for edge port configuration. This makes the transition to RSTP simpler.

=============================================

Jon

Thank you sir!