Service Desk Knowledgebase: Scratch space

From Computer Laboratory System Administration
Jump to navigationJump to search

Help Desk Scratch Space

gt19 has decided to treat them all the same, so just the one case. RSs should be allocated machine names 128.232.65.5[0-9]. Other 'misc pool' temporary use (e.g. short term visitors; people buying kit when they have settled in) should be allocated machine names 128.232.65.6[0-9].

Here is the ticklist from http://www.wiki.cl.cam.ac.uk/rowiki/SysInfo/MachineSetup Items marked '-' do not apply, those marked 'D' have been done. I believe HelpDesk needs to do those marked '*' and oper those marked '+'. HelpDesk needs to tell oper the DNS name to use as well as the user and office+desk When done, oper will tell Helpdesk the Inv# and 'old' name of the system used, so that 2.2 and 2.3 can be done.


2 Pre install D 2.1 Gather info - first thing

  • 2.2 DNS - pre use if needed (e.g. Linux)
names and addresses assigned, but once 3.3 is done, update TXT RR
  • 2.3 Inventory - pre use if using DHCP (Windows) <CLCO>
once 3.3 is done, put RT# in comment, set user and office

- 2.4 DHCP - pre use if needed (Windows) LAN - any time (Linux on IPv6 VLAN) - 2.5 LDAP - pre use if needed (Linux - rarely) - 2.6 local user - before user login if needed (Linux in DMZ) - 2.7 AD - pre use generate host keytab if needed (Linux)

3 Machine install + 3.1 Network setup <oper> 

Need to setup and document UTP connection

- 3.2 BMC BIOS setup - if present <oper> + 3.3 OS install <oper> 

unplug HDD SATA cable and put SSD loose in lower 3.5" HDD slot
Install OS
  • 3.4 keytab install (Linux)
On $HOST: cl-onserver --keytab
If there is no keytab to install, create one and retry

4 Tidies

  • 4.1 User Admin - when running if needed (Linux)
If oper were not told the 'assigned user' for 3.3,
on $HOST: cl-asuser cl-hostid-fix --user $CRSID -a
  • 4.2 Arrivals - when done
fix https://dbwebserver.ad.cl.cam.ac.uk/SCG/Equipment/PhDArrivals.aspx
Update RT ticket to include machine name in ticket Subject:
  • 4.3 Tell the user - when done
Send user message
Resolve RT

- 4.4 Rack - at leisure if needed - 4.5 hosts.props - at leisure

  • 4.6 ssh_known_hosts - at leisure if needed (Linux)
when the machine is running, on *another* machine run
/global/src/usr.bin/ssh/fetch-host-key scan $HOST

- 4.7 BMC ACL - when up if present

  • 4.8 ownfiles - at leisure if needed (Linux)
run: (umask 2; touch /usr/groups/linux/ownfiles/CKSUM/$HOST)
  • 4.9 WoL - at leisure
run: /usr/groups/netmaint/boot_wol_file-add.pl $HOST

+ 4.10 Wiring database - once physically installed <oper> 

document what was done in 3.1 if not already done

- 4.11 Snapshot - once system in service (VM) - 4.12 UPS - once physically installed - 4.13 INSTALLED - once system is FULLY installed (linux)


Procedure To Be Tidied Up

So from https://rt.cl.cam.ac.uk/Ticket/Display.html?id=96922 this seems to boil down to the following for the Help Desk for the https://rt.cl.cam.ac.uk/Ticket/Display.html?id=96580 test case.

NOTE: There is ONLY now one case...


Machine install

keytab install (Linux)

On $HOST: cl-onserver --keytab
If there is no keytab to install, create one and retry

Tidies

  • 4.1 User Admin - when running if needed (Linux)
If oper were not told the 'assigned user' for 3.3,
on $HOST: cl-asuser cl-hostid-fix --user $CRSID -a
  • 4.2 Arrivals - when done
fix https://dbwebserver.ad.cl.cam.ac.uk/SCG/Equipment/PhDArrivals.aspx
Update RT ticket to include machine name in ticket Subject:
  • 4.3 Tell the user - when done
Send user message
Resolve RT
  • 4.6 ssh_known_hosts - at leisure if needed (Linux)
when the machine is running, on *another* machine run
/global/src/usr.bin/ssh/fetch-host-key scan $HOST
  • 4.8 ownfiles - at leisure if needed (Linux)
run: (umask 2; touch /usr/groups/linux/ownfiles/CKSUM/$HOST)
  • 4.9 WoL - at leisure
run: /usr/groups/netmaint/boot_wol_file-add.pl $HOST


HelpDesk needs to tell oper the DNS name to use as well as the user and office+desk When done, oper will tell Helpdesk the Inv# and 'old' name of the system used, so that 2.2 and 2.3 can be done.

Pre install

  • 2.2 DNS - pre use if needed (e.g. Linux)
names and addresses assigned, but once 3.3 is done, update TXT RR
  • 2.3 Inventory - pre use if using DHCP (Windows) <CLCO>
once 3.3 is done, put RT# in comment, set user and office
Retrieved from "https://wiki.cam.ac.uk/wiki/cl-sys-admin/index.php?title=Service_Desk_Knowledgebase:_Scratch_space&oldid=3023"