6 Replies Latest reply on Apr 4, 2012 4:20 PM by richard mcleod

    BladeLogic RSCD Agent Licensing data flow

    richard mcleod

      Looking for information around the way agent's are licensed. Reason being is my application servers are in a firewalled environment and I have been receiving some of the following errors when running autolic nsh jobs.

       

      Error Apr 4, 2012 3:47:15 PM SOAP FAULT: SOAP-ENV:Client

      Error Apr 4, 2012 3:47:15 PM "Connection timed out"

      Error Apr 4, 2012 3:47:15 PM Detail: TCP connect failed in tcp_connect()

      Error Apr 4, 2012 3:47:15 PM Unable to contact BladeLogic licensing service

      Error Apr 4, 2012 3:50:24 PM SOAP FAULT: SOAP-ENV:Client

      Error Apr 4, 2012 3:50:24 PM "Connection timed out"

      Error Apr 4, 2012 3:50:24 PM Detail: TCP connect failed in tcp_connect()

      Error Apr 4, 2012 3:50:24 PM Unable to contact BladeLogic licensing service

       

      I'm assuming by the messages above that the application server is acting as a handshake for licenses between the agent and the web service.

      The flow I imagine works like this: (italics=data, underline=service/host)

       

      AppServer --> autolic user pass server --> BMC WebService --> license --> AppServer --> license --> RSCD Agent

       

      Can anyone confirm if this is correct?

       

      Also looking for licensing target information: dns name/ip + port + protocol. I will most likely need to raise additional firewall rules to allow this traffic