Glossary · Network and IT fundamentals
CRC errors
Frames received with a bad checksum, usually a sign of a failing cable, optic or port rather than a configuration problem.
In REAP
In REAP’s troubleshooting moment, input and CRC errors on the interface are checked before protocol settings, because a physical fault drops hello packets too.
Related terms
More in network and IT fundamentals
- ACL (access control list)
- Active/standby (high availability pair)
- API (application programming interface)
- Availability zone (AZ)
- BGP (Border Gateway Protocol)
- Change window and maintenance window
- CLI (command-line interface)
- Cloud controller
- Cloud network constructs
- CMDB (configuration management database)
- DHCP and DHCP relay
- DNS
- ERP and MES
- Escalation
- EVPN and VXLAN (overlay fabrics)
- Firewall
- Firmware and software upgrade
- Flow records (NetFlow, IPFIX)
- HSRP and VRRP (first-hop redundancy)
- Hybrid cloud
- Interface counters
- ITSM
- Kubernetes
- Leaf-spine fabric
- LLDP and CDP (neighbor discovery)
- Method of procedure (MOP)
- MLAG and MC-LAG (multi-chassis link aggregation)
- Monitoring and NMS
- MTU (maximum transmission unit)
- NAT (network address translation)
- Network operating system (NOS)
- NOC (network operations center)
- NTP (network time)
- Object group
- On-call
- Operational technology (OT)
- OSPF (Open Shortest Path First)
- Outage and degradation
- Path trace
- Port-channel (link aggregation, LACP)
- Postmortem
- Pre-check and post-check
- Priority and severity (P1 to P4)
- QoS (quality of service)
- Reachability probe
- RPO and RTO
- Running and startup configuration
- SD-WAN
- Security advisory (PSIRT)
- SNMP
- Spanning tree (STP)
- SSH
- Standard operating procedure (SOP)
- Streaming telemetry
- Syslog
- Vendor TAC case
- VLAN (virtual LAN)
- VPN
- VTY lines
Bring us your last P1.
Keep the root cause to yourself; in a 30-minute session we walk through how REAP would have investigated it, evidence first. The replay on your own network happens inside the proof of value.