Colo Server Setup - Revision history

208.121.64.2: /* Post install */

2012-12-20T23:27:12Z

Post install

← Older revision		Revision as of 16:27, 20 December 2012
Line 65:		Line 65:
	= Post install =		= Post install =

	* update the system record in mgmt to reflect the correct asset tag, ATS port, cabinet and newly-assigned IP. You can keep the notes or not, but at least keep the disk partition and OS note. Leave the password field blank. If this asset isn't in the database, you may be prompted to add it first.		* update the system record in mgmt to reflect the correct asset tag, ATS port (if at i2b), cabinet and newly-assigned IP. You can keep the notes or not, but at least keep the disk partition and OS note. Leave the password field blank. If this asset isn't in the database, you may be prompted to add it first.
	* update [[Cabinetmap]] with location of server, also label switch port and ATS port		* update [[Cabinetmap]] with location of server, also label switch port and ATS port
	* reboot the server and in the process of posting, power down, then power up the port using ATS controls to confirm the server is assigned to the right ATS port.		* reboot the server and in the process of posting, power down, then power up the port using ATS controls to confirm the server is assigned to the right ATS port.

76.88.21.129: /* Post install */

2012-12-10T03:24:56Z

Post install

← Older revision		Revision as of 20:24, 9 December 2012
Line 65:		Line 65:
	= Post install =		= Post install =

	* update the system record in mgmt to reflect the correct asset tag, ATS port, cabinet and newly-assigned IP. You can keep the notes or not, but at least keep the disk partition and OS note. Leave the password field blank.		* update the system record in mgmt to reflect the correct asset tag, ATS port, cabinet and newly-assigned IP. You can keep the notes or not, but at least keep the disk partition and OS note. Leave the password field blank. If this asset isn't in the database, you may be prompted to add it first.
	* update [[Cabinetmap]] with location of server, also label switch port and ATS port		* update [[Cabinetmap]] with location of server, also label switch port and ATS port
	* reboot the server and in the process of posting, power down, then power up the port using ATS controls to confirm the server is assigned to the right ATS port.		* reboot the server and in the process of posting, power down, then power up the port using ATS controls to confirm the server is assigned to the right ATS port.

76.88.21.129: /* Post install */

2012-12-10T03:24:31Z

Post install

← Older revision		Revision as of 20:24, 9 December 2012
Line 65:		Line 65:
	= Post install =		= Post install =

	* update the system record in mgmt to reflect the correct asset tag, ATS port, cabinet and newly-assigned IP. You can keep the notes or not, but at least keep the disk partition and OS note.		* update the system record in mgmt to reflect the correct asset tag, ATS port, cabinet and newly-assigned IP. You can keep the notes or not, but at least keep the disk partition and OS note. Leave the password field blank.
	* update [[Cabinetmap]] with location of server, also label switch port and ATS port		* update [[Cabinetmap]] with location of server, also label switch port and ATS port
	* reboot the server and in the process of posting, power down, then power up the port using ATS controls to confirm the server is assigned to the right ATS port.		* reboot the server and in the process of posting, power down, then power up the port using ATS controls to confirm the server is assigned to the right ATS port.

76.88.21.129: /* Post install */

2012-12-10T03:24:01Z

Post install

← Older revision		Revision as of 20:24, 9 December 2012
Line 65:		Line 65:
	= Post install =		= Post install =

	* update the system record in mgmt to reflect the ATS port and ~~cabinet~~		* update the system record in mgmt to reflect the correct asset tag, ATS port, cabinet and newly-assigned IP. You can keep the notes or not, but at least keep the disk partition and OS note.
	* update [[Cabinetmap]] with location of server, also label switch port and ATS port		* update [[Cabinetmap]] with location of server, also label switch port and ATS port
	* reboot the server and in the process of posting, power down, then power up the port using ATS controls to confirm the server is assigned to the right ATS port.		* reboot the server and in the process of posting, power down, then power up the port using ATS controls to confirm the server is assigned to the right ATS port.

76.88.21.129: /* Post install */

2012-12-10T03:22:08Z

Post install

← Older revision		Revision as of 20:22, 9 December 2012
Line 73:		Line 73:
	* add server colo (and hostname if multiple servers) to description field on cisco port:		* add server colo (and hostname if multiple servers) to description field on cisco port:
	Go to the serial console for the switch they're connected to (refer to cabinet map as to which switch is in that cabinet):		Go to the serial console for the switch they're connected to (refer to cabinet map as to which switch is in that cabinet):

			<pre>
			switch-p26>en
			Password:
			switch-p26#conf t
			Enter configuration commands, one per line. End with CNTL/Z.
			switch-p26(config)#int fa0/11
			switch-p26(config-if)#des col02171
			switch-p26(config-if)#en
			switch-p26#wr me
			</pre>


	* put a note to add a colo label to the server (or ask DC staff to do it- front and back). Also label hostname if cust has mult servers at DC		* put a note to add a colo label to the server (or ask DC staff to do it- front and back). Also label hostname if cust has mult servers at DC

76.88.21.129: /* Install the OS */

2012-12-10T01:18:39Z

Install the OS

← Older revision		Revision as of 18:18, 9 December 2012
Line 58:		Line 58:

	You may need to create <tt>/usr/local/sbin</tt> on some OS's		You may need to create <tt>/usr/local/sbin</tt> on some OS's

			Don't forget to add to /etc/resolv.conf:
			nameserver 69.55.225.225
			nameserver 69.55.230.3

	= Post install =		= Post install =

76.88.21.129: /* Install the OS */

2012-12-10T01:12:57Z

Install the OS

← Older revision		Revision as of 18:12, 9 December 2012
Line 24:		Line 24:
	When requested to setup a new user, choose 'user'.		When requested to setup a new user, choose 'user'.
	All passwords for user/root are newrootNNNN where the NNNN is the sig. digits from the CID. So if the new CID is col001234 the password is: newroot1234		All passwords for user/root are newrootNNNN where the NNNN is the sig. digits from the CID. So if the new CID is col001234 the password is: newroot1234

			When setting up Ubu, make sure to set the first (or boot partition) bootable (set bootable flag).

	If the customer has not requested that you add more than 1 IP initially (with a valid reason) then just add the 1 IP (or the number they requested if applicable.)		If the customer has not requested that you add more than 1 IP initially (with a valid reason) then just add the 1 IP (or the number they requested if applicable.)

76.88.21.129: /* Install the OS */

2012-12-10T01:11:10Z

Install the OS

← Older revision		Revision as of 18:11, 9 December 2012
Line 21:		Line 21:

	It'll be a crapshoot which ethernet device (if there are multiple) is the active one. You basically have to guess and assign an IP to one and immediately after configuring it go ping it. If it's pinging, you guessed right. If not, you can either go back and give the IP to the other nic (this may not work since the other nic may still have the same IP) or you can ask the DC to swap the cat5 cable to the other port.		It'll be a crapshoot which ethernet device (if there are multiple) is the active one. You basically have to guess and assign an IP to one and immediately after configuring it go ping it. If it's pinging, you guessed right. If not, you can either go back and give the IP to the other nic (this may not work since the other nic may still have the same IP) or you can ask the DC to swap the cat5 cable to the other port.

			When requested to setup a new user, choose 'user'.
			All passwords for user/root are newrootNNNN where the NNNN is the sig. digits from the CID. So if the new CID is col001234 the password is: newroot1234

	If the customer has not requested that you add more than 1 IP initially (with a valid reason) then just add the 1 IP (or the number they requested if applicable.)		If the customer has not requested that you add more than 1 IP initially (with a valid reason) then just add the 1 IP (or the number they requested if applicable.)

76.88.21.129: /* Install the OS */

2012-12-10T01:03:11Z

Install the OS

← Older revision		Revision as of 18:03, 9 December 2012
Line 21:		Line 21:

	It'll be a crapshoot which ethernet device (if there are multiple) is the active one. You basically have to guess and assign an IP to one and immediately after configuring it go ping it. If it's pinging, you guessed right. If not, you can either go back and give the IP to the other nic (this may not work since the other nic may still have the same IP) or you can ask the DC to swap the cat5 cable to the other port.		It'll be a crapshoot which ethernet device (if there are multiple) is the active one. You basically have to guess and assign an IP to one and immediately after configuring it go ping it. If it's pinging, you guessed right. If not, you can either go back and give the IP to the other nic (this may not work since the other nic may still have the same IP) or you can ask the DC to swap the cat5 cable to the other port.

			If the customer has not requested that you add more than 1 IP initially (with a valid reason) then just add the 1 IP (or the number they requested if applicable.)

	FreeBSD systems will require you to complete the OS load over ftp since the OS won't recognize the IPKVM's ISO as a CD drive (this despite the fact that it clearly booted to it initially). This is why we use "netboot" ISOs.		FreeBSD systems will require you to complete the OS load over ftp since the OS won't recognize the IPKVM's ISO as a CD drive (this despite the fact that it clearly booted to it initially). This is why we use "netboot" ISOs.

76.88.21.129: /* Post install */

2012-12-10T00:53:50Z

Post install

← Older revision		Revision as of 17:53, 9 December 2012
Line 55:		Line 55:

	* update the system record in mgmt to reflect the ATS port and cabinet		* update the system record in mgmt to reflect the ATS port and cabinet
	* update [[Cabinetmap]]		* update [[Cabinetmap]] with location of server, also label switch port and ATS port
	* reboot the server and in the process of posting, power down, then power up the port using ATS controls to confirm the server is assigned to the right ATS port.		* reboot the server and in the process of posting, power down, then power up the port using ATS controls to confirm the server is assigned to the right ATS port.
	* make sure billing is all set		* make sure billing is all set
	* send welcome email (use "colo welcome" from big pastes page).		* send welcome email (use "colo welcome" from big pastes page).
	* mark KVM as unused in KVM notes screen (A0P4)		* mark KVM as unused in KVM notes screen (A0P4)
	* add server colo (and hostname if multiple servers) to description field on cisco port		* add server colo (and hostname if multiple servers) to description field on cisco port:
			Go to the serial console for the switch they're connected to (refer to cabinet map as to which switch is in that cabinet):


	* put a note to add a colo label to the server (or ask DC staff to do it- front and back). Also label hostname if cust has mult servers at DC		* put a note to add a colo label to the server (or ask DC staff to do it- front and back). Also label hostname if cust has mult servers at DC