- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 5308XL and 2524 vlan routing
Switches, Hubs, and Modems
1752866
Members
4494
Online
108791
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
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО01-23-2006 09:00 PM
тАО01-23-2006 09:00 PM
We are in the process of converting the connection between a 5308xl and a 2524 from ADSL with cisco routers to a direct fiber connection.
I would like to keep the subnet used on the 2524 network site. How do I go about setting this up? VLAN and routing? I have never setup VLAN's before.
The network on the 5308 side is 10.47.8.0 255.255.252.0 and the network on the 2524 side is 10.47.12.0 255.255.252.0
I also need to have DHCP access.
Any info is appreciated..
-rgds
Jan Fredrik
I would like to keep the subnet used on the 2524 network site. How do I go about setting this up? VLAN and routing? I have never setup VLAN's before.
The network on the 5308 side is 10.47.8.0 255.255.252.0 and the network on the 2524 side is 10.47.12.0 255.255.252.0
I also need to have DHCP access.
Any info is appreciated..
-rgds
Jan Fredrik
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-23-2006 09:58 PM
тАО01-23-2006 09:58 PM
Solution
Assume:
Port 26 on HP2524
connected to
Port A1 on 5308 XL.
HP2500 DHCP server on subnet different from 10.47.12.0/255.255.252.0 - e.g. on the 10.47.8.0/255.255.252.0 network.
Define:
VLAN 100 as the VLAN serving the 10.47.8.0 255.255.252.0 network
VLAN 200 as the VLAN on the 2524.
Configuration:
HP2500:
vlan 200
name Remote
untagged 1-24
tagged 26
exit
HP5308 XL:
ip routing
vlan 100
name Local
! Untag all ports used locally
untagged a2-a12, b1-b16
ip address 10.47.8.x 255.255.252.0
vlan 200
name Remote
tagged A1
ip address 10.47.12.x 255.255.252.0
! use 10.47.12.x as Default GW on clients
! at remote site
! Define
! helper-address
ip helper-address 10.47.8.x
Regards
Regnar
Port 26 on HP2524
connected to
Port A1 on 5308 XL.
HP2500 DHCP server on subnet different from 10.47.12.0/255.255.252.0 - e.g. on the 10.47.8.0/255.255.252.0 network.
Define:
VLAN 100 as the VLAN serving the 10.47.8.0 255.255.252.0 network
VLAN 200 as the VLAN on the 2524.
Configuration:
HP2500:
vlan 200
name Remote
untagged 1-24
tagged 26
exit
HP5308 XL:
ip routing
vlan 100
name Local
! Untag all ports used locally
untagged a2-a12, b1-b16
ip address 10.47.8.x 255.255.252.0
vlan 200
name Remote
tagged A1
ip address 10.47.12.x 255.255.252.0
! use 10.47.12.x as Default GW on clients
! at remote site
! Define
! helper-address
ip helper-address 10.47.8.x
Regards
Regnar
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-24-2006 12:53 AM
тАО01-24-2006 12:53 AM
Re: 5308XL and 2524 vlan routing
Thanks, that helped a lot.. A stupid question... If I have 2x 2524 on the remote site, do I have to setup VLAN on both boxes? One switch is connected to the other (stacked)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-24-2006 02:40 AM
тАО01-24-2006 02:40 AM
Re: 5308XL and 2524 vlan routing
You don't have to - but it is in my opinion the "right" way to it.
It gives you the flexibility to add more VLANs at a later time (VoIP and other stuff might show up).
Furthermore it is easier to manage, if you on each switch can identify the VLANs are used on the switch.
IMHO the configuration is an important part of your documentation. As with other documentation - make it explicit yet concise.
E.g.:
HP2500-1 (connected to 5300):
int 24
name "HP2500-2 24"
vlan 200
name Remote
tag 24,26
untag 1-23
HP2500-2 (connected to first HP2500):
int 24
name "HP2500-1 24"
vlan 200
name Remote
tag 24
untag 1-23
The shortcut would be to connect number 2 switch to one of the untagged VLAN 200 ports on number 1.
It gives you the flexibility to add more VLANs at a later time (VoIP and other stuff might show up).
Furthermore it is easier to manage, if you on each switch can identify the VLANs are used on the switch.
IMHO the configuration is an important part of your documentation. As with other documentation - make it explicit yet concise.
E.g.:
HP2500-1 (connected to 5300):
int 24
name "HP2500-2 24"
vlan 200
name Remote
tag 24,26
untag 1-23
HP2500-2 (connected to first HP2500):
int 24
name "HP2500-1 24"
vlan 200
name Remote
tag 24
untag 1-23
The shortcut would be to connect number 2 switch to one of the untagged VLAN 200 ports on number 1.
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