JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Solaris System Management Agent Developer's Guide
search filter icon
search icon

Document Information

Preface

1.  Introduction to the System Management Agent

2.  Creating Modules

3.  Data Modeling

4.  Storing Module Data

5.  Implementing Alarms

Refresh Intervals

Asynchronous Trap Notification

Thresholds for Sending Traps

demo_module_4 Code Example for Alarms

Reading Data From the demo_module_4.conf Configuration File

Using SNMP_CALLBACK_POST_READ_CONFIG in demo_module_4

Generating Traps in demo_module_4

6.  Deploying Modules

7.  Multiple Instance Modules

8.  Long-Running Data Collection

9.  Entity MIB

10.  Migration of Solstice Enterprise Agents to the System Management Agent

A.  SMA Resources

B.  MIBs Implemented in SMA

Glossary

Index

Thresholds for Sending Traps

In the System Management Agent, any configurable data can be stored in a module-specific configuration file. Data from this file can be loaded into the module at the time of module initialization. Data is read from the configuration files into a module by registering a callback function to be called whenever an interesting token is encountered.

register_config_handler("demo_module_4", "threshold_loadavg1",
read_load_thresholds, NULL, NULL);

In this example demo_module_4, whenever a threshold_loadavg1 token is read by the agent in the demo_module_4.conf file, the read_load_thresholds() function is called, with token name and value as arguments. The read_load_thresholds() function stores the token value in appropriate variables and uses these thresholds to determine alarm conditions. For more information on the register_config_handler APIs, see the documentation in /usr/sfw/doc/sma_snmp/html/group__read__config.html.