DLY-MTCE MINOR

[BENANDSERA]

Hello Everyone

G3 Version 14 Platform 6 S8700 CM
So I just started my new job and was looking at my alarms and noticed I had a dly-mtce(Translations audit and saved failure) minor that occurred on April 26th of this year. Can’t find the error type number code.

The translation backups are scheduled every day at 1am and backup history and logs all look good up to today’s date and even the dates before and after the alarm occurred. So I’m assuming that my backup of translations are good?

If my history and backup logs all show good backups before and after that date, then why do I have an active alarm? Was this just a single event where maybe the audit and or backup failed but now everything is normal? If so, why won’t this alarm clear?

There are no other alarms on this system.
Thanks for your time


"To err is human... to really foul up requires the root password."

 

[AvayaTier3]

backups may include copy of xln1 and xln2

swversion will show last translation saved timestamp as will Linux CLI "ls -l /etc/opt/defty/xln*"
If translations are not being saved, you likely have software corruption that's blocking a daily save.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[BENANDSERA]

Thanks for the quick response bsh!

I went ahead and checked the swversion timestamp and xln like you suggested. Both have translation save dates of 5/24/2016. Almost a month after the dly-mtce minor alarm that happened on April 26th. So I guess I could assume that the audit and save translations are still happening every day. Do you think the reason that I still have an dly-mtce alarm is that I'm actually backing up corrupted files or would the audit function catch that?

Thanks for your time.

"To err is human... to really foul up requires the root password."

 

[joe2938]

Have you manually done a save trans and see if this clears the alarm

 

[AvayaTier3]

Are your duplicated servers both showing same timestamps for xln1 and xln2?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[BENANDSERA]

Hey bsh

I think your question helped me find the problem, definitely pointed me in the right direction. Looks as though my duplicated server at that location could be down, unable to ping it for sure. Willing to bet that it went down on around that date and therefore is causing that alarm, just a theory though. What do you think?

"To err is human... to really foul up requires the root password."

 

[AvayaTier3]

try Linux CLI
You will known quickly

server
pingall -a



A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[BENANDSERA]

Just wanted to update what's going, I appreciate all the help from Joe and bsh.

Restored the server that was offline but I still have the dly-mtce minor alarm on the first one. Backups continue to go every night like clockwork. Timestamps for xln1 and xln2 are good, I would assume that if the files were corrupt or backup was not occurring that the time stamp for the dly-mtce alarm would change. This is only happening on the first server. Its only happened once on April 28th.

Has anyone else experienced this and if so how did the dly-mtce alarm finally clear.

"To err is human... to really foul up requires the root password."