<?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: HP Procurve Manager in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364306#M17551</link>
    <description>Hi Andy. I have the same problem with SNMP and community name. I'm interested to know how you resolved your problem . &lt;BR /&gt;Thanks you to respond.</description>
    <pubDate>Tue, 24 Mar 2009 06:50:37 GMT</pubDate>
    <dc:creator>willinfo</dc:creator>
    <dc:date>2009-03-24T06:50:37Z</dc:date>
    <item>
      <title>HP Procurve Manager</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364299#M17544</link>
      <description>Hello Everyone!!&lt;BR /&gt;&lt;BR /&gt;I have recently installed hp procurve manager so that we have more control over our core network.  Unfortunately it is only picking up about 25% of our switches?  I have looked at all device configs and I can not see any difference in the way snmp is set on the devices that are not being discovered by hp procurve manager. (Some expert help needed i think!!!!)&lt;BR /&gt;I would be happy to provide more information &amp;amp; running configs if needed.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;BR /&gt;&lt;BR /&gt;Andy Johnson</description>
      <pubDate>Mon, 23 Feb 2009 14:28:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364299#M17544</guid>
      <dc:creator>andy_johnson(cnews)</dc:creator>
      <dc:date>2009-02-23T14:28:16Z</dc:date>
    </item>
    <item>
      <title>Re: HP Procurve Manager</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364300#M17545</link>
      <description>hi Andy&lt;BR /&gt;&lt;BR /&gt;please read this guide &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://cdn.procurve.com/training/Manuals/PCM23-AdminGuide59908850-1207.pdf" target="_blank"&gt;http://cdn.procurve.com/training/Manuals/PCM23-AdminGuide59908850-1207.pdf&lt;/A&gt;</description>
      <pubDate>Mon, 23 Feb 2009 15:17:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364300#M17545</guid>
      <dc:creator>cenk sasmaztin</dc:creator>
      <dc:date>2009-02-23T15:17:10Z</dc:date>
    </item>
    <item>
      <title>Re: HP Procurve Manager</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364301#M17546</link>
      <description>Some troubleshooting tips that might help:&lt;BR /&gt;&lt;BR /&gt;- Is there any pattern in the set of devices that were not discovered? - for example all of them are of some different subnet?&lt;BR /&gt;- Check if any of these devices have been for some reason listed under "Unknown Devices" in the Device Tree on left display in PCM.&lt;BR /&gt;- Check if the configurations in Tools&amp;gt;Preferences&amp;gt;Discovery ( like exclude devices, managed subnet etc) are all OK.&lt;BR /&gt; - Launch Tools&amp;gt; Manual Discovery Wizard and specify IP of a ( carefully determined and not yet discovered) device  through which many others in the network can possibly be reached. Uncheck "Use defaults " and supply correct SNMP/CLI credentials for that device.&lt;BR /&gt;- If the above operation fails, check few logs under server\logs\ like Disco*.log, Cs-err*.log, Cs-out*.log and see for some clue - there could be some messages giving an hint to the problem.&lt;BR /&gt;&lt;BR /&gt;Hope that helps&lt;BR /&gt;Javed&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Feb 2009 05:52:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364301#M17546</guid>
      <dc:creator>Javed Padinhakara</dc:creator>
      <dc:date>2009-02-24T05:52:03Z</dc:date>
    </item>
    <item>
      <title>Re: HP Procurve Manager</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364302#M17547</link>
      <description>Thanks for you for getting back to me&lt;BR /&gt;&lt;BR /&gt;I can see all switches that have not been recognised in 'unknown devices'.&lt;BR /&gt;It appears that the switches in unknown devices all share the same ip range '10.0.35.x(edges) apart from one 10.0.2.4(second core ).&lt;BR /&gt;I have added the 10.0.0.0 &amp;amp; 10.0.35.0 to pcm global discovery but its still not finding anything?&lt;BR /&gt;When I run manual discovery I get:&lt;BR /&gt;&lt;BR /&gt;Checking read access community name...&lt;BR /&gt;Read community name failed, operation timed out&lt;BR /&gt;&lt;BR /&gt;Checking write access community name...&lt;BR /&gt;Write community name failed, operation timed out&lt;BR /&gt;&lt;BR /&gt;Unable to communicate with device 10.0.35.28&lt;BR /&gt;&lt;BR /&gt;Another thing is our core switches are 10.0.2.3 &amp;amp; 10.0.2.4 pcm is happy to pick up 10.0.2.3 but is blissfully ignores 10.0.2.4.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;&lt;BR /&gt;Andy Johnson&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 24 Feb 2009 12:01:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364302#M17547</guid>
      <dc:creator>andy_johnson(cnews)</dc:creator>
      <dc:date>2009-02-24T12:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: HP Procurve Manager</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364303#M17548</link>
      <description>Ok I think I have worked this one out it seems that the time out is being caused by the snmp traffic having no route back from vlan 135(switches) to vlan 100(servers). &lt;BR /&gt;&lt;BR /&gt;I will assigning an ip address to vlan 100 and applying a static routes help?</description>
      <pubDate>Tue, 24 Feb 2009 15:12:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364303#M17548</guid>
      <dc:creator>andy_johnson(cnews)</dc:creator>
      <dc:date>2009-02-24T15:12:24Z</dc:date>
    </item>
    <item>
      <title>Re: HP Procurve Manager</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364304#M17549</link>
      <description>Yes Andy. That should do the trick.&lt;BR /&gt;&lt;BR /&gt;The timeout error is usually because of unavailability of the PCM server to communicate with the the device.&lt;BR /&gt;&lt;BR /&gt;You can setup the routes such that from PCM server the devices are pingable atleast.&lt;BR /&gt;&lt;BR /&gt;Do let know how that goes about</description>
      <pubDate>Tue, 24 Feb 2009 15:57:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364304#M17549</guid>
      <dc:creator>Javed Padinhakara</dc:creator>
      <dc:date>2009-02-24T15:57:03Z</dc:date>
    </item>
    <item>
      <title>Re: HP Procurve Manager</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364305#M17550</link>
      <description>Thanks for your advice I have done the configuraion that was necessary and can now see all our switches using pcm.&lt;BR /&gt;&lt;BR /&gt;Thanks Again&lt;BR /&gt;&lt;BR /&gt;Andy Johnson</description>
      <pubDate>Thu, 05 Mar 2009 08:52:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364305#M17550</guid>
      <dc:creator>andy_johnson(cnews)</dc:creator>
      <dc:date>2009-03-05T08:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: HP Procurve Manager</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364306#M17551</link>
      <description>Hi Andy. I have the same problem with SNMP and community name. I'm interested to know how you resolved your problem . &lt;BR /&gt;Thanks you to respond.</description>
      <pubDate>Tue, 24 Mar 2009 06:50:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364306#M17551</guid>
      <dc:creator>willinfo</dc:creator>
      <dc:date>2009-03-24T06:50:37Z</dc:date>
    </item>
    <item>
      <title>Re: HP Procurve Manager</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364307#M17552</link>
      <description>The issue I experienced was caused by our vlan's set up!  As it turned out snmp was timing out because it could not find the ip address I supplied to the manual discovery wizard.&lt;BR /&gt;&lt;BR /&gt;My problem was solved by double and triple checking the snmp settings and then assigning an ip address to the corresponding vlan so that snmp has connectivity.&lt;BR /&gt;&lt;BR /&gt;Cheers &lt;BR /&gt;&lt;BR /&gt;Andy</description>
      <pubDate>Tue, 24 Mar 2009 07:40:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364307#M17552</guid>
      <dc:creator>andy_johnson(cnews)</dc:creator>
      <dc:date>2009-03-24T07:40:13Z</dc:date>
    </item>
    <item>
      <title>Re: HP Procurve Manager</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364308#M17553</link>
      <description>It's possible that you tell me exactly what you did because I don't know how to do ?</description>
      <pubDate>Tue, 24 Mar 2009 09:32:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/hp-procurve-manager/m-p/4364308#M17553</guid>
      <dc:creator>willinfo</dc:creator>
      <dc:date>2009-03-24T09:32:18Z</dc:date>
    </item>
  </channel>
</rss>

