[j-nsp] Re: xntpd newbie ....

[Richmond, Jeff (ELI)]

Agreed. Same issue here. We have no services PICs in production and are seeing this across all Junipers that have been upgraded to 7.0R2.7

-Jeff

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net]On Behalf Of Pekka Savola
Sent: Tuesday, February 01, 2005 6:54 AM
To: Jared Mauch
Cc: juniper-nsp at puck.nether.net; Harshit Kumar
Subject: Re: [j-nsp] Re: xntpd newbie ....


On Mon, 17 Jan 2005, Jared Mauch wrote:
> On Mon, Jan 17, 2005 at 12:41:29PM -0800, Harshit Kumar wrote:
>> Those messages aren't going to harm the system in any way. 10.0.0.1
>>  is an internal address which resides in an internal routing instance
>> (__juniper_private1__). You will see it when you have certain services
>> pics installed. Its for communication between RE and the PIC only and is
>>
>> not world-reachable.
>
> 	Seems that that IP shouldn't be attempted to be bound to by
> ntp at all if it's not globally reachable.
>
> 	isn't that a bug then that your IPC ip range is being leaked?

Regarding Harshit's first comment..

FWIW, this has nothing to do with services pics.  We have none of 
those, nor routing instances of our own, and when we upgraded to 
7.0R2.7, started seeing these messages.

PR55431 despite its pretty bogus description is probably tracking this 
issue and there is no need to report it (again) ?

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp