What is a benefit of WWN zoning over port zoning?

Question

Options

• AA server, after being moved to another switch port in the fabric, maintains connectivity to its zone
• BA server, after replacement of its HBAs, maintains connectivity to its zone partners without the need
• CA server, after replacement of its HBAs, does not require performing a fabric login to maintain
• DA server, after being moved to another fabric, maintains connectivity to its zone partners without

• A
  80% (24)
• B
  13% (4)
• C
  3% (1)
• D
  3% (1)

Explanation

Zoning can be categorized into three types: Port zoning: Uses the physical address of switch ports to define zones. In port zoning, access to node is determined by the physical switch port to which a node is connected. The zone members are the port identifier (switch domain ID and port number) to which HBA and its targets (storage devices) are connected. If a node is moved to another switch port in the fabric, port zoning must be modified to allow the node, in its new port, to participate in its original zone. However, if an HBA or storage device port fails, an administrator just has to replace the failed device without changing the zoning configuration. WWN zoning: Uses World Wide Names to define zones. The zone members are the unique WWN addresses of the HBA and its targets (storage devices). A major advantage of WWN zoning is its flexibility. WWN zoning allows nodes to be moved to another switch port in the fabric and maintain connectivity to its zone partners without having to modify the zone configuration. This is possible because the WWN is static to the node port. Mixed zoning: Combines the qualities of both WWN zoning and port zoning. Using mixed zoning enables a specific node port to be tied to the WWN of another node.

No community discussion yet for this question.