Update Internet Protocol in runtime environment (PARMGEN)

Edit online

Update the Internet Protocol (IPv4, IPv6) that is used for communication in your runtime environment using PARMGEN.

Before you begin

To update the communication used between the components in an OMEGAMON runtime environment, you must define the communication protocol and ports for each component. You might also have to update the host setting and the list of network interfaces. This topic describes how to modify the settings for the Internet Protocol that is used, focusing on the migration from IPv4 to IPv6.

Before you can update your OMEGAMON runtime environment from IPv4 to IPv6, your mainframe environment must be enabled for IPv6. You must have the name of the IPv6-enabled z/OS host and IP address available. Your site might reconfigure an existing host from IPv4 to IPv6, or it might add a new host with a different host name.

If you are using distributed components, your distributed environment must also be configured to communicate using IPv6. IPv6 communication over IPv4-only networks is not supported.
Note: If a component needs to communicate using IPv6 with some components and IPv4 with others, the host must be enabled for dual-stack operation. For more information, see IBM Tivoli Monitoring Installation and Setup Guide: Choose between IPv6 and IPv4.
Note: IPv6 is not supported for sending EIF events from the hub monitoring server or from monitoring agents.
To update your configuration, you must modify the settings for the runtime environment using Configuration Manager or PARMGEN. This task describes this process using PARMGEN.
Note: If you use Configuration Manager, see Update Internet Protocol in runtime environment (Configuration Manager).
Related links:

About this task

The communication protocol and ports for any monitoring server and all monitoring agents must be the same for communication to be successful.

If you are updating the communication protocol for the runtime environment or plan to use a port number that is different from the default port for the protocol, you must update the values for all communication protocols and ports specified within the profile. You might also have to update the host and the list of network interfaces.

To change the communication protocol that your runtime environment uses, you modify the communication protocol setting for any monitoring servers and the monitoring agents. You might also have to update the name of the host, if it is different; and you can also modify the ports that are used, if you want to use a port other than the default port for the protocol.

You will use the following parameters when updating the Internet Protocol for your runtime environment:
Table 1. Parameters for setting IP protocol using PARMGEN
Component Parameter Description
Tivoli Enterprise Monitoring Server KDS_TEMS_TCP_HOST Specifies the TCP/IP host name or IP address of the z/OS system where themonitoring server is installed.
KDS_TEMS_COMM_PROTOCOLn Communication protocol to be supported by the Tivoli Enterprise Monitoring Server, where n corresponds to a number between 1 and 7 to indicate the priority sequence for the communication protocols.
IPv4 ports: Well-known ports for the monitoring server over IPv4.
IPv6 ports: Well-known ports for the monitoring server over IPv6.
Remote monitoring server KDS_HUB_TCP_HOST Specifies the TCP/IP host name or IP address of the z/OS system where the hub monitoring server is installed. This parameter applies only to a remote monitoring server that uses TCP/IP for communications.
IPv4 ports: Well-known ports for the hub monitoring server over IPv4, specified during configuration of a remote monitoring server.
IPv6 ports: Well-known ports for the hub monitoring server over IPv6, specified during configuration of a remote monitoring server.
Monitoring agents Kpp_TEMS_TCP_HOST Specifies the TCP/IP host name or IP address of the z/OS system of the agent's primary monitoring server.
Kpp_AGT_COMM_PROTOCOLn Communication protocol for the connection between the monitoring agent and the Tivoli Enterprise Monitoring Server, where n corresponds to a number between 1 and 7 to indicate the priority sequence for the communication protocols.
IPv4 ports: Well-known ports for the monitoring agents over IPv4.
IPv6 ports: Well-known ports for the monitoring agents over IPv6.
Network interface lists IPv4 communication: Specifies lists of network interfaces for the monitoring server and monitoring agent to use for IPv4 communication, respectively.
IPv6 communication: Contains a list of interface addresses in the order for which these interface addresses should be discovered and used for IPv6 communication.
Tip: Configuration Manager simplifies the process of configuring communication protocols and ports by offering an easy way to set all components to the same values, rather than setting parameters individually for each component. If you are a PARMGEN user, consider moving to Configuration Manager.

The following procedure describes how to change the IP protocol, such as from IPv4 to IPv6, for your runtime environment using PARMGEN.

Procedure

  1. From the Workflow - Primary Option Menu, select option 2, Customize PARMGEN configuration profiles.
    The Customize PARMGEN Configuration Profile Members (KCIP@PG6) panel is displayed.
  2. Select option 1 to edit the runtime environment (RTE) configuration profile.
    The profile member is displayed.
  3. Update the settings for the monitoring server to use to communicate with the other components, as follows:
    1. Assign the communication protocol as the first priority protocol. The following example sets the first priority protocol to use the IP6.SPIPE communication protocol (the TCP/IP protocol that supports Secure Sockets Layer communications over IPv6):
      KDS_TEMS_COMM_PROTOCOL1         IP6SPIPE  * Secure TCP over IPv6
    2. Specify the port number using the corresponding parameter for the specified protocol. The following example sets the port for the monitoring server for the IP6.SPIPE communication protocol; in this case, it is the default port number:
      KDS_TEMS_TCP_PIPE6S_PORT_NUM    3660      * Secure IP.PIPE for IPv6
      Important: For all port parameters that are not related to the defined communication protocol, remove the parameter value, if defined. Otherwise, parameter validation will fail.
    3. If this monitoring server is a remote monitoring server, specify the port number of the hub monitoring server by using the corresponding parameter for the specified protocol:
      KDS_HUB_TCP_PIPE6S_PORT_NUM     3660      * Secure IP.PIPE for IPv6
    4. Specify the host.
      Note: If you are migrating from IPv4 to IPv6, the host must be IPv6-enabled. Your site might reconfigure the existing host to enable IPv6, or it might add a new host with a different host name or IP address.
      KDS_TEMS_TCP_HOST               "SYSA"
    5. Update the network interface list. If you are migrating from IPv4 to IPv6, set the interface list parameter that is used for IPv4 communication to the hyphen (-) character:
      KDS_TEMS_TCP_KDEB_INTERFACELIST "-"
  4. Update the settings for each of the monitoring agents to use to communicate with the other components, as follows:
    1. Assign the communication protocol as the first priority protocol for each of the agents. The following example sets the first priority protocol to use the IP6.SPIPE communication protocol:
      Kpp_AGT_COMM_PROTOCOL1          IP6SPIPE  * Secure TCP over IPv6
    2. Specify the port number using the corresponding parameter for the specified protocol:. The following example sets the well-known port for the monitoring server for the IP6.SPIPE communication protocol.
      Kpp_TEMS_TCP_PIPE6S_PORT_NUM    3660      * Secure IP.PIPE for IPv6
    3. Specify the host.
      Kpp_TEMS_TCP_HOST               "SYSA"
    4. Update the network interface list. If you are migrating from IPv4 to IPv6, set the interface list parameter that is used for IPv4 communication to the hyphen (-) character:
      Kpp_AGT_TCP_KDEB_INTERFACELIST  "-"
  5. Save the changes and return to the Customize PARMGEN Configuration Profile Members panel.
  6. If you are using or migrating to IPv6 communication, update the list of interface addresses for IPv6 communication as follows:
    1. Select option 4 on the Customize PARMGEN Configuration Profile Members panel to customize the WCONFIG data set.
    2. Specify the list of interface addresses for IPv6 communication in the KDEB_INTERFACELIST_IPV6 embed override parameter by editing embed override member WCONFIG(KDS$PENV) for the monitoring server and WCONFIG(KAG$PENV) for the monitoring agents. By default, this parameter is commented out; you must remove the asterisk (*) that precedes the parameter name to enable the parameter setting. 
      KDEB_INTERFACELIST_IPV6=\
(2002:930:9b04:305:9:48:133:98)\
(2002:930:9b04:305:9:48:133:100)
    3. Save the changes and return to the Customize PARMGEN Configuration Profile Members panel.
  7. Return to the Workflow - Primary Options Menu panel.
  8. Regenerate the runtime members and jobs, as follows:
    1. Select Create the RTE members and jobs.

      The $PARSE/$PARSESV: Create the RTE Members and Jobs (KCIP@PR1) panel is displayed.

    2. Select option 1 to submit the $PARSE job (or the $PARSESV job, if variables are enabled).
    3. Return to the Workflow - Primary Options Menu panel.
  9. Copy the runtime members from the work libraries to the production libraries, as follows:
    1. Select Submit batch jobs to complete PARMGEN setup from the menu.

      The Submit Batch Jobs To Complete PARMGEN Setup (KCIP@SUB) panel is displayed.

    2. Optional: Select option 11 and submit the KCIJPCPR job to back up the production libraries.
    3. Select option 12 and submit the KCIJPW2R job (or the KCIJPW1R job) to copy the work libraries to the production libraries.
  10. Recycle the started tasks for the monitoring server and the monitoring agents.