3com 4200G MIB Companion
3com 4200G MIB Companion
Approvals
Title 3Com JVCo 3Com JVCo 3Com JVCo
Product Product Programme Programme Software Software
Manager Manager Manager Manager Leader Leader
Name
Date
I Revision History 16
ii References 18
1. Introduction 18
3. RFC1213 - MIB-II 22
3.3.1. atTable: 28
3.4.2. ipAddrTable: 30
3.5.2. tcpConnTable: 30
3.6.2. udpTable: 31
3.8.1. ipNetToMediaTable 32
4. ifMIB- RFC2233 32
4.1. ifXTable 32
5. IP-FORWARD-MIB 34
5.1. ipCidrRouteTable 34
5.2. ipCidrRouteNumber 35
6. A3COM-HUAWEI-LswINF-MIB 35
6.2. hwifHybridPortTable 36
6.3. hwifVLANTrunkStatusTable 36
6.4. hwethernetTable 37
6.5. hwifXXTable 38
7. A3COM-HUAWEI-IswVLAN-MIB 40
7.1. hwdot1qVlanMIBTable 40
7.2. hwVlanInterfaceTable 41
7.3. hwVlanInterfaceAddrTable 42
8. EtherLike-MIB-RFC2665 42
8.1. dot3StatsTable 42
9. BRIDGE-MIB-RFC1493 43
9.1. dot1dBase 43
9.1.1. dot1dBaseBridgeAddress 43
9.1.2. dot1dBaseNumPorts 43
9.1.3. dot1dBasePortTable 43
9.2. dot1dTp 44
9.2.1. dot1dTpAgingTime 44
9.2.2. dot1dTpFdbTable 44
9.2.3. dot1dTpPortTable 44
10.2.1. dot1qBase 45
10.2.2. dot1qTpFdbTable 46
10.2.3. dot1qTpGroupTable 46
10.2.4. dot1qPortVlanTable 46
11.4.2. snmpTargetAddrTable 49
11.4.3. snmpTargetParamsTable 49
11.7.1. vacmMIBObjects 53
11.7.2. vacmMIBViews 53
12.1.1. Statistics 54
12.1.2. History 55
12.1.2.1. historyControlTable 55
12.1.2.2. etherHistoryTable 56
12.1.3. Alarm 56
12.1.3.1. alarmTable 56
12.1.4. Event 57
12.1.4.1. eventTable 57
12.1.4.2. logTable 58
12.2.1. etherStatsHighCapacityTable 58
12.2.2. etherHistoryHighCapacityTable 59
12.3.1. priAlarmTable 60
13. A3COM-HUAWEI-FLASH-MAN-MIB 61
13.1. h3cFlashDevice 61
13.1.1. h3cFlhSupportNum 61
13.1.2. H3cFlashTable 61
13.1.3. H3cFlashChips 62
13.1.4. h3cFlashPartitions 62
13.1.5. huaweiFlhFileTable 63
13.2. H3cFlashOperate 63
13.2.1. h3cFlhOpTable 65
14. A3COM-HUAWEI-CONFIG-MAN-MIB 66
14.1.2. h3cCfgLogTable 67
14.2.1. h3cCfgOperateTable 68
14.2.2. h3cCfgOperateResultTable 70
15. A3COM-HUAWEI-SYS-MAN-MIB 70
15.2. h3cSysCurTable 71
a) h3cSysReloadScheduleTable 71
15.3. h3cSysImageTable 72
15.4. h3cSysCFGFileTable 72
15.5. h3cSysBtmLoadTable 73
15.6. Notifications 75
16. A3COM-HUAWEI-LswIGSP-MIB 75
17. A3COM-HUAWEI-LswDHCP-MIB 76
17.1. hwLswDhcpMib 76
17.1.1. hwLswDhcpMibObject 76
17.1.1.1. hwDhcpGroupTable 76
17.1.1.2. hwDhcpSecurityTable 76
17.1.1.3. hwDhcpToL3IfTable 76
18.1. IEEE8023-LAG-MIB 77
18.1.1.1. dot3adAggTable 77
18.1.1.2. dot3adAggPortListTable 77
18.1.2.1. dot3adAggPortTable 78
18.1.3. dot3adAggPortStatsTable 79
18.1.3.1. dot3adAggPortDebugTable 79
18.1.4. dot3adTablesLastChanged 80
18.2. A3COM-HUAWEI-LAG-MIB 80
18.2.1. hwAggLinkTable 80
18.2.2. hwAggPortTable 81
18.2.3. hwAggResourceAllocationValue 81
19. IEEE8021D-STP-MIB 82
19.1. dot1dStpPortTable 82
19.2. dot1dStpGlobalTable 82
20. . A3COM-HUAWEI-LswMSTP-MIB 84
20.2. hwdot1sVIDAllocationTable 85
20.3. hwdot1sInstanceTable 85
20.4. hwdot1sPortTable 86
21.1.1.1. OverViews 89
I Revision History
hRHgmpWhitelistNbTable, hRHgmpBlacklistTable,
hRHgmpMemberPriPortTable, hRHgmpNTDPTopLinkStatus in
A3COM-HUAWEI-HGMP-MIB
h3cSecureVlanAssignment, h3cSecureRalmReauthenticate
0.07 13/04/06 Zhanghailun 1. Can not write spaces to sysname MIB object submitted
D32170
7 LSD16507
sysDescr
3. add hwAggPortInactiveNotification2,
h3cLpbkdtTrapLoopbacked, h3cLpbkdtTrapRecovered,
h3cLpbkdtTrapPerVlanLoopbacked, h3cLpbkdtTrapPerVlanRecovered
ii References
No Document
1. Introduction
Firstly, if a MIB is not listed in this document, then it must not be supported.
Secondly, although there are many MIBs listed in this document, the specific features
and/or functions should be implemented and/or supported firstly before the corresponding
MIBs are supported.
If a MIB is not supported or implemented, then the notifications or traps (if existed) of the
MIB are not supported as well.
2006-04-14 Page18, Total 203
Confidential Information of H3C.
In the tables in which the detail of MIB objects are filled, the explanations of the header of
the column are stated here:
If the meaning of a MIB is not clearly described in tables, or other information would be
provided, an independent section could be appended after/before the related MIBs or
tables. That is, further descriptions may be given below the tables, at the beginning of the
section. These descriptions can be written as a paragraph, a formula, a chart, etc.
Aragog will conform to the IETF RFCs/ IEEE standards and Huawei-3Com private standards
as described below.
ipDefaultTTL:read-only supported
ipRouteTable:read-only supported
ipNetToMediaTable:read-write supported
tcpConnState :read-only supported
EGP group: not supported.
Supported Monitoring, Trap Registration
RFC1215 RFC-1215 Traps MIB 1.0
B
RFC2819 RMON I 1.1 4 groups – EtherStats, History, Alarms &
Events on Aragog
etherHistoryHighCapacityGroup are
supported partially
-MIB
-MIB
B -vlan.mib
A3COM-HUAWEI-LswMAM-MI A3com-huawei-splat
1.0 Fully supported
B -mam.mib
IB -rstp.mib
A3COM-HUAWEI-LswIGSP-MI A3com-huawei-splat 1.0 Fully supported
B -igsp.mib
.mib
NG-MIB mib
A3COM-HUAWEI-ENTITY-EX A3com-huawei-entit 1.0 Fully supported
T-MIB y-ext.mib
ON-MIB lation.mib
A3COM-HUAWEI-LswQos-MIB A3com-huawei-splat 1.0 Partially supported.
-qos.mib
mib
management of
cluster
A3COM-HUAWEI-UI-MAN-MIB A3com-huawei-ui-m 1.0 Fully supported
an.nub
A3COM-HUAWEI-8021PAE-MI A3com-huawei-8021 1.0 Fully supported
B x-ext.mib
URITY-MIB security.mib
A3COM-HUAWEI-LAG-MIB A3com-huawei-lag. 1.0 Fully supported
mib
1.0 Partially supported
A3COM-HUAWEI-RMON-EXT- A3com-huawei-rmon
MIB -ext.mib
A3COM-HUAWEI-TRNG-MIB A3com-huawei-trng. 1.0 Fully supported
mib
H-EXT-MIB er-eth-ext.mib
3. RFC1213 - MIB-II
Only the groups mentioned below are supported. All other MIB-II groups are not supported
(udp, tcp, snmp).
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.
GigabitEthernet 1/0/1
In 32bits index, frame(unit) is behind slot, just to inherit VRP former structure. In figure 2,
portnum is calculated by VRP on base of interface name. It is not the global port number
notified by Device Management Module. It means this number comes from interface name,
such as GigabitEthernet 1/0/1. Portnum equals to Subslot Num plus Max Port Num for Each
Subslot and add 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. 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.
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. They are same.
In fact, others don’t need to care about this offset. Offsets just mean different logic interface is
stored in different position. For example, index structure as fllowing:
Slot(6bits)/unit(4bits)/position(19bits)/type(3bits)
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.
0: loopback
1: GigabyteEthernet
2: Ethernet
7: Vlan-interface
Above definition is for product Aragog, which has one CPU on one device.
port.
The value of testing(3) is not
supported
ifOperStatus read-only No The current operational state (link
status) of the interface. This node
is not supported for aux port.
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.
ifInOctets read-only No This node is not supported for
aux, null0 and inloopback0
interface.
ifInUcastPkts read-only No This node is not supported for
aux, null0 and inloopback0
interface.
3.3.1. atTable:
3.4.2. ipAddrTable:
3.5.2. tcpConnTable:
3.6.2. udpTable:
3.8.1. ipNetToMediaTable
4. ifMIB- RFC2233
4.1. ifXTable
ifAlias read-write No
This object is an 'alias' name for
name.
Just support read-only for aux
port.
ifCounterDiscontinuityTime read-only No not support
ifStackStatus Not support
5. IP-FORWARD-MIB
5.1. ipCidrRouteTable
5.2. ipCidrRouteNumber
6. A3COM-HUAWEI-LswINF-MIB
6.2. hwifHybridPortTable
Note: The values of below nodes must be appointted at the same time when SET:
hwifHybridTaggedVlanListLow,
hwifHybridTaggedVlanListHigh,
hwifHybridUnTaggedVlanListLow,
hwifHybridUnTaggedVlanListHigh
6.3. hwifVLANTrunkStatusTable
6.4. hwethernetTable
6.5. hwifXXTable
7. A3COM-HUAWEI-IswVLAN-MIB
7.1. hwdot1qVlanMIBTable
7.2. hwVlanInterfaceTable
7.3. hwVlanInterfaceAddrTable
Variable Bindings
Must set this object when create
a row
hwVlanInterfaceIpType read-write No Ip address type of interface.
hwVlanInterfaceIpRowStatus read-create No Only support createAndGo(4),
active(1) , destory(6)
8. EtherLike-MIB-RFC2665
8.1. dot3StatsTable
9. BRIDGE-MIB-RFC1493
9.1. dot1dBase
9.1.1. dot1dBaseBridgeAddress
9.1.2. dot1dBaseNumPorts
9.1.3. dot1dBasePortTable
9.2. dot1dTp
9.2.1. dot1dTpAgingTime
9.2.2. dot1dTpFdbTable
Because the fdb address is obtained from the driver. Device just retrieves information from
driver and the fdb address already stored in memory. So there are not any more
measurements to make the quering proceduce faster.
Note: Since the fdb addresses kept in software is indexed by mac address and vlan, the
table only uses mac address as its index, there will be some collision.
9.2.3. dot1dTpPortTable
The new Bridge MIB is an extension to the current Bridge MIB (RFC 1493), and is only partially
supported.
Scalar object:
dot1dPortCapabilitiesTable
dot1dPortPriorityTable
10.2.1. dot1qBase
10.2.2. dot1qTpFdbTable
10.2.3. dot1qTpGroupTable
10.2.4. dot1qPortVlanTable
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.
11.4.2. snmpTargetAddrTable
11.4.3. snmpTargetParamsTable
2: [Loaded: SNMPv2-TM]
snmpTargetAddrTDomain.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.55.5
4.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.5
4.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.5
5.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)
10:
snmpTargetParamsMPModel.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.5
5.54.46.55.54 (integer) 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.
14:
snmpTargetParamsStorageType.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.4
6.55.54.46.55.54 (integer) nonVolatile(3)
15:
snmpTargetParamsRowStatus.116.114.97.112.104.111.115.116.46.103.108.46.49.54.57.46.50.53.52.46.
55.54.46.55.54 (integer) active(1)
11.7.1. vacmMIBObjects
11.7.2. vacmMIBViews
12.1.1. Statistics
The steps to create a new row under the table of etherStatsTable through MIB Browser is
as usual. Only one column need
And then, you could find this new added row through the walk operation or the command
of "dis rmon statistics unit 1" under CLI.
12.1.2. History
12.1.2.1. historyControlTable
12.1.2.2. etherHistoryTable
As the definition above, the maximum entries of the table are1000( 100*10);
12.1.3. Alarm
12.1.3.1. alarmTable
12.1.4. Event
12.1.4.1. eventTable
12.1.4.2. logTable
12.2.1. etherStatsHighCapacityTable
kts
ctets
kts64Octets
ets
kts65to127Octets
27Octets
kts128to255Octets
255Octets
kts256to511Octets
511Octets
kts512to1023Octets
1023Octets
kts1024to1518Octets
o1518Octets
12.2.2. etherHistoryHighCapacityTable
Pkts
Octets
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.
12.3.1. priAlarmTable
13. A3COM-HUAWEI-FLASH-MAN-MIB
This Mib supplies the information for the management of flash devices.
13.1. h3cFlashDevice
13.1.1. h3cFlhSupportNum
13.1.2. H3cFlashTable
flash:
13.1.3. H3cFlashChips
13.1.4. h3cFlashPartitions
For a given flash indexed by h3cFlhIndex, if it cannot be partitioned, there is only one instance
in this table.
13.1.5. huaweiFlhFileTable
The table contains the files in a given partition of a flash, including the hidden files.
13.2. H3cFlashOperate
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.
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.
1: opInProgress(1)
2: opSuccess(2)
10: opDeviceError(10)
12: opDeviceFull(12)
13: opFileOpenError(13)
14: opFileTransferError(14)
16: opNoMemory(16)
19: opUnknownFailure(19)
1: opInProgress(1)
2: opSuccess(2)
3: opInvalidOperation(3)
7: opInvalidServerAddress(7)
10: opDeviceError(10)
12: opDeviceFull(12)
13: opFileOpenError(13)
14: opFileTransferError(14)
16: opNoMemory(16)
17: opAuthFail(17)
19: opUnknownFailure(19)
1: opInProgress(1)
2: opSuccess(2)
20:opDeleteFileOpenError(20),
21:opDeleteInvalidDevice(21),
22:opDeleteInvalidFunction(22),
23:opDeleteOperationError(23),
24:opDeleteInvalidFileName(24),
25:opDeleteDeviceBusy(25),
26:opDeleteParaError(26),
27:opDeleteInvalidPath(27)
13.2.1. h3cFlhOpTable
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 the flash index in a unit. For example, the first flash in the unit1 which has
the entity index of 2 may be defined as 131073(0x20001).
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.
14. 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.
This group defines a collection of objects for management of configuration event log. This
group contains six scalar objects and a table.
14.1.2. h3cCfgLogTable
14.2.1. h3cCfgOperateTable
h3cCfgOperateFileName read-create No
The value must be specified when
h3cCfgOperateType is ‘Net2Startup’,
‘Net2Running’ or ‘Running2Net’ .
transfers.
applicable.
14.
h3cCfgOperateServerAdd read-create No As per MIB
ress
h3cCfgOperateUserName read-create No As per MIB
h3cCfgOperateUserPass read-create No As per MIB
word
h3cCfgOperateEndNotific read-create No As per MIB. Default value is false
ationSwitch
h3cCfgOperateRowStatus read-create No As per MIB. All the status are
supported.
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, and zero are invalid.
14.2.2. h3cCfgOperateResultTable
15. A3COM-HUAWEI-SYS-MAN-MIB
15.2. h3cSysCurTable
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.
a) h3cSysReloadScheduleTable
NOTE:
h3cSysReloadEntity: The value of this object is the entity index which depends on the
implementation of ENTITY-MIB. h3cSysReloadRowStatus: CreatAndGo and CreatAndWait
operations are supported.
15.3. h3cSysImageTable
31 15 0
Entity index Image file index
For Aragog, the entity index is the entPhysicalIndex of Unit as defined in the entPhysicalTable.
Other values are invalid.
15.4. h3cSysCFGFileTable
31 15 0
Entity index Configuration file
index
For Aragog, the entity index is the entPhysicalIndex of Unit as defined in the entPhysicalTable.
Other values are invalid.
15.5. h3cSysBtmLoadTable
Terms
(The terms listed below are just used in the range of this section.)
BootRom: a special program which is used to boot the system on system startup.
Bootrom file: a file which exists in file system. The content of such file is BootRom.
Function
The responsibility of this table is to update BootRom from a BootRom file in file system
to BOOT ROM.
It assumes that the source Bootrom file already exists in the file system of the device
before doing operation. On system startup, this table is empty.
Notes
1) Be careful that the operation on BOOT ROM updating is risky. Other operations may
halt during updating BOOT ROM. Such operation may take a long time as well.
4) It is strongly recommended that the name of a Bootrom file ends with “.btm”, but this
table will not check whether a Bootrom file ends with “.btm”. The verification of validity of a
Bootrom file will be performed after the h3cSysBtmRowStatus of this instance turns into
‘active’.
5) If h3cSysBtmFileName of the instance includes a path, that path must refer to the
same device identified by ‘entityIndex’ part of h3cSysBtmLoadIndex of the instance. If
h3cSysBtmFileName includes just a filename without a path, the root directory will be
used internally.
The Boot Rom in BOOT ROM can not be removed through h3cSysBtmLoadTable, but it
can be updated through this table.
When removing an instance from this table, there is no any deletion of the
corresponding file in file system.
After updating a Bootrom file into BOOT ROM, the corresponding file can be removed
from the file system, but it is not the responsibility of this table to remove a Bootrom file
from the file system.
Examples
A valid Bootrom file named with “s4e01_06.btm” is supposed existing in file system.
h3cSysBtmFileName.131073 = “s4e01_06.btm”
h3cSysBtmFileType.131073 = ‘main’
h3cSysBtmRowStatus.131073 = ‘createAndGo’
15.6. Notifications
16. A3COM-HUAWEI-LswIGSP-MIB
17. A3COM-HUAWEI-LswDHCP-MIB
17.1. hwLswDhcpMib
17.1.1. hwLswDhcpMibObject
17.1.1.1. hwDhcpGroupTable
17.1.1.2. hwDhcpSecurityTable
17.1.1.3. hwDhcpToL3IfTable
18.1. IEEE8023-LAG-MIB
18.1.1.1. dot3adAggTable
18.1.1.2. dot3adAggPortListTable
18.1.2.1. dot3adAggPortTable
18.1.3. dot3adAggPortStatsTable
18.1.3.1. dot3adAggPortDebugTable
18.1.4. dot3adTablesLastChanged
18.2. A3COM-HUAWEI-LAG-MIB
18.2.1. hwAggLinkTable
18.2.2. hwAggPortTable
18.2.3. hwAggResourceAllocationValue
19. IEEE8021D-STP-MIB
19.1. dot1dStpPortTable
19.2. dot1dStpGlobalTable
20. . A3COM-HUAWEI-LswMSTP-MIB
20.2. hwdot1sVIDAllocationTable
default value is 0.
20.3. hwdot1sInstanceTable
stLow
stHigh
Low
High
20.4. hwdot1sPortTable
Type
oint
21.1.1.1. OverViews
entityPhysicalTable describe the relationship of all the entities and other useful information
corresponding to them.
PhysicalClass:
SYNTAX INTEGER {
other(1),
unknown(2),
chassis(3),
backplane(4),
powerSupply(6),
fan(7),
sensor(8),
port(10),
chassis unit
stack fabric
slot container
subslot container
Entity relations:
-->SubSlot-->SubCard-->Port
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 are completely numbered.
Fabric
1
Unit 1
3 4 5 6
14 15 16
Port Port
Port
45 46
17 44
The Aragog products have 2 slots, 1 power, 2 fans, 1 board per slot per unit, 28 ports per
board at most. The following table shows the index range of each physical class of each
unit for 4200G 24-port. “Port on subcard” changed to “stack port” if this port is used to
connect between units.
For Aragog 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
products
below.
powersupply,submodule.
ENT_PHY_UNKNOWN,/*2*/not
supported
ENT_PHY_CHASSIS,/*3*/--unit
ENT_PHY_BACKPLANE,/*4*/ not
supported
ENT_PHY_CONTAINER,/*5*/slot
(container leve2)
ENT_PHY_POWERSUPPLY,/*6*/
supported
ENT_PHY_FAN,/*7*/ supported
ENT_PHY_SENSOR,/*8*/ not
supported
ENT_PHY_MODULE,/*9*/board (in
ENT_PHY_PORT,/*10*/ supported
ENT_PHY_STACK/*11*/--fabric
powersupply
read.
read-only.
read-only.
In the following table, if the entity is virtual, all objects except “entPhysicalContainedIn” and
“entPhysicalParentRelPos” are meaningless to that entity.
21.1.1.3.1. entPhysicalDescr
entity entPhysicalDescr
3Com OS V3.02.00s56c01”
3Com OS V3.02.00s56c01”
3Com OS V3.02.00s56c01”
‘cXX’ stands for development build number. For first one, it is ‘c01’.
PowerSupply PSU
Fan FAN
21.1.1.3.2. entPhysicalVendorType
Slot null
SubSlot null
PowerSupply h3cevtPowerSupplyAC
Fan h3cevtNonHotSwapFan
Board null
h3cevtPortSw-1000BaseTx, h3cevtPortSw-1000BaseLxSm,
h3cevtPortSw-1000BaseSxMm, h3cevtPortSw-1000BaseCx,
h3cevtPortSw-1000BaseZenithFx, h3cevtPortSw-1000BaseLongFx,
h3cevtPortSw-100MMultimodeFx, h3cevtPortSw-100M100BaseTx,
h3cevtPortSw-1000BaseZenithFx, h3cevtPortSw-1000BaseLongFx,
h3cevtPortSw-Combo1000BaseLx, h3cevtPortSw-Combo1000BaseSx,
h3cevtPortSw-Combo1000BaseZx, h3cevtPortSw-1000BASE-MM-SFP,
h3cevtPortSw-1000BASE-T-AN-SFP, h3cevtPortSw-XFP-10GBASE-SR,
h3cevtPortSw-XFP-10GBASE-LR, h3cevtPortSw-XFP-10GBASE-ER,
h3cevtPortSw-XFP-10GBASE-SW, h3cevtPortSw-XFP-10GBASE-LW,
h3cevtPortSw-XFP-10GBASE-EW, h3cevtPortSw-XFP-10GBASE-CX4,
h3cevtPortSw-XFP-10GBASE-LX4, h3cevtPortSw-XPK-10GBASE-SR ,
h3cevtPortSw-XPK-10GBASE-LR , h3cevtPortSw-XPK-10GBASE-ER,
h3cevtPortSw-XPK-10GBASE-SW, h3cevtPortSw-XPK-10GBASE-LW,
h3cevtPortSw-XPK-10GBASE-EW, h3cevtPortSw-XPK-10GBASE-CX4,
h3cevtPortSw-XPK-10GBASE-LX4,
h3cevtPortSw-XPK-NOCONNECTOR , h3cevtPortSw-XFP-UNKNOWN,
h3cevtPortSw-SFP-NO-CONNECTOR,
h3cevtPortSw-SFP-UNKNOWN-CONNECTOR,
h3cevtPortSw-XFP-NO-CONNECTOR.
Fabric null
21.1.1.3.3. entPhysicalContainedIn
Unit None
Slot None
SubSlot None
PowerSupply None
Fan None
Board None
SubCard None
Port None
Fabric None
21.1.1.3.4. entPhysicalClass
entity entPhysicalClass
Unit chassis(3)
Slot container(5)
SubSlot container(5)
PowerSupply PowerSupply(6)
Fan fan(7)
Board module(9)
SubCard module(9)
Port Port(10)
Fabric stack(11)
21.1.1.3.5. entPhysicalParentRelPos
Unit None
Slot None
SubSlot None
PowerSupply None
Fan None
Board None
SubCard None
Port None
Fabric None
21.1.1.3.6. entPhysicalName
Unit “Unit1”
Fabric Fabic
21.1.1.3.7. entPhysicalHardwareRev
Slot None
SubSlot None
SubCard None
Port None
Fabric None
21.1.1.3.8. entPhysicalFirmwareRev
Unit BootRomVersion
Slot None
SubSlot None
PowerSupply None
Fan None
SubCard None
Port None
Fabric None
21.1.1.3.9. entPhysicalSoftwareRev
V3.02.00s168c02
Slot None
SubSlot None
PowerSupply None
Fan None
Board None
SubCard None
Port None
Fabric None
21.1.1.3.10. entPhysicalSerialNum
entity entPhysicalSerialNum
Slot None
SubSlot None
PowerSupply None
Fan None
SubCard none
Port SFP (that is optical module) may have serial number which is
string.
Fabric None
21.1.1.3.11. entPhysicalMfgName
Slot None
SubSlot None
Board None
Port None
21.1.1.3.12. entPhysicalModelName
chassis
Slot None
SubSlot None
PowerSupply none
Fan none
SubCard none
Port None
Fabric None
21.1.1.3.13. entPhysicalAlias
entity entPhysicalAlias
Unit None
Slot none
SubSlot None
PowerSupply None
Fan None
Board None
SubCard None
Port None
Fabric none
21.1.1.3.14. entPhysicalAssetID
entity entPhysicalAssetID
Unit None
Slot None
SubSlot None
PowerSupply None
Fan None
Board None
SubCard None
Port None
Fabric None
21.1.1.3.15. entPhysicalIsFRU
entity entPhysicalIsFRU
Unit True(1)
Slot False(2)
SubSlot False(2)
PowerSupply True(1)
Fan True(1)
Board False(2)
SubCard True(1)
Fabric False(2)
21.1.1.4. Example
Aragog 4200G 24-port: has 3 subcards, 1 powers and 2 fans, each subcard has a maximum of
28 ports(28 ports on Front panel, 1 ports for each subcard), here front panel is regared as
subcard0.
Powersupply1 8 powerSupply(6) 4 1
Powersupply2 9 powerSupply(6) 5 1
fan1 10 fan(7) 6 1
… … port(10) 14 …
21.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
the entityIndex is the index of the entity, same as the entPhysicalIndex in Entity MIB.
21.1.1.5.2.2. entRelationType
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...
21.1.1.5.2.3. relatedEntityIndex
relatedEntityIndex is the entity index that entityIndex related to, same as the
entPhysicalIndex in Entity MIB.
21.1.1.5.3. examples
29 2 30
We regard that board and subcard are all “module” in RFC2737. So NMS cannot
distinguish a board from a subcard by reading MIB nodes—“entPhysicalClass”. We
designed the following way to distinguish them.
Explanation in detail:
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.
21.2. A3COM-HUAWEI-ENTITY-EXT-MIB
This mib includes the general environment information of the device, which is an extension of
entity mib defined in RFC2737.
21.2.1. H3cEntityExtStateTable
in ENTITY-MIB
hreshold
this node.
Normal (2)
POST failure(3)
POE error(4)
stack error(5)
entityAbsent(4)
poeError(11)
stackError(21)
sfpRecvError(31)
sfpSendError(32)
sfpBothError(33)
fanError(41)
psuError(51
rpsError(61)
moduleFaulty(71)
subcard)
SubSlot)
us (R/W) or disabled)
is state of
board/sub
card
hwEntityStandbySt N N N Y N N N
atus (R)
hwEntityAlarmLight N N N N N N N
(R)
hwEntityCpuUsage N N N Y N N N
(R)
hwEntityCpuUsage N N N Y N N N
Threshold (R/W)
hwEntityMemUsag N N N Y N N N
e (R)
hwEntityMemUsag N N N Y N N N
eThreshold(R/W)
hwEntityMemSize N N N Y N N N
(R)
of the
unit
hwEntityTemperatu N N N N N N N
re (R)
hwEntityTemperatu N N N N N N N
reThreshold (R/W)
hwEntityVoltage(R) N N N N N N N
hwEntityVoltageLo N N N N N N N
wThreshold(R/W)
hwEntityVoltageHig N N N N N N N
hThreshold(R/W)
hwEntityExtCriticle N N N N N N N
TempertatureThres
hold(R/W)
of the of this
unit unit
N N N N Y Y Y
h3cEntityExtErrorSt
atus(R)
21.3. A3COM-HUAWEI-ENTRELATION-MIB
The MIB describles the relationship of two physical entities: stacking ports and combo pairs.
Aragog only supports combo ports.
21.3.1. h3cEntRelationTable
22. A3COM-HUAWEI-LswMAM-MIB
-1 Blackhole mac-address
-1 Static mac-address
sible
23. A3COM-HUAWEI-TRNG-MIB
This mib is being applied for and may be changed before the final draft.
23.1. hwTrngCreateTimerangeTable
create an instance
23.2. hwTrngAbsoluteTable
create an instance
23.3. hwTrngPeriodicTable
create an instance
24. A3COM-HUAWEI-LswQos-MIB
24.2. hwQueueTable
24.3. hwRateLimitTable
24.4. hwPriorityTable
operation.
operation.
operation.
ity
ity
24.5. hwPortTrustTable
overcastDSCP(2) and
meaningless
24.6. hwRemarkVlanIDTable
24.7. hwRedirectTable
24.8. hwStatisticTable
24.9. hwMirrorTable
24.10. hwPortMirrorTable
24.11. hwLineRateTable
24.12. hwBandwidthTable
24.13. hwRedTable
24.14. hwMirrorGroupTable
24.15. hwMirroringGroupMirrorMacTable
24.16. hwMirroringGroupMirrorVlanTable
24.17. hwFlowtempTable
24.18. hwFlowtempEnableTable
24.19. hwTrafficShapeTable
24.20. hwPortQueueTable
24.21. hwDropModeTable
24.22. hwWredTable
24.23. hwCosToLocalPrecedenceMapTable
24.24. hwCosToDropPrecedenceMapTable
24.25. hwCosToDscpMapTable
24.26. hwDscpToLocalPreMapTable
24.27. hwDscpToDropPreMapTable
24.28. hwDscpToCosMapTable
24.29. hwDscpToDscpMapTable
24.30. hwDscpMapTable
24.31. hwExpMapTable
24.32. hwLocalPrecedenceMapTable
24.33. hwPortWredTable
25. A3COM-HUAWEI-ACL-MIB
25.1. H3cAclMode
25.2. h3cAclNumGroupTable
ACL
number’ed ACL
state:CreateAndGo,Active,Destroy.
25.3. h3cAclBasicRuleTable
25.4. h3cAclAdvancedTable
25.5. h3cAclIfRuleTable
available.
is available.
25.6. h3cAclLinkTable
26.1. IEEE8021-PAE-MIB
26.1.2. dot1xPaePortTable
FALSE.
26.1.3. dot1xAuthConfigTable
26.1.4. dot1xAuthStatsTable
26.1.5. dot1xAuthSessionStatsTable
26.2. A3COM-HUAWEI-8021PAE-MIB
26.2.2. hwdot1xAuthConfigExtTable
26.3. A3COM-HUAWEI-PORT-SECURITY-MIB
3FC 407R will be add in this MIB. Now the objects are not confirmed by JV engineers.
They will be added to this MIB after being confiemed.
h3cSecurePortVlanMembershipLis accessible-for-
No As per MIB
t notify
h3cSecureRalmAuthServerTimeou
read-write Yes As per MIB
tTime
26.3.2. h3cSecureRalmGroup
h3cSecureRalmDefaultSessionTi
read-write Current Not Supported
me
Writing a MAC
causes an immediate
on line, it silently
object is meaningless
26.3.3. h3cSecurePortTable
The h3cSecurePortTable defines the security status of each secure port. Each port can have a number of
authorized MAC addresses.
The value of
be supported.
other value.
read-writ
h3cSecureNeedToKnowMode Current As per MIB
e
The value of
read-writ
h3cSecureIntrusionAction Current allowDefaultAccess will not
e
be supported.
read-writ
h3cSecureNumberAddresses Current As per MIB
e
h3cSecureNumberAddressesStore read-onl
Current As per MIB
d y
read-onl
h3cSecureMaximumAddresses Current As per MIB
y
26.3.4. h3cSecureOUITable
The h3cSecureOUITable stores the OUI values for OUI based authorization.
and 16.
26.3.5. h3cSecureBindingTable
This table stores the elements of a binding rule include the MAC addresses , the IP address
and the port.
h3cSecureBindingRowStatu
read-create Current As per MIB
s
26.3.6. h3cSecureAssignTable
authorization information on
3 is untagged.
Note: When a port assigned into one vlan by radius server, it can be found in
hwdot1qVlanMIBTable.
For an “access” port, no matter what vlan it belonged to, after radius server assigned vlan
and the user logon using this port, it will be in the vlan assigned by the radius server, and
never belong to the vlan before. If the user logout, this port will recover automatically. For
a “hybrid” or “trunk” port, after radius server assigned vlan and the user logon network
using this port, it will be both in the vlan assigned by radius server and the original vlans. If
the user logout, this port will recover automatically.
27.1. RADIUS-ACC-CLIENT-MIB
radiusAccClientInvalidServerAddre
read-only No As per MIB
sses
27.1.2. radiusAccServerTable
As per MIB
servers.
radiusAccClientMalformedRespon
read-only No As per MIB
ses
27.2. RADIUS-AUTH-CLIENT-MIB
27.2.2. radiusAuthServerTable
ssions
Responses
27.3. A3COM-HUAWEI-RADIUS-MIB
27.3.1. h3cRdInfoTable
not-accessib
h3cRdGroupName Yes As per MIB
le
standard(0) and
h3cRdServerType read- create Yes extendedtype(4) are
supported on Monza.
27.3.2. h3cRdAccInfoTable
not-accessib
h3cRdAccGroupName Yes As per MIB
le
h3cRdAccSaveStopPktEnabl
read- create Yes As per MIB
e
27.3.3. h3cRadiusAccServerTable
h3cRadiusAccClientStartReq
read-only No As per MIB
uests
h3cRadiusAccClientStartRes
read-only No As per MIB
ponses
h3cRadiusAccClientInterimR
read-only No As per MIB
equests
h3cRadiusAccClientInterimR
read-only No As per MIB
esponses
h3cRadiusAccClientStopReq
read-only No As per MIB
uests
h3cRadiusAccClientStopRes
read-only No As per MIB
ponses
Name Description
h3cRadiusAuthServerD
As per MIB
ownTrap
h3cRadiusAccServerDo
As per MIB
wnTrap
This section contains a list of the traps defined in the standard MIB(defined by IETF or IEEE).
This section contains a list of the traps defined in the private MIB(defined by enterprise).
2006-04-14 Page146, Total
Confidential Information of H3C.
203
No Spreading without Permission
Aragog MIB Companion Secret
tion
sholdNotification
holdNotification
sholdNotification
oldNotfication
holdNotification
ureThresholdNotification
MIB
-MIB
-MIB
owerToNormal
igherToNormal
speed.
inactive
secureAddressLearned A3COM-HUAWEI-PORT-SECURITY-M
As per MIB
IB
h3cSecureViolation A3COM-HUAWEI-PORT-SECURITY-M
As per MIB
IB
A3COM-HUAWEI-PORT-SECURITY-M
h3cSecureLoginFailure As per MIB
IB
A3COM-HUAWEI-PORT-SECURITY-M
h3cSecureLogon As per MIB
IB
A3COM-HUAWEI-PORT-SECURITY-M
h3cSecureLogoff As per MIB
IB
failed.
packets.
generated when a
superior BPDU.
aged out.
VLAN
ered
29. A3COM-HUAWEI-HGMP-MIB
Duplex
ed
29.11. hgmpWhitelistTable
29.12. hgmpWhitelistNbTable
29.13. hgmpBlacklistTable
29.14. hgmpMemberPriPortTable
30. A3COM-HUAWEI-VOICE-VLAN-MIB
30.2. h3cvoiceVlanOuiTable
30.3. h3cvoiceVlanPortTable
31. A3COM-HUAWEI-QOS-PROFILE-MIB
31.1. QosProfObjects
31.1.1. QosProf
The row can not be modified, Reset the row must undo the row first;
31.1.2. QosActions
31.1.2.1. QosTrafficLimitTable
2006-04-14 Page160, Total
Confidential Information of H3C.
203
No Spreading without Permission
Aragog MIB Companion Secret
31.1.2.2. QosTrafficPriorityTable
cp
alPre
pPriority
31.1.2.3. QosTrafficFilterTable
31.1.3. QosProfPortMapping
31.1.3.1. QosProfPortMappingTable
31.1.3.2. QosProfPortMappingModeTable
31.1.3.3. QosProfDynMappingTable
me
31.2. QosProfPortMappingTraps
32. A3COM-HUAWEI-UI-MAN-MIB
32.2. h3cUIMgtBasicGroup
ndex ble
way ble
33. DISMAN-PING-MIB
Ping Algorithm:
pingCtlRowStatus createAndGo(4)
pingResultsOperStatus
pingResultsIpTargetAddress
pingResultsMinRtt
pingResultsMaxRtt
pingResultsAverageRtt
pingResultsProbeResponses
pingResultsSentProbes
pingResultsRttSumOfSquares
33.1. pingNotifications
can be generated.
testCompletion(4).
33.3. pingCtlTable
name)
must be IPV4, it is 1.
must be IPV4, it is 1.
33.4. pingResultsTable
pe
33.5. pingProbeHistoryTable
34. POWER-ETHERNET-MIB
34.1. pethPsePortTable
34.2. pethMainPseTable
34.3. pethNotificationControlTable
34.4. Trap
35. A3COM-HUAWEI-POWER-ETH-EXT-MIB
35.1. h3cPsePortTable
35.2. h3cMainPseTable
35.3. h3cPsePortTable
36. A3COM-HUAWEI-DISMAN-PING-MIB
36.1. hwPingAgentEnable
able
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
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
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
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.
The min bandwidth for rate control is 64kbps and the min step is 64kbps
Port mirroring with only one monitor-port and all the other port as mirroring-port
About resource restrictions please refer to product specification section 5.1 performance
summary table.
All configurations can be stroed in configuration file. No special design is to backup the
device’s ip address, default gateway or subnet mask.
The Aragog products do not keep a shadow of mac address table so this requirement is not
met with.
If the administrator transfers one configuration file of 48ports 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.
The Aragog products do not support 3com private backup and restore mibs. Please refer
section 13 A3COM-HUAWEI-SYS-MAN-MIB.
39. A3COM-HUAWEI-LPBKDT-MIB
accessible-for-
h3cLpbkdtVlanID No The ID of VLAN
notify
40. A3COM-HUAWEI-LLDP-EXT-MIB
40.2. h3clldpPortConfigTable
le
Status
‘c01’.
pingMib
pingMib ortAge
pingMib eTime
pingMib e
42. A3COM-HUAWEI-DOMAIN-MIB
42.2. h3cDomainInfoTable
42.3. h3cDomainSchemeTable
1) when a domain was created, the agent will create a row for accounting, a row for authentication, a
row for authorization with the value of h3cDomainSchemeMode be ‘local’.
h3cDomainSchemeMode
h3cDomainSchemeAAAType
h3cDomainSchemeAAAName
h3cDomainSchemeAccessMode: Only support ‘default’, other values is invalid.if the item is not
specified, the default value is ‘default’.
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.
SchemeMode
Local TRUE ⅹ ⅹ
Radius+Local TRUE ⅹ ⅹ
Hwtacacs+Local TRUE ⅹ ⅹ
If h3cDomainSchemeMode is
h3cDomainSchemeAAAName
h3cDomainSchemeAAAName
43. A3COM-HUAWEI-IF-EXT-MIB
43.2. h3cIfStatTable
43.3. h3cIfSpeedStatTable
When updating a single device or the command switch in cluster, use the device’s IP and
port 161 as usual to connect with SNMP. When updating a member switch in cluster, the
IP of command switch will be used, and the UDP Port of SNMP packet defined as below:
15 11 10 0
++++++++++++++++++++++++++++++
++++++++++++++++++++++++++++++
For example, the command switch’s IP address is 10.1.1.1, and the cluster member’s
number is 2. To access the member switch, the IP address and UDP Port 10.1.1.1/49154
will be used.
set to FTP or TFTP; and h3cFlhOperServerAddress must be set to the ftp/tftp server’s IP
address.
A3COM-HUAWEI-HGMP-MIB
A3COM-HUAWEI-FLASH-MAN-MIB
A3COM-HUAWEI-SYS-MAN-MIB
ENTITY-MIB
44.1.4. An example:
Having got the proper files from ftp/tftp server by SNMP, you may want to upgrade a single
device or devices in cluster.
1. 3NS first walks h3cSysImageTable to get which file is main image file and which one is
backup image file. Assume that “s3t03_01_00s56c01.app” is main image,
“s3t03_01_00s56c01.app” is backup image and “s3t03_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.
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’.
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
For Aragog, only ‘main’ ‘backup’and ‘none’ values of h3cSysImageType are supported.
The maximum entries in this table are limited by the space of flash. Now image file size of
Aragog will be controlled to about 4.0M. Flash space is 16M. For this product, there are
normally 2 image files in flash and one web interface image, thus h3cSysImageTable has
about 2*4=8 entites.
31 15 0
+++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++
3. 3NS uses h3cFlhOperTable to download the new image file to the fabric and
overwrites the an existed image file (here existed file is “s3t03_01_00s56c02.app”) by
setting h3cFlhOperDestinationFile to that existed file name.
h3cFlhOperType.65537 net2FlashWithErase(1)
clustertftp(4) (for
member of cluster)
h3cFlhOperServerAddress.65537 10.153.70.110
h3cFlhOperSourceFile.65537 “s551_02.bin”
h3cFlhOperDestinationFile.65537 “s3t03_01_00s56c02.ap
p”
h3cFlhOperEndNotification.65537 True(1)
h3cFlhOperRowStatus.65537 1
Here the h3cFlhOperIndex with 65537 means that the image file of “s551_02.bin” will be
downloaded and renamed as “s3t03_01_00s56c02.app” to the device.
31 15 0
+++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++
H3cSysReloadEntity.1 2
h3cSysReloadCfgFile.1 0
H3cSysReloadImage.1 131074
H3cSysReloadReason.1 “Upgrade”
H3cSysReloadScheduleTime.1 “”
H3cSysReloadScheduleTagList.1 “3Com-Network-Supervisor”
H3cSysReloadRowStatus.1 Active
Here, H3cSysReloadImage.1 = 131074 = 2 * 216 +2; that is unit1’s 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. 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.
8. 3NS then will ask the agent to reload the default image. It sets the reload action to
reboot at once for the device.
H3cSysReloadTag.0 “3Com-Network-Supervisor”
H3cSysReloadAction.0 reloadAtOnce(3)
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 device.
This MIB changes to the new version number when the device has rebooted.
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 upgrade fail, or device do not reboot. 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.
A3COM-HUAWEI-CONFIG-MAM-MIB
ENTITY-MIB
44.2.3. An example:
Here we will discuss the action of backup and restore.
The following table is the result of a set operation of creating an instance in the entry. The
operation will restore the configuration stored in BackupCfg.cfg from the server
(10.153.70.110) to the unit1 by using tftp.
NAME VALUE
h3cCfgOperateType.3 net2Startup(5)
h3cCfgOperateFileName.3 BackupCfg.cfg
h3cCfgOperateEndNotificationSwitch. 3 True(1)
h3cCfgOperateRowStatus. 3 Active(1)
To save the configuration of the fabric from memory to flash, the following is an example
(with the index of 0x0000001).
NAME VALUE
h3cCfgOperateType.1 running2Startup(1)
h3cCfgOperateFileName.1 myConfig.cfg
h3cCfgOperateEndNotificationSwitch.1 True(1)
h3cCfgOperateRowStatus.1 Active(1)
With the result of this operation, an instance will be added to the h3cSysCFGFileTable of
A3COM-HUAWEI-SYS-MAN-MIB.
Getting the fabric configuration file from device (backup saved configuration) (with the
index of 0x0000002):
NAME VALUE
h3cCfgOperateType.2 startup2Net(6)
h3cCfgOperateFileName.2 BackupCfg.cfg
h3cCfgOperateEndNotificationSwitch.2 True(1)
h3cCfgOperateRowStatus.2 Active(1)
2. Ensure there is and row for each entity we want to reboot (the
h3cSysReloadRowStatus //createAndGo
and:
operation)
"3Com-Network-Supervisor"
h3cSysReloadAction to reloadAtOnce(3)
Comments: all the mibs are based on the current platform, not the latest
RFC.
Comments: ok
Comments: ok
Comments: ok
Where an 3fc-510 MIB does not exist on a device, this MIB should be
implemented in preference to creating a new private MIB
Where new private MIBs are used, the same private MIB should be
implemented on all JV-CO devices (where applicable)
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.
[Quidway]display version
(b) The trap source will be set to to the IP address which was used to make
the SNMP request;
(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:
Comments: agree
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.
3com requirement:
Comments: ok
Comments: ok
If the power supply (AC or RPS) fails the software can detect the error
and report it.
If the fan stops rotation the software can detect and report.
If the temperate of PSU on POE device is over the setting the software
can detect it and report it.
The CLI commands are based on bedrock platform and it is similar with
Monza products.
The RFC 2674 is supported but the ip routing configuration mib will keep
unchanged.
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.
The specific traps when the user logs on/logs off are based on bedrock
platform.
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
Ok.
Text file Release Notes must be installed and displayed during installation for
both products.
Comments: The above requirement can not be met with. The release not can
not shown when downloading a software image to flash.
In plan phase, 3com will join the discussion about the feature design.
OK
About the common bugs, the bug will be fixed on the platform and each
products will take new released platform code to release patches.
Comments: Agreed, the RM and SM can be installed in any order, but they
can’t be de-installed separately
The quidview and web interface will also have a software version number,
just like x.xx;
About the consistency between SM and RM, the bedrock will do our best to
realize it, but we don’t 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 F1.
The RADIUS protocol configuration is performed based on a RADIUS scheme basis. First,
you should create a new RADIUS scheme and configure it correctly. Every scheme’s
name is unique. For example, we want to create a scheme which name is
“radius.pqe.com”, so h3cRdGroupName =
14.114.97.100.105.117.115.46.112.113.101.46.99.111.109.
scheme which we want to create is existed. If it existed, please go to step III, If not,
radius scheme row for authentication server, An h3cRdAccInfo Table entry is also
created simultaneously.
III.For h3cRdGroupName= radius.pqe.com, please fill in the value which shows the
h3cRdInfoTable.h3cRdGroupName.h3cRdPrimUdpPort = 1812,
h3cRdInfoTable.h3cRdGroupName.h3cRdSecUdpPort = 1812,
h3cRdInfoTable.h3cRdGroupName.h3cRdKey <password>
h3cRdInfoTable.h3cRdGroupName.h3cRdPrimAuthIpAddrType ipv4(1)
h3cRdInfoTable.h3cRdGroupName.h3cRdPrimAuthIpAddr InetAddress,
h3cRdInfoTable.h3cRdGroupName.h3cRdSecAuthIpAddrType ipv4(1)
h3cRdInfoTable.h3cRdGroupName.h3cRdSecAuthIpAddr InetAddress,
h3cRdInfoTable.h3cRdGroupName.h3cRdServerType extended(4)
h3cRdInfoTable.h3cRdGroupName.h3cRdUserNameFormat withoutdomain(1)
h3cRdAccInfoTable.h3cRdAccGroupName.h3cRdPrimAccIpAddr = InetAddress
h3cRdAccInfoTable.h3cRdAccGroupName.h3cRdSecAccIpAddr = InetAddress
h3cRdAccInfoTable.h3cRdAccGroupName.h3cRdAccKey = <password>
An Internet service provider (ISP) domain is a group of users who belong to the same ISP.
In a multi-ISP environment, the users connected to the same access device may belong
to different domains. Every domain have unique name.
To determine whether the domain which we want to create is existed or not.. If it existed,
please go to step III.If not, please go to next step.,
h3cDomainTable.h3cDomainName.h3cDomainState = active(1)
h3cDomainTable.h3cDomainName.h3cDomainRowStats = CreateAndGo(4)
when a domain has been created , there are three entries will be added to the
h3cDomainSchemeTable.
h3cDomainSchemeMode = local(2)
h3cDomainSchemeAAAType = authentication(2)/authorization(3)/accounting(1)
h3cDomainSchemeAAAName.X = h3cRdGroupName
h3cDomainSchemeMode.X = radius(3)
h3cDomainSchemeAAAType.X = h3cDomainSchemeAAAType.X
Set :
h3cDomainDefault = h3cDomainName.
If a user logon the device that its name has no “@<domain name>” suffix, the user will
belong to the specified default domain, else he will belong to the specified domain which
come from suffix.
Set :
h3cDomainVlanAssignMode = string(2)
Set :
h3cSecureRalmAuthMode = papUserNameFixed(2)
46. Appendix