3com 4500 MIB Companion (V3.3.2p19)

3Com 4500(buckbeak) MIB Compaion
V0.13
Title: Authors: Revision: Creation Date:
1404013 Buckbeak MIB Companion

Buckbeak Team 0.13 08/06/2005 15:32
Modification Date: 19/03/2013 Abstract: This document described the MIBs supported by Buckbeak devices.
Approvals Title Name Date
3Com Product Manager
JVCo Product Manager
3Com Programme Manager
JVCo Programme Manager
3Com Software Leader
JVCo Software Leader
This document is copyrighted and may not be copied or disclosed to a third party without the specific written authority of 3Com. 3Com Corporation. All Rights Reserved
Copyright
COMPANY CONFIDENTIAL: NOT FOR EXTERNAL DISTRIBUTION
Page 1 of 132

V0.13
I II 1. 2. 3. 4.
REVISION HISTORY REFERENCES INTRODUCTION STATEMENT MIB SUPPORT & RFC COMPLIANCE RFC1213 - MIB-II 4.1 4.2 4.2.1 4.2.2 4.3 4.3.1 4.4 4.4.1 4.4.2 4.4.3 4.5 4.5.1 4.5.2 4.6 4.6.1 4.6.2 4.7 4.8 SYSTEM GROUP {MIB-2.1} INTERFACES GROUP{MIB-2.2} ifIndex Value Allocation ifTable mib ADDRESS TRANSLATION GROUP(AT) {MIB-2.3} atTable: IP GROUP {MIB-2.4} Scalar Objects: ipAddrTable: ipRouteTable: TCP GROUP{MIB-2.6} Scalar objects: tcpConnTable: UDP GROUP{MIB-2.7} Scalar objects: udpTable: SNMP GROUP{MIB-2.11} ARP MIB
10 11 12 13 13 15 15 15 15 17 18 18 19 19 19 19 20 20 20 20 20 21 21 22 22 22 23 23 24 24 24 24 24 24 24 24 24 25 25 25 25 25 25 26 26 26
Copyright
5.
IFMIB- RFC2233 5.1

IFXTABLE
6.
ETHERLIKE-MIB-RFC2665 6.1
DOT3STATSTABLE
7.
RFC1493 BRIDGE-MIB 7.1 7.1.1 7.1.2 7.1.3 7.2 7.2.1 7.2.2 7.2.3 7.2.4
DOT1DBASE
dot1dBaseBridgeAddress dot1dBaseNumPorts dot1dBasePortTable DOT1DTP dot1dTpLearnedEntryDiscards dot1dTpAgingTime dot1dTpFdbTable dot1dTpPortTable
8.
RFC2674 P-BRIDGE-MIB Q-BRIDGE-MIB 8.1 8.1.1 8.1.2 8.2 P-BRIDGE MIB dot1dExtBase { pBridgeMIBObjects.1} dot1dPriority{ pBridgeMIBObjects.2} Q-BRIDGE MIB
9.
SNMP PROTOCOL MIBS 9.1 9.2 SNMPMIB { SNMPMODULES.1} SNMPFRAMEWORKMIB{ SNMPMODULES.10}
Page 2 of 132

V0.13
9.2.1 9.3 9.4 9.4.1 9.4.2 9.4.3 9.5 9.5.1 9.6 9.6.1 9.6.2
9.6.2.1 9.6.2.2
the allocation of snmpEngineID SNMPMPDMIB{ SNMPMODULES.11} SNMPTARGETMIB{ SNMPMODULES.12} Scalar objects: snmpTargetAddrTable snmpTargetParamsTable SNMPNOTIFICATIONMIB{ SNMPMODULES.13} snmpNotifyTable{ snmpNotificationMIB.1} SNMPUSMMIB{ SNMPMODULES.15} usmStats group { snmpUsmMIB.1} usmUser group { snmpUsmMIB.2}
Scalar objects { usmUser.1}: usmUserTable { usmUser.2}:
SNMPVACMMIB{ SNMPMODULES.16}
26 26 27 27 27 28 29 29 30 30 30
30 30
9.7 9.7.1
9.7.1.1 9.7.1.2 9.7.1.3
vacmMIBObjects
vacmContextTable { vacmMIBObjects.1} vacmSecurityToGroupTable { vacmMIBObjects.2} vacmAccessTable { vacmMIBObjects.4}:
31 31
31 31 32
9.7.2
9.7.2.1 9.7.2.2
vacmMIBViews
Scalar { vacmMIBViews.1} vacmViewTreeFamilyTable{ vacmMIBViews.2}
32
32 32
10.
RMON MIBS RFC2819 - RMON 1 Statistics History Alarm Event RFC2021 - PROBECONFIG RFC3273 - HC-RMON-MIB RFC2613- SMON A3COM-HUAWEI-PERFORMANCE-MIB - EXTENSION TO RMON ALARM priAlarmTable NETCONFIGTABLE
32 32 33 33 34 35 35 35 35 36 36 36 36 36 37 37 37 37 37 37 38 38 38 38 38 38 38 38 39 39 39 39
Copyright
10.1 10.1.1 10.1.2 10.1.3 10.1.4 10.2 10.3 10.4 10.5 10.5.1 10.6 11.
RFC2674 - BRIDGE MIB EXTENSIONS

DOT1QVLAN GROUP
11.1 11.1.1 11.1.2 11.1.3 11.2 11.2.1 11.2.2 11.2.3 12. 13.
dot1qVlanStaticTable dot1qVlanCurrentTable dot1qPortVlanTable DOT1QTP GROUP dot1qFdbTable dot1qTpFdbTable dot1qTpGroupTable
RFC1850-OSPF(NOT SUPPORT) RFC 1724-RIPV2

RIP2GLOBALS { RIP2 1 } RIP2IFSTATTABLE { RIP2 2 }
13.1 13.2 13.2.1 13.3 13.3.1 13.4 13.4.1 14. 15.
rip2IfStatEntry { rip2IfStatTable 1 } RIP2IFCONFTABLE { RIP2 3 } rip2IfConfEntry { rip2IfConfTable 1 } RIP2PEERTABLE { RIP2 4 } Rip2PeerEntry { rip2PeerTable 1 }
RFC2668 MAU MIB(NOT SUPPORT) A3COM-HUAWEI-FLASH-MAN-MIB:FLASH MANAGEMENT MIBS
Page 3 of 132

V0.13
15.1 15.1.1 15.1.2 15.1.3 15.2 16.
H3CFLASHDEVICE
h3cFlhSupportNum: The number of flash supported by system. H3cFlashTable: The information for each flash. H3cFlashChips:The information for each chip in a flash(h3cFlashManMIBObjects.2) H3CFLASHOPERATE
39 39 39 40 41 43 43 43 44 44 45 45 46 46 46 47 48 48 48 48 48 49
A3COM-HUAWEI-CONFIG-MAN-MIB THE CONFIGURATION LOG MANAGEMENT- H3CCFGLOG MIB GROUP scalar objects h3cCfgLogTable THE CONFIGURATION BACKUP AND RESTORE- H3CCFGOPERATE MIB GROUP h3cCfgOperateTable h3cCfgOperateResultTable
16.1 16.1.1 16.1.2 16.2 16.2.1 16.2.2 17. 17.1 17.2 17.3 17.4 17.5 18.
A3COM-HUAWEI-SYS-MAN-MIB: SYSTEM INFORMATION AND SYSTEM MANAGEMENT

H3CSYSCLOCK-SYSTEM CLOCK MANAGEMENT GROUP H3CSYSRELOAD-SYSTEM RELOAD MANAGEMENT GROUP H3CSYSIMAGE-SYSTEM IMAGE MANAGEMENT GROUP H3CSYSCFGFILE-SYSTEM WCONFIGURATION FILES MANAGEMENT GROUP H3CSYSCURRENT-SYSTEM CURRENT STATUS GROUP
A3COM-HUAWEI-LSWIGSP-MIB HWLSWIGMPSNOOPINGMIB { LSW COMMON 7 } hwLswIgmpsnoopingMibObject { h3cLswIgmpsnoopingMib 1 }
18.1 18.1.1 19.
A3COM-HUAWEI-LSWDHCP_MIB
HWLSWDHCPMIB { LSWCOMMON
19.1 19.1.1
19.1.1.1 19.1.1.2 19.1.1.3
hwLswDhcpMibObject {
8} hwLswDhcpMib 1
49 49
49 49 49
hwDhcpGroupTable {hwLswDhcpMibObject 1 } hwDhcpSecurityTable {hwLswDhcpMibObject 2 } hwDhcpToL3IfTable {hwLswDhcpMibObject 3 }
20. 21.
A3COM-HUAWEI-DHCPR-MIB LACP MIBS IEEE8023-LAG-MIB dot3adAgg Group

dot3adAggTable dot3adAggPortListTable
49 49 49 49
49 50
21.1 21.1.1
21.1.1.1 21.1.1.2
21.1.2
21.1.2.1
dot3adAggPort Group
dot3adAggPortTable
50
50
21.1.3
21.1.3.1
dot3adAggPortStatsTable
dot3adAggPortDebugTable
51
51
21.1.4 21.2 21.2.1 21.2.2 21.2.3 22. 22.1 22.2 23. 23.1 23.2 23.3 23.4
dot3adTablesLastChanged A3COM-HUAWEI-LAG-MIB hwAggLinkTable hwAggPortTable hwAggResourceAllocationValue
51 51 51 52 52 52 52 53 53 54 54 55 55
Copyright
IEEE8021D-STP-MIB
DOT1DSTPPORTTABLE DOT1DSTPGLOBALTABLE
DISMAN-PING-MIB
PINGNOTIFICATIONS PINGCTLT ABLE PINGRESULTSTABLE PINGPROBEHISTORYTABLE
Page 4 of 132

V0.13
24. 24.1 25. 25.1 25.2 25.3 25.4 26.
A3COM-HUAWEI-PING-MIB
HW PINGAGENTENABLE
56 56 56 56 56 56 57 57 { entityPhysical 1} 57 57
57 60 61 67 68 69
A3COM-HUAWEI-LSWRSTP-MIB SCALAR OBJECTS: HWDOT1DSTPIGNOREDVLANTABLE HWDOT1DSTPPORTXTABLE HWRSTPEVENTSV2 DEVICE MANANGEMENT MIBS

ENTITY MIB-RFC2737
26.1 26.1.1
26.1.1.1 26.1.1.2 26.1.1.3 26.1.1.4 26.1.1.5 26.1.1.6
entityPhysicalTable
OverViews Index Range Table: Sytax or meaning of each object in physical table: Example Implementation of stack port and combo port Ways to distinguish board from subcard
26.1.2 26.1.3 26.1.4 26.1.5 26.1.6 26.2 26.2.1 27. 27.1 27.2 28. 28.1 28.2 29.
entLogicalTable { entityLogical 1 } (Not support) entLPMappingTable { entityMapping 1 }(Not support) entPhysicalContainsTable { entityMapping 3 } entAliasMappingEntry{ entityMapping 3} entityGeneral {entityMIBObjects 4}(Not support) A3COM-HUAWEI-ENTITY-EXT-MIB MIB H3cEntityExtStateTable
69 69 69 69 70 70 70 72 72 72 73 73 73 74 74 74 74 75 75 75 75 76 76 76 77 77 77 77 78 78 78 78 79
Copyright
MAC ADDRESS MANANGEMENT MIBS- HWLSWMACPORT

HWDOT1QMACSEARCHTABLE { H3CLSW MACPORT 1 } HWDOT1QTPFDBSETTABLE { HWLSWMACPORT 2 }
A3COM-HUAWEI-LSWDEVM -MIB
HWDEVMFANSTATUSTABLE HWDEVMPOWERSTATUSTABLE
A3COM-HUAWEI-LSWINF-MIB
HWIFXXTABLE HWIFAGGREGATETABLE HWIFHYBRIDPORTTABLE HWIFVLANTRUNKSTATUSTABLE
29.1 29.2 29.3 29.4 29.4.1 29.5 29.5.1 30.
hwifVLANTrunkStatusTable HWETHERNETTABLE hwethernetTable
A3COM-HUAWEI-LSWVLAN-MIB
HWDOT1QVLANMIBTABLE
30.1 30.1.1 30.2 30.2.1 30.3 30.3.1 31. 31.1 31.2 31.3 32. QOS MIBS
hwdot1qVlanMIBTable HW VLANINTERFACETABLE hwVlanInterfaceTable HW VLANINTERFACEADDRTABLE hwVlanInterfaceAddrTable
TIME RANGE MANANGEMENT MIBS

HWTRNGCREATETIMERANGETABLE HWTRNGABSOLUTETABLE HWTRNGPERIODICTABLE
Page 5 of 132

V0.13
32.1 32.2 32.3 32.4 32.5 32.6 32.7 32.8 32.9 32.10 32.11 32.12 32.13 32.14 32.15 32.16 32.17 32.18 32.19 32.20 32.21 32.22 33. ACL MIBS
HWQUEUETABLE HWRATELIMITTABLE(NOT SUPPORT) HW PRIORITYTABLE (NOT SUPPORT) HWREDIRECTTABLE(NOT SUPPORT) HW STATISTICTABLE(NOT SUPPORT) H3CMIRRORTABLENOT SUPPORT HW PORTMIRRORTABLE HWLINERATETABLE HWREDTABLENOT SUPPORT HWMIRRORGROUPTABLE(NOT SUPPORT) HWFLOWTEMPTABLE(NOT SUPPORT) HWFLOWTEMPENABLETABLE(NOT SUPPORT) HWTRAFFICSHAPETABLE(NOT SUPPORT) HW PORTQUEUETABLE(NOT SUPPORT) HWDROPMODETABLE(NOT SUPPORT) HWW REDTABLE(NOT SUPPORT) HWCOSTOLOCALPRECEDENCEMAPTABLE(NOT SUPPORT) HWCOSTODROPPRECEDENCEMAPTABLE(NOT SUPPORT) HWDSCPMAPTABLE(NOT SUPPORT) HW EXPMAPTABLE(NOT SUPPORT) HWLOCALPRECEDENCEMAPTABLE(NOT SUPPORT) HW PORTW REDTABLE(NOT SUPPORT)
79 79 80 81 82 83 83 83 84 84 84 85 85 86 86 86 86 87 87 87 87 87 88
33.1 33.2 33.3 33.4 33.5 33.6 33.7 33.8 33.9 33.10 34. 35. 36. LCS MIBS
H3CACLMODE(NOT SUPPORT) H3CACLNUMGROUPTABLE H3CACLNAMEGROUPTABLE H3CACLBASICRULETABLE H3CACLADVANCEDTABLE H3CACLIRULEFTABLE H3CACLLINKTABLE H3CACLUSERTABLE H3CACLACTIVETABLE H3CACLIDSTABLE
88 88 88 88 89 90 90 91 91 92 92 92 92 92 92 93 93 93 94 94 94 94 94 94
SOFTWARE VERSION MIB 802.1X MIBS IEEE8021-PAE-MIB Scalar Objects dot1xPaePortTable dot1xAuthConfigTable dot1xAuthStatsTablenot support dot1xAuthSessionStatsTable(not support) A3COM-HUAWEI-8021PAE-MIB Scalar Objects hwdot1xAuthConfigExtTable A3COM0458-PORT-SECURITY(NOT SUPPORT)
36.1 36.1.1 36.1.2 36.1.3 36.1.4 36.1.5 36.2 36.2.1 36.2.2 36.3 37. 37.1 37.2 37.3 38. FTM MIB
SCALAR OBJECTS H3CFTMUNITTABLE NOTIFICATIONS VOICE VLAN MIB
95 95 96 96
Copyright
Page 6 of 132

V0.13
38.1 38.2 38.3 39. POE MIB
SCALAR OBJECTS H3CVOICEVLANOUITABLE H3CVOICEVLANPORTTABLE(THIS TABLE IS FOR BUCKBEAK VERSION 3.3.2PXX.)
96 96 97 97
39.1 39.2 39.2.1 39.2.2 39.2.3 39.3 39.3.1 39.3.2 40. 40.1 40.2 40.3 41.
PETTHNOTIFICATIONS PETHOBJECTS
pethPsePortTable pethMainPseObjects pethNotificationControl PETHCONFORMANCE pethComplicance pethGroups
97 97 97 98 98 98 98 98 98 98 99 99 99 99 99
99
POE EXT MIB

H3CPSEPORTTABLE H3CMAINPSETABLE SCALAR OBJECTS
A3COM-QOS-PROFILE-MIB DEFINITIONS QOSPROFOBJECTS QosProf

h3cQoSProfTable
41.1 41.1.1
41.1.1.1
41.1.2
41.1.2.1 41.1.2.2
QosActions
h3cQoSTrafficLimitTable h3cQoSTrafficFilterTable
99
99 101
41.1.3
41.1.3.1 41.1.3.2 41.1.3.3
QosProfPortMapping
h3cQoSProfPortMappingTable h3cQoSProfPortMappingModeTable h3cQoSProfDynPortMappingTable
H3CQOSPROFPORTMAPPINGTRAPS
102
102 102 102
41.2 42. 43. 43.1 44. 45. 45.1 46. 46.1 46.2 47. 47.1 48. 48.1 48.2 48.3 48.4 48.5 49. 49.1
102 102 103 103 103 103 103 103 103 103 104 104 104 104 105 105 105 106 106 106
Copyright
3COM-HUAWEI-UI-MAN-MIB A3COM-HUAWEI-ENTRELATION-MIB
H3CENTRELATIONTABLE
SNMP-REPEATER-MIB RFC2108(NOT SUPPORT) A3COM-HUAWEI-IP-BROADCAST-MIB

H3CIPSCALARGROUP
A3COM-HUAWEI-VRRP-EXT-MIB SCALAR OBJECTS H3CVRRPEXTTABLE OF H3CVRRPEXTMIBOBJECT A3COM-HUAWEI-PROTOCOL-PRIORITY-MIB

H3CPROTOCOLPRIORITYTABLE
A3COM- HUAWEI-LSWMSTP-MIB SCALAR OBJECTS HWDOT1SVIDALLOCATIONTABLE HWDOT1SINSTANCETABLE HWDOT1SPORTTABLE TRAPS OF HWMSTPEVENTSV2 A3COM-HUAWEI-RADIUS-MIB SCALAR OBJECTS
Page 7 of 132

V0.13
49.2 50. 50.1 50.2 50.3 50.4 50.5 50.6 50.7 50.8 50.9 51. 51.1 51.2 51.3 51.4 52. 52.1 52.2 53. 53.1 53.2 54.
H3CRDINFOTABLE
106 107 107 108 109 109 109 110 110 110 110 111 111 111 112 113 113 113 114 114 114 114 114 114 115 115 116 118 119 119 119 120 120 120 120 120 120 120 121 121 121 122 122 122 127 127 127 127
Copyright
A3COM-HUAWEI-SYSLOG-MIB
SCALAR OBJECTS H3CSYSLOGLOGBUFFERTABLE H3CSYSLOGTRAPBUFFERTABLE H3CSYSLOGLOGHOSTTABLE H3CSYSLOGCHANNELTABLE H3CSYSLOGMODULETABLE H3CSYSLOGLOGTABLE H3CSYSLOGTRAPTABLE H3CSYSLOGDEBUGTABLE
A3COM-HUAWEI-DOMAIN-MIB SCALAR OBJECTS H3CDOMAININFOTABLE H3CDOMAINSCHEMETABLE H3CDOMAINIPPOOLTABLE (THIS TABLE IS NOT SUPPORTED) A3COM-HUAWEI-LPBKDT-MIB
H3CLPBKDTOBJECTS SUPPORTED PRIVATE TRAPS
A3COM-HUAWEI-LLDP-EXT-MIB SCALAR OBJECTS H3CLLDPPORTCONFIGTABLE SUPPORTED TRAPS SUPPORTED STANDARD TRAPS SUPPORTED PRIVATE TRAPS Common Traps Switch traps
54.1 54.2 54.2.1 54.2.2 55. 56.
FOLLOWING PRIVATE MIB DEFINED IN 3FC-510 ADDITIONAL REQUIREMENT IN 3FC 510 ADDITIONAL AGENT UPDATE REQUIREMENTS ADDITIONAL QOS REQUIREMENTS ADDITIONAL BACKUP / RESTORE REQUIREMENTS IP Address, Default Gateway and Subnet Mask MAC Address Checking HARDWARE CONFIGURATION CHECKING VERSION NUMBERING MIB ITEMS USED BY 3NS BACKUP AND RESTORE
56.1 56.2 56.3 56.3.1 56.3.2 56.4 56.5 56.6 57. 58.
FACTORY DEFAULTS AGENT UPDATING HOW TO UPGRADE THE AGENT 5500 Agent Update Algorithm The MIBs concerned: Functions of the MIBs: An example: HOW TO BACKUP & RESTORE THE AGENT The MIBs concerned: Functions of the MIBs: An example:
58.1 58.1.1 58.1.2 58.1.3 58.1.4 58.2 58.2.1 58.2.2 58.2.3
Page 8 of 132

V0.13
59.
ABOUT 760-174 3 ABOUT SECTION 4.1 3COM REQUIREMENT ABOUT SECTION 4.4 MIB COMPANION ABOUT SECTION 4.5 AGENT VERSION ABOUT SECTION 4.6 TRAP DESTINATION ABOUT SECTION 4.8 TOPOLOGY ABOUT SECTION 4.9 MODULE AND PORT SIZING ABOUT SECTION 4.10 HC-RMON ABOUT SECTION 4.11 AGENT UPDATE ABOUT SECTION 4.12 BACKUP AND RESTORE ABOUT SECTION 4.12 COMPONENT MONITORS ABOUT SECTION 4.14 MANAGEMENT VIA CLI COMMANDS ABOUT SECTION 4.15 POE MIB ABOUT SECTION 5 AGENT-MEDIUM PRIORITY About section 5.1 vlans About section 5.2 device warranty registration About section 5.3 radius and network login ABOUT SECTION 6 AGENT-LOW PRIORITY About section 6.1 Rmon enable About section 6.2 Qos ABOUT SECTION 7 SWITCH MANAGER AND ROUTER MANAGER About section 7.1 Testing About section 7.2 Installation About section 7.3 Supported Platform About section 7.4 Release Notes About section 7.5 new feature list About section 7.6 Device Mimic About section 7.7 Common bug fixes About section 7.8 Co-Existence About section 7.9 vresion number About section 7.10 Improving consistency between SM/RM About section 7.11 Improving online help
128 128 128 129 129 129 129 129 130 130 130 130 130 130 130 130 130 130 130 131 131 131 131 131 131 131 131 131 131 132 132 132 132
59.1 59.2 59.3 59.4 59.5 59.6 59.7 59.8 59.9 59.10 59.11 59.12 59.13 59.13.1 59.13.2 59.13.3 59.14 59.14.1 59.14.2 59.15 59.15.1 59.15.2 59.15.3 59.15.4 59.15.5 59.15.6 59.15.7 59.15.8 59.15.9 59.15.10 59.15.11 60. APPENDIX
Copyright
Page 9 of 132

V0.13
Revision History
Date 2005-06-08 2005-7-21 Author Plat MIB team wangyingxia Reason for Change First Draft 1. modify information about h3cEntityExtErrorStatus ,ifInDiscards, ifInDiscards, entPhysicalSoftwareRev by liyutao 1. modified the port type in entPhysicalVendorType by yangyanhong 2. modified the description of hwMaxMacLearn by zhangjianwei 02811 for D020205 3. modified the description of ifAdminStatus by wanglirong 4. modified the description of dot1dStpTimeSinceTopologyChange by miaochen D20116 5. modified the description of hwifEthernetIsolate by wanglirong for D20223 6. add rfc3418 MIB for D20492 by longyin 7. modified description of hwDhcpToL3AddressCheck for lipei by longyin, buckbeak 1. modified the description of sysObjectId by liyutao for D20613 2. add A3COM-HUAWEI-LswDEVM MIB by panxidong for D20501 3. modified the description of entPhysicalModelName by wangshunli for D20647 4. update snmpUsmMIB and snmpVacmMIB by songjie for D20491 5. modified the description of ipNetToMediaIfIndex by fujiajia for D20609 6. modified the description of h3cVoiceVlanPortEnableList by liaoyuxia for D20729
Revision 0.01 0.02
0.03
2005-07-29
wangyingxia
0.04
2005-08-09
wangyingxia
0.05 0.06 0.07
2005-9-12 2006-9-29 2008-09-10
wangyingxia chenjun wangshunli
1. add a3com-huawei-radius.mib by xulei for D21232 1.add A3COM-HUAWEI-SYSLOG-MIB by chenjun for D30312 1. indicate that ftp protocol also supports to backup and restore for the whole fabric in the section How to backup & restore the agent 1. Added description of h3cCfgOperateTable. 2. Added dot1qVlanStaticTable. 1. Add A3COM-HUAWEI-DOMAIN-MIB mib 1. Modified the description fo h3cCfgOperateFileName 1. Add A3COM-HUAWEI-LPBKDT-MIB mib, inserted before 'Supported Traps' 1. Modified the description fo h3cCfgOperateFileName, When h3cCfgOperateType is Net2Startup or Net2Running, directory is supported at this time 2. Add section 38.3 h3cvoiceVlanPortTable in voice vlan mib 3. Add A3COM-HUAWEI-LLDP-EXT-MIB mib, inserted before 'Supported Traps' 1. Add A3COM-HUAWEI-LLDP-EXT-MIB declaration in section 3 MIB Support & RFC Compliance
Copyright
0.08 0.09 0.10 0.11 0.12
2008-11-05 2009-01-13 2009-05-11 2009-05-18 2009-06-18
Wangshunli Wangshunli Wangshunli Wangshunli Wangshunli
0.13
2009-8-27
Wangshunli
Page 10 of 132

V0.13
ii
No
References
Document
Copyright
Page 11 of 132

V0.13
1.
Introduction
In the tables describing the MIB objects to be supported, the columns means: Name - MIB object name Access - access as defined in MIB. PDS - whether the value always remains the same as the machine rebooting.(permanent data storage) Description - general comments
Copyright
Page 12 of 132

V0.13
2.
Statement
Whether the MIB listed on the document is supported or not depended on the description of it. If the description of the MIB node is not supported, it means the node is not supported by the product even the value of it can be got, the value will be ignored unless it makes problem. If the description of the node is As per MIB, it means the implement of the node is the same as the description of the MIB file. If the node has other description, it means the implement of it is different from the MIB file and the actual implement lies on the document. The MIB not listed in this document will be not supported totally, although the value of the node can be got or set. The meaning of the item access in the document is identical with the MAX-ACCESS in the MIB file. For example: if the MAX-ACCESS of a node in the MIB file is read-write, then the item access in the MIB Companion will be read-write , but if the node only support read in the product, then detailed information will be acquired in the item description of this node in this document For Buckbeak 1, SNMPv1 does not support the get/get-next operation of Counter64 MIB object.
3.
MIB Support & RFC Compliance
Buckbeak will conform to the IETF RFCs/ IEEE standards and Huawei-3Com private standards as described below. Table 1: Buckbeak Support IETF RFCs/IEEE standards Reference
RFC1213
Description
MIB II
Version
1.0
Notes
System and IP groups are supported. The following are partially supported: ifAdminStatus :read-write supported atTable: read-only supported ipForwarding not supported ipDefaultTTL:read-only supported ipRouteTable:read-only supported ipNetToMediaTable:read-only supported tcpConnState :read-only supported EGP group: not supported. snmpMIB is fully supported. partially supported Fully supported. Fully supported. partially supported: snmpNotifyTable Fully supported. Fully supported. Fully supported. 4 groups EtherStats, History, Alarms & Events on Buckbeak The probe configuration group is supported to provide trap destination control. not supported not supported dot1dBase Group, dot1dBasePortTable & dot1dTp Group are fully supported The ifTable is supported. The tunnelIfTable is supported.
Copyright
RFC1907 RFC2233 RFC2571 RFC2572 RFC2573 RFC2573 RFC3414 RFC3415 RFC2819 RFC2021
snmpV2 IF-MIB SNMP-FRAMEWORK-MIB SNMP-MPD-MIB SNMP-NOTIFICATION-MIB SNMP-TARGET-MIB SNMP-USER-BASED-SM-MI B SNMP-VIEW-BASED-ACM-MI B RMON I RMON II Probe Config
1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.1 1.0
RFC2613 RFC3273 RFC1493 RFC2233 RFC2667
SMON HC-RMON-MIB Bridge MIB Interfaces MIB IP Tunnel MIB
1.0 1.0 1.0 1.0
Page 13 of 132

V0.13 RFC2668 RFC2665 Rfc2674 Rfc2674 RFC2674 MAU MIB EtherLike-mib Q-BRIDGE MIB P-BRIDGE MIB Bridge MIB Extensions 1.0 1.0 1.0 1.0 1.0 Partially supported. Only support dot3StatsTable Partially supported Partially supported The following are partially supported :dot1qVlan Group dot1qVlanStaticTable dot1qVlanCurrentTable dot1qPortVlanTable dot1qTp Group dot1qTp Group Only entityPhysicalTable and entLogicalTable are supported at present. Not support read-create Not support read-create Partially supported, Not support sysORLastChange and sysORTable
RFC2737 RFC1253 RFC1724 RFC3418
ENTITY-MIB OSPF-MIB RIPv2-MIB
1.0 1.0 1.0
Table 2: Buckbeak Reference

A3com-huawei-config-man-m ib.mib A3com-huawei-flash-mib.mib A3com-huawei-sys-man,mib A3com-huawei-splat-igsp.mi b A3com-huawei-splat-dhcp.mi b A3com-huawei-dhcpr.mib A3com-huawei-dhcps.mib A3com-huawei-entity-ext.mib hwLswMacPort A3com-huawei-splat-intf.mib A3com-huawei-splat-qos.mib A3COM-HUAWEI-ACL-MIB A3COM-HUAWEI-FTM-MIB
Support Private MIBs Version

1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0
Description
Configuration management mib The flash management mib System management mib mibs for Igmp snooping mibs for dhcp client mibs for dhcp relay mibs for dhcp server Entity environment mib Mac address management Interface management QOS Topology management of fabric Licence mib
Notes
Fully supported Fully supported Fully supported Fully supported Partially supported Not support hwDhcpToL3AddressCheck Fully supported Fully supported Fully supported Fully supported Partially supported. Partially supported. Partially supported. Fully supported
LCS MIB A3COM-HUAWEI-IP-BROADC AST-MIB A3COM-HUAWEI-LLDP-EXTMIB
1.0 1.0 1.0
not supported Fully supported Fully supported
more MIB objects privately For LLDP implementation
Copyright
Page 14 of 132

V0.13
4.
RFC1213 - MIB-II
Only the groups mentioned below are supported. All other MIB-II groups are not supported (udp, tcp, snmp). 4.1 System Group {mib-2.1}
This group is fully supported.
Name
SysDescr
Access
read-only
PDS
Yes
Description
3CR17561-91 "3Com SuperStack 3 Switch 4500 26-Port Software Version 3Com OS V3.01.00s56c01 " 3CR17562-91 "3Com SuperStack 3 Switch 4500 50-Port Software Version 3Com OS V3.01.00s56c01 " 3CR17571-91 "3Com SuperStack 3 Switch 4500 PWR 26-Port Software Version 3Com OS V3.01.00s56c01 " 3CR17572-91 "3Com SuperStack 3 Switch 4500 PWR 50-Port Software Version 3Com OS V3.01.00s56c01 " for the strong encryption, the s56 will be replaced by s168 SysObjectID for Buckbeak switches as follows: -- jvSwitch4500-26 OBJECT IDENTIFIER ::= { jvSwitches 21 } -- jvSwitch4500-50 OBJECT IDENTIFIER ::= { jvSwitches 22 } -- jvSwitch4500-pwr-26 OBJECT IDENTIFIER ::= { jvSwitches 23 } -- jvSwitch4500-pwr-50 OBJECT IDENTIFIER ::= { jvSwitches 24 } As per MIB Set with a blank string 4500 The set operation now only supports 1-30 characters. Set with a blank string 78 (indicates that can provide the following sevices:
datalink/subnetwork (e.g., bridges) internet (e.g., IP gateways) end-to-end (e.g., IP hosts) applications (e.g., mail relays)
SysObjectID
read-only
Yes
SysUpTime SysContact SysName SysLocation SysServices
read-only Read-write Read-write Read-write read-only
No Yes Yes Yes Yes
sysORLastCha nge
read-only
no
) Not supported
4.2
Interfaces Group{mib-2.2}
The Interfaces group is implemented as modified by RFC2233. The ifNumber value will display the actual number of entries in the ifTable. The behaviour of the ifTable entries and the above additional fields is dependant on the type of interface - not all of them apply to all types of interface. See the detailed descriptions below for full details. 4.2.1 ifIndex Value Allocation
The values for ifIndex are as follows:
Copyright
Page 15 of 132

V0.13
unit_id
subslot_num
port_id
Ethernet 2/1/2
interface-type interface-num
Figure 1
Figure 1 Interface name

Figure 2
Figure 3 Figure 4 Figure 2 Interface Index Figure 5 In ULONG index, frame(unit) is behind slot, just to inherit VRP former structure. In figure 2, port_num is calculated by VRP on base of interface name. It is not the global port number notified by DEVM module. It means this number comes from interface name, such as ethernet2/1/2. But a fabric port number is notified by DEVM(Device Management Module of VRP). Frame number range is from 1 to 8(for buckbeak ). Slot is a global board number on fabric wide, begins from 0. For port on unit1, the slot value in ifIndex is 0. And port on unit2, its slot in ifIndex is 1. port_num = subslot_num * MAX_PORT_NUM_EACH_SUBSLOT(52) + port_id. Subslot also can be called sub-card. For port on panel, its subslot_num is 0. Otherwise, subslot_num begins from 1. Some interface, such as vlanif, loopback, null0, we call them logic interface. They exist on each unit of XRN. We define their unit number and slot number 0. But vlanif, loopback and null0 may have same slot and unit with physical ports located on unit 0, slot 0. So we give each type of interface an offset. This index is used in ifTable mib. Figure 6 In the interface name, there is no slot. There is just sub-slot. The topology of sub-slot called by H3C, 3COM call it slot. The are same. Figure 7 In fact, others dont need to care about this offset. Offsets just mean different logic interface is stored in different position. For example, index structure as fllowing: Figure 8 Slot(6bits)/unit(4bits)/position(19bits)/type(3bits)
Figure 9 For logic interface, slot and unit are 0. Null0 position is 1. Inloopback0 is 2. The position of vlan interface will follow Inloopback0. It equals to vlanID(e.g. number 10 in Vlan-interface10) plus 2. We call number 2 offset. And The position of loopback interface follow the vlan-interface. So its position is max vlanID number plus loopback number, 1 and 2. Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 The value of 3 bits type as following: 0: loopback 1: GigabyteEthernet 2: Ethernet 6: Other (reserved port type for future) 7: Vlan-interface Above definition is for product buckbeak, which have one CPU on one device.
Figure 17 For some products, such as 7700, one device has multi slots and multi CPUs. Their interface name will be like ethernet2/2/0/1 if it supports XRN. There are slot and sub-slot in the interface name on the same time.
Copyright
Page 16 of 132

V0.13
For any product which doesnt support XRN function, its interface na me will not have unit-id number. And the ifIndex is different from above definition. 4.2.2 ifTable mib Access
read-only read-only
MIB Objects
ifIndex ifDescr
PDS
Yes Yes
Comments
interface index, described as section 3.2.1
A textual string containing information about the
ifType
read-only
Yes
interface. Here it is interface name, such as Aux0/0/0, null0, Vlan-interface2, ethernet1/0/1 interface type. Value list: inloopback0 is softwareLoopback(24), aux is ppp(23), aux is the serial port (console port ). null0 is other(1), M-Ethernet and Ethernet or GigabyteEthernet are ethernet-csmacd(6),
GigabyteEthernet is 117.
ifMtu
read-only
Yes
ifSpeed
read-only
Yes
ifPhysAddress
read-only
Yes
the buckbeak does not support M-Ethernet. Vlan-interface is 136, etc. Null0 is a internal interface. If the routing entrys next hop is null0 interface, the packet which matchs this entry will be dropped. The size of the largest datagram which can be sent/received by interface in octets. This node is not supported for aux port An estimate of the interface's current bandwidth in bits per second. This node is not supported for aux, null0 and inloopback0 interface. MAC address The following type of interfaces support mac address: Vlan interface: Ethernet port Gigabit Ethernet port Other type of interfaces dont support mac address As to buckbeak products: One mac per port for stp/lacp protocol All vlan interface has same mac address. When stack is built the mac address for vlan interface is the mac address of master unit. This node is not supported for aux, null0 and inloopback0 interface. enable or disable an interface This node is not supported for aux, null0 and inloopback0 interface.
For combo port., if this node is set to up(1) which means this combo port will be enabled, else
ifAdminStatus
read- write
Yes
ifOperStatus
read-only
No
this combo port will be disabled after setting to down(2). Each set operation will make the device reboot, then the set operation will take affect. The current operational state(link status) of the interface. This node is not supported for aux port
Copyright
Page 17 of 132

V0.13 ifLastChange read-only No The value of sysUpTime at the time the interface entered its current operational state. If the current state was entered prior to the last re-initialization of the local network management subsystem, then this object contains a zero value. AS PER MIB This node is not supported for aux, null0 and inloopback0 interface. AS PER MIB This node is not supported for aux, null0 and inloopback0 interface. AS PER MIB This node is not supported for aux, null0 and inloopback0 interface. As per MIB AS PER MIB This node is not supported for aux, null0 and inloopback0 interface. not support This node is not supported for aux port AS PER MIB This node is not supported for aux, null0 and inloopback0 interface. AS PER MIB This node is not supported for aux, null0 and inloopback0 interface. AS PER MIB This node is not supported for aux, null0 and inloopback0 interface. AS PER MIB This node is not supported for aux, null0 and inloopback0 interface. AS PER MIB This node is not supported for aux, null0 and inloopback0 interface. not support Not supported.
ifInOctets
read-only
No
ifInUcastPkts
read-only
No
ifInNUcastPkts
read-only
No
ifInDiscards ifInErrors
read-only read-only
No No
ifInUnknownProtos ifOutOctets
read-only read-only
No No
ifOutUcastPkts
read-only
No
ifOutNUcastPkts
read-only
No
ifOutDiscards
read-only
No
ifOutErrors
read-only
No
ifOutQLen ifSpecific
read-only read-only
No No
4.3
Address Translation Group(at)
{mib-2.3}
This group is fully supported. 4.3.1 Name

atIfIndex atPhysAddress
atTable: Access
read-write read-write
PDS
Yes Yes
Description
As per MIB. ( Not surpport SET operation with index(s) ) As per MIB. ( Not surpport SET operation with index(s) )
Copyright
Page 18 of 132

V0.13 atNetAddress read-write Yes
Write operation is used to create static arp entry,and not support modify existing arp entries.
4.4
IP Group
{mib-2.4}
The following objects will be supported: 4.4.1 Name

ipForwarding ipDefaultTTL ipInReceives ipInHdrErrors ipInAddrErrors ipForwDatagrams ipInUnknownProtos ipInDiscards ipInDelivers ipOutRequests ipOutDiscards ipOutNoRoutes ipReasmTimeout ipReasmReqds ipReasmOKs ipReasmFails ipFragOKs ipFragFails ipFragCreates ipRoutingDiscards
Scalar Objects: Access

read-write read-write read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only
PDS
Yes Yes No No No No No No No No No No No No No No No No No No
Description
As per MIB. The number may be set from 1 to 255 As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB In our system ,the value of this node is same as ipOutNoRoutes
4.4.2 Name
ipAddrTable: Access
read-only read-only read-only read-only read-only
PDS
Yes Yes Yes Yes Yes
Description
As per MIB As per MIB As per MIB As per MIB As per MIB
ipAdEntAddr ipAdEntIfIndex ipAdEntNetMask ipAdEntBcastAddr ipAdEntReasmMaxSize
4.4.3 Name
ipRouteTable: Access
read-write read-write read-write read-write read-write read-write
PDS
No No No No No No
Description
Not writable Not writable Not writable Not writable Not writable Not writable
Copyright
ipRouteDest ipRouteIfIndex ipRouteMetric1 ipRouteMetric2 ipRouteMetric3 ipRouteMetric4
Page 19 of 132

V0.13 ipRouteNextHop ipRouteType ipRouteProto ipRouteAge ipRouteMask ipRouteMetric5 ipRouteInfo read-write read-write read-only read-write read-write read-write read-only No No No No No No No Not writable Not writable As per MIB Not writable Not writable Not writable As per MIB
4.5 4.5.1
TCP Group{mib-2.6}
Scalar objects: Access

read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only
MIB Objects
tcpRtoAlgorithm tcpRtoMin tcpRtoMax tcpMaxConn tcpActiveOpens tcpPassiveOpens tcpAttemptFails tcpEstabResets tcpCurrEstab tcpInSegs tcpOutSegs tcpRetransSegs tcpInErrs tcpOutRsts
PDS
No No No No No No No No No No No No No No
Comments
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
4.5.2
tcpConnTable: Access
read-write read-only read-only read-only read-only
MIB Objects
tcpConnState tcpConnLocalAddress tcpConnLocalPort tcpConnRemAddress tcpConnRemPort
PDS
No No No No No
Comments
Not writable As per MIB As per MIB As per MIB As per MIB
4.6 4.6.1
UDP Group{mib-2.7}
Scalar objects:
A statistics collection for UDP group. MIB Objects

udpInDatagrams udpNoPorts udpInErrors udpOutDatagrams
Access
readonly read-onl y read-onl y read-onl y
PDS
No Yes Yes No
Comments
As per MIB As per MIB As per MIB As per MIB
Copyright
Page 20 of 132

V0.13
4.6.2
udpTable: Access
readonly read-onl y
MIB Objects
udpLocalAddress udpLocalPort
PDS
Yes Yes
Comments
As per MIB As per MIB
4.7
snmp Group{mib-2.11}
MIB Objects
snmpInPkts snmpOutPkts snmpInBadVersions snmpInBadCommunityName s snmpInBadCommunityUses snmpInASNParseErrs snmpInTooBigs snmpInNoSuchNames snmpInBadValues snmpInReadOnlys snmpInGenErrs snmpInTotalReqVars snmpInTotalSetVars snmpInGetRequests snmpInGetNexts snmpInSetRequests snmpInGetResponses snmpInTraps snmpOutTooBigs snmpOutNoSuchNames snmpOutBadValues snmpOutGenErrs snmpOutGetRequests snmpOutGetNexts
Access
read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y read-onl y
PDS
NO N/A Yes N/A Yes Yes Yes Yes Yes Yes Yes N/A Yes N/A N/A Yes N/A N/A Yes Yes Yes Yes Yes Yes
Comments
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB NOT SUPPORTED NOT SUPPORTED As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
Copyright
Page 21 of 132

V0.13 snmpOutSetRequests snmpOutGetResponses snmpOutTraps snmpEnableAuthenTraps snmpSilentDrops snmpProxyDrops read-onl y read-onl y read-onl y read-writ e read-onl y read-onl y Yes N/A Yes YES No No As per MIB As per MIB As per MIB Default value is enabled(1) As per MIB As per MIB
4.8
ARP MIB
ipNetToMediaTable Name
ipNetToMediaIfIndex
Access
read-write
PDS
Yes
Description
Write just references create static ARP entries or delete both static and dynamic ARP entries, but not support modifies existing entries. The ipNetToMediaIfIndex of static ARP always equals to zero. Now just support read-only Now just support read-only Now just support read-only
ipNetToMediaPhysAddres s ipNetToMediaNetAddress ipNetToMediaType
read-write read-write read-write
Yes Yes Yes
5.
ifMIB- RFC2233
Only support ifXTable.

5.1 ifXTable Access
read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-write
MIB Objects
ifName ifInMulticastPkts ifInBroadcastPkts ifOutMulticastPkts ifOutBroadcastPkts ifHCInOctets ifHCInUcastPkts ifHCInMulticastPkts ifHCInBroadcastPkts ifHCOutOctets ifHCOutUcastPkts ifHCOutMulticastPkts ifHCOutBroadcastPkts ifLinkUpDownTrapEnable
PDS
No No No No No No No No No No No No No No
Comments
interface name, same as ifDescr in ifTable AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB Indicates whether linkUp/linkDown traps should be generated for this interface. AUX,Loopback and NULL interface are not support. Now not support.An estimate of the interface's current bandwidth in units of 1,000,000 bits per second.
Copyright
ifHighSpeed
read-only
No
Page 22 of 132

V0.13 ifPromiscuousMode ifConnectorPresent read-write read-only No No Not supported This object has the value 'true(1)' if the interface sublayer has a physical connector and the value'false(2)' otherwise. This object is an 'alias' name for the interface as specified by a network manager, and provides a non-volatile 'handle' for the interface. Default for each interface is HUAWEI, Quidway Series, xxxx Interface or null string. Xxxx is interface name. not support Not support
ifAlias
read-write
Yes
ifCounterDiscontinuityTi me ifStackStatus
read-only
No
6.
EtherLike-MIB-RFC2665
This mib describes generic objects for Ethernet-like network interfaces Only support dot3StatsTable. 6.1 dot3StatsTable Access
read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only
MIB Objects
Dot3StatsIndex Dot3StatsAlignmentError s Dot3StatsFCSErrors Dot3StatsSingleCollision Frames Dot3StatsMultipleCollisio nFrames Dot3StatsSQETestErrors Dot3StatsDeferredTransm issions Dot3StatsLateCollisions Dot3StatsExcessiveCollis ions Dot3StatsInternalMacTran smitErrors Dot3StatsCarrierSenseErr ors Dot3StatsFrameTooLong s Dot3StatsInternalMacRec eiveErrors Dot3StatsetherChipSet Dot3StatsSymbolErrors Dot3StatsDuplexStatus
PDS
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Comments
AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB
Copyright
Page 23 of 132

V0.13
7.
7.1
RFC1493 BRIDGE-MIB
dot1dBase
7.1.1
dot1dBaseBridgeAddress
Access
read-only
MIB Objects dot1dBaseBridgeAddre ss
PDS
No
Comments
As per MIB
7.1.2 dot1dBaseNumPorts
MIB Objects dot1dBaseNumPorts dot1dBaseType MIB Objects dot1dBaseType
Access
read-only
PDS
No
Comments
As per MIB
Access
read-only
PDS
No
Comments
As per MIB
7.1.3 dot1dBasePortTable
MIB Objects
dot1dBasePort dot1dBasePortIfIndex dot1dBasePortCircuit dot1dBasePortDelayExcee dedDiscards dot1dBasePortMtuExceed edDiscards 7.2 dot1dTp
Access
PDS
No No No No No
Comments
7.2.1 dot1dTpLearnedEntryDiscards
MIB Objects
dot1dTpLearnedEntryDisc ards 7.2.2 dot1dTpAgingTime
Access
read-only
PDS
N/A
Comments
Not supported at present
MIB Objects
dot1dTpAgingTime 7.2.3 dot1dTpFdbTable
Access
read-write
PDS
No
Comments
As per MIB, 300s by default
Because the fdb address is obtained from the driver which is developed by 3Com. Our device just retrieves information from driver and the fdb address already stored in memory. So we have not any more measurements to make the quering proceduce faster. Optimizing the driver module to implement a fast and reliable query may be a better way.
Timelimit: maximum 3 seconds for get next response.
MIB Objects
dot1dTpFdbAddress
Access
read-only
PDS
No
Comments
As per MIB
Copyright
Page 24 of 132

V0.13 dot1dTpFdbPort dot1dTpFdbStatus read-only read-only No No As per MIB As per MIB
7.2.4 dot1dTpPortTable
MIB Objects
dot1dTpPort dot1dTpPortMaxInfo dot1dTpPortInFrames dot1dTpPortOutFrames dot1dTpPortInDiscards
Access
PDS
No No No No No
Comments
As per MIB As per MIB Not Support Not Support Not Support
8.
RFC2674 P-BRIDGE-MIB Q-BRIDGE-MIB
Support the Q-BRIDGE MIB and P-BRIDGE MIB. 8.1 P-BRIDGE MIB
Support dot1dExtBase group and dot1dPriority group. The dot1dTrafficClassTable is not supported. 8.1.1
dot1dExtBase { pBridgeMIBObjects.1}
Scalar object: MIB Objects

dot1dDeviceCapabilities dot1dTrafficClassesEnable d dot1dGmrpStatus
Access
read-only read-only read- write
PDS
No No No
Comments
As per MIB As per MIB Only support read-only access not support
dot1dPortCapabilitiesTable MIB Objects

dot1dPortCapabilities
Access
read-only
PDS
No
Comments
Capability information of the port.
8.1.2
dot1dPriority{ pBridgeMIBObjects.2}
Only support dot1dPortPriorityTable. dot1dPortPriorityTable MIB Objects

dot1dPortDefaultUserPriority dot1dPortNumTrafficClasses
Access
read- write read-only
PDS
No No
Comments
As per mib Not supported
8.2
Q-BRIDGE MIB
The Q-BRIDGE-MIB is not supported in buckbeak.
Copyright
Page 25 of 132

V0.13
9.
9.1
SNMP Protocol MIBs

SnmpMIB { snmpModules.1}
This MIB is fully supported. Name

snmpTrapOID
Access
accessible-for-noti fy accessible-for-noti fy
PDS
No
Description
As per MIB
snmpTrapEnter prise coldStart warmStart authenticationF ailure snmpSetSerial No
No
As per MIB
N/A N/A N/A Read-write No
9.2
snmpFrameworkMIB{ snmpModules.10}

snmpEngineID
Access
Read-onl y Read-onl y
PDS
YES
Description
As per MIB
snmpEngineBoots
YES
snmpEngineTime
Read-onl y Read-onl y
No
The value of this node is the number of times that the SNMP engine has (re-)initialized itself since its initial configuration." As per MIB
snmpEngineMaxMe ssageSize
YES
As per MIB
9.2.1
the allocation of snmpEngineID
The snmpEngineID has a length of 11 octets: 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. The fifth octet is 3 indicates that the following is MAC address. The remaining six octets are the MAC address main board. 9.3 snmpMPDMIB{ snmpModules.11}

snmpUnknownSecurity Models
Access
Read-only
PDS
No
Description
As per MIB
Copyright
Page 26 of 132

V0.13 snmpInvalidMsgs snmpUnknownPDUHand lers Read-only Read-only No No As per MIB As per MIB
9.4
snmpTargetMIB{ snmpModules.12}
This MIB is fully supported. snmpTargetAddrTable and snmpTargetParamsTable combined are used to create a valid target host row in device. This entry can be displayed as snmp-agent target-host trap address udp-domain There are some rules need conformed with. For a valid target host entry which is made up of one entry in snmpTargetAddrTable and another entry in snmpTargetParamsTable, 1) The value of snmpTargetAddrName is the same as the value of snmpTargetAddrParams. 2) The value of snmpTargetAddrParams is the same as the value of snmpTargetParamsName. 3) The value format of snmpTargetAddrName is something like "traphost." + snmpTargetParamsSecurityName + IpAddress. The IpAddress is the ip address part of snmpTargetAddrTAddress. If IpAddress not equal to the four frontal octets of snmpTargetAddrTAddress,it will return error. 4) The value of snmpTargetAddrTagList must be octect string "TrapeHost". 5) The value of snmpTargetAddrTDomain must be snmpUDPDomain. 6) The value of snmpTargetAddrStorageType should be nonVolatile. 7) The length of snmpTargetParamsSecurityName in snmpTargetAddrParams restricted in 1 to 32 octets. 8) The value of snmpTargetAddrRowStatus can not be set to notInService or notReady. It means that if the a row in this table is active, it can not be set to other state excepted destroy(6). 9) After a row active, set operation can be done on all object excepted the index snmpTargetAddrName. Summarizetly, before a success create row operation, the index must be correctly, and the format of the index is hex code. The snmpTargetAddrRowStatus must be set to createAndGo, value of snmpTargetAddrTagList must be octect string "TrapeHost", value of snmpTargetAddrTDomain must be snmpUDPDomain. 9.4.1 Name
snmpTargetSpi nLock snmpUnavailab leContexts snmpUnknown Contexts
Scalar objects: Access

Read-write Read- only Read-only
PDS
No No No
Description
As per MIB As per MIB As per MIB
9.4.2 Name
snmpTargetAddrTable Access
Not-acces sible Read-cre ate Read-cre ate Read-cre ate Read-cre
PDS
YES YES YES NO NO
Description
Copyright
snmpTargetAddrName snmpTargetAddrTDomain snmpTargetAddrTAddress snmpTargetAddrTimeout snmpTargetAddrRetryCou
Page 27 of 132

V0.13 nt snmpTargetAddrTagList ate Read-cre ate
YES
snmpTargetAddrParams snmpTargetAddrStorageT ype snmpTargetAddrRowStatu s
Read-cre ate Read-cre ate Read-cre ate
YES YES YES
As per MIB, The string "TrapeHost" must be set when setting snmp trap destination As per MIB As per MIB Only support active createAndGo and destroy
9.4.3 Name
snmpTargetParamsTable Access PD S Description
snmpTargetPar Not-accessi YE As per MIB amsName ble S snmpTargetPar Read-create YE As per MIB amsMPModel S snmpTargetPar Read-create YE As per MIB amsSecurityMo S del snmpTargetPar Read-create YE As per MIB amsSecurityNa S me snmpTargetPar Read-create YE As per MIB amsSecurityLe S vel snmpTargetPar Read-create YE As per MIB amsStorageTy S pe snmpTargetPar Read-create YE Only support active and destroy amsRowStatus S The flowing is an example: ***** SNMP QUERY STARTED ***** 1: snmpTargetSpinLock.0 (integer) 13736 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.54.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.54.46.55.54 (octet string) TrapeHost [54.72.61.70.65.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.54.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.55.54.46.55.54 (integer) active(1)
Copyright
Page 28 of 132

V0.13 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.52.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.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.5 4 (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.5 4 (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 ***** Above is a retrieve for SNMP TARGET entry. Here the index of this entry is 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, which is the hex code of string "traphost.gl.169.254.76.76" The first part, 116.114.97.112.104.111.115.116.46, is hex code of "traphost." string. The second part, 103.108.46, is ascii code of "gl.". The last part, 46.49.54.57.46.50.53.52.46.55.54.46.55.54, is hex code of "169.254.76.76".
9.5
snmpNotificationMIB{ snmpModules.13}
This MIB is partially supported: snmpNotifyTable. 9.5.1 snmpNotifyTable{ snmpNotificationMIB.1}
This table has only one instance. Name

snmpNotifyNa me snmpNotifyTag
Access
not-acces sible Read-crea te Read-crea te Read-crea te
PDS
No YES
Description
As per MIB Only support read-only access
snmpNotifyTyp e snmpNotifySto rageType
YES
Only support read-only access
YES
Only support read-only access
Copyright
Page 29 of 132

V0.13
9.6 9.6.1
snmpUsmMIB{ snmpModules.15} usmStats group { snmpUsmMIB.1}
This group is fully supported. Name

usmStatsUnsu pportedSecLev els usmStatsNotIn TimeWindows usmStatsUnkn ownUserName s usmStatsUnkn ownEngineIDs usmStatsWron gDigests usmStatsDecry ptionErrors usmUserSpinL ock
Access
Read- only
PDS
No
Description
As per MIB
Read- only Read- only
No No
Read- only Read- only Read- only Read-write
No No No No
9.6.2
usmUser group { snmpUsmMIB.2} Scalar objects { usmUser.1}: Access

Readwrite
9.6.2.1 Name
PDS
No
Description
As per MIB
usmUserSpinL ock
9.6.2.2 Name
usmUserTable { usmUser.2}: Access

Not-accessi ble Not-accessi ble Read-only Read- create Read- create Read- create Read- create Read- create Read- create Read- create Read- create Read- create
PD S
No YE S YE S No YE S No No YE S No No No No
Description
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
Copyright
usmUserEngin eID usmUserName usmUserSecuri tyName usmUserClone From usmUserAuthP rotocol usmUserAuthK eyChange usmUserOwnA uthKeyChange usmUserPrivPr otocol usmUserPrivKe yChange usmUserOwnP rivKeyChange usmUserPublic usmUserStorag
Page 30 of 132

V0.13 eType usmUserStatus
Read- create
YE S
As per MIB
9.7
snmpVacmMIB{ snmpModules.16}
9.7.1 vacmMIBObjects
A configuration management MIB, includes the VACM information of SNMP. The VACM(View-based Access Control) Model defines a set of services that an application (such as a Command Responder or a Notification Originator application) can use for checking access rights. It is the responsibility of the application to make the proper service calls for access checking.
SNMP engine (identified by snmpEngineID)
Dispatcher
Message Processing Subsystem
Security Subsystem
Access Control Subsystem

View-based Access Control Model
9.7.1.1
vacmContextTable { vacmMIBObjects.1}
This table is fully supported. This object has only one instance of - Name
vacmContextN ame
Access
Read- only
PDS
YES
Description
As per MIB
9.7.1.2 Name
vacmSecurityToGroupTable { vacmMIBObjects.2} Access

not-acces sible not-acces sible Readcreate Readcreate Readcreate
PDS
No No No No
Description
vacmSecurityM odel vacmSecurityN ame vacmGroupNa me vacmSecurityT oGroupStorage Type vacmSecurityT oGroupStatus
No
As per MIB
Copyright
Page 31 of 132

V0.13
9.7.1.3 Name
vacmAccessTable { vacmMIBObjects.4}:
Access
not-acces sible not-acces sible not-acces sible Readcreate Readcreate Readcreate Readcreate Readcreate Readcreate
PDS
No No No YES YES YES YES No YES
Description
The Value of this object must be - As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
vacmAccessCo ntextPrefix vacmAccessSe curityModel vacmAccessSe curityLevel vacmAccessCo ntextMatch vacmAccessRe adViewName vacmAccessWr iteViewName vacmAccessNo tifyViewName vacmAccessSt orageType vacmAccessSt atus
9.7.2
vacmMIBViews Scalar
9.7.2.1
{ vacmMIBViews.1}
This group is fully supported. Name

vacmViewSpin Lock
Access
Readwrite
PDS
NO
Description
As per MIB
9.7.2.2 Name
vacmViewTreeFamilyTable{ vacmMIBViews.2}
Access
not-acces sible not-acces sible Readcreate Readcreate Readcreate Readcreate
PDS
No
Description
As per MIB
vacmViewTree FamilyViewNa me vacmViewTree FamilySubtree vacmViewTree FamilyMask vacmViewTree FamilyType vacmViewTree FamilyStorage Type vacmViewTree FamilyStatus
No No No No
No
As per MIB
10. RMON MIBs

10.1 RFC2819 - RMON 1
The following RMON groups are supported:
Copyright
Page 32 of 132

V0.13
10.1.1
Statistics
etherStatsTable is fully supported. The maximum entries for the table are 100; Direction for Creating a row in this table:
The steps to create a new row under the table of etherStatsTable through MIB Browser is as usual. Only one column need to be created in etherStatsTable, please set a value for etherStatsDataSource, which should be the value of ifindex OID. And then, you could find this new added row through the walk operation or the command of "dis rmon statistics unit 1" under CLI.
MIB Objects
etherStatsIndex etherStatsDataSource etherStatsDropEvents ehterStatsOctets etherStatsPkts etherStatsBroadcastPkts etherStatsMulticastPkts etherStatsCRCAlignErrors etherStatsUndersizePkts etherStatsOversizePkts etherStatsFragments etherStatsJabbers etherStatsCollisions etherStatsPkts64Octets etherStatsPkts65to127Octets etherStatsPkts128to255Octets etherStatsPkts256to511Octets etherStatsPkts512to1023Octet s etherStatsPkts1024to1518Octe ts etherStatsOwner etherStatsStatus
Access
Read-only Read-creat e Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-creat e Read-creat e
PDS
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO
Comments
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
10.1.2
History
historyControlTable: The maximum entries for the table are 100; The max buckets in historyControlTable are 10; MIB Objects
historyControlIndex CoryControlDataSource historyControlBucketsRequest ed
Access
Read-only Read-creat e Read-creat e
PDS
NO NO NO
Comments
As per MIB As per MIB Our software only supports 10 buckets at maximum currently, If a value more than 10 is input, our software will return success, but the historyControlBucketGranted will be assigned to 10 as for implementation. Our software only supports 10 buckets at maximum currently
Copyright
historyControlBucketsGranted
Read- only
NO
Page 33 of 132

V0.13 historyControlInterval historyControlOwner historyControlStatus Read-creat e Read-creat e Read-creat e NO NO NO The value from 5 to 3600 is supported. As per MIB As per MIB
etherHistoryTable As the definition above, the maximum entries of the table are1000( 100*10); MIB Objects
etherHistoryIndex etherHistorySampleIndex etherHistoryIntervalStart etherHistoryDropEvents etherHistoryOctets etherHistoryPkts etherHistoryBroadcastPkts etherHistoryMulticastPkts etherHistoryCRCAlignErrors etherHistoryUndersizePkts etherHistoryOversizePkts etherHistoryFragments etherHistoryJabbers etherHistoryCollisions etherHistoryUtilization
Access
Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only Read-only
PDS
NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO
Comments
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
10.1.3
Alarm
alarmTable The maximum entries for etherHistoryTable are 60; MIB Objects
alarmIndex alarmInterval alarmVariable alarmSampleType alarmValue alarmStartupAlarm alarmRisingThreshold alarmFallingThreshold alarmRisingEventIndex alarmFallingEventIndex alarmOwner
Access
Read-only Read-creat e Read-creat e Read-creat e Read-only Read-creat e Read-creat e Read-creat e Read-creat e Read-creat e Read-creat e
PDS
NO NO NO NO NO NO NO NO NO NO NO
Comments
As per MIB The range is for 5 to 65535 As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
Copyright
Page 34 of 132

V0.13 alarmStatus Read-creat e NO when setting alarmStatus valid, the return value of success means that the setting operation is accepted by agent successfully. But it doesnt guarantee that the alarmStatus will change to valid. Only the entry of alarmTable meets the requirement of validation,alarmStatus will be valid after setting it.
10.1.4
Event
eventTable: The maximum entries for the table are 60; For every event, the maximum logs are 10; MIB Objects
eventIndex eventDescription eventType eventCommunity eventLastTimeSent eventOwner eventStatus
Access
Read-only Read-creat e Read-creat e Read-creat e Read-only Read-creat e Read-creat e
PDS
NO NO NO NO NO NO NO
Comments
As per MIB As per MIB As per MIB This node dosent take effect As per MIB As per MIB As per MIB
logTable: The maximum entries for the table are 600(60*10) MIB Objects
logEventIndex logIndex logTime logDescription
Access
Read-only Read-only Read-only Read-only
PDS
NO NO NO NO
Comments
10.2
RFC2021
- ProbeConfig
This MIB is not supported. 10.3 RFC3273 - HC-RMON-MIB
The buckbeak products do not supported this mib because of the limitation of BCM silicon. 10.4 RFC2613- SMON
The buckbeak products do not support SMON mib because of the limitation of BCM silicon.
Copyright
Page 35 of 132

V0.13
10.5
A3COM-HUAWEI-PERFORMANCE-MIB - extension to RMON alarm
This MIB is an extension to the RMON alarm. RMON alarm group supplies alarms based on sampling the single object. The extended mib monitors the system alarm by sampling multi objects. In this group, only priAlarmTable is supported. 10.5.1 priAlarmTable Access
read-only read-write read-write read-write
MIB Objects
prialarmIndex prialarmInterval prialarmVariable prialarmSympol
PDS
No No No No
Comments
As per MIB. As per MIB. As per MIB. The value can not be a blank string,and its first charater cant be space. The set operation now only supports 1-128 characters. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. The value can not be a blank string,and its first charater cant be space. The set operation now only supports 1-127 characters. when setting prialarmStatus valid, the return value of success means that the setting operation is accepted by agent successfully. But it doesnt guarantee that the prialarmStatus will change to valid. Only the entry of prialarmTable meets the requirement of validation, prialarmStatus will be valid after setting it.
prialarmSampleType prialarmValue prialarmStartupAlarm prialarmRisingThreshold prialarmFallingThreshold prialarmRisingEventIndex prialarmFallingEventIndex prialarmStatCycle prialarmStatType prialarmOwner
read-write read- only read-write read-write read-write read-write read-write read-write read-write read-write
No No No No No No No No No No
prialarmStatus
read-write
No
10.6
netConfigTable
the netConfigTable is not supported so the following mib nodes are not supported: netConfigIPAddress, probeSoftwareRev, probeHardwareRev
11. RFC2674 - Bridge MIB Extensions

The new Bridge MIB is an extension to the current Bridge MIB (RFC 1493), and is only partially supported by buckbeak . 11.1 dot1qVlan Group Access
read-only
MIB Objects
dot1qVlanNumDeletes
PDS
No
Comments
not support .
Copyright
Page 36 of 132

V0.13 dot1qNextFreeLocalVlanInde x read-only No not support
11.1.1
dot1qVlanStaticTable Access
read-crea te read-crea te read-crea te read-crea te read-crea te
MIB Objects
dot1qVlanStaticName dot1qVlanStaticEgressPorts dot1qVlanForbiddenEgressP orts dot1qVlanStaticUntaggedPor ts dot1qVlanStaticRowStatus
PDS
No No No No No
Comments
Only support read. The value is description of VLAN Not support. Not support. Not support. Not support.
11.1.2
dot1qVlanCurrentTable
this table is not supported.
11.1.3
dot1qPortVlanTable
This table augments dot1dBasePortTable. Table 2 - dot1qPortVlanTable MIB Objects

dot1qPvid dot1qPortAcceptableFrameT ypes dot1qPortIngressFiltering dot1qPortGvrpStatus
Access
Read-rite Read-rite Read-onl y Read-rite
PDS
Yes Yes Yes Yes
Comments
this node not support set operation when the port type is access All set requests will return badValue error. Not support write operation As per mib Support write-access. dot1qPortGvrpStatus should be set before setting this MIB. As per MIB. As per MIB.
dot1qPortGvrpFailedRegistr ations dot1qPortGvrpLastPduOrigi n
read-only read-only
No No
11.2
dot1qTp Group
The dot1qTpGroup is partially supported in buckbeak devices. 11.2.1 dot1qFdbTable
This table is not supported in buckbeak . 11.2.2 dot1qTpFdbTable
Table 3 - dot1qTpFdbTable MIB Objects

dot1qTpFdbPort
Access
read-only
PDS
No
Comments
As per MIB.
Copyright
Page 37 of 132

V0.13 dot1qTpFdbStatus Read-onl y No As per MIB
11.2.3
dot1qTpGroupTable
This table will not be supported by Buckbeak.
12. RFC1850-OSPF(Not support)

This mib file is not supported by Buckbeak because it does not support ospf protocol
13. RFC 1724-RIPv2

13.1 rip2Globals { rip2 1 } Access
read-only read-only
MIB Objects
rip2GlobalRouteChanges rip2GlobalQueries
PDS
No No
Comments
As per MIB. As per MIB.
13.2 13.2.1
rip2IfStatTable { rip2 2 } rip2IfStatEntry { rip2IfStatTable 1 } Access

read-only read-only read-only read-only read-crea te
MIB Objects
rip2IfStatAddress rip2IfStatRcvBadPackets rip2IfStatRcvBadRoutes rip2IfStatSentUpdates rip2IfStatStatus
PDS
Yes No No No No
Comments
As per MIB. As per MIB. As per MIB. As per MIB. Only support read-only access
13.3 13.3.1
rip2IfConfTable { rip2 3 } rip2IfConfEntry { rip2IfConfTable 1 } Access

read-only read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te
MIB Objects
rip2IfConfAddress rip2IfConfDomain rip2IfConfAuthType rip2IfConfAuthKey rip2IfConfSend rip2IfConfReceive rip2IfConfDefaultMetric rip2IfConfStatus rip2IfConfSrcAddress
PDS
Yes Yes Yes Yes Yes Yes Yes No Yes
Comments
As per MIB. Only support read-only access Now support read-only. Now support read-only. Only support read-only access Only support read-only access Only support read-only access Now support read-only. Only support read-only access
Copyright
Page 38 of 132

V0.13
13.4 13.4.1
rip2PeerTable { rip2 4 } Rip2PeerEntry { rip2PeerTable 1 } Access

read-only read-only read-only read-only read-only read-only
MIB Objects
rip2PeerAddress rip2PeerDomain rip2PeerLastUpdate rip2PeerVersion rip2PeerRcvBadPackets rip2PeerRcvBadRoutes
PDS
No No No No No No
Comments
As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB.
14. RFC2668 MAU MIB(Not support)

The Buckbeak products do not support MAU-MIB
15. A3COM-HUAWEI-FLASH-MAN-MIB:Flash management MIBs

This Mib supplies the information for the management of flash devices. 15.1 h3cFlashDevice
Flash device mamagement group(h3cFlashManMIBObjects.1) 15.1.1 h3cFlhSupportNum: The number of flash supported by system.
Table 11.1-1 h3cFlhSupportNum MIB Objects

h3cFlhSupportNum
Access
Read-onl y
PDS
No
Comments
As per MIB
15.1.2
H3cFlashTable: The information for each flash.
Table 11.1-2 h3cFlashTable MIB Objects

h3cFlhIndex
Access
Read-onl y
PDS
No
Comments
The index of h3cFlashTable. It have the minimum vaule of 1, for XRN device, the maximum value is related with the maximum unit number that system supported. As per MIB not support The name for flash, described as follows: As per MIB As per MIB As per MIB As per MIB The value is always false for Buckbeak
Copyright
h3cFlhSize h3cFlhPos h3cFlhName h3cFlhChipNum h3cFlhDescr h3cFlhInitTime h3cFlhRemovable h3cFlhPartitionBool
Read-onl y Read-onl y Read-onl y Read-onl y Read-onl y Read-onl y Read-onl y Read-wri
No No No No No No No No
Page 39 of 132

V0.13 te Read-onl y Read-onl y Read-onl y
h3cFlhMinPartitionSize h3cFlhMaxPartitions h3cFlhPartitionNum
No No No
The value is always 8M for SI and 16M for EI, the unit is bytes The value is always 1 for Buckbeak The value is always 1 for Buckbeak
h3cFlhName named as follows: flash: h3cFlhPos: If the entiy-mib is not implemented, the value for h3cFlhPos is the unit ID in XRN device.
15.1.3
H3cFlashChips:The information for each chip in a flash(h3cFlashManMIBObjects.2)
h3cFlhChipTable:This table is indexed by h3cFlhIndex and h3cFlhChipSerialNo. Each flash may contains several chips, this table provides the information of each chip in a flash. Table 11.1-3 h3cFlhChipTable MIB Objects
h3cFlhChipSerialNo h3cFlhChipID h3cFlhChipDescr h3cFlhChipWriteTimesLimit h3cFlhChipWriteTimes h3cFlhChipEraseTimesLimit h3cFlhChipEraseTimes
Access
Not-acce ssible Read-onl y Read-onl y Read-onl y Read-onl y Read-onl y Read-onl y
PDS
No No No No No No No
Comments
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
h3cFlashPartitions: Flash partition information and files information in the partition. For a given flash indexed by h3cFlhIndex, if it cannot be partitioned, there is only one instance in this table. Table 11.1-4 h3cFlhPartitionTable MIB Objects
h3cFlhPartIndex h3cFlhPartFirstChip h3cFlhPartLastChip h3cFlhPartSpace h3cFlhPartSpaceFree h3cFlhPartFileNum h3cFlhPartChecksumMethod h3cFlhPartStatus h3cFlhPartUpgradeMode
Access
Not-acce ssible Read-onl y Read-onl y Read-onl y Read-onl y Read-onl y Read-onl y Read-onl y Read-onl
PDS
No No No No No No No No No
Comments
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
Copyright
Page 40 of 132

V0.13 y Read-onl y Read-onl y Read-onl y
h3cFlhPartName h3cFlhPartRequireErase h3cFlhPartFileNameLen
No No No
Table 11.1-5 huaweiFlhFileTable The table contains the files in a given partition of a flash, including the hidden files. MIB Objects Access PDS Comments
h3cFlhFileIndex h3cFlhFileName h3cFlhFileSize h3cFlhFileStatus h3cFlhFileChecksum Not-acce ssible Read-onl y Read-onl y Read-onl y Read-onl y No No No No No As per MIB As per MIB As per MIB As per MIB As per MIB
15.2
H3cFlashOperate
This MIB describles the operation in flash group. (h3cFlashManMIBObjects.2) The operation types supported by device are: net2FlashWithErase (1): Copy a file to flash; erase flash before copy. Use the FTP or TFTP protocol. net2FlashWithoutErase (2): Copy a file to flash; do not erase. Note that this command will fail if the PartitionNeedErasure object specifies that the partition being copied to needs erasure. Use the FTP or TFTP protocol. flash2Net (3): Copy a file from flash using the FTP or TFTP protocol. Delete (4): Delete the file specified by h3cFlhOperSourceFile. If the operation is implemented, the file will be deleted from flash completely.
NOTE: To copy a file from (to) flash to (from) the network, the device is regarded as FTP(TFTP) client, and the remote NMS serves as FTP(TFTP) server. To create an instance in the table, CreatAndGo and CreateAndWait operations are available. When ftp 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) 10: opDeviceError(10) 12: opDeviceFull(12) 13: opFileOpenError(13) 14: opFileTransferError(14) 16: opNoMemory(16) 19: opUnknownFailure(19) The following values of H3cFlashOperationStatus are implemented for ftp protocol:
This document is copyrighted and may not be copied or disclosed to a third party without the specific written authority of 3Com. 3Com Corporation. All Rights Reserved Copyright
Page 41 of 132

V0.13 1: opInProgress(1) 2: opSuccess(2) 3: opInvalidOperation(3) 7: opInvalidServerAddress(7) 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 H3cFlashOperationStatus are implemented for delete operation: 1: opInProgress(1) 2: opSuccess(2) 20:opDeleteFileOpenError(20), 21:opDeleteInvalidDevice(21), 22:opDeleteInvalidFunction(22), 23:opDeleteOperationError(23), 24:opDeleteInvalidFileName(24), 25:opDeleteDeviceBusy(25), 26:opDeleteParaError(26),
27:opDeleteInvalidPath(27) Table 11.2-1 h3cFlhOpTable

NOTE:This table must be set before walk, or it will be empty.
MIB Objects
H3cFlhOperIndex H3cFlhOperType H3cFlhOperProtocol h3cFlhOperServerAddre ss h3cFlhOperServerUser h3cFlhOperPassword h3cFlhOperSourceFile h3cFlhOperDestinationF ile
Access
Not-aceesible Read-create Read-create Read-create Read-create Read-create Read-create Read-create
PDS
Comments
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB. Default value is the same as that of h3cFlhOperSourceFile. If the path for file is not specified, the default path of root of flash is used. As per MIB As per MIB. Default value is false As per MIB As per MIB. All the status are supported.
h3cFlhOperStatus h3cFlhOperEndNotificati on h3cFlhOperProgress h3cFlhOperRowStatus
Read-only Read-create Read-only Read-create
No No No No
Note that the algorithm for h3cFlhOperIndex is as the follows: There are two parts for a given h3cFlhOperIndex. The part of first two bytes (from left) is the entity index of unit which is defined in entity MIB (RFC2737). The remaining part of h3cFlhOperIndex is optional and will be ignored.
31
15
0
Copyright
Page 42 of 132

V0.13
+++++++++++++++++++++++++++++++++++++++++++++++ entPhysicalIndex of stack + random index(derived by 3NS) +++++++++++++++++++++++++++++++++++++++++++++++

If entity index part of h3cFlhOperIndex is zero or the entity index of fabric, it means that the operation is for all the units in the fabric. Other values except for the entity index of unit and fabric, and zero are invalid.
16. A3COM-HUAWEI-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. Note: Writing flash can be done by Backup(save) as described in figure 16-1. The object of h3cWriteConfig is replaced by this mib.
Flash
Backup(ftp/tftp) Restore Restore(ftp/tftp) Backup(save) Backup(ftp/tftp) Restore(ftp/tftp)
Memory
Network
Figure 16-1 16.1 The configuration log management- h3cCfgLog mib group
This group defines a collection of objects for management of configuration event log. This group contains six scalar objects and a table. 16.1.1 scalar objects
Table 12.1-1 scalar objects MIB Objects

h3cCfgRunModifiedLast h3cCfgRunSavedLast h3cCfgStartModifiedLast
Access
read-only read-only read-only
PDS
No No No
Comments
Copyright
Page 43 of 132

V0.13
MIB Objects
h3cCfgLogLimitedEntries
Access
read-only
PDS
Yes
Comments
The object shows the maximum number of rows in h3cCfgLogTable. The value supported by the system is 10, and For XRN Devices the vaule is 10 for each unit As per MIB Available for distributed systems. Always false value for a centralized system.
h3cCfgLogDeletedEntries h3cCfgLogWantBackup
read-only read- write
No No
16.1.2
h3cCfgLogTable
Table 12.1-2 h3cCfgLogTables MIB Objects

h3cCfgLogIndex h3cCfgLogTime h3cCfgLogSrcCmd h3cCfgLogSrcData h3cCfgLogDesData h3cCfgLogTerminalType h3cCfgLogTerminalUser
Access
Not-acces sible read-only read-only read-only read-only read-only read-only
PDS
Comments
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB When users modify configuration through SNMP agent, the value of this instance is the name of the write community. As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
h3cCfgLogTerminalNum h3cCfgLogTerminalLocati on h3cCfgLogCmdSrcAddres s h3cCfgLogVirHost h3cCfgLogUserName h3cCfgLogServerAddress h3cCfgLogFile
read-only read-only read-only read-only read-only read-only read-only
16.2
The configuration backup and restore- h3cCfgOperate mib group
Table 12.2-1 scalar objects MIB Objects

h3cCfgOperateGlobalEntry Limit
Access
read-only
PDS
Yes
Comments
The object shows the maximum number of rows in h3cCfgOperateTable. The value supported by the system is 5, and For XRN Devices the vaule is 5 for each unit As per MIB The object shows the maximum number of rows in h3cCfgOperateResultTable. The value can be modified. For XRN system, each unit have a h3cCfgOperateResultTable, the maximum number of rows in this table is no more than the value of h3cCfgOperateResultGlobalEntryLimit.
h3cCfgOperateEntryAgeO utTime h3cCfgOperateResultGlob alEntryLimit
read-wrtie read-write
Yes Yes
Copyright
Page 44 of 132

V0.13 16.2.1 h3cCfgOperateTable
Table 12.2-2 h3cCfgOperateTable MIB Objects

h3cCfgOperateIndex h3cCfgOperateType h3cCfgOperateProtocol h3cCfgOperateFileName
Access
Not-accessi ble read-create read-create read-create
PDS
No No No No
Comments
As per MIB As per MIB The maxinum length of the file name is 52
The value must be specified when h3cCfgOperateType is Net2Startup, Net2Running or Running2Net .The value may include the file path if applicable. When h3cCfgOperateType is Net2Startup or Net2Running , this node specify the source file name of transfers, directory is supported in the filename. When h3cCfgOperateType is Running2Net , this node specify the destination file name of transfers. When h3cCfgOperateType is Startup2Net ,the object may not be
h3cCfgOperateServerAddress h3cCfgOperateUserName h3cCfgOperateUserPassword h3cCfgOperateEndNotificatio nSwitch h3cCfgOperateRowStatus
read-create read-create read-create read-create read-create
No No No No No
created instead of using the file name of startup configuration file. The maxinum length of the file name is 52. As per MIB As per MIB As per MIB As per MIB. Default value is false As per MIB. All the status are supported.
Note that the algorithm for h3cCfgOperateIndex is as the follows: There are two parts for a given h3cCfgOperateIndex. The part of first two bytes (from left) is the entity index of unit which is defined in entity MIB (RFC2737). The remaining part of h3cCfgOperateIndex is the operation index in a unit. For example, the first operation in the unit1 which has the entity index of 2 may be defined as 131073(0x20001). Entity index part of h3cCfgOperateIndex is the entity index of fabric, it means that the operation is for all the units in the fabric. Other values except for the entity index of unit and fabric are invalid. When executing a Backup operation in firbric, the remote filenames will be extended _UnitID as a suffix, and UnitID is from the device where the configuration file generated. The other way round, when a firbric Restore operation occurring, the algorithm makes an exact remote file restore to the only device depend on the suffix of _UnitID.
16.2.2
h3cCfgOperateResultTable
Table 12.2-3 h3cCfgOperateResultTable MIB Objects

h3cCfgOperateResultIndex
Access
Not-accessi ble
PDS
No
Comments
As per MIB
Copyright
Page 45 of 132

V0.13
MIB Objects
h3cCfgOperateResultOptInde x h3cCfgOperateResultOpType h3cCfgOperateState h3cCfgOperateTime h3cCfgOperateEndTime
Access
PDS
No No No No No
Comments
17. A3COM-HUAWEI-SYS-MAN-MIB: System information and system management

This MIB is defined for the general system information management. There are six groups in this mib as follows: System clock management group System reload management group System image management group System configuration files management group System current status group 17.1
h3cSysClock-System clock management group
This group contains only one scalar object which gives the current local time of the system. Table 13.1-1Scalar object MIB Objects
h3cSysLocalClock
Access
Read-only
PDS
No
Comments
As per MIB
17.2
H3cSysReload-System reload management group
This group contains only two scalar objects and a table which gives the reload operation access. Table 13.2-1 Scalar objects MIB Objects
h3cSysReloadSchedule h3cSysReloadAction
Access
Read-write Read- write
PDS
No No
Comments
If the reload action is done,the value will be 0 the set operation is used to set the reload status. The success of set operation of this object does not mean the reload action will succeed, If the reload action is done,the value will be reloadUnavailable As per MIB
h3cSysReloadTag
Read- write
No
Adding an instance to h3cSysReloadScheduleTable does not mean that it can be reloaded at once. It is required to specify the value of h3cSysReloadAction, and h3cSysReloadSchedule or h3cSysReloadTag to perform the reload action. To reboot a device, firstly you must give the value of h3cSysReloadSchedule or h3cSysReloadTag. And then h3cSysReloadAction. The object of h3cSysReloadSchedule is used to reload a specified entity, such as a unit. If multiple units are to be reload, h3cSysReloadTag should be used. h3cSysReloadTag is a tag which can map several entities in the h3cSysReloadScheduleTable by using h3cSysReloadTagList object.
Page 46 of 132

V0.13
Table 13.2-2 h3cSysReloadScheduleTable MIB Objects

h3cSysReloadScheduleIndex h3cSysReloadEntity h3cSysReloadCfgFile h3cSysReloadImage
Access
Not-accessi ble Readcreate Readcreate Readcreate
PDS
No No No No
Comments
As per MIB As per MIB As per MIB when the value is 0 , its means that there is no iamge file for next reboot and its forbidden to reboot. So if you want to reboot certain unit, you must check the value of h3cSysReloadImage First. In each unit, h3cSysReloadImage must be one of value of h3cSysImageIndex in h3cSysImageTable corresponding. As per MIB As per MIB If the value of h3cSysReloadSchedule is not 0, the h3cSysReloadTagList will be ignored, As per MIB
h3cSysReloadReason h3cSysReloadScheduleTime h3cSysReloadTagList
Readcreate Readcreate Readcreate Readcreate
No No No
h3cSysReloadRowStatus
No
NOTE: h3cSysReloadEntity: The value of this object is the entity index which depends on the implementation of ENTITY-MIB. If there is no ENTITY-MIB, the value for this object is the unit ID for XRN devices or 0 for non-XRN device. h3cSysReloadRowStatus: CreatAndGo and CreatAndWait operations are supported. 17.3
h3cSysImage-System image management group
This group contains only one scalar object and a table which gives all the image file available in the system. Table 13.3-1 Scalar objects MIB Objects
h3cSysImageNum
Access
Read-only
PDS
Yes
Comments
As per MIB
Table 13.3-2 h3cSysImageTable MIB Objects

h3cSysImageIndex h3cSysImageName h3cSysImageSize h3cSysImageLocation h3cSysImageType
Access
Not-accessi ble Read-only Read-only Read-only Read-write
PDS
No Yes Yes Yes Yes
Comments
As per MIB As per MIB As per MIB As per MIB For Buckbeak, main , backup and none are supported
The value for h3cSysImageIndex is divided two parts as follows : 31 Entity index 15 Image file index
Copyright
Page 47 of 132

V0.13
For Buckbeak , the entity index is the entPhysicalIndex of Unit as defined in the entPhysicalTable. Other values are invalid. 17.4
h3cSysCFGFile-System wconfiguration files management group
This group contains only one scalar object and a table which gives all the image file available in the system. Table 13.4-1 Scalar objects MIB Objects
h3cSysCFGFileNum
Access
Read-only
PDS
Yes
Comments
As per MIB
Table 13.4-2 h3cSysCFGFileTable MIB Objects Access h3cSysCFGFileIndex Not-accessi ble h3cSysCFGFileName Read-only h3cSysCFGFileSize Read-only h3cSysCFGFileLocation Read-only
PDS No Yes Yes Yes
Comments As per MIB As per MIB As per MIB As per MIB
The value for h3cSysCFGFileIndex is divided two parts as follows : 31 Entity index 15 Configuration file index 0
For buckbeak, the entity index is the entPhysicalIndex of Unit as defined in the entPhysicalTable. Other values are invalid.
17.5
h3cSysCurrent-System current status group
This group includes a table which describes the configuration file and image file used by a specific entity currently. h3cSysCurEntPhysicalIndex: The value of this object is the entity index which depends on the implementation of ENTITY-MIB. If there is no ENTITY-MIB, the value for this object is the unit ID for XRN devices or 1 for non-XRN device. Table 13.5-1 h3cSysCurTable MIB Objects
h3cSysCurEntPhysicalIndex h3cSysCurCFGFileIndex
Access
Not-accessi ble Read-only
PDS
No Yes
Comments
As per MIB As per MIB. If the current used configuration file does not exist,the value will be remain As per MIB. If the current reboot image file does not exist, the value will be remain
h3cSysCurImageIndex
Read-only
Yes
18. A3COM-HUAWEI-LswIGSP-MIB
18.1 18.1.1 HwLswIgmpsnoopingMib { lswCommon 7}
hwLswIgmpsnoopingMibObject { h3cLswIgmpsnoopingMib 1 } Access

read-write
MIB Objects
hwIgmpSnoopingStatus
PDS
yes
Comments
The default setting is disabled
Copyright
Page 48 of 132

V0.13 hwIgmpSnoopingRouterPort Age hwIgmpSnoopingResponseT ime hwIgmpSnoopingHostTime read-write read-write read-write yes yes yes The default value is 105 seconds The default value is 10 seconds The default value is 260 seconds
19. A3COM-HUAWEI-LswDHCP_MIB
19.1 19.1.1 hwLswDhcpMib { lswCommon hwLswDhcpMibObject { 8} }
hwLswDhcpMib 1
19.1.1.1 MIB Objects
hwDhcpGroupTable {hwLswDhcpMibObject 1 } Access

read-crea te read-write read-write read-crea te
PDS
Yes Yes Yes Yes
Comments
As per MIB. As per MIB. As per MIB. As per MIB.
hwDhcpGroupID hwIpDhcpServerAddress1 hwIpDhcpServerAddress2 hwDhcpRowStatus
The above table is for dhcp-server feature and for buckbeak it belongs to phase 2 19.1.1.2 MIB Objects
hwDhcpClientIpAddress hwDhcpClientMacAddress hwDhcpClientProperty hwDhcpClientRowStatus
hwDhcpSecurityTable {hwLswDhcpMibObject 2 } Access

read-only read-write read-write read-crea te
PDS
No Yes Yes Yes
Comments
19.1.1.3 MIB Objects
hwDhcpToL3IfTable {hwLswDhcpMibObject 3 } Access

read-only read-write read-write read-crea te
PDS
No Yes Yes Yes
Comments
As per MIB. As per MIB. Not supported. As per MIB.
hwDhcpToL3VlanIfIndex hwDhcpToL3GroupId hwDhcpToL3AddressCheck hwDhcpToL3RowStatus
20. A3COM-HUAWEI-DHCPR-MIB
This mib is for router not lanswitch so it is not supported on Buckbeak products.
21. LACP MIBs

21.1 IEEE8023-LAG-MIB
21.1.1
dot3adAgg Group dot3adAggTable
21.1.1.1
Table 21.1-1 - dot3adAggTable
Copyright
Page 49 of 132

V0.13
MIB Objects
dot3adAggIndex dot3adAggMACAddress dot3adAggActorSystemPriority dot3adAggActorSystemID dot3adAggAggregateOrIndividual dot3adAggActorAdminKey
Access
Not-accessible read-only read- write read-only read-only read- write
PDS
No No yes No No yes
Comments
As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. Write operation means that the port is added to a specified aggregation and set value equals the aggregation ID As per MIB. As per MIB. As per MIB. As per MIB. As per MIB.(write operation ignored by agent)
dot3adAggActorOperKey dot3adAggPartnerSystemID dot3adAggPartnerSystemPriority dot3adAggPartnerOperKey dot3adAggCollectorMaxDelay
read-only read-only read-only read-only read- write
No No No No yes
21.1.1.2
dot3adAggPortListTable
Table 21.1-2 - dot3adAggPortListTable MIB Objects

dot3adAggPortListPorts
Access
read-only
PDS
No
Comments
Max port number is 52.
21.1.2
dot3adAggPort Group dot3adAggPortTable
21.1.2.1
Table 21.1-3 - dot3adAggPortTable MIB Objects

dot3adAggPortIndex dot3adAggPortActorSystemPriority dot3adAggPortActorSystemID dot3adAggPortActorAdminKey dot3adAggPortActorOperKey dot3adAggPortPartnerAdminSystemPriority dot3adAggPortPartnerOperSystemPriority dot3adAggPortPartnerAdminSystemID dot3adAggPortPartnerOperSystemID dot3adAggPortPartnerAdminKey dot3adAggPortPartnerOperKey dot3adAggPortSelectedAggID dot3adAggPortAttachedAggID dot3adAggPortActorPort dot3adAggPortActorPortPriority dot3adAggPortPartnerAdminPort dot3adAggPortPartnerOperPort dot3adAggPortPartnerAdminPortPriority dot3adAggPortPartnerOperPortPriority dot3adAggPortActorAdminState
Access
Not-accessible read- write read-only read- write read-write read-write read-only read-write read-only read-write read-only read-only read-only read-only read- write read-write read-only read-write read-only read-write
PDS
No yes No yes no yes No yes No yes No No No No yes yes No yes No yes
Comments
As per MIB. As per MIB. As per MIB. As per MIB. As per MIB.(Write operation ignored by agent ) As per MIB.(Write operation ignored by agent) As per MIB. As per MIB.(Write operation ignored by agent) As per MIB. As per MIB.(Write operation ignored by agent) As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB.(Write operation ignored by agent) As per MIB. As per MIB.(Write operation ignored by agent ) As per MIB. As per MIB.(Write operation ignored by agent)
Copyright
Page 50 of 132

V0.13 dot3adAggPortActorOperState dot3adAggPortPartnerAdminState dot3adAggPortPartnerOperState dot3adAggPortAggregateOrIndividual 21.1.3 dot3adAggPortStatsTable read-only read-write read-only read-only No yes No No As per MIB. As per MIB.(Write operation ignored by agent) As per MIB. As per MIB.
Table 21.1-4 - dot3adAggPortListTable
MIB Objects
dot3adAggPortStatsLACPDUsRx dot3adAggPortStatsMarkerPDUsRx dot3adAggPortStatsMarkerResponsePDUsRx dot3adAggPortStatsUnknownRx dot3adAggPortStatsIllegalRx dot3adAggPortStatsLACPDUsTx dot3adAggPortStatsMarkerPDUsTx dot3adAggPortStatsMarkerResponsePDUsTx
Access
read-only read-only read-only read-only read-only read-only read-only read-only
PDS
Comments
As per MIB. 0 is returned at present. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB.
21.1.3.1 dot3adAggPortDebugTable Table 21.1-5 - dot3adAggPortListTable MIB Objects

dot3adAggPortDebugRxState dot3adAggPortDebugLastRxTime dot3adAggPortDebugMuxState dot3adAggPortDebugMuxReason dot3adAggPortDebugActorChurnState dot3adAggPortDebugPartnerChurnState dot3adAggPortDebugActorChurnCount dot3adAggPortDebugPartnerChurnCount dot3adAggPortDebugActorSyncTransitionCount dot3adAggPortDebugPartnerSyncTransitionCount dot3adAggPortDebugActorChangeCount dot3adAggPortDebugPartnerChangeCount
Access
read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only read-only
PDS
No No No No No No No No No No No No
Comments
As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB.
21.1.4
dot3adTablesLastChanged
Table 21.2-1 - dot3adAggPortListTable Name

dot3adTablesLastChanged
Access
read-only
PDS
No
Description
Not implemented.
21.2 21.2.1
A3COM-HUAWEI-LAG-MIB hwAggLinkTable
Table 21.2-1 - hwAggLinkTable MIB Objects

hwAggLinkNumber hwAggLinkName
Access
n/a readcreate
PDS
No yes
Comments
Aggregated link number. Aggregated link Description.
Copyright
Page 51 of 132

V0.13 hwAggLinkMode readcreate yes Type of aggregation. 1 => Manual aggregation, no LACP 2 => Membership specified by user, LACP is used to validate 3 => Completely dynamic aggregation detected by LACP. hwAggLinkMode and hwAggLinkState must be set together List of ports in this AL, by bridge port number. If the type is manual or static, you can update this list to your hearts content. If, however, the AL is dynamic, then the system will maintain it.You are NOT permitted to set the value of this to all zeroes. RowStatus. 1 is returned in read operation hwAggLinkMode and hwAggLinkState must be set together. A PortList of physical ports that have selected to this aggregator, but which have not yet attached.. PortList of physical ports that the same Actor SystemID and partner systemID as this aggregator,but have differing actor and partner keys.
hwAggLinkPortList
readcreate
yes
hwAggLinkState
readcreate read-only read-only
yes
hwAggPortListSelectedPorts hwAggPortListSamePartnerPorts
No No
21.2.2
hwAggPortTable
Table 21.2-2 - hwAggLinkTable MIB Objects

hwAggPortIndex hwAggPortNotAttachedReason
Access
n/a read-write
PDS
No No
Comments
port index reason why this port is selected for an aggregatorbut not attached,-- 1 - all active ports are already.in-use for this aggregator.-- 2 - all aggregation resources are already in-use.-- 3 - the port's configuration is not appropriate. -- 4 - the port's partner is not appropriate. Write operation is ignored by agent Control lacp enble or disable the reason string why this port is selected for an aggregator but not attached. Write operation is ignored by agent
hwAggPortLacpState hwAggPortNotAttachedString
YES No
21.2.3
hwAggResourceAllocationValue
Table 21.2-3- hwAggLinkTable Name

hwAggResourceAllocationValue
Access
read-only
PDS
No
Description
The priority value calculated to decide which aggregations have first call on the load-sharing aggregation resources in the hardware
22. IEEE8021D-STP-MIB
22.1 dot1dStpPortTable
MIB Objects
dot1dStpPort dot1dStpPortPriority dot1dStpPortState dot1dStpPortEnable dot1dStpPortPathCost dot1dStpPortDesignatedRoot dot1dStpPortDesignatedCost dot1dStpPortDesignatedBridge
Access
read-only read-write read-only read-write read-write read-only read-only read-only
PDS
No Yes No Yes Yes No No No
Comments
As per MIB. As per MIB. As per MIB. As per MIB. The Object can not be supported in MSTP. As per MIB. As per MIB. As per MIB.
Copyright
Page 52 of 132

V0.13 dot1dStpPortDesignatedPort dot1dStpPortForwardTransitions 22.2 dot1dStpGlobalTable read-only read-only No No As per MIB. As per MIB.
MIB Objects
dot1dBaseBridgeAddress dot1dStpProtocolSpecification dot1dStpPriority dot1dStpTimeSinceTopologyChange
Access
read-only read-only read-write read-only
PDS
No No Yes No
Comments
As per MIB. As per MIB. As per MIB. The time (in hundredths of a second) since the last time a topology change was detected by the bridge entity Not supported in RSTP The total number of topology changes detected by this bridge since the management entity was last reset or initialized. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB.
read-only dot1dStpTopChanges dot1dStpDesignatedRoot dot1dStpRootCost dot1dStpRootPort dot1dStpMaxAge dot1dStpHelloTime dot1dStpHoldTime dot1dStpForwardDelay dot1dStpBridgeMaxAge dot1dStpBridgeHelloTime dot1dStpBridgeForwardDelay read-only read-only read-only read-only read-only read-only read-only read-write read-write read-write
No
No No No No No No No Yes Yes Yes
23. DISMAN-PING-MIB Ping Algorithm.

This feature will be enabled by using hwPingAgentEnable. Create a row in the pingCtlTable by setting: pingCtlOwnerIndex pingCtlTestName pingCtlTargetAddress pingCtlTimeOut pingCtlProbeCount pingCtlFrequency companion. pingCtlRowStatus '3Com Network Director' '3Com Network Director' destination ipaddress (not needed default is 3 seconds) (not needed default is 1) number of seconds, must be set. Range will be specified in MIB createAndGo(4)
To check the results, use PingResultsTable: pingResultsOperStatus pingResultsIpTargetAddress pingResultsMinRtt pingResultsMaxRtt pingResultsAverageRtt pingResultsProbeResponses pingResultsSentProbes pingResultsRttSumOfSquares Destroy the pingCtlTable row manually.
Page 53 of 132

V0.13
23.1
pingNotifications Access
N/A
Name
pingProbeFailed
PDS
N/A
Description
Generated when a probe failure is detected when the corresponding pingCtlTrapGeneration object is set to probeFailure(0) subject to the value of pingCtlTrapProbeFailureFilter. The object pingCtlTrapProbeFailureFilter can be used to specify the number of successive probe failures that are required before this notification can be generated. Generated when a ping test is determined to have failed when the corresponding pingCtlTrapGeneration object is set to testFailure(1). In this instance pingCtlTrapTestFailureFilter should specify the number of probes in a test required to have failed in order to consider the test as failed.
Generated at the completion of a ping test when the corresponding pingCtlTrapGeneration object is set to testCompletion(4).
pingTestFailed
N/A
N/A
pingTestCompleted
N/A
N/A
23.2
pingCtlTable Access
not-acces sible not-acces sible read-creat e
Name
pingCtlOwnerInd ex pingCtlTestName pingCtlTargetAd dress
PDS
Yes
Yes
Description
As per MIB.( Administrator name) Aggregated link Description.(Ping test name) Specifies the host address to be used at a remote host for performing a ping operation. The host address type is determined by the object value of corresponding pingCtlTargetAddressType. A value for this object MUST be set prior to transitioning its corresponding pingCtlEntry to active(1) via pingCtlRowStatus. Reflects the desired state that a pingCtlEntry should be in: enabled(1) - Attempt to activate the test as defined by this pingCtlEntry. disabled(2) - Deactivate the test as defined by this pingCtlEntry. Refer to the corresponding pingResultsOperStatus to determine the operational state of the test defined by this entry. Specifies the time-out value, in seconds, for a remote ping operation. Specifies the number of times to perform a ping operation at a remote host.
Yes
pingCtlAdminSta tus
read-creat e
Yes
pingCtlProbeCou nt pingCtlTimeOut pingCtlFrequenc y pingCtlRowStatu s
read-create read-create
Yes Yes
read-creat e read-creat e
Yes No
The number of seconds to wait before repeating a ping test is between 0 and 65535 seconds.
This object allows entries to be created and deleted in the pingCtlTable. Deletion of an entry in this table results in all corresponding (same pingCtlOwnerIndex and pingCtlTestName index values) pingResultsTable and pingProbeHistoryTable entries being deleted. A value MUST be specified for pingCtlTargetAddress prior to a transition to active(1) state being accepted. Activation of a remote ping operation is controlled via pingCtlAdminStatus and not by changing this object's value to active(1). Transitions in and out of active(1) state are not allowed while an entry's pingResultsOperStatus is active(1) with the exception that deletion of an entry in this table by setting its RowStatus object to destroy(6) will stop an active ping operation.
The operational state of a ping operation can be determined by examination of its pingResultsOperStatus object.
Page 54 of 132

V0.13
23.3
pingResultsTable Access
read-only read-only read-only
Name
pingResultsOper Status pingResultsIpTar getAddressType pingResultsIpTar getAddress
PDS
No No No
Description
Reflects the operational state of a pingCtlEntry: enabled(1) - Test is active.
pingResultsMinR tt pingResultsMaxR tt pingResultsAver ageRtt pingResultsProb eResponses
read-only
No
read-only
No
read-only read-only
No No
disabled(2) - Test has stopped. This objects indicates the type of address stored in the corresponding pingResultsIpTargetAddress object. This objects reports the IP address associated with a pingCtlTargetAddress value when the destination address is specified as a DNS name. The value of this object should be a zero length octet string when a DNS name is not specified or when a specified DNS name fails to resolve. The minimum ping round-trip-time (RTT) received. A value of 0 for this object implies that no RTT has been received. The maximum ping round-trip-time (RTT) received. A value of 0 for this object implies that no RTT has been received. The current average ping round-trip-time(RTT). Number of responses received for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probe responses have been received. The value of this object reflects the number of probes sent for the corresponding pingCtlEntry and pingResultsEntry. The value of this object MUST be reported as 0 when no probes have been sent. This object contains the sum of the squares for all ping responses received. Its purpose is to enable standard deviation calculation. The value of this object MUST be reported as 0 when no ping responses have been received. Date and time when the last response was received for a probe.
pingResultsSent Probes
read-only
No
pingResultsRttSu mOfSquares
read-only
No
pingResultsLast GoodProbe
read-only
No
23.4
pingProbeHistoryTable Access
not-acces sible
Name
pingProbeHistory Index
PDS
No
Description
An entry in this table is created when the result of a ping probe is determined. The initial 2 instance identifier index values identify the pingCtlEntry that a probe result (pingProbeHistoryEntry) belongs to. An implementation MUST start assigning pingProbeHistoryIndex values at 1 and wrap after exceeding the maximum possible value as defined by the limit of this object ('ffffffff'h). The amount of time measured in milliseconds from when a probe was sent to when its response was received or when it timed out. The value of this object is reported as 0 when it is not possible to transmit a probe. The result of a particular probe done by a remote host. The last implementation method specific reply code
Copyright
pingProbeHistory Response
read-only
No
pingProbeHistory Status pingProbeHistory
read-only read-only
No No
Page 55 of 132

V0.13
LastRC
pingProbeHistory Time
read-only
No
received. If the ICMP Echo capability is being used then a successful probe ends when an ICMP response is received that contains the code ICMP_ECHOREPLY(0). The ICMP responses are defined normally in the ip_icmp include file. Timestamp for when this probe result was determined.
24. A3COM-HUAWEI-PING-MIB
24.1
Name
hwPingAgentEnable
hwPingAgentEnable
Access
read-create
PDS
Yes
Description
Enable Ping test function
25. A3COM-HUAWEI-LswRSTP-MIB
25.1 Scalar Objects: Access
readwrite readwrite readwrite read-only readwrite readwrite readwrite readwrite
MIB Objects
hwdot1dStpStatus hwdot1dStpForceVersion hwdot1dStpDiameter hwdot1dStpRootBridgeA ddress hwDot1dStpBpduGuard hwDot1dStpRootType hwDot1dStpPathCostStan dard hwDot1dTimeOutFactor
PD S
Ye s Ye s Ye s No Ye s Ye s Ye s Ye s
Comments
Whether STP protocol enabled on the bridge. Running mode of RSTP protocol on the bridge. Number of bridges permitted between any of two bridge. Not support. MAC address of root bridge. Weather BPDU Protection enabled. Type of root bridge(primary or secondary) The default path cost standard to compute path cost (dot1d-1998 or dot1t). Time out factor of configuration of port.
25.2
hwdot1dStpIgnoredVlanTable
Table X - hwDot1dStpVlanTable MIB Objects

hwDot1dVlan hwDot1dStpIgnore
Access
Read-only read- write
PDS
No yes
Comments
VLAN id supported on the bridge. Whether STP ignore enabled on the specified VLAN above
25.3
hwDot1dStpPortXTable
MIB Objects
hwdot1dStpPortStatus hwdot1dStpPortEdgeport hwdot1dStpPortPointToPoint hwdot1dStpMcheck
Access
read- write read- write read- write read- write
PDS
Yes Yes Yes No
Comments
enable/disable stp on this port Whether the port can be configured as an edge port. Whether the port can be configured as a point-to-point port Monitor whether entered port migration state machine.
Copyright
Page 56 of 132

V0.13 hwdot1dStpTransLimit hwdot1dStpRXStpBPDU hwdot1dStpTXStpBPDU hwdot1dStpRXTCNBPDU hwdot1dStpTXTCNBPDU hwdot1dStpRXRSTPBPDU hwdot1dStpTXRSTPBPDU hwdot1dStpClearStatistics hwdot1dStpRootGuard hwdot1dStpLoopGuard hwdot1dSetStpDefaultPortCost hwdot1dStpPortBlockedReason hwdot1dStpRXTCBPDU 25.4 hwRstpEventsV2 read- write read-only read-only read-only read-only read-only read-only Read-write read- write read- write write-only read-only Read-only Yes No No No No No No No Yes Yes No No No Max BPDU permitted to transmit during a hello time. Number of STP BPDU received. Number of STP BPDU transmitted. Number of TCN BPDU received. Number of TCN BPDU transmitted. Number of RSTP BPDU received. Number of RSTP BPDU transmitted. Clear statistics of RSTP. Reading value is not signification and always return clear(1). Configure Root protection of port. Configure Loop protection of port. Set path cost back to default value The reason why the port is blocked. As per mib
MIB Objects
hwRstpBpduGuarded
Access
accessibl e-for-notif y accessibl e-for-notif y accessibl e-for-notif y accessibl e-for-notif y
PDS
No
Comments
An edged port of the BPDU-guard switch received BPDU packets. A root-guard port receives a superior BPDU
No
hwRstpRootGuarded hwRstpBridgeLostRootPr imary hwRstpLoopGuarded
No
The bridge is no longer the root bridge of the spanning tree. Another switch with higher priority has already been the root bridge. A loop-guard port is aged out
No
26. Device Manangement MIBs

26.1 26.1.1
entity mib-RFC2737
entityPhysicalTable
{ entityPhysical
1}
26.1.1.1 OverViews entityPhysicalTable describe the relationship of all the entities and other useful information corresponding to them. PhysicalClass:
All the entities can be classified to one of the following physicalclasses. PhysicalClass defined in entity mib-RFC2737 is: SYNTAX INTEGER {
other(1), unknown(2), chassis(3), backplane(4), container(5), powerSupply(6), fan(7),

-- e.g., chassis slot or daughter-card holder
Page 57 of 132

V0.13
sensor(8), module(9), port(10), stack(11) } Some of PhysicalClass of entities in RFC2737 is different from what we called: chassis stack slot subslot board / card Subboard / subcard unit fabric container container module module -- e.g., stack of multiple chassis entities -- e.g., plug-in card or daughter-card
Entity relations:
By 4: entPhysicalContainedIn and 6: entPhysicalParentRelPos , a Physical Entity Relation Treecan be uniquely constructed. The following graph shows the Physical Entity Relation Tree of Buckbeak. The figure inside the circle is the PhysicalIndex of the entity and the figure outside the circle is PhysicalClass + ID. Each PhysicalClass may have several instance(or called entity), and each instance is identified by a unique and fixed physicalIndex. Only in this way can we know the exact position of the entity in the tree, that is which entity it is contained in, and its relative postion among its siblings. Chain of container and containee: Fabric-->unit-->Slot-->board | power | Fan
| -->SubSlot-->SubCard-->Port
Rule of numbering PhysicalIndex of each entity 1. fabric is always 1; 2. in each unit, PhysicalIndex is increase 1 from the first entity of the unit to the last entity. In the same layer in the tree, numbering order is from left to right. Between the layers in the tree, numbering order is from up to down. The next unit will be numbered only after all the entities of the previous unit is completely numbered.
Fabric 1
Unit 1 2
Unit 2 63
Unit3
Unit 4 124
Unit 5 185
Unit6 242
Unit7 303
Unit8 364 425 Unit 2
This document is copyrighted and may not be copied or disclosed to a third party without the specific written authority of 3Com. 3Com Corporation. All Rights Reserved 3 4 5 6
Card 0 7
Power 1
Slot 0
Slot 1
Slot 2
Slot 3
63
Copyright
COMPANY CONFIDENTIAL: NOT FOR EXTERNAL Slot 0 DISTRIBUTION Slot 1 Slot 2

Power 2
Fan 1
Page 58 of 132
Slot 3 66 67 Fan 1
10 Card 0
64
Power 1
65
Power 2

V0.13
Unit 5 242
Unit 6 303
Slot 0 243 Card 0
Slot 1
Slot 2 244 245
Slot 3 246 Fan 1 249 250
Slot 0 304 Card 0 308
Slot 1
Slot 2 305 306
Slot 3 307 Fan 1 310 311
Power 1
Power 2
Power 1
Power 2
247
248
309
Sslot 0 251
Scard 0
Sslot 0 312
Scard 0
252
313
Port 0 253
Port50 302 Unit 7
Port 0 314
Port50 363 Unit 8
364
425
Slot 0
Slot 1
Slot 2
Slot 3
Slot 0
Slot 1
Slot 2
Slot 3
This document is copyrighted and be copied or disclosed 365may not 366 367 368 to a third party without the specific written 426 authority 427 of 3Com. 428 3Com Corporation. All Rights Reserved
Card 0
Copyright 429
Fan 1
COMPANY NOT FOR EXTERNAL DISTRIBUTION Power 1 CONFIDENTIAL: Power 2 Power 1 Fan 1 Card 0
Page 59 of 132
372
Power 2
369
370
371
430
431
432
433

V0.13
26.1.1.2 Index Range Table: The Buckbeak products have 8 units in a stack and 1 slot , 2 power, 1 fan, 1 board per solt per unit, 50 ports per board at most. The following table show the index range of each physical class of each unit. Port on subcard changed to stack port if this port is used to connect between units. index range Unit1 EntPysic alContai nedin 0 1 3 7 8,9 10 entPhysi calParent RelPos -1 1 1 1 1 1 Unit2 EntPysic alContain edin 0 1 64 68 69,70 71 1 1 entPhysi calParent RelPos -1 2 1 Unit3 EntPysic alContain edin 0 1 125 129 130,131 132 entPhysi calParent RelPos -1 3 1 1 1 1 Unit4 EntPysical Containedi n 0 1 186 190 191,192 193 entPhysicalP arentRelPos -1 4 1 1 1 1
stack(fabric ) chassis(Uni t) container level1(slot) moduleleve l1(board) powersuppl y fan
Copyright
Page 60 of 132

V0.13
container level2(subs lot) module level2(subc ard) port on subcard index range
11
72
133
194
12
73
134
195
13..62
1..50
74.. 123
1..50
135..184
1..50
196..241
1..50
Unit5 EntPysic alContai nedin 0 1 243 247 248,249 250 251 entPhysi calParent RelPos -1 5 1 1 1 1 1
Unit6 EntPysic alContain edin 0 1 304 308 309,310 311 312 entPhysi calParent RelPos -1 6 1 1 1 1 1
Unit7 EntPysic alContain edin 0 1 365 369 370,371 372 373 entPhysi calParent RelPos -1 7 1 1 1 1 1
Unit8 EntPysical Containedi n 0 1 426 430 431,432 433 434 entPhysicalP arentRelPos -1 8 1 1 1 1 1
stack(fabric ) chassis(Uni t) container level1(slot) moduleleve l1(board) powersuppl y fan container level2(subs lot) module level2(subc ard) port on subcard Stack port container Stack port
252
313
374
435
253..302
1..50
314..363
1..50
375..424
1..50
436..485
1..50
For Buckbeak product, it is not a frame device, so we regard that the whole device is one board. This board is numbered zero. Board0 is not really existed, it is just to make the physical class hierarchy compatible with that of frame device 26.1.1.3 Sytax or meaning of each object in physical table: Access
not-accessible read-only
MIB Objects
entPhysicalIndex entPhysicalDescr
PDS
N/A N/A
Comments
the index will chage for different products All of the entities should be given.For internal use. See table below.
Copyright
Page 61 of 132

V0.13 entPhysicalVendorType read-only N/A Use MIB objects in vendortype mib List for unit, module, fans, powersupply,submodule. Given a port entry in the physicalentity table, this mib object can be used to identify the parent Used to find out the unit, module, submodule of its children. ENT_PHY_OTHER = 1,/*1*return this /if a known classbut does not match any supported values. ENT_PHY_UNKNOWN,/*2*/not supported ENT_PHY_CHASSIS,/*3*/--unit ENT_PHY_BACKPLANE,/*4*/ not supported ENT_PHY_CONTAINER,/*5*/slot (container level) and subslot (container leve2) ENT_PHY_POWERSUPPLY,/*6*/ supported ENT_PHY_FAN,/*7*/ supported ENT_PHY_SENSOR,/*8*/ not supported ENT_PHY_MODULE,/*9*/board (in slot container level1)and subboard (in subslot container level2) ENT_PHY_PORT,/*10*/ supported ENT_PHY_STACK/*11*/--fabric use this mib object to determine the sibling postion of unit, modules submodules, ports, fans and powersupply As per mib As per mib, Chassis only., xxx:paola to confirm As per mib, Chassis only. xx.yy.zzs56cpp (weak encryption) xxx.yy.zzs168cpp(strong encryption) xx: vrp version number,now it is vrp 3.0 yy.zz: product version number, now it it version 01.04 pp- Minor bug fixes or service pack s: Strong/Strict encryption as opposed to none or weak c:Candidate release MUST come first, mutually exclusive with Patch for example, 3.01.04s56 for the strong encryption, the s56 will be replaced by s168
entPhysicalContainedIn
read-only
N/A
entPhysicalClass
read-only
N/A
entPhysicalParentRelPos
read-only
N/A
entPhysicalName entPhysicalHardwareRev entPhysicalFirmwareRev entPhysicalSoftwareRev
read-only read-only read-only read-only
N/A N/A N/A N/A
Page 62 of 132

V0.13 entPhysicalSerialNum read-write N/A Provide for module, submodule, fans, powersupply. Number .Now only support read. as per mib as per mib Internal use only as per mib. Now only support read-only. as per mib. Now only support read-only. as per mib
entPhysicalMfgName entPhysicalModelName entPhysicalAlias entPhysicalAssetID entPhysicalIsFRU
read-only read-only read-write read-write read-only
N/A N/A N/A N/A N/A
In the following table, if the entity is virtual, all objects exce pt entPhysicalParentRelPos are meaningless to that entity. 26.1.1.3.1 entPhysicalDescr entity
entPhysicalContainedIn and
entPhysicalDescr 1. if the entity has value in VendorType MIB, that value will be filled in. 2. if no value in VendorType MIB, but some poduct request, the request value will be filled in. 3. if no value in VendorType MIB and no request, a null string will filled in.
Number of device module 3CR17561-91 "3Com SuperStack 3 Switch 4500 26-Port Software Version 3Com OS V3.01.00s56c01 " 3CR17562-91 "3Com SuperStack 3 Switch 4500 50-Port Software Version 3Com OS V3.01.00s56c01 " 3CR17571-91 "3Com SuperStack 3 Switch 4500 PWR 26-Port Software Version 3Com OS V3.01.00s56c01 " 3CR17572-91 "3Com SuperStack 3 Switch 4500 PWR 50-Port Software Version 3Com OS V3.01.00s56c01 " for the strong encryption, the s56 will be replaced by s168 CONTAINER LEVEL1 CONTAINER LEVEL2 PSU FAN MODULE LEVEL1 MODULE LEVEL2 slot/port, e unit/slot/port, g unit/slot/port product version of a whole series product, 4500
Unit
Slot SubSlot PowerSupply Fan Board SubCard Port Fabric
26.1.1.3.2 entPhysicalVendorType entity entPhysicalVendorType(need complete VendorType MIB)

Unit No value in vendorType mib SysObjectID of the product a3Com.1.16.4.3.12 null null h3cevtPowerSupplyAC or h3cevtPowerSupplyDC null null null
Slot SubSlot PowerSupply Fan Board SubCard
Copyright
Page 63 of 132

V0.13 Port
h3cevtPortSw-10or100M h3cevtPortSw-1000BaseLxSm h3cevtPortSw-1000BaseSxMm h3cevtPortSw-100MSinglemodeFx h3cevtPortSw-100MMultimodeFx h3cevtPortSw-100M100BaseTx h3cevtPortSw-1000BaseZenithFx h3cevtPortSw-1000BaseLongFx h3cevtPortSw-100MLongFx h3cevtPortSw-1000BaseCx h3cevtPortSw-1000BASE-T h3cevtPortSw-1000BASE-SX-SFP h3cevtPortSw-1000BASE-LX-SFP h3cevtPortSw-1000BASE-T-AN-SFP h3cevtPortSw-1000BASE-ZX-SFP h3cevtPortSw-1000BASE-MM-SFP h3cevtPortSw-100BASE-SX-SFP h3cevtPortSw-100BASE-LX-SFP h3cevtPortSw-100BASE-T-AN-SFP h3cevtPortSw-100BASE-ZX-SFP h3cevtPortSw-100BASE-MM-SFP h3cevtPortSw-SFP-NO-CONNECTOR
Fabric
h3cevtPortSw-SFP-UNKNOWN-CONNECTOR null
26.1.1.3.3 entPhysicalContainedIn entity entPhysicalContainedIn(see index range table above)

Unit Slot SubSlot PowerSupply Fan Board SubCard Port Fabric None None None None None None None None None
26.1.1.3.4 entPhysicalClass entity

Unit Slot SubSlot PowerSupply Fan Board SubCard Port Fabric
entPhysicalClass
chassis(3) container(5) container(5) PowerSupply(6) fan(7) module(9) module(9) Port(10) stack(11)
26.1.1.3.5 entPhysicalParentRelPos entity entPhysicalParentRelPos(see index range table above)

Unit Slot SubSlot None None None
Copyright
Page 64 of 132

V0.13 PowerSupply Fan Board SubCard Port Fabric None None None None None None
26.1.1.3.6 entPhysicalName entity
entPhysicalName(everything can buy should be a name)the index range of Buckbeak is given at the end of the line in the brackets.
Unit+UnitID;Like Unit1 [1..8] Slot+SlotNO;like Slot0 [0..2] SubSlot+SubSlotNO;like SubSlot0 [0] like PSU1 [1] Fan+FanNO;like Fan1 [1] virtual board SubCard+SubCardNO;like SubCard0 [0] like Ethernet 1/0/1 front panel [1..8]/0/[1..50]; XRN Fabic
26.1.1.3.7 entPhysicalHardwareRev entity entPhysicalHardwareRev(everything can buy should be a name)

Unit Slot SubSlot PowerSupply Fan Board SubCard Port Fabric PCB Version of Main board, for example, REV. A None None not available not available None, because it is a logic(virtual) entity. None None None
26.1.1.3.8 entPhysicalFirmwareRev entity entPhysicalFirmwareRev(everything can buy should be a name)

Unit Slot SubSlot PowerSupply Fan Board SubCard Port Fabric BootRomVersion None None None None None, because it is a logic(virtual) entity. None None None
26.1.1.3.9 entPhysicalSoftwareRev entity entPhysicalSoftwareRev(used in Technique Support)

Unit Slot SubSlot PowerSupply Fan The first version is 3.01.00s56c01 None None None None
Copyright
Page 65 of 132

V0.13 Board SubCard Port Fabric None None None None
26.1.1.3.10 entity
Unit Slot SubSlot PowerSupply Fan Board SubCard Port
entPhysicalSerialNum entPhysicalSerialNum
Customer Visible Serial Number None None None None Customer Visible Serial Number none SFP(that is optical module) may have serial number which is stored in ROM of SFP module, other type of ports is an empty string. None
Fabric
26.1.1.3.11 entity
entPhysicalMfgName entPhysicalMfgName must provided

A string 3Com None None A string 3Com A string 3Com None A string 3Com None A string 3Com
26.1.1.3.12 entity
entPhysicalModelName entPhysicalModelName confirm to each entry3C Number chassis

Buckbeak 26 SuperStack 3 Switch 4500 26-Port 3CR17561-91 Buckbeak 50 SuperStack 3 Switch 4500 50-Port 3CR17562-91 Buckbeak 26 PWR SuperStack 3 Switch 4500 PWR 26-Port 3CR17571-91 Buckbeak 50 PWR SuperStack 3 Switch 4500 PWR 50-Port 3CR17572-91 None None none none None, because it is a logic(virtual) entity. none None None
Unit
Slot SubSlot PowerSupply Fan Board SubCard Port Fabric
26.1.1.3.13 entity
Unit
entPhysicalAlias entPhysicalAlias
None
Copyright
Page 66 of 132

V0.13 Slot SubSlot PowerSupply Fan Board SubCard Port Fabric none None None None None None None none
26.1.1.3.14 entity
entPhysicalAssetID entPhysicalAssetID
None None None None None None None None None
26.1.1.3.15 entity
entPhysicalIsFRU entPhysicalIsFRU
True(1) False(2) False(2) True(1) True(1) False(2) True(1) If a SFP(that is optical module) port, True(1); else, False(2) False(2)
26.1.1.4
Example
Buckbeak: one fabric, including 8 Units , each unit has 1 subcards, 1 powers and 1 fans, each subcard has a maximum of 50 ports(50 ports on Front panel, 0 ports for each subcard, here front panel is regared as subcard0. (this example is not finished) User sees Stack Unit 1 slot0(for board0) slot1(for Powersupply1) slot2(for powersupply2) slot3(for fan1) Board0(a virtual board that contains subslots) Powersupply1 Powersupply2 fan1 Subslot0(for front panel) EntPhysi calIndex 1 2 3 4 5 6 7 8 9 10 11 entPhysicalClas s stack (11) chassis (3) container(5) container(5) container(5) container(5) module(9) powerSupply(6) powerSupply(6) fan(7) container(5) EntPysicalC ontainedin 0 1 2 2 2 2 3 4 5 6 7 entPhysicalPare ntRelPos -1 1 0 1 2 3 1 1 1 1 0
Copyright
Page 67 of 132

V0.13
Subcard0(front panel) Port on front panel Port on front panel Unit2 Unit4
12 13 14 63 185
module(9) port(10) port(10) port(10) chassis (3) chassis (3)
11 12 12 12 1 1
1 1 2 2 4
26.1.1.5
Implementation of stack port and combo port
stack port is already supported. . 26.1.1.5.1 OverView Entity MIB is used to express the physical location of the physical entities. Other relations, such as stack port pair and combo port pair, are not suitable to be implemented in Entity MIB. So it is better to create a new MIB to express these relations. The following is the sketch of this new table. There are 3 objects in entityRelationTable, they are entityIndex, entRelationType, relatedEntityIndex , and all of them are indexes of this table to identify one row of this table. This table is designed to express only relationship between entities, so if the status or other information of the entity is wanted, NMS can look into other tables. For example, if the ifDescr of the stack port is wanted, NMS can get ifIndex from AliasMappingTable, and then get ifDescr from ifTable by ifIndex. +----entityRelationTable +----entityIndex +----entRelationType +----relatedEntityIndex 26.1.1.5.2 Definition of each objects 26.1.1.5.2.1 entityIndex the entityIndex is the index of the entity, same as the entPhysicalIndex in Entity MIB. 26.1.1.5.2.2 entRelationType entRelationType describes the relation type of the two entities(indicated by entityIndex and relatedEntityIndex) . entRelationType { stackport, /*(1)*/ comboport /*(2)*/ } stackport: this port is a stack port. entityIndex is the default uplinkport index, and relatedEntityIndex is the default downlinkport index... 26.1.1.5.2.3 relatedEntityIndex relatedEntityIndex is the entity index that entityIndex related to, same as the entPhysicalIndex in Entity MIB. 26.1.1.5.3 examples entPhysicalIndex of stack port on unit1 is 27(uplinkport) and 28(downlinkport); entPhysicalIndex of stack port on unit2 is 132(uplinkport) and 133(downlinkport); stack port connection topology: 27->133132->28;
entityIndex
entRelationType
relatedEntityIndex
Copyright
Page 68 of 132

V0.13
27 132 29
1 1 2
133 28 30
26.1.1.6 Ways to distinguish board from subcard We regard that board and subcard are all module in RFC2737. So NMS cannot distinguish a board from a subcard by reading MIB nodesentPhysicalClass. We designed the following way to distinguish them. PhysicalClass ->ContainedIn->VendorType->slot or subSlot: Explanation in detail: By PhysicalClass, we can get whether the entity is a board or subcard; then by ContainedIn, we can get the PhysicalIndex of the container that it is contained in; then by VendorType, we can read h3cevtContainer and get if it is a h3cevtSlot or h3cevtSubSlot. If h3cevtSlot , then this entity is board; Else if h3cevtSubSlot, then this entity is subcard.
26.1.2
entLogicalTable { entityLogical
1 } (Not support)
This table is not supported now. MIB Objects

entLogicalIndex entLogicalDescr entLogicalType entLogicalCommunity entLogicalTAddress entLogicalTDomain entLogicalContextEngineID entLogicalContextName
Access
not-acces sible read-only read-only read-only read-only read-only read-only read-only
PDS
Comments
As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB. As per MIB.
26.1.3
entLPMappingTable { entityMapping 1 }(Not support)

entLPPhysicalIndex
Access
read-only
PDS
No
Comments
As per MIB.
26.1.4
entPhysicalContainsTable { entityMapping 3 }
Introduction: The input is the pair of ulEntPhysicalIndex and ulEntPhysicalChildIndex, the output is one pair of ulEntPhysicalIndex and ulEntPhysicalChildIndex. MIB Objects
entPhysicalChildIndex
Access
read-only
PDS
No
Comments
As per MIB.
26.1.5
entAliasMappingEntry{ entityMapping
3}
Introduction: this table will be applied to ports. The input is the EntPhysicalIndex of ports, the output is the IfIndex of port. Any port supported in entPhysicalTable will be supported here. MIB Objects Access PDS Comments
Copyright
Page 69 of 132

V0.13 entAliasLogicalIndexOrZero entAliasMappingIdentifier not-acces sible read-only No No As per MIB. As per MIB. Filled with the value of ifIndex of ifTable. Maps port entity index to ifTable index Provides iftable index for ports. For stack ports, it is the ifindex of the normal port corresponding to the stack port.
26.1.6
entityGeneral {entityMIBObjects 4}(Not support)

entLastChangeTime
Access
read-only
PDS
No
Comments
In current design, the LastChangeTime on the master unit will be returned to network management (not support now, and it is to be fixed.)
NOTE: If there are changes in the tables(e.g unit ID change, board plug in/out etc.) above, the device will send out a trap to the network management to ask for an update of the tables. 26.2
A3COM-HUAWEI-ENTITY-EXT-MIB mib
This mib includes the general environment information of the device, which is an extension of entity mib defined in RFC2737. 26.2.1 H3cEntityExtStateTable
The table is indexed by hwEntPhysicalIndex the same as entPhysicalIndex defined in RFC2737. Some objects in the table may be not supported by a specific entity. In that case, the instance for the object has no meaning. For example, h3cEntityCpuUsage for fans has no meaning. MIB Objects
H3cEntityExtPhysicalIndex
Access
Access-fo r-notificat ion read-write read-only
PDS
NO
Comments
The index of the table, the same as the entPhysicalIndex defined in ENTITY-MIB As per MIB. As per mib Represent the possible values of operational states. A value of disabled means the entity goes wrong, and cannot be operated. A value of enabled means the entity is partially or fully operable. As per MIB. not support As per MIB. not support As per MIB. not support As per MIB. As per MIB. supported by PWR device supported by PWR device
Copyright
H3cEntityExtAdminStatus H3cEntityExtOperStatus
NO NO
H3cEntityExtStandbyStatus H3cEntityExtAlarmLight H3cEntityExtCpuUsage H3cEntityExtCpuUsageThreshol d H3cEntityExtMemUsage H3cEntityExtMemUsageThresho ld h3cEntityExtMemSize h3cEntityExtUpTime h3cEntityExtTemperature H3cEntityExtTemperatureThres hold
read-only read-only read-only read-write read-only read-write read-only read-only read-only read-write
NO NO NO NO NO NO NO NO NO NO
Page 70 of 132

V0.13 H3cEntityExtVoltage H3cEntityExtVoltageLowThresh old H3cEntityExtVoltageHighThresh old H3cEntityExtCriticalTemperatur eThreshold H3cEntityExtMacAddress read-only read-write read-write read-write Read-onl y Read-onl y NO NO NO NO No supported by PWR device supported by PWR device not support not support. Not support.Only the entity which has MAC address can support this node. Indicate the port status
notSupported(1), normal(2), postFailure(3), entityAbsent(4), poeError(11), stackError(21), stackPortBlocked(22), stackPortFailed(23), sfpRecvError(31), sfpSendError(32), sfpBothError(33), fanError (41), psuError(51), rpsError(61), moduleFaulty (71)
h3cEntityExtErrorStatus
No
Entity extend property
Stack (Fabric)
Chassis (Unit)
hwEntityAdminStatus (R/W)
Contain er (Slot, SubSlot ) N
Module (board, subcard)
PowerSupply
Fan
Port(excl uding virtual port) Y(port enabled or disabled) Ylinkup linkdown
hwEntityOperStatus (R)
hwEntityStandbyStatus (R) hwEntityAlarmLight (R) hwEntityCpuUsage (R) hwEntityCpuUsageThres hold (R/W) hwEntityMemUsage (R) hwEntityMemUsageThres hold(R/W) hwEntityMemSize (R) hwEntityUpTime (R)
N N N N N N N Y,SysUp Time(bo ot time of the whole
N N N N N N N Y,(boot time of the unit)
Y infact this object is state of board/s ubcard N N N N N N N N
Y Now not support Y Y(Now not support) Y Now not support Y N
Y N N N N N N N
Y N N N N N N N
N N N N N N N N
Copyright
Page 71 of 132

V0.13
hwEntityTemperature (R)
fabric) N
hwEntityTemperatureThr eshold (R/W) hwEntityVoltage(R)
hwEntityVoltageLowThre shold(R/W) hwEntityVoltageHighThre shold(R/W) hwEntityExtCriticleTempe rtatureThreshold(R/W) h3cEntityExtMacAddress
Y(Now not uppport) Y(Now not uppport) Y(Now not uppport) Y(Now not uppport) Y(Now not uppport) Y(Now not uppport)
Y MAC address of master unit in the fabric
Y MAC address of this unit
27. Mac Address Manangement MIBs- hwLswMacPort

This mib is in A3com-huawei-lswman-mib file. 27.1
hwdot1qMacSearchTable { h3cLswMacPort 1 }
NOTE : This table only support Get operation MIB Objects

hwdot1qMacSearchAddress hwdot1qMacSearchVlanID hwdot1qMacSearchPort hwdot1qMacSearchAgeTime
Access
PDS
No No No No
Comments
As per MIB. As per MIB. As per MIB. 0 Dynamic mac-address -1 Blackhole mac-address -1 Static mac-address
27.2
hwdot1qTpFdbSetTable { hwLswMacPort 2 }
MIB Objects
hwdot1qTpFdbSetAddress hwdot1qTpFdbSetPort hwdot1qTpFdbSetStatus hwdot1qTpFdbSetOperate
Access
not-acces sible read-write readwrite write -only
PDS
No No No No
Comments
Copyright
Page 72 of 132

V0.13
28.
A3COM-HUAWEI-LswDEVM -MIB
This MIB contains objects to manage configuration of device management. can be managed by this MIB. All the parameters change events
28.1
hwdevMFanStatusTable
Name
hwDevMFanNum hwDevMFanStatus
Access
read-only read-only
PDS
No No
Description
As Per MIB As Per MIB
28.2
hwdevMPowerStatusTable
Name
hwDevMPowerNum hwDevMPowerStatus
Access
read-only read-only
PDS
No No
Description
As Per MIB As Per MIB
Copyright
Page 73 of 132

V0.13
29. A3COM-HUAWEI-LswINF-MIB
This mib is used for switch only. 29.1 hwifXXTable
Name
hwifUnBoundPor t hwifISPhyPort hwifAggregatePo rt hwifMirrorPort hwifVLANType hwifMcastControl hwifFlowControl hwifSrcMacContr ol hwifClearStat hwifXXBasePortI ndex hwifXXDevPortIn dex hwifPpsMcastCo ntrol
Access
read-only read-only read-only read-write read-write read-write read-write read-only Read-write read-only read-only
read-write
PDS
No No No Yes Yes Yes Yes No No No No NO
Description
As per mib As per mib As per mib Not supported As per mib As per mib.The default value is 100. As per mib.The default value is false(2). As per mib. The default value is false(2). only support write Value list :from 1 to 65535 65535 measns no existed port index Not supported The broadcast suppression with pps(packet per second) type, the max value is determined by the port type and product.
29.2
hwifAggregateTable This table is not supported.
Name
hwifAggregatePo rtIndex hwifAggregatePo rtName hwifAggregatePo rtListPorts hwifAggregateMo del hwifAggregateOp erStatus
Access
read-only read-write read-write read-write read-creat e
PDS
Description
29.3
hwifHybridPortTable
Name
hwifHybridPortIn dex hwifHybridTagge dVlanListLow
Access
read-only read-write
PDS
No Yes
Description
As per mib As per mib
Copyright
Page 74 of 132

V0.13
hwifHybridTagge dVlanListHigh hwifHybridUnTag gedVlanListLow hwifHybridUnTag gedVlanListHigh
Yes Yes Yes
As per mib As per mib As per mib
The values of below nodes must be appointted at the same time when SET operation.: hwifHybridTaggedVlanListLow, hwifHybridTaggedVlanListHigh, hwifHybridUnTaggedVlanListLow, hwifHybridUnTaggedVlanListHigh
29.4 29.4.1
hwifVLANTrunkStatusTable hwifVLANTrunkStatusTable
Access read-only read-only PDS No No Comments Index of VLANTrunk interface. Real VLAN passed through the port every bit denote a VLAN. From1 to 2048 Real VLAN passed through the port every bit denote a VLAN. From 2049 to 4094 VLAN permited to pass through the port.every bit denote a VLAN. From 1 to 2048 VLAN permited to pass through the port.every bit denote a VLAN. From 2049 to 4094
MIB Objects hwifVLANTrunkIndex HwifVLANTrunkPassListLow
HwifVLANTrunkPassListHigh
read-only
No
hwifVLANTrunkAllowListLow
read-write
No
hwifVLANTrunkAllowListHigh
read-write
No
hwifVLANTrunkGvrpRegistration
read-write
Yes
Not supported
29.5 29.5.1
hwethernetTable hwethernetTable
Access read-write PDS Yes Comments interface duplex mode configured by user. value list: full(1) half(2) , auto(3) from the configuration, not actual value MTU on the Ethernet interface Interface speed mode configured by user value list: auto(0) ,s10M(10) ,s100M(100) , s1000M(1000) , s10000M(10000) just from configuration, not actual value Type of the line connected to the port: MDI-II (straight-through cable): 1, MDI-X (crossover cable): 2, MDI-AUTO (auto-sensing): 3 The maximum number of MAC addresses that the port can learn. 65535 is the default value, which doesnt limit the number of mac-address learned.
MIB Objects hwifEthernetDuplex
hwifEthernetMTU hwifEthernetSpeed
Yes Yes
hwifEthernetMdi
read-write
Yes
hwMaxMacLearn
read-write
Yes
Copyright
Page 75 of 132

V0.13 hwifMacAddressLearn read-only No eanbled(1) means the interface can learn mac address, otherwise disabled(2) should be set. When hwMaxMacLearn is set to zero then it will become disabled, Test this interface. Buckbeak doesnt support this item. IVL or SVL. Not support Only support read-only The isolate group that the port belongs to .The maximum number of isolate group can be queried from the node hwIsolateGroupMax The value cannot be set when the ports STP is on.
hwifEthernetTest hwifMacAddrLearnMode hwifEthernetFlowInterval

hwifEthernetIsolate
Write-only Read-only Read-write Read-write
No No Yes yes
hwifVlanVPNStatus
read-write
No
30. A3COM-HUAWEI-LswVLAN-MIB
30.1 30.1.1
hwdot1qVlanMIBTable hwdot1qVlanMIBTable
Access read-only read-write Read-write PDS No No No Comments The VLAN-ID Description of VLAN Port list that belongs to the VLAN. Each bit of hwdot1qVlanPorts represents a port within fabric-wide. In fabric, any port has an exclusive fabric-wide portId. So each bit can means only one fabric wide port. MAX_PORT_NUM_PER_UNIT(=52 for Buckbeak) is a macro which help to distinguish the port of different unit. MAX_PORT_NUM_PER_UNIT indicates the max port number of a unit. So the exclusive fabric wide port number can be acquired from local-unit port number by this way: portId (fabric wide) = (unitId-1)*MAX_PORT_NUM_PER_UNIT+portid (unit-wide). The range of unitId is [1..8] for Buckbeak.. Portid(unit-wide) is [0.. MAX_PORT_NUM_PER_UNIT-1] For example, the first port on unit 2 has a fabric-wide port id: (2-1)* MAX_PORT_NUM_PER_UNIT + 0=64. So the 64th bit of h3cdot1qVlanPorts represents the first port on unit 2. Vlan type Common vlan(2) Sub_vlan(3) Primary_vlan(4) Secondary_vlan(5)
Copyright
MIB Objects hwdot1qVlanIndex hwdot1qVlanName hwdot1qVlanPorts
hwdot1qVlanType
Read-write
No
Page 76 of 132

V0.13 hwdot1qVlanMacFilter hwdot1qVlanMcastUnknownP rotos hwExistInterface hwVlanInterfaceIndex hwdot1qVlanMacLearn hwdot1qVlanStatus hwdot1qVlanCreationTime hwdot1qVlanPriority hwdot1qVlanRowStatus
hwdot1qVlanBroadcastSuppressi on
Read-ony read-only read-only read-only read-only read-only read-only Read-write Read-create read-write
No No No No No No No No No no
Not supported Not supported Whether virtual interface exist. VLAN virtual interface index. Not supported Steate of the VLAN. sysUpTime of the VLAN when the Vlan created. Priotity of the vlan. Only support createAndGo(4), active(1) , destory(6) Not supported.
30.2 30.2.1
hwVlanInterfaceTable hwVlanInterfaceTable
Access read-only read-only read-write PDS No No No Comments Index of virtual interface of VLAN. VLANID Ip address of interface. Set opertion only support Multiple Variable Bindings . This object must bind hwdot1qVlanIPAddressMask. Address mask of interface. Set opertion only support Multiple Variable Bindings. This object must bind hwdot1qVlanIPAddress. State of virtual interface of VLAN. Frame type accepted by virtual interface of VLAN. Only support createAndGo(4), active(1) , destory(6) Not support Not supported.
MIB Objects hwVlanInterfaceID hwdot1qVlanID hwdot1qVlanIPAddress
hwdot1qVlanIPAddressMask
read-write
No
hwVlanInterfaceAdminStatus hwVlanInterfaceFrameType hwInterfaceRowStatus hwDhcpGroupIndex hwVlanInterfaceIPMethod
read-write read-only read-create read-create Read-write
No No No No Yes
30.3 30.3.1
hwVlanInterfaceAddrTable hwVlanInterfaceAddrTable
Access read-only Read-write read-write PDS No No No Comments Interface index of VLAN Ip address of interface. Set opertion only support Multiple Variable Bindings Address mask of interface. Set opertion only support Multiple Variable Bindings Must set this object when create a row
Copyright
MIB Objects hwVlanInterfaceIpIfIndex HwVlanInterfaceIpAddr HwVlanInterfaceIpMask
Page 77 of 132

V0.13 hwVlanInterfaceIpType hwVlanInterfaceIpRowStatus read-write read-create No No Ip address type of interface. Set opertion only support Multiple Variable Bindings Only support createAndGo(4), active(1) , destory(6) Set opertion only support Multiple Variable Bindings
Scalar objects
hwBpduTunnelStatus read-write No As per mib.
31. Time Range Manangement MIBs

This mib is being applied for and may be changed before the final draft. 31.1 hwTrngCreateTimerangeTable
The creation of a time range is implemented by hwTrngCreateTimerangeTable Name Access PDS Description
Yes hwTrngIndex hwTrngName hwTrngValidFlag hwTrngCreateRowStatus not-accessi ble Read-create read- only read-create As per MIB
Yes Yes Yes
As per MIB True for valid. Only support creadandgo(4) to create an instance
31.2
hwTrngAbsoluteTable
hwTrngAbsoluteTable: specify a absolute range for a time range created in hwTrngCreateTimerangeTable. Name Access PDS Description
hwTrngAbsoluteNameIndex hwTrngAbsoluteSubIndex hwTimerangeAbsoluteStartTime hwTimerangeAbsoluteEndTime hwTimerangeAbsolueRowStatus not-accessi ble Not-accessi ble read-create read-create read-create Yes Yes Yes Yes Yes As per MIB As per MIB As per MIB As per MIB Only support creadandgo(4) to create an instance
31.3
hwTrngPeriodicTable
hwTrngPeriodicTable: specify a periodic range for a time range created in hwTrngCreateTimerangeTable. Name Access PDS Description
hwTrngPeriodicNameIndex hwTrngPeriodicSubIndex hwTrngPeriodicDayOfWeek hwTimerangePeriodicStartTime hwTimerangePeriodicEndTime Not-accessi ble Not-accessi ble read-create read-create read-create Yes Yes As per MIB As per MIB
Yes Yes Yes

Copyright
Page 78 of 132

V0.13 Yes hwTimerangePeriodicRowStatus read-create Only support creadandgo(4) to create an instance
32. QOS MIBs

This mib is being applied for and may be changed before the final draft. Name
hwPriorityTrustMode
Access
Read-only
PDS
No
Description
Not supported
32.1 Name
hwQueueTable Access
Read-only Read-write Read-write Read-write Read-write Read-write Read-write Read-write Read-wirte Read-write Read-write
PDS
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Description
Not support Not support Not support Not support Not support
Not support Not support Not support Not support Not support not support
hwQueueIfIndex hwQueueScheduleMode hwQueueWeight1 hwQueueWeight2 hwQueueWeight3 hwQueueWeight4 hwQueueWeight5 hwQueueWeight6 hwQueueWeight7 hwQueueWeight8 hwQueueMaxDelay
32.2
hwRateLimitTable(Not support)
This table is not supported by buckbeak Name

hwRateLimitAclIndex
Access
read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea
PDS
Yes
Description
As Per MIB Now not support set and creat operation. As Per MIB Now not support set and creat operation. The value is 0 Now not support set and creat operation. As Per MIB Now not support set and creat operation. 0 is invalid value 65535 is invalid value As Per MIB, the range is 2000 to 3999 The valid range is 0 to 65534 As Per MIB The valid range is 4000 to 4999. As to buckbeak, it is not
Copyright
hwRateLimitIfIndex
Yes
hwRateLimitVlanID
Yes
hwRateLimitDirection
Yes
hwRateLimitUserAclNum hwRateLimitUserAclRule hwRateLimitIpAclNum hwRateLimitIpAclRule hwRateLimitLinkAclNum hwRateLimitLinkAclRule hwRateLimitTargetRateMbps
Yes Yes Yes Yes Yes Yes Yes
Page 79 of 132

V0.13 te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-only read-crea te read-crea te read-crea te read-crea te supported As to buckbeak, it is supported As to buckbeak, it is not supported as to buckbeak it is supported. not support not support not support not support not support As to buckbeak it is supported. As to buckbeak, it is supported. As Per MIB Now support three state:CreateAndGo,Active,De stroy. As to buckbeak, it is not supported. not support not support
hwRateLimitTargetRateKbps hwRateLimitPeakRate hwRateLimitCIR hwRateLimitCBS hwRateLimitEBS hwRateLimitPIR hwRateLimitConformLocalPre hwRateLimitConformActionTy pe hwRateLimitExceedActionTyp e hwRateLimitExceedDscp hwRateLimitRuntime hwRateLimitRowStatus
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
hwRateLimitExceedCos hwRateLimitConformCos hwRateLimitConformDscp
Yes Yes Yes
32.3
hwPriorityTable (not support)

hwPriorityAclIndex
Access
read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te
PDS
Yes
Description
As Per MIB Now not support set and creat operation. As Per MIB Now not support set and creat operation. The value is 0 Now not support set and creat operation. As Per MIB Now not support set and creat operation. As to buckbeak, it is supported 0 is invalid value As to buckbeak, it is supported As Per MIB 0 is invalid value The valid range is 0 to 65534
Copyright
hwPriorityIfIndex
Yes
hwPriorityVlanID
Yes
hwPriorityDirection
Yes
hwPriorityUserAclNum
Yes
hwPriorityUserAclSubitem hwPriorityIpAclNum hwPriorityUserAclRule
Yes Yes Yes
Page 80 of 132

V0.13 hwPriorityIpAclNum hwPriorityIpAclRule hwPriorityLinkAclNum hwPriorityLinkAclRule hwPriorityDscp hwPriorityIpPre hwPriorityIpPreFromCos hwPriorityCos hwPriorityCosFromIpPre hwPriorityLocalPre hwPriorityPolicedServiceType hwPriorityPolicedServiceDscp hwPriorityPolicedServiceExp hwPriorityPolicedServiceCos hwPriorityPolicedServiceLoaclP re hwPriorityPolicedServiceDropPr iority hwPriorityRuntime hwPriorityRowStatus read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-crea te read-only read-crea te Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes As Per MIB As Per MIB 0 is invalid value The valid range is 0 to 65534 As Per MIB As Per MIB As per MIB As Per MIB As per MIB As Per MIB Not support Not support Not support Not support Not support Not support As Per MIB Now support three state:CreateAndGo,Activ e,Destroy.
32.4
hwRedirectTable(not support)

hwRedirectAclIndex read-create hwRedirectIfIndex read-create hwRedirectVlanID read-create hwRedirectDirection hwRedirectUserAclNum hwRedirectUserAclRule read-create read-create Yes Yes Yes Yes Yes
Access
read-create
PDS
Yes
Description
As Per MIB Now not support set and creat operation. As Per MIB Now not support set and creat operation. The value is 0 Now not support set and creat operation. As Per MIB Now not support set and creat operation. as to buckbeak, it is supported as to buckbeak, it is
Copyright
Page 81 of 132

V0.13 supported as to buckbeak, it is supported The valid range is 0 to 65534 as to buckbeak, it is supported The valid range is 0 to 65534 As to buckbeak, it is supported As Per MIB Not support Not support As Per MIB Now support three state: CreateAndGo, Active, Destroy
hwRedirectIpAclNum hwRedirectIpAclRule hwRedirectLinkAclNum hwRedirectLinkAclRule hwRedirectCpu hwRedirectToIfIndex hwRedirectToNextHop1 hwRedirectToNextHop2 hwRedirectRuntime hwRedirectRowStatus
Yes Yes
read-create read-create read-create read-create read-create read-create read-only read-create
Yes Yes Yes Yes Yes Yes Yes Yes
32.5
hwStatisticTable(Not support)

hwStatisticAclIndex hwStatisticIfIndex hwStatisticVlanID hwStatisticDirection hwStatisticUserAclNum read-create hwStatisticUserAclRule hwStatisticIpAclNum hwStatisticIpAclRule hwStatisticLinkAclNum hwStatisticLinkAclRule hwStatisticRuntime hwStatisticPacketCount hwStatisticByteCount hwStatisticCountClear hwStatisticRowStatus read-only read-only Yes Yes read-create read-create read-create read-create read-only read-only read-only read-write read-create Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Access
read-create read-create read-create read-create read-create
PDS
Yes Yes Yes Yes Yes
Description
As Per MIB As Per MIB The value is 0 As Per MIB As to Buckbeak, it is supported 0 is invalid value As to Buckbeak, it is supported 65535 is invalid value 0 is invalid value The valid range is 0 to 65534 0 is invalid value The valid range is 0 to 65534 As Per MIB As Per MIB As to Buckbeak, it is not support As Per MIB Now support three state: CreateAndGo, Active, Destroy. As to Buckbeak, it is supported Not support
hwStatisticPacketXCount hwStatisticByteXCount
Copyright
Page 82 of 132

V0.13
32.6
h3cMirrorTablenot support
This table is not supported

Name hwMirrorAclIndex Access read-create PDS Yes Description As Per MIB Now not support set and creat operation. 0 is invalid value Now not support set and creat operation. The value is 0 Now not support set and creat operation. As Per MIB Now not support set and creat operation. As to buckbeak, it is supported 0 is invalid value As to buckbeak, it is supported 65535is invalid value Not support Not support Not support Not support As Per MIB as to buckbeak, it is supported Not support Now support three state: CreateAndGo, Active, Destroy
hwMirrorIfIndex
read-create
Yes
hwMirrorVlanID
read-create
Yes
hwMirrorDirection
read-create
Yes
hwMirrorUserAclNum
Read-create
Yes
hwMirrorUserAclRule
Read-create
Yes
hwMirrorIpAclNum hwMirrorIpAclRule hwMirrorLinkAclNum hwMirrorLinkAclRule hwMirrorToIfIndex hwMirrorToCpu hwMirrorRuntime hwMirrorRowStatus
32.7 Name
hwPortMirrorTable Access
read-create
PDS
Yes
Description
As Per MIB Now not support set and creat operation. As Per MIB Now support three state: CreateAndGo, Active, Destroy
hwPortMirrorIfIndex hwPortMirrorDirection hwPortMirrorRowStatus read-create read-create Yes Yes
32.8 Name
hwLineRateTable Access
read-creat e read-creat e read-creat
PDS
Yes Yes Yes
Description
As Per MIB Now not support set and creat operation. As Per MIB Now not support set and creat operation. as to buckbeak, the rate value range is
Copyright
hwLineRateIfIn dex hwLineRateDir ection hwLineRateVal
Page 83 of 132

V0.13 ue hwLineRateRo wStatus e read-creat e 64Kbps to 100Mbps or 1000Mbps Now support three state: CreateAndGo, Active, Destroy
Yes
Hwbandwidthtable is not supported. 32.9 hwRedTablenot support
This mib is not supported. Name Access

hwRedAclIndex hwRedIfIndex hwRedVlanID hwRedDirection hwRedIpAclNum hwRedIpAclRule hwRedLinkAclNum hwRedLinkAclRule hwRedStartQueueLen hwRedStopQueueLen hwRedProbability hwRedRuntime hwRedRowStatus read-create read-create read-create read-create read-create read-create read-create read-create read-write read-write read-write read-only read-write
PDS
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Description
Now support not-accessible , as to buckbeak, it is not support Now support not-accessible , as to buckbeak, it is not support Now support not-accessible , as to buckbeak, it is not support Now support not-accessible , as to buckbeak, it is not support Not support Not support Not support Not support Not support Not support Not support Not support Not support
32.10 hwMirrorGroupTable(not support) This mib is not supported by buckbeak. Name Access
hwMirrorGroupID hwMirrorGroupDirection hwMirrorGroupMirrorIfIndexLi st hwMirrorGroupMonitorIfIndex hwMirrorGroupRowStatus read-write read-write Yes Yes read-only read-write read-write
PDS
Yes Yes Yes
Description
Now support not-accessible AS PER MIB The valid range of IfIndexList is decided by different products: As to buckbeak, all ports can be mirrored. AS PER MIB AS PER MIB
32.11 hwFlowtempTable(not support) This mib is not supported by buckbeak.. Name Access
hwFlowtempIndex hwFlowtempIpProtocol hwFlowtempTcpFlag hwFlowtempSPort read-only read-creat e read-creat e read-creat e
PDS
Yes Yes Yes Yes
Description
Not support Not support Not support Not support
Copyright
Page 84 of 132

V0.13 hwFlowtempDPort hwFlowtempIcmpType hwFlowtempIcmpCode hwFlowtempFragment hwFlowtempDscp hwFlowtempIpPre hwFlowtempTos hwFlowtempSIp hwFlowtempSIpMask hwFlowtempDIp hwFlowtempDIpMask hwFlowtempEthProtocol hwFlowtempSMac hwFlowtempSMacMask hwFlowtempDMac hwFlowtempDMacMask hwFlowtempVpn hwFlowtempRowStatus read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e read-creat e Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support
32.12 hwFlowtempEnableTable(not support) This table is not supported by buckbeak; Name Access
hwFlowtempEnableIfIndex hwFlowtempEnableVlanID hwFlowtempEnableFlowtempIndex read-creat e read-creat e read-write
PDS
Yes Yes Yes
Description
Not support Not support Not support
32.13 hwTrafficShapeTable(not support) This table is not supported by buckbeak;. Name Access
hwTrafficShapeIfIndex hwTrafficShapeQueueId hwTrafficShapeMaxRate read-creat e read-creat e read-creat
PDS
Yes Yes Yes
Description
Copyright
Page 85 of 132

V0.13 e read-creat e read-creat e read-creat e
hwTrafficShapeBurstSize hwTrafficShapeBufferLimit hwTrafficShapeRowStatus
Yes Yes Yes
Not support Not support Only support creadAndGo(4) to create an instance
32.14 hwPortQueueTable(not support) This table is not supported by buckbeak; Name Access
hwPortQueueIfIndex hwPortQueueQueueID hwPortQueueWrrPriority hwPortQueueWeight read-only read-only read-write read-write
PDS
Yes Yes Yes Yes
Description
Not support Not support Not support Not support
32.15 hwDropModeTable(not support) This table is not supported by buckbeak; Name Access
hwDropModeIfIndex hwDropModeMode hwDropModeWredIndex read-only read-write read-write
PDS
Yes Yes Yes
Description
32.16 hwWredTable(not support) This table is not supported by buckbeak; Name Access
hwWredIndex hwWredQueueId hwWredGreenMinThreshold hwWredGreenMaxThreshold hwWredGreenMaxProb hwWredYellowMinThreshold hwWredYellowMaxThreshold hwWredYellowMaxProb hwWredRedMinThreshold hwWredRedMaxThreshold hwWredRedMaxProb hwWredExponent read-only read-only read-write read-write read-write read-write read-write read-write read-write read-write read-write read-write
PDS
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Description
Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support Not support
32.17 hwCosToLocalPrecedenceMapTable(not support) This table is not supported by buckbeak; Name Access
hwCosToLocalPrecedenceMapCosI ndex hwCosToLocalPrecedenceMapLoc read-only read-write
PDS
Yes Yes
Description
Not support AS per mib
Copyright
Page 86 of 132

V0.13 alPrecedenceValue
32.18 hwCosToDropPrecedenceMapTable(not support) This table is not supported by buckbeak; Name Access
hwCosToDropPrecedenceMapCosI ndex hwCosToDropPrecedenceMapDrop PrecedenceValue read-only read-write
PDS
Yes Yes
Description
Not support Not support
32.19 hwDscpMapTable(not support) This table is not supported by buckbeak; Name Access
hwDscpMapConformLevel hwDscpMapDscpIndex hwDscpMapDscpValue hwDscpMapExpValue hwDscpMapCosValue hwDscpMapLocalPrecedence hwDscpMapDropPrecedence read-only read-only read-write read-write read-write read-write read-write
PDS
Description
Not support Not support Not support Not support Not support Not support Not support
32.20 hwExpMapTable(not support) This table is not supported by buckbeak; Name Access
hwExpMapConformLevel hwExpMapExpIndex hwExpMapDscpValue hwExpMapExpValue hwExpMapCosValue hwExpMapLocalPrecedence hwExpMapDropPrecedence read-only read-only read-write read-write read-write read-write read-write
PDS
Description
Not support Not support Not support Not support Not support Not support Not support
32.21 hwLocalPrecedenceMapTable(not support) This table is not supported by buckbeak; Name Access
hwLocalPrecedenceMapConformL evel hwLocalPrecedenceMapLocalPrec edenceIndex hwLocalPrecedenceMapCosValue read-only read-write read-write
PDS
Yes Yes Yes
Description
32.22 hwPortWredTable(not support) This table is not supported by buckbeak;

Page 87 of 132

V0.13
Name
hwPortWredIfIndex hwPortWredQueueID hwPortWredQueueStartLength hwPortWredQueueProbability
Access
read-only read-only read-write read-write
PDS
Yes Yes Yes Yes
Description
AS PER MIB AS PER MIB AS PER MIB AS PER MIB
33. ACL MIBs
33.1 Name
H3cAclMode(not support) Access

read-write
PDS
Yes
Description
Not supported
H3cAclMode
33.2
h3cAclNumGroupTable
Access not-accessible read-create read-only read-write read-create read-create PDS Yes Yes Yes Yes Yes Yes Description The number of the numbered ACL. The match order of the numbered ACL The subitem number of the numbered ACL The description of this acl group Reset the value of count Now support three state:CreateAndGo,Active,Destroy.
Name h3cAclNumGroupAclNum h3cAclNumGroupMatchOrder h3cAclNumGroupSubitemNum h3cAclNumGroupDescription h3cAclNumGroupCountClear h3cAclNumGroupRowStatus
33.3
h3cAclNameGroupTable
It is not supported by buckbeak. Only acl number is supported Name

h3cAclNameGroupIndex h3cAclNameGroupCreateName h3cAclNameGroupTypes h3cAclNameGroupMatchOrder h3cAclNameGroupSubitemNum h3cAclNameGroupRowStatus
Access
read-create read-create read-create read-create read-only read-create
PDS
Yes Yes Yes Yes Yes Yes
Description
The number of the nameed ACL The match order of the nameed ACL The subitem number of the nameed ACL The description of this acl group Reset the value of count Only support creadAndGo(4) to create an instance
33.4
h3cAclBasicRuleTable
This table is not supported by buckbeak;. NOTE: h3cAclBasicSrcIp and h3cAclBasicSrcWild SHOULD be set simultaneously. Name
h3cAclBasicAclNum h3cAclBasicSubitem
Access
not-accessible not-accessible
PDS
Yes Yes
Description
As per MIB As per MIB The valid range of this node is 0 to
Copyright
Page 88 of 132

V0.13 65534 As per MIB As per MIB As per MIB As per MIB As per MIB As to buckbeak, it is not supported As per MIB As per MIB as to buckbeak, it is supported Now support three state: CreateAndGo, Active, Destroy.
h3cAclBasicAct h3cAclBasicSrcIp h3cAclBasicSrcWild h3cAclBasicFragments h3cAclBasicTimeRangeName h3cAclBasicEnable h3cAclBasicCount h3cAclBasicCountClear h3cAclBasicRowStatus h3cAclBasicSubitem
read-create read-create read-create read-create read-create Read-write read-only read-only read-create read-create
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
33.5
h3cAclAdvancedTable
This table is not supported by buckbeak; NOTE: h3cAclAdvancedSrcIp and h3cAclAdvancedSrcWild SHOULD be set simultaneously;h3cAclAdvancedDestIp and h3cAclAdvancedDestWild SHOULD be set simultaneously; Name
h3cAclAdvancedAclNum h3cAclAdvancedSubitem
Access
PDS
Yes Yes
Description
As per MIB As per MIB The valid range of this node is 0 to 65534 As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB As Per mib As per mib As per mib As per mib As Per MIB As Per MIB As to buckbeak, it is supported Now support three state: CreateAndGo, Active, Destroy.
Copyright
h3cAclAdvancedAct h3cAclAdvancedProtocol h3cAclAdvancedEstablish h3cAclAdvancedSrcIp h3cAclAdvancedSrcWild h3cAclAdvancedSrcOp h3cAclAdvancedSrcPort1 h3cAclAdvancedSrcPort2 h3cAclAdvancedDestIp h3cAclAdvancedDestWild h3cAclAdvancedDestOp h3cAclAdvancedDestRange h3cAclAdvancedDestPort1 h3cAclAdvancedDestPort2 h3cAclAdvancedPrecedence h3cAclAdvancedTos h3cAclAdvancedDscp h3cAclAdvancedTimeRangeName h3cAclAdvancedIcmpType h3cAclAdvancedIcmpCode h3cAclAdvancedFragments h3cAclAdvancedLog h3cAclAdvancedEnable h3cAclAdvancedCount h3cAclAdvancedCountClear h3cAclAdvancedRowStatus
read-create read-create read-create read-create read-create read-create Read-create Read-create Read-create read-create read-create read-create read-create read-create read-create read-create read-create read-create Read-create Read-create Read-create Read-create read-only read-only read-create Read-create
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Page 89 of 132

V0.13
33.6
h3cAclIRulefTable
This table is not supported by buckbeak; Name

h3cAclIfAclNum h3cAclIfSubitem
Access
PDS
Yes Yes
Description
As per MIB As per MIB The valid range of this node is 0 to 65534 As Per MIB As Per MIB, it can not be set with h3cAclIfAny together. Only one object is available. As Per MIB it can not be set with h3cAclIfIndex together. Only one object is available. As Per MIB As Per MIB As Per MIB as to buckbeak, it is supported As per mib
h3cAclIfAct h3cAclIfIndex
Yes Yes
h3cAclIfAny
read-create
Yes
h3cAclIfTimeRangeName h3cAclIfEnable h3cAclIfCount h3cAclIfCountClear h3cAclIfRowStatus
read-create read-only read-only read-create read-create
Yes Yes Yes Yes Yes
33.7
h3cAclLinkTable
This table is not supported by buckbeak;

NOTE:h3cAclLinkSrcAny and h3cAclLinkSrcVlanId, h3cAclLinkSrcMac, h3cAclLinkSrcIfIndex SHOULD NOT be set simultaneously;If h3cAclLinkSrcMacWild is supported, then h3cAclLinkSrcMac and h3cAclLinkSrcMacWild SHOULD be set simultaneously;h3cAclLinkDestAny and h3cAclLinkDestVlanId, h3cAclLinkDestMac, h3cAclLinkDestIfIndex SHOULD NOT be set simultaneously;If h3cAclLinkDestMacWild is supported, then h3cAclLinkDestMac and h3cAclLinkDestMacWild SHOULD be set simultaneously.
Name
h3cAclLinkAclNum h3cAclLinkSubitem
Access
PDS
Yes Yes
Description
As per MIB As per MIB The valid range of this node is 0 to 65534 As Per MIB As Per MIB As to buckbeak, it is not supported As to buckbeak, it is not supported As Per MIB As to buckbeak, it is supported As Per MIB Supported, Source Mac wild not support As Per MIB Not supported As Per MIB Destination Mac wild
Copyright
h3cAclLinkAct h3cAclLinkProtocol h3cAclLinkFormatType h3cAclLinkVlanTag h3cAclLinkVlanPri h3cAclLinkSrcVlanId h3cAclLinkSrcMac h3cAclLinkSrcMacWild h3cAclLinkSrcIfIndex h3cAclLinkSrcAny h3cAclLinkDestVlanId h3cAclLinkDestMac h3cAclLinkDestMacWild
read-create read-create read-create read-create read-create read-create read-create read-create read-create read-create read-create read-create read-create
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Page 90 of 132

V0.13 h3cAclLinkDestIfIndex h3cAclLinkDestAny h3cAclLinkTimeRangeName h3cAclLinkEnable h3cAclLinkRowStatus H3cAclLinkTypeCode H3cAclLinkTypeMask H3cAclLinkLsapCode H3cAclLinkLsapMask h3cAclLinkL2LabelRangeOp h3cAclLinkL2LabelRangeBegin h3cAclLinkL2LabelRangeEnd h3cAclLinkL2LabelRangeEnd read-create read-create read-create read-only read-create Read-create Read-create Read-create Read-create read-create read-create read-create read-create Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Not support Not support As Per MIB As Per MIB as per mib Not support Not support Not support Not support Buckbeak 1 does not support this node Buckbeak 1 does not support this node Buckbeak 1 does not support this node Buckbeak 1 does not support this node
33.8
h3cAclUserTable

NOTE: Support or Not Support this table is decided by different products. As to buckbeak, it is supported. h3cAclUserRuleStr and h3cAclUserRuleMask SHOULD be set simultaneously.
Name
h3cAclUserAclNum h3cAclUserSubitem
Access
PDS
Yes Yes
Description
As per MIB As per MIB The valid range of this node is 0 to 65534 As Per MIB Not supported Not supported As Per MIB As Per MIB As Per MIB As Per MIB As Per MIB
h3cAclUserAct h3cAclUserFormatType h3cAclUserVlanTag h3cAclUserRuleStr h3cAclUserRuleMask h3cAclUserTimeRangeName h3cAclUserEnable h3cAclUserRowStatus
33.9
h3cAclActiveTable

NOTE:h3cAclActiveUserAclNum and h3cAclActiveIpAclNum SHOULD NOT be set simultaneously; h3cAclActiveUserAclNum and h3cAclActiveLinkAclNum SHOULD NOT be set simultaneously.This table is not supported by Buckbeak.
Name
h3cAclActiveAclIndex h3cAclActiveIfIndex H3cAclActiveVlanID
Access
Read-create read-create Read-create
PDS
Yes Yes Yes
Description
Copyright
Page 91 of 132

V0.13 h3cAclActiveDirection h3cAclActiveUserAclNum h3cAclActiveUserSubitem h3cAclActiveIpAclNum h3cAclActiveIpSubitem h3cAclActiveLinkAclNum h3cAclActiveLinkSubitem h3cAclActiveRuntime h3cAclActiveRowStatus read-create read-create read-create read-create read-create read-create read-create read-only read-create Yes Yes Yes Yes Yes Yes Yes Yes Yes As per MIB supported supported As per MIB The valid range of this node is 0 to 65534 As per MIB The valid range of this node is 0 to 65534 As per MIB as per mib
It is not supported by buckbeak.
33.10
h3cAclIDSTable
Name h3cAclIDSName h3cAclIDSSrcMac h3cAclIDSDestMac h3cAclIDSSrcIp h3cAclIDSSrcWild h3cAclIDSDestIp h3cAclIDSDestWild h3cAclIDSSrcPort h3cAclIDSDestPort h3cAclIDSProtocol h3cAclIDSDenyTime h3cAclIDSAct h3cAclIDSRowStatus
Access
not-accessi ble read-create read-create read-create read-create read-create read-create read-create read-create read-create read-create read-create read-create
PDS
No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Description
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
34. LCS MIBs

The buckbeak products do not support licensing mib.
35. Software version mib

Huawei.h3c.h3cSystem.h3cSoftwareersion is supported.
36. 802.1x MIBs

36.1 36.1.1 Name
dot1xPaeSystemAuthControl
IEEE8021-PAE-MIB Scalar Objects Access

read-write
PDS
Yes
Description
As per MIB
Copyright
Page 92 of 132

V0.13
36.1.2 Name
dot1xPaePortTable Access
not-accessible read-only read-only read-write
PDS
Yes Yes Yes No
Description
As per MIB As per MIB As per MIB Read operation is supported, Set operation is not supported Read operation is supported, Set operation is not supported
dot1xPaePortNumber dot1xPaePortProtocolVersion dot1xPaePortCapabilities dot1xPaePortInitialize
read-write dot1xPaePortReauthenticate
No
36.1.3 Name
dot1xAuthConfigTable Access
read-only read-only read-write read-only read-only read-write read-write read-write read-write read-write read-write read-write read-write read-write
PDS
No No Yes No Yes Yes No No no no no no yes yes
Description
not supported, Always return initialize(1). not supported, Always return request(1) set operation is not supported. As per mib As per MIB As per MIB read always return 0 When read, return 0 read always return 0 When read, return 0 read always return 0 When read, return 0 read always return 0 When read, return 0 read always return 0 When read, return 0 read always return 0 When read, return 0 set op is not supported. set op is not supported.
dot1xAuthPaeState dot1xAuthBackendAuthState dot1xAuthAdminControlledDirections dot1xAuthOperControlledDirections dot1xAuthAuthControlledPortStatus dot1xAuthAuthControlledPortControl dot1xAuthQuietPeriod dot1xAuthTxPeriod dot1xAuthSuppTimeout dot1xAuthServerTimeout dot1xAuthMaxReq dot1xAuthReAuthPeriod dot1xAuthReAuthEnabled dot1xAuthKeyTxEnabled
36.1.4
dot1xAuthStatsTablenot support
this table is not supported. Name

dot1xAuthEapolFramesRx dot1xAuthEapolFramesTx dot1xAuthEapolStartFramesRx dot1xAuthEapolLogoffFramesRx dot1xAuthEapolRespIdFramesRx dot1xAuthEapolRespFramesRx dot1xAuthEapolReqIdFramesTx dot1xAuthEapolReqFramesTx dot1xAuthInvalidEapolFramesRx
Access
read-only read-only read-only read-only read-only read-only read-only read-only read-only
PDS
no no no no no no no no no
Description
as per MIB as per MIB as per MIB as per MIB as per MIB as per MIB as per MIB as per MIB as per MIB
Copyright
Page 93 of 132

V0.13 dot1xAuthEapLengthErrorFramesRx dot1xAuthLastEapolFrameVersion dot1xAuthLastEapolFrameSource read-only read-only read-only no no no as per MIB as per MIB as per MIB
36.1.5
dot1xAuthSessionStatsTable(not support)
This mib is not supported. Name

dot1xAuthSessionOctetsRx dot1xAuthSessionOctetsTx dot1xAuthSessionFramesRx dot1xAuthSessionFramesTx dot1xAuthSessionId dot1xAuthSessionAuthenticMethod dot1xAuthSessionTime dot1xAuthSessionTerminateCause dot1xAuthSessionUserName
Access
read-only read-only read-only read-only read-only read-only read-only read-only read-only
PDS
Description
as per MIB as per MIB as per MIB as per MIB as per MIB as per MIB as per MIB as per MIB as per MIB
The above table is not supported. 36.2 36.2.1 Name

hwdot1xAuthQuietPeriod hwdot1xAuthTxPeriod hwdot1xAuthSuppTimeout hwdot1xAuthServerTimeout hwdot1xAuthMaxReq hwdot1xAuthReAuthPeriod
A3COM-HUAWEI-8021PAE-MIB Scalar Objects Access

read-write read-write read-write read-write read-write read-write
PDS
yes yes yes yes yes No
Description
as per MIB as per MIB as per MIB as per MIB as per MIB Not support
36.2.2 Name
hwdot1xAuthConfigExtTable Access
read-write read-write read-write read-only read-write
PDS
yes yes yes no no
Description
as per MIB as per MIB as per MIB as per MIB as per MIB
hwdot1xpaeportAuthAdminStatus hwdot1xpaeportControlledType hwdot1xpaeportMaxUserNum hwdot1xpaeportUserNumNow h3cdot1xpaeportClearStatistics
36.3
A3COM0458-PORT-SECURITY(not support)
This mib is not supported by buckbeak products.
37. FTM mib

This mib Is used to products which support XRN. when change unit ID, the time restriction are as follows: Case 1:
Copyright
Page 94 of 132

V0.13
8 units in fabric with auto numbering by default, to change them to manual numbering one by one, the total time is 150 seconds. For the first 5 units, it takes about 15 seconds for each unit to finish the unit ID change; for the last 3 units, it takes about 30 seconds for each unit to do it; In this case, there is no master unit change and no unit ID conflict; Case 2: 8 units in fabric with master change, for example, to change unit 1 to unit 8, it takes about 120 seconds; Case 3: 8 units in fabric without master change but with unit ID conflict, for example, to change unit 2 to unit 3, it takes about 90 seconds; For 3ND, only case 1 is used, so we think that it may set the overtime to be 30 seconds with one packet one unit ID change operation to fix this problem;
37.1
Scalar Objects
Name
h3cFtmAuthMode h3cFtmAuthValue h3cFtmFabricVlanI D h3cFtmFabricType
Access
read-write read-write Read-write read-only
PDS
Yes Yes yes NO
Description
As per mib As per mib As per mib As per MIB
37.2
H3cFtmUnitTable
A table of informations of XRN-Fabric Unit.
Name
h3cFtmIndex h3cFtmUnitID h3cFtmUnitNa me h3cFtmUnitRol e h3cFtmNumber Mode
Access
not-accessi ble read-write read-write read-only read-only
PDS
No No Yes NO NO
Description
This is the entPhysicalIndex for Buckbeak . As per MIB As per MIB As per MIB Numbering Mode of unit in XRN-Fabric. If the unit ID is assigned by the auto numbering algorithm, the numbering mode will be automatic numbering; if the unit ID (h3cFtmUnitID) is assigned by the user, the numbering mode will be manual numbering; if h3cFtmUnitID is set to be zero, the numbering mode will become automatic numbering. For buckbeak the default value is 0.
Copyright
Page 95 of 132

V0.13
37.3
Notifications
Name
h3cFtmUnitIDChange h3cFtmUnitNameCha nge
Access
NA NA
PDS
No No
Description
38. Voice vlan mib

This mib is supported by switch only. This mib need to be confirmed by products whether supported or not. 38.1 Scalar objects
Name
h3cVoiceVlanEnabledId h3cVoiceVlanPortEnableList
Access
PDS
Yes Yes
Description
As per MIB The port list indicates which ports are voice vlan enabled ports. Each port is represented, in the form of the most significant bit of the first octet representing the port 8, the next most significant bit representing the port 7, the least significant bit of the first octet representing the port 1, the most significant bit of the second octet representing the port 16, the next most significant bit representing the port 15, the least significant bit of the second octet representing the port 9. The rest may be deduced by analogy. The ports are voice vlan enabled ports for those ports which have one in its corresponding bit, not otherwise. As per MIB As per MIB As per MIB
h3cVoiceVlanAgingTime h3cVoiceVlanConfigState h3cVoiceVlanSecurityState
Yes Yes Yes
38.2
h3cvoiceVlanOuiTable
Name
h3cVoiceVlanOuiAddress
Access
read-only
PDS
Yes
Description
As per MIB
Copyright
Page 96 of 132

V0.13 h3cVoiceVlanOuiMask h3cVoiceVlanOuiDescription h3cVoiceVlanOuiRowStatus read-write read-write read-create Yes Yes No As per MIB As per MIB As per MIB
38.3
h3cvoiceVlanPortTable(This table is for buckbeak Version 3.3.2pxx.)
Name
h3cVoiceVlanPortifIndex h3cVoiceVlanPortMode h3cVoiceVlanPortLegacy h3cVoiceVlanPortQosTrust
Access
not-accessi ble read-write read-write read-write
PDS
Yes Yes Current Current
Description
39. Poe mib

39.1 petthNotifications
Name
pethPsePortOnOffNotification pethMainPowerUsageOnNotifica tion pethMainPowerUsageOffNotifica tion
Access
NOTIFICATION-TYP E NOTIFICATION-TYP E NOTIFICATION-TYP E
PDS
No No No
Description
As per Mib As per Mib As per Mib
39.2
39.2.1
pethObjects pethPsePortTable
Name
pethPsePortGroupIndex pethPsePortIndex pethPsePortAdminEnable pethPsePortPowerPairsControlA bility
Access
Not-accessible Not-accessible Read-write Read-only
PDS
no no no no
Description
As per mib As per mib As per mib
Spare mode is not supported on the switch now.
pethPsePortPairs pethPsePortDetectionStatus pethPsePortPowerPriority pethPsePortMPSAbsentCounter pethPsePortType pethPsePortPowerClassification s pethPsePortInvalidSignatureCou nter pethPsePortDEniedCounter pethPsePortOverLoadCounter
Read-write Read-only Read-write Read-only Read-write Read-only Read-only Read-only Read-only
As per mib As per mib As per mib As per mib As per mib As per mib As per mib As per mib As per mib
Copyright
Page 97 of 132

V0.13 pethPsePortShortCounter 39.2.2 Name pethMainPseGroupIndex pethMainPsePower pethMainPseOperStatus pethMainPseConsumptionPower pethMainPseUsageThreshold 39.2.3 Name pethNotificationControlGroupIn dex pethNotificationControlEnable Read-only no As per mib
pethMainPseObjects
Access Not-accessible Read-only Read-only Read-only Read-write PD S No No No No No Description As per Mib As per Mib As per Mib As per Mib As per Mib
pethNotificationControl
Access Not-accessible Read-write PD S No No Description As per Mib As per Mib
39.3
39.3.1
pethConformance pethComplicance
Access Not-accessible PDS No Description As per Mib
Name pethCompliance
39.3.2 Name
pethGroups
Access Not-accessible Not-accessible Not-accessible Not-accessible Not-accessible PD S No No No No No Description As per Mib As per Mib As per Mib As per Mib As per Mib
pethPsePortGroup pethMainPseGroup pethNotificationControlGroup pethPsePortNotificationGroup pethMainPowerNotificationGrou p
40. POE ext mib

40.1
Name H3cPsePortFaultDEscription H3cPsePortPeakPower h3cPsePortAveragePower H3cPsePortCurrentPower H3cPsePortPowerLimit
h3cPsePortTable
Access Read-write Read-write Read-write Read-only Read-write PD S No No No No No Description As per Mib As per Mib As per Mib As per Mib As per Mib
Copyright
Page 98 of 132

V0.13
40.2
Name
h3cMainPseTable
Access Read-write Read-write Read-write Read-only PD S No No No No Description only support read operation As per Mib As per Mib As per Mib
H3cMainPsePowerlimit H3cMainPseAveragePower H3cMainPsePeakPower H3cMainGuaranteedPowerRema ining
40.3
Name
Scalar objects
Access Read-write PD S No Description Now only support read-only
H3cPseAutoDetectActive
41. A3COM-QOS-PROFILE-MIB DEFINITIONS

the mib is being test. 41.1 41.1.1 QosProfObjects QosProf h3cQoSProfTable
41.1.1.1
The row can not be modified, Reset the row must undo the row first; Create the row at least require: h3cQoSProfIndex, h3cQoSProfName, h3cQoSProfRowStatus
Name h3cQoSProfIndex h3cQoSProfName h3cQoSProfActionNumber h3cQoSProfRowStatus Access not-accessible Read-Create Read-only Read-Create PD S No No No No Description As per Mib As per Mib As per Mib As per Mib
41.1.2
QosActions h3cQoSTrafficLimitTable
41.1.2.1
Note:The row can not be modified, Reset the row must undo the row first; Create the row at least repuire: h3cQoSTrafLmtProfIndex, h3cQoSTrafLmtDirection, h3cQoSTrafLmtTargetRateKbps, h3cQoSTrafLmtRowStatus, and choose one group of AclNum and AclRule, for example:
h3cQoSTrafLmtActionIndex,
(h3cQoSTrafLmtUserAclNum,h3cQoSTrafLmtUserAclRule), (h3cQoSTrafLmtIpAclNum,h3cQoSTrafLmtIpAclRule), (h3cQoSTrafLmtLinkAclNum,h3cQoSTrafLmtLinkAclRule))

Name Access PD S Description
Copyright
Page 99 of 132

V0.13 h3cQoSTrafLmtProfIndex h3cQoSTrafLmtActionIndex h3cQoSTrafLmtDirection h3cQoSTrafLmtUserAclNum h3cQoSTrafLmtUserAclRule h3cQoSTrafLmtIpAclNum h3cQoSTrafLmtIpAclRule h3cQoSTrafLmtLinkAclNum h3cQoSTrafLmtLinkAclRule h3cQoSTrafLmtTargetRateMbps not-accessibl e not-accessibl e Read-create Read-create Read-create Read-create Read-create Read-create Read-create Read-create No No No No No No No No No No As per Mib As per Mib As per Mib 0 is invalid value As per Mib As per Mib 65535 is invalid value 0 is invlaid value 65535 is invalid value As per Mib. This Object not supported by buckbeak 1.0. As per Mib As per Mib. This Object not supported by buckbeak 1.0. As per Mib As per Mib. This Object not supported by buckbeak 1.0. As per Mib. This Object not supported by buckbeak 1.0. As per Mib. This Object not supported by buckbeak 1.0. As per Mib. This Object not supported by buckbeak 1.0. As per Mib. This Object not supported by buckbeak 1.0. As per Mib As per Mib As per Mib. This Object not supported by buckbeak 1.0. As per Mib The remarked COS value of conformed flow. COS 255 is used as default value and for get/get-next operation of this node. If the user does not set
Copyright
h3cQoSTrafLmtTargetRateKbps h3cQoSTrafLmtPeakRate
Read-create Read-create
No No
h3cQoSTrafLmtCIR h3cQoSTrafLmtCBS
Read-create Read-create
No No
h3cQoSTrafLmtEBS
Read-create
No
h3cQoSTrafLmtPIR
Read-create
No
h3cQoSTrafLmtConformLocalPre
Read-create
No
h3cQoSTrafLmtConformActionType
Read-create
No
h3cQoSTrafLmtExceedActionType h3cQoSTrafLmtExceedDscp h3cQoSTrafLmtExceedCos
Read-create Read-create Read-create
No No No
h3cQoSTrafLmtRowStatus h3cQoSTrafLmtConformCos
Read-create read-create
No Yes
Page 100 of 132

V0.13 conforming action as remarking COS, then value 255 is returned for get/get-next operation. This Object not supported by buckbeak 1.0. The remarked DSCP value of conformed flow. DSCP 255 is used as default value and for get/get-next operation of this node. If the user does not set conforming action as remarking DSCP, then value 255 is returned for get/get-next operation. This Object not supported by buckbeak 1.0.
h3cQoSTrafLmtConformDscp
read-create
Yes
41.1.2.2
h3cQoSTrafficFilterTable
Note:The row can not be modified, Reset the row must undo the row first, Create the row at least require: h3cQoSTrafFilterProfIndex, h3cQoSTrafFilterActionIndex, h3cQoSTrafFilterDirection, h3cQoSTrafFilterRowStatus, and choose one group of AclNum and AclRule, for example:
(h3cQoSTrafFilterIpAclNum, h3cQoSTrafFilterIpAclRule), (h3cQoSTrafFilterLinkAclNum, h3cQoSTrafFilterLinkAclRule), (h3cQoSTrafFilterUserAclNum, h3cQoSTrafFilterUserAclRule),

Name h3cQoSTrafFilterProfIndex h3cQoSTrafFilterActionIndex h3cQoSTrafFilterDirection h3cQoSTrafFilterUserAclNum h3cQoSTrafFilterUserAclRule h3cQoSTrafFilterIpAclNum h3cQoSTrafFilterIpAclRule h3cQoSTrafFilterLinkAclNum h3cQoSTrafFilterLinkAclRule Access not-accessibl e not-accessibl e Read-create Read-create Read-create Read-create Read-create Read-create Read-create PD S No No No No No No No No No Description As per Mib As per Mib As per Mib 0 is invalid value 65535 is invalid value 0 is invalid value 65535 is invalid value 0 is invalid value 65535 is invalid value
Copyright
Page 101 of 132

V0.13 h3cQoSTrafFilterRowStatus Read-create No As per Mib
41.1.3
QosProfPortMapping h3cQoSProfPortMappingTable
Access not-accessibl e not-accessibl e Read-create PDS No No No Description As per Mib As per Mib As per Mib
41.1.3.1
Name h3cQoSProfPortMappingIfIndex h3cQoSProfPortMappingProfIndex h3cQoSProfPortMappingRowStatus
41.1.3.2
Name
h3cQoSProfPortMappingModeTable
Access not-accessible Read-write PD S No No Description As per Mib As per Mib The default value is user-based(1).
h3cQoSProfPortMappingModeIfInde x h3cQoSProfPortMappingMode
41.1.3.3
Name
h3cQoSProfDynPortMappingTable
Access not-accessible not-accessible Read-only Read-only Read-only Read-only PD S No No No No No No Description As per Mib As per Mib As per Mib As per Mib As per Mib As per Mib
h3cQoSProfDynPortMappingIfIndex h3cQoSProfDynPortMappingUserSrc MAC h3cQoSProfDynPortMappingUserNa me h3cQoSProfDynPortMappingUserIP Addr h3cQoSProfDynPortMappingUserVL ANID h3cQoSProfDynPortMappingUserPr ofName
41.2
h3cQoSProfPortMappingTraps
Access notified PDS No Description As per Mib
Name h3cQoSProfPortMappingError
42. 3COM-HUAWEI-UI-MAN-MIB
This MIB is used to manage user interfaces.
41.1 Scalar Objects

This MIB has no Scalar Object. 41.2 h3cUIMgtBasicGroup This group now only has h3cVtyAccTable
Copyright
Page 102 of 132

V0.13
Name
h3cVtyAccUserIn dex h3cVtyAccConn way h3cVtyAccAclNu m
Access
not-acces sible not-acces sible read-write
PDS
NO Yes Yes
Description
As per MIB As per MIB Now only support read-only.
43. A3COM-HUAWEI-ENTRELATION-MIB
43.1 h3cEntRelationTable
Name h3cEntityIndex h3cEntRelationType h3cRelatedEntityIndex Access not-accessible not-accessible read-only PDS No No No Description As per MIB As per MIB As per MIB
44. SNMP-REPEATER-MIB RFC2108(not support)

The buckbeak products do not support this mib.
45. A3COM-HUAWEI-IP-BROADCAST-MIB
This MIB is not supportted by buckbeak. 45.1 h3cIpScalarGroup
Name h3cIpForward Broadcast h3cIpReceive Broadcast
Access
read-write
PDS
YES
Description
The value of this node refer whether a device forwards direct broadcast datagrams or not The value of this node refer whether a device receive direct broadcast datagrams or not.
read-write
Yes
46. A3COM-HUAWEI-VRRP-EXT-MIB
This mib is not supportted by buckbeak. This MIB is used to manage user interfaces.
46.1 Scalar Objects

This MIB has no Scalar Object. 46.2 h3cVrrpExtTable of h3cVrrpExtMibObject
Name h3cVrrpExtTrackInterface
Access not-accessibl
PDS No
Description As per MIB

Copyright
Page 103 of 132

V0.13 e read-create read-create
h3cVrrpExtPriorityReduc e h3cVrrpExtRowStatus
Yes Yes
47. A3COM-HUAWEI-PROTOCOL-PRIORITY-MIB
This MIB is not supported by buckbeak. The MIB is a priority configuration of protocol, includes type of protocol,type of priority,value of priority and RowStatus. The priority of protocol may be changed by CLI, SNMP or other ways defined as the MIB.
47.1 h3cProtocolPriorityTable
Name h3cPPriProtocolType h3cPPriPriorityType h3cPPriPriorityValue h3cPPriRowStatus
Access not-accessible read-create read-create read-create
PDS Yes Yes Yes Yes
Description Type of protocol. Type of priority. When setting and modifing,h3cPPriPriorityType and h3cPPriPriorityValue must change at the same time. Value of priority. RowStatus, Now support three states:CreateAndGo, Active, Destroy.
48.
A3COM- HUAWEI-LswMSTP-MIB
This mib is used for switch only.Only use for products of R002
48.1 Scalar objects
Name hwdot1sStpStatus hwdot1sStpForceVersion hwdot1sStpDiameter hwdot1sMstBridgeMaxHops hwdot1sMstMasterBridgeID hwdot1sMstMasterPathCost hwdot1sMstBpduGuard hwdot1sMstAdminFormatSelect or hwdot1sMstAdminRegionName hwdot1sMstAdminRevisionLev el hwdot1sMstOperFormatSelector hwdot1sMstOperRegionName hwdot1sMstOperRevisionLevel hwdot1sMstOperConfigDigest
Access
read-write read-write read-write read-write read-only read-only read-write read-write read-write read-write read-only read-only read-only read-only
PDS
Yes Yes Yes Yes No No Yes No No No No Yes Yes No
Description
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
Copyright
Page 104 of 132

V0.13
hwdot1sMstRegionConfActive hwdot1sMstDefaultVlanAllo hwdot1sMstDefaultRegionNam e
No No No
48.2
hwdot1sVIDAllocationTable
Name hwdot1sMstVID hwdot1sAdminMstID hwdot1sOperMstID
Access
read-only read-write read-only
PDS
Yes No Yes
Description
As per MIB need confirm by product As per MIB
48.3
hwdot1sInstanceTable
Name hwdot1sInstanceID hwdot1sMstiBridgeID hwdot1sMstiBridgePriority hwdot1sMstiDesignedRoot hwdot1sMstiRootPathCost hwdot1sMstiRootPort hwdot1sMstiRootType hwdot1sMstiRemainingHops hwdot1sMstiAdminMappedVla nListLow hwdot1sMstiAdminMappedVla nListHigh hwdot1sMstiOperMappedVlanL istLow hwdot1sMstiOperMappedVlanL istHigh
Access
read-only read-only read-write read-only read-only read-only read-write read-only read-only read-only read-only read-only
PDS
Yes No Yes No No No Yes No No No Yes Yes
Description
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
48.4
hwdot1sPortTable
Name hwdot1sMstiPortIndex hwdot1sMstiState hwdot1sMstiPortPriority hwdot1sMstiPathCost hwdot1sMstiDesignatedRoot hwdot1sMstiDesignatedCost hwdot1sMstiDesignatedBridge hwdot1sMstiDesignatedPort
Access
read-only read-only read-write read-write read-only read-only read-only read-only
PDS
No No Yes Yes No No No No
Description
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
Copyright
Page 105 of 132

V0.13
hwdot1sMstiMasterBridgeID hwdot1sMstiMasterPortCost hwdot1sMstiStpPortEdgeport hwdot1sMstiStpPortPointToPoi nt hwdot1sMstiStpMcheck hwdot1sMstiStpTransLimit hwdot1sMstiStpRXStpBPDU hwdot1sMstiStpTXStpBPDU hwdot1sMstiStpRXTCNBPDU hwdot1sMstiStpTXTCNBPDU hwdot1sMstiStpRXRSTPBPDU hwdot1sMstiStpTXRSTPBPDU hwdot1sMstiStpRXMSTPBPD U hwdot1sMstiStpTXMSTPBPDU hwdot1sMstiStpClearStatistics hwdot1sMstiStpDefaultPortCost hwdot1sMstiStpStatus hwdot1sMstiPortRootGuard hwdot1sMstiPortLoopGuard
read-only read-only read-write read-write read-write read-write read-only read-only read-only read-only read-only read-only read-only read-only read-write read-write read-write read-write read-write
No No Yes Yes No Yes No No No No No No No No No No Yes Yes Yes
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
48.5
Traps of hwMstpEventsV2
Name hwPortMstiStateForwarding hwPortMstiStateDiscarding hwBridgeLostRootPrimary hwPortMstiRootGuarded hwPortMstiBpduGuarded hwPortMstiLoopGuarded
Access
NA NA NA NA NA NA
PDS
No No No No No No
Description
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
49.
49.1
A3COM-HUAWEI-RADIUS-MIB
Scalar Objects
This MIB has no Scalar Object.
49.2
h3cRdInfoTable
Name h3cRdGroupName h3cRdPrimAuthIp h3cRdPrimUdpPor t h3cRdPrimState
Access
PD S
Yes Yes Yes No
Description
The name of the RADIUS group. The IP address of primary RADIUS server. The UDP port of primary RADIUS server. The state of the primary RADIUS
Copyright
Page 106 of 132

V0.13 server. The IP address of secondary RADIUS server. The UDP port of secondary RADIUS server. The state of the secondary RADIUS server. The secret shared between the RADIUS client and RADIUS server. The number of attempts the client will make when trying to send requests to a server before it will consider the attempt failed. The timeout value the client will use when sending requests to a server.
h3cRdSecAuthIp h3cRdSecUdpPort h3cRdSecState h3cRdKey h3cRdRetry
Yes Yes No Yes Yes
h3cRdTimeout
read-only
Yes
50. A3COM-HUAWEI-SYSLOG-MIB
A Syslog MIB, includes Syslog management. All the configuration of the Syslog can be managed by the Syslog Mib. 50.1 scalar objects
Name
h3cSyslogState h3cSyslogMaxLoghost h3cSyslogMaxChannel
Access
read-write read-only read-only
PDS
No No No
Description
The state of Syslog: enable Syslog or disable Syslog The object shows the maximum number of rows in h3cLoghostTable The object shows the maximum number in h3cSyslogChannelTable. (The maximum number of channel is 10) The maximum number of messages that can be stored in logbuffer The maximum number of messages that can be stored in trapbuffer The channel number of console (The valid value of channel number in syslog mib is from 1 to h3cSyslogMaxChannel, while that in command line is from 0 to 9) The channel number of monitor (The valid value of channel number in syslog mib is from 1 to h3cSyslogMaxChannel, while that in command line is from 0 to 9) The channel number of snmp (The valid value of channel number in syslog mib is from 1 to h3cSyslogMaxChannel, while that in command line is from 0 to 9)
h3cSyslogMaxLogbuffersize h3cSyslogMaxtrapbuffersize
read-only read-only
No No
h3cSyslogConsoleChannel
read-write
No
h3cSyslogMonitorChannel
read-write
No
h3cSyslogSnmpChannel
read-write
No
Copyright
Page 107 of 132

V0.13
h3cSyslogLogbufferChannel
read-write
No
h3cSyslogLogbufferSize
read-write
No
h3cSyslogTrapbufferChannel
read-write
No
h3cSyslogTrapbufferSize h3cSyslogLoghostSourceInterface
No No
h3cSyslogLoghostTimestampType
read-write
No
h3cSyslogLogTimestampType
read-write
No
h3cSyslogTrapTimestampType
read-write
No
h3cSyslogDebugTimestampType
read-write
No
The channel number of Logbuffer (The valid value of channel number in syslog mib is from 1 to h3cSyslogMaxChannel, while that in command line is from 0 to 9) The number of log messages that can be stored in Logbuffer The channel number of Trapbuffer (The valid value of channel number in syslog mib is from 1 to h3cSyslogMaxChannel, while that in command line is from 0 to 9) The number of trap messages that can be stored in Trapbuffer The source interface which sends message to Loghost. All Loghosts use the same SourceInterface. Time stamp type of message sent to Loghost. The valid value of this node: date none datewithoutyear Time stamp type of log message. The valid value of this node: date boot none Time stamp type of trap message. The valid value of this node: date boot none Time stamp type of debug message. The valid value of this node: date boot none
50.2 h3cSyslogLogbufferTable
Name
h3cLogbufferIndex h3cLogbufferCurrentMessages h3cLogbufferOverwrittenMessages h3cLogbufferDroppedmessages
Access
not-accessible read-only read-only read-only
PDS
No No No No
Description
The index of h3cSyslogLogbufferTable. In fabric, the value of this index is unit id, otherwise the value is 1 The number of log messages stored in Logbuffer The number of log messages overwritten in Logbuffer The number of log messages dropped in Logbuffer
Copyright
Page 108 of 132

V0.13
50.3 h3cSyslogTrapbufferTable
Name
h3cTrapbufferIndex h3cTrapbufferCurrentMessages h3cTrapbufferOverwrittenMessages h3cTrapbufferDroppedmessages 50.4 h3cSyslogLoghostTable
Access
not-accessible read-only read-only read-only
PDS
No No No No
Description
The index of h3cSyslogTrapbufferTable. In fabric, the value of this index is unit id, otherwise the value is 1 The number of trap messages stored in Trapbuffer The number of trap messages overwritten in Trapbuffer The number of trap messages dropped in Trapbuffer
Name
h3cSyslogLoghostIndex h3cSyslogLoghostChannel h3cSyslogLoghostIpaddressType h3cSyslogLoghostIpaddress
Access
not-accessible read-create read-create read-create
PDS
No No No No
Description
As per MIB The valid value of this node: 1~h3cSyslogMaxLoghost The channel number of loghost The valid value of this node: 1~h3cSyslogMaxChannel The ip address type (ipv4 or ipv6) of Loghost The valid value is ipv4 The ip address of Loghost As per MIB The valid value of this node: local0(0), local1(1), local2(2), local3(3), local4(4), local5(5), local6(6), local7(7) The language of the message sent to the Loghost The status of this table entry
h3cSyslogLoghostFacility
read-create
No
h3cSyslogLoghostLanguage h3cSyslogLoghostOperateRowStatus
No No
50.5 h3cSyslogChannelTable
Name
h3cSyslogChannelIndex
Access
not-accessible
PDS
No
Description
The index of h3cSyslogChannelTable The valid value of this node: 1~h3cSyslogMaxChannel The name of channel The length of the channel name is from 1 to 30 The channel name must be different from each other.
Copyright
h3cSyslogChannelName
read-write
No
Page 109 of 132

V0.13
50.6 h3cSyslogModuleTable This table is not available now and will be realized in the future
Name
h3cSyslogModuleIndex h3cSyslogModuleName
Access
not-accessible read-only
PDS
No No
Description
The index of h3cSyslogModuletable The name of module The length of the module name is from 1 to 20
50.7 h3cSyslogLogTable This table is not available now and will be realized in the future
Name
h3cSyslogLogChannelIndex h3cSyslogLogState
Access
not-accessible read-create
PDS
No No
Description
The index of channel The valid value of this node: 1~h3cSyslogMaxChannel The switch state of log The level of log message The valid value of this node: emergency(1), alert(2), critical(3), error(4), warning(5), notice(6), informational(7), debug(8) The status of this table entry
h3cSyslogLogLevel
read-create
No
h3cSyslogLogRowStatus
read-create
No
50.8 h3cSyslogTrapTable This table is not available now and will be realized in the future
Name
h3cSyslogTrapChannelIndex h3cSyslogTrapState
Access
PDS
No No
Description
The index of channel The valid value of this node: 1~h3cSyslogMaxChannel The switch state of trap The level of trap message The valid value of this node: emergency(1), alert(2), critical(3), error(4), warning(5), notice(6), informational(7), debug(8) The status of this table entry
h3cSyslogTrapLevel
read-create
No
h3cSyslogTrapRowStatus
read-create
No
50.9 h3cSyslogDebugTable This table is not available now and will be realized in the future
Page 110 of 132

V0.13
Name
h3cSyslogDebugChannelIndex h3cSyslogDebugState
Access
PDS
No No
Description
The index of channel The valid value of this node: 1~h3cSyslogMaxChannel The switch state of debug The level of debug message The valid value of this node: emergency(1), alert(2), critical(3), error(4), warning(5), notice(6), informational(7), debug(8) The status of this table entry
h3cSyslogDebugLevel
read-create
No
h3cSyslogDebugRowStatus
read-create
No
51. A3COM-HUAWEI-DOMAIN-MIB
The MIB module is used for managing domain.
51.1 Scalar Objects
Name
h3cDomainDefault 51.2 h3cDomainInfoTable Name h3cDomainName h3cDomainState h3cDomainMaxAccessNum
Access
read-write
PDS
Current
Description
As per MIB
Access not-accessible read-create read-create
PDS No Current Current
Description As per MIB As per MIB The range is from 1 to 4120 The vlan assignment mode. The mode SHOULD be the same as the mode of corresponding server. 1 (integer) - Integer Vlan assignment mode. 2 (string) - String Vlan assignment mode. 3 (vlanlist) - VLAN-List Vlan assignment mode. The default value is integer. The 3rd mode is to support auto-vlan feature, which is started to support on the new software version (V3.3.2pxx). As per MIB As per MIB As per MIB As per MIB
Copyright
h3cDomainVlanAssignMode
read-create
Current
h3cDomainIdleCutEnable h3cDomainIdleCutMaxTime h3cDomainIdleCutMinFlow h3cDomainMessengerEnable
read-create read-create read-create read-create
Current Current Current Current
Page 111 of 132

V0.13
h3cDomainMessengerLimitTime h3cDomainMessengerSpanTime h3cDomainSelfServiceEnable h3cDomainSelfServiceURL h3cDomainAccFailureAction h3cDomainRowStatus 51.3 h3cDomainSchemeTable
read-create read-create read-create read-create read-create read-create
Current Current Current Current Current Current
As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB
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. 2) when change a row, the following objects must be specified.
h3cDomainSchemeMode h3cDomainSchemeAAAType h3cDomainSchemeAAAName h3cDomainSchemeAccessMode: Only support default, other values is invalid.if the item is not specified, the default value is default.
3) when create a new row, the following object must be specified,
h3cDomainSchemeMode h3cDomainSchemeRowStatus h3cDomainSchemeAAAType: h3cDomainSchemeAAAName h3cDomainSchemeAccessMode: Only support default, other values is invalid.if the item is not specified, the default value is default.
4) when a domain was destroyed, a row for accounting, a row for authentication, a row for authorization must be reserved. 5) Limitations
Limitation 1: The maximum row number of h3cDomainSchemeTable for each domain is 6. The maximum row number that have the same h3cDomainSchemeAAAType value is 2, and that two rows have the same h3cDomainSchemeAAAType and h3cDomainSchemeMode value is not allowed.
Limitation 2: The combinations of the AAAType and SchemeMode in the table below have been supported.The values set do not match the rules, return failure. The value TURE in the table below corresponds to the combination of the AAAType and SchemeMode supported. AAAType SchemeMode Radius Hwtacacs Local TRUE TRUE TRUE TRUE TRUE TRUE Authentication Authorization Accounting
Copyright
Page 112 of 132

V0.13
None Radius+Local Hwtacacs+Local
TRUE TRUE TRUE
TRUE
TRUE
Limitation 3: It is prohibited to modify the value of h3cDomainSchemeAAAType of a row existed.The attempt of such modification will be a failure.
Name
h3cDomainSchemeIndex h3cDomainSchemeMode h3cDomainAuthSchemeName h3cDomainAcctSchemeName h3cDomainSchemeRowStatus h3cDomainSchemeAAAType
Access
not-accessible read-create read-create read-create read-create read-create
PDS
No Current Current Current Current Current
Description
As per MIB As per MIB Not supported and the value will be ignored Not supported and the value will be ignored As per MIB Service Type of the server If h3cDomainSchemeMode is radius or tacacs then the value of h3cDomainSchemeAAAName must be valid scheme name, if the h3cDomainSchemeMode is none or local, the value of h3cDomainSchemeAAAName will be a null string. The access mode of the domain scheme . Only support default
h3cDomainSchemeAAAName
read-create
Current
h3cDomainSchemeAccessMode
read-create
Current
51.4 h3cDomainIpPoolTable (This table is not supported) Name

h3cDomainIpPoolNum h3cDomainIpPoolLowIpAddrType h3cDomainIpPoolLowIpAddr h3cDomainIpPoolLen h3cDomainIpPoolRowStatus
Access
not-accessible read-create read-create read-create read-create
PDS
No Current Current Current Current
Description
Not supported Not supported Not supported Not supported Not supported
52. A3COM-HUAWEI-LPBKDT-MIB
52.1 h3cLpbkdtObjects Name Access PDS Description
Copyright
Page 113 of 132

V0.13
accessible-fornotify
h3cLpbkdtVlanID
No
The ID of VLAN
52.2 Supported Private Traps This section contains a list of the traps defined in the private MIB (defined by enterprise).
Trap h3cLpbkdtTrapLoopbacke d h3cLpbkdtTrapRecovered h3cLpbkdtTrapPerVlanLoo pbacked h3cLpbkdtTrapPerVlanRec overed MIB A3COM-HUAWEI-LPBKDT-MIB A3COM-HUAWEI-LPBKDT-MIB A3COM-HUAWEI-LPBKDT-MIB Comments Not support Not support Trap message is generated when the interface is looped in the VLAN. Not support
A3COM-HUAWEI-LPBKDT-MIB
53. A3COM-HUAWEI-LLDP-EXT-MIB
Extended LLDP management MIB is complementary MIB with IEEE802.1ab standard MIB for implementation. And this private extended MIB is designed to fulfil three following management requirements: (1)Globally enable/disable LLDP entity. (2)Globally enable/disable CDP compliance of LLDP. (3)Port-based CDP Compliance controlling of LLDP. 53.1 Scalar objects
Name h3clldpAdminStatus h3clldpComplianceCDPStatus
Access
PDS
Current Current
Description
53.2 h3clldpPortConfigTable
Name h3clldpPortConfigPortNum h3clldpPortConfigCDPComplia nceStatus
Access
not-accessi ble read-write
PDS
Current Current
Description
54. Supported Traps

54.1 Supported Standard Traps
This section contains a list of the traps defined in the standard MIB(defined by IETF or IEEE).
Trap ColdStart WamStart MIB RFC1215 RFC1215 Comments As per MIB As per MIB
Copyright
Page 114 of 132

V0.13 LinkDown RFC1215 The varbinds as defined in RFC1573. This will be used for VPN tunnel interfaces as well. In the case of dynamic VPNs (auto-mesh) - the ifIndex in the linkDown trap may no longer exist in the ifTable. The varbinds as defined in RFC1573. This will be used for VPN tunnel interfaces as well. In the case of dynamic VPNs (auto-mesh) - the ifIndex in the linkUp trap may no longer exist in the ifTable. As per MIB As per MIB As per MIB As per MIB As per MIB not supported As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB As per MIB not supported not supported not supported not supported
Not support
LinkUp
RFC1215
AuthenticationFailure risingAlarm fallingAlarm entConfigChange ospfNbrStateChange ospfVirtNbrStateChange ospfIfConfigError ospfVirtIfConfigError ospfIfAuthFailure ospfVirtIfAuthFailure ospfVirtIfRxBadPacket ospfTxRetransmit ospfVirtIfTxRetransmit ospfOriginateLsa ospfMaxAgeLsa ospfLsdbOverflow ospfLsdbApproachingOve rflow pingProbeFailed
pingTestFailed pingTestCompleted rpMauJabberTrap
RFC1215 RMON-MIB RMON-MIB RFC2737 RFC1850 RFC1850 RFC1850 RFC1850 RFC1850 RFC1850 RFC1850 RFC1850 RFC1850 RFC1850 RFC1850 RFC1850 RFC1850
DISMAN-PIN G-MIB DISMAN-PIN G-MIB DISMAN-PIN G-MIB MAU-MIB
rpMauJabberTrap ifMauJabberTrap
MAU-MIB MAU-MIB
Not support Not support
54.2
Supported Private Traps
This section contains a list of the traps defined in the private MIB(defined by enterprise). 54.2.1 Common Traps
Traps both supported by router and switch

Trap
mplsXCUp mplsXCDown hwMplsLdpFailedInitSessionTh resholdExceeded
MIB HUAWEI-MPLS-LSR-MIB HUAWEI-MPLS-LSR-MIB HUAWEI-MPLS-LDP-MIB
Comments As per MIB As per MIB Not support

Copyright
Page 115 of 132

V0.13
hwMplsLdpCrlspTunnelUp hwMplsLdpCrlspTunnelDown hwMplsLdpCrlspTunnelSetupF ailure hwMplsLdpIncarnUpEventFailu re hwMplsLdpIncarnDownEventF ailure hwMplsLdpEntityUpEventFailur e hwMplsLdpEntityDownEventFa ilure hwMplsLdpSessionUpEventFai lure hwMplsLdpSessionDownEvent Failure hwWriteSuccessTrap hwWriteFailureTrap h3cCfgManEventlog h3cCfgOperateCompletion h3cSysClockChangedNotificati on h3cSysReloadNotification h3cFlhOperNotification h3cEntityExtTemperatureThres holdNotification h3cEntityExtVoltageLowThresh oldNotification h3cEntityExtVoltageHighThres holdNotification h3cEntityExtCpuUsageThresho ldNotfication h3cEntityExtMemUsageThresh oldNotification h3cEntityExtOperEnabled h3cEntityExtOperDisabled h3cEntityExtCriticalTemperatur eThresholdNotification hwRebootSendTrap
HUAWEI-MPLS-LDP-MIB HUAWEI-MPLS-LDP-MIB HUAWEI-MPLS-LDP-MIB HUAWEI-MPLS-LDP-MIB HUAWEI-MPLS-LDP-MIB HUAWEI-MPLS-LDP-MIB HUAWEI-MPLS-LDP-MIB HUAWEI-MPLS-LDP-MIB HUAWEI-MPLS-LDP-MIB HUAWEI-MLSR-SYSTEM-MIB HUAWEI-MLSR-SYSTEM-MIB H3C-CONFIG-MAN-MIB H3C-CONFIG-MAN-MIB H3C-SYS-MAN-MIB H3C-SYS-MAN-MIB H3C-FLASH-MAN-MIB H3C-ENTITY-EXT-MIB H3C-ENTITY-EXT-MIB H3C-ENTITY-EXT-MIB H3C-ENTITY-EXT-MIB H3C-ENTITY-EXT-MIB H3C-ENTITY-EXT-MIB H3C-ENTITY-EXT-MIB H3C-ENTITY-EXT-MIB H3C-COMMON-SYSTEM-MIB
Not support Not support Not support Not support Not support Not support Not support As per MIB As per MIB Not support. Not support. AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB AS PER MIB.
54.2.2
Switch traps
MIB HUAWEI-8021PAE-MIB HUWAEI-LswPERFORMANCE-MIB HUWAEI-LswPERFORMANCE-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB Comments As per MIB As per MIB As per MIB Refer to entity ext mib refer to entity ext mib not support not support not support refer to entity ext mib refer to entity ext mib not support not support not support not support not support not support not support not support
Copyright
Trap supplicantproxycheck
pririsingAlarm prifallingAlarm powerfailure hwPowerNormal hwMasterPowerNormal hwSlavePowerNormal hwPowerRemoved fanfailure hwFanNormal hwBoardRemoved hwBoardInserted hwBoardFailure hwBoardNormal hwSubcardRemove hwSubcardInsert hwBoaardTemperatureLower hwBoaardTemperatureFromLo werToNormal
Page 116 of 132

V0.13
hwBoaardTemperatureHigher hwBoaardTemperatureFormHig herToNormal hwRequestLoading hwLoadFailure hwLoadFinished hwBackBoardModeSetFuilure hwBackBoardModeSetOK hwPowerInserted hwRstpBpduGuarded
HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswTRAP-MIB HUAWEI-LswRSTP-MIB
not support not support not support not support not support not support not support not support The SNMP trap that is generated when an edged port of the BPDU-guard switch receives BPDU packets. The SNMP trap that is generated when a root-guard port receives a superior BPDU. This trap is generated when the bridge is no longer the root bridge of the spanning tree. Another switch with higher priority has already been the root bridge. This trap is generated when a loop-guard port is aged out. This event will be triggered whenever an aggregation changes its speed.(Not implemented now) This event will be triggered whenever any port in aggrerator is made inactive not support not support not support As per MIB As per MIB Not support Not support Not support Not support Not support Not support Not support Not support as per MIB as per MIB as per MIB as per MIB as per MIB as per MIB
hwRstpRootGuarded
HUAWEI-LswRSTP-MIB
hwRstpBridgeLostRootPrimary
HUAWEI-LswRSTP-MIB
hwRstpLoopGuarded
HUAWEI-LswRSTP-MIB
hwSlaveSwitchOver hwAggSpeedChangedNotificati on
HUAWEI-LswMix-MIB HUAWEI-LAG-MIB
hwAggPortInactiveNotification
HUAWEI-LAG-MIB
hgmpMemberfailure hgmpMemberRecover hgmpMemberStatusChange
h3cFtmUnitIDChange h3cFtmUnitNameChange secureAddressLearned secureAddressLearned2 secureViolation2 secureViolation3 secureViolation4 secureLoginFailure secureLogon secureLogoff
hwPortMstiStateForwarding hwPortMstiStateDiscarding hwBridgeLostRootPrimary hwPortMstiRootGuarded hwPortMstiBpduGuarded hwPortMstiLoopGuarded
HUAWEI-HGMP-MIB HUAWEI-HGMP-MIB HUAWEI-HGMP-MIB H3C-FTM-MIB H3C-FTM-MIB A3COM0458-PORT-SECURITY A3COM0458-PORT-SECURITY A3COM0458-PORT-SECURITY A3COM0458-PORT-SECURITY A3COM0458-PORT-SECURITY A3COM0458-PORT-SECURITY A3COM0458-PORT-SECURITY A3COM0458-PORT-SECURITY HUAWEI-LswMSTP-MIB HUAWEI-LswMSTP-MIB HUAWEI-LswMSTP-MIB HUAWEI-LswMSTP-MIB HUAWEI-LswMSTP-MIB HUAWEI-LswMSTP-MIB
Copyright
Page 117 of 132

V0.13
55. Following PRIVATE mib defined in 3FC-510

These private mibs are unsupported:s FDDI-SMT73-MIB CB9000-EME-MIB FMS100-MIB PERSEUS-MIB USRSTACK-MIB USR-DRM-MIB USR-CONFIG-MIB USR-PEM-MIB A3COM0023-RPTREXTENSIONS A3Com463-Component-Status IEEE802dot11-MIB SRAP-DOT11EXT-MIB A3COM-TRAFFIC-MIB A3COM440-LAYER4-REDIRECTION USR-DRM-MIB USR-USER-MAN-MIB Cip-MIB A3COM0012-TRAPTABLE2 A3COM-SWITCHINGSYSTEMS-MIB STACK-MIB CB9000-EME-MIB A-3COM-SWITCHINGSYSTEMS-MIB SRAP-WCM-MIB Stack Configuration MIB - 3Com352 A3COMQOSPROFILES-MIB(3FC410) 3FC-469 mib A3COM-SWITCHINGSYSTEMS-MIB A3COM0353-SWITCH-EXTENSION, A3COM0019-RMON-REMOTE-POLL, A3COM0018-ERMOTE-POLL A3COM-SWITCHING-SYSTEMS-POLL-MIB HOST-EXT-MIB A3Com-Generic-Hub-MIB
Page 118 of 132

V0.13
SWITCHING-SYSTEM-MIB
probeDownloadFile probeDownloadTFTPServer probeResetControl probeDownloadAction probeDownloadStatus probeSoftwareRev
A3COM0420-SWITCH-EXTENSION-LACP-ENABLE A3COM0353-SWITCH-EXTENSION
A3COM0352-STACK-CONFIG A3COM0418-MIB-SUMMARY A3COM0304-RESILIENT-LINKS
56. additional requirement in 3FC 510

56.1 Additional Agent Update Requirements
After upgrade, the administrator must specify this software image as booting software agent and the switch must be reboot to active the new software image and the switch will run the configuration file in flash. The upgrade process can be divided into 3 parts: download file to flash, select booting image, restart switch to active the image. It is important for administrator to select booting image correctly. If he selects right software image it is not necessary to check the software version again and it is ensured by administrator not software. Because the switch has been restarted, so all the tcp sessions are broken and the snmp will lose connection. The file name format is defined in 3FC 518,519document.
56.2 Additional QoS Requirements
The buckbeak products support following qos function

Acl L2 traffic classification based on source/destination mac address or vlan or port L3/L4 traffic classification based on source/destination ip address or tcp/udp port or protocol type Support permit rule and deny rule Qos Support ingress/egress rate-limit per port Support ingress/egress traffic-limit per flow The min bandwidth for rate control is 64kbps and the step is 64kbps Port mirroring with only one monitor-port and all the other port as mirroring-port Traffic mirroring The traffic to cpu mirroring Queue-schedule with SP/WRR/WFQ mode Priority remaping between 802.1p and dscp
Page 119 of 132

V0.13 Priority remarking 802.1p or dscp based on traffic Support WRED/RED Support tail drop Support traffic redirection Support traffic statistics Support 8 egress queues
About resource restrictions please refer to product specification section 5.1 performance summary table. 56.3 56.3.1 Additional Backup / Restore Requirements IP Address, Default Gateway and Subnet Mask
All the configuration can be stroed in configuration file. No special design is to backup the devices ip address, default gateway or subnet mask. 56.3.2 MAC Address Checking
The buckbeak products do not keep a shadow of mac address table so this requirement is not met with. 56.4 Hardware Configuration Checking
If the administrator transfers one configuration file of 52ports device to 24device and he makes a mistake. When the 24 ports device restarts, the software will read the configuration file and execute the content. Because the format of configuration file is same so part of content can run on 24 ports device. The software does not know the configuration file is wrong. The administrator can display the current configuration and compare current configuration with saved configuration with CLI commands or snmp to find the difference. There is no hardware configuration checking. 56.5 Version Numbering
the version number is based on 3FC 518,519 document. 56.6 MIB Items used by 3NS Backup and Restore
The buckbeak products do not support 3com private backup and restore mibs. Please refer section 17 A3COM-HUAWEI-SYS-MAN-MIB.
57. Factory Defaults

This is the expected factory defaults of a units persistent configuration. MIB Group
system system system system
Object
sysName sysContact sysLocation sysDescr
Default Value
4500 3CR17561-91 "3Com 4500 26-Port Software Version 3Com OS V3.01.00s56c01 " 3CR17562-91 "3Com 4500 50-Port Software Version 3Com OS V3.01.00s56c01 " 3CR17571-91 "3Com 4500 PWR 26-Port Software Version 3Com OS V3.01.00s56c01 " 3CR17572-91 "3Com 4500 PWR 50-Port Software
Copyright
Page 120 of 132

V0.13
MIB Group
snmp h3cFtmManMIB h3cFtmManMIB ospfIfTable ospfIfTable ospfIfTable ospfIfTable ospfIfTable ospfIfTable ospfIfMetricTabl e h3cLswIgmpsno opingMib h3cLswIgmpsno opingMib h3cLswIgmpsno opingMib h3cLswIgmpsno opingMib
Object
snmpEnableAuthenTraps h3cFtmAuthMode h3cFtmAuthValue ospfIfRtrPriority ospfIfTransitDelay ospfIfRetransInterval ospfIfHelloInterval ospfIfRtrDeadInterval ospfIfPollInterval ospfIfMetricValue h3cIgmpSnoopingStatus h3cIgmpSnoopingRouter PortAge h3cIgmpSnoopingRespo nseTime h3cIgmpSnoopingHostTi me
Default Value
Version 3Com OS V3.01.00s56c01 " Disable(2) Noauth(1) NULL 1 1 5 The default value of the interface which is Nbma or ptmp is 30,the others is 10 The default value of the interface which is Nbma or ptmp is 120,the others is 40 The default value of the interface which is Nbma or ptmp is 120,the others is 40 10^8/ifspeed The default setting is disabled The default value is 260 seconds The default value is 10 seconds The default value is 260 seconds
58. Agent updating

58.1 58.1.1 How to upgrade the agent 5500 Agent Update Algorithm
1. 2. 3. 3.1 3.2 3.3
3.4 3.5 4. 4.1
determine the running version from entPhysicalSoftwareRev of unit with index 1 determine free space on the device using h3cFlhPartSpaceFree if the size of all agent files is more than the free space on the device, remove some files: if a file is in the h3cSysImageTable and it's h3cSysImageType is not main(1) it is safe to delete work out using h3cSysImageSize, which agent files need to be removed to free up enough space. If there still isn't enough space, fail with a lack of space error. files are deleted by adding a row into the h3cFlhOperTable using the following attributes h3cFlhOperIndex <index> (the index of each file on each unit in the h3cSysImageTable) h3cFlhOperType delete(4) h3cFlhOperSourceFile <filename> as in the h3cSysImageTable h3cFlhOperRowStatus createAndGo(4) poll the h3cFlhOperStatus item untill it is not opInProgress(1). If h3cFlhOperStatus is an error, we fail with an error. remove the entry by setting h3cFlhOperRowStatus to destroy(6) each new agent file can now be uploaded to the device: trigger the upload by adding a row into the h3cFlhOperTable using the following attributes: h3cFlhOperIndex <index_for_unit> (base this on the existing agents for each unit and increment the index) h3cFlhOperType net2FlashWithErase(1) h3cFlhOperProtocol tftp(2) h3cFlhOperServerAddress <local_ip> h3cFlhOperSourceFile <filename> h3cFlhOperRowStatus createAndGo(4)
Copyright
Page 121 of 132

V0.13
4.2 poll the h3cFlhOperStatus entry for the row untill it is no longer opInProgress(1) 4.2.2 if h3cFlhOperStatus is a failure, fail with an error 4.3 remove the entry by setting h3cFlhOperRowStatus to destroy(6) 5. find the h3cSysImageIndex of all the new images in the h3cSysImageTable by checking h3cSysImageName. 6. once all required agent files are uploaded to each unit, set the h3cSysImageType value of the new image to main(1) 8. Find the h3cSysReloadTag with ("3Com-Network-Supervisor") 9. set h3cSysReloadAction to reloadAtOnce(3) to reload the new configuration. 10. poll entPhysicalSoftwareRev for the stack until it matches the agent version expected from the new agent. 11. Check the stack remains intact by ensuring the serial numbers of each unit are still correct, if not then fail the operation. 58.1.2 The MIBs concerned:
HUAWEI-FLASH-MAN-MIB HUAWEI-SYS-MAN-MIB ENTITY-MIB 58.1.3 Functions of the MIBs:
Please refer to the description above. 58.1.4 An example:
You may want to upgrade an XRN device depicted in the following figure (figure 31-1).
figure 31-1 When 3NS wants to update agent, it should follow the steps: 1. 3NS first walks h3cSysImageTable to get which file is main image file and which one is backup image file. Assume that s4a03_01_00s56c01.app is main image , s4a03_01_00s56c01.app is backup image and s4a03_01_00s56c02.app is secure image. 2. The value of h3cSysImageType is main means this file will be the active file after reboot. The value of h3cSysImageType is none means this file is neither main nor backup and just a normal image file. The value of h3cSysImageType is secure means if the secure image is supported and main and backup image files fail to reboot, the secure image file will be used. Some rules, which are enforced by the system, for setting h3cSysImageType: h3cSysImageType can not be set to none manually in order to avoid all the image files are set to none. h3cSysImageType can not be set to secure manually because the secure image file is downloaded to flash during manufacturing. If an image file is set to main or backup, the old one will change to none.
Page 122 of 132

V0.13
If a secure image is set to main, the file has the property main_secure. If a secure image is set to backup, the file has the property backup_secure. If a secure image is set to main and backup ,the file has the property main_backup_secure. If main image is set to backup, the file has the property main_backup, and vice versa. The following table describes whether it is ok to set to another state directly from original state. Original type Set to main Set to backup Set to none Set to secure Yes no no main yes backup Yes no no yes Yes no none yes yes secure yes yes no Yes
For Buckbeak, only main backupand none values of h3cSysImageType are supported. The maximum entries in this table is limited by the space of flash. Now image file size of buckbeak EI is about 4.3M, size of SI is about 3.5M and will be bigger in future. Flash space of SI is 8M and of EI is 16M. For EI products, There are normally 3 image files at most in the flash and one web interface image. Thus h3cSysImageTable has about 3*4=16 entries. For SI products, there are normally 2 image files at most in flash and one web interface image, thus h3cSysImageTable has about 2*4=8 entites. Below table lists the four units entries. Asume entPhysicalIndex of unit1 is 2, of unit2 is 65, of unit3 is 128, of unit4 is191. s4a03_01_00s56c01.app 654321 unit1>flash:/ Main s4a03_01_00s56c02.app 123456 unit1>flash:/ None yyy( other files name) 666666 unit1>flash:/ None s4a03_01_00s56c03.app 654321 unit2>flash:/ Main s4a03_01_00s56c04.app 123456 unit2>flash:/ None yyy( other files name) 666666
Copyright
h3cSysImageName. 131073 h3cSysImageSize. 131073 h3cSysImageLocation. 131073 h3cSysImageType. 131073 h3cSysImageName. 131074 h3cSysImageSize. 131074 h3cSysImageLocation. 131074 h3cSysImageType. 131074 h3cSysImageName. 131075 h3cSysImageSize. 131075 h3cSysImageLocation. 131075 h3cSysImageType. 131075 h3cSysImageName. 4259843 h3cSysImageSize. 4259843 h3cSysImageLocation. 4259843 h3cSysImageType. 4259843 h3cSysImageName. 4259844 h3cSysImageSize. 4259844 h3cSysImageLocation. 4259844 h3cSysImageType. 4259844 h3cSysImageName. 4259845 h3cSysImageSize. 4259845
Page 123 of 132

V0.13
h3cSysImageLocation. 4259845 h3cSysImageType. 4259845 h3cSysImageName. 8388613 h3cSysImageSize. 8388613 h3cSysImageLocation. 8388613 h3cSysImageType. 8388613 h3cSysImageName. 8388614 h3cSysImageSize. 8388614 h3cSysImageLocation. 8388614 h3cSysImageType. 8388614 h3cSysImageName. 8388615 h3cSysImageSize. 8388615 h3cSysImageLocation. 8388615 h3cSysImageType. 8388615 h3cSysImageName. 12517383 h3cSysImageSize. 12517383 h3cSysImageLocation. 12517383 h3cSysImageType. 12517383 h3cSysImageName. 12517384 h3cSysImageSize. 12517384 h3cSysImageLocation. 12517384 h3cSysImageType. 12517384 h3cSysImageName. 12517385 h3cSysImageSize. 12517385 h3cSysImageLocation. 12517385 h3cSysImageType. 12517385
unit2>flash:/ None s4a03_01_00s56c05.app 654321 unit3>flash:/ Main s4a03_01_00s56c06.app 123456 unit3>flash:/ None yyy( other files name) 666666 unit3>flash:/ None s4a03_01_00s56c07.app 654321 unit4>flash: Main s4a03_01_00s56c08.app 123456 unit4>flash: None yyy( other files name) 666666 unit4>flash: None
In the h3cSysCurTable of HUAWEI-SYS-MAN-MIB, the running image file and configuration file are: Use h3cSysCurTable to get the index h3cSysCurImageIndex for the current image. See above table. Get the filename of the current image using h3cSysCurImageIndex All the image files in the A3COM-HUAWEI-SYS-MAN-MIB: system are described according to the h3cSysImageTable
3NS will use a dual bank agent image system. 3NS will use 2 default images names, s4a03_01_00s56c01.app, s4a03_01_00s56c01.app. 3NS will overwrite the non-currently active bank file. The agent must have the default bank names in all file system tables as required requires. new rows, it will use existing entries. 3NS will not create
The device has permanent entries in the h3cSysImageTable for the stack index and for any unit indexes as it requires for both default bank image names (located in the root directory).
Page 124 of 132

V0.13
A new MIB, h3cSysImageType to return whether the bank is active or inactive. 3NS will not create these entries, but will set the h3cSysImageType. For the value of h3cSysImageType, main means active, backup means inactive. If the current active image iss4a03_01_00s56c01.app, the new filename will be s4a03_01_00s56c0 2.app. If it is s4a03_01_00s56c02.app or another filename, the new agent filename will be s4a03_01_00s56c01.app. The device creates automatically a permanent entry in the h3csysReloadScheduleTable for the active image for every unit when h3cSysImageType is set to active. This index of the table above is defined in A3COM-HUAWEI-SYS-MAN-MIB as below: 31 15 0 +++++++++++++++++++++++++++++++++++++++++++ + entPhysicalIndex + random image index(16(bits)+ +++++++++++++++++++++++++++++++++++++++++++ 3. 3NS uses h3cFlhOperTable to download the new image file to the fabric and overwrites the an existed image file (here existed file is s4a03_01_00s56c02.app) by setting h3cFlhOperDestinationFile to that existed file name. h3cFlhOperType.131073 net2FlashWithErase(2) h3cFlhOperProtocol. 131073 tftp(2) h3cFlhOperServerAddress. 131073 10.153.70.110 h3cFlhOperSourceFile. 131073 s551_02.bin s4a03_01_00s56c02.ap h3cFlhOperDestinationFile. 131073 p h3cFlhOperEndNotification. 131073 True(1) h3cFlhOperRowStatus. 131073 1 Here the h3cFlhOperIndex with 131073 means that the image file of s551_02.bin will be downloaded and renamed as s4a03_01_00s56c02.app to unit1 of the fabric(stack). So for Buckbeak, there is also a rule for h3cFlhOperIndex just as following:
31 15 0 +++++++++++++++++++++++++++++++++++++++++++++++ entPhysicalIndex of stack + random index(derived by 3NS) +++++++++++++++++++++++++++++++++++++++++++++++
During downloading, 3NS will poll h3cFlhOperStatus while it is opInProgress. When h3cFlhOperStatus is opSuccess, this indicates that the agent has copied the image to this unit as it requires. If h3cFlhOperStatus returns an error, it means that the operation has failed and 3NS will not activate the new image file or attempt to reboot the default agent.. 5. If successful, 3NS sets the new downloaded image file to main using h3cSysImageType for each unit. 6. The device creates automatically a permanent entry in the h3csysReloadScheduleTable for the main image for every unit when h3cSysImageType is set to main. H3cSysReloadEntity.131072 2(unit1) h3cSysReloadEntity. 4259842 65(unit2) h3cSysReloadEntity. 8388612 128(unit3) h3cSysReloadEntity. 12517382 191(unit4) h3cSysReloadCfgFile. 131072 0 h3cSysReloadCfgFile. 4259842 0 h3cSysReloadCfgFile. 8388612 0 H3cSysReloadCfgFile. 12517382 0
4.
Page 125 of 132

V0.13
H3cSysReloadImage. 131072 H3cSysReloadImage. 4259842 H3cSysReloadImage. 8388612 H3cSysReloadImage. 12517382 H3cSysReloadReason. 131072 H3cSysReloadReason. 4259842 H3cSysReloadReason. 8388612 H3cSysReloadReason. 12517382 H3cSysReloadScheduleTime. 131072 H3cSysReloadScheduleTime. 4259842 H3cSysReloadScheduleTime. 8388612 H3cSysReloadScheduleTime. 12517382 H3cSysReloadScheduleTagList. 131072 H3cSysReloadScheduleTagList. 4259842 H3cSysReloadScheduleTagList. 8388612 H3cSysReloadScheduleTagList. 12517382 H3cSysReloadRowStatus. 131072 H3cSysReloadRowStatus. 4259842 H3cSysReloadRowStatus. 8388612 H3cSysReloadRowStatus. 12517382 Here, H3cSysReloadImage.1 = 131074 = 2 *
131074 4259843 8388613 12517383 Upgrade Upgrade Upgrade Upgrade 3Com-Network-Supervisor 3Com-Network-Supervisor 3Com-Network-Supervisor 3Com-Network-Supervisor Active Active Active Active
216 +2; that is unit1s main image file.
Also a default tag must exist. 3NS will not create it. This tag is like as following: H3cSysReloadScheduleTagList 3Com-Network-Supervisor 7. 8. 3NS need not read the currently running image name in H3cSysCurTable to find out which file is main because it gets the current main image from h3cSysImageTable. 3NS then will ask the agent to reload the default image. It sets the reload action to reboot at once for the stack. 3Com-Network-Supervisor reloadAtOnce(3)
H3cSysReloadTag.0 H3cSysReloadAction.0
3NS waits for device to restart. It then matches the version number in the filename it has just downloaded to the version number reported by entPhysicalSoftwareRev of the stack. This MIB changes to the new version number when all the units in the fabric have rebooted and are running the same version. 3NS should check the entity table to ensure stack integrity. While the system fails to reboot with specific main file , a trap will be sent to indicate which the current image file (I.e back-up or secure) is because the device can not stand up normally.(whether the trap is sent or not depend on the product). When upgrading is failed, or units do not reboot, the stack splits because there may be different agent versions running. 3NS only communicates with the master. The IP address of the master may not be the same. The user may retry the upgrade from 3NS, downgrade the device, or attempt a recovery by doing an upgrade manually from the CLI 3NS derives the version number from the filename. There must be agreement between 3NS, the filename and the value returned by the device. In the above example, the filename is s551_02.bin, so the agent version returned by hwSoftwareversion must be 1.02. 3fc-518 and 519 describe the format and need to be supported by the device, the version numbering specified in the MIB companion to show it is clearly understood. When the two versions match exactly, 3NS will report to the user that the upgrade has been successful.
Page 126 of 132

V0.13
58.2 58.2.1
How to backup & restore the agent The MIBs concerned:
A3COM-HUAWEI-CONFIG-MAM-MIB ENTITY-MIB 58.2.2 Functions of the MIBs: Please refer to the description above. 58.2.3 An example:
Here we will discuss the action of backup and restore. When using h3cCfgOperateTable, the first two bytes of h3cCfgOperateIndex are specified to be the entPhysicalIndex of the unit. For example, all the operation on the unit1 (considering the entPhysicalIndex of which is 2) must specify the value of the h3cCfgOperateIndex with 0x0002xxxx. The operation on the whole fabric must specify the value of hwCfgOperateIndex with 0x0001xxxx.
The following table is an example for a set operation of creating an instance in the entry. To save the configuration of the unit1 from memory to flash, the following is an example (with the index of 0x00020001). NAME h3cCfgOperateType.131073 h3cCfgOperateFileName h3cCfgOperateEndNotificationSwitch.131073 h3cCfgOperateRowStatus.131073 VALUE running2Startup(1) <filename>.cfg True(1) createAndGo(4)
If you want to save the configuration of the whole fabric from memory to flash, using the index of 0x0001xxxx. h3cCfgOperateFileName is optional, if we dont choose it when create a row, the configuration will be saved as default configuration name. Getting the fabric configuration file(backup saved configuration) from unit1(with the index of 0x00020002). The saved configuration file will be transferred to tftp server, and the file name will be BackupCfg_1.cfg. NAME VALUE h3cCfgOperateType.131074 h3cCfgOperateProtocol. 131074
h3cCfgOperateFileName. 131074
startup2Net(6) Tftp BackupCfg.cfg 10.153.70.110 True(1) createAndGo(4)
h3cCfgOperateServerAddress. 131074 h3cCfgOperateEndNotificationSwitch. 131074 h3cCfgOperateRowStatus.131074
To Getting the whole fabric configuration file from device, please do the above operate with the index of 0x0001xxxx. The backup configuration files in tftp server will be named BackupCfg_n.cfg, you can distinguish the unitID from the number n. For example, the backup configuration file of unit1 will have the name BackupCfg_1.cfg: Here is a restore example. The operation will restore the configuration stored in BackupCfg_1.cfg from the server (10.153.70.110) to the unit1(with the index of 0x00020003) by using tftp.
Page 127 of 132

V0.13
NAME h3cCfgOperateType.131075 h3cCfgOperateProtocol.131075

h3cCfgOperateFileName.131075
VALUE net2Startup(5) Tftp BackupCfg.cfg 10.153.70.110 True(1) createAndGo(4)
h3cCfgOperateServerAddress. 131075 h3cCfgOperateEndNotificationSwitch. 131075 h3cCfgOperateRowStatus. 131075
If you do the above operation using the index of 0x0001xxxx, it will be in effect on the whole fabric. And the file named BackupCfg_n.cfg which is in tftp server will be restored to the unit whose unitID is number n. For example, the file named BackupCfg_2.cfg will be restored to the unit2. In the old version, only tftp protocol supports to backup & restore the whole fabric. In the new version, both TFTP and FTP protocols support.
59. about 760-174

59.1 3 about section 4.1 3com requirement
In section 4.3.1.1 of 760-174 mentions the following requirement and we do not agree part of requirement: All standard MIBs should be latest RFC
Comments: all the mibs are based on the current platform not the latest RFC. All devices must be tested for SNMP conformance before release to 3Com.
Comments: ok All Huawei private MIBs to be under the a3Com.45.1 (jv-mib.huawei) branch.
Comments: ok All Huawei private MIBs must contain a complete DESCRIPTION in English for each object
Comments: not all private mibs contains a complete description. All MIBs must be compiled with HP Openview.
Comments: ok Devices must conform to 3fc-510 and support as many of the IEEE standard MIBs/3Com 3fcs/Huawei MIBs specified there as possible
Comments: the unsupported mib in 3fc-510 have been listed in section 44 Where an 3fc-510 MIB does not exist on a device, this MIB should be implemented in preference to creating a new private MIB
Comments: if the mib defined in 3fc-510 is supported it is listed in section 44 Where new private MIBs are used, the same private MIB should be implemented on all JV-CO devices (where applicable)
Comments: its based on the actual situation 59.2 about section 4.4 mib companion
In section 4.4.1.1 mentions that The MIB Companion should describe how the MIBs are implemented on the devices rather than the MIBs themselves.
Page 128 of 132

V0.13
Comments: we think It is not necessary to describe the implementation of mibs becase all these feature are introduced in product spec and CLI manual. 59.3 about section 4.5 agent version
The display of software version is based on bedrock platform style. For example, the display of version number on buckbeak products should be the below: 59.4 about section 4.6 trap destination
When a trapDest entry is added: (a) All traps will be enabled Comments: all traps are enabled by default. (b) The trap source will be set to to the IP address which was used to make the SNMP request; Comments: the trap source must be specified by cli commands. (c) The CLI and the MIB will remain in sync in V1 version, because we can adds a new target-host in V2,V3 version via the CLI. If the user adds a new target-host in V1 version via the CLI, a new entry is added to the TrapDest table. Comments: not sure about it. Confirm with bedrock mib team. (d) The user can manually disable trap groups using the CLI. Command: [Router]undo snmp trap enable Comments: agree In addition, We add a node to save current configuration Comments: the flash man mib supports it.
59.5 about section 4.8 topology
the stp and link aggregation can be shown and the mac address can be searched in dot1dTpFdbTable. There is no software copy for the mac table. The algorithm to derive the unit/port from the ifindex is done in this document. 59.6 about section 4.9 module and port sizing
3com requirement: Support HUAWEI_DEVICE_MIB, HUAWEI_LswINF_MIB as described in 3fc-510 in all switches Comments: ok Support router.module.moduletable in all routers (Module Table may be replaced by ENTITY_MIB on new devices, but module table will continue to be supported on existing devices) Comments: ok Also support the sections marked MAU-MIB in 3fc-510. Comments: mau-mib is not supported, refer to section 14. Phase in support for Entity MIB on new devices - Please provide timetable and details of which new devices will support the Entity MIB Comments: the current entity mib supports buckbeak/F1/Garibaldi products. 59.7 About section 4.10 HC-RMON
HC-RMON is not supported by buckbeak products.
Copyright
Page 129 of 132

V0.13
59.8
About section 4.11 agent update
Refer to section 47 in buckbeak mib companion. 59.9 About section 4.12 backup and restore
3com requirement: Allow TFTP backup and restore to be initiated remotely by SNMP. The restore operation must return the device to exactly the same configuration as is stored in the backup (regardless of subsequent changes to the device). Also see section 7 Additional Backup / Restore Requirements. Comments: A3COM-HUAWEI-CONFIG-MAN-MIB is used to implement this functionality, not 3FC-469. See for more details 59.10 about section 4.12 Component monitors the buckbeak poroducts supports the following hardware monitoring: 1> if the power supply of EI products fails the software can detects this errors and reports it. 2> If the fan stops rotating the software can detects it and reports it. 3> If the temperate of PSU on POE device is over the setting the software can detect it and report it. 4> The cpu usage and memory usage can not be monitored. 59.11 About section 4.14 management via CLI commands The CLI commands are based on bedrock platform and it is similar with 7700 products. 59.12 About section 4.15 POE mib The mib of POE feature is similar with 3FC document. Refer to section 38/39 in buckbeak mib companion. 59.13 About section 5 Agent-medium priority 59.13.1 About section 5.1 vlans The RFC 2674 is supported but the ip routing configuration mib will keep unchanged. 59.13.2 About section 5.2 device warranty registration The permant unit configuration data is supported now and the 3FC number or track serial number is stored in flash which can be obtained by entity mib. The process of warranty registration is done by customer. 59.13.3 About section 5.3 radius and network login The specific traps when the user logs on/logs off are based on bedrock platform. 59.14 About section 6 Agent-Low priority
59.14.1
About section 6.1 Rmon enable This
3com requirement: Provide a common MIB table to allow RMON to be enabled on a given LAN interface. will be used by Router Manager and Switch Manager Performance Monitoring/RMON function; Comments: refer to section 10 in buckbeak mib companion.
Copyright
Page 130 of 132

V0.13 59.14.2 About section 6.2 Qos
3com requirement: Huawei Routers and Switches support Traffic Classification, Traffic Policing, Traffic Shaping, Traffic Marking, Congestion Management, and Congestion Avoidance. We would like to configure Classification and Congestion Management using the 3NS Prioritisation Wizard. To do this we require a common QoS MIB to be supported by all Huawei Switches and Routers perhaps based on the VRP 3 QoS MIB. This MIB should be a superset of the functionality of all devices, with each device implementing the features it can support. Huawei to supply details of common MIB Comments: refer to section 27/28 in buckbeak mib companion.
59.15 About section 7 switch manager and router manager

59.15.1
About section 7.1 Testing
3com requirement: Huawei are responsible for all testing of the functionality of the application on all supported platforms (see platform list below). A Test Report will be provided by Huawei with each code drop listing all known problems and any fixes/changes since the last code drop
Comments: it will be done by our test team. 59.15.2 About section 7.2 Installation Buckbeak/F1/Garibaldi products can support same swith manager.
59.15.3
About section 7.3 Supported Platform
Ok.
59.15.4
About section 7.4 Release Notes
About release note requirement: Text file Release Notes must be installed and displayed during installation for both products. The Release notes will also be displayed in the Start menu. Comments:The above requirement can not be met with. The release not can not shown when downloading a software image to flash.
59.15.5
About section 7.5 new feature list
In plan phase, 3com will join the discussion about the feature design.
59.15.6
About section 7.6 Device Mimic
ok
59.15.7
About section 7.7 Common bug fixes
About the common bugs, the bug will be fixed on the platform and each products will take new released platform code to release patches.
59.15.8
About section 7.8 Co-Existence
3com requirement: Huawei must provide a detailed plan showing how RM and SM and their respective patches will co-exist on the same PC. Can they be installed in any order, can they be de-installed separately etc.
Page 131 of 132

V0.13
Comments: Agreed, the RM and SM can be installed in any order, but they cant be de -installed separately
59.15.9
About section 7.9 vresion number
The quidview and web interface will also have a software version number, just like x.xx;
59.15.10 About section 7.10 Improving consistency between SM/RM
About the consistency between SM and RM, the bedrock will do our best to realize it, but we dont assure that all functionality will have the same look and feed, because the Router Manager and Switch Manager is different from the system architecture. We can ensure the functionality have the same look and feed in Elan / Garibaldi/F1.
59.15.11 About section 7.11 Improving online help
3com requirement: MS Word format User Guide (based on On-line help) to be provided for each SM/RM release/upgrade. Installation section to be added for both products (based on QuidView Installation Guide) Comments: not sure, confirm with quidview team. 3com requirement: Text needs to be made consistent between SM and RM and enhanced in various ways details TBD. Comments: not sure, confirm with quidview team.
60. Appendix
Copyright
Page 132 of 132

3com 4500 MIB Companion (V3.3.2p19)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

3com 4500 MIB Companion (V3.3.2p19)

Uploaded by

Copyright:

Available Formats

3Com 4500(buckbeak) MIB Compaion

Title: Authors: Revision: Creation Date:

1404013 Buckbeak MIB Companion

Approvals Title Name Date

3Com Product Manager

JVCo Product Manager

3Com Programme Manager

JVCo Programme Manager

3Com Software Leader

JVCo Software Leader

COMPANY CONFIDENTIAL: NOT FOR EXTERNAL DISTRIBUTION

3Com 4500(buckbeak) MIB Compaion

IFMIB- RFC2233 5.1

dot1dBaseBridgeAddress dot1dBaseNumPorts dot1dBasePortTable DOT1DTP dot1dTpLearnedEntryDiscards dot1dTpAgingTime dot1dTpFdbTable dot1dTpPortTable

SNMP PROTOCOL MIBS 9.1 9.2 SNMPMIB { SNMPMODULES.1} SNMPFRAMEWORKMIB{ SNMPMODULES.10}

COMPANY CONFIDENTIAL: NOT FOR EXTERNAL DISTRIBUTION

3Com 4500(buckbeak) MIB Compaion

RFC2674 - BRIDGE MIB EXTENSIONS

dot1qVlanStaticTable dot1qVlanCurrentTable dot1qPortVlanTable DOT1QTP GROUP dot1qFdbTable dot1qTpFdbTable dot1qTpGroupTable

RFC1850-OSPF(NOT SUPPORT) RFC 1724-RIPV2

13.1 13.2 13.2.1 13.3 13.3.1 13.4 13.4.1 14. 15.

RFC2668 MAU MIB(NOT SUPPORT) A3COM-HUAWEI-FLASH-MAN-MIB:FLASH MANAGEMENT MIBS

COMPANY CONFIDENTIAL: NOT FOR EXTERNAL DISTRIBUTION

3Com 4500(buckbeak) MIB Compaion

15.1 15.1.1 15.1.2 15.1.3 15.2 16.

A3COM-HUAWEI-SYS-MAN-MIB: SYSTEM INFORMATION AND SYSTEM MANAGEMENT

A3COM-HUAWEI-LSWIGSP-MIB HWLSWIGMPSNOOPINGMIB { LSW COMMON 7 } hwLswIgmpsnoopingMibObject { h3cLswIgmpsnoopingMib 1 }

18.1 18.1.1 19.

hwDhcpGroupTable {hwLswDhcpMibObject 1 } hwDhcpSecurityTable {hwLswDhcpMibObject 2 } hwDhcpToL3IfTable {hwLswDhcpMibObject 3 }

A3COM-HUAWEI-DHCPR-MIB LACP MIBS IEEE8023-LAG-MIB dot3adAgg Group

dot3adTablesLastChanged A3COM-HUAWEI-LAG-MIB hwAggLinkTable hwAggPortTable hwAggResourceAllocationValue

COMPANY CONFIDENTIAL: NOT FOR EXTERNAL DISTRIBUTION

3Com 4500(buckbeak) MIB Compaion

24. 24.1 25. 25.1 25.2 25.3 25.4 26.

A3COM-HUAWEI-LSWRSTP-MIB SCALAR OBJECTS: HWDOT1DSTPIGNOREDVLANTABLE HWDOT1DSTPPORTXTABLE HWRSTPEVENTSV2 DEVICE MANANGEMENT MIBS

MAC ADDRESS MANANGEMENT MIBS- HWLSWMACPORT

29.1 29.2 29.3 29.4 29.4.1 29.5 29.5.1 30.

hwifVLANTrunkStatusTable HWETHERNETTABLE hwethernetTable

hwdot1qVlanMIBTable HW VLANINTERFACETABLE hwVlanInterfaceTable HW VLANINTERFACEADDRTABLE hwVlanInterfaceAddrTable

TIME RANGE MANANGEMENT MIBS

COMPANY CONFIDENTIAL: NOT FOR EXTERNAL DISTRIBUTION

3Com 4500(buckbeak) MIB Compaion

SCALAR OBJECTS H3CFTMUNITTABLE NOTIFICATIONS VOICE VLAN MIB

COMPANY CONFIDENTIAL: NOT FOR EXTERNAL DISTRIBUTION

3Com 4500(buckbeak) MIB Compaion

38.1 38.2 38.3 39. POE MIB

SCALAR OBJECTS H3CVOICEVLANOUITABLE H3CVOICEVLANPORTTABLE(THIS TABLE IS FOR BUCKBEAK VERSION 3.3.2PXX.)

pethPsePortTable pethMainPseObjects pethNotificationControl PETHCONFORMANCE pethComplicance pethGroups

POE EXT MIB

A3COM-QOS-PROFILE-MIB DEFINITIONS QOSPROFOBJECTS QosProf

SNMP-REPEATER-MIB RFC2108(NOT SUPPORT) A3COM-HUAWEI-IP-BROADCAST-MIB

A3COM-HUAWEI-VRRP-EXT-MIB SCALAR OBJECTS H3CVRRPEXTTABLE OF H3CVRRPEXTMIBOBJECT A3COM-HUAWEI-PROTOCOL-PRIORITY-MIB

COMPANY CONFIDENTIAL: NOT FOR EXTERNAL DISTRIBUTION

3Com 4500(buckbeak) MIB Compaion

54.1 54.2 54.2.1 54.2.2 55. 56.

58.1 58.1.1 58.1.2 58.1.3 58.1.4 58.2 58.2.1 58.2.2 58.2.3

COMPANY CONFIDENTIAL: NOT FOR EXTERNAL DISTRIBUTION

3Com 4500(buckbeak) MIB Compaion

COMPANY CONFIDENTIAL: NOT FOR EXTERNAL DISTRIBUTION

3Com 4500(buckbeak) MIB Compaion

Revision 0.01 0.02

0.05 0.06 0.07