cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Known Issue: Beacon prioritization is not performed when attempting downloads/uploads if any beacon selector algorithm cannot be loaded (IOJ-1810099)

Known Issue: Beacon prioritization is not performed when attempting downloads/uploads if any beacon selector algorithm cannot be loaded (IOJ-1810099)

Summary

If a configured selector algorithm for prioritizing beacon for upload/download operations cannot be loaded by the agent, then no prioritization is performed.

Details

This issue may be particularly evident on Unix-like operating systems, where the selector algorithm is commonly configured to include "MgsADSiteMatch" - but this algorithm only works on Windows.

Logging similar to the following is evident in the agent logs when this issue occurs:

[Wed 18 Jan 2017 01:56:21 PM PST (G, 0)] {23342} Uploading started
[Wed 18 Jan 2017 01:56:21 PM PST (G, 0)] {23342} 
------------------------------------------------------------
[Wed 18 Jan 2017 01:56:21 PM PST (N, 2)] {23342} Prioritizing servers for upload
[Wed 18 Jan 2017 01:56:21 PM PST (N, 2)] {23342} Starting to prioritize servers from "HKLM\Software\ManageSoft Corp\ManageSoft\Common\UploadSettings"
[Wed 18 Jan 2017 01:56:21 PM PST (N, 2)] {23342} Applying prioritization algorithm "MgsRandom" with parameters ""
[Wed 18 Jan 2017 01:56:21 PM PST (N, 2)] {23342} Applying prioritization algorithm "MgsPing" with parameters ""
[Wed 18 Jan 2017 01:56:21 PM PST (N, 2)] {23342} Applying prioritization algorithm "MgsADSiteMatch" with parameters ""
[Wed 18 Jan 2017 01:56:21 PM PST (N, 2)] {23342} SelectorAlgorithm "MgsADSiteMatch" could not be loaded
[Wed 18 Jan 2017 01:56:21 PM PST (N, 2)] {23342} ERROR: Could not successfully prioritize servers

Note that a failure like this does not impact the agent's ability to upload files to a beacon. However if beacon prioritization has not occurred because of this issue then the order in which connection attempts are made to beacons may not be optimal.

Workaround

Configure the selector algorithm to only use algorithms that can be loaded. In particular, ensure algorithm names that are not available on the operating system and not included.

For example, on Unix-like operating systems this could be achieved by executing commands like the following:

$ cat <<EOF >/tmp/mgsconfig.ini
[ManageSoft\NetSelector\CurrentVersion]
SelectorAlgorithm=MgsRandom;MgsPing
EOF

$ /opt/managesoft/bin/mgsconfig -i /tmp/mgsconfig.ini

Related information

See the following page for information about configuring the selector algorithm: Selecting Inventory Beacons > Saving the Configuration.

 

Fix status

This issue has been fixed in the following FlexNet Manager Suite releases: 2021 R1.4 / Mar 2022 (Cloud), 2022 R1 (On Premises)

Other information

Affected components: Agent

Master issue ID: IOJ-1810099

Also known as: FNML-75099

Labels (1)
Was this article helpful? Yes No

Tip: If you have been impacted by this issue, please click the KUDOS button above. This helps to track the relative significance and importance of issues. Clicking on an option against "Was this article helpful?" also helps assess and improve the usefulness of content.

No ratings
Comments

is this the proper way to set up the netselector?

 

; Registry settings to be created under
; HKLM\Software\ManageSoft Corp\ManageSoft\NetSelector
[NetSelector]
;desc0 = Description
;val0 = Value
; ... etc.
Desc0 = SelectorAlgorithm
Val0 = MgsDomainMatch
Desc1 = SelectorAlgorithm
Val1 = MgsBandwidth
Desc2 = SelectorAlgorithm
Val2 = MgsPing

or 

; Registry settings to be created under
; HKLM\Software\ManageSoft Corp\ManageSoft\NetSelector
[NetSelector]
;desc0 = Description
;val0 = Value
; ... etc.
Desc0 = SelectorAlgorithm
Val0 = MgsDomainMatch;MgsBandwidth;MgsPing

Version history
Last update:
‎Jun 12, 2022 03:52 AM
Updated by: