login issue

Hello,

I recently purchased used A10 6430 antiddos ,I plugged it in and powered it on, and used a console cable to login to it.
after a moment it shows me
“localhost login:”
I tried (admin,reset,install,a10…etc) almost everything but to no avail
anyone can help me with that ?

You can try the administrator password recovery procedure:
This procedure can only be performed through the security console, and only within the first five minutes of rebooting the ACOS device.

1. Find and record the serial number on the back of the A10 
2. Reboot the ACOS device.
3. Connect to the serial console.
4. When prompted for the user name and password, enter the following:
User Name: reset
Password: serial number for your device
Use the serial number recorded in step 1.
5. After logging in, the CLI presents the following questions:
a. Do you want to reset admin password to default?[y/n]:
Answering y to this question resets the admin user name and password to the factory default admin
and a10.
b. Do you want to reset enable password to default?[y/n]:
Answering y to this question resets the enable password to the factory default, which is no password.
c. Do you want to erase startup config?[y/n]:
Answering y to this question clears the startup config, thus returning the device to its factory default
settings.
6. Answer y to the first question so that you can log on to the device; answer the other two questions as
desired for your needs.
7. After you log on to the device, change the admin password for security purposes.

Thanks for your reply
unfortunately, I tried “reset” but it did not accept it
note that it did not even move to password prompt, stuck in “localhost login:”

anyone ?

You could try booting from the other boot image location. After initial POST, you should see a prompt to hit ESC to select boot image. Try both Primary and Secondary to see if we can get a prompt other than “localhost”

I tried the secondary image


same, but when I enter something two additional lines shows
CentOS
Kernel

anyone?

Unfortunately, this sounds like an underlying image issue, and the device will need to be reviewed by TAC. I apologize for the inconvenience.