Dynabrade Dynabug 57810, Dynabug 57812, Dynabug 57811, Dynabug 57813, Dynabug 57814 User Manual

Junos®OS

Time Management Administration Guide for Routing Devices

Release

13.3

Published: 2014-04-22

Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www.juniper.net

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

Junos®OS Time Management Administration Guide for Routing Devices

The information in this document is current as of the date on the title page.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.

END USER LICENSE AGREEMENT

The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at

http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of

that EULA.

Table of Contents

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Using the Examples in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Merging a Full Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Merging a Snippet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Part 1 Overview

Chapter 1 Time Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

NTP Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Understanding NTP Time Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Part 2 Configuration

Chapter 2 Configuring Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Setting the Date and Time Locally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Configuring NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Modifying the Default Time Zone for a Router or Switch Running Junos OS . . . . . 12

Synchronizing and Coordinating Time Distribution Using NTP . . . . . . . . . . . . . . . . 13

Configuring NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configuring the NTP Boot Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Specifying a Source Address for an NTP Server . . . . . . . . . . . . . . . . . . . . . . . . 13

Configuring the NTP Time Server and Time Services . . . . . . . . . . . . . . . . . . . . . . . 14

Configuring the Router or Switch to Operate in Client Mode . . . . . . . . . . . . . . 15

Configuring the Router or Switch to Operate in Symmetric Active Mode . . . . 15

Configuring the Router or Switch to Operate in Broadcast Mode . . . . . . . . . . 16

Configuring the Router or Switch to Operate in Server Mode . . . . . . . . . . . . . 16

Example: Configuring NTP as a Single Time Source for Router and Switch Clock

Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Configuring NTP Authentication Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configuring the Router or Switch to Listen for Broadcast Messages Using

NTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring the Router or Switch to Listen for Multicast Messages Using NTP . . . 19

Time Management Administration Guide for Routing Devices

Updating the IANA Time Zone Database on Junos Devices . . . . . . . . . . . . . . . . . . 20

Importing and Installing Time Zone Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Configuring a Custom Time Zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 3 Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

System Management Configuration Statements . . . . . . . . . . . . . . . . . . . . . . . . . . 23

authentication-key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

boot-server (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

broadcast-client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

multicast-client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

ntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

peer (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

server (NTP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

source-address (NTP, RADIUS, System Logging, or TACACS+) . . . . . . . . . . . . . . . 37

system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

time-zone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

use-imported-time-zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Part 3 Administration

Chapter 4 Operational Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

set date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Chapter 5 Monitoring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

show ntp associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

show ntp status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Part 4 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

List of Tables

About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Part 3 Administration

Chapter 5 Monitoring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Table 3: show ntp associations Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Table 4: show ntp status Output Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Time Management Administration Guide for Routing Devices

About the Documentation

•

Documentation and Release Notes on page vii

•

Supported Platforms on page vii

•

Using the Examples in This Manual on page viii

•

Documentation Conventions on page ix

•

Documentation Feedback on page xi

•

Requesting Technical Support on page xi

Documentation and Release Notes

To obtain the most current version of all Juniper Networks®technical documentation, see the product documentation page on the Juniper Networks website at

http://www.juniper.net/techpubs/.

If the information in the latest release notes differs from the information in the documentation, follow the product Release Notes.

Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration. The current list can be viewed at http://www.juniper.net/books.

Supported Platforms

For the features described in this document, the following platforms are supported:

•

M Series

•

MX Series

•

T Series

•

J Series

•

EX Series

•

PTX Series

Time Management Administration Guide for Routing Devices

Using the Examples in This Manual

If you want to use the examples in this manual, you can use the load merge or the load

merge relative command. These commands cause the software to merge the incoming

configuration into the current candidate configuration. The example does not become active until you commit the candidate configuration.

If the example configuration contains the top level of the hierarchy (or multiple hierarchies), the example is a full example. In this case, use the load merge command.

If the example configuration does not start at the top level of the hierarchy, the example is a snippet. In this case, use the load merge relative command. These procedures are described in the following sections.

Merging a Full Example

To merge a full example, follow these steps:

1. From the HTML or PDF version of the manual, copy a configuration example into a

text file, save the file with a name, and copy the file to a directory on your routing platform.

For example, copy thefollowingconfigurationto a file and name the file ex-script.conf. Copy the ex-script.conf file to the /var/tmp directory on your routing platform.

system {

scripts {

commit {

file ex-script.xsl;

}

} interfaces {

fxp0 {

disable; unit 0 {

family inet {

address 10.0.0.1/24;

}

2. Merge the contents of the file into your routing platform configuration by issuing the

load merge configuration mode command:

[edit] user@host# load merge /var/tmp/ex-script.conf load complete

Merging a Snippet

About the Documentation

To merge a snippet, follow these steps:

1. From the HTML or PDF version of the manual, copy a configuration snippet into a text

file, save the file with a name, and copy the file to a directory on your routing platform.

For example, copy the following snippet to a file and name the file

ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory

on your routing platform.

commit {

file ex-script-snippet.xsl; }

2. Move to the hierarchy level that is relevant for this snippet by issuing the following

configuration mode command:

[edit] user@host# edit system scripts [edit system scripts]

3. Merge the contents of the file into your routing platform configuration by issuing the

load merge relative configuration mode command:

[edit system scripts] user@host# load merge relative /var/tmp/ex-script-snippet.conf load complete

For more information about the load command, see the CLI User Guide.

Documentation Conventions

Table 1 on page ix defines notice icons used in this guide.

Table 1: Notice Icons

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware damage.Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Table 2 on page x defines the text and syntax conventions used in this guide.

Time Management Administration Guide for Routing Devices

Table 2: Text and Syntax Conventions

ExamplesDescriptionConvention

Fixed-width text like this

Italic text like this

Text like this

Represents text that you type.Bold text like this

Represents output that appears on the terminal screen.

•

Introduces or emphasizes important new terms.

•

Identifies guide names.

•

Identifies RFC and Internet draft titles.

Represents variables (options for which you substitute a value) in commands or configuration statements.

Represents names of configuration statements, commands, files, and directories;configurationhierarchylevels; or labels on routing platform components.

To enter configuration mode, type the configure command:

user@host> configure

user@host> show chassis alarms

No alarms currently active

•

A policy term is a named structure that defines match conditions and actions.

•

Junos OS CLI User Guide

•

RFC 1997, BGP Communities Attribute

Configure the machine’s domain name:

[edit] root@# set system domain-name

domain-name

•

To configure a stub area, include the

stub statement at the [edit protocols ospf area area-id] hierarchy level.

•

The console port islabeledCONSOLE.

stub <default-metric metric>;Encloses optional keywords orvariables.< > (angle brackets)

| (pipe symbol)

# (pound sign)

[ ] (square brackets)

Indention and braces ( { } )

; (semicolon)

GUI Conventions

Indicates a choice between the mutually exclusivekeywords or variables on either side of the symbol. The set of choices is often enclosed in parentheses for clarity.

same lineas the configuration statement to which it applies.

Encloses a variable for which you can substitute one or more values.

Identifies a level in the configuration hierarchy.

Identifies a leaf statement at a configuration hierarchy level.

broadcast | multicast

(string1 | string2 | string3)

rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the

community name members [ community-ids ]

[edit] routing-options {

static {

route default {

nexthop address; retain;

}

Table 2: Text and Syntax Conventions (continued)

Bold text like this

Representsgraphicaluser interface (GUI) items you click or select.

About the Documentation

ExamplesDescriptionConvention

•

In the Logical Interfaces box, select

All Interfaces.

•

To cancel the configuration, click

Cancel.

> (bold right angle bracket)

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can improve the documentation. You can send your comments to

techpubs-comments@juniper.net, or fill out the documentation feedback form at

https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include

the following information with your comments:

•

Document or topic name

•

URL or page number

•

Software release version (if applicable)

Requesting Technical Support

Technical productsupport is availablethrough theJuniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC support contract, or are covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.

Separates levels in a hierarchy of menu selections.

In the configuration editor hierarchy, select Protocols>Ospf.

•

JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User Guide located at

http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

•

Product warranties—For product warranty information, visit

http://www.juniper.net/support/warranty/.

•

JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.

Self-Help Online Tools and Resources

For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features:

•

Find CSC offerings: http://www.juniper.net/customers/support/

•

Search for known bugs: http://www2.juniper.net/kb/

Time Management Administration Guide for Routing Devices

•

Find product documentation: http://www.juniper.net/techpubs/

•

Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/

•

Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

•

Search technical bulletins for relevant hardware and software notifications:

http://kb.juniper.net/InfoCenter/

•

Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

•

Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/

To verifyservice entitlement by product serialnumber,use ourSerial Number Entitlement (SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

•

Use the Case Management tool in the CSC at http://www.juniper.net/cm/.

•

Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, see

http://www.juniper.net/support/requesting-support.html.

PART 1

Overview

•

Time Management Overview on page 3

Time Management Administration Guide for Routing Devices

CHAPTER 1

Time Management Overview

•

NTP Overview on page 3

•

Understanding NTP Time Servers on page 5

NTP Overview

Network Time Protocol (NTP) is a widely used protocol used to synchronize the clocks of routers and other hardware devices on the Internet. Primary NTP servers are synchronizedto areferenceclock directlytraceableto Coordinated Universal Time(UTC). Reference clocks include GPS receivers and telephone modem services, NTP accuracy expectations depend on the environment application requirements, however, NTP can generally maintain time to within tens of milliseconds over the public internet.

NTP isdefined inthe RFC5905: Network Time Protocol Version4: Protocol and Algorithms Specification

Junos devices can be configured to act as an NTP client, a secondary NTP server, or a primary NTP server. These variations are as follows:

•

Primary NTP Server—Primary NTP servers are synchronized to a reference clock that is directly traceableto UTC. These servers then re-distribute thistime data downstream to other Secondary NTP servers or NTP clients.

•

Secondary NTP Server—Secondary NTP servers are synchronized to a primary or secondary NTP server. These servers then re-distribute this data downstream to other Secondary NTP servers or NTP clients.

Time Management Administration Guide for Routing Devices

•

NTP Client—NTP clients aresynchronizedto aprimary or secondaryNTP server.Clients do not re-distribute this time data to other devices.

NOTE: The NTP subnet includes a number of widely accessible public primary

time servers that can be used as a network’s primary NTP server. Juniper Networks strongly recommends that you authenticate any primary servers you use.

Each device on your network can be configured to run in one or more of the following NTP modes:

•

Broadcast Mode—One or more devices is set up to transmit time information to a specified broadcast or multicast address. Other devices listen time sync packets on these addresses. This mode is less accurate than the client/server mode.

•

Client/Server Mode—Devices are organized hierarchically across the network in client/server relationships.

NOTE: QFX devices cannot be act as NTP servers, only clients.

•

Symmetric Active (peer) Mode—Two or more devices are configured as NTP server peers to provide redundancy.

By default, if an NTP client time drifts so that the difference in time from the NTP server exceeds 128 milliseconds, the NTP client is automatically stepped back into synchronization. The NTP client will still synchronize with the server even if the offset betweenthe NTP client and server exceeds the 1000-secondthreshold.You can manually request that adevice synchronize with an NTP serverby using the set datentp operational command on the router. On devices running Junos OS that have dual Routing Engines, the backup Routing Engine synchronizes directly with the master Routing Engine.

For more details on the Network Time Protocol, go to the Network Time Foundation website at http://www.ntp.org.

Chapter 1: Time Management Overview

NOTE: NTP is required for Common Criteria compliance. For more information

on the Common Criteria certification, see Public Sector Certifications.

In Junosoperating system (Junos OS) Release 11.2or later, NTPsupports IPv4VPN routing and forwarding (VRF) requests. This enables an NTP server running on a provider edge (PE) router to respond to NTP requests from a customer edge (CE) router. As a result, a PE router can process anyNTP request packet coming fromdifferent routing instances. In Junos OS Release 11.4 and later, NTP also supports IPv6 VRF requests.

Documentation

Synchronizing and Coordinating Time Distribution Using NTP on page 13•

• Example: Configuring NTP as a Single Time Source for Router and Switch Clock

Synchronization on page 17

Understanding NTP Time Servers

The IETF defined the NetworkTime Protocol(NTP) tosynchronize the clocks ofcomputer systems connected to each other over a network. Most large networks have an NTP server that ensures that time on all devices is synchronized, regardless of the device location. If you useone or more NTP servers on your network, ensure you include the NTS server addresses in your Junos OS configuration.

When configuring the NTP, you can specify which system on the network is the authoritative time source, or time server, and how time is synchronized between systems on the network. To do this, you configure the router, switch, or security device to operate in one of the following modes:

•

Client mode—In this mode, the local router or switch can be synchronized with the remote system, but the remote system cannever be synchronized with thelocal router or switch.

•

Symmetricactive mode—Inthis mode,the local router orswitch andthe remote system can synchronize with each other. You use this mode in a network in which either the local router or switch or the remote system might be a better source of time.

•

Broadcast mode—In this mode, the local router or switch sends periodic broadcast messages to a client population at the specified broadcast or multicast address. Normally, you include this statement only when the local router or switch is operating as a transmitter.

•

Server mode—In this mode, the local router or switch operates as an NTP server.

NOTE: Symmetric active mode can be initiated by either the local or the

remote system. Only one system needs to be configured to do so. This means that the local system can synchronize with any system that offers symmetric active mode without any configuration whatsoever. However, we strongly encourage you to configure authentication to ensure that the local system synchronizes only with known time servers.

Time Management Administration Guide for Routing Devices

NOTE: In NTP server mode, the Junos OS supports authentication as

follows:

•

If the NTP request from the client comes with an authentication key (such as a key ID and message digest sent with the packet), the request is processed and answered based on the authentication key match.

•

If the NTP request from the client comes without any authentication key, the request is processed and answered without authentication.

Documentation

• Configuring the NTP Time Server and Time Services

• Example: Configuring NTP as a Single Time Source for Router and Switch Clock

Synchronization on page 17

PART 2

Configuration

•

Configuring Time on page 9

•

Configuration Statements on page 23

Time Management Administration Guide for Routing Devices

CHAPTER 2

Configuring Time

•

Setting the Date and Time Locally on page 9

•

Configuring NTP on page 10

•

Modifying the Default Time Zone for a Router or Switch Running Junos OS on page 12

•

Synchronizing and Coordinating Time Distribution Using NTP on page 13

•

Configuring the NTP Time Server and Time Services on page 14

•

Example: Configuring NTP as a Single Time Source for Router and Switch Clock Synchronization on page 17

•

Configuring NTP Authentication Keys on page 18

•

Configuring the Router or Switch to Listen for Broadcast Messages Using NTP on page 19

•

Configuring the Router or Switch to Listen for MulticastMessagesUsing NTP on page 19

•

Updating the IANA Time Zone Database on Junos Devices on page 20

Setting the Date and Time Locally

You can set the device time on the command-line using the set date operational command:

To set the time in your Junos OS device, you can either configure it manually, or your device can take a system time from an Network Time Protocol (NTP) server. If you do not have access to an NTP server, you can configure Junos OS to keep its own local time using an onboard clock.

To set time locally:

1. From operational mode, manually set the date and time.

Because this is an operational-mode command, there is noneed to perform a commit operation.

user@host> set date YYYYMMDDhhmm.ss

For example:

user@host> set date 201307251632 Thu Jul 25 16:32:00 PDT 2013

2. Verify the time.

+ 47 hidden pages

Dynabrade Dynabug 57810, Dynabug 57812, Dynabug 57811, Dynabug 57813, Dynabug 57814 User Manual

Specifications and Main Features

Frequently Asked Questions

User Manual