SNMP eng - Versionsgeschichte

Lh am 13. Mai 2024 um 09:24 Uhr

2024-05-13T09:24:19Z

Lh am 13. Mai 2024 um 09:22 Uhr

2024-05-13T09:22:22Z

Lh am 19. April 2024 um 07:50 Uhr

2024-04-19T07:50:20Z

Änderungen zeigen

Lh am 27. März 2024 um 08:32 Uhr

2024-03-27T08:32:11Z

Lh am 27. März 2024 um 08:31 Uhr

2024-03-27T08:31:50Z

Lh am 27. März 2024 um 08:29 Uhr

2024-03-27T08:29:38Z

Lh am 26. März 2024 um 14:13 Uhr

2024-03-26T14:13:28Z

Lh am 26. März 2024 um 14:11 Uhr

2024-03-26T14:11:41Z

Lh am 18. März 2024 um 10:36 Uhr

2024-03-18T10:36:36Z

Lh: Die Seite wurde neu angelegt: „
SNMP-get:Enables the acceptance of SNMP-GET commands.
SNMP-set:Allows the reception of SNMP-SET commands.
SNMP UDP Port:…“

2024-03-18T10:36:11Z

Die Seite wurde neu angelegt: „ SNMP-get:Enables the acceptance of SNMP-GET commands. SNMP-set:Allows the reception of SNMP-SET commands. SNMP UDP Port:…“

Neue Seite

SNMP-get:Enables the acceptance of SNMP-GET commands.
 SNMP-set:Allows the reception of SNMP-SET commands.
 SNMP UDP Port:Sets the UDP port where SNMP messages are received.
 sysContact:Value of RFC 1213 sysContact.
 sysName:Value of RFC 1213 sysName.
 sysLocation:Value of RFC 1213 sysLocation.
 Enable SNMP v2:Activates SNMP v2.
 
 [[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.
 
 Community public:The community password for SNMP GET requests.
 Community private:The community password for SNMP SET requests.
 Enable SNMP v3:Activates SNMP v3.
 SNMP v3 Username:The SNMP v3 User Name.
 SNMP v3 Authorization Algorithm:The selected Authentication Algorithm.
 SNMP v3 Privacy Algorithm:SNMP v3 Encryption Algorithm..
 
 [[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.
 
 [[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.
 
 Send SNMP traps:Here you can specify whether, and in what format the device should send SNMP traps.
 SNMP trap receiver:You can insert here up to eight SNMP trap receiver.
 MIB table:The download link to the text file with the MIB table for the device.
 More information about SNMP settings are available from our support or can be found
on the Internet at www.gude.info/wiki.

@@ Zeile 5: / Zeile 5: @@
 * SET
 <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 />
 ='''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
@@ Zeile 81: / Zeile 76: @@
 <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 />
 {|cellpadding="10" border="0" cellspacing="1"
 |- bgcolor="#D9D9D9"

@@ Zeile 5: / Zeile 5: @@
 * SET
 <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 />
 ='''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

@@ Zeile 47: / Zeile 47: @@
 <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 '''
+='''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 />

@@ Zeile 32: / Zeile 32: @@
 <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 />
-<br />'''Security '''
+='''Security '''=
 <br />
 <br />The following aspects should be considered:
@@ Zeile 42: / Zeile 42: @@
 * From the foregoing considerations, we would recommended at present "HMACSHA-96" with "AES-128" as authentication and encryption method.
 <br />
-<br />'''Change in Trap Design '''
+='''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.

@@ Zeile 6: / Zeile 6: @@
 <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.
-=MIB Tables=
+='''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=
+='''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=
+='''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 />
@@ Zeile 72: / Zeile 72: @@
 <br />snmpset -v2c -mALL -c private 192.168.1.232 epc822XPortState.1 integer 1
 <br />
-'''Device MIB 8041'''
+='''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. 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 />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.

@@ Zeile 44: / Zeile 44: @@
 <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 /> [[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.
@@ Zeile 50: / Zeile 50: @@
 <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 />c:\usr\share\snmp\mibs
+<br /><code>c:\usr\share\snmp\mibs</code>
 <br />or
 <br />
-<br />/usr/share/snmp/mibs
+<br /><code>/usr/share/snmp/mibs</code>
 <br />
 <br />So later you can use the 'subtree names' instead of OIDs:
 <br />
-<br />Name: snmpwalk -v2c -mALL -c public 192.168.1.232 gudeads
+<br /><code>Name: snmpwalk -v2c -mALL -c public 192.168.1.232 gudeads</code>
-<br />OID: snmpwalk -v2c -mALL -c public 192.168.1.232 1.3.6.1.4.1.28507
+<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 '''

@@ 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 />
-<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 /><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.
+" 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 />
-<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 />
-<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 /><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.
+<br />'''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:

← Nächstältere Version		Version vom 18. März 2024, 10:36 Uhr
Zeile 1:		Zeile 1:
		+	[[Datei:SNMP.png]]
	<br /><u>SNMP-get:</u>Enables the acceptance of SNMP-GET commands.		<br /><u>SNMP-get:</u>Enables the acceptance of SNMP-GET commands.
	<br /><u>SNMP-set:</u>Allows the reception of SNMP-SET commands.		<br /><u>SNMP-set:</u>Allows the reception of SNMP-SET commands.