SNMP eng: Unterschied zwischen den Versionen

Aus Gude Systems GmbH
Zur Navigation springen Zur Suche springen
 
(7 dazwischenliegende Versionen desselben Benutzers werden nicht angezeigt)
Zeile 1: Zeile 1:
−
[[Datei:SNMP.png]]
+
SNMP can be used for status information via UDP (port 161). Supported SNMP commands are:
−
<br /><u>SNMP-get:</u>Enables the acceptance of SNMP-GET commands.
+
* GET
−
<br /><u>SNMP-set:</u>Allows the reception of SNMP-SET commands.
+
* GETNEXT
−
<br /><u>SNMP UDP Port:</u>Sets the UDP port where SNMP messages are received.
+
* GETBULK
−
<br /><u>sysContact:</u>Value of RFC 1213 sysContact.
+
* SET
−
<br /><u>sysName:</u>Value of RFC 1213 sysName.
+
<br />To query via SNMP you need a Network Management System, such as HP OpenView, OpenNMS, Nagios etc., or the simple command line tools of NET-SNMP software. The device supports SNMP protocols v1, v2c and v3. If traps are enabled in the configuration, the device messages are sent as notifications (traps). SNMP Informs are not supported. SNMP Requests are answered with the same version with which they were sent. The version of the sent traps can be set in the configuration.
−
<br /><u>sysLocation:</u>Value of RFC 1213 sysLocation.
+
 
−
<br /><u>Enable SNMP v2:</u>Activates SNMP v2.
+
='''MIB Tables'''=
 +
<br />The values that can be requested or changed by the device, the so-called "Managed Objects", are described in Management Information Bases (MIBs). These substructures are subordinate to so-called "OID" (Object Identifiers). An OID digit signifies the location of a value inside a MIB structure. Alternatively, each OID can be referred to with its symbol name (subtree name). The device's MIB table can be displayed as a
 +
text file by clicking on the link "MIB table" on the SNMP configuration page in the browser.
 +
 
 +
='''SNMP v1 and v2c'''=
 +
<br />SNMP v1 and v2c authenticates the network requests by so-called communities. The SNMP request has to send along the so-called community public for queries (read access) and the community private for status changes (write access) . The SNMP communities are read and write passwords. In SNMP v1 and v2 the communities are transmitted unencrypted on the network and can be easily intercepted with IP sniffers within this collision domain. To enforce limited access we recommend the use of DMZ or IP-ACL.
 +
 
 +
='''SNMP v3'''=
 +
<br />Because the device has no multiuser management, only one user (default name "standard") is detected in SNMP v3. From the User-based Security Model (USM) MIB variables, there is a support of "usmStats ..." counter. The "usmUser ..." variables will be added with the enhancement of additional users in later firmware versions. The system has only one context. The system accepts the context "normal" or an empty context.
 
<br />
 
<br />
−
<br /> [[Datei:Wichtig_zeichen.png]] Because of security issues, it is advisable to use only SNMP v3, and to disable SNMP v2. Accesses to SNMP v2 are always insecure.
+
<br />'''Authentication '''
 
<br />
 
<br />
−
<br /><u>Community public:</u>The community password for SNMP GET requests.
+
<br />The algorithms "HMAC-MD5-96" and "HMAC-SHA-96" are available for authentication. In addition, the "HMAC-SHA-2" variants (RFC7630) "SHA-256", "SHA-384" and "SHA-
−
<br /><u>Community private:</u>The community password for SNMP SET requests.
+
512" are implemented.  
−
<br /><u>Enable SNMP v3:</u>Activates SNMP v3.
+
<br /> [[Datei: Wichtig_zeichen.png]] "SHA-384" and "SHA512" are calculated purely in software. If "SHA-384" or "SHA- 512" is set on the configuration page, the time for the key generation may take once up to approx. 45 seconds.
−
<br /><u>SNMP v3 Username:</u>The SNMP v3 User Name.
+
<br/>
−
<br /><u>SNMP v3 Authorization Algorithm:</u>The selected Authentication Algorithm.
+
'''Encryption '''
−
<br /><u>SNMP v3 Privacy Algorithm:</u>SNMP v3 Encryption Algorithm..
 
 
<br />
 
<br />
−
<br /> [[Datei:Wichtig_zeichen.png]] If the password mask is redisplayed, only four "bullets" are shown as a symbolic placeholder, since for security reasons the device never stores the password itself, but only the key formed using the Authorization Algorithm. If you want to change a password, the complete password must always be re-entered.
+
<br />The methods "DES", "3DES", "AES-128", "AES-192" and "AES-256" are supported in combination with "HMAC-MD5-96" and "HMAC-SHA-96." For the "HMAC-SHA-2" protocols, there is currently neither RFC nor draft that will allow for cooperation with an encryption.
 +
<br /> [[Datei: Wichtig_zeichen.png]] While in the settings "AES-192" and "AES256" the key calculation is based on "draft-blumenthalphoto-aes-usm-04", the methods "AES 192-3DESKey" and "AES 256-3DESKey" utilize a key generation, which is also used in the "3DES" configuration ("draft-reeder-snmpv3-usm-3desede-00"). If one is not an SNMP expert, it is recommended
 +
to try in each case the settings with and without "...- 3DESKey".
 
<br />
 
<br />
−
<br /> [[Datei:Wichtig_zeichen.png]] The calculation of the password hashes varies with the selected algorithms. If the Authentication or Privacy algorithms are changed, the passwords must be re-entered in the configuration dialog. "SHA-384" and "SHA512" are calculated purely in software. If "SHA-512" is set on the configuration page, the time for the key generation may take once up to approx. 45 seconds.
+
<br />'''Passwords '''
 
<br />
 
<br />
−
<br /><u> Send SNMP traps:</u>Here you can specify whether, and in what format the device should send SNMP traps.
+
<br />The passwords for authentication and encryption are stored only as computed hashes for security reasons. Thus it is, if at all, very difficult to infer the initial password. However, the hash calculation changes with the set algorithms. If the authentication or privacy algorithms are changed, the passwords must be re-entered in the configuration dialog.
−
<br /><u>SNMP trap receiver:</u>You can insert here up to eight SNMP trap receiver.
+
<br />
−
<br /><u>MIB table:</u>The download link to the text file with the MIB table for the device.
+
='''Security '''=
−
<br />More information about SNMP settings are available from our support or can be found
+
<br />
−
on the Internet at www.gude.info/wiki.
+
<br />The following aspects should be considered:
 +
* If encryption or authentication is used, then SNMP v1 and v2c should be turned off. Otherwise the device could be accessed with it.
 +
* If only authentication is used, then the new "HMAC-SHA-2" methods are superior to the MD5 or SHA-1 hashing algorithms. Since only SHA-256 is accelerated in hardware, and SHA-384 and SHA-512 are calculated purely in software, one should normally select SHA-256. From a cryptographic point of view, the security of SHA-256 is sufficient for today's usage.
 +
* For SHA-1, there are a little less attack scenarios than MD5. If in doubt, SHA-1 is preferable.
 +
* Encryption "DES" is considered very unsafe, use only in an emergency for reasons of compatibility!
 +
* For cryptologists it's a debatable point whether "HMAC-MD5-96" and "HMAC-SHA- 96" can muster enough entropy for key lengths of "AES-192" or "AES-256".
 +
* From the foregoing considerations, we would recommended at present "HMACSHA-96" with "AES-128" as authentication and encryption method.
 +
<br />
 +
='''Change in Trap Design '''=
 +
<br />
 +
<br /> [[Datei:Wichtig_zeichen.png]]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 example, from '''epc8221SwitchEvtPort1''' to '''epc8221SwitchEvtPort12'''. Since new firmware versions can generate many more different events, this behavior quickly produces 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 variable bindings.
 +
<br />
 +
<br />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 '''=
 +
<br />NET-SNMP provides a very widespread collection of SNMP command-line tools (snmpget, 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
 +
<br />
 +
<br /><code>c:\usr\share\snmp\mibs</code>
 +
<br />or
 +
<br />
 +
<br /><code>/usr/share/snmp/mibs</code>
 +
<br />
 +
<br />So later you can use the 'subtree names' instead of OIDs:
 +
<br />
 +
<br /><code>Name: snmpwalk -v2c -mALL -c public 192.168.1.232 gudeads</code>
 +
<br /><code>OID: snmpwalk -v2c -mALL -c public 192.168.1.232 1.3.6.1.4.1.28507</code>
 +
<br />
 +
<br />'''NET-SNMP Examples '''
 +
<br />
 +
<br /> [[Datei:Wichtig_zeichen.png]] These examples refer to Gude devices that have switchable ports.
 +
<br />
 +
<br />Query Power Port 1 switching state:
 +
<br />
 +
<br />snmpget -v2c -mALL -c public 192.168.1.232 epc822XPortState.1
 +
<br />
 +
<br />Switch on Power Port 1:
 +
<br />
 +
<br />snmpset -v2c -mALL -c private 192.168.1.232 epc822XPortState.1 integer 1
 +
<br />
 +
='''MIB table'''=
 +
<br />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.
 +
<br />The example for a complete OID would be "1.3.6.1.4.1.28507.85.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.
 +
<br />Good to know: In the web server on every device you can find the MIB table under the SNMP tab. You can also download the MIB tables on our website under Downloads.
 +
<br />
 +
<br />
 +
<br /> Please note that not all commands are available for all of our devices.
 +
<br /> This table was created for our Expert Power Control 8045.
 +
<br />
 +
<br />
 +
{|cellpadding="10" border="0" cellspacing="1"
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|Name
 +
|align="left"|Description
 +
|align="left"|OID
 +
|align="left"|Type
 +
|align="left"|Acc.
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045TrapCtrl
 +
|align="left"|0 = off 1 = Ver. 1 2 = Ver. 2c 3 = Ver. 3
 +
|align="left"|87.1.1.1.1.0
 +
|align="left"|Integer32
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045TrapIPIndex
 +
|align="left"|A unique value, greater than zero, for each receiver slot.
 +
|align="left"|.87.1.1.1.2.1.1.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045TrapAddr
 +
|align="left"|DNS name or IP address specifying one Trap receiver slot. A port can
 +
optionally be specified: 'name:port' An empty string disables this slot.
 +
|align="left"|.87.1.1.1.2.1.2.x
 +
|align="left"|OCTETS
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045portNumber
 +
|align="left"|The number of Relay Ports
 +
|align="left"|.87.1.3.1.1.0
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045PortIndex
 +
|align="left"|A unique value, greater than zero, for each Relay Port.
 +
|align="left"|.87.1.3.1.2.1.1.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045PortName
 +
|align="left"|A textual string containing name of a Relay Port.
 +
|align="left"|OCTETS
 +
|align="left"|RW
 +
|align="left"|
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045PortState
 +
|align="left"|current state of a Relay Port
 +
|align="left"|.87.1.3.1.2.1.3.x
 +
|align="left"|INTEGER
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045PortSwitchCount
 +
|align="left"|The total number of switch actions ocurred on a Relay Port. Does not
 +
count switch commands which will not switch the ralay state, so just real
 +
relay switches are displayed here.
 +
|align="left"|.87.1.3.1.2.1.4.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045PortStartupMode
 +
|align="left"|set Mode of startup sequence (off, on , remember last state)
 +
|align="left"|.87.1.3.1.2.1.5.x
 +
|align="left"|INTEGER
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045PortStartupDelay
 +
|align="left"|Delay in sec for startup action
 +
|align="left"|.87.1.3.1.2.1.7.x
 +
|align="left"|Integer32
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045PortRepowerTime
 +
|align="left"|Delay in sec for repower port after switching off
 +
|align="left"|.87.1.3.1.2.1.7.x
 +
|align="left"|Integer32
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045PortResetDuration
 +
|align="left"|Delay in sec for turning Port on again after Reset action
 +
|align="left"|.87.1.3.1.2.1.8.x
 +
|align="left"|Integer32
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045Buzzer
 +
|align="left"|turn Buzzer on and off
 +
|align="left"|.87.1.3.10.0
 +
|align="left"|Integer32
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045ActivePowerChan
 +
|align="left"|Number of suppported Power Channels.
 +
|align="left"|.87.1.5.1.1.0
 +
|align="left"|Unsigned32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045PowerIndex
 +
|align="left"|Index of Power Channel entries
 +
|align="left"|.87.1.5.1.2.1.1.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045ChanStatus
 +
|align="left"|0 = data not active, 1 = data valid
 +
|align="left"|.87.1.5.1.2.1.2.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045AbsEnergyActive
 +
|align="left"|Absolute Active Energy counter.
 +
|align="left"|.87.1.5.1.2.1.3.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045PowerActive
 +
|align="left"|Active Power
 +
|align="left"|.87.1.5.1.2.1.4.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045Current
 +
|align="left"|Actual Curent on Power Channel.
 +
|align="left"|.87.1.5.1.2.1.5.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045Voltage
 +
|align="left"|Actual Voltage on Power Channel
 +
|align="left"|.87.1.5.1.2.1.6.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045Frequency
 +
|align="left"|Frequency of Power Channel
 +
|align="left"|.87.1.5.1.2.1.7.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045PowerFactor
 +
|align="left"|Power Factor of Channel between -1.0 and 1.00
 +
|align="left"|.87.1.5.1.2.1.8.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045Pangle
 +
|align="left"|Phase Angle between Voltage and L Line Current between -180.0 and 180.0
 +
|align="left"|.87.1.5.1.2.1.9.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045PowerApparent
 +
|align="left"|L Line Mean Apparent Power
 +
|align="left"|.87.1.5.1.2.1.10.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045PowerReactive
 +
|align="left"|L Line Mean Reactive Power
 +
|align="left"|.87.1.5.1.2.1.11.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045AbsEnergyReactive
 +
|align="left"|Absolute Reactive Energy counter.
 +
|align="left"|.87.1.5.1.2.1.12.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045AbsEnergyActiveResettable
 +
|align="left"|Resettable Absolute Active Energy counter. Writing '0' resets all
 +
resettable counter.
 +
|align="left"|.87.1.5.1.2.1.13.x
 +
|align="left"|Gauge32
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045AbsEnergyReactiveResettable
 +
|align="left"|Resettable Absolute Reactive Energy counter.
 +
|align="left"|.87.1.5.1.2.1.14.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045ResetTime
 +
|align="left"|Time in seconds since last Energy Counter reset.
 +
|align="left"|Gauge32
 +
|align="left"| RO
 +
|align="left"|
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045ForwEnergyActive
 +
|align="left"|Forward Active Energy counter.
 +
|align="left"|.87.1.5.1.2.1.16.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045ForwEnergyReactive
 +
|align="left"|Forward Reactive Energy counter.
 +
|align="left"|.87.1.5.1.2.1.17.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045ForwEnergyActiveResettable
 +
|align="left"|Resettable Forward Active Energy counter.
 +
|align="left"|.87.1.5.1.2.1.18.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045ForwEnergyReactiveResettable
 +
|align="left"|Resettable Forward Reactive Energy counter.
 +
|align="left"|.87.1.5.1.2.1.19.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045RevEnergyActive
 +
|align="left"|Reverse Active Energy counter.
 +
|align="left"|.87.1.5.1.2.1.20.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045RevEnergyReactive
 +
|align="left"|Reverse Reactive Energy counter.
 +
|align="left"|.87.1.5.1.2.1.21.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045RevEnergyActiveResettable
 +
|align="left"|Resettable Reverse Active Energy counter.
 +
|align="left"|.87.1.5.1.2.1.21.x
 +
|align="left"| Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045RevEnergyActiveResettable
 +
|align="left"|Resettable Reverse Active Energy counter.
 +
|align="left"|.87.1.5.1.2.1.22.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045RevEnergyReactiveResettable
 +
|align="left"|Resettable Reverse Reactive Energy counter.
 +
|align="left"|.87.1.5.1.2.1.23.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045ResidualCurrent
 +
|align="left"|Actual Residual Current on Power Channel. According Type A IEC
 +
60755. Only visible on models that support this feature.
 +
|align="left"|.87.1.5.1.2.1.24.x
 +
|align="left"|Unsigned32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045LineSensorName
 +
|align="left"|A textual string containing name of a Line Sensor
 +
|align="left"|.87.1.5.1.2.1.100.x
 +
|align="left"|OCTETS
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045OVPIndex
 +
|align="left"|None
 +
|align="left"|.87.1.5.2.1.1.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045OVPStatus
 +
|align="left"|shows the status of the built-in Overvoltage Protection
 +
|align="left"|.87.1.5.2.1.2.x
 +
|align="left"|INTEGER
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spActivePowerChan
 +
|align="left"|Number of Single Port Power Channels. Value is zero on EPC 8220 series.
 +
|align="left"|.87.1.5.5.1.0
 +
|align="left"|Unsigned32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spPowerIndex
 +
|align="left"|Index of Single Port Power Channel entries. Indices 0-5 mean Ports A1
 +
to A6, 6-11 are Ports B1 to B6.
 +
|align="left"|.87.1.5.5.2.1.1.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spChanStatus
 +
|align="left"|0 = data not active, 1 = data valid
 +
|align="left"|.87.1.5.5.2.1.2.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spAbsEnergyActive
 +
|align="left"|Absolute Active Energy counter.
 +
|align="left"|.87.1.5.5.2.1.3.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spPowerActive
 +
|align="left"|Active Power
 +
|align="left"|.87.1.5.5.2.1.4.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spCurrent
 +
|align="left"|Actual Curent on Power Channel.
 +
|align="left"|.87.1.5.5.2.1.5.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spVoltage
 +
|align="left"|Actual Voltage on Power Channel
 +
|align="left"|.87.1.5.5.2.1.6.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spFrequency
 +
|align="left"|Frequency of Power Channel
 +
|align="left"|.87.1.5.5.2.1.7.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spPowerFactor
 +
|align="left"|Power Factor of Channel between -1.0 and 1.00
 +
|align="left"|.87.1.5.5.2.1.8.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spPangle
 +
|align="left"|Phase Angle between Voltage and L Line Current between -180.0 and 180.0
 +
|align="left"|.87.1.5.5.2.1.9.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spPowerApparent
 +
|align="left"|L Line Mean Apparent Power
 +
|align="left"|.87.1.5.5.2.1.10.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spPowerReactive
 +
|align="left"|L Line Mean Reactive Power
 +
|align="left"|.87.1.5.5.2.1.11.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spAbsEnergyReactive
 +
|align="left"|Absolute Reactive Energy counter.
 +
|align="left"|.87.1.5.5.2.1.12.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spAbsEnergyActiveResettable
 +
|align="left"|Resettable Absolute Active Energy counter. Writing '0' resets all resettable counter.
 +
|align="left"|.87.1.5.5.2.1.13.x
 +
|align="left"|Gauge32
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spAbsEnergyReactiveResettable
 +
|align="left"|Resettable Absolute Reactive Energy counter.
 +
|align="left"|.87.1.5.5.2.1.14.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spResetTime
 +
|align="left"|Time in seconds since last Energy Counter reset.
 +
|align="left"|.87.1.5.5.2.1.15.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spForwEnergyActive
 +
|align="left"|Forward Active Energy counter.
 +
|align="left"|.87.1.5.5.2.1.16.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spForwEnergyReactive
 +
|align="left"|Forward Reactive Energy counter.
 +
|align="left"|.87.1.5.5.2.1.17.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spForwEnergyActiveResettable
 +
|align="left"|Resettable Forward Active Energy counter.
 +
|align="left"|.87.1.5.5.2.1.18.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spForwEnergyReactiveResettable
 +
|align="left"|Resettable Forward Reactive Energy counter.
 +
|align="left"|.87.1.5.5.2.1.19.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spRevEnergyActive
 +
|align="left"|Reverse Active Energy counter.
 +
|align="left"|.87.1.5.5.2.1.20.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spRevEnergyReactive
 +
|align="left"|Reverse Reactive Energy counter.
 +
|align="left"|.87.1.5.5.2.1.21.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045spRevEnergyActiveResettable
 +
|align="left"|Resettable Reverse Active Energy counter.
 +
|align="left"|.87.1.5.5.2.1.22.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045spRevEnergyReactiveResettable
 +
|align="left"|Resettable Reverse Reactive Energy counter.
 +
|align="left"|.87.1.5.5.2.1.23.x
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045CPUSensorVsystem
 +
|align="left"|System Voltage on CPU Board
 +
|align="left"|.87.1.5.14.1.0
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045CPUSensorVaux
 +
|align="left"|Auxiliary Voltage on CPU Board
 +
|align="left"|.87.1.5.14.2.0
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045CPUSensorVmain
 +
|align="left"|Main Voltage on CPU Board
 +
|align="left"|.87.1.5.14.3.0
 +
|align="left"|Gauge32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045CPUSensorTcpu
 +
|align="left"|Temperature on CPU Board
 +
|align="left"|.87.1.5.14.4.0
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045NTPTimeValid
 +
|align="left"|Show if valid Time is received
 +
|align="left"|.87.1.5.15.1.0
 +
|align="left"|INTEGER
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045NTPUnixTime
 +
|align="left"|show received NTP time as unixtime (secs since 1 January 1970)
 +
|align="left"|.87.1.5.15.2.0
 +
|align="left"|Unsigned32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045NTPLastValidTimestamp
 +
|align="left"|show seconds since last valid NTP timestamp received
 +
|align="left"|.87.1.5.15.3.0
 +
|align="left"|Unsigned32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045RCMBInfoIndex
 +
|align="left"|Index of RCMB Info entries
 +
|align="left"|.87.1.5.16.1.1.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045RCMBCurrentRMS
 +
|align="left"|Actual Residual Current RMS on Power Channel. According Type B IEC 60755. Only visible on models that support this feature.
 +
|align="left"|.87.1.5.16.1.2.x
 +
|align="left"|Unsigned32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045RCMBlCurrentDC
 +
|align="left"|Actual Residual Current DC on Power Channel. According Type B IEC
 +
60755. Only visible on models that support this feature.
 +
|align="left"|.87.1.5.16.1.3.x
 +
|align="left"|Unsigned32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045RCMBOutputRMS
 +
|align="left"|shows the output S1 of the RCMB module
 +
|align="left"|.87.1.5.16.1.4.x
 +
|align="left"|INTEGER
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045RCMBOutputDC
 +
|align="left"|shows the output S2 of the RCMB module
 +
|align="left"|.87.1.5.16.1.5.x
 +
|align="left"|INTEGER
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045RCMBModuleStatus
 +
|align="left"|RCMB Module Status Word
 +
|align="left"|.87.1.5.16.1.6.x
 +
|align="left"|Unsigned32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045SensorIndex
 +
|align="left"|None
 +
|align="left"|.87.1.6.1.1.1.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045TempSensor
 +
|align="left"|actual temperature
 +
|align="left"|.87.1.6.1.1.2.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045HygroSensor
 +
|align="left"|actual humidity
 +
|align="left"|.87.1.6.1.1.3.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045AirPressure
 +
|align="left"|actual air pressure
 +
|align="left"|.87.1.6.1.1.5.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045DewPoint
 +
|align="left"|dew point for actual temperature and humidity
 +
|align="left"|.87.1.6.1.1.6.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045DewPointDiff
 +
|align="left"|difference between dew point and actual temperature (Temp -
 +
DewPoint)
 +
|align="left"|.87.1.6.1.1.7.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045ExtSensorName
 +
|align="left"|A textual string containing name of a external Sensor
 +
|align="left"|.87.1.6.1.1.32.x
 +
|align="left"|OCTETS
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045ExtActiveInputs
 +
|align="left"|Number of suppported Input Channels.
 +
|align="left"|.87.1.6.2.1.0
 +
|align="left"|Unsigned32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045ExtInputIndex
 +
|align="left"|None
 +
|align="left"|.87.1.6.2.2.1.1.x
 +
|align="left"|Unsigned32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045ExtInput
 +
|align="left"|Input state of device
 +
|align="left"|.87.1.6.2.2.1.2.x
 +
|align="left"|INTEGER
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045ExtInputName
 +
|align="left"|A textual string containing name of the Input
 +
|align="left"|.87.1.6.2.2.1.32.x
 +
|align="left"|OCTETS
 +
|align="left"|RW
 +
|-
 +
|- bgcolor="#FFFFFF"
 +
|align="left"|epc8045ExtInputPortNum
 +
|align="left"|Number of external Sensor Port when value greater zero, else device built-in Input.
 +
|align="left"|.87.1.6.2.2.1.33.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|- bgcolor="#D9D9D9"
 +
|align="left"|epc8045ExtInputBlockIndex
 +
|align="left"|Either index of device built-in Input, or index of Input in external sensor.
 +
|align="left"|.87.1.6.2.2.1.34.x
 +
|align="left"|Integer32
 +
|align="left"|RO
 +
|-
 +
|}

Aktuelle Version vom 13. Mai 2024, 10:24 Uhr

SNMP can be used for status information via UDP (port 161). Supported SNMP commands are:

  • GET
  • GETNEXT
  • GETBULK
  • SET


To query via SNMP you need a Network Management System, such as HP OpenView, OpenNMS, Nagios etc., or the simple command line tools of NET-SNMP software. The device supports SNMP protocols v1, v2c and v3. If traps are enabled in the configuration, the device messages are sent as notifications (traps). SNMP Informs are not supported. SNMP Requests are answered with the same version with which they were sent. The version of the sent traps can be set in the configuration.

MIB Tables


The values that can be requested or changed by the device, the so-called "Managed Objects", are described in Management Information Bases (MIBs). These substructures are subordinate to so-called "OID" (Object Identifiers). An OID digit signifies the location of a value inside a MIB structure. Alternatively, each OID can be referred to with its symbol name (subtree name). The device's MIB table can be displayed as a text file by clicking on the link "MIB table" on the SNMP configuration page in the browser.

SNMP v1 and v2c


SNMP v1 and v2c authenticates the network requests by so-called communities. The SNMP request has to send along the so-called community public for queries (read access) and the community private for status changes (write access) . The SNMP communities are read and write passwords. In SNMP v1 and v2 the communities are transmitted unencrypted on the network and can be easily intercepted with IP sniffers within this collision domain. To enforce limited access we recommend the use of DMZ or IP-ACL.

SNMP v3


Because the device has no multiuser management, only one user (default name "standard") is detected in SNMP v3. From the User-based Security Model (USM) MIB variables, there is a support of "usmStats ..." counter. The "usmUser ..." variables will be added with the enhancement of additional users in later firmware versions. The system has only one context. The system accepts the context "normal" or an empty context.

Authentication

The algorithms "HMAC-MD5-96" and "HMAC-SHA-96" are available for authentication. In addition, the "HMAC-SHA-2" variants (RFC7630) "SHA-256", "SHA-384" and "SHA- 512" are implemented.
Wichtig zeichen.png "SHA-384" and "SHA512" are calculated purely in software. If "SHA-384" or "SHA- 512" is set on the configuration page, the time for the key generation may take once up to approx. 45 seconds.
Encryption

The methods "DES", "3DES", "AES-128", "AES-192" and "AES-256" are supported in combination with "HMAC-MD5-96" and "HMAC-SHA-96." For the "HMAC-SHA-2" protocols, there is currently neither RFC nor draft that will allow for cooperation with an encryption.
Wichtig zeichen.png While in the settings "AES-192" and "AES256" the key calculation is based on "draft-blumenthalphoto-aes-usm-04", the methods "AES 192-3DESKey" and "AES 256-3DESKey" utilize a key generation, which is also used in the "3DES" configuration ("draft-reeder-snmpv3-usm-3desede-00"). If one is not an SNMP expert, it is recommended to try in each case the settings with and without "...- 3DESKey".

Passwords

The passwords for authentication and encryption are stored only as computed hashes for security reasons. Thus it is, if at all, very difficult to infer the initial password. However, the hash calculation changes with the set algorithms. If the authentication or privacy algorithms are changed, the passwords must be re-entered in the configuration dialog.

Security



The following aspects should be considered:

  • If encryption or authentication is used, then SNMP v1 and v2c should be turned off. Otherwise the device could be accessed with it.
  • If only authentication is used, then the new "HMAC-SHA-2" methods are superior to the MD5 or SHA-1 hashing algorithms. Since only SHA-256 is accelerated in hardware, and SHA-384 and SHA-512 are calculated purely in software, one should normally select SHA-256. From a cryptographic point of view, the security of SHA-256 is sufficient for today's usage.
  • For SHA-1, there are a little less attack scenarios than MD5. If in doubt, SHA-1 is preferable.
  • Encryption "DES" is considered very unsafe, use only in an emergency for reasons of compatibility!
  • For cryptologists it's a debatable point whether "HMAC-MD5-96" and "HMAC-SHA- 96" can muster enough entropy for key lengths of "AES-192" or "AES-256".
  • From the foregoing considerations, we would recommended at present "HMACSHA-96" with "AES-128" as authentication and encryption method.


Change in Trap Design



Wichtig zeichen.pngIn 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 example, from epc8221SwitchEvtPort1 to epc8221SwitchEvtPort12. Since new firmware versions can generate many more different events, this behavior quickly produces 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 variable 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 (snmpget, 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

Wichtig zeichen.png These examples refer to Gude devices that have switchable ports.

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

MIB table


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 complete OID would be "1.3.6.1.4.1.28507.85.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.
Good to know: In the web server on every device you can find the MIB table under the SNMP tab. You can also download the MIB tables on our website under Downloads.


Please note that not all commands are available for all of our devices.
This table was created for our Expert Power Control 8045.

Name Description OID Type Acc.
epc8045TrapCtrl 0 = off 1 = Ver. 1 2 = Ver. 2c 3 = Ver. 3 87.1.1.1.1.0 Integer32 RW
epc8045TrapIPIndex A unique value, greater than zero, for each receiver slot. .87.1.1.1.2.1.1.x Integer32 RO
epc8045TrapAddr DNS name or IP address specifying one Trap receiver slot. A port can

optionally be specified: 'name:port' An empty string disables this slot.

.87.1.1.1.2.1.2.x OCTETS RW
epc8045portNumber The number of Relay Ports .87.1.3.1.1.0 Integer32 RO
epc8045PortIndex A unique value, greater than zero, for each Relay Port. .87.1.3.1.2.1.1.x Integer32 RO
epc8045PortName A textual string containing name of a Relay Port. OCTETS RW
epc8045PortState current state of a Relay Port .87.1.3.1.2.1.3.x INTEGER RW
epc8045PortSwitchCount The total number of switch actions ocurred on a Relay Port. Does not

count switch commands which will not switch the ralay state, so just real relay switches are displayed here.

.87.1.3.1.2.1.4.x Integer32 RO
epc8045PortStartupMode set Mode of startup sequence (off, on , remember last state) .87.1.3.1.2.1.5.x INTEGER RW
epc8045PortStartupDelay Delay in sec for startup action .87.1.3.1.2.1.7.x Integer32 RW
epc8045PortRepowerTime Delay in sec for repower port after switching off .87.1.3.1.2.1.7.x Integer32 RW
epc8045PortResetDuration Delay in sec for turning Port on again after Reset action .87.1.3.1.2.1.8.x Integer32 RW
epc8045Buzzer turn Buzzer on and off .87.1.3.10.0 Integer32 RW
epc8045ActivePowerChan Number of suppported Power Channels. .87.1.5.1.1.0 Unsigned32 RO
epc8045PowerIndex Index of Power Channel entries .87.1.5.1.2.1.1.x Integer32 RO
epc8045ChanStatus 0 = data not active, 1 = data valid .87.1.5.1.2.1.2.x Integer32 RO
epc8045AbsEnergyActive Absolute Active Energy counter. .87.1.5.1.2.1.3.x Gauge32 RO
epc8045PowerActive Active Power .87.1.5.1.2.1.4.x Integer32 RO
epc8045Current Actual Curent on Power Channel. .87.1.5.1.2.1.5.x Gauge32 RO
epc8045Voltage Actual Voltage on Power Channel .87.1.5.1.2.1.6.x Gauge32 RO
epc8045Frequency Frequency of Power Channel .87.1.5.1.2.1.7.x Gauge32 RO
epc8045PowerFactor Power Factor of Channel between -1.0 and 1.00 .87.1.5.1.2.1.8.x Integer32 RO
epc8045Pangle Phase Angle between Voltage and L Line Current between -180.0 and 180.0 .87.1.5.1.2.1.9.x Integer32 RO
epc8045PowerApparent L Line Mean Apparent Power .87.1.5.1.2.1.10.x Integer32 RO
epc8045PowerReactive L Line Mean Reactive Power .87.1.5.1.2.1.11.x Integer32 RO
epc8045AbsEnergyReactive Absolute Reactive Energy counter. .87.1.5.1.2.1.12.x Gauge32 RO
epc8045AbsEnergyActiveResettable Resettable Absolute Active Energy counter. Writing '0' resets all

resettable counter.

.87.1.5.1.2.1.13.x Gauge32 RW
epc8045AbsEnergyReactiveResettable Resettable Absolute Reactive Energy counter. .87.1.5.1.2.1.14.x Gauge32 RO
epc8045ResetTime Time in seconds since last Energy Counter reset. Gauge32 RO
epc8045ForwEnergyActive Forward Active Energy counter. .87.1.5.1.2.1.16.x Gauge32 RO
epc8045ForwEnergyReactive Forward Reactive Energy counter. .87.1.5.1.2.1.17.x Gauge32 RO
epc8045ForwEnergyActiveResettable Resettable Forward Active Energy counter. .87.1.5.1.2.1.18.x Gauge32 RO
epc8045ForwEnergyReactiveResettable Resettable Forward Reactive Energy counter. .87.1.5.1.2.1.19.x Gauge32 RO
epc8045RevEnergyActive Reverse Active Energy counter. .87.1.5.1.2.1.20.x Gauge32 RO
epc8045RevEnergyReactive Reverse Reactive Energy counter. .87.1.5.1.2.1.21.x Gauge32 RO
epc8045RevEnergyActiveResettable Resettable Reverse Active Energy counter. .87.1.5.1.2.1.21.x Gauge32 RO
epc8045RevEnergyActiveResettable Resettable Reverse Active Energy counter. .87.1.5.1.2.1.22.x Gauge32 RO
epc8045RevEnergyReactiveResettable Resettable Reverse Reactive Energy counter. .87.1.5.1.2.1.23.x Gauge32 RO
epc8045ResidualCurrent Actual Residual Current on Power Channel. According Type A IEC

60755. Only visible on models that support this feature.

.87.1.5.1.2.1.24.x Unsigned32 RO
epc8045LineSensorName A textual string containing name of a Line Sensor .87.1.5.1.2.1.100.x OCTETS RW
epc8045OVPIndex None .87.1.5.2.1.1.x Integer32 RO
epc8045OVPStatus shows the status of the built-in Overvoltage Protection .87.1.5.2.1.2.x INTEGER RO
epc8045spActivePowerChan Number of Single Port Power Channels. Value is zero on EPC 8220 series. .87.1.5.5.1.0 Unsigned32 RO
epc8045spPowerIndex Index of Single Port Power Channel entries. Indices 0-5 mean Ports A1

to A6, 6-11 are Ports B1 to B6.

.87.1.5.5.2.1.1.x Integer32 RO
epc8045spChanStatus 0 = data not active, 1 = data valid .87.1.5.5.2.1.2.x Integer32 RO
epc8045spAbsEnergyActive Absolute Active Energy counter. .87.1.5.5.2.1.3.x Gauge32 RO
epc8045spPowerActive Active Power .87.1.5.5.2.1.4.x Integer32 RO
epc8045spCurrent Actual Curent on Power Channel. .87.1.5.5.2.1.5.x Gauge32 RO
epc8045spVoltage Actual Voltage on Power Channel .87.1.5.5.2.1.6.x Gauge32 RO
epc8045spFrequency Frequency of Power Channel .87.1.5.5.2.1.7.x Gauge32 RO
epc8045spPowerFactor Power Factor of Channel between -1.0 and 1.00 .87.1.5.5.2.1.8.x Integer32 RO
epc8045spPangle Phase Angle between Voltage and L Line Current between -180.0 and 180.0 .87.1.5.5.2.1.9.x Integer32 RO
epc8045spPowerApparent L Line Mean Apparent Power .87.1.5.5.2.1.10.x Integer32 RO
epc8045spPowerReactive L Line Mean Reactive Power .87.1.5.5.2.1.11.x Integer32 RO
epc8045spAbsEnergyReactive Absolute Reactive Energy counter. .87.1.5.5.2.1.12.x Gauge32 RO
epc8045spAbsEnergyActiveResettable Resettable Absolute Active Energy counter. Writing '0' resets all resettable counter. .87.1.5.5.2.1.13.x Gauge32 RW
epc8045spAbsEnergyReactiveResettable Resettable Absolute Reactive Energy counter. .87.1.5.5.2.1.14.x Gauge32 RO
epc8045spResetTime Time in seconds since last Energy Counter reset. .87.1.5.5.2.1.15.x Gauge32 RO
epc8045spForwEnergyActive Forward Active Energy counter. .87.1.5.5.2.1.16.x Gauge32 RO
epc8045spForwEnergyReactive Forward Reactive Energy counter. .87.1.5.5.2.1.17.x Gauge32 RO
epc8045spForwEnergyActiveResettable Resettable Forward Active Energy counter. .87.1.5.5.2.1.18.x Gauge32 RO
epc8045spForwEnergyReactiveResettable Resettable Forward Reactive Energy counter. .87.1.5.5.2.1.19.x Gauge32 RO
epc8045spRevEnergyActive Reverse Active Energy counter. .87.1.5.5.2.1.20.x Gauge32 RO
epc8045spRevEnergyReactive Reverse Reactive Energy counter. .87.1.5.5.2.1.21.x Gauge32 RO
epc8045spRevEnergyActiveResettable Resettable Reverse Active Energy counter. .87.1.5.5.2.1.22.x Gauge32 RO
epc8045spRevEnergyReactiveResettable Resettable Reverse Reactive Energy counter. .87.1.5.5.2.1.23.x Gauge32 RO
epc8045CPUSensorVsystem System Voltage on CPU Board .87.1.5.14.1.0 Gauge32 RO
epc8045CPUSensorVaux Auxiliary Voltage on CPU Board .87.1.5.14.2.0 Gauge32 RO
epc8045CPUSensorVmain Main Voltage on CPU Board .87.1.5.14.3.0 Gauge32 RO
epc8045CPUSensorTcpu Temperature on CPU Board .87.1.5.14.4.0 Integer32 RO
epc8045NTPTimeValid Show if valid Time is received .87.1.5.15.1.0 INTEGER RO
epc8045NTPUnixTime show received NTP time as unixtime (secs since 1 January 1970) .87.1.5.15.2.0 Unsigned32 RO
epc8045NTPLastValidTimestamp show seconds since last valid NTP timestamp received .87.1.5.15.3.0 Unsigned32 RO
epc8045RCMBInfoIndex Index of RCMB Info entries .87.1.5.16.1.1.x Integer32 RO
epc8045RCMBCurrentRMS Actual Residual Current RMS on Power Channel. According Type B IEC 60755. Only visible on models that support this feature. .87.1.5.16.1.2.x Unsigned32 RO
epc8045RCMBlCurrentDC Actual Residual Current DC on Power Channel. According Type B IEC

60755. Only visible on models that support this feature.

.87.1.5.16.1.3.x Unsigned32 RO
epc8045RCMBOutputRMS shows the output S1 of the RCMB module .87.1.5.16.1.4.x INTEGER RO
epc8045RCMBOutputDC shows the output S2 of the RCMB module .87.1.5.16.1.5.x INTEGER RO
epc8045RCMBModuleStatus RCMB Module Status Word .87.1.5.16.1.6.x Unsigned32 RO
epc8045SensorIndex None .87.1.6.1.1.1.x Integer32 RO
epc8045TempSensor actual temperature .87.1.6.1.1.2.x Integer32 RO
epc8045HygroSensor actual humidity .87.1.6.1.1.3.x Integer32 RO
epc8045AirPressure actual air pressure .87.1.6.1.1.5.x Integer32 RO
epc8045DewPoint dew point for actual temperature and humidity .87.1.6.1.1.6.x Integer32 RO
epc8045DewPointDiff difference between dew point and actual temperature (Temp -

DewPoint)

.87.1.6.1.1.7.x Integer32 RO
epc8045ExtSensorName A textual string containing name of a external Sensor .87.1.6.1.1.32.x OCTETS RW
epc8045ExtActiveInputs Number of suppported Input Channels. .87.1.6.2.1.0 Unsigned32 RO
epc8045ExtInputIndex None .87.1.6.2.2.1.1.x Unsigned32 RO
epc8045ExtInput Input state of device .87.1.6.2.2.1.2.x INTEGER RO
epc8045ExtInputName A textual string containing name of the Input .87.1.6.2.2.1.32.x OCTETS RW
epc8045ExtInputPortNum Number of external Sensor Port when value greater zero, else device built-in Input. .87.1.6.2.2.1.33.x Integer32 RO
epc8045ExtInputBlockIndex Either index of device built-in Input, or index of Input in external sensor. .87.1.6.2.2.1.34.x Integer32 RO
Abgerufen von „https://wiki.gude-systems.com/index.php?title=SNMP_eng&oldid=1061“