Integrating Broadcom Flow Vision Rules with MAPS
Sound monitoring and syslogging practices are the first and sometimes most important step in troubleshooting. They also the most overlooked as they must be configured before a problem happens. If system logging is not configured before a problem happens, valuable information is lost.
Broadcom has two important features that you can use to monitor the health of your Broadcom fabrics and alert you when problems are detected: Flow Vision (the monitoring) and Monitoring And Alerting Policy Suite (MAPS), which can both monitor and alert if it detects error conditions. In this post I'll provide a brief overview of each feature and then we'll see how we can integrate Flow Vision into MAPs to provide a comprehensive monitoring and alerting solution.
- Flows through the fabric for virtual machines or standalone hosts connected via NPIV that start from from a single N_Port ID (PID) to destination targets.
- Flows monitoring inside logical fabrics and inter-fabric (routed) traffic passing through
- Gaining insights into application performance through the capture of statistics for specified flows.
- Monitoring various frame types at a switch port to provide deeper insights into storage I/O access such as the various SCSI commands
Integrating Flow Vision with MAPs
Step 1: Create the flow:
Step 3: Verify the Flow has been imported
|Host1_ABTS|||No|||Port |3|||Monitored Flow|