You should have an empty.db file of 19kb, and the installer should copy a file samib of 2972kb. Except if it finds an samib.db in the "old" location (c:\program files\salive) then it will copy that to the new location. So if that file was somehow corrupt (or nulled) then you can end-up with a 0kb file.
dirk From: Servers Alive Discussion List [mailto:[email protected]] On Behalf Of Kevin Stone Sent: Monday, August 15, 2011 6:31 PM To: Servers Alive Discussion List Subject: Re: [SA-list] MIB database for SNMP traps I just did a clean install and have the same issue. When I look at the saMIB.db it is a 0KB file. This was 6.3.2399 installed on Windows XP. Installed on a Windows 2003 server and it worked as expected, I can see 64 MIB files in the database. I copied that database file to my XP system and everything worked. Maybe it's something unexpected during installation. Is there an install log? -Kevin On Mon, Aug 15, 2011 at 3:30 AM, Dirk <[email protected] (mailto:[email protected])> wrote: When you goto setup-general-mib database, you should see the MIB files that are loaded. On my system for example it states 68 MIB files, containing 8886 OID. I download that ZIP file from HP, extracted it all into one directory and added it with *.* This gives a lot of load errors, mostly due to invalid valid files. No dependency errors at all. If I then exit the setup, and re-enter it, I have 276 loaded MIB files (42287 OIDs). If you want to download this saMIB file, you can get it from http://beta.woodstone.nu/temp/loaded-mibs.zip (http://beta.woodstone.nu/temp/loaded-mibs.zip) (zip file is about 4.5mb, extracted it's about 32mb) On a 6.3 beta install the samib file is located in C:\Documents and Settings\All Users\Application Data\Woodstone\Servers Alive\saMIB.db (on XP that is) From: Servers Alive Discussion List [mailto:[email protected] (mailto:[email protected])] On Behalf Of Kevin Stone Sent: Monday, August 15, 2011 2:01 AM To: Servers Alive Discussion List Subject: Re: [SA-list] MIB database for SNMP traps I just tested and have the same issue. It's true with other MIBs that depend on items that already exist in the MIB database. I tried adding rfc1213.mib and was it failed due to a dependency in rfc1155.mib which already exists in the database. Dirk, should we be able to see the existing MIBs in the database window? My installation says there is one mib with one OID but adding MIBs says that others exist -Kevin On Sun, Aug 14, 2011 at 11:00 AM, Viktor Sokol <[email protected] (mailto:[email protected])> wrote: Hello Servers, Trying to decrypt SMTP traps. I have a lots a HP hardware. Downloaded http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&swItem=MTX-722ee8c388c04a469c24ff60df&jumpid=reg_R1002_USEN (http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&swItem=MTX-722ee8c388c04a469c24ff60df&jumpid=reg_R1002_USEN) Trying to add into SA database (SETUP/General/MIB datasabe (SNMP) select for example vc-domain-mib.mib when you trying to add it its says Missing dependency 'SNMPv2-SMI' even if I have SNMPv2-SMI.mib in the same directory. When I tried to add SNMPv2-SMI.mib UI says 'SNMPv2-SMI.mib' already exist in the database. Still nothing showing in MIB datasabe (SNMP) tag. My questing: Does anyone using SNMP traps from HP hardware? How you decrypt SNMP traaps? -- Best regards, Viktor mailto:[email protected] (mailto:[email protected]) To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
