IP packet communication MPLS GMPLS 1/6

A The information is trasmitted in pakets, each

B packets contains the source addres and the
destination address.
Each node of the network (router) is able to route
packets following the roules indicated in the
routing table

Routing table
a 1 2
A c Router Target Next Router
5
3 2 B Port

3 2 Destination to use

5 1 a B b 3

4 1 b B c 1
b
c B locall 2

Problems:
Consequences: Solution:
-Sky roketing of the attached nodes
Bandwith demand increases
-Introduction of new applications
Routing calculation time
Label switching
-Routers are the bottelneck of the increases
network
-Huge routing tables
1
 IP packet communication MPLS GMPLS 2/6
A label is assigned to each IP packets. The
Label Switching: label is a property that uniquely identifies a
flow on a logical or physical interface. Assign
label to a packets permit to encapsulate
A different ip addresses in a unique label. The
f result is to semplify the route calculation and
a B to isolate the network from the IP address
5 1 context.
SA DA 4 32 1 2 Labels can be specific to an interface
SA DA Label
54 3 SA DA •Label 3 on interface A means
SA DA Label
something different from label 3 on
4 b interface B
1
Or labels can be platform-wide
3 2
•Label 3 is label 3, no matter what
d interface
it is received on
Exemple of Label Switching: Label value may change at each hop
Connection Table

In Out Label
(port, label) (port, label) Operation
IP 25
Port 1 Port 2 (1, 22) (2, 17) Swap

(1, 24) (3, 17) Swap

Port 3 Port 4 (1, 25) (4, 19) Swap

IP 19
(2, 23) (3, 12) Swap

MPLS (Multy protocol label switching)

MPLS is an Architecture able to manage the 2
label switching machanism
 IP packet communication MPLS GMPLS 3/6

MPLS: MPLS main caracteristic

The MPLS architecture permit to setup a Label
Switching Path (LSP). MPLS provides fast restoration
LSR and Quality of Service Connections
New
LSR LSR York To setup LSP each node should know the topology
San
information (links and node)
Francisco LSR
The LSP setup start from the head node and trough
“signaling” the LSP configuration is forwarded to all
LSP node of the path until the tail node.
Label Switch Routers (LSRs)

LSP setup:
There are three key elements of MPLS
The MPLS header stack
LSP setup
• Which contain the MPLS label on which Label Switch
Routers will forward the packet. Headers can be stacked.
Network
Head The enhanced IP routing protocols
topology Info.
Tail • Which distribute topology and constraint based data
Signaling
The label distribution protocols
• The standardized connection establishment protocols
through which LSR’s set up a complete path from ingress
LSR to egress LSR ( LSP).
• They provide an instrument for an end-to-end path
management.
3
 IP packet communication MPLS GMPLS 3/6

MPLS Routing Protocols

•OSPF
•Five types of OSPF routing protocol
packets
•Hello
•Database description Distribute topology information only
•Link-state request
•Link-state update
•Link-state acknowledgment
IS-IS

•BGP-4
Constraint data
Link capacity,Link utilization
Resource class
Priority
•OSPF-TE
Pre-emption etc
•IS-IS –TE
Explicit route calculation
Route determined by ingress (or egress)
LSR based on overall view of topology, and
RSVP-TE constraints
Traffic engineering (the ability to control
traffic flows in a network the ability to
move traffic away from the shortest path to
a less congested path)
Fast rerouting 4
Quality of Service and Class of Service
 IP packet communication MPLS GMPLS 5/6

GMPLS:
The evolution of the MPLS is the Extends MPLS called GMPLS (generalized MPLS).
GMPLS is designed to support multiple switching types
•TDM switching (SDH/SONET)
•Wavelength switching (Lambda)
•Physical port switching (Fiber)

The Advantages are:

Uses existing and evolving technology
Facilitates parallel evolution in the IP and optical transmission domains
Enhances service provider revenues
New service creation
Faster provisioning
Operational efficiencies
5
 IP packet communication MPLS GMPLS 6/6

The GMPLS Network introduce the concept of plane:

Control plane is the domain of:

Management plane
•routing :protocols dedicated to
the Path routing management
signaling plane
Control plane { routing plane
•Signaling: protocols dedicated to
the path (LSP) set up
data plane
Data Plane represent the network
NM
NM functions in the NE, e.g. LMP resources (Link)
plane
Managent Plane correspond to the
Manager of the GMPLS architecture
(Node or NMS)
MPLS GMPLS

M
IGP (OSPF, IS-IS), EGP (BGP) Routing g
Control t

LDP, CR-LDP, RSVP-TE Signaling plane p

l
User a
Packet / Label , fiber, VC-x / Label Forwarding Plane n
(data Plane) e

6
 ASON Networks 1/1
The networks operating with the GMPLS protocols are called ASON networks.
The question is now: Why ASON Network?:

Multi-vendor interworking (networking) Multi – Layer interworking

How to establish a connection across multi vendor islands?
Multi-layer collaboration
(IP, Ethernet, MPLS, SDH, OTH) Interworking of SDH backbone with Ethernet On
Demand Traffic
Interoperability based on standards
Unified management of multi-service network Dynamic restoration with resources sharing
Static protection schemes setup via NMS with dedicated
protection resources (e.g. SNCP)
Distributed Restoration
Wwith “restoration” only 25% spare bandwidth is necessary or
Efficient use of bandwidth even lower due to differentiated protection priorities with
preemption for low priority traffic
High availability

Auto-discovery of network topology many protecting routes

Open Interfaces
destination reached along
High flexibility different paths
High scalability each span can be upgraded independently

Reducing CAPEX (CAPital EXpenditure)

Reducing OPEX (OPerating Expenses)

7
 GMRE ARCHITECTURE 1/6

The basic elements of the ASON networks are the GMRE nodes. The GMRE nodes are designed to
implement the GMPLS architecture. In the Alcatel-Lucent portfolio, at the moment, only the 1678MCC
and 1674LG are supporting GMRE
In the GMRE nodes reside a set of processes implementing the control plane ( Signaling, Routing, link
and path management). Those processes interact with the NE MIB trough the Q3 interface and with
the Management palne truugh a dedicated interface. The Managemnt plane is represented by the
NMS or a simple user command line interface (CLI)

CLI Network
: Management Terminal Management
Plane System residing
in NMS
GMRE
Control
Plane

GMRE Mgmt. Agent

Control Signaling Path Routing
Plane GMRE Applications Mgmt.
Frameworks
Link Management

native
management Transport
Transport interface to Plane
Plane Q3 MIB of NE
MIB

residing
in NE

NE OXC
8
 GMRE ARCHITECTURE 2/6
GMRE node main blocks:
RM corba CLI Manual commands

LM: Link management: resources available on the

GMRE
MA NE
PM: Path Management, path information

LM PM RH SH PH
RH: It manage the OSPF protocol for the path
routing
SH: It manages the communication between NEs
LG Adapter
PH: Policy Manager (It calculates the path priority)
NE
• Signaling:
SH Supports connection establishment and release
Signaling protocol: RSVP-TE
• Routing
RH
– Runs a routing protocol: OSPF-TE:
– Maintains a database with topology and network status
information
– Disseminates network (link) status information of local links
– Exchange of Link State Advertisements (LSAs)
LM
– Performs constraint-based path computations (CSPF)
• Link Management:
PM – Manages the SONET/SDH labels: allocation/de-allocation
– Runs the link management protocol (LMP) 9
• Path Management
 GMRE ARCHITECTURE 3/6
connection setup ASON Domain
Signaling Details:
•RSVP is an Internet Standard (RFC) for reserving resources
GMRE GMRE GMRE GMRE GMRE
MIB MIB MIB MIB MIB
NE NE NE NE NE •RSVP is a soft-state protocol
–PATH and RESV messages must be resent periodically to refresh
ingress transit transit transit egress the LSP and keep it alive
node node node node node
•RSVP has been extended (TE extensions) to support (G)MPLS:
–it can deal with LSPs, LSP attributes, and labels
Path
ACK Path
ACK –supports explicit routing (ERO)
Path
Head Resv + –allows to record a route (RRO) - important in case of loose routes
MESSAGE_ID_ACK
Resv
ACK
ACK •RSVP has two message types for connection establishment:
Resv
Enable fault ResvConf + UNI Transport Connection Established –PATH: establish state and request label assignment
monitor MESSAGE_ID_ACK
Source -C
UNImay start transmitting –RESV:distribute labels and reserve resources
ACK
ResvConf ResvConf Enable fault •Runs ingress-to-egress and not end-to-end (UNI RSVP sessions on either end
Enable fault monitor monitor, start are different from the NNI session)
ACK
ACK data transmission
Source UNI
- -
Source NNI - NNI
Destination - UNI
Destination Routing Details:

E.g: adding the node the routng •OSPFv2 is an Internet Standard (RFC 2328 for IPv4) for routing
IP node B neighbors table are updated
IP node C •OSPF is a link state routing protocol (in contrast to a distance vector routing
IP node D protocol)
D
•OSPF provides its own HELLO mechanism to find its neighbors
A
•OSPF supports 2 levels of routing hierarchies (area concept)
•OSPF has been extended (TE extensions) to support (G)MPLS:
–allows the dissemination of additional TE link attributes like

B –link capacity (maximum/unreserved bandwidth)

IP node A
C IP node C –protection type
IP node A IP node D
IP node B –shared link risk group (SRLG)
IP node D 10
–supports link bundling
–opaque LSA type 10 is used to carry additional TE-link information
TE-Link and SRG 1/2

TE-LINK
In the GMPLS Network it has beeen introduced the TE-Link concept. TE-links is an network
object representing the links boundle. It means that more physical links are groupped in a
unic entity and trafic is routed trough the TE-link instead of the single link.

TE-link #1
SRG Shared Risk Group.
STM-4 STM-4 SRG represent the risk of
STM-4 STM-4 interruption assigned to a link
Data
•••

Bearer or a set of links.

STM-4 STM-4
NE A NE B
Databearer: correspond to the
physical links
STM-16 STM-16
STM-16 STM-16
Data
•••

Bearer
STM-16 STM-16 The main creteria of the TE
link boundlink is the SRG. It
TE-link #2 means that the TE-link is
composed by links having th
same SRG

11
 TE-Link and SRG 2/2

With SRG and TE links objects it’s possible to protect the traffic using a spare route SRG divers with the main
route. The result is to reduce the possibility that th main and spare route are interrupted simultaneously

SRG 1,2 SRG 1 SRG 2 SRG 1 SRG 2

1 2 1 2 1 2

SRG1,3
SRG 3 SRG 3
SRG 2,3
SRG 5 SRG 4 SRG 5 SRG 4 SRG 5
SRG 4
3 3
3

Route Main
Fig 1 Fig 2 Route Spare

The Fig 1 represent a path with main and spare route SRG diverse Main : SRG 1,3 Spare: SRG 4

The Fig 2 represent a path with main and spare route not SRG diverse Main : SRG 1,3 Spare: SRG 1,2 SRG 5
If the Tube correspoding the SRG 1 is broken both main and spare route are affected

1—2 SRG 1,2 SRG1,2 SRG 1,3 SRG 2,3 <> 0 SRG not Diverse
1---3 SRG 1,3 SRG 1,3 (SRG 1,2 SRG 5 ) <> 0 SRG not Diverse
SRG 4 SRG1,2 SRG 4 = 0 SRG Diverse
SRG 1,2 SRG 5 SRG2,3 SRG 5 = 0 SRG Diverse
2---3 SRG 2,3 and SRG 5
12
 GMRE ARCHITECTURE 4/6

GMRE nodes required a set of interfaces suporting the different GMPLS protocols just before described

InBand physical Interface Physical port dedicated to the internal DCC (LAPDs)

OutOfBand physical Interface

IP tunnel based on the external DCC (ethernet interface)

IpTunnel Virtual interface that provides the information on which source and destination ip
address the RSVP and DPR stacks need. The IP tunnel is mapped on the
available physical interfaces InB or OOB physical links.
ControlplaneProtocol Interface Virtual interface managing the signaling trough RSVP protocol trough the ip
tunnels
DataplaneProtocol Interface
Virtual interface managing the routing trough DBR protocol trough the ip tunnels
Dataplane Physical links (databearer) and groups of physical link (TE-LINKs)

GMRE node GMRE node

The various protcols RSVP,DPR, LMP
databearer databearer can be supported by the external DCC:
TE LINK TE LINK
databearer databearer • Out of band Configuration (OOB)
or by the internal LAPDs trogh the
Out Of Band configuration databeares
RSVP Ethernet Ethernet RSVP
•In band Configuration (InB)
DPR DPR
IpTunnel In band Configuration IpTunnel
Note: The TE-LINKs could be
LMP LMP
databearer databearer composed by databearers supporting
TE LINK TE LINK also signaling and routing (InB)
databearer databearer
13
 GMRE ARCHITECTURE 5/6
Pratical Example (1678MCC GMRE interfaces)
-------------------------------------------------------------------------------------------------
Index Name Type IP address Speed AdminSt OpSt
-------------------------------------------------------------------------------------------------
83 1678_B/1678_A-83 TELink 10.10.255.86 12440 Up Up
86 1678_C/1678_A-86 TELink 10.10.255.84 4976 Up Up
Dataplane
88 1678_D/1678_A-88 TELink 10.10.255.83 2488 Up Up
2000 IPTunnel 10.10.255.86 - Up Up External
2001 IPTunnel 10.10.255.84 - Up Up IpTunnel DCC
2002 IPTunnel 10.10.255.83 - Up Up
3000 RSVPNNI 10.10.255.86 - Up Up
Controlplane
3001 RSVPNNI 10.10.255.84 - Up Up Protocol OutOfBand channel
3002 RSVPNNI 10.10.255.83 - Up Up Interface
5000 DPR 10.10.255.86 - Up Up
5001 DPR 10.10.255.84 - Up Up Dataplane
5002 DPR 10.10.255.83 - Up Up
Protocol
Interface 10.10.255.85
10.10.255.86
9000 lapd1 LAPD 10.10.255.84 - Up Up B
InBand A
9001 lapd0 LAPD 10.10.255.86 - Up Up OInBand channel
physical
9002 lapd2 LAPD 10.10.255.83 - Up Up Interface 01-3-07-05
11000 ipip4 OOBTunnel 10.10.255.86 - Up - 01-3-07-03
11002 ipip3 OOBTunnel 10.10.255.84 - Up -
OutOfBand 01-3-07-15
physical
11003 ipip5 OOBTunnel 10.10.255.83 - Up - Interface
13070301 01-3-07-03 DataBearer - 2488 Up Up
13070501 01-3-07-05 DataBearer - 2488 Up Up
13071501 01-3-07-15 DataBearer - 2488 Up Up
D
13071601 01-3-07-16 DataBearer - 2488 Up Up C
10.10.255.83
13140101 01-3-14-01 DataBearer - 2488 Up Up 10.10.255.84
13140201 01-3-14-02 DataBearer - 2488 Up Up Dataplane
13140401 01-3-14-04 DataBearer - 2488 Up Up
10.10.255.X = GMRE Node Address
13140501 01-3-14-05 DataBearer - 2488 Up Up
13050701 01-3-05-07 DataBearer - 622 - Down
13070101 01-3-07-01 DataBearer - 2488 ShuttingDown Up
------------------------------------------------------------------------------------------------- 14
 GMRE ARCHITECTURE 6/6

Gteway Address
LAPD
In Band Tunnels

OOB Tunnels
IpTunnels
Stating Routing .of OOB Config. NM Connection

15
Stating Routing of InBand Config.
 Network Model 1/1

Drop Port
EMS/NMS
ASON (RM)
E-NNI
Proprietary
Interface
CORE Domain 1 METRO 2
E-NNI
TNA 41
TNA 1 I-NNI
UNI
Client 1 Client 4
E-NNI
TNA 42
METRO 1
UNI

METRO 3
TNA 3
Client 2 TNA 2 TNA 5
UNI
E-NNI Client 5
CORE Domain 2
Client 3

Interior NNI - Intra-Domain

User to network interface - UNI Non
ASON
Exterior NNI - Inter-Domain network
Drop
Network Access Points TNA Port

In the real environment, assume relavant importance the interworking between the Legacy network (SDH) and the ASON
domain. In this context the main factor to be consider is the possibility of sharing resorces between the two different type of
network. The problem is solved by the proper management of Access Control Domain (ACD). It define “who” can control
the network resources. So that, the NMS assigns a specific ACD roule for ecach interfaces.

Drop Port: domain shared between GMRE domain and Manager Domain (RM) ACD: J$

NNI port : domain managed by GMRE: ACD G$

16
External Port (NonAson Domain) ACD :R$
 Type Of Protection 1/1
• Unprotected
– A failed path is not restored
• Guaranteed Restoration (GR)
– A backup path is calculated and established in soft manner before the failure and activated once the nominal
path failed.
• Failure diverse Source Based Rerouting (SBR)
– A failed path is restored in post calculated mode taking nominal resources into account for reuse.
• SNCP
• Protection restoration combined (PRC)
– Combination of SNCP and SBR by restoring the failed SNCP leg

General roles and Definitions

• Nominal Main: Route defined at the set up time, it’s managed by the NMS (RM). Constraints are supported
• Nominal Spare: Route spare of a SNCP path, it’s managed by RM manager. Constraints are supported
• Backup Route: Spare route of the GR path, it’s “pre calculated” when the path is set up. The backup route is fully managed
by the GMRE node. The backup could be “active”, when the traffic is running on it, “inactive” when the traffic is runing on
the nominal route
• Current Route: Route currently running. Without link failure it should correspond to the Nominal Route, in presence of
problems it correspond to the backup route.
• The reversion to of the current to the nominla route could be automatic or manual.
• Automatic: it’s automatical done after a dedicated time out interval since the nominal route has been repaired.
The time out interval is configurable by Unix, the dfault is 5 min, the minimum value supported is 3 min.
• Manual: only a manual command can move the path to his nominal route
• The criteria of the backup route is calculated taking into account the following paramter with the following order:

GR • 1 SRG diverse SBR • 1 Use the nominal route as much as possible

• 2 Minimum cost (STM64 more backup is TE-Link diverse (not SRG diverse) to
exepensive then STM1) point of failure
• 3 After 1st restoration, the 2nd inactive backup re-uses as • 2 When calculating the route costs, the nominal
• much of the nominal route as possible with zero cost. route links are taken as zero costs. 17
 Type Of Protection 1/4

Path Priority and Preemption

• Support of path priorities allows to support different classes of service (COS) (gold, silver, bronze, best effort, etc.)
• Lowest priority is 4 the higher is 1.

• Requires more complex preemption rules in GMRE

• Priority based Preemption of backup paths
• Priority based Preemption of traffic-carrying paths

Following preemption rules are applied:

• When a path is set up, free resources shall be used whenever possible (Preemption of traffic-carrying
paths only if necessary!)
• (Nominal) paths that are set up or backup paths that are activated preempt all (other) registered and
non-active backups that cannot be accommodated any longer - this is not affecting traffic!
• Paths with a high priority can only preempt paths with a lower priority (Not supported by RM)
• Preemption of a link resource increases the link cost in CSPF depending on priority of preempted paths
(Not supported by RM)

18
Type Of Protection 2/4

-UNPROTECTED
-Principle
Signaling
•In case of failure the path is not restored
tail
head
•The path is established by the signalling RSVP

•SNCP
-Principle
Nominal Main
•It’s like a the Legacy SNCP path with main and
spare legs established by signalling RSVP

•The switch criteria are identical to the SNCP SDH

SBR -Principle
• SBR calculates new path after the failure
• Contention resolved by priority mechanisms
• New path will use old path resources where possible
– Benefits
• SBR guarantees path recovery for any failure in the
network
• Flexible and extremely efficient use of spare network
resources
• Multiple failure recovery without manual intervention
• If GR and PRC don’t find backup resources SBR is
applied to save the traffic
 Source Based Restoration for complex failure scenarios 19
Type Of Protection 2/4
Nominal Main
GUARANTED RESTORATION
- Principle
• Each working path has a pre-reserved backup path
which can be shared with other backups of disjoint
paths
• Restoration mechanism activates the backup path
after failure
• Backup will be restored after failure and provides Inactive Backkup
fully protected status of the restored path
- Benefits
• GR guarantees path recovery for any failure in the
network
• Flexible and efficient use of spare network
resources
• Recovery of backup path using SBR
• Multiple failure recovery without manual
intervention
 Guaranteed Restoration for multiple failures

20
Type Of Protection 4/4

Nominal Main
PRC Protection Restoration Combined
 Principle
• SNCP is set up for highest priority paths
(ultra fast recovery time)
• Restoration mechanism creates a new
SNCP path after failure recovery, i.e.
provides fully protected status of the
restored path using SBR mechanism Nominal Spare
– Benefits
• SNCP guarantees path recovery time of less Current Main
than 50ms
• Flexible and efficient use of spare network
resources
• Ultra-fast multiple failure recovery without
manual intervention
 Restoration for multiple failures guaranteed within
50 ms

21
Network Installation Main step 1/1

1. Node Installation: MCC1678 see Admin Guide Install NE sw plus GMRE application in a single shot

2. Node Creation (by Craft Terminal)

3. Node supervision (NMS)

4. Verify the GMRE is up and Running on all nodes and set the nodes Administration status Up

5. Edit the file /usr/Systems/1354RM_X.X/conf/GMRE.cfg inserting the TEFEP ID managing the GMRE
nodes

6. Network construction by the NMS (automatic upload)

7. Implementation of the ASON protection by the NMS

8. Dataplane Configuration: Managed by RM (Physical connection, Dropp port, NNI port, TE Link)

9. In Band Signaling configuration: LAPD and static Routing See Admin Guide (automatic)

10. Upload Control Plane (GMRE node configuration automode setup)

11. Path Setup

22
 Network Configurtion implemented by CLI 1/1
It’s also possible to perform the step 4-5 manually by a CLI commands:
IP TUNNEL:config interface IpTunnel 2001 ifname “Tunnel Name” RemoteAddress 10.10.255.X AdminState Up
RSVPNNI:config interface RSVPNNI 3001 ifname “ RSVPNNI NAME” UnderlyingIf 2001 RsvpType I_NNI
AdminState Up

DPR: config interface DPR 5001 ifname “DPR NAME” UnderlyingIf 2001 OspfType I_NNI AdminState Up

In case the GMRE node are not controlled by RM it possible to complete the step 7 manually:
config interface DataBearer 13020101 RemoteIfIndex 13020101 LinkType I_NNI ifname “Link
DATABEARER:
Name” AdminState Up

TE-LINK:config interface TeLink 10001 IfName “TE-LINK Name” UnderlyingIf 13020101 RemoteNodeAddress
10.10.255.X RemoteIfIndex 13020101

Drop port:config interface DataBearer 13140101 ifname 1-3-14-1-1 acdvalue sharedport LinkType

Basic CLI Commands:

show interface : Shows the interface (DPR,RSPV, IP Tunn., Databearer.......) configured in the node
show interface telink 100000: Shows all the parameters of the specifyed interface
show lsp lspindex X: Shows the details of the LSP x
Config node adminState Up: set the administration state of the node to up
Config interface databearer adminState Up set the administration state of the link to up
With the “ ? “ simbol it’s possible to visualize the available commands, typing “TAB” it’s possible to complete the
command

NOTE: Reccomended Ranges

Iptunnel 2000 + Neighbour Nr RSVPNNI 3000 + Neighbour Nr
RSVPUNI 4000 + Neighbour Nr DPR 5000 + Neighbour Nr
23
TE-LINK 100000 <= n <= 999999
 Communication Infrastructure, trace and troubleshhoting 1/3

ASON communication interfaces: The MTNM interface (CORBA ) between the NMS
Topology Resource SNC and the NE manage the LSP set up and the
NML
(RM, …)
Management Management Management
spontaneous “GMRE” events (e.g LSP Alarms).
Q3 Adapter MTNM Adapter
Q
3
Element Management
The Q3 interface manages, as in the legacy
EML (FCAPS)
MTNM
network, the NE configuration (board and CC) and
(CT, SH) Q3 CLI the SDH Alarms
Adapter Adapter
Q
CLI
3
CLI MTNM The CLI (Client User Interface) uses a dedicated
Network Q3 GMRE IP address to connect the GMRE node.
Elements
Q3
(1678 MCC MIB
with GMRE) NE

ASON Manager

events/alarms

Event Notification Mechanism

• there is only one Notification Server (NS) in the getEventChannel()
Notification
network Server
events/alarms
• all GMREs send alarm/event to this unique NS
• ASON manager retrieves alarm/event from this unique
NS only
• the getEventChannel() operation replies the reference
CORBA Bus
to the event channel the addressed GMRE is using. GMRE 1 GMRE 2 GMRE n
• The NS is located at network manager side
• The GMRE events are transmitted to the RM manager
trough the MTMN interface
24
Communication Infrastructure, trace and troubleshhoting 2/3

On Rm the notification Services is an add on product installed under the MTNM

component :
/usr/snml/RM_MTNM/script
ipb491,sys,root # ls
checkStatusNotifService resetNotifService
disable_impl_repository restartInvolvedFeps
disable_naming_service restart_impl_repository
disable_notification_service restart_naming_service
enable_impl_repository restart_notification_service
enable_naming_service run_impl_repository
enable_notification_service run_naming_service
openFusionManager run_notification_service

Incase the Events are not properly received, it possible to re-create the notificatio
services by the command (as root): resetNotifService
Its important to verify that the TFP are automatic stopped, otherwise use the
command (as root) : restartInvolvedFeps

Here the list of the GMRE event receiv ed by the ASON manager
•EMS: NE not reachable
•EMS: GMRE degraded
•SNC: Rerouted (cleared once reverts to intended)
•SNC: Ready to revert
•SNC: Reversion blocked
•SNC: Backup unavailable
•SNC: Active unavailable
25
•SNC: SNCP degraded
 Communication Infrastructure, trace and troubleshhoting 3/3

The ASON traces resides in the tsdCfg agent

trace: It s’ possible to enable it with the following Example:
commands: ageName=tsdFepCfg_105_105000
. ${NXNL_PRD}/bin/rdrctOut "${ageName}"
Edit a dile / trlFile="${NXNL_PRD}/trcLevel/${ageName}.trc"
usr/System/1354RM_X/bin/TEFEP/tsdFepCfg_X_ [ -f "${trlFile}" ] || touch "${trlFile}" # Create trace-level file if missing
X000.com GMRE_CONF_FILE="${NXNL_PRD}/conf/GMRE.cfg"
if [ -f "${GMRE_CONF_FILE}" ]
Where X is the EML ID managing the ASON
then grep '105' ${GMRE_CONF_FILE} && export NLcorbaMTNM=1
nodes
fi
Inser the variable: unset GMRE_CONF_FILE
Export TAO_DEBUG=1
export TAO_DEBUG=1
export NXNL_REACTOR_TIMEOUT=5
Normally it’s also better to increase the trace size exec ${NXNL_PRD}/bin/TEFEP/${ageName} \
-eml 105 \
Adding the line -tefep 105000 \
-trcs 15000000 -trcs 15000000 \
-trl ${trlFile}
Then re-start the TSD FEP

E.g Trace file related to a SNC switch:

GIOP message - HEXDUMP 216 bytes
47 49 4f 50 01 02 00 00 00 00 00 cc 00 00 00 17 GIOP............
03 00 00 00 00 00 00 00 00 00 00 23 14 01 0f 00 ...........#....
4e 53 54 45 c4 0d 66 00 0d c5 ac 00 00 00 01 00 NSTE..f.........
00 00 01 00 00 05 4f 00 00 00 01 00 00 05 50 94 ......O.......P.
00 00 00 0c 73 77 69 74 63 68 52 6f 75 74 65 00 ....switchRoute.
00 00 00 00 40 6d 5b 08 00 00 00 03 00 00 00 04 ....@m[.........
45 4d 53 00 00 00 00 0d 31 30 2e 31 30 2e 32 35 EMS.....10.10.25
35 2e 38 36 00 6d 5b 08 00 00 00 15 4d 75 6c 74 5.86.m[.....Mult
69 4c 61 79 65 72 53 75 62 6e 65 74 77 6f 72 6b iLayerSubnetwork
00 00 00 00 00 00 00 02 30 00 5b 08 00 00 00 15 ........0.[.....
53 75 62 6e 65 74 77 6f 72 6b 43 6f 6e 6e 65 63 SubnetworkConnec
74 69 6f 6e 00 6e b4 b0 00 00 00 03 32 34 00 6c tion.n......24.l 26
00 00 00 02 31 00 48 7b 00 00 00 00 00 00 00 03 ....1.H{........
00 00 00 00 00 00 00 00 ........
Traffic Migration 1/1

By the NMS it’s possible to migrate the traffic from the Legacy domain to the ASON domain and viceversa, without
impacting the traffic. The procedure is described below:

• Select a path belonging the Legacy network and

add the constraint : use the ASON NPA for the
spare route
• Modify the path attribute CP restoration: “guaranted Legacy
restoration” Spare leg
Path
• Add the protection to the path
Spare leg in
• Verify that the spare leg cross the ASON domain the ASON
• Execute a manual switch to the spare route Domain

• Check that the traffic is running error free

• Remove the protection keeping spare
• Verify that the path is running and protected in the
ASON domain

27
ABBREVIATIONS 1/1

>ASON Automatically Switched Optical Networks

>IETF Internet Engineering Task Force
>ITU International Telecommunication Union
>GMRE GMPLS Routing Engine
>LSP Label Switched Path
>OIF Optical Interface Forum
>OSPF Open Shortest Path First
>PRC Protection Restoration Combined
>RSVP Resource Reservation Protocol
>SBR Source Based Restoration
>SNCP Subnetwork Connection Protection

28
ASON application Management (RM) 1/18

1.1. SRG creation and internal Physical Connection correlation

Purpose:
The purpose of this test is to create the SRG and correlate it with the physical connection
Procedure:
 Create a SRG
 Select the 1354RM Network Domain
 Actions
 Shared Risk Group
 Create/Remove  Next
· Select the SRG Type (Cable, Conduit…..)
· Fill in mask the label and the comments
· Correlate the SRG to the physical connection
· Actions
· Shared Risk Group
· Correlated/modify/SDH SRG Calculation
· Select the Physical Connection (not already correlated)
· Finish

29
 ASON application Management (RM) 2/18

1.2. 1354RM ASON NPA Creation

Purpose:
The purpose of this procedure is to implement an ASON NPA
Procedure:
 Open a RM maps; select the topology where the NPA will be placed. Actions -> Create -> Npa
 Select the NPA Type ASON
 Select the Bundling Rules for the internal physical connection of the ASON NPA
 WithSameRisk and Cost: means that all the physical connection with the same end points and the same risk and same
cost will be grouped in the same TE-Link in the ASON Network
 All Together: means that all the physical connection with the same end points will be grouped in the same TE-Link in
the ASON Network
 OnebyOne: means that in the ASON Network will be set one TE-Link for each physical
 Modify the NPA Cost parameter if you need
 NPA Reduction Cost Factor (Reduction cost assigned to the Physical links belonging to NPA)
 NPA Usage Cost (cost assigned to the NPA)

 Click on Next, and select the ‘internal’ and the ‘interworking’ physical connection involved in the NPA.
 Click on Finish
 Select the defined ASON NPA and implement it
Set for all the physical connections involved in the ASON NPA (both internal and interworking) the ‘Administrative State’ as
‘Unlocked’. In order to execute this action select the physical connection, push the right button of the mouse, select
‘Administrative State’ and choose ‘Set Unlock’

30
ASON application Management (RM) 3/18

1.3. 1354RM Setup a Point to Point Bi-directional Path

Purpose:
The purpose of this procedure is to create a point-to-point bi-directional path between two nodes.
Procedure:

Path Creation

 Select the two nodes and choose Actions -> Create-> Path
 From the Path Creation Wizard select:
 The Service Type (PDH, ATM, Ethernet, Data, CBR)
 The Service Rate (this attribute can be one of)
 PDH: 2M…
 Ethernet: 10-100Mb Rate Adaptive
 Transport rate: TU12, TU3, AU4, TU12-nV TU3-nV
 Configuration Rate: Automatic/Manual 10/100Mb
 Concatenation Level (if the Transport Rate is nV)
 1Gb Transp
 1Gb Rate Adaptive
 Transport rate: AU4-nV
 Concatenation Level
 100Mb Transp
 MPLS

31
ASON application Management (RM) 4/18

Transport rate: TU12, TU3, AU4

 Feb6 10-100Mb
 Transport rate: TU12, TU3, AU4
 DATA: (Board PR) FDDI, ESCON, Digital video, Fiber Channel, STM1, STM4, PR HO
Virtual Concatenation
 CBR: CBR (Constant Bit Rate)
 The User Label
 The Path Type
 BIDIR
 UNIDIR
 BROADCAST
 The Protection[1]
 InRing (the path get the protection type of the NPA crossed)
 SNCP
 D&C SNCP (in case there are not enough resources the protection type is automatically reduced to
SNCP)
 The MS Protection Usage Profile (only in case of MS SPRING 4F)
 Normal
 Protection preferred (Path allocated preferred on the spare AU4)
 Protection Only (path allocated only in the spare AU4)
 The Sncp Type (only in case of SNCP path: N (Not Intrusive) or I (Inherent)
 Click Next and select the source and sink Naps
 Click Next and select
 Allocation Rule: Manual or Automatic
 Implementation Rule: Manual or Automatic
 Allocation Constraint: ‘All objects’
 Algorithm: ‘Automatic’
 Set if needed the optional value for Comment1, Comment2, Customer, Path Group, Automatic
Monitoring, Text1, Text2, Text
32
ASON application Management (RM) 5/18

Using the Alarm Sub Window select

 The Automatic Monitoring: True or False, to enable or disable the automatic PM (24H) creation
 The Alarm Propagation Rules
 The Client alarm enabling rule
 The Transport alarm-enabling rule
 Using the Routing Subwindow select
 NPA main and spare
 MS-SPRING D&C
 Using the LCAS Subwindow select (only in case of Ethernet Path on ISA ES board)
 Lcas protocol enabled or disabled
 Using the CP Restoration Subwindow select (only in case of path involved in ASON network)
 Pre-Calculate (the ASON network will pre-calculate a backup route for the span of the path belonging
the ASON network it-self. The spare route (will be calculated as SRG diverse )
 Upon Failure (SBR) (The ASON network will calculate the spare route only in case of failure. The spare route
will be disjoined from the minimum as possible, only link diverse from the affected link)
 NoRestoration (the span inside the ASON network will be implemented without restoration protection)
 Priority:from 1 minimum to 5 maximum

 Using the User Subwindow insert comments if needed

 Click Finish

Allocation Implementation and Commisioning

 Select the path created before and choose Actions->Configuration-> Conf. State Modification->Allocate
•By the Allocated path choose Actions -> Configuration -> Conf. State Modification -> Implement
•By the Implemented path choose Actions -> Configuration -> Conf. State Modification -> Commision

[1] If the path has to cross ASON networks the protection inside this domain will be specified in the ‘CP 33
Restoration’ section. ‘Protection’ in this section is the kind of protection outside the ASON domains
ASON application Management (RM) 6/18
1.4. TE-Link Management
Purpose:
The purpose of this procedure is to manage the TE-LINK/Physical connection/SRG association
Procedure:

UPDATE TE-Link

•Select a TE-LINK
•Actions--->Update TE-Link
 Modify the TE link Metric
 Modify the SRG
The modification will be propagated on all physical connection belonging the TE-Link

MOVE PHYSICAL CONNECTION

•Select a TE-LINK composed by at least 2 physical connection bundled together

•Lock the physical connection to be moved
Move to a new TE-Link
 Actions--->Move physical connection
 Select the p.c to be moved in the Update TE-Link wizard in the source side.
 Press with the mouse the arrow and move the p.c on the destination side
 Change the link metric and the SRG
 Press to finish
Move to an existing TE-Link
 Actions--->Move physical connection
 Select the option Move to an existing TE-Link in the Update TE-Link wizard
 Select the p.c to be moved in the Update TE-Link wizard in the source side
 Select the destination TE-Link
 Press with the mouse the arrow in the source area and move the p.c on the destination area
 Press to finish

34
ASON application Management (RM) 7/18

1.5. Unprotected path life cycle (VC4,VC4-4c,VC4-16c & VC4-64c)

Purpose:
The purpose of this procedure is to verify Unprotected path life cycle for some type of traffic (VC4,VC4-4c,VC4-16c &
VC4-64c)
Procedure:

 Setup a bi-directional path belonging the ASON node, selecting in the CP Restoration Sub window, No Restoration
 Cut the working fiber and verify that the traffic will be not protected
 Repair the fiber and verify that the traffic will be restored
 Lock the working physical connection and verify that the traffic will be not protected
 Unlock the physical connection the traffic will be restored

1.6. SBR path life cycle (VC4,VC4-4c,VC4-16c and VC4-64c)

Purpose:
The purpose of this procedure is to verify SBR path life cycle for some type of traffic (VC4,VC4-4c,VC4-16c & VC4-64c)
Procedure:

 Setup a bi-directional path belonging the ASON node, selecting in the CP Restoration Sub window, Upon Failure
 Create failure to provoke restoration and check restoration time
 Clear the failure and check the reversion

35
 ASON application Management (RM) 8/18
1.7. GR path life cycle (VC4,VC4-4c,VC4-16c and VC4-64c)
Purpose:
The purpose of this procedure is to verify GR path life cycle for some type of traffic (VC4,VC4-4c,VC4-16c & VC4-64c)
Procedure:
 Setup a bi-directional path belonging the ASON node, selecting in the CP Restoration Sub window, Pre-
calculated
 Check nominal and backup route
 Using the Highlight
 Select the main route and the backup route from the routing display (selecting the ASON symbol on the head
node)
 By the CLI command
 From the node view double click on the control plane
 Insert the user and password
 Execute the CLI commands
 Create failure to provoke restoration and check restoration time
 Check nominal and backup route
 Clear the failure and check the reversion

1.8. PRC path life cycle (VC4,VC4-4c,VC4-16c and VC4-64c)

Purpose:
The purpose of this procedure is to verify PRC path life cycle for some type of traffic (VC4,VC4-4c,VC4-16c & VC4-64c)
Procedure:
 Setup a bi-directional SNCP ath belonging the ASON node, with the sncp switch included in the ASON Domain.
From the path Creation Wizard tool select in the CP Restoration Sub window, Pre-calculated
 Check main and spare legs
 Create failure to provoke the switch and check switching time
 Check the protection of the leg with failures
 Using the Highlight
 Select the main route and the backup route from the routing display (selecting the ASON symbol on the head node)
 By the CLI command
 From the node view double click on the control plane
 Insert the user and password
36
 Execute the CLI commands
 Clear the failure and check the schema status and reversion
ASON application Management (RM) 9/18

1.9 SNCP path life cycle

Purpose:
The purpose of this procedure is to verify SNCP path life cycle for some type of traffic (VC4,VC4-4c,VC4-16c & VC4-
64c)
Procedure:

 Setup a bi-directional SNCP ath belonging the ASON node, with the sncp switch outside the ASON Domain.
From the path Creation Wizard tool select in the CP Restoration Sub window, Pre-calculated
 Check main and spare legs
 Using the Highlight
 Select the main route and the backup route from the routing display (selecting the ASON symbol on the head
node)
 By the CLI command
 From the node view double click on the control plane
 Insert the user and password
 Execute the CLI commands
 Create failure to provoke the switch and check switching time
 Check the protection of the leg with failures
 Clear the failure and check the schema status and reversion

1.10. GB-Ethernet path life cycle

Purpose:
The purpose of this procedure is to verify GB-Ethernet path life cycle for some type of traffic concatenation: (1-7)
Procedure:

 Setup a bi-directional GB-Ethernet path Belonging the ASON node, From the path Creation Wizard tool
select:
 Path type: Ethernet
 Service Rate 1Gbit rate adaptive.
 Concatenation level: (1-7)
 CP Restoration: Pre-calculated 37
ASON application Management (RM) 10/18

 The GB-Eth NAPS are automatically defined as drop port during the path implementation.
 Check nominal and backup route of the HO trail automatically created by the GB Eth. path
 Using the Highlight
 Select the main route and the backup route from the routing display (selecting the ASON symbol on the head
node)
 By the CLI command
 From the node view double click on the control plane
 Insert the user and password
 Execute the CLI commands
 Create failure to provoke restoration and check restoration time
 Check nominal and backup route
 Clear the failure and check the reversion

1.11. Path Route Visualization

Purpose:
The purpose of this procedure is to verify the system capability to visualize the Path route (Nominal Main, Nominal Spare,
Current, Backup)
Procedure:

 Setup a bi-directional path PRC Type

 From the map view click on the highlight button
 From the map view select ----> current
-----> Nominal
----> Backup Route
In case PRC or SNCP path select --> Main/Spare
 Verify that the different routing are correctly displayed
Open the routing display of the path, select the ASON npa symbol behind the head node, then --->Action ----
>Display-----> Details on gmre
 Verify that the CLI interface displays the path routing information
 From the routing select the ASON npa symbol behind the head node, search----> All related item -----> current
route/backup route
38
 Verify that the routing path information, current and backup, are correctly displayed
 ASON application Management (RM) 11/18

1.12. SNCP disjoint path provisioning

Purpose:
The purpose of this procedure is to verify the system capability to “disjoint” the main and spare legs of a path with SNCP
protection outside the ASON domain
Procedure:

 Create a SNCP schema outside ASON domain with main and spare legs within ASON
 Check the paths corresponding to the main and spare segments within ASON are disjoint

1.13. SRG Diversity

Purpose:
The purpose of this procedure is to verify that the backup and restoration route are calculated according to SRG diversity
Procedure:

 Setup a bi-directional path belonging the ASON node, selecting in the CP Restoration Sub window, Pre-Calculated
 Check nominal and backup routes are SRG diverse.

1.14. TE-Link diversity

Purpose:
The purpose of this procedure is to verify that the backup route could not be calculated on TE-link with same cost and SRG. The
TE-Link (same cost same SRG) could be used only in case there are no resource available.
Procedure:
 Setup a GR bi-directional path belonging the ASON node, belonging two nodes with two TE link with the same cost
and SRG.
 Verify that the backup route could be not calculated on the second TE-Link with same SRG and cost.
 If there are non other resource available the TE Link could be used only after the failure on the nominal
39
 ASON application Management (RM) 12/18

1.15.
Link Cost (TE-Links metric) on current and backup routes
Purpose:
The purpose of this procedure is to verify that the routes are calculated according to TE-Link metric.
Procedure:

 Setup a GR bi-directional path Belonging the ASON nodes

 Check that nominal route is the lowest cost according to TE-Link metric

1.16. Priority and Pre-emption

Purpose:
The purpose of this procedure is to verify that the correct management of SPC priorities and pre-emption on nominal
and current route.
Procedure:
 Select two routes in the network between two node belonging the ASON network
 Create the maximum number of path possible on the first route, with priority 4
 Create the maximum number of path possible on the second route, with priority 1
 Look all the other links in order to force the paths routing on the two selected routes
 Look the link of the second route, and verify that the paths are protected with the first link pre-empting the path
with priority 4.
 Unlock the second link and wait until the path are reverted
 Lock the first link and verify that the paths are not protected

40
 ASON application Management (RM) 13/18
1.17. Manual Move of paths blocking a reversion
Purpose:
The purpose of this procedure is to verify the system capability to move manual move the paths blocking the reversion.
Procedure:
Setup a GR bi-directional path Priority 1 Belonging the ASON nodes
 Cut the nominal route
 Setup a GR bi-directional path Priority 4 using as nominal route the backup of the path priority 1 (use the RM constraint)
 Verify that the alarm “reversion blocked” is correctly displayed on the path priority 4
 Select the path priority 4, Actions---->maintenance---->Reversion blocked management
 From the SNC Reversion blocked management wizard, select the path/paths to be moved and click on apply (the path will
be moved ONLY if there are resources available)
 Verify that the path/paths blocking the reversion are moved, and the path priority 4 is correctly reverted, and the alarm is
“Reversion blocked” cleared

1.18 Circuit switching and reversion

Purpose:
The purpose of this procedure is to verify the system capability to move manual move the paths blocking the reversion.
Procedure
 Setup a GR bi-directional path , belonging the ASON nodes and with the reversion mod set to automatic
 From the routing display select the Sub network Connection on head node
 Action---->switch----->To Backup
 Verify that the path has been switched on the backup route
 Check the reversion
 Change the reversion mode of the path from automatic to manual
 From the routing display select the Sub network Connection on head node
 Action---->modify----->Attribute
 Set the reversion mode to manual and apply
 From the routing display select the Sub network Connection on head node
 Action---->switch----->To Backup
 Verify that the path has been rerouted on the Backup route
 From the routing display select the Sub network Connection on head node
 Action---->switch----->To Nominal 41
 Verify that the path has been rerouted on the Nominal route
ASON application Management (RM) 14/18
1.19 SNCP Ring Closure (FROM NR 7.3)
Purpose:
The purpose of this procedure is to verify the system capability to setup a path in ASON domain closed between two
SNCP rings having the drop port protected SNCP.

Procedure
 Consider a network topology base on an ASON network between two SNCP ring
 Setup a GR bi-directional path , belonging the ASON nodes staring in the first SNCP ring and ending in the
second ring.
 Verify that the path has been protected SNCP on the two rings, protected inside the ASON domain, and with
the drop port protected sncp by the GMRE
 From the routing display select the cross connection objects between the ASON and SNCP ring and verify the
SNCP protection of the drop port.
 Open the CLI interface and verify the path routing and the drop port protection.
 Provoke a single failure on the first SNCP ring, in the second SNCP ring and inside the ASON domain and
verify that the circuit is protected.

1.20. SNC Disjoin & Constraint (FROM NR 7.3)

Purpose:
The purpose of this procedure is to verify the system capability to setup a SNC disjoined from a selected SNC

Procedure
 Select a SNC Action---->Maintenance----->SNC constraint management.
 From the SNC constraint view, in the upper window, select the SNC that it must be disjoined from the given
SNC
 From the SNC constraint view, in the lower window, select the TE Link that it must be not used from the given
SNC
 Then click on finish.
 Verify that the routings of the two SNC are disjoined and the selected TE link is not used by the given SNC.
 Verify by the CLI interface the presence of the attribute link diversity. That attribute value
……………………… 42
ASON application Management (RM) 15/18

1.21. Physical connection statistic (payload configuration summary) (FROM NR 7.3)

Purpose:
The purpose of this procedure is to verify the system capability to display the Physical Connection resources availability
(available bandwidth, payload configuration summary)

Procedure:
 From the Physical Connection list view, select a physical connection, Action -->select all related item--->payload
configuration summary
 Verify that the information about the traffic running in the TE Link is correctly displayed
 From the TE Link List view select a TE link and click in the icon Payload Configuration Summary
 Verify that the information about the payload configuration and the bandwidth available related to the selected
physical connection are correctly displayed
 The details of the available information is listed below:
 Rate: rate of physical connection
 Current Available: number of AU current available
 Current Busy: number of AU currently in use
 Current Total: Number of the total current AU available
 Potential Available: Number of AU that can be potential used (if the payload is modified)
 Fill Up:
 Max on total:
 Fragmentation:

43
ASON application Management (RM) 16/18
1.22. Move Current route (maintenance physical link)
Purpose:
The purpose of this procedure is to verify the system capability to move the current route
:
Procedure:
 From the Physical Connection list view, select a physical connection, Action -->select all related item--->payload
configuration summary
Select a physical link and select Action---->ASON----->maintenance
From the ASON Maintenance Wizard tool, set the link in “shuttingDown” status
From the ASON Maintenance Wizard tool, clik on the reload button and display the entire path running
inside the link.
Select all the path, and click on apply
Click again in the reload button and verify that all the path are rerouted (if the resources are available
Click on the check button and verify that the status of the link is changed to “lock” if the entire path has been moved.

•1.23 Move Nominal route

•Purpose:
The purpose of this procedure is to verify the system capability to change the nominal route
Procedure:
 Select a path and add constraint accordingly with the new nominal route
 From the routing display click on “Path/Trail modification” tool
Select reroute and click on next
Select the “A” connection
Select the “Z” connection
 Then click on finish.
 Verify that the nominal route has been changed.
 Click on the check button and verify that the status of the link is changed to “lock” if the entire path has been
moved.
44
 ASON application Management (RM) 17/18

1.20 TE Link statistic (payload configuration summary) (FROM NR 7.3)

Purpose:
The purpose of this procedure is to verify the system capability to display the Telink resources availability (available
bandwidth, payload configuration summary)

Procedure:
 From the TE Link List view select a TE link and click in the icon path/Trail with traffic status
 Verify that the information about the traffic running in the TE Link is correctly displayed
 From the TE Link List view select a TE link and click in the icon Payload Configuration Summary
 Verify that the information about the payload configuration and the bandwidth available related to the selected
TE Link are correctly displayed
 The details of the available information is listed below:
 Rate: rate of the physical connection belonging the given TE Link
 Current Available: number of AU current available
 Current Busy: number of AU currently in use
 Current Overlapped:
 Current Total: Number of the total current AU available
 Potential Available: Number of AU that can be potential used (if the payload is modified)
 Potential Busy:
 Potential Overlapped: Number of the AU that are potentially overlapped by the current traffic related to the
different payload (AU4C, AU16C…)
 Potential Total:
 Current On Total Band:
 Fill Up:
 Max on total:
 Fragmentation:

45
 ASON application Management (RM) 18/18
1.21. Gbith Eth path with LCAS (FROM NR 7.3)
Purpose:
The purpose of this procedure is to verify the system capability to manage the Gbit Eth Path with LCAS function

Procedure
 Setup a bi-directional GB-Ethernet path Belonging the ASON node
 Select the Lcas Option to Enable ,set Sever trail routing to Diverse Routing , and set concatenation level to 7
 Verify that the path is correctly implemented, and all the 7 trail are (even/odd) are route diverse
 Connect the instrument to the ends point of the path and checking the throughput In/Out
 Modify the bandwidth, select the path Action-----> Modification----> Decrease/increase bandwidth
 Verify by the analyzer that the throughput In/Out

1.22. SNC alarms on A1330 AS (FROM NR 7.3)

Purpose:
The purpose of this procedure is to verify the management of the SNC alarms trough the A1330AS interface

Procedure
 Select a path from the path list and open its routing display
 Provoke a failure affecting the selected path
 Verify the SNC alarm generation in the routing display
 Open the A1330AS and check the presence of the same SNC alarms.
 Select a node and stop one of its GMRE processes
 Verify that the NPA symbol get the new alarm severity, and verify the elementary alarms details: Action----
>Alarms--->Details--->Elementary Alarms
 Check that the same alarm is automatically displayed on the A1330AS interface

46