Date post: | 01-Jun-2018 |
Category: |
Documents |
Upload: | knowledge-of-all |
View: | 770 times |
Download: | 110 times |
8/9/2019 APOLLO ECI TELEKOM
1/176
8/9/2019 APOLLO ECI TELEKOM
2/176
Table of ContentsSTMS overview
STMS Alarms
NMS LightSoft Introduction
NMS Elements & Groups
NMS Topology Links
NMS Optical Trails
TCI -Trail Consistency Indicator
TR10_4 Configuration
TR100 Configuration
CMR40 Configuration
AoC10 Card Configuration
CMR100 ConfigurationTheory of ASON Technology
ASON Technology Implementation in Apollo
DNI Configuration
DRI Configuration
3
19
27
39
47
53
71
79
87
97
105
117131
145
161
169
1
8/9/2019 APOLLO ECI TELEKOM
3/176
Global Professional Services ECI Training ServicesECI Telecom Ltd.
This page is intentionally blank
2
8/9/2019 APOLLO ECI TELEKOM
4/176
STMS Overview1/30
STMS Integrated
ShadeTree Management Suite
Global Services Division
ECI Training Department
STMS Overview2/30
Content
Introduction
STMS architecture and platforms
STMS client
Configuration features
Faults
PM Performance Monitoring
DB Backup
3
8/9/2019 APOLLO ECI TELEKOM
5/176
STMS Overview3/30
Introduction
STMS (ShadeTree Management Suite) is the elementmanagement (EMS), service provisioning andmonitoring solution for the Apollo (OPT9600) productsfamily: OPT9624H & OPT9624L
OPT9608
OPT9603
STMS provides FCAPS:1. Fault
2. Configuration
3. Accounting
4. Performance
5. Security
STMS Overview4/30
TMN Architecture
STMS Client
JDBCJavaRMI
Third-party NMS
STMSOracle
Database
Network
Element
Element
Management
Network
Management
Business/Service
Management
LightSoft NMS
SNMP CORBA over SSL
CORBA/MTNM (TMF-814) Java RMI
Northbound OSS: MTNM
NMS client
OPT9603 OPT9608OPT9624
4
8/9/2019 APOLLO ECI TELEKOM
6/176
STMS Overview5/30
LightSoft or NMS/OSS Integration
STMS is fully integrated with LightSoft to support:
Inventory management
Alarm management
PMs
Topology links/Optical trails configuration
ODU XC Configuration
GUI cut-through
STMS can integrate with existing OSS applications viathe Northbound Application Programming Interface(NB-API) that supports Java RMI
LightSoft/NMS
STMS
CORBA/MTNM (TMF-814)
Java RMI NorthBound API
STMS Overview6/30
STMS Platforms
Carrier grade three tier architecture Server:
Sun Solaris 9, 10
RedHat Linux RHEL 3, RHEL 4
Database:
Oracle 9i, 10g
Thin client Java GUI:
Windows XP, 2000, 7
Solaris
Linux
5
8/9/2019 APOLLO ECI TELEKOM
7/176
STMS Overview7/30
STMS Client
STMS Client is a Java-based GUI from which operatorscan manage STMS server
The STMS Client can run as a standalone applicationon Windows, Linux, Solaris or any other platform thatsupports Java
Client must resolve the host-name of the STMS server
Configure DNS server Or edit hosts file
STMS Overview8/30
Entering STMS
1. In NMS LightSoft, go to the Physical (EMS) layer
2. Right click the STMS and Open
6
8/9/2019 APOLLO ECI TELEKOM
8/176
STMS Overview9/30
Alarms, Events & Log tabs
Network Explorer
Network Element work table
Navigating STMS
STMS Overview10/30
Navigating STMS
Network Explorer
Displays a representation of the network in the form of a treehierarchy
7
8/9/2019 APOLLO ECI TELEKOM
9/176
STMS Overview11/30
Creating a Group
Creation of sub-groups is possible by creating a new folder under an existingone, or by dragging a folder below another oneUploading an NE into a group can be done by the Discover NE option oneach folder you can also drag and move NEs between folders (NOT serviceaffecting)
STMS Overview12/30
Customer Explorer
Displays all of the services and XS assigned to a specific customer
Navigating STMS
8
8/9/2019 APOLLO ECI TELEKOM
10/176
STMS Overview13/30
Inventory View
Graphical representation of the chassis
STMS Overview14/30
Slot Assignment
9
8/9/2019 APOLLO ECI TELEKOM
11/176
STMS Overview15/30
Installed Modules
The Show Actual checkbox shows which modules arephysicallyinstalled inthe chassis
STMS Overview16/30
Assigned Vs. Actual
Actual card (yellowbackground) is OA_MLAssigned card (graybackground) is OA_ML
Actual card (yellowbackground) is OA_MLAssigned card (graybackground) is TR10_4
Actual card (yellowbackground) is empty slotAssigned card (graybackground) is ROADM
10
8/9/2019 APOLLO ECI TELEKOM
12/176
STMS Overview17/30
Physical Port Configuration
STMS Overview18/30
Fiber Connectivity
11
8/9/2019 APOLLO ECI TELEKOM
13/176
STMS Overview19/30
Cross Connections
STMS Overview20/30
Creating Users in STMS
In the Server Preferences tab, click the Users tab
Click Create User..
12
8/9/2019 APOLLO ECI TELEKOM
14/176
STMS Overview21/30
Fault Management
Alarm management Multiple alarm levels Displays only active alarms Correlates alarms into a single notification Uploaded as they are into LightSoft
STMS Overview22/30
Fault Management
Displays STMS messages thatindicate system events, exceptions,or conditions
Displays Network events
Displays STMS Client messages thatindicate non-error system events orconditions, such as network elementsbeing discovered
Displays STMS Client messages ofsystem exceptions or conditions
13
8/9/2019 APOLLO ECI TELEKOM
15/176
STMS Overview23/30
PM
STMS Overview24/30
PM
14
8/9/2019 APOLLO ECI TELEKOM
16/176
STMS Overview25/30
1) Tools -> Configuration Manager
2) Enter username and passwordfor STMS users in the STMS zone and select the
communication protocol
NE DB Backup
STMS Overview26/30
NE DB Backup
To create an immediate one time backup, click on Create
Enter a label, select the NEs to be backed up. And clickon OK.
15
8/9/2019 APOLLO ECI TELEKOM
17/176
STMS Overview27/30
NE DB Backup
The backup file is created and listed in the BackupManager tab.
STMS Overview28/30
Backup Scheduler
Go to Backup Scheduler tab and Click on Create,
Enter the Schedule attributes and click on OK.
16
8/9/2019 APOLLO ECI TELEKOM
18/176
STMS Overview29/30
Restore DB
Right click on the DB file from the Backup Manager listand select Restore
STMS Overview30/30
Summary
Introduction
EMS for Apollo products family
STMS Architecture and Platforms
Integrated into LightSoft
STMS Client
STMS can work as standalone
Configuration Features
Ports, Fiber Connectivity, Cross-Conections
Faults
Alarms, Logs and Events
PM
DB Backup
17
8/9/2019 APOLLO ECI TELEKOM
19/176
Global Professional Services ECI Training ServicesECI Telecom Ltd.
This page is intentionally blank
18
8/9/2019 APOLLO ECI TELEKOM
20/176
8/9/2019 APOLLO ECI TELEKOM
21/176
STMS Alarms3/16
Alarm Hierarchy
In the STMS, alarm indications are propagated throughthe object hierarchy and are displayed up to the highestlevel
STMS Alarms4/16
Alarm Types
Alarms conditions are classified according to severitylevels and are visually reflected in the STMS Clientwindow using the following colors and indications:
Severity Color Indicator Description
Minor Yellow Indicates problem conditions that do nothave a serious effect on service tocustomers or are not essential tonetwork element operations.
Major Orange Indicates a serious disruption of service
or the malfunctioning or failure of
important components or functions.
Critical Red Indicates a severe, service-affecting
condition and that immediate corrective
action is imperative.
Clear White/Green None Indicates that an alarm condition no
longer exists.
20
8/9/2019 APOLLO ECI TELEKOM
22/176
STMS Alarms5/16
Alarm Window
Table view (the default view) displays alarms in a simpletable format
Each alarm is displayed as a separate row in the table
In table view, double-clicking a row opens the property sheet forthe object associated with the alarm
STMS Alarms6/16
Alarm Window
Severity Description
Ack Whether the alarm has been acknowledged. If thealarm has been acknowledged, a check mark will appear in the box
Time The time of the Alarm
Clear Time The time an associated clear alarm was received
Source The host name or IP address of the network element associated
with the alarm
Name The object (i.e., subinterface, logical interface, etc.) associated with
the alarm
Severity The severity of the Alarm
Type The type of the Alarm
SA Whether the alarm is Service Affecting
Description A short description of the alarm
21
8/9/2019 APOLLO ECI TELEKOM
23/176
STMS Alarms7/16
Historical Alarms
By default, the STMS does not maintain nor displayinformation about historical alarms, only active alarms
If order to retain historical
alarm information, this
feature must be enabled
STMS Alarms8/16
Historical Alarms
Viewing historical alarms
22
8/9/2019 APOLLO ECI TELEKOM
24/176
STMS Alarms9/16
Alarm Details
Right Click
STMS Alarms10/16
Alarm Details
Column Description
Time The time of the Alarm
Element Name The object (i.e., subinterface, logical interface, etc.)
Source NE The host name or IP address of the network element
Trap Name The trap name for the alarm
Severity Minor, Major, Critical
Service Affecting Whether the alarm is service affecting (SA)
Acknowledged Whether the alarm has been acknowledged
Acknowledged by Displays the STMS user name of the user whoacknowledged the alarm
Acknowledged at Displays the date and the time that the alarm wasacknowledged
Annotation Any notes about the alarm
Short Description
Detailed Description A detailed description of the alarm
23
8/9/2019 APOLLO ECI TELEKOM
25/176
STMS Alarms11/16
Managing Alarms
Acknowledging Alarms
Right Click
STMS Alarms12/16
Clearing Inactive Alarms
Auto-Clearing
STMS automatically correlates clear alarms with activealarms
By default, when a clear alarm is received, the associated activealarm is automatically cleared and removed from the list of
active alarms in the STMS
24
8/9/2019 APOLLO ECI TELEKOM
26/176
STMS Alarms13/16
Clearing Inactive Alarms
Clearing manually
STMS Alarms14/16
Alarm Preferences
25
8/9/2019 APOLLO ECI TELEKOM
27/176
STMS Alarms15/16
Alarm Preferences
STMS Alarms16/16
Summary
Alarm Hierarchy Alarm indications are propagated through the object hierarchy and
are displayed up to the highest level
Alarm Types Minor, Major, Critical, Clear
Alarm Window Displays alarms in a simple table format
Historical Alarms Disabled by default
Alarm Details Displays information regarding selected alarm
Managing Alarms Acknowledge, Clearing
Alarm Preferences Notification parameters
26
8/9/2019 APOLLO ECI TELEKOM
28/176
LightSoft GUI1.21
NMS LightSoft V6
Introduction
Global Services Division
ECI Training Department
LightSoft GUI2.21
Management Architecture
ManagedManagedManagedManaged
EquipmentEquipmentEquipmentEquipment
NetworkNetworkNetworkNetwork
ManagementManagementManagementManagementLayerLayerLayerLayer
ElementElementElementElementManagementManagementManagementManagement
LayerLayerLayerLayer
BGBGBGBG linelinelinelineXDM lineXDM lineXDM lineXDM line
OtherOtherOtherOtherequipmentequipmentequipmentequipment
OSSOSSOSSOSS
LightSoftLightSoftLightSoftLightSoft
EMSEMSEMSEMS----XDMXDMXDMXDM EMSEMSEMSEMS----BGFBGFBGFBGF Other EMSsOther EMSsOther EMSsOther EMSs
TMF-MTNM Corba I/F
TMF-MTNM Corba I/F
27
8/9/2019 APOLLO ECI TELEKOM
29/176
LightSoft GUI3.21
Tabs No More Menus
NMS LightSoft has a modern look and feel
ECI Button Tabs no menus
LightSoft GUI4.21
ECI Button
ECI button contains the Help and About LightSoftoptions
The ECI Button menu cannot be customized
28
8/9/2019 APOLLO ECI TELEKOM
30/176
LightSoft GUI5.21
LightSoft Ribbon
The LightSoft ribbon is maximized or minimized
To maximize or minimize:
Double click a tab
Ctrl + F1
View tab click on Ribbon
Minimized Maximized
LightSoft GUI6.21
Quick Access Area
Above the ribbon
Static (always visible to user)
Displays:
Technology layers
Consistency indicators
Alarm counters
Technology
Layers
Consistency
Indicators
Alarm
Counters
29
8/9/2019 APOLLO ECI TELEKOM
31/176
LightSoft GUI7.21
Technology Layers
LightSoft has traffic fromdifferent technology types
You can see the elementsprocessing the different traffic types:
Optical (WDM, OTN)
SDH
Ethernet & MPLS
Example:If you go to the ETH/MPLS layer, you see where in yourtopology you have Ethernet or MPLS cards & traffic
LightSoft GUI8.21
Topology Layer Types
Physical (Site)
Physical (EMS)
SDH/SONET
Optical (OTN)
OCH
Ethernet/MPLS Physical(EMS)
SDH/
SONET
SDH/
SONET
Ethernet/MPLSEthernet/MPLS
Physical(Site) Optical
(OTN)
Optical
(OTN)
30
8/9/2019 APOLLO ECI TELEKOM
32/176
LightSoft GUI9.21
Example of Layers
Physical (Site):This layer shows your
whole network, including3rd party equipment(technology transparent)
ETH/MPLSThis layer shows yourEthernet and MPLSswitches in yournetwork
LightSoft GUI10.21
Elements
ME/NE: Managed/Network Element
UME: Unmanaged Element
Groups
31
8/9/2019 APOLLO ECI TELEKOM
33/176
8/9/2019 APOLLO ECI TELEKOM
34/176
LightSoft GUI13.21
Inserting an Element
LightSoft GUI14.21
Consistency Indicators
Show the inconsistencies between the NMS LightSoft
DB, and the EMS databases
33
8/9/2019 APOLLO ECI TELEKOM
35/176
LightSoft GUI15.21
Alarm Counters
A general picture of all the alarms in the system
LightSoft GUI16.21
Context Sensitive Tabs
CST an accepted industry standard
This tab contains only relevant commands for selectedelements (Nodes, Groups and Links)
34
8/9/2019 APOLLO ECI TELEKOM
36/176
LightSoft GUI17.21
Hot Keys
Pressing Alt toggles hot key tips
Once the are tips displayed, type the letter to open thattab level 1
LightSoft GUI18.21
Hot Keys continued
When you go to that tab, you see the hot keys for thattab level 2
If there is more than one letter in the key, pressing thekeys should be sequential and not simultaneousi.e. for FC, press F, then C
35
8/9/2019 APOLLO ECI TELEKOM
37/176
LightSoft GUI19.21
Tree Seeing the Network
View Tree
The Tree shows all
MEs in the topology
LightSoft GUI20.21Map Move Zoom & Navigation
View Functions
Zoom & NavigationSeeing all, or different parts of the topology
Move moving elements on the screen and
saving/not saving changes
Map working with groups of elements(Expanding or collapsing groups)
36
8/9/2019 APOLLO ECI TELEKOM
38/176
LightSoft GUI21.21
Summary
Tabs No More Menus
ECI Button
LightSoft Ribbon
Minimizing/Maximizing
Categories in each tab
Quick Access Area
Technology layers
Consistency indicators
Alarm Counters Context Sensitive Tabs
Hot Keys
Tree, and View menu
37
8/9/2019 APOLLO ECI TELEKOM
39/176
Global Professional Services ECI Training ServicesECI Telecom Ltd.
This page is intentionally blank
38
8/9/2019 APOLLO ECI TELEKOM
40/176
Elements1.15
Elements & Groups in NMS
NMS LightSoft
Global Services Division
ECI Training Department
Elements2.15
Content
Creating a Managed Element (ME)
Creating a Logical Element (LE)
Creating and Modifying an Unmanaged Element (UME)
Creating and Modifying Groups
39
8/9/2019 APOLLO ECI TELEKOM
41/176
Elements3.15
Topology Layer Types
Physical (Site)
Physical (EMS)
SDH/SONET
Optical (OTN)
OCH
Ethernet/MPLS Physical(EMS)
SDH/
SONET
SDH/
SONET
Ethernet/MPLSEthernet/MPLS
Physical(Site) Optical
(OTN)Optical(OTN)
Elements4.15
Creating an ME
. ()
.
. ()
.
. .
.
.
()
40
8/9/2019 APOLLO ECI TELEKOM
42/176
8/9/2019 APOLLO ECI TELEKOM
43/176
Elements7.15
Unmanaged Elements (UME)
UME an element of another operator or vendor,managed by a different managing system
Extremely useful for:
Giving a better view of the network structure
Allowing to handle traffic by trails (and not XC)
Created in the Physical (Site) layer
UMEs are not managed by the NMS
Elements8.15
Creating a UME
.
.
3. Apply & Close
42
8/9/2019 APOLLO ECI TELEKOM
44/176
Elements9.15
Changing a UMEs Configuration
() ()
,
.
.
Elements10.15
Groups
Groups allow you to organize the network hierarchically:
According to Physical location rack, site, city
According to Technological topology chain, ring
Can be created in any layer (physical/ technological)
Members can be added/removed from the group at anytime
You can also create groups of groups
43
8/9/2019 APOLLO ECI TELEKOM
45/176
Elements11.15
Creating a Group
,
Elements12.15
Removing Elements from a Group
!
44
8/9/2019 APOLLO ECI TELEKOM
46/176
Elements13.15
Adding Elements to a Group
!
.
.
Elements14.15
Map Operations
( )
( )
( )
( )
( )
45
8/9/2019 APOLLO ECI TELEKOM
47/176
Elements15.15
Summary
Managed Elements(ME)
Logical Elements(LE)
Why theyre used
Mostly used in DWDM and Data
Unmanaged Elements(UME)
Creating and deleting
Editing UMEs
Groups
Creating and deleting
Adding and removing group members
46
8/9/2019 APOLLO ECI TELEKOM
48/176
Topology Links1.12
Working with TopologyLinks
NMS LightSoft
Global Services Division
ECI Training Department
Topology Links2.12
Topology Links
A topology link represents the physical connection (fiberor copper) between network elements
A topology link connects two ports of different objects(MEs, LEs, and UMEs)
Traffic trails can only be defined over topology links
47
8/9/2019 APOLLO ECI TELEKOM
49/176
Topology Links3.12
Creating a Topology Link
2 2
1
2
3
Topology Links4.12
Create Topology Link Window
2
*
1
2
3
48
8/9/2019 APOLLO ECI TELEKOM
50/176
Topology Links5.12
Create Topology Link Attributes
Topology Links6.12
Create Topology Link Attributes
.
, , .
( )
, . .
(/)
, , , ,
, .
, .
() .
.
49
8/9/2019 APOLLO ECI TELEKOM
51/176
Topology Links7.12
Create Topology Link Attributes
()
11000.
..
( .. ) , 1 ( ) 5
( )
(*/) /. ,
() . ,
0
( )
Topology Links8.12
A Topology Link in LightSoft
A topology link appears in the physical (site) layer and inthe relevant technology layer
50
8/9/2019 APOLLO ECI TELEKOM
52/176
Topology Links9.12
Topology Links Color-Coding
Color-coding for operational links:
Red critical or major alarm
Orange minor alarm
Yellow warning
Green clear (no alarms)
Color-coding for non-operational links:
Light blue the link is connected and not uploaded(an intermediate state)
Dark blue the link is being uploaded(intermediate, longer state)
Dark grey the link is disconnected
White inconsistent link
Topology Links10.12
Internal Links
Internal link A link between two ports of one element
When an arrow appears next to the ME- it indicates thatan internal link exists in the element
51
8/9/2019 APOLLO ECI TELEKOM
53/176
Topology Links11.12
Viewing Internal Link Details
1
2
Topology Links12.12
Summary
Topology Links
Between elements
Internal links
52
8/9/2019 APOLLO ECI TELEKOM
54/176
Optical Trails1.13
Optical Trails
NMS LightSoft
Global Services Division
ECI Training Department
Optical Trails2.13
Content
Creating Logical Elements
Creating UMEs for clients
Topology links
Optical Trails
53
8/9/2019 APOLLO ECI TELEKOM
55/176
8/9/2019 APOLLO ECI TELEKOM
56/176
Optical Trails5.13
Creating a Logical Element
Optical Trails6.13
Creating UMEs For Clients
55
8/9/2019 APOLLO ECI TELEKOM
57/176
8/9/2019 APOLLO ECI TELEKOM
58/176
Optical Trails9.13
Creating Clients Capacity Links
Optical Trails10.13
Creating OMS Trails
57
8/9/2019 APOLLO ECI TELEKOM
59/176
Optical Trails11.13
Creating OCH Trails
Optical Trails12.13
Creating LP Trails
58
8/9/2019 APOLLO ECI TELEKOM
60/176
Optical Trails13.13
Content
Creating Logical Elements
Creating UMEs for clients
Topology links
OPS-1
OTM
Optical Trails
OMS
OCH
ODU LP
59
8/9/2019 APOLLO ECI TELEKOM
61/176
8/9/2019 APOLLO ECI TELEKOM
62/176
Optical Trails3.20
LightSoft Optical Layer Benefits
New SDH-like workflow for optical trail acquisition replacesTCI
SRLG support - SRLG can be assigned to OMS and OPS_1links
Enhanced Availability Table shows used, available andblocked channels. Details available for selected channel
Show Ring - enable the user to enter the ring name for allSDH and OTN layers.
Add link name - support for virtual links
Optical Trails4.20
Optical Layer Display
The Optical Layer simplifies the network by displayingonly optical ports.
View all of the sites and connections along an opticallink Simple and effective navigation within the network
View all of the components in each direction of the link
Thorough and complete view of the complete optical link
61
8/9/2019 APOLLO ECI TELEKOM
63/176
Optical Trails5.20
Optical Network Creating Process
On EMS:
Create NE in EMS
Make slot assignments
Configure all internal parameters of optical cards
On NMS (optical layer) Create and configure LEs for all relevant components
(optional)
Create and configure relevant UMEs ( OTN)
Create OTM links Create OPS_1 Links
Create client Links ( SDH, GbE, DSR)
Discover Optical Trails
Optical Trails6.20
Create Optical Layer LEs
LEs can be created manually or automatically
62
8/9/2019 APOLLO ECI TELEKOM
64/176
Optical Trails7.20
Creating and Configuring Optical UME
Select UME type in OTN and configure accordingly
Optical Trails8.20
Create Optical Topology Link
63
8/9/2019 APOLLO ECI TELEKOM
65/176
Optical Trails9.20
Types of Topology Link
Self Link - a link between two ports housed on the sameOptical Element
Topology Link - a link between two ports housed ondifferent Optical Elements
OTM (Optical Terminal Multiplexer) links
A link that could contain several channels connected to anoptical MUX/DEMUX
OPS_1- topology physical connection for one channel(SIO/TRP/CMBR)
Optical Trails10.20
Simple Optical Link Characteristics
Src Snk SIO/TRP SIO/TRP
D
M
U
X
M
U
X
OFA
OMS
LP
OPS_1 OPS_1OTM OTM
OCH
64
8/9/2019 APOLLO ECI TELEKOM
66/176
Optical Trails11.20
When Creating Optical Trails
Terminology
OTM - topology physical connection (link) that contains morethan 1 channel (OFA, MUX/DEMUX, SV, OADM)
OMS_OTN - logical trail of the OTM link (like an optical ServerTrail)
OPS_1 - topology physical connection (link) for 1 channel (TRP)
OCH_OTN - logical trail of the OCH link (1 optical channel fromend-to-end)
LP_SDH - logical trail from UME or SDH connected to clientside of the TRP
LP_GbE - logical trail from UME (defined as GbE PORTS)connected to client side of the TRP
Optical Trails12.20
When Creating Optical Trails
Note
Optical Trails are bidirectional
Optical trails are created from Topology Links using theDiscover Optical Trailsfunction
65
8/9/2019 APOLLO ECI TELEKOM
67/176
Optical Trails13.20
Show discovered optical trail
Optical Trails Discovery on selected resources
Optical Trails of all Rates will be created on selectedlinks:
OMS
OCH
LP
High Order ( VC-4 or EoS)
Discovered Optical Trails are bidirectional
Optical Trails14.20
Show Discovered Optical Trail
66
8/9/2019 APOLLO ECI TELEKOM
68/176
Optical Trails15.20
Optical Trails after Discovery
Optical Trails16.20
Predefined Filter Data over WDM
67
8/9/2019 APOLLO ECI TELEKOM
69/176
Optical Trails17.20
Wavelength Utilization Tables
Quickly and effectively view which channels are:
Free for use
In-Use
Blocked from being used
Utilization can be seen per single or multiple OMS
segments.
Optical Trails18.20
Wavelength Utilization Table
Select any channeland view the opticaltrail and the service
68
8/9/2019 APOLLO ECI TELEKOM
70/176
8/9/2019 APOLLO ECI TELEKOM
71/176
Global Professional Services ECI Training ServicesECI Telecom Ltd.
This page is intentionally blank
70
8/9/2019 APOLLO ECI TELEKOM
72/176
1
TCI in Lightsoft1.16
TCI -Trail ConsistencyIndicator
Light Soft
Global Services Division
ECI Training Department
TCI in Lightsoft2.16
Content
EMS NMS Hierarchy
Inconsistency Types
NMS info is partial- yellow flag
EMS info is partial- red flag
TCI Window
Tool bar
Parameters (auto actions)
Trail Synchronization Window- Color Indication
Additional Windows
71
8/9/2019 APOLLO ECI TELEKOM
73/176
2
TCI in Lightsoft3.16
EMS NMS Hierarchy
()
()
TCI in Lightsoft4.16
Inconsistencies
Inconsistencies between the LightSoft database and EMS
databases can develop over time for a number of reasons
such as:
XCs were defined or changed on the EMS or craftterminal level
XCs were accidently deleted from the EMS
Trails were deleted from the NMS while performingmaintenance operations
72
8/9/2019 APOLLO ECI TELEKOM
74/176
3
TCI in Lightsoft5.16
Inconsistency Types
Two types of inconsistencies depending on where theinformation is partial- EMS or NMS
TCI in Lightsoft6.16
TCI Counters
The TCI counter in the NMS main window toolbar shows:
Number of inconsistencies in all trails
OR
Number of inconsistencies in SDH trails only
Clicking the counter icon swaps between total and SDH
The color of the flag indicates the type of the worstinconsistency
No inconsistency
73
8/9/2019 APOLLO ECI TELEKOM
75/176
4
TCI in Lightsoft7.16
TCI Window
To open TCI window click the Trail Consistency icon
TCI in Lightsoft8.16
TCI Window Tool Bar
Start Process
Stop Process- The operation continues on the trailsprocessed up to that point
Abort- The entire operation stops at once and no resultsare provided
Show Selected Objects- Opens Selected Trails pane thatlists the trails selected when the TCI window wasopened
Close Show Selected Objects- closes the pane
74
8/9/2019 APOLLO ECI TELEKOM
76/176
8/9/2019 APOLLO ECI TELEKOM
77/176
6
TCI in Lightsoft11.16
TCI Window - Parameters
Auto impose to network:
Classified- automaticallyimpose P2P trails from
Database to Network
Auto admit to database:
Classified- automaticallyadmit P2P trails from
the Network to theDatabase
Flex- automatically admitFlex trails from theNetwork to the Database
TCI in Lightsoft12.16
Trail Synchronization Window- Colors
Trails in the DB window may have counterparts in thenetwork window that are:
Exactly matching
Partially matching
Overlapping
When you select a trail in one window the
corresponding trail in the other window is highlightedwith a color that indicates the relation between the trails
Different treatment is required according to the conditionimplied by the color
76
8/9/2019 APOLLO ECI TELEKOM
78/176
7
TCI in Lightsoft13.16
Trail Synchronization Window- Colors
Green
Yellow
Blue
Correspondingin Grey
TCI in Lightsoft14.16
Trail Synchronization Window- Colors
.
.
.
.
77
8/9/2019 APOLLO ECI TELEKOM
79/176
8
TCI in Lightsoft15.16
Additional Windows
Queue Window-Displays the selected trail (admitted or imposed)After activating displays the action status (success orfailure)
Imposed and Admitted Trails Windows-
Displays the trails that were automaticallyadmitted/imposed
Event List Window-Displays information about problems that may occur inthe synchronization process
TCI in Lightsoft16.16
Summary
EMS NMS Hierarchy
Inconsistency Types
TCI icon & window
Trail Synchronization Window- Color Indication
Additional Windows
78
8/9/2019 APOLLO ECI TELEKOM
80/176
TR10_4 Configuration1.16
TR10_4 Configuration
Apollo
Global Services Division
ECI Training Department
TR10_4 Configuration2.16
TR10_4 Card Configuration
79
8/9/2019 APOLLO ECI TELEKOM
81/176
TR10_4 Configuration3.16
TR10_4 Port Configuration
Manual
Client > Line
Y - Protection
OTU2/2e
TR10_4 Configuration4.16
TR10_4 Ports Configuration
80
8/9/2019 APOLLO ECI TELEKOM
82/176
TR10_4 Configuration5.16
Verifying Port Properties
TR10_4 Configuration6.16
Y Protection
Only the first Client port - 0 can be in Y Protection
81
8/9/2019 APOLLO ECI TELEKOM
83/176
TR10_4 Configuration7.16
IOP Protection Configuration
IOP protection group:
U5 & U7
Choose one of the cards from the IOP Group:
IOP protection configuration is done via the ports
TR10_4 Configuration8.16
IOP Protection Configuration
Right click on the client port
Note: Client ports belonging to the same IOP Protection Groupmust be configured similarly with the same parameters!
82
8/9/2019 APOLLO ECI TELEKOM
84/176
TR10_4 Configuration9.16
Deleting IOP Protection
Each port is deleted separately Only via the main port
TR10_4 Configuration10.16
FEC & EFEC Configuration
From the optical port, move to the OTU Attributes:
Scroll down:
83
8/9/2019 APOLLO ECI TELEKOM
85/176
TR10_4 Configuration11.16
FEC & EFEC Configuration
FEC & EFEC
FEC is supported between Apollo and XDM
EFEC is not supported between Apollo and XDM
SD-FEC Soft Decision FEC
For Testing of 100Gb Rate
FEC Ignore Disable = RX (receiver side) expects to getFEC or EFEC from the other side
FEC Ignore Enable = RX (receiver) doesnt expect FECor EFEC from the other side
TR10_4 Configuration12.16
GCC Mode
From the optical port, move to the OTU Attributes:
84
8/9/2019 APOLLO ECI TELEKOM
86/176
TR10_4 Configuration13.16
Loopbacks
Client & Line ports supports Remote or Local loopbacks
Remote = Facility (Far End)
Local = Terminal (Near End)
TR10_4 Configuration14.16
Port Performance Monitoring
85
8/9/2019 APOLLO ECI TELEKOM
87/176
TR10_4 Configuration15.16
Port Alarms
TR10_4 Configuration16.16
TR10_4 Optical Parameters
86
8/9/2019 APOLLO ECI TELEKOM
88/176
TR100 Configuration1.20
TR100 Configuration
Apollo V4.1
Global Services Division
ECI Training Department
TR100 Configuration2.20
Content
Assignment
Modes: Transponder, Regenerator & IOP Protection
Line (LFF) Port Configuration
Client (CFP) Port Configuration
IOP Protection Configuration
87
8/9/2019 APOLLO ECI TELEKOM
89/176
TR100 Configuration3.20
Configuration of TR100
Slot Assignment
actual & expected type of the card is TR100
Two modes are supported: Transponder & Regenerator
TR100 Configuration4.20
Assignment Rules for OPT9624
Transponder mode:
0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22
Pair slots for the Regenerator:
0&2; 4&6; 12&14; 16&18; 20&22
Exception: regenerator mode, cannot
be assigned in slots 8 and 10
Pair slots for IOP Protection:
0&2; 4&6; 8&10; 12&14;
16&18; 20&22
88
8/9/2019 APOLLO ECI TELEKOM
90/176
TR100 Configuration5.20
Assignment Rules for OPT9608/03
OPT9608
Transponder mode:
0, 2, 4, 6
Pair slots for IOP Protection:
0&2; 4&6
Regenerator mode is not supported in OPT9608
OPT9603
Transponder mode:
0
TR100 Configuration6.20
Line (LFF) Port Configuration
Line - OTU4
Line needs wavelength definition:
89
8/9/2019 APOLLO ECI TELEKOM
91/176
TR100 Configuration7.20
Line (LFF) Port Configuration
Loopback of LINE side
From the Line Port:
Local
RemoteRemote Client Line
TR100 Configuration8.20
Line (LFF) Port Configuration
Laser Attributes
90
8/9/2019 APOLLO ECI TELEKOM
92/176
TR100 Configuration9.20
Line (LFF) Port Configuration
Basic & TTI Attributes
Basic Attributes:
TTI Attributes:
TR100 Configuration10.20
Line (LFF) Port Configuration
FEC Attributes:
GCC Attributes:
CD Attributes:
91
8/9/2019 APOLLO ECI TELEKOM
93/176
TR100 Configuration11.20
Line (LFF) Port Configuration
Optical & ONCP Parameters
Optical Parameters:
ONCP Parameters:
TR100 Configuration12.20
Client (CFP) Port Configuration
Three types of CFP client ports:
OTR100_SR10
OTR100_LR10
OTR100_LR4
All types support 100GbE
92
8/9/2019 APOLLO ECI TELEKOM
94/176
TR100 Configuration13.20
Client (CFP) Port Configuration
Basic Info:
Laser Info:
TR100 Configuration14.20
Client (CFP) Port Configuration
Maintenance Operation:
Loopback
Test Mode
93
8/9/2019 APOLLO ECI TELEKOM
95/176
TR100 Configuration15.20
Client (CFP) Port Configuration
Laser Attributes
TR100 Configuration16.20
Client (CFP) Port Configuration
CSF/TSF Action Type:
LF/RF Mode:
PCS Status:
94
8/9/2019 APOLLO ECI TELEKOM
96/176
TR100 Configuration17.20
IOP Protection Configuration
Example of two TR100 Cards
Slots U20 & U22
Choose left-handed card from the IOP Group:
U20
IOP Protection configuration done via the Client port
TR100 Configuration18.20
IOP Protection Configuration
Right click on the client port
Note: Client ports belonging to the same IOP Protection Groupmust be configured similarly with the same parameters!
95
8/9/2019 APOLLO ECI TELEKOM
97/176
TR100 Configuration19.20
Deleting IOP Protection
Deleting only via the main port:
TR100 Configuration20.20
Summary
Assignment
Modes: Transponder, Regenerator & IOP Protection
Line (LFF) Port Configuration
Client (CFP) Port Configuration
IOP Protection Configuration
96
8/9/2019 APOLLO ECI TELEKOM
98/176
CMR40 Configuration1/16
CMR40Configuration
Apollo
Global Services Division
ECI Training Department
CMR40 Configuration2/16
Content
CMR40 Configuration via STMS
Base card configuration
Port configurations
Client ports
Fixed line port
Alarms
PM
Maintenance
97
8/9/2019 APOLLO ECI TELEKOM
99/176
CMR40 Configuration3/16
CMR40 Configuration
CMR40 Configuration4/16
Ports Configuration
98
8/9/2019 APOLLO ECI TELEKOM
100/176
CMR40 Configuration5/16
Ports Configuration
CMR40 Configuration6/16
Ports Configuration
99
8/9/2019 APOLLO ECI TELEKOM
101/176
CMR40 Configuration7/16
Performance Monitoring
CMR40 Configuration8/16
Alarms
100
8/9/2019 APOLLO ECI TELEKOM
102/176
CMR40 Configuration9/16
Temperature
CMR40 Configuration10/16
Client Port Properties
101
8/9/2019 APOLLO ECI TELEKOM
103/176
CMR40 Configuration11/16
Client Port Properties Main
CMR40 Configuration12/16
Client Port Properties Transceiver
102
8/9/2019 APOLLO ECI TELEKOM
104/176
CMR40 Configuration13/16
Client Port Properties ETY Attributes
CMR40 Configuration14/16
Line Port Properties Main
103
8/9/2019 APOLLO ECI TELEKOM
105/176
CMR40 Configuration15/16
Line Port Properties OTU Attributes
CMR40 Configuration16/16
Line Port Properties
Optical Parameters
104
8/9/2019 APOLLO ECI TELEKOM
106/176
AOC10 Configuration1.22
AoC10 CardConfiguration
Apollo
Global Services Division
ECI Training Department
AOC10 Configuration2.22
Content
Slot assignment
Card status verification
Port configuration
Fiber connectivity
Maintenance
105
8/9/2019 APOLLO ECI TELEKOM
107/176
AOC10 Configuration3.22
Slot Assignment
The element is empty and therefore the slot assignmentbegins
AOC10 Configuration4.22
View after Assignment
Two AoC cards
Two ROADMs
Two amplifiers
ROADM
ROADM
OA-PA
OA-PA
AoC
AoC
106
8/9/2019 APOLLO ECI TELEKOM
108/176
AOC10 Configuration5.22
Card Status Verification
Following assignment all cards should be working
Right Click on Apollo shelf >> Element Status
AOC10 Configuration6.22
Port Configuration
Right click on the card
107
8/9/2019 APOLLO ECI TELEKOM
109/176
AOC10 Configuration7.22
AoC Port Configuration
AOC10 Configuration8.22
Fiber Connectivity
Right click on the Apollo shelves >> Show FiberConnectivities
108
8/9/2019 APOLLO ECI TELEKOM
110/176
AOC10 Configuration9.22
Create Fiber Connectivity
Click on the Create button on the bottom right side:
AOC10 Configuration10.22
Fiber Connectivity
109
8/9/2019 APOLLO ECI TELEKOM
111/176
8/9/2019 APOLLO ECI TELEKOM
112/176
AOC10 Configuration13.22
Edit Fiber Connectivity
Fiber connectivity can be edited when required
AOC10 Configuration14.22
Remote and Local loopbacks are supported on anyclient/line port
Each loopback should be loop and continue
Only one loopback at a time
Remote and Local Loopbacks
111
8/9/2019 APOLLO ECI TELEKOM
113/176
AOC10 Configuration15.22
Remote and Local Loopbacks
Remote Loopback - Signal is turned back towards theline
received signal is transmitted to the line and continues along theoriginal path
Local Loopback - Signal is turned back towards the
card
AOC10 Configuration16.22
AoC ALS
Disconnect on the Receiver (Rx) side shuts down thelaser toward the Transmit (Tx) side
112
8/9/2019 APOLLO ECI TELEKOM
114/176
AOC10 Configuration17.22
ALS Configuration
From the card, choose the required port:
From the Main button scroll down till Laser Info:
AOC10 Configuration18.22
AoC CSF
CSF Client Signal Failure
113
8/9/2019 APOLLO ECI TELEKOM
115/176
AOC10 Configuration19.22
AoC TSF
TSF Traffic Signal Failure
AOC10 Configuration20.22
AoC Drop and Continue
114
8/9/2019 APOLLO ECI TELEKOM
116/176
AOC10 Configuration21.22
AoC East / West Protection
AOC10 Configuration22.22
AoC Full Client Protection
115
8/9/2019 APOLLO ECI TELEKOM
117/176
Global Professional Services ECI Training ServicesECI Telecom Ltd.
This page is intentionally blank
116
8/9/2019 APOLLO ECI TELEKOM
118/176
Interfaces & Protocols1.41
CMR100 Configuration
Apollo
Global Services Division
ECI Training Department
Interfaces & Protocols2.41
Content
CMR100 assignment
Assignment rules for OPT9624/08/03
Line (LFF) port configuration
Client port configuration
IOP protection configuration
117
8/9/2019 APOLLO ECI TELEKOM
119/176
Interfaces & Protocols3.41
CMR100 Configuration via STMS
Slot Assignment
Actual & Expected type of the card is CMR100
Interfaces & Protocols4.41
Assignment Rules for OPT9624
Muxponder Expected Mode:
0, 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22
Paired slots for IOP Protection:
0&2; 4&6; 8&10; 12&14;
16&18; 20&22
118
8/9/2019 APOLLO ECI TELEKOM
120/176
Interfaces & Protocols5.41
Assignment Rules for OPT9608/03
OPT9608
Expected Muxponder mode:
0, 2, 4, 6
Pair slots for IOP Protection:
0&2; 4&6
OPT9603
Expected Muxponder mode: 0
Interfaces & Protocols6.41
Line (LFF) Port Configuration
Line Transceiver defined by default
Line Port Port 0
Client Ports: 1 to 10
119
8/9/2019 APOLLO ECI TELEKOM
121/176
Interfaces & Protocols7.41
Line (LFF) Port Configuration
Tx Wavelength definition:
From the Main window
Scroll down to the right bottom corner:
Interfaces & Protocols8.41
Line (LFF) Port Configuration
Loopbacks
Type: Local or Remote
Loop and Continue
From the Main window
Scroll down to the left bottom corner:
Local
RemoteRemote Client Line
120
8/9/2019 APOLLO ECI TELEKOM
122/176
Interfaces & Protocols9.41
Line (LFF) Port Configuration
Laser Info:
AlS State
Disable (Default)
Enable
Tx Enable:
Enable (Default)
Disable
Interfaces & Protocols10.41
Line (LFF) Port Configuration
Transceiver Laser Attributes:
121
8/9/2019 APOLLO ECI TELEKOM
123/176
Interfaces & Protocols11.41
Line (LFF) Port Configuration
OTU Attributes:
Basic Attributes:
TTI Attributes:
Interfaces & Protocols12.41
Line (LFF) Port Configuration
OTU Attributes
FEC Attributes: FEC Ignore Disable (By Default)
GCC Attributes: GCC Termination Disable (By Default)
CD Attributes:
122
8/9/2019 APOLLO ECI TELEKOM
124/176
Interfaces & Protocols13.41
Line (LFF) Port Configuration
Optical Parameters
Input & Output Parameters
Refresh in:
Default 1 min
Interfaces & Protocols14.41
Line (LFF) Port Configuration
At the end, return to the Main window
and click on Apply
123
8/9/2019 APOLLO ECI TELEKOM
125/176
Interfaces & Protocols15.41
Client Port Configuration
First Option: Example with ETY100GOC
Example with OTU2e
Interfaces & Protocols16.41
Client Port Configuration
Second Option:
Scroll down toward the bottom right corner:
If transceiver type is color:
124
8/9/2019 APOLLO ECI TELEKOM
126/176
Interfaces & Protocols17.41
Client Port Configuration
Port Basic Info
Operational Info, Alarm Master Mask & PM Monitor
Actual Tx Status: Must be On
Interfaces & Protocols18.41
Client Port Configuration
Laser Info
ALS State Disable by Default
Tx Enable Enable by Default
Maintenance Info
Loopback: Local or Remote (Default No Loopback)
Loop and Continue
125
8/9/2019 APOLLO ECI TELEKOM
127/176
Interfaces & Protocols19.41
Client Port Configuration
Transceiver Laser Attributes:
Interfaces & Protocols20.41
Client Port Configuration
OTU Attributes
Basic Attributes:
TTI Attributes:
126
8/9/2019 APOLLO ECI TELEKOM
128/176
Interfaces & Protocols21.41
Client Port Configuration
OTU Attributes
FEC Attributes: FEC Ignore Disable (By Default)
GCC Attributes: GCC Termination Disable (By Default)
CD Attributes:
Interfaces & Protocols22.41
Client Port Configuration
Optical Parameters
Input & Output Parameters
Refresh in:
Default 1 min
127
8/9/2019 APOLLO ECI TELEKOM
129/176
Interfaces & Protocols23.41
Client Port Configuration
At the end, back to the Main window
and perform Apply
Interfaces & Protocols24.41
IOP Protection Configuration
The characteristics of IOP protection scheme are:
1+1
Non-Revertive or Revertive
Uni-directional
Each port will switch independently
128
8/9/2019 APOLLO ECI TELEKOM
130/176
Interfaces & Protocols25.41
IOP Protection Configuration
Example of two CMR100 Cards
Choose left-handed card from
the IOP Group:
U20
IOP Protection configuration done
via the Client port
Interfaces & Protocols26.41
IOP Protection Configuration
Right click on the client port
Note: Client ports belonging to the same IOP Protection Group,must be configured similarly with the same parameters!
Port 1 in the both cards defined same: OTU2e
Port 2 in the both cards defined same: STM64
Port 3 in the both cards defined same: FC1200
129
8/9/2019 APOLLO ECI TELEKOM
131/176
Interfaces & Protocols27.41
IOP Protection Configuration
Note: Fiber Connectivity must be done before IOPProtection
Interfaces & Protocols28.41
Deleting IOP Protection
Deleting only via the main port:
130
8/9/2019 APOLLO ECI TELEKOM
132/176
ASON Technology1.26
Theory ofASON Technology
Apollo
Global Services Division
ECI Training Department
ASON Technology2.26
Content
ASON overview & general description
GMPLS overview & working mode
ASON framework
Control plane basic functions
ASON protection & restoration
ASON recovery types
131
8/9/2019 APOLLO ECI TELEKOM
133/176
ASON Technology3.26
ASON Overview
ASON Automatically Switched Optical Network
ASON functionality creates a network of NEs thatrecognize one another
If traffic fails somewhere in the network, a protectionpath is automatically found to reroute the traffic
When the main path is repaired, the traffic isautomatically reverted back by the system
The restoration path resources are released
ASON Technology4.26
ASON Overview
Suitable for sub lambda services and low capacity trails
Less complicated (no need to consider opticalimpairments)
Signal is terminated in each ODU-XC
Restoration is based on (SD) PM
Restoration modes could be recovered in second andless
132
8/9/2019 APOLLO ECI TELEKOM
134/176
ASON Technology5.26
ASON General Description
ASON uses a control plane & restoration based onGMPLS at the ODU_XC level
Enables automatic delivery, protection and restoration oftransport ODUk services:
ODUk: ODU0, ODU1, ODU2
Supported by Apollo OPT9624-H
Available only when the automatic package optional
feature is enabled
ASON Technology6.26
GMPLS Overview
GMPLS - Generalized Multi-Protocol Label Switching
GMPLS Protocol:
Supports and manages multiple types of switching technologiesother than packet interfaces & switching
Technologies such as TDM & L2 switching - Wavelength &
Fiber (port) switch
Enables ODUk and Lambda service provisioning
Multiple protection and restoration options
133
8/9/2019 APOLLO ECI TELEKOM
135/176
ASON Technology7.26
How does GMPLS Work?
Based on generalized labels
Composed of three main protocols:
Signaling protocol - Resource Reservation Protocol withTraffic Engineering extensions (RSVP-TE)
Routing protocol - Open Shortest Path First with TrafficEngineering extensions (OSPF-TE)
Link Management Protocol (LMP)
ASON Technology8.26
ASONFramework ITU-T G.8080
Architecture for the automatically switched opticalnetwork
Transport PlaneInterfacesUNI: User-Network InterfaceNNI: Network-Network InterfaceMNI: Management-Node InterfaceCCI: Connection Control Interface -between the control plane and the transport plane
CCI
I-NNI
MNI
UNI
Control Plane
ManagementP
lane
E-NNI
134
8/9/2019 APOLLO ECI TELEKOM
136/176
ASON Technology9.26
ASONFramework ITU-T G.8080
Management Plane
The plane that controls and monitors the data plane
(Operations, Administration, Maintenance and provisioning)
Control Plane
Middle plane that enables intelligent optical networking - addsdynamic monitoring & control
Consists of individual processors (control plane instances)within each Apollo NE
A dedicated MNI is used between the control plane and
NMS (Management Plane)
Transport Plane
Responsible for transporting services between endpoints usingthe switching equipment
ASON Technology10.26
Control Plane Basic Functions
Network Auto Discovery ( using OSPF)
Mechanisms for Neighbor Discovery & Topology Discovery
Cards, intra-node connectivity
Routing/Topology Advertisement using OSPF
Topology flooding information
Network topology discovery
Route computation
Connection Management Signaling using GMPLS +RSVP-TE
Automated provisioning and failure recovery
Automatic add and remove connections
135
8/9/2019 APOLLO ECI TELEKOM
137/176
ASON Technology11.26
Network Auto Discovery
Neighbor Discovery Each node builds a networktopology using the neighbor discovery function
Topology Discovery by NMS Builds the topology using:
Topology Maps
Consistency Check
Auto Discovery includes discovery of:
remote network element and remote port of the OTUk link
ASON Technology12.26
Routing/Topology using OSPF
Routing OSPF TE :
Responsible for automatic network topology discovery
Automatic resource discovery
Automatic route computation
Maintains a local topology database on each control planeinstance
OSPF LightSoft
136
8/9/2019 APOLLO ECI TELEKOM
138/176
ASON Technology13.26
Connection Signaling using RSVP
Provides the underlying mechanism for dynamic calland connection management
Handles connection requests, such as:
Connection creation or restoration
RSVP TE - Resource Reservation Protocol
Transport Layer protocol designed to reserve resources across
a network for an integrated services
ASON Technology14.26
Service Provisioning
GMPLS RSVP-TE path
OSPF
PATH
PATH
LightSoft
Discovery SignalingRouting
137
8/9/2019 APOLLO ECI TELEKOM
139/176
ASON Technology15.26
Protection against Failures
ASON protects a network against:
Multiple data-link failures
Equipment failure associated directly with the data-link
ODU failures when trails are SNCP protected
ASON Technology16.26
ASON Protection & Restoration
ASON enables automatic protection and restoration oftransport ODUk services:
Protection
Executed by the two end NEs
Capacity is configured across the network and NEs
No sharing backup resources Less than 50msec protection switching time
Restoration
No pre-allocated capacity
Network automatically calculates a new route based on availableresources
Services with low priority can be used on the capacity used forrestoration
Performed in more than 50msec
138
8/9/2019 APOLLO ECI TELEKOM
140/176
8/9/2019 APOLLO ECI TELEKOM
141/176
8/9/2019 APOLLO ECI TELEKOM
142/176
ASON Technology21.26
Restoration Protected (1+R)
Trail recovers within less than one second for any failureas long as the route is found from head-end to tail end
In SDH terms this is an unprotected trail with ASON
ASON Technology22.26
One Time SNCP & Restoration Protected (1+1+R)
Trail recovers within less than 50 ms for the first failureand less than one second for any consequent failure aslong as a route is found from the head-end to the tail-end
141
8/9/2019 APOLLO ECI TELEKOM
143/176
ASON Technology23.26
1+1+R Protection Scheme
LightSoft
P-Working
M-Working
P-Restoration
50 msec protection guarantee for multiple failures
ASON Technology24.26
SNCP & Restoration Protected (1++)
SNCP & Restoration Protected Forever
Trail recovers within less than 50 ms for any failure aslong as a route is found from the head-end to the tail-
end
142
8/9/2019 APOLLO ECI TELEKOM
144/176
ASON Technology25.26
Apollo ASON Restoration Modes
1++ 1+1+ 1+1
0 0
(1 )
0 2
0 1 /
,
,
,
ASON Technology26.26
ASON Summary
ASON Components:
Planes
Interfaces
Protocols
Links
143
8/9/2019 APOLLO ECI TELEKOM
145/176
Global Professional Services ECI Training ServicesECI Telecom Ltd.
This page is intentionally blank
144
8/9/2019 APOLLO ECI TELEKOM
146/176
Implementing ASON Technology1.32
ASON TechnologyImplementation
in Apollo
NMS LightSoft & STMS
Global Services Division
ECI Training Department
Implementing ASON Technology2.32
Content
License for the ASON technology
FIO cards parameters STMS
Creating links NMS
Creating OCH trails NMS
Creating ODU* trails NMS
Creating restoration of the LP NMS
1+R
1+1+R
1++
Maintenance operations
Useful CLI commands
145
8/9/2019 APOLLO ECI TELEKOM
147/176
Implementing ASON Technology3.32
ASON Configuration
What do we need to do to build an ASON Network? NMS License (V10 and higher) - Level Package 2
STMS License (V5.1 and higher) - Per Port
OPT9624H shelves
FIO cards
Create a Topology link
Create OCH Trails (Build ASON Data Link)
ODU XC * ( depends on the LP Service)
Create a light path - LP: 1+R; 1+1+R; 1++
Implementing ASON Technology4.32
ASON License in NMS & STMS
To be able to implement ASON check the licenses in:
NMS Level Package 2 STMS per port
NMS
STMS
146
8/9/2019 APOLLO ECI TELEKOM
148/176
Implementing ASON Technology5.32
Implementing ASON Technology6.32
Shelf Mode with FM1000-Fabric
Today only OPT9624H shelf support ASON Technology
For FIO cards assignment this configuration mode mustbe done:
Go to the Properties of the shelf
And check Shelf Mode:
147
8/9/2019 APOLLO ECI TELEKOM
149/176
8/9/2019 APOLLO ECI TELEKOM
150/176
Implementing ASON Technology9.32
Implementing ASON Technology10.32
Creating Links in the Optical Layer
Supports all types of FIO & Photonic (DWDM) cards
The ASON end points should be FIO cards
FIOMR_16/16B, FIO10_5/10_5B, FIO40, FIO100
FIO Cards represented by LEs
149
8/9/2019 APOLLO ECI TELEKOM
151/176
Implementing ASON Technology11.32
Creating OCH Trails
Before OCH trail creation:
Choose rate: OCH
Protection Types: Unprotected, Current, etc
Advanced Protection
Build ASON Data Link
Implementing ASON Technology12.32
OCH Layer
After OCH trail creation move to the OCH layer
If A is White OCH trail is Inconsistent orPending
If A is Yellow OCH trail: Active
150
8/9/2019 APOLLO ECI TELEKOM
152/176
Implementing ASON Technology13.32
Checking Link Availability
Shown on the Optical technology layer and on the OCHtechnology layer
For the ODU trails and the LP
Implementing ASON Technology14.32
ODU Trails
ODU trails support the following rates:
ODU1
ODU2
ODU2e
ODU3e
ODU4
151
8/9/2019 APOLLO ECI TELEKOM
153/176
8/9/2019 APOLLO ECI TELEKOM
154/176
Implementing ASON Technology17.32
LP Trail Creation
If ASON checkbox is checked, the Protection combo box has thefollowing list of values:
&
&
&
Implementing ASON Technology18.32
LP Completion Methods
Two ways to complete a Light Path
Auto-complete
Explicit Selection
153
8/9/2019 APOLLO ECI TELEKOM
155/176
Implementing ASON Technology19.32
1+R (Bronze) Restoration
1+R trail is an ASON trail that has only a Main path anda P2P topology
Implementing ASON Technology20.32
1+R (Bronze) Restoration
154
8/9/2019 APOLLO ECI TELEKOM
156/176
8/9/2019 APOLLO ECI TELEKOM
157/176
Implementing ASON Technology23.32
1+1+R (Silver) Restoration
1+1+R trail must have Main and Protection paths
Implementing ASON Technology24.32
1++ (Gold) Restoration
1++ trails must have Main and Protection paths
156
8/9/2019 APOLLO ECI TELEKOM
158/176
Implementing ASON Technology25.32
1++ (Gold) Restoration
The trail should contain main and protection LSPs
1++ is a trail with main and protection provisioned pathsthat is protected by dynamic restoration
Implementing ASON Technology26.32
1++ (Gold) Restoration
Purple line shows the Main - blue outline
shows where the actual traffic is
Light blue line
shows the protection
Current trafficMain
Protection
157
8/9/2019 APOLLO ECI TELEKOM
159/176
Implementing ASON Technology27.32
1++ (Gold) Restoration
Purple line shows the Main - blue line in the
middle shows where the actual traffic is
Light blue line
shows the protection
Current traffic
Main
Protection
Implementing ASON Technology28.32
Showing the Highlighted Trail
This icon shows us where the active route (active traffic)
is run
158
8/9/2019 APOLLO ECI TELEKOM
160/176
Implementing ASON Technology29.32
ASON Trail Maintenance Operations
Revert Manual Main Path
Revert Manual Protection Path
Revert Force Main Path
Revert Force Protection Path
Reroute Manual Main Path
Reroute Manual Protection Path
Implementing ASON Technology30.32
ASON Trail Export & Import
All ASON trail features that are supported from the GUIcan be supported through XML files
ASON trails can be exported to CSV files
159
8/9/2019 APOLLO ECI TELEKOM
161/176
Implementing ASON Technology31.32
Alarms, Current PM, PMH
The list of alarms and probable cause events:
Restoration Attempt Timeout
Restoration Admission Control Failure
Restoration Failure No Route Found
Faulty Trail
Trail Degraded
Restoration event
Reversion event
Implementing ASON Technology32.32
Useful CLI Commands
To check the ASON alarms & status via CLI:
root@AsonNE1xx# run show mpls interface detail
root@AsonNE1xx# run show chassis alarms
root@AsonNE1xx# show trails
root@AsonNE1xx# show cross-connects
root@AsonNE1xx# run show protection traffic
160
8/9/2019 APOLLO ECI TELEKOM
162/176
DNI LP Configuration1/14
LP DNI Configuration
NMS LightSoft
Global Services Division
ECI Training Department
DNI LP Configuration2/14
Content
Topology
Protection Scheme
Prerequisite
DNI LP Trail Configuration
DNI Cross-Connects in STMS
DNI Cross-Connects CLI
161
8/9/2019 APOLLO ECI TELEKOM
163/176
DNI LP Configuration3/14
Topology
Apollo-85 Apollo-86 Apollo-87Apollo-88Apollo-89
DNI LP Configuration4/14
Protection Scheme
Main
Protection
DNI Bridge
Apollo-85 Apollo-86 Apollo-87Apollo-88Apollo-89
162
8/9/2019 APOLLO ECI TELEKOM
164/176
DNI LP Configuration5/14
Prerequisites
1. Slot assignment and ports configuration
2. Topology links
3. OMS and OCH trails
DNI LP Configuration6/14
Topology in LightSoft
163
8/9/2019 APOLLO ECI TELEKOM
165/176
DNI LP Configuration7/14
DNI LP (LightPath) Trail
Open Create Trail window
Select the endpoints of the LP trail (In this example:STM64 port on C1 port of TR10_4 on both sides)
DNI LP Configuration8/14
DNI LP Trail
164
8/9/2019 APOLLO ECI TELEKOM
166/176
DNI LP Configuration9/14
DNI LP Trail
Open the Trail list window
Select the previously configured LP trail
DNI LP Configuration10/14
DNI Cross-Connects
Right click on FIO(DNI node) and select CrossConnection
165
8/9/2019 APOLLO ECI TELEKOM
167/176
DNI LP Configuration11/14
DNI Cross-Connects in STMS
,
DNI LP Configuration12/14
DNI Cross-Connects in STMS
166
8/9/2019 APOLLO ECI TELEKOM
168/176
DNI LP Configuration13/14
DNI Cross-Connects in CLI
DNI LP Configuration14/14
Summary
Topology
Protection Scheme
Prerequisite
DNI LP Trail Configuration
DNI Cross-Connects in STMS
DNI Cross-Connects CLI
167
8/9/2019 APOLLO ECI TELEKOM
169/176
Global Professional Services ECI Training ServicesECI Telecom Ltd.
This page is intentionally blank
168
8/9/2019 APOLLO ECI TELEKOM
170/176
DRI LP Configuration1/12
LP DRI Configuration
NMS LightSoft
Global Services Division
ECI Training Department
DRI LP Configuration2/12
Content
Topology
Protection Scheme
Prerequisite
DRI LP Trail Configuration
169
8/9/2019 APOLLO ECI TELEKOM
171/176
DRI LP Configuration3/12
Topology
Apollo-85
Apollo-87
Apollo-86Apollo-89
DRI LP Configuration4/12
Protection Scheme
Main
Protection
DRI Bridge
Apollo-85
Apollo-87
Apollo-86Apollo-89
170
8/9/2019 APOLLO ECI TELEKOM
172/176
DRI LP Configuration5/12
Prerequisites
1. Slot assignment and ports configuration
2. Topology links
3. OMS and OCH trails
DRI LP Configuration6/12
Topology in LightSoft
171
8/9/2019 APOLLO ECI TELEKOM
173/176
DRI LP Configuration7/12
DRI LP (LightPath) Trail
Open Create trail window
Select the endpoints of the LP trail (In this example:STM64 port on C1 port of TR10_4 on both sides)
DRI LP Configuration8/12
DRI LP Trail
172
8/9/2019 APOLLO ECI TELEKOM
174/176
DRI LP Configuration9/12
DRI LP Trail
Open the Trail list window
Select the previously configured LP trail
DRI LP Configuration10/12
DRI LP Trail
Resource Tree
Bridge 1 - Main
Bridge 1 - Protection
173
8/9/2019 APOLLO ECI TELEKOM
175/176
8/9/2019 APOLLO ECI TELEKOM
176/176