CRC chyby na portu switche ?

[Helium]

CRC chyby na portu switche ?

Na jednom portu switche mi jeho diagnostika hlasi CRC chyby,
co se muze dit s takovym srovna prenasenym macframem ?
Je ztracen, poskozen nebo je na teto nizke urovni nejeke
znovuzaslani ?

[tomaash]

Copypaste z helpu nemenovaneho switcha

Excessive CRC/alignment errors
---------------------------------
Description: A high percentage of data errors was detected on this port.
Possible causes: Faulty cabling or topology, half/full duplex mismatch,
a misconfigured NIC, or a malfunctioning NIC, NIC driver, or transceiver.
Actions:
1. If this port is 100Base-T, make sure the cable, connectors, punch-down
blocks, and patch panels connecting to the port are Category 5 or
better. Verify the correctness of the installation using a Category
5 test device.
2. Check the directly-connected device for mismatches in half/full
duplex operation (half duplex on the switch and full duplex on the
connected device, or the reverse).
3. Update the NIC driver software.
4. Verify that the network topology conforms to IEEE 802.3 standards.
5. Replace or relocate the cable. Also check the wiring closet components,
transceivers, and NICs for proper operation.

Kazdopadne, zalezi na tom, kolko CRC errorov na tom porte je, aby sa to seriozne prejavilo aj na performance.

[Helium]

Copypaste z helpu nemenovaneho switcha

Excessive CRC/alignment errors
---------------------------------
Description: A high percentage of data errors was detected on this port.
Possible causes: Faulty cabling or topology, half/full duplex mismatch,
a misconfigured NIC, or a malfunctioning NIC, NIC driver, or transceiver.
Actions:
1. If this port is 100Base-T, make sure the cable, connectors, punch-down
blocks, and patch panels connecting to the port are Category 5 or
better. Verify the correctness of the installation using a Category
5 test device.
2. Check the directly-connected device for mismatches in half/full
duplex operation (half duplex on the switch and full duplex on the
connected device, or the reverse).
3. Update the NIC driver software.
4. Verify that the network topology conforms to IEEE 802.3 standards.
5. Replace or relocate the cable. Also check the wiring closet components,
transceivers, and NICs for proper operation.

Kazdopadne, zalezi na tom, kolko CRC errorov na tom porte je, aby sa to seriozne prejavilo aj na performance.

Coz o to, ze tam byl vibracema uvolnenej vnitrek konektoru, to jo,
ale mohli se tam ztracet data (propojeni mezi switchema),
pri 3-5 CRC chybach za vterinu ??

[Fox!MURDER]

Copypaste z helpu nemenovaneho switcha

Excessive CRC/alignment errors
---------------------------------
Description: A high percentage of data errors was detected on this port.
Possible causes: Faulty cabling or topology, half/full duplex mismatch,
a misconfigured NIC, or a malfunctioning NIC, NIC driver, or transceiver.
Actions:
1. If this port is 100Base-T, make sure the cable, connectors, punch-down
blocks, and patch panels connecting to the port are Category 5 or
better. Verify the correctness of the installation using a Category
5 test device.
2. Check the directly-connected device for mismatches in half/full
duplex operation (half duplex on the switch and full duplex on the
connected device, or the reverse).
3. Update the NIC driver software.
4. Verify that the network topology conforms to IEEE 802.3 standards.
5. Replace or relocate the cable. Also check the wiring closet components,
transceivers, and NICs for proper operation.

Kazdopadne, zalezi na tom, kolko CRC errorov na tom porte je, aby sa to seriozne prejavilo aj na performance.

Coz o to, ze tam byl vibracema uvolnenej vnitrek konektoru, to jo,
ale mohli se tam ztracet data (propojeni mezi switchema),
pri 3-5 CRC chybach za vterinu ??

crc umi jednu chybu snad i opravit. vic chyb jen odhalit.
rozhodne bych nepocital s tim ze by se neztracely. ale kdyz ti to fungovalo tak to ani neres

[Helium]

Copypaste z helpu nemenovaneho switcha

Excessive CRC/alignment errors
---------------------------------
Description: A high percentage of data errors was detected on this port.
Possible causes: Faulty cabling or topology, half/full duplex mismatch,
a misconfigured NIC, or a malfunctioning NIC, NIC driver, or transceiver.
Actions:
1. If this port is 100Base-T, make sure the cable, connectors, punch-down
blocks, and patch panels connecting to the port are Category 5 or
better. Verify the correctness of the installation using a Category
5 test device.
2. Check the directly-connected device for mismatches in half/full
duplex operation (half duplex on the switch and full duplex on the
connected device, or the reverse).
3. Update the NIC driver software.
4. Verify that the network topology conforms to IEEE 802.3 standards.
5. Replace or relocate the cable. Also check the wiring closet components,
transceivers, and NICs for proper operation.

Kazdopadne, zalezi na tom, kolko CRC errorov na tom porte je, aby sa to seriozne prejavilo aj na performance.

Coz o to, ze tam byl vibracema uvolnenej vnitrek konektoru, to jo,
ale mohli se tam ztracet data (propojeni mezi switchema),
pri 3-5 CRC chybach za vterinu ??

crc umi jednu chybu snad i opravit. vic chyb jen odhalit.
rozhodne bych nepocital s tim ze by se neztracely. ale kdyz ti to fungovalo tak to ani neres

Muzes byt presnejsi, pri tech CRC se data ztracely nebo neztracely ?

[Fox!MURDER]

Copypaste z helpu nemenovaneho switcha

Excessive CRC/alignment errors
---------------------------------
Description: A high percentage of data errors was detected on this port.
Possible causes: Faulty cabling or topology, half/full duplex mismatch,
a misconfigured NIC, or a malfunctioning NIC, NIC driver, or transceiver.
Actions:
1. If this port is 100Base-T, make sure the cable, connectors, punch-down
blocks, and patch panels connecting to the port are Category 5 or
better. Verify the correctness of the installation using a Category
5 test device.
2. Check the directly-connected device for mismatches in half/full
duplex operation (half duplex on the switch and full duplex on the
connected device, or the reverse).
3. Update the NIC driver software.
4. Verify that the network topology conforms to IEEE 802.3 standards.
5. Replace or relocate the cable. Also check the wiring closet components,
transceivers, and NICs for proper operation.

Kazdopadne, zalezi na tom, kolko CRC errorov na tom porte je, aby sa to seriozne prejavilo aj na performance.

Coz o to, ze tam byl vibracema uvolnenej vnitrek konektoru, to jo,
ale mohli se tam ztracet data (propojeni mezi switchema),
pri 3-5 CRC chybach za vterinu ??

crc umi jednu chybu snad i opravit. vic chyb jen odhalit.
rozhodne bych nepocital s tim ze by se neztracely. ale kdyz ti to fungovalo tak to ani neres

Muzes byt presnejsi, pri tech CRC se data ztracely nebo neztracely ?

mno data se neztratej. data se poskodej. a kdyz prijdou poskozeny data tak ti je kazdej normalni protokol opravi (jde-li to) nebo zahodi. resp. pokud ty CRC chyby detekoval switch tak to asi zahazoval on
a pokud nepouzivas primitivni protokoly typu syslog tak by te ztraceny pakety nemely trapit ... TCP je posila znovu samo, UDP si vetsinou hlida 7ma vrstva...

[Helium]

Dik.