DX Unified Infrastructure Management

 View Only
  • 1.  post-could not get 'prid' from head PDS

    Posted Apr 06, 2020 06:37 PM
    Hi broadcom,

    We recently received this alert coming from spooler probe: "post-could not get 'prid' from head PDS". This is new to me and I couldn't see any article regarding the log. What does it mean? Is it ignorable? if no, how can we fix it? Thanks

    John


  • 2.  RE: post-could not get 'prid' from head PDS

    Posted Apr 06, 2020 07:02 PM
    Not familiar with this so it is just a copy past from a support case. 

    From hub-7.95 build, We have added a hard check in spooler for prid(probe id) field in qos and alarm message header. If prid field is not present, spooler will drop this message.

    If there are any custom QoS metrics or alarms defined at the robot a dummy prid will need to be added for the message to not get dropped. Also an enhancement request has been made in regards to this.

    ------------------------------
    Support Engineer
    Broadcom
    ------------------------------



  • 3.  RE: post-could not get 'prid' from head PDS

    Posted Apr 06, 2020 10:17 PM
    So how can we add a dummy prid? so that the messages doesn't get dropped


  • 4.  RE: post-could not get 'prid' from head PDS

    Broadcom Employee
    Posted Apr 07, 2020 09:13 AM
    what are you doing to generate the message without a prid?
    We would need to know this before we can help further.

    ------------------------------
    Gene Howard
    Principal Support Engineer
    Broadcom
    ------------------------------



  • 5.  RE: post-could not get 'prid' from head PDS
    Best Answer

    Posted Apr 07, 2020 08:25 PM
    We received this alert:  Unable to reset out-queue.

    Then someone did this procedure: 
    ♦ Stop spooler service
    ♦ Flushed spooler queues
    ♦ Started spooler service
    ♦ Restarted nimsoft service

    After that, I started seeing this "post-could not get 'prid' from head PDS" alerts




  • 6.  RE: post-could not get 'prid' from head PDS

    Posted Apr 07, 2020 09:54 AM
    This is a completely terrible "enhancement" to the spooler BTW. If the message does not come from a probe, it should not be required to carry a prid. We have a few integrations that push alarms into UIM from outside via the nimalarm command, and a blank probe name made the most sense for those. Now the nimalarm command sets the probe name to "TestAlarmProbe", which is completely ridiculous. There's no better way to get people to ignore alarms than to make them sound like they are coming from a test system.


  • 7.  RE: post-could not get 'prid' from head PDS

    Posted Apr 07, 2020 07:19 PM
    Hi Keith,
    I agree. Most customers are using the nimalarm executable to send real alarms into UIM, not for testing purposes.

    ------------------------------
    [Designation]
    [City]
    ------------------------------