Field descriptions – Alcatel Carrier Internetworking Solutions Omni Switch/Router User Manual

Page 307

Advertising
background image

NTP Statistics Menu

Page 12-29

It is possible to reset the statistics for more than one

NTP

association at a time by adding more

than one address to the command. For example, to reset statistics for a peer with IP address
1.1.1.4 and a peer with IP address 1.1.1.5, you would enter:

ntppreset 1.1.1.4 1.1.1.5

A brief message is displayed confirming the command.

Display Packet Count Statistics from the Control Module

In a comprehensive network-management environment, facilities should exist to perform
routine

NTP

control and monitoring functions. The control module of

NTP

is responsible for

sending and receiving control messages. To display the statistics for the control module, enter
the

ntpctlstat

command at the system prompt. A screen similar to the following is shown:

time since reset:

0

requests received:

0

responses sent:

0

fragments sent:

0

async messages sent: 0
error msgs sent:

0

total bad pkts:

0

packet too short:

0

response on input:

0

fragment on input:

0

error set on input:

0

bad offset on input:

0

bad version packets:

0

data in pkt too short:

0

unknown op codes:

0

Field Descriptions

The following section describes the fields displayed using the

ntpctlstat

command.

time since reset

. The number of seconds since the last reset of

NTP

(usually a switch reboot).

requests received

. The number of

NTP

requests received from any

NTP

association.

responses sent

. The number of

NTP

messages sent from this switch in response to

NTP

associ-

ation requests.

fragments sent

. The number of

NTP

messages sent from this switch that did not contain all

appropriate

NTP

data. This can occur if timestamp information from other NTP entities is

judged by this switch to be incorrect.

async messages sent

. The number of async trap packets sent.

error msgs sent

. The number of error messages sent from the switch to other

NTP

entities

because the switch was not able to respond to the

NTP

entity’s request.

total bad pkts

. The total number of packets received that

NTP

was not able to read.

packet too short

. The number of packets received that

NTP

rejected because the packet was

the incorrect length.

response on input

. The number of packets received that required the switch to respond to the

sender with an

NTP

message.

fragment on input

. The number of packets received that the switch that did not contain

complete

NTP

data.

error set on input

. The number of input control packets received with the error bit set.

Advertising