All future HP kit is comware. I.e. descended from h3c kit they bought.<br><br>Of course it all gets the pro curve brand even if they share nothing in common.<br><br>Tom Laermans &lt;tom.laermans@powersource.cx&gt; wrote:<br><br>
    <div class="moz-cite-prefix">Paul,<br>
      <br>
      Yea, all HP Networking, maybe - but this was catching other HP
      devices too. What's the issue, they should be comware instead? Do
      we have a comware OS type? We have so many I have no clue... :-)<br>
      <br>
      sysDescr matching could be enough.<br>
      <br>
      Tom<br>
      <br>
      On 19/03/2013 13:45, Paul Gear wrote:<br>
    </div>
    <blockquote cite="mid:51485DE8.4010501@gear.dyndns.org" type="cite">Hi
      Tom,
      <br>
      <br>
      A few Comware-based HP switches have been detected as ProCurve
      recently as well.&nbsp; I think it's due to bone-headed changes by HP
      in the sysDescr string they're returning (because, contrary to
      your commit message, everything HP Networking must be
      ProCurve-branded :-).&nbsp; If i grab some snmpwalk results, do you
      need any particular flags, or is just the content of the string
      enough?
      <br>
      <br>
      Regards,
      <br>
      Paul
      <br>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
observium mailing list
<a class="moz-txt-link-abbreviated" href="mailto:observium@observium.org">observium@observium.org</a>
<a class="moz-txt-link-freetext" href="http://postman.memetic.org/cgi-bin/mailman/listinfo/observium">http://postman.memetic.org/cgi-bin/mailman/listinfo/observium</a>
</pre>
    </blockquote>
    <br>