Previous topic |
Next topic |
Contents |
Contact z/OS |
Library |
PDF
EZZ6321I z/OS Communications Server: IP Messages Volume 4 (EZZ, SNM) SC27-3657-01 |
|
EZZ6321I agent_job could not find configuration
file - using public community name ExplanationThis SNMP agent could not find a configuration file to use as its source for user, view, access list, and community name definitions, and the -c agent start parameter was not specified. The agent first searches for an SNMPD.CONF file. If no SNMPD.CONF file is found, then the agent searches for a PW.SRC file. See the TCP/IP configuration data sets information in z/OS Communications Server: IP Configuration Reference for a description of the search order used to find an SNMPD.CONF and a PW.SRC file. Because the agent could not find a configuration file, and the -c start parameter was not specified, the agent is using community-based security and it has defined a default, well-known community name of public. Any SNMP requests that are received by the agent that use a community name of public will be permitted to access all SNMP management data. In
the message text:
System actionThe SNMP agent continues initialization. Operator responseContact the system programmer. System programmer responseIf you want to restrict access to SNMP management data, provide either an SNMPD.CONF or PW.SRC configuration file to the SNMP agent. See the SNMP information in z/OS Communications Server: IP Configuration Reference for information about these configuration files. User responseNot applicable. Problem determinationSee the system programmer response Sourcez/OS® Communications Server TCP/IP: SNMP Agent ModuleEZASNAC3 Routing code8,10 Descriptor code12 AutomationThis message is written to the system console and to the syslog daemon. This message is a good candidate for automation. Automation can allow you to be informed when the SNMP agent cannot find a configuration file. Example
|
Copyright IBM Corporation 1990, 2014
|