Configuration Guide for Cisco Optical Site Manager, IOS XR Release 24.3.x
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the tasks related to node configuration in Cisco Optical Site Manager.
If Cisco Optical Site Manager is used to manage an XR device, any configuration changes made to the device using XR (CLI or
NETCONF) will trigger a resynchronization of the device in Cisco Optical Site Manager. This means that Cisco Optical Site
Manager will temporarily be out of sync with the device while it updates itself with the changes. Any alarms during this period
will be reported on Cisco Optical Site Manager after the synchronization process is complete.
Note
Removing any line card from the XR device will cause the configuration of the card to revert to the preconfigure state. This
will result in the same behavior described above.
Figure 1. Configure the Node
Import a Cisco Optical Network Planner configuration file
Use this task to import a Cisco Optical Network Planner NETCONF file (.xml) into Cisco Optical Site Manager to configure device
parameters automatically.
If you have a NETCONF file (.xml) exported from Cisco Optical Network Planner, you can import it to Cisco Optical Site Manager.
This file includes node, shelf, card type, port (including wavelength), Pluggable Port Module (PPM), OTN, and FEC parameters.
Only values present in XML format appear as the configuration file parameters. If the values are not in XML format, the corresponding
column appears blank. Imported values are reported independently and do not affect future configuration changes.
Before you begin
Ensure that:
The NETCONF file (.xml) contains these parameters available on Cisco Optical Site Manager:
Navigate to the location where the NETCONF file (.xml) is present and select it.
Click Yes.
Click Upload.
A confirmation message appears after the upload is complete.
Step 4
(Optional) Click the Download Node Configuration as XML button, to export the XML file.
Step 5
Create an authorization group for the device added through the imported XML. For details, see Manage authorization groups
Step 6
Edit the device details:
Click Devices in the left panel.
In the Devices tab, click the Devices section to expand it.
Select the device and update its IP Address and Auth Group.
Click Apply.
Wait until Sync Status shows sync-completed, and alarm-synchronized.
Optical Degrees
From a topological point of view, all the units that are equipped in a node belong to a side. A side can be identified by
a letter, or by the ports that are physically connected to the spans. A node can be connected to a maximum of 20 different
spans. Each side identifies one of the spans to which the node is connected.
Manage Optical Degrees
Use this task to create, view, modify, or delete optical degrees in the node.
Click the Optical Configuration tab and then click Optical Degrees to expand it.
Step 3
Perform these steps, as needed.
To create an optical degree, perform these steps:
Click the + button.
The Create Optical Degree dialog box appears.
Select the Degree, Line In, and Line Out, values from their respective drop-down lists.
(Optional) Enter a description in the Description field.
Click Apply.
To modify any one of the optical degree parameters described below degree, perform the following step as needed:
To modify the span validation of an optical degree, select a value from the drop-down list in the Span Validation column and click Apply.
Go to the related cell in the Channel Spacing column, select 50 or 100 from the drop-down list, and click Apply
Go to the related cell in the Spectrum Occupancy column, enter a valid value, and click Apply.
To delete an optical degree, perform these steps:
Check the check box corresponding to the optical degree you want to delete.
Click the - button to delete the selected optical degree.
A confirmation message appears.
Click Yes.
The optical degree is deleted from the table.
Step 4
(Optional) Click the Export to Excel button to export the information to an Excel sheet.
Note
You can only create a maximum of 20 optical degrees. The optical degree is created and added to the table that displays the
following information.
Degree—Specifies the optical span of the side.
Description—Specifies the description as entered while creating the optical degree.
Line In—Specifies line in settings.
Line Out—Specifies line out settings.
Connected-to (IP/Degree)—Specifies the IP address and the optical degree of the remote Cisco Optical Site Manager instance that is connected on the
other side of the span.
Span Validation—Specifies whether the span can be used by the GMPLS algorithm for channel routing and validation. Values are True or False.
Channel Grid—Specifies the type of grid. Values are Flexible-Grid or Fixed-Grid.
Channel Spacing—Specifies the minimum frequency spacing between two adjacent channels in the optical grid. Values are 100 or 50 GHz.
Spectrum Occupancy—Specifies a percentage of the spectral density (the ratio of the C-band used by the carrier versus the total bandwidth).
The valid range is 50% to 91%.
Domain Type—Specifies the algorithm that is active on the span. By default, LOGO is displayed.
Internal Patch Cords
Virtual links can be created between network termination points using Internal Patch Cords (IPC). These termination points
include OSC ports, transponder or muxponder trunk ports, line ports, and passive device ports.
Create Internal Patch Cords
Use this task to create, modify, view, or delete internal patch cords in the node.
Click the Optical Configuration tab and then click Internal Patch Cords to expand it.
Step 3
Click the + button.
The Create Internal Patch Cord dialog box appears. It displays the From and To columns indicating the two termination points.
Step 4
Perform the following steps for the From and To columns:
Select the patch cord type from the Type drop-down lists. of the patch cord from the From and To drop-down lists.
Available options are Chassis, Passive Chassis, and Passive Unit.
The UID drop-down is displayed.
Select the unique ID of the device from the UID drop-down list
The Port drop-down is displayed.
Select Bidirectional or Mpo check box for the From column.
If you want to make the patch cord bidirectional, select the Bi-directional check box.
Select the slot from the Slot type drop-down list for the To column.
If the selected UID in the previous step is a Passive Unit, the Slot field is not displayed.
Click the Add button to add the selected Internal Patch Cord options to the Adding list.
(Optional) the Reset button to remove all the added Internal Patch Cords from the Adding list.
Step 5
Click Apply.
The internal patch cord is created and added to the table that displays the following information:
From—Specifies the location from where the connection originates.
To—Specifies the location where the connection terminates.
Type—Specifies the type of internal patch cord. Possible values are Transport and Add-Drop.
Step 6
(Optional) Select the check boxes corresponding to the internal patch cords you want to delete and click the - button.
Step 7
(Optional) Click the Export to Excel button to export the information to an Excel sheet.
Tip
You can view the internal patch cords and detailed information about cards and ports from the Map and Detailed views.
Automatic Power Control
The Automatic Power Control (APC) feature performs the following functions:
Maintains constant per-channel power increases optical network resilience, even when changes to the number of channels occur.
Compensates for the degradation of optical networks caused by aging effects.
Simplifies installation and upgrades of DWDM optical networks by automatically calculating amplifier setpoints.
The amplifier software uses a control gain loop to keep channel power constant regardless of the number of channels. It monitors
input power changes and adjusts output power proportionately. The shelf controller software emulates the control output power
loop to compensate for fiber degradation.
For proper functioning, the control card needs to know the channel distribution via a signaling protocol, and the expected
per-channel power which you can set. It compares actual amplifier output power with expected power and adjusts setpoints if
needed.
APC at the Shelf Controller Layer
Amplifiers are managed through software to monitor
changes in the input power. Changes in the network characteristics have an impact on
the amplifier input power. Changes in the input power are compensated for by only
modifying the original calculated gain, because input power changes imply changes in
the span loss. As a consequence, the gain to span loss established at the amplifier
start-up is no longer satisfied, as shown in the following figure.
Figure 3. Using Amplifier Gain
Adjustment to Compensate for System Degradation
In the preceding figure, Node 1 and Node 2 are equipped with booster amplifiers and
preamplifiers. The input power received at the preamplifier on Node 2 (Pin2) depends
on the total power launched by the booster amplifier on Node1, Pout1(n) (where n is
the number of channels), and the effect of the span attenuation (L) between the two
nodes. Span loss changes due to aging fiber and components or changes in operating
conditions. The power into Node 2 is given by the following formula:
Pin2 = LPout1(n)
The phase gain of the preamplifier on Node 2
(GPre-2) is set during provisioning to compensate for the span loss so that the Node
2 preamplifier output power (Pout-Pre-2) is equal to the original transmitted power,
as represented in the following formula:
Pout-Pre-2 = L x GPre-2 x Pout1(n)
In cases of system degradation, the power received at Node 2 decreases due to the change of span insertion loss (from L to
L'). As a consequence of the preamplifier gain control working mode, the Node 2 preamplifier output power (Pout-Pre-2) also
decreases. The goal of APC at the shelf controller layer is simply to detect if an amplifier output change is needed because
of changes in the number of channels or to other factors. If factors other than the "changes in the number of channels" factor
occur, APC provisions a new gain at the Node 2 preamplifier (GPre-2') to compensate for the new span loss, as shown in the
formula:
Generalizing on the preceding relationship, APC is able to compensate for system degradation by adjusting working amplifier
gain or variable optical attenuation (VOA) and to eliminate the difference between the power value read by the photodiodes
and the expected power value. The expected power values are calculated using:
Provisioned per channel power value
Channel distribution (the number of express, add, and drop channels in the node)
ASE estimation
Channel distribution is determined by the sum of the provisioned and failed channels. Information about provisioned wavelengths
is sent to APC on the applicable nodes during the circuit creation. Information about failed channels is collected through
a signaling protocol that monitors alarms on ports in the applicable nodes and distributes that information to all the other
nodes in the network.
ASE calculations purify the noise from the power
level that is reported from the photodiode. Each amplifier can compensate for its
own noise, but cascaded amplifiers cannot compensate for ASE generated by preceding
nodes. The ASE effect increases when the number of channels decreases; therefore, a
correction factor must be calculated in each amplifier of the ring to compensate for
ASE build-up.
APC is a network-level feature that is distributed among different nodes. An APC domain is a set of nodes that are regulated
by the same instance of APC at the network level. An APC domain optically identifies a network portion that can be independently
regulated. 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. An optical network can be divided into several different domains, with the
following characteristics:
Every domain is terminated by two node sides. The node sides terminating domains are:
Terminal node (any type)
ROADM node
Hub node
Cross-connect (XC) termination mesh node
Line termination mesh node
APC domains are shown in the GUI.
Inside a domain, the APC algorithm designates a primary node that is responsible for starting APC hourly or every time a new
circuit is provisioned or removed. Every time the primary node signals APC to start, gain and VOA setpoints are evaluated
on all nodes in the network. If corrections are needed in different nodes, they are always performed sequentially following
the optical paths starting from the primary node.
APC corrects the power level only if the variation exceeds the hysteresis thresholds of +/– 0.5 dB. Any power level fluctuation
within the threshold range is skipped because it is considered negligible. Because APC is designed to follow slow time events,
it skips corrections greater than 3 dB. This is the typical total aging margin that is provisioned during the network design
phase. After you provision the first channel or the amplifiers are turned up for the first time, APC does not apply the 3-dB
rule. In this case, APC corrects all the power differences to turn up the node.
To avoid large power fluctuations, APC adjusts power levels incrementally. The maximum power correction is +/– 0.5 dB. This
is applied to each iteration until the optimal power level is reached. For example, a gain deviation of 2 dB is corrected
in four steps. Each of the four steps requires a complete APC check on every node in the APC domain. APC can correct up to
a maximum of 3 dB on an hourly basis. If degradation occurs over a longer time period, APC compensates for it by using all
margins that you provision during installation.
APC can be manually disabled. In addition, APC automatically disables itself when:
A Hardware Fail (HF) alarm is raised by any
card in any of the domain nodes.
A Mismatch Equipment Alarm (MEA) is raised by any card in any of the domain nodes.
An Improper Removal (IMPROPRMVL) alarm is raised by any card in any of the domain nodes.
Gain Degrade (GAIN-HDEG), Power Degrade (OPWR-HDEG), and Power Fail (PWR-FAIL) alarms are raised by the output port of any
amplifier card in any of the domain nodes.
A VOA degrade or fail alarm is raised by any of the cards in any of the domain nodes.
The signaling protocol detects that one of the APC instances in any of the domain nodes is no longer reachable.
APC raises the following minor, non-service-affecting alarms:
APC Out of Range—APC cannot assign a new setpoint for a parameter that is allocated to a port because the new setpoint exceeds
the parameter range.
APC Correction Skipped—APC skipped a correction to one parameter allocated to a port because the difference between the expected
and current values exceeds the +/– 3-dB security range.
APC at the Amplifier Card Level
In constant gain mode, the amplifier power out control
loop performs the following input and output power calculations, where G represents
the gain and t represents time.
Pout (t) = G * Pin (t) (mW)
Pout (t) = G + Pin (t) (dB)
In a power-equalized optical system, the input power scales with the number of channels, and the amplifier software adjusts
for power fluctuations caused by changes in the incoming signal's channel count.
The amplifier software detects input power changes at two instances, t1 and t2, as traffic fluctuations occur. In the formula,
'm' and 'n' denote distinct channel numbers, and Pin/ch signifies the input power per channel.
Pin (t1)= nPin/ch
Pin (t2) = mPin/ch
The output power is quickly adjusted in response to input power changes, maintaining constant power for each channel, even
during upgrades or fiber cuts, with a reaction time in milliseconds.
The power and mode for each channel are determined by Automatic Node Setup (ANS) on a per-degree basis during provisioning.
Forcing Power Correction
A wrong use of maintenance procedures can lead the system to raise the APC Correction Skipped alarm. The APC Correction Skipped
alarm strongly limits network management (for example, a new circuit cannot be converted into In-Service (IS) state).
The Force Power Correction button in the APC section helps the user to restore normal conditions by clearing the APC Correction Skipped alarm. The use of the Force Power Correction button must be supervised by Cisco TAC to prevent any traffic loss.
Click the Optical Configuration tab and then click APC to expand it.
A list of degrees is displayed.
Step 3
Select the check box corresponding to the degree you want to enable APC and click the Edit button.
Step 4
Select automatic-enabled from the Admin Status drop-down list.
Only degrees with Admin Status as force-disabled can be enabled.
Step 5
Click Apply.
Step 6
Verify that the Service Status field changes to enabled.
Disable APC
Use this task to disable APC.
Caution
When APC is disabled, aging compensation is not applied and circuits cannot be activated. Disable APC only to perform specific
troubleshooting or node provisioning tasks. When the tasks are completed, enable and run APC. Leaving APC disabled can cause
traffic loss.
Click the Optical Configuration tab and then click APC to expand it.
A list of degrees is displayed.
Step 3
Select the check box corresponding to the degree you want to enable APC and click the Edit button.
Step 4
Select force-disabled from the Admin Status drop-down list.
Only degrees with Admin Status as automatic-enabled can be disabled.
Step 5
Click Apply.
Step 6
Verify that the Service Status field changes to force-disabled.
Span Loss Measurement
Span loss measurements (in dB) check the span loss and are useful whenever changes to the network
occur.
The span loss operational parameters are:
Measured By—Displays whether the span loss is measured by the channel or Optical Service Channel (OSC). If a channel is not configured,
the span loss is measured by the OSC. An EDFA measures the span loss based on circuits.
Measured Span Loss—Displays the measured span loss.
Measured Span Loss Accuracy—Displays the accuracy of the
span loss measurement. For example, if the measured span loss is 20 dB and the
displayed accuracy value is 2.5, the actual span loss could either be 19 or 21
dB.
Measured Time—Displays the time and date when the last span loss measured value is changed.
If there is a new network with Cisco Optical Site Manager, the operational parameters list of span loss has two rows.
The first row displays the OSC-measured span loss details. After the channel is
configured, the second row is added, which displays the channel-measured span loss
details. After the channel is configured, only the channel-measured span loss details
are updated.
View or modify span loss parameters
Use this task to measure span loss and update the minimum and maximum expected span loss values for an optical span.
Span loss parameters help monitor optical span performance and detect conditions where measured loss exceeds expected thresholds.
If a channel or OSC is not configured, span loss measurement is not reported and the operational parameters list is empty.
Follow these steps to view or modify span loss parameters.
Procedure
Step 1
Click Optical Setup in the left panel.
Step 2
Click the Optical Configuration tab, and then click Span Loss to expand it.
Step 3
Click the + icon next to a degree to expand it.
Step 4
Select a row and click Measure Span Loss.
A message appears.
Click OK.
Step 5
Click Retrieve to view updated values.
The measured span loss, accuracy, and measurement time are updated.
Step 6
Enter values for Min. Exp. Span Loss or Max. Exp. Span Loss in dB.
The valid range is from 0 to 99 dB.
Step 7
Click Apply.
A confirmation message appears.
Step 8
Click Yes.
The span loss range is extended to include the accuracy value.
A Span Loss Out of Range condition is raised when the measured span loss exceeds the extended range.
Step 9
(Optional) Click Export to Excel to export the data.
The Span Loss Measured Data section displays the following information:
Field
Description
Degree
Displays the side for which span loss information is shown.
Measured By
Indicates whether the measurement was executed using OSC or channels.
Min. Exp. Span Loss (dB)
Displays the minimum expected span loss value.
Max. Exp. Span Loss (dB)
Displays the maximum expected span loss value.
Measured Span Loss (dB)
Displays the measured span loss value.
Measured Accuracy (dB)
Displays the accuracy of the span loss measurement.
For example, if the measured span loss is 20 dB and the accuracy value shown is 2.5, the actual span loss may range approximately
from 19 dB to 21 dB.
Measured Time
Displays the date and time of the last span loss measurement.
Configure amplifier parameters
Set the optical amplifier settings for cards. This includes selecting the amplifier working mode (such as Channel Power or
Fixed Gain), setting gain values, tilt, power setpoints, and other parameters to optimize the amplifier’s performance and
maintain signal quality across the optical network.
The Amplifier section displays the following details:
Table 1. Parameters for amplifier cards
Parameter
Description
Displayed Values
Port
(Display only) Displays the port number, port type, and direction (TX or RX).
—
Total Output Power (dBm)
(Display only) Shows the current power level for each port.
—
Output Power Setpoint (dBm)
Shows the output power setpoint.
—
Working Mode
Select the working mode.
Total Power
Optimized
Start and Hold
Role
Role of the amplifier.
Preamplifier
Booster
Actual Gain (dB)
Actual gain setpoint.
—
Target Gain (dB)
Target gain setpoint.
—
Tilt Setpoint (dB)
Target output tilt requested by the user.
—
PSD Optimized (dBm/GHz)
Optimized PSD
—
Gain Setpoint (dB)
Target amplifier gain requested by the user.
—
Gain Range
Sets the gain range of the amplifier.
Gain Range 1
Gain Range 2
No Gain Range
Power Degrade Threshold (High) (dBm/GHz)
Shows the current value of the optical power degrade high threshold.
—
Power Degrade Threshold (Low) (dBm/GHz)
Shows the current value of the optical power degrade low threshold.
—
Status
Shows the current status of the amplifier.
—
Gain Degrade High (dB)
(Display only) Shows the current value of the gain degrade high threshold configured in the card. This threshold applies only
when the amplifier is active and in constant gain mode.
Gain Degrade High refers to the Gain value of the port and is automatically calculated by the control card when the amplifier
is turned up.
—
Gain Degrade Low (dB)
(Display only) Shows the current value of the gain degrade low threshold configured in the card. This threshold applies only
when the amplifier is active and in constant gain mode.
Gain Degrade Low refers to the Gain value of the port and is automatically calculated by the control card when the amplifier
is turned up.
—
Max OSC Power Delta
The maximum allowable deviation or change in the optical power level of the OSC before an alarm or warning is triggered.
—
Provision interface parameters
Use this task to provision or modify interface parameters. This supports operational requirements for enabling, disabling,
or tuning optical interfaces as needed.
Change administrative state, set optical thresholds, and adjust interface-related parameters for RX or TX ports.
Follow these steps to provision interface parameters:
Procedure
Step 1
Click Optical Setup in the left panel.
Step 2
Click the ANS Parameters tab and then click Interface to expand it.
Step 3
Modify the required settings in the interface table. This table describes each parameter and its options.
Table 2. Interface Options
Parameter
Description
Options
Port
Displays the port number, port type, and direction (RX or TX).
All RX and TX ports (Display only)
Admin State
Sets the administrative state of the port.
Unlocked / IS
Locked, disabled / OOS, DSBLD
Locked, maintenance / OOS, MT
Unlocked, automaticInService / IS, AINS
Service State
Displays the autonomously generated state that gives the port's overall condition (display only). States appear as: Primary
State-Primary State Qualifier, Secondary State.
Displays the optical power for each port (display only).
—
OSC Power (dBm)
Displays the service-channel power level for each port (display only).
—
Optical PSD Setpoint (dBm/GHz)
Target output Power Spectral Density requested by the user.
-50 to 10
Attenuator Value (dB)
Sets the attenuator value.
—
Optical Power Threshold Low (dBm)
Fail low threshold used to detect the LOS alarm on the port.
—
OSC Power Threshold Low (dBm)
Displays the OSC power level for each port (display only).
—
Current Power Degrade High (dBm)
Shows the current value of the optical power degrade high threshold configured in the card (display only). Power Degrade High
refers to the Signal Output Power value and is automatically calculated.
—
Current Power Degrade Low (dBm)
Shows the current value of the optical power degrade low threshold configured in the card (display only). Power Degrade Low
refers to the Signal Output Power value and is automatically calculated.
—
Current Power Failure Low (dBm)
Shows the optical power failure low threshold for the port (display only).
—
Step 4
Click Apply to save the changes.
Note
For passive modules, the Service State is displayed as IS-NR by default.
The specified ANS interface parameters are provisioned as required.
What to do next
Verify the state and alarms of the affected ports after making changes. Adjust further as required to ensure stable operation.
Provision Raman Amplifier Parameters
Use this task to provision the optical Raman amplifier parameters.
Click the ANS Parameters tab and then click Raman Amplifier to expand it.
Step 3
Modify any of the settings described in the following table.
Table 3. Raman Amplifier Parameters for Amplifier Cards
Parameter
Description
Options
Port
(Display only) Displays the port number, port type, and
direction (TX or RX).
—
Status
Displays the Status of the port.
Gain Setpoint (dB)
Target amplifier gain requested by the user.
—
Actual Gain (dB)
(Display only) Displays the actual amplifier gain.
—
Pumping Scheme
(Display only) Displays the pumping scheme that the card
uses.
Counter-Propagating for the RAMAN-CTP, RMN-CTP-CL,
EDRA-1-xx, and EDRA-2-xx cards.
Co-Propagating for the RAMAN-COP card.
Calibration Type
Calibration type that the card uses.
The RAMAN-COP card supports only manual calibration. The RAMAN-CTP card supports both automatic and manual calibration. The RMN-CTP-CL card supports only automatic calibration. If a node has both RAMAN-CTP and RAMAN-COP cards, the RAMAN-CTP card supports only manual calibration.
Automatic
Manual
No-Calibration
Unsaturated Gain Setpoint (dBm)
Unsaturated target amplifier gain. This field is editable
only for the RAMAN-COP card.
0–50
Step 4
Click Apply to save the changes.
The RAMAN port section is displayed.
Step 5
Expand the RAMAN port to view the pump power details.
Table 4. RAMAN Pump Power Parameters
Parameter
Description
Pump ID
(Display only) Identifier of the Raman Pump (2 pumps with RAMAN-CTP and 4 pumps with EDRA).
Pump Power Setpoint (mW)
(Only for RAMAN-CTP and RAMAN-COP cards) Provisioned value of pump power setpoint. This value is effective only for manual
calibration of RAMAN-CTP and RAMAN-COP cards and if the calibration is not performed. The value of this parameter must also
be provided for automatic calibration of the RAMAN-CTP card even if the value is not effective.
Pump Power Target (mW)
(Display only) Target power set by the internal control algorithm. The result of calibration can be both automatic and manual.
Pump Power (mW)
(Display only) Actual power value of the individual pump.
Step 6
Click Apply to save the changes.
Manage Raman Interface Parameters
Use this task to manage the Raman interface parameters.
Click the ANS Parameters tab and then click Raman Interface to expand it.
Step 3
View the settings described in the following table. Only the Admin State
parameter can be modified.
Table 5. Interface Options
Parameter
Description
Options
Port
(Display only) Displays the port number, port type, and
direction (RX or TX)
All the RX and TX ports
Admin State
Sets the administrative state of the port.
From the drop-down list, choose one of the following:
Unlocked (ETSI)/ IS (ANSI)
Locked, disabled (ETSI)/OOS, DSBLD (ANSI)
Locked, maintenance (ETSI)/OOS, MT (ANSI)
Unlocked, automaticInService (ETSI)/ IS, AINS
(ANSI)
Service State
(Display only) Identifies the autonomously generated
state that gives the overall condition of the port.
Service states appear in the format: Primary
State-Primary State Qualifier, Secondary State.
IS-NR/
Unlocked-enabled
OOS-AU,AINS/
Unlocked-disabled, automaticInService
OOS-MA,DSBLD/
Locked-enabled,disabled
OOS-MA,MT/
Locked-enabled,maintenance
Optical Power (mW)
(Display only) Displays the optical power for each port.
—
Current Optical Power Setpoint (mW)
(Display only) Shows the current value of the optical
power setpoint that must be reached.
—
Current Power Degrade High (mW)
(Display only) Shows that the current value of the
optical power degrade high threshold.
Power Degrade High refers to the Signal Output Power
value of the port and is automatically calculated by the
control card.
—
Current Power Degrade Low (mW)
(Display only) Shows that the current value of the
optical power degrade high threshold configured in the
card.
Power Degrade Low refers to the Signal Output Power value
of the port and is automatically calculated by the
control card.
—
Current Power Failure Low (mW)
(Display only) Shows the optical power failure low
threshold for the port.
—
Step 4
Click Apply to save the changes.
Optical cross-connect management
An Optical Cross-Connect (OXC) circuit is a bidirectional optical connection that links two optical nodes over a specified
C-band wavelength within a DWDM system.
Defined and instantiated using data models.
Operates on C-band wavelengths.
Provides bidirectional connectivity between optical nodes through DWDM elements.
How Optical Cross-Connect Circuits Work
An OXC circuit establishes an optical path through DWDM network elements and provides a wavelength-based bidirectional connection
between two interface ports.
The connection is formed through the following optical components:
Wavelength selective switches (WSS)
Multiplexers and demultiplexers
Add/drop cards
Typical signal flow for an OXC circuit:
Enters the DWDM system from the source interface port.
Traverses DWDM network elements (WSS, mux/demux, add/drop).
Exits the DWDM system toward the destination interface port.
The following table describes the administrative states of an OXC circuit.
Table 6. OXC Administrative States
State
Operational Status
Description
IS/Unlocked
In Service
The circuit is active and unlocked.
IS, AINS/Unlocked
Automatic In Service
The circuit automatically transitions to an in-service state.
OOS, DSBLD/Locked
Out of Service
The circuit is disabled and locked.
Important
Cisco Optical Site Manager operates with native IOS XR NETCONF (CLI) data models. Configurations performed using OpenConfig
(OC) models are incompatible with IOS XR native models. Do not use OpenConfig models to configure devices that are intended
to be managed by Cisco Optical Site Manager.
Note
Administrative state changes affect circuit availability but do not change the physical optical path.
Example of an Optical Cross-Connect Circuit
An OXC circuit connects two optical nodes across a DWDM network by routing a specific C-band wavelength from a source interface,
through wavelength selective switches and multiplexing components, to a destination interface.
Non-OXC Optical Connectivity
A unidirectional optical path or a simple fiber patch that does not traverse DWDM components and that is not modeled as a
bidirectional, wavelength-based circuit does not qualify as an Optical Cross-Connect circuit.
Analogy for Optical Cross-Connect Circuits
An OXC circuit is similar to a railway switchyard: it dynamically connects tracks (wavelength paths) to guide trains (optical
signals) along specific routes without altering the physical rails themselves.
View Optical Cross-Connect Circuits
Use this task to view the configuration and operational details of Optical Cross-Connect (OXC) circuits that are modeled on
a node. The task explains how to access OXC information, export OXC data, and synchronize OXC information with the managed
device.
Inspect OXC parameters such as central frequency, allocation width, and path endpoints.
Export OXC details for reporting or offline review.
Synchronize OXC data with the associated NCS device to refresh the displayed information.
OXC circuits are created using data models and provide bidirectional wavelength-based connectivity between two optical nodes
in a DWDM network. This task describes how to view those OXC records in the Web UI.
The information shown on the Optical Cross Connections tab is primarily read-only. Some actions (for example, deletion or device synchronization) depend on your deployment and
device capabilities.
OXC entries represent modeled, bidirectional circuits mapped to C-band wavelengths.
To refresh OXC data from the device, use the Sync from device action (if available for your device model).
Ensure network connectivity to the associated NCS device if you plan to use the Sync from device action.
Follow these steps to view the configuration and operational details of Optical Cross-Connect circuits that are modeled on
a node.
Procedure
Step 1
Click Optical Setup in the left panel.
Step 2
Click the Optical Cross Connections tab.
Step 3
Expand the cross-connect entry to view Path 1 and Path 2 details by clicking the + icon.
Click the down arrow on the right of a path to show internal path parameters.
Step 4
Review the cross-connect summary fields displayed in the table.
The table includes the following fields for each cross-connect:
Connection Label—Name of the cross-connect.
Type—Type of cross-connect (bidirectional).
Admin Status—Administrative state of the circuit.
Service Status—Operational status of the service.
Central Frequency (THz)—Spectral position of the circuit.
Allocation Width (GHz)—Bandwidth occupied by the service (range: 25–300 GHz).
Signal Width (GHz)—Carrier bandwidth.
Path 1 End-points—Source and destination interfaces for Path 1.
Path 2 End-points—Source and destination interfaces for Path 2.
To view per-path internal details, expand Path 1 or Path 2 and review these items:
Interface Name—Interface identifier.
Optical Power—Measured optical power.
Power Failure Low—Threshold for power-failure detection.
Optical PSD Setpoint (dBm/GHz)—Configured optical power spectral density setpoint (independent of circuit width).
Current PSD Setpoint—Current PSD setpoint.
Optical Power Setpoint—Power setpoint scaled to the circuit width.
Step 5
(Optional) Click the Export to Excel button to export the displayed OXC information to an Excel file.
Step 6
(Optional) Click the Download OXC as XML button to download the cross-connect details as an XML file.
Step 7
(Optional) Click the Sync from device button to synchronize the OXC information with the associated device.
Step 8
(Conditional) To remove a cross-connect, select the check box for the cross-connect and click the - button.
Note: The Optical Cross Connections entries are typically read-only in many deployments. Deletion is only possible when your COSM deployment and device model
allow direct modification of modeled OXC records. If deletion is not available, use device-side management or a supported
provisioning workflow.
The Optical Cross Connections tab displays a list of OXC circuits with the fields described above. Expanding an entry reveals per-path details and measured
values.
What to do next
After viewing or exporting OXC information, confirm any required follow-up actions such as device-side configuration or synchronization.
If you synchronized from the device, verify that the displayed Service Status reflects the expected operational state.
If you exported data, store the export in your documentation system as required.
Feedback