Send General Query with SNMP Manager on redundant system

[uxout]

Hello,

I'm using WinCC OA 3.15P1 on Win10 x64.
I'm using SNMP Driver on a redundant system and I want to send a GQ from the active (let's say server 1 here) server to SNMP agent 1 (correctly connected).
I tried:

Code: Select all

dpSet("_Driver1.GQ", 1);

But both SNMP Manager are sending the GQ, is it a bug?
When I try :

Code: Select all

dpSet("_Driver1_2.GQ", 1);

Only SNMP Manager from server 2 sends the GQ, here it's ok.

My goal is to send GQ from SNMP Manager only from server 1 or 2 with CTRL Scripts, am I wrong here?

Any help would be appreciated, thanks.

[rglock]

Hello,

at first some general clarification:

_Driver1.GQ represents the driver with driver number 1 at the first redundant partner

_Driver1_2.GQ represents the driver with driver number 1 at the second redundant partner


Setting 1,2,3... at this GQ-Element in case of SNMP means the Agent Number, to which the GQ should be sent.

Example:
Setting _Driver1.GQ = 5 (via dpSet), means "send a GQ to the SNMPAgent 5, configured at the SNMP Manager, running with number 1"


Normally the config.redu of the WinCCOA-version contains the following line (and other DPEs in addition):

# Commands for the driver
[event]
copyDpType = "_DriverCommon.GQ"

Setting _Driver1.GQ = 5 will therefore lead to copying the value 5 to _Driver1_2.GQ and that's the reason, why the driver 1 at the second redundancy partner will also send a GQ (because it reacts on _Driver1_2.GQ-Element).

[uxout]

Thanks for the informations.
That's actually not a bug then, but now how can I send a GQ on the first redundant partner only?

[adaneau]

Hi,

Just adapt the config.redu to not have a copydp entry for your driver GQ DPE and it should make the trick

Edit: just be careful to not make it for all drivers because otherwise you will have strange behavior.

[uxout]

Hi ^^
That's what I did finally, but I hopped for a better solution, more clean.
I'll make it that way right now, thanks anyway.

[leoknipp]

Modifying the config.redu-file for the WinCC OA installation is not the best idea.
When installing an update the settings will be changed.

With the config entry drvGQ you can defined which dp element shall be used to trigger a GQ. The default value is _Driver.GQ
You can define your own dp-element (which is not copied by the config.redu settings) for the SNMP driver to start a GQ.

Where is the problem if the GQ is send by both redundant servers?
Data received by the driver on the passive server will be discarded.

Best Regards
Leopold Knipp
Senior Support Specialist

[uxout]

Ok, this could be better for my case, thanks.
Actually, it's not a problem, it is just one need in the project : only active server sends/receives SNMP message, passive do nothing. (even the traps must be discarded).