Application Note WAGO-I/O-PRO V2.3. SNMP Communication A Version 1.1.0

Transcription

1 Application Note WAGO-I/O-PRO V2.3 A500850

2 2 Anwendungshinweis A by WAGO Kontakttechnik GmbH & Co. KG All rights reserved. WAGO Kontakttechnik GmbH & Co. KG Hansastraße 27 D Minden Phone: +49 (0) 571/ Fax: +49 (0) 571/ Online: info@wago.com Technical Support Phone: +49 (0) 571/ Fax: +49 (0) 571/ support@wago.com Every conceivable measure has been taken to ensure the accuracy and completeness of this documentation. However, as errors can never be fully excluded, we always appreciate any information or suggestions for improving the documentation. We wish to point out that the software and hardware terms, as well as the trademarks of companies used and/or mentioned in the present document are generally protected by trademark or patent.

3 Anwendungshinweis A Description 3 Information about This Documentation Copyright This documentation, including all figures and illustrations contained therein, is subject to copyright protection. Any use of this documentation that infringes upon the copyright provisions stipulated herein is prohibited. Reproduction, translation, electronic and phototechnical filing/archiving (e.g., photocopying), as well as any amendments require the written consent of WAGO Kontakttechnik GmbH & Co. KG, Minden, Germany. Non-observance will entail the right of claims for damages. Number Notation Table 1: Number Notation Number Code Example Comment Decimal 100 Normal notation Hexadecimal 0x64 C notation Binary '100' ' ' In quotation marks, nibble separated by a period Font Conventions Table 2: Font Conventions Font Type Explanation italic Names of paths and files are displayed in italics, e.g.: C:\Programs\WAGO-I/O-CHECK Menu Menu options are displayed in bold, e.g., : Save > A greater than symbol between two names denotes the selection of a menu option, e.g.: File > New Input Designation of input or optional fields are displayed in bold, e.g.: Start of measurement range Value Input or selection values are displayed in quotation marks, e.g.: Enter the value 4mA under Start of measurement range. [Button] Button labels within the dialogs are bold and enclosed in square brackets, e.g.: [Input] [Key] Key labels on the keyboard are displayed in bold and enclosed in square brackets, e.g.: [F5]

4 4 Description Anwendungshinweis A Symbols DANGER DANGER WARNING CAUTION NOTICE ESD (Electrostatic Discharge) Warning against personal injury! Indicates a high-risk, imminently hazardous situation which, if not avoided, will result in death or serious injury. Do not work on components while energized! Indicates a high-risk, imminently hazardous situation which, if not avoided, will result in death or serious injury. Warning against personal injury! Indicates a moderate-risk, potentially hazardous situation which, if not avoided, could result in death or serious injury. Warning against personal injury! Indicates a low-risk, potentially hazardous situation which, if not avoided, may result in minor or moderate injury. Warning: Damage to property! Indicates a potentially hazardous situation which, if not avoided, may result in damage to property. Warning: Damage to property caused by electrostatic discharge (ESD)! Indicates a potentially hazardous situation which, if not avoided, may result in damage to property. Note Information Important note! Indicates a potential malfunction which will not result in damage to property, however, if not avoided. Additional Information Refers to additional information which is not an integral part of this documentation (e.g., the Internet).

5 Anwendungshinweis A Description 5 Legal Principles Subject to Change WAGO Kontakttechnik GmbH & Co. KG reserves the right to make any alterations or modifications that serve to increase the efficiency of technical progress. WAGO Kontakttechnik GmbH & Co. KG owns all rights arising from granting patents or from the legal protection of utility patents. Third-party products are always mentioned without any reference to patent rights. Thus, the existence of such rights cannot be excluded. Personnel Qualification The use of the product described in this document is exclusively geared to specialists having qualifications in PLC programming, electrical specialists or persons instructed by electrical specialists who are also familiar with the appropriate current standards. Moreover, the persons cited here must also be familiar with all of the products cited in this document, along with the operating instructions. They must also be capable of correctly predicting any hazards which may not arise until the products are combined. WAGO Kontakttechnik GmbH & Co. KG assumes no liability resulting from improper action and damage to WAGO products and third-party products due to non-observance of the information contained in this document. Limitation of Liability This documentation describes the use of various hardware and software components in specific example applications. The components may represent products or parts of products from different manufacturers. The respective operating instructions from the manufacturers apply exclusively with regard to intended and safe use of the products. The manufacturers of the respective products are solely responsible for the contents of these instructions. The sample applications described in this documentation represent concepts, that is, technically feasible applications. Whether these concepts can actually be implemented depends on various guidelines. For example, different versions of the hardware or software components can require different handling than that described here. Therefore, the descriptions contained in this documentation do not form the basis for assertion of a certain product characteristic. Responsibility for safe use of a specific software or hardware configuration lies with the party that produces or operates the configuration. This also applies when one of the concepts described in this document was used for implementation of the configuration. WAGO Kontakttechnik GmbH & Co. KG assumes no liability for the realization of these concepts.

6 6 Description Anwendungshinweis A Table of Contents Table of Contents Description Material Used Required Libraries Devices Tools Overview of the SNMP Explanation of Terms System Overview PFC Controller as SNMP Agent Structure of the Management Information Database (MIB) SNMP Basic Configuration Creating an MIB Reproducing the WAGO MIB Implementation in e!cockpit Implementation in WAGO-I/O-PRO V Creating a Customer-Specific MIB Working Procedure Applying for a "Private Enterprise Number" Defining the MIB data points Create PLC program Implementation in e!cockpit Implementation in WAGO-I/O-PRO V MIB file Validating the MIB file Example "AIRCON MIB" SNMP Traps and Inform Notifications Integrating and Sending Variables Trap Definition SNMP V SNMP V2C/V PFC Controller as SNMP Manager... 27

7 Anwendungshinweis A Description 7 1 Description This application note explains how the WAGO controllers PFC100 and PFC200 can communicate via SNMP: Sending traps / inform notifications Creating an MIB Using the controller as an SNMP agent To do so, the SNMP-specific libraries for WAGO-I/O-PRO V2.3 and e!cockpit are used. 2 Material Used 2.1 Required Libraries Library Description Version* WagoLibNetSnmpManager SNMP manager and agent functions WagoLibNetSnmp WagoApp SNMP Register, read and write OIDs SNMP manager and agent functions; register, read and write OIDs *This version was used when the instructions for use were created. 2.2 Devices 2.3 Tools WAGO-I/O-PRO WAGO-I/O-PRO e!cockpit Supplier Quantity Description Item Version* No. WAGO 1 WAGO PFC x V (06) *This version was used when the instructions for use were created. Designation Item Version* No. WAGO-e!COCKPIT WAGO-I/O-PRO V2.3 (CODESYS) ManageEngine (Zoho Corp.) Free SNMP MIB Browser *This version was used when the instructions for use were created. 1

8 8 Overview of the SNMP Anwendungshinweis A Overview of the SNMP The network protocol Simple Network Management Protocol (SNMP) is used to monitor and control other devices in the network (Agents) from a central station (Manager). Figure 1: Overview of SNMP The central station can access devices that support SNMP via SNMP commands (GET, SET) for reading and writing. With this approach, for instance, it is possible to adapt the configuration of a switch or access the process data of a WAGO controller. An SNMP agent can also send a report to the central station to inform it of a current event. This allows, for instance, a standardized report (Trap) to be sent to the SNMP manager if there is an temperature increase in the server room which is recognized by a WAGO controller. Figure 2: SNMP communication

9 Anwendungshinweis A Overview of the SNMP Explanation of Terms Manager Agent Managed Objects (MO) Management Information Base (MIB) Object Identifier (OID) Trap Inform Notification The central station which enables access to the SNMP agents in the network. The agent does not necessarily need to be dedicated hardware; the manager can also run on any computer in the form of an application (e.g., MIB browser). The manager sends GET or SET queries to the agents and receives the corresponding answers. The manager also receives the trap reports sent by the agents. WAGO controllers can also take over manger tasks and query other SNMP agents via GET and SET data. An agent is a network device which answers the queries from a manager. An agent is typically also able to send eventcontrolled trap reports to the manager. Designation for a data point which can be queried or written by an SNMP manager; a managed object is addressed by the manager via an "Object IDentifier" (OID). MIB designates the data structure which describes the data provided by an SNMP agent; the MIB describes the SNMP agents as a compilation of managed objects. The MIB is organized in a tree structure. The individual managed objects are addressed by the OID. WAGO controllers provide all the managed objects described in the MIB-II. In addition, customer-specific managed objects can be created and linked with data from the PLC runtime environment. Explicit and unique identifier which identifies a managed object within an SNMP network; an OID consists of a series of numbers, each separated by a period. Each point represents a branch in the MIB tree structure. An SNMP report which is sent by an SNMP agent because of an event; the receiver for this type of report is typically a component of the SNMP manager. Corresponds to a normal trap report, but requires a confirmation from the SNMP manager when it is received. This makes the use of this procedure more reliable. Only available with SNMP V2C and V3.

10 10 Overview of the SNMP Anwendungshinweis A System Overview The SNMP functionality of the PFC devices is based on the open source software Net-SNMP 2. This standard packet can be accessed from the PLC runtime environment via library functions. One use of the PFC200 is as an SNMP agent: Creating, reading and writing objects in the MIB Sending traps (SNMP V1, V2C, V3) Sending inform notifications (SNMP V2C, V3) Functions are also available for operating the PFC as SNMP manager and accessing other SNMP agents: SNMP-GET SNMP-SET Figure 3: System overview The actual SNMP communication takes place through Net-SNMP services running in the background. SNMP-specific parameters (community name, trap receiver, SNMP V3-user) can be set via the Web-Based Management (WBM). 2

11 Anwendungshinweis A PFC Controller as SNMP Agent 11 4 PFC Controller as SNMP Agent 4.1 Structure of the Management Information Database (MIB) This chapter indicates which data a WAGO PFC controller can provide as an SNMP agent and how this data is organized. First, a general overview of how data is structured in the SNMP context is presented. A data point which can be accessed by SNMP is designated as a management object. The total amount of all managed objects comprises the MIB of an SNMP agent. The individual managed objects are addressed via an object identifier (OID). The managed objects are organized in a tree structure. This tree structure forms the basis for name assignment. The path marked in red in Figure 3 shows how the OID is assembled to query the system description of an SNMP agent. The OID can be represented as text (.iso.org.dod.internet.mgmt.mib-ii.system.sysdescr.0), a number series ( ), or as a mixture of the two forms ( sysDescr.0) The "0" at the end of the OID is what is referred to as the instance ID. This ID must be attached to the OID for GET and SET queries of scalable objects (e.g., sysdescr, sysname), that is, objects which are not organized in a table. The ID of the corresponding table element must be attached for objects that are organized in tables (e.g.,. ifdescr). 3 Figure 4: Tree structure 3

12 12 PFC Controller as SNMP Agent Anwendungshinweis A Basically, each SNMP must support a minimum set of managed objects. This basic element is designated as MIB-II and is specified in RFC The MIB-II contains, for instance, general information about the SNMP agent (system description, runtime, location) and information about its connectivity (network interface status). Manufacturer-specific managed objects can also be defined. The branch.iso.org.dod.internet.private.enterprise ( ) in the MIB tree is reserved for this definition. For this area of the MIB, each device manufacturer can apply to the "Assigned Number Authority (IANA) for a cost-free "Private Enterprise Number") 5. For instance, the number is reserved for WAGO. In this manufacturer-specific area, the owner of the "Private Enterprise Number" can then define arbitrary device-specific managed objects and make them available to an SNMP manager. The owner of the "Private Enterprise Number" is responsible for managing the objects provided by the his devices. The uniqueness of each object, the associated OID and therefore the information provided must be ensured 6. For instance, the OID must not refer to the system description for one SNMP and the name of the ETHERNET interface for different one. WAGO has identified its own objects with the WAGO MIB 7, which enable access to data of the PLC runtime environment and other functions. The WAGO ETHERNET controllers of the x family support this WAGO MIB as default. In contrast, the MIB can be configured with complete freedom on the PFC100 and PFC200 devices. The WAGO MIB is not implemented. Thus, two scenarios for using the functionality of the devices PFC100 and PFC200 can be formulated: Reproduction of objects defined in the WAGO MIB; for instance, the SNMP functionality of an ETHERNET fieldbus controller can be reproduced 8. The objects are located in the address space (WAGO). Creation of a customer-specific MIB using a customer-specific "Private Enterprise Number", e.g., an air conditioning system is controlled by a PFC200. The manufacturer of this air conditioning system provides data (e.g., temperature and humidity) via the SNMP under his own enterprise number. The objects are located in the address space xyz, whereby xyz corresponds to the private enterprise number assigned by the IANA. The concrete implementation of these two scenarios is explained later in this chapter (manual, Chapter 16)

13 Anwendungshinweis A PFC Controller as SNMP Agent SNMP Basic Configuration The page "General Configuration" is under the menu item "SNMP" in Web-Based Management (WBM). Figure 5: WBM basic configuration The parameter "Service active" controls the Net-SNMP services running in the background. If this parameter is set, the Net-SNMP services are started and the PFC, acting as the SNMP agent, can process corresponding queries of an SNMP manager. The parameter change is immediately accepted when the "Submit" button is clicked. The corresponding default objects can be directly accessed from the MIB-II via the additional entry fields. Changes are only accepted after the PFC is restarted: Parameters OID Name Name of device sysname Description sysdescr Physical location syslocation Contact syscontact Table 1: MIB-II parameters

14 14 PFC Controller as SNMP Agent Anwendungshinweis A Creating an MIB To implement an MIB, corresponding libraries are available for the programming systems WAGO-I/O-PRO V2.3 (CODESYS) and e!cockpit: Programming system Library Function name e!cockpit WagoAppSNMP Description FuSnmpAgent_CustomOIDRegister Creating a user-specific OID (INT32, UINT32, STRING) FuSnmpAgent_CustomOIDSet FuSnmpAgent_CustomOIDGet Writes a value in the OID; this value can be read by the SNMP manager Readout of the value of an OID which is, e.g., written by an SNMP manager. Table 2: Library function e!cockpit Programming system WAGO-I/O-PRO V2.3 Library Function name snmpregistercustomoid_int32 snmpregistercustomoid_uint32 snmpregistercustomoid_uint32 snmpsetvaluecustomoid_int32 snmpsetvaluecustomoid_uint32 snmpsetvaluecustomoid_string snmpgetvaluecustomoid_int32 snmpgetvaluecustomoid_uint32 snmpgetvaluecustomoid_string WagoLibNetSnmp Description Creating a user-specific OID (INT32, UINT32, STRING) Writes a value in the OID; this value can be read by the SNMP manager Readout of the value of an OID which is, e.g., written by an SNMP manager. Table 3: Library function WAGO-I/O-PRO V2.3

15 Anwendungshinweis A PFC Controller as SNMP Agent Reproducing the WAGO MIB How to use the PFC to reproduce the function of the "PLC data group" defined in the WAGO MIB is explained here as an example. The "PLC Data Group" defines three tables. Each of these tables defines 255 INT32 variables. These variables can be used as the container for an exchange of any data between the PLC runtime and an SNMP manager. OID Entry Access Description wioplcdataindex R/W Index wioplcdatareadarea R/W INTEGER [1..255] wioplcdatawritearea R INTEGER [1..255] Table 4: Overview of the "PLC Data Group" The table "wioplcdatareadarea" is described by the SNMP manager and read out by the PLC runtime environment. The table "wioplcdatawritearea" is described by the PLC runtime environment and read by the SNMP manager. Figure 6: Overview of the WAGO MIB WAGO provides a corresponding file for the WAGO MIB; this file can be imported in the SNAP manager or MIB browser. MIB files contain all the OIDs defined in a device and so simplify configuration of the SNMP manager. The WAGO MIB is available for download on the WAGO homepage 9. The "Free SNMP MIB Browser" from ManageEngine is used in these instructions for use. The following screenshots display the tree structure of the WAGO MIB and the table view of the "PLC Data Group". 9

16 16 PFC Controller as SNMP Agent Anwendungshinweis A Figure 7: MIB browser with WAGO MIB Figure 8: Table view in the MIB browser

17 Anwendungshinweis A PFC Controller as SNMP Agent Implementation in e!cockpit The example project "SNMP_eCOCKPIT_Example" demonstrates how the OIDs of the "PLC Data Group" defined in the WAGO MIB can be reproduced. The corresponding implementation is located in the folder "WAGO-MIB example": Figure 9: Implementation in e!cockpit Implementation in WAGO-I/O-PRO V2.3 The example project "SNMP_CoDeSys_Example" demonstrates how the OIDs of the "PLC Data Group" defined in the WAGO MIB can be reproduced. The corresponding implementation is located in the folder "WAGO-MIB example": Figure 10: Implementation in WAGO-I/O-PRO V2.3

18 18 PFC Controller as SNMP Agent Anwendungshinweis A Creating a Customer-Specific MIB A customer-specific MIB must always be created when the PFC should register with a customer-specific "Private Enterprise Number" instead of as a WAGO device in the SNMP environment. The following scenario explains the process for creating a customer-specific MIB: The company AirCon delivers an air conditioning system for a server room at the company ACME. The air conditioning system is controlled by a PFC200. It should be possible to read the current temperature in the server room from the SNMP manager of the ACME company. It should also be possible to specify the setpoint temperature for the server room from the SNMP manager. If a maximum temperature is exceeded, the ventilation system should send an alarm (trap) to the SNMP manager. Figure 11: Example application "Customer-specific MIB" Working Procedure The following work steps are required to create a customer-specific SNMP application: 1. Apply for a "Private Enterprise Number". 2. Define the MIB data points. 3. Create the PLC program. 4. Create MIB file. Figure 12: Working procedure

19 Anwendungshinweis A PFC Controller as SNMP Agent Applying for a "Private Enterprise Number" A "Private Enterprise Number" can be applied for via the Internet site of the "Assigned Number Authority (IANA) at no cost: The customer-specific MIB can be defined as soon as the "Private Enterprise Number" has been received. In the following, it is assumed that the "Private Enterprise Number" has been assigned to the fictive company AirCon Defining the MIB data points The air conditioning system should provide the following objects: Type designation, STRING, read only Version, STRING, read only Actual temperature value, INT32, read only Temperature setpoint value, INT32, read and write After the data points have been specified, they can be arranged in the MIB tree. A node for "products" is added below the enterprise number. The different AirCon products can then be entered below the "products" node. For this example, the data objects in the product line "acs" (air conditioning system) are added: Figure 13: Customer-specific MIB tree

20 20 PFC Controller as SNMP Agent Anwendungshinweis A The OIDs of the individual objects can be derived from the MOB tree structure. In Figure 13, the customer-specific objects are marked in green. The "lower camel case" is usually used to designate the objects 10, whereby the names of the objects contain the abbreviation of the higher-order MIB node as a prefix. In this example scenario, therefore, the names start with the prefix "acs" (air conditioning system). Description Name OID Data type Access Type designation acstype STRING R Version acsversion STRING R Actual temperature value acscurtemp INT32 R Temperature setpoint value acssettemp INT32 R/W Table 5: MIB objects The OIDs defined in the MIB-II (blue marking in Figure 13) can be configured via the WBM (Chapter 5.1) Create PLC program Implementation in e!cockpit The example project "SNMP_eCOCKPIT_Example" demonstrates how the OIDs can be generated and how a trap is sent. The corresponding implementation is located in the folder "CUSTOM-MIB example" Implementation in WAGO-I/O-PRO V2.3 The example project "SNMP_CoDeSys_Example" demonstrates how the OIDs can be generated and how a trap is sent. The corresponding implementation is located in the folder "CUSTOM-MIB example". 10

21 Anwendungshinweis A PFC Controller as SNMP Agent MIB file An MIB file contains all the OIDs with traps that are defined in a device and therefore simplifies configuration of the SNMP manager. The MIB file is written as an ASCII file in SMI syntax. The file contains the following information for each managed object 11 : Data type (SYNTAX) Access authorization (ACCESS) Status (STATUS) Description (DESCRIPTION) Position in the MIB A text editor is sufficient for creating an MIB file. Programs from different manufacturers (MIB Designer) are available at cost for more complex scenarios. For example: Agent ++ MIB Designer ( MG-SOFT Visual MIB Designer ( Validating the MIB file Tools for checking the syntax of an MIB file are available on the Internet: Simple Web ( Web interface to libsmi ( Figure 14: Example MIB validation 11

22 22 PFC Controller as SNMP Agent Anwendungshinweis A Example "AIRCON MIB" The MIB file comprises the bridge between OIDs and the PLC variables. VAR END_VAR stype : STRING := 'AirCon ACS 4711'; (* Type description *) sversion : STRING := '1.0'; (* Version number *) diacttemp : DINT := 23; (* Actual temperature value *) disettemp : DINT := 20; (* Setpoint value *) soidmodel soidversion soidacttemp soidsettemp : STRING := ' '; : STRING := ' '; : STRING := ' '; : STRING := ' '; ApplicationNoteA mib -- Version: Date: Author: WAGO Kontakttechnik GmbH & Co. KG -- Descr: This MIB file includes the objects which are defined in application note a T-- The MIB for the air conditioning system developed by the fictive company "AirCon" is defined as an example AIRCON-MIB DEFINITIONS ::= BEGIN IMPORTS OBJECT-TYPE FROM RFC-1212 TRAP-TYPE FROM RFC-1215 enterprises FROM RFC1155-SMI; aircon OBJECT IDENTIFIER ::= {enterprises 65535} products OBJECT IDENTIFIER ::= {aircon 1} acs OBJECT IDENTIFIER ::= {products 1} acstype OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0..80)) ACCESS read-only STATUS mandatory DESCRIPTION "Model description of air conditioning system" DEFVAL { "AirCon ACS 4711" } ::= { acs 1 } acsversion OBJECT-TYPE SYNTAX OCTET STRING (SIZE (0..80)) ACCESS read-only STATUS mandatory DESCRIPTION "Version number of air conditioning system" ::= { acs 2 } acsacttemp OBJECT-TYPE SYNTAX INTEGER ACCESS read-only STATUS mandatory DESCRIPTION "Actual temperature" ::= { acs 3 } acssettemp OBJECT-TYPE SYNTAX INTEGER ACCESS read-write STATUS mandatory DESCRIPTION "Temperature set value" ::= { acs 4 }

23 Anwendungshinweis A PFC Controller as SNMP Agent TRAP DEFINITIONS END acstemperaturealarm TRAP-TYPE ENTERPRISE aircon VARIABLES { acsacttemp } DESCRIPTION "Temperature has exceeded maximum!" ::= 25 Figure 15: MIB file in the MIB browser Figure 16: Trap receiver

24 24 PFC Controller as SNMP Agent Anwendungshinweis A SNMP Traps and Inform Notifications Trap Inform Notification An SNMP report which is sent by an SNMP agent because of an event; the receiver for this type of report is typically a component of the SNMP manager. Corresponds to a normal trap report, but requires a confirmation from the SNMP manager when it is received; this makes the use of this process more reliable. Only available with SNMP V2C and V3. Functions for sending this report are available for WAGO-I/O-PRO V2.3 and e!cockpit. For some functions, the receiver data is configured in the Web- Based Management (WBM). In other cases, the receiver data is specified directly in the PLC program. The use of all available functions is demonstrated in the example projects for e!cockpit and WAGO-I/O-PRO V2.3. Figure 17: SNMP configuration in the WBM

25 Anwendungshinweis A PFC Controller as SNMP Agent Integrating and Sending Variables The functions for sending SNMP traps and information notifications offer the possibility to attach any OID to the report. In the example "Creating a customerspecific MIB" (Chapter 5.2), this option is used to attach the OID "acsacttemp" to a trap report. Basically, the variable to be linked must be defined in the MIB of the PFC controller. If, for instance, an arbitrary text should be sent via a trap, first a corresponding OID containing the text to be sent must be created. This OID can then be attached to the trap report. The WAGO MIB defines ten OIDs for userspecific reports which can be used when the PFC is used as an SNMP device with a WAGO enterprise number. If a customer-specific enterprise number should be used, the WAGO MIB can be used as a template and correspondingly adapted: wiousertrapmessages OBJECT IDENTIFIER ::= { wiosnmp 5 } wiousertrapmsg1 OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "String for 1.SNMP-Trap" ::= { wiousertrapmessages 1 } wiousertrapmsg2 OBJECT-TYPE SYNTAX DisplayString (SIZE (0..255)) ACCESS read-write STATUS mandatory DESCRIPTION "String for 1.SNMP-Trap" ::= { wiousertrapmessages 2 }

26 26 PFC Controller as SNMP Agent Anwendungshinweis A Trap Definition To make the traps and inform notifications provided by a PFC known to a network management system, the system must be defined in the MIB file. In the example "Creating a customer-specific MIB" (Chapter 5.2), an SNMP-V1 trap is sent and defined in the MIB file. The difference between the SNMP-V1 and V2C- /V3 traps is explained in this chapter. Detailed information can be obtained, e.g., from the Wiki of the Net-SNMP projects SNMP V1 Definition of an SNMP-V1 trap with the specific trap number 25; the report contains the variable "acsacttemp". aircon OBJECT IDENTIFIER ::= {enterprises 65535} -- TRAP DEFINITIONS acstemperaturealarm TRAP-TYPE ENTERPRISE aircon VARIABLES { acsacttemp } DESCRIPTION "Temperature has exceeded maximum!" ::= SNMP V2C/V3 The definition of SNMP-V2C-/V3 traps is slightly different. The traps are defined as NOTIFICATION TYPE. Instead of the specific trap number like for V2C-/V3 traps, the OID snmptrapoid.0 is always attached as a second variable. This OID must always contain the OID for identifying the trap 13. The OID must be assigned by the creator, since, in contrast to SNMP V1 traps generic trap numbers are not existing. For the following example, the branch 999 is used within the aircon Enterprises. aircon OBJECT IDENTIFIER ::= {enterprises 65535} airconotif OBJECT IDENTIFIER ::= { aircon 999 } -- TRAP DEFINITIONS acstemperaturealarm NOTIFICATION-TYPE OBJECTS { acsacttemp } DESCRIPTION "Temperature has exceeded maximum!" ::= { airconotif 25 } The OID results for the trap defined here. This OID is transferred via the parameter "senterprise" of the corresponding V2C- /V3 function in e!cockpit or WAGO-I/O-PRO. This value is then attached to the trap report with the identifier snmptrapoid.0 as a second variable sics_snmpv2cv3traps.html

27 Anwendungshinweis A PFC Controller as SNMP Manager 27 5 PFC Controller as SNMP Manager In order to use a PFC controller as the SNMP manager, corresponding function blocks are available for WAGO-I/O-PRO V2.3 and e!cockpit. The SNMP commands GET and SET are supported. In the example projects for e!cockpit and WAGO-I/O-PRO V2.3, the use of these function blocks is demonstrated.

28 WAGO Kontakttechnik GmbH & Co. KG PO box 2880 D Minden Hansastraße 27 D Minden Phone: +49 (0) 571/ Fax: +49 (0) 571/ info@wago.com Web: