- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: HP Procurve Manager
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2009 06:28 AM
тАО02-23-2009 06:28 AM
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!!!!)
I would be happy to provide more information & running configs if needed.
Thanks in advance,
Andy Johnson
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2009 07:17 AM
тАО02-23-2009 07:17 AM
Re: HP Procurve Manager
please read this guide
http://cdn.procurve.com/training/Manuals/PCM23-AdminGuide59908850-1207.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2009 09:52 PM
тАО02-23-2009 09:52 PM
Re: HP Procurve Manager
- Is there any pattern in the set of devices that were not discovered? - for example all of them are of some different subnet?
- Check if any of these devices have been for some reason listed under "Unknown Devices" in the Device Tree on left display in PCM.
- Check if the configurations in Tools>Preferences>Discovery ( like exclude devices, managed subnet etc) are all OK.
- Launch Tools> 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.
- 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.
Hope that helps
Javed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2009 04:01 AM
тАО02-24-2009 04:01 AM
Re: HP Procurve Manager
I can see all switches that have not been recognised in 'unknown devices'.
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 ).
I have added the 10.0.0.0 & 10.0.35.0 to pcm global discovery but its still not finding anything?
When I run manual discovery I get:
Checking read access community name...
Read community name failed, operation timed out
Checking write access community name...
Write community name failed, operation timed out
Unable to communicate with device 10.0.35.28
Another thing is our core switches are 10.0.2.3 & 10.0.2.4 pcm is happy to pick up 10.0.2.3 but is blissfully ignores 10.0.2.4.
Thanks in advance
Andy Johnson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2009 07:12 AM
тАО02-24-2009 07:12 AM
Re: HP Procurve Manager
I will assigning an ip address to vlan 100 and applying a static routes help?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2009 07:57 AM
тАО02-24-2009 07:57 AM
SolutionThe timeout error is usually because of unavailability of the PCM server to communicate with the the device.
You can setup the routes such that from PCM server the devices are pingable atleast.
Do let know how that goes about
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2009 12:52 AM
тАО03-05-2009 12:52 AM
Re: HP Procurve Manager
Thanks Again
Andy Johnson
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2009 11:50 PM
тАО03-23-2009 11:50 PM
Re: HP Procurve Manager
Thanks you to respond.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2009 12:40 AM
тАО03-24-2009 12:40 AM
Re: HP Procurve Manager
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.
Cheers
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2009 02:32 AM
тАО03-24-2009 02:32 AM