Home/Catalog/BROCADE-CONTEXT-MAPPING-MIB

BROCADE-CONTEXT-MAPPING-MIB

AI MIB Summary

The BROCADE-CONTEXT-MAPPING-MIB manages SNMPv3 context names and community-to-context mappings on Brocade networking devices to isolate management data across Virtual Routing and Forwarding (VRF) instances. It enables granular access control by associating specific SNMP community strings with distinct logical contexts, ensuring that management information retrieval is restricted to the intended VRF scope.

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.
Main OID:
brocadeContextMappingMIB.1.3.6.1.4.1.1588.3.1.7
15
Objects
Active
Status
5
Dependencies

Imported Objects

Objects

15 total
Object Name
brocadeContextMappingMIBThis 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.
MODULE-IDENTITY
.1.3.6.1.4.1.1588.3.1.7
bContextMapMIBNotifs
OBJECT IDENTIFIER
.1.3.6.1.4.1.1588.3.1.7.0
bContextMapMIBObjects
OBJECT IDENTIFIER
.1.3.6.1.4.1.1588.3.1.7.1
bcmContexMapConfig
OBJECT IDENTIFIER
.1.3.6.1.4.1.1588.3.1.7.1.1
bcmContextMappingTableA 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.
SEQUENCE OF BcmContextMappingEntry
.1.3.6.1.4.1.1588.3.1.7.1.1.1
bcmContextMappingEntryA conceptual entry (row) of this table. Each entry represents a Context and has all the mapping information of the managed device.
BcmContextMappingEntry
.1.3.6.1.4.1.1588.3.1.7.1.1.1.1
bcmContextMappingVacmContextNameThe 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.
SnmpAdminString
.1.3.6.1.4.1.1588.3.1.7.1.1.1.1.1
bcmContextMappingVrfNameThis object specifies the VRF name mapped to this 'context'.ro
SnmpAdminString
.1.3.6.1.4.1.1588.3.1.7.1.1.1.1.2
bcmContextMappingStorageTypeThe storage type for this conceptual row. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.ro
StorageType (SNMPv2-TC)
.1.3.6.1.4.1.1588.3.1.7.1.1.1.1.3
bcmContextMappingRowStatusThis object facilitates the creation, modification or deletion of a conceptual row in this table.ro
RowStatus (SNMPv2-TC)
.1.3.6.1.4.1.1588.3.1.7.1.1.1.1.4
bContextMapMIBConform
OBJECT IDENTIFIER
.1.3.6.1.4.1.1588.3.1.7.2
brocadeContextMapMIBCompliances
OBJECT IDENTIFIER
.1.3.6.1.4.1.1588.3.1.7.2.1
brocadeContextMapMIBComplianceThe compliance statement for entities which implement BROCADE-CONEXT-MAPPING-MIB.
Unknown
.1.3.6.1.4.1.1588.3.1.7.2.1.1
brocadeContextMapMIBGroups
OBJECT IDENTIFIER
.1.3.6.1.4.1.1588.3.1.7.2.2
brocadeContextMapConfigGroupA collection of objects for the management of the Brocade SNMP context Mapping.
Unknown
.1.3.6.1.4.1.1588.3.1.7.2.2.1

More MIBs from Brocade

Browse all BrocadeMIBs →
SW-MIB

SW-MIB provides management and monitoring capabilities for Brocade Fibre Channel switches, exposing critical operational metrics such as port status, traffic counters, buffer credits, and fabric topology state. This module enables the collection of performance data and fault detection for storage area network (SAN) infrastructure via SNMP.

249 objects→
BROCADE-SYSTEM-MIB

The BROCADE-SYSTEM-MIB provides standard SNMP access to Brocade Fibre Channel and Ethernet switch system-level attributes, including device identity, hardware status, environmental sensors, and operational counters. It enables centralized monitoring of critical infrastructure health metrics such as temperature, fan status, power supply states, and system uptime across the Brocade SAN and LAN fabric.

82 objects→
LINK-INCIDENT-MIB

The LINK-INCIDENT-MIB module monitors FICON link incident and failure events for host and device connections to Brocade Fibre Channel switches within Fabos environments. It provides specific counters and status indicators to track link stability and fault conditions for FICON traffic traversing the switch fabric.

81 objects→
BROCADE-MPLS-MIB

The BROCADE-MPLS-MIB enables monitoring and management of Multi-Protocol Label Switching (MPLS) operational states and traffic statistics on Extreme Networks (formerly Brocade) routing platforms. It provides access to specific metrics including MPLS label forwarding table entries, LSP (Label Switched Path) status, and associated interface counters for troubleshooting label-switched network performance.

65 objects→
BROCADE-TMSTATS-MIB

The BROCADE-TMSTATS-MIB module provides SNMP access to performance counters and operational statistics for Brocade Traffic Manager (TM) hardware and software components, specifically monitoring data plane throughput, packet processing rates, buffer utilization, and traffic flow metrics.

53 objects→
BROCADE-ACL-MIB

The BROCADE-ACL-MIB enables SNMP-based configuration and monitoring of Access Control List (ACL) policies on Brocade Fibre Channel and Ethernet switches, specifically tracking rule definitions, hit counts, and packet drop statistics to enforce network segmentation and security.

49 objects→