- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Establishing static IP routing
Switches, Hubs, and Modems
1753665
Members
5828
Online
108798
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
тАО10-26-2004 09:04 AM
тАО10-26-2004 09:04 AM
Establishing static IP routing
We have a 4108gl switch acting as our backbone. Right now we're using 2 IP subnets in our network; one for admin stuff and one for process stuff. The admin IP subnet is 10.36.12.0/23 and the other is 10.36.58.0/24. Right now our main CISCO 3600 router is handling the layer 3 routing to keep the traffic flowing between these two subnets. We're going to have the router down for replacement in a few days and I'd like to not hinder operations. So is it possible for me to establish some internal layer 3 IP routing on the 4108 and keep that job off the router? I've never done this... so I need some good info.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-28-2004 10:58 PM
тАО10-28-2004 10:58 PM
Re: Establishing static IP routing
Hi Dwight,
See: http://www.hp.com/rnd/support/manuals/4108gl.htm
There is one chapter about routing. Should not be a problem I suppose.
Regards,
Alexander
See: http://www.hp.com/rnd/support/manuals/4108gl.htm
There is one chapter about routing. Should not be a problem I suppose.
Regards,
Alexander
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-29-2004 12:48 AM
тАО10-29-2004 12:48 AM
Re: Establishing static IP routing
Yes, I've seen the manual. But it is not very clear on how to accomplish my situation. I was looking for info from someone who might have done this before. I have called HP and they gave me instructions on how to accomplish my goal. But I'd still be interested in hearing other ideas.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-04-2004 08:33 PM
тАО11-04-2004 08:33 PM
Re: Establishing static IP routing
I assume you have both subnets in different VLAN's on the switch.
Enabling routing is as easy as:
switch(config)#ip routing
The VLAN's need to have ip-addresses assigned to them.
Things to consider:
Your clients and servers have default gateways assigned. I assume they have the Cisco 3600 as the default gateway (for both subnets).
Only enabling ip routing on the switch will not be enough to establish communications between the two subnets (from the clients perspective).
You can do two things:
- Assign the VLAN's on the switch unused ip-addresses, and on the day change the default gateway of all nodes (clients/servers/printers etc).
- Right after the 3600 is disconnected from the network, assign the VLAN's the ip-addresses that 3600 had, and enable routing.
I would choose for the second option. The first option is a lot of work (changing DHCP option for the clients isn't too much work, manually changing the def gw on the servers and printers is. (and changing it back again after maintenance)).
If you do the second option, and some nodes aren't working immediately, clear their arp-cache (arp -d *) or reboot them.
A final note:
If you use the 3600 only for connecting the subnets, you can consider using the switch for a router as a permanent solution (not bringing back the 3600). This has two distinct advantages:
- The performance is better.
- One less single point of failure
Enabling routing is as easy as:
switch(config)#ip routing
The VLAN's need to have ip-addresses assigned to them.
Things to consider:
Your clients and servers have default gateways assigned. I assume they have the Cisco 3600 as the default gateway (for both subnets).
Only enabling ip routing on the switch will not be enough to establish communications between the two subnets (from the clients perspective).
You can do two things:
- Assign the VLAN's on the switch unused ip-addresses, and on the day change the default gateway of all nodes (clients/servers/printers etc).
- Right after the 3600 is disconnected from the network, assign the VLAN's the ip-addresses that 3600 had, and enable routing.
I would choose for the second option. The first option is a lot of work (changing DHCP option for the clients isn't too much work, manually changing the def gw on the servers and printers is. (and changing it back again after maintenance)).
If you do the second option, and some nodes aren't working immediately, clear their arp-cache (arp -d *) or reboot them.
A final note:
If you use the 3600 only for connecting the subnets, you can consider using the switch for a router as a permanent solution (not bringing back the 3600). This has two distinct advantages:
- The performance is better.
- One less single point of failure
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