Step 16: Verify that the ADNR system is functioning correctly (optional)

View the MVS™ console of the ADNR system after you have started it to verify that the application started correctly and is still running. If there are any failure messages, see the appropriate message description for the appropriate corrective action. View the syslogd file of the ADNR system to see whether any error or warning messages were issued.

Use the following commands to verify that ADNR is functioning correctly:

• If connectivity cannot be established, ADNR issues the eventual action message EZD1272E, ADNR CONNECTION ATTEMPT TO GWM gwmipaddress FAILED. If this message is issued and the GWM is active, verify that routing exists between the IP addresses used by the GWM and ADNR.
• Verify that ADNR is started and connected to the expected Advisor by issuing ADNR's MODIFY procname,DISPLAY,GWM,DETAIL command. Verify that the GWM IP address and port is the expected IP address and port of the Advisor to which you intended to connect.
• From the Advisor, issue the MODIFY procname,DISPLAY,LB command to list the LB indexes known to the Advisor. Identify the LB index representing ADNR, and then issue the Advisor MODIFY procname,LB,INDEX=lb-index command. Verify that each member you have registered that you expect to be available in the sysplex displays as available in the AVAIL field. If there is a discrepancy in the availability status, check the FLAGS field for possible reasons why a member is not available. For more information about the flags in the FLAGS field for the Advisor, see z/OS Communications Server: IP System Administrator's Commands.
• Verify that server and host groups have been properly registered to the GWM by issuing ADNR's MODIFY procname,DISPLAY,GWM,GROUPS,DETAIL command. Verify that each member you have registered that you expect to be available in the sysplex displays as available in the AVAIL field. If there is a discrepancy in the availability status, check the FLAGS field for possible reasons why a member is not available. For more information about the flags in the FLAGS field for ADNR, see z/OS Communications Server: IP System Administrator's Commands.
• Verify that Agents are aware of members that they own by issuing the MODIFY procname,DISPLAY,MEMBERS Agent command. Any ADNR-registered IP addresses owned by the system where the Agent is running should appear in the display.
• Verify that ADNR is able to communicate properly with the name servers it manages by issuing ADNR's MODIFY procname,DISPLAY,DNS,ZONES,SUMMARY command. Verify that the ZONE STATUS field is or changes to SYNCHRONIZED after the convergence period expires. For the definition of the convergence period, see Step 8: Configure ADNR to automatically restart in case of application or system failure (optional). If any zone status begins with the value NOT_RESPONSIVE, there is either a connectivity problem between ADNR and the name server, or there is a configuration mismatch between ADNR and the name server. For more information about diagnosing unresponsive zones, see z/OS Communications Server: IP Diagnosis Guide. If ADNR is unable to properly communicate with a name server, ADNR issues eventual action message EZD1278E, which remains until the problem is resolved.
• Verify that name servers reflect the availability status of the sysplex resources that you have configured with ADNR. Issue ADNR's MODIFY procname,DISPLAY,ZONES,ZONEID=zone_label,DETAIL command for each zone configured to ADNR, or issue the MODIFY procname,DISPLAY,ZONES,DETAIL to view all zones. Verify that the DNS RR STATUS field for each resource record display is PRESENT for each resource that is available in the sysplex.
• Use the z/OS® UNIX dig command to perform a zone transfer of the ADNR-managed zones, and verify that the zone contents match the expected content, based on the members configured to ADNR and the availability status of those members in the sysplex. The dig command to use has the following form:

  dig @name_server_address  domain_name axfr

  Tip: If zone transfers were restricted by name server configuration to clients from specific IP addresses or from clients that have digitally signed their requests (TSIG), you might have to issue the dig command with the -b option or the -k option to, respectively, force the request to originate from a specific IP address or be digitally signed with the appropriate signature. For more information about the dig command, see z/OS Communications Server: IP System Administrator's Commands.
• Verify that ADNR is functioning correctly when using AT-TLS:
  • Use the pasearch command from the z/OS UNIX shell to query information from the Policy Agent. For more information about displaying policy based networking information, see z/OS Communications Server: IP System Administrator's Commands.
  • Use the Netstat TTLS/-x command to display z/OS Load Balancing Advisor and ADNR AT-TLS policies. For more information about the Netstat TTLS/-x report, see z/OS Communications Server: IP System Administrator's Commands.