[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference netcad::hub_mgnt

Title:DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:NETCAD::COLELLADT
Created:Wed Nov 13 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:4455
Total number of notes:16761

3235.0. "Repeater 900TM,strange problem" by IAMOSI::LEUNG (Dennis Leung, Sydney CSC) Mon Feb 05 1996 03:48

2 Hub900 (HW=F,RO=V1.1.6,SW=V4.0.2)
2 Repeater 900TM (V1.1.0), one each hub, say named A & B
No IP address is set on the individual modules in each hub except for the Hub900
itself.


Customer reports the following problem :
Both repeater have acquired the IP address of another host in the network
(20.10.10.8). Customer use the "show current settings" option in the Repeater
900TM menu and it shows that an IP address (20.10.10.8) has been set. That
happens on both repeater900TMs. Customer mantains that no person would set that
address manually or through SNMP (if that is possible?).
That address is used by an HP laserjet printer. When the problem occurs,
printing to the printer fails.

Customer went to one of the hubs and removed the IP address (20.10.10.8) from
the repeater 900tm A. Then, "show current settings" displays that the address
has been removed and that it is using the hub900's ip address.
Without changing anything on the other repeater 900tm B, "show current settings"
now displays that no IP address has been set on it and it is using hub900 ip
address!!! However, when customer tries to ping to that ip address and check the
arp entry, he found that repeater 900tm B was still responding by checking the
arp table entry and finding the 900tm B's mac address.

Rebooting the Repeater900TM solves the problem.
Nothing in the error logs for hub and repeater.

Anyone seen this before?
Thanks
Dennis
T.RTitleUserPersonal
Name
DateLines
3235.1Bad BOOTP Server?NETCAD::GALLAGHERMon Feb 05 1996 12:0532
I don't know the answer, but may be able to give some clues.

DECrepeater900TMs (like all 900-series repeaters) will attempt to get an
IP address using the BOOTP (Bootstrap Protocol).  They broadcast BOOTP
requests.  User's can configure BOOTP servers to respond to the request
with an IP address.  The BOOTP servers are configured with MAC address/
IP address binding so, for example, when repeater 08-00-2b-42-42-42 sends
a BOOTP request to server gives it IP address 1.2.3.4.

So it seems your customer's repeaters are aquiring IP addresses via BOOTP.
Perhaps there's misconfigured BOOTP server on the network?

I think the latest versions of firmware allow you to disable BOOTP on
the repeaters.  (I'll check.)

>Rebooting the Repeater900TM solves the problem.

BOOTP requests are sent after 1 second, then two seconds later, then
4 seconds, 8, 16....up to 512 seconds.  I don't know how rebooting would
solve the problem.

>                        Customer maintains that no person would set that
>address manually or through SNMP (if that is possible?).

No, it's not possible.  The only way to set an IP address is thru the
setup port or via BOOTP. 

>Anyone seen this before?

Never heard of this one.
						-Shawn

3235.2NETCAD::GALLAGHERWed Feb 07 1996 12:198
>I think the latest versions of firmware allow you to disable BOOTP on
>the repeaters.  (I'll check.)

Yes, you can disable the device sending BOOTP request thru the set-up port.

This is a curious problem.  Any progress?

						-Shawn
3235.3more info....IAMOSI::LEUNGDennis Leung, Sydney CSCThu Feb 08 1996 02:329
Re : .2

There is a UNIX bootp server on the network but customer maintains that there is
not booptab entries for these repeaters in the booptab file.
Anyway, customer has not seen it happen again and we'll take it as a once-off
occurrence. Will monitor and see if it re-occurs.

Thanks
Dennis