Alcatel-Lucent 9500 MXC, Руководство пользователя

Страница: 661 / 916

9500 MXC User Manual
3DB 23063 ADAA - Rev 004 July 2007 Vol. V-2-5
• Many hardware alarms are only initiated as a loss-of-communications alarm
during a reboot, software upgrade, or reconfiguration. By not being able to
communicate with the NCC/IDU, their settings cannot be loaded. The fault
may be at the hardware device (most likely), communications to it, or the
NCC/IDU.
• Hardware/software compatibility alarms will be raised when a new plug-in
is installed that needs a later version of 9500 MXC software.
• A configuration not supported alarm will be raised if the installed license is
incompatible with the configured RAC/radio capacity.
• NCC slot management alarms will be raised when a plug-in is installed in a
slot that has been configured for a different plug-in, or a configured plug-in
is missing.
•
RAC before an ODU
. If there is doubt about whether a fault is in a RAC/IDU,
or ODU, always replace the RAC/IDU first; it is quicker and easier.
• Hot-pluggable . INU/INUe modules are hot-pluggable. There is no need to
power-down before replacing, but traffic will be lost unless the plug-in is
protected. Unplugging the NCC will cause all traffic to be lost, unless protected
by an NPC.
•
Plug-in restoration time
. Ensure adequate time is allowed for services to
resume when a plug-in is replaced:
• When an option-slot plug-in is replaced it should resume operation within
60 seconds. Check for a green Status LED, and for a RAC, a green Online
LED. An exception is where the replaced RAC is one of a protected pair, and
its partner is online for Tx and Rx. In this situation the online LED of the
replaced RAC will become unlit, indicating it is ready to protect for Tx and/
or Rx.
• Unless protected by an NPC, when an NCC is replaced it is the same as
booting from cold, meaning up to two minutes may be needed for all LED
indications to stabilize, and for CT communications to re-establish.
• If an NCC is protected by an NPC, and the TDM bus clock is with the NCC,
there is a momentary traffic hit (less than one errored second) as the clock
switches to NPC control. When an NCC is re-inserted, there is no traffic hit,
as the clock remains with the NPC until forced to return to the NCC using
the CT Systems/Control screen, or by unplugging the NPC.
• Additional NCC-specific restoration times . While traffic should return to
normal within two minutes for a rebooted node, there are two situations
requiring additional time:
There is no operational requirement to return a clock from NPC to NCC; should
the NPC fail it auto-switches the clock to the NCC.