Not reported status between BFserver e pc

Usage and Config
1

Hi everyone, I am having problems with bigfix 9.5, premising that I have already checked for errors due to the compatibility of my bigfix server with the other components. My problem is that when I launch the installation of the disconnected scanners on the computers via fixlet, I get an error given by as if the bes agent could not get to the machines, I have already checked that oprta 52311 was open and I understand that the PCs are communicating with the server correctly. The question is what could the error be due to that is not letting me get the parts communicating?

thank you

2

I think we might need some more detail on what you’re trying to do. Which Disconnected Scanner are you talking about? Can you give us the fixlet site and fixlet ID?

I’m not sure I understand why one would run a Disconnected Scanner on a machine that has a connected BESClient (at least if you mean the BigFix Inventory disconnected scanner…)

3

fixlet ID is 00-229 - install disconnected Scanner on UNIX. . I launched the installation of disconnected scanners from a BFClient because after migration I have to make the computers communicate with bigfix and ilmt

4

What site is that fixlet in? I’m not seeing it in ‘IBM License Reporting (ILMT) v9’, is it elsewhere?

5

Perhaps that’s the Action ID. There is a Task ID:1008 called install the Disconnected Scanner on Unix (9.2.38.0).

6

yes, it is in IBM License Reporting (ILMT) V9 , i would install the disconnected scanned on unix 9.2.38 in the computers, but the status of the action is ‘not reported’. The UDP gate 52311 confirmed is enabled. how can I solve this unreported status?

7

Ok, and are you getting an error message, or they’re just staying ‘Not Reported’ ?

‘Not Reported’ usually means the client has not received the UDP notification and is not aware of the existence of the new action. That may be any firewall in between, or host-based firewall on the endpoint, blocking UDP. To workaround UDP notification blockages we’d normally suggest Command Polling or Persistent Connections. Otherwise you could restart the BESClient server on the endpoint, or wait for it to perform a relay selection (every 6 hours by default) and at that time it will see the new action.

If you’re actually getting an error (besides ‘Not Report’) for the action, we’ll need some more details. You may be better off opening a Support ticket to get live support.