AP7930 firmware

cgraham_apc · ‎2021-06-28

This was originally posted on APC forums on 5/13/2010

Hi,

After upgrading one of our AP7930 PDU's the AMP reading is now showing 35.6 with a critical alarm. So i left it and checked the next day and it was reading correctly. Now 2 days later it is not reading the amps correctly. The original version was V2.6.4 and i have upgraded the unit to v3.7.3. I have a couple more AP7930's that are working fine after perfoming the same upgrade.

Any ideas?

cgraham_apc · ‎2021-06-28

This was originally posted on APC forums on 5/13/2010

Hi,

After upgrading one of our AP7930 PDU's the AMP reading is now showing 35.6 with a critical alarm. So i left it and checked the next day and it was reading correctly. Now 2 days later it is not reading the amps correctly. The original version was V2.6.4 and i have upgraded the unit to v3.7.3. I have a couple more AP7930's that are working fine after perfoming the same upgrade.

Any ideas?

See Answer In Context

BillP · ‎2021-06-28

This reply was originally posted by Angela on APC forums on 5/13/2010

just to be clear - is this via the LCD display you mean or in the web interface?

what does it read when it displays the "correct" value? is it off by a decimal place?

cgraham_apc · ‎2021-06-28

This was originally posted on APC forums on 5/13/2010

Both the web interface and the display on the unit read 35 amps but it is only connected to a 15 amp circuit.

cgraham_apc · ‎2021-06-28

This was originally posted on APC forums on 5/14/2010

I reset everything on the PDU to default except the ip but that did not fix the issue. so i downgraded the firmwre to v3.7.0 and everthing looks good now. I will play around some more and see if i can put 3.7.3 back on.

BillP · ‎2021-06-28

This reply was originally posted by Angela on APC forums on 5/17/2010

that is quite interesting. you said you had other AP7930's that did NOT do this or were those PDUs different models?

cgraham_apc · ‎2021-06-28

This was originally posted on APC forums on 5/13/2010

here are the logs from before and after the upgrade.

Date Time I IMax IMin
05/11/2010 23:30:41 35.7 36.3 35.5
05/11/2010 23:20:41 35.7 36.0 35.5
05/11/2010 23:10:41 35.6 36.1 35.5
05/11/2010 22:40:23 10.5 10.8 10.4
05/11/2010 22:30:23 10.6 10.8 10.4
05/11/2010 22:20:23 10.5 10.9 10.4
05/11/2010 22:10:23 10.6 10.9 10.4
05/11/2010 22:00:23 10.5 10.8 10.4
05/11/2010 21:50:23 10.5 11.0 10.4

Message was edited by: cgraham

BillP · ‎2021-06-28

This reply was originally posted by Angela on APC forums on 5/13/2010

hm interesting.

can you post the event.txt from the relevant time as well? you can remove any information you don't want seen in there such as your username, etc

if you go to the administration tab->general->about, does it report everything correctly in there such as the model of the PDU and serial number? can you tell me the first couple of digits of the serial number? like ZA0752?

thanks

cgraham_apc · ‎2021-06-28

This was originally posted on APC forums on 5/13/2010

Model Number: AP7930
Serial Number: ZA0527015992
Hardware Revision: B2
Manufacture Date: 07/01/2005
MAC Address: 00 C0 B7 77 1B FF
Management Uptime: 1 Day 14 Hours 36 Minutes

Name: rpdu
Version: v3.7.3
Date: 02/24/2010
Time: 11:32:52

Name: aos
Version: v3.7.3
Date: 02/02/2010
Time: 17:05:14

cgraham_apc · ‎2021-06-28

This was originally posted on APC forums on 5/13/2010

Here are the event logs from the time of the upgrade

05/11/2010 23:04:25 System: Web user 'infosat' logged out from 1.0.10.18.
05/11/2010 23:02:42 System: Web user 'infosat' logged in from 1.0.10.18.
05/11/2010 23:01:06 System: FTP user 'infosat' logged out from 1.0.10.18.
05/11/2010 23:01:06 System: FTP user 'infosat' logged in from 1.0.10.18.
05/11/2010 23:01:04 Switched Rack PDU: Overload.
05/11/2010 23:01:02 Switched Rack PDU: Communications established.
05/11/2010 23:00:54 System: Network service started. System IP is 1.0.10.108 from manually configured settings.
05/11/2010 23:00:54 System: Warmstart.
05/11/2010 22:57:44 System: FTP user 'infosat' logged in from 1.0.10.18.
05/11/2010 22:57:28 System: Web user 'infosat' logged out from 1.0.10.18.
05/11/2010 22:57:14 System: Web user 'infosat' logged in from 1.0.10.18.
05/11/2010 22:57:00 System: Web user 'infosat' logged out from 1.0.10.18.
05/11/2010 22:54:03 System: Web user 'infosat' logged in from 1.0.10.18.
05/11/2010 22:52:39 Switched Rack PDU: Overload.
05/11/2010 22:52:39 System: FTP user 'infosat' logged out from 1.0.10.18.
05/11/2010 22:52:39 System: FTP user 'infosat' logged in from 1.0.10.18.
05/11/2010 22:52:37 Switched Rack PDU: Communications established.
05/11/2010 22:52:37 Switched Rack PDU: Phase configuration change. Overload threshold.
05/11/2010 22:52:37 Switched Rack PDU: Phase configuration change. Warning threshold.
05/11/2010 22:52:37 Switched Rack PDU: Phase configuration change. Overload threshold.
05/11/2010 22:52:37 Switched Rack PDU: Phase configuration change. Warning threshold.
05/11/2010 22:52:37 Switched Rack PDU: Phase configuration change. Overload threshold.
05/11/2010 22:52:33 Switched Rack PDU: Phase configuration change. Warning threshold.
05/11/2010 22:52:32 System: Initializing data in the EventLogConfiguration file.
05/11/2010 22:52:28 System: Network service started. System IP is 1.0.10.108 from manually configured settings.
05/11/2010 22:52:28 System: Warmstart.
05/11/2010 22:44:51 System: FTP user 'infosat' logged in from 1.0.10.18.
05/11/2010 22:44:51 System: FTP user 'infosat' logged out from 1.0.10.18.
05/11/2010 22:44:51 System: FTP user 'infosat' logged in from 1.0.10.18.
05/11/2010 22:44:51 System: FTP user 'infosat' logged out from 1.0.10.18.

BillP · ‎2021-06-28

This reply was originally posted by Angela on APC forums on 5/13/2010

hmm to start what I would do is [download your config.ini|http://nam-en.apc.com/cgi-bin/nam_en.cfg/php/enduser/std_adp.php?p_faqid=9321] (via those instructions) and then try resetting the PDU to defaults EXCLUDING TCP/IP settings. this is under Administration->General->Reset/reboot->Reset ALL (EXCLUDE TCP/IP) so you don't lose your IP settings.

let's see what happens there and the config.ini will have all of your settings for us to re-upload to the NMC in the PDU afterwards.

BillP · ‎2021-06-28

This reply was originally posted by Angela on APC forums on 5/18/2010

just a couple of points, if you're still at 3.7.0, can you try to upgrade it again?

did you upgrade all of your PDUs from the 2.6.4 to 3.7.3 or were some at some newer versions?

if you have any left, we could try going from 2.x, to 3.3, to 3.7.3 incase anything between the versions got messed up, since there is a bigger gap.

let me know what you'd like to do but we'd like to research to avoid the problem again.

also, - if you are familiar with SNMP or can use a MIB browser, can you see what the OID of 1.3.6.1.4.1.318.1.1.12.1.15 will retrieve from a PDU exhibiting a problem?

BillP · ‎2021-06-28

This reply was originally posted by Angela on APC forums on 5/13/2010

also another thing, i see some threshold configuration changes in the log, which i am not sure if that was you playing around with it at any point or not but if you want to tell me what those thresholds are for overloads and warnings, you can do that or post the config.ini file after you remove any private information, that will work.

cgraham_apc · ‎2021-06-28

This was originally posted on APC forums on 5/13/2010

Hi,

After upgrading one of our AP7930 PDU's the AMP reading is now showing 35.6 with a critical alarm. So i left it and checked the next day and it was reading correctly. Now 2 days later it is not reading the amps correctly. The original version was V2.6.4 and i have upgraded the unit to v3.7.3. I have a couple more AP7930's that are working fine after perfoming the same upgrade.

Any ideas?