Discussion:
snmp responding from V240 ALOM but docs say it's not supposed to
(too old to reply)
Scott
2010-09-07 22:13:54 UTC
Permalink
I have a Sun Fire V240 with the latest OBP upgrade dated Feb/09/2010:
OBP 4.30.4.a, POST 4.30.4.a, OBDIAG 4.30.4.a
When I telnet to the network mgmt port it says "ALOM 1.3".

My security dept. says it's responding to snmp on it's network
management port
(this isn't on a port the OS uses).
What I've been able to look up through sunsolve and Google says it
doesn't have snmp capability. With Windows-based tool, snmpwalk, I
can get a response:
$ snmpwalk -v 2c -c public -m ALL <my IP address>
SNMPv2-MIB::sysDescr.0 = STRING: VxWorks SNMPv1/v2c Agent
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::zeroDotZero
DISMAN-EXPRESSION-MIB::sysUpTimeInstance = Timeticks: (26852104) 3
days, 2:35:2
.04
SNMPv2-MIB::sysContact.0 = STRING: Wind River Systems
SNMPv2-MIB::sysName.0 = STRING: rsc
SNMPv2-MIB::sysLocation.0 = STRING: Planet Earth
SNMPv2-MIB::sysServices.0 = INTEGER: 79
Error in packet.
Reason: resourceUnavailable (This is likely a out-of-memory failure
within the
gent)


$ snmpwalk -v 1 -c public -m ALL <my IP address>
SNMPv2-MIB::sysDescr.0 = STRING: VxWorks SNMPv1/v2c Agent
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::zeroDotZero
DISMAN-EXPRESSION-MIB::sysUpTimeInstance = Timeticks: (26856492) 3
days, 2:36:0
.92
SNMPv2-MIB::sysContact.0 = STRING: Wind River Systems
SNMPv2-MIB::sysName.0 = STRING: rsc
SNMPv2-MIB::sysLocation.0 = STRING: Planet Earth
SNMPv2-MIB::sysServices.0 = INTEGER: 79
Error in packet.
Reason: (genError) A general failure occured


There's no ability to:
sc> showsc
and get back a "if_snmp" variable; If I try to set the variable to
false I get an error.

It's frustrating. Security thinks it's a problem. As far as I can
tell I can't disable it or do anything else with it.
Scott
2010-09-14 15:27:27 UTC
Permalink
Post by Scott
OBP 4.30.4.a, POST 4.30.4.a, OBDIAG 4.30.4.a
When I telnet to the network mgmt port it says "ALOM 1.3".
My security dept. says it's responding to snmp on it's network
management port
(this isn't on a port the OS uses).
What I've been able to look up through sunsolve and Google says it
doesn't have snmp capability.  With Windows-based tool, snmpwalk, I
$ snmpwalk -v 2c -c public -m ALL <my IP address>
SNMPv2-MIB::sysDescr.0 = STRING: VxWorks SNMPv1/v2c Agent
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::zeroDotZero
DISMAN-EXPRESSION-MIB::sysUpTimeInstance = Timeticks: (26852104) 3
days, 2:35:2
.04
SNMPv2-MIB::sysContact.0 = STRING: Wind River Systems
SNMPv2-MIB::sysName.0 = STRING: rsc
SNMPv2-MIB::sysLocation.0 = STRING: Planet Earth
SNMPv2-MIB::sysServices.0 = INTEGER: 79
Error in packet.
Reason: resourceUnavailable (This is likely a out-of-memory failure
within the
gent)
$ snmpwalk -v 1 -c public -m ALL <my IP address>
SNMPv2-MIB::sysDescr.0 = STRING: VxWorks SNMPv1/v2c Agent
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::zeroDotZero
DISMAN-EXPRESSION-MIB::sysUpTimeInstance = Timeticks: (26856492) 3
days, 2:36:0
.92
SNMPv2-MIB::sysContact.0 = STRING: Wind River Systems
SNMPv2-MIB::sysName.0 = STRING: rsc
SNMPv2-MIB::sysLocation.0 = STRING: Planet Earth
SNMPv2-MIB::sysServices.0 = INTEGER: 79
Error in packet.
Reason: (genError) A general failure occured
sc> showsc
and get back a "if_snmp" variable;  If I try to set the variable to
false I get an error.
It's frustrating.  Security thinks it's a problem.  As far as I can
tell I can't disable it or do anything else with it.
To answer my own question, I had ALOM 1.3 on this Sun Fire V240.
I had thought that applying OBP/POST upgrades upgraded the ALOM at the
same time.
It does not. An ALOM upgrade is a different patch, applied by scadm
when the OS is
running.
I upgraded to the current version, ALOM 1.6.10, and the snmp public
community no
longer responds.

Regards, Scott

Loading...