Can you explain why it is a best practice to disable portfast connected to a L3 device such as a router? Switch, obviously, but a router?
---- Matthew Huff | 1 Manhattanville Rd Director of Operations | Purchase, NY 10577 OTA Management LLC | Phone: 914-460-4039 aim: matthewbhuff | Fax: 914-460-4139 > -----Original Message----- > From: [email protected] [mailto:cisco-nsp- > [email protected]] On Behalf Of Chris Gotstein > Sent: Wednesday, May 23, 2012 2:15 PM > To: Gert Doering > Cc: [email protected] > Subject: Re: [c-nsp] Lot of input errors on a NPE-G1 interface > > It's probably not going to address the overrun issue, but from a best > practices stand point, it should not be enabled on interfaces that > connected to other connected devices, ie a router or switch. > > On 5/23/2012 12:57 PM, Gert Doering wrote: > > Hi, > > > > On Wed, May 23, 2012 at 10:18:45AM -0500, Chris Gotstein wrote: > >> First suggestion i would make is removing spanning-tree portfast > from > >> the switch config. > > > > How exactly is that going to *help* with overruns? > > > > All it will do is annoy you after a link flap, and if you run rstp, > it > > will annoy half your network after a flap on that link. > > > > gert > > -- > ---- ---- ---- ---- > Chris Gotstein, Network Engineer, U.P. Logon/Computer Connection U.P. > http://uplogon.com | +1 906 774 4847 | [email protected] > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
