Daily checks for AIX business critical boxes. Post: 302367462

Sponsored Content

Operating Systems AIX Daily checks for AIX business critical boxes. Post 302367462 by bakunin on Monday 2nd of November 2009 05:38:17 PM

11-02-2009

Registered User

Quote:

Originally Posted by deepm

Ok as you said some systems have to be monitored hourly, so i want to know what are the things to be monitored hourly is it just restricted to FileSystem, Memory.....?

Ask yourself what it is that keeps a system going (that is: fulfilling its purpose). This is your answer.

If anything has to be monitored every minute, hour, day, week or month depends on the system and the characteristics of its purpose. There is no general answer because there is no "general system".

If you ask "which is the best car" without specifying for which purpose the only thing one could answer is: that depends. If you want to transport tons of goods it might be some large truck and not the Ferrari, if you want to win races it might be the other way round and if you want to go offroad you will quickly find out that both are quite bad compared to a Landrover.

Coming back to your question: what does a system keep going:

a) environmental issues
- energy
- climate/temperature control
- ....

b) OS level
- availability of processing resources - CPU
- availability of memory
- availability of storage space - filesystem
- OS resources consumption: process table, etc.
- availability of network bandwith
- ...

c) application specific
- depends on the application, things like queue lengths, transaction times, ...

Be aware that this list is far from being complete, its just the most obvious things, feel free to add whatever is important for your system to continue working. As a rule: everything that is important for the system to continue doing its purpose you need a "sensor" - a logfile, a piece of software, a blinking warning lamp, what ever.

Some of the things might be already covered: you do not have to watch climate control if the system is in a data center where air condition is provided and covered for without you doing anthing. You still might want to watch over fans, etc. and get an alarm if the system starts overheating.

Speaking about the things left on the list: it depends on the system and what it is used for, how often something has to be checked. Because these checks take usually some processing power (in most cases little programs do the work) it is generally good to do the checks as often as necessary and as rarely as possible. If you have a system where never data gets stored (a gateway system, for instance) a check of the filesystems every minute is superfluous, on a database server it might be necessary. The same goes for CPU, network and all the other things on the list.

So there is no such thing as a "thing that has to be monitored hourly", because, whatever the thing in question is, depending on the specifics of the system one hour might be an overkill as well as far too little.

I hope this helps.

bakunin

bakunin

View Public Profile for bakunin

Find all posts by bakunin

8 More Discussions You Might Find Interesting

1. Programming

text boxes, radio buttons , check boxes in c++ on unix

Hi ! Please tell me how to get radio buttons, text boxes , check boxes , option buttons , pull down menus in C++ on Unix. I think it would be done using curses.h ..but that's all i know. TIA, Devyani.

2. UNIX for Advanced & Expert Users

Allocate memory for a shell script in Aix at runtime-urgent critical

How to allocate memory for a shell script on aix box at the time of execution i.e at runtime Are there any commands for AIX in specific Thanks in Advance

3. AIX

Capturing Process on AIX boxes - IMP

Guys we all know what command 'COLUMNS=2047 /usr/bin/ps –eo pid,ppid,uid,user,args' does.It prints 5-column output for the running processes on a AIX box. Here is simple thing i need: I need to insert this tabular data in a db2 table. How do i need? I have created table with these five...

4. UNIX for Dummies Questions & Answers

Daily File Checks

Hello all, I'm sorry if this is answered elsewhere, I've used the search function and can't find the specifics of what I'm after. I am brand new to playing with linux, and ideally I want to get better to help the company that I now work for. What I want to do: Create a script that I...

5. AIX

Post mortem for critical Production AIX System Reboot/Crash

Hello All, Critical AIX production box crashed/rebooted while our team is working on it and we need to generate a detailed report for that, below are few questions that need to be included in the report. (We are System Administration team and everyone in our team has root access via sudo as well...

6. Shell Programming and Scripting

Daily Checks

Hey Guys, I'm seeking some assistance in getting this script to run as a cron job for the user oracle.. the script is basically to perform 2 ADRCI checks... see the script below... i'm getting the following error: /export/home/oracle/Daily_Checks/ADRCI_Daily_Checks.sh: syntax error at line 16:...

7. Red Hat

Cron entry for every 10 mints on business day business hour

Could you �crontab� it to run every 10 minutes on work days (Mo - Fr) between 08:00 and 18:00 i know to run every 10 mints but can any one guide me how to achieve the above one

8. AIX

Setup 1 Digi PortServer II with 5 x AIX boxes

Hi everyone, My latest challenge sees me assisting with the setup of one of our classroom labs. We are trying to configure the lab so that the (5) IBM 9115-505 servers (all running AIX7.1) have their serial 0 ports connected to a Digi PortServer II, which is on the classroom LAN, along with the...

LEARN ABOUT DEBIAN

critical

CRITICAL_ENTER(9)					   BSD Kernel Developer's Manual					 CRITICAL_ENTER(9)

NAME

     critical_enter, critical_exit -- enter and exit a critical region

SYNOPSIS

     #include <sys/param.h>
     #include <sys/systm.h>

     void
     critical_enter(void);

     void
     critical_exit(void);

DESCRIPTION

     These functions are used to prevent preemption in a critical region of code.  All that is guaranteed is that the thread currently executing
     on a CPU will not be preempted.  Specifically, a thread in a critical region will not migrate to another CPU while it is in a critical
     region.  The current CPU may still trigger faults and exceptions during a critical section; however, these faults are usually fatal.

     The critical_enter() and critical_exit() functions manage a per-thread counter to handle nested critical sections.  If a thread is made
     runnable that would normally preempt the current thread while the current thread is in a critical section, then the preemption will be
     deferred until the current thread exits the outermost critical section.

     Note that these functions are not required to provide any inter-CPU synchronization, data protection, or memory ordering guarantees and thus
     should not be used to protect shared data structures.

     These functions should be used with care as an infinite loop within a critical region will deadlock the CPU.  Also, they should not be inter-
     locked with operations on mutexes, sx locks, semaphores, or other synchronization primitives.  One exception to this is that spin mutexes
     include a critical section, so in certain cases critical sections may be interlocked with spin mutexes.

HISTORY

     These functions were introduced in FreeBSD 5.0.

BSD
								  October 5, 2005							       BSD