[jboss-jira] [JBoss JIRA] Commented: (JBAS-4451) SNMP Adaptor of JBOSS does not handle the read community properly, it responds with "public" community instead of custom one.

[Alexander Else (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBAS-4451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12511472#action_12511472 ] 

Alexander Else commented on JBAS-4451:
--------------------------------------

Is this issue getting any love? I'm seeing the same problem on JBoss 4.3. I encountered the problem, also did a packet dump, and later ended up at this ticket.

> SNMP Adaptor of JBOSS does not handle the read community properly, it responds with "public" community instead of custom one.
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBAS-4451
>                 URL: https://jira.jboss.org/jira/browse/JBAS-4451
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: SNMP adapter
>    Affects Versions: JBossAS-4.0.5.GA
>         Environment: Tested on REDHAT enterprise, JDK 1.5.0
>            Reporter: Pascal Heraud
>            Assignee: Dimitris Andreadis
>
> I'm using JBOSS SnmpAdaptor to monitor jboss and my web application.
> Ive modified the read community of the snmp adaptor into the META-INF/jboss-service.xml configuration file :
> <attribute name="ReadCommunity">myCommunity</attribute>
> The software we're using for monitoring is using the PERL implementation NET-SNMP and is issuing errors because JBOSS does not reply using the good ReadCommunity (it responds using "public").
> We tried with snmpwalk and you can find the logs.
> Pascal.
> Here is the details of the snmpwalk to the server, the -d options outputs the buffzer
> =======================================================
> >snmpwalk -d -v1 -c myCommunity localhost:1161 1.2.3.4.1.2
> Sending 43 bytes to UDP: [127.0.0.1]:1161
> 0000: 30 29 02 01  00 04 0B 6D  79 43 6F 6D  6D 75 6E 69    0).....myCommuni
> 0016: 74 79 A1 17  02 02 38 B6  02 01 00 02  01 00 30 0B    tyí...8Â......0.
> 0032: 30 09 06 05  2A 03 04 01  02 05 00                    0   ..*......
> Received 42 bytes from UDP: [127.0.0.1]:1161
> 0000: 30 28 02 01  00 04 06 70  75 62 6C 69  63 A2 1B 02    0(.....publicó..
> 0016: 02 38 B6 02  01 00 02 01  00 30 0F 30  0D 06 05 2A    .8Â......0.0...*
> 0032: 03 04 01 03  42 04 1F A5  00 00                       ....B..Ñ..
> Sending 43 bytes to UDP: [127.0.0.1]:1161
> 0000: 30 29 02 01  00 04 0B 6D  79 43 6F 6D  6D 75 6E 69    0).....myCommuni
> 0016: 74 79 A0 17  02 02 38 B7  02 01 00 02  01 00 30 0B    tyá...8À......0.
> 0032: 30 09 06 05  2A 03 04 01  02 05 00                    0   ..*......
> Received 42 bytes from UDP: [127.0.0.1]:1161
> 0000: 30 28 02 01  00 04 06 70  75 62 6C 69  63 A2 1B 02    0(.....publicó..
> 0016: 02 38 B7 02  01 00 02 01  00 30 0F 30  0D 06 05 2A    .8À......0.0...*
> 0032: 03 04 01 02  42 04 05 55  4A D8                       ....B..UJÏ
> iso.2.3.4.1.2 = Gauge32: 89475800

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira