[j-nsp] Strange xntpd log messages

[Josef Buchsteiner]

Thursday, June 23, 2005, 3:39:25 PM, you wrote:

   
   
TS> I have 4 m10is, all configured essentially identically.

    I believe they are not identically. Look at the configuration of
    your syslog level. You must have logging enabled for debugging.
    like "any any" ?

    in version 6.4R1 7.0R1  and higher we have moved those messages
    into debug_level whereas before it was info_evel before.

    please confirm
    Josef

TS>   All have legal
TS>  public addresses on the loopback interface.  Only one gives out this
TS>  message. I'll be happy to hear any resolution to this issue.
 
TS>  -----Original Message-----
TS>  From: juniper-nsp-bounces at puck.nether.net
TS>  [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Jee Kay
TS>  Sent: Thursday, June 23, 2005 8:20 AM
TS>  To: Harry Reynolds
TS>  Cc: juniper-nsp at puck.nether.net
TS>  Subject: Re: [j-nsp] Strange xntpd log messages
 
 
TS>  On 6/23/05, Harry Reynolds <harry at juniper.net> wrote:
 >> You might try adding a non-martian address to the loopback interface.
 >> Xntpd should bind to that IP and stop logging errors. I expect you may
 >> have to restart routing (or at minimum the xntpd) for the change to
TS>  take
 >> effect.
 
TS>  The loopback is in publically routable address space. There are no
TS>  martians in any part of the configuration. (The router has been
TS>  through a full reboot since the addition of the Lo interface)
 
TS>  _______________________________________________
TS>  juniper-nsp mailing list juniper-nsp at puck.nether.net
TS>  http://puck.nether.net/mailman/listinfo/juniper-nsp
 
TS>  _______________________________________________
TS>  juniper-nsp mailing list juniper-nsp at puck.nether.net
TS>  http://puck.nether.net/mailman/listinfo/juniper-nsp