You are on page 1of 57

SCHEDULE OF COMPLIANCE

Clause No /
Item
Sub-Clause No. 

 Section-6 (A)

Bangladesh Telecommunications Company Limited (BTCL) intends to have a high capacity optical
fiber transmission network covering several important locations of Bangladesh, which will be able
to provide service in multiple fiber cut scenario for increased reliability and have maintenance
opportunity to reduce downtime. To do so, the scope under this tender is to supply high capacity
 6.1 (100G per lamda) DWDM optical transmission equipment using Reconfigurable Add Drop
Multiplexer (ROADM), Optical Line Amplifiers (OLA) with associated material and services at
different locations of Bangladesh with Protection and Restoration facility using Layer 0 (L0)-
ASON/GMPLS/Optical ASON along with inbuilt Optical Time Domain Reflectometer (OTDR)
Facility.

 6.2 For this purpose, following types of DWDM and OLA equipment along with related auxiliary
equipment are to be supplied, installed and commissioned.
 6.3

In order to achieve the intended goal of the purchaser, Bidder during designing and configuring the equipment at each site
shall follow the following fundamental rules;
- Fixed Optical Add Drop Multiplexer (FOADM) is not allowed in the network.
- For line side, Optical Channel (Och) of only 100G lamda will be used.
- Line signal Protection and Restoration facility must be implemented.
- Automatically Switched Optical Network (ASON) must be implemented using Layer 0 (L0)ASON/GMPLS/Optical
ASON for Restoration.
- Regeneration of line signal in between Source and destination node (Anywhere in between the Main, Protection and
restoration paths) is not allowed.
- Use of external Dispersion Compensation module is not allowed.
- Line and Client ports must be on separate cards.
- Inbuilt OTDR functionality must be provided for all fiber connectivity between all nodes.

Any disagreement/deviation will be treated as “Material Deviation” and/or “Reservation”.

The network topology with all nodes and fiber connectivity with approximate distance and total
dB loss (maximum value) between the nodes are given in Annex-1 and Annex-3 of Section 8
 6.4 (Network Topology with Distance and dB Loss). The fiber connections between the nodes are
shown in two different colors. Blue color represents one pair of fiber of BTCL. Red color
represents that, the pair from other operator i.e PGCB.

The requirements of different Line and client interfaces of the DWDM equipment at different
 6.5 sites are given in Annex-2 of Section 8 (Requirements of different Line and client interfaces of
different sites).

Requirements for minimum Optical link Margin between Hops


For the planning and design of the network and choice of different line cards and amplifiers,
 6.6 bidder has to consider minimum margin of 3 dB for each adjacent hop on top of the db loss
mentioned in Annex-1 and Annex-3 of Section 8.
Any disagreement/deviation will be treated as “Critical Deviation”.

Bidder will quote the DWDM equipment for the all the ROADM and OLA nodes complying
6.7 technical specifications specified in Section 7 and will design and equip as specified below.
Requirements for DWDM Equipment Design

a) Each node will be equipped with:

1) Flexgrid Och Add/Drop Mux with at least No. of Ports according to Traffic Matrix at each
node expandable up to minimum 80/96 Channels
2) Required no. of WSS (8 Port or higher), Amplifier, OSC, OPS etc. equipped in optical sub-
racks.
3) Required no. of Line cards (Transponder), Client cards, OTN Switch (If used) equipped in
same optical sub-racks or separate sub racks.
4) Required no. of cards/hardware for OTDR functionality.
5) Necessary software.
Where,
6) All sub-Rack must have power redundancy.
7) All Sub-Rack must have controller redundancy.
8) OTN switch (If used) must haver redundan
9) Line and client ports may be in separate or same card but in any case, main and protection
channel (Och) must be connected through minimum two distinct optical add-drop facility at each
6.7.1 node i.e. Onbe for Main and one for protection path.

b) The offered equipment must be equipped with all necessary hardware and software to
provide line side protection and restoration facility through fiber connectivity given in Annex-1
and Annex-3 of Section 8 (Network Topology with Distance and dB Loss) for all the Line signals
specified in Annex-2 of Section 8 (Requirements of different Line and client interfaces of different
sites).
c) The offered Line card/Transponder should have reach, Dispersion Tolerance, OSNR to travel
through the longest possible path/link so that no regeneration of line signal in between Source
and destination node of traffic (Anywhere in between the Main, Protection and restoration
paths) is required in all possible Restoration scenario and no dispersion compensation module is
required.

d) The offered equipment must be equipped with necessary hardware and software for OTDR
functionality.
Any disagreement/deviation will be treated as “Critical Deviation” individually for each sub-
clause.

Service (Traffic) requirements

DWDM network service demands are defined at 10G/10GbE/100GE client service rate level and
mentioned in Annex-2 (Requiremnts of Different Line and Client interfaces of different Sites) of
6.7.2 Section 8. Bidder must equip and qoute necessary SFP/XFP/CFP/optical interface module
accordingly to the service requirement. Optical module of client side should be minimum 10KM
of length.
Any disagreement/deviation will be treated as “Critical Deviation”.
Requirements of Network Protection and restoration
a) To cope with simultaneous multiple failures both protection and restoration functionalities
shall be provided.
b) Line side protection to handle the 1st break (Optical Fiber/equipment failure) must be done
6.7.3 in an automatic manner within the maximum 50 ms delay excluding failure detection time.
c) For the 2nd break and/or consecutive break, restoration is required in an automated
manner as long as a single routing path is available.
Any disagreement/deviation will be treated as “Critical Deviation”.

Submission of BOQ of DWDM Equipment

Besides Form PG4-3A or PG4-3B or PG4-3C, Bidder must submit Summary price and quote with
Detail Bill of Quantity (BoQ) of all DWDM equipment with ancillary items (i.e. Rack, 4X30m 25rm
6.7.4 DC Cable etc. for each site) and related software site wise in Form C.1x, which will be added and
quoted in Form B.1 and finally added and quoted in Form A. The forms are provided in Section 7.
Any disagreement/deviation will be treated as “Critical Deviation”.

Requirements for NMS Design

The NMS consisting Main server and standby Server and 1 (One) client hardware along with any
switch/router required and all necessary software will be quoted and installed/commissioned at
Moghbazar site. Bidder will also quote and supply 1 (One) Laptop (Craft Terminal) with
appropriate software to connect DWDM equipment directly so that configuration, monitoring can
be done from the Laptop.
6.8.1
a) Minimum number of NE handling by NMS shall be 50 (Fifty) Nodes for DWDM Equipment.
b) Minimum number of WS (Client) can be connected to NMS shall be 5 (Five).
c) Minimum 5 (Five) users can login a server and work simultaneously.
d) Minimum 20 (Twenty) Performance measurement can be initiated in the system and data
can be recorded simultaneously.

Any disagreement/deviation will be treated as “Critical Deviation”.


NMS Hardware Requirement
Bidder will quote NMS hardware will minimum specification.
NMS Server Specifications:
Processor : 2*Xeon E5-2680 v4 2.4GHz;
Memory : 64 GB
Hard Disk : As necessary
Other drives : As necessary
Equivalent or better to meet the requirement

Client Specifications:
CPU : Intel I5;
6.8.2 Memory : 8 GB RAM;
Hard Disk : As necessary
Other drives : As necessary

Equivalent or better to meet the requirement


Laptop (LCT) Specification:

CPU : Intel I5;


Memory : 8 GB RAM;
Hard Disk : As necessary Other drives : As necessary
Monitor : 14” LED monitor or higher
Other Facility : WiFi, Bluetooth,etc
Equivalent or better to meet the requirement
Any disagreement/deviation will be treated as “Critical Deviation”.

Submission of BOQ of NMS Equipment and Software


Besides Form PG4-3A or PG4-3B or PG4-3C, Bidder must submit Summary price and quote with
6.8.3 Detail Bill of Quantity (BoQ) of all NMS equipment along with related ancillary items and related
software in Form C.2, which will be added and quoted in Form B.2 and finally added in Form A.
The forms are provided in Section 7.
Any disagreement/deviation will be treated as “Critical Deviation”.

7
7.1 Introduction
This Section describes the technical specifications for Optical Fiber Platform of Dense Wavelength
Division Multiplexing (DWDM) technology (DWDM equipment) operating at discrete wavelengths
in the C-band centered around 193.1 THz frequency as per ITU-T Rec.G.694.1 grid, at 50GHz/100
GHz channel spacing. The DWDM system shall have 100
Gb/s transmission on line side or higher bandwidth per channel in the C-band. The 10GE and
10Gbps shall be supported simultaneously on the client side with no changes to the common
equipment at the optical layer.

The Specifications in this section covers the technical requirements of Optical Fiber Platform of
Dense Wavelength Division Multiplexing (DWDM) technology (DWDM equipment) on single
mode optical fibers conforming to ITU Rec. G. 652D. The key requirement is to transmit
bandwidth efficiently that can be achieved with WDM deployments considering the following
requirements:

a) High capacity transport.


b) 10 Gbps / 10 GE / 100 GE Multiplexing and grooming capabilities
7.1.1 c) End to End transparency
d) Without requirement of any Regeneration of line signal (Minimum 100G per lamda) in
between Source and destination node (Anywhere in between the Main, Protection and
restoration paths).
e) Without requirement of using any Dispersion Compensation module.
f) Capable of implementing Protection and Restoration mechanism using Layer 0
(L0)ASON/GMPLS/Optical ASON for increased service availability and decreased downtime.
g) Having inbuilt OTDR functionality.
h) Same Type/Unique type of 100G Line Card should be offered in this Tender.
i) Same Type/Unique type of 100G Client Card should be offered in this Tender.
j) Same Type/Unique type of 10G Client Card should be offered in this Tender.
k) Same Type/Unique type of WSS Card should be offered in this Tender.
l) Same Type/Unique type of OTDR Function Card should offered in this Tender.
m) OLA Backplane/Shelf/Chassis should be same as ROADM Backplane/Shelf/ Chassis so that in
future 100G Line Card, 100G Client Card, 10G Client Card, WSS Card, etc can be inserted. OTDR
Function Card must be inserted in OLA system.

Any disagreement/deviation will be treated as “Critical Deviation”.

7.2 DWDM SYSTEM


The DWDM equipment/system shall conform to the following ITU-T and IEEE Recommendations. The latest
version of ITU-T and IEEE Recommendations at date of contract signature will also be considered.

a) G.661 ‘Definitions and test methods for the relevant generic parameters of optical amplifier devices
and subsystems’
b) G.662 ‘Generic characteristics of optical amplifier devices and subsystems’
c) G.663 ‘Application related aspects of optical amplifier devices and subsystems’
d) G.667 ‘Characteristics of adaptive chromatic dispersion compensators’
e) G.671 ‘Transmission characteristics of optical components and subsystems’
f) G.672 ‘Characteristics of multi-degree reconfigurable optical add/drop multiplexers’
g) G.681 ‘Functional characteristics of interoffice and long-haul line systems using optical amplifiers,
including optical multiplexing’
h) G.692 ‘Optical interfaces for multichannel systems with optical amplifiers’
7.2.1 i) G.693 ‘Optical interfaces for intra-office systems’
j) G.694.1 ‘Spectral grids for WDM applications: DWDM frequency grid’
k) G696.1 ‘Longitudinally compatible intra-domain DWDM applications’
l) G.709 ‘Interfaces for the optical transport network ‘
m) G.783 ‘Characteristics of synchronous digital hierarchy (SDH) equipment functional blocks’
n) G.798 ‘Characteristics of optical transport network hierarchy equipment functional blocks’
o) G.806 ‘Characteristics of transport equipment - Description methodology and generic functionality’
p) G.8251 ‘The control of jitter and wander within the optical transport network (OTN)
q) IEEE 802.3ba ‘Media Access Control Parameters, Physical Layers and Management
Parameters for 40 Gb/s and 100 Gb/s Operation’
r) G.8080/Y.1304 ‘Architecture for the automatically switched optical network’
s) RFC 3945 ‘Generalized Multi-Protocol Label Switching (GMPLS) Architecture’
Any disagreement/deviation of each of the above recommendations will be treated as “Major Deviation”.
General Features of the DWDM system

i. The equipment shall implement 100GB/100GBE on line side and 100GB/100GBE or 10GB/10GBE on client side according to the traffic matrix.
iii. The equipment must support the WSS and implementation of GMPLS (RFC 3945) and/or ASON (ITU-T G.8080) for restoration requirement in the offered model and sub-rack.
The GMPLS/ASON control plan is adopted in Optical Channel (Och) scenarios. iv. The equipment shall have plan/concrete roadmap of inter-working with the IP/MPLS routers. The
inter-working should base on ITU-T, IETF, and OIF standards.
v. The DWDM network sahll be based on minimum 100G line per channel with Flexgrid Och Add/Drop Mux with required No. of Ports according to Traffic Matrix at each
node expandable up to minimum 80/96 Channels
vi. The DWDM equipment shall support non-blocking ROADM architecture.
vii. The Client ports and line (Transponder) ports may be on seperate cards and shall be connected through backplane or line and client port may be in same card provided all
thechnical requiremnt of line port and client port stated in the tender document is/are complied.
viii. Equipment should support multiple protection architecture based on OCH/OMS or OTS with optical switching module or OTN switch, having protection switching
achieved within 50ms.
ix. Both Line side and Client-side protection must be possible.
x. The line card (Transponder) must be able to sync fast enough so that effective switching time from main to protection path does not exceed 50ms. Service-level switching
time must not exceed 50ms neither for line side protection switching nor for client side protection switching.
xi. Wavelength Grid and DWDM system capacity shall be, as defined in ITU-T recommendation G.694.1 Wavelength channel spacing, should be flexible (flexi grid
supported).
xii. The OSC (optical supervisory channel) channel and service channel must be separated and OSC channel shall not be amplified.
xiii. The DWDM system shall have the modularity and scalability of at least 80/96 ch (system architecture for Point-to-Point, ring and mesh network application). From day
one flexgrid add/drop MUX with required number of ports accordingly to the traffic matrix of the node must be configured which is expandable up to minimum 80/96 channels
per node.
7.2.2 xiv. The line card (Transponder) must be software tunable type and can be tuned to any of 80/96 channels on Standard and offset ITU-grid within the full C band spectrum.
xv. The line card (Transponder) must be flexi rate modules capable to support modulation with bandwidth of 100 Gbps or 200 Gbps on line side and the transmission rate
should be software configurable.
xvi. The supplier's solution shall support WSS/ROADM architectures for wavelength grooming with reference topology for 50 GHz / 100 GHz operation.
xvii. The DWDM system shall support and provide all type and capacity of WSS (ROADM) to Re-Route any optical Channel from any path to any path among all paths
connected to that node (For all possible restoration paths).
xviii. DWDM system shall support Remote NMS Reconfiguration, at least 80/96 Och reconfiguration with access to all channels and switching between common port and
switched ports.
xix. The DWDM system shall support a modular and flexible architecture, in order to allow scaling, the equipment in accordance to the network requirements. xx. Optical
equipment should be able to cater the required link Budget (Total loss of cable at each span) along with 3 dB (On top of cable loss) margin for each span.
xxi. It shall be possible to equip the DWDM system progressively, in accordance to the number of wavelengths transmitted, in order to allow real “pay as you grow”
configurations.
xxii. The DWDM system shall be in-service upgradeable from one wavelength up to its maximum wavelength capacity.
xxiii. The proposed DWDM system should be able to ensure hitless in-service insertion of new channels or removal of channels, with ability to automatically adjust/tune.
xxiv. The DWDM system shall support Automatic Power Equalization (APE). The system shall be capable of automatically adjusting power per channel to its optimum value, if
and when channels are added or removed without the need for manual adjustment.
xxv. The DWDM system shall support all type of architecture i.e. Optical Terminal Multiplexers (OTM), Reconfigurable Optical Add and Drop Multiplexers (ROADM), sharing
the common modules, in order to minimize the number of spares.
xxvi. The DWDM system shall support Protection and subsequent restoration of traffic using Layer 0 (L0)-ASON/GMPLS/Optical ASON. xxvii. The DWDM system shall support
OTDR functionality and able to measure without impacting traffic while DWDM system is in service.

Any disagreement/deviation will be treated as “Critical Deviation” individually for each subclause.

Requirements of Online System Performance Monitoring

a) The DWDM equipment system shall have the capability to monitor system performance
online without circuit interruption.
b) The DWDM equipment system shall support monitoring and estimating OSNR, measure
7.2.3 optical power of each channel. Operator shall be able to view the related data in NMS.
c) The DWDM system shall support OTDR functionality. Operator shall be able to view the
related data in NMS.
Any disagreement/deviation will be treated as “Critical Deviation” individually for each subclause.
Requirements of the OTU

a) Access service: Support 100GbE, 10 Gb (STM-64) and 10GbE.


b) 100GbE overhead processing shall conform to the IEEE802.3ba standard.
c) Optical interface of OTU S/R side shall meet one or more optical interface standard defined in ITU-T
G.691, ITU-T G.693, ITU-T G.959.1, and IEEE 802.3ba, 10 × 10 MSA technical specifications.
d) 10xSTM-64 multiply to 100 Gb/s
1) Optical interface for client shall support the transparent transmission of 10 Gb/s. The wavelength from
output in the line side shall meet the standard of ITU-T G.694.1.
2) Branch route optical interface shall possess the ability to intercommunicate with the optical interface
using the same standard from other manufacturers.
e) 10x10GbE multiply to 100 Gb/s
7.2.4 f) The proposed system shall comply GFP mapping according to ITU-T G.7041 and the bidder shall
describe its support to the following Ethernet encapsulation schemes referencing the offered 10G/100G
Transponders/Muxponders as applicable. Moreover, the bidder shall clarify if the mapping of Ethernet to
OTN is according to G.709 and if both GFP-F and GFPT mapping options are available, emphasizing the
benefits of the supported encapsulation scheme.
10 GbE into ODU2e in timing transparent manner
g) The bidder shall describe their solution for mapping 10GE LAN PHY/10GE WAN PHY to ODU-2.
h) The bidder's solution shall support 10 x STM-64 / 10GBE LAN PHY / 10GE WAN PHY signals mapped into
ODU4.
i) The bidder's solution shall support STM-64 / 10GE signals mapped into ODU4.

Any disagreement/deviation will be treated as “Major Deviation” individually.

Requirement of OADM

OADM shall have the following basic functions:

b) Support add/drop of wavelength of 100Gb/s single channel rate;


c) The operation of drop wavelength shall not affect pass through /straightway wavelengths;
d) In case of upstream optical fiber broken, it will not affect the normal work of the downstream business;
7.2.5 e) In case that addition of new channels is required in DWDM node, the addition should not
influence/stop service, performance and function in existing channels.
f) Optical amplifiers such as pre amplifier, booster can be used, if necessary.
g) The maximum transporting distance (reach of line card/transponder) needs to be sufficient to cover the
BTCL’s longest path requirement in BTCL SMF.
h) Optical amplifier needs to compensate the loss of optical power according to type of use.

Any disagreement/deviation will be treated as “Major Deviation”.

Requirements of safety
a) Laser, optical fiber amplifier have the obvious safety signs to ensure personal safety. The
7.2.6 system is certified as a Class 1M laser product with hazard level 1M according to the IEC 60825-1
and IEC 60825-2.
b) When the fiber is disconnected, according to the recommendations of the G.664 to support
the APR function, and has automatic / manual restart process.
Automatic gain equalization and automatic power control requirements

a) Must have automatic gain equalization and automatic power control function.
b) The process of Channel power dynamic control does not affect the other channel which is
adjusted and the work of online business service.
7.2.7 c) N x 100 Gb/s DWDM system can support the function of line power dynamic adjustment
which does not influence the regular working service.
d) Increase/decrease the channel without interrupting the business service.
e) Automatic equalization function can realize the dynamic adjustment.
f) The equipment shall support in-service gain/tilt adjustment without interruption of service.
Any disagreement/deviation will be treated as “Critical Deviation” individually for each subclause.
Protection Requirement
a) The system must support Optical Line Active/Protection switching using Optical Protection
switch (OPS) or OTN switch.
b) In any case, the switch time of Optical Line Active/Protection switching should be no more
than 50ms excluding the detection time.
c) It should be easily managed by same NMS system as DWDM equipment and other optical
card (amplifier card, MUX/DEMUX card etc.).
d) Protection switch of all traffic shall be triggered on optical power monitoring and there shall
be provision to set the LOS thresholds.
7.2.8 e) Automatic switching shall be triggered by line faults (LOS, LOF etc.), OCh layer faults.
f) The switching priority of Optical Line Active/Protection switching should support functions
like Clear Switching, Forced Switching, Automatic Switching.
g) Revertive operation must be provided.
h) Non-revertive operation must be provided.
i) Provisionable "generic hold-off function" must be provided.
j) Lockout of protection and forced switch commands shall be supported.
k) The system should have the fault notification function in order to notify the external
terminal equipment connecting to downstream system of fault occurred on the Network

Any disagreement/deviation will be treated as “Critical Deviation” individually for each subclause.
Restoration Requirement
a) For Restoration, all OADM sites must be able to Re-Route Optical Channels. Re-routing will
be possible from any path to any path among all paths connected to that node.
b) Restoration path from source node to destination node must be created automatically.
c) The system must be able to create consecutive restoration paths one after another at
multiple fiber cut scenario, as long as a single path is available between the two nodes.
d) The solution shall support and provide all type and capacity of WSS (ROADM) to Re-Route
any optical Channel from any path to any path between all paths connected to that node.
e) The equipment must support the WSS and implementation of GMPLS (RFC 3945) and/or
ASON (ITU-T G.8080) for restoration requirement in the offered model and sub-rack. The
7.2.9 GMPLS/ASON control plan is adopted in Och scenarios.
f) The control plane should support automatic discovery of the network topology and network
resources.
g) ASON/GMPLS should support the calculation of the source node route.
h) Restoration will be possible without requirement of any regeneration of line signal in
between Source and destination node.
i) The transmission system shall give alarm or indication to router/switch to stop
transmission/packet forwarding on 10GbE ports of transmission Ethernet card, if there is link
down between transmission media due to fibre cut or some fault.

Any disagreement/deviation will be treated as “Critical Deviation” individually for each subclause.

OTDR Function Requirement

DWDM system must have OTDR function. Following parameter must be complied.
a) Operating Wavelength: Any or multiple wavelength between 1500 nm to 1650 nm. b)
Resolution: ±3 meter
7.2.10 c) Should measure at least 20 dB per direction.
d) Measure from both sides into same fiber.
e) OTDR measurements should be possible while DWDM system is in service.
f) OTDR measurements should be done without impacting traffic while DWDM system is in
service.
g) No extra optical fibre core will be required or allocated for OTDR function.
Any disagreement/deviation will be treated as “Critical Deviation” individually for each subclause.

Availability

7.2.11 The system availability shall be higher than 0.99999.


Any disagreement/deviation will be treated as “Major Deviation”.
HW Resiliency

a) The solution will be of modular chassis architectures.


b) The solution must support insertion, replacement and removal of modules whilst the
equipment is powered up without affecting traffic and / or damaging any module.
7.2.12 c) Each shelf shall have individual shelf control card.
d) The solution shall provide indications on each individual module to indicate a failure of the
module.
e) The equipment shall also have an alarm display showing at least major and minor summary
alarms.
Any disagreement/deviation will be treated as “Major Deviation”

SW Resiliency

a) The supplier shall indicate if control and forwarding parts are separated (autonomous) and if
a control failure does affect (or not) the forwarding part.
b) The supplier shall confirm that SW upgrade and SW patches can be performed without any
service interruption and that its solution supports the upgrade of all operating software without
7.2.13 any traffic interruption.
c) Regarding in-service configuration backup and restore features, the supplier shall confirm
that its solution has the capability to batch download software and firmware and switch in bulk.
d) The supplier shall confirm that their solution is capable of autonomous operation, without
assistance from the Management System.

Any disagreement/deviation will be treated as “Major Deviation”.

Synchronization

7.2.14 a) The system must support clock recovery and stamping based on NTP.

Any disagreement/deviation will be treated as “Major Deviation”.

Optical supervisory channel (OSC)

a) Must have separate optical supervisory channel.


b) The wavelength of optical supervisory channel is 1510nm ± 10nm.
7.2.15 c) The BER performance of optical supervisory channel should be in the range of 1.0Exp (-3) to
1.0Exp (-12).
d) The failure and replacement of filters units cannot affect the DCN communication via OSC.
e) The failure of an OSC unit must be non-traffic affecting.
Any disagreement/deviation will be treated as “Critical Deviation”.

Environmental Requirements

The DWDM equipment shall satisfy the following environmental conditions


7.2.16 a) Ambient temperature: 0°C to 45°C for the DWDM.
b) Relative humidity: Up to 85% at non-condensing for the DWDM.
Any disagreement/deviation will be treated as “Critical Deviation”.
Power Requirements

7.2.17 For the DWDM equipment, the input voltage will be -48 VDC (-60 ~ -42).
Any disagreement/deviation will be treated as “Critical Deviation”.

Requirements of system reliability

a) Flexgrid Och Add/Drop Mux with least No. of Ports according to Traffic Matrix at each node
expandable up to minimum 80/96 Channels
b) The Optical (photonic) part i.e. WSS, Amplifier, OSC, OPS etc. must be equipped in optical
sub-racks.
c) Line cards (Transponder), Client cards, OTN Switch (If used) can be equipped in separate sub
racks from the optical sub-racks.
7.2.18 d) Line port and client port must be on separate cards.
e) All sub-Rack must have power redundancy.
f) All Sub-Rack must have controller redundancy.
g) OTN switch (If used) must have redundancy.
h) All the ports in any type of card and or device be active or passive must be useable instantly
when required without any further requirements of related software/license.
Any disagreement/deviation will be treated as “Critical Deviation”.

Requirement of Encryption facility at Client Port


7.2.19 Bidder shall offer price for encryption facility of 100G client port and 10G client port to the client
port as optional
Network Management System
The Network Management System (NMS) solution for the monitoring and management of the
devices and network is required. The NMS shall be fully centralized for management of all
network elements (NE), offering the possibility to perform network management tasks from
single site or several sites. The NMS shall be of Server and clients-based architecture.

7.3 The NMS system shall be provided with user-friendly interfaces based on Unix and/or Linux
and/or windows operating system. The NMS shall be able to provide an on-screen view of the
managed network.
It shall be possible to access any managed NE from the whole network in the managed domain.
The NMS shall be able to depict the failure state of each link and node in the displayed network.
Further, it shall be possible from the NMS system to get the details of status of an individual
managed NE, such as equipment presence, settings, alarm status etc.

It shall be possible to add/delete/configure/modify a NE by point & click feature.

Management Facility

The following Management facilities must be provided:


a) Fault Management
b) Configuration Management
c) Inventory Management
7.3.1 d) Security Management
e) Alarm & Event Management
f) Performance Management
g) Software upload/download capability
h) Backup and Restoration Management of all NE

Any disagreement/deviation will be treated as “Critical Deviation”.

Visualization of Network domain


a) NMS shall provide end-to-end visualization of wavelength paths
b) NMS shall provide end-to-end display of optical power measurements
7.3.2 c) NMS shall provide for details for end-to-end wavelength channel provisioning and
automated wavelength channel restoration.
d) NMS shall provide visualization of OTDR report of fiber spans.

Any disagreement/deviation will be treated as “Critical Deviation” individually for each subclause.
Features of Network Management System

a) The NMS shall run on Unix/Linux/Windows platform.


b) NMS shall be connected to the proposed node equipment via IP interface.
c) NMS should provide web-based client interface which enables anywhere management.
d) NMS must support E2E service configuration, monitoring and performance checking.
e) NMS must support user-friendly GUI and easy point & click operations.
f) NMS should support quicker end-to-end provisioning of multi-service, including WDM circuit, SDH circuit, Ethernet circuit, and wavelength transport.
g) NMS should provide Fault, Configuration, Performance & security features in their respective Window.
h) NMS must support Ethernet OAM standards such as Y.1731,
i) The NMS shall provide management functionalities and web-based management.
j) The NMS shall support remote downloading of all types of software and firmware required by WDM equipment.
k) The system shall support up-gradation of the software version preloaded in the system without loss of traffic or configuration.
l) System shall allow revert back to the previous version of the software.
7.3.3 m)
n)
Download failure on the NE shall not affect other applications running on NMS.
The NMS should have the capability of auto discovery of new NE.
o) NMS shall provide the inventory details of all systems in the network up to card and SFP/XFP level with simple operation.
p) NMS shall have report generation capacity such as Number of configured WDM circuits, SDH circuits, Ethernet paths, used and unused capacity of each Network Element etc.
q) NMS shall provide Comprehensive network map (geographic and synoptic) of all the managed elements with a sophisticated alarm and traffic status display, real time alarm and traffic
monitoring and giving a full access to all NE technical management features through a user-friendly interface.
r) NMS shall support SNMP, TMF CORBA & REST NBIs
s) NMS shall support FCAPS via REST NBI
t) NMS shall have capability for interworking with 3rd. Party SDN/Orchestration Solutions.
u) NMS shall have capability for integration of 3rd. Party NEs via SBI.
v) NMS shall support Warm/Hot Standby Server Redundancy Solution (Max. 10 Sec. for Switching over between Main & Standby Servers).
w) In Warm/Hot Standby concept, NMS shall support automatic switch-over between Main Server and Standby Server (without user-intervention).
x) In Warm/Hot Standby concept, after switch-over to Standby server, all clients must be automatically switched-over to Standby Server (without user-intervention).

Any disagreement/deviation will be treated as “Major Deviation”.

NMS HW requirements

a) The NMS shall consist of Server and clients-based architecture.


b) There will be provision to use Laptop/Notebook as Local Craft terminal (LCT) with
appropriate software to connect DWDM equipment directly so that configuration, monitoring can
be done from the Laptop. The LCT shall be able to connect all network elements on the same
network (autonomous system) from locally connected device.

c) Required HW resource for Server, Client workstations, Local Craft Terminal i.e.
7.3.4 CPU (type and number of cores, speed)
RAM (Capacity)
Disk (Capacity + required partitioning)
Number of network interfaces
Platform power consumption, power protection
Other HW requirements

should be chosen for each management entity according to the total size of the network and no.
of node / NE to be managed and monitored by the NMS.

Any disagreement/deviation will be treated as “Major Deviation”.


7.3.6.1 Fault and Alarm Management
All fault and alarm events shall be reported. Adequate arrangement for display and logging shall
be provided if there is any event received at the NMS. All alarms received at the NMS shall cause
a change of color/add object on the appropriate object on screen. There shall be visible
indication on screen that there is an alarm somewhere in the system. In addition to the displays,
alarm details may be displayed in tabular format.

a) NMS should provide real time surveillance of network faults from the various alarm
captured from the network elements.
b) Alarms in any Node/NE shall be shown by the NMS.
c) Fiber Link/Path (Fiber Cut / High Loss) alarm shall be shown by the NMS.
d) The reported alarm shall have date and time stamped.
7.3.6.1 e) Alarms shall be displayed on NMS screen in different color/object representing the severity
(critical, major and minor) and the state of the alarm. The operator shall be able to acknowledge
and investigate the cause of the alarm.
f) Single alarm window for all NEs displaying network active alarms, cleared alarms, severity of
alarms.
g) Alarm list, threshold and severity should be customized.
h) System shall be capable to log performance parameters on 15 min/24 hours basis and made
available whenever required through NMS beside current register counters, NMS shall be
capable of storing history register counters for the last one months and if required can be
exported to the external hard disk.
i) There should be facility to send SMS/Mail for various alarms. This should be configurable on
basis of alarms and SMS/Mail list to be configurable.

Any disagreement/deviation will be treated as “Major Deviation”.

Configuration Management
Following configurations should be possible:

a) E2E service provisioning


7.3.6.2 b) Port settings.
c) Loopbacks.
d) All configurable parameters for the equipment shall be configured using the NMS.
e) Should be possible to create, configure, provision and manage the traffic based on
bandwidth and QoS requirements.
Any disagreement/deviation will be treated as “Major Deviation”.
Performance management

a) System has to be able to collect all standard quality parameters/indicators for WDM/SDH
based part as well as for packed switch part in accordance with related standards. Data shall be
available for online and offline data analyzes. System shall provide tools to analyze and report
quality parameters/indicators from network on network level (for each network service). It
means that system shall provide quality report not only on node/element level but also on
network service level.
b) For Performance reports, all performance parameters to be monitored on 15 min, hour, day,
month and weekly basis.
7.3.6.3 c) The receiving level monitoring to be provided on real time basis - both in table as well as
graphical view with time stamp.
d) The system should be able to monitor service quality parameters regarding availability on
real time basis.
e) It should be possible to monitor packet drops in case of Ethernet interface.
f) Comprehensive Ethernet performance counters & utilization reports generation must be
supported by NMS.
g) Support to MIB access must be available for integration / real time utilization monitoring by
third party systems i.e. MRTG etc.
h) Facilities should be available to backup stored log data and other data.

Any disagreement/deviation will be treated as “Major Deviation”.

Security Management
7.3.6.4
This functionality shall provide necessary security to the data as well as access to the network.

Access Security
Facilities shall be provided to ensure that only authorized users are allowed to access all or a
certain part of the system. These include comprehensive log-in operator identities and password
facilities. Low level protection for read only access to faults and performance information,
Medium level protection for access to configuration status and features and High level protection
7.3.6.4.1 for control of access to aforesaid clauses and to change in the configuration and control
parameters. All Log in and Log out attempts shall be logged in the security Log File of the NMS
system.

System shall support following authentication and authorization mechanisms for security
management on management system level as well as on element level: RADIUS or TACACS+ or
Microsoft authentication protocol
Data Security

Adequate arrangement to protect data and to recover data lost due to stoppage or failure of the
7.3.6.4.2 EMS hardware or communication system is to be provided. The NMS shall be able to back up and
restore the data base to and from external storage media or internal storage media.

Any disagreement/deviation will be treated as “Major Deviation”.

Inventory Management

System shall support:


7.3.6.5
a) Scheduled automatic inventory data collecting and storing
b) Listing and filtering inventory data
c) Exporting inventory data

HW inventory
7.3.6.5.1 System shall support collecting and storing installed HW inventory data (e.g. hardware
configuration, serial numbers, card positions, etc.).

Service inventory

7.3.6.5.2 System shall support collecting and storing information about configured network services in the
network.
Any disagreement/deviation will be treated as “Major Deviation”.
Bidder's Response
Reference in Bid document*
Agreed / Not Agreed

Agreed
Agreed

Agreed

Agreed

Agreed

Agreed
Agreed
Agreed

Agreed

Scale targets are available on the


install guide
https://www.cisco.com/c/en/us/
td/docs/net_mgmt/epn_manage
r/3_0/install_guide/bk_CiscoEvol
Agreed vedProgrammableNetworkMana
ger_3_0_InstallationGuide/bk_Ci
scoEvolvedProgrammableNetwo
rkManager_3_0_InstallationGuid
e_chapter_00.html#con_123659
2
Product hardware and software
requirement are listed on
following URL:
https://www.cisco.com/c/en/us/
td/docs/net_mgmt/epn_manage
r/3_0/install_guide/bk_CiscoEvol
Agreed vedProgrammableNetworkMana
ger_3_0_InstallationGuide/bk_Ci
scoEvolvedProgrammableNetwo
rkManager_3_0_InstallationGuid
e_chapter_00.html#con_123659
2
g) OTDR white paper:
https://www.cisco.com/c/dam/e
n/us/products/se/2019/7/Collat
eral/benefits-otdr-ncs2k-wp.pdf
a),b),f)
Agreed https://www.cisco.com/c/en/us/
td/docs/optical/r11/ncs/networ
k-
config/guide/b_ncs_network_co
nfiguration-
R11/b_ncs_network_configurati
on_chapter_0100.html
Agreed
FS-SMR data sheet:
https://www.cisco.com/c/en/us/
products/collateral/optical-
Agreed networking/network-
convergence-system-2000-
series/datasheet-c78-
734544.html

a), b) Monitor performance:


https://www.cisco.com/c/en/us/
td/docs/optical/15000r/ncs/con
figuration/guide/b_monitor-
performance_ncs.html
Agreed
c) OTDR white paper:
https://www.cisco.com/c/dam/e
n/us/products/se/2019/7/Collat
eral/benefits-otdr-ncs2k-wp.pdf
Agreed

FLD4 data sheet:


https://www.cisco.com/c/en/us/
Agreed products/collateral/optical-
networking/ons-15200-series-
dwdm-systems/data_sheet_c78-
727050.html

NCS 2000 data sheet:


https://www.cisco.com/c/en/us/
products/collateral/optical-
Agreed networking/network-
convergence-system-2000-
series/data_sheet_c78-
729221.html
Configuration guide
https://www.cisco.com/c/en/us/
td/docs/optical/r11/ncs/networ
Agreed k-
config/guide/b_ncs_network_co
nfiguration-
R11/b_ncs_network_configurati
on_chapter_0111.html#ID286
100G/200G/400G TXP/XP Config
Presentation:
https://salesconnect.cisco.com/
open.html?c=aeda78f7-644b-
4a35-8445-edd2f9c8b283
PSM data sheet:
https://www.cisco.com/c/en/us/
products/collateral/optical-
networking/ons-15454-m12-
multiservice-transport-platform-
mstp/data_sheet_c78-501902-
00.html

Agreed 400G-XP data sheet:


https://www.cisco.com/c/en/us/
products/collateral/optical-
networking/network-
convergence-system-2000-
series/datasheet-c78-
736916.html
10x10G data sheet:
https://www.cisco.com/c/en/us/
products/collateral/optical-
networking/ons-15454-series-
multiservice-provisioning-
platforms/data_sheet_c78-
713296.html
Configuration guide:
https://www.cisco.com/c/en/us/
td/docs/optical/15000r10_0/ncs
Agreed /network_config/guide/b_ncs_n
etwork_configuration/b_ncs_net
work_configuration_chapter_01
00.html#ID2656

Controllers data sheet:


https://www.cisco.com/c/en/us/
products/collateral/optical-
networking/ons-15454-series-
multiservice-transport-
Agreed platforms/datasheet-c78-
602903.html
OTDR white paper:
https://www.cisco.com/c/dam/e
n/us/products/se/2019/7/Collat
eral/benefits-otdr-ncs2k-wp.pdf

CTP release note:


https://www.cisco.com/c/en/us/
Agreed td/docs/optical/metroplanner/m
etroplanner_11/release-
notes/b-ctp-11-relnotes.html
Alarm management:
https://www.cisco.com/c/en/us/
td/docs/optical/15000r/ncs/con
Agreed figuration/guide/b_alarm_tca_m
onitoring_ncs.html#concept_833
1D767CA1A4BF2B7D523B4D07D
2C73

Upgrade guide:
https://www.cisco.com/c/en/us/
td/docs/optical/15000r/ncs/upg
rade/guide/b-ncs-11-
upgrade.html
Agreed
CTC operations:
https://www.cisco.com/c/en/us/
td/docs/optical/15000r9_2/dwd
m/reference/guide/454d92_ref/
454d92_ctcoperation.pdf

Configuration guide:
https://www.cisco.com/c/en/us/
td/docs/optical/r11/ncs/controlc
Agreed ard-config/guide/b-ncs-11-
control-card-node-config/b-ncs-
11-control-card-node-
config_chapter_0100.html

Agreed

NCS 2000 data sheet:


https://www.cisco.com/c/en/us/
products/collateral/optical-
Agreed networking/network-
convergence-system-2000-
series/data_sheet_c78-
729221.html
Hardware specifications:
https://www.cisco.com/c/en/us/
Agreed td/docs/optical/hardware/ncs/g
uide/b-hig-ncsinstall/b-hig-
ncsinstall_appendix_01110.pdf

We understand that Line ports


Agreed and Client ports can be on the
same card also.

Configuration guide:
https://www.cisco.com/c/en/us/
Agreed td/docs/optical/15000r/ncs/con
figuration/guide/b_security_refe
rence_ncs.html
The Cisco® Evolved
Programmable Network (EPN)
Manager is a simplified and cost-
effective device operation,
administration, and network
fault management solution for
today’s converging IP and optical
multilayer networks. This all-in-
one, next-generation product
provides device management,
network provisioning, and
network assurance across core,
edge, aggregation, and access
networks. EPN Manager
Agreed provides end-to-end network
management of Carrier
Ethernet, L3VPN, MPLS TE,
Optical Transport Network
(OTN), Dense Wave-Division
Multiplex (DWDM) networks.
Built on a model-based
architecture with content
decoupled from the platform, it
greatly improves agility in
content delivery. It is a flexible,
easy-to-deploy solution with a
visually appealing user interface
and a common inventory and
data model.

Listed feature set is available in


Agreed EPN-M

Listed feature set is available in


Agreed EPN-M
Agreed Listed feature set is available in
EPN-M, except CORBA NBI

Product hardware and software


requirement are listed on
following URL:
https://www.cisco.com/c/en/us/
td/docs/net_mgmt/epn_manage
r/3_0/install_guide/bk_CiscoEvol
Agreed vedProgrammableNetworkMana
ger_3_0_InstallationGuide/bk_Ci
scoEvolvedProgrammableNetwo
rkManager_3_0_InstallationGuid
e_chapter_00.html#con_123659
2
Agreed Listed feature set is available in
EPN-M

Agreed Listed feature set is available in


EPN-M
Listed feature set is available in
EPN-M. SNMP MIB available
Agreed here
ftp://ftp.cisco.com/pub/mibs/v2
/CISCO-EPM-NOTIFICATION-
MIB.my

The whole flow from network to


the end user is secued.
Communication between EPNM
and managed devcies can be
secured via SSL.Data collected
from the network are secured in
Agreed an Oracle DB whom access is
onloy granted via its web UI.
Web UI implements RBAC for
exhosting granulatity on user
previledges accessing the
system. Web UI relies on HTTPS

The whole flow from network to


the end user is secued.
Communication between EPNM
and managed devcies can be
secured via SSL.Data collected
from the network are secured in
an Oracle DB whom access is
onloy granted via its web UI.
Agreed Web UI implements RBAC for
exhosting granulatity on user
previledges accessing the
system. Web UI relies on HTTPS
RADIUS, TACACS and LDAP for
externalk authentication are
supported, as protocol. As
products, only Cisco ACS and ISE
servers
EPNM supports external FTP
Agreed server where to store
application backups

Listed feature set is available in


Agreed EPN-M

Agreed Listed feature set is available in


EPN-M

Agreed Listed feature set is available in


EPN-M
Remarks

1)Proposed cisco SMR-20 in 3 locations and SMR-9 for other loactions and can be
controlled using GMPLS control plane.
https://www.cisco.com/c/en/us/products/collateral/optical-networking/network-
convergence-system-2000-series/datasheet-c78-734544.html
2) Proposed EDFA-35
in 6 locations and EDFA-17 in one location(daudkandi).
Cisco SMRs and EDFAs cards doesn't supports OTDR functionality but
proposed TNCS -20 Line card supports in Line OTDR funtionality.
https://www.cisco.com/c/en/us/products/collateral/optical-networking/ons-15454-
series-multiservice-transport-platforms/datasheet-c78-602903.html 3)In BOQ,
added spare Equipment for Sylhet site.

Proposed Cisco 9-SMR ROADM , Refer


https://www.cisco.com/c/en/us/products/collateral/optical-networking/network-
convergence-system-2000-series/datasheet-c78-734544.html.
-Proposed Cisco 400G XP card supports
100G , Refer https://www.cisco.com/c/en/us/products/collateral/optical-
networking/network-convergence-system-2000-series/datasheet-c78-736916.html
-Proposed WSON functionality with GMPLS enabled.
-Proposed TNCS-2O to provide in service OTDR, Refer
https://www.cisco.com/c/en/us/products/collateral/optical-networking/ons-15454-
series-multiservice-transport-platforms/datasheet-c78-602903.html
Proposed Cisco 20-SMR and 9-SMR ROADM , For more information please Refer to
attached link https://www.cisco.com/c/en/us/products/collateral/optical-
networking/network-convergence-system-2000-series/datasheet-c78-734544.html
Proposed
Cisco 400G XP card supports 100Gbps with QPSK modulation. For more information
please Refer to attached link
https://www.cisco.com/c/en/us/products/collateral/optical-networking/network-
convergence-system-2000-series/datasheet-c78-736916.html
-Proposed WSON
functionality with GMPLS enabled.
-Proposed TNCS-2O to provide in service OTDR, Refer
https://www.cisco.com/c/en/us/products/collateral/optical-networking/ons-15454-
series-multiservice-transport-platforms/datasheet-c78-602903.html

As per the given Annex-1 and Annex-3 of Section 8 (Network Topology with Distance and
dB Loss).created the DWDM toplogy.

As per the Annex-2 of Section 8 created traffic matrix in the network and site wise Line
and client interfaces are included in BOM.

Proposed 3 dB Aging loss


)Proposed SMR-20 supports 96 channels with 50 GHz spacing . 2)Proposed Cisco
SMR-20 supports 20 xWSS, 9-SMR supports 9xWSS.
Refer https://www.cisco.com/c/en/us/products/collateral/optical-networking/network-
convergence-system-2000-series/datasheet-c78-734544.html
3)Depends upon the traffic matrix given by the customer calculated required numbers line
cards and the required number of line cards per site wise will be included in Bill of meterial.
4)For one subrack
proposed 2xTNCS-20 line cards with 1+1 redundency. 5)Necessary software will
be included in BOM. 6)The proposed Cisco NCS
2006 chassis supports 1+1 power dedundency 7)Proposed M6 chassis supports 1+1
controller card redundency. 8)In the proposed solution not using any
OTN switch. https://www.cisco.com/c/en/us/products/collateral/optical-networking/network-
convergence-system-2000-series/data_sheet_c78-729221.html
9)Proposed cisco 400G-XP LC supports clients and
trunks in the same card and supports PSM protection.For more information about 400G-XP line
card. Refer the attached link:https://www.cisco.com/c/en/us/products/collateral/optical-
networking/network-convergence-system-2000-series/datasheet-c78-736916.html

The proposed Cisco NCS 400G-XP card supports 10/100GE client interfaces supports
QSFP+/QSFP28 based client ports. For more information please Refer to the attached
link: https://www.cisco.com/c/en/us/products/collateral/optical-networking/network-
convergence-system-2000-series/datasheet-c78-736916.html
WSON control plane with enabled GMPLS supports protection with 50 ms switch over
time and automatic restoration mechanism.
https://www.cisco.com/c/en/us/products/collateral/optical-networking/ons-15454-
series-multiservice-provisioning-platforms/data_sheet_c78-689160.html

BOQ will be submitted as a separate attachment.


Create BOM left to AM
c) Optical wavelengths are by definition transparent to whatever client protocol is carried
inside the optical signal.
d) The CTP design tool prioritizes optical routes without regeneration. The regeneration
is configured if and only if the traffic demand cannot be satisfied otherwise.
e) If the network is full coherent, the CTP design tool does not include any Dispersion
Compensation Module.
g) The NCS 2000 Series supports Dynamic Service restoration with WSON Control Plane.
From h to m) These constraints can be forced in CTP design tool so to obtain the use of
the same hw modules on all the nodes.
ix) As client protection NCS 2000 Series supports y-cable protection on 10Gx10G and
100G/200G transponders.
xxvi) The NCS 2000 Series supports Dynamic Service restoration with WSON Control
Plane. ASON is not supported.

The NCS 2000 Series supports the capability to pro-actively monitor the services running
on the network by leveraging on the performance monitoring available at different
network layers (optical, OTN/FEC, client Ethernet/SONET/SDH/OTN) in conjunction with
alarms and conditions reported by the optical devices carrying the customer services.
With such tools the user can monitor degrades of performances across the network and
pro-actively take corrective actions.

The NCS 2000 coherent transponders are capable of estimating the end-to-end line
OSNR by leveraging on embedded Digital Signal Processor (DSP) device and return this
value on Optical Performance Monitoring (PM) data.
Proposed Cisco 400G XP card. Please Refer to attached link
https://www.cisco.com/c/en/us/products/collateral/optical-networking/network-
convergence-system-2000-series/datasheet-c78-736916.html

The NCS 2000 Series is compliant to the following standards:


IEC 60950-1 /EN 60950-1, 2nd Ed.
21CFR1040
IEC 60825-1, 2007-03
IEC 60825-2, 2010-12
ITU-T G.664 (2006)
The NCS 2000 Series utilizes Automatic Power Control (APC) on a per span-basis.
It is coordinated on a per node-basis throughout the "APC Domain". APC adjusts
the amplifier gain, and the ROADM cards regulate the integrated variable optical
attenuators, in order to maintain an optimal system. APC runs automatically
when a channel is added or removed or a fiber break occurs. APC also runs
automatically every hour when the system is static and it is able to correct and
re-balance power fluctuations of 3 dB.
When a known fiber is connected to the ROADM, the card performs a span loss
calculation by using the Optical Service Channel (OSC) and it compares the
measurement with the value coming from the design: if the delta between them
is greater than the resolution, a Span Lenght Out-Of-Range alarm is raised by the
ROADM card facing the side.
When the link is active, NCS 2000 will leverage on the first active channel to
recalculate the span loss. When APC runs, it collects power values that compares
with the previous ones; the delta between them defines the action that needs to
be taken:
- if the power goes below the Channel Loss threshold, ALS kicks in and turns off
the amplifiers until the issue is fixed. Same thing will happen in case of fiber cut.
- if the delta is greater than 3 dB, APC will not automatically balance the power
on the system, but it will raise an APC-Correction-Skipped alarm, which means
that it is the user that chooses to force the APC correction manually. This is a
further safety mechanism.
- If the variation is lower, APC will fix the amplifiers gain in order to recover the
original power set point.
The amplifier is able to converge to the expected power level in few
seconds.
There are multiple 1+1 Protection schemes:
- Y-cable allows to protect at card level and build two different paths belonging to the
same Protection group.
- Protection Switching Module (PSM) is a line card that does optical switch offering 1+1
Protection.
- Splitter Protection allows to build two independent protected services using two
different trunks on the same card.

Different types of transponder/muxponder/crossponder cards support different sets of


protection schemes.
Restoration is a best effort mechanism: the control plane tries to re-route the service
considering the steps below. Restoration of Wavelength is done considering that the
circuit is configured as mentioned in the user guide.
A GMPLS circuit can be set to restorable with Include node or Exclude node or specific
degree constraints.
Additional constraints on Restoration trigger with specific time can be configurable.
Time taken for a wavelength to be restored depends on:
1. Feasibility of a route with specific wavelength based on constraints set
2. Priority of the circuit for Restoration, number of circuits that needs to be restored
3. Number of intermediate nodes which include Amplifiers and ROADMs (in case of
optical xconnections). Minimum time can be around dozens of seconds to few minutes.
Maximum depends on the conditions above.
h) Restoration generically tries to avoid regeneration. Only if there is no available end-to-
end path, a WSON control plane looks for a regen site supporting the end-to-end
restoration route.

In NCS 2000 Series the OTDR feature is supported and built in the node controller TNCS-
O. A Pseudo Noise Bit Sequence is transmitted in the fiber next to the optical pulse at
1518nm. The reflected light is sampled against time and mathematically correlated with
the original probe sequence. The correlation method allows for better noise filtering,
providing a significant noise advantage respect to pulse method (12 dB measured). Also,
since pulse probe energy spreads along a bit stream, this method better adapts to the
typical lasers used in pluggable interfaces, which can provide lower TX Power.
In NCS 2000 Series OTDR has a dinamic range that is able to cover 100 km / 20 dB of
span.
The scan can be used on 5 different zones with preconfigured values:
• Zone 1 from 0 to 1km: for patch panel and connections at central office
• Zone 2 from 0 to 25 km: Raman critical zone
• Zone 3 from 0 to 80 km: most of the links
• Zone 4 from 0 to 100km: full span
• Auto mode
Furthermore, the Expert Mode zone allows the user to run a custom type of scan.

b) Resolution of 3 meters is achievable on short spans as on longer the computation time


would be excessively high.

Node availability strictly depends on the node architecture and active/passive linecards
used to build up the solution; as such is not possible to provide 99.999% availability with
all the possible target node/network configuration. However, the use of specific
protection schemes allows to bring the link availability up to 99.999%. Nevertheless NCS
2000 Cisco Transport Planner (CTP) is able to provide link availability for each and every
simulated services. The feature is available on the Link Availability tab presents in the
Results.
The NCS 2000 Series features enhanced resiliency mechanism against controller card
failure. Both NCS 2006 and NCS 2015 run in duplex mode with active/standby controller
cards plus a flash memory containing copy of the running image and of the latest
database. NCS 2002 runs in simplex mode a single controller card + flash memory. In the
event of single controller failure (NCS 2002) or double controller failure (NCS 2006 and
NCS 2015) the user can replace the failed controllers with brand new units which are
getting the image and the configuration from the flash memory. The headless condition
is supported for a limited amount of time enough to replace the controllers.

The NCS 2000 Series supports alarm management.


See the link for more details.

The NCS 2000 Series supports In-Service-Software-Upgrades. ISSU is non traffic-affecting


for each supported upgrade path (see the hyperlink to software upgrading matrix).

Both CTC and EPNM offer the possibility to backup and restore the DB.

NTP settings help ensure that Cisco NCS 2000 Series receives the correct timestamps for
events. When specifying the time zone, enter the time zone's acronym and its difference
(in hours) from Coordinated Universal Time (UTC).
Both primary and secondary server can be configured and timezone as well. SNTP-HOST
alarm is raised when servers are unreachable.

The NCS 2000 Series supports OSC transceiver power readings for both tx and rx
directions.
The OSC tx wavelength is 1510nm/1518nm and is completely independent of service
traffic flow.

The NCS 2000 Series avoids DCN single point of failure. The node can rely on two
different DCN ports on the ECU module, a LAN port on each controller faceplate and
inband OSC on each outgoing fiber pair. As such a failure occurring on the DCN or on one
of the optical spans can be easily bypassed using the other available interfaces.
d) If by filter unit it is meant the passive mux/demux, the answer is yes.

The NCS 2000 Series can operate within the range of 0 to 55 degrees Celsius.

The NCS 2000 Series supports operating ambient RH - non condensing: 5% - 85%.
The NCS 2006 DC40 power module supports 1920W in 1+1 configuration. The DC power
modules have –48 VDC or –60 VDC dual-hole lug power terminals. The fuse rating must
not exceed 60A.
The NCS 2015 DC power modules supports 1750W per module and total of 5250W in the
shelf in 3+1 configuration. The DC power modules have –48 VDC or –60 VDC dual-hole
lug power terminals. The fuse rating must not exceed 60A.

The NCS 2000 Series supports the encryption feature on WSE, MR-MXP, 400G-XP line
cards. The encrypting platform is transparent to client data.
Increased operational scale and efficiency through simplified, integrated, and automated
device operations, network provisioning, and network assurance

Proactive service assurance and highly effective fault management and trend information
to help providers avoid future service disruptions
Comprehensive, graphical views of the entire network, from the topology to the device
level, with centralized inventory, status, and fault information
Automated discovery, device configuration, and change management with up-to-date
displays of network events, states, and changes

Modern GUI with wizard-led workflows, topology-guided troubleshooting, and multilayer


visualization (Figure 2)

Point-and-click provisioning for Carrier Ethernet and optical transport, (Figure 3)


Fault management for the underlying infrastructure with graphical correlation

Proactive network health monitoring, including network-level alarms, threshold crossing


alerts (TCAs), metrics collection, and performance reporting

Multilayer management, performance monitoring, and provisioning

You might also like