Hi,
I have 2 sets of 2-host Clusters on site with a similar setup off-site,
linked by an FDDI ring. All boxes are 4xEV5/533 1Gb RAM AS4100 4.0D/pk3
ASE1.5 Production Server, using DMQ3.2B.
Each box has memory channel card = 10.?.?.?, FDDI = 123.69.93.?, Eth1 =
123.69.94.?, Eth2 = 123.69.94.?
This part of the network is separated from the site network by a firewall,
and from the outside world by 2 more. It has it's own DNS, and there are
various VMS (VAX & Alpha), Tandems, and some NT x86.
One of the on site servers & one off-site server is running joind to
facilitate 6 "thin-client" NCD boxes to connect via bootp.
My questions:
Any ideas on an alternative? I am concerned that a lot of traffic is being
generated for little reason (There is no other reason for using joind, DHCP
is not being used).
Any ideas what might be causing this 16-field MAC address (see below) or
what it might relate to? There are zillions of these entries in this log
file. (The log files had grown to over 500Mb in one case).
Can I use bootp instead of joind?
Messages are ALSO being written to /nsr/logs/messages but Networker is not
being used (it's installed, but not licensed so I intend to de-install it).
/var/join/log on FRED:
received on address 123.69.94.127
BOOTP/DHCP packet with "chaddr"
52:41:53:20:70:73:be:ab:79:95:bf:01:01:00:00:00 and htype 1 has hlen field
of 16 which isn't the expected value of 6 : packet discarded
/var/join/log on BARNEY:
received on address 123.69.94.63
BOOTP/DHCP packet with "chaddr"
52:41:53:20:70:07:06:fd:f3:93:bf:01:01:00:00:00 and htype 1 has hlen field
of 16 which isn't the expected value of 6 : packet discarded
BARNEY# cat /etc/bootptab
#
# /etc/bootptab: database for bootp server (/etc/bootpd)
# Blank lines and lines beginning with '#' are ignored.
#
# Legend:
#
# first field -- hostname
# (may be full domain name and probably should be)
#
# hd -- home directory
# bf -- bootfile
# cs -- cookie servers
# ds -- domain name servers
# gw -- gateways
# ha -- hardware address
# ht -- hardware type
# im -- impress servers
# ip -- host IP address
# lg -- log servers
# lp -- LPR servers
# ns -- IEN-116 name servers
# rl -- resource location protocol servers
# sm -- subnet mask
# tc -- template host (points to similar host entry)
# to -- time offset (seconds)
# ts -- time servers
#
# Be careful about including backslashes where they're needed. Weird (bad)
# things can happen when a backslash is omitted where one is intended.
#
# First, we define a global entry which specifies the stuff every host uses.
global.template:\
:sm=255.255.255.0:\
:td=/tftpboot:\
:hd=/tftpboot:\
:ds=123.69.94.131:\
:to=18000:\
:ht=ethernet:
# Individual entries (could also have different servers for some/all of
these)
xterm1:\
:tc=global.template:\
:ha=0000a7027961:\
:bf=Xncdxpl:\
:ip=123.69.93.1:
xterm2:\
:tc=global.template:\
:ha=0000a702f3da:\
:bf=Xncdxpl:\
:ip=123.69.93.2:
xterm3:\
:tc=global.template:\
:ha=0000a702f418:\
:bf=Xncdxpl:\
:ip=123.69.93.3:
xterm4:\
:tc=global.template:\
:ha=0000a70421ff:\
:bf=Xncdxpl:\
:ip=123.69.93.4:
xterm5:\
:tc=global.template:\
:ha=0000a70421ed:\
:bf=Xncdxpl:\
:ip=123.69.93.5:
xterm6:\
:tc=global.template:\
:ha=0000a7042f49:\
:bf=Xncdxpl:\
:ip=123.69.93.6:
xterm7:\
:tc=global.template:\
:ha=0000a70421e4:\
:bf=Xncdxpl:\
:ip=123.69.93.7:
xterm8:\
:tc=global.template:\
:ha=0000a702f43a:\
:bf=Xncdxpl:\
:ip=123.69.93.8
/etc/inetd.conf:
bootps dgram udp wait root /usr/sbin/joind joind -d4
I guess if I take out the -d4 that this will reduce the debugging and hence
the messages, but this won't resolve the cause.
If you've read this far, you may have some idea of what's going on (!),
so...what I have tried so far -
I couldn't see any reason for have the "ds" entry in the global.template in
bootptab - quite the reverse in fact, as the only boxes using BOOTP are the
aforementioned NCD boxes, which all have an entry with their MAC address. So
I commented it out, and did a kill -1 on joind, but this didn't make any
difference. Should I do a kill -1 on inetd to stop joind & restart it?
Also of note - all the NCD boxes are on the same subnet as the server FDDI -
123.69.93, but the messages are coming from a 123.69.94.? address. What is
also interesting is that the addresses in the log file 123.69.94.63/127 are
according to the network people, "BROADCAST" addresses. Can I restrict bootp
to look at one NIC (123.69.93.?) only?
Any suggestions greatly appreciated, but I won't hold my breath!!!
TIF & Rgds,
Tony.
Tony McElhill.
Unix Systems Manager.
ISMA,
7 Limeharbour,
London E14 9NQ.
Tel : +44 (0)20 7510 2617.
Fax: +44 (0)20 7538 1368.
This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by return e-mail to the originator and then delete this message from your system. Please do not copy it or use it for any purpose, or disclose its contents to any other person: to do so could be a breach of confidence.
Received on Thu May 10 2001 - 15:35:16 NZST