Provide TCP/IP profile statements

Update the following configuration statements in hlq.PROFILE.TCPIP:
  • AUTOLOG
  • PORT

There are two primary TCP/IP ports used by the SNMP agent, one for receiving incoming requests and one for sending traps to managers.

The default port used by the SNMP agent to receive incoming requests is 161. If you want the agent to use port 161 for this purpose and want to ensure that no other application uses this port, you must specify the following PORT statement in your profile data set: 
PORT
  161 UDP OSNMPD              ; SNMP Agent port for SNMP requests

If the agent will be started from the z/OS® shell, reserve the port instead for z/OS UNIX by typing OMVS instead of OSNMPD.

If you want to define a port other than 161 for SNMP requests, take the following steps:

  1. Start the agent with the -p parameter.
  2. Configure management applications to use the new port:
    • For the snmp command, make an entry in the OSNMP.CONF file with the correct port number. For details on creating this entry, see the description for targetAgent in the OSNMP.CONF statement in the z/OS Communications Server: IP Configuration Reference.
    • Where supported, configure other management applications to use the new port.
  3. Configure subagents to use the new port:
    1. Specify the port number to use on the SACONFIG profile statement for the TCP/IP subagent.
    2. Specify the port number to use on the ROUTESA_CONFIG profile statement for the OMPROUTE subagent.
    3. Specify the port number to use on the -p parameter when starting the Network SLAPM2 subagent.
    4. Specify the port number to use on the TNSACONFIG profile statement for the TN3270E Telnet subagent.
    5. If you are using DPI subagents other than those supplied with z/OS Communications Server, set the SNMP_PORT environment variable to enable user-written subagents to connect to the agent.
The SNMP agent uses port 162, by default, for sending traps to the managers specified in SNMPTRAP.DEST or SNMPD.CONF file. Port 162 should be reserved for the management application primarily responsible for trap processing. If your environment requires multiple management applications at the same IP address to receive traps, consider using the Trap Forwarder Daemon. See Step 5: Configure the trap forwarder daemon for more details. If the SNMP query engine is typically used for processing traps and other applications, such as snmp, that are only occasionally used, the following port reservations are recommended. 
PORT
  162 UDP SNMPQE  ; SNMPQuery Engine
You must also reserve additional ports for use by the snmp command by specifying
nnnnn UDP OMVS

where nnnnn is a number in the range 0–65535 and nnnnn is used as the -p parameter value on the snmp trap command.

If you want the SNMPQE and OSNMPD address spaces to be started automatically when the TCPIP address space is started, then include SNMPQE and OSNMPD in the AUTOLOG statement: 
AUTOLOG
  SNMPQE                      ; SNMP Query Engine
  OSNMPD                      ; SNMP Agent
ENDAUTOLOG
Parent topic: Step 1: Configure the SNMP agent