none
Getting ERROR EVENT 101 , SNA IP-DLC LINK Sevice RRS feed

  • Question

  • LDLC command frame retry limit exceeded
      Link                   = @N000001
      Port                   = IPPORT00
      DLC                    = IPDLC000
      Local address          = 10.***.***.** SAP=4
      Destination address    = 10.***.***.** SAP=4
      Local UI address       = 10.***.***.** SAP=4
      Destination UI address = 0
      ACK timer duration     = 15000
      Retry limit            = 3

     Cause:
     LDLC command frame retry limit exceeded.
     
     Effect:
     Link activation will fail, or an active link will be brought down.
     
     Action:
     If the remote node is not accessible, it is normal for LDLC to detect outage in this way. If LDLC is taking too long to detect link outages, then decrease the configured ACK timer or retry limit. If LDLC is deactivating links during network congestion or heavy processor loading, then increase the configured ACK timer or retry limit.


    Thanks and Regards Jagdish
    Monday, January 31, 2011 12:35 PM

Answers

  • Error removed using Correct values.
    Thanks and Regards Jagdish
    • Marked as answer by Cheeta LM Tuesday, February 1, 2011 6:39 AM
    Tuesday, February 1, 2011 6:39 AM
  • Jagdish,

    The last error that you are seeing can occur for several reasons, the following are some things to check that have caused this error for others setting up the IP-DLC link service in HIS:

    RESOLUTION (Mainframe)
    There are numerous causes of this error; each step will need to be performed until the issue is resolved.
     
    1. Verify the correct primary NNS is entered in the IP-DLC Link Service.
    2. Verify the NNS is operational.
    3. Verify UDP ports 12000-12004 are open in both directions (You can use the PortQRYUI tool available at http://www.microsoft.com/downloads/details.aspx?familyid=8355E537-1EA6-4569-AABB-F248F4BD91D0&displaylang=en or another port scanning tool to see if the ports are opened).
    4. Review Mainframe system log.
     
    RESOLUTION (AS/400)
    1. Verify the correct primary NNS is entered in the IP-DLC Link Service.
    2. Verify the NNS is operational.
    3. Verify UDP ports 12000-12004 are open (Use PortQRYUI tool or anotehr port scanning tool).
    4. Verify AS/400 IP-DLC APPC Controller configuration settings.
    5. Verify AS/400 IP-DLC APPC Controller is varied on.
    6. Verify AS/400 QSYSOPR log.

    Thanks...

     


    Stephen Jackson - MSFT
    • Marked as answer by Cheeta LM Saturday, February 12, 2011 10:43 AM
    Thursday, February 3, 2011 9:57 PM

All replies

  • Error removed using Correct values.
    Thanks and Regards Jagdish
    • Marked as answer by Cheeta LM Tuesday, February 1, 2011 6:39 AM
    Tuesday, February 1, 2011 6:39 AM
  • Jagdish

    What is your question? In other words, what is it about this message or the circumstances in which it appeared which you do not understand and with which you would like help?

    Chris Mason

     

    Tuesday, February 1, 2011 6:41 AM
  • Hi Chris,

    My question was how to resolve above error , I got this when i am trying to congfigure host integration server . I saw this in event viewer of HIS.

    Now i am getting following error

    Log Name:      Application
    Source:        SNA IP-DLC Link Service

    Date:          31/01/2011 13:41:42
    Event ID:      121
    Task Category: Base
    Level:         Warning
    Keywords:      Classic
    User:          #############

    Computer:    #############  
    Description:
    The attempt to start the link to Network Node Server XX.XXX.XX.XX failed.
     NNS link station: @N000001
     Secondary return code: 0x13400000

     Cause:
     An LS_FAILURE was returned from a START_LS NOF verb.  The Network Node Server may be inactive, or an invalid NNS address may have been configured for the link service.
     
     Effect:
     The IP-DLC link service will continue to attempt to connect to the Network Node Server.  If this fails, and no alternative NNS has been configured, no connections will be able to start successfully.
     
     Action:
     Check that the Network Node Server address has been configured correctly, that the NNS is active, and that it is reachable across the IP network.

    for this we need to verify the certain VTAM definitions , It will be great if you can provide the log of below commands

    I need help in resolving this

    Thanks in advance !


    Thanks and Regards Jagdish
    Tuesday, February 1, 2011 6:40 PM
  • Jagdish,

    The last error that you are seeing can occur for several reasons, the following are some things to check that have caused this error for others setting up the IP-DLC link service in HIS:

    RESOLUTION (Mainframe)
    There are numerous causes of this error; each step will need to be performed until the issue is resolved.
     
    1. Verify the correct primary NNS is entered in the IP-DLC Link Service.
    2. Verify the NNS is operational.
    3. Verify UDP ports 12000-12004 are open in both directions (You can use the PortQRYUI tool available at http://www.microsoft.com/downloads/details.aspx?familyid=8355E537-1EA6-4569-AABB-F248F4BD91D0&displaylang=en or another port scanning tool to see if the ports are opened).
    4. Review Mainframe system log.
     
    RESOLUTION (AS/400)
    1. Verify the correct primary NNS is entered in the IP-DLC Link Service.
    2. Verify the NNS is operational.
    3. Verify UDP ports 12000-12004 are open (Use PortQRYUI tool or anotehr port scanning tool).
    4. Verify AS/400 IP-DLC APPC Controller configuration settings.
    5. Verify AS/400 IP-DLC APPC Controller is varied on.
    6. Verify AS/400 QSYSOPR log.

    Thanks...

     


    Stephen Jackson - MSFT
    • Marked as answer by Cheeta LM Saturday, February 12, 2011 10:43 AM
    Thursday, February 3, 2011 9:57 PM