Opened 9 years ago

Closed 9 years ago

#1030 closed incident (fixed)

HybridZTWMeerburgkerk ue0 foute ipconfiguratie

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

Description

De interface ue0 is active en kennelijk verbonden met de nanostation die oorspronkelijk op ue2 zat:

HybridZTWMeerburgkerk# /tools/find-nanostation ue0
tcpdump: listening on ue0, link-type EN10MB (Ethernet), capture size 1500 bytes
20:28:10.522523 CDPv1, ttl: 120s, checksum: 376 (unverified), length 76
	Device-ID (0x01), length: 11 bytes: 'MBKERK-OOST'
	Address (0x02), length: 13 bytes: IPv4 (1) 172.16.7.211
	Capability (0x04), length: 4 bytes: (0x00000002): Transparent Bridge
	Version String (0x05), length: 9 bytes: 
	  XM.v5.5.8
20:28:13.591030 CDPv1, ttl: 120s, checksum: 376 (unverified), length 78
	Device-ID (0x01), length: 13 bytes: 'HNK-NOORDWEST'
	Address (0x02), length: 13 bytes: IPv4 (1) 172.16.7.210
	Capability (0x04), length: 4 bytes: (0x00000002): Transparent Bridge
	Version String (0x05), length: 9 bytes: 
	  XM.v5.5.8

Change History (1)

comment:1 by huub, 9 years ago

Resolution: → fixed
Status: new → closed

De ue0 config aangepast (link naar Heineken) en ue1 uit de config gehaald. Op ue1 zit een nano met ip-adres 172.17.116.2, maar slechte verbinding met de node met packetloss.

Note: See TracTickets for help on using tickets.