User guide

Upstream Control Protocol (UCP) Display Viewing NTE8 Configuration Faults
AlliedView NMS Administration Guide (Configuring Network Services)
6-234
6.17.9 Viewing NTE8 Configuration Faults
When the NTE8 configuration is set up and running, faults can be generated on four components:
• NTE8 Card
• DS1/E1 port (such as LOS, LOF, Receiving AIS, etc.)
• PPP (Configuration Failure, Peer Disabled, etc.)
• MLPPP
Note: Refer to the iMAP User Guide for a complete description of these faults, and the iMAP Log Manual for a
complete list of alarms.
Trap Parsers and/or Filter are used to receive and process the iMAP PPP/MLPPP link traps into NMS Events/Alarms. (For an
overview of the Fault Management system, refer to Section 9.)
The traps are propagated as follows:
• DS1/E1 Port Alarms are generated from their corresponding Link down/up traps.
• PPP and MLPPP alarms are generated from their corresponding Link down/up traps. (Note PPPs of an MLPPP do not pro-
duce Link traps.)
• The Bandwidth Degraded alarm is generated when an interface defect trap is received from the iMAP.
• DS1/E1, PPP and MLPPP Link down/up traps are propagated to any of their associated VLANIFs and LINKs (including
VLINK symbols on VLAN maps).
• MLPPP Bandwidth Degraded traps (when a PPP of an MLPPP goes down) are propagated to any of their associated
VLANIFs and LINKs (including VLINK symbols on VLAN maps).
FIGURE 6-237 Alarms Associated with NTE Endpoints
6.18 Upstream Control Protocol (UCP) Display
UCP is a proprietary protocol that informs other devices in the network that it is the “upstream node” for a UFO VLAN. More-
over, using UCP protocol messages, the non-upstream nodes for the UFO VLAN can dynamically determine their upstream
interfaces. UCP actions occur independently of the topology feature being used; therefore, UCP can be used by itself as well as
with EPSR.
Note: For a complete explanation of UCP and how it works with various topology features, refer to the iMAP User
Guide.