- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Procurve Manager fails to map 2650s
Switches, Hubs, and Modems
1752802
Members
5563
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
12-20-2006 02:18 AM
12-20-2006 02:18 AM
HP Procurve Manager fails to correctly map four 2650 switches while mapping correctly every other device on my network.
More precisely, 2650s remain disconnected from two core-switches (two 9304s), PCM fails to discover uplinks and 2600s remain isolated.
I know that 2600 is the worst family of Procurve offer, they have no sFlow neither RMON but I think that doscvery should work even without these protocols.
More precisely, 2650s remain disconnected from two core-switches (two 9304s), PCM fails to discover uplinks and 2600s remain isolated.
I know that 2600 is the worst family of Procurve offer, they have no sFlow neither RMON but I think that doscvery should work even without these protocols.
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-20-2006 10:30 AM
12-20-2006 10:30 AM
Solution
I believe the reason is that 2600's are not mapping correctly to the 9300's is because the 2600's support only LLDP, and the 9300's support only FDP.
It mentions this in the release notes for PCM 2.1:
ftp://ftp.hp.com/pub/networking/software/PCM21-Release-Notes-1105.htm#9300
LLDP-capable devices connected directly to 93xx devices may not map properly. Using a CDP-capable device between the 93xx and LLDP-capable device will resolve the problem.
It mentions this in the release notes for PCM 2.1:
ftp://ftp.hp.com/pub/networking/software/PCM21-Release-Notes-1105.htm#9300
LLDP-capable devices connected directly to 93xx devices may not map properly. Using a CDP-capable device between the 93xx and LLDP-capable device will resolve the problem.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP