network os servers administration

7/31/2019 Network OS Servers Administration

http://slidepdf.com/reader/full/network-os-servers-administration 1/16

System Administration Made Easy 15 –1

&KDSWHU1HWZRUN266HUYHU

$GPLQLVWUDWLRQ

&RQWHQWV

Overview ................................................................................................................15 –2

Operating System Tasks ......................................................................................15–2

Other Tasks .........................................................................................................15–12



Chapter 15: Network/OS/Server Administration

Overview

Release 4.6A/B 15 –2

2YHUYLHZ

This chap ter is about u sing transactions to get to the op erating system log, regardless of the

platform.

2SHUDWLQJ6\VWHP7DVNV

2SHUDWLQJ6\VWHP$OHUW$/

*XLGHG7RXU

Use the opera ting system alert monitor for a qu ick visual review.

1. In the Command field, enter transaction AL16 and choose Enter

(or from th e SAP standard menu, choose Tools → CCMS → Control/Monitoring→ Performance menu →

Operating System → Local → Alerts → AL16-Operating system).

2. Review this screen for potential

problems.




Operating System Tasks

System Adminstration Made Easy15 –3

6\VWHP/RJV26

:KDW

The system logs are wh ere the operating system an d som e app lications write event records.

Depend ing on the operating system, there may be mu ltiple logs.

:K\

There may be indications of a developing p roblem (for examp le, a hard dr ive that generates

errors may indicate that it is failing and needs to be replaced).

+RZ

*XLGHG7RXU

1. In the Command field, enter transaction OS06 and choose Enter (or from th e SA P standard menu, choose Tools → CCMS → Control/Monitoring→ Performance menu →

Operating System → Local → OS06-Activity).

2. Choose Detail analysis menu .

2






3. Choose OS Log.

This screen shows th e operating

system log. In this example, it is

the N T event log.

3






17(YHQW/RJV

:KDW

NT has three event logs:

< System< Security

< Application

:K\

There may be indications of a developing p roblem. If the security au dit pa rameters have

been properly set, you could d etect un auth orized attemp ts to access files.

Configuring the security aud it fun ction is a trad eoff amon g the following:

< The need to log security events.

< System resources to track and maintain th e log.The more d etailed you make the log, the more the system p erformance will degrad e.

This degrad ation is du e to the extra processing required to track and log the items.

< Effort required to aud it the log (dep end ent on th e size of the log).

*XLGHG7RXU

The following steps show you h ow to op en the N T event logs.

1. On the NT desktop, choose Start → Programs → Administrative Tools → Event Viewer .

2. The following logs can be selectedunder Log:

< System

< Security

< Application

3. Look for un usu al entries.

Monitor these entries regularly to

recognize unfamiliar events su ch

as errors, failures, or security-

related entries. These events d o

not u sually occur.

2






&KHFNLQJ)LOH6\VWHP6SDFH8VDJH5=

:KDW

The file system should have suff icient “free space” for norm al operations. Over time,

var ious activities will write files that w ill use u p file space. These files need to be

periodically reviewed and moved or backed u p and deleted.

A few of the items that consum e file space when mon itoring file space usage include:

< Transports

< Sup port packages

< Extract files from the R/ 3 System

< Program logs

< Backup logs

< Error logs

< Inbound interface files

< Third-party programs that store their d ata outside the R/ 3 database

< Trace files

< Spool files (if stored at th e OS level)

In add ition to these items, check to see that the “hou se cleaning” program s are run ning

prop erly (see SAP note 16083).

:K\

If your file system fills up, the R/ 3 System m ay stop because the d atabase cannot w rite to a

file. If R/ 3 stops, any business operations that u se the system will also stop.

For example, note the following sequen ce of events:

1. The SQL Server transaction log fills up the file system.

2. SQL Server cannot write anymore entries into the log.

3. SQL Server will stop .

4. R/ 3 will stop.

Your u ser will not be able to per form activities such as:

< Enter orders

< Generate shipping d ocum ents to ship prod ucts

To plan for such a situation:

< Anticipate and p lan for disk space needs.

< Determine if storage space expansion is needed .

If storage space expan sion is needed , purchase and installation p lans need to be made.

The expansion should be plann ed to minimize operational disruption.






< Determine if “house cleaning” is needed .

If archiving is required for data files, archive to qua lity storage m edia such as an optical

disk, CD, or other long-term storage media.

*XLGHG7RXU

You can use the R/ 3 Alert Monitor or go to the operating system to check file system space usage. In this

section, we use the R/ 3 Alert Monitor, because w e can set alert points.

1. In the Command field, enter transaction RZ20 and choose Enter

(or from th e SAP standard menu, choose Tools → CCMS → Control/Monitoring→ RZ 20-Alert Monitor).

2. Click the node (+) to expand the

monitor set.

3. Select the monitor set (for

example, SAS for docu).

4. Choose .

2

3

4






5. Drill down to get to the following

starting node:

<SID>\ <host >_<SID>_< Instance>

(for example,

SAS\ pa100767_SAS_00).

6. Drill dow n to the dr ives

OperatingSystem → Filesystems.

The drives are color coded to

indicate alert status:

< Green (OK)

< Yellow (Warning)

< Red (Critical)

7. Select a dr ive (for examp le, H:)

and dr ill dow n to see its statistics

(Freespace an d Percentage_Used ):

These are statistics at the d rive

(not d irectory) level.

As you v iew these statistics, keep

your system in m ind.

For examp le, on you r system,

drive H may contain the d atabase

wh ich takes up all the space on

that d rive. Keeping this in mind,

you can expect and ignore the

warning message, or change the

alert threshold for that specific

dr ive. For more information on

changing the alert threshold, see

page 15–9.

5

6

7






&KDQJLQJWKH$OHUW7KUHVKROG5=

Also see chap ter 10, Maintaining the Alert Thresholds for RZ20.

To customize the points when the

alert indicator chan ges from green to

yellow, yellow to red , back from red

to yellow, and yellow to g reen:

1. Click the node of the drive for

which you wan t to change the

threshold (for example, drive H:).

2. Select an alert (for examp le,

Freespace).

3. Choose Properties.

1

3

2






4. Then:

a. Choose .

b. The Threshold values fields w ill

change color from grey to

wh ite, indicating tha t you can

change the values.

5. Under Threshold values, select a

threshold chan ge point (for

example, Change from GREEN to

YELLOW ).

6. Enter the new value for wh en the

alert w ill change color (for

example, 500).

These threshold values are sp ecificto your system an d even to

specific drives in your system.

7. Choose Save.

8. A message app ears in the status

bar indicating that the new

properties were saved.

6

7

5

8

4b

4a






&OHDQLQJ2XW2OG7UDQVSRUW)LOHV

:KDW

Transport files are used to transp ort or m ove SAP objects and customizing changes between

clients and systems.

:K\

If left un checked, tran spor t files could grad ua lly fill up the file system.

If the file system fills, operations m ay be affected because:

< Outbou nd R/ 3 System files may not be created.

< Transport export may fail.

< Inbound files may n ot be created.

In an extreme situation, if you ru n ou t of file system sp ace, R/ 3 may stop, or you m ay have

other failures because R/ 3 or other ap plications cannot write to the necessary files.

:KHQ

The transport directory check is imp ortant:

< After a major imp lementation where many transp orts have been created that take up a

lot of space.

< Immed iately before (or after) performing a database copy, if you do n ot use a central

transp ort d irectory, most (if not all) files dated before the copy become irrelevant to the

system.

< After installing a large supp ort package.

+RZ

To comp lete a transpor t d irectory check:

1. Check the following directories un der /usr/sap/trans:

< Data

< Cofiles

< Log

2. Sort the directory by date to determine file age.

3. Archive obsolete files.

These are files created before a d atabase refresh or those that h ave been ap pliedsuccessfully to all target systems.

4. As an option, archive old tran sports to a backup med ia such as tape, optical disc, or CD.




Other Tasks


Check the following:

< Sup port p ackage directory /usr/sap/trans/EPS/in

< Transport da ta directory /usr/sap/trans/data

Sup port p ackage files can be reloaded if needed and can be large (for examp le, hot

package 10 for Release 4.0B is over 200MB).

2WKHU7DVNV

&OHDQWKH7DSH'ULYH

To minimize a backup failure d ue to a d irty head, clean the tap e dr ive as part of a

preventive m aintenance program.

To keep you r tape d rive clean:

< Follow the tape dr ive manu facturer’s instructions for you r tape dr ive.

Some d rives specify a specific interval of use for cleaning, typically based on hou rs of

use. Adjust your cleaning frequency to account for you r u sage. Remember, that these are

recommendations not ru les. If you consistently have recording errors or “head dirty”

messages, then decrease the time between cleanings. If you have to clean you r tape

dr ives more or less frequently, this task should be moved to the ap prop riate interval.

Some drives (for example, DLT) do not requ ire regular cleaning. They only need

cleaning w hen th e “clean head” indicator light is activated .

< Use the man ufacturer’s app roved cleaning cartridge for the tape d rive.

< Use the cleaning cartridge according to the m anu facturer’s instructions.

< Between uses, store the cleaning cartridge according to the man ufacturer’s instructions.

Keep you r server room clean.

A du sty or dirty environment w ill not only make you clean your tap e drive more often, but

will also coat the inside of the server w ith du st and cause a cooling problem.




Other Tasks


8QLQWHUUXSWLEOH3RZHU6XSSO\

&KHFNWKH8QLQWHUUXSWLEOH3RZHU6XSSO\

:KDW

The uninterrup tible power supp ly (UPS) that you u se shou ld be monitored by a control

program. This program, wh en triggered by a pow er event, records the event an d initiates a

shutd own p rocess of the R/ 3 environmen t (R/ 3, the database, related ap plications, and th e

operating system), and finally the server. In ad dition, most UPSs have a self-test and

capacity calibration fun ction. The resu lts of these tests are logged . Specific data logged

depend s on the program and the UPS.

:K\

You n eed to review the p ower events tha t triggered the UPS control program .

While the UPS protects the server, the control program should be recording pow er eventssuch as pow er dips, brown outs, power failures, etc. This record ing could help you or the

facilities person solve electrical problems in th e facility. For examp le, a pattern of pow er

dips or ou tages may indicate a problem elsewh ere in the building.

You need to verify that:

< The UPS is functionin g

< The self-tests comp leted su ccessfully

< There is sufficient capacity in the ba tteries

The batteries in the UPS mu st be period ically replaced. If the batter ies are low, the cap acity

test will indicate that the batteries do n ot have sufficient capacity to shu tdow n the system

before failing.

+RZ

Review th e log for the UPS control program .

&KHFN\RXU8366KXWGRZQ3URFHVV

:KDW

Verify that your UPS shutd own process works. A shu tdow n pr ocess is an autom ated script

for the UPS to shut d own R/ 3, the database, other app lications, the operating system, andthe UPS.

:K\

This check verifies that the entire shu tdow n process works as planned an d d ocumented .

When there is a power failure, the R/ 3 environment should be shu t dow n in an orderly

man ner. There shou ld be sufficient reserve in the UPS to reach the en d of the shu tdow n




Other Tasks


process. Something m ight have changed since your last test to cause the shu tdow n p rocess

to fail. If this process fails, you n eed to find out wh y an d fix the p roblem.

The stopsap comman d d oes not work w ithin all UPS control programs. You need to

verify that you r UPS control program will properly stop R/ 3 and the database before

shutting d own the server.

Like a car battery, UPS batteries wear ou t over time an d mu st be replaced. If the battery is

worn out, the UPS will not hav e sufficient power to complete the shutd own process.

&KHFN0DLQWHQDQFH&RQWUDFWV

:KDW

Many of the servers and related equ ipmen t are und er maintenan ce or service contracts with

the manu facturer or distributor.

< The produ ction system and critical equipment shou ld be und er a “prem ium” 24 hour x 7

day (x 2 hou r response) sup port agreemen t.< Less critical equipm ent can be un der a next-business-day support agreement.

:K\

If you n eed sup port or service and the service contract has expired, the confusion an d time

to reestablish the service contract could be critical.

:KDW

The supp ort level should be selected based on equ ipment u se. If a piece of equipm ent

becomes critical to the compan y’s operation, its supp ort level should be u pgraded to reflect

the critical nature of tha t equipment. Conversely, equipment could become “noncritical” orbe replaced. In this situation, the service contracts could be d own graded or d ropp ed as

appropriate.

+RZ

< Keep a list of service contracts.

Includ e wh at these contracts are for and the expiration d ate in the list.

< Review equipm ent usage to determine if the supp ort level for equipm ent should be

upgraded, downgraded, or dropped.

< Review the list for expiration d ates each quarter.

How long in advance of the expiration date to do this review dep ends on the time ittakes to go through th e pu rchase requisition and ap prova l process in your comp any.

< Renew service contracts.




Other Tasks


5HYLHZ+DUGZDUHRUD6\VWHP0RQLWRU3DJLQJ6\VWHP

:KDW

A hard ware or system mon itor paging system generates alert messages (includ ing e-mail)

and pages based on your p redefined parameters. Depend ing on the software, the following

can be monitored:

< Hard ware items (such as servers, routers, and p rinters)

< Logs (such as op erating system, app lications, and database)

By mon itoring the NT event logs, you can m onitor events from the SAP system log. This

way, critical events such a s an Update Terminate can be detected an d acted on a s soon as

they happ en.

The following screen is courtesy of TNT Software.

The screenshot above shows that th e monitor has three functional wind ows:

< Notification Rules

This mechanism passes or filters events, and d etermines wh at action w ill be taken on the

events that are passed.

< Events

These are the events that have been p assed to the monitor program . (They got through

the filters in Notification Rules.)

< Monitored device




Other Tasks

Release 4.6A/B 15 16

These are the monitored servers and IP devices.

This example, however, has not been configured to p ick up and report on SAP events.

Initially, there will be a lot of tuning as th e system p aram eters are adjusted. Over time,

parameter adjustments will redu ce.

:K\

You m ay need to change alert parameters to filter noncritical events and to generate alerts

for critical even ts. The key to rem ember is that this process is dyn amic. Some of these tasks

are as follows:

< Accoun t for new events that have never occurred .

Critical, you need to generate a p age

Importan t, you need to generate a m essage (for examp le, e-mail)

< Determine if an event th at used to be filtered now needs to generate an alert

< Filter out events (both old an d n ew) that shou ld not genera te alert messages

Filtering is necessary to m anage th e messages that are r eviewed. If too man y irrelevantmessages get through the filter, it becomes d ifficult to review the alert m essage log.

< Adjust for personnel changes

There may be oth er events that r equire action (for examp le, shift or d uty chan ges for

organizations with several people “on call”).

< Test that all alert m echanisms are fun ctional.

The paging/ messaging fun ction needs to be tested regu larly. If the monitoring program is

unable to send a page, you will not receive the page w hen a critical alert occurs.

The inability to send a page can be caused by:

< Someone changing something in the e-mail or phone system th at preven ts alertmessages from being sent.

< A phone patch cable that has disconnected from the modem.

+RZ

To review the paging system:

< Review the var ious monitored logs (such as the NT event logs) to look for events that

should generate an alert message (e-mail or page).

The monitor program needs to be configured to pick these events up and prop erly

process them.

< Review the a lert monitor log for alert events that should be “filtered” out.

The monitor program needs to be configured to filter or ignore such even ts.

< Test all alert mechanisms, such as p ager, e-mail, etc. to make sure th at they are

functional.

If you receive regu lar d aily e-mail messages, then the e-mail testing is being done for

you.

network os servers administration

Documents