- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Procurve 2650 VLAN
-
-
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 VLAN
- 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
02-25-2008 06:57 AM
02-25-2008 06:57 AM
Procurve 2650 VLAN
Procurve 2650 VLAN
We are migrating into a new VLAN environment consisting of two HP 2650 48 port switches. These two switches are Daisy-Chained in connectivity, our Core switch is connected to Sales2 first then from Sales2 to Sales1 (which is the end of the chain).
I made an incorrect setting on Sales1 causing no connectivity to it's Web GUI, and is completely unreachable. To access it I use the wired port on the back.
These switches were moving from Default_VLAN(1) to VLAN4 (CLIENTS), Sales2 switch working correctly.
Is there a command to erase all the settings on the Sales1 switch to start over? And if i do this, will any clients in Sales1 be able to travel through the chain (even if they are not on VLAN4)?
thanks
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-25-2008 03:02 PM
02-25-2008 03:02 PM
Re: Procurve 2650 VLAN
Re: Procurve 2650 VLAN
If you were to untag VLAN4 on the Sales2 port that connects to Sales1, it would ensure that all users on Sales1 were not affected during this reconfiguration.... but it's probably better to do after hours.
You can attach your configurations here and a network map if you need further help.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-26-2008 05:50 AM
02-26-2008 05:50 AM
Re: Procurve 2650 VLAN
Re: Procurve 2650 VLAN
more later!
thanks
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
02-27-2008 06:22 AM
02-27-2008 06:22 AM
Re: Procurve 2650 VLAN
Re: Procurve 2650 VLAN
"Erase startup-config" righted the situation, bringing me back to setup and restoring all ports to VLAN1 (Default).
I created the same VLAN's all over again then tried moving port 19 (on Sales1)to VLAN4, which should have made that machine jump from 192.168.1.x to 192.168.4.x . All that happened was complete communication loss for that machine.
Is there anything special I need to get this working?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
03-05-2008 12:19 PM
03-05-2008 12:19 PM
Re: Procurve 2650 VLAN
Re: Procurve 2650 VLAN
Start-->Run-->[in the box, type]cmd
In the CMD window, run
C:\>ipconfig /release
C:\>ipconfig /renew
This will force the computer to get rid of its current ip address and ask for a new one.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2018 Hewlett Packard Enterprise Development LP