SMC Applicability Tool

Transcription

1 z/os Communications Serer SMC Applicability Tool Version2Release1

2 Note: Links to related publications are from original documents and might not work. The links to publications are included for reference purposes only.

3 Contents Tables IP System Administrator's Commands VARY TCPIP command VARY command: TCP/IP address space VARY TCPIP,,SMCAT Index iii

4 i SMC Applicability Tool

5 Tables 1. Serers or address spaces that support the MVS VARY TCPIP command Functions that support the VARY TCPIP command

6 i SMC Applicability Tool

7 IP System Administrator's Commands VARY TCPIP command Use the VARY TCPIP command from the MVS operator console to display help for a supported command or to control some functions of the address space that corresponds to the started procedure name that was specified on the command. The abbreiated ersion of the command is the letter V. This is the general format of the VARY command: Vary TCPIP, procname, parameter procname The name of the member in a procedure library that was used to start the serer or address space. You can omit the procname parameter when you direct the command to a TCP/IP stack address space and only one TCP/IP stack is currently actie. parameter Any of the parameters that are alid for the serer. The following serers or address spaces support the MVS VARY TCPIP command. Not all serers support the same parameters. For further descriptions of the supported parameters, see Table 1. Table 1. Serers or address spaces that support the MVS VARY TCPIP command Serer or address space Main parameters Additional information TCP/IP address space DATTRACE, DROP, OBEYFILE, OSAENTA, PKTTRACE, PURGECACHE, SMCAT, START, STOP, SYNTAXCHECK, SYSPLEX See VARY command: TCP/IP address space TN3270E Telnet serer address space HELP, OBEYFILE, TELNET, LUNS See "VARY command: TN3270E Telnet serer address space" VARY command: TCP/IP address space The functions listed in Table 2 support the VARY TCPIP command when it is directed to a TCP/IP stack address space. Table 2. Functions that support the VARY TCPIP command Function Command DATTRACE "VARY TCPIP,,DATTRACE" DROP "VARY TCPIP,,DROP" OBEYFILE "VARY TCPIP,,OBEYFILE" OSAENTA "VARY TCPIP,,OSAENTA" PKTTRACE "VARY TCPIP,,PKTTRACE" 1

8 Table 2. Functions that support the VARY TCPIP command (continued) Function PURGECACHE SMCAT START or STOP SYNTAXCHECK SYSPLEX Command "VARY TCPIP,,PURGECACHE" VARY TCPIP,,SMCAT "VARY TCPIP,,START or VARY TCPIP,,STOP" "VARY TCPIP,,SYNTAXCHECK" "VVARY TCPIP,,SYSPLEX" VARY TCPIP,,SMCAT Use the VARY TCPIP,,SMCAT command to control the SMC Applicability Tool (SMCAT). Shared Memory Communications oer RDMA (SMC-R), introduced in z/os V2R1, proides optimized communications for qualifying TCP connections. You can use the SMCAT to ealuate TCP/IP network traffic and use the ealuation to plan for any potential use of SMC-R. To make the ealuation, you do not need to enable the SMC-R function on any system or enable the RoCE Express features. You can use SMCAT to monitor a TCP/IP stack for a set of configured destination IP addresses or subnets, and to proide a report in the job log for the TCP/IP stack. Enabling SMCAT does not modify any network flows for the TCP connections that are monitored. Use the VARY TCPIP,,SMCAT command to turn on or turn off the SMCAT. The report indicates the following information for TCP connections on that stack that use the specified destination IP addresses or subnets: The percentage of all TCP connections that are connected to one of the configured IP addresses that qualify for SMC communications. These TCP connections are considered eligible to use SMC communications. The percentage of the eligible connections that hae a workload pattern best suited for SMC communications. These eligible connections are considered well-suited connections. Connections that are short-lied and exchange a small amount of data are not well-suited for SMC communications. The percentage of all TCP workloads, measured in segments sent and receied, that flowed oer the SMC well-suited connections. A breakdown of the application send and receie sizes that are used by the well-suited connections. In general, the performance benefits of SMC ersus TCP increase because the application send and receie size increases. The report is generated at the end of the interal and contains the following sections: A TCP SMC traffic analysis for all matching connections section, containing data for all eligible TCP connections. All eligible TCP connections include connections that are not directly connected and those that are directly connected. This section indicates the total amount of workload that can use SMC communications with some network topology changes. For the eligible TCP connections that are not directly connected, network traffic between the hosts requires traersal of a router that is not supported by the SMC-R protocol. For the eligible TCP connections that are directly connected, network traffic between the hosts does not require traersal of any IP routers. 2 SMC Applicability Tool

9 Format A TCP SMC traffic analysis for matching direct connections section, containing data only for the eligible TCP connections that are directly connected. For the eligible TCP connections that are directly connected, network traffic between the hosts does not require traersal of any IP routers. This section indicates the amount of workload that can immediately use SMC communications after SMC enablement. This section is a subset of the TCP SMC traffic analysis for all matching connections section. An SMCAT Summary Report Export Area section, containing the alues from the application send and receie sizes in a format that can be exported to the SMCAT CPU saings estimate worksheet. This worksheet can be found at the Shared Memory Communications oer RDMA Reference Information site ( The SMCAT report is written as a multi-line WTO message to the TCP/IP stack job log by using routing code 11. To ensure that the report is not displayed on the consoles, your consoles must not be configured to receie routing code 11 messages. The IBM Health Checker for z/os Consoles, CNZ_Console_Routcode_11, can be actiated to determine whether any consoles receie routing code 11 messages. Guidelines: The TCP connections that meet the following requirements are considered eligible to SMC communications: The destination IP address of the TCP connection matches an SMCAT configured IP address or subnet. The TCP connections do not use IPSec or Fast Response Cache Accelerator (FRCA). When you consider workloads for SMC-R and select the IP address to be measured, consider that RoCE is an Ethernet based technology that imposes limits on the distance between exploiting hosts. The RoCE is typically deployed within a site but can be deployed across sites by using IBM System z Qualified Waelength Diision Multiplexer (WDM) products for Multi-site Sysplex and GDPS solutions to extend Ethernet LANs/VLANs up to 100 KM. When you hae many instances of hosts that proide similar workloads using similar application serers, consider measuring only a subset of the hosts and extrapolating the SMCAT results of your sample across your enterprise data center. You can authorize users to inoke the command by permitting user IDs for CONTROL access to the RACF profile name MVS.VARY.TCPIP.SMCAT. Vary TCPIP, procname, SMCAT, datasetname OFF Parameters procname The identifier of the TCP/IP address space. When the procname alue is not specified, only one TCP/IP address space can be started. If more than one TCP/IP address space is aailable and no procname alue is specified, the request fails with an error message. IP System Administrator's Commands 3

10 SMCAT Specify this parameter to turn on or turn off the analysis of TCP connections to determine whether the connections can potentially use the SMC function. datasetname The datasetname alue indicates that the SMCAT is turned on. The datasetname alue is the name of a data set that contains the SMCATCFG statement that specifies monitoring interal and the IP addresses or subnets to be monitored. The data set must be a cataloged and fully-qualified data set name that is specified without any quotation marks. The datasetname alue can be either a sequential data set or a member in a PDS. The datasetname alue cannot be a z/os UNIX file. See SMCATCFG input statement for a description of the contents of datasetname. If the tool is actie, the following error message is issued: EZZ0140I SMCAT COMMAND REJECTED - SMC APPLICABILITY TOOL ALREADY ACTIVE OFF Guideline: To modify an actie SMCAT datasetname configuration, the tool must be turned off and restarted with the modified configuration. Indicates that the SMCAT is turned off and a report is generated. If the tool is not actie, the following error message is issued: EZZ0141I SMCAT OFF COMMAND IGNORED - SMC APPLICABILITY TOOL NOT ACTIVE Tip: Consider capturing SMCAT reports during periods of time of interest. For example, capture the typical workloads during periods of steady state traffic that are representatie of the target hosts. SMCATCFG input statement The data set that is specified on the VARY TCPIP,,SMCAT command must contain an SMCATCFG statement. This statement proides the monitoring interal alue and the list of IP addresses or subnets whose TCP connections are to be monitored. Restriction: Only one SMCATCFG statement can be specified in the data set. Syntax SMCATCFG INTERVAL 60 INTERVAL minutes IPADDR ip4_address ip4_address/num_mask_bits ip6_address ip6_address/prefix_length Parameters SMCATCFG This is a configuration statement for the SMCAT. The data set can contain only one SMCATCFG statement. 4 SMC Applicability Tool

11 INTERVAL minutes Specifies the length of time in minutes of the monitoring interal that collection of data is done before the results are reported. Valid alues are in the range The default alue is 60 minutes. IPADDR Specifies a list of 32-bit IP4 addresses in dotted decimal notation, 128-bit IP6 addresses that use colon hexadecimal notation and IP subnets. You can use the SMCAT to monitor TCP connections from this stack to these remote IP addresses and IP subnets. SMC-R is a peer to peer protocol, so it requires that both peers are capable and enabled for SMC-R communications. As a result, the IP addresses that are specified reflect peer hosts that are either capable of SMC-R or might be capable in the future. The following information shows key considerations in specifying the destination IP addresses to be monitored: When you use an IP4 subnet or IP6 prefix specification, all hosts on these networks are considered SMC-R eligible. If the specified network contains hosts that will be SMC-R capable and hosts that will not, the specification of indiidual IP addresses is recommended. If TCP connections from the local TCP/IP stack to a monitored peer use multiple IP addresses, all of the peer's IP addresses that might be used are specified. The peer's IP addresses include all IP addresses, static VIPAs, and dynamic VIPAs for that peer. Guideline: If the destination peer and the local host can communicate directly oer a shared subnet but the configured peer IP address is a static or dynamic VIPA in a different subnet, you must also configure the host IP address of the OSA used on the remote system to connect to the shared subnet. This ensures that connections to that VIPA oer the shared subnet will be counted as direct connections by SMCAT monitoring. If the SMCAT is turned on, you must specify at least one IP address or IP subnet. A limit of 256 combined indiidual IP addresses and IP subnets can be specified. The following alues are not allowed for IP4 addresses: Broadcast address ( ) Multicast addresses Default loopback address ( ) INADDR_ANY address ( ) The following alues are not allowed for IP6 addresses: Default loopback address (::1) IP4-mapped IP6 addresses IP4-compatible IP6 addresses Multicast addresses Unspecified address (::) Resered addresses Note: For information about the IP6 resered addresses, see Restrictions on IP6 addresses configured in the TCP/IP profile in z/os Communications Serer: IP Configuration Reference. IP System Administrator's Commands 5

12 Code examples VARY,,SMCAT command The following examples show the VARY command for the SMCAT. The following example shows the command for turning on the SMCAT and directing it to a TCP/IP address space named TCPPROC. In the example, the sequential data set USER99.TCPIP.SMCAT1 contains the SMCATCFG statement. VARY TCPIP,TCPPROC,SMCAT,USER99.TCPIP.SMCAT1 The following example shows the command for turning off the SMCAT. VARY TCPIP,TCPPROC,SMCAT,OFF SMCATCFG statement The following examples show the SMCATCFG statement in the input data set. The following example specifies one IP subnet to be monitored and uses the default interal of 60 minutes. SMCATCFG IPADDR /24 The following example specifies multiple IP subnets to be monitored and specifies an interal of 120 minutes. SMCATCFG INTERVAL 120 IPADDR C5::1:2:3:4/ /24 Report examples Configuration report The following example shows the report that is created by the SMCAT when it is turned on. This report proides the configuration parameters that are used for the monitoring interal. In the example, the tool monitors the TCP connections for stack TCPCS2 oer a 3 minute interal, for the list of IP addresses or subnets. EZD2040I TCP/IP CS V2R1 TCPIP Name: TCPCS2 SMC Applicability Configuration Parameters - 10/08/2014, 14:04:40.08 Interal: 3 minutes IP addresses/subnets being monitored / ::4/ / / ::1/ / ::3/ ::3/96 End of configuration parameters Report field descriptions: 6 SMC Applicability Tool

13 Interal The interal that is in effect when the SMCAT is turned on. IP Addresses/subnets being monitored A list of IP addresses or subnets that the SMCAT monitors. Interal report The following example shows the interal report that is created by the SMCAT when the monitoring interal expires or the tool is turned off. EZD2033I TCP/IP CS V2R1 TCPIP Name: TCPCS2 SMC Applicability Interal Report - 10/08/2014, 14:07:32.06 Configured Interal Duration: Actual Interal Duration: 3 minutes 3 minutes TCP SMC traffic analysis for all matching connections Includes connections not meeting direct connectiity requirements 20% of all TCP connections can use SMC (eligible) 90% of eligible connections are well-suited for SMC 22% of all TCP traffic (segments) is well-suited for SMC 20% of outbound traffic (segments) is well-suited for SMC 25% of inbound traffic (segments) is well-suited for SMC Interal Details: Total TCP Connections: 100 Total SMC eligible connections: 20 Total SMC well-suited connections: 18 Total outbound traffic (in segments) 1000 SMC well-suited outbound traffic (in segments) 200 Total inbound traffic (in segments) 500 SMC well-suited inbound traffic (in segments) 125 Application send sizes used for well-suited connections: Size # sends Percentage (<=1500): 20 36% 4K (>1500 and <=4k): 10 18% 8K (>4k and <= 8k): 4 7% 16K (>8k and <= 16k): 5 9% 32K (>16k and <= 32k): 10 18% 64K (>32k and <= 64k): 5 9% 256K (>64K and <= 256K): 2 4% >256K: 0 0% Application receie sizes used for well-suited connections: Size # recs Percentage (<=1500): 10 33% 4K (>1500 and <=4k): 5 17% 8K (>4k and <= 8k): 3 10% 16K (>8k and <= 16k): 3 10% 32K (>16k and <= 32k): 5 17% 64K (>32k and <= 64k): 2 7% 256K (>64K and <= 256K): 2 7% >256K: 0 0% IP System Administrator's Commands 7

14 TCP SMC traffic analysis for matching direct connections Connections meeting direct connectiity requirements 15% of all TCP connections can use SMC (eligible) 93% of eligible connections are well-suited for SMC 15% of all TCP traffic (segments) is well-suited for SMC 15% of outbound traffic (segments) is well-suited for SMC 14% of inbound traffic (segments) is well-suited for SMC Interal Details: Total TCP Connections: 100 Total SMC eligible connections: 15 Total SMC well-suited connections: 14 Total outbound traffic (in segments) 1000 SMC well-suited outbound traffic (in segments) 150 Total inbound traffic (in segments) 500 SMC well-suited inbound traffic (in segments) 70 Application send sizes used for well-suited connections: Size # sends Percentage (<=1500): 15 37% 4K (>1500 and <=4k): 7 17% 8K (>4k and <= 8k): 3 7% 16K (>8k and <= 16k): 4 10% 32K (>16k and <= 32k): 8 20% 64K (>32k and <= 64k): 3 7% 256K (>64K and <= 256K): 1 2% >256K: 0 0% Application receie sizes used for well-suited connections: Size # recs Percentage (<=1500): 8 38% 4K (>1500 and <=4k): 3 14% 8K (>4k and <= 8k): 2 10% 16K (>8k and <= 16k): 2 10% 32K (>16k and <= 32k): 4 20% 64K (>32k and <= 64k): 1 5% 256K (>64K and <= 256K): 1 5% >256K: 0 0% SMCAT Summary Report Export Area ,10,4,5,10,5,2,0 10,5,3,3,5,2,2,0 15,7,3,4,8,3,1,0 8,3,2,2,4,1,1, End Export Area End of report Report field descriptions: Configured Interal Duration The interal that is in effect when the SMCAT is turned on. Actual Interal Duration The interal that the report coers. This alue might be different from the alue of Configured Interal Duration if the SMCAT is stopped by using the VARY TCPIP,,SMCAT,OFF command. TCP SMC traffic analysis for all matching connections The data for all eligible TCP connections. The eligible TCP connections are connections with a destination IP address that match configured IP addresses or subnets. All eligible TCP connections include the connections that are not directly connected and the connections that are directly 8 SMC Applicability Tool

15 connected. This section indicates the total amount of workload that can use SMC communications with some network topology changes. Percentage of connections can use SMC (eligible) The percentage of all TCP connections that match the configured IP addresses or subnets. These TCP connections are the SMC eligible connections. Percentage of eligible connections are well-suited for SMC The percentage of all SMC eligible connections that hae a workload pattern best suited for SMC communications. These eligible connections are well-suited connections for SMC. Percentage of total traffic (segments) is well-suited for SMC The percentage of all TCP workload, measured in segments sent and receied, that flowed oer well-suited connections for SMC. Percentage of outbound traffic (segments) is well-suited for SMC The percentage of all outbound TCP workload, measured in segments sent, that flowed oer well-suited connections for SMC. Percentage of inbound traffic (segments) is well-suited for SMC The percentage of all inbound TCP workload, measured in segments receied, that flowed oer well-suited connections for SMC. Interal details The breakdown of the data that is used to calculate the percentages. Total TCP Connections The number of all actie TCP connections during the SMCAT monitoring interal. Total SMC eligible connections The number of actie TCP connections that are connected to a configured IP address during the SMCAT monitoring interal. These TCP connections are considered eligible connections to use SMC communications. Total SMC well-suited connections The number of eligible TCP connections that hae a workload pattern best suited for SMC communications. These eligible connections are considered well-suited connections. Connections that are short-lied and exchange a small amount of data are not considered well-suited for SMC communications. Total outbound traffic (in segments) The amount of outbound traffic oer all TCP connections during the SMCAT monitoring interal. SMC well-suited outbound traffic (in segments) The amount of outbound traffic oer the SMC well-suited connections during the SMCAT monitoring interal. Total inbound traffic (in segments) The amount of inbound traffic oer all TCP connections during the SMCAT monitoring interal. SMC well-suited inbound traffic (in segments) The amount of inbound traffic oer the SMC well-suited connections during the SMCAT monitoring interal. IP System Administrator's Commands 9

16 Application Send Size for well-suited connections The number and the percentage of the application send sizes that are used by the well-suited connections. The percentage might not reach 100% because of rounding. TCP SMC traffic analysis for matching direct connections The data for only the directly connected eligible TCP connections. The directly connected eligible TCP connections use one of the configured IP addresses or subnets. This section indicates the amount of workload that can use SMC communications immediately after SMC enablement. This section is a subset of the TCP SMC traffic analysis for all matching connections section. The fields under this section are the same as the fields under the TCP SMC traffic analysis for matching connections with direct network connectiity. 10 SMC Applicability Tool

17 Index S SMCAT 2 SMCATCFG 4 statements, TCP/IP configuration 1, 2 T TCP/IP configuration statements 1, 2 V VARY TCPIP command 1 SMCAT 2 TCP/IP address space 1 VARY TCPIP,,SMCAT command modifying 2 SMCAT 2 11

18 12 SMC Applicability Tool

19

20 Printed in USA