Skip to ContentSkip to Footer
Start of content
Online Expert Day - HPE Data Storage - Live Now
April 24/25 - Online Expert Day - HPE Data Storage - Live Now
Read more
Read more
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- ProCurve 2650 - J4899B - VLAN routing problem
Switches, Hubs, and Modems
turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
-
Categories
- Topics
- Hybrid IT with Cloud
- Mobile & IoT
- IT for Data & Analytics
- Transformation
- Strategy and Technology
- Products
- Cloud
- Integrated Systems
- Networking
- Servers and Operating Systems
- Services
- Storage
- Company
- Events
- Partner Solutions and Certifications
- Welcome
- Welcome
- Announcements
- Tips and Tricks
- Feedback
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- Converged Data Center Infrastructure
- Digital Transformation
- Grounded in the Cloud
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- Networking
- OEM Solutions
- Servers: The Right Compute
- Telecom IQ
- Transforming IT
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Categories
-
Forums
-
Blogs
-
InformationEnglish
ProCurve 2650 - J4899B - VLAN routing problem
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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-27-2006 05:39 AM
01-27-2006 05:39 AM
ProCurve 2650 - J4899B - VLAN routing problem
ProCurve 2650 - J4899B - VLAN routing problem
The switch is running firmware H.08.86.
4 VLANS are defined and were working splendidly until today.
Today, for some reason, I can hit all of the VLAN addresses from a remote subnet, but I cannot ping any of the nodes on VLANs 2 & 3.
Communication to VLANs 1 & 8 are fine.
A node on VLAN 1 cannot even ping a node on VLAN 2, even though both are connected to the same physical switch.
From the switch, I can ping all of the nodes on any VLAN.
It appears as though the switch has suddenly decided to stop routing packets (ip routing is enabled).
I've tried dropping and re-creating the VLANs to no avail.
At this point, I'm seriously considering erasing the startup config and starting over.
Anyone ever run into this type of problem before?
4 VLANS are defined and were working splendidly until today.
Today, for some reason, I can hit all of the VLAN addresses from a remote subnet, but I cannot ping any of the nodes on VLANs 2 & 3.
Communication to VLANs 1 & 8 are fine.
A node on VLAN 1 cannot even ping a node on VLAN 2, even though both are connected to the same physical switch.
From the switch, I can ping all of the nodes on any VLAN.
It appears as though the switch has suddenly decided to stop routing packets (ip routing is enabled).
I've tried dropping and re-creating the VLANs to no avail.
At this point, I'm seriously considering erasing the startup config and starting over.
Anyone ever run into this type of problem before?
2 REPLIES
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
01-31-2006 09:30 AM
01-31-2006 09:30 AM
Re: ProCurve 2650 - J4899B - VLAN routing problem
Re: ProCurve 2650 - J4899B - VLAN routing problem
first: ping every ipaddress local from the switch, if you cannot ping any interface, maybe a layer1-problem.
second: If you have problems with clients in a special vlan. check the default-gatewayentry of the clients.
third: check speed and autoneg of the switchports and the clients
fourth: fine stable runnig now?
cu
Guido
second: If you have problems with clients in a special vlan. check the default-gatewayentry of the clients.
third: check speed and autoneg of the switchports and the clients
fourth: fine stable runnig now?
cu
Guido
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-01-2006 12:10 AM
02-01-2006 12:10 AM
Re: ProCurve 2650 - J4899B - VLAN routing problem
Re: ProCurve 2650 - J4899B - VLAN routing problem
Clients on each VLAN could ping their respective default gateways.
All nodes and switchports were set to 100-full except 49 & 50 which were set to auto-1000 and were configured as a static trunk.
All nodes on VLANs 2 & 3 were DHCP-enabled and were receiving the correct configuration from the DHCP server on VLAN 1.
From the switch itself, I could ping any host and get a response. Nodes on the same VLAN could ping each other, but could intermittently ping nodes on other VLANS. On average, I was seeing 50% packet loss on the switch.
Cables were swapped with known good ones, but the porblem persisted.
I erased the startup config and rebuilt the configuration. Still no go.
As a last ditch effort, I performed the factory default reset. This also didn't quite work right. The switch retained the manager password I had assigned in the previous configuration.
I've received another 2650 J4899B switch and configured it to take the place of the offending switch and haven't encountered any problems.
The intermittently functional switch is being replaced today.
All nodes and switchports were set to 100-full except 49 & 50 which were set to auto-1000 and were configured as a static trunk.
All nodes on VLANs 2 & 3 were DHCP-enabled and were receiving the correct configuration from the DHCP server on VLAN 1.
From the switch itself, I could ping any host and get a response. Nodes on the same VLAN could ping each other, but could intermittently ping nodes on other VLANS. On average, I was seeing 50% packet loss on the switch.
Cables were swapped with known good ones, but the porblem persisted.
I erased the startup config and rebuilt the configuration. Still no go.
As a last ditch effort, I performed the factory default reset. This also didn't quite work right. The switch retained the manager password I had assigned in the previous configuration.
I've received another 2650 J4899B switch and configured it to take the place of the offending switch and haven't encountered any problems.
The intermittently functional switch is being replaced today.
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2018 Hewlett Packard Enterprise Development LP