what is the core os SLES 12 SPx or SLES 15 SPX

It is SLES 15 SP4

I have to add another question: which GW version?

I can remember there were issues with older GW versions ...

Currently running GW18.1

Running LDD against the file generates 

undefined symbol: snmp_free_varbind (./libgwsnmp.so)
undefined symbol: read_module (./libgwsnmp.so)
undefined symbol: snmp_set_var_typed_value (./libgwsnmp.so)
undefined symbol: shutdown_mib (./libgwsnmp.so)
undefined symbol: init_mib (./libgwsnmp.so)
undefined symbol: send_trap_vars (./libgwsnmp.so)
undefined symbol: add_mibdir (./libgwsnmp.so)
undefined symbol: snmp_set_var_objid (./libgwsnmp.so)
undefined symbol: snmp_log (./libgwsnmp.so)
undefined symbol: netsnmp_register_handler (./libgwsnmp.so)
undefined symbol: netsnmp_create_handler_registration (./libgwsnmp.so)
undefined symbol: init_mib_internals (./libgwsnmp.so)
undefined symbol: snmp_varlist_add_variable (./libgwsnmp.so)
undefined symbol: snmp_vlog (./libgwsnmp.so)

Have you seen this ... www.novell.com/.../gw18_readme.html

Thanks.  Looks like we will have to go the upgrade route to resolve.

Please remember that from GW 18.5 there may be a topic with certificates. There are many references to this in the forum. In GroupWise itself, the server FQDN must be set everywhere instead of IP (there is only one exception), it may be that the GroupWise internal CA has to be redone, here it must be strictly ensured that in the Self Signed certificate in the CN the server FQDN is to be found instead of the IP and GroupWise WebAccess goes as far as I remember up to version 18.3.

If WebAcess is absolutely necessary, there is a post here on how this can be implemented.

@ Diethmar, thanks you were quick again, I wanted to know the Core OS first and then see if the Core OS is released for the GroupWise version. cessary, there are also hints here in the forum, otherwise you have to deal with GW Web.

George

I dropped snmp monitoring of gw agents a long time ago. Too cumbersome. However gw agents have all the stats available in xml format, and most of them display the correct information, only some of it is wrong.

For example:

curl -s -k -H "Content-Type: text/xml" -H "Accept: text/xml" -X GET --user-agent "GWMonitor" --user $username:$password https://$serverfqdn:7181

I wrote my own script to filter the important data and push it to our monitoring system.

I have some customers who check and watch GW agents with CheckMK.