When the last scan and baseline configurations differ, the last scan details are displayed on the graph. Choose Base Scan in the drop-down list to view the baseline scan.

Fast scan trace is displayed to the user for quick reference before the composite trace. It is displayed at the end of OTDR training operation and before start of the composite trace. A progress bar is provided to the user for each scan in the sector that displays the percentage of execution of the entire scan operation.

In R10.8, auto sector is substituted with the composite trace. The composite trace is stitched through scans executed on legacy zones (1km, 25km, 80km, 100km). The composite trace is provided only when OTDR training is successfully executed. When you start a fast scan on the RX port, an OTDR-FAST-SCAN-IN-PROGRESS-RX alarm is raised. When you start a fast scan on the TX port, an OTDR-FAST-SCAN-IN-PROGRESS-TX alarm is raised. The fast scan shuts down the OSC channel.

When you start a Hybrid scan on the RX port, an OTDR-HYBRID-SCAN-IN-PROGRESS-RX condition is raised. When you start a Hybrid scan on the TX port, an OTDR-HYBRID-SCAN-IN-PROGRESS-TX condition is raised. Hybrid scan does not shut down the OSC channel and takes longer time to complete.

In case of EDRA, When you start a Fast scan on the RX port, an OTDR-FAST-SCAN-IN-PROGRESS-TX alarm is raised. When you start Fast scan on the TX port, an OTDR-FAST-SCAN-IN-PROGRESS-RX alarm is raised. Fast scan shuts down the OSC channel. When you start a Hybrid scan on the RX port, an OTDR-HYBRID-SCAN-IN-PROGRESS-TX alarm is raised. When you start a Hybrid scan on the TX port, an OTDR-HYBRID-SCAN-IN-PROGRESS-RX alarm is raised. Hybrid scan does not shut down the OSC channel and takes longer time to complete.

Any ongoing scan operation can be stopped by clicking Cancel.

When the scan is completed, click OK in the Scan Completed dialog box. The OTDR scan results are displayed in the graph having Distance (km or mile) on the x-axis and Loss (dB) on the y-axis. To zoom in or zoom out of a graph, see DLP-G785 Zoom In/Out with Graphs.

The baseline scan is indicated by blue color and the last scan is indicated by red color on the graph. When a baseline scan is set, you can compare the last scan result with the baseline scan values in the graph.

When the event scan is completed, the OTDR event scan result is displayed on the graph. The value in the Sector drop-down list changes to Event Scan Result. To zoom in or zoom out of a graph, see DLP-G785 Zoom In/Out with Graphs.

Scan on event executes an Expert Scan with a specific set of parameters defined for any kind of fiber plant. Since the set of parameters computed doesn’t take into account the specific characteristics of the fiber plant, it’s possible that the event under analysis isn’t found and reported in the event table associated to the scan on the event panel even if the graph is correctly reported. To overcome the issue, follow this procedure:

OTDR identifies EOF as a fiber termination event along with the reflection or loss event. EOF is checked along the life of the fiber plant to check for possible changes to fiber length. If the fiber length is higher than 20dB or 100 km, it’s not guaranteed to find the EOF.

There are default values set in the table for both the RI and BS parameters. The value for RI is 1.4986 and BS is -82. To configure and define the fiber, the values of parameters in the table can be changed. There is a defined range of values that can be entered in both the RI and BS columns. The value range for RI is from 1 to 2, and for BS is 0 to -100.

Click Reset to reset values to default.

• Press and hold the Shift Key on your keyboard.

• Click the mouse cursor anywhere on the graph and draw a box at that point.

• Right click the mouse cursor on a point on the graph and move to the desired view.

The APC Discovery dialog box appears with the discovered APC domains. It may take 10-15 seconds for all the domains to appear. Each discovered domain will be identified as "Discovered: Domain" followed by "node name side, node name side". If APC could not be discovered on a node, a triangle with an exclamation point appears next to the node. If this occurs, double-click the node to display the reason. If you want to save the APC discovery results to a text file, complete the following sub-steps. Otherwise, continue with Step 4.

Only domains with a status, APC State: Enabled, can be disabled.

The APC Discovery dialog box appears with the discovered APC domains. It may take 10-15 seconds for all the domains to appear. Each discovered domain will be identified as "Discovered: Domain" followed by "node name side, node name side". If APC could not be discovered on a node, a triangle with an exclamation point appears next to the node. If this occurs, double-click the node to display the reason. If you want to save the APC discovery results to a text file, complete the following sub-steps. Otherwise, continue with Step 4.

The APC Discovery dialog box appears with the discovered APC domains. It may take 10-15 seconds for all the domains to appear. Each discovered domain will be identified as "Discovered: Domain" followed by "node name side, node name side". If APC could not be discovered on a node, a triangle with an exclamation point appears next to the node. If this occurs, double-click the node to display the reason. If you want to save the APC discovery results to a text file, complete the following sub-steps. Otherwise, continue with Step 4.

• Position—The node, side, and slot.

• Last Modification-—The last time a modification to the APC parameters occurred, in Date-Hour-Time Zone format. APC parameters are reported only when their ports are in IS-NR/Unlocked-enabled service state.

• Parameter—The parameter that was last modified. Parameters can include:

  • Gain and optical power setpoints on the LINE-TX ports of the OPT-BST, OPT-BST-L, OPT-BST-E, OPT-AMP-L, OPT-AMP-17-C, OPT-AMP-C, OPT-EDFA-17,OPT-EDFA-24, and OPT-EDFA-35 cards.

  • Gain and optical power setpoints on the COM-TX port of the OPT-PRE card.

  • Gain setpoints on the DC-TX ports of the OPT-RAMP-C and OPT-RAMP-CE cards.

  • VOA target attenuation on the DC-TX ports of the OPT-RAMP-C and OPT-RAMP-CE cards.

  • VOA target attenuation on the COM-RX ports of 32DMX, 32DMX-O, 32DMX-L, and 40-DMX-C/40-DMX-CE cards.

  • VOA target attenuation on the COM-RX ports of 32DMX, 32DMX-O, 32DMX-L, and 40-DMX-C/40-DMX-CE cards.

  • VOA target attenuation on the W-RX and P-RX ports of the PSM card.

• Last Check—The date and time the APC parameters were last monitored, in Date-Hour-Time Zone format. APC parameters are reported only when their ports are in IS-NR/Unlocked-enabled service state.

• Side—The letter of the side, A through H.

  Note	If you have created a side for the PSM card, the Side field will display both the working (w) and the protected (p) side.

• APC State-Displays the APC state:

  • Enabled—APC is enabled.

  • Disabled—User-APC was disabled by a user action.

  • Disabled Internal—APC was disabled by an internal action.

  • Not Applicable—APC parameters are not reported, for example, does not apply to the side, for example, no amplifiers are installed.

• Domain—Optically identifies a set of nodes that can be independently regulated by the same instance of APC at the network level. Every domain is terminated by two node sides residing on a terminal node, ROADM node, hub node, line termination meshed node, or an XC termination meshed node.

• APC State—Displays the APC state:

  • Enabled—APC is enabled.

  • Disabled—User-APC was disabled by a user action.

  • Disabled—Internal-APC was disabled by an internal action.

  • Not Applicable—APC parameters are not normally reported, for example, a gain set point when working mode is set to Control Power.

• Admin State—Displays the admin state of the APC engine:

  • Free to run

  • APC Disabled

  • APC Disabled Internal

• Progress State—Indicates the APC engine state:

  • APC Running

  • APC Aborted

  • APC Run Completed

• Run APC—Runs the APC function manually for the selected domain. To run APC on multiple domains, press CTRL and select the desired domains, before clicking Run APC.

• General: Node Name

• General: Contact

• Location: Latitude

• Location: Longitude

• Location: Description

• Time: Use NTP/SNTP Server

• Time: NTP/SNTP Server IP Address (if Use NTP/SNTP Server is checked)

• Time: Date (M/D/Y)

• Time: Time (H:M:S)

• Time: Time Zone

• Time: Use Daylight Saving Time

• S-V Insertion On STS-1 Signal Degrade - Path: Insert AIS-V on STS-1 SD-P

• AIS-V Insertion On STS-1 Signal Degrade - Path: SD-P BER

See the "NTP-G24 Set Up Name, Date, Time, and Contact Information" procedure in the chapter "Turn Up a Node" in the Cisco ONS 15454 DWDM Configuration Guide for detailed field descriptions.

• TARP PDUs L1 Propagation—If checked (default), TARP Type 1 PDUs that are received by the node and are not excluded by the LDB are propagated to other NEs within the Level 1 OSI area. (Type 1 PDUs request a protocol address that matches a target identifier [TID] within a Level 1 routing area.) The propagation does not occur if the NE is the target of the Type 1 PDU, and PDUs are not propagated to the NE from which the PDU was received

  Note	The TARP PDUs L1 Propagation parameter is not used when the Node Routing Area (Provisioning > OSI > Main Setup tab) is set to End System.

• TARP PDUs L2 Propagation—If checked (default), TARP Type 2 PDUs received by the node that are not excluded by the LDB are propagated to other NEs within the Level 2 OSI areas. (Type 2 PDUs request a protocol address that matches a TID within a Level 2 routing area.) The propagation does not occur if the NE is the target of the Type 2 PDU, and PDUs are not propagated to the NE from which the PDU was received.

  Note	The TARP PDUs L2 Propagation parameter is only used when the Node Routing Area is provisioned to Intermediate System Level 1/Level 2

• TARP PDUs Origination—If checked (default), the node performs all TARP origination functions including:

  • TID to Network Service Access Point (NSAP) resolution requests (originate TARP Type 1 and Type 2 PDUs)

  • NSAP to TID requests (originate Type 5 PDUs)

  • TARP address changes (originate Type 4 PDUs)

  Note	TARP Echo and NSAP to TID are not supported.

• TARP Data Cache—If checked (default), the node maintains a TARP data cache (TDC). The TDC is a database of TID-to-NSAP pairs created from TARP Type 3 PDUs that are received by the node and modified by TARP Type 4 PDUs (TID-to-NSAP updates or corrections). TARP 3 PDUs are responses to Type 1 and Type 2 PDUs. The TDC can also be populated with static entries entered on the TARP > Static TDC tab.

  Note	This parameter is only used when the TARP PDUs Origination parameter is enabled.

• L2 TARP Data Cache—If checked (default), the TIDs and NSAPs of NEs originating Type 2 requests are added to the TDC before the node propagates the requests to other NEs.

  Note	The L2 TARP Data Cache parameter is designed for Intermediate System Level 1/Level 2 nodes that are connected to other Intermediate System Level 1/Level 2 nodes. Enabling the parameter for Intermediate System Level 1 nodes is not recommended.

• LDB—If checked (default), enables the TARP loop detection buffer. The LDB prevents TARP PDUs from being sent more than once on the same subnet.

  Note	The LDB parameter is not used if the Node Routing Mode is provisioned to End System or if the TARP PDUs L1 Propagation parameter is not enabled.

• LAN TARP Storm Suppression—If checked (default), enables TARP storm suppression. This function prevents redundant TARP PDUs from being unnecessarily propagated across the LAN network.

• Send Type 4 PDU on Startup—If checked, a TARP Type 4 PDU is originated during the initial ONS 15454 startup. Type 4 PDUs indicate that a TID or NSAP change has occurred at the NE. (The default setting is not enabled.)

• Type 4 PDU Delay—Sets the amount of time that will pass before the Type 4 PDU is generated when Send Type 4 PDU on Startup is enabled. 60 seconds is the default. The range is 0 to 255 seconds.

  Note	The Send Type 4 PDU on Startup and Type 4 PDU Delay parameters are not used if the TARP PDUs Origination parameter is not enabled.

• LDB Entry—Sets the TARP loop detection buffer timer. The LDB buffer time is assigned to each LDB entry for which the TARP sequence number (tar-seq) is zero. The default is 5 minutes. The range is 1 to 10 minutes.

• LDB Flush—Sets the frequency period for flushing the LDB. The default is 5 minutes. The range is 0 to 1440 minutes.

• T1—Sets the amount of time to wait for a response to a Type 1 PDU. Type 1 PDUs seek a specific NE TID within an OSI Level 1 area. The default is 15 seconds. The range is 0 to 3600 seconds.

• T2—Sets the amount of time to wait for a response to a Type 2 PDU. TARP Type 2 PDUs seek a specific NE TID value within OSI Level 1 and Level 2 areas. The default is 25 seconds. The range is 0 to 3600 seconds.

• T3—Sets the amount of time to wait for an address resolution request. The default is 40 seconds. The range is 0 to 3600 seconds.

• T4—Sets the amount of time to wait for an error recovery. This timer begins after the T2 timer expires without finding the requested NE TID. The default is 20 seconds. The range is 0 to 3600 seconds.

• Level-Sets the TARP Type Code that will be sent:

  • Level 1—Indicates that the adjacency is within the same area as the current node. The entry generates Type 1 PDUs.

  • Level 2—Indicates that the adjacency is in a different area from the current node. The entry generates Type 2 PDUs.

• NSAP—Enter the OSI NSAP address in the NSAP field or, if preferred, click Use Mask and enter the address in the Masked NSAP Entry dialog box.

• All L1/L2 virtual routers on the NE must reside in the same area. This means that all neighboring virtual routers must have at least one common area address.

• For OSI L1/L2 to ES routing mode changes, only one L1/L2 virtual router and no more than one subnet can be configured.

• For OSI L1 to ES routing mode changes, only one L1 virtual router and no more than one subnet can be configured.

• End System—The ONS 15454 performs OSI IS functions. It communicates with IS and ES nodes that reside within its OSI area. It depends upon an IS L1/L2 node to communicate with IS and ES nodes that reside outside its OSI area.

• Intermediate System Level 1—The ONS 15454 performs IS functions. It communicates with IS and ES nodes that reside within its OSI area. It does not communicate with IS nodes that reside in other OSI areas except through an IS L1/L2 node residing in its own area

• Intermediate System Level 1/Level 2—The ONS 15454 performs IS functions. It communicates with IS and ES nodes that reside within its OSI area. It also communicates with IS L1/L2 nodes that reside in other OSI areas. Before choosing this option, verify the following:

  • The node is connected to another IS Level 1/Level 2 node that resides in a different OSI area.

  • The node is connected to all nodes within its area that are provisioned as IS L1/L2.

• L1 LSP Buffer Size—Adjusts the Level 1 link state PDU buffer size.

• L2 LSP Buffer Size—Adjusts the Level 2 link state PDU buffer size.

• ESH—The End System Hello (ESH) PDU propagation frequency. An end system NE transmits ESHs to inform other ESs and ISs about the NSAPs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

• ISH—The Intermediate System Hello (ISH) PDU propagation frequency. An intermediate system NE sends ISHs to other ESs and ISs to inform them about the NEs it serves. The default is 10 seconds. The range is 10 to 1000 seconds.

• IIH—The Intermediate System to Intermediate System Hello (IIH) PDU propagation frequency. The IS-IS Hello PDUs establish and maintain adjacencies between ISs. The default is 3 seconds. The range is 1 to 600 seconds .

• Tunnel Type-Edit the tunnel type:

  • Cisco—Creates the proprietary Cisco IP tunnel. Cisco IP tunnels add the CLNS header to the IP packets.

  • GRE—Creates a generic routing encapsulation (GRE). GRE tunnels add the CLNS header and a GRE header to the IP packets.

    The Cisco proprietary tunnel is slightly more efficient than the GRE tunnel because it does not add the GRE header to each IP packet. The two tunnel types are not compatible. Most Cisco routers support the Cisco IP tunnel, while only a few support both GRE and Cisco IP tunnels. You generally should create Cisco IP tunnels if you are tunneling between two Cisco routers or between a Cisco router and an ONS node.

    Caution

    Always verify that the IP-over-CLNS tunnel type you choose is supported by the equipment at the other end of the tunnel.

• IP Address—Enter the IP address of the IP-over-CLNS tunnel destination.

• IP Mask—Enter the IP address subnet mask of the IP-over-CLNS destination.

• OSPF Metric—Enter the Open Shortest Path First (OSPF) metric for sending packets across the IP-over-CLNS tunnel. The OSPF metric, or cost, is used by OSPF routers to calculate the shortest path. The default is 110. Normally, it is not changed unless you are creating multiple tunnel routes and want to prioritize routing by assigning different metrics.

• NSAP Address—Enter the destination NE or OSI router NSAP address.

• IP Address

• Net/Subnet Mask Length

• Default Router

• IPv6 Configuration

• LCD Setting

• Suppress CTC IP Display

• Forward DHCP Request To

Gateway Settings

• Enable SOCKS proxy on Port. If enabled, one of the following:

  • External Network Element

  • Gateway Network Element

  • SOCK Proxy only

See the "DLP-G56 Provision IP Settings" task in the chapter "Turn Up a Node" of the Cisco ONS 15454 DWDM Configuration Guide for detailed field descriptions.

If you changed a network field that will cause the node to reboot, such as the IP address, or subnet mask, the Change Network Configuration confirmation dialog box appears. If you changed a gateway setting, a confirmation appropriate to the gateway field appears.

If you changed an IP address, subnet mask length, TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards reboot, one at a time. A TCC2/TCC2P/TCC3/TNC/TNCE/TSC/TSCE card reboot causes a temporary loss of connectivity to the node, but traffic is unaffected.

• IP Address

• Subnet Mask

• Default Router

• LCD IP Setting—Choose one of the following:

  • Allow Configuration—Displays the backplane IP address on the LCD and allows it to be changed using the LCD buttons.

  • Display only—Displays the backplane IP address on the LCD but does not allow it to be changed using the LCD buttons.

  • Suppress Display—Suppresses the display of the IP address on the LCD.

• Suppress CTC IP Address—If checked, suppresses the IP address from display on the Data Comm subtab, CTC node view or multishelf view information area, and other locations.

• IPv6 Configuration—Allows provisioning of IPv6 addresses. After you provision an IPv6 address, you can access the device using the IPv6 address. Configure these settings only if you want to enable IPv6 on the node. IPv6 cannot be configured using the LCD push buttons.

• Enable IPv6—Select this check box to assign an IPv6 address to the node. The IPv6 Address, Prefix Length, and IPv6 Default Router fields are enabled only if this check box is selected. The check box is disabled by default.

  Note	The Enable SOCKS Proxy on Port check box is enabled when you enable IPv6 and can be disabled only when IPv6 is disabled.

• IPv6 Address—Enter the IPv6 address that you want to assign to the node. This IP address is the global unicast IPv6 address. This field is disabled if the Enable IPv6 check box is not selected.

• Prefix Length-Enter the prefix length of the IPv6 address. This field is disabled if the Enable IPv6 check box is not selected.

• IP6 Default Router—Enter the IPv6 address of the default router of the IPv6 NE. This is optional. This field is disabled if the Enable IPv6 check box is not selected.

  Note	ONS platforms use NAT-PT internally to support native IPv6. NAT-PT uses the IPv4 address range 128.x.x.x for packet translation. Do not use this address range when you enable the IPv6 feature.

If you changed the IP address, subnet mask, or default router, the node will reboot. This will take 5 to 10 minutes.

• Backplane Ethernet Port—Assigns the backplane IP address as the node IP address.

• TCC Ethernet Port—Assigns the TCC2P/TCC3/TNC/TNCE/TSC/TSCE port IP address as the node IP address.

• New IP Address—Allows you to define a new IP address. If you choose this option, enter the new IP address, subnet mask, and default router IP address.

• External Network Element (ENE)—If selected, SOCKS proxy will be disabled by default, and the CTC computer is only visible to the ONS 15454 where the CTC computer is connected. The computer is not visible to the secure mode data communications channel (DCC)-connected nodes. Firewall is enabled, which means that the node prevents IP traffic from being routed between the DCC and the LAN port.

• Gateway Network Element (GNE)—If selected, the CTC computer is visible to other DCC-connected nodes and SOCKS proxy remains enabled. However, the node prevents IP traffic from being routed between the DCC and the LAN port.

• Proxy-only—If selected, the ONS 15454 responds to CTC requests with a list of DCC-connected nodes within the firewall for which the node serves as a proxy. The CTC computer is visible to other DCC-connected nodes. The node does not prevent traffic from being routed between the DCC and LAN port.

Within the next 30 to 40 seconds, the TCC2P/TCC3/TNC/TNCE/TSC/TSCE cards reboot. CTC switches to network view, and the CTC Alerts dialog box appears. In network view, the node changes to gray and a DISCONNECTED condition appears.

• Mask

• Next Hop

• Cost

See the "DLP-G58 Create a Static Route" task in the chapter, "Turn Up a Node" of the Cisco ONS 15454 DWDM Configuration Guide for detailed field descriptions.

You might have to scroll down on the list to find "network."

The Preferences Management area field lists all dialog boxes where "Do not show this message again" is enabled.

• Don't Show Any—Hides all do-not-display check boxes.

• Show All—Overrides do-not-display check box selections and displays all dialog boxes.

• All—Displays both TDM and DWDM nodes.

• DM—Displays only ONS 15454s with SONET or SDH cards including the transponder (TXP) and muxponder (MSP) cards.

• DWDM—Displays only ONS 15454s with DWDM cards, including the TXP and MXP cards.

• To toggle between the links, go to Step 3.

• To consolidate all the links on the network map, go to Step 4.

• To consolidate a link or links between two nodes, go to Step 5.

• To view information about a consolidated link, go to Step 6.

• To access an individual link within a consolidated link, go to Step 7.

• To expand consolidated links, go to Step 8.

• To filter the links by class, go to Step 9.

The links consolidate by class. For example, if you select a DCC link for consolidation only the DCC links will consolidate, leaving any other link classes expanded.

The following figure shows the network view with unconsolidated DCC and PPC links.

The following figure shows a network view with globally consolidated links.

The following figure shows a network view with local DCC link consolidation between two nodes.

• Name—Type the changes to the protection group name. The name can have up to 32 alphanumeric characters.

• Revertive—Check this box if you want traffic to revert to the working card after failure conditions stay corrected for the amount of time chosen from the Reversion Time list. Uncheck this box if you do not want traffic to revert.

• Reversion time—If the Revertive check box is selected, choose the reversion time from the Reversion time drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. This is the amount of time that will elapse before the traffic reverts to the working card. Traffic can revert when conditions causing the switch are cleared.

• Name—Type the changes to the protection group name. The name can have up to 32 alphanumeric characters.

• Revertive—Check this box if you want traffic to revert to the working card after failure conditions stay corrected for the amount of time chosen from the Reversion Time list. Uncheck this box if you do not want traffic to revert.

  Note

  The reversion pulse width is configurable in the card view > Provisioning > Reversion tab in CTC only if the protection is revertive. This is applicable only to PSM cards. The reversion pulse width is calculated using the following formula : Minimum reversion pulse width= ROADM delay + 10 seconds ROADM delay = N x 5 x 2 Where N = number of filter cards in the network between the source and destination PSM nodes on the working path. 5= maximum startup delay in seconds 2= bidirectional communication

• Reversion time—If the Revertive check box is selected, choose the reversion time from the Reversion time drop-down list. The range is 0.5 to 12.0 minutes. The default is 5.0 minutes. This is the amount of time that will elapse before the traffic reverts to the working card. Traffic can revert when conditions causing the switch are cleared.

If conditions permit, the Manual switch will be applied. To clear the Manual switch, see the DLP-G180 Clear a Manual or Force Y-Cable or Splitter Protection Switch.

The Force switch will be applied. To clear the Force switch, see the DLP-G180 Clear a Manual or Force Y-Cable or Splitter Protection Switch.

The Manual or Force protection switch is cleared.

The lock-on has been applied. Traffic cannot switch to the protect card. To clear the lock-on, see the DLP-G183 Clear a Lock-On or Lockout.

The lockout has been applied. Traffic cannot switch to the protect card. To clear the lockout, see the DLP-G183 Clear a Lock-On or Lockout.

The lock-on or lockout is cleared.

• GCC (both ANSI and ETSI)

• DCC

  • SDCC and LDCC (for ANSI)

  • RS-DCC and MS-DCC (for ETSI)

• GCC Rate—(Display only) Indicates the communication channel rate.

• Disable OSPF on Link—If checked, OSPF is disabled on the link. OSPF should be disabled only when the slot and port connect to third-party equipment that does not support OSPF.

• Far End is Foreign—Check this box to specify that the DCC/GCC termination is a non-ONS node

• Far end IP—If you checked the Far End is Foreign check box, type the IP address of the far-end node or leave the 0.0.0.0 default. An IP address of 0.0.0.0 means that any address can be used by the far end.

• GCC (both ANSI and ETSI)

• DCC

  • SDCC and LDCC (for ANSI)

  • RS-DCC and MS-DCC (for ETSI)

• GCC-EOC for GCC termination

• EOC for SDCC termination

• EOC-L for LDCC termination

Until all network OSC terminations are deleted, loss of signal (LOS) or power failure alarms might appear on the OPT-BST amplifier, OSCM card, and OSC-CSM card.