firepower management center

[edwincharles]

Dears,

I have installed the firepower management center on the VM

I have issue with access the GUI of firepower management center

system process are starting , please wait

[soumbis12]

Dear Edwin,

Can you try once by rebooting the VM please.

[edwincharles]

Dear Soumik,

Tried rebooting , still same

messages received on vm console

[Dennis Perto]

Did you install the FMC on an ESXi server, or in VMware Workstation?

[edwincharles]

we  installed FMC on VMware Workstation

[Dennis Perto]

As far as I know, this is not supported. This may be your issue.

[edwincharles]

thanks for the update

so what is preferred

directly installing on EXSI, what is the minimum specs required

[Dennis Perto]

I will recommend installing everything on ESXi.

Minimum specs depends on the version of the FMC and the sensor. I see that you are using FMC 6.2.1.

For this I will recommend 8 virtual cores and 8GB memory, but you can go with 4 virtual cores.

[Qamar Islam]

Hi Dennis,

I also have a same issue.

Versions:

FMC: 6.2.2

FTD: 6.2.2

I allocate above mentioned specs but still GUI has a systems processes are started. Please wait error shows.

Your kind expertise needed.

Thanks

Qamar

[ahmed.morsy]

Hello,

I was also having the same Issue with the same version of the FMC 6.2.2 and FTD 6.2.2 running on VMware Workstation,

But after I letting the VM running for about 2 hours the message "system process are starting, please wait” disappeared the FMC start working normally and then I restarted the VM to make sure that it will work again it started normally and didn’t take much time as first time.

Thanks,

[Qamar Islam]

Hi Morsy,

I just changed the FMC IP address to resolve this issue.

Thanks

[z328443036]

我也遇到这个问题，但是FMC的配置已经高于官方的推荐8cpu，12G内存，workstations12。

TRANSLATION:

I also encountered this problem, but the FMC configuration has been higher than the official recommendation 8cpu, 12G memory, workstations12.

[Ariq Ibne Aziz]

Is there any solution of this login issue ? Im facing the same . changed my IP, resterted the VM but still having the same problem.

My LAB setup is done in Vmware Workstation. is there any way around ?

[anubmath]

Hello,

Check what processes are down or disabled.

Use pmtool status | grep -i gui

Share the results.

In case of down situation try

#pmtool restartbyid <service_name>

Secondly, make sure about the hardware specs for the VM.

Regards,

Anubhav

[FGR]

I have the same problem for years. Send all files you can possibly think of to Cisco. Also I self Analyzed some log files in management center (unix):

in /var/log/messages the following error repeats itself when booting FirePOWER MC.

(none):SybaseDatastore [WARN] SybaseDatastore.c:488:clientmsg_callback(): Client Library erro: severity(0) nuimber (4) origin(3) layer(5): ct_connect(): network packet layer: internal net library erro: Net-Lib protocol driver call to connect two endpoints failed.

It takes a long time starting up FirePOWER MC webinterface (system processes starting, please wait)

Even now with upgrade to 6.2.3.7-51.

Same problem. Wait a couple of hours.

Hello Mario,

Here is al piece of /var/log/messages 

On Jun22 21:46:38 I reboot the VM, after that a Sybase error repeat itselfs 

One hour later, Sysbase connects on Jun 22 22:42:19, and I can start using Firepower MC.

Jun 22 21:46:38 firepower SF-IMS[4401]: [4401] pm:log [INFO] Process 'Syncd' closed output.
Jun 22 21:46:38 firepower SF-IMS[4401]: [4401] pm:process [INFO] Process Syncd (5696) exited cleanly
Jun 22 21:46:38 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:46:40 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:46:43 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:46:45 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:46:47 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:46:49 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:46:52 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:46:54 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:46:56 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:46:58 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:47:01 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:47:03 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:47:05 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:47:07 firepower SF-IMS[4401]: [4401] pm:process [INFO] Killing DCCSM with /var/sf/bin/dccsmstop.pl
Jun 22 21:47:08 firepower SF-IMS[5009]: [5009] (none):SybaseDatastore [WARN] SybaseDatastore.c:488:clientmsg_callback(): Client Library error: severity(0) number(4) origin(3) layer(5): ct_connect(): network packet layer: internal net library error: Net-Lib protocol driver call to connect two endpoints failed
Jun 22 21:47:08 firepower SF-IMS[5009]: [5009] (none):SybaseDatastore [ERROR] SybaseDatastore.c:505:clientmsg_callback(): Operating system error number(111): Socket connect failed - errno 111 Connection refused
Jun 22 21:47:08 firepower SF-IMS[5009]: [5009] (none):SybaseDatastore [ERROR] SybaseDatastore.c:801:Connect(): Failed to connect to Sybase service after 4294960390 seconds

....

....

....

Finally, MC has a sybase connection!!!!

Jun 22 22:42:19 firepower SF-IMS[6863]: [6863] (none):SybaseDatastore [INFO] SybaseDatastore.c:808:Connect(): Connected to Sybase server after 51 seconds
Jun 22 22:42:19 firepower SF-IMS[6931]: [6931] (none):SybaseDatastore [INFO] SybaseDatastore.c:808:Connect(): Connected to Sybase server after 45 seconds