[1905] in Moira
host IP assigned out of range
daemon@ATHENA.MIT.EDU (Angie Kelic)
Mon Dec 10 12:17:21 2001
Message-Id: <200112101717.MAA27011@prowler.mit.edu>
To: network@MIT.EDU
cc: bug-moira@MIT.EDU
Date: Mon, 10 Dec 2001 12:17:18 -0500
From: Angie Kelic <sly@MIT.EDU>
When I was doing the deletion of Tang hostnames I ran
across the following:
prowler:/mit/rescomp/internal/Tang % stella 'oakland-lake' -ac "owner presumed no longer in Tang" -S 3
/usr/athena/bin/stella: Bad address while updating host.
prowler:/mit/rescomp/internal/sshd % stella oakland-lake
Machine: OAKLAND-LAKE.MIT.EDU
Address: 18.251.4.250 Network: W84
Owner: USER chenghan Use data: 02-feb-2001 10:32:13
Status: Active (1) Changed: 02-feb-2001 10:32:13
Vendor: IBM Location: W84
Model: PC Contact: Cheng-Han Chen
OS: WINDOWS Billing Contact:
Opt: 0 Account Number:
Adm cmt:
Op cmt:
Created by sean_lie on 02-feb-2001 10:32:13
Last mod by sean_lie at 02-feb-2001 10:32:13 with moira.
Now looking up Tang's network listing, the IP address is clearly
out of range:
Get network information
Network's Name: w84
Network: W84
Description: Building W84
Status: Resnet (5)
Contact:
Account Number:
Address: 18.251.0.0 Mask: 255.255.0.0
High: 18.251.4.249 Low: 18.251.0.27
I have no idea how this could have happened unless moira
somehow calculated the address space incorrectly when told
to assign a unique IP address or if the network numbers changed
at some point.
I've fixed the problem by assigning the machine another IP
address and then deleting it, but I thought I'd let people
know in case there's a bug somewhere.
--Angie
******************************************************
The goal of engineering is to build better mousetraps.
The goal of nature is to build better mice.
******************************************************
