Supply the NNMi administrator username to run the script. This script requires the NNMi administrator username unless you use an nnm.properties file. See the nnm.properties.4 reference page for more information.

Supply the NNMi administrator password to run the script. This script requires the NNMi administrator password unless you use an nnm.properties file. See the nnm.properties.4 reference page for more information.

Show the properties associated with Trap Service and their current values.

Start the Trap Service. NOTE this command only starts the TrapServer which is running in JBoss. Use nnmtrapreceiver to start the standalone TrapReceiver.

Stop the Trap Service. NOTE this command only stops the TrapServer which is running in JBoss. If the TrapReceiver is not stopped as well, your server will continue to receive and cache traps. Use nnmtraprecevier to stop the standalone TrapReceiver.

Cause Trap Service to read the filter configuration files.

Print out the filter configuration and the blocking caches that the Trap Service creates.

Reset the blocking caches in the Trap Service.

The name of a user with system or administrator roles.

The password for the specified user.

Set values for properties associated with Trap Service.

Set IP address on which the Trap Service listens for traps. By default it listens on all interfaces.

Set Trap Service to listen on all interfaces.

Set the port on which the Trap Service listens for traps. By default this is 162.

Set the size of socket buffer, in kilobytes, on which Trap Service listens for traps.

Block all incoming SNMP v1 and v2 traps, forwarding only v3 traps. Disabled by default.

Accept every incoming SNMP trap, including v1 and v2. This is the default.

Sets the IP Address to replace the source address of a trap if the source address is a loopback address before forwarding the trap.

Resets the loopback override address. When this options is executed, the user supplied loopback override address will be removed. In this case, NNM chooses one of the server's addresses as the loopback override address.

Block traps based on filter and threshold configurations.

Do not block traps.

Set the rate in traps/sec at which trap sources or trap oids are blocked.

Set the rate in traps/sec at which blocked trap sources or trap oids are unblocked. This rate should be less than or equal to the thresholdRate.

Set the rate in traps/sec at which all incoming traps are blocked.

Set the rate in traps/sec at which all incoming traps are unblocked. This rate should be less than or equal to the overallThresholdRate

Set monitoring window size in seconds. This determines the window size in which trap sources are monitored. This means that whenever this time expires the counters keeping track of incoming traps are reset and a new window is started.

Set the time period in seconds after which the list of blocked traps and sources are updated.

Set the time period in seconds after which the list of blocked traps and sources are reported in the trapanalytics log file under the NNM_LOG directory. This is also the time period after which a trap storm incident is generated, in case a trap storm occurs and the overallThresholdRate is violated.

Set the minimum number of traps to be received from a source before it is considered for blocking. Also the minimum number of the same trap received before that trap is considered for blocking.

Set the number of nosiest sources to monitor at any given time. These will be the sources that are sending the most traps as well as the traps that occur most frequently. This information is reported in the trapanalytics log file in the NNM_LOG directory.

Set the maximum number of traps that can be held in the queue that writes traps to the database.

Set the maximum number of traps that can be held in the queues for each stage of the trap pipeline.

Set the maximum size, in MB, for one file in the trap database. When the file size reaches this value a rollover happens.

Set the maximum number of files in the trap database.

Enable or disable hosted object trap storm detection and suppression.

If a hosted object's trap rate is greater than this threshold in seconds, its traps will be suppressed.

The mode that the trap logger will operate with, valid values are: OFF, CSV, TXT, BOTH. Default value: CSV

OFF: Turns off all trap logging
CSV: Traps will be logged in a CSV format
TXT: Traps will be logged in a txt format similiar to trapd.log
BOTH: Traps will be logged in both formats

If true, traps will be logged in a gz compression, Default: false

Maximum size in MB that the trap log files will grow to before being rolled archived to a .old file. Only 1 .old file is retained for each log format. Defaul: 5MB

Maximum number of attempts the trap logger will try to roll a log file internally. Default: 1

Time in seconds the trap logger will wait before writing traps to the filesystem. Defult: 6 seconds

Maximum number of traps that will be written to the filesystem during each interval. Default: 256

Set the port the TrapReceiver will monitor for connections from JBoss. Default: 5447

Set the maximum amount of memory in bytes each JMS queue can consume, this value must be more than jms-page. Default: 128MB (134217728)

Set the maximum file size in bytes for JMS queue pages, this value must be more than 1,048,576 and less than jms-memory. Default: 10MB (10485760)

Set the JMS message TTL in ms. Must be a non-negative long. This is the amount of time that traps will be cached by the TrapReceiver. If JBoss is down for longer than this time, data will be lost. Default: 5 Minutes (300000)

Set the time delta in ms, to use when replaying traps during startup after a failover. Must be a non-negative long. A value of zero guarantees no duplicate data, however a value of zero may lead to lost data. Default: 10 Seconds (10000)

Persist the current properties so that on future restarts these values will be used.

If you are persisting properties in a HA or application failover environment, HP suggests stopping and starting the TrapReceiver on the inactive server to ensure that both the active and inactive nodes are using the same properties.