슬라이드 1 - ibm - united states · ppt file · web view ·...

© 2009 IBM Corporation

2009 하반기 SMA 세미나HACMP Best Practices

2009. 10. 15.백진훈 ([email protected])MTS, GTS, IBM Korea


목차

’’


•


• “…A fundamental design goal of (successful) cluster design is the elimination of single points of failure (SPOFs) through appropriate design, planning, selection of hardware, configuration of software, and carefully controlled change management discipline.…”


High Availability does not mean no interruption to the application thus we say,

fault resilient instead of tolerant.


• “…A fundamental design goal of (successful) cluster design is the elimination of single points of failure (SPOFs).…”


’’


–

RG1 (NodeA, NodeB)

NODE A NODE B

StorageSubsystem

Topology Components:• Cluster name• Node Names• IP Network

• Interfaces• Serial Network

Types of Resources• Service IP• Volume Group/s• Application Server

Resource Components:• Resource Group/s

• Policies - startup - fallover - fallback

• Dependencies• Parent / Child• Location

RG2 (NodeB)

Service IPVolume GroupDevelopment App

Cluster Name: Cluster 1

Network: net_ether0

Network: rs232_net

Network: diskhb_net

Service IPVolume GroupProduction App


RG1 (NodeA, NodeB)

NODE A NODE B

StorageSubsystem

RG2 (NodeB)

Service IPVolume GroupDevelopment App


Network: net_ether0

Network: rs232_net

Network: diskhb_net

Service IPVolume GroupProduction App

Location Dependencies:- RGs can coexist on same node- RGs can coexist on different nodes

- Can also set Priorities:- High- Intermediate- Low

Diagram Assumptions:RG1 – High PriorityRG2 – Low Priority

On Fallover:- RG2 Offline- RG1 will move to Node B


RG1 (NodeA, NodeB)

NODE A NODE B

StorageSubsystem

RG2 (NodeB, NodeA)

Service IPVolume GroupApplication 2


Network: net_ether0

Network: rs232_net

Network: diskhb_net


Environment:- Each Machine is running its own Production application - Node A fails to Node B - Node B fails to Node A

Fallover Behavior:- On fallover the target machine will need enough CPU & memory resources in order to handle the load of both applications

RG2 (NodeB, NodeA)


RG1 (NodeA, NodeB)


ONLINE

ONLINE


I/O drawer

I/O drawer

I/O drawer

I/O drawer

I/O drawer

1

2

3

4

5

6

7

8

9

10

Ie 2. Two nodes sharing I/O drawer

Ie 1. SCSI adapters for rootvg on same BUS

Real Customer Scenarios:


…………………………


Planar 1 Planar 2

rootvg

11

fcs2

ent4

1

ent48

ent8

fcs3

fcs4

fcs0

fcs1

ent16

ent20

ent12

SA0

fcs7

fcs6

fcs15

fcs8

fcs5

EmpTy

EmpTy

EmpTy

2 3 4 5 6 7 8 9 10 1 2 3 4 5 6 7 8 9 10

fcs11

ent24

1

ent28

ent32

fcs12

fcs13

fcs9

fcs10

ent40

ent44

ent36

SAS0

fcs17

fcs16

fcs19

fcs18

fcs14

EmpTy

EmpTy

EmpTy

2 3 4 5 6 7 8 9 10 1 2 3 4 5 6 7 8 9 10

L8 L9 L10 L11

L8 L9 L10 L11

L8 L9 L10 L11

L8 L9 L10 L11

T6

Planar 2 Planar 1

T5 T6 T5

rootvg

00

rootvg

22


–“”

p595

20GB

30GB

30GB

rootvg X1

X4

X3

datavg

appvg

I/O drawer * 2ea

16 core

60GB


VS.


––


–

–““


––

–

––


––

––


“


–

–


–

–

–


– ––


– – –

’


–

–


–


–––– –“”–••––


’’


–


–

※


–

ThinkC en ter

1 394

P72

Th inkC enter

1 394

P72

ThinkC en ter

1394

P72

ThinkC enter

139 4

P72

SVC

SVC

DWDM(FC Extender)

DWDM(FC Extender)

SVC/ Metro-Mirroring(Syncronous PPRC)

HACMP/ XD


’’


FRAME 1

–


–


–

“” –

–––

“”

–––


“”


–

In virtualized environments:

9.12.4.11

9.12.4.13

9.12.4.11

!REQD en2 100.12.7.9

9.12.4.13

!REQD en2 100.12.7.10-

Typical File:

Most adapters will use netmon in the traditional manner, pinging 9.12.4.11 and 9.12.4.13 along with other local adapters or known remote adapters, and will only care about the interface's inbound byte count for results.

interface en2 will only be considered up if it can ping either 100.12.7.9 or 100.12.7.10

Note:There are additional !REQD formats that may be used within the netmon.cf file outlined in the description of APAR IZ01332


’’


Do’s

‘’


’


’

“–‘’”


’’


–

슬라이드 1 - ibm - united states · ppt file · web view ·...

Documents