Hi, On 2/1/14, [email protected] <[email protected]> wrote: > Hi Lee, > > I didnt express my thoughts very well on that. > > Basically, the short version is the problem stays with the machine (\\new) > housing the support files minus the executable.
OK Which means the 'files are different/output is different' theory is still a possibility > When I remotely execute the snmptable.exe that resides on the machine > that gives bad results - from the machine that gives good results - the > results are good > and vise-versa > > In other words, the problem appears to lie in the support files or some > other machine configuration, not the .exe itself. > > I will try the idea of delete all of the files from the 'malfunctioning' > machine, and copying them from the 'functioning machine and see what that > gives and let you know the results. > > I was hoping for less of a shotgun approach, but I've already done a lot > of file compares, etc and haven't found anything. Yeah, I'm not thrilled with the nuke everything & restore from a known good approach either, but 1. it's likely to work and 2. it's easy to describe. If copying all the files over from the old machine doesn't fix it, I guess we're left with environment variables & registry entries. Envars are easy to see - just type in "set" in a command window. I don't know where the registry entries are kept -- maybe HKLM/software/Net-SNMP or HKCU/software/Net-SNMP?? You could get a copy of process monitor from http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx set a filter for process name is snmpwalk.exe and see exactly which files/registry entries are used Lee > > Thanks > > keith > > > > From: > Lee <[email protected]> > To: > [email protected] > Cc: > [email protected] > Date: > 01/31/2014 05:50 PM > Subject: > Re: diff in output format between 2 machines > > > > Hi, > > On 1/31/14, [email protected] > <[email protected]> wrote: >> Hi Lee, >> >> Thanks for the response. >> >> I attempted to track back the defs as you suggested.. >> >> I will describe the process in case my method was flawed: >> >> I located where the mac definitions were taking place on the 'working' >> machine by searching the Net-SNMP directory (D:\Program >> Files\OPENXTRA\NET-SNMP) file contents for "MacAddress ::=" >> >> That led me to SNMPv2-TC.txt in D:\Program >> Files\OPENXTRA\NET-SNMP\usr\share\snmp\mibs. >> Examining that file, I found the same display hint that you showed > below. >> >> I then repeated the above process on the machine that was displaying >> incorrectly ( format "F0 1F AF nn nn nn " 183 learned >> ) >> >> It came down the the same file " SNMPv2-TC.txt" in "C:\program files >> (x86)\openxtra\net-snmp\usr\share\snmp\mibs" >> and it had the same display hint notation. >> >> The interesting thing is that from the old machine (correct display) I > can >> launch the new machines exec with the command below >> >> \\PCNm\c$\PROGRA~2\OPENXTRA\NET-SNMP\usr\bin\snmptable -m BRIDGE-MIB -v > 1 >> -c <community> <IP> 1.3.6.1.2.1.17.4.3 >> >> and the format is incorrect. Likewise when I launch the exec on the old >> machine, from the new one, the format is incorrect. > > That's not making any sense.. > old machine> \\new-machine\snmptable -m ... > gives the "bad" format output, same as > > new-machine> snmptable -m ... > and > new machine> \\old-machine\snmptable -m ... > > Is that right? > >> Any other ideas, or ideas on how I can track this down? > > A bit drastic, but you could always delete the NET-SNMP directory on > the new machine & then copy it over from the old machine. Less > intrusive would be to compare the directories from the two machines > and copy old -> new to remove any differences. I like WinMerge > (http://winmerge.org/) for that, but I'm sure there's lots of > different programs for that. > > I thought there was an snmp program option for showing which mib files > were loaded in what order, but I'm not finding it now :( Some > combination of snmptable -Pe -PR -Pw might give you a hint as to > what's different between the two machines. > > Do you have a .bat file that you run to initialize the environment or > is everything coming from the env. variables and/or registry? > > Comparing the output from "set" on the two machines might show what's > different. > >> I am using the >> output from this command in a program, and the program is crashing > because >> the output is different. And, while I could modify the program to accept >> either format, Id rather know how to make the 2 PCs format the output > data >> the same. > > I understand. I'd be doing the same thing in your place :) > > Lee > > > >> >> thanks again for your help >> >> keith >> >> >> >> >> From: >> Lee <[email protected]> >> To: >> [email protected] >> Cc: >> [email protected] >> Date: >> 01/31/2014 02:49 PM >> Subject: >> Re: diff in output format between 2 machines >> >> >> >>> ... copied over essentially all of the core files >> >> I'm guessing one or more files on the new machine don't match up with >> the files on the old machine & you're missing a display hint on the >> new machine. >> >> I have non-standard mib files & locations, so I can't point you to a >> set of files to check. >> What you'll need to do is find the file where dot1dTpFdbAddress is >> defined; for me it's in BRIDGE-MIB.my: >> dot1dTpFdbAddress OBJECT-TYPE >> SYNTAX MacAddress >> MAX-ACCESS read-only >> STATUS current >> >> no display hint, so find where MacAddress is defined; probably near >> the top of the file: >> IMPORTS MacAddress FROM SNMPv2-TC >> >> figure out where SNMPv2-TC comes from, look in there for the >> definition of MacAddress >> >> MacAddress ::= TEXTUAL-CONVENTION >> DISPLAY-HINT "1x:" >> STATUS current >> DESCRIPTION >> "Represents an 802 MAC address represented in the >> `canonical' order defined by IEEE 802.1a, i.e., as if it >> were transmitted least significant bit first, even though >> 802.5 (in contrast to other 802.x protocols) requires MAC >> addresses to be transmitted most significant bit first." >> SYNTAX OCTET STRING (SIZE (6)) >> >> add the display hint if it's missing. >> >> Regards, >> Lee >> >> >> >> On 1/30/14, [email protected] >> <[email protected]> wrote: >>> Hello All, >>> >>> I am having a strange problem between 2 machines. >>> >>> I installed Net-SNMP on a new windows7 - 64b machine - the first time > in >> a >>> while - and copied over essentially all of the core files from the >>> existing machine (also win7-64b) to insure they were configured the >> same. >>> >>> I have verified the version on both is 5.2.1.2 >>> >>> However when I run the command below on both machines, I get different >>> output formats - plus the new machine shows a lot of garbage entries >>> >>> snmptable -m BRIDGE-MIB -v 1 -c <community> <IP> 1.3.6.1.2.1.17.4.3 >>> >>> (sample output from original machine) I want it to look like this: >>> f0:4d:a2:nn:nn:nn 24 learned >>> f0:4d:a2:nn:nn:nn 241 learned >>> f0:4d:a2:nn:nn:nn 241 learned >>> f0:4d:a2:nn:nn:nn 134 learned >>> f0:4d:a2:nn:nn:nn 241 learned >>> f0:4d:a2:nn:nn:nn 82 learned >>> f0:4d:a2:nn:nn:nn 239 learned >>> >>> (sample output from new machine) >>> "F0 1F AF nn nn nn " 183 learned >>> "F0 1F AF nn nn nn " 174 learned >>> "F0 1F AF nn nn nn " 183 learned >>> "F0 1F AF nn nn nn " 174 learned >>> "F0 1F AF nn nn nn " 24 learned >>> "dM¢+Å"" 24 learned >>> "dM¢Ü¶z" 241 learned >>> "dM¢Ü·-" 241 learned >>> >>> As you can see, the second sample has quotes around it - with upper and >>> lower case; no colons separating the groups. >>> >>> I have a very vague memory of some configuration command you enter 1 >> time >>> to fix this but I cant find anything on it in the official FAQ or >> general >>> google searches. >>> >>> Has anyone run across this before? >>> >>> Thx >> >> >> >> >> NOTICE: This email transmission and any attachments that accompany it > may >> contain information that is confidential or otherwise exempt from >> disclosure under applicable law and is intended solely for the use of > the >> individual(s) to whom it was intended to be addressed. If you have >> received this email by mistake, or you are not the intended recipient, > any >> disclosure, dissemination, distribution, copying or other use or > retention >> of this communication or its substance is prohibited. If you have > received >> this communication in error, please immediately report to the author via >> email that you received this message by mistake and also permanently >> destroy printed copies and delete the original and all copies of this >> email and any attachments from your computer. >> > > > > > NOTICE: This email transmission and any attachments that accompany it may > contain information that is confidential or otherwise exempt from > disclosure under applicable law and is intended solely for the use of the > individual(s) to whom it was intended to be addressed. If you have > received this email by mistake, or you are not the intended recipient, any > disclosure, dissemination, distribution, copying or other use or retention > of this communication or its substance is prohibited. If you have received > this communication in error, please immediately report to the author via > email that you received this message by mistake and also permanently > destroy printed copies and delete the original and all copies of this > email and any attachments from your computer. > ------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk _______________________________________________ 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
