- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- 5308 Routing
Switches, Hubs, and Modems
1752802
Members
5897
Online
108789
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-05-2007 02:00 AM
тАО01-05-2007 02:00 AM
HP Guru types
I have come into a new situation/job and would like your help in resolving routing issues on this network, and its bottlenecks.
The Current network setup is:
6 Vlans
172.16.0.0
172.17.0.0
172.18.0.0
(3)192.168.x.x - These are used for firewalls(?)
Each 172.x.x.x VLAN uses a default gateway of a Windows 2000 box with two nics running a routes.bat file. One nic is on the 172.x.x.x network, and another is on a network of 192.168.x.x which connects to the firewall and pushes internet traffic out the door.
Now this setup works, but I have never seen anything like it in my previous jobs, and I KNOW this is creating a bottleneck in the network. We have a 5308xl which currently we just use for switch connectivity, but I'd like to use for our routing.
Help! Where do I start?
I have come into a new situation/job and would like your help in resolving routing issues on this network, and its bottlenecks.
The Current network setup is:
6 Vlans
172.16.0.0
172.17.0.0
172.18.0.0
(3)192.168.x.x - These are used for firewalls(?)
Each 172.x.x.x VLAN uses a default gateway of a Windows 2000 box with two nics running a routes.bat file. One nic is on the 172.x.x.x network, and another is on a network of 192.168.x.x which connects to the firewall and pushes internet traffic out the door.
Now this setup works, but I have never seen anything like it in my previous jobs, and I KNOW this is creating a bottleneck in the network. We have a 5308xl which currently we just use for switch connectivity, but I'd like to use for our routing.
Help! Where do I start?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-05-2007 11:50 AM
тАО01-05-2007 11:50 AM
Solution
That is a fairly unique setup you have there...
On the 5300 to make it the router these are the basic steps you'd need to take:
1. Enable 'IP routing'
2. Give each VLAN an IP address (which will be the default gateway for the clients on the respective VLANs). You may want to set this as the IP addresses that are currently in use on the 2000 server, but you'll obviously need to be careful not to cause any IP address conflicts.
3. Create a default route to the firewall, 'ip route 0.0.0.0 0.0.0.0'
4. On the firewall, make sure it has routes pointing back to the 5300.
5. For DHCP, if the 2000 server is giving out addresses you'll need to add an 'ip helper-address' for each VLAN on the 5300.
There may be some other hiccups you run into along the way but that should give you a good start.
On the 5300 to make it the router these are the basic steps you'd need to take:
1. Enable 'IP routing'
2. Give each VLAN an IP address (which will be the default gateway for the clients on the respective VLANs). You may want to set this as the IP addresses that are currently in use on the 2000 server, but you'll obviously need to be careful not to cause any IP address conflicts.
3. Create a default route to the firewall, 'ip route 0.0.0.0 0.0.0.0
4. On the firewall, make sure it has routes pointing back to the 5300.
5. For DHCP, if the 2000 server is giving out addresses you'll need to add an 'ip helper-address' for each VLAN on the 5300.
There may be some other hiccups you run into along the way but that should give you a good start.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-05-2007 12:55 PM
тАО01-05-2007 12:55 PM
Re: 5308 Routing
Thanks Matt
So do I then use ACLs in the 5308 to control what traffic can touch what within VLANS?
Do you have a good link on building ACLs in the 5308?
Thanks again
So do I then use ACLs in the 5308 to control what traffic can touch what within VLANS?
Do you have a good link on building ACLs in the 5308?
Thanks again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-05-2007 02:35 PM
тАО01-05-2007 02:35 PM
Re: 5308 Routing
ACL's are probably the way to go in this instance if you need to tighten it down a little (sometimes you can also use source-port filtering depending on the requirement).
Apart from the manuals for the product, searching the forums here is probably a good start for ACL assistance - otherwise if you can list down what resources you need to permit/deny, myself or someone else here can probably help you out.
Apart from the manuals for the product, searching the forums here is probably a good start for ACL assistance - otherwise if you can list down what resources you need to permit/deny, myself or someone else here can probably help you out.
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