Cannot SSH on FMC 4500 after upgrading to 6.5.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-15-2019 09:39 AM - edited 02-21-2020 09:42 AM
Hello,
After upgrading our FMC 4500 to 6.5.0, we can no longer SSH into it.
Here are the symptoms:
1. Before upgrade, we could successfully use Putty and SecureCRT to access CLI via SSH
2. We are trying to use Putty and SecureCRT and neither emulator is working after the upgrade.
3. SecureCRT says "password authentication failed" see pic
4. Putty says "access denied" see pic
5. We have verified usernames and pw's of people attempting to access and they have admin rights.
6. We have attempted multiple users
7. We are not using external authentication. All of our users have local accounts to the FMC
8. See attached FMC Log file too
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2019 06:42 AM
We are having a similar issue as well. Upgraded to 6.5.0 and not we are no longer able to use SSH. Has anyone else seen this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2019 07:05 AM
@TW80CJ5 Your log file was not attached.
Did you check that you are running current versions of your emulators (putty and SecureCRT)? I have seen customers running really old putty that started failing when they upgraded their network equipment that had quietly deprecated older ciphers.
I have a couple of FMCv appliances running 6.5 and have no problem with ssh access. I don't have any hardware-appliance FMCs on 6.5 just yet though.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2019 07:07 AM
Our 4500 is on a physical box...no VM's...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-19-2019 10:48 AM
In version 6.5.0, there are some deprecated commands. Per the Help documentation on the Web GUI, the only user that has access to the CLI is the admin account. When we attempted to access the CLI via SSH, we still couldn't connect.
We ultimately had to reboot the FMC and select option 4 to reset the local admin password via the console. Once we did that, we connected!!!!
