Operating System - HP-UX
1837835 Members
2445 Online
110121 Solutions
New Discussion

Bootpd / JetDirect errors

 
SOLVED
Go to solution
Ron Bombard
Frequent Advisor

Bootpd / JetDirect errors

When ever I reset specific jetdirect devices, I get the following error in the syslog.log file:

Bootpd[8040]: client 192.168.100.44 requested unknown/unservable option.tag=33

This line will be repeated many times, with three different option.tag numbers: 33, 36, & 90.

My bootptab entries look like this:

jetd_IT: :ht=ether: :ha=0060b0b9c417: :hn: :ip=192.168.100.45: :vm=rfc1048:

Every entry is the same except for the lable, ha, & ip tags (obviously).

I've been having problems recently with jetdirect printers being disabled and the only way to print to them is to reset the jetdirect. But I don't think this problem is related because #1 its a recent problem, and #2 I see these bootpd errors in the syslog file going back to the begining of the file (august).

Any insight as to what these errors are, and how to fix them would be greatly appreciated.

Thanks!
Ro
Meddle not in the affairs of dragons... for you are crunchy and taste like chicken.
5 REPLIES 5
Sanjay_6
Honored Contributor
Solution

Re: Bootpd / JetDirect errors

Hi ron,

Probably your jetdirect printer is sending info to the syslkog file. Look under the printer configuration on the printer and see if the syslog server is defined as this server of yours where the messaged are logged.

Do a telnet to the printer and then press "/". this will bring up the network configuration for the printer. See if syslog server is defined. If you remove the syslog server entry from the printer, it will stop sending these alerts to your server.

Hope this helps.

regds
Mark Greene_1
Honored Contributor

Re: Bootpd / JetDirect errors

What HP-UX are you running? The man page for bootpd on my 11.0 server shows option tag 33 for static routes, but 36 and 90 are not in the list. Check your man page for a list of option tags that are recognized; there is also much discussion there on tags.

You can also try bootpquery on the ip addresses in question. Man bootpquery for info on syntax and flags; be aware it does not appear to be trivial.

HTH
mark
the future will be a lot like now, only later
Steven Gillard_2
Honored Contributor

Re: Bootpd / JetDirect errors

You're right, these bootpd errors in syslog aren't related. They're just informational messages bootpd gives when it doesn't understand an option supplied in a request packet. In fact i think if you install the latest bootpd/DHCP server patch (PHNE_19241 on HPUX 11) these messages will stop appearing.

Did you recently upgrade your jetdirect software? I've seen other forum posts that talk about problems with the new version on HPUX.

Regards,
Steve
Ron Bombard
Frequent Advisor

Re: Bootpd / JetDirect errors

Thanks Guys!

Sanjey: The syslog entry WAS blank. I added a server entry and got even more worthless syslog entries.... Gonna just ignore 'em.

Mark: I'm using 10.20. The man page for bootpd dosn't show entries for 36 or 90 either....

Steve: I haven't upgraded bootpd/dhcp OR jetdirect in quite some time... I'll do that later today.

Thanks for all suggestions. Dosn't seem too critical. Thanks again.
Meddle not in the affairs of dragons... for you are crunchy and taste like chicken.
Mark Greene_1
Honored Contributor

Re: Bootpd / JetDirect errors

Ron,
sounds like the patch is what you need. I am using my 10.20 as a syslogd for some problem printers, and I get messages like this from jetdirect:

Feb 18 10:55:17 ats8000.crhc.org printer: offline or intervention needed
Feb 18 10:55:17 ats8000.crhc.org printer: paper out
Feb 18 10:55:39 ats8000.crhc.org printer: error cleared
Feb 18 10:55:50 ats8000.crhc.org printer: offline or intervention needed
Feb 18 10:55:50 ats8000.crhc.org printer: paper out
Feb 18 10:55:57 ats8000.crhc.org printer: error cleared
Feb 18 10:56:08 ats8000.crhc.org printer: offline or intervention needed
Feb 18 10:56:08 ats8000.crhc.org printer: paper out
Feb 18 10:56:09 ats8000.crhc.org printer: error cleared

99% of the time I can ignore them, as they are regular operational stuff. It's that 1% of the time where the messages help diagnosing whether I've got a network or a printer issue.

HTH
mark
the future will be a lot like now, only later