Alarm 2725 ADJACENT CELL IDENTIFIER CONFIGURATION ERROR is raised

Symptoms
The alarm is raised when there are problems with adjacent cell identifications. An
external handover attempt is interrupted, and the call continues in the source cell.
Handovers between the cells do not work until the problem is corrected.
Either the BSC or MSC can detect the problem.

When the BSC detects the problem, counters 004100 MSC O ADJ CELL ID ERR
and 500513 ADJ CELL ID ERR are updated.
When the MSC detects the problem, counters 004100 MSC O ADJ CELL ID
ERR and 500926 M INVALID CELL are updated.

Possible causes
The source cell's adjacent cell information in the BSS Radio Network Configuration
Database (BSDATA) is incorrect. The source BSC notices this from the HANDOVER
COMMAND message received from the MSC. Layer 3 information in the message
contains the broadcast control channel (BCCH) frequency and the base station identity
code (BSIC) of the target cell. The source BSC compares the BCCH frequency and the
BSIC with the original information it has on the handover candidates. If these do not
match, the handover attempt is interrupted.
There are also other possible causes. The source cell's adjacent cell information in the
RCSPRB data area may be incorrect, or the HANDOVER COMMAND message may
have been generated incorrectly in the target BSC.
The source BSC or MSC can detect the error also if the routing information has been
defined incorrectly in the MSC. The MSC can detect the error also if the error is in the
target BSC, for example, if the target cell is locked.
Instructions
In the EVENT field of the alarm, check if the fault was detected by the MSC or BSC.
If the fault was detected by the MSC, implement the following steps:
1. Ensure that the routing information is defined correctly in the MSC.
Ensure that the target cell in the target BSC is not locked.
2.
ZEEI;
If the fault was detected by the BSC, implement the following steps:
1. Check the source cell's adjacent cell information in the BSDATA.
ZEAO;

If the BCCH and BSIC information in the alarm match with the adjacent cell,
the cause of the alarm may be that the source cell's adjacent cell information
in the RCSPRB data area is incorrect, or the data area is corrupted.
Example:
BSCSG9902
BCSU-2
SWITCH
2004-03-24
09:45:36.96
** ALARM BCSU-2
1A002-27
HAS_BX
(0004) 2725 ADJACENT CELL IDENTIFIER CONFIGURATION
ERROR

111d 01 02 02 623d
LOCATION AREA CODE......................(LAC)... 1000
CELL IDENTIFICATION.....................(CI)....27926
NETWORK COLOUR CODE.....................(NCC)...
BACKGROUND NETWORK COLOUR CODE..........(BNCC)..
BTS COLOUR CODE.........................(BCC)...
BACKGROUND BTS COLOUR CODE..............(BBCC)..
FREQUENCY NUMBER OF BCCH................(FREQ)..

2
2
623

If the BCCH and BSIC information in the alarm do not match with the
adjacent cell, the HANDOVER COMMAND has probably been generated
incorrectly.
Example:
BSCSG9902
BCSU-2
SWITCH
2004-03-24 09:45:36.96
** ALARM BCSU-2
1A002-27
HAS_BX
(0004) 2725 ADJACENT CELL IDENTIFIER CONFIGURATION
ERROR
111d 01 06 02 623d
LOCATION AREA CODE......................(LAC)... 1000
CELL IDENTIFICATION.....................(CI)....27926
NETWORK COLOUR CODE.....................(NCC)...
BACKGROUND NETWORK COLOUR CODE..........(BNCC)..
BTS COLOUR CODE.........................(BCC)...
BACKGROUND BTS COLOUR CODE..............(BBCC)..
FREQUENCY NUMBER OF BCCH................(FREQ)..

2
2
623

In both cases, a Base Station Controller Signalling Unit (BCSU) switchover solves
the problem.
Perform a BCSU switchover.
2.
ZUSC:BCSU,<WO_index>:SP,;
If the problem persists, collect all the information needed for a Problem Report and
3. contact Nokia Siemens Networks for further investigations. For instructions,
seeCollecting alarm 2725 logs in BSC Problem Reporting.