snmpconfig (command)


The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

components can act as managed systems by reporting information through SNMP to a managing system (master) on your network.

Setting up a component instance as a managed system involves configuring a local agent for the instance, specifying the SNMP versions that you want to use, and configuring traps.

For

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

and

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

instances, you cannot configure the SNMP service through a web interface, so you must use the CLI and the snmpconfig command.

SNMP traps

The macro unmigrated-inline-wiki-markup from Confluence is no longer available.

components support SNMPv1, SNMPv2c, and SNMPv3.

To use SNMP trap-based alerting, you must configure a server address to act as the recipient for all traps generated by the component instance. You must also define trap dispatching settings for each instance to follow when it sends alerts.

Traps must be sent using the same protocol level used by the recipient: v1, v2c, or v3.

Remote logging commands

Use the following commands to display SNMP service status, enable or disable the service, and perform other configuration tasks.

Commands for configuring the SNMP service

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*