On Messaging Server 6.3, Service Management Facility, and SNMP

Quick Summary

For Messaging Server 6.3 on Solaris 10 6/06 U2, there does not seem to be a way to automate startup using SMF if snmpd is required. Manually starting/restarting snmpd seems unavoidable. The problem does not occur if you are using a full initial installation of Solaris OS 10 (Update 3).

The Complete Story

One of our Messaging Server experts alerted me to a situation that he came across involving Messaging Server 6.3, the Service Management Facility (SMF), and auto-enabling SNMP. The problem occurs only on Solaris OS 10 6/06 (Update 2) (but might have existed previously as well). He did not experience this problem on Solaris OS 10 (Update 3) using a full initial installation.

This then, seems to be the situation. In brief, if you have Messaging Server 6.3 on Solaris OS 10 U2, there does not seem to be a way to automate startup using SMF if snmpd is required. Manually starting/restarting snmpd seems unavoidable.

The situation was only reproducible by installing Update 2 and performing a live upgrade to Update 3 (11/06). The problem exists in U2 and remains if U3 is applied this way. However, you can apply 10_Recommended (in two passes) to either a U2 installed host or one live upgraded to a U3 host to solve the problem. (Using the 10_Recommended bundle did "undo" edits to the snmp.conf file of appending the line containing "master agentx" to the file, but once this was added in again, running messaging with snmp enabled was successful.)

Here are the tested scenarios that led to this conclusion:

Scenario #1: Manually Start Services

  1. Machine is fresh booted without SMF controlling snmp or messaging.
  2. Log in and become root.
  3. Run /etc/init.d/init.sma start (/usr/sfw/sbin/snmpd shows in 'ps -ef').
  4. Run /opt/SUNWmsgsr/sbin/start-msg (all services start).
    Side note: madmand and watcher processes are owned by root, other processes are owned by mailsrv.
Summary: Successful, until next reboot, when you need to restart services need to manually. No automation.

Scenario #2: Manually start services via SMF

  1. Machine is fresh booted without SMF controlling snmp or messaging.
  2. Log in and become root.
  3. Run svcadm enable sma (/usr/sfw/sbin/snmpd shows in 'ps -ef').
  4. Run svcadm enable messaging (all services start).
Note: Using a modified jes-messaging.xml manifest, all of the restart_on settings were set to none, and a dependency for svc:/application/management/sma:default grouped as optional_all was added.

Summary: Successful, until next reboot, messaging gets put into maintenance mode by SMF. Automation fails. You need to force stop snmpd with /etc/init.d/init.sma stop before messaging fault can be cleared with svcadm clear messaging. Manual intervention is successful. Still no automation.

Scenario #3: SMF controls just snmpd

  1. Machine is fresh booted with SMF controlling snmp, not messaging.
  2. Log in and become root.
  3. Run svcs sma (online).
    (/usr/sfw/sbin/snmpd shows in 'ps -ef')
    (snmpwalk -Os -c public -v 1 localhost system gives output)
  4. Run /opt/SUNWmsgsr/sbin/start-msg (starts all but madmand).
    (watcher, enpd, imsched, dispatcher, job_controller running) SMF is removed from step 4. SNMP is running. Cannot test for successful "master agentx" configuration? Same position as scenarios #1 and #2 after reboot.
  5. /etc/init.d/init.sma stop (SMF restarts snmpd before you can even see it happen, but /usr/sfw/sbin/snmpd does have a new pid).
  6. /opt/SUNWmsgsr/sbin/start-msg snmp (madmand running)

Summary: Automation fails. You need to manually restart snmpd and messaging subagent needs manual start. Close but no cigar.

Scenario #4: SMF controls snmpd and messaging, local.snmp.enable=0

  1. Machine is fresh booted.
  2. Log in and become root.
  3. Run svcs sma (online).
  4. Run svcs messaging (online).
  5. Run /opt/SUNWmsgsr/sbin/start-msg snmp (WARNING: snmp is disabled).
  6. Run /opt/SUNWmsgsr/sbin/configutil -o local.snmp.enable -v 1.
  7. Run /opt/SUNWmsgsr/sbin/start-msg snmp (error initializing).
  8. Run /etc/init.d/init.sma stop (auto restarted by SMF).
  9. Run /opt/SUNWmsgsr/sbin/start-msg snmp (success).

Summary: There does not seem to be a way to automate startup if snmpd is required. Manually starting/restarting snmpd seems unavoidable.

Comments:

Can you please publish jes-messaging.xml file.
Thanks.

Posted by guest on November 16, 2007 at 06:59 AM MST #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Reporting about Unified Communications Suite Documentation, including news, Comms 101, documentation updates, and tips and tricks.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today