Agent Technology › Mainframe Agent Customization Considerations › The Discovery Process

The Discovery Process

You can encounter some problems with the discovery of agents on a z/OS LPAR. The following list provides a few tips for diagnosing and resolving these problems:

• Make sure your z/OS node is properly classified.

  The first-level discovery process uses the SNMP process from your TCP/IP stack to classify your mainframe node. This service is not the Agent Technology SNMP service, this is the SNMP service that comes with the IBM (or third-party) TCP/IP stack. This service must be running at the time the mainframe node is discovered for the node to be properly classified as an IBM3090.

  If the node is not properly classified, it can be reclassified manually from the NSM computer (using the reclass command).

• Community strings must agree between the z/OS aws_sadmin service and the NSM computer.

  See Configuring the aws_sadmin Service in the Installation Considerations section previously in this chapter for more information.

• Is the z/OS SNMP service listener port bound?

  Run onetstat under OMVS to ensure the SNMP listener port (6665 by default) is in the proper state. Verify that there are no firewalls preventing UDP traffic from entering your mainframe network.

• Is the awsAdmin MIB loaded in the z/OS store?

  If not, MIB-mixed agents are not discovered on this node.

• Can you Mibbrowse the awsAdmin MIB on the mainframe?

  The second-level discovery process uses the awsAdmin MIB to discover agents running on z/OS.

  1. Run mibbrowse in DOS from the NSM computer to verify this capability.
  2. Connect to the awsAdmin MIB on the appropriate host name and UDP port (6665 by default).
  3. Attempt to drill down though awsAdminAgentGroup >awsAdminAgentTable.

     Each active agent that is listed appears.