Opened 6 years ago

Closed 6 years ago

#780 closed incident (fixed)

HybridZTWRijneke frekwente reboots: voedingsadapter vervangen

Reported by: huub Owned by:
Keywords: Zoeterwoude Cc:
Location: Generiek

Description

Het valt me op dat Rijneke vaak reboot. Ik zie heel korte 'up' tijden daar. Zal de configuratie eens actualiseren.

Change History (8)

comment:1 Changed 6 years ago by ed

Misschien te maken met onderstaande

arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
arp: 00:0d:b9:29:4e:61 is using my IP address 172.16.3.233 on vr2!
HybridZTWRijneke# 

comment:2 Changed 6 years ago by ed

HybridStjan? heeft hetzelfde ipnummer

vr1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
	ether 00:0d:b9:29:4e:61
	inet 172.16.3.233 netmask 0xfffffff8 broadcast 172.16.3.239
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
	media: Ethernet autoselect (100baseTX <full-duplex>)
	status: active

comment:3 Changed 6 years ago by ed

In de genesis config van HybridStjan? staat dat deze interface 172.16.3.236 moet hebben.
Dit aangepast en wl-config gestart om de gegevens te actualiseren.

comment:4 Changed 6 years ago by ed

Tevens heeft het Nanostaton aan vr2 van HybridZTWRijneke ook het zelfde ipnummer.

HybridZTWRijneke# ./find-nanostation vr2
tcpdump: listening on vr2, link-type EN10MB (Ethernet), capture size 1500 bytes
06:44:34.826866 CDPv1, ttl: 120s, checksum: 376 (unverified), length 76
	Device-ID (0x01), length: 11 bytes: 'il-zuidwest'
	Address (0x02), length: 13 bytes: IPv4 (1) 172.16.3.233
	Capability (0x04), length: 4 bytes: (0x00000002): Transparent Bridge
	Version String (0x05), length: 9 bytes: 
	  XM.v5.5.8
	Platform (0x06), length: 3 bytes: 'N5N'
	Port-ID (0x03), length: 3 bytes: 'br0'
	unknown field type (0xff), length: 1 byte: 
	  0x0000:  2e
06:45:00.990127 CDPv1, ttl: 120s, checksum: 376 (unverified), length 86
	Device-ID (0x01), length: 12 bytes: 'IL-NOORDOOST'
	Address (0x02), length: 22 bytes: IPv4 (2) 172.16.3.235 IPv4 (1) 169.254.59.245
	Capability (0x04), length: 4 bytes: (0x00000002): Transparent Bridge
	Version String (0x05), length: 9 bytes: 
	  XM.v5.5.8
	Platform (0x06), length: 3 bytes: 'N5N'
	Port-ID (0x03), length: 3 bytes: 'br0'
	unknown field type (0xff), length: 1 byte: 
	  0x0000:  2e
2 packets captured
157 packets received by filter
0 packets dropped by kernel

comment:5 Changed 6 years ago by huub

Ik heb ip-adres van de nano gecorrigeerd en ook de nagios config aangepast zodat nu de nano bij Rijneke en bij StJan? correct gecheckt worden.

comment:6 Changed 6 years ago by huub

Oorzaak is vrijwel zeker de voeding: de nano's rebooten ook. Adapter vervangen.

comment:7 Changed 6 years ago by huub

Summary: HybridZTWRijneke frekwente rebootsHybridZTWRijneke frekwente reboots: voedingsadapter vervangen

comment:8 Changed 6 years ago by huub

Resolution: fixed
Status: newclosed

Ik heb de voedingsadapter vanmiddag vervangen. De oude adapter was een beetje warm. Bij thuiskomst bleek er nog wel spanning uit te komen, maar misschien haalt hij toch het vermogen niet meer.
In ieder geval: node is nu ruim 4 uur in de lucht, houdt goede moed!

Note: See TracTickets for help on using tickets.