Story #8028
Updated by Dave Vieglais about 7 years ago
UNM now has a DMZ available which will place servers outside of the campus intrusion prevention infrastructure, and so should significantly reduce latency and increase throughput for network activity.
The goal of this story is to migrate all UNM CNs including test instances to the new network.
Network info:
<pre>
IP Range: 64.106.84.2/27 (.2 - .8 currently reserved for DataONE, .5 - .8 currently available for CNs)
Gateway: 64.106.84.1
Netmask: 255.255.255.224
Broadcast: 64.106.84.31
</pre>
To move a VM to the new network:
1. Select IP Address
2. Update /etc/network/interfaces
3. Update /etc/hosts
4. Reconfigure any services that specify IP address, including but not limited to:
a) apache
b) UFW
c) Zookeeper
d) LDAP (?)
e) Hazelcast
f) Metacat replication
g) CILogon ?
Note that the other CNs also specify specific IP addresses for connectivity, so it will be necessary to update configurations on those machines as well.
5. Select the DMZ network in VMWare configuration for the VM
6. Restart the VM
The goal of this story is to migrate all UNM CNs including test instances to the new network.
Network info:
<pre>
IP Range: 64.106.84.2/27 (.2 - .8 currently reserved for DataONE, .5 - .8 currently available for CNs)
Gateway: 64.106.84.1
Netmask: 255.255.255.224
Broadcast: 64.106.84.31
</pre>
To move a VM to the new network:
1. Select IP Address
2. Update /etc/network/interfaces
3. Update /etc/hosts
4. Reconfigure any services that specify IP address, including but not limited to:
a) apache
b) UFW
c) Zookeeper
d) LDAP (?)
e) Hazelcast
f) Metacat replication
g) CILogon ?
Note that the other CNs also specify specific IP addresses for connectivity, so it will be necessary to update configurations on those machines as well.
5. Select the DMZ network in VMWare configuration for the VM
6. Restart the VM
