It's your place to connect with experts and peers, get continuous support, and share knowledge.
Find out how SCADA systems and networks, like EcoStruxure Geo SCADA Expert, help industrial organizations maintaining efficiency, processing data for smarter decision making with IoT, RTU and PLC devices.
You can subscribe to this forum after you log in or create your free account..
Posted: 2020-09-11 06:47 AM
Posted: 2020-09-11 06:47 AM
I need some advice on setting up an SNMP point to process a specific trap:
An SI of ours trying to set up Geo SCADA to receive SNMP traps from a third party VSWR monitor (from BirdTech), for a voice radio transmitter.
The specific trap we are trying to receive carries OID: 18.104.22.168.4.1.21522.214.171.124.2 as defined in the MIB file for the device.
We have tried several permutations for setting up a SNMP String Point as a specific trap (tweaking, the Position, Location, Variable, and Specific Code fields), we’ve also selected and unselected the “Displayable as String” check box.
With all of our Specific Trap configurations, we’ve been unsuccessful at receiving the trap – the Process count for the point remains 0 and no value is displayed.
The help files give us generic descriptions for the fields that can be configured, but there is no example of how to set those fields for this particular scenario.
See attachments for details on the equipment and the trap we are trying to recieve.
GeoSCADA version is 2019 Build 81.7457
Any advice on how to configure the point to process this trap would be welcomed.
Posted: 2020-09-11 07:49 AM
I always find SNMP frustrating and not simple at all, mostly revolving around terrible or non existent mib files, and how to practically alarm off of traps and show an alarm has cleared.
I have not done much with SNMP in Geo/ClearSCADA, but for another SCADA platform we used Kepware to get the traps and then into a database. We, as in my coworker, did have to do some magic to keep from making duplicate entries. It holds the last X number (settable number) of traps it has received, and we would get up to 10 at a time from a device, but not always the same number so identifying new vs old was the issue.
Might be an option to purse if you just can't get it working in Geo/ClearSCADA,like you want.
Posted: 2020-09-14 05:35 PM
SNMP is a little confusing.
My suggestion is to use a separate SNMP Browser / Trap Agent to start with and confirm that you have the end device configuration all correct.
Wireshark is good for final verification, and comparison between conversations. But you really want to start from a 'known good' configuration, and that is easiest to get working (from my experience) without ClearSCADA / Geo SCADA in the picture.
It is entirely possible that SNMP Traps themselves have some 'traps' since it's not a commonly used feature of ClearSCADA / Geo SCADA. So you might want to prepare yourself for sending in a bug report (or two) around this functionality.
If you can get it working correctly with a third party SNMP Browser / Trap Agent, and then converting those settings across to ClearSCADA / Geo SCADA doesn't work, you could provide that information to your local Schneider Tech Support office.
Posted: 2020-10-04 03:17 AM
This doesn't sound like it's ClearSCADA / GeoSCADA related... it sounds like you might be talking about either the WMI SNMP Server service, or the Windows SNMP Client service. Neither of which will get SNMP Trap data into ClearSCADA / GeoSCADA (although the first can help to generate Trap data related to the Windows server itself... but there's normally other ways of doing that anyway.. like with the Performance Monitor driver).
Checking to see whether the Windows SNMP Client server has 'captured' the SNMP Trap port is worthwhile however. Since if it grabs port 162 before ClearSCADA gets a chance to, then Traps to ClearSCADA won't work either..
Posted: 2020-10-05 11:37 AM
Bevan that message above yours looks like a spam account. one post and external links.
Posted: 2020-10-06 11:20 AM
Schneider Electric Level 3 tech support came to my aid and helped me figure it out - the setup of the SNMP point in Geo SCADA to process specific traps is not very difficult, once you understand how it works. However, it isn't very obvious.
I'll be putting together a small how-to guide soon. I can post it here if you are interested.