DX Unified Infrastructure Management

  • Private Community

  • 1.  Nimbus unable to reach agent

    Posted Aug 19, 2016 02:54 PM

    Hello all,

     

    We are frequently getting Nimbus unable to reach agent alerts/notification on one of the Nimbus Hub server itself. Please let us know the reason of this alert and how to fix?

     

    Thanks in Advance

     

    Regards,
    San



  • 2.  Re: Nimbus unable to reach agent

    Broadcom Employee
    Posted Aug 19, 2016 04:54 PM

    Can you please post the exact error you are getting or a screen shot of the detail alarm from IM?

    Your phrasing is not ringing a bell on what the problem may be.



  • 3.  Re: Nimbus unable to reach agent

    Posted Aug 25, 2016 03:11 AM

    Robot is inactive

     

    Usually i see this inactive alert for a while and if i check logs everything seems to be normal. I have attached the controller log as well.

     

    Below is the controller log

     

    ug 25 01:55:59:091 [2684] Controller: **********************************
    Aug 25 01:55:59:091 [2684] Controller: portAliveCheck (hubonly) - check hub 48002
    Aug 25 01:55:59:091 [2684] Controller: AliveCheckNext hub/48002
    Aug 25 01:55:59:091 [2684] Controller: (async)async_req 10.6.200.106/48002 - _status
    Aug 25 01:55:59:091 [2684] Controller: nimSessionAConnect - host = 10.6.200.106, port = 48002, secWait = 45
    Aug 25 01:55:59:091 [2684] Controller: sockConnect - to host 10.6.200.106, port 48002
    Aug 25 01:55:59:091 [2684] Controller: (async)cb_pacallback
    Aug 25 01:55:59:091 [2684] Controller: (async)cb_pacallback - diff = 0, cmd = _status
    Aug 25 01:55:59:091 [2684] Controller: SREQUEST: _status ->10.6.200.106/48002
    Aug 25 01:55:59:091 [2684] Controller: RREPLY: status=OK(0) <-10.6.200.106/48002 h=37 d=284
    Aug 25 01:55:59:091 [2684] Controller: cb_pacallback - cb_reply from 10.6.200.106/48002
    Aug 25 01:55:59:091 [2684] Controller: SREQUEST: _close ->10.6.200.106/48002
    Aug 25 01:56:15:005 [2684] Controller: RREQUEST: verify_login <-10.6.200.106/58749 h=230 d=233
    Aug 25 01:56:15:005 [2684] Controller: verify_login from 10.6.200.106/58749
    Aug 25 01:56:15:005 [2684] Controller: (async)async_hub_req_s - verify_login
    Aug 25 01:56:15:005 [2684] Controller: (async)async_hub_req - verify_login
    Aug 25 01:56:15:005 [2684] Controller: (async)async_hub_check
    Aug 25 01:56:15:005 [2684] Controller: (async)async_hub_check - diff = 0, cmd = verify_login
    Aug 25 01:56:15:005 [2684] Controller: SREQUEST: verify_login ->10.6.200.106/48002
    Aug 25 01:56:15:005 [2684] Controller: (async)async_hub_check done
    Aug 25 01:56:15:005 [2684] Controller: RREPLY: status=OK(0) <-10.6.200.106/48002 h=37 d=50
    Aug 25 01:56:15:005 [2684] Controller: (async)cb_hub_acallback
    Aug 25 01:56:15:005 [2684] Controller: (async)cb_hub_acallback - diff = 0, cmd = verify_login
    Aug 25 01:56:15:005 [2684] Controller: cb_hub_acallback - reply from 10.6.200.106/48002
    Aug 25 01:56:15:005 [2684] Controller: (async)cb_hub_req_s 0
    Aug 25 01:56:15:005 [2684] Controller: (async)SessionFindList (5)
    Aug 25 01:56:15:005 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58749
    Aug 25 01:56:15:005 [2684] Controller: (async)cb_hub_acallback done
    Aug 25 01:56:15:005 [2684] Controller: RREQUEST: _close <-10.6.200.106/58749 h=223 d=0
    Aug 25 01:56:15:036 [2684] Controller: RREQUEST: probe_list <-10.6.200.106/58750 h=289 d=16
    Aug 25 01:56:15:036 [2684] Controller: nimSockaddr2Ip - found 10.6.200.106
    Aug 25 01:56:15:036 [2684] Controller: nimVerifyLogin robot
    Aug 25 01:56:15:036 [2684] Controller: nimSessionConnect - host = 10.6.200.106, port = 48002, secWait = 180
    Aug 25 01:56:15:036 [2684] Controller: sockConnect - to host 10.6.200.106, port 48002
    Aug 25 01:56:15:036 [2684] Controller: SREQUEST: verify_login ->10.6.200.106/48002
    Aug 25 01:56:15:036 [2684] Controller: RREPLY: status=OK(0) <-10.6.200.106/48002 h=37 d=50
    Aug 25 01:56:15:036 [2684] Controller: SREQUEST: _close ->10.6.200.106/48002
    Aug 25 01:56:15:036 [2684] Controller: probe_list (nas-ao) from 10.6.200.106/58750
    Aug 25 01:56:15:036 [2684] Controller: Remote probe remote_pdnodec1206_netware: robot = pdnodec1206, name = netware
    Aug 25 01:56:15:036 [2684] Controller: Remote probe remote_pmh-nds-4_netware: robot = pmh-nds-4, name = netware
    Aug 25 01:56:15:036 [2684] Controller: SREPLY: status = 4(not found) ->10.6.200.106/58750
    Aug 25 01:56:15:051 [2684] Controller: RREQUEST: _close <-10.6.200.106/58750 h=284 d=0
    Aug 25 01:56:20:076 [2684] Controller: RREQUEST: get_info <-10.6.200.106/58755 h=286 d=0
    Aug 25 01:56:20:076 [2684] Controller: get_info from 10.6.200.106/58755
    Aug 25 01:56:20:076 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58755
    Aug 25 01:56:20:092 [2684] Controller: RREQUEST: _close <-10.6.200.106/58755 h=284 d=0
    Aug 25 01:56:20:092 [2684] Controller: RREQUEST: probe_list <-10.6.200.106/58756 h=289 d=21
    Aug 25 01:56:20:092 [2684] Controller: nimSockaddr2Ip - found 10.6.200.106
    Aug 25 01:56:20:092 [2684] Controller: nimVerifyLogin robot
    Aug 25 01:56:20:092 [2684] Controller: nimSessionConnect - host = 10.6.200.106, port = 48002, secWait = 180
    Aug 25 01:56:20:092 [2684] Controller: sockConnect - to host 10.6.200.106, port 48002
    Aug 25 01:56:20:092 [2684] Controller: SREQUEST: verify_login ->10.6.200.106/48002
    Aug 25 01:56:20:092 [2684] Controller: RREPLY: status=OK(0) <-10.6.200.106/48002 h=37 d=50
    Aug 25 01:56:20:092 [2684] Controller: SREQUEST: _close ->10.6.200.106/48002
    Aug 25 01:56:20:092 [2684] Controller: probe_list (controller) from 10.6.200.106/58756
    Aug 25 01:56:20:092 [2684] Controller: Remote probe remote_pdnodec1206_netware: robot = pdnodec1206, name = netware
    Aug 25 01:56:20:092 [2684] Controller: Remote probe remote_pmh-nds-4_netware: robot = pmh-nds-4, name = netware
    Aug 25 01:56:20:092 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58756
    Aug 25 01:56:20:107 [2684] Controller: RREQUEST: _close <-10.6.200.106/58756 h=284 d=0
    Aug 25 01:56:20:107 [2684] Controller: RREQUEST: _status <-10.6.200.106/58758 h=285 d=0
    Aug 25 01:56:20:107 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58758
    Aug 25 01:56:20:123 [2684] Controller: RREQUEST: _close <-10.6.200.106/58758 h=284 d=0
    Aug 25 01:56:20:123 [2684] Controller: RREQUEST: probe_config_get <-10.6.200.106/58759 h=296 d=21
    Aug 25 01:56:20:123 [2684] Controller: nimSockaddr2Ip - found 10.6.200.106
    Aug 25 01:56:20:123 [2684] Controller: nimVerifyLogin robot
    Aug 25 01:56:20:123 [2684] Controller: nimSessionConnect - host = 10.6.200.106, port = 48002, secWait = 180
    Aug 25 01:56:20:123 [2684] Controller: sockConnect - to host 10.6.200.106, port 48002
    Aug 25 01:56:20:123 [2684] Controller: SREQUEST: verify_login ->10.6.200.106/48002
    Aug 25 01:56:20:123 [2684] Controller: RREPLY: status=OK(0) <-10.6.200.106/48002 h=37 d=50
    Aug 25 01:56:20:123 [2684] Controller: SREQUEST: _close ->10.6.200.106/48002
    Aug 25 01:56:20:123 [2684] Controller: (probe_config_get) - called from 10.6.200.106/58759
    Aug 25 01:56:20:123 [2304] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58759
    Aug 25 01:56:20:123 [2304] Controller: SREQUEST: _close ->10.6.200.106/58759
    Aug 25 01:56:20:154 [2684] Controller: RREQUEST: _status <-10.6.200.106/58761 h=285 d=0
    Aug 25 01:56:20:154 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58761
    Aug 25 01:56:20:170 [2684] Controller: RREQUEST: _close <-10.6.200.106/58761 h=284 d=0
    Aug 25 01:56:20:170 [2684] Controller: RREQUEST: get_info <-10.6.200.106/58762 h=286 d=0
    Aug 25 01:56:20:170 [2684] Controller: get_info from 10.6.200.106/58762
    Aug 25 01:56:20:170 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58762
    Aug 25 01:56:20:185 [2684] Controller: RREQUEST: _close <-10.6.200.106/58762 h=284 d=0
    Aug 25 01:56:20:185 [2684] Controller: RREQUEST: gethub <-10.6.200.106/58763 h=284 d=0
    Aug 25 01:56:20:185 [2684] Controller: gethub from 10.6.200.106/58763
    Aug 25 01:56:20:185 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58763
    Aug 25 01:56:20:201 [2684] Controller: RREQUEST: _close <-10.6.200.106/58763 h=284 d=0
    Aug 25 01:56:20:201 [2684] Controller: RREQUEST: gethub <-10.6.200.106/58764 h=284 d=0
    Aug 25 01:56:20:201 [2684] Controller: gethub from 10.6.200.106/58764
    Aug 25 01:56:20:201 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58764
    Aug 25 01:56:20:216 [2684] Controller: RREQUEST: _close <-10.6.200.106/58764 h=284 d=0
    Aug 25 01:56:20:279 [2684] Controller: RREQUEST: probe_config_get <-10.6.200.106/58766 h=295 d=53
    Aug 25 01:56:20:279 [2684] Controller: nimSockaddr2Ip - found 10.6.200.106
    Aug 25 01:56:20:279 [2684] Controller: nimVerifyLogin robot
    Aug 25 01:56:20:279 [2684] Controller: nimSessionConnect - host = 10.6.200.106, port = 48002, secWait = 180
    Aug 25 01:56:20:279 [2684] Controller: sockConnect - to host 10.6.200.106, port 48002
    Aug 25 01:56:20:279 [2684] Controller: SREQUEST: verify_login ->10.6.200.106/48002
    Aug 25 01:56:20:279 [2684] Controller: RREPLY: status=OK(0) <-10.6.200.106/48002 h=37 d=50
    Aug 25 01:56:20:279 [2684] Controller: SREQUEST: _close ->10.6.200.106/48002
    Aug 25 01:56:20:279 [2684] Controller: (probe_config_get) - called from 10.6.200.106/58766
    Aug 25 01:56:20:279 [7112] Controller: handle_probe_config_get: finding value of section=/spooler, key=origin
    Aug 25 01:56:20:279 [7112] Controller: handle_probe_config_get : could not find value of section=/spooler, key=origin
    Aug 25 01:56:20:279 [7112] Controller: SREPLY: status = 4(not found) ->10.6.200.106/58766
    Aug 25 01:56:20:279 [7112] Controller: SREQUEST: _close ->10.6.200.106/58766
    Aug 25 01:56:21:995 [2684] Controller: RREQUEST: _status <-10.6.200.106/58768 h=285 d=0
    Aug 25 01:56:21:995 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58768
    Aug 25 01:56:22:011 [2684] Controller: RREQUEST: _close <-10.6.200.106/58768 h=284 d=0
    Aug 25 01:56:22:011 [2684] Controller: RREQUEST: get_info <-10.6.200.106/58769 h=286 d=0
    Aug 25 01:56:22:011 [2684] Controller: get_info from 10.6.200.106/58769
    Aug 25 01:56:22:011 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58769
    Aug 25 01:56:22:026 [2684] Controller: RREQUEST: _close <-10.6.200.106/58769 h=284 d=0
    Aug 25 01:56:22:026 [2684] Controller: RREQUEST: gethub <-10.6.200.106/58770 h=284 d=0
    Aug 25 01:56:22:026 [2684] Controller: gethub from 10.6.200.106/58770
    Aug 25 01:56:22:026 [2684] Controller: SREPLY: status = 0(OK) ->10.6.200.106/58770
    Aug 25 01:56:22:042 [2684] Controller: RREQUEST: _close <-10.6.200.106/58770 h=284 d=0
    Aug 25 01:57:00:555 [2684] Controller: **** Request Queue Statistics ****
    Aug 25 01:57:00:555 [2684] Controller: * Hub Queue:
    Aug 25 01:57:00:555 [2684] Controller: * Current size : 0 requests
    Aug 25 01:57:00:555 [2684] Controller: * Maximum size reached (this period) : 1 requests
    Aug 25 01:57:00:555 [2684] Controller: * Maximum size reached (from startup) : 2 requests
    Aug 25 01:57:00:555 [2684] Controller: * Maximum size reached at : Fri Aug 12 10:24:31 2016
    Aug 25 01:57:00:555 [2684] Controller: * Probe Queue:
    Aug 25 01:57:00:555 [2684] Controller: * Maximum size reached at : Fri Aug 12 10:29:27 2016

     

     

    Regards,
    San



  • 4.  Re: Nimbus unable to reach agent

    Broadcom Employee
    Posted Aug 22, 2016 06:20 PM

    If the hub version is 7.x and uses tunnel connection, please try the settings in the following KB article and see if it helps.

     

    hub and tunnel connection settings in 7.x
    http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec000004536.aspx?intcmp=searchresultclick&resultnum=1



  • 5.  Re: Nimbus unable to reach agent

    Broadcom Employee
    Posted Aug 22, 2016 11:08 PM

    Hi,

    In case you are getting false robot inactive alarms you can also try with the

    hub_780HF14.zip

     

    http://www.ca.com/us/support/ca-support-online/product-content/recommended-reading/technical-document-index/ca-unified-infrastructure-management-hotfix-index.aspx?intcmp=searchresultclick&resultnum=1

     

    Hub 7.80HF14 fixes the following issues:

     

    - Tunnel instability  (hub 7.80HF9 contains the same improved tunnel code as hub 7.72)

    - Infrastructure Manager runs slowly when a remote hub is down

    - False robot inactive alerts

     

    It can be applied to any version of UIM and for best results, all hubs in the environment should be set to the same version.