Take a look at the facts that are gathered, the IP address you want are in there. Then just deploy your ini file using a template task, using the correct variable.
On Wed, 30 Mar 2022 at 17:20, Nitrous <[email protected]> wrote: > > Digging more, there is a ini file, that saves the IP for the server: > > ####################################################################### > # LogRhythm System Monitor Agent Configuration File > # Copyright 2008-2017 LogRhythm, Inc. > # > # Comments begin with '#', blank lines are ignored > ####################################################################### > > # Mediator sections - up to 3 Mediators are supported > # Each Mediator has its own section with an incrementing header number: > [Mediator n] > [General] > # Default scsm.log logging level is VERBOSE > LogLevel=4 > EntityID= > [Mediator 1] > > # IP address or DNS name of the Mediator this Agent will connect to. > Host=xx.xx.xx.xx > > # Port number the Mediator is listening on > ServerPort=443 > > # IP address or index of the address to use for transmitting messages to the > Mediator. > # This is either a static IP v4/v6 address (recommended) or the zero-based > index of the > # address to use from a list of all available IP addresses. The family > (i.e., IP v4/v6) > # is dependent on the Host property above. Valid values are: > # > # - static IP v4/v6 Address > # - index of address to use, for example: > # - '0' for the first available IP address > # - '2' for the third available IP address > ClientAddress=xx.xx.xx.xx > > # Port number to use for transmitting messages to the Mediator. > ClientPort=0 > > The bolded part needs to be filled in with the IP of the current primary NIC. > > What I can do, using ansible, install the exe for the agent, copy the > scsm.ini file from an existing server. > > But how can I then fill in the IP section for the server in the ini file? > > On Wednesday, March 30, 2022 at 9:04:33 AM UTC-5 Nitrous wrote: >> >> So we have an agent that we need to push to our servers, and below is the >> command to run it: >> >> LRSystemMonitor.exe /s /v" /qn ADDLOCAL=System_Monitor HOST=xx.xx.xx.xx >> SERVERPORT=443 CLIENTADDRESS=0 CLIENTPORT=3333" >> >> Only issue is this part: >> CLIENTADDRESS=0 >> >> The CLIENTADDRESS portion needs to have the local IP of the server and not >> 0. i.e CLIENTADDRESS=10.10.10.1 for example. >> >> We have to push this agent to 500+ servers in our environment, we can >> install using the above script, but I am not exactly sure, how we can make >> the clientaddress point to the IP of the primary NIC of the server to be >> installed on, by itself. >> >> >> > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/fea50ad0-1c12-41ea-a670-186fcd852d0cn%40googlegroups.com. -- Dick Visser Senior Trust & Identity Infrastructure Architect GÉANT -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAL8fbwPfPpm6pZAvTXevQH7fMsVx%2BVO7ci1a7xN6hch9a%2BAOCQ%40mail.gmail.com.
