- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 3500yl config help
Switches, Hubs, and Modems
1753505
Members
4790
Online
108794
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
04-14-2010 05:37 AM
04-14-2010 05:37 AM
3500yl config help
I am implementing a 3500yl in my network to be the core switch. We will have three Vlan's: Default_Vlan, Voice, Servers.
We have a VOIP phone system and currently it is on a different range than our data LAN. We also have Remote branches that are connected VIA a MPLS network that the VOIP travels over.
We are going to leave all workstations and printers in the default VLAN 1.
Servers are going to be In VLAN 10.
Voice is Vlan 20.
Now my question is, do i need to tag all the uplinks through my network with the Server VLAN? or will the request get to Core switch without the tagging.
Next issue, All the servers are in the same Subnet and range as the workstations. If i change from a 255.255.255.0 to a 255.255.255.128, will i be able to assign the two vlans the same subnet in the same IP range?
Thanks for your help
We have a VOIP phone system and currently it is on a different range than our data LAN. We also have Remote branches that are connected VIA a MPLS network that the VOIP travels over.
We are going to leave all workstations and printers in the default VLAN 1.
Servers are going to be In VLAN 10.
Voice is Vlan 20.
Now my question is, do i need to tag all the uplinks through my network with the Server VLAN? or will the request get to Core switch without the tagging.
Next issue, All the servers are in the same Subnet and range as the workstations. If i change from a 255.255.255.0 to a 255.255.255.128, will i be able to assign the two vlans the same subnet in the same IP range?
Thanks for your help
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2010 11:00 PM
04-14-2010 11:00 PM
Re: 3500yl config help
Hello Chris,
regarding your questions:
1) On uplinks (Switch to Switch links) VLAN tagging is mandatory to distinguish between them. For VLAN 1 you can do this, but it is not mandatory. Default setting for VLAN 1 is untagged.
2) It is not possible to assign IP addresses of the same subnet to different VLANs. In you setup I recommend dedicated Class C subnets to each VLAN.
Cheers,
Michael
regarding your questions:
1) On uplinks (Switch to Switch links) VLAN tagging is mandatory to distinguish between them. For VLAN 1 you can do this, but it is not mandatory. Default setting for VLAN 1 is untagged.
2) It is not possible to assign IP addresses of the same subnet to different VLANs. In you setup I recommend dedicated Class C subnets to each VLAN.
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