San Switch Policy Monitors - Brocade Communications Systems Brocade 8/12c User Manual

Brocade network advisor san user manual v11.1x (53-1002167-01, may 2011)
Hide thumbs Also See for Brocade 8/12c:
Table of Contents

Advertisement

SAN Switch policy monitors

Enables you to set the following policy monitors on SAN switches.
Brocade Network Advisor SAN User Manual
53-1002167-01
Check if the product is configured to send events to this server—Enables you to determine if
the Management application server is registered as an SNMP recipient and Syslog recipient.
If the Management application server fails to register as a listener for SNMP, Syslog, and other
events, the Management application server cannot notify you of changes to the fabric or
device. If a fabric or switch fails, the Management application cannot provide notification, log,
or support data. Therefore, you may not realize that there is an inconsistency between the
physical device status and device status in the Management application for some time.
Rule Violation Fix—If the report shows a SNMP not registered as recipient violation, the SAN
Administrator can register the Managemet server as a SNMP recipient through the SNMP Trap
Recipients dialog box (Monitor > SNMP Setup > Product Trap Recipients). Refer to Fault
Management.
If the report shows a Syslog not registered as recipient violation, the SAN Administrator can
register the Managemet server as a Syslog recipient through the Syslog Recipients dialog box
(Monitor > Syslog Configuration > Product Syslog Recipients). Refer to Fault Management.
Check for redundant connections to neighboring switches—Enables you to determine if there
are at least the minimum number of configured inter-switch links (ISL) between each switch
pair.
The resiliency and/or 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 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 number of tunnels is used to
compare with the minimum number setting to decide if the redundant ISL check is success or
fail.
Rule Violation Fix—If the report shows a violation, the SAN Administrator can add redundant
ISLs between the source and target switch.
Policy Monitor overview
29
825

Advertisement

Table of Contents
loading

This manual is also suitable for:

Network advisor 11.1.xBrocade bladesystem 4/24

Table of Contents