What is doing the pinging and what is being pinged? In addition to the great advice from Michael, which has you check to see when the switch learns a MAC address, keep in mind that the pinger needs to get a MAC address too. Assuming it's on the same subnet as the device that it is pinging, it will ARP for the device. That can take a little while. If the pinger is a PC, you can check its ARP table with arp -a from an MS-DOS prompt.
If the devices are in different subnets, then the pinger would ARP for its default gateway. Just a couple other things to keep in mind, not a definite answer. Priscilla At 10:58 AM 10/30/01, Michael Williams wrote: >I'm in the boat with Paul, as my kneejerk reaction was "enable portfast". >However, if you've done that, then you can start to analyse the problem from >ground up (or Layer 1 up =) . Since you *can* ping this thing eventually, I >think we could safely rule out a physical wiring problem or the like. So >next, I would console (or telnet) into the switch and watch the that >specific port (in the 1900 series it's under the Port Addressing menu). >Then, plug the PC in and keep watching the port addressing for that port and >see how long/when the switch learns the MAC for the PC. If it learns the >MAC instantly (which it should), then I don't see where the switch is >causing the problem. As long as switch sees the MAC addr. Also, assuming >your switch and the PC are in the same IP subnet, I would try pinging the PC >from the switch directly instead of from another PC. > >Hope this helps some.... let me know how it goes...... interesting problem. > >Mike W. ________________________ Priscilla Oppenheimer http://www.priscilla.com Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=24685&t=24648 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
