Cisco Secure Firewall Management Center Virtual - BYOL
Cisco Systems, Inc. | 7.6.0-113Linux/Unix, Other 7.6.0-113 - 64-bit Amazon Machine Image (AMI)
It works
After an initial install of 6.2.2 in Apr 2018, where it took approximately 50+ minutes to setup/install I got it working (check the instance console to see progress) Trying to connect before it is completely setup will result in issues connecting to it via SSH.
Just rememebr to mention to cisco that you are using a FMCv when contacting support about anything.
- Leave a Comment |
- Mark review as helpful
Setup worked when following instructions
I saw a lot of poor reviews due to problems logging into the FMC after install. Following the instructions on Cisco's website gave me no trouble at all, and I was able to log in after setup was complete.
https://www.cisco.com/c/en/us/td/docs/security/firepower/quick_start/aws/fmcv-aws-qsg.html
It seems some people may have missed the following steps:
- During instance creation: "Under Advanced Details, add the default login information."
Sample Login Configuration:
#MC
{
"AdminPassword": "
"Hostname": "
}
- When setup is complete (after approximately 30 to 40 minutes), the Instance Screenshot should show a message similar to âÂÂCisco Firepower Management Center for AWS vW.X.Y (build ZZ)âÂÂ... You should then be able to log in to the newly created Firepower Management Center Virtual using SSH or HTTPs.
Works Great
Seamless transition from on-premise appliance to this. Performance is great with the recommended EC2 size and the documentation is accurate. This makes it a no brainer to deploy.
Followed instructions - don't work
Spun up,went all ok, can ping the device.
Tried to access via ssh and used admin user like so:
ssh -l admin
Asks for password - cannot access VM.
Instructions in AMI description to not work:
Connect to your instance using an SSH client, and the private SSH key selected or created earlier in these steps. Example: ssh -i mykeypair.pem admin@myhostname.compute-1.amazonaws.com 12. If you need management access to your FMCv from outside of your VPC, you will need to create an Elastic IP and associate it with one of the FMCv network interfaces. 13. Once SSH has connected, you may begin configuring your instance.
Just need to follow instructions
Had problems at first but once I re-read instructions and used ADMIN instead of ROOT, everything went ok.
Cisco Support is very helpful as long as you describe the problem correctly.
Must use the correct terms. Like FMCv on AWS and FTD on AWS or FMC outside AWS.
Cant even login
Prompts for password, default Admin123 does not work.
Server refused certificate key. Unable to access CLI/HTTPS.
Dont bother calling Cisco, would not assist.
You just cant access 6.2 version
No web access, ssh always ask for password if you follow instruction on cisco site with static password set up it do not work... it looks this version do not work for management vm...