XMA: How to optimize SLSENDER to handle multiple SIEMs for version XMA 2.70 and higher

XMA: How to optimize SLSENDER to handle multiple SIEMs for version XMA 2.70 and higher

SLSENDER must be optimized for the number of SIEMS and transactions

1. SLSENDER can be configured in XMA_MANAGER. 
 

>run xma install
>XMA_MANAGER
>2: Movers
>18: Configure SysLog Send server


2. In the SysLog Send server menu (SLSENDER), the Max Number of Open Transactions (option 7) should be at least SIEM COUNT(option 15) multiplied by MAX NUMBER OF MESSAGES  (option 6).
 

5:   Max Number of Messages in a Connection Queue       :10
6:   Max Number of Pending IO callss                    :10
13:  Number of SIEMs to optimize processing for         :1


Therefore the value of option 6 >= the value of option 13 * the value of option 5.

If you are unable to locate the solution needed or if you need additional assistance please Click Here to open a case from our Customer Care Portal.


    • Related Articles

    • XMA: How do I optimize SLSENDER to handle multiple SIEMs for version XMA 2.65 or earlier

      SLSENDER must be optimized for the number of SIEMS and transactions 1. SLSENDER can be configured in XMA_MANAGER. >run xma install >XMA_MANAGER >2: Movers >18: Configure SysLog Send server) 2. In the SysLog Send server menu (SLSENDER), the Max Number ...

    • XMA: How to optimize SLSENDER to handle multiple SIEMs

      SLSENDER must be optimized for the number of SIEMS and transactions 1. SLSENDER can be configured in XMA_MANAGER. >run xma install >XMA_MANAGER >2: Movers >18: Configure SysLog Send server) 2. In the SysLog Send server menu (SLSENDER), the Max Number ...

    • XMA: How to uninstall SLSENDER.

      As the SLSENDER is configured and added to the XMA pathway when the customer follows the installation process in the XMA manual. The following procedure can be used to manually stop the SLSENDER , remove any records that have been generated, and stop ...

    • XMA: SLSENDER fails to start after upgrading to Merged Audit 2.65

      There is a known issue where SLSENDER will not start after upgrading to XMA 2.65. If the customer cannot start SLSENDER after upgrading, the post upgrade steps below can be used. If we know a customer will be upgrading to XMA 2.65, pre-upgrade steps ...

    • XMA: SLSENDER - Steps to follow for SLSENDER When Upgrading to XMA 2.65

      The upgrade to XMA 2.65 makes changes to the SYSLOGQ table. Consequentially, this could cause fatal errors for SLSENDER when it it initially started following the upgrade. This is due to outstanding TMF transactions that remains until they are ...