|
|
Traffic mapping |
50 GHz scalability is supported only with {0} design rules. |
Traffic mapping |
Verify if in Add/Drop sites, OADM units are forced and compatible with the traffic. |
Traffic mapping |
No available wavelength due to units forced on optical bypass site {0} |
Traffic mapping |
Verify if in the optical bypass interfaces there are wavelengths compatible units |
Traffic mapping |
The network is broken: please connect all the sites together. |
Traffic mapping |
The traffic model is empty: please add at least one service request. |
Traffic mapping |
Number of add/drop nodes exceeded the maximum ({0}) allowed in the network. |
Traffic mapping |
ONS15454 DWDM platform supports up to {0} non-pass-though sites. |
Traffic mapping |
Line+ sites can't support DMX-O units due to layout constraints. |
Traffic mapping |
Line+ sites can't support Individual Shelf with DCC chain option due to layout constraints. |
Traffic mapping |
Client {0} is not available in the equipment list. |
Traffic mapping |
Any to Any traffic is not supported by {0} rules. |
Traffic mapping |
Can't find a valid path between site {0} and site {1} due to ROADM demand strategy |
Traffic mapping |
Any to Any traffic requires ROADM units but ROADM is not allowed by restricted equipment list. |
Traffic mapping |
Can't place ROADM units in site {0} to support Any to Any traffic. |
Traffic mapping |
ROADM configuration is not allowed by restricted equipment list. |
Traffic mapping |
Mux Demux configuration is not allowed by restricted equipment list. |
Traffic mapping |
Only ROADM configuration is allowed with selected design rules. |
Traffic mapping |
ROADM is not allowed by the selected design rules. |
Traffic mapping |
ROADM-O is not allowed with L band. |
Traffic mapping |
Line+ or Terminal+ site topologies are not allowed by selected design rules. |
Traffic mapping |
Line+ or Terminal+ site topologies require ROADM units but ROADM is not allowed by restricted equipment list. |
Traffic mapping |
OADM unit {0} defined in {1} is not allowed by restricted equipment list. |
Traffic mapping |
Can't find a valid aggregating client. |
Traffic mapping |
Can't find a valid client. |
Traffic mapping |
Client {0} can't be tuned on wavelength {1}. |
Traffic mapping |
Forced wavelength {0} is outside selected band. |
Traffic mapping |
Forced client {0} can't be tuned on selected band. |
Traffic mapping |
Interface Type {0} is not supported by the selected Design Rules. |
Traffic mapping |
Add/Drop not available in site {0}. |
Traffic mapping |
Maximum wavelength re-usage reached for ITU channel {0}. |
Traffic mapping |
All solutions exceed {0} wavelengths. See the "Wavelength Exceeded" section. |
Traffic mapping |
The anti ASE option is available only in sites with add/drop capability. |
Traffic mapping |
More than one anti ASE site was selected. |
Traffic mapping |
Protected services are not allowed with linear networks. |
Traffic mapping |
In a network with hub nodes protected services are allowed only between hub sites. |
Traffic mapping |
Invalid routing (out of network boundary). See the "Invalid Routing" section. |
Traffic mapping |
Can't route service with optical bypass in {0}. |
Traffic mapping |
Can't find alternate route due to multiple HUB nodes along the path. See the "Cannot Find Alternate Route" section. |
Traffic mapping |
Can't route service through HUB node {0}. See the "Cannot Route Service" section. |
Traffic mapping |
Overlapped services assigned to the same wavelength. See the "Overlapped Services Assigned to the Same Wavelength" section. |
Traffic mapping |
Protected services assigned to the same wavelength. See the "Protected Services Assigned to the Same Wavelength" section. |
Traffic mapping |
Can't route service due to add drop equipment constraints. See the "Cannot Route Service Because of Add/Drop Constraints" section. |
Traffic mapping |
Design requires forcing a site as ROADM or Full Mux/Demux but no valid site was found. |
Traffic mapping |
Design requires forcing site as ROADM or Full Mux/Demux: remove equipment constraints. |
Traffic mapping |
Path constraints prevent routing of {0} |
Traffic mapping |
Traffic subnet constraints prevent routing of {0} |
Traffic mapping |
In a linear network, terminal sites must have structure Terminal |
Traffic mapping |
Wavelength {0} may require additional ASE filtering |
Traffic mapping |
50 GHz scalability is supported only with {0} design rules |
Traffic mapping |
The Network is broken: please connect all the sites together |
Traffic mapping |
The traffic model is empty: please add at least one service request |
Traffic mapping |
Number of add/drop nodes exceeded the maximum ({0}) allowed in the network |
Traffic mapping |
ONS15454 DWDM platform supports up to {0} non-pass-though sites |
Traffic mapping |
Line+ sites can't support DMX-O units due to layout constraints |
Traffic mapping |
Line+ sites can't support Individual Shelf with DCC chain option due to layout constraints |
Traffic mapping |
Client {0} is not available in the equipment list |
Traffic mapping |
Any to Any traffic is not supported by {0} rules |
Traffic mapping |
Any to Any traffic requires ROADM units but ROADM is not allowed by restricted equipment list |
Traffic mapping |
Can't place ROADM units in site {0} to support Any to Any traffic |
Traffic mapping |
ROADM configuration is not allowed by restricted equipment list |
Traffic mapping |
WXC configuration is not allowed by restricted equipment list |
Traffic mapping |
Mux Demux configuration is not allowed by restricted equipment list |
Traffic mapping |
Only ROADM configuration is allowed with selected design rules |
Traffic mapping |
Multidegree structure in site {0} is not allowed with selected design rules |
Traffic mapping |
ROADM is not allowed by the selected design rules |
Traffic mapping |
ROADM-O is not allowed with L band |
Traffic mapping |
Line+ or Terminal+ site topologies are not allowed by selected design rules |
Traffic mapping |
Line+ or Terminal+ site topologies require ROADM units but ROADM is not allowed by restricted equipment list |
Traffic mapping |
OADM unit {0} defined in {1} is not allowed by restricted equipment list |
Traffic mapping |
In mesh network user must force OADM units for site configured as OADM |
Traffic mapping |
Can't find a valid aggregating client |
Traffic mapping |
Can't find a valid client |
Traffic mapping |
Can't find a valid XFP |
Traffic mapping |
Client {0} can't be tuned on wavelength {1} |
Traffic mapping |
Forced wavelength {0} is outside selected band |
Traffic mapping |
Forced client {0} can't be tuned on selected band |
Traffic mapping |
Interface Type {0} is not supported by the selected Design Rules |
Traffic mapping |
Add/Drop not available in site {0} |
Traffic mapping |
Maximum wavelength re-usage reached for ITU channel {0} |
Traffic mapping |
All solutions exceed {0} wavelengths |
Traffic mapping |
The anti ASE option is available only in sites with add/drop capability |
Traffic mapping |
More than one anti ASE site was selected |
Traffic mapping |
No specific anti-ASE node is required for this traffic matrix requirement |
Traffic mapping |
Protected services are not allowed with linear networks |
Traffic mapping |
In a network with hub nodes protected services are allowed only between hub sites |
Traffic mapping |
Invalid routing (out of network boundary) |
Traffic mapping |
Can't route service with optical bypass in {0} |
Traffic mapping |
Can't find alternate route due to HUB nodes along the path |
Traffic mapping |
Can't route service through HUB node {0} |
Traffic mapping |
Overlapped services assigned to the same wavelength |
Traffic mapping |
Routing for some of the services cannot be completed with the given constraints. Please use the link aside for details about the problem. |
Traffic mapping |
Protected services assigned to the same wavelength |
Traffic mapping |
Can't route service due to add drop equipment constraints |
Traffic mapping |
Design requires forcing a site as ROADM or Full Mux/Demux but no valid site was found |
Traffic mapping |
Design requires forcing site as ROADM or Full Mux/Demux: remove equipment constraints |
Traffic mapping |
PP4 is not allowed in site {0} (fiber interfaces are limited to A,B,C and D) |
Traffic mapping |
No valid path from {0} to {1} |
Traffic mapping |
No valid path from {0} to {1}, bypass in {2} |
Traffic mapping |
Wavelength forced outside of selected band for {0} |
Traffic mapping |
Client {0} can't be tuned at {1} |
Traffic mapping |
Invalid functionality option for structure {0} in site {1} |
Traffic mapping |
Invalid mux - demux configuration in site {0} |
Traffic mapping |
Invalid mux - demux combination on two sides of site {0} |
Traffic mapping |
Unit options are not compatible with design rule {0} in site {1} |
Traffic mapping |
Unit options are not compatible with design rules in site {0} |
Traffic mapping |
Unit {0} is not available in Restricted Equipment List |
Traffic mapping |
Mesh topology not supported yet |
Traffic mapping |
Network Cluster {0} requires mesh algorithm |
Traffic mapping |
Unconnected site {0} |
Traffic mapping |
Incompatible port {0} assignment in site {1} |
Traffic mapping |
No valid SFP was found for port {0} in site {1} |
Traffic mapping |
Only one GE-STS24 can be assigned to port {0} in site {1} |
Traffic mapping |
Incompatible rate/reach options circuit {0} |
Traffic mapping |
Incompatible rate/reach options for port {0} in site {1} |
Traffic mapping |
Incompatible CIR settings for port {0} in site {1} |
Traffic mapping |
Can't find a valid SFP for port {0} in site {1} |
Traffic mapping |
Port {0} in site {1} is not available |
Traffic mapping |
Exceeded rate for port {0} in site {1} |
Traffic mapping |
Can't provision circuit {0} |
Traffic mapping |
Maximum frame rate exceeded in section {0} - {1} |
Traffic mapping |
Maximum frame rate exceeded in node {0} |
Traffic mapping |
Protected circuits are not allowed in a linear traffic subnet |
Traffic mapping |
Invalid routing {0} |
Traffic mapping |
Client protection is not allowed if all nodes are single card configuration |
Traffic mapping |
Trunk protection with no client protection is not allowed if at least one node is double card configuration |
Traffic mapping |
Client protection with no trunk protection is not allowed |
Traffic mapping |
Errors were found on {0}: please run the checker and fix all problems |
Traffic mapping |
Client and trunk protections are not allowed at the same time on port {0} in site {1} |
Traffic mapping |
50 GHz scalability is not supported with Ethernet or TDM aggregated demands |
Traffic mapping |
Cards required for {0} demand are not available in the equipment list |
Traffic mapping |
Impossible to find two independent paths for protected service |
Traffic mapping |
Structure {0} is not supported for design rule {1} |
Traffic mapping |
No available wavelength found due to traffic constraints |
Traffic mapping |
Too many add/drop nodes ({0} > {1}) in cluster {2} |
Traffic mapping |
Too many nodes ({0} > {1}) in cluster {2} |
Traffic mapping |
Too many ROADM nodes ({0} > {1}) in group {2} |
Traffic mapping |
Demand {0} defined on traffic subnet {1} is in an invalid status |
Traffic mapping |
Demand {0} is crossing different sites clusters |
Traffic mapping |
PP4 forced on site {0} can handle at most 4 sides |
Traffic mapping |
{0} in Any to Any demand doesn't support 50 GHz scalability |
Traffic mapping |
Regeneration not available |
Traffic mapping |
Alien traffic type cannot be regenerated |
Traffic mapping |
Regeneration not allowed |
Traffic mapping |
Regeneration not allowed for PSM-OCH protected demands |
Traffic mapping |
Cards forced in the trails of PRing are not compatible |
Traffic mapping |
L Band Option not allowed with PSM topology |
Traffic mapping |
32MUX-O/32-DMX-O cards are not allowed for PSM configuration |
Traffic mapping |
Optical ByPass not allowed with PSM Config |
Traffic mapping |
Regeneration not allowed with PSM Config |
Traffic mapping |
Only LINE site topology is allowed between PSM config |
Traffic mapping |
Only OLA and Passthrough sites allowed between PSM config |
Traffic mapping |
Only Passthrough sites allowed between PSM Config |
Traffic mapping |
Terminal or Terminal Plus configurations are not allowed for PSM Och protection |
Traffic mapping |
Is not allowed to insert circuit from site {0} to site {1} because is tagged as Omnidirectional Entry Point configuration |
Traffic mapping |
Is not allowed to insert Any to Any Group contains site {0} and site {1} because is tagged as Omnidirectional Entry Point configuration |
Traffic mapping |
No Interoperable group found for the card selection. Please check if its a valid card selection |
Traffic mapping |
All the trails of the P-Ring should have same card |
Traffic mapping |
Restricted Equipment forced by user tm.client_restricted2.details = Client {0} is not available in the equipment list |
Traffic mapping |
Incompatible source and destination |
Traffic mapping |
Forced source and destination cards are not compatible |
Traffic mapping |
Demand cannot be regenerated |
Traffic mapping |
Conflicting trunk mode |
Traffic mapping |
Unfeasible trunk mode forcing by the user |
Traffic mapping |
Cannot force different cards for protection {0} in demand {1} |
Traffic mapping |
Trunk pluggable not found |
Traffic mapping |
No trunk pluggable found for the user forced card |
Traffic mapping |
Unfeasible card mode forcing by user |
Traffic mapping |
OTU2 XP can have both in/out going trunks in EFEC only in Enhanced Regen Mode |
Traffic mapping |
No suitable card found |
Traffic mapping |
Unable to find a compatible card for source or destination |
Traffic mapping |
Alien traffic type cannot be regenerated |
Traffic mapping |
User must force OADM units for sites configured as OADM. |
Traffic mapping |
Mux-Demux should not be forced for site ( {0} ) as it is not supported by the site type. |
Traffic mapping |
For hybrid 216 {0} only FLA8 and MD-40 Mux/Demux is allowed. |
Traffic mapping |
The express loss in the site {0} is High. Please reduce the number of FLAs. |
Traffic mapping |
The add/drop loss in the site {0} is High. Please reduce the number of FLAs. |
Traffic mapping |
We cannot mix hybrid 15216 sites with non-hybrid pure MSTP site {0}. |
Traffic mapping |
We must have atleast one Hub site in a Ring Topology. |
Traffic mapping |
ROADM demands are not allowed with 15216 hybrid network. |
Traffic mapping |
L-Band optical subnet rule is not supported in 15216 network. |
Traffic mapping |
Multiple optical subnets are not supported in single 15216 cluster. |
Traffic mapping |
A 15216 network is capable only till C Band odd 40ch. Please remove any higher capacity selected {0}. |
Traffic mapping |
We cannot force FLA8 {0} in a 40 ch optical subnet. |
Traffic mapping |
Site type Mux/Demux not allowed for {0} in 8 ch optical subnet. |
Traffic mapping |
Optical by pass at {0} is not allowed with 15216 Network. |
Traffic mapping |
PSM Line or Section protection at {0} is not allowed with 15216 network. |
Traffic mapping |
There is an overlap in the Route involving {0}. This may be due to the order of regeneration selected. |
Traffic mapping |
Trunk protection with no client protection is not allowed for selected traffic type. |
Traffic mapping |
ROADM demand is not supported for PSM Line, PSM Section topology. |
Traffic mapping |
Optical Bypass is not allowed in a non Add Drop Site {0}. |
Traffic mapping |
SMR Multidegree site {0} cannot have an omni-direction entry interface. |
Traffic mapping |
SMR Multidegree is not allowed in site {0} (fiber interfaces are limited to A,B,C and D) |
Traffic mapping |
PP-Mesh-4-SMR is restricted. SMR Multidegree is not possible in site {0} |
Traffic mapping |
SMR-1 is restricted. Site {0} type cannot be SMR-1 |
Traffic mapping |
SMR-2 is restricted. Site {0} type cannot be SMR-2 |
Traffic mapping |
Incorrect Client Interface forcing for LAN-WAN Conversion traffic. |
Traffic mapping |
Incompatible Client Interface forcing. |
Traffic mapping |
Y-Cable protection is not allowed with electrical SFP. |
Traffic mapping |
Incompatible trunk Interface forcing |
Traffic mapping |
10G-XR support w/o FEC trunk interface only. |
Traffic Mapping |
Cannot Route demand! Didn't find any colorless ports free. |
Traffic Mapping |
A demand Added or Dropped to a Remote Add/Drop Site cannot be Colorless. |
Traffic Mapping |
This demand is conflicting with the Wavelength {0} with some other new demand.Please unlock the demand and re-analyze. |
Traffic Mapping |
50Ghz design is not allowed for site {0} with Remote Add/Drop. |
Traffic Mapping |
Invalid Structure for {0}. Only Multidegree Site can be OmniDirectional. |
Traffic Mapping |
Cannot Route demand! Didn't find any colorless ports free. |
Traffic Mapping |
Cannot Route demand! Didn't find any valid OmniDirectional Side. |
Traffic Mapping |
OmniDirectional Sides not possible for this protected demand in {0}. Atleast two sides needs to be available. |
Traffic Mapping |
Cannot Route demand! Didn't find any OmniDirectional Side for {0}. |
Traffic Mapping |
OmniDirectional Side not possible in {0}. No Free side left. |
Traffic Mapping |
Optical ByPass is not allowed for OmniDirectional or(and) Colorless Demand. |
Traffic Mapping |
No Colorless Ports found in {1}. Please force the {0} as OmniDirectional or force any Line Side in the site with Colorless Ports. |
Traffic Mapping |
Atleast one colorless port must be forced for demand {0} at {1}. |
Traffic Mapping |
Incompatible configuration with SMR. Please unlock {0}. |
Traffic Mapping |
Unit {0} is not available in equipment list. |
Traffic Mapping |
Demand {0} defined on traffic subnet {1} is in an invalid status. |
Traffic Mapping |
Hybrid layout option is not supported for SMR site types. |
Traffic Mapping |
Raman Amplification is not supported with SMR site types. |
Traffic Mapping |
Side/Side Cabling option should be Auto for SMR2 type in site {0}. |
Traffic Mapping |
Omni-directional interface is not allowed for site type {0}. |
Traffic Mapping |
Omni-directional interface is not allowed for site functionality {0}. |
Traffic Mapping |
Invalid mux-demux forcing. |
Traffic Mapping |
Colorless ports not allowed for site type {0}. |
Traffic Mapping |
0} has only {1} Layer-I Colorless Ports against the needed {2} ports.Please update the forcings. |
Traffic Mapping |
{0} has only {1} Colorless ports available.Layer-II units are not allowed for non-omnidirectional OXC/SMR interface. |
Traffic Mapping |
Site Connected to Remote Spur Duct should be of functionality Add/Drop and type Mux-Demux. |
Traffic Mapping |
Selected functionality or type does not support Remote Add/Drop Port on it. |
Traffic Mapping |
Mux-Demux should not be forced on side ( {0} ) which is not connected to any duct and not forced as omnidirectional. |
Traffic Mapping |
Mux-Demux cards cannot be forced on {0} ,Since second layer cascade is not allowed on {1} site. |
Traffic Mapping |
Forcing of mux/demux is not allowed on {0},since all available add/drop ports has been remotize'd. |
Traffic Mapping |
Forced Site type does not allow to remotize more than {0} add/drop ports. |
Traffic mapping |
Preamplifier setting on {0} is not compatible with M2 chassis type setted on this site. |
Traffic mapping |
Booster amplifier setting on {0} is not compatible with M2 chassis type setted on this site. |
Traffic mapping |
In {0}, OSC-CSM forcing is not compatible with OSC frame type selected. |
Traffic mapping |
[SiteName1], [SiteName 2] Do not have colorless ports. |
Traffic mapping |
[SiteName1], [SiteName 2] Do Do not have 2 Omni Interfaces. |
Traffic mapping |
[SiteName1], [SiteName 2] Do Do not have 1 Omni Interface. |
Traffic mapping |
[SiteName1], [SiteName 2] are not Multi Degree. |
Traffic mapping |
[SiteName1], [SiteName 2] do not have 2 Omni Interfaces with at least 1 colorless port each. |
Traffic mapping |
[SiteName1], [SiteName 2] do not have Omni Interfaces with at least 2 colorless ports each. |
Traffic mapping |
Site is not LINE or LINE plus. |
Traffic mapping |
Chromatic dispersion of the two fibers are not same. |
Traffic mapping |
Chromatic dispersion-L of the two fibers are not same. |
Traffic mapping |
Subnet rules (C Band) of the two fibers are not same. |
Traffic mapping |
Subnet rules (L Band) of the two fibers are not same. |
Traffic mapping |
DCN extension rule of the two fibers are not same. |
Traffic mapping |
OSC Framing rule of the two fibers are not same. |
Traffic mapping |
Fiber type of the two fibers are not same. |
Traffic mapping |
Connection type of the two fibers are not same. |
Traffic mapping |
C-Band option of the two fibers are not same. |
Traffic mapping |
Site has a remote add-drop node connected to it. |
Traffic mapping |
Absolute length loss of the two fibers are not same. |
Traffic mapping |
Raman amp option of the two fibers are not same. |
Traffic mapping |
Measurement unit (e.g. k.m., miles etc.) of the two fibers are not same. |
Traffic mapping |
Cannot Merge Ducts [Duct1] and [Duct 2]. |
Traffic mapping |
Do you want the ducts connected to be merged Click Yes if you want to Merge or else No to delete the Ducts Apply Changes. |
Traffic mapping |
Can only Merge Fibers for Line or Line Plus site [SiteName] is [topology]. |
Network design analysis |
Preamplifier setting on {0} is not compatible with M2 chassis type setted on this site. |
Network design analysis |
Booster amplifier setting on {0} is not compatible with M2 chassis type setted on this site. |
Network design analysis |
In {0}, OSC-CSM forcing is not compatible with OSC frame type selected. |
Network design analysis |
Node {0} is attached to SMR-2 site {1} through an interface tagged as Omnidirectional Entry Point and therefore no amplifier can be forced. |
Network design analysis |
{0} is configured as a Remote Add/Drop side and therefore no amplifier can be forced. |
Network design analysis |
Link {0}-{1} is a remote spur and therefore no amplifier can be forced. |
Network design analysis |
Link {0}-{1} is a remote spur and therefore Raman amplification is not supported. |
Network design analysis |
Link {0}-{1} is a remote spur and therefore DCN must be enabled. |
Network design analysis |
Interface {0} is configured as Omnidirectional and therefore amplifiers cannot be forced as None. |
Network design analysis |
Interface {0} is configured as Omnidirectional and therefore the OSC unit is not allowed. |
Network design analysis |
In {0} is impossible to find an OSC unit that supports selected OSC frame type and site constraints. |
Network design analysis |
Raman amplification is not supported on duct {0}, connecting two hybrid sites. |
Network design analysis |
Some circuit exceeded the maximum number of allowed amplified spans. Please contact Custom Design team for validating the design. |
Network design analysis |
Service type {0} does not allow DCU on its optical path. Please force related DCU positions to NONE. |
Network creation |
Omni-directional side {0} - {1} is not used by any Service Demand. |
Network creation |
Installation parameters for this side cannot be generated; please take corrective actions before loading ANS file to this node. |
Network creation |
Service type {0} does not allow DCU on its optical path. Please force related DCU positions to NONE. |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, 32 channels cards are not supported in WXC site. |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, different design rules for different spans are not supported |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, Line+ node does not support the selected design rule |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, multidegree node does not support the selected design rule. |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, only WXC functionality is supported |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, 40-MUX-C or 40-DMX-C is not supported. |
Amplifier Placement |
In {0}, required {1} is in restricted equipment list |
Amplifier Placement |
In {0}, cannot force a demux if it is not supported by site type. |
Amplifier Placement |
In {0}, cannot force a mux if it is not supported by site type. |
Amplifier Placement |
In {0}, cannot force an in-line attenuator if it is not supported by site type. |
Amplifier Placement |
In {0}, cannot force an in-line attenuator because of presence of OADMs in the other side. |
Amplifier Placement |
Node {0} is set as Pass-through and therefore no hardware or setpoint can be forced |
Amplifier Placement |
Node {0} faces a raman amplified span, forcing not feasible |
Amplifier Placement |
Forcing of Raman on {0} is not compatible with the amplifier forcing done in Node {1}. Please correct the forcings done. |
Amplifier Placement |
Selection of OPT-BST or OPT-BST-E units as pre-amplifier is allowed only if Raman is used on {0}. Please correct the forcings done. |
Amplifier Placement |
Raman Amplifier configuration for {0} is not allowed by restricted equipment list |
Amplifier Placement |
Raman post amp forcing is not allowed for {0} |
Amplifier Placement |
In {0}, OSC card cannot be set to "none" |
Amplifier Placement |
In {0}, cannot force OSCM card in hybrid node |
Amplifier Placement |
In {0}, cannot force output power or tilt setpoint without the related amplifier forced. |
Amplifier Placement |
Invalid forcing in amplifier node of {0} because of Pass-through site forcing. |
Amplifier Placement |
In {0}, cannot force unplaced OSC card in a non Pass-through site. |
Amplifier Placement |
In {0}, cannot force OSCM without an amplifier forced. |
Amplifier Placement |
Cannot force input attenuator in {0} without the related amplifier forced. |
Amplifier Placement |
Cannot force DCUs in {0} without forcing an amplifier that supports them. |
Amplifier Placement |
Incompatible types for DCU couple in {0}. |
Amplifier Placement |
Incompatible dispersion modules in {0} |
Amplifier Placement |
In {0}, output power is out of limits of amplifier selected. |
Amplifier Placement |
In {0}, amplifier tilt is out of allowed range. |
Amplifier Placement |
Couple between {1} and {2} has an invalid value in {0} |
Amplifier Placement |
Couple between {0} and {1} is of invalid type |
Amplifier Placement |
Fiber between {1} and {2} has an invalid value in {0} |
Amplifier Placement |
Fiber between {0} and {1} has SOL total loss greater than EOL total loss. |
Amplifier Placement |
Span {0} is forced as Raman but no traffic is present |
Amplifier Placement |
In {0} interfaces selected for add channels cannot be equalized with 40-MUX-C. |
Amplifier Placement |
Try selecting fewer or more similar interface types, and/or do not use the 40-MUX-C card |
Amplifier Placement |
Can't respect forcing on {0} attenuator (on channel {1}) in {2} {3} {4}. No A/D ports are available |
Amplifier Placement |
Tilt forced on {0} in {1} {2} {3} when no-tilt design option is selected |
Amplifier Placement |
DMX-O is suggested as drop unit in {0} instead of the forced DMX. |
Amplifier Placement |
DMX might cause problems during channels provisioning and or in case of equipment failures. |
Amplifier Placement |
Fail low channel threshold cannot be set in {0} {1} {2}; please allow placement of booster amplifier. |
Amplifier Placement |
In {0}, {1} is working with a gain of {2} dB: this value is below its minimum allowed gain. |
Amplifier Placement |
In {0}, {1} in EOL condition will be working with a gain of {2} dB: this value is below its minimum allowed gain. |
Amplifier Placement |
In {0}, {1} is working with a gain of {2} dB: this value exceeds its maximum allowed gain. |
Amplifier Placement |
In {0}, {1} in EOL condition will be working with a gain of {2} dB: this value exceeds its maximum allowed gain. |
Amplifier Placement |
Site {0} cannot be installed without Cisco Transport Planner configuration file. |
Amplifier Placement |
Unsupported configuration due to excessive number of amplifiers (max {0} per directions). |
Amplifier Placement |
Unsupported configuration due to excessive number of OSC regen sites (max {0}). |
Amplifier Placement |
In {0}, channel power is near the fail low threshold. |
Amplifier Placement |
In {0}, minimum channel power is below the fail low threshold. |
Amplifier Placement |
In {0}, OSC channel power is below the fail low threshold. |
Amplifier Placement |
Network cannot be installed as one or more OSC links are unfeasible. |
Amplifier Placement |
If possible, try selecting DCN extension option on the longest spans. |
Amplifier Placement |
Try to unfreeze amplifier or DCUs in site {0}, interface {1}, {2} position. |
Amplifier Placement |
Transmission error. Please contact custom design. |
Amplifier Placement |
Transmission error on channel {0}. Please contact custom design. |
Amplifier Placement |
Excessive ROADM crossTalk penalty on channel {0}. Try to lower the output power of the preamplifier in the ROADM site in which the failed channels are added. |
Amplifier Placement |
Excessive filtering penalty on channel {0}. Please contact custom design |
Amplifier Placement |
Filtering problem on channel {0}. Please contact custom design |
Amplifier Placement |
Excessive PMD on channel {0}. Please contact custom design. |
Amplifier Placement |
Excessive SC on channel {0}. Please contact custom design. |
Amplifier Placement |
In site {0} the Pass Through forcing and DCN Extension option are incompatible |
Amplifier Placement |
In {0}, DCN Extension option have to be set on both fiber couples facing a Pass-Through node |
Amplifier Placement |
Automatic Node Turn-Up: node {0} mandatory requires preamplifiers (otherwise this node must be set as Pass-Through). |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, amplifier output power cannot be forced. |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, Fiber Switch protection scheme is not supported. |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, only "32 Chs +5 dbm/Ch" and "40 Chs +4 dbm/Ch" design rules are supported. |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, only "32 Chs +5 dbm/Ch" design rule is supported. |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, C + L band upgradeability is not supported. |
Amplifier Placement |
Automatic Node Turn-Up: In {0}, OADM output power cannot be forced. |
Amplifier Placement |
Automatic Node Turn-Up: node {0} cannot be set as OADM full mux/demux. |
Dithering Generation |
Lower Dithering limit ({0}) cannot be less than {1} |
Dithering Generation |
Upper Dithering limit ({0}) cannot be greater than {1} |
Dithering Generation |
Lower Dithering limit ({0}) cannot exceed Upper Limit ({1}) |
Dithering Generation |
Site {0} Dithering value cannot be less than Lower Dithering limit {1} |
Dithering Generation |
Site {0} Dithering value cannot be greater than Upper Dithering limit {1} |
Dithering Generation |
Sites {0} and {1} cannot have the same Dithering value |
Dithering Generation |
Number of available Dithering values {0} cannot be less than number of MultiDegree sites {1} |
Dithering Generation |
Cannot find available Dithering value for site {0} |
Dithering Generation |
Cannot force Dithering value different from 0 in site {0} |
Layout |
MSTP shelves number in site {0} exceeds maximum MultiShelf configuration ({1}) |
Layout |
No linecards placed in Hybrid site {0} optical shelf |
Layout |
Release 4.7/5.0 does not support MultiShelf |
Layout |
No PRE/BST card present with OSCM in site {0} |
Layout |
Layout not feasible for {0} Individual Shelf configuration - No room in the optical shelf to host all the OTS units |
Layout |
No space for DCU: unlock Site {0} layout |
Layout |
Hybrid Layout in Site {0} is allowed with Individual Shelf only |
Layout |
Node protection is not allowed in Terminal Site {0} |
Layout |
DCC Chain in Site {0} is allowed with Individual Shelf only |
Layout |
Node protection in Site {0} is not allowed with Individual Shelf |
Layout |
Cable DB part not identified in Site {0} |
Layout |
Site {0} layout must be unlocked to allow Patch Panel/DCU insertion |
Layout |
Layout in site {0} cannot be built due an internal error. Other reports for the same site may be wrong or incomplete. Please contact support. |
Layout |
{0} site layout must be unlocked to apply modified properties |
Layout |
A/D cards configuration in site {0} is not allowed: please select "Multi Shelf External Switch" or force 32-DMX card |
Layout |
Units equipped in site {0} shelf {1} need FTA4. Please replace current fan tray before equipping the units into the shelf |
Layout |
Only card Layout position can be changed (Site {0}) |
Layout |
Card in Rack {0} - Shelf {1} - Slot {2} cannot be moved to Rack {3} - Shelf {4} - Slot {5} (Site {6}) |
Layout |
Just one move is allowed for Card in Rack {0} - Shelf {1} - Slot {2} (Site {3}) |
Layout |
Cards in Rack {0} - Shelf {1} - Slot {2} and Rack {3} - Shelf {4} - Slot {5} (Site {6}) belong to a YCable Protection Group and must be moved to the same destination shelf |
Layout |
Multidegree topology in site {0} is not supported with Individual Shelf configuration |
Layout |
Y cable protection with GE XP / 10GEXP / GE EXP / 10GE EXP traffic demand in site {0} is not supported with Osmine Configuration |
Layout |
Y cable protection with GE XP / 10GEXP traffic demand in site {0} is not supported with Osmine Configuration |
Layout |
Network not managed by Osmine: Site {0} with WXC and WSS is not admitted. |
Layout |
Layout not feasible for {0} M2 Shelf cannot go in MSM Configuration. |
Layout |
Layout not feasible for {0},M2 chassis is in Restricted List and is forced. |
Layout |
Layout not feasible for {0},M6 chassis is in Restricted List and is forced. |
Layout |
Layout not feasible for {0},M12 chassis is in Restricted List and is forced. |
Layout |
Layout not feasible M12 chassis and M6 Chassis are in Restricted List. |
Layout |
Layout not feasible for Site: {0} and Side: {1},M6 chassis is forced or GE Frame forced but M6 is not supported for the site configuration. |
Layout |
Layout not feasible for Site: {0} and Side: {1},M6 is not supported for the site configuration and M12 Chassis is in Restricted Equipment List. |
Layout |
Extra M2 Shelf cannot go in MSM Configuration for site {0}, hence ignoring additional M2 chassis. |
Layout |
MSM External Configuration for site {0} and M6 Forced, M6 Chassis has integrated MSM capability. |
Layout |
OSC frame type is forced to GE for site {0} and Interface {1}, Power is not sufficient with the available GE Module. |
Layout |
Layout not feasible for {0},Single Controller card doesn't support MSM. |
Layout |
The forced {0} is not compatible with the {1} forced for the {2}. |
Layout |
M2 Chassis cannot have more than one neighbour with ONS 15454 chassis forced. |
Layout |
When M2 chassis is forced, all the connected ducts with only one exception, should have couples forced with valid OSC Frames. |
Layout |
Layout not feasible for {0} with the selected Shelf. |
Layout |
The frame forcings across {0} are not compatible because the site is a passthrough site. The current values will be ignored and best defaults would be chosen. |
Layout |
The OSC frame forcing in the couples connecting the PSM Line {0} need to be same. |
Layout |
The {0} is a OSC regen site hence the connected couples should not have GE frame type forced. |
Layout |
The {0} has OSC-CSM forced which is not compatible with GE frame forcing on the couple in {1}. |
Layout |
The {0} has WSS card with DMX and M2 forced which is not compatible. Analysis not feasable. |
Layout |
MSTP shelves number in site {0} exceeds maximum MultiShelf configuration ({1}). |
Layout |
Racks in site {0} exceeds maximum number of supported Racks({1}). Layout is not built for the site. |
Layout |
No linecards placed in Hybrid site {0} optical shelf. |
Layout |
Release 4.7/5.0 does not support MultiShelf. |
Layout |
No PRE/BST card present with OSCM in site {0}. |
Layout |
Layout not feasible for {0} Individual Shelf configuration - No room in the optical shelf to host all the OTS units. |
Layout |
No space for DCU: unlock Site {0} layout. |
Layout |
Hybrid Layout in Site {0} is allowed with Individual Shelf only. |
Layout |
Node protection is not allowed in Terminal Site {0}. |
Layout |
Node protection is not allowed in PSM Line/Section Site {0}. |
Layout |
DCC Chain in Site {0} is allowed with Individual Shelf only. |
Layout |
Node protection in Site {0} is not allowed with Individual Shelf. |
Layout |
Node protection in Site {0} is not allowed without ADD/DROP. |
Layout |
Cable DB part not identified in Site {0}. |
Layout |
Site {0} layout must be unlocked to allow Patch Panel/DCU insertion. |
Layout |
Layout in site {0} cannot be built due an internal error. Other reports for the same site may be wrong or incomplete. Please contact support. |
Layout |
{0} site layout must be unlocked to apply modified properties. |
Layout |
A/D cards configuration in site {0} is not allowed: please select "Multi Shelf External Switch" or force 32-DMX card. |
Layout |
Units equipped in site {0} shelf {1} need FTA4. Please replace current fan tray before equipping the units into the shelf. |
Layout |
Only card Layout position can be changed (Site {0}). |
Layout |
Card in Rack {0} - Shelf {1} - Slot {2} cannot be moved to Rack {3} - Shelf {4} - Slot {5} (Site {6}). |
Layout |
Multidegree topology in site {0} is not supported with Individual Shelf configuration. |
Layout |
Invalid Alien Shelf Height for site {0}, Alien Shelves Could not be added. |
Layout |
Alien Shelf Height is more than Rack Height for site {0}, Alien Shelves Could not be added. |
Layout |
Unit in the Rack {0} - Shelf {1} - Slot {2} for site {3} requires FAN TRAY 4. |
Layout |
SMR2 in Separate Shelf is not Feasible for Site {0} due to cable unavailable with appropriate length. |
Layout |
Layout not feasible for {0} M2 Shelf cannot go in MSM Configuration. |
Amplifier algorithm |
In {0}, can't force a demux if it is not supported by site type. |
Amplifier algorithm |
In {0}, can't force an inline attenuator if it is not supported by site type. |
Amplifier algorithm |
In {0}, can't force an inline attenuator because of presence of OADMs in the other side. |
Amplifier algorithm |
Invalid forcing in amplifier node of {0} because of Pass-through site forcing. |
Amplifier algorithm |
In {0}, can't force unplaced OSC card in a non Pass-through site. |
Amplifier algorithm |
In {0}, can't force OSCM without an amplifier forced. |
Amplifier algorithm |
Can't force power output or tilt in {0} without the related amplifier forced. |
Amplifier algorithm |
Cannot force input attenuator in {1} without the related amplifier forced. |
Amplifier algorithm |
Can't force DCUs in {0} without forcing an amplifier that supports them. See the "Incompatible DCUs (C-Band)" section. |
Amplifier algorithm |
Incompatible types for DCU couple in {0}. See the "Incompatible DCUs (C-Band)" section. |
Amplifier algorithm |
Incompatible dispersion modules in {0}. See the "Incompatible DCUs (C-Band)" section. |
Amplifier algorithm |
In {0}, MMU presence requires OPT-AMP-L forcing in bst and pre position. See the "MMU Does Not Have Correct Amplifier (L-Band)" section. |
Amplifier algorithm |
In {0}, MMU presence requires OPT-PRE and OPT-BST-E forcing. See the "MMU Does Not Have Correct Amplifier (C-Band)" section. |
Amplifier algorithm |
In {0}, output power setting is not supported by the amplifier. See the "Output Power or Tilt are Out of Range" section. |
Amplifier algorithm |
In {0}, amplifier tilt is out of limits. See the "Output Power or Tilt are Out of Range" section. |
Amplifier algorithm |
Couple between {1} and {2} has an invalid value in {0}. See the "Invalid Fiber Values, Types, and Loss Values" section. |
Amplifier algorithm |
Couple between {0} and {1} is of invalid type. See the "Invalid Fiber Values, Types, and Loss Values" section. |
Amplifier algorithm |
Fiber between {1} and {2} has an invalid value in {0}. See the "Invalid Fiber Values, Types, and Loss Values" section. |
Amplifier algorithm |
Fiber between {0} and {1} has SOL total loss greater than EOL total loss. See the "Invalid Fiber Values, Types, and Loss Values" section. |
Amplifier algorithm |
A {0} attenuator (on channel {1}) in {2} {3} {4} was present, but A/D ports on this channel are no longer available. See the "Unavailable Add/Drop Channels" section. |
Amplifier algorithm |
Tilt forced on {0} in {1} {2} {3} when no-tilt design option is selected. See the "Tilt Forced When No Tilt Design Is Selected" section. |
Amplifier algorithm |
Can't change DMX with DMX-O as needed in {1} because user forcing. See the "Cannot Replace 32-DMX with 32DMX-O" section. |
Amplifier algorithm |
Low threshold on channels power in {0} {1} {2} because passive user forcing on OPT-BST position. |
Amplifier algorithm |
In {0}, {1} is working in an invalid mode. See the "Preamplifier Working in Invalid Mode" section. |
Amplifier algorithm |
In {0}, {1} is working with a gain of {2} dBm: this is too low. See the "Gain Too Low for an Amplifier" section. |
Amplifier algorithm |
In {0}, {1} will be work (in EOL condition) with a gain of {2} dBm: this is too low. See the "Gain Too Low for an Amplifier" section. |
Amplifier algorithm |
In {0}, {1} is working with a gain of {2} dBm: this is too high. See the "Gain Too High for an Amplifier" section. |
Amplifier algorithm |
In {0}, {1} will be work (in EOL condition) with a gain of {2} dBm: this is too high. See the "Gain Too High for an Amplifier" section. |
Amplifier algorithm |
In {0}, {1} cannot respect user forcing. See the "User Forcing Overridden" section. |
Amplifier algorithm |
In {0}, {1} cannot respect user forcing due to {2}. See the "User Forcing Overridden" section. |
Amplifier algorithm |
Unsupported configuration due to excessive number of amplifiers (max {0} per directions). See the "Unsupported Configuration" section. |
Amplifier algorithm |
Unsupported configuration due to excessive number of OSC regen sites (max {0}). See the "Unsupported Configuration" section. |
Amplifier algorithm |
In {0}, channel power is near the fail threshold. See the "Channel Power Near the Fail Threshold" section. |
Amplifier algorithm |
In {0}, channel power is below the fail threshold. See the "Channel Power Below the Fail Threshold" section. |
Amplifier algorithm |
In {0}, OSC channel power is near the fail threshold. See the "Channel Power Near the Fail Threshold" section. |
Amplifier algorithm |
In {0}, OSC channel power is below the fail threshold. See the "OSC Channel Power Below the Fail Threshold" section. |
Amplifier algorithm |
Network unfeasible due to OSC channel. See the "OSC Channel Power Below the Fail Threshold" section. |
Amplifier algorithm |
Try to unfreeze amplifier or dcus in site {0}, interface {1}, {2} position |
Amplifier algorithm |
Transmission error. Please contact custom design. |
Amplifier algorithm |
Transmission error on channel {0}. Please contact custom design. |
Amplifier algorithm |
Excessive ROADM crossTalk penalty on channel {0}. Try to lower the output power of the preamplifier in the Roadm site in which the failed channels are added. |
Amplifier algorithm |
Excessive filtering penalty on channel {0}. Please contact custom design. |
Amplifier algorithm |
Filtering problem on channel {0}. Please contact custom design. |
Amplifier algorithm |
One or more demands present unexpected results at the end of the analysis. Refer to channels errored on system. |
Amplifier algorithm |
Excessive PMD on channel {0}. Please contact custom design. |
Amplifier algorithm |
Node {0} is set as Pass-Through and therefore no hardware or setpoint can be forced |
Amplifier algorithm |
Forcing of tilt in {0} is not allowed in case of Raman amplified span |
Amplifier algorithm |
Forcing of Raman ({0}) is not allowed in PSM Topology. Please correct the forcings done. |
Amplifier algorithm |
In {0} Raman embedded amplifier has dispersion modules with MAL greater then supported |
Amplifier algorithm |
In {0} Raman post amplifier has total dispersion modules with MAL greater then supported |
Amplifier algorithm |
Network analysis must be validated. Please contact custom design. |
Amplifier algorithm |
In network with PSM-Line protection and different fiber types, DCU placement must be validated. |
Amplifier algorithm |
Site {0} connected to duct with DCN extension property enabled must have functionality Add/Drop. |
Amplifier algorithm |
Couple under duct {0} must have DCN extension property disabled |
Amplifier algorithm |
In site {0} between fibers DCN extension, no OSC and no Booster are allowed |
Amplifier algorithm |
In Add/Drop site {0}, OSC cannot be forced since the facing fiber has DCN extension enabled |
Amplifier algorithm |
In Add/Drop site {0} facing a fiber with DCN extension enabled, Booster cannot be forced as None |
Amplifier algorithm |
The DCN path from {0} to {1} contains too many Line Amplifier sites |
Amplifier algorithm |
In interfaces tagged as Omnidirectional Entry Point is not allowed set Mux or Demux |
Amplifier algorithm |
In interfaces tagged as Omnidirectional Entry Point a Terminal site must be connected |
Amplifier algorithm |
Node {0} refers to an interface tagged as Omnidirectional Entry Point and therefore no amplifier can be forced |
Amplifier algorithm |
Node {0} refers to an interface tagged as Omnidirectional Entry Point and therefore no OSC card can be forced |
Amplifier algorithm |
Raman Amplifier module is required in node {0}. Unlock it |
Amplifier algorithm |
Forcing of amplifier in {0} is not allowed in case of Raman amplified span. |
Amplifier algorithm |
Node {0} faces a raman amplified span, only OPT-BST unit can be forced. |
Amplifier algorithm |
Span {0} must be configured as Raman to allow Raman amplifier {1} in node {2}. |
Amplifier algorithm |
Forcing of Raman on {0} is not compatible with the amplifier forcing done in Node {1}. Please correct the forcings done. |
Amplifier algorithm |
Selection of OPT-BST or OPT-BST-E units as pre-amplifier is allowed only if Raman is used on {0}. Please correct the forcings done. |
Amplifier algorithm |
Raman Amplifier configuration for {0} is not allowed by restricted equipment list. |
Amplifier algorithm |
Raman post amp forcing is not allowed for {0} |
Amplifier algorithm |
Node {0} faces a raman amplified span, only OPT-BST unit can be forced. |
Amplifier algorithm |
Span {0} must be configured as Raman to allow Raman amplifier {1} in node {2}. |
Amplifier algorithm |
Forcing of Raman on {0} is not compatible with the amplifier forcing done in Node {1}. Please correct the forcings done. |
Amplifier algorithm |
Selection of OPT-BST or OPT-BST-E units as pre-amplifier is allowed only if Raman is used on {0}. Please correct the forcings done. |
Amplifier algorithm |
Raman Amplifier configuration for {0} is not allowed by restricted equipment list. |
Amplifier algorithm |
Raman post amp forcing is not allowed for {0} |
Amplifier algorithm |
Span {0} is forced as Raman but no traffic is present. |
Amplifier algorithm |
In {0} is not allowed forcing a booster or setting DCN extension enabled. |
Amplifier algorithm |
In Add/Drop site {0} facing a fiber with DCN extension enable, OSC cannot be forced |
Amplifier algorithm |
Site {0} is facing spans with different optical design rules: an Add/Drop functionality is required. |
Amplifier algorithm |
{0} is an hybrid 15454 MSTP site : selection of OPT-BST or OPT-BST-E units as pre-amplifiers is not allowed. |
Amplifier algorithm |
Span is too short for Raman amplification. If possible, lower the output power setpoint of the booster. |
Amplifier algorithm |
Raman optical amplifiers are not available in L Band. |
Amplifier algorithm |
In {0} is not allowed forcing a pre-amplifier or setting DCN extension enabled. |
Amplifier algorithm |
In {0}, cannot force OSCM card without an amplifier or SMR forced. |
Amplifier algorithm |
Forcing of T-DCU on both {0} is not allowed.Please remove T-DCU forcing either from {1}. |
Amplifier algorithm |
{0} - side{1} is connected to a span not used by any Service Demand. |
Amplifier algorithm |
In multidegree site {0} configured as SMR2 type with Individual Shelf, only first two sides can have OSC-CSM unit forcing. |
Amplifier algorithm |
{0} has OSC functionality : side {1} can't face a fiber with DCN extension enabled. |
Amplifier algorithm |
Raman amplification is not supported on duct {0}, connecting two hybrid sites. |
Amplifier algorithm |
Some circuit exceeded the maximum number of allowed amplified spans. Please contact Custom Design team for validating the design. |
Layout messages |
MSTP shelves number in site {0} exceeds maximum MultiShelf configuration (12). |
Layout messages |
No linecards placed in Hybrid site {0} optical shelf. |
Layout messages |
Release 4.7/5.0 does not support MultiShelf. |
Layout messages |
No PRE/BST card present with OSCM in site {0}. |
Layout messages |
Layout not feasible for {0} Individual Shelf configuration - No room in the optical shelf to host all the OTS units. |
Layout messages |
No space for DCU: unlock Site {0} layout. |
Layout messages |
Hybrid Layout in Site {0} is allowed with Individual Shelf only. |
Layout messages |
Node protection is not allowed in Terminal Site {0}. |
Layout messages |
DCC Chain in Site {0} is allowed with Individual Shelf only. |
Layout messages |
Node protection in Site {0} is not allowed with Individual Shelf. |
Layout messages |
Cable DB part not identified in Site {0}. |
Layout messages |
Site {0} layout must be unlocked to allow Patch Panel/DCU insertion. |
Layout messages |
Layout in site {0} cannot be built due an internal error. Other reports for the same site may be wrong or incomplete. Please contact support. |
Layout messages |
Y cable protection with GE XP / 10GEXP traffic demand in site {0} is not supported with Osmine Configuration |
Layout messages |
Network not managed by Osmine: Site {0} with WXC and WSS is not admitted. |
Layout messages |
Invalid Alien Shelf Height for site {0} , Alien Shelves Could not be added. |
Layout messages |
Alien Shelf Height is more than Rack Height for site {0} , Alien Shelves Could not be added. |
Layout messages |
SMR with Raman Amplification is Not Supported on Side {0} for Site {1}. |
Layout messages |
SMR2 in Separate Shelf is not Feasible for Site {0} due to cable unavailable with appropriate length. |
Generic |
Error deleting site- generic, cannot be classified. |
Generic |
At least one optical bypass point is defined in this site. The site can not be deleted until the optical bypass is removed. |