A NIC failed recently or port down
This is a real life sample alert from indeni
Some network interfaces or ports have gone from “working” to “not working”, some network traffic may be lost.
indeni will re-check this alert every 1 minute. If indeni determines the issue has been resolved, it will automatically be flagged as such.
Affected Network Interfaces or Ports:
GigabitEthernet0/2 (MAC Address: 00:0f:34:fe:00:1a, IP Address: 10.0.10.245/30, Description: Our Connection to ACME)
Manual Remediation Steps:
For GigabitEthernet0/2(Our Connection to ACME): The following log lines may assist with troubleshooting this issue:
- Nov 12 18:30:24.704 GMT: %TRACKING-5-STATE: 2 interface Gi0/2 line-protocol Up->Down
- Nov 12 18:30:26.588 GMT: %LINK-3-UPDOWN: Interface GigabitEthernet0/2, changed state to down
- Nov 12 18:30:26.588 GMT: %ENTITY_ALARM-6-INFO: ASSERT CRITICAL Gi0/2 Physical Port Link Down
- Nov 12 18:30:27.588 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/2, changed state to down
How does this alert work?
indeni uses different commands for different devices to determine if the NICs are working correctly and the ports are up. Examples:
- On many Linux-based OS’s, indeni will use ifconfig.
- On Cisco devices indeni will use “show interface” and related commands.
In the specific case of switches, indeni will attempt to determine if it is monitoring an access switch and will avoid alerting about ports that tend to go up and down a lot. Trunk ports, for example, will still be monitored.