Configuration Guide for Cisco Optical Site Manager, IOS XR Releases 25.x.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 the Cisco Optical Network Planner Configuration File
If you have a configuration file NETCONF file (.xml) exported from Cisco Optical Network Planner, you can import it to Cisco
Optical Site Manager. The file includes parameters for the node, shelf, card type, port (including the wavelength of the card),
pluggable port module (PPM), OTN, and FEC parameters.
Only the values present in XML format appear in the configuration file parameters. If the values are not in XML format, a
column appears blank. The XML file values are independently reported and do not affect any configuration changes that you
apply.
Use this task to import the Cisco Optical Network Planner NETCONF file (.xml) into Cisco Optical Site Manager.
Before you begin
Before importing the NETCONF file (.xml), ensure that:
The NETCONF file (.xml) contains the following parameters available on Cisco Optical Site Manager:
Click Select Files, navigate to the location where the NETCONF file (.xml) is present and select it.
A confirmation message appears.
Step 4
Click Yes.
Step 5
Click Upload.
A confirmation message appears after the upload is complete.
Step 6
To export the XML file, click the Download Node Configuration as XML button.
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
Table 1. Feature History
Feature Name
Release Information
Description
Support for Trunk and Client Port Connections
Cisco IOS XR Release 25.1.1
Cisco Optical Site Manager now allows one or more trunk ports on line cards to feed multiple line cards via client ports.
This feature supports real and pre-provisioned line cards and is visible in NFV view with optical types txp and roadm. It enables IPC connections between trunk ports and client ports, allowing for efficient data flow across various line cards.
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.
You can also create IPC between trunk ports of one line card and the client ports of another line card, optimizing data flow
across various line cards. These IPC can be viewed in the NFV, where optical types are selected as txp and roadm.
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 view or modify span loss parameters.
Note
If a channel or OSC is not configured, span loss measurement is not reported and the operational parameters list is empty.
Click the Optical Configuration tab and then click Span Loss to expand it.
Step 3
Click the + button corresponding to a degree in the list and then click Span Loss Measured Data to expand it.
Step 4
Select a row and click the Measure Span Loss button.
A message appears. Click OK.
Step 5
Click the Retrieve button to view the updated Measured Span Loss, Measured Accuracy, and Measured time values.
Step 6
Enter the values for Min. Exp. Span Loss or Max. Exp. Span Loss in dB. The range is from 0 to 99.
Step 7
Click Apply.
A confirmation message appears.
Step 8
Click Yes.
The span loss range is extended including the Accuracy value. A Span Loss Out
of Range condition is raised when the measured span loss is higher than the
extended range.
Step 9
(Optional) Click the Export to Excel button to export
the information to an Excel sheet.
The Span Loss Measured Data section displays the following information:
Degree—Displays the side for which span loss information appears.
Measured By—Displays whether the measurement was executed with or without channels. Values are OSC or CHANNEL.
Min Exp. Span Loss (dB)—Displays the minimum expected span loss (in dB) for the incoming span.
Max Exp. Span Loss (dB)—Displays the maximum executed span loss (in dB) for the incoming span.
Measured Span Loss (dB)—Displays the measured span loss value.
Measured Accuracy (dB)—Displays the resolution or accuracy of the span loss measurement. The resolution is +/-1.5 dB if the measured span loss is
0–25 dB. The resolution is +/-2.5 dB if the measured span loss is 25–38 dB.
Measured Time—Displays the time and date when the last span loss measured value is changed.
Configure Amplifier Parameters
Use this task to configure the optical amplifier parameters.
Click the ANS Parameters tab and then click Amplifier to expand it.
Step 3
Modify any of the settings described in the following table.
Table 2. Amplifier Parameters for Amplifier Cards
Parameter
Description
Options
Working Mode
Shows the working mode.
Channel Power
Total Power
Optimized
Fixed Gain
Start and Hold
Tilt Setpoint (dB)
Target output tilt requested by the user.
—
PSD Setpoint (dBm/GHz)
Power Spectral Density. Target output power requested by
the user for each circuit.
—
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
Step 4
Click Apply to save the changes.
The Amplifier section displays the following details:
Table 3. Amplifier 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
Shows the working mode.
Channel Power
Total Power
Optimized
Fixed Gain
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 Setpoint (dBm/GHz)
Power Spectral Density. Target output power requested by the user for each circuit.
—
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.
—
Provision Interface Parameters
Use this task to change the optical interface parameters.
Click the ANS Parameters tab and then click Interface to expand it.
Step 3
Modify the settings described in the following table. The provisionable parameters are listed in the Options column in the table.
Table 4. 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 / IS
Locked, disabled/OOS, DSBLD
Locked, maintenance/OOS, MT
Unlocked, automaticInService/IS, AINS
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 (dBm)
(Display only) Displays the optical power for each port.
—
OSC Power (dBm)
(Display only) Displays the service-channel power level for each port.
—
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)
(Display only) Displays the OSC power level for each port.
—
Current Power Degrade High (dBm)
(Display only) Shows the current value of the optical power degrade high threshold configured in the card.
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 (dBm)
(Display only) Shows the current value of the optical power degrade low 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 (dBm)
(Display only) Shows the optical power failure low threshold for the port.
—
Step 4
Click Apply to save the changes.
Note
For passive modules, the Service State is displayed as IS-NR by default.
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 5. 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 6. 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 7. 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
Optical cross-connect (OXC) circuits are used to connect two optical nodes on a specified C-band wavelength. These circuits
are created using data models and are bidirectional in nature. The connection is established through the ports present on
the wavelength selective switches, multiplexers, demultiplexers, and add/drop cards.
In an OXC circuit, the wavelength from a source interface port enters to a DWDM system and then exits from the DWDM system
to the destination interface port.
The administrative states are:
IS/Unlocked
IS, AINS/Unlocked, AutomaticInService
OOS, DSBLD/Locked, disabled
View Optical Cross-connect Circuits
Use this task to view the details of the optical cross-connects that are created for a node using data models.
Note
The optical cross-connects are read-only and cannot be modified.
To delete an optical cross-connect, select the check box corresponding to the OXC you want to delete and click the - button.
Step 4
(Optional) Click the Export to Excel button to export the information to an Excel sheet.
Step 5
(Optional) Click the Download OXC as XML button to download the details of the optical cross-connects as a XML file.
Step 6
(Optional) Click the Sync from device button to synchronize the optical cross-connect information with the associated NCS 1000 device.
The Optical Cross Connections tab displays the following details for each cross-connect.
Connection Label—Displays the name of the cross-connect.
Type—Displays the type of cross-connect. It is bidirectional.
Admin Status—Displays the admin state on the circuit.
Service Status—Displays the status of the service.
Central Frequency (THz)—Displays the spectral position of the circuit.
Allocation Width (GHz)—Displays the bandwidth occupied by the service. The range is 25 to 300GHz.
Signal Width (GHz)—Displays the carrier bandwidth.
Path 1 End-points—Displays the source and destination interfaces of the path.
Path 2 End-points—Displays the source and destination interfaces of the path.
To view Path 1 or Path 2, click the + icon to expand the cross-connect. Click the down arrow on the right to view the internal
details of Path 1 or Path 2. The details are:
Interface Name—Displays the interface name.
Optical Power—Displays the value of the optical power.
Power Failure Low—Displays the threshold for power failure.
Optical PSD Setpoint (dBm/GHz)—Displays the configured optical power spectral density setpoint. This setpoint is independent of the width of the circuit.
Current PSD Setpoint—Displays the current optical power spectral density setpoint. This setpoint is independent of the width of the circuit.
Optical Power Setpoint—Displays optical power setpoint. This setpoint is scaled to the width of the circuit and matches the value of the optical
power parameter.
GMPLS UNI
Table 8. Feature History
Feature Name
Release Information
Description
GMPLS UNI Circuit Connection
Cisco IOS XR Release 25.1.1
You can now establish circuit connections between two clients within an optical network using the Generalized Multiprotocol
Label Switching (GMPLS) User Network Interface (UNI). This connection is facilitated through signaling exchanges between UNI
Client (UNI-C) nodes, which are router nodes, and UNI Network (UNI-N) nodes, which are optical nodes.
This integration enables effective usage of the DWDM grid with minimal wastage of spectral bandwidth and allows the transmission
of mixed bit-rate or mixed modulation data in a grid with different channel widths.
The Generalized Multiprotocol Label Switching (GMPLS) User Network Interface (UNI) creates a circuit connection between two
clients (UNI-C) of an optical network.
GMPLS UNI Advantages
GMPLS UNI plays a crucial role in connecting and optimizing network functionalities:
GMPLS UNI allows packet networks to directly access the optical transport control plane, enabling coordination of resource
requirements with the optical transport network.
By leveraging open standards, GMPLS UNI optimizes network resources and enhances utilization across both packet and optical
networks.
Channel Spacing Types in GMPLS
GMPLS supports two types of channel spacing, each affecting the capacity and flexibility of traffic management:
Fixed Grid Channel Spacing: This spacing is fixed at 50 GHz, supporting traffic rates of 100 and 200 Gbps.
Flexible Grid Channel Spacing: This spacing is set at 6.25 GHz, accommodating all data rates.
How to Create a GMPLS UNI Tunnel
Before you begin
The NCS 2000 node must possess a valid license for ROADM and WSON support.
Management IP addresses for both NCS 1014/NCS 1004 and NCS 2000 nodes must be accessible.
The administrative state of the trunk port of the optics controller on the NCS 1014 or NCS 1004 node must not be in the shutdown
state.
Workflow
Figure 4. GMPLS UNI Tunnel Between two NCS 1014/NCS 1004 Nodes
Creating a tunnel between two NCS 1014 or NCS 1004 nodes on a network involves establishing a connection from the headend
to the tailend. The tunnel can be created between the source and destination NCS 1014 or NCS 1004 nodes without involving
NCS 2000 nodes in the middle. The NCS 2000 provides GMPLS control plane support and enables dynamic provisioning and rerouting
of lightpaths.
These stages describe how to create a connection between the NCS 1014 and NCS 2000 at the headend of the network.
Add a card mode on the NCS 1014 or NCS 1004 card. For more details, see NCS 1000 line card modes.
Repeat the same steps at the tailend of the network to ensure complete connectivity.
Create static Link Management Protocol link for GMPLS
Table 9. Feature History
Feature Name
Release Information
Description
Static Link Management Protocol configuration for GMPLS
Cisco IOS XR Release 25.1.1
You can now configure static Link Management Protocol (LMP) using the Cisco Optical Site Manager web UI to establish connectivity
between an NCS 2000 node and NCS 1004 and NCS 1014 nodes for GMPLS UNI.
This protocol efficiently manages the control channel across GMPLS UNIs, ensuring smooth Traffic Engineering (TE) link connectivity
between interfaces. Furthermore, it performs fault management functions, helping in fault isolation, link property correlation,
and verifying link connectivity.
Link Management Protocol (LMP) manages and maintains the control and data links between nodes while overseeing the channels
and links necessary for routing, signaling, and comprehensive link management. The LMP link is created to establish connectivity
between an NCS 2000 node and an NCS 1004 node.
LMP effectively manages the control channel across the GMPLS UNIs, ensuring seamless Traffic Engineering (TE) link connectivity
between these interfaces. Also, it performs fault management, aiding in fault isolation, link property correlation, and verifying
link connectivity.
To to create LMP to establish connectivity between an NCS 2000 node and an NCS 1004 node, using the LMP Configuration Wizard in Cisco Optical Site Manager, perform these tasks:
Click the Optical Configuration tab and then click GMPLS > LMP to expand it.
Step 3
Click the + button to open LMP Configuration Wizard.
From the LMP Type drop-down list, choose the type of LMP.
If the LMP link is going to be established with
Select...
NCS 1004 or 1014 device
LOCAL TXP/OCHNC
NCS 1004 or NCS 4000 routers
Signaled
a TXP in a remote NCS 2000 ROADM node
Remote TXP
Note
The LOCAL TXP/OCHNC and Remote TXP systems support a multi-carrier configuration, which involves bundling two Add & Drop ports
to enable inverse multiplexing of traffic across trunks. This approach optimizes bandwidth distribution. However, the Signaled
LMP does not support multi-carrier configuration.
Step 4
Click Next.
Select the optical parameters for LMP
Use this task to configure various optical parameters for different LMP types:
External links are the logical links between two optical degrees that belong to two adjacent nodes. From this release, you
can add one or more external links on a node using different optical degrees configured on that node. The creation of an external
link allows the management of a remote node and these external links are used when it is not possible to create an optical-service-channel
(OSC) communication.
Cisco Optical Site Manager enables you to create and provision external logical links between a source local node and a destination
remote node. These nodes use local and remote degrees and require IP addresses of the NCS 2000 devices.
Limitations for DCN Extension
If any external link is already configured for a degree on a device, then you cannot use that degree for another external
link on the same node or device. To achieve this, you should delete the existing external link and create a new external link
on the same degree of the device.
You cannot delete the degree if that degree is already used by an external link.
Manage DCN Extension
Use this task to add, view, or delete external links on the node.
Ensure that the degrees are existing in the node before configuring external links.
Procedure
Step 1
Click the hamburger icon at the top-left of the page, and select Node Configuration.
Step 2
Click the Optical Configuration > External Links tabs.
Step 3
Perform these steps, as needed.
To add a new external link, perform these steps:
Click the + button.
The New External Link dialog box appears.
In the Local IP field, the Local IP address of Cisco Optical Site Manager instance that you are connected gets displays.
Enter username of the remote user who is allowed to perform configuration on the remote Cisco Optical Site Manager instance
in the Remote Username field.
Enter password of the remote user who is allowed to perform configuration on the remote Cisco Optical Site Manager instance
in the Remote Password field.
Enter the IP address of an Cisco Optical Site Manager instance that you want to get connected in the Remote IP field.
Click the refresh (image) button at the end of the Remote IP field. The details from the remote node are fetched to allow the configuration.
From the Local Degrees drop-down list, select the available local degrees to create a starting point for the external link connection.
From the Remote Degrees drop-down list, select the available remote degrees to create an ending point for the external link connection.
Note
If no degree is displayed, check the remote Cisco Optical Site Manager instance to configure the degrees.
Click Add.
The external link is added to the table of the local and remote Cisco Optical Site Manager Node Configuration pages. The table displays the following information under the External Links section of the Node Configuration page:
Local Degrees—Specifies the local degree on which the external link is created.
Interfaces—Specifies the interfaces on which the external link is created.
Connected To—Specifies the remote node instance to which it is connected. You can click the remote node instance link that is connected
and it opens the remote node Cisco Optical Site Manager instance. If nothing is displayed, then the local endpoint is not
connected.
Local IP—Specifies the IP address of the NCS 2000 device on which the external link is created.
Remote IP—Specifies the NCS 2000 remote device IP address which is the end of the external link connection.
To delete the external link, perform these steps:
Check the check boxes corresponding to the external link that you want to delete.
Click the - button to delete the selected external link.
A confirmation message appears. You must authenticate with the username and password for the remote Cisco Optical Site Manager
instance to which the external links are connected.
Click Yes.
The external link is deleted from both the local and remote Cisco Optical Site Manager instances.
Remote Node Management Using GCC
The remote node management feature allows you to remotely manage NCS 2000 devices with transponder cards using the in-band
General Communication Channel (GCC) channels with fiber optics from OTN clients. You can only use the Cisco Light Web UI on
the NCS 2000 node to create and manage the GCC channel to the remote NCS 2000 node.
The transponder cards that are supported for remote node management using GCC on Cisco web UI are 200G-CK-LC, and 400G-XP
and 10x10-LC cards.
Limitations
For remote node using a GCC0 channel, the Cisco Optical Site Manager and NCS 2000 router should be in different subnets.
Manage Remote Node Using GCC
To manage a remote node, perform the following steps:
Provision a Node in GCC Using Light Web UI for Remote Node
Use this task to provision a node in GCC using the Cisco Light web UI.
Procedure
From the Cisco light web UI, click Provisioning > GCC Configurations.
In the GCC Configuration section, enter the following details:
Shelf Number—Choose the shelf number.
Slot Number—Choose the slot number.
Port Number—Choose the port number. The options are:
200G—Port 2
400G—Port 11 or 12 pluggable
Port Mode—Choose the transponder card port mode.
200G—The option is MXP 10x10G.
400G—The options are M100 or M200.
M100
First Slice—First slice should be configured when you are using M_200G as the port mode.
Second Slice—Choose the slice on which the card is configured. The options are OPM 100G or OPM 10 X 10G.
M200
First Slice—Choose the slice on which the card is configured. The options are OPM 100G or OPM 10 X 10G.
Second Slice—Choose the slice on which the card is configured. The options are OPM 100G or OPM 10 X 10G.
GCC Rate—Choose the GCC rate for the channel.
200G—192K and 1200K
400G—1200K
FEC—Choose the FEC rate.
200G—Standard, HG_FEC_7, or SD_FEC_20.
400G—SD_FEC_15_DE_OFF, SD_FEC_15_DE_ON, SD_FEC_25_DE_OFF, or SD_FEC_25_DE_ON.
Wavelength—Choose the wavelength for the GCC channel.
View the GCC channel added under the GCC once the status of the GCC channel changes to Sync Completed. You can view the status
of the GCC channel from both the Cisco Optical Site Manager web UI and light web UI.
For the light web UI, you can check if the node is provisioned properly under the Summary table.
Now the GCC channel is created from remote to local node and the GCC channel is up.
Add a device
Cisco Optical Site Manager automatically detects and onboards directly connected peer devices on the network. However, if
you've added a new device after configuring Cisco Optical Site Manager, you can manually add the device for management using
the application.
Figure 5. Add a Device
Follow these steps to add an NCS 1000 or NCS 2000 device to Cisco Optical Site Manager.
Feedback