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.
Summary of Contents for Omni Switch/Router
Page 1: ...Part No 060166 10 Rev C March 2005 Omni Switch Router User Manual Release 4 5 www alcatel com ...
Page 4: ...page iv ...
Page 110: ...WAN Modules Page 3 40 ...
Page 156: ...UI Table Filtering Using Search and Filter Commands Page 4 46 ...
Page 164: ...Using ZMODEM Page 5 8 ...
Page 186: ...Displaying and Setting the Swap State Page 6 22 ...
Page 202: ...Creating a New File System Page 7 16 ...
Page 270: ...Displaying Secure Access Entries in the MPM Log Page 10 14 ...
Page 430: ...OmniChannel Page 15 16 ...
Page 496: ...Configuring Source Route to Transparent Bridging Page 17 48 ...
Page 542: ...Dissimilar LAN Switching Capabilities Page 18 46 ...
Page 646: ...Application Example DHCP Policies Page 20 30 ...
Page 660: ...GMAP Page 21 14 ...
Page 710: ...Viewing the Virtual Interface of Multicast VLANs Page 23 16 ...
Page 722: ...Application Example 5 Page 24 12 ...
Page 788: ...Viewing UDP Relay Statistics Page 26 24 ...
Page 872: ...The WAN Port Software Menu Page 28 46 ...
Page 960: ...Deleting a PPP Entity Page 30 22 ...
Page 978: ...Displaying Link Status Page 31 18 ...
Page 988: ...Displaying ISDN Configuration Entry Status Page 32 10 ...
Page 1024: ...Backup Services Commands Page 34 14 ...
Page 1062: ...Diagnostic Test Cable Schematics Page 36 24 ...
Page 1072: ...Configuring a Switch with an MPX Page A 10 ...
Page 1086: ...Page B 14 ...
Page 1100: ...Page I 14 Index ...