You are on page 1of 217

AMP 200 Course Introduction

Revision 1017 11
AMP 200 Course Introduction

Revision 1017 12
AMP 200 Course Introduction

Revision 1017 13
AMP 200 Course Introduction

Revision 1017 14
AMP 200 Course Introduction

Revision 1017 15
AMP 200 Course Introduction

Revision 1017 16
AMP 200 Course Introduction

Revision 1017 17
AMP 200 Course Introduction

Revision 1017 18
AMP 200 Course Introduction

Facebook Brocade Certified


http://www.facebook.com/pages/Brocade-Certified/161604617227755
LinkedIn Brocade Certified
http://www.linkedin.com/groups?gid=3752161&trk=hb_side_g
MyBrocade Brocade University Community
http://community.brocade.com/community/forums/education
MyBrocade Certification Community
http://community.brocade.com/community/forums/education/certification
MyBrocade Education Alumni Community
http://community.brocade.com/community/forums/education/alumni

Revision 1017 19
AMP 200 Course Introduction

Revision 1017 1 10
AMP 200 Course Introduction

Revision 1017 1 11
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 21
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 22
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 23
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 24
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 25
AMP 200 Analytics Monitoring Platform Introduction

Fabric Vision technology comprises two integrated fabric solutions:


Monitoring and Alerting Policy Suite (MAPS): Provides an easy-to-use solution for policy-
based threshold monitoring and alerting. MAPS proactively monitors the health and
performance of the storage infrastructure to ensure application uptime and availability. By
leveraging prebuilt rule-/policy-based templates, MAPS simplifies fabric-wide threshold
configuration, monitoring, and alerting. Administrators can configure the entire fabric (or
multiple fabrics) at one time using common rules and policies, or customized policies for
specific ports or switch elementsall through Brocade Network Advisor.
Flow Vision: Provides a comprehensive vision of and deep insight into fabric traffic flows,
along with the ability to non-disruptively create and capture copies of traffic flows for analysis
of traffic flows, bottlenecks, bandwidth utilization, and similar fabric connectivity functionality.
Flow Vision also provides a test flow generation capability that you can use to pre-test a SAN
infrastructure for robustness. This test flow generation capability is also useful for testing the
internal connections on a switch before deploying the switch into a production environment. In
addition, Flow Vision allows you to test for fabric connectivity issues, such as slow drain,
bandwidth utilization, and similar issues.
Brocade Analytics Monitoring Platform:
Optimize infrastructure without downtime
Quickly pinpoint problems, uncover issues before users are affected
Gain deeper insight into end-to-end application performance
Automate monitoring and alerting of abnormal behaviors
Revision 1017 26
AMP 200 Analytics Monitoring Platform Introduction

The Brocade Analytics Monitoring Platform is a purpose-built SAN appliance dedicated for
measuring application- and device-level I/O performance and analyzing traffic behavior within
a Brocade Gen 5 and above Fibre Channel network. These analytics deliver actionable
intelligence to administrators, enabling them to maximize performance across the data center.
The platform utilizes Brocade Fabric Vision technology to non-invasively and non-
disruptively conduct analytics data collection and provide insight into performance,
dramatically reducing troubleshooting time.
The Analytics Monitoring Platform runs a special version of Fabric OS (FOS) with additional
services added to create the new metrics and data. Users familiar with the FOS CLI will feel
right at home on the Analytics Monitoring Platform, since it uses the same commands. All
configuration of the Analytics Monitoring Platform and metrics can be accessed directly from
the CLI.

Revision 1017 27
AMP 200 Analytics Monitoring Platform Introduction

Footnote 1: A single AMP device can monitor up to 20,000 flows.

Revision 1017 28
AMP 200 Analytics Monitoring Platform Introduction

Footnote 1: Application slowdown can be influenced by the following conditions:


Host:
Resources- Memory, CPU etc.
HBA- Driver, Queue depth
Network:
Speed Mismatch
Oversubscribed ISL
Slow Drain
Storage:
Fan In
Workload spread based on IOPS and Throughput
Queue depth

Revision 1017 29
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 10
AMP 200 Analytics Monitoring Platform Introduction

In order to manage the AMP device, post installation, BNA needs to discover the AMP device
and the desired monitoring and notification policies configured.

Revision 1017 2 11
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 12
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 13
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 14
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 15
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 16
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 17
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 18
AMP 200 Analytics Monitoring Platform Introduction

Flow Collections are a group of entities of homogeneous type qualified by one or more
properties. Flow Collections are similar to MAPS port groups in in that they allow the ability to
perform operations (monitoring and notifications) based on a specified set of grouped flows.

Revision 1017 2 19
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 20
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 21
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 22
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 23
AMP 200 Analytics Monitoring Platform Introduction

Virtual taps can be deployed on any F_Port non-disruptively and with no additional hardware
Dual virtual tap or double mirroring: monitoring at host and target
Benefits:
Provides direct visibility into host device behavior
Allows direct measurement of fabric latency at IO level

Revision 1017 2 24
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 25
AMP 200 Analytics Monitoring Platform Introduction

Revision 1017 2 26
AMP200 Analytics Monitoring Platform Deployment Overview

Revision 1017 31
AMP200 Analytics Monitoring Platform Deployment Overview

Revision 1017 32
AMP200 Analytics Monitoring Platform Deployment Overview

The Brocade Analytics Monitoring Platform has the following key features:
Ability to monitor a compatible switch in the fabric running Remote Flow Mirroring (RFM)
technology from Brocade with nonintrusive flow monitoring requiring no physical taps into the
physical (optical) media within the fabric
The data gathering by AMP is non-disruptive to the SAN environment. It is transparent to
the host/target device communications when being deployed as well as when in use
The visibility into the I/O stream is done in a way that does not introduce latency or degrade
the link quality in any way
The actual data payload of the traffic is not exposed in any way
The Fibre Channel switch and fabric being monitored are not impacted in terms of additional
load on the CPU
The deployment and configuration are simple and the flows are detected and monitored
automatically
Dedicated hardware
8 MBytes of zone database memory (2 MBytes per partition)
Monitoring and management software
Easy and transparent scalability

Revision 1017 33
AMP200 Analytics Monitoring Platform Deployment Overview

Diagram Description:
Once connected, the analytics platform learns and discovers I/O traffic flows between devices
to analyze device behavior, derive metrics, and flag anomalies in the device transactions. The
following figure illustrates a typical topology. In this case, all traffic between Host 1 and Target
1 can be monitored by AMP by mirroring select frames across the ASL. In this configuration,
the monitoring is all from the perspective of Target 1's connection to the Monitored Switch.
Monitoring could also be done from Host 1's connection into the fabric by connecting an ASL
from the analytics platform to Switch 1, making it a Monitored Switch as well.
AMP provides visibility to SAN System Administrators for the following information:
I/O-level performance information
SCSI command behaviors
Both historical and real-time performance tracking for Service Level Agreements (SLAs)
AMP also provides tools to perform the following functions:
Optimize the performance of tape-, disk-, and flash-based storage systems
Integrate fabric- and physical-level metrics with host/storage device SCSI-level performance
metrics
Customize I/O performance data access in the form of easy-to-read dashboards and auto-
generated reports (requires purchase and deployment of a compatible Network Advisor
product

Revision 1017 34
AMP200 Analytics Monitoring Platform Deployment Overview

Revision 1017 35
AMP200 Analytics Monitoring Platform Deployment Overview

In order to manage the AMP device, post installation, BNA needs to discover the AMP device
and the desired monitoring and notification policies configured.

Revision 1017 36
AMP200 Analytics Monitoring Platform Deployment Overview

Footnote 1: The ASL is a trunkable connection between the monitored switch and the
analytics platform that uses a specialized form of E_Port (Analytics E_Port, or AE_Port) on
both ends of the connection. The AMP Platform is connected to a monitored switch directly
through an AE_Port-to-AE_Port ASL, which redirects the mirrored frames to the AF_Port in
the analytics platform.
Attaching devices other than a monitored switch to the analytics platform is not supported.
Both 16 Gbps and 8 Gbps ports are supported; but using an 8 Gbps port is not recommended
as this reduces by half the amount of data that can be mirrored.

Revision 1017 37
AMP200 Analytics Monitoring Platform Deployment Overview

Footnote 1: Fabric latency cannot be monitored for flows when the host and target are
connected to the same ASIC. If both the host and target reside on a fixed-port switch or on the
same blade, AMP will behave differently depending on the monitored switch.
Gen 5: AMP will track a single vTap when both host and target reside on the same ASIC. I/O
statistics will be collected only on the target port. AMP will track two vTaps when the host and
target reside on two different ASICs.
Gen 6: AMP will track a single vTap when both host and target reside on the same ASIC. I/O
statistics will be collected only on the host port. AMP will track two vTaps when the host and
target reside on two different ASICs.

Revision 1017 38
AMP200 Analytics Monitoring Platform Deployment Overview

The size of the supported zone database is 2 MB per partition for a total of 8 MB per physical
device enabling AMP to join directory only fabrics with up to 2 MB zone database

Revision 1017 39
AMP200 Analytics Monitoring Platform Deployment Overview

Multiple AE_Ports or AE_Port trunks are supported between a monitored switch and a logical
instance of an analytics platform. If multiple AE_Ports are present, the first AE_Port detected
(primary port) is used. The decision as to which port will be used is dynamic and cannot be
predetermined. In order to use more than one physical AE_Port, the ports must be trunked
and belong to the same trunk group.
The analytics platform supports a maximum of 23 AE_Ports, which are shared across all
logical instances of the analytics platform. The maximum count for any one instance is 24
minus the number of ports assigned to other logical instances of the analytics platform.
Both 16 Gbps and 8 Gbps ports are supported; but using an 8 Gbps port is not recommended
as this reduces by half the amount of data that can be mirrored.

Revision 1017 3 10
AMP200 Analytics Monitoring Platform Deployment Overview

The AF_Port must be configured on the analytics platform before vTap can import the
configuration. When connected, the vTap automatically (on monitored switch) discovers and
identifies the ASL and identifies the Analytics F_Port (AF_Port) on the analytics platform as
the destination port for the mirrored traffic

Revision 1017 3 11
AMP200 Analytics Monitoring Platform Deployment Overview

AF_Port: The AF_Port is the destination or target port for the vTap flows on the monitored
switches. The mirrored data from the vTap flows over the ASLs. However, the mirrored data is
ultimately directed to the AF_Port associated with the vTap flow as the destination port for the
sys_mon_analytics flow

Revision 1017 3 12
AMP200 Analytics Monitoring Platform Deployment Overview

Diagram Description:
Creating an Analytics F_Port:
In Brocade Network Advisor, you can configure an unoccupied Fibre Channel port on a
Brocade Analytics Monitoring Platform as an Analytics F_Port (AF_Port)
To create an AF_Port using Brocade Network Advisor, complete the following steps
1. Locate an unoccupied Fibre Channel port on the Brocade Analytics Monitoring Platform
2. Use one of the following methods to set that port as the AF_Port:
Select Monitor > Fabric Vision > Flow > Analytics Port > Enable
Right-click the unoccupied Fibre Channel port in the product tree and select Fabric Vision >
Flow > Analytics Port >Enable
NOTE: You can configure only one port as an analytical port in a logical switch or virtual
fabric.

Revision 1017 3 13
AMP200 Analytics Monitoring Platform Deployment Overview

Footnote 1: The following Gen 5 and Gen 6 switches running Fabric OS 8.0.1a or Fabric OS
8.0.1b support the multi-VF feature, where multiple sys_analytics_vtap flows can be active on
the same physical switch.
Brocade DCX 8510-4
Brocade DCX 8510-8
Brocade 6520
Brocade X6-4
Brocade X6-8
Terminology definitions
Virtual Fabric (VF): A fabric supported by a logical switch on the monitored switch.
ISL : A dedicated (physical) link between two logical switches.
Fabric ID: A distinct identifying number for a fabric.

Revision 1017 3 14
AMP200 Analytics Monitoring Platform Deployment Overview

Footnote 1: Virtual fabric (VF) functionality is covered in the Brocade Professional System
Administration course (BPSA300)
NOTE: The Brocade G620 Gen 6 switch and any Gen 5 switch running a version of Fabric
OS earlier than 8.0.1a do not support the multi-VF feature. There can only be one
sys_analytics_vtap flow active at a time in those cases.
A single physical AMP can only support up to four logical partitions. When an AMP has been
partitioned into four logical instances, it can monitor up to four fabrics, and up to 20 monitored
switches or 20 ASLs total in those four fabrics. Each of the four fabrics has at least one active
vTap flow (possibly more) pointing at their specific individual AF_Port on the AMP

Revision 1017 3 15
AMP200 Analytics Monitoring Platform Deployment Overview

Footnote 1: Enabling the mode may require you to disable the QoSH or QoSH5 zones, turn
on the compatibility mode, and then enable the zones again. When QoSH or QoSH5 zones
are present, enabling the vTap+QoSH compatibility mode requires a chassis disable. A
RASLog ZONE-1067 is posted when the vTAP+QoSH mode is enabled and QoSH5 zones
are remapped.

Revision 1017 3 16
AMP200 Analytics Monitoring Platform Deployment Overview

If vTap+QoSH compatibility mode is enabled and RFM is also active on the monitored switch,
then the vTap+QoSH compatibility mode cannot be disabled. You must deactivate the vTap on
the monitored switch, including all logical partitions where it is enabled and disable the
chassis, prior to disabling vTap+QoSH compatibility mode. By default, vTap+QoSH
compatibility mode is disabled. For switches that support partitioning, the configurechassis
command can be issued from any logical switch partition or context, but affects a chassiswide
scope regardless of switch context
Attempting to enable the vtap flow without the vTap and QoSH compatability mode enabled
will result in the following message:
Monitor_switch_host:FID128:admin> flow --activate sys_analytics_vtap
Enable vTap and QOS High Priority Zone Compatibility Mode to
activate VTAP flow. Please use configurechassis command to enable
this compatibility mode.

Revision 1017 3 17
AMP200 Analytics Monitoring Platform Deployment Overview

Use the flow --modify sys_analytics_vtap ingrport ingress_port_ID


mirrorport remote_domainID, remote_portID
command to set the desired values for the ingress and mirror ports. You can use an asterisk
(*) for the ingress port ID to indicate all valid ingress ports.
The remote domain ID is the domain ID of the analytics platform and the remote port ID is the
port index number of the AF_Port on the analytics platform.
In order to modify the ingress ports (which F_port traffic you wish to monitor) you must first
de-activate the flow. (flow deactivate sys_analytics_vtap)
Monitoring a specific F_Port on the switch
The following example modifies the sys_analytics_vtap flow to monitor a specific F_Port
(1/20) on the switch as the ingress port, then activates the flow.
mon_sw_host:admin> flow --modify sys_analytics_vtap -ingrport 1/20
mon_sw_host:admin> flow --activate sys_analytics_vtap

Revision 1017 3 18
AMP200 Analytics Monitoring Platform Deployment Overview

Revision 1017 3 19
AMP200 Analytics Monitoring Platform Deployment Overview

Revision 1017 3 20
AMP200 Analytics Monitoring Platform Deployment Overview

To modify the predefined analytics vTap flow from the Flow Monitoring dialog box, complete
the following steps.
1. Open the Flow Monitoring dialog box by choosing one of the following options:
Select a vTap flow, then select Flow > Edit.
Right-click the monitored switch and select Fabric Vision > Flow > Modify Analytics vTap
The Flow Monitoring dialog box displays with the following default values:
Target Switch: The monitored switch on which you want to modify the analytics vTap flow.
Flow Name: The flow name. By default, the flow name is sys_analytics_vtap.
Ingress: Whether ingress is a port or MAPS port group. By default, the Port option is
selected.
Analytics Port: Select the Auto Select check box to display the connected analytics platform
AF_Port. By default, the Auto Select check box is disabled.
D/I: The Port ID (in D,I format). Only available if you select the Auto Select check box.
2. Modify the values for the ingress port by clicking the browse button adjacent to the name.
3. Select an ingress port and click OK.

Revision 1017 3 21
AMP200 Analytics Monitoring Platform Deployment Overview

Revision 1017 3 22
AMP200 Analytics Monitoring Platform Deployment Overview

The AMP device does support monitoring OFI flows.


Overflow IT Flows: Flows are gathered under the OFI label for all IT flows learned after the
maximum number of individually monitored IT flows that can be supported by the current
configuration of AMP, has been reached. The maximum number of individually monitored IT
flows is determined by the reserved count for the IT flows and the available number from the
shared pool. IT flows in excess of this number and up to 10,000 flows, are collected under the
OFI category. The SID, DID and the associated vTap information is captured. When space
becomes available for reasons such as aging or deletion of an individually monitored IT flow,
the next IT flow learned by the AMP gets the space. The flow could be a new one or from the
OFI category.

Revision 1017 3 23
AMP200 Analytics Monitoring Platform Deployment Overview

Revision 1017 3 24
AMP200 Analytics Monitoring Platform Metrics Overview

Revision 1017 41
AMP200 Analytics Monitoring Platform Metrics Overview

Revision 1017 42
AMP200 Analytics Monitoring Platform Metrics Overview

Diagram Description:
Brocade Network Advisor (BNA): The primary graphical interface to manage and monitor the
Brocade Analytics Monitoring
Platform and the fabric switches.
Monitored Switch: This device supports the Brocade Virtual Tap (vTap) feature to mirror
selected frames remotely when connected to a Brocade Analytics Monitoring Platform using
an Analytic Switch Link.
Brocade Analytics Monitoring Platform: This device hosts the I/O analytics engine, and
leverages Flow Vision and the Monitoring and Alerting Policy Suite (MAPS) to receive,
monitor, and analyze the mirrored frame data
Flow Vision: Brocade technology that allows the construction of remote mirrored flows,
allowing flow data and metadata to be monitored for anomalies and problems.
Monitoring and Alerting Policy Suite (MAPS): Brocade technology that evaluates metrics
against thresholds, and can alert you to abnormal behaviors. On the analytics platform, MAPS
is also able to monitor I/O latency and performance metrics.

Revision 1017 43
AMP200 Analytics Monitoring Platform Metrics Overview

Footnote 1: The Remote Flow mirroring feature is a multi-faceted feature which includes
support for the AMP solution. Within a supported Brocade fabric the RFM capability can be
used to mirror traffic to a protocol analyzer or mirror select traffic to the switchs CPU for
analytic and troubleshooting purposes. A detailed look at the complete Remote Flow mirroring
functionality is presented in the Brocade Professional System Administration course (BPSA
300).

Revision 1017 44
AMP200 Analytics Monitoring Platform Metrics Overview

Diagram Description:
The Brocade Fabric Vision technology enables SCSI command frames and the associated
responses, as well as error message frames to be mirrored from the monitored switch running
Remote Flow Mirroring (RFM) to the analytics platform.

Revision 1017 45
AMP200 Analytics Monitoring Platform Metrics Overview

Footnote 1: Fabric latency monitoring correlates metrics derived at the Initiator and Target
ports of a flow to derive the transmission time between source and destination fabric
monitored switch ports.
All I/O metrics are collected and maintained at the flow level only.
AMP creates an IT metric entry for an IT flow when the AMP records a SCSI command being
sent from an Initiator to a Target. For an ITL flow, an ITL metric entry is created only if that
SCSI exchange involves a read (RD) or write (WR) command from the Initiator to a specific
LUN on the target. All other command exchanges where the read or write commands are not
involved (such as SCSI reserve and release pairs) are tracked using the default ITL metric.
This metric cumulatively tracks all commands for which a LUN has not been discovered,
proprietary SCSI commands that the AMP cannot decode (for example, proprietary data
replication or backup application commands), or if resource limitations prevent flows from
being included in the analysis. These restrictions help optimize the available ITL resources on
the AMP

Revision 1017 46
AMP200 Analytics Monitoring Platform Metrics Overview

Diagram Description:
Host initiates the IO by sending a read command.
Target sends 1 or more data frames.
Target completes the IO operation by sending status frame.
FCP is Fibre Channel Protocol.

Revision 1017 47
AMP200 Analytics Monitoring Platform Metrics Overview

Diagram Description:
Host initiates the IO by sending a write command.
Target sends xfer ready to signal host to start sending data.
Host can send 1 or more data frames.
Target completes the IO operation by sending status frame.
FCP is Fibre Channel Protocol.

Revision 1017 48
AMP200 Analytics Monitoring Platform Metrics Overview

Diagram Description:
The initiator will allow up to 7 outstanding commands when writing or reading from the target.
Most targets and hosts (HBA queue depth) allow this to be configured
The Q depth can impact the performance of a target

Revision 1017 49
AMP200 Analytics Monitoring Platform Metrics Overview

Footnote 1: The queue depth can impact the performance of a target port. Most targets allow
the queue depth to be configured.

Revision 1017 4 10
AMP200 Analytics Monitoring Platform Metrics Overview

The Fabric Insight Portal is web client of BNA that is used to manage the AMP device. In this
view the Read Completion Time is shown and it is reporting upwards of 300 ms. This
measurement is indicative of an application slowdown.

Revision 1017 4 11
AMP200 Analytics Monitoring Platform Metrics Overview

The Fabric Insight Portal is web client of BNA that is used to manage the AMP device. In this
view the Read Pending IOs are being shown. This number is being reported from the Storage
end.
Flow versus Port level pending IO reporting: (there is a dedicated default widget for the
highest port pending IOs values)
Storage Port pending IOs are a critical metric to determining IO oversubscription for storage
Storage devices can handle 2k IOs max

If storage port is over-queued, flow metrics can determine causation (identify host device(s)
responsible)

Revision 1017 4 12
AMP200 Analytics Monitoring Platform Metrics Overview

IOPS values are grouped by I/O block size (in bytes) into four groups: less than 8K, 8K to less
than 64K, 64K to less than 512K, and 512K or greater.
Additionally, the All group includes information for all the I/O block sizes.

Revision 1017 4 13
AMP200 Analytics Monitoring Platform Metrics Overview

The Fabric Insight Portal is web client of BNA that is used to manage the AMP device. In this
view avg number of outstanding IOPS for this flow is close to 170.

Revision 1017 4 14
AMP200 Analytics Monitoring Platform Metrics Overview

The Brocade Analytics Monitoring Platform measures flow exceptions associated with the
SCSI Read (RD), Write (WR), Inquiry (INQ), Request (REQ), Test unit ready (TUR), Reserve
(RSRV), and Release (RLSE) commands. The Other (OTH) category accounts for any other
SCSI I/O commands.
The AMP supports three types of error tracking for every flow: Aborts, Timeouts, and Check
Condition.
Each metric is incremented based on the following structure:
The Abort metric increments whenever an ABTS frame is received from either an Initiator or
Target port.
The Timeout metric increments for any I/O frame received by the analytics platform when no
associated First Response, Status, or ABTS frame is received for that I/O frame.
The Check Condition metric increments if the Target sends a status frame having the
SCSI_STATUS value set to an error.

Revision 1017 4 15
AMP200 Analytics Monitoring Platform Metrics Overview

The Brocade Analytics Monitoring Platform measures flow exceptions associated with the
SCSI Read (RD), Write (WR), Inquiry (INQ), Request (REQ), Test unit ready (TUR), Reserve
(RSRV), and Release (RLSE) commands. The Other (OTH) category accounts for any other
SCSI I/O commands.
The AMP supports three types of error tracking for every flow: Aborts, Timeouts, and Check
Condition.
Each metric is incremented based on the following structure:
The Abort metric increments whenever an ABTS frame is received from either an Initiator or
Target port.
The Timeout metric increments for any I/O frame received by the analytics platform when no
associated First Response, Status, or ABTS frame is received for that I/O frame.
The Check Condition metric increments if the Target sends a status frame having the
SCSI_STATUS value set to an error.

Revision 1017 4 16
AMP200 Analytics Monitoring Platform Metrics Overview

Diagram Description:
In order for a Brocade Analytics Monitoring Platform to provide fabric latency monitoring,
monitoring must be enabled on both host and target F_Ports for an Initiator-Target pair, and
the Host and Target devices must be part of the same fabric and connected to the same
analytics platform logical instance.
The following figure shows a typical configuration for fabric latency monitoring. An analytics
platform is connected to a fabric (FID 1) by way of Analytic Switch Links (ASLs) to two
different monitored switches. The analytics engine can then compare the time stamps on
frames that pass through the fabric against the ones mirrored directly to the appliance.
Fabric performance can be impacted due to any of the following issues:
One or more slow drain devices (a device that is slow to return buffer credits)
Oversubscribed device ports (too much traffic trying to use a port)
Oversubscribed ISLs (too much traffic trying to use a link)
Some other fabric issue (bad devices, problematic cabling, and so on)

Revision 1017 4 17
AMP200 Analytics Monitoring Platform Metrics Overview

The fabric latency flow metrics are calculated based on when the monitored frame enters and
exits the fabric.
Consult the Brocade Monitoring Analytics Platform User guide for the most probable potential
problems when high values are returned for fabric latency values

Revision 1017 4 18
AMP200 Analytics Monitoring Platform Metrics Overview

The Fabric Insight Portal is web client of BNA that is used to manage the AMP device. In this
view the Fabric IO Latency Status time and Read Exchange completion time is being shown
for a single flow. The green line indicates that there is almost zero fabric latency while the
Read Exchange Fabric Latency remains high. The next step would be to check the First
Response Time for this flow to check whether the storage device is able to keep up with the
IO command requests.

Revision 1017 4 19
AMP200 Analytics Monitoring Platform Metrics Overview

Revision 1017 4 20
AMP200 Analytics Monitoring Platform Metrics Overview

Revision 1017 4 21
AMP200 Analytics Monitoring Platform Metrics Overview

Limitations and considerations


In dual mirroring mode, the vTap on the host-side switch is used for calculating the host-
device demand rate.
For accurate host level demand rate, all IT flows under the given host must be mirrored in
the same AMP.
RoS % will not be calculated or displayed for NPIV devices, devices connected to AG-mode
switches, and devices connected to switches with firmware version lower than 8.0.1.
Because the algorithm to predict RoS is based on recent historical data, reporting for an IT
flow may start only after sufficient data has been gathered

Revision 1017 4 22
AMP200 Analytics Monitoring Platform Metrics Overview

Revision 1017 4 23
AMP200 Analytics Monitoring Platform Metrics Overview

You can determine Oversubscription based on a metric called Demand Rate. AMP gathers
data points to predict demand rate of an IT flow or an Initiator. The AMP logic will learn various
read IO profiles issued by the host and the corresponding data rates. For the current IO
profile, the demand rate will indicate the potential data rate of the flow if the host, target,
fabric, or other external factors does not have any bottleneck or limitations. You can determine
the over subscription type and extent of oversubscription by comparing the demand rate, data
rate, and link speed.
The percentage of RoS is the ratio between the demand rate and link speed. The Request-
over-Subscription state is calculated using the average demand rate per second and the host
port speed.

Revision 1017 4 24
AMP200 Analytics Monitoring Platform Metrics Overview

You can determine Oversubscription based on a metric called Demand Rate. AMP gathers
data points to predict demand rate of an IT flow or an Initiator. The AMP logic will learn various
read IO profiles issued by the host and the corresponding data rates. For the current IO
profile, the demand rate will indicate the potential data rate of the flow if the host, target,
fabric, or other external factors does not have any bottleneck or limitations. You can determine
the over subscription type and extent of oversubscription by comparing the demand rate, data
rate, and link speed.
The percentage of RoS is the ratio between the demand rate and link speed. The Request-
over-Subscription state is calculated using the average demand rate per second and the host
port speed.

Revision 1017 4 25
AMP200 Analytics Monitoring Platform Metrics Overview

You can determine Oversubscription based on a metric called Demand Rate. AMP gathers
data points to predict demand rate of an IT flow or an Initiator. The AMP logic will learn various
read IO profiles issued by the host and the corresponding data rates. For the current IO
profile, the demand rate will indicate the potential data rate of the flow if the host, target,
fabric, or other external factors does not have any bottleneck or limitations. You can determine
the over subscription type and extent of oversubscription by comparing the demand rate, data
rate, and link speed.
The percentage of RoS is the ratio between the demand rate and link speed. The Request-
over-Subscription state is calculated using the average demand rate per second and the host
port speed.

Revision 1017 4 26
AMP200 Analytics Monitoring Platform Metrics Overview

Revision 1017 4 27
AMP200 Analytics Monitoring Platform Metrics Overview

Footnote 1: In a common data-center environment, application-related data may need to be backed up in real time. Many of
the storage arrays that host these applications in the main data center, replicate the data to remote sites using synchronous
or asynchronous replication methods.
Footnote 2: Having visibility to all metrics from the host that runs the application, the storage port, and replication ports at
both sites helps to troubleshoot and resolve identified application latency
Diagram Description: The figure above shows two sites, local (Site A) and remote (Site B), connected over a WAN. The
AMP at Site A is connected to Monitored Switch 1 which has a storage array, Target 1, with replication ports attached to it.
The array has LUNs that need to be replicated to the remote site. The remote site has a storage array, Target 2, which is
connected to the remote Monitored Switch 2. Optionally, you can connect AMP to the remote site as well for visibility on
metrics for all flows on the remote storage ports. Both source Flow monitoring with data replication and destination switches,
as well as the AMP at Site A and at Site B, are managed by the same Brocade Network Advisor server. AMP supports
several data replication solutions.
Limitations:
The monitored switches must be running Fabric OS 7.4.1x, 8.0.1, or higher, and AMPs must be running AMP OS 2.0.1 or
higher.
The two sites must have Fibre Channel connectivity over a DWDM, dark fiber or FCIP network.
For Gen 6 directors, you can connect the replication ports to any blade.
For Gen 5 directors with FX8 extension blades, you must connect the replication ports to a Gen 5 blade and not to an FX8
extension blade.
The replication array ports must not be connected to a Brocade 7840 Extension Switch.
Other switches in the fabric can be running earlier versions of Fabric OS.
I/O and latency metrics for replication traffic flows are gathered, but only reads and writes are reported separately. Metrics
for all other commands are reported under the other (OTH) category.
Both control and data frames are treated alike. AMP does not perform any separation of or differentiate between control and
data frames

Revision 1017 4 28
AMP200 Analytics Monitoring Platform Metrics Overview

Revision 1017 4 29
AMP200 Analytics Monitoring Platform Management Overview

Revision 1017 5 1
AMP200 Analytics Monitoring Platform Management Overview

Revision 1017 5 2
AMP200 Analytics Monitoring Platform Management Overview

Footnote 1: Network Advisor 14.1 is also a requirement to manage switches running Fabric
OS 8.1.0
Network Advisor Professional Plus: a SAN management application designed for medium-
size businesses or departmental SANs for managing up to thirty-six physical or virtual fabrics
(FOS) and up to 2,560 switch ports. It supports Brocade director products (X6-4, DCX 8510-4,
and DCX-4S), FC switches, Fibre Channel Over IP (FCIP) switches, Fibre Channel Routing
(FCR) switches/ Integrated Routing (IR) capabilities, Fibre Channel over Ethernet (FCoE) /
DCB switches, and Qlogic and Emulex HBAs / CNAs, and Brocade Analytics Monitoring
Platform.
Network Advisor Enterprise: a management application designed for enterprise-class SANs
for managing up to one hundred physical or virtual fabrics and up to 15,000 switch ports.
Network Advisor SAN Enterprise supports all the hardware platforms and features that
Network Advisor Professional Plus supports, and adds support for the Brocade directors (X6-
8, DCX 8510-8, and DCX) and Fiber Connectivity (FICON) capabilities.
It is recommended that you run Brocade Network Advisor on a dedicated machine to avoid
conflicts with other applications that use the same resources and ports (such as SNMP, web
server, and so on).

Revision 1017 5 3
AMP200 Analytics Monitoring Platform Management Overview

Memory requirements are only applicable when there are no other applications running on the
Brocade Network Advisor server. Paging space should be equal to or exceed the physical
memory size.

Revision 1017 5 4
AMP200 Analytics Monitoring Platform Management Overview

Memory requirements are only applicable when there are no other applications running on the
Brocade Network Advisor server. Paging space should be equal to or exceed the physical
memory size.

Revision 1017 5 5
AMP200 Analytics Monitoring Platform Management Overview

Revision 1017 5 6
AMP200 Analytics Monitoring Platform Management Overview

These licenses are displayed with the licenseShow output:


AMP:FID128:admin> licenseshow
J7TELm3agQFRZYmBSrTQPaPETa9L7T9ZEZJfMHAZDa:
Analytics Upgrade license
Maximum Flows 20000
mTaHFCXKNFXTaXJKEPZS4LHa4HLGYNMB7tB:
Fabric Insight Portal Advanced Analytics Management license
This release has been restricted to advanced AMP-capabilities such as flow metrics
monitoring, collection, and aggregation to a single Network Advisor instance at a logical switch
level.
Licenses required for the monitored switches:
Trunking License
Fabric Vision license or its equivalent

Revision 1017 5 7
AMP200 Analytics Monitoring Platform Management Overview

It is recommended to use JRE version 1.8.0_101 to launch the remote client

Revision 1017 5 8
AMP200 Analytics Monitoring Platform Management Overview

Footnote 1: FCOE10-24, FX8-24, FS8-18, and FC8-64 blades in DCX8510-8/DCX8510-4 are


not supported for monitoring by Analytics Monitoring Platform

Revision 1017 5 9
AMP200 Analytics Monitoring Platform Management Overview

It is recommended to use JRE version 1.8.0_101 to launch the remote client

Revision 1017 5 10
AMP200 Analytics Monitoring Platform Management Overview

Footnote 1: Currently in the AMPOS 2.1 timeframe there is an implementation service


required.
The following are the default port details for the Monitor service:
Database port: 5433
Monitor service ports(jboss): 24700 through 24705
If you start, stop, or refresh the services after enabling the monitor in the Network Advisor
Server Management Console dialog box, the newly added Monitor Server and Monitor
Database Server display along with the list of services in the launch dialog boxes

Revision 1017 5 11
AMP200 Analytics Monitoring Platform Management Overview

Steps to bind an AMP device to a BNA server instance:


1. Discover a fabric, which has AMP connected and running AMP_OS version 2.0.0.
The Network Advisor server binds to the discovered AMP logical switch with the Fabric Insight
Portal AAM license.
2. Verify the Switch details view in Inventory to see if it is bound to the logical AMP.
The status in the Switch Properties displays the message, if binding fails. Network Advisor
receives a trap once the server IP is successfully bound with the AMP
To unbind the AMP using the CLI use the following command : mgmtapp --unbind

Revision 1017 5 12
AMP200 Analytics Monitoring Platform Management Overview

You must log into a Management application server to monitor the network. To launch a web
client, complete the following steps.
1. Open a web browser and enter the IP address or host name of the Management application
server in the Address bar.If the web server port number does not use the default (443 if is
SSL Enabled; otherwise, the default is 80), you must enter the web server port number in
addition to the IP address. For example, IP_Address:Port_Number.
The web client login page displays. You can launch the Java client from login page of the web
client by clicking Desktop Client.
You can download the client bundle (64-bit OS only), JRE, or MIB files by clicking JRE and
MIB files
2. Enter your user name and password. Do not enter Domain\User_Name in the User ID field
for LDAP server authentication
3. Press Enter or click Login.
NOTE:
If the Administrator disconnects the web client using the Active Sessions dialog box (Server >
Active Sessions), the web client redirects to the login page after three minutes or as soon as
you make a selection.

Revision 1017 5 13
AMP200 Analytics Monitoring Platform Management Overview

Revision 1017 5 14
AMP200 Analytics Monitoring Platform Management Overview

Footnote 1: A template (view) is a definition consisting of data widgets and their layout
Footnote 2: The Events page lists the events and alerts that have occurred on discovered
devices in your network as well as on the Management server. The Events page displays a
maximum of 5,000 events within the selected time scope
Footnote 3: Includes Filter and Collection Management:
Filter Management: Create and manage flow filters to filter the content.
Collection Management: Create and manage a group of flows with advance capabilities

Revision 1017 5 15
AMP200 Analytics Monitoring Platform Management Overview

Revision 1017 5 16
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 1
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 2
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 3
AMP200 Fabric Insight Portal Dashboard Overview

Footnote 1: A template (view) is a definition consisting of data widgets and their layout
Footnote 2: The Events page lists the events and alerts that have occurred on discovered
devices in your network as well as on the Management server. The Events page displays a
maximum of 5,000 events within the selected time scope
Footnote 3: Includes Filter and Collection Management:
Filter Management: Create and manage flow filters to filter the content.
Collection Management: Create and manage a group of flows with advance capabilities

Revision 1017 6 4
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 5
AMP200 Fabric Insight Portal Dashboard Overview

You must have the Dashboard Management privilege with read permission to view
dashboards.
You can only create and add customized widgets from the Java client.
Only devices in your area of responsibility (AOR) display in the dashboard
The Dashboard displays the status widgets and performance monitors. You can also display
additional status widgets and performance monitors, as needed. The Management application
has the following default dashboards: Analytics Summary and SAN Port Health.
The dashboard provides a high-level overview of the network and the current states of
managed devices. This allows you to easily check the status of the devices on the network.
The dashboard also provides several features to help you quickly access reports, device
configurations, and system event logs.
The dashboard refreshes the flow widgets every five minutes and refreshes the status and
performance widgets every 10 minutes regardless of the size of your network. Note that data
may become momentarily out of sync between the dashboard and other areas of the
application. For example, if you remove a product from the network while another user
navigates from the dashboard to a more detailed view of the product, the product may not
appear in the detailed view

Revision 1017 6 6
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 7
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 8
AMP200 Fabric Insight Portal Dashboard Overview

The Analytics Summary dashboard provides the following preconfigured status and performance widgets:
Flow - Summary Latency widget
Flow - Summary Performance widget
Top Initiator Target Flow Latency widget
Top Initiator Target Flow Performance widget
Top Port Flow Latency widget
Top Port Flow Performance widget
Port Violations widget
Analytics Health Violations widget
The SAN Ports Health dashboard provides the following preconfigured status and performance widgets for the
ISL, Host, and Target ports:
Top Port Utilization
Top Port Utilization Percentage
Bottom Port Utilization Percentage
Bottom Port Utilization
Top Port CRC Errors widget
Top Port Sync Losses widget
Top Port Link Failures widget
Top Port C3 Discards RX TO widget
Top Port Link Resets widget
Top Port PCS Block Errors widget

Revision 1017 6 9
AMP200 Fabric Insight Portal Dashboard Overview

To create a new template and use the pre-defined layout choose Select Widgets and then
populate your template by selecting and moving over chosen widgets into the right-hand pane
using the arrow function. Select OK and move to the Create Template dialog window and
then you need Save the template.

Revision 1017 6 10
AMP200 Fabric Insight Portal Dashboard Overview

The Save As operation allows you to modify an existing template in order to create a new
template (leaving the original template intact)

Revision 1017 6 11
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 12
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 13
AMP200 Fabric Insight Portal Dashboard Overview

The default network scope is All. It includes all managed and monitored fabrics or groups in
your AOR. You can display all objects in your area of responsibility (AOR) or a subset of
objects (fabrics, devices, or groups) using the network scope selection. If the selected fabric
or group is deleted from discovery, the widget refreshes and returns to the default network
scope (All).
You can also search for a product or fabric by entering search criteria in the Search field. The
Network Scope list automatically filters out any products that do not match the search criteria.
If you select a fabric scope, the dashboard widgets display data for all products and ports in
the fabric.
If you select a product scope, the dashboard widgets display data for the selected products
and the ports that belong to the selected products.
If you select a port scope, the dashboard widget display data for the specified ports and the
products to which the ports belong.
If any of the selected ports are initiator or target ports, the dashboard widgets display data for
the attached switch port

Revision 1017 6 14
AMP200 Fabric Insight Portal Dashboard Overview

Setting the global time interval in the Dashboards page configures the data display time
range for all the applicable widgets. Time interval in the Scope list allows you to select a
specific time range for which you want to display data in the Dashboards page.
The available time scopes include the following options:
30 Minutes Displays data for 30 minutes
1 Hour Displays data for 1 hour
6 Hours Displays data for 6 hours
12 Hours Displays data for 12 hours
1 Day Displays data for 24 hours
3 Days Displays data for 3 days
1 Week Displays data for 1 week
1 Month Displays data for 30 days

Revision 1017 6 15
AMP200 Fabric Insight Portal Dashboard Overview

Because you can manage up to 10 logical switches with total number of flows limiting to 100K
and 250K inactive flows filters are required to narrow down the scope of your template /
dashboard reporting. It is possible to add up to 5 different filters.

Revision 1017 6 16
AMP200 Fabric Insight Portal Dashboard Overview

Footnote 1: Any changes to the network scope, time scope and filters applied on the live
dashboard is applicable only for the current view in that user session which is not persisted
against the template. i.e If user navigates to another tab (say Inventory) and comes back to
Dashboard, the scopes and filters applied to dashboard is obtained from the template
preferences

Revision 1017 6 17
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 18
AMP200 Fabric Insight Portal Dashboard Overview

User can mark any one template as favorite by clicking on the Favorite icon.
The favorite template is displayed by default in the dashboard when the user logs into web
client. Once the user selects a different template and/or clicks on the Favorite icon, he has an
option to either apply the changes by clicking on OK button or cancel the operation by
clicking on Cancel button.
User can un-favorite a template by clicking on the highlighted icon

Revision 1017 6 19
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 20
AMP200 Fabric Insight Portal Dashboard Overview

Footnote 1: No pending IO metric available in this widget because there is a dedicated new default widget: Top Target
port pending IOs

Revision 1017 6 21
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 22
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 23
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 24
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 25
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 26
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 27
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 28
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 29
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 30
AMP200 Fabric Insight Portal Dashboard Overview

Revision 1017 6 31
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 71
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 72
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 73
AMP200 Fabric Insight Portal Filters and Flows Overview

Footnote 1: A template (view) is a definition consisting of data widgets and their layout
Footnote 2: The Events page lists the events and alerts that have occurred on discovered
devices in your network as well as on the Management server. The Events page displays a
maximum of 5,000 events within the selected time scope
Footnote 3: Includes Filter and Collection Management:
Filter Management: Create and manage flow filters to filter the content.
Collection Management: Create and manage a group of flows with advance capabilities

Revision 1017 74
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 75
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 76
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 77
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 78
AMP200 Fabric Insight Portal Filters and Flows Overview

Diagram Description:
Above are three Filter creation examples: ITL, Zone Alias and Attached Switch Port.
Filter types:
ITL - Creates a filter to display IT and ITL flows that belong to a specific Initiator or Target
ports or LUN field with an asterisk (*) specified. The filter will search for any of the initiators
that match with any of the specified targets.
ActiveZone - Creates a filter to display all flows that match the Active Zone name and LUN ID
specified from all fabrics.
Zone Alias - Creates a filter to display all flows that match the specified zone alias and LUN ID
specified from all fabrics.
Attached Switch Port - Creates a filter to display all flows that have the specified F-port and its
NPIVs (if any) as either initiator or target.

Revision 1017 79
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 7 10
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 7 11
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 7 12
AMP200 Fabric Insight Portal Filters and Flows Overview

The Network Flows page displays the flows listed in a table format displaying the Initiator,
Target, LUN, vTap, and Status columns as shown in the following figure. The Initiator, Target,
and vTap columns are displayed with the zone alias name when Zone Alias is configured or
the port name when a port is configured. It will display FC address or Port ID when Port name
or Zone Alias is not configured. You can launch Investigate Flow to view ITL's for an IT flow.
The page loads first 100 flow details and displays the remaining flows on scrolling further.
The Network Flows page refresh requires a manually refresh. This is not intended to be a
real-time monitoring page. Real time would be done using the Dashboard (setup your filters
to monitor your widgets).

Revision 1017 7 13
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 7 14
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 7 15
AMP200 Fabric Insight Portal Filters and Flows Overview

The Table includes the default Read and Write Metrics displayed.

Revision 1017 7 16
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 7 17
AMP200 Fabric Insight Portal Filters and Flows Overview

The total pending I/Os reflects the actual IT and ITL queue depth at the device. The total
pending IOs are reported at IT, ITL, and target levels. Statistics are shown for physical ports
only.

Revision 1017 7 18
AMP200 Fabric Insight Portal Filters and Flows Overview

Footnote 1: Beginning with AMP OS 2.1.0, more details on SCSI errors are available for
SCSI IO errors. These include:
ABTS
Timeouts
Check Condition
Condition met
Busy
Reservation conflict
Task set full
Auto cont align (ACA)
Task aborted

Revision 1017 7 19
AMP200 Fabric Insight Portal Filters and Flows Overview

Revision 1017 7 20
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 1
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 2
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 3
AMP200 Fabric Insight Portal Investigation Mode Overview

Footnote 1: A template (view) is a definition consisting of data widgets and their layout
Footnote 2: The Events page lists the events and alerts that have occurred on discovered
devices in your network as well as on the Management server. The Events page displays a
maximum of 5,000 events within the selected time scope
Footnote 3: Includes Filter and Collection Management:
Filter Management: Create and manage flow filters to filter the content.
Collection Management: Create and manage a group of flows with advance capabilities

Revision 1017 8 4
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 5
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 6
AMP200 Fabric Insight Portal Investigation Mode Overview

The Investigation Mode page displays the Measures pane on the left side and details of the
selected IT or ITL flows in a table format below the graph. You can investigate single or
multiple IT/ITL flows.
Investigation Mode for Multiple IT flows: When you launch multiple IT flows from
dashboard widgets, the Measures option on the left pane is auto-selected and the graph will
be plotted for the selected flows.
Investigation Mode for Single ITL flow: When launching the ITL flows, the Allow Multi
Select option is not applicable. The actions menu in the table will list Show all ITL's option to
view all related ITL flows that share the same initiator, target, and vTap. The Show All ITLs
page will become the default view to the user.
Investigation Mode for Multiple ITL flows: When launching the ITL flows, the Allow multi
select option is enabled by default. All the IT and ITL flows will be displayed at the same level
when Show all ITLs is selected.

Revision 1017 8 7
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 8
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 9
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 10
AMP200 Fabric Insight Portal Investigation Mode Overview

Diagram Description:
Flow Table
Based on the context of launch, the table lists either IT or ITL flows
Example, when launched from top collection widget; the table lists all the IT flows that are part of
that collection
Flows are sorted based on the metric in the context to enable user to easily pick the right flow to
investigate
This is applicable only when the launch origin has a metric context (from Dashboard widgets)
If there is no metric context , the table dynamically sorts the content based on the first measure
selected from the measures list
For all the IT flows, the expander reveals all the ITLs learned

Allow Multi Select


When selected, user can select multiple flows but only one metric from the measures table
Unselecting this option will allow user to select one flow against multiple metrics

Revision 1017 8 11
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 12
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 13
AMP200 Fabric Insight Portal Investigation Mode Overview

Chart Title - Displays the I and T of the flow selection


Comma separated values when multiple flows from different I, T are selected
It honors the naming chronology

Tool tip displayed when mouse hovers on the data block


Tooltip contains - Flow identifiers, Measure details, Series type (Max/Avg), Corresponding value
with its unit and Timestamp

Export chart can be exported as .png file

Revision 1017 8 14
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 15
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 16
AMP200 Fabric Insight Portal Investigation Mode Overview

Revision 1017 8 17
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 91
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 92
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 93
AMP200 Fabric Insight Portal Collections and MAPS Overview

Footnote 1: A template (view) is a definition consisting of data widgets and their layout
Footnote 2: The Events page lists the events and alerts that have occurred on discovered
devices in your network as well as on the Management server. The Events page displays a
maximum of 5,000 events within the selected time scope
Footnote 3: Includes Filter and Collection Management:
Filter Management: Create and manage flow filters to filter the content.
Collection Management: Create and manage a group of flows with advance capabilities

Revision 1017 94
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 95
AMP200 Fabric Insight Portal Collections and MAPS Overview

Collection management allows you to monitor flows with advance capabilities. For Fabric OS
devices, collection allows the administrator to configure a set of rules and actions to be taken
to meet the flows monitoring conditions. Collection allows you to create rules based on the
pre-defined measures and data size groupings automatically alerts you to problems with
notifications long before they get worse and become costly failures.

Revision 1017 96
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 97
AMP200 Fabric Insight Portal Collections and MAPS Overview

You must create a collection to display the data that you wish to view in the Management
application and activate the collection with a set of rules for all Brocade Analytics Platform
(AMP) switches. You can create Collections based on flows with the help of saved filters or
create your own flow by providing initiator, target and LUN details. Collection will be activated
on all managed AMP switches based on the set of rules being assigned to collections. You
can choose the aggregate option to aggregate the flows in collection and display in the
collection dashboard widgets. Collections created are user-specific and other users can view
the collections, but not allowed to edit the collections.
By default, if no collection is created or applied on a view, the Collection Management page
will be blank. It gets populated with data only if a collection is created and added
Save button:
Save will save the collection in BNA server and also deploy the collection to all the monitored
AMPs if there are rules associated. If collection do not have flows or rule set configured, it will
be saved to BNA alone

Revision 1017 98
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 99
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 10
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 11
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 12
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 13
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 14
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 15
AMP200 Fabric Insight Portal Collections and MAPS Overview

Maximum MAPS user defined rules supported are 500 per Logical AMP

Revision 1017 9 16
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 17
AMP200 Fabric Insight Portal Collections and MAPS Overview

User can also change the time scope to view Collection graph for the particular time
Note: Network Scope & Filters wont have any effect on the collection widgets

Each collection widget is provided with a measure type dropdown menu


User can either select one or more measures for a given collection widget
For a single collection in a widget, user can select up to 4 measures
On the other hand, up to 4 collections can be viewed in a single collection widget for a single
measure

Revision 1017 9 18
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 19
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 20
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 21
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 22
AMP200 Fabric Insight Portal Collections and MAPS Overview

What is MAPS:
An optional advanced SAN monitoring utility used to allow a switch to monitor itself for faults
Monitors fabric-wide events, ports, FRUs, and environmental parameters
Fabric measures and alert thresholds can be configured on a per-port or group basis
Provides enhanced monitoring
Monitoring the same error counter across two different time periods
Footnote 1: MAPS supports system level rules to prevent AMP from back-pressuring the
monitored switch. The system rule actions are triggered irrespective of the MAPS globally-
configured actions.

Revision 1017 9 23
AMP200 Fabric Insight Portal Collections and MAPS Overview

What is MAPS:
An optional advanced SAN monitoring utility used to allow a switch to monitor itself for faults
Monitors fabric-wide events, ports, FRUs, and environmental parameters
Fabric measures and alert thresholds can be configured on a per-port or group basis
Provides enhanced monitoring
Monitoring the same error counter across two different time periods
Footnote 1: MAPS supports system level rules to prevent AMP from back-pressuring the
monitored switch. The system rule actions are triggered irrespective of the MAPS globally-
configured actions.

Revision 1017 9 24
AMP200 Fabric Insight Portal Collections and MAPS Overview

Diagram Description:
The default policies (aggressive, moderate and conservative) assign rules to the Sys_mon_analytics
MAPS system group. Each default policy has rules that monitor specified measures for all flows being
sent to the AMP device. The default policies can cloned and customized for a particular production
environment. MAPS is managed using the thick client and is not managed on the Fabric Insight
Portal.

Revision 1017 9 25
AMP200 Fabric Insight Portal Collections and MAPS Overview

Note: Collections rules always override the sys_mon_analytics rules (either default or user defined)

Revision 1017 9 26
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 27
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 28
AMP200 Fabric Insight Portal Collections and MAPS Overview

Revision 1017 9 29
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Revision 1017 10 1
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Revision 1017 10 2
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Revision 1017 10 3
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Footnote 1: A template (view) is a definition consisting of data widgets and their layout
Footnote 2: The Events page lists the events and alerts that have occurred on discovered
devices in your network as well as on the Management server. The Events page displays a
maximum of 5,000 events within the selected time scope
Footnote 3: Includes Filter and Collection Management:
Filter Management: Create and manage flow filters to filter the content.
Collection Management: Create and manage a group of flows with advance capabilities

Revision 1017 10 4
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Revision 1017 10 5
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Revision 1017 10 6
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Ports Table:
Lists key attributes of the port: Status, Configured speed and the device (switch, AMP or end
device) connected
User can select multiple ports of same Type to Investigate the performance

Revision 1017 10 7
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Ports Table:
Lists key attributes of the port: Status, Configured speed and the device (switch, AMP or end
device) connected
User can select multiple ports of same Type to Investigate the performance

Revision 1017 10 8
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

You can investigate the Historical or Real-Time performance for selected fabric and port for a
selected time range. In this example, a single port has been selected from a fabric switch and
the Tx and Rx % Utilization measures selected. It is also possible to graph a single measure
for multiple ports by using the Multi-select option. On this current slide one would need to
change the Show option to ALL Ports instead of Selected Ports to have the multi-select
option appear.

Revision 1017 10 9
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Revision 1017 10 10
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Revision 1017 10 11
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Revision 1017 10 12
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Events are grouped into four categories


Alert
Maps to: Emergency, Alert & Critical
Error
Maps to Error
Warning
Maps to Warning
Info
Maps to Notice, Info & Debug

Event has more information than the most important fields listed in the events table
More details of particular event will be available by clicking on expand icon
Click on View Product Details link on the event details to launch the Product details page

Action Menu
View Fabric : Provides options to view the inventory view of fabric associated with the event
View Product : Directly launch the product details page from the events list

Revision 1017 10 13
AMP200 Fabric Insight Portal SAN Inventory and Event Overview

Revision 1017 10 14