I've been having a weird situation occur sporadically. The monitors at my office will show customers as unpingable.
When they are not pingable, we tracert it to see the point of failure. The issue usually shows in the next hop outside my T1 provider. Usually by the time I can check it the issue has resolved itself. My T1 provider says there are no issues. Tonight I caught the issue as it happened. I could not ping certain customers from my office, but I was able to ping them from my home via charter cable. After working with the T1 provider, it looks like it was my leaf box! (??) While telnet'd into the T1 router (adtran), the T1 tech could ping the ip's in question. After I booted the firewall, I was able to get to them as well. I checked dmesg, shorewall.log and messages. I saw nothing that stuck out. I tried an arp -a. It took approximately 45 seconds to respond with the info for the T1 router on eth0. So...if I catch this again, what should I check next? ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ------------------------------------------------------------------------ leaf-user mailing list: [email protected] https://lists.sourceforge.net/lists/listinfo/leaf-user Support Request -- http://leaf-project.org/
