- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- ProCurve blocking traffic to internal ports
Switches, Hubs, and Modems
1753580
Members
6369
Online
108796
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
08-11-2009 08:45 AM
08-11-2009 08:45 AM
ProCurve blocking traffic to internal ports
We are upgrading several of our LANs to new HP switches. We are using 5 VLANs to segregate our traffic. We have 2524 switches out in the individual buildings, and either 4108s or 4208s back at the head ends. I am running into an issue where the internal traffic is being blocked on the 2524s. For example, If I have a printer (or any node) plugged into a port that is a member of the same VLAN as a PC that is plugged into the same 2524 switch, I cannot access it or ping the ip address. I can ping it from a PC plugged into the 4108 back at the head end, or from a PC in a remote site hundreds of miles away, but not plugged into the same switch. If I cycle the power to the switch, I can access the resource briefly, then it appears to be blocked again when the switch has run for a brief period. The event logs show the port being blocked by LACP when the switch completes it's POST. I can turn that off easily enough, but it seems like that usually runs in other locations where we are successfully running these without VLANs. I have also checked to make sure that the tagging/untagging is identical throughout the paths and that the VLAN names are identical. Any suggestions? Thanks!
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