HP-UX system administrator tasks

[Craig Tran]

Hi all,
I am new in the Unix enviroment. I don't know what thing that I have to check, or pay attention to as an HP-UX system administrator.

all advices are helpful. Is there a guideline from HP to someone like me??

Thanks

[Steven E. Protter]

This is not complete but covers some basics:

Quartly Tasks:
Make sure my application cd is ordered and apps are installed.
Check on any service contracts coming due.
Check and see if I have to spec or purchase new servers.
Make sure quarterly patch sets are installed.
Sit and think about what manual tasks i can automate with an innovative new cron job


Monthly Tasks:
Review Bastille security_patch_check output, plan and build any releases needed.
Review output of imporant monthly cron jobs.
check_patches swverify software(also after any software install)
Plan work for my monthly downtime maintenance

Weekly:
Review all relavent security logs(usually spread this out over a few days), the important stuff emails me anyway.
Check file system space
Review tripwire reports/audit reports ids/9000 data.

Daily:
Review enterprise critical cron output. The really important stuff is automated and emails me when there is trouble.
Review btmp(lastb) and wtmp(last) output for stuff done by root that I did not do.
Think like an evil hacker and figure out how I'd compromise my system, device a plan to plug the hole.
make sure cron is running. It thats not running, half my security stuff isn't being checked.
Review Oracle reports from oracle's cron jobs.
Conduct a meeting with operations to find out about anything I may need to know.

Many of the other suggestions you will receive I do by automated cron job(s).

SEP

[Joseph Loo]

hi,

read these opinions:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=203667

and the online document on managing system and workgroup for HP-UX:

http://www.docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/5187-2216/5187-2216_top.html&con=/hpux/onlinedocs/5187-2216/00/00/1-con.html&toc=/hpux/onlinedocs/5187-2216/00/00/1-toc.html&searchterms=5187-2216&queryid=20040610-202918

regards.

[Hemanth Gurunath Basrur]

Hello Craig,

HP can also assist you in performing system administration tasks. This Website gives you information about various HP-UX system administration tasks

http://www.hp.com/hps/perevent/valupack/hpuxsysadmin/#services

Also, go through HP-UX System Administration Manager (SAM) documentation on http://docs.hp.com.

Also, plan to attend this training
http://www.hp.com/education/courses/h5875s.html

The course outline describes various tasks performed by a system administrator.

HTH.

Regards,
Hemanth

[Shaikh Imran]

Hi,
In a very simple way:
These are the tasks a sys adm have to perform.It may vary from organisation to organisation but most are common.
1)check & update individual patches.
2)check & update monthly patches.
3)keep a track on the server resources by monitoring the servers,storages & backup devices.
4)if you are also expected to do the backup then make sure you have the latest backup of O.S. as well as the database till date.If possible verify these backups.
5)Regular check for the filesystems
6)Regular check for syslog and other log files for errors.
7)Physical checks if possible for LED/LCD error codes on systems,storages,etc..,
8)schedule some cron jobs for automated daily and monthly processes and also to monitor the o/p of the same.
9)Some system admins also monitor user processes and trim the unwanted processes and also keep a track of idle users etc..,
10)Some also do the kernel tuning as and when required for database & O.S. performance
11)Also Most important task is the system security. system admin must ensure that their systems are secured from the external attacks or internal fingers..
12)Active part in database setup,reorganisation etc..,

And many more ...

Regards,

[Sanjay Kumar Suri]

Following is from SNA material on "The Role of the System Administrator":
Hardware Responsibilities
- Create and maintain a hardware diagram of the system.
- Verify that peripherals are installed correctly and tested.
- Monitor performance of hardware components.
- Arrange for repair in event of hardware failure.
Software Responsibilities
- Install & configure the HP-UX OS.
- Create file systems. Manage the integrity of file systems.
- Monitor system resource usage.
- Design and implement backup and recovery routines.
- Configure and maintain printer spooler software.
- Install and maintain network communication software.
- Update the HP-UX OS for new releases.
- Install & update application software.
Responsibilities to the Users
- Allow user access to the system as required.
- Evaluate user needs.
- Plan for future growth/change.
- Provide assistance to the user community.
- Implement the policies and procedures regarding the use of the computer system and network.

sks

[R. Sri Ram Kishore_1 · Accepted solution]

Hi,

Here is a list:

1. Daily Tasks
a.Check local disks on all machines to prevent them from filling up
b. Check for runaway processes on all machines
c. Check print queues
d. Check printer paper

2. Weekly Tasks
a. Tape backups
b. Disk usage reports
c. Check printer toner/pens/wax sheets

3. Miscellaneous Jobs
a. Update scripts
b. Upgrade software
c. Update documentation
f. Contacting vendors

HTH,
Sri Ram

[MarkSyder]

Check the following files daily:

/var/adm/btmp
/var/adm/sulog
/var/adm/wtmp
/var/adm/cron/log
/var/adm/lp/log
/var/adm/syslog/syslog.log

If any of them become extremely large null them thus:

> /var/adm/... (filename as appropriate). DO NOT delete any of these files - nulling the file will empty the file leaving it available for future use.

Check for core files:

find / -name core -print

You can almost always delete these, but be aware that some developers who have never worked as sys admins occasionally create files called core.

Make sure your backups work every night - preferably Data Protector. In addition, backup your system disc via ignite at least annually, and definitely before making any major system change (which includes installing a patch with a name beginning PHKL).

Make sure your predecessor aliased potentially dangerous commands (e.g. rm = remove). If he didn't, make sure you do.

That should keep you busy for the next day or two!

Mark Syder (like the drink but spelt different)