[j-nsp] SNMP issue...

Derick Winkworth dwinkworth at att.net
Fri Feb 20 13:10:06 EST 2009


#########
Feb 20 17:44:54 snmpd[4d88b0c2] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Feb 20 17:44:54 snmpd[4d88b0c2] >>> Get-Next-Request
Feb 20 17:44:54 snmpd[4d88b0c2] >>>  Source:      10.254.0.33
Feb 20 17:44:54 snmpd[4d88b0c2] >>>  Destination: 10.254.23.2
Feb 20 17:44:54 snmpd[4d88b0c2] >>>  Version:     SNMPv2
Feb 20 17:44:54 snmpd[4d88b0c2] >>>  Request_id:  0x4d88b0c2
Feb 20 17:44:54 snmpd[4d88b0c2] >>>  Community:   testcommunity
Feb 20 17:44:54 snmpd[4d88b0c2] >>>  Error:       status=0 / vb_index=0
Feb 20 17:44:54 snmpd[4d88b0c2] >>>   OID  : mib_2
Feb 20 17:44:54 snmpd[4d88b0c2] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Feb 20 17:44:54 SNMPD_AUTH_FAILURE: nsa_initial_embedcomm: unauthorized SNMP community from 10.254.0.33 to unknown community name (testcommunity)
###########



and here is the config...


############
[edit snmp]
juniper at BD-Bottom-M120# show

community testcommunity {
    authorization read-only;
    routing-instance RDI;
}
routing-instance-access;
traceoptions {
    file snmp;
    flag all;
}
################


The traffic is coming in on the RDI routing-instance, which is what we want...

Any ideas?  The community string is valid.


More information about the juniper-nsp mailing list