Shutting Down Service

From JCWiki
Revision as of 18:13, 27 December 2012 by 70.230.212.110 (talk)
Jump to navigation Jump to search

Dedicated Server

When a dedicated customer shuts down service, we use the cancel date in management as the reminder date to shut the server off. When the "SHUTDOWN TODAY" email is received, the server should be powered down by NOC staff on that day (unless prior arrangements have been made to keep the server up or down for another reason). Also, billing should be stopped on that date to avoid future billing. You may remove the next bill date, or delete the sub to stop billing.

The server should remain in cancelled but not stopped status until the server is physically pulled from the DC. The reason for this is the cancelled status is a reminder that we need to pull the hardware out of the DC.

After the hardware is pulled the following steps should be taken:

  • stop the system in management (this will mark the customer as cancelled if this was the last active server)
  • remove the description label for the switch port:

Assuming they're on port 21 on switch p23:

en
conf t
interface fa0/21
no description
exit
write memory

If they also had an RMM/DRAC repeat the process for the other port. Running a show run should show you which ports the customer is labeled for.

  • destroy the nfs data mount and data, if applicable:
umount /data/customers/col00xxx
rmdir /data/customers/col00xxx
rm /data/customers/col00xxx-file
vi /etc/exports (remove entry)
vi  /etc/nfs_backup_mounts.sh (remove entries - 2)

If the umount fails, restart the nfsd:

/etc/init.d/nfs-kernel-server restart
  • remove DNS entries:
listdomains col00xxx
vi /etc/namedb/named.conf (remove all domains for customer)