It was (is) the circuit. Regional problem w/ carrier. ________________________________
From: Ziots, Edward [mailto:[email protected]] Sent: Thursday, October 29, 2009 2:42 PM To: NT System Admin Issues Subject: RE: Cisco sho int (reliabilty) Input errors are not good, maybe port issue or cabling issue. Also the aborts are not a good sign either. Z Edward Ziots Network Engineer Lifespan Organization MCSE,MCSA,MCP+I, ME, CCA, Security +, Network + [email protected] Phone:401-639-3505 ________________________________ From: David Mazzaccaro [mailto:[email protected]] Sent: Thursday, October 29, 2009 12:17 PM To: NT System Admin Issues Subject: RE: Cisco sho int (reliabilty) I just cleared the counters, and now see: Received 135 broadcasts, 0 runts, 0 giants, 0 throttles 258862 input errors, 172196 CRC, 86489 frame, 0 overrun, 0 ignored, 177 abort 38629 packets output, 3695862 bytes, 0 underruns Not a cisco expert here, but can this tell if the problem points to the carrier or my equipment? ________________________________ From: David Mazzaccaro [mailto:[email protected]] Sent: Thursday, October 29, 2009 12:12 PM To: NT System Admin Issues Subject: Cisco sho int (reliabilty) When I do a "sho int serial0", I get this: reliability 138/255, txload 2/255, rxload 1/255 I assume the reliability should always be 255/255, unless there is a problem? Users are can't get into any applications over this circuit. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
