SnmpWalk fails with Timeout: No Response for ILOM

Asset ID:	1-71-2313132.1
Update Date:	2017-10-03
Keywords:

Solution Type Technical Instruction Sure

Solution 2313132.1 : SnmpWalk fails with Timeout: No Response for ILOM

Applies to:

Sun SPARC Enterprise T5440 Server - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.

Goal

While running SnmpWalk for oracle ilom, getting error "Timeout: No Response", though snmp(v2c) is enabled and configured in ilom.

Hardware - SPARC Enterprise T5440
ILOM - Version 3.0.10.3.a r59348
System FW: 7.2.10.a 2010/10/08 16:40

-> show

/SP/services/snmp
Targets:
communities
mibs
users

Properties:
engineid = (none)
port = 161
servicestate = enabled
sets = disabled
v1 = disabled
v2c = enabled
v3 = disabled

/SP/services/snmp/communities/public
Properties:
permission = ro

@ilom/@usr@local@bin@spshexec_show_-script_@X@logs@event@list.out
23675 Fri Sep 22 15:12:06 2017 Audit Log minor root : Open Session : object = "/SP/session/type" : value = "shell" : success
23614 Fri Sep 22 11:06:47 2017 Audit Log minor root : Set : object = "/SP/alertmgmt/rules/1/community_or_username" : value = "public" : success
23613 Fri Sep 22 11:06:15 2017 Audit Log minor root : Set : object = "/SP/alertmgmt/rules/1/snmp_version" : value = "2c": success
23555 Fri Sep 22 09:24:38 2017 Audit Log minor root : Set : object = "/SP/network/test/ping" : value = "x.x.x.125" : success
23554 Fri Sep 22 09:24:34 2017 Audit Log minor root : Set : object = "/SP/network/test/ping" : value = "x.x.x.124" : success
23553 Fri Sep 22 09:24:29 2017 Audit Log minor root : Set : object = "/SP/network/test/ping" : value = "x.x.x.123" : success
23548 Fri Sep 22 09:21:01 2017 Audit Log minor root : Set : object = "/SP/network/test/ping" : value = "x.x.x.1" : success

Error as shown below while running SNMPWalk from remote machine to ilom,

x.x.x.85= ilom ip

#snmpwalk -c public -v2c x.x.x.85
Timeout: No Response from x.x.x.85

Solution

- check ilom network is configured and able to ping from network

-> show /SP/network

- ensure snmp is enabled and configured in ilom

-> show /SP/services/snmp

- reset service processor

-> reset /SP

if the above actions do not resolve, the next step will be to open a service request with oracle support.

sp reset resolved the issue under SR 3-15795109061.

Attachments

This solution has no attachment