Page 1 of 2

incvisu log

Posted: 03 Aug 2009 09:33
by thkim81
hi~

i first writing post .

i concerned this logs...

what means this log? when is wake up logs?

pls answer my question.


03/08/09 14:29:45 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 3
03/08/09 14:29:45 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 4
03/08/09 14:29:46 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 3
03/08/09 14:29:47 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 4
03/08/09 14:30:04 000001M|001/09/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 248
03/08/09 14:30:04 000001M|001/09/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 248
03/08/09 14:30:16 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 3
03/08/09 14:30:16 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 4
03/08/09 14:30:17 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 3
03/08/09 14:30:17 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 4
03/08/09 14:30:30 000001M|004/26/-/---|=2:4408=INT-IP Ethernet error code 4 (status 1 0 0xca8 0x00 0x00)
03/08/09 14:30:55 000001M|001/09/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 248
03/08/09 14:30:55 000001M|001/09/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 248
03/08/09 14:31:06 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 3
03/08/09 14:31:06 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 4
03/08/09 14:31:07 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 3
03/08/09 14:31:07 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 4
03/08/09 14:31:09 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 3
03/08/09 14:31:09 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 4
03/08/09 14:31:10 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 3
03/08/09 14:31:11 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 4
03/08/09 14:31:12 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 1 , value : 4 3
03/08/09 14:31:12 000001M|001/10/-/---|=0:3660=status of 8KFS (0 is OK, 1 is KO): 0 , value : 4 4

Re: incvisu log

Posted: 03 Aug 2009 15:40
by tincho.rn
Hi. You can use incinfo command to know a little more about a incident. For these incident execute: incinfo US0 3660 (incinfo <language> <inc number>)
For this incident you get an advise to reboot the INTOF.
Then always post your release and some information about the configuration. Maybe someone knows that this is a known bug.
Regards.

Re: incvisu log

Posted: 03 Aug 2009 16:43
by tot3nkopf
It looks like your INTOF is not synchronised ---> possibel synchro problem between shelfs.

Post output for these commands:
infocs
config 1
config x
config y
where x is the shelf to which INTOF on position 1-10 connects to
and y is the shelf to which INTOF on position 1-9 connects to

Re: incvisu log

Posted: 05 Aug 2009 02:21
by thkim81
tot3nkopf

your reply is very useful...thank you

and then I entered command and below the result

but i don'n know wht means that message


> infocs

Wed Aug 5 15:13:18 KST 2009


+----------------------------------------------------------------------+
| N_CR | N_CPL | TYPE | N_ACCES | PRIO | SYNC_CLOCK | TG/LK |
+----------------------------------------------------------------------+
+----------------------------------------------------------------------+

+---------------------------------------------------------------------+
| Synchronization on global domain |
+---------------------------------------------------------------------+
+---------------------------------------------------------------------+
| Synchronization on domain no 1 |
+---------------------------------------------------------------------+
| N_CR | N_CPL | TYPE | N_ACCES | PRIO | SYNC_CLOCK | TG/LK |
+---------------------------------------------------------------------+
| 1 | 25 | NPRAE | 1 | 200 | SYNCHRO | TG:30 |
| 1 | 25 | NPRAE | 0 | 200 | POT_SYNCHRO | TG:30 |
| 1 | 1 | NPRAE | 0 | 200 | POT_SYNCHRO | TG:10 |
| 1 | 3 | NPRAE | 0 | 201 | POT_SYNCHRO | TG:10 |
+---------------------------------------------------------------------+
+---------------------------------------------------------------------+
| Synchronization on domain no 2 |
+---------------------------------------------------------------------+
| N_CR | N_CPL | TYPE | N_ACCES | PRIO | SYNC_CLOCK | TG/LK |
+---------------------------------------------------------------------+
| 2 | 0 | NPRAE | 0 | 200 | SYNCHRO | TG:10 |
| 2 | 9 | NPRAE | 0 | 201 | POT_SYNCHRO | TG:10 |
+---------------------------------------------------------------------+


+========================== Synchro DECT ==================================+

+--------------------------------------------------------------------------+
| N_CR | N_CPL | TYPE | DECT_CLOCK | Depending Crystals |
+--------------------------------------------------------------------------+
+--------------------------------------------------------------------------+


+========= campus synchronization via INTOFS ====================+

this node 1 is SLAVE of campus synchronization (master node = ?)
synchro = PHASE_NO_OPERATION (phase shift values = 0,0)
info1=0 info2=0 info3=0 info4=0

Re: incvisu log

Posted: 05 Aug 2009 02:56
by thkim81
tincho.rn !!

your reply thank you .....

as your reply i do reset th intof board sync lamp turn on red

but that after few minutes voice guide is gone on the GPA2 board .

and intof sync lamp ever.

why do that incident is occuerence ?

i attachement the log file.

pls reply my question.....

Re: incvisu log

Posted: 05 Aug 2009 04:57
by tot3nkopf
Try to change the sync priority of the NPRAE accesses from positions 2-0 and 2-9 from 200 and 201 to 255, then reset the INTOF's on the positions 1-8, 1-9 and 1-0 and see if SYC problem comes back.

please post
config 1
and
config 2
command output.

Re: incvisu log

Posted: 05 Aug 2009 10:16
by thkim81
i atached config 1, config 2 , config 4

now my site configuration is application server ,ACT shelf - 3EA and version is 9.0.31.b

Shelf 1(config 1) is main Shelf 2(config 2) and Shelf 4(config 4) are Peripheral

Each shelf entered board had configed in NPRAE boards that sync priorty 200,201,202

refer to attachment infocs log file

another thing i wonder one.

when is the occurence incvisu logs ?

ex> PCM : Unexcepted event , MIC?SYNC access , Alarm : SET resources quantity critical etc...

PS

i traced mtracer that observation below strange log

what is that log mean ?


CPL_CPU_MSG_DEBUG_CPL ipcSend error: -7 :o :?

Re: incvisu log

Posted: 10 Aug 2009 03:57
by chatchennai
I guess the sync prio for the crystal hardware architecture should be from 0 to 199. The range 200 to 255 is used for Common hardware.

Re: incvisu log

Posted: 10 Aug 2009 15:18
by tot3nkopf
Did you even tried what I told you to do?

Re: incvisu log

Posted: 10 Aug 2009 23:10
by thkim81
sure!

I did it that your recommend

but sync is uncomportable not yet.

and sync priority is reconfigured immeditely.

and uploaded attached on previous reply.

Do i more than the configure for solution ? :(


p.s.

your reply like sunshine to me

thanks.