Service Desk Knowledgebase: Required Updates: Difference between revisions

From Computer Laboratory System Administration
Jump to navigationJump to search
No edit summary
Line 32: Line 32:
https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94951 has the policy on requests for SW for the pool of 41 ACS machines.
https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94951 has the policy on requests for SW for the pool of 41 ACS machines.
Basically individual users can load private copies of any 'special' things they need in their $HOME (and maybe setting some environment variables to find it); anything of use to the bulk of the people doing the course should be requested by the course giver.
Basically individual users can load private copies of any 'special' things they need in their $HOME (and maybe setting some environment variables to find it); anything of use to the bulk of the people doing the course should be requested by the course giver.
https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94942 has info on how an 'assigned user' may be able to wake a machine more reliably than using WoL


https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94954 has info on sshd brute force defences, possible reduction, and pointer to 'bedtime reading' and 'dos and donts' (he created an account without contacting us)
https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94954 has info on sshd brute force defences, possible reduction, and pointer to 'bedtime reading' and 'dos and donts' (he created an account without contacting us)


https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94965 et al are about old ssh clients connecting to the Lab ssh servers and being told "no matching mac found: client hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 server hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-ripemd160-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256". Correct fix is to upgrade their ssh clients (which may require upgrade of OS). Til then, connect in via slogin-oldssh.cl.cam.ac.uk
https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94965 et al are about old ssh clients connecting to the Lab ssh servers and being told "no matching mac found: client hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 server hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-ripemd160-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256". Correct fix is to upgrade their ssh clients (which may require upgrade of OS). Til then, connect in via slogin-oldssh.cl.cam.ac.uk

Revision as of 16:52, 20 March 2015

This is the CL Wiki Required Updates page of Service Desk Knowledgebase. The overall objective is to provide a catalogue of services which the CL provides to its users, and to provide focused information about them. The target audience is however the Service Desk team in order to help them handle incidents, problems and requests about CL services.

Return to the Service Desk Knowledgebase SERVICE PORTFOLIO

This list is only to act as a reminder for administrative processes.


Need checking:


Re-writes to be done by vrw10

Please put in here hints, tips and procedures (or links to them) that you would like re-written into the Service Desk Knowledgebase contents pages "in my words".

https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94616 suggest that (cl-)amttool, amtterm, wsman and ipmitool need to be added to the tools. See the section on RemoteManagement on http://www.wiki.cl.cam.ac.uk/clwiki/SysInfo such as http://www.wiki.cl.cam.ac.uk/clwiki/SysInfo/IAMT and http://www.wiki.cl.cam.ac.uk/clwiki/SysInfo/IPMI

(vrw10: Note made at https://wiki.cam.ac.uk/cl-sys-admin/Service_Desk_Knowledgebase:_Remote_Management#Further_CL_Sys-Admin_Resources but we'll need a step-by-step guide to used these tools.)

https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94951 has the policy on requests for SW for the pool of 41 ACS machines. Basically individual users can load private copies of any 'special' things they need in their $HOME (and maybe setting some environment variables to find it); anything of use to the bulk of the people doing the course should be requested by the course giver.

https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94954 has info on sshd brute force defences, possible reduction, and pointer to 'bedtime reading' and 'dos and donts' (he created an account without contacting us)

https://rt.cl.cam.ac.uk/Ticket/Display.html?id=94965 et al are about old ssh clients connecting to the Lab ssh servers and being told "no matching mac found: client hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160,hmac-ripemd160@openssh.com,hmac-sha1-96,hmac-md5-96 server hmac-sha2-512-etm@openssh.com,hmac-sha2-256-etm@openssh.com,hmac-ripemd160-etm@openssh.com,umac-128-etm@openssh.com,hmac-sha2-512,hmac-sha2-256". Correct fix is to upgrade their ssh clients (which may require upgrade of OS). Til then, connect in via slogin-oldssh.cl.cam.ac.uk