17.03.2015 Views

Storage Area Networks For Dummies®

Storage Area Networks For Dummies®

Storage Area Networks For Dummies®

SHOW MORE
SHOW LESS

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

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 5: Designing the SAN<br />

127<br />

WWN zoning (soft zoning) is more flexible than port zoning (hard zoning)<br />

because the zone information is based on the device’s address instead of<br />

the port on the switch that it’s connected to. If a switch port goes bad and<br />

you move the device connected to that port to a different port, you need to<br />

change the zone information to reflect the changed port before the device connected<br />

to the new port will work again in the fabric. By using WWN zoning, the<br />

address will have moved with the device, so no zone changes are needed.<br />

Hard zoning<br />

Hard zoning is a method of grouping individual physical switch ports in<br />

a switched fabric together into a zone that only allows communication<br />

between physical ports on the switches. (See Figure 5-31.) Only the physical<br />

ports in the zone can communicate with each other. No other ports in<br />

the fabric can communicate with those ports, and members of that zone set<br />

cannot communicate with any other ports in the fabric.<br />

Zone members can communicate only with other members of their zone. A<br />

zone set can accommodate multiple zones; switch ports can be members of<br />

multiple zone sets. If a switch port is made a member of multiple zone sets, it<br />

can communicate with the ports of all the zone sets that it has membership<br />

with. The same holds true for soft zone members (see the preceding section).<br />

Hard zoning at the level of physical ports is the most secure method of zoning.<br />

You can mix domain and port names along with WWNs in the same zone, but<br />

after you do, all the ports revert to soft zoning. (See Figure 5-32.)<br />

Zone alias names<br />

An alias is a custom name that you can assign to switch ports and WWN<br />

addresses in a zone. You use an alias to rename the port names of the switch<br />

and the WWNs of the HBAs connected to the switches with something that<br />

makes more sense to a human. Trying to figure out what has access to what<br />

by using port IDs and/or WWN addresses is hard. Using more human-understandable<br />

naming makes better practical sense.<br />

As an example, suppose you have four servers and one storage array in your<br />

SAN, as in Figure 5-33. This is your production SAN. Two of the servers run an<br />

Oracle database under Unix, and the other two run your mail system under<br />

Windows NT. The servers each have two HBAs apiece, connected to the storage<br />

array through two different switches. As you can see from the figure, the<br />

switch ports assume the address of the HBA of the server that’s plugged into it.

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

Saved successfully!

Ooh no, something went wrong!