Lates APC ATS DDF

[DCIM_Support]

This question was originally posted on DCIM Support by Yang Gao on 2017-09-22

---

Can someone send me the latest APC ATS DDF to me. This file is not listed under Device Support. Is there way to download the DDF file from DCE client?

Thanks,

(CID:125211213)

[DCIM_Support]

This answer was originally posted on DCIM Support by spezialist on 2017-09-22

---

Hi Yang Gao,

It must be so, since the latest DDF-file for APC ATS is already in DCE-server, for example, in the latest version of DCE-7.4.3.

Always glad to answer your questions.

(CID:125211222)

[DCIM_Support]

This comment was originally posted on DCIM Support by Yang Gao on 2017-09-22

---

how do you download the DDF file from DCE to laptop?

(CID:125211228)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2017-09-22

---

The latest DDF-file for APC ATS in DCE-7.4.3 is v.10 and it can not be downloaded to your PC in a standard way.

But if you really need it, I can help you.

Always glad to answer your questions.

(CID:125211233)

[DCIM_Support]

This comment was originally posted on DCIM Support by Yang Gao on 2017-09-22

---

Yes, please send the file to me at gaoya@navcanada.ca

(CID:125211239)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2017-09-22

---

Hi Yang Gao,

Please, check you mailbox.

Always glad to answer your questions.

(CID:125211241)

[DCIM_Support]

This comment was originally posted on DCIM Support by Yang Gao on 2017-09-25

---

I couldn't find the OID for "Device Status - ATS" in either APC ATS DDF file or POWERNET423.mib. Can you please help to find out or point a direction for me to find out? is there more MIB file for APC ATS beyond POWERNET423.mib?

(CID:125211623)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2017-09-25

---

Hi Yang Gao,

This is because this sensor is standard for all native Schneider Electric devices. Therefore, it is defined for all native devices in the core.xml DDF-file.

Specifically for your ATS device:

.1.3.6.1.4.1.318.1.4.2.2.1.2.1 - Device Name (for example ATS)
.1.3.6.1.4.1.318.1.4.2.2.1.4.1 - Device Status (for example 2)

Where OID "Device Status" can have the following values:

1 - Unknown
2 - Normal
3 - Warning
4 - Critical

Always glad to answer your questions.

(CID:125211650)

[DCIM_Support]

This comment was originally posted on DCIM Support by Yang Gao on 2017-09-25

---

can you please send the core MIB and DDF files? Thanks.

(CID:125211655)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2017-09-25

---

Check you mail box please.

(CID:125211668)

[DCIM_Support]

This comment was originally posted on DCIM Support by Yang Gao on 2017-09-25

---

can you please send me the MIB file that contains the OIDs for device status?

(CID:125211753)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2017-09-26

---

Hi Yang Gao,

I couldn't find the OID for "Device Status - ATS" in either APC ATS DDF file or POWERNET423.mib. Can you please help to find out or point a direction for me to find out? is there more MIB file for APC ATS beyond POWERNET423.mib?

You are mistaken: the mib-file has a complex tree structure. Therefore, it is better to view it using special software, for example, "iReasoning MIB Browser Free Personal Edition" or the like.

Thus, if you carefully examine the file powernet423.mib, then we will see the following:

33907powernet423.mibtrue atsStatusSwitchStatus OBJECT-TYPE SYNTAX INTEGER { fail(1), ok(2) } ACCESS read-only STATUS mandatory DESCRIPTION "This variable returns the status of the ATS." ::= { atsStatusDeviceStatus 10 } 

Yes, of course, so it's not easy 😀 to know the complete SNMP OID for this parameter. But if you use the above MIB-viewer software, we will see more clear information:

Thus, the parameter that you are interested in has SNMP OID .1.3.6.1.4.1.318.1.1.8.5.1.10.0 and can only take two numeric values (fail (1), ok (2)).

And yet I repeat: the DCE-server does not use the above SNMP OID when determining the status of the ATS. Instead, it uses two SNMP OIDs, of which I wrote above. So, these two SNMP OIDs are drawn from the experimental branch and they are not really described in the file powernet423.mib:

snmpwalk -m +ALL -v2c -cpublic 192.168.0.139 .1.3.6.1.4.1.318.1.4.2.2.1.2.1
PowerNet-MIB::experimental.2.2.1.2.1 = STRING: "ATS"

snmpwalk -m +ALL -v2c -cpublic 192.168.0.139 .1.3.6.1.4.1.318.1.4.2.2.1.4.1
PowerNet-MIB::experimental.2.2.1.4.1 = INTEGER: 2

I hope I clearly explained.

Always glad to answer your questions.

(CID:125212058)

[DCIM_Support]

This comment was originally posted on DCIM Support by Yang Gao on 2017-09-26

---

Thanks for your explanation.

I did use iReasoning MIB browser to view ATS OIDs with Powernet423.mib. I couldn't find the OID for Device Status as you said because the OID for Device Status is under Experimental branch.

If I understand  correctly, the Experimental branch is for APC internal use and is not visible to customer and thus there is no published MIB description for customer use.

if the Experimental branch is available to customer, is it possible for you to send me the MIB file as I asked before. Our development team wants to use OID 192.168.0.139 .1.3.6.1.4.1.318.1.4.2.2.1.4.1 to  develop alarm monitoring driver on our operational monitoring system if the Experimental branch is available to public user.

(CID:125212319)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2017-09-27

---

Hi Yang Gao,

I did use iReasoning MIB browser to view ATS OIDs with Powernet423.mib. I couldn't find the OID for Device Status as you said because the OID for Device Status is under Experimental branch.

Yes, that's right.

If I understand  correctly, the Experimental branch is for APC internal use and is not visible to customer and thus there is no published MIB description for customer use.

I can not neither confirm nor deny, since I am not an employee of Schneider Electric. So use this "as is" as many community users do 😀.

if the Experimental branch is available to customer, is it possible for you to send me the MIB file as I asked before.

Unfortunately, this is impossible because of the reason I mentioned above.

Our development team wants to use OID 192.168.0.139 .1.3.6.1.4.1.318.1.4.2.2.1.4.1 to  develop alarm monitoring driver on our operational monitoring system if the Experimental branch is available to public user.

You are a little mistaken: 192.168.0.139 is the IP-address of my device for example 😀, and SNMP OID is .1.3.6.1.4.1.318.1.4.2.2.1.4.1. I do not see any problems for using the standard SNMP branch for APC ATS from powernet423.mib, which I showed in my screenshot. In this branch also have SNMP OID for ATS status (this can be seen in my screenshot). Then why your development team can not or does not want to use it?

Always glad to answer your questions.

(CID:125212840)

[DCIM_Support]

This comment was originally posted on DCIM Support by Yang Gao on 2017-09-27

---

Our development team wants to receive one Summary Alarm only from ATS. Device Status OID  .1.3.6.1.4.1.318.1.4.2.2.1.4.1 appears meet the summary alarm requirement. The atsStatusSwitchStatus OID .1.3.6.1.4.1.318.1.1.8.5.1.10.0 does not fully meet the summary requirement. I simulated a over current alarm condition, Device Status showed a alarm but the atsStatusSwitchStatus did not.

(CID:125212878)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2017-09-27

---

The atsStatusSwitchStatus OID .1.3.6.1.4.1.318.1.1.8.5.1.10.0 does not fully meet the summary requirement. I simulated a over current alarm condition, Device Status showed a alarm but the atsStatusSwitchStatus did not.

Probably, therefore, this SMMP OID is not used in the native DDF-file for APC ATS from the DCE-server...

In any case, you will have to use the information I gave you "as is", and do not rely on any "private" 😀 MIB-file from Schneider Electric.

Always glad to answer your questions.

(CID:125212899)

[DCIM_Support]

This comment was originally posted on DCIM Support by Yang Gao on 2018-01-05

---

My development team wants to know if APC can add the device status OID 1.3.6.1.4.1.318.1.4.2.2.1.4.1 to Powernet423.mib or if APC can provide a MIB file that contains that OID.

(CID:127535467)

[DCIM_Support]

This answer was originally posted on DCIM Support by Steven Marchetti on 2017-09-22

---

Hi Yang,

While in Struxureware, you can always go to the device menu, SNMP device communications settings, and device definition files. Click Add/update definitions, check APC website. This will allow DCE to get the latest DDF files assuming you have connectivity to the internet. 

Thanks,

Steve

(CID:125211235)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2017-10-03

---

Hi Yang Gao,

Have you solved your problem or not?

With respect.

(CID:126159039)

[DCIM_Support]

This comment was originally posted on DCIM Support by Yang Gao on 2017-10-03

---

Our development team is reluctant to use the Device Status OID unless  there is published MIB. Thanks for your help.

(CID:126159125)

[DCIM_Support]

This comment was originally posted on DCIM Support by spezialist on 2017-10-03

---

Hi Yang Gao,

Very thanks for the feedback.

With respect.

(CID:126159128)

[DCIM_Support]

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