dhcp6_messages.mes 9.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191
  1. # Copyright (C) 2012 Internet Systems Consortium, Inc. ("ISC")
  2. #
  3. # Permission to use, copy, modify, and/or distribute this software for any
  4. # purpose with or without fee is hereby granted, provided that the above
  5. # copyright notice and this permission notice appear in all copies.
  6. #
  7. # THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
  8. # REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
  9. # AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
  10. # INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
  11. # LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
  12. # OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  13. # PERFORMANCE OF THIS SOFTWARE.
  14. $NAMESPACE isc::dhcp
  15. % DHCP6_CCSESSION_STARTED control channel session started on socket %1
  16. A debug message issued during startup after the IPv6 DHCP server has
  17. successfully established a session with the BIND 10 control channel.
  18. % DHCP6_CCSESSION_STARTING starting control channel session, specfile: %1
  19. This debug message is issued just before the IPv6 DHCP server attempts
  20. to establish a session with the BIND 10 control channel.
  21. % DHCP6_COMMAND_RECEIVED received command %1, arguments: %2
  22. A debug message listing the command (and possible arguments) received
  23. from the BIND 10 control system by the IPv6 DHCP server.
  24. % DHCP6_CONFIG_COMPLETE DHCPv6 server has completed configuration: %1
  25. This is an informational message announcing the successful processing of a
  26. new configuration. it is output during server startup, and when an updated
  27. configuration is committed by the administrator. Additional information
  28. may be provided.
  29. % DHCP6_CONFIG_LOAD_FAIL failed to load configuration: %1
  30. This critical error message indicates that the initial DHCPv6
  31. configuration has failed. The server will start, but nothing will be
  32. served until the configuration has been corrected.
  33. % DHCP6_CONFIG_NEW_SUBNET a new subnet has been added to configuration: %1
  34. This is an informational message reporting that the configuration has
  35. been extended to include the specified subnet.
  36. % DHCP6_CONFIG_OPTION_DUPLICATE multiple options with the code: %1 added to the subnet: %2
  37. This warning message is issued on attempt to configure multiple options with the
  38. same option code for the particular subnet. Adding multiple options is uncommon
  39. for DHCPv6, yet it is not prohibited.
  40. % DHCP6_CONFIG_START DHCPv6 server is processing the following configuration: %1
  41. This is a debug message that is issued every time the server receives a
  42. configuration. That happens start up and also when a server configuration
  43. change is committed by the administrator.
  44. % DHCP6_CONFIG_UPDATE updated configuration received: %1
  45. A debug message indicating that the IPv6 DHCP server has received an
  46. updated configuration from the BIND 10 configuration system.
  47. % DHCP6_DB_BACKEND_STARTED lease database started (type: %1, name: %2)
  48. This informational message is printed every time DHCPv6 is started.
  49. It indicates what database backend type is being to store lease and
  50. other information.
  51. % DHCP6_LEASE_ADVERT lease %1 advertised (client duid=%2, iaid=%3)
  52. This debug message indicates that the server successfully advertised
  53. a lease. It is up to the client to choose one server out of othe advertised
  54. and continue allocation with that server. This is a normal behavior and
  55. indicates successful operation.
  56. % DHCP6_LEASE_ADVERT_FAIL failed to advertise a lease for client duid=%1, iaid=%2
  57. This message indicates that the server failed to advertise (in response to
  58. received SOLICIT) a lease for a given client. There may be many reasons for
  59. such failure. Each specific failure is logged in a separate log entry.
  60. % DHCP6_LEASE_ALLOC lease %1 has been allocated (client duid=%2, iaid=%3)
  61. This debug message indicates that the server successfully granted (in
  62. response to client's REQUEST message) a lease. This is a normal behavior
  63. and incicates successful operation.
  64. % DHCP6_LEASE_ALLOC_FAIL failed to grant a lease for client duid=%1, iaid=%2
  65. This message indicates that the server failed to grant (in response to
  66. received REQUEST) a lease for a given client. There may be many reasons for
  67. such failure. Each specific failure is logged in a separate log entry.
  68. % DHCP6_NOT_RUNNING IPv6 DHCP server is not running
  69. A warning message is issued when an attempt is made to shut down the
  70. IPv6 DHCP server but it is not running.
  71. % DHCP6_NO_INTERFACES failed to detect any network interfaces
  72. During startup the IPv6 DHCP server failed to detect any network
  73. interfaces and is therefore shutting down.
  74. % DHCP6_NO_SUBNET_DEF_OPT failed to find subnet for address %1 when adding default options
  75. This warning message indicates that when attempting to add default options
  76. to a response, the server found that it was not configured to support
  77. the subnet from which the DHCPv6 request was received. The packet has
  78. been ignored.
  79. % DHCP6_NO_SUBNET_REQ_OPT failed to find subnet for address %1 when adding requested options
  80. This warning message indicates that when attempting to add requested
  81. options to a response, the server found that it was not configured
  82. to support the subnet from which the DHCPv6 request was received.
  83. The packet has been ignored.
  84. % DHCP6_OPEN_SOCKET opening sockets on port %1
  85. A debug message issued during startup, this indicates that the IPv6 DHCP
  86. server is about to open sockets on the specified port.
  87. % DHCP6_PACKET_PARSE_FAIL failed to parse incoming packet
  88. The IPv6 DHCP server has received a packet that it is unable to interpret.
  89. % DHCP6_PACKET_RECEIVED %1 packet received
  90. A debug message noting that the server has received the specified type
  91. of packet. Note that a packet marked as UNKNOWN may well be a valid
  92. DHCP packet, just a type not expected by the server (e.g. it will report
  93. a received OFFER packet as UNKNOWN).
  94. % DHCP6_PACKET_RECEIVE_FAIL error on attempt to receive packet: %1
  95. The IPv6 DHCP server tried to receive a packet but an error
  96. occured during this attempt. The reason for the error is included in
  97. the message.
  98. % DHCP6_PACKET_SEND_FAIL failed to send DHCPv6 packet: %1
  99. This error is output if the IPv6 DHCP server fails to send an assembled
  100. DHCP message to a client. The reason for the error is included in the
  101. message.
  102. % DHCP6_PACK_FAIL failed to assemble response correctly
  103. This error is output if the server failed to assemble the data to be
  104. returned to the client into a valid packet. The reason is most likely
  105. to be to a programming error: please raise a bug report.
  106. % DHCP6_PROCESS_IA_NA_REQUEST server is processing IA_NA option (duid=%1, iaid=%2, hint=%3)
  107. This is a debug message that indicates a processing of received IA_NA
  108. option. It may optionally contain an address that may be used by the server
  109. as a hint for possible requested address.
  110. % DHCP6_QUERY_DATA received packet length %1, data length %2, data is %3
  111. A debug message listing the data received from the client or relay.
  112. % DHCP6_RESPONSE_DATA responding with packet type %1 data is %2
  113. A debug message listing the data returned to the client.
  114. % DHCP6_SERVER_FAILED server failed: %1
  115. The IPv6 DHCP server has encountered a fatal error and is terminating.
  116. The reason for the failure is included in the message.
  117. % DHCP6_SESSION_FAIL failed to establish BIND 10 session (%1), running stand-alone
  118. The server has failed to establish communication with the rest of BIND
  119. 10 and is running in stand-alone mode. (This behavior will change once
  120. the IPv6 DHCP server is properly integrated with the rest of BIND 10.)
  121. % DHCP6_SHUTDOWN server shutdown
  122. The IPv6 DHCP server has terminated normally.
  123. % DHCP6_SHUTDOWN_REQUEST shutdown of server requested
  124. This debug message indicates that a shutdown of the IPv6 server has
  125. been requested via a call to the 'shutdown' method of the core Dhcpv6Srv
  126. object.
  127. % DHCP6_SRV_CONSTRUCT_ERROR error creating Dhcpv6Srv object, reason: %1
  128. This error message indicates that during startup, the construction of a
  129. core component within the IPv6 DHCP server (the Dhcpv6 server object)
  130. has failed. As a result, the server will exit. The reason for the
  131. failure is given within the message.
  132. % DHCP6_STANDALONE skipping message queue, running standalone
  133. This is a debug message indicating that the IPv6 server is running in
  134. standalone mode, not connected to the message queue. Standalone mode
  135. is only useful during program development, and should not be used in a
  136. production environment.
  137. % DHCP6_STARTING server starting
  138. This informational message indicates that the IPv6 DHCP server has
  139. processed any command-line switches and is starting.
  140. % DHCP6_START_INFO pid: %1, port: %2, verbose: %3, standalone: %4
  141. This is a debug message issued during the IPv6 DHCP server startup.
  142. It lists some information about the parameters with which the server
  143. is running.
  144. % DHCP6_SUBNET_SELECTED the %1 subnet was selected for client assignment
  145. This is a debug message informing that a given subnet was selected. It will
  146. be used for address and option assignment. This is one of the early steps
  147. in the processing of incoming client message.
  148. % DHCP6_SUBNET_SELECTION_FAILED failed to select a subnet for incoming packet, src=%1 type=%2
  149. This warning message is output when a packet was received from a subnet for
  150. which the DHCPv6 server has not been configured. The cause is most likely due
  151. to a misconfiguration of the server. The packet processing will continue, but
  152. the response will only contain generic configuration parameters and no
  153. addresses or prefixes.