11.07.2015 Views

z/VM: TCP/IP Messages and Codes - z/VM - IBM

z/VM: TCP/IP Messages and Codes - z/VM - IBM

z/VM: TCP/IP Messages and Codes - z/VM - IBM

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

DNS <strong>and</strong> Resolver <strong>Messages</strong>terminated. This can happen when attempting toinitiate a zone transfer or when sending a request to aremote name server via <strong>TCP</strong>. The action will be retried.The situation can be caused by network outages orfailures at the remote host.System Action:User or Operator Response:The operation will be retried.None.RoutineName: FORWARDERS address <strong>IP</strong>addressignored, only limit are allowedSeverity:WarningExplanation: The FORWARDERS statement containedmore than limit <strong>IP</strong> addresses. Any <strong>IP</strong> addressesencountered after this limit is reached are ignored. Thisis done to balance reliability <strong>and</strong> performance. Morethan 3 addresses can adversely impact performancewithout significantly improving reliability.System Action:Exection continues.User or Operator Response:None.RoutineName:Foreign name server responds withRCODE = rcodeSeverity:WarningExplanation: The name server was in the process oftransferring a zone from a remote name server. In thepacket being processed, the foreign name serverindicated that there was a problem. The nature of theproblem is indicated by the value ofrcode. Thisindication could also mean the the foreign name serverhas refused to transfer the zone to us. In that case thevalue of rcode is 5.System Action: Exection continues. The zone transferwill be attempted again later.User or Operator Response: If the problem persists,the administrator of the remote name server should becontacted <strong>and</strong> informed of the problem.RoutineName: Ignoring fileId file, forwarding in useSeverity:Informational.Explanation: The name server will not use thespecified root cache file, because forwarding is in use.When a FORWARDERS statement is specified in theconfiguration file, the name server will only use the <strong>IP</strong>addresses of the name servers to help answerquestions.System Action:Exection continues.User or Operator Response:None.RoutineName: Insufficient data availableSeverity:Warning.Explanation: The name server received a datagramcontaining fewer bytes than was requested. The sizerequested was based on the amount expected <strong>and</strong>required to continue processing the current request.System Action: The current request will fail. Therequest will be retried by the originating host.User or Operator Response:None.RoutineName: Invalid flags 'xxxx'xSeverity:Error.Explanation: A name being extracted from a nameserver packet is incorrectly constructed.System Action: The data from such a packet is usuallydiscarded. The name server may return an error packetto the sending host with a return code that indicates aformatting error.User or Operator Response: If these messages becomeexcessive, turn on queue tracing to determine thesource of the bad packets <strong>and</strong> contact the name serveradministrator of that system.RoutineName: Label 0 or > 63 - input 'hostString'Severity:Error.Explanation: A name server host name had an invalidlength. The maximum length is 63 characters for anyportion of the name, the portions being separated bydots. The length cannot be 0. This is usually the resultof invalid data in the local SQL database.System Action: The packet that was being constructedwill be discarded. The invalid data cannot be sent toanother host.User or Operator Response: The hostString can beused to indicate what data to check in the SQLdatabase.RoutineName: dataType length > maxLengthSeverity:Warning.Explanation: The data being processed in a resourcerecord is too long.System Action: The name server truncates the data tothe MAX length indicated <strong>and</strong> sends that data.User or Operator Response: Correct the resourcerecord defined in the SQL tables.24 z/<strong>VM</strong>: <strong>TCP</strong>/<strong>IP</strong> <strong>Messages</strong> <strong>and</strong> <strong>Codes</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!