Service Desk Knowledgebase: Remote Management

From Computer Laboratory System Administration
Jump to navigationJump to search


This is the Remote management content page of the CL Wiki Service Desk Knowledgebase. Its purpose is to provide information to the Service Desk team on how to handle problems and requests about this CL service. If you are involved with the provision of this CL service please feel free to add to the knowledge about that it.

If CL staff need to tell the Service Desk team about problems with this service please email
sys-admin-aside@cl.cam.ac.uk.

Return to the Service Desk Knowledgebase SERVICE PORTFOLIO

Key Service Description & URLs

CL Customer Documentation

Further CL Sys-Admin Resources

cl-amttool

The command cl-amttool on the slogin-serv machines allows direct control using userids and passwords stored on the filer. When users have control over other systems, the same userids and passwords are used.

amtterm

wsman

ipmitool

Underpinning Services

  • ??? - Any supporting or underpinning services

Customer-base for this Service

  • All staff and students of the Computer Laboratory

Costs

  • Free to all current staff and students of the Computer Laboratory

SLA

  • N/A

Service Desk Call Handling Procedure

  • RT tickets can be escalated by changing the Queue to backoffice with the Owner set to Nobody and the Status as new. Tell the requestor:
    I am passing this request over to the experts who, I'm sure, will be in contact shortly.

Contacts

Primary

Availability

  • Monday:
  • Tuesday:
  • Wednesday:
  • Thursday:
  • Friday:
  • Saturday: Closed
  • Sunday: Closed

Hints, Tips & Known Issues

Sorting out BMC Access

See BMC ACL - when up if present

Cannot SSH to a Linux Box

Machines on the Self Managed subnet can only be accessed from machines which are on the Lab's 'internal' VLANs. Users should be able to connect to slogin-serv, and then on to the Self Managed VLAN.

Piete Brooks (24/03/15)

If the machine is pingable but SSH to it gives: 

 ssh: connect to host torbatejam port 22: Connection refused

It means either 'machine up as far as IP up, but not services' (e.g. stuck in fsck) or 'sshd isn't running'.

To find out about the machine's BMC capabilties at a laira:~: prompt use:
cl-hosts -p MachineName | tr ' ' '\12' | grep BMC
For example: 

 BMC
 BMC_AMT
 BMC_AMT_2
 BMC_AMT_2.1
 BMC_AMT_2.1.3
 BMC_AMT_IDER
 BMC_AMT_SOL
 BMC_AMT_SOL_16994
 BMC_IDER
 BMC_SOL
 BMC_next_MAC
 BMC_shared_NIC
 BMC_www
 BMC_www_16992

It needs have BMC_vnc_plus and cl-amttool MachineName | grep AMT.ver would need to show AMT 6 or later 

 AMT version: 2.1.3

to support BMC KVM using VNC Viewer Plus.

Using BMC SoL (how?) to login using Radmin Viewer 3.5 (Install on local PC). SSH can be checked with cl-asuser service ssh status 

 ssh stop/waiting

started with cl-asuser service ssh start 

 ssh start/running, process 3286

and checked again with cl-asuser service ssh status 

 ssh start/running, process 3286



If you get ticket with "can't ssh to $host .cl.cam.ac.uk" then you need to look at what information has been given by the user. If none has been provided then the first task is: 

 Dear XXXXX,
           Can you send me your log of the attempted connection please?
 If possible can you paste the time/date you attempted to ssh. This will help ascertain the fault.
 Regards

Categorising Keywords

  • RemoteManagement Remote Management IPMI BMC
Retrieved from "https://wiki.cam.ac.uk/wiki/cl-sys-admin/index.php?title=Service_Desk_Knowledgebase:_Remote_Management&oldid=3361"