Problem with CS - call servers, both CS are in main status!?
Problem with CS - call servers, both CS are in main status!?
Hello, could someone help me?
Last edited by acamup on 23 Sep 2024 08:33, edited 2 times in total.
Problem with CS - call servers, both CS are in main status!?
I have an AL OXE IP MG R.11.0.1 with a duplicated CS configuration in two different subnets and in different locations, a few days ago I noticed that CS, xa and xb are not visible and both north are in "main" status. I restarted xb but it always goes back to "main" status. The phone app works normally. I checked the network parameters on both processors and they are all set correctly. How to bring the system to a normal state, so that xa server is in "main" and xb is in "stand-by" status?
- frank
- Alcatel Unleashed Certified Guru

- Posts: 3386
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
Re: Problem with CS - call servers, both CS are in main status!?
Both can only be in a main status if they can't see each other anymore.
That s a network issue on your end. As soon as they see each other, one will reboot to go back in standby mode.
That s a network issue on your end. As soon as they see each other, one will reboot to go back in standby mode.
Code Free Or Die
Re: Problem with CS - call servers, both CS are in main status!?
Thank you Mr. Frank,
first I checked the network itself, when I telnet on xb (which should be stand-by) the processor can ping xa (Main) and vice versa with xa I can ping Xb. With the command netadmin -m sa the network parameters were checked and all are OK. Everything seems fine, but the processors are still not visible.
first I checked the network itself, when I telnet on xb (which should be stand-by) the processor can ping xa (Main) and vice versa with xa I can ping Xb. With the command netadmin -m sa the network parameters were checked and all are OK. Everything seems fine, but the processors are still not visible.
- frank
- Alcatel Unleashed Certified Guru

- Posts: 3386
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
Re: Problem with CS - call servers, both CS are in main status!?
do you have a license installed?
is auto start on?
are the phone applications up and running?
What does the command 'twin' shows?
is auto start on?
are the phone applications up and running?
What does the command 'twin' shows?
Code Free Or Die
Re: Problem with CS - call servers, both CS are in main status!?
Yes, Dear Mr. Frank, I have a license, the system has been in operation since 2010, autostart is turned on, the phone application is up and running on both processors.
Welcome to xa011001
Alcatel-Lucent OmniPCX Enterprise
login: mtcl
Password:
Last login: Mon Sep 23 12:02:29 from 172.22.26.9
Alcatel-Lucent OmniPCX Enterprise
standard installation last performed: 20-Sep-2018 16:46:02
# The role of the CPU is MAIN
Application software identity
R11.0.1-k1.520-47-a-yu-c80s1
Business identification: R11.0.1
Release:
DELIVERY k1.520
Patch identification: 47
Dynamic patch identification: a
Country: yu
Cpu: c80s1
ACD VERSION
release : 8
bug_fixing : 1
protocol_id : 90
version_dy_hr_stat : 11
--------------------------------------------------------------------------------------------------------------------
(1101)xa011001> role -b
MAIN stand-by CPU state : NOT READY
--------------------------------------------------------------------------------------------------------------------
(1101)xa011001> twin
Thu Sep 26 13:25:33 CEST 2024
Usage : twin [Redundancy Cpu Enable (y/n)]
Role and CPU positions:
Role of the CPU : MAIN
CPU position : 06
CPU address : 172.22.26.2
Twin CPU position : UNKNOWN
Twin CPU address : UNKNOWN
Redundancy State:
Duplicated configuration : YES
Wished sig. transfer mode : C1 signalling channel
Transmission CPU-CPU : KO
Telephony redundancy : KO
monitel redundancy : KO
memloader redundancy : KO
All applications redundancy : KO
--------------------------------------------------------------------------------------------------------------------------
DLL version = 0121 DLL version = 0121
File version = 4 File version = 4
OXE version = 0110 OXE version = 0110
Soft Key = ef182f3c368a45b56c58 Soft Key = ef182f3c368a45b56c58
Cpu Id 0 = FF00BE80 Cpu Id 0 = FF00BE80
Cpu Id 1 = FF00BEB4 Cpu Id 1 = FF00BEB4
Your System CPU-Id:FF00BE80 Your System CPU-Id:FF00BE80
System CPU-Id found System CPU-Id found
Handle 4760 = FF00BE80 Handle 4760 = FF00BE80
Timestamp : Timestamp :
Fri Jul 12 12:27:30 2019 Fri Jul 12 12:27:30 2019
186 E-CS redundancy = 1 -> 1
-----------------------------------------------------------------------------------------------------------------------
(1101)xa011001>ls
menu mtcl.cron
----------------------------------------------------------------------------------------------------------------------
ALCATEL-LUCENT
Autostart menu Installation FACILITIES 2.78.0
Autostart is set
1 Set autostart
2 Unset autostart
Q Go back to previous menu
Your choice [1..2, Q] ? 1
Autostart is set
Autostart is set on twin CPU
Autostart has been set on both CPUs
------------------------------------------------------------------------------------------------------------------------------
The following error is printed on the hyper terminal xa (main) of the processor:
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
hda: status timeout: status=0xd0 { Busy }
ide0: unexpected interrupt, status=0x80, count=287
hda: no DRQ after issuing WRITE
ide0: reset: success
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
hda: status timeout: status=0xd0 { Busy }
ide0: unexpected interrupt, status=0x80, count=288
hda: no DRQ after issuing WRITE
ide0: reset: success
floppy0: no floppy controllers found
floppy0: no floppy controllers found
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
On the xb (stand-by) processor, the state is as follows:
Welcome to xb011001
Alcatel-Lucent OmniPCX Enterprise
login: mtcl
Password:
Last login: Thu Sep 26 08:20:30 from 172.22.26.9
Alcatel-Lucent OmniPCX Enterprise
standard installation last performed: 20-Sep-2018 07:35:53
There is a disk dump on /dev/crashdump, date: 2024/09/16 11:34:50
# The role of the CPU is MAIN
Application software identity
R11.0.1-k1.520-47-a-yu-c80s1
Business identification: R11.0.1
Release:
DELIVERY k1.520
Patch identification: 47
Dynamic patch identification: a
Country: yu
Cpu: c80s1
ACD VERSION
release : 8
bug_fixing : 1
protocol_id : 90
version_dy_hr_stat : 11
-------------------------------------------------------------------------------------------------------------------
(1101)xb011001> role -b
MAIN stand-by CPU state : NOT READY
(1101)xb011001> twin
Thu Sep 26 13:36:29 CEST 2024
Usage : twin [Redundancy Cpu Enable (y/n)]
Role and CPU positions:
Role of the CPU : MAIN
CPU position : 06
CPU address : Not Declared
Twin CPU position : UNKNOWN
Twin CPU address : UNKNOWN
Redundancy State:
Duplicated configuration : YES
Wished sig. transfer mode : C1 signalling channel
Transmission CPU-CPU : KO
Telephony redundancy : KO
monitel redundancy : KO
memloader redundancy : KO
All applications redundancy : KO
---------------------------------------------------------------------------------------------------------------------------
DLL version = 0121 DLL version = 0121
File version = 4 File version = 4
OXE version = 0110 OXE version = 0110
Soft Key = ef182f3c368a45b56c58 Soft Key = ef182f3c368a45b56c58
Cpu Id 0 = FF00BE80 Cpu Id 0 = FF00BE80
Cpu Id 1 = FF00BEB4 Cpu Id 1 = FF00BEB4
Your System CPU-Id:FF00BEB4 Your System CPU-Id:FF00BEB4
System CPU-Id found System CPU-Id found
Handle 4760 = FF00BE80 Handle 4760 = FF00BE80
Timestamp : Timestamp :
Fri Jul 12 12:27:30 2019 Fri Jul 12 12:27:30 2019
186 E-CS redundancy = 1 -> 1
-------------------------------------------------------------------------------------------------------------------
ALCATEL-LUCENT
Autostart menu Installation FACILITIES 2.78.0
Autostart is set
1 Set autostart
2 Unset autostart
Q Go back to previous menu
Your choice [1..2, Q] ? 1
Autostart is set
Press return
(1101)xb011001> ls
menu mtcl.cron
Welcome to xa011001
Alcatel-Lucent OmniPCX Enterprise
login: mtcl
Password:
Last login: Mon Sep 23 12:02:29 from 172.22.26.9
Alcatel-Lucent OmniPCX Enterprise
standard installation last performed: 20-Sep-2018 16:46:02
# The role of the CPU is MAIN
Application software identity
R11.0.1-k1.520-47-a-yu-c80s1
Business identification: R11.0.1
Release:
DELIVERY k1.520
Patch identification: 47
Dynamic patch identification: a
Country: yu
Cpu: c80s1
ACD VERSION
release : 8
bug_fixing : 1
protocol_id : 90
version_dy_hr_stat : 11
--------------------------------------------------------------------------------------------------------------------
(1101)xa011001> role -b
MAIN stand-by CPU state : NOT READY
--------------------------------------------------------------------------------------------------------------------
(1101)xa011001> twin
Thu Sep 26 13:25:33 CEST 2024
Usage : twin [Redundancy Cpu Enable (y/n)]
Role and CPU positions:
Role of the CPU : MAIN
CPU position : 06
CPU address : 172.22.26.2
Twin CPU position : UNKNOWN
Twin CPU address : UNKNOWN
Redundancy State:
Duplicated configuration : YES
Wished sig. transfer mode : C1 signalling channel
Transmission CPU-CPU : KO
Telephony redundancy : KO
monitel redundancy : KO
memloader redundancy : KO
All applications redundancy : KO
--------------------------------------------------------------------------------------------------------------------------
DLL version = 0121 DLL version = 0121
File version = 4 File version = 4
OXE version = 0110 OXE version = 0110
Soft Key = ef182f3c368a45b56c58 Soft Key = ef182f3c368a45b56c58
Cpu Id 0 = FF00BE80 Cpu Id 0 = FF00BE80
Cpu Id 1 = FF00BEB4 Cpu Id 1 = FF00BEB4
Your System CPU-Id:FF00BE80 Your System CPU-Id:FF00BE80
System CPU-Id found System CPU-Id found
Handle 4760 = FF00BE80 Handle 4760 = FF00BE80
Timestamp : Timestamp :
Fri Jul 12 12:27:30 2019 Fri Jul 12 12:27:30 2019
186 E-CS redundancy = 1 -> 1
-----------------------------------------------------------------------------------------------------------------------
(1101)xa011001>ls
menu mtcl.cron
----------------------------------------------------------------------------------------------------------------------
ALCATEL-LUCENT
Autostart menu Installation FACILITIES 2.78.0
Autostart is set
1 Set autostart
2 Unset autostart
Q Go back to previous menu
Your choice [1..2, Q] ? 1
Autostart is set
Autostart is set on twin CPU
Autostart has been set on both CPUs
------------------------------------------------------------------------------------------------------------------------------
The following error is printed on the hyper terminal xa (main) of the processor:
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
hda: status timeout: status=0xd0 { Busy }
ide0: unexpected interrupt, status=0x80, count=287
hda: no DRQ after issuing WRITE
ide0: reset: success
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
floppy0: no floppy controllers found
hda: status timeout: status=0xd0 { Busy }
ide0: unexpected interrupt, status=0x80, count=288
hda: no DRQ after issuing WRITE
ide0: reset: success
floppy0: no floppy controllers found
floppy0: no floppy controllers found
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
On the xb (stand-by) processor, the state is as follows:
Welcome to xb011001
Alcatel-Lucent OmniPCX Enterprise
login: mtcl
Password:
Last login: Thu Sep 26 08:20:30 from 172.22.26.9
Alcatel-Lucent OmniPCX Enterprise
standard installation last performed: 20-Sep-2018 07:35:53
There is a disk dump on /dev/crashdump, date: 2024/09/16 11:34:50
# The role of the CPU is MAIN
Application software identity
R11.0.1-k1.520-47-a-yu-c80s1
Business identification: R11.0.1
Release:
DELIVERY k1.520
Patch identification: 47
Dynamic patch identification: a
Country: yu
Cpu: c80s1
ACD VERSION
release : 8
bug_fixing : 1
protocol_id : 90
version_dy_hr_stat : 11
-------------------------------------------------------------------------------------------------------------------
(1101)xb011001> role -b
MAIN stand-by CPU state : NOT READY
(1101)xb011001> twin
Thu Sep 26 13:36:29 CEST 2024
Usage : twin [Redundancy Cpu Enable (y/n)]
Role and CPU positions:
Role of the CPU : MAIN
CPU position : 06
CPU address : Not Declared
Twin CPU position : UNKNOWN
Twin CPU address : UNKNOWN
Redundancy State:
Duplicated configuration : YES
Wished sig. transfer mode : C1 signalling channel
Transmission CPU-CPU : KO
Telephony redundancy : KO
monitel redundancy : KO
memloader redundancy : KO
All applications redundancy : KO
---------------------------------------------------------------------------------------------------------------------------
DLL version = 0121 DLL version = 0121
File version = 4 File version = 4
OXE version = 0110 OXE version = 0110
Soft Key = ef182f3c368a45b56c58 Soft Key = ef182f3c368a45b56c58
Cpu Id 0 = FF00BE80 Cpu Id 0 = FF00BE80
Cpu Id 1 = FF00BEB4 Cpu Id 1 = FF00BEB4
Your System CPU-Id:FF00BEB4 Your System CPU-Id:FF00BEB4
System CPU-Id found System CPU-Id found
Handle 4760 = FF00BE80 Handle 4760 = FF00BE80
Timestamp : Timestamp :
Fri Jul 12 12:27:30 2019 Fri Jul 12 12:27:30 2019
186 E-CS redundancy = 1 -> 1
-------------------------------------------------------------------------------------------------------------------
ALCATEL-LUCENT
Autostart menu Installation FACILITIES 2.78.0
Autostart is set
1 Set autostart
2 Unset autostart
Q Go back to previous menu
Your choice [1..2, Q] ? 1
Autostart is set
Press return
(1101)xb011001> ls
menu mtcl.cron
Re: Problem with CS - call servers, both CS are in main status!?
For xb011001 (twin command) - CPU address : Not Declared?
Re: Problem with CS - call servers, both CS are in main status!?
(1101)xb011001> netadmin -m
Ethernet interface setup
========================
Netmask : 255.255.255.192
==============================================================================
| Machine type | Local interface | Name | Address |
==============================================================================
| local | Ethernet | xb011001 | 172.22.28.2 |
| local main | Ethernet | xmb011001 | 172.22.28.3 |
| router | Ethernet | router | 172.22.28.1 |
| local | IP/X25 tunnel | x011001_tun | 172.30.11.1 |
==============================================================================
<return> to continue.
CPU redundancy setup
====================
Netmask : 255.255.255.0
==============================================================================
| Machine type | Local interface | Name | Address |
==============================================================================
| local | Ethernet | xa011001 | 172.22.26.2 |
| local main | Ethernet | xma011001 | 172.22.26.3 |
| router | Ethernet | routerxa | 172.22.26.1 |
(1101)xa011001> netadmin –m
Ethernet interface setup
========================
Netmask : 255.255.255.0
==============================================================================
| Machine type | Local interface | Name | Address |
==============================================================================
| local | Ethernet | xa011001 | 172.22.26.2 |
| local main | Ethernet | xma011001 | 172.22.26.3 |
| router | Ethernet | rooutera | 172.22.26.1 |
| local | IP/X25 tunnel | x011001_tun | 172.30.11.1 |
==============================================================================
<return> to continue.
CPU redundancy setup
====================
Netmask : 255.255.255.192
==============================================================================
| Machine type | Local interface | Name | Address |
==============================================================================
| local | Ethernet | xb011001 | 172.22.28.2 |
| local main | Ethernet | xmb011001 | 172.22.28.3 |
| router | Ethernet | routerb | 172.22.28.1 |
==============================================================================
Ethernet interface setup
========================
Netmask : 255.255.255.192
==============================================================================
| Machine type | Local interface | Name | Address |
==============================================================================
| local | Ethernet | xb011001 | 172.22.28.2 |
| local main | Ethernet | xmb011001 | 172.22.28.3 |
| router | Ethernet | router | 172.22.28.1 |
| local | IP/X25 tunnel | x011001_tun | 172.30.11.1 |
==============================================================================
<return> to continue.
CPU redundancy setup
====================
Netmask : 255.255.255.0
==============================================================================
| Machine type | Local interface | Name | Address |
==============================================================================
| local | Ethernet | xa011001 | 172.22.26.2 |
| local main | Ethernet | xma011001 | 172.22.26.3 |
| router | Ethernet | routerxa | 172.22.26.1 |
(1101)xa011001> netadmin –m
Ethernet interface setup
========================
Netmask : 255.255.255.0
==============================================================================
| Machine type | Local interface | Name | Address |
==============================================================================
| local | Ethernet | xa011001 | 172.22.26.2 |
| local main | Ethernet | xma011001 | 172.22.26.3 |
| router | Ethernet | rooutera | 172.22.26.1 |
| local | IP/X25 tunnel | x011001_tun | 172.30.11.1 |
==============================================================================
<return> to continue.
CPU redundancy setup
====================
Netmask : 255.255.255.192
==============================================================================
| Machine type | Local interface | Name | Address |
==============================================================================
| local | Ethernet | xb011001 | 172.22.28.2 |
| local main | Ethernet | xmb011001 | 172.22.28.3 |
| router | Ethernet | routerb | 172.22.28.1 |
==============================================================================
Re: Problem with CS - call servers, both CS are in main status!?
So your CPUs in different LANs.
Looks like UDP blocked between your CPUs.
Looks like UDP blocked between your CPUs.
If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.
Re: Problem with CS - call servers, both CS are in main status!?
Yes, dear Mr. Alex, the Dual Processors (CS) of my PBX are located in two different networks and have been for several years. They stopped seeing each other a few days ago.
I checked with iperf applications running on computers in the same networks and UDP is not blocked.
Thank you for your suggestion.
I checked with iperf applications running on computers in the same networks and UDP is not blocked.
Thank you for your suggestion.
