The DMI to SNMP mapper for UnixWare 7.

Configuring the mapper

Basic mapper configuration is performed automatically at installation time. Manual configuration may be required to carry out additional tasks.

Forcing SNMP to accept traps from enterprise OIDs other than 412.

The following lines are added to /etc/netmgt/snmpd.peers at installation time. These instruct SNMP to forward traps from the DMTF enterprise OID (412).

   "dmi2snmpd.trapper" "nopassword"
   "dmi2snmpd.commander"   "nopassword"
In addition one line of the following format should be added to snmpd.peers for every other trap enterprise OID you wish to be forwarded:
   "dmi2snmpd.trapper"   <trap enterprise OID>  "nopassword"
If this line is not specified, SNMP will fail to send the trap and the mapper will re-send it with, dynamically generated, OID under dmtf.1.2 (

Forcing SNMP to forward traps to a specific management station.

Add the addresses of the station to which traps are to be sent to the file /etc/netmgt/snmpd.trap. For Example:

   ip public 162

Allowing write access via SNMP

Add the following line to the file /etc/netmgt/snmpd.comm:

   ip public write
you also ensure that dmi is started with the write enable (-w) flag; and you should be aware that, as with any other form of SNMP write access, this exposes your system to a degree of security risk. This can be reduced, but not eliminated, by defining a different community name for such access types, for example:
   ip <new community> write

Filtering traps

The DMI to SNMP standard does not address the SNMP trap filtering issue. This release gives a proprietary solution for this problem. The mapper uses a configuration file /etc/dmi/dmi2snmp.cfg which contains the list of enabled or disabled trap (enterprise or subtree) OIDs. The section ``enable traps'' contains the list of trap OIDs that are to be passed to SNMP agent. All other traps are masked.

The section ``disable traps'' contains the list of trap OIDs that are be masked; all other traps are passed to the SNMP agent. In the case that the configuration file contains both sections, the ``enable traps'' are applied first and ``disable traps'' leads only to the masking of relevant traps.

If there is no configuration file, all traps are passed to SNMP. Examples:

Only DMTF dmiMIBObjects's traps (under are allowed:

   [enable traps]
All DMTF traps (under are disabled:
   [disable traps]
All DMTF traps (under are enabled except
   [enable traps]

   [disable traps]

© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 27 April 2004