schneiderops.xml in DCE 7.3.0: old or new (or vise versa)?

[DCIM_Support]

Hi all!

Long ago I wanted to learn the concrete answer to my question: why in each new DCE version (for example, and at DCE 7.3.0) there is an outdated DDF-file for Schneider Electric StruxureWare Operations schneiderops.xml_from_DCE730 ?

If in the DCE client to execute internet online search of updatings for SNMP DDF-files, it is offered to download and apply the new updated version above the specified file: schneiderops.xml_from_inetupdate .

These are different files, only a question: what of them new and actual and what of them outdated also demands replacement?

Very thanks for the support.

(CID:105460319)

[DCIM_Support]

Hi spezialist We will look into this and get back to you. Thanks Jesper

(CID:105460688)

[DCIM_Support · Accepted solution]

Hi spezialist,

The version from DCE 730 is version 3 of the DDF file, and the version you posted from inetupdate is version 1.

Version 3 includes support for extended states of the DCO server including more information about the state of the DCO service, it's database service, and it's load balancer. There is also support for more alarming conditions that could be reported by DCO.

I hope this helps,

Scott

(CID:105461311)

[DCIM_Support]

Scott, thanks for the answer. From all this the question arises: why in online repositories of DDF-files there is an outdated version? After all has to be on the contrary: in online repositories have to be always the freshest versions of DDF-files. Why?

(CID:105462051)

[DCIM_Support]

That's a good question 🙂 I'm looking into that now. I believe that the issue is that we modified something in the DDF file between version 1 and 3 in such a way that the system is not recognizing that they're the same DDF (aside from version). It should be recognizing that you have version 3 installed and that it has downloaded an older version from the web and just ignore version 1. But for now it is showing version 1 as a "New" file. I should be able to get to the bottom of this relatively quickly and hopefully get a new bundle on the web without this conflict.

(CID:105462133)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.