GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Routing Help Please
Operating System - HP-UX
1844311
Members
3762
Online
110230
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
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
10-09-2003 03:05 AM
10-09-2003 03:05 AM
Hi,
We are going to change IP scope from 207.186.218.1/24 to 172.16.16.1/28 in the whole companay. On one server we cannot change IP address for its too old. We plan to put a router in front it and route a network segment of 207.186.218.1 to the router. Thus we don't have to change its IP and all clients with the new IP addresses of 172.16.16.1/28 still can use it.
I don't know how to implement it. I can make it that far as to have clients to connect still use 207.186.218.1/24 IP and connect to this router.
What is the way to have it work, i.e.
1) that server IP not change
2) client with changed IP can connect
I am debating with manager, and are beat with this.
Very appreciated if giving any help!!
Steven
We are going to change IP scope from 207.186.218.1/24 to 172.16.16.1/28 in the whole companay. On one server we cannot change IP address for its too old. We plan to put a router in front it and route a network segment of 207.186.218.1 to the router. Thus we don't have to change its IP and all clients with the new IP addresses of 172.16.16.1/28 still can use it.
I don't know how to implement it. I can make it that far as to have clients to connect still use 207.186.218.1/24 IP and connect to this router.
What is the way to have it work, i.e.
1) that server IP not change
2) client with changed IP can connect
I am debating with manager, and are beat with this.
Very appreciated if giving any help!!
Steven
Steve
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2003 04:59 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-09-2003 09:03 AM
10-09-2003 09:03 AM
Re: Routing Help Please
If you have a Cisco router then you just use a secondary address on it to handle the odd ball. The router will happily switch between the two addresses on the same interface and you won't have to waste an interface for the purpose. You may want to add
ip route-cache same-interface
to the config under the interface. That will make it faster at switching between the two.
Let's say your old box has a default gateway of 207.186.218.254 and you don't want to change anything on the old box. You assign E0/1 as the interface for the 172.16.16 network and you want it to be 172.16.16.1 (which will be the new default gateway for the new subnet). You plug your switch into this interface and all of your devices including the odd ball are plugged into the switch.
Then you do
conf t
ip subnet-zero
ip classless
int e0/1
ip add 172.16.16.1 255.255.255.240
ip add 207.186.218.254 255.255.255.0 second
ip route-cache same-interface
end
wr me
Now the router will switch between the two subnets without a problem and as an advantage you do not have to recable the devices. They will still be able to talk using their old IP address until you get around to changing them. (Ip classless and IP subnet-zero are on by default in 12.0 and higher code so you don't need them if you are on a new router.)
Of course, you can use a router with 2 interfaces and put each subnet on a separate interface but then you have to do some recabling to get it to work.
Ron
ip route-cache same-interface
to the config under the interface. That will make it faster at switching between the two.
Let's say your old box has a default gateway of 207.186.218.254 and you don't want to change anything on the old box. You assign E0/1 as the interface for the 172.16.16 network and you want it to be 172.16.16.1 (which will be the new default gateway for the new subnet). You plug your switch into this interface and all of your devices including the odd ball are plugged into the switch.
Then you do
conf t
ip subnet-zero
ip classless
int e0/1
ip add 172.16.16.1 255.255.255.240
ip add 207.186.218.254 255.255.255.0 second
ip route-cache same-interface
end
wr me
Now the router will switch between the two subnets without a problem and as an advantage you do not have to recable the devices. They will still be able to talk using their old IP address until you get around to changing them. (Ip classless and IP subnet-zero are on by default in 12.0 and higher code so you don't need them if you are on a new router.)
Of course, you can use a router with 2 interfaces and put each subnet on a separate interface but then you have to do some recabling to get it to work.
Ron
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
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP