IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Agent Installation Guides > IBM i Agent Installation Guide > Agent installation and configuration > Support for SSL communication with the Monitoring Agent for IBM i

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2


Configure the monitoring agent

Four environment variables have been introduced for SSL configuration on the agent.

You can set the KDEBE_OS400_APP_ID and KDEBE_PROTOCOL variables by editing the QAUTOTMP/KMSPARM(KBBENV) file. You can set the IP_PIPE and KDC_PORTSSL variables using the configuration screen provided using GO OMA, Option 4.

KDEBE_APPLICATIONID

Required for identifying the Application Identifier used to establish the SSL communication between the Monitoring Agent for IBM i OS and the monitoring server. The value for this variable depends on the Application Identifier name that is created using DCM. The default value is QIBM_ITM_KA4_AGENT for the Monitoring Agent for IBM i OS. If the default Application Identifier is not used, you must update the KDEBE_APPLICATIONID value in the KBBENV configuration file with the correct Application ID.

IP_SPIPE

Used to store the monitoring server's SPIPE Address. This can be either the DNS name or IP address. This value can be set using the configuration screen available from the main menu (GO OMA Option 4). You do not need to edit the KBBENV environment variable file for this variable.

KDC_PORTSSL

Used to store the monitoring server's SPIPE port number. This value can be set using the configuration screen available from the main menu (GO OMA Option 4). You do not need to edit the KBBENV environment variable file for this variable.

KDEBE_PROTOCOL

Used to set the SSL Version protocol that the agent computer uses to connect to the monitoring server computer.

KDEBE_PROTOCOL has the following characteristics:

  • KDEBE_PROTOCOL=SSL_VERSION_3 (SSL 3 only). This causes an override of the available cipher suites to preclude the use of AES.

  • KDEBE_PROTOCOL=SSL_VERSION_CURRENT (TLS with SSL 3 and 2 compatibility)

  • KDEBE_PROTOCOL=SSL_VERSION_2 (SSL 2, not recommended, weak) KDEBE_PROTOCOL=TLSV1_SSLV3 (TLS with SSL 3 compatibility)


Parent topic:

Support for SSL communication with the Monitoring Agent for IBM i

+

Search Tips   |   Advanced Search