[j-nsp] NTP Sources placement in MPLS network

[Jared Mauch]

In this case you can sync to any other device or devices that are globally reachable.  Typically you can just use some IP that doesn’t often change, e.g.: loopback.  If you are running 100% of the network, you can also use the ‘ntp broadcast’ and similar interface commands to listen/send this data hop-by-hop.

There’s lots of ways to do this, and not necessarily a ‘wrong’ way.

- Jared

On Nov 18, 2013, at 5:54 PM, Yham <yhameed81 at gmail.com> wrote:

> Thank Jared,
> 
> NTP is only needed to synchronize the logs so on event of failure, logs from related devices can be correlated.
> 
> Thanks
> 
> 
> 
> On Mon, Nov 18, 2013 at 2:52 PM, Jared Mauch <jared at puck.nether.net> wrote:
> This all depends on what you need the clocking for.
> 
> If you want just generic time for accurate logs?
> 
> Depending on what you want to do, there's cheap NTP clocks like this:
> 
> http://www.netburnerstore.com/product_p/pk70ex-ntp.htm
> 
> For about $350 (including S/H in the US) you get a GPS clock.  With the right location/antenna you can get signal through some roofs.
> 
> There's a variety of higher-end timing options depending on what you need.
> 
> - Jared
> 
> On Nov 18, 2013, at 2:33 PM, Yham <yhameed81 at gmail.com> wrote:
> 
>> Hi Guys,
>> 
>> 
>> In a SP environment where there are hundreds of PEs and P devices that got
>> hundreds of customers VRFs, what is the best place to connect NTP sources.
>> The place i can think of is connecting with VPNv4 Route Reflectors because
>> they exist on top of hierarchy and so clock can travel downward from RR to
>> PEs and P and from PEs to CEs and further down if required.
>> 
>> Any thoughts on this please.
>> 
>> Regards
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 
>