Gude Expert Power Control 8042 Series, Manual

Page: 68 / 96

68
Expert Power Control 8042 © 2020 GUDE Systems GmbH
Specifications
In older MIB tables, a separate trap was defined for each combination of an event
and a port number. This results in longer lists of trap definitions for the devices. For ex-
ample, from
epc8221SwitchEvtPort1 to epc8221SwitchEvtPort12. Since new firm-
ware versions can generate many more different events, this behavior quickly pro-
duces several hundred trap definitions. To limit this overabundance of trap definitions,
the trap design has been changed to create only one specific trap for each event type.
The port or sensor number is now available in the trap as an index OID within the vari-
able bindings.
In order to recognize this change directly, the "Notification" area in the MIB table has
been moved from sysObjectID.0 to sysObjectID.3. This way, unidentified events are
generated until the new MIB table is imported. For compatibility reasons, SNMP v1
traps are created in the same way as before.
NET-SNMP
NET-SNMP provides a very widespread collection of SNMP command-line tools (snm-
pget, snmpset, snmpwalk etc.) NET-SNMP is among others available for Linux and
Windows. After installing NET-SNMP you should create the device-specific MIB of the
device in NET-SMP share directory, e.g. after
c:\usr\share\snmp\mibs
or
/usr/share/snmp/mibs
So later you can use the 'subtree names' instead of OIDs:
Name:
snmpwalk -v2c -mALL -c public 192.168.1.232 gudeads
OID:
snmpwalk -v2c -mALL -c public 192.168.1.232 1.3.6.1.4.1.28507
NET-SNMP Examples
Query Power Port 1 switching state:
snmpget -v2c -mALL -c public 192.168.1.232 epc822XPortState.1
Switch on Power Port 1:
snmpset -v2c -mALL -c private 192.168.1.232 epc822XPortState.1 integer 1
4.5.1
Device MIB 8042
Below is a table of all device-specific OID 's which can be accessed via SNMP. In the
numerical representation of the OID the prefix " 1.3.6.1.4.1.28507 " (Gude Enterprise
OID) was omitted at each entry in the table to preserve space. The example for a com-
plete OID would be "1.3.6.1.4.1.28507.86.1.1.1.1". A distinction is made in SNMP OID
's in between tables and scalars. OID scalar have the extension ".0" and only specify a
value. In SNMP tables the "x" is replaced by an index (1 or greater) to address a value
from the table.
Name OID Type Acc.
Description
epc8042TrapCtrl .86.1.1.1.1.0 Integer32 RW
0 = off 1 = Ver. 1 2 = Ver. 2c 3 = Ver. 3
epc8042TrapIPIndex .86.1.1.1.2.1.1.x Integer32 RO