Reset Search
 

 

Article

Why is the Error 'Cannot assign valid AD at the Login Session' returned after downgrading from 5.0.x to 4.1.x?

« Go Back

Information

 
TitleWhy is the Error 'Cannot assign valid AD at the Login Session' returned after downgrading from 5.0.x to 4.1.x?
Question
After downgrading from 5.0.x to 4.1.x, the user and admin account logins no longer work. The failure message Cannot assign valid AD at the Login Session is returned after the login failure.
Environment
Answer
After the downgrade, the userDB database file was not properly converted to the 4.1.x format, which caused the error and the login to fail.
  1. Power cycle the switch and get into Boot PROM (Hit ESC during AutoBoot)
  2. Type 3 at the prompt to open the command shell
  3. Type setenv bootargs 'root=/dev/sda$prt rootfstype=ext4 quiet S'
  4. Type saveenv
  5. Type reset
  6. Type mount -vo remount,rw,noatime /
  7. Type mount /dev/sda2 /mnt
  8. Type cp /etc/fabos/user.db /etc/fabos/user.db.bkup
  9. Type cp /etc/fabos/user.db.default /etc/fabos/user.db
  10. Type bootenv bootargs 'root=/dev/sda$prt rootfstype=ext4 quiet'
  11. Type "partman -r" to reboot

This issue is fixed in NOS 5.0.1b.
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255