Inventory Agent Server endpoints

Portal User asked a question.

July 6, 2021 at 9:48 AM

Anyone know if there's a limit to how many server endpoints that can be configured in the Snowagent.config file? We use 2 for our customers for their internal service gateway and then our hosted master inventory server.

Anyone have experience of using more??

Thanks

Adam

Top Rated Answers

Detlev Eufinger (Flexera Software)
5 years ago
Hi Adam -QBS

Snow Inventory Agent works when choosing an endpoint to send the inventory scan results (when there are multiple endpoints configured):
the first time it runs it tries them (in the same order they are specified) until one of them responds correctly
then the information on the valid endpoint is saved and used as the preferred (first one tried) from then on
in the case the valid endpoint stops responding, the information on the last good known endpoint is scrapped and the cycle starts from the first point
Note:
The more server endpoints defined in the agent configuration, the longer it will take to negotiate a connection. This is typically not an issue but when writing scripts, keep in mind that it may introduce a significant delay since the agent has to timeout on a bad server endpoint configuration before it can try the next one.

So from this perspective, we have no limitations!!
Expand Post
Selected as Best

All Answers

piideleteJune
5 years ago
The most I've ever had the "pleasure" of using in a config was 5 specified GW's and one direct to master server - don't ask why :-)
Expand Post
- Laim McKenzie
  5 years ago
  We found there was no real limit when we had to add in 10 GWs and the master
  
  I mean.. it worked... :p
  Expand Post
Detlev Eufinger (Flexera Software)
5 years ago
Hi Adam -QBS

Snow Inventory Agent works when choosing an endpoint to send the inventory scan results (when there are multiple endpoints configured):
the first time it runs it tries them (in the same order they are specified) until one of them responds correctly
then the information on the valid endpoint is saved and used as the preferred (first one tried) from then on
in the case the valid endpoint stops responding, the information on the last good known endpoint is scrapped and the cycle starts from the first point
Note:
The more server endpoints defined in the agent configuration, the longer it will take to negotiate a connection. This is typically not an issue but when writing scripts, keep in mind that it may introduce a significant delay since the agent has to timeout on a bad server endpoint configuration before it can try the next one.

So from this perspective, we have no limitations!!
Expand Post
Selected as Best
Portal User
5 years ago
Thanks Both - that's what I thought... just worth a check :-)
Expand Post

Related Product Forums

→ Flexera One

→ Snow Atlas

→ FlexNet Manager

→ Snow License Manager

→ App Broker

Need help finding an answer?

Ask a Question →