HPE GreenLake Administration
- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Routing Problem
Switches, Hubs, and Modems
1827817
Members
1742
Online
109969
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
Forums
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
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
06-20-2006 01:36 AM
06-20-2006 01:36 AM
Routing Problem
Helle everybody
First, please watch the Picture, attached to this thread.
I was buying a HP Layer 3 Switch to connect our Networks.
Before, the Net 192.168.1.0 was directly connected to the WAN. But now, we have a direct Layer 2 Fiber Connection between the Nets 192.168.1.0 and 192.168.2.0.
On the Layer 3 Swicht, I configurated two VLAN's. One has only one Port (VLAN 2), the rest of the Ports are dedicated to VLAN 1.
If I use the VLAN Management IP as default gateway, everything is working fine. But I can't change the default Gateway of the devices in 192.168.2.0, because, if I do, they don't have access to the WAN.
Is there a way to make the switch transparent, that all MAC-Addresses in 192.168.1.0 are dedicated to Port 1 (VLAN2) of the L3 Switch?
If i just reroute the traffic on the WAN-Router (192.168.2.1) to 192.168.2.2, everything has to pass our Trafficshaper.
any Ideas?
First, please watch the Picture, attached to this thread.
I was buying a HP Layer 3 Switch to connect our Networks.
Before, the Net 192.168.1.0 was directly connected to the WAN. But now, we have a direct Layer 2 Fiber Connection between the Nets 192.168.1.0 and 192.168.2.0.
On the Layer 3 Swicht, I configurated two VLAN's. One has only one Port (VLAN 2), the rest of the Ports are dedicated to VLAN 1.
If I use the VLAN Management IP as default gateway, everything is working fine. But I can't change the default Gateway of the devices in 192.168.2.0, because, if I do, they don't have access to the WAN.
Is there a way to make the switch transparent, that all MAC-Addresses in 192.168.1.0 are dedicated to Port 1 (VLAN2) of the L3 Switch?
If i just reroute the traffic on the WAN-Router (192.168.2.1) to 192.168.2.2, everything has to pass our Trafficshaper.
any Ideas?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2006 02:16 AM
06-20-2006 02:16 AM
Re: Routing Problem
A few ideas..
1. Have you set any routes on the 2824? Since access the the other networks will go via 192.168.2.1, you can set the default route on the 2824 to point to that:
ip route 0.0.0.0 0.0.0.0 192.168.2.1
2. I would recommend clients on VLANs 1 and 2 use the IP address of 2824 VLAN interfaces as their default gateways. With the default route in place they should have access to the rest of the network.
3. On the 192.168.2.1 router, you will also need to configure a static route for VLAN 1, e.g. 'ip route 192.168.1.0 255.255.255.0 192.168.2.2'
4. Often people here suggest that you create a 3rd VLAN in this type of setup. For your current VLAN 2 (192.168.2.0) the only 2 devices in that VLAN would be the 2824 and the Cisco (and I guess the packet shaper). The 3rd VLAN could be 192.168.5.0 and you would move the clients from the current VLAN 2 into that new VLAN.
With the traffic shaper I don't really understand it, does it have to see the mac-address of the clients to work properly? If that is the case then your only choice would be use only VLAN 2. Otherwise I'm guessing you would need to purchase a second one and reposition them behind the 2824.
Hopefully it works on IP addresses though, if so the original suggestions above should work.
Cisco > Packet Shaper > VLAN2 of 2824 > VLAN 1 & 3 clients connected.
1. Have you set any routes on the 2824? Since access the the other networks will go via 192.168.2.1, you can set the default route on the 2824 to point to that:
ip route 0.0.0.0 0.0.0.0 192.168.2.1
2. I would recommend clients on VLANs 1 and 2 use the IP address of 2824 VLAN interfaces as their default gateways. With the default route in place they should have access to the rest of the network.
3. On the 192.168.2.1 router, you will also need to configure a static route for VLAN 1, e.g. 'ip route 192.168.1.0 255.255.255.0 192.168.2.2'
4. Often people here suggest that you create a 3rd VLAN in this type of setup. For your current VLAN 2 (192.168.2.0) the only 2 devices in that VLAN would be the 2824 and the Cisco (and I guess the packet shaper). The 3rd VLAN could be 192.168.5.0 and you would move the clients from the current VLAN 2 into that new VLAN.
With the traffic shaper I don't really understand it, does it have to see the mac-address of the clients to work properly? If that is the case then your only choice would be use only VLAN 2. Otherwise I'm guessing you would need to purchase a second one and reposition them behind the 2824.
Hopefully it works on IP addresses though, if so the original suggestions above should work.
Cisco > Packet Shaper > VLAN2 of 2824 > VLAN 1 & 3 clients connected.
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP