HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- ProCurve 2650 and 802.1x authentication - question
Switches, Hubs, and Modems
1825583
Members
2267
Online
109682
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
Forums
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
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
11-29-2004 02:33 AM
11-29-2004 02:33 AM
ProCurve 2650 and 802.1x authentication - question
Hi,
Implementing 802.1x authentication for my wired (not wireless) company network and need some information before I jump headlong into this:
Building with 3 wiring closets. Each closet has a single HP ProCurve 2650 switch. Switches 1 and 3 are uplinked to switch 2 (servers located in this wiring closet) over Cat5e via GB port on each switch.
What I hope to achieve is a network where only authorized computers can access anything beyond the switch port that they are connected to. To do this, I want to use 802.1x with certificates (already have PKI in place) and port security (MAC address learning).
I appear to need the port security because in my initial tests, everything works fine until you add a downlevel desktop switch - anything connected to that switch has unfettered access through a Dot1x-controlled port after the 1st Dot1x-compliant device authenticates. Using MAC address learning should negate this issue.
I also want to ensure that only authorized network equipment (switches, etc) can connect to switch 2. Based on information from the 2650 admin guide, I understand that 2650 ports can be supplicants to another 2650 port. I would like to configure the uplink ports on switches 1 and 3 to be supplicants to the uplink port on switch 2.
My questions:
1. Given the switch configuration that I've given, are there any issues that I might run into?
2. Each switch handles 30 - 40 computers / printers. In this configuration, would I be able to use a static MAC assignment for each of the uplink ports that are acting as supplicants or will that cause problems?
I have all of the documentation that the HP site offers, but if anyone has any additional documentation (config guides, "notes from the field", etc) on this topic, please email it to me at ewallig@aerocontractors.com.
Thanks in advance.
Implementing 802.1x authentication for my wired (not wireless) company network and need some information before I jump headlong into this:
Building with 3 wiring closets. Each closet has a single HP ProCurve 2650 switch. Switches 1 and 3 are uplinked to switch 2 (servers located in this wiring closet) over Cat5e via GB port on each switch.
What I hope to achieve is a network where only authorized computers can access anything beyond the switch port that they are connected to. To do this, I want to use 802.1x with certificates (already have PKI in place) and port security (MAC address learning).
I appear to need the port security because in my initial tests, everything works fine until you add a downlevel desktop switch - anything connected to that switch has unfettered access through a Dot1x-controlled port after the 1st Dot1x-compliant device authenticates. Using MAC address learning should negate this issue.
I also want to ensure that only authorized network equipment (switches, etc) can connect to switch 2. Based on information from the 2650 admin guide, I understand that 2650 ports can be supplicants to another 2650 port. I would like to configure the uplink ports on switches 1 and 3 to be supplicants to the uplink port on switch 2.
My questions:
1. Given the switch configuration that I've given, are there any issues that I might run into?
2. Each switch handles 30 - 40 computers / printers. In this configuration, would I be able to use a static MAC assignment for each of the uplink ports that are acting as supplicants or will that cause problems?
I have all of the documentation that the HP site offers, but if anyone has any additional documentation (config guides, "notes from the field", etc) on this topic, please email it to me at ewallig@aerocontractors.com.
Thanks in advance.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2004 07:11 PM
11-29-2004 07:11 PM
Re: ProCurve 2650 and 802.1x authentication - question
Hello,
Turn portsecurity on, in this case only the authorised 802.1x client gets access.
#> port-security 1-24 learn-mode port-access
S
Turn portsecurity on, in this case only the authorised 802.1x client gets access.
#> port-security 1-24 learn-mode port-access
S
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP