This issue is due to the presence of Cisco bug ID CSCin91851.
In this issue, when you use the router as an Secure Shell (SSH) server that authenticates to an SDI/radius backend, normal authentications work. But, neither the new PIN mode nor the Next Token mode dialogues complete successfully.
This issue is only observed in New PIN mode or Next Token mode dialogue.
For a temporary workaround, use Telnet for authentication or set virtual terminal (vty) lines to authenticate to the Radius (non-SDI) server instead.
In order to permanently resolve this issue, upgrade the router to Cisco IOS Software Release 12.4(10.1)T. Use the Cisco IOS Upgrade Planner in order to download the suggested image.
Good day, I have two Firepower 1140 firewalls configured using FMC.I am trying to setup a 1:1 NAT on it and I can't seem to get it working. We have /28 subnet from our ISP that we are using. I created a NAT with the following settings (thi...
Hello Network Security Community, We have a new FPR-1010, without additional feature subscription. What are the options to license it when both Internet access and FMC are not available? We do have a Smart account though. Thanks for ...
Good day, Has anyone done the flexconfig configurations for Dead Peer Detection (DPD) on a FTD 1120 in HA? The design idea is to have multiple sites with different vendor equipment connect to the FTD via IPsec VPN. There are 2 public ...
Hi All, wanted to know if ASA can automatically block an IP I was monitoring the ASA using SNMPv3 on UDP 161 port using a IT monitoringsuddenly i received alerts saying that ASA was unreachable but I was able to access ASDM/SSH