<?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: Mismatch in OIDs of MIBs for DL380 Gen10 in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/mismatch-in-oids-of-mibs-for-dl380-gen10/m-p/7081117#M169896</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;What is the application and have you tried an older version of MIB?&lt;/P&gt;&lt;P&gt;We have tested in the labs with an base snmp receipent and getting the proper OIDs for the tests carried out for the PSU redundancy.&lt;/P&gt;&lt;P&gt;Make sure that there are no changes happening to the MIB files when integrated to your application.&lt;/P&gt;</description>
    <pubDate>Mon, 02 Mar 2020 15:02:03 GMT</pubDate>
    <dc:creator>KK</dc:creator>
    <dc:date>2020-03-02T15:02:03Z</dc:date>
    <item>
      <title>Mismatch in OIDs of MIBs for DL380 Gen10</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/mismatch-in-oids-of-mibs-for-dl380-gen10/m-p/7080304#M169772</link>
      <description>&lt;P&gt;hello,&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just have downloaded the last updated MIBs in HPE SIM MIB KIT and shared with customer for testing alarms. OID in shared MIBs are registered as&amp;nbsp;&lt;STRONG&gt;1.3.6.1.4.1.232&lt;/STRONG&gt;.XXXX, although customer is receiving a different OID as&amp;nbsp;&lt;STRONG&gt;1.3.6.1.4.1.232&lt;/STRONG&gt;.&lt;FONT size="5"&gt;&lt;U&gt;&lt;STRONG&gt;0&lt;/STRONG&gt;&lt;/U&gt;&lt;/FONT&gt;.XXXX,&amp;nbsp;&lt;/P&gt;&lt;P&gt;MIBs shared: cpqhlth&lt;/P&gt;&lt;P&gt;The server is a DL380 GEN 10 and the SNMP credentials are configured in iLO 5.&lt;/P&gt;&lt;P&gt;Where should i get the correct MIBs so i can share them and the Manager can identificate them correctly?, at this moment these are unrecognized alarms.&lt;/P&gt;&lt;P&gt;Thanks a lot,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2020 16:59:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/mismatch-in-oids-of-mibs-for-dl380-gen10/m-p/7080304#M169772</guid>
      <dc:creator>manu7cabre87</dc:creator>
      <dc:date>2020-02-24T16:59:15Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch in OIDs of MIBs for DL380 Gen10</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/mismatch-in-oids-of-mibs-for-dl380-gen10/m-p/7080505#M169809</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Could you let us know how the alarms are being tested.&lt;/P&gt;&lt;P&gt;Are the alarms are received from iLO5 with a wrong OID?&lt;/P&gt;&lt;P&gt;Hope the alarms are not being checked with the OS on the server as there are no SNMP or WBEM based management agents provided for Gen10 servers.&lt;/P&gt;&lt;P&gt;A screenshot or output of the alarm showing wrong OID will be helpful to provide further updates.&lt;/P&gt;&lt;P&gt;A supported list of SNMP traps and MIBs is provided in the document&amp;nbsp;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&amp;amp;docId=emr_na-a00026111en_us" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&amp;amp;docId=emr_na-a00026111en_us&lt;/A&gt;.&lt;/P&gt;&lt;P&gt;Also the previous version of MIB kit can be checked and it is available at&amp;nbsp;&lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04272529" target="_blank"&gt;https://support.hpe.com/hpesc/public/docDisplay?docId=emr_na-c04272529&lt;/A&gt;.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Feb 2020 08:21:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/mismatch-in-oids-of-mibs-for-dl380-gen10/m-p/7080505#M169809</guid>
      <dc:creator>KK</dc:creator>
      <dc:date>2020-02-26T08:21:11Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch in OIDs of MIBs for DL380 Gen10</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/mismatch-in-oids-of-mibs-for-dl380-gen10/m-p/7080743#M169839</link>
      <description>&lt;P&gt;hello,&lt;/P&gt;&lt;P&gt;The testing consists of removing 1 power supply of the server, this is part of the acceptance of the server.&lt;/P&gt;&lt;P&gt;As the documentation establishes, the server will send .1.3.6.1.4.1.232.6069 (cpqHe4FltTolPowerSupplyACpowerloss), but instead the customer is receiving .1.3.6.1.5.232.&lt;STRONG&gt;0&lt;/STRONG&gt;.6069. Due to this, the customer is not recognizing the OID because the MIBs shared are not correct.&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Wrong OID.png" style="width: 1554px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/114220i3262965138A059CC/image-size/large?v=v2&amp;amp;px=2000" role="button" title="Wrong OID.png" alt="Wrong OID.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;According to cpqhlth MIB, the prefix is:&lt;/P&gt;&lt;P&gt;"The Compaq Enterprise number is 232.&lt;BR /&gt;-- The ASN.1 prefix to, and including the Compaq Enterprise is:&lt;BR /&gt;-- 1.3.6.1.4.1.232"&lt;/P&gt;&lt;P&gt;Is there a MIB file included with the additional cero (0) of the OID so the customer can recognized the alarm?&lt;/P&gt;</description>
      <pubDate>Thu, 27 Feb 2020 17:47:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/mismatch-in-oids-of-mibs-for-dl380-gen10/m-p/7080743#M169839</guid>
      <dc:creator>manu7cabre87</dc:creator>
      <dc:date>2020-02-27T17:47:57Z</dc:date>
    </item>
    <item>
      <title>Re: Mismatch in OIDs of MIBs for DL380 Gen10</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/mismatch-in-oids-of-mibs-for-dl380-gen10/m-p/7081117#M169896</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;What is the application and have you tried an older version of MIB?&lt;/P&gt;&lt;P&gt;We have tested in the labs with an base snmp receipent and getting the proper OIDs for the tests carried out for the PSU redundancy.&lt;/P&gt;&lt;P&gt;Make sure that there are no changes happening to the MIB files when integrated to your application.&lt;/P&gt;</description>
      <pubDate>Mon, 02 Mar 2020 15:02:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/mismatch-in-oids-of-mibs-for-dl380-gen10/m-p/7081117#M169896</guid>
      <dc:creator>KK</dc:creator>
      <dc:date>2020-03-02T15:02:03Z</dc:date>
    </item>
  </channel>
</rss>

