Losing last character of username after AOS upgrade (2.x -> 3.7)

[Anonymous user]

I have been updating some AOS on our Switch Rack PDU's, mainly AP7921. When upgrading AOS, all username with 10characters are getting trunk to 9, losing the last one. Accounts with less then 10 are ok. Is there a fix for that?

thank you

[Erasmus_apc]

Have both parts (AOS/APP) of the firmware upgrade completed successfully before going into the web GUI and experimenting with user names and passwords? Can you verify that the upgrade completed successfully by viewing the firmware AOS/APP version in the web GUI under "Administration" -> "General" -> "About"? Are you using any special characters in the user name? Or, is there something going on during the firmware upgrade itself that I may be misunderstanding?

[Anonymous user]

Yes both parts have been upgraded. The upgrade works fine when username is less than 10 character. Even after the upgrade, if I create a username with 10 characters it works OK. I looks like during the reconfiguration , the AOS itself skips the 10th char. No special char in username, only numbers and letters. Upgrades are sucessful (AOS 3.7 is alot different than 2.7). I ftp the aos, then upon reboot the rpdu. more than 200 pdu's were upgraded successfully using this method and only 10 characters username have had their last char trunk.

[Erasmus_apc]

We are investigating a complaint along these lines internally, but as far as I can see it should not affect web GUI log-in/out functionality and after the card is up and running the truncation should only apply to what the user would see in the event logs for the unit.

[Anonymous user]

It's not only affecting the display of the username but the login too. Login minus the last char works. The initial username not.

[Erasmus_apc]

Alright, have you tried resetting to defaults except TCP/IP and then recreating an experimental user name and password? I have been messing around with an AP79xx series Switched RPDU we have here with 3.7.0 firmware and the 10 character limit isn't changing for me whether I change the admin user name or a device user, etc. The firmware upgrade (reflashing back to the same version, 3.7.0) also works fine.

The user name/pass I used for admin each time was: apcapcapc1/apcapcapc1
For device user: device1111/apcapcapc1

[Anonymous user]

After the upgrade, I have no problem creating a 10 char user. The goal is not to have to recreate the users. It's only happening after upgrading the AOS, must be something happening in the reconfiguration process. It happens when passing from 2.7 to 3.7

Message was edited by: tms

[Erasmus_apc]

I understand the nature of the concern and I will have to look into it. Like I said, flashing the firmware worked fine for me. I also for kicks downgraded the firmware, and then ramped back up to 3.7.0. If there is anything in terms of a "fix" that I find I will post.

[Anonymous user]

Do you have any news on that? Is there something I could do to help? Is there a way that I could send you the current firmware of a PDU before I do an update so you could use that for test?

[Erasmus_apc · Accepted solution]

You can post the file you have used as an attachment, that's fine. I have the latest firmware revision from our website and as I said before it worked fine with me on both the PDU at my desk and a PDU in our APC lab. I am still investigating as to whether this is a widespread occurrence or not...so far I haven't heard of it in another case.