Professional Documents
Culture Documents
STMS 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 Configuration
Theory of ASON Technology
ASON Technology Implementation in Apollo
DNI Configuration
DRI Configuration
3
19
27
39
47
53
71
79
87
97
105
117
131
145
161
169
STMS Integrated
ShadeTree Management Suite
STMS Overview
Content
Introduction
STMS architecture and platforms
STMS client
Configuration features
Faults
PM Performance Monitoring
DB Backup
2/30
STMS Overview
Introduction
STMS (ShadeTree Management Suite) is the element
management (EMS), service provisioning and
monitoring solution for the Apollo (OPT9600) products
family:
OPT9624H & OPT9624L
OPT9608
OPT9603
Fault
Configuration
Accounting
Performance
Security
3/30
STMS Overview
TMN Architecture
Business/Service
Management
Network
Management
Third-party NMS
LightSoft NMS
NMS client
Java RMI
CORBA/MTNM (TMF-814)
Element
Management
STMS Client
JDBC
Java
RMI
Oracle
Database
STMS
SNMP
Network
Element
OPT9603
OPT9608
4/30
OPT9624
STMS Overview
Inventory management
Alarm management
PMs
Topology links/Optical trails configuration
ODU XC Configuration
GUI cut-through
STMS
5/30
STMS Overview
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
6/30
STMS Overview
STMS Client
STMS Client is a Java-based GUI from which operators
can manage STMS server
The STMS Client can run as a standalone application
on Windows, Linux, Solaris or any other platform that
supports Java
Client must resolve the host-name of the STMS server
Configure DNS server
Or edit hosts file
7/30
STMS Overview
Entering STMS
1. In NMS LightSoft, go to the Physical (EMS) layer
2. Right click the STMS and Open
8/30
STMS Overview
Navigating STMS
9/30
STMS Overview
Navigating STMS
Network Explorer
Displays a representation of the network in the form of a tree
hierarchy
10/30
STMS Overview
Creating a Group
Navigating STMS
Customer Explorer
Displays all of the services and XS assigned to a specific customer
12/30
STMS Overview
Inventory View
Graphical representation of the chassis
13/30
STMS Overview
Slot Assignment
14/30
STMS Overview
Installed Modules
The Show Actual checkbox shows which modules are
physically
installed in
the chassis
15/30
STMS Overview
16/30
STMS Overview
10
17/30
STMS Overview
Fiber Connectivity
18/30
STMS Overview
11
Cross Connections
19/30
STMS Overview
2
3
20/30
STMS Overview
12
Fault Management
Alarm management
21/30
STMS Overview
Fault Management
Displays Network events
STMS Overview
13
PM
23/30
STMS Overview
PM
24/30
STMS Overview
14
NE DB Backup
1) Tools -> Configuration Manager
25/30
STMS Overview
NE DB Backup
To create an immediate one time backup, click on Create
26/30
STMS Overview
15
NE DB Backup
The backup file is created and listed in the Backup
Manager tab.
27/30
STMS Overview
Backup Scheduler
Go to Backup Scheduler tab and Click on Create,
28/30
STMS Overview
16
Restore DB
Right click on the DB file from the Backup Manager list
and select Restore
29/30
STMS Overview
Summary
Introduction
EMS for Apollo products family
STMS Client
STMS can work as standalone
Configuration Features
Ports, Fiber Connectivity, Cross-Conections
Faults
Alarms, Logs and Events
PM
DB Backup
30/30
STMS Overview
17
18
STMS Alarms
STMS Alarms
Content
Alarm Hierarchy
Alarm Types
Alarm Window
Historical Alarms
Alarm Details
Managing Alarms
Alarm Preferences
2/16
STMS Alarms
19
Alarm Hierarchy
In the STMS, alarm indications are propagated through
the object hierarchy and are displayed up to the highest
level
NE
Card
Alarm
Port
Unit
3/16
STMS Alarms
Alarm Types
Alarms conditions are classified according to severity
levels and are visually reflected in the STMS Client
window using the following colors and indications:
Severity
Color
Indicator
Minor
Yellow
Major
Orange
Critical
Red
Clear
White/Green
None
4/16
20
Description
Alarm Window
Table view (the default view) displays alarms in a simple
table format
Each alarm is displayed as a separate row in the table
In table view, double-clicking a row opens the property sheet for
the object associated with the alarm
5/16
STMS Alarms
Alarm Window
Severity
Description
Ack
Time
Clear Time
Source
Name
Severity
Type
SA
Description
6/16
STMS Alarms
21
Historical Alarms
By default, the STMS does not maintain nor display
information about historical alarms, only active alarms
STMS Alarms
Historical Alarms
Viewing historical alarms
8/16
STMS Alarms
22
Alarm Details
Right Click
9/16
STMS Alarms
Alarm Details
Column
Time
10/16
Description
The time of the Alarm
Element Name
Source NE
Trap Name
Severity
Service Affecting
Acknowledged
Acknowledged by
Acknowledged at
Displays the date and the time that the alarm was
acknowledged
Annotation
Short Description
Detailed Description
23
Managing Alarms
Acknowledging Alarms
Right Click
11/16
STMS Alarms
12/16
STMS Alarms
24
13/16
STMS Alarms
Alarm Preferences
14/16
STMS Alarms
25
Alarm Preferences
15/16
STMS Alarms
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
16/16
STMS Alarms
26
NMS LightSoft V6
Introduction
LightSoft GUI
Management Architecture
OSS
Element
Management
Layer
LightSoft
EMSEMS-BGF
Other EMSs
Managed
Equipment
BG line
XDM line
2.21
Other
equipment
LightSoft GUI
27
ECI Button
Tabs no menus
3.21
LightSoft GUI
ECI Button
ECI button contains the Help and About LightSoft
options
The ECI Button menu cannot be customized
4.21
LightSoft GUI
28
LightSoft Ribbon
The LightSoft ribbon is maximized or minimized
Minimized
Maximized
To maximize or minimize:
Double click a tab
Ctrl + F1
View tab
click on Ribbon
5.21
LightSoft GUI
Technology
Layers
Consistency
Indicators
Alarm
Counters
6.21
LightSoft GUI
29
Technology Layers
LightSoft has traffic from
different technology types
You can see the elements
processing the different traffic types:
Optical (WDM, OTN)
SDH
Ethernet & MPLS
Example:
If you go to the ETH/MPLS layer, you see where in your
topology you have Ethernet or MPLS cards & traffic
7.21
LightSoft GUI
Physical (Site)
Physical (EMS)
SDH/SONET
Optical (OTN)
OCH
Ethernet/MPLS Physical
(EMS)
Physical
(Site)
SDH/
SONET
Optical
(OTN)
Ethernet/MPLS
8.21
LightSoft GUI
30
Example of Layers
Physical (Site):
This layer shows your
whole network, including
3rd party equipment
(technology transparent)
ETH/MPLS
This layer shows your
Ethernet and MPLS
switches in your
network
9.21
LightSoft GUI
Elements
ME/NE: Managed/Network Element
Groups
10.21
LightSoft GUI
31
Topology Links
Represent the physical connections between elements
Must be created before provisioning traffic
11.21
LightSoft GUI
Provisioned Traffic
Trail List shows the trails in the network
12.21
LightSoft GUI
32
Inserting an Element
After
Before
13.21
LightSoft GUI
Consistency Indicators
Client
(GUI)
Server
(Database)
EMS XDM
DB
EMS
BG DB
BroadGate
XDM
14.21
33
Other
EMS DB
Other
transport
equipment
LightSoft GUI
Alarm Counters
Alarm types
Red
Yellow
15.21
LightSoft GUI
16.21
LightSoft GUI
34
Hot Keys
Pressing Alt toggles hot key tips
Once the are tips displayed, type the letter to open that
tab level 1
17.21
LightSoft GUI
LightSoft GUI
35
Tree
19.21
LightSoft GUI
View Functions
Zoom & Navigation
Seeing 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)
Map
20.21
Move
36
LightSoft GUI
Summary
Tabs No More Menus
ECI Button
LightSoft Ribbon
Minimizing/Maximizing
Categories in each tab
LightSoft GUI
37
38
Elements
Content
2.15
Elements
39
Physical (Site)
Physical (EMS)
SDH/SONET
Optical (OTN)
OCH
Ethernet/MPLS Physical
(EMS)
Physical
(Site)
SDH/
SONET
Optical
(OTN)
Ethernet/MPLS
3.15
Elements
Creating an ME
2
1
1. Switch to Physical (EMS) layer
2. Right click on the relevant EMS
4.15
Elements
40
5.15
Elements
Creating an LE
1
Select resource(s) to
be part of the LE
4
4. Click to place the LE on
the map
6.15
Elements
41
7.15
Elements
Creating a UME
1
3
4. Click to place the UME
on the map
8.15
42
1
Switch to Physical (Site) layer
3,4
3. Change configuration
4. Apply
9.15
Elements
Groups
Groups allow you to organize the network hierarchically:
According to Physical location rack, site, city
According to Technological topology chain, ring
10.15
Elements
43
Creating a Group
2
1
Select elements to include in
the group
4,5
11.15
Elements
!
The element is no longer
part of the group
12.15
Elements
44
!
See that the element is
now part of the group
13.15
Elements
Map Operations
Expand
Collapse
Collapse all
14.15
Elements
45
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
15.15
Elements
46
Topology Links
Topology Links
A topology link represents the physical connection (fiber
or 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
2.12
Topology Links
47
3.12
Topology Links
2
Select 2 endpoints
*Only resources that
support the rate
selection are available
3
4.12
Topology Links
48
5.12
Topology Links
Explanation
Technology Layer
Media Type
Media Subtype
Length (km/mile)
Protection
SRLG (Ducts)
Ring Name
6.12
Topology Links
49
Explanation
Assigned Cost
(1-1000)
Quality
(Best 1..5 Worst)
Dispersion
(ps*nm/km)
Path Trace
Configuration
button
7.12
Topology Links
8.12
Topology Links
50
Red
Orange
Yellow
Green
9.12
Topology Links
Internal Links
Internal link A link between two ports of one element
When an arrow appears next to the ME- it indicates that
an internal link exists in the element
10.12
Topology Links
51
11.12
Topology Links
Summary
Topology Links
Between elements
Internal links
12.12
Topology Links
52
Optical Trails
NMS LightSoft
Optical Trails
Content
2.13
Optical Trails
53
Src
TR/CMR/AoC
M
U
X
OPS-1
D
M
U
X
OFA
OTM
OTM
TRP/CMR/AoC
Snk
OPS-1
OMS
OCH
LP
3.13
Optical Trails
4.13
Optical Trails
54
5.13
Optical Trails
6.13
Optical Trails
55
3
2
7.13
Optical Trails
8.13
Optical Trails
56
9.13
Optical Trails
10.13
Optical Trails
57
2
3
11.13
Optical Trails
Creating LP Trails
12.13
Optical Trails
58
Content
Creating Logical Elements
Creating UMEs for clients
Topology links
OPS-1
OTM
Optical Trails
OMS
OCH
ODU
LP
13.13
Optical Trails
59
NMS LightSoft
Optical Trails
Optical Trails
UME Enhancements
New types - Transponder, Regenerator
2.20
Optical Trails
60
Optical Trails
4.20
Optical Trails
61
Optical Trails
6.20
Optical Trails
62
7.20
Optical Trails
8.20
Optical Trails
63
9.20
Optical Trails
Src
SIO/TRP
SIO/TRP
M
U
X
OPS_1
OFA
OTM
OTM
Snk
D
M
U
X
OPS_1
OMS
OCH
LP
10.20
Optical Trails
64
11.20
Optical Trails
12.20
Optical Trails
65
OMS
OCH
LP
High Order ( VC-4 or EoS)
13.20
Optical Trails
14.20
Optical Trails
66
15.20
Optical Trails
16.20
Optical Trails
67
17.20
Optical Trails
Optical Trails
68
19.20
Optical Trails
TRP1
OADMG
TRP2
M
U
X
D
M
U
X
add
OFA1
OFA2
OFA1
drop
TRP
OFA2
Single card
drop
Node A
2
2
D
M
U
X
TRP1
TRP2
TRP
add
OFA2
Node C
Node B
Single card
add
OFA1
OFA2
drop
Single
card
OADMG
20.20
OFA1
Single
card
M
U
X
TRP2
TRP1
Optical Trails
69
70
TCI in Lightsoft
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)
2.16
TCI in Lightsoft
71
Client
(GUI)
Server
(Database)
EMS
XDM
XDM
EMS
BG
Broad Gate
Other
EMS
Other
transport
equipment
3.16
TCI in Lightsoft
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 craft
terminal level
XCs were accidently deleted from the EMS
Trails were deleted from the NMS while performing
maintenance operations
4.16
TCI in Lightsoft
72
Inconsistency Types
Red flag
Yellow flag
Network (EMS)
info is:
Database (NMS)
info is:
Completing the
partial info is:
Partial
Full
Full
Partial
Traffic affecting
Required mode:
Master
Monitor
TCI in Lightsoft
TCI Counters
TCI in Lightsoft
73
TCI Window
To open TCI window click the Trail Consistency icon
Tool bar
Parameters
7.16
TCI in Lightsoft
8.16
TCI in Lightsoft
74
Inconsistency Types
When a trail exists in one window but not in the other:
If the network trail is missing, the DB trail should be
imposed on the network (network = EMS DB)
If the DB trail is missing, the network trail should be
admitted to the DB (DB = NMS DB)
9.16
TCI in Lightsoft
Monitor mode:
Monitor modeactions only on the DB are
available
Master modeactions on the Network are
available too
Dropdown list:
Choose level of TCI to
process
10.16
Recommended to check
TCI in Lightsoft
75
TCI in Lightsoft
TCI in Lightsoft
76
Corresponding
in Grey
Yellow
Blue
13.16
TCI in Lightsoft
Yellow
Blue
Condition
MatchingThe DB and
Network trails
are exactly
equivalent
Partially
MatchingThe DB trail has
more XCs than
the Network trail
Action
needed
none
Impose DB trail
to the Network
14.16
TCI in Lightsoft
77
Additional Windows
Queue WindowDisplays the selected trail (admitted or imposed)
After activating displays the action status (success or
failure)
Imposed and Admitted Trails WindowsDisplays the trails that were automatically
admitted/imposed
Event List WindowDisplays information about problems that may occur in
the synchronization process
15.16
TCI in Lightsoft
Summary
16.16
TCI in Lightsoft
78
TR10_4 Configuration
Apollo
TR10_4 Configuration
2.16
TR10_4 Configuration
79
OTU2/2e
3.16
Y-Protection
(0)Client -> Line (1 + 2)
Configuration
TR10_4 Configuration
4.16
TR10_4 Configuration
80
3
2
5.16
TR10_4 Configuration
Y Protection
Only the first Client port - 0 can be in Y Protection
6.16
TR10_4 Configuration
81
7.16
TR10_4 Configuration
1
2
3
8.16
TR10_4 Configuration
82
9.16
TR10_4 Configuration
Scroll down:
10.16
TR10_4 Configuration
83
TR10_4 Configuration
GCC Mode
From the optical port, move to the OTU Attributes:
2
12.16
TR10_4 Configuration
84
Loopbacks
Client & Line ports supports Remote or Local loopbacks
Remote = Facility (Far End)
Local = Terminal (Near End)
13.16
TR10_4 Configuration
14.16
TR10_4 Configuration
85
Port Alarms
3
2
15.16
TR10_4 Configuration
16.16
TR10_4 Configuration
86
TR100 Configuration
Apollo V4.1
TR100 Configuration
Content
Assignment
Modes: Transponder, Regenerator & IOP Protection
Line (LFF) Port Configuration
Client (CFP) Port Configuration
IOP Protection Configuration
2.20
TR100 Configuration
87
Configuration of TR100
Slot Assignment
actual & expected type of the card is TR100
3.20
TR100 Configuration
4.20
TR100 Configuration
88
5.20
TR100 Configuration
2
3
6.20
TR100 Configuration
89
Client
100GbE
CFP
Line
Remote
OTU4
LFF
Local
7.20
TR100 Configuration
8.20
TR100 Configuration
90
Basic Attributes:
TTI Attributes:
9.20
TR100 Configuration
GCC Attributes:
CD Attributes:
10.20
TR100 Configuration
91
Optical Parameters:
ONCP Parameters:
11.20
TR100 Configuration
12.20
TR100 Configuration
92
Laser Info:
13.20
TR100 Configuration
Test Mode
14.20
TR100 Configuration
93
15.20
TR100 Configuration
LF/RF Mode:
PCS Status:
16.20
TR100 Configuration
94
17.20
TR100 Configuration
18.20
TR100 Configuration
95
19.20
TR100 Configuration
Summary
Assignment
Modes: Transponder, Regenerator & IOP Protection
Line (LFF) Port Configuration
Client (CFP) Port Configuration
IOP Protection Configuration
20.20
TR100 Configuration
96
CMR40
Configuration
Apollo
CMR40 Configuration
Content
CMR40 Configuration via STMS
Base card configuration
Port configurations
Client ports
Fixed line port
Alarms
PM
Maintenance
2/16
CMR40 Configuration
97
CMR40 Configuration
1
3/16
CMR40 Configuration
Ports Configuration
1
4/16
CMR40 Configuration
98
Ports Configuration
4
5/16
CMR40 Configuration
Ports Configuration
6/16
CMR40 Configuration
99
Performance Monitoring
1
7/16
CMR40 Configuration
Alarms
1
3
8/16
CMR40 Configuration
100
Temperature
9/16
CMR40 Configuration
10/16
CMR40 Configuration
101
11/16
CMR40 Configuration
12/16
CMR40 Configuration
102
13/16
CMR40 Configuration
14/16
CMR40 Configuration
103
15/16
CMR40 Configuration
16/16
CMR40 Configuration
104
AoC10 Card
Configuration
Apollo
AOC10 Configuration
Content
Slot assignment
Card status verification
Port configuration
Fiber connectivity
Maintenance
2.22
AOC10 Configuration
105
Slot Assignment
The element is empty and therefore the slot assignment
begins
3.22
AOC10 Configuration
Two amplifiers
OA-PA
ROADM
AoC
OA-PA
ROADM
AoC
4.22
AOC10 Configuration
106
5.22
AOC10 Configuration
Port Configuration
Right click on the card
6.22
AOC10 Configuration
107
7.22
AOC10 Configuration
Fiber Connectivity
Right click on the Apollo shelves >> Show Fiber
Connectivities
8.22
AOC10 Configuration
108
9.22
AOC10 Configuration
Fiber Connectivity
Fiber connectivity = Internal
10.22
AOC10 Configuration
109
11.22
AOC10 Configuration
12.22
AOC10 Configuration
110
13.22
AOC10 Configuration
Local loopback
AOC10 Configuration
111
15.22
AOC10 Configuration
AoC ALS
Disconnect on the Receiver (Rx) side shuts down the
laser toward the Transmit (Tx) side
16.22
AOC10 Configuration
112
ALS Configuration
From the card, choose the required port:
17.22
AOC10 Configuration
AoC CSF
CSF Client Signal Failure
18.22
AOC10 Configuration
113
AoC TSF
TSF Traffic Signal Failure
19.22
AOC10 Configuration
20.22
AOC10 Configuration
114
21.22
AOC10 Configuration
22.22
AOC10 Configuration
115
116
CMR100 Configuration
Apollo
Content
CMR100 assignment
Assignment rules for OPT9624/08/03
Line (LFF) port configuration
Client port configuration
IOP protection configuration
2.41
117
3.41
4.41
118
OPT9603
Expected Muxponder mode:
0
5.41
119
7.41
Line Remote
OTU4
LFF
8.41
120
Tx Enable:
Enable (Default)
Disable
9.41
10.41
121
Basic Attributes:
TTI Attributes:
11.41
CD Attributes:
12.41
122
Refresh in:
Default 1 min
13.41
14.41
123
1
15.41
16.41
124
17.41
Maintenance Info
Loopback: Local or Remote (Default No Loopback)
Loop and Continue
18.41
125
19.41
Basic Attributes:
TTI Attributes:
20.41
126
CD Attributes:
21.41
Refresh in:
Default 1 min
22.41
127
23.41
24.41
128
26.41
129
27.41
28.41
130
Theory of
ASON Technology
Apollo
ASON Technology
Content
ASON overview & general description
GMPLS overview & working mode
ASON framework
Control plane basic functions
ASON protection & restoration
ASON recovery types
2.26
ASON Technology
131
ASON Overview
ASON Automatically Switched Optical Network
ASON functionality creates a network of NEs that
recognize one another
If traffic fails somewhere in the network, a protection
path is automatically found to reroute the traffic
When the main path is repaired, the traffic is
automatically reverted back by the system
The restoration path resources are released
3.26
ASON Technology
ASON Overview
Suitable for sub lambda services and low capacity trails
Less complicated (no need to consider optical
impairments)
Signal is terminated in each ODU-XC
Restoration is based on (SD) PM
Restoration modes could be recovered in second and
less
4.26
ASON Technology
132
5.26
ASON Technology
GMPLS Overview
GMPLS - Generalized Multi-Protocol Label Switching
GMPLS Protocol:
Supports and manages multiple types of switching technologies
other 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
6.26
ASON Technology
133
7.26
ASON Technology
Management Plane
I-NNI
8.26
Control Plane
E-NNI
MNI
UNI
CCI
Transport Plane
Interfaces
UNI: User-Network Interface
NNI: Network-Network Interface
MNI: Management-Node Interface
CCI: Connection Control Interface -between the control plane and the transport ASON
plane
Technology
134
Control Plane
Middle plane that enables intelligent optical networking - adds
dynamic 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 using
the switching equipment
9.26
ASON Technology
10.26
ASON Technology
135
11.26
ASON Technology
OSPF
12.26
ASON Technology
136
13.26
ASON Technology
Service Provisioning
GMPLS RSVP-TE path
LightSoft
OSPF
PATH
PATH
Discovery
14.26
Routing
Signaling
ASON Technology
137
15.26
ASON Technology
Restoration
No pre-allocated capacity
Network automatically calculates a new route based on available
resources
Services with low priority can be used on the capacity used for
restoration
Performed in more than 50msec
16.26
ASON Technology
138
Restoration Benefits
Restoration increases the capacity in the network
Increases network reliability by providing recovery for
multiple failures
Providing different quality of service for different
services
17.26
ASON Technology
1+1
Unprotected
Service
Dynamic
Path restoration
18.26
ASON Technology
139
19.26
ASON Technology
20.26
ASON Technology
140
21.26
ASON Technology
22.26
ASON Technology
141
LightSoft
M-Working
P-Restoration
P-Working
ASON Technology
24.26
ASON Technology
142
Highest
Protection
Scheme
Protected
Forever
Lowest
Protected and
Restored
Protected
Restoration
Unprotected
Protection
Method
1++
1+1+R
1+1
Dynamic path
Restoration
Non
Protection Time
< 50msec
<50msec
(1st failure)
>50msec 2nd
onwards
< 50msec
1 sec
N/A
Capacity
Consumed
Highest
Higher
Lower
Lowest
Applications
High Priority
Customers
Voice, Voice
mobile, fix
enterprise
Telemetry,
Internal data
network
25.26
ASON Technology
ASON Summary
ASON Components:
Planes
Interfaces
Protocols
Links
26.26
ASON Technology
143
144
ASON Technology
Implementation
in Apollo
NMS LightSoft & STMS
Global Services Division
ECI Training Department
1.32
Content
Maintenance operations
Useful CLI commands
2.32
145
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++
3.32
STMS
NMS
4.32
146
STMS
5.32
6.32
147
7.32
8.32
148
NMS
9.32
10.32
149
Advanced Protection
Build ASON Data Link
11.32
OCH Layer
After OCH trail creation move to the OCH layer
If A is White OCH trail is Inconsistent or
Pending
If A is Yellow OCH trail: Active
12.32
150
13.32
ODU Trails
ODU trails support the following rates:
ODU1
ODU2
ODU2e
ODU3e
ODU4
14.32
151
15.32
16.32
152
LP Trail Creation
If ASON checkbox is checked, the Protection combo box has the
following list of values:
1+R (Bronze)
1+1+R (Silver)
1++ (Gold)
17.32
LP Completion Methods
Two ways to complete a Light Path
Auto-complete
Explicit Selection
18.32
153
19.32
20.32
154
Trail List
To be able to see the ASON Path State in the Trail List:
Click on the Configure Columns square
Click on ASON Path State
21.32
22.32
155
23.32
24.32
156
25.32
Current traffic
Main
Protection
26.32
157
Main
Protection
Current traffic
27.32
28.32
158
29.32
30.32
159
31.32
32.32
160
LP DNI Configuration
NMS LightSoft
DNI LP Configuration
Content
Topology
Protection Scheme
Prerequisite
DNI LP Trail Configuration
DNI Cross-Connects in STMS
DNI Cross-Connects CLI
2/14
DNI LP Configuration
161
Topology
Apollo-85
Apollo-86
FIO10_5
MUX
FIO10_5
FIO10_5
MUX
MUX
MUX
TR10_4
MUX
Apollo-87
TR10_4
FIO10_5
MUX
MUX
Apollo-88
MUX
Apollo-89
3/14
DNI LP Configuration
Protection Scheme
Apollo-89
Apollo-88
Apollo-85
Apollo-86
Apollo-87
Main
Protection
DNI Bridge
4/14
DNI LP Configuration
162
Prerequisites
1. Slot assignment and ports configuration
2. Topology links
3. OMS and OCH trails
5/14
DNI LP Configuration
Topology in LightSoft
6/14
DNI LP Configuration
163
7/14
DNI LP Configuration
DNI LP Trail
8/14
DNI LP Configuration
164
DNI LP Trail
Open the Trail list window
Select the previously configured LP trail
9/14
DNI LP Configuration
DNI Cross-Connects
Right click on FIO(DNI node) and select Cross
Connection
10/14
DNI LP Configuration
165
DNI cross-connects
11/14
DNI LP Configuration
FIO10_5
FIO10_5
FIO10_5
FIO10_5
2
12/14
DNI LP Configuration
166
FIO10_5
FIO10_5
4
8
FIO10_5
FIO10_5
2
8
13/14
DNI LP Configuration
Summary
Topology
Protection Scheme
Prerequisite
DNI LP Trail Configuration
DNI Cross-Connects in STMS
DNI Cross-Connects CLI
14/14
DNI LP Configuration
167
168
LP DRI Configuration
NMS LightSoft
DRI LP Configuration
Content
Topology
Protection Scheme
Prerequisite
DRI LP Trail Configuration
2/12
DRI LP Configuration
169
Topology
Apollo-87
FIO10_5
FIO10_5
FIO10_5
Apollo-85
Apollo-86
TR10_4
TR10_4
FIO10_5
Apollo-89
FIO10_5
FIO10_5
FIO10_5
FIO10_5
3/12
DRI LP Configuration
Protection Scheme
Apollo-87
Apollo-86
Apollo-89
Apollo-85
Main
Protection
DRI Bridge
4/12
DRI LP Configuration
170
Prerequisites
1. Slot assignment and ports configuration
2. Topology links
3. OMS and OCH trails
5/12
DRI LP Configuration
Topology in LightSoft
6/12
DRI LP Configuration
171
7/12
DRI LP Configuration
DRI LP Trail
Select maximum
number of DRI
bridges (up to 16)
Check the DRI box
8/12
DRI LP Configuration
172
DRI LP Trail
Open the Trail list window
Select the previously configured LP trail
9/12
DRI LP Configuration
DRI LP Trail
Resource Tree
Bridge 1 - Main
Bridge 1 - Protection
10/12
DRI LP Configuration
173
DRI LP Trail
Apollo-87
FIO10_5
FIO10_5
FIO10_5
3
4
FIO10_5
1
2
1 4
3 2
Apollo-85
FIO10_5
FIO10_5
FIO10_5
FIO10_5
11/12
DRI LP Configuration
Summary
Topology
Protection Scheme
Prerequisite
DRI LP Trail Configuration
12/12
DRI LP Configuration
174