H3C-MDC-MIB
AI MIB Summary
The H3C-MDC-MIB module manages H3C device multitenancy by monitoring and configuring default and non-default Multitenant Device Contexts, specifically tracking allocated CPU, memory, and storage resources alongside physical interface assignments and context operational status.
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.
Main OID:
h3cMDC.1.3.6.1.4.1.2011.10.2.136
53
Objects
Active
Status
4
Dependencies
Imported Objects
Objects
53 total| Object Name |
|---|
h3cMDCThis 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. MODULE-IDENTITY .1.3.6.1.4.1.2011.10.2.136 |
h3cMDCScalarObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.136.1 |
h3cMDCMaxMDCNumThe maximum number of MDCs which the system supported to create.ro Integer32 .1.3.6.1.4.1.2011.10.2.136.1.1 |
h3cMDCCurrentMDCNumThe current number of MDCs which the system has created.ro Integer32 .1.3.6.1.4.1.2011.10.2.136.1.2 |
h3cMDCTables OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.136.2 |
h3cMDCControl OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.136.2.1 |
h3cMDCControlTableThis table is used to configure MDCs for a device and show MDC's status. SEQUENCE OF H3cMDCControlEntry .1.3.6.1.4.1.2011.10.2.136.2.1.1 |
h3cMDCControlEntryAn entry of the h3cMDCControlTable, every entry is corresponding with an MDC. H3cMDCControlEntry .1.3.6.1.4.1.2011.10.2.136.2.1.1.1 |
h3cMDCIndexMDC ID is used as MDCIndex, the value range of MDC ID depends on the device model. MDCIndex cannot be modified after creation.ro Integer32 .1.3.6.1.4.1.2011.10.2.136.2.1.1.1.1 |
h3cMDCNameSpecifies the MDC name, a case-sensitive string of 1 to 15 characters. The MDC name cannot be modified after creation.rw DisplayString .1.3.6.1.4.1.2011.10.2.136.2.1.1.1.2 |
h3cMDCActionState 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.rw H3cMdcActionValue .1.3.6.1.4.1.2011.10.2.136.2.1.1.1.3 |
h3cMDCStatusStatus of MDCs.ro H3cMdcRunStatus .1.3.6.1.4.1.2011.10.2.136.2.1.1.1.4 |
h3cMDCRowStatusThe status of this table entry. Only support active, createAndGo and destroy.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.136.2.1.1.1.5 |
h3cMDCResource OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.136.2.2 |
h3cMDCDISKResourceTableThis 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. SEQUENCE OF H3cMDCDISKResourceEntry .1.3.6.1.4.1.2011.10.2.136.2.2.1 |
h3cMDCDISKResourceEntryAn 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. H3cMDCDISKResourceEntry .1.3.6.1.4.1.2011.10.2.136.2.2.1.1 |
h3cMDCDISKResourceInstanceInstance index of disk resource. Different instances for disk: Flash, CF cards. Integer32 .1.3.6.1.4.1.2011.10.2.136.2.2.1.1.1 |
h3cMDCDISKResourceInstanceNameInstance name of disk resource. Such as: Flash, CF cards.ro DisplayString .1.3.6.1.4.1.2011.10.2.136.2.2.1.1.2 |
h3cMDCDISKResourceMinLimitLimit minimum (reserve resources, must be all 0).rw Integer32 .1.3.6.1.4.1.2011.10.2.136.2.2.1.1.3 |
h3cMDCDISKResourceMaxLimitMaximum 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 setrw Integer32 .1.3.6.1.4.1.2011.10.2.136.2.2.1.1.4 |
h3cMDCDISKResourceReserveThe reserve limit resources of disk.ro Unsigned32 UNITS "KB" .1.3.6.1.4.1.2011.10.2.136.2.2.1.1.5 |
h3cMDCDISKResourceQuotaThe total limit resources of disk according to h3cMDCDiskResourceMaxLimit.ro Unsigned32 UNITS "KB" .1.3.6.1.4.1.2011.10.2.136.2.2.1.1.6 |
h3cMDCDISKResourceUsageCurrent usage of disk resources.ro Unsigned32 UNITS "KB" .1.3.6.1.4.1.2011.10.2.136.2.2.1.1.7 |
h3cMDCDISKResourceAvailableCurrent available resources of disk.ro Unsigned32 UNITS "KB" .1.3.6.1.4.1.2011.10.2.136.2.2.1.1.8 |
h3cMDCMemoryResourceTableThis 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. SEQUENCE OF H3cMDCMemoryResourceEntry .1.3.6.1.4.1.2011.10.2.136.2.2.2 |
h3cMDCMemoryResourceEntryAn 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. H3cMDCMemoryResourceEntry .1.3.6.1.4.1.2011.10.2.136.2.2.2.1 |
h3cMDCMemoryResourceMinLimitLimit minimum(reserve resources, must be all 0). Non-default MDC cannot set.rw Integer32 .1.3.6.1.4.1.2011.10.2.136.2.2.2.1.1 |
h3cMDCMemoryResourceMaxLimitMaximum 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.rw Integer32 .1.3.6.1.4.1.2011.10.2.136.2.2.2.1.2 |
h3cMDCMemoryResourceReserveThe reserve limit resources of memory.ro Unsigned32 UNITS "KB" .1.3.6.1.4.1.2011.10.2.136.2.2.2.1.3 |
h3cMDCMemoryResourceQuotaThe total limit resources of memory.ro Unsigned32 UNITS "KB" .1.3.6.1.4.1.2011.10.2.136.2.2.2.1.4 |
h3cMDCMemoryResourceUsageCurrent usage of memory resources.ro Unsigned32 UNITS "KB" .1.3.6.1.4.1.2011.10.2.136.2.2.2.1.5 |
h3cMDCMemoryResourceAvailableCurrent available value of memory resources.ro Unsigned32 UNITS "KB" .1.3.6.1.4.1.2011.10.2.136.2.2.2.1.6 |
h3cMDCCPUResourceTableThis 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. SEQUENCE OF H3cMDCCPUResourceEntry .1.3.6.1.4.1.2011.10.2.136.2.2.3 |
h3cMDCCPUResourceEntryAn 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. H3cMDCCPUResourceEntry .1.3.6.1.4.1.2011.10.2.136.2.2.3.1 |
h3cMDCCPUResourceLimitCPU weight-maximum of available resources of CPU, this number specifies a CPU weight for an MDC. Non-default MDC cannot set.rw Integer32 .1.3.6.1.4.1.2011.10.2.136.2.2.3.1.1 |
h3cMDCCPUResourceUsagethe CPU usagero Integer32 .1.3.6.1.4.1.2011.10.2.136.2.2.3.1.2 |
h3cMDCLocation OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.136.2.3 |
h3cMDCLocationTableThis 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. SEQUENCE OF H3cMDCLocationEntry .1.3.6.1.4.1.2011.10.2.136.2.3.1 |
h3cMDCLocationEntryAn 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. H3cMDCLocationEntry .1.3.6.1.4.1.2011.10.2.136.2.3.1.1 |
h3cMDCLocationStatusTo 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.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.2011.10.2.136.2.3.1.1.1 |
h3cMDCAllocate OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.136.2.4 |
h3cMDCGroupIfTableThis table indication of relation between interfaces and groups, which helps to realize the allocation, together with h3cMDCAllocateTable. Non-default MDC cannot operate. SEQUENCE OF H3cMDCGroupIfEntry .1.3.6.1.4.1.2011.10.2.136.2.4.1 |
h3cMDCGroupIfEntryAn 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. H3cMDCGroupIfEntry .1.3.6.1.4.1.2011.10.2.136.2.4.1.1 |
h3cMDCGroupIdentityThe 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.ro Integer32 .1.3.6.1.4.1.2011.10.2.136.2.4.1.1.2 |
h3cMDCAllocateTableThis 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. SEQUENCE OF H3cMDCAllocateEntry .1.3.6.1.4.1.2011.10.2.136.2.4.2 |
h3cMDCAllocateEntryAn entry of the h3cMDCAllocateTable, every entry is the status whether physical interfaces have been assigned to an MDC. H3cMDCAllocateEntry .1.3.6.1.4.1.2011.10.2.136.2.4.2.1 |
h3cMDCAllocateGroupIndexThe 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. Integer32 .1.3.6.1.4.1.2011.10.2.136.2.4.2.1.1 |
h3cMDCAllocateGroupDescriptionInterfaces list Such as: GigabitEthernet4/5/0/1 to GigabitEthernet4/5/0/24, GigabitEthernet4/5/0/48ro DisplayString .1.3.6.1.4.1.2011.10.2.136.2.4.2.1.2 |
h3cMDCAllocateMDCIdMDC 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.rw Integer32 .1.3.6.1.4.1.2011.10.2.136.2.4.2.1.3 |
h3cMDCNotification OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.136.3 |
h3cMDCNotificationObjects OBJECT IDENTIFIER .1.3.6.1.4.1.2011.10.2.136.3.0 |
h3cMDCStateChangeToActiveThe h3cMDCStateChangeToActive trap indicates that the MDC status has changed to active. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.136.3.0.1 |
h3cMDCStateChangeToInactiveThe h3cMDCStateChangeToInactive trap indicates that the MDC status has changed to inactive. NOTIFICATION-TYPE .1.3.6.1.4.1.2011.10.2.136.3.0.2 |