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.
button—When clicked, causes page to be reloaded from Host
Monitoring a Remote Unit
Reset Unit
Decommission Unit
•
button—When clicked, causes the Remote to reboot. This causes a
Loss of Service until Remote has returned to normal operation. Typical down
time is two to four minutes. See “Resetting a Remote Unit” on page 246.
The use of the Reset Unit button causes Loss of Service and should not be used unless
other troublesh
experienced at the Remote.
•
ooting processes have been follow ed and did not fix the issue being
button—When clicked, deletes any configuration settings
for that Remote and removes all corresponding alarms from the EMS alarm
summaries (see “Decommissioning a Remote Unit” on page 244).
The Remote reboots (resets), which causes a Loss of Service until the Remote has
returned to normal operation. Typical down time is two to four minutes.
-n view in the EMS View Frame, in the Function
(where
the Remote number that corresponds to a Host SFP port number and
name).
indicates
n is the Remote
The
-n view provides an alarm summary for the SeRF card on
the identified Remote.
•
status indicator—Summary alarm status indicator for Remote optical
ports. Red indicates no light (such as the RxNolight Fault) or a laser fault.
•
status indicator—Summary alarm status indicator for Remote SeRF
card. Red indicates that an alarm exists for the Remote SeRF card.
10.9VIEWING REMOTE SERF OPTICAL PORTS
The
optical ports on the Remote, plus current values of operating parameters. The
-n view only shows the ports that are in current use (that is, they have
a fiber and connector plugged into them with the other end of the fiber being
connected to Remote).
To open the
Explorer Tree select
and
indicates the Remote number that corresponds to a Host SFP port number
n is the Remote name).
-n view shows the current usage and alarm status of the
-n view in the EMS View Frame, in the Function
(where
-n view provides an alarm summary for the SeRF card on
the identified Remote.
•
for this particular port
•
—System-assigned port number and link to the
—User-entered port name or
indicating no name
has been entered
•
—Disabled for Remotes. This parameter indicates if the link is carrying IP
traffic. It can only be set on the Host as described in “Configure the Remote SeRF
Optical Ports” on page 158.
•
—Laser range, which is
to meet 3Gbps optical transmission
requirements.
•
•
—Launch power in dB of REV path signal, from the Remote to the Host.
—Launch power in dB of receive level of the FWD path, from the Host
to the Remote. The minimum REV launch power is -27 dBm, and the maximum is
-9 dBm.
•
•
fiber. Fault threshold is
•
—Number displayed is wave length transmitted through this port
—Yellow indicates that there ware too many errors on the receiving
.
—Red indicates that no light is detected on the receiving fiber
•
•
threshold is
•
underdrive is from -28dBm to -33dBm. Fault threshold is
—Red indicates reverse path laser is not sending light
—Red indicates forward path optical signal is too strong. Fault
.
—Yellow indicates forward path optical signal is too weak. The
.
—Name of the Host at the other end of the fiber.
Managing Remote Units
Alarm Summary of RF Groups of Remote-
Remote-
Alarm Summary of RF Groups of Remote-
System View,Remotes,Remote#-x,RF Groups
Remote#
DART
LPA
10.10VIEWING AN ALARM SUMMARY OF THE REMOTE RF
ROUPS
G
The
four RF groups on a particular Remote (
To open the
the Function Explorer Tree select
n is the Remote name).
and
indicates the Remote number that corresponds to a Host SFP port number
n view provides an alarm summary for the
n).
n view in the EMS View Frame, in
(where
To understand how the EMS maps the RF Groups in the Remote to their
representation in the GUI, see “RF Groups in the Remote and the EMS GUI” on
page 160. The RF Group alarm indicators are listed below.
•
—Summary alarm state of the DART card upconverter, downconverter and
the DART FPGA. Yellow indicates that a Minor alarm is the highest-level alarm and
Red indicates that a Major alarm exists for the DART.
•
—Summary alarm state of Linear Power Amplifier (LPA), where both LPA
indicators refer to the same LPA. Yellow indicates that a Minor alarm is the
highest-level alarm and Red indicates that a Major alarm exists for the LPA.
band in the RF Groups view (upper link) to open the
n
n window.
The
n
n window has the the following
components. For corrective actions for alarm states, refer to “Troubleshooting
Alarms” on page 264.
–
—Summary alarm state of the DART card upconverter
downconverter and the DART FPGA. Red indicates that either the clock
source for the DART card is outside the acceptable range or the DART FPGA
is not programmed.
–
–
—Red indicates DART card DC supply is faulted.
—Red indicates an invalid passband
configuration for the DART.
–
temperature is too high. Fault threshold is
–
—Red indicates DART card internal
.
—Red indicates that the Host is unable to
implement the signal delay entered in the RF Band Configuration Page
(described in “Link the Host and Remote DARTs.” on page 159).
–
—Red indicates a VSWR fault at the interface to the
antenna (greater than 3:1).
–
output is too low. The threshold for this fault is
Some EMS parameter values are associated with alarms. When a parameter enters an
alarm state, an alarm status indicator is activated where the color of the indicates the
alarm severity, where:
••Red indicates a major alarm
••Yellow indicates a minor alarm
••Green indicates a normal (okay) state
••Grey indicates that the alarm has been masked
••White indicates that an associated device is unplugged or missing.
Only a user logged in under the admin or a Network Manager account can change Prism
system settings t
Masking an alarm type causes the EMS to stop reporting alarms of that type until the
alarm is unmasked. By default all alarms are unmasked. When an alarm type is
masked (mask status enabled), the following is true:
••The corresponding status indicator shows in gray.
••The alarm state is not calculated into the higher level alarm summary
••The corresponding trap is not sent to SNMP managers.
To mask an alarm:
hrough the EMS.
11To access the EMS Menu bar, in the Function Explorer Tree, click on
Table 11-1. EMS Alarm Descriptions and Corrective Actions (Cont.)
Alarm NameAlarm
Sev erity
Level
MajorSummary status of
MajorIndicates a hardware
DescriptionAction
Inspect
DART upconverter
and/or
downconverter and
DART FPGA status.
The clock source for
the DART is outside
an acceptable range
or the DART FPGA is
not programmed.
may also occur with
the
DARTDCSupplyFault.
mismatch for the
DART boards
between linked Host
and Remote
upconverter and/or
downconverter
alarms. If these
alarms are found
and persist, consult
ADC, replace DART.
If no
upconverter/downc
onverter alarms are
found, unplug DART
from Host, then
replug DART in Host
to reload the FPGA. If
persistent, consult
ADC, replace DART.
Check if a linked
DART of one type
was unplugged and
not decommissioned
then replaced with a
DART of another
type. Make sure
linked Host and
Remote DARTs are
of same type
for
Majorthe RF signal
received from BTS is
greater than +5dBm.
The allowed range is
-25 dBm to +5 dBm.
MinorWhen the Host input
level is 20 dB less
than the expected
Host DART Input. For
example, for 30 dB of
Host DART gain (-25
dBm expected input),
the threshold is -45
dBm. For 0 dB of
Host DART gain (+5
dBm expected input),
the threshold is -15
dBm.
Table 11-1. EMS Alarm Descriptions and Corrective Actions (Cont.)
Alarm NameAlarm
Sev erity
Level
MajorRemote not
DescriptionAction
There are two
receiving any
messages from
connected Host
possible actions:
•Check for optics
disconnect. Check
the optical link
and determine the
source of lost
communications.
If an optical meter
on the output of
the SFP
determines that
no power is being
transmitted, or
meter measuring
receive levels at
the SFP
determines the
receiver is broken,
replace SFP with
the appropriate
type for the range
of signal
supported.
•There may be an
IP conflict. For
example, if the
Host is configured
in External
Network mode but
there's not a DHCP
server running on
the network, the
Remote will not
receive an IP
address, there
therefore will not
be communication
with the Host,
which would
activate this
alarm.
Replace SFP with the
appropriate type for
range of signal
supported
Externally attenuate
Host forward path
signal or replace
Host SFP with one of
less strength
Managing Alarms
RmtSERFOptRxBERFault
RmtSERFOptRxNoLightFault
RmtSERFOptUnderDriveFault
RmtSERFSynthAlarmFault
RmtSystemVswrFault
RmtUnderTempFault
Table 11-1. EMS Alarm Descriptions and Corrective Actions (Cont.)
Alarm NameAlarm
Sev erity
Level
MinorToo many errors on
MajorNo light detected
MinorThe power of the
MajorOnboard
DescriptionAction
Check fiber for kink
the receiving fiber
from the receiving
fiber
signal received on
the fiber is too weak
synthesizer fault
or sharp bend. Check
for too much gain.
Make sure the fiber
is clean.
Check for broken or
disconnected fiber.
Check for out of
service Host
Check fiber for too
much gain, dirty
connectors. Check
SFP type being used
(too weak for range)
Check clock signal
coming from Host.
Host is not
generating a proper
signal. Possibly Host
clock source is bad
or Host has bad
FPGA
MajorLPA VSWR FaultPerform cable
sweeps on external
antenna cable
system. Put a load on
the Remote by
disconnecting the
external antenna
cable to determine if
the source of the
VSWR condition is
internal or external.
If it's internal,
replace the RF
Module. If it's
external,
troubleshoot and
determine source of
high VSWR reading.
SNMP (Simple Network Management Protocol) is an international standard for remote
monitoring and control of online devices. The EMS provides an interface for those
wishing to access a Prism system using an SNMP manager such as the AdventNet
application shown in Figure 12-1.
Figure 12-1. EMS SNMP Interface Example
The FlexWave EMS SNMP interface can manage FlexWave Prism and URH units. This
document describes how
The FlexWave system SNMP interface, shown schematically in Figure 12-2, allows a
remote user using an SNMP manager to access the same database as accessed by the
standard EMS interface. The database accessed is an SNMP database called a
Management Information Base (MIB).
Web
IP
GET/SETTRAP
Network port
EMS
INTERNAL
MIB
IP
Windows 2000 or Windows XP
computer running
Internet Explorer 6.0
and/or SNMP Manager
URH Host Unit
75356-05
Figure 12-2. SNMP Interface
This section describes the FlexWave system SNMP interface, and provides procedures
for using the SNMP interface to “get” and “set” system parameters and receive alarms.
In SNMP terminology, the parameters in a MIB are called “objects” and alarms are
called “traps.”
SNMP (Simple Network Management Protocol) is an international standard for remote
control of online devices. A typical scenario involves the devices being controlled,
remote computers (called managers) that can control them, a network connection,
and SNMP software. The SNMP software includes SNMP manager software on each
controlling computer and SNMP “proxy agent” software and one or more MIBs on
each of the controlled devices.
A MIB is a database defined in accordance with SNMP requirements. A MIB consists
of tables of objects used to exchange information between a manager and agent.
Information is exchanged using three basic operations: GET, SET, and TRAP. A
manager uses GET to obtain an object value from a MIB and SET to set an object to a
new value. A TRAP is a notification that is sent out by an agent when the value of a
trap object exceeds a threshold defining an alarm state.
In a manager browser, a MIB looks like an Explorer hierarchy of folders and files, as
shown in Figure 12-3. The items at the lowest level, analogous to files in the Explorer
view, are not files, however; they are objects that each represent one system
parameter (object) and its current value. MIB objects are arranged in tables. Each set
of objects (within a single folder) represents one such table. An object marked with a
key symbol indicates that view is the key value for that table.
In the FlexWave system, the MIB accessed through the SNMP interface is the same
database as used by the EMS graphical user interface. There is therefore a one-to-one
correspondence between MIB objects and the parameters displayed in the EMS Web
pages. Likewise, there is a one-to-one correspondence between the SNMP trap objects
and the alarm indicator LEDs displayed on the EMS pages. The MIB object names and
the EMS page names for the same items differ in a way that can be easily figured out.
For example, the MIB object “fwuHstDARTPassBand” corresponds to the “Host DART
Pass Band” parameter on the Host DART Configuration and Alarm Details Page.
The FlexWave system uses a single MIB called the ADC-FLEXWAVE-URH.mib. The MIB
resides on the SeRF card in the Host where the EMS software also runs. The SNMP
proxy agent software required for the interface with SNMP managers also resides and
runs on the Host SeRF card.
A complete list of the objects that compose the FlexWave-Prism Agent MIB are listed
in this section in two tables. Table 12-2 on Page 292 lists objects that may be accessed
for GET/SET operation. Table 12-3 on page 308 lists traps that are sent to SNMP
managers registered to receive them whenever the respective fault condition occurs.
This topic contains procedures done at the SNMP manager to interact with the
FlexWave-Prism Agent MIB. Any SNMP manager may be used. These procedures are
illustrated with examples from an AdventNet MIB Browser.
Figure 12-4 shows the features of a typical MIB browser.
Figure 12-4. Typical MIB Browser
Examples show n in this chapter use the AdventNet MIB Browser. Some procedural
details may vary with a
The FlexWave-Prism Agent MIB can be accessed using any SNMP manager with an
active network connection. The IP address of the FlexWave-Prism Host must be
known and entered in the MIB browser.
11On the manager computer, open the MIB Browser.
22Load the ADC-FLEXWAVE-URH.mib file.
33Enter the IP address of the Host of the FlexWave-Prism system in the text box
provided next to
.
44Enter the
as 8001.
55Enter the Read Community as public and Write Community as private.
66To see an overview the MIB content, expand the MIB tree.
To receive traps using the manager, you must first register the manager using the
procedure in “Registering the Manager for Receiving Traps (static—non AdventNet MIB
Browser)” on page 283 o
(dynamic—AdventNet MIB Browser)” on page 284.
The
r in “Registering the Manager for Receiving Traps
dialog opens.
icon on the Toolbar.
22In the
33(Optional) In the
traps. The default is
44Click the
the
The Port and Community list can be deleted by clicking the Delete Entry button.
55Click the
66Click the
box, enter the desired port number. The default is
button to add the
box, enter the community string for the incoming
.
and
list to the
list box).
button to load the trap parser file.
button. Trap Viewer begins to receive traps from the specified port
—defines the type of the trap or the inform request.
—represents the IP address of the source from where the traps were
sent.
•
•
—shows the date and time when the trap was received.
—lists the VarBind list of the trap, if any.
The status of the trap is displayed in the status pane at the bottom of the dialog
box. Moreover, the Trap count and the inform count is displayed in the status
pane.
77To log the received traps, select the
traps are logged to a file. The default name of the log file is
88To view the details of the traps, click on the
right-click the trap in the trap table and select
99Click
to stop listening to the port.
100 To delete a trap, select the trap and click the
right-click the trap in the trap table and select
check box. All the incoming
button. You can also
button. You can also
.
.
.
Another option in
is the
can filter the incoming
traps according to certain criterion called the Parser Criteria. The configuration of
the criterion is made possible by using the
Objects in the FlexWave-URH Agent MIB divide into two types:
trap objects. This section describes the
objects. For information on trap
objects and
objects, see “Traps” on page 308.
Table 12-2 lists all objects within the FlexWave-URH Agent MIB that are available for
GET and/or SET commands. Objects that are available for SET commands are also
available for GET commands.
For each SNMP syntax, there is a range of values defined in the MIB file. These are the
possible values that can be entered in a SET command and returned in a GET
command.
You can also
(
) or not (
or
masking, which sets whether the trap will be raised
). Thresholds dictate when a trap will be activated. Table 12-2
lists all FlexWave-URH Agent MIB objects for which traps, masks and thresholds are
sent to the SNMP manager.
Diversity Status of Remote
DART card, where diversity is
1 and no diversity is 0
Primary Gain in forward path
of Remote DART card
Primary Gain in reverse path
of Remote DART card
Forward Delay for Remote
DART card Micro Seconds
(from 1 to 500). If the Forward
Delay value is not equal to
Actual Forward Delay value
then, then a Ranging fault will
be raised if the Remote DART
is Linked
Reverse Delay for Remote
DART card Micro Seconds
(from 1 to 500). If the Reverse
Delay value is not equal to the
Actual Reverse Delay value
then, then a Ranging fault will
be raised if the Remote DART
is linked
ID of DART at Host to which
the Remote DART is to be
connected (from 1 to 8)
ID of host side SFP ID
connected toward the remote
DART. (from 1 to 8)
Pass-band type of Host DART
card
ID of the Remote from which
DART is to be connected
ID of Remote DART to which
the Host DART will connect
(from 1 to 8)
ID of Remote side SFP ID
connected toward the Host
DART (from 1 to 8)
INTEGERGET
INTEGERSET
INTEGERSET
PASSBANDTypeGET
REMOTENBRT
ype
INTEGERSET
INTEGERSET
or
SET
SET
Remote side Band-PassBand
information of the linked
darts
Start timeslot on the fiber
that is carrying the DART
traffic. This is a read-write
object but it is not available
for user to do a RW operation.
End timeslot on the fiber that
is carrying the RF traffic from
Host to Remote DART card.
This is a Read-Write object,
but is not available for user
as a Read-Write operation.
Status of rowRowStatusSET
Provides a way to reset the
Remote SeRF card. Set to 1 to
trigger a Remote reset