Incident 1612 & 1613 (NOE protocol error)

[mgoegel]

Hi folks,

i've an customer with (now) OXE f4.401.24b.
They had problems 4029/4039 sets and broken calls.
Incidents as above - the version was f4.401.20. I've seen some corrections in patch 21,
so yesterday we upgraded the PBX to 24b.
This morning, after all sets were flashed, i have the same incidents on a few sets again. I have currently no informations about broken calls.

Any hints, may i made somewhere an wrong configuration?

Mario

[knightr1der]

what does 'downstat t' show you? does it show that there are still sets waiting to be downloaded?

Also, I had a similar problem. It turned out to be the customer plugged wrong phone type in f.e. user programmed for 4029, but 4039 plugged in. This generates the same error.

[mgoegel]

downstat t says, that no phone needs to be downloaded.

I know those messages, if a set type is wrong, but my colleague checked yesterday the set types.
This was the 1st thing in my mind. They have only a few (3) 4039, rest of them (97) are 4029.

The message appeared this morning on 4 sets.

Mario

[alex]

I just ignoring these messages (with incident filter) as long as customer do not complain. Also installed some latest patches hoping that these incidents disappear. Hoped in vain. Looks like it is a problem of a user pressing wrong button of something like this. Because when there is low trffic on a system there is no such error/ When traffic is high I have bunch of these errors appearing randomly.

[Eliott_DUP]

Is an AOM connected?
Is a default homepage set correctly?

You can see this by using the getnoeversion command.
This will create an Excel readable CSV file.

[mgoegel]

I don't think, they have AOMs.

What exactly do you mean with "default homepage set correctly".
Is there any difference, between the pages, the sets are showing?

I'll try the command looks interesting. Maybe I#ll see something there

[Eliott_DUP]

What exactly do you mean with "default homepage set correctly".

I don't know. Yes, it's configurable.
I can remember that there was a problem with the default homepage a long time ago but it should be fixed in your version so just forget it.

[luckyme2]

The same incidents happen here.
This customers has blade server for CS so all hardware is on IP.
In this case the error only occur on common hardware (MG).
Sets behind crystal hardware don't have the problem.

29/06/07 11:31:39 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 4531)
29/06/07 11:31:39 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.95.15.00.ff.00.00.00.00.00
29/06/07 11:32:03 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 3977)
29/06/07 11:32:03 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.95.15.00.ff.00.00.00.00.00
29/06/07 11:32:16 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 3977)
29/06/07 11:32:16 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.95.15.00.ff.00.00.00.00.00
29/06/07 11:32:22 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 3977)
29/06/07 11:32:22 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.95.15.00.ff.00.00.00.00.00
29/06/07 11:32:25 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 3977)
29/06/07 11:32:25 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.95.15.00.ff.00.00.00.00.00
29/06/07 11:33:10 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 4533)
29/06/07 11:33:10 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.94.15.00.ff.00.00.00.00.00
29/06/07 11:33:19 000001M|--/--/-/---|=0:1612=Protocol error on Alcatel 8&9 series, type 13 (neqt 4533)
29/06/07 11:33:19 000001M|--/--/-/---|=3:1613=15.04.0d.00.02.02.94.15.00.ff.00.00.00.00.00

No one else have any idea ?
I think I will have to go for an SR.

I forgot : It's an OXE release f5401.17c

[mgoegel]

In patch environments i install the sets with plug'n'play (set in/out of service function).
Yesterday i saw this incident, when a set was going out of service and back in service, in a new installed system (set flashing was already done).
This was release f5.401.17d - but no incidents other as on this event.

Maybe the customer was moving some sets when i wrote the first post.

Mario

[OXE_4400]

I saw something similar when not correct set type was pluggedin.