IBM Tivoli Netcool/OMNIbus SNMP Writer Gateway: Reference Guide

More documents

Recommendations

Info

Running the gateway Table 12. Encrytion key file command line options (continued) Command line option Description -k key Use this option to specify the key to be written out, expressed as hex digits. Note: This option bypasses automatic key generation. -h |-? Use this option to print the help information and exit Note: AES encryption is used as the initial encryption method for sensitive data. However, this does not mean that the data can be considered to be secure purely due to AES encryption; the security of the data depends on the restriction of access to the key file used for AES encryption. Access to this file is controlled using UNIX file permissions. Using encrypted data To use encrypted data, you must add the following line to the WRITER section of the configuration file: LOAD ENCRYPTION KEY FROM ’key_file_path’ USING ’AES’ Where key_file_path is the path to the file containing the encryption key. Running the ObjectServer in a secure mode When the gateway connects to the ObjectServer running in secure mode, it needs to authenticate with a user name and password. This user name and password can be encrypted using the nco_aes_crypt tool. To enable the encryption, the location of the key file must be specified at the beginning of the configuration file. This is followed by the AUTH_USER and AUTH_PASSWORD fields which contain the encrypted user name and password required for authentication. The following example shows the three fields that need to be added at the beginning of the configuration file when the ObjectServer runs in a secure mode: LOAD ENCRYPTION KEY FROM ’/HOME/72/solaris/omnibus/keyflie_name’ USING ’AES’; AUTH_USER ’@44:2yXgd6fp9q1Ey4sSAb2RibzA3+PpCZmhAZXo6nNdkvQ=@’; # encrypted_user_name AUTH_PASSWORD ’@44:mdyEb8VTh+2wALnNlR7dnGnxRZ3BkMOQbR5IgxLlHuc=@’; # encrypted_password This topic describes how to run the gateway. On Windows operating systems, you can run the gateway as a service. To start the gateway on UNIX and Linux operating systems, run the following command: $OMNIHOME/bin/nco_g_snmp To start the gateway as a process on Windows operating systems, run the following command: 26 IBM Tivoli Netcool/OMNIbus SNMP Writer Gateway: Reference Guide
Error messages %OMNIHOME%\bin\nco_g_snmp.exe To start the gateway as a service on Windows operating systems, use the following steps: 1. Register the gateway with the Service Control Manager. 2. If the gateway and the ObjectServer are running on the same host, run the following command: %OMNIHOME%\bin\nco_g_snmp.exe -install -depend NCOObjectServer 3. If the gateway and the ObjectServer are running on different hosts, run the following command: %OMNIHOME%\bin\nco_g_snmp.exe -install 4. Start the gateway using the Microsoft Services Management Console. Error messages provide information about problems that have occurred during the operation of the gateway. You can use the information that they contain to resolve such problems. The following table describes the error messages that the gateway generates: Table 13. Error messages Error Description Action Failed to send trap for The gateway failed to Verify that the endpoint is SNMP trap forwarder with forward a trap for the reason available and reachable. error error. Retrying... specified in the error Check for any intervening message. It is trying to re-send the trap. firewalls. Failed to create session The gateway was unable to Verify that the endpoint is for SNMP trap forwarder. reconnect to the endpoint still available and that there after a previous disconnection. is no intervening firewall. Failed to initialize The gateway could not Verify that the properties file gateway properties. initialize the gateway has correct permissions. properties. Check the values set in the properties file. Invalid value specified The transport protocol field Specify the value of the for PROTOCOL attribute. is incorrectly specified and Gate.SNMP.Protocol property Ignored and using UDP. the gateway is defaulting to the UDP protocol. as either UDP or TCP. Node index not found for The gateway was unable to Verify that there is a ’Node’ SNMP trap forwarder find a column entitled 'Node' = ’@’ entry in in the configured table. the mapping file that you are using. oid property has an The Gate.SNMP.OID property Ensure that the invalid value; must be a must be specified as an Gate.SNMP.OID property is string or a field object identifier (OID) string specified as an OID string or reference. or a reference to the node group field. as @NodeGroup. Snmpversion property has The SNMP writer version is Specify the value of the unknown SNMP version incorrectly specified. Gate.SNMP.SNMPVersion specified in SNMP trap forwarder. Please set it to12or3 property as either 1, 2, or3. IBM Tivoli Netcool/OMNIbus SNMP Writer Gateway 27
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 32 and 33: You can use the Gate.Reader.IducFlu
Page 34 and 35: AES encryption Error handling is pr
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?