How to get SNMP configured on SLES15 or SLES15 SP1 with GroupWise 18.2

  • 7024336
  • 11-Dec-2019
  • 01-Apr-2020


GroupWise 18 SP2
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 15 SP1


How can I configure SLES 15 or SLES 15 SP1 to allow SNMP monitoring of GroupWise 18 SP2 agents


How to get SNMP configured on SLES15 or SLES15 SP1 with GroupWise 18.2

You can monitor the GroupWise agents from SNMP management and monitoring programs. When properly configured, the GroupWise agents send SNMP traps to network management consoles for display along with other SNMP monitored programs.

NOTE:  You should normally have these 3 snmp libraries installed on SLES15: 

     You can use this terminal command to verify you have the needed snmp libraries:   

       rpm –qa | grep snmp

NOTE:  In the below examples “5.7.3” and “7.6.1” are the Version and Release numbers for these

snmp rpms, yours may be a different number than what I have listed below.

a.       snmp-mibs-5.7.3-7.6.1.x8_64

b.       libsnmp30-5.7.3-7.6.1.x86_64

c.       net-snmp-5.7.3-7.6.1.x86_64

If you do not have these libraries installed you can use YAST to install them.

1.        On SLES15, as “root” at a terminal cd to /etc/snmp

2.       Edit the file “snmpd.conf”, it may be a good idea to make a backup copy of this file.  If you do not have one you can create a new empty file in this directory called “snmpd.conf”.

3.       Make it look like this :


# Please see /usr/share/doc/packages/net-snmp/EXAMPLE.conf for a

# more complete example and snmpd.conf(5).


# Writing is disabled by default for security reasons.  If you'd like

# to enable it uncomment the rwcommunity line and change the community

# name to something nominally secure (keeping in mind that this is

# transmitted in clear text).


# don't use ' < > in strings for syslocation or syscontact

# Note that if you define the following here you won't be able to change

# them with snmpset

syslocation Server Room

syscontact Sysadmin (root@localhost)


#agentAddress  udp:


# These really aren't meant for production use.  They include all MIBS

# and can use considerable resources.  See snmpd.conf(5) for information

# on setting up groups and limiting MIBS.

rocommunity public

# rwcommunity mysecret

dlmod Gwsnmp /opt/novell/groupwise/agents/lib/


4.       At /usr/lib/systemd/system, there should be a snmpd.service file.   Make a backup copy of this file.  Modify snmpd.service so it looks like the following:



Description=Simple Network Management Protocol (SNMP) Daemon.








ExecStart=/usr/sbin/snmpd -f

ExecReload=/bin/kill -HUP $MAINPID




5.       Before you start “snmpd”, you need to stop GroupWise with the command:

systemctl stop groupwise

6.       Run systemctl daemon-reload

7.       Run systemctl start snmpd

8.       Note:  You will now have a /var/log/Net-snmpd.log file

9.       Run systemctl start grpwise

10.   To run a simple test if snmp is working now , do these commands at a terminal on the server in which you configured snmp where GroupWise is installed :

a.       snmpwalk –c public –v2c .   ( for mta )

b.       snmpwalk –c public –v2c .   ( for poa )

c.       snmpwalk –c public –v2c .          ( for gwia )


11.   Common errors :

a.       “End of MIB”, when there is no other snmp response shown.

                                                               i.      Check log file /var/log/Net-smpd.log file

                                                             ii.      Check if your GroupWise agents have the http user name and password defined

                                                           iii.      If above is true, then check if you provide the common userID and password in the GroupWise Admin console for read-only access.

Additional Information

This is no support for SNMP monitoring for classic Webaccess (grpwise-tomcat) or GroupWise Monitor or GroupWise Calendar Publishing.