Remote System Admin

[okcunix]

I'm part of a team of Sys Admins that are going to start doing "remote system admin" at multiple sites across the US. Would like to hear from someone who's done/doing it, the types of things that we need to be aware of? What toolsets do you use?

[Sridhar Bhaskarla]

Hi Tim,

We did it before. There will be times when you will feel desperate to go the system. If you have anyone located near the system (probably an SA with minimal experience), then you will feel comfortable. Otherwise, you will run into problems during the hardware maintenances etc.,

Having a access to the console of the system is a must. It can be done either though GSP lan or a terminal server.

You may also want to consider monitoring tools like VPO etc., so that you can get alarms in advance. EMS can be very handy in such instances.

-Sri

[Patrick Wallek]

I am currently doing that. My co-worker and I have about 20 systems around the country. The biggest thing you want is (as already stated by Sridhar) some sort of console access, be it web console, terminal server or something.

We also make use of the EMS toolset and OVO / VPO / whatever the name is today.

The biggest problem I have is when something goes wrong and HP is at the remote site and I'm not. I'm one that is always looking over the CSE's should when they are repairing the machine.

It's really not bad if your machines are stable and you have a decent network/WAN connection between you and the remote machines.

[Michael Tully]

One older method of having access to system consoles was setting up a terminal server, but these days most people use the GSP lan where possible.
If you have Operators on the site this can help in certain situations. One of the best things is to have tools available to you to do monitoring, where it can be done via a paging service, snmp traps or even email. If there are any hardware problems, having trusty on site engineers is far better than a operator.

[John J Read]

Good notes.

Also,

*Mirroring the root drive has saved me more than once on remote servers.

* Keep a set of updated Ignite tapes with the remote server and make sure someone knows how to find/insert them. I leave them in the drives usually.

* Network backups are tough with remote servers. Firewalls usually get in the way.

* Make sure you know the network admin at the remote site especially if you have NIC on their network or if they control the routers.