RE: snmpget and snmpwalk return corrupt string instead of hex string when MAC address starts with non zero
Randall C Grimshaw <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <D1ED659D5D76664389FB55EE3E3EE506095CE8EF80@suex07-mbx-01.ad.syr.edu> |
When I add > PhysAddress > FROM SNMPv2-TC To the IMPORTS list in the RFC1213-MIB.txt file - it works.... (albeit it changes the PHP formatting to require the use of the snmp_set_quick_print(TRUE); and snmp_set_valueretrieval(0); functions) Is this safe to adopt in production? Randy From: Fulko Hew [mailto:[email protected]] Sent: Wednesday, July 14, 2010 4:02 PM To: Randall C Grimshaw Cc: [email protected] Subject: Re: snmpget and snmpwalk return corrupt string instead of hex string when MAC address starts with non zero On Wed, Jul 14, 2010 at 3:33 PM, Randall C Grimshaw <[email protected]<mailto:[email protected]>> wrote: Dave (cc: Fulko, etc) When I tried to remove the RFC1213-MIB the apps fail. ip.ipNetToMediaTable.ipNetToMediaEntry.ipNetToMediaPhysAddress.443: Unknown Object Identifier (Sub-id not found: (top) -> ip) The only DISPLAY-HINT I can find in IP-MIB to use as an example is for Ipv6AddressIfIdentifierTC I made the same 'junior' mistake when I look at the file a few hours ago :-) In IP-MIB: ipNetToMediaPhysAddress is defined as a PhysAddress which is IMPORTed from SNMPv2-TC (see the top of the IP-MIB file) where the def'n of PhysAddress does indeed have a DISPLAY-HINT I tried to add a hint to the RFC1213-MIB under ipNetToMediaPhysAddress and it also reminds me that I do not know what I am doing. Bad format of optional clauses (DISPLAY-HINT): At line 1314 in /usr/local/net-snmp/5.5/share/snmp/mibs/RFC1213-MIB.txt Bad parse of OBJECT-TYPE: At line 1314 in /usr/local/net-snmp/5.5/share/snmp/mibs/RFC1213-MIB.txt ip.ipNetToMediaTable.ipNetToMediaEntry.ipNetToMediaPhysAddress.443: Unknown Object Identifier (Sub-id not found: (top) -> ip) Now... you are probably stumbling over the problem of DISPLAY-HINT is probably not allowed in an SMI v1 formatted file such as RFC1213. Which is why you can't (and shouldn't) try to change _that_ file. But Dave's original comment remains correct... Somehow you are picking up the definition of PhysAddr from RFC1213 instead and should be picking it up from IP-MIB. The question is 'why' isn't it? When you removed the RFC1213, it complained that it couldn't find the 'sub-identifier' called 'ip'. Its as if It cannot find/read the IP-MIB file where 'ip' is defined. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ 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