Empty MTA trace for Avaya CM 1

[hcmbmt]

Enable MST trace for PMS message but when download the log file, It's empty, Is there any missing step to get it?
1.Disable MST and there is a messages out

2. Check list mst to check messages are generated

3. Putty to CM and enter command: /usr/bin/sudo /opt/ecs/bin/logc -c 'view%mta' -t 1009:1606-1009:16:29 > /tmp/mstdecoded8.m

3. WinSCP to CM at tmp folder to get the file but it's no content


any idea for this issue.
I also try login to CM Web Administration - diagnostic - MTA but nothing.

btw, is there any tool to read the raw mst messages?

 

[john3voltas]

I am assuming this is not your first time running an MST on Aura products.
But, are you sure you enabled the log MST when you ran the change MST?
Just checked your post again and it is clear that there is MST output.

EDIT
You've got a typo in your command.
Check the 16:29 in your CLI command.
Remove that colon and try again.

 

[hcmbmt]

Yes, that's my typo. After my post, I edit and try again but also nothing. I reset mst. Create another one

with correct format:
/usr/bin/sudo /opt/ecs/bin/logc -c 'view%mta' -t 1009:1749-1009:1753 > /tmp/mstlogfile2.m

But the generated file is also 1kb.

 

[john3voltas]

Heck, try to run a full day:
/usr/bin/sudo /opt/ecs/bin/logc -c 'view%mta' -t 1009:0000-1009:2359 > /tmp/mstlogfile2.m

Maybe it's something to do with timezones or something. Running a 24h you will probably hit it.
Because there's no doubt there are messages to be extracted. From your print, there's 220 of them...
Also, curious to know the output of "date" from the CLI.

 

[JefferP]

logc -t today MST > /tmp/msttrace.m
OR
logc -t today MST | logmst > /tmp/msttrace.M if trace analyzer is selected on 'ch mst' screen, then you can use
mta msttrace.M | imt > /tmp/trace

Hope you have a beany with a propeller

 

[hcmbmt]

Hi all,
Thank you so much for your support.
@john3voltas: I followed your advice, print full day and I got the result:


@JefferP : your command also get the log but It's raw data.

 

[hcmbmt]

@JefferP : Sorry. I missed one line of your post.
I use "logc -t today MST | logmst > /tmp/msttrace.M" as trace analyzer is enable.
then I got the mstttrace.M


Run the "mta msttrace.M | imt > /tmp/trace" but it shows error

 

[john3voltas]

@hcmbmt
Sorry but now I feel kinda lost.
It seems that eventually you were able to extract your analyzed MSTs. But did you figure out what was preventing you from extracting them in the first place?
Was it a difference in the server clock compared to your watch?
Would love to find out what happened to be the culprit.
Oh, and I was most glad that I could help on this instance. ;-)
Cheers

 

[JefferP]

Looks like imt is not loaded on your CM or you need an Avaya login to access it.
mta msttrace.M
is all you're going to get. At least that should convert from hex to something readable.

 

[hcmbmt]

@hcmbmt
Sorry but now I feel kinda lost.
It seems that eventually you were able to extract your analyzed MSTs. But did you figure out what was preventing you from extracting them in the first place?
Was it a difference in the server clock compared to your watch?
Would love to find out what happened to be the culprit.
Oh, and I was most glad that I could help on this instance. ;-)
Cheers

I used start and end time shown in "status mst" - assuming that that match with server clock but no idea why there's no output. Anyway, next time i'll expand the time range to cover the full duration.