SMA trailblazer not starting

[Steflstefan]

After upgrade vSMA to 13.6.1-193 trailblazer cann't be started.

sma> trailblazerconfig status

trailblazer is not running
sma> trailblazerconfig enable

trailblazer is enabled.
To access the Next Generation web interface, use the port 4431 for HTTPS.
sma> trailblazerconfig status

trailblazer is not running

sma> version

Current Version
===============
Product: Cisco M100V Content Security Virtual Management Appliance
Model: M100V
Version: 13.6.1-193
Build Date: 2020-05-27
Install Date: 2020-06-10 14:22:03
Serial #: --deleted--
BIOS: 6.00
CPUs: 2 expected, 2 allocated
Memory: 6144 MB expected, 6144 MB allocated
RAID: NA
RAID Status: Unknown
RAID Type: NA
BMC: NA

Ports 8443, 6080, 6443, 4431 are open on firewall.

Can I find a log with more information?
What can we do to investigate the issue?

Thanks Stefan

[ppreenja]

Hi,

Make sure that your DNS is able to resolve the hostname otherwise trailblazer won't be enabled.

For more information on trailblazer configuration please check on the below link:

https://www.cisco.com/c/en/us/support/docs/security/content-security-management-appliance/214391-administrative-details-on-trailblazer.html

I hope the above helps.

Cheers,
Pratham

[Steflstefan]

Hi Pratham,

sorry, I haven't mentoned before. DNS resolution works.
SMA is single-homed with one IP address. Both, appliance host name and USQ host name will be resolved to correct ip address.

sma.ourtestdomain.ch> nslookup sma.ourtestdomain.ch

A=172.25.1.54 TTL=30m
sma.ourtestdomain.ch> nslookup usq-sma.ourtestdomain.ch

A=172.25.1.54 TTL=1h

Any hint?

I think trailblazer has worked before upgrade SMA to 13.6.1-193, but I m not sure.
On our productive SMA, running 13.0.0-249 on M300V, trailblazer can be enabled and disabled as I want.

Thanks and Greez

Stefan

[Kalipso]

Hello @Steflstefan, 

Did you find out why trailblazer wouldn't start ?

I have the same issue here. I'm trying to use the new webUI, but trailblazer doesn't want to start on one member.

The other member of the cluster is running well.

The hostname is well resolved.

(I have ESA cluster on C390 appliances)

Marie

[rolelael]

Same issue here with version 13.6.2-023

xxxxxx> trailblazerconfig enable

trailblazer is enabled.
To access the Next Generation web interface, use the port 4431 for HTTPS.

xxxxxx> trailblazerconfig status

trailblazer is not running

Hostname is resolvable ( on internal dns )

However I also had this :

trailblazerconfig enable 4431

Port 443 is already in use

Any idea ? I unchecked https in interfaceconfig... and can enable it now, but status says as you can see disabled.

[rolelael]

Guys, I did the following and got it enabled :

- so as in my post before unchecked https 443 in web gui , commit

- Enabled trailblazer on 4431 -> started

- Status = disabled

Then I went in cli to interfaceconfig and re-enabled https on 443 -> commit

Issued again :

trailblazerconfig enable

trailblazer is already running.

 trailblazerconfig status

trailblazer is running with https on 4431 port.

So strangly enough it's running now, after I refreshed the interfaceconfig via CLI

[Kalipso]

For me it was resolved by adding a specific entry for DNS.

Because the hostname of ESA was not well resolved : the hostname uses a private domain, and the default DNS is external and doesn't know the private domain.

So I added a DNS server for my specific private domain and then the trailblazer would start normally.

[crengifo]

Hello all,

Thank you for bringing this up!

For those who are still experiencing the same behavior reported here or if you found this post because trailblazer won't initialize and you're looking for a way to get it to work, I would like to share with you the following article that may help you find a way to resolve this issue:

Why Does Trailblazer Fail to Initialize?

https://www.cisco.com/c/en/us/support/docs/security/content-security-management-appliance/215994-why-does-trailblazer-fail-to-initialize.html

I hope you find it helpful!

Regards,

Cristian Rengifo

[t.regner]

Maybe this will help you 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvv13564

[Claritine]

I've run into this with our ESA. The solution for me was to rename the management interface back to "Management"

BUG ID: BIGID-CSCvo83400