<?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: IMC SNMP issues in IMC</title>
    <link>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6925065#M3416</link>
    <description>&lt;P&gt;I have also went through nortel&amp;nbsp;documentation and if I understand it correctly snmp v1 is used for traps and v2 for something else -&amp;nbsp;weird&lt;/P&gt;&lt;P&gt;can you actually set IMC to work that way - listen for traps with snmp v1 and monitoring with v2 for the same device?&lt;/P&gt;&lt;P&gt;this is directly from the document&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;FONT face="Arial" size="3"&gt;&lt;STRONG&gt;Trap &lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT face="Arial" size="3"&gt;– a one-way notification sent from the SNMP agent on a device to&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;the Network Management System (NMS) when a specific condition occurs,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;such as the failure of a system component. In Nortel Communication&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Server 1000 products, the traps are sent in the form of a SNMP V1&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;TRAP-TYPE Protocol Data Unit (PDU). The PDU type is TRAP-V1, and&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;the trap type is Enterprise-Specific.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 13 Dec 2016 14:54:03 GMT</pubDate>
    <dc:creator>pattap</dc:creator>
    <dc:date>2016-12-13T14:54:03Z</dc:date>
    <item>
      <title>IMC SNMP issues</title>
      <link>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6924281#M3397</link>
      <description>&lt;P&gt;I've received a few complaints about SNMP not being able to communicate with Nortel CS1000E.&lt;/P&gt;&lt;P&gt;Now, the device is fully discovered and added in IMC, customer claims that it has gone down and it's been missed&lt;BR /&gt;by IMC. They started digging into it and noticed that they are not able to test SNMP for devices in question, see the below&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="IMCSNNMP.JPG" style="width: 1356px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/88801iD44E5690A687DF72/image-dimensions/1356x755?v=v2" width="1356" height="755" role="button" title="IMCSNNMP.JPG" alt="IMCSNNMP.JPG" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="IMCSNNMP1.JPG" style="width: 256px;"&gt;&lt;img src="https://community.hpe.com/t5/image/serverpage/image-id/88802i58E8277DFF8AF677/image-size/large?v=v2&amp;amp;px=2000" role="button" title="IMCSNNMP1.JPG" alt="IMCSNNMP1.JPG" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Like I said above the device is added to IMC using auto discovery so it seems that IMC is able to communicate with it in certain cases but not when testing SNMP. I'm just not sure why it is failing the test.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Dec 2016 08:38:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6924281#M3397</guid>
      <dc:creator>pattap</dc:creator>
      <dc:date>2016-12-08T08:38:24Z</dc:date>
    </item>
    <item>
      <title>Re: IMC SNMP issues</title>
      <link>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6924470#M3406</link>
      <description>&lt;P&gt;Since it's plaintext SNMP, I would start by capturing SNMP packets between IMC &amp;amp; the device when you're running that test. Check what it's sending, and what (if anything) the device is responding with.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Dec 2016 19:34:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6924470#M3406</guid>
      <dc:creator>LindsayHill</dc:creator>
      <dc:date>2016-12-08T19:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: IMC SNMP issues</title>
      <link>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6924596#M3408</link>
      <description>&lt;P&gt;Just did that last night, it seems snmp requests are hitting the device but for some reason&amp;nbsp;Nortel&amp;nbsp;won't respond with anything.&lt;/P&gt;&lt;P&gt;Then we generated test SNMP traps from the Nortel kit and that finds IMC no problems&lt;/P&gt;</description>
      <pubDate>Fri, 09 Dec 2016 08:18:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6924596#M3408</guid>
      <dc:creator>pattap</dc:creator>
      <dc:date>2016-12-09T08:18:11Z</dc:date>
    </item>
    <item>
      <title>Re: IMC SNMP issues</title>
      <link>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6924826#M3412</link>
      <description>&lt;P&gt;Traps are a separate configuration on the device side. Check and make sure that the Notel will accept snmp from the address/subnet IMC is using.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 10 Dec 2016 00:48:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6924826#M3412</guid>
      <dc:creator>NeilR</dc:creator>
      <dc:date>2016-12-10T00:48:58Z</dc:date>
    </item>
    <item>
      <title>Re: IMC SNMP issues</title>
      <link>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6925029#M3415</link>
      <description>&lt;P&gt;The thing is you can discover these Nortel hosts with IMC no problem - using auto discovery feature. In this case&amp;nbsp;I'd assume Nortel does accept&amp;nbsp;SNMP from IMC.&lt;/P&gt;&lt;P&gt;Also&amp;nbsp;from wireshark capture I can see IMC talking to Nortel, it's only when trying to use that TEST feature it wouldn't work.&lt;/P&gt;&lt;P&gt;It doesn't seem to be affecting the way IMC monitors those hosts, apart from CPU not being monitored properly but that different story I believe - MIB missing etc&lt;/P&gt;</description>
      <pubDate>Mon, 12 Dec 2016 09:20:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6925029#M3415</guid>
      <dc:creator>pattap</dc:creator>
      <dc:date>2016-12-12T09:20:03Z</dc:date>
    </item>
    <item>
      <title>Re: IMC SNMP issues</title>
      <link>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6925065#M3416</link>
      <description>&lt;P&gt;I have also went through nortel&amp;nbsp;documentation and if I understand it correctly snmp v1 is used for traps and v2 for something else -&amp;nbsp;weird&lt;/P&gt;&lt;P&gt;can you actually set IMC to work that way - listen for traps with snmp v1 and monitoring with v2 for the same device?&lt;/P&gt;&lt;P&gt;this is directly from the document&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;FONT face="Arial" size="3"&gt;&lt;STRONG&gt;Trap &lt;/STRONG&gt;&lt;/FONT&gt;&lt;FONT face="Arial" size="3"&gt;– a one-way notification sent from the SNMP agent on a device to&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;the Network Management System (NMS) when a specific condition occurs,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;such as the failure of a system component. In Nortel Communication&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Server 1000 products, the traps are sent in the form of a SNMP V1&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;TRAP-TYPE Protocol Data Unit (PDU). The PDU type is TRAP-V1, and&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;the trap type is Enterprise-Specific.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 13 Dec 2016 14:54:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/imc/imc-snmp-issues/m-p/6925065#M3416</guid>
      <dc:creator>pattap</dc:creator>
      <dc:date>2016-12-13T14:54:03Z</dc:date>
    </item>
  </channel>
</rss>

