Storage Area Networks For DummiesÂ®

More documents

Recommendations

Info

$Fsagamocdo testebi me-4 kurselTaTvis pediatriaSi \\\\ razea yvelaze ...$

$\\\\ gulmkerdis romeli fascia uqmnis kafsulas sarZeve jirkvals ...$

288 Part IV: SAN Management and Troubleshooting array 1 array 2 array 3 switch_A switch_B Figure 11-7: Use SAN management framework software to monitor the SAN’s health. server1 backup1 server2 test_01 webserver4 Agent-based management To funnel the status of all your SAN components into one easy-to-understand view, you need some way for each component to communicate its status to the SAN management framework. This task is usually accomplished by little software programs called agents, which are small pieces of code that run on a server, switch, or storage array; monitor the status of the component; and report back to your SAN management framework. This agent technology exists because different vendor components aren’t universal (interchangeable), just as Chevy parts don’t fit on a <strong>For</strong>d. Competition causes vendors to make things unique to their products because that gives them an advantage in the industry. These advantages are ultimately disadvantages, however, when it comes to trying to get these products to work together. To circumvent the lack of compatibility, someone writes an agent that knows how to translate from one component’s language to the other’s so that the component can be monitored and controlled.
Chapter 11: Approaches to SAN Management 289 Health monitoring Health monitoring works in conjunction with the agents that I mention in the preceding section. Because the agent talks to the components, the hub, switch, HBA, or storage array can give the agent an update on what it’s doing, how it’s performing, and whether anything is going on that the administrator needs to be warned about. Then the agent forwards this update to the management framework so that it can be logged and presented to the SAN administrator. Any changes in the status of any component on the SAN can be displayed on the SAN administrator’s console immediately, and then the administrator can take action. Levels of monitoring Health monitoring involves various levels of detail: ✓ At the simplest level, you’re notified whether a component is up or down (in other words, on or off). ✓ The next level gives some information on whether the status of the component is good or bad. A SAN switch, for example, can report that all its internal components are working properly and that the status is good. If one of its dual power supplies burns out but the switch is still operating, it reports that things are bad but that it’s still functioning. ✓ The lowest level of monitoring reports details about a component — in the case of a switch power supply, for example, the actual voltage level coming in from the outlet. All these health-monitoring levels allow you to capture the status of everything in your SAN without having to run around the computer room checking the status lights on all your components. Your SAN management framework takes all these messages and converts them to events or icons on the administrator’s screen to show you what’s going on. In-band and out-of-band management You have two ways to communicate with your components to read their status or tell them to do something: ✓ In-band management ✓ Out-of-band management Figure 11-8 shows the two ways that your management server can communicate with your SAN components.
Page 1:
Making Everything Easier! 2nd Edit
Page 4 and 5:
Storage Area Networks For Dummies
Page 7 and 8:
Author’s Acknowledgments Christop
Page 9:
Contents at a Glance Introduction .
Page 12 and 13:
x Storage Area Networks For Dummies
Page 14 and 15:
xii Storage Area Networks For Dummi
Page 16 and 17:
xiv Storage Area Networks For Dummi
Page 18 and 19:
xvi Storage Area Networks For Dummi
Page 20 and 21:
xviii Storage Area Networks For Dum
Page 22 and 23:
2 Storage Area Networks For Dummies
Page 24 and 25:
4 Storage Area Networks For Dummies
Page 26 and 27:
In this part . . . The computer ind
Page 28 and 29:
8 Par t I: SAN 101 In a nutshell, y
Page 30 and 31:
10 Par t I: SAN 101 Disk drives in
Page 32 and 33:
12 Par t I: SAN 101 Finding Out Whe
Page 34 and 35:
14 Par t I: SAN 101 ✓ Servers tha
Page 36 and 37:
16 Par t I: SAN 101 ✓ Gateway: A
Page 38 and 39:
18 Par t I: SAN 101 on the other ha
Page 40 and 41:
20 Par t I: SAN 101 All Fibre Chann
Page 42 and 43:
22 Par t I: SAN 101 ✓ Any backup
Page 44 and 45:
24 Par t I: SAN 101 Host layer Fabr
Page 46 and 47:
26 Par t I: SAN 101 Newer drive-int
Page 48 and 49:
28 Par t I: SAN 101 ✓ Long-wave:
Page 50 and 51:
30 Par t I: SAN 101 Large-scale, co
Page 52 and 53:
32 Par t I: SAN 101 Hubs typically
Page 54 and 55:
34 Par t I: SAN 101 You could conne
Page 56 and 57:
36 Par t I: SAN 101 Using modular s
Page 58 and 59:
38 Par t I: SAN 101 Data routers A
Page 60 and 61:
40 Par t I: SAN 101 Cables Cables a
Page 62 and 63:
42 Par t I: SAN 101 Core (9-micron
Page 64 and 65:
44 Par t I: SAN 101 Basic SAN port
Page 66 and 67:
46 Par t I: SAN 101 Table 2-2 (cont
Page 68 and 69:
48 Par t I: SAN 101 a Fibre Channel
Page 70 and 71:
50 Par t I: SAN 101 The RAID type t
Page 72 and 73:
52 Par t I: SAN 101 ✓ RAID 2: RAI
Page 74 and 75:
54 Par t I: SAN 101 RAID 0+1 set: D
Page 76 and 77:
56 Par t I: SAN 101 downtime is a p
Page 78 and 79:
58 Par t I: SAN 101 These arrays ar
Page 80 and 81:
60 Par t I: SAN 101 Most SAN storag
Page 82 and 83:
62 Par t I: SAN 101
Page 84 and 85:
64 Par t I: SAN 101 When you were a
Page 86 and 87:
66 Par t I: SAN 101 Bandwidth Movin
Page 88 and 89:
68 Par t I: SAN 101 The phone netwo
Page 90 and 91:
70 Par t I: SAN 101 The Switched Fa
Page 92 and 93:
72 Par t I: SAN 101 Again, think of
Page 94 and 95:
74 Par t I: SAN 101 The switches’
Page 96 and 97:
76 Par t I: SAN 101 So what can you
Page 98 and 99:
78 Par t I: SAN 101 For example, if
Page 100 and 101:
80 Par t I: SAN 101 Distance slows
Page 102 and 103:
82 Par t I: SAN 101 You need to rep
Page 104 and 105:
84 Par t I: SAN 101 Little things c
Page 106 and 107:
86 Par t I: SAN 101 If you’re pur
Page 108 and 109:
88 Par t I: SAN 101 Dual I/O paths
Page 110 and 111:
90 Par t I: SAN 101 All switch vend
Page 112 and 113:
In this part . . . If this were a b
Page 114 and 115:
94 Par t II: Designing and Building
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
100 Par t II: Designing and Buildin
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
In this part . . . Don’t let the
Page 216 and 217:
196 Par t III: Using Advanced SAN F
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
226 Part III: Using Advanced SAN Fe
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259: 238 Part III: Using Advanced SAN Fe
Page 292 and 293: In this part . . . Now that you’v
Page 294 and 295: 274 Part IV: SAN Management and Tro
Page 354 and 355: In this part . . . This is the part
Page 356 and 357: 336 Par t V: Understanding the Cool
Page 358 and 359:
338 Par t V: Understanding the Cool
Page 360 and 361:
Page 362 and 363:
Page 364 and 365:
Page 366 and 367:
Page 368 and 369:
Page 370 and 371:
Page 372 and 373:
Page 374 and 375:
Page 376 and 377:
Page 378 and 379:
Page 380 and 381:
Page 382 and 383:
Page 384 and 385:
Page 386 and 387:
Page 388 and 389:
Page 390 and 391:
Page 392 and 393:
Page 394 and 395:
Page 396 and 397:
Page 398 and 399:
Page 400 and 401:
Page 402 and 403:
Page 404 and 405:
Page 406 and 407:
Page 408 and 409:
Page 410 and 411:
Page 412 and 413:
Page 414 and 415:
Page 416 and 417:
Page 418 and 419:
Page 420 and 421:
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
In this part . . . Ah, The Part of
Page 428 and 429:
408 Par t VI: The Part of Tens Usin
Page 430 and 431:
410 Par t VI: The Part of Tens and
Page 432 and 433:
412 Par t VI: The Part of Tens much
Page 434 and 435:
414 Par t VI: The Par t of Tens NAS
Page 436 and 437:
416 Par t VI: The Par t of Tens But
Page 438 and 439:
418 Par t VI: The Par t of Tens rem
Page 440 and 441:
420 Storage Area Networks For Dummi
Page 442 and 443:
Page 444 and 445:
Page 446 and 447:
Page 448 and 449:
Page 450 and 451:
Page 452 and 453:
Page 454 and 455:
Page 456 and 457:
Page 458:
show all

Storage Area Networks For DummiesÂ®

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?