Project:Sandbox

Active Servers
Before a server move can actually be scheduled for the customer, the following steps must be taken: 1. Locate an acceptable target location • observe VLAN requirement and available IP adresses • verify power capacity 2. Prepare the target location for the move • Verify the correct rails for the chassis being moved are installed • Verify there are no issues with network or power cables for the target location • Mark off the location with a strip of tape with the ticket number 3. Schedule the ticket For a physical move of the customers server 1. Verify reserved location is ready for the new server • VLAN, Power, Rack Prep 2. Log into the server and perform a graceful shutdown 3. In the Hardware Object, • Go to Properties for each network connection, make a note of the Primary IPv4 Address and remove it. click apply • Select Release IPMI by clicking the drop down to the right of mgmt0 and click ok       • Go to Detach VLAN on each of the Network connections and click Detach Vlan. • Go to Disconnect on each of the Network connections and click Disconnect. • Go to Disconnect on each of the Power connections and click Disconnect. • Change the location to the new location 5. Once the new location is set in the Hardware Object, • Use auto connect to connect network interfaces to the new switch. Always confirm that the connections are correct before accepting. • Use auto connect to connect power connections to the strip. Always confirm that the connections are correct before accepting. see: Power Strip Control • Go to “Attach VLAN” on each of the Network connections. Select the desired VLAN from the drop down box and click “Attach Vlan.” • Go to “Properties” on each of the Network connections. Click the link stating, “Assign first available IPs to this component.” • Push Provision on public and private connections • Push Production on mgmt0 and Kernel (this will also give it a new IPMI ipv4 address) • Once IPMI is up, boot the server into the OS. 6. Log in via console or KVM and Re-IP server. see:RE IP SERVER PAGE STUFF 8. Push production on private and public networks 7. Ping private/public port to ensure it can now talk on the network. 1. Verify reserved location is ready for the new server • VLAN, Power, Rack Prep 2. Log into the server and perform a graceful shutdown 3. In the Hardware Object, • Go to Disconnect on each of the Network connections and click Disconnect. • Go to Disconnect on each of the Power connections and click Disconnect. • Change the location to the new location 5. Once the new location is set in the Hardware Object, • Use auto connect to connect network interfaces to the new switch. Always confirm that the connections are correct before accepting. • Use auto connect to connect power connections to the strip. Always confirm that the connections are correct before accepting. see: Power Strip Control • Push Provision on public and private connections • Push Production on mgmt0 and Kernel • Once IPMI is up, boot the server into the OS. 8. Push production on private and public networks 7. Ping private/public port to ensure it can now talk on the network.
 * Scheduling
 * Moving Across routers
 * Moving within same router

Preparing Chassis and Scheduling
1. Locate an acceptable target chassis • The target chassis must be behind the same router or it will need to be moved. 2. Match the configuration of the target chassis with the customer's chassis • RAM, Processors, Motherboard and Drive controllers must be the same when there is no OS reload • If the customer has requested an os reload, this may be subbed to a comparable configuration. This is common with older hardware. 3. Verify all of the hardware POSTs properly 4. Verify IPMI works 5. Set the status to Reserved and add an internal note with reason and ticket link. 5. Paste a link for the target HWO internally in the swap ticket 6. Schedule the Chassis swap

Chassis Transfer Tool
What the tool does: • Transfers configuration and service offerings from one Hardware Object to another • Transfers network configuration from from one Hardware Object to another What the tool does not do: • Install an OS on the new server • Assign new IP addresses • Uptate OS network configurations with new MAC addresses • Set IPMI to its new production network configuration How to use the tool: 1. In the original Hardware Object click the Transfer Chassis link 2. at the bottom of the page Select Assign Hardware(OVERRIDE) • If no chassis has been prepared select Find New Chassis 3. Select This is an exact match and enter the SL tag of the new chassis • If hardware modification is needed, select this and a hardware change ticket will be created 4. Hit Transfer • The new chassis will be Reserved • A HWTXN will be created 5. If a drive is to be moved, do so at this time. • If performing a DRS leave the drive hanging 6. If a build ticket was needed, make the necessary changes and Confirm the build. • When you confirm the build, be sure to quote the ticket number(s) that required the chassis swap in the justification field. • Pressing submit will allow the transaction to proceed 7. Before the server boots, IPMI will need to be Kerneled • Push eth 0 to povision and pxe boot to Kernel. Leave mgmt0 on production. 8. If the transaction has stalled, RA once IPMI is responding and it will complete 9. Verify that server has booted correctly and is pinging. • Windows will automatically set the new MAC addresses while linux will require modifications to the network configurations. • If an OS reload is needed, start it now 10. Set the original Hardware Object to "Hardfail" status if it is broken, or "Inventory" status if it is not. • If it is hardfailed, add detailed internal notes as to why with a ticket link