Automated Testing

Automated Testing

Automated Testing

Build an automated testing process to enable continuous integration of your hybrid cloud applications including z/OS

 View Only
  • 1.  Licence problem with LDK server

    Posted Thu June 29, 2017 04:05 PM

    Hi everbody

    I have a problem with the utilzation of zDT with Software Software Based Licensing (LDK)

    The licence server LDK runs and i have a valide licence

     

    the UIM server is Ok also 

    on th zdt server the uim client is OK and comunicate with the unim server on licence server

     

    the conenxion between servers seems OK 

     

     

    but when i send the zdt server th e log indcate à licence problem 

     

     

    Thank you for your assitance 

     

    Alexandre 

    3acti


  • 2.  Re: Licence problem with LDK server

    Posted Fri June 30, 2017 09:49 AM

    Hi Alexandre, you need to check 2 other requirements:

    - port 1947 must be open in your firewall in the License manager instance

    - in the License Manger GUI, go to configuration > access from remote clients

      Check if you put rules to allow remote clients to get license. In general we do as follows:

    AdilsonColombo


  • 3.  Re: Licence problem with LDK server

    Posted Mon July 03, 2017 04:39 AM

    Hi Adilson,

    Thank you for you response

    I verified the acess to port 1947 on the licence and it seem OK , because i can access to the web interlace since mu PC

    but i modified the both  IPTABLE (server licence and zdpt server)


    [root@s00vl9967917 produit]# iptables -L -v -nChain INPUT (policy ACCEPT 3707 packets, 449K bytes) pkts bytes target     prot opt in     out     source               destination    0     0 ACCEPT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0            udp dpt:7001    0     0 ACCEPT     udp  --  *      *       0.0.0.0/0            0.0.0.0/0            udp dpt:7002    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:7001    0     0 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:7002  673 66417 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:1947  462 63012 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:9450    1    44 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0            tcp dpt:9451Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target     prot opt in     out     source               destinationChain OUTPUT (policy ACCEPT 3702 packets, 609K bytes) pkts bytes target     prot opt in     out     source               destination[root@s00vl9967917 produit]#
    [root@s00vl9967917 produit]# iptables -LChain INPUT (policy ACCEPT)target     prot opt source               destinationACCEPT     udp  --  anywhere             anywhere             udp dpt:afs3-callbackACCEPT     udp  --  anywhere             anywhere             udp dpt:afs3-prserverACCEPT     tcp  --  anywhere             anywhere             tcp dpt:afs3-callbackACCEPT     tcp  --  anywhere             anywhere             tcp dpt:afs3-prserverACCEPT     tcp  --  anywhere             anywhere             tcp dpt:sentinelsrmACCEPT     tcp  --  anywhere             anywhere             tcp dpt:sntlkeyssrvrACCEPT     tcp  --  anywhere             anywhere             tcp dpt:9451Chain FORWARD (policy ACCEPT)target     prot opt source               destinationChain OUTPUT (policy ACCEPT)target     prot opt source               destination

     

    [root@s00vl9967917 logs]# nmap -p 1974 10.18.0.196

    Starting Nmap 6.40 ( http://nmap.org ) at 2017-07-03 09:55 CEST
    Nmap scan report for parvl3021197.fr.net.intra (10.18.0.196)
    Host is up (0.00066s latency).
    PORT     STATE SERVICE
    1947/tcp open  sentinelsrm

    Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds
    [root@s00vl9967917 logs]# nmap -p 9450 10.18.0.196

    Starting Nmap 6.40 ( http://nmap.org ) at 2017-07-03 09:55 CEST
    Nmap scan report for parvl3021197.fr.net.intra (10.18.0.196)
    Host is up (0.00058s latency).
    PORT     STATE  SERVICE
    9450/tcp closed unknown

    Nmap done: 1 IP address (1 host up) scanned in 0.06 seconds
    [root@s00vl9967917 logs]# nmap -p 9451 10.18.0.196

    Starting Nmap 6.40 ( http://nmap.org ) at 2017-07-03 09:55 CEST
    Nmap scan report for parvl3021197.fr.net.intra (10.18.0.196)
    Host is up (0.00058s latency).
    PORT     STATE SERVICE
    9451/tcp open  unknown

    Nmap done: 1 IP address (1 host up) scanned in 0.07 seconds


    [root@parvl3021197 lb24938]# iptables -L -v -nChain INPUT (policy ACCEPT 534K packets, 586M bytes) pkts bytes target     prot opt in     out     source               destination74318   13M ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:1947    2    84 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:9451  931 55844 ACCEPT     tcp  --  *      *       0.0.0.0/0            0.0.0.0/0           tcp dpt:9450Chain FORWARD (policy ACCEPT 0 packets, 0 bytes) pkts bytes target     prot opt in     out     source               destinationChain OUTPUT (policy ACCEPT 401K packets, 420M bytes) pkts bytes target     prot opt in     out     source               destination[root@parvl3021197 lb24938]# iptables -LChain INPUT (policy ACCEPT)target     prot opt source               destinationACCEPT     tcp  --  anywhere             anywhere            tcp dpt:hlserverACCEPT     tcp  --  anywhere             anywhere            tcp dpt:9451ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:sntlkeyssrvrChain FORWARD (policy ACCEPT)target     prot opt source               destinationChain OUTPUT (policy ACCEPT)target     prot opt source               destination[root@parvl3021197 lb24938]#
    [root@parvl3021197 lb24938]# nmap -p 1947 10.244.18.185Starting Nmap 5.21 ( http://nmap.org ) at 2017-07-03 07:58 Local time zone must be set--see zic manual pageNmap scan report for s00vl9967917.fr.net.intra (10.244.18.185)Host is up (0.00056s latency).PORT     STATE SERVICE1947/tcp open  unknownNmap done: 1 IP address (1 host up) scanned in 0.30 seconds[root@parvl3021197 lb24938]# nmap -p 9450 10.244.18.185Starting Nmap 5.21 ( http://nmap.org ) at 2017-07-03 07:58 Local time zone must be set--see zic manual pageNmap scan report for s00vl9967917.fr.net.intra (10.244.18.185)Host is up (0.0014s latency).PORT     STATE SERVICE9450/tcp open  unknownNmap done: 1 IP address (1 host up) scanned in 0.07 seconds[root@parvl3021197 lb24938]# nmap -p 9451 10.244.18.185Starting Nmap 5.21 ( http://nmap.org ) at 2017-07-03 07:58 Local time zone must be set--see zic manual pageNmap scan report for s00vl9967917.fr.net.intra (10.244.18.185)Host is up (0.00056s latency).PORT     STATE  SERVICE9451/tcp closed unknownNmap done: 1 IP address (1 host up) scanned in 0.08 seconds[root@parvl3021197 lb24938]#

     

    And the box is checked

    For more explanation a schema of the architechture

     

    And the problem is the same

    CMD : 070317 09:22:06: awsstart devmap_bnppLOG : 070317 09:22:06: AWSSTART:z1091, version 1-6.49.23, build date - 10/21/16 for Linux on RedHat 64bitLOG : 070317 09:22:06: AWSSTART: Intel-64 architectureLOG : 070317 09:22:06: AWSSTART: Configuration File-devmap_bnppINFO: 070317 09:22:06: STA: AWSSTA204I zPDT started in directory '/apps/zpdt/produit'.INFO: 070317 09:22:06: STA: AWSSTA146I Starting independent 1090 instance 'lb24938'CMD : 070317 09:22:06: awsap -p 31379LOG : 070317 09:22:06: CPU: DEVMAP loaded for EMILY process, RC=64LOG : 070317 09:22:06: CPU: Creating 2 CPUsLOG : 070317 09:22:06: CPU: Starting CPUs.LOG : 070317 09:22:06: CPU: ERAS: Starting RAS setupCMD : 070317 09:22:06: sclp_process 0 0 validLOG : 070317 09:22:07: CPU: IPR started for CPU 1LOG : 070317 09:22:07: CPU: CPU resetLOG : 070317 09:22:07: CPU: IPR complete for CPU 1LOG : 070317 09:22:07: CPU: IPR started for CPU 0LOG : 070317 09:22:07: CPU: CPU resetLOG : 070317 09:22:07: CPU: IPR complete for CPU 0LOG : 070317 09:22:07: LIC: hasp:  * Sentinel protection key not available :   code=7LOG : 070317 09:22:07: LIC: hasp:  * Sentinel protection key not available :   code=7INFO: 070317 09:22:09: EMI: AWSEMI005I Waiting for 1090 licenseINFO: 070317 09:22:21: OSA: OSA code level = 0x4301INFO: 070317 09:22:25: DSA: AWSDSA010I AWSOSA is ready for chpid: 0xA0 device: 0x400INFO: 070317 09:22:26: DSA: AWSDSA010I AWSOSA is ready for chpid: 0xA0 device: 0x401INFO: 070317 09:22:26: DSA: AWSDSA010I AWSOSA is ready for chpid: 0xA0 device: 0x402INFO: 070317 09:22:26: DSA: AWSDSA010I AWSOSA is ready for chpid: 0xF0 device: 0x404INFO: 070317 09:22:26: DSA: AWSDSA010I AWSOSA is ready for chpid: 0xF0 device: 0x405INFO: 070317 09:22:26: DSA: AWSDSA010I AWSOSA is ready for chpid: 0xF0 device: 0x406CMD : 070317 09:22:26: tnportl2 -r -l -n LB24938INFO: 070317 09:22:28: STA: AWSSTA059I System initialization completeINFO: 070317 09:22:28: STA: AWSSTA012I All configured subsystems startedERR : 070317 09:22:53: EMI: AWSEMI315E zPDTA License Unavailable for CPU 1ERR : 070317 09:23:39: EMI: AWSEMI315E zPDTA License Unavailable for CPU 0

    thank you for help

     

    3acti


  • 4.  Re: Licence problem with LDK server

    Posted Thu July 06, 2017 05:15 PM

    Hi 

    I managed to find the cause of the problem following the advice of the team IBM France

     

    It missed the configuration of the LDK server on zPDT

     

    Thank you for your help

     

    Alexandre 

    3acti