Who's Afraid of Linux on Power, AIX and VIOS? Not i.

31
© HelpSystems. Company Confidential. All trademarks and registered trademarks are the property of their respective owners. Who’s Afraid of Linux on Power, AIX, and VIOS? Not i. Donnie MacColl Director of EMEA Technical Services

Transcript of Who's Afraid of Linux on Power, AIX and VIOS? Not i.

© HelpSystems. Company Confidential.All trademarks and registered trademarks are the property of their respective owners.

Who’s Afraid of Linux on Power, AIX, and VIOS? Not i.Donnie MacCollDirector of EMEA Technical Services

© HelpSystems. Company Confidential. 2

Agenda

• Comparing IBM i, AIX/VIOS, and Linux Monitoring Requirements

• Is VIOS the Same as AIX?• Using Best Practice Templates• Do I Need to Throw Away All My Scripts?• Reporting

© HelpSystems. Company Confidential. 3

Comparing IBM i, AIX/VIOS, and Linux Monitoring Requirements

© HelpSystems. Company Confidential. 4

How Many Companies UseAIX and VIOS?

HelpSystems conducted the 2015 IBM i Marketplace Survey and the results are in!

© HelpSystems. Company Confidential. 5

What are the three most common itemsthat affect performance?

a) CPU, disk, and memory

b) Processors, ASPs, and memory pools

c) CPU, file systems (logical and physical), and memory

d) All of the above

The answer is D. Yep, they’re all the same!

Comparing IBM i, AIX, and Linux

© HelpSystems. Company Confidential. 6

• VIOS

• A mirrored disk or a raid disk becomes inactive

• QSECOFR or another powerful user profile is used or changed

• Java processes and webservers need monitoring

• An interactive job is using an excessive amount of CPU– Maybe an intensive SQL query

IBM i

© HelpSystems. Company Confidential. 7

• Applications are slow

• Know when powerful commands are used– For example, STRSST, CRTUSRPRF, and DLTLIB

• Cache battery is low

• A communications port or line is failing

• Uncapped processors exceed a pre-defined threshold

• Power fails or systems are being run on utility power

• QSYSMSG– Who uses it already?

IBM i

© HelpSystems. Company Confidential. 8

• Monitor and report on entries in the Error Report

• Check that critical subsystems exist and are active

• When disk mirroring is active, alert when Quorum is set to “on”

• For each file system, check when stale physical partitions exist

• Check for failed logins

AIX

© HelpSystems. Company Confidential. 9

• Monitor for disk I/O busy and sustained disk utilization

• Verify operational status of path to MPIO device(s)– hdisk0 & hdisk1

• Ensure critical files exist are alert if modified– For example, new entries in cron

• Monitor for disk usage, including inode space used

• Paging space should be relative

AIX

© HelpSystems. Company Confidential. 10

• Check logical volumes are available

• Check for failed drives

• Ensure vital files exist and have not been modified within a specific time frame period– For example, cron, profile, INITTAB, and iptables

Linux

© HelpSystems. Company Confidential. 11

• Monitor for login failures in secure log

• Check used disk space does not exceed threshold

• Ensure there is plenty of inode space

• Paging file usage should be relative

• Sustained CPU identified

• Ensure critical processes are active

Linux

© HelpSystems. Company Confidential. 12

Is VIOS the Same as AIX?

© HelpSystems. Company Confidential. 13

Is VIOS the Same as AIX?

© HelpSystems. Company Confidential. 14

What Is VIOS?

Until recently, every partition running on IBM i required hardware such as disk storage and network connections dedicated to that partition.

This is inflexible and can be costly because of the hardware that is required for each partition. IBM has developed the Virtual I/O Server, which addresses these issues by acting as a host partition for I/O.

Virtual I/O Server (VIOS) is a logical partition (LPAR) that has physical I/O such as disk storage and network adapters connected to it.

This I/O is then provided to client LPARs running IBM i, AIX, or Linux within the same physical server.

© HelpSystems. Company Confidential. 15

Using Best Practice Templates

© HelpSystems. Company Confidential. 16

Solutions Portfolio

© HelpSystems. Company Confidential. 17

© HelpSystems. Company Confidential. 18

Why Re-Invent the Wheel?

© HelpSystems. Company Confidential. 19

Use Templates

• Write once, apply to many

• Consistent approach

• Ease of deployment

• Let’s look at some pre-configured templates

© HelpSystems. Company Confidential. 21

Do I Need to Throw Away All My Scripts?

© HelpSystems. Company Confidential. 22

Existing Scripts

• Will Halcyon make our existing scripts redundant?

• Why use scripts?

• Let’s look at how we can harness the power of your scripts by using the flexibility of Halcyon

© HelpSystems. Company Confidential. 23

Reporting

© HelpSystems. Company Confidential. 24

Reporting

© HelpSystems. Company Confidential. 25

Reporting

© HelpSystems. Company Confidential. 26

© HelpSystems. Company Confidential. 27

© HelpSystems. Company Confidential. 28

© HelpSystems. Company Confidential. 29

© HelpSystems. Company Confidential. 30

Key Takeaways

1. There’s no need to be afraid of VIOS/AIX or Linux.2. The things you need to be monitoring on IBM i, AIX,

and Linux are similar.3. You can monitor VIOS or AIX without necessarily

knowing the operating system.4. You can enhance the power of your existing scripts

by embedding them into a point-and-click solution with instant alerting methods.

5. It’s easy to create SLA performance reports on the fly for capacity planning and management reporting purposes.

6. Halcyon offers built-in templates to monitor and keep control of critical processes and applications running on your AIX and Linux environments.

© HelpSystems. Company Confidential. 31

Contact Information:

Web: www.helpsystems.com/

halcyon

Email:

[email protected]

Phone U.S. 800-328-1000

Outside U.S. +44 (0) 870 120 3148

Thank You For Joining Us