[j-nsp] SNMP issue...

2009-02-20 Thread Derick Winkworth 
#
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]
juni...@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.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] SNMP issue...

2009-02-20 Thread Nilesh Khambal 
Are you querying like communityn...@instance-name. In your case it 
will be testcommun...@rdi. If not can you try that.


Thanks,
Nilesh.


Derick Winkworth wrote:

#
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]
juni...@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.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] SNMP issue...

2009-02-20 Thread Masood Ahmad Shah 
This is what it should be like r...@testcommunity

HTH

Regards,
Masood

-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Nilesh Khambal
Sent: Saturday, February 21, 2009 12:53 AM
To: Derick Winkworth
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] SNMP issue...

Are you querying like communityn...@instance-name. In your case it 
will be testcommun...@rdi. If not can you try that.

Thanks,
Nilesh.


Derick Winkworth wrote:
 #
 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]
 juni...@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.
 ___
 juniper-nsp mailing list juniper-nsp@puck.nether.net
 https://puck.nether.net/mailman/listinfo/juniper-nsp
 
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] SNMP issue...

2009-02-20 Thread Nilesh Khambal 

Thats correct. Sorry. My bad. It should be instance-n...@community-name.

I am sure he must have figured it out by now after checking the logs :).

BTW, if you think this is not documented well enough, please open a JTAC 
 case. They will open a doc bug to fix this.


Thanks,
Nilesh.


Masood Ahmad Shah wrote:

This is what it should be like r...@testcommunity

HTH

Regards,
Masood

-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Nilesh Khambal
Sent: Saturday, February 21, 2009 12:53 AM
To: Derick Winkworth
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] SNMP issue...

Are you querying like communityn...@instance-name. In your case it 
will be testcommun...@rdi. If not can you try that.


Thanks,
Nilesh.


Derick Winkworth wrote:

#
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]
juni...@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.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp



___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp