|
|
DMI event types are converted, by the mapper, to trap enterprise OIDs. If SNMP does not forward traps, it is often difficult to work out which OID values are being generated; these OID values need to be put into the SNMP configuration files in order to fix the problem. This problem is particularly difficult when dynamically assigned OIDs are used.
The solution to this problem is use of the trap_rece(1Msnmp) application. trap_rece receives and displays all SNMP traps. When SNMP refuses to pass on a trap it generates an ``authentication failure'' trap which contains details of the trap. This can be seen with trap_rece and the OID of the original trap determined.
For an example of how OIDs can be explicitly assigned, see the phonebook sample code in /usr/src/dmi/samples/CI_support/phonebook. If the comment symbols around both
Pragma = SNMP ...statements in phonebook.mif are removed, event2 will cause traps with the assigned OID to be generated.
Dynamically assigned OIDs, generated by the mapper, can have very large OID values. Many SNMP tools and management applications do not handle these correctly and can behave unpredictably. For safe operation it is recommended that OIDs are administratively assigned ( using a pragma statement ) for all groups in the DMI MIF files.