3.1
Maintenance
3.1.1
Generalities
The following conditions require maintenance to handle boards after these are accepted:
-
First appearance in the system:
•
System configuration aspect when a new board is detected
•
Initialization and start-up of the corresponding hardware
-
Dynamic appearance or disappearance due to physical causes:
•
Warm system reset
•
Board plugged/unplugged while the system is running
•
Problems detected requiring actions on the corresponding board
-
Dynamic appearance or disappearance due to logical causes (MMC commands)
The following rules apply:
-
Any detected board is considered by the maintenance as PRESENT.
-
A PRESENT board can be considered as ACCEPTED or REFUSED depending on the
system dimensioning or power budget criteria.
-
On cold reset, all the PRESENT boards are acknowledged (accepted or refused).
-
Hardware decrease aspects are only applied at cold reset. A board seen as PRESENT on
cold reset might not be detected on warm reset (board detection failure or board
unplugged). In such a situation, such a board is considered by maintenance as ABSENT
(the board configuration data is still available) after warm reset.
3.1.1.1
Single CPU replacement
When a CPU is faulty, a spare CPU with same traffic capacity has to be identified and the
faulty CPU isolated from the network (OmniSwitch configuration).
The DHCP configuration has to be updated to give the IP parameters of the faulty CPU to the
new CPU and the configuration save (done with the AST) restored to this new CPU. Once the
configuration is restored, the CPU will run and the telephony services will be available. The
license for the old CPU will only be operational for 30 days so a new license must be
requested for the new CPU ID.
3.1.1.2
Chassis replacement
If a failure on the master CPU or a hardware failure of the chassis leads to a dysfunction of all
the CPUs of the chassis , the CPU will be individually seen as faulty. In that case, the
procedure for single CPU replacement must be applied to all the faulty CPUs.
3.1.2
System with a Software Version older than R2.0
The system should always be powered down before plugging/unplugging a board.
3.1.2.1
Plugging a Board
! "#$ ! % $& !
13/62
Summary of Contents for OmniPCX Office
Page 1: ... ...