- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- PCM 3.1 & Discovery Anomolies
Switches, Hubs, and Modems
1752563
Members
4492
Online
108788
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
тАО07-28-2010 04:43 PM
тАО07-28-2010 04:43 PM
PCM 3.1 & Discovery Anomolies
Hi,
I am running PCM 3.1 with a large site and I have two issues.
-When a device is decommissioned and its IP is assigned to another device say 5406 to 3500yl or even a Cisco CAT, the device remains within PCM and even after a discovery has run, all the infromation stays in thier relvant to the retired device
-The device name and information does not update after a Discovery has run. i.e. device name may reference old DNS name etc.
I have seen this on other small sites and have always just removed the device and rediscovered it. why is this not happening automatically?
Cheers,
Trev.
I am running PCM 3.1 with a large site and I have two issues.
-When a device is decommissioned and its IP is assigned to another device say 5406 to 3500yl or even a Cisco CAT, the device remains within PCM and even after a discovery has run, all the infromation stays in thier relvant to the retired device
-The device name and information does not update after a Discovery has run. i.e. device name may reference old DNS name etc.
I have seen this on other small sites and have always just removed the device and rediscovered it. why is this not happening automatically?
Cheers,
Trev.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2010 05:00 AM
тАО07-29-2010 05:00 AM
Re: PCM 3.1 & Discovery Anomolies
Hi
1. This is indeed the case. When a device is decommissioned, it is a good routine to delete it in PCM as well.
This is happening as the IP address is binded to the sysOiD of the specific switch model.
2. The current scans performed does not include any dns lookup. It will only scan the device itself. Once a device is discovered, it will not perform any dns lookup on the displayed name.
Basically both issues you mention is by design.
You could check with your sales representative for the possibility of filing a enhancement request.
Tore
1. This is indeed the case. When a device is decommissioned, it is a good routine to delete it in PCM as well.
This is happening as the IP address is binded to the sysOiD of the specific switch model.
2. The current scans performed does not include any dns lookup. It will only scan the device itself. Once a device is discovered, it will not perform any dns lookup on the displayed name.
Basically both issues you mention is by design.
You could check with your sales representative for the possibility of filing a enhancement request.
Tore
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-29-2010 03:26 PM
тАО07-29-2010 03:26 PM
Re: PCM 3.1 & Discovery Anomolies
Thanks for the Explanation Tore.
I have many feature request forms to fill out as the software has so much potential.
Trev
I have many feature request forms to fill out as the software has so much potential.
Trev
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2010 04:18 AM
тАО08-03-2010 04:18 AM
Re: PCM 3.1 & Discovery Anomolies
Hi Trevor
Just to get back on item nr 1.
There is a good chance that this might change under PCM 3.2.
Im not gonna state it 100%, but its a good chance they will implement SySOiD check etc.. during device polling cycle.
Tore
Just to get back on item nr 1.
There is a good chance that this might change under PCM 3.2.
Im not gonna state it 100%, but its a good chance they will implement SySOiD check etc.. during device polling cycle.
Tore
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