In UI and CLI, we have only monitoring options for SNMP. We also should be able to enable and disable the SNMP protocol. And we should be able to set the following attributes:
nsSNMPOrganization nsSNMPLocation nsSNMPContact nsSNMPDescription
The examples and documentation from the Admin guide:
20.10.2. Enabling and Disabling SNMP Support
By default, the SNMP protocol is enabled in Directory Server and, after configuring the subagent, you can use it. To enable or disable SNMP in an instance, set the nsSNMPEnabled parameter to on or off. For example, to disable SNMP in a Directory Server instance: # ldapmodify -D "cn=Directory Manager" -W -p 389 -h server.example.com -x dn: cn=SNMP,cn=config changetype: modify replace: nsSNMPEnabled nsSNMPEnabled: on
20.10.3. Setting Parameters to Identify an Instance Using SNMP
Directory Server provides the following attributes which help identifying instances using SNMP: nsSNMPOrganization nsSNMPLocation nsSNMPContact nsSNMPDescription For details about the parameters, see their descriptions in the cn=SNMP section in the Red Hat Directory Server Configuration, Command, and File Reference. For example, to the set the nsSNMPLocation parameter to Munich, Germany: # ldapmodify -D "cn=Directory Manager" -W -p 389 -h server.example.com -x dn: cn=SNMP,cn=config changetype: modify replace: nsSNMPLocation nsSNMPLocation: Munich, Germany
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.2
Metadata Update from @mreynolds: - Issue priority set to: minor - Issue set to the milestone: 1.4.3 (was: 1.4.2)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3511
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix - Issue status updated to: Closed (was: Open)