Workload Automation Agents

 View Only
  • 1.  Agent configuration and connection to Schedule master.

    Posted Jan 21, 2021 11:11 AM
      |   view attached
    Good Morning everyone,
    I have recently been upgrading some test agents to version 12 built 6181 service pack and maintenance level 00, in the current environment we have 8 agents 7 of which are configured correctly, actively talking to the schedule master (ESP), executing workload no issues seen. With the 8th server (windows 2012 R2) The install was completed as all the other servers were however I am receiving a send err. The transmitter log states an invalid message header, invalid protocol type. This typically tells me something in the communication encryption is incorrect. This server is configured with AES encryption checking both the encryption key on the server and on the schedule master multiple times. regening the key using the keygen function changing the encryption type to DES receiving the same error. I have gone as far as reinstalling the agent from scratch multiple times. Looking for the next lead to figure out what is going on. I have attached the transmitter log. Thanks in advance for any lead possibilities.

    Attachment(s)

    txt
    transmitter.txt   834 KB 1 version


  • 2.  RE: Agent configuration and connection to Schedule master.

    Posted Jan 21, 2021 12:08 PM

    Can you post the Agent definition in ESP and the agentparm.txt?

    Of the 8 Agents is this the only one using AES encryption?

    What do you see in the Job Output from ESP?

    Have you tried going back to the previous agent version on the non-working server?



    ------------------------------
    Senior Systems Analyst
    UPS
    ------------------------------



  • 3.  RE: Agent configuration and connection to Schedule master.

    Posted Jan 21, 2021 12:23 PM

    All agents are using AES encryption. Agent parm is attached.

     

    Page Mode shows a send err, job submission gives transmission error.

    This shows up in the ESP main log file 12.14.49 STC29251  GDCM1546E Error sending a message to WGFCTS03

     

    Parmlib definitions. AGENT WGFCTS03 is the one not working the one below it is working just fine.

    AGENT WGFCTS03  ADDRESS(WGFCTS03) PORT(7520) NT ASCII  -

         TCPIP  PREFIXING ENCRYPT KEY(WGFCTS03)             

                                                             

    AGENT WFCTSGV2  ADDRESS(WFCTSGV2) PORT(7520) NT ASCII  -

          TCPIP  PREFIXING ENCRYPT KEY(WFCTSGV2)            

                                                             

     

     

    Dustin Neely
    DevOps Analyst/Certified Automation button pusher

    W 423.535.5784
    M 423.208.6255
    E Dustin_Neely@bcbst.com
    www.bcbst.com

    Batch Scheduling Wiki

     

     

     

     



    Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer:  https://www.bcbst.com/about/our-company/corporate-governance/privacy-security/email-policy.page

    This email was sent by "Neely, Dustin" <dustin_neely@bcbst.com> securely using Transport Layer Security (TLS).</dustin_neely@bcbst.com>






  • 4.  RE: Agent configuration and connection to Schedule master.

    Broadcom Employee
    Posted Jan 22, 2021 08:53 AM
    Hi Dustin,
    So, R12 was not tested on Windows 2012, because OS was out of mainstream support when agent was released.  Anyhow, here it looks like encryption type is not same between ESP and agent.
    01/21/2021 09:53:19.517-0500 1 TCP/IP Controller Plugin.Transmitter pool thread <Regular:1>.CybTargetHandlerChannel.a[:617] - Error sending message to GD_MANAGER1:   cybermation.library.communications.CybConversationException: Invalid message header, invalid protocol type 	at cybermation.library.communications.protocol.CybCommunicationProtocolDynamic.receiveData(CybCommunicationProtocolDynamic.java:763)
    If you can, attach receiver and agent_properties log.

    Nitin Pande


    ------------------------------
    Support
    Broadcom
    Toronto
    ------------------------------



  • 5.  RE: Agent configuration and connection to Schedule master.

    Posted Jan 22, 2021 11:36 AM
      |   view attached
    Everyone thank you for the replies.

    1. I need to make a correction i stated this was a 2012 server above that is incorrect it is a 2016 server.

    2. I now have rolled back to version 11.4 with success. the agent is up and running and workload is submitting using local security and AES encryption.

    I will continue working to identify the issue.

    For those who asked i have posted the agentparm.txt file

    Attachment(s)

    txt
    agentparm.txt   2 KB 1 version


  • 6.  RE: Agent configuration and connection to Schedule master.

    Posted Jan 22, 2021 03:00 PM
    here are the transmitter and receiver logs.

    Attachment(s)

    log
    transmitter.log   481 KB 1 version
    log
    receiver.log   3 KB 1 version


  • 7.  RE: Agent configuration and connection to Schedule master.

    Broadcom Employee
    Posted Jan 22, 2021 03:12 PM
    Edited by Nitin Pande Jan 22, 2021 03:11 PM
    Hi,
    I see that you have defined manager ID in agentparm as this:

    communication.managerid_1=GD_MANAGER1

    But I see this as the manager ID coming from ESP:

    01/21/2021 12:14:50.904-0500 2 TCP/IP Controller Plugin.Receiver pool thread <Regular:1>.CybReceiverSession.accept[:292] - Message received: 20210121 12144915+0500 WGFCTS2A GDCMSTR . .....

    You need to make sure that ID matches on agent side exactly as it is on ESP side.  Edit your agentparm, edit to correct ID and restart.

    HTH,

    Nitin Pande

    ------------------------------
    Support
    Broadcom
    Toronto
    ------------------------------



  • 8.  RE: Agent configuration and connection to Schedule master.

    Posted Jan 22, 2021 03:38 PM

    Yes that was one problem fixed and then it has come down to having the wrong port defined.

     

    Dustin Neely

    DevOps Analyst/Certified Automation button pusher

    P – 423-535-5784

    E – Dustin_Neely@bcbst.com

    Batch Scheduling Wiki