<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Registering Mibs in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037097#M48669</link>
    <description>If a MIB is not registered then doing the mxmib and mcompile to get it loaded shouldn't cause any problems.&lt;BR /&gt;&lt;BR /&gt;I guess the worst case is if you compiled an older MIB over a new one.&lt;BR /&gt;But, as all of the MIB's are in the one directory this shouldn't be an issue.&lt;BR /&gt;&lt;BR /&gt;As a quick check you can use mxmib -l which will list the MIB's compiled. I did that on my server and didn't see any bladetype-4 MIBs, just bladetype-2.&lt;BR /&gt;There were a number of cisco and old-cisco MIBs compiled in.&lt;BR /&gt;</description>
    <pubDate>Thu, 29 Mar 2007 16:11:32 GMT</pubDate>
    <dc:creator>Rob Buxton</dc:creator>
    <dc:date>2007-03-29T16:11:32Z</dc:date>
    <item>
      <title>Registering Mibs</title>
      <link>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037094#M48666</link>
      <description>I was not receiving some alerts and when I checked, I found that 66 of the compiled Mibs have been registered!  I followed the instructions when I downloaded the latest version and ran the following command:&lt;BR /&gt;cscript updatemibs.js&lt;BR /&gt;&lt;BR /&gt;After this, do I still have to run an mxcompile each time to make sure they are all registered?</description>
      <pubDate>Wed, 28 Mar 2007 12:23:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037094#M48666</guid>
      <dc:creator>Rancher</dc:creator>
      <dc:date>2007-03-28T12:23:43Z</dc:date>
    </item>
    <item>
      <title>Re: Registering Mibs</title>
      <link>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037095#M48667</link>
      <description>My understanding is that you just need to run the vb script.&lt;BR /&gt;I'm sure that's what the instructions say - and I always read the instructions first!&lt;BR /&gt;&lt;BR /&gt;I've only had to use the mxcompile for non-HP MIBs.&lt;BR /&gt;&lt;BR /&gt;Which MIBs were missing?</description>
      <pubDate>Wed, 28 Mar 2007 15:30:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037095#M48667</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2007-03-28T15:30:51Z</dc:date>
    </item>
    <item>
      <title>Re: Registering Mibs</title>
      <link>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037096#M48668</link>
      <description>I am also an instruction-reader!&lt;BR /&gt;&lt;BR /&gt;It looks like you are right about the non-HP mibs.  The specific one I wanted was the powernet.mib.  However, some of them are HP (bladetype4-etc. mibs) and not all of the Cisco ones registered.  It is really kind of hit and miss!  Some are old and some of the unregistered Mibs are the latest version.&lt;BR /&gt;&lt;BR /&gt;If I run mxcompile would it hurt anything?&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Mar 2007 09:24:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037096#M48668</guid>
      <dc:creator>Rancher</dc:creator>
      <dc:date>2007-03-29T09:24:24Z</dc:date>
    </item>
    <item>
      <title>Re: Registering Mibs</title>
      <link>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037097#M48669</link>
      <description>If a MIB is not registered then doing the mxmib and mcompile to get it loaded shouldn't cause any problems.&lt;BR /&gt;&lt;BR /&gt;I guess the worst case is if you compiled an older MIB over a new one.&lt;BR /&gt;But, as all of the MIB's are in the one directory this shouldn't be an issue.&lt;BR /&gt;&lt;BR /&gt;As a quick check you can use mxmib -l which will list the MIB's compiled. I did that on my server and didn't see any bladetype-4 MIBs, just bladetype-2.&lt;BR /&gt;There were a number of cisco and old-cisco MIBs compiled in.&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Mar 2007 16:11:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037097#M48669</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2007-03-29T16:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: Registering Mibs</title>
      <link>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037098#M48670</link>
      <description>Great, I will just do that.&lt;BR /&gt;My only concern was overwriting new ones, but since they are in the same directory, it should be OK.</description>
      <pubDate>Mon, 02 Apr 2007 14:39:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037098#M48670</guid>
      <dc:creator>Rancher</dc:creator>
      <dc:date>2007-04-02T14:39:03Z</dc:date>
    </item>
    <item>
      <title>Re: Registering Mibs</title>
      <link>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037099#M48671</link>
      <description>I will just recompile and register as Rob suggests.</description>
      <pubDate>Mon, 02 Apr 2007 14:41:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/registering-mibs/m-p/5037099#M48671</guid>
      <dc:creator>Rancher</dc:creator>
      <dc:date>2007-04-02T14:41:47Z</dc:date>
    </item>
  </channel>
</rss>

