Verifying your connection between the MSS LPAR and your MOI Appliance

Products

• Mainframe Operational Intelligence

Issue/Introduction

The MOI (Mainframe Operational Intelligence) appliance receives metric data from the MSS (Message Service Server) STC.   If the metric data is not flowing and there are no obvious errors in the MSS logs, there are some network commands that can be checked to see if there are any network connection type errors.   If the network commands listed in the Resolution section of this Knowledge Document fail, you will need to contact your company's networking group to resolve the connection issue before metric data will not start flowing. 

 

Environment

Release : 2.1

Component : MF OPERATIONAL INTELLIGENCE

Resolution

The steps to check the network connection between the MSS LPAR and your MOI appliance: 

1)  From the LPAR that your MSS STC is running on:

               In ISPF option 6, execute the following command:

                tso  ping  <your MOI appliance hostname>                                  

 

                 Successful reply :    CS V2R5: Pinging host <your MOI appliance hostname> (10.xxx.xxx.xxx)

                                                         Ping #1 response took 0.051 seconds. (50.518 milliseconds)                

                                                                        

                Unsuccessful ping response will be a timeout such as the response below:

                                               CS V2R5: Pinging host 10.xxx.xxx.xxx 

                                                       Ping #1 timed out                   

                              

 2) To check the mainframe hostname for the next step, please use the following commands: 

                      Option ===> TSO OMVS

                      $ hostname               

                                <hostname>.<company domain>

     

3) From the MOI appliance Linux machine:

 

                [root@nnnnnn ~]#  ping <hostname>.<company domain>

                                                 PING <hostname>.<company domain> :(10.xxx.xx.xx) 56(84) bytes of data.

                                                 64 bytes from <hostname>.<company domain>: (10.xxx.xx.xx): icmp_seq=1 ttl=54 time=55.1 ms

                                                 64 bytes from <hostname>.<company domain>: (10.xxx.xx.xx): icmp_seq=2 ttl=52 time=52.1 ms

                                                64 bytes from <hostname>.<company domain>: (10.xxx.xx.xx)icmp_seq=3 ttl=52 time=50.9 ms

             .

 

4)  You can additionally check the network connection of your MOI appliance from Windows:

                C:\Users\nnnnnnnn>   ping <MOI appliance Linux machine hostname>

 

                                                       Pinging <hostname>.<company domain> (10.xxx.xx.xx)with 32 bytes of data:

                                                       Reply from (10.xxx.xx.xx): bytes=32 time=86ms TTL=56

                                                       Reply from (10.xxx.xx.xx): bytes=32 time=82ms TTL=56

                                                       Reply from (10.xxx.xx.xx): bytes=32 time=82ms TTL=56

                                                       Reply from (10.xxx.xx.xx): bytes=32 time=83ms TTL=56

 

                                                       Ping statistics for (10.xxx.xx.xx):

                                                       Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

                                                       Approximate round trip times in milli-seconds:

                                                       Minimum = 82ms, Maximum = 86ms, Average = 83ms

 

 

5) Please also check the ports that listening on your MOI appliance Linux machine with the following command: 

 

[root@<MOI appliance Linux machine hostname> ~]# ss -tulwn | grep LISTEN

tcp    LISTEN     0      128       *:111                   *:*

tcp    LISTEN     0      128       *:22                    *:*

tcp    LISTEN     0      128    [::]:61443              [::]:*

tcp    LISTEN     0      128    [::]:61480              [::]:*

tcp    LISTEN     0      128    [::]:111                [::]:*

tcp    LISTEN     0      128    [::]:61616              [::]:*

tcp    LISTEN     0      128    [::]:22                 [::]:*

tcp    LISTEN     0      128    [::]:61340              [::]:*

tcp    LISTEN     0      128    [::]:61980              [::]:*

tcp    LISTEN     0      128    [::]:61341              [::]:*

tcp    LISTEN     0      128    [::]:61983              [::]:*

 

 

Or if the netstat command is installed, you can use it instead: 

 

 

[root@<MOI appliance Linux machine hostname> ~]# netstat -tulpn | grep LISTEN

tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN      710/rpcbind

tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1490/sshd

tcp6       0      0 :::61443                :::*                    LISTEN      4638/docker-proxy-c

tcp6       0      0 :::61480                :::*                    LISTEN      4626/docker-proxy-c

tcp6       0      0 :::111                  :::*                    LISTEN      710/rpcbind

tcp6       0      0 :::61616                :::*                    LISTEN      4806/docker-proxy-c

tcp6       0      0 :::22                   :::*                    LISTEN      1490/sshd

tcp6       0      0 :::61340                :::*                    LISTEN      5622/docker-proxy-c

tcp6       0      0 :::61980                :::*                    LISTEN      5057/docker-proxy-c

tcp6       0      0 :::61341                :::*                    LISTEN      5609/docker-proxy-c

tcp6       0      0 :::61983                :::*                    LISTEN     

5044/docker-proxy-c