Equalogic Backup Drive: Difference between revisions

From Research Computing Center Wiki
Jump to navigation Jump to search
No edit summary
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
====Is this project complete? GD /7/31====
=== Objective ===
=== Objective ===
Leverage the Burke Lab iSCSI device to add to and assist with the migration of the GACRC SAN from 10.0.0.0/8 IP addresses to 192.168.0.0/16 IP addresses. This needs to happen because the SAN VLAN is unable to be monitored. A monitoring node cannot have interfaces on separate networks with the same IP addresses and the 10.0.0.0/8 network is already used on the internodal network (VLAN 40).
Leverage the Burke Lab iSCSI device to add to and assist with the migration of the GACRC SAN from 10.0.0.0/8 IP addresses to 192.168.0.0/16 IP addresses. This needs to happen because the SAN VLAN is unable to be monitored. A monitoring node cannot have interfaces on separate networks with the same IP addresses and the 10.0.0.0/8 network is already used on the internodal network (VLAN 40).


== Completed ==
=== Completed ===
* Remove Franklin configuration
* Remove Franklin configuration
* Configure ports in the Thumper Rack for VLAN 31
* Configure ports in the Thumper Rack for VLAN 31
Line 17: Line 20:
* Migrate non-essential VMs to Burke Storage while monitoring latency
* Migrate non-essential VMs to Burke Storage while monitoring latency
* Provision additional LUNs for high-volume service VMs
* Provision additional LUNs for high-volume service VMs
== Need to be Completed ==
* Migrate zhead/zcluster active VMs
* Migrate zhead/zcluster active VMs
* Remove LUNs from Hosts and reboot them, one host at a time
* Remove LUNs from Hosts and reboot them, one host at a time
Line 24: Line 25:
* Reattach Equalogics to Hosts and reboot them, one host at a time
* Reattach Equalogics to Hosts and reboot them, one host at a time
* Migrate some or all VMs back
* Migrate some or all VMs back
=== Need to be Completed ===
* Decide based on LUN latency how to proceed with storage provisioning
* Decide based on LUN latency how to proceed with storage provisioning


== Notes ==
=== Notes ===
* Use Burke iSCSI as Virtual Machine backup?
* Use Burke iSCSI as Virtual Machine backup?
* Use Burke iSCSI as exports for Gluster?
* Use Burke iSCSI as exports for Gluster?
* Use Both Burke iSCSI And Equalogics for VMWare
* Use Both Burke iSCSI And Equalogics for VMWare

Latest revision as of 08:28, 31 July 2013

Is this project complete? GD /7/31

Objective

Leverage the Burke Lab iSCSI device to add to and assist with the migration of the GACRC SAN from 10.0.0.0/8 IP addresses to 192.168.0.0/16 IP addresses. This needs to happen because the SAN VLAN is unable to be monitored. A monitoring node cannot have interfaces on separate networks with the same IP addresses and the 10.0.0.0/8 network is already used on the internodal network (VLAN 40).

Completed

  • Remove Franklin configuration
  • Configure ports in the Thumper Rack for VLAN 31
  • Configure IP addresses
  • Add VMKernel interfaces with 192.168/16 IP addresses to ESX hosts
  • Create LUNs
  • Attach LUNs to VMWare Hosts
  • Begin Migrating VMs
  • Monitor LUN Latency and adjust
  • Gave Burke iSCSI unit definition in Rocks
  • Name: gacrc-iscsi-2
  • MGMT IP address: 172.16.33.114
  • iSCSI Access IP addresses: 192.168.0.1, 192.168.0.2, 192.168.0.3, 192.168.0.4 netmask 255.255.0.0
  • Migrate non-essential VMs to Burke Storage while monitoring latency
  • Provision additional LUNs for high-volume service VMs
  • Migrate zhead/zcluster active VMs
  • Remove LUNs from Hosts and reboot them, one host at a time
  • Change Equalogics IP addresses
  • Reattach Equalogics to Hosts and reboot them, one host at a time
  • Migrate some or all VMs back

Need to be Completed

  • Decide based on LUN latency how to proceed with storage provisioning

Notes

  • Use Burke iSCSI as Virtual Machine backup?
  • Use Burke iSCSI as exports for Gluster?
  • Use Both Burke iSCSI And Equalogics for VMWare