BROCADE-CONTEXT-MAPPING-MIB

All MIBs › BROCADE-CONTEXT-MAPPING-MIB

Organization: Brocade Communications Systems, Inc.

Last Updated: 2015-06-18

Category: Vendor: Foundry/Brocade

Description: Maps SNMP context identifiers to virtual routing instances on Brocade network devices.

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-CONTEXT-MAPPING-MIB?

BROCADE-CONTEXT-MAPPING-MIB is a Brocade enterprise MIB that manages how SNMP contexts map to virtual routing/forwarding (VRF) instances on Brocade network devices. It exposes a mapping table linking each SNMP context name (used for VACM access control) to a corresponding VRF name, along with row status and storage type for each mapping entry. Its monitoring value is largely configuration-oriented, letting an admin verify that SNMP context-to-VRF associations are correctly provisioned so that management queries reach the intended virtual routing instance, rather than exposing hardware health data itself. It depends on the standard SNMP-FRAMEWORK-MIB/VACM model for the context concept it is extending. It is deployed on Brocade (now Extreme Networks/Ruckus-lineage) routers and switches that support multiple VRFs needing per-context SNMP access. Engineers can download the BROCADE-CONTEXT-MAPPING-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in BROCADE-CONTEXT-MAPPING-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 router or switch
multi-VRF capable network device

Monitoring Examples

An operator can walk bcmContextMappingTable/bcmContextMappingEntry to confirm each bcmContextMappingVacmContextName correctly resolves to the intended bcmContextMappingVrfName, catching misconfigured context-to-VRF bindings that would otherwise cause SNMP polls to hit the wrong routing instance. The bcmContextMappingRowStatus column shows whether a given mapping entry is active, notInService, or being created/destroyed. This MIB is configuration-focused rather than a fault/performance MIB, so its main monitoring use is validating SNMP context provisioning.

What Can Be Monitored

SNMP context to VRF mapping
context mapping row status
context mapping storage type

Imported Objects

From Brocade-REG-MIB

bcsiModules

OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus
StorageType

OIDs

OID symbolic	OID numeric	Type	Access	Description
brocadeContextMappingMIB	1.3.6.1.4.1.1588.3.1.7			This MIB module is for the management of the SNMP context in the Brocade managed entities. An SNMP context, or just 'context' for short, is a collection of management information accessible by an SNMP entity. An item of management information may exist in more than one context. An SNMP entity potentially has access to many contexts. While SNMP context itself is generically defined to cater to the access of multiple instances of the MIB modules and management information, it is required to define what 'context' means for a given managed entity. This MIB module provides the management of such context. As technology evolves, the definition of the context can evolve and hence such definition should be extensible. The context referred in this management module is same as 'contextName' as defined in the SNMPv3 PDU and also maps to the 'snmpCommunityContextName' of snmpCommunityTable in 'SNMP-COMMUNITY-MIB'. The rest of the elements of procedure described for processing SNMP PDU remains the same. Glossary of the terms used in this MIB: -------------------------------------- SNMP Context - Name of the SNMP context name used in SNMPv3 PDU/SNMPv2 community mapping. VRF - Virtual Routing and Forwarding.
bContextMapMIBNotifs	1.3.6.1.4.1.1588.3.1.7.0
bContextMapMIBObjects	1.3.6.1.4.1.1588.3.1.7.1
bcmContexMapConfig	1.3.6.1.4.1.1588.3.1.7.1.1
bcmContextMappingTable	1.3.6.1.4.1.1588.3.1.7.1.1.1		not-accessible	A tabe that provides the mapping of SNMP context represented by the value of (vacmContextName) to the various entities within the entities within the managed device.
bcmContextMappingEntry	1.3.6.1.4.1.1588.3.1.7.1.1.1.1		not-accessible	A conceptual entry (row) of this table. Each entry represents a Context and has all the mapping information of the managed device.
STR bcmContextMappingVacmContextName	1.3.6.1.4.1.1588.3.1.7.1.1.1.1.1	SnmpAdminString	not-accessible	The vacmContextName given to the SNMP context. This is a human readable name identifying a particular SNMP VACM context at a particular SNMP entity. The empty contextName (zero length) represents the default context.
STR bcmContextMappingVrfName	1.3.6.1.4.1.1588.3.1.7.1.1.1.1.2	SnmpAdminString	read-only	This object specifies the VRF name mapped to this 'context'.
STO bcmContextMappingStorageType	1.3.6.1.4.1.1588.3.1.7.1.1.1.1.3	StorageType	read-only	The storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.
ROW bcmContextMappingRowStatus	1.3.6.1.4.1.1588.3.1.7.1.1.1.1.4	RowStatus	read-only	This object facilitates the creation, modification or deletion of a conceptual row in this table.
bContextMapMIBConform	1.3.6.1.4.1.1588.3.1.7.2
brocadeContextMapMIBCompliances	1.3.6.1.4.1.1588.3.1.7.2.1
brocadeContextMapMIBCompliance	1.3.6.1.4.1.1588.3.1.7.2.1.1			The compliance statement for entities which implement BROCADE-CONEXT-MAPPING-MIB.
brocadeContextMapMIBGroups	1.3.6.1.4.1.1588.3.1.7.2.2
brocadeContextMapConfigGroup	1.3.6.1.4.1.1588.3.1.7.2.2.1			A collection of objects for the management of the Brocade SNMP context Mapping.

RFC description

Vendor-private MIB for Brocade SAN switches; manages VF (Virtual Fabric) context mapping and logical domain isolation.

Start monitoring Brocade routers/switches (multi-VRF) 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-CONTEXT-MAPPING-MIB

What Is BROCADE-CONTEXT-MAPPING-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description