There reported error while configuring the management IP and replication IP
Publication Date: 2012-11-06Views: 59Downloads: 0
At a certain site, there reported error while configuring the T series storage management and the iscsi IP according to the requirement. We found the management IP is different from the replication IP.
The IP segment provided by the user can’t satisfy the requirement, and there isn’t any redundant address, through discussing, we actualize it via adding the subnet. Take the address segment “18.104.22.168” as an example (just for illustrating):
The IP you want to divide is: 188.188.165.000, this is a B type IP address
The number of subnet you want to divide is: 10, the subnet mask is: 255.255.240.000
Each network code of the subnet is equal to the last number of the TO’s front IP reducing one
Each broadcast address of the subnet is equal to the last number of the TO’s back IP reducing one.
1> 22.214.171.124 TO 126.96.36.199
2> 188.8.131.52 TO 184.108.40.206
3> 220.127.116.11 TO 18.104.22.168
4> 22.214.171.124 TO 126.96.36.199
5> 188.8.131.52 TO 184.108.40.206
6> 220.127.116.11 TO 18.104.22.168
7> 22.214.171.124 TO 126.96.36.199
8> 188.8.131.52 TO 184.108.40.206
9> 220.127.116.11 TO 18.104.22.168
10> 22.214.171.124 TO 126.96.36.199
11> 188.8.131.52 TO 184.108.40.206
12> 220.127.116.11 TO 18.104.22.168
13> 22.214.171.124 TO 126.96.36.199
14> 188.8.131.52 TO 184.108.40.206
15> 220.127.116.11 TO 18.104.22.168
16> 22.214.171.124 TO 126.96.36.199
After this dividing, the management IP and replication IP are independent from each other.
Our company’s storage array management IP and replication IP are in the different network segments, they are independent. Whereas, the user’s IP of this site is limited and they want to manage them in the same network segment.
For some users, their IP schemes are un-suitable; they can take this method to isolate the management IP from the service IP.