Avaya S8300 Logs with Errors

[FXLL]

Hi Team,

can anyone help me to know what the lines below means?
I have multiple errors like this ones in my Avaya LSP server logs

20161101:163531245:1044994:initmap(28871):MED:[3MIN OCC: ST+CP=3.09% ST=2.98% CP=0.11% SM=7.29% AV=89.62% TC=0]
20161101:163533243:1044995:hmm(28863):MED:[CM6_proc_err: pro=7204,err=201,seq=19000,da1=16784384(0x1001c00),da2=0(0x0)]
20161101:163533243:1044996:com(28854):HIGH:[COM_ERR: err=172, da1=322(0x142), da2=112(0x70), da3=604(0x25c)]
20161101:163703240:1044997:hmm(28863):MED:[CM6_proc_err: pro=7204,err=201,seq=19000,da1=16784384(0x1001c00),da2=0(0x0)]
20161101:163703241:1044998:com(28854):HIGH:[COM_ERR: err=172, da1=323(0x143), da2=112(0x70), da3=604(0x25c)]
20161101:163831242:1044999:initmap(28871):MED:[3MIN OCC: ST+CP=2.40% ST=2.30% CP=0.10% SM=5.82% AV=91.79% TC=0]
20161101:163833242:1045000:hmm(28863):MED:[CM6_proc_err: pro=7204,err=201,seq=19000,da1=16784384(0x1001c00),da2=0(0x0)]
20161101:163833242:1045001:com(28854):HIGH:[COM_ERR: err=172, da1=324(0x144), da2=112(0x70), da3=604(0x25c)]
20161101:164003244:1045002:hmm(28863):MED:[CM6_proc_err: pro=7204,err=201,seq=19000,da1=16784384(0x1001c00),da2=0(0x0)]
20161101:164003244:1045003:com(28854):HIGH:[COM_ERR: err=172, da1=325(0x145), da2=112(0x70), da3=604(0x25c)]
20161101:164131241:1045004:initmap(28871):MED:[3MIN OCC: ST+CP=2.47% ST=2.38% CP=0.10% SM=6.27% AV=91.26% TC=0]
20161101:164133241:1045005:hmm(28863):MED:[CM6_proc_err: pro=7204,err=201,seq=19000,da1=16784384(0x1001c00),da2=0(0x0)]
20161101:164133242:1045006:com(28854):HIGH:[COM_ERR: err=172, da1=326(0x146), da2=112(0x70), da3=604(0x25c)]
20161101:164303243:1045007:hmm(28863):MED:[CM6_proc_err: pro=7204,err=201,seq=19000,da1=16784384(0x1001c00),da2=0(0x0)]
20161101:164303243:1045008:com(28854):HIGH:[COM_ERR: err=172, da1=327(0x147), da2=112(0x70), da3=604(0x25c)]
20161101:164431240:1045009:initmap(28871):MED:[3MIN OCC: ST+CP=2.62% ST=2.52% CP=0.10% SM=7.14% AV=90.24% TC=0]
20161101:164433241:1045010:hmm(28863):MED:[CM6_proc_err: pro=7204,err=201,seq=19000,da1=16784384(0x1001c00),da2=0(0x0)]
20161101:164433241:1045011:com(28854):HIGH:[COM_ERR: err=172, da1=328(0x148), da2=112(0x70), da3=604(0x25c)]
20161101:164603242:1045012:hmm(28863):MED:[CM6_proc_err: pro=7204,err=201,seq=19000,da1=16784384(0x1001c00),da2=0(0x0)]
20161101:164603242:1045013:com(28854):HIGH:[COM_ERR: err=172, da1=329(0x149), da2=112(0x70), da3=604(0x25c)]

 

[kyle555]

Nothing much? 3 min occ is just how busy the CM processor is - so, static+call processing occupancy is 3.09%.
The others could mean something, but probably nothing and you wouldn't look in to them unless some problem you're investigating led you there.

 

[FXLL]

The issue that I'm investigating is in regards the PRI Sync Source,
I had configured the 2 MM710 cards the first one with the primary sync source , suddenly at 10/01 they lose the sync source :


This is how it was configured:

SYNCHRONIZATION CONTROL: --- Local ---

SOURCE MM or VoIP STATUS FAILURE
--------- ------------------- ----------------------- ---------------
Primary v2 Active None
Secondary v3 Standby None
Local v0 Standby None

Active Source: v2 Sync Source Switching: Enabled

Done!

This are the log entries:

<187>Nov 01 16:38:41 CSTLAVAYAG450-2 -NoTag: -NoUTC 2016 375 1 mediagateway.g450 | 0 SYN-TRPMAJNO[VOICE-Error: Clock sync failure CLEAR, ID=7001005274

<187>Nov 01 16:38:16 CSTLAVAYAG450-2 -NoTag: -NoUTC 2016 370 1 mediagateway.g450 | 0 SYN-TRPMAJNO[VOICE-Error: Clock sync failure FAULT, ID=7001005274


And now they are sync to the local source:


SYNCHRONIZATION CONTROL: --- Local ---

SOURCE MM or VoIP STATUS FAILURE
--------- ------------------- ----------------------- ---------------
Primary Not Configured
Secondary Not Configured
Local v0 Active None

Active Source: v0 Sync Source Switching: Enabled

Done!

 

[kyle555]

I think you just need to put them back in and that the gateway removed them because of a lot of failures from them.

Sync source switching enabled lets you fall back from one source to another if you lose the circuit, but if that circuit starts being really funky, the gateway would just give up and go in free run - I think that's what you're dealing with.
If you put them back, does it work ok?