Nile Portal Alerts

crc error alert overview the crc error alert triggers when an interface detects corrupted data packets a cyclic redundancy check (crc) error occurs when a frame fails its integrity check, meaning data was damaged during transit alert details severity sev 2 (configurable) trigger condition triggered when any wired client link experiences crc errors after the link comes up for that client clear condition once crc stops portal will wait for another 24 hours to confirm if issue is occuring again potential impact packet loss corrupted packets are dropped, requiring retransmissions network degradation slow application performance and reduced throughput on the affected link troubleshooting steps check physical connections inspect the copper or fiber cables for physical damage or loose connections verify sfp/transceiver health check the optical power levels (dom/ddm) on fiber ports to ensure they are within operational limits isolate electromagnetic interference (emi) ensure network cables are not running too close to high voltage power lines or faulty machinery test the cable use a cable tester or swap the cable with a known working one to isolate the issue link speed/duplex mismatch alert overview the link mismatch alert triggers when two connected network devices are configured with conflicting speed or duplex settings this typically happens when one side is hardcoded and the other relies on auto negotiation alert details severity sev 2 (configurable) trigger condition triggered when the wired client link speed decreases from the original speed observed when the link came up clear condition once the link speed returns to its original speed, the portal waits for 24 hours to confirm that the issue does not recur before clearing the alert potential impact severe performance drop duplex mismatches cause massive collision rates, dropping performance to a fraction of the capacity flapping links the interface may repeatedly go up and down total disconnect a complete speed mismatch will prevent the link from establishing a connection entirely troubleshooting steps verify interface settings check the configuration on both local and remote devices standardize configuration ensure auto negotiation is enabled on both sides, or manually hardcode the exact same speed and duplex settings on both devices check capabilities confirm that both physical hardware interfaces are capable of supporting the same maximum speed