This section describes the read-only status indicators in the Host Summary view. For
information on setting Host attributes, see “Enter a Host Name, Clock Source, and
Linking Mode” on page 147 and “Changing to Built-In Network Mode” on page 186.
To open the
select
, and then click on the Host name node.
view in the EMS View Frame, in the Function Explorer Tree
The read-only status indicators are:
•
—Current summary alarm state of Host SeRF card. Red indicates that a major
alarm exists for some component module of the SeRF. Yellow indicates a minor
alarm.
•
—Current summary alarm state is indicated by status indicator on same row
of page. Red indicates that a major alarm exists for the DART. Yellow indicates a
minor alarm.
•
—Dry alarm NO/NC contact (labeled ALARM
OUTPUTS HOST) on the Host. Current state of major alarm contacts is indicated
by Alarm Summary status indicator on same row of page.
•
—Dry alarm NO/NC contact (labeled ALARM
OUTPUTS HOST) on the Host. Current state of minor alarm contacts is indicated
by Alarm Summary status indicator on same row of page.
•
Red indicates Host NO/NC major alarm
contacts are in an alarm position. These connections are typically wired to a local
alarm alert system. This status indicator is red when a major alarm is present on
any Remote connected to the Host.
•
Red indicates that Host NO/NC minor alarm
contacts are in an alarm position. These connections are typically wired to a local
alarm alert system. This status indicator is red when a minor alarm is present on
any Remote connected to Host.
Once you click OK, the confirmation dialog closes and the Host reboots. It will
take some time for the Host to retrieve data from connected Remotes and to
reconfigure data on the Remotes. During this time, an alert message displays in
the
view and on any other page where data can be set. Any attempt
to SET will fail. You cannot make configuration changes while this message is
displayed. Wait until the message clears before continuing with configuration
settings.
view is a summary of throughput and number of errors
on the twelve Ethernet (ENET) ports on the Host SeRF card. These ports consist of
eight ports used for connection to Remotes and four ports used for system
management and maintenance functions.
22(Optional) To enlarge the view, click Full Screen to open a separate window that
shows only the
table.
33To update the counters, click
The
view lists the Ethernet ports and their corresponding
.
status.
••The row headers in the first column are as follows:
–
–
–
–
–
—on card processor's connection to the switch on the SeRF card
—on card processor's connection to the PHY port labeled Craft
—Ethernet switch interface to SFP 1-8
—Ethernet switch interface to on-card processor
—switch interface to the PHY port labeled Network
••The column headers, from left to right, are as follows:
–
—Receive byte counter. Increments by the byte count of frames
received, including those in bad packets, excluding preamble and SFD but
including FCS bytes
–
—Receive packet counter. Increments for each frame received
packet (including bad packets, all unicast, broadcast, and multicast
packets)
–
—Receive FCS error counter. Increments for each frame
received that has an integral 64 to 1518 length and contains a frame check
sequence error
—Receive broadcast packet counter. Increments for each
broadcast good frame of lengths 64 to 1518 (non VLAN) or 1522 (VLAN),
excluding multicast frames. Does not include range/length errors
–
—Receive multicast packet counter. Increments for each
multicast good frame of lengths 64 to 1518 (non VLAN) or 1522 (VLAN),
excluding broadcast frames. This count does not include range/length
errors
–
—Receive fragments counter. Increments for each
frame received that is less than 64 bytes and contains an invalid FCS. This
includes integral and non-integral lengths
–
—Receive jabber counter. Increments for frames received
that exceed 1518 (non VLAN) or 1522 (VLAN) bytes and contain an invalid
FCS. This includes alignment errors
–
—Transmit byte counter. Increments by the number of bytes
that were put on the wire including fragments of frames that were involved
with collisions. This count does not include preamble/SFD or jam bytes.
This counter does not count if the frame is truncated
–
—Transmit packet counter. Increments for each transmitted
packet (including bad packets, excessive deferred packets, excessive
collision packets, late collision packets, all unicast, broadcast, and
multicast packets)
–
—Transmit broadcast packet counter. Increments for
each broadcast frame transmitted (excluding multicast frames)
–
—Transmit multicast packet counter. Increments for each
Only a user logged in under the admin or a Network Manager account can change Prism
system settings t
This procedure is for decommissioning a DART in a Host. For information on
decommissioning a DART in
on page 232.
hrough the EMS.
a Remote, see “Decommissioning an RF Module in a Remote”
The
removed. You use the
button is available only when a DART has already been physically
button to remove DART configuration settings
and to delete DART alarms from EMS alarm summaries. Entries in the Alarm History
Log, however, are preserved.
Decommission a DART only if it has been permanently removed from the Remote and
will not be replaced
procedure removes information about the
inventory) from the EMS database.
You must delete any RF links before you can decommission a Host DART. The FlexWave
system prevents a
11In the Function Explorer Tree, select
the Host name) to open the
with another DART. When a DART is taken out of service, this
page provides a summary for the SeRF (Serial Radio Frequency) card
located in the Host. The Host SeRF card contains the processor chip where the EMS
software documented in this manual resides. The SeRF controls communication
between the Host and the Remotes, and maintains the system configuration settings.
In the Function Explorer Tree, select
name) to open the
-n view in the EMS View Frame.
(where
x is the Host
The
•
—alarm status indicator for Host optical ports. Red indicates that an
-n view has the following elements:
alarm exists for at least one of the eight optical ports on the SeRF card. Yellow
indicates a minor alarm.
•
—state of the SeRF. Red indicates that either the SeRF clock source is
unacceptable or the SeRF card FPGA is not programmed.
•
—state of the Host chassis fan. Red indicates that the Host chassis
•
temperature of the Host is above its operating limits. Fault threshold is
•
—Red indicates that the current chassis-internal
.
—Indicates that there is another Host in a Multi-Host
system that has the same Clock Priority Level (CPL) as this Host. All Hosts that are
in conflict generate this alarm. When all Hosts with this alarm are provisioned
with unique CPLs, the alarm clears. Service is disrupted on all systems when this
alarm is present. The
•
—Yellow indicates that the current chassis-internal
temperature of the Host is below its operating limits. Fault threshold is
•
—In a three-Host system, indicates that the Clock
is a Major alarm.
.
Priority Level for the Host managing the Remote has been changed. All Hosts in
the system generate this alarm. When all Hosts with this alarm are provisioned
with unique CPLs, the alarm clears. Service is not disrupted, but could become
disrupted if the host providing the clock becomes unavailable. The
•
is a Minor alarm.
—Gives the current chassis-internal temperature in
degrees Centigrade detected by the Host.
For corrective actions for alarm states, refer to “Troubleshooting Alarms” on
page 264. For information on setting the Clock Priority Level, see “Set the Clock
Priority Level” on page 150.
view shows the current usage and alarm status of the optical
ports on the Host plus the current values of some key operating parameters. The Host
has eight optical ports, but the
view only shows active ports
(physically connected to a Remote). Each port in the page represents one set of
forward and reverse paths between a Host and Remote. Physically, this may have
been accomplished with two fibers through that port or with a single fiber (if WDM is
used). Each physical port contains an SFP transceiver with two connectors.
The
view provides a link that can be used to enter or edit the name
for a Host optical port (see “Enter a Host Name, Clock Source, and Linking Mode” on
page 147).
For corrective actions for alarm states, refer to “Troubleshooting Alarms” on
page 264.
To access the
The
view for
(where
view, in the Function Explorer Tree, select
x is the Host name).
-n opens in the EMS View Frame, which only shows the
,
Receive power level from the Remote unit (REV path). To see the Receive power level
in the FWD path (from the Host to the Remote), you must open the
view
for the desired Remote as described in “Viewing Remote SeRF Optical Ports” on
The following informational columns are provided in the
•
•
—System assigned port number. This is a link to the
for this particular port.
—user entered port name or
, which indicates that
table.
no name has been entered.
•
—indicates that the laser range, which is
to meet 3Gbps
optical transmission requirements.
•
—Launch power level in dBm of forward path signal. The minimum
FWD launch power is -2 dBm, and the maximum is 3 dBm.
•
—Receive power level in dBm of reverse path signal, which incorporates
the launch power of the Remote Unit SFP plus all optical losses (insertion losses,
fiber cable loss, and so forth). The minimum REV launch power is -27 dBm, and
the maximum is -9 dBm.
•
—Number displayed is wave length transmitted through this port:
–Non-duplex and WDM configurations: 1550 nm fwd, 1310 rev
–CWDM configurations can be one of eight wavelengths: 1470, 1490, 1510,
1530, 1550, 1570, 1590, 1610.
•
—An attempt to enable IP on a fiber (Host) to a Remote that already
has IP enabled on another fiber (Host) has been made. The alarm is cleared if IP is
disabled on the fiber. It is also cleared if IP becomes enabled. This latter condition
can occur if the fiber that was already carrying IP later has IP disabled, or if the
fiber otherwise becomes disabled. For information on setting Ip Enable, see
“Configure the Remote SeRF Optical Ports” on page 158.
•
—Yellow indicates that too many errors have been received on the
receiving fiber. Fault threshold is
•
threshold is below
•
•
Fault threshold is
•
Fault threshold is
•
—Red indicates that no light is detected on the receiving fiber. Fault
—Red indicates that the forward path laser is faulty.
—Red indicates power of signal received on the fiber is too strong.
. Threshold cannot be changed.
—Yellow indicates power of signal received on fiber is too weak.
—name of the Remote connected to this Optics port.
A Host may support up to eight DART cards. Each DART card provides one RF band
for up to eight Remotes. The DART card converts between serial (optical) and RF data
in both forward and reverse directions. The
all DART cards currently installed in the Host and provides an alarm summary status
indicator for each card. This page also provides a link, for each DART card, to a more
detailed page that can be used to configure the DART card and obtain alarm details
(for more information, see “Configure the Host DARTs” on page 152).
—Summary alarm state of the DART card. Red indicates a problem
with passing RF.
•
is too strong. Fault threshold is
•
—Red indicates that the RF signal received from the BTS
.
—Red indicates that the DART type doesn't match
the assigned Pass Band. Examples: After assigning the Pass Band, if the DART
is changed with another DART type, then the
occurs. Or, if you swap DART types (such as, from GSM1800 to UMTS), the
is raised as the stored database has one DART
type configured, and the new hardware doesn't match it.
•
—Yellow indicates that the power of the signal received
on the RF input to the DART is 20 dB below the optimal input level. For
example:
Host Forward
DART Gain
30 dB-25 dBm-45 dBm
20 dB-15 dBm-35 dBm
10 dB-5 dBm-25 dBm
0 dB+5 dBm-15 dBm
Maximum RMS
Input Power
UnderDrive
Threshold
33Click
to update the alarm summary. For corrective actions for alarm states,
The Remote SERF ENET page is a summary of throughput and number of errors on
the twelve Ethernet (ENET) ports on the Remote SeRF card. These ports, located on
the front side of the SeRF card, consist of eight ports used for connection to Remotes
and four ports used for system management and maintenance functions.
To open the
Tree select
view in the EMS View Frame, in the Function Explorer
.
The
•
•
•
•
•
•
—on card processor's connection to the PHY port labeled Craft
—Receive byte counter. Increments by the byte count of frames received,
—on card processor's connection to the switch on the SeRF card
—Ethernet switch interface to on-card processor
view lists the Ethernet ports and their corresponding status.
—Ethernet switch interface to SFP 1-8
—switch interface to the PHY port labeled Network
including those in bad packets, excluding preamble and SFD but including FCS
bytes
•
—Receive packet counter. Increments for each frame received packet
(including bad packets, all unicast, broadcast, and multicast packets)
•
—Receive FCS error counter. Increments for each frame received that
has an integral 64 to 1518 length and contains a frame check sequence error
—Receive broadcast packet counter. Increments for each
broadcast good frame of lengths 64 to 1518 (non VLAN) or 1522 (VLAN),
excluding multicast frames. Does not include range/length errors
•
—Receive multicast packet counter. Increments for each multicast
good frame of lengths 64 to 1518 (non VLAN) or 1522 (VLAN), excluding
broadcast frames. This count does not include range/length errors
•
—Receive fragments counter. Increments for each frame
received that is less than 64 bytes and contains an invalid FCS. This includes
integral and non-integral lengths
•
—Receive jabber counter. Increments for frames received that
exceed 1518 (non VLAN) or 1522 (VLAN) bytes and contain an invalid FCS. This
includes alignment errors
•
—Transmit byte counter. Increments by the number of bytes that
were put on the wire including fragments of frames that were involved with
collisions. This count does not include preamble/SFD or jam bytes. This counter
does not count if the frame is truncated
•
—Transmit packet counter. Increments for each transmitted packet
(including bad packets, excessive deferred packets, excessive collision packets,
late collision packets, all unicast, broadcast, and multicast packets)
•
—Transmit broadcast packet counter. Increments for each
Only a user logged in under the admin or a Network Manager account can change Prism
system settings t
Decommission a RF Module only if it has been permanently removed from the Remote
and will not be repl
This procedure is for decommissioning a Remote’s RF Modules, which contain the
Remote DARTS. For info
“Decommissioning a DART in a Host” on page 220.
hrough the EMS.
aced with another DART.
rmation on decommissioning a DART in a Host, see
The
have already been physically removed. You use the
button is available only when a RF Module and hence the DART(s)
button when an RF
Module and its DART(s) have taken out of service. This procedure removes all
information about this RF Module (such as associated alarms, links, and inventory)
from the EMS database. Entries in the Alarm History Log, however, are preserved.
11In the Function Explorer Tree, select
(where
port number and
The
indicates the Remote number that corresponds to a Host SFP
n is the Remote name).
view opens in the EMS View Frame. For a
description of the RF Groups, see “RF Groups in the Remote and the EMS GUI” on
Both LPAs in a dual-slot 40W module can be controlled from the
window, which allows you to set the
, enable/disable a LPA, or
reset a LPA, as shown below:
The following rules apply to the dual-slot LPA installation:
••For the second LPA, the GUI displays it in an RF group by itself. There will be no
DART in the RF group. However, you will be able to view alarms and configuration
for the RF group in case of dual LPA setup. For the “missing” DART, default values
will display. You cannot configure the missing DARTs, but can set the LPA mode
and reset the LPA.
••User-initiated configuration of dual LPAs is simulataneous for both the LPAs. If
one of the LPAs is placed into
mode, both go into
, both go into standby. If one is placed into
mode.
••User initiated LPA resets are simulataneous. If one LPA is reset, so is the other.
••Alarm handling for the two LPAs occurs independently. If one alarms and goes
into
, the second LPA continues in its current state. Automatic alarm
Only a user logged in under the admin or a Network Manager account can change Prism
system settings t
hrough the EMS.
You use the
button to bring an LPA back into service (restart) that stopped
because of an LPA alarm.
This section comprises a 6-step process that is broken into 2 sections that first
identifies the fault and then resets the LPA.
10.4.1Identify the LPA Fault
11In the Function Explorer Tree, select
(where
number and
indicates the Remote number that corresponds to a Host SFP port
n is the Remote name).
22In the rectangle for the RF group selected, click on the
whose LPA needs to be reset. The
window opens (where x is the DART, Group or Remote name).
link for the band
x
x
An LPA Reset is necessary when any of the alarms listed below have occurred.
•
—Red indicates that the Linear Power Amplifier is disabled
because it encountered a problem. Check for a corresponding LPA fault listed in
this section (such as
, and so forth), then correct
the LPA fault. If LPA Reset does not clear this alarm, the corresponding RF Module
may need to be replaced. Contact ADC Technical Assistance for further help (see
“Contacting ADC” on page 335).
•
—Red indicates an internal VSWR fault state of the LPA. Check the
Remote’s antenna connection. If the connection is good and a subsequent LPA
reset does not clear the alarm, inspect the blue cable going from the
corresponding Remote Antenna port to the Duplexer—verify that the connection
is tight. If this doesn't clear the fault, the Duplexer may need to be replaced. Notify
ADC Technical Support (see “Contacting ADC” on page 335).
•
—Red indicates that the voltage level inside the LPA is outside its
acceptable range. If the LPA Reset does not clear this alarm, contact ADC
Technical Assistance for further help as the RF Module that contains the LPA or
the Power supply within the SeRF Module may need to be replaced (see
“Contacting ADC” on page 335).
•
—Red indicates that the LPA is not sure of the feedback loop, so it
has placed itself into a safe state. You can attempt to recover the LPA by reducing
forward gain by 10dB on both DART cards, resetting the LPA, then restoring GAIN.
If the reset does not work, contact ADC Technical Support (see “Contacting ADC”
on page 335).
•
—Red indicates that the power level inside the LPA is high
enough to damage the LPA. Reduce the Remote Forward Gain (see “Link the Host
and Remote DARTs.” on page 159), then reset the LPA.
•
—Red indicates that the internal gain of the LPA does not meet
specifications. In addition to an LPA Reset, try putting the LPA into standby and
then back to enable to see if this clears this fault. If neither troubleshooting step
clears this alarm, the corresponding RF Module may need to be replaced. contact
ADC Technical Assistance for further help (see “Contacting ADC” on page 335).
•
LPA Missing Fault—Red indicates that the LPA is missing. This fault cannot be cleared
Once an LPA Reset is started, Loss of Service occurs. It take approximately 10 to 20
seconds before t
depending on the number of Remotes
Remotes the power reading could take sev eral minutes
he LPA signal recov ers. The GUI RF pow er reading w ill take longer
equipped—for a fully loaded Prism system with 8
to update.
33In the Function Explorer Tree, select
(where
SFP port number and
indicates the Remote number that corresponds to a Host
n is the Remote name).
44In the rectangle for the RF group selected, click on the
22If the Alarm Summary status indicator for any Remote is red or yellow, indicating
that an alarm exists for that Remote, in the Function Explorer Tree, select the node
that corresponds to that Remote. In the preceding example, you would click on
the remote node labeled
status indicator is red or yellow, you must
go another level lower in the Function Explorer Tree for this same Remote to select
the page for the SeRF or RF Groups. For more information on these displays, see
“Viewing Remote SeRF Alarms” on page 248 or “Viewing Remote SeRF Optical
Ports” on page 248.
The GPS alarm is not supported at present; this status indicator will be white.