Re: wrong MAC int the trap

Lee <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <CAD8GWsvdcn--8jxMDNAz4Xirv5qv9hJASuPRz+rhXHyrScNLRw@mail.gmail.com>
Adding a display-hint to the mib file might work.  But with snmptrapd
printing out
> 22#011.1.3.6.1.4.1.45.1.6.5.3.12.1.3.1.22 = "`s\\/c("
it doesn't look like it's found the mibs.

> I also installed the needed MIBs in /usr/share/snmp/mibs

The default  location for the mib files is /usr/local/share/snmp/mibs
In any case, once you've got snmptrapd reading the mibs try adding
  DISPLAY-HINT "2x:"
to the definition of the variable.  For example:
        Ipv6Address ::= TEXTUAL-CONVENTION
             DISPLAY-HINT "2x:"
             STATUS       current
             DESCRIPTION
               "This data type is used to model IPv6 addresses.
                This is a binary string of 16 octets in network
                byte-order."
             SYNTAX       OCTET STRING (SIZE (16))

Regards,
Lee


On 2/28/13, Meike Stone <[email protected]> wrote:
> Hello dear list,
>
> I'm using snmptrapd and get  link up/down from a Nortel Networks switch:
> The snmptrapd logs the traps in the logfile. But sometime, the value
> from the MAC-Address is misinterpreted (as string, eg. "`s\\/c(")
> In the network capture from tcpdump, the bytecode from a working trap
> and a not working trap looks like the same, except the bytes from the
> MAC itself.
>
> Working trap:
> 10.32.12.240(via UDP: [10.32.12.240]:4682->[10.216.17.90]) TRAP, SNMP
> v1, community public#012#011.1.3.6.1.4.1.45.1.6.2.1 Enterprise
> Specific Trap (5) Uptime:
> 48:17:31:03.16#012#011.1.3.6.1.4.1.45.1.6.5.3.12.1.1.1.2  =
> 1#011.1.3.6.1.4.1.45.1.6.5.3.12.1.2.1.2  =
> 2#011.1.3.6.1.4.1.45.1.6.5.3.12.1.3.1.2 = "50 26 90 9E 66 44 "
>
>
> Not working trap with wrong interpreted MAC:
> 10.22.2.240 (via UDP: [10.22.2.240]:2925->[10.216.17.90])  TRAP, SNMP
> v1, community public#012#011.1.3.6.1.4.1.45.1.6.2.1 Enterprise
> Specific Trap (5) Uptime:
> 33:21:06:58.47#012#011.1.3.6.1.4.1.45.1.6.5.3.12.1.1.1.22 =
> 1#011.1.3.6.1.4.1.45.1.6.5.3.12.1.2.1.22 =
> 22#011.1.3.6.1.4.1.45.1.6.5.3.12.1.3.1.22 = "`s\\/c("
>
>
> I straced the snmptrapd while recvmsg:
> recvmsg(8, {msg_name(16)={sa_family=AF_INET, sin_port=htons(3705),
> sin_addr=inet_addr("10.22.2.240")},
> msg_iov(1)=[{"0t\2\1\0\4\6public\244g\6\n+\6\1\4\1-\1\6\2\1@\4\n\26\2\360\2\1\6\2\1\5C\4\21\201\\V0G0\24\6\17+\6\1\4\1-\1\6\5\3\f\1\1\1\26\2\1\0010\24\6\17+\6\1\4\1-\1\6\5\3\f\1\2\1\26\2\1\0260\31\6\17+\6\1\4\1-\1\6\5\3\f\1\3\1\26\4\6`s\\/c(\5\21\1\5\4\0\4\6\0\37<\262\205w\1\1\3\1\2\1\1\1\3\201\23\2\1\23\0
>
>
> I also installed the needed MIBs in /usr/share/snmp/mibs
> - S5-ROOT-MIB.mib
> - SYNOPTICS-ROOT-MIB.mib
>  and started the snmptrapd with -m ALL. But nothing changed (I used
> strace -f -e open to exterminate, if the MIBs are loaded).
> With this MIBs, I can use
>
> snmptranslate -m ALL .1.3.6.1.4.1.45.1.6.2.1
> S5-ROOT-MIB::s5EthTrap
>
> What is going wrong, does anyone has a clue?
>
> Thanks, Meike
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Net-snmp-users mailing list
> [email protected]
> Please see the following page to unsubscribe or change other options:
> https://lists.sourceforge.net/lists/listinfo/net-snmp-users
>

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.