Technical Guide
Eclipse INU Card Maintenance Guidelines
Corporate Headquarters
Stratex Networks
120 Rose Orchard Way
San Jose, CA 95134
Telephone: +1.408.943.0777
Facsimile: +1.408.944.1648/9
North America
NorthAmerica@stratexnet.com
Latin America
LatinAmerica@stratexnet.com
Asia Pacific
AsiaPacific@stratexnet.com
Europe
Europe@stratexnet.com
Middle East and Africa
MEA@stratexnet.com
Sub-Saharan Africa
SouthAfrica@stratexnet.com
www.stratexnet.com
This guide provides rules, hints and tips for withdrawing and inserting plug-in cards on the INU/INUe.
It includes the actions of non-protected and protected card withdrawal/insertion, and insertion of
additional cards.
CAUTION: Always wear an ESD grounding strap when changing or handling plug-in cards and
avoid hand contact with the PCB back-plane and top-plane. Connect your ESD
grounding strap to the ground connector on the INU rack ear.
NOTE: Slots: For information on which slots are appropriate for which plug-ins, refer to the
Eclipse User Manual, Volume III, Chapter 3; Installing the INU and INUe.
Protection: For information on Node protection options, protection switch criteria
and switch times, refer to Eclipse User Manual, Volume II, Chapter 3; Node
Protection Options.
Testing: For information on test procedures for Node protection options, refer to
Eclipse User Manual, Volume V, Chapter 1; Commissioning.
Contents
Rules Essential card management data.
Card Protection Options List of protectable and un-protectable cards
Quick Guide Summary guidelines for card withdrawal/insertion.
Detail Guide Detail guidelines for card withdrawal/insertion with descriptions of
protected operation.
LED Indications Table of front-panel LED indications.
Portal Problem Icons List of Portal problem icons.
Regional Help Desks Contact details for technical help desks.
Rules
All cards are hot-pluggable, meaning they can be withdrawn and inserted, or new cards added
while the INU is powered on.
Cards must be withdrawn and inserted using their finger-grip fasteners/pulls. Never withdraw or
insert using attached cables.
All slots must be filled with either a card or a blanking panel. Failure to do so will compromise
EMC integrity and distribution of cooling air from the FAN.
Keep any removed blanking panels for future use.
Spare cards or cards to be returned for service must be enclosed in an anti-static bag. When
removing a card from the anti-static bag for installation in an INU, or placing a card in a bag, do so
at the INU and only when connected to the INU via your ESD grounding strap.
When installing a card, ensure its backplane connector is correctly engaged before applying
sufficient pressure to bring the card panel flush with the INU front panel.
Cards must be held secure by their fasteners.
Eclipse INU Card Maintenance_Ltr_Oct05 Page 1 of 15
Technical Guide

When removing a RAC from a powered INU, always disengage the RAC from the backplane
before disconnecting its ODU cable. Similarly before inserting a RAC, always reconnect the ODU
cable before engaging the backplane. Arcing during live connection and disconnection of the ODU
cable can damage connector contact surfaces, and power spikes may also cause momentary errors
on other traffic passing through the INU. The only exception to live disconnection and connection
should be for checks of protected operation at link commissioning.
The DC power connector on the NCC and NPC can be shorted inadvertently if applied at an angle.
Always insert with correct alignment.
For a DAC 16x, ensure correct orientation of the Mini RJ-21 connector before pushing it home.
This can be checked by the scalloped key to one side of the connector. Additionally, a trib cable
supplied by Stratex Networks will have the cable exiting to the right side when viewed from the
front.
When swapping or installing new cards, up to 60 seconds can be required for the INU to show its
revised status via the front panel LEDs, or via Portal.
Several seconds may be needed for the NCC to recognize a card withdrawal and insertion. This
particularly applies to RACs.

Card Protection Options

Protectable cards: NCC
RAC 30
RAC 10
RAC 3X
RAC 40
DAC 155o
DAC 2x155o
DAC 155oM
DAC 2x155e
Non-protectable cards: DAC 4x
DAC 16x
DAC ES
DAC GE
AUX

Eclipse INU Card Maintenance_Ltr_Oct05 Page 2 of 15

Technical Guide

Quick Guide
The Quick Guide provides an overview of INU/INUe action when a card is withdrawn/inserted. For
information on LED indications, Portal event browser and alarm indications, protected operation and
protected switch action, refer to the Detail Guide.

Non-Protected Card Action

Unless a card is protected, the service provided by a withdrawn card is lost.

Protected Card Action

NCC/NPC
NCC Withdrawal
NPC protects NCC bus clock management and power supply.
o Protection of the bus clock is not hitless (service is
Clock Online <100 ms hit

interrupted). Clock Offline Nil hit

o Protection of the power supply is hitless (service is not
NPC Withdrawal
interrupted).
Clock Online <100 ms hit
When the NCC is withdrawn, the switch to NPC clocking affects
Clock Offline Nil hit
all traffic on the Node for <100 ms.
When the NCC is re-inserted traffic is not affected clock management remains with the NPC.
There is no operational need to return clock management to the NCC.
If clock management is returned to the NCC, or the NPC is withdrawn while it is managing the
bus clock, the switch to NCC clocking affects all traffic on the Node for <100 ms.

RAC/RAC Hot-Standby and Space Diversity

RAC Withdrawal
One RAC is transmitting. Both RACs are receiving; the online Rx
RAC manages Rx voting. TX Online <100 ms hit

The primary RAC is the default online Tx RAC. Tx Offline Nil hit

The secondary RAC is the default online Rx RAC. Rx Online <100 ms hit
Rx Offline Nil hit
Tx switching is not hitless.
Rx switching is hitless providing the online RAC is not withdrawn.
When a RAC is withdrawn:
o If it is providing the online Tx, the switch of online status to the partner Tx RAC affects
all link traffic for <100 ms.
o If it is providing the online Rx function, the switch of online status to the partner Rx RAC
affects all link traffic for <100 ms.
o If it is providing the offline (protection partner) Tx or Rx function, link traffic is not
affected.

RAC/RAC Frequency Diversity

RAC Withdrawal
Both RACs are transmitting and receiving.
o The online Tx RAC controls Tx traffic synchronization.
TX Online <100 ms hit

o The online Rx RAC manages Rx voting.

Tx Offline Nil hit
Rx Online <100 ms hit
The primary RAC is the default online Tx RAC.
Rx Offline Nil hit
The secondary RAC is the default online Rx RAC.
Tx switching is hitless providing the online Tx RAC is not withdrawn.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 3 of 15

Technical Guide

Rx switching is hitless providing the online Rx RAC is not withdrawn.

When a RAC is withdrawn:
o If it is providing the online Tx or Rx function, the switch of online status to the partner
RAC affects all link traffic for <100 ms.
o If it is providing the offline (protection partner) Tx or Rx function, link traffic is not
affected.

RAC/RAC Ring Protection

RAC Withdrawal
Both RACs are transmitting and receiving. One is the east RAC,
East RAC <100 ms hit
the other is west.
West RAC <100 ms hit
Protection is provided by ring-wrapping. Wrapping and
unwrapping is not hitless.
When a RAC is withdrawn the ring is wrapped at this Node and at the remote Node for the link.
Affects all ring traffic for <100 ms.
When the RAC/link is restored to service, the ring is automatically unwrapped after a time-out
period of 5 minutes. Unwrapping affects all ring traffic for <100 ms.

DAC/DAC Protection DAC Withdrawal

One DAC is normally transmitting (to customer) and receiving
DAC Online <100 ms hit
(from customer).
DAC Offline Nil hit
The primary DAC is the default online Tx and Rx DAC.
o Tx and Rx tribs are switched independently, which means one DAC can be online Tx and
the other online Rx.
o When a switch occurs, all Tx and/or Rx trib traffic is switched.

Switching is not hitless.

When a DAC is withdrawn:
o If it is providing the online Tx and/or Rx function, the switch of online status to the
partner DAC affects DAC traffic for <100 ms.
o If it is providing the offline Tx or Rx function, DAC traffic is not affected.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 4 of 15

Technical Guide

Detail Guide
The detail guide provides a description of INU/INUe events and indications resulting from the
withdrawal and insertion of a plug-in card. Includes descriptions of protected operation and protected
switch action.

Contents
When a Card is Withdrawn / Inserted
When a Protected Card is Withdrawn / Inserted
NCC/NPC
Protection Function
LED and Portal Indications
RAC/RAC
Protection Function
Online/Offline
LED and Portal Indications for Hot-Standby and Diversity RACs
LED and Portal Indications for Ring RACs
DAC/DAC
Protection Function
LED and Portal Indications
When a New (Additional) Card is Inserted

When a Card is Withdrawn / Inserted

This section describes expected LED and Portal screen responses when a card is withdrawn from an
INU that is operating normally (no live LED or Portal alarms), and then reinserted.
CAUTION: Unless a card is protected, the service provided by a withdrawn card will be lost.
Withdrawing an NCC, unless protected by an NPC, will kill the Node all traffic will
be lost.
Withdrawing a card will cause:
1. The NCC status LED to flash orange.
2. A major alarm and a card missing icon to appear in the status bar of all Portal screens
(bottom of screen). Depending on the card, card version, and software version, a transport
problem icon may also appear and the major alarm may become a critical alarm.
3. A major alarm and a card missing icon to appear against the withdrawn plug-in in the
Diagnostics > System Summary screen (Portal opening screen). Depending on the card, card
version, and software version, a transport problem icon may also appear and the major alarm
become a critical alarm.
4. Card missing to appear against the withdrawn plug-in in the Configuration > Layout screen.
5. A slot plug-in missing event in the Diagnostics > Event Browser screen. Other events will also
be displayed, depending on the card type and traffic carried.
6. A slot plug-in missing alarm in the Diagnostics > Alarms screen > NCC. Other alarms may also
be displayed, depending on the card type and traffic carried.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 5 of 15

Technical Guide

Re-inserting a card will cause:

1. The NCC status LED to go green within approximately 10 seconds.
2. The service provided to return to normal. Depending on the card, this may take up to two
minutes, during which time the status bar and system Summary screen will display a checking
plug-in icon. Once cleared the status LED on the inserted card will go green, and all
related problem icons and alarms will be cleared.
3. For a RAC, its status LED will initially be red, and then become green after about 30 to 40
seconds. Its online LED will remain unlit until the status LED goes green, whereupon it goes red
for approximately 15 seconds before becoming green to indicate the link is up.

When a Protected Card is Withdrawn / Inserted

This section describes the protection provided and expected traffic, LED and Portal screen action when
a protected card is withdrawn/inserted. Information is provided for NCC/NPC, RAC/RAC and
DAC/DAC pairings.

NCC/NPC
Protection Function
The NPC provides protection for NCC TDM bus management (bus clock), and power supply functions.
One NPC can be installed per INU/INUe. Bus protection protects all payload and auxiliary traffic;
Alarm I/O is not protected.
Switching is not hitless (service is interrupted) for a bus clock failure; service is restored within 100 ms,
during which time all traffic on the node is affected.
Protection is hitless (service is not interrupted) for a power supply failure. If the NCC power supply or
one of its supply rails fails, the NPC will take over without interruption. And vice versa.
When the bus clock has switched to NPC control, it will not automatically revert to NCC control on
restoration of the NCC. Return to NCC control requires either withdrawal/failure of the NPC, or use of
commands in the Diagnostics > System/Controls screen. (There is no operational need to always revert
to NCC for bus clocking).
LED and Portal Indications
Normal status is indicated by green NCC Test and Status LEDs, a green NPC Status LED, and an unlit
NPC Protect LED. This indicates that bus clock management is with the NCC and that the NPC is ready
to protect.
Withdrawing an NCC that is managing the bus clock will cause:
A green NPC Protect LED, indicating the bus clock has switched to NPC control.
Momentary loss of traffic through the node (< 100 ms).
Loss of all Portal updates. Screens will be frozen at a point just prior to NCC withdrawal.
Withdrawing an NCC that is not managing the bus clock will cause:
No change to NPC Status and Protect LEDs; both will remain green.
No loss of traffic through the node.
Loss of all Portal updates. Screens will be frozen at a point just prior to NCC withdrawal
Withdrawing an NPC that is not managing the bus clock will cause:
NCC status LED and Portal screen indications for card missing. Refer to When a Card is
Withdrawn / Inserted on page 5.
No loss of traffic through the node.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 6 of 15

Technical Guide

Withdrawing an NPC that is managing the bus clock will cause:

NCC status LED and Portal screen indications for card missing. Refer to When a Card is
Withdrawn / Inserted on page 5.
Momentary loss of traffic through the node (< 100 ms).
If bus clocking is with the NPC (green NPC Protect LED), then the NCC can be removed and restored
without impacting traffic. If the clock is with the NCC (unlit NPC Protect LED), the NPC can be
removed and restored without impacting traffic.
Re-installing an NCC
No change to NPC Status and Protect LEDs; both will remain green. Bus clock management
remains with the NPC until forced back to the NCC using commands in Diagnostics >
System/Controls, or withdrawal of the NPC.
No loss of traffic through the node.
Return of Portal screen access after approximately 2 minutes. NCC Test and Status LEDs will be
green.
IF testing NCC/NPC protection operation, wait at least 3 minutes after restoring the NCC before
removing the NPC.
Re-installing an NPC
NCC status LED will return to green within approximately 10 seconds.
No loss of traffic through the node.
Normal NPC ready to protect indications of a green Status LED and an unlit Protect LED will
be returned within approximately 30 seconds.
Return of normal Portal screen indications. Refer to When a Card is Withdrawn / Inserted on
page 5.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 7 of 15

Technical Guide

RAC/RAC
Protection Function
Transmit switching for hot-standby and space diversity is not hitless; service is restored within 100 ms.
Transmit switching for frequency diversity is hitless providing the online Tx RAC is not removed.
Receive switching for hot-standby and space/frequency diversity is hitless with RAC 30s, RAC 3Xs,
RAC 40s, and RAC 10v2s, providing the online Rx RAC is not removed. Paired RAC 10v1s may be
used for hot-standby operation, but receive switching is not hitless.
Ring protection using back-to-back RACs is provided by ring-wrapping. Ring wrapping and
unwrapping is not hitless.
Online/Offline. The meaning of Online and Offline for hot-standby and space/frequency diversity
is summarized below. For ring protection, both RACs are online Tx and Rx.
The primary RAC is default online Tx; secondary RAC is default online Rx.

Online/Offline Protection Type Meaning of Online/Offline

Tx Online Hot-standby and space Refers to the RAC that is on-air transmitting.
(default diversity:
primary RAC) Frequency diversity: Refers to the RAC that is controlling the Tx
synchronization. (Both online and offline RACs
are transmitting).
Rx Online Hot-standby and Refers to the RAC that is controlling Rx hitless
(default space/frequency diversity: switching (voting) and sending the Rx traffic to
secondary the TDM bus. (Both RACs are receiving but the
RAC) online Rx RAC decides which Rx stream to
select).
Tx Offline Hot-standby and space Refers to the non-transmitting partner Tx RAC.
(default diversity:
secondary Frequency diversity: Refers to the RAC Tx that is not controlling Tx
RAC) synchronization. (Offline Tx is transmitting).
Rx Offline Hot-standby and Refers to the RAC that is partnering the online
(default space/frequency diversity: Rx RAC. (Offline RAC is receiving).
primary RAC)

When an online RAC is withdrawn the resulting protection switch action must be understood to
understand how traffic will be affected:
Transmit Switching, Hot-standby and Diversity:
The primary RAC is the default online Tx RAC.
When a Tx switch from primary to secondary occurs, the online Tx status is transferred from the
primary to secondary RAC, and remains with the secondary RAC; the primary-designated RAC
is not automatically returned to online on repair/replacement. The same process occurs in reverse
- for a switch from secondary RAC Tx online to primary RAC Tx online.
o For hot-standby and space diversity the online Tx status is changed for a card withdrawal,
RAC/ODU failure, or software load failure.
o For frequency diversity the online status is only changed for a card withdrawal or software
load failure.
The switch of online Tx status is not hitless, service is restored within 100 ms.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 8 of 15

Technical Guide

Receive Switch Operation, Hot-standby and Diversity:

Receiver switching (voting) between the two receiving RACs is hitless for hot-standby and
diversity configurations. The least errored data stream is selected on a frame-by-frame basis
within the online, bus-driving, Rx RAC. This is the RAC that is controlling the protection
switch, and is by default the secondary RAC in a protected primary/secondary pairing.
o The protection switch function is contained within the RACs and is transferred between
RACs to always be with the online Rx RAC.
o Changing the online status from one RAC to the other using the locks in the
System/Controls screen, or by removing the online Rx RAC, forces the online protection
switch function to the partner RAC, which causes a service interruption of not more than
100 ms.
Receive Switch Action, Hot-standby and Diversity:
If the designated offline Rx RAC (default primary) fails or is removed, the receive data stream
will not be errored as the RAC designated as online (default secondary) is controlling the
switching and driving the TDM bus.
If the designated online Rx RAC (default secondary) receiver fails, the receive data stream will
not be errored if the failure occurs prior to the RAC Rx diversity bus (between ODU antenna
input and the RAC Rx diversity bus).
If the designated online Rx RAC (default secondary) fails after the diversity bus (between RAC
Rx diversity bus and the TDM bus) or the RAC is removed, the offline Rx RAC (default
primary) is switched to become the online bus-driving and protection-controlling RAC. This
switching is not hitless (< 100 ms), and the primary RAC remains as the online bus-driving RAC
until changed within Portal or ProVision, or a subsequent bus-drive switch event.
Selection of online RACs:
Tx and Rx online status can be checked and selected (forced) in the Diagnostics > System/Controls
screen.
There is no operational requirement to stay with default settings of primary RAC for online Tx and
secondary RAC for online Rx, except for single-antenna hot-standby operation with an unequal-loss
coupler. For this configuration, the low-loss side should be assigned to the online Tx RAC (default
primary), and in the event of a switch, online Tx should be returned to the RAC connected to the low-
loss side, which should ideally be at a time when traffic will be least affected.
Transmit and Receive Switching, Ring:
In an Eclipse Super-PDH ring one RAC is configured as east, the other as west. Both are online
Tx and Rx.
Switching is not hitless for a ring-wrap or unwrap; service is restored within 100 ms.
The unwrap command to return to normal ring operation occurs 5 minutes after all wrap
conditions are cleared.

LED and Portal Indications for Hot-Standby and Diversity RACs

The following indications are with default RAC settings, where the primary designated RAC is online
Tx, and the secondary RAC is online Rx.
Both RACs will have green Online and Status LEDs. (The Online LED will be green for Tx or Rx
online, or for Tx and Rx online. The Online LED will be unlit for a RAC that is offline for both Tx and
Rx).
Default settings must be maintained for the following descriptions to be valid. Settings can be
checked/forced in the Diagnostics > System/Controls screen. (If other online settings are used, use the
transmit switching and receive switching information under Protection Function to work out how traffic
will be affected).

Eclipse INU Card Maintenance_Ltr_Oct05 Page 9 of 15

Technical Guide

NOTE: No protection switch operation is permitted within a 2 minute period from power-on,
which is also the time typically required before Portal log-in is permitted.
Withdrawing the primary RAC will cause:
Assumes the default situation of primary RAC online for Tx and secondary RAC online for Rx.
A Tx switch for hot-standby and space/frequency diversity; Tx online is switched from primary
RAC to secondary. Switch is not hitless; Tx is restored within 100 ms.
No Rx hit (Rx traffic not affected).
NCC status LED and Portal screen indications for card missing. Refer to When a Card is
Withdrawn / Inserted on page 5.
At this point, the secondary RAC is online for Tx and Rx.
Re-installing the primary RAC will cause:
Assumes re-insertion of the primary RAC following its withdrawal above.
No Tx switch. Tx stays with secondary RAC.
No Rx hit.
NCC status LED will return to green within approximately 10 seconds.
Primary RAC status LED to go from red to green within approximately 30 seconds. Online LED
to go from red to unlit within a further 20 seconds.
Return of normal Portal screen indications. Refer to When a Card is Withdrawn / Inserted on
page 5.
At this point the secondary RAC is online for Tx and Rx.
Withdrawing the secondary RAC will cause:
Assumes the default situation of primary RAC online for Tx and secondary RAC online for Rx.
An Rx switch. Switch is not hitless; service is restored within 100 ms.
No Tx switch.
NCC status LED and Portal screen indications for card missing. Refer to When a Card is
Withdrawn / Inserted on page 5.
At this point, the primary RAC is online for Tx and Rx.
Re-installing the secondary RAC will cause:
Assumes re-insertion of the secondary RAC following its withdrawal above.
No Tx switch.
No Rx hit. Online Rx remains with the primary RAC.
NCC status LED to return to green within approximately 10 seconds.
Secondary RAC status LED to go from red to green within approximately 30 seconds. Online
LED to go from red to unlit within approximately 20 seconds.
Return of normal Portal screen indications. Refer to When a Card is Withdrawn / Inserted on
page 5.
At this point the primary RAC is online for Tx and Rx.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 10 of 15

Technical Guide

LED and Portal Indications for Ring RACs

The following indications are for east and west configured RACs in an Eclipse Super-PDH ring. For
normal unwrapped operation, both RACs are online Tx and Rx; both will have green status and online
LEDs.
NOTE: Before withdrawing a RAC to test ring protection, a node must have been switched on for
not less than 5 minutes to ensure completion of internal system checks and updates.
Withdrawing the east or west RAC will cause:
A ring-wrap; the ring will be wrapped at this site and at the remote site for the affected link. Ring
traffic is restored within 100 ms.
NCC status LED and Portal screen indications for card missing. Refer to When a Card is
Withdrawn / Inserted on page 5.
Re-installing the east or west RAC will cause:
Assumes re-insertion of the RAC withdrawn above. To view normal LED indications, do not re-insert
until at least 20 seconds after withdrawal.
The RAC status LED will initially go red, and then become green after about 30 to 40 seconds.
The RAC online LED will remain unlit until the status LED goes green, whereupon it goes red
for approximately 15 seconds before becoming unlit. It will stay unlit until the unwrap timeout
period of 5 minutes is up, whereupon it will go green, indicating normal unwrapped operation.
o The System Summary screen for Eclipse SW releases to 3.0.72 (July 2005) provides normal
RAC return-to-service indications as in When a Card is Withdrawn / Inserted on page 5, but
does not indicate wrapped status. To view wrap status in Portal, select Diagnostics >
System Controls > RAC.
o Eclipse SW releases from 3.0.72 include a ring-wrapped icon in the System Summary
screen.
Other Portal screen indications are as in When a Card is Withdrawn / Inserted on page 5.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 11 of 15

Technical Guide

DAC/DAC
Protection Function
Tributary protection (DAC redundancy) is provided by operating two identical DACs as a protected
pair. Tx and Rx tribs are independently switched meaning it is possible for one of the DACs to be
online Tx, and the other online Rx.
When a switch occurs, all Tx and/or Rx tributaries are switched to the protection partner.
Switching is not hitless; trib traffic is restored with 100 ms.
The DACs are configured as primary and secondary. The primary is the default online DAC for Tx and
Rx.
Two protection options are provided, tributary protection, or always-on:
Tributary Protection (TT):
"Y" cables connect the paired DACs to customer equipment.
In the Rx direction (from the customer) both DACs receive data, but only the online Rx DAC
sends this data to the TDM bus.
In the Tx direction, the online Tx DAC sends data to customer equipment, the other mutes its Tx
line interface.
Tributary Always On (TA):
Separate cables connect each DAC to customer equipment.
In the Rx direction (from the customer) both DACs receive data, but only the online Rx DAC
sends this data to the TDM bus.
In the transmit direction both DACs send data to customer equipment, and the customer
equipment switches between these two "always on" tributaries.
TA protection must be used where two Eclipse INU/INUes are to be interfaced using protected
DACs.

LED and Portal Indications for DACs

The following indications are with default DAC settings, where the primary designated DAC is online
for Tx and Rx. Both DACs will have green status LEDs.
If other online settings are used, use the Tx and Rx protection information above to work out how trib
traffic will be affected. Online settings can be checked/forced in the Diagnostics > System/Controls
screen.
NOTE: No protection switch operation is permitted within a 2 minute period from power-on,
which is also the time typically required before Portal log-in is permitted.
Withdrawing the primary DAC will cause:
Assumes the default situation of primary DAC online for trib Tx and Rx.
A Tx and Rx switch to the secondary DAC. Switch is not hitless; service is restored within 100
ms.
NCC status LED and Portal screen indications for card missing. Refer to When a Card is
Withdrawn / Inserted on page 5.
At this point, the secondary DAC is online for Tx and Rx.
Re-installing the primary DAC will cause:
Assumes re-insertion of the primary DAC following its withdrawal above.
No Tx or Rx trib switch. Tribs remain with the secondary DAC.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 12 of 15

Technical Guide

Withdrawing the secondary DAC will cause:

Assumes the default situation of primary DAC online for trib Tx and Rx.
No trib Tx or Rx switch. Tribs stay with the primary DAC.
NCC status LED and Portal screen indications for card missing. Refer to When a Card is
Withdrawn / Inserted on page 5.
At this point, the primary DAC is online for Tx and Rx.
Re-installing the secondary DAC will cause:
Assumes re-insertion of the secondary DAC following its withdrawal above.
No Tx or Rx trib switch. Tribs remain with the secondary DAC.

When a New (Additional) Card is Inserted

Ensure that:
The new card is of a type that is compatible with the selected backplane bus configuration for the
INU/INUe. Bus configuration for E1, DS1, E3, DS3 or STM1/OC3 is selected in the
Configuration > Circuits screen.
The Node license is valid for installation of new RACs and their intended capacity.
Appropriate slot allocations are used. Refer to the Eclipse User Manual, Volume III, Chapter 3;
Installing the INU and INUe.
Installing a new card will cause:
No change to NCC LEDs.
No change to System Summary screen.
System Layout screen to show the newly occupied slot as status Unexpected, and a description
of Detected: (card type) and Expected: Empty. To accept the new card or cards, click on Use
Detected, or Use Detected for All, then click Send.
The status LED for the new card will go green after approximately 30 seconds.
The new card can now be configured.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 13 of 15

Technical Guide

LED Indications
Table summarizes INU/INUe LED behavior. Empty cells in table indicate that the associated LED state
is not used.

LED
LED
State NCC Status NCC DAC Status RAC Status RAC NPC NPC FAN
Test AUX Status Online Status Protect
Off INU/INUe INU/INUe INU/INUe INU/INUe INU power INU/INUe Off-line Normal
(unlit) power off power off power off power off off, or power off operation
ODU is
Ready
muted and to
RAC is not
protect
driving the
TDM bus
Green Normal Normal Normal Transmitter Normal On-line
operation operation operation is online, operation (driving
or RAC is TDM
driving bus
(Rx) the clock)
TDM bus
Orange Configuration Diagnostic Configuration Configuration
Flashing corrupt or not (test) corrupt or not corrupt or not
supported, card mode supported, or supported, or
missing, or active incompatible incompatible
incompatible software software
software
Red Critical alarm Critical alarm RAC or ODU No Rx Critical Critical
critical alarm signal from alarm alarm
ODU

Portal Problem Icons

Eclipse INU Card Maintenance_Ltr_Oct05 Page 14 of 15

Technical Guide

Regional Technical Help Desks

Americas Technical Help EMEA Technical Help Asia Pacific Technical Help

Stratex Networks Stratex Networks Stratex Networks

120 Rose Orchard Way 4 Bell Drive Bldg 10, Unit B
San Jose, CA 95134-1358 Hamilton International Philexcel Industrial Park
U.S.A. Technology Park Clark Special Economic Zone
Blantyre, Scotland Clark Field
G72 0FB Pampanga, Philippines
United Kingdom
Phone: Phone: Phone:
0800 362 9283 (free within USA) +44 1698 717 230 +63 45 599 5192
+44 1698 714076 from outside USA
Email: Email: Email:
americas_help@stratexnet.com emea_help@stratexnet.com asia_help@stratexnet.com

You can also call your local Stratex Networks office. Contact information is available on our website at
www.stratexnetworks.com.

Eclipse INU Card Maintenance_Ltr_Oct05 Page 15 of 15