- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: Procurve Manager 3.10 scans external networks
Switches, Hubs, and Modems
1753798
Members
7295
Online
108805
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
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
03-18-2010 03:24 AM
03-18-2010 03:24 AM
Procurve Manager 3.10 scans external networks
We have installed Procurve Manager (latest release with updates: PCM C.03.10.201) on a WinXP PC a few days ago. Now we've received security alerts from other sites elsewhere in our country which report that the PCM host is portscanning their devices on port 161 (SNMP). I have no clue as to why PCM apparently attempts to discover devices on non-local networks, and I've not been able to find any configuration item in the PCM GUI which can be used to restrict device discovery to our local subnet only.
Question: How can one configure PCM to restrict device discovery to only specific (local) subnets ?
Question: How can one configure PCM to restrict device discovery to only specific (local) subnets ?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-18-2010 09:59 AM
03-18-2010 09:59 AM
Re: Procurve Manager 3.10 scans external networks
Hello Ole,
according to my experience the PCM will never add any remote subnets by itself. You have to add them manually to the discovery agent.
Please doublecheck your discovery settings:
Agent manager | Discovery | Managed Subnets
If the subnet is set to "unmanaged" the PCM should not touch these ranges with SNMP. Is this the case for your remote subnet?
Cheers,
Michael
according to my experience the PCM will never add any remote subnets by itself. You have to add them manually to the discovery agent.
Please doublecheck your discovery settings:
Agent manager | Discovery | Managed Subnets
If the subnet is set to "unmanaged" the PCM should not touch these ranges with SNMP. Is this the case for your remote subnet?
Cheers,
Michael
Ingentive Networks GmbH
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