Then we noticed that one of our servers was reporting an IP conflict
with a certain ethernet address. Sure enough, it was the PM2 that
we had removed from the network. We hooked a console up to it and
it showed no abnormal settings, it certainly wasn't in conflict
with any other IP numbers on our network. It's been running fine
for months and there were no recent changes made to it. Yet every time
we put it on the ethernet it starts killing all the PM2's and various
servers report duplicate IP numbers originating from this device.
This happened once before, exactly the same way, except with a different
PM2. At that time we had just upgraded it to the latest ComOS and
rebooted it - wham, same thing as described above.
When this happens it doesn't affect any of the PM3's on the same network,
nor does it seem to affect any other devices (except for the console
messages on the UNIX boxes about duplicate IP's).
Does this ring any bells for anyone? Any idea what's going on? Could
the ethernet port on these two units have gone south?
It's quickly becoming a moot point as we are almost finished replacing
all PM2's with PM3's, but I'm still curious...
Mark
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.