BROCADE-MAPS-MIB

All MIBs › BROCADE-MAPS-MIB

Organization: Brocade Communications Systems, Inc.,

Last Updated: 2013-04-22

Category: Fibre Channel and Storage, Vendor: Foundry/Brocade

Description: Manages MAPS (Monitoring and Alerting Policy Suite) threshold policies on Brocade SAN switches.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is BROCADE-MAPS-MIB?

BROCADE-MAPS-MIB is a Brocade Communications Systems proprietary MIB for the Monitoring and Alerting Policy Suite (MAPS), a Fibre Channel SAN health-monitoring framework built into Brocade FOS switches. It exposes MAPS rule configuration objects — rule name, trigger condition, associated monitoring-system (category) name, the object being measured (group/key type and value), and the rule's current measured value and time base. As a configuration/performance MIB it lets an administrator confirm which MAPS rules are defined and read their currently-measured values, complementing MAPS's own notification/dashboard alerting. It is deployed on Brocade Fibre Channel SAN switches and directors running FOS with MAPS enabled. Engineers can download the BROCADE-MAPS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BROCADE-MAPS-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Brocade Fibre Channel SAN switches/directors (FOS with MAPS)

Monitoring Examples

An administrator checks mapsConfigCurrentValue against mapsConfigCondition for a rule monitoring port CRC errors to confirm how close a port currently is to triggering a MAPS alert.

What Can Be Monitored

MAPS rule configuration and current measured value

Imported Objects

From Brocade-REG-MIB

bcsiModules

OBJECT-IDENTITY

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

From SW-MIB

swVfId

OBJECT-TYPE

OIDs

OID symbolic	OID numeric	Type	Access	Description
maps	1.3.6.1.4.1.1588.3.1.4			The MIB module is for Brocade's Monitoring and Alerting Policy Suite[MAPS] feature.
mapsTraps	1.3.6.1.4.1.1588.3.1.4.0			The OID represents the MAPS Trap.
NTF mapsTrapAM	1.3.6.1.4.1.1588.3.1.4.0.1			Trap to be send for MAPS threshold events.
mapsConfig	1.3.6.1.4.1.1588.3.1.4.1			The OID represents the MAPS Config params.
OCT mapsConfigRuleName	1.3.6.1.4.1.1588.3.1.4.1.1	OCTET STRING	read-only	It indicates the rule name which associates a condition with actions that need to be triggered when the specified condition is evaluated to true.
OCT mapsConfigCondition	1.3.6.1.4.1.1588.3.1.4.1.2	OCTET STRING	read-only	It indicates the condition defined in the rule. It includes the counter, time base and threshold value with the logical operation (eg: >, = etc) that needs to be evaluated. Eg: (CRC/MIN > 10)
I32 mapsConfigNumOfMS	1.3.6.1.4.1.1588.3.1.4.1.3	Integer32	read-only	It indicates the number of monitoring system entries in the notifications
OCT mapsConfigMsName	1.3.6.1.4.1.1588.3.1.4.1.4	OCTET STRING	read-only	This is monitoring system name like CRC, ITW, PS, FAN.
INT mapsConfigObjectGroupType	1.3.6.1.4.1.1588.3.1.4.1.5	INTEGER	read-only	It indicates the object group type like circuit, PS, FAN.
INT mapsConfigObjectKeyType	1.3.6.1.4.1.1588.3.1.4.1.6	INTEGER	read-only	It indicates the object key type. The main purpose of this object to help NMS applications to interpret the data easily. Eg: If the mapsConfigObjectGroupType is port then the key type is an integer and key value is the port number.
OCT mapsConfigObjectKeyValue	1.3.6.1.4.1.1588.3.1.4.1.7	OCTET STRING	read-only	It indicates the object key value. Incase of integer this field keeps as 1, 2, 3, 4, etc., and for string it keeps flowname1, flowname2, etc., Eg: if Group type is port, then the object key value is the port number.
INT mapsConfigValueType	1.3.6.1.4.1.1588.3.1.4.1.8	INTEGER	read-only	It indicates the value type which could be integer, float or string. The main purpose of this object to help NMS applications to interpret the data easily.
OCT mapsConfigCurrentValue	1.3.6.1.4.1.1588.3.1.4.1.9	OCTET STRING	read-only	It indicates the actual value of the monitoring system.
OCT mapsConfigTimeBase	1.3.6.1.4.1.1588.3.1.4.1.10	OCTET STRING	read-only	The time period across which the change in a counter is to be monitored
INT mapsConfigSeverityLevel	1.3.6.1.4.1.1588.3.1.4.1.11	INTEGER	read-only	It indicates the severity level of the condition triggered
OCT mapsConfigMsList	1.3.6.1.4.1.1588.3.1.4.1.12	OCTET STRING	read-only	It indicates the list of the monitoring systems. The format is ,,, ::,,,::.
I32 mapsConfigAction	1.3.6.1.4.1.1588.3.1.4.1.13	Integer32	read-only	It indicates the actions(bitmask value) that need to be triggered when the specified condition evaluated to be true. Action bitmask value mapping are none (0), raslog (1), snmp (2), port-fence (8), email (16), switchstatus-down (64), switchstatus-marginal (128), switchstatus-healthy (256), switchpolicy (512), sfp-marginal (1024) Ex: mapsConfigAction value 3 represents both raslog and snmp action
OCT mapsDbCategory	1.3.6.1.4.1.1588.3.1.4.1.14	OCTET STRING	read-only	indicates db category name

RFC description

Brocade Monitoring and Alerting Policy Suite (MAPS) configuration for condition monitoring and alert rules.

Start monitoring Brocade Fibre Channel SAN switches/directors (FOS with MAPS) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download BROCADE-MAPS-MIB

What Is BROCADE-MAPS-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description