Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Secret
Revision: V2.01
31 LLDP-EXT-DOT1-MIB ......................................................................................... 96
31.1 lldpXdot1ConfigPortVlanTable ............................................................................ 97
31.2 lldpXdot1ConfigVlanNameTable ......................................................................... 97
31.3 lldpXdot1ConfigProtoVlanTable .......................................................................... 97
31.4 lldpXdot1ConfigProtocolTable ............................................................................ 97
31.5 lldpXdot1LocTable .............................................................................................. 97
31.6 lldpXdot1LocProtoVlanTable .............................................................................. 97
31.7 lldpXdot1LocVlanNameTable ............................................................................. 98
31.8 lldpXdot1RemTable ............................................................................................. 99
31.9 lldpXdot1RemProtoVlanTable ............................................................................. 99
31.10 lldpXdot1RemVlanNameTable ............................................................................ 99
31.11 lldpXdot1RemProtocolTable ............................................................................... 99
32 LLDP-EXT-DOT3-MIB ......................................................................................... 99
32.1 lldpXdot3PortConfigTable ................................................................................. 100
32.2 lldpXdot3LocPortTable ...................................................................................... 100
32.3 lldpXdot3LocPowerTable .................................................................................. 100
32.4 lldpXdot3LocLinkAggTable ............................................................................... 101
32.5 lldpXdot3LocMaxFrameSizeTable .................................................................... 101
32.6 lldpXdot3RemPortTable .................................................................................... 101
32.7 lldpXdot3RemPowerTable ................................................................................ 102
32.8 lldpXdot3RemLinkAggTable ............................................................................. 102
32.9 lldpXdot3RemMaxFrameSizeTable .................................................................. 102
33 LLDP-MIB........................................................................................................... 103
33.1 Scalar Objects ................................................................................................... 104
33.2 lldpPortConfigTable ........................................................................................... 104
33.3 lldpConfigManAddrTable................................................................................... 104
33.4 lldpStatsTxPortTable ......................................................................................... 105
33.5 lldpStatsRxPortTable ........................................................................................ 105
33.6 lldpLocPortTable ............................................................................................... 105
33.7 lldpLocManAddrTable ....................................................................................... 106
33.8 lldpRemTable .................................................................................................... 106
33.9 lldpRemManAddrTable ..................................................................................... 107
33.10 lldpRemUnKnownTLVTable .............................................................................. 107
33.11 lldpRemOrgDefInfoTable .................................................................................. 107
34 A3COM-HUAWEI-TRNG-MIB ........................................................................... 108
34.1 hwTrngCreateTimerangeTable ......................................................................... 108
when creating the row. After a row created, all the instance of this row can not be
changed. .................................................................................................................. 196
70.3 h3cvoiceVlanPortTable ..................................................................................... 197
71 A3COM-HUAWEI-UI-MAN-MIB ......................................................................... 197
71.1 Scalar Objects ................................................................................................... 197
71.2 h3cVtyAccTable ................................................................................................ 197
72 A3COM-HUAWEI-USER-MIB ............................................................................ 198
72.1 h3cUserInfoTable .............................................................................................. 199
72.2 h3cUserAttributeTable ...................................................................................... 200
72.3 h3cUserGroupInfoTable .................................................................................... 203
73 A3COM-HUAWEI-ENTRELATION-MIB ............................................................ 203
73.1 h3cEntRelationTable ......................................................................................... 203
74 H3C-NTP-MIB .................................................................................................... 204
74.1 hwNTPPeerMIBObjects .................................................................................... 204
74.2 hwNTPPeerTable .............................................................................................. 205
75 A3COM-HUAWEI-CONFIG-MAN-MIB .............................................................. 208
75.1 Scalar objects of h3cCfgLog group ................................................................... 209
75.2 h3cCfgLogTable ................................................................................................ 209
75.3 Scalar objects of h3cCfgOperate group ............................................................ 210
75.4 h3cCfgOperateTable ......................................................................................... 211
75.5 h3cCfgOperateResultTable .............................................................................. 212
75.6 Scalar objects of h3cCfgExecuteOperate group .............................................. 214
76 A3COM-HUAWEI-TUNNEL-MIB ....................................................................... 214
76.1 h3cTunnelIfTable............................................................................................... 214
76.2 h3cTunnelInetConfigTable ................................................................................ 216
77 A3COM-HUAWEI-DHCPRELAY-MIB................................................................ 216
77.1 h3cDHCPRStatisticsGroup ............................................................................... 216
77.2 h3cDHCPRIfSelectTable................................................................................... 218
77.3 h3cDHCPRIpToGroupTable ............................................................................. 218
77.4 h3cDHCPRIfToGroupTable .............................................................................. 218
77.5 h3cDHCPRAddrCheckTable ............................................................................. 218
77.6 h3cDHCPRSecurityTable.................................................................................. 218
77.7 h3cDHCPRConfigOption82IfTable ................................................................... 219
78 A3COM-HUAWEI-MAC-INFORMATION-MIB ................................................... 219
78.1 Scalar objects .................................................................................................... 219
78.2 h3cMACInfomationIfTable................................................................................. 220
I Revision History
(5) h3cFlhPos
(6) h3cCfgExecuteOperateResultTable
2. Add h3cSysBtmLoadTable
3. Copy A3COM-HUAWEI-PORT-SECURITY-MIB
from Aragog Mib companion
snmpTargetAddrTable
according V5 mib companion revision
5. modify the description of
h3cCfgRunModifiedLast according V5 mib
companion revision
6. modify the description of SysDescr to keep
consistent with F1
Purpose
This document describes all of MIBs and the MIB objects which are supported by
4510G devices.
Introduction
Firstly, the Public MIBs List and Private MIBs list should be read by users who refer to this
document.
Secondly, if a MIB is not listed in this document, then it must not be supported.
Thirdly, although there are many MIBs listed in this document, the specific features and/or
functions should be implemented and/or supported firstly before the corresponding MIBs
are supported.
If a MIB is not supported or implemented, then the notifications or traps (if existed) of the
MIB are not supported as well.
In the tables in which the detail of MIB objects are filled, the explanations of the header of
the column are stated here:
Access The access/max-access value as defined in MIBs. For trap objects, the contents of
PDS Permanent data storage (See below for further explanation). For trap objects, the
'Yes' means that one object would be saved automatically if its value changed.
‘No' means that the value of the object could not be saved. Even if its value has
changed when the device is running, after the device reboots, the value will changed
‘Current’ means that when the value of an object changes, if saved explicitly, the
value would be what it has been set after the device reboots. Otherwise, the value
would be returned to its original value or be lost after the device reboots
Description General comments, all specific or products related information should be placed
‘Need confirm by products’: Detail information about the MIB object are different
among products
If the meaning of a MIB is not clearly described in tables, or other information would be
provided, an independent section could be appended after/before the related MIBs or
tables.. That is, further descriptions may be given below the tables, at the beginning of the
section. These descriptions can be written as a paragraph, a formula, a chart, etc.
If, for a MIB, there is a difference between products, further information should be
provided to explain such a gap.
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.
nts
Group of rfc1213
IPv6 Interface
Management
1AB
Port Priority
GARP
GMRP
mib
GVRP
t.mib
nts
B nt.mib
Route Management
TCP
UDP
ARP
SNMP
System Management
k.mib
n.mib
IB Management
mib
rfc3418-snmpv2.mib rfc3418
MIB Management
Group of rfc1213
-acl.mib
-cbqos2.mib
N-MIB -config-man.mib
-MIB -dhcprelay.mib
-dldp.mib
-domain.mib
MIB -enitty-ext.mib
A3COM-HUAWEI-ENTITY-VEN a3com-huawei
DORTYPE-OID-MIB -entity-vendortype-o
id.mib
N-MIB -entrelation.mib
MIB -flash-man.mib
-MIB -ip-address.mib
ST-MIB -ip-broadcast.mib
SS-MIB -ipv6-address.mib
UP-MIB -mirrorgroup.mib
-mpm.mib
-nqa.mib
A3COM-HUAWEI-PORT-SECU a3com-huawei
RITY-MIB -port-security.mib
EXT-MIB -power-eth-ext.mib
VLAN-MIB -protocol-vlan.mib
-qinq.mib
LITY-MIB -qos-capability.mib
-radius.mib
STRAIN-MIB -storm-constrain.mi
-rrpp.mib
B -sys-man.mib Management
-ui-man.mib
-user.mib
-MIB -voice-vlan.mib
-8021x-ext.mib
-hgmp.mib
-lag.mib
B -splat-devm.mib Management
-splat-inf.mib Management
B -splat-mam.mib
FDB table
B -splat-mstp.mib
B -splat-trap.mib
B -splat-vlan.mib
MIB -splat-performance.
mib
-trng.mib
-STORM-CONSTRAIN-MIB -storm-constrain
3 RFC1213-MIB
Switch4510G-24
1.3.6.1.4.1.43.1.16.4.3.31----
Switch4510G-48
1.3.6.1.4.1.43.1.16.4.3.32----
Switch4510G-24-PWR
1.3.6.1.4.1.43.1.16.4.3.33---
- Switch4510G-24-PWR
sysUpTime read-only No As per MIB
sysContact read-write Current “3Com Corporation.”
sysName read-write Current “4510G”
The set operation now only
supports 1-30 characters
Space can not be included in
the string assigned to this
object
sysLocation read-write Current "Marlborough, MA 01752
USA"
sysServices read-only Current 78 (2^ (2-1) + 2^ (3-1) + 2^
(4-1) + 2^ (7-1)). indicates
that can provide the
following services:
2 datalink/subnetwork (e.g.,
bridges)
3 internet (e.g., supports the
IP)
4 end-to-end (e.g.,
supports the TCP)
7 applications (e.g.,
supports the SMTP)
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.5.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.
If the snmpEngineID has been configured and its value differs from the former one, then
the snmpEngineBoots is reverted to 1.
If the snmpEngineTime reachs its maximum value then the snmpEngineBoots increments 1.
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
8.5 ifRcvAddressTable
9 RIPv2-MIB
9.2 rip2IfStatTable
9.3 rip2IfConfTable
9.4 rip2PeerTable
10 RADIUS-ACC-CLIENT-MIB
10.2 radiusAccServerTable
11 RADIUS-AUTH-CLIENT-MIB
11.2 radiusAuthServerTable
12 EtherLike-MIB
12.1 dot3StatsTable
12.2 dot3ControlTable
12.3 dot3PauseTable
13 MAU-MIB
14 ENTITY-MIB
This document 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
‘stack (11)', '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 an agent represents multiple logical entities with this MIB, then this
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
2006-03-30 Confidential Information of H3C. Page 48 of 231
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.
The following table shows the index range of each physical class of each unit in Gryffindor
products. In Gryffindor products, there are 1 solt, 1 PSU, 1 RPS and 1 Fan as level 1
containers, and there are 3 subslots as level 2 containers. They are front panel subslot,
stacking ports subslot, expansion card subslot. The max port number in a subslot is 52,
including 48 RJ45 fixed ports and 4 SFP ports. Such as the figure and the table shown:
FAN 10 fan(7) 6 1
SubSlot0 11 container(5) 7 0
SubSlot1 12 container(5) 7 1
SubSlot2 13 container(5) 7 2
SubCard0(Front Panel) 14 module(9) 11 1
SubCard1(Expan Card 15 module(9) 12 1
1)
SubCard2(Expan Card 16 module(9) 13 1
2)
Port on front panel 17 port(10) 14 1
Port on front panel 18 port(10) 14 2
… 19 port(10) 14 3
Port on expansion card 69 port(10) 15 1
1
Port on expansion card 70 port(10) 15 2
1
Port on expansion card 71 port(10) 16 1
2
Port on expansion card 72 port(10) 16 2
2
14.1 entPhysicalTable
A3COM-HUAWEI-ENTITY-VEN
DORTYPE-OID-MIB. When
described separately.
In the following table, if the entity is a virtual one, the objects except for the
“entPhysicalContainedIn” and “entPhysicalParentRelPos” are meaningless to that entity.
entity entPhysicalDescr
if the entity has value in VendorType MIB, that value will be filled in.
if no value in VendorType MIB, but some poduct request, the request value
will be filled in.
if no value in VendorType MIB and no request, a null string will filled in.
Unit Number of device model.
For Gryffindor 24, it should be “3Com Switch 4510G 24-Port Software
Version 3Com OS V5.01.00s56” or
“3Com Switch 4510G 24-Port Software Version 3Com OS V5.01.00s168”
Fabric NULL
entity entPhysicalContainedIn()
Unit see index range table above
Slot see index range table above
SubSlot see index range table above
PowerSupply see index range table above
Fan see index range table above
Board see index range table above
SubCard see index range table above
Port see index range table above
Fabric see index range table above
entity entPhysicalClass
Unit chassis(3)
Slot container(5)
SubSlot container(5)
PowerSupply PowerSupply(6)
Fan fan(7)
Board module(9)
SubCard module(9)
Port Port(10)
Fabric stack(11)
entity entPhysicalParentRelPos
Unit see index range table above
Slot see index range table above
SubSlot see index range table above
PowerSupply see index range table above
Fan see index range table above
Board see index range table above
SubCard see index range table above
Port see index range table above
Fabric see index range table above
entity entPhysicalName.
Unit “4510G”
Slot NULL
SubSlot NULL
PowerSupply “PowerSupply”
Fan “Fan1”
Board None
SubCard ”SubCard”+SubCardNO;like “SubCard0” [0..2]
Port Port_Type + UnitID/SubslotID/Port_Number, like “GigabitEthernet 1/0/1”
Fabric NULL
entity entPhysicalHardwareRev
Unit PCB version of Slot0
Slot None
SubSlot None
PowerSupply not available
Fan not available
Board None, because it is a logical (virtual) entity.
SubCard PCB version of SubCard
Port None
Fabric None
entity entPhysicalFirmwareRev
Unit Bootrom version of Slot0
Slot None
SubSlot None
PowerSupply None
Fan None
Board None,
SubCard None
Port None
Fabric None
Unit The software version will follow the format: ww.xx.yySzzCaa, here the ww is
the main platform version, the xx is the product main revision number and yy
is the build number of the software and zz is encryption method of software
(56 or 168) and the aa is the release candidate, so the first software image
will show such version information: 5.01.00s56c01
Slot None
SubSlot None
PowerSupply None
Fan None
Board None
SubCard None
Port None
Fabric None
entity entPhysicalSerialNum
Unit Customer Visible Serial Number
Slot None
SubSlot None
PowerSupply None
Fan None
Board None
SubCard None
Port If SFP or XFP ports, the entPhysicalSerialNum should be the serial number
of the optical module
Fabric None
chassis
Unit Gryffindor 24 3CR17761-91
Gryffindor 48 3CR17762-91
Gryffindor 24 PWR 3CR17771-91
Gryffindor 48 PWR 3CR17772-91
Slot None
SubSlot None
PowerSupply None
Fan None
Board None
SubCard Module 2 x CX4 i/f 3C17767
Module 2x XFP i/f 3C17766
Module 1x XFP i/f 3C17768
Port None
Fabric None
entity entPhysicalAlias
Unit None
Slot None
SubSlot None
PowerSupply None
Fan None
Board None
SubCard None
Port None
Fabric none
entity entPhysicalAssetID
Unit None
Slot None
SubSlot None
PowerSupply None
Fan None
Board None
SubCard None
Port None
Fabric None
entity entPhysicalIsFRU
Unit True(1)
Slot False(2)
SubSlot False(2)
PowerSupply False(2)
Fan False(2)
Board False(2)
SubCard True(1)
Port If a SFP or XFP(that is optical module) port, True(1); else, False(2)
Fabric False(2)
14.2 entAliasMappingTable
14.3 entPhysicalContainsTable
15 DISMAN-PING-MIB
This MIB should be supported by device which implements disman ping function. This
MIB cannot mix using with CLI.
15.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.
pingIcmpEcho pingCtlTargetAddressType
pingCtlTargetAddress
pingCtlDataSize
pingCtlDataFill
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlIfIndex
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingUdpEcho pingCtlTargetAddressType
pingCtlDataSize
pingCtlDataFill
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingSnmpQuery pingCtlTargetAddressType
pingCtlTargetAddress
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingTcpConnectionAttempt pingCtlTargetAddressType
h3cNqaTcpconnect or pingCtlTargetAddress
hwpingTcpconnect pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingCtlDataSize
pingCtlDataFill
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
pingCtlDataFill
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
h3cNqaHttp pingCtlTargetAddressType
pingCtlTargetAddress
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
h3cNqadlsw pingCtlTargetAddressType
pingCtlTargetAddress
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
h3cNqadhcp pingCtlIfIndex
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
h3cNqaftp pingCtlTargetAddressType
pingCtlTargetAddress
pingCtlSourceAddressType
pingCtlSourceAddress
pingCtlByPassRouteTable
pingCtlDSField
pingCtlProbeCount
pingCtlTrapProbeFailureFilter
pingCtlTrapTestFailureFilter
15.3 pingResultsTable
15.4 pingProbeHistoryTable
16 SNMP-TARGET-MIB
16.2 snmpTargetAddrTable
16.3 snmpTargetParamsTable
snmpTargetParamsSecurityName.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) gl [67.6C (hex)]
13:
snmpTargetParamsSecurityLevel.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) noAuthNoPriv(1)
14:
snmpTargetParamsStorageType.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) nonVolatile(3)
15:
snmpTargetParamsRowStatus.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) active(1)
16: snmpUnavailableContexts.0 (counter) 0
17: snmpUnknownContexts.0 (counter) 0
***** SNMP QUERY FINISHED *****
2:
snmpTargetAddrTDomain.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.46.
3:
snmpTargetAddrTAddress.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.46.
4:
snmpTargetAddrTimeout.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.46.4
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
7:
snmpTargetAddrParams.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.46.4
[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.
9:
snmpTargetAddrRowStatus.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.49.4
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
14:
snmpTargetParamsStorageType.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.
15:
snmpTargetParamsRowStatus.116.114.97.112.104.111.115.116.46.112.117.98.108.105.99.46.49.46.4
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,
which is the hex code of string "traphost.public.1.1.1.1.vpn "
17 SNMP-USER-BASED-SM-MIB
18 SNMP-VIEW-BASED-ACM-MIB
18.1 vacmContextTable
18.2 vacmSecurityToGroupTable
18.3 vacmAccessTable
19 BRIDGE-MIB
19.2 dot1dBasePortTable
19.4 dot1dStpPortTable
19.6 dot1dTpPortTable
20 POWER-ETHERNET-MIB
20.1 pethPsePortTable
20.2 pethMainPseTable
20.3 pethNotificationControlTable
21 P-BRIDGE-MIB
21.2 dot1dPortCapabilitiesTable
21.3 dot1dPortPriorityTable
21.4 dot1dPortGarpTable
22 Q-BRIDGE-MIB
22.2 dot1qTpFdbTable
22.3 dot1qTpGroupTable
22.5 dot1qPortVlanTable
23 RMON-MIB
23.1 etherStatsTable
23.2 historyControlTable
23.3 etherHistoryTable
23.4 alarmTable
23.5 eventTable
23.6 logTable
24 IEEE8021-PAE-MIB
24.3 dot1xAuthConfigTable
25 IGMP-STD-MIB
25.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.
25.2 igmpCacheTable
The igmpCacheTable contains information about multicast groups for which there are
members on a particular interface.
26 IEEE8023-LAG-MIB
26.1 dot3adAggTable
26.2 dot3adAggPortListTable
26.3 dot3adAggPortTable
26.4 dot3adAggPortStatsTable
26.5 dot3adAggPortDebugTable
27 IPV6-TCP-MIB
27.1 ipv6TcpConnTable
28 IPV6-UDP-MIB
28.1 ipv6UdpTable
29 IPV6-ICMP-MIB
29.1 ipv6IfIcmpTable
30 IPV6-MIB
30.2 ipv6IfTable
30.3 ipv6AddrPrefixTable
30.4 ipv6AddrTable
30.5 ipv6NetToMediaTable
31 LLDP-EXT-DOT1-MIB
The LLDP Management Information Base extension module for IEEE 802.1
organizationally defined discovery information.
31.1 lldpXdot1ConfigPortVlanTable
31.2 lldpXdot1ConfigVlanNameTable
31.3 lldpXdot1ConfigProtoVlanTable
31.4 lldpXdot1ConfigProtocolTable
31.5 lldpXdot1LocTable
31.6 lldpXdot1LocProtoVlanTable
31.7 lldpXdot1LocVlanNameTable
lldpXdot1LocProtocolTable
31.8 lldpXdot1RemTable
31.9 lldpXdot1RemProtoVlanTable
31.10 lldpXdot1RemVlanNameTable
31.11 lldpXdot1RemProtocolTable
32 LLDP-EXT-DOT3-MIB
The LLDP Management Information Base extension module for IEEE 802.3
organizationally defined discovery information.
32.1 lldpXdot3PortConfigTable
32.2 lldpXdot3LocPortTable
32.3 lldpXdot3LocPowerTable
32.4 lldpXdot3LocLinkAggTable
32.5 lldpXdot3LocMaxFrameSizeTable
32.6 lldpXdot3RemPortTable
32.7 lldpXdot3RemPowerTable
32.8 lldpXdot3RemLinkAggTable
32.9 lldpXdot3RemMaxFrameSizeTable
33 LLDP-MIB
Management Information Base module for LLDP configuration statistics, local system data
and remote systems data components.
33.2 lldpPortConfigTable
33.3 lldpConfigManAddrTable
33.4 lldpStatsTxPortTable
33.5 lldpStatsRxPortTable
33.6 lldpLocPortTable
33.7 lldpLocManAddrTable
33.8 lldpRemTable
33.9 lldpRemManAddrTable
33.10 lldpRemUnKnownTLVTable
33.11 lldpRemOrgDefInfoTable
34 A3COM-HUAWEI-TRNG-MIB
34.1 hwTrngCreateTimerangeTable
34.2 hwTrngAbsoluteTable
34.3 hwTrngPeriodicTable
35 A3COM-HUAWEI-8021PAE-MIB
35.2 dot1xAuthConfigTable
36 A3COM-HUAWEI-LSW-DEV-ADM-MIB
36.2 hwLswFrameTable
36.3 hwLswSlotTable
36.4 hwLswSubslotTable
36.5 hwLswPortTable
37 A3COM-HUAWEI-LAG-MIB
37.2 hwAggLinkTable
37.3 hwAggPortTable
38 A3COM-HUAWEI-LswDEVM-MIB
38.2 hwdevMFanStatusTable
38.3 hwdevMPowerStatusTable
39 A3COM-HUAWEI-DISMAN-PING-MIB
This MIB should be supported by device which implements disman ping function. This
MIB cannot mix using with CLI.
39.2 hwPingCtlTable
b) Once the configuration is modified, the result and histories of the corresponding
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
be set.
39.3 hwpingResultsTable
39.4 hwPingJitterStatsTable
39.5 hwPingTcpServerTable
39.6 hwPingUdpServerTable
40 A3COM-HUAWEI-HGMP-MIB
41 HUAWEI-LswIGSP-MIB
41.2 hwIgmpSnoopingStatsObjects
41.3 hwIgmpSnoopingVlanStatusTable
42 A3COM-HUAWEI-LswINF-MIB
42.1 hwifXXTable
42.2 hwifHybridPortTable
The values of below objects must be appointted at the same time when SET
operation.:
hwifHybridTaggedVlanListLow,
hwifHybridTaggedVlanListHigh,
hwifHybridUnTaggedVlanListLow,
hwifHybridUnTaggedVlanListHigh
42.3 hwifComboPortTable
42.7 hwPortIsolateGroupTable
43 A3COM-HUAWEI-LswMAM-MIB
43.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.
44 A3COM-HUAWEI-RMON-EXT-MIB
44.1 prialarmTable
45 A3COM-HUAWEI-LswMSTP-MIB
45.2 hwdot1sVIDAllocationTable
45.3 hwdot1sInstanceTable
45.4 hwdot1sPortTable
46 A3COM-HUAWEI-LswTRAP-MIB
47 A3COM-HUAWEI-LswVLAN-MIB
47.2 hwvLANMibSwitchCountTable
47.3 hwvLANMibHoldTimeTable
47.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.
47.5 hwVlanInterfaceTable
47.6 hwVlanInterfaceAddrTable
48 A3COM-HUAWEI-ACL-MIB
48.1 h3cAclMib2NodesGroup
48.2 h3cAclMib2CapabilityTable
48.3 h3cAclNumberGroupTable
Notes:
48.4 h3cAclIPAclBasicTable
All the objects in the table except h3cAclIPAclBasicComment can not be modified
now.
48.5 h3cAclIPAclAdvancedTable
If a rule will be created, h3cAclIPAclAdvancedRowStatus must be 4 and the rule
number does not exist.
The value of h3cAclIPAclAdvancedAct is 1,2 or 3;
When the value of h3cAclIPAclAdvancedProtocol is udp or tcp,
h3cAclIPAclAdvancedSrcOp, h3cAclIPAclAdvancedSrcPort1 and
h3cAclIPAclAdvancedSrcPort2 can be set.
The value of h3cAclIPAclAdvancedDestAddrType and
h3cAclIPAclAdvancedSrcAddrType is 1 or 2.
All the objects in the table except h3cAclIPAclAdvancedComment can not be modified
now.
48.6 h3cAclMACTable
If a rule will be created, h3cAclMACRowStatus must be 4 and the rule number
does not exist.
The value of h3cAclMACAct is 1, 2 or 3 and the set of h3cAclMACAct is required
when a rule is created.
h3cAclMACTypeCode and h3cAclMACTypeMask must be set together.
h3cAclMACSrcMac and h3cAclMACSrcMacWild must be set together.
h3cAclMACDestMac and h3cAclMACDestMacWild must be set together.
h3cAclMACLsapCode and h3cAclMACLsapMask must be set together.
If. h3cAclMACTypeCode or h3cAclMACTypeMask is set, h3cAclMACLsapCode or
h3cAclMACLsapMask must be not set.
If. h3cAclMACLsapCode or h3cAclMACLsapMask is set, H3cAclMACTypeCode or
h3cAclMACTypeMask must be not set.
All the objects in the table except h3cAclMACComment can not be modified now.
49 A3COM-HUAWEI-CBQOS2-MIB
49.2 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.
49.3 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.
49.4 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.
50 A3COM-HUAWEI-DLDP-MIB
50.2 h3cDLDPPortStateTable
50.3 h3cDLDPPortDLDPTable
50.4 h3cDLDPNeighborTable
51 A3COM-HUAWEI-DOMAIN-MIB
51.2 h3cDomainInfoTable
51.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
52 A3COM-HUAWEI-IP-ADDRESS-MIB
52.2 h3cIpAddrSetTable
This table does not supported modify the variable of exist entry, only supported create a
new entry and destroy an exist entry.
52.3 h3cIpAddrReadTable
53 A3COM-HUAWEI-IP-BROADCAST-MIB
This MIB is used to set whether a device receives direct broadcast datagram.
53.1 h3cIpForwardBroadcast
54 A3COM-HUAWEI-IPV6-ADDRESS-MIB
54.2 h3cIpv6AddrSetTable
This table does not supported modify the variable of exist entry, only supported create a
new entry and destroy an exist entry.
54.3 h3cIpv6AddrReadTable
55 A3COM-HUAWEI-MPM-MIB
55.2 h3cMPortGroupJoinTable
55.3 h3cMPortGroupTable
55.4 h3cMPortConfigTable
The h3cMPortConfigTable containing configuration about fast leave status, group limit
number and group policy parameter on a port in the specified VLAN.
56 A3COM-HUAWEI-NQA-MIB
This MIB should be supported by device which implements disman ping function.
This MIB cannot mix using with CLI.
56.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
notDefined(1)
h3cNqaCtlTTL
h3cNqaCtlJitterAdminInterval
h3cNqaCtlJitterAdminNumPackets
h3cNqaCtlCodecType
h3cNqaCtlJitterAdminNumPackets
h3cNqaCtlICPIFAdvFactor
h3cNqaCtlCodecType
h3cNqaHttp h3cNqaCtlTTL
h3cNqaCtlHttpOperationType
h3cNqaCtlHttpOperationString
h3cNqadlsw h3cNqaCtlTTL
h3cNqadhcp
h3cNqaftp h3cNqaCtlTTL
h3cNqaCtlFtpOperationType
h3cNqaCtlFtpUsername
h3cNqaCtlFtpPassword
h3cNqaCtlFtpOperationString
g711Ulaw or g729A to
codec-type configuration.
is notDefined, g711Alaw,
56.3 h3cNqaResultsTable
56.4 h3cNqaJitterStatsTable
56.5 h3cNqaTcpServerTable
56.6 h3cNqaUdpServerTable
56.7 h3cNqaStatisticsCtlTable
56.8 h3cNqaStatisticsResultsTable
56.9 h3cNqaGroupStatsJitterTable
57 A3COM-HUAWEI-PORT-SECURITY-MIB
h3cSecurePortSecurityContro
read-write Current As per MIB
l
h3cSecurePortVlanMembers accessible-f
No As per MIB
hipList or-notify
h3cSecureRalmAuthDomain read-write Yes As per MIB
h3cSecureRalmAuthOfflineTi
read-write Yes As per MIB
me
h3cSecureRalmAuthServerTi
read-write Yes As per MIB
meoutTime
57.2 h3cSecureRalmGroup
h3cSecureRalmDefaultSessi
read-write Current Not Supported
onTime
h3cSecureRalmHoldoffTime read-write Current As per MIB
Write a MAC address to this
object causes an immediate
cut connection of this
h3cSecureRalmReauthentica
read-write No address. If the MAC address
te
not currently known to
RALM, it silently ignores the
write.
h3cSecureRalmAuthMode read-write Current As per MIB
h3cSecureRalmAuthUsernam
read-write Current As per MIB
e
h3cSecureRalmAuthPasswor
read-write Current As per MIB
d
57.3 h3cSecurePortTable
The h3cSecurePortTable defines the security status of each secure port. Each port can
have a number of authorized MAC addresses, and these are stored in the
h3cSecureAddressTable.
The value of
continuousLearning will not
be supported.
When we change the
h3cSecurePortMode read-write Current h3cSecurePortMode value,
we should first change its
value to noRestrictions, then
continue to change it to the
other value.
h3cSecureNeedToKnowMode read-write Current As per MIB
The value of
h3cSecureIntrusionAction read-write Current allowDefaultAccess will not
be supported.
h3cSecureNumberAddresses read-write Current As per MIB
h3cSecureNumberAddresses
read-only Current As per MIB
Stored
h3cSecureMaximumAddress
read-only Current As per MIB
es
57.4 h3cSecureAddressTable
accessible-f
h3cSecureAddrMAC Current As per MIB
or-notify
not-accessib
h3cSecureAddrVlanID Current As per MIB
le
h3cSecureAddrMACStatus read-create Current As per MIB
h3cSecureAddrRowStatus read-create Current As per MIB
57.5 h3cSecureOUITable
The h3cSecureOUITable stores the OUI values for OUI based authorization.
57.6 h3cSecureBindingTable
This table stores the elements of a binding rule include the MAC addresses , the IP
address and the port.
57.7 h3cSecureAssignTable
Supported Traps
Name Description
h3cSecureAddressLearne
As per MIB
d
h3cSecureViolation As per MIB
h3cSecureLoginFailure As per MIB
h3cSecureLogon As per MIB
h3cSecureLogoff As per MIB
h3cSecureRalmLoginFailu This trap is sent whenever a user network access
re authentication has failed.
This trap is sent when a new session is started for
h3cSecureRalmLogon
an authorised port user.
h3cSecureRalmLogoff This trap is sent when a user session is terminated.
58 A3COM-HUAWEI-POWER-ETH-EXT-MIB
58.2 h3cPsePortTable
58.3 h3cMainPseTable
58.4 h3cPseProfilesTable
59 A3COM-HUAWEI-QINQ-MIB
59.2 h3cQINQBpduTunnelTable
59.3 h3cQINQVidTable
59.4 h3cQinQIfConfigTable
60 A3COM-HUAWEI-QOS-CAPABILITY-MIB
60.1 h3cQoSCapabilityTable
61 A3COM-HUAWEI-RRPP-MIB
61.2 h3cRrppDomainTable
61.3 h3cRrppRingTable
61.4 h3cRrppPortTable
62 A3COM-HUAWEI-STORM-CONSTRAIN-MIB
62.2 h3cStormCtrlTable
Name Access PDS Description
Now only supported
h3cStormCtrlPortStatus read-only No
accessible-for-notify
h3cStormCtrlBroadcastUnit read-create No Not supported
h3cStormCtrlBroadcastUpper read-create No Not supported
h3cStormCtrlBroadcastLower read-create No Not supported
h3cStormCtrlMulticastUnit read-create No Not supported
h3cStormCtrlMulticastUpper read-create No Not supported
h3cStormCtrlMulticastLower read-create No Not supported
h3cStormCtrlUnicastUnit read-create No Not supported
h3cStormCtrlUnicastUpper read-create No Not supported
h3cStormCtrlUnicastLower read-create No Not supported
h3cStormCtrlRowStatus read-create No Not supported
63 A3COM-HUAWEI-RADIUS-MIB
work on another table. That is, to create a new row in h3cRdInfoTable, a row with the
same group name will appear in h3cRdAccInfoTable. To delete a row from
h3cRdInfoTable, corresponding row in h3cRdAccInfoTable will be cleared away and vice
versa.
63.1 h3cRdInfoTable
63.2 h3cRdAccInfoTable
63.3 h3cRadiusAccServerTable
64 A3COM-HUAWEI-FLASH-MAN-MIB
This Mib supplies the information for the management of flash devices.
64.2 h3cFlashTable
64.3 h3cFlhChipTable
64.4 h3cFlhPartitionTable
64.5 h3cFlhFileTable
64.6 h3cFlhOpTable
When ftp protocol is used to transmit file, the values for h3cFlhOperServerUser and
h3cFlhOperPassword must be specified.
The following values of H3cFlashOperationStatus are implemented for tftp protocol:
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)
65 A3COM-HUAWEI-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.
65.2 h3cSysCurTable
65.3 h3cSysReloadScheduleTable
reloading.
65.4 h3cSysImageTable
65.5 h3cSysCFGFileTable
65.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.
Examples
h3cSysBtmFileName.131073 = “flash:/s4e01_06.btm”
h3cSysBtmFileType.131073 = ‘main’
h3cSysBtmRowStatus.131073 = ‘createAndGo’
66 A3COM-HUAWEI-DISMAN-PING-MIB
66.2 hwPingCtlTable
66.3 hwpingResultsTable
66.4 hwPingJitterStatsTable
66.5 hwPingTcpServerTable
66.6 hwPingUdpServerTable
67 A3COM-HUAWEI-PROTOCOL-VLAN-MIB
67.2 h3cProtocolVlanTable
67.3 h3cProtocolVlanPortTable
68 A3COM-HUAWEI-ENTITY-VENDORTYPE-OID-MIB
69 A3COM-HUAWEI-ENTITY-EXT-MIB
69.1 h3cEntityExtStateTable
69.2 h3cEntityExtManuTable
69.3 h3cProcessTable
h3cEntityExtAdmin N N N N N N Y
Status (R/W)
h3cEntityExtOperSt N N Y Y Y Y Y
atus (R)
h3cEntityExtStandb N N N N N N N
yStatus (R)
hwEntityExtAlarmLi N N N N N N N
ght (R)
h3cEntityExtCpuUs N N N Y(the N N N
age (R) module
which
has
cpu)
h3cEntityExtCpuUs N N N Y(the N N N
ageThreshold (R/W) module
which
has
cpu)
h3cEntityExtMemUs N N N Y(the N N N
erialNum )
h3cEntityExtManuB N Y N Y(board N N N
uildInfo )
h3cEntityExtManuB N Y N Y(board N N N
OM )
h3cEntityExtMacAd N Y N Y(board N N N
dressCount )
1. “Yes” means the preporty of that entity is implemented. Others are not supported.
2. If the result by the operation is “No such name”, it denotes this MIB object is not
to be supported for the specific entity.
70 A3COM-HUAWEI-VOICE-VLAN-MIB
70.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
70.3 h3cvoiceVlanPortTable
71 A3COM-HUAWEI-UI-MAN-MIB
71.2 h3cVtyAccTable
72 A3COM-HUAWEI-USER-MIB
Scalar Objects
72.1 h3cUserInfoTable
When h3cUserPassword and h3cAuthMode want to be setted ,this two nodes must
be setted simultaneously
72.2 h3cUserAttributeTable
72.3 h3cUserGroupInfoTable
73 A3COM-HUAWEI-ENTRELATION-MIB
The MIB describles the relationship of two physical entities, including stacking ports
and combo pairs. Now only supported stacking ports
This table just provide the relationship of combo pairs, user can activate the port
through the standard ifAdmin setting, No additional MIB will be used to change active
port in a combo pair.
73.1 h3cEntRelationTable
2006-03-30 Confidential Information of H3C. Page 203 of 231
74 H3C-NTP-MIB
74.1 hwNTPPeerMIBObjects
74.2 hwNTPPeerTable
75 A3COM-HUAWEI-CONFIG-MAN-MIB
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.
Note: Writing flash can be done by Backup (save) as described in figure 16-1. The
object of hwWriteConfig is replaced by this MIB.
Flash
Backup(ftp/tftp)
Restore
Restore(ftp/tftp)
Backup(save)
Backup(ftp/tftp)
Memory Network
Restore(ftp/tftp)
Figure 16-1
75.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 include saving
current configuration, resetting saved-configuration, renaming current startup
configuration file and overwriting current startup configuration file by copy command.
75.4 h3cCfgOperateTable
75.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)
76 A3COM-HUAWEI-TUNNEL-MIB
76.1 h3cTunnelIfTable
76.2 h3cTunnelInetConfigTable
77 A3COM-HUAWEI-DHCPRELAY-MIB
77.1 h3cDHCPRStatisticsGroup
77.2 h3cDHCPRIfSelectTable
77.3 h3cDHCPRIpToGroupTable
77.4 h3cDHCPRIfToGroupTable
77.5 h3cDHCPRAddrCheckTable
77.6 h3cDHCPRSecurityTable
77.7 h3cDHCPRConfigOption82IfTable
78 A3COM-HUAWEI-MAC-INFORMATION-MIB
78.2 h3cMACInfomationIfTable
Name Access PDS Description
h3cMACLearntEnable read- write Current As per MIB
h3cMACRemovedEnable read- write Current As per MIB
79 A3COM-HUAWEI-MIRRORGROUP-MIB
not-accessibl
h3cMGID Current range from 1 to 4
e
not-accessibl
h3cMGMirrorIfIndex Current As per MIB
e
not-accessibl
h3cMGMirrorDirection Current As per MIB
e
not-accessibl
h3cMGMonitorIfIndex Current As per MIB
e
not-accessibl
h3cMGReflectorIfIndex Current As per MIB
e
not-accessibl
h3cMGRprobeVlanID Current As per MIB
e
80 A3COM-HUAWEI-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.
80.1 3.1 scalar objects
Name Access PDS Description
accessible-f
h3cStormTrapType No As per MIB
or-notify
accessible-f
h3cStormTrapThreshold No As per MIB
or-notify
80.2 3.2 h3cCfgLogTable
Name Access PDS Description
h3cStormCtrlPortStatus read-only No As per MIB
81 A3COM-HUAWEI-TRAP-MIB
81.2 h3cDetailRtTrapTable
82 Supported Traps
This section contains a list of the traps defined in the standard MIB(defined by IETF
or IEEE).
This section contains a list of the traps defined in the private MIB(defined by enterprise).