ABSTRACT:
3COM PRODUCTMIB MIBs Modified to Compile with ManageWise MIB Compiler to fix errors defined in Detailed Description
DETAILED DESCRIPTION
CHANGES TO MIBS
1. frm.mib redefined DisplayString and PhysAddress so I removed the redefinitions.
2. ls3k30b2.mib redefined DisplayString, PhysAddress, MacAddress and OwnerString so I removed the redefinitions.
3. ls3k30b2.mib did not have a definition for LsAtmDlConnectionFaultEntry changed to what I thought they meant.
4. ls1k3_02.mib redefined DisplayString, PhysAddress, MacAddress, OwnerString so I removed the redefinitions.
5. Since fms.mib, lsk30b2.mib and ls1k3_02.mib all define PRODUCTMIB, it is impossible to use them all together. I don't understand the intent of the vendor to use the same mib definition in separate files. The customer can only use one at a time depending on the hardware and agent.
lsk30b2.mib is defined as follows:
Product: LinkSwitch 1000 MIB Version: 1.00 The MIB is used in conjunction with version 1.03 (and all previous releases) of the LinkSwitch 1000 agent software.
ls1k3_02.mib is defined as follows:
Product: LinkSwitch 1000 MIB Version: 1.00 Comments: The MIB is used in conjunction with version 1.03 (and all previous releases) of the LinkSwitch 1000 agent software.
fms.mib is defined as follows:
Product: 3Com SuperStack Hub 10 MIB Version: 3.03 Comments: The MIB is used in conjunction with version 3.04 of the FMS agent software, which supports all SuperStack II, FMS, FMS II and 10BT/BTi units. This release is hosted on a 3C16030 FMS Management Module.
Since I do not know what the customer has in the way of software agent and hardware, I cannot know what mib is desired. I picked fms.mib as active, and renamed the others to nop. If one of the others is desired, please let me know which one, and I will rename fms.mib to fms.nop and replace it with the appropriate mib.
| xmws012.exe | 364.7 K | 2005-04-06 |
--devsup
© 2008 Novell, Inc. All Rights Reserved.