H3C-MDC-MIB

All MIBs › H3C-MDC-MIB

Organization: Hangzhou H3C Tech. Co., Ltd.

Last Updated: 2013-03-05

Category: Device Management, Vendor: H3C/HH3C

Description: H3C MIB for Multi-Device Context (MDC) managing logical device partitions on H3C chassis-based systems.

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 H3C-MDC-MIB?

H3C-MDC-MIB is an H3C-specific MIB for managing Multitenant Device Context (MDC) on H3C chassis-based systems, a virtualization feature that partitions a single physical device into multiple logical devices each with its own allocated resources. It exposes the maximum and current number of MDCs supported/configured, a control table for creating, naming, and managing the lifecycle (action, status, row status) of each MDC, and a resource table tracking disk-resource allocation per MDC. This is chiefly a software/resource-status monitoring MIB: administrators use it to confirm how many logical device contexts exist, whether each MDC is active/healthy (h3cMDCStatus), and whether allocated disk resources per MDC are within expected bounds, relating to hardware-resource-partitioning status rather than raw physical sensor data. It has no stated formal MIB import dependency, being a self-contained H3C proprietary virtualization feature, though it interacts conceptually with interface/CPU/memory resource assignment elsewhere on the device. It is typically deployed on H3C chassis-based core switches/routers used as a multi-tenant or multi-role platform consolidating several logical devices onto one physical chassis, and administrators can download the H3C-MDC-MIB file to load into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in H3C-MDC-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

H3C chassis-based core switches/routers (multi-tenant/MDC-capable platforms)

Monitoring Examples

Polling h3cMDCControlTable / h3cMDCControlEntry indexed by h3cMDCIndex shows each MDC's h3cMDCName and h3cMDCStatus, letting an admin confirm a given logical device context is running normally. Comparing h3cMDCCurrentMDCNum against h3cMDCMaxMDCNum shows how much MDC capacity remains before the chassis limit is reached. h3cMDCDISKResourceTable / h3cMDCDISKResourceEntry (h3cMDCDISKResourceInstance) reveals disk-resource allocation per MDC, useful for spotting an MDC running low on assigned storage.

What Can Be Monitored

number of configured vs. maximum MDCs
per-MDC status
per-MDC disk resource allocation
MDC creation/action state

Imported Objects

From ENTITY-MIB

entPhysicalIndex

OBJECT-TYPE

From HUAWEI-3COM-OID-MIB

h3cCommon

OBJECT-IDENTITY

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
RowStatus
TEXTUAL-CONVENTION
TruthValue

OIDs

OID symbolic	OID numeric	Type	Access	Description
h3cMDC	1.3.6.1.4.1.2011.10.2.136			This MIB contains objects to manage MDC (Multitenant Device Context) operations. Such as: 1. Configure MDCs for a device and display MDCs and their status. 2. Assign CPU, storage space, and memory space resources to the MDC, and display their status. 3. Authorize the MDC to use the interface cards, and assign physical interfaces to an MDC. Default MDC: A device supporting MDCs is an MDC itself, and it is called the default MDC. From the default MDC, administrators can manage the entire physical device, create and delete non-default MDCs, and assign interfaces, CPU resources, storage space, and memory space to non-default MDCs. Non-default MDC: No MDCs can be created on a non-default MDC. Administrators of non-default MDCs can only manage and maintain their respective MDCs. A non-default MDC can use only the resources assigned to it.
h3cMDCScalarObjects	1.3.6.1.4.1.2011.10.2.136.1
I32 h3cMDCMaxMDCNum	1.3.6.1.4.1.2011.10.2.136.1.1	Integer32	read-only	The maximum number of MDCs which the system supported to create.
I32 h3cMDCCurrentMDCNum	1.3.6.1.4.1.2011.10.2.136.1.2	Integer32	read-only	The current number of MDCs which the system has created.
h3cMDCTables	1.3.6.1.4.1.2011.10.2.136.2
h3cMDCControl	1.3.6.1.4.1.2011.10.2.136.2.1
h3cMDCControlTable	1.3.6.1.4.1.2011.10.2.136.2.1.1		not-accessible	This table is used to configure MDCs for a device and show MDC's status.
h3cMDCControlEntry	1.3.6.1.4.1.2011.10.2.136.2.1.1.1		not-accessible	An entry of the h3cMDCControlTable, every entry is corresponding with an MDC.
I32 h3cMDCIndex	1.3.6.1.4.1.2011.10.2.136.2.1.1.1.1	Integer32	accessible-for-notify	MDC ID is used as MDCIndex, the value range of MDC ID depends on the device model. MDCIndex cannot be modified after creation.
STR h3cMDCName	1.3.6.1.4.1.2011.10.2.136.2.1.1.1.2	DisplayString	read-create	Specifies the MDC name, a case-sensitive string of 1 to 15 characters. The MDC name cannot be modified after creation.
H3C h3cMDCAction	1.3.6.1.4.1.2011.10.2.136.2.1.1.1.3	H3cMdcActionValue	read-write	State of MDC action: start/stop. After an MDC is started, administrators of the MDC can log in to the MDC for MDC configuration and maintenance. Stopping an MDC interrupts all services on the MDC and logs out all users of the MDC. Non-default MDC cannot operate.
H3C h3cMDCStatus	1.3.6.1.4.1.2011.10.2.136.2.1.1.1.4	H3cMdcRunStatus	read-only	Status of MDCs.
ROW h3cMDCRowStatus	1.3.6.1.4.1.2011.10.2.136.2.1.1.1.5	RowStatus	read-create	The status of this table entry. Only support active, createAndGo and destroy.
h3cMDCResource	1.3.6.1.4.1.2011.10.2.136.2.2
h3cMDCDISKResourceTable	1.3.6.1.4.1.2011.10.2.136.2.2.1		not-accessible	This table is for disk resource management: Specify a disk space percentage for an MDC and display the disk space usage. Default: All MDCs share the disk space in the system, and an MDC can use all free disk space in the system. Non-default MDC can only query the disk space usage.
h3cMDCDISKResourceEntry	1.3.6.1.4.1.2011.10.2.136.2.2.1.1		not-accessible	An entry of the h3cMDCDISKResourceTable, every entry is corresponding to disk resource of an MDC. Note that only entPhysicalIndex values that represent physical boards (i.e., associated entPhysicalClass value is 'module(9)') are permitted to exist in this table.
I32 h3cMDCDISKResourceInstance	1.3.6.1.4.1.2011.10.2.136.2.2.1.1.1	Integer32	not-accessible	Instance index of disk resource. Different instances for disk: Flash, CF cards.
STR h3cMDCDISKResourceInstanceName	1.3.6.1.4.1.2011.10.2.136.2.2.1.1.2	DisplayString	read-only	Instance name of disk resource. Such as: Flash, CF cards.
I32 h3cMDCDISKResourceMinLimit	1.3.6.1.4.1.2011.10.2.136.2.2.1.1.3	Integer32	read-write	Limit minimum (reserve resources, must be all 0).
I32 h3cMDCDISKResourceMaxLimit	1.3.6.1.4.1.2011.10.2.136.2.2.1.1.4	Integer32	read-write	Maximum of available resources of disk. Make sure the disk space amount assigned to an MDC is greater than the disk space amount the MDC is using. Non-default MDC cannot set
U32 h3cMDCDISKResourceReserve	1.3.6.1.4.1.2011.10.2.136.2.2.1.1.5	Unsigned32	read-only	The reserve limit resources of disk.
U32 h3cMDCDISKResourceQuota	1.3.6.1.4.1.2011.10.2.136.2.2.1.1.6	Unsigned32	read-only	The total limit resources of disk according to h3cMDCDiskResourceMaxLimit.
U32 h3cMDCDISKResourceUsage	1.3.6.1.4.1.2011.10.2.136.2.2.1.1.7	Unsigned32	read-only	Current usage of disk resources.
U32 h3cMDCDISKResourceAvailable	1.3.6.1.4.1.2011.10.2.136.2.2.1.1.8	Unsigned32	read-only	Current available resources of disk.
h3cMDCMemoryResourceTable	1.3.6.1.4.1.2011.10.2.136.2.2.2		not-accessible	This table is for memory resource management: Specify a memory space percentage for an MDC and display the memory space usage. Default: All MDCs share the memory space in the system, and an MDC can use all free memory. Non-default MDC can only query resource message of memory.
h3cMDCMemoryResourceEntry	1.3.6.1.4.1.2011.10.2.136.2.2.2.1		not-accessible	An entry of the h3cMDCMemoryResourceTable, every entry is corresponding with memory resource of an MDC. Note that only entPhysicalIndex values that represent physical boards (i.e., associated entPhysicalClass value is 'module(9)') are permitted to exist in this table.
I32 h3cMDCMemoryResourceMinLimit	1.3.6.1.4.1.2011.10.2.136.2.2.2.1.1	Integer32	read-write	Limit minimum(reserve resources, must be all 0). Non-default MDC cannot set.
I32 h3cMDCMemoryResourceMaxLimit	1.3.6.1.4.1.2011.10.2.136.2.2.2.1.2	Integer32	read-write	Maximum of available resources of memory, it specifies the ratio of the memory space that an MDC can use. Make sure this amount is sufficient for the MDC to operate properly. Non-default MDC cannot set.
U32 h3cMDCMemoryResourceReserve	1.3.6.1.4.1.2011.10.2.136.2.2.2.1.3	Unsigned32	read-only	The reserve limit resources of memory.
U32 h3cMDCMemoryResourceQuota	1.3.6.1.4.1.2011.10.2.136.2.2.2.1.4	Unsigned32	read-only	The total limit resources of memory.
U32 h3cMDCMemoryResourceUsage	1.3.6.1.4.1.2011.10.2.136.2.2.2.1.5	Unsigned32	read-only	Current usage of memory resources.
U32 h3cMDCMemoryResourceAvailable	1.3.6.1.4.1.2011.10.2.136.2.2.2.1.6	Unsigned32	read-only	Current available value of memory resources.
h3cMDCCPUResourceTable	1.3.6.1.4.1.2011.10.2.136.2.2.3		not-accessible	This table is for CPU resource management: Specify a CPU weight for an MDC and display the CPU usage. The amount of CPU resources an MDC can use depends on the CPU weight settings for all MDCs that share the same CPU. Non-default MDC can only query CPU resources.
h3cMDCCPUResourceEntry	1.3.6.1.4.1.2011.10.2.136.2.2.3.1		not-accessible	An entry of the h3cMDCCPUResourceTable, every entry is corresponding with CPU resources of an MDC. Note that only entPhysicalIndex values that represent physical boards (i.e., associated entPhysicalClass value is 'module(9)') are permitted to exist in this table.
I32 h3cMDCCPUResourceLimit	1.3.6.1.4.1.2011.10.2.136.2.2.3.1.1	Integer32	read-write	CPU weight-maximum of available resources of CPU, this number specifies a CPU weight for an MDC. Non-default MDC cannot set.
I32 h3cMDCCPUResourceUsage	1.3.6.1.4.1.2011.10.2.136.2.2.3.1.2	Integer32	read-only	the CPU usage
h3cMDCLocation	1.3.6.1.4.1.2011.10.2.136.2.3
h3cMDCLocationTable	1.3.6.1.4.1.2011.10.2.136.2.3.1		not-accessible	This table is for location management: Authorize an MDC to use an interface card and query state of location. To assign physical interfaces to an MDC, administrators must authorize the MDC to use the interface cards to which the physical interfaces belong. Default: All interface cards of the device belong to the default MDC, and a non-default MDC cannot use any interface card. Non-default MDC can only query location state.
h3cMDCLocationEntry	1.3.6.1.4.1.2011.10.2.136.2.3.1.1		not-accessible	An entry of the h3cMDCLocationTable, every entry is the status whether an MDC has been Authorized to use the interface cards. Note that only entPhysicalIndex values that represent physical boards (i.e., associated entPhysicalClass value is 'module(9)') are permitted to exist in this table.
T/F h3cMDCLocationStatus	1.3.6.1.4.1.2011.10.2.136.2.3.1.1.1	TruthValue	read-write	To authorize the MDC to use the interface cards, set the value of this object to 'true (1)'. To cancel the authorization, set this value to 'false (2)'. Note that the return noError means the command is being executed. For the execution result, check h3cMDCLocationStatus.
h3cMDCAllocate	1.3.6.1.4.1.2011.10.2.136.2.4
h3cMDCGroupIfTable	1.3.6.1.4.1.2011.10.2.136.2.4.1		not-accessible	This table indication of relation between interfaces and groups, which helps to realize the allocation, together with h3cMDCAllocateTable. Non-default MDC cannot operate.
h3cMDCGroupIfEntry	1.3.6.1.4.1.2011.10.2.136.2.4.1.1		not-accessible	An entry of the h3cMDCGroupIfTable, every entry is the relationship between interfaces and groups. Due to hardware restrictions, the interfaces on some interface cards are grouped. The interfaces in a group must be assigned to the same MDC at the same time or removed from an MDC at the same time. Interface grouping depends on the device model. This table is used for h3cMDCAllocateTable to show interfae group lists. Note that only entPhysicalIndex values that represent physical ports (i.e., associated entPhysicalClass value is 'port(10)') are permitted to exist in this table.
I32 h3cMDCGroupIdentity	1.3.6.1.4.1.2011.10.2.136.2.4.1.1.2	Integer32	read-only	The interface group ID. There are two parts for this id depicted as follows: 31 7 0 +++++++++++++++++++++++++++++++++++++++++ + entity index + group index + + ( bit 8..31 ) ( bit 0..7 ) + +++++++++++++++++++++++++++++++++++++++++ From bit0 to bit7 (one byte), it is interfaces group index. From bit8 to bit31 (three bytes), it is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. Note that only entPhysicalIndex values that represent physical boards (i.e., associated entPhysicalClass value is 'module(9)') are permitted to exist in this table.
h3cMDCAllocateTable	1.3.6.1.4.1.2011.10.2.136.2.4.2		not-accessible	This table is used to assigning a physical interface to an MDC. It is allowed that allocate interfaces to a non-default MDC from the default MDC, and allocate interfaces back to the default MDC from a non-default MDC. All physical interfaces on the device belong to the default MDC, and a non-default MDC has no physical interfaces to use. Multiple physical interfaces can be assigned to a non-default MDC. A physical interface must meet the following conditions to be assigned to a non-default MDC: 1. Belongs to the default MDC. 2. Not the console or AUX port. 3. Not the management Ethernet interface. 4. Not in an interface group with an interface assigned to another MDC. 5. The default MDC uses only the physical interfaces that are not assigned to a non-default MDC. Non-default MDC cannot set this table.
h3cMDCAllocateEntry	1.3.6.1.4.1.2011.10.2.136.2.4.2.1		not-accessible	An entry of the h3cMDCAllocateTable, every entry is the status whether physical interfaces have been assigned to an MDC.
I32 h3cMDCAllocateGroupIndex	1.3.6.1.4.1.2011.10.2.136.2.4.2.1.1	Integer32	not-accessible	The interface group ID, the same as h3cMDCGroupIdentity. There are two parts for this id. depicted as follows: 31 7 0 +++++++++++++++++++++++++++++++++++++++++ + entity index + group index + + ( bit 8..31 ) ( bit 0..7 ) + +++++++++++++++++++++++++++++++++++++++++ From bit0 to bit7 (one byte), it is interfaces group index. From bit8 to bit31 (three bytes), it is the physical index the same as the entPhysicalIndex specified in ENTITY-MIB. Note that only entPhysicalIndex values that represent physical boards (i.e., associated entPhysicalClass value is 'module(9)') are permitted to exist in this table.
STR h3cMDCAllocateGroupDescription	1.3.6.1.4.1.2011.10.2.136.2.4.2.1.2	DisplayString	read-only	Interfaces list Such as: GigabitEthernet4/5/0/1 to GigabitEthernet4/5/0/24, GigabitEthernet4/5/0/48
I32 h3cMDCAllocateMDCId	1.3.6.1.4.1.2011.10.2.136.2.4.2.1.3	Integer32	read-write	MDC ID is used as h3cMDCAllocateMDCId. Default MDC: It is allowed that allocate interfaces to non-default MDC from the default MDC, and allocate interfaces back to the default MDC from a non-default MDC. Non-default MDC cannot set allocation, can only query grouping of own MDC.
h3cMDCNotification	1.3.6.1.4.1.2011.10.2.136.3
h3cMDCNotificationObjects	1.3.6.1.4.1.2011.10.2.136.3.0
NTF h3cMDCStateChangeToActive	1.3.6.1.4.1.2011.10.2.136.3.0.1			The h3cMDCStateChangeToActive trap indicates that the MDC status has changed to active.
NTF h3cMDCStateChangeToInactive	1.3.6.1.4.1.2011.10.2.136.3.0.2			The h3cMDCStateChangeToInactive trap indicates that the MDC status has changed to inactive.

RFC description

H3C Multitenant Device Context (MDC) management for device partitioning, CPU allocation, and resource assignment.

Start monitoring H3C chassis-based core switch/router (Multitenant Device Context) 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 H3C-MDC-MIB

What Is H3C-MDC-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description