Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

TM Problem

Status
Not open for further replies.

Mikhen

Technical User
Mar 18, 2016
9
SE
Hi all,

I have a problem that we get an 294 alarm now and then, Se below, always at the same time. We have no other alarms that can be related to this like buffer alarms etc (See alarm log). When we look at ´the content of TM catalogue we can se that for the days this alarm occur that TM files are much smaller in size. I have not been able to identify what INF1=0 means.

We have no idea why this happen and the solution to it.

Any feedback is appreciated.

Se below for Alarm log and Fiscp.

294 TRAFFIC RECORDING INTERNAL MEMORY DATA ERASED - MIDNIGHT DUMP
DATE TIME ALP NOIF UNIT INF1
06OCT17 00:11:05 9 1 0

<ALLOP;
ALARM LOG
IDENTITY: 05-5036
VERSION: CXP1010105/4/TSWSP04/R5A

DATE: 06OCT17 TIME: 08:14:24
CLASS: 1
261 NO CONNECTION WITH OPERATOR CONSOLE
DATE TIME ALP NOIF EQU BRDID INF1
05OCT17 08:20:28 1 1 002-1-52-02 77 9

261 NO CONNECTION WITH OPERATOR CONSOLE
DATE TIME ALP NOIF EQU BRDID INF1
05OCT17 08:20:59 4 1 003-0-40-02 77 7

261 NO CONNECTION WITH OPERATOR CONSOLE
DATE TIME ALP NOIF EQU BRDID INF1
05OCT17 08:21:21 6 1 001-1-52-07 77 9

261 NO CONNECTION WITH OPERATOR CONSOLE
DATE TIME ALP NOIF EQU BRDID INF1
05OCT17 08:21:28 7 1 001-1-42-15 77 8

261 NO CONNECTION WITH OPERATOR CONSOLE
DATE TIME ALP NOIF EQU BRDID INF1
05OCT17 16:17:38 8 1 003-0-40-00 77 6

294 TRAFFIC RECORDING INTERNAL MEMORY DATA ERASED - MIDNIGHT DUMP
DATE TIME ALP NOIF UNIT INF1
06OCT17 00:11:05 9 1 0

CLASS: 0
261 NO CONNECTION WITH OPERATOR CONSOLE
DATE TIME ALP NOIF EQU BRDID INF1
05OCT17 08:20:48 3 1 003-0-50-00 77 9
RDATE RTIME
06OCT17 07:16:41
261 NO CONNECTION WITH OPERATOR CONSOLE
DATE TIME ALP NOIF EQU BRDID INF1
05OCT17 08:21:10 5 1 003-0-50-11 77 5
RDATE RTIME
05OCT17 08:47:04
261 NO CONNECTION WITH OPERATOR CONSOLE
DATE TIME ALP NOIF EQU BRDID INF1
05OCT17 16:12:17 2 2 002-1-52-03 77 8
RDATE RTIME
06OCT17 08:11:49

LAST ALREI: 05OCT17, 08:20:23

END
<FISCP:IODEV=SYSDISK1;
FILE SYSTEM CAPACITY DATA
TOTAL DISK SPACE: 245 MBYTES
SUBFS: SYSSUBFS11
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
122880 8604 12288 /SYSN/USR1
SUBFS: SYSSUBFS21
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
122880 81088 12288 /SYSN/USR2
END

Edit. The system is a TSW SP 4

<CaDAP;
CALENDAR DATA
IDENTITY=05-5036
VERSION=CXP1010105/4/TSWSP04/R5A
09:43:54
THU 12 OCT 2017
EN

Thanks in advance
 
Hi,
ADD INFO 1 = User interrupt

This means that the current TRREP operation is conflicting with the dump attempt.

\Satellite1900
 
Hi Satellite,

Thanks for answer

Ok so Addinfo1= 0 equals "User Interrupt" I didn´t know (couldn´t find it) that piece of information though I searched Alex
We have some menos (TM) running until 24:00 do you think they could cause this even though the 294 alarm always occur at 00:11?

Example

115 ROUDIO 09JAN16 31DEC17 00:00-24:00 ROU = 47
131 ROUDIO 09JAN16 31DEC17 00:00-24:00 ROU = 16
But we have more running until that hour

Edit: Of course they run from 00:00-24:00

But a curious note is that this 294 alarm does not occur every night but occasionally during the week?

//Mikael H
 
Hi Mikhen,
sorry I have nothing constructive to add but I believe that Satellite misread your alarm print as addinfo1=1 is "user interrupt". According to my documentation addinfo1=0 has no entry in the fault locating guide so it is "Undefined error. Consult an expert".

This is an example of why it is important to use formatting when copying printouts to a post.
For example-
Unformatted alarm print
CLASS: 2
344 CIL, FAULTY CONNECTION TO NIU PORT
DATE TIME ALP NOIF EQU BRDID INF1
27FEB11 08:54:03 1 1 009-0-70-04 106 1

Same print formatted using the "Pre" option (just select the text and press the Pre button.)
[pre]CLASS: 2
344 CIL, FAULTY CONNECTION TO NIU PORT
DATE TIME ALP NOIF EQU BRDID INF1
27FEB11 08:54:03 1 1 009-0-70-04 106 1
[/pre]

Much easier to read.

Good luck.
 
Hi himdp,

And thank you for your input

Probably Sattelite misunderstood yet it´s not his fault but mine. Ok so "Pre" is the one to use, thank you.

Ok so the problem is something else then. I´m cleaning my TM measurements anyway now so we can only wait and see if the problem disappear.

Any other inputs are invaluable

Thanks in advance.

//Mikael H
 
Hi again,

No idea what the solution can be? Cleaning and doing changes to active measurement (TM) didn´t help still same problem.

[pre]294 TRAFFIC RECORDING INTERNAL MEMORY DATA ERASED - MIDNIGHT DUMP
DATE TIME ALP NOIF UNIT INF1
08NOV17 00:11:00 6 1 0 [/pre]

Looked through HIMDP as well yet couldn´t find anything useful.

Any ideas appreciated.
Thank you
 
Hi,
can you print this command?
IODDP;
FISCP:IODEV=XXXXX1/2;
CNBIP:BPOS=(NIU POSITION);
DUFQP;
HIMDP;


\Satellite1900
 
Hi,
00:11 is the time, when the daily file (with the traffic measurement data) is stored to disk.
Do you run an automatic dump "DUSYI" at this time ?? (check with DUFQP)(maybe a timing problem when dumping customer data and TM-data)

The available size of your SYSSUBFS11 looks a little bit low with "8604"(8MB), (e.g more then 110MB are used)
How many LIM do your System have ? (normally uses space is ca. 30 MB + ca. 2,5 MB per Lim)
TOTAL DISK SPACE: 245 MBYTES
SUBFS: SYSSUBFS11
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
122880 8604 12288 /SYSN/USR1

You wrote, that you did "Cleaning and doing changes to active measurement..."

Have you deleted old TM-files, and do you have now more space than 8604 available ?

P.S.
TM files can be found in /sysn/usr1/acs/tm/

best regards,
Norbert
 
Hi Satellite1900,

A HIMDP for Lim 1 and a HIEDP will be provided here among other.

How do I create a spoiler that can be closed?

Just for you below Satellite 1900 tell me if you need some more information.

[pre]<IODDP;
I/O DEVICE DATA
NODE IODEV/SUBFS BPOS/EQU I/O-BUS TYPE/USAGE STATUS AUTH
SYSN - 001-0-60 - - IN SERVICE
SYSN SYSDISK1 001-0-60-0 MASTER SanDisk IN SERVICE
SYSSUBFS11
SYSSUBFS21
SYSN SYSTERMINAL 001-0-60-1 - MML - 7
SYSN MODEM 001-0-60-2 - MML - 7
SYSN DNASERV 001-0-60-4 - NETWORK/OUT IN SERVICE
SYSN LAN-MML1 001-0-60-4 - NETWORK/MML - 7
SYSN LAN-MML2 001-0-60-4 - NETWORK/MML - 7
SYSN LAN-MML3 001-0-60-4 - NETWORK/MML - 7
SYSN LAN-MML4 001-0-60-4 - NETWORK/MML - 7
SYSN LAN-MML5 001-0-60-4 - NETWORK/MML - 7
SYSN LAN-MML6 001-0-60-4 - NETWORK/MML - 7
XTRA - 001-0-50 - - IN SERVICE
XTRA ONEBOX 001-0-50-4 - NETWORK/OUT IN SERVICE
XTRA LANMML6 001-0-50-4 - NETWORK/MML - 7
XTRA4 - 004-0-60 - - IN SERVICE
XTRA4 CSTA 004-0-60-4 - NETWORK/OUT IN SERVICE
XTRA4 LAN-LIM4 004-0-60-4 - NETWORK/MML - 7
END

<FISCP:IODEV=SYSDISK1;
FILE SYSTEM CAPACITY DATA
TOTAL DISK SPACE: 245 MBYTES
SUBFS: SYSSUBFS11
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
122880 15212 12288 /SYSN/USR1
SUBFS: SYSSUBFS21
KBYTES FILES
TOTAL AVAIL TOTAL MOUNTED
122880 81088 12288 /SYSN/USR2
END

<cnbip:bpos=1-0-60;

DEVICE BOARD REVISION INFORMATION
DATE: 09NOV17 TIME: 10:00:03

BPOS BOARD/BRDID PRODUCT NUMBER REVISION STATUS ADD
/IND

001-0-60 NIU ROF 137 5396/2 R2A
CAA 1580021 R8A EXE
CAA 1580021 R7A OLD

END
<cnbip:bpos=1-0-50;

DEVICE BOARD REVISION INFORMATION
DATE: 09NOV17 TIME: 10:00:10

BPOS BOARD/BRDID PRODUCT NUMBER REVISION STATUS ADD
/IND

001-0-50 NIU2 ROF 137 5396/2 R3A
CAA 1580021 R9A EXE
CAA 1580021 R6A OLD

END
<dufqp;
DUMP FREQUENCY DATA
TIME DATE INT
22:00 09NOV17 24
END

<CLDFP;
FILE ADMINISTRATION DATA
FILE STATE
SMETH ACT
IODEV/PATH USER DEVICE STATE PRIORITY
ONEBOX CIL-1 READY/STARTED C
END

HIEDP and HIMDP


hiedp;
TIME DATE
10:08:11 09NOV17
LIM EVENTS OVERWRITTEN OLDEST EVENT NEWEST EVENT LAST HIREI
EVENTS
001 18 0 19:19:42 27SEP17 07:40:34 09NOV17 21:13:36 26SEP17
002 78 0 21:15:25 26SEP17 13:01:32 07NOV17 21:13:36 26SEP17
003 5 0 10:48:27 05OCT17 10:54:04 08NOV17 21:13:37 26SEP17
004 100 1 05:56:37 27SEP17 11:05:52 08NOV17 21:13:37 26SEP17
005 9 0 14:52:39 02OCT17 15:12:50 23OCT17 21:13:36 26SEP17
006 59 0 14:58:46 27SEP17 09:57:55 09NOV17 21:13:36 26SEP17
007 4 0 12:54:56 29SEP17 11:38:37 08NOV17 21:13:37 26SEP17
008 47 0 10:27:14 27SEP17 09:55:15 09NOV17 21:13:36 26SEP17
009 1 0 15:12:50 23OCT17 15:12:50 23OCT17 21:13:37 26SEP17
010 4 0 08:33:13 27SEP17 13:02:58 09OCT17 21:13:37 26SEP17

END
<Himdp:lim=1;

DIAGNOSTICS FROM OPERATING SYSTEM
[pre]TIME DATE
10:08:30 09NOV17
DIAGNOSTICS FROM LIM 001, LAST HIREI: 21:13:36 26SEP17

TIME DATE ERROR CODE
07:40:34 09NOV17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 0200439C
ENTER
SWSW A-LEVEL SIGNAL RELPAT (H'0047)
FROM CMP (H'2D2) EXE A IN LIM 001
TO SCP (H'32F) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 5
WITH 0 1 2 3 4 5 6 7 8 9
000 00 08 BB 07 FF


TIME DATE ERROR CODE
15:37:36 08NOV17 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 0200A17E
BRANCHVALUE = 00000006
ENTER
SWSW A-LEVEL SIGNAL CONNECT (H'001E)
FROM RELP (H'1E8) EXE A IN LIM 001
TO LSP (H'054) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 18
WITH 0 1 2 3 4 5 6 7 8 9
000 01 73 01 E8 00 73 CE 03 01 6D
010 22 01 03 2F 00 16 55 00

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 47 82

TIME DATE ERROR CODE
22:35:20 03NOV17 H'14
JUMP TO ILLEGALSTATE
LOGICAL PROGRAM ERROR ADDRESS = 020022D4
ENTER
SWSW A-LEVEL SIGNAL KEYLOADRES (H'0047)
FROM IPLP (H'1B1) EXE A IN LIM 001
TO IPLD (H'1B2) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 4
WITH 0 1 2 3 4 5 6 7 8 9
000 00 01 00 00
STACK ADDRESS = 02001FAE
SIGNAL SEND ADDRESS = 0202985E

USER STACK DUMP
0 1 2 3 4 5 6 7 8 9 A B C D E F
02 00 09 A8 02 00 03 9E

TIME DATE ERROR CODE
08:37:30 01NOV17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02001666
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3BD) EXE A IN LIM 001
TO SLP60 (H'37B) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 77 5C
STACK ADDRESS = 00000000
SIGNAL SEND ADDRESS = 0200E0C8


TIME DATE ERROR CODE
14:49:16 31OCT17 H'13
FAULTY POINTER
LOGICAL PROGRAM ERROR ADDRESS = 02001434
ENTER
SWSW A-LEVEL SIGNAL ANSWER (H'00C0)
FROM TLP60 (H'3BD) EXE A IN LIM 001
TO CMP (H'2D2) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 7
WITH 0 1 2 3 4 5 6 7 8 9
000 FF F8 00 9A 03 BD 01


TIME DATE ERROR CODE
14:47:24 29OCT17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02001666
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3BD) EXE A IN LIM 001
TO SLP60 (H'37B) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 8F 80
STACK ADDRESS = 00000000
SIGNAL SEND ADDRESS = 0200E0C8


TIME DATE ERROR CODE
10:42:29 17OCT17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02001666
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3BD) EXE A IN LIM 001
TO SLP60 (H'37B) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 AB 94


TIME DATE ERROR CODE
09:58:03 17OCT17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02001666
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3BD) EXE A IN LIM 001
TO SLP60 (H'37B) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 0C 62


TIME DATE ERROR CODE
20:12:30 08OCT17 H'13
FAULTY POINTER
LOGICAL PROGRAM ERROR ADDRESS = 02001434
ENTER
SWSW A-LEVEL SIGNAL ANSWER (H'00C0)
FROM TLP60 (H'3BD) EXE A IN LIM 001
TO CMP (H'2D2) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 7
WITH 0 1 2 3 4 5 6 7 8 9
000 FF F9 00 9F 03 BD 01
STACK ADDRESS = 02008F34
SIGNAL SEND ADDRESS = 02021260


TIME DATE ERROR CODE
16:48:06 07OCT17 H'44
COMMUNICATION STATUS ERROR AT BUFFER TRANSFER
SEND ERRORS, DUPLEX MODE = 000
RECEIVE ERRORS, DUPLEX MODE = 001
SEND ERRORS, SIMPLEX MODE = 000
EXE A IN LIM 001

TIME DATE ERROR CODE
13:18:24 05OCT17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02004B16
ENTER
SWSW A-LEVEL SIGNAL USRREL (H'00FF)
FROM IMP (H'2FA) EXE A IN LIM 001
TO RELP (H'1E8) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 5
WITH 0 1 2 3 4 5 6 7 8 9
000 01 CC B3 00 00
STACK ADDRESS = 0200378A
SIGNAL SEND ADDRESS = 02006BFE


TIME DATE ERROR CODE
13:18:24 05OCT17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02004704
ENTER
SWSW A-LEVEL SIGNAL USRPRO (H'00EF)
FROM IMP (H'2FA) EXE A IN LIM 001
TO RELP (H'1E8) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 22
WITH 0 1 2 3 4 5 6 7 8 9
000 01 CC B3 01 AB 3D 02 FA 01 05
010 0A 01 00 FF FF FF 00 00 00 00
020 00 FF


TIME DATE ERROR CODE
13:18:24 05OCT17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02003756
ENTER
SWSW A-LEVEL SIGNAL USRINF (H'0049)
FROM IMP (H'2FA) EXE A IN LIM 001
TO RELP (H'1E8) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 87
WITH 0 1 2 3 4 5 6 7 8 9
000 01 CC B3 00 FF 00 0F 02 00 03
010 FF 00 B2 10 03 BD 01 FF 01 09
020 40 01 10 20 F6 00 0D 09 01 07
030 92 38 11 F4 FF FF FF FF 01 09
040 40 01 10 20 F6 00 0D 09 01 07
050 92 38 11 F4 FF FF FF 00 FF FF
060 FF FF FF FF FF FF FF FF 00 00
070 00 FF FF FF FF FF FF FF FF FF
080 FF 00 00 00 00 00 00


TIME DATE ERROR CODE
13:18:24 05OCT17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02003756
ENTER
SWSW A-LEVEL SIGNAL USRINF (H'0049)
FROM IMP (H'2FA) EXE A IN LIM 001
TO RELP (H'1E8) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 87
WITH 0 1 2 3 4 5 6 7 8 9
000 01 CC B3 00 02 01 0B 06 FF 0F
010 FF 00 CD 60 01 E3 04 01 00 00
020 FF FF FF FF FF 00 05 59 26 F3
030 FF FF FF FF FF FF FF 01 00 00
040 FF FF FF FF FF 01 00 FF FF FF
050 FF FF FF FF FF FF FF 00 FF FF
060 FF FF FF FF FF FF FF FF 00 00
070 05 59 26 F3 FF FF FF FF FF FF
080 FF 00 00 00 00 00 00


TIME DATE ERROR CODE
08:03:02 04OCT17 H'44
COMMUNICATION STATUS ERROR AT BUFFER TRANSFER
SEND ERRORS, DUPLEX MODE = 000
RECEIVE ERRORS, DUPLEX MODE = 001
SEND ERRORS, SIMPLEX MODE = 000
EXE A IN LIM 001

TIME DATE ERROR CODE
10:58:04 30SEP17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02001666
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3BD) EXE A IN LIM 001
TO SLP60 (H'37B) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 F0 F6


TIME DATE ERROR CODE
15:00:16 28SEP17 H'60
ADDRESS CONTROL FAILURE
LOGICAL PROGRAM ERROR ADDRESS = 02001666
ENTER
SWSW A-LEVEL SIGNAL BPAANSACK (H'0094)
FROM TLP60 (H'3BD) EXE A IN LIM 001
TO SLP60 (H'37B) EXE A IN LIM 001
NUMBER OF DATA BYTES IN SIGNAL = 2
WITH 0 1 2 3 4 5 6 7 8 9
000 DB B5
STACK ADDRESS = 00000000
SIGNAL SEND ADDRESS = 0200E0C8


TIME DATE ERROR CODE
19:19:42 27SEP17 H'34
RECEIVING LIM ADDRESS NOT AVAILABLE
LOGICAL PROGRAM ERROR ADDRESS = 0200F7C6
ENTER
SWSW B-LEVEL SIGNAL PERSB (H'0019)
FROM EXS (H'003) EXE A IN LIM 001
TO GSP (H'043) EXE A IN LIM 001
NO DATA IN SIGNAL

SEND
SWSW B-LEVEL SIGNAL *************** (H'0062)
FROM GSP (H'043) EXE A IN LIM 001
TO ****** (H'FFF) EXE A IN LIM 255
NUMBER OF DATA BYTES IN SIGNAL = 10
WITH 0 1 2 3 4 5 6 7 8 9
000 00 FF 00 01 00 43 04 01 00 43


END[/pre]
<

Cheers

//Mikael H




 
Hi Norbert (snor),

Thanks for input

No I have nothing conflicting with the daily storing to disc of TM data as of my knowledge, automatic dump runs at 22:00 changed that from 23:00 to be sure. I usually copy TM files to external storage and delete the files on disc every other month or when we get an alarm that disc is almost full and we get that alarm when the space on disc is approximately 3500.

With cleaning and doing changes to active measurement I first ran TRDIP and discovered some not active measurements and some measurement running from 00:00 to 24:00 so I deleted them to see if that could be the problem but same problem persisted.

Se my answer to Satellite1900 as well.

Cheers

//Mikael H
 
Hi,
Another question, please print:
FIFTI:SUBFS=SYSSUBFS11;
FIFTI:SUBFS=SYSSUBFS21;






\Satellite1900
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top