Datatek UMI - Manual (Page 37)

U N I V E R S A L M E D I A T I O N I N T E R F A C E ( U M I ) U S E R M A N U A L
04/30/09 37
A single or multiple SNMP managers can access the UMI. However, only one SNMP manager
can be predefined as the trap manager. As result of using this command, all traps will be directed
to the chosen trap manager. The
ipaddr field defines the IP address of the SNMP manager to
whom the traps are to be sent. The port field indicates the UDP port on that SNMP manager and
defaults to the standard value of 162. If closed user groups are to be defined on the interface the
cug option allows the association of up to 32 individual groups defined with the
cug command.
The COMM option allows the configuration of a private SNMP community. The public community
is always present per the specification. This option takes effect immediately.
The UMI allows setting of an SNMP community in addition to the public community. The public
community is recognized when the [ PUBLIC=YES ] option is selected. Recognition of the public
community is the default operation. When [ PUBLIC=NO ] is selected, the public community is
not recognized.
The sysContact option allows a non-volatile initialization of the MIB-II sysContact variable. The
MIB-II sysContact variable remains changeable from the SNMP management station. However, it
is initialized to the non-volatile value each time the UMI is rebooted. Setting this option to the
constant none removes the non-volatile initialization of the MIB-II variable. This option takes
effect immediately. However, the non-volatile contents are stored on the DTK41. If a DTK41 is not
installed, the settings are lost on the next reboot. If the UMI is administered via the Datakit
Controller enhanced interface updated for build #21 or later, the DTK41 is not required since the
Datakit controller will apply the settings on each restart.
The sysName option allows a non-volatile initialization of the MIB-II sysName variable. The MIB-
II sysName variable remains changeable from the SNMP management station. However, it is
initialized to the non-volatile value each time the UMI is rebooted. Setting this option to the
constant none removes the non-volatile initialization of the MIB-II variable. This option takes
effect immediately. However, the non-volatile contents are stored on the DTK41. If a DTK41 is not
installed, the settings are lost on the next reboot. If the UMI is administered via the Datakit
Controller enhanced interface updated for build #21 or later, the DTK41 is not required since the
Datakit controller will apply the settings on each restart.
The sysLocation option allows a non-volatile initialization of the MIB-II sysLocation variable. The
MIB-II sysLocation variable remains changeable from the SNMP management station. However,
it is initialized to the non-volatile value each time the UMI is rebooted. Setting this option to the
constant none removes the non-volatile initialization of the MIB-II variable. This option takes
effect immediately. However, the non-volatile contents are stored on the DTK41. If a DTK41 is not
installed, the settings are lost on the next reboot. If the UMI is administered via the Datakit
Controller enhanced interface updated for build #21 or later, the DTK41 is not required since the
Datakit controller will apply the settings on each restart.
5.19 INSTALL ( Software Registration )
Syntax: install [ key=<software key> ]
[ fpkey=<software key>]
The UMI has a unique device software key, and multiple per port feature package keys. This
section is included in the user manual for completeness. Under normal circumstances, only the
mechanized utilities utilize this command. It may be executed manually under an emergency
situation. Depending on the device, the keys may or may not be installed by the factory. The per
port feature package keys my be added at any time, and do not affect the operation of the unit.