IBM Tivoli Netcool/OMNIbus SNMP Writer Gateway: Reference Guide

More documents

Recommendations

Info

You can use the Gate.Reader.IducFlushRate property to specify the frequency (in seconds) at which the gateway reader requests updates from the ObjectServer using an Insert, Delete, Update, or Control (IDUC) communication protocol. The default value of the ObjectServer IDUC update interval is 60 seconds (as specified by the ObjectServer Granularity property). This default value is optimal for most systems. The default value of the Gate.Reader.IducFlushRate property is 0, which equates to the default ObjectServer update interval. This means that, using the default setting of 0 seconds for the IDUC flush rate and the default setting of 60 for the ObjectServer granularity, the gateway reader gets its updates at 60-second intervals. You can specify a value greater than 0 for the Gate.Reader.IducFlushRate. This makes the gateway reader run at a faster rate (higher granularity) than the ObjectServer, thus enabling the gateway to capture more detailed event changes in systems where the ObjectServer itself has high granularity settings. Note: When both the ObjectServer Granularity property and the Gate.Reader.IducFlushRate property are set to their default values, the gateway's ability to forward alert updates is affected. If the Gate.SNMP.ForwardUpdates property is set to TRUE in these conditions, the gateway will not be able to capture all alert updates. Forwarding alert updates The gateway can forward updates to alerts that it has previously sent to the ObjectServer. The default gateway setting is to forward only new alerts to the ObjectServer. To forward alert updates, you must specify a value of TRUE for the Gate.SNMP.ForwardUpdates property. In effect, this reduplicates alerts (as opposed to the ObjectServer's deduplication mechanism). Note: The gateway never forwards alert deletion, journal, or details information. Store-and-forward mode When the remote SNMP writer is no longer active, the gateway can be run in store-and-forward mode. This ensures that the ObjectServer and database writers can continue to run. When the gateway detects that the target SNMP writer is not present or is not functioning (usually because the writer is unable to write an alert), it switches into store-and-forward mode. In this mode, the gateway stores everything it would normally send to the database in a storage file with a .store suffix. The default storage file is $OMNIHOME/var/NCO_GATE_snmp_.store. When the gateway detects that the destination server is back on line, it switches into forward mode and sends the alert information held in the storage file to the destination server. After all of the alerts in the storage file have been forwarded, the gateway returns to normal operation. Store-and-forward mode only works when a connection to the SNMP writer has first been established, used, and then lost. If the destination server is not running when the gateway starts, store-and-forward mode is not triggered and the gateway shuts down. 22 IBM Tivoli Netcool/OMNIbus SNMP Writer Gateway: Reference Guide
If the gateway connects to the SNMP writer and a storage file already exists, the gateway forwards the contents of the file before it sends new alerts. To configure store-and-forward mode, set the Gate.SNMP.StoreAndForward property to TRUE and use the Gate.SNMP.StoreFile to specify a storage file. Restart the gateway to activate store-and-forward mode. To deactivate store-and-forward mode, set the Gate.SNMP.StoreAndForward property to FALSE and restart the gateway. Note: Store-and-forward mode will not work if the gateway is using the User Datagram Protocol (UDP) transport protocol. UDP communication is one-way only, so the gateway cannot detect if the target server to which it is trying to forward events is running. If you specify UDP as the transport protocol and you also activate store-and-forward mode, the storage file will not be created. To use store-and-forward mode, you must use the Gate.SNMP.Protocol property to specify the Transmission Control Protocol (TCP) transport protocol. Hash table cache The gateway uses a hash table cache to store details of tables that must be transferred from one ObjectServer to another. The cache aids performance optimization by providing the gateway with an in-memory summarized view of the contents of the ObjectServers to which it is linked. Using a hash table cache means that the gateway does not have to query an ObjectServer to check for the existence of an event, or the Serial value or Tally value of an event. Instead, it can check the cache of the target ObjectServer. The main function of the cache is to facilitate insert operations in Journal and Details tables. When a journal or detail is forwarded for insertion into a target ObjectServer, the gateway writer needs to know the corresponding Serial value in the target ObjectServer. This information is found in the cache. It is also used for any other tables specified using the table replication definition table. You can control the size of the hash table cache using the Gate.CacheHashTblSize property. By default, the size of the hash table cache is 5023 elements (rows). This can be increased if the status table has a large number of rows (for example, in excess of 20,000). Note: To maximize efficiency, you should specify a prime number for the Gate.CacheHashTblSize property. Process Agent control The gateway can be run under Process Agent (PA) control. The Gate.PAAware property specifies whether or not the gateway is PA-aware. The Gate.PAAwareName property specifies which PA is running the gateway. Note: These properties are maintained automatically by the PA server and provide information only. Do not manually change the values of these properties. Error handling You can troubleshoot problems with the gateway by consulting error messages. To help you do this, the gateway has configurable error handling. IBM Tivoli Netcool/OMNIbus SNMP Writer Gateway 23
Page 1: IBM ® Tivoli ® Netcool/OMNIbus SN
Page 4 and 5: Notice Before using this informatio
Page 6 and 7: iv IBM Tivoli Netcool/OMNIbus SNMP
Page 8 and 9: Table 1. Document modification hist
Page 10 and 11: viii IBM Tivoli Netcool/OMNIbus SNM
Page 12 and 13: Table 3. Summary (continued) Requir
Page 14 and 15: Console mode To install the gateway
Page 16 and 17: v “Advanced properties” on page
Page 18 and 19: Table 6. Generic gateway properties
Page 20 and 21: Table 6. Generic gateway properties
Page 22 and 23: Table 7. Gateway-specific propertie
Page 28 and 29: Note: After the gateway has started
Page 30 and 31: This section describes the property
Page 34 and 35: AES encryption Error handling is pr
Page 36 and 37: Running the gateway Table 12. Encry
Page 38 and 39: Table 13. Error messages (continued
Page 40 and 41: Any references in this information
Page 42: 32 IBM Tivoli Netcool/OMNIbus SNMP

IBM Tivoli Netcool/OMNIbus SNMP Writer Gateway: Reference Guide

Create successful ePaper yourself

Delete template?

Save as template?