Service Desk Knowledgebase: Scratch space: Difference between revisions
From Computer Laboratory System Administration
Jump to navigationJump to search
(→Help Desk Scratch Space: tidy up for WiKi) |
|||
| Line 1: | Line 1: | ||
=Help Desk Scratch Space= | =Help Desk Scratch Space= | ||
==Special information for re-use of PCCL0xx machines for 2015/10== | |||
There is a ticklist of steps to ensure a lab system is setup and documented correctly at http://www.wiki.cl.cam.ac.uk/rowiki/SysInfo/MachineSetup whose ToC can be used as an aide-memoire to check that everything has been done, or by going into the text itself, to see what needs to be done. | |||
Due to unfortunate expected dates for new Intel CPUs and chipsets and Asus Motherboards, a number of 2015/10 arrivals will be given ex-SW11 PWF Dell machines to tide them over until the BMC version of the Asus motherboard is available and tested. | |||
To aid with the setup of these machines, the ToC has been analysed and the expected required steps listed below. | |||
There are two classes of users: | |||
RSs should be allocated machine names 128.232.65.5[0-9]. | # 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]. | # 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]. | ||
HelpDesk needs to tell oper the DNS name (''$HOST'') to use, as well as the user and office+desk if known. | |||
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. | 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.2 DNS - pre use if needed (e.g. Linux)''': update the TXT RR for the machine to note the PCCL0xx machine actually used | |||
* '''2.3 Inventory - pre use if using DHCP (Windows) <CLCO>''': Update the Inventory record for the PC: replace the name of the host; put the old name and the RT# in comment' set the user and office | |||
* '''3.4 keytab install (Linux)''': Ensure $HOST has a keytab. If the command below fails, create a new keytab (contact gt19 is necessary). On $HOST run: | |||
* 2.2 DNS - pre use if needed (e.g. Linux) | cl-onserver --keytab | ||
* '''4.1 User Admin - when running if needed (Linux)''': If oper were not told the 'assigned user', on $HOST run: | |||
* 2.3 Inventory - pre use if using DHCP (Windows) <CLCO> | 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 and update RT ticket to include machine name ($HOST) in ticket Subject: | |||
* '''4.3 Tell the user - when done''': Send final 'std email' to user. Resolve RT ticket. | |||
* '''4.6 ssh_known_hosts - at leisure if needed (Linux)''': when the machine is running, on a '''different''' machine run | |||
* 4.1 User Admin - when running if needed (Linux) | |||
If oper were not told the 'assigned user' | |||
* 4.2 Arrivals - when done | |||
* 4.3 Tell the user - when done | |||
* 4.6 ssh_known_hosts - at leisure if needed (Linux) | |||
/global/src/usr.bin/ssh/fetch-host-key scan $HOST | /global/src/usr.bin/ssh/fetch-host-key scan $HOST | ||
* '''4.8 ownfiles - at leisure if needed (Linux)''': to ensure that '''ownfiles''' data is collected, run | |||
* 4.8 ownfiles - at leisure if needed (Linux) | (umask 2; touch /usr/groups/linux/ownfiles/CKSUM/$HOST) | ||
* '''4.9 WoL - at leisure''': to ensure that WoL is available, run: | |||
* 4.9 WoL - at leisure | /usr/groups/netmaint/boot_wol_file-add.pl $HOST | ||
==Procedure To Be Tidied Up== | ==Procedure To Be Tidied Up== | ||
Revision as of 15:24, 10 September 2015
Help Desk Scratch Space
Special information for re-use of PCCL0xx machines for 2015/10
There is a ticklist of steps to ensure a lab system is setup and documented correctly at http://www.wiki.cl.cam.ac.uk/rowiki/SysInfo/MachineSetup whose ToC can be used as an aide-memoire to check that everything has been done, or by going into the text itself, to see what needs to be done.
Due to unfortunate expected dates for new Intel CPUs and chipsets and Asus Motherboards, a number of 2015/10 arrivals will be given ex-SW11 PWF Dell machines to tide them over until the BMC version of the Asus motherboard is available and tested.
To aid with the setup of these machines, the ToC has been analysed and the expected required steps listed below.
There are two classes of users:
- 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].
HelpDesk needs to tell oper the DNS name ($HOST) to use, as well as the user and office+desk if known. 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.2 DNS - pre use if needed (e.g. Linux): update the TXT RR for the machine to note the PCCL0xx machine actually used
- 2.3 Inventory - pre use if using DHCP (Windows) <CLCO>: Update the Inventory record for the PC: replace the name of the host; put the old name and the RT# in comment' set the user and office
- 3.4 keytab install (Linux): Ensure $HOST has a keytab. If the command below fails, create a new keytab (contact gt19 is necessary). On $HOST run:
cl-onserver --keytab
- 4.1 User Admin - when running if needed (Linux): If oper were not told the 'assigned user', on $HOST run:
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 and update RT ticket to include machine name ($HOST) in ticket Subject:
- 4.3 Tell the user - when done: Send final 'std email' to user. Resolve RT ticket.
- 4.6 ssh_known_hosts - at leisure if needed (Linux): when the machine is running, on a different machine run
/global/src/usr.bin/ssh/fetch-host-key scan $HOST
- 4.8 ownfiles - at leisure if needed (Linux): to ensure that ownfiles data is collected, run
(umask 2; touch /usr/groups/linux/ownfiles/CKSUM/$HOST)
- 4.9 WoL - at leisure: to ensure that WoL is available, run:
/usr/groups/netmaint/boot_wol_file-add.pl $HOST
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
