Loading ...
home » spaces » Racks, Rack Accessories, & Cooling » discussion » General » apc ap7920 - reboot management interface looses all settings. Is this normal?

apc ap7920 - reboot management interface looses all settings. Is this normal?

Discussion in Racks, Rack Accessories, & Cooling started by Jason , 2/27/2017 2:25 PM
Login  to follow, share, and participate in this space.
Not a member?Join now
  • JasonJLee
    Jason
    Novice
    Novice
    Jason 2/27/2017 2:25 PM

    Hi,

    I bought a used AP7920 which arrived already up to date. I also flashed the firmware again myself to make sure.

    When it turns on, I have to detect it using the device ip configuration utility, and set an IP.

    When I log in and fill out all the settings, everything works fine. Manually set to to a fixed IP, named the connections, turned things on and off all fine.

    However, none of these settings stay with the device if I reboot the management interface, or if I simply turn the power supply off and on again.

    It tries to grab an IP address (even though its set to fixed IP), fails and drops back to being unassigned, where I can use the utility again to find it and go around again.

    My question is, is this the normal functioning of the device?

    Is it not supposed to remember the setting, and I am supposed to load the config.ini onto it whenever it looses power or reboots, via a script, or using a bootp or DHCP server that supplies some settings, OR is something wrong with the unit?

  • ipicKedawinna
    Angela
    =S= Representative
    Angela 2/28/2017 2:07 PM (in response to Jason)

    Hi Jason,

    No, this is not normal. Is there anything in the PDU event log (control L through serial or can be viewed through web) after this or is that also lost post reboot?

    This type of problem and symptom sounds like an internal communication or hardware problem to me unfortunately. Seems like settings are not saving to the onboard NMC's non-volatile flash memory which is where things go when the device is powered off as opposed to RAM, like a computer, where running config and the real time OS is running while the device is powered on.

  • JasonJLee
    Jason
    Novice
    Novice
    Jason 2/28/2017 4:06 PM (in response to Angela)

    Hi Angela,

    Thanks for replying! I just tested the following..

    I reset the log, changed some settings, got timed out (phonecall), logged back in and then rebooted the management interface.

    02/28/2017 15:30:56 System: Web user 'apc' logged in from 192.168.0.61.
    02/28/2017 14:47:00 System: Web user 'apc' logged out from 192.168.0.61.
    02/28/2017 14:43:56 System: Configuration change. System location.
    02/28/2017 14:43:56 System: Configuration change. System contact.
    02/28/2017 14:43:56 System: Configuration change. System name.
    02/28/2017 14:43:29 System: Configuration change. System inactivity timeout.
    02/28/2017 14:43:05 System: Event Log cleared.

    Then the device reset to 0.0.0.0, then I ran the wizard to program in 192.168.0.148 and logged in again.. that log looks like this.

    Date  Time  Event
    02/28/2017 15:45:45 System: Web user 'apc' logged in from 192.168.0.61.
    02/28/2017 15:45:28 System: Network service started. System IP is 192.168.0.148 from manually configured settings.
    02/28/2017 15:45:28 System: Configuration change. Boot mode.
    02/28/2017 15:45:28 System: Configuration change. BOOTP server address.
    02/28/2017 15:45:28 System: Configuration change. TCP/IP gateway.
    02/28/2017 15:45:28 System: Configuration change. TCP/IP subnet mask.
    02/28/2017 15:45:28 System: Configuration change. TCP/IP address.
    02/28/2017 15:42:10 Switched Rack PDU: Communications established.
    02/28/2017 15:42:00 System: Configuration change. User class.
    02/28/2017 15:42:00 System: Initializing data in the Rack PDU file.
    02/28/2017 15:42:00 System: Configuration change. System name.
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Link on outlet #8 (Outlet 8).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Reboot Duration on outlet #8 (Outlet 8).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Name on outlet #8 (Outlet 8).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Link on outlet #7 (Outlet 7).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Reboot Duration on outlet #7 (Outlet 7).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Name on outlet #7 (Outlet 7).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Link on outlet #6 (Outlet 6).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Reboot Duration on outlet #6 (Outlet 6).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Name on outlet #6 (Outlet 6).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Link on outlet #5 (Outlet 5).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Reboot Duration on outlet #5 (Outlet 5).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Name on outlet #5 (Outlet 5).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Link on outlet #4 (Outlet 4).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Reboot Duration on outlet #4 (Outlet 4).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Name on outlet #4 (Outlet 4).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Link on outlet #3 (Outlet 3).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Reboot Duration on outlet #3 (Outlet 3).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Name on outlet #3 (Outlet 3).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Link on outlet #2 (Outlet 2).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Reboot Duration on outlet #2 (Outlet 2).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Name on outlet #2 (Outlet 2).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Link on outlet #1 (Outlet 1).
    02/28/2017 15:42:00 Switched Rack PDU: Device configuration change. Reboot Duration.
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Reboot Duration on outlet #1 (Outlet 1).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Outlet Name on outlet #1 (Outlet 1).
    02/28/2017 15:42:00 Switched Rack PDU: Outlet configuration change. Device name .
    02/28/2017 15:42:00 Switched Rack PDU: Phase configuration change. Overload threshold.
    02/28/2017 15:42:00 Switched Rack PDU: Phase configuration change. Near overload threshold.
    02/28/2017 15:42:00 Switched Rack PDU: Phase configuration change. Overload threshold.
    02/28/2017 15:42:00 Switched Rack PDU: Phase configuration change. Near overload threshold.
    02/28/2017 15:42:00 Switched Rack PDU: Phase configuration change. Overload threshold.
    02/28/2017 15:42:00 Switched Rack PDU: Phase configuration change. Near overload threshold.
    02/28/2017 15:42:00 System: Initializing data in the DCal file.
    02/28/2017 15:42:00 System: Initializing data in the PDU Action file.
    02/28/2017 15:42:00 System: Initializing data in the Syslog file.
    02/28/2017 15:42:00 System: Configuration change. Syslog, re-mapped local severity: 'None'.
    02/28/2017 15:42:00 System: Configuration change. Syslog, re-mapped local severity: 'Informational'.
    02/28/2017 15:42:00 System: Configuration change. Syslog, re-mapped local severity: 'Warning'.
    02/28/2017 15:42:00 System: Configuration change. Syslog, re-mapped local severity: 'Severe'.
    02/28/2017 15:42:00 System: Configuration change. Syslog facility.
    02/28/2017 15:42:00 System: Configuration change. Syslog server port 4 port.
    02/28/2017 15:42:00 System: Configuration change. Syslog server IP 4 address.
    02/28/2017 15:42:00 System: Configuration change. Syslog server port 3 port.
    02/28/2017 15:42:00 System: Configuration change. Syslog server IP 3 address.
    02/28/2017 15:42:00 System: Configuration change. Syslog server port 2 port.
    02/28/2017 15:42:00 System: Configuration change. Syslog server IP 2 address.
    02/28/2017 15:42:00 System: Configuration change. Syslog server port 1 port.
    02/28/2017 15:42:00 System: Configuration change. Syslog server IP 1 address.
    02/28/2017 15:42:00 System: Configuration change.
    02/28/2017 15:42:00 System: Initializing data in the EventLogConfiguration file.
    02/28/2017 15:42:00 System: Initializing data in the Event Action file.
    02/28/2017 15:41:58 System: Configuration change. NTP GMT offset.
    02/28/2017 15:41:58 System: Configuration change. Secondary NTP server address.
    02/28/2017 15:41:58 System: Configuration change. Primary NTP server address.
    02/28/2017 15:41:58 System: Initializing data in the NTP file.
    02/28/2017 15:41:58 System: Initializing data in the Diagnostic file.
    02/28/2017 15:41:58 System: Initializing data in the File Transfer file.
    02/28/2017 15:41:58 System: Initializing data in the TFTP Client file.
    02/28/2017 15:41:58 System: Configuration change. TFTP address.
    02/28/2017 15:41:58 System: Configuration change. System XMODEMquot; user access.
    02/28/2017 15:41:57 System: Configuration change. System readonly user access.
    02/28/2017 15:41:57 System: Configuration change. System read-only user password.
    02/28/2017 15:41:57 System: Configuration change. System read-only user name.
    02/28/2017 15:41:57 System: Configuration change. Device user password.
    02/28/2017 15:41:57 System: Configuration change. Device user name.
    02/28/2017 15:41:57 System: Configuration change. System administrator password.
    02/28/2017 15:41:57 System: Configuration change. System administrator name.
    02/28/2017 15:41:57 System: Configuration change. Device administrator authentication phrase.
    02/28/2017 15:41:57 System: Configuration change. System inactivity timeout.
    02/28/2017 15:41:57 System: Configuration change. System location.
    02/28/2017 15:41:57 System: Configuration change. System name.
    02/28/2017 15:41:57 System: Configuration change. System contact.
    02/28/2017 15:41:57 System: Initializing data in the System file.
    02/28/2017 15:41:57 System: Configuration change. FTP address.
    02/28/2017 15:41:57 System: Configuration change. FTP password.
    02/28/2017 15:41:57 System: Configuration change. FTP username.
    02/28/2017 15:41:57 System: Initializing data in the FTP Client file.
    02/28/2017 15:41:57 System: Configuration change. FTP server port.
    02/28/2017 15:41:57 System: Configuration change. FTP server transfergt;.
    02/28/2017 15:41:57 System: Initializing data in the FTP Server file.
    02/28/2017 15:41:57 System: Configuration change. SSH encryption.
    02/28/2017 15:41:57 System: Configuration change. SSH encryption.
    02/28/2017 15:41:57 System: Configuration change. SSH encryption.
    02/28/2017 15:41:57 System: Configuration change. SSH port.
    02/28/2017 15:41:57 System: Configuration change. Telnet port.
    02/28/2017 15:41:57 System: Configuration change. Telnet server access.
    02/28/2017 15:41:57 System: Initializing data in the Telnet file.
    02/28/2017 15:41:57 System: Configuration change. Boot mode transition.
    02/28/2017 15:41:57 System: Configuration change. User class.
    02/28/2017 15:41:57 System: Configuration change. Boot mode.
    02/28/2017 15:41:57 System: Initializing data in the TCP/IP file.
    02/28/2017 15:41:57 System: Warmstart.
    02/28/2017 15:41:11 System: Restarting. Web user request.
    02/28/2017 15:30:56 System: Web user 'apc' logged in from 192.168.0.61.
    02/28/2017 14:47:00 System: Web user 'apc' logged out from 192.168.0.61.
    02/28/2017 14:43:56 System: Configuration change. System location.
    02/28/2017 14:43:56 System: Configuration change. System contact.
    02/28/2017 14:43:56 System: Configuration change. System name.
    02/28/2017 14:43:29 System: Configuration change. System inactivity timeout.
    02/28/2017 14:43:05 System: Event Log cleared.

    So the log survives a reboot (the 15:41 restarting and Warmstart).

    Will try power on and off to see if log still survives..

  • JasonJLee
    Jason
    Novice
    Novice
    Jason 2/28/2017 4:28 PM (in response to Jason)

    Wont post the whole log, but it does indeed continue, even after pulling the power, to remember the old log data, after I give it an address again..

    here's the top

    02/28/2017 16:14:26 System: Web user 'apc' logged in from 192.168.0.61.
    02/28/2017 16:14:00 System: Configuration change. Boot mode.
    02/28/2017 16:14:00 System: Network service started. System IP is 192.168.0.148 from manually configured settings.
    02/28/2017 16:14:00 System: Configuration change. BOOTP server address.
    02/28/2017 16:14:00 System: Configuration change. TCP/IP gateway.
    02/28/2017 16:14:00 System: Configuration change. TCP/IP subnet mask.
    02/28/2017 16:14:00 System: Configuration change. TCP/IP address.

    I've cut a lot out at this point... but here is where the 'coldstart' happened..

    02/28/2017 16:11:30 System: Configuration change. Boot mode.
    02/28/2017 16:11:30 System: Initializing data in the TCP/IP file.
    02/28/2017 16:11:30 System: Coldstart.
    02/28/2017 16:10:01 System: Web user 'apc' logged in from 192.168.0.61.
    02/28/2017 15:59:00 System: Web user 'apc' logged out from 192.168.0.61.
    02/28/2017 15:55:59 System: Web user 'apc' logged in from 192.168.0.61.
    02/28/2017 15:49:09 System: Web user 'apc' logged out from 192.168.0.61.
    02/28/2017 15:45:45 System: Web user 'apc' logged in from 192.168.0.61.
    02/28/2017 15:45:28 System: Network service started. System IP is 192.168.0.148 from manually configured settings.
    02/28/2017

    15:45:28

    System: Configuration change. Boot mode.

    So the time and date setting and log is surviving either warm or cold restarts...... so some part of the system is holding settings without any power...

  • JasonJLee
    Jason
    Novice
    Novice
    Jason 2/28/2017 6:45 PM (in response to Jason)

    OK I changed the time zone settings to see if it would take that, and it now wont come back up at all, just fixed red led and no number display or power coming on... I think the unit is now completely dead.

    Will have to get it replaced from the seller.

    Thanks for trying to help.

  • ipicKedawinna
    Angela
    =S= Representative
    Angela 2/28/2017 7:10 PM (in response to Jason)

    Hi Jason,

    No problem. Do you have the first six digits of the serial number? We can see the age of the unit..as the unit gets older, of course the likelihood of these types of things increases as the product age goes up.

    It does seem strange that some settings would keep and others not. I am not sure specifically what it means at the hardware level and what component is the culprit but I agree with you there is a problem and it should be replaced.

  • JasonJLee
    Jason
    Novice
    Novice
    Jason 29 days ago (in response to Angela)

    Hi,

    I thought I replied yesterday, but there is nothing here...

    From the bottom of the device,

    JA040400

  • ipicKedawinna
    Angela
    =S= Representative
    Angela 29 days ago (in response to Jason)

    Hi Jason - no problem. It was manufactured in the 4th week of 2004 so quite old now. As we discussed, this type of problem for a unit of this age is not unexpected.

    Definitely think you should get your money back..

  • afzal
    Afzal
    Novice
    Novice
    Afzal 16 days ago (in response to Angela)

    dear angela,

                      will you tell me about apc  ups surt-d 3000xli or 5000xli model .how can we change the serial number of ups and how can we change  the value of callibration .

    thanks

    best regards

    sher afzal

  • wpasquil
    Bill
    =S= Representative
    Bill 16 days ago (in response to Afzal)

    Hi,

    This is a duplicate post and does not belong attached to a post concerning AP7920. You post to http://forums.apc.com/spaces/5/smart-ups-symmetra-lx-rm/forums/general/10401/surt3000xli-unable-to-access-through-hyper-terminal 12 days ago.

    The SURTD model Smart-UPS utilize Microlink communication protocol so serial communications is limited as noted in the first post. Older models such as SUA Smart-UPS utilized UPSLink which allowed for greater communication via serial comm. Unfortunately MicroLink does not allow for programming of the UPS like UPSLink does. 

    The reason new model Smart-UPS utilize MicroLink is because UPSLink is based on ASCii characters. We were running out of available characters which was limiting the ability to add to new features so the change was made to MicroLInk protocol.

    Sorry for the inconvenience. 

  • Page 1 of 1 (10 items)
Choose your language:  English  
powered by Communifire
Version 5.0.5741.40378