Opened 5 years ago

#1031 new incident

HybridLivinglab niet bereikbaar

Reported by: ed Owned by:
Keywords: Cc:
Location: Leiden

Description

Host Status:	
  DOWN  
 (for 0d 0h 11m 51s)
Status Information:	CRITICAL - Host Unreachable (172.20.140.1)
Performance Data:	
Current Attempt:	1/10  (HARD state)
Last Check Time:	09-06-2015 16:49:27
Check Type:	ACTIVE
Check Latency / Duration:	0.850 / 0.030 seconds
Next Scheduled Active Check:  	09-06-2015 16:54:37
Last State Change:	09-06-2015 16:38:07
Last Notification:	N/A (notification 0)
Is This Host Flapping?	
  YES  
 (22.37% state change)
In Scheduled Downtime?	
  NO  
Last Update:	09-06-2015 16:49:57  ( 0d 0h 0m 1s ago)

Node is niet meer bereikbaar.

HybridHaagwijk# ping 172.16.17.113
PING 172.16.17.113 (172.16.17.113): 56 data bytes
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down
^C
--- 172.16.17.113 ping statistics ---
8 packets transmitted, 0 packets received, 100.0% packet loss

Het nanostation bij LivingLab? is nog wel te bereiken.

HybridHaagwijk# ping 172.16.17.114
PING 172.16.17.114 (172.16.17.114): 56 data bytes
64 bytes from 172.16.17.114: icmp_seq=0 ttl=64 time=2.183 ms
64 bytes from 172.16.17.114: icmp_seq=1 ttl=64 time=2.175 ms
64 bytes from 172.16.17.114: icmp_seq=2 ttl=64 time=2.020 ms
64 bytes from 172.16.17.114: icmp_seq=3 ttl=64 time=2.103 ms
64 bytes from 172.16.17.114: icmp_seq=4 ttl=64 time=2.095 ms
^C
--- 172.16.17.114 ping statistics ---
5 packets transmitted, 5 packets received, 0.0% packet loss

Node heeft een reboot op locatie nodig, dan gelijk even meekijken op de serieele port
of er vreemde foutmeldingen te zien zijn.

Change History (0)

Note: See TracTickets for help on using tickets.