cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1424
Views
8
Helpful
8
Replies

Cisco FMCv 7.0.5 - Cant be access with GUI and SSH

Agung1007
Level 1
Level 1

Hi team,

Our customer have some issue with their FMCv (version 7.0.5).

The issue noticed on 2 days ago, that the FMCv cant be access by GUI and SSH (attached, screenshot when try to access to GUI FMC)

what causing this?

do everyone have a same experience?

(fortunately the FTD managed device is doing fine)

 

Thanks,
Best Regards

1 Accepted Solution

Accepted Solutions

balaji.bandi
Hall of Fame
Hall of Fame

Try to reload FMC and test it.

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

View solution in original post

8 Replies 8

balaji.bandi
Hall of Fame
Hall of Fame

Try to reload FMC and test it.

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

thanks for the feedback.

If we reload the FMC by KVM console, it will not causing an outage?

if you reboot the FMC it does not affect the FTD only the FTD is the one handling the traffic. FMC is only managing the FTD so in short you can shutdown or reboot FMC anytime as long as there is not on going deployment.

With the Webpage prompting an Error, this is a good fix.

ALSO,

If you do not receive a webpage or SSH response, you may be getting blocked from the Access-List. Go to a working station, and check the GUI by clicking on the Gear>>Configuration>>Access Rules. You may not have a whitelisted IP address that allows 443/22. This commonly happens when moving imported copies/backups around.

FMC is a management box so you will not have any service impact.

Policies can not be pushed, but any way your FMC GUI access issue so no one can modify the policies.

 

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

Agung1007
Level 1
Level 1

Hi all,

thanks for the response.
after Force Restart (shutdown VM - Startup VM) the issue is able to solve,

but unfortunately we dont know what causing it
*on the Health Event only define "core-compressor exited X time(s)"

most likely some services in the FMC was not able to start up automatically or got stuck somewhere in the boot up process.

Correct might be some services which stop responding. Can verify with logs.

Review Cisco Networking for a $25 gift card