Configuration worksheet for communication protocols if the hub monitoring server is on a distributed system

Edit online

Fill out the following communication protocols worksheet if you plan to put your hub monitoring server on a distributed system.

For information about general requirements for using the TCP/IP communication protocols, see Requirements for TCP/IP communication protocols.

Table 1. Configuration worksheet for communication protocols if the hub monitoring server is on a distributed system
Summary for complex table
Value	Description	Value for your configuration
Communication protocols for a monitoring server on a distributed system You specify the communication protocols for the monitoring server in Configure the Tivoli Enterprise Monitoring Server.	You must plan communication protocols for a monitoring server on a distributed system to send data to other Tivoli Tape Optimizer Monitoring Agent components, such as remote monitoring servers and portal servers. Choose from the following protocols: IP.PIPE Uses the TCP/IP protocol for underlying communications. IP.UDP Also a TCP/IP protocol. Uses the User Datagram Protocol (UDP). IP.SPIPE Secure IP.PIPE protocol. SNA Uses the VTAM^® SNA Advanced Program-To-Program Communications (APPC).	Protocol 1 Highest-priority communication protocol. The IP.PIPE or IP.SPIPE protocol is generally the best choice for Protocol 1 in firewall environments. These protocols enable the monitoring server to communicate with the monitoring agent on z/OS and with other components on other systems, even if the components are running behind firewalls. Protocol 2 Protocol 3
IP.PIPE or IP.SPIPE Settings (See Configuration worksheet if the hub monitoring server is on a distributed system.)
Host name or IP address	Host name or IP address of the system where the monitoring server is installed.
Port number	Listening port for the hub monitoring server to use in communicating with the monitoring agent. The default port number is 1918 for IP.PIPE and 3660 for IP.SPIPE. Note: The same TCP/IP port number must be used for every monitoring server in the enterprise. Also, make sure that the monitoring server well-known port is not on the TCP/IP reserved port list.
IP.UDP Settings (See Configuration worksheet if the hub monitoring server is on a distributed system.)
Host name or IP address	Host name or IP address of the system where the monitoring server is installed.
Port or pool number	Listening port for the hub monitoring server to use in communicating with the monitoring agent, or the pool from which the port is to be selected. The default number is 1918.
SNA Settings
Network Name	SNA network identifier for your location.
LU name	LU name for the monitoring server. This LU name corresponds to the Local LU Alias in your SNA communications software.
LU 6.2 logmode	Name of the LU6.2 logmode. The default value is CANCTDCS.
TP name	Transaction program name for the monitoring server. The default value is SNASOCKETS.
Communication protocols for the monitoring agent You specify the communication protocols for the monitoring agent in “Step 5. Configure the monitoring agent” on page 66.	You must plan communication protocols for the monitoring agent to send data to the monitoring server. Tip: Make sure that at least one of the protocols you specify for the monitoring agent corresponds to a protocol specified for the agent's primary monitoring server. Choose from the following protocols: IP.PIPE Uses the TCP/IP protocol for underlying communications. IP.UDP Uses the TCP/IP User Datagram Protocol (UDP). IP6.PIPE Uses the TCP/IP protocol for underlying communications. IPV6 must be installed and operational. IP6.UDP Uses the TCP/IP User Datagram Protocol (UDP). IPV6 must be installed and operational. IP.SPIPE Secure IP.PIPE protocol. The z/OS system must be V1R7 or higher. IP6.SPIPE Secure IP.PIPE protocol. IPV6 must be installed and operational, and the z/OS system must be V1R7 or higher. SNA.PIPE Uses the VTAM SNA Advanced Program-To-Program Communications (APPC).	Protocol 1 Highest-priority communication protocol. IP.PIPE, IP.SPIPE, IP6.PIPE, or IP6.SPIPE is generally the best choice for Protocol 1 in firewall environments. These protocols enable the monitoring agent on z/OS to communicate with the monitoring server on a distributed system, even if both components are running behind firewalls. Protocol 2 Protocol 3
Language locale	Specify a numeric value (1-36) representing the language and region. For example, specify 1 for United States English. For a list of the language locale values, press F1 (Help) in the Configuration Tool panel where the prompt is displayed.
TEMS name (node ID)	Node ID of the hub monitoring server. Note that the TEMS name, or node ID, is generally not the same as the host name. It is an arbitrary name assigned during Tivoli Enterprise Monitoring Server configuration. Find the node ID as follows, depending on where the monitoring server is installed: On Windows systems, you can find the TEMS name in Manage Tivoli Monitoring Services. Right-click Tivoli Enterprise Monitoring Server and select Browse Settings, and look for the value of CMS_NODEID. On Linux and UNIX systems, you can find the value of CMS_NODEID in the KBBENV file located in the $itmhome/tables/cms_name subdirectory.
IP.* or IP6.* protocols
Host name	Host name of the system where the monitoring agent is installed. To obtain the host name, enter TSO HOMETEST at the command line of the z/OS system where the monitoring agent is installed. If the z/OS domain name resolver configuration specifies a search path that includes the target domain suffix, specify only the first qualifier of the host name. (Example: sys is the first qualifier of the fully qualified host name sys.ibm.com.) Otherwise, specify the fully qualified host name.
Address	IP address of the system where the monitoring agent is installed. To obtain the IP address, enter TSO HOMETEST at the command line of the z/OS system where the monitoring agent is installed.
Started task	Started task name of the TCP/IP server. You can specify * to allow the IP stack to dynamically find the TCP/IP image. * is the suggested value for the started task.
Network interface list	A list of network interfaces for the monitoring agent to use. This parameter is required for sites that are running more than one TCP/IP interface or network adapter on the same z/OS image. Setting this parameter allows you to direct the monitoring agent to connect to a specific TCP/IP local interface. Specify each network adapter by the host name or IP address to be used for input and output. Use a blank space to separate the entries. If your site supports DNS, you can enter IP addresses or short host names. If your site does not support DNS, you must enter fully qualified host names. If you specify an interface address or a list of interface addresses, the Configuration Tool generates the KDEB_INTERFACELIST parameter in the KHLENV member of the `&rhilev.&rtename`.RKANPARU library.
Address translation	By default, Ephemeral Pipe Support (EPS) is enabled automatically to allow IP.PIPE connections to cross a (network address) translating firewall. This feature obviates the need for a broker partition file (KDC_PARTITIONFILE=KDCPART). If you specifically want to disable EPS, specify Y for Address translation.
Partition name	If you specified Y for Address translation, specify the partition name that identifies the monitoring agent relative to the firewall used for address translation.
SNA settings
VTAM applid prefix	Specify the applid prefix to create the VTAM node and applids required by the monitoring agent. These applids begin with a prefix, and end with a unique applid value. The applids are contained in the VTAM major node. The default prefix is CTDRW.
Communication protocols for the portal server You specify the communication protocols for the portal server in Configure the Tivoli Enterprise Portal.	You must plan communication protocols for the portal server to receive data from the monitoring server. Choose from the following protocols: IP.PIPE Uses the TCP/IP protocol for underlying communications. IP.UDP Uses the TCP/IP User Datagram Protocol (UDP). IP.SPIPE Secure IP.PIPE protocol. SNA.PIPE Uses the SNA Advanced Program-To-Program Communications (APPC).	Protocol 1 Highest-priority communication protocol. The IP.PIPE or IP.SPIPE protocol is generally the best choice for Protocol 1 in firewall environments. These protocols enable the portal server to communicate with a monitoring server on another system, even if both components are running behind firewalls. Protocol 2 Protocol 3
IP.* settings (See Configuration worksheet if the hub monitoring server is on a distributed system.)
Host name or IP address	Host name or IP address of the hub monitoring server.
Port number	Same port number you specified for the hub monitoring server.
SNA settings
Network name	SNA network identifier for your location.
LU name	LU name for the monitoring server. This LU name corresponds to the Local LU Alias in your SNA communications software.
LU 6.2 logmode	Name of the LU6.2 logmode. The default value is CANCTDCS.
TP name	Transaction program name for the monitoring server. The default value is SNASOCKETS.