Sun Storage 7000 Unified Storage System: SNMP is not Responding and is set to Transition State

Asset ID:	1-72-1613073.1
Update Date:	2016-02-15
Keywords:

Solution Type Problem Resolution Sure

Solution 1613073.1 : Sun Storage 7000 Unified Storage System: SNMP is not Responding and is set to Transition State

Applies to:

Sun Storage 7310 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7210 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun Storage 7110 Unified Storage System - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7420 - Version All Versions to All Versions [Release All Releases]
Sun ZFS Storage 7320 - Version All Versions to All Versions [Release All Releases]
7000 Appliance OS (Fishworks)

Symptoms

SNMP is not responding to requests.

Changes

No changes were reported.

Cause

The root cause was that SNMP was not restarting, so SNMP services were not actually running - even though the service appeared to be online.

configuration services snmp> ls

Properties:	      <status> = online 
                     community = public
                       network = x.x.x.x/32 
                    syscontact = customer_name@customer_domain
                     trapsinks = x.x.x.x

This SNMP service was transitioning to offline since Nov 04 - in this example, that was over a month (!)

To check the state, run:

confirm shell svcs |grep snmp

online* 14:04:54 svc:/application/management/net-snmp:default
online 14:04:54 svc:/system/fm/snmp-notify:default

The * means the service is in the transition state.

confirm shell svcs -l net-snmp
fmri svc:/application/management/net-snmp:default
name net-snmp SNMP daemon
enabled true
state online
next_state offline <<<<< here >>>>>
state_time Mon Nov 04 10:45:00 2013

Solution

1. From the CLI, disable the SNMP service

configuration services snmp> disable

( The CLI hung at this point in this example, so aborted the command by 'ctrl-C' to get control of CLI back, it still went to disabled )

2. Confirm the service is disabled

    configuration services snmp> ls

    Properties:
                      <status> = disabled
		      community = public
                       network = x.x.x.x/32 
                    syscontact = customer_name@customer_domain
                     trapsinks = x.x.x.x

3. Then restart svc.startd , by killing its process

CLI> confirm shell pgrep svc.startd

83 <<< this is the process to kill so

CLI> confirm shell kill 83

4. Check the process restarts - svc.startd should always restart, if it does not, please log a support call.

CLI> confirm shell tail -5 /var/svc/log/svc.startd.log

    Nov  4 11:14:19/6: instance svc:/system/console-login:default exited with status 1
    Dec 19 14:02:44/1: restarting after interruption  <<  this is good

5. Re-enable the SNMP service via the CLI:

configuration services snmp> enable

6. Confirm that the SNMP service is online:

configuration services snmp> ls

   Properties:
                      <status> = online

                     community = public
                       network = x.x.x.x/32 
                    syscontact = customer_name@customer_domain
                     trapsinks = x.x.x.x

7. Now check for the 'transition' state:

    CLI> confirm shell svcs |grep snmp
    online 14:04:54 svc:/application/management/net-snmp:default
    online 14:04:54 svc:/system/fm/snmp-notify:default

... there is no * by the service state (online)

Attachments

This solution has no attachment