[c-nsp] Lot of input errors on a NPE-G1 interface

Chris Gotstein chris at uplogon.com
Wed May 23 16:02:37 EDT 2012


I always just played it safe, but now i'm better informed, thank you.

On 5/23/2012 2:27 PM, Phil Mayers wrote:
> On 05/23/2012 08:18 PM, Chris Gotstein wrote:
>> %Warning: portfast should only be enabled on ports connected to a single
>> host. Connecting hubs, concentrators, switches, bridges, etc… to this
>> interface when portfast is enabled, can cause temporary bridging loops.
>>
>> My understanding of this was a router would be included as well since
>> it's used to connect multiple hosts.
>
> If you don't enable portfast, you have to suffer the STP state
> transitions, which lead to delays in traffic forwarding after link-up.
>
> Portfast basically means: "This port is unlikely to be connected to
> another bridge or hub, so skip the LISTENING/LEARNING transitions and
> jump straight to forwarding; if it goes wrong, STP will close the loop
> shortly."
>
> It's not magic; and it should be enabled on all host ports. Routers are
> hosts, at layer2.
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/

-- 
---- ---- ---- ----
Chris Gotstein, Network Engineer, U.P. Logon/Computer Connection U.P.
http://uplogon.com | +1 906 774 4847 | chris at uplogon.com


More information about the cisco-nsp mailing list