File:  [ELWIX - Embedded LightWeight unIX -] / embedaddon / ntp / html / decode.html
Revision 1.1.1.1 (vendor branch): download - view: text, annotated - select for diffs - revision graph
Tue May 29 12:08:38 2012 UTC (12 years ago) by misho
Branches: ntp, MAIN
CVS tags: v4_2_6p5p0, v4_2_6p5, HEAD
ntp 4.2.6p5

    1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    2: <html>
    3: 	<head>
    4: <meta http-equiv="content-type" content="text/html;charset=iso-8859-1">
    5: <meta name="generator" content="HTML Tidy, see www.w3.org">
    6: <title>ntpd Event Messages and Status Words</title>
    7: <link href="scripts/style.css" type="text/css" rel="stylesheet">
    8: </head>
    9: <body>
   10: <h3>Event Messages and Status Words</h3>
   11: <img src="pic/alice47.gif" alt="gif" align="left"><a href="http://www.eecis.udel.edu/%7emills/pictures.html">from <i>Alice's Adventures in Wonderland</i>, Lewis Carroll</a>
   12: 
   13: <p>Caterpillar knows all the error codes, which is more than most of us do.</p>
   14: 
   15: <p>Last update:
   16: <!-- #BeginDate format:En2m -->30-Apr-2010  23:13<!-- #EndDate -->
   17: UTC</p>
   18: <br clear="left">
   19: 
   20: <h4>Related Links</h4>
   21: 
   22: <p><script type="text/javascript" language="javascript" src="scripts/install.txt"></script></p>
   23: 
   24: <h4>Table of Contents</h4>
   25: 
   26: <ul>
   27: <li class="inline"><a href="#intro">Introduction</a></li>
   28: <li class="inline"><a href="#sys">System Status Word</a></li>
   29: <li class="inline"><a href="#peer">Peer Status Word</a></li>
   30: <li class="inline"><a href="#clock">Clock Status Word</a></li>
   31: <li class="inline"><a href="#flash">Flash Status Word</a></li>
   32: <li class="inline"><a href="#kiss">Kiss Codes</a></li>
   33: <li class="inline"><a href="#crypto">Crypto Messages</a></li>
   34: </ul>
   35: 
   36: <hr>
   37: 
   38: <h4 id="intro">Introduction</h4>
   39: 
   40: <p>This page lists the status words, event messages and error codes used for <tt>ntpd</tt> reporting and monitoring. Status words are used to display the current status of the running program. There is one system status word and a peer status word for each association. There is a clock status word for each association that supports a reference clock. There is a flash code for each association which shows errors found in the last packet received (pkt) and during protocol processing (peer). These are commonly viewed using the <tt>ntpq</tt> program.</p>
   41: 
   42: <p>Significant changes in program state are reported as events. There is one
   43: 	set of system events and a set of peer events for each association. In addition,
   44: 	there is a set of clock events for each association that supports a reference
   45: 	clock. Events are normally reported to the <tt>protostats</tt> monitoring file
   46: 	and optionally to the system log. In addition, if the trap facility is configured,
   47: 	events can be reported to a remote program that can page an administrator.</p>
   48: 
   49: <p>This page also includes a description of the error messages produced by the Autokey protocol. These messages are normally sent to the <tt>cryptostats</tt> monitoring file.</p>
   50: 
   51: <p>In the following tables the Code Field is the status or event code assigned and the Message Field a short string used for display and event reporting. The Description field contains a longer explanation of the status or event. Some messages include additional information useful for error diagnosis and performance assessment.</p>
   52: 
   53: <h4 id="sys">System Status Word</h4>
   54: 
   55: <p>The system status word consists of four fields LI (0-1), Source (2-7), Count (8-11) and Code (12-15). It is reported in the first line of the <tt>rv</tt> display produced by the <tt>ntpq</tt> program.</p>
   56: 
   57: <table width="50%" border="1" cellspacing="2" cellpadding="2">
   58: 
   59: <tr>
   60: <td><div align="center">Leap</div></td>
   61: <td><div align="center">Source</div></td>
   62: <td><div align="center">Count</div></td>
   63: <td><div align="center">Code</div></td>
   64: </tr>
   65: 
   66: </table>
   67: 
   68: <p>The Leap Field displays the system leap indicator bits coded as follows:</p>
   69: 
   70: <table width="100%" border="1" cellspacing="2" cellpadding="2">
   71: 
   72: <tr>
   73: <td>Code</td>
   74: <td>Message</td>
   75: <td>Description</td>
   76: </tr>
   77: 
   78: <tr>
   79: <td><tt>0</tt></td>
   80: <td><tt>leap_none</tt></td>
   81: <td>normal synchronized state</td>
   82: </tr>
   83: 
   84: <tr>
   85: <td><tt>1</tt></td>
   86: <td><tt>leap_add_sec</tt></td>
   87: <td>insert second after 23:59:59 of the current day</td>
   88: </tr>
   89: 
   90: <tr>
   91: <td><tt>2</tt></td>
   92: <td><tt>leap_del_sec</tt></td>
   93: <td>delete second 23:59:59 of the current day</td>
   94: </tr>
   95: 
   96: <tr>
   97: <td><tt>3</tt></td>
   98: <td><tt>leap_alarm</tt></td>
   99: <td>never synchronized</td>
  100: </tr>
  101: 
  102: </table>
  103: 
  104: <p>The Source Field displays the current synchronization source coded as follows:.</p>
  105: 
  106: <table width="100%" border="1" cellspacing="2" cellpadding="2">
  107: 
  108: <tr>
  109: <td>Code</td>
  110: <td>Message</td>
  111: <td>Description</td>
  112: </tr>
  113: 
  114: <tr>
  115: <td><tt>0</tt></td>
  116: <td><tt>sync_unspec</tt></td>
  117: <td>not yet synchronized</td>
  118: </tr>
  119: 
  120: <tr>
  121: <td><tt>1</tt></td>
  122: <td><tt>sync_pps</tt></td>
  123: <td>pulse-per-second signal (Cs, Ru, GPS, etc.)</td>
  124: </tr>
  125: 
  126: <tr>
  127: <td><tt>2</tt></td>
  128: <td><tt>sync_lf_radio</tt></td>
  129: <td>VLF/LF radio (WWVB, DCF77, etc.)</td>
  130: </tr>
  131: 
  132: <tr>
  133: <td><tt>3</tt></td>
  134: <td><tt>sync_hf_radio</tt></td>
  135: <td>MF/HF radio (WWV, etc.)</td>
  136: </tr>
  137: 
  138: <tr>
  139: <td><tt>4</tt></td>
  140: <td><tt>sync_uhf_radio</tt></td>
  141: <td>VHF/UHF radio/satellite (GPS, Galileo, etc.)</td>
  142: </tr>
  143: 
  144: <tr>
  145: <td><tt>5</tt></td>
  146: <td><tt>sync_local</tt></td>
  147: <td>local timecode (IRIG, LOCAL driver, etc.)</td>
  148: </tr>
  149: 
  150: <tr>
  151: <td><tt>6</tt></td>
  152: <td><tt>sync_ntp</tt></td>
  153: <td>NTP</td>
  154: </tr>
  155: 
  156: <tr>
  157: <td><tt>7</tt></td>
  158: <td><tt>sync_other</tt></td>
  159: <td>other (IEEE 1588, openntp, crony, etc.)</td>
  160: </tr>
  161: 
  162: <tr>
  163: <td><tt>8</tt></td>
  164: <td><tt>sync_wristwatch</tt></td>
  165: <td>eyeball and wristwatch</td>
  166: </tr>
  167: 
  168: <tr>
  169: <td><tt>9</tt></td>
  170: <td><tt>sync_telephone</tt></td>
  171: <td>telephone modem (ACTS, PTB, etc.)</td>
  172: </tr>
  173: 
  174: </table>
  175: 
  176: <p>The Count Field displays the number of events since the last time the code changed. Upon reaching 15, subsequent events with the same code are ignored.</p>
  177: 
  178: <p>The Event Field displays the most recent event message coded as follows:</p>
  179: 
  180: <table width="100%" border="1" cellspacing="2" cellpadding="2">
  181: 
  182: <tr>
  183: <td>Code</td>
  184: <td>Message</td>
  185: <td>Description</td>
  186: </tr>
  187: 
  188: <tr>
  189: <td><tt>00</tt></td>
  190: <td><tt>unspecified</tt></td>
  191: <td>unspecified</td>
  192: </tr>
  193: 
  194: <tr>
  195: <td><tt>01</tt></td>
  196: <td><tt>freq_not_set</tt></td>
  197: <td>frequency file not available</td>
  198: </tr>
  199: 
  200: <tr>
  201: <td><tt>02</tt></td>
  202: <td><tt>freq_set</tt></td>
  203: <td>frequency set from frequency file</td>
  204: </tr>
  205: 
  206: <tr>
  207: <td><tt>03</tt></td>
  208: <td><tt>spike_detect</tt></td>
  209: <td>spike detected</td>
  210: </tr>
  211: 
  212: <tr>
  213: <td><tt>04</tt></td>
  214: <td><tt>freq_mode</tt></td>
  215: <td>initial frequency training mode</td>
  216: </tr>
  217: 
  218: <tr>
  219: <td><tt>05</tt></td>
  220: <td><tt>clock_sync</tt></td>
  221: <td>clock synchronized</td>
  222: </tr>
  223: 
  224: <tr>
  225: <td><tt>06</tt></td>
  226: <td><tt>restart</tt></td>
  227: <td>program restart</td>
  228: </tr>
  229: 
  230: <tr>
  231: <td><tt>07</tt></td>
  232: <td><tt>panic_stop</tt></td>
  233: <td>clock error more than 600 s</td>
  234: </tr>
  235: 
  236: <tr>
  237: <td><tt>08</tt></td>
  238: <td><tt>no_system_peer</tt></td>
  239: <td>no system peer</td>
  240: </tr>
  241: 
  242: <tr>
  243: <td><tt>09</tt></td>
  244: <td><tt>leap_armed</tt></td>
  245: <td>leap second armed from file or Autokey</td>
  246: </tr>
  247: 
  248: <tr>
  249: <td><tt>0a</tt></td>
  250: <td><tt>leap_disarmed</tt></td>
  251: <td>leap second disarmed</td>
  252: </tr>
  253: 
  254: <tr>
  255: <td><tt>0b</tt></td>
  256: <td><tt>leap_event</tt></td>
  257: <td>leap event</td>
  258: </tr>
  259: 
  260: <tr>
  261: <td><tt>0c</tt></td>
  262: <td><tt>clock_step</tt></td>
  263: <td>clock stepped</td>
  264: </tr>
  265: 
  266: <tr>
  267: <td><tt>0d</tt></td>
  268: <td><tt>kern</tt></td>
  269: <td>kernel information message</td>
  270: </tr>
  271: 
  272: <tr>
  273: <td><tt>0e</tt></td>
  274: <td><tt>TAI...</tt></td>
  275: <td>leapsecond values update from file</td>
  276: </tr>
  277: 
  278: <tr>
  279: <td><tt>0f</tt></td>
  280: <td><tt>stale leapsecond values</tt></td>
  281: <td>new NIST leapseconds file needed</td>
  282: </tr>
  283: <tr>
  284: <td><tt>10</tt></td>
  285: <td><tt>clockhop</tt></td>
  286: <td>spurious clock hop suppressed</td>
  287: </tr>
  288: 
  289: </table>
  290: 
  291: <h4 id="peer">Peer Status Word</h4>
  292: 
  293: <p>The peer status word consists of four fields: Status (0-4), Select (5-7), Count (8-11) and Code (12-15). It is reported in the first line of the <tt>rv <i>associd</i></tt> display produced by the <tt>ntpq</tt> program.</p>
  294: 
  295: <table width="50%" border="1" cellspacing="2" cellpadding="2">
  296: 
  297: <tr>
  298: <td><div align="center">Status</div></td>
  299: <td><div align="center">Select</div></td>
  300: <td><div align="center">Count</div></td>
  301: <td><div align="center">Code</div></td>
  302: </tr>
  303: 
  304: </table>
  305: 
  306: <p>The Status Field displays the peer status code bits in hexadecimal; each bit is an independent flag.  (Note this field is 5 bits wide, and combines with the the 3-bit-wide Select Field to create the first full byte of the peer status word.)  The meaning of each bit in the Status Field is listed in the following table:</p>
  307: 
  308: <table width="100%" border="1" cellspacing="2" cellpadding="2">
  309: 
  310: <tr>
  311: <td>Code</td>
  312: <td>Message</td>
  313: <td>Description</td>
  314: </tr>
  315: 
  316: <tr>
  317: <td><tt>08</tt></td>
  318: <td><tt>bcst</tt></td>
  319: <td>broadcast association</td>
  320: </tr>
  321: 
  322: <tr>
  323: <td><tt>10</tt></td>
  324: <td><tt>reach</tt></td>
  325: <td>host reachable</td>
  326: </tr>
  327: 
  328: <tr>
  329: <td><tt>20</tt></td>
  330: <td><tt>authenb</tt></td>
  331: <td>authentication enabled</td>
  332: </tr>
  333: 
  334: <tr>
  335: <td><tt>40</tt></td>
  336: <td><tt>auth</tt></td>
  337: <td>authentication ok</td>
  338: </tr>
  339: 
  340: <tr>
  341: <td><tt>80</tt></td>
  342: <td><tt>config</tt></td>
  343: <td>persistent association</td>
  344: </tr>
  345: 
  346: </table>
  347: 
  348: <p>The Select Field displays the current selection status. (The T Field in the following table gives the corresponding tally codes used in the <tt>ntpq peers</tt> display.) The values are coded as follows:</p>
  349: 
  350: <table width="100%" border="1" cellspacing="2" cellpadding="2">
  351: 
  352: <tr>
  353: <td>Code</td>
  354: <td>Message</td>
  355: <td>T</td>
  356: <td>Description</td>
  357: </tr>
  358: 
  359: <tr>
  360: <td><tt>0</tt></td>
  361: <td><tt>sel_reject</tt></td>
  362: <td>&nbsp;</td>
  363: <td>discarded as not valid (TEST10-TEST13)</td>
  364: </tr>
  365: 
  366: <tr>
  367: <td><tt>1</tt></td>
  368: <td><tt>sel_falsetick</tt></td>
  369: <td><tt>x</tt></td>
  370: <td>discarded by intersection algorithm</td>
  371: </tr>
  372: 
  373: <tr>
  374: <td><tt>2</tt></td>
  375: <td><tt>sel_excess</tt></td>
  376: <td><tt>.</tt></td>
  377: <td>discarded by table overflow (not used)</td>
  378: </tr>
  379: 
  380: <tr>
  381: <td><tt>3</tt></td>
  382: <td><tt>sel_outlyer</tt></td>
  383: <td><tt>-</tt></td>
  384: <td>discarded by the cluster algorithm</td>
  385: </tr>
  386: 
  387: <tr>
  388: <td><tt>4</tt></td>
  389: <td><tt>sel_candidate</tt></td>
  390: <td><tt>+</tt></td>
  391: <td>included by the combine algorithm</td>
  392: </tr>
  393: 
  394: <tr>
  395: <td><tt>5</tt></td>
  396: <td><tt>sel_backup</tt></td>
  397: <td><tt>#</tt></td>
  398: <td>backup (more than <tt>tos maxclock</tt> sources)</td>
  399: </tr>
  400: 
  401: <tr>
  402: <td><tt>6</tt></td>
  403: <td><tt>sel_sys.peer</tt></td>
  404: <td><tt>*</tt></td>
  405: <td>system peer</td>
  406: </tr>
  407: 
  408: <tr>
  409: <td><tt>7</tt></td>
  410: <td><tt>sel_pps.peer</tt></td>
  411: <td><tt>o</tt></td>
  412: <td>PPS peer (when the prefer peer is valid)</td>
  413: </tr>
  414: 
  415: </table>
  416: 
  417: <p>The Count Field displays the number of events since the last time the code changed. Upon reaching 15, subsequent events with the same code are ignored. </p>
  418: 
  419: <p>The Event Field displays the most recent event message coded as follows:</p>
  420: 
  421: <table width="100%" border="1" cellspacing="2" cellpadding="2">
  422: 
  423: <tr>
  424: <td>Code</td>
  425: <td>Message</td>
  426: <td>Description</td>
  427: </tr>
  428: 
  429: <tr>
  430: <td><tt>01</tt></td>
  431: <td><tt>mobilize</tt></td>
  432: <td>association mobilized</td>
  433: </tr>
  434: 
  435: <tr>
  436: <td><tt>02</tt></td>
  437: <td><tt>demobilize</tt></td>
  438: <td>association demobilized</td>
  439: </tr>
  440: 
  441: <tr>
  442: <td><tt>03</tt></td>
  443: <td><tt>unreachable</tt></td>
  444: <td>server unreachable</td>
  445: </tr>
  446: 
  447: <tr>
  448: <td><tt>04</tt></td>
  449: <td><tt>reachable</tt></td>
  450: <td>server reachable</td>
  451: </tr>
  452: 
  453: <tr>
  454: <td><tt>05</tt></td>
  455: <td><tt>restart</tt></td>
  456: <td>association restart</td>
  457: </tr>
  458: 
  459: <tr>
  460: <td><tt>06</tt></td>
  461: <td><tt>no_reply</tt></td>
  462: <td>no server found (<tt>ntpdate</tt> mode)</td>
  463: </tr>
  464: 
  465: <tr>
  466: <td><tt>07</tt></td>
  467: <td><tt>rate_exceeded</tt></td>
  468: <td>rate exceeded (kiss code <tt>RATE</tt>)</td>
  469: </tr>
  470: 
  471: <tr>
  472: <td><tt>08</tt></td>
  473: <td><tt>access_denied</tt></td>
  474: <td>access denied (kiss code <tt>DENY</tt>)</td>
  475: </tr>
  476: 
  477: <tr>
  478: <td><tt>09</tt></td>
  479: <td><tt>leap_armed</tt></td>
  480: <td>leap armed from server LI code</td>
  481: </tr>
  482: 
  483: <tr>
  484: <td><tt>0a</tt></td>
  485: <td><tt>sys_peer</tt></td>
  486: <td>become system peer</td>
  487: </tr>
  488: 
  489: <tr>
  490: <td><tt>0b</tt></td>
  491: <td><tt>clock_event</tt></td>
  492: <td>see clock status word</td>
  493: </tr>
  494: 
  495: <tr>
  496: <td><tt>0c</tt></td>
  497: <td><tt>bad_auth</tt></td>
  498: <td>authentication failure</td>
  499: </tr>
  500: 
  501: <tr>
  502: <td><tt>0d</tt></td>
  503: <td><tt>popcorn</tt></td>
  504: <td>popcorn spike suppressor</td>
  505: </tr>
  506: 
  507: <tr>
  508: <td><tt>0e</tt></td>
  509: <td><tt>interleave_mode</tt></td>
  510: <td>entering interleave mode</td>
  511: </tr>
  512: 
  513: <tr>
  514: <td><tt>0f</tt></td>
  515: <td><tt>interleave_error</tt></td>
  516: <td>interleave error (recovered)</td>
  517: </tr>
  518: 
  519: <tr>
  520: <td><tt>10</tt></td>
  521: <td><tt>TAI...</tt></td>
  522: <td>leapsecond values update from server</td>
  523: </tr>
  524: 
  525: </table>
  526: 
  527: <h4 id="clock">Clock Status Word</h4>
  528: 
  529: <p>The clock status word consists of four fields: Unused (0-7), Count (8-11) and Code (12-15). It is reported in the first line of the <tt>clockvar <i>associd</i></tt> display produced by the <tt>ntpq</tt> program.</p>
  530: <table width="50%" border="1" cellspacing="2" cellpadding="2">
  531: 
  532: <tr>
  533: <td><div align="center">Unused</div></td>
  534: <td><div align="center">Count</div></td>
  535: <td><div align="center">Code</div></td>
  536: </tr>
  537: 
  538: </table>
  539: 
  540: <p>The Count Field displays the number of events since the last <tt>lockvar</tt> command, while the Event Field displays the most recent event message coded as follows:</p>
  541: 
  542: <table width="100%" border="1" cellspacing="2" cellpadding="2">
  543: 
  544: <tr>
  545: <td>Code</td>
  546: <td>Message</td>
  547: <td>Description</td>
  548: </tr>
  549: 
  550: <tr>
  551: <td><tt>00</tt></td>
  552: <td><tt>clk_unspe</tt></td>
  553: <td>nominal</td>
  554: </tr>
  555: 
  556: <tr>
  557: <td><tt>01</tt></td>
  558: <td><tt>clk_noreply</tt></td>
  559: <td>no reply to poll</td>
  560: </tr>
  561: 
  562: <tr>
  563: <td><tt>02</tt></td>
  564: <td><tt>clk_badformat</tt></td>
  565: <td>bad timecode format</td>
  566: </tr>
  567: 
  568: <tr>
  569: <td><tt>03</tt></td>
  570: <td><tt>clk_fault</tt></td>
  571: <td>hardware or software fault</td>
  572: </tr>
  573: 
  574: <tr>
  575: <td><tt>04</tt></td>
  576: <td><tt>clk_bad_signal</tt></td>
  577: <td>signal loss</td>
  578: </tr>
  579: 
  580: <tr>
  581: <td><tt>05</tt></td>
  582: <td><tt>clk_bad_date</tt></td>
  583: <td>bad date format</td>
  584: </tr>
  585: 
  586: <tr>
  587: <td><tt>06</tt></td>
  588: <td><tt>clk_bad_time</tt></td>
  589: <td>bad time format</td>
  590: </tr>
  591: 
  592: </table>
  593: 
  594: <p>When the clock driver sets the code to a new value, a <tt>clock_alarm</tt> (11) peer event is reported.</p>
  595: 
  596: <h4 id="flash">Flash Status Word</h4>
  597: 
  598: <p>The flash status word is displayed by the <tt>ntpq</tt> program <tt>rv</tt> command. It consists of a number of bits coded in hexadecimal as follows:</p>
  599: 
  600: <table width="100%" border="1" cellspacing="2" cellpadding="2">
  601: 
  602: <tr>
  603: <td>Code</td>
  604: <td>Tag</td>
  605: <td>Message</td>
  606: <td>Description</td>
  607: </tr>
  608: 
  609: <tr>
  610: <td><tt>0001</tt></td>
  611: <td>TEST1</td>
  612: <td><tt>pkt_dup</tt></td>
  613: <td>duplicate packet</td>
  614: </tr>
  615: 
  616: <tr>
  617: <td><tt>0002</tt></td>
  618: <td>TEST2</td>
  619: <td><tt>pkt_bogus</tt></td>
  620: <td>bogus packet</td>
  621: </tr>
  622: 
  623: <tr>
  624: <td><tt>0004</tt></td>
  625: <td>TEST3</td>
  626: <td><tt>pkt_unsync</tt></td>
  627: <td>protocol unsynchronized</td>
  628: </tr>
  629: 
  630: <tr>
  631: <td><tt>0008</tt></td>
  632: <td>TEST4</td>
  633: <td><tt>pkt_denied</tt></td>
  634: <td>access denied</td>
  635: </tr>
  636: 
  637: <tr>
  638: <td><tt>0010</tt></td>
  639: <td>TEST5</td>
  640: <td><tt>pkt_auth</tt></td>
  641: <td>bad authentication</td>
  642: </tr>
  643: 
  644: <tr>
  645: <td><tt>0020</tt></td>
  646: <td>TEST6</td>
  647: <td><tt>pkt_stratum</tt></td>
  648: <td>bad synch or stratum</td>
  649: </tr>
  650: 
  651: <tr>
  652: <td><tt>0040</tt></td>
  653: <td>TEST7</td>
  654: <td><tt>pkt_header</tt></td>
  655: <td>bad header</td>
  656: </tr>
  657: 
  658: <tr>
  659: <td><tt>0080</tt></td>
  660: <td>TEST8</td>
  661: <td><tt>pkt_autokey</tt></td>
  662: <td>bad autokey</td>
  663: </tr>
  664: 
  665: <tr>
  666: <td><tt>0100</tt></td>
  667: <td>TEST9</td>
  668: <td><tt>pkt_crypto</tt></td>
  669: <td>bad crypto</td>
  670: </tr>
  671: 
  672: <tr>
  673: <td><tt>0200</tt></td>
  674: <td>TEST10</td>
  675: <td><tt>peer_stratum</tt></td>
  676: <td>peer bad synch or stratum</td>
  677: </tr>
  678: 
  679: <tr>
  680: <td><tt>0400</tt></td>
  681: <td>TEST11</td>
  682: <td><tt>peer_dist</tt></td>
  683: <td>peer distance exceeded</td>
  684: </tr>
  685: 
  686: <tr>
  687: <td><tt>0800</tt></td>
  688: <td>TEST12</td>
  689: <td><tt>peer_loop</tt></td>
  690: <td>peer synchronization loop</td>
  691: </tr>
  692: 
  693: <tr>
  694: <td><tt>1000</tt></td>
  695: <td>TEST13</td>
  696: <td><tt>peer_unreach</tt></td>
  697: <td>peer unreachable</td>
  698: </tr>
  699: 
  700: </table>
  701: 
  702: <h4 id="kiss">Kiss Codes</h4>
  703: 
  704: <p>Kiss codes are used in kiss-o'-death (koD) packets, billboard displays and log messages. They consist of a string of four zero-padded ASCII charactes. In practice they are informal and tend to change with time and implementation. Some of these codes can appear in the reference identifier field in <tt>ntpq</tt> billboards. Following is the current list:</p>
  705: 
  706: <table width="100%" border="1" cellspacing="2" cellpadding="2">
  707: 
  708: <tr>
  709: <td>Code</td>
  710: <td>Description</td>
  711: </tr>
  712: 
  713: <tr>
  714: <td><tt>ACST</tt></td>
  715: <td>manycast server</td>
  716: </tr>
  717: 
  718: <tr>
  719: <td><tt>AUTH</tt></td>
  720: <td>authentication error</td>
  721: </tr>
  722: 
  723: <tr>
  724: <td><tt>AUTO</tt></td>
  725: <td>Autokey sequence error</td>
  726: </tr>
  727: 
  728: <tr>
  729: <td><tt>BCST</tt></td>
  730: <td>broadcast server</td>
  731: </tr>
  732: 
  733: <tr>
  734: <td><tt>CRYPT</tt></td>
  735: <td>Autokey protocol error</td>
  736: </tr>
  737: 
  738: <tr>
  739: <td><tt>DENY</tt></td>
  740: <td>access denied by server</td>
  741: </tr>
  742: 
  743: <tr>
  744: <td><tt>INIT</tt></td>
  745: <td>association initialized</td>
  746: </tr>
  747: 
  748: <tr>
  749: <td><tt>MCST</tt></td>
  750: <td>multicast server</td>
  751: </tr>
  752: 
  753: <tr>
  754: <td><tt>RATE</tt></td>
  755: <td>rate exceeded</td>
  756: </tr>
  757: 
  758: <tr>
  759: <td><tt>TIME</tt></td>
  760: <td>association timeout</td>
  761: </tr>
  762: 
  763: <tr>
  764: <td><tt>STEP</tt></td>
  765: <td>step time change</td>
  766: </tr>
  767: 
  768: </table>
  769: 
  770: <h4 id="crypto">Crypto Messages</h4>
  771: 
  772: <p>These messages are sent to the <tt>cryptostats</tt> file when an error is detected in the Autokey protocol.</p>
  773: 
  774: <table width="100%" border="1" cellspacing="2" cellpadding="2">
  775: 
  776: <tr>
  777: <td>Code</td>
  778: <td>Message</td>
  779: <td>Description</td>
  780: </tr>
  781: 
  782: <tr>
  783: <td><tt>01</tt></td>
  784: <td><tt>bad_format</tt></td>
  785: <td>bad extension field format or length</td>
  786: </tr>
  787: 
  788: <tr>
  789: <td><tt>02</tt></td>
  790: <td><tt>bad_timestamp</tt></td>
  791: <td>bad timestamp</td>
  792: </tr>
  793: 
  794: <tr>
  795: <td><tt>03</tt></td>
  796: <td><tt>bad_filestamp</tt></td>
  797: <td>bad filestamp</td>
  798: </tr>
  799: 
  800: <tr>
  801: <td><tt>04</tt></td>
  802: <td><tt>bad_public_key</tt></td>
  803: <td>bad or missing public key</td>
  804: </tr>
  805: 
  806: <tr>
  807: <td><tt>05</tt></td>
  808: <td><tt>bad_digest</tt></td>
  809: <td>unsupported digest type</td>
  810: </tr>
  811: 
  812: <tr>
  813: <td><tt>06</tt></td>
  814: <td><tt>bad_identity</tt></td>
  815: <td>unsupported identity type</td>
  816: </tr>
  817: 
  818: <tr>
  819: <td><tt>07</tt></td>
  820: <td><tt>bad_siglength</tt></td>
  821: <td>bad signature length</td>
  822: </tr>
  823: 
  824: <tr>
  825: <td><tt>08</tt></td>
  826: <td><tt>bad signature</tt></td>
  827: <td>extension field signature not verified</td>
  828: </tr>
  829: 
  830: <tr>
  831: <td><tt>09</tt></td>
  832: <td><tt>cert_not_verified</tt></td>
  833: <td>certificate signature not verified</td>
  834: </tr>
  835: 
  836: <tr>
  837: <td><tt>0a</tt></td>
  838: <td><tt>cert_expired</tt></td>
  839: <td>host certificate expired</td>
  840: </tr>
  841: 
  842: <tr>
  843: <td><tt>0b</tt></td>
  844: <td><tt>bad_cookie</tt></td>
  845: <td>bad or missing cookie</td>
  846: </tr>
  847: 
  848: <tr>
  849: <td><tt>0c</tt></td>
  850: <td><tt>bad_leapseconds</tt></td>
  851: <td>bad or missing leapseconds values</td>
  852: </tr>
  853: 
  854: <tr>
  855: <td><tt>0d</tt></td>
  856: <td><tt>cert_missing</tt></td>
  857: <td>bad or missing certificate</td>
  858: </tr>
  859: 
  860: <tr>
  861: <td><tt>0e</tt></td>
  862: <td><tt>bad_group_key</tt></td>
  863: <td>bad or missing group key</td>
  864: </tr>
  865: 
  866: <tr>
  867: <td><tt>0f</tt></td>
  868: <td><tt>proto_error</tt></td>
  869: <td>protocol error</td>
  870: </tr>
  871: 
  872: </table>
  873: 
  874: <hr>
  875: 
  876: <script type="text/javascript" language="javascript" src="scripts/footer.txt"></script>
  877: 
  878: </body>
  879: </html>

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>