Timeline for Using SNMP retrieve MAC addresses of directly connected machines to a switch
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 21, 2014 at 5:57 | comment | added | cpt_fink | I had to go ask on that old thread why portfast towards switches... I recognize the poster so I know he's got a valid reason for saying that, I just don't know what it is. | |
| Nov 20, 2014 at 20:13 | comment | added | Eddie | @MikePennington, there are always exceptions ;) I changed the wording of that phrase to indicate its not a guarantee. But, I think we can all agree that in most networks, a "portfast" interface is going to typically (99% of the time) mean an end host. If a Portfast idealist happens to be in charge of the network, and intentionally set all his ports to Portfast, then surely when Subhash explains how his application works, that particular idealist will clue in that his network is the exception case. | |
| Nov 20, 2014 at 20:09 | history | edited | Eddie | CC BY-SA 3.0 |
Added "see below" regarding Edge Ports and end hosts.
|
| Nov 20, 2014 at 19:44 | comment | added | YLearn | @MikePennington, to clarify, I believe the point is to use portfast on all client/customer facing ports (along with BPDUGuard), whether they are access ports or trunk ports. If you provide an trunk port to a client device without portfast enabled and are running RST on your network (or possibly MST depending on configuration), then you will most likely result in a situation where your network will take as long as CST to converge rather than the faster RST timers. | |
| Nov 20, 2014 at 18:20 | comment | added | Mike Pennington | FYI "portfast" is not always indicative of user ports; some engineers advocate portfast on all ports | |
| Nov 20, 2014 at 16:43 | history | answered | Eddie | CC BY-SA 3.0 |