<?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: Monitor Cisco Devices in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234197#M2111</link>
    <description>Thanks for the input.  I have seen those but the mibs listed are mostly routers which is great but I also have a bunch of Cisco Catalyst switches that are not listed.  Any suggestion on how to monitor those?</description>
    <pubDate>Tue, 30 Mar 2004 14:11:44 GMT</pubDate>
    <dc:creator>Mike Tuggle</dc:creator>
    <dc:date>2004-03-30T14:11:44Z</dc:date>
    <item>
      <title>Monitor Cisco Devices</title>
      <link>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234195#M2109</link>
      <description>I know there have been a lot of threads about compiling cisco mibs but I have a little different question.  I want to monitor basically up/down.  I would like to some how change the SYSTEM TYPE from Unknown to Networking.  Any suggestions on how to do this?  If there is currently an easy way to load the mibs I will do that but from what I have read that is not exactly an easy task.</description>
      <pubDate>Tue, 30 Mar 2004 13:50:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234195#M2109</guid>
      <dc:creator>Mike Tuggle</dc:creator>
      <dc:date>2004-03-30T13:50:48Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor Cisco Devices</title>
      <link>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234196#M2110</link>
      <description>If you look in Options --&amp;gt; Discovery --&amp;gt; Manage Systems Types you'll see a number of Cisco devices that have rules to be automatically recognized.  It looks like hpSIM is looking at an SNMP OID of 1.3.6.1.4.1.9.1.x with the last number being a unique value for each of the Cisco devices.</description>
      <pubDate>Tue, 30 Mar 2004 14:05:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234196#M2110</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2004-03-30T14:05:04Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor Cisco Devices</title>
      <link>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234197#M2111</link>
      <description>Thanks for the input.  I have seen those but the mibs listed are mostly routers which is great but I also have a bunch of Cisco Catalyst switches that are not listed.  Any suggestion on how to monitor those?</description>
      <pubDate>Tue, 30 Mar 2004 14:11:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234197#M2111</guid>
      <dc:creator>Mike Tuggle</dc:creator>
      <dc:date>2004-03-30T14:11:44Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor Cisco Devices</title>
      <link>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234198#M2112</link>
      <description>Look above at my previous post.  The SNMP OID is being used to uniquely identify each CISCO device:&lt;BR /&gt;&lt;BR /&gt;1.3.6.1.4.1.9.2.40 = Cisco 1000&lt;BR /&gt;1.3.6.1.4.1.9.2.41 = Cisco 1003&lt;BR /&gt;1.3.6.1.4.1.9.2.44 = Cisco 1004&lt;BR /&gt;&lt;BR /&gt;What you're looking for is a unique OID that can identify the device.  In the case of the devices above, apparently the presence of the OID itself is unique to the device (the device type manager isn't looking for a particular value, just anything). I don't have a Catalyst to play with, but maybe someone else out there does.  An SNMP browser could be helpful in viewing the data available at various OIDs.  Once you have something that you can use to identify it, you have your rule and you can plug it in.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 30 Mar 2004 14:44:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234198#M2112</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2004-03-30T14:44:59Z</dc:date>
    </item>
    <item>
      <title>Re: Monitor Cisco Devices</title>
      <link>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234199#M2113</link>
      <description>Thanks I believe I just got what you are talking about.  You are saying to find the OID string and just create a new rule.  That sounds easy enough.  Thanks for the help.</description>
      <pubDate>Tue, 30 Mar 2004 14:59:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/monitor-cisco-devices/m-p/3234199#M2113</guid>
      <dc:creator>Mike Tuggle</dc:creator>
      <dc:date>2004-03-30T14:59:16Z</dc:date>
    </item>
  </channel>
</rss>

