How to: Keep DHCPDISCOVER messages off the console in Solaris 11

[Richard Westerveld]

All,

   Not real familiar (yet) with the ISC DHCP server.  In the past we
used the regular old Solaris non-ISC version.  Hopefully we'll get more
familiar with this one as time goes on.

   Have it up and running - and working, from the viewpoint of what we
use it for.  We don't use it for actually assigning leases like a
traditional use (all our clients have static IP addresses); we use it
for booting already identified clients (ie ones that have entries in
/etc/inet/dhcpd4.conf).

   The problem is we get lots of those DHCPDISCOVER/no free leases
messages continually scrolling on the console for units that haven't
been identified as ones we want to net boot (there's an application that
adds their entries to the conf file when someone wants to boot them).

   I'd like some way to either turn that particular message off; or else
direct them to some other location.

   I tried setting "unknown-clients" to ignore; but that apparently
doesn't turn off the messages.  (Note:  I *think* these requests are
coming from "unknown" clients; since I haven't found their mac addresses
in the conf file.)

   I also tried setting the dhcp server to use syslog; but that doesn't
seem to keep them from appearing on the console either.

   I'm sure *someone* at some point has tried to get rid of these same
messages; so can anyone point me to the proper place to find out how to
do it?  An example might help, too.

   Thanks.

-Richard

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Rick Dicaire]

Aren't messages to console controlled by syslog? Maybe look at what syslog facilities/levels get sent to console, and what syslog facilities/levels the dhcp server is using?

On Fri, Mar 22, 2019 at 4:28 PM Richard Westerveld <[hidden email]> wrote:

All,

   Not real familiar (yet) with the ISC DHCP server.  In the past we
used the regular old Solaris non-ISC version.  Hopefully we'll get more
familiar with this one as time goes on.

   Have it up and running - and working, from the viewpoint of what we
use it for.  We don't use it for actually assigning leases like a
traditional use (all our clients have static IP addresses); we use it
for booting already identified clients (ie ones that have entries in
/etc/inet/dhcpd4.conf).

   The problem is we get lots of those DHCPDISCOVER/no free leases
messages continually scrolling on the console for units that haven't
been identified as ones we want to net boot (there's an application that
adds their entries to the conf file when someone wants to boot them).

   I'd like some way to either turn that particular message off; or else
direct them to some other location.

   I tried setting "unknown-clients" to ignore; but that apparently
doesn't turn off the messages.  (Note:  I *think* these requests are
coming from "unknown" clients; since I haven't found their mac addresses
in the conf file.)

   I also tried setting the dhcp server to use syslog; but that doesn't
seem to keep them from appearing on the console either.

   I'm sure *someone* at some point has tried to get rid of these same
messages; so can anyone point me to the proper place to find out how to
do it?  An example might help, too.

   Thanks.

-Richard

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

[Bill Shirley-2]

Console messages are controlled by the kernel.printk knob.  Try
sysctl -w "kernel.printk=3 4 1 7"

I have this in /etc/sysctl.d/99-mystuff.conf which is run after a reboot:
#define KERN_EMERG    "<0>"  /* system is unusable               */
#define KERN_ALERT    "<1>"  /* action must be taken immediately */
#define KERN_CRIT     "<2>"  /* critical conditions              */
#define KERN_ERR      "<3>"  /* error conditions                 */
#define KERN_WARNING  "<4>"  /* warning conditions               */
#define KERN_NOTICE   "<5>"  /* normal but significant condition */
#define KERN_INFO     "<6>"  /* informational                    */
#define KERN_DEBUG    "<7>"  /* debug-level messages             */
#- console_loglevel: messages with a higher priority than
#  this will be printed to the console
#- default_message_level: messages without an explicit priority
#  will be printed with this priority
#- minimum_console_loglevel: minimum (highest) value to which
#  console_loglevel can be set
#- default_console_loglevel: default value for console_loglevel

# console was too verbose
kernel.printk = 3 4 1 7

Bill

On 3/22/2019 4:27 PM, Richard Westerveld wrote:

All,

  Not real familiar (yet) with the ISC DHCP server.  In the past we used the regular old Solaris non-ISC version.  Hopefully we'll get more familiar with this one as time goes on.

  Have it up and running - and working, from the viewpoint of what we use it for.  We don't use it for actually assigning leases like a traditional use (all our clients have static IP addresses); we use it for booting already identified clients (ie ones that have entries in /etc/inet/dhcpd4.conf).

  The problem is we get lots of those DHCPDISCOVER/no free leases messages continually scrolling on the console for units that haven't been identified as ones we want to net boot (there's an application that adds their entries to the conf file when someone wants to boot them).

  I'd like some way to either turn that particular message off; or else direct them to some other location.

  I tried setting "unknown-clients" to ignore; but that apparently doesn't turn off the messages.  (Note:  I *think* these requests are coming from "unknown" clients; since I haven't found their mac addresses in the conf file.)

  I also tried setting the dhcp server to use syslog; but that doesn't seem to keep them from appearing on the console either.

  I'm sure *someone* at some point has tried to get rid of these same messages; so can anyone point me to the proper place to find out how to do it?  An example might help, too.

  Thanks.

-Richard

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users