Kbase P99716: The Fathom Management SNMP trap does not conform to the definition in the Fathom SNMP MIB
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/22/2008 |
|
Status: Verified
GOAL:
The Fathom Management SNMP trap does not conform to the definition in the Fathom SNMP MIB
FACT(s) (Environment):
Fathom Management 2.x
Fathom Management 3.x
FIX:
The Fathom SNMP MIB file, <fathom>/config/PSC-FM-MIB.txt defines the trap variables used by Fathom Management. There are two fields in the SNMP trap header generated by Fathom Management that do not match what would be expected from inspecting the MIB definition.
1) The fmgenTrap entry in the MIB has an ENTERPRISE field with a value of fmv20a. This indicates that Fathom will transmit traps with the Enterprise field of the SNMP header containing the Fathom Management OID
.1.3.6.1.4.1.1730.1.2.1.1
(.iso.org.dod.internet.private.enterprises.progress.products.fathom.management.fmv20a).
Instead Fathom is actually sending traps with the abbreviated OID of
.1.3.6.1.4.1.1730 (.iso.org.dod.internet.private.enterprises.progress).
2) The fmgenTrap entry in the MIB has an identifier of 1. This indicates that the Specific Type field in the SNMP header will contain a 1. Instead the field contains a 6. These errors make it difficult for the receiver to know what to expect. They cause a problem when importing the MIB into frameworks like Tivoli and HP OpenView / HP's Network Node Manager. Products that can generate event receivers based on the MIB definitions will create handlers with information that does not match what is being sent. In HP NNM the expected trap based on the MIB will be .1.3.6.1.4.1.1730.1.2.1.1.0.1 and what is received will be .1.3.6.1.4.1.1730.0.6.
Below is an example dump of a Fathom Management trap showing the SNMP trap header along with the variable bindings sent with the trap. Note the Enterprise and the Specific Type fields.
SNMP Trap PDU
SNMP Version: Version 1
Remote Host: 192.168.1.1
Remote Port: 33508
Community: public
Request ID: 0
Timeout: 0
Retries: 0
Enterprise: .1.3.6.1.4.1.1730
Trap Type: 6
Specific Type: 6
UpTime: 42255
Error Status: no error
SNMP PDU Variable Bindings:
Object ID: .1.3.6.1.4.1.1730.1.2.1.1.2.0
STRING: http://pctest:9090 </exchweb/bin/redir.asp?URL=http://pctest:9090>
Object ID: .1.3.6.1.4.1.1730.1.2.1.1.5.1.0
INTEGER: 1
Object ID: .1.3.6.1.4.1.1730.1.2.1.1.5.2.0
INTEGER: 1
Object ID: .1.3.6.1.4.1.1730.1.2.1.1.5.3.0
INTEGER: 2
Object ID: .1.3.6.1.4.1.1730.1.2.1.1.5.4.0
INTEGER: 27
Object ID: .1.3.6.1.4.1.1730.1.2.1.1.5.5.0
STRING: Fathom Trend Database commits low
The problem can be worked around by adjusting the trap receiver's event handler definitions to expect the data actually being sent. The MIB can be edited to reflect the generated trap /*before*/ importing the MIB into a management framework. To edit the PSC-FM-MIB.txt file, locate the fmgenTrap entry towards the end of the file. Change the following 2 lines:
From:
ENTERPRISE fmv20a
To:
ENTERPRISE progress
From:
::= 1
To:
::= 6
In future releases of Fathom Management, the trap data will be changed to conform to the published MIB.