Sun Storage 7000 Unified Storage System: When SNMP community is changed, traps still show 'public' as the community

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

Solution Type Problem Resolution Sure

Solution 1525946.1 : Sun Storage 7000 Unified Storage System: When SNMP community is changed, traps still show 'public' as the community

Applies to:

Sun Storage 7210 Unified Storage System - Version All Versions and later
Sun Storage 7310 Unified Storage System - Version All Versions and later
Sun Storage 7410 Unified Storage System - Version All Versions and later
Sun ZFS Storage 7120 - Version All Versions and later
Sun ZFS Storage 7320 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

After changing the SNMP service configuration to a community other than "public", examining SNMP packets will still show the community set as public.

This does not affect the functionality of the service, systems that wish to read SNMP traps from an appliance will still need to specify the correct community if it has been changed from public.

However examining the SNMP trap packet itself, using tcpdump, wireshark, snoop, etc., will show the community still set as public.

e.g.

The SNMP configuration is changed such that the community is set to some other value than public:

lbl-262:configuration services snmp> show
Properties:
<status> = online
community = someothervalue
network = 0.0.0.0/0
syscontact = -
trapsinks = 192.168.0.10

The printable text from a test alert seen by wireshark:

<z"3DUExy$4

e`0YpublicJ0:0+C40 <=== **** THE COMMUNITY STILL SHOWS AS PUBLIC HERE ****
++*a0Z2+*a$21dd5738-e86b-43f8-c380-aa77bb7f42d4$21dd5738-e86b-43f8-c380-aa77bb7f42d40C2+*a$21dd5738-e86b-43f8-c380-aa77bb7f42d4alert.ak.test0S2+*a$21dd5738-e86b-43f8-c380-aa77bb7f42d4A test alert has been posted.0@2+*a$21dd5738-e86b-43f8-c380-aa77bb7f42d4
AK-8000-LM0;2+*a$21dd5738-e86b-43f8-c380-aa77bb7f42d4alert0;2+*a$21dd5738-e86b-43f8-c380-aa77bb7f42d4Minor0;2+*a $21dd5738-e86b-43f8-c380-aa77bb7f42d4None.0
++*a

Analyzing an SNMP trap dump using tcpdump:

dumph_recv: SNMPv2c message

dumph_recv:   SNMP version
dumpx_recv:    02 01 01
dumpv_recv:      Integer:       1 (0x01)
dumph_recv:   community string
dumpx_recv:    04 06 70 75 62 6C 69 63
dumpv_recv:      String:        public <=== **** THE COMMUNITY STRING IS STILL SET TO PUBLIC ***
dumph_recv:   PDU
dumpv_recv:     Command TRAP2

However looking from the client receiving the traps - the behaviour seems correct:

snmpwalk -v2c -c public <appliance IP>
Timeout: No Response from <appliance IP>

There is no response using the "public" community.

snmpwalk -v2c -c someothervalue <sppliance IP>
SNMPv2-MIB::sysDescr.0 = STRING: SunOS zs7420-tvp540-b-h2 5.11
ak/generic@2011.04.24.1.0,1-1.8 i86pc
SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs.3
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (7768304) 21:34:43.04
...

There is a response when using the correct "someothervalue" community.

Changes

The SNMP configuration has been changed so that the community is set to some other value than "public".

Cause

This is a known problem.

Solution

Please contact Oracle Support for more details.

This issue is fixed in Appliance Firmware Release 2013.1.2.0

See <Bug 15785448> for more details.

Fixed in 2013.1.2.0, for earlier releases contact phillip.hughes@oracle.com for a workflow workaround.

References

<BUG:15785448> - SUNBT7161273 SNMP TRAPS ARE SENT WITH PUBLIC COMMUNITY EVEN IF THIS WAS CUSTOMIZ
<NOTE:1408716.1> - Sun Storage 7000 Unified Storage System: How to Troubleshoot SMB (CIFS) Problems

Attachments

This solution has no attachment