- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 5406zl vlan Routing
Switches, Hubs, and Modems
1754235
Members
3333
Online
108812
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
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-20-2010 05:16 AM
тАО04-20-2010 05:16 AM
5406zl vlan Routing
Hello and welcome to HP ressources,i am new here cause i always administrates procurve since a half a year.
Before two weeks i install two parallel networks,which should be at first divided by hardware,so different subnet,and different procurves,uplinks and panels,lwl,and its own 5406zl switch,Every Firm has its own vlan,router, and ip ranges on the 5406.
Now the chiefs whishes to cross the two 5406 to avoid that local traffic between this vlans goes across the wan,so if someone from firm ZOLL wants to administrate a client from firm B it should goes directly across the core switches and than maybe to the access area.
We make a link(rj45 1000mbit) from 5406 to the other,giving both coreswitches an adress from the other vlan,tagged this port for the vlan and there is a connect.
the core switches directly communicate without using there gateways but every other pc,and access switch uses his gateway and so the wan traffic.
to my opinion there muzst be a special routing command to the cores or better on the routers to avoid that traffic between the firms go across the gateway and wan.
Maybe someone knows what do i have to configure on the cores or routers.
Core Firm A Vlan50 10.178.50.50 255.255.254.0
gateway 10.178.50.1
Core Firm B Vlan176 10.180.176.111
255.255.248.0
Gateway 10.180.176.1
Every core either has another vlan and address from the other subnet ,port b2 from every core is tagged on both vlans.
sh ip routing says that there is a connect,but the traffic goes over the gateways and on the wan and takes to long to arrive at the end.100ms and so.
Thanks for your help Peter
Firm B Vlan 176
Before two weeks i install two parallel networks,which should be at first divided by hardware,so different subnet,and different procurves,uplinks and panels,lwl,and its own 5406zl switch,Every Firm has its own vlan,router, and ip ranges on the 5406.
Now the chiefs whishes to cross the two 5406 to avoid that local traffic between this vlans goes across the wan,so if someone from firm ZOLL wants to administrate a client from firm B it should goes directly across the core switches and than maybe to the access area.
We make a link(rj45 1000mbit) from 5406 to the other,giving both coreswitches an adress from the other vlan,tagged this port for the vlan and there is a connect.
the core switches directly communicate without using there gateways but every other pc,and access switch uses his gateway and so the wan traffic.
to my opinion there muzst be a special routing command to the cores or better on the routers to avoid that traffic between the firms go across the gateway and wan.
Maybe someone knows what do i have to configure on the cores or routers.
Core Firm A Vlan50 10.178.50.50 255.255.254.0
gateway 10.178.50.1
Core Firm B Vlan176 10.180.176.111
255.255.248.0
Gateway 10.180.176.1
Every core either has another vlan and address from the other subnet ,port b2 from every core is tagged on both vlans.
sh ip routing says that there is a connect,but the traffic goes over the gateways and on the wan and takes to long to arrive at the end.100ms and so.
Thanks for your help Peter
Firm B Vlan 176
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2010 12:27 PM
тАО04-20-2010 12:27 PM
Re: 5406zl vlan Routing
Paste your config from both
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2010 09:19 PM
тАО04-20-2010 09:19 PM
Re: 5406zl vlan Routing
Core 1
ip default-gateway 10.180.176.1
vlan 1
name "DEFAULT_VLAN"
no untagged A1-A24,B1-B24,C1-C24,D1-D24
no ip address
exit
vlan 176
name "VLAN176"
untagged A1-A24,B1,B3-B24,C1-C24,D1-D24
ip address 10.180.176.111 255.255.248.0
tagged B2
exit
vlan 50
name "VLAN50"
ip address 10.178.50.71 255.255.254.0
tagged B2
primary-vlan 176
Core 2
ip default-gateway 10.178.50.1
vlan 1
name "DEFAULT_VLAN"
no untagged A1-A24,B1-B24,C1-C24,D1-D24
no ip address
exit
vlan 50
name "VLAN50"
untagged A1-A24,B1,B3-B24,C1-C24,D1-D24
ip address 10.178.50.50 255.255.254.0
tagged B2
exit
vlan 176
name "VLAN176"
ip address 10.180.176.143 255.255.248.0
tagged B2
primary-vlan 50
Every Core and Lan has its own cisco router,so its like a campus with two buildings
where we want to connect the two buildings to force traffic between the two buildings not to go over the routers and the wan.
Thanks Peter
ip default-gateway 10.180.176.1
vlan 1
name "DEFAULT_VLAN"
no untagged A1-A24,B1-B24,C1-C24,D1-D24
no ip address
exit
vlan 176
name "VLAN176"
untagged A1-A24,B1,B3-B24,C1-C24,D1-D24
ip address 10.180.176.111 255.255.248.0
tagged B2
exit
vlan 50
name "VLAN50"
ip address 10.178.50.71 255.255.254.0
tagged B2
primary-vlan 176
Core 2
ip default-gateway 10.178.50.1
vlan 1
name "DEFAULT_VLAN"
no untagged A1-A24,B1-B24,C1-C24,D1-D24
no ip address
exit
vlan 50
name "VLAN50"
untagged A1-A24,B1,B3-B24,C1-C24,D1-D24
ip address 10.178.50.50 255.255.254.0
tagged B2
exit
vlan 176
name "VLAN176"
ip address 10.180.176.143 255.255.248.0
tagged B2
primary-vlan 50
Every Core and Lan has its own cisco router,so its like a campus with two buildings
where we want to connect the two buildings to force traffic between the two buildings not to go over the routers and the wan.
Thanks Peter
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