Skip to main content
Solved

Tune 111 error codes

E

Hello Everyone, I am looking at the devices under Fine Tune/ CLI Configurations failed.  I have over 1400 devices that can pull CLI Configurations and a few are failing to pull information due to 111 errors.   I tried the setup that worked for the other devices and manually added my own login credentials under the tune process and it fails. I also verified I am able to login to the device with my credentials. 

 

 Does anyone know what are the causes for the 111 error? Does Netbrain have a list of error codes and possible fixes? 

2023-03-20 09:09:37 Begin tune process via Worker NETBRA11(pid: 6668)
..
2023-03-20 09:10:12 Connecting failed, error code: 111, error description: [111] Connection refused.
2023-03-20 09:10:12 Can not Telnet/SSH to the device.
2023-03-20 09:10:12 End tune process

Best answer by ec485n

We figured out it in this case.   111 seemed to have been not pword issue but port issue.  We figured out when someone just noticed it hey we are doing ssh to access our equipment, but they were seeing port 23. We changed it to port 22 and then it worked. We discovered via shared device settings.   Thanks for the assist. 

View original
    Did this topic help you find an answer to your question?

    3 replies

    C
    Forum|alt.badge.img+1

    Hi @ec485n,

    we had the same issue, the cause was an expired user. Please note that when you update your user/PW settings in Domain Management - Network Settings you have to re-assign this user to the device. I believe this is because NetBrain hard-codes the settings to the device and changes will not be automatically transferred. Please test this with one device.

    E
    • ec485n
    • Author
    • Inspiring
    • 15 replies
    • March 21, 2023

    Thanks for the response. I tried with new login information and tried with my own login creds and same result. To cover the bases, I also extended my timeout time in adv settings for the shared device to a much longer time with the same results. It could probably be something stuck in the backend. Will follow up with Netbrain reps.

    E
    • ec485n
    • Author
    • Inspiring
    • 15 replies
    • Answer
    • March 23, 2023

    We figured out it in this case.   111 seemed to have been not pword issue but port issue.  We figured out when someone just noticed it hey we are doing ssh to access our equipment, but they were seeing port 23. We changed it to port 22 and then it worked. We discovered via shared device settings.   Thanks for the assist. 

    Reply


    Most helpful members this week

    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings
    Community |  Ideas

    Facebook |  Instagram |  Youtube |  Twitter |  LinkedIn
    Privacy & Security Statement  |  Terms & Conditions |  Impressum  |  UK Modern Slavery Statement
    Copyright © 2021 by NetBrain Technologies Inc. - All rights reserved.