Fiji error

[lapakhora]

Hit it sis 81c release 4.5.

System is giving Fiji0006 error, how can i remove this error.

 

[Firebird Scrambler]

I'm not sure, but the error message is

Recovery on both rings failed.
Perform actions for FIJI0005 for both rings.
Severity: Critical

also refer to FIJI0005 which is..

Recover failed on Ring 0/1.
Parameter 1 = Ring Number.
Check for failure reason:

1. STAT RING S
Make sure all FIJIs are up.
2. STAT ALRM S
Make sure no LOP, LOS, LOF, BER, or TXIP alarms are on and that the
NEWK and NEWZ values are correct.
(See FIJI0010-0016 messages)
3. After all alarms are cleared:
a) RSET - Wait for ring audit to bring the rings to the proper state,
or
b) RSTR
Severity: Critical




Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website =

http://somertel.com

linkedin

 

[lapakhora]

Thanks for the response. in 81c four Fiji cards are installed, can you help what is the exact location of each CPU?? i mean 0 1 or 1 0.

 

[lapakhora]

any help

 

[bhassell2000]

in LD 39 can you do commands
Stat ring 0
stat ring 1

and post the results?

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[lapakhora]

Status of below command is ok but it also shows
2 0 = not responding

 

[KCFLHRC]

Not sure what you are showing here with the 2 0 not responding, there are only 2 rings. The 2 may be the group # which may not be equipped. How many Network Groups do you have? And did you stat the rings n ld 39? they should show half and half in a normal state. If you have 4 FIJI cards then you should have only 2 network groups and 2 0 is configured but no hardware to support it.

 

[KCFLHRC]

A quick search on the solutions site turned up the below solution. It would appear you have the same issue. CNI's configured for a network group that doesn't exist.

CS1000: Many FIJI006 error
Rate Content Rate this Page

Doc ID: SOLN231234
Version: 2.0
Status: Published
Published date: 19 Jun 2013
Updated: 02 Dec 2014
Author:
Flavio Pagani

Details

CS1000M MG Release 6.00R
Problem Clarification

The system printout a lot of FIJI006. Problem started after the software was reinstalled from the scrach and no a backup available, the default DB was used.

%
% FIJI006
%
% FIJI006
%
% FIJI006
%
% FIJI006
%
% FIJI006
%
% FIJI006
%

>ld 39
ISR000
.
FIJI006
stat ring 0
RING STATE: SURVIVAL STATE
RING AUTO RECOVERY IS ON
FIJI 0 0 ENBL
FIJI 1 0 ENBL
FIJI 2 0 UNEQ
FIJI 3 0 UNEQ
FIJI 4 0 SYS DSBL - NOT RESPONDING
FIJI 5 0 UNEQ
FIJI 6 0 UNEQ
FIJI 7 0 UNEQ

.stat ring 1
RING STATE: SURVIVAL STATE
RING AUTO RECOVERY IS ON
FIJI 0 1 ENBL
FIJI 1 1 ENBL
FIJI 2 1 UNEQ
FIJI 3 1 UNEQ
FIJI 4 1 SYS DSBL - NOT RESPONDING
FIJI 5 1 UNEQ
FIJI 6 1 UNEQ
FIJI 7 1 UNEQ

.
FIJI006



>ld 135
CCED000
.
FIJI006
stat cni
cni 0 9 0: remote = group 0 ENBL
cni 0 9 1: remote = group 1 ENBL
cni 0 10 0: remote = group 2 DSBL: 'NOT RESPONDING'
cni 0 10 1: remote = group 3 DSBL: 'NOT RESPONDING'
cni 0 11 0: remote = group 4 DSBL: 'NOT RESPONDING' 23
cni 0 11 1: remote = group 5 DSBL: 'NOT RESPONDING'
cni 0 12 0: remote = group 6 DSBL: 'NOT RESPONDING'
cni 0 12 1: remote = group 7 DSBL: 'NOT RESPONDING'

cni 1 9 0: remote = group 0 ENBL
cni 1 9 1: remote = group 1 ENBL
cni 1 10 0: remote = group 2 DSBL: 'NOT RESPONDING'
cni 1 10 1: remote = group 3 DSBL: 'NOT RESPONDING'
cni 1 11 0: remote = group 4 DSBL: 'NOT RESPONDING'
cni 1 11 1: remote = group 5 DSBL: 'NOT RESPONDING'
cni 1 12 0: remote = group 6 DSBL: 'NOT RESPONDING'
cni 1 12 1: remote = group 7 DSBL: 'NOT RESPONDING'
.
AUD000

REQ prt
TYPE cequ

CEQU
MPED 8D
TERM
TERD
TERQ 154
SUPL 004 016 020 032
040 048 056 N132
SUPC
SUPF
DDCS
DTCS
XCT 000 014 030 046
062
TDS * 000 * 014 * 030 * 046
* 062
CONF * 001 * 015 * 031 * 047
* 063
MFSD * 000 * 014 * 030 * 046
* 062
PRI2 002 003 008 009
012 013 024 025
036 037 052 053
APVL
DTI2
MISP
SYNM 0
EXT0 3PE
CNI 009 000 000
CNI 009 001 001
CNI 010 000 002
CNI 010 001 003
CNI 011 000 004
CNI 011 001 005
CNI 012 000 006
CNI 012 001 007
EXT1 3PE
CNI 009 000 000
CNI 009 001 001
CNI 010 000 002
CNI 010 001 003
CNI 011 000 004
CNI 011 001 005
CNI 012 000 006
CNI 012 001 007
MCFN 509 MB
Cause

Wrong configuration. Actually the system have installed only two network group instead the default DB have all the CNI configured.
Solution

Removed the CNI cards and TERQ loop 154 unequipped on the site

REQ prt
TYPE cequ

CEQU
MPED 8D
TERM
TERD
TERQ ---> removed loop154
SUPL 004 016 020 032
040 048 056 N132
SUPC
SUPF
DDCS
DTCS
XCT 000 014 030 046
062
TDS * 000 * 014 * 030 * 046
* 062
CONF * 001 * 015 * 031 * 047
* 063
MFSD * 000 * 014 * 030 * 046
* 062
PRI2 002 003 008 009
012 013 024 025
036 037 052 053
APVL
DTI2
MISP
SYNM 0
EXT0 3PE
CNI 009 000 000 ------------> Removed unused CNI
CNI 009 001 001
EXT1 3PE
CNI 009 000 000
CNI 009 001 001
MCFN 509 MB

 

[KCFLHRC]

My guess is something lead up to this issue, please explain

 

[bhassell2000]

Do you have a group 2 shelf 0? Is there an error on the front of that FIJI card?

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[kstaff22]

That does not look right, if I'm reading this correctly you removed the cni port for group 0 on ext 0----Go back in LD 17 CEQU and program back the cni 9 0 0 you removed from ext 0.
Go into ld 39 and do a stat ring 0 and a stat ring 1 and post here.

 

[KCFLHRC]

That text was copied and pasted from the Avaya Solutions site, it is an example, and yes I agree, incorrect. However, it would appear he has a network group configured that shouldn't be there.

 

[kstaff22]

sorry--------------I missed that.

if it's just fiji 4 on both rings then I think it's your config ---cequ----------------you must have cni 11 0 still configured.

 

[lapakhora]

There are only two network group shelf and total of four fiji card in the system. I get the Fiji0006 after every single minute. What you guys advise? should i verify the CEQU data?

 

[bhassell2000]

can you print your cequ and your stst ring info and post it here?

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[lapakhora]

ok. Two days are off here. I will post on monday