本文发表在 rolia.net 枫下论坛As I do not know your network well, I assume that your router has two FastEthernet F0 and F1
F0: connect to site A with the IP address 10.12.255.254 255.255.0.0 and this IP address is all of the site A devices’ default gateway;
F1: connect to site B with the IP address 10.50.255.254 255.255.0.0 and this IP address is all of the site B devices’ default gateway;
If I am correct, I have to say that the design is totally bad, honestly.
Anyway, you can achieve it by two ways:
The first way:
1, change your F0 IP address from 10.12.255.254 255.255.0.0 to:
Ip address 10.12.1.254 255.255.255.0
Ip address 10.12.2.254 255.255.255.0 secondary
Ip address 10.12.3.254 255.255.255.0 secondary
Ip address 10.12.4.254 255.255.255.0 secondary
Ip address 10.12.6.254 255.255.255.0 secondary
2, keep your site A devices’ IP addresses, but change the subnet mask from 255.255.0.0 to 255.255.255.0.
Then change their default gateway from 10.12.255.254 to 10.12.X.254 ( X=1,2,3,4,6, depends on the devices’ IP address or subnet)
3, keep the F1 IP address and add a secondary IP address:
IP address 10.12.5.254 255.255.255.0 secondary
4, Move your servers’ to site B, keep the servers’ IP address but change the subnet mask to 255.255.255.0 and the default gateway 10.12.5.254.
This way is so unprofessional and so bad too, but you can get the achievement.
The potential issues are:
1, it will cause the F0 performance problem if the traffic between subnets is heavy, as the traffic is not “switched” as before, but “routed” via F0, but it is not the criminal;
2, if your router is running some dynamic routing protocol and all of the IP blocks take part in it, it will cause some IP route issue as some dynamic routing protocols do not support secondary IP address or do not support well.
The second way:
I assume your router and switches support trunk encapsulate( 802.1q or ISL)
1, encapsulate F0 to trunk and use the sub-interfaces:
F0.1: vlan 10 IP:10.12.1.254 255.255.255.0
F0.2: vlan 20 IP:10.12.2.254 255.255.255.0
F0.3: vlan 30 IP:10.12.3.254 255.255.255.0
F0.4: vlan 40 IP:10.12.4.254 255.255.255.0
F0.6: vlan 60 IP:10.12.6.254 255.255.255.0
2, configure your switch, the interface connecting to F0 need to encapsulate trunk( the same protocol as F0)
Create VLAN10,20,30,40,60 and allocate the other interfaces to the proper vlan as access mode;
If you have more than one switches, you need configure the same way.
Note: interfaces between switches need to be trunk.
3, keep your site A devices’ IP addresses, but change the subnet mask from 255.255.0.0 to 255.255.255.0.
Then change their default gateway from 10.12.255.254 to 10.12.X.254 ( X=1,2,3,4,6, depends on the devices’ IP address or vlan)
4, configure F1 and site B’s devices, include switch(es) as the same way. Make the 10.12.5.0/24 as a subnet in F1.
5,move your servers to site B and connect to proper interfaces of the switches.
This way has the same potential issue as the first way’s #1.
I do not think it carefully, I hope it is helpful.更多精彩文章及讨论,请光临枫下论坛 rolia.net
F0: connect to site A with the IP address 10.12.255.254 255.255.0.0 and this IP address is all of the site A devices’ default gateway;
F1: connect to site B with the IP address 10.50.255.254 255.255.0.0 and this IP address is all of the site B devices’ default gateway;
If I am correct, I have to say that the design is totally bad, honestly.
Anyway, you can achieve it by two ways:
The first way:
1, change your F0 IP address from 10.12.255.254 255.255.0.0 to:
Ip address 10.12.1.254 255.255.255.0
Ip address 10.12.2.254 255.255.255.0 secondary
Ip address 10.12.3.254 255.255.255.0 secondary
Ip address 10.12.4.254 255.255.255.0 secondary
Ip address 10.12.6.254 255.255.255.0 secondary
2, keep your site A devices’ IP addresses, but change the subnet mask from 255.255.0.0 to 255.255.255.0.
Then change their default gateway from 10.12.255.254 to 10.12.X.254 ( X=1,2,3,4,6, depends on the devices’ IP address or subnet)
3, keep the F1 IP address and add a secondary IP address:
IP address 10.12.5.254 255.255.255.0 secondary
4, Move your servers’ to site B, keep the servers’ IP address but change the subnet mask to 255.255.255.0 and the default gateway 10.12.5.254.
This way is so unprofessional and so bad too, but you can get the achievement.
The potential issues are:
1, it will cause the F0 performance problem if the traffic between subnets is heavy, as the traffic is not “switched” as before, but “routed” via F0, but it is not the criminal;
2, if your router is running some dynamic routing protocol and all of the IP blocks take part in it, it will cause some IP route issue as some dynamic routing protocols do not support secondary IP address or do not support well.
The second way:
I assume your router and switches support trunk encapsulate( 802.1q or ISL)
1, encapsulate F0 to trunk and use the sub-interfaces:
F0.1: vlan 10 IP:10.12.1.254 255.255.255.0
F0.2: vlan 20 IP:10.12.2.254 255.255.255.0
F0.3: vlan 30 IP:10.12.3.254 255.255.255.0
F0.4: vlan 40 IP:10.12.4.254 255.255.255.0
F0.6: vlan 60 IP:10.12.6.254 255.255.255.0
2, configure your switch, the interface connecting to F0 need to encapsulate trunk( the same protocol as F0)
Create VLAN10,20,30,40,60 and allocate the other interfaces to the proper vlan as access mode;
If you have more than one switches, you need configure the same way.
Note: interfaces between switches need to be trunk.
3, keep your site A devices’ IP addresses, but change the subnet mask from 255.255.0.0 to 255.255.255.0.
Then change their default gateway from 10.12.255.254 to 10.12.X.254 ( X=1,2,3,4,6, depends on the devices’ IP address or vlan)
4, configure F1 and site B’s devices, include switch(es) as the same way. Make the 10.12.5.0/24 as a subnet in F1.
5,move your servers to site B and connect to proper interfaces of the switches.
This way has the same potential issue as the first way’s #1.
I do not think it carefully, I hope it is helpful.更多精彩文章及讨论,请光临枫下论坛 rolia.net