mcdonald@aedc-vax.af.mil (05/24/91)
We have been getting several messages like the following logged to our console each day: May 20 10:36:25 ccfiris grcond[21429]: CIO: t0: transmit: no carrier May 20 10:36:25 ccfiris grcond[21429]: CIO: et0: transmit: no carrier May 20 10:36:25 ccfiris last message repeated 8 times Has anyone else seen this before? Is it something that we need to call TAC about & possibly get something corrected by field service? Thanks. vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv | Kenneth M. McDonald * OAO Corp * Arnold Engineering Development Center | | MS 120 * Arnold AFS, TN 37389-9998 * (615) 454-3413 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ INTERNET: mcdonald@aedc-vax.af.mil LOCAL: c60244@ccfiris
vjs@rhyolite.wpd.sgi.com (Vernon Schryver) (05/25/91)
"no carrier" usually means the ethernet cable is not connected or loose. "late collision" means a long packet suffered a collision after the 1st 64 bytes, which in turn means that your ethernet is mis-configured. A late collision means the distance between distant parts of the network is more than 64-byte times. The most common error is using excessively long drop cables. With at least some twisted pair transceivers, you're limited to 10 or 20 feet. It is also easy to break thick net by using three or more 75 meter drop cables. Vernon Schryver, vjs@sgi.com