Topic
  • 6 replies
  • Latest Post - ‏2015-02-24T11:08:34Z by germinaromachado
Acc_Rdz
Acc_Rdz
18 Posts

Pinned topic Unable to start RD&T with OSA and TUN interface

‏2013-09-23T17:56:37Z |

Hi Team,

 

We are unable to start the RD&T with OSA and TUN interface. While starting the system the getting the below error.

IBM System z Personal Development Tool (zPDT)
Licensed Materials - Property of IBM
5799-ADE
(C) Copyright IBM Corp. 2007 All Rights Reserved.

z1090, version 1-4.45.26.01, build date - 05/24/13 for Linux on RedHat 64bit
AWSSTA014I Map file name specified: aviprof
AWSSTA204I zPDT started in directory '/rdtmount/rdtv9'.
AWSSTA146I Starting independent 1090 instance 'ibmsys1'
AWSEMI453W WARNING!! The number of CPUs specified=2 vs schedulable=1. Forcing to 1 CPUs
AWSEMI3141 CPU 0 zPDTA License Obtained
OSA code level = 0x4301
 Failure ffffffff d
 Failure ffffffff d
AWSRAS168E component OSA subcomponent F0 does not exist
chpid Number F0 Has stopped - Max retry exceeded !!
AWSRAS168E component OSA subcomponent A0 does not exist
chpid Number A0 Has stopped - Max retry exceeded !!
AWSSTA125I System shutdown in progress ...
AWSSTA052E Initialization of OSA failed, RC=-4

AWSSTA143I Shutdown complete
AWSSTA140E Initialization failure.
 

Could you please let us know what is the problem causing this error.

our devicemap file is a below.

[system]
memory 4G
processors 2
3270port 3270                             # port number for non-SNA (coax) 3270

[manager]
name aws3274 0001                         # define non-SNA (coax) 3270 terminals
device 0700 3279 3274 mstcon
device 0701 3279 3274 tso1


[manager]                             # define network adapter (OSA) for communication with Linux
name awsosa 0024 --path=A0 --pathtype=OSD --tunnel_intf=y     # QDIO mode
device 400 osa osa
device 401 osa osa
device 402 osa osa
[manager]                             # define network adapter (OSA) for communication with network
name awsosa 22 --path=F0 --pathtype=OSD             # QDIO mode
device 404 osa osa
device 405 osa osa
device 406 osa osa

 

 

Thanks,

Sathya

Updated on 2015-08-19T14:49:14Z at 2015-08-19T14:49:14Z by rbrunkh
  • germinaromachado
    germinaromachado
    11 Posts
    ACCEPTED ANSWER

    Re: Unable to start RD&T with OSA and TUN interface

    ‏2015-02-24T11:08:34Z  

    Hello,

     

    Try

     

    [root@rdt ~]# chown 0:0 /usr/z1090/bin/eDMosa
    [root@rdt ~]# chmod 4755 /usr/z1090/bin/eDMosa

     

    When i have this problem (AWSSTA052E Initialization of OSA failed, RC=-4
    ) , this commands was the solution...

     

     

  • RDzJohn
    RDzJohn
    292 Posts

    Re: Unable to start RD&T with OSA and TUN interface

    ‏2013-09-23T18:28:16Z  

    Some questions:

    - Have you run the z1090instcheck command to verify your installation?

    - What version of RD&T are you trying to start?

    - Are you using a RD&T USB hardware key that matches your RD&T version?

    - How many CPU cores do you have on your machine?

    - How many CPs is your RD&T licensed for?

    - Have you run the find_io command to verify that the OSA device numbers you are trying to use are actually defined and available on your machine?

     

    RDzJohn

     

  • Acc_Rdz
    Acc_Rdz
    18 Posts

    Re: Unable to start RD&T with OSA and TUN interface

    ‏2013-09-23T18:51:43Z  
    • RDzJohn
    • ‏2013-09-23T18:28:16Z

    Some questions:

    - Have you run the z1090instcheck command to verify your installation?

    - What version of RD&T are you trying to start?

    - Are you using a RD&T USB hardware key that matches your RD&T version?

    - How many CPU cores do you have on your machine?

    - How many CPs is your RD&T licensed for?

    - Have you run the find_io command to verify that the OSA device numbers you are trying to use are actually defined and available on your machine?

     

    RDzJohn

     

    Hi John,

     

    1.Yes we have run z1090instcheck and verified. Everything was ok.

    2.RD&T 9 we are trying to start

    3.yes we are you using a RD&T USB hardware key that matches your RD&T version

    4. It looks like only one core is available. we had asked the team to add more core to the system.

    5. we have 3CPs RD&T licenesed

    6.yes we have run the find_io command.

             Interface         Current          MAC                IPv4              IPv6          
     Path    Name              State            Address            Address           Address       
    ------   ----------------  ---------------- -----------------  ----------------  --------------
      F0     eth0              UP, RUNNING      00:0c:29:2a:ea:ff  10.80.57.110      fe80::20c:29ff:fe2a:eaff%eth0 
    .
      A0     tap0             
    DOWN             02:a0:a0:a0:a0:a0  *                 *             
      A1     tap1              DOWN             02:a1:a1:a1:a1:a1  *                 *              
      A2     tap2              DOWN             02:a2:a2:a2:a2:a2  *                 *              
      A3     tap3              DOWN             02:a3:a3:a3:a3:a3  *                 *              
      A4     tap4              DOWN             02:a4:a4:a4:a4:a4  *                 *              
      A5     tap5              DOWN             02:a5:a5:a5:a5:a5  *                 *              
      A6     tap6              DOWN             02:a6:a6:a6:a6:a6  *                 *              
      A7     tap7              DOWN             02:a7:a7:a7:a7:a7  *                 *              
      
     End of FIND_IO

     

    Regards,

    Sathya

  • RDzJohn
    RDzJohn
    292 Posts

    Re: Unable to start RD&T with OSA and TUN interface

    ‏2013-09-23T19:09:31Z  
    • Acc_Rdz
    • ‏2013-09-23T18:51:43Z

    Hi John,

     

    1.Yes we have run z1090instcheck and verified. Everything was ok.

    2.RD&T 9 we are trying to start

    3.yes we are you using a RD&T USB hardware key that matches your RD&T version

    4. It looks like only one core is available. we had asked the team to add more core to the system.

    5. we have 3CPs RD&T licenesed

    6.yes we have run the find_io command.

             Interface         Current          MAC                IPv4              IPv6          
     Path    Name              State            Address            Address           Address       
    ------   ----------------  ---------------- -----------------  ----------------  --------------
      F0     eth0              UP, RUNNING      00:0c:29:2a:ea:ff  10.80.57.110      fe80::20c:29ff:fe2a:eaff%eth0 
    .
      A0     tap0             
    DOWN             02:a0:a0:a0:a0:a0  *                 *             
      A1     tap1              DOWN             02:a1:a1:a1:a1:a1  *                 *              
      A2     tap2              DOWN             02:a2:a2:a2:a2:a2  *                 *              
      A3     tap3              DOWN             02:a3:a3:a3:a3:a3  *                 *              
      A4     tap4              DOWN             02:a4:a4:a4:a4:a4  *                 *              
      A5     tap5              DOWN             02:a5:a5:a5:a5:a5  *                 *              
      A6     tap6              DOWN             02:a6:a6:a6:a6:a6  *                 *              
      A7     tap7              DOWN             02:a7:a7:a7:a7:a7  *                 *              
      
     End of FIND_IO

     

    Regards,

    Sathya

    According to the previously supplied information and the results from the awsstart command, you are trying to start RD&T with a zPDT (STG) key.  This is not allowed in V9.0.  STG supplied keys are used to start zPDT.  Rational supplied keys are used to start RD&T.  You will need to fix this before you can proceed.  When you have a matching key, this:  


    z1090, version 1-4.45.26.01, build date - 05/24/13 for Linux on RedHat 64bit

     

    will look like this:


    z1091, version 1-4.45.26.01, build date - 05/24/13 for Linux on RedHat 64bit

     

    Please also fix the number of cpus in your devmap to match the number that you actually have available on your machine.  Note, even a 1 CP RD&T instance must be run on a 2 core physical processors.  You cannot run on a single core box and expect any sort of performance.

    Your find_io command reports that device A0 is DOWN.  You will need to investigate the cause of this.

    These concern me and I will follow up with development to get some clarification on them.


     Failure ffffffff d
     Failure ffffffff d

     

    RDzJohn

     

  • Acc_Rdz
    Acc_Rdz
    18 Posts

    Re: Unable to start RD&T with OSA and TUN interface

    ‏2013-09-23T22:22:48Z  
    • RDzJohn
    • ‏2013-09-23T19:09:31Z

    According to the previously supplied information and the results from the awsstart command, you are trying to start RD&T with a zPDT (STG) key.  This is not allowed in V9.0.  STG supplied keys are used to start zPDT.  Rational supplied keys are used to start RD&T.  You will need to fix this before you can proceed.  When you have a matching key, this:  


    z1090, version 1-4.45.26.01, build date - 05/24/13 for Linux on RedHat 64bit

     

    will look like this:


    z1091, version 1-4.45.26.01, build date - 05/24/13 for Linux on RedHat 64bit

     

    Please also fix the number of cpus in your devmap to match the number that you actually have available on your machine.  Note, even a 1 CP RD&T instance must be run on a 2 core physical processors.  You cannot run on a single core box and expect any sort of performance.

    Your find_io command reports that device A0 is DOWN.  You will need to investigate the cause of this.

    These concern me and I will follow up with development to get some clarification on them.


     Failure ffffffff d
     Failure ffffffff d

     

    RDzJohn

     

    Hi John,

    We had changed the ownership of user and group for  /usr/z1090. then we are able to start the system with OSA and TUN interface.

    We are customizing the tcpip. we are encountering the below error on PORTB

    EZZ4310I ERROR: CODE=0810002B REPORTED ON DEVICE PORTB. DIAGNOSTIC CODE  03  

    TCPIP Profile:

    ;This device defines the tunnel 
     DEVICE PORTA MPCIPA 
     LINK TAP0 IPAQENET PORTA 
     HOME 192.18.10.20 TAP0 

     DEVICE PORTB MPCIPA 
     LINK ETH1 IPAQENET PORTB 
     HOME 161.178.198.160 ETH1       
      PRIMARYINTERFACE ETH1    
     BEGINRoutes 
     ; Destination SubnetMask FirstHop LinkName Size 
      ROUTE 192.168.10.0 255.255.255.0 = TAP0 MTU 1492 
      ROUTE 161.178.198.0 255.255.255.128 = ETH1 MTU 1492 
      ROUTE DEFAULT 161.178.198.129 ETH1 MTU 1492 
     ENDRoutes                                                         
    START PORTA 
     START PORTB  

     

    Could you please let us know, what could you be the problem.

     

    Regards,

    Sathya

  • RDzJohn
    RDzJohn
    292 Posts

    Re: Unable to start RD&T with OSA and TUN interface

    ‏2013-09-24T11:30:22Z  
    • Acc_Rdz
    • ‏2013-09-23T22:22:48Z

    Hi John,

    We had changed the ownership of user and group for  /usr/z1090. then we are able to start the system with OSA and TUN interface.

    We are customizing the tcpip. we are encountering the below error on PORTB

    EZZ4310I ERROR: CODE=0810002B REPORTED ON DEVICE PORTB. DIAGNOSTIC CODE  03  

    TCPIP Profile:

    ;This device defines the tunnel 
     DEVICE PORTA MPCIPA 
     LINK TAP0 IPAQENET PORTA 
     HOME 192.18.10.20 TAP0 

     DEVICE PORTB MPCIPA 
     LINK ETH1 IPAQENET PORTB 
     HOME 161.178.198.160 ETH1       
      PRIMARYINTERFACE ETH1    
     BEGINRoutes 
     ; Destination SubnetMask FirstHop LinkName Size 
      ROUTE 192.168.10.0 255.255.255.0 = TAP0 MTU 1492 
      ROUTE 161.178.198.0 255.255.255.128 = ETH1 MTU 1492 
      ROUTE DEFAULT 161.178.198.129 ETH1 MTU 1492 
     ENDRoutes                                                         
    START PORTA 
     START PORTB  

     

    Could you please let us know, what could you be the problem.

     

    Regards,

    Sathya

    This error is mot often caused because of a mismatch between the devmap, TCPIP, and VTAM definitions.  Make sure all names and definitions match each other.

     

    RDzJohn

  • germinaromachado
    germinaromachado
    11 Posts

    Re: Unable to start RD&T with OSA and TUN interface

    ‏2015-02-24T11:08:34Z  

    Hello,

     

    Try

     

    [root@rdt ~]# chown 0:0 /usr/z1090/bin/eDMosa
    [root@rdt ~]# chmod 4755 /usr/z1090/bin/eDMosa

     

    When i have this problem (AWSSTA052E Initialization of OSA failed, RC=-4
    ) , this commands was the solution...