Brocade Communications Systems Network Advisor 12.3.0, User Manual

Page: 1285 / 1940

Brocade Network Advisor SAN User Manual 1233
53-1003154-01
Policy monitor overview
31
Some devices can function as both initiator and target. If the application finds this type of
device as one of the active zone members, this device port is treated as both initiator and
target:
-
Target (storage port) — The application counts the number of initiator ports zoned to this
storage port.
-
Initiator — The application counts this device as an initiator port for other storage ports in
the same zone.
Rule Violation Fix — If the policy monitor report shows a violation, the Administrator must make
sure the initiator port limit is under the recommended number.
•
Check zones that do not contain any online member — This fabric policy monitor enables you to
identify zones in which all zone members are offline.
NOTE
The application does not count end devices which are missing from the fabric and D,PI zone
members (online or offline) as online zone members. The application only counts zones with
online WWN members as online zone members.
Rule Violation Fix — If the policy monitor report shows a violation, you can use the Zoning dialog
box (Configure > Zoning > Fabric) to bring the devices back online (refer to
“Zoning” on
page 885).
For example, if you use the policy monitor to determine when all WWN members in a zone are
offline, you can fix the violation through the Zoning dialog box by locating the target fabric and
bringing the devices back online.
Switch and router configuration policy managers
Switch and router configuration policy managers enable you to set the following configuration
policy managers on switches and routers.
•
Check connections: redundant connections to neighboring switches (SAN only) — This switch
and router configuration policy manager enables you to determine if there are at least the
minimum number of configured inter-switch links (ISLs) between each switch pair.
The resiliency and redundancy of the fabric is an important aspect of the SAN topology. To
remove any single point of failure, SAN fabrics have resiliency built into the Fabric OS.
For example, when a link between two switches fails, routing is recalculated and traffic is
assigned to a new route. Therefore, to provide redundancy and enable resiliency, using ISLs,
the best practice is to make sure that there are at least two ISLs between each switch pair.
The redundant link refers to both the physical connection and the logical ISL. No matter how
many physical connections exist between the two base switches, there is only one logical ISL
between two logical switches. A logical ISL counts as one connection between the source and
destination switches; therefore, when a logical ISL is present, the connection count may be
inaccurate. To pass this monitor, the total number of logical ISL and physical connections must
be greater than the minimum connection.
For FCIP tunnels, one tunnel counts as one connection. This rule does not check circuits within
the FCIP tunnel. The total number of trunk ISLs, single ISLs, and the number of tunnels is
compared with the minimum number settings to decide if the redundant ISL check is a
success or a failure.