Configuring the SNMP agent

NetView IP management requires the SNMP management functions that are provided by the Communications Server SNMP agent.

Procedure

To configure the SNMP agent and subagents, complete the following steps:

  1. Update the TCP/IP profile configuration to enable the SNMP subagent.
    Use the following statements:
    ; Enable the SNMP TCP/IP subagent
SACONFIG ENABLED SETSENABLED OSAENABLED ; enables SNMP TCP/IP subagent
;
; Set the community name (must match community name used by SNMP agent)
SACONFIG ENABLED COMMUNITY communityname      ; replace with your value
;
; Enable packet trace service and OSA-Express Network Traffic Analyzer
; (OSAENTA) trace service
NETMONITOR PKTTRCSERVICE NTATRCSERVICE
;
; Enable real-time SMF NMI service
NETMONITOR SMFS TCPCONNS MINLIFET 0 
;
; Set UDP ports
PORT
   161 UDP OMVS                ; OSNMPD Server  
   162 UDP SNMPQE              ; SNMPQE Agent
  2. Optional: If you want to start the SNMP TCP/IP subagent when TCP/IP starts, add the IOBSNMP procedure to the AUTOLOG statement in the TCP/IP profile.
  3. Update the Telnet profile to enable the SNMP TN3270E Telnet subagent.
    Use the following statements:
    ; Enable the SNMP TN3270E Telnet subagent
TNSAConfig                  ; Start up TN SNMP subagent
   Enabled                  ; Subagent must be enabled
   Agent 161                ; Specify agent port to contact
   Cachetime 30             ; Rebuild MIB info if older than 30 seconds
   Community communityname  ; Community name (replace with your value)
  4. To activate the configuration changes, stop and restart the TCP/IP and TN3270 address spaces.
    For more information about restarting address spaces, see the documentation of the MVS STOP and START commands in the MVS System Commands Reference at http://publib.boulder.ibm.com/infocenter/zos/v1r13/index.jsp.
  5. Update the snmpd.conf file in the /etc HFS directory.
    Make sure that the community name matches the name specified in the TCP/IP profile. Community names are case sensitive.
    Tip: If no snmpd.conf file exists in the /etc directory, you can copy the sample snmpd.conf file provided with z/OS Communications Server from the /usr/lpp/tcpip/samples directory. This sample defines the community name publicv2c for SNMP version 2c. This sample configuration file might need additional customization to provide adequate security for your environment.

    For more information about the snmpd.conf file, see the documentation of the SNMP agent (OSNMPD) in the z/OS Communications Server: IP Configuration Reference at http://publib.boulder.ibm.com/infocenter/zos/v1r13/index.jsp.

  6. Copy the osnmpd.data sample file from the /usr/lpp/tcpip/samples HFS directory to the /etc HFS directory as snmpd.data.
    Modify the sysDescr, sysContact, sysLocation, and sysName statements as needed.
  7. To obtain management information base (MIB) files for OSA adapters, go to https://www.ibm.com/servers/resourcelink and search for OSA MIB.
    Download the MIB files that are appropriate for your OSA adapters and copy the files to /etc/netview/mibs on the NetView system.
    Note: The IBM Resource Link website requires that you log in with an IBM ID. If you do not have an IBM ID, you can register to create one.
  8. To start the SNMP agent:
    1. Copy the OSNMPDPR sample JCL procedure from the EZA.SEZAINST data set to a system procedure library as OSNMPD.
    2. Modify the sample, following the instructions in the header.
    3. Run the modified procedure.
  9. To start the OSA subagent:
    1. Copy the IOBSNMP JCL sample procedure from the EZA.SEZAINST data set to a system procedure library.
    2. Modify the sample, following the instructions in the header.
    3. Run the modified procedure.
  10. To verify that the SNMP agent and subagents are running correctly, follow these steps:
    1. Run the following command from the OMVS environment: 
      osnmp -h hostname -c communityname walk sysordescr
      If the agent is running correctly, output similar to the following example is displayed:
      1.3.6.1.2.1.1.9.1.3.1 = z/OS SNMP Agent
1.3.6.1.2.1.1.9.1.3.2 = z/OS TN3270 SNMP Subagent
1.3.6.1.2.1.1.9.1.3.3 = z/OS TCP/IP SNMP Subagent
1.3.6.1.2.1.1.9.1.3.4 = OSA subagent
    2. Run the following command from the OMVS environment: 
      osnmp -c communityname -v walk ibmOSAExpChannelTable
      If the agent is running correctly, output similar to the following example is displayed:
      ibmOSAExpChannelNumber.4 = '0002'h
ibmOSAExpChannelNumber.6 = '0001'h
ibmOSAExpChannelNumber.10 = '000b'h
ibmOSAExpChannelNumber.12 = '0004'h
ibmOSAExpChannelNumber.14 = '0006'h
ibmOSAExpChannelType.4 = 49
ibmOSAExpChannelType.6 = 49
ibmOSAExpChannelType.10 = 17
ibmOSAExpChannelType.12 = 48