<?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: Cisco MIB issues in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/cisco-mib-issues/m-p/3212605#M1566</link>
    <description>Hi Joe,&lt;BR /&gt;&lt;BR /&gt;It is possible to import Cisco MIBs into SIM, but I can tell you from my experience with IM7 that it is not easy.  For starters, I had to rename all the .my files to .mib and take out all the dashes from the MIB names.  There were numerous changes that had to be made inside the MIBs, as well.  Basically, I gave up, and from what I've seen on the forums, other people have had problems too.  &lt;BR /&gt;&lt;BR /&gt;I'm using another monitoring tool for my Cisco devices.  If you need to use SIM, do you need more than standard traps (link up/down, cold/warm start, etc.)?  You don't need to compile MIBs for those.&lt;BR /&gt;&lt;BR /&gt;Good luck,&lt;BR /&gt;- Steve&lt;BR /&gt;</description>
    <pubDate>Tue, 09 Mar 2004 08:40:02 GMT</pubDate>
    <dc:creator>Steve Kadish</dc:creator>
    <dc:date>2004-03-09T08:40:02Z</dc:date>
    <item>
      <title>Cisco MIB issues</title>
      <link>https://community.hpe.com/t5/server-management-systems/cisco-mib-issues/m-p/3212604#M1565</link>
      <description>Anyone know of a good set of Cisco MIB files that can be used in SIM?  I've tried importing the ones from Cisco's site, but they seem to be full of errors.</description>
      <pubDate>Mon, 08 Mar 2004 15:19:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/cisco-mib-issues/m-p/3212604#M1565</guid>
      <dc:creator>Joe Hegyi</dc:creator>
      <dc:date>2004-03-08T15:19:14Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco MIB issues</title>
      <link>https://community.hpe.com/t5/server-management-systems/cisco-mib-issues/m-p/3212605#M1566</link>
      <description>Hi Joe,&lt;BR /&gt;&lt;BR /&gt;It is possible to import Cisco MIBs into SIM, but I can tell you from my experience with IM7 that it is not easy.  For starters, I had to rename all the .my files to .mib and take out all the dashes from the MIB names.  There were numerous changes that had to be made inside the MIBs, as well.  Basically, I gave up, and from what I've seen on the forums, other people have had problems too.  &lt;BR /&gt;&lt;BR /&gt;I'm using another monitoring tool for my Cisco devices.  If you need to use SIM, do you need more than standard traps (link up/down, cold/warm start, etc.)?  You don't need to compile MIBs for those.&lt;BR /&gt;&lt;BR /&gt;Good luck,&lt;BR /&gt;- Steve&lt;BR /&gt;</description>
      <pubDate>Tue, 09 Mar 2004 08:40:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/cisco-mib-issues/m-p/3212605#M1566</guid>
      <dc:creator>Steve Kadish</dc:creator>
      <dc:date>2004-03-09T08:40:02Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco MIB issues</title>
      <link>https://community.hpe.com/t5/server-management-systems/cisco-mib-issues/m-p/3212606#M1567</link>
      <description>Hello,&lt;BR /&gt;&lt;BR /&gt;i'just done it.&lt;BR /&gt;&lt;BR /&gt;Most of the problem in cisco mib (V2) it that :&lt;BR /&gt;&lt;BR /&gt;- mcompile modify "counter64" entry in "(null)"&lt;BR /&gt;- don't understand "BITS" entry&lt;BR /&gt;- have problem with parent definition&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Mib V1 are bettter. but your equipment must be configured to transmit trap in V1 mode.&lt;BR /&gt;&lt;BR /&gt;One of the main  problem come from the parent definition &lt;BR /&gt;When The message "no parent ..." appear when try to execute mxmib ...  you must add "cisco OBJECT IDE... {entreprises 9 }"in your .cfg file before execute mxmib.&lt;BR /&gt;&lt;BR /&gt;Another problem is to rename mib file .my to mib and -V1SMI.my to .mib. Some "import" must be modify in the cisco file to point to the correct file.&lt;BR /&gt;&lt;BR /&gt;It's not easy by it works....</description>
      <pubDate>Wed, 10 Mar 2004 04:07:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/cisco-mib-issues/m-p/3212606#M1567</guid>
      <dc:creator>zep</dc:creator>
      <dc:date>2004-03-10T04:07:22Z</dc:date>
    </item>
  </channel>
</rss>

