17.03.2015 Views

Storage Area Networks For Dummies®

Storage Area Networks For Dummies®

Storage Area Networks For Dummies®

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

312<br />

Part IV: SAN Management and Troubleshooting<br />

reference to see whether it could be related to your current issue. The log is<br />

either in the memory of the SAN switch itself or on a management console<br />

that monitors switches for these types of events.<br />

Broken fabric switch<br />

Here, I’m talking about a switch that’s physically broken, not a software corruption<br />

or configuration that went astray. (I cover those situations in the<br />

upcoming section “Continuous problems.”)<br />

A good SAN switch has many redundant features, such as dual power supplies<br />

and multiple fans. Most switches have a network connection to send<br />

Simple Network Management Protocol (SNMP) alerts to your SAN management<br />

framework server that monitors the whole SAN. A catastrophic outright<br />

failure of an entire switch is unheard of (knock on wood), but it is possible.<br />

Your SAN management framework should be able to alert you about powersupply<br />

failures, fan problems, ports going bad, or even an outright disappearance<br />

of your SAN switch from the rest of the fabric.<br />

The most important thing is that you have a backup of your switch configuration<br />

somewhere. If a switch is toast and needs to be replaced, would you<br />

know the zoning and port configuration off the top of your head? Didn’t think<br />

so. <strong>For</strong> this reason, it’s important to have this configuration saved somewhere<br />

off the switch itself.<br />

In a single-switch SAN, or one with two switches that aren’t directly connected,<br />

the configuration of the SAN is isolated to that switch. In other words,<br />

all the settings that define what port can see what other port (zoning) and<br />

how those ports are supposed to communicate (fabric, point-to-point, loop<br />

mode, and so on) are all self-contained on that switch only. If you had to<br />

replace that switch with one fresh out of a box, you’d have to replace the configuration<br />

manually.<br />

Most switch vendors have a command that you can issue to the switch to<br />

make it save its current configuration to a file somewhere on your network.<br />

The process usually requires a protocol such as File Transfer Protocol (FTP)<br />

to log in to a server on your network and save a file that contains all the<br />

zoning and switch parameters. Then this file can be restored via a command<br />

to the switch at any time (usually, if something goes horribly wrong).<br />

Figure 12-2 shows the two directions that a configuration can go in: dumped to<br />

a server for safekeeping or loaded back to a switch to restore a configuration.<br />

In multiple-switch SAN fabrics, the switches share the configuration information,<br />

so if you plug a brand-new switch into an existing fabric, it learns the SAN<br />

configuration from the other switches. Check with your switch vendor, but<br />

most switch manufacturers are adopting this automatic configure process to<br />

make adding onto or replacing switches easier.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!