[j-nsp] SNMPD_AUTH_FAILURE

[Eric Van Tol]

> Are you using snmp v3 ?

I'm not using v3 yet on this router, but I will keep this in mind, as it's some good info. 

-evt

> -----Original Message-----
> From: Samuel [mailto:samuel.gay at c-s.fr] 
> Sent: Tuesday, November 13, 2007 9:44 AM
> To: Eric Van Tol; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] SNMPD_AUTH_FAILURE
> 
> Hi Eric,
> 
> I have already got this kind of problem.
> Are you using snmp v3 ?
> 
> My problem was next :
> 
> When we change a RE, you have to generate again the MD5 password :
> 
> # set snmp v3 usm local-engine user TOTO authentication-md5 
> authentication-password PASSWORD
> # commit
> 
> For exemple is you have this configuration :
> snmp {
>     engine-id {
>         use-mac-address;
>     }
> }
> In this case the MD5 hash is genereted with the MAC address of the 
> management interface (fxp0).
> http://www.juniper.net/techpubs/software/junos/junos80/swconfi
> g80-net-mgmt/html/snmp-v3-summary9.html 
> 
> 
> Regards,
> Samuel
> 
> 
> Eric Van Tol a écrit :
> > Hello,
> > We replaced an old M5 with an M10i last week and ever since 
> then, we get
> > the following in syslog every day:
> >
> > Nov 13 07:38:21 snmpd[3317]: SNMPD_AUTH_FAILURE: 
> agent_io_reader: failed
> > input interface authorization from 172.26.26.5 to unknown (3)
> >
> > The IP is our NMS.  There are only two ways to get into 
> this router from
> > the NMS perspective; the ae0 and ae1 interfaces, both of which are
> > configured in the snmp config:
> >
> > snmp {
> >     interface [ ae0.0 ae1.0 lo0.0];
> > }
> >
> > The strangest thing about this is that it occurs at 7:38AM 
> every day.
> > Not 7:12AM or 9:35PM, but 7:38AM.  Anyone seen this before?  I'm not
> > seeing this message on any other routers.  JUNOS is 8.4R1.13.
> >
> > -evt
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
> >
> >   
> 
>