Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
I Revision History.............................................................................................................. 23
ii References ..................................................................................................................... 30
Introduction ....................................................................................................................... 32
Consideration ................................................................................................................... 33
3 RFC1213-MIB ............................................................................................................ 36
4 SNMP-FRAMEWORK-MIB ........................................................................................ 44
5 SNMPv2-MIB ............................................................................................................. 44
6 SNMP-MPD-MIB ........................................................................................................ 45
6.1 SnmpMPDStats.................................................................................................... 45
7 SNMP-NOTIFICATION-MIB ...................................................................................... 45
8 IF-MIB ........................................................................................................................ 45
8.2 ifTable................................................................................................................... 46
9 ISIS-MIB ..................................................................................................................... 48
9.1 isisSysObject........................................................................................................ 48
9.2 isisManAreaAddrTable......................................................................................... 48
9.8 isisCircTable......................................................................................................... 50
9.17 isisLSPSummaryTable......................................................................................... 54
9.18 isisLSPTLVTable.................................................................................................. 54
10 BGP4-MIB ............................................................................................................ 55
10.2 bgpPeerTable....................................................................................................... 55
11 RIPv2-MIB ............................................................................................................ 57
11.3 rip2IfConfTable..................................................................................................... 58
11.4 rip2PeerTable....................................................................................................... 58
12 OSPF-MIB ............................................................................................................ 59
93.4 ospfLsdbTable...................................................................................................... 60
93.6 ospfIfMetricTable.................................................................................................. 61
93.8 ospfNbrTable........................................................................................................ 61
13 RADIUS-ACC-CLIENT-MIB ................................................................................. 63
13.2 radiusAccServerTable.......................................................................................... 63
14 RADIUS-AUTH-CLIENT-MIB ............................................................................... 64
15 EtherLike-MIB ...................................................................................................... 65
15.3 dot3ControlTable.................................................................................................. 65
16 MAU-MIB .............................................................................................................. 66
17 Entity-MIB ............................................................................................................. 67
18 DISMAN-PING-MIB ............................................................................................. 77
19 DOT3-OAM-MIB................................................................................................... 85
20 SNMP-TARGET-MIB ........................................................................................... 88
21 SNMP-USER-BASED-SM-MIB ............................................................................ 93
22 SNMP-VIEW-BASED-ACM-MIB .......................................................................... 95
23 VRRP-MIB............................................................................................................ 97
24 BRIDGE-MIB ........................................................................................................ 99
28 RMON-MIB......................................................................................................... 105
36 IPV6-ICMP-MIB.................................................................................................. 120
40 LLDP-MIB........................................................................................................... 130
49 HUAWEI-LswINF-MIB........................................................................................ 157
52 HUAWEI-RMON-EXT-MIB................................................................................. 163
56 HUAWEI-TRNG-MIB.......................................................................................... 173
57 HUAWEI-8021PAE-MIB..................................................................................... 175
64 H3C-SYS-MAN-MIB........................................................................................... 204
69 H3C-IPV6-ADDRESS-MIB................................................................................. 219
85 H3C-DLDP-MIB.................................................................................................. 258
I Revision History
The format of Revision“” is xx.yy. And xx is major version, yy is minor version. The
initial version begins with 0.01.
All modifications should be recorded here to indicate the reader which changes are
happened.0.022004-06-19
ion
team
for HSD09817
h3cSysSummerTimeMethod, h3cSysSummerTimeStart,
h3cSysSummerTimeEnd, h3cSysSummerTimeOffset by
LSD13790
WLD01955
HSD12398.
HSD12431
ion
for LSD14135
RTD14086
for LSD15028
RTD15201
LSD16507
RTD17727
RTD17931
RTD17932
ion
RTD18493
for HSD22421
WLD06267
LSD21171
Update H3C-RRPP-MIB by songjianyong for HSD23021.
description of h3cQinQIfEthernetType,
h3cQinQCustomerTPIDValue in H3C-QINQ-MIB by
wangjinwang.
ion
for LSD22713.
LSD23773.
LSD23952
HSTB02075
RTD24001
RTD24591
ion
RTD24736
h3cEponUniVCTCableStatus and
h3cEponUniVCTCableLength to h3cEponUniSysManTable by
RTD26355
hwdot1xpaeportHandshakeStatus in
WLD12651.
ion
for HSD34676.
RTD26841.
HSD35930.
ion
RTD28419
h3cEponOperationResult 、 h3cEponOnuAutoBindTrap in
qianxuebiao.
uan h3cRrppDomainInstanceListHigh,
h3cRrppDomainProtectVlanListLow and
HSD41426.
uan
Added h3cDomainCurrentAccessNum to h3cDomainInfoTable
ion
LSD38890
ii References
This document describes Management Information Base (MIB) and objects in them, which
are supported by H3C Middle End Switch Products. It is supposed that this document
gives a guideline for usage of MIBs in H3C Switch Products.
Introduction
This document contains “Public MIB List” section and “Private MIB list” section.
The “Public MIB List” provides a MIB list containing the Internet standard MIBs supported
by switch. The “Private MIB List” provides H3C private MIB list.
The following chapters describe the implementation of the objects of all public and private
MIBs.
Consideration
Any action to modify, delete, remove and add must be recorded in Revision History
In File name column, the MIB file name must conform with the naming rule, that is the MIB
module name prefixed with the RFC index like rfc2737-entity.mib. Note that file name is
lowercase.
the IP Group of
rfc1213
IEEE Std
802.1AB-2005
IEEE Std
802.1AB-2005
of IEEE Std
802.1AB-2005
of rfc1213
trap
Huawei
version
3 RFC1213-MIB
3.2.1 ifNumber
The ifNumber value will display the actual number of entries in the ifTable.
3.4.2 ipAddrTable
3.4.3 ipRouteTable
Note: 1) The ipRouteTable can get only one of the equal-cost routes.
2) The ipRouteTable can get only one of the routes with same destination and
different mask.
3.6.2 tcpConnTable
3.7.2 udpTable
3.9.1 ipNetToMediaTable
4 SNMP-FRAMEWORK-MIB
The first four octets are set to the binary equivalent of the agent's SNMP management
private enterprise number as assigned by the Internet Assigned Numbers Authority
(IANA), and the very first bit is set to 1. For example, if Huawei Networks has been
assigned enterprises 2011, the first four octets would be assigned '800007DB'H.
For switches, the fifth octet is 3 indicates that the following is MAC address. The
remaining six octets are the MAC address main board.
5 SNMPv2-MIB
6 SNMP-MPD-MIB
6.1 SnmpMPDStats
7 SNMP-NOTIFICATION-MIB
7.1 snmpNotifyTable
8 IF-MIB
8.2 ifTable
8.3 ifXTable
8.4 ifTestTable
At the same time, only one test can be in progress, the second test is rejected.
For distributed device, the result is holding on master board. If the device reboots, the test
result is be lost.
The objects ifTestStatus, ifTestId, and ifTestOwner must be set together when ownership
of the ifTestEntry is obtained successfully.
8.5 ifRcvAddressTable
9 ISIS-MIB
9.1 isisSysObject
isisSysMaxAge is not
implemented
isisSysMaxLSPGenInt, but it
greater than
isisSysMaxLSPGenInt
is not implemented
ipv6(2)
9.2 isisManAreaAddrTable
9.3 IsisAreaAddrTable
9.4 isisSummAddrTable
9.5 isisRouterTable
9.6 isisSysLevelTable
isisSysLevelTEEnabled is true(1)
isisSysLevelMetricStyle is
narrow(1)
9.7 isisCirc
9.8 isisCircTable
broadcast(1), ptToPt(2)}
9.9 isisCircLevelTable
isisSysLevelMetricStyle is narrow
(1) or both(3)
isisSysLevelMetricStyle is wide
(2)
9.10 isisSystemCounterTable
as
ms
9.11 isisCircuitCounterTable
9.12 isisPacketCounterTable
9.13 isisISAdjTable
9.14 isisISAdjAreaAddrTable
9.15 isisISAdjIPAddrTable
9.16 isisISAdjProtSuppTable
9.17 isisLSPSummaryTable
9.18 isisLSPTLVTable
9.19 isisNotificationEntry
notify
notify
notify
notify
notify
notify
notify
notify
notify
notify
notify
notify
notify
notify
notify
10 BGP4-MIB
10.2 bgpPeerTable
10.3 bgp4PathAttrTable
10.4 bgpTraps
11 RIPv2-MIB
11.2 rip2IfStatTable
11.3 rip2IfConfTable
11.4 rip2PeerTable
12 OSPF-MIB
93.1 ospfGeneralGroup
93.2 ospfAreaTable
93.3 ospfStubAreaTable
93.4 ospfLsdbTable
93.5 ospfIfTable
93.6 ospfIfMetricTable
93.7 ospfVirtIfTable
93.8 ospfNbrTable
93.9 ospfVirtNbrTable
93.10 ospfExtLsdbTable
93.11 ospfAreaAggregateTable
13 RADIUS-ACC-CLIENT-MIB
13.2 radiusAccServerTable
14 RADIUS-AUTH-CLIENT-MIB
14.2 radiusAuthServerTable
15 EtherLike-MIB
15.1 dot3StatsTable
15.2 dot3CollTable
15.3 dot3ControlTable
15.4 dot3PauseTable
16 MAU-MIB
17 Entity-MIB
This chapter describes the information of Entity MIB. The Entity MIB contains five groups
of MIB objects: entityPhysical group, entityLogical group, entityMapping group,
entityGeneral group and entityNotifications group. Thereinto, the entityPhysical group
describes the physical entities managed by a single agent. This group contains a single
table to identify physical system components, called the entPhysicalTable. The
entPhysicalTable contains one row per physical entity, and must always contain at least
one row for an "overall" physical entity, which should have an entPhysicalClass value of
'chassis(3)' or 'module(9)'. Each row is indexed by an arbitrary, small integer, and contains
a description and type of the physical entity. It also optionally contains the index number
of another entPhysicalEntry indicating a containment relationship between the two.
The entityLogical group describes the logical entities managed by a single agent. This
group contains a single table to identify logical entities, called the entLogicalTable. The
entLogicalTable contains one row per logical entity. Each row is indexed by an arbitrary,
small integer and contains a name, description, and type of the logical entity. It also
contains information to allow access to the MIB information for the logical entity. This
includes SNMP versions that use a community name (with some form of implied context
representation) and SNMP versions that use the SNMP ARCH [RFC2571] method of
context identification. If a agent represents multiple logical entities with this MIB, then this
2008-02-26 Page67, Total 299
Confidential Information of H3C.
group must be implemented for all logical entities known to the agent. If an agent
represents a single logical entity, or multiple logical entities within a single naming scope,
then implementation of this group may be omitted by the agent.
The entityMapping group describes the associations between the physical entities logical
entities, interfaces, and non-interface ports managed by a single agent. This group
contains three tables to identify associations between different system components. The
entLPMappingTable contains mappings between entLogicalIndex values (logical entities)
and entPhysicalIndex values (the physical components supporting that entity). A logical
entity can map to more than one physical component, and more than one logical entity
can map to (share) the same physical component. If an agent represents a single logical
entity, or multiple logical entities within a single naming scope, then implementation of this
table may be omitted by the agent. The entAliasMappingTable contains mappings
between entLogicalIndex, entPhysicalIndex pairs and 'alias' object identifier values. This
allows resources managed with other MIBs (e.g., repeater ports, bridge ports, physical
and logical interfaces) to be identified in the physical entity hierarchy. Note that each alias
identifier isonly relevant in a particular naming scope. If an agent represents a single
logical entity, or multiple logical entities within a single naming scope, then implementation
of this table may be omitted by the agent. The entPhysicalContainsTable contains simple
mappings between 'entPhysicalContainedIn' values for each container/'containee'
relationship in the managed system. The indexing of this table allows an NMS to quickly
discover the 'entPhysicalIndex' values for all children of a given physical entity.
The entityGeneral group describes general system attributes shared by potentially all
types of entities managed by a single agent. This group contains general information
relating to the other object groups. At this time, the entGeneral group contains a single
scalar object (entLastChangeTime), which represents the value of sysUptime when any
part of the Entity MIB configuration last changed.
The entityNotifications group contains status indication notifications. This group contains
notification definitions relating to the overall status of the Entity MIB instantiation.
17.1 entPhysicalTable
17.2 entAliasMappingTable
17.3 entPhysicalContainsTable
Note :
1. “Yes” means the property of that entity is implemented. Others are not supported.
2. If the result of the operation is “no such name/instance”, then this MIB object is not to be
supported for the specific entity.
entity entPhysicalMfgDate
chassis No
backplane No
container No
powerSupply No
fan No
entity entPhysicalMfgDate
sensor No
module Yes
port No
cpu No
entity entPhysicalUris
chassis No
backplane No
container No
powerSupply No
fan No
sensor No
module Yes
port No
cpu No
entPhysicalDescr
entity
chassis Yes
backplane No
container Yes
powerSupply Yes
fan Yes
sensor No
module Yes
port Yes
cpu No
entPhysicalVendorType
entity
chassis Yes
backplane No
container Yes
powerSupply Yes
fan Yes
sensor No
module Yes
port Yes
cpu No
entPhysicalContainedIn
entity
chassis Yes
backplane No
container Yes
powerSupply Yes
fan Yes
sensor No
module Yes
port Yes
cpu No
entPhysicalClass
entity
chassis Yes
backplane No
container Yes
powerSupply Yes
fan Yes
sensor No
module Yes
port Yes
cpu No
entPhysicalParentRelPos
entity
chassis Yes
backplane No
container Yes
powerSupply Yes
fan Yes
sensor No
module Yes
port Yes
cpu No
entPhysicalName
entity
chassis Yes
backplane No
container Yes
powerSupply Yes
fan Yes
sensor No
module Yes
port Yes
cpu No
entPhysicalHardwareRev
entity
chassis Yes
backplane No
container No
powerSupply No
fan No
sensor No
module Yes
port No
cpu No
entPhysicalFirmwareRev
entity
chassis Yes
backplane No
container No
powerSupply No
fan No
sensor No
module Yes
port No
cpu No
entPhysicalSoftwareRev
entity
chassis Yes
backplane No
container No
powerSupply No
fan No
sensor No
module Yes
port No
cpu No
entPhysicalSerialNum
entity
chassis No
backplane No
container No
powerSupply No
fan No
sensor No
module Yes
port Yes
cpu No
entPhysicalMfgName
entity
chassis No
backplane No
container No
powerSupply No
fan No
sensor No
module No
cpu No
entPhysicalModelName
entity
chassis Yes
backplane No
container No
powerSupply No
fan No
sensor No
module No
port No
cpu No
entPhysicalAlias
entity
chassis No
backplane No
container No
powerSupply No
fan No
sensor No
module No
port No
cpu No
entPhysicalAssetID
entity
chassis No
backplane No
container No
powerSupply No
fan No
sensor No
module No
port No
cpu No
entPhysicalIsFRU
entity
chassis Yes
backplane No
container Yes
powerSupply Yes
fan Yes
sensor No
module Yes
port Yes
cpu No
Entity POWE FAN BACK CHAS CONT MODU PORT SENS CPU
eRev
entPhysicalFirmwar Yes Yes
eRev
entPhysicalSoftware Yes Yes
Rev
entPhysicalSerialNu Yes Yes
m
entPhysicalMfgNam Yes
e
entPhysicalModelN Yes
ame
entPhysicalMfgDate Yes
entPhysicalUris
entPhysicalAlias
entPhysicalAssetID
18 DISMAN-PING-MIB
This MIB should be supported by device which implements disman ping function. This
MIB cannot mix using with CLI.
18.2 pingCtlTable
b) When creating a test entry, the default value of pingCtlType is pingIcmpEcho. Once
created, pingCtlType cannot be changed, so pingCtlType must be set as the entry
created.
pingCtlTrapGeneration,
pingCtlTrapProbeFailureFilter,
pingCtlTrapTestFailureFilter,
pingCtlDescr,
pingCtlMaxRows(If the value of this object is smaller than the previous value,
the redundant histories records will be deleted.)
The results, histories and statistics must be the factual reflection of the test results
of current configurations.
Users will be puzzled when they get the results which caused by the previous
configurations.
pingCtlTargetAddressType
pingIcmpEcho
pingCtlTargetAddress
pingCtlDataSize
pingCtlDataFill
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlIfIndex
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingCtlTargetAddressType
pingUdpEcho
pingCtlTargetAddress
h3cNqaUdpEcho or hwpingUdpEcho pingCtlDataSize
pingCtlDataFill
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingCtlTargetAddressType
pingSnmpQuery
pingCtlTargetAddress
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingCtlTargetAddressType
pingTcpConnectionAttempt
pingCtlTargetAddress
h3cNqaTcpconnect or pingCtlSourceAddressType
hwpingTcpconnect pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingCtlTargetAddressType
h3cNqajitter ( for udp-jitter test)
pingCtlTargetAddress
h3cNqaCtlCodecTyp is defined as notDefined(1) pingCtlDataSize
pingCtlDataFill
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingCtlTargetAddressType
h3cNqajitter (for voice test)
pingCtlTargetAddress
h3cNqaCtlCodecTyp is defined as g711Alaw(2)、 pingCtlDataSize
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlTargetAddressType
h3cNqaHttp
pingCtlTargetAddress
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingCtlTargetAddressType
h3cNqadlsw
pingCtlTargetAddress
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingCtlIfIndex
h3cNqadhcp
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingCtlTargetAddressType
h3cNqaftp
pingCtlTargetAddress
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
unknown(0).
pingCtlTargetAddressType is
If the value of
pingCtlTargetAddressType is
value is 100.
operation is 2s.
operation is 60s.
value is 3s
to 200.
operation is 2s.
value is 0s.
pingTestCompleted(2) is
supported.
type(probeFailure) in
pingCtlTrapGeneration is
specified.
If the value of
this object is 1.
invalid.
type(testFailure) in
pingCtlTrapGeneration is
specified.
If the value of
this object is 1.
invalid.
creation.
with space.
unknown(0).
pingCtlSourceAddressType is
If the value of
pingCtlSourceAddressType is
vlan interface.
18.3 pingResultsTable
18.4 pingProbeHistoryTable
19 DOT3-OAM-MIB
19.1 dot3OamTable
19.2 dot3OamPeerTable
19.3 dot3OamStatsTable
19.4 dot3OamEventConfigTable
19.5 dot3OamEventLogTable
20 SNMP-TARGET-MIB
For a valid target host entry which is made up of one entry in snmpTargetAddrTable
and another entry in snmpTargetParamsTable:
20.2 snmpTargetAddrTable
20.3 snmpTargetParamsTable
2: [Loaded: SNMPv2-TM]
snmpTargetAddrTDomain.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.55.
54.46.55.54 (object identifier) snmpUDPDomain
3:
snmpTargetAddrTAddress.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.55
.54.46.55.54 (octet string) A9.FE.4C.4C.00.A2 (hex)
4:
snmpTargetAddrTimeout.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.55.5
4.46.55.54 (integer) 1500
5:
snmpTargetAddrRetryCount.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.
55.54.46.55.54 (integer) 3
6:
snmpTargetAddrTagList.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.55.5
4.46.55.54 (octet string) TrapHost [54.72.61.70.48.6F.73.74 (hex)]
7:
snmpTargetAddrParams.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.55.5
4.46.55.54 (octet string) traphost.gl.169.254.76.76
[74.72.61.70.68.6F.73.74.2E.67.6C.2E.31.36.39.2E.32.35.34.2E.37.36.2E.37.36 (hex)]
8:
snmpTargetAddrStorageType.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46
.55.54.46.55.54 (integer) nonVolatile(3)
9:
snmpTargetAddrRowStatus.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.5
5.54.46.55.54 (integer) active(1)
10:
snmpTargetParamsMPModel.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.
55.54.46.55.54 (integer) 0
11:
snmpTargetParamsSecurityModel.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.5
2.46.55.54.46.55.54 (integer) 1
12:
snmpTargetParamsSecurityName.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.5
2.46.55.54.46.55.54 (octet string) gl [67.6C (hex)]
13:
snmpTargetParamsSecurityLevel.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.5
2.46.55.54.46.55.54 (integer) noAuthNoPriv(1)
14:
snmpTargetParamsStorageType.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52
.46.55.54.46.55.54 (integer) nonVolatile(3)
15:
snmpTargetParamsRowStatus.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.4
6.55.54.46.55.54 (integer) active(1)
2:
snmpTargetAddrTDomain.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.46.
49.46.49.46.118.112.110 (object identifier) snmpUDPDomain
3:
snmpTargetAddrTAddress.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.46.
49.46.49.46.118.112.110 (octet string) 01.01.01.01.00.A2 (hex)
4:
snmpTargetAddrTimeout.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.46.4
9.46.49.46.118.112.110 (integer) 1500
5:
snmpTargetAddrRetryCount.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.4
6.49.46.49.46.118.112.110 (integer) 3
6:
snmpTargetAddrTagList.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.46.49
.46.49.46.118.112.110 (octet string) TrapHost [54.72.61.70.48.6F.73.74 (hex)]
7:
snmpTargetAddrParams.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.46.4
9.46.49.46.118.112.110 (octet string) traphost.public.1.1.1.1.vpn
[74.72.61.70.68.6F.73.74.2E.70.75.62.6C.69.63.2E.31.2E.31.2E.31.2E.31.2E.76.70.6E (hex)]
8:
snmpTargetAddrStorageType.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.
46.49.46.49.46.118.112.110 (integer) nonVolatile(3)
9:
snmpTargetAddrRowStatus.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.4
6.49.46.49.46.118.112.110 (integer) active(1)
10:
snmpTargetParamsMPModel.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.
46.49.46.49.46.118.112.110 (integer) 0
11:
snmpTargetParamsSecurityModel.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.4
6.49.46.49.46.49.46.118.112.110 (integer) 1
12:
snmpTargetParamsSecurityName.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.4
13:
snmpTargetParamsSecurityLevel.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46
.49.46.49.46.49.46.118.112.110 (integer) noAuthNoPriv(1)
14:
snmpTargetParamsStorageType.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.
49.46.49.46.49.46.118.112.110 (integer) nonVolatile(3)
15:
snmpTargetParamsRowStatus.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.4
9.46.49.46.49.46.118.112.110 (integer) active(1)
21 SNMP-USER-BASED-SM-MIB
22 SNMP-VIEW-BASED-ACM-MIB
22.1 vacmContextTable
22.2 vacmSecurityToGroupTable
22.3 vacmAccessTable
23 VRRP-MIB
24 BRIDGE-MIB
24.2 dot1dBasePortTable
24.4 dot1dStpPortTable
24.6 dot1dTpPortTable
25 POWER-ETHERNET-MIB
25.2 pethPsePortTable
25.3 pethMainPseTable
25.4 pethNotificationControlTable
26 P-BRIDGE-MIB
26.2 dot1dPortCapabilitiesTable
26.3 dot1dPortPriorityTable
26.4 dot1dPortGarpTable
27 Q-BRIDGE-MIB
27.2 dot1qTpFdbTable
27.3 dot1qTpGroupTable
27.5 dot1qVlanStaticTable
27.6 dot1qPortVlanTable
28 RMON-MIB
28.1 etherStatsTable
No row exists in this table by default. The Max number of RMON Entries in this table is 100. If the
interface that the etherStatsEntry is monitoring is removed, the value of the objects of this entry can’t be
operation tries to change the value of these objects, an 'inconsistentValue' error will be returned.
28.2 historyControlTable
No row exists in this table by default. The Max number of RMON Entries in this table is 100. If the
interface that the historyControlEntry is monitoring is removed, the value of the objects of this entry can’t
historyControlStatus. If a set operation tries to change the value of these objects, an 'inconsistentValue'
28.3 etherHistoryTable
28.4 alarmTable
2008-02-26 Page106, Total
Confidential Information of H3C.
299
No Spreading without Permission
Comware V5 S7900E MIB Companion Secret
28.5 eventTable
28.6 logTable
29 IEEE8021-CFM-MIB
29.2 dot1agCfmMdTable
29.3 dot1agCfmMaNetTable
29.4 dot1agCfmMaCompTable
dot1agCfmMaCompPrimaryVlanId
read-create Current Can not be modified after
creation
dot1agCfmMaCompMhfCreation
read-create Current As per MIB
dot1agCfmMaCompIdPermission
read-create No Only support sendIdNone (1) and
sendIdDefer (5)
dot1agCfmMaCompNumberOfVid
read-only No The value is always 1.
s
dot1agCfmMaCompRowStatus
read-create Current Only support active(1),
createAndGo(4) and destroy(6)
29.5 dot1agCfmMaMepListTable
dot1agCfmMaMepListRowStatus
read-create Current Only support active(1),
createAndGo(4) and destroy(6)
29.6 dot1agCfmMepTable
creation
creation
defErrorCCM(4), defXconCCM
(5)
re
re
rs
er
MacAddress
MepId
sMepId
ages
lv
riority
ropEnable
tOK
umber
MacAddress
MepId
sMepId
sIdentifier
30 IEEE8021-PAE-MIB
30.3 dot1xAuthConfigTable
30.4 dot1xAuthStatsTable
31 IEEE8023-LAG-MIB
31.1 dot3adAggTable
31.2 dot3adAggPortListTable
31.3 dot3adAggPortTable
31.4 dot3adAggPortStatsTable
31.5 dot3adAggPortDebugTable
32 IGMP-STD-MIB
32.1 igmpInterfaceTable
The igmpInterfaceTable contains one row for each interface on which IGMP is
enabled. It is used to configure the IGMP information on the interface.
32.2 igmpCacheTable
The igmpCacheTable contains information about multicast groups for which there are
members on a particular interface.
33 IP-FORWARD-MIB
33.1 ipCidrRouteTable
34 IPV6-TCP-MIB
34.1 ipv6TcpConnTable
35 IPV6-UDP-MIB
35.1 ipv6UdpTable
36 IPV6-ICMP-MIB
36.1 ipv6IfIcmpTable
37 IPV6-MIB
37.2 ipv6IfTable
37.3 ipv6IfStatsTable
37.4 ipv6AddrPrefixTable
37.5 ipv6AddrTable
37.7 ipv6RouteTable
37.8 ipv6NetToMediaTable
38 LLDP-EXT-DOT1-MIB
Notes:
The following section defines the Management Information Base (MIB) for link layer
discovery protocol in the Internet community. In particular, it describes a set of managed
objects that allow managing discovery operations, which are used on LAN switch products.
The definitions of managed objects in the following section are formed into a specification
for link layer discovery used for switches.
The Link Layer Discovery Protocol (LLDP) allows stations attached to an IEEE 802 LAN to
advertise, to other stations attached to the same IEEE 802 LAN, the major capabilities
provided by the system incorporating that station, the management address or addresses
of the entity or entities that provide management of those capabilities, and the
identification of the station’s point of attachment to the IEEE 802 LAN required by those
management entity or entities.
The information distributed via this protocol is stored by its recipients in a standard
Management Information Base (MIB), making it possible for the information to be
accessed by a Network Management System (NMS) using a management protocol such
as the Simple Network Management Protocol (SNMP).
In this section, several set operations about enable IEEE802.1 organizational specific
TLVs transmission on given port are presented. For this purpose, the value of associated
objects should be set to:
38.1 lldpXdot1ConfigPortVlanTable
38.2 lldpXdot1ConfigVlanNameTable
38.3 lldpXdot1ConfigProtoVlanTable
38.4 lldpXdot1ConfigProtocolTable
FALSE
38.5 lldpXdot1LocTable
38.6 lldpXdot1LocProtoVlanTable
38.7 lldpXdot1LocVlanNameTable
38.8 lldpXdot1LocProtocolTable
protocol
38.9 lldpXdot1RemTable
38.10 lldpXdot1RemProtoVlanTable
38.11 lldpXdot1RemVlanNameTable
38.12 lldpXdot1RemProtocolTable
39 LLDP-EXT-DOT3-MIB
Notes:
All the IEEE 802.3 organizationally defined discovery information will be transmitted on
every port as default configuration, so when LLDP is global enabled on a switch , the
following value will be set:
lldpXdot3PortConfigTLVsTxEnable.20 = ‘ f ’ H
The network management can configure to transmit some of that information and let the
others not to be transmitted.
For example, if the network management only want to transmit Link Aggregation TLV and
Maximum Frame Size TLV in the LLDPDU on a given port, the following value will be set:
lldpXdot3PortConfigTLVsTxEnable.20 = ‘c’ H
39.1 lldpXdot3PortConfigTable
given port.
39.2 lldpXdot3LocPortTable
39.3 lldpXdot3LocPowerTable
39.4 lldpXdot3LocLinkAggTable
39.5 lldpXdot3LocMaxFrameSizeTable
39.6 lldpXdot3RemPortTable
39.7 lldpXdot3RemPowerTable
39.8 lldpXdot3RemLinkAggTable
39.9 lldpXdot3RemMaxFrameSizeTable
40 LLDP-MIB
Notes:
This document defines the LLDP basic MIB for use with SNMP in TCP/IP based internets.
The LLDP MIB consists of two types of MIB modules, the mandatory basic MIB defined in
this clause and from zero to n optional organizationally specific MIB extensions such as
LLDP-EXT-DOT1-MIB, LLDP-EXT-DOT3-MIB. Each MIB module is divided into two major
sections to allow selective MIB support for the particular operating mode (transmit only,
receive only, or both transmit and receive) being implemented. The basic MIB in this
document describes LLDP configuration, statistics, local system data and remote systems
data components.
All the basic discovery information will be transmitted on every port as default
configuration. So when LLDP is global enabled on a switch , the following value will be
set:
lldpPortConfigTLVsTxEnable = ‘ f ‘ H
The network management can configure to transmit some of that information and let the
others not to be transmitted.
For example, if the network management only want to transmit System Name TLV in the
LLDPDU on a given port, the following value will be set:
lldpPortConfigTLVsTxEnable.20 = ‘2’ H
lldpMessageTxInterval).
me
40.2 lldpPortConfigTable
40.3 lldpConfigManAddrTable
advertising indicated
40.4 lldpStatsTxPortTable
40.5 lldpStatsRxPortTable
otal
Total
40.6 lldpLocPortTable
40.7 lldpLocManAddrTable
unknown(1).
address.
zero.
40.8 lldpRemTable
40.9 lldpRemManAddrTable
40.10 lldpRemUnKnownTLVTable
40.11 lldpRemOrgDefInfoTable
41 MPLS-LDP-STD-MIB
41.3 mplsLdpEntityTable
41.4 mplsLdpEntityStatsTable
41.6 mplsLdpPeerTable
41.7 mplsLdpSessionTable
41.8 mplsLdpSesStatsTable
41.9 mplsLdpHelloAdjacencyTable
41.10 mplsLdpSessionPeerAddrTable
42 MPLS-FTN-STD-MIB
42.2 mplsFTNTable
42.3 mplsFTNMapTable
43 MPLS-LSR-STD-MIB
43.2 mplsInterfaceTable
43.3 mplsInSegmentTable
43.4 mplsInSegmentPerfTable
43.5 mplsOutSegmentTable
43.6 mplsOutSegmentPerfTable
43.7 mplsXCTable
43.8 mplsLabelStackTable
43.9 mplsInSegmentMapTable
44 HUAWEI-DHCPS-MIB
44.2 hwDHCPSGlobalPoolTable
44.3 hwDHCPSGlobalPoolConfigTable
44.4 hwDHCPSGlobalPoolParaTable
44.5 hwDHCPSGlobalPoolOptionTable
44.6 hwDHCPSGlobalTreeTable
44.7 hwDHCPSForbiddenIPTable
44.8 hwDHCPSConflictIPTable
45 HUAWEI-DISMAN-PING-MIB
This MIB should be supported by device which implements disman ping function. This
MIB cannot mix using with CLI.
45.2 hwPingCtlTable
b) Once the configuration is modified, the result and histories of the corresponding
entry will be cleared.
The results and histories must be the factual reflection of the test results of current
configurations.
Users will be puzzled when they get the results which caused by the previous
configurations.
pingIcmpEcho hwpingCtlTTL
hwpingCtlVPNInstance
pingUdpEcho hwpingCtlTargetPort
hwpingUdpEcho hwpingCtlSourcePort
hwpingCtlTTL
pingSnmpQuery hwpingCtlSourcePort
hwpingCtlTTL
pingTcpConnectionAttempt hwpingCtlTargetPort
hwpingTcpconnect hwpingCtlTTL
hwpingjitter hwpingCtlTargetPort
hwpingCtlSourcePort
hwpingCtlTTL
hwpingCtlJitterAdminInterval
hwpingCtlJitterAdminNumPackets
hwpingHttp hwpingCtlTTL
hwpingCtlHttpOperationType
hwpingCtlHttpOperationString
hwpingdlsw hwpingCtlTTL
hwpingdhcp
hwpingftp hwpingCtlTTL
hwpingCtlFtpOperationType
hwpingCtlFtpUsername
hwpingCtlFtpPassword
hwpingCtlFtpOperationString
"pingUdpEcho" or
"pingTcpConnectionAttempt", the
"hwpingUdpEcho" or
“HTTP/1.0”(case- insensitive).
space.
cannot be space.
to 200.
to 31.
be set.
45.3 hwpingResultsTable
45.4 hwPingJitterStatsTable
SD
SD
SD
SD
SD
SD
DS
DS
DS
DS
DS
DS
DS
expression: (statistical
(statistical summation)/
(statistical times).
expression: (statistical
45.5 hwPingTcpServerTable
45.6 hwPingUdpServerTable
46 HUAWEI-LSW-DEV-ADM-MIB
46.2 hwLswFrameTable
46.3 hwLswSlotTable
46.4 hwLswSubslotTable
46.5 hwLswPortTable
47 HUAWEI-LAG-MIB
47.2 hwAggLinkTable
47.3 hwAggPortTable
48 HUAWEI-LswDEVM-MIB
48.2 hwdevMFanStatusTable
48.3 hwdevMPowerStatusTable
48.4 hwdevMSlotEnvironmentTable
49 HUAWEI-LswINF-MIB
49.1 hwifXXTable
supported
49.2 hwifHybridPortTable
The values of below objects must be appointted at the same time when SET
operation.:
hwifHybridTaggedVlanListLow,
hwifHybridTaggedVlanListHigh,
hwifHybridUnTaggedVlanListLow,
hwifHybridUnTaggedVlanListHigh
49.3 hwifComboPortTable
can be written.
49.5 hwifVLANTrunkStatusTable
49.7 hwPortIsolateGroupTable
50 HUAWEI-LswMAM-MIB
50.1 hwdot1qTpFdbSetTable
Note: The set operation of this table only supports Multiple Variable Bindings set
operation. Variables that must be bound in a set operation include
hwdot1qTpFdbSetPort, hwdot1qTpFdbSetStatus and hwdot1qTpFdbSetOperate.
51 HUAWEI-LswMix-MIB
52 HUAWEI-RMON-EXT-MIB
52.1 prialarmTable
53 HUAWEI-LswMSTP-MIB
53.2 hwdot1sVIDAllocationTable
53.3 hwdot1sInstanceTable
53.4 hwdot1sPortTable
54 H3C-VOICE-VLAN-MIB
54.2 h3cvoiceVlanOuiTable
3) All the objects in this table can not be set separately. The value must be
appointed when creating the row. After a row created, all the instance of this row
54.3 h3cvoiceVlanPortTable
55 HUAWEI-LswVLAN-MIB
55.2 hwvLANMibSwitchCountTable
55.3 hwvLANMibHoldTimeTable
55.4 hwdot1qVlanMIBTable
In this table the leaf node can be classified as config node and query node, config
node can both be used for config and query purposes, while query node can be used for
query only.
hwdot1qVlanName
hwdot1qVlanPorts
hwdot1qVlanType
hwdot1qVlanPriority
hwdot1qVlanRowStatus
hwdot1qVlanBroadcastSuppression
hwdot1qVlanBcastSuppressionPPS
hwdot1qVlanMIBTable use VLAN Index as the table index, which is normally called
VLANID,
if a row is to be created, it is recommended to traverse this table first and use the
unused VLAN index to create the row. In this table rowstatus only support active(1),
createAndGo(4), destory(6).
When the rowstatus node and the following nodes are set simultaneously
hwdot1qVlanName
hwdot1qVlanPorts
hwdot1qVlanType
hwdot1qVlanPriority
hwdot1qVlanBroadcastSuppression
hwdot1qVlanBcastSuppressionPPS
For hwdot1qVlanName, VLAN name string check is performed, the row is created
only if the string check succeeds.
For rest of the leaf nodes listed above, the row will be created before setting the
properties. If errors happen when setting the properties, the operation will fail while the
row has already been created.
1) hwdot1qPorts: through this MIB node only access type ports can be added or
deleted. Operation will fail while the row has already been created, if some of the ports to
be added or deleted are not of access type.
2) hwdot1qVlanType: with value sub-vlan(3) can not be set using this MIB, when
rowstatus(createAndGo(4)) and hwdot1qVlanType(sub-vlan(3)) are set together,
Operation will fail while the row has already been created.
hwdot1qVlanPorts To set the node successfully you should first get the
value of the node, and then only change the corresponding bit of the access port.
hwdot1qVlanPriority
hwdot1qVlanBroadcastSuppression
hwdot1qVlanBcastSuppressionPPS
3. configuration example
1) Configuration succeess
2) Configuration fail
Precondition: there is trunk type port existing on the device and port not belongs to this
vlan. hwdot1qVlanRowStatus(createAndGo(4)) and hwdot1qVlanPorts with trunk port
corresponding bit in the octet string setting to 1 are set together, Operation will fail while
the row has already been created.
55.5 hwVlanInterfaceTable
55.6 hwifIsolateMappingTable
The values of below objects must be appointted at the same time when SET
operation.:
hwifIsolateSecondaryVlanlistLow,
hwifIsolateSecondaryVlanlistHigh,
55.7 hwVlanInterfaceAddrTable
56 HUAWEI-TRNG-MIB
hwTrngAbsoluteTable.
56.1 hwTrngCreateTimerangeTable
56.2 hwTrngAbsoluteTable
56.3 hwTrngPeriodicTable
57 HUAWEI-8021PAE-MIB
57.2 hwdot1xAuthConfigExtTable
These objects are filled into Supplicantproxycheck trap when such a trap is sent.
58 HUAWEI-LswIGSP-MIB
58.1 hwLswIgmpsnoopingMibObject
Name Access PDS Description
hwIgmpSnoopingStatus read-write Current The default setting is disabled
hwIgmpSnoopingRouterPortAge read-write Current As per MIB
hwIgmpSnoopingResponseTime read-write Current As per MIB
hwIgmpSnoopingHostTime read-write Current As per MIB
us
58.2 hwIgmpSnoopingStatsObjects
Name Access PDS Description
hwRecvIGMPGQueryNum read-only No As per MIB
hwRecvIGMPSQueryNum read-only No As per MIB
hwRecvIGMPV1ReportNum read-only No As per MIB
hwRecvIGMPV2ReportNum read-only No As per MIB
hwRecvIGMPLeaveNum read-only No As per MIB
hwSentIGMPSQueryNum read-only No As per MIB
hwRecvErrorIGMPPacketNum read-only No As per MIB
hwIgmpSnoopingClearStats read-write No As per MIB
58.3 hwIgmpSnoopingVlanStatusTable
59 H3C-ACL-MIB
59.1 h3cAclMib2NodesGroup
59.2 h3cAclMib2CapabilityTable
59.3 h3cAclNumberGroupTable
Notes:
59.4 h3cAclIPAclBasicTable
Notes:
All the objects in the table except h3cAclIPAclBasicComment can not be modified
now.
operation.
59.5 h3cAclIPAclAdvancedTable
Notes:
h3cAclIPAclAdvancedSrcAddrType, h3cAclIPAclAdvancedSrcAddr,
h3cAclIPAclAdvancedSrcPrefix, or h3cAclIPAclAdvancedSrcWild does not be
executed. when the node h3cAclIPAclAdvancedSrcAny is not set, If the node
h3cAclIPAclAdvancedSrcAddrType is set and the value of
h3cAclIPAclAdvancedSrcAddrType is 1, h3cAclIPAclAdvancedSrcAddr and
h3cAclIPAclAdvancedSrcWild must be set correctly and the set operation of node
h3cAclIPAclAdvancedSrcPrefix is forbidden; If the node
h3cAclIPAclAdvancedSrcAddrType is set and the value of
h3cAclIPAclAdvancedSrcAddrType is 2, h3cAclIPAclAdvancedSrcAddr and
h3cAclIPAclAdvancedSrcPrefix must be set correctly and the set operation of node
h3cAclIPAclAdvancedSrcWild is forbidden.. The value of
h3cAclIPAclAdvancedSrcAddrType is 1 or 2 now. So do
h3cAclIPAclAdvancedDestAddrType, h3cAclIPAclAdvancedDestAddr,
h3cAclIPAclAdvancedDestPrefix, h3cAclIPAclAdvancedDestAny and
h3cAclIPAclAdvancedDestWild.
All the objects in the table except h3cAclIPAclAdvancedComment can not be modified
now.
‘deny’.
If the rule is Simple ACL, the
value of this object must be
‘invalid’.
h3cAclIPAclAdvancedProtocol read-create Current As per MIB
h3cAclIPAclAdvancedAddrFlag read-create Current As per MIB
h3cAclIPAclAdvancedSrcAddrTyp read-create Current As per MIB
59.6 h3cAclMACTable
Notes:
If a rule will be created, h3cAclMACRowStatus must be 4 and the rule number does not
exist.
All the objects in the table except h3cAclMACComment can not be modified now.
60 H3C-CBQOS2-MIB
h3cCBQoSClassifierCfgInfoTable
h3cCBQoSBehaviorCfgInfoTable
h3cCBQoSPolicyCfgInfoTable.
busy(2).
60.2 h3cCBQoSAccountingRunInfoTable
60.3 h3cCBQoSBehaviorCfgInfoTable
This table does not support to modify the variable of existing entry, only supports to
create a new entry and destroy an existing entry.
(2) Use the value as h3cCBQoSBehaviorIndex to create the new entry of this
table.
60.4 h3cCBQoSCarCfgInfoTable
This table does not support to modify the variable of existing entry, only supports to create
a new entry and destroy an existing entry.
always 4294967295.
remark-dscp-pass(10).
remark-dscp-pass(10).
remark-dscp-pass(10).
60.5 h3cCBQoSCarRunInfoTable
60.6 h3cCBQoSClassifierCfgInfoTable
This table does not support to modify the variable of existing entry, only supports to
create a new entry and destroy an existing entry.
(2) Use the value as h3cCBQoSClassifierIndex to create the new entry of this
table.
table.
always unavailable(1).
h3cCBQoSMatchRuleCfgInfoTab
le.
60.7 h3cCBQoSFirewallCfgInfoTable
This table does not support to modify the variable of existing entry, only supports to create
a new entry and destroy an existing entry.
60.8 h3cCBQoSGlobalApplyTable
This table does not support to modify the variable of existing entry, only supports to
create a new entry and destroy an existing entry.
60.9 h3cCBQoSIfApplyPolicyTable
This table does not support to modify the variable of existing entry, only supports to
create a new entry and destroy an existing entry.
60.10 h3cCBQoSMatchRuleCfgInfoTable
This table does not support to modify the variable of existing entry, only supports to
create a new entry and destroy an existing entry.
(2) Use the value as h3cCBQoSMatchRuleIndex to create the new entry of this
table.
60.11 h3cCBQoSNestCfgInfoTable
ue
60.12 h3cCBQoSPolicyCfgInfoTable
This table does not support to modify the variable of existing entry, only supports to
create a new entry and destroy an existing entry.
(2) Use the value as h3cCBQoSPolicyIndex to create the new entry of this
table.
always unavailable(0).
h3cCBQoSPolicyClassCfgInfoTa
ble.
60.13 h3cCBQoSPolicyClassCfgInfoTable
(2) Use the value as h3cCBQoSPolicyClassIndex to create the new entry of this
table.
(4) Variables that must be bound when creating a new entry of this table include
h3cCBQoSPolicyClassClassifierIndex and h3cCBQoSPolicyClassBehaviorIndex.
dex
ame
dex
me
e always 2147483647.
60.14 h3cCBQoSRemarkCfgInfoTable
This table does not support to modify the variable of existing entry, only supports to create
a new entry and destroy an existing entry.
typeIpPrecedence(1),
typeDscp(2), typeVlan8021p(4),
typeVlanID(7),
typeDropPrecedence(9),
typeLocalPrecedence(10),
typeTopMostVlanID(11).
60.15 h3cCBQoSVlanApplyPolicyTable
This table does not support to modify the variable of existing entry, only supports to
create a new entry and destroy an existing entry.
on
always 0.
61 H3C-CONFIG-MAN-MIB
A configuration management MIB, includes configuration log management and Backup &
Restore operation of configuration.
All the configuration change events can be managed by the log management MIB. The
configuration may be changed by CLI, SNMP or other ways defined as the MIB.
Backup & Restore MIB group provides the configuration backup and restore among flash,
memory and network.
Flash
Backup(ftp/tft
Resto p)
Restore(ftp/tft
re
p)
Backup(sav
e)
Memory Backup(ftp/tft Network
p)
Restore(ftp/tftp)
61.2 h3cCfgLogTable
All the events of configuration change triggered by SNMP agent will be recorded in
the table. But only four command-line events can be recorded, these events
61.4 h3cCfgOperateTable
61.5 h3cCfgOperateResultTable
The following values of h3cCfgOperateState are implemented for "netFtp" operation with ftp protocol:
- 1: opInProgress(1)
- 2: opSuccess(2)
- 3: opInvalidOperation(3)
- 4: opInvalidProtocol
- 5: opInvalidSourceName
- 7: opInvalidServerAddress(7)
- 8: opDeviceBusy
- 10: opDeviceError(10)
- 12: opDeviceFull(12)
- 13: opFileOpenError(13)
- 14: opFileTransferError(14)
- 16: opNoMemory(16)
- 17: opAuthFail(17)
- 19: opUnknownFailure(19)
The following values of h3cCfgOperateState are implemented for "netFtp" operation with tftp protocol:
- 1: opInProgress(1)
- 2: opSuccess(2)
- 3: opInvalidOperation(3)
- 4: opInvalidProtocol
- 7: opInvalidServerAddress(7)
- 8: opDeviceBusy
- 10: opDeviceError(10)
- 12: opDeviceFull(12)
- 13: opFileOpenError(13)
- 14: opFileTransferError(14)
- 16: opNoMemory(16)
- 19: opUnknownFailure(19)
- 1: opInProgress(1)
- 2: opSuccess(2)
- 10: opDeviceError(10)
61.7 h3cCfgExecuteResultTable
62 H3C-DOMAIN-MIB
62.2 h3cDomainInfoTable
Name Access PDS Description
h3cDomainName not-accessible No As per MIB
h3cDomainState read-create Current As per MIB
h3cDomainMaxAccessNum read-create Current Range from 0 to 2147483646, If
the value is set to 0, the access
limit will be disabled
h3cDomainVlanAssignMode read-create Current Not supported
h3cDomainIdleCutEnable read-create Current As per MIB
h3cDomainIdleCutMaxTime read-create Current As per MIB
h3cDomainIdleCutMinFlow read-create Current Not supported
h3cDomainMessengerEnable read-create Current Not supported
h3cDomainMessengerLimitTime read-create Current Not supported
h3cDomainMessengerSpanTime read-create Current Not supported
62.3 h3cDomainSchemeTable
1) when a domain was created, the agent will create a row for accounting, a row for authentication, a
row for authorization with the value of h3cDomainSchemeMode be ‘local’.
h3cDomainSchemeMode
h3cDomainSchemeAAAType
h3cDomainSchemeAAAName
h3cDomainSchemeAccessMode
h3cDomainSchemeMode
h3cDomainSchemeRowStatus
h3cDomainSchemeAAAType
h3cDomainSchemeAAAName
h3cDomainSchemeAccessMode
63 H3C-FLASH-MAN-MIB
This MIB supplies the information for the management of flash devices.
63.2 h3cFlashTable
63.3 h3cFlhChipTable
63.4 h3cFlhPartitionTable
63.5 h3cFlhFileTable
63.6 h3cFlhOpTable
When ftp protocol is used to transmit file, the values for h3cFlhOperServerUser and
h3cFlhOperPassword must be specified.
1: opInProgress(1)
2: opSuccess(2)
5: opInvalidSourceName(5)
10: opDeviceError(10)
12: opDeviceFull(12)
13: opFileOpenError(13)
14: opFileTransferError(14)
16: opNoMemory(16)
19: opUnknownFailure(19)
1: opInProgress(1)
2: opSuccess(2)
3: opInvalidOperation(3)
5: opInvalidSourceName(5)
6: opInvalidDestName(6)
7: opInvalidServerAddress(7)
10: opDeviceError(10)
12: opDeviceFull(12)
13: opFileOpenError(13)
14: opFileTransferError(14)
16: opNoMemory(16)
17: opAuthFail(17)
19: opUnknownFailure(19)
1: opInProgress(1)
2: opSuccess(2)
5: opInvalidSourceName(5)
20:opDeleteFileOpenError(20),
21:opDeleteInvalidDevice(21),
22:opDeleteInvalidFunction(22),
23:opDeleteOperationError(23),
24:opDeleteInvalidFileName(24),
25:opDeleteDeviceBusy(25),
26:opDeleteParaError(26),
27:opDeleteInvalidPath(27)
64 H3C-SYS-MAN-MIB
Note: The values of these two objects are restricted by each other. The rule will be
identical with CLI. If the values of these two objects are all set to zero together, that means
the user want to abolish summer time, and all the value in this group will be initialization.
64.2 h3cSysCurTable
64.3 h3cSysReloadScheduleTable
64.4 h3cSysImageTable
64.5 h3cSysCFGFileTable
64.6 h3cSysBtmLoadTable
Terms
(The terms listed below are just used in the range of this section.)
BootRom: a special program which is used to boot the system on system startup.
Bootrom file: a file which exists in file system. The content of such file is BootRom.
Function
The responsibility of this table is to update BootRom from a BootRom file in file system
to BOOT ROM.
It assumes that the source Bootrom file already exists in the file system of the device
before doing operation. On system startup, this table is empty.
Notes
1) Be careful that the operation on BOOT ROM updating is risky. Other operations may
halt during updating BOOT ROM. Such operation may take a long time as well.
4) It is strongly recommended that the name of a Bootrom file ends with valid filename
extention, but this table will not check the filename. The verification of validity of a
Bootrom file will be performed after the h3cSysBtmRowStatus of this instance turns into
‘active’.
5) If h3cSysBtmFileName of the instance includes a path, that path must refer to the
same device identified by ‘entityIndex’ part of h3cSysBtmLoadIndex of the instance. If
h3cSysBtmFileName includes just a filename without a path, the root directory will be
used internally.
The Boot Rom in BOOT ROM can not be removed through h3cSysBtmLoadTable, but it
can be updated through this table.
When removing an instance from this table, there is no any deletion of the
corresponding file in file system.
After updating a Bootrom file into BOOT ROM, the corresponding file can be removed
from the file system, but it is not the responsibility of this table to remove a Bootrom file
from the file system.
10)Please refer to the switch guideline to make sure that the module supports
updating.
Examples
h3cSysBtmFileName.131073 = “flash:/s4e01_06.btm”
h3cSysBtmFileType.131073 = ‘main’
h3cSysBtmRowStatus.131073 = ‘createAndGo’
65 H3C-ENTITY-EXT-MIB
65.1 h3cEntityExtStateTable
The information of this MIB depends on the information of the hardware, so As per
MIB when filling the value of items.
65.2 h3cEntityExtManuTable
65.3 h3cEntityExtPowerTable
65.4 h3cProcessTable
entity h3cEntityExtMemUsageThreshold(R/W)
chassis No
backplane No
container No
powerSupply No
fan No
sensor No
module Yes(Only support the Module Level1)
port No
stack No
other No
unknown No
entity h3cEntityExtTemperatureThreshold(R/W)
chassis No
backplane No
container No
powerSupply Yes
fan Yes
sensor No
module Yes
port No
stack No
other Yes
unknown No
entity h3cEntityExtMacAddress
entity h3cEntityExtMacAddress
chassis Yes
backplane No
container No
powerSupply No
fan No
sensor No
module No
port No
stack No
other No
unknown No
entity h3cEntityExtErrorStatus
chassis No
backplane Yes
container Yes
powerSupply Yes
fan Yes
sensor Yes
module No
port Yes
stack No
other Yes
unknown Yes
entity h3cEntityExtManuSerialNum
chassis Yes
backplane No
container No
powerSupply No
fan No
sensor No
module Yes
port No
cpu No
entity h3cEntityExtManuBuildInfo
chassis Yes
backplane No
container No
powerSupply No
fan No
sensor No
module Yes
port No
cpu No
entity h3cEntityExtMacAddressCount
chassis Yes
backplane No
container No
powerSupply No
fan No
sensor No
module Yes
port Yes
cpu No
entity h3cEntityExtManuBOM
chassis Yes
backplane No
container No
powerSupply No
fan No
sensor No
module Yes
port No
cpu No
PLY
h3cEntityExtAdminS Yes
tatus (R/W)
h3cEntityExtOperSt Yes Yes Yes Yes
atus (R)
h3cEntityExtStandb Yes Yes
yStatus (R)
hwEntityExtAlarmLi
ght (R)
h3cEntityExtCpuUs Yes
age (R)
h3cEntityExtCpuUs Yes
ageThreshold (R/W)
h3cEntityExtMemUs Yes
age (R)
h3cEntityExtMemUs Yes
ageThreshold(R/W)
h3cEntityExtMemSi Yes
ze (R)
h3cEntityExtUpTime Yes
(R)
h3cEntityExtTemper Yes Yes Yes
ature (R)
h3cEntityExtTemper Yes Yes Yes
atureThreshold
(R/W)
h3cEntityExtMacAd Yes
dress
h3cEntityExtErrorSt Yes Yes Yes Yes Yes
atus
66 H3C-IF-EXT-MIB
This MIB is an extension of interface MIBs such as IF-MIB. This MIB is applicable to
switches. Some objects in this may be used only for some specific switch s, so users
should refer to the related documents to acquire more detail information.
66.2 h3cUIMgtBasicGroup
67 H3C-IP-ADDRESS-MIB
67.2 h3cIpAddrSetTable
This table does not support modify the variable of exist entry, only support create a new
entry and destroy an exist entry.
67.3 h3cIpAddrReadTable
68 H3C-IP-BROADCAST-MIB
This MIB is used to set whether a device receives direct broadcast datagram.
68.1 h3cIpForwardBroadcast
69 H3C-IPV6-ADDRESS-MIB
69.1 h3cIpv6AddrSetTable
This table does not support modify the variable of exist entry, only support create a new
entry and destroy an exist entry.
69.2 h3cIpv6AddrReadTable
70 H3C-MIRRORGROUP-MIB
71 H3C-MPM-MIB
71.2 h3cMPortGroupJoinTable
71.3 h3cMPortGroupTable
71.4 h3cMPortConfigTable
72 H3C-NQA-MIB
This MIB should be supported by device which implements disman ping function.
This MIB cannot mix using with CLI.
72.2 h3cNqaCtlTable
b) Once the configuration is modified, the result, histories, and statistics of the
corresponding entry will be cleared.
c) The results, histories and statistics must be the factual reflection of the test
results of current configurations.
d) Users will be puzzled when they get the results which caused by the previous
configurations.
pingIcmpEcho h3cNqaCtlTTL
h3cNqaCtlVPNInstance
pingUdpEcho h3cNqaCtlTargetPort
h3cNqaUdpEcho h3cNqaCtlSourcePort
h3cNqaCtlTTL
pingSnmpQuery h3cNqaCtlSourcePort
h3cNqaCtlTTL
pingTcpConnectionAttempt h3cNqaCtlTargetPort
h3cNqaTcpconnect h3cNqaCtlTTL
h3cNqaCtlJitterAdminInterval
h3cNqaCtlJitterAdminNumPackets
h3cNqaCtlCodecType
h3cNqaCtlJitterAdminNumPackets
h3cNqaCtlICPIFAdvFactor
h3cNqaCtlCodecType
h3cNqaHttp h3cNqaCtlTTL
h3cNqaCtlHttpOperationType
h3cNqaCtlHttpOperationString
h3cNqadlsw h3cNqaCtlTTL
h3cNqadhcp
h3cNqaftp h3cNqaCtlTTL
h3cNqaCtlFtpOperationType
h3cNqaCtlFtpUsername
h3cNqaCtlFtpPassword
h3cNqaCtlFtpOperationString
“pingUdpEcho” or
“pingTcpConnectionAttempt”, the
"h3cNqaUdpEcho" or
“HTTP/1.0”(case- insensitive).
to 200
to 31.
be set.
invalid.
test.
g711Ulaw or g729A to
notDefined, the entry of voice
codec-type configuration.
and g729A..
72.3 h3cNqaResultsTable
included in DISMAN-PING-MIB
72.4 h3cNqaJitterStatsTable
SD
SD
SD
SD
SD
sSD
SD
SD
DS
DS
DS
DS
DS
sDS
DS
DS
(statistical summation)/
(statistical times).
expression: (statistical
72.5 h3cNqaTcpServerTable
72.6 h3cNqaUdpServerTable
72.7 h3cNqaStatisticsCtlTable
supported.
supported.
Range from 0 to
h3cNqaStatsMaxGroupNumber,
default value is 2.
supported.
never stop.
72.8 h3cNqaStatisticsResultsTable
ype
72.9 h3cNqaGroupStatsJitterTable
SD
gSD
gDS
h3cNqaStatJitterMinOfMOS read-only No
Only voice test is supported ,the
73 H3C-PORT-SECURITY-MIB
t notify
73.2 h3cSecureRalmObjects
me
value is set to
papUsernameAsMacAddress(1),
h3cSecureRalmAuthUsername
and
h3cSecureRalmAuthPassword
values.
When h3cSecureRalmAuthMode
value is set to
papUsernameFixed(2),
h3cSecureRalmAuthUsername
and
h3cSecureRalmAuthPassword
supported.
tTime
73.3 h3cSecureBindingTable
value of h3cSecureBindingIndex
is 2048.
74 H3C-POWER-ETH-EXT-MIB
74.2 h3cPsePortTable
74.3 h3cMainPseTable
74.4 h3cPseProfilesTable
74.5 h3cPOEModuleInfoTable
74.6 h3cPOEDCOutStateTable
74.7 h3cPOEDCOutInfoTable
74.8 h3cPOEACSwitchStateTable
74.9 h3cPOESwitchStateVolExTable
74.10 h3cPOEAlarmStateInfoTable
75 H3C-QINQ-MIB
75.2 h3cQINQBpduTunnelTable
Name Access PDS Description
h3cQinQProtocolIndex not-accessible Current Only support stp(2)
h3cQinQBpduRowStatus read-create Current Active, createAndGo and Destroy
operation support only
75.3 h3cQinQIfConfigTable
Name Access PDS Description
h3cQinQIfEthernetType read-create Current Not supported.
h3cQinQIfSwitch read-create Current As per MIB
h3cQinQIfRowStatus read-create Current Active, createAndGo and Destroy
operation support only
h3cQinQIfServiceTPIDValue read-create Current As per MIB
h3cQinQIfCustomerTPIDValue read-create Current Not supported
h3cQinQIfUplinkSwitch read-create Current As per MIB
h3cQinQIfDownlinkSwitch read-create Current As per MIB
76 H3C-QOS-CAPABILITY-MIB
76.1 h3cQoSCapabilityTable
77 H3C-RRPP-MIB
77.2 h3cRrppDomainTable
2 to 4093. Sub-VLAN ID is
major-VLAN ID plus 1.
will be deleted.
77.3 h3cRrppRingTable
77.4 h3cRrppPortTable
78 H3C-RADIUS-MIB
78.1 h3cRdInfoTable
Name Access PDS Description
h3cRdGroupName not-accessible No The length of this object is range
from 1 to 32
h3cRdPrimAuthIp read-create Current Not supported
h3cRdPrimUdpPort read-create Current The range of primary UDP port is
from 1 to 65535.
h3cRdPrimState read-create No As per MIB
h3cRdSecAuthIp read-create Current Not supported
h3cRdSecUdpPort read-create Current The range of secondary UDP port
is from 1 to 65535
78.2 h3cRdAccInfoTable
Name Access PDS Description
h3cRdAccGroupName not-accessible No As per MIB
h3cRdPrimAccIpAddrType read-create Current Support IPv4 only
h3cRdPrimAccIpAddr read-create Current Support IPv4 only
h3cRdPrimAccUdpPort read-create Current The range of primary UDP port is
from 1 to 65535
h3cRdPrimAccState read-create No As per MIB
h3cRdSecAccIpAddrType read-create Current Support IPv4 only
h3cRdSecAccIpAddr read-create Current Support IPv4 only
h3cRdSecAccUdpPort read-create Current The range of secondary UDP port
is from 1 to 65535
h3cRdSecAccState read-create No As per MIB
h3cRdAccKey read-create Current As per MIB
h3cRdAccRetry read-create Current The range of retry times is from 1
to 20
h3cRdAccTimeout read-create Current Range from 1 to 10
h3cRdAccServerType read-create Current only standard(1) and extended(4)
are supported
h3cRdAccQuietTime read-create Current As per MIB
h3cRdAccFailureAction read-create Current Not supported
h3cRdAccRealTime read-create Current As per MIB
h3cRdAccRealTimeRetry read-create Current As per MIB
78.3 h3cRadiusAccServerTable
78.4 h3cRadiusAuthServerTable
79 H3C-PROTOCOL-VLAN-MIB
79.2 h3cProtocolVlanTable
79.3 h3cProtocolVlanPortTable
80 H3C-SUBNET-VLAN-MIB
80.2 h3cSubnetVlanTable
Name Access PDS Description
h3cSubnetVlanVlanId not-accessible Current As per MIB
h3cSubnetVlanSubnetIndex not-accessible Current As per MIB
h3cSubnetVlanVlanIpAddressType read-create Current Support creation but not support
modification
h3cSubnetVlanIpAddressValue read-create Current Support creation but not support
modification
h3cSubnetVlanNetMaskValue read-create Current Support creation but not support
modification
h3cSubnetVlanRowStatus read-create No As per MIB
80.3 h3cSubnetVlanPortCreateTable
81 H3C-UI-MAN-MIB
81.2 h3cVtyAccTable
82 H3C-USER-MIB
82.2 h3cUserInfoTable
82.3 h3cUserAttributeTable
82.4 h3cUserGroupInfoTable
83 HUAWEI-NTP-MIB
83.1 hwNTPSystemMIBObjects
83.2 hwNTPPeerTable
Name Access PDS Description
hwNTPPeerConfig read-only No As per MIB
hwNTPPeerAuthenable read-only No As per MIB
hwNTPPeerAuthentic read-only No As per MIB
hwNTPPeerRemAdr not-accessible No As per MIB
hwNTPPeerRemPort read-only No As per MIB
hwNTPPeerLocAdr read-only No As per MIB
hwNTPPeerLocPort read-only No As per MIB
hwNTPPeerLeap read-only No As per MIB
hwNTPPeerHMode not-accessible No As per MIB
hwNTPPeerStratum read-only No As per MIB
hwNTPPeerPPoll read-only No As per MIB
hwNTPPeerHPoll read-only No As per MIB
hwNTPPeerPrecision read-only No As per MIB
hwNTPPeerRootDelay read-only No This is a signed fixed-point
number indicating the total
roundtrip delay to the primary
reference source at the root of
the synchronization subnet, in
milliseconds. Note that this
variable can take on both positive
and negative values, depending
on clock precision and skew.
84 H3C-DHCPRELAY-MIB
84.1 h3cDHCPRStatisticsGroup
84.2 h3cDHCPRIfSelectTable
84.3 h3cDHCPRIpToGroupTable
84.4 h3cDHCPRIfToGroupTable
84.5 h3cDHCPRAddrCheckTable
84.6 h3cDHCPRSecurityTable
84.7 h3cDHCPRConfigOption82IfTable
85 H3C-DLDP-MIB
h3cDLDPAuthenticationPasswor
d.
characters or equal to 24
characters.When equal to 24
h3cDLDPAuthenticationPassword read-write Current
characters,
h3cDLDPAuthenticationMode
85.2 h3cDLDPPortStateTable
85.3 h3cDLDPPortDLDPTable
85.4 h3cDLDPNeighborTable
86 H3C-EPON-MIB
The objects in this MIB module are used to manage and display current
configuration of Ethernet Passive Optical Network (EPON) port which are based on
the Ethernet in the First Mile (EFM) PON as defined in IEEE Draft P802.3ah/D3.0
clause 60, 64, 65.
86.2 h3cEponSysManTable
86.3 h3cEponAutoUpdateTable
86.4 h3cEponOuiIndexNextTable
86.5 h3cEponOuiTable
86.6 h3cEponMulticastControlTable
86.7 h3cOltSysManTable
86.8 h3cOltInfoTable
86.9 h3cOltDbaManTable
86.10 h3cOltPortAlarmThresholdTable
86.11 h3cOnuSysManTable
86.12 h3cOnuLinkTestTable
86.13 h3cOnuBandWidthTable
86.14 h3cOnuSlaManTable
86.15 h3cOnuInfoTable
86.16 h3cOnuMacAddrInfoTable
86.17 h3cOnuBindMacAddrTable
86.18 h3cOnuFirmwareUpdateTable
86.19 h3cEponOnuTypeManTable
86.20 h3cOnuPacketManTable
86.21 h3cOnuProtocolTable
86.22 h3cOnuDot1xTable
86.23 h3cOnuPriorityQueueTable
86.24 h3cOnuCountTable
86.25 h3cOnuQueueBandwidthTable
86.26 h3cOnuIpAddressTable
86.27 h3cOnuChipSetInfoTable
86.28 h3cOnuCapabilityTable
86.29 h3cOnuDbaReportTable
86.30 h3cOnuCosToLocalPrecedenceTable
86.31 h3cEponBatchOperationBySlotTable
86.32 h3cEponBatchOperationByOLTTable
86.33 h3cEponStatTable
87 H3C-DOT3-EFM-EPON-MIB
87.1 h3cdot3MpcpTable
87.2 h3cDot3MpcpStatTable
This table defines the list of statistics counters of [802.3ah] clause 64 MPCP interface.
87.3 h3cDot3OmpEmulationTable
87.4 h3cDot3OmpEmulationStatTable
87.5 h3cDot3EponMauTable
88 H3C-EFM-COMMON-MIB
88.1 h3cDot3OamTable
Name Access PDS Description
h3cDot3OamAdminState read-write No Not supported
h3cDot3OamOperStatus read-only No Not supported.
88.2 h3cDot3OamPeerTable
Name Access PDS Description
h3cDot3OamPeerStatus read-only No Not supported
h3cDot3OamPeerMacAddress read-only No Not supported
h3cDot3OamPeerVendorOui read-only No Not supported
h3cDot3OamPeerVendorInfo read-only No Not supported
h3cDot3OamPeerMode read-only No Not supported
h3cDot3OamPeerMaxOamPduSiz read-only No Not supported
e
h3cDot3OamPeerConfigRevision read-only No Not supported
h3cDot3OamPeerFunctionsSuppo read-only No Not supported.
rted
88.3 h3cDot3OamLoopbackTable
Name Access PDS Description
h3cDot3OamLoopbackCommand read-write No Not supported
h3cDot3OamLoopbackStatus read-only No Not supported
h3cDot3OamLoopbackIgnoreRx read-write No Not supported
88.4 h3cDot3OamStatsTable
Name Access PDS Description
h3cDot3OamInformationTx read-only No Not supported
h3cDot3OamInformationRx read-only No Not supported
h3cDot3OamUniqueEventNotificati read-only No Not supported.
onTx
h3cDot3OamUniqueEventNotificati read-only No Not supported
onRx
h3cDot3OamDuplicateEventNotific read-only No Not supported.
ationTx
88.5 h3cDot3OamEventConfigTable
Name Access PDS Description
h3cDot3OamErrSymPeriodWindo read-write No Not supported
wHi
h3cDot3OamErrSymPeriodWindo read-write No Not supported
wLo
h3cDot3OamErrSymPeriodThresh read-write No Not supported
oldHi
h3cDot3OamErrSymPeriodThresh read-write No Not supported.
oldLo
h3cDot3OamErrSymPeriodEvNotif read-write No Not supported.
Enable
h3cDot3OamErrFramePeriodWind read-write No Not supported.
ow
h3cDot3OamErrFramePeriodThre read-write No Not supported
shold
h3cDot3OamErrFramePeriodEvNo read-write No Not supported
tifEnable
h3cDot3OamErrFrameWindow read-write No Not supported
h3cDot3OamErrFrameThreshold read-write No Not supported
88.6 h3cDot3OamEventLogTable
Name Access PDS Description
h3cDot3OamEventLogIndex not-accessible No Not supported
h3cDot3OamEventLogTimestamp read-only No Not supported
h3cDot3OamEventLogOui read-only No Not supported
h3cDot3OamEventLogType read-only No Not supported
h3cDot3OamEventLogLocation read-only No Not supported
h3cDot3OamEventLogWindowHi read-only No Not supported
h3cDot3OamEventLogWindowLo read-only No Not supported
h3cDot3OamEventLogThresholdH read-only No Not supported
i
h3cDot3OamEventLogThresholdL read-only No Not supported
o
h3cDot3OamEventLogValue read-only No Not supported
h3cDot3OamEventLogRunningTot read-only No Not supported
al
h3cDot3OamEventLogEventTotal read-only No Not supported
89 H3C-EPON-DEVICE-MIB
89.1 h3cEponDeviceControlTable
Name Access PDS Description
h3cEponDeviceObjectReset read-write No Not supported
h3cEponDeviceObjectModes read-only No As per MIB
h3cEponDeviceObjectFecEnabled read-write No Only support read operation
89.2 h3cEponDeviceRemoteMACAddressLLIDTable
Name Access PDS Description
h3cEponDeviceRemoteMACAddre read-create No Only support read operation
ssLLIDName
h3cEponDeviceRMadlLLID read-create No Only support read operation
h3cEponDeviceRMadlLogID read-create No Only support read operation
h3cEponDeviceRMadlRemoteAdd read-create No Only support read operation
ress
h3cEponDeviceRMadlType read-create No Only support read operation
h3cEponDeviceRMadlAction read-create No As per MIB
h3cEponDeviceRMadlEntryStatus read-create No As per MIB
89.3 h3cEponDeviceStatTable
Name Access PDS Description
h3cEponDeviceStatTxFramesQue read-only No Not supported
ue0
h3cEponDeviceStatTxFramesQue read-only No Not supported
ue1
h3cEponDeviceStatTxFramesQue read-only No Not supported
ue2
h3cEponDeviceStatTxFramesQue read-only No Not supported
ue3
h3cEponDeviceStatTxFramesQue read-only No Not supported
ue4
89.4 h3cEponDeviceEventsLogTable
Name Access PDS Description
h3cEponDeviceSampleMinimum read-write No Not supported
h3cEponDeviceDyingGaspAlarmSt read-only No Not supported
ate
h3cEponDeviceDyingGaspAlarmE read-write No Not supported
nabled
h3cEponDeviceCriticalEventState read-only No Not supported
h3cEponDeviceCriticalEventEnabl read-write No Not supported
ed
h3cEponDeviceLocalLinkFaultAlar read-only No Not supported
mState
h3cEponDeviceLocalLinkFaultAlar read-write No Not supported
mEnabled
h3cEponDeviceTemperatureEventI read-only No Not supported
ndicationState
h3cEponDeviceTemperatureEventI read-write No Not supported
ndicationEnabled
h3cEponDevicePowerVoltageEven read-only No Not supported
tIndicationState
h3cEponDevicePowerVoltageEven read-write No Not supported
tIndicationEnabled
h3cEponDeviceGlobalEventState read-only No Not supported
h3cEponDeviceGlobalEventEnabl read-write No Not supported
ed
h3cEponDeviceErroredSymbolPeri read-only No Not supported
odEventState
h3cEponDeviceErroredSymbolPeri read-write No Not supported
odEventEnabled
h3cEponDeviceErroredFrameEve read-only No Not supported
ntState
h3cEponDeviceErroredFrameEve read-write No Not supported
ntEnabled
h3cEponDeviceErroredFramePeri read-only No Not supported
odEventState
h3cEponDeviceErroredFramePeri read-write No Not supported
odEventEnabled
89.5 h3cEponDeviceEventsLogTable
Name Access PDS Description
h3cEponDeviceEventsLogName not-accessible No Not supported
h3cEponDeviceEventsLogIndex not-accessible No Not supported
h3cEponDeviceEventsLogID read-create No Not supported
h3cEponDeviceEventsLogFirstTim read-only No Not supported
e
h3cEponDeviceEventsLogLastTim read-only No Not supported
e
h3cEponDeviceEventsLogCounts read-only No Not supported
h3cEponDeviceEventsLogType read-only No Not supported
h3cEponDeviceEventsLogEntrySt read-create No Not supported
atus
90 H3C-EPON-FB-MIB
90.1 h3cEponFBMIBTable
91 H3C-EPON-UNI-MIB
This MIB is used to manage user interfaces. The VOIP port, which is an interface used for
telephone of the ONU and whose index ranges from 81 to 144, only supports
h3cEponUniIndex and h3cEponUniAdminStatus in this MIB module.
91.1 h3cEponUniParaMan
Scalar Objects:
91.2 h3cEponUniSysManTable
91.3 H3cEponUniCountTable
91.4 h3cEponUniIgmpInfoTable
91.5 h3cEponUniPortPolicyTable
91.6 h3cEponUniMulticastTable
91.7 h3cEponUniTechAbilityTable
91.8 h3cEponUniMulticastControlTable
91.9 h3cEponUniQosIndexNextTable
91.10 h3cEponUniQosConfTable
91.11 h3cEponUniQosRuleTable
91.12 h3cEponUniMirrorGroupTable
91.13 h3cEponUniMirrorGroupIdNextTable
91.14 h3cEponUniMulticastCtrlInfoTable
91.15 h3cEponUniMulticastIndexNextTable
92 H3C-SSH-MIB
92.2 h3cSSHUserConfigTable
Name Access PDS Description
h3cSSHUserName not-accessible Current The length of value is from 1 to
80.
h3cSSHUserServiceType read-create Current The default value is invalid(1).
h3cSSHUserAuthType read-create Current The default value is invalid(1).
When this object is set to
password, means that this user
uses password authentication in
AAA(Authentication,
Authorization, Accounting)
module.
When this object is set to
publicKey, means that this user
uses public key authentication in
PKEY(Public Key) module.
When this object is set to any,
means that this user uses either
password authentication or
publickey authentication.
When this object is set to
publicKeyPassword, means that
this user uses both publickey
authentication and password
authentication.
h3cSSHUserPublicKeyName read-create Current The length of value is from 1 to
64.
The default value is null string.
This object only can get value
from an existent public key, which
is managed in PKEY (Public Key)
module.
h3cSSHUserWorkDirectory read-create Current The length of value is from 1 to
135.
The default value is null string.
When `h3cSSHUserRowStatus'
is set to active(1), no object in the
conceptual row can be modified.
In particular, a newly created
SFTP user row cannot be made
active(1) until the corresponding
instance of
`h3cSSHUserServiceType' is
'sftp' or 'all', and the
'h3cSSHUserWorkDirectory' is
configured appropriately.
In particular, a newly created user
row which uses public key
authentication cannot be made
active(1) until the corresponding
instance of
`h3cSSHUserAuthType' is
'publicKey' or
'publicKeyPassword', and the
'h3cSSHUserPublicKeyName' is
configured appropriately.
92.3 h3cSSHSessionInfoTable
Name Access PDS Description
h3cSSHSessionID not-accessible No As per MIB
h3cSSHSessionUserName read-only No The length of value is from 1 to
80.
h3cSSHSessionUserIpAddrType read-only No As per MIB
h3cSSHSessionUserIpAddr read-only No As per MIB
h3cSSHSessionServiceType read-only No As per MIB
h3cSSHSessionClientVersion read-only No As per MIB
h3cSSHSessionEncry read-only No As per MIB
h3cSSHSessionState read-only No As per MIB
93 H3C-MAC-INFORMATION-MIB
93.2 h3cMACInfomationIfTable
Name Access PDS Description
h3cMACLearntEnable read- write Current As per MIB
h3cMACRemovedEnable read- write Current As per MIB
94 H3C-STORM-CONSTRAIN
The storm-constrain provides the function to control a port forwarding state. If all types of
the flux in normal, the port will be in normal (forwarding) state. If any type of the flux
exceeds its upper limit, the port will be change into controlled (discarding) state to avoid
packets storm. When all flux of the port which exceed upper limit falling under their lower
limit, the port in controlled (discarding) will recover normal (forwarding) state.
95 Supported Traps
This section contains a list of the traps/notification defined in the standard MIB
(defined by IETF, IEEE or other standard organization).
cation
cation
ence
ch
ch
This section contains a list of the traps defined in the private MIB(defined by enterprise).
Notfication
supported.
dNotification
supported.
maintenance responsibility
on
on
on
tion
hwSlaveSwitchOver HUAWEI-LswMix-MIB
erToNormal
rToNormal
ap
ap
erTrap
verTrap
verTrap
erTrap
ap
overTrap
vent
verEvent
Trap
protocol version.
p B